UI tweaks

This PR:

makes the navbar links white and adds an underline to them when you hover over them
removes the visualizer descriptions from the homepage
adds an underline to the homepage 'scope button when you hover over it
uses the footer color for homepage "Go to the 'Scope" button
makes the Numberscope background image a link to the 'scope
adds GitHub and Twitter links to footer
eliminates space from the acknowledgements link in footer

Oops, sorry, didn't notice you had filed this, I guess it got lost in the github updates on Slack. (Feel free to ping me when you need a review.) Looking now.

OK, I offer an additional commit with two points:

Until now, the layout has had the footer, with its nice acknowledgments, positioned just off the bottom of the screen -- apparently deliberately. This modifies the layout so that on the Home page on a PC the footer should make it onto the page, so that people have a chance of seeing the info there (otherwise there doesn't seem to be any motivation to scroll down on the Home view). Note this involved tweaking some dimensions; I put vertical dimensions into the "ex" unit which is intended for vertical use; "em" is primarily intended for horizontal use.
Three different IDs for the sake of making all the links the same color niggled at me, so I found the CSS specifier that would override Bootstrap's setting.

Please try/review and if there's anything you'd prefer to roll back, let me know.

Until now, the layout has had the footer, with its nice acknowledgments, positioned just off the bottom of the screen -- apparently deliberately. This modifies the layout so that on the Home page on a PC the footer should make it onto the page, so that people have a chance of seeing the info there (otherwise there doesn't seem to be any motivation to scroll down on the Home view). Note this involved tweaking some dimensions; I put vertical dimensions into the "ex" unit which is intended for vertical use; "em" is primarily intended for horizontal use.

I tried to get the footer to stick to the bottom of the page using my limited front-end skills. Unfortunately, it seems like we'll have to live with either some space underneath the footer or the footer being off screen. I don't think it's worth our time (at this point) to fuss with it too much more.

Three different IDs for the sake of making all the links the same color niggled at me, so I found the CSS specifier that would override Bootstrap's setting.

Thank you.

Re the footer issue: I tried to follow this tutorial because I've had success with it in the past, but it didn't work.

tried to get the footer to stick to the bottom of the page using my limited front-end skills

Aha. I truly did not realize that was the design intent since i basically have never seen the footer on screen until i scrolled. I will give it a whirl to make this a sticky footer whose bottom is exactly the bottom of the screen. That should definitely be doable. Then the bundle cards should scroll leaving the header and footer in place, which all sounds fine.

Is this latest commit I just added the sort of thing you were looking for? I'll be honest I thought the footer taller than the top navbar looked weird but I managed to pare it down to the same thickness, I think it looks OK that way. But @liam-mulhall @katestange is it now weird that the top bar scrolls off the top but the footer doesn't? To me it sort of makes the nav bar look less important than the footer, which I think is reversed. Should we make them both be pinned? Pin just the top nav bar and put the footer at the bottom with the content between its natural height, just make sure it's visible on the home page? Or go back to neither of them pinned, and let everything scroll, just make sure that everything fits on a typical screen on the homepage?  I am no graphic designer, so thanks for your thoughts.

Is this latest commit I just added the sort of thing you were looking for?

No. Ideally:

the footer sits underneath the "main content" and never overlaps with any "main content" (I'm not referring specifically to the <main> tag here, I mean the main content as in the featured content of the page)
if the content is too long for the viewport, the footer is pushed down past the end of the content (and therefore offscreen)
if the content is too short for the viewport, the footer sits flush to the bottom of the viewport

I'll be honest I thought the footer taller than the top navbar looked weird but I managed to pare it down to the same thickness, I think it looks OK that way.

It looks fine to me.

is it now weird that the top bar scrolls off the top but the footer doesn't?

Yes.

Should we make them both be pinned?

I don't like pinned navbars and footers, but whether they're pinned is not a hill I'm willing to die on.

Or go back to neither of them pinned, and let everything scroll, just make sure that everything fits on a typical screen on the homepage?

This is the approach I'd prefer for now.

I wasn't pushing for pinning. I misunderstood the design intent. I will change the CSS so that:

Nothing is pinned
The footer sits at or below the natural content end.
If the natural content ends before the full screen height, extra space is added so the footer sits at the very bottom of the screen.
Will post when I have that working.

OK, I believe the footer is now working the way you intended, and as far as making the CSS more consistent across the site, see my latest comments in the review above. Please look over when you can, and if it looks OK to you I will be happy to merge. If you think some of the styling changes are unattractive or inappropriate, feel free to suggest or implement alternatives. Otherwise I think this is good to go.

Unless @katestange would like to look these changes over, I think it's ready to merge, @gwhitney.

I think they really are just tweaks, and I don't see any other concerns, so I am going ahead with the merge. Thanks for initiating these cleanups!


jetbrains: update

Motivation for this change
jetbrains.clion: 2021.1 -> 2021.1.1
jetbrains.datagrip: 2021.1 -> 2021.1.1
jetbrains.goland: 2021.1 -> 2021.1.1
jetbrains.idea-community: 2021.1 -> 2021.1.1
jetbrains.idea-ultimate: 2021.1 -> 2021.1.1
jetbrains.phpstorm: 2021.1 -> 2021.1.2
jetbrains.pycharm-community: 2021.1 -> 2021.1.1
jetbrains.pycharm-professional: 2021.1 -> 2021.1.1
jetbrains.rider: 2021.1.1 -> 2021.1.2
jetbrains.ruby-mine: 2021.1 -> 2021.1.1
jetbrains.webstorm: 2021.1 -> 2021.1.1
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 121421 at 4c91aa7b run on aarch64-linux 1

9 packages failed to build:

jetbrains.clion
jetbrains.datagrip
jetbrains.goland
jetbrains.phpstorm
jetbrains.pycharm-community
jetbrains.pycharm-professional
jetbrains.rider
jetbrains.ruby-mine
jetbrains.webstorm

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.


Add stateful applications for controller switching

What is the purpose of the change
Using MySQL to Switch Stateful Controllers in Nacos
Brief changelog
Verifying this change
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist.
[ ] Run `mvn clean compile --batch-mode -DskipTests=false -Dcheckstyle.skip=false -Drat.skip=false -Dmaven.javadoc.skip=true to make sure basic checks pass.

Codecov Report

Merging #1194 (4ad947f) into refactor-with-go (cf1c91b) will not change coverage.
The diff coverage is n/a.

@@                Coverage Diff                @@
##           refactor-with-go    #1194   +/-   ##
=================================================
  Coverage             49.47%   49.47%
=================================================
  Files                    95       95
  Lines                  5114     5114
  Branches                 41       41
=================================================
  Hits                   2530     2530
  Misses                 2325     2325
  Partials                259      259

Impacted Files
Coverage Δ

dubbo-admin-ui/src/api/menu.js
0.00% <ø> (ø)

dubbo-admin-ui/src/components/ServiceDetail.vue
0.00% <ø> (ø)

dubbo-admin-ui/src/components/apiDocs/ApiForm.vue
0.00% <ø> (ø)

dubbo-admin-ui/src/components/public/AceEditor.vue
0.00% <ø> (ø)

...ubbo-admin-ui/src/components/public/Breadcrumb.vue
0.00% <ø> (ø)

dubbo-admin-ui/src/components/public/Drawer.vue
0.00% <ø> (ø)

dubbo-admin-ui/src/router/index.js
0.00% <ø> (ø)

dubbo-admin-ui/src/util/index.js
0.00% <ø> (ø)

... and 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Question:

Question on: https://github.com/microsoft/PartnerResources/tree/master/_docs/Azure/Data, Analytics, and AI/Microsoft Purview.md
Under the Fundamentals section What is Data Governance link points to content that does not appear to related to data governance. I am not sure if the title is wrong or the link is wrong.

Thank you! It should've linked to the "What is data governance?" session in the academy but the link wasn't formatted correctly -- this should be resolved.


fix: emit target_reached signal after updating state

Backport to 3.x for the fix in #67939, as discussed in that PR

Needs rebase to fix iOS build issue (since fixed in 3.x).

✅  @akien-mga

Thanks!

Cherry-picked for 3.5.2


Server Tasks is querying non-enabled nodes and showing an Error Triangle

It ought to not bother trying non-enabled nodes

Changing it so it will still hit disabled nodes (in case they are still up and doing work), but will ignore errors from disabled nodes.
Also the errors in the triangle were not being cleared prior to refresh so have fixed that.

Fixed in >7.4.4


Multilingual collections

Hello guys,
Does any body knows a way to have multilingual versions of a collection entry for example?
Is something that can be done in cockpit?
Regards,
Diamantis

Hi @diamantisk!
In the cockpit admin go to settings -> settings add the following to the config.yaml file:
# define the languages you want to manage
languages:
    en: Englisch
    nl: Dutch

Then while adding or editing fields of a collection you can Localize a field. When creating or editing a entry you can select the language on the right sidebar.
See the orange boxes on the images to clarify the last 2 steps.

It worked as expected! Thank you very much!


feat(resolvers/antdv.ts): make form that doesn't have prefix in antdv compatible

Description
Add option.resolvePrefix in AntDesignVueResolver's paramater to deside whether to resolve prefix 'A' or not.
If option.resolvePrefix is undefined or false, AntDesignVueResolver will perform as before. And if it is true, it will resolve form like LayoutContent rather than ALayoutContent.
Why did I do this
At the ant-design, which is the original version of antdv, we usually use form like LayoutContent rather than ALayoutContent to import the component. But AntDesignVueResolver only resolve form like ALayoutContent, so that I wirte this PR to make form like LayoutContent compatible by options.resolvePrefix.
Additional Content
I test this in my protect and it perform perfectly.

I think change the option to prefix is better, the prefix's type is boolean |  string , the default value is A,if you need an empty prefix,you can set false

I think change the option to prefix is better, the prefix's type is boolean | string , the default value is A,if you need an empty prefix,you can set false

It's a good idea, I will modify this later today.

I think change the option to prefix is better, the prefix's type is boolean | string , the default value is A,if you need an empty prefix,you can set false

I think that assigning prefix '' to replace false could be better, so that the prefix's type can be string only. And it actually performs perfectly.


Dev cli

Updating Ent and Std instructions for greenfield deploments

@kriation  , Updating Ent and Std instructions for greenfield deployments , please review am merge.


Non-existent file is referenced by scaling_data_injestion

We're asked to COPY a file which we're never provided: psql -c "\COPY counters FROM 'counters-20160304.csv' (FORMAT CSV)"
(edited to include the correct url)
https://docs.citusdata.com/en/v6.0/performance/scaling_data_ingestion.html
In fact, this page has lots of references to files which don't exist, making it difficult to follow along.

Our benchmarking steps have all changed and use pgbench scripts to populate tables rather than telling the user to download data files.


Release proposal: v1.34.1

New decade, new libuv 🍾
As the v1.x branch currently stands, there are a number of commits queued up, primarily for build/compile issues and better support on Tier 3 platforms. I'd like to release 1.34.1 next week (1/5 - 1/11). Please raise any comments or concerns here.

Upgrading libuv in node will close out https://github.com/nodejs/node/issues/31170 now that #2597 has been merged.

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1706/
Node.js integration CI: https://ci.nodejs.org/view/libuv/job/libuv-in-node/120/

What's that pipe_server_close failure? Is there an open issue?

Not that I'm aware of.


Examples out of date?

It would appear this documentation is out of date possibly. When I attempt to run these scripts I get the following error
az deployment: 'group' is not in the 'az deployment' command group. See 'az deployment --help'. If the command is from an extension, please make sure the corresponding extension is installed. To learn more about extensions, please visit https://docs.microsoft.com/en-us/cli/azure/azure-cli-extensions-overview

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

ID: f0aca150-4747-7670-f465-7439aecc40e5
Version Independent ID: f836844c-0089-1477-57af-43a76181e5d6
Content: Deploy resources with Azure CLI and template - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/deploy-cli.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

Never mind, I used winget to update my azure cli. Apparently it was out of date.

Thanks for the update @AgSync-Aaron . We will now close this issue.


Markdown editor inline styling can fall into broken state

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
Markdown editor inline marks (e.g. bold, italic) can become stuck in an active state
- If the current behavior is a bug, please provide the steps to reproduce.

Enter text in the markdown editor
With no text selected, activate an inline mark, such as bold
In the same block that is currently focused, select some text and attempt to toggle inline marks

- What is the expected behavior?

Inline marks should toggle on and off when toolbar buttons are clicked

- Please mention your CMS, node.js, and operating system version.

Confirmed in 0.6.0 and 0.7.2.

Loosely related to #774.

This looks to have been addressed through the Slate 0.30 upgrade.


Game crashes not sure why

Minecraft Version
1.20.x
Mod Loader Version
47.2.17 not fabric but forge
Mod Version
1.20.1 - 6.0.3
Describe the Issue
playing a bettermc forge playthrough and wanted to add teird and it wouldn't boot up for some reason its strange
latest.log
crash-2024-03-09_17.05.20-fml.txt
Do you use any other mods except the required ones?
yes.

O.o I only support fabric out of time reasons.


Bus Error on Apple Silicon on clicking "Calibrate Capture Volume"

Thank you for great tool.
Steps to reproduce:

On apple silicon, follow installation instruction
Calibrate camera's intrinsic parameters
Place extrinsic parameter video
Click "Calibrate Capture Volume"
The program crashes. Log on terminal says "zsh: bus error".

Note

This issue is caused by a bug in external library.

np.linalg.inv  is called in non-main thread. (caliscope.cameras.camera_array_initializer.get_inverted_stereopair).
On Apple silicon, certain numpy function calls do not work outside main thread (!).

The following lines fix this issue. (credit to this answer in stackoverflow)

export MKL_NUM_THREADS=1
export NUMEXPR_NUM_THREADS=1
export OMP_NUM_THREADS=1

It may be nice to get this issue up for a while, for reference.

Thank you for this information! I've updated the README with a link back to this issue. I'm running Windows at the moment so I really appreciate you being able to provide this help.

Closing now that this is made explicit on the README


Exponential notation with a plus sign gets formatted to cause a syntax error.

Description
The exponential notation of a number with a plus sign between the "e" and the power of 10 (i.e. "2e+3") will get formatted to cause a javascript SyntaxError (i.e. "2e + 3").  You can write the code without a plus sign (i.e. "2e3"), but it is valid JavaScript to have the plus sign.  The Number.prototype.toExponential() method returns a formatted string that has the plus sign in it.
Input Before Beautification
This is what the code looked like before:
var x = 2e+3 + 2;
var z = 2e3 + 2;
var y = 2e-3 + 2;

Expected Output
The beautified code should have looked like this:
var x = 2e+3 + 2;
var z = 2e3 + 2;
var y = 2e-3 + 2;

Actual Output
The beautified code actually looked like this (notice the first line has a syntax error):
var x = 2e + 3 + 2;
var z = 2e3 + 2;
var y = 2e-3 + 2;

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code has a syntax error

Checklist
I have:

[ ] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[x] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[x] Reloaded (or restarted) Atom to ensure it is not a caching issue
[x] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[ ] Generated debugging information and added link for debug.md Gist to this issue

I can reproduce the defect in Pretty Diff but not in JS Beautify.  I will open an issue for this.

Closing as a Pretty Diff bug, fixed with https://github.com/prettydiff/prettydiff/issues/385


Problems with the definition of "disability"

The definition of "disability" reads:

A Quality inhering in an Agent by virtue of a physical or mental condition that limits the Agent's movements, senses, or activities.

Does any physical or mental condition of the relevant sort count here, or only those that are internal/intrinsic to the Agent?
If the former, then it seems the definition would count an agent who is in the condition (i.e., state) of being tied up or being blindfolded as having a disability, which is clearly mistaken.
However, even if the latter, problems may remain. I am in the internal/intrinsic condition of being two-legged, and that condition limits my movements in certain ways, yet I do not have a disability by virtue of being in that condition. Similarly, I am in the internal/intrinsic condition of having a certain eye structure, and that condition limits my senses (by, e.g., making me unable to see in the ultraviolet range), yet (again) I do not have a disability by virtue of having that eye structure.

This paper (partially by Alex Cox @APCox  and Mark Jensen @mark-jensen ) goes a long way in addressing these concerns, and 'blindness' can be seen as a metaphor for other kinds of 'disabilities'.
Some disabilities are temporary, some permanent, and even what counts as a disability can vary from context to context, but there is a rich area here to explore.
The current term, as you have pointed out, is agnostic on many of these issues to allow users to be flexible with what more specific kind of disability they are modeling. In many cases, the 'gain' or 'loss' of disposition classes may be useful. However, the process of losing a disposition itself is not a quality, and the term 'disability' would refer to that process, and therefore should be thought of as a kind of measurement. (of some process having occurred). So, by calling disability a quality implicitly references this past un-disabled state, and goes into measurement territory.
There are many other things to consider, but those come to mind first.
In any event, this term can be improved upon with some some clarification and better design patterns.

@cameronmore:
Thanks for the paper! I'll give it a look. :)
You might be being too generous when you say that I pointed out the flexibility of the definition. I was simply putting forward some purported counterexamples to it.
I do agree that such flexibility is desirable. However, counterexamples are, presumably, undesirable. Although perhaps you meant to deny that the cases I presented constitute counterexamples? Sorry, that wasn't entirely clear to me.

@cameronmore:
I finally got a chance to read the paper on blindness you linked to. Thanks again for referring me to it. I found it interesting and enjoyable, and something like the proffered account of blindness seems promising. Perhaps, as I think you were suggesting, something like it, suitably generalized, could be used to formulate a more satisfactory replacement for the current definition of 'disability'.
[Despite being a fan of the paper, I do have some criticisms of it. For one thing, I think the authors are mistaken when they claim that in BFO, a realizable entity cannot undergo a decrease. That claim certainly conflicts with the definitions of 'damaged stasis' and 'wounded stasis' in the Event Ontology, and I believe it also conflicts with some of what Barry Smith has said in his writings on realizable entities, though I'd have to go back and reread them to be sure.
For another, I don't think the proffered account of blindness--according to which "blindness is a reduction of the trigger conditions under which the sight function is realized"--can be quite right. (Hence why I said only that something like it seems promising.) Here are two worries about it:

It seems natural to treat a reduction as a process during which something is reduced, a process which ends when the reducing stops. But if that's right, then the proffered account gets the temporal facts about blindness wrong: By identifying blindness with the relevant reduction process, it implies that someone's blindness ceases when that process ends. In fact, however, someone's blindness will typically outlast the reduction process.
The proffered account seems unable to handle certain clear-cut cases of blindness. Consider, in particular, people with congenital blindness whose sight is always limited to the same degree and hence never experience a reduction of the relevant sort. The proffered account seems to imply, incorrectly, that these people are not blind.]

the authors are mistaken when they claim that in BFO, a realizable entity cannot undergo a decrease

As I understand, this is not quite a settled issue, and the Common Core Ontologies offer an account of realization and disposition that extends BFO, but does not (aim to) contradict it. BFO is agnostic with respect to the representation of actuality v. possibility, for example, and the CCO offers one, of multiple, interpretations with the modal relation ontology.

It seems natural to treat a reduction as a process during which something is reduced, a process which ends when the reducing stops. But if that's right, then the proffered account gets the temporal facts about blindness wrong: By identifying blindness with the relevant reduction process, it implies that someone's blindness ceases when that process ends. In fact, however, someone's blindness will typically outlast the reduction process.

Consider realization to be a formula of disposition + stimulus + context = realization, where realization causes some effect. For example, my hand has the disposition to grip something, and when it realizes this disposition, something in the world is actually gripped (a change in a given state of affairs has occurred).
Your response conflates parts of these activities of reduction and being-reduced. There is a process which reduces the ability for the triggering stimulus (light) to reach the relevant parts of the eye, and that process has the result that the disposition to absorb light and see is reduced. The effect of the reduction can outlast the process of reducing--there's no problem with that from the BFO perspective. The paper may have failed to articulate that, but it is certainly on the right track.

The proffered account seems unable to handle certain clear-cut cases of blindness. Consider, in particular, people with congenital blindness whose sight is always limited to the same degree and hence never experience a reduction of the relevant sort. The proffered account seems to imply, incorrectly, that these people are not blind.

Well, sort of. Whether one is born without the ability to see has no bearing on the fact that the eye does in fact bear that function, it just never may be realized because of some injury or defect.

I think fully expanding out the ideas in the paper would be useful. Do you have a suggested definition we could replace the current one with? If you offer a start, we can wordsmith something here, but the paper is certainly a good start as you mentioned.

@cameronmore:
Let me start by addressing the replies you give in your first comment to my three criticisms of the paper:

First criticism: I think we basically agree here: BFO is neutral about whether a realizable entity can undergo a decrease. Indeed, my criticism was that the paper didn't take BFO to be neutral, but instead took BFO to entail that a realizable entity cannot undergo a decrease.
Second criticism: I agree with the distinctions you draw here (although I'm not sure which of the things you distinguish between you think I conflated). I'm pretty sure I also agree with your other claims about the mechanism behind the onset of blindness. But I'm not convinced by your reply. You note, correctly, that "the effect of the reduction can outlast the process of reducing" (my italics). However, the proffered account of blindness--i.e., "blindness is a reduction of the trigger conditions under which the sight function is realized"--identifies blindness with the reduction itself, not with its effect. It thus implies that blindness lasts only as long as the reduction lasts, regardless of whether its effect lasts longer. (Of course, an account which instead identified blindness with the effect of the reduction would have different, and perhaps more plausible, implications concerning the temporal facts about blindness.)
Third criticism: I admit I'm puzzled by your reply here. You point out that in the cases of congenital blindness I describe, the eye still bears the function to see. But I never denied that the function exists in those cases (and, in fact, I agree that it does). What I did deny is that "a reduction of the trigger conditions under which the sight function is realized" exists in those cases (because in those cases, the trigger conditions remain constant for the person's entire life). Since the proffered account identifies blindness with such a reduction, it implies that no blindness exists in those cases.

In your second comment, you ask whether I have a suggested replacement definition for 'disability'. I wish that I did, but I suspect that constructing a satisfactory definition would be a very tough task. I will say this, though: I'm inclined to think that a satisfactory definition would involve the notion of canonicity, a la the Foundational Model of Anatomy.
Your request for a replacement definition did raise a question for me, though. In my ongoing exploration of CCO, I've noticed that every class has a definition. Why is this? Don't get me wrong; I understand that it's best to provide a definition when possible. But in the case of terms like 'disability', where a satisfactory definition is very difficult to construct, might it not be better to provide an elucidation, along with some clarificatory comments, instead?

@cameronmore:
Fair enough re: the paper on modeling blindness. While the line in question reads to me as a straightforward identification, you might be right that that wasn't the intent.
Thanks for your answer to my question about definitions vs. elucidations and comments. :)

I think the term vulnerability might already capture the notion of disability discussed above.
Vulnerability = A Disrupting Disposition the realization of which would disrupt a process that the bearer of the Disrupting Disposition has an interest in.
(And , Disrupting Disposition = A disposition the realization of which would disrupt a process some entity has an interest in.)
The bearer of a disability is disrupted when that disability disrupts and interferes with processes they participate in. A disability sounds like a vulnerability with some other criteria which we can still think on, but I think this is a good direction.

@cameronmore: This is an interesting proposal, and I agree with you that it's potentially promising. One question to consider might be: Should the disability be identified with the vulnerability itself--a disposition--or rather with the internal physical grounds of this disposition--a quality?

We should work offline on it a bit, glad you agree

Moving issue to discussion thread to continue development


Don't require auth for fetching public ical

The public ical endpoint is designed to be fetched by calendar applications with no authentication, so exclude it from auth enforcement.

@flooey, make sure your code change is passing flake8 validation

This probably closes #374

Hey all, just checking in on this.

Is there a reason this never got merged in @diegocepedaw ?


Kaspersky disabled WSL1

Environment
Windows build number: Microsoft Windows [Version 10.0.18363.1198]
Your Distribution version: Ubuntu-18.04 (Can't get in to view version...)
Whether the issue is on WSL 2 and/or WSL 1: WSL1

Steps to reproduce
I am required to run Kaspersky Endpoint Security for work. Yesterday, it registered a false positive and quarantined WSL. Despite restoring the (presumably) affected files, I have been unable to recover the system.
At the time, I was unzipping a tar.gz file, and Kaspersky reports that it quarantined bash, gzip, and tar, at the following addresses:
\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState\rootfs\bin\bash
\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState\rootfs\bin\gzip
\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState\rootfs\bin\tar

I have restored the files, and disabled Kaspersky to the best of my ability (while also whitelisting the above addresses for good measure), but running wsl.exe returns immediately, and starting Windows Terminal returns [process exited with code 1]. Repairing from Add or Remove Programs has not been successful.
Unfortunately, I haven't backed up the installation in about a year, and would like to recover it if at all possible. Is it possible to recover from this?
If it isn't possible to repair the system, please feel free to open another issue to discuss how I might go about safely recovering the data from my home directory to a fresh installation. Thanks!

WSL logs: https://aka.ms/AAaiyvd
Expected behavior
WSL starts as usual.
Actual behavior
WSL does not start.

Most probably the restoration process did not restore all the file attributes, so you will need to reinstall your distro. See https://devblogs.microsoft.com/commandline/do-not-change-linux-files-using-windows-apps-and-tools/
Report the error to Kaspersky, they screwed it up, so they should fix it.

You can likely generate an archive of yohr distro with wsl.exe --export which you can use in a new installation to extract your home directory.

Thanks for the advice; I expect that corruption is the case. I also didn't realize the proscription on modifying the files in %localappdata% extended to access, which I certainly did at some point, so that is probably the culprit here.
Fortunately, I was able to generate the archive with wsl.exe --export. Are there details of the format that I can use to extract what I need? If there was a way to diff the contents of the archive with a clean distro, that would be ideal... Just want to make sure I don't miss anything outside of the home directory.
I'll leave this open for the time being until I get a response from Kaspersky, but at the moment will proceed with a reinstallation (barring any other tricky ideas).

So, the exported archive is a standard tar or tar.gz file -- you can access it, or extract it, with the tar utility. Diffing the contents is going to be a bit of a bear...

This is going t obe a bit wild.
Can you try launching your existing distribution and specifying the shell directly?
wsl -e /bin/sh

This might get you in.
If you can get in:
chmod +x /bin/bash /bin/gzip /bin/tar

Then try launching wsl normally.

Wow! That worked! I had to sudo chmod, but everything appears to be in order otherwise. Thank you so much!


Export/Import or backup/restore Database in DBFlow

i use DBFlow for my sql lite jobs in android program. i need export or backup my data base and import or restore from special location in memory of phone. how can i do this?

any one?

you can either use the @Database(backupEnabled = true) and call backupDatabase() on the DatabaseDefinition or simple file copy.


Back Propagate Post v0.1.1 Release

Current coverage is 98.38%

Merging #15 into develop will not affect coverage as of deed994

@@            develop     #15   diff @@
=======================================
  Files             2       2
  Stmts            62      62
  Branches          0       0
  Methods           0       0
=======================================
  Hit              61      61
  Partial           0       0
  Missed            1       1

Review entire Coverage Diff as of deed994

Powered by Codecov. Updated on successful CI builds.


Oauth2 v2 is incompatible and Oauth2 dependency is not bounded to <2.0.0

Version 2.x of the oauth2 gem is incompatible - using it will result in "invalid client id" errors on attempting a BC store install.
Since the oauth2 version for this gem isn't limited to less than 2.0, any new installs or bundle updates will automatically pull in the absolute latest version causing project breakage.
While upgrading this gem to be compatible with oauth2 v2 would be a nice-to-have, at a minimum the oauth2 dependency should be limited to 1.x.
EDIT: Workaround is to explicitly include oauth2 in your gemfile with version 1.x

I was also able to work around this by explicitly adding client_id and client_secret to the set of token_params configured for this provider:

This works because the OAuth builder includes any token_params content within the set passed into the QAuth2 gem (source), which then results in these being incorporated into the request body sent to the BigCommerce OAuth token creation endpoint (source).

@JCaporuscio, @hstrowd I'll get new release out which ensures we don't upgrade path oauth2 2.0.


Replace --output-resolution and --infant with --output-spaces

Summary
Related to https://github.com/PennLINC/qsiprep/issues/681.

We'll need a way to define custom resolutions with niworkflows' space classes before we can do this.


VSCODE Open with multiple windows every time!

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.57.1 (user setup)
OS Version: WIN 10 version 21h1, Compilation: 19043.1052

Steps to Reproduce:

Every time I open it the vscode or open a new window with right click, it opens 10 or more empty windows with the last opened.
I need a resolution please, this is annoying and discouraging me from using this editor.

Follow the gif and understand my problem

What is the contents of these windows? And closing them one by one would always restore them?

What is the contents of these windows? And closing them one by one would always restore them?

The contents of one window are the last open workspace, and the other nine windows are all empty. And after closing all windows, when I try to open the editor again the same ten windows open again.

Are there maybe dirty files in them that restore? Or do the empty windows somewhere read "Untitled Workspace" in explorer or title?

There is no junk being restored in the windows, they all open as "Untitled workspace" or no title in the window title or in the vscode file explorer. As in the gif below:

@rxngui in one of those empty windows, can you:

hit Ctrl+Shift+P
execute the Developer: Log Working Copies command
open dev tools (from the Help menu)
click on Console if not already opened
copy the output

It is possibly looking somewhat like this:
INFO
[Working Copies]
<none>

[Backups]
untitled:Untitled-1?typeId=textAreaWorkingCopy (typeId: textAreaWorkingCopy)

My console its this:

My output its this:
[Working Copies]
<none>

[Backups]
vsls:/admin/classes/classUpload.php (typeId: <no typeId>)

And what can i do now?

@rxngui do you recall having had installed a extension (possibly PHP related?) that would provide a custom editor where you maybe left dirty changes?
Bottom line: this indicates there is a backup of a custom editor that we enforce to restore from a previous session.
I will see if I can make the experience better, e.g. show a notification when the extension is no longer installed.
As a last resort, you can go into %APPDATA%\User\ and delete the Backups folder. CAUTION: if you have any other dirty or untitled files, they would be gone then.

I remember installing a PHP related extension, but it was in another vscode installation. But I just deleted the Backups folder and everything is back to normal. But I couldn't access it through %APPDATA%\User\, I searched in the file explorer on the disk that has VSCODE installed for Backups.
I accessed the folder and permanently deleted everything inside, just in case.
Thank you so much for supporting Benjamin Pasero, and congratulations on the incredible work you've been doing in supporting the users of this wonderful Editor. 😊

hit Ctrl+Shift+P
execute the Developer: Log Working Copies command
open dev tools (from the Help menu)
click on Console if not already opened
copy the output

It is possibly looking somewhat like this:

My console returns this output:
 INFO
[Working Copies]
<none>

[Backups]
<none>

Hm, can you check for contents in that Backup folder or rename it to see if that helps?

This works, thanks!

Removing Backups folder works.

I pushed a fix for this to allow to close the empty window and have it not restore anymore and https://github.com/microsoft/vscode/issues/127163 is the real solution with nice UI.

Anyone suffering from this issue, please try out our insiders release and report back if that helped:
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/
You may see the empty windows open once more, but closing them should stop restoring them.


Backport of 2561 in stable-3.1

Backport of #2561 in stable-3.1

jenkins test luminous-ansible2.4-centos7_cluster

jenkins test luminous-ansible2.4-ooo_collocation

jenkins test luminous-ansible2.4-docker_cluster_collocation

jenkins test luminous-ansible2.4-ooo_collocation

jenkins test luminous-ansible2.4-ooo_collocation


AppDomainAssemblyCatalog correctly unloads the assemblies that were probed for any Nancy reference.

Prerequisites

[X] I have written a descriptive pull-request title
[X] I have verified that there are no overlapping pull-requests open
[X] I have verified that I am following the Nancy code style guidelines
[X] I have provided test coverage for my change (where applicable)

Description
AppDomainAssemblyCatalog, in order to load all the assemblies that have a reference to Nancy, probes for the loaded assemblies as well as those that are in the "load path". The probing occurs by purposefully loading the assembly into a temporal AppDomain that is unloaded after the loading of useful assemblies is complete.
However this is accomplished by using AppDomain.Load(), and as specified by MSDN, this is just a convenience method for Assembly.Load(). This means that the current code loads all the assemblies into both the inspection AppDomain and AppDomain.Current, when the code intent was clear that this is not the desired behavior.
Moreover, if the assembly is passed between application domains, because it is not serializable (MarshalByRefObject), it would be loaded as well into both domains, therefore the solution is to make a remote proxy probing instance which loads the assembly in the inspection domain and locally determines if the desired reference exists.

Hi @arturosevilla, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@arturosevilla, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

I believe #2653 is breaking my PR.

You should rebase your PR and it should go away

That did it 👍

This is a really nice PR! :sparkles: Thanks :heart:

@khellang care to give this one last round of reviewing before we pull it in?

@khellang did you happen to kick the tires on it when you were working on it? Quick sanity check that everything is functioning as expected

@thecodejunkie Nope, but I'm assuming we have at least some test coverage there. Maybe that should be a billet point for 2.0? Do a coverage scan, see if we have big holes anywhere, and fix those?

@khellang it's mostly a runtime thing so hard to put good tests around it. Improving out coverage is always a good thing 👍


intermittent connection refused on 6443

Environmental Info:
K3s Version:
WARN[0000] Failed to resolve user home directory: getwd: no such file or directory
k3s version v1.27.4+k3s1 (36645e73)
go version go1.20.6
Node(s) CPU architecture, OS, and Version:
Linux  5.15.0-1035-raspi #38-Ubuntu SMP PREEMPT Tue Jul 18 12:17:11 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
Cluster Configuration:
right now only the control-plane/master is installed with a external postgresDB
Describe the bug:
intermittently the below error is received when running "k3s kubectl get nodes"
The connection to the server <IP_ADDRESS>:6443 was refused - did you specify the right host or port?
Steps To Reproduce:
completely removed k3s
ran install with : curl -sfL https://get.k3s.io | sh -s - server --datastore-endpoint="postgres://"
execute k3s kubectl get nodes
Expected behavior:
NAME         STATUS   ROLES                  AGE   VERSION
   Ready    control-plane,master   11m   v1.27.4+k3s1
Actual behavior:
The connection to the server <IP_ADDRESS>:6443 was refused - did you specify the right host or port?
Additional context / logs:

Sounds like it's crashing. Have you checked the server logs?
if the postgres database is also running on the Pi, you probably don't have enough CPU or disk IO to support that database engine. This would be indicated by latency warnings in the k3s service log, followed by the service crashing - usually due to failure to renew leases in a timely manner.


Check voltage

If you haven't already, please read through our contributing guidelines before opening your PR
What is the purpose of this PR?
Closes #127.
How did you implement your changes
Retrieve the detector voltage from each FOV json in the run and check whether it stays constant or changes. If not the same throughout, identify the FOV names and voltage values at each point of change in the run and print them in an error statement.
Remaining issues
If there are specific areas of your implementation that you feel need specific feedback, or if there are things you aren't sure about, please highlight them here

yep, works on the jsons in data/tissue and I just double checked it on a run from 6-13


alasql.fn.total is not a function

Spawn from https://github.com/AlaSQL/alasql-sqllogictest/blob/a10ff82e75edafae2ce96c9d02ab47cfc85d4507/results/output.md#3620-testevidenceslt_lang_aggfunctest
SELECT total(y) FROM t1

alasql.fn.total is not a function

We would like to support TOTAL. Its almost the same as SUM but

This function is similar to the sum() function, except in the way it handles NULL inputs. When there are no non-NULL values, then sum() returns NULL (instead of 0.0 like the total() function returns).

https://database.guide/how-sqlite-total-works/

Amazing. Thank you!
See if you can reuse some of the code so we dont duplicate everything. Also consider if it makes sense to use a function that you can call to avoid repeating typeof == 'number' && typeof ==.....
Another input: the codebase was created before the tick notation was supported. I propose that you look into using something like
var pre = 'if(
						typeof ${colexp} !="undefined"
 						&& (!g[\'$$_VALUES_${colas}'][${colexp}])
					){`;

instead of
var pre =
							'if(typeof ' +
							colexp +
							'!="undefined" && (!g[\'$$_VALUES_' +
							colas +
							"'][" +
							colexp +
							'])) {';

as it makes everything much easier to read.

@mathiasrw what should be the expected behavior if strings or booleans or nulls exist while calculating the total? Is my assumption correct for the following case?
var data = [
{a: null, b: 9, c: true, c2: 1, d: null, e: 'XYZ1', f: new Number(2)},
{a: null, b: 1, c: false, c2: false, d: 5, e: 'XYZ2', f: new Number(11)},
];
expected: {a: 0, b: 10, c: 0, c2: 1, d: 5, e: 0, f: 13}

That is such a good question.
Hmmm. Let me check the other DBs.

I propose aggregating the values if they can be translated natively to a number.
A bit like this
sum = sum + (val == +val ? +val:0)

This means the following result:
var data = [
			{a: null, b: 9, c: true, c2: 1, d: null, e: 'XYZ1', f: new Number(2)},
			{a: null, b: 1, c: false, c2: false, d: 5, e: 'XYZ2', f: new Number(11)},
		];

expected: {a: 0, b: 10, c: 1, c2: 1, d: 5, e: 0, f: 13}

Notice how true = 1 so c is different than your proposal

the sum of numbers in strings like '+44' and '-43' = 1.  shouldn't we cover this case in aggregator SUM as well? or it is a specific case of aggregator TOTAL only?

We could expand SUM if that makes it easier regarding the implementataion - but its a breaking change, so lets only do it if that makes your fix easier

Released as part of v2.5.0


Clean up imported CMake target naming

For most imported targets I've followed the Dependency::dependency naming convention. I've also moved the target creation to the Find*.cmake files. For the allocators I've named the target hpx_dependencies_allocator. It has no namespace just like our other internal targets (e.g. hpx_private_flags). The old hpx::boost target is now called hpx_dependencies_boost as it's also an internal target and depends on multiple Boost targets. In other cases I've simply replaced the hpx::boost::* targets by Boost::*.
~The only bigger change I did was to change the MPI handling. It now links to the target MPI::MPI_CXX (provided by CMake's FindMPI.cmake). I haven't actually tried this though.~ I dropped the MPI changes (except for renaming). I've opened #4484 to track that instead.
For cleaning up CUDA handling I've opened #4482.
All of this will be slightly simpler as well once we can propagate dependencies correctly from modules (#4135).

Let's see if this passes tests now. It turns out our pkgconfig file generation did not handle imported targets (not the same as interface targets, apparently). I've added code to handle it at least for Boost.

This looks ready to go in.


Automatically reload emotes when changing a tab, button to reload all emotes in all tabs

What should be added?
1 Automatically reload ffz, bttv, and sub emotes when you switch to a different, pre-existing tab
2 Add a button (and keybind) to reload all emotes in all tabs
Why should it be added?
1 It makes it easier to see current emotes without having to reload emotes manually
2 Sometimes emotes fail to load in many tabs on Chatterino startup, so adding this would be useful without having to restart Chatterino completely, also it would be an easy way to reload all the emotes for channels without having to do it individually, one by one.

Automatically reload ffz, bttv, and sub emotes when you switch to a different, pre-existing tab

I don't agree with this, it will probably result in spamming the ffz and bttv apis.

2 Add a button (and keybind) to reload all emotes in all tabs

I like this, but due to the way splits work, I think it'd be better if this was per tab, not all tabs

Sometimes emotes fail to load in many tabs on Chatterino startup

This is most likely the result of ffz/bttv api

I've thought about this aswell, but I think if an addition was implemented that refreshed many tabs at once this may result in emotes not reloading as you mentioned, like on startup. the best option now is to just restart Chatterino until the emotes properly reload in every channel.

it will probably result in spamming the ffz and bttv apis.

Yeah I was thinking about that. Maybe it is possible to only reload emotes after you’ve been in a tab for a certain amount of seconds/time, like 5 seconds

Sometimes emotes fail to load in many tabs on Chatterino startup

This is most likely the result of ffz/bttv api

About that, it's worth noting that sometimes global emotes for 3rd party don't load and when such issue occurs, there's no other way to (re)load emotes than just restarting chatterino which is quite annoying.

Given the reasoning in the issue body I'll close this in favour of #2924 and try implementing an option to easily reload Global 3rd-party emotes without having to restart the whole application.


chore: add manual install option

With the help from this issue, this PR add a manual installation option as well as specifying directory for config.json in README
What kind of change does this PR introduce? (check at least one)

[x] Other, please describe: README

The PR fulfills these requirements:

[x] All tests are passing?
[x] New/updated tests are included?
[x] If any static assets have been updated, has ui/bindata.go been regenerated?
[x] Are there doc blocks for functions that I updated/created?
All the above don't apply to this PR

pushed a fix for indentation
was:

now:


Update vLLMInvocationLayer to accept an API key for vLLM endpoints that require authentication

This change allows developers to pass an API key to vLLMInvocationLayer so that it is correctly set in the header values with making OpenAI compatible calls.

Yup, we can add this. I don't think vLLM currently needs an API key, but maybe some other openai-like APIs expect it to be set. 👍


Process map

I think this is handy, but comes down to whether or not we have a stomach for this kind of thing in the viz.yaml
process:
  -
    id: state_geoms_dataframe
    location: cache/state_geoms_dataframe.rds
    reader: rds
    processor: geom_dataframe
    eval_args:
      class: I("state")
      mouseover: "sprintf('hovertext(\"%s\", evt)', name)"
      mouseout: I("hovertext(\" \")")

This helps us add attributes quickly, but also brings in a library for non-standard eval and has this pattern for eval_args that we don't see elsewhere.
This works w/ vizmake(), but I couldn't figure out this make error (using the makefile instead of remake)
vizlab/make/fetch.make: createBlockMakefile(block='fetch',outfile='vizlab/make/fetch.make')
make: *** [vizlab/make/fetch.make] Error 1

Exited with status 2.

This also jumped over #23 since that wasn't done, but what I did here for fetch should be tossed and replaced with the solution for #23.
Feedback? @aappling-usgs @dblodgett-usgs

I'm not a big fan of adding more to viz.yml. I'd also be concerned that we would quickly find a need to construct the contents of eval_args in code anyways.
Another thing to consider is that sf data.frames are supposed to help us use dplyr verbs more easily. This goes away from that practice toward something that is a bit less intuitive (IMHO). I think it might be nice to embrace that direction and keep doing the dplyr mutate/ifelse/etc. chains to build up these svg classes and stuff.
I think the pattern in the helper function is great but am not a big fan of do.call and passing ... around unless it's really needed. It's tricky to debug and not familiar to noobs 🤔 like me...
Not saying don't do it, just stating a downside of a "fancy" pattern like this.


Added Lambda "Quantization Level" Parameter

Adds a quantization level parameter to allow for more gradual introduction of quantization rather than applying it abruptly to the weights and activations for each tensor. Quantization Level = 0 means that there is no quantization happening. Quantization Level = 1 means full quantization. This quantization level is only applied during training to the activations and linears.

From discussion change kwargs to iter_num directly.
And also provide a demo script that shows difference with and without gradual quantization with tinystories (verifying inference too)


updated dependency to support symfony/process v5

Some of my other packages require symfony/process v5 as a minimum, so it would be really nice to get this pulled.

Fixed in v1.4.0


dupradar

add dupradar

This was added with PR #25 but I think we need to revisit tests once we have a test dataset.


merge package from arlac77/npm-package-template

package.json

chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(engines<EMAIL_ADDRESS>chore(package): add xo from template
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

.travis.yml

chore(travis): remove node versions 10.14
chore(travis): add node versions 10.14.1

:tada: This PR is included in version 5.0.48 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Catch for htmllint promise fails, updated dependencies, travis.yml, e…

…xecute tests properly, assert output, remove obsolete clean step

Is this project dead? Would be nice to get the html lint version updated without having to hack it with npm-shrinkwrap or yarn.lock


Add option to not lock device and randomise device list when picking device for running tests

Is your feature request related to a problem? Please describe.
Device cloud providers like browserstack will have multiple number of devices with same phone model and android version. If we lock the device, the chance of getting device reduces even if browserstack has the device. Also while running large suite of tests beyond 150 tests, the device cache tend to get corrupted causing lot of tests to get skipped.
Describe the solution you'd like
Add option to no lock/engage devices in device cache. This is make sure device cache does not get corrupted. Also randomise the list before getting the device for running test so that there is higher chance of variety of devices when running with no lock option
Describe alternatives you've considered
Have not considered alternatives
Additional context
We use browserstack and ekam together. The DeviceEnagagedException issue happening occasionally when number of tests goes beyond 150. This is reducing teams trust on Ekam framework.

Feature is working as expected in ekam device manager version 1.0.2-beta


RFE: config-options: Allow additional_repos on copr to be not exact match

Example
For example in project A I have a release-nightly setup like this:
jobs:
  - job: copr_build
    trigger: pull_request
    owner: Namespace1
    project: ProjA
  - job: copr_build
    trigger: commit
    branch: main
    owner: Namespace1
    project: nightly
  - job: copr_build
    trigger: release
    owner: Namespace1
    project: release

Copr project ProjA is for CI testing, nightly is for nightly builds and release is for latest tagged releases. And I link these to project B, which could be in different namespaces, like this:
jobs:
  - job: copr_build
    trigger: pull_request
    owner: Namespace2
    project: ProjB
    additional_repos:
      - copr://Namespace1/release
  - job: copr_build
    trigger: commit
    branch: main
    project: nightly
    owner: Namespace2
    additional_repos:
      - copr://Namespace1/release
  - job: copr_build
    trigger: release
    owner: Namespace2
    project: release

Here the CI and nightly only check for the latest release versions, which might be before the downstream PR is merged
Issue
That works all fine, but what if there is a project C that does not have a dependency on project A, but resides in the same Namespace2. If we configure it like project A:
jobs:
  - job: copr_build
    trigger: pull_request
    owner: Namespace2
    project: ProjC
  - job: copr_build
    trigger: commit
    branch: main
    project: nightly
    owner: Namespace2
  - job: copr_build
    trigger: release
    owner: Namespace2
    project: release

Then there is a clash with Namespace2/nightly because in one version it has copr://Namespace1/release, and in the other it has to be empty. So it will constantly complain that it is not well configured for either case. But in practice including copr://Namespace1/release has no effect on project C, so it would be fine to leave the configuration as is for project B.
Suggestion
Add a configuration flag/variable like includes_repo, allow_additional_repos, etc. such that it will only check if a given repository is included in the list, not that the list is exactly equal.

Hi again, thanks for the report!
I think this might be related to #1974 and maybe the behaviour you are proposing should be the default, without requiring additional configuration flag/variable.

That would make config files generally simpler. But I can also see situations where you would want the current behaviour. Maybe we can just have some better variables for these:

using_repos/exclusive_repos: current behaviour, use only those repos as external (hopefully someone can find a better name)
include_repos: Just make sure it is present

Is this still relevant?

Yeah, still hitting this when trying to share copr projects, like a nightly/latest copr project design, where the nightly grows and pulls in nightly repos from other projects.


Twemsentinel

Python twemproxy agent for the master-change event and nutcracker config/restart

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Term Schedule, Can find UI library for this already made.

It seems like it does not work properly when louched, only locally


Exported column named types or exported column constants

#It would be nice if sqlboiler used schema specific named types for columns other than the golang string type.
type Account struct {
	ProfileID    string `boil:"profile_id" json:"profile_id" toml:"profile_id" yaml:"profile_id"`
	Username     string `boil:"username" json:"username" toml:"username" yaml:"username"`
	Password     string `boil:"password" json:"password" toml:"password" yaml:"password"`
	Salt string `boil:"salt" json:"salt" toml:"salt" yaml:"salt"`
}

type accountColumn string

func(a accountColumn) String() string{
	return string(a)
}

const (
	ColumnAccountProfileId accountColumn  = "profile_id"
	ColumnAccountUsername  accountColumn  = "username"
	ColumnAccountPassword  accountColumn  = "password"
	ColumnAccountSalt      accountColumn  = "salt"
)

var (
	accountColumns               = []accountColumn{ColumnAccountProfileId, ColumnAccountUsername, ColumnAccountPassword, ColumnAccountSalt}
	accountColumnsWithoutDefault = []accountColumn{ColumnAccountProfileId, ColumnAccountUsername, ColumnAccountPassword, ColumnAccountSalt}
	accountColumnsWithDefault    = []accountColumn{}
	accountPrimaryKeyColumns     = []accountColumn{ColumnAccountProfileId}
)

Having typed columns significantly increase the type safety of database calls such as Insert and Update and   team members won't have to use error prone strings to make these calls.
err := account.Insert(db, models.ColumnAccountUsername, models.ColumnAccountPassword )
err := account.Update(db, models.ColumnAccountUsername, models.ColumnAccountPassword )
This shouldn't too difficult of a refactor.  If you like the idea, I can start working on a pull request.

This feature is accomplished by using MySQL and Postgres enums which we support: https://github.com/vattle/sqlboiler#enums

Or is your idea that the enums should be typed as something else?

This feature would be unrelated to the Postgres/MySQL enums.  This is more from the standpoint of a bit more type safety.   For example:
//Current Generated Code func (o *Account) Update(exec boil.Executor, whitelist ...string) error .... func (o *Account) UpsertG(updateOnConflict bool, conflictColumns []string, updateColumns []string, whitelist ...string) error
//Proposed Generated Code func (o *Account) Update(exec boil.Executor, whitelist ...accountColumn) error ... func (o *Account) UpsertG(updateOnConflict bool, conflictColumns []accountColumn, updateColumns []accountColumn, whitelist ...accountColumn) error
Basically type string and []string would be replaced by named type accountColumn  and []accountColumn.

I fully understand this now. And the idea is actually pretty good.
There's two things that are not great about this:

Currently not everywhere in the system could use this. For example a Where() clause couldn't use it because it's not generated code. This is something that I've thought about changing in a v4 maybe after looking at another Go ORM.
The names get fairly long

This is also a breaking change so would have to be considered either optional or part of v3. Let's talk more about this one.

@FourSigma This is done now, though it doesn't use a new type, it allows a small measure more safety than using plain strings. See the latest release https://github.com/vattle/sqlboiler/releases/tag/v2.5.0


Yarn build fails if project has the word "fields" in its absolute path

Problem Description
Yarn build fails, if the absolute path to the extension has the word "fields" in it - notice the parent directory name foofields in the example below:
$ yarn build
yarn run v1.22.4
$ divi-scripts build
Creating an optimized production build...
fs.js:125
    throw err;
    ^

Error: ENOENT: no such file or directory, open '[MY_PROJECT_PATH]\foofields\my-extension\styles\style.min.css'
    at Object.openSync (fs.js:454:3)
    at Object.readFileSync (fs.js:354:35)
    at [MY_PROJECT_PATH]\foofields\my-extension\node_modules\divi-scripts\scripts\build.js:169:22
    at [MY_PROJECT_PATH]\foofields\my-extension\node_modules\webpack\lib\Compiler.js:265:13
    at Compiler.emitRecords ([MY_PROJECT_PATH]\foofields\my-extension\node_modules\webpack\lib\Compiler.js:371:38)
    at [MY_PROJECT_PATH]\foofields\my-extension\node_modules\webpack\lib\Compiler.js:258:10
    at [MY_PROJECT_PATH]\foofields\my-extension\node_modules\webpack\lib\Compiler.js:364:12
    at next ([MY_PROJECT_PATH]\foofields\my-extension\node_modules\tapable\lib\Tapable.js:218:11)
    at Compiler.<anonymous> ([MY_PROJECT_PATH]\foofields\my-extension\node_modules\webpack\lib\performance\SizeLimitsPlugin.js:99:4)
    at Compiler.applyPluginsAsyncSeries1 ([MY_PROJECT_PATH]\foofields\my-extension\node_modules\tapable\lib\Tapable.js:222:13)
    at Compiler.afterEmit ([MY_PROJECT_PATH]\foofields\my-extension\node_modules\webpack\lib\Compiler.js:361:9)
    at [MY_PROJECT_PATH]\foofields\my-extension\node_modules\webpack\lib\Compiler.js:350:15
    at [MY_PROJECT_PATH]\foofields\my-extension\node_modules\async\dist\async.js:473:16
    at iteratorCallback ([MY_PROJECT_PATH]\foofields\my-extension\node_modules\async\dist\async.js:1064:13)
    at [MY_PROJECT_PATH]\foofields\my-extension\node_modules\async\dist\async.js:969:16
    at [MY_PROJECT_PATH]\foofields\my-extension\node_modules\graceful-fs\graceful-fs.js:61:14
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

The issue stems from this specific webpack configuration rule:
{
    test: /\.(s?css|sass)$/,
    exclude: [/\.module\.css$/, /fields/],
    use: extractTextPluginFrontend.extract(
    // ...

Webpack rule tests are ran against absolute filepaths and thus the /fields/ exclusion regex leads to modules' style.css file not being bundled correctly.
Steps To Reproduce

mkdir foofields
cd foofields
npx create-divi-extension my-extension
cd my-extension
yarn build

P.S @atanas-dev says hi :)

Attached PR

https://github.com/elegantthemes/create-divi-extension/pull/417

Thanks @NaimNaimov for spotting that. This is now fixed in https://github.com/elegantthemes/create-divi-extension/pull/417


bambu-studio: Fix build

It was broken by a cgal bump in https://github.com/NixOS/nixpkgs/pull/292492
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] 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.05 Release Notes (or backporting 23.05 and 23.11 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.

I think this has broken orca-slicer, which has this patch already applied

@mabl Attempted a fix in https://github.com/NixOS/nixpkgs/pull/296839.


Ensure FileStream is used for file access where possible

Use FileStream where we can.  Certain libraries do not support overriding the file access routines, so they need the raw filesystem path, such as SQLite, CURL etc, so they will still work as intended.

@halx99 It's almost ready, just still fixing a bug in somewhere in the ZipUtils.  I'll let you know when it's all done.

@halx99 All done. This has been tested on Windows and Android with the default PosixFileStream, and all works fine.  I've also tested with a custom FileStream implementation that wraps PhysFS as a virtual file system into ZIP files, and that works well on Android and Windows.  I haven't had a chance to test iOS or Linux, but they should work as well, since I've updated any relevant fopen references in the platform specific code.

@halx99 All done. This has been tested on Windows and Android with the default PosixFileStream, and all works fine. I've also tested with a custom FileStream implementation that wraps PhysFS as a virtual file system into ZIP files, and that works well on Android and Windows. I haven't had a chance to test iOS or Linux, but they should work as well, since I've updated any relevant fopen references in the platform specific code.

Thanks for you provide this excellent feature, and I have idea abount use openFileStream, just see follow code:
std::unique_ptr<FileStream> fs(FileUtils::getInstance()->openFileStream(fullPath, mode);

This is the perfect candidate for the use of a unique_ptr, but initially I assumed it wasn't preferred after searching the engine code and find very little usage of it.  I would be more than happy to change it to use unique_ptr, since it wouldn't affect performance, but would actually simplify the usage of FileStream, and also reduce or prevent any memory leaks from forgetting to delete raw pointers.
Do you want me to go ahead with changing it to use unique_ptr?

@halx99 I just noticed a bit of an issue.  What data do you prefer FileStream::seek() to return? Some implementations of seek return the current position, while others return 0 for success, -1 for error.  Which one is preferred?
I just found sections of code that try to use the return value, assuming it's size, so I need to fix them all, but need to know what seek should return before I do so.

I think, if there is tell API, should like fseek, otherwise, should like lseek

You can create a seperate pr to use unique_ptr, once this pr merged.

You can create a seperate pr to use unique_ptr, once this pr merged.

Will do! This PR should be complete unless you notice something that needs fixing.

looks good to me, merged

Excellent! New PR should be up soon with the unique_ptr changes.


Error while downloading data for some stocks

I'm getting an error while I was trying to download data for certain stocks during particular time frames.
import yfinance as yf

print(yf.__version__)

yf.download('PG', period='1m') # This works just fine

yf.download('PG', period='1y') # This throws error

Output:
0.2.26
[*********************100%***********************]  1 of 1 completed
[*********************100%***********************]  1 of 1 completed

1 Failed download:
['PG']: Exception("The following 'Dividends' events are out-of-range, did not expect with interval 1d: DatetimeIndex(['2022-07-21 00:00:00-04:00', '2022-10-20 00:00:00-04:00',\n               '2023-01-19 00:00:00-05:00', '2023-04-20 00:00:00-04:00',\n               '2023-07-20 00:00:00-04:00'],\n              dtype='datetime64[ns, America/New_York]', freq=None)")

What was wrong with the 'Bug Report' new issue option?


Check and update example configurations

Some of the examples don't work anymore, because I believe some mandatory options have been added to the leveldataoverride.lua which we do not set at the moment. That means, basically all examples using a leveldataoverride.lua possibly do not work anymore at the moment.

Fixed the shard example with https://github.com/dst-academy/docker-dontstarvetogether/pull/116


add event top, resize, commit and so on support in swarm

I found in docker version 1.10- and 1.10+, docker daemon supports event top which is missing in Swarm.
In docker 1.9.1: https://github.com/docker/docker/blob/v1.9.1/daemon/top_unix.go#L79
In docker 1.12.1: https://github.com/docker/docker/blob/v1.12.1/daemon/top_unix.go#L124
This PR adds top event in Swarm, and when getting an top event, I think nothing should be refreshed in containers, so just break for convenience.
In addition, I added some other events here to make swarm manager not to call engine node.
@dongluochen @nishanttotla
Signed-off-by: allencloud<EMAIL_ADDRESS>

LGTM

ping @nishanttotla @vieux
PTAL

I searched all the container event in docker 1.10.0- and 1.10.0+, and clarified that which events would not make swarm refresh the container, So a added in to the do nothing case in switch.
PR updated.
I think this will make swarm's performance much better when events number are large.
PTAL @dongluochen @nishanttotla

Thanks @dongluochen
I was wondering maybe it is better to list all the events in the switch...case...
WDYT?
@nishanttotla

PTAL @nishanttotla
I think this PR could improve the performance a lot for Swarm. Thanks.

thanks @nishanttotla

Test failures seem unrelated, there are some flaky tests. Should we merge this @dongluochen?


testing transactions?

maybe I missed it, but when testing, i run
client.create_invoice(price:1, currency: "USD")
and I get terminal output.
=> {"url"=>"https://test.bitpay.com/invoice?id=Ltqh6hvwJfhSfTpx1ryr6Q", "status"=>"new", "price"=>1, "currency"=>"USD", "invoiceTime"=>1535824778467, "expirationTime"=>1535825678467, "currentTime"=>1535824778484, "guid"=>"044553c7-b3cb-4d6c-906b-ad7c2b087184", "id"=>"Ltqh6hvwJfhSfTpx1ryr6Q", "lowFeeDetected"=>false, "amountPaid"=>0, "exceptionStatus"=>false, "transactions"=>[], "buyer"=>{}, "refundAddresses"=>[], "refundAddressRequestPending"=>false, "buyerProvidedInfo"=>{}, "paymentSubtotals"=>{"BTC"=>13900, "BCH"=>163700}, "paymentTotals"=>{"BTC"=>382100, "BCH"=>163900}, "exchangeRates"=>{"BTC"=>{"USD"=>7193.300000000001, "BCH"=>11.772609734542241}, "BCH"=>{"USD"=>611.01, "BTC"=>0.08515806946610527}}, "minerFees"=>{"BTC"=>{"satoshisPerByte"=>2504.556, "totalFee"=>368200}, "BCH"=>{"satoshisPerByte"=>1.019, "totalFee"=>200}}, "supportedTransactionCurrencies"=>{"BTC"=>{"enabled"=>true}, "BCH"=>{"enabled"=>true}}, "paymentCodes"=>{"BTC"=>{"BIP72b"=>"bitcoin:?r=https://test.bitpay.com/i/Ltqh6hvwJfhSfTpx1ryr6Q", "BIP73"=>"https://test.bitpay.com/i/Ltqh6hvwJfhSfTpx1ryr6Q"}, "BCH"=>{"BIP72b"=>"bitcoincash:?r=https://test.bitpay.com/i/Ltqh6hvwJfhSfTpx1ryr6Q", "BIP73"=>"https://test.bitpay.com/i/Ltqh6hvwJfhSfTpx1ryr6Q"}}, "token"=>"8HTkFUEHQkbiAErDBHqySmuevbzH2wVQVcxzvKP72hFRuXgs2XKpyvVytXmjEbHCdk"}
however when i use block.io or any other testnet supported wallet it tells me there's no valid address. and it's true: WHERE IS THE BITCOIN ADDRESSS? THIS IS BITCOIN. WHERE IS THE ADDRESS?  URLS ARE NOT BITCOIN ADDRESSES. Block.io, nor Blockchain.info, nor any other wallets seem to support this proprietary new way of accessing payment urls.
HOW DOES ONE HAVE A BITCOIN INVOICE WITHOUT A BITCOIN ADDRESS? WTF BITPAY. WHAT ARE MY USERS SUPPOSED TO COPY AND PASTE INTO THEIR BITCOIN WALLETS??? ART THOU RETARDED?
https://www.reddit.com/r/Bitcoin/comments/7muew2/bitpay_invoices_no_longer_show_an_addresswtf/dufgrq2/

BitPay requires BIP-70 (Payment Protocol) to pay an invoice.
You can find more information about paying a BitPay invoice here: https://bitpay.com/pay-with-bitcoin
Background info about BitPay & Payment Protocol you can find here: https://blog.bitpay.com/payment-protocol-results/


Random Quote Generator

added web project.

please merge my pull request and give me Hacktoberfest label.

Thanks for PR.


fixsupport topn-filter for non pipeline engine

Proposed changes
related be side pr: 32208
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run feut

run performance


date picker problem

I've got problems with the datepicker of the query ui (http://www.remino.me/rm/campaignOverview.php?s=1) is this a known issue or is it a problem in my programming?

The problem is that the compressed version of foundation.js that is included in the zip download has jQuery already.
You are including jQuery, jQuery UI then adds it's methods to $, and then by adding foundation.js jQuery is added again replacing the previous version with the $.datepicker().
You can fix this by removing your version of jQuery, or using the version of Foundation on GitHub that has all the js files broken apart, and use whatever version of jQuery you would like.
I'll open another issues to potentially have jQuery broken out in the compressed foundation.js to make this less confusing in the future.

Thanks a Lot Matt! You saved my day :-)
Bernd Rehm
<EMAIL_ADDRESS>Am 10.11.2011 um 22:22 schrieb Matt<EMAIL_ADDRESS>
The problem is that the compressed version of foundation.js that is included in the zip download has jQuery already.
You are including jQuery, jQuery UI then adds it's methods to $, and then by adding foundation.js jQuery is added again replacing the previous version with the $.datepicker().
You can fix this by removing your version of jQuery, or using the version of Foundation on GitHub that has all the js files broken apart, and use whatever version of jQuery you would like.
I'll open another issues to potentially have jQuery broken out in the compressed foundation.js to make this less confusing in the future.

Reply to this email directly or view it on GitHub:
https://github.com/zurb/foundation/issues/86#issuecomment-2701304

No problem :)


doc add comparison to eslint

That would be nice however it needs some digging. I am not aware of all the eslint rules.
I think we can mark as good first issue. It is more like comparing the 2 docs. No coding is needed.
Should we add the list to this doc page?

Should we add the list to this doc page?

I'd say so, cause it's part of the comparison


fix(esl-popup): wrong popup position when the popup is shown at the first time

Fixes:

wrong popup position when the popup is shown at the first time
IE fix 'ShadowRoot is undefined'
IE fix 'properties x and y are absent in DOMRect'

:tada: This PR is included in version 3.0.0-beta.16 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[4.0][Bug] Elfinder menu item is not working

Bug report
What I did
I installed a fresh version of Backpack via php artisan backpack:install --elfinder yes
What I expected to happen
File Manager menu item to work.
What happened
File Manager menu item is not working in the menu.
What I've already tried to fix it
I think the problem in the quotations here:

It works fine after removing the repeated quotations.
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 7.4.0 (cli) (built: Nov 27 2019 10:14:18) ( ZTS Visual C++ 2017 x64 )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
LARAVEL VERSION:
v7.0.8@d71ba61d51aec79a0a0f907991ec215dc24b09d4
BACKPACK VERSION:
4.0.52@574eb04050fbc8e073202fe0c38ed6bbb3718bfb

@mamprogr can you confirm you are using Windows ?

Yes, Windows and Wamp

Can you test my solution in #2532 if it fixes ?
If it does fix, please leave a comment in the PR thread so when @tabacitu sees it, it knows it had been tested atleast by two persons, and would make it easy for him to merge the change.
I would like to thank you very much for submiting this issues, the upgrade to Laravel 7 should have not been so broken, a lot of stuff changed in Laravel dependencies and not all are documented, so we only know about them when we get the errors .
For that bad experience we apologize! Hope next weeks will bring better news than this! :)
Wish you the best,
Pedro

I've just merged #2532 - which hopefully fixes this. Please let us know if after a composer update you get any more issues @mamprogr . And just like @pxpm said - thanks a lot. Very helpful.
Cheers!


Scalajs compilation error - not permitted because enclosing is not a subclass

Hi,
When trying to update magnolia to 1.1.4 in diffx I got the following error:
[info] compiling 9 Scala sources to /home/runner/work/diffx/diffx/core/target/js-3/test-classes ...
[error] -- Error: /home/runner/work/diffx/diffx/core/src/test/scala/com/softwaremill/diffx/test/DiffSemiautoTest.scala:42:49
[error] 42 |implicitvaldACoproduct: Diff[ACoproduct] = Diff.derived[ACoproduct]
[error]    |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^
[error]    |methodsealedTraitFromMirror in traitSealedTraitDerivation cannot be accessed as a member of (Derivation_this :
[error]    |  (Derivation_this² : (Derivation_this³ : com.softwaremill.diffx.Diff.type))
[error]    |) from class DiffSemiautoTest.
[error]    | Access to protected methodsealedTraitFromMirror not permitted because enclosing classDiffSemiautoTest in packagecom.softwaremill.diffx.test
[error]    | is not a subclass of traitSealedTraitDerivation in packagemagnolia1 where target is defined
[error]    |
[error]    |where:    Derivation_this  is a value in the initializer of valuedACoproduct
[error]    |          Derivation_this² is a value in the initializer of valuedACoproduct
[error]    |          Derivation_this³ is a value in the initializer of valuedACoproduct
[error]    | This location contains code that was inlined from magnolia.scala:73
[error]    | This location contains code that was inlined from magnolia.scala:77
[error]    | This location contains code that was inlined from magnolia.scala:80

https://github.com/softwaremill/diffx/runs/7254960766?check_suite_focus=true
Any idea what could be the cause?

After updating scalajs to the latest version the issue disappeared.


Improve the text for better clarity

This PR improves the text of the onboarding page, to clarify several things that were not fully explained, generating confusion or anxiety in users.

I made some minor changes in order to solve some visual issues in the page @alranel. It should be ready to merge.


Revert "Peertableview alternating row colors"

Reverts bitcoin-core/gui#298
I think this has made the table more cluttered now, and perhaps this pull request could be re-merged in the future once it's done with making the changes optional.

I agree.

... making the changes optional.

Done in #307.

My preference would be for #307. Some people were for this change, some against. #307 is the democratic option for appeasing both sides.

I am concept NACK this, without a plan for 307, which has now been closed

I actually quite like the stripes now :) acquired taste I guess....!


Change fairy ring destinations to be same as in in-game list

Using fairy rings displays 2 different location names when setting and comparing codes from the map and the menu

have a screen shot?

Is this an issue of Jagex naming the location one thing within their fairy ring interface and then rune lite naming it another? A lack of consistency?

Yeah that's what i was asking about, seems inconsistent

Don't think the location names in the fairy ring interface are supposed to match the in-game ones

This is very much working as intended.

If we're going to rename it in one place why not rename it in both? We should either use the Jagex names or overwrite them, having two different names for each destination is kinda confusing

RuneLite only adds the search filter to fairy rings. Inconsistent naming would have to be corrected by Jagex.

This is working as intended, we're not interested in changing it.


Regarding t-sne visualization in Figure 4.

Hi, Thanks for sharing great work.
I would like to ask the embedding used for the t-sne algorithm.
As I understand, the final output of the relation representation (rel_rep_norm) has 4096 dim.
Did you use the relation rep directly to visualize the t-sne ?
or did you use any pre-processing or other representations?
Best, Kanghoon Yoon

I use PCA for dimensionality reduction and then t-sne for visualization

降低到2维，然后使用了t-sne可视化

降低到2维，然后使用了t-sne可视化

谢谢！:)

Thanks for replying ,I will close my issue!


NUMA aware placement for vCenter

Description
This issue is to implement placement constraints on NUMA nodes. A VM can be pinned on a node based on:

PCI affinity
Memory affinity
Manual node assigment

Use case
Improve performance of VM by making memory and/or I/O access to the same NUMA node.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

ESX takes care of the NUMA placement. We will only allow the definition of the virtual topology. Sunstone needs to deprecate the core per sockets dialog in favor of the NUMA one, with the following characteristics for vCenter:

Fix pin policy to 1
Calculate automatically the number of sockets, similar as what we do now in the General tab
Remove huge pages and memory access
Fix threads to 1

@tinova PR to be approved:

code
docs
Test: Pending


[INFO] building with MacPorts

I managed to run this example by installing dependencies using MacPorts instead of pixi,. Here is what I had to do:
Install deps:
sudo port install cmake opencv4 eigen3

When running cmake:
export CMAKE_PREFIX_PATH=/opt/local/libexec/opencv4/cmake/
cmake -DCMAKE_CXX_STANDARD_INCLUDE_DIRECTORIES=/opt/local/include ..

let's add this to the readme then!


FEAT: Add Question To Take a Picture (Items In Hand)

@frederickbaier its looks good to me if it is working on local, do you still want me to test run on local?

@preetvadaliya No, you don't need to. It is working for me.


Use Organization CRD from organization-operator

As the organization-operator repo is now the canonical source of the Organization CRD, this PR changes the CRD docs to use the new source.

FYI @fiunchinho


Add Support for Loading CSV datasets

Description
PR stemming from this discussion: https://github.com/openvinotoolkit/anomalib/discussions/1042
In summary, to add csv file loading functionality to anomalib on top of loading from folders for custom datasets.
The CSV dataset format:
    |---|-------|-----------|---------------|---------------------------------------|-------------|
    |   | split |  label*   | image_path*   | mask_path                             | label_index |
    |---|-------|-----------|---------------|---------------------------------------|-------------|
    | 0 |  test |  abnormal |  filename.png | ground_truth/defect/filename_mask.png | 1           |
    |---|-------|-----------|---------------|---------------------------------------|-------------|

Single csv file containing following columns:

Required columns*:

image_path: Path to image file (to join with root from config.dataset.root)
label: normal, abnormal or normal_test

Optional columns:

split: If split column not defined in CSV, generate train and test splits the based on labels (same as how folder dataset handles this: normal samples = train, all abnormal and normal_test samples = test). Need to check that train split should only have normal. if abnormal found drop and ignore.
label_index: function of label where, normal = 0 and abnormal = 1
mask_path

Defined in single new csv_file config key - path to csv file

Code changes:

Add CSVDataset and CSV DataModule
Add _prepare_filemeta_from_csv function in path.py using pandas to read CSV contents, ensure file required columns defined in csv file are correctly defined, have the correct extensions.
Handling of required columns for DataModule _setup in make_csv_dataset
Added support for test csv file during inferencing too - csv loading added in data/utils/image.py and lightning_inference.py

Also addresses #1072
Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which refactors the code base)
[x]  New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist

[x] My code follows the pre-commit style and check guidelines of this project.
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing tests pass locally with my changes
[ ] I have added a summary of my changes to the CHANGELOG (not for minor changes, docs and tests).

@samet-akcay Disappointed to see the end of the PR - after being ignored for 2 years. We were avid users of anomalib and we're hoping to be recognised as contributors to the library. Unfortunately, this repo is not very friendly to contributors.


Add an Option for Use Without Rails

Font Fix
Fixed a bug with the font includes in this branch. There was some ruby specific code that wasn't fully migrated over in a pre-existing mixin. Now when this version of SassyPam is included and a user specifies the location of the font folder it will correctly resolve the fonts.
Renamed File
This isn't just for bower anymore, so I made it more generic.
Also, after this, can we delete this branch?
CC: @eprislac

Agreed. Having to point at a branch is definitely sub-optimal.
The branch exists, though, because at the time, the sassypam gem was utilized by several applications that had not yet been migrated to Rails 4. It was in upgrading to Rails 4 that we started getting font bugs in the app. As we needed to make changes within sassypam to get the fonts to render correctly, and there were other apps still able to use the older code, we branched, in order to fix the fonts for rails 4 apps while being able to continue to use the older code in apps that weren’t up for upgrade. As long as all the apps using sassypam still render correctly with the new code in this PR, I see no reason not to merge it and point SMS back at master branch.
On Mar 5, 2016, at 11:58 AM, Zachary Fantauzzi <notifications<EMAIL_ADDRESS>wrote:
I'd like us to not have to point our (front-end) package managers at a separate branch in order to use SassyPam. While there is probably a better way to do this, for now it is the path of least resistance when needing it for PoCs.
Why Does this Branch Exist
Don spiked a version of this repo that would not require rails in order to use SassyPam. This is useful for front-end engineers who want to use this in a new project and/or create a PoC without the need for a Rails environment.
Usage
Users would include the 'sassypam_no_rails.sass' version of sassypam and then specify a font path for where the fonts are located. The font-path is located in the 'fonts/_fonts_norails.scss' file.
Font Fix
I also fixed a bug with the font includes in this branch. There was some ruby specific code that wasn't fully migrated over in a pre-existing mixin. Now when this version of SassyPam is included and a user specifies the location of the font folder it will correctly resolve the fonts.
CC: @eprislachttps://github.com/eprislac

You can view, comment on, or merge this pull request online at:
https://github.com/CINBCUniversal/sassypam/pull/6
Commit Summary

fixed: path was not working correctly when pointing at font directory
modified: added .idea to .gitignore
renamed: this is really usable with any non-rails package manager, so I renamed it to be generic

File Changes

M .gitignorehttps://github.com/CINBCUniversal/sassypam/pull/6/files#diff-0 (1)
M vendor/assets/stylesheets/fonts/_fonts_norails.scsshttps://github.com/CINBCUniversal/sassypam/pull/6/files#diff-1 (38)
R vendor/assets/stylesheets/sassypam_no_rails.sasshttps://github.com/CINBCUniversal/sassypam/pull/6/files#diff-2 (0)

Patch Links:

https://github.com/CINBCUniversal/sassypam/pull/6.patch
https://github.com/CINBCUniversal/sassypam/pull/6.diff

—
Reply to this email directly or view it on GitHubhttps://github.com/CINBCUniversal/sassypam/pull/6.


allow encoding (base64?)

It would be great if the users had the ability to bypass normal filters that check for specific patterns in the url, like "twitter.com", and this can be done in many ways
base64
say that after https://crossorigin.me/ we had something like b64:aHR0cHM6Ly90d2l0dGVyLmNvbQ==, that will evaluate to https://twitter.com, and the user can easily get it with btoa('https://twitter.com')
rot13
add a rot13 function for the users to call in the console (rather than explicitly in the page), so they can just rotate the characters and put the output of rot13('twitter.com:443') in https://crossorigin.me/r13:
polymorphic function
that changes every day or so, this way the url can't be checked easily, and you'd provide a function like rot13 that the user can look for in the JS code or by enumerating global variables

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38029363-allow-encoding-base64?utm_campaign=plugin&utm_content=tracker%2F12536595&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F12536595&utm_medium=issues&utm_source=github).

Can you describe a specific use case for these?

The idea behind crossorigin.me is to get past the "cross-origin" bottleneck. Why not go all the way, and make it so that networks that disallow patterns like imgur to be in the requested url can still let it through?

This seems rather out of scope for the purpose of the proxy, and would likely get me in trouble with schools (which is problematic since crossorigin.me is used in an AP CS Principles curriculum).

If redirectatob were server-based..


cmd/cue: yaml import fails on string containing zero code point

commit 456108de1c31cd5c61045ec20832c3723f2ae9b2
The following YAML fails on import:
b: "\0"

The error message is:
b: invalid string: invalid syntax:
    ./y.yaml:1:5

The syntax appears correct, and 0 is a valid Unicode code point, so this should be OK.

This issue has been migrated to https://github.com/cue-lang/cue/issues/514.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Fix: Cannot read property 'type' of undefined

Patch to solve this error :
Uncaught TypeError: Cannot read property 'type' of undefined
at BootstrapTable.js:228
at forEachSingleChild (ReactChildren.js:49)
at traverseAllChildrenImpl (traverseAllChildren.js:75)
at traverseAllChildrenImpl (traverseAllChildren.js:91)
at traverseAllChildren (traverseAllChildren.js:170)
at Object.forEachChildren [as forEach] (ReactChildren.js:69)
at BootstrapTable.initTable (BootstrapTable.js:221)
at BootstrapTable.initTable (createPrototypeProxy.js:44)
at BootstrapTable.componentWillReceiveProps (BootstrapTable.js:419)
at BootstrapTable.componentWillReceiveProps (createPrototypeProxy.js:44)

Hi, I have the same problem with the 4.0.6, this patch should be sufficient

Fixed on v4.1.0, thanks your contributions


docs: setup structure, installation

I made some changes to the installation files to enhance the formatting for a cleaner look. Additionally, I replaced the logo with a transparent version to eliminate the background and addressed some issues identified in Korel's PR- https://github.com/dentproject/docs.dent.dev/pull/6.

Considering the revised changes in https://github.com/dentproject/docs.dent.dev/pull/6, from https://github.com/dentproject/docs.dent.dev/pull/6/commits/24ed65d0a8178d3851b9ac4559233af97ba583e8 to https://github.com/dentproject/docs.dent.dev/pull/6/commits/c868b1dac39f766beec771775854e9b014813952,  I'm closing this PR. I'll be working on a separate PR to incorporate all my changes, focusing specifically on LocalMachine.md and index.md. These are the files I primarily worked on along with addressing issues in other files, along with some of the images that Korel missed from my Medium article.
Please ensure that the files I've worked on are properly addressed so that I get credit for my contributions. Alternatively, if feasible, you could cherry-pick the changes from this PR. However, I believe a separate PR from me would streamline the process for you. @taraschornyiplv


How to use activation function "PReLu"

I have read the information about "chainer.functions.prelu " but still have no idea how to use it. Could anyone give an example as below? Thanks~
`from keras.layers.advanced_activations import LeakyReLU, PReLU
...
model.add(Dense(512, 123, activation='linear'))
model.add(PReLU((123,)))

Hi,
Is it the case that you want to use PReLU similar to how it's used in Keras?
Unless you explicitly want to keep track of the weights of PReLU on your own, you might want to consider using http://docs.chainer.org/en/stable/reference/generated/chainer.links.PReLU.html which is a Link, a wrapper of the PReLU function that you mentioned.
The Link needs to be instantiated and added to the model. It will initializes the weights and "optimize them for you".

It works! Thank you for your information.