langchain agent -> Exiting LLM run with output: { "generations": [ [ null ] ] }

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain.js documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain.js rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
export const GPTmodel = (model, temp) => {
  return new ChatOpenAI({
        model,
        temperature,
        configuration: {
            baseURL: LLM_GATEWAY_BASE_URL,
            dangerouslyAllowBrowser: true,
            defaultHeaders: {
              blabla
            },
        },
        azureOpenAIBasePath: `ourpath`,
        azureOpenAIApiDeploymentName: model,
        azureOpenAIApiVersion: '2024-02-01',
        azureOpenAIApiKey: 'fake-key-we-use-auth',

}

export const ProcessMiningTutor = async () => {
    const llm = GPTmodel(GPTModel.GPT4, 0);

    const promptTemplate = SystemMessagePromptTemplate.fromTemplate(`
    answer the user question in a funny and rap like way.
    The user question is: {input}
    also what is the value of foo?
    `);

    const prompt = ChatPromptTemplate.fromMessages([
        [ 'system', 'You are a helpful assistant.' ],
        promptTemplate,
        new MessagesPlaceholder('agent_scratchpad'),
    ]);
    const tools = [
        new DynamicTool({
            name: 'FOO',
            description: 'call this to get the value of foo.',
            // eslint-disable-next-line @typescript-eslint/require-await
            func: async () => 'baz',
        }),
    ];

    const agent = await createOpenAIFunctionsAgent({
        llm,
        prompt,
        tools,
    });

    return new AgentExecutor({
        agent,
        tools,
        verbose: true,
    }).withConfig({ runName: 'Agent' });
};

then when I call it

 const {
        isLoading, error,
    } = useQuery(
        {
            // eslint-disable-next-line @stylistic/max-len
            queryKey: [ 'agentResponse', currentQuestion?.id, currentQuestion, currentQuestion?.agent, currentQuestion?.question, askedQuestions ],
            queryFn: async () => {
                if (!currentQuestion) {
                    return;
                }
                console.log(currentQuestion);
                // I have multiple agents so just think I'm giving the agent from above
                const agentName = currentQuestion.agent;
                const agentCreator = agentRegistry[agentName];
                const executor = (await agentCreator()) as AgentExecutor;

               // this thing ALWAYS fails.
                const result = executor.streamEvents({ input: currentQuestion.question }, { version: 'v1' });

                for await (const event of result) {
                    const eventType = event.event;
                    if (eventType === 'on_chain_start') {
                        // Was assigned when creating the agent with `.withConfig({"runName": "Agent"})` above
                        if (event.name === 'Agent') {
                            console.log('\n-----');
                            console.log(
                                `Starting agent: ${event.name} with input: ${JSON.stringify(
                                    event.data.input,
                                )}`,
                            );
                        }
                    } else if (eventType === 'on_chain_end') {
                        // Was assigned when creating the agent with `.withConfig({"runName": "Agent"})` above
                        if (event.name === 'Agent') {
                            console.log('\n-----');
                            console.log(`Finished agent: ${event.name}\n`);
                            console.log(`Agent output was: ${event.data.output}`);
                            console.log('\n-----');
                        }
                    } else if (eventType === 'on_llm_stream') {
                        const content = event.data?.chunk?.message?.content;
                        // Empty content in the context of OpenAI means
                        // that the model is asking for a tool to be invoked via function call.
                        // So we only print non-empty content
                        if (content !== undefined && content !== '') {
                            console.log(`| ${content}`);
                        }
                    } else if (eventType === 'on_tool_start') {
                        console.log('\n-----');
                        console.log(
                            `Starting tool: ${event.name} with inputs: ${event.data.input}`,
                        );
                    } else if (eventType === 'on_tool_end') {
                        console.log('\n-----');
                        console.log(`Finished tool: ${event.name}\n`);
                        console.log(`Tool output was: ${event.data.output}`);
                        console.log('\n-----');
                    }
                }

Error Message and Stack Trace (if applicable)
@tanstack_react-query.js?v=77745d11:2942 Uncaught TypeError: Cannot read properties of undefined (reading 'content')
    at OpenAIFunctionsAgentOutputParser._baseMessageToString (chunk-NSISG4FD.js?v=77745d11:32:27)
    at OpenAIFunctionsAgentOutputParser._callWithConfig (chunk-NSISG4FD.js?v=77745d11:54:22)
    at OpenAIFunctionsAgentOutputParser._callWithConfig (chunk-2YXJZ3EI.js?v=77745d11:12447:28)
    at async OpenAIFunctionsAgentOutputParser._streamIterator (chunk-2YXJZ3EI.js?v=77745d11:12392:5)
    at async OpenAIFunctionsAgentOutputParser.transform (chunk-2YXJZ3EI.js?v=77745d11:12612:5)
    at async _RunnableSequence._streamIterator (chunk-2YXJZ3EI.js?v=77745d11:13336:24)

then after using verbose: true on the agent ->
 Entering LLM run with input: {
  "messages": [
    [
      {
        "lc": 1,
        "type": "constructor",
        "id": [
          "langchain_core",
          "messages",
          "SystemMessage"
        ],
        "kwargs": {
          "content": "You are a helpful assistant.",
          "additional_kwargs": {},
          "response_metadata": {}
        }
      },
      {
        "lc": 1,
        "type": "constructor",
        "id": [
          "langchain_core",
          "messages",
          "SystemMessage"
        ],
        "kwargs": {
          "content": "\n    answer the user question in a funny and rap like way.
    The user question is: what the dawg doing?
    also what is the value of foo?  ",
          "additional_kwargs": {},
          "response_metadata": {}
        }
      }
    ]
  ]
}
chunk-2YXJZ3EI.js?v=77745d11:5262 [llm/end] [1:chain:Agent > 2:chain:OpenAIFunctionsAgent > 7:llm:ChatOpenAI] [1.28s] Exiting LLM run with output: {
  "generations": [
    [
      null
    ]
  ]
}
chunk-2YXJZ3EI.js?v=77745d11:5225 [chain/start] [1:chain:Agent > 2:chain:OpenAIFunctionsAgent > 8:parser:OpenAIFunctionsAgentOutputParser] Entering Chain run with input: {}
chunk-2YXJZ3EI.js?v=77745d11:5243 [chain/error] [1:chain:Agent > 2:chain:OpenAIFunctionsAgent > 8:parser:OpenAIFunctionsAgentOutputParser] [0ms] Chain run errored with error: "Cannot read properties of undefined (reading 'content')\n\nTypeError: Cannot read properties of undefined (reading 'content')\n    at OpenAIFunctionsAgentOutputParser._baseMessageToString (http://localhost:9000/node_modules/.vite/deps/chunk-NSISG4FD.js?v=77745d11:32:27)\n    at OpenAIFunctionsAgentOutputParser._callWithConfig (http://localhost:9000/node_modules/.vite/deps/chunk-NSISG4FD.js?v=77745d11:54:22)\n    at OpenAIFunctionsAgentOutputParser._callWithConfig (http://localhost:9000/node_modules/.vite/deps/chunk-2YXJZ3EI.js?v=77745d11:12447:28)\n    at async OpenAIFunctionsAgentOutputParser._streamIterator (http://localhost:9000/node_modules/.vite/deps/chunk-2YXJZ3EI.js?v=77745d11:12392:5)\n    at async OpenAIFunctionsAgentOutputParser.transform (http://localhost:9000/node_modules/.vite/deps/chunk-2YXJZ3EI.js?v=77745d11:12612:5)\n    at async _RunnableSequence._streamIterator (http://localhost:9000/node_modules/.vite/deps/chunk-2YXJZ3EI.js?v=77745d11:13336:24)"

Description
I'm trying to use langchain to create an agent with openai functions/tools.
My application is living fully in the front-end. React.
In my network tab I can see the responce of the llm is SUCCESSFUL I CAN SEE THE CONTENT but the parser fails
But I CAN'T get langchain agents to work, since I'm using it on the front-end and the library is made for the back-end I suppose  there are some kind of timeouts going under the hood that don't await the completion of a agent/tool and it just throws error ( inputVariables becomes always undefined :trollface:  )
( after some more reasearch I foudn this guy has the same issue but in angular  Seems like its a known problem for langchain when doing it in front-end https://stackoverflow.com/questions/77075029/langchain-simple-llm-predict-in-angular-returns-empty-result )
BUT IF I do it in a nodeJS environment it works as expected
But I can see the network tab

that the responce is there -_-
P.S. I know I made this and a post in discussions, sorry for the spam, I'm on a tight deadline and need to get this working as soon as possible
System Info
"@langchain/core": "^0.2.31",
"@langchain/openai": "^0.2.10",
"langchain": "^0.3.0",
platform macos
node version -> Node.js v20.12.2.
npm version 10.8.2

 Uncaught TypeError: Cannot read properties of undefined (reading 'content')
    at OpenAIFunctionsAgentOutputParser._baseMessageToString (chunk-NSISG4FD.js?v=77745d11:32:27)
    at OpenAIFunctionsAgentOutputParser._callWithConfig (chunk-NSISG4FD.js?v=77745d11:54:22)
    at OpenAIFunctionsAgentOutputParser._callWithConfig (chunk-2YXJZ3EI.js?v=77745d11:12447:28)
    at async OpenAIFunctionsAgentOutputParser._streamIterator (chunk-2YXJZ3EI.js?v=77745d11:12392:5)
    at async OpenAIFunctionsAgentOutputParser.transform (chunk-2YXJZ3EI.js?v=77745d11:12612:5)
    at async _RunnableSequence._streamIterator (chunk-2YXJZ3EI.js?v=77745d11:13336:24)

but my issue is different @dosu
I get
Uncaught TypeError: Cannot read properties of undefined (reading 'content')
at OpenAIFunctionsAgentOutputParser._baseMessageToString (chunk-NSISG4FD.js?v=77745d11:32:27)
at OpenAIFunctionsAgentOutputParser._callWithConfig (chunk-NSISG4FD.js?v=77745d11:54:22)
at OpenAIFunctionsAgentOutputParser._callWithConfig (chunk-2YXJZ3EI.js?v=77745d11:12447:28)
at async OpenAIFunctionsAgentOutputParser._streamIterator (chunk-2YXJZ3EI.js?v=77745d11:12392:5)
at async OpenAIFunctionsAgentOutputParser.transform (chunk-2YXJZ3EI.js?v=77745d11:12612:5)
at async _RunnableSequence._streamIterator (chunk-2YXJZ3EI.js?v=77745d11:13336:24)
I don't even get a response from langchain... ( but I can see in my network thab that the ai responded )

I managed to narrow it down to the issue being with vite. I tried making the exact same thing as -> https://js.langchain.com/v0.1/docs/modules/agents/how_to/custom_agent/
in a normal create-react-app it worked. But create-react-app is not using vite.But in my repo regardless of the config it wont work.

I managed to narrow it down to the issue being with vite. I tried making the exact same thing as -> https://js.langchain.com/v0.1/docs/modules/agents/how_to/custom_agent/
in a normal create-react-app it worked. But create-react-app is not using vite.But in my repo regardless of the config it wont work. @dosu

so what I'm getting is I need to add a polyfill to my vite config in order for it to work ? @dosu

@dosu what about vite polyfill?


Where is waxbee.jar

The readme.html says to run the waxbee.jar file but there is no waxbee.jar in the repository or information on how to build it.
There is a manifest.txt that lists the waxbee.jar file but not where to find it.

Sorry for the late reply!
The release .zip contains everything to run it - including "waxbee.jar" -- just go to the "Release" section in Github to download the .zip package. Follow instructions. Happy drawing!
https://github.com/popbee/waxbee/releases/latest
I'll add this link to the readme so there is less "searching".


Add filter(_:orElse:) which takes a parameter for the failure error

The type of the filter BrightFutures already has is
Future<V, E> -> (V -> Bool) -> Future<V, BrightFuturesError<E>>

That's annoying if you want to use filter in a chain of operations that share the same error type: a.flatMap(b).flatMap(c).filter(p).flatMap(d) where all the error types of a,b,c match. Suddenly d has to fail with a BrightFuturesError<E> instead of the E the others do: and if we have another filter somewhere in the chain we get BrightFuturesError<BrightFuturesError<E>>... A prettier solution at the type level is to convert filter-failure into an error, but one that matches the error type of the chain.
(Side note: this will get more compelling when generic typealiases land: typealias NetworkOp<A, B> = A -> Future<B, NetworkErrorEnum>.)
One can sort of work around this with mapError but it's rather ugly:
a.filter(p).mapError { error in
    switch error {
    case .NoSuchElement:
        return .MyOwnErrorCase
    case .External(let originalError):
        return originalError
    default: // trust the BrightFutures docs that this won't happen (ouch)
        fatalError("Oops oh well")
    }
}

This filter version instead lets you specify the error to return when the filter predicate fails. I called the argument orElse: for no very compelling reason.

Hi @tikitu, thanks for the PR!
I think you're right in that it is not very nice to use filter combined with your custom error types. Your solution definitely is an improvement, but I'm thinking of an alternative that I'd like to get your opinion on:
We could define a protocol BrightFuturesErrorType that defines a method called noSuchElementError(). We could then define (a variant of) filter on Futures that have an error type conforming to BrightFuturesErrorType. The implementation of filter would then create an instance of the custom error type. The only thing you'd have to do is make your error type conform to the protocol and everything would work nicely.
Your proposed solution is a little bit more flexible (because you can return any error), but also adds a second parameter.
What do you think?

For the use case that prompted this PR I definitely want the second parameter: it means I can use two different filter calls in a futures chain and have each return a different error enum case. Using a protocol pushes the decision "things I might want to filter on" into the (extension on the) error type, which means it has to have one (context-independent) answer.
My use case is something like this (not showing you the real thing because it's full of my custom operators...):
authenticateUser(email: email, password: password)
.filter(allSitesResponded, orElse: .SitesDownForMaintenance)
.filter(userHasAccessToAtLeastOneSite, orElse: .UsernameOrPasswordNotRecognised)
.flatMap(getUserChoiceOfWhichSiteToEnter)
.flatMap(getHomepage)
.filter(homepageHasFeatureX, orElse: .FeatureXNotSupported)

+1 on this, just stumbled upon a similar use case and filter(_:orElse:) would perfectly fit my needs

Sorry for the inactivity. I've revisited your proposal and unfortunately am going to close this PR because I believe it doesn't add enough value for it to be part of the library. I also believe it stretches the meaning of filtering.
I would implement this same pattern using flatMap. It could look something like this:
authenticateUser(email: email, password: password).flatMap { val in
  if !allSitesResponded(val) {
    return Future(error: .SitesDownForMaintenance)
  }
  return Future(value: val)
}

I agree this doesn't look as nice as the one-liner you are using, but for that you could create your own extension on Future that lives in your project that calls flatMap.
Thanks for your time, I hope you understand!


Anyway to add csutom spaces/lines in HTML?

I had this open here https://github.com/victorporof/Sublime-HTMLPrettify/issues/665
I'm trying to figure out how to add some custom space/line after some divs but can't find any info.
For example:

Home

About

Blog

Support

Contact

After that nav, here I want to add some lines then a new div but on save it just moves up my elements. Can I add some custom space or lines with the "format_on_save": true,
If there are settings for this then could you point me out to them?

What do you want the output to look like when you're done?

@bitwiseman Sorry for the less info, I would like this to be formatted as output:

Home

About

Blog

Support

Contact

Then after the input if I would like to add more empty lines for another section then it just move them up. Trying to figure out how to have more custom spaces, eg: 👇
<!DOCTYPE html>

    <meta charset="UTF-8">
    <title>Document</title>

Home

About

Blog

Support

Contact

Lorem ipsum dolor sit amet, consectetur adipisicing elit.

Lorem ipsum dolor sit amet, consectetur adipisicing elit.

            Copyrights

I can add comments to separate the section but sometime need to add spaces and upon save it just remove them, like this:
<!DOCTYPE html>

    <meta charset="UTF-8">
    <title>Document</title>

Home

About

Blog

Support

Contact

Lorem ipsum dolor sit amet, consectetur adipisicing elit.

Lorem ipsum dolor sit amet, consectetur adipisicing elit.

            Copyrights

@Abd-Ur-Rehman
Several possible settings:

"preserve_newlines": true  - this should make it so the blank-lines you add are not removed.
"extra_liners": ['head', 'body', '/html'] - This adds a blank line before any specified element.  It isn't ideal, but it can get you closer.   For example, "extra_liners": ["head", "body", "/html", "/body", "nav", "section", "footer"] will get the following output:

<!DOCTYPE html>

    <meta charset="UTF-8">
    <title>Document</title>

Home

About

Blog

Support

Contact

Lorem ipsum dolor sit amet, consectetur adipisicing elit.

Lorem ipsum dolor sit amet, consectetur adipisicing elit.

            Copyrights

Thanks for the support, yeah the 2's example is working fine.  But the 1 still removes extra spaces. I have added them in HTML settings:
https://gist.github.com/Abd-Ur-Rehman/d65803d5c203bdf5c0c3c129e080f52a#file-jsbeautifyrc-L65
https://gist.github.com/Abd-Ur-Rehman/d65803d5c203bdf5c0c3c129e080f52a#file-jsbeautifyrc-L67

Was that supposed to be in the HTML?

@Abd-Ur-Rehman
Glad #2 works.  What you showed should work for #1.  Can you try this on https://beautifier.io ?  I suspect there is some other part of your IDE that is removing the newlines.

Hey, @bitwiseman thanks here it works but here I'm seeing that it has  "max_preserve_newlines": "3", I have added that to my settings and it works fine, doesn't remove any lines. Thanks again! 😊

Closing the issue as it's resolved with those settings. Thanks 👍

Sorry, @bitwiseman I'm trying to figure out how to add space between selectors in CSS I have my the input as below:
.the-checkbox:checked+p {
    background: red;
}

I want output like this:
.the-checkbox:checked + p {
    background: green;
}

It's removing the spaces how can I have them?
Thanks

@Abd-Ur-Rehman
Please look at the CSS issues for one that matches this or open a new issue and we can track this that way (it is a separate issue from this one).   As to where you can find more information, the readme should be up-to-date but it might need updates.

@bitwiseman Not quite sure if this is related. https://github.com/beautify-web/js-beautify/issues/1489

@Abd-Ur-Rehman I think this is the one: https://github.com/beautify-web/js-beautify/issues/676

@bitwiseman Yeah, that's happening with the descendant selector as well, I just had tested with the adjacent selector. Will be following that issue for a fix. Thanks


Fix examples + types

What:
Update docs to match dom-testing-library v2 api
Why:

How:

Checklist:

[ ] Documentation
[ ] Tests
[ ] Ready to be merged
[ ] Added myself to contributors table

@maddijoyce the typescript definitions are almost certainly wrong 😃

All looks good there now. As far as separating the types into their respective libraries, I'll put a PR through this week.

The inline type signatures for the wrapped methods don't have the new options yet, but maybe that can be a followup

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Build error with glibc >= 2.32

Problem description
Ubuntu 22.04+ ships with glibc 2.32 or newer. From the release notes at https://sourceware.org/pipermail/libc-announce/2020/000029.html:

The deprecated arrays sys_siglist, _sys_siglist, and sys_sigabbrev are no longer available to newly linked binaries, and their declarations have been removed from <string.h>.  They are exported solely as compatibility symbols to support old binaries.  All programs should use strsignal instead.

https://github.com/aws/amazon-redshift-odbc-driver/blob/main/src/pgclient/src/port/exec.c#L529
Changing that line to strsignal call corrects the build error. This probably needs to be wrapped in a different macro conditional based on glibc version.

Hi @rokclimb15
Thanks for the hint.
I will make this change and test with other platforms and if everything is ok, I will include it in the subsequent releases.


Training facilities

So far, deepnog only allow to perform inference using models trained by us, the developers, in separate Jupyter notebooks. This does not scale to a larger number of models for more levels of EggNOG, or even other orthology databases.
This PR introduces components that allow users to train custom models. The primary use case is taking the DeepNOG (=DeepEncoding) architecture, and train additional levels of EggNOG. Additionally, different architectures can be introduced, and trained, with reasonable effort.
At the heart of this PR is the new training.py that runs training and validation epochs. The Dataset and DataLoader classes now support labels, and a ShuffledDataset is introduced that still iterates over the FASTA file, but can shuffle the input data (s.t. a user-defined buffer size).
EDIT: An additional ProteinDataset class is introduced that features random access. This enables complete shuffling of sequences, ensuring that minibatches differ in epochs, which might affect training. This comes at the cost of first loading the complete fasta file and storing in memory. This might replace the ShuffledDataset.
The client now uses two subparsers: train and infer.
The general package structure was reworked to offer more intuitive modularity.
deepnog now uses a YAML configuration file, which includes the supported databases (for inference), architectures (for training) and possibly more.

Closes #18


Cannot receive udp data on iOS 10.1.1

Hi, I am using the example code posted on the README,
var listenPort = 11011;
var receiver = new UdpSocketReceiver();

receiver.MessageReceived += (sender, args) =>
{
    // get the remote endpoint details and convert the received data into a string
    var from = String.Format("{0}:{1}", args.RemoteAddress, args.RemotePort);
    var data = Encoding.UTF8.GetString(args.ByteData, 0, args.ByteData.Length);

    Debug.WriteLine("{0} - {1}", from, data);
};

// listen for udp traffic on listenPort
await receiver.StartListeningAsync(listenPort);

and I cannot receive data via iPhone on iOS 10.1.1, but it works with Android, did I do anything wrong?

Howdy,
Can you talk more about your setup? e.g. - are you using iOS device or simulator? what network is the device/simulator running on? what are you sending the udp packets from and what network is that device on? If another computer, is it inside a vm?

I am using iPhone 6s and iPhone 7, it is running on a router, basically computer <-> router <-> phones. Not using a VM, it works with Android phones, but not iOS.


Enable resource limits on pods

We have been running without setting resource limits, which can cause all sorts of problem. This patch simply enabled the default resource limits set by the charts.
There might be need for further tuning of limits.

I prefer not to enable resource limits initially and gather the utilization once we are in a LA phase and set these limit. The default limits are way too small, unusable, for larger production setups from what I can see and it would lead to constant pod terminations

Fair enough. I agree with you that the values can be better tweaked. Lets wait for GA to get some data.

Closing this for now. Will re-visit after LA with better understanding of usage.


Run bazel_to_cmake on Conversion/CodegenUtils dir

FYI, this was already fixed on the google branch, just waiting on merge back into main: https://github.com/google/iree/commit/765786f0ea9a2dafd9a092687ee5c6c7e8011cad, https://github.com/google/iree/commit/4c3b5bd221d32259af09b3a6738ad0b77870074e. Hopefully no merge conflicts now, but if so we can test resolving them more - conflicts in auto-generated files are easy to resolve.
Going forward, when there are fewer outstanding changes to the google branch, we should be able to look just at the main branch most of the time.

Yeah this is my bad for not finding a green commit on the google branch when merging back from it last time. I was doing a demo and didn't think about it.


Add the host to the Java API

It was added to the Scala API last week and still needs to be added to the Java API:
https://github.com/playframework/Play20/commit/c69f6a6477ada907ff937ee028a8279e9b3fb87d

this is now fixed. thank you

thanks!


Filling a form using JQuery fails validation

So I am in the process of attempting to use some simple code injection to populate a form and submit it, in most cases, I am able to have the textbox revalidate by firing the blur event, but in the case of a react form build on redux, it does not validate in the same manner.
I tried using the following code, but it does not work:
top.jQuery('input#last-name-\\[0\\]').val('Smith').attr('value','Smith').trigger('blur');
Is there an event that I should be firing instead of the input event?
The values are not detected as firing the click event on the submit fails validation, as though no data has been entered in the form.
I tried a number of triggers including keyup, keydown, keypress, focus, blur, and changed.
Please note that using default values are not an option, because I am injecting the form data into a website that is not my own.
This is the code that react is using to build the component:
function LastNameComponent(_ref) {
    var index = _ref.index,
        isFirstField = _ref.isFirstField,
        formatValue = _ref.formatValue;

    var minLength = 2;
    var maxLength = 80;
    return _react2.default.createElement(
        'div',
        { className: 'form--item span3' },
        _react2.default.createElement(
            'label',
            { className: 'search-label small field__icon_group' },
            _react2.default.createElement(
                'span',
                null,
                '*'
            ),
            'Last Name',
            _react2.default.createElement(_TextInput2.default, {
                id: "last-name-[" + index + "]",
                model: "searchParams.searches[" + index + "].fields.lastName",
                validators: { required: function required(value) {
                        return !value || value.length < minLength || value.length > maxLength;
                    } },
                formatValue: formatValue
            }),
            _react2.default.createElement(_ErrorMessage2.default, {
                model: "searchParams.searches[" + index + "].fields.lastName",
                messages: { required: "Please enter the member's Last Name" }
            })
        )
    );
}

In the past I was able to  use .trigger('blur') and .trigger('change') but neither work anymore.

Please make a reproducible code example. I never use jQuery so I wouldn't know where to begin with this one.

Here is a use case: https://codesandbox.io/s/VOxrnZPYX
As you can see, it is populated by the data, but it is never fired (ie) The event that should fire to revalidate does not because it does not detect the texboxes being filled.

@Bitz This is using Redux-Form, not React-Redux-Form. Please move this issue to that repo: https://github.com/erikras/redux-form/issues
Thanks!


fix: linux fix for #158

This should be passing on builds.

Closing yet another PR because of unsaved changes, hopefully my next PR after this will resolve issue.


make use of tables from ./output/scores for analysis notebooks?

https://github.com/Fudenberg-Research-Group/dynamic_extrusion_boundaries/blob/main/analysis/sweeps_map_frips.ipynb
seems to use file = pd.read_csv('inputs/data/fripscore_hres.csv'). Could this instead make use of one of the tables in ./output/scores?
Also, can directory='/project/fudenber_735/polychrom/Dynamic_boundary_model/1d_sims_dynamic_boundary/dynamical_boundary_simulations/sims/' #simulation directory be deleted, as well as everything before cell [60] as that is where manuscript-related content appears to begin? Then this notebook could be renamed to something that could align nicely with the paper.

I think previous cells are included in supplementary figures of manuscript.

thanks; resolved.


ARAM

The aram builds are from two patches ago, did you will update it? Thank's for your work

ARAM updates are from lolflavor. According to their pages they are up to date, double check with their site. Championify pulls directly from them, and you have to make sure you hit the import button yourself, it's not automatic yet. If there's anything else I'll reopen this issue.


Converting audio example?

Hi. Could You, please, provide come example how to convert audio file from one format to another (wav -> mp3) using Your library?

I wouldn't recommend using sox for this, usually it's not compiled with mp3 support for legal reasons. However, as I understand it you should be able to just name the output file with .mp3 as the file extension, and if you have a valid encoding defined, it should do the conversion. That is, if libsox is compiled with mp3 support.

Ok, I have compiled sox with mp3 support. How should I convert file?
OpenRead, OpenWrite and then? Read all samples from input to output sample by sample?
By the way Your example4 with conversion doesn't work.

@krig any hint on how to set the input and output format?


Guardian.Plug.sign_out() doesn't seems to revoke the token

In my application sign_out doesn't seems to revoke token get by Guardian.Plug.sign_in
Here is how I get a token :
Test.Guardian.Plug.sign_in(conn, user, %{claim: "access"}, ttl: {30, :days})
And here is how I revoke it:
Test.Guardian.Plug.sign_out(conn)
I can get the token (with Test.Guardian.Plug.current_token(conn) ) before the call to sign_out but also after the call to sign_out wich shouldn't happend no?

What is the value of Test.Guardian.Plug.current_token(conn) after sign_out ?

It's the token itself

I am seeing similar behaviour.  In my case I have the following call to sign in: App.Guardian.Plug.sign_in(user, key: :admin) and on sign out: App.Guardian.Plug.sign_out(key: :admin).  I spent some time looking into the data in the session and I noticed that upon sign in I have a guardian_default_token in my session (conn.private.plug_session).  Working through the sign out path the code is removing guardian_admin_token from the session.
It appears that sign_in isn't loading up the session with the same key that sign out expects.

When I correctly call App.Guardian.Plug.sign_in then keys in the session are as expected.  In my above example sign_in should have been called as follows: App.Guardian.Plug.sign_in(conn, user, %{}, key: :admin)

@loustak which conn are you passing down?
Could you please post the full test code so I can see what you are doing it.

@loustak which conn are you passing down?
I'm not really sure about what you mean there.
Link to my project.
I have also another question. I read somewhere that the jwt is stored in "connections". But I don't understand what are connections when speaking about Phoenix. Is this something in memory? My concern here is the scalabitility of this storage.
Thanks for help !

Where is the link to the test where you are trying to make it pass.

@loustak which conn are you passing down?
I'm not really sure about what you mean there.

I am trying to see how you are using the package and make sure that you are using the write connection.
Please do not merge one thing with the other one, keep it clean and better ask those questions on Slack channel where people could help you with it.

I have also another question. I read somewhere that the jwt is stored in "connections". But I don't understand what are connections when speaking about Phoenix. Is this something in memory? My concern here is the scalabitility of this storage.

JWT are stored on your cookie and/or your clients storage and send it every request on the header. JWT are stateless which means you don't store them on the server but your clients.

Feel free to open the issue if the problem persists.


RTP with threading+initial UI ashlar integration

(tentative pull request to show changes, needs testing before approval, do not merge yet)

The changes here have all been incorporated into master-with-realtime-and-cfg. Closing this PR


Issue: ESB Toolkit 2.1 Itinerary Designer Extension install fails when BizTalk not installed to C: drive

ESB Toolkit 2.1 Itinerary Designer Extension install fails when BizTalk not installed to C: drive.  Include a workaround for D: drive installation since that is the most likely alternate install path.
This work item was migrated from CodePlex
CodePlex work item ID: '9838'
Assigned to: 'tfabraham'
Vote count: '1'

[UnknownUser@5/8/2013]
Resolved with changeset 72803: Add workaround for ESB Toolkit 2.1 Itinerary Designer extension install when ESB Toolkit installed on D: (#9838)

[UnknownUser@5/16/2013]


Add design doc for new declare/script interface

Introduced changes

Opens up a discussion about sncast declare/script interfaces, first raised under this PR https://github.com/foundry-rs/starknet-foundry/pull/1093

Checklist

[X] Linked relevant issue
[X] Updated relevant documentation
[X] Added relevant tests
[X] Performed self-review of the code
[X] Added changes to CHANGELOG.md

I disagree with ditching the --package flag for declare and script, I think it should be required. A user should always explicitly specify a package to look for a script/contract in to avoid ambiguity. The only case when it could be omitted is for a workspace with a single member.

We do not support it now, so there's no ditching. At the moment we require users to pass a path to correct manifest. Not sure users should always specify the package, I don't think this is necessary to be honest. If we have only one contract called "whatever" in all the packages in all workspaces, why shouldn't we be able to just do sncast declare whatever? And if the contract name isn't unique across the packages, why shouldn't we only then require users to specify (eg using path I proposed in this doc)?

2. The approach with paths is impossible to implement with `sncast declare` (see the comment below). We should instead pass the name of the contract.

why?

We do not support it now, so there's no ditching

Mb, wrong assumption.

If we have only one contract called "whatever" in all the packages in all workspaces, why shouldn't we be able to just do sncast declare whatever

Okay, you convinced me. I think the --package flag should be optional

The approach with paths is impossible to implement with sncast declare (see the comment below). We should instead pass the name of the contract.

why?

Didn't understand your idea with paths for declare, I think it is confusing to have sth looking like a cairo path that may actually not be a valid cairo path :/ That's why I would rather have the optional --package flag

Not sure if compilation optimisations are that relevant for sncast, but the optional --package flag would make it easy to compile only what we need. If user passes it, it is obvious which package we should build with scarb build --package $PKG, in case --package is not passed we build for the entire workspace with scarb build --workspace. As I said though, it may be not that important for sncast

@Arcticae can you please skim it too see if there are any inconsistencies with snforge interface?

Another question what is the matching algorithm of the module path? IMO should be specified.


Dependencies not being de-duplicated and deployed multiple times

What happened?
We have some projects which have a lot of dependencies (25+ with transitive dependencies, usually one deployment per dependency), and the initial devspace deploy can take quite a bit of time (ie. a few minutes rather than less than a minute - which is what we had with our docker-compose setup). Once everything is running, devspace dev -x is working great!
Part of this increased spin-up time may be due to this: we seem to sometimes end up with the same dependencies being deployed multiple times... e.g as part of the mentioned dependency graph we have multiple services depending on the same postgres dependency (same git source/branch/vars etc.), but I still see the postgres helm chart being installed/upgraded multiple times in the logs:
❯ devspace update dependencies
[done] √ Pulled git@github.com:bforchhammer/devspace-dependency-example
[done] √ Pulled git@github.com:bforchhammer/devspace-dependency-example
[done] √ Pulled git@github.com:bforchhammer/devspace-dependency-example
[done] √ Successfully updated all dependencies
❯ kubectl delete ns test2
namespace "test2" deleted
❯ helm ls
NAME    NAMESPACE       REVISION        UPDATED STATUS  CHART   APP VERSION
❯ devspace deploy
[info]   Using namespace 'test2'
[info]   Using kube context 'docker-desktop'
[done] √ Created namespace: test2
[info]   Start resolving dependencies
[done] √ Resolved dependencies successfully

[info]   Execute 'helm upgrade postgres --namespace test2 --values /var/folders/xj/7sl84q_16fb61dqplqr193hm0000gp/T/955378123 --install /Users/benedikt.forchhammer/.devspace/component-chart/component-chart-0.8.4.tgz --kube-context docker-desktop'
[done] √ Deployed helm chart (Release revision: 1)
[done] √ Successfully deployed postgres with helm
[done] √ Deploy dependency app.app2.postgres completed
...
[info]   Execute 'helm upgrade postgres --namespace test2 --values /var/folders/xj/7sl84q_16fb61dqplqr193hm0000gp/T/3632472368 --install /Users/benedikt.forchhammer/.devspace/component-chart/component-chart-0.8.4.tgz --kube-context docker-desktop'
[done] √ Deployed helm chart (Release revision: 2)
[done] √ Successfully deployed postgres with helm
[done] √ Deploy dependency app.postgres completed
...
[done] √ Successfully deployed!

❯ helm ls
NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
app             test2           1               2022-01-06 10:36:30.995718 +0100 CET    deployed        component-chart-0.8.4
app2            test2           1               2022-01-06 10:36:27.193464 +0100 CET    deployed        component-chart-0.8.4
postgres        test2           2               2022-01-06 10:36:29.015276 +0100 CET    deployed        component-chart-0.8.4

What did you expect to happen instead?
I expect postgres to only be helm install-ed once, ie. the helm revision for the postgres release should be 1. (The output above is only a simple example, in our case some helm releases seem to be upgraded 10+ times).
How can we reproduce the bug? (as minimally and precisely as possible)
I created an example to reproduce the issue here: https://github.com/bforchhammer/devspace-dependency-example
The addition of the POSTGRES_USER variable to the postgres dependency seems to be what causes the issue (https://github.com/bforchhammer/devspace-dependency-example/commit/0fe3258c23e8a94d563acb74d59f8f26c1954c9c); without it the postgres helm release is only installed once!
Local Environment:

DevSpace Version: 5.18.1
Operating System: mac
ARCH of the OS: AMD64
Kubernetes Cluster:
Cloud Provider: docker-desktop
Kubernetes Version: v1.22.4

Anything else we need to know?
Happy to provide more info if needed :)

/kind bug

@bforchhammer thanks for creating this issue! Yes you are correct, DevSpace shouldn't deploy the postgres dependency twice. We'll fix that!

@FabianKramm Thanks for fixing this and the new release! It's improved the deploy time on some of our projects immensely! 💯


build: Treat .gnut files as .nut for syntax highlighting

Their syntax is functionally the same anyway
No testing needed as this only modifies .gitattributes which has nothing to do with the game.

Syntax highlighting works 🎉
https://github.com/R2Northstar/NorthstarMods/blob/efa942c1b224774c744eb8939579c41ef6f258ba/Northstar.Custom/mod/scripts/vscripts/sh_custom_air_accel.gnut

Omg totally yes because it always bugs me out why its not doing syntax highlighting with gnut files.


DEV:LOG:Not providing  will make UpdateInStore fail

Reported on 6/25 by SLB (refer to email entitled "Issues found in Drillflow V0.14 image"):
Log, not providing  will make UpdateInStore fail.

Error returned from DrillFlow is "JSONObject["name"] not found."

Noted as not solved  by SLB – active in current sprint
ETA TBD pending @TessForGithub2  RTC support bandwidth

Dev analysis in progress - ETA is 7/10

Dev analysis complete; Code change in progress @TessForGithub2  will update card ETA - 7/22

UPDATE: Need to recall code change & proceed.


Added pylint for model and visualizationGenerator and changed other n…

…ecessary files
Background

Updated util files: model.py and VisualizationGenerator.py to satisfy 10/10 linting
Modified other files to work with changes made due to changes for satisfying pylint

Also pushed some virtual environment changes


Response with both an empty result list and a NextToken when using filters

What issue did you see ?
I am getting both an empty result list  AND a NextToken when calling boto3.client("ssm").list_command_invocations with a specific set of filters.
What does this response mean? Can I safely stop querying the API when I receive the first empty response list, or do I have to keep querying until there's no NextToken in the response? The former approach takes 0.5s, while the latter takes around 15s -- so not a trivial difference. In both cases the end result is still an empty list.
It is my understanding that the Filters argument applies the filters server-side. If I have to keep querying until there's no NextToken, however, I could've just as well performed the filtering client-side.
Steps to reproduce
import boto3

if __name__ == "__main__":
    ssm = boto3.client("ssm")
    response = ssm.list_command_invocations(
        Filters=[{"key": "Status", "value": "InProgress"}]
    )
    command_invocations = response["CommandInvocations"]
    while response.get("NextToken", ""):
        response = ssm.list_command_invocations(
            Filters=[{"key": "Status", "value": "InProgress"}],
            NextToken=response["NextToken"],
        )
        command_invocations += response["CommandInvocations"]

Closed in favor of https://github.com/boto/boto3/issues/2643


Error for custom script in Octoprint

Hi,
I use some custom scripts to set the brighness of the camera, without having to open the CLI.

Thsese work fine in Octoprint itself, and somewhere in the past (I don't use them very often, they also worked through the OctoPod app, but now they don't anymore

The commands run a .sh script in the Pi home-folder.
The "Start video stream" and "Stop video stream" commands also run a .sh scripts in the Pi home-folder, and strangely enough, they do work.

This is interesting @TheLion. There are no recent changes made to system commands so not sure why it stopped working. Have you recently changed something else like updating OctoPrint?
BTW, if you can share your setup (e.g. config.yaml or how to add those system commands) I can try reproducing it and see what is going on.
Thanks,
Gaston

This is interesting @TheLion. There are no recent changes made to system commands so not sure why it stopped working. Have you recently changed something else like updating OctoPrint?

I did update OctoPrint to v1.40 a couple of weeks after it was released, but I'm not sure if that was the moment it stopped working.

BTW, if you can share your setup (e.g. config.yaml or how to add those system commands) I can try reproducing it and see what is going on.

I will share the part of config.yaml tomorrow,so hopefully you can reproduce it.

Thanks @TheLion. Once you shared the info I will see of reproducing this issue.

The relevant part of the config is:
system:
    actions:
    -   action: streamon
        command: /home/pi/scripts/webcam start
        confirm: false
        name: Start video stream
    -   action: streamoff
        command: sudo /home/pi/scripts/webcam stop
        confirm: false
        name: Stop video stream
    -   action: setwebcam default
        command: sudo /home/pi/setwebcam.sh
        confirm: false
        name: Set Webcam Default
    -   action: setwebcam Exposure 800
        command: sudo /home/pi/setwebcam800.sh
        confirm: false
        name: Set Webcam Exposure 800
    -   action: setwebcam Exposure 400
        command: sudo /home/pi/setwebcam400.sh
        confirm: false
        name: Set Webcam Exposure 400
    -   action: setwebcam Exposure 200
        command: sudo /home/pi/setwebcam200.sh
        confirm: false
        name: Set Webcam Exposure 200

the .sh files contain, or something similar:
v4l2-ctl --set-ctrl=focus_auto=0 --verbose
v4l2-ctl --set-ctrl=focus_absolute=50 --verbose
v4l2-ctl --set-ctrl=exposure_auto=1 --verbose
v4l2-ctl --set-ctrl=exposure_auto_priority=0 --verbose
v4l2-ctl --set-ctrl=exposure_absolute=400 --verbose
v4l2-ctl --set-ctrl=sharpness=200 --verbose
v4l2-ctl --set-ctrl=white_balance_temperature_auto=0 --verbose
v4l2-ctl --set-ctrl=white_balance_temperature=6000 --verbose

If you need any more info, let me know.

I think this is enough for me to try reproducing this. Could you do one more thing? Could you go to OctoPrint -> Settings -> Logging and set tornado.access to INFO? This will log HTTP traffic to octoprint.log. You are going to see things like

2020-04-24 23:09:42,220 - tornado.access - INFO - 204 POST /api/system/commands/core/restart (2601:1c0:4600:1b3:a4d7:1f10:6498:5956) 54.18ms
2020-04-24 23:09:42,228 - tornado.access - INFO - 200 POST /api/system/commands/core/restart (2601:1c0:4600:1b3:a4d7:1f10:6498:5956) 61.93ms

Once you configured this, could you run the system command from OctoPod and then look at octoprint.log and paste here the entries that were logged? I expect OctoPrint to not be returning 200 but some other error code.
Thanks,
Gaston

Sure, no problem.
I run the scripts 3 times, once from Octoprint web interface from my Windows computer (192.168.xxx.1), once from OctoPod app on my iPhone outside the network (<IP_ADDRESS>) and once from OctoPod on my iPhone inside the network (192.168.xxx.207). External and interal didn't make a difference though. But the requests from the OctoPod app didn't even appear to come through.
From Octoprint webgui
2020-04-25 11:31:16,457 - tornado.access - INFO - 200 PUT /plugin/logging/setup/levels (::ffff:<IP_ADDRESS>) 18.42ms 2020-04-25 11:31:16,458 - tornado.access - INFO - 200 PUT /plugin/logging/setup/levels (::ffff:<IP_ADDRESS>) 19.69ms 2020-04-25 11:31:17,936 - tornado.access - INFO - 200 POST /api/settings (::ffff:<IP_ADDRESS>) 1474.15ms 2020-04-25 11:31:17,938 - tornado.access - INFO - 200 POST /api/settings (::ffff:<IP_ADDRESS>) 1475.49ms 2020-04-25 11:31:17,999 - tornado.access - INFO - 200 GET /api/system/commands (::ffff:<IP_ADDRESS>) 10.94ms 2020-04-25 11:31:18,207 - tornado.access - INFO - 200 GET /api/settings (::ffff:<IP_ADDRESS>) 205.33ms 2020-04-25 11:31:18,254 - tornado.access - INFO - 200 GET /api/connection (::ffff:<IP_ADDRESS>) 43.53ms 2020-04-25 11:31:18,264 - tornado.access - INFO - 200 GET /api/printer/command/custom (::ffff:<IP_ADDRESS>) 8.22ms 2020-04-25 11:31:18,275 - tornado.access - INFO - 200 GET /api/slicing (::ffff:<IP_ADDRESS>) 7.81ms 2020-04-25 11:31:18,285 - tornado.access - INFO - 200 GET /api/printer/command/custom (::ffff:<IP_ADDRESS>) 8.18ms 2020-04-25 11:31:44,013 - octoprint.server.api.system - INFO - Performing command for custom:setwebcam Exposure 800 2020-04-25 11:31:44,240 - tornado.access - INFO - 204 POST /api/system/commands/custom/setwebcam%20Exposure%20800 (::ffff:<IP_ADDRESS>) 246.25ms 2020-04-25 11:31:44,242 - tornado.access - INFO - 200 POST /api/system/commands/custom/setwebcam%20Exposure%20800 (::ffff:<IP_ADDRESS>) 248.35ms
From outside the network:
2020-04-25 11:34:01,571 - tornado.access - INFO - 200 GET /api/job (::ffff:<IP_ADDRESS>) 27.36ms 2020-04-25 11:34:01,603 - tornado.access - WARNING - 409 GET /api/printer?exclude=sd,history (::ffff:<IP_ADDRESS>) 11.54ms 2020-04-25 11:34:14,512 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:<IP_ADDRESS> 2020-04-25 11:35:01,568 - tornado.access - INFO - 200 GET /api/job (::ffff:<IP_ADDRESS>) 19.64ms 2020-04-25 11:35:01,601 - tornado.access - WARNING - 409 GET /api/printer?exclude=sd,history (::ffff:<IP_ADDRESS>) 9.31ms 2020-04-25 11:35:04,673 - tornado.access - INFO - 101 GET /sockjs/websocket (::ffff:<IP_ADDRESS>) 3.74ms 2020-04-25 11:35:04,678 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:<IP_ADDRESS> 2020-04-25 11:35:04,937 - tornado.access - INFO - 200 GET /api/version (::ffff:<IP_ADDRESS>) 5.37ms 2020-04-25 11:35:04,983 - tornado.access - INFO - 200 GET /api/connection (::ffff:<IP_ADDRESS>) 43.85ms 2020-04-25 11:35:04,991 - tornado.access - WARNING - 409 GET /api/printer (::ffff:<IP_ADDRESS>) 5.26ms 2020-04-25 11:35:05,102 - tornado.access - INFO - 304 GET /api/settings (::ffff:<IP_ADDRESS>) 108.48ms 2020-04-25 11:35:05,127 - tornado.access - INFO - 304 GET /api/printerprofiles (::ffff:<IP_ADDRESS>) 20.45ms 2020-04-25 11:35:05,135 - octoprint.server.util.flask - INFO - Passively logging in user _api from ::ffff:<IP_ADDRESS> 2020-04-25 11:35:05,137 - octoprint.access.users - INFO - Logged in user: _api 2020-04-25 11:35:05,149 - tornado.access - INFO - 200 POST /api/login (::ffff:<IP_ADDRESS>) 44.69ms 2020-04-25 11:35:05,150 - tornado.access - INFO - 200 POST /api/login (::ffff:<IP_ADDRESS>) 45.65ms 2020-04-25 11:35:05,154 - octoprint.server.util.sockjs - INFO - User _api logged in on the socket from client ::ffff:<IP_ADDRESS> 2020-04-25 11:35:11,840 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:<IP_ADDRESS>
From inside the network
`
2020-04-25 11:36:40,870 - octoprint.server.util.flask - INFO - Passively logging in user _api from ::ffff:<IP_ADDRESS>
2020-04-25 11:36:40,873 - octoprint.access.users - INFO - Logged in user: _api
2020-04-25 11:36:40,878 - tornado.access - INFO - 200 POST /api/login (::ffff:<IP_ADDRESS>) 526.85ms
2020-04-25 11:36:40,879 - tornado.access - INFO - 200 POST /api/login (::ffff:<IP_ADDRESS>) 527.78ms
2020-04-25 11:36:40,884 - octoprint.server.util.sockjs - INFO - User _api logged in on the socket from client ::ffff:<IP_ADDRESS>
2020-04-25 11:36:42,327 - tornado.access - INFO - 200 GET /api/system/commands (::ffff:<IP_ADDRESS>) 25.93ms
2020-04-25 11:36:42,562 - tornado.access - INFO - 200 GET /api/settings (::ffff:<IP_ADDRESS>) 229.90ms
2020-04-25 11:36:42,610 - tornado.access - INFO - 200 GET /api/connection (::ffff:<IP_ADDRESS>) 45.70ms
2020-04-25 11:36:42,621 - tornado.access - INFO - 200 GET /api/slicing (::ffff:<IP_ADDRESS>) 8.26ms
2020-04-25 11:36:42,666 - tornado.access - INFO - 200 GET /api/connection (::ffff:<IP_ADDRESS>) 42.79ms
2020-04-25 11:36:42,872 - tornado.access - INFO - 200 GET /api/settings (::ffff:<IP_ADDRESS>) 203.86ms
2020-04-25 11:36:42,885 - tornado.access - INFO - 200 GET /api/printer/command/custom (::ffff:<IP_ADDRESS>) 7.63ms
2020-04-25 11:36:42,896 - tornado.access - INFO - 200 GET /api/printer/command/custom (::ffff:<IP_ADDRESS>) 8.32ms
2020-04-25 11:36:42,920 - tornado.access - INFO - 304 GET /api/printerprofiles (::ffff:<IP_ADDRESS>) 21.24ms
2020-04-25 11:36:42,937 - tornado.access - INFO - 200 POST /api/plugin/cancelobject (::ffff:<IP_ADDRESS>) 61.93ms
2020-04-25 11:36:42,937 - tornado.access - INFO - 200 POST /api/plugin/cancelobject (::ffff:<IP_ADDRESS>) 62.51ms
2020-04-25 11:36:42,970 - tornado.access - INFO - 204 POST /api/plugin/domoticz (::ffff:<IP_ADDRESS>) 47.85ms
2020-04-25 11:36:42,971 - tornado.access - INFO - 200 POST /api/plugin/domoticz (::ffff:<IP_ADDRESS>) 48.71ms
2020-04-25 11:36:42,993 - octoprint.plugins.logging - INFO - Setting logger tornado.access level to 20
2020-04-25 11:36:43,000 - tornado.access - INFO - 200 PUT /plugin/logging/setup/levels (::ffff:<IP_ADDRESS>) 15.84ms
2020-04-25 11:36:43,001 - tornado.access - INFO - 200 PUT /plugin/logging/setup/levels (::ffff:<IP_ADDRESS>) 16.88ms
2020-04-25 11:36:43,220 - tornado.access - INFO - 200 POST /api/settings (::ffff:<IP_ADDRESS>) 208.60ms
2020-04-25 11:36:43,221 - tornado.access - INFO - 200 POST /api/settings (::ffff:<IP_ADDRESS>) 209.24ms
2020-04-25 11:36:43,389 - tornado.access - INFO - 200 GET /api/printer/command/custom (::ffff:<IP_ADDRESS>) 7.99ms
2020-04-25 11:36:43,925 - tornado.access - INFO - 200 GET /api/system/commands (::ffff:<IP_ADDRESS>) 22.23ms
2020-04-25 11:36:44,301 - octoprint.plugins.excluderegion - INFO - Setting update detected: g90InfluencesExtruder=False, clearRegionsAfterPrintFinishes=False, mayShrinkRegionsWhilePrinting=False, loggingMode=octoprint, enteringExcludedRegionGcode=None, exitingExcludedRegionGcode=None, extendedExcludeGcodes={'G4': {"gcode": "G4", "type": "ExcludedGcode", "mode": "exclude", "description": "Ignore all dwell commands in an excluded area to reduce delays while excluding"}, 'M205': {"gcode": "M205", "type": "ExcludedGcode", "mode": "merge", "description": "Record advanced setting changes while excluding and apply the most recent values in a single command after exiting the excluded area"}, 'M204': {"gcode": "M204", "type": "ExcludedGcode", "mode": "merge", "description": "Record default acceleration changes while excluding and apply the most recent values in a single command after exiting the excluded area"}}, atCommandActions={'ExcludeRegion': [{"action": "enable_exclusion", "type": "AtCommandAction", "command": "ExcludeRegion", "parameterPattern": "^\s*(enable|on)(\s|$)", "description": "Default action to enable exclusion"}, {"action": "disable_exclusion", "type": "AtCommandAction", "command": "ExcludeRegion", "parameterPattern": "^\s*(disable|off)(\s|$)", "description": "Default action to disable exclusion"}]}
2020-04-25 11:36:51,899 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:<IP_ADDRESS>
`
Is this the info you need? Is it the right information? If not, let me know..

Thanks @TheLion. I think that with the info you share I know what is going on. Notice that the commands that fail have an empty space in the action property. To confirm this I just created this command

-  action: dis o bay
   command: sudo disobay
   name: Command With Spaces

and got this error

POST not possible. Invalid URL found. Server: http://<IP_ADDRESS>:5000. Service: /api/system/commands/custom/dis o bay

When you run the command from the web UI, the browser is escaping those characters. I will do the same now. In the meantime, replace space with _ like this

-  action: dis_o_bay
   command: sudo disobay
   name: Command With Spaces

Thanks for helping find the root cause.
Gaston


Installing on Raspberry Pi

I just installed Juliaup no problem on a raspberry pi 4. After doing that, I ran ~ pi $source .bashrc  to update the path, as reccomended. However, on attempting to launch julia, I got the following error.
~ pi $julia
Error: The Julia launcher failed to start Julia.

Caused by:
    No such file or directory (os error 2)

But prebuildt binaries exist at https://julialang.org/downloads/. Would it be possible to install such a suitable prebuild binary from juliaup, also on a raspberry pi?

Accidental duplicate of https://github.com/JuliaLang/juliaup/issues/603


Resolution don't change on setting page

mm: develop git version
google Chrome: 78.0.3904.108 (Hivatalos verzió) (64 bites) linux

It happens only if you have multiple webcams.

Fixed in new client


[DOCFIX] Clarify steps to configure Alluxio on k8s

I added a section to point users towards the configuration steps for Alluxio workers. Without configuring/disabling Alluxio worker short-circuit access, the Worker Pods will never start.

Can one of the admins verify this patch?

@jiacheliu3 PTAL, thanks!

alluxio-bot, merge this please.

alluxio-bot, cherry-pick this to branch-2.5 please.

alluxio-bot, cherry-pick this to branch-2.5 please


Allow kwargs through fit

Allows same arguments constructors take to be passed through fit.

Codecov Report

Merging #164 into master will increase coverage by 0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #164      +/-   ##
==========================================
+ Coverage    90.1%   90.17%   +0.06%
==========================================
  Files          13       13
  Lines        1324     1323       -1
==========================================
  Hits         1193     1193
+ Misses        131      130       -1

Impacted Files
Coverage Δ

src/pls.jl
94.54% <100%> (ø)
:arrow_up:

src/PIRLS.jl
92.48% <100%> (+0.53%)
:arrow_up:

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 50d7646...0d0edd3. Read the comment docs.

Sorry, I didn't see #164 and #165 until today.


Any possibility for network engine abstraction

In our app we use Firebase, we would love to abstract this to the point where we can use alamofire or firebase without the caller knowing anything.
As it is we will have to either have an abstraction of an abstraction or have the code know it's calling Moya or non-moya code.

Hmm, this is an interesting question. There's no reason we can't/shouldn't do this, it's just never been a priority before, so it's definitely worth considering. I'm thinking we abstract the functions we call from Alamofire into protocols, and extend Alamofire types to conform to those protocols. Then we just need a way to specify a different set of types that also conform.
There's a bit of hassle where we're currently using typealias to create Moya-specific types from Alamofire ones (for things like request methods, GET, POST, etc) that would need a little bit more code, but nothing too dramatic.
I've got a flight tomorrow, might take a stab at this on the plane. In the meantime, you could explore subclassing Moya's Provider class to give you similar behaviour. Please let us know if you have ideas for implementation, too.

My fork has done this.

I forgot about that, thanks!

I took an initial stab at this, it's quite an overwhelming change. We actually lean on Alamofire a lot, include use of typealias to create Moya types that are really just Alamofire types. If we do this, I would want someone to be able to theoretically use Moya without having any reference to Alamofire code at all.
@jasl how up-to-date is your fork? Moya has added multipart form uploading and a few other large structural changes recently, would it work with those changes?

@ashfurrow I sync all commits to https://github.com/jasl/Moya and it's a fork of Moya.
I'm afraid my fork has large different with current Moya, because I've done myself version multipart-upload, new Swift 3 naming convention, refactor example, non-generic provider etc  before

Okay, thanks for the quick response!
I tried to tackle this from top-down, like replacing our references to Alamofire.Manager with a new protocol defined in Moya, but everything broke immediately, and I was no where near finished an hour later. I think a better approach would be to remove the typealiass in Moya+Alamofire.swift first, then replace use of Manager with a new protocol. I'll see what I can do later.

In my fork, I wrap network engine into Backend which handle initiallizing and configuring the engine, and it's has a request method, that accept Moya's Endpoint value.
In request method, the backend should handle how to make a Endpoint become to request and launch it, then invoking response closure when get response, Moya don't care about how to encode the parameter or how to make endpoint to request, these job is NSURLSession's or Alamofire's, Moya just provides a easy way to encapsulation the remote API definition, and give a easy way to intercept the upcoming Endpoint. I think this is the core value of a networking abstraction.

and I think using typealias isn't a good way to abstract engines, because engines interface are different, and may need to configure, so we need to wrap them.

I don't think there's enough common ground to abstract AlamoFire (one request -> one response pattern) and Firebase (one subscription -> 0..N events in a stream), at least not on Moya's level.
Moving the abstraction up a layer works nice though: RxSwift works great for mapping both variants into streams.

@vzsg yeah currently thats what we are doing.

I tried abstracting Alamofire and found Moya to be too tightly coupled to it to reasonably separate. This is probably because we've always built Moya on top of Alamofire, the de facto standard networking library on iOS. This is a reasonable hard dependency from my perspective, but as always, it's open for discussion. If anyone would like to send a pull request with this specific feature, I'd be happy to look it over :+1: In the mean time, we can keep this issue open in case others have ideas or suggestions.

Since there hasn't been any activity on this thread for some time, I am going to go ahead and close it. Please re-open or create a new issue if you would like to discuss further. Thanks.

I understand this is an old and closed thread but I recently started working on a project for Firebase inspired by Moya. I've called it Nora. I'm really a huge fan of the Moya networking abstraction pattern. I initially tried seeing if Moya could support Firebase but like others in this thread have mentioned, Moya is too tightly coupled with Alamofire and it would require a different Provider and Target types. Thank you everyone for your hard work on this project and the inspiration.

Thanks for the kind words, @SD10, and good luck with Nora. :)


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/110305

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/110555

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/110937


Updated list of native smart contracts addresses

Description
Modified the list of native smart contracts addresses used for EVM callbacks. Now it is created starting from the list of message processors.
Jira Ticket
SDK-1349
Changes
Added getNativeSmartContractAddressList method to BaseAccountStateView trait
Modified EvmMessageProcessor so nativeContractAddresses is initialized calling getNativeSmartContractAddressList on BaseAccountStateView object
Breaking Changes
Checks

[X ] Project Builds
[ X] Project passes tests and checks
[ ] Updated documentation accordingly
[ ] Breaking changes have been correctly tagged and notified

Additional information

Merged in st/SDK_1351 branch.


reflect-metadata dependency

This library states in the README that it requires reflect-metadata. The consumer has to install this package manually. Why is this dependency not in the dependency list of package.json so that it is automatically installed along with sequelize-typescript?

Hey @MatthiasKunnen, this is to prevent that multiple reflect-metadata packages get installed. Why? Each reflect-metadata installation has its own metadata storage, from which it reads and writes from.
So if you had a project with multiple reflect-metadata packages, it could happen that in one file you write metadata in one reflect-metadata package and  in another file you’re trying to retrieve this metadata accidently from the other reflect-metadata package, which of course doesn’t exist there.
The only way is to list reflect-metadata in peerDependencies, but you would need to install it manually anyway.


fix liquid argon

Hmm it looks like jobs just aren't spawning in general @staticfloat ?

Oh sorry, there's just no indicator but I see it on the BK site.


[fixed] Don't steal focus from a descendent when rendering

Fixes #220.
Changes proposed:

Before focusing on the content div, check to see that the currently focused element isn't a descendent of the content div, to respect any focusing the application may have already done.

Acceptance Checklist:

[x] All commits have been squashed to one.
[x] The commit message follows the guidelines in CONTRIBUTING.md.
[x] Documentation (README.md) and examples have been updated as needed.
[x] If this is a code change, a spec testing the functionality has been added.
[x] If the commit message has [changed] or [removed], there is an upgrade path above.

I'm confused by this.  The modal contents, before being opened doesn't exist in the DOM, so nothing inside it should be able to be focused prior to the modal opening.
If you need to set focus to something after the modal has opened, you can you use the onAfterOpen function prop to set focus to something other than the content div immediately after opening.

React life cycle events and ref callbacks are called on children before they are called on parents. When componentDidUpdate is called on ModalPortal, it's already been called on all of it's descendants, so there plenty of opportunity for a child to have already given focus to some element in the modal. Right now though, that focus is being reassigned to the content div immediately afterward.
You could set focus in the onAfterOpen hook, but that would require you to traverse down from the component that opened the modal, coupling all of the components you pass through (especially problematic if your focusable element is deeply nested). Devs also already manage focus with componentDidMount/Update and ref callbacks. It seems strange that they'd need to implement a second set of focus logic to account for their component appearing in a modal.

Good points.  I don't see any reason that we shouldn't implement this.


Refactoring: Make code more robust and more portable

The code could be improved to be more consistent and more portable (mostly ChatGPT 4 recommendations):

Unify the use of echo vs. printf.
Quote Variables: Always quote your variables to handle spaces and special characters correctly. For instance, use "$PWD" instead of $PWD etc.
Consistent if Statement Syntax: For portability and readability, use a consistent style for if statements. For example, instead of [[ "$CURRENT_DIR" = "$CDFPATH" || "$CURRENT_DIR" == "$CDFPATH"/* ]], use [ "$CURRENT_DIR" = "$CDFPATH" ] || [ "$CURRENT_DIR" = "$CDFPATH"/* ].
Avoid Using [[ for Portability: The [[ syntax is not POSIX-compliant and might not work in shells other than Bash and Zsh. Use [ or test for portability.
Handle realpath and ln Commands for Portability: The realpath and ln commands might not be available or behave differently on some systems. You can write a function to manually resolve real paths or use readlink as an alternative. Similarly, for ln, check if the command exists and handle errors.
Handle cd Command Failure: The cd command can fail (e.g., due to permission issues). Always check its exit status to ensure the subsequent commands operate in the correct directory.
Avoid Using find for Autocomplete: The find command in _cdf_autocomplete may not be efficient or necessary. Consider using a simpler approach, like a for loop over the contents of $CDFPATH.
Sanitize Input: Ensure that input (like shortcut names) is sanitized to prevent potential command injection or other security issues or conflicts. Maybe simply restrict the format of the shortcut name via regexes.
Check for Command Existence: Before using commands like find, realpath, or ln, check if they exist on the system for better portability.
Test with zsh and other Non-Bash shells.

Unify the use of echo vs. printf.

done, except for tests where it's not worth the effort.

Quote Variables: Always quote your variables to handle spaces and special characters correctly. For instance, use "$PWD" instead of $PWD etc.

done, except maybe for tests

Handle realpath and ln Commands for Portability: The realpath and ln commands might not be available or behave differently on some systems. You can write a function to manually resolve real paths or use readlink as an alternative. Similarly, for ln, check if the command exists and handle errors.

done in the form of a test at install time and run time. Likely available on most modern systems.

Handle cd Command Failure: The cd command can fail (e.g., due to permission issues). Always check its exit status to ensure the subsequent commands operate in the correct directory.

done, same for ln in addfav

Sanitize Input: Ensure that input (like shortcut names) is sanitized to prevent potential command injection or other security issues or conflicts. Maybe simply restrict the format of the shortcut name via regexes.

done for the shortcut name in both cdf and addfav

Check for Command Existence: Before using commands like find, realpath, or ln, check if they exist on the system for better portability.

done, see No. 5, except for find (which may be replaceable by a loop or similar)

TODO:

Consistent if Statement Syntax: For portability and readability, use a consistent style for if statements. For example, instead of [[ "$CURRENT_DIR" = "$CDFPATH" || "$CURRENT_DIR" == "$CDFPATH"/* ]], use [ "$CURRENT_DIR" = "$CDFPATH" ] || [ "$CURRENT_DIR" = "$CDFPATH"/* ].
Avoid Using [[ for Portability: The [[ syntax is not POSIX-compliant and might not work in shells other than Bash and Zsh. Use [ or test for portability.
Avoid Using find for Autocomplete: The find command in _cdf_autocomplete may not be efficient or necessary. Consider using a simpler approach, like a for loop over the contents of $CDFPATH.
Test with zsh and other Non-Bash shells.

The check for find is now also implemented.

Completed with v0.4


⚠ Spryr has degraded performance

In 43fe08a, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4328 ms

Resolved: Spryr performance has improved in 207838c after 11 minutes.


Initial commit: Set up GitHub Pages with a basic layout and essential…

First commit:
Establish the foundation for our GitHub Pages, including the creation of a responsive and user-friendly website. This commit introduces the initial HTML structure, CSS styling, and essential files to kickstart our project. The GitHub Pages repository is now ready for further development and customization.

How to add content?


Feat update terminology doc template code

this commit includes changes on doc, templates, and Autoscale code; excludes changes on FOS CLI commands that aren't currently available on AWS marketplace yet.

I additionally found "master-election-no-wait" as not having been changed. I believe this one will be changed as a later date as it is not currently visible to the end user.

it is invisible to the end users but I have to change it as well.


[DEVOPS-1037] Enable new data layer for wallet in nix scripts

Description
Changes the default wallet data layer to the new one by adding new-wallet flag when running cardano-node.
Linked issue
https://iohk.myjetbrains.com/youtrack/issue/DEVOPS-1037
Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub.

Testing checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

QA Steps

Screenshots (if available)

This is moot now, as we just merged https://github.com/input-output-hk/cardano-sl/pull/3562

@adinapoli-iohk this has been updated to use legacy-wallet flag. This will be required for exchanges that haven't upgraded from v0 API.


Bring back the integration test permutations.

My more exotic attempt at #78 doesn't work since Linux seems to never actually gives back the released memory. This method of pooling the Contexts will have to do. I don't really like the fact that the integration tests could interfere with each other now (if there are any bugs in Z3) but I suppose it will have to do.


adds RunModeManager class and migrates code from cantroller2 to use it

currently fails the following two tests:
8. push ch3 to panic stop, should drop to shutdown mode but the mode color is light pink.
9. quickly turn speed to 0 before it times out, should make pink turn dark pink or red (still shutdown mode.
color is staying dark red

Merged in Soren’s PR


Add validation annotations to CleanupConfig

Add Jakarta Bean Validation annotations to the CleanupConfig class to permit validation, for example if an application uses external configuration to specify the configuration to use when cleaning up application errors.
This does not require adding a new dependency, since this library already depends (transitively) on jakarta.validation:jakarta.validation-api. However, it does now make it an explicit dependency, so we should probably make it explicit in the POM.

Since we're using Dropwizard's Duration class (io.dropwizard.util.Duration) in this configuration class, it makes sense to not only use standard validation Jakarta Bean Validation annotations like @NotNull but also to use Dropwizard's own custom validation annotations, in this case to use @MinDuration on the Duration fields. Since we mainly want to ensure that the duration isn't zero (or even negative), we can make the minimum as 1 minute for the fields. That probably isn't very useful in real life for most applications, but it ensures there is at least a valid minimum. I don't think we should set any maximum durations, since maybe someone wants to save them for 1 year, 2 years, etc. or even effectively forever by using a very large number of days.


System.InvalidCastException: Unable to cast object of type 'System.Windows.Documents.Run' to type 'System.Windows.FrameworkElement'.

Microsoft PowerToys version
0.41.3
Running as admin

[X] Yes

Area(s) with issue?
General, ColorPicker, FancyZones, FancyZones Editor, Image Resizer, Keyboard Manager, MD Preview, PowerRename, PowerToys Run, Shortcut Guide, SVG Preview, SVG Thumbnail, Settings, Welcome / PowerToys Tour window, System tray interaction, Installer
Steps to reproduce
System.InvalidCastException: Unable to cast object of type 'System.Windows.Documents.Run' to type 'System.Windows.FrameworkElement'.
✔ Expected Behavior
Open the "Photoshop" app.
❌ Actual Behavior
Bug reporting popup window
Other Software
Adobe Photoshop CC 2018

Here's the log file.
Log_2021-06-30.txt
runner-log_2021-06-30.txt

Looks for me like #11898

we're have a fix checked in are tracking in #11898 and hope to have a fix out shortly.


Add Information Ratio to tearsheet (the type from Fundamental Law of Active Management)

described here:
http://www.barra.com/newsletter/nl163/SevIns3NL163.asp

Nice one. How are "independent bets per year" computed? Just number of trades?

I think it's definitely tough to infer # of independent bets without knowing underlying algo logic, but I'm thinking something along the lines of the using the roundtrip analysis you've done which, if I recall, infers # of trades per month from parsing the buy/sell transactions.  We could then just multiply # of trades per month by 12 to get an approximation of 'independent bets per year.'

Implemented in the round trip tear sheet.


tox.ini: Test py35 and py36

$ tox
...
  py35-syntax: commands succeeded
  py36-syntax: commands succeeded
  py35-unit: commands succeeded
  py36-unit: commands succeeded
  congratulations :)

Can one of the admins verify this patch?

@msabramo thanks for the pr. We only support py35 officially now, and other python versions are just best effort. Feel free to add this locally, but until we support python36 we're not going to add this.

OK, no problem.


Make column selection code completion context sensitive

Describe the feature
Right now, when you are selecting from a model or CTE, all column names in the entire project appear in the dropdown. It would be great to limit them to only the columns available from the model or CTE.
Describe alternatives you've considered
I start typing immediately after a select. A dropdown appears but it lists every single column in the project. It should be narrowed to just what columns would be available at this point in the query. This could be done with dbt metadata.
Who will benefit?
All users will benefit as they will be able to select columns much more quickly, by only seeing the columns that are available to them at the point of the query.
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Duplicate of https://github.com/AltimateAI/vscode-dbt-power-user/issues/79


"Băbiciu" is listed in the drop-down menu

Description:
When user writes "Băbiciu" the location appears in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Băbiciu"
Expected results
The location appears in the drop-down menu as "Comuna Băbiciu, OLT"

@Elena1303996 please retest


example memory leak

all examples print Memory leaks detected at the end
./bio run examples/hello.lisp
How many times to print Hello?
1
Hello
Memory leaks detected

Interesting, I'm not getting this on macOS, latest Zig trunk. What Zig version/commit are you at?
Either way, I likely won't fix this as I've recently integrated BoehmGC as the root allocator. This will be pushed fairly soon.

zig version 0.11.0-dev.4183+32a175740

Pushed initial Boehm GC integration. Let me know if you're able to compile and run the examples.

works


Update using-template-engines.md

Added about template cache

LGTM

Sorry for the delay.  I've been out on vacation.


Blog design and styling

Placeholder for the design and styling work for the blog.

Is this still a thing? The Blog looks fine to me.

No, I think we'll be going with what we have


Error when try to compile example "helloworld".

Logs:
λ tondev sol compile helloDebot.sol
Starting build...
Code was generated and saved to file helloDebot.code

ABI was generated and saved to file helloDebot.abi.json

TVM linker 0.1.0
COMMIT_ID: 69757926ca24fff2f61a0eb3a666038f35a14384
BUILD_DATE: Unknown
COMMIT_DATE: 2021-03-11 21:48:13 +0300
GIT_BRANCH: HEAD

ABI_PATH (obtained from INPUT): helloDebot.abi.json

Error: line 93: cannot resolve label: name "storeStringInBuilders_macro" not found

Error: 1
C:\Users\olegv\.tondev\solidity\tvm_linker.exe failed

Versions:
λ tondev sol version
Component  Version  Available
---------  -------  ---------
compiler   0.38.1   0.38.1
linker     0.1.0    0.1.0
stdlib     1.0.0    1.0.0

TONDev Version: 0.3.1
OS: Win10

Fixed in tondev 0.3.2, thanks.


remove the prepare container logic, and also do not set the stemcell container to public.

Use SAS when copying stemcell blob to another storage account
if the source is a blob in another account, the source blob must either be public or must be authenticated via a shared access signature.

https://docs.microsoft.com/en-us/rest/api/storageservices/copy-blob


fix import error xdg.BaseDirectory

Found this while installing ovos-local-backend.  Seems to work now

replaced by https://github.com/OpenVoiceOS/OVOS-local-backend/pull/12


I18n Spanish: Patient - Data Entry

What are we trying to do?
This ticket is part of the DARIA translation effort. The goal is to implement all our text in both English and Spanish through the i18n* process.
This ticket is for the Patient Data Entry view.
Code link:
app/views/patients/data_entry.html.erb
The current English text should be moved to config/locales/en.yml,
and new Spanish text should be added to config/locales/es.yml.
Google translate is perfectly acceptable!
PRs will be reviewed by a fluent CM to correct any weirdness.
For this ticket, consider reusing keys defined for the main Patient object!
How could we solve this issue?
Steps
For each view

find each instance of displayed text on the view
<%= f.date_field :appointment_date, label: 'Appointment date', autocomplete: 'off', help: "Approx gestation at appt: #{patient.last_menstrual_period_at_appt}" %>
replace it with a call to i18n t function with a unique identifier based on the file path & field
<%= f.date_field :appointment_date, label: t('patient.dashboard.appt_date'), autocomplete: 'off', help: t('patient.dashboard.approx_gestation', gest: patient.last_menstrual_period_at_appt) %>
add a config entry for each language with that identifier as the key, and the language line as the value.
en.yml:patient:
  dashboard:
    approx_gestation: 'Approx gestation at appt: %{gest}'
    appt_date: Appointment date

es.yml:patient:
  dashboard:
    approx_gestation: 'Aprox la gestación en la cita: %{gest}'
    appt_date: Día de la cita

Completed View Example
For an example of a completed view translation, see the footer view i18n PR.
Formatting in the YAML files
Each view should have a it's own section. If you see the same key being used across Some commonly used values can go under a shared secton. app/views/patients/_patient_dashboard.html.erb keys go under patient: -> dashboard:.
For this particular view, you should consider reusing existing fields under patient!
Finalizing with i18n-tasks
After you finish all the keys, you should run the i18n checker before committing! This sorts the keys in a standard way and checks for missing keys.
i18n-tasks normalize
i18n-tasks health - address any issues this highlights!
More info on using i18n-tasks
* 'i18n' is shorthand for 'Internationalization'. More info on i18n in Rails
Part of #1382

I'd like to work on this issue tonight!

@drubaby this is already in progress in #1649 - sorry that wasn't tagged on here!


Support drawing annotations with geojs

This supports an upcoming PR in HistomicsTK to draw annotation on top of large_image viewers.  This adds a components:

New models and collections representing both "annotations" and "elements".  The annotation types are real models that can be sync'ed to the server, but elements are ephemeral objects for storing the individual primitive elements.
Modules in web_client/annotations/geojs that generate large_image annotations from native geojs annotation objects.
A couple of methods and events added to the viewer class itself to trigger "drawing mode".

The CI is current failing at server_large_image.tiles.  I assume the failure is also in master because I didn't make any relevant server side changes.

The CI is failing because of a recent change to girder_worker and in travis we are sharing a python environment between girder and girder worker.  PR #176 contains a fix as well as its relevant code.

Yeah, the missing coverage is mostly in imageViewerWidget/geojs.js; particularly the drawing part.  I struggled a bit to figure out how to test much of that inside phantom.  I managed to do it in my integration tests in HistomicsTK using vgl mocking and interactor.simulateEvent.  I can do the same here in a future PR.


Custom CosmWasm Integration

Description

This follows up on the earlier CosmWasm integration work and adds custom bindings for Osmosis AMM functionality.
Contract Bindings
The other half of the work lives in https://github.com/confio/osmosis-bindings (which we are happy to transfer to the osmosis org when this is merged). If you import osmo-bindings in your contract, it will get an Osmosis-specific feature flag (so it will be rejected on upload by other chains), and gets access to some custom functionality. In particular, messages to Swap or Mint native tokens. As well as various queries on the AMM. We are currently missing queries for TWAP as that is not yet implemented, but we will add such bindings in a future PR when that feature is stable in the main branch.
These APIs are stable and the contracts will look the same even if the keepers and Go data types change (I just had to do one such fix right before merge), as this PR serves as a translation layer from contracts to the AMM. The Rust bindings comes with a sample contract, which we upload and use in a lot of CI tests in this PR to ensure the whole flow (contract -> Osmosis -> contract) is working correctly.
Go adapters
I will comment key points in the PR, but we update OsmosisApp to register custom Wasm query and message handlers. All code is stored in app/wasm, which exposes high level interfaces that are imported by the OsmosisApp.

message_plugin.go - Code to handle the OsmosisMsg types returned and make native calls
queries.go and query_plugin.go - Code to handle the OsmosisQuery type and return proper data
wasm.go the high level binding that can be imported by OsmosisApp to register all the handlers
bindings/ - Go types to match the Rust types exported by https://github.com/confio/osmosis-bindings (same JSON representation)
testdata/ - Compiled wasm test contract and scripts to update
test/ - CI tests to ensure basic contract functionality (from initial permissioned integration) as well as all the custom callback handlers.

For contributor use:

[x] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer

Codecov Report

Merging #1135 (e6c6000) into main (d143d83) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1135      +/-   ##
==========================================
- Coverage   20.21%   20.17%   -0.05%
==========================================
  Files         199      201       +2
  Lines       25062    25112      +50
==========================================
  Hits         5066     5066
- Misses      19069    19119      +50
  Partials      927      927

Impacted Files
Coverage Δ

app/wasm/bindings/query.go
0.00% <0.00%> (ø)

app/wasm/bindings/types.go
0.00% <0.00%> (ø)

x/gamm/keeper/keeper.go
29.16% <0.00%> (-31.71%)
:arrow_down:

x/pool-incentives/module.go
56.25% <0.00%> (-1.33%)
:arrow_down:

x/gamm/module.go
66.66% <0.00%> (-0.84%)
:arrow_down:

x/incentives/keeper/distribute.go
61.00% <0.00%> (-0.12%)
:arrow_down:

x/claim/abci.go
0.00% <0.00%> (ø)

osmomath/math.go
64.44% <0.00%> (ø)

x/mint/module.go
56.75% <0.00%> (ø)

x/claim/handler.go
0.00% <0.00%> (ø)

... and 40 more

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 d143d83...e6c6000. Read the comment docs.

This is only failing linter, but not sure how to run that locally (and there is no clear error message in the CI).
Any tips?

So our original thinking re: native token minting was to make a "tokenfactory" module #584 / #1029 . Would it be possible / a blocker to comment out or otherwise disable the Mint tokens API for now, and re-enable that once the token factory gets on mainnet?
The goal right now is to get a mainnet upgrade out around April 8th / applied on chain week of April 15th. So we likely can't get token factory in on that time frame. Should we aim to get osmo bindings in?
Related: how careful do we need to be around backwards compatibility? (Are the bindings versioned)

Re linting: make lint lets you run it locally. You may need to merge main into the branch, since the linter had some updates in the last week.
The error here appears to be trailing newlines, so I think make format may even fix that for you

So our original thinking re: native token minting was to make a "tokenfactory" module #584 / #1029 . Would it be possible / a blocker to comment out or otherwise disable the Mint tokens API for now, and re-enable that once the token factory gets on mainnet?

Sure.

The goal right now is to get a mainnet upgrade out around April 8th / applied on chain week of April 15th. So we likely can't get token factory in on that time frame. Should we aim to get osmo bindings in for swaps, just without minting tokens?
Related: how careful do we need to be around backwards compatibility? (Are the bindings versioned)

The bindings are versioned. That's what the version.txt field in app/wasm/testdata is for. Every time the bindings are (breaking) changed, a new version of osmosis would need to be released, with the integration / support for the changes. There can be some non-breaking changes, basically depending on the json support of optional / omitted fields. But that will not be the case in general.

@ValarDragon

So our original thinking re: native token minting was to make a "tokenfactory" module https://github.com/osmosis-labs/osmosis/pull/584 / https://github.com/osmosis-labs/osmosis/issues/1029 . Would it be possible / a blocker to comment out or otherwise disable the Mint tokens API for now, and re-enable that once the token factory gets on mainnet?

This is commented out. Since the commits will be squashed and this will not be in the git history, I left this in as comments. When the token factory is added, we can add osmosis-v2 bindings that contain this in addition (and all v1 functionality)

Merged main and fixed conflicts.
I will merge PR once CI passes.


antivirus flagged as a virus

why my antivirus flag the script as trojan? is it safe to use it

@rifqy354 I am not sure what you have downloaded and from where.
Can you please provide more information and the whole antivirus message?

it is my kaspersky antivirus that flagged it as a virus while the scraping is on process.
this is the whole report from kaspersky
Event: Download denied
User: LAPTOP-INHBRJQR\ASUS
User type: Active user
Application name: chrome.exe
Application path: C:\Users\ASUS\AppData\Local\ms-playwright\chromium-978106\chrome-win
Component: Web Anti-Virus
Result description: Blocked
Type: Trojan
Name: HEUR:Trojan.Script.Generic
Precision: Heuristic Analysis
Threat level: High
Object type: File
Object name: elfsight-whatsapp-chat.js?ver=1.2.0
Object path: http://bumisurabaya.com/wp-content/plugins/elfsight-whatsapp-chat-cc/assets
MD5: 83AA8AC89DCE72069AFCAA4CD20FC827
Reason: Expert analysis
Databases release date: Today, 17/03/2024 09:03:00

have you enabled to get emails?
When you do that the program visits an external page (not gmaps).
see that: Object path: http://bumisurabaya.com/wp-content/plugins/elfsight-whatsapp-chat-cc/assets
this has nothing to do with the code in this repo

i insert -email to script. ok, thanks for helping


Update dashboard bg color to match Figma

In Figma there's a semi-transparent color (#F4F6F799) overlayed on top of the background image (see: app > window > 2nd "window"); this layer seems to be the difference between the application bg color seen in Figma and our current color.

i'm not too sure about that - figma seems to indicate that the white background color is correct.
however, it is true that our opacity is wrong for some reason...
will open a PR soon.

change of plans on the dashboard side (for now) - the asset panel background has been reverted to white / 40% opacity, and instead a shadow + clip path has been used to display a shadow on the left side

nvm


Update tutorial-c-module.md

@kgremban - Would you review the latest updates and let us know whether the PR is ready to merge? Thanks!

#sign-off
Thanks, Dane

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


Update style check tools

Fix: #4610
Related: #4674

@kmaehashi @beam2d Can you merge this?

Jenkins CI test (for commit<PHONE_NUMBER>c233448376876b2d64d3a93a527f69) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

The Jenkins failure (links_tests.normalization_tests.test_batch_renormalization.BatchRenormalizationTest_param_9.test_forward_multi_gpu) is irrelevant to the PR.

Context behind this PR

We are planning to stop using hacking in v5 final release. The motivation is to make version of each tool under our control, so that we can use the latest tools (ie, which includes the latest bug fixes) as early as possible.
As a first step, we substituted hacking package with explicit tool requirements with version specified. Please note that this is currently under the trial phase; we may revise this later.
This PR does not intend to change our coding style.
The ignore rules are adjusted so that code that passes check with toolset installed via hacking==1.0.0 should be able to pass check with toolset installed via new dependencies proposed in this PR. However, the reverse may not be true; it will be confirmed during the trial period.

LGTM!


Fixes #28: unsupported entry types handled

Coverage increased (+0.1%) to 88.478% when pulling 0751b445a17ed8cf8853cdbfc21631df383800ea on anton-nayshtut:issue_28 into d11488a8233edb8e81172ef1f0c16e22ed349b3e on conbus:master.


[SPARK-42310][SQL] Assign name to _LEGACY_ERROR_TEMP_1289

What changes were proposed in this pull request?
This PR proposes to assign name to _LEGACY_ERROR_TEMP_1289, "INVALID_COLUMN_NAME".
Why are the changes needed?

We should assign proper name to LEGACY_ERROR_TEMP*
Does this PR introduce any user-facing change?

No
How was this patch tested?

./build/sbt "sql/testOnly org.apache.spark.sql.SQLQueryTestSuite*

Thanks for the review, @MaxGekk !
Just adjusted the comments.

Merged to master and branch-3.4.


Not able to access kuma GUI on Local

Hello,
I am following article https://konghq.com/blog/getting-started-kuma-service-mesh/
and when running kubectl port-forward svc/kuma-control-plane -n kuma-system 5681:5681 command, below error logs are appearing on terminal and GUI is either not working or very very slow.
what am I doing wrong?
Error Logs: -
jaikratsinghtariyal@C02G47JNML7H bin % kubectl port-forward svc/kuma-control-plane -n kuma-system 5681:5681
Forwarding from <IP_ADDRESS>:5681 -> 5681
Forwarding from [::1]:5681 -> 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
E0914 23:02:27.145726   24504 portforward.go:372] error copying from remote stream to local connection: readfrom tcp4 <IP_ADDRESS>:5681-><IP_ADDRESS>:60517: write tcp4 <IP_ADDRESS>:5681-><IP_ADDRESS>:60517: write: broken pipe
E0914 23:02:27.910222   24504 portforward.go:372] error copying from remote stream to local connection: readfrom tcp4 <IP_ADDRESS>:5681-><IP_ADDRESS>:60519: write tcp4 <IP_ADDRESS>:5681-><IP_ADDRESS>:60519: write: broken pipe
Handling connection for 5681
E0914 23:02:57.142136   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681
E0914 23:02:57.927721   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
Handling connection for 5681
E0914 23:03:27.149215   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:03:27.937567   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681
E0914 23:03:38.330821   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:03:38.653888   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681
E0914 23:03:45.625788   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:03:47.466218   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681
Handling connection for 5681
E0914 23:03:53.193923   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:03:56.610405   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:03:59.576055   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:04:12.001369   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:04:19.851502   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
E0914 23:04:19.851553   24504 portforward.go:340] error creating error stream for port 5681 -> 5681: Timeout occurred
Handling connection for 5681

Hi @jaikratsinghtariyal is there any specific details you can provide on how you are running this? How is your k8s cluster running? If the control-plane pod running?

@lahabana ...I am good... this ticket can be closed.