Saturday, August 12, 2023

Show HN: Weaviate – Multi Tenancy Notebook https://ift.tt/gzQPjEs

Show HN: Weaviate – Multi Tenancy Notebook https://ift.tt/0nsAptH August 12, 2023 at 04:20AM

Track Replacement on the L Taraval Line

Track Replacement on the L Taraval Line
By Sevilla Mann

If you’ve traveled through the Sunset or Parkside neighborhoods recently, you may have seen a lot of construction activity on Taraval Street. Major construction projects are an inconvenience, and the impacts seem to be never ending. You may wonder, why does it take so long

We would like to thank everyone for your ongoing patience and understanding as the L Taraval Improvement Project to replace aging infrastructure continues. Since we announced the beginning of the second segment of improvements on Taraval Street in January 2022, we’ve been busy wrapping up upgrades to the sewer and water lines, underground conduits and new pole foundations for the Overhead Contact System (OCS) that powers our Muni trains. We have also installed the necessary infrastructure to upgrade existing electrical for the trains, current and future streetlights and light poles.

We’ve now begun work on some of the above-ground improvements that you’ll be soon able to experience for yourself when the project is completed next year. To improve safety and accessibility, we’re upgrading existing boarding islands and adding additional islands that are ADA compliant. We are also making curb ramp upgrades, adding pedestrian bulbs and paving streets. To beautify the street, new trees and landscaping will be planted. We’re completely replacing the worn tracks that were initially installed in 1975. This will make your ride smoother and more reliable. You can learn more about 100 years of rail on Taraval.  

A rail track under construction with orange bollards on each side. 

Track installation between 28th and 31st avenues in 2023.

Track Replacement Work

This is a once in a lifetime opportunity to see the tracks replaced in the City’s 150 rail infrastructure. San Francisco’s unique rail system dates back 150 years and ties together our cable cars, historic electric street cars and today’s modern Muni light rail service. Over the years, our rail maintenance team has been vigilant in keeping the rails in good working condition for as long as possible. Now the tracks are at the end of their useful life, and we are replacing the rails and upgrading our rail system to keep our trains operating smoothly well into the 21st century. 

Track work between 16th and 19th avenues has begun, and the middle of Taraval Street will be closed to traffic traveling north- and southbound on 17th and 18th Avenues across Taraval Street for excavation work. East- and westbound lanes will remain open and traffic approaching Taraval Street will be allowed right turns only. 

Note: that some L Taraval Bus stops may be temporarily relocated in active construction areas; please look for signs posted at bus stops.  

A rail track is under construction with orange bollards on each side.

Track excavation between 28th and 31st avenues in 2023.

On Monday, August 14, we will do a “rail pull” -- literally pulling the rails from the current staging location on Wawona Street and 20th Avenue for installation on Taraval Street between 16th and 19th avenues. The rails have been assembled from 100-yard rods into 400-yard “strings” ready for installation. We will use two loaders to push and pull the rails from storage, guide the strings down 21st Avenue and turn onto Taraval Street. Each rail segment is over a block long, so moving them to their new home will be quite a feat.  

A map of where the rail pull and installation will occur.

There will be intermittent temporary traffic delays along the pull route and at the intersection of 19th and Taraval Street. So, if you’re in the neighborhood on Monday, August 14, please try to avoid driving along the rail pull route. Or better yet, grab a bite to eat from one of Taraval’s excellent restaurants and watch history being made from the sidelines! If you miss this rail pull, stay tuned for the next one by signing up for project updates.  



Published August 12, 2023 at 03:04AM
https://ift.tt/k4IUJvB

Show HN: Clop – optimise screenshots and recordings automatically https://ift.tt/mHCideD

Show HN: Clop – optimise screenshots and recordings automatically https://ift.tt/dsotblv August 12, 2023 at 01:41AM

Friday, August 11, 2023

Show HN: Openform – use Google Forms and Google Sheets as a simple database https://ift.tt/6AUqMVh

Show HN: Openform – use Google Forms and Google Sheets as a simple database https://ift.tt/SmsVA58 August 11, 2023 at 07:10AM

Show HN: Chatmate.dev: Create chatbots from multiple chat and document component https://ift.tt/km6fGHq

Show HN: Chatmate.dev: Create chatbots from multiple chat and document component Chatmate allows you to customize and combine multiple chat chains (gpt4 chat completions) and document retrievals. Chat components can be customized by all the regular openai api parameters and allow you to refer to other chat components in the system prompt and user message. For example, you could have a chat component that generates a list of actions that should be taken to solve a users query, then refer to this component in another chat component that uses the actions list in it's system prompt. You can refer to other by components by typing "@" in the rich text editors. Any available components (components that you can refer to without creating a circular dependency) will show up. Document components allow you to embed any number of documents (pdf, txt, json, md, mdx, html) and query them by cosine similarity for a given search query. The search query can also depend on chat components (i.e. You can make a "Standalone question" component which turns the user query into a standalone question (question + chat context) and then use this as your search query to retrieve more relevant documents). I would like to implement conditional components and code components next. Conditional components will use gpt4 function calls to select a component to run, and code componts will run code in a sandbox (with network support). I'm also working on exposing the chatbots as an api and a multitenat domain (i.e. {projectname}.chatmate.dev) so that chatbots can be used in your own projects or shared. Let me know what you think. Any feedback is appreciated! https://ift.tt/2gzFSAM August 11, 2023 at 03:29AM

Show HN: VectorFlow – Open-Source Vector Embedding Pipeline https://ift.tt/YZGBvjE

Show HN: VectorFlow – Open-Source Vector Embedding Pipeline Hey HN We've just released the initial version of our open-source vector embedding pipeline. It's designed to embed large volumes of data. While embedding a few documents for Q&A is straightforward, consistently ingesting gigabytes of unstructured data is a whole different ballgame. By using our API, you can embed raw data and store vectors in your vector database, sidestepping the complexities of cloud infrastructure. Now, in true YC spirit, we're launching before everything is polished. Our Github repo ( https://ift.tt/v9PhisU ) is a work in progress, and we're eager to get it in front of the community early on. Check out our Github repo and let us know what you think. Your feedback, suggestions, and critiques will be highly appreciated as we continue to refine and develop. https://ift.tt/v9PhisU August 10, 2023 at 11:05PM

Show HN: Q&A with AI Trained on Bankruptcy Law https://ift.tt/EqIVeah

Show HN: Q&A with AI Trained on Bankruptcy Law I crawled a #$%^ ton of bankruptcy case law and pointed a LLM at it to answer bankruptcy legal questions. I just tried it on the Supreme Court's request today in its order stopping the Purdue Pharma settlement[1], and it gives a decent answer. > The parties are directed to brief and argue the > following question: Whether the Bankruptcy Code authorizes a > court to approve, as part of a plan of reorganization under > Chapter 11 of the Bankruptcy Code, a release that extinguishes > claims held by nondebtors against nondebtor third parties, > without the claimants’ consent. ChatLaw's answer: The Bankruptcy Code does not explicitly authorize a court to approve, as part of a plan of reorganization under Chapter 11, a release that extinguishes claims held by non-debtors against non-debtor third parties, without the claimants’ consent. However, courts have interpreted certain provisions of the Bankruptcy Code to permit such non-consensual third-party releases under certain circumstances. The relevant provisions of the Bankruptcy Code include Section 105(a), which empowers the court to issue any order, process, or judgment that is necessary or appropriate to carry out the provisions of this title, and Section 1123(b)(6), which allows a plan to include any other appropriate provision not inconsistent with the applicable provisions of this title. In the case of In re: Mallinckrodt PLC, (District of Delaware, 02/08/2022), the court noted that while Section 524(e) of the Bankruptcy Code should be read to preclude non-debtor releases, releases are not the equivalent of a discharge. The court also noted that the Third Circuit has recognized that bankruptcy courts do have statutory and constitutional authority to approve a plan of reorganization that contains non-consensual third-party releases, albeit, only in extraordinary cases. In the case of In Re: 18-13374-mew Aegean Marine Petroleum Network Inc. (Southern District ofNew York, 2019-04-08), the court noted that some Circuit Courts of Appeal have held that bankruptcy courts lack the power to grant nonconsensual third-party releases of the kind that the Debtors seek here. However, other Courts of Appeal, including the Second Circuit Court of Appeals, have held that bankruptcy courts have the power to impose involuntary releases, but that such involuntary releases should be imposed only in rare cases. In the case of 22-110 In re: Purdue Pharma L.P. (Second Circuit Court of Appeals, 5/30/2023), the court concluded that two sections of the Bankruptcy Code, 11 U.S.C. 105(a), 1123(b)(6), jointly provide the statutory basis for the bankruptcy courts authority to approve a plan that includes nonconsensual releases of third-party claims against non-debtors. The court further held that the bankruptcy courts inclusion of the releases is equitable and appropriate under the specific factual circumstances of this case. In the same case, in a concurring opinion, Judge Richard C. Wesley agreed that a bankruptcy court has the authority to approve a Chapter 11 reorganization plan that includes nonconsensual nondebtor releases, based on the court's precedent in In re Drexel Burnham Lambert Grp., Inc., 960 F.2d 285, 293 (2d Cir. 1992). However, he expressed concerns about the lack of explicit statutory basis for such releases in the Bankruptcy Code. In conclusion, while the Bankruptcy Code does not explicitly authorize non-consensual third-party releases, courts have interpreted certain provisions of the Code to permit such releases under certain circumstances. The permissibility of such releases often depends on the specific facts and circumstances of the case, and courts have cautioned that such releases should be approved only in rare cases. [1] https://ift.tt/JcfeVmB... https://www.chatlaw.us August 11, 2023 at 05:28AM

Show HN: Do You Know RGB? https://ift.tt/t8kUpbO

Show HN: Do You Know RGB? https://ift.tt/OWhvmMT June 24, 2025 at 01:49PM