Elasticsearch rest async context propagation

What does this PR do?
Initially reported in our forum.
When using the new ES Java client (8.x), the asynchronous call is delegated to a CompletableFuture (CF) using code similar to the following:
  RestClient restClient = RestClient.builder(ES_HOST).setDefaultHeaders(DEFAULT_HEADERS).build();
        ElasticsearchTransport transport = new RestClientTransport(restClient, new JacksonJsonpMapper());
        ElasticsearchAsyncClient client = new ElasticsearchAsyncClient(transport);

        CompletableFuture<SearchResponse<Product>> search = client.search(s -> s.index("products")
                        .query(q -> q.term(t -> t.field("name")
                                .value(v -> v.stringValue("product")))),
                Product.class);

        CompletableFuture<SearchResponse<Product>> result = search
                .thenApplyAsync(response -> {

                    // We don't see the active transaction or span, even if there is one
                    System.out.println("span = "+ ElasticApm.currentSpan());
                    System.out.println("span = "+ ElasticApm.currentTransaction());

                    return response;
                }, _executorService);

In practice, the context propagation works already for the CompletableFuture, and I just had to extend co.elastic.apm.agent.esrestclient.ResponseListenerWrapper to ensure this entry-point in the ES driver is properly covered.
While the example above relies on the new 8.x ES client, the underlying method that is instrumented is available in recent 7.17 versions, thus we just provide it in a new7.x ES instrumentation plugin (previously it was only just for testing).
Checklist

[x] This is a bugfix

[ ] I have updated CHANGELOG.asciidoc
[x] I have added tests that would fail without this fix

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-02-08T16:30:33.575+0000

Duration: 31 min 48 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
2218

Skipped
48

Total
2266

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Bugfix has been validated by the end-user (who initially reported it in the forum).


Need Help in Integrating with A-Frame webgl context

I am trying to integrate A-Frame with handtracking.js but not successfull.
Here's the code: https://woolen-windy-legal.glitch.me
When I see Console ,I get error:
Uncaught (in promise) TypeError: Cannot read property height of null
at getInputTensorDimensions (handtrack.min.js:25)
at ObjectDetection.detect (handtrack.min.js:42)
at runDetection (aframe.html:49)
at aframe.html:60
Please help me fix this !!!

You need make sure your object / variable is not returning null, or if it is handle it in someway.


Qt warning after exiting editor

When using the following config, I am getting multiple generic Qt warnings after exiting the editor.
log message(s):
Using QCharRef with an index pointing outside the valid range of a QString. The corresponding behavior is deprecated, and will be changed in a future version of Qt.

chr configuration:
color_space_end=true
color_tabs=true
highlight_bracket=true
right_margin_hint=80
tab=false
tabsize=8
theme=dark
wrap_lines=true

Thanks for reporting this reproducer.
With highlight_bracket=true empty lines trigger that message while processing bracket highlight.
I've fixed this cause of the error message in c1267820.
I'll close this issue for now.
But if you find another reproducible way to trigger these kind of error messages, please feel free to open another report.


Additional API for Weewx

In reference to #217 and #70 an additional API for Weewx weather integration was added.  I also added a sample JSON responese for testing.

Hi thanks for your PR! I cannot test this at the moment but as it seems not to break any existing functionality, I will gladly merge it. Could you provide some instructions how to use this in the readme?

Just curious... in the WeeWX JSON, characteristics which have units are broken out into arrays grouped according to the measurement system used.  I followed your lead in my contribution, but I was wondering why it's that way. Is it because WeeWX does the conversions itself, and all those values are already available?  Or because the developer of weewx-json handled it that that way?  The homebridge-weather-plus code has functions in characteristics.js for doing the unit conversions, and I think providing only one system of units in the JSON input and having weather-plus do the conversions would generally be more preferable.

I based the formatting off of the JSON response and the api reader on the Weather Underground JSON response and just included all the units that it would respond with.  You could format it to only use metric_si units, but I planned on using this JSON response with another application so I wanted to include the other units as well.  It also helped me to make sure I had everything coded correctly since I could make sure I was getting the correct units.

Really looking forward to this feature! 😊

Today, i have tried to install and connect to weewx. weewx create the json-File.
But the homebridge shows no values. homebridge shows an error:
[10.5.2022, 18:34:03] [WeatherPlus] Error retrieving weather report and forecast
[10.5.2022, 18:34:03] [WeatherPlus] Error Message: Error: [
{
"error": {
"code": "CDN-0001",
"message": "Invalid apiKey."
}
}
]
any ideas?
am I too early? or too fast?
greatings

I don't believe this branch/edits has been incorporated yet.

Oh yes, I really need to merge and create a new release. Will do it this week.


refactor cssutils filter initalization

remove try/except ImportError and change workaround for silencing cssutils

The try/except ImportError is not needed anymore as neither a django settings object is accessed nor an import is taking
place.
The setLog / setlog deprecation workaround is not needed anymore because even Debian wheezy ships a newer version of
cssutils.
Raising the log level to fatal is enough to hide all of cssutil's warnings encountering CSS3.

This is a follow-up to the discussions held in #423.

Great, thanks!


Are there any examples how to use the evaluation framework from 2102.08921

Question
In the paper How Faithful is your Synthetic Data? Sample-level Metrics for Evaluating and Auditing Generative Models this group proposed a way to evaluate the performance of synthetic data. I was wondering if there any tutorials available that demonstrate how to use the synthcity code to do this?
I think the loss function defined in equation 8 in the above paper is defined here right?
Do you also recommend using this triple metric approach (α-Precision, β-Recall, Authenticity) for evaluating the performance of synthetic data
Cheers!

Hi @fountaindive,
The source code for that paper is all here. If you have any specific questions on the paper, you will probably get the best answer by contacting the authors directly.
I would definitely recommend using α-Precision, β-Recall, and Authenticity for measuring data fidelity (synthetic data quality). We tend to talk about synthetic data performance as being data utility, if that is what you wish to measure then you should measure performance on a downstream model, instead/as well.
Hope that helps!

Very helpful, thanks @robsdavis ! (And thanks for updating the package recently!)


Form validation

Hello,
I need to show an message error if input name is empty.
You will find below my react file and the error displayed in the console for chrome :
Hire-us.js
import React, { Component, PropTypes } from 'react';
import Helmet from 'react-helmet';
import { reduxForm } from 'redux-form';
import _ from 'lodash';

const FIELDS = {
  userName: {
    type: 'input',
    label: 'Name for person'
  }
}

class HireUs extends Component {
    onSubmit(props) {
      alert('Thanks');
    }
    render() {
        const{ fields: { userName }, handleSubmit } = this.props;

        return (

            <Helmet title="Hire us to help you realize your idea"/>

Hire us to help you realize your idea

Let's get in touch today, We're excited to hear from you!

                <form onSubmit={handleSubmit(props => this.onSubmit(props))} >

                    What is your name ?
                    <input type="text" className="form-control" {...userName} />
                    { userName.touched && userName.error &&
 { userName.error }
 }

                  <button type="submit">Submit</button>
                </form>

        );
      }
}

function validate(values) {
  const errors = {};
  if (!values.userName) {
    errors.userName = 'Name is required';
  }
  return errors;
}

HireUs.PropTypes = {
  fields : PropTypes.object.isRequired,
  handleSubmit : PropTypes.func.isRequired
};

export default reduxForm({
  form: 'HireUs',
  fields: _.keys(FIELDS),
  validate
})(HireUs);

Error
Uncaught TypeError: Cannot read property 'touched' of undefined
Uncaught TypeError: Cannot read property '__reactInternalInstance$1yra2hb0l1kux74pqspxcx47vi' of null

You can help me please.

Judging by your example, it seems you forgot to wrap your input with Field. So right now it's not connected to ReduxForm.
See here for details: http://redux-form.com/6.3.1/docs/api/Field.md/. Otherwise refer to the sync validation example here: http://redux-form.com/6.3.1/examples/syncValidation/.

Effectively, your right.
Thanks for your help Dennis :+1:

Published fix in v6.4.2.


Deceptive site ahead

Deceptive site ahead
Browser: Chrome
Version: 78.0.3904.108

There seems to be a problem with the SSL certificate. FF shows this: "Peer's Certificate has been revoked."

I believe this is to do with the Expired certificate, although the cert shows that it expired on the 10th December. There is a ticket raised under #332

Can this be fixed ASAP?

The service is not working. Can we please update the certificate?

localtunnel.me is now up and running again :)
i took over the hosting and maintenance part from @defunctzombie so feel free to use it as before.
let us know if you have further questions

I am now hosting localtunnel.me for this project so it should work like before. The only difference is that I'm handing out subdomains under the domain *.loca.lt instead of *.localtunnel.me (that's because I don't have full DNS control and without it can't get a free wildcard cert for the domain without). Let me know if you run into any issues.

@defunctzombie feel free to close this issue.


Fix documentation docker Readme

What current issue(s) does this address, or what feature is it adding?
Just documentation update.
How did you solve this problem?
How did you make sure your solution works?
Are there any special changes in the code that we should be aware of?
Please check the following, if applicable:

[ ] Did you add any tests?
[ ] Did you run make lint?
[ ] Did you run make test?
[ ] Are you making a PR to a feature branch or development rather than master?
[ ] Did you add an entry to CHANGELOG.rst? (if not, please do)

Coverage remained the same at 80.238% when pulling e95ceb5cf0a55954bba775d1aa8695167fd41342 on nunojusto:fix-documentation-dockerfile into 5cec42e3a965f522a2ff3ec559f8a936e23e671a on CityOfZion:development.


