AP Politician IDs

hi, I'm interested in adding AP politican IDs to the legislators-current.yaml file
working with APs election data, I assume its a pretty common use case to map it to other data sources or get more information about an incumbent
I've scraped the publicly available AP polIds found on this website:

http://pre-election.ap.org/
http://pre-election.ap.org/bios/1384.html

Scraped: https://github.com/AlJohri/ap_data/blob/master/pre_election_ap/data/pol_ids.csv
is there interest in merging something like this in?

I would check with the AP in terms of the recency of this data. For example, just checking Florida, it still has the 2014 governors race listed and doesn't appear to have details for 2016. If you can find a 2016 source, I'd be ok adding it in, but not as-is.

@dwillis that makes sense - I figured it might be helpful regardless since the politician ids are unchanging over time. I haven't yet found a public source for 2016 data other than test data all over Github such as https://github.com/newsdev/elex/tree/master/tests/data.
I've also semi-manually mapped all of the legislators-current.yaml to the 2016 AP Pol Ids in my own internal application. I'd be happy to make a CSV of AP IDS to Bioguides public but I understand this repository generally gets data in a reproducible manner.


colorbar.tickfont.color not appearing, colorbar.tickprefix not disappearing

related: https://github.com/plotly/plotly.js/issues/2834


Add stream agnostic metrics for realtime

Some of the metrics in Controller and Server have KAFKA in their names. We cannot directly rename them, as we will lose out on alerts setup on the old names, if any.
The plan is to introduce new metrics which have stream agnostic names. We will start using the new metrics, while also having the older one around. Once we have collected sufficient days of metrics for the enw one, we can phase out the old one.
We need to announce to the open source community that the older metrics will be going away eventually, and a shift to the new ones is required.

Linking to https://github.com/linkedin/pinot/issues/2583

Codecov Report

Merging #3426 into master will decrease coverage by 12.7%.
The diff coverage is 66.66%.

@@              Coverage Diff              @@
##             master    #3426       +/-   ##
=============================================
- Coverage      60.4%   47.69%   -12.71%
=============================================
  Files           993      993
  Lines         45638    45644        +6
  Branches       6111     6111
=============================================
- Hits          27567    21770     -5797
- Misses        16067    22092     +6025
+ Partials       2004     1782      -222

Impacted Files
Coverage Δ
Complexity Δ

.../core/realtime/PinotLLCRealtimeSegmentManager.java
45.79% <0%> (-18.23%)
0 <0> (ø)

...manager/realtime/LLRealtimeSegmentDataManager.java
55.37% <100%> (+11.81%)
0 <0> (ø)
:arrow_down:

...com/linkedin/pinot/common/metrics/ServerGauge.java
95.83% <100%> (+4.92%)
0 <0> (ø)
:arrow_down:

...linkedin/pinot/common/metrics/ControllerMeter.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

...edin/pinot/broker/queryquota/QueryQuotaConfig.java
0% <0%> (-100%)
0% <0%> (ø)

...ommon/utils/retry/RetriableOperationException.java
0% <0%> (-100%)
0% <0%> (ø)

...aggregation/function/AvgMVAggregationFunction.java
0% <0%> (-100%)
0% <0%> (ø)

.../com/linkedin/pinot/transport/common/NoneType.java
0% <0%> (-100%)
0% <0%> (ø)

...e/startree/v2/builder/OnHeapSingleTreeBuilder.java
0% <0%> (-100%)
0% <0%> (ø)

...a/aggregator/PercentileTDigestValueAggregator.java
0% <0%> (-100%)
0% <0%> (ø)

... and 676 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 75aa028...8050693. Read the comment docs.


Type literals handled poorly by IntelliSense

From @zackschuster on July 18, 2017 18:24

VSCode Version: 1.15.0-insiders
OS Version: Windows 10

Steps to Reproduce:

Open a new file in TypeScript mode. File does not need to be part of a project.
Copy the code from this gist: https://gist.github.com/zackschuster/3172f3d85e04ea2619d86129d9b4ec60
Expected behavior is in comments

I left a comment in https://github.com/Microsoft/vscode/issues/25034 with some of this info, then after finding more problems I decided to post a new issue. I bring this up because issues here may indirectly affect that bug.
Basically, it seems that IntelliSense is given a lot of over-simplified information w/r/t type literals, none of which follows a reliable or even necessarily coherent theory; depending on the context, the same literal may be revealed as its primitive, as its type alias, or as a completely unrelated type alias (!!!) that just happens to share properties.
While none of this appears to have an impact on compile-time correctness, it does make navigating code with IntelliSense more cumbersome than it needs to be while losing an opportunity to use keyof and crew with vscode in really powerful ways.
Reproduces without extensions: Yes
Copied from original issue: Microsoft/vscode#30951

A simple example:
interface I { foo: "foo" };
const x: I = { foo: "foo" };

Quick info on the second foo: should show "foo", but it currently shows string.

this is not about the quick info/intellisense, this is about how the type system handle immutable properties. please see https://github.com/Microsoft/TypeScript/issues/15271 for more details.


Remove all content of the list

Can we have a function to clean all the list content?
For the moment I'm doing the following:
	base = document.getElementById('main_body');
	while (base.lastChild != null) {
		base.removeChild(base.lastChild);
	}
	list.items = [];

Good suggestion! There are now a function called clear() in the List-object. To remove all objects from the list you write:
  mylist.clear()


Baseline MAINTAINERS, CODEOWNERS, and external collaborator permissions

Follow https://github.com/opensearch-project/.github/issues/125 to baseline MAINTAINERS, CODEOWNERS, and external collaborator permissions.
Close this issue when:

MAINTAINERS.md has the correct list of project maintainers.
CODEOWNERS exists and has the correct list of aliases.
Repo permissions only contain individual aliases as collaborators with maintain rights, admin, and triage teams.
All other teams are removed from repo permissions.

If this repo's permissions was already baselined, please confirm the above when closing this issue.

