fix css selector

This PR fixes #15937
turns out the issue is caused by bad css selector in welcome page, it meant to apply the style to the h1.. and p to the welcome page, but it is not written correctly, as a result, the color is applied globally.
fix:
fix the css selector, I tested and it only needs p, h3, and h4.
no impact to the welcome page:
Before:

After:

Migration wizard:
Before:

After:

Pull Request Test Coverage Report for Build 984325755

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 42.929%

Totals

Change from base Build 983867689:
0.002%

Covered Lines:
26353

Relevant Lines:
55743

💛  - Coveralls


unable to use wolfram notebook assistent and in all tryouts it did not work

Describe the issue in detail here. Attach any relevant screenshots or files. The section below was automatically generated. Remove any information that you do not wish to include in the report.
https://github.com/WolframResearch/Chatbook/blob/92802b1ef8f559233ce0b012c36984092f64df5b/Source/Chatbook/PromptGenerators/VectorDatabases.wl#L635-L642

Debug Data

Property
Value

Name
"Wolfram/Chatbook"

Version
"2.0.1"

ReleaseID
"92802b1ef8f559233ce0b012c36984092f64df5b"

EvaluationEnvironment
"Session"

FrontEndVersion
"Desktop: 14.1 for Microsoft Windows (64-bit) (July 16, 2024)"

KernelVersion
"14.1.0 for Microsoft Windows (64-bit) (July 16, 2024)"

SystemID
"Windows-x86-64"

Notebooks
True

DynamicEvaluation
False

SynchronousEvaluation
False

TaskEvaluation
False

Settings

Property
Value

InheritanceTest
True

SetCellDingbat
False

TabbedOutput
False

WorkspaceChat
True

AllowSelectionContext
True

AppName
"NotebookAssistance"

LLMEvaluator
"NotebookAssistant"

MaxContextTokens
32768

MaxToolResponses
3

Model
<|"Service" -> "LLMKit", "Name" -> Automatic|>

PromptGenerators
{"RelatedDocumentation"}

ServiceCaller
"NotebookAssistance"

Tools
{"NotebookEditor"}

ToolSelectionType
<|"DocumentationLookup" -> None, "DocumentationSearcher" -> None|>

ToolOptions
<|"WolframLanguageEvaluator" -> <|"AppendURIPrompt" -> True, "Method" -> "Session"|>|>

AutoGenerateTitle
True

AutoSaveConversations
True

ConversationUUID
"55ebcd6f-2fe2-4592-9693-d35bd6e81d0a"

StyleSheetVersion
"<IP_ADDRESS>.3941177587"

