IR image on D455 is much darker then on D435i

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D435i and D455

Firmware Version
<IP_ADDRESS> for both cameras

Operating System & Version
Linux (Ubuntu 20.04)

Kernel Version (Linux Only)
5.8.0-48

Platform
PC

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
Robot

Issue Description
<Describe your issue / question / feature request / etc..>
There are few complains:

Infrared image on D455 is generally much darker then on D435i. When I manually adjust Advanced Controls -> AE Control to the same value as on D435i, D455 depth quality increases. IR and Depth images:
D435i

D455

D455 IR image after manual AE Control adjustment

another complain: table top is nicely visible on depth image on D435i and basically invisible on D455. For robot it is important to see floor as well

Is it suppose to be like that, or it is just my D455 camera misbehave? Both cameras are connected to the same computer next to each other.

Hi @dsvua   I was able to replicate your infrared results with my own D435i and D455 side by side.  Disabling auto-exposure or instead changing the Mean Intensity Set Point value of AE Control on the D455 (as you suggested) made the infrared images of the two cameras more equal.
I found in my own tests that once both cameras were set to the same Mean Intensity Set Point of 1536 then their infrared images of a table-top were almost identical.

Yeah, but no depth for table top on D455. Like on attached depth images, you can see that on table top is covered in blue on depth image for D435i, when D455 have very sparse little depth islands.

Please try maximizing the Laser Power option to '360' on the D455 controls to see whether it makes a positive difference.  the sparseness of the depth image is tied to the value of Laser Power.  A lower value increases sparseness (more holes / gaps) and a higher value reduces sparseness.

Almost the same. Plus I tried changing laser power when posted pictures - no visual effect on Depth image on D455

I can see how the reduced visibility of the IR dot pattern on the desk on the D455 image could impact the ability of the camera to read depth detail from it.  Surfaces such as desks, walls and doors typically have low texture detail or no texture, so having a dot pattern projected onto such surfaces because the camera can use the dots as a texture source to analyze for depth detail.  So if the dot pattern on a low-texture surface has faint visibility or no visibility then that will have an impact on the depth image due to the reduction in analyzable depth detail.
Black or dark grey surfaces are also generally difficult for the camera to analyze because the dark color absorbs lights.  The darker the color, the more the light is absorbed by the surface.  Hence why a white wall has much brighter dots.  If a strong light source is cast on to a black surface (e.g a leather office chair) then it can help to bring out texture detail and make the illuminated areas more blue instead of being empty of depth detail.  The principle is illustrated in thhe link below.
https://github.com/IntelRealSense/librealsense/issues/6757

I understand that, but why D435i has no problem, when D455 cannot produce depth on table top? What is the difference between cameras?

D455 has a minimum depth sensing distance of 0.4 meters, whilst on D435i it is just 0.1 meters (meaning that it can get closer to surfaces before the depth image starts breaking up).  So at close-range, the D455 may have less detail on the depth image in the foreground.  This difference gives the D455 a greater maximum depth sensing range.
You can reduce the minimum depth distance of the camera, whilst reducing its maximum depth distance as a trade-off, by increasing the value of the Disparity Shift option.  Setting the disparity shift to '50' should provide a good balance between gain in foreground and loss of background.

Hi @dsvua  Do you require further assistance with this case, please?  Thanks!

Can you confirm that my understanding is right:

D455 has generally darker IR images then D435i and it is normal.
Worst D455 performance (in comparison to D435i) for floor distance detection is due to wider IR cameras distance and related to it, worst, close to camera, depth detection.

Technically, this thread could be closed.

I do not have any information to add about the infrared beyond what has already been mentioned.
In regard to the depth and the reduced detail on the desk near to the camera, this is symptomatic of the results that might be expected from the D455's larger minimum depth sensing distance (0.4 meters on D455 instead of 0.1 m on D435i).  Basically, a surface / object has to be further away from the camera lens on D455 for it to be rendered on the depth image.
As mentioned in https://github.com/IntelRealSense/librealsense/issues/8717#issuecomment-812131672 above, the camera's minimum depth sensing distance (MinZ) can be reduced by increasing the Disparity Shift option's value, enabling more of the near-range depth detail to be rendered on the depth image.

Hi @dsvua  Do you require further assistance with this case, please?  Thanks!

Thanks very much @dsvua for the update!


Analytics Script

I would like to work on this issue

Can you do it for the Pull requests within a week?

Will try and update the same with you

Cool! take your time and if you need help @swat1998 can help you out


Write ADR-01 on overall tool architecture

The purpose of ADR-01 is to outline the decomposition of Modelator into components and their APIs, such that the work on the tool can be efficiently parallelized. As the tool will undergo many changes in the near future, the constructed document will have to also undergo several refinement iterations; please read the resulting document critically, and feel free to propose changes. The description of architecture of sub-components will be delegated to subsequent ADRs.

While writing this ADR has been overtaken by implementation efforts, it might be a good idea to get back to it when/after working on #297.


Validate the global and toast specific settings

apparently no one has been interested in this so i'm closing it for now


fix: ts and lint errors in ez-vue

fix the lint and compilation errors that occur in the GitHub pipeline. The errors are located in the ez-vue package.

The root cause was deeper than that .. see #11


[SPARK-50011][INFRA][FOLLOW-UP] Refresh the image cache job

What changes were proposed in this pull request?
Refresh the image cache job
Why are the changes needed?
this job has been broken: https://github.com/apache/spark/actions/runs/11387123331/job/31682246504
Does this PR introduce any user-facing change?
no, infra-only
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no

thank you @Yikun @dongjoon-hyun and @HyukjinKwon
merged to master

Thank all, it seems this the cache take effect in both master https://github.com/apache/spark/actions/runs/11399304381/job/31717882423 and my repo https://github.com/zhengruifeng/spark/actions/runs/11399270535/job/31717789932

To @zhengruifeng , unfortunately, it seems that this broke branch-3.5 and branch-3.4. Could you take a look at that?
Error: buildx failed with: ERROR: unable to prepare context: path "./dev/infra/base/" not found

Sorry, but let me revert this first for now in order to recover the release branch CIs as a release manager for Apache Spark 3.4.4 EOL release.

Oh, it's too bad. It seems that the cache is gone and reverting makes the situation worse. :(

Let me revert SPARK0-50011 too because it never works seamlessly until now in all CI combinations.

oops, we discussed old branches before, but thought no change needed.
my bad, let me take a look

No problem at all. As you know, I inevitably reverted them to unblock Apache Spark 3.4.4 release preparation (next Monday). If we don't have a release schedule, they would remain in the branch.
Thank you again, @zhengruifeng !


feat(webpack-builder): html plugin support template & templateByEntries

PR Details

Description

html plugin support template & templateByEntries

Related Issue

Motivation and Context

How Has This Been Tested

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project.
[ ] I have updated changeset
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

文档也加一波吧~

文档也加一波吧~

done.


Add projects for System.Numerics support

I added legacy support classes for System.Numerics namespace (BigInterger, etc),
and change xunit test to nunit test for each .net versions
Please release for nuget and unitpackage, if nothing wrong.

Thanks for pull request! I'll take a look at this commit.
Could you tell me why you want to use these classes on pre .NET 4 env?
Definitely BigInteger and Complex are quite basic things but still wonder why.

Sorry for late response on your comment.
Github didn't notify for me, (any error??) so I see your comment today.
To answer you question, I want to use BigInterger class in unity project which use .net 3.5.
(But BigInteger exists in .NET4.0, it's my mistake.)
Anyway, I decide to make my own package, so I cancel this pull request.
Sorry for border you =)


Expose length of datasets so we can start/stop

Builds on #64
previously we treated datasets as having unknown length, which was kinda problematic sometimes.
This changes behavior: in training, we have to explicitly loop forever, and we now skip the last little bit of shards that aren't the shortest shard. Previously we would skip the last little bit of every "batch" of docs written to the token cache

this one at least is ready i think


Compile March data for monthly stats

Monthly spreadsheet

Then again, spike in January known to be due to bots, so March user numbers are just returning to normal.

Here are user numbers from Jan 2023:

If we discount April 2023 before spam filter was deployed in May and period second half of Jan 2024 to first week of Mar 2024, then user numbers appear steady.

@jcateswellcome ☝ The user stats seem to have 2 anomalous periods: one before the spam filter was deployed in May last year and one 8/1/24-6/3/24. I wasn't asked to comment on January or February numbers but I'm thinking it would be helpful to provide commentary on why there has been a 22% decrease on site visitors from last month.
The only thing I can think is that the AWS anti-bot rules have fended off attacks. If that is the case, why did they only start making a different on 6/3/24?

This appears to be due to due to bytespider activity. Here's user numbers by country with China highlighted in purple:

The ticket highlighting this bot issue is #10769 .
In the meantime, the monthly stats will be reported less the monthly average for China for January, February and March. This approach may need to be adopted for April stats as well.


feat(vscode): support lint vue file

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #1745

PR #1760

PR #1814

PR #1842   👈

This stack of pull requests is managed by Graphite.

Merge activity

Dec 31, 9:14 AM: @Boshen started a stack merge that includes this pull request via Graphite.


'proposals/rpn_r50_fpn_1x_val2017.pkl',

proposal_file=data_root + 'proposals/rpn_r50_fpn_1x_val2017.pkl',  请问这个怎么获得？

Please use English or English&Chinese for issues.
You can test a RPN model on the dataset to get the proposals.


Incentivized Receive Channel dispatch status

incorporated into #219 in https://github.com/Snowfork/polkadot-ethereum/pull/219/commits/9b3e7d41b398909f0c1a1f20d4518e0d3c5afd5e

incorporated into #219 in https://github.com/Snowfork/polkadot-ethereum/pull/219/commits/9b3e7d41b398909f0c1a1f20d4518e0d3c5afd5e


Feature request: Allow uploading of experiment files

