Longs URL aren't matched. (Greater than 4096 Bytes)

Urls bigger that 4096 Bytes won't be matched, because in org.mockserver.server.unification.PortUnificationHandler#switchToHttp the HttpServerCodec uses the default constructor which is 4096.
I'm currently using MockServerRule and after debugging I see the following error
An HTTP line is larger than 4096 bytes.
I cloned mockserver an changed PortUnificationHandler locally to test if by increasing the maxInitialLineLength the url would be matched or not, and it does work.
The change looks as follows:
 private void switchToHttp(ChanelHandlerContext ctx, ByteBuf msg) {
        ChannelPipeline pipeline = ctx.pipeline();
        addLastIfNotPresent(pipeline, new HttpServerCodec(8192, 8192, 8192));
        addLastIfNotPresent(pipeline, new HttpContentDecompressor());
        addLastIfNotPresent(pipeline, new HttpContentLengthRemover());
        addLastIfNotPresent(pipeline, new HttpObjectAggregator(Integer.MAX_VALUE));
        if (logger.isDebugEnabled()) {
            addLastIfNotPresent(pipeline, new LoggingHandler());
        }
        configurePipeline(ctx, pipeline);
        pipeline.remove(this);
        // fire message back through pipeline
        ctx.fireChannelRead(msg);
    }

I came with 2 possible solutions:

Overload the constructor org.mockserver.junit.MockServerRule and take another parameter that could be Property object which it could be use to set the desired values.

Read properties from the system, something like
System.getProperty("netty.httpservercodec.maxInitialLineLength")
That would mean the person using mockserver, would have to set those properties before starting mockserver.

I'm not sure if those are valid solutions at all.
Could anyone help me?

Both of those solutions sounds sensible, another option would also be just to increase the default maximum.  When I get a chance I'll took into implementing increasing the default maximum and possible also the system property option.

Ok thanks for the Feedback.

Sorry for the delay, but this has now been fixed and will be available in the next release, or the current SNAPSHOT version.


[nrf fromlist] mcumgr/img_mgmt: Fix passing bool where pointer is exp…

…ected
The zcbor_bool_encode, in os_mgmt_bootloader_info, has been passed bool value instead of expected pointer.
Upstream PR: https://github.com/zephyrproject-rtos/zephyr/pull/71831

@nvlsianpu ping


Improve API for handling the same event from multiple contracts

For example if the same contract interface is deployed multiple times.

Duplicate of #4 in graphprotocol/specs#4


Various improvements

Pick and choose.

CBlock should not check anything, it is a data structure. Validation logic does not belong in data structures.

Difference of opinion :). I find Bitcoin Core's general design of "everything is a dumb data structure and all the actual logic goes in main.cpp so its all in one place" to be annoying :p

Well validation logic obviously has to be split up and modularized further
and not remain all in main.cpp.

In any case, a TODO is not the place to suggest a significant design
change. That's confusing to people reading it who may want to pick it up.


open_dataset uses cftime, not datetime64, when calendar attribute is "Gregorian"

What happened:
I used xarray.open_dataset to open a NetCDF file whose time coordinate had the calendar attribute set to Gregorian. All dates were within the Timestamp-valid range.
The resulting dataset represented the time co-ordinate as a
cftime._cftime.DatetimeGregorian.
What you expected to happen:
I expected the dataset to represent the time co-ordinate as a datetime64[ns], as documented here and here.
Minimal Complete Verifiable Example:
import xarray as xr
import numpy as np
import pandas as pd

def print_time_type(dataset):
    print(dataset.time.dtype, type(dataset.time[0].item()))

da = xr.DataArray(
    data=[32, 16, 8],
    dims=["time"],
    coords=dict(
        time=pd.date_range("2014-09-06", periods=3),
        reference_time=pd.Timestamp("2014-09-05"),
    ),
)

# Create dataset and confirm type of time
ds1 = xr.Dataset({"myvar": da})
print_time_type(ds1)  # prints "datetime64[ns]" <class 'int'>

# Manually set time attributes to "Gregorian" rather
# than default "proleptic_gregorian".
ds1.time.encoding["calendar"] = "Gregorian"
ds1.reference_time.encoding["calendar"] = "Gregorian"
ds1.to_netcdf("test-capitalized.nc")

ds2 = xr.open_dataset("test-capitalized.nc")
print_time_type(ds2)
# prints "object <class 'cftime._cftime.DatetimeGregorian'>"

# Workaround: add "Gregorian" to list of standard calendars.
xr.coding.times._STANDARD_CALENDARS.add("Gregorian")
ds3 = xr.open_dataset("test-capitalized.nc")
print_time_type(ds3)  # prints "datetime64[ns]" <class 'int'>

Anything else we need to know?:
The documentation for the use_cftime parameter of open_dataset says:

If None (default), attempt to decode times to np.datetime64[ns] objects; if this is not possible, decode times to cftime.datetime objects.

In practice, we are getting some cftime.datetimes even for times which are interpretable and representable as np.datetime64[ns]s. In particular, we have some NetCDF files in which the time variable has a calendar attribute with a value of Gregorian (with a capital ‘G’). CF conventions allow this:

When this standard defines string attributes that may take various prescribed values, the possible values are generally given in lower case. However, applications programs should not be sensitive to case in these attributes.

However, xarray regards Gregorian as a non-standard calendar and falls back to cftime.datetime. If (as in the example) Gregorian is added to xr.coding.times._STANDARD_CALENDARS, the times are read as np.datetime64[ns]s.
Suggested fix: in xarray.coding.times._decode_datetime_with_pandas, change ‘if calendar not in _STANDARD_CALENDARS:’ to ‘if calendar.lower() not in _STANDARD_CALENDARS:’.
  I totally agree we should be able to handle this.  It would be great if you could put together a PR with a fix and some added test coverage.
My only suggestion would be to implement your fix at a higher level in the call stack, e.g. by converting the input calendar to lowercase within xarray.coding.times.decode_cf_datetime before using it anywhere else.  I think this may be cleaner since we do similar checks to the one in _decode_datetime_with_pandas in other places, e.g. here.

Thank you very much for the swift fix -- I had been meaning to put a PR together but things have been very busy lately.


Added "Django Macros URL"

Django Macros URL
As alternative you can use (Django Macros URL)[https://github.com/phpdude/django-macros-url] for building your urls.py files. Django Macros URL makes it easy to read and write patterns without using regular expressions for standard patterns.

Hi, I built amazing django helper library and want to write about it in your guide. Is it possible?
Best Regards,
Alexandr Shurigin.

ping :)


Fix idempotency on service and provider state

Added a return false if already enabled in the provider and a guard to a ruby_block resource to avoid restarting the service at each chef run.

Thank you Tensibai.  Apologies for the delay.

You're welcome, I even had forget this PR ;)


Update ecs-deployment-tutorial.md

add camel case distinction
add JSON for scalable target and scalable policy
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: added camel case distinction, added JSON for scalable target and scalable policy
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66ce5b2e401f1ca9b9b7aa9d--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66ce6d2988b5caba24b43842--harness-developer.netlify.app


qemu://session?

I don't want to run VMs as root, one would think naturally. When I specify the user socket I get:
2017/12/01 18:53:19 failed to connect: internal error: unexpected QEMU URI path '/system', try qemu:///session

So I searched through the code for system but I could not find anything that would be obvious that I could change to session. Any guidance on this topic would be appreciated for both this library and the qemu one you maintain. If this a repeat I apologize, but I did look through the issues of both libraries and did not see anything that was obviously relevant.

Hi @lostinblue, this may help: https://libvirt.org/uri.html#URI_qemu
What is the full connection URI you are using?

I have been studying that page and have not had luck unfortunately.
I have tried qemu for the network and session for the address but that had failure. So I tried using the socket, by doing unix network and using /run/user/1000/libvirt/libvirt-sock as the address which generated this error. I tried also libvirtd as the network which has the same failure as qemu as the network. So I'm not sure if the URI page is helpful unfortunately. Thanks for the quick response.

Oh I got it working with the libvirt/libvirt-go package but I would rather use a pure go implementation. I'm guessing its somehow hardcoded to use the root system QEMU path which seems like an odd choice because of potential VM breakouts leading to full root access of the hypervisor.

Can you give me the exact connection URI you're using, even better a sample piece of code that's failing?

Thanks for taking time to help me out with this issue, I would really like to use and contribute to this library.
So I'm using the very basic example code:
package main

import (
	"fmt"
	"log"
	"net"
	"time"

	"github.com/digitalocean/go-libvirt"
)

func main() {
	//c, err := net.DialTimeout("tcp", "<IP_ADDRESS>:16509", 2*time.Second)
	//c, err := net.DialTimeout("tcp", "<IP_ADDRESS>:16509", 2*time.Second)
	c, err := net.DialTimeout("unix", "session", 2*time.Second)
	if err != nil {
		log.Fatalf("failed to dial libvirt: %v", err)
	}

	l := libvirt.New(c)
	if err := l.Connect(); err != nil {
		log.Fatalf("failed to connect: %v", err)
	}

	v, err := l.Version()
	if err != nil {
		log.Fatalf("failed to retrieve libvirt version: %v", err)
	}
	fmt.Println("Version:", v)

	domains, err := l.Domains()
	if err != nil {
		log.Fatalf("failed to retrieve domains: %v", err)
	}

	fmt.Println("ID\tName\t\tUUID")
	fmt.Printf("--------------------------------------------------------\n")
	for _, d := range domains {
		fmt.Printf("%d\t%s\t%x\n", d.ID, d.Name, d.UUID)
	}

	if err := l.Disconnect(); err != nil {
		log.Fatal("failed to disconnect: %v", err)
	}
}

Example 1
c, err := net.DialTimeout("unix", "/var/run/libvirt/libvirt-sock", 2*time.Second)
2017/12/02 22:59:43 failed to connect: authentication required
Example 2
c, err := net.DialTimeout("unix", "/run/user/1000/libvirt/libvirt-sock", 2*time.Second)
2017/12/02 23:01:35 failed to connect: internal error: unexpected QEMU URI path '/system', try qemu:///session
So I tried both unix sockets. I tried every variation of using qemu://session I could think of.

Dialing "qmp", or "qemu" will never work. unix, tcp, tcp6, etc.. are the only valid network identifiers. As for the socket or tcp authentication methods, you'll want to take a look at your libvirtd configuration, specifically under the sections "UNIX socket access controls" and "Authentication".

Would you accept a pull request where I make this a configurable option? We need session not system

Yes, it would be good to address this.


Wrong labels of Tox21 dataset

Hello,
I found there are some problems with the labels in Tox21 dataset. There are nan and more than one 1 values  in the one-hot labels. This issue can be reproduced  by the following code:
from subgcon.efficient_dataset import GraphSubgraphDataset
dataset = GraphSubgraphDataset('tox21', 'args.sb', 'args.tag_data_path', num_classes=12, few_shot=False)
print(dataset.dataset[7820].y)

I downloaded the data from this link https://huggingface.co/datasets/zkchen/tsgfm/blob/main/minilmdata.zip.

Hi, moleculeNet dataset do have nan labels. The label is not one-hot but multiple binary values. You need to filter those abnormal values

Thank you for the clarification!


Transition   Functional comp causes error in Jest tests: Cannot read property '_isDestroyed' of undefined

Version
2.6.10
Reproduction link
https://github.com/Akryum/vue-issue-test-transition-functional
Steps to reproduce
Using a <transition> on a stubbed functional component is throwing an error during the unit tests with Jest (using shallowMount).
Examples: Component | Test
In the reprod, run:
yarn install
yarn run test:unit

What is expected?
No error in the console
What is actually happening?
The tests pass but an error is displayed in the console:
[Vue warn]: Error in nextTick: "TypeError: Cannot read property '_isDestroyed' of undefined"

Position of the error

Not sure if this should be fixed in Vue core or Vue test utils.
In Vue core, a quick fix would be to check if componentInstance is defined on the vnode here.

Note: workaround is manually stubbing the functional component in the test. This makes the error disappear.

@eddyerburgh maybe you know where this comes from 🙂

Getting this error in the production environment
Difficult to debug as in happens only on Static version of the site.

We see this in static site generated by Nuxt.js. This only happens on page refresh.

Happening on my side with Jest test when I use provide/inject and render function instead of template :(


401 on twitter API when logging in

Hey I'm using this library with nextjs and have this configuration for twitter the dialogue for Login shows and when I authorize APP it sends an API request to
https://cors.bridged.cc/https://api.twitter.com/2/oauth2/token
this API fails with 401. Any idea what I'm doing wrong or is it something from the library?

The code is here:
<LoginSocialTwitter
        redirect_uri={REDIRECT_URI}
        client_id={process.env.TWITTER_CLIENT_ID}
        onResolve={({ provider, data }) => {
          console.log(provider, data, "Twitter Data");
        }}
        onReject={(err) => {
          console.log(err);
        }}
      >

          <svg
            xmlns="http://www.w3.org/2000/svg"
            width="23"
            height="23"
            viewBox="0 0 23 23"
            fill="none"
          >
            <path
              d="M22.1466 4.03046C21.3329 4.40106 20.4567 4.65159 19.5377 4.76353C20.4761 4.18773 21.1964 3.27454 21.5357 2.18695C20.6569 2.72019 19.6859 3.1081 18.6485 3.31607C17.8218 2.41101 16.6401 1.84576 15.3325 1.84576C12.8249 1.84576 10.7906 3.93184 10.7906 6.50461C10.7906 6.86985 10.8295 7.22436 10.9075 7.56572C7.13161 7.37091 3.78441 5.51806 1.54193 2.69615C1.15074 3.38666 0.927028 4.18773 0.927028 5.04088C0.927028 6.65652 1.72914 8.0827 2.94839 8.91855C2.20494 8.89588 1.50283 8.68394 0.88931 8.33738V8.39465C0.88931 10.6527 2.45564 12.5362 4.53548 12.9628C4.15467 13.0722 3.75292 13.1269 3.3382 13.1269C3.0458 13.1269 2.7598 13.0988 2.4828 13.0442C3.0612 14.8944 4.73809 16.242 6.72692 16.278C5.17219 17.5284 3.21207 18.2734 1.08413 18.2734C0.717504 18.2734 0.354859 18.2522 0 18.2094C2.01098 19.529 4.40018 20.3009 6.96482 20.3009C15.3231 20.3009 19.8922 13.2026 19.8922 7.04563C19.8922 6.84303 19.8882 6.64043 19.8804 6.4418C20.7687 5.78468 21.5395 4.96492 22.1466 4.03046Z"
              fill="#00AAEC"
            />
          </svg>

            Continue with Twitter

      </LoginSocialTwitter>

My blind guess is the token used in x-cors-grida-api-key is expired.

ok. let me check for you.

My blind guess is the token used in x-cors-grida-api-key is expired.
Oh. I don't think so. you can try it at https://react-social-login.netlify.app. It still works normally.

Btw, one solution for you is passing the props isOnlyGetCode to the component and sending the code response to the server side, and then getting access_token from it.

But I want full profile from twitter. I tried on production by using the same code but it takes forever to redirect back to website after I authorize it from twitter. Any workaround for that or any idea what's happening?

Oh. I don't think so. you can try it at https://react-social-login.netlify.app. It still works normally.
Yes it is but that's using isOnlyGetCode option, what to do in case of full profile, I can see you have written a getProfile for it in library, and Its giving 401 locally and on prod I explained what's happening.

could you give me your link website? and make sure redirect_uri should be window.location.href

https://www.taltol.com/login Website
https://github.com/The-GigaDevs/Taltol/blob/faisal_integrations/components/auth/SocialLogins.jsx The component

Seem it still works normally

Are you testing twitter?

After researching, I think you need to make a little bit of change to your twitter app config.
Please follow this: https://stackoverflow.com/a/72534686
Let me know if it still doesn't work.

It works now. Adding screenshot for future references. Thanks @cuongdevjs.
Also I want to ask something regarding Linkedin too, how do I get email of Linkedin user & image? It provide weird data like you can see in your own screenshot above

I am never try but you can try passing props scope = r_basicprofile r_emailaddress

This problem has been resolved

Hi, I have the same configuration but do not get any data from Twitter
  <LoginSocialTwitter
    client_id={process.env.TWITTER_CLIENT_ID}
    redirect_uri={REDIRECT_URI}
    onResolve={({ provider, data }: IResolveParams) => {
      console.log(provider, data, "Twitter Data");
    }}
    onReject={(err: any) => {
      console.log(err);
    }}
  >
    <TwitterLoginButton />
  </LoginSocialTwitter>

What is response you get and what status code you are getting?


update au/tasmania source

Closes #1457
AU/Tasmania addresses are provided in a single state wide file.
Although we already have au/countrywide, it's still useful to have both in OA I think.

address ranges appear as 84.0-86 since they are stored as real's not integers in the source data. Is there any way to fix this?

Not without modifications to the OA machine.  It appears that when a single value is available, the conversion from real to integer is supported but not when the format function is used.  I'll take a look.

When number consists entirely of, say, 349.0, this line removes the .0 suffix when performing final normalization.  Unfortunately, when the format function has a field value ending with .0 but other field values follow, no normalization is performed.  This shouldn't be a big deal to fix.

Submitted a PR to the machine.  Hopefully this will be live in the next day or two.

Fixed in the machine, should be available within a day or two for source processing.

DO NOT MERGE, processing was accidental, waiting on openaddresses/machine#649 to be deployed.

Re-run this please

Thanks @trescube for your effort in changing machine to fix the issue here! Looks good to me, merge away.
Hopefully in the future there will be tools/reporting from OA to see a diff of regions doubled up (eg. au/tasmania and au/countrywide), and to get a combined dataset without the duplicates.


Cannot reblog Friendica posts

I use AndStatus with my Friendica account. On my Friendica account, I import the remote Twitter timeline. Reblogging a post on Friendica triggers a Retweet also on Twitter, but when I selecct Reblog on AndStatus, nothing happens at all.
Please help me debug this as I'm inexperienced.

I guess that there is an incompatibility in the API. I experienced something similar with Twidere and Friendica as well. I have to have a look at Friendica's API, but hadn't got time by now.
Could you open an issue at Friendica for that so that we don't forget about it?

I think you could phrase it better than I did :)

Since I'm having some problems with AndStatus on my device (I'm not sure, if my phone isn't powerful enough or my Friendica account makes too much traffic for Andstatus) so it would be good if you would create the issue since you then should make the final test.


GetPushName

Hello, is it possible to get the PushName of the contact?

This function is not yet implemented into the api. Whatsapp sends a contacts message immediatly after the connection was established. We would need to store all contacts and then provide a function to search them.

You can now get the contact from wac.Store.Contacts[jid]. The function, that retrieve the updated contacts from the server is already implemented, but it does not update the contacts in the store yet.

Ola, perfect worked perfectly.


Add handling for starting local HTTP golang serve for development

Added a flag -s to serve the local www folder with net/http in golang. This removes the need for the python run.sh SimpleHTTPServer.

Very cool! Thank you for the contribution :v:


Do not warn when selecting a text with comma

When a text with comma is selected, the ember-cli-page-object produces a warning. Example:
// <fieldset>
//  <button>Lorem, Ipsum</button>
// </fieldset>

import { create, clickOnText } from 'ember-cli-page-object';

const page = create({
  clickOnButton: clickOnText('button')
});

page.clickOnButton('Lorem, Ipsum'); // Usage of comma separated selectors is deprecated in ember-cli-page-object

Fixes https://github.com/san650/ember-cli-page-object/issues/518
Conflicts with https://github.com/san650/ember-cli-page-object/pull/494

just published your fix as 1.17.4


[CI] Happy workaround

Install GHC
Use cabal to install Happy

This is to fix https://github.com/microsoft/bond/issues/989

It looks like this needs to be merged with the tip of master to pick up the doc build fix.
Also, something's busted with the Python unit tests it appears. @lalo, can you dig into those?

@chwarr looks like it was picking up some mingw python version brought in by one of the new dependencies. The merge build will likely succeed.


Weirdness for POJO field access

Here's my POJO with annotations added for JSimpleDB:
@JSimpleClass
public class Person {

	private int id;
	private String name;
	private String email;
	private int age;

	@JField(indexed = true)
	public int getId() {
		return id;
	}
	public void setId(int id) {
		this.id = id;
	}

	@JField
	public String getName() {
		return name;
	}
	public void setName(String name) {
		this.name = name;
	}

	@JField
	public String getEmail() {
		return email;
	}
	public void setEmail(String email) {
		this.email = email;
	}

	@JField
	public int getAge() {
		return age;
	}
	public void setAge(int age) {
		this.age = age;
	}

	public void updateWith(Person upToDatePerson) {
		this.age = upToDatePerson.age;
		this.email = upToDatePerson.email;
		this.name = upToDatePerson.name;
	}

//	@Override
//	public String toString() {
//		return "Person{" +
//				"id=" + id +
//				", name='" + name + '\'' +
//				", email='" + email + '\'' +
//				", age=" + age +
//				'}';
//	}

	@Override
	public String toString() {
		return "Person{" +
				"id=" + getId() +
				", name='" + getName() + '\'' +
				", email='" + getEmail() + '\'' +
				", age=" + getAge() +
				'}';
	}
}

There's two alternate toString() implementations there. One that Intellij made for me that uses fields to compose the RV. In use those were 0 and null despite prior setXyz() calls on the instance. When I changed it to use the getters it worked as expected. I deduce that the POJOs own fields are effectively disabled.  While I understand that JSimpleDB wants to subclass POJOs, I feel it could be more faithful to the definition of POJOs if each generated method were to also invoke the super with the same args.
Or give up on POJOs and suggest abstractions only.
The trouble with the latter is that web frameworks like Spring want to create a temp 'model' object from request params (and cookie vars and form fields) to hand to a controller method, and according to MVC* that model object could be discarded and not at all saved - subject to the control flow within the controller method (and whatever collaborating methods it calls). Given 'not save' is a viable lifecycle for a Person instance (in this case) that'd be coming through a web-UI, then we cannot insist that all Person instances are made via JTransaction.create(modelClass). If we did it would be data-binding*.
Say we did insist that. I'd end up with Person.class for saving to JSimpleDB, and PersonUI.class with all the same fields and methods for the UI framework to casually create at will, and a checklist activity for the dev team to ensure that the two Person classes tracked each other's fields etc over the months and years. Or a code gen situation.
* https://paulhammant.com/2015/04/29/mvc-misunderstood-for-37-years - find "Late to MVC Party" in page

Yes, the "normal" usage is to have abstract classes (or interfaces) with abstract methods.
Supporting POJO's is always going to be a little weird/different.
Regarding the MVC stuff, if there is an open transaction you can just use the database objects directly. If no, you need to "copy out" the database objects.

Any thoughts on calling the super.setXyz() from your overridden gen'd classes?

It's certainly possible to do. We could add an option to JSimpleDBFactory to enable that behavior.
I'll leave this ticket open as a feature request for that.

No weirdness anymore, after recent POJO work.


Build aarch64 wheels using cibuildwheel

Latest cibuildwheel allows for the building of aarch64 using QEMU.
See https://cibuildwheel.readthedocs.io/en/stable/options/#archs for more information

@nedbat Any thoughts on this PR?

@nedbat Ping.

I'm no expert on what wheels to provide, or how to build them, but this seems to work, so OK!

@nedbat Thanks for merging! Any ETA on when the aarch64 wheels show up in pypi? I saw 6.0 an rc. It doesn't have aarch64 wheels though?

@nedbat Gah! Just checked again. Apologies, see the aarch64 wheels in the rc.


Node version changed for cypress/included:12.1.0 - was this intentional?

Hey there, we see our CI builds failing recently, and where able to pin down the issue to a change of the node version included with your cypress/included:12.1.0 image that we are using. It seems like that the node version included with that image recently changed from 16 to 20.
Was that done on purpose? That's fine, we can always switch to using a custom image based on factory, just curious. Thx!

@wolfgangrittner
This is an old unanswered question and Node.js 16 entered end-of-life on Sep 11, 2023, so I am going to close this issue now.
Hopefully you are not relying on Cypress 12.1.0 any more!


Page refresh problem on the Apollo branch

Wanted to report that -

On Log-in the page doesn't automatically refresh, but shows this - http://screencast.com/t/dqk7v0d1s - the user is logged in but shows up only when the page is physically refreshed

A new post shows up in the list but AFTER 10 seconds (on local dev) without refreshing. Is this an outcome of replacing DDP with GraphQL?

The first thing is a bug, but the second one is the expected behavior. Posts are now refreshed on a 20s interval.

Thanks, Sacha. But as there is no confirmation on submission, a 20s interval might disorient the user . Can't it be made shorter?

Issue closed. There IS a confirmation :)


Revert "Enable zlib build tag in Cluster Agent to enable compression"

Reverts DataDog/datadog-agent#5327

Closing this - we don't need to revert the original PR https://github.com/DataDog/datadog-agent/pull/5327 (only applies to DCA - milestone updated).


Problem with ejecting Page.NotFound

👋🏼 Hi there!
I'm using v6 and trying to customize the Page.NotFound default page. However, every time I start the dev server, elm-spa regenerates the default Page.NotFound module located in .elm-spa/defaults/Pages/NotFound.elm. I'll take a look to see if I can open a PR with the fix.
Cheers!

After cloning the repo and looking at the code, I realized that there is no such issue. It was just an implementation issue of my project. Sorry for any inconvenience. 🙌🏼


Add a hashtag filter for asking questions

What do you think about adding a #vegquestions or #vegassist filter that people could use to ask questions about going vegan? That way people who find out about the bot could share their questions with all the bot's followers, without having to match one of the current filters.

One problem I see that might happen is people using the hashtag incorrectly (like when answering questions) which could get spammy.

I think the intention behind this might be worth addressing. Right now, tweets to @VegAssist aren't visible to followers of the bot. I think @plorry has manually retweeted a few (example), but it might be nice to automate that in some way.
As far as I can tell, though, these sort of tweets are quite rare, so maybe manual retweets can cover it.

I didn't really consider @mentions because I though that would include people replying to retweets, but now I think about it that could easily be avoided by excluding tweets with multiple mentions.

As far as I can tell, though, these sort of tweets are quite rare, so maybe manual retweets can cover it.

They might become less rare if we tell people about it (when replying to retweets). If people have questions a few days after their initial tweet, they probably won't send out another tweet that would match one of the filters, and they probably wouldn't feel comfortable contacting one of the people that replied initially.

Right, there have been a few instances of that I've seen and the second tweet sometimes gets ignored. Would it be too much to retweet all tweets that only mention @VegAssist (and perhaps only when it's at the start or end of the tweet)? Seems potentially abusable, but I'm not sure how else to go about it.

I don't really expect any big problems, but it might be a good idea to keep a close eye on it for a while if we try it. One thing we could do to mitigate abuse is limit the amount of mentions retweeted per X time.

I like this idea too. It provides people with a way to follow-up after getting a re-tweet from @VegAssist.
Just as an added note. is it possible to add to the bot's description on the right-side a FAQ or links about going vegan? this may help people who go to the bot's page to know more after getting a re-tweet.

I'll consider this closed with @Shaderboy's latest push.
Can revisit if we want to do it by hashtag.


Unable to change brightness

Hey, the brightness in the settings is unable to change

yes, someone already had made an issue with that!
link: #5


KeyError: 1765

location : True
.apk/classes.dex
Traceback (most recent call last):
File "deoptfuscator.py", line 23, in
deobfuscator.main(".apk/"+dex)
File "deobfuscator/deobfuscator.py", line 20, in main
dexfile(dex)
File "deobfuscator/classes.py", line 27, in dexfile
dexf_a[dex_location+2] = class_dic[f_idx+add]
KeyError: 1765

used the following commands:
source launch.sh
python3 deoptfuscator.py <apkname>

used this command
python3 deoptfuscator.py <apk_path>
If it throwed error, please upload your sample apk on this Issue!

https://play.google.com/store/apps/details?id=com.sbi.lotusintouch

I solved the error about the app you sent.
The app is not highly obfuscated, so it may not be de-obfuscated in deoptfuscator.
We will develop a setting for de-obfuscation intensity.

Cool. All the best


Added PHP 5.6 to Travis.

Coverage remained the same at 90.54% when pulling c852a31cc229ddd0d810dcd8b099104835b9ac21 on h4cc:patch-1 into fa09e9bdfcf1b7aecf8655ee11a8a520d814b5e2 on onelogin:master.

Coverage remained the same at 90.54% when pulling c852a31cc229ddd0d810dcd8b099104835b9ac21 on h4cc:patch-1 into fa09e9bdfcf1b7aecf8655ee11a8a520d814b5e2 on onelogin:master.


Added fa9r to .github/teams.yml.

Describe changes
I added myself (@fa9r) to .github/teams.yml.
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to docs, I have updated the documentation accordingly.
[x] If I have added an integration, I have updated the integrations table.
[x] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Other (add details above)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Updated InteractiveImage for compatibility with bokeh 0.12.10

Adds support for using the bokeh messaging protocol in bokeh version > 0.12.9, which is required for InteractiveImage to work in bokeh 0.12.10 and above.

Made the requested changes. Should be ready to merge once tests pass.


StepDefiner with regex options

It might be useful to be able to configure regular expressions on demand, i.e. if they are case sensitive or should match full strings. Default value of this follows current behaviour.

For some reason this fails on Xcode 9 but works on Xcode 10

@ilyapuchka Try this - just use a default parameter value ([.caseInsensitive]) for regexOptions in the original init instead of creating a convenience method which just calls the original with the default.
--- a/Pod/Core/StepDefiner.swift
+++ b/Pod/Core/StepDefiner.swift
@@ -22,11 +22,7 @@ open class StepDefiner: NSObject, XCTestObservation {
     /// Options to configure steps regular expressions. Default is `[.caseInsensitive]`
     public let regexOptions: NSRegularExpression.Options

-    required convenience public init(test: XCTestCase) {
-        self.init(test: test, regexOptions: [.caseInsensitive])
-    }
-
-    public init(test: XCTestCase, regexOptions: NSRegularExpression.Options) {
+    public required init(test: XCTestCase, regexOptions: NSRegularExpression.Options = [ .caseInsensitive ]) {
         self.test = test
         self.regexOptions = regexOptions

@deanWombourne thanks, it worked, green now 🎉


chore(ci): test with latest and next showcase images

Description of the change

https://github.com/janus-idp/backstage-showcase/issues/545 got fixed, so we can revert to using the regular latest tag
this also adds new test using next tag to validate that this chart is compatible with the next release (main branch)

Existing or Associated Issue(s)

Additional Information

Checklist

[ ] Chart version bumped in Chart.yaml according to semver.
[ ] Variables are documented in the values.yaml and added to the README.md. The pre-commit utility can be used to generate the necessary content. Use pre-commit run -a to apply changes.
[ ] JSON Schema template updated and re-generated the raw schema via pre-commit hook.
[ ] List tests pass for Chart using the Chart Testing tool and the ct lint command.

@tumido, what do you think about this?

@kadel , do we want to potentially run all tests against both images or is this just one test case?
If it is just one test case, we should define it as one instead by adding a values file into this folder:
https://github.com/janus-idp/helm-backstage/tree/main/charts/backstage/ci

All tests against both images. I want to make sure that updates to this helm chart are not somehow incompatible with Janus current and future releases.


[5.x] MongoDB support

？？？？？ 标题党

@AlvisZhang MongoDB will be supported in openswoole 5.x, not now.

@doubaokun Hello, what is the current status for MongoDB support?


Don't use pip internal API

pip is not supported as a module API. In fact, the developers are
actively trying to discourage everyone from using it this way. In pip
v10, the entire pip.req was moved to pip._internal.req, thus breaking
all scripts which imported it.
This commit removes the need for pip.req.parse_requirements by using
pure Python instead.
Reference: https://github.com/pypa/pip/issues/2286
Reference: https://github.com/pypa/pip/commit/95bcf8c5f6394298035a7332c441868f3b0169f4
Signed-off-by: Cristian Prundeanu<EMAIL_ADDRESS>

@alzix - could this be reviewed?

the proposed change is no longer relevant/required


Dot not changing on page change

I'm fairly certain I've implemented everything as required, working off the sample with defaultIndicator. But when I change pages, the dots don't change along.
I'm working within a Fragment, in onViewCreated:
CircleIndicator pagerIndicator = (CircleIndicator) view.findViewById(R.id.pager_indicator); pagerIndicator.setViewPager(pager);
I think that's all that is required besides the XML implementation in the view? Or am I missing something?

What's your XML?

Straight out of the sample:
<me.relex.circleindicator.CircleIndicator             android:id="@+id/indicator_default"             android:layout_centerInParent="true"             android:layout_width="fill_parent"             android:layout_height="40dp"/>
The dots show, the first one is highlighted, but when I swipe, nothing changes.

I just release a new version, Would you like to try it ?  And what's your system version?

I'll give it a shot today, thanks. System version...I'm targeting API 21 and above only, Lollipop.

I just tried 1.1.3 and still do not get a dot change on page change.
I have three pages, so three dots. The first dot is highlighted properly and the other two dots are smaller and dimmed. When I change pages, nothing changes with the dots, the first one is still highlighted.

It's weird……Can you post your java code?  Please make sure do not setOnPageChangeListener again

Here's what I have (with a few things removed for clarity....pageNames is just a string array):
    public void onViewCreated(View view, Bundle savedInstanceState) {

        pager = (ViewPager) view.findViewById(R.id.viewpager);
        final Toolbar toolbar = (Toolbar) getActivity().findViewById(R.id.toolbar);
        toolbar.setTitle(pageNames[0]);
        CircleIndicator pagerIndicator = (CircleIndicator) toolbar.findViewById(R.id.toolbar_pager_indicator);

        // Build the adapter with the known page names and set it to the pager
        adapter = buildMyAdapter(pageNames);
        pager.setAdapter(adapter);
        pagerIndicator.setViewPager(pager);

        // Pager page transformer (animation used when swiping between pages)
        pager.setPageTransformer(true, new DepthPageTransformer());
        pager.setOnPageChangeListener(new ViewPager.OnPageChangeListener() {
            @Override
            public void onPageScrolled(int position, float positionOffset, int positionOffsetPixels) {
            }

            @Override
            public void onPageSelected(int position) {
                toolbar.setTitle((pageNames[position]));
            }

            @Override
            public void onPageScrollStateChanged(int state) {
            }
        });
    }

Yes，CircleIndicator has already use OnPageChangeListener.
You should set OnPageChangeListener to CircleIndicator.
pagerIndicator.setOnPageChangeListener(new ViewPager.OnPageChangeListener() {
            @Override
            public void onPageScrolled(int position, float positionOffset, int positionOffsetPixels) {
            }

            @Override
            public void onPageSelected(int position) {
                toolbar.setTitle((pageNames[position]));
            }

            @Override
            public void onPageScrollStateChanged(int state) {
            }
        })

Success! That small, but critical piece I missed. thanks for setting me straight.

how to change color? fill

@aizhe11
You can create custom indicator drawable (xml shape or bitmap).
Use these properties
app:ci_drawable
app:ci_drawable_unselected

<me.relex.circleindicator.CircleIndicator
android:id="@+id/indicator"
android:layout_width="match_parent"
android:layout_height="48dp"
app:ci_drawable="@drawable/pager_indicator_accent_radius"
app:ci_drawable_unselected="@drawable/pager_indicator_black_radius"
android:layout_alignParentBottom="true"/>
the indicator still default, not accent on selected and not black on unselected

app:ci_drawable="@drawable/pager_indicator_accent_radius"
app:ci_drawable_unselected="@drawable/pager_indicator_black_radius"

<me.relex.circleindicator.CircleIndicator             android:id="@+id/indicator"             android:layout_width="match_parent"             android:layout_height="48dp"             app:ci_drawable="@drawable/pager_indicator_accent_radius"             app:ci_drawable_unselected="@drawable/pager_indicator_black_radius"             android:layout_alignParentBottom="true"/>


New Activity Idea: Planets Activity

I've created a new possible activity for Sugarizer. Planets Activity ver. 1 offers a 3D model of the solar system planets, which allows students to take a closer look at them. This would hopefully help them appreciate and learn more about the Solar System's planets. As always, let me know what you think!

[x] Add Basic functionality
[x] Include Fullscreen Mode
[x] Allow Responsiveness
[x] Add name of each planet on home view
[x] Select/Unselect Rotation & Info icons
[x] Replace "Go Home" button with "Back" button
[x] Add relative position/size of planets
[x] Handle Journal
[ ] Add localization
[ ] Include Tutorial

Very cool idea and very good start 👍
Do you use a portable 3D library? Mean that could work on Chrome/Firefox/Safari/Android/iOS?
Don't forget to credit the source of image/content.
An UI suggestion: may be you could use a black background on the home page.
Plan a smartphone mode too (fullscreen button in the toolbar), it's now a pre-requisite for new activities.
Can't wait to see the final result.

I used Three.js library, and base on my research, I think it's portable.
In this latest commit, I made the activity more responsive and I've also added a fullscreen mode. The home page's background should also be black (it is much nicer).

Nice.
Few suggestion:

Will be nice to add the name of each planet on the home view
Will be nice to have a way to see relative position/size of planets in the solar system. Could be another view or a small graphic in the detailed view of each planet
Not a big fan of the "Go home" button and of the house icon. May be could be replaced by a planet list to remind the home view
A set of error appears in the console on my side (look like some file are missing):

@llaske I've fixed the console error and added the the suggested enhancement.
I have a question regarding adding the relative position/size of planets. Did you mean something like this:

@AndreaGon yes, exactly.
BTW, look like some files are missing in your last commit.

I've added the planet position and size in this latest commit. This should also fix the error message on the console.

Very nice.
Few remarks:

The compare-icon.svg is missing in the repo, so the button is not visible
It will be nice to display the sun (partially) in the new view, else we don't know if the sun is to the left or to the right of the screen :-)
The image for Saturn on planet position is weird, we expect a view where rings is over the planet
The back to planets lists button should be visible even when planet info are not displayed
May be you could add the Distance to sun value in the planet info too

I've added the suggested enhancement in this latest commit. I have also included journal handling. Let me know what you think!

That's cool.
I've seen two issues:

The distance from the sun is undefined but in my mind the idea was just to repeat the value from the planet position screen, so you could put the planet radius instead
The back button is not visible

I've fixed the undefined issues in this commits.
As for the back button, its appearing on my side. Will look into it

Hmmm. I've tested with both Chrome and Firefox and I've got the same issue.
Sounds like the button is here but at the wrong position:

Try to clean your cache.

I've included the tutorial and localization. The back button should be fixed as well :)

Nice. The Back button is now here.
Few remarks:

There is large black margin at the left of planets list, it was not there before. Is it a consequence of the Back button?

The distance to the sun in the planet distance screen is so big that they overlap each other. I wonder if it's a good idea to display it here. May be we could put it as property of the planet detail screen.

Why not allow the user to click on the planets in the distance screen to display directly the detail screen for this planet (may be we could detect a rectangle around smaller planets)?

I've added the enhancements in these commits.
The margin on the left is also fixed. It wasn't caused by the back button, but it's because I tried putting the list view in the middle.
Let me know what you think!

Very nice. It's cool like that.
Just an issue thought: in touch mode, the planet position screen doesn't work. When touching  planets, nothing happens.

Plus if possible avoid scrollbar in this screen.

This should fix the issue. When switching to touchscreen mode, the browser needs to be refreshed for it to detect whether it is in touchscreen mode or not.
Thoughts?

Work very nice now.
Just found another small issue (not related to touch):

Create a new instance of the activity
Click on a planet to see detail
Click on toggle info button in the toolbar to hide info
Go back to the list of planet
Click on a planet again
The info is displayed but the toolbar button is unselected so to hide the info you should click two times on the button

I've fixed the issue in this commit. The same thing happens to rotation button, so I also fixed it.

Good.
There is an issue in localization, planets name are not localized in list view.

I've tried to localize it here but it don't works because it seems that the localized event is not raised.

The localization issue should now be fixed. I also did the same thing for the planet position view.

The problem now is that the lists is filled two times.

It happens because the localized event is raised two times by the l10n framework. The first time for the browser language, the second time for the Sugarlizer language. May be you could remove the content of the list before fill it.

Just seen another issue on Safari (MacOS) and on iOS. The planet name in the list view is not displayed under the planet image.

May be you're using a display style not supported on some browsers.

The extra list view should now be removed. As for the list view in Safari, I made some changes on the CSS file as well. Let me know if the issue still persist.

Works very well now on all platforms.
Thanks a lot to add this beautiful activity.


⚠ SceneTime has degraded performance

In cd87b78, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 11207 ms

Resolved: SceneTime performance has improved in 7192b8c after 5 minutes.


support merge keys (YAML >> tag), also with interpolation

Is your feature request related to a problem? Please describe.
I would like to be able to merge one config section into another, and augment the result with new keys. In vanilla YAML, this is straightforwardly accomplished via anchors and the merge key tag. The following piece of code illustrates this:
import yaml
print(yaml.safe_load("""
        a: &A
            x: 1
            y: 2

        b:
            <<: *A
            x: 3
            z: 1
"""))

results in
{'a': {'x': 1, 'y': 2}, 'b': {'x': 1, 'y': 2, 'z': 1}}

Loading the same YAML into omegaconf results in an exception:
from omegaconf import *
conf = OmegaConf.create("""
        a: &A
            x: 1
            y: 2

        b:
            <<: *A
            x: 3
            z: 1
""")

yaml.constructor.ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:merge'

Describe the solution you'd like
Well it would be nice if the vanilla YAML merge key worked. However, this whole anchor/alias business is rather clumsy. Top prize would be if this could work with the interpolation feature, like so:
        a:
            x: 1
            y: 2

        b:
            <<: ${a}
            x: 3
            z: 1

Even better would be if this worked across a merge of configs (similar to what's discussed in https://github.com/omry/omegaconf/issues/442). I.e.
from omegaconf import *
conf1 = OmegaConf.create("""
        a:
            x: 1
            y: 2
""")
conf2 = OmegaConf.create("""
        b:
            <<: ${a}
            x: 3
            z: 1
""")
conf3 = OmegaConf.merge(conf1, conf2)

Describe alternatives you've considered
I could use lists with nested mappings in them, and merge the keys in the code. Seems ugly though. I don't see any other way around it.
Additional context
Current onegaconf master, python 3.6.9.

Loading the same YAML into omegaconf results in an exception:

This looks like a bug. we will have to take a closer look.

Well it would be nice if the vanilla YAML merge key worked. However, this whole anchor/alias business is rather clumsy. Top prize would be if this could work with the interpolation feature, like so:

        a:
            x: 1
            y: 2

        b:
            <<: ${a}
            x: 3
            z: 1

This is not happening. pyyaml is handling tag merging at load time. it will not know how to handle with the OmegaConf interpolation.
because pyyaml is handling tags at load time, it cannot not support merging across different config files. Same way it cannot support accessing anchors from different config files (this is actually the primary reason OmegaConf has interpolation to begin with).

I could use lists with nested mappings in them, and merge the keys in the code. Seems ugly though. I don't see any other way around it.

Your entire bug report does not talk about lists. then you pop them up in the alternative.

pyyaml is handling tag merging at load time. it will not know how to handle with the OmegaConf interpolation.

OK yeah that should've been obvious if I'd only thought about it for another minute... :)
Let me rephrase the feature request then: is there any conceivable way of combining interpolation with a key merge in OmegeConf? I would like to compose a config section by merging in previously defined sections, then adding or overriding some keys. Exactly what the << tag offers, but with the ability to refer to stuff across files.

Your entire bug report does not talk about lists. then you pop them up in the alternative.

Yeah sorry, that was inspired by your suggestion in #442, and then I elided the explanation... let me backtrack. What I'd really like is to be able to merge two configs:
file1.yml
a:
  x: 1
  y: 2

and file2.yml:
b:
  # include all the keys from "a" somehow, since <<: ${a} can't work
  y: 3
  z: 4

The only workaround I can think of at present is:
b:
 - ${a}
 -
   y: 3
   z: 4

...and then have explicit code in the application itself which loops over the elements of b and merges them into one dict. Which is the part that feels ugly and non-generic.

Having looked a bit, it looks like the yaml loaded OmegaConf is using is messing up with the merge loader. that's not intentional but after spending 30 minutes trying to fix it I am officially parking it. I don't have time for it at the moment.
(This is related to a feature request of OmegaConf failing on duplicate keys. the person suggesting it copy an arcane piece of code from somewhere and it's breaking the merge tag).

Let me rephrase the feature request then: is there any conceivable way of combining interpolation with a key merge in OmegeConf? I would like to compose a config section by merging in previously defined sections, then adding or overriding some keys. Exactly what the << tag offers, but with the ability to refer to stuff across files.

pyyaml doing everything in load  times means it's hostile to mixing with things that happens afterwards.
I do not know if there is "any conceivable way", and it's an area I don't really want to spend my cycles thinking about. I haven't thought much about yaml merge tag so far.
OmegaConf supports that directly via an API.
cfg = OmegaConf.create({"foo": {"bar" : 10}})
OmegaConf.merge(cfg, {"foo": {"X" :  20}})
# {'foo': {'bar': 10, 'X': 20}}

Or via the somewhat internal merge_with:
cfg = OmegaConf.create({"foo": {"bar" : 10}})
cfg.foo.merge_with({"x":  20})
# {'foo': {'bar': 10, 'x': 20}}

@jgehring , your fix for duplicate keys in #257 is causing an error when using yaml merge tags.
Can you take a look?

OmegaConf supports that directly via an API

Yeah I was playing with that too... but then it's the application code then that has to decide which sections to merge in. If I go back to the single-file YML example using anchors:
a1: &FOO
  x: 1
  y: 2

a2: &BAR
  x: 'a'
  y: 'b'

b:
  <<: *FOO
  y: 3

...whether the "base section" for b is FOO or BAR is a config-side option, completely transparent to the application.
I suppose I could have the application scan the whole config for a magic key in each section, and trigger a merge based on its value. Something like:
b:
   _merge: a1

...would work. Anyway, I just wanted to check if you thought it was simple or worthwhile adding this functionality to the core omegaconf... which from the sound of it it isn't.

If you aren't using it, I suggest you take a look at Hydra.
It supports driving the config composition via the config itself.
Can you please file a separate clean bug report for the tag issue? I think we can close this feature request once you do.

I did start with Hydra actually, but it wasn't quite right for the job, but that led me to omegaconf, which is elegant, and already practically perfect. Thanks for a very useful library, by the way (I should have started with this)!
It was actually a quick job to add a function to the app code to recursively scan the config and act on "_merge" keys. So this now works for me and I'm very happy with it. Even the syntax feels similar to <<.
a1:
  x: 1

a2:
  y: 2

b:
  _merge: a1, a2
  z: 3

There's only one wrinkle: iterating over ListConfig and DictConfig.items() causes normal interpolations to be resolved, which is not necessarily desirable at this stage. I found that iterating over _iter_ex(False) and items_ex(False) avoids this. I am, however, a little nervous about relying on such seemingly "internal" functions. Any chance they can be promoted to the official API?

Bug is #470.

Once you get to do config composition like that you are going to hit some internal functions. I do not plan to promote the special iterators to be a public API at this time but you should feel comfortable relaying on them. (Hydra is also using them).
I would be happy to hear what you think about Hydra 1.1 upcoming support for nested default lists.
It's getting close to being merged to master, in the mean time the docs are mostly ready.
take a look at these and tell me if you feel they would cover your needs:

Defaults List
Packages
Patterns/Extending Configs
Patterns/Configuring Experiments

Keep in mind that the support in Hydra need to meet a very high quality bar (specifically, it needs to play out properly with everything else Hydra is doing and should be very well tested).
The pull request introducing it is probably twice as big as all of OmegaConf.
This is significantly more powerful than your current _merge_ approach in that the choices can be overridden from the outside while composing the config object.
You are of course welcome to use your own solution if you would like (I like the fact that you are exploring in that direction).

I would be happy to hear what you think about Hydra 1.1 upcoming support for nested default lists.

Looks very powerful... still trying to wrap my head around all of it, so I'll just have to ponder it into next year... If I understand correctly though, the composition in Hydra only happens at the defaults level, right? Subsequent sections can only augment whatever was set up in defaults. If this is correct, then it's a bit of an awkward fit to one of our use cases, where we use YAML to describe a pipeline workflow. The YAML file then is becoming more of a (long) imperative program than a configuration. For this reason, it is preferable to have the composition of each section specified locally within that section, rather than separately up front. If that makes sense.
I think I'm converging on a nice solution with just omegaconf though. And now I see you've even implemented relative interpolation targets, wonderful!
Anyway, thanks for all the help, and down with 2020!

Looks very powerful... still trying to wrap my head around all of it, so I'll just have to ponder it into next year... If I understand correctly though, the composition in Hydra only happens at the defaults level, right? Subsequent sections can only augment whatever was set up in defaults.

The definition of the composition can only happen in the defaults. this is the alternative to having scattered merge magic in config file.
In terms of expressive power, this is similar because it let's you compose into a specific package (the terminology in Hydra for the path in the config).
All the defaults lists (in the primary, and then in included configs and so on) and first converted into a tree structure and then into a single list.
Each item in that final defaults list contains the logical config path of the config (e.g /db/mysql or /server/db/mysql) and the final package to place the config content into.
That single list is used by starting with an empty config and then calling cfg = OmegaConf.merge(cfg, cfg_from_list) for each item. (with the extra complication of embedding the cfg from the list into the final package first).
Another advantage of Hydra is that the config discovery is abstracted from the process. Hydra supports a config search path and configs can be in the file system, in Python packages and also in the config store (which is an in-memory store typically used to store Structured Configs acting as schema).

I think I'm converging on a nice solution with just omegaconf though. And now I see you've even implemented relative interpolation targets, wonderful!

Yup, this makes interpolation more practical in the presence of dynamic composition :).
Keep in mind that 2.1 is not officially out yet and there are a handful of small breaking changes there.
You can see them in the news directory.
You can install the dev release though (dev releases are not pretending to have a stable API across their versions).

Anyway, thanks for all the help, and down with 2020!

Happy new year!
I don't want to jinx 2021 by saying 2020 was a pesky pesky year :).

Hi @omry,
Is there a way to use the interpolation in the same config file, with merge? I am unable to find the correct syntax. What I want is the omegaconf syntax for regular YAML merge.
Example:
main_config: &main
  seed: 42
  device: cuda
train_config:
  <<: *main
  epochs: 2
  optimizer: adam

yaml merge is a load time feature and interpolation is a runtime feature.
Those two features are generally incompatible.
The only equivalent to yaml merge is OmegaConf.merge(), which is an API you have to call in your code.
If you are looking to automate config composition look at Hydra (https://hydra.cc).

Hi @omry,
Thanks a lot. I built omegaconf from source, and now I am facing an issue with variable interpolation (it doesn't work), even when there is no merge syntax used. Is this expected?

Since it has nothing at all to do with this issue, can you not hijack it?
If you think you found a bug submit as new issue with a minimal repro.


Support for Native Text Indexing in Pinot

Build a fully functional text search engine on top of native Pinot indices, allowing exact matches, prefix and suffix matches, substring matches and regular expressions.
Performance of the text search component (automaton, matcher and FST) should be comparable or better than Lucene's FST, matcher and automaton.
Build the engine using core Pinot capabilities and have it deeply integrated with Pinot's core components
Allow the library to be reusable across Pinot.
Allow the library to be extensible without requiring application changes
Please see:
https://docs.google.com/document/d/1PMhoRy6WF46C4d4mw0LVe9b8Vjqes6vsXZkmxXzMYzw/edit#heading=h.krgi6ulfrbxj

As part of the design, it would be great to see details on how different analysis chains can be specified (e.g. based on target language, for a column).
It would also be great to plan for supporting dynamic analysis chains, typically based on language classification (either manual or dynamic), per row, as that solves a major problem for many text search use cases.

Thanks @atris . I would like to review. Please give me couple of days to go through the doc.

High level question
After we added lucene based text index, there was FST text index added which uses Lucene FST libraries for purely regex searches as the former one took more storage if the user only wanted regex searches and not term, phrase etc.
For the current proposal of native text indexes, are we planning to re-implement all of Lucene libraries for search within Pinot ?

Looking at the doc and PR, it looks like only the FST is being implemented. Pinot already has the posting list and the ability to evaluate boolean expressions over posting lists. Is there anything else?

No, FST and regexp automaton are the only two things - - rest of the
operations will be performed by Pinot indices
On Fri, 10 Sep 2021, 01:10 Kishore Gopalakrishna, @.***>
wrote:

Looking at the doc and PR, it looks like only the FST is being
implemented. Pinot already has the posting list and the ability to evaluate
boolean expressions over posting lists. Is there anything else?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/pinot/issues/7395#issuecomment-916383166, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AANE5Y42X34HBC3VHHKYSCLUBEETDANCNFSM5DMMPHBQ
.

Wanted to understand a few things better.
IIUC, this is our current state

Lucene text index - wrapper over Lucene to get phrase, term, regex etc search query functionality
Lucene FST index - this was added later (by Confluera I guess) to use FST libraries of Lucene to purely get regex search functionality from Lucene.

In both the above cases, we get FST and regexp automaton as part of using Lucene. We also advise users to not use Lucene text index if they want to do exact matches since Pinot's native inverted index is way faster for exact matches. When we say we are implementing native FST index, what exact functionality are we adding and/or improving ? This is not clear in the design doc. The doc talks about control/flexibility and potential future improvements but they are a bit vague IMHO and few more details can be added in those sections.
My guess is that this is about improving phrase, regex and fuzzy search by building a native FST index which can work on top of existing Pinot's native structures -- inverted index and dictionary. So it seems like a bridge is missing between Pinot's native inv index and dictionary structure and Lucene FST. Is this correct ? If so, can this not be achieved by continuing to use Lucene FST library as opposed to putting it into Pinot. Something we already do as part of Lucene FST index.
Also, how will this new work be different from what is currently offered by Lucene FST index in terms of functionality and performance. There are some performance charts but if I am reading them right, the improvement seems marginal.
Also, thanks for clarifying in the doc that this work won't regress the TEXT_MATCH functionality (query syntax etc) and performance. In case, we go ahead with this new work, I think from the end state, we should not have the mandatory step of removing current Lucene text index and TEXT_MATCH. If someone wants to migrate, there should be a migration path. Rest of the users can continue to use what we have today

Thanks for reviewing the document, @siddharthteotia !
Here are my thoughts:
Current text search infrastructure: Status quo, we simply build side car Lucene indices and expose a UDF which allows users to specify Lucene queries. IMO, this is a component that should ideally be outside of Pinot since it has no correlation with Pinot itself.
So, an eventual goal is to move text search to native Pinot indices and dictionary, and follow the SQL Standard (LIKE operator) syntax as much as possible.
Now, coming to the FST itself. There are three reasons as to why a native FST makes sense:

Flexibility and Control -- Lucene is a full fledged search library. It is built for generic text search use cases and consists of capabilities which allow ranked retrieval, norm storage and impact filtering,  to name a few capabilities. None of these are of relevance to us since we do not perform ranking. As I mentioned before, if we are building our text search capabilities on top of Pinot data structures, then pulling in Lucene just for the FST is an overkill, and also stops us from any potential changes that we may wish to do. Lucene's FST is a generic engine, not optimized for our use cases (only dictionary IDs as output symbols, primary query load being prefix and suffix matches from LIKE operator). Other improvements may or may not come in later, but if we do not move to our native implementation, we remove the possibility of any such improvements.

Ability to perform Pinot specific optimizations -- As stated in the above point, it is not possible for us to do specific changes/enhancements. For e.g., it should be possible to short circuit the evaluation of regular expressions ending with match-all and having a short prefix before the same, thus accelerating a common use case of LIKE operator.

Realtime Capabilities -- Lucene builds FST during segment flush, thus forcing us to flush frequently. Also, this inhibits us from doing real time text search, which is a limitation. With a native FST implementation,  we should be able to explore this path.

Regarding TEXT_MATCH, while it is my dearest wish to deprecate the module, I understand that some users may wish to use it. As highlighted, both indices can co exist, with no mandate to migrate to one over the other.

I had followed up for clarifying few additional things with @atris in slack channel. Copying here for reference and visibility
Can we all confirm the following ? I am sorry to have asked this couple of times as part of different threads in the doc but since doc still indicates some sort of migration Note that till completion of phase 4,  we will be maintaining the existing text indices within Pinot. I just want to make sure

Existing Lucene text index functionality offered via TEXT_MATCH will continue to work as is and is essentially untouched by this work
Both indexes can co-exist and we are not removing Lucene dependency ?
Upon segment reload, existing Lucene index can potentially be converted to new format (if need be). However, if someone wishes to do this, how will the query syntax used in TEXT_MATCH from lucene based remain compliant for native FST index (which I believe will follow SQL LIKE semantics). I am guessing the users will have to change queries if they wish to migrate ?
For the native FST index, the plan is to eventually support all kinds of searches -- phrase, term, regex, fuzzy etc. So for example, phrase search needs position info which I am not sure if it comes for free as part of FST. Regardless, all of that is the end state and comprehensive text search functionality will be available through this native index ?

This is important for us because eventually (and this is a big eventual for us :slightly_smiling_face: ) we might want to migrate our production Li users from Lucene text index to native FST index if performance is better. I can't promise if that will happen as it will certainly be a lot of work (hence seeking confirmation that we are not removing anything). Our production users use a lot of phrase queries.

General question - are you planning to make this functionality available both via LIKE and TEXT_MATCH or want to keep it separate and just use LIKE ? Latter can also be overloaded as long as user docs clearly indicate that TEXT_MATCH can be used for both native and lucene text index
Request on code - since FST is like a black box (for me except for whatever I learned from paper and online presentations), can you please make sure that code is sufficiently documented and explains algorithm as and when needed. Initially, we were just relying on Lucene committers but now we will have to maintain. This will also help with easy review

@atris 's response

Yes, Lucene Indices and TEXT_MATCH will be completely untouched and unaffected by this effort.
No, we are not removing the dependency and both indices can coexist, oblivious of each other.
Here is the interesting one. Native FST can support all queries that Lucene does. However, since our indices do not store some metadata (such as positional index) that Lucene Indices do, we will have to implement custom operators on top of native FST. However, syntactically, native FST shall pose no challenges in that implementation. If there are specific operators outside of the four planned currently (regexp, like, phrase and fuzzy) that will be needed for users to migrate, I will be more than happy to support.
Yes, in the end state, comprehensive text search will be natively available.
I was actually not planning to overload TEXT_MATCH since it basically supports Lucene syntax, but rather have custom functions for phrase, fuzzy and regexp, and let the LIKE operator deal with the rest. However, there is no reason why we can't go down that route.
I completely agree. I have tried to document the code as elaborately as possible and also written supporting documents (e.g. On the Regexp compilation process). If there is more needed on specific areas, I will gladly write more :)

Based on above clarifications, I am ok with proceeding
@amrishlal , @jackjlli  please feel free to add any additional discussion notes

Did a brief sync up with @atris yesterday. We would like to try this out for functional and perf testing on our prod use case as soon as the phrase and term search part is complete. Will have to discuss/ handle index conversion and query migration (if possible). We will collaborate during testing / rollout for any feature, perf gaps etc.
cc @vvivekiyer @jasperjiaguo


Adds Storybook navbar component

This one is pretty complex. I've added stories for the following:

different colors (rockarch.org versus DIMES/Library)
text and image brands (again, rockarch.org versus DIMES/Library)
static nav items (DIMES)
dropdown nav (rockarch.org)
social media icons (rockarch.org)

I suspect we'll have to tweak both the HTML and the styles for this as we implement.
Wondering if this should be a Header component instead of a Navbar? That's what we called it in DIMES...
fixes #19

Yes, I vote to call this a header. Some of these iterations don't contain a nav, and header is an html element, whereas navbar evokes a Bootstrap header with navigation.
I recently learned that apparently menu and menu-itemare meant to be used specifically for an OS or application menu, not anav, so I think we've implemented that incorrectly in DIMES (we used to also use role="menu"in rockarch.org, but moved away from that). I believe the "With Nav Items" component for mobile should follow our rockarch.org hamburger button pattern with anul` of navigation links.

Thanks for all the work on this @HaSistrunk!


Donald.pasquarello_iis_dashboard

What does this PR do?
Added my JSON file for IIS Out of the Box integration
Motivation
asked to help with the dashboard revamp
Additional Notes
added additional notes, graphs and logs
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

hi @ChristineTChen, yes that is what I am trying to accomplish. I changed up the format and there is a screen shot of the dashboard and what it looks like as well

Hi @donp123 , thanks for the update. Are you trying to update IIS - Overview dashboard or the IIS - Metrics dashboard?

hi @ChristineTChen, the IIS - Overview.


Bruce zcq master

Check it out. Now it's possible to choose action by property tapDismissAction
Also you can find example usage for one of the pickers in this pull request.

@skywinder Thanks


✨ ⇧⌘[ and ⇧⌘] keyboard shortcuts to cycle between editor tabs in the active editor

Description
⇧ ⌘ [ and ⇧ ⌘ ] should cycle between editor tabs in the active editor.
Alternatives Considered
No response
Additional Context
No response
Screenshots
No response

I would prefer Ctrl + Tab. Am used to that. Perhaps the best solution would be a section in the app settings to choose your own keyboard shortcut mappings.


Document how to set uv install directory from uv-installer.sh

Was about to add a feature request then realised it already works:
$ curl --proto '=https' --tlsv1.2 -OLsSf https://github.com/astral-sh/uv/releases/download/0.2.29/uv-installer.sh
$ env -i CARGO_HOME=/tmp/foo/cargo HOME=/tmp/foo/home /usr/bin/bash uv-installer.sh --no-modify-path
downloading uv 0.2.29 x86_64-unknown-linux-gnu
installing to /tmp/foo/cargo/bin
  uv
  uvx
everything's installed!
$ tree -a /tmp/foo
/tmp/foo
├── cargo
│   └── bin
│       ├── uv
│       └── uvx
└── home
    └── .config
        └── uv
            └── uv-receipt.json

6 directories, 3 files

Might be helpful to document this for others.

Thanks! This would go in https://github.com/astral-sh/uv/blob/main/docs/installation.md#standalone-installer if someone is interested in contributing.


pod Amplify 版本不支持

Describe the bug
https://github.com/aws-amplify/amplify-swift
这个是Amplify代码仓库，为什么我用pod依赖管理工具pod 'Amplify' 得到的代码目录结构和git仓库的目录结构不一样？而用Swift Package Manager引入的库就和git仓库的目录结构一样的，而且用 Swift Package Manager 得到的版本比pod高很多，这是为什么？
Steps To Reproduce
Amplify iOS端 一共分两种引入方式：
1、SPM   这种方式亚马逊官方在用很适合美国那边的开发者，看了一下版本比较高都到2.28.0以上了
2、pod    这种方式很适合中国的开发者，但是最高版本是1.30.8，很显然这个版本比SPM低多了，我用这个方式引入后调用终端代码报错，说signInResult找不到isSignedI字段。
func signIn(username: String, password: String) async {
        do {
            let signInResult = try await Amplify.Auth.signIn(
                username: username,
                password: password
                )
            if signInResult.isSignedIn {
                print("Sign in succeeded")
            }
        } catch let error as AuthError {
            print("Sign in failed \(error)")
        } catch {
            print("Unexpected error: \(error)")
        }
    }
而SPM方式不会报错，我看源码发现这两种版本的代码确实不一样：
SPM的定义：
public func signIn(username: String? = nil,
                       password: String? = nil,
                       options: AuthSignInRequest.Options? = nil) async throws -> AuthSignInResult {
        return try await plugin.signIn(username: username, password: password, options: options)
    }

pod的定义：
func signIn(
        username: String? = nil,
        password: String? = nil,
        options: AuthSignInOperation.Request.Options? = nil
    ) -> AuthSignInOperation {
        signIn(username: username, password: password, options: options, listener: nil)
    }
很明显看到不一样的地方是：SPM版本的返回值是AuthSignInResult，所以有isSignedI字段。而pod版本的返回值是AuthSignInOperation，没有isSignedI字段。pod版本的Amplify太落后。

我的问题是：想请您帮我找一下有没有比较高的pod版本的Amplify，和SPM版本的Amplify SDK保持一致，同步更新的版本。

Expected behavior
不支持  pod Amplify最新版本。
Amplify Framework Version
1.30.8
Amplify Categories
Auth
Dependency manager
Cocoapods
Swift version
v5.8
CLI version
12+
Xcode version
14.2
Relevant log output
signInResult找不到isSignedI字段。

Is this a regression?
No
Regression additional context
No response
Platforms
iOS
OS Version
ios 13+
Device
any
Specific to simulators
any
Additional context
No response

Hi @zhangshouyin!
Amplify v2 (i.e. versions 2.x.x. and higher) is only distributed through SPM, and we have no plans of adding CocoaPods support.
Amplify v1 (i.e. versions 1.x.x) is currently in Maintenance Mode, so we advice you to use Amplify v2 instead.

Hi @zhangshouyin! Amplify v2 (i.e. versions 2.x.x. and higher) is only distributed through SPM, and we have no plans of adding CocoaPods support.
Amplify v1 (i.e. versions 1.x.x) is currently in Maintenance Mode, so we advice you to use Amplify v2 instead.

Hi @zhangshouyin! Amplify v2 (i.e. versions 2.x.x. and higher) is only distributed through SPM, and we have no plans of adding CocoaPods support.
Amplify v1 (i.e. versions 1.x.x) is currently in Maintenance Mode, so we advice you to use Amplify v2 instead.

Hi @zhangshouyin! Amplify v2 (i.e. versions 2.x.x. and higher) is only distributed through SPM, and we have no plans of adding CocoaPods support.
Amplify v1 (i.e. versions 1.x.x) is currently in Maintenance Mode, so we advice you to use Amplify v2 instead.

I saw that aws-sdk-ios is written in Objective-C, with 1.7K stars, it should be very stable, will it continue to be updated?
So should I give up Amplify v2 and use aws-sdk-ios instead? I don't know which solution is better for me?
What are the advantages of Amplify v2 compared to aws-sdk-ios?

Hi @zhangshouyin! Amplify v2 (i.e. versions 2.x.x. and higher) is only distributed through SPM, and we have no plans of adding CocoaPods support.
Amplify v1 (i.e. versions 1.x.x) is currently in Maintenance Mode, so we advice you to use Amplify v2 instead.

Hi @ruisebas
I saw that aws-sdk-ios is written in Objective-C, with 1.7K stars, it should be very stable, will it continue to be updated?
So should I give up Amplify v2 and use aws-sdk-ios instead? I don't know which solution is better for me?
What are the advantages of Amplify v2 compared to aws-sdk-ios?

The AWS SDK for iOS is still maintained, although we advice you to use Amplify v2 instead.
Amplify v2 is written fully in Swift and takes advantages of the language's features. It provides higher level APIs that support a wide range of common use cases out of the box. The SDK on the other hand is more of a low-level client that lets you interact directly with AWS APIs, but as such you will need a deeper understanding of how they work and how to handle them.
You can read more about it in this FAQ: How is the SDK different from the Amplify Libraries, and in Amplify's documentation main page: How Amplify works.

Hi @zhangshouyin! Amplify v2 (i.e. versions 2.x.x. and higher) is only distributed through SPM, and we have no plans of adding CocoaPods support.
Amplify v1 (i.e. versions 1.x.x) is currently in Maintenance Mode, so we advice you to use Amplify v2 instead.

Hi @ruisebas
Is it feasible for me to privatize the Amplify v2 code into my own repository and then add the corresponding podspec files to each library?

Hi @zhangshouyin! Amplify v2 (i.e. versions 2.x.x. and higher) is only distributed through SPM, and we have no plans of adding CocoaPods support.
Amplify v1 (i.e. versions 1.x.x) is currently in Maintenance Mode, so we advice you to use Amplify v2 instead.

Hi @ruisebas!
I'm accustomed to using CocoaPods to manage code libraries and not comfortable with SPM. I still want to use CocoaPods.
So, Is it feasible for me to privatize the Amplify v2 code into my own repository and then add the corresponding podspec files to each library?

You're free to fork the repo and make modifications to the code that fits your use cases better, but please be aware that we cannot offer any support on forks.
Alternatively, you might be able to wrap Amplify v2 in an xcframework and/or host that xcframework as a podspec in your build system.

You're free to fork the repo and make modifications to the code that fits your use cases better, but please be aware that we cannot offer any support on forks.
Alternatively, you might be able to wrap Amplify v2 in an xcframework and/or host that xcframework as a podspec in your build system.

Hi @ruisebas  Thanks for your advice I tried packaging into xcframework.


📝 Docs: Adding useful missing information

Relates to #116
Added

Missing .env variables

FIREBASE_PROD_URI
ALGOLIA_PROD_INDEX_NAME

Note to switch to release-1.0 branch
Info about google-services.json file to android development setup
Start Android Emulator section
Note about android-start error on Windows 10

@adilanchian Thank you so much for the review! I will close this issue and I think it can be merged in:)

I think you accidentally closed the PR haha. Just reopened and merging in now :)

I think you accidentally closed the PR haha. Just reopened and merging in now :)

Oops I did, my bad. Thank you!


Upgraded fHDHR and Plugins with git pull, doesn't work again

Hey guys...  Back again...
All that I did was a git pull for the main fHDHR repo, and the 3 plugin repos that I use (fHDHR_plugin_interface_hdhr,  fHDHR_plugin_origin_ceton, and  fHDHR_plugin_stream_ffmpeg), and now it won't start again.  I then ran the pip command to install the requirements, and got a little farther.  I think what I'm seeing now is that something is missing from my config, but I can't decipher exactly what's missing... here's the crashlog...
Checking and Installing Core Dependencies.
[2021-03-06 10:41:07,061] NOOB - Loading fHDHR v0.9.0-beta with fHDHR_web v0.9.0-beta
Traceback (most recent call last):
  File "/opt/fHDHR/lib/python3.8/site-packages/urllib3/connection.py", line 169, in _new_conn
    conn = connection.create_connection(
  File "/opt/fHDHR/lib/python3.8/site-packages/urllib3/util/connection.py", line 73, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/opt/fHDHR/lib/python3.8/site-packages/gevent/_socketcommon.py", line 230, in getaddrinfo
    addrlist = get_hub().resolver.getaddrinfo(host, port, family, type, proto, flags)
  File "/opt/fHDHR/lib/python3.8/site-packages/gevent/resolver/thread.py", line 63, in getaddrinfo
    return self.pool.apply(_socket.getaddrinfo, args, kwargs)
  File "/opt/fHDHR/lib/python3.8/site-packages/gevent/pool.py", line 161, in apply
    return self.spawn(func, *args, **kwds).get()
  File "src/gevent/event.py", line 305, in gevent._gevent_cevent.AsyncResult.get
  File "src/gevent/event.py", line 335, in gevent._gevent_cevent.AsyncResult.get
  File "src/gevent/event.py", line 323, in gevent._gevent_cevent.AsyncResult.get
  File "src/gevent/event.py", line 303, in gevent._gevent_cevent.AsyncResult._raise_exception
  File "/opt/fHDHR/lib/python3.8/site-packages/gevent/_compat.py", line 65, in reraise
    raise value.with_traceback(tb)
  File "/opt/fHDHR/lib/python3.8/site-packages/gevent/threadpool.py", line 142, in __run_task
    thread_result.set(func(*args, **kwargs))
socket.gaierror: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/fHDHR/lib/python3.8/site-packages/urllib3/connectionpool.py", line 699, in urlopen
    httplib_response = self._make_request(
  File "/opt/fHDHR/lib/python3.8/site-packages/urllib3/connectionpool.py", line 394, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/opt/fHDHR/lib/python3.8/site-packages/urllib3/connection.py", line 234, in request
    super(HTTPConnection, self).request(method, url, body=body, headers=headers)
  File "/usr/lib/python3.8/http/client.py", line 1255, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib/python3.8/http/client.py", line 1301, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.8/http/client.py", line 1250, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.8/http/client.py", line 1010, in _send_output
    self.send(msg)
  File "/usr/lib/python3.8/http/client.py", line 950, in send
    self.connect()
  File "/opt/fHDHR/lib/python3.8/site-packages/urllib3/connection.py", line 200, in connect
    conn = self._new_conn()
  File "/opt/fHDHR/lib/python3.8/site-packages/urllib3/connection.py", line 181, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f6949da2e50>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/fHDHR/lib/python3.8/site-packages/requests/adapters.py", line 439, in send
    resp = conn.urlopen(
  File "/opt/fHDHR/lib/python3.8/site-packages/urllib3/connectionpool.py", line 755, in urlopen
    retries = retries.increment(
  File "/opt/fHDHR/lib/python3.8/site-packages/urllib3/util/retry.py", line 573, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='none', port=80): Max retries exceeded with url: /stream_request.cgi (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f6949da2e50>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/fHDHR/fHDHR/main.py", line 27, in <module>
    sys.exit(run.main(SCRIPT_DIR, fHDHR_web, deps))
  File "/opt/fHDHR/fHDHR/fHDHR/cli/run.py", line 129, in main
    returned_code = start(args, script_dir, fHDHR_web, deps)
  File "/opt/fHDHR/fHDHR/fHDHR/cli/run.py", line 109, in start
    return run(settings, logger, db, script_dir, fHDHR_web, plugins, versions, web, scheduler, deps)
  File "/opt/fHDHR/fHDHR/fHDHR/cli/run.py", line 32, in run
    fhdhr = fHDHR_OBJ(settings, logger, db, plugins, versions, web, scheduler, deps)
  File "/opt/fHDHR/fHDHR/fHDHR/__init__.py", line 42, in __init__
    self.fhdhr.origins = Origins(self.fhdhr)
  File "/opt/fHDHR/fHDHR/fHDHR/origins/__init__.py", line 25, in __init__
    self.origin_selfadd()
  File "/opt/fHDHR/fHDHR/fHDHR/origins/__init__.py", line 43, in origin_selfadd
    self.origins_dict[method] = self.fhdhr.plugins.plugins[plugin_name].Plugin_OBJ(plugin_utils)
  File "/opt/fHDHR/fHDHR/plugins/fHDHR_plugin_origin_ceton/origin/__init__.py", line 15, in __init__
    self.startstop_ceton_tuner(i, 0)
  File "/opt/fHDHR/fHDHR/plugins/fHDHR_plugin_origin_ceton/origin/__init__.py", line 87, in startstop_ceton_tuner
    StartStopUrlReq = self.plugin_utils.web.session.post(StartStopUrl, StartStop_data)
  File "/opt/fHDHR/lib/python3.8/site-packages/requests/sessions.py", line 590, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
  File "/opt/fHDHR/lib/python3.8/site-packages/requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "/opt/fHDHR/lib/python3.8/site-packages/requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "/opt/fHDHR/lib/python3.8/site-packages/requests/adapters.py", line 516, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='none', port=80): Max retries exceeded with url: /stream_request.cgi (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f6949da2e50>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))

Looks like trouble connecting to your Ceton device.
@DanAustinGH will add some better handling for the error.
However, nothing should* have changed to effect the ceton plugin. My instincts are that something has changed with your network, or your access to your Ceton device.

SONOFAB**CH... Somehow my config got moved when I did the update...


Git failed to find repository: permission denied

VSCode Version: Code - Insiders 1.16.0-insider (8b942faafb2d1bee6fd6a346853548d528c7eb5a, 2017-08-31T07:27:43.804Z)
OS Version: Windows_NT x64 10.0.15063

Steps to Reproduce:
Under a standard account, open the c:\Windows folder in Code
bug
See a large number of "failed to find repository" errors

extensionHost.ts:383 [Extension Host] Failed to find repository: Error: spawn C:\Program Files\Git\cmd\git.exe ENOENT
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)

Reproduces without extensions: Yes

This no longer happens in today's build.


Turn off Location selection on map?

first off, thank you so much for this awesome package, I wanted to ask few questions:

Can we disable the Map location selection, meaning when i click on the map it doesnt change location OR just simply hide the map?
Is there a radius for nearby locations?

Would very much like to know if im missing something here.
Thanks!

Currently the tap gesture is provided for selection.
The radius is set as 150 for nearby locations now. If you want I can expose a property to set the radius

Currently the tap gesture is provided for selection.
The radius is set as 150 for nearby locations now. If you want I can expose a property to set the radius

So i take it its not possible to hide the map and only enable nearby locations? thinking of it like a feature of Snapchat when u show list of nearby locations.

So you want to hide just the map and show nearby locations?

So you want to hide just the map and show nearby locations?

That would be Big as an optional feature with a desired Radius set, the map still shows (Or Not) but you cant click and change position and only shows you a limited number of Places based on radius. Thats how Snapchat for example is doing it.

I could probably fork this over the weekend and do that change but If this is something you want to add in the package then i would not do that i guess.

Ahh that's too much of a change for me right now lol. Sorry about that.
Please fork the repo and the desired UI changes.

Ahh that's too much of a change for me right now lol. Sorry about that. Please fork the repo and the desired UI changes.

understandable, thanks.

Closing as non issue.


One big output matrix multiply per minibatch

In the forward step, we currently do |sentence| multiplies of the form
|batch| x |hidden| times |hidden| x |vocab|
But the output matrix isn't needed to continue time steps, so we could just buffer up the hidden states (we need the activations in RAM anyway) and do one big
|sentence| x |batch| x |hidden| tensor times |hidden| x |vocab|
This came from a discussion with NVIDIA and supposes that larger matrix multiplies are generally faster.
It's an instance of the more general autobatching.

True, clever.
I do however have models where the next step depends on the output, the hard attention models for instance.  Will take a look at that.

Actually, after some thinking, I believe we are doing this already? During translation you need to do it per time step due to beam search. During training there is only one big multiply.

Closing unless I am wrong.


Remove Private Key field for members after X days

The document graph maintains a node with a created_date for each member document. I think that we should disallow using the private key field if the member document's created_date is older than X days (45 days?).  This gives them a grace period for account setup and getting started while also eliminating this risk.

I'm still using my PK when Anchor is acting strange <_<

Yes, this is too early to turn off PK. I would say we need at least 50+%
adoption and no stability issues with Anchor and theLight wallet functional
(in beta).
On Wed, Nov 4, 2020 at 12:27 PM Grégory LATINIER<EMAIL_ADDRESS>wrote:

I'm still using my PK when Anchor is acting strange <_<
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/hypha-dao/dho-web-client/issues/174#issuecomment-721868500,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF4UQTXFNHRDTF3TP42T4I3SOGFH5ANCNFSM4TKKEE5Q
.


Question about the LFTP call

So I had to redo my sd card in my all sky raspberry pi.  I redid the config.sh and the FTP-Settings file to match what I had before.  I was getting a live image but was unable to upload any images to my website.  Looking at the allsky.log I noticed a Certificate  Validation
Sep  4 19:33:12 Pi-AllSky allsky.sh[624]: cd: Fatal error: Certificate verification: certificate common name doesn't match requested host name ‘n3bsq.com’ (:::::::::::::*::::::)
Sep  4 19:33:13 Pi-AllSky allsky.sh[624]: put: image.jpg: Fatal error: Certificate verification: certificate common name doesn't match requested host name ‘n3bsq.com’ (:::::::::::::::::::)
Sep  4 19:33:14 Pi-AllSky allsky.sh[624]: mv: Fatal error: Certificate verification: certificate common name doesn't match requested host name ‘n3bsq.com’ (::::::::::::**:::::::)
I then remembered on the old version I had to add the following command to the lftp.conf
set ssl:verify-certificate no
as soon as I added that the error in the log file went away
so my question is what is the best way to do this via the lftp.conf or somewhere else.
Mike

Mike,  I don't remember the error I was getting, but here are my notes:
To allow lftp to work with unknown certificates, add:
		set ssl:check-hostname false
	to /etc/lftp.conf

I believe it's also possible to add that to a file in the $HOME directory.  Either way, I'm trying to get away from telling people to edit the scripts - that's too difficult for most people.
Another possibility that might be easier for people would be for Thomas or I to put a variable in config.sh that the lftp commands would include.  People like you and I would set that variable to "set ssl:verify-certificate no".  This might also make it easier to move to a new device as long as someone kept their config.sh file.
Your command and mine are different; I'm not sure if that means we had different error messages or there are two ways to resolve the same issue.
Anyway, I'll add this to the "troubleshooting and tips" WiKi I'm creating.
If this answers your question, please close this issue.   Thanks.

Eric,
I added you command also to the lftp.conf and commented my command.  It appears both commands work.  Not sure which one is the best one to use for this issues.  I will close it out for now unless anyone has any suggestion as to the best one to use.

Thanks Mike.  Interesting that both our commands work.  I'll have to undo my fix and see what error message I get.  Either way, I'll add both to the WiKi.


Update AriaNG to 1.2.5

Update AriaNG to 1.2.5
Btw, is this project dead? Last commit on Jun 14, 2019

refer to https://github.com/RossWang/Aria2-Integration/issues/89


Let AVG ignore null

Spawn from #709

Any inputs on why the AVG function is not implemented like MIDDLE and STDVAR would be helpful


Upgrade to v1.11.0

upgrade to crossplane 1.11.0

Merged into: https://github.com/giantswarm/crossplane/pull/36


[#2934] feat(catalog-mysql): use metaData.getTables instead of directly SQL

What changes were proposed in this pull request?
use metaData.getTables instead of directly SQL
Why are the changes needed?
Fix: #2934
Does this PR introduce any user-facing change?
N/A
How was this patch tested?
IT

@FANNG1 @yuqi1129  Could you help to review this PR when you have time?

@jerryshao @FANNG1
Should we disable sentences like show tables in MySQL, I remember that it's okay to use it...

@jerryshao @FANNG1 Should we disable sentences like show tables in MySQL, I remember that it's okay to use it...

I prefer to first retrieve metadata from JDBC as it is more general and maintainable.

@yuqi1129 @jerryshao  do you have any other comments?

@yuqi1129 @jerryshao do you have any other comments?

I'm okay with it.

@zhoukangcn , merged to main, thanks for your work!


Add example targets

to easily interact with.
e.g.
cargo run --example <example-name>

They currently work without needing to add them as targets because of default cargo auto discovery.
→ cargo run --example input
   Compiling regex-syntax v0.6.23
   Compiling terminal_size v0.1.16
   Compiling regex v1.4.5
   Compiling console v0.14.1
   Compiling dialoguer v0.8.0 (/Users/pksunkara/Coding/mitsuhiko/dialoguer)
    Finished dev [unoptimized + debuginfo] target(s) in 9.06s
     Running `target/debug/examples/input`
? Your name › ⏎


Exclude fields with #[codec(skip)] attribute

Addresses issue #14

Awesome, thank you for resolving this so quickly!
I'm enjoying reading through #16 (as well as the other paritytech repos) and am learning a lot!!


unable to type in an address while creating new mail

K9mail 5.600 from F-Droid Store.
Unfortunately I am not able to complete typing an e-mail address in the address field, here is an example:
You put<EMAIL_ADDRESS>into the Addressbook so that lookup works.
then type:  some.body@o
and the cursor ends up in the new message field. You are unable to finish typing therdomain.com
You are also unable to fix the Address you have just typed which is annoying.
Only Workaround is to copy and paste the e-mail Address which is even more annoying.

Duplicate of #2829


'TorchBackend' object has no attribute 'sort2'

Update morpho_sparse_utils.py

thanks zEpoch, really appreciate it! @YifanLu2000 can you please review and merge this?

Please update POT to the latest version, this will fix the issue and we don't need to change the code.