Failure Data
<|
  "Evaluation" :> Wolfram`Chatbook`PromptGenerators`VectorDatabases`Private`getAndCacheEmbeddings[{"User: How many people live in the Netherlands", "User: How many people live in the Netherlands"}],
  "Information" -> "PackedArray@@Source/Chatbook/PromptGenerators/VectorDatabases.wl:635,19-642,10",
  "ConfirmationType" -> "ConfirmBy",
  "Expression" :> Join[$Failed][[{2, 1}]],
  "Function" -> Developer`PackedArrayQ,
  "Stack" :> Wolfram`Chatbook`Common`Private`$stack$14782,
  "Failure" -> Failure["ConfirmationFailed", <|"MessageTemplate" -> "PackedArray@@Source/Chatbook/PromptGenerators/VectorDatabases.wl:635,19-642,10", "MessageParameters" -> {}, "ConfirmationType" -> "ConfirmBy", "Expression" :> Join[$Failed][[{2, 1}]], "Information" -> "PackedArray@@Source/Chatbook/PromptGenerators/VectorDatabases.wl:635,19-642,10", "Function" -> Developer`PackedArrayQ|>],
  "Arguments" -> {}
|>

Stack Data
trimURL
throwFailure
catchTop
formatGeneratedPrompt
catchTopAs
withChatState

After paying and following the setup instructions I am still unable to use wolfram notebook assistant and in all tryouts it did not work

Could you try the follow set of commands to see if it helps?
ResourceRemove[ResourceObject["all-MiniLM-L6-v2"]]

Quit

ResourceUpdate["all-MiniLM-L6-v2"]

Quit

NetModel["all-MiniLM-L6-v2"]


Update WebGPU API to draft 2024-11-22

Needed for https://github.com/gfx-rs/wgpu/issues/6614

Just pushed the same commit again, and now it works. Definitely a flaky test.


line numbers are not hidden when using statuscolumn

Alpha-nvim shows line numbers when setting:
statuscolumn = "%s%{v:relnum?v:relnum:v:lnum}%C"
i expect line numbers to be hidden

The issue is that your settings for status column overwrite that functionality.  It always sets the line numbers.  You need to first do a check to see if numbers should be shown.  Something like:
%s%{&nu?(&rnu && v:relnum?v:relnum:v:lnum):''}%C


Typescript not setup correctly in Build a React App

File: runtime/tutorials/how_to_with_npm/react.md
Running the example with a fresh VSCode installation and in a new folder:
[zweieuro@thewallet /tmp]$ deno run -A npm:create-vite@latest --template react-ts
✔ Project name: … deno_test

Scaffolding project in /tmp/deno_test...

Done. Now run:

  cd deno_test
  deno install
  deno run dev

[zweieuro@thewallet /tmp]$ cd deno_test
[zweieuro@thewallet /tmp/deno_test]$ deno install

deno task dev runs fine, but deno is disabled.
Running deno: enable in VSCode does shows the following:

React UMD global not preset
svg paths not recognized properly (in this case vite.svg isn't even in the project, its from vite directly)
svg paths to files not recognized correctly

There is no deno.json file
Should these things be setup correctly?

Ran into similar problems myself, following along with the runtime/tutorials/how_to_with_npm/react.md
They actually added an easier way to do this in the latest release > #26896
You can also see this on the blog
https://deno.com/blog/v2.1#deno-init--npm-vite
However this template is still just the basic npm version, does not create a deno.json and throws a bunch of errors like you had when enabling the extension, requiring a lot of fiddling as well as just generally looking messy with all the unnecessary config files
The command I had the most joy with is this, using vite-extra templates
 deno init --npm vite-extra

Then select deno-react > TypeScript
Should give you what you need, and actually includes a deno.json 😅
Not sure of the reasoning behind the current tutorial, since it includes a lot of the extra tools and configs that defeat the purpose of actually using deno over npm 🤷
Hope this helps anyway, let me know if you get it working

I've updated the post to mention that the create-vite app will need you to disable the deno extension, and I've created a react-vite template that has a deno.json which can be used in place of create-vite and written up a tutorial for that too - PR here: https://github.com/denoland/docs/pull/1195
Sadly we've been told that create-vite-extra will not be supported for much longer so we're not recommending folks use that right now.


Add more prometheus samples

What type of PR is this?
Add more samples of prometheus OBI to show some advanced usages.

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

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

/lgtm


Fix example Grafana dashboard's "Last archived WAL" panel

Hi there!
This panel in the example dashboard was reporting the wrong value because there was a negative that wasn't being negated. Here's the before image:

And here's after:

Comparison:

Let me know if there's anything else you want me to test!

@perfectra1n The query seems to me has problem, but I do have another thought of fixing, please see analysis below
The
time() - timestamp( cnpg_pg_stat_archiver_seconds_since_last_archival{xxx})
is collecting the time escaped from the time metics collected to now, in max internal is 30 seconds.
and cnpg_pg_stat_archiver_seconds_since_last_archival{xxx}  is the collecting the time escaped from last wal archive to the time metics collected.
so the total time from wal archive to now should be
total time from wal archive to now  = time (from the time metics collected to now). + time (from last wal archive to the time metics collected)
The query should be
time() - timestamp( cnpg_pg_stat_archiver_seconds_since_last_archival{xxx}) + cnpg_pg_stat_archiver_seconds_since_last_archival{xxx}

see my test in prometus

Hi there! Yes, I believe that appropriately fixes the query, so the full query after importing the file here turns out to be the following:
max((1 - cnpg_pg_replication_in_recovery{namespace=~"$namespace",pod=~"$instances"}) * (time() - timestamp(cnpg_pg_stat_archiver_seconds_since_last_archival{namespace=~"$namespace",pod=~"$instances"}) +
cnpg_pg_stat_archiver_seconds_since_last_archival{namespace=~"$namespace",pod=~"$instances"}))

Which then results in the following:

So I think those changes did the trick @litaocdl, the PromQL was giving me a headache trying to comprehend, thanks for digging into it.

sorry @perfectra1n I have to force push, granafa conflict is hard to resolve, there is another granafa change merged in main.

/ok-to-merge


table / column editors missing "unsigned" checkbox for ints

System information:

MacOS 10.14.6
DBeaver <IP_ADDRESS>002151353
JDBC / MariaDB extension

Connection specification:

MariaDB
MariaDB
Do you use tunnels or proxies (SSH, SOCKS, etc)? Yes

Describe the problem you're observing:
When creating / editing INT fields, the editors do not display "unsigned" checkbox to be able to set/unset an int as unsigned.
Steps to reproduce, if exist:
go into any of the editors

looks like "unsigned" is supported in a drop-down list as a specific "data type"; a little clunky, but workable.


Difference between submit actionCreator and submit bound actionCreator?

Is there a reason for the difference in behavior between using submit('myForm') and using the submit() bound action creator that's provided as a prop tomyForm?
I've got a page that has multiple forms that may or may not be present, and I'd like all of them to submit/fail simultaneously. The pattern that pops into my head is to use something like the following:
Promise.all([submit('myForm1'), submit('myForm2'), submit('myForm3')])

Where my expectation would be that the normal actionCreator has the same API as the bound actionCreator and returns a promise, which isn't the case. Is there a reason for this difference? It's confusing.
Is there a pattern that's better suited to this use case? If so, I'd be happy to write it up as an FAQ doc.

I ended up finding a pattern to get around this using a higher-order component:
import { getFormNames, hasSubmitSucceeded } from 'redux-form';
import { connect } from 'react-redux';

/*
 * This component is magic.
 * Not really.
 * But what it does is gets the active forms using getFormNames, then gets whether
 * they've had a successful submission using hasSubmitSucceeded. By using an
 * every clause, we're able to get a single boolean (allSubmitted) which is then
 * passed to the child component.
 */

const mapStateToProps = state => {
  const formNames = getFormNames()(state);
  return {
    // If there are no formNames because they haven't been rendered yet, we want it to return false.
    // Otherwise, we want it to return the submission status of each one of them.
    allSubmitted: formNames.length > 0 && formNames.every(form => hasSubmitSucceeded(form)(state)),
  };
};
export default component => connect(mapStateToProps)(component);

Is this worth documenting somewhere?

And I ended up reworking that as a selector, because the HOC was a bit verbose.

Because this issue saw almost no activity for a few months, I'm closing it.


Drop Python 2.7 support

Is there still people using Python 2.7 and this library?
Now, I only use Python 3 so we should consider dropping Python 2.7 support.
Any comment?

No vote for me.

Hi,
2.7 is still required if you want, for instance, to integrate with other existing projects supporting that version, e.g.,  https://github.com/mhallsmoore/qstrader/pull/207
Kind regards.

My opinion is that QSTrader should drop Python 2.7 support.
There is many things to do in this project without having to deal with technical debt.
On my side I'm more and more involved in Julia community.
It's a great language with very good performances.

I agree, will suggest in Qstrader thread.

I've been working with a large company that has very large Python projects that haven't even looked at Python3, so if you want other people to be able to use the library, Python2 is required. Also, it can depend of the Python that's with the Operating System that you are running on: there's lots of use of Ubuntu 14 in AWS projects, so Python2 is still esssential if the library is to be for use by other people. In corporate envrionments, I've seen people use Ubuntu 12 in production until the last day the LTS release was supported!
I think Wes is planning to drop support for Python2 next year in pandas, but even then, you can expect people to use the Python2 versions for a year or two after the new Python3-only versions come out. I have 2.7+3.4+3.5 and there's not a chance I'll be able to drop Python2 this year. C'est la vie.

Closing this. Support for 2.7 has been dropped


chore: remove patch-package for react-native-device-info

Description
This PR removes the patch-package for react-native-device-info that was put in place after it was flagged by Apple for a missing privacy manifest.
The issue was reportedly resolved by react-native-device-info, so this PR removes the patch-package to see if Apple will pass it.
Changelog updates
Changelog updates
Dev changes

Remove patch-package for react-native-device-info - iskounen

This PR contains the following changes:

Dev changes (Remove patch-package for react-native-device-info - iskounen - iskounen)

  Generated by :no_entry_sign: dangerJS against 0a6d267e401d1919092e7ac6eb7793362b68db29


Documentation Unclear

As noted in https://github.com/jasonslyvia/react-lazyload/issues/56 this currently only supports lazy loading on the vertical / y-axis, I think the documentation should reflect that since I just wasted a bunch of time in frustration with a horizontal container.

This project seems abandoned =/


Try adding zlib

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

perhaps libzlib is redundant?

Yup, that's the case, because zlib depends on it already (and will add a run-export to that effect).


Customize 500 error page

Sure -- I'll make a mockup that you can copy, if that works. Stand by for
great exploding image...
On Wed, Jul 12, 2023 at 11:30 AM Bruce Crevensten @.***>
wrote:

@carolynrosner https://github.com/carolynrosner can you make something
fun for this? It's a bog-standard 500-error-page (not a 404 not found) that
indicates that the code blew up.
—
Reply to this email directly, view it on GitHub
https://github.com/ua-snap/data-api/issues/76#issuecomment-1633018874,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHC4BL2JYGBQPXVK5H7XADXP3ULRANCNFSM5NCBJMXA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Carolyn Rosner
Graphic Designer
Scenarios Network for Alaska + Arctic Planning http://www.snap.uaf.edu/
University of Alaska Fairbanks
760-920-3721

Here's an image -- does it need anything else? It's 2000px wide


Tooltip flickers on icon hover

Overview of the problem
Oruga version: [0.5.10]
Vuejs version: [3.2.47]
OS/Browser: all
Description
I created an icon with a tooltip like this:
<o-tooltip           label="some text"           position="left"           appendToBody           multiline>           <o-icon icon="circle-info" size="medium" class="mx-1" /> </o-tooltip>
Since I added "appendToBody" the tooltip flickers when I hover over the icon.

Steps to reproduce

Hover over the icon

Expected behavior
The tooltip stays as long as the mouse hovers over the icon
Actual behavior
The tooltip flickers

Problem was caused by a css class of a parent


Required elf2tab version

Are there any requirements on which elf2tab version must be used in libtock-c?
I must have built something with libtock-rs first, because I have version 0.4.0 installed as specified in the libtock-rs Makefile
The test in the configuration will succeed and not pull the current version:
https://github.com/tock/libtock-c/blob/53af0d2660f9d09338746df1896aa271c8b602b3/Configuration.mk#L75
And it seems like shell.nix will use version 0.3.0

And it seems like shell.nix will use version 0.3.0

That is correct. I cannot make any statements regarding the minimum required version, however for RISC-V I've found that v0.6.0 will work. Please see my related PR regarding a Cargo.lock update. As soon as that's merged, I'll make a PR to update shell.nix to the current release.
Pinging @bradjc as this is likely an action item for him.

Thanks for the feedback @lschuermann. I also had some problems with elf2tab 0.4.0 and RISC-V.
Not sure if https://github.com/tock/libtock-c/pull/109 requires a specific elf2tab version, but I had trouble getting the headers to the correct position with elf2tab v0.4.0. Maybe @alistair23  has some insight on the requirements here.

I just use the latest version (0.6.0) and don't have any issues.

@towoe To make sure that the app always starts at a specific offset from the TBF headers, as you suspected, elf2tab allows specifying a protected region size. In the nix shell, it failed for me as well, although that is because the command line option was not recognized in version 0.3.0
https://github.com/tock/libtock-c/blob/53af0d2660f9d09338746df1896aa271c8b602b3/shell.nix#L35-L37
I'm not quite sure why it wouldn't work with 0.4.0 for you since the protected region size is already supported there, but I'd just suggest manually building elf2tab until the Cargo.lock is updated and I've updated shell.nix.

Yes the --protected-region-size argument helped. This is what is used in libtock-rs.
Or using elf2tab v0.6.0 could also resolve the issue with the header, that's why I wanted to know what the required version is.
I guess either one should be used and documented here as well because the default settings might not produce the correct output.

Okay, the documentation actually says something about the version: up-to-date.

Okay, the documentation actually says something about the version: up-to-date.

Great. I'd actually prefer to keep it that way. Introducing yet another number to bump would probably cause that to get outdated quickly. Great to hear that v0.6.0 solves the issues for you.

I think it should be documented what version is required. Maybe that should be done centrally so bumping dependencies is clearly defined.
Especially with a check and installation by the build system the user will not suspect that an incompatible version is installed.
And with a valid looking generated output it requires deeper knowledge to find the problem.

I'm not sure there's a clean way to mark this in a single central place -- with libtock-rs now being up to date, hopefully this won't be an issue for folks moving forward, so I'm going to close this out for now.


Incorrect treatment of 'tel'-links

I realize that this is probably the wrong repository to report this issue in, but I'm a bit lost on where to go to actually solve it.
Basically the problem I have is that a link on the form [+15553485](tel:+15553485) generates the following html: +15553485 instead of the expected +15553485.

Hi @hedvigoscar. As you suspected, this is a matter for remark itself. If you do open an issue in that repo, I'd urge you to bring some links demonstrating that this is indeed what a Markdown parser is expected to do.

See protocols in hast-util-sanitize!


Question about the paper: how is Unlearn Success computed exactly?

The above definition is a bit confusing - do you do an exact token-by-token match to see if the generated answer matches the true answer?
If not, can you elaborate on how the metric is computed?
If yes, won't this be very sensitive to paraphrases?

Thank you for your attention to our work!
The metric we use, as adopted in previous works such as knowledge unlearning [1] and editing [2], measures performance by comparing the generated answer to the true answer on a token-by-token basis, rather than requiring an exact match. For instance, if the answer_ids are [1, 2, 3, 4] and the prediction_ids are [2, 2, 3, 4], this metric would yield a score of 75%.
We acknowledge that there are limitations in our current metrics for evaluating generation. Therefore, we are exploring alternative metrics, such as evaluations using GPT-4.
[1] Machine Unlearning of Pre-trained Large Language Models
[2] Editing large language models: Problems, methods, and opportunities


Add option to remove/disable all banned accounts

Add to the Mass Switch.

Closing as a duplicate of #230 which is better defined in its task.


Add GuiKeepModule, Fix #738

Players are now able to craft their items even if the workbench is broken.

This doesn't take into account shift-clicking.

Yeah, I'll fix that.

tested and works fine

Any chance you could sqaush these into a single commit?

Done ;)

I've tested in Minecraft Vanilla and while you are sneaking but you haven't anything in your hand you can still access to the crafting table.
If I don't do that players can access to the workbench but If someone break it, the GUI disappear.

That still does not explain why you are checking that, when I read it is says that, if a player is not sneaking and has nothing in their hand, open the inventory. Have you checked your code?

That's not "and", that's "or".
If the player is sneaking > Nothing in his hand ? Open the inventory.
If not > Always open the inventory.

I meant to say or. But that does not do that you are saying:
if player is not crouching > open inventory
if player has nothing in hand > open inventory
if player is sneaking > don't open
if player has item in hand > don't open

@CaptainElliott He's saying that you always open the crafting table when not sneaking, and when you have nothing in your hand, you open it regardless. His logic in the code is correct because he's saying open the inventory if the player is not sneaking, or if the player has nothing in their hand.

@iEli2tyree011 ohh I didn't realize that opening a inventory with an empty hand while shifting still opened the inventory

This seems good to merge, any problems with it? @twizmwazin

This is awesome, great work @maestro34!

Thank you, @ryanw-se !

thanks, merged


Implementation of travelling salesman problem added

Please star this repository to show your support, in the meantime I am reviewing your code.

Excellent work @gayatri517 Thanks a lot for making this PR.


feat: add publish workflow

:pencil: Description

:link: Related Issues

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Figure out a neater way to compose functions (postcss)

Loaders like postcss-loader define a part of their configuration through functions. You might have
postcss: function () {
  return [precss, autoprefixer];
}

The problem is that it's not possible to split this up neatly yet. Ideally you should be able to have
postcss: function () {
  return [precss];
}

and
postcss: function () {
  return [autoprefixer];
}

The question is, how to compose this through webpack-merge?

How about special-casing the merging for a top-level postcss property by calling the functions and appending the results - any danger from that?
I've been looking at this for nwb too, but there I can just have a default list there and tell users to pass in their own list when customising, then append them and return that from the postcss function.
From the last time I looked at this, am I remembering correctly that the position of autoprefixer is also significant? If you're already special-casing, it would be cool to be able to warn the user if their config looks like it will problematic.

How about special-casing the merging for a top-level postcss property by calling the functions and appending the results - any danger from that?

That feels like a merge strategy. So we would get something like
merge.strategy({postcss: function(a, b) {
  return merge(a(), b());
}});

From the last time I looked at this, am I remembering correctly that the position of autoprefixer is significant? If you're already special-casing, it would be cool to be able to warn the user if their config looks like it will problematic.

I don't know. Maybe this is one of those things that could be handled within a postcss specific merge strategy?
I've been discussing an alternative solution at https://github.com/postcss/postcss-loader/issues/69 . If we made it so that postcss-loader supported arrays and composition, that would make the problem disappear as we append by default. Then you would get exactly the result I described above as you would end up with
postcss: [
  function () {
    return [precss];
  },
  function () {
    return [autoprefixer];
  }
]

after merge. postcss-loader could pick this up, apply and merge to
postcss: function () {
  return [precss, autoprefixer];
}

That's easy code to write. postcss-loader supports also returning objects, but that can be dealt with separately. The only worrying case is the mixed one (arrays and objects), but in that case an error could be thrown and that could be disallowed entirely.
I guess the question is, what's the right place to solve this. Perhaps allowing a function based strategy is a good idea even if we end up solving it at the loader level.

I'm back look at this for nwb - do you know why all the postcss-loader examples use the function config form?
It looks like it accepts Arrays or Objects directly and none of the examples make use of the this value the loader sets as context for the call, or as an argument.
What can you actually do with whatever this is inside a loader? :)

@insin Good question. It might be worth commenting at https://github.com/postcss/postcss-loader/issues/69 . I've been a bit busy with work lately so I haven't had a lot of cycles for this.

I'm closing this as postcss-loader supports array mode already. It's a little puzzling though that all the examples use the function form, though.
There's not much we can do with functions. We could do something silly like write a function that calls the merged functions in succession and concatenates the result, but that would be awfully specific.


Imx9 lpspi fixes

Summary
This PR corrects the 9-16 bit transfers on IMX9 LPSPI, where buffer lengths were handled wrong. The driver was originally tested only on 8-bit transfers.
Additionally, this syncs the driver with TII branch by adding a small optimization for cache invalidation.
Impact
Impacts only imx9 platform and lpspi when using >8 bit transfers
Testing
Tested on custom imx93 board, connected to adis16470 IMU via SPI, using 16-bit transfers.

[Experimental Bot, please feedback here]
The PR description is mostly okay, but could be improved for clarity and completeness against the NuttX requirements. Here's a breakdown:
Strengths:

Summary: Clearly states the "why" (bug fix, syncing with TII branch) and "what" (9-16 bit transfer fix, cache invalidation optimization).

Areas for Improvement:

Summary:

Functional part: Be more specific than just "driver." Which file(s) were modified?
How:  Briefly elaborate on HOW the buffer length handling was wrong and how it's now fixed.
Issues/PRs:  Are there any related issues this PR addresses? If so, link them.

Impact:

User impact:  While the impact is limited, will users see any functional changes (e.g., improved performance)?
Build impact:  Unlikely, but state "NO" explicitly for completeness.
Hardware: Specify which imx9 board(s) were used for testing.
Documentation: Does the driver documentation need updating to reflect the fix?
Security:  Unlikely, but state "NO" explicitly.
Compatibility:  Unlikely, but state "NO" explicitly.

Testing:

Build Host:  Provide details about your development environment.
Targets:  Be specific about the "custom imx93 board" – is there a name or reference design?
Logs:  While you mention "tested," concrete logs demonstrating the issue before and the fix after are crucial.

Concise Feedback:
The PR description is on the right track but lacks specifics in the "Impact" and "Testing" sections. Enhance it with detailed information about your build environment, target hardware, and, most importantly, provide comparative logs showcasing the fix in action.


Maybe add re2:run/2

Maybe we should add re2:run/2 as a shallow wrapper around re2:match/2, in order to make it easier to switch between re and re2.

Implemented in feature/compat-run_2. Before we can merge this, the following questions need to be resolved:

Is this beneficial enough to add to the API?
Are the accepted arguments and resulting behavior compatible enough to avoid confusion?

Feedback welcome.


animateScroll() won't scroll down for integers

Version: 12.1.4
When trying to use
    const smoothScroll = new SmoothScroll()
    smoothScroll.animateScroll(1000)

everything works fine when I am below 1000px and smooth scroll smoothly scrolls me up to 1000. If I am however, in the beginning of the page (or anywhere above the defined integer), smooth scroll doesn't do anything.
If I provide a node to scroll to, it doesn't smoothly scroll to it, but rather jumps to it if we are above the node. As soon as I'm below the element, it scrolls smoothly again.

I suspect it may have been related to this issue: https://github.com/cferdinandi/smooth-scroll/pull/385
Would you mind downloading the latest version (12.1.5) and seeing if that fixes the issue?

It did indeed! Thanks for the help! :)


Give command timeout

hi, is possible to give timeout to command?
equal to subprocess (python 3.3+)
from subprocess import STDOUT, check_output

output = check_output(cmd, stderr=STDOUT, timeout=seconds)

Closing due to inactivity :+1:

timeout is not work:
import delegator

c = delegator.run('sleep 10', timeout=2)

these codes actually took 10 seconds to end


Cast in order by

I am trying to achieve a cast in the orderBy expression, so the resulting MySQL query will look like:
SELECT * FROM ... ORDER BY cast(number as unsigned);
number is a String field/column. The order Expression I currently use is:
JPQLQuery query = from(qLocation);

if (pageable.getSort() != null) for (Sort.Order o : pageable.getSort()) {
	PathBuilder orderByExpression = new PathBuilder(Location.class, "location");

	query.orderBy(
			new OrderSpecifier(
					o.isAscending() ? com.mysema.query.types.Order.ASC : com.mysema.query.types.Order.DESC,
					orderByExpression.get(o.getProperty())));
}

Have you tied expr.castToNum(Integer.class)?

Do you mean sth. like orderByExpression.getString(o.getProperty()).castToNum(Integer.TYPE) inside the OrderSpecifier?

yes, but Integer.class instead of Integer.TYPE.

That's it. Many thanx.


Add hotkeys

Add hotkey functions to Alerta Web UI via angular-hotkeys

Closing due to merge conflicts. If conflicts are resolved will re-open.


Unhidden commits shouldn't be garbage collected

Description of the bug
I have several commits that have been hanging around for a month or two. I looked at my smartlog today and found they're now listed as <garbage collected>.

Actual behavior
git garbage collection took them and their metadata away and now I don't have record of what was in them.
Version of rustc
rustc 1.61.0 (fe5b13d68 2022-05-18)
Automated bug report
No response
Version of git-branchless
git-branchless 0.3.12
Version of git
git version 2.36.1

Hi @AaronLieberman, sorry to hear that this happened to you ☹. In principle, git-branchless generates references to keep commits around, so I'm not sure exactly what happened. Do you know if one of the following applied in your situation?

You didn't run git branchless init in your repository. In https://github.com/arxanas/git-branchless/pull/185, I suppressed the generation of GC references in a repository which hasn't been inited, to address https://github.com/arxanas/git-branchless/issues/183. But it looks like the underlying problem, which is that tig shows the GC references, seems to have been fixed, so we could revert that change.
One of these commits was created before git branchless init, and you later deleted the branch pointing to that commit. I suppose the GC ref might not have been created in that case.
You hid the commit, then git branchless gc ran at some point, and then you unhid it, but the GC ref wasn't recreated.

Would running git branchless init multiple times be a problem? I've used that to upgrade to new versions of branchless.
I'm trying to remember the sequence of events that led to this but it's been a while since I created those commits. I'm 100% sure they've been created or modified (e.g. moved) long after I branchless init'd the repo. I first created the repo probably in November, started using Branchless around December, and these commits were between 2 and 4 months old.
As for your hide/gc/unhide theory, I think it's unlikely as you described but it's possible that they were affected by some sequence of git move then git undo or git move and git unhide. This is because I sometimes move old commits forward, try to address merge conflicts, then decide it's not worth it right now so abort. However, it seems strange that all 4 of my old commits disappeared at the same time. I guess if I managed to remove all the gc references through various actions and then a gc pass cleaned them up.
Is there a way to get rid of them from this repo so they're not showing in the smartlog? They fail to hide because they can't be found.

@AaronLieberman the simplest way to get rid of them is to attach branches to any commits you care about, then delete the event log database at .git/branchless/db.sqlite3. The principled solution is probably to add some git branchless repair command which will reconcile any mismatched commits/branches.


feat(cms): cms navigation and page component

Description :sparkles:
Issues :bug:
Closes :no_good_woman:
DEV-XXX:
Related :handshake:
Testing :alembic:
Automated tests :gear:
Manual testing :construction_worker_man:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #215 (c619f82) into master (be4e9aa) will decrease coverage by 1.07%.
The diff coverage is 37.76%.

@@            Coverage Diff             @@
##           master     #215      +/-   ##
==========================================
- Coverage   80.97%   79.89%   -1.08%
==========================================
  Files         211      215       +4
  Lines        3769     3880     +111
  Branches     1153     1173      +20
==========================================
+ Hits         3052     3100      +48
- Misses        690      753      +63
  Partials       27       27

Impacted Files
Coverage Δ

src/domain/app/routes/LocaleRoutes.tsx
91.66% <ø> (ø)

src/domain/app/routes/constants.ts
100.00% <ø> (ø)

src/headless-cms/components/CmsPage.tsx
11.11% <0.00%> (-8.89%)
:arrow_down:

src/headless-cms/components/CmsPageNavigation.tsx
7.69% <8.33%> (-4.81%)
:arrow_down:

src/headless-cms/hooks.ts
24.63% <24.63%> (ø)

src/generated/graphql-cms.tsx
47.82% <33.33%> (+13.04%)
:arrow_up:

src/headless-cms/components/CmsPageContent.tsx
25.00% <33.33%> (+5.00%)
:arrow_up:

src/domain/app/header/Header.tsx
67.50% <50.00%> (-0.56%)
:arrow_down:

src/common/components/htmlToReact/HtmlToReact.tsx
83.33% <83.33%> (ø)

src/headless-cms/utils.ts
91.66% <91.66%> (ø)

... and 5 more

Continue to review full report at Codecov.

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


Fixing a vulnerability

The warn commands is missing the permissions decorator so I have added it.

I will push those in a bit when I push the mute command and some others I have made.

Ok, when you do push those, push it to this, and rename the PR


code formatting, strict typechecking, linting, code cleanup and bugfixes

This PR includes some of the work I did on this extension that excludes any new major features I planned. I can split this into multiple PRs or remove some parts that are undesired if that helps with getting this reviewed and merged.
There are a lot of changes is in this PR. Here are some of the notable changes:

use prettier as the code formatter
enable typescript strict mode
enable recommended, strict and stylistic lints from typescript-eslint
remove the execCmd utility function and cleanup code around spawning child processes
fix an issue where ZLS wouldn't start or restart after changing zig.zls.path
consider the initial setup done when zig.path and zig.zls.path are set
show progress while downloading Zig or ZLS

@Vexu I accidentally force pushed to this branch which removed the commits you have added. I was about to restore them but then your merged this PR a few seconds before I pushed again.

No worries, I pushed them directly to master so that I could release a new version.


What is the Dockstore URL?

I see the .dockstore.yml. What is the URL on https://dockstore.org/ for this repository? I am interested in seeing the page. Thanks.

That's another great question. The most useful thing to point to is probably our HPRC organization page here -- though the documentation could probably use an update. Let us know if that is what you are looking for.

Thanks! That URL that you introduced is the link that I was looking for! I am especially looking for the Workflow and Tools page for the below WDL files.

https://github.com/human-pangenomics/hpp_production_workflows/blob/master/QC/wdl/tasks/contamination.wdl
https://github.com/human-pangenomics/hpp_production_workflows/blob/master/assembly/wdl/tasks/filter_hifi_adapter.wdl


react-graphql-client production builds don't work

getting
This function should not be invoked. It should be used to tag template literals that will be
    transcompiled into graphql-js-client's query builder syntax.

closing to get this out of my PR list


Roc 6.1.x

error:
Repo command failed due to the following SyncFailFastError errors:
GitCommandError: 'fetch --quiet --progress KhronosGroup --prune --recurse-submodules=no --tags tag rocm-6.1.1 +refs/tags/rocm-6.1.1:refs/tags/rocm-6.1.1 +refs/tags/:refs/tags/' on OpenCL-ICD-Loader failed
stdout: fatal: couldn't find remote ref refs/tags/rocm-6.1.1
GitCommandError: 'fetch --quiet --progress KhronosGroup --prune --recurse-submodules=no --tags tag rocm-6.1.1 +refs/tags/rocm-6.1.1:refs/tags/rocm-6.1.1 +refs/tags/:refs/tags/' on OpenCL-ICD-Loader failed
stdout: fatal: couldn't find remote ref refs/tags/rocm-6.1.1
Solution:
OpenCL-Runtime Environment is archived https://github.com/ROCm/ROCm-OpenCL-Runtime located in default.xml but it is not needed there, it has been replaced by clr https://github.com/ROCm/clr

Thanks.  I think this was addressed in https://github.com/ROCm/ROCm/commit/b2f0f0acdf56c3c9f7a1b34460f97d3e225a6b58.  We can probably close this PR.


Remove junit test result processor

This has some problems, namely that it gets confused as to what workflow
run to add results to. Related issue:
https://github.com/EnricoMi/publish-unit-test-result-action/issues/12
This seems to be a shortcoming of the github API:
https://github.community/t/specify-check-suite-when-creating-a-checkrun/118380/7

Do we need to revert ci.yml changes too?

@mxpv No, CI.yml just collects the files as build artifacts those are still useful.


Support HTTP 2

HTTP 2 opens less sockets and behaves much better than HTTP 1.1 in case of sudden growth of requests or in case of multiple timeouts.
With HTTP 2 the configuration of the service would also become simpler, for example defaults for  HTTP_CLIENT_CONNECT_THROTTLE and  HTTP_CLIENT_CONNECTION_POOL_SIZE would always be OK

We are going to do HTTP2
@sugarhl, @misha1sh, @Ydot12344

Initial implementation was merged


FTP password field should note that it accepts parameters.

While the FTP Username field states that it accepts parameters, the Password field does not.  Through trying it, I discovered that putting a parameter in that field works (i.e., the password used is the one prompted for in the Run dialog), but it would be nice if that were noted in the documentation.

Bitbucket: https://bitbucket.org/nskvortsov/deployer/issue/15
Originally reported by: Anonymous
Originally created at: 2013-06-14T19:00:16.474

Thank you, this is indeed by design. I have added a note.
Fixed in this build

Original comment by: Nikita Skvortsov

I think the same may apply to SSH Exec and SSH Deployer jobs - I pick Authentication Method: Password. Username has parameter hints, but password field does not. Still, after pasting %param_name% into ****** password field it seems to pick the value from the password parameter just fine.


Error about Cogent installing

Hi @Magdoll ,
After I activating the anacognet by typing :
source activate anaCogent
and it also show :
(anaCogent) user181@cu02#
that proved activation successful.
But when I type :
git clone https://github.com/Magdoll/Cogent.git
to begin install Cogent, the server showed :
zsh: correct 'git' to '_git' [nyae]?
and I will type n, then it showed :
zsh: command not found: git
It's abnormal that anacogent cannot find git, and I couldn't install Cogent normally.
So, I don't know how to deal with this problem.
Thanks for any suggestions!

I have encountered another problem about Cogent installing.
In the wiki of 'Installing Cogent', it mentioned that using :
conda install -c http://conda.anaconda.org/timcera pulp
to install PuLP, but I couldn't install it successfully and it has reported some errors, such as:
/wtmp/user181/software/Anaconda/anaconda2/lib/python2.7/site-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.22) or chardet (2.2.1) doesn't match a supported version!
Solving environment: failed
An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on your way.
ConnectionError(MaxRetryError("HTTPSConnectionPool(host='nanomirrors.tuna.tsinghua.edu.cn', port=443): Max retries exceeded with url: /anaconda/cloud/bioconda/conda/linux-64/repodata.json (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f442574d2d0>: Failed to establish a new connection: [Errno 101] Network is unreachable',))",),)
A reportable application error has occurred. Conda has prepared the above report.
These errors which are part of it has reported just like above, and if you want to see whole errors it has reported, I can send it to your e-mail, because these error are too long.
And I also try to install PuLP in other channel using conda in anaCogent, but it would report the same errors.
So, I will very appreciate for any suggestions!
Another, My conda's version is 4.5.1, can that influence the installing of PuLP? If it influenced, how can we do to fix it?


Subsequent user access request confirmation page shows a server error [6]

Describe the Bug:
When a subsequent user requests access to an operator that already has an admin, after requesting access the confirmation page shows a server error. The request does however go through and the access request is created properly in the database.

Probability (how likely the bug is to happen, scored from 1-5): 3
Effect (how bad the bug is when it does happen, scored from 1-5): 3
Steps to reproduce the behaviour:

As an IO user request access to an operator that already has an approved admin
See the server error at the end of the workflow

@Sepehr-Sobhani I feel like this is maybe related to something you've brought up recently about an endpoint being called unnecessarily?

Yes that was addressed in: https://github.com/bcgov/cas-registration/pull/516
By any chance, do you have server logs?

I manually deployed the head of develop today, so it should have been in there.
Here are the logs when I made the request:

Do I have a cache or something on my shipit?

Sorry, you mentioned manually.
I don't see any errors on logs though :/

I tried this locally and couldn't replicate the error, I'm confused.

I will try it again in dev

Huh, I didn't get the error this time. May have just been a 'blip'. I'll close this card for now, but it's a workflow to keep an eye on as we're QA'ing things


Composer install should say what version of nodejs it requires

Describe the bug

Installing Composer on a Mac without nodejs, it gives you a popup to install NodeJS but doesn't provide guidance it should be version 12 or 14.
Version

Version:  2.0.0-nightly.245007.8406071
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0
Browser

[X] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[X] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Install Composer on Mac 15 (Intel)
Click on "Create New"
See image below.

Expected behavior

Should list expected versions (ie, nodejs 10/12/14)
Screenshots

Additional context

This check in general is a bit odd.  It happens when you click "Create New".  At that time, I haven't registered intent to use C# or NodeJS.  I'm assuming the nodejs it requires is in case it needs to generate a nodejs bot, and not for the Composer runtime itself - it's clearly running.

Shiproom - you can run the tools on any shipping version of nodejs.


IntelliJ 143.* support

IntelliJ 143.* support, should fix #78
This change breaks compatibility with earlier IntelliJ versions.

Thanks! Just in time for the new releases :)


Make it easier to debug 500s that cause casper failures

Right now, if you have a Casper test that fails due to a 500 in the server in the / endpoint, it's really difficult to debug.
Here's an example bad change (breaks the / endpoint):
diff --git a/zerver/lib/events.py b/zerver/lib/events.py
index 123c03a..a1dda84 100644
--- a/zerver/lib/events.py
+++ b/zerver/lib/events.py
@@ -405,6 +405,7 @@ def do_events_register(user_profile, user_client, apply_markdown=True,
                        event_types=None, queue_lifespan_secs=0, all_public_streams=False,
                        include_subscribers=True, narrow=[]):
     # type: (UserProfile, Client, bool, Optional[Iterable[str]], int, bool, bool, Iterable[Sequence[Text]]) -> Dict[str, Any]
+    raise Exception("Bad exception!")
     # Technically we don't need to check this here because
     # build_narrow_filter will check it, but it's nicer from an error
     # handling perspective to do it before contacting Tornado

Here's what the output looks like:
https://travis-ci.org/timabbott/zulip/jobs/212317830
Aka:
ReferenceError: Can't find variable: $
Traceback:
  undefined:2
  :4
Suite explicitly interrupted without any message given.

/var/casper/server.log isn't available in Travis CI, and locally it just has this (with not traceback):
2017-03-18 03:50:35,474 INFO     <IP_ADDRESS>       GET     500  72ms (db: 3ms/3q) /<EMAIL_ADDRESS>via website)
2017-03-18 03:50:35,475 ERROR    "GET / HTTP/1.1" 500 146661

Error logs are written in var/log/errors.log, and has other stuff, but is missing this traceback from the / view.  I think there's a few things we need to fix:

We should try to detect that casper error in the Casper output and suggest it's likely the result of a 500 loading the / page, since that casper output is super confusing.
We should make sure that exception gets into the the server logs.  I think the issue is actually constrained to the / URL -- for some reason exceptions there don't go anywhere in development (you don't need to be doing casper testing to reproduce it).

Working on this.

@zulipbot claim


Add port for sensu-client

Hi,
I would add multiple clients on the same server. It would be cool add port in the template in order to custom port :)

@duylong why do you need a port for the client? The clients are reporting to the server.

I have isolated clients, I no longer need to use "network_mode: host", I close my request :)


⬆  Upgrade Airflow EKS Cluster (Development)

Part of the upgrades of sandpit, development and production.
User Story
As a platform engineer
I expect my clusters to be up to date
So that they whither and die, or end up on extended support because 💰
Value / Purpose
No response
Useful Contacts
Gary, Jacob, Julia, Emma.
Proposal
Upgrade the Airflow cluster - airflow-dev in analytical-platform-data-production
Additional Information
kubernetes-release-calendar
Definition of Done

[ ] Research the components that make up the cluster and understand if the impact/dependencies of upgrading.
[ ] Understand and document how to test the cluster functionality for when this is done in Production
[ ] Upgrade the cluster to 1.30
[ ] Proceed to upgrade the airflow-production cluster

PR to bring the development high-memory nodes into line with the ami used in production. Both now have kubelets at v1.25.

Documented the upgrade process taken in Development, applies to all environments.

Airflow in development was upgrade to version 1.27 as per the above PR last Thursday.

EKS Development now 1.28

Cluster upgraded. More detail in all pull requests if required. Closing issue.


composer not initiating

Description:
when composer command is run from terminal composer is not opened. (I have installed laravel composer and when invoking composer command laravel composer is initiated). link http://localhost:9091 won't open composer i had to manually run composer to make the link work.
It will be useful to distinguish ballerina composer from other composers.
Composer explorer window, when folder structure is changed manually in the directory, is not updated/refreshed automatically. Every time i had to manually refresh.
-----Composer icon on taskbar need to be fixed----

Even these are very minor issues i hope they affect user experience.
Affected Versions:
Ballerina 0.980.0
OS, DB, other environment details and versions:
Windows 10
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

@mster3313 thanks for reporting the issue.
Have you used the Ballerina installer to install Composer?
If you used the installer, you can simply use the start menu shortcut created for Composer to launch it.
More Info: https://ballerina.io/learn/quick-tour/#run-the-composer
We are now packaging Composer with Electron. Hence now there is no need to manually open the browser and point it to http://localhost:9091.
Fix for the distorted task bar icon is already merged and will be available with the next release.
However, the command conflict with composer (php dependency manager) is still valid for linux users and we will look into possible solutions.

@mster3313 I have created a separate issue to track command conflict
https://github.com/ballerina-platform/ballerina-lang/issues/9659

@mster3313 Regarding automatic refresh on explorer upon file system changes:
We hope to add this functionality for future - along with similar functionality for editor tabs where the tab will refresh when a file is changed on disk by external means.
Created a seperate issue to track this https://github.com/ballerina-platform/ballerina-lang/issues/9661

Closing this as per the previous answers.


linkify function does not match URL with underscore

URL with an underscore do not get replaced with HTML links.
In function linkify, the pattern match "a-z" needs to be "a-z_" to match URL with an underscore.

PRs welcome :)


Initialization failed after install the plugin

No controls and graphs shows but when I close the program it asks to save the config

What plugin? And what exactly is the problem? The fact the plugin doesn't initialize? The fact it ask for a save after you made some changes?

https://github.com/Rem0o/FanControl.ADLX/releases/tag/V0.1


style: apply theme globally

@SK-143381 Please resolve the merge conflicts and squash merge once ready.


Simplesort with binary index improvements

@obeliskos
I am currently try to port the newest changes of LokiJS V1 to V2.
I have some questions regarding the simplesort improvements (https://github.com/techfort/LokiJS/commit/4e28e8183aa1d2fa529e8d19a0a805923d11a650,  https://github.com/techfort/LokiJS/commit/82b5eb082e5786a8a3a6de52b197b97183101ecf, et sqq.)

Did you miss to add the field a to the binary indices of the collection?

https://github.com/techfort/LokiJS/blob/7702b06b9ed1bd0f72756e4de7bd949649254d5c/spec/generic/sortingIndexing.spec.js#L291-L294

DynamicView's simplesort uses compoundsort to sort the data.

https://github.com/techfort/LokiJS/blob/7702b06b9ed1bd0f72756e4de7bd949649254d5c/src/lokijs.js#L4100-L4103
https://github.com/techfort/LokiJS/blob/7702b06b9ed1bd0f72756e4de7bd949649254d5c/src/lokijs.js#L4418
Shouldn't compoundsort check also for the new option {desc: true/false}?
https://github.com/techfort/LokiJS/blob/7702b06b9ed1bd0f72756e4de7bd949649254d5c/src/lokijs.js#L3140-L3146

CheckIndex has an unused variable iter. Should it be used in any way?

https://github.com/techfort/LokiJS/blob/7702b06b9ed1bd0f72756e4de7bd949649254d5c/src/lokijs.js#L5301-L5302

Still, thank you very much for your ongoing maintenance!

Thanks @Viatorus !  More validation of benefits that Typescript tooling and checking will benefit us with LokiJS2...

randomSampling has been fixed so that it is actually not ignoring and doing full scan anyways
unit test has been fixed

As for simplesort in dynamic view, our internal typings were a bit convoluted but functionally correct.  I believe a have made changes which should maintain the same functional effect but allow better internal typing for LokiJS2...

Instead of having a single internal representation for both compound sort and simple sort, there are now two... compound sort uses the same (awkward and possibly nested arrays) and simplesort now uses a simple object with propname and options.
The reason this worked before my latest changes is that Resultset.prototype.compoundSort calls simplesort if only one item exists in criteria array.
So rather than load up the method interface of compound sort to accomodate new simplesort options, i decoupled them.
Currently compound sort does not leverage binary indices, that internal call to simplesort was workaround in case there was only one (indexed) criteria.  If a user wants to leverage a binary index on a search criteria, they should go through simplesort.

Let me know if I missed anything or if other glaring internal type cleanup might be useful. I'm starting to familiarize myself more with Typescript so I may join you in LokiJS2 soon :)  Will take a while to absorb all your fine refactoring though :)


feat: implementation of the constant "Pi"

Which issue does this PR close?
Part of https://github.com/apache/arrow-datafusion/issues/5838
Rationale for this change
What changes are included in this PR?
Implementation of the constant "Pi" (3.14159...)
Are these changes tested?
Yes
Are there any user-facing changes?
Yes

Thank you for the review @ozankabak


follow Docker official images recommendation

Description
Publishes latest changes on main branch as package.
What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[x] 🤖 Build
[ ] 🔁 CI
[x] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents

Related Issue # (issue)
Closes # (issue)
Fixes # (issue)

Remove if not applicable

Screenshots

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help
[ ] Separate ticket for tests # (issue/pr)

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?

[x] 📜 README.md
[ ] 🙅 no documentation needed

Checklist:

[ ] My code follows the style 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
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Guter Punkt, wir sollten das latest tag beim release auch schreiben, oder?

macht Uwe das nicht hier https://github.com/open-component-model/ocm/tree/main/components/ocmcli mit OCM-Mitteln?

yes and no... there is no latest tag available - and those images are created only, when there is a new release... so there is currently no 'nightly' build available as docker image


Is this comment still valid ?

I think the ADR is fully supported if the changlog is right, so maybe this comment is outdated ?
https://github.com/brocaar/loraserver/blob/73fae6cfccdcaf19baec78705abe505c29586ff5/internal/adr/adr.go#L25

That comment can indeed be removed. Would you like to create a pull-request?


Making sure that LHM will retry the atomic switch on lock wait timeouts

Problem
If the metadata lock is taken a LHM will fail with  lock wait timeout
Solution
Sleep one second and retry until we succeed or reach  MAX_RETRIES.
This is a patch already merged and used in Shopify/lhm
@arthurnn  @jasonhl

cc @sroysen @SingerWang

Can you add a changelog entry?

Failed on some ar versions that we might not care now?

hmm lies failure is legit, will fix

@arthurnn tests should be working now but travis is :hankey: y at the moment.

@arthurnn do you have admin on travis, I suspect that concurrent tests are making this fail, the reason is the test that tests locked txs will lock the whole db, which is fine when it is running in isolation, if it happens to lock the db when something else is running that test will fail and probs make the locking test fail.
Ideally we have to diff test commands with diff concurrency but to test that I'm not wrong would be good to reduce the concurrency of the build to 1, and see. travis did add that but AFAIK it cannot be controlled from travis.yml https://github.com/travis-ci/travis-core/pull/367/files

I retried only one build to see if would pass, however still getting this error:
 1) Error:
Lhm::AtomicSwitcher::switching#test_0002_should give up on lock wait timeouts after MAX_RETRIES:
ActiveRecord::StatementInvalid: Mysql2::Error: closed MySQL connection: SELECT DATABASE() as db

see  https://travis-ci.org/soundcloud/lhm/jobs/52670405

@arthurnn

ActiveRecord::StatementInvalid: Mysql2::Error: closed MySQL connection: SELECT DATABASE() as db

Is weird sounds to me like travis being not great.

was it configured with a single job at a time ?

@camilo I am running this tests locally, and they randomly fail. So , I dont think this is travis related.
I think we are missing a teardown/clean method on the new tests on atomic_switcher_spec.rb , or something like that. Because seems like that is leaving behind bad state.

works on my machine :tm:

I'll check.

@arthurnn what failures? I can't repro.

https://gist.github.com/arthurnn/a337b91797c228366b76

ping @camilo

OK sycned those threads better, this should pass as long as the test don't run in parallel, if they do the locking thread for a test could lock any other db op and cause weird failures.

ok passes now... small-ish caveat, I'm throwing mysql (the old mysql gem) under the :bus: here and not even attempting retries.

this looks great camilo!!! thanks a lot!
:heart: :heart: :heart: :heart: :heart: :heart:

Any chance of releasing a new version to RubyGems? It's been a full year since the last release, and this critical bug has never made it into a release.

@m1foley thanks for the notice. I will put together a release soon

Thanks! I have some migrations to do in the meantime -- can I assume that master is safe to use in production environments?

@m1foley Yes the one thing you might hit that I'm not sure has been merged is if for some reason you LHM a table with a single row  you might lose that row, there are two patches for that on the PRs, on the other hand why would you LHM a table with a single row?

@arthurnn To follow up, it's been 2 years since the last RubyGems release. There should be another release to include this important bugfix.


fix payloadData length error

fix payloadData length error when it's length is more than 0xffff

Wow good catch.  Took me a minute (actually, several) to even realize why this was broken and how this fix works :)


Updated license

Updated license from ISC to MIT in folder /k8s/package.json to resolve issue #203.

I am closing it as it was already fixed by an earlier pull request.
Thank you for the help, and I hope to see more contributions from you 👍


Merge master of City-of-Helsinki into tre-varaamo

Merge upstream changes from City of Helsinki up until tag 0.4.0 to tre-varaamo which is the active development branch of Tampere-specific Respa stuff.
Refs TAM-24

NOTE: There are a couple of Helsinki-specific things added with this merge that will need to be changed in another PR:

Accessibility API Base URL is set to https://asiointi.hel.fi/kapaesteettomyys/. This is used for Respa Admin Accessibility data input link. If left empty, the input link remains hidden in Respa Admin.
A button has been added to Respa Admin for importing Helsinki divisions


Shift and Spacebar

Hello!
Shift + ctrl + key and Shift + Alt + key are exhibited but Shift + key is not exhibited.
Spacebar is showing up nothing. Just one empty position on screen.
Shift + Space doesn't works like the Ctrl + Space.
Windows 7 x64.

hi @shiftkey ,
Same issue with @andremeireles , Shift + key could not showed up and also single Spacebar.
App download from http://ginnivan.blob.core.windows.net/carnac/Carnac.application
Windows 10 x64

@tonidy @andremeireles apologies for the delay on replying.

Shift + key could not showed up and also single Spacebar.

Let's break these up into two different cases:

what's "key" in this case? If it's a letter, we're probably converting it to the upper case version
we're probably not doing anything with space and it's being displayed as, well, a space

I'd love to understand what the inputs and outputs you're seeing here so that I can reproduce them accurately on my side.

When you want to make a video tutorial (eg. for a content creation application, like Blender) displaying "A" instead of "Shift + A" is not helping. Same for empty " " instead of the key's actual name: "SPACE".
I made a keymap file as a quick workaround.
my_fix.zip
It's not perfect (it displays in both ways at the same time), but it's better than nothing.

Really is very isefull if you can add an option to only show keystrokes.
Then only show ctrl/shift/alt combination and disable all the other keyboard listening.
As other says, it's very usefull to make video tutorials.

The "shortcuts only" option only appears to show shift combinations when used with another shortcut key like ctrl or alt... Some shortcuts, like using Shift+Ins to paste in a linux virtual machine for example, would be nice.
@Kazioo - how would one implement your keymap file?

@shiftkeys What @Kazioo is refering to is probably a choice. Shift+ currently displays the letter as it would ie. either a lowercase or uppercase letter depending on CAPSLOCK. Whereas Shift +  display just the Shift + TAB. In normal user input scenario's its probably correct to display the UPPER/lowercase letter when typing with Shift pressed but when used in applications that have shortcuts attached to these Shift +  combinations (ie. you are not typing text) it would be preferable to also display those as the Shift +  instead of simply displaying the UPPER/lowercase letter. Perhaps this can be a setting preference...

I would also like to see shift and space displayed as modifier keys to show for program tutorials


Making an angular auth guard

This is what I've got
import { Injectable } from '@angular/core';
import { User, UserManager, UserManagerEvents } from 'oidc-client-ts';
import { SettingsService } from './settings.service';
import { Observable, from, of } from 'rxjs';
import { switchMap } from 'rxjs/operators';
import { CanActivate, Router } from '@angular/router';

const url: string = 'http://localhost:44418/';

@Injectable({
  providedIn: 'root'
})
export class AuthService implements CanActivate {

  userManager: UserManager;
  isAuthenticated: boolean;

  constructor(private appSettings: SettingsService, private router: Router) {
    const settings = {
      authority: this.appSettings.authority,
      client_id: 'truth_portal',
      redirect_uri: `${url}signin-callback`,
      silent_redirect_uri: `${url}silent-callback.html`,
      post_logout_redirect_uri: `${url}`,
      response_type: 'code',
      scope: 'openid profile offline_access truth_portal'
    };
    this.userManager = new UserManager(settings);

    this.isAuthenticated = false;
    this.userManagerEvents.addUserLoaded(() => this.update());
    this.userManagerEvents.addUserSignedIn(() => this.update()); // Doesn't work.
    this.userManagerEvents.addUserSignedOut(() => this.update()); // Doesn't work.
    this.userManagerEvents.addAccessTokenExpiring(() => this.userManager.startSilentRenew()); // Haven't witnessed...
    this.update();
}

  get userManagerEvents(): UserManagerEvents {
    return this.userManager.events;
  }

  public getUser(): Observable<User | null> {
    return from(this.userManager.getUser());
  }

  public login(): Observable<void> {
    return from(this.userManager.signinRedirect());
  }

  public renewToken(): Observable<User | null> {
    return from(this.userManager.signinSilent());
  }

  public logout(): Observable<void> {
    return from(this.userManager.signoutRedirect());
  }

  update() {
    console.log('AuthService.update');
    this.getUser().pipe(
      switchMap((user: User | null) => {
        if (user && !user.expired) {
          this.isAuthenticated = true;
        }
        else {
          this.isAuthenticated = false;
        }
        return of(user); // Seem to have to return something; don't know why.
      })
    ).subscribe(
      //  response => console.log(response),
      //  err => console.warn(err),
      //  () => console.log('-- completed --')
    );
  }

  canActivate(): boolean {
    if (this.isAuthenticated) {
      return true;
    }
    this.router.navigate(['']);
    return false;
  }
}

The problem is that the page loads and is redirected to the login screen before this.isAuthenticated gets set.
Can it be made to work? How are you supposed to do it?

What are you trying to achieve ? Protect a specific route or the entire application ?
Conceptually, the fact that you are using your service as a guard is a bit wrong, you should separate the two.
Ideally, you should have:

an AuthService, provided in the APP_INITIALIZER of your app and call an AuthService.init() in a sync way (so that you are sure the whole authentication is ready when your app starts)
an AuthGuard which inject your AuthService and use it to do whatever's needed to protect your routes

PS: I don't like doing advertisement, but I've made a lib that is doing just that (ie. authentication in Angular). It is based on oidc-client-ts and get you ready in just a few steps. You can have a look here. Don't pay attention to the beta tag, it is actually stable - only the documentation remains to be done.

This issue (question) staled, closing it for now.


kali下源码安装完毕后，web页面的密码是啥？没有地方说明

我想登陆进去。
可是不知道web页面的密码，求告知

The default password is given here: https://www.seccubus.com/documentation/12-installation-on-debian/
It is GiveMeVulns!
You can reset the default password via the seccubus_passwd utility in the bin directory as well.

Please confirm it this solves the issue for you.

Google transation of question:
Kali under the source installation is completed, the web page password is what? There is no place to explain

I want to land in.
But do not know the web page password, ask for advice

No reply, closing issue


KSV038 is triggered and failing on all Kubernetes files expect of good network security policies

Used by trivy:0.28
No negative test in selector_usage_in_network_policies_test.rego

Add a test with a  Deployment manifest
On Tue, May 17, 2022, 8:01 PM Liam Galvin @.***> wrote:

Hi @Alexander-Bartosh https://github.com/Alexander-Bartosh - we have a
test that passes in the following scenario:
apiVersion: v1
kind: NetworkPolicy
metadata:
name: hello-cpu-limit
spec:
podSelector:
matchLabels:
role: db
It can be found here
https://github.com/aquasecurity/defsec/blob/master/test/testdata/kubernetes/KSV038/allowed.yaml
.
Using a podSelector or namespaceSelector should cause the check to pass.
Do you have an example scenario where this is not the case?
—
Reply to this email directly, view it on GitHub
https://github.com/aquasecurity/defsec/issues/606#issuecomment-1129161038,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE3AZZEH7T4LJMKWE5C4TTVKPNIPANCNFSM5WFQLQYQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

My apologies. It is about a service manifest. Here is a failing test:
test_service {
r := deny with input as {
"apiVersion": "v1",
"kind": "Service",
"spec": {
"clusterIP": "None",
"internalTrafficPolicy": "Cluster",
"ipFamilyPolicy": "SingleStack",
"selector": {
"app": "zylabhold-azure-devops-build-agent-v2"
},
"sessionAffinity": "None",
"type": "ClusterIP"
},
}
count(r) == 0

}

0002-Fix-for-https-github.com-aquasecurity-defsec-issues-.patch.zip

it is in the PR


WIP: Update plugin name to opensearch-anomaly-detection

Description
Updates the plugin name and folder to follow the naming convention opensearch-<plugin-name> (all lowercase).
Updates the version to build a zip with version <IP_ADDRESS>-beta1 appended.
Updates the job scheduler plugin name to opensearch-job-scheduler, which will be changed after this PR merges
Built successfully locally to confirm the artifact name.
Issues Resolved
#22
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

The integ test failure is related to the job scheduler name change - we may wait for that change to merge, add an updated zip in src/test/resources, and retry the workflow.

Let's definitely wait for upstream changes and alpha2 to get all this stuff to green.

Build is green so you can finish this.

Closing in favor of #28


MIT site currently broken

Sometime between 2/3 and 2/5 it seems the site hydrant.mit.edu went down and now displays a 403. As a stopgap, the wayback machine has a usable version from 2/3 haha (EDIT: it doesn't allow any calendar exports though). If I had to guess, it would be from a botched crontab deployment after the recent PR, but I can't really be sure. Thanks for all the hard and often thankless work!

no, it's down because scripts is down. there's a mirror up at https://sipb.github.io/hydrant/


Improve RegressionErrorResult

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

Project coverage is 100.00%. Comparing base (06e86b8) to head (98fe193).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #501   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          114       114
  Lines         3052      3057    +5
  Branches       178       178
=========================================
+ Hits          3052      3057    +5

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


CheckStyle-Rule-Extension: 5, 6, 7

Check 6:  @ServiceClientBuilder

All service client builder should be named ClientBuilder and annotated with @ServiceClientBuilder.
Has a method 'buildClient()' to build a synchronous client,
Has a method 'buildAsyncClient()' to build an asynchronous client

Check 7:  @ServiceInterface

The annotation property 'name' should be non-empty
The length of value of property 'name' should be less than 10 characters and without space

Take off rule 5 check and prioritize on rule 8 and 9

There are 116 checkstyle errors produced by rule 9. Fixing those now

No 9 is still experiencing the IO exception failed which is the same problem about reflection. But the existing rule implementation is ready for review.

I think these checks might have to be split up into another PR. (ie. Check 9 about logAndThrow will result in a PR that touches many files.)

Cleaned up and ready for review again. :>

PR is ready for reviewing again


Feat: add vela debug command

Description of your changes

Vela Debug
Add vela debug command, which can debug all the applications with debug policy.
All the flags:
Flags:
  -e, --env string         specify environment name for application
  -f, --focus string       specify the focus value to debug
  -h, --help               help for debug
  -n, --namespace string   specify the Kubernetes namespace to use
  -s, --step string        specify the step to debug

Usage:
vela debug <application-name>

First, it will ask you to choose a workflow step or component to debug:

Then, choose the field to debug:

Some example outputs:

Error case:

You can also use --focus or -f to show the specific value:
vela debug <application> -s <step> -f <focus>

Some example outputs:

For applications with components only, it will show the result of dry-run:

Vela Up
Add --debug in vela up, if the debug flag is specified, it will add debug policy in the application automatically and jump into debug mode after the application is created.
TODO:

[ ] Add --watch flag in vela debug.
[x] Add tests.
[ ] Debug policy can support choosing components.

I have:

[x] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[x] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

/cc @wonderflow @Somefive @leejanee @chivalryq @yangsoon

this feature will go into v1.4


Makefile use  GNU sed and force thrift to use the same user

fixes #339

Coverage remained the same at 100.0% when pulling dd9ea97bfded2998d5262084d1294045809e18ae on pavolloffay:fix-sed into 413942a087934711620cc1e15ea72886eebadffd on uber:master.

I'm using the default MacOS sed, which has no version, but its man page says
     -i extension
             Edit files in-place, saving backups with the specified extension.  If a zero-length extension is given, no
             backup will be saved.  It is not recommended to give a zero-length extension when in-place editing files, as
             you risk corruption or partial content in situations where disk space is exhausted, etc.

...

STANDARDS
     The sed utility is expected to be a superset of the IEEE Std 1003.2 (``POSIX.2'') specification.

     The -E, -a and -i options are non-standard FreeBSD extensions and may not be available on other operating systems.

HISTORY
     A sed command, written by L. E. McMahon, appeared in Version 7 AT&T UNIX.

AUTHORS
     Diomidis D. Spinellis<EMAIL_ADDRESS>
BSD                              May 10, 2005                              BSD

basically the -i switch requires an argument

The -E, -a and -i options are non-standard FreeBSD extensions and may not be available on other operating systems.

I have added a simple hack. It would be better to use just the standard GNU version https://stackoverflow.com/a/34815955/4158442.
When I run it, it produces some changes like:
diff --git a/thrift-gen/jaeger/tchan-jaeger.go b/thrift-gen/jaeger/tchan-jaeger.go
index 393b8f1..89e1e9c 100644
--- a/thrift-gen/jaeger/tchan-jaeger.go
+++ b/thrift-gen/jaeger/tchan-jaeger.go
@@ -43,6 +43,10 @@ func (c *tchanCollectorClient) SubmitBatches(ctx thrift.Context, batches []*Batc
        }
        success, err := c.client.Call(ctx, c.thriftService, "submitBatches", &args, &resp)
        if err == nil && !success {
+               switch {
+               default:
+                       err = fmt.Errorf("received no result or unknown exception for submitBatches")
+               }
        }

        return resp.GetSuccess(), err

Is it fine?

Coverage remained the same at 100.0% when pulling 22dfcb7cbbed78e11e4a5cf38e83dc8d33930e2c on pavolloffay:fix-sed into 413942a087934711620cc1e15ea72886eebadffd on uber:master.

don't think the hack quite worked.
when I ran make thrift, it did not produce any differences in the existing files, but created three new files
	thrift-gen/agent/agent.go-e
	thrift-gen/agent/constants.go-e
	thrift-gen/agent/ttypes.go-e

I think the -e was interpreted as a suffix.

This is bad I will revert to pure GNU sed. Can we just use the standard GNU sed which is available on all systems? It's definitely a good thing for the community. Gnu sed can be easily installed on MacOS.

I have tried the last workaroud using -i.bak and then remove those files. But this does not prevent that new BSD commands will be added and it will fail for other contributors.

Coverage remained the same at 100.0% when pulling 93cdd4dde25b946b1f0dd8cd71024dbd7fdcffe8 on pavolloffay:fix-sed into 413942a087934711620cc1e15ea72886eebadffd on uber:master.

This is bad I will revert to pure GNU sed. Can we just use the standard GNU sed which is available on all systems? It's definitely a good thing for the community

I have mixed feelings about it, installing GNU sed is simple using brew, but one needs to finagle the path to make it the default sed that is used for everything. (Also, it would probably break other software that assumes that BSD sed is installed)
Is it too bad to have a conditional on uname -s, with the appropriate sed commands for a given environment?

@vprithvi now it should be compatible with BSD and GNU could you please test it?

Works for me, could you add a comment on why we are doing these shenanigans with sed in the makefile?

Coverage remained the same at 100.0% when pulling 69508e893dec925d9a32ca73d192cfe3c856379b on pavolloffay:fix-sed into 413942a087934711620cc1e15ea72886eebadffd on uber:master.

works for me. I restarted the builds.


Asset caching

Additions that make it possible to write in-memory stores for on-disk data.

Codecov Report

Merging #32 into v3.0.0 will increase coverage by 0.32%.
The diff coverage is 90.38%.

@@            Coverage Diff             @@
##           v3.0.0      #32      +/-   ##
==========================================
+ Coverage   88.24%   88.56%   +0.32%
==========================================
  Files           7        7
  Lines         621      656      +35
  Branches       59       65       +6
==========================================
+ Hits          548      581      +33
- Misses         56       57       +1
- Partials       17       18       +1

Impacted Files
Coverage Δ

luna/server.h
97.72% <ø> (ø)
:arrow_up:

luna/types.h
100% <100%> (ø)
:arrow_up:

luna/server.cpp
76.59% <100%> (+0.5%)
:arrow_up:

luna/private/server_impl.cpp
88.58% <90%> (+0.41%)
:arrow_up:

Continue to review full report at Codecov.

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


🚀 Feature: App description should come from config

🔖 Feature description
Currently, the application description is hardcoded to https://github.com/backstage/backstage/blob/master/packages/app/public/index.html#L9
This, like the title, should come from the application config if available.
🎤 Context
Description change requires now that the index page is modified instead of app config. This makes changing the title and description work differently.
✌ Possible Implementation
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

I think we'll want to leave this to be configurable manually in packages/app/public/index.html. The title is already available in config so it makes sense to grab it by default, but I'm feeling it's not worth adding a new configuration key for the description, at least not at this point.

Ok, it's just a bit weird that these live in different places 😄 I wouldn't mind having another config value for description. Or removing the title; just as long as it's consistent.

@drodil yeah I appreciate that and it's a little unfortunate that if we were to remove the title from config it would be a breaking change. We were just thinking that it's one of the most common use cases and that option was in config from the beginning. Happy to keep this open to see if there's others that want to chime in too on maybe adding some other options in config.


⚠ Bofrost.fr has degraded performance

In 4a49d8c, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1254 ms

Resolved: Bofrost.fr performance has improved in b1d7e53 after 6 minutes.


<EMAIL_ADDRESS>

Release: https://github.com/aherrmann/rules_zig/releases/tag/v0.1.0
Closes https://github.com/aherrmann/rules_zig/issues/90

@fmeum I think this one still needs a tag for CI to run.


tail: reuse opened file --follow=descriptor and renamed

Discussed here https://github.com/uutils/coreutils/pull/3798#issuecomment-1212438940
@jhscheer, I'm not sure we need ?, because it only happens when initially we couldn't open the file, so tail printed cannot open file for reading telling about an error to the user. But there can be a case when the file has been renamed twice, for example, in which case we don't print anything now, but later on the next event we will print something.

@jhscheer ok with you ?

@jhscheer ok with you ?

Yes, looks good to me.


Editor rwsignal

Some of the view code uses a RwSignal<Editor> when that doesn't entirely make sense.
Editor is 99% shared in-of-itself, except for the Cell<Scope>s: effects_cx is disposed & recreated if you call recreate_view_effects / update_doc / update_styling. These being Cells mean they aren't shared.
Currently TextEditor stores the Editor instance directly and clones it for an RwSignal to pass into the view.
This is incorrect as the user may want to call TextEditor::with_editor_mut in order to replace signals with their own signals. (Such as in Lapce — though Lapce doesn't use TextEditor — where we have some behavior shared between all the editors)
Cloning it on the creation of the TextEditor is wrong as it means if you want to replace those signals, well you've already the view and it won't see those replaced signals.
Lapce stores it as Rc<Editor> for this reason.
Technically, you could just the TextEditor field as an RwSignal<Editor> and then just have with_editor_mut use update. However in reality the editor view functions aren't really made to support completely swapping out the signals after the views have been created, that is meant as an initialization method.
It should really be that Rc<Editor> (or Arc<Editor>? Lapce currently doesn't try sharing editor data across threads that directly) is passed into editor_container_view and friends, as update doesn't hold that much of a meaning when we aren't tracking it to that degree.
(An alternative would be to allow completely replacing those rwsignals via properly propagating gets of RwSignal<Editor>, but I do think it is simpler codewise and less prone to bugs to go "if you want to swap out the signals do it at initialization of Editor, or spam create_effect instead of actually replacing them")

I think an Rc would make sense.


Remove use of time.Now()

Description
The use of time.Now() should be completely avoided due to non-determinism. Here's an example of the use of time.Now() being reported as a vulnerability in the past: link.
In the scope of testing, this is usually fine to use. However, looking through here, it seems like there are instances where it is being used outside of the scope of testing. This should be replaced with ctx.BlockTime() which will be the same for all nodes running the blockchain.

@migueldingli1997 noted

It has been replaced with ixo v0.20.0 thanks @migueldingli1997


updates to html and css

fixed duplicated attr and cleaned up css and title styles
Changes / Comments
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[x] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

FFG_End of the world character sheet


Github organization configured to the child should be shown to the parent CLA groups manage screen.

Go to the PCC dev https://pcc.dev.platform.linuxfoundation.org/
Create one parent project (PCC-Parent-Project)
Add two child projects to the parent (PCC-Child-Project-1 and PCC-Child-Project-2)
Create CLA group to first child project and configured github org.
Create CLA group to second child project and configured github org.
Go to the parent project
You can see both the CLA groups
click on manage button
No github organisation shown.

Issue is tested & found that it is fixed as expected on dev site, related frontend tickets are already moved to QA-Done state , So moving this tickets status QA-Passed on dev site
Related ticket : PCC-2479 : Easycla : Wrong GitHub organization appears at child project

Now able to see GitHub organization at child1 & child 2 projects as expected, Reported issue is properly fixed & deployed at prod end.

Done.


Images

I am using a lot of mnemonics for my flash cards and audio files. Does ankdown support them? And if yes, how would I add them to my flash cards?

Had the same question here - I haven't tried it yet, but it looks like perhaps HTML image tags might work, as per this section in the code: https://github.com/benwr/ankdown/blob/38839a0f1d3e4c1c4040c5142b1ea2827d325cfe/ankdown/ankdown.py#L157
Might be possible to modify this to look for the usual markdown image tags, not sure!

Yes, images should work - if they don't, feel free to reopen this issue.


chore: change logging to use name instead of module

Closing this since we're using structlog now.


Remove all RSpec test filters related to Ruby 1.8 and 1.9

Removes all RSpec filters used with Ruby < 2 and some related lib/ code.
I left all the tests using RUBY_VERSION for another future PR.
Fixes from #2497:

[ ] spec/support/platform_helpers.rb#L26-L28

closed by #2823


support multi-threaded memory-sharing features

Can the MemoryStorage support multi-threaded memory-sharing features? Like supporting MVCC

Good suggestion, thanks.
I think it would be good to make another storage rather than adding multi-threaded feature to MemoryStorage. SharedMemoryStorage may work.
Limiting the scope to single-threaded makes codes extremely simple, as we see the codes in MemoryStorage.
I expected the role of MemoryStorage as, not just production-ready single-threaded in-memory storage, but also it can be the good guide document for someone who considers to make their own custom storages.
SharedMemoryStorage, I don't have plan to make it by myself at least until this year, but anyone can dive into this task :)

Good suggestion, thanks. I think it would be good to make another storage rather than adding multi-threaded feature to MemoryStorage. SharedMemoryStorage may work.
Limiting the scope to single-threaded makes codes extremely simple, as we see the codes in MemoryStorage. I expected the role of MemoryStorage as, not just production-ready single-threaded in-memory storage, but also it can be the good guide document for someone who considers to make their own custom storages.
SharedMemoryStorage, I don't have plan to make it by myself at least until this year, but anyone can dive into this task :)

I'm going to take it as a sub task.
But since it can work for a very long time, anyone can take this issue.


Use of override since Godot is now c++11

Since Godot is now c++11, what are the opinions on using override in derived class methods everywhere?
It uses the compiler to help detect if the method made is the exact method overridden to avoid mistakes.
It's like the use of const, where it enforces rules but is not necessary.

Since Godot is now c++11

Godot requires a C++11 compiler because some of its dependencies, but the source of Godot itself it's still based on C++03. See #9694.

That doesn't really answer the question posed in the original post.
Are you saying that the use of the override keyword is disallowed?

When will that be?

Reopen when godot revisits c++11.


changing the colours of UI to enhance user experience

THe current UI colours can be changed in order to enhance the user experience .


added blocking true to call medator in digest mode

 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.


[MXNET-130]disable cpu/gpu consistency test for Proposal OP and Multi Proposal OP

Description
I'm sorry that I made a mistake in the CPU/GPU consistency test for Proposal Operator and Multi Proposal Operator.
I disable cpu/gpu consistency test for Proposal OP and Multi Proposal OP temporarily until fixed.
Unit Test Detail:
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-10161/5/pipeline/549#step-919-log-1763
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Please create a JIRA issue and link it in the test-disable-reason. The explanation you gave there gets put into the JIRA issue instead.

@marcoabreu Hello. I have created a JIRA issue and linked it. Thank you!


13.19 Update

Hi please include the built .dll file in the update pull requests so if someone is not able to download visual studio and its huge volume can download it directly like for this one I uploaded at here

Hi please include the built .dll file in the update pull requests so if someone is not able to download visual studio and its huge volume can download it directly like for this one I uploaded here

Hey :) see my releases, 13.19 has both the injector and the dll.


Spin.js freezes when DOM is being manipulated in IE9

The docs seem to indicate that hwaccel: true should push the animation onto the graphics hardware and out of the main UI thread, thus permitting the animation to continue while the page DOM is being manipulated.
And this works well for Chrome. Unfortunately, it does NOT work for IE9. It does animate while a form is being processed (one IE issue) but following an AJAX request or other dynamic changes to the page (such as when angular-spinner is used in an AngularJS application), the icon freezes and it becomes no better than a lame animated gif from 1999.

If this is still a problem in spin.js v3.0, please reopen the issue with a reproducible example.


New version: DenoLand.Deno version 1.36.0

Pull request has been created with Komac v1.9.1 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115136&drop=dogfoodAlpha

@wingetbot run


How do I install it

Dumb question, I know

$ cd udpreplay
$ make build
$ cd build
$ cmake ..
$ make
$ make install
I should put this in the readme. This is the standard CMake build and install procedure.
Sent from Mail for Windows 10
From: Will Bishop
Sent: Saturday, January 14, 2017 5:37 AM
To: rigtorp/udpreplay
Cc: Subscribed
Subject: [rigtorp/udpreplay] How do I install it (#1)
Dumb question, I know
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Loan comparison: mobile editing functionality & mobile inputs styling

Additions

Loan name:

setLoanName function in loan store adds letter name property to loan for display on mobile
Tests for setLoanName function

Mobile editing functionality

adds startMobileEditing and stopMobileEditing functions in App component to store loan being edited in app state
adds mobile header in LoanInputTable component to identify loan being edited & mobile-editing classes to toggle display of loan inputs on mobile
adds 'save and close' buttons in LoanInputTable to stop mobile editing
adds edit buttons for each loan in LoanOutputTableMobile component to start mobile editing
hooks up name display & outputs for loan amount, summary, and points in  LoanOutputTableMobile
adds loan amount output for display on mobile in LoanDownpaymentInput component

Mobile input styles

Adds identifying class to each LoanInputTableRow so they can be targeted on mobile
adds mobile-specific less for inputs

Removals

Removed interest rate update button & associated state

Notes

At the moment, the api is still being called on every change in mobile editing. These calls should just be made when exiting edit state, but I'm holding off on this until the output loading state is ready. I've revised the mobile editing task in the next sprint to cover this change.

Preview

Review
@cfarm @stephanieosan

@virginiacc Can you resolve the conflicts?  Then I can start reviewing

@amymok I think all the merge conflicts are fixed now...

@amymok The loan-comparison.js file is now commented out in the grunt browserify task, so you will need to uncomment the references to it locally in your Gruntfile to view these changes.

Looks great to me!


Update fails - undefined method `ungz'

I'm trying to update all the gems that come with logstash 1.5 beta1 and this gem fails with the error below.  How do I skip a gem when I'm trying to update all the gems?  Otherwise, I'm going to have to list every single gem I want to update.
NoMethodError: undefined method `ungz' for LogStash::Util::FileTools:Module
process_downloads at /logstash/lib/logstash/util/filetools.rb:180
each at file:/logstash/vendor/jruby/lib/jruby.jar!/jruby/java/java_ext/java.util.rb:7
process_downloads at /logstash/lib/logstash/util/filetools.rb:162
setup_hook at /logstash/lib/logstash/pluginmanager/vendor.rb:13
call at org/jruby/RubyProc.java:271
run_post_install_hooks at /logstash/vendor/jruby/lib/ruby/shared/rubygems/installer.rb:273
each at org/jruby/RubyArray.java:1613
run_post_install_hooks at /logstash/vendor/jruby/lib/ruby/shared/rubygems/installer.rb:272
install at /logstash/vendor/jruby/lib/ruby/shared/rubygems/installer.rb:237
install at /logstash/vendor/jruby/lib/ruby/shared/rubygems/request_set.rb:75
each at org/jruby/RubyArray.java:1613
install at /logstash/vendor/jruby/lib/ruby/shared/rubygems/request_set.rb:62
install at /logstash/vendor/jruby/lib/ruby/shared/rubygems/dependency_installer.rb:363
update_gem at /logstash/lib/logstash/pluginmanager/update.rb:70
execute at /logstash/lib/logstash/pluginmanager/update.rb:36
each at org/jruby/RubyArray.java:1613
execute at /logstash/lib/logstash/pluginmanager/update.rb:36
run at /logstash/vendor/bundle/jruby/1.9/gems/clamp-0.6.3/lib/clamp/command.rb:67
execute at /logstash/vendor/bundle/jruby/1.9/gems/clamp-0.6.3/lib/clamp/subcommand/execution.rb:11
run at /logstash/lib/logstash/runner.rb:144
call at org/jruby/RubyProc.java:271
run at /logstash/lib/logstash/runner.rb:171
call at org/jruby/RubyProc.java:271
initialize at /logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.18/lib/stud/task.rb:12

hi @rabidscorpio, we recently fixed this in https://github.com/elasticsearch/logstash/pull/2572. Unfortunately this requires you to use the latest version of Logstash core. We are working on a RC1 release (soon) which will include this fix

From the last comment it sounds like this was fixed. Gonna close this. Feel free to open a new ticket if this continues to be a problem.


VideoStream.read() returns a none type object in ubuntu 16.04

I used this code to check and it did print none in the console
from imutils.video import VideoStream
webcam = VideoStream(src=0).start()
while True:
    frame = webcam.read()
    print(frame)

It sounds like your are unable to access the webcam on your system. It's 99% likely that your install of OpenCV wasn't compiled with video support. Re-install OpenCV and compile it with video support.
Alliteratively, the index of your src may be incorrect.

Yes @jrosebr1, I got this solved by compiling the opencv again. Previously I've installed opencv using apt-get.  I uninstalled the opencv and downloaed opencv from github repo and compiled it. Now it's working. If anyone having the same issue, follow this tutorial http://www.pyimagesearch.com/2015/07/20/install-opencv-3-0-and-python-3-4-on-ubuntu/ to install opencv.

Nice job resolving the issue @prabushitha 😄


chore: add immutable nodes and trie

TODO:

[x] Modify timestamps on clone
[ ] Test individual nodes for Arc

Merged with https://github.com/surrealdb/tart/pull/1