@macohen want to do this and take over this repo (#49)?

I'll make a PR with myself added and then we can go through the process of removing maintainers as needed.

Closed via https://github.com/opensearch-project/project-website-search/pull/50.


Upload artifacts to draft when new tag

Closes #585
Requires testing, will do tomorrow

it's ready!


[React Native] [1.1.0-beta.8] main module field that could not be resolved

error: Error: While trying to resolve module swr from file /project/src/core/api/common/ApiConfig.tsx, the package /project/node_modules/swr/package.json was successfully found. However, this package itself specifies a main module field that could not be resolved (/project/node_modules/swr/dist/index.mjs. Indeed, none of these files exist:

/project/node_modules/swr/dist/index.mjs(.native|.ios.js|.native.js|.js|.ios.json|.native.json|.json|.ios.ts|.native.ts|.ts|.ios.tsx|.native.tsx|.tsx)
/project/node_modules/swr/dist/index.mjs/index(.native|.ios.js|.native.js|.js|.ios.json|.native.json|.json|.ios.ts|.native.ts|.ts|.ios.tsx|.native.tsx|.tsx)
at DependencyGraph.resolveDependency (/project/node_modules/metro/src/node-haste/DependencyGraph.js:311:17)
at Object.resolve (/project/node_modules/metro/src/lib/transformHelpers.js:129:24)
at resolve (/project/node_modules/metro/src/DeltaBundler/traverseDependencies.js:396:33)
at /project/node_modules/metro/src/DeltaBundler/traverseDependencies.js:412:26
at Array.reduce ()
at resolveDependencies (/project/node_modules/metro/src/DeltaBundler/traverseDependencies.js:411:33)
at processModule (/project/node_modules/metro/src/DeltaBundler/traverseDependencies.js:140:31)
at async addDependency (/project/node_modules/metro/src/DeltaBundler/traverseDependencies.js:230:18)
at async Promise.all (index 0)
at async processModule (/project/node_modules/metro/src/DeltaBundler/traverseDependencies.js:198:5)

Looks like metro currently doesn't support .mjs as source file extension
https://github.com/facebook/metro/issues/535


Powerwall operation mode does not update from the cloud following HA restart

Version of the custom_component
3.12.2
Configuration
From core.config_entries
      {
        "entry_id": "<redacted>",
        "version": 1,
        "domain": "tesla_custom",
        "title": "<redacted>",
        "data": {
          "token": “<redacted>“,
          "access_token": "<redacted>",
          "expiration":<PHONE_NUMBER>,
          "username": "<redacted>",
          "domain": "https://auth.tesla.com",
          "include_vehicles": true,
          "include_energysites": true,
          "initial_setup": false
        },
        "options": {},
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "user",
        "unique_id": null,
        "disabled_by": null
      },

Describe the bug
Following HA restart the OperationMode sensor is always empty 'unknown' and does not update from the cloud, even after many hours (tested up to 11 hours).

Debug log
Debug log attached below but the following may be relevant.
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:560
First occurred: 6:11:47 PM (1 occurrences)
Last logged: 6:11:47 PM

Entity select.my_home_operation_mode (<class 'custom_components.tesla_custom.select.TeslaEnergyOperationMode'>) is using self.async_update_ha_state(), without enabling force_update. Instead it should use self.async_write_ha_state(), please report it to the custom integration author.

home-assistant_tesla_custom_2023-05-29T06-46-22.585Z.log

Transferring this comment from #619 for reference:
This started May 27 at 4:12PM (NZST), just 2 days ago. Before that the sensor would populate correctly after a restart. Other powerwall tesla custom sensors are populating without issue.

Additionally, changes made to the setting in the official phone Tesla app do not propagate down to this custom_component.
Changes made in this custom_component DO propagate up to the cloud and are reflected in the official phone Tesla app.

Checking the time it is attempting to update the value against debug logs, I am seeing a "script error":
ERROR (MainThread) [frontend.is.latest.202305033] :0:0 Script error.
Working through this, I see other sensors updating with valid values at the same time, e.g. 'Grid charging'

The sensor is updated from 'unavailable' to 'Yes' at 11:21:34
However for the 'Operation Mode' sensor, it is updated from 'unavailable' to 'unknown' at the same time, 11:21:34

@alandtse , I see the response in the debug logs does not return an operationhow does one use the HA service 'Tesla Custom Integration: api' ?
Specifically what does one put in each field? The following does not work and the links are not really helpful unless you're familiar with the process. The following results in Failed to call service tesla_custom.api. Unknown error
command: "SITE_SUMMARY"

parameters: {
    "AUTH": true,
    "TYPE": "GET",
    "URI": "api/1/energy_sites/11xxxxx0-14-J--CNxxxxxxxx4J03Y/site_status"
  }

Some of the ID is redacted above.

Looking at the code in `services.yaml', I found the following:
api:
  # Description of the service
  description: Run an API command using controller.api. https://teslajsonpy.readthedocs.io/en/latest/teslajsonpy/teslajsonpy.html#teslajsonpy.Controller.api
  # Different fields that your service accepts
  fields:
    # Key of the field
    email:
      # Description of the field
      description: Email address (optional if only one account)
      # Example value that can be passed for this field
      example<EMAIL_ADDRESS>      required: false
      selector:
        text:
    command:
      # Description of the field
      description: Command to run. See https://github.com/zabuldon/teslajsonpy/blob/master/teslajsonpy/endpoints.json
      # Example value that can be passed for this field
      example: "WAKE_UP"
      required: true
      selector:
        text:
    parameters:
      # Description of the field
      description: Parameters in a dictionary. `path_vars` replace variables in endpoints.json path. All others are passed directly to controller.api. For command parameters see https://tesla-api.timdorr.com/vehicle/commands.
      # Example value that can be passed for this field
      example: '{"path_vars": {"vehicle_id":"1"}, "wake_if_asleep":True}'
      required: true
      selector:
        object:

However, the example: does not show in the UI

But the above still produces the same error

Progressing after viewing in YAML mode but still errored.

@jaymunro thanks for your details on this issue, I have also been having states disappear so hopefully switching to #606 will resolve this issue as well.

TLDR: I think the teslajsonpy code needs to change the API call from BATTERY_DATA to SITE_CONFIG to retrieve this data. I'd appreciate comments from people with more background on this than me.
Using debug logs I found that the data is being retrieved by API calls to BATTERY_SUMMARY and BATTERY_DATA, neither of which contain the operation mode. It seems this is defined in teslajsonpy in energy.py on lines 175-178
    @property
    def operation_mode(self) -> str:
        """Return operation mode."""
        return self._battery_data.get("operation")

It expects the operation mode to exist at the top level in battery_data, but it is not there, it is actually in the API call SITE_CONFIG under the property "default_real_mode" (not "operation"). This may have been an API change by Tesla (would be strange) or teslajsonpy using a deprecated API.
I determined this by using Developer Tools > Services with a call to service Tesla Custom Integration: api, and found:
BATTERY_DATA call response. (operation is totally absent)
{"response":{
    "site_name":"My Home",
    "energy_left":9567.05263157895,
    "total_pack_energy":13846,
    "grid_status":"Active",
    "backup":{
        "backup_reserve_percent":15,
        "events":[
            {"timestamp":"2023-01-08T00:07:31+13:00","duration":34626},
            {"timestamp":"2022-07-02T13:36:25+12:00","duration":21030}],
        "events_count":0,
        "total_events":0},
    "user_settings":{
        "storm_mode_enabled":true,
        "powerwall_onboarding_settings_set":true,
        "powerwall_tesla_electric_interested_in":false,
        "sync_grid_alert_enabled":false,
        "breaker_alert_enabled":false},
    "components":{
        "solar":true,
        "solar_type":"pv_panel",
        "battery":true,
        "grid":true,
        "backup":true,
        "gateway":"teg",
        "load_meter":true,
        "tou_capable":true,
        "storm_mode_capable":true,
        "flex_energy_request_capable":false,
        "car_charging_data_supported":false,
        "off_grid_vehicle_charging_reserve_supported":false,
        "vehicle_charging_performance_view_enabled":false,
        "vehicle_charging_solar_offset_view_enabled":false,
        "battery_solar_offset_view_enabled":true,
        "solar_value_enabled":true,
        "energy_value_header":"Energy Value",
        "energy_value_subheader":"Estimated Value",
        "show_grid_import_battery_source_cards":true,
        "backup_time_remaining_enabled":true,
        "battery_type":"ac_powerwall",
        "configurable":false,
        "grid_services_enabled":false,
        "customer_preferred_export_rule":"pv_only"},
    "installation_date":"2022-07-01T15:15:19+12:00",
    "power_reading":[{
        "timestamp":"2023-06-02T18:09:54+12:00",
        "load_power":920,
        "solar_power":0,
        "grid_power":19,
        "battery_power":910,
        "generator_power":0}],
    "battery_count":1}}

SITE_CONFIG call response. (Note the 4th property "default_real_mode":"autonomous")
{
    "response":{
        "id":"<redacted>",
        "site_name":"My Home",
        "backup_reserve_percent":15,
        "default_real_mode":"autonomous",
        "installation_date":"2022-07-01T15:15:19+12:00",
        "user_settings":{
            "storm_mode_enabled":true,
            "powerwall_onboarding_settings_set":true,
            "powerwall_tesla_electric_interested_in":false,
            "sync_grid_alert_enabled":true,
            "breaker_alert_enabled":false},
        "components":{
            "solar":true,
            "solar_type":"pv_panel",
            "battery":true,
            "grid":true,
            "backup":true,
            "gateway":"teg",
            "load_meter":true,"tou_capable":true,
            "storm_mode_capable":true,
            "flex_energy_request_capable":false,
            "car_charging_data_supported":false,
            "off_grid_vehicle_charging_reserve_supported":false,
            "vehicle_charging_performance_view_enabled":false,
            "vehicle_charging_solar_offset_view_enabled":false,
            "battery_solar_offset_view_enabled":true,
            "solar_value_enabled":true,
            "energy_value_header":"Energy Value",
            "energy_value_subheader":"Estimated Value",
            "energy_service_self_scheduling_enabled":true,
            "show_grid_import_battery_source_cards":true,
            "set_islanding_mode_enabled":true,
            "wifi_commissioning_enabled":true,
            "backup_time_remaining_enabled":true,
            "battery_type":"ac_powerwall",
            "configurable":true,
            "grid_services_enabled":false,
            "customer_preferred_export_rule":"pv_only",
            "edit_setting_permission_to_export":true,
            "edit_setting_grid_charging":true,
            "edit_setting_energy_exports":true},
        "version":"23.4.2-1 fe55682a",
        "battery_count":1,
        "tou_settings":{
            "optimization_strategy":"economics",
            "schedule":[
                {
                    "target":"off_peak",
                    "week_days":[1,0],
                    "start_seconds":75600,
                    "end_seconds":0},
                {
                    "target":"peak",
                    "week_days":[1,0],
                    "start_seconds":0,
                    "end_seconds":75600}
            ]},
        "nameplate_power":5000,
        "nameplate_energy":13500,
        "installation_time_zone":"Pacific/Auckland",
        "max_site_meter_power_ac":14.1,
        "min_site_meter_power_ac":-1000000000,
        "geolocation":{
            "latitude":-43.501566,
            "longitude":172.5709272},
        "address":{
            "address_line1":"<redacted>",
            "city":"<redacted>",
            "state":"<redacted>",
            "zip":"<redacted>",
            "country":"NZ"
        }}}

I tested the default_real_mode by changing the mode in the Tesla iOS app and the tesla_custom API service call to change the operation mode (still works).
Tesla app
Operation Mode     default_real_mode
Self-Powered       "self_consumption"
Time-Based Control "autonomous"
Backup             [no longer exists in the UI]

tesla_custom select. setting
Operation Mode     default_real_mode
Self-Powered       "self_consumption"
Time-Based Control "autonomous"
Backup             "self_consumption" ("backup_reserve_percent" is changed to 100)

I’ve opened a fork to start a PR, but first need to test. Does anyone have any pointers on how to get changed teslajsonpy code into HA for testing a change with tesla_custom?


! mark is not working

Issue Type: Feature Request
! mark is not working  not giving elements
VS Code version: Code 1.69.0 (92d25e35d9bf1a6b16f7d0758f25d48ace11e5b9, 2022-07-07T05:28:36.503Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

/duplicate of https://github.com/microsoft/vscode/issues/154375


chore: Promote Scaling Modifiers to GA

Also here: keda.sh/docs/2.15/reference/scaledobject-spec#scalingmodifiers

nice catch! updated


Watcher API re-connect issues

Hi,
First, my apologies for this long comment.
I have read previous issues #73 and #76 but I think that there are still issues related to watcher re-connect.
Documentation Issues
The first issue is related to documentation at Readme.md file. I think that the current code isn't right:
void wait_for_connection(Client &client) {
  // wait until the client connects to etcd server
  // `head` API is only available in version later than 0.2.1
  while (!client.head().get().is_ok()) {
    sleep(1);
  }
}

void initialize_watcher(const std::string &endpoints,
  const std::string &prefix,
  std::function<void(Response)> callback,
  std::shared_ptr<etcd::Watcher> &watcher) {
    Client client(endpoints);
    wait_for_connection(client);
    watcher->reset(new etcd::Watcher(client, prefix, callback));
    watcher->Wait([endpoints, prefix, callback,
                   watcher_ref /* keep the shared_ptr alive */, &watcher](bool cancelled) {
        if (cancelled) {
            return;
        }
        initialize_watcher(endpoints, prefix, callback, watcher);
    });
}

std::string endpoints = "http://<IP_ADDRESS>:2379";
std::function<void(Response)> callback = printResponse;
const std::string prefix = "/test/key";

// the watcher initialized in this way will auto re-connect to etcd
std::unique_ptr<etcd::Watcher> watcher;
initialize_watcher(endpoints, prefix, callback, watcher);

I have found the following issues:

Type error calling watch reset, it should be watcher.reset(new etcd::Watcher(...) instead watcher->reset(new etcd::Watcher(...)
Typo error in lambda parameters?

watcher->Wait([endpoints, prefix, callback,
		watcher_ref /* keep the shared_ptr alive */, &watcher](bool cancelled) { };

Compiler error on watcher_ref. What do you really want here?
Do you want to capture watcher variable by reference in the lambda function?
watcher->Wait([endpoints, prefix, callback,
		/*watcher_ref keep the shared_ptr alive */ &watcher](bool cancelled) {
	if (cancelled) {
		return;
	}
	initialize_watcher(endpoints, prefix, callback, watcher);
});

or, Do you want capture watcher variable by value in the lambda function?
// Notice that in this case lambda requires `mutable` qualifier.
watcher->Wait([endpoints, prefix, callback,
		watcher_ref  = /*keep the shared_ptr alive */ watcher](bool cancelled) mutable {
	if (cancelled) {
		return;
	}
	initialize_watcher(endpoints, prefix, callback, watcher_ref);
});

These two options will make the code to compile successfully, but they have different consequences. I will explain it later.

To be able compile it, you have to use a shared_ptr instead unique_ptr when initialize_watcher() is called for first time, so code should be:

// the watcher initialized in this way will auto re-connect to etcd
std::shared_ptr<etcd::Watcher> watcher;
initialize_watcher(endpoints, prefix, callback, watcher);

I think that some of these issues has been introduced in commits 2338a83 (#76) and 891dc7b
Behaviour Issues
Related to re-connect behaviour (#73), I think that is still not fixed. In my case, I need to use a re-connect watcher but I would like to cancel the watcher when unlock operation happens. Depending the type of capture over watch variable used in lambda function, I have different behaviours but neither fits the objective.
Using capture by reference
Running the following test code:
void initialize_watcher(const std::string& endpoints,
	const std::string& prefix,
	std::function<void(etcd::Response)> callback,
	std::shared_ptr<etcd::Watcher>& watcher) {
	etcd::Client client(endpoints);
	original::wait_for_connection(client);
	watcher.reset(new etcd::Watcher(client, prefix, callback));
	watcher->Wait([endpoints, prefix, callback,
		/*watcher_ref  keep the shared_ptr alive ,*/ &watcher](bool cancelled) {
			if (cancelled) {
				return;
			}
			original::initialize_watcher(endpoints, prefix, callback, watcher);
		});
}

std::string my_endpoints = "http://<IP_ADDRESS>:2379";
std::function<void(etcd::Response)> callback = ot_etcd::print_event_response;
const std::string my_prefix = "/test/key";

// the watcher initialized in this way will auto re-connect to etcd
std::shared_ptr<etcd::Watcher> watcher;
original::initialize_watcher(my_endpoints, my_prefix, callback, watcher);

std::this_thread::sleep_for(std::chrono::seconds(10));
std::cout << "sleep one completed" << std::endl;

watcher->Cancel();
std::this_thread::sleep_for(std::chrono::seconds(10));
std::cout << "sleep two completed" << std::endl;

In this case there are two results:

The connection isn't lost during the tests. In this case the watcher->Cancel() is completed, so the watcher won't report anything after cancelling and all will work as expected.
But, if the connection is lost after initialize_watcher() call and before teh Cancel() call (I'm forcing it closing socket externally) then an exception happens. More precisely when watcher.reset() is executed  then etcd::Watcher destructor of previous object is called internally that leads throwing _Throw_Cpp_error(_RESOURCE_DEADLOCK_WOULD_OCCUR); due the thread::join() is executed from the same thread that wait_callback is called in Watcher::doWatch().

Using capture by value
Running the following test code:
void initialize_watcher(const std::string& endpoints,
	const std::string& prefix,
	std::function<void(etcd::Response)> callback,
	std::shared_ptr<etcd::Watcher>& watcher) {
	etcd::Client client(endpoints);
	original::wait_for_connection(client);
	watcher.reset(new etcd::Watcher(client, prefix, callback));

	// Notice that lambda requires `mutable`qualifier.
	watcher->Wait([endpoints, prefix, callback,
		/*watcher_ref  keep the shared_ptr alive ,*/ watcher](bool cancelled) mutable {
			if (cancelled) {
				return;
			}
			original::initialize_watcher(endpoints, prefix, callback, watcher);
		});
}

std::string my_endpoints = "http://<IP_ADDRESS>:2379";
std::function<void(etcd::Response)> callback = ot_etcd::print_event_response;
const std::string my_prefix = "/test/key";

// the watcher initialized in this way will auto re-connect to etcd
std::shared_ptr<etcd::Watcher> watcher;
original::initialize_watcher(my_endpoints, my_prefix, callback, watcher);

std::this_thread::sleep_for(std::chrono::seconds(10));
std::cout << "sleep one completed" << std::endl;

watcher->Cancel();
std::this_thread::sleep_for(std::chrono::seconds(10));
std::cout << "sleep two completed" << std::endl;

In this case, when we capture std::shared_ptr by value then a new std::shared_ptr is created when lambda captures by value and increments the reference count.
Again there are two results:

The connection isn't lost during the tests. In this case the watcher->Cancel() is completed, so the watcher won't report anything after cancelling and all will work as expected.
But, if the connection is lost after initialize_watcher() call and before the Cancel() call ((I'm forcing it closing socket externally), then code doesn't crash by exception (it doesn't because the previous shared_ptr isn't release its object because reference count increased when parameter was capture by value in lambda). But watcher->Cancel() doesn't have effect due we are calling Cancel on the old object, then we are continue receiving notifications from a watcher (the last Watcher object created).
So with this approach, we will have a dangled Watcher object each time that a connection lost happens and new Watcher is be created in initialize_watcher().

Probably the right way is to capture by reference in lambda, but then we have issues destroying Watch on cancel. On the other hand, avoiding thread:join() issues capturing by value in lambda makes that we will have dangled objects and cancellation doesn't work either, although app doesn't crash.
How to fix that? Any ideas?
Thanks.

I have a fix, see pull-request (#118) for details.

See also https://github.com/etcd-cpp-apiv3/etcd-cpp-apiv3/pull/118#issuecomment-1092775690


consult the detail of 1.2example in spec

A compasable CPU and CFU packages is mentioned, in chapter 1.2 examples of spec. I'm interested in how it implement crypto and compression by CFU. So I want to know the source of Alice system and the detail of it. Is it a open source project? Can I study and know it future? @grayresearch

Sorry, little*, but this is a hypothetical example of a composed system, not a citation of an extant system. Yet.


Bottom to top button is added in evey page

The button shape is absurd. Please make it circular
It should not be statically placed over the footer and rather be dynamic in nature . Reference
Make sure the color scheme is coherent with the rest of the project.

@anushbhatia any suggestions from your side?

ff43fd2298569154eb4b5b93d08a3595ed8cbc50

Overall there is a huge improvement and I believe we can merge this soon. @anushbhatia could you please help out @royalleads15 with the specifics of the color and the size to suit our existing UI.
Deploy Preview

@smaranjitghose  issue removed . Now review it .

@anushbhatia I have made some changes according to you .Review it again .

@smaranjitghose please review it .

Not upto expectations


[Bug] Alfheim causing huge amount of ram consumption with dummyworld in jei

Describe the bug
When using alfheim with mods using DummyWorld, the game consumes much more ram than w/o alfheim.
This happens for alfheim with versions above 1.2.
Tested mods:

GregTechCEu
Modular Machinery CE
Multiblocked

Reproducibility

[X] I reproduced this issue with as few other mods as possible installed.
[ ] I am unable to reproduce this issue consistently.

Screenshots and/or videos
No response
Logs
N/A
Debug Logs
No response
Crash Reports
No response
Alfheim Version
1.4-Dev-1
Forge Version
1.12.2 - <IP_ADDRESS>60
MixinBooter Version
9.1
Java Version
1.8-352
Java Virtual Machine
Hotspot
Operating System
Windows 11
GPU Vendor
NVIDIA
Code of Conduct

[X] I agree to follow this project's Code of Conduct

fixed in GregTechCEu/GregTech#2475


Need support to recognize dual format ipv6

Our system does not support dual addresses, we need to know how to exclude these cases.
Examples:

fd00:ffff:0000:0000:1::<IP_ADDRESS> - version 2.1.0 was failing to parse, version 2.2.0 gives valid ipv6, no method to recognize dual address
2001:db8:3333:4444:5555:6666:<IP_ADDRESS> - parsed successfully by both 2.1.0 and 2.2.0 giving valid ipv6, no method to recognize dual address

Hmm... probably we can just check for dot in the string


Update to ruby 2.5.0; required vcr_cassettes reset

This updates to Ruby 2.5.0, the latest officially-released
version of Ruby.  It is supposed to be slightly faster.
This commit required updating all the vcr_cassettes, and I had
to fix a few things to make that work (it's been a while since
we updated vcr cassettes).  For example, the tests now skip loading
a VCR file if it isn't there (this is necessary when we delete
VCR files).  This commit modifies the test documentation
in doc/testing.md to explain some key points, so that this
process will be easier to repeat in the future.
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

I fixed one error by updating rubocop (the old version of rubocop didn't know about Ruby 2.5.0).
I now have a different error, on the next step.  Not sure why it's happening.  Here is the report from CircleCI:
bundle exec rake ci00:06config
Exit code: 1

bundle exec rake ci

bundle doctor
Traceback (most recent call last):
	3: from /opt/circleci/.rvm/gems/ruby-2.5.0/bin/ruby_executable_hooks:15:in `<main>'
	2: from /opt/circleci/.rvm/gems/ruby-2.5.0/bin/ruby_executable_hooks:15:in `eval'
	1: from /opt/circleci/.rvm/gems/ruby-2.5.0/bin/bundle:23:in `<main>'
/opt/circleci/.rvm/gems/ruby-2.5.0/bin/bundle:23:in `load': cannot load such file -- /opt/circleci/ruby/ruby-2.5.0/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/exe/bundle (LoadError)
rake aborted!
Command failed with status (1): [bundle doctor...]
/home/ubuntu/best-practices-badge/lib/tasks/default.rake:77:in `block in <top (required)>'
/home/ubuntu/best-practices-badge/vendor/bundle/ruby/2.5.0/gems/rake-12.3.0/exe/rake:27:in `<top (required)>'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:75:in `load'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:75:in `kernel_load'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:28:in `run'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib/bundler/cli.rb:424:in `exec'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib/bundler/cli.rb:27:in `dispatch'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib/bundler/cli.rb:18:in `start'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/exe/bundle:30:in `block in <top (required)>'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib/bundler/friendly_errors.rb:122:in `with_friendly_errors'
/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/exe/bundle:22:in `<top (required)>'
/opt/circleci/.rvm/gems/ruby-2.5.0/bin/bundle:23:in `load'
/opt/circleci/.rvm/gems/ruby-2.5.0/bin/bundle:23:in `<main>'
/opt/circleci/.rvm/gems/ruby-2.5.0/bin/ruby_executable_hooks:15:in `eval'
/opt/circleci/.rvm/gems/ruby-2.5.0/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => ci => bundle_doctor
(See full trace by running task with --trace)

bundle exec rake ci returned exit code 1

Suggestions welcome.  It's not obvious to me what is causing this.  (It's probably simple, that's not the same thing :-) ).

LGTM, looks like a lot of work.
For debugging CircleCI, I recommend logging in via SSH and trying several bundle commands.
A reminder that I'm still meaning to convert this to a Docker container to remove the differences between dev, test and prod.

What's weird is that updating Ruby is usually trivial.
I ssh'ed in.  Doing a cd best-practices-badge, followed by
"gem install bundler" or "bundle exec gem install bundler", reports this as expected:
Fetching: bundler-1.16.1.gem (100%)
Successfully installed bundler-1.16.1

But the bundler that is loaded into /opt/circleci/ruby/ruby-2.5.0
is version 1.16.0, not version 1.16.1:
ls /opt/circleci/ruby/ruby-2.5.0/lib/ruby/gems/2.5.0/gems
bundler-1.16.0		minitest-5.10.3     rubygems-bundler-1.4.4
bundler-unload-1.0.2	net-telnet-0.1.1    rvm-<IP_ADDRESS>
did_you_mean-1.2.0	power_assert-1.1.1  test-unit-3.2.7
executable-hooks-1.3.2	rake-12.3.0	    xmlrpc-0.3.0
gem-wrappers-1.3.2	rdoc-6.0.1

Sounds like a path issue. You also might open a ticket with CircleCI.

Running bundler directly in this directory works as expected with version 1.16.1:
bundler --version
Bundler version 1.16.1
ubuntu@box4343:~/best-practices-badge$ bundler doctor
The Gemfile's dependencies are satisfied
No issues found with the installed bundle
ubuntu@box4343:~/best-practices-badge$ bundler audit
No vulnerabilities found

Definitely a path issue.  The question is, where is it coming from?

Things to investigate:
bundle exec gem install bundler
rvm repair all

I should note that I normally use rbenv in development, but rvm is used in in CircleCI.  I tried to configure things so it would work either way, but that may be a problem in this case.

"bundle --version" says "1.16.0", even though we installed 1.16.1.
PATH at the end of the process:
/opt/circleci/.rvm/gems/ruby-2.5.0/bin:/opt/circleci/.rvm/gems/ruby-2.5.0@global/bin:/opt/circleci/.rvm/rubies/ruby-2.5.0/bin:/opt/circleci/.rvm/bin:/home/ubuntu/.yarn/bin:/opt/circleci/nodejs/v4.2.6/bin:/opt/google-cloud-sdk/bin:/home/ubuntu/.local/bin:/opt/ghc/8.0.2/bin:/opt/cabal/1.24/bin:/opt/alex/3.1.7/bin:/opt/happy/1.19.5/bin:/home/ubuntu/.composer/vendor/bin:/opt/circleci/.phpenv/shims:/opt/circleci/.phpenv/bin:/home/ubuntu/.go_workspace/bin:/usr/local/go/bin:/opt/circleci/nodejs/v4.2.6/bin:/opt/circleci/.pyenv/shims:/opt/circleci/.pyenv/bin:/opt/google-cloud-sdk/bin:/usr/local/android-sdk-linux/platform-tools:/usr/local/android-sdk-linux/tools:/usr/local/apache-maven/bin:/home/ubuntu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/gradle-1.10/bin

I modified lib/tasks/default.rake, stuck in "byebug" inside "bundle_doctor", ran "bundle exec rake ci", from byebug ran sh('bash'), and then examined the failing environment.  "bundle doctor" does indeed fail in that environment.
I looked at the environment variables using "env", and it isn't what I expected.  The environment at that point is quite different. GEM_PATH is empty, and the bundler env variables are now BUNDLER_ORIG_...
Here are some of the differences in the environment, between before we run bundle exec rake ci, and the actual environment in place inside the rake task bundle_doctor:
-GEM_HOME=/opt/circleci/.rvm/gems/ruby-2.5.0
+GEM_HOME=/home/ubuntu/best-practices-badge/vendor/bundle/ruby/2.5.0
-GEM_PATH=/opt/circleci/.rvm/gems/ruby-2.5.0:/opt/circleci/.rvm/gems/ruby-2.5.0@global
+GEM_PATH=
+BUNDLE_BIN_PATH=/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/exe/bundle
+BUNDLE_GEMFILE=/home/ubuntu/best-practices-badge/Gemfile
+BUNDLER_ORIG_BUNDLE_BIN_PATH=BUNDLER_ENVIRONMENT_PRESERVER_INTENTIONALLY_NIL
+BUNDLER_ORIG_BUNDLE_GEMFILE=BUNDLER_ENVIRONMENT_PRESERVER_INTENTIONALLY_NIL
+BUNDLER_ORIG_BUNDLER_ORIG_MANPATH=BUNDLER_ENVIRONMENT_PRESERVER_INTENTIONALLY_NIL
+BUNDLER_ORIG_BUNDLER_VERSION=BUNDLER_ENVIRONMENT_PRESERVER_INTENTIONALLY_NIL
+BUNDLER_ORIG_GEM_HOME=/opt/circleci/.rvm/gems/ruby-2.5.0
+BUNDLER_ORIG_GEM_PATH=/opt/circleci/.rvm/gems/ruby-2.5.0:/opt/circleci/.rvm/gems/ruby-2.5.0@global
+BUNDLER_ORIG_MANPATH=/opt/circleci/nodejs/v4.2.6/share/man:/opt/circleci/nodejs/v4.2.6/share/man:/opt/circleci/nodejs/v4.2.6/share/man:/usr/local/man:/usr/local/share/man:/usr/share/man
+BUNDLER_ORIG_PATH=/opt/circleci/.rvm/gems/ruby-2.5.0/bin:/opt/circleci/.rvm/gems/ruby-2.5.0@global/bin:/opt/circleci/.rvm/rubies/ruby-2.5.0/bin:/opt/circleci/.rvm/bin:/home/ubuntu/.yarn/bin:/opt/circleci/nodejs/v4.2.6/bin:/opt/google-cloud-sdk/bin:/home/ubuntu/.local/bin:/opt/ghc/8.0.2/bin:/opt/cabal/1.24/bin:/opt/alex/3.1.7/bin:/opt/happy/1.19.5/bin:/home/ubuntu/.composer/vendor/bin:/opt/circleci/.phpenv/shims:/opt/circleci/.phpenv/bin:/home/ubuntu/.go_workspace/bin:/usr/local/go/bin:/opt/circleci/nodejs/v4.2.6/bin:/opt/circleci/.pyenv/shims:/opt/circleci/.pyenv/bin:/opt/google-cloud-sdk/bin:/usr/local/android-sdk-linux/platform-tools:/usr/local/android-sdk-linux/tools:/usr/local/apache-maven/bin:/home/ubuntu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/gradle-1.10/bin
+BUNDLER_ORIG_RB_USER_INSTALL=BUNDLER_ENVIRONMENT_PRESERVER_INTENTIONALLY_NIL
+BUNDLER_ORIG_RUBYLIB=BUNDLER_ENVIRONMENT_PRESERVER_INTENTIONALLY_NIL
+BUNDLER_ORIG_RUBYOPT=BUNDLER_ENVIRONMENT_PRESERVER_INTENTIONALLY_NIL
+BUNDLER_VERSION=1.16.1
-PATH=/opt/circleci/.rvm/gems/ruby-2.5.0/bin:/opt/circleci/.rvm/gems/ruby-2.5.0@global/bin:/opt/circleci/.rvm/rubies/ruby-2.5.0/bin:/opt/circleci/.rvm/bin:/home/ubuntu/.yarn/bin:/opt/circleci/nodejs/v4.2.6/bin:/opt/google-cloud-sdk/bin:/home/ubuntu/.local/bin:/opt/ghc/8.0.2/bin:/opt/cabal/1.24/bin:/opt/alex/3.1.7/bin:/opt/happy/1.19.5/bin:/home/ubuntu/.composer/vendor/bin:/opt/circleci/.phpenv/shims:/opt/circleci/.phpenv/bin:/home/ubuntu/.go_workspace/bin:/usr/local/go/bin:/opt/circleci/nodejs/v4.2.6/bin:/opt/circleci/.pyenv/shims:/opt/circleci/.pyenv/bin:/opt/google-cloud-sdk/bin:/usr/local/android-sdk-linux/platform-tools:/usr/local/android-sdk-linux/tools:/usr/local/apache-maven/bin:/home/ubuntu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/gradle-1.10/bin
+_=/opt/circleci/.rvm/gems/ruby-2.5.0/bin/bundle
+PATH=/home/ubuntu/best-practices-badge/vendor/bundle/ruby/2.5.0/bin:/opt/circleci/.rvm/gems/ruby-2.5.0/bin:/opt/circleci/.rvm/gems/ruby-2.5.0@global/bin:/opt/circleci/.rvm/rubies/ruby-2.5.0/bin:/opt/circleci/.rvm/bin:/home/ubuntu/.yarn/bin:/opt/circleci/nodejs/v4.2.6/bin:/opt/google-cloud-sdk/bin:/home/ubuntu/.local/bin:/opt/ghc/8.0.2/bin:/opt/cabal/1.24/bin:/opt/alex/3.1.7/bin:/opt/happy/1.19.5/bin:/home/ubuntu/.composer/vendor/bin:/opt/circleci/.phpenv/shims:/opt/circleci/.phpenv/bin:/home/ubuntu/.go_workspace/bin:/usr/local/go/bin:/opt/circleci/.pyenv/shims:/opt/circleci/.pyenv/bin:/usr/local/android-sdk-linux/platform-tools:/usr/local/android-sdk-linux/tools:/usr/local/apache-maven/bin:/home/ubuntu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/gradle-1.10/bin
+RUBYLIB=/opt/circleci/.rvm/gems/ruby-2.5.0/gems/bundler-1.16.1/lib
+RUBYOPT=-rbundler/setup

I'm out of time.  If someone has suggestions, I'd love to hear them.

I've sent a ticket to CircleCI.  Maybe this is obvious to them?!

Kyle Tryon (Support Engineer @ CircleCI) on Feb 27, 06:34 PST received my earlier comment, and added the following suggestion for the problem:

I was able to find this, which seems to suggest this is a known issue that has since been resolved in 2.7.4 if you are able to upgrade.
https://github.com/travis-ci/travis-ci/issues/8978#issuecomment-354036443

This occurs with the combination of Bundler 1.16.1 and rubygems 2.7.3.
Since this problem has been addressed in rubygems 2.7.4, execute gem update --system in before_install should fix an error.
Let me know if this works for you.

I didn't expect that suggestion to work in this case, but I went ahead and tried it by adding "gem update --system" to the early process (in dependencies/pre before we run "gem install bundler --no-document").
Remarkably, it did work!  I don't know if this works when integrated into one of the executing stages (such as master), but I don't see why it wouldn't.  Good job, CircleCI support, that probably fixed it!
So - someone let me know if see a problem with this.  If no problems, I'll merge it into master. If it works once moved into master, we'll close out this CircleCI ticket as being successfully resolved.

I'll add a separate issue to cover moving from CircleCI 1.0 to 2.0.


gradle release v3.2.1

To be merged after the release is complete.

Have to fix a jackson-bom issue.


Caches per recording

Moves Caches from AppState to the StoreHub, and make them per-recording instead of viewer-wide in the process.
This is:

a pre-requisite to fix the repeated static logging issues (#7404)
a necessary step towards proper secondary caching
a fix for a very old issue: cache memory is not reclaimed when closing a recording

I'm not a fan of the implementation: it's brittle, confusing, and I don't like it. Still, it's a net improvement over the status quo, and fixes a very annoying "leak" for end users.
Before:
https://github.com/user-attachments/assets/a54c1923-a939-4700-a485-eeb2a2dd4966
After:
https://github.com/user-attachments/assets/dd5adb65-d328-474c-bc31-e65a59332f03

Part of #7404

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!
[x] If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

Should also fix

https://github.com/rerun-io/rerun/issues/6755

but should probably check first

Should also fix
* [GPU memory not freed when closing recording, but keeping viewer open #6755](https://github.com/rerun-io/rerun/issues/6755)

but should probably check first

I checked and it's definitely not the case: Counted GPU barely budges when closing the recording. :disappointed:

Counted GPU is fed by what re_renderer holds on to, so yeah something goes sideways there hum


Updated package.json to use the correct casing for the 'main' entrypoint

In the rollup script 'angularFire2.umd.js'  is used, where in the package.json 'angularfire2.umd.js' was used, causing for loading problems on linux based systems (Ubuntu in this case)
https://github.com/angular/angularfire2/blob/master/rollup.publish.config.js#L5

I signed the CLA

The casing is wrong on our side actually. We'd rather change the casing in the rollup config.
https://github.com/angular/angularfire2/blob/master/rollup.publish.config.js#L5
https://github.com/angular/angularfire2/blob/master/rollup.test.config.js#L7
Would you like to change those two files and then I'll merge the PR?

I signed and modified the github accountname for the CLA

@davideast
I didn't modify https://github.com/angular/angularfire2/blob/master/rollup.test.config.js#L7 as it was the module name and not the file name. The rollup test config doesn't affect this issue as it uses a totally different filename.

This has been merged now under #599. Thanks @meDavid for finding and providing the fix.

@maxmumford The CLA check no longer worked for me. I updated the CLA details to contain my github username, but it didn't update the cla label.


Option to make window stay inside page

https://github.com/McIntireEvan/drawingapp/issues/50

Other issues related to this
https://github.com/McIntireEvan/drawingapp/issues/54
https://github.com/McIntireEvan/drawingapp/issues/53
https://github.com/McIntireEvan/drawingapp/issues/50


Measurement Unit Mixins

This PR mainly contains mixins that deal with measurements and being able to easily control the measurement unit that they are displayed in. It also contains some bug fixes and some other small additions. There are a lot of changes/additions so I'll just summarise the ones that are important or that might need discussing. I wrote all of these a few weeks ago so I hope I've remembered everything.
Library Changes:

library/mixin.lua

In keeping with the changes in #150, personal mixins can now be added to a personal_mixin folder. Personal mixins are checked first, so they can override a public mixin.
Added UI function which is the mixin equivalent of finenv.UI()

library/measurement.lua

Added methods that return an abbreviation for the measurement unit. I haven't come across an official abbreviation for EVPU or Pica, so let me know if you would like something different.

mixin_helper

Mainly just a large refactor to enable code reuse between custom control and window change events.

FCM Mixin Changes:

FCMCtrlEdit

Added some missing change event triggers

FCMCtrlPopup, FCMUI

Additional convenience methods.

FCMCustomWindow

Parent window is now stored and is accessible via GetParent while window is showing as modal.

FCMCustomLuaWindow

Command events occasionally fire twice (eg at Init, or when a child modal is opened) for the same control, the second while the first is still running. So I added a check to avoid concurrency issues and race conditions.

FCX Mixins:

FCXCustomLuaWindow

Includes the ability to set the measurement unit at the window level. This is then adhered to by the control mixins below.
Any control that has a method called UpdateMeasurementUnit will be instantly updated when the measurement unit is changed.

FCXCtrlMeasurementUnitPopup

This is a popup that allows the user to set the measurement unit for the window in the same manner as Finale's in-built dialogs (eg Document Options, Page Format, etc)

FCXCtrlMeasurementEdit

Displays measurements in the parent window's measurement unit and updates automatically when it changes.

FCXCtrlStatic

Added methods for setting a measurement value
Measurement values ares displayed in the parent window's measurement unit with the option to set a display suffix.

FCXCtrlUpDown

ConnectMeasurementEdit will only accept a FCXCtrlMeasurementEdit
Added methods to set a custom step size for different measurement units. I included a set of default step sizes which are more closely in harmony with the measurement unit they relate to, rather than a blanket step size of 1 EVPU. Let me know what you think or if any of the defaults need to be changed. Play around with the test script below to see it in action. There are different defaults depending on whether the MeasurementEdit's type is EVPU or EFIX.

Here is a script for testing out measurement edits, the new up/down mixin and the measurement unit popup:
local mixin = require("library.mixin")
local dialog = mixin.FCXCustomLuaWindow()

local edit = dialog:CreateMeasurementEdit(10, 10)

-- To test default EFIX step sizes, uncomment the line below
--edit:SetTypeMeasurementEfix()

dialog:CreateUpDown(80, 10):ConnectMeasurementEdit(edit, 0, 100)

dialog:CreateMeasurementUnitPopup(10, 40)

dialog:ExecuteModal(nil)

I would encourage you to get setup with Visual Studio Code using the recommended settings recently committed to the master branch. this will allow you to delint your code. The lastest mixin merge (#139) introduced a number of lint issues that look like they are probably bugs.

In keeping inline with Robert's suggestion, all you need to do is copy the contents of .vscode/recommended_settings.json into a new .vscode/settings.json, then install the recommended extensions (either VS Code will prompt you, or you can manually install the ones listed in .vscode/extensions.json.
This will give you several benefits:

Automatic code formatting
Linting to remove bugs and code likely to contain bugs
Better syntax highlighting and code completion

Okay, I have VS Code up and running and I have fixed all the linting issues that showed up.

@ThistleSifter unrelated to the PR, did you find getting VS Code setup easy? Any issues you may have run into?
I ask because Robert and I spent a long time trying to get things setup for him (finally just figured it out a week or two ago), and it would be great to get some feedback to see if we're on the right direction of helping others get setup as well.
The PR looks good to me.

I didn't run into any issues setting it up, but I have noticed that occasionally the style fixer does odd things.
Eg The comment in line 242 in mixin/FCMCtrlListBox.lua applies to the else below, so it should only be indented once, not twice.
I'm not a fan of some of the line splitting, although I understand that these boil down to personal preference so I'm not going to quibble about it:

Line 447 in mixin/FCMCtrlListBox.lua, which it won't let me split into multiple lines so it visually matches the following arguments.
I'd prefer to have the for...do in line 216 in mixin/FCMCusomWindow.lua be all on the same line
The splitting on line 32 and below in mixin/FCXCustomLuaWindow.lua isn't great.

I tend to agree with @ThistleSifter that I don't like the forced line splitting. In fact, I continue to do most of my editing in ZeroBrane because of the debugging. But it also allows me to fix lint issues found by VSCode without having to take the line splitting on board.

Since the comments about the formatter itself are valid but off-topic to this PR, I moved that conversation to a separate issue (#168). That way, we can also easily keep track of it in the future.
TLDR, I'm open to improving the automated formatting.
@rpatters1 , feel free to merge this PR if it looks good to you.


Icon not shown when toolbar its hidden

It would be nice to show the adb wifi icon even if the toolbar is hidden, as Fabric does

Wow @saulmm it could be great if you collaborate with this project implementing this feature!

Look @saulmm a new version is coming!


Fix usage of RISC-V toolchain

This PR introduces few changes:

switches to the active RISC-V toolchain version in CI,
ensures in Makefile that RISC-V toolchain is installed, it checks for bot 64-bit and 32-bit versions, in that order,
uses new march syntax for Zifencei extension in versions higher or equal to 12.2.0 of RISC-V toolchain.

Solves https://github.com/chipsalliance/caliptra-rtl/issues/371.

@robertszczepanski do you consider this ready to merge?


update webpack peer-dep

This PR updates the webpack peer-dependency to be the same as the one used in globalize-webpack-plugin

0.4.3 published


About Foundation and CoreFoundation

Hi,
During the configure I see that checks for Foundation and CoreFoundation are being made. The former is available on Linux through gnustep-base and the latter through OpenCFLite.
Would there be an interest to using those if they're available?

I don't use GNUStep or OpenCFLite myself, so I'm not really sure how to proceed here.
I do know that on iOS/OS X, dispatch_object_t's are also NSObjects -- I could look into how this works, with a view to supporting this feature on Linux as well.
libdispatch doesn't depend on CoreFoundation -- I think the configure check is to support conditional compilation of one unit test that tests interoperability with CFRunLoop's main loop. My libdispatch port should already provide all the bits necessary for interoperability with the main CFRunLoop via dispatch_main_queue_get_handle_np()/dispatch_main_queue_drain_np() methods.


Monitors in Maintenance Mode incorrectly shown in Monitor count

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
I have several monitors in maintenance as per the screenshot attached but they are showing in the Unknown count instead of Maintenance

👟 Reproduction steps
Unknown
👀 Expected behavior
Monitors shown in Maintenance count
😓 Actual Behavior
Monitors shown in Unknown count
🐻 Uptime-Kuma Version
1.19.4
💻 Operating System and Arch
Ubuntu 22.04.1 x86_64
🌐 Browser
Firefox
🐋 Docker Version
N/A
🟩 NodeJS Version
19.3.0
📝 Relevant log output
No response

Cannot reproduce. What are the monitor types? Is there anything special about your setup?

Standard HTTPS monitors. Install is done as per the wiki non-docker instructions.

I am able to reproduce.
when scheduled maintenance starts for monitor and monitor status changes from up or down to maintenance, value of unknown is increased instead of value of maintenance


fix to multi-class for ss4 support

Object create no longer exists

Although these are failing, it appears as though it's due to namespacing issues in core.


Put message body in email subject

Wouldn't it be better to back up SMS with From and To of the e-mail set to the corresponding values and the subject filled with the message itself? I can understand this might not work for MMS, but it would make reading a conversation thread much easier.  gammu does it this way but does not work with Android.

Thank you for the reply.
I wonder how gammu does it.  I guess it just cut things off if they are too long and repeats the message in the body.


[enhancement]: add Kandinsky 2.0 - the first multilingual text2image model

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
Ability to write Prompt in more than 100 languages.
Kandinsky 2.0
https://github.com/ai-forever/Kandinsky-2.0
https://huggingface.co/sberbank-ai/Kandinsky_2.0
Model architecture:
It is a latent diffusion model with two multilingual text encoders:
mCLIP-XLMR 560M parameters
mT5-encoder-small 146M parameters
These encoders and multilingual training datasets unveil the real multilingual text-to-image generation experience!
Kandinsky 2.0 was trained on a large 1B multilingual set, including samples that we used to train Kandinsky.
In terms of diffusion architecture Kandinsky 2.0 implements UNet with 1.2B parameters.

Alternatives
No response
Aditional Content
No response

Available in Diffusers now btw: https://huggingface.co/docs/diffusers/v0.19.3/en/api/pipelines/kandinsky#diffusers.KandinskyPriorPipeline

This can be added as a custom node very easily, using Diffusers.


routeRules stopped working in 2.9 when deployed to Azure

Environment

Operating System: Windows_NT
Node Version:     v21.7.2
Nuxt Version:     3.11.2
CLI Version:      3.11.1
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      future, alias, nitro, experimental, vue, hooks, app, modules, runtimeConfig, routeRules, tailwindcss, graphqlServer, content, site, vite
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>storybook-vue-addon/nuxt<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://github.com/JabRef/JabRefOnline/pull/2370 not really a "minimal reproduction" but since there are issues with the deployment of the nitro example in https://github.com/unjs/nitro-deploys, I'm not sure where I should start
Describe the bug
After the upgrade from nitro 2.8.1 to 2.9.0 (or 2.9.6) all routes defined in nuxt.config as well as all pages except for the index are resulting in 404 errors when deployed to azure functions. Strangely, also the server routes are working correctly (in my case /api). I cannot reproduce it locally with the azure cli, and running the dev server locally also works. No errors are logged in the azure portal. Hence, I have no idea how to investigate this issue further.
If you have any idea what change could have triggered this, can try it again with a patched version.
Additional context
Perhaps https://github.com/nuxt/nuxt/issues/26567 is related
Logs
No response

Seems to be working now.


Missing plot_reconstruction.py

The file plot_reconstruction.py seems to be missing.

Hi,
That file shouldn't be listed in the documentation as it doesn't exist! I'll remove it from the README.
The proper way to use the DGP code is to first run reconstruct_surface.py or reconstruct_single_patch.py (see the README for instructions and examples). This file produces a .pt file (you specify the name with -o, e.g. -o mymodel outputs mymodel.pt.
To generate an upsampled pointcloud from the .pt file outputted by reconstruct_surface.py or reconstruct_single_patch.py, you must run export_point_cloud.py with the .pt file as an argument. export_point_cloud.py outputs a ply file with a dense point cloud which you can visualize in any software supporting PLY. Run the script with -h to see the full set of parameters used to control the upsampled point cloud.


Add depth and offset field to heading

As discussed proposed in #2768, this adds the depth and offset parameter to the heading element, resolves #2768. Allowing one to set offset: 1, resulting in all headings to start at level 2:
= Level 1
== Level 2
=== Level 3

#set heading(offset: 1)
= Level 2
== Level 3
=== Level 4

Tasks

[x] Implementation
[x] Tests
[ ] Documentation

Remaining Questions

Should offset and depth be included in the field synthesis?
Do we use depth instead of level for bibliography and outline headings? This would make them respond to offset.
Should depth and level be swapped or changed? Their names, as well as their documentation, are likely still confusing to the average user. I'm looking for suggestions to improve this, but I generally want to keep level to be the resolved value, to reduce breakage.

It turns out, something that seemed to have worked before doesn't anymore with my changes:
#let it = [= Heading]
#it.body \
#it.level

A show rule like this works:
#show heading: it => it.level

=
==
===

I'm wondering why the previous example stopped working after I rebased from d77356a16f3d2493709f5ebd78c0ce489a4fd98c to b1256283da047fd4e2c0ba24d981759c745661b.
I only changed the type of level, not any of its attributes. Shouldn't it be auto in the first example? That also opens the question if it should be resolved here too somehow, or if it should be exposed as a function instead.
I left the scripting.md file unchanged, which causes the test failure.

Ok, it seems that's inline with what would've happened if I did it.numbering, so I'll simply change the example to use depth.

I like this in general. I still have this small feeling that we should realize this with a more general solution, but given that it solves a real problem and no properly working general solution (with support for selectors etc.) is in sight, I think we could go ahead with this.

I've opted to call depth the "relative nesting depth" and level the "the absolute nesting depth" in the docs. And added some examples, I think this makes the distinction clearer.
If you have better ideas for the name of depth itself, I'm all ears.

Thank you!


Boxplot as a feature?

Good afternoon,
I use Excel's Boxplot charts quite often in managing my business/life. I would love to see Boxplot charts in fl_chart, as I have numerous places I can use it in my own projects.
Although I've been a solo developer for as long as I can remember, I've never contributed to an open-source project.
I would like to tackle this feature, but would not want to tread on any toes. Is there somebody who can guide me through the process of adding Boxplot charts to this project?

Hi @DooRooSA
Contribution can be started simply.
For example, now you are contributing to this project by mentioning your issue (demanding a new chart).
Yes trust me, this is a contribution!
BTW, start by reading our CONTRIBUTING guideline
Your next step can be finding a simple issue to fix, I tried to group some simple issues here.
Then start reading our ScatterChart source code. It's our simplest cartesian-based chart.

Anyways it seems like a candle stick chart. Correct?
If yes, there is another open issue here: #433.
We can close it and follow it up there.

Thank  you, I will certainly look at starting on some of the simpler issues first to get used to the process.
As for the boxplot vs candlestick, they are certainly different charts altogether. As I understand the candlestick is used for trading financial instruments. The boxplot is a statistical analysis chart that shows the median, quartiles and maximum and minimum values of a dataset. It can also be configured to display the outliers, which is very useful to see. The boxplot shines in the fact that you can quite easily see if your data is skewed.
Although they look similar, their purpose is vastly different. I suppose the boxplot can also be grouped in a similar way that the BarChart is grouped on fl_chart (possible code re-use?). The image below is the format that I use 99% of the time, so this format would be a good starting point in my opinion, as it encompasses most of the features of a boxplot.

I'm thinking of having a generic CandleStickc chart that supports both usecases.
They have a lot of shared things to draw.
What are those dots?

I agree, the visuals are very similar.
The dots are the outliers. I'm including a screenshot of Excel that I made to explain them. Here is a list of numbers between 20 and 30. The last 3 numbers, fall outside those two values. I've marked them in orange in the table. You will notice that the values 8, 6 and 41 are indicated as outliers on the chart

I got it.
They are pretty similar. Let's close it and continue on #443.

Please put your samples on #443 thread.


Broken CI

Not sure since when (maybe since #199? - @jscotka) but Zuul CI doesn't seem to work. (see #207, #208)
TASK [wait for tests to finish]
task path: /home/zuul-worker/src/github.com/packit-service/packit-service/files/check-inside-openshift.yaml:52
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["oc", "wait", "job/packit-tests", "--for", "condition=complete", "--timeout=300s"], ... "stderr": "error: timed out waiting for the condition", "stderr_lines": ["error: timed out waiting for the condition"]
[localhost] TASK: wait for tests to finish (debug)> User interrupted execution
make: *** [Makefile:77: check-inside-openshift-zuul] Error 99

There were more issues, what start it failing:

several PR what was started before these tests were fixed ans was not rebased before merge.
some of these PRs touched COPR part of packit service, what is covered by these tests.
it is nontrivial to debug it ansible+OS (because you have no logs from machine in case it fail)

There were enough to regenerate files and it started PASS again https://github.com/packit-service/packit-service/pull/211
And possible AI would be to improve ansible+openstack debugging (eg) somehow run it, not fail, return results and then pass/fail based on status of run command, to avoid, that ansible inside openshift hides deeper information what happen there.

Thanks for investigation!


When retrieving a list of invoices, the invoice_url is always null

When I retrieve a list of invoices through the java wrapper, the invoice_url field is always null. When I try the same with a pure REST client (no java wrapper), the invoice_url is populated.

To anyone having the same issue: don't expect this to be fixed anytime soon as Zoho support has confirmed that they have dropped support for the java client.


Black screen "No video recieved from host"

I'm unable to get Moonshine to function. On the client after trying to connect through Moonlight, it gives a black screen with a weird broken white border and after awhile "No video recieved from host". I'm using Arch Linux on the host with a GTX 2080ti. I followed the directions on the main page but maybe I missed something. What could cause this?

Is it because I'm using KDE Plasma on Wayland? Does this project not support Wayland at the moment?

On the host side you need to use X, unfortunately. It's a limitation in the
frame capture library from Nvidia.
On Wed, Oct 9, 2024, 06:20 zoobporsor @.***> wrote:

Is it because I'm using KDE Plasma on Wayland? Does this project not
support Wayland at the moment?
—
Reply to this email directly, view it on GitHub
https://github.com/hgaiser/moonshine/issues/13#issuecomment-2400978919,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFO22RL5DXZEMRFLIRKZT3Z2RSFNAVCNFSM6AAAAABPTJRJFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBQHE3TQOJRHE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

EDIT: Well, the same thing happens on X11 session, So I guess its not that
I am using the latest nvidia-open drivers on arch, everything is stock and default. Do I need to do some custom Nvidia patched driver thing to get the encoders to work properly on Linux or something?

A patched driver shouldn't be necessary, but it's worth a try. I wasn't using the nvidia-open drivers, but I think I did at some point and it worked as well.
Are there any error messages on the host side?

Closing, let me know if this is still an issue (feel free to reopen in that case too).


Functionalize the entrypoint to allow outside sourcing for extreme customizing of startup

This will allow a user to write a script to use our script as a base for their own postgres startup.
We need to ensure that that we define the set of functions that users can call. Currently that is any function that doesn't start with an underscore (listed below):
file_env
# create_postgres_dirs
docker_create_db_directories
# init_pgdata
docker_init_database_dir
docker_verify_minimum_env
docker_process_init_files
docker_process_sql
docker_setup_db
docker_setup_env
pg_setup_hba_conf
docker_temp_server_start
docker_temp_server_stop

EDIT: example updated (and tested) with an example docker run.
Here is an example using the current interface to run other init scripts on every start:
#!/usr/bin/env bash
set -Eeo pipefail

# Example using the functions of the postgres entrypoint to customize startup to always run files in /always-initdb.d/

source "$(which docker-entrypoint.sh)"

docker_setup_env
docker_create_db_directories
# assumption: we are already running as the owner of PGDATA

# This is needed if the container is started as `root`
#if [ "$1" = 'postgres' ] && [ "$(id -u)" = '0' ]; then
#	exec gosu postgres "$BASH_SOURCE" "$@"
#fi

if [ -z "$DATABASE_ALREADY_EXISTS" ]; then
	docker_verify_minimum_env
	docker_init_database_dir
	pg_setup_hba_conf

	# only required for '--auth[-local]=md5' on POSTGRES_INITDB_ARGS
	export PGPASSWORD="${PGPASSWORD:-$POSTGRES_PASSWORD}"

	docker_temp_server_start "$@" -c max_locks_per_transaction=256
	docker_setup_db
	docker_process_init_files /docker-entrypoint-initdb.d/*
	docker_temp_server_stop
else
	docker_temp_server_start "$@"
	docker_process_init_files /always-initdb.d/*
	docker_temp_server_stop
fi

exec postgres "$@"

$ docker run -it --rm \
  -e POSTGRES_PASSWORD=12345 \
  -v "$PWD/custom-entrypoint.sh":/usr/local/bin/custom-entrypoint.sh \
  -v "$PWD/docker-entrypoint-initdb.d/":/docker-entrypoint-initdb.d/ \
  -v "$PWD/always-initdb.d/":/always-initdb.d/ \
  -v "$PWD/data/":/var/lib/postgresql/data/ \
  --name=pg --user=1000 \
  postgres:11-test custom-entrypoint.sh -c 'max_locks_per_transaction=512'

Closes #463, closes #461
EDIT: Threading the needle; related to https://github.com/docker-library/rabbitmq/pull/281
EDIT: applied new function names from discussion and nearing completion of https://github.com/docker-library/mysql/pull/471 (rebased commits incoming)

I wonder if it'd make sense to namespace our functions to be more considerate of other functions folks might be using -- something like docker_xxx?
FYI @ltangvald (this is probably relevant to your interests for https://github.com/docker-library/mysql/pull/471 -- it'd be great if we could get both using a similar approach :heart:)

Yeah, makes sense. Prefixing everything with docker_ sounds good to me :)

I really miss support for `/docker-entrypoint-always.d/* as a place where to store your own scripts that would be executed always before the postgres server is started.
Many times one needs to ensure some DB configurations state, no matter if the DB existed previously or not.
Do you think this is a good chance to tackle that?

@Yajo, the example I show for possible user customization includes exactly that and allows for all sorts of other customization.

Any news on this PR? I would love to have the chown fix 👍

Any update on this? Our use case is very similar to that of @Yajo

Left out applying update.sh until consensus is reached.

This will allow a user to write a script to use our script as a base for their own postgres startup.
We need to ensure that that we define the set of functions that users can call. Currently that is any function that doesn't start with an underscore (listed below):
file_env
# create_postgres_dirs
docker_create_db_directories
# init_pgdata
docker_init_database_dir
docker_verify_minimum_env
docker_process_init_files
docker_process_sql
docker_setup_db
docker_setup_env
pg_setup_hba_conf
docker_temp_server_start
docker_temp_server_stop

EDIT: example updated (and tested) with an example docker run.
Here is an example using the current interface to run other init scripts on every start:
#!/usr/bin/env bash
set -Eeo pipefail

# Example using the functions of the postgres entrypoint to customize startup to always run files in /always-initdb.d/

source "$(which docker-entrypoint.sh)"

docker_setup_env
docker_create_db_directories
# assumption: we are already running as the owner of PGDATA

# This is needed if the container is started as `root`
#if [ "$1" = 'postgres' ] && [ "$(id -u)" = '0' ]; then
#	exec gosu postgres "$BASH_SOURCE" "$@"
#fi

if [ -z "$DATABASE_ALREADY_EXISTS" ]; then
	docker_verify_minimum_env
	docker_init_database_dir
	pg_setup_hba_conf

	# only required for '--auth[-local]=md5' on POSTGRES_INITDB_ARGS
	export PGPASSWORD="${PGPASSWORD:-$POSTGRES_PASSWORD}"

	docker_temp_server_start "$@" -c max_locks_per_transaction=256
	docker_setup_db
	docker_process_init_files /docker-entrypoint-initdb.d/*
	docker_temp_server_stop
else
	docker_temp_server_start "$@"
	docker_process_init_files /always-initdb.d/*
	docker_temp_server_stop
fi

exec postgres "$@"

$ docker run -it --rm \
  -e POSTGRES_PASSWORD=12345 \
  -v "$PWD/custom-entrypoint.sh":/usr/local/bin/custom-entrypoint.sh \
  -v "$PWD/docker-entrypoint-initdb.d/":/docker-entrypoint-initdb.d/ \
  -v "$PWD/always-initdb.d/":/always-initdb.d/ \
  -v "$PWD/data/":/var/lib/postgresql/data/ \
  --name=pg --user=1000 \
  postgres:11-test custom-entrypoint.sh -c 'max_locks_per_transaction=512'

Closes #463, closes #461
EDIT: Threading the needle; related to docker-library/rabbitmq#281
EDIT: applied new function names from discussion and nearing completion of docker-library/mysql#471 (rebased commits incoming)

Hi @yosifkit I'm following this reference for a custom entry point to cache the database I create. I've below command in my Dockerfile
RUN custom-entrypoint.sh postgres || exit 0
ENTRYPOINT [ "custom-entrypoint.sh" ]

However when it run the RUN custom-entrypoint.sh postgres I get below error always, bcz of exec command in custom-entrypoint.sh (exec postgres "$@"). Are you able to provide any workaround to resolve this error please ?
postgres: invalid argument: "postgres"
Try "postgres --help" for more information.

I've removed that exec command from custom-entrypoint.sh, and moved to Dockerfile as below, And that seems to be working. But not sure that's the ideal way to do this ? Highly appreciate your thoughs
RUN custom-entrypoint.sh postgres || exit 0
CMD ["postgres"]
ENTRYPOINT [ "custom-entrypoint.sh" ]

@Chanaka, yeah you only need the postgres in one spot; either in the exec postgres "$@" or as an argument to the entrypoint (custom-entrypoint.sh postgres).
It depends on how you expect to use the custom entrypoint script. If you plan on allowing running things that aren't postgres, like bash or echo, then just ending with exec "$@" is what you want. If you just want the custom entrypoint only running postgres, then make that part of the script and not passing it in.   In the default entrypoint, we do both and detect the desire to run postgres by it being the default CMD (i.e. "$1" = postgres) or by the first argument being a flag (starts with a dash, -.
For your use case, you'll probably need to set PGDATA to somewhere outside the already defined VOLUME of /var/lib/postgresql/data so that the database gets saved in the resulting image (like https://github.com/docker-library/postgres/issues/672).

@yosifkit I also had the chanaka's issue so I followed your instrauctions.
Changed Dockerfile to ENTRYPOINT [ "custom-entrypoint.sh","postgres"]
Changed cutome-entrypoint.sh to exec "$@"
but I build the image using this command docker image build --tag myDb:latest .
My build step hangs with below logs
2020-03-08 02:54:46.096 UTC [8] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432 2020-03-08 02:54:46.096 UTC [8] LOG:  listening on IPv6 address "::", port 5432 2020-03-08 02:54:46.102 UTC [8] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2020-03-08 02:54:46.116 UTC [55] LOG:  database system was shut down at 2020-03-08 02:54:46 UTC 2020-03-08 02:54:46.126 UTC [8] LOG:  database system is ready to accept connections
I don't run the image yet. I only need the images created and tagged so I can run them later.I have other stuff needs to happen after database image creation.
But currently it seems container starts and stays there.
Simply I need this ,
1. Start postgres     2. Load the database and build an image with database     3. Tag the image so I can use that image in later step
How can I resolve this ?

My build step hangs with below logs

If you are running the entrypoint in a RUN step, then you need your script to initialize and exit (not to start postgres). So the if [ -z "$DATABASE_ALREADY_EXISTS" ]; then block should exit and not fall through to the exec


x/pkgsite: display table of contents (TOC) in command documentation

What is the URL of the page with the issue?
https://pkg.go.dev/cmd/go
Screenshot

What did you do?
Visited command documentation. As an example, see https://pkg.go.dev/cmd/go, but this applies to any command (package with name "main").
What did you expect to see?
A table of contents, like on https://golang.org/cmd/go:

What did you see instead?
No table of contents.
This is a feature request to have feature parity with previous documentation rendering on golang.org and the godoc package documentation viewer.
/cc @julieqiu

A table of contents, like on https://golang.org/cmd/go:

Did you perhaps intend for the comparison here to be with https://godoc.org/cmd/go?

I meant to compare with golang.org. godoc.org doesn't implement this feature.
Some implementation notes.
golang.org renders (via x/tools/godoc package) the table of contents on the frontend via a generateTOC function here:

https://github.com/golang/tools/blob/a49f79bcc2246daebe8647db377475ffc1523d7b/godoc/static/godocs.js#L369

pkg.go.dev does not need to do this on the frontend, it can render a table of contents on the backend (together with the where all of package documentation rendering currently happens).
This table of contents is applicable only for commands; library packages already have a table contents (it displays the functions, types, methods, etc.).
x/tools/godoc uses a div named "manual-nav" to disable the frontend from generating a table of contents for non-commands. See:

https://github.com/golang/tools/blob/a49f79bcc2246daebe8647db377475ffc1523d7b/godoc/static/godocs.js#L33-L35
https://github.com/golang/tools/blob/a49f79bcc2246daebe8647db377475ffc1523d7b/godoc/static/package.html#L57-L58

Here is a mockup of the TOC feature.

Index and "Jump to" feature for command documentations would be nice too.

@hyangah that's a good idea, would you file that under a new issue? We'll need some discussion and UX review to figure out how it would work.


Adding more caching to GL backend. (#1221)

See #1221 from v0.14 branch

:umbrella: The latest upstream changes (presumably #1234) made this pull request unmergeable. Please resolve the merge conflicts.

@homu r+

:pushpin: Commit e48fb69 has been approved by kvark

:hourglass: Testing commit e48fb69 with merge 038cfa0...

:sunny: Test successful - status


fix requirements in setup.py and README

I tried to install nematus and I discovered a comma missing in setup.py. And I need to install bottle before running python setup.py install. Therefore, I added it to README.md pip command.

thanks - pulled!


boilerplate preprocess module for conversion to png with logging

put the  to /input/

invoke the module as
python3 preprocessing.py <file to convert>

output file goes to /converted/

Requirements: PIL
can be installed by :
pip3 install PILLOW

Good stuff, but we can merge in at the end of this Sprint with the entire preprocessing routine integrated within the application.


Add action to remove current file

I would like there to be HarpoonerRemoveFile action, which removes the currently viewed file from the harpoon list if it exists there. If the maintainer approves, I can implement & PR it myself.

Hei @InfiniteRain!
Yeah, it'd be awesome if you implemented it since I don't have much time now.
The code could use some cleaning up when I look at it after awhile 😬😅
You'd probably need to

add method to a service
register an action in the plugin.xml
Then I'll redeploy the plugin

I hope it will help!


IOS Undefined symbols for architecture x86_64

ld: warning: ignoring file /Users/TWY/servers/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_openim_sdk-0.0.9+6/ios/Framework/OpenIMCore.framework/OpenIMCore, missing required architecture x86_64 in file /Users/TWY/servers/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_openim_sdk-0.0.9+6/ios/Framework/OpenIMCore.framework/OpenIMCore (1 slices)
Undefined symbols for architecture x86_64:
"_Open_im_sdkForceSyncMsg", referenced from:
flutter_openim_sdk.MessageManager.forceSyncMsg(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkCreateCardMessage", referenced from:
flutter_openim_sdk.MessageManager.createCardMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkCreateCustomMessage", referenced from:
flutter_openim_sdk.MessageManager.createCustomMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkCreateLocationMessage", referenced from:
flutter_openim_sdk.MessageManager.createLocationMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkCreateMergerMessage", referenced from:
flutter_openim_sdk.MessageManager.createMergerMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkCreateFileMessageFromFullPath", referenced from:
flutter_openim_sdk.MessageManager.createFileMessageFromFullPath(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkCreateVideoMessageFromFullPath", referenced from:
flutter_openim_sdk.MessageManager.createVideoMessageFromFullPath(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkCreateVideoMessage", referenced from:
flutter_openim_sdk.MessageManager.createVideoMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkCreateImageMessageFromFullPath", referenced from:
flutter_openim_sdk.MessageManager.createImageMessageFromFullPath(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkCreateSoundMessageFromFullPath", referenced from:
flutter_openim_sdk.MessageManager.createSoundMessageFromFullPath(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkCreateImageMessage", referenced from:
flutter_openim_sdk.MessageManager.createImageMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkCreateTextAtMessage", referenced from:
flutter_openim_sdk.MessageManager.createTextAtMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o
"_Open_im_sdkMarkC2CMessageAsRead", referenced from:

先用真机吧

ld: warning: ignoring file /Users/TWY/servers/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_openim_sdk-0.0.9+6/ios/Framework/OpenIMCore.framework/OpenIMCore, missing required architecture x86_64 in file /Users/TWY/servers/flutter/.pub-cache/hosted/pub.flutter-io.cn/flutter_openim_sdk-0.0.9+6/ios/Framework/OpenIMCore.framework/OpenIMCore (1 slices) Undefined symbols for architecture x86_64: "_Open_im_sdkForceSyncMsg", referenced from: flutter_openim_sdk.MessageManager.forceSyncMsg(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkCreateCardMessage", referenced from: flutter_openim_sdk.MessageManager.createCardMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkCreateCustomMessage", referenced from: flutter_openim_sdk.MessageManager.createCustomMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkCreateLocationMessage", referenced from: flutter_openim_sdk.MessageManager.createLocationMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkCreateMergerMessage", referenced from: flutter_openim_sdk.MessageManager.createMergerMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkCreateFileMessageFromFullPath", referenced from: flutter_openim_sdk.MessageManager.createFileMessageFromFullPath(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkCreateVideoMessageFromFullPath", referenced from: flutter_openim_sdk.MessageManager.createVideoMessageFromFullPath(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkCreateVideoMessage", referenced from: flutter_openim_sdk.MessageManager.createVideoMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkCreateImageMessageFromFullPath", referenced from: flutter_openim_sdk.MessageManager.createImageMessageFromFullPath(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkCreateSoundMessageFromFullPath", referenced from: flutter_openim_sdk.MessageManager.createSoundMessageFromFullPath(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkCreateImageMessage", referenced from: flutter_openim_sdk.MessageManager.createImageMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkCreateTextAtMessage", referenced from: flutter_openim_sdk.MessageManager.createTextAtMessage(methodCall: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in MessageManager.o "_Open_im_sdkMarkC2CMessageAsRead", referenced from:

先用真机

Please update the sdk to : 1.0.2


Beta opt in instruction updates.

Thanks for bringing this to our attention, @pinae

merged via b0767a07101657859331ea42244eb0a217d3147e


[BUG]

Versions
Spigot/Paper/Sponge:
GriefDefender: 2.0.7
LuckPerms: 5.3.89

_Describe the bug
i can't /ignoreclaims , while I'm op, and it says i don't have permission. I am new to this and I am very lost, a link or step by step would be helpful.

Steps to reproduce the behavior
go to claim, then type /ignoreclaims

Expected behavior
i will be able to open players chests and destroy,etc

OP means nothing in GD. Assign the proper permissions as stated on permission page.
https://github.com/bloodmc/GriefDefender/wiki/Permissions


TST: ubuntu-16.04 about to reach EOL; upgrade to ubuntu-latest

According to the Ubuntu release schedule, Ubuntu Xenial 16.04 is to reach it's end of standard support in a few days. Upgrading to ubuntu-latest, which is currently an alias to Ubuntu Focal 20.04.

Coverage remained the same at 85.133% when pulling 2b124435a8b5f61bff505c936aeb0a40f420668c on mwtoews:ubuntu-latest into 9667fe86b6668deb319e6eb0479bc84e5f6e73ee on Toblerity:master.


add logging

<!-- Thank you for submitting a Pull Request. Please:

Read our Pull Request guidelines:
https://github.com/microsoft/vscode/wiki/How-to-Contribute#pull-requests
Associate an issue with the Pull Request.
Ensure that the code is up-to-date with the main branch.
Include a description of the proposed changes and how to test them.
-->

This PR fixes #

pinging @TylerLeonhardt since this PR comes from a branch of yours.

This is a really old branch of mine that I used for debugging purposes only. I'm gonna close this since I never intended on it going in.


No coverage information can be collected when using istanbul inside npm test

So I have this repo setup to with npm test as istanbul cover ava -- test/**/*.spec.js.
However running npm test results in the tests running but istanbul exits saying, No coverage information was collected, exit without writing coverage information.
Which is weird because simply running istanbul cover ava -- test/**/*.spec.js manages to collect the coverage information just fine.
I've pinned the difference down to the published npm version(0.2.0) and the version on github. The only reason I started using the GH version was for beforeEach.

Read through #47  and found nyc.
Changed to that and everything works.


chore(main): release prisma-model-types 0.1.10

:robot: I have created a release beep boop
0.1.10 (2023-06-02)
Bug Fixes

model-types: Remove old ModelTypes namespace (077ece9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/BradenM/prisma-utils/releases/tag/prisma-model-types-v0.1.10 :sunflower:


Simultaneous Jobs.

According to #667, Simultaneous builds/jobs is not supported yet.
I would like to know what's currently prevents strider CD from supporting that.
Is it the runners, or strider itself?
I am currently writing a runner that run the code in a Google Compute Engine slave VM.
I managed to get it to work for 1 slave, my runner is extending the [simple runner] (https://github.com/Strider-CD/strider-simple-runner), just like the docker runner.

Probably both, but we are focusing efforts to support that with the new API which is being developed under Strider-CD/core.
Do you have your runner published anywhere?

is the new API usable/ready?

No, it's still in prototype mode and we'd love all the help/feedback/ideas we can get.


Remove duplicated BIO_get_ktls_send calls in do_ssl3_write

This rather long function used to call BIO_get_ktls_send
mutliple times, although that result cannot change during
the execution of that function.
There was a similar unnecessary call to BIO_get_ktls_recv
in ssl3_get_record.
And while I'm already there, rewrite ssl3_write_bytes
to use BIO_get_ktls_send as a boolean (so using "!" instead
of "== 0").
This is just a re-factoring change, and is expected to allow
some additional compiler optimizations.

Refactorings are not allowed on stable branches unless part of a larger bug fix.

This PR is in a state where it requires action by @openssl/otc but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

This pull request is ready to merge

Merged to master. Thank you.


use videohub_ref id

@jmelvnsn @mparent61 Like this?

Coverage decreased (-0.1%) to 85.763% when pulling 41fd9df741103745fcb5d01f8601e3c9caafe87a on use-videohub-ref-id into 6cdafe8e1b81598cd85b4d74c443706ed15a0e58 on master.

Coverage decreased (-0.2%) to 85.685% when pulling 41fd9df741103745fcb5d01f8601e3c9caafe87a on use-videohub-ref-id into 6cdafe8e1b81598cd85b4d74c443706ed15a0e58 on master.


Fix xinput GetApi()

Summary of the PR
Adds an implementation of GetApi() for XInput which currently throws a not implemented exception.
Related issues, Discord discussions, or proposals
https://discord.com/channels/521092042781229087/587346162802229298/1007383458978467920
Further Comments
None.

Did some tests and after installing the DirectX 2010 sdk it is working fine.


IPv6?

What should we be doing if our network is IPv4/IPv6?  Do we need to block IPv6 for the host(s) using this gateway?  What's the best way to do this?

I would block IPv6 in general, and disable it on the devices you want using the VPN.  IPv6 will just be a big headacke otherwise.


[BUG]AndroidManifest.xml:316: error: '@2030305280' is incompatible with attribute resource (attr) reference

Information

Apktool Version (apktool -version) -2.9.0
Operating System (Mac, Linux, Windows) - Windows 10
APK From? (Playstore, ROM, Other) - F-Droid
Java Version (java --version) - java 12.0.2

Stacktrace/Logcat

Steps to Reproduce

Download https://f-droid.org/repo/org.totschnig.myexpenses_665.apk and rename it to test.apk
Put apktool.bat, apktool.jar, test.apk in one folder

Run .\apktool.bat d .\test.apk

Run .\apktool.bat b test -o new.apk

APK
https://f-droid.org/repo/org.totschnig.myexpenses_665.apk
Questions to ask before submission

Have you tried apktool d, apktool b without changing anything? Yes
If you are trying to install a modified apk, did you resign it? No, I'm not trying to install it.
Are you using the latest apktool version? Yes

Thanks for the report. I'm tracking this in this issue: https://github.com/iBotPeaches/Apktool/issues/3183
This comment in specific: https://github.com/iBotPeaches/Apktool/issues/3183#issuecomment-1644070864
Thanks - closing as duplicate.


Suppressed distributed logs

Issue #, if available:
#493 (Redo the fix after modularization)
Description of changes:
Suppresses distributed log spam
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-771-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-771/2/index.html


example source code unreadable

The code examples on redux-form.com/5.0.1 are unreadable; they have a black background and the text is a shade of grey that disappears into the background.
One example is here, but all the examples i viewed have the same problem.  The only way to view the code is to highlight/copy/paste somewhere.
/Users/jseidel/Pictures/2016-04-13_1902_ExamplesUnreadable.png

Looks fine to me, could be your browser?

Sounds like you're not getting the code formatting CSS. My best bet is that you have a security-conscious browser extension that is forbidding third party css.

Thanks, Erik... that was the problem: Privacy Badger on Chrome -- it's history now and so is this issue.


Refine readme

We should not have a build_prereqs.sh script, for many reasons:
* Its not tested, so can become outdated as dependencies change

I created this script by making some changes to a script from Mev. It worked well for me.

* Its required to run as sudo which may not be possible for some users
* It only works with ubuntu
* We have to maintain two lists of dependencies

It would be better to just add the apt install command needed for ubuntu before installing rbuild.
If we do add a build_prereqs.sh script then it should be called from the docker files and use cget to build the dependencies like what we do currently in the dockerfile.
This is a good approach, and the script should also works called directly by a user. So the following aspect should include:

installing rbuild (either use sudo or specify the user as you mentioned later)
command to ignore the packages
command to cget init
command to install packages.

I created this script by making some changes to a script from Mev. It worked well for me.

I dont mean that it currently doesn't work, just that since its not tested in our CI, it could easily become outdated. Furthermore, I would like to avoid doubling our testing in order to ensure this is tested in our CI.

I have tested the steps, and did not see any issues.
Tested 1st method in a ROCm installed system, there are no issues and easy to follow.
Tested 3rd method with docker. It points back to 2nd method, I did not see any issues building MIGraphX inside the docker.
Did not test Calling MIGraphX APIs. Looks straightforward to change cmake.
Building documentation works okay too.
One small recommendation is to maybe add bullet lists to Building from source first paragraph for the three steps mentioned. It would improve readability. Otherwise all good to me.

I have tested the steps, and did not see any issues.
Tested 1st method in a ROCm installed system, there are no issues and easy to follow.
Tested 3rd method with docker. It points back to 2nd method, I did not see any issues building MIGraphX inside the docker.
Did not test Calling MIGraphX APIs. Looks straightforward to change cmake.
Building documentation works okay too.
One small recommendation is to maybe add bullet lists to Building from source first paragraph for the three steps mentioned. It would improve readability. Otherwise all good to me.

Thanks for the suggestion, just changed accordingly.


Accuracy 1-100

Describe your problem here.
How do I get the accuracy from 1 - 100 but there is only 2 decimal places
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Only added a few mods

That's already in for version 0.5 and onward

That's already in for version 0.5 and onward

In LUA

Dude, stop using 0.4.2.  Like I said, that's already in 0.5 and onward, so switch to that please

Update your Psych Engine version.


How to hook location.href

Hi,How to hook location.href,get the value of it,and not navigate to other pages,tks!

Just get it from the page using page.evaluate:
console.log('location.href: ' + await page.evaluate(() => location.href));


Update CONTRIBUTING.md

Description
I added a line to add files before committing the messages
Fixes:  #232

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist:

[x] I have made this from my own
[ ] I have taken help from some online resourses
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

Please mention the Issue no for this pull request


Move voodoo to OCaml.org or ocaml-docs-ci

OCaml.org is split into three repositories:

OCaml.org
Voodoo
ocaml-docs-ci

This makes maintenance more complicated than it needs to be and increases the entry bar for new contributors for seemingly no added value. While the docs pipeline should probably remain separated from OCaml.org, we can merge voodoo with one of the other repositories. I'm in favour of moving it to the ocaml-docs-ci repository as it is essentially defining the behaviour of the pipeline, so it seems like a better separation of concerns.

IMO, the most confusing thing about voodoo as a newcomer is the name. It doesn't give any hints on what this actually does. So I would be in favor of renaming voodoo to something more descriptive, e.g. like package-docs-gen
We have here:

ocaml.org: the webserver. It looks up data, then renders HTML pages. In ocaml.org's repository also lives the data-generator ood-gen which generates HTML for various data items on ocaml.org.
voodoo: the package documentation generator. Given a package, it generates data in a format that ocaml.org consumes.
ocaml-docs-ci: the system that creates tasks that run the package documentation generator. Since the data is dynamically changing all the time, as people publish new packages and versions, it makes sense that this is separate from ocaml.org, so that the substantial complexity of building package documentation in the background is insulated from ocaml.org.

I would argue that changes to voodoo and ocaml.org often go hand-in-hand, so I think that your earlier idea of co-locating voodoo within ocaml.org's repository would be fine. Newcomers to ocaml.org development need to easily find where the package documentation data is generated, when they need to make changes to the package documentation webpages. They don't need to see all the complexities of the pipeline for that.
However, to move voodoo somewhere else, we first need a solid plan for how to handle upgrades of voodoo.

Moving to either OCaml.org or ocaml-docs-ci would simplify the whole setup, so I'm fine with anything you prefer!

Move into ocaml.org and expose voodoo via Dockerfile with opam-repository pin sounds sane to me.

This relocation will help us with our centralization efforts. I've provisionally re-assigned this to @cuihtlauac, thinking that his experience with ocaml.org may provide useful context. But we should talk about how to move forward here and whether it is a good fit synchronously.