We have been developing an online runtime for OpenSesame experiments (https://github.com/shyras/osweb). With very, very little effort, I was able to set up JATOS and integrate these experiments. Impressive! (If you're interested: An experiment is bundled into a single html which embeds the experiment script and the OpenSesame interpreter, and this can be uploaded to JATOS.)
JATOS seems to be the best option to host and manage experiments (osweb is just a runtime). But one option is missing, especially if we want to roll this out on a larger scale: I can create a component in JATOS, but to add the actual experiment files I have to go outside of JATOS and manually upload the files. Or am I missing something?
Hence a feature request: Please allow for uploading of files through JATOS!

Ping @dschreij and @shyras

Your JS library for OpenSesame sounds really interesting. I'm glad to hear that it was easy to integrate it with JATOS! Do you have an example that you could send me so I could try it out?
Now to your feature request, a file upload function. It sounds to me like you're using JATOS on a server only. But usually doing an experiment with JATOS involves 2 JATOS instances: a local one where you develop everything and then a server one where the actual run with participants happen. So I'd think a file upload isn't really necessary, just export/import the whole study would do. The only advantage of a single file upload that I can see is when you have big file sizes and uploading the whole study would take much longer than just one file.
Let me clarify: This separation into local and server JATOS has the advantage that you can easily create and edit all HTML/JS/CSS files (called study assets in JATOS) needed for your experiment (called study in JATOS) because you have complete access to your local file system. Then when you are done (or at least want to test it with participants) you export the study from your local JATOS (in the GUI: study page -> More -> Export) and import it into your server JATOS. Export means: everything that belongs to a study (study asset files + study and component properties) is put by JATOS into a zip file. If you want to update your study you just export/import a second time: JATOS will ask you then whether it should overwrite the study.
Does this answer your issue? I'm happy to think of solutions if it doesn't.

I'm glad to hear that it was easy to integrate it with JATOS! Do you have an example that you could send me so I could try it out?

 Do you want me to submit them through GitHub or mail?
I hadn't understood this workflow of exporting and importing experiments with two JATOS instances. For our immediate need, this is actually enough, and it also avoid the issue of needing to mount the container storage when running inside Docker (ping @dschreij).
However, if we would want to roll out JATOS for non-technical users to manage their own experiments, this export-import routine would be too complicated. And this is what we're looking for: Not primarily to run our experiments, but to provide a service for researchers to easily run their own experiments without needing to set up anything. Do you see JATOS develop in that direction?

I just uploaded a Cats, dogs, and capybaras experiment to the cortex test server to see if it works (and it does!). This is a pretty big experiment with images and sounds, so loading times are a bit high.

I just tried your Cats, Dogs, and Capybaras experiment and it looks great!
I had a look at the source code, very nice! When OSWEB is ready and if you
agree we can put a page in the JATOS docs describing how to put an OSWEB
experiment into JATOS.
I think we have 2 separate points here:

Actually I think this export/import routine is quite simple even for
non-technical users. But I see your point that it might not be intuitive in
the beginning. People are used to upload their files and work with them in
the application directly. JATOS' approach with one local and one server
instance takes some initial explaining. We also thought about other
solutions: We could use git or tools like rsync in the background to
synchronize between different instances. Or use some FTP library. Or even
provide a file upload feature. In the end we always came to the conclusion
that a export/import is the easiest for the user. But maybe you have
another idea?

What we could always do is put up a JATOS in the cloud for everyone
whose experiments do not require high data privacy (similar to
cortex.jatos.org). With this JATOS the user doesn't have to care for
anything but their experiment since I would care for administration. But
although cloud VMs aren't expensive we just didn't have the funding so far.

One alternative to an open JATOS server is an institute-wide one (a bunch
of universities did this already). And this works well. The user doesn't
have to set up anything since it's done by the IT.
Happy to hear your thoughts.
On Sun, 19 Aug 2018 at 11:59 Sebastiaan Mathot<EMAIL_ADDRESS>wrote:

I just uploaded a Cats, dogs, and capybaras experiment to the cortex test
server to see if it works (and it does!). This is a pretty big experiment
with images and sounds, so loading times are a bit high.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/JATOS/JATOS/issues/149#issuecomment-414116865, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH1eBs2umtoAslr_LbCBT909u7xkuoktks5uSTcAgaJpZM4WBLa2
.

I understand the reasons behind the importing/exporting routine of Jatos. I think @smathot 's approach of packaging everything in one big index.html file is quite unconventional, but I also understand why he has chosen to do it like this.
@smathot, if you think of it, packaging all experiment assets separately into one .zip file is more analogous of what you are doing with .osexp files, so wouldn't it be better to create an export function in OpenSesame that packages/zips an experiment in such a way that it can be directly imported by JATOS? That way, you don't have to cram everything into one big HTML file, and uphold a 'separation of concerns' by keeping all images, experiment files and other resources as they are. I think it also makes it easier to debug osweb experiments in the long run.
For the osweb source itself, I would say we need to place the osweb en vendor bundles on some CDN, and uphold a strict versioning system, so users can always download the osweb version for/with which the experiment was built, but don't have to redownload these osweb files every time again (I think osweb plus the vendor source bundles also exceed 1MB already).

create an export function in OpenSesame that packages/zips an experiment
in such a way that it can be directly imported by JATOS?
This is actually what is done in the new version of lab.js: generate a zip
that can be directly imported to JATOS. It's works well. The format that
JATOS needs is rather straight forward and I can help with it.

On Sun, 19 Aug 2018 at 21:58 Daniel Schreij<EMAIL_ADDRESS>wrote:

I understand the reasons behind the importing/exporting routine of Jatos.
I think @smathot https://github.com/smathot 's approach of packaging
everything in one big index.html file is quite unconventional, but I also
understand why he has chosen to do it like this.
@smathot https://github.com/smathot, if you think of it, packaging all
experiment assets separately into one .zip file is more analogous of what
you are doing with .osexp files, so wouldn't it be better to create an
export function in OpenSesame that packages/zips an experiment in such a
way that it can be directly imported by JATOS? That way, you don't have to
cram everything into one big HTML file, and uphold a 'separation of
concerns' by keeping all images, experiment files and other resources as
they are. I think it also makes it easier to debug osweb experiments in the
long run.
For the osweb source itself, I would say we need to place the osweb en
vendor bundles on some CDN, and uphold a strict versioning system, so users
can always download the osweb version for/with which the experiment was
built, but don't have to redownload these osweb files every time again (I
think osweb plus the vendor source bundles also exceed 1MB already).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/JATOS/JATOS/issues/149#issuecomment-414151857, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH1eBpmIqYi0xEmn-zD5hgW9HUAOYmAdks5uScNQgaJpZM4WBLa2
.

Hej everybody,
looking forward to the osweb integration with JATOS! I just wanted to confirm that the zip import works excellently, even for very large studies. Please don't hesitate to let me know if I can walk you through how we set this up in lab.js!
Cheers, and keep up the awesome work everybody!
-Felix

Thanks for your input guys! I'm just thinking one step ahead already (which is maybe still a bridge too far at the moment), but is it, or will it be possible to do token-based authentication with JATOS? This would allow us to let OpenSesame login on behalf of the user and upload or export experiments directly without the user having to perform the explicit export/import step. We have something similar working for the OSF, which exposes an API that is protected with OAuth2.
An option would be to enable JATOS to work with JWT? I don't know how much of a hassle it is to build something like this, but a lot of (non-Java) frameworks I've worked with offer this kind of functionality out of the box or with simple plugins, so I'm hoping this is relatively easy to realize.

Exporting experiments as JATOS studies might be a good workflow, and it avoids users from having to work with two instances.
Does this mean that all development is done in OSWEB and only if it's ready to use it's exported to a JATOS server? This would be a possibility indeed!

