lbry

The Issue
Steps to reproduce

Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

Please close this if it was opened by mistake.


Auto Imports

I am using Webstorm and Typescript.
Tabnine does not work as well as intellij when it comes to calling functions and referencing variables in other modules. Intellij can auto import these symbols when you hit enter. Can you make it so intellij has higher priority in the suggestion list for these symbols. Or perhaps make a hotkey selection possible for the intellij suggested symbols?

Hey @njmaeff
There is a setting you can enable in your IDE to make this work: https://www.jetbrains.com/help/idea/creating-and-optimizing-imports.html#automatically-add-import-statements
Let me know if that did not work. Thanks.

I have all the auto import settings enabled but I still don't get any imports with the tabnine suggestions. I do if I select one of the intellij suggestions, for example the writeFileSync suggestion in the original post. Here is my editor info.
WebStorm 2020.3.2
Build #WS-203.7148.54, built on January 25, 2021
Runtime version: <IP_ADDRESS>+11-b1145.77 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 5.4.0-64-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 3987M
Cores: 16
Registry: ide.balloon.shadow.size=0, js.debugger.webconsole=false, ide.images.show.chessboard=true
Current Desktop: ubuntu:GNOME

I suspect that this is a bug in Jetbrains' Auto Imports feature. I'd advise you to submit a bug for them, as we rely on that mechanism (which is working on various other setups we used to try it).
Let me know if I can further assist you.


Support for choosing to update from different channels

Does Nuts support being able to choose which channel I want to update from? For example, I have my app with version v0.1.0. If I want to choose between uploading to version v0.1.1 or v0.1.2-alpha (channel depends on tag names), is there a way to do this? like
var platform = ...;
var version = ...; // the usual
autoUpdater.setFeedURL('http://.../update/channel/stable/platform/version")

or
autoUpdater.setFeedURL("http://.../update/channel/alpha/plaform/version")

I know electron-release-server does this, but I want to stick with Nuts.

Hey try our fork for test https://github.com/Coldewey/nuts
I merged this kind of stuff https://github.com/GitbookIO/nuts/issues/20 to get the channel update behavior

@JPeColCom I just made a fork that supports this (added a simple route for /channel). I'll test yours out soon :)

👍

@JPeColCom I got around to trying your fork, it had a bit of stuff missing. Here's my fork - I added new endpoints, and channels are supported by tag name suffixes. I'll submit a PR and see how it goes. I'm using it now for my app if you were interested:
https://github.com/mzmousa/nuts


Fix shading opt out in io/google-cloud-platform

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Changes Unknown when pulling dd1b001728375aeecfc577de7ea13761aa37322c on aviemzur:fix-google-io-shading-opt-out into ** on apache:master**.

R: @amitsela
This is a fix for broken master build.
Looks like the opt-out instructions in PR #2096 (comment) were faulty and caused this build to break.
I've since edited the comment with a correct version and opened PR #2259 which uses the fixed version for opting out.

LGTM


Release 0.4.12

Codecov Report
Patch coverage has no change and project coverage change: +20.87 :tada:

Comparison is base (f0623d7) 73.35% compared to head (e7c3ab1) 94.23%.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #349       +/-   ##
===========================================
+ Coverage   73.35%   94.23%   +20.87%
===========================================
  Files         198      116       -82
  Lines        9756     3120     -6636
  Branches      812      375      -437
===========================================
- Hits         7157     2940     -4217
+ Misses       2168      180     -1988
+ Partials      431        0      -431

Flag
Coverage Δ

backend
94.23% <ø> (ø)

frontend
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 82 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Rename KeyType -> KeyAlgorithm

KeyType was found to be a bit confusing: https://github.com/TBD54566975/web5-rs/pull/20#discussion_r1412220155
We originally had it as KeyAlgorithm, but changed it here: https://github.com/TBD54566975/web5-rs/pull/17#discussion_r1401124839
This PR switches it back to KeyAlgorithm!

Point taken, closing!

Thanks for sharing @decentralgabe, I wasn't aware of the distinction


Add configuration validation

Validate the configuration on changes in the ConfigurationCenter. We should use utilities from Spring that should make this quite simple. Don't update nor fire the update event if the new configuration is not valid.

@JonasKunz is this fixed actually with #22?

Yes, thought this was a part of #4 :D

I think we forgot about one point which should be adressed here:
What happens if the startup configuration is invalid? Should the agent terminate or should it run with the default configuration? Or should we use some kind of "fail-safe" configuration where everything in the agent is disabled except for the polling for configuration changes?

Good point.. Let's tackle this case as well..


Add data.logentries.com endpoint

Allow for Users to use data.logentries.com endpoint instead of api.logentries.com.
The benefit here is that this endpoint allows connections over port 80 and 443.
Currently making it an optional param as I am worried I will break folks integration if I change the currentd default endpoint.
In other news I think the options list has become extremely bloated :(

@stakach take a look?

Love your work! Looks good to me. :)


it's required fields that should not exceed 300, not optional + required

did you read https://sbqr.ru/standard/files/standart.pdf?
it's required fields that should not exceed 300, not optional + required
https://github.com/codebude/QRCoder/blob/cecf2066d3f3a74b142aaa7c8d9f744c4673118c/QRCoder/PayloadGenerator.cs#L2531
please fix asap

Guuuys, it must be done asap

So it just needs to be  if (bytesOut.Length >= 300)

no, the spec says:

meaning only required fields should not exceed 300, meaning bytesOut should contain only required fields
it says nothing about optional fields

about optional fields:
the spec says:

meaning what free space remains may be used by optional fields


Allow CallbackExceptionHandler to be set on DeferredManager and Promise

The result of a quick spike to figure out if it's possible to define CallbackExceptionHandler on both DeferredManager and Promise in order to have localized exception handling. The current rules are:

setting CEH on a Promise  (once submitted) takes precedence over the other CEH (as long as it's set before any callback resolves).
every Promise passes on its CEH to any Promise created by it, such as FilteredPromise and PipedPromise, in other words children promises inherit the CEH from their parent.
setting CEH on DeferredManager sets it on every Promise created by this DM.

Precedence of invocation for CEH is thus set as: promise, dm, global.
Please have a look at FailureTest to see how this mechanism works.

This change is

Coverage increased (+1.0%) to 55.717% when pulling 9c8e08e147110be2829887b6d03f84ac0fa59861 on aalmiray:local-exception-handler into 395e988dd18af90d711659aa4a39b9efcf8ec8fe on jdeferred:2.x.

My first thought at this is, what if the promise is shared w/ multiple consumers? Each consumer can attach their done/fail callbacks. But when it comes to callback exception handling, they could overwrite each other.

Review status: 0 of 20 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

indeed. There are other problems such as: let's assume you have a Promise created by dm1, combine it with other promises from dm2 -> the first promise now has it's CEH set by dm2 (if non-null, I missed that check). This definitely requires more work, specially coming up with possible scenarios

Review status: 0 of 20 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Add pull request template.

This mainly contains a checklist of things we should think of when making a new PR.
It should then appear by default in the description of the PR when opening a new PR. If you guys find that unnecessary, no problem, it's just a suggestion ;-).

Fine with me. This is a good idea.


Fix CachedQueryResultsTest

This results in the failing tests going from 130 to 125

Awesome! Thanks

💪

Nice.

🙏


Embed tutorial video

@shikokuchuo, this PR embeds a 2-minute video showing how to use the GitHub UI to contribute packages.

The video itself is at https://vimeo.com/923333903.

It really looks good on the site though!
@eitsupi FYI video instructions now live at https://r-releases.github.io/contributors

Great suggestions. I got the video down to exactly 1 minute, and the new version is posted. I'll go ahead and change "2-minute video" to "1-minute video" in the description.


Difficulty in setting up the FORCE repo - Local & Prod Development Setup

Hi Team,
I have some difficulty in setting up the force project locally, and I am looking forward to contributing to the Force code.
I have followed the below steps as per the CONTRIBUTING.md guidelines:-
Local Development setup:-

git clone git@github.com:artsy/force.git && cd force
Run ./scripts/setup.sh (for installations and env files setup)
yarn start

Facing below issues:-

Failing auth (URL - /API/v1/xapp_token) - Do the client id and secret still valid for the OSS development

Module Not found - (src/generated folder)

Can't see any data due to issue 2 I guess. Let me know if the OSS env (API/Cloudfront images URL) variables values are still valid or require some change.

Local Production Development:-

Webpack config fails

Note: I added a cross-env package to set the env variables on my window machine.
Have a few questions about the repo

I see that Redis is being used - Can you please highlight when it caches the data?  (During the load or pre-loading of the page?)
About React-Relay (Have used apollo previously, but new to react relay) - How is the GraphQL (Types and Hooks ) getting automatically generated within the src/generated folder (is this done under the hood by relay-compiler)?
Backend Setup? (any guidelines here)?

Thanks in advance :) Looking forward to your response.

Hi @desaijay315 - could you please paste the entire error printout from your first image? You can use triple backticks like ```  to apply monospaced/code formatting.
Regarding your question number 2, does the command yarn react-relay work? It should execute successfully and not say that any files were changed or generated in its output.
Finally, I would say this repository makes some assumptions about your develop environment, including that you are in a MacOS or linux environment. If you are using WSL it's likely there will be some additional setup steps at a minimum.

Hello @erikdstock - Thanks for your response.
Yes, I am on a windows machine :(
Here's the entire error printed on a gif - Kindly ZOOM-IN to your browser

yarn run relay

@desaijay315 as a mostly windows user, I can affirm that wsl will be the way to go to ease setup on this project.
Here is a guide on getting WSL set up in windows:
https://learn.microsoft.com/en-us/windows/wsl/install

Sure, let me give it a try...:) That might surely work I feel since it
works successfully on macOS and Linux...
On Thu, 20 Oct 2022, 20:03 Laura Bhayani, @.***> wrote:

@desaijay315 https://github.com/desaijay315 as a mostly windows user, I
can affirm that wsl will be the way to go to ease setup on this project.
Here is a guide on getting WSL set up in windows:
https://learn.microsoft.com/en-us/windows/wsl/install
—
Reply to this email directly, view it on GitHub
https://github.com/artsy/force/issues/11203#issuecomment-1285655218, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHKWYKNPZVUYTMMA4RMTCDWEFJ3JANCNFSM6AAAAAARIYV774
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @desaijay315,
First of all, thank you for your interest in Artsy and this repository!
At Artsy, we have a long-held open source by default principle. However, that doesn't mean that all of our code is open source. When we keep services/repositories closed source, we have good reasons to do so. By choosing to open source many of our repositories, we gain a lot in return. It's easy for us to share our work with the larger community outside of Artsy. We can refer to specific PRs or code in our blog posts and podcast episodes. And we hope that it's an educational benefit for the larger community outside of Artsy. Interested engineers can browse the code freely. They can even clone the repository and run it locally but since this app relies on services that are closed source, the expectation is that when running Force locally, Force communicates with our hosted staging services.
As that's the case, we do not provide support (nor encourage) to run this application outside of Artsy in a staging/production environment. External use of this repository can be used for educational purposes or the occasional contribution but we don't support running this repository against any self-managed backend services. The documentation we've included so far is provided without guaranteed support from the team. We'll do our best to keep it updated but we unfortunately do not have the capacity to extend much support beyond what we've already documented.
As @erikdstock and @laurabeth suggest, if you're still interested in running this app locally against our staging services, I would recommend switching to one of our supported environments (even if that means running a Virtual Machine on your Windows setup). You might have better luck getting the app to boot up.
Thank you for understanding! 💜

Hello Devon,
Thank you so much for your response...
I appreciate that the team and company also thinks about the community
overall and that's what brought to me to the Artsy force repo..
I won't be using this to deploy somewhere outside..but checking this repo
only for educational purpose and would love to contribute once I get the
grasp on the project or starting to solve some small issues on the app
initially.
Regards,
JD
On Thu, 20 Oct 2022, 22:12 Devon Blandin, @.***> wrote:

Hi @desaijay315 https://github.com/desaijay315,
First of all, thank you for your interest in Artsy and this repository!
At Artsy, we have a long-held open source by default
https://github.com/artsy/README/blob/main/culture/engineering-principles.md#open-source-by-default
principle. However, that doesn't mean that all of our code is open source.
When we keep services/repositories closed source, we have good reasons to
do so. By choosing to open source many of our repositories, we gain a lot
in return. It's easy for us to share our work with the larger community
outside of Artsy. We can refer to specific PRs or code in our blog posts
and podcast episodes. And we hope that it's an educational benefit for the
larger community outside of Artsy. Interested engineers can browse the code
freely. They can even clone the repository and run it locally but since
this app relies on services that are closed source, the expectation is that
when running Force locally, Force communicates with our hosted staging
services.
As that's the case, we do not provide support (nor encourage) to run this
application outside of Artsy in a staging/production environment. External
use of this repository can be used for educational purposes or the
occasional contribution but we don't support running this repository
against any self-managed backend services. The documentation we've included
so far is provided without guaranteed support from the team. We'll do our
best to keep it updated but we unfortunately do not have the capacity to
extend much support beyond what we've already documented.
As @erikdstock https://github.com/erikdstock and @laurabeth
https://github.com/laurabeth suggest, if you're still interested in
running this app locally against our staging services, I would recommend
switching to one of our supported environments (even if that means running
a Virtual Machine on your Windows setup). You might have better luck
getting the app to boot up.
Thank you for understanding! 💜
—
Reply to this email directly, view it on GitHub
https://github.com/artsy/force/issues/11203#issuecomment-1285856651, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHKWYMB76VUMQDDQ3CUUXTWEFY6NANCNFSM6AAAAAARIYV774
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hello @erikdstock , @laurabeth  - I have now completed the setup on WSL. Thank you for your advice
1 Question - Do we have the cors enabled for localhost:4000?
Getting this error currently
Access to fetch at 'https://metaphysics-staging.artsy.net/v2' from origin 'http://localhost:4000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.```

@desaijay315 Can you provide your browser's unique report URL as shown here on whatismybrowser.com?
For example, here's mine: https://www.whatismybrowser.com/w/CSJ4YT8
By default, Force is configured to run on port 5000 so I'm surprised that Force booted up with port 4000. I'd try running yarn start again with no configuration changes if possible. For example, with a fresh clone, I was able to run the following:
$ cp .env.oss .env.shared
$ cp .env.example .env
$ yarn
$ yarn start
[Force] Building client-side development code...
[Force] Initializing cache...
[Force] Initializing artsyXapp...
[Force] Successfully fetched xapp token.
[Force] Booting on http://localhost:5000
Finished after 7.232 seconds.

Note that I already had Node 14.17.5 and Redis installed.
I saw the following error in the server logs, but it should be safe to ignore and not block the app from running:
[Force] Error creating feature flag service: Error: Unleash API "url" is required
    at new Unleash (/Users/devon/code/test/force/node_modules/unleash-client/src/unleash.ts:91:13)
    at initialize (/Users/devon/code/test/force/node_modules/unleash-client/src/index.ts:21:14)

Hi @desaijay315,
Looks like you were hitting one of our firewall block rules. Sorry about that!
I made a minor adjustment to that config and if you try again, that XAPP token fetch should work.

Okay Sure, I'll try running yarn start
On Fri, 21 Oct 2022, 14:47 devon blandin, @.***> wrote:

Hi @desaijay315 https://github.com/desaijay315,
Looks like you were hitting one of our firewall block rules. Sorry about
that!
I made a minor adjustment to that config and if you try again, that XAPP
token fetch should work.
—
Reply to this email directly, view it on GitHub
https://github.com/artsy/force/issues/11203#issuecomment-1286689021, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHKWYJ22KGSKX455AZNCLTWEJNTPANCNFSM6AAAAAARIYV774
.
You are receiving this because you were mentioned.Message ID:
@.***>

Looks like you were hitting one of our firewall block rules. Sorry about that!

Thank you so much for looking into this - Works fine now :)