Plugin not working against android plugin 1.4.x-beta

Google released 1.4.0-beta2 (2015/09/15)
http://tools.android.com/tech-docs/new-build-system
and it's crashing while looking for
https://github.com/groovy/groovy-android-gradle-plugin/blob/master/src/main/groovy/groovyx/grooid/GroovyAndroidPlugin.groovy#L19
Stacktrace
Caused by: groovy.lang.MissingPropertyException: No such property: bootClasspath for class: com.android.builder.core.AndroidBuilder
	at groovyx.grooid.GroovyAndroidPlugin$__clinit__closure10.doCall(GroovyAndroidPlugin.groovy:19)
	at groovyx.grooid.GroovyAndroidPlugin.getRuntimeJars(GroovyAndroidPlugin.groovy:154)
	at groovyx.grooid.GroovyAndroidPlugin$getRuntimeJars$1.call(Unknown Source)
	at groovyx.grooid.GroovyAndroidPlugin$_attachGroovyCompileTask_closure5_closure19.doCall(GroovyAndroidPlugin.groovy:102)
	at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:554)
	at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:535)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)

I checked the structure of the com.android.builder.core.AndroidBuilder object in runtime , and there's a different signature in the getBootClassPath method between the 1.4.0-beta1 and the 1.4.0-beta2 version:

1.4.0-beta1:
public List getBootClasspath();
1.4.0-beta2:
public List getBootClasspath(boolean);

So, by adding a parameter to the method getBootClasspath, it can no longer be called as a property.
I tested the values returned with both boolean values:
Return value from getBootClasspath(true):
    ['C:\android-sdk\platforms\android-23\android.jar', C:\android-sdk\platforms\android-23\optional\org.apache.http.legacy.jar']
Return value from getBootClasspath(false):
    ['C:\android-sdk\platforms\android-23\android.jar']
I can guess the parameter means "include legacy bootClasspath" or something similar
I created a pull request (#62) to add the code to support 1.4.0-beta2. I tested in a simple application, that had the same error as reported (Caused by: groovy.lang.MissingPropertyException: No such property: bootClasspath for class: com.android.builder.core.AndroidBuilder
), and now it compiles without problems
I couldn't find a way to download the exact 1.4.0-beta1 and 1.4.0-beta2 source code, don't know if it's available from Google, not sure if this is the actual source code

I can't find it too. Anyways thanks for the update. I will retest the plugin once they release to 1.4.0 - no beta :)

Problem still occurs in final version v1.5.0

I seem to be having the same problem with v1.5.0 - is a release coming soon?

On the 1.5.0 version of the plugin the method bootClassPath has the same signature @dmancilla mentioned.

Until release SNAPSHOT version can be used provided by Jitpack:
https://jitpack.io/#groovy/groovy-android-gradle-plugin/1b77dd6763
It works perfectly with 1.5.0 version of the plugin.

Looks like I'm having the same issue on stable plugin 1.5.0 but I suspect it is related to dexguard (Or maybe not). Project builds fine but it can't execute.
Here's the stacktrace
Error:groovy.lang.MissingPropertyException: No such property: bootClasspath for class: com.android.builder.core.AndroidBuilder
	at com.guardsquare.dexguard.L.doCall(DexGuard7.0.19:287)
	at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:548)
	at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:529)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)

Any ideas?

@ThanosFisherman you have to use latest SNAPSHOT version
repositories {
    maven { url "https://jitpack.io" }
}
compile 'com.github.groovy:groovy-android-gradle-plugin:1b77dd6763'

Is there any news on when a new release is being planned?

+1

Thanks to @dbacinski I could also work around this issue using the snapshot version. Since it's already fixed I'm also hoping for a new release soon :)!

@JordyLangen I'm working on finding a better CI option and getting some other pieces of knowledge transferred so that I can get a new release out.

Nothing is better than TravisCI at the moment.
On Jan 5, 2016 8:17 PM, "Andrew Reitz"<EMAIL_ADDRESS>wrote:

@JordyLangen https://github.com/JordyLangen I'm working on finding a
better CI option and getting some other pieces of knowledge transferred so
that I can get a new release out.
—
Reply to this email directly or view it on GitHub
https://github.com/groovy/groovy-android-gradle-plugin/issues/61#issuecomment-169187355
.

@pieces029 Can vouch for what @jaredsburrows says, nothing beats Travis CI

@JordyLangen No, I cannot. I didn't want to start an argument on the internet though.

This has been fixed and released in the 0.3.7 release.


Use node package dependency to manage JSC version

Summary
In origin approach, we packed libjsc.so inside react-native.aar and it is difficult for user to choose different JSC variants. E.g., the Intl supported version.
This change list allows application to determine JSC versions or variants by npm/yarn package.
To use Intl JSC
There is a |useIntlJsc| flag in build.gradle, it will use the same JSC version but with Intl support.
To use latest JSC
yarn add jsc-android@canary
Changelog
[Android] [Changed] - Allow application to select different JSC variants
MIGRATION
Note that there are some changes in build.gradle.
Existing application needs to change their android/build.gradle and android/app/build.gradle.
Hopefully, the rn-diff-purge should handle the case well.
Test Plan

Test RNTester build and run successfully.
Create a new project by react-native init Foo --version /somewhere/react-native-1000.0.0.tgz and test that build and run successfully.
Turn on |useIntlJsc| and add console.log('Intl type is ' + typeof Intl) to App.js, verify if the adb log show "Intl type is object"
yarn add jsc-android@canary and rebuild. Verify adb log adb logcat | grep 'JavaScriptCore.Version' and it should return 241213.0.0 not 236355.1.0

Update: just need to figure out the internal test system to actually land this but it should be good to go soon.

Thanks @cpojer for the update and revise wording for useIntlJsc comment.
Just a reminder that there is yet another same comment not revised in template/android/app/build.gradle.
Will you prefer to update that together?

@Kudo Do you want to send another PR for the remaining changes?

@cpojer Sure, will have a PR after we have clarify which solution is better.

I think this broke the docker build because downloadJSC is still refrenced here. cc @hramos
FAILURE: Build failed with an exception.

* What went wrong:
Task 'downloadJSC' not found in project ':ReactAndroid'.

Fixed in https://github.com/facebook/react-native/pull/24360

Oops, my fault to miss this in Dockerfile. Thank you @sahrens @hramos


Cannot read property 'value' of null

Issue Id: ca98494e-9926-c29c-0bdc-e7ce6981041dVersions - 1.26.0-insider (7/6/2018 5:15:15 AM)Stack TypeError: Cannot read property 'value' of null/vs/base/browser/ui/inputbox/inputBox.ts#229:20 (value)/vs/base/browser/ui/inputbox/inputBox.ts#517:11 (addToHistory)/vs/editor/contrib/find/findWidget.ts#315:28 (task)/vs/base/common/async.ts#289:11 (onComplete)/vs/base/common/winjs.base.js#1191:0 (_notify)/vs/base/common/winjs.base.js#867:0 (enter)/vs/base/common/winjs.base.js#1089:0 (_run)/vs/base/common/winjs.base.js#1057:0 (onSuccess)/vs/base/common/async.ts#295:8

/duplicate #53421


BUG - Not eq operator for id (UUID) field parsing error

Description
Mockserver unable to parse this request, specifically at the $filter=not%20(id%20eq%20631e9c9f-b3f7-47e2-aebb-ce76802f883a%20or%20id%20eq%206e67a558-5421-41da-8314-3636bfe9124b) section.
InspectionResults?$orderby=id&$select=executedOn,id,imageUrl,status&$expand=inspectionView($select=id,name),prediction($select=id,rating,result),sfc($select=id,name)&$filter=not%20(id%20eq%20631e9c9f-b3f7-47e2-aebb-ce76802f883a%20or%20id%20eq%206e67a558-5421-41da-8314-3636bfe9124b)&$skip=18&$top=2
However, a CAP CDS server with the exact same metadata is able to parse this request that is automatically generated by SAP UI5 after deleting an ODataContext.
Steps to Reproduce
Steps to reproduce the behavior:

Call the API endpoint of the mockserver using the request URL

Expected results
Able to receive the GET response.
Actual results
Parsing error
Screenshots
If applicable, add screenshots to help explain the problem.

Version/Components/Environment
Add any other context about the problem here
OS:

[X] Mac OS
[ ] Windows
[ ] Other

Root Cause Analysis
Problem
{describe the problem}
Fix
{describe the fix}
Why was it missed
{Some explanation why this issue might have been missed during normal development/testing cycle}
How can we avoid this
{if we don’t want to see this type of issues anymore what we should do to prevent}

Fixed with @sap-ux/ui5-middleware-fe-mockserver": "^2.1.125


gdb failure - "Operation not permitted."

Hi,
I cannot seem to get gdb to work with any pods. I get the following error. Any clue as to what might be going on?
Please note pods run as non root (if that has anything to do with it).
(gdb) target remote localhost:54990
Remote debugging using localhost:54990
Reading /usr/bin/node from remote target...
warning: File transfers from remote targets can be slow. Use "set sysroot" to access files locally instead.
warning: "target:/usr/bin/node": could not open as an executable file: Operation not permitted.
Reading /usr/bin/node from remote target...
warning: `target:/usr/bin/node': can't open to read symbols: Operation not permitted.
warning: Could not load vsyscall page because no executable was specified

Hi @naseemkullah it looks like you are debugging node.js with gdb, is that true?

Hi @mitchdraft, in fact it is node js “wrapped” c++

Interesting, I am not familiar with that paradigm. Could you provide an example? I'd like to give it a shot.
Are you able to use gdb on this target when running locally? If so, squash + gdb should work in cluster.
It's possible that you need to use a node js built with debug symbols.
I don't think it's a non-root user issue, since squash-plank runs as root when opening a gdb connection: https://github.com/solo-io/squash/blob/master/cmd/plank/Dockerfile.gdb

So an example of this paradigm would be: https://github.com/martinbark/nan-hello-world
I'd like to point out that after remove the securityContext of the workload, which included readOnlyFileSystem, the error dissapeared!  https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#securitycontext-v1-core
Ideally we would be able to run the pods with the securityContext and still be able to use squash.
However I am now faced with the following error, any clues as to what may be causing this?
(gdb) target remote localhost:60009
Remote debugging using localhost:60009
warning: <threads>
<thread id="48c3a"/>
</threads>
: No such file or directory.
warning: Remote failure reply: E01

PS when you ask about running locally, do you mean the process running locally, or as a container or as a k8s workload on minikube?

thanks for the link, that's really cool.
When I say "are you able to debug locally", I mean can you run the process on your computer (no kubernetes, minikube, or container) and debug it with gdb, also running locally. This is a good sanity check when testing squash in a new language/environment. If gdb works in that case, it should work through squash.
I'm glad you figured out why gdb couldn't open the file as an executable. I'm not sure if we can make it work while readOnlyFileSystem is in effect. It would be interesting to investigate.
For your new error, I don't think you need to use the remote commands. The way squash works is to run gdb on the same node as your target process and then attach directly. You should not need to specify a target once gdb is running. Could you try a different gdb command, something like list instead?

Np for the link!
Ah I see now with regards to locally. Yes gdb does work with process running locally.
Yes or it would be nice if we could have a RO filesystem and juste have maybe /usr/bin/node as Read-Execute somehow, maybe securityContext's will evolve to permit this.
With regards to current error, just to be clear I get the following message when starting up squash:
Squash will create a debugger pod in your target pod's namespace.
Creating service account squash-plank in namespace squash-debugger

Creating cluster role squash-plank-cr

Creating cluster role binding squash-plank-crb

All squashctl permission resources created.

Pod creating
Forwarding from <IP_ADDRESS>:52429 -> 33171
Forwarding from [::1]:52429 -> 33171
gdb debug port available on local port 52429.

If I just type list as a command I get the following:
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) list
No symbol table is loaded.  Use the "file" command.
(gdb)

So I think using a remote target of localhost with the forwarded port is the right idea as per: https://github.com/solo-io/squash/blob/master/next_docs.md
Just guessing but might it have something to do with my gdb running on macOS and the container being Ubuntu based?

ah yes, sorry, you were write about the invocation. I need to move those docs into the website.
I think you just need to tell gdb where to find the symbol table now. You should be able to do that with directory. You may also need to specify a substitute-path. Here's a link to the man pages https://sourceware.org/gdb/onlinedocs/gdb/Source-Path.html
I have used squash and gdb from mac to ubuntu containers without problems in the past.


Mention the stretching behavior of PopupPanel

Closes #27555

Looks good, thanks! Guess this applies to 3.x too then?

Yes, in 3.x the behavior is the same.

Cherry-picked for 3.6.

Cherry-picked for 3.5.1.


CLOUDSTACK-8805: Domains become inactive automatically.

Handled the '%' case by replacing that with a literal character rather than a wildcard character.

@nitin-maharana I see also PR #775, can this be closed?

Both are valid solutions for the very same problem, we would have to choose between one of them. @nitin-maharana said that he tested with the other solution, so I think this one can be closed.

@remibergsma Yes this one should be closed. PR #775 does the same thing. Thanks.


Local dataset server like MinIO [FEATURE]

🚨🚨 Feature Request

[x] Related to an existing Issue

Is your feature request related to a problem?
In my environment, there are multiple local servers storing data and training models. To properly manage data, I wanna isolate one machine and start a data server like MinIO. Unfortunately HUB can only store data locally, or upload to S3, Google and Azure. Is there a plan to work on a local server?
If your feature will improve HUB
To make HUB work on a collaborative team with local shared data.
Description of the possible solution
Adding more options to url and token,.

You could try using a local tag (eg tag = "./local_dir"), which tells Hub to work with the local machine.
I know it doesn't directly answer your question, but I have not tried out Hub + MinIO. @AbhinavTuli might be able to help.

Hey @qizhen816, hub should already work with MinIO, take a look at this example for reference. Do let me know if you face any issues.

I was also thinking about it, and then I found this test case where you can set url to s3://whatever and the token to something like this:
token = {
    "aws_access_key_id": "your_minio_access_key",
    "aws_secret_access_key": "your_minio_secret_key",
    "endpoint_url": "your_minio_url:port",
}

and it just works! I've tested myself by hosting a local minio/minio container and this Getting started example.

@gabriel-milan it's good to hear that you got it working. I think we should probably add it to the getting started section along with gcs, s3, azure sections. Would you be interested in making a PR for the same 😄 ?

Sure, there you go! https://github.com/activeloopai/Hub/pull/605

Thanks! It works!


[ci skip] adding user @maresb

Hi! This is the friendly automated conda-forge-webservice.
I've added user @maresb as instructed in #17.
Merge this PR to add the user. Please do not rerender this PR or change it in any way. It has [ci skip] in the commit message to avoid pushing a new build and so the build configuration in the feedstock should not be changed.
Please contact conda-forge/core to have this PR merged, if the maintainer is unresponsive.
Fixes #17

Only if you feel like it... just offering to help out


Fixes for dc/refactor branch

Bugfixes for dc/refactor branch (#693):

Invalid torrent identifier error when adding new torrent
Step Forward and Step Backward commands not working

LGTM. About to cherry pick. Thanks!

W dniu środa, 6 lipca 2016 Adam Gotlib<EMAIL_ADDRESS>napisał(a):

Bugfixes for dc/refactor branch (#693
https://github.com/feross/webtorrent-desktop/pull/693):

Invalid torrent identifier error when adding new torrent
Step Forward and Step Backward commands not working

You can view, comment on, or merge this pull request online at:
https://github.com/feross/webtorrent-desktop/pull/706
Commit Summary

Refractor main.js: controllers.playback.skip()
Fix 'invalid torrent identifier' error

File Changes

M main/menu.js
https://github.com/feross/webtorrent-desktop/pull/706/files#diff-0
(4)
M renderer/controllers/playback-controller.js
https://github.com/feross/webtorrent-desktop/pull/706/files#diff-1
(5)
M renderer/controllers/torrent-list-controller.js
https://github.com/feross/webtorrent-desktop/pull/706/files#diff-2
(20)
M renderer/main.js
https://github.com/feross/webtorrent-desktop/pull/706/files#diff-3
(19)
M renderer/webtorrent.js
https://github.com/feross/webtorrent-desktop/pull/706/files#diff-4
(16)

Patch Links:

https://github.com/feross/webtorrent-desktop/pull/706.patch
https://github.com/feross/webtorrent-desktop/pull/706.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/feross/webtorrent-desktop/pull/706, or mute the
thread
https://github.com/notifications/unsubscribe/ASUyHUAucw4is9Gx-ma9q8OSByuUDiWnks5qS-BrgaJpZM4JGS-Y
.


迁移未完成进程终止

使用的是最新版的工具，但是还是会出现这种迁移没有完成，程序就终止了，但是并没有任何报错信息，日志给出的也是完成的日志。

配置文件参数如下：

不管迁移的版本是从8.x迁移到8.x，还是8.x迁移到7.x，7.x迁移到7.x都会出现这种现象

you can use the version v1.1.1

you can use the version v1.1.1

还是一样的结果，迁移一部分后就结束进程了，不知道什么原因
{"file":"D:/go/pkg/mod/github.com/!charell!king/ela-lib@v1.0.31/service/migrator.go:817","func":"github.com/CharellKing/ela-lib/service.(*Migrator).singleBulkWorker","level":"info","msg":"bulk progress 0.5352 (2242488, 4190366, 0)","sourceEsVersion":"8.7.1","targetEsVersion":"7.15.1","taskAction":"sync","taskId":"2b6f87df-ae40-4463-ab27-38818d536c55","taskName":"task1","time":"2024-10-10T19:48:35+08:00"}
{"file":"D:/go/pkg/mod/github.com/!charell!king/ela-lib@v1.0.31/service/migrator.go:817","func":"github.com/CharellKing/ela-lib/service.(*Migrator).singleBulkWorker","level":"info","msg":"bulk progress 0.5372 (2250977, 4190366, 0)","sourceEsVersion":"8.7.1","targetEsVersion":"7.15.1","taskAction":"sync","taskId":"2b6f87df-ae40-4463-ab27-38818d536c55","taskName":"task1","time":"2024-10-10T19:48:43+08:00"}
{"file":"D:/go/pkg/mod/github.com/!charell!king/ela-lib@v1.0.31/service/migrator.go:743","func":"github.com/CharellKing/ela-lib/service.(*Migrator).search.(*Migrator).searchSingleSlice.func3","level":"info","msg":"scroll slice 1 exit","sourceEsVersion":"8.7.1","targetEsVersion":"7.15.1","taskAction":"sync","taskId":"2b6f87df-ae40-4463-ab27-38818d536c55","taskName":"task1","time":"2024-10-10T19:49:15+08:00"}
{"file":"D:/go/pkg/mod/github.com/!charell!king/ela-lib@v1.0.31/service/migrator.go:885","func":"github.com/CharellKing/ela-lib/service.(*Migrator).bulkWorker","level":"info","msg":"bulk progress 0.5452 (2284500, 4190366, 0)","sourceEsVersion":"8.7.1","targetEsVersion":"7.15.1","taskAction":"sync","taskId":"2b6f87df-ae40-4463-ab27-38818d536c55","taskName":"task1","time":"2024-10-10T19:49:17+08:00"}
{"file":"D:/go/pkg/mod/github.com/!charell!king/ela-lib@v1.0.31/service/bulkmigrator.go:771","func":"github.com/CharellKing/ela-lib/service.(*BulkMigrator).parallelRun.func1","level":"info","msg":"task progress 1.0000 (1, 1)","sourceEsVersion":"8.7.1","targetEsVersion":"7.15.1","taskAction":"sync","taskId":"2b6f87df-ae40-4463-ab27-38818d536c55","taskName":"task1","time":"2024-10-10T19:49:17+08:00"}
{"file":"D:/go/pkg/mod/github.com/!charell!king/ela-lib@v1.0.31/service/taskmgr.go:57","func":"github.com/CharellKing/ela-lib/service.(*TaskMgr).Run","level":"info","msg":"tasks progress 1.0000 (1, 1)","sourceEsVersion":"8.7.1","targetEsVersion":"7.15.1","taskAction":"sync","taskId":"2b6f87df-ae40-4463-ab27-38818d536c55","taskName":"task1","time":"2024-10-10T19:49:17+08:00"}

you can use the version v1.1.1

如果是较小的索引迁移的话出现这种现象可以再执行一次迁移过程才可以完全的迁移完成，但是如果是大索引的话再执行一次很明显不符合迁移的效率

you have 5 slices. why only one slice exit: {"file":"D:/go/pkg/mod/github.com/!charell!king/ela-lib@v1.0.31/service/migrator.go:743","func":"github.com/CharellKing/ela-lib/service.(*Migrator).search.(*Migrator).searchSingleSlice.func3","level":"info","msg":"scroll slice 1 exit","sourceEsVersion":"8.7.1","targetEsVersion":"7.15.1","taskAction":"sync","taskId":"2b6f87df-ae40-4463-ab27-38818d536c55","taskName":"task1","time":"2024-10-10T19:49:15+08:00"}

you have 5 slices. why only one slice exit: {"file":"D:/go/pkg/mod/github.com/!charell!king/ela-lib@v1.0.31/service/migrator.go:743","func":"github.com/CharellKing/ela-lib/service.(*Migrator).search.(*Migrator).searchSingleSlice.func3","level":"info","msg":"scroll slice 1 exit","sourceEsVersion":"8.7.1","targetEsVersion":"7.15.1","taskAction":"sync","taskId":"2b6f87df-ae40-4463-ab27-38818d536c55","taskName":"task1","time":"2024-10-10T19:49:15+08:00"}

你说的这个进程，是在逐渐的退出的，例如我有50 slices ，在迁移过程中会逐渐的退出，而我给出的日志只有一部分

you can try v1.1.2; maybe your slice scroll request has some problem.

you should use the newest version v1.1.3


070 national agricultural library call number

https://github.com/uwlib-cams/MARC2RDA/blob/main/Working Documents/0XX.csv

@pennylenger @GordonDunsire
The google sheet and document indicate different mappings for when 070 is a "serial-like item" versus not. How do I determine this?

I am not sure, but I looked at the example:
070 | 0#$a281.9$bC81A [Number assigned from the USDA library scheme.]
070 | 0#$aQH301.A5 $b1981 [Number assigned from the LC classification scheme.]
Can we use a pattern like [A-Z][1-9] to determine the LC classification scheme?

@cspayne, @pennylenger: The transformation of 'serial-like' resources is out of scope for this phase. What determines 'serial-like' will be dependent on the values of other fields, especially 00x.
However, I agree with @pennylenger's suggestion. It avoids getting entangled in diachronic weeds, and it is a really neat way of distinguishing LC classification from other schemes.

"Prefixes may occur in NAL call numbers. "A" specifies a USDA publication in the old USDA scheme; "a" specifies a USDA publication in the LC classification scheme; "R" specifies a rare book; "J" specifies a juvenile book; and "Fo" specifies a folio publication."
Do we know whether numbers assigned from the USDA library scheme are always only numbers or beginning with "A" and then only numbers? Or can we only determine whether it's from LC when it starts with "a"?

@cspayne: I don't know anything about the old USDA scheme, but in the example '281.9' cannot be based on any LC scheme because it is a decimal number without a preceding alphabetical class indicator. So presumably it is the same USDA classification as 'A 281.9'. This cannot be confused with LC numbers under class indicator 'A' because it is immediately sub-classed by a second upper-case alpha character, for example 'AC'.
So I think it's safe to remove 'A' if it is immediately followed by a numeric character, and treat it as being in the original USDA scheme.
It's also ok to remove the prefix 'a' and treat the value as being in the LC scheme.
I have no idea what to do with the other prefixes, or this example from the MARC 21 manual:
070 	0# $aTRANSL$b17828

Since we don't do anything with NAL numbers, I'm not familiar with them.
Adam
Adam L. Schiff
Principal Cataloger
University of Washington Libraries
(206) 543-8409
@.***

From: Cypress @.>
Sent: Monday, September 16, 2024 10:48 AM
To: uwlib-cams/MARC2RDA @.>
Cc: Adam L Schiff @.>; Mention @.>
Subject: Re: [uwlib-cams/MARC2RDA] 070 national agricultural library call number (Issue #89)
@AdamSchiffhttps://urldefense.com/v3/__https://github.com/AdamSchiff__;!!K-Hz7m0Vt54!iyTdAzoxEWD3GFt46wPwhxI6zQiPMZW0H2fxQBVKh9i2-Ng0P9xYBdsG3UVp-nfarehZaJXr2dZcZradZrc6yMQ$
Do you know if there is a good way to tell whether a National Agricultural Library call number comes from the old USDA scheme or from LC aside from the prefixes?
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/uwlib-cams/MARC2RDA/issues/89*issuecomment-2353541817__;Iw!!K-Hz7m0Vt54!iyTdAzoxEWD3GFt46wPwhxI6zQiPMZW0H2fxQBVKh9i2-Ng0P9xYBdsG3UVp-nfarehZaJXr2dZcZradn3zmJaM$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ADFBVB2AA5KMAZKGHKHIIZLZW4KWBAVCNFSM6AAAAABN7NLLRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJTGU2DCOBRG4__;!!K-Hz7m0Vt54!iyTdAzoxEWD3GFt46wPwhxI6zQiPMZW0H2fxQBVKh9i2-Ng0P9xYBdsG3UVp-nfarehZaJXr2dZcZradMIRrFbk$.
You are receiving this because you were mentioned.Message ID: @.***>


Update banking.yml

Added Santander UK

Every site is required to have an accompanying logo. Please see CONTRIBUTING for details.

Either the CONTRIBUTING or the wiki. The wiki might be easier to read

Oh hey, look at that. Wiki. Wiki is good.

@xeonwales are you going to add another commit to the PR?
If not then I will close the PR in a few days just to clean up the list of PRs.


automaticSilentRenew iframe/callback URI issues - Cordova (android)

I'm writing an Ionic2 application and I'm having trouble dealing with the callback URI in the iframe used by the automaticSilentRenew feature.  Bear with me, I am new to the whole Ionic/cordova world.
The refresh event is triggered, the iframe is created, and the process begins.  I can verify from my identity provider that the refresh is taking place and the redirect is issued successfully.
The issue is when the iframe handles the redirect to the callback URI, and an exception is thrown -
"ERR_CONNECTION_REFUSED".  Makes sense, we are running on a phone, not in a true web-based SPA.
So, my question is, how do you suggest handling automatic refresh in a native environment?

One option I tried was to mimic the silent renew manually.  But when I do this, I hit a wall validating the auth response and trying to update the UserManager with the new values (I would have to do all of this manually as well).
For example, open up a way to call the OidcClient.processSigninResponse(url, stateStore) method manually through the UserManager.

If your redirect uri is handled by the application , so something like com.myApp://authredirect then does this not work? I've done something similar in React Native.

You should be using a different library than this for a native app. See here for a reference: https://github.com/openid/AppAuth-JS

I've had zero luck with AppAuth-JS in our project.  Build/npm errors right out of the gate.  It seems like it's still in it's infancy stages.

Well, you're building a native app, not a browser-based app (at least according to the OAuth2/OIDC distinctions), so oidc-client is not designed for native apps.

@brockallen Is there anything specific that AppAuth-JS does that this library doesn't? I'm using this library in a native app and it seems to be working.

It hybrid flow and PKCE. This library only does implicit.

@brockallen I just want to clarify, I'm working on a hybrid/Cordova app - which this library seemed to originally support (CordovaPopupNavigator, CordovaIFrameNavigator, etc).  I understand hybrid+PKCE flow, but have yet to find a production-ready client that supports this for a hybrid/Cordova app.
@sattaman, if you find a suitable replacement for this library, let me know.  I will do the same.

Yes, we did add cordova support but that was before the various PKCE specs and updated recommendations for Cordova style apps (which fall into the native app category).


conda init tcsh results in:  Illegal variable name.

I ran conda init tcsh and it modified my .tcshrc file, but when I login or source .tcshrc, the mods result in an error:
Illegal variable name.  The offending file is:
/gpfs/u/home/tomas/.tcshrc
and the I believe the  illegal variable error is coming from this line:
__conda_setup="$('/glade/work/tomas/miniconda3/bin/conda' 'shell.tcsh' 'hook' 2> /dev/null)"

As an initial workaround, I think you can remove those lines from your .tcshrc file.
This is a common problem, e.g.
https://github.com/ESMValGroup/ESMValTool/issues/301
I am not sure what the correct solution is, other than switching to bash.

@roberttomas, @matt-long  this is a known issue and there's a fix in the works for the next conda release: https://github.com/conda/conda/pull/8591

I believe conda/conda#8591 addresses different, but related issue to the issue I brought up.  The focus of the discussion at that link is on the lines immediately below the line I pointed to  that resulted in an "Illegal variable name" error message.
__conda_setup="$('/glade/work/tomas/miniconda3/bin/conda' 'shell.tcsh' 'hook' 2> /dev/null)"

for the purposes of the py tutorial next week should we plan on using bash?

@wwieder, I don't think there are any show stoppers with respect to tcsh, it's just that the shell integration is limited. I believe you can still manage environments, etc. just fine. I would suggest, however, that if you don't have compelling reasons not to switch to bash for the long-term, you should switch to bash.

Changes that are supposed to address this issue are included in conda releases >=4.7.4.
It would be great if a tcsh user with a recent version of conda can confirm whether this is still an issue.


Created endpoint for calculating annual income needed during retireme…

closes #241
endpoint for calculating annual income needed during retirement period

i have created main.py and functions.py and added the endpoint on ENDPOINTS.md

Congrats @kharshita590 🎉, your PR got merged! Star this repo to get more awesome swags!


[Snackbar] Shouldn't be light in dark mode

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
In dark mode, snackbar have a white background and a dark color. However, snackbar actions seems to have the same style as if they were not part of a snackbar. This means that disabled actions appears white on a white background.

Expected Behavior 🤔
Disabled snackbar actions should be visible on dark mode.
Steps to Reproduce 🕹
https://codesandbox.io/s/material-ui-issue-forked-9zlxc

Steps:

Configure a custom theme with dark mode enabled
Display a Snackbar with a disabled action

@manufont While I'm tempted to say that we can ignore your issue because if the action is disabled, it shouldn't be shown in the first place in a toast. However, having a closer look at the Material Design guidelines, I believe the snackbar should be dark, not light. At least; it's the behavior I could find on

YouTube
Google Keep

This would also solve the contrast issue with the action button

@manufont While I'm tempted to say that we can ignore your issue because if the action is disabled, it shouldn't be shown in the first place in a toast. However, having a closer look at the Material Design guidelines, I believe the snackbar should be dark, not light. At least; it's the behavior I could find on

YouTube
Google Keep

This would also solve the contrast issue with the action button

Can I work on this?

Can I work on this?

@manufront you could provide a light theme to the button https://codesandbox.io/s/material-ui-issue-forked-ucdv8?file=/src/Demo.js but it would only likely hide the root issue. I would encourage to either customize the button or to not render a disabled one inside the snackbar (what's the use case if it can't be interacted with)?

@manufront you could provide a light theme to the button https://codesandbox.io/s/material-ui-issue-forked-ucdv8?file=/src/Demo.js but it would only likely hide the root issue. I would encourage to either customize the button or to not render a disabled one inside the snackbar (what's the use case if it can't be interacted with)?


Xcode 15.1 isn't available during some runs with macOS 13

Description
Xcode 15.1 is listed as available for macOS 13 but it's not available during some runs
Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[X] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[X] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
https://github.com/maxim-lobanov/setup-xcode/issues/74
Is it regression?
No
Expected behavior
Xcode 15.1 would always be available as listed
Actual behavior
Xcode 15.1 isn't available during some runs so the failed job has to be re-run and hopefully assigned to a runner with 15.1 installed
Repro steps
Use setup-xcode to specify ~15.1.0 and notice that some of the builds fail

Hey, what's the image version ad the build link? Could please you provide those?

All the info in Set up job looks the same when it works and when it doesn't, so here's two examples of it failing multiple times and then finally working
1-6 on this one (attempt 7 finally worked):
https://github.com/awresports/pitchaware-charting-app/actions/runs/7335561426/attempts/6
1-2 on this one (attempt 3 worked):
https://github.com/awresports/awresports-app/actions/runs/7335424009/attempts/2

@daveisfera your repo seems to be private so we do not have access

Sorry, I figured you could look up stuff from private repos.  After a detailed investigation we have found the root cause of the problem. The problem will gone likely after the next release. Thank you for understanding.

Great to hear! Thanks for helping get this resolved

@Alexey-Ayupov can you share what the issue is? That way we may be able to work around it?

Should be fixed now.

@freef4ll it was fixed without making a new release


Implemented Dispose

I implemented dispose in the WebWindow but I am having trouble getting it to work in Windows.
Linux was a complete shot in the dark as I have never worked with C++ let alone on Linux before.
I get
Exception thrown: 'System.EntryPointNotFoundException' in WebWindow.dll
whenever I try to call the dispose method. As far as I can tell I implemented everything correctly, but I am knew to C++ so its very likely I missed something. Any feedback would be greatly appreciated. I also didn't see a WebWindow.Mac.cpp file to make changes too.

I also didn't see a WebWindow.Mac.cpp file to make changes too.

It's WebWindow.Mac.mm.

@ajmcateer Thanks for contributing this!
Do you think you'll be in a position to finish this PR off? That would involve figuring out the solution to whatever issue you're describing, as well as tidy this up to remove the unnecessary changes (e.g., in  WebWindow.Native.vcxproj).
If that's not something you'll get round to, no problem - I may add some functionality like this myself eventually, though there's no ETA.


Fix spatial observer and validate with tests

Overview
WMRObserver had a bug where it would auto-start itself in enable() even when set to manual start.
This change move the functionality to BaseObjectObserver and creates some tests for basic observer functionality.
Changes

Fixes: #6908

Verification

As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run

/azp run

/azp run


Add support for raw moseq outputs

Fixes #50

Currently code fully converts the output of moseq2-extract (See Moseq2 for a breakdown of different depth-moseq pipeline steps).
moseq2-pca output (PCs) and moseq2-model output (syllables) are not supported yet.
Still need to think about how to approach modularity to maximize re-usability for Datta Lab while keeping moseq stuff together in the nwbfile.

Confirmed that there is no easy way to break this DataInterface: it expects exact types by name in the init, can't pass in some arbitrary data field, can't add extra parameters.

Next steps:

Move to a temporally aligned interface, lines https://github.com/catalystneuro/datta-lab-to-nwb/pull/51/files#diff-89a37d11a954b4631ea551537ea0ace0e36f407a0f13f7f18a8ad9d7ca787875R84-R87 then move to the conversion script or converter protocol for temporal alignment

Remove unrelated metadata schema fields: https://github.com/catalystneuro/datta-lab-to-nwb/pull/51/files#diff-89a37d11a954b4631ea551537ea0ace0e36f407a0f13f7f18a8ad9d7ca787875R47-R72

Also

Move ndx-moseq-extract to CatalystNeuro and publish official version when stable


Fail to package and distribute in Windows 10 and Ubuntu 16

Hi Vjekoslav,
Can you please update the project with electron-packager (https://github.com/electron-userland/electron-packager). I cannot package and distribute the project with npm run dist in both Windows 10 and Ubuntu 16. Here is the error message about it:

Error: Build for OS X is supported only on OS X, please see https://github.com/electron-userland/electron-builder/wiki/Multi-Platform-Build

Thank you.

The message is saying it all. You can publish for OSX only from OSX. From
OSX you can publish for all 3 platforms.
On Wed, 24 Aug 2016 at 21:35, Khoa Ho<EMAIL_ADDRESS>wrote:

Hi Vjekoslav,
Can you please update the project with electron-packager (
https://github.com/electron-userland/electron-packager). I cannot package
and distribute the project with npm run dist in both Windows 10 and
Ubuntu 16. Here is the error message about it:
Error: Build for OS X is supported only on OS X, please see
https://github.com/electron-userland/electron-builder/wiki/Multi-Platform-Build
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Vj3k0/ea-todo/issues/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABkQHv2SfAIVpY6wUbeWtNjREA2w7lL-ks5qjJ0XgaJpZM4JsXvE
.

I use electron-packager to test on both Windows 10 and Ubuntu 16:
electron-packager . --platform=all --arch=all
The result is:
Windows 10 has four created packages: linux-ia32, linux-x64, win32-ia32 and win32-x64
Ubuntu 16 has three created packages: linux-ia32, linux-x64 and darwin-x64
So we can use Windows 10 to build packages for Windows and Linux, Ubuntu for Linux and OSX.
I don't have a Mac machine to test.

I've just installed Wine (https://wiki.winehq.org/Ubuntu), then run electron-packager again electron-packager . --platform=all --arch=all in Ubuntu 16. All the packages in Windows, Linux and OSX are created!
eatodo-win32-ia32
eatodo-win32-x64
eatodo-linux-ia32
eatodo-linux-x64
eatodo-darwin-x64
eatodo-mas-x64
The interesting thing is the ia32 and x64 builds from Windows not work on Windows. While the ia32 and x64 builds from Linux works on Windows.
You may update the package.json to add support for electron-packager.
Thank you.

This project is using electron-builder, not packager directly.
On Thu, 25 Aug 2016 at 22:27, Khoa Ho<EMAIL_ADDRESS>wrote:

I've just installed Wine (https://wiki.winehq.org/Ubuntu), then run
electron-packager again electron-packager . --platform=all --arch=all in
Ubuntu 16. All the packages in Windows, Linux and OSX are created!
eatodo-win32-ia32
eatodo-win32-x64
eatodo-linux-ia32
eatodo-linux-x64
eatodo-darwin-x64
eatodo-mas-x64
The interesting thing is the ia32 and x64 builds from Windows not work on
Windows. While the ia32 and x64 builds from Linux works on Windows.
You may update the package.json to add support for electron-packager.
Thank you.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Vj3k0/ea-todo/issues/2#issuecomment-242527048, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABkQHhkb48dt_pfcouJovN6obXegjQxVks5qjfrLgaJpZM4JsXvE
.

It's good to know that we can use both electron-builder and electron-packager to build/package the project.


Auth routes: Bug

Issue: Authorization intercept is not functioning for React router
Observed behavior: Attempting to access a restaurant page when not logged in results in the page loading with no data.
Further, attempting to access the auth page while logged in displays the login / signup pages.
Expected behavior: The pages should be blocked depending on authorization status and appropriately re-routed.
Fix: Check with react-router-dom documentation for solutions as a first step.

Update: This is an issue with upgrading from react-router-dom v3 to v4.
Resources:
https://codeburst.io/react-router-v4-unofficial-migration-guide-5a370b8905a
https://codeburst.io/react-router-v4-unofficial-migration-guide-5a370b8905a


fix: unwanted linebreaks added when translating html blockquote to markdown

Fixed Issues
$ https://github.com/Expensify/App/issues/20725
PROPOSAL: https://github.com/Expensify/App/issues/20725#issuecomment-1590344432
Tests

Go to a chat and add comment

==== Case 1: simple quote ===
> one line quote a

> two line quote b
> two line quote b

> quote c with internal line break
>
> quote c with internal line break

==== Case 2: quote surrounded by text ===
text a
> quote a

> quote b
text b

text c
> quote c
text c

==== Case 3: quote surrounded by inline element ===
_italic a_
> quote a

> quote b
*bold b*

_italic c_
> quote c
*bold c*

Open the comment in editing mode and verify that the initial draft is same as input.
Test copy and pasting
3a. On Web and Desktop, select the comment, copy the selection by Ctr/Cmd + C, paste it to composer and verify that it's same as input
3b. On mobile, long press comment, copy to clipboard, pasting in composer and verify that it's same as input
(Perform step 4-9 on Web only) Open w3schools, add following html and run

<!DOCTYPE html>

==== Case 4A: quote surrounded by block element ===

code fence a

quote a

quote b

code fence b

code fence c

quote c

code fence c

Select and copy html from right hand side of w3schools page and paste it to composer
Verify that the composer input is equal to following input

==== Case 4A: quote surrounded by block element ===
```
code fence a
```
> quote a

> quote b
```
code fence b
```

```
code fence c
```
> quote c
```
code fence c
```

https://github.com/Expensify/App/assets/117511920/12b54ae0-e024-4212-8c49-7a6b11595c33

Repeat Step 4 with following html

<!DOCTYPE html>

==== Case 4B: quote surrounded by block element ===

h1 a

quote a

quote b

h1 b

h1 c

quote c

h1 c

Repeat step 5
Verify that the composer input is equal to following input

==== Case 4B: quote surrounded by block element ===
# h1 a
> quote a

> quote b
# h1 b

# h1 c
> quote c
# h1 c

https://github.com/Expensify/App/assets/117511920/c31728f3-f183-430a-9196-eae236342a32

[x] Verify that no errors appear in the JS console

Offline tests
QA
Same as tests.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/expensify-common/assets/117511920/506663cb-2b32-4d82-ac09-1b3303212e02
https://github.com/Expensify/expensify-common/assets/117511920/972ce5cf-5d38-45c2-b61f-95a7d3b8efab
https://github.com/Expensify/expensify-common/assets/117511920/dc0dd8c2-6992-44e1-9738-8f35cf8ff0e9

Mobile Web - Chrome

https://github.com/Expensify/expensify-common/assets/117511920/fab436c6-4033-4690-836f-bf9c01c3aa79

Mobile Web - Safari

https://github.com/Expensify/expensify-common/assets/117511920/b932ce11-f87f-4723-aa63-6086d9108ce8

Desktop

https://github.com/Expensify/expensify-common/assets/117511920/8f9bb6cc-3f07-4402-b2a7-bd4421677eab

iOS

https://github.com/Expensify/expensify-common/assets/117511920/c151ed5b-f54b-474b-8225-8b1755387ce4

Android

https://github.com/Expensify/expensify-common/assets/117511920/cfe65284-bd67-4401-855d-b081ae1692f9

@eh2077 can you please resolve merge conflicts?

@narefyev91 Updated!

@eh2077 I think your changes were already includes in this merged PR - which happened right after yours https://github.com/Expensify/expensify-common/commit/06a5ff5b0e2f24fe535754eb6b85cec86d157ab2

@narefyev91 No, the hash for this PR is later than than that one.

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/28352309/de748cd6-dc92-4811-94cc-301c114c2df8

Mobile Web - Chrome
https://github.com/Expensify/App/assets/28352309/9b67832a-c8c1-4e79-be75-e1b0a9a0bf97

Mobile Web - Safari
https://github.com/Expensify/App/assets/28352309/95620896-bebb-44db-aa64-1bab0e9c5359

Desktop
https://github.com/Expensify/App/assets/28352309/fea88ba2-d5eb-470c-aeb1-b71621d8d7b9

iOS
https://github.com/Expensify/App/assets/28352309/0f71f8c7-6a68-4e6e-8cc0-4054cfdec5dc

Android
https://github.com/Expensify/App/assets/28352309/a531a329-88f8-445c-a902-00f9e9295564

This is just a library change, where's the actual PR?

@iwiznia The version hash is from this PR https://github.com/Expensify/expensify-common/pull/554
We can find the related PR from the linked issue.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/iwiznia in version: 1.3.38-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.38-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Memory leak in update function

import pyuniprot
pyuniprot.update(taxids=[9606,10090,10116]) # human, mouse, rat
After ~42k entries in the database the update process consumes ~12Gb of memory. I assume a problem in lxml. Found several articles describing similar problems with big XML files. BUT here I avoid to load the whole document in the iterparser (tested is and directly starts with 5Gb of memory consumption and then constantly increases). If the problem won't be solved it seem not feasible to load the whole UniProt.

Found this article <https://benbernardblog.com/tracking-down-a-freaky-python-memory-leak-part-2/>_ recommends to set collect_ids=False like I did.
parser = etree.XMLParser(collect_ids=False)
entries = etree.fromstringlist(entries_xml, parser)
But even this not helps.

I found a workaround:
Reload lxml etree for every chunk of XML entries.
Stupid, but it works and memory usage dramatically is reduced.


BOUNTY: Toastify Notifications

Use the 'Toastify' library to create notifications for users regarding relay health and new events.
The basic functionality for this is mostly implemented and it is mainly a UI/UX task of building unobtrusive and informative notifications in any media device context (desktop, tablet, mobile)
Reward
$100

@42Pupusas, Please assign me?

Sorry for the delay, didn't expect contributors so soon.
Mind sharing how you found the bounty list?

@aliraza556 are you up with the solution?

@42Pupusas can you assign me this issue?

@aliraza556 are you still working on this?
please respond or I will assign this issue to @rahat2134 .
@rahat2134  ive assigned you the other issue you requested. you can start with that one and if aliraza does not respond I will transfer this issue to you.

Hi @42Pupusas, Please assign to @rahat2134.

@rahat2134 great work on this.
please add a BTC address on this thread, I will comment back with the transaction for the bounty reward

Bounty has been paid @rahat2134 !
$100 @ ~$67600 for a total of 0.00147672  BTC
You can check transaction here:
https://mempool.space/tx/2d95aa85d521b5802a0ac5043c4275a8c37e81e188044f7573af654df581fbaa
Hope to see many more contributions from you!


[Feedback Requested] How should the CLI work for v1.0?

One of the biggest changes in v1.0 is that we will be encouraging people to only customize/extend the parts of the default config they'd actually like to change, so they will have a much smaller config file at the end of the day than they do now. We don't want to automatically force people to own all of Tailwind's default config as soon as they create a config file, so the question is:
What should tailwind init actually do in v1.0?
My initial thoughts are that it should create a pretty minimal config file, maybe something like this:
module.exports = {
  theme: {
    // Some useful comment
  },
  variants: {
    // Some useful comment
  },
  plugins: [
    // Some useful comment
  ]
}

...or maybe not even that much.
Some folks have expressed the desire to still scaffold out the entire config like in the 0.x days too, which I think I'm fine with supporting as an option. Maybe a separate tailwind eject command that merges the default config with your existing customizations and writes that out to your config file, with perhaps an --eject flag that you can pass to init to do it from the beginning?

I think that ‘init’ should go away alltogether. Partial scaffolding provides very little value.
‘eject’ should be added but with a different name perhaps. Other frameworks state that ‘eject’ cannot be undone. This is not the case with tailwind. However, i don’t have any ideas for a better name.

It totally makes sense to me to provide an option to eject it. Personally, I like the code snippet above as a minimal config file. Otherwise, you have always to look at the docs to create that, even it's very simple.
I was one of the guys who voted to keep the configuration file. I use it very often as a reference. It is fast and simple. So if that option would be still available, I'd be more than happy.

About the config merging
While this behavior is convenient I feel that it promotes a hidden behavior. A simpler and more powerful approach is to ask users to explicitly spread the default config.
My recommendation is to keep the current behavior for graceful configuration recovery but in all examples use the spread operator.
// tailwind.config.js
const default = require('tailwindcss/defaultConfig')

module.exports = {
  ...default,
  theme: {
    ...default.theme,
    // Some useful comment
  }
}

Consolidate config and theme
When using the above approach there is no need to keep config and theme as separate modules.
init command
The init command would generate the example above at the minimum. Having the spread operators there indicates where to look for available options.
eject should probably be --full
eject as used by other frameworks, indicated unreversible operation. This is not the case with Tailwind.
npx tailwind init --full [filename]

I'm going to be using my custom default config 95% of the time so we definitely need something like --full or eject. I agree with @MattStypa that eject might not be the right term for this.
Also, if we're still going to allow users to extend their config files, maybe we should just have that there instead of spreading the defaults in?

I'd vote for providing an option to generate a default, full config with --full. I can definitely feel for a case where I wanna start off with all the things from Tailwind and remove/modify the things I see there. Doing a minimal config file only would force me to go back and forth to the docs and copy paste config names (blergh).

Something I'd also like to see is a version of tailwind build that supports PurgeCSS (if you have it installed) and maybe the .postcssrc.js file if available.
I'd be 👍 to PR this if you think it'd be useful.

What we have now is pretty good I think, tailwind init for simple config, tailwind init --full for full config.


enable testpackage linter

I do have my concerns over whether this linter is a good idea, but the changes aren't too tricky so we should investigate!
/approve
/lgtm


GUI for MetaCom

Current version of user interface looks like a prototype. It's not ugly, but not good at all. So I propose to try to create new pretty version of GUI based on a current navigation logic. I doubt that we will look for a graphical designer for this project, that's why I can try to do it myself, but only if you, @GYFK, will approve this task.

@GreatAndPowerfulKing No we do not need special design for this app, we need just simple GUI with common platform guidelines, default controls and nothing custom.

@tshemsedinov Okay.

@metarhia/ios We need good UX and UI but I do not believe in designers. They are drawing custom an never use theirs own UI, so I think developers can do it better.

@tshemsedinov I'm not proposing to create all new custom controls and interfaces. Just to add maybe few colors and some background. For example, replace this:

with something like this (just example):

I suppose it's a common and easy way to make app looks better and more user-friendly, but using default controls.

@GreatAndPowerfulKing although I don't fully agree with the last @tshemsedinov's statement (but I see where he's coming from and what's his motivation to say so), regarding your example... well, in my opinion, the first screenshot definitely looks more beautiful 😄

@GreatAndPowerfulKing though I do apprehend that it may be just a not well-turned example, and you have my +1 for using colors and solid or simple geometric backgrounds.

@aqrln I completely agree with you that the first screenshot looks more clear, but the second is just hot midnight example 😅.

Don't turn an app into svistoperdelka, how it would be in English

@tshemsedinov it's "bells and whistles" in English, fwiw ;)


Default toolchain

Feature Description
By default the predefined rules in https://github.com/sagiegurari/cargo-make/tree/master/src/lib/descriptor/makefiles use the native cargo command.  In order to get them to use a toolchain, I have to write a bunch of extend task like
[tasks.build]
toolchain = "stable"

It would be nice to be able to force a default toolchain for all tasks.
Describe The Solution You'd Like
Something like:
[config]
default-toolchain = "stable"

ya i can take a look at that

Or perhaps
[env]
CARGO_MAKE_RUST_CHANNEL = "stable"

its obviously will be an environment variable and not a new config

@jayvdb this is now implemented in the dev branch: 0.36.3
can you please try it out and check if it works well for you?
you will see to set the following env var: CARGO_MAKE_RUST_DEFAULT_TOOLCHAIN to the value you need (default is empty and ignored)

wfm, thanks!


Translate from german to english #153

translating from german to english from line 126 in file crib-cheat_git.md

This pull request wants to merge into master. Please change it to dev.

@JohannesBru wie kann man Pull Request von Master zu Dev wechseln ?

@Rahmandityo You can Edit your PR. In this page at the top on right side -> Klick on "Edit" -> on top under the PR title you can change the "base" from dev to master

got it, thx!! @JohannesBru

I resolved a few conflicts and now the feature branch is reade to be merged. I will merge it into dev


Cms/blogs/try again what in the ml is going on around here

Description
Blog PR, Draft 1
Issues Resolved
#2001
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Thanks for your help Nate. I'll make a few changes and then let you have at it.

@nateynateynate @dtaivpp - This is ready to post once the date and meta is updated. Let's get this shipped today, please.


Offline model support

Hello,
To support information protection, I suggest to try to have a local GPT model helping parsing a UI page. For that, using LLAMA 3 could be good enough.
I can try to work around it, but I suggest first to speak about it.
A project Iv'e used to load pre-defined model is: https://github.com/Formartha/ai1899
I would appreciate your inputs.

Hi @Formartha - LaVague is made to be customizable so you can swap out any of our default models for any LlamaIndex compatible models you want, so you can use local models.
There is some information on how to do this here:
Does that help? Feel free to share your local config on our Discord!

Hi @Formartha,
Just to add an example - you could try with any HF LLM - performance will vary but feel free to test different models and let us know how you get on:
from lavague.drivers.selenium import SeleniumDriver
from lavague.core import ActionEngine, WorldModel
from lavague.core.agents import WebAgent
from lavague.core.logger import AgentLogger
from llama_index.embeddings.huggingface import HuggingFaceEmbedding
from llama_index.llms.huggingface import HuggingFaceLLM

driver = SeleniumDriver(headless=True)

llm = HuggingFaceLLM(model_name="deepseek-ai/deepseek-coder-6.7b-instruct")
embedding = HuggingFaceEmbedding(
    model_name="BAAI/bge-small-en-v1.5"
)

action_engine = ActionEngine(driver=driver, llm=llm, embedding=embedding)
world_model = WorldModel()

agent = WebAgent(world_model, action_engine)

agent.get("https://huggingface.co/")
agent.run("what is the top model")

Here I use a local embedder and LLM. I still use OpenAI for the multi-modal LLM used by the World Model though because I am not aware of an open source alternative working well at the moment - we're working on this!

Will close for now as no new activity on this one for a while. Feel free to re-open or ping us if you want to discuss this further @Formartha


Sample Powershell script needs updating

This article has just saved me a lot of effort thanks :)
However, I think there's an issue with the PowerShell scripts to add/remove the firewall rules, according to the docs, -FireWallRuleName should be RuleName and -ResourceGroupName is unnecessary in each of the function calls:

  Get-AzureSqlDatabaseServerFirewallRule

  New-AzureSqlDatabaseServerFirewallRule

  Set-AzureSqlDatabaseServerFirewallRule

  Remove-AzureSqlDatabaseServerFirewallRule

-FirewallRuleName $FirewallRuleName -ResourceGroupName $ResourceGroupName
should actually be:
-RuleName $FirewallRuleName -ResourceGroupName $ResourceGroupName
Ref:
https://learn.microsoft.com/en-us/powershell/module/servicemanagement/azure.service/new-azuresqldatabaseserverfirewallrule?view=azuresmps-4.0.0
https://learn.microsoft.com/en-us/powershell/module/servicemanagement/azure.service/set-azuresqldatabaseserverfirewallrule?view=azuresmps-4.0.0
etc.

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

ID: 81f4ee44-6500-b0e6-62d8-7a23e5b461fa
Version Independent ID: 75bd021b-fed5-f258-315d-0ef8628fb887
Content: Deploy to Azure SQL Database - Azure Pipelines
Content Source: docs/pipelines/targets/azure-sqldb.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-targets
GitHub Login: @ramiMSFT
Microsoft Alias: rabououn

@PhilEmpyrean Thank you for the great feedback!


Service Start / Stop issue.

when I start an driver with processhacker. I can't see stop option untill I restart Processhacker.
this bug exist since a year. do you have any plan to fix this?

Try changing the EnableServiceNonPoll setting to 1 or 0.
If it's 1, try 0 and if it's 0 try 1


release 2.0.0

Verified.
v2.0.0-rc2 was successfully released. and it can be checked from https://github.com/threefoldtech/tfgrid-sdk-ts/releases


build: Add git reference printing.

I'm working to add target determination so we only build what's changed on pull requests. In order to do that, I need to know what references are available on PRs. It's especially confusing because I need to know what the build system sees on forks. This commit adds a reference printing so I can see what PRs have available today.

TL;DR - I'm going to rebase existing PRs off of this change to ensure I get this right before enabling it


Email slurping

We gather emails from a wide number of sources:

meetup.com
eventbrite signups
members
mailing lists
newsletter subscribers
various online forms, such as donations etc.

It would be very handy to have MM be the thing that centrally captures all these emails so that we can export a managed list for email marketting. This would also allow us to track conversion, ie people who come in for a tour or event. Another thing it would enable us to do is provide a 'newsletter only', or community access (ie forums,discord) membership level ($5/m sort of thing).

Sounds like a great idea to finally get our mailing list(s) under control. I'm not entirely sure what needs to be implemented though so just want to confirm what you'd like to see.
Are you thinking MM should use the API for each of those services to pull in a list of all email addresses? Or something else?

Api usage would be obviously the best practice, but maybe a long term goal? I think eventbrite will be easy enough, and meetup we will probably retire soon. The mailing list stuff is old/static. The online forms I think are managed with jotform so theres probably an api there.
A very short term approach might be csv import and support for a member type that is kind of, email data only? And perhaps some way to put a text field on the website to capture peoples emails that can be put through that same funnel. (things like mailchimp do this for you, but i'm thinking the path of the data goes via the portal)

Right ok cool that makes sense. So it's just some way of being able to import all of the email addresses we have on various systems into one system (MM). Then MM becomes the source of truth for our mailing list(s).
I think the best way to achieve this while balancing complexity and time, would be to have a manual import process. Essentially you'd be able to import a CSV of names/emails into the system. Then the system can generate an up to date mailing list whenever we need one (or can send it straight to mailchimp on a regular basis).
This means both our member emails, and the emails from all of our other sources will be collected and managed in one place. I'm thinking basically another page with a table (like the member list) that will have a combined list of all emails in the system, with the option to remove specific ones (that aren't members) or to "mute" them - ie remove then from any mailing list export.

Sounds good. Data model wise i would treat them all as another type of 'member', rather than its own table of emails. if you look at other similar member management systems, like tidyclub etc, their data model is to have 'contacts' and contacts can have active memberships etc. Same thing here. atm we have active / inactive / new, when what we probably want is a flow something like contact > new > active / paused / banned / expired / cancelled
In the end, yes, MM should be a source of truth regarding our data, and that data includes the emails of everyone we interact with.

Yeah I'll be updating the member state system when I implement the automatic payments in #9. Since Stripe will be keeping track and deciding if someone is active or not, I'll do something like separate the access system state (which is linked to Stripe) and add a new property which is member type.


Added UTF-8 support in corpus

Diacritics did not work with Croatian corpus and I think it should help with other languages as well. I am planning to create a pull request for Croatian corpus as well these days.

Looks good :+1:


Remove Fedora 22 from RPM build as it is EOL

Fedora 22 reached end of life on July 19th, and
will no longer receive updates;
https://fedoramagazine.org/fedora-22-end-of-life-2016-july/
With the recent release of Fedora 24, Fedora 22 will officially enter End Of
Life (EOL) status on July 19th, 2016. After July 19th, all packages in the
Fedora 22 repositories will no longer receive security, bugfix, or enhancement
updates, and no new packages will be added to the Fedora 22 collection.
Upgrading to Fedora 23 or Fedora 24 before July 19th 2016 is highly recommended
for all users still running Fedora 22.
ping @runcom ptal

LGTM :)


dockerfiles: upgrade to ubuntu:20.04

Polkadot companion: https://github.com/paritytech/polkadot/pull/3828
I'm upgrading the CI image from being based on debian:buster to ubuntu:20.04, some details: https://github.com/paritytech/scripts/pull/309
The binaries produced in our new CI image will be linked by the newer GLIBC so won't be executable in debian:
/usr/local/bin/adder-collator: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /usr/local/bin/adder-collator)
/usr/local/bin/adder-collator: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by /usr/local/bin/adder-collator)

@chevdor I wanted to ask you about https://github.com/paritytech/substrate/blob/master/.maintain/Dockerfile

is it still used?
if yes, it should follow our containers policy and use ubuntu:20.04 as base
and have some metadata as the other images do

is it still used?

Yes, and it is critical to keep it.

if yes, it should follow our containers policy and use ubuntu:20.04 as base

I see no issue with that. Do you want to include that in the PR? If not, please open an issue and I will take care of it.

and have some metadata as the other images do

100%


Endpoint for batch tokenization in core

We should have a batch end point for tokenization that we can use here:
https://github.com/dust-tt/dust/blob/656576bff4220b84a68099c5e926ec42949c83e6/front/lib/api/assistant/generation.ts#L172-L194

Moved to Olympus!

So after digging a bit, all our tokenizers are singletons behind a RW lock. So unless we accept to change that, we wouldn't get much from a batch endpoint since everything will continue to be sequential.
@spolu Is there a strong reason to have a lock on the tokenizers ?

The RW lock is used in read mode for tokenization and therefore allow for parallelization within core, additionally this would save the N connections + Promise.all which would overall be much more efficient :+1:

Thanks @spolu


feat(tools): add docker testing tool for Hyperledger Iroha

Is your feature request related to a problem? Please describe.
In order to develop LedgerPlugin for Hyperledger Iroha, docker testing tool of Hyperledger Iroha is neccesary on /tools/docker .
Describe the solution you'd like
To provide docker testing tool for Hyperledger Iroha.

This issue was resolved by #980 .


pwsh-preview no work

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
When I run pwsh-preview, i get this message: pwsh-preview: The term 'pwsh-preview' is not recognized as a name of a cmdlet, function, script file, or executable program.

According to this, this is the method of starting a session of Powershell Preview:
pwsh-preview
When I use only pwsh, I got the 7.3.4 version:

So, I have to add something to my path (what path?)
Why was it not added on install (from the Microsoft Store)?
Expected behavior
Start Windows PowerShell Preview

Actual behavior
pwsh-preview: The term 'pwsh-preview' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Error details
No response
Environment data
Name                           Value
----                           -----
PSVersion                      7.4.0-preview.3
PSEdition                      Core
GitCommitId                    7.4.0-preview.3
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

reinstall pwsh-preview， and choose add path varible
or
$env:path = $env:path + ‘;C:\Program Files\PowerShell\7-preview;’

reinstall pwsh-preview， and choose add path varible or $env:path = $env:path + ‘;C:\Program Files\PowerShell\7-preview;’

Hello, I use Windows and I did not see that option when installing from the Windows Store

I'm not running the current ones but all the previous ones have kept the executable name as PWSH.
The preview doesn't put itself on the path - that way the released version runs by default,  and the full path to the preview should be used.

You would have to uninstall in the Settings of Windows under Apps > Installed apps and remove it that way and then you can reinstall via the store or GitHub.

This is a limitation with the MSIX package, we will explore ways to improve this so you have pwsh-preview in the path.


Manual commit takes long

Description
I am commiting every single message manually & synchronous, meaning next message will be consumed after previously finished commit. How ever when I synchronously publish a message it takes 95ms. So issue is that synchronous commit takes 1036 ms while synchronous publish takes 95 ms. How can I make commits as fast as publishes?
Maybe there is an issue with my configuration? Please, suggest what could be wrong. Thanks!
Update
I have tried on a different topic and with freshly created topic it works flawlessly, maybe you can suggest what could cause the problem in the settings of the topic?
How to reproduce
Create a new consumer on each message received perform CommitAsync in a synchronous fashion. Blocking of Commit will take something close to 1036 ms.
Checklist
Please provide the following information:

[x] Confluent.Kafka nuget version: 0.11.1
[x] Apache Kafka version: 0.10
[x] Client configuration:

<add key="group.id" value="Consumer" />
<add key="bootstrap.servers" value="hosts" />
<add key="socket.blocking.max.ms" value="1" />
<add key="enable.auto.commit" value="false" />

[x] Operating system: Win7x64
[ ] Provide logs (with "debug" : "..." as necessary in configuration): There are no logs related to it.
[ ] Provide broker log excepts: There are no logs related to it.
[ ] Critical issue

librdkafka will use the same broker connection both for commits and fetching messages, thus a commit may be backed up behind a long-poll blocking Fetch request.
The long-poll behaviour of fetch requests is configured with the fetch.wait.max.ms property that defaults to 100ms. You can decrease that value to decrease offset commit latency at the expense of a larger number of Fetch requests (depending on your traffic pattern).
To see the latency of each request you can enable debug=protocol and look at the rtt (round-trip-time) printout of OffsetCommit and Fetch requests.

@edenhill Thank you so much for getting back to me! I will try to apply these configuration properties when I get back to work.
Say, could that be the case even if one topic allows you to commit within 100 ms range while another topic performs same task 10x slower (1s)?

this is the same issue as #433 and https://github.com/edenhill/librdkafka/issues/1787 . closing in favor of those.


2221-Fides: Update cypress tests to reflect nav 2.0

Closes #2221
Code Changes

Updated admin-ui cypress tests to reflect the navbar 2.0 navigation.

Steps to Confirm

Execute cy:start via Terminal prompt (fides > clients > admin-ui directory)

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation:

[ ] documentation complete, PR opened in fidesdocs
[ ] documentation issue created in fidesdocs

[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[x] Update CHANGELOG.md

Description Of Changes
Write some things here about the changes and any potential caveats

Thanks for this - I've made the same changes and incorporated @allisonking's feedback alongside retiring the dynamic nav code in a follow-up PR here: https://github.com/ethyca/fides/pull/2762
Closing this one in favour of that


Add test suite

Test suite setup with Bats
Assertion library courtesy of the very well done bats-assert

Fixtures
I've set up a few fixtures, based on some tricky cases.
# creating a fixture file:
git --no-pager diff .  > fixture.diff
# running it directly:
cat fixture.diff | ./diff-so-fancy

Assertions
The basics look like this:
output=$( load_fixture "ls-function" | $diff_so_fancy )

@test "that it doesnt break" {
  assert_output --partial "diff: "
  refute_output --partial "index 33c3d8b"
}

Between bats and bats-assert there is indended to be support for something like assert_line --index 7 to define specific lines of output`, however I was unable to make that work. I believe its a bug between empty text lines and the escape codes.
CI
This is setup with CircleCI, which works great. The Travis bots are crazy slow for me (though it does work), so I'd prefer being on CircleCI for now.

https://circleci.com/gh/paulirish/diff-so-fancy
Fixes #32

:tada: Thanks @paulirish , This is so great!
Do I need to enable the hook to make CI work?

@stevemao no you just need to signup with CircleCI and the permissions you grant them will take care of it.

i'd be a fan of merging this earlier than later. shall we?


[N4S] RULE add isBetween/isInRange

Add a new enforce rule:
enforce(5).isBetween(0, 5) // ✅
enforce(5).isBetween(0, 10) // ✅
enforce(5).isBetween(0, 2) // 🚨

I would liket o take this one

Cool. Go ahead. I think it could easily be a function using lte and gte.