gets_s does more than the documentation describes

Switching from gets to gets_s caused my program to crash. I did not know the length of the buffer so I entered a really big number. The gets_s does what the documentation describes but it also continues to put stuff into memory after the terminating null character. It pads 0xFE to every byte after the terminating null character up to the length of the buffer.

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

ID: 7e6a3b86-cdb0-2d96-d61b-38dd9f4964e0
Version Independent ID: 02427c3f-c55c-8fac-4784-693679c0de71
Content: gets, _getws
Content Source: docs/c-runtime-library/gets-getws.md
Product: visual-cpp
Technology: cpp-ucrt
GitHub Login: @corob-msft
Microsoft Alias: corob

Closing as duplicate of #1668.


When RPC 0.5 Become starndard endpoint

Is your feature request related to a problem? Please describe.

[ ] Refactor waitForTransaction with getTransactionStatus
[ ] Remove waitForTransaction pascalToSnake fix

Resolved in v5.23.0


DO NOT MERGE (PUP-7008) acceptance: hiera v5 can use hiera v3 config and datafiles

i probably have to re-target this at stable


✅ Fix backend tests failing if FIRST_SUPERUSER_PASSWORD is not "changethis"

See discussion here: https://github.com/tiangolo/full-stack-fastapi-template/discussions/1135#discussioncomment-9508587
This was changed in the following PR: https://github.com/tiangolo/full-stack-fastapi-template/pull/632
Changing it back to settings.FIRST_SUPERUSER_PASSWORD makes it work again.
I think the issue is that after this test, the password is changed to something else and the other tests can't authorize.
There was another fix in that discussion here: https://github.com/tiangolo/full-stack-fastapi-template/discussions/1135#discussioncomment-8938134
Don't know what is preferred, let me know.

Forgot to add...
To reproduce:

Clone master
Edit FIRST_SUPERUSER_PASSWORD in .env to something other than "changethis"
docker compose up
Exec into backend container
5.bash ./scripts/test.sh

Hi @alejsdev. Before I merge, there was another comment here on this: https://github.com/tiangolo/full-stack-fastapi-template/discussions/1135#discussioncomment-10078421
Should we consider this? I think the API functionality is still tested, but the commenter is right that the actual password change isn't really tested...
I think one solution is caching original password, changing it, testing the change, and then resetting it back to the original.

I see, I think it would be better to create a new user and use it to reset his password or using @swelborn approach because changing the password of the first superuser would break the other tests, and using the same password doesn't make much more sense, I think it would be better to refactor this test cc @tiangolo :thinking:

I see, I think it would be better to create a new user and use it to reset his password or using @swelborn approach because changing the password of the first superuser would break the other tests, and using the same password doesn't make much more sense, I think it would be better to refactor this test cc @tiangolo @estebanx64  :thinking:

Hey @javadzarezadeh and @alejsdev - I see that you both approved this. Could merge for now to avoid tests failing for new users, and then refactor a different way with a new issue?


⚠ ClamAV has degraded performance

In 66a1f76, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 71 ms

Resolved: ClamAV performance has improved in b553a98.


bunt#PlainTextLength does not return the correct size

Running the following unit test
Expect(bunt.PlainTextLength("\x1b[0;32mINFO \x1b[mNo dependencies found")).To(BeEquivalentTo(len("INFO No dependencies found")))

one would expect the two values to be the same, as both the green color as well as the color reset should be ignored in the PlainTextLength method.
The unit test fails with "Expected 29 to be equivilant to 26". I personally didn't have the time nor energy to look into why that issue comes up so I don't have more insight on why it happens

Should be fixed by PR #11


Impossible to access kano/weacast services

The following error is raised when accessing weacast or kano services:
type: 'FeathersError', name: 'Forbidden', message: 'You are not allowed to access service xxx', code: 403, className: 'forbidden'
Probably a side-effect of https://github.com/kalisio/aktnmap/issues/341.

Related to the permissions system cache. As the distributed services are not immediately available on app startup, if a user logs in before they appear his abilities have been computed and stored in cache without access to these services.
We should either refresh the cache each time a new service pops-up (could be costly) or at least force a cache update each time a user logs in/out to mitigate this.

Waiting for https://github.com/kalisio/kdk/issues/888.


Is this project already abandoned? v2.0

v1.0 #824

Maybe it's better to find new fresh and inspired maintainers which can handle all of the exhausting problems.

@akiran can you comment?

There are so many open PRs and a lot of other people who would love to help out and spend some time and energy in this project. @akiran would be nice if you could at least comment it.

@akiran Could we reopen maintainers discussion?

Maybe it's better to find new fresh and inspired maintainers which can handle all of the exhausting problems.


Automate installation and configuration of libvirtd/nova-compute/neutron-openvswitch-agent

this is compute node plan, not the kolla ,right? so all those stuffs deploy on VM/baremetal directly?

completed


core api: add header definitions for native interface

Co-authored-by: Jose Ulises Nino Rivera<EMAIL_ADDRESS>Signed-off-by: Mike Schore<EMAIL_ADDRESS>Description: Introduces the interfaces for the core API.
Risk Level: Low
Testing: CI

@mattklein123 I am assuming that you're talking about any unary API. Could you help me understand your preference of not exposing an unary APIs at this layer?
From my perspective, there needs to be some layer which exposes a unary/streaming API for the end consumer. If we don't do it on this layer, the platform layers would need to handle the distinction between the two types of calls.

Could you help me understand your preference of not exposing an unary APIs at this layer?

It is my experience that not accounting for streaming at every layer creates large architectural issues/debt that will have to be dealt with later. I think it's in our best interest to only expose streaming as far up the stack as possible. Unary APIs are trivial wrappers around the streaming APIs and can be done at the top layer.

Thanks for the explanation @mattklein123!

Regarding exposing streaming APIs, I replied in a thread here but want to reiterate for visibility:
I primarily want to make sure we understand the trade-offs of exposing the unary APIs from the C layer versus the Swift/Kotlin (platform) layers and that we're all on the same page with what those mean:
Exposing from C layer

Unary + streaming APIs are available from C layer
Unary will call into streaming APIs under the hood within this layer
Platform layers can call directly into unary or streaming depending on their need (for v0.2, it'll just be unary), minimizing their logic

Exposing from platform layer

C layer only has streaming APIs
Native layers have both streaming and unary APIs (just unary for v0.2)
Both native layers have logic to bridge from unary requests to C streaming APIs

I definitely see the value in only exposing streaming APIs from the C layer, as long as we're okay with duplicating some amount of logic between iOS/Android with regard to bridging unary APIs back to streaming requests. Thoughts @mattklein123?

Thanks for the summary @rebello95, that is representative of my thoughts with a couple additional things
Exposing unary signatures from C layer

Depending on implementation we have to implement buffer handling/ownership for both cases.
In fact for 0.2, I think, there would be no streaming callsites in the platform layer

Exposing unary signatures from the platform layer

Implementing duplicate code in both platform layers is the biggest point against pushing the unary signature up the layers. I guess as far as implementing twice goes, this is probably one of the most innocuous points. But I think that it is something that shouldn’t go unchecked.

I think we can make it work both ways and both have tradeoffs. @goaway brought up a good point with the fact that we gave both call patterns the same callback struct so both are handled the same in that direction w.r.t the C layer. Moreover, this would allow us to reevaluate more easily if need be.

I definitely see the value in only exposing streaming APIs from the C layer, as long as we're okay with duplicating some amount of logic between iOS/Android with regard to bridging unary APIs back to streaming requests. Thoughts @mattklein123?

Yeah, my preference is for duplication right now at higher layers, mainly because the logic to do this is trivial. This will force us to think through all of this from a "streaming first" perspective. Once more code is written, if we decide to push some unary interfaces back down the stack, I think that is reasonable. WDYT?

Thanks for clarifying @junr03.

Yeah, my preference is for duplication right now at higher layers, mainly because the logic to do this is trivial. This will force us to think through all of this from a "streaming first" perspective. Once more code is written, if we decide to push some unary interfaces back down the stack, I think that is reasonable. WDYT?

This is fine with me. If we decide to move some unary interfaces into the C layer later on, it should be relatively trivial to toss code out from the native/platform layers and shift it. For now we can expose streaming-only APIs from C and provide ergonomics in Swift/Kotlin for unary.

@mattklein123 any other comments?

thanks all 🚀


"file sharing enabled" rollback action doesn't fully activate file sharing

launchctl load -w /System/Library/LaunchDaemons/com.apple.smbd.plist; defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist EnabledServices -array disk
required an additional step of enabling users for smbd (available through UI) - need an equivalent for CLI.

Additionally, this rollback depends on "local firewall disabled" rollback action.

done


testing: improve grouping, labeling, rate limits, & scheduling of dependency updates

Significant bundling of non-major updates, sliced by language and mono-repo component
Adjust schedule to match a 2 week sprint cycle
Expand the volume of PRs opened by Renovate at one time, so a more complete backlog is populated
Give dependencies 3 days to stabilize before we pull them in. We rely on dependabot for time-sensitive security updates.
Add labels to dependency updates to raise visibility on major/minor/patch updates for reviews
Switch to JSON5 so we can have comments!

Good news! Once per merge this, we can use the dependency dashboard issue to cause Renovate to revise already existing PRs. This means we are able to iterate if any given renovate change is bad.


Son-access package signing and auth. partial implementation

retest this please

retest this please

retest this please

retest this please


Bangladesh Premier League Analysis

ML-Crate Repository (Proposing new issue)
:red_circle: Project Title : Bangladesh Premier League Analysis
:red_circle: Aim : Analyze and visualize the matches of BPL for the 2021-22 season.
:red_circle: Dataset : https://www.kaggle.com/abdunnoor11/bpl-data
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.
Hello, ML-Crate contributors, this issue is only for the contribution purposes and allocated only to the participants of SWOC 2.0 Open Source Program and JWOC '22 Open Source Program.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'SWOC' and 'JWOC' contributors of 'ML-Crate' project.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Participant ID :
Approach for this Project :
What is your participant role?

[ ] SWOC 2.0 Participant.
[ ] JWOC 2022 Participant.
[ ] Contributor

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Hi
Full Name: Vishnu Bhaarath
github profile link:https://github.com/VishnuBhaarath
Approach: Have gone through the dataset, would be take differnt factors in to account and doing visualization in python.
Participant role: JWOC 2022 participant
Can you assign this issue to me

Issue assigned to you @VishnuBhaarath

Issue assigned to you @VishnuBhaarath

Hi @abhisheks008  have given a PR


Stanley development

Please review

Thank you @hengelman and @kyrabusser for all your thoughts and advice. I really appreciate it. This is my first time using GitHub, I'm really doing my best in learning how to use the platform more efficiently. 😄  Please pardon my many errors 😆  Thanks again everyone!

So glad you're stretching and learning new things! One thing I noticed is that you marked this PR as closed--is that intentional, or do you want to reopen it?

So I need some clarifications. Do I need to create a new pull request each time there's a conflict, like do I need to close the current PR and create a new PR with the implemented changes after I have resolved the conflict?
What is the most effective way to resolve conflicts on GitHub (rewriting the code) without having to go back to my text editor?
Assuming I went back to my text editor to rewrite the code, how do I update it on the current conflicted PR without having to create a new PR from my console?
How do I make sure the code in my local computer is always up to date with the master on GitHub?
Thanks
@kyrabusser @hengelman @CharlesArday

I know that's a lot of questions 🤣 Please pardon me. I'm just trying to get better 🙂

Questions are great! Thanks for asking them and learning new things! :smile:
Nope, you don't need to make a new PR--in fact, if you keep using the same one, then we can all see the history. As long as you're making the changes in new commits and pushing them up to your same branch, they'll show in the PR. But no worries about this for this one--we can just continue in #10 :+1:
You can edit code or resolve conflicts using the GitHub web interface, but I think I would recommend going back to your text editor instead. That way we're only editing in one place, and the flow is more consistent.
A pull request is asking to merge one branch into another, and a branch can be a whole series of many commits. That means you can add new commits to the same branch, then push them to GitHub, and they'll be part of the same PR.
To keep your local code up-to-date, use git pull origin master early and often! This will grab all the latest changes from GitHub and put them in your local code. If necessary, this will also create a merge commit, and if there are conflicts it will warn you about them and make you resolve them locally. See the CodeU site here: https://sites.google.com/codeustudents.com/spring-2019/codeu-toolbox/reference-guides/using-git#h.p_Ru9ON8xbx9fC
Hope that helps! Please always let me know when questions come up. :+1:


added school info file

@ArielSegal1 file/lib/domains/il/org/amit365.txt: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.


Some pegs are inconsistent on the maps

Peg states in D2 and D6 have been reported to be out of sync on the dungeon maps. Other dungeons may also have the same problem.

D6 looked correct to me, I went over it twice with debug mode.


Feature/strm 1763

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


Where can I download the theme of this site? https://learn.getgrav.org/16

Really?..
https://getgrav.org/downloads/themes

@lufog
I found the theme of this website is learn4, but I didn't find it here.

Learn4 is not a 'released' theme yet, because i've not had time to clean it up and make it ready.  You can mess with it by downloading directly: https://github.com/getgrav/grav-theme-learn4


Links - construct, use, empty

Build links in a predefined order
Have miners send energy to other links
Have upgraders refill from controller link
Set all creeps to pull from storage link if it is full.
Add factotum creep to manage energy flow in core structures.
Make sure observer program doesn’t freak out in the sim.

Beginning of a terminal management system.

resolves #68

This Pull Request has been merged by GitConsensus.
Vote Totals

Yes
No
Abstain
Voters

3
0
0
3

Vote Breakdown

User
Yes
No
Abstain

tedivm
✔

dragoonreas
✔

PostCrafter
✔

Vote Results

Criteria
Result

Has Quorum
True

Has Votes
True


g-cli did not show any warnings or errors when using the deprecated (2.x) --timeout argument

I have a build that used the g-cli 2.x and was utilizing the --timeout argument, which has been renamed --connect-timeout.  I was getting build errors that g-cli was timing out connecting and that seemed odd. I then did a g-cli --help and noticed there was no --timeout argument and it took me a few scans of the list of args to realize that it had been renamed.
Things that would have helped me (just a few ideas):

support the deprecated argument names as aliases to the new argument names
show a deprecation warning when using deprecated arguments
show a warning or error message when g-cli receives and unknown argument

Thanks!

Hmm this should already be aliased, I'll added some testing in case the aliasing is broken and see if I can detect it and generate a warning


Implement "native" leader selection using cosmos-sdk staking module

ref: https://github.com/celestiaorg/optimint/issues/18

Duplicate of https://github.com/rollkit/rollkit/issues/815


[Bug] Transactions that fail to execute the finalize function are not rejected

🐛 Bug Report
Transactions that fail to execute the finalize function are not rejected.
Steps to Reproduce

Create a transaction Tx whose finalize result is wrong (intentional).
Broadcast the transaction Tx.
In the logic of the node executing the produce_next_block() -> propose_next_block() -> prepare_advance_to_next_block() -> speculate() -> atomic_speculate() function, because the finalize execution of the transaction Tx fails, a ConfirmedTransaction will be created, we call it CTx, whose type is RejectedExecute, contains a Fee transaction. CTx will be returned as a transaction in the new block.
The node executes check_next_block() to check the new block, and executes the atomic_speculate() function again. Because there is a Fee transaction in the transactions of the new block, according to the logic of atomic_speculate(), the program reports an error "Cannot speculate on a fee transaction".

Expected Behavior
This case should be rejected and the fee consumed, otherwise a malicious transaction can be sent to the network.
Your Environment

snarkOS: 796de94816d6b8aa238c51468f0398fe0170bc14
snarkVM: 0.12.6
rustc: 1.69.0
OS: Ubuntu 18.04.5 LTS

您好，我已收到您的邮件。我将尽快给您回复。

Closed with https://github.com/AleoHQ/snarkVM/pull/1736


[PROPOSAL] Investigate alternative release version management

Purpose:
Currently, we use bump2version when managing release versions across the different integrations and client libraries. This results in silly version issues, such as seen in this commit.
Other version management solutions exist, such as versioneer, which don't require regex find/replace scripts. We should evaluate those alternatives and fix the issues that cause release issues, such as the one mentioned above.

Added versioneer for client/python to my local tree here: https://github.com/OpenLineage/OpenLineage/compare/main...mobuchowski:versioneer?expand=1


Log Output should be saved to file automatically

What would you like to be added:
when running the eks-a CLI, log output should be automatically output to file as well as to stdout
Why is this needed:
in cases where an SSH connection to a mgmt machine is terminated, but the CLI is still running, there is no way to recover the log output in a reliable way; we should set up a way where this can be recovered more easily.

It would be beneficial to have this also always output verbose logs so that we have that output when a user doesn't specify verbose logging.


Add support for preflight check configuration

What this PR does / why we need it:
This adds configuration file support (preflightRules) for preflight checks. Each preflight check must add a SetConfig() method to accept configuration from the Preflight registry.
Which issue(s) this PR fixes:

Fixes #899
Does this PR introduce a user-facing change?

Add support for preflightRules configuration

Additional Notes for your reviewer:
Review Checklist:

[ ] Follows the developer guidelines
[ ] Relevant tests are added or updated
[ ] Relevant docs in this repo added or updated
[ ] Relevant carvel.dev docs added or updated in a separate PR and there's
a link to that PR
[ ] Code is at least as readable and maintainable as it was before this
change

Additional documentation e.g., Proposal, usage docs, etc.:

Proposal https://github.com/carvel-dev/carvel/pull/729

Looks good to me apart from Bryce's comment. Should we add/update the preflight permissions e2e tests with a config example? (I am okay with just the unit tests as well)
Would would also have to add the preflight option in the configuration docs.

I'll create a new PR for the docs.
The unit tests cover the code as written. IMHO, an e2e would be more appropriate once a preflight check adds configuration settings; otherwise, the e2e would effectively be a duplicate test.


Speed up cygwin path transformation.

Reported in issue #299

I wonder if maybe another thing you may want here is to execute this caching only if we're running under cygwin?


HDF crash with int3d-type fields

The attached Regent code hdf_int3d_field.txt crashes on my local machine with:
HDF5-DIAG: Error detected in HDF5 (1.8.16) thread<PHONE_NUMBER>87392:
  #000: ../../../src/H5D.c line 358 in H5Dopen2(): not found
    major: Dataset
    minor: Object not found
  #001: ../../../src/H5Gloc.c line 430 in H5G_loc_find(): can't find object
    major: Symbol table
    minor: Object not found
  #002: ../../../src/H5Gtraverse.c line 861 in H5G_traverse(): internal path traversal failed
    major: Symbol table
    minor: Object not found
  #003: ../../../src/H5Gtraverse.c line 641 in H5G_traverse_real(): traversal operator failed
    major: Symbol table
    minor: Callback failed
  #004: ../../../src/H5Gloc.c line 385 in H5G_loc_find_cb(): object 'cell' doesn't exist
    major: Symbol table
    minor: Object not found
HDF5 error on dset_id = H5Dopen2(info->file_id, hdf5_info.dsetname->c_str(), H5P_DEFAULT):
HDF5-DIAG: Error detected in HDF5 (1.8.16) thread<PHONE_NUMBER>87392:
  #000: ../../../src/H5D.c line 358 in H5Dopen2(): not found
    major: Dataset
    minor: Object not found
  #001: ../../../src/H5Gloc.c line 430 in H5G_loc_find(): can't find object
    major: Symbol table
    minor: Object not found
  #002: ../../../src/H5Gtraverse.c line 861 in H5G_traverse(): internal path traversal failed
    major: Symbol table
    minor: Object not found
  #003: ../../../src/H5Gtraverse.c line 641 in H5G_traverse_real(): traversal operator failed
    major: Symbol table
    minor: Callback failed
  #004: ../../../src/H5Gloc.c line 385 in H5G_loc_find_cb(): object 'cell' doesn't exist
    major: Symbol table
    minor: Object not found
a.out: /home/manolis/sw/legion/runtime/realm/transfer/channel.cc:1527: virtual long int Realm::HDFXferDes::get_requests(Realm::Request**, long int): Assertion `0' failed.
Aborted

It looks like the attached code is expecting an int3d field named cell to be blasted out into 3 separate fields called cell.__ptr.x, cell.__ptr.y, and cell.__ptr.z, but I think this has been recently changed in regent (in order to make dependent partitioning operations work properly).  @elliottslaughter , can you confirm that the field fusing (un-splitting?) we did is intended for hdf5 attachment as well?

Also note that this example has been minimized as far as it can go. In particular, dumping the region only once (rather than twice, as this example does) does not cause a crash. The code also works if you skip the for-loop before the dumping.

Yes, you'll need a minimum set of things to occur before the Legion runtime admits that it actually has to write data to the HDF5 file on disk, which is when the mismatch between the field name provided by regent during the attach operation and the dataset names in the HDF5 created by the app becomes apparent.

@streichler is right, the fields were fused in deppart and the fusion applies everywhere (we can't fuse the field for runtime calls and then unfuse it for HDF5). HDF5 does support compound data types, so this means you'll need to tweak the code that generates the HDF5 files to define the type of the the struct before first use. E.g.:
https://support.hdfgroup.org/HDF5/Tutor/compound.html

@manopapad Were you able to get past this issue?

I haven't had the time to try this yet. I'll update the issue when I have. Or you can close it right now if you prefer, and I'll reopen if it's still not working.

I got this working by creating a compound HDF datatype. For posterity, here's how to properly set that up:
struct Foo {
  bar : int3d;
}
terra hdf5create(filename : &int8) : {}
  var fid = HDF5.H5Fcreate(filename, HDF5.H5F_ACC_TRUNC,
                           HDF5.H5P_DEFAULT, HDF5.H5P_DEFAULT)
  var sizes : uint64[1]
  sizes[0] = INDEX_SPACE_SIZE
  var int3dType = HDF5.H5Tcreate(HDF5.H5T_COMPOUND, 24)
  HDF5.H5Tinsert(int3dType, "x", 0, HDF5.H5T_STD_I64LE_g)
  HDF5.H5Tinsert(int3dType, "y", 8, HDF5.H5T_STD_I64LE_g)
  HDF5.H5Tinsert(int3dType, "z", 16, HDF5.H5T_STD_I64LE_g)
  var dataSpace = HDF5.H5Screate_simple(1, sizes, [&uint64](0))
  var dataSet = HDF5.H5Dcreate2(fid, "bar", int3dType, dataSpace,
                                HDF5.H5P_DEFAULT, HDF5.H5P_DEFAULT, HDF5.H5P_DEFAULT)
  HDF5.H5Dclose(dataSet)
  HDF5.H5Sclose(dataSpace)
  HDF5.H5Tclose(ptrType)
  HDF5.H5Fclose(fid)
end


langchain, community: Implement GraphDB QA Chain

Description: Implement GraphDB QA Chain
Issue: N/A
Dependencies: N/A
Twitter handle: @OntotextGraphDB

I've synced this branch with the master branch. @baskaryan, @eyurtsev, @hwchase17, please, approve the workflows again and provide feedback. Is there anything else I should do, so this PR is merged?

Hello @baskaryan . Thank you for the quick reply. I completely agree with you and I've deleted all example files and heavily reduced the size of the changes. I've also renamed classes containing "GraphDB" to "OntotextGraphDB" (note that you proposed "OntoTextGraphDB", but "Ontotext" is a company name and it's written with lowercase "t") and added links to the website for clarity in the classes docs. Please, approve the workflows.

awesome stuff, thank you @nelly-hateva!!


 All of the helpers correspond to something more mathematical in the paper (ie, omega(), gamma(), etc.). I just used the English names of all of those functions.
I defined everything using the math base module instead of numpy or pandas, because I figured that would be the best way to keep things simple and let us check with the paper. That means nothing is vectorized, though.
Definitely check my work with respect to the big function, and any of the helpers. The biggest mistake-prone place is that everything in code has to be in radians (because of how Python works), but the authors are constantly referring to degrees. I did by absolute best to try and make sure that everything lined up, but I may have missed one or two degree units.

@BostonTLee Silly python question here- why do you have to pass the class (cls variable) into every function in the class? Also, your class works like 80% well. I'm just going to have to make some small tweaks to get the numbers to work just right but it is producing results.

@akiehl2000 The cls variable essentially references the class as a whole. These are all class methods, meaning they are intented to be used without instantiating an object. However, they still need to be able to see each other. Usually when methods are associated with an object, they see each other through the self implicit variable, but the standard for class methods is cls. The only other way to get the methods to see each other while they are included in a class is to prefix calls with the class name, like AstronomicalAdjustment.func(), which is too verbose.
Once you push your changes, I can add decorators to make things more clear.

I left the main at the bottom for now for testing. Once we're confident that all our methods are doing what we want, we should remove this.
The only thing I could find in the paper that we haven't accounted for is daylight savings time which would be tough and I'm not sure how much of an impact it would make (though it definitely has a non-zero impact).


Automated cherry pick of #10608: fix: time sync duration

Cherry pick of #10608 on release/3.7.
#10608: fix: time sync duration

/lgtm

/approve


Add Lab4 Task1. Does not intend to add Task2.

Thanks for your contributing！

will be deployed after I finished lab4 task2


运行报错

Traceback (most recent call last):
File "D:/deyaTrade/test_api", line 82, in
tt = TestTrade(front_trade, broker, investor, pwd, appid, auth_code, proc)
File "D:/deyaTrade/test_api", line 23, in init
self.t = CtpTrade()
File "C:\Program Files\python36\lib\site-packages\py_ctp\trade.py", line 49, in init
self.t = Trade()
File "C:\Program Files\python36\lib\site-packages\py_ctp\ctp_trade.py", line 36, in init
self.h = CDLL(absolute_dllfile_path)
File "C:\Program Files\python36\lib\ctypes_init_.py", line 348, in init
self._handle = _dlopen(self._name, mode)
OSError: [WinError 126] 找不到指定的模块。

用的是https://pypi.org/project/py-ctp/的测试代码


Preview mode for draft & preview posts

Next has a preview mode for viewing non-public posts.
The WP + Next example has instructions on how to do auth, and how to implement preview mode.
WP is going to need to link to the correct API routes for previewing, which can be accomplished via filters

New WP has application passwords that might make this easier.
https://wptavern.com/wordpress-5-6-to-introduce-application-passwords-for-rest-api-authentication

New WP has application passwords that might make this easier.
https://wptavern.com/wordpress-5-6-to-introduce-application-passwords-for-rest-api-authentication

WP engine has a new headless framework that might make both the Next and WP sides simpler to implement:
https://github.com/wpengine/headless-framework/tree/canary/docs/previews

@ccorda, I’ve been trying to figure out preview mode for Wordpress today to see how Next’s built in option and the Headless Framework implemented it. While I understand the headless framework’s implementation of a /preview route is preferable and redirecting to Wordpress login is nice, it looks pretty complicated to roll out both on the WP and Next side without just switching to their framework.  If we wanted to do that, just grabbing that functionality piecemeal would take me a while as I don’t really understand how all the pieces work together.
Next.js built-in preview mode’s technical setup makes sense to me and we could expand it to behave more similarly to Headless Framework, specifically by making a /preview catch-all that checks for preview mode and either redirects to the page in preview mode if the preview mode cookies are set OR redirects to Wordpress login, and then post-login, starts preview mode through Wordpress and redirects back to the page in preview mode. We could show a black bar on the top of the page when in preview mode with a link to edit post & exit preview mode too.
I’m not sure how to proceed further at the moment, please let me know when you have a few minutes and let’s hop on a call and figure it out.

Preview mode has been implemented for several months now, closing.


Add banner ads support

@PabloReszczynski, could you please, marge the pull request (I do not have permissions to do it) and create a new version and tag / update packagist version (https://packagist.org/packages/topsort/sdk).
I will then reference this version in Magento extension's composer.json: https://github.com/Topsort/magento-topsort/blob/master/composer.json


Page Says Feature Is Preview...Has Been Announced On Yammer as GA

This page still refers to this as a Preview feature.  On Yammer it was announced as being in GA (https://www.yammer.com/azureadvisors/#/threads/show?threadId=924551419158528).

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

ID: 597c9b5f-f41f-400c-f4da-8bc8159d366a
Version Independent ID: 5b993db0-eb4c-11ce-83a2-3c577be2eebc
Content: Prevent accidental deletion - Azure file shares
Content Source: articles/storage/files/storage-files-prevent-file-share-deletion.md
Service: storage
Sub-service: files
GitHub Login: @roygara
Microsoft Alias: rogarana

Thanks for reporting this. I have assigned the issue to the content author to investigate further and update the document as appropriate.

Thanks for reaching out, we've gone ahead and made updates to both soft delete articles. They'll be live later today.
Accordingly, I'll close this out:
#please-close


Nice with new 7.2.0 but not solving all things

Great to get a new version 7.2.0 and now the integration can start on HA 2023.10.3 with OS 11.0. without errors.
The integration now start without errors, but still not able to start P2P stream that worked fine with HA 2023.9.x
WebRTC also got updated to 3.4.0 during this time.
Any ideas?
Thanks,
Ase

sharing the device with me or sharing the logs :)

Do you have their T8220-Z doorbell with Homebase T8020 and it works for You?
Please advice how to activate proper log levels for you to troubleshoot and how to deliver those to you,
Don’t want to share all logs to openly here, they can include secrets that I missed to sanitised.
Thanks,
Ase

I have;

2C
indoor pan tilt
S100

follow the readme file and you can post them to<EMAIL_ADDRESS>Your password is part of add-on and integration would not fetch it, so it should be safe to share over email.

Checked the readme file now several times. Cannot see the log level you want and what exact logs.

Event image is not updating either whenever there is motion or person detected. I have an S100.

I have S100 camera at home and event image is working fine. So, it is a specific thing probably missing on your setup we need to find out. @amatt09 , what do you want me say here, I do not now.
Garden Event Image changed to October 16, 2023 at 17:46
17:46:22 - 4 hours ago

Garden Event Image changed to October 16, 2023 at 17:41
17:41:40 - 4 hours ago

@AseKarlsson , sorry, I meant, debug template, not readme.

@fuatakgun , it was pa art of the readme. But no info there on log level or what files to send.

you know, the issue is that, this bug was not created properly. Instead of deleting the bug template with all the contents and replacing whatever you want to write, we would not be having this discussion right now.
But, interestingly, I have been having this conversation many times. I have explicitly called out in the bug template that, without logs, I will resolve the issue, so I must do it and you should follow the template.
Without this, I will automatically resolve this issue

I have;

2C
indoor pan tilt
S100

follow the readme file and you can post them to<EMAIL_ADDRESS>Your password is part of add-on and integration would not fetch it, so it should be safe to share over email.

If you do not have more devices from them I understand that the support for this integration is hard :(

Eufy would not give us devices, this is an unofficial integration and I am sure they even do not like us.

I know your integration is an unofficial and thankful for your wok. Let’s hope you get this working again!


collaboration

Hi, I am looking for a collaboration on a project - are you reachable?

Yes. Brother, Sent from Mail for Windows From: gamefispaceSent: Wednesday, April 13, 2022 11:22 AMTo: truewill06/Bitcoin-Random-Seed-CheckerCc: SubscribedSubject: [truewill06/Bitcoin-Random-Seed-Checker] collaboration (Issue #2) Hi, I am looking for a collaboration on a project - are you reachable?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID<EMAIL_ADDRESS>
ok, let me shoot you an email

Hi, I am having trouble trying to search you on discord - it shows I need to add 4 digits after the username you have shared to be able to search your handle.


fix: dep update

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add provider type to charts

Adding the provider type the charts and bump the chart versions

This should go in before #13 as that one will require the charts to be modified again.


add optional prerender callback

@elnarddogg, first, sorry for the delay. This has been sitting here for quite a while to be pulled.
Can you please explain the scenario a bit where you need prerender? Also, you elected next() as the fallback, in case user has not utilized this new option. Would it not be so that calling next() in pre-rendering step change the intended order of execution?


using in LXC container  cent8 to rocky fails immediately

this is the error:
Can't find EFI mount.  No EFI  boot detected.
An error occurred while we were attempting to convert your system to Rocky Linux. Your system may be unstable. Script will now exit to prevent possible damage.

Can you please show the /var/log/migrate2rocky.log file?

that's all there is in there

If you can't show the entire migrate2rocky.log file then I can't help you, there is certainly much more in it than what you have shared.

I agree with that, there's actually nothing else in there, I assume from running it over and over.  would running the script 'set -x' be helpful?  I  can also just stand up a fresh centos8 container and see what happens with that.

What is the command you're using to run migrate2rocky?

Same problem here.
cat /var/log/migrate2rocky.log
Can't find EFI mount. No EFI boot detected.
My command was: ./migrate2rocky.sh -r

What is the command you're using to run migrate2rocky?

migrate2rocky.sh -r

Okay, yes, can you add set -x to the top of the script and show the output?

Same issue here. It fails after not finding /boot/efi:
+ local efi_mount kname
+ declare -g -a efi_disk efi_partition
++ findmnt --mountpoint /boot/efi --output SOURCE --noheadings
+ efi_mount=
+ exit_message 'Can'\''t find EFI mount.  No EFI  boot detected.'
+ errmsg '
Can'\''t find EFI mount.  No EFI  boot detected.

'
+ local msg
+ msg_format msg '
Can'\''t find EFI mount.  No EFI  boot detected.

'
+ local _var
+ _var=msg
+ shift
+ ((  1 > 1  ))

Can't find EFI mount.  No EFI  boot detected.

An error occurred while we were attempting to convert your system to Rocky Linux. Your system may be unstable. Script will now exit to prevent possible damage.

 A log of this installation can be found at /var/log/migrate2rocky.log

I think I see what's happening here.  Does LXC bind mount /sys from the host system?  I think what is happening is the host system is EFI mounted so the /sys which is bind-mounted and a copy of the one on the host is showing that EFI boot exists, but the container itself doesn't do EFI boot, and can't access the EFI partition from the host.  I think that if the EFI partition isn't found then we should simply turn off EFI boot processing and allow the script to continue.

Yes it is mounted from the host system including /sys/firmware/efi/.
One possible solution would just to ignore it and carry on if no EFI partition is not mounted. But if a user has chosen to not mount the EFI partition for whatever reason the system would fail to boot.
Another possible solution would be to check if it's running inside a container (for ex. with systemd-detect-virt). This utility is included with the main systemd package and should therefore be present on all supported operating systems.

Another possible solution would be to check if it's running inside a container (for ex. with systemd-detect-virt). This utility is included with the main systemd package and should therefore be present on all supported operating systems.

This is a good idea, I'm going with this one.

@tastle73 @tryano @andrin55 can you test with this version, please:
https://github.com/pajamian/rocky-tools/tree/issue74/migrate2rocky

@tastle73 @tryano @andrin55 can you test with this version, please:
https://github.com/pajamian/rocky-tools/tree/issue74/migrate2rocky

Thank you it worked.
If anyone else is running an unprivileged LXC CentOS 8 container: There is a bug with the filesystem package (https://bugzilla.redhat.com/show_bug.cgi?id=1589968#c20). The workaround does not work since the /etc/rpm/macros.dist file seems to gets overwritten when running the script. In my case migration was successful when removing the exit code check on line 793 from distro-sync.

If anyone else is running an unprivileged LXC CentOS 8 container: There is a bug with the filesystem package (https://bugzilla.redhat.com/show_bug.cgi?id=1589968#c20). The workaround does not work since the /etc/rpm/macros.dist file seems to gets overwritten when running the script. In my case migration was successful when removing the exit code check on line 793 from distro-sync. Another option would be to try it with --exclude=filesystem.

That workaround should work with any file named macros.*, can you try this before running the script and see if it works:
printf '%s\n' '%_netsharedpath /sys:/proc' > /etc/rpm/macros.migrate2rocky
...if it works I'll incorporate it into the script.

If anyone else is running an unprivileged LXC CentOS 8 container: There is a bug with the filesystem package (https://bugzilla.redhat.com/show_bug.cgi?id=1589968#c20). The workaround does not work since the /etc/rpm/macros.dist file seems to gets overwritten when running the script. In my case migration was successful when removing the exit code check on line 793 from distro-sync. Another option would be to try it with --exclude=filesystem.

That workaround should work with any file named macros.*, can you try this before running the script and see if it works:
printf '%s\n' '%_netsharedpath /sys:/proc' > /etc/rpm/macros.migrate2rocky
...if it works I'll incorporate it into the script.

It worked.

@andrin55 can you try with this version of migrate2rocky and see if it works properly?  It should create and remove the macros file as needed for containers: https://github.com/pajamian/rocky-tools/blob/issue74/migrate2rocky/migrate2rocky.sh

@andrin55 can you try with this version of migrate2rocky and see if it works properly? It should create and remove the macros file as needed for containers: https://github.com/pajamian/rocky-tools/blob/issue74/migrate2rocky/migrate2rocky.sh

Worked flawlessly. No errors while installing, no files left in /etc/rpm/ after migration. I think this issue can be closed. Thank you for your work.

Changes merged.


osm2pgsql: 1.10.0 → 1.11.0

Description of changes
https://github.com/osm2pgsql-dev/osm2pgsql/releases/tag/1.11.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 289548 run on x86_64-linux 1

1 package built:

osm2pgsql

Result of nixpkgs-review pr 289548 run on x86_64-darwin 1

1 package built:

osm2pgsql

The only concern I have is whether we are supposed to move packages to by-name by hand as it is done in this PR.

From https://github.com/NixOS/nixpkgs/tree/master/pkgs/by-name#manual-migration-guidelines:

Manual migrations should only be lightly encouraged if the relevant code is being worked on anyways. For example with a package update or refactoring.


Text is overlapping with the Debugging the Data Plane box from  771px to 856px on page: /catalog

Description

Text is overlapping with the (Debugging the Data Plane) box from  771px to 856px on page: /catalog

Expected Behavior

Screenshots

Enviroment:

OS: Windows
Browser: Chrome
Version:
Device: Desktop

Contributor Guides and Handbook
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Thanks @UtkarshMishra12 , will you like to work on this?

@Harshit-Dandriyal Yes please assign it to me.


Browser back button doesn't work in coverage report

Browser back button doesn't work in the coverage report, and the icon you have to click on is too small.

As this is a single-page application, only the components within the page changes and browser history doesn't change.
The component changing happens according to state changes and these state changes could not be added to browser history.
Best approach to fix the issue will be to use routes instead of states for changing components.
It is also recommended to upgrade the entire code to newer versions of React before the fix.

Since the change will significantly change the current template, we do not have to prioritize this. Let's increase the size of the button for now.


Add osi support for stdout and stderr

When writing a utility in Swish, sometimes it's useful to be able to write to the standard output port and standard error port using asynchronous, binary I/O.
We have osi_get_stdin but not osi_get_stdout and osi_get_stderr. Consider passing a file descriptor to make it more general.

See pull request https://github.com/becls/swish/pull/25.


Taxonomy management: Edit page

wip - persist/execute
#3562

This pull request introduces 1 alert when merging 34543f7a038b57bb1e0b6f02713812e21e7faad2 into 69ff7375c6d86562d3e0dcc7097257ca60676a01 - view on LGTM.com
new alerts:

1 for Unused variable, import, function or class

Comment posted by LGTM.com


rsyslog: fix dependencies

libmongo-client is not available any longer. Having link on it in rsyslog causes build with --check options failure. Also, libmongo-client has been removed from master branch.
Description of changes
Link for libmongo-client dependency removed for rsyslog package.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Why the huge diff?


cursor pointer not available

can not set cursor: pointer; to file-input
<file-input>
  <paper-button><paper-button>
  <core-icon></core-icon>
</file-input>

and css
file-input { cursor: pointer }

has no effect

you'll need to target the underlying input[type="file"] instead


WMG cell type ordering

BE API cell_types endpoint should return cell types ordered by ontology layout, per this algorithm.

Implemented Pablo's code in the notebook.


Delay distributions slides could benefit from a figure

I think it would be easier to convey the ideas presented in the delay distributions slides as a figure. There are quite a few in the wild that can be re-used here with attribution.

Examples:
https://www.reconlearn.org/slides/outbreak-statistics/outbreak-statistics#14
https://academic.oup.com/aje/article/158/11/1039/162725?login=false
https://drive.google.com/file/d/1p4wgQ5AS0S7ZTqPXO5KjDAwA7qNcmXpn/view

I agree but closing this as not a priority.


Set up backups for both the Dev and Prod databases in Firebase

Different ways to backup Firebase data
Link to see quota's for the dev database and the prod database
1. Using Firebase's PITR(Point in Time Recovery)

What's being measured:

Storage: Cloud Firestore measures the database size daily. Over the period of a month, these sample points are averaged to calculate the database storage size. This average value is multiplied by the unit price of PITR (GB-month). See storage pricing for more information.
Compute billing: Any queries that you make during the PITR window of 7 days, either through stale reads or exports, incur read operation costs based on the number of documents read.

Still a bit unsure about what this entails in terms of costs.

Costs:

Storage: Not supported by free quota

$0.18 GiB/Month

Restore: Supported by free quota? Documentation is a bit vague

Free up to 50,000 Document reads, then $0.06 per 100,000 documents

Ease of use:

Very easy, is just a feature that needs to be enabled in Firebase and it will handle the backups for us.
Can perform full or partial backups on database

Timeline:

Stores backup data for the past 7 days and updates every minute

Thoughts:

Seems simple to implement and use, but could be a little bit of overkill for what we need.
On the other hand, it seems very cost-efficient for what it provides.

2. Using Scheduled Backups

What's being measured:

The amount of storage used by each backup.

The storage size for a backup is equal to the storage size of the database when you took the backup.
Storage costs for backups are in GiB/month and calculated daily. Cloud Firestore measures the size of your database backups once a day. Over the period of a month, these sample points are averaged to calculate the backup storage size. This average value is multiplied by the unit price of backups (GiB-month).

For a restore operation, you're charged based on the size of the backup.

When you perform a restore operation, Cloud Firestore measures the size of the backup for the restore operation. The size of the backup is multiplied by the unit price of restore operations (GiB).

Cost:

Backup: Not supported by free quota

$0.03 GiB/Month

Restore Operation: Not supported by free quota

$0.4 GiB

Ease of use:

Seems relatively simple, requires using gcloud CLI to set up backup schedule.
Can only perform full database restore

Timeline:

Stores backup data at either daily or weekly intervals.
If set at daily interval, data can be stored for up to 1 week.
If set at weekly interval, data can be stored for up to 14 weeks.

Thoughts:

Similar to PITR, this option also seems simple to implement and use, and seems to fit more of what we need.
Backing up is a lot cheaper than PITR unless we need to restore the database more than every 2-3 months, which seems unlikely.

3. Exporting/Importing data

What's being measured:

Export and import operations are charged for document reads and writes at the rates listed in Cloud Firestore pricing.

Export operations incur one read operation per document exported.
Import operations incur one write operation per document imported.

Output files stored in Cloud Storage count towards your Cloud Storage data storage costs.

Cost:

Export: Supported by free quota

Free up to 50,000 Document reads, then $0.06 per 100,000 documents

Import: Supported by free quota

Free up to 20,000 Document writes, then $0.18 per 100,000 documents

Storage: Supported by free quota

Free up to 1 GiB storage, then $0.18 GiB/Month

Ease of Use:

There is an option inside Firestore to export the whole database or specific collections.
Also an option to import the whole database, but requires using gcloud CLI to import specific collections.

Timeline:

Is performed manually, so whenever someone remembers to do it.

Thoughts:

Probably the least desirable out of the options above.
In terms of cost, would probably be the most expensive because it'll eat into the free quota costs and since we already use more  than half the free quota daily, it'll go over the limit whenever we would want to run the operation.
Also after reading other users experiences with this operation, it seems that it takes quite a while for it to complete.

Final Thoughts
Overall, I believe that PITR and Scheduled Backups are definitely the main choices right now. In terms of costs, Scheduled Backups seem to be better if we don't need to restore the database frequently(longer than every 2-3 months) and I envision it averaging around 1-2 dollars. In addition, PITR seems to be a relatively new feature and there could be costs with some hidden situations, so I believe Scheduled Backups are a safe choice.

Thanks so much @kiminkim724 !  This is extremely thorough and helpful.
The costs all seem so small, I don't think that will be a factor in decision making.
PITR's ease of use is attractive. But do I understand correctly that it only supports 7 days of rollback? I think we'd prefer the ability to go back in time farther than that, in which case it seems (IIUC) that S.B. is much preferable. Is that the right analysis?
I gather our current prod database size is 0.7 GB.  At that size, we could cheaply store a daily backup stretching back multiple months (3 months of data is $2/month; 90 days0.7 GB0.03 $/GB/month). Supposing we grow that 100x, it's 70GB; we could still store 10 backups at that size at a reasonable cost (~$20/month).
So, my proposal would be to setup S.B. with daily backups expiring after 3 months. Let's also retain a single monthly backup for archival storage, if we can do that.

That is correct for PITR, it will only store up to 7 days of rollback.
I forgot to mention this in my initial analysis, but for S.B., depending on the recurrence value(which is either daily or weekly), you can retain the backups for up to 1 week for daily backups, or up to 14 weeks for weekly backups. Which means that for your proposal, I believe that the closest fit would be to do a weekly backup stretching 14 weeks, or 2 months, costing about ($0.5/month; 14 weeks * 0.7 GB * 0.03/GB/month. And with the 100x scale, we could cut back on the retention periods, but keep the weekly backup.
Then to address the last point, I believe that single monthly backup for archival would probably be done by the third method. And after a bit of more research there should be a way to schedule this as well, which would require a Cloud Scheduler job. For this part, I believe for additional jobs apart from the 3 free ones per month, it will cost $0.1 to run. Then for the storage itself, it should be considered part of the regular storage costs, which is about $0.18 GiB/month. But I wonder if these costs would add up over time as we continue to grow.
One clarification that I have is if we were only setting this up on prod, which I would assume since dev would be a lot less important?

Thanks so much, @kiminkim724 . IIUC # 2 is the easiest and fastest solution, so we may as well set that up right away with a weekly cadence. If we can get the automation working for # 3, it seems to give us more fleixbility over retention and periodicity, so may be a better fit long term.
I think we might as well retain a weekly backup of dev, too, for the rare instance that we accidentally delete stuff and want to restore it.  But I'm not too concerned about data loss there; it's not 'real' data. @sashamaryl do you agree?

Anytime! @nesanders. That is correct. Just to clarify, my final proposal is a combination of both # 2 and 3: using # 2 for our main backup solution and having # 3 just for archival purposes. So, # 2 would be a need and # 3 would be more of a want.


Error: Vectors must have the same length as the number of dimensions (undefined)

I'm trying to create embeddings for a documentation and store it in Chroma.
As soon as the first chunk of Documents is written using Chroma.fromDocuments, the next chunk (with addDocuments) throws that error:
 Error: Vectors must have the same length as the number of dimensions (undefined)
    at Chroma.addVectors (/Users/baunov/Documents/dev/langchain-ts-starter/node_modules/langchain/dist/vectorstores/chroma.js:74:19)
    at Chroma.addDocuments (/Users/baunov/Documents/dev/langchain-ts-starter/node_modules/langchain/dist/vectorstores/chroma.js:39:20)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at vectorizeDocs (/Users/baunov/Documents/dev/langchain-ts-starter/src/vectorize-docs.ts:52:13)
    at <anonymous> (/Users/baunov/Documents/dev/langchain-ts-starter/src/index.ts:23:1)

Here's the full code for this:
export const vectorizeDocs = async (dir: string, collection: string) => {
    const files: string[] = await readFilesInFolder(path.join(__dirname, '..', dir));
    const json = files.map((f) => JSON.parse(f)).filter((j) => j.content.length > 0);

    const textSplitter = new RecursiveCharacterTextSplitter({chunkSize: 1000, chunkOverlap: 0});

    const docs: Document[] = await textSplitter.createDocuments(
        json.map((j) => j.content),
        json.map((j => ({url: j.url, category: collection})))
    );

    const exists = Boolean(await chromaClient.getCollection(collection));

    const embeddings = new OpenAIEmbeddings();
    let docsChunks = splitIntoChunks(docs, 30);
    const store = exists ? await Chroma.fromExistingCollection(embeddings, {
        collectionName: collection
    }) : await Chroma.fromDocuments(docsChunks[0], embeddings, {
        collectionName: collection
    }).then((s) => {
        docsChunks = docsChunks.slice(1);
        return s;
    });
    console.log('Chunk 1 successfully written');

    for (const chunk of docsChunks) {
        try {
            await store.addDocuments(chunk);
            console.log('Added chunk');
        }
        catch (e) {
            console.log('Error adding chunk', chunk, e);
        }
    }
};

And interestingly, this doesn't happen to all docs. Some docs are vectorised without errors. But I can't tell why.
Here's the data I'm feeding into that function (basically scraped langchain docs):
langchain.zip

I have the same question

Having same issues!

Same error here.

I had this issue as well. For me it was due to passing a documents array of length === 0. So make sure that the split docs you provide to the vector store and then the retriever are of length >= 1.


Building and pushing images using container extension

Removing the manual building & pushing of container images introduced in #50 in favor of using quarkus container image extensions.

Looks good to me. I thought you needed to change the properties but you didn't which is better.

Nope can do it all from the command line

I saw it's execution failed for some reason. I'll look into why

Awesome!


provide a generic health check for generic Node.js applications

We could:

make it available through the management API
make the composer aware of these health check, so if one of those fails it start reporting failures.

@mcollina Can we close this?

Yes


feat: Upload revised proposal and revised proposal dropdown (Ver.2)

Re-upload button available to coordinator when the review status of the proposal changes to "Revise"
Dropdown button available when the proposal has revised version/original version
Create badges to highlight original proposal

my general feedback on this pr:
Please avoid unnecessary complication and redundancy in your code though it's great to able to write general purpose functions(code) that takes care of multiple cases.
Also revisedProposals dropdown on submissions list page should be available to coordinators, reviewers and chair. Right now it's only available to chair.