How to convert a newMeRequest() call to use RetroFacebook

Sorry for the newbie question, but I'm new to Facebook Graph API and even greener when it comes to RetroFacebook. I'm using Facebook SDK with the provided Login Button, setting the needed read permissions, and just after login I'm issuing a newMeRequest() call to get extra data for the user. I'm stuck converting my code to use RetroFacebook. How could I convert the following code to use RetroFacebook?
    void processLoginSuccess(LoginResult loginResult) {
        // I was trying to use this
        Facebook facebook = Facebook.create(this);
        facebook.me(); // this returns User which does not contain the extra fields I need

        // Instead of using Facebook's provided API
        GraphRequest request = GraphRequest.newMeRequest(
                loginResult.getAccessToken(),
                new GraphRequest.GraphJSONObjectCallback() {
                    @Override
                    public void onCompleted(JSONObject object, GraphResponse response) {
                        Log.v(TAG, response.toString());

                        try {
                            String name = object.getString("name");
                            String email = object.getString("email");
                            String birthday = object.getString("birthday"); // 01/31/1980 format
                        } catch (JSONException e) {
                            Log.e(TAG, "unexpected JSON exception", e);
                        }
                    }
                });
        Bundle parameters = new Bundle();
        parameters.putString("fields", "id,name,email,gender,birthday,picture,cover,age_range,locale,about,location");
        request.setParameters(parameters);
        request.executeAsync();
    }

I've included my pointless attempt at using facebook.me()... Just for reference...
I'm setting up the permissions on the FacebookLoginButton like this, and the code works:
        final LoginButton loginButton = (LoginButton)findViewById(R.id.login_button);
        loginButton.setCompoundDrawables(drawable, null, null, null);
        loginButton.setReadPermissions(Arrays.asList(
                "public_profile", "email", "user_birthday", "user_friends", "user_about_me", "user_location"));

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39519544-how-to-convert-a-newmerequest-call-to-use-retrofacebook?utm_campaign=plugin&utm_content=tracker%2F17798003&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F17798003&utm_medium=issues&utm_source=github).

Hi @loudenvier ,
You can use this api to login with needed permissions, but
final Facebook facebook = Facebook.create(activity);

loginButton.setOnClickListenter(v -> {
  logInWithReadPermissions(Arrays.asList("public_profile", "email", "user_birthday", "user_friends", "user_about_me", "user_location"))
  .flatMap(login -> facebook.getProfile())
  .subscribe(profile -> {
     System.out.println(profile.name());
     System.out.println(profile.email());
     System.out.println(profile.birthday());
  });
})

I've tested this example using v4 version and I'm not obtaining any print so I've changed to this code:
`
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
Facebook facebook = Facebook.create(this);
setContentView(R.layout.activity_home);
    //Facebook Button
    LoginButton button_login_facebook = (LoginButton) findViewById(R.id.button_login_facebook);

    button_login_facebook.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View view) {
            facebook.logInWithReadPermissions(Arrays.asList("public_profile",
                    "email",
                    "user_birthday"))
                    .flatMap(
                            loginResult -> {
                                Log.d("HomeActivity", "LoginResult: " + loginResult);
                                return null;
                            },
                            throwable -> {
                                Log.d("HomeActivity", "Error: " + throwable);
                                return null;
                            },
                            () -> {
                                Log.d("HomeActivity", "Completed");
                                return null;
                            });
        }
    });
}

`
but it never prints the result of  Log.d("HomeActivity", "LoginResult: " + loginResult); or even 'Log.d("HomeActivity", "Completed");'
I forced an error like removing the facebook activity from manifest and it prints the result of  Log.d("HomeActivity", "Error: " + throwable.getMessage()); and it prints the error correctly.
I get this on the log but nothing more:
4-05 17:21:32.047 15867-15867/com.xxxxx D/RetroFacebook: request new: public_profile 04-05 17:21:32.047 15867-15867/com.xxxxx D/RetroFacebook: request new: email 04-05 17:21:32.047 15867-15867/com.xxxxx D/RetroFacebook: request new: user_birthday
Any ideia?
Thanks in advance.