Then about OAuth2 or JWT authentication: We would definitely consider putting this into JATOS if it is needed and wanted by the users. But we would need more information what exactly you want to do.
And I also have an opinion about the the huge index.html (although I'm the back-end guy here ;)). My browser (Chrome and FF) were not able to debug with it because the source code was just to large (at least with this Dogs, Cats and Capybra experiment). But this is just me as a developer wanting to see what's going on under the hood. The participants probably don't mind.

Then about OAuth2 or JWT authentication: We would definitely consider putting this into JATOS if it is needed and wanted by the users. But we would need more information what exactly you want to do.

This basically means exposing your backend API to the public and protecting it by some form of authentication, so that only registered users can access it. This allows other systems or programs to make calls directly to your backend API and interact with it. One possibility is, that it could allow OpenSesame to directly create a study on behalf of a user, and upload the corresponding experiment files, instead of the user having to do this all through the JATOS web interface (which is quite good actually, but it's just convenience  😄).
The most widely adopted authentication system currently is OAuth2, of which you can read a (slightly technical) primer at http://www.bubblecode.net/en/2016/01/22/understanding-oauth2/.
JWT is a token that is received after authentication which can be used by a system or app to identify itself to the backend again and also securely transmit information (see https://medium.com/vandium-software/5-easy-steps-to-understanding-json-web-tokens-jwt-1164c0adfcec). JWTs are
mainly used nowadays in combination with Single Page Apps (SPA's) so I don't know if it's relevant here.


Added Note

Added Note

cc: @MarkusVi
GitHub Issue: https://github.com/MicrosoftDocs/azure-docs/issues/92420

@JamesTran-MSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@JamesTran-MSFT: I'm sorry - only the author of this article, @MarkusVi, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@shlipsey3 can you #sign-off

#sign-off


Impossible to know number of dimensions in c function used by nquad?

Copy of http://stackoverflow.com/questions/42536982. In short, documentation for using a c function states:
f(int n, double args[n])
where n is the number of extra parameters and args is an array of doubles of the additional parameters.

so is it impossible to know from within the c function how many dimensions are being integrated so that correct number of args is used? The provided example doesn't use n but assumes args[0]...args[2] can be used.

IIRC n is the number of dimensions.

But this should be more clear in scipy 0.19.0 (to be released soon).
https://scipy.github.io/devdocs/generated/scipy.integrate.nquad.html#scipy.integrate.nquad

Thanks, so extra parameters really means coordinates? Dev docs still mention args but there is no such parameter anymore.


[PERS-24] [PERS-25] Pattern API Update

NOTE: This update will induce the following breaking changes:

fsm/read-next and the persephone/match-* functions will now return a set of maps, instead of a single map.
The aforementioned maps will have a :state value that is a single state, an :accepted? value that's true if that one state is an accept state, and a new :visited value that is a vec of visited transition IDs.
fsm/profile->fsms now returns a map of :id, :dfa, and :nfa. (The :dfa FSM is what is used for normal pattern matching; the :nfa FSM is used to construct the failure trace.)
fsm/update-children and fsm/pattern->fsm have been made private.
fsm/pattern-tree->fsm has been renamed to fsm/pattern-tree->dfa.
persephone/match-* functions now return ~keywords~ either {:error err-kw} or an empty set with that as metadata, rather than throwing exceptions, if one or more statements have invalid context or (sub-)registration information. (They still throw exceptions if the DFA is invalid.)

In addition to the above breaking changes, here are extending changes:

fsm/read-next now accepts NFAs as well as DFAs; it is dispatched on the :type value of the map.
The NFA construction algorithm now accept an optional meta? argument; if true, the NFAs are returned with a :states map in the metadata.
fsm/pattern-tree->nfa was added to construct an NFA that accepts strings and has associated pattern metadata.
persephone/match-* now associates failure metadata to the return value if that value is an empty set (signifying no more matching).
A pattern.errors namespace has been added to allow for the above failure metadata to be printed.

TODO:

[x] Allow for easy pattern filtering with the API function.
[x] Return list of visited statement templates upon pattern validation error.
[x] Return list of visited patterns upon pattern validation error.

Additional TODOs:

[ ] Change the input of match-statement-(batch)-vs-pattern to match-statement-(batch)-vs-pattern, so that we can apply implicit validation of the requirement "same registration (+ subregistration) => same pattern" to the former.
[ ] Make detailed error traces (including additional NFA compilation + transition ID accretion) toggleable


feat(api): restrict permission to externally validate simulation runs to model repositories and super users

Closes #3612
@bilalshaikh42 this is ready to merge, except this needs to correctly check permissions for machine accounts.

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


Fix a bug due to case sensitivity

(Neo)vim did not recognize the syntax file due to different cases (NONMEM vs nonmem), also in the README the instructions were to set the syntax and file to "nm" which was not recognized either.

Updates  (removes) maintainer

Adds installation instructions

Thanks for the updates!

Thanks for the updates!


postgresql version upgraded to 42.4.1

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Same change is completed a part of different PR.


Fix record delimiting on row group boundaries (#2025)

The CI for #2027 appears to be totally borked, attempting to create a new PR to see if it fixes whatever borkage is going on

No dice


Feature/org prune

Critical Changes
Changes

Adds cci org prune to automatically remove all expired scratch orgs from the keychain (cci org list)

Issues Closed

@bethbrains also be sure to run black and merge changes from master.

@bethbrains thanks for this!


Enable issues to be raised to Kong kafka fork

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
2.4.1
Current Behavior
Per:
https://softwareengineering.stackexchange.com/questions/179468/forking-a-repo-on-github-but-allowing-new-issues-on-the-fork
Can you please open an issues section for:
https://github.com/Kong/lua-resty-kafka as it introduces new fields but am not seeing tests involving those new fields for formatting purposes of my own certs/keys. Would like to either see readme providing more clarification or some sample data.
Would like to raise a point on the:
client_cert
client_priv_key
Fields as reaching of the maintainers via email from the repo's readme was not effective in gaining an answer(the Kong maintainer email does not even exist any longer so guessing left the company):

Or if there is a more appropriate channel or email I could direct this request to for adding issues to your forked repos let me know! I think forked repos by default should enable issues because new functionality can be added that the origin never supports.
Thx,
Jeremy
Expected Behavior
NA
Steps To Reproduce
NA

Anything else?
NA

Hmm after fixing the log since index is nil I see:
[lua] producer.lua:274: buffered messages send to kafka err: , retryable: true, topic: com_eis_dasi_ness_uhgwm110-019282_dev_core, partition_id: 1, length: 1, context: ngx.timer, client: <IP_ADDRESS>, server: <IP_ADDRESS>:8000

and
[lua] producer.lua:183: _send(): retry to send messages to kafka err: nil, retryable: false, topic: com_eis_dasi_ness_uhgwm110-019282_dev_core, partition_id: 1, context: ngx.timer, client: <IP_ADDRESS>, server: <IP_ADDRESS>:8000

@jschmid1  . Would Kong 2.4.1 have the necessary underlying dependencies this kong kafka logging implementation needs?
/ $ kong version --vv
2021/09/27 16:18:49 [verbose] Kong: 2.4.1
2021/09/27 16:18:49 [debug] ngx_lua: 10019
2021/09/27 16:18:49 [debug] nginx: 1019003
2021/09/27 16:18:49 [debug] Lua: LuaJIT 2.1.0-beta3
2.4.1

I would think so since my original SSL connection implementation worked fine before trying this mtls enabled underlying lib yall wrote up in a fork.

@jeremyjpj0916 Yes, kong 2.4.x should work fine.

Thats what I was thinking. Hmm wish the lib gave better insight since a nil or blank err field isn't much help haha. No fault of Kongs since thats original source code behavior, not yalls additions.

The lib indeed isn't very precise in case of errors. We'd absolutely appreciate patches if you happen to find a good way to improve that.

For sure, will add some more debug patching logs to these files and see if we can nail down where the actual issue is.
For the record our config is like so in the higher level plugin:
 "config": {
    "producer_async_buffering_limits_messages_in_memory": 50000,
    "topic": "com_eis_dasi_ness_uhgwm110-019282_dev_core",
    "keepalive": 60000,
    "bootstrap_servers": [
      "server.com:9093",
      "server.com:9093",
      "server.com:9093",
      "server.com:9093",
      "server.com:9093",
      "server.com:9093",
      "server.com:9093",
      "server.com:9093",
      "server.com:9093",
      "server.com:9093",
      "server.com:9093",
      "server.com:9093",
      "server.com:9093"
    ],
    "client_cert": "-----BEGIN CERTIFICATE-----\nXXXXXXXXXXX\n-----END CERTIFICATE----",
    "client_priv_key": "-----BEGIN RSA PRIVATE KEY-----\nXXXXXXXXXXX\n-----END RSA PRIVATE KEY-----",
    "ssl": true,
    "producer_request_acks": 1,
    "producer_request_timeout": 2000,
    "producer_request_limits_messages_per_request": 200,
    "timeout": 10000,
    "producer_request_limits_bytes_per_request": 1048576,
    "producer_request_retries_max_attempts": 10,
    "producer_request_retries_backoff_timeout": 100,
    "producer_async": true,
    "ask_id": "UHGWM110-019282",
    "app_name": "StargateSharedDevCore",
    "producer_async_flush_timeout": 1000,
    "ssl_verify": false
  }

I would think ssl true without requiring the client to do ssl verification is fine for mtls on the client side, meaning client will still send the cert deets over the wire but not require server side verification. Makes it more 1 way TLS but thats fine I just want to auth to the topic over TLS.
And the team providing the kafka topic gives us these deets. I see it has 2 partitions but I am no Kafka expert but imagine thats irrelevant to our errors:

lets close this for now. Feel free to re-create since the original topic is resolved


Which python version is good to test CIL library?

The CIL module is a very good module, please tell me, which version of python is used to test all the tests of this module library, I am currently using version 3.10, and found that there are many other dependent module libraries that do not support it, please Tell me what is the stable test python version, thank you very much for replying to me while helping.

Hi @TianSong1991
CIL is currently built and tested with python 3.8, 3.9 and 3.10 on linux and Windows. Python 3.11 will be supported soon.
Hopefully this helps. Do not hesitate to reopen the issue, if you find that my reply has not solved it.

Thank you for your replying. Python version 3.10 is ok.


bug?  URL of saved map says /(unsaved)/  but the link wokrs

May be a mistake on my part, but why does the path say "unsaved"?
http://onlinewardleymaps.com/(unsaved)#dKoTIcn4EidQsqoAwH

I can recreate this by clicking (unsaved) then saving the map.  Thanks for the issue, I'll work on a fix.


Please detail correct installation procedures.

There are two known ways to install node-red contribs.

Recommended?  Use the Pallette manager.
Use NPM.

I am getting different effects depending on what system I am using this contrib on.  I have installed it on an NT node-red system using pallette manager and it works. (V1.0.4)
My production system, running on a diet-pi system, which has served this contrib for many months, has stopped working. (V1.0.2)
The lasted incarnation of failure is the message: "Please Enable Cookies to Continue""
Under issue 147, I have seen suggestions to run "NPM Update", and the statement "Changed the dependency in the package.json to alexa-remote2 3.2.5 and updated".
This suggests that anyone who uses this contrib has to be a deep coding hacker.
For those of us who only know enough about node-red to use pallette manager, could you PLEASE provide RECOMMENDED installation instructions?
Clearly there are a lot of dependencies that are NOT satisfied by a simple pallette manager install.
Thanks!

Bump


omni_listtransactions in testnet  return empty

I have some transactions on my omni wallet(testnet) , omni_listtransactions return infos when the transaction is going. But renturn nothing where transaction has done.
omnicore-cli -datadir=/data/omni_testnet -rpcport=7832 -port=7833 -testnet omni_listtransactions
[
]
How can i get these transactions in my wallet?
Thanks

I had the same problem. Try to set up optional parameters. It works for me.
https://github.com/OmniLayer/omnicore/blob/master/src/omnicore/doc/rpc-api.md#omni_listtransactions
"*" 10 0 0 1296426
1296426 - max known block

Hey @sjgga,
the RPC omni_listtransactions only lists wallet transactions, so just to clarify: do you have Omni Layer transactions in your wallet?
If you want to watch out for external ones, check out the [omni_listblocktransactions](https://github.com/OmniLayer/omnicore/blob/master/src/omnicore/doc/rpc-api.md#omni_listblocktransactions] RPC.

same for me, parameter doesn't help

I think this is the problem with testnet, because omni_listtransactions on testnet returned me nothing whilst listtransactions was showing some info. I tried this on mainnet and omni_listtransactions worked fine.
So, I guess it's the bug on testnet ;)

I test the results of the testnet
If omni_listtransactions is executed immediately after transfer, it will get a history record, but after a while (10 minutes), the record will be empty again.

I am getting the same results as WuWeiWW.  Using testnet initially omni_listtransactions worked fine, now I get an empty response.  Anyone know why?  And are we certain this is a testnet-specific issue?
Without knowing for sure this only happens on testnet I think I am going to try using the base bitcoin listtransactions, (which I have confirmed still works) then pass each txid to omni_gettransaction.

Hey guys,
can you please test the following:
./omnicore-cli omni_listtransactions 999999 0 0 999999

For the testnet, headers is greater than 1000000 (getblockchaininfo) currently. The default endblock paramter of omni_listtransactions is 999999, which is lesser. Try to use a greater endblock (e.g. 9999999) should help.

For testnet, the headers (with getblockchaininfo) is greater than 1000000; for mainnet, the headers is > 500000. The default endblock paramter of omni_listtransactions is 999999, which is lesser than headers of testnet, but greater than the mainnet. Try to set a greater endblock parameter (e.g. 9999999), it works for me.

@dexX7 - you bet:
$ ./omnicore-0.3.0/bin/omnicore-cli -conf=testnet3/bitcoin.conf omni_listtransactions 999999 0 0 999999
[
]

Thanks a lot @phanalpha, this makes a lot of sense! I pushed a pull request to bump the default.


VDDS configure mu-scope

With version v1.6.0 of the VDDS (see its PR), we can use the mu-call-scope-id to opt-out of delta messages to mu-cl-resources to prevent it from being overloaded.
How to test
Before checking out this branch, inspect the logs of mu-cl-resource and run a healing on the VDDS. Notice the many logs mu-cl-resources generates as it is trying to keep up with the changes.
Then checkout this branch and perform the healing again. There should be no logs, because the data generated comes from the VDDS and should be within the mu-scope that is ignored by the delta-notifier.

@benjay10 thanks


Request for sample for 'writing structured logs'

The following documentation page is missing a code snippet for "Writing structured logs" for C#:
https://cloud.google.com/functions/docs/monitoring/logging#writing_structured_logs
This request is based on sample feedback b/266181393

Closing as a duplicate of #1768


Problem with twilight_evening_nautical() at specific date and observatory

I'm using astroplan to schedule observations, and one of the many tasks is getting the nautical twilight time each night. It worked perfectly for many months, until it unexpectedly broke on the 3rd of November.
The code to reproduce the error is the following:
import astroplan
from astropy.time import Time

date = Time("2022-11-03")
lasilla = astroplan.Observer.at_site("lasilla")
evening_twilight = lasilla.twilight_evening_nautical(date, which="next")

The output:
WARNING: TargetNeverUpWarning: Target with index 0 does not cross horizon=-12.0 deg within 24 hours [astroplan.observer]
<Time object: scale='utc' format='jd' value=nan>

For some reason, it thinks the Sun never crosses the horizon on the 3rd of November.
To troubleshoot, I tried changing the dates, and it works for a day earlier (02/11) or a day later (04/11). So it's specifically with the 3rd of November, and of any year as well.
And apparently this error only appears with "lasilla" at the site of the observer. When I change it to "paranal" it does work. So I'm a bit lost on what could be causing this problem.

Does this FAQ page answer your question? https://astroplan.readthedocs.io/en/latest/faq/precision.html


Acceptance Criteria

[x] Use mysql2
[x] sequelize
[x] dotenv package
[x] Syncs Sequelize models to a MySQL database on the server start.
[x] Includes column definitions for all four models outlined in the Challenge instructions.
[x] Includes model associations outlined in the Challenge instructions.

PR #6


Installation does not work on Mac OS 12.6

Describe the bug
There is no connection to Faderport8. Installation went fine, but no connection. I have checked Control/OSC/web under preferences and there is no CSI installed.
To Reproduce
Steps to reproduce the behavior:
Just followed installation procedure
Operating System

[] Windows 10
[x] Max OS

Versions
Versions can be found on the About page of the installer

Reasonus Installer:
Reasonus Resources: v1.0.1
CSI (ReaSonus): 1.1 (reasonus-edition)

Expected behavior
Faderport should connect to Reaper
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
none

Hi pasicemir, thanx for reporting. Can you check thereaper.ini file for me? I'm interested in the lines starting with: csurf_.
Can you share these lines? This looks like a bug reported before and I thought/hoped it was fixed.
Thanx

Sure:
csurf_0=HTTP 0 8080 '' 'WebRemoteInterface.html' 1 'emir'
csurf_1=CSI 0 0
csurf_2=OSC "" 3 9000 "<IP_ADDRESS>" 8000 1024 10 ""
csurf_3=MCU 0 9 46 47 0
csurf_cnt=2
Den fre. 30. sep. 2022 kl. 12.12 skrev Navelpluisje <
@.***>:

Hi pasicemir, thanx for reporting. Can you check thereaper.ini file for
me? I'm interested in the lines starting with: csurf_.
Can you share these lines? This looks like a bug reported before and I
thought/hoped it was fixed.
Thanx
—
Reply to this email directly, view it on GitHub
https://github.com/navelpluisje/reasonus-install/issues/20#issuecomment-1263379448,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEVTKBE2OFPFSFEF6QJYZWDWA24HPANCNFSM6AAAAAAQZSOS4A
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi there is something wrong with control window in Reaper:
[image: image.png]
It shows just a part of a window and I can not resize it.
Best regards
Emir
Den fre. 30. sep. 2022 kl. 12.12 skrev Navelpluisje <
@.***>:

Hi pasicemir, thanx for reporting. Can you check thereaper.ini file for
me? I'm interested in the lines starting with: csurf_.
Can you share these lines? This looks like a bug reported before and I
thought/hoped it was fixed.
Thanx
—
Reply to this email directly, view it on GitHub
https://github.com/navelpluisje/reasonus-install/issues/20#issuecomment-1263379448,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEVTKBE2OFPFSFEF6QJYZWDWA24HPANCNFSM6AAAAAAQZSOS4A
.
You are receiving this because you authored the thread.Message ID:
@.***>

HI Emir,
Looks like images do not get through when replying by email

Ok, I just sent an image that shows that window of an editor for reasonus
fader in reaper does not show its content fully. Is is also not possible to
close it or resize it.
Best regards
Emir
Den fre. 30. sep. 2022 kl. 16.58 skrev Navelpluisje <
@.***>:

HI Emir,
Looks like images do not get through when replying by email
—
Reply to this email directly, view it on GitHub
https://github.com/navelpluisje/reasonus-install/issues/20#issuecomment-1263684905,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEVTKBAEGWVQI7LEKCDEJILWA35YPANCNFSM6AAAAAAQZSOS4A
.
You are receiving this because you authored the thread.Message ID:
@.***>

Did a small test with the settings from your reaper.ini. After I ran the installer 2 lines were removed as intended. Those are csurf_2 and csurf_3. So this raises some questions:

When did you download the installer?
Did the install finish successfull?
Is there a CSI/Zones/ReasonusFaderPort folder in the REAPER resource folder? (Can be found by going to: Options > Show REAPER Resource....)
I'm not quite sure which window you are reerring to. How did you open that window?

Regards, Erwin

When did you download the installer?

The same day I posted the bug

Did the install finish successfull?

Yes

Is there a CSI/Zones/ReasonusFaderPort folder in the REAPER resource
folder? (Can be found by going to: Options > Show REAPER Resource....)

Yes

I'm not quite sure which window you are reerring to. How did you open
that window?

From Reaper action: reasonus faderport editor

Den søn. 2. okt. 2022 kl. 13.03 skrev Navelpluisje @.***

:

Did a small test with the settings from your reaper.ini. After I ran the
installer 2 lines were removed as intended. Those are csurf_2 and csurf_3.
So this raises some questions:

When did you download the installer?
Did the install finish successfull?
Is there a CSI/Zones/ReasonusFaderPort folder in the REAPER resource
folder? (Can be found by going to: Options > Show REAPER Resource....)
I'm not quite sure which window you are reerring to. How did you
open that window?

Regards, Erwin
—
Reply to this email directly, view it on GitHub
https://github.com/navelpluisje/reasonus-install/issues/20#issuecomment-1264614273,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEVTKBG7AIHLUHFREYMHOHDWBFTXTANCNFSM6AAAAAAQZSOS4A
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hello again,
I managed to get it working, partially. The problem was a MIDI port that was not assigned in Reaper control surfaces preferences. I added it manually and now I can connect to the faderport. But the problem with the ReaSonus Faderport Control is still there. When I start ReaSonus Faderport Control from the action list it opens a window that shows just a part of the control. There are no buttons to close the window and it is not possible to resize it.
I also found another bug on the faderport.
The value bar of the channel that is pan hard left does not show the signal at all. I have to pan the signal either to the middle position or hard left to see the signal.

At least good that it starts working. The iussue with the ReaSonus FaderPort control sounds really weird. Do you by any means have time next sunday to do a call?

Sure, are you located in Europe?
i live in Denmark. I have a recording session sunday, but Tuesday I will
have time afternoon.
Best regards
Emir
Den fre. 14. okt. 2022 kl. 18.02 skrev Navelpluisje <
@.***>:

At least good that it starts working. The iussue with the ReaSonus
FaderPort control sounds really weird. Do you by any means have time next
sunday to do a call?
—
Reply to this email directly, view it on GitHub
https://github.com/navelpluisje/reasonus-install/issues/20#issuecomment-1279190724,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEVTKBEWFR3GGESEWSUDYJLWDF72PANCNFSM6AAAAAAQZSOS4A
.
You are receiving this because you authored the thread.Message ID:
@.***>

Tuesday afternoon will be fine I think. Depends a bit on my work, but will let you know monday

That’s fineOn 14 Oct 2022, at 18.37, Navelpluisje @.***> wrote:
Tuesday afternoon will be fine I think. Depends a bit on my work, but will let you know monday
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


tickets/DM-44689: Add resource limits/requests to prepulled pods

Add limits and requests to prepulled pods.

Rebase when DM-44654 merged.  Also do scriv collect at that point.


Add Ruby-3 support & upgrade to new Klaviyo Client (removing deprecated)

presume we should merge this along with README changes, and then PR the solidus repo


Conditional Stacking/Group Rule

I've though a lot about correlation lately, and how it can help in building lineups.
With that, I was wondering if anyone could assist in the development of additional rules and "conditionals" for the optimizer.
Here are some features that I had in mind:
Conditional Stacking
IF player X appears in a lineup, INCLUDE a minimum 1, maximum 3 of players A,B,C
(IF Terry McLaurin is in the lineup, play AT LEAST 1 player(s) of Amari Cooper, CeeDee Lamb, Dalton Schultz, using a maximum of 3).
or
(If Anthony Davis is in a lineup, play AT LEAST 1 player from a Kemba Walker/Jayson Tatum group)
Additional Stacking Rule
If I remember correctly, several optimizers on the market have rules like "Limit player to 1 from teams, unless stacked with a QB." I would assume that an additional rule will need to be added to the optimizer's features?
Also, specifically in NFL, having a second stack is sometimes beneficial. Could we add a stack rule to include sometime like
optimizer.add_stack(PositionsStack(['QB', ('WR', 'TE')]))
and then
optimizer.add_stack(PositionsStack(['WR', ('RB', 'TE')])) from opposing teams (independent of the first called stack).
Thanks again everyone, I hope this can possibly start conversation.

I would recommend doing this through projections, rather than optimizer rules. There is no requirement that you generate lineups from one set of projections, so you can use a variety of projection scenarios to generate multiple lineups.
In your example above, you would generate a set of projections assuming a QB has a good game, and also the likelihood that the opposing team's output will be increased by the game script. Then optimize on those projections. You can do this for any number of scenarios.
import numpy as np
import pandas as pd

lineups = []
o = get_optimizer(...)

# assume projections csv has the following columns:
# player, pos, team, salary, fppg
df = pd.read_csv('myprojections.csv')

# go through a variety of scenarios
# scenario 1: in LAC vs. NYJ, the LAC QB plays well
# also assume WR & opp WR play better as well

# specify a range of assumptions of how the players
# could deviate from your median projections
qb_low_end = 1.1
qb_high_end = 1.6
wr_low_end = 1.1
wr_high_end = 1.6
opp_wr_low_end = 1
opp_wr_high_end = 1.4

# randomly draw the multipliers for the relevant groups
qb_multiplier = np.random.uniform(qb_low_end, qb_high_end)
qb_wr_multipliers = np.random.uniform(wr_low_end, wr_high_end, size=3)
qb_opp_wr_multipliers = np.random.uniform(opp_wr_low_end, opp_wr_high_end, size=3)

# apply multipliers to projections
scen1 = df.copy()
scen1.loc[scen1.player == 'Justin Herbert', 'fppg'] = scen1.loc[scen1.player == 'Justin Herbert', 'fppg'] * qb_multiplier
... apply to WR / opp WR ...

# now create player objects from dataframe
# row to player is a function you write to create Player objects
players = scen1.apply(row_to_player, axis=1)
o.load_players(players)

for lineup in o.optimize(n_lineups):
    lineups.append(lineup)

@sansbacon This is interesting. Could it be applied in the same way if the csv uses percentile projections instead of deviations? Could these be added to the pandas data frame?
As an extra step, it might be interesting to incorporate correlation coefficients for each player? For example if Matthew Stafford has a good game, typically either of Kenny Golladay or Marvin Jones has a good game (-.453 correlation to one another)

Yes, I think correlation coefficients would be the way to estimate the range of outcomes for the stacked players. So you would start with an optimistic projection for a game or a QB, and then base your projections for the remaining players on that original optimistic projection, which will tend to push players from that game into optimal lineups for that projection set.
The key insight here is that it makes more sense to have different projection sets based on scenarios than it does to make the optimizer insanely complex to account for a variety of rules. Aggregate lineups over many different sets of projections, which will keep the optimizer simple.

@sansbacon If I'm understanding correctly, this would get a bit tedious to write out scenarios for different players/teams, right? Is there a way to generalize this with the randomness in the optimizer?
For instance, if you randomize the projections while running the optimizer, Justin Herbert hitting a x percentile outcome would affect Keenan Allen or Mike Williams' projections by y amount.

One way to do it on a general basis is as follows:

Draw team points scored from a distribution based on historical results given game total and spread
Draw QB points scored from a distribution based on historical results given team points and team/qb data
Draw other player points scored from a distribution based on historical results given team points, QB points scored
Have a corrective mechanism so the total of other player points scored is not too far out of whack with what the QB scored

If you don't want to get that far in the weeds, then I would construct a table of historical results that has columns for fantasy points for QB, WR1, WR2, RB1, TE1, etc. A simple way to determine who is WR1, etc. is to base it on either DFS salary or a rolling average of fantasy points - the WR1 has the highest WR salary or rolling average on the team, and so forth. I think you also would want to round fantasy points to the nearest integer. You could then calculate the probability of other-position fantasy points given QB fantasy points and use that for drawing values.


[build-presets] Foundation built based on platform

What's in this pull request?

Yet another attempt at getting the XCTest build preset to work on both Linux and OS X.
Previously, the XCTest CI preset would attempt to build corelibs-foundation on OS X. corelibs-foundation is not meant to be built via the build-script on OS X, so this would cause issues.
Remove the explicit --foundation option, and instead leave it up to the build-script to determine whether to build corelibs-foundation when building XCTest.
Resolved bug number: None

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

@shahmishal Unfortunately https://github.com/apple/swift-corelibs-xctest/pull/77 looks like it still failed on OS X. I think this change could get things working...

@swift-ci Please test and merge

Thanks, @shahmishal! Could you ask @swift-ci to please test https://github.com/apple/swift-corelibs-xctest/pull/77 again? :bow:


Babylon dict dumper

I observe plans underway to improve and import new dicts. It would be enormously valuable to be able to dump such data into babylon format (and also trivial for @akprasad ). This remains true whether or not the resultant dump is to be shared publicly or privately, automatically triggered or not.
@akprasad might now be familiar with the babylon format from https://github.com/sanskrit/ambuda/issues/2 . Very simple (3 lines per entry, with  replacing newlines in definitions and headwords separated by |.)
HEADWORD_1|HEADWORD_2
DEFINITION
EMPTY_LINE

अऋणिन्
अऋणिन्

पदविभागः - विशेष्यनिघ्नम्
कन्नडार्थः - ಋಣವಿಲ್ಲದ / ಸಾಲವಿಲ್ಲದ
व्युत्पत्तिः - न ऋणी |
प्रयोगाः - “दिवसस्याष्टमे भागे शाकं पचति यो नरः । अऋणी चाप्रवासी च स रात्रिञ्चर मोदते” ||
उल्लेखाः - भा० ।
विस्तारः - [ऋ ಕಾರಕ್ಕೆ ವ್ಯಂಜನತ್ವವನ್ನು ಒಪ್ಪುವುದರಿಂದ ಇಲ್ಲಿ “नृट्” ಆಗಮವು ಬಂದಿರುವುದಿಲ್ಲ.]

Does the DEFINITION need to follow any specific structure? If I produce arbitrary XML, is that still usable?

Does the DEFINITION need to follow any specific structure?

Html or plain text is what we seek there. A limited set of HTML tags are acceptable (unfortunately I don't have a definitive list). If in doubt, just assume that all html tags are ok - that'll be least burdensome on you; and if there are very minor adjustments to be made I can request later.

If I produce arbitrary XML, is that still usable?

Not directly - so, far more preferable to get a babylon which can be plugged in downstream directly.

This is simple work, but it has two hidden costs:

Opportunity cost. Time for this project is limited; I implement this, that's time I can't spend on another feature.
Maintenance cost. I have slightly less flexibility in the future if I need to make big changes to the dictionary output, since I'll also need to support this script that supports a minor feature.

The ambuda.seed.dictionaries scripts are quite clean and it's easy to delete the database write logic and write out a babylon file instead.
Since I am Ambuda's only contributor right now, I wish to focus as much as I can on core features. If you feel very passionately about this data dump, I'm happy to accept a pull request and offer "as-is" support, i.e. the script might break in the future.

Fair points - I would've liked to the dumper to access your database (rather than the source files, which might be private in some cases, and inconsistent in format) though. Is there a way I can access it from a python script running on - say - my desktop? That would be perfect- I could then take care of the dumping script.

Sorry, I can't grant direct access to the DB. For now, though, all of the dictionary sources I use are public, and the scripts will fetch them automatically from specific URLs that I've checked in.
https://ambuda.readthedocs.io/en/latest/ for repo setup and how to run the DB scripts.
Once I start using private dictionary data, I'll give this issue higher priority. I can see how it would be difficult to do without DB access.


Fix the construction of the Shelley initial UTxO

Base the initial UTxO entries on the address used in the initial funds,
and export a function for use by wallets and CLI tools to do the same.
This means that the pseudo TxIn to use to spend funds from the initial
UTxO is purely a function of the address, and not a function of the
whole initial funds. This makes it much easier to explain and easier
to use in tools that have to construct spending transactions.

This is an alternative approach to #2017

bors merge


Add the participant events to the notification service Android

Add following events to the notification service:

participant joined
participant left

Only Android work. Flutter and iOS to be done in separate ticket.

This ticket contains work for both Flutter and Android.


Java component template using Gradle, the Gradle Kotlin DSL, and the Gradle wrapper

NOTE: This template will not work until Gradle Kotlin DSL support and Gradle wrapper support are added into GDK
Description of changes:
This adds a template that uses Gradle, the Gradle Kotlin DSL, and the Gradle wrapper
Why is this change necessary:
I have a lot of code that uses the Gradle Kotlin DSL and the Gradle wrapper and I'd like to use it with GDK
How was this change tested:
I published my own simple Hello World component with it
Any additional information or context required to review the change:
This build script adds a little extra intelligence when building and publishing to let the user know where to go to find information about the values they need to set. I do think it's useful but I could see it being removed if we want a more minimal script.
When executing ./gradlew build this code will correctly set the component version number by reading it from the gdk-config.json so it doesn't need to be in the gdk configuration and the build script. If the version is set to NEXT_PATCH the JAR will use 1.0.0 as the version number so gdk can find it.
When executing ./gradlew publish this code will also run the build task so the user doesn't need to do ./gradlew build or gdk component build and then gdk component publish. They still have the option of publishing without building by using gdk component publish directly. But generally in my development process I want to do both at the same time.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

If all of the fancy stuff isn't desired everything below line 37 can be deleted and then this can be used in its place:
tasks.shadowJar {
    archiveFileName.set("${project.description}-1.0.0.jar")
}


New option to use d-pad as analog stick for NGC

For bartop/arcade cabinets where only a d-pad stick is available, enable this option to use it as the analog control stick on Gamecube. Many games can be playable with this option - which can be configured system-wide or on a game-by-game basis.
Needs the corresponding PR on configgen/dolphinControllers.py (which is being added at the same time)

conflict

Useless now that https://github.com/batocera-linux/batocera.linux/pull/1066 is automatic.


font.compileGlyph is missing

this was quite useful for building accented glyphs using anchors… can we add it?
# old RoboFab code, doesn't work in fontParts

f = CurrentFont()

accentsDict = {
    'Aacute' : ['A', [('acute', 'top')]],
    'ccedilla : ['c', [('cedilla 'bottom')]],
}

for accentedGlyph, (baseGlyph, accents) in accentsDict.items():
    f.compileGlyph(accentedGlyph, baseGlyph, accents)

+1

This always seemed very limited to me. Maybe if the construction format was more robust it could come back. @typemytype didn't you do some work on a better system?

@typesupply see https://github.com/typemytype/GlyphConstruction

GlyphConstruction is great, I’ve used it in recent projects.
Still, having f.compileGlyph would be nice for compatibility with older scripts.


Proxy pattern

PyMOL's RPC server doesn't pre-register methods anymore but exposes the API via a proxy pattern.

Thanks!


Camo dropped your images; your readme is torched

It's torched on npm too

Thanks @StoneCypher for reporting. Looking into that

Fixed now. Great thanks for reporting

Semi-confirmed.
Don't know if you care, but the second table of colors on NPM shows as narrow strips rather than squares.

Thanks, I see it as:

What browser are you using?

Ah.  It's about width.
I discovered it because at my initial zoom, they were "normal" looking in Firefox, but zero-width and therefore invisible in Edge.  Then I decided to take screenshots.  After the firefox screenshot, and I went back to Edge, I decided to take them with the inspector out, so that you could see metrics.  Then I had to go back to Firefox, and on opening the inspector, I saw it go from looks fine to what the hell
You can see it happen here
To stop this, observe that GitHub has a minimum width, and remove probably two columns, so that the color chips will still be at full width once the column is at minimum width.
The effect in the video has been successfully replicated on evergreen-current Chrome, Edge, and Firefox, all on Win10 pro x64

@StoneCypher great thanks for explaining in detail.
Indeed it doesn't look good in narrow window
As I check, I would either need to restructure the table so it has fewer items in a row (max 5 I assume) or insert an image instead.
I'll leave it open for now

yeah i think 5 is prolly max
note: what the hell is actually a technical term

I've actually updated it, so it's presented via image.
If you have a better idea let me know, but I consider it as addressed at this point.
Great thanks for reporting it!

Thanks for ping. It was just published (CI is already configured, I just needed to bump version in package.json).


Add getSearchParams util in UrlUtil

Proposed Changes
Added a small util to that parses the current url and returns the search params as an object. I added a new lib at the same time that handles query-strings in a graceful way. I will need this lib in some incoming PR.
I didn't do any tests for that one because its simply impossible to mock window.location in any way with jasmine :hankey:
Potential Breaking Changes
None
Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

Codecov Report

Merging #1311 into add-missing-hoc-table-utils will not change coverage.
The diff coverage is n/a.

@@                     Coverage Diff                      @@
##           add-missing-hoc-table-utils    #1311   +/-   ##
============================================================
  Coverage                        99.44%   99.44%
============================================================
  Files                              362      362
  Lines                             9082     9082
  Branches                          2146     2146
============================================================
  Hits                              9032     9032
  Misses                              50       50

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 77449ee...ed3ad1e. Read the comment docs.


onComplete(root()) callback sometimes not invoked when defined in several models

Describe the bug
When plugging several models with onComplete(root()) hook, the onComplete() callback is is only performed for the model that was added first.
Expected result
onComplete() is performed for all models regardless of the import order
Actual result
onComplete() only performed for the first model
Additional information
May not be an actual bug, but iirc this behavior is not described in the docs
Link to a minimal sample project reproducing the issue or runnable sample code
https://github.com/kateabr/instancio_on_complete_example
Please run OnCompleteTest for a reproducible example.

Java version: 17
Instancio version: 5.0.1

@kateabr thanks for raising this issue and the sample project! From what I can tell, it is working as expected. Having said that, it's a pretty complicated example, so I don't fully understand all the pieces and maybe I misunderstood something.
When the models get combined, if there are multiple equal selectors, then the last selector wins. A simplified example would be this:
@Test
void callbacks() {
    record Foo(String value) {}

    Instancio.of(Foo.class)
            .onComplete(root(), value -> System.out.println("Callback 1: " + value))
            .onComplete(root(), value -> System.out.println("Callback 2: " + value)) // overwrites the first onComplete()
            .create();

// Sample output:
// Callback 2: Foo[value=ZKWYN]
}

This behaviour applies to regular selectors (e.g. Select.field() and Select.all(Class)) as well as the root() selector.
You might be able to workaround this by replacing root() with an  equivalent predicate selector:
Instancio.of(Foo.class)
        .onComplete(types().atDepth(0), value -> System.out.println("Callback 1: " + value))
        .onComplete(types().atDepth(0), value -> System.out.println("Callback 2: " + value))
        .create();

// Sample output:
// Callback 2: Foo[value=FHXVXL]
// Callback 1: Foo[value=FHXVXL]

In this case, both callbacks are called because predicate selectors can't overwrite each other (because there's no equals() for predicates).
I'm not sure if this addresses your question since your example is much more complicated. If you could simplify it to the absolute minimum, I could look into further.

Thank you for your answer!
I suspected they could be overwriting each other, but then, as you said, one would expect the last selector to win, not the first one?
I tried replacing root() with types().of(X) and types().of(X).atDepth(0) and it does work, but in my particular case (as in the first version of my example) the entities have multiple cyclic references, so the callback ends up being invoked twice.
I've simplified my example, so please have a look again

@kateabr thanks for updating the sample. It made it much easier to see what's going on. I just merged a PR  (#1160) that should fix this issue. Could you please try 5.0.2-SNAPSHOT to verify? You might need to add the snapshot repository:
<repositories>
    <repository>
        <id>oss-snapshot-repository</id>
        <url>https://s01.oss.sonatype.org/content/repositories/snapshots</url>
    </repository>
</repositories>

Works like a charm, thank you!

I just pushed version 5.0.2. It should be available from Maven central shortly. Let me know if you run into any other issues.


[CIRCLE-CI] Optimize CircleCI Cache Keys to Reduce Excessive Storage Use

Problem
This PR aims to address the issue of excessive storage use in our CircleCI builds by optimizing the cache key patterns. Previously, our cache keys included both the branch name and a checksum value, which led to the creation of numerous cache entries and increased storage consumption. By removing the branch name from the cache keys, we can significantly reduce the number of cache entries and improve cache hit rates, ultimately optimizing our storage usage.
Solution
Cache Key Optimization:

Removed Branch Name from Cache Keys: The branch name ({{ .Branch }}) has been removed from all cache key patterns. The new cache keys now rely solely on the checksum value ({{ checksum "/tmp/checksum.txt" }}).
Affected Jobs: This change has been applied to all jobs that include restore_cache and save_cache steps in the .circleci/continue_config.yml file.

One-line summary:
Optimize CircleCI cache keys by removing branch names to reduce excessive storage use and improve cache efficiency.
Checklist

[ ] You've signed-off your work
[ ] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[ ] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] Your comment includes a one-liner for the changelog about the specific purpose of the change (not required for changes to tests, docs, or CI config)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2024 contributors to the OpenLineage project

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

Project coverage is 85.52%. Comparing base (3cb3e1c) to head (2b7021c).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2982   +/-   ##
=======================================
  Coverage   85.52%   85.52%
=======================================
  Files          58       58
  Lines        3413     3413
=======================================
  Hits         2919     2919
  Misses        494      494

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


Use an older version of numpy for compatibility with Python3.6

numpy==1.21.6 is not compatible with Python 3.6. This downgrades the numpy version
to 1.19.5 for compatibility with Python 3.6.

@shivadbhavsar is there a minimum numpy version we need for the torch-migraphx to function correctly?

Is numpy here only used for testing? If so, this will have no effect on torch migraphx. If its needed for functionality past just testing then it might be an issue. Torch migraphx looks for numpy > 1.20

@shivadbhavsar is there a minimum numpy version we need for the torch-migraphx to function correctly?

Is numpy here only used for testing? If so, this will have no effect on torch migraphx. If its needed for functionality past just testing then it might be an issue. Torch migraphx looks for numpy > 1.20

Yes, numpy here is used for testing(in the Python virtual environment) only.

All CI checks pass except the following two:

continuous-integration/jenkins/pr-head saying This commit cannot be built.
Jenkins - clang_release

@causten when you get a chance, can you please share the error for the Jenkins failures? I am not able to access Jenkins to see the logs. Thanks!


[Mention The Feature]: Adding Search Bar On Project Page

Is your feature request related to a problem? Please describe.
Currently, users may find it challenging to locate specific types of projects on the project page due to the lack of a Search option. This makes it time-consuming to browse through a large list, especially when users are searching for projects that fit certain categories or criteria.
Describe the solution you'd like.
With this feature, users will be able to quickly narrow down the list of projects to match their preferences, making it easier to find relevant projects and improving overall navigation and user experience.
Describe alternatives you've considered.
Add a filtering option on the project page, allowing users to sort and filter projects based on criteria such as category, status, date added, or popularity.
Additional context.
Please add gssoc-ext labels and assign me this issue
Show us the magic with screenshots

Search bar like this above the list of projects make it easier for the user to browse.
Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

Hi, Thank you for raising the issue.
But for now it is not required.
So I am closing this issue.
Please understand.
And one more thing this project is already inactive including me also due to some of my works.
Please do contribute to other projects.
I hope you understand.


Chat QoL: Tab completions - Server-side only

This is only the server-side stuff necessary for tab completion.
(This is cherry-picked from https://github.com/0x0ade/CelesteNet/pull/26)
The server now has some basic info about:

what sort of first argument a command expects
which commands are aliased to which
the auth tags required and it'll be smart about sending the list (regular players won't get /kick as a completion option)

... and it can send this info to the client.

If a client doesn't understand the DataCommandList DataType it will just be ignored and current clients run as usual.
If we merge & release this first, dev clients could properly evalute https://github.com/0x0ade/CelesteNet/pull/26 on the live server.

Things to note:
The using static Celeste.Mod.CelesteNet.DataTypes.DataCommandList; is probably a bit of a sin?... I threw that into every ChatCMD... class just so that I could use the enum CompletionType values there...

Accidentally merged the entirety of #26 into this and even with a revert, the whole commit history is trashed here now, so closing here and opened new PR with new cherry-pick branch...
#46


Google V3 Recaptcha error on order without account

PHP Version
8.1.28
Shopware Version
<IP_ADDRESS>
Affected area / extension
Platform(Default)
Expected behaviour
Finishing my order without an account
Actual behaviour
The provided value for captcha
"Shopware\Storefront\Framework\Captcha\GoogleReCaptchaV3" is not valid.

How to reproduce

Enable Google ReCaptcha v3 in the basic information tab from Shopware backend with the 2 correct corresponding captcha keys
Add a product to cart
Fill in user data and address
Try to finish order

The user data gets filled in on page https://domainhere.com/checkout/register and after pressing the button to finish order you get redirected to https://domainhere.com/account/register with the corresponding error. This is default shopware flow.

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-38111
[created from NEXT-38111, comment 491610]

[public] We were unable to reproduce the error on several end devices. Could you go deeper into the analysis? It should be this method that causes the error “https://github.com/shopware/shopware/blob/v<IP_ADDRESS>/src/Storefront/Framework/Captcha/GoogleReCaptchaV3.php#L28“.
Possible causes of the error could be the following

Are the keys stored correctly? ( perhaps a space at the beginning or end, keys swapped)
Is your system allowed to communicate externally? In particular with the Google endpoint
Validate the response from Google

[created from NEXT-38111, comment 494703]


Happens "Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node." on https://remix.run/

What version of Remix are you using?
v1.4.1?
Steps to Reproduce

Convert any language with Google Translate  of Chrome extension.

Keep scrolling down

Will see errors on the website.

Expected Behavior
No errors are displayed.
Actual Behavior
Console
DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
    at Ys (https://remix.run/build/_shared/chunk-AGZHEPHC.js:7:5603)
    at Yf (https://remix.run/build/_shared/chunk-AGZHEPHC.js:9:3820)
    at L.unstable_runWithPriority (https://remix.run/build/_shared/chunk-AGZHEPHC.js:1:4026)
    at rn (https://remix.run/build/_shared/chunk-AGZHEPHC.js:5:38448)
    at Ge (https://remix.run/build/_shared/chunk-AGZHEPHC.js:9:1807)
    at yi (https://remix.run/build/_shared/chunk-AGZHEPHC.js:7:11071)
    at https://remix.run/build/_shared/chunk-AGZHEPHC.js:5:38670
    at L.unstable_runWithPriority (https://remix.run/build/_shared/chunk-AGZHEPHC.js:1:4026)
    at rn (https://remix.run/build/_shared/chunk-AGZHEPHC.js:5:38448)
    at Cs (https://remix.run/build/_shared/chunk-AGZHEPHC.js:5:38616)
ui @ chunk-AGZHEPHC.js:7

Seems to be https://github.com/facebook/react/issues/17256

Issue migrated to the remix website (private) repo.

So, what is the correct solution for this problem?

@regchiu Did you fix this problem already ?

@regchiu Did you fix this problem already ?

No. This issue should have been listed as a special issue by the team to deal with. Probably not solved yet.

@regchiu Did you fix this problem already ?

No. This issue should have been listed as a special issue by the team to deal with. Probably not solved yet.

I have no idea about this bug. Would you mind to explain that for me 😄 ? @regchiu
I try to use i18next to changing multi-language (by choose language in app setting and detect by web browser settings).
Then I try to use npm run build and deploy this web. The problem happens when I turn on gg translate in Chrome and Safari in iPhone @@. It said the same error with your case.
Thank you very much @regchiu. Please help me explain this error 😥

@tmhuyy
It should be that Google Translate will change the DOM, causing such an error.(https://github.com/facebook/react/issues/11538#issuecomment-390386520)
I saw someone discussing that currently preventing browsers from automatically asking for translation can temporarily solve this problem caused by users accidentally using Google Translate.(https://github.com/facebook/react/issues/17256#issuecomment-1022045269)

@regchiu
Thanks for your help 😀 Have a great day


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/527 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit 5e0dc28:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/sql-database-engine.png
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


compile error: undefined reference

I download and build leveldb according to this README, and then properly add libleveldb.a and the include/leveldb directory (header files) to my environment path.
My test code:
/*leveldb_test.cpp
 */

#include <iostream>
#include <sstream>
#include <string>
#include <leveldb/db.h>

using namespace std;

int main(int argc, char** argv)
{
    leveldb::DB* db;
    leveldb::Options options;
    options.create_if_missing = true;

    leveldb::Status status = leveldb::DB::Open(options, "./testdb", &db);
    assert(status.ok());

    return 0;
}

And I compile it as:
g++ leveldb_test.cpp -o leveldb_test -lpthread -lleveldb -std=c++11

It produces "undefined reference" errors:
leveldb_test.o: In function `main':
leveldb_test.cpp:(.text+0x79): undefined reference to `leveldb::DB::Open(leveldb::Options const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, leveldb::DB**)'
leveldb_test.cpp:(.text+0x29e): undefined reference to `leveldb::Status::ToString[abi:cxx11]() const'
collect2: error: ld returned 1 exit status

What is the problem?
My environment: Linux version 3.10.0-327.el7.x86_64 - gcc version 4.8.3 20140911 - Red Hat 4.8.3-9
Thanks for any advise.

When you say you "add libleveldb.a and the include/leveldb directory (header files) to my environment path" what exactly are you doing? What environment variables?
What happens if you:
g++ leveldb_test.cpp -o leveldb_test -lpthread -Lpath/to/dir/with/leveldb/lib -lleveldb -std=c++11

Because I have not root access to install leveldb globally, I copy libleveldb.a into /home/myname/usr/lib, and leveldb/include/leveldb into /home/myname/usr/include.
Then in /home/myname/.bash_profile I append:
export C_INCLUDE_PATH=$C_INCLUDE_PATH:/home/myname/usr/include
export CPLUS_INCLUDE_PATH=$CPLUS_INCLUDE_PATH:/home/myname/usr/include
export LIBRARY_PATH=$LIBRARY_PATH:/home/myname/usr/lib
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/myname/usr/lib

Afterwards source .bash_profile .
(Here am I missing something ?)
When I try:
g++ leveldb_test.cpp -o leveldb_test -lpthread -L /home/myname/usr/lib/ - I /home/myname/usr/include/ -std=c++11

the output is again:
/tmp/ccm4vVhs.o: In function `main':
leveldb_test.cpp:(.text+0x24): undefined reference to `leveldb::Options::Options()'
leveldb_test.cpp:(.text+0x79): undefined reference to `leveldb::DB::Open(leveldb::Options const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, leveldb::DB**)'
leveldb_test.cpp:(.text+0x29e): undefined reference to `leveldb::Status::ToString[abi:cxx11]() const'
collect2: error: ld returned 1 exit status

You shouldn't need to set any of the environment variables above because you are using the -I and -L options and they are searched first. I think you're missing -lleveldb when you invoke g++.

I commented out
# export C_INCLUDE_PATH=$C_INCLUDE_PATH:/home/myname/usr/include
# export CPLUS_INCLUDE_PATH=$CPLUS_INCLUDE_PATH:/home/myname/usr/include
# export LIBRARY_PATH=$LIBRARY_PATH:/home/myname/usr/lib
# export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/myname/usr/lib

and re-source .bash_profile.
And I try again g++ command:
g++ leveldb_test.cpp -o leveldb_test -lpthread -lleveldb -L /home/myname/usr/lib/ - I /home/myname/usr/include/ -std=c++11

(ps:  I did indeed always have -lleveldb invoking g++ but error copy in my last comment above)
But error still exits......

I did a test and it works fine for me. Here's a Makefile:
leveldb_test: leveldb_test.cpp Makefile
	g++ leveldb_test.cpp -o leveldb_test -lpthread -lleveldb -L build -I include/leveldb -std=c++11

I noticed that you have - I instead of -I (extra space).

I commented out
# export C_INCLUDE_PATH=$C_INCLUDE_PATH:/home/myname/usr/include
# export CPLUS_INCLUDE_PATH=$CPLUS_INCLUDE_PATH:/home/myname/usr/include
# export LIBRARY_PATH=$LIBRARY_PATH:/home/myname/usr/lib
# export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/myname/usr/lib

and re-source .bash_profile.
And I try again g++ command:
g++ leveldb_test.cpp -o leveldb_test -lpthread -lleveldb -L /home/myname/usr/lib/ - I /home/myname/usr/include/ -std=c++11

(ps: I did indeed always have -lleveldb invoking g++ but error copy in my last comment above)
But error still exits......

I hava the same problem, do you solve it?

Have you installed the snappy?

I did have the exact same error and this worked for me:
g++ sample.cpp -o sample -I/..path../deps/leveldb/include -L/..path../deps/leveldb/lib -lleveldb -lpthread -std=c++11
to mention a stupid mistake that took me minutes to know it, this was not working for me (moving options to the beginning):
g++ -I/..path../deps/leveldb/include -L/..path../deps/leveldb/lib -lleveldb -lpthread -std=c++11 sample.cpp -o sample
Also @cmumford is right about - I thing in your compile script

Do any one solve this？ I still have this problem with leveldb 1.22

Same problem, use clang++ replace g++ resolve this. Hope this would be helpful.
On Ubuntu 20.04 arch amd64, I install libleveldb-dev, gcc, clang from official repo:
$ dpkg -l | grep leveldb
ii  libleveldb-dev:amd64           1.22-3ubuntu2                         amd64        fast key-value storage library (development files)
ii  libleveldb1d:amd64             1.22-3ubuntu2                         amd64        fast key-value storage library

$ g++ --version
g++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ clang++ --version
clang version 10.0.0-4ubuntu1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

$ cat getting_started.cc
#include <cassert>
#include <leveldb/db.h>

int main() {
  leveldb::DB *db;
  leveldb::Options options;
  options.create_if_missing = true;
  leveldb::Status status = leveldb::DB::Open(options, "/tmp/testdb", &db);
  assert(status.ok());
}

Use g++ has the same problem but clang++ is OK.
$ g++ -lleveldb getting_started.cc
/usr/bin/ld: /tmp/cchC3JJd.o: in function `main':
getting_started.cc:(.text+0x2a): undefined reference to `leveldb::Options::Options()'
/usr/bin/ld: getting_started.cc:(.text+0x7b): undefined reference to `leveldb::DB::Open(leveldb::Options const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, leveldb::DB**)'
collect2: error: ld returned 1 exit status

$ clang++ -lleveldb getting_started.cc
$ ls
a.out  getting_started.cc

Try the below, library mentioned as last of argument -
$ g++ getting_started.cc -lleveldb

Hi everyone, I am trying to install leveldb on my machine.
I have proceeded with cloning the source of level db. I have followed the documentation.
I have build the source with cmake on my linux mint.
Now I'm trying to test the code on the doc with this command-line :
g++ main.cpp -I ~/projects/leveldb/leveldb/include
Then it gives me the following error : main.cpp:(.text+0x1f): undefined reference to leveldb::Options::Options()'`
I'm a beginner with leveldb. If you can help me, I would be very happy. Thank you in advance. :)

Hi everyone, I am trying to install leveldb on my machine. I have proceeded with cloning the source of level db. I have followed the documentation. I have build the source with cmake on my linux mint.
Now I'm trying to test the code on the doc with this command-line : g++ main.cpp -I ~/projects/leveldb/leveldb/include
Then it gives me the following error : main.cpp:(.text+0x1f): undefined reference to leveldb::Options::Options()'`
I'm a beginner with leveldb. If you can help me, I would be very happy. Thank you in advance. :)

I guess you need -L /path/to/leveldb-static-library


Add packaging, tests, and CI

This PR does the following:

Adds packaging using a declarative setup.cfg in combination with pyproject.toml (which allows for skipping having a setup.py)
Adds a simple test and configuration for running with tox
Adds a GitHub action that runs the tests via tox

Great, thanks!

@bgyori should be good, I added the little extra config necessary for using the non src-layout :)


 I'll try to repro tomorrow and get back with a fix

Hi @mikestaub I was not able to repro your error. It's running fine for me. But I have cleaned up the file a bit and also requirements.txt.. Please give it a try once more and lmk if it's still broken for you.

How are you passing the URLs to the app? I still get 422 errors. Here is the response:
{
    "detail": [
        {
            "type": "missing",
            "loc": [
                "body",
                "event_id"
            ],
            "msg": "Field required",
            "input": {
                "data": [
                    "what is this tool?"
                ],
                "event_data": null,
                "fn_index": 0,
                "session_hash": "jc1v2dszb08"
            },
            "url": "https://errors.pydantic.dev/2.4/v/missing"
        }
    ]
}

I simply pass the url in the chat

That doesn't work for me on Sonoma 14.2 with M3 max chip

@mikestaub its working fine. its issue with your system i guess. please use python 3.10 & create new enviroment & try it.

you can open the issue if you face any problem


add a speaker series page under resources

create a speaker series page to post recordings and advertisements/registration links for upcoming events
similar to https://www.pih.org/pages/covid-webinar-series

Close by Speaker series #125


 See documentation.

:robot: Created releases:

v0.5.0
:sunflower:


zafiro-icons: 0.7.9 -> 0.8

Motivation for this change
Update to version 0.8
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Thanks :sparkler:


[Suggestion] Add Windows Insider signing option (for Microsoft Development PCA 2014)

Applying a WDAC policy to a Windows Insider build in block mode can/will have severe consequences as binaries are signed with Microsoft Development PCA 2014 which is obviously not in the default rules. Suggestion to add this as an option in the GUI.

Applying a WDAC policy to a Windows Insider build in block mode can/will have severe consequences as binaries are signed with Microsoft Development PCA 2014 which is obviously not in the default rules. Suggestion to add this as an option in the GUI.

@AndreasStenhall all of our templates have rules to allow the flighting root (Development PCA 2014)

Did you perhaps disable flight signing?

I did not disable Flight signing. I guess the problem is that the template "Signed and reputable" does not contain Flighting Root 2014, but the other two templates Default Windows Mode and Allow Microsoft Mode do contain Flighting Root 2014.

I don't think it was intentional to leave the flighting root off the Signed and Reputable template so I'm going to keep this bug open and evaluate updating the template. Thanks!


peers connection error

2024-06-28T09:25:48.483975Z  WARN sync::controllers::serial: No peers available to connect self.tx_seq=216

it creates a huge amount of logfile size, i think there's a problem with the autosync


[Container] Log split not taking effect for DLedger in container

BUG REPORT

Please describe the issue you observed:

What did you do (The steps to reproduce)?
Container has 3 brokers for each node.

What is expected to see?
Logs belonging to different brokers should be output to different directories.

What did you see instead?
The log is output by defaultAppend, that is, the log is output to the same directory

Please tell us about your environment:

branch: 5.0.0-beta
Linux

Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
The logger for different brokers can't be found because brokerId for dLedger may be changed. We should use dLedgerId to replace brokerId for dLedger mode.

Merged


style css not being applied

Added styles below to css files, but being ignored.
Any ideas?
.dg-btn--ok {
border-color: green;
}
.dg-btn-loader .dg-circle {
background-color: green;
}

@v-cagome I think this is due to the fact that the styles are injected just before the close of the head tag.
This means that your custom style will probably be above the injected style and it will be overridden.
A quick fix will be to make the custom style important. ie:
.dg-btn--ok {
border-color: green !important;
}

.dg-btn-loader .dg-circle {
background-color: green !important;
}

The best solution will be to make the style injection optional. That way, users can just link the css file in the head tag.

Now you can use custom components and style has been extracted into a separate file to be included manually


Fixed H2StreamStateMachine to ignore certain frames in the closed state

This PR fixes state transitions in H2StreamStateMachine to ignore WINDOW_UPDATE and RST_STREAM frames when stream is in the closed state. Also added tests to reproduce these scenarios.
Quote from RFC 7540 (https://tools.ietf.org/html/rfc7540#section-5.1):
closed:
      The "closed" state is the terminal state.
      ...
      WINDOW_UPDATE or RST_STREAM frames can be received in this state
      for a short period after a DATA or HEADERS frame containing an
      END_STREAM flag is sent.  Until the remote peer receives and
      processes RST_STREAM or the frame bearing the END_STREAM flag, it
      might send frames of these types.  Endpoints MUST ignore
      WINDOW_UPDATE or RST_STREAM frames received in this state, though
      endpoints MAY choose to treat frames that arrive a significant
      time after sending END_STREAM as a connection error
      (Section 5.4.1) of type PROTOCOL_ERROR.
      ...

@pgjones @Lukasa please review changes
Fixes #1183

This looks good to me. I've merged manually as I accidentally created a merge commit on this PR.

Thanks!