Glad to hear that!
I'll go ahead and close this issue and thanks again for your interest! 💯

Thank you so much @dblandin. I really appreciate your help
Can you also redirect me to the list of issues? It seems that Issues are tracked within Jira dashboard.
How can I get access to the same? I will see if I can pick some of the issues, starting something with low severity, may be :)


[FEATURE] Add DoRA: Weight-Decomposed Low-Rank Adaptation

🚀 Feature
Add support for Weight-Decomposed Low-Rank Adaptation (DoRA).
"DoRA decomposes the pre-trained weight into two components, magnitude and direction, for fine-tuning, specifically employing LoRA for directional updates to efficiently minimize the number of trainable parameters. "
Paper: https://arxiv.org/abs/2402.09353
Implementation in Peft: https://github.com/huggingface/peft/releases/tag/v0.9.0
Motivation
Authors claim that DoRA is more efficient w.r.t. param count as LoRA and achieves better results throughout all tests.

I'd like to bump this... seems DoRA yields accuracy basically on par with full fine tuning.


Dependency path inet.af/peercred no longer resolves

Hi there 👋
Apparently the inet.af domain is no longer valid. Seems referencing the module path is now the correct way of bringing in dependencies. Hence, we're seeing the following issue trying to build with an Athenz dependency:
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>unrecognized import path "inet.af/peercred": https fetch: Get "https://inet.af/peercred?go-get=1": dial tcp: lookup inet.af on <IP_ADDRESS>:53: no such host

See:

https://github.com/tailscale/tailscale/pull/11132
https://github.com/tailscale/peercred/commit/b535050b2aa4bdee850843970fb63ee0c1c4bec7

Thanks @gregfurman . We'll make the move to github.com module. Since you referenced 1.10.x, are you using that release in some form as opposed to 1.11.x or 1.12.x releases?


FAQ in docs

Things to add to the FAQ:

[ ] Discrepancy, minor mistake, and inconsistency in the documentation and between similar functionnality: https://github.com/icebob/vue-form-generator/issues/145#issuecomment-288014329
[ ] Unknown custom element: #222

Might be easier to create a "documentation: faq" label and apply that to the issues directly. I don't have permission to create labels, afaik.


:lady_beetle: Not possible to use values other than predefined values for VMs in flight

In the console plugin for MTV the available settings for maximum VMs in flight is 2,10,20, and more.
I would like to at least have 1 and 5 as well to reduce load on our demo environment.
Version: MTV 2.5.6 on OCP 4.15.9

another option, a open text input a user can enter the number manually

addressed by https://github.com/kubev2v/forklift-console-plugin/pull/1164


simplify update_user_me

The problem is that the idea is that a user can only update his/her own password, full_name and email.
By setting the body to UserUpdate that would allow (or at least give the impression that it would allow) the user to also update is_superuser, is_active, etc.
So I'm gonna pass on this one. But thanks for your interest!


Add more detailed documentation/demo about default behavior after login

When user submits the login, the submit button is disabled to prevent another attempt before the login is processed.
Add:

Documentation describing the behavior
Demo with details with what the developer should do in order to re-enable login

For the documentation part, the behavior is described in AbstractLogin.
/**
 * Abstract component for the {@code <vaadin-login-overlay>} and
 * {@code <vaadin-login-form>} components.
 * On {@link LoginForm.LoginEvent} component becomes disabled.
 * Disabled component stops to process login events, however
 * the {@link LoginForm.ForgotPasswordEvent} event is processed anyway.
 * To enable use the {@link com.vaadin.flow.component.HasEnabled#setEnabled(boolean)} method.
 * Setting error {@link #setError(boolean)} true makes component automatically enabled for
 * the next login attempt.
*/

Is this enough? Should this be replicated in the subclasses? How about a simple @see AbstractLogin in each subclass?


Post site build checks to verify links are not broken

The build should not be deployed if we find broken links. There are tools that should be used to detect broken links in the documentation built and stop automatic deployment if something is broken and notify teams via slack and email.

Obsolete.


[TST, DOC, ENH]: Update Python versions

Update docs to reflect 3.6+ is supported
Test CI with Python 3.9 and bump actions versions
Add python_requires to help pip install the right version for the user
Add Trove classifier metadata for the Python versions for display on PyPI
Upgrade Python syntax with https://github.com/asottile/pyupgrade (this also has a pre-commit hook available)

Many thanks for this improvement @hugovk and apologies for missing the PR earlier!


refactor(admin): move operations to their own classes

Fixes NODE-1897

Note that some of these operations use ExecuteDbAdminCommandOperation. I'll be sure to refactor them to use @mbroadst's updated version of CommandOperation after #1974 is merged.


No lightning ignition in Log. 2.4.1

Scrpple 2.4.1
Lightning Ignitions do not appear to be stored in the ignitions log. I have lightning in the events log, killing trees, and all that. Yet each lightning ignition in the ignition log is zero.  Please see the images of logs.
Thank you,
-Zachary

Yes

Z, I found a bug, fixed that.  Also expanded IgnitionLog to include both AttemptedNumIgnitions and Actual.  This may or may not solve the problem.

Okay I should have the testing done by the end of the week

In the newest version, the new AttemptedNumIgnitions appear to always be zero, even if the Actual is a number.

In line 665 of Plugin.cs
int BinomDraw = new Random().Next(0, 2);
double alpha = Math.Pow(Math.E, (binomb0 + (binomb1 * fireWeatherIndex)));
double zerosprob = alpha / (alpha + 1);
if (BinomDraw <= zerosprob)
BinomDraw may need to be a decimal not an integer as zeroprob is a probability between(0,1). If Binomdraw is just either 0 or 1, then that draw would be the determinate, not the zero inflated portion. I may have that wrong, but I think that might be the discrepancy

Zachary,
A rather obvious error.  Try installer 2.4.3.


Update README.md

Elasticsearch is not a camel-cased name.

Whoops I need to update this with some changes to other files too. Pending...

Ok, good to go now!

@jasonkuhrt Great catch. Thanks-.

@pilwon Cheers.


Missing images/wavedrom/instruction_formats.adoc

At aa50390
%  asciidoctor-pdf -r asciidoctor-diagram -r asciidoctor-mathematical -a mathematical-format=svg -r asciidoctor-bibtex book_header.adoc -a pdf-style=resources/themes/risc-v_spec-pdf.yml -a pdf-fontsdir=resources/fonts --trace
asciidoctor: ERROR: tables_graphics.adoc: line 207: include file not found: /work/jscheid/src/gh/riscv/docs-templates/images/wavedrom/instruction_formats.adoc

This is an issue again. Looking into this.

Note, also missing some some fonts, wavedrom_edit.adoc (referenced in book_header.adoc), and the risc-v_spec-pdf.yml theme.

Turns out this was from some cleanup that was done recently. We will update this so that the build succeeds soon.


Add initial OpenSSL CryptoEngine implementation and key/cert handling

@havardpe please review 🦄✨
@bjorncs FYI
The current implementation is known to be sub-optimal due to requiring
memory copies in and out of OpenSSL's working BIOs for every encode
and decode. Codec design is also up for change, depending on how
well it fits with crypto socket integration.

🏆

Re: vespalib::string vs std::string I think we should transition to std::string (and std::string_view) in most places, but we cannot do that as long as we need to support ye olde GCC ABI with internal refcounting. Only downside with the new ABI std::string is that the max size of the small string optimization is implementation defined instead of being something we control. I believe GCC only has 16 bytes as opposed to vespalib's 48.
Will change API strings in this PR to vespalib strings to make things more unified.

on the string topic: I prefer vespalib::string{,ref} to distinguish it from std::string

@havardpe PTAL 2.0, now with more PTAL.


fix: removing static type checking for query constructs

This reverts commit 342ea364b75aa128f7642f18809a7c29a872e321.
Describe your changes
How best to test these changes
Issue ticket number and link

Codecov Report
Patch coverage: 82.07% and project coverage change: -0.48 :warning:

Comparison is base (1d7ae2e) 89.84% compared to head (037232e) 89.36%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #284      +/-   ##
==========================================
- Coverage   89.84%   89.36%   -0.48%
==========================================
  Files          29       29
  Lines        5149     5183      +34
  Branches      600      607       +7
==========================================
+ Hits         4626     4632       +6
- Misses        522      550      +28
  Partials        1        1

Impacted Files
Coverage Δ

src/search/search-index.ts
71.02% <58.97%> (-2.26%)
:arrow_down:

src/utility.ts
94.63% <86.36%> (-2.01%)
:arrow_down:

src/collection.ts
97.25% <100.00%> (ø)

src/search/query.ts
100.00% <100.00%> (ø)

src/types.ts
90.79% <100.00%> (+0.07%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Satellite Reverse Engineering #2

Reverse Engineer A Satellite Codebase
CDH member @whatdoes3plus1equalsto has found some open-source satellite projects that we could benefit from reverse engineering and analysis of their code bases. There are three parts to this task that I will list here.

Reverse engineer the given satellite codebase:
Take a deep dive into the satellite's codebase. Try to determine what type of code they have written things like "how do they control peripherals?", "Are they using a real-time operating system? If they are what type of tasks do they have and how are they organized" things like that. Also, take extra care to evaluate their error correction code like CRC checks on their memory and other corruption preventative measures.

Identify modules that could improve our design:
Now that you have your footing in the codebase and how it operates, try to identify some useful parts that are missing from our codebase that we could implement in our satellite. Once you find some bring it up with @GrahamDrive or @DaighB and we can discuss how it could be used.

Finally some coding!:
Now that you know what you want to add to the satellite you can try making a test project for a proof of concept. Go ahead and create a brand new project for your dev board and try to implement the given feature you have decided on. Have fun with it play around and add your ideas and flair.

Show off your work:
Now that you have completed the code and tested it you can show it off in a meeting!

University of Patras
This task will be regarding the UPSat CubeSat from the University of Patras in Greece. It is completely open source and good for it uses a stm32 microprocessor, its codebase can be found here. UpSat also has its own Wikipedia page that could have a ton of valuable information you could use the link to it is here.
As always if you have any questions don't hesitate to ask!

I did some research on this on my own, and I thought I'd document what I've gathered thus far.
High-Level Tidbits

The link Graham provided brings you to the On-Board-Computer repository, but there is also

an ADCS repo found here,
a Comms repo found here, and
a Power (or as they call it, Electrical Power System) repo here
There is another repo called ECSS Services which appears to contain lots of services and utilities that each subsystem uses here.

They are using UART to communicate between subsystems

The ADCS repo actually contains a B-Dot detumbling algorithm and a pointing algorithm using a sun-sensor here

The On-Board-Computer (OBC)
Here are some points I've gathered about their On-Board-Computer (OBC):

They are using RTOS with CMSIS, and a full FAT32 filesystem. The filesystem goes under the name mass_storage and is defined in the ECSS Services repo.
The cubeMX/ subfolder contains two STM32 projects: disco/ and obc/. disco/ appears to be some sort of testing ground for various things. obc/ appears to be the flight-ready code.
The only file of interest is really the main.c file. Every other file appears to be part of a third-party library.
obc_data is a giant struct containing all the state of OBC. It's NOT defined in the OBC repo though. Instead it's defined in the ECSS repo here.
Similar to TSAT, UPSAT is using task scheduling with RTOS to perform all of its functions. There are five separate threads/tasks:

UART_task (function definition): This task listens for incoming messages on the UART bus. There are four different message queues: EPS, COMMS, ADCS, & DBG. These queues are checked in an infinite loop, and it appears as though OBC is just relaying the messages back to UART, possibly so that the subsystems can communicate between one another.
HK_task (function definition): "HK" actually stands for Housekeeping (not the best naming scheme tbh) and this is another service defined in the ECSS repo. At a high level, this task simply initialises the Housekeeping service with hk_INIT defined in ECSS here, and then calls hk_SCH defined here in an infinite loop. From a surface viewing, it's really hard to tell what HK is actually doing. More research may be needed to make sense of it.
IDLE_task (function definition: Again, it's not clear what this one is doing. More research is required.
SU_SCH (function definition): Same as above
sche_se_sch (function definition): Calls cross_schedules in an infinite loop, which is part of the scheduling_service service in ECSS. It's again not clear what it's doing, but it may have to do with executing "APIDs" whatever those are.

I'll probably be investigating their error handling practices next, so I'll post my findings when I do.

I did some research on their error handling practices. I mostly looked at the ADCS and ECSS repositories since it actually looks like the OBC repo doesn't contain any error handling at all!
Here's what I jotted down:
Handling Errors

They don't do anything with the HAL Error_Handler function, which might make sense since it's not clear what the right corrective action might be if HAL throws an error. It does seem a little unfortunate that nothing is logged though.

/**
  * @brief  This function is executed in case of error occurrence.
  * @param  None
  * @retval None
  */
void Error_Handler(void)
{
  /* USER CODE BEGIN Error_Handler */
  /* User can add his own implementation to report the HAL error return state */
  while(1)
  {
  }
  /* USER CODE END Error_Handler */
}

They also don't modify the assert_failed function which gets called by HAL when a parameter to a function is invalid. Again, no logging is performed for such occurences

/**
   * @brief Reports the name of the source file and the source line number
   * where the assert_param error has occurred.
   * @param file: pointer to the source file name
   * @param line: assert_param error line source number
   * @retval None
   */
void assert_failed(uint8_t* file, uint32_t line)
{
  /* USER CODE BEGIN 6 */
  /* User can add his own implementation to report the file name and line number,
    ex: printf("Wrong parameters value: file %s on line %d\r\n", file, line) */
  /* USER CODE END 6 */

}

SAT_returnState
Defined here in ECSS.
SAT_returnState is an enum type for errors totalling at 57 possible error values (including SATR_OK). It's not the only enum for errors, but it appears to be the one that's used within the ECSS library.
adcs_error_status
Defined here in ADCS.
adcs_error_status is the enum type for ADCS errors. There are 10 total possible values. The errors don't appear to be particularly specific.
error_handler
Defined here in ADCS.
This gets called in the program's main loop once for each cycle of the TIM7 timer. This is accomplished by setting ADCS_event_period_status to TIMED_EVENT_NOT_SERVICED in the ISR for TIM7, and then checking every iteration of the while loop if it's set. Once it is set and the if statement is triggered, the flag gets reset at the end after error_handler is called.
int main(void) {

	// ... init code ..

    while (1) {
        /* GPS update */
        error_status = update_gps(&gps_state);

        /* Control loop runs at 68ms, interrupt runs every ~1.2s, WDG at ~2.4s */
        if (ADCS_event_period_status == TIMED_EVENT_NOT_SERVICED) {

			// ... code ...

			/* Update flag */
            ADCS_event_period_status = TIMED_EVENT_SERVICED; // reset condition to false.

            /* Software error handler runs for actuator and sensor 230ms*/
            adcs_sysview_print();

            error_handler(error_status);
            error_status = ERROR_OK;
        }
	}

The error handler function performs different operations based on the value of error_status.
error_propagation
Defined here in ADCS.
This function takes in a parameter current_error which is of type adcs_error_status.

if current_error is ERROR_OK (i.e. no error is passed), then the function defaults to returning error_status (which is ERROR_OK by default at the start of the program).
otherwise, current_error is not ERROR_OK and that is returned instead.
This creates a behaviour where error_status acts as a second-priority error code in case the calling function was successful.

In the below code sequence found in the main function, you'll see that if any one of these function calls fails, the rest will also fail with the same error code.
error_status = init_mem(); // let's say this fails with ERROR_FLASH
error_status = increment_boot_counter(); // then this will return ERROR_FLASH too (even if the operation was successful)
error_status = init_obc_communication(adcs_boot_cnt); // same as above

Note that in the second line, if increment_boot_counter fails with something else, that error code will become the new secondary error code. This actually means errors can get overwritten and lost, and they won't be rectified when error_handler eventually gets called. This is a pretty bad way to deal with errors.
Bugs, Bugs, Everywhere
What's humerous is there is actually a bug with increment_boot_counter. There is a case where it returns FLASH_ERROR when it should return ERROR_FLASH. This is an example of why having a good naming scheme is important.
FLASH_ERROR is defined in adcs_flash.h and is NOT part of the adcs_error_status enum. See below:
typedef enum {
    FLASH_ERROR = 0, FLASH_NORMAL
} flash_status;

And of course the code still compiles because C allows you to mix enums even though that is completely dangerous to do.
Honestly, the code in UPSAT is really bad. It's full of inconsistent naming schemes and mistakes. It's hard to believe this code made it to space.

I didn't realize there was so much information in their Git repository. The FAT system is particularly intriguing. I've been considering whether we should use one or not; although I don't have experience with them in embedded systems, I assume it would make our work significantly easier though.
Thanks for this fantastic deep dive, Logan!

UPSAT appears to be storing a lot of different types of data (I believe I even saw some scripts being loaded), whereas TSAT just needs to store telemetry data. So I think it's acceptable if not desirable that we don't have one.


How to improve Leaflet.VectorTiles for flutter ?

Hello author flutter map
I thanks you create widget map is very good,
But raster tiles is blurred on mobile , you can update read verter tile same leaftlet.

I can't reproduce this issue, sorry


gitbucket does correctly use --port parameter

Tested on 3.7, launch gitbucket via java -jar gitbucket.war --port=9090
Open your browser on http://localhost:9090.
The gitbucket homepage is rendered with many errors because most URLs use a bad port number of 8080.

review config file:   Base URL param
check whether the parameters are correct

@McFoggy Did you set http://localhost:8080 as base url as @pinghe mentioned?

Sorry you're right I didn't changed it. I launched a second instance to test upgrade to 3.7 and didn't thought I need to change that settings.
Sorry for disturbance.


Kate yoak/patch 1

What does this PR do?
Documentation change with a note for source_type_name

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

It looks like this is based on an old commit, and includes some unrelated commits?  I suspect that a git rebase and a force-push is required.

Thanks for this!  I'm going to close this as stale, but do feel free to open a new PR based on an updated main branch and with a signed CLA.


"wrong username or password" when they are true / on all builds

2015-01-01 06:42:51,332 - PixivUtil20141216 - INFO - ###############################################################
2015-01-01 06:42:51,332 - PixivUtil20141216 - INFO - Starting...
2015-01-01 06:42:51,335 - PixivUtil20141216 - INFO - Setting log level to: DEBUG
2015-01-01 06:42:51,335 - PixivUtil20141216 - INFO - No default cookie jar available, creating...
2015-01-01 06:42:51,339 - PixivUtil20141216 - INFO - Only process member where day last updated >= 7
2015-01-01 06:42:51,339 - PixivUtil20141216 - INFO - Using Username: qqroo
2015-01-01 06:42:51,339 - PixivUtil20141216 - INFO - Log in using form.
2015-01-01 06:42:57,039 - PixivUtil20141216 - INFO - Logging in, return url: https://www.secure.pixiv.net/login.php
2015-01-01 06:42:57,075 - PixivUtil20141216 - INFO - Wrong username or password.
they honestly true ;_;

Try to log in using browser? Usually this is because your pc date/time is not correct.
I tried to log in using the latest version and I can download just fine.
If still cannot login, try the cookie method in readme.txt -> FAQ -> Section C -> Q3

login successful. thank you!


[CDC][SPI] added synchronizer between sys_clk and spi_clk (option 2 + enhanced pulse_stretcher)

This PR is for another discussion on the short pulse issue in https://github.com/lowRISC/opentitan/pull/13586.
https://github.com/lowRISC/opentitan/pull/13586/ may not support a short pulse of csb_i where spi_clk is much faster than sys_clk, so csb_rst_toggle_spi_clk = 0 pulse may not be detected by sys_clk. csb_rst_toggle_spi_clk becomes 0 when csb_i is de-asserted.
This fix is to make csb_rst_toggle_spi_clk = 0 by another ack signal from sys_clk just after csb_pulse is generated in sys_clk. So, csb_rst_toggle_spi_clk is supposed to have enough low pulse width before csb_i is de-asserted.
This transaction is checked by ASSERTION.
We can choose either https://github.com/lowRISC/opentitan/pull/13586 + another ASSERTION or this approach.
Signed-off-by: Joshua Park<EMAIL_ADDRESS>

@jeoongp i think i understand waht this is doing.
But just to confirm, this means after clk_csb_pos_pulse_stretch asserts, you effectively always reset its input back to 0 (ahead of tpm_rst_n releasing, is that right?

@jeoongp i think i understand waht this is doing. But just to confirm, this means after clk_csb_pos_pulse_stretch asserts, you effectively always reset its input back to 0 (ahead of tpm_rst_n releasing, is that right?

Yeah, it's right.

a couple of minor comments on the static tpm_en, but otherwise this looks good to me.
It might be good to explain this to @weicaiyang and we can probably add some tests that really stress the clock ratio and pulse width timing to make sure this does what we think it should

a couple of minor comments on the static tpm_en, but otherwise this looks good to me. It might be good to explain this to @weicaiyang and we can probably add some tests that really stress the clock ratio and pulse width timing to make sure this does what we think it should

I agree! BTW, where can we find a spec that describes this timing info?

wait sorry @jeoongp did we still have concerns on the signal prefixes? I still see some signals that switch from spi_clk to sys suddenly. I can't remember if we discussed that in this PR or another.

wait sorry @jeoongp did we still have concerns on the signal prefixes? I still see some signals that switch from spi_clk to sys suddenly. I can't remember if we discussed that in this PR or another.

I fixed signal prefix issues one month ago but if you still find a naming issue, let me know.
For signals that switch from spi_clk to sys suddenly, did you find another CDC issue?

wait sorry @jeoongp did we still have concerns on the signal prefixes? I still see some signals that switch from spi_clk to sys suddenly. I can't remember if we discussed that in this PR or another.

I fixed signal prefix issues one month ago but if you still find a naming issue, let me know. For signals that switch from spi_clk to sys suddenly, did you find another CDC issue?

o no, there's no cdc issue, just a style thing. Let me point it out in the code.

ah looks like ascentlint failed in your latest push, you probably want to try to run that locally to see what the issue is.

ah looks like ascentlint failed in your latest push, you probably want to try to run that locally to see what the issue is.

Thanks! They seem to be in the waiver list. Let me review and adjust the regr exp.

ah looks like ascentlint failed in your latest push, you probably want to try to run that locally to see what the issue is.

Thanks! They seem to be in the waiver list. Let me review and adjust the regr exp. Just I'm curious of how these lint errors are detected now by renaming one signal..

When I run ascentlint on spi_device locally, it's passing. Can you let me know what the lint errors are in the log? I am not able to access it.

hmmm.... i wonder if this was an enviornment thing.
Let me help you re-run first.

were you able to find out what lint is complaining about?
On Thu, Sep 1, 2022 at 10:21 AM jeoongp @.***> wrote:

@.**** commented on this pull request.
In hw/ip/spi_device/rtl/spi_tpm.sv
https://github.com/lowRISC/opentitan/pull/13859#discussion_r960918039:

 for (int unsigned i = 0 ; i < NumLocality ; i++) begin

   sck_active_locality[i] <=

     sys_tpm_reg.access[AccessRegSize*i + ActiveLocalityBitPos];

 sys_clk_tpm_cfg <= '{default: '0};

 sys_clk_tpm_reg <= '{default: '0};

 sys_clk_tpm_en <= 1'b0;

end else begin

 if (sys_csb_pulse_stretch) begin

   sys_clk_tpm_cfg <= sys_tpm_cfg;

   sys_clk_tpm_reg <= sys_tpm_reg;

   for (int unsigned i = 0 ; i < NumLocality ; i++) begin

     sys_active_locality[i] <=

       sys_tpm_reg.access[AccessRegSize*i + ActiveLocalityBitPos];

   end

 end

 if (spi_clk_csb_pulse) begin

Thanks. I updated RTL to simply use 2 flops in spi_clk
—
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/13859#discussion_r960918039,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSQOE257IATP72SLOX3V4DQX7ANCNFSM54XTNTGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

were you able to find out what lint is complaining about?
…
On Thu, Sep 1, 2022 at 10:21 AM jeoongp @.> wrote: @.* commented on this pull request. ------------------------------ In hw/ip/spi_device/rtl/spi_tpm.sv <#13859 (comment)>: > - for (int unsigned i = 0 ; i < NumLocality ; i++) begin - sck_active_locality[i] <= - sys_tpm_reg.access[AccessRegSizei + ActiveLocalityBitPos]; + sys_clk_tpm_cfg <= '{default: '0}; + sys_clk_tpm_reg <= '{default: '0}; + sys_clk_tpm_en <= 1'b0; + end else begin + if (sys_csb_pulse_stretch) begin + sys_clk_tpm_cfg <= sys_tpm_cfg; + sys_clk_tpm_reg <= sys_tpm_reg; + for (int unsigned i = 0 ; i < NumLocality ; i++) begin + sys_active_locality[i] <= + sys_tpm_reg.access[AccessRegSizei + ActiveLocalityBitPos]; + end + end + if (spi_clk_csb_pulse) begin Thanks. I updated RTL to simply use 2 flops in spi_clk — Reply to this email directly, view it on GitHub <#13859 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH2RSQOE257IATP72SLOX3V4DQX7ANCNFSM54XTNTGQ . You are receiving this because you were mentioned.Message ID: @.***>

No.. lint on spi_device is passing locally as I ran ./util/dvsim/dvsim.py hw/top_earlgrey/lint/top_earlgrey_lint_cfgs.hjson -t ascentlint --select-cfgs spi_device. Did you mean running lint over all blocks like lint regression?

were you able to find out what lint is complaining about?
…
On Thu, Sep 1, 2022 at 10:21 AM jeoongp @.> wrote<EMAIL_ADDRESS>commented on this pull request. ------------------------------ In hw/ip/spi_device/rtl/spi_tpm.sv <#13859 (comment)>: > - for (int unsigned i = 0 ; i < NumLocality ; i++) begin - sck_active_locality[i] <= - sys_tpm_reg.access[AccessRegSize_i + ActiveLocalityBitPos]; + sys_clk_tpm_cfg <= '{default: '0}; + sys_clk_tpm_reg <= '{default: '0}; + sys_clk_tpm_en <= 1'b0; + end else begin + if (sys_csb_pulse_stretch) begin + sys_clk_tpm_cfg <= sys_tpm_cfg; + sys_clk_tpm_reg <= sys_tpm_reg; + for (int unsigned i = 0 ; i < NumLocality ; i++) begin + sys_active_locality[i] <= + sys_tpm_reg.access[AccessRegSize_i + ActiveLocalityBitPos]; + end + end + if (spi_clk_csb_pulse) begin Thanks. I updated RTL to simply use 2 flops in spi_clk — Reply to this email directly, view it on GitHub <#13859 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH2RSQOE257IATP72SLOX3V4DQX7ANCNFSM54XTNTGQ . You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>
No.. lint on spi_device is passing locally as I ran ./util/dvsim/dvsim.py hw/top_earlgrey/lint/top_earlgrey_lint_cfgs.hjson -t ascentlint --select-cfgs spi_device. Did you mean running lint over all blocks like lint regression?

yeah that's right.
could you try with --select-cfgs chip_earlgrey_asic? let's see if anything pops out.
let me see if the latest logs are more helpful.

Oh I see. I found 22 errors when I ran on top_earlgrey. Most of them are in ibex. Let me also run on chip_earlgrey_asic.

Oh I see. I found 22 errors when I ran on top_earlgrey. Most of them are in ibex. Let me also run on chip_earlgrey_asic.

wait.. if they're in ibex, and you're able to run top_earlgrey, that probably means your database is outdated (in the latest top_earlgrey is no longer an option).  Can you rebase on master once more?

Oh I see. I found 22 errors when I ran on top_earlgrey. Most of them are in ibex. Let me also run on chip_earlgrey_asic.

wait.. if they're in ibex, and you're able to run top_earlgrey, that probably means your database is outdated (in the latest top_earlgrey is no longer an option). Can you rebase on master once more?

They are gone after rebase. Thanks!

@jeoongp should we merge once CI passes?

@jeoongp should we merge once CI passes?

I will run spi_device regression tonight and will let you know tomorrow

spi_device regression results look good.
I think we can merge.


[TOOLS-4458] Create a Cubrid plugin based on generic

http://jira.cubrid.org/browse/TOOLS-4458

refactoring cubrid plugin
create cubrid, cubrid UI plugin based on generic plugin
register new added plugins

Dear @kisoo-han,
There were some issues with many commits and messages in the previous pull request. I just organized it to make it look clean, that's why I have created a new above pull request here.

@longhaseng52 ,
I see!


Incorrect Description for Servo Calibration

"Retracting servos fully..." and "retracting them fully..." I'm pretty sure one of those sentences should have "extending" in them, but I dunno which one.

https://www.youtube.com/watch?v=2yF-SJcg3zQ&t=855s
Seems like FULLY EXTENDED should be "can't close hand" and FULLY RECTRACTED should be "hand has complete freedom of motion"

yep, gonna fix that now, thanks for spotting it!


[BUG] Handle Marqo-OS errors better

Describe the bug
In the process of translating a Marqo-OS error into a more understandable one for users,  a parsing error can occur which is given to users as a 500
To Reproduce
Steps to reproduce the behavior:
We can probably reproduce via mocking

Mock a request to Marqo-os
Make it return an unusually formatted JSON error message
See error

Expected behavior
Even if there is an error parsing the Marqo-OS error, it should handle this and return users an appropriate error message (perhaps forwarding the message/status from Marqo-OS

This is the associated Marqo error logs:
2023-02-13T03:18:05.950542854Z INFO:     <IP_ADDRESS>:49072 - "POST /indexes/marqo-simplewiki-demo-all/search?&device=cpu HTTP/1.1" 500 Internal Server Error
2023-02-13T03:18:05.960026414Z   warnings.warn(
2023-02-13T03:18:05.960030637Z ERROR:    Exception in ASGI application
2023-02-13T03:18:05.960035082Z Traceback (most recent call last):
2023-02-13T03:18:05.960039483Z   File "/app/src/marqo/_httprequests.py", line 134, in __validate
2023-02-13T03:18:05.960044481Z     request.raise_for_status()
2023-02-13T03:18:05.960048853Z   File "/usr/local/lib/python3.8/dist-packages/requests/models.py", line 1021, in raise_for_status
2023-02-13T03:18:05.960062108Z     raise HTTPError(http_error_msg, response=self)
2023-02-13T03:18:05.960066412Z requests.exceptions.HTTPError: 401 Client Error: UNAUTHORIZED for url: https://.../_msearch
2023-02-13T03:18:05.960075767Z During handling of the above exception, another exception occurred:
2023-02-13T03:18:05.960084137Z Traceback (most recent call last):
2023-02-13T03:18:05.960088264Z   File "/usr/local/lib/python3.8/dist-packages/uvicorn/protocols/http/httptools_impl.py", line 419, in run_asgi
2023-02-13T03:18:05.960092712Z     result = await app(  # type: ignore[func-returns-value]
2023-02-13T03:18:05.960097493Z   File "/usr/local/lib/python3.8/dist-packages/uvicorn/middleware/proxy_headers.py", line 78, in __call__
2023-02-13T03:18:05.960102355Z     return await self.app(scope, receive, send)
2023-02-13T03:18:05.960115464Z   File "/usr/local/lib/python3.8/dist-packages/fastapi/applications.py", line
---- Starlette and FastAPI error handling stuff...
2023-02-13T03:18:05.960240557Z   File "/app/src/marqo/tensor_search/./api.py", line 114, in search
2023-02-13T03:18:05.960244530Z     return tensor_search.search(
2023-02-13T03:18:05.960249268Z   File "/app/src/marqo/tensor_search/tensor_search.py", line 836, in search
2023-02-13T03:18:05.960253688Z     search_result = _vector_text_search(
2023-02-13T03:18:05.960258145Z   File "/app/src/marqo/tensor_search/tensor_search.py", line 1164, in _vector_text_search
2023-02-13T03:18:05.960262589Z     response = HttpRequests(config).get(path=F"{index_name}/_msearch", body=utils.dicts_to_jsonl(body))
2023-02-13T03:18:05.960267393Z   File "/app/src/marqo/_httprequests.py", line 93, in get
2023-02-13T03:18:05.960272166Z     res = self.send_request(requests.get, path=path, body=body, content_type=content_type)
2023-02-13T03:18:05.960276852Z   File "/app/src/marqo/_httprequests.py", line 80, in send_request
2023-02-13T03:18:05.960281211Z     return self.__validate(response)
2023-02-13T03:18:05.960285638Z   File "/app/src/marqo/_httprequests.py", line 137, in __validate
2023-02-13T03:18:05.960290584Z     convert_to_marqo_web_error_and_raise(response=request, err=err)
2023-02-13T03:18:05.960295220Z   File "/app/src/marqo/_httprequests.py", line 159, in convert_to_marqo_web_error_and_raise
2023-02-13T03:18:05.960300381Z     open_search_error_type = response_dict["error"]["type"]
2023-02-13T03:18:05.960305358Z TypeError: string indices must be integers

Probably as simple as catching Type errors, along with key errors


Improve the format of README

Improve the readability of the Examples section.

I'm closing this PR since the changes are not applicable anymore because we don't use the rst format.


Merge pull request #1 from Susmita-Dey/main

pull

What's this?
__
  Summary: :question: I have a question

@rani620 explain ur work plz?

Closing this as invalid
__
  Tags: Brittle


Website-Responsiveness

It will improve the responsiveness of your website
please assign me for this issue
I am a gssco'21 participant and wants to contribute on this project

Hi @Avishake007, First of all, thank you so much for taking out the time to create this issue.
Actually, currently, we are inclined towards adding more features, and due to that there are a lot of undergoing UI changes, so It would be better if we once finish that stuff, and then we are good to go with the responsiveness of this website.

Okay I will work on it later

Hi i am a gssoc participant , can i work on this issue?

Hi i am a gssoc participant , can i work on this issue?

Sorry @simranbhalla3, but this issue is already on hold.

Can I work on this issue?

I would like to work on this, will you assign me?


Config Server returned a NON-JSON body while generating value for '/bosh/cfcr/tls-kubelet' with type 'certificate'

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

What happened:
while deploying kubo i am getting the following error.
Task 7 | 09:48:58 | Preparing deployment: Preparing deployment (00:00:02)
L Error: Config Server returned a NON-JSON body while generating value for '/bosh/cfcr/tls-kubelet' with type 'certificate'
Task 7 | 09:49:00 | Error: Config Server returned a NON-JSON body while generating value for '/bosh/cfcr/tls-kubelet' with type 'certificate'
Task 7 Started  Wed Sep 19 09:48:58 UTC 2018
Task 7 Finished Wed Sep 19 09:49:00 UTC 2018
Task 7 Duration 00:00:02
Task 7 error
Updating deployment:
Expected task '7' to succeed but state is 'error'
Exit code 1
What you expected to happen:
successful deployment of kubo on openstack
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Deployment Info (bosh -d <deployment> deployment):
Environment Info (bosh -e <environment> environment):
Name      bosh
UUID      261a5d5d-0dc0-4d47-9db4-bc0e9ee4b603
Version   266.4.0 (00000000)
CPI       openstack_cpi
Features  compiled_package_cache: disabled
config_server: enabled
dns: disabled
snapshots: disabled
User      admin

Succeeded

Kubernetes version (kubectl version): 1.11.2
Cloud provider (e.g. aws, gcp, vsphere): openstack

Hi @sdinesh116 - can you please provide the command you were ran when you encountered this error?

I used the following command to deploy kubo on Openstack
bosh deploy -d cfcr cfcr.yml
I have generated the cfcr.yml using the generate_kubo_manifest script.

Hi @sdinesh116 - unfortunately our generate_kubo_manifest and deploy_k8s scripts are deprecated.  Please instead follow the instructions here: https://github.com/cloudfoundry-incubator/kubo-release/blob/master/README.md


Report Grids: measurable hierarchy cols cause timeout on grids over app-groups

Description
Grid unable to load with measurable hierarchy cols added, usually times out.
Waltz Version
No response
Steps to Reproduce

...
Expected Result
No response
Actual Result
No response

This seems to have fixed by updating the dbms table statistics / rebuilding indexes.


Update ios-install.md

Changed the wordings as it is connect VPN and Not establish VPN anymore

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/8583


Default converter for Array types does not work with objects as elements

Description

Default converter for Array types does not work with objects as elements.
The default Array Converter converts its elements to strings by simple casting. The documentation (https://lit-element.polymer-project.org/guide/properties) says however:
For Objects and Arrays, when the property is:

null or undefined, remove the attribute.
Defined and not null, set the attribute value to JSON.stringify(propertyValue).

Either the documentation should be changed, or the behavior changed to match the documentation.
Live Demo
https://stackblitz.com/edit/lit-element-example-a37cfp
Steps to Reproduce

Create an element with a property of type Array
Include the element in another element, setting the corresponding attribute to an Array with objects as elements:

html`<my-element my-attr=${ [ { key: 'val') } ] }></my-element>`

This renders as <my-element my-attr="[object Object]"></my-element>
The attribute cannot be deserialized

Expected Results
The attribute should be converted to JSON as specified in the documentation.
<my-element my-attr='[ { "key": "val" } ]'></my-element>
Actual Results
<my-element my-attr="[object Object]"></my-element>
Browsers Affected

[X] Chrome
[X] Firefox
[x] Edge
[x] Safari 11
[x] Safari 10
[x] IE 11

Versions

lit-element: 0.7.1
webcomponents: v2.2.3

I also faced the same issue, actually the library should support the objects as elements, Workaround as of now is to stringify your whole array and pass it  <shopping-list-ul items="${JSON.stringify(this.items)}">

i find it easier to use these as properties. Very little value comes from attributes for complex objects. Properties are also faster.
<shopping-list-ul .items="${this.items}"></shopping-list-ul>

@arasmus8 in your example you're also mapping complexList to complex-list attribute. Polymer lib did that, but afaik, lit-element does not do that translation

I believe this is working as intended. Let me explain by going back to basics. Elements can have properties and attributes and LitElement helps reflect values between these. This is convenient because HTML contains attributes, not properties. That said, as noted above, with lit-html we do have a declarative syntax for setting properties. So, using lit-html, to set an attribute items=${value} or a property .items=${value}. Generally, when passing data to another element in render using properties is better since properties can have any type. Using attributes is usually only necessary for styling and requires serializing/deserializing to a string.
When you say a property is type: Array, this makes LitElement reflect the attribute (which is always a string) to a property via JSON.parse(attributeValue). Likewise, LitElement will stringify property to the attribute value if reflect: true is set via JSON.stringify(propertyValue).
Putting this together, if you really wanted to pass an array value as an attribute using lit-html, you'd have to do: items=${JSON.stringify(propertyValue)}. Again, we wouldn't generally recommend this because passing the property is much simpler (.items=${propertyValue}).
Hope that explains it.

While I have no problem changing my code to use a property instead (and have done so), I would certainly like to encourage the team to update the documentation to match the intended behavior instead of misleadingly suggesting that the default converter build into lit-element can be used on Array or Object type values when they simply don't work.

I think the Polymer team is always interested in feedback and making the docs better. I'm not sure if this is necessarily in the LitElement area of responsibility though. The docs do specify attributes are always strings (a platform requirement) so MyElement has to handle converting it's complexList to a string to or JavaScript will coerce it. The default converter for SubComponent's complexList is trying to working as expected but it's getting "[object Object],[object Object]" instead of valid JSON.
Maybe adding a note to convert between properties and attributes that type conversion is only applied to an instance itself, not when properties are used in a child element would help clarify?


Trainee Onboarding Journey

Problem:
The trainee onboarding journey is a bit chaotic and the messaging is confusing. We do lots of admin and manually move people through the system and people can get lost.
Actions taken:
I have researched the journey, mapped the current situation from the trainee's perspective, and then reorganised it to simplify a bit. I've put that out for consultation with Proms and will leave it out for a week.
https://miro.com/app/board/o9J_kujEdws=/?moveToWidget=3458764561300661427&cot=14
Next steps:

Identify as many simplifications as possible and make them.
Write the boilerplate messaging for each contact stage and remove all the ad hoc stuff
Identify the biggest bottlenecks that cannot easily be removed and turn them into projects

Subtickets

[ ] #6
[ ] #7
[ ] Prom/vol training

Adding here some of the actions
Ongoing

Fixing the applicant page on Dashboard - Epic/Milestone for the Trainee onboarding steps (Agreement, Slack agreement, PC Form, etc.)

Future (do we agree on these?)

Review the Steps on ITD - do need versions or should we just have an "archive" options and keep dates
Review PD Steps - replace Motivation Letter
Replace CEFR with English test (Duolingo practice) (PS: We can then have a proper certificate test in end of Fundamentals, which would mean people would not be allowed into SDC)

The Duolingo certification is such a blessing!

I think this is done and the rest fold into Sheffied


Brief Title Field?

Taking a look at a record with a massive title, it would be helpful to have a way to create/edit a brief version of the title so the display in the search results looks cleaner. GeoBL by default truncates the titles, but this leaves titles trailing in the middle of words. Even if we were to modify the truncate method to cut off after a word, the text displaying might omit crucial info. Ie:
1:1 500 000 series [cartographic material] : tectonic map of
Having the ability to curate a brief title display would be the cleanest way to address the issue of overly verbose titles.

Example:


recheck current route guards on permission change

resolves #1439

I can't replicate this. Anyway I've changed the way the error page redirects and hope this fixes the issue.

I can reproduce this now. Happens only in chromium.


Add Italian translation

Hi there, I am happy to contribute to this and of course, more maintainers are very welcome!
In terms of experience, I used to do English to Italian translations for the Notebook reviews website Notebookcheck.com  => Notebookcheck.it

Hi @deblasis ! Thanks for volunteering! Let's wait for other maintainers to show up then we'll get you started!

Hi, I'd love to join too if help is needed. I've got no previous experiences apart from having contributed to the Visual Studio Code and Azure Data Studio community localisation projects.

Perfect! @deblasis let me know if you're alright with just two of you to start and I'll merge this repo in!

@tesseralis I am happy to start just the two of us and let's see how that goes.
Welcome @LucaBlackDragon! Or I should say... Ciao! 😄

@deblasis hi/ciao! :D

Let's get you two started!

Here's your repo! https://github.com/reactjs/it.reactjs.org/issues/1
Use this issue to track your progress. Happy translatiing!


fix: keycloak user sync

This fixes the syncing of keycloak users in the data service.
I setup iterators to do paginated requests to Keycloak and then just completely forgot to add a while loop to keep going through all possible pages. So currently only the first 20 users were imported.
I tested a job with this code on dev and it works. I use asyncio.gather for the user updates so if I use a nullpool then I open too many connections to postgres. That is why I added a pool with 2. I know this slows things down but this is just a job that runs periodically and it does not need to be fast. It is better for this to be slow than to nuke the db.
Once this is approved and merged. I will make a bugfix release from 0.5.0 that includes this change and then make a renku bugfix release. Currently on main in this repo we have a lot of stuff that will go out with renku 0.50.0 but this fix will be added to 0.49.x so that it can be deployed sooner than 0.50.0.
This is preventing admins from adding users to different resource pools.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 35 (2.86%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 88.69%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

bases/renku_data_services/keycloak_sync/config.py
0
1
0.0%

components/renku_data_services/users/kc_api.py
0
33
0.0%

Files with Coverage Reduction
New Missed Lines
%

components/renku_data_services/crc/models.py
1
85.06%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
5097

Relevant Lines:
5747

💛  - Coveralls


SIMD docs

I recently used SIMD capabilities of .net and I find it fascinating, however, the official documentation seems lagging in this regard -the only thing I could find is this Numerics in .NET which is not complete- so I wanted to create a complete SIMD documentation.
my proposed outline  contains:

What is SIMD
How we can use SIMD in .net
Caution and don'ts of SIMD
Maybe some benchmarks at the end

also, I did some docs contribution to .Net foundation projects not long ago, and I'm fairly familiar with the process.
https://github.com/aspnet/AspNetCore.Docs/issues/11770
https://github.com/aspnet/AspNetCore.Docs/pull/12108
https://github.com/aspnet/AspNetCore.Docs/pull/12137

Thanks you, @FIVIL, for offering to provide some solid information on SIMD. We'd welcome your contribution, and your basic outline looks good. How would you like to proceed, and what sort of time frame are you looking at for submitting a PR?
@terrajobst, do you have any feedback about more detailed SIMD content?

@tannergooding would be the best person to provide feedback on this because he's been working heavily on all the intrinsics lately. We should probably talk about SIMD in general and then how we're exposing in the the BCL, as an abstraction (Vector<T>) and as a set of in System.Runtime.Intrinsics.
I like the idea of dos and dont's but that's definitely @tannergooding territory.

Adding conceptual docs for hardware intrinsics is on my list of backlog items to do for 3.0. However, I would be very happy if someone else wanted to start that work and would be happy to review and provide input as appropriate 😄
Also CC. @danmosemsft

Thanks, @tannergooding. Does the rough outline that @FIVIL provided sound good, with the possible addition of a section on SIMD and the underlying hardware?

Yes, the four sections listed look to cover what I would expect.

@rpetrusha , I'm planning to get the best of my free time by providing this tutorial, so I think maybe I can deliver it in a month or so, hope that's Ok, and after that, I'll be open to any note and comment and change needed in order to finalize it.  and also I think the best way to do this will be 2 separate articles the first one containing a simple definition and instruction and some simple code samples for starters. and the second article will be a deep dive into the concept of SIMD, underlying hardware, CPU, capabilities and the best practices for SIMD with some insights and of course, some benchmarks to demonstrate benefits of using SIMD.
I will /cc you in the PRs.

@tannergooding and @terrajobst  tnx for your insights.
also, I might need to ask some questions about some concepts during the process if that's OK.

That sounds good, @FIVIL. We'll look forward to reviewing your PR in about a month.


Remove Puppet bits

Since we are not using Puppet anymore to provision hosts, let's remove the existing Puppet bits from the repository.

Removed in e2d9d66958d07f435762c8c8ddff008e946d2cfb


[e2e]: generic schedule main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8336900099
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Tue Mar 19 03:17:13 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8353231998
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Wed Mar 20 03:06:16 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8369052369
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Mar 21 03:09:17 UTC 2024
Tests are passing now. Closing this issue.


Renegade X Using HTTPS

Describe the issue you are having
Renegade X's launcher is now using HTTPS for game installs and updates. Reached out to the Totem Arts team on their Discord and confirmed the change.
As a result, game installs and updates no longer cache. The Renegade service should be removed until the launcher switches to HTTP.
The team also provided their new domain name for their CDN, though it isn't relevant since they're HTTPS: patches.totemarts.services

I talked with the developers and they told me they changed it back to HTTP 6 days ago. I wait for the domain names so I can update that 😊

See #249 - this change should already be live. You will need to restart your lancache-dns and monolithic containers for those changes to take effect.

They changed it back to HTTPS, now it is no longer cachable.

What on … why?

We didnt intentionally revert back to https, there is likely a automation somewhere that did it. Just need go take some time to dig into that :)  Will try to update you folks when I fix it.

I believe I found the culprit, you can try it again now. It may take up to 24 hours for caching to expire everywhere.

I believe I found the culprit, you can try it again now. It may take up to 24 hours for caching to expire everywhere.

Thanks mate 😍


Added more application examples

This pull request resolve #24

Codecov Report

Merging #26 into master will increase coverage by 0.98%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master      #26      +/-   ##
============================================
+ Coverage     82.16%   83.14%   +0.98%
  Complexity      184      184
============================================
  Files            23       23
  Lines           611      611
  Branches         80       80
============================================
+ Hits            502      508       +6
+ Misses           58       52       -6
  Partials         51       51

Impacted Files
Coverage Δ
Complexity Δ

...plating/mail/service/ThymeleafTemplateService.java
81.81% <ø> (ø)
5 <ø> (ø)
:x:

...lating/mail/service/FreemarkerTemplateService.java
81.81% <100%> (+18.18%)
4 <ø> (ø)
:x:

...mplating/mail/service/MustacheTemplateService.java
87.5% <100%> (+12.5%)
5 <ø> (ø)
:x:

...templating/mail/service/PebbleTemplateService.java
86.66% <100%> (+13.33%)
5 <ø> (ø)
:x:

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 9053fde...47dd9d1. Read the comment docs.


[WFCORE-4904] Remove setting Metaspace

Issue JIRA : https://issues.redhat.com/browse/WFCORE-4904

Can one of the admins verify this patch?

We need a clear case for removing the -XX:MetaspaceSize=96M setting. The discussion I've seen around this is focused on the -XX:MaxMetaspaceSize setting.
The -XX:MetaspaceSize=96M setting was added because we observed that relying on the default value resulted in a full gc in the middle of server boot as the jvm adjusted to the necessary amount of memory.

Based on Brian's comments I have added the hold label as this sounds like it needs to be a part of a larger investigation.

Based on Brian's comments I have added the hold label as this sounds like it needs to be a part of a larger investigation.

@darranl Thanks for adding Hold label on it, even I was looking for the same. Investigating more on it.

Working on it.


Macros support?

Does this plugin support Twig macros? I'm trying to use one in pagination/templates/pagination-unbounded, but I'm getting the following error
An error occurred whilst rendering /project/home/ihiutch/workspace/stories/pagination/templates/pagination-unbounded.twig: TypeError: Cannot read properties of undefined (reading 'valueOf')
Codesandbox
**Also, excuse the other files, I found this plugin and am in the midst of migrating (If I can get macros to work!)

I tried playing around with some simpler implementations and noticed that it seemed to work intermittently. But the error that came up (in browser) was always the same fs.statSync one

Can you give https://github.com/larowlan/vite-plugin-twig-drupal/pull/6 a try? Test in the PR seems to show it working, even with self references. Took me a while to get it going because I naffed up the macro syntax in the test twig files :upside_down_face:

Happy to make a release with #6 if that's easier for testing, it doesn't make things any worse

Seems to be working, locally. Thank you!

Cutting a new tag

https://github.com/larowlan/vite-plugin-twig-drupal/releases/tag/v1.0.2 should be on npm


Pretty print

I have a map with lots of nested data structures that I want to pretty print (using tabs for indentation). Is this possible? E.g.
Map {
    data: Map {}
}

I would love to do this, yes.

I ran into this recently, and decided to throw together a little pretty-print lib for it
https://github.com/glenjamin/pretty-immutable

Closing this aging issue. (nice work, @glenjamin!)

Is it worth me sending in a PR to have this behaviour in core?


Fix GaussianKernel in multi-sigma case

It is extremely slow. Example:
#!/usr/bin/env python3
from falkon import Falkon
from falkon.kernels import GaussianKernel
from falkon.options import FalkonOptions
import numpy as np
import time
import torch

def build_dataset():
    X = torch.rand(10000,28)
    f = lambda x: torch.sin(x)
    Y = f(X)
    return X,Y

def single_sigma():
    sigma = 2.8
    lam = 1e-5
    ITERS = 10
    SEED= 4242
    config = {
        'kernel': GaussianKernel(sigma=sigma),
        'penalty': lam,
        'M': 200,
        'maxiter': ITERS,
        'seed': SEED,
        'options': FalkonOptions()
    }
    return Falkon(**config)

def multi_sigma():
    sigma = torch.tensor([2.8 for _ in range(28)])
    lam = 1e-5
    ITERS = 10
    SEED= 4242
    config = {
        'kernel': GaussianKernel(sigma=sigma),
        'penalty': lam,
        'M': 200,
        'maxiter': ITERS,
        'seed': SEED,
        'options': FalkonOptions()
    }

    return Falkon(**config)

def multi_sigma_matrix():
    sigma = 2.8 * torch.eye(28,28)
    lam = 1e-5
    ITERS = 10
    SEED= 4242
    config = {
        'kernel': GaussianKernel(sigma=sigma),
        'penalty': lam,
        'M': 200,
        'maxiter': ITERS,
        'seed': SEED,
        'options': FalkonOptions()
    }

    return Falkon(**config)

def test_fit(X,Y, flk):
    st = time.time()
    flk.fit(X, Y)
    end = time.time()
    return end - st

X, Y = build_dataset()
print("[->] Single sigma => dataset fitted in {} seconds".format(test_fit(X, Y, single_sigma())))
print("[->] Multi sigma => dataset fitted in {} seconds".format(test_fit(X, Y, multi_sigma())))
print("[->] Multi sigma (using a matrix with sigmas in the diagonal) => dataset fitted in {} seconds".format(test_fit(X, Y, multi_sigma_matrix())))

The issue is that we treat diagonal length-scales the same as a full matrix, and this breaks KeOps at a much lower data-dimension than with a single lengthscale. I'll implement two fixes:

Rework the Gaussian kernel so that it uses division by the lengthscale instead of the full-matrix multiplication in case a vector of length-scales is provided. This is a common use case!
Switch to the matmul implementation earlier when full-matrix lengthscales are used.

In the meantime you can try to use the option use_keops="no" for full-matrix lengthscales. This should speed things up.


Expand on 'Using iriusrisk for the Risk management workflow'

commercial product more focused on Threat Modeling, but since it now has an 'Accept Risk' button, it could be used for the Risk Workflow

integrates with JIRA (can be used to create and manage issues)
very active development and lead by known AppSec security experts
would be interesting in seeing it's cost when compared with JIRA (in an environment that doesn't have JIRA)

there is an community edition: https://community.iriusrisk.com/

Hi @DinisCruz thank you for including our product! Shout if you have any questions.  We're using github for issue tracking and wiki: https://github.com/continuumsecurity/IriusRisk


Issue with k8s.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/

This is a Bug Report

I want to verify the validity for all of my kube cluster certificates. I see kubeadm alpha certs check-expiration is a way to do that from kube docs. But thats really not working for me. RIght now I'm trying to use something openssl x509 -enddate -noout -in ../apiserver.crt but definitely would like to use kubeadm for all sorts of my cluster details.

Problem:
$kubeadm alpha certs check-expiration
Commands related to handling kubernetes certificates

Usage:
  kubeadm alpha certs [command]

Aliases:
  certs, certificates

Available Commands:
  renew       Renews certificates for a Kubernetes cluster

Flags:
  -h, --help   help for certs

Global Flags:
      --log-file string   If non-empty, use this log file
      --rootfs string     [EXPERIMENTAL] The path to the 'real' host root filesystem.
      --skip-headers      If true, avoid header prefixes in the log messages
  -v, --v Level           number for the log level verbosity

Use "kubeadm alpha certs [command] --help" for more information about a command.

I don't see check-expiration in the available commands. Does this work for certain kubeadm versions? If so, listing the versions could be helpful. if not please let me know if there is anything I'm missing here to get this working.
Proposed Solution:

Possibly update the docs with more information on how exactly this check-expiration can be used if the existing docs miss anything here.
if this command is no longer supported, please suggest the alternative ways that can used.

Page to Update:
https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/

$kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:08:49Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

Sorry if this is a spam and thanks in advance for your inputs.

This is a feature of 1.15, your kubeadm version is 1.14, please update and try again.
/close

Thank you @thecrudge


[wip] Make MaskRCNN TorchScript compatible

TODO:

Run the previous version and this one both in eager and script, verify the results between the 3 are the same

I've been working on the same problem for the last few days.
I've converted most parts to support scripting. The problem is with lazy_import.
What's the plan to handle C++ bindings?

@cted18 I'm trying to fix the problem of the lazy import. I'm not yet sure how I'll make it compatible with torchhub, but I'll give it a try

What is left to do for this PR? Could we try to get it ready for review?

Subsumed by #1407


chore: update local-node version

Description:

Related issue(s):
Fixes #
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

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

Project coverage is 75.15%.  Consider uploading reports for the commit 3d581ea to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2245   +/-   ##
=======================================
  Coverage   75.15%   75.15%
=======================================
  Files          13       13
  Lines         644      644
  Branches      118      118
=======================================
  Hits          484      484
  Misses        115      115
  Partials       45       45

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


Skeleton loader not showing when navigating to browse datasets page

Describe the bug
When navigating to the browse datasets page, it should show a skeleton loader for the table because remix should be doing a client side transition when loading the page
To Reproduce
Steps to reproduce the behavior:

Go to https://cryoetdataportal.czscience.com/
Click on Browse Data
Notice that page takes a long time to open browse datasets page

@codemonkey800 to update the description


Make PHP 7.1 a minimum requirement

Makes no sense to support older versions anymore in my opinion

I'd rather not, because that will seriously limit the amount of people that can benefit from this module.

The README says Laravel 5.5 is required and that itself requires PHP 7.0+: https://laravel-news.com/laravel-5-5-php-7-0

@Jalle19 I see, I think we can change that to Laravel / Lumen 5.3 in that case.


installing "lines" in a symfony project results in 'Attempted to load class "UnicodeString" from namespace' error

as "lines" replaces symfony/string
....
    "replace": {
        "symfony/string": "*",
        "symfony/polyfill-ctype": "*",
        "symfony/polyfill-intl-grapheme": "*",
        "symfony/polyfill-mbstring": "*"
    },
...

but does not provide a real replacement, it results in an error if installed in a symfony project
Executing script cache:clear [KO]
 [KO]
Script cache:clear returned with error code 255
!!
!!
!!  Symfony\Component\ErrorHandler\Error\ClassNotFoundError^ {#4401
!!    #message: """
!!      Attempted to load class "UnicodeString" from namespace "Symfony\Component\String".\n
!!            Symfony\Component\ErrorHandler\ErrorHandler->handleException() {}
!!    }
!!  }
!!
Script @auto-scripts was called via post-update-cmd

Thanks for reporting :+1:
Could you try the <IP_ADDRESS> version? If that helps, I'll keep only the downgraded tagging

I've just released 0.5 version that is downgraded without any weird suffix. Could you try it?


CARDS-1220: Odd looking selection dialog appears after canceling creation of subject's parent

I can sometimes get in an inconsistent state, trying to pin down the exact sequence of back and forth, but I can get to something like:

new tumor region
new tumor parent for it
new patient parent for it, but the table only lists "Tumor" as the available type
new patient parent for it, so the planned hierarchy is patient / tumor / tumor / tumor region, and then clicking Create fails

@sashaandjic can you also try to reproduce this?

Steps to reproduce:

create new subject
type t as subject identifier and select Tumor
click on CONTINUE --> Select Patient for new tumor t dialog appears
click on 'NEW`
click on CANCEL
click on BACK
select Tumor region as a type of the new subject

I retested this PR for the 1220 issue and all is good. I believe we can merge this PR.


Download combined table of BLAST results and combined raw file

Description
According to the updated spec (see ENSWBSITES-1768)), submission download payload has been updated, such that:

All BLAST job results are saved into a single table file
All raw outputs are collated into a single txt file

Related JIRA Issue(s)

https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-1843
https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-1768

Deployment URL(s)
http://blast-download-update.review.ensembl.org

This is how the data section in the TSV file looks. Is this what we expect it to look like?

For multiple job results, headers need a newline before concatenating.

For multiple job results, headers need a newline before concatenating.

Thanks, should be fixed now.


Allow store keys to be camel cased.

This PR allows up to use single quotes around a property to exclude it from being snake cased in the case we may not have an eloquent model in the store.

Testing file changes were not found.
Paging @johnnie502 to review the back-end work in this pull request!
Paging @juanmrad to review the testing work in this pull request!

!reassign back-end

Paging @RedEnchilada to review the back-end work in this pull request!

Reassigned backend review because Johnnie will not be back until Friday.

QA Information
There is nothing to test.


Build steps failing due to -Werror=class-memaccess

I'm trying to build this repo in a Docker container following the steps in the readme.  Here is an excerpt from my Dockerfile:
FROM mcr.microsoft.com/dotnet/core/sdk:3.1

ARG tools_dependencies="gcc cmake libboost-dev libboost-thread-dev unzip zlib1g-dev"
RUN DEBIAN_FRONTEND=noninteractive apt-get update && apt-get install -y --no-install-recommends \
    ${tools_dependencies}

RUN curl -sSL https://get.haskellstack.org/ | sh

RUN cd /tmp && \
    git clone --recursive https://github.com/microsoft/bond.git && \
    cd bond && \
    mkdir build && \
    cd build && \
    cmake -DBOND_ENABLE_GRPC=FALSE .. && \
    make -j $(nproc) && \
    make install && \
    cd ../.. && \
    rm -rm /tmp/bond

The make step fails with:
/tmp/bond/thirdparty/rapidjson/include/rapidjson/document.h:1939:24: error: 'void* memcpy(void*, const void*, size_t)' writing to an object of type 'class rapidjson::GenericValue<rapidjson::UTF8<> >' with no trivial copy-assignment; use copy-assignment or copy-initialization instead [-Werror=class-memaccess]
             std::memcpy(e, values, count * sizeof(GenericValue));

Looks like there are some reports of this in the upstream with some fixes. Does it build if you change the RapidJSON submodule to point to commit 2bbd33b332 or later?
If so, a PR to bump the RapidJSON submodule version would be appreciated.
If not, can you either contribute a PR

to upstream that fixes this issue that can be consumed here or
to Bond that pushes/pops a suppression for this error around the RapidJSON #includes?

@chwarr - Any issues with bumping up RapidJSON submodule to the latest commit that is building correctly on upstream? I am thinking of 8f4c021 on Apr 10?
I can send a PR for this.

Probably not.


Consider zero item use cases

I think the best way to handle this is with a null person case, so the display could handle a common message about not finding said person.


Allow multiple packages for uv tool upgrade/uninstall

Summary
Resolves https://github.com/astral-sh/uv/issues/6571
Test Plan
cargo test

Looks great, thank you!


gui: show more info on synchronisation screen

This is to resolve #646.
I've added the specified text to the synchronisation screen and also display the progress as a percentage above the progress bar.
This is how it looks (on signet with Liana-managed bitcoind):

Also, for external bitcoind:

Looks great.


Don't error when using xcode-select to find current selected version.

$ xcodes list
Failed executing: `/usr/bin/xcode-select -p` (2).

MAINTAINER EDITED BELOW
If I don't have any Xcode version installed, Xcodes currently errors out using the xcode-select to print out which version is selected
A bit of refactor is needed, but Xcodes should fail gracefully if xcodeSelectPrintPath fails.

Thanks @thii - i've updated the wording to make this issue more of how to fix it.

Xcodes should fail gracefully if xcodeSelectPrintPath fails.

I think it should not fail though. If I have a new Mac, the first thing I download would be xcodes, and I want it to be able to download Xcode. But currently I'd have to manually download Xcode in order to run xcodes in order to download Xcode.


feat: add passthrough columns to card model.

Please provide your name and company
Bram - Gigs
Link the issue/feature request which this PR is meant to address
https://github.com/fivetran/dbt_stripe_source/issues/80
Detail what changes this PR introduces and how this addresses the issue/feature request linked above.
Add passthrough variables for the stg_stripe__card model. This can, for example, be used to pull in non-standard columns from Stripe such as description, iin and issuer.
How did you validate the changes introduced within this PR?
Followed the instructions here and tested the changes against our own internal data. Note, I could only do this for iin and issuer, not for description.
Which warehouse did you use to develop these changes?
BigQuery
Did you update the CHANGELOG?

[x] Yes

Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)

[x] Yes

Typically there are additional maintenance changes required before this will be ready for an upcoming release. Are you comfortable with the Fivetran team making a few commits directly to your branch?

[X] Yes
[ ] No

If you had to summarize this PR in an emoji, which would it be?

🐸
Feedback
We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.
PR Template

Community Pull Request Template (default)

Maintainer Pull Request Template (to be used by maintainers)

Thanks @bramrodenburg for opening this! Looks great.
One question - Regarding description, did you just not include it in your tests, or was it throwing an error or something like that?

Followed the instructions here and tested the changes against our own internal data. Note, I could only do this for iin and issuer, not for description.

One question - Regarding description, did you just not include it in your tests, or was it throwing an error or something like that?

I didn't include it in our tests. We asked Stripe at the time to enable the iin and issuer columns, but not the description column. So that's why I didn't include that column in the test.

Woo thank you! This looks great to me. I'm going to merge it into a release branch to make some other changes and CI tests.
Many thanks


New version: EclipseAdoptium.Temurin.17.JRE version <IP_ADDRESS>

Pull request has been created with Komac v1.11.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Duplicate of https://github.com/microsoft/winget-pkgs/pull/118447


Use the related models on_delete setting

It would be good to honor each related model's on_delete setting rather than a global on_delete setting. For example, if you had the following models.
class Author(models.Model):
    name = models.CharField(max_length=100)

class Book(models.Model):
    author = models.ForeignKeyField(Author, on_delete=models.RESTRICT)

If you tried to delete the author and the author was used in a book, it shouldn't allow the deleting because there are models that use that author.

Thank you @epicserve ! Yep, good catch. I'll try to add this functionality with the very next update.

Hi @epicserve , the latest version of this lib is already can use on_delete option as well. You could use it as a regular Django model. But pay attention, this functionality works only if all related models are SoftDeleteModel.
I close this issue. But If you still have some questions, feel free to open it again.


Refactor and review Page Management plugin

Path should have only one segment (/a/b is not valid)
Parent Page id should not be the same page's id
Path should be unique
Path should be stored as the user entered, but when we want to check the uniqueness, it should be case insensitive
Null parent page is not working
Think of parent page deletion

for number 3, I think (Parent Page + Path) should be unique not only path


API documentation

Currently, the versions of the API aren't tracked in combination with the software versions of Lisk Core.
Also, the API specification in the documentation is always referring to a Testnet node and might differ from Mainnet.
It should be possible to browse both network API specifications, and changes of the API should be documented for older versions of the software.

Added API docs for Testnet and Mainnet


[website] Update selection colors for readability

I sometimes find myself selecting parts of text that I'm reading, the current selection styles are not optimal for readability:

PR preview
I've re-used current colors and already-defined custom properties to make selected text more readable:

This could be improved further to ensure a certain level of contrast of course, if anyone is interested in doing that.

A somewhat related (to colors) but off topic comment:
CSSWG is looking to potentially standardize color ramps, which may not only be of interest to your organization but perhaps you've got some valuable insight. See https://twitter.com/tabatkins/status/1442979946914205712.