Hi @ejbp,
Did you override onActivityResult() like this:
XXXActivity extends Activity {
    // ..
    @Override
    protected void onActivityResult(int requestCode, int resultCode, Intent data) {
        super.onActivityResult(requestCode, resultCode, data);
        facebook.onActivityResult(requestCode, resultCode, data);
}

I think I forgot to write on README, sorry.

Yes. That was the issue. Thank you very much.
Nice lib, by the way. Thanks for that too.


Uncaught Exception: Attempting to call a function in a renderer window that has been closed or released. Function provid

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.0.1
Time: Tue Mar 15 2016 09:50:51 GMT-0600 (Hora estándar central (México))
Error:
Attempting to call a function in a renderer window that has been closed or released. Function provid
Error: Attempting to call a function in a renderer window that has been closed or released. Function provided here: Object.<anonymous> (D:\Users\praxis03\AppData\Local\GPMDP_3\app-3.0.1\resources\app\build\inject\GPMInject\interface\mouseButtonNavigation.js:8:8.
    at BrowserWindow.callIntoRenderer (D:\Users\praxis03\AppData\Local\GPMDP_3\app-3.0.1\resources\atom.asar\browser\lib\rpc-server.js:201:19)
    at emitTwo (events.js:92:20)
    at BrowserWindow.emit (events.js:172:7)

This issue was created automatically inside the uncaughtException handler

Closing this automatically reported issue as a duplicate of #470


Roll Flutter Engine from 39f5e4cbaed9 to 5aadda2f40b1 (1 revision)

https://github.com/flutter/engine/compare/39f5e4cbaed9...5aadda2f40b1
2023-02-07<EMAIL_ADDRESS>Roll Skia from 419bb63e733d to 83da27e4cd3a (1 revision) (flutter/engine#39448)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC bdero@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


SAVEPOINT Doc Update

Re: SAVEPOINT
This page should state that, when savepoint cockroach_restart is used, a future release savepoint cockroach_restart is a commit - i.e. the only thing that can follow it is a commit statement (which is a no-op), and rolling back afterwards is not possible. All of this is not compatible with Postgres.

Closing as out of date.


Regression with deployment in version 4.8.0 to camunda version 7.8.0

Describe the Bug
After upgrading from modeller 4.7.0 to 4.8.0, it's not possible to do deployments from the modeller anymore.
I'm quite sure it's due to the /engine-rest/version call that is being made now, but that endpoint isn't available on camunda version (7.8.0). I can see that modeller 4.8.0 is trying to call that endpoint, but it returns a 404.
Steps to Reproduce

use camunda modeller 4.8.0
use camunda 7.8.0
try deployment
nothing happens (not even an error message)

Expected Behavior
deploy
Environment

OS: Ubuntu
Camunda Modeler Version: 4.8.0
Execution Platform: Camunda Platform
Installed plug-ins: N/A

I was able to reproduce this issue locally. Thank you for reporting.
The problem is within the DeploymentTool. We try to retrieve the version and when the call fails, deployment is aborted. So to fix this, we could make sure that the deployment continues even if we cannot detect the version.

As Camunda Platform 7.8.0 is out of support, we are rather not prioritising this issue. Still, feel free to implement a fix. We will happily accept a pull request.


Refactor search engine stuff

progress for this is going to be in the same branch as #7, so fix-google-search (see PR #9)

some higher level goals for the cleanup

[ ] separate clearbit API stuff from google.py
[ ] dont put reverse image search and text search stuff together, should be separate
[ ] test and update non-google engine impls
[ ] documentation
[ ] reduce imports + dependencies where possible

tbh it looks like most of the bing engine was just copy pasted code from google, i highly doubt it actually works.

same CSS classes for extracting search result URLs
same code for detecting rate limits (based on specific warning message from the engine)
uses www.google., https://www.google.com/imgres?, translate.google. and webcache.googleusercontent. to verify URLs (I doubt bing uses those names)

Can confirm by comparing source is that the bing source is almost entirely copied from google

Yandex text search no work: it has better robot detection, after changing from HTTP to HTTPS requests (without change it defo doesnt work) every request simply gets a response with a captcha (Please confirm that you and not a robot are sending requests)


Japanese feedback

Sorry, I know this isn't the right direct route but is there a way to escalate feedback to the localization team? Most Azure docs have separate feedback streams for each language but that doesn't seem to be enabled for Dynamics.
In Japanese, the section on "customer-insights services" is still translated as "Customer Insights サービス". Leaving aside the incredibly confusing naming issue for a moment, those references need to be cleaned up, ideally into something like 顧客分析サービス that translates the meaning instead of bringing it over like a product name.
This was fixed in English in June but apparently the significance was not apparent in localization (namely, that Customer Insights is a discontinued service and not the same as what is discussed here).

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

ID: d2df3185-bb74-f7be-c02a-0f5553e0d6d1
Version Independent ID: 0cc238a3-a149-fff5-5a92-37b2f8805692
Content: Configure core marketing functionality in Dynamics 365 for Marketing
Content Source: ce/marketing/marketing-settings.md
Service: dynamics-365-marketing
GitHub Login: @kamaybac
Microsoft Alias: kamaybac

Thank you for reporting this @dcbrown16 . I'll forward the issue to our translation team.


Creating a sequential znode under / doesn't work.

This fails:
from kazoo.client import KazooClient
k = KazooClient("localhost:2181")
k.start()
k.create("/", "", sequence=True)
....
BadArgumentsError
...

Checking with zk-dump [1], this is what I see:
$ sudo zk-dump --iface lo --zookeeper-port 2181
Writing log files to disk in /var/tmp
15:48:51:490416 CreateRequest(size=49, xid=2, path=//, ephemeral=False, sequence=True, client=<IP_ADDRESS>:38587)
————————►15:48:51:518140 FailedCreateReply(xid=2, zxid=42, error=-8, path=, client=<IP_ADDRESS>:38587)

kazoo.protocol.paths#normpaths doesn't handle '/', when trailing=True. PR coming up in a bit.
[1] https://github.com/twitter/zktraffic/

It appears this was closed by #262


[ML] fix(next-pylint): Resolve consider-using-dict-items, use-dict-literal, consider-using-dict-items

Description
This pull request is part of a effort to ready the Azure ML Python SDK for an impending bump to the versions of pylint and azure-pylint-guidelines-checker that is used in our CI.
This pull request specifically resolves:

C0201 (consider-iterating-dictionary)
R1735 (use-dict-literal)
C0206 (consider-using-dict-items)

Validated with:
pylint==2.15.8
azure-pylint-guidelines-checker=0.0.8
pylint --rcfile=../../../eng/pylintc --disable=all --enable=C0201,R1735,C0206 azure/
General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


coerceIn is unnecessary

If I understand coerceIn correctly it does the same thing as num.clamp:
https://api.dartlang.org/stable/2.7.0/dart-core/num/clamp.html
The other two coerce methods do the same thing as min() and max(). Maybe your methods are slightly easier to understand, but min and max are so common in other programming languages that keeping the convention might be more important than introducing a second way to do the same thing. If you still want to keep the methods maybe you could at least change the implementation to use min / max instead of the more verbose comparison.

I did not even know clamp() existed. I'm not sure about how to move forward. Many users come from Kotlin and maybe we should keep some duplicates for them.
This is also related to #10 and #16

We decided to keep some duplicate methods to make finding them easier for new users (for example Kotlin users)


Coordinates

Added first pass at coordinate transformations using the astropy frames code, + a simple script showing how the transformations are made for most frames.
Currently it is rather slow and needs more documentation. Also, we need a good system in place for providing the current pointing direction (currently hard coded) of a given telescope as well as the array. Some small changes were also made to the Hillas parameter maker to perform parameterisation in the nominal system.
Not sure if this is ready for the master yet, but comments on how to get this into shape and discussion of how to pass on pointing information would be helpful.

I don't like the idea of doing any transforms inside the hillas_parameters routine - it should be completely generic. Hillas parameters can be computed regardless of the system.  Also, since transforms are slow if done event-by-event, we should avoid doing them in any function that is called event-wise.
The correct way to do it would be then to read a set of events, transform them to the proper system (all at once), and then do the hillas parameterization (or else do the transform after the parameterization, which is maybe even faster - e.g. transform the parameters)
That is one of the negative "lessons learned" from HESS: coordinate transforms are done and undone many times, and they dominate the CPU when processing. That's very inefficient. We should avoid doing any transforms when possible, and only do them once they are really needed.
What should can do now is keep the hillas_parameters as before, and make wrapper class that does the transform and calls the hillas routine.

Hi, agreed keeping this code within the hillas code doesn't seem like a great idea. I'm a little reluctant about transforming the Hillas parameters themselves as for some telescopes (maybe the SC based ones) we may need to perform a non linear transformation to get from the camera frame to the nominal frame, due to distortions in the FoV which will not really work with Hillas params.
Already the the code will process transformations of an N dimensional numpy array. Does this need a wrapper class? or will ultimately the "chunked" data be processed directly.

I have made some changes to the code to remove the modification to the Hillas parameter maker and perform the Hillas reconstruction elsewhere.


Bump kube_version to v1.8.3

As title

Signed

Added Github as a social network login

Added signature to this project

Please include changes to the following files:
inventory/group_vars/k8s-cluster.yml
README.md

That file is already included in this PR:
grep kube_version inventory/group_vars/k8s-cluster.yml
kube_version: v1.8.3

README.md updated to reflect v1.8.3

FYI, identical to #1971

Gah, good spot! Closing.


⚠ Bofrost.de has degraded performance

In 3929c90, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1522 ms

Resolved: Bofrost.de performance has improved in f163c03.


Cannot sign into new installation

I have installed the Portainer setup method, with docker.
The issue I am currently having though is this:

I cannot get any further. It locks me out for some reason. Here are the logs:
_papermerge_redis_1_logs.txt
_papermerge_db_1_logs (1).txt
_papermerge_es_1_logs (1).txt
_papermerge_frontend_1_logs.txt
_papermerge_ws_server_1_logs.txt
_papermerge_backend_1_logs.txt
_papermerge_worker_1_logs.txt
_papermerge_backend_init_1_logs (1).txt
_portainer_logs.txt
_papermerge_traefik_1_logs.txt
Please help. I don't know what to do at this point.

Hmm, yeah... I am using Ubuntu server 20.04 LTS with docker and Portainer installed. It has no GUI (being server) so I have to use a separate PC to connect to it. I did not change any of the config (Besides the other issue you mentioned), so I don't know what could be causing it.

Ohhhhh I just looked at which log you were talking about. That error is because I am using portainer locally only, and it is using a self-generated TLS certificate. I have to click the "proceed to this site anyways" in chrome when I go to the portainer web portal.

Ok, the issue still happens. I used the new setup, with the HOSTNAME variable, and it now has the old 404: File Not Found error again.

Would this have anything to do with the error?

2022-05-03 13:32:39.193 UTC [69] STATEMENT:  SELECT "core_user"."password", "core_user"."last_login", "core_user"."is_superuser", "core_user"."username", "core_user"."first_name", "core_user"."last_name", "core_user"."email", "core_user"."is_staff", "core_user"."is_active", "core_user"."date_joined", "core_user"."id", "core_user"."role_id", "core_user"."home_folder_id", "core_user"."inbox_folder_id", "core_user"."created_at", "core_user"."updated_at" FROM "core_user" WHERE "core_user"."username" = 'admin' LIMIT 21,
2022-05-03 13:32:39.193 UTC [69] ERROR:  relation "core_user" does not exist at character 416

Also noticed a bunch of python errors in the backend_init container:
_papermerge_backend_init_1_logs (2).txt
.

AHA! I found something! the 1st line in that backent_init log is:
File "/venv/lib/python3.8/site-packages/django/db/backends/base/base.py", line 603, in temporary_connection, django.db.utils.ProgrammingError: relation "core_user" does not exist
And the error in the Database is:
2022-05-03 13:32:39.193 UTC [69] STATEMENT:  SELECT "core_user"."password", "core_user"."last_login", "core_user"."is_superuser", "core_user"."username", "core_user"."first_name", "core_user"."last_name", "core_user"."email", "core_user"."is_staff", "core_user"."is_active", "core_user"."date_joined", "core_user"."id", "core_user"."role_id", "core_user"."home_folder_id", "core_user"."inbox_folder_id", "core_user"."created_at", "core_user"."updated_at" FROM "core_user" WHERE "core_user"."username" = 'admin' LIMIT 21,
2022-05-03 13:32:39.193 UTC [69] ERROR:  relation "core_user" does not exist at character 416

Notice the core_user errors correlate. There is an error creating the core_user field in the database, and then the backend fails to read it because core_user doesn't exist.

Also noticed a bunch of python errors in the backend_init container: _papermerge_backend_init_1_logs (2).txt

In log there is error message saying:
django.db.utils.OperationalError: could not connect to server: Connection refused

	Is the server running on host "db" (<IP_ADDRESS>) and accepting

	TCP/IP connections on port 5432?

Which means that for some reason it connect connect to database. In docker compose file, backend_init depends on db.

There is an error creating the core_user relation in the database, and then the backend fails to read it because core_user doesn't exist.

Because database was not up and running.

Huh. The database is running. I don't know why it would be connecting.

Have you looked into doing something like this: https://docs.docker.com/compose/networking/#links
If you add a link to the backend_init compose section connecting it to db, that might help IDK.

Ok, the issue still happens. I used the new setup, with the HOSTNAME variable, and it now has the old 404: Page Not Found error again.

I discovered Papermerge today and gave it a try. This setup was started via docker-compose on a dedicated SLES 15 SP3 host. I experienced the same issues as described here during startup ("core_user" missing, db connection refused... seem to be irrelevant here) and also that "404: Page Not Found" error.
I configured "HOSTNAME" in .env as a full-qualified hostname ("somehost.my.domain"). Using the FQDN in the browser lead to that 404 error while using just the short name worked perfectly and presented the login page as expected.
Searching for an explanation revealed that docker-compose just used the local part "somehost" when ${HOSTNAME} was used in docker-compose.yml.
I finally solved this 404 error for my setup and it seems that #22 is broken by design (@ciur):
"HOSTNAME" from the .env file is simply not used if that variable also exists in the shell environment where docker-compose is executed. On my system "HOSTNAME" is set automatically and contains the local part of my system's hostname.
See docker-compose documentation regarding environment variables

You can set default values for environment variables using a .env file, which Compose automatically looks for in project directory (parent folder of your Compose file). Values set in the shell environment override those set in the .env file.

I fixed this by just renaming the variable HOSTNAME to USE_HOSTNAME in .env and docker-compose.yml.

@cupracer , awesome research! Thank you!
@gljones2001, can you please confirm if renaming HOSTNAME variable  to USE_HOSTNAME fixes your issue ?

Closing the ticket due to inactivity.


Upload nbm to Maven Central

For PP3: https://netbeans-vm.apache.org/pluginportal/

Done. https://netbeans-vm.apache.org/pluginportal/catalogue/?id=24


notification alert by voip call from the system to any social media like whatsapp, telegram, signal,...etc

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
New Notification
🔖 Feature description
Problem
Some critical alerts need to be notified by voip call through a system to the client by doing any integration.
please consider it as high feature which you will be a different and best from others like zabbix...
please note that critical systems need to be notified when there is an issue immediately by such feature because email or any other notification not effective on such occasions.
✔ Solution
we need the kuma server to do voip call to the client when a particular server or application goes down or not responding or latency,...
it a critical alert notification because all monitoring tools didn't introducing it, and the NOC engineers need to be notified on time.
thanks in advance
❓ Alternatives
No response
📝 Additional Context
No response

I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/3295
If you agree, please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage.
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^
Note that bot's normally cannot call users:

Telegram: https://stackoverflow.com/q/70438115
Whatsapp/Signal does not officially support bots or sending messages programatically as far as I can tell from their docs

To prevent misscomunication: we are open to such notifiation providers, here is our contribution guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

As this issue is covered by https://github.com/louislam/uptime-kuma/issues/3295 and thus a duplicate I am going to close this issue in favor of the other one.


[TASK] Follow the traditional builder pattern in MultiJobRunner

Overview
Right now, the MultiJobRunner kind of acts as a nested builder, in that it itself is a builder, but also has the with_job() method, which then spins off another builder.
That makes it a little difficult to read:
#[gadget_sdk::main(env)]
async fn main() {
    let x_square = blueprint::XsquareEventHandler {
        service_id: env.service_id.unwrap(),
        client: client.clone(),
        signer,
    };

    let x_square2 = blueprint::XsquareEventHandler {
        service_id: env.service_id.unwrap(),
        client: client.clone(),
        signer,
    };

    MultiJobRunner::new(&env)
        .with_job()
        .with_default_price_targets()
        .finish(x_square)
        .with_job()
        .with_default_price_targets()
        .finish(x_square2)
        .run()
        .await?;
}

It'd be better to instead:

Keep MultiJobRunner simple. You want to add a job, use MultiJobRunner::job().
Remove the with_ prefixes, builders typically use, for example, price_targets(PriceTargets) rather than with_price_targets(PriceTargets).
Keep defaults as default. When creating a JobBuilder, it should implicitly have the default price targets, rather than calling with_default_price_targets().

Ideally, the above example would look like:
#[gadget_sdk::main(env)]
async fn main() {
    let x_square = blueprint::XsquareEventHandler {
        service_id: env.service_id.unwrap(),
        client: client.clone(),
        signer,
    };

    let x_square2 = blueprint::XsquareEventHandler {
        service_id: env.service_id.unwrap(),
        client: client.clone(),
        signer,
    };

    MultiJobRunner::new()
        .job(JobBuilder::new(&env).job(x_square).build())
        .job(JobBuilder::new(&env)
                .price_targets(/* Something, if you want */)
                .job(x_square2)
                .build())
        .run()
        .await?;
}

:100:


WRO-12044: Increase code coverage for Popup/PopupTabLayout

Enact-DCO-1.0-Signed-off-by: Stanca Pop<EMAIL_ADDRESS>Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Code coverage for Popup and PopupTabLayout needs to be over 80%.
Resolution
Increased code coverage to 80.88% for Popup and to 61.90% for PopupTabLayout.
Additional Considerations
Links
WRO-12044
Comments

Could you please add one more tc to PopupTabLayout to verify panel navigating via left key? I think it can be implemented in a similar way as below.
test('should fire onBack event when left key pressed from the second TabPanel', () => {
		const onBack = jest.fn();
		render(
			<FloatingLayerController>
				<PopupTabLayout open>
					<Tab title="Tab Title">
						<TabPanels rtl={false} index={1} onBack={onBack}>
							<TabPanel>
								<Item>Item 1</Item>
								<Item>Item 2</Item>
							</TabPanel>
							<TabPanel>
								<Item>Item 3</Item>
								<Item>Item 4</Item>
							</TabPanel>
						</TabPanels>
					</Tab>
				</PopupTabLayout>
			</FloatingLayerController>
		);

		const firstItem = screen.getByText('Item 3');
		leftKeyDown(firstItem);
		expect(onBack).toHaveBeenCalled();
	});


Missing type definition for error in the return type of useQuery

When the following simple query is compiled with Typescript:
const Demo = () => {
   const { data, error, loading } = useQuery(GET_DEMOS)
}

Typescript complains about error not being found on the return type of useQuery, error message is as follows:
Property 'error' does not exist on type 'ApolloQueryResult<any> &
Pick<ObservableQuery<any, OperationVariables>, "refetch" | "startPolling" | "stopPolling" | "updateQuery"> &
{ fetchMore<K extends string | number>(fetchMoreOptions: FetchMoreQueryOptions<...> &  FetchMoreOptions<...>): Promise<...>; }'.

The definition of ApolloQueryResult can be found in the apollo-client repo, and apparently only errors are defined there. Changing error to errors in the code above does fix the problem. However, to maintain consistency with react-apollo, it would be great to define error.

It should be fixed since v0.4.0. There is a difference between errors (which are returned by your GraphQL server resolvers) and error (e. g. network error, but since v0.4.0 this field is also set if there is anything in errors).


issue: [TYPO]: there should be ',' use between "sure" and "you"

Fixes #3964
Describe the changes you have made in this PR -

[x] Added ',' between 'sure' and 'you' for promote member modal
[x] Added ',' between 'sure' and 'you' for demote mentor modal
[x] Added ',' between 'sure' and 'you' for remove assignment modal
[x] Added ',' between 'sure' and 'you' for remove member modal

Screenshots of the changes (If any) -
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

@vedant-jain03  Thank you for the merge sir. I was looking to get into GSoC, but it is too late for 2023 so i am starting early for 2024. 😄


Ensure items that had no ultimate drag destination get destroyed

Addresses #133

Hi @mattgodbolt , thank you for your pull request.
I was wondering: I have started running a tech startup (deepstream.io/deepstreamhub) a few month ago and it is a crazy amount of work. As a result, I can't help but neglect GoldenLayout and pull requests are piling up.
It's a good and widely used project and I wouldn't want to see it die. Would you be interested in becoming a maintainer (be elevated to "admin", curate the project etc.)? Happy to promote/ announce your role in any way you wish.

Hi Wolfram,
I'm flattered: thanks! I'm pretty rammed at the moment with my own stuff
too, so can't currently devote any meaningful time to GL I'm afraid. That
said: I plan on using it on Compiler Explorer (https://gcc.godbolt.org) and
will need a way to fix the (minor) issues I'm finding...
If you're absolutely stuck for willing volunteers I'd be happy to review
PRs and whatnot. Is there a test suite anywhere? When I made my change I
tried running 'grunt' locally to see if there was a test suite but it
seemed not (plus the paths seem hardcoded for Windows and I had to hack it
to even get it running on Linux).
On Sun, Sep 11, 2016 at 11:45 PM Wolfram Hempel<EMAIL_ADDRESS>wrote:

Hi @mattgodbolt https://github.com/mattgodbolt , thank you for your
pull request.
I was wondering: I have started running a tech startup (
deepstream.io/deepstreamhub) a few month ago and it is a crazy amount of
work. As a result, I can't help but neglect GoldenLayout and pull requests
are piling up.
It's a good and widely used project and I wouldn't want to see it die.
Would you be interested in becoming a maintainer (be elevated to "admin",
curate the project etc.)? Happy to promote/ announce your role in any way
you wish.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/deepstreamIO/golden-layout/pull/134#issuecomment-246245565,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmsdTrozfWP9T86tyFK5YtTFC3BViUvks5qpNkBgaJpZM4J3j3c
.

Dear WolframHempel and mattgodbolt, sorry for chiming in. I've started using this amazing tool few weeks ago on top of a new quite complex client-server application that will (hopefully) become a start up pretty soon. I found it so beautiful that I truly felt in love with it. However, it's so sad to see that the last commit has been made 4 months ago and, as wolfram highlighted, the PR are piling up. So... please guys, don't let it die. Let's find a way to involve new people on it, but wasting all the time and the beautiful work spent on it would truly be a tech crime. I sincerely appreciate your efforts.Thanks

Thanks so much both - and again, my apologies for not being able to be more active. I think it makes sense to spread the load between a few contributors interested in the project - @mattgodbolt happy to elevate you and chase some more together. GL has a test suite, but it isn't as comprehensive as it could be. When I originally wrote it, it had significantly more tests - but I counter-intuitively reduced them later as I found that I wasn't able to test the complex d&d user interactions that GoldenLayout is all about and unit tests just fixated whatever the current behavior was

@WolframHempel I'd be delighted to help. I'm loving GL and I'm now using it on a (currently non-public) beta of https://gcc.godbolt.org but I'm already getting a few bug reports from users that appear to be related to GL. It'd be great to be able to fix them up :)
I'd need to make a few changes to get GL more "cross-platform", but I'm happy to do that, with the caveat that I don't have easy access to a Windows box to test on. I can help set up a continuous build though to get better auto coverage.

@mattgodbolt really appreciated. I've added you as a collaborator with full access to this repo. If there's anything I can help with you can also reach me at<EMAIL_ADDRESS>

Many thanks!


HBASE-25766 Introduce RegionSplitRestriction that restricts the …

…pattern of the split point

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 13s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 20s
master passed

+1 :green_heart:
compile
3m 21s
master passed

+1 :green_heart:
checkstyle
1m 14s
master passed

+1 :green_heart:
spotbugs
2m 13s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 59s
the patch passed

+1 :green_heart:
compile
3m 18s
the patch passed

+1 :green_heart:
javac
3m 18s
the patch passed

-0 :warning:
checkstyle
1m 12s
hbase-server: The patch generated 5 new + 150 unchanged - 0 fixed = 155 total (was 150)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
19m 54s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
2m 22s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 13s
The patch does not generate ASF License warnings.

51m 32s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3150

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 3219d3f0e50a 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / f9e928e5a7

Default Java
AdoptOpenJDK-1.8.0_282-b08

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
86 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 14s
Docker mode activated.

I don't think the unit test failures are related to this change. When I did run the failed tests locally, they were successful.
@Apache9 Can you please review it? Thanks.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  7s
Docker mode activated.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 38s
the patch passed

+1 :green_heart:
compile
1m  2s
the patch passed

+1 :green_heart:
javac
1m  2s
the patch passed

+1 :green_heart:
shadedjars
7m 45s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 35s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
149m 25s
hbase-server in the patch passed.

178m 13s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3150

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 83f05932c161 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 33e886c6cc

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/3/testReport/

Max. process+thread count
4297 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/3/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 58s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
5m  3s
master passed

+1 :green_heart:
compile
1m 18s
master passed

+1 :green_heart:
shadedjars
8m 39s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
master passed

-0 :warning:
patch
9m 33s
Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 47s
the patch passed

+1 :green_heart:
compile
1m 18s
the patch passed

+1 :green_heart:
javac
1m 18s
the patch passed

+1 :green_heart:
shadedjars
8m 33s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
206m 12s
hbase-server in the patch passed.

241m  2s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3150

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 0fd0a5c87967 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 33e886c6cc

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/3/testReport/

Max. process+thread count
3113 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/3/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  9s
Docker mode activated.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 59s
the patch passed

+1 :green_heart:
compile
3m 16s
the patch passed

+1 :green_heart:
javac
3m 16s
the patch passed

-0 :warning:
checkstyle
1m 12s
hbase-server: The patch generated 1 new + 150 unchanged - 0 fixed = 151 total (was 150)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
19m 43s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
2m 22s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 11s
The patch does not generate ASF License warnings.

50m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3150

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 73ffebe1d3fd 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 33e886c6cc

Default Java
AdoptOpenJDK-1.8.0_282-b08

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/4/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
86 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/4/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  7s
Docker mode activated.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 49s
the patch passed

+1 :green_heart:
compile
1m 16s
the patch passed

+1 :green_heart:
javac
1m 16s
the patch passed

+1 :green_heart:
shadedjars
8m 30s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 42s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
206m  1s
hbase-server in the patch passed.

239m 44s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/5/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3150

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7ad76eb44869 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 33e886c6cc

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/5/testReport/

Max. process+thread count
3192 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/5/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 12s
Docker mode activated.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 44s
the patch passed

+1 :green_heart:
compile
1m 19s
the patch passed

+1 :green_heart:
javac
1m 19s
the patch passed

+1 :green_heart:
shadedjars
8m 37s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
206m 55s
hbase-server in the patch passed.

240m 47s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/6/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3150

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9523c762fa60 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 781da1899a

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/6/testReport/

Max. process+thread count
3150 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/6/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 17s
Docker mode activated.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 42s
the patch passed

+1 :green_heart:
compile
1m 18s
the patch passed

+1 :green_heart:
javac
1m 18s
the patch passed

+1 :green_heart:
shadedjars
8m 35s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 42s
hbase-server generated 8 new + 80 unchanged - 0 fixed = 88 total (was 80)

_ Other Tests _

-1 :x:
unit
205m 28s
hbase-server in the patch failed.

239m 18s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/7/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3150

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ce740e4a1f9e 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 781da1899a

Default Java
AdoptOpenJDK-11.0.10+9

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/7/artifact/yetus-jdk11-hadoop3-check/output/diff-javadoc-javadoc-hbase-server.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/7/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/7/testReport/

Max. process+thread count
3192 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3150/7/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@saintstack @Apache9 I added a WARN message when the user-specified split point is over-ruled by the restriction as follows:
https://github.com/apache/hbase/pull/3150/files#diff-1302b8959c14450ef8cb33e8825f48d3b6ad19a0f820cacd58b498c36b1997baR122-R127
And I also added JavaDoc for RegionSplitRestriction as follows:
https://github.com/apache/hbase/pull/3150/files#diff-84b259559f75b99c101829aeebe86d9baa3686d7ced8892806ccf11158b1f41dR27-R63
Please let me know if you have any other things we should to do here.
Thank you.


WSL2 opens in home directory instead of directory corresponding to Windows working directory

No reproducible steps, but wanted to create an issue to make sure this is logged:
I've heard from various users that WSL2 sometimes doesn't come up in current working dir  (corresponding to the folder where started in Windows), but starts in the home directory instead.
Rebooting the VM seems to fix the issue.
https://stackoverflow.com/questions/56609858/vscode-remote-release-and-wsl-2
https://github.com/microsoft/vscode-remote-release/issues/21#issuecomment-506321702
https://github.com/microsoft/vscode-remote-release/issues/883
I'l probably make a fix to VSCode Remote WSL to no longer rely that the cwd is mapped to unblock users.

Thanks @aeschli - Not much to go on here, and I'm unable to reproduce this myself.  Please keep me updated if you find out any more information.

@benhillis I ran into this issue when I turned Windows Sandbox feature on, then I turned it off and the issue is gone. I tried to reproduce by turning Windows Sandbox on again, but the issue wasn't reproduced this time. Not sure if this helps because I failed consistently reproducing it, my OS build version is 18930.1000.

You're a lifesaver bro.
Thanks


Create basic landing page

Create a basic landing page for https://dfetch.github.io/
Some basic bootstrap gave me:
https://htmlpreview.github.io/?https://github.com/dfetch-org/dfetch/blob/feature/landing-page/doc/landing.html

Deployed first iteration on https://dfetch-org.github.io/


FileNotFoundException, gurobi90.netstandard20

Hello.
I obtained gurobi dlls, but I cannot figure out where to put them, so the GUI app works in HybridStyle.
Can you please give more info on that?
System.IO.FileNotFoundException: 'Could not load file or assembly 'gurobi90.netstandard20, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=21e2c4b1860157bc'. The system cannot find the file specified.'

I have gurobi90.netstandard20.dll of exact same version <IP_ADDRESS>

I hope this was resolved, if not feel free to re-open.


Added unbindEvent() to reload.

This pairs the bind/unbindEvent when reload() is being used.

This PR is for issue https://github.com/angular-ui/ui-scroll/issues/226.


feat: add create cli command

Current dependencies on/for this PR:

main

PR #8

PR #9   👈

This stack of pull requests is managed by Graphite.

Merge activity

Nov 6, 9:49 AM: @richardcase started a stack merge that includes this pull request via Graphite.


CarlaUE4/Plugins/StreetMap/Source/StreetMapRuntime/Private/StreetMapComponent.cpp:15:10: fatal error: 'Carla/BlueprintLibary/MapGenFunctionLibrary.h' file not found

CARLA version:0.9.14
Platform/OS:ubuntu18.04.5
Unreal Engine Version: 4.26.2
Problem you have experienced:
I want to use StreetMap unreal plugins (https://github.com/carla-simulator/StreetMap),but when i make launch, it show errors:
carla-0.9.14/Unreal/CarlaUE4/Plugins/StreetMap/Source/StreetMapRuntime/Private/StreetMapComponent.cpp:15:10: fatal error: 'Carla/BlueprintLibary/MapGenFunctionLibrary.h' file not found。How to solve it?

请问一下这个问题你解决了吗

That Plugin depends completely on CARLA so is installed with carla when you make a make launch. Please, try to use it with CARLA itself. if you do not want to, please refer to original plugin https://github.com/ue4plugins/StreetMap


Just a message

I notice that you have forked my github profile repo ever.
It is a special repository that can prepend custom information into Github-profile via a README.md.
You can create a new public repository named with your username, and initialize it with a README to get started.

Thanks for the reminder, this was a mistaken click. I noticed the fork a few days ago and already deleted it. I will create my own repo later.

I notice that you have forked my github profile repo ever.
It is a special repository that can prepend custom information into Github-profile via a README.md.
You can create a new public repository named with your username, and initialize it with a README to get started.


How to get the current selected item ID in the QuickLauch ?

I'm currently developing a BreadCrumb in SPFX with React and i need to get the current id of the selected item in the  QuickLauch  menu.

I'm currently searching the item exploring the object in the context (context.pageContext.legacyPageContext.navigationInfo.quickLaunch) .
Is there an other ways to get the current QuickLauch selected item id ?

This is not exposed via an API. As such, there's no supported way to do this. When I say "supported", I mean anything you do would be inspecting the DOM & classes to get the selected item, and those are subject to change without notice.

Ok ok Thank you for the response


bctoolbox: 5.1.17 -> 5.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bctoolbox/versions.
meta.description for bctoolbox is: "Utilities library for Linphone"
meta.homepage for bctoolbox is: "https://gitlab.linphone.org/BC/public/bctoolbox"
meta.changelog for bctoolbox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.1.45 with grep in /nix/store/fz2q4w2gjxm0jyq3kqmdcxc3mhsakd41-bctoolbox-5.1.45
found 5.1.45 in filename of file in /nix/store/fz2q4w2gjxm0jyq3kqmdcxc3mhsakd41-bctoolbox-5.1.45

Rebuild report (if merged into master) (click to expand)

19 total rebuild path(s)

13 package rebuild(s)

13 x86_64-linux rebuild(s)
6 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fz2q4w2gjxm0jyq3kqmdcxc3mhsakd41-bctoolbox-5.1.45 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bctoolbox https://github.com/r-ryantm/nixpkgs/archive/b83e6c9038bdb96c96e77390f969a826a3a57b5e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fz2q4w2gjxm0jyq3kqmdcxc3mhsakd41-bctoolbox-5.1.45
ls -la /nix/store/fz2q4w2gjxm0jyq3kqmdcxc3mhsakd41-bctoolbox-5.1.45/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

13 packages built:

bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Maintainer pings
cc @7c6f434c @jluttine for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bctoolbox/versions.
meta.description for bctoolbox is: "Utilities library for Linphone"
meta.homepage for bctoolbox is: "https://gitlab.linphone.org/BC/public/bctoolbox"
meta.changelog for bctoolbox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.1.55 with grep in /nix/store/jp42mbyj3fbc4l8wkjasy15x7x08hj73-bctoolbox-5.1.55
found 5.1.55 in filename of file in /nix/store/jp42mbyj3fbc4l8wkjasy15x7x08hj73-bctoolbox-5.1.55

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jp42mbyj3fbc4l8wkjasy15x7x08hj73-bctoolbox-5.1.55 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bctoolbox https://github.com/r-ryantm/nixpkgs/archive/34966deda5b98eb6dbfda813b20015d7e1a96542.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jp42mbyj3fbc4l8wkjasy15x7x08hj73-bctoolbox-5.1.55
ls -la /nix/store/jp42mbyj3fbc4l8wkjasy15x7x08hj73-bctoolbox-5.1.55/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

13 packages built:

bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Maintainer pings
cc @7c6f434c @jluttine for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bctoolbox/versions.
meta.description for bctoolbox is: "Utilities library for Linphone"
meta.homepage for bctoolbox is: "https://gitlab.linphone.org/BC/public/bctoolbox"
meta.changelog for bctoolbox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.1.58 with grep in /nix/store/xzhrwj28y4kvw84rn1sc0p68mmz76qnc-bctoolbox-5.1.58
found 5.1.58 in filename of file in /nix/store/xzhrwj28y4kvw84rn1sc0p68mmz76qnc-bctoolbox-5.1.58

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xzhrwj28y4kvw84rn1sc0p68mmz76qnc-bctoolbox-5.1.58 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bctoolbox https://github.com/r-ryantm/nixpkgs/archive/4b8d7cc79c59ff191b3206d6d8105d925f61b7d1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xzhrwj28y4kvw84rn1sc0p68mmz76qnc-bctoolbox-5.1.58
ls -la /nix/store/xzhrwj28y4kvw84rn1sc0p68mmz76qnc-bctoolbox-5.1.58/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

13 packages built:

bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Maintainer pings
cc @7c6f434c @jluttine for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bctoolbox/versions.
meta.description for bctoolbox is: "Utilities library for Linphone"
meta.homepage for bctoolbox is: "https://gitlab.linphone.org/BC/public/bctoolbox"
meta.changelog for bctoolbox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.1.61 with grep in /nix/store/5radglq0s07sr0rh5lzrs93d16s3x8r2-bctoolbox-5.1.61
found 5.1.61 in filename of file in /nix/store/5radglq0s07sr0rh5lzrs93d16s3x8r2-bctoolbox-5.1.61

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5radglq0s07sr0rh5lzrs93d16s3x8r2-bctoolbox-5.1.61 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bctoolbox https://github.com/r-ryantm/nixpkgs/archive/8ab78a4efae7cae1a9b046f7bd8119aedb70bbb7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5radglq0s07sr0rh5lzrs93d16s3x8r2-bctoolbox-5.1.61
ls -la /nix/store/5radglq0s07sr0rh5lzrs93d16s3x8r2-bctoolbox-5.1.61/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

13 packages built:

bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Maintainer pings
cc @7c6f434c @jluttine for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bctoolbox/versions.
meta.description for bctoolbox is: "Utilities library for Linphone"
meta.homepage for bctoolbox is: "https://gitlab.linphone.org/BC/public/bctoolbox"
meta.changelog for bctoolbox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.1.64 with grep in /nix/store/0b7lgfvfpj4lz8sh9wq91lsyply2dg7v-bctoolbox-5.1.64
found 5.1.64 in filename of file in /nix/store/0b7lgfvfpj4lz8sh9wq91lsyply2dg7v-bctoolbox-5.1.64

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0b7lgfvfpj4lz8sh9wq91lsyply2dg7v-bctoolbox-5.1.64 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bctoolbox https://github.com/r-ryantm/nixpkgs/archive/34b8c64374aeb48a6fb085051de7b3776113b5dd.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0b7lgfvfpj4lz8sh9wq91lsyply2dg7v-bctoolbox-5.1.64
ls -la /nix/store/0b7lgfvfpj4lz8sh9wq91lsyply2dg7v-bctoolbox-5.1.64/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

13 packages built:

bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Maintainer pings
cc @7c6f434c @jluttine for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bctoolbox/versions.
meta.description for bctoolbox is: "Utilities library for Linphone"
meta.homepage for bctoolbox is: "https://gitlab.linphone.org/BC/public/bctoolbox"
meta.changelog for bctoolbox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.1.66 with grep in /nix/store/r8y6jfc5bs7j7af3ihq8s1g601i4wd1l-bctoolbox-5.1.66
found 5.1.66 in filename of file in /nix/store/r8y6jfc5bs7j7af3ihq8s1g601i4wd1l-bctoolbox-5.1.66

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r8y6jfc5bs7j7af3ihq8s1g601i4wd1l-bctoolbox-5.1.66 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bctoolbox https://github.com/r-ryantm/nixpkgs/archive/aa4055c759c92f1036d91926b68ef83058c8675f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r8y6jfc5bs7j7af3ihq8s1g601i4wd1l-bctoolbox-5.1.66
ls -la /nix/store/r8y6jfc5bs7j7af3ihq8s1g601i4wd1l-bctoolbox-5.1.66/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

13 packages built:

bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Maintainer pings
cc @7c6f434c @jluttine for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bctoolbox/versions.
meta.description for bctoolbox is: "Utilities library for Linphone"
meta.homepage for bctoolbox is: "https://gitlab.linphone.org/BC/public/bctoolbox"
meta.changelog for bctoolbox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.1.67 with grep in /nix/store/r1x7ijg7ljx82i7ij7476r4ynkgbh54l-bctoolbox-5.1.67
found 5.1.67 in filename of file in /nix/store/r1x7ijg7ljx82i7ij7476r4ynkgbh54l-bctoolbox-5.1.67

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r1x7ijg7ljx82i7ij7476r4ynkgbh54l-bctoolbox-5.1.67 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bctoolbox https://github.com/r-ryantm/nixpkgs/archive/497a6d59e54476c5294893247e18d93e73d7c238.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r1x7ijg7ljx82i7ij7476r4ynkgbh54l-bctoolbox-5.1.67
ls -la /nix/store/r1x7ijg7ljx82i7ij7476r4ynkgbh54l-bctoolbox-5.1.67/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

13 packages built:

bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Maintainer pings
cc @7c6f434c @jluttine for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bctoolbox/versions.
meta.description for bctoolbox is: "Utilities library for Linphone"
meta.homepage for bctoolbox is: "https://gitlab.linphone.org/BC/public/bctoolbox"
meta.changelog for bctoolbox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.1.71 with grep in /nix/store/nqfj1lj07is2jz4p9x1vxlp8bdh7b1ym-bctoolbox-5.1.71
found 5.1.71 in filename of file in /nix/store/nqfj1lj07is2jz4p9x1vxlp8bdh7b1ym-bctoolbox-5.1.71

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nqfj1lj07is2jz4p9x1vxlp8bdh7b1ym-bctoolbox-5.1.71 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bctoolbox https://github.com/r-ryantm/nixpkgs/archive/c3c80c07625f2ff926309c7cce7653bd7e970f99.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nqfj1lj07is2jz4p9x1vxlp8bdh7b1ym-bctoolbox-5.1.71
ls -la /nix/store/nqfj1lj07is2jz4p9x1vxlp8bdh7b1ym-bctoolbox-5.1.71/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

13 packages built:

bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Maintainer pings
cc @7c6f434c @jluttine for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bctoolbox/versions.
meta.description for bctoolbox is: "Utilities library for Linphone"
meta.homepage for bctoolbox is: "https://gitlab.linphone.org/BC/public/bctoolbox"
meta.changelog for bctoolbox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.1.72 with grep in /nix/store/b4cndc15vbqbdjzwr9b5vqm2pcasd8s4-bctoolbox-5.1.72
found 5.1.72 in filename of file in /nix/store/b4cndc15vbqbdjzwr9b5vqm2pcasd8s4-bctoolbox-5.1.72

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b4cndc15vbqbdjzwr9b5vqm2pcasd8s4-bctoolbox-5.1.72 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bctoolbox https://github.com/r-ryantm/nixpkgs/archive/3905492bd9dfd3bbe0e468a958043d70eca94b0b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b4cndc15vbqbdjzwr9b5vqm2pcasd8s4-bctoolbox-5.1.72
ls -la /nix/store/b4cndc15vbqbdjzwr9b5vqm2pcasd8s4-bctoolbox-5.1.72/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

13 packages built:

bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Maintainer pings
cc @7c6f434c @jluttine for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bctoolbox/versions.
meta.description for bctoolbox is: "Utilities library for Linphone"
meta.homepage for bctoolbox is: "https://gitlab.linphone.org/BC/public/bctoolbox"
meta.changelog for bctoolbox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.2.0 with grep in /nix/store/bay71aj2iwg58h7mk73hb80na0hf96wa-bctoolbox-5.2.0
found 5.2.0 in filename of file in /nix/store/bay71aj2iwg58h7mk73hb80na0hf96wa-bctoolbox-5.2.0

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bay71aj2iwg58h7mk73hb80na0hf96wa-bctoolbox-5.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bctoolbox https://github.com/r-ryantm/nixpkgs/archive/56172aec1a5354e5462f2c3a8777e368739ba697.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bay71aj2iwg58h7mk73hb80na0hf96wa-bctoolbox-5.2.0
ls -la /nix/store/bay71aj2iwg58h7mk73hb80na0hf96wa-bctoolbox-5.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

13 packages built:

bctoolbox
belcard
belle-sip
belr
bzrtp
liblinphone
lime
linphone
mediastreamer
mediastreamer-openh264
msilbc
ortp
trx

Maintainer pings
cc @7c6f434c @jluttine for testing.

@ofborg build bctoolbox belcard belle-sip belr bzrtp liblinphone lime linphone mediastreamer mediastreamer-openh264 msilbc ortp trx


Add autodecoder for Set<'a>

using lists for now, but this would be cool to have

I guess it should be possible to do something similar to Map<'Key, 'Value>
For reference:

Source Fable
Source .Net


Wallet

The wallet does not connect Yobit.
The wallet does not work on Android, via the TOR browser. The tor browser is banned in the Russian Federation. We need a metamask, a tone, and other wallets. In addition, exchanges cannot connect to the network

@cal

The wallet does not connect Yobit. The wallet does not work on Android, via the TOR browser. The tor browser is banned in the Russian Federation. We need a metamask, a tone, and other wallets. In addition, exchanges cannot connect to the network

first, there are instructions on how to shut tor off. second, yobit is a scam exchange. everyone knows that.

Captain
You closed this yesterday. Hope you're doing well.
On Tue, Sep 6, 2022, 12:52 sunerok @.***> wrote:

Closed #1094 https://github.com/vergecurrency/verge/issues/1094 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/vergecurrency/verge/issues/1094#event-7326465052, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACKY3WXOPRCJN2DFKYOPNR3V42WW5ANCNFSM6AAAAAAQEPJFMM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Captain You closed this yesterday. Hope you're doing well.
…
On Tue, Sep 6, 2022, 12:52 sunerok @.> wrote: Closed #1094 <#1094> as completed. — Reply to this email directly, view it on GitHub <#1094 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACKY3WXOPRCJN2DFKYOPNR3V42WW5ANCNFSM6AAAAAAQEPJFMM . You are receiving this because you are subscribed to this thread.Message ID: @.>

aye, doin well brother. about to push some updates ;)


requires Ruby 2.x

Looks like maybe the "double splat" operator here requires Ruby 2.x:
http://stackoverflow.com/questions/18289152/what-does-a-double-splat-operator-do/18289216#18289216
Once we upgraded the ruby version, worked like a charm.  Realize it's not a bug per say, but thought it might be worth mentioning somewhere.  Some plain Ubuntu installs still come with Ruby 1.9.x it seems.

Thanks for this note (and sorry for the delay).  I'll add a prominent comment to the readme.


feat: ignore docs folder

Versioning docs folder is causing changes on every build and commit. docs should not be in version control since it is always rebuilt in the CI and deployed in its own branch.
#185

Coverage remained the same at 100.0% when pulling 8b20ef45ceb3c77296bf75b8afcf1460c146f258 on cyphercodes:master into 4ab50a231a0a9203311d07e4b7ef8308830bee77 on alexjoverm:master.


Add project logo to Discovery UI

We should use the slug not the project name as those differ in certain projects. There is no easy way to get that in l2b without adding a dependency onto the layer2s/layer3s array which I don't want to do because it will kill the start up performance of that command and it will introduce the dependency of path you run it from. We will probably add it in the future. Closing for now.


Amount message?

As I was reviewing https://github.com/Open-Reaction-Database/ord-editor/issues/3, I found myself wondering why we don't have an Amount message:
message Amount {
  oneof kind {
    Mass mass = 1;
    Moles moles = 2;
    Volume volume = 3;
  }
}

This would change accessors like getattr(compound, compound.WhichOneof('amount')).value to getattr(compound.amount, compound.amount.WhichOneof('kind')).value but might be more readable since "Amount" will always show up in the pbtxt.
This would slightly reduce code duplication with the other amount oneof fields (in CrudeComponent and Workup) but also require additional validation to e.g. make sure that moles is not used when it is not appropriate.
I don't feel strongly about this either way, but wanted to bring it up as an opportunity to be slightly more explicit/consistent as we are making changes to the schema.
@connorcoley WDYT?

Gentle ping...

I was considering that as well...we do reuse Amounts in a few different places. I don't love the additional level of nesting in the programmatic definitions but overall I think it makes sense from a code reusability perspective. I can't think of any significant downsides, can you?

No, I don't see any significant downsides. I think an Amount message would be consistent with the way we've factored out other groups of things.
I'll create a PR to your PR for review.


Flutter tool analytics doesn't appear to report the CLI or IDE distinction

We'd like to be able to determine the difference between a CLI user and an IDE user for flutter_tool. Are we sending that info? If not, we'd like to send that.
Thanks!

cc @devoncarew @johnmccutchan

@mit-mit

As per an email thread, I think we want IDEs to pass in an env var to help us distinguish how the tool's being invoked. Something like FLUTTER_ENVIRONMENT=IntelliJ-IDEA flutter run --machine ...

Sounds like this requires two changes.  One to intellij and one to the tool?

Added the IDE one here: https://github.com/flutter/flutter-intellij/issues/840.

Just to update, the IDE PR landed - the work will be in the next milestone release. The env var name we ended up using is FLUTTER_HOST_ENV.

flutter_tools should likely populate the aiid session variable w/ any info from a FLUTTER_HOST_ENV env var.


Update for RTM ANCM common errors

Fixes #1626
There will be one more to update the common error added by @CIPop. I'll get that in as soon as his PR merges.

@Rick-Anderson Originally reported by @wildsylvan, there is an access violation exception that can crop up if the AppPool user identity doesn't have access to dotnet.exe. The exception is a little cryptic because it comes back simply as 'failed to start the process (502.5)' ... not the expected 500.19, 0xc0000005, or something along those lines.
I'll ask in a separate issue about the quality of that exception over in IISIntegration tomorrow, but I just added a blurb (even if just temporarily) to the appropriate spot in Common Errors to cover this for others who hit it.
Thanks to @wildsylvan for reporting the problem and working through it ... probably just saved hundreds of devs several hours each! :smile: :+1:


Route parameter set to 0 (zero) is ignored

Steps to reproduce.

Define route with parameter

FlowRouter.route('/example-route/:routeParam', {
  name: 'exampleRoute',
  action() {
    // Some action...
  },
});

Attempt to go to route with routeParameter set to 0

FlowRouter.go('exampleRoute', { routeParam: 0 });
The value 0 for routeParam is ignored.
Guessing a generic is null/undefined check against the param will be causing this
(i.e. if (routeParam) { do something })
Workaround is set to parameter as { routeParam: '0' }. However, this is counter intuitive when all other integers work as route parameters.
I can submit PR with fix if this is a feature you wish to include.

Just letting you know a fix for this would be appreciated as it it still an existing issue.


docs: add next verse

@devStack03, congratulations on your shiny new YOLO badge! If you've found this repository to be a valuable resource, go ahead and show some love with a stellar ⭐! Your support boosts its visibility within the community galaxy. 🔥🚀


Add spoken command to pin clippy

Eg saying "clippy pin" should show clippy if it's not already showing, and cause it to stay put after a paste. Equivalent to clicking the pin in the top right

Showing the window if it's hidden when you issue this command is no problem. "clippy pin" is defined as togglePinned. That means that if it was pinned and you issue that command it will be unpinned now.
Basically show window if hidden and then toggle pinned. Does that work for you?

I think that's ok. Is it possible for it to be pinned and hidden? If so, then I would be surprised when "clippy pin" results in it appearing and not being pinned
I would be tempted to have "clippy pin" and "clippy unpin". Idempotence is nice

It can definitely be pinned and hidden. If it's pin you can still hide it. Do you think that should unpin it?
I can add both set and toggle.

I have now added idempotent command identifiers to all toggle commands.
https://github.com/AndreasArvidsson/andreas-talon/blob/03ec15e089a80c56a2fab33a1d7f3f13bf72d86e/plugins/clippy/clippy.py#L22-L44


Fix making regex global

Regex.replace and Regex.scan are currently throwing errors because the flags property does not exist on a regex. This updates it to check the opts property instead, which does exist.
Additionally, Regex.replace was generating a global regex, reg, but was not using it when calling string.replace.

Thanks for catching that!


Remove chatty log errors which show up on machine ls

Not sure what the general sentiment is around this, but throwing it out there.
Right now docker-machine ls is pretty chatty if there are machines in error state.
In general, I would argue against this style of logging and in favor of:

A machine error command that would give you more information about
what kind of error state the machine is in, and/or:
Finer granularity in the types of "Error" state we return (e.g. is it
aborted?  Did something go wrong in create?  Is the network down?
etc.)

@ehazlett @bfirsh @sthulb WDYT?
Signed-off-by: Nathan LeClaire<EMAIL_ADDRESS>

@nathanleclaire i like this.  could you explain a bit more about what you think for machine error?  Am I understanding correctly that by default it would a general fail would be reported and then you would run machine error to explain?

@ehazlett Yes, that's exactly what I had in mind.  We could get drivers to dump API responses, for instance, to get more insight into what is happening behind the scenes when we deliberately ask for it.

+1
I think this could be included as part of the logging refactor.  Thoughts?

Absolutely.

I think this could be included as part of the logging refactor. Thoughts?

+1.  Would be good to include DumpError method or similar on the driver interface to allow each driver to check for various things that might be going wrong on an individual basis.

Unless I'm mistaken, this is covered by #591, so I'm closing


sharing: use IMR rather than AMR for sharing identity

Also greatly simplify the sharing algorithm, which can be made much simpler thanks to the IMR.
I think there are still some issues with the IMR calculation but we can address that in a later PR with more tests.

@roconnor-blockstream There are cases where the IMR of two nodes is the same and the source / target types are different, right? This is why types must be checked during the sharing computation.

@uncomputable all non-hidden nodes have their source and target types hashed into the IMR. So it's only hidden nodes where we might want to worry about the types differing.
It can happen that you can have two hidden nodes with different types but same hash (and therefore same IMR), though ofc this would indicate that something weird is going on. But my read of the consensus C code is that this is forbidden -- "sharing" means exactly "all IMRs are unique". See https://github.com/BlockstreamResearch/simplicity/blob/7be9a8725135ea81f6454968af574a6ca2390407/C/dag.c#L551-L572
But yes, let's get some clarification from @roconnor-blockstream before merging this.

I never understood why the IMR computation has a second pass with types hashed into it. That is the source of my confusion.
Hidden nodes are not a problem because they are never executed. The only reason we care about types is that iden nodes have to copy a certain number of bits, etc.

So, from @roconnor-blockstream on IRC:

Hidden nodes do not actually have types so their IMRs are equal to their CMRs (with a different IV)
Because they have no types, the types that our code assigns to them does not affect their CMRs. Any hidden nodes with the same content must be shared, regardless of type concerns.
Possibly we should drop Hidden nodes entirely ... in consensus they are only valid as part of an AssertL/AssertR, and it's hard for me to think what other "in-construction" use we might have for them.

So anyway this PR is fine as-is, though there is a bug in our IMR computation for Hidden ... and I think for Jet as well, and possibly others. But we can address that separately.


create containers with readonly root device

Add the ability to create readonly containers, i.e. containers with a readonly root device.
This will prevent the container from changing itself (changing os configuration, etc).
This can be done as a more general feature that allows lxdops to apply another set of profiles to the container when it is done configuring it.  lxdops can configure a container with the default LXD profile, and then replace it with a profile that has a readonly root device.

There could be a problem if lxdops makes the root device of a container readonly, while the container is not done configuring itself.  But the readonly property will have effect after the container reboots, so the problem is the same as when lxdops stops the container and makes a snapshot.  Lxdops waits 5 seconds (configurable) to give the container time to complete its tasks.  I wish there was a better way to do this.