Where should I set the table_info parameter?

Hello.  In Prompts.py around line 294, there is a variable called table_info, for designating which tables the agent should search.  It is not obvious in your code where this variable should be set.

This is a variable that is dynamically populated by the langchain's sql agent. Refer to the langchain repo so you can understand how the agent works:
https://github.com/langchain-ai/langchain/blob/master/libs/langchain/langchain/agents/agent_toolkits/sql/toolkit.py
https://github.com/langchain-ai/langchain/blob/master/libs/langchain/langchain/tools/sql_database/tool.py


fix: nested sidenav items, more selective hiding

Fix #80
Test URLs:

Before: https://main--prisma-cloud-docs-website--hlxsites.hlx.page/prisma/prisma-cloud/en/compute/public-sector/release-findings/release-findings
After: https://issue-90--prisma-cloud-docs-website--hlxsites.hlx.page/prisma/prisma-cloud/en/compute/public-sector/release-findings/release-findings

@maxakuru Looks good, just a couple of comments. I put my comments in the issue here:
https://github.com/hlxsites/prisma-cloud-docs-website/issues/90#issuecomment-1603691979


Two features to Reporting area

We (Brightfox, gobrightfox.com) are an educational tutoring center where the tutors write summary notes about what happened, mostly for parents to read. We want these notes to be high quality, so we implemented Sapling and require the instructors to clear all underlined portions by Sapling (Accept or Ignore) before submitting.
We don't want this to be a burden on them which makes their job much worse. We would like to keep adding more dictionary words to improve the usefulness.

In my opinion "Accept to Ignore ratio" is the signal of success. We want as many accepts as possible with very few ignores. It would be nice to add this chart, which seems like it should be easy. This is the main metric I will be monitoring.

It would be nice to see the list of actual ignores so we can add words to the Dictionary. For example, if there is a technical word in Math like "L'hospital's Rule" that the instructors keep having to click Ignore over and over again, I should be able to see that, and add it to the Dictionary.

The list of ignored words would be something like:
l'hospital's rule (5) where 5 is the total count of times it's been ignored
sqrt3 (4)
microplasmal (3)
biopsy (3)

Hi @alexmccauley, we'll get back to you later this week with updates on both requests!

hi @alexmccauley , we've shipped an update to our website - you should now see an Accepts/Ignores graph as well.

Hi @alexmccauley, you can find ignores from multiple teammates (within the last 30 days) at the bottom of the team dictionary panel as suggested candidates to add to a team dictionary. We filter out common words and edits that get a noisy accept/reject ratio.


Support shelf 0.6.0

+1

+1

Can you please send over a pull request? Thanks!
cc @kevmoo

@sethladd There was a breaking change in shelf with the last update and I have no idea what needs to be considered. I'm still not very familiar with shelf. I looked into it but gave up. Not at least because debugging async code still doesn't work reliable for me (breakpoints are ignored, bug is reported).

Thanks for giving it a shot.

Starting on this now...

Apologies I realised I had actually fixed and ported this a while back but as I did it as part of a bunch of other shelf related work that I haven't completed yet, I hadn't got around the the PR
https://github.com/dart-lang/shelf_appengine/pull/8 in case it is not too late

I'm going to land some simple tests first, then I'll land your changes.
Thanks!

Fixed with cec0e5a2dc02a933625f463875a94cd99033d3e1


dispatch_release is not needed in iOS 6 with ARC

hi,
thanks for wonderful work.
when set Deployment Target about 6.0. Error occur
cause dispatch_release is not needed in iOS 6 with ARC

Thanks, you can add framework  instead source code to your project, to fix building error.
I will fix this issue later.


NoMethodError: undefined method `to_i' - Devise Model

https://github.com/michaeldv/awesome_print/issues/165
Throwing this error in rails c when I try to look up a devise model. Is there a way around this?
User.all # works as intended
User.last # NoMethodError: undefined method `to_i'

basically awesome print cannot handle inet fields.... hi moe!

@asharma-ror as @miamiruby this was a bug on the awesome_print, this was fixed on the 1.6.0 if you guys got any issue please post here https://github.com/michaeldv/awesome_print/issues/165


Create edit/commit/push functionality for git

In thinking about https://github.com/atomist-skills/keep-a-changelog-skill/issues/67 , I wonder if it might be helpful to offer a function that applies a change, commits it, and pushes it. The "change" would likely be in the form of a function argument to run. The pseudo code representation would be:

Execute change function
Commit change
Push change
If push fails, git reset --hard origin/BRANCH GOTO 1

I like that idea.
If I understand it, I think I implemented something similar or at least the start of this: See https://github.com/atomist-skills/skill/blob/main/lib/github/pull_request.ts#L48

@ddgenome, do you want to take this?

Yes to everything.
The persistChanges function seems like a great start and the place to add in this idea of "retry".
I'll get started on implementing it.
Thanks for the pointers.


Memory leak warning at compile time

It would be nice to get errors for a malloc() whose return value is never free()d. However, I don't want:

automagic freeing of memory (Rust, C++)
something that is correct in every corner case imaginable and hence annoying to use (Rust).

Jou should still feel like C. It would just emit warnings for some common memory management mistakes.
For example, consider:
def foo():
    for i = 0; i < 10; i++:
        f = fopen(...)
        ...do stuff...
    fclose(f)

The decision tree for this function is basically:
                                ,--------- ... ---------.
                                V                       |
,-------.     .-------.     .--------. yes     ,----------------.
| start | --> | i = 0 | --> | i < 10 | ------> | f = fopen(...) |
`-------'     `-------'     `--------'         `----------------'
                                |no   ,-----------.      ,-----.
                                `---> | fclose(f) | ---> | end |
                                      `-----------'      `-----'

If the compiler knows that fopen(...) returns something that needs cleanup, and fclose(f) does cleanup to f, it could deduce that f may already contain something worth cleaning up when we get to f = fopen(...). It could then generate a warning that looks something like this:
compiler warning for file "foo.py", line 3: old value of variable 'f' should be cleaned up to avoid memory leaks

IMO we shouldn't distinguish various different kinds of things to be cleaned up. It is rare to accidentally use free() on a pointer that came from fopen(). It is much more common to forget the cleanup entirely or do it twice.

Once again, I don't want to add more magic to Jou. I want it to be a simple language that doesn't hide things from you. IMO such language shouldn't magically clean up your garbage.

And if the compiler is mistaken in some cases, there should be a way to notify it :).

Undefined variables are a bit similar. There are currently two warnings:

the value of 'foo' is undefined (compiler is sure that your code is wrong)
the value of 'foo' may be undefined (compiler thinks your code might be wrong, but is not sure)

If you get a "may be undefined" warning, you should probably rewrite that part of your code anyway, because it's confusing.
For memory leaks, I only want one warning. Something like:

old value of variable 'foo' needs cleanup to avoid a memory leak (compiler is sure that your code is wrong)

A "may need cleanup" warning in Jou would either spam you with lots of false positive warnings, or it would be so complicated that it's basically impossible to implement.


SNOW-1320449: Support subtracting two timestamps.

Fixes SNOW-1320449

Please rebase and then I'll take a pass thanks!


RestartDriver() API + Common code for PerfromTask

Added RestartDriver() API to volume driver.
Factored out common code for trigger-based perform task action in
a separate package.

PX-Backup Jenkins job which is consuming changes from this PR:
https://jenkins.portworx.co/job/tp-backup-vinayak/18/console
Test Suite Name: BackupCreateRestore

Jenkins tp-dev-test job: https://jenkins.portworx.co/job/Torpedo/job/tp-dev-test/443/console


Replace Tails by turboprop

Some forks report issue related to tails as discussed here: https://elixirforum.com/t/turboprop-toolkit-to-create-accessible-component-libraries/64228
I decided to borrow Merge module from Turboprop and copied to SaladUI code base. Sadly because Turboprop is now discontinued.
I've tested on all existing components, and so far so good.
Summary by Sourcery
Replace 'tails' with 'turboprop' for merging Tailwind CSS classes, update related configurations, and refactor tests to improve maintainability.
Enhancements:

Refactor tests to use a more modular approach for asserting HTML class presence, improving readability and maintainability.

Documentation:

Update documentation to replace references to 'tails' with 'turboprop' and adjust installation instructions accordingly.

Tests:

Remove tests related to 'tails' configuration and update tests to reflect the new 'turboprop' integration.

Chores:

Remove 'tails' dependency and related configuration from the project.

thanks @bmalum I'll update document


Fragment child order with false/null child

Running the example and pressing "Run" outputs "B C A" but should be "A B C". That is corrected however when a re-render happens (the second button).
This is fixed by either making Preview not return false or null or by replacing Fragment with e.g. div.
I have a feeling this is related to https://github.com/developit/preact/pull/1440
The devtools always show the correct order.
https://codesandbox.io/s/m498m04nly
import {h, render, Component, Fragment} from 'preact';

const Preview = () => null; // or false

class App extends Component {
  constructor(props) {
    super(props);

    this.state = {
      output: null,
      value: null
    };
  }

  run() {
    this.setState({
      output: ['A', 'B', 'C']
    });
  }

  render() {
    return (

        <button onClick={() => this.run()}>Run</button>
        <button onClick={() => this.setState({value: {}})}>Re-render</button>
        {this.state.output && (
          <Fragment>
            {this.state.output.map(v => (

                {v}

            ))}
            <Preview output={this.state.output} />
          </Fragment>
        )}

    );
  }
}

render(<App />, document.getElementById('root'));

Using Preact 10.0.0-beta.0

@mischnic Thank you so much for the detailed bug report. I was quickly able to reproduce it and create a proper fix. You rock :+1: :100:


Could not import faiss-node (NextJS) when loading from python

Hi, I know this is a duplicate of:
https://github.com/langchain-ai/langchainjs/issues/2107
However, in that issue it says that this has been resolved. While I'm on the latest release:
0.1.2
Which should have the fix for this available here:
https://github.com/langchain-ai/langchainjs/pull/2178
My issue is the following:
https://github.com/langchain-ai/langchainjs/issues/2107#issuecomment-1891106038
For reference, I'll post it below:
Hi there,
I'm getting the same type of error message in my console when I try to:
const vectorstore = await FaissStore.loadFromPython("./knowledge", new OpenAIEmbeddings({
            modelName: "text-embedding-ada-002"
}));

knowledge is a folder in the root folder that includes 2 files:
index.pkl
index.faiss

I am using the following to see whether my API route in nextjs can reach the files:
const knowledge = path.resolve('./knowledge');
const filenames = fs.readdirSync(knowledge);
console.log(filenames);

this logs the actual filenames, so I know they're there...
I'm getting the following error message in my console:
 Error: Could not import faiss-node. Please install faiss-node as a dependency with, e.g. `npm install -S faiss-node`.

Error: Cannot read properties of undefined (reading 'indexOf')
    at FaissStore.importFaiss (webpack-internal:///(rsc)/./node_modules/@langchain/community/dist/vectorstores/faiss.js:363:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async readIndex (webpack-internal:///(rsc)/./node_modules/@langchain/community/dist/vectorstores/faiss.js:292:37)
    at async Promise.all (index 1)
    at async FaissStore.loadFromPython (webpack-internal:///(rsc)/./node_modules/@langchain/community/dist/vectorstores/faiss.js:295:32)
    at async POST (webpack-internal:///(rsc)/./app/api/chat/route.ts:56:29)
    at async D:\Development\Persoonlijk\gpt-creator\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:6:63251

I'm running this on windows with npm run dev
I've already tried installing the package, but I have no clue why my nextjs isn't importing the files...
My node version is 20.10.0
Is there anything I can do to get this issue sorted?
It says read properties of undefined (reading 'indexOf')
This to me indicates it can not read the ./knowledge folder with files for some reason. But I haven't been able to figure out why yet. I could be totally wrong here though.

I'll test this on a ubuntu server soon, I'll also test it on mac os if need be...
I'll give updated info tomorrow.

The loadFromPython method does indeed have issues. I saved index using the latest version of the Python package and encountered an error when trying to load it with the following code.
langchain                  0.1.0
langchain-community        0.0.12
langchain-core             0.1.10

from langchain_community.embeddings import FakeEmbeddings

from langchain.text_splitter import CharacterTextSplitter
from langchain_community.vectorstores import FAISS
from langchain_community.document_loaders import TextLoader

loader = TextLoader("state_of_the_union.txt")
documents = loader.load()
text_splitter = CharacterTextSplitter(chunk_size=1000, chunk_overlap=0)
docs = text_splitter.split_documents(documents)

embeddings = FakeEmbeddings(size=4)

db = FAISS.from_documents(docs, embeddings)

query = "What did the president say about Ketanji Brown Jackson"
docs = db.similarity_search(query)

db.save_local("faiss_index")

This is because the namespace of InMemoryDocstore was changed on the Python side. Consequently, the newly saved .pkl file cannot be imported. I will fix this next.

@Simbaclaws  However, I did not encounter the same error as you did. Please try the example code below without loadFromPython. This way, I can confirm whether it is an issue with importing the package or with loadFromPython.
async function run() {
    const vectorStore = await FaissStore.fromTexts(
        ["Hello world", "Bye bye", "hello nice world"],
        [{ id: 2 }, { id: 1 }, { id: 3 }],
        new FakeEmbeddings()
      );

      const resultOne = await vectorStore.similaritySearch("hello world", 1);
      console.log(resultOne);
}

@ewfian
Where do I import FakeEmbeddings from?
The suggested packages by my IDE seem to all fail:
Module not found: Package path ./dist/utils/testing is not exported from package /home/simbaclaws/Projects/Personal/my-gpt/node_modules/@langchain/community (see exports field in<EMAIL_ADDRESS>
Module not found: Package path ./dist/embeddings/fake is not exported from package /home/simbaclaws/Projects/Personal/my-gpt/node_modules/langchain (see exports field in /home/simbaclaws/Projects/Personal/my-gpt/node_modules/langchain/package.json

@ewfian
Where do I import FakeEmbeddings from?
The suggested packages by my IDE seem to all fail:
Module not found: Package path ./dist/utils/testing is not exported from package /home/simbaclaws/Projects/Personal/my-gpt/node_modules/@langchain/community (see exports field in<EMAIL_ADDRESS>
Module not found: Package path ./dist/embeddings/fake is not exported from package /home/simbaclaws/Projects/Personal/my-gpt/node_modules/langchain (see exports field in /home/simbaclaws/Projects/Personal/my-gpt/node_modules/langchain/package.json

"langchain/embeddings/fake"

@Simbaclaws I just created a Next.js project and reproduced your issue using the App Router pattern. From the error, I noticed that faiss-node is being bundled by webpack, which is incorrect since faiss-node is a native module.

https://js.langchain.com/docs/integrations/vectorstores/faiss
I found a configuration in the documentation that exempts faiss-node from bundling.
https://nextjs.org/docs/app/api-reference/next-config-js/serverComponentsExternalPackages
After adding this config for faiss-node, it should work correctly. Please give it a try.

That works!! Thank you so much!
You are my hero :100:

When I put loadFromPython back in it says:
TypeError: NameRegistry is not a constructor
at readStore (webpack-internal:///(rsc)/./node_modules/.pnpm/@langchain+community@0.0.17_faiss-node@0.5.1/node_modules/@langchain/community/dist/vectorstores/faiss.js:280:30)
at async Promise.all (index 0)
at async FaissStore.loadFromPython (webpack-internal:///(rsc)/./node_modules/.pnpm/@langchain+community@0.0.17_faiss-node@0.5.1/node_modules/@langchain/community/dist/vectorstores/faiss.js:295:32)
at async POST (webpack-internal:///(rsc)/./app/api/chat/route.ts:86:29)
at async /home/simbaclaws/Projects/Personal/vero-gpt/node_modules/.pnpm/next@14.0.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:63251
perhaps I'm still doing something wrong?

@Simbaclaws  It seems that pickleparser has not been imported correctly. To read a .pkl file saved in Python, the pickleparser is needed. Please try a few basic cases with pickleparser to see if it works.
import { NameRegistry } from 'pickleparser'
console.log(NameRegistry.getFullyQualifiedName("testmodule", "testname"))  // testmodule.testname
const registry = new NameRegistry();
registry.register("testmodule", "testname", () => 123)
const func = registry.resolve("testmodule", "testname") as any
console.log(func()) // 123

I'm sorry I'm quite new to all of faiss, langchain, and openai.
In the case of loading a folder with a pkl file, what exactly would I have to do with the NameRegistry? It confuses me a little.
In python it looks like I can just say:
VectorStore = FAISS.load_local('knowledge', OpenAIEmbeddings(model='text-embedding-ada-002', openai_api_key=OPENAI_API_KEY))

And it would work in importing the knowledge folder with the pkl. I don't have to do anything with any sort of NameRegistry in python.
I assumed this worked the same way in javascript.
What exactly is this NameRegistry and how do I use it in a similar fashion according to my example:
const vectorstore = await FaissStore.loadFromPython("./knowledge", new OpenAIEmbeddings({
            modelName: "text-embedding-ada-002"
}))

I'll use your example code to test whether it'll work, but I'm just a bit confused what the extra steps would be to read from a knowledge folder that is local.

@Simbaclaws Python will export two files: index.pkl and index.faiss. index.faiss contains internal data for faiss and can be directly read by faiss-node. On the other hand, index.pkl is used to record mapping relationships and metadata. The structure of this file is in Python's pickle format, which is a binary file and JavaScript cannot directly read this file, so we need to use pickleparser to read it.
When pickleparser reads a .pkl file, it needs to handle the mapping relationships between Python identifiers such as modules and class names, and the data structures in JavaScript. These mappings are managed through NameRegistry.
const registry = new NameRegistry()
  .register("langchain.docstore.in_memory", "InMemoryDocstore", PyInMemoryDocstore)
  .register("langchain_community.docstore.in_memory", "InMemoryDocstore", PyInMemoryDocstore)
  .register("langchain.schema", "Document", PyDocument)
  .register("langchain.docstore.document", "Document", PyDocument)
  .register("langchain.schema.document", "Document", PyDocument)
  .register("langchain_core.documents.base", "Document", PyDocument)
  .register("pathlib", "WindowsPath", (...args) => args.join("\\"))
  .register("pathlib", "PosixPath", (...args) => args.join("/"));

For example, .register("langchain.docstore.in_memory", "InMemoryDocstore", PyInMemoryDocstore);
In Python, the class name is InMemoryDocstore, located in langchain.docstore.in_memory, while in JavaScript, it is PyInMemoryDocstore.
The error you are currently encountering is a bug.
TypeError: rawStore.toInMemoryDocstore is not a function

Please refer to the comments above; I will file a pull request to fix this later. In the meantime, you can make a simple edit in<EMAIL_ADDRESS>Add the following two lines of code to make it work.

EDIT 2: I think I understand now that I just needed the pickleparser package to get further I guess... Wouldn't it be wise by the maintainers of faiss-node to make the pickleparser a dependency of the faiss-node package? Or is this something that should be excluded by default? If you have code in your package that makes use of another package, it would be useful to include that package in the dependencies IMO...

In fact, there is no relationship between the faiss-node and pickleparser. they are simply used together in loadFromPython of langchian. This is explicitly mentioned in the Langchain documentation as well: https://js.langchain.com/docs/integrations/vectorstores/faiss

Oh wow, I must've overlooked that.
Thank you so much for everything, I'm currently checking whether the solution works.
I'll report back!

@Simbaclaws  Please try deleting the .next directory to invalidate the build cache.

I'm sorry if I'm being a nuisance...
Currently I'm using the following code:
const vectorstore = await FaissStore.loadFromPython("./knowledge", new OpenAIEmbeddings({
            modelName: "text-embedding-ada-002"
        }))

        const vectorStoreRetriever = vectorstore.asRetriever();
        // Create a system & human prompt for the chat model
        const SYSTEM_TEMPLATE = `
        This is some prompt I'm giving to my gpt
        ==========
        {question}
        ==========

       Answer:
       Source:;

        const templateMessages = [
            SystemMessagePromptTemplate.fromTemplate(SYSTEM_TEMPLATE),
            HumanMessagePromptTemplate.fromTemplate("{question}"),
        ];
        const docs = await vectorstore.similaritySearch(messages.content, 1);
        const prompt = ChatPromptTemplate.fromMessages(templateMessages);

        const chain = RunnableSequence.from([
            {
                // Extract the "question" field from the input object and pass it to the retriever as a string
                sourceDocuments: RunnableSequence.from([
                    (input) => input.question,
                    vectorStoreRetriever,
                ]),
                question: (input) => input.question,
            },
            {
                // Pass the source documents through unchanged so that we can return them directly in the final result
                sourceDocuments: (previousStepResult) => previousStepResult.sourceDocuments,
                question: (previousStepResult) => previousStepResult.question,
                context: (previousStepResult) =>
                    formatDocumentsAsString(previousStepResult.sourceDocuments),
            },
            {
                result: prompt.pipe(model).pipe(new StringOutputParser()),
                sourceDocuments: (previousStepResult) => previousStepResult.sourceDocuments,
            },
        ]);

        const response = await chain.invoke({
            question: messages.content,
            input_documents: docs
        })

        console.log(response)
        return new NextResponse(response.result, {status: 200})

It's now responding with:
 TypeError: Cannot read properties of undefined (reading 'replace')
    at OpenAIEmbeddings.embedQuery (webpack-internal:///(rsc)/./node_modules/.pnpm/@langchain+openai@0.0.11/node_modules/@langchain/openai/dist/embeddings.js:183:46)
    at FaissStore.similaritySearch (webpack-internal:///(rsc)/./node_modules/.pnpm/@langchain+core@0.1.13/node_modules/@langchain/core/dist/vectorstores.js:117:90)
    at POST (webpack-internal:///(rsc)/./app/api/chat/route.ts:112:40)
    at async /home/simbaclaws/Projects/Personal/vero-gpt/node_modules/.pnpm/next@14.0.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:6:63251

Am I using the similaritysearch wrong?

@Simbaclaws  It seems that loadFromPython has now passed. Based on the error "OpenAIEmbeddings.embedQuery," after a quick review of the code, I suspect that the replace below may be causing a Null Reference Exception (NRE).

Please confirm the content of messages.content.
const docs = await vectorstore.similaritySearch(messages.content, 1);

Awesome! I was indeed messing up the messages content.
It's working as intended...
I have a last question that I want to ask:
In python there is a function called:
load_qa_with_sources_chain

This is a function that loads a question and answer, and returns the answer + a source to the url it got the information from. I think the url is provided in the documents...
I'm trying to accomplish the same thing by doing this part:
const chain = RunnableSequence.from([
            {
                // Extract the "question" field from the input object and pass it to the retriever as a string
                sourceDocuments: RunnableSequence.from([
                    (input) => input.question,
                    vectorStoreRetriever,
                ]),
                question: (input) => input.question,
            },
            {
                // Pass the source documents through unchanged so that we can return them directly in the final result
                sourceDocuments: (previousStepResult) => previousStepResult.sourceDocuments,
                question: (previousStepResult) => previousStepResult.question,
                context: (previousStepResult) =>
                    formatDocumentsAsString(previousStepResult.sourceDocuments),
            },
            {
                result: prompt.pipe(model).pipe(new StringOutputParser()),
                sourceDocuments: (previousStepResult) => previousStepResult.sourceDocuments,
            },
        ]);

But instead of returning just the source url in the answer, it is giving me all of the documents it has searched and not give me back a url to where it got the answer from...
Do you perhaps know of a way to put the url from the source documents into the response?

Awesome! I was indeed messing up the messages content.
It's working as intended...
I have a last question that I want to ask:
In python there is a function called:
load_qa_with_sources_chain()

This is a function that loads a question and answer, and returns the answer + a source to the url it got the information from. I think the url is provided in the documents...
I'm trying to accomplish the same thing by doing this part:
const chain = RunnableSequence.from([
            {
                // Extract the "question" field from the input object and pass it to the retriever as a string
                sourceDocuments: RunnableSequence.from([
                    (input) => input.question,
                    vectorStoreRetriever,
                ]),
                question: (input) => input.question,
            },
            {
                // Pass the source documents through unchanged so that we can return them directly in the final result
                sourceDocuments: (previousStepResult) => previousStepResult.sourceDocuments,
                question: (previousStepResult) => previousStepResult.question,
                context: (previousStepResult) =>
                    formatDocumentsAsString(previousStepResult.sourceDocuments),
            },
            {
                result: prompt.pipe(model).pipe(new StringOutputParser()),
                sourceDocuments: (previousStepResult) => previousStepResult.sourceDocuments,
            },
        ]);

But instead of returning just the source url in the answer, it is giving me all of the documents it has searched and not give me back a url to where it got the answer from...
Do you perhaps know of a way to put the url from the source documents into the response?
It also seems that my input documents aren't working... For some reason it's not using the data I provided, just the last document is being used..

Sorry, I'm not familiar with this question. perhaps you can ask @jacoblee93 for help or create a new discussions.

Awesome! I was indeed messing up the messages content.
It's working as intended...
I have a last question that I want to ask:
In python there is a function called:
load_qa_with_sources_chain()

This is a function that loads a question and answer, and returns the answer + a source to the url it got the information from. I think the url is provided in the documents...
I'm trying to accomplish the same thing by doing this part:
const chain = RunnableSequence.from([
            {
                // Extract the "question" field from the input object and pass it to the retriever as a string
                sourceDocuments: RunnableSequence.from([
                    (input) => input.question,
                    vectorStoreRetriever,
                ]),
                question: (input) => input.question,
            },
            {
                // Pass the source documents through unchanged so that we can return them directly in the final result
                sourceDocuments: (previousStepResult) => previousStepResult.sourceDocuments,
                question: (previousStepResult) => previousStepResult.question,
                context: (previousStepResult) =>
                    formatDocumentsAsString(previousStepResult.sourceDocuments),
            },
            {
                result: prompt.pipe(model).pipe(new StringOutputParser()),
                sourceDocuments: (previousStepResult) => previousStepResult.sourceDocuments,
            },
        ]);

But instead of returning just the source url in the answer, it is giving me all of the documents it has searched and not give me back a url to where it got the answer from...
Do you perhaps know of a way to put the url from the source documents into the response?
It also seems that my input documents aren't working... For some reason it's not using the data I provided, just the last document is being used..

Sorry, I'm not familiar with this question. perhaps you can ask @jacoblee93 for help or create a new discussions.

I'll do that, thank you for everything so far! I'm really happy with the progress that was made.

When your PR has been merged (for the actual fix), I'll close this github issue as solved.

I've figured out the source code for getting my load with qa chains to work.


Upgrade from upstream kong-2.1.0

Update the app to align with upstream chart 2.1.0 which includes updates for kong to 2.4.1 and kong ingress controller 1.2.0. For more information check the linked changelogs.

Almost all changes are upstream changes.


feature gate deprecated APIs for marshal

Part of #3960
Move deprecated marshal APIs behind gil-refs features gate.

Rebased to unblock CI


Large Diagram doesn't render correctly

Hello,
I'm new to PlantUML but have jumped in with a pretty giant diagram for my first go.  I've been using Notepad++ with your PlantUML plugin as my primary editing/rendering tool.
For most of my diagram build I have had good success, however as I "got toward the end" weird things started happening.  I think it might have to do with the diagram being too large for something in the plugin?
I can render the diagram correctly at the command line using plantuml-1.2022.5.jar but it does not render correctly (after growing past a certain size) in the PlantUML Viewer Notepad++ plugin.
In this example you'll see that a note tied to both the yellow packages on the far right appears in both the "test_working_" images but only in the CMD version of the "test_not_working_" images.  The "test_not_working.txt" file adds 16 lines that are not in the original.  I've been able to also induce "syntax errors" that aren't really there by adding more lines to the diagram.
I'm running Notepad++ v8.4.2 (64-bit) with PlantUML Viewer <IP_ADDRESS>.
At the command line I'm using plantuml-1.2022.5.jar
Both are using Java JRE 1.8.0_331
Take a look at the attachments:

test_working.txt renders correctly in both Notepad++ and at the command line
-- test_working_NPP.png was rendered in Notepad++
-- test_working_CMD.png was rendered at the command line
test_not_working.txt adds 16 lines (all connections) and only renders correctly at the command line (notice the note that links the two yellow packages on the far right only renders in the CMD variant, not the NPP variant)
-- test_not_working_NPP.png was rendered in Notepad++
-- test_not_working_CMD.png was rendered at the command line

Thanks,
Sean
test_working.txt
test_not_working.txt

Hi Sean,
nice to hear you are using the plugin for your work. Thanks for your great investigation and hints here already.
After having a look at your samples, my first guess is that this could be really the size of your diagramm. You are exactly working at the size of 10.000 characters. Version 1.1 indeed contains a bug where exactly here some issues are occuring.
Please have a look at the Changelog for version <IP_ADDRESS>: Fixed crash generating large documents with more than 10000 characters.
Could you please try to render your diagram with the latest release <IP_ADDRESS> to check if the issue also occurs here? For me it seems to work at least.
Let me know if this fixes it also for you.
Cheers,
Philipp

That appears to have fixed it!  Thanks for the quick response!  What incredibly lucky timing that 1.2.06 came out 6 days ago and addressed my very issue!
I had also noticed that the character count was right around 10,000 which seemed suspicious! hehe
Thanks,
Sean

Happy to hear this. Have fun with the plugin!
BR,
Philipp


fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/terraform-ibm-key-protect-all-inclusive
module
patch
v1.1.1 -> v1.1.2

github.com/terraform-ibm-modules/terraform-ibm-observability-instances
module
minor
v1.0.0 -> v1.1.0

github.com/terraform-ibm-modules/terraform-ibm-resource-group
module
patch
v1.0.3 -> v1.0.4

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.

This PR has been generated by Renovate Bot.

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


Add links to categories in main page

Categories on the home page are not clickable. Link them to search result page as /SearchResult/tag:<tag name>
For example, on clicking Novels category, page should redirect to /SearchResult/tag:Novel

Seems to be easy, but i don't have experience with React yet...

@taticorrea It is a good first issue. This issue doesn't require knowledge of react js, but you should be able to set up your environment to run this project locally. If you want you can try to solve this issue, If it works then great, otherwise tell me, I will assign it to someone else.
Should I assign this issue to you?

Is this issue still open?


Sudo does not persist on Linux version

Describe the bug
Wave seems to start a new shell session at each user input without giving the ability to resume a previous shell session, this leads to sudo authentication to not persist and asks for password/fingerprint at each sudo command.
To Reproduce
Steps to reproduce the behavior:

Open Wave
Go to any workspace
Select any tab
Write a command with sudo (eg. sudo whoami)
Write another command with sudo

Expected behavior
Shell should only ask once for sudo authentication and then persist the authentication for a given time (eg. on Ubuntu the default timeout is 15 minutes).
Desktop (please complete the following information):

OS: Ubuntu Linux 22.04.3 / amd64
Version: v0.5.1

Thanks for submitting.  This is on our radar and we plan to put some time into working with how connections are handled (including how they handle sudo) in this release.  No guarantees because we haven't scoped all of the work yet, but we hope to have this fixed in early January.

This is not specifically related to connections though, this sudo handling issue happens locally too when using Wave as a regular terminal.

This is now fixed as of v0.7.4!


fix compilation of ASE gtase because missing sysfs

fix compilation of ASE gtase because missing sysfs

I second @tswhison . If we merge this change into feature/plugin-api, we would be able to test it out before merging feature/plugin-api into master.


Updating kube-burner-ocp and k8s-netperf versions

Type of change

[ ] Refactor
[x] New feature
[x] Bug fix
[x] Optimization
[ ] Documentation Update

Description
Updating versions for kube-burner-ocp and k8s-netperf
kube-burner-ocp - v1.3.0 -> v1.3.1
k8s-netperf - v0.1.23 -> v0.1.24
Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Testing
Will be verified through CI tests.

/test ?

/test e2e-cluster-density-v2-single-node
/test e2e-network-smoke-single-node
/test e2e-node-density-single-node


Delete unused plugins

Remove plugins that we don't use in any builds, and that don't seem to be depended on by any other plugins.

I tried deploying this to Jenkins a few days ago, and we haven't seen any issues with these plugins being missing.


changes made in task and progress section slider

Added a classname to Slider and removed width from Box style

https://user-images.githubusercontent.com/47269110/158030970-c4b16c38-9b7c-4c45-a612-2dd9e1015161.mp4
@Tess-Vanta Video is added

Could you attach a video of the behavior of the page when resizing ?

@Shlok1999  Can u show the page at its max screen width (a image would be fine ) , have u changed the pattern ? like originally 5-6 cards came onone line have u changed it , if yes please keep at as before for max-width screen . only change it for smaller screen .

@SaraswatGit the cards overlapped earlier , so i changed the width and adjusted some space between them

.

@Shlok1999  Please reduce the width of the cards on the max-width screen try to fit in at least fours cards in a line and reduce the width of the cards .

@Shlok1999  Please resolve this issue .

And attach a latest picture of the calendar page at max width with he changes discussed a while earlier . otherwise seems awesome ! .


Possible bug in LJSpeech training data

Some sentences in LJSpeech dataset start with a quote, and seems like quotes are substituted for $ in such cases.
For example, check this file: LJ005-0077.wav (vocaroo link)
Text from the original dataset: "expedient to introduce such measures and arrangements as shall not only provide for the safe custody,
Text from Data/train_list.txt: LJ005-0077.wav|dˈɑːlɚɹ ɛkspˈiːdiənt tʊ ˌɪntɹədˈuːs sˈʌtʃ mˈɛʒɚz ænd ɚɹˈeɪndʒmənts æz ʃˌæl nˌɑːt ˈoʊnli pɹəvˈaɪd fɚðə sˈeɪf kˈʌstədi ,|0
There is dˈɑːlɚɹ in the beginning, but audio doesn't actually have this word. Same happens for other files that start with " (approx. 83 samples).

I have just stumbled upon some other examples, and seems like it also happens with quotes in the middle of a text.
LJ005-0068.wav:
Text from LJSpeech metadata: sought to "rank the prisons they built among the most splendid buildings of the city or town."
Phonemized text from train_list.txt: LJ005-0068.wav|sˈɔːt tə dˈɑːlɚ ɹˈæŋk ðə pɹˈɪzənz ðeɪ bˈɪlt ɐmˌʌŋ ðə mˈoʊst splˈɛndɪd bˈɪldɪŋz ʌvðə sˈɪɾi ɔːɹ tˈaʊn.dˈɑːlɚ|0
So, both quotes in this text were phonemized as dˈɑːlɚ which sounds like a word dollar. Is this intentional substitution or some kind of a bug?

The phonemization+tokenization code that ships with StyleTTS2 correctly processes the original LJSpeech dataset sentence at least. Into :
sˈɔːt tuː `` ɹˈæŋk ðə pɹˈɪzənz ðeɪ bˈɪlt ɐmˌʌŋ ðə mˈoʊst splˈɛndɪd bˈɪldɪŋz ʌvðə sˈɪɾi ɔːɹ tˈaʊn . ''
So that code is working.
Whatever generated the example train_list.txt must have been using some other phonemizer? Or maybe didn't handle quotes properly. 🤔 It would be hilarious if the LJSpeech model had been trained with that odd typo in the training data!
For finetuning you can use the LibriTTS checkpoint as base. If the OOD_texts.txt file is any indication (it contains part of the LibriTTS dataset), then the processing of that dataset did not introduce that error into the transcripts, so it should be ok to use that checkpoint for further things.

Unfortunately it seems like a bug. I took the data directly from VITS repo  (https://github.com/jaywalnut310/vits/blob/main/filelists/ljs_audio_text_test_filelist.txt.cleaned) without any scrutinization.
@Kreevoz I guess you are correct😂. I just tested it and the model can't pronounce "dollar" because of this bug (so dollar was mapped to silence in this model): https://vocaroo.com/1EK8v2wnFGUH (the text was LJSpeech model couldn't pronounce the word, "dollar", because of a bug in preprocessing of VITS's repo.)
I did preprocessing for OOD_texts.txt myself (which was also the training data for the LibriTTS model) and it works fine there, although I noticed that the hyphen character (-) was used as dash (–) which makes the model pause unnaturally when it shouldn't do so.

Maybe I'll redo the preprocessing of LJSpeech dataset and train a new model with corrected data file when I get time.

Unfortunately it seems like a bug. I took the data directly from VITS repo (https://github.com/jaywalnut310/vits/blob/main/filelists/ljs_audio_text_test_filelist.txt.cleaned) without any scrutinization.
@Kreevoz I guess you are correct😂. I just tested it and the model can't pronounce "dollar" because of this bug (so dollar was mapped to silence in this model): https://vocaroo.com/1EK8v2wnFGUH (the text was LJSpeech model couldn't pronounce the word, "dollar", because of a bug in preprocessing of VITS's repo.)
I did preprocessing for OOD_texts.txt myself (which was also the training data for the LibriTTS model) and it works fine there, although I noticed that the hyphen character (-) was used as dash (–) which makes the model pause unnaturally when it shouldn't do so.

I just checked VITS's dataset and found they didn't have dollar. I don't know how I ended up getting dollars there, so it's not VITS's problem but my problem. It gotta be fixed with a new model for sure.

Was the code for the tokenization changed during the development of StarTTS2? I think the implementation you settled with in the end is pretty good though.

Could it be caused by this: https://github.com/yl4579/StyleTTS2/blob/2c427fc45291d5a046d4d46eb0c99d97b0cc1606/meldataset.py#L23


Difficult to see search results

Hi Joosep 👋
I really like your theme and I have been using it for the past week or so. However, I struggle to see the search results:

I forked your repository and changed Search and IncSearch to be:
Search       = { fg = c.background_darker, bg = c.yellow },
IncSearch    = { fg = c.background_darker, bg = c.yellow },

Perhaps the low contrast search results are intentional. In that case you can just close this issue.
Have a nice day and thank you for creating this theme ⭐

Hey, thanks for using the theme!
The lower contrast is mostly intentional since the usual high contrast search highlights in other themes are a bit too much to me. But I can definitely see how it can be hard to see the results (especially on a big screen with small-ish font size). Maybe it would be nice to add some optional higher contrast settings to this theme? There might be a few other cases where I have preferred to have lower contrast for highlights.
Until then, though, since this theme is quite extensible, you should be able to easily add overrides to the highlights like so:
local c = require('palenightfall').colors

require('palenightfall').setup({
  highlight_overrides = {
    Search    = { fg = c.background_darker, bg = c.yellow },
    IncSearch = { fg = c.background_darker, bg = c.yellow },
  },
})

So there should be no need to fork the repo just for customizing the theme

I think that sounds fair! The only issue I've had are the searches. Other than that I've just enjoyed the minimalism.
Thanks for the snippet - I'll add that to my config.


Add contract builds to clippy cache

Recently clippy became one of the longest CI jobs with 6 minutes. Turns out, clippy builds all the contracts but did not cache build results.

The contracts lint quickly now. In the last run, just the cranelift VM was slow, which is because the cranelift dependencies are not yet stored in the cache but will at the next cache invalidation.


feat: appid overwrite

Implements #72
I'm not a rust developer, I hope this works. Tested it local and seems like it.

Thanks @ceifa for the feedback! I implemented your suggestions.

Fixed cargo formatting error.


Cannot find test project even if project exists in solution

Extension Version: 1.0.26
Visual Studio 2017 (15.9.13)
"Goto project" and "Generate tests for type ..." does not locate project if test project is located in a side or sub folder to the source folder like this:

/src/X/Y/Y.ProjectZ/...
/src/X/Y/Y.Tests/Y.ProjectZ.Tests...
/src/solution.sln

or

/src/X.ProjectY/...
/src/solution.sln
/test/X.ProjectY.Tests/...

It seems it only can find test if solution (sln) file is located like this:

/src/X.ProjectY/...
/src/solution.sln
/src/X.Tests/X.ProjectY.Tests/...

Sample Solution:
SentryOne.zip
Screen dump of error message:

Hello
Thanks for the report - I can't repro this - as long as the projects are loaded and in the same solution then it will find them by project name, not by project path. Would you be able to clarify a bit further so I can reproduce the issue you are having?
Thanks for your feedback!
 A new release will be out soon.

1.0.27 is now available which should address the issue. If you wouldn't mind confirming the fix here I'd appreciate it. Thanks again for your help!

Extension version 1.0.27 now finds the test project in the Sample Solution supplied in the original issue note.


Provide infrastructure for 3rd party driver docs

I'm not sure what this would look like or how it would be possible, but as a 3rd party library author it would be great to be able to take advantage of the RethinkDB official docs.
A few options:

Copy the docs manually and change the code samples
Make it possible to maintain just the code samples, and keep the official documentation guides

Relates to #665, https://github.com/apa512/clj-rethinkdb/issues/49

For the PHP driver, I'm using some heuristics to automatically translate the JavaScript examples to PHP syntax, and then apply a final patch to accommodate differences that cannot be translated automatically.
See https://github.com/danielmewes/php-rql/tree/master/docs for the scripts and a README.
It is a pretty hacky solution, but might work for some other languages as well.
Your second proposal I think is going to be 70% covered by https://github.com/rethinkdb/docs/issues/710. Those changes are going to make the parts that are specific to different languages explicit. The missing part would be to provide a convenient way of maintaining the language-specific pieces separately, though it should be fairly easy to write your own scripts for doing that.


update documentation

readme needs some love.

finally getting around to this..

will be starting this very soon

really soon.


Android crashes when any form of ScrollView exists in signed production build "app-release.apk"

Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
Environment:
OS: Windows 10
Node: 8.9.1
Yarn: 1.3.2
npm: 5.5.1
Watchman: Not Found
Xcode: N/A
Android Studio: Version  <IP_ADDRESS> AI-171.4408382
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.51.0 => 0.51.0
Steps to Reproduce

When building the app in normal debug mode, no issue.
Created a dummy certificate and updated the build.gradle correctly, In the "android" directory, I ran "gradlew assembleRelease".
This created the correct SIGNED app-release.apk in the apk directory.
Installed the app-release.apk in both the emulator on computer as well as an LG V20 device.
Both the emulator and the device crash on startup.
Other person with same issue:
GitHub issue 353891887

Expected Behavior
I expected that the release version would work as the debug version did.
Actual Behavior
Signed apk crashes when any screen which has any version of ScrollView in it's render.
The problem is this:
  this._subscribableSubscriptions.forEach
fails because the "this._subscribableSubscriptions" is null (and should not be).
Here is where the error occurs: in Subscribable.js
(..\node_modules\react-native\Libraries\Components\Subscribable.js)
This is the original code.
  componentWillUnmount: function() {
    this._subscribableSubscriptions.forEach(
      (subscription) => subscription.remove()
    );
    this._subscribableSubscriptions = null;
  },

Here is where i removed the failing call.  I have confirmed that this._subscribableSubscriptions returns a null and crashes when the forEach() is called.
  componentWillUnmount: function() {
  console.log(`Subscribable - error location? ${this._subscribableSubscriptions}`)
  if (false) {
    this._subscribableSubscriptions.forEach(
      (subscription) => subscription.remove()
    );
  }
    this._subscribableSubscriptions = null;
  },

Following removing the offending code, the app no longer crashes on startup.
FROM LOGCAT:
12-26 16:02:51.675 20609 20609 D ReactNative: ReactInstanceManager.ctor()
12-26 16:02:51.678 20609 20609 D ReactNative: ReactInstanceManager.createReactContextInBackground()
12-26 16:02:51.678 20609 20609 D ReactNative: ReactInstanceManager.recreateReactContextInBackgroundInner()
12-26 16:02:51.679 20609 20609 D ReactNative: ReactInstanceManager.recreateReactContextInBackgroundFromBundleLoader()
12-26 16:02:51.679 20609 20609 D ReactNative: ReactInstanceManager.recreateReactContextInBackground()
12-26 16:02:51.679 20609 20609 D ReactNative: ReactInstanceManager.runCreateReactContextOnNewThread()
12-26 16:02:51.721 20609 20625 D ReactNative: ReactInstanceManager.createReactContext()
12-26 16:02:51.783 20609 20625 D ReactNative: Initializing React Xplat Bridge.
12-26 16:02:51.784 20609 20625 D ReactNative: Initializing React Xplat Bridge before initializeBridge
12-26 16:02:51.789 20609 20625 D ReactNative: Initializing React Xplat Bridge after initializeBridge
12-26 16:02:51.789 20609 20625 D ReactNative: CatalystInstanceImpl.runJSBundle()
12-26 16:02:51.807 20609 20633 D ReactNative: ReactInstanceManager.setupReactContext()
12-26 16:02:51.807 20609 20633 D ReactNative: CatalystInstanceImpl.initialize()
12-26 16:02:51.812 20609 20633 D ReactNative: ReactInstanceManager.attachRootViewToInstance()
12-26 16:02:51.940 20609 20632 I ReactNativeJS: Running application "test" with appParams: {"rootTag":1}. __DEV__ === false, development-level warning are OFF, performance optimizations are ON
12-26 16:02:51.965 20609 20632 E ReactNativeJS: TypeError: undefined is not an object (evaluating 'this._subscribableSubscriptions.forEach')
12-26 16:02:51.965 20609 20632 E ReactNativeJS:
12-26 16:02:51.965 20609 20632 E ReactNativeJS: This error is located at:
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in ScrollView
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.969 20609 20632 E ReactNativeJS: TypeError: undefined is not an object (evaluating 'this._subscribableSubscriptions.forEach')
12-26 16:02:51.969 20609 20632 E ReactNativeJS:
12-26 16:02:51.969 20609 20632 E ReactNativeJS: This error is located at:
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in ScrollView
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in t
12-26 16:02:52.418 20609 20609 D ReactNative: ReactInstanceManager.detachViewFromInstance()

Reproducible Demo
Because the app crashes on a production build here is a simple App.js file.
This demo can be reproduced by:

creating a new:           react-native init test
substituting the App.js code below for the App.js which is the default on creating a project.
follow instructions for creating a keystore
updating the gradle.build as per the instructions in react-native docs.
build in the android directory with "gradlew assembleRelease"
run and see that with version 51.0 crashes in the Scribbable.js (as show above) although, of course, it's not Scribbable wher the error is, that is just where it occurs.

NOTE: but probably not important.  When I build my app (either my own app or the test app), I must run gradlew assembleRelease twice, it always fails the first time.  I think it needs to reset the transform cache.
ADDITIONAL NOTE: From what the other person who has seen  this said, when reducing the version of React-native to 49.5 the problem goes away.
/**
 * Sample React Native App
 * https://github.com/facebook/react-native
 * @flow
 */

import React, { Component } from 'react';
import {
  Platform,
  FlatList,
  StyleSheet,
  Text,
  View
} from 'react-native';

const instructions = Platform.select({
  ios: 'Press Cmd+R to reload,\n' +
    'Cmd+D or shake for dev menu',
  android: 'Double tap R on your keyboard to reload,\n' +
    'Shake or press menu button for dev menu',
});

export default class Example extends Component<{}> {
  render() {
    return (
      <View style={styles.container}>
        <FlatList
          data={[{key: 0, title: 'Hello1'}, {key: 1, title: 'Hello2'}, {key: 2, title: 'Hello3'}]}
          renderItem={(itm)=> {
            return (<View key={itm.item.key}><Text>{itm.item.title}</Text></View>)
          }}
        />
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#F5FCFF',
  },
  welcome: {
    fontSize: 20,
    textAlign: 'center',
    margin: 10,
  },
  instructions: {
    textAlign: 'center',
    color: '#333333',
    marginBottom: 5,
  },
});

I've got same thing on iOS on react-native 0.48.3, and actually suddenly I have bunch of warning at the beginning
2017-12-26 22:46:10.139 [info][tid:main][RCTCxxBridge.mm:213] Initializing <RCTCxxBridge: 0x6000003c1b30> (parent: <RCTBridge: 0x6080000d2050>, executor: (null))
2017-12-26 22:46:10.186 [warn][tid:main][RCTBridge.m:121] Class RCTCxxModule was not exported. Did you forget to use RCT_EXPORT_MODULE()?
2017-12-26 22:46:10.202 [warn][tid:main][RCTModuleData.mm:69] Module RNCrashes requires main queue setup since it overrides `constantsToExport` but doesn't implement `requiresMainQueueSetup`. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.
2017-12-26 22:46:10.202 [warn][tid:main][RCTModuleData.mm:69] Module RCTCameraManager requires main queue setup since it overrides `constantsToExport` but doesn't implement `requiresMainQueueSetup`. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.
2017-12-26 22:46:10.202 [warn][tid:main][RCTModuleData.mm:69] Module CodePush requires main queue setup since it overrides `constantsToExport` but doesn't implement `requiresMainQueueSetup`. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.
...

I think your issue goes back to the previous thread you were on.... Not this bug.

I've got the same error as you on production version, but at the same time these errors appear on development version. I don't know if it's related.

I am closing the issue I created today for this one.  Here is what I contributed on it.
Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
Environment:
OS: Windows 10
Node: 8.9.1
Yarn: 1.3.2
npm: 5.5.1
Watchman: Not Found
Xcode: N/A
Android Studio: Version  <IP_ADDRESS> AI-171.4408382
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.51.0 => 0.51.0
Steps to Reproduce

When building the app in normal debug mode, no issue.
Created a dummy certificate and updated the build.gradle correctly, In the "android" directory, I ran "gradlew assembleRelease".
This created the correct SIGNED app-release.apk in the apk directory.
Installed the app-release.apk in both the emulator on computer as well as an LG V20 device.
Both the emulator and the device crash on startup.
Other person with same issue:
GitHub issue 353891887

Expected Behavior
I expected that the release version would work as the debug version did.
Actual Behavior
Signed apk crashes when any screen which has any version of ScrollView in it's render.
The problem is this:
  this._subscribableSubscriptions.forEach
fails because the "this._subscribableSubscriptions" is null (and should not be).
Here is where the error occurs: in Subscribable.js
(..\node_modules\react-native\Libraries\Components\Subscribable.js)
This is the original code.
  componentWillUnmount: function() {
    this._subscribableSubscriptions.forEach(
      (subscription) => subscription.remove()
    );
    this._subscribableSubscriptions = null;
  },

Here is where i removed the failing call.  I have confirmed that this._subscribableSubscriptions returns a null and crashes when the forEach() is called.
  componentWillUnmount: function() {
  console.log(`Subscribable - error location? ${this._subscribableSubscriptions}`)
  if (false) {
    this._subscribableSubscriptions.forEach(
      (subscription) => subscription.remove()
    );
  }
    this._subscribableSubscriptions = null;
  },

Following removing the offending code, the app no longer crashes on startup.
FROM LOGCAT:
12-26 16:02:51.675 20609 20609 D ReactNative: ReactInstanceManager.ctor()
12-26 16:02:51.678 20609 20609 D ReactNative: ReactInstanceManager.createReactContextInBackground()
12-26 16:02:51.678 20609 20609 D ReactNative: ReactInstanceManager.recreateReactContextInBackgroundInner()
12-26 16:02:51.679 20609 20609 D ReactNative: ReactInstanceManager.recreateReactContextInBackgroundFromBundleLoader()
12-26 16:02:51.679 20609 20609 D ReactNative: ReactInstanceManager.recreateReactContextInBackground()
12-26 16:02:51.679 20609 20609 D ReactNative: ReactInstanceManager.runCreateReactContextOnNewThread()
12-26 16:02:51.721 20609 20625 D ReactNative: ReactInstanceManager.createReactContext()
12-26 16:02:51.783 20609 20625 D ReactNative: Initializing React Xplat Bridge.
12-26 16:02:51.784 20609 20625 D ReactNative: Initializing React Xplat Bridge before initializeBridge
12-26 16:02:51.789 20609 20625 D ReactNative: Initializing React Xplat Bridge after initializeBridge
12-26 16:02:51.789 20609 20625 D ReactNative: CatalystInstanceImpl.runJSBundle()
12-26 16:02:51.807 20609 20633 D ReactNative: ReactInstanceManager.setupReactContext()
12-26 16:02:51.807 20609 20633 D ReactNative: CatalystInstanceImpl.initialize()
12-26 16:02:51.812 20609 20633 D ReactNative: ReactInstanceManager.attachRootViewToInstance()
12-26 16:02:51.940 20609 20632 I ReactNativeJS: Running application "test" with appParams: {"rootTag":1}. __DEV__ === false, development-level warning are OFF, performance optimizations are ON
12-26 16:02:51.965 20609 20632 E ReactNativeJS: TypeError: undefined is not an object (evaluating 'this._subscribableSubscriptions.forEach')
12-26 16:02:51.965 20609 20632 E ReactNativeJS:
12-26 16:02:51.965 20609 20632 E ReactNativeJS: This error is located at:
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in ScrollView
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.965 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.969 20609 20632 E ReactNativeJS: TypeError: undefined is not an object (evaluating 'this._subscribableSubscriptions.forEach')
12-26 16:02:51.969 20609 20632 E ReactNativeJS:
12-26 16:02:51.969 20609 20632 E ReactNativeJS: This error is located at:
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in ScrollView
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in t
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in RCTView
12-26 16:02:51.969 20609 20632 E ReactNativeJS:     in t
12-26 16:02:52.418 20609 20609 D ReactNative: ReactInstanceManager.detachViewFromInstance()

Reproducible Demo
Because the app crashes on a production build here is a simple App.js file.
This demo can be reproduced by:

creating a new:           react-native init test
substituting the App.js code below for the App.js which is the default on creating a project.
follow instructions for creating a keystore
updating the gradle.build as per the instructions in react-native docs.
build in the android directory with "gradlew assembleRelease"
run and see that with version 51.0 crashes in the Scribbable.js (as show above) although, of course, it's not Scribbable wher the error is, that is just where it occurs.

NOTE: but probably not important.  When I build my app (either my own app or the test app), I must run gradlew assembleRelease twice, it always fails the first time.  I think it needs to reset the transform cache.
ADDITIONAL NOTE: From what the other person who has seen  this said, when reducing the version of React-native to 49.5 the problem goes away.
/**
 * Sample React Native App
 * https://github.com/facebook/react-native
 * @flow
 */

import React, { Component } from 'react';
import {
  Platform,
  FlatList,
  StyleSheet,
  Text,
  View
} from 'react-native';

const instructions = Platform.select({
  ios: 'Press Cmd+R to reload,\n' +
    'Cmd+D or shake for dev menu',
  android: 'Double tap R on your keyboard to reload,\n' +
    'Shake or press menu button for dev menu',
});

export default class Example extends Component<{}> {
  render() {
    return (
      <View style={styles.container}>
        <FlatList
          data={[{key: 0, title: 'Hello1'}, {key: 1, title: 'Hello2'}, {key: 2, title: 'Hello3'}]}
          renderItem={(itm)=> {
            return (<View key={itm.item.key}><Text>{itm.item.title}</Text></View>)
          }}
        />
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#F5FCFF',
  },
  welcome: {
    fontSize: 20,
    textAlign: 'center',
    margin: 10,
  },
  instructions: {
    textAlign: 'center',
    color: '#333333',
    marginBottom: 5,
  },
});

Closing issue for
I am closing the issue I created today for this one.
https://github.com/facebook/react-native/issues/17348


[TJET-42] Add device type to device objects

Added protocol field to device objects and modified API to support it.

Clang formatted a lot of existing code here so sorry in advance if this is hard to piece through


Only add backend.run inputs if kwarg is not None

Summary
kwargs that default to None should not be included in the backend.run inputs. This is also necessary for running qasm3-runner circuits from qiskit-ibm-provider.
Details and comments
Fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 64.098%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_runtime/ibm_backend.py
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
3144

Relevant Lines:
4905

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-2 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 64.098%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_runtime/ibm_backend.py
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
3144

Relevant Lines:
4905

💛  - Coveralls


Support historyApiFallback.rewrites for ng serve to allow path routing on non-standard entry points

Currently it is not possible to run ng serve when using path based routing in Luigi.
In order to get rid of *Webpack npm scripts, we should aim to enable historyApiFallback rewrites in angular-cli
Actual config in webpack.conf.js:
devServer: {
  // because of 404 issue, which redirected us to sampleapp.html instead of index.html
  historyApiFallback: {
    rewrites: [{ from: /./, to: './src/index.html' }]
  }
}

ng serve has an option --proxy where you can specify proxies, but as far as I have seen this does not allow dev server settings.
Possible solution
So we could check if creating a pull request at angular-cli would be possible.
DISCLAIMER: It seems any PR regarding this would get closed, my assumption on that comment: https://github.com/angular/angular-cli/issues/9640#issuecomment-382464344
There are already some topics around it https://github.com/angular/angular-cli/issues?utf8=✓&q=is%3Aissue+historyApiFallback+
Looks like dev-server/index.ts is the place where the default is defined. According to the cli issues, we should also implement the possibility to set it to false (so a general override of the historyApiFallback setting).

Fixed by https://github.com/kyma-project/luigi/pull/288


[ranking_factorization_recommender] - negative sampling

Hi,
I am currently using the ranking_factorization_recommender. When the BPR is done and a negative sample is chosen, I believe that the sample is currently chosen among all other possibilities.
I was wondering if it could be possible to modify this and make use of a column giving information on the items. When sampling for negative samples (ie looking for user/item pairs that never existed) at training time, items would be sampled only from a particular category. I believe that this would speed up the training process, as mentioned here (from paper http://www.shuwu.name/sw/PRFM.pdf ): " when the number of items is very large, the random sampler will derive massive meaningless and ineffective training instances which can not provide much helpful information to tune the personalized ranking lists. For example, in common sense, we can not say that a user dislikes a smart phone because he likes a toothbrush, and this pair, i.e., toothbrush and smart phone, is meaningless in real-world scenarios."
Would you know where in the code I should look at in order to modify this sampling strategy? Or are you planning to enable this feature altogether?
Thank you very much in advance
Best,
Benjamin

Hello @benjaminbraunberkeley,
Thanks for your interest in this!  I'm happy to provide you with some guidance if you want to dig into this more.  I don't think we'll be implementing this, but you're welcome to play around with it.  The sampling code is in the choose_negative_example method of src/unity/toolkits/factorization/ranking_sgd_solver_base.hpp.
The challenge with weighted sampling strategies is that there are a lot of side effects that are not immediately intuitive here. The negative sampling works more as a regularizer on the solution than as an objective to maximize the difference between the positive and negative examples.  The real objective is to end up with a solution such that the predicted scores of the negative items -- those that the negative sampling suppresses -- are actually ranked according to the users preferences.  In other words, the question to ask is actually "Which unobserved items are most resistant to being suppressed?"  This question then leads us to assume that the sampling should be effectively exchangeable or uniform.  Thus, if you target ones that are the most "sensible" to suppress, you may decrease their predictive score while, as a side effect, you increase the predicted score of less desirable user-item pairs.
Looking at the paper you mentioned, I'm quite skeptical.  First, it's relatively expensive to do their sampling - while theirs converges faster per iteration, each iteration is substantially more expensive than MF-BPR.    One could do 20-30 iterations of the MF-BPR method in one iteration of PRFM.  (See Figure 3 vs. Figure 4).  Second, we did not find vanilla MF-BPR to perform that well; it should be combined with choosing the negative sample as the one in a large randomly drawn pool that has the largest predicted score, then adjust the negative sampling pool size -- how many negative samples are considered before one is chosen for the sgd descent -- to accommodate users rating a small proportion of items.   This is still very efficient.   Third, AUC is a weird metric in this case for the reasons given above, and the fact that they don't give details on the number of iterations for different methods in Table 2 or Table 3 also makes me skeptical.

Hi @hoytak! Thanks very much again for your detailed answer! That's very helpful


test: generate certificates

Same as already done in Drawbridge.
Refs https://github.com/profianinc/drawbridge/pull/219

Marking ready on review as requested, @rjzak will make sure these certificates are used in the tests in PEM format


Check if port 3000 is already in use

It is assumed that port 3000 can be used in the forwarding. In my case, however, a Docusaurus process is already running on port 3000. An error should occur at this point or another port should be used. Instead, the browser was simply opened on port 3000 (where Docusaurus was running)
ui	 |I| Forwarding from <IP_ADDRESS>:3000 -> 80

Which version of Glasskube have you tested?
tldr:

We are actually doing it already, but the Docusaurus (node) webserver is a specific case.
It binds on all interfaces and not only on localhost, but we don't want to on all network interfaces for security purposes.

You can read about the full technical details in the original pull request review comment: https://github.com/glasskube/glasskube/pull/208#discussion_r1481948763

Tested with
$ glasskube --version
glasskube version 0.0.3

Hi @berendt, thank you for your report! As @pmig already mentioned, such a check is already in place, although the error is not really propagated to the UI yet.
I just tried the same (also running a docusaurus dev server in the background) and got the correct error message:
could not open cyclops: could not open entrypoint ui: tcp port 3000 is not free

Could you please try to reproduce this bug again and then run netstat -ntlp. The output could be very helpful for us.

Another issue that can happen in this situation is that the browser still has a cached version of the other site. This can happen even if the docusaurus dev server is no longer running. Reloading the page once usually resolves this issue.

@berendt we are closing this issue now, if it still persists feel free to open again.


Address feedback for the dynamic scheduler post

Avoid implying that remote execution is problematic: we have picked
pathological cases for our measurements.
Clarify that this feature is experimental.
Warn users about potential correctness issues.
Clarify that most measurements were taken against Google's internal
remote execution engine and that they are not indicative of RBE
performance.

@dslomov Could you take a look at this? Also, CC @buchgr .

FYI @ericburnett, @bergsieker

Thanks @jmmv! I think someone from RBE should also take a look to make sure they are ok with publishing benchmark results.

I think I have addressed all feedback,and in particular from @EricBurnett (RBE). I think this is ready to merge with an approval from any of you -- and the sooner we amend the post, the better.

I am giving people until 23:00 CEST = 15:00 NYC time to comment.

LGTM from me, though I'll leave it to bazel folk to formally Approve and merge this.

@dslomov It's already past the deadline you gave and nobody has raised objections. In fact, they have LGTMd the post. So I consider this good to go. I'll dismiss your request to make changes in about an hour, just in case you are a little bit late.

@jmmv The post LGTM as well—I mentioned that over chat but should mention it here, too.

hey it's only 22:08 CEST here
On Wed, 6 Feb 2019, 21:47 David Jacobs<EMAIL_ADDRESS>wrote:

@jmmv https://github.com/jmmv The post LGTM as well—I mentioned that
over chat but should mention it here, too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/bazel-blog/pull/152#issuecomment-461181315,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AExrX6iLxVeJC1Bxk6eQkazRWWIxBdSQks5vKz9ugaJpZM4ahZMq
.

(I guess I messed up timezone conversions)
On Wed, 6 Feb 2019, 22:08 Dmitry Lomov<EMAIL_ADDRESS>wrote:

hey it's only 22:08 CEST here
On Wed, 6 Feb 2019, 21:47 David Jacobs<EMAIL_ADDRESS>wrote:

@jmmv https://github.com/jmmv The post LGTM as well—I mentioned that
over chat but should mention it here, too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/bazel-blog/pull/152#issuecomment-461181315,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AExrX6iLxVeJC1Bxk6eQkazRWWIxBdSQks5vKz9ugaJpZM4ahZMq
.

Heh, anyway... is there a point in waiting an extra hour?

no it's fine, go ahead and submit ;)
On Wed, 6 Feb 2019, 22:10 Julio Merino<EMAIL_ADDRESS>wrote:

Heh, anyway... is there a point in waiting an extra hour?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/bazel-blog/pull/152#issuecomment-461188538,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AExrX32vNjEJOVdBGrrFBEHLeD1UhCbvks5vK0TAgaJpZM4ahZMq
.

Thanks to everyone for the feedback! And let's put a process in place to coordinate better on any future posts.


update to use trading_as rather than name for Trading As

related to https://github.com/ONSdigital/ras-party/pull/121 and https://github.com/ONSdigital/ras-backstage/pull/94

Codecov Report

Merging #121 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #121   +/-   ##
=======================================
  Coverage   96.13%   96.13%
=======================================
  Files          32       32
  Lines        1138     1138
=======================================
  Hits         1094     1094
  Misses         44       44

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 e199c7d...25e61e9. Read the comment docs.

 US108: Display Trading As on RU Details


Support multiple networks configured vis SetupUI

Setup UI should support setting up federations on

[ ] Testnet
[x] Regtest
[ ] Signet
[ ] Mainnet

Hello I'll like to work on this issue

Still an issue because a user has to select the right network as configured in deployed bitcoin service. Selecting any other network is not supported

Actually, the issue with switching network at runtime is discussed in #4. Closing this one as duplicate


Tune the error message if model fails to generate embedding

When model fails to generate embedding, neural search will return null pointer exception. How about we check the result first and throw a more readable error message like "No embedding generated from model"?
{
   "type":"null_pointer_exception",
   "reason":"Cannot read the array length because \"array\" is null"
}

Looks like this is done in InferenceProcessor as part of PR https://github.com/opensearch-project/neural-search/pull/333


Startup error with Spring Boot 3.3.0 and Blaze Persistence Repositories

Description
After updating my project to the new Spring Boot 3.3.0, I encountered errors during the application startup in EntityView repositories (those extending EntityViewRepository) from Blaze Persistence:
An attempt was made to call a method that does not exist. The attempt was made from the following location:

    com.blazebit.persistence.spring.data.base.query.JpaParameters.<init>(JpaParameters.java:58)

The following method did not exist:

    'void org.springframework.data.repository.query.Parameters.<init>(java.lang.reflect.Method)'

The calling method's class, com.blazebit.persistence.spring.data.base.query.JpaParameters, was loaded from the following location:

    jar:file:{m2-path}/.m2/repository/com/blazebit/blaze-persistence-integration-spring-data-base-3.1/1.6.11/blaze-persistence-integration-spring-data-base-3.1-1.6.11.jar!/com/blazebit/persistence/spring/data/base/query/JpaParameters.class

The called method's class, org.springframework.data.repository.query.Parameters, is available from the following locations:

    jar:file:{m2-path}/.m2/repository/org/springframework/data/spring-data-commons/3.3.0/spring-data-commons-3.3.0.jar!/org/springframework/data/repository/query/Parameters.class

The called method's class hierarchy was loaded from the following locations:

    org.springframework.data.repository.query.Parameters: file:{m2-path}/.m2/repository/org/springframework/data/spring-data-commons/3.3.0/spring-data-commons-3.3.0.jar

Action:

Correct the classpath of your application so that it contains compatible versions of the classes com.blazebit.persistence.spring.data.base.query.JpaParameters and org.springframework.data.repository.query.Parameters

The issue seems to be in the JpaParameters class of BP, which is trying to call a non-existent method in the superclass Parameters from Spring Data Commons. Additionally, this class from BP is also trying to override a method that no longer exists.

Expected behavior
I expected the EntityView repositories to initialize and work correctly after updating to Spring Boot 3.3.0. This update is particularly important because Spring Boot 3.3.0 includes an upgrade to Hibernate 6.5.x. The new Hibernate version brings significant improvements, including the ability to pre-generate IDs for entities that are yet to be persisted. Consider a scenario where UUIDs (PKs) are generated within a mobile application. With the new Hibernate version, you can seamlessly handle these pre-generated UUIDs during the persistence process.
Actual behavior
The application fails to start, specifically in repositories that extend EntityViewRepository, due to missing methods in the Parameters class from Spring Data Commons.
Steps to reproduce

Update a Spring Boot project to version 3.3.0;
Create a repository that extends EntityViewRepository;
Attempt to compile and start the application.

Environment

Version: 1.6.11
Spring Boot: 3.3.0
JPA-Provider: 6.5.2.Final
DBMS: h2, postgresql
Application Server: N/A

This is why you should never use a library without the full support of a whole community.

In holidays this week, could try to take care of sb 3.0 support after that

@EugenMayer Why did you find my words so offensive? It's a truism: the library is great but needs a large community

We managed to keep up with the Spring boot versions so far and will do so in the future as well, but someone from the community needs to step up and help with that. So far, @EugenMayer worked on this, so he will surely look into this when he has time. If you can't await that, please provide a PR with a fix.

Started with the integration in #1912 - might take a bit since we have to create new integration libraries


[CHALLENGE SUBMISSION] - Challenge Six (Durable Entities with C#, Vue.js)

Please provide the following information for your submission:
What is your name? (First, Last)
Stuart Leaver
Where is your GitHub Repo ?(Link to your challenge solution)
https://github.com/stuartleaver/seasons-of-serverless/tree/main/06-the-magic-chocolate-box
What Challenge is this for? (Challenge number between 1 and 7)
6
(Optional) Anything else we should know? e.g., language used, location, blog post, tell us how you solved this solution, including any challenges you faced solving it.
The solution makes use of Azure Functions written in C#, Vue.js. For the Functions, Durable Entities are used to maintain the state of different families. This state being the chocolate box they selected and the reservations their family members have made.
As the functions for the Durable Entities are hosted in a Function app, it is possible to try them out separate from the UI. There are details on the endpoints in the README.md file. There is also an example 'family' in SHEPPARDEXAMPLE.md.
The endpoint where they can be tested is https://magicchocolatebox.azurewebsites.net

thank you for this submission!

thank you for this submission!


cplp-656- delete business partner number of assigned user

delete business partner number of assigned user

@Akshay-Chaudhari-BMW please share if the update of Keycloak is already a part of the commit. If not, I propose we add that before letting someone start the review.

Alright all good then ;)


Split into multiple files

To start with this is my first time looking at the code, so take this as the first impression that it is. Does it make sense to split the project into multiple files? The ################### sections seam to build on each other. That may be a place to start the splitting.
As always just starting a discussion, and willing to help implement any fix.

Yes, this might be a good idea. What are the pros and cons?

It would make the code more manageable
It would make it slightly more complicated for functions to call each other across the files
But it wouldn't have to affect the end-user API because we could just import all the individual files in __init__.py (?)

Other considerations?


Add Pro Tip mentioning JOSE and the importance of publishing

Sorry for the typos, I am always forgetting to consult grammarly!

Thanks @arm61 for the addition :smile:


redis option for json serializer

To use json instead of pickle for serialize, you' d better set a redis instance like this:
from flask_session import Session, RedisSessionInterface

RedisSessionInterface.serializer = json
rds = redis.Redis(decode_responses=True) # make sure utf8
app.config['SESSION_REDIS'] = rds

This issue was moved to mcrowson/flask-session#11

Msgspec will be added in 0.7.0 with JSON and Msgpack support. Also note, subclassing interfaces will need to import redis.RedisSessionInterface.
This is a great tip to use for best security until Pickle is fully removed in 1.0.0


Properties reset

This PR adds the ability to reset properties of Companies, Deals and Contacts back to null.
The problem is that we have previously tried to check for modified properties on the objects. However, the result of the check is all properties that have a value set to something other than null, and not a true diff of what has actually changed.
Why we have not seen any issues with this previously is that the hubspot API seem to be smart enough to only update the properties that have actually been modified on the object.
This PR will therefor remove our check for modified properties as it is not working and post all the properties of the object to hubspot. Their API is able to handle the diff instead of trying to do this in the SDK.

@elindanielsson @simgu Please have a look if you have the time


update @apollographql dependencies

What problem does this feature solve?
Ability to use vuejs in corporate environments with automated license checks for controls & compliance.
In particular, these dependencies cause friction for me on<EMAIL_ADDRESS>
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
What does the proposed API look like?
The project moved from graphql/graphql-language-service to graphql/graphiql.
The change may ultimately be upstream, but this project is where I feel it.

A quick yarn why @apollographql/graphql-language-service-interface reveals the following result:
info Reasons this module exists
   - "@vue#cli#@vue#cli-ui#vue-cli-plugin-apollo#apollo#apollo-language-server" depends on it
   - Hoisted from "@vue#cli#@vue#cli-ui#vue-cli-plugin-apollo#apollo#apollo-language-server#@apollographql#graphql-language-service-interface"

It looks like #5663 was opened for the same issue, but closed without resolution and only points at one such link meanwhile my issue has four links.  I'd like to offer patches and get this resolved, but I don't have experience navigating monorepos and github searches seem inadequate.

is there an update on this issue? It's currently blocking the installation of the @vue/cli in enterprise environments.

@sodatea I see you in #5663 pointed @antonioaguilar on which dependency needs to be updated.  What led you to finding that?  I'd like to get this pair of issues resolved.

I looked at the first section of the yarn why output and then looked for the package.json of each package that appeared in the result to see which one was using the outdated dependency.
=> Found "<EMAIL_ADDRESS>info Reasons this module exists
   - "@vue#cli#@vue#cli-ui#vue-cli-plugin-apollo#apollo#apollo-language-server" depends on it
   - Hoisted from "@vue#cli#@vue#cli-ui#vue-cli-plugin-apollo#apollo#apollo-language-server#@apollographql#graphql-language-service-interface"
                                                                     ^

any ETA on this? these are red flags that I have to explain to our InfoSec team regularly.


Using custom text matcher instead of hasProperty matcher.

Github import of changes:

Using custom text matcher instead of hasProperty because hasProperty formats the description differently and it looks bad with the new error message logs.

Old one shown as: an object with text<EMAIL_ADDRESS>New one shown as<EMAIL_ADDRESS>PiperOrigin-RevId: 145150301

I think this one needs to wait for https://github.com/google/EarlGrey/pull/401, but both of those are good to merge


fix: handle backend responses more gracefully in datasets requests

Handles problematic dataset list backend responses more gracefully, by printing one warning per call, rather than throwing an error.
Also, unrelated to the main change, but makes the auth argument of the internal _get_datasets function positional, for consistency.

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (7394f23) 78.37% compared to head (2edbace) 40.74%.

:exclamation: Current head 2edbace differs from pull request most recent head dc6e4ee. Consider uploading reports for the commit dc6e4ee to get more accurate results

Files
Patch %
Lines

src/datasets.jl
71.42%
4 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #46       +/-   ##
===========================================
- Coverage   78.37%   40.74%   -37.64%
===========================================
  Files          16       16
  Lines        2234     2216       -18
===========================================
- Hits         1751      903      -848
- Misses        483     1313      +830

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


[1.21][neoforge] Chimera phase into half of a block when sitting preventing any interaction

Describe the bug
It seems that the collision of the chimera when sitting is not working properly. So it stays halfway inside the block where it should be sitting.
I tried removing the blocks underneath, but it fell and stopped half inside the next block below it.
To Reproduce
Steps to reproduce the behavior:

summon a chimera
Right click to have it sit it

Expected behavior
The chimera should be on the block, not inside the block.
Screenshots

System (please complete the following information):

Occultism Version: 1.136.5
OS: Windows
Minecraft Version: 1.21

uhh .. I have to look into that more. I think in 1.21 minecraft incorporates scale into entities (before it mostly ignored it) which seems to cause all these issues


Added accessibility complaint form

Adds accessibility subpage complaint form and tests update.
Additions

Adds accessibility subpage complaint form.

Changes

Updates accessibility subpage test to look for form.

Testing

Visit /sub-pages/file-a-formal-accessibility-complaint-or-website-feedback/, see form

Review

@KimberlyMunoz
@sebworks

Screenshots

Tests pass and everything looks good. I flagged a couple things above which are mostly questions about how we want to treat phone numbers and email addresses as fields.

:+1:


Update the Fotografias section

I added a blue background to the paragraphs and borders radius to keep the shapes and layout consistency like the button. and some padding to make some room for the paragraphs.

Thanks Samuel for the help! 😄

Thanks Samuel for the help! 😄

@Pextre it's been my pleasure to help.

@Pextre it's been my pleasure to help.


How to run On Real IBM Quantum Computer using  qiskit_ibm_runtime import QiskitRuntimeService

how to run Circuit Knitting Toolbox 0.7.0 on Real IBM Quantum Computer using  qiskit_ibm_runtime import QiskitRuntimeService as well as local computer using sampler? means when i run on real computer it cut circuits on real computer otherwise run on local system.

Circuit Knitting Toolbox 0.7.0

Why the old version?  If it's because you want to use CutQC, the following instructions may not work there.
Essentially, the cutting tutorials now phrase everything in terms of "fake backends", because if you have qiskit-ibm-runtime set up correctly, the only thing you need to do is change one of the tutorials to use a real backend, and then it will work the same but on hardware.

Circuit Knitting Toolbox 0.7.0

Why the old version? If it's because you want to use CutQC, the following instructions may not work there.
Essentially, the cutting tutorials now phrase everything in terms of "fake backends", because if you have qiskit-ibm-runtime set up correctly, the only thing you need to do is change one of the tutorials to use a real backend, and then it will work the same but on hardware.

i want it because i am working in it. tell me how to run it on real IBM Quantum

tell me how to run it on real IBM Quantum

I think you are looking for https://docs.quantum.ibm.com/guides/execute-on-hardware


ngtcp2: disable examples since they fail to compile on aarch64-linux …

…and are not installed anyway
Oversite happened in #189757
Description of changes

Things done

Built on platform(s)

[ ] 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/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Working build with this variant?
diff --git a/pkgs/development/libraries/ngtcp2/default.nix b/pkgs/development/libraries/ngtcp2/default.nix
index 90372cc97a2..646ce4ecfa1 100644
--- a/pkgs/development/libraries/ngtcp2/default.nix
+++ b/pkgs/development/libraries/ngtcp2/default.nix
@@ -1,5 +1,5 @@
 { lib, stdenv, fetchFromGitHub
-, autoreconfHook, pkg-config, file
+, cmake
 , libev, nghttp3, quictls
 , cunit, ncurses
 , withJemalloc ? false, jemalloc
@@ -18,13 +18,13 @@ stdenv.mkDerivation rec {

   outputs = [ "out" "dev" "doc" ];

-  nativeBuildInputs = [ autoreconfHook pkg-config file ];
+  nativeBuildInputs = [ cmake ];
   buildInputs = [ libev nghttp3 quictls ] ++ lib.optional withJemalloc jemalloc;
   checkInputs = [ cunit ncurses ];

-  preConfigure = ''
-    substituteInPlace ./configure --replace /usr/bin/file ${file}/bin/file
-  '';
+  cmakeFlags = [
+    "-DENABLE_STATIC_LIB=OFF"
+  ];

   doCheck = true;
   enableParallelBuilding = true;


#30 add array length polyfill

A known limitation will now be that an object cannot have a property named length as it will be interpreted as a call to a length function.
Also contributing, @nilssonan.

@AgronKabashi Any chance of getting this one merged? Currently it's not possible to check the length of an array.


Vortex isn't seeing release 0.2.0 on Nexus

I'm not sure what's going on, but Vortex isn't recognizing the release of 0.2.0 from the Nexus site. The extensions pane only sees 0.1.5 and isn't finding any updates. I could install 0.2.0 manually, but I'm not sure if that might screw something up.
I should mention that Vortex doesn't load the extension in %APPDATA%\Vortex\plugins\game-acecombat7skiesunknown instead the folder is %APPDATA%\Vortex\plugins\AC7 Support for Vortex-125-0-1-5-1599583613 I don't know if that might have something to do with it?

Vortex will only load updates once they've been added to a special file in the Vortex repo that it reads for available updates.
You should be seeing the update available now. If you manually install it (aka into %APPDATA%\Vortex\plugins\game-acecombat7skiesunknown Vortex unfortunately won't auto-update it).

That's... really annoying. They're taking feedback for Vortex updates, I may bring that up because it should just check Nexus itself, not some special file in a repo. Thanks for the help!

Just to give you a heads up, I've raised this before with them and they've indicated that this is the approach they're sticking to. They have their reasons and as much as it's irritating (especially for someone in my position) it's also reasonably integral to Vortex's current extensibility model.
I definitely agree, but just don't get your hopes up too high on that changing :)


Extend max delayed job from 5 mins to 20 mins

We have been getting a lot of timeouts, https://app.bugsnag.com/ruby-for-good/human-essentials/errors/64e437ef88578c00083d0b99?filters[event.unhandled]=true&filters[event.since]=30d&filters[app.release_stage]=production&sort=events
We should separately do a check to see if the particular job, HistoricalDataCacheJob, can be made more efficient. But this is an easy fix.

Thank you sir


feat: Add move cursor and extend selection to word boundary

Added moveCursorToWordBoundary and extendSelectionToWordBoundary (forward and selection).
Shortcut keys:

Move cursor to word boundary (Alt + ←/→)
Extend selection to word boundary (Shift + Alt + ←/→)

This is an example:
https://github.com/reqable/re-editor/assets/75752751/ebc376fa-4ef7-4fcc-9b0b-16b5707b0daa

👏👏👏 Thanks!


Loosen version constraints on protobuf

Hello,
We would like to use google-cloud-batch within Google Cloud Composer. Unfortunately there is no way to install it at the moment because of a conflicting requirement on protobuf.
In particular, google-cloud-batch requires protobuf!=3.20.0 whereas almost all recent versions of Composer have protobuf==3.20.0 installed as can be seen here.
Do you think it is possible to loosen this requirement on your side?
Thank you for you help,

Hello @alexandreyc,
protobuf 3.20.0 and 3.20.1 was explicitly excluded in new releases because of a security bulletin. I'm reaching out to the Cloud Composer team to determine next steps.

Googlers see b/282956119

Hello @parthea,
Do you have any news about this?
Thanks,

Regretfully I don't have any updates. I've sent a follow up message to the Cloud Composer team to request an ETA.

I'm going to transfer this issue to the google-cloud-python repository as we are preparing to move the code for google-cloud-batch to that repository. I've also pinged the Cloud Composer team to get information about their next release candidate which will support protobuf >= 4.x.