feature: convert CBOR to JSON (and vice versa) with unknown content

What version of fxamacker/cbor are you using?
<EMAIL_ADDRESS>Does this issue reproduce with the latest release?
Yes.

See my (hopefully minimalistic) example code here.
https://play.golang.org/p/5YMin1Qw6kI
I've got some code that is acting as a proxy. At the one side (client) I exclusively communicate in CBOR and at the other side (server) I exclusively communicate in JSON. Therefore, I need to convert CBOR to JSON and vice versa. During these conversions, the content can be anything, so I have no knowledge over the object that is being transferred. I don't need to do anything with the content, so if there is a way to make these conversions without first creating the 'native' objects, please let me know.
As far as I can see there are 2 issues with the conversion from JSON to CBOR.

The numbers are converted to floats.
I've played around with the EncOptions a bit and searched through the docs and examples, but coudn't get it working as I expect. I do see a difference between the size of the encoded number when I add and use the different ShortestFloat options. Nonetheless, it always stays a float.
The datetime is not converted as datetime format (tag 1).
The datetime is a string in the CBOR object. I've tried playing around with the EncOptions for Time and some of the tag related options, but it always kept being a string.

I don't even know if this is the correct approach to do this conversion so am also very open to pointers to a different approach if there is a better one!
Also: this is the first time I'm using this library and I'm relatively new to Go, so maybe I'm overlooking something very obvious too :p Any help would be greatly appreciated.
I think I've got the conversion of CBOR to JSON (playground) except for a separate issue with the datetime.
What did you expect to see?

I expected for the numbers to be converted as integers.
I expected the date to be converted to a timestamp item (tag 1).

What did you see instead?

The numbers are converted to floats.
The date is a string.

@jdbruijn thanks for opening this issue.
Given the code snippet doing:
JSON --> encoding/json --> interface{} --> fxamacker/cbor --> CBOR
We should expect:
A. When interface{} contains Go time.Time value, fxamacker/cbor outputs CBOR datetime.
B. When interface{} contains Go string value, fxamacker/cbor outputs CBOR text string.
Unfortunately, there appears to be a limitation in encoding/json when decoding to interface{}, so encoding/json does this:

JSON number -> Go float64
JSON datetime -> Go string

When Go float64 and Go string are given to fxamacker/cbor, it correctly encodes them to CBOR floating-point and CBOR text string.
The best solution would be to use a JSON decoder that can decode JSON datetime strings to Go time.Time and etc. when decoding to Go interface{}.
Normally, I wouldn't suggest this but your issue is so well-written I think you might have a better shot than most of us at convincing Go team to add this as an option to the decoder in encoding/json.
@fxamacker can you take a look in case I missed anything?

@x448 Thanks a lot for the elaborate reply.
I now understand that this is not an issue with CBOR, but rather with encoding/json. I also found the Go JSON specification that states the types that it uses for conversions (which obviously don't include int and datetime.
I'll continue my quest for a JSON encoder/decoder that works like I want and might create an issue for this in the Go repo. Thanks for pointing me in the right directions!
BTW: Great job on the documentation on this library! Looks real nice!

For anyone running into this issue I thought I share my results here.
I've solved/worked around the issue by creating a function that standardises a JSON interface. Hope this helps anyone! BTW I've also got a bunch of unit tests of this code if anyone is interested just let me know and I can share those too.
package app

import (
	"math"
	"reflect"
	"regexp"
	"time"
)

// StandardiseJSONInterface standardises certain entities in a given JSON
// interface.
//
// This function is intended to be used on interfaces returned by encoding/json
// `Unmarshal` function. On this interface, this function will perform the
// standardisations listed below.
// - If a string is found that matches the specific date format described below,
//   that string is converted to `time.Time`.
//   The only supported format is `YYYY-MM-DDTHH:mm:ss.sssZ`, which is a
//   simplified ISO 8601 format. This is the specific format that the Javascript
//   `Date.prototype.toISOString()` returns.
// - If a number (float64) is found that has a fractional part of exactly zero,
//   that number is converted to an iteger (int64).
//
// The numbers that can be safely represented are numbers between -(2^53 - 1)
// and 2^53 - 1. This is because the numbers in the object are first converted
// to the Go type `float64`, which is a double-precision 64-bit binary format
// IEEE 754 value. This format can only safely represent integer numbers within
// the range described above.
func StandardiseJSONInterface(obj interface{}) interface{} {
	value := reflect.ValueOf(obj)

	switch value.Kind() {
	case reflect.Float64:
		item := value.Float()

		// It the item can be truncated and is still the same, that means that there
		// is truncated part had no significance and the item can be safely
		// represented by an integer number.
		// `9007199254740991` is the IEEE 754 largest positive double precision
		// integer number (2^53 -1).
		integer, _ := math.Modf(item)
		if math.Abs(integer) <= float64(9007199254740991) && item == integer {
			if math.Signbit(item) {
				return int64(item)
			}
			return uint64(item)
		}

	case reflect.String:
		match, _ := regexp.MatchString(
			`^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d{3}Z$`, value.String())
		if match {
			t, err := time.Parse(time.RFC3339, value.String())
			if err == nil {
				return t
			}
		}

	case reflect.Slice:
		returnSlice := make([]interface{}, value.Len())
		for i := 0; i < value.Len(); i++ {
			returnSlice[i] = StandardiseJSONInterface(value.Index(i).Interface())
		}
		return returnSlice

	case reflect.Map:
		tmpData := make(map[string]interface{})
		for _, k := range value.MapKeys() {
			tmpData[k.String()] = StandardiseJSONInterface(
				value.MapIndex(k).Interface())
		}
		return tmpData
	}

	return obj
}

@rbolkey Glad it helped and thanks for sharing your experience. To not spam this ticket too much, let's continue the conversation here: https://gist.github.com/jdbruijn/09ba26d13a603128960eb5747a60014c


I cant get ouput

What am I doing wrong.
e.g.
pid_controller:
sensor:
- platform: pid_controller
name: pid_1
enabled: '{{ states("input_boolean.pid_one_enabled") }}'
etc..
HA doesn't recognise sensor.pid_1
if I add it to a card I get Entity not available: sensor.pid_1
I think I have followed every step and followed the example but am stuck at this point.
Seems everyone can see the output so sorry for the basic question.

Try searching on the developer tools just for "pid". See if home assistant "decided" to name your entity with another name, for example adding a "_2" to the end!

Not there.  I think my problem is that if I follow your instructions exactly I end up with a "duplicate key" on sensors.  So I put the  PID stuff right at the top and had all the sensors below.  Then I tried putting all the helpers above thinking they may need to be defined before I use them.  Still no luck.  I am not experience with YAML so I am sure I am doing something silly
here is my whole configuration.yaml
Loads default set of integrations. Do not remove.
default_config:
Text to speech
tts:

platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
input_boolean:
pid_one_invert:
name: Invert
initial: no
pid_one_enabled:
name: Enabled
input_select:
pid_one_round:
initial: Round
options:
- Floor
- Ceil
- Round
input_number:
pid_one_sample_time:
name: Sample Time
initial: 0
min: 0
max: 30
step: 1
pid_one_minimum:
name: Minimum
initial: 0
min: 0
max: 5
step: 1
pid_one_maximum:
name: Maximum
initial: 50
min: 0
max: 50
step: 1
pid_one_set_point:
name: Set Point
initial: 15
min: 0
max: 30
step: 1
pid_one_proportional:
name: Proportional
initial: 0
min: 0
max: 10
step: 0.01
pid_one_integral:
name: Integral
initial: 0
min: 0
max: 10
step: 0.01
pid_one_derivative:
name: Derivative
initial: 0
min: 0
max: 10
step: 0.01
pid_one_precision:
name: Precision
initial: 2
min: 0
max: 10
step: 1
pid_one_windup:
name: Windup
initial: 0
min: 0
max: 30
step: 1
pid_one_reading:
name: Sensor Reading
initial: 0
min: -1000
max: 1000
step: 1
pid_controller:
sensor:

platform: pid_controller
name: pid_1
enabled: '{{ states("input_boolean.pid_one_enabled") }}'
set_point: '{{ states("input_number.pid_one_set_point") }}'
p: '{{ states("input_number.pid_one_proportional") }}'
i: '{{ states("input_number.pid_one_integral") }}'
d: '{{ states("input_number.pid_one_derivative") }}'
entity_id: input_number.pid_one_reading
invert: '{{ states("input_boolean.pid_one_invert") }}'
precision: '{{ states("input_number.pid_one_precision") }}'
minimum: '{{ states("input_number.pid_one_minimum") }}'
maximum: '{{ states("input_number.pid_one_maximum") }}'
round: '{{ states("input_select.pid_one_round") }}'
sample_time: '{{ states("input_number.pid_one_sample_time") }}'
windup: '{{ states("input_number.pid_one_windup") }}'

platform: template
sensors:
energy_diff:
value_template: "{{ states('sensor.grid_energy_returned') | float - states('sensor.grid_energy') | float }}"

platform: template
sensors:
house_power:
value_template: "{{ states('sensor.solar_power') | float + states('sensor.grid_power') | float }}"

platform: template
sensors:
kettle_power:
value_template: '{{ state_attr("switch.kettle_plug", "current_consumption") }}'
unit_of_measurement: W

platform: template
sensors:
pool_power:
value_template: '{{ state_attr("switch.pool_power", "current_consumption") }}'
unit_of_measurement: W

platform: template
sensors:
outside_temp_hvac:
value_template: '{{ state_attr("climate.lounge_room_ac", "outdoor_temp") }}'
unit_of_measurement: °C

The order at this point is irrelevant, if a entity already exists, normally home assistant adds a _2 to the end of the name! Did you tried adding a different name to test? Try the name New PID Controller. For example.

um, I did the core update this morning with no changes it worked - thanks for bearing with me!


Landing Page for Beauty Product Startup

Describe the project
A clear and concise description of the project you are going to add to this repository.
Issue Type:

[ ] Bug Report
[ ] Feature Request
[ ] Documentation
[x] New Project

Additional context
Add any other context or screenshots about the project here.
Screenshots

If applicable, add screenshots to help explain your problem.
My project aims to provide a starter landing page for startups focusing on beauty products.

@bhavyasingh75  @TusharKesarwani I want to work on this issue can you assign this issue to me

Hey! @TusharKesarwani , I go through your project of "landing page for beauty project startup" , I really liked your idea of the that startup and looking forward to contribute more in this project to upskill the project to another level. I will be happy if you assign that issue to me. Waiting for your kind response.

on it


Disconnect ROS & M-series code upgrades.

Changes Made:

Added DisconnectROS method in Drone and Sensor Interface
Implemented DisconnectROS method in drone and sensor scripts
Ensured all sensor scripts implement ROS Sensor interface
Implemented dictionary in ROSManager to keep track of all ROS connections
Added functionality in ROSManager to disconnect all connections on the application quit
Created base class for Matrice drones and documented it
Added functional base dynamic waypoint system (will work with @apollovision to improve as it will depend on user actions)
Removed all code from M100, M210, and M600 scripts. We will work on adding functionality specific to each drone and removing functionality not supported by drones as needed.
Removed DroneFlightSim from World game object as each drone now generates it's own.

Looks good to me. Didn't test tho. Also, you updated the scene Main.unity, was that intentional?

Yeah, I mentioned it in the changes made. Removed the drone flight sim.


The restart command does not fully restart the level (changes made remain)

Probably related with this issue.


Where do I get my mailchimp post url?

From README.md:
"
The mailchimp post url will look like this:
http://blahblah.us1.list-manage.com/subscribe/post?u=5afsdhfuhdsiufdba6f8802&id=4djhfdsh99f

"
Where do I get my mailchimp post URL?

The URL can be found on the mailchimp admin interface.
In the admin interface, first create a list. Something like, "Mycompany Newsletter". After creating a list, you will be given the option to create an embedded sign up form. The admin interface will give you some html to paste into your site. In that html you will find the url under the div #mc_embed_signup.

This should be added to the readme

You save the day!


gnome.gnome-shell-extensions can't be removed

Describe the bug
gnome.gnome-shell-extensions can't be removed
Steps To Reproduce
Steps to reproduce the behavior:

Exclude package
Rebuild
Reboot
Package still exists

Expected behavior
gnome.gnome-shell-extensions should be removed
https://github.com/NixOS/nixpkgs/blob/nixos-23.11/nixos/modules/services/x11/desktop-managers/gnome.nix#L451
https://github.com/NixOS/nixpkgs/blob/nixos-23.11/nixos/modules/services/x11/desktop-managers/gnome.nix#L381
Additional context
In situation when package can't be remove because is required by gnome-shell maybe it will be better replace gnome.gnome-shell-extensions by gnome-extension-manager in new gnome release of NixOS? As is the case with openSuSe MicroOS and Fedora Silverblue spins ( Universal Blue ).
Notify maintainers
@jtojnar
@amaxine
@dasj19
@hedning
@bobby285271
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[kamilcynk@nixos:~]$  nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.22, NixOS, 24.05 (Uakari), 24.05pre598982.b06025f1533a`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

That is part of gnome.gnome-shell itself, not gnome.gnome-shell-extensions.
It might be possible to build it separately, since it is a Meson subproject. Maybe someone can tackle that after we are done with GNOME 46.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/excluding-gnome-extensions-not-working-removing/50048/5


Environment Setup

Description
For this project, we will need to install web3py and set up an nft/sdk folder.
Definition of Done

[x] web3py is installed
[ ]nft/sdkfolder is created

So far I altered the base contract class that was there to be simpler.
I imagine that all other contract classes will inherit from the base contract class.
The base contract class so far only needs the chainId. I don't believe it's like the JavaScript version where we need the signer or wallet since we sign transactions separately.
ZapMedia was used as an example to use the BaseContract class. The parent BaseClass connects to the node and the child class can connect to contract instance using connect_to_contract inherited from the base class.
Note:

Need to check web3py if there is a wallet classes to use.
We should have a separate file that holds custom exceptions.

I also think we should isolate the Legacy Zap SDK from the NFT Zap SDk.
I propose a folder structure like this
src/
├─ legacy/
├─ nft/
│  ├─ ZapMedia/
│  ├─ Zap_or_ZapMarket/
│  ├─ MediaFactory/
│  ├─ ZapVault/
│  ├─ AuctionHouse/
├─ ZapToken/
├─ __init__.py

Since the legacy modules depend on ZapToken, we could probably place it in the root. Then both SDKs can import it.
We should also discuss whether or not we will keep the legacy SDK.

In the future, we will be using setuptools to make a wheel package that would be uploaded to pypi.
Dependencies will be defined in a setup.py file within the root of the repo, with a MANIFEST.in file to define excluded directories and includes/grafted directories.


Feature request: Add getPhoneCodeForWilaya and getPhoneCodesForWilaya

⚠⚠⚠
This issue is for first-timers only, we'd like you to start your open-source journey from here 😄
⚠⚠⚠
As a library consumer, I would like to have a method that returns phone codes for each wilaya.
One of the use cases for this feature is with forms; in order to have a better user experience, we would like to set the phone code initials when the user select their wilaya. For example: if I fill the address block and set my city to Oran (code: 31) I would like if the phone number block is set automatically to 041.
What we want to add:

A getPhoneCodeForWilaya function that takes one parameter (wilayaCode: number) and returns the first phone code (as a wilaya, like Algiers have two phone codes: 21, 23).
A getPhoneCodesForWilaya  function that takes one parameter (wilayaCode: number) and returns an array of all phoneCodes of that wilaya.

NB:

Please read our contributing guidelines and our code of conduct
Comment here so we know that you're on it 🐝 .
Clone this repository, read the code and try to understand how we structured it.
Start hacking (PS: You can check the PRs we merged and see how our smart contributors added this kind of features)
Update documentation in the readme file
Ask for help, here or in Slack.

Happy Hacking !

@Fcmam5 I will take getPhoneCodeForWilayaand getPhoneCodesForWilaya

@oussamabouchikhi please check #20 , let's keep this issue for first-timers 😄

@oussamabouchikhi please check #20 , let's keep this issue for first-timers 😄

No problem

Hi! May I contribute by taking on this issue?

I would love to have this for my first time, if you need someone to help i think i could do this

Hi! May I contribute by taking on this issue?

@joeylnguyen you got it! Happy Hacktober Hacking 🎉 !

I would love to have this for my first time, if you need someone to help i think i could do this

@xxKeefer you can take #24 😄


Release 4.0.0

The plugins folder is missing

Codecov Report
Attention: 92 lines in your changes are missing coverage. Please review.

Comparison is base (82f19c4) 80.02% compared to head (4d01255) 84.06%.

Files
Patch %
Lines

aizynthfinder/tools/make_stock.py
26.31%
26 Missing and 2 partials :warning:

aizynthfinder/context/scoring/scorers.py
89.87%
10 Missing and 6 partials :warning:

aizynthfinder/context/config.py
80.00%
9 Missing and 2 partials :warning:

aizynthfinder/context/stock/queries.py
77.27%
8 Missing and 2 partials :warning:

aizynthfinder/search/mcts/node.py
89.06%
2 Missing and 5 partials :warning:

aizynthfinder/interfaces/aizynthapp.py
50.00%
5 Missing :warning:

aizynthfinder/search/retrostar/cost.py
86.66%
4 Missing :warning:

aizynthfinder/aizynthfinder.py
84.61%
1 Missing and 1 partial :warning:

aizynthfinder/analysis/utils.py
0.00%
1 Missing :warning:

aizynthfinder/context/collection.py
50.00%
1 Missing :warning:

... and 7 more

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #141      +/-   ##
==========================================
+ Coverage   80.02%   84.06%   +4.04%
==========================================
  Files          65       56       -9
  Lines        4995     4676     -319
  Branches      828      863      +35
==========================================
- Hits         3997     3931      -66
+ Misses        807      556     -251
+ Partials      191      189       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update stable version in repo from 0.0.0 to 1.0.0

Think about adding version 1.0.0 to stable repository.
Version: stable=0.0.0 (0 days old) => latest=1.0.0 (53 days old)
Installs: stable=0 (0%), latest=2 (50%), total=4
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.0.0 but the current stable version is already 1.0.0.
So this issue should be closed.


Fix for two issues I had to get leantime working for me.

Hi Dave,
I had an issue to upgrade to the latest release for my existing install.
One issue is the non existence of defaultTimezone in the configuration file. The relevant commit adds this and extends the readme.
The other was at buildtime there is an issue with php throwing an error for missing ext-ldap. The quickest solution was to add the --ignore-platform-req=ext-ldap which was a proposed solution for the error message. I believe this is a temporary fix.
Kind regards, Arjen

Thanks for this.  Can you refactor this a bit before I accept?
TIMEZONE is being handled by the up-up-upstream image (tiredofit/alpine) which hardcodes a Timezone variable right in the Dockerfile (Default Etc/UTC) so it can be removed from the "defaults" file.
Also, I think you may be able to get away with getting LDAP to work by right before the composer install command executing this helper php-ext enable core - That will preload the LDAP extension therefore bypassing the need to skip the check introduced. This was a weird development decision I did with the PHP-FPM image that sometimes needs to be done prior to building or installing dependencies.


Added package.json and UMD loader wrapper

Hi Taufik,
I found your color-picker widget a few weeks ago and decided to use it for a few projects that I have. I neede da basic color picker and love that yours (in comparison ot many others outthere) is light in size, dependency free and not bloated with too many extra feature.  What I found to be missing (for me :) ) is a package.json, which allows folks to use package managers (ex. npm) and (most important), that it provides support for use with module patterns, so that the glboal window space is not automtically poluted with the CP namespace...
With this contribution, I am providing:

A package.json file
Changes to color-picker.js to wrap the library in an UMD declaration.

This will enable your library to be used with packge manager, as well as modern module loaders (ex. ES2015 import or AMD or CommonJS.
Thanks for your work on this and for sharing it on GitHub.
/Paul

Uhm, the issue already discussed here: https://github.com/tovic/color-picker/issues/1

Will add this next time in a duplicate file named as color-picker.umd.js or maybe you could just create a fork of my project and add the UMD support so that I can link your modified version to the README file 👍

The package.json is okay, but the UMD pattern is not. I want to keep this library written in plain JavaScript and to be functioned directly as it is. If it is for color picker, then it should function as a color picker, that’t it.
The reasons behind my statement that I will never add any UMD patterns to my projects is because there are no(t yet)? standards on importing and exporting modules in the ECMAScript specification. Yes, I know that AMD and CommonJS are very popular and widely used but they are not part of the JavaScript itself. They are just another JavaScript products, like jQuery. So adding this pattern is like adding support for the jQuery plugin.

Too much competition and choice. The solution is ES6 module syntax.

Thanks for getting back to me.
I agree that the solution is ES6 Module Pattern... When I first saw your library, I was hoping that I could just import it into my projects (most of them are now written in ES6 module pattern), but it does not seem to implement an export default statement.  Everything is just public and global, which is (IMO and experience) never a good think.
ES6 did standardize the module pattern... What is still missing is a standard around the module loaders, and thus the current need for the UMD type of wrapper...
This is no problem.. I will use my fork of you project instead and may also make other changes of issues I'm seeing (ex. your .fit() method does not seem to account for color pickers inside of absolute positioned elements or elements that have offset applied to them).
Thanks again for taking the time getting back to me...
/Paul.

There may also be a need for kind of HSLA color support because the reverse version of HSLA color converter is still buggy in the demo page.

Your .fit() method does not seem to account for color pickers inside of absolute positioned elements or elements that have offset applied to them.

Maybe I should define context before offset parameter so that we can set custom boundaries like:
$.fit(boundaries, offset);

picker.fit(picker.picker.parentNode, [4, 10]);

picker.fit(window, [4, 10]); // default

I have not looked exactly at what the issue is in side of .fit()... My currently solution: I'm using a custom "position()" method on the cpInstance.picker HTML element... I invoke it by placing a listener on the enter event.   My position funtion (I use it in several other use cases) uses a combination getBoundingClientRect() + window.body.scrollTop -- which seems to work OK, because the cpInstance.picker is always appended to window.body.
What you suggest might work.. I assume the array is offset from top, right?

Left and top (X and Y).
https://tovic.github.io/color-picker/#section:method-fit


feat: support export * without as

Fix #124.

Emm, this does not seem right. While yet is might work with toExports, most of the time, unimport is to used with injectImports (auto imports). For auto import to work, we need to know the names of the APIs to be imported at build time. Meaning importing from * won't work.

Ah, I wanted make use of it in Nuxt with auto imports, figured it was enough to export from the generated imports file in .nuxt directory. Did not know they are purposely to be named.

While yes using export * from, TypeScript can infer the exports for your IDE to show up the list, but unimport can't know that. That means it offers you a fake situation where you can see the type, but they are not actually been auto imported.

Well, that is a shame.


Unit testing

https://github.com/gulpjs/gulp/blob/master/docs/recipes/mocha-test-runner-with-gulp.md

Look at metalsmith-metadata-plugin for an example of this.


Uniform Makefiles for all programs with Usage instructions

I've updated and tested makefiles and added usage instructions to the README's of the corresponding programs,
The idea was to keep it simple and uniform while not breaking it's dependencies
It has the following 3 commands common to all the programs:

make build
make run
make clean
So as to not make it confusing and/or overwhelming for first time C++ OpenCV users

Makefiles and instrunctions for the following are yet to be added:
1_image_representation
3_interpolation
which i'll add as soon as I can

And have you remamed all code in subfolders as main.cpp? - For uniformity

It's as per the original file structure, you don't need to type the file names, so it doesn't matter anyways.

Makefiles and instrunctions for the following are yet to be added:
1_image_representation
3_interpolation
~ which i'll add as soon as I can~

Added support for all Makefiles


Alphafold exits without result, but with warning of maximum number of residues 32763 exceeded in sequence

Alphafold exists without result, but reamins lots of warnings such as below:
I0818 04:41:49.407580<PHONE_NUMBER>0816 run_docker-2.py:193] E0817 20:41:49.119690<PHONE_NUMBER>11136 hhblits.py:141] - 19:20:25.909 WARNING: maximum number of residues 32763 exceeded in sequence tr|A0A091T648|A0A091T648_PHALP Titin (Fragment) OS=Phaethon lepturus GN=N335_02550 PE=4 SV=1
Anyone knows what it is about?

I have the same problem.

Titin

This is from ChimeraX twitter? They did not use the full sequence. They cut in pieces.

Duplicate of https://github.com/deepmind/alphafold/issues/172.
TL;DR: AlphaFold can fold at most 2,700-residue proteins and the sequence you are trying to run with is 32k residues. The best workaround is to split the sequence in shorter ones and fold those, then merge.

AlphaFold can fold at most 2,700-residue proteins and the sequence you are trying to run with is 32k residues. The best workaround is to split the sequence in shorter ones

Actually what Alphafold DB does it splits into highly overlapping segments of 1400aa length overlapping fragments (residues 1–1400, residues 201–1600, etc).

I got the same problem for a complex sequence with 200 residues. Could anyone provide answers?

I got the same problem for a complex sequence with 200 residues. Could anyone provide answers?

I also got this issue on a multimer run with sequences of 200-400. I believe the issue is that Titin proteins are being found as templates/homologs b and their size is causing the issue

I have the same problem, too!

I am seeing a similar problem

Same problem


chore(vmalertmanager): remove default 200Mi request

None of the other VM objects have this behaviour and it can cause problems if the memory limit is lower than the request.
Fixes: #706

Thanks for the fix! But there is default resources for vmalertmanager that haven't be used correctly, should be fixed together in https://github.com/VictoriaMetrics/operator/pull/710. Will close this)


feat(rust): enable access to channel remote public key via channel manager

This enables a channel manager / channel to export the remote end's public key. However, I'm still not sure where in the channel manager (or elsewhere) code would be a good place to return the channel address created so that a later call can find the public key. Suggestions appreciated! (@robinbudd / @mikelodder7)

Closing in favor of different approach. Will have another small PR shortly.


Remove Protein submodule

The package has turned out quite clean with nice abstractions. The ideas from earlier versions have been distilled to an elegant set of types and functions, with some new additions.
The elephant in the room however is the Protein submodule, with plenty of arbitrary design decisions having been made. Having support for proteins in the package natively is convenient, but PDB IO basically requires us to have 2 dependencies: BioStructures for robust PDB reading, and PDBTools for easy writing.
Nevertheless, we could technically support proteins with a BioStructures extension, for example by defining a Backbone(chain::BioStructures.Chain, residue_selectors...) constructor or something, keeping the core package clean.
Alternatively, there could be a whole other package for protein stuff.

If it's any use here, you can use AtomRecord to write from BioStructures without having to construct the whole object:
julia> pdbline(AtomRecord(false, 669, "CA", ' ', "ILE", "A", 90, ' ', [31.743, 33.11, 31.221], 1.00, 25.76, "C", ""))
"ATOM    669  CA  ILE A  90      31.743  33.110  31.221  1.00 25.76           C  "

See more at https://biojulia.dev/BioStructures.jl/stable/documentation/#Writing-PDB-files.
I'd like to fix any usability issues you have with BioStructures though so let me know if that isn't sufficient.


prettier: Support experimental languages (Handlebars)

In case the filetype has an exprimental support in Prettier, the --parser flag has to be set manually.
I'm not 100% sure if it's relevant or not to tie ale to an experimental flag in Prettier. But the patch is done, so I leave it to your judgement @w0rp 🙂.
For the time being, I'm using this workaround: https://github.com/w0rp/ale/issues/2247#issuecomment-457660222
Would close https://github.com/w0rp/ale/issues/2247

Actually, that doesn't work. Because of the compound filetype and html being matched first, it selected the wrong parser. In that case, just use the first filetype check to set l:parser to 'glimmer', and check !exists('l:parser').

And what do you say of switching html and handlebars lines in l:prettier_parsers definition (with a comment)? I liked your solution being so light.

And what do you say of switching html and handlebars lines in l:prettier_parsers definition (with a comment)? I liked your solution being so light.

This doesn't work. Your suggestion is implemented.

That's much better. Cheers! :beers:


Create landing page for all content using individual user accounts

VS can fwlink to the landing page.
see #3788

@danroth27  @sayedihashimi  would https://docs.microsoft.com/en-us/aspnet/core/security/#aspnet-security-documentation work? Do we need a dedicated page? I could add an H2 to that page - something like
Tutorials that use ASP.NET Core templates and user authentication

first
second, etc.


For android stripe is not working with new architecture enabled.

Describe the bug
I'm using CardField imported from react-native. Any of there is not triggering onCardChange, onFocus, onBlur. Please note when I'm setting newArchEnabled=false in my project then it it working but I wanna go with newArchEnabled=true it's compulsory.
Expected behavior
All events should work with newArchEnabled=true
Smartphone:

Device: [Samsung s24 ultra]
OS: [13]

Can I ask you to try what happens when a 3ds secure screen appears with RN 0.76?
In my case (new architecture enabled or not, no difference), I got the app freezed on iOS.

Same here, my app is crashing on iOS with newArch enabled.
I am using latest expo version 52.0.11 and stripe latest version 0.40.0
Please take a look at below screenshot, app is crashing onBlur function


Update docker-compose.yaml

Please remove these it is exposing docker's credentials

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


Avoid spurious inserted rules warning.

Description

Related issues/PRs

Fixes #9380.
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

Fix spurious warning about unexpected inserted rules.

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

/merge-when-ready

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and leave the branch after I've merged it.


Whether it could be implemented using images from surveillance camera?

Does anybody know if this method could be used in vehicle 3D detection in residential scenes?
In that case, The images are from surveillance cameras. And those cameras are set at about 3-4 meters high from the ground.
Thus, the Roll angle of cameras are definitely not 0.
If I directly use the the pretrained model and original camera calibration files, the predictions are reaaaaally bad in my scenes.
So how could I change the camera calibration files to make it adaptable for image datasets by surveillance cameras?
Or it's not capable to do that?

请问你解决了吗？


Incorrect fonts used in engineeringresumes theme

#100

Could you please elaborate? I don’t understand what you mean by incorrect fonts.

Sorry, I'm not quite following up on what this issue is about. Also, it doesn't seem like a bug to me, more like an enhancement request.
You need to clarify what you want precisely and explain the reasons behind it. The reasons are very important because that's how we will decide whether to do these things.
I see you want two things:

Remove available fonts from engineeringresumes theme.
Add a new font, xcharter.

Can you explain the reasons for each of these points?


Layer panel font sizes don't align

Bug Description
The different types of layers in the layer panel have different font sizes:

They should have a similar font size as can be seen in Figma:

Expected Behaviour
Font sizes are expected to be similar according to Figma.
Steps to Reproduce

Add a text layer and observe a different font size from the background layer.

Screenshots

Additional Context

Plugin Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Verified in QA


NATIVE-155 Put content and resource-cache directories in a version dir

NATIVE-155 Put content and resource-cache directories in a version dir

Hm seems like builds are hanging. Easiest would be to do a push by rewriting the history for example.
Also feel free to create branches in the react-native repo :)

Closing this and open a new one in origin repo


Add watervisibility QA to the system

how to simulate watervisibility?
implement watervisibility observer

period = 2pi/B
water_visibility = Amplitude * sin(Bx) + min_water_visibility

Should x be a position or time?

t = current_time - self.initial_time
        v_delta = water_visibility_amp + water_visibility_min
        water_visibility = water_visibility_amp * math.cos(
            (2*math.pi/water_visibility_period)*t) + v_delta


Ionic4.alpha.2: Breaking change, missing Document.resume and Document.pause

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[ ] 3.x
[x] 4.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
Current behavior:
At the moment it seems, pause and resume are not implemented on angular's Platform. https://github.com/ionic-team/ionic/blob/2b3c14b608d1fb6c41b469e7ed3f001f40d62d5a/angular/src/providers/platform.ts
Expected behavior:
I think having a look to the v2/v3. docs https://ionicframework.com/docs/api/platform/Platform/ and at the sourcecode of v4 there are also other functions which probably at the moment are not implemented.
I think some of this features, like the pause and resume for us are very important.
Not sure if this breaking changes is an accident or wanted. I hope the first one. :)

fixed https://github.com/ionic-team/ionic/commit/c929dad2e930b809feda07ffbb4c4c2a0ef59335


chore(master): release 3.0.4

:robot: I have created a release beep boop
3.0.4 (2024-01-19)
Bug Fixes

deps: bump the production-dependencies group with 4 updates (#135) (0a2dfe5)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ccntrq/git-create-jira-branch/releases/tag/v3.0.4 :sunflower:


Create update-setting-parentUniqueId.sh to re populate parentUniqueId with correct values

We are encountering an issue where the User Settings migration process is incorrectly identifying values for Account Settings, resulting in incorrect data population for existing settings. To address this, we need to:

Remove the unique indexes associated with both fields.
Clear the prefilled data to correct the inaccuracies.
Reset the migration flag to enable a re-run of the migration with the correct parameters.
Restart the NG Manager to execute the updated migration.

This process will ensure that the migration runs accurately and populates the settings correctly.
This need to be done for folk who updated to any of the following versions of SMP:
0.17.0 0.17.1 0.17.2 0.18.0 0.18.1
If they are upgrading to 0.17.3 and 0.18.2 directly from 0.16.x or any lower version this would not be needed

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


Add css styles to the digest.ftl

The appropriate css styles should be added to the digest.ftl

Resolved in 2bf287f


Encountered a Dart Analysis Server error - Android Studio

Analyzer Feedback from IntelliJ
Encountered a Dart Analysis Server error.

There is no error attached to this issue.

How did you solve it? I have the same question?


Missing package

Just letting you guys know that github.com/ahmedaabouzied/blockscore-go in your go.mod is no longer available.

@dmint007 I made a PR with a fix and a workaround


Add alternate table view

Add table view as alternate display for schedule list with sorting options

Completed in v1.1.8


feat: support object progress

Fix #14, below is the source code of bullmq:
https://github.com/taskforcesh/bullmq/blob/cf0710cfe322eb2147f439364b425763b4d5c592/src/classes/job.ts#L246

https://github.com/taskforcesh/bullmq/blob/cf0710cfe322eb2147f439364b425763b4d5c592/src/classes/scripts.ts#L231

I'm not sure is it ok to just change 'progress' from Int to JSON, but it works for me in both cases:

i don't understand how this is suppose to work, when there is no changes inside this method

I'm using the bull-monitor cli, where bull-adapter is used.
I can only see bullmq-adapter is only referenced in fixtures/bull-server/server.

take a look at the readme. bull (or bullmq) adapter is required in order to make bull-monitor work, since we support both bull and bullmq.

btw now i understand why you are getting that weird gql error - our cli works fine only with bull(not bullmq)

yes, I'm using the cli, can we support it? maybe some option is needed?

definitely possible, i guess we can add some flag like "bullmq" to the cli and wrap queues with the appropriate adapter


Path normalization breaks classpath-relative paths with a custom ResourceAccessor

Search first

[X] I searched and no similar issues were found

Description
I am trying again to upgrade Bootique.io framework to Liquibase 4.x from 3.x. An earlier issue #3105 was fixed in LB 4.17, and helped us to move forward. However, there are still a few places where the base path of a resource is altered, so the relative resources can not be properly resolved inside a custom ResourceAccessor. The culprit is stripping the classpath: prefix during path normalization. So this change to DatabaseChangeLog.normalizePath(..) fixes everything for me:
--- a/liquibase-standard/src/main/java/liquibase/changelog/DatabaseChangeLog.java
+++ b/liquibase-standard/src/main/java/liquibase/changelog/DatabaseChangeLog.java
@@ -1028,10 +1028,6 @@ public class DatabaseChangeLog implements Comparable<DatabaseChangeLog>, Conditi
             return null;
         }

-        if (filePath.startsWith("classpath:")) {
-            filePath = filePath.substring("classpath:".length());
-        }
-
         if (filePath.contains("\\")) {
             filePath = filePath.replace("\\", "/");
         }

But I suspect such a change may break things elsewhere, so not sending a PR just yet 😀 Instead, let me point to some of the call spots for normalizePath(..) that resulted in broken relative resources, and maybe someone can suggest a proper solution, such as an alternative normalize method that preserves the "protocol" prefix in paths:

https://github.com/liquibase/liquibase/blob/d956d5f9d9377e9d4205a82238a247a2965b4e21/liquibase-standard/src/main/java/liquibase/parser/core/yaml/YamlChangeLogParser.java#L46
https://github.com/liquibase/liquibase/blob/d956d5f9d9377e9d4205a82238a247a2965b4e21/liquibase-standard/src/main/java/liquibase/parser/core/xml/AbstractChangeLogParser.java#L20
https://github.com/liquibase/liquibase/blob/d956d5f9d9377e9d4205a82238a247a2965b4e21/liquibase-standard/src/main/java/liquibase/changelog/DatabaseChangeLog.java#L969

Steps To Reproduce
This test on branch 123 fails: https://github.com/bootique/bootique-jdbc/blob/123/bootique-jdbc-junit5-derby/src/test/java/io/bootique/jdbc/junit5/derby/DerbyTester_Liquibase_RelativeIT.java
git clone git@github.com:bootique/bootique-jdbc.git
cd bootique-jdbc
git checkout -b 123 origin/123
mvn clean verify

Caused by: liquibase.exception.LiquibaseException: Error parsing classpath:io/bootique/jdbc/junit5/derby/DerbyTester_Liquibase_RelativeIT-changelog.yml : java.io.FileNotFoundException: /Users/andrus/work/bootique/bootique-jdbc/bootique-jdbc-junit5-derby/io/bootique/jdbc/junit5/derby/changelogs/changelog.sql (No such file or directory)
at liquibase.changelog.DatabaseChangeLog.include(DatabaseChangeLog.java:987)
at liquibase.changelog.DatabaseChangeLog.include(DatabaseChangeLog.java:907)
at io.bootique.jdbc.liquibase.LiquibaseRunner.lambda$createDatabaseChangeLog$0(LiquibaseRunner.java:108)
... 17 more
Caused by: liquibase.exception.ChangeLogParseException: Error parsing classpath:io/bootique/jdbc/junit5/derby/DerbyTester_Liquibase_RelativeIT-changelog.yml : java.io.FileNotFoundException: /Users/andrus/work/bootique/bootique-jdbc/bootique-jdbc-junit5-derby/io/bootique/jdbc/junit5/derby/changelogs/changelog.sql (No such file or directory)
at liquibase.parser.core.yaml.YamlChangeLogParser.parse(YamlChangeLogParser.java:96)
at liquibase.changelog.DatabaseChangeLog.lambda$include$4(DatabaseChangeLog.java:957)
at liquibase.Scope.child(Scope.java:199)
at liquibase.Scope.child(Scope.java:175)
at liquibase.changelog.DatabaseChangeLog.include(DatabaseChangeLog.java:956)
... 19 more
Caused by: liquibase.exception.SetupException: java.io.FileNotFoundException: /Users/andrus/work/bootique/bootique-jdbc/bootique-jdbc-junit5-derby/io/bootique/jdbc/junit5/derby/changelogs/changelog.sql (No such file or directory)
at liquibase.changelog.DatabaseChangeLog.handleChildNode(DatabaseChangeLog.java:465)
at liquibase.changelog.DatabaseChangeLog.load(DatabaseChangeLog.java:390)
at liquibase.parser.core.yaml.YamlChangeLogParser.parse(YamlChangeLogParser.java:90)
... 23 more
Caused by: liquibase.exception.LiquibaseException: java.io.FileNotFoundException: /Users/andrus/work/bootique/bootique-jdbc/bootique-jdbc-junit5-derby/io/bootique/jdbc/junit5/derby/changelogs/changelog.sql (No such file or directory)
at liquibase.changelog.DatabaseChangeLog.include(DatabaseChangeLog.java:987)
at liquibase.changelog.DatabaseChangeLog.handleChildNode(DatabaseChangeLog.java:455)
... 25 more
Caused by: liquibase.exception.ChangeLogParseException: java.io.FileNotFoundException: /Users/andrus/work/bootique/bootique-jdbc/bootique-jdbc-junit5-derby/io/bootique/jdbc/junit5/derby/changelogs/changelog.sql (No such file or directory)
at liquibase.parser.core.sql.SqlChangeLogParser.parse(SqlChangeLogParser.java:54)
at liquibase.changelog.DatabaseChangeLog.include(DatabaseChangeLog.java:959)
... 26 more

Expected/Desired Behavior
The framework code setting DatabaseChangeLog.physicalFilePath (either via constructor or setter) should not strip an optional "protocol" (such as classpath:) from the path. This will allow to apply the same protocol to relative child resources.
Liquibase Version
4.27.0
Database Vendor & Version
No response
Liquibase Integration
Bootique.io
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
No response
Additional Context
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR (Thank you!)

Hi @andrus, thank you for reporting this issue.
This is a complex topic, as some users need the classpath: to be stripped when normalizing the path, and others need it to not be stripped.

But I suspect such a change may break things elsewhere, so not sending a PR just yet 😀
I'd recommend the opposite, considering that you have a possible solution - if you submit a PR we can test it and see what/if it breaks. Our development team is always available to provide guidance or discuss changes if needed.

Please consider submitting a PR, and let me know if you have any questions.
Thank you!
Tatiana


No kinematics plugins defined

Description
Hello everyone
I'm currently trying to plan a path for a pose using the hello moveit tutorial. Unfortunately, it always happens that no kinematic plugins are defined and the path planning stops.
I saw an issue about this and tried to fix it that way. However, it doesn't help if I call the node and call the kinematics.yaml in the parameters
This is the example how I tried to fixed it.
https://github.com/ros-planning/moveit2_tutorials/blob/main/doc/examples/move_group_interface/launch/move_group_interface_tutorial.launch.py
Your environment

ROS Distro: [Humble
OS Version: Ubuntu 22.04
Binary build
If binary, which release version?

Steps to reproduce
I went through the setup assistant step by step and configured my URDF. Afterwards I adapted my demo launch which is as follows:
from launch import LaunchDescription
from launch_ros.actions import Node
from moveit_configs_utils import MoveItConfigsBuilder
from moveit_configs_utils.launches import generate_demo_launch
from launch.substitutions import PathJoinSubstitution
from launch_ros.substitutions import FindPackageShare
def generate_launch_description():
# ... (Dein bisheriger Code bleibt unverändert)
moveit_config = (MoveItConfigsBuilder("threedof_manipulator", package_name="moveit_endeffektor")
    .robot_description(file_path="config/threedof_manipulator.urdf.xacro")
    .robot_description_semantic(file_path="config/threedof_manipulator.srdf")
   # .robot_description_kinematics(file_path="config/kinematics.yaml")
    .planning_pipelines(
            pipelines=["ompl", "pilz_industrial_motion_planner", "chomp"],
            default_planning_pipeline="ompl",
        )
    .to_moveit_configs()
)

# Node für move_group_interface_tutorial
move_group_demo = Node(
    name="hello_moveit",
    package="path_planner",
    executable="DummyNode",
    output="screen",
    parameters=[
        moveit_config.robot_description_kinematics,
    ],
)

# Füge die Nodes zur Launch-Beschreibung hinzu
return LaunchDescription([generate_demo_launch(moveit_config), move_group_demo])

Expected behaviour
I want to send a Pose to my Moveit which will then plan a path for the joints
Backtrace or Console output
For the Node:
[DummyNode-8] [WARN] [1699986750.922330646] [moveit_ros.robot_model_loader]: No kinematics plugins defined. Fill and load kinematics.yaml!
[DummyNode-8] [INFO] [1699986779.258699667] [move_group_interface]: Ready to take commands for planning group Arm.
[DummyNode-8] [INFO] [1699986779.258779256] [move_group_interface]: MoveGroup action client/server ready
[move_group-3] [INFO] [1699986779.259937407] [moveit_move_group_default_capabilities.move_action_capability]: Received request
[DummyNode-8] [INFO] [1699986779.260274815] [move_group_interface]: Planning request accepted
[move_group-3] [INFO] [1699986779.260282412] [moveit_move_group_default_capabilities.move_action_capability]: executing..
[move_group-3] [INFO] [1699986779.266656808] [moveit_move_group_default_capabilities.move_action_capability]: Planning request received for MoveGroup action. Forwarding to planning pipeline.
[move_group-3] [INFO] [1699986779.267405156] [moveit.ompl_planning.model_based_planning_context]: Planner configuration 'Arm[RRTstarkConfigDefault]' will use planner 'geometric::RRTstar'. Additional configuration parameters will be set when the planner is constructed.
[rviz2-4] [INFO] [1699986779.310657015] [move_group_interface]: Ready to take commands for planning group Arm.
[move_group-3] [WARN] [1699986784.267838919] [ompl]: ./src/ompl/tools/multiplan/src/ParallelPlan.cpp:138 - ParallelPlan::solve(): Unable to find solution by any of the threads in 5.000193 seconds
[move_group-3] [INFO] [1699986784.358803715] [moveit.ompl_planning.model_based_planning_context]: Unable to solve the planning problem
[move_group-3] [INFO] [1699986784.358861872] [moveit_move_group_default_capabilities.move_action_capability]: Catastrophic failure
[DummyNode-8] [INFO] [1699986784.360475603] [move_group_interface]: Planning request aborted
[rviz2-4] [INFO] [1699986784.361429888] [moveit_ros_visualization.motion_planning_frame]: group Arm
[DummyNode-8] [ERROR] [1699986784.362546859] [move_group_interface]: MoveGroupInterface::plan() failed or timeout reached
[DummyNode-8] [ERROR] [1699986784.363325268] [hello_moveit]: Planning failed!
[INFO] [DummyNode-8]: process has finished cleanly [pid 74971]

Looks like your using a custom robot threedof_manipulator. You'll need to create a valid config package e.g. with the MoveIt Setup Assistant  and define the kinematics plugins and groups e.g. like here. Feel free to re-open this is issue if you run into any problems


Compilation Mistake

Hello I have a problem with the compilation I have double check that the dependence is installed, I am running Linux Debian 11  5.10.0-8-amd64
./autogen.sh && ./configure && make && make test && make install autoreconf: Entering directory .'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:35: installing './compile'
configure.ac:28: installing './missing'
examples/decoding/Makefile.am: installing './depcomp'
autoreconf: Leaving directory `.'
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C preprocessor... gcc -E
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for gawk... (cached) gawk
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for main in -lprotobuf... yes
checking for main in -lprotoc... yes
checking for protoc... protoc
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for check >= 0.9.10... no
configure: WARNING: check not found; cannot build tests
checking for lcov... lcov
checking for genhtml... genhtml
checking for valgrind... valgrind
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for ANSI C header files... (cached) yes
checking whether time.h and sys/time.h may both be included... yes
checking float.h usability... yes
checking float.h presence... yes
checking for float.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdint.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for inline... inline
checking for size_t... yes
checking for int32_t... yes
checking for int64_t... yes
checking for uint8_t... yes
checking for uint32_t... yes
checking for uint64_t... yes
checking for ptrdiff_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible realloc... yes
checking for working strtod... yes
checking for localeconv... yes
checking for memmove... yes
checking for setlocale... yes
checking for strchr... yes
checking for strpbrk... yes
checking for strtol... yes
checking for strtoul... yes
checking for strtoull... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating examples/decoding/Makefile
config.status: creating examples/encoding/Makefile
config.status: creating examples/messages/Makefile
config.status: creating examples/Makefile
config.status: creating include/Makefile
config.status: creating src/core/Makefile
config.status: creating src/generator/Makefile
config.status: creating src/message/Makefile
config.status: creating src/util/Makefile
config.status: creating src/Makefile
config.status: creating src/protobluff-lite.pc
config.status: creating src/protobluff.pc
config.status: creating tests/core/buffer/Makefile
config.status: creating tests/core/decoder/Makefile
config.status: creating tests/core/descriptor/Makefile
config.status: creating tests/core/encoder/Makefile
config.status: creating tests/core/stream/Makefile
config.status: creating tests/core/varint/Makefile
config.status: creating tests/core/Makefile
config.status: creating tests/message/buffer/Makefile
config.status: creating tests/message/cursor/Makefile
config.status: creating tests/message/field/Makefile
config.status: creating tests/message/journal/Makefile
config.status: creating tests/message/message/Makefile
config.status: creating tests/message/nested/Makefile
config.status: creating tests/message/oneof/Makefile
config.status: creating tests/message/part/Makefile
config.status: creating tests/message/Makefile
config.status: creating tests/util/chunk_allocator/Makefile
config.status: creating tests/util/descriptor/Makefile
config.status: creating tests/util/validator/Makefile
config.status: creating tests/util/Makefile
config.status: creating tests/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
protobluff 1.1.1
CC:                     gcc
CFLAGS:                  -std=c99 -O3 -DNDEBUG -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -fno-stack-protector -fomit-frame-pointer
CXX:                    g++
CXXFLAGS:                -std=c++11 -O3 -DNDEBUG -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -fno-stack-protector -fomit-frame-pointer
CPPFLAGS:                -Wall -Wno-deprecated-declarations -Wno-address
LDFLAGS:

prefix:                 /usr/local
sysconfdir:             ${prefix}/etc
libdir:                 ${exec_prefix}/lib
includedir:             ${prefix}/include

make  all-recursive
make[1]: Entering directory '/home/borbon/Repositories/protobluff'
Making all in include
make[2]: Entering directory '/home/borbon/Repositories/protobluff/include'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/borbon/Repositories/protobluff/include'
Making all in src
make[2]: Entering directory '/home/borbon/Repositories/protobluff/src'
Making all in core
make[3]: Entering directory '/home/borbon/Repositories/protobluff/src/core'
CC       libprotobluff_core_la-allocator.lo
CC       libprotobluff_core_la-buffer.lo
CC       libprotobluff_core_la-decoder.lo
CC       libprotobluff_core_la-descriptor.lo
CC       libprotobluff_core_la-encoder.lo
CC       libprotobluff_core_la-stream.lo
CC       libprotobluff_core_la-varint.lo
CCLD     libprotobluff-core.la
make[3]: Leaving directory '/home/borbon/Repositories/protobluff/src/core'
Making all in message
make[3]: Entering directory '/home/borbon/Repositories/protobluff/src/message'
CC       libprotobluff_message_la-buffer.lo
CC       libprotobluff_message_la-common.lo
CC       libprotobluff_message_la-cursor.lo
CC       libprotobluff_message_la-field.lo
CC       libprotobluff_message_la-journal.lo
CC       libprotobluff_message_la-message.lo
CC       libprotobluff_message_la-nested.lo
CC       libprotobluff_message_la-oneof.lo
CC       libprotobluff_message_la-part.lo
CCLD     libprotobluff-message.la
make[3]: Leaving directory '/home/borbon/Repositories/protobluff/src/message'
Making all in util
make[3]: Entering directory '/home/borbon/Repositories/protobluff/src/util'
CC       libprotobluff_util_la-chunk_allocator.lo
CC       libprotobluff_util_la-descriptor.lo
CC       libprotobluff_util_la-validator.lo
CCLD     libprotobluff-util.la
make[3]: Leaving directory '/home/borbon/Repositories/protobluff/src/util'
Making all in generator
make[3]: Entering directory '/home/borbon/Repositories/protobluff/src/generator'
CXX      protoc_gen_protobluff-enum.o
CXX      protoc_gen_protobluff-enum_value.o
CXX      protoc_gen_protobluff-extension.o
CXX      protoc_gen_protobluff-field.o
CXX      protoc_gen_protobluff-file.o
CXX      protoc_gen_protobluff-generator.o
CXX      protoc_gen_protobluff-message.o
CXX      protoc_gen_protobluff-oneof.o
CXX      protoc_gen_protobluff-protoc-gen-protobluff.o
CXX      protoc_gen_protobluff-strutil.o
CXXLD    protoc-gen-protobluff
make[3]: Leaving directory '/home/borbon/Repositories/protobluff/src/generator'
make[3]: Entering directory '/home/borbon/Repositories/protobluff/src'
CCLD     libprotobluff-lite.la
CCLD     libprotobluff.la
make[3]: Leaving directory '/home/borbon/Repositories/protobluff/src'
make[2]: Leaving directory '/home/borbon/Repositories/protobluff/src'
Making all in tests
make[2]: Entering directory '/home/borbon/Repositories/protobluff/tests'
Making all in core
make[3]: Entering directory '/home/borbon/Repositories/protobluff/tests/core'
Making all in buffer
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/core/buffer'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/core/buffer'
Making all in decoder
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/core/decoder'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/core/decoder'
Making all in descriptor
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/core/descriptor'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/core/descriptor'
Making all in encoder
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/core/encoder'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/core/encoder'
Making all in stream
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/core/stream'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/core/stream'
Making all in varint
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/core/varint'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/core/varint'
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/core'
make[4]: Nothing to be done for 'all-am'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/core'
make[3]: Leaving directory '/home/borbon/Repositories/protobluff/tests/core'
Making all in message
make[3]: Entering directory '/home/borbon/Repositories/protobluff/tests/message'
Making all in buffer
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/message/buffer'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/message/buffer'
Making all in cursor
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/message/cursor'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/message/cursor'
Making all in field
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/message/field'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/message/field'
Making all in journal
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/message/journal'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/message/journal'
Making all in message
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/message/message'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/message/message'
Making all in nested
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/message/nested'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/message/nested'
Making all in oneof
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/message/oneof'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/message/oneof'
Making all in part
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/message/part'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/message/part'
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/message'
make[4]: Nothing to be done for 'all-am'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/message'
make[3]: Leaving directory '/home/borbon/Repositories/protobluff/tests/message'
Making all in util
make[3]: Entering directory '/home/borbon/Repositories/protobluff/tests/util'
Making all in chunk_allocator
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/util/chunk_allocator'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/util/chunk_allocator'
Making all in descriptor
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/util/descriptor'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/util/descriptor'
Making all in validator
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/util/validator'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/util/validator'
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/util'
make[4]: Nothing to be done for 'all-am'.
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/util'
make[3]: Leaving directory '/home/borbon/Repositories/protobluff/tests/util'
make[3]: Entering directory '/home/borbon/Repositories/protobluff/tests'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/home/borbon/Repositories/protobluff/tests'
make[2]: Leaving directory '/home/borbon/Repositories/protobluff/tests'
make[2]: Entering directory '/home/borbon/Repositories/protobluff'
make[2]: Leaving directory '/home/borbon/Repositories/protobluff'
make[1]: Leaving directory '/home/borbon/Repositories/protobluff'
Making check in include
make[1]: Entering directory '/home/borbon/Repositories/protobluff/include'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/home/borbon/Repositories/protobluff/include'
Making check in src
make[1]: Entering directory '/home/borbon/Repositories/protobluff/src'
Making check in core
make[2]: Entering directory '/home/borbon/Repositories/protobluff/src/core'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/home/borbon/Repositories/protobluff/src/core'
Making check in message
make[2]: Entering directory '/home/borbon/Repositories/protobluff/src/message'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/home/borbon/Repositories/protobluff/src/message'
Making check in util
make[2]: Entering directory '/home/borbon/Repositories/protobluff/src/util'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/home/borbon/Repositories/protobluff/src/util'
Making check in generator
make[2]: Entering directory '/home/borbon/Repositories/protobluff/src/generator'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/home/borbon/Repositories/protobluff/src/generator'
make[2]: Entering directory '/home/borbon/Repositories/protobluff/src'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/home/borbon/Repositories/protobluff/src'
make[1]: Leaving directory '/home/borbon/Repositories/protobluff/src'
Making check in tests
make[1]: Entering directory '/home/borbon/Repositories/protobluff/tests'
Making check in core
make[2]: Entering directory '/home/borbon/Repositories/protobluff/tests/core'
Making check in buffer
make[3]: Entering directory '/home/borbon/Repositories/protobluff/tests/core/buffer'
make  test
make[4]: Entering directory '/home/borbon/Repositories/protobluff/tests/core/buffer'
CC       test-test.o
test.c:24:10: fatal error: check.h: No such file or directory
24 | #include <check.h>
|          ^~~~~~~~~
compilation terminated.
make[4]: *** [Makefile:441: test-test.o] Error 1
make[4]: Leaving directory '/home/borbon/Repositories/protobluff/tests/core/buffer'
make[3]: *** [Makefile:546: check-am] Error 2
make[3]: Leaving directory '/home/borbon/Repositories/protobluff/tests/core/buffer'
make[2]: *** [Makefile:393: check-recursive] Error 1
make[2]: Leaving directory '/home/borbon/Repositories/protobluff/tests/core'
make[1]: *** [Makefile:614: check-recursive] Error 1
make[1]: Leaving directory '/home/borbon/Repositories/protobluff/tests'
make: *** [Makefile:502: check-recursive] Error 1
`

Thanks for reporting. The warning is pretty explanatory:
...
configure: WARNING: check not found; cannot build tests
...

You need to install check.


'Session.Event' initializer is inaccessible due to 'internal' protection level

Client: Swift
Version 1.3.0

using cocoa pods and trying to create Session.Event instance, but got this error.
same as Session and Session.Proposal, but these two types do not needs to create manually. so it's fine ~

Session.Event has no public initialiser

@llbartekll
I want to emit an event to a dApp with this function in SignClient:
    /// For the wallet to emit an event to a dApp
    ///
    /// When a client wants to emit an event to its peer client (eg. chain changed or tx replaced)
    ///
    /// Should Error:
    /// - When the session topic is not found
    /// - When the event params are invalid
    /// - Parameters:
    ///   - topic: Session topic
    ///   - event: session event
    ///   - chainId: CAIP-2 chain
    public func emit(topic: String, event: Session.Event, chainId: Blockchain) async throws {
        try await sessionEngine.emit(topic: topic, event: event.internalRepresentation(), chainId: chainId)
    }

but don't know how to create the Event instance.
the dapp's supported Events is in the ProposalNamespace, but is in string format. how do I create or get the Session.Event?
public struct ProposalNamespace: Equatable, Codable {

   public let chains: Set<Blockchain>?
   public let methods: Set<String>
   public let events: Set<String>

   public init(chains: Set<Blockchain>? = nil, methods: Set<String>, events: Set<String>) {
       self.chains = chains
       self.methods = methods
       self.events = events
   }
}

hey @Crypto-Doby
please upgrade the sdk to the lates version
and take a look at this test:
https://github.com/WalletConnect/WalletConnectSwiftV2/blob/2886a39933535969b3abb190729946057fecfd34/Example/IntegrationTests/Sign/SignClientTests.swift#L350

thanks ~ I will go and take a look ~


[WIP] get: try to remove destination directory before renaming download

If the package.json file is missing from an installed package (not very likely) fetch will fail while trying to rename to an existing directory.
rm ~/go/src/gx/ipfs/QmdbxjQWogRCHRaxhhGnYdT1oQJzL9GdqSKzCdqWr85AP2/pubsub/package.json
gx install
# ERROR: [97 / 97 ] parallel fetch: failed to fetch package: QmdbxjQWogRCHRaxhhGnYdT1oQJzL9GdqSKzCdqWr85AP2: rename go/src/gx/ipfs/QmdbxjQWogRCHRaxhhGnYdT1oQJzL9GdqSKzCdqWr85AP2.part go/src/gx/ipfs/QmdbxjQWogRCHRaxhhGnYdT1oQJzL9GdqSKzCdqWr85AP2: file exists
# ERROR: install deps: failed to fetch dependencies

Should a test be added?

@schomatis
I created a similar patch to this https://github.com/whyrusleeping/gx/pull/163
It moves the check up so it only tries to remove when proven to exist and also removes an uneeded dependency.
Sorry for the overlap, I came across this independently myself and got frustrated with an ambiguous "Access is denied" error. I didn't see this pull when I started.
I can instigating failure by doing this inside of the go-ipfs repo
gx install --local git clean -fdx gx install --local
git clean -fdx was not removing any packages with tests in them which caused the problem when trying to move the temporary to the target.

@schomatis sorry I didnt see this one either. I'm merging @djdv's PR as both of these fixes work, but he points out that go's os package now properly does the rename, we no longer need the gorename package.
thank you for the PR!

@djdv No problem, I'm closing this PR as I like your solution more, it employs the standard library and handles the existence of the destination in a logically coherent place: next to the original check of FindPackageInDir, even if the Shell().Get() fails (for other reasons) it makes sense that the destination should be removed early in the function.

Oh, @whyrusleeping already took care of it :)


 in .net core 2.1

I am converting my app from .net framework to .net core 2.1. Now I am facing two issues

In .net framework we could use HttpClientCertificate cert = Request.ClientCertificate;` So how can we use Request.ClientCertificate in .net core.

In .net framework we could set location config like

<location path="MyPath">     <system.webServer>       <security>         <access sslFlags="Ssl.SslRequireCert,SslNegotiateCert,Ssl128" />       </security>     </system.webServer>   </location>
I want to use <access sslFlags="Ssl.SslRequireCert,SslNegotiateCert,Ssl128" /> in net core. How can I do these 2 things. Any help?

This issue was moved to dotnet/corefx#31560


Refactor forest custom libp2p metrics to use libp2p-metrics

Summary of changes
Changes introduced in this pull request:
Reference issue to close (if applicable)

Closes #2255
Other information and links

When I create the issue, I was thinking about migrating how original libp2p metrics are recorded in process_gossipsub_event. Sry for forgetting abt including those detail, @tyshko5 could you also evaluate if this is feasible?
let (tipset, source) = match event {
            NetworkEvent::HelloRequestInbound { .. } => {
                metrics::LIBP2P_MESSAGE_TOTAL
                    .with_label_values(&[metrics::values::HELLO_REQUEST_INBOUND])
                    .inc();
                return Ok(None);
            }
            NetworkEvent::HelloResponseOutbound { request, source } => {
                metrics::LIBP2P_MESSAGE_TOTAL
                    .with_label_values(&[metrics::values::HELLO_RESPONSE_OUTBOUND])
                    .inc();
                let tipset_keys = TipsetKeys::new(request.heaviest_tip_set);
                let tipset = match Self::get_full_tipset(
                    network.clone(),
                    chain_store.clone(),
                    source,
                    tipset_keys,
                )
                .await
                {
                    Ok(tipset) => tipset,
                    Err(why) => {
                        debug!("Querying full tipset failed: {}", why);
                        return Err(why);
                    }
                };
                (tipset, source)
            }


Force single case mapping by default

Always use single case mapping, so dynamically use the right constant

https://unicode.org/faq/casemap_charprop.html#11

Single Case-Mapping will not be forced. This issue will solve #39 instead.

https://github.com/Wisdom/Awesome-Unicode


control-service: Add support for vdk version

Currently, the vdk image used when a data job is deployed, is decided based on the python version. This is done in order to avoid possible incompatibility issues between the vdk image and the job base image. However, it also blocks the possibility to use testing vdk images in CI/CD acceptance tests.
This change adds functionality that allows a client to pass a specific vdk image to be used for a data job deployment. This would allow for CI/CD tests to test specific vdk images before they are released.
Testing Done: Unit and Integration tests

Please standardize the name to either vdkVersion or vdkImage.

We still have both vdkVersion and vdkImage. I suggest renaming all variables to vdkImage, including the API.

We still have both vdkVersion and vdkImage. I suggest renaming all variables to vdkImage, including the API. But let's leave the API changes for a separate PR.

@mivanov1988 Well, we cannot change the instances to vdkImage without changing the API. VDK version is passed in multiple APIs (deployment POST/PATCH) as part of DataJobDeployment, https://github.com/vmware/versatile-data-kit/blob/main/projects/control-service/projects/model/apidefs/datajob-api/api.yaml#L1133, and in GET as part of the DataJobDeploymentStatus, https://github.com/vmware/versatile-data-kit/blob/main/projects/control-service/projects/model/apidefs/datajob-api/api.yaml#L1170 and is then propagated throughout the different Control Service components.

JobDeployerV2 should be changed as well.

JobDeployerV2 should be changed as well.

Good point. Fixed, thanks


SRS: UML Class Diagram

Add the UML class diagram for InfoSafe to the SRS.

Class Diagram done, will need to update as implementation continues


[bug]: Outpainting in tile

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
8GB
What happened?
Tile mode for outpainting produces pixelated outpaints every time, (image strength is above 0.7), and if I try and change the tile size it produces the error...
Screenshots

Additional context
Any help would be greatly appreciated!!!
Contact Details
No response

I fixed the patchmatch somehow but tile is not working at all


Facing an issue where the model will generate responses out of order when encountering dialect

I have realised when if I am talking to the chatbot  and suddenly use a dialect word or phrase , the entire flow of the conversation become out-of-order. I have no problems with question in Standard English.
For example:

User: How are you?

Bot: I'm fine thanks!

User: Happy Birthday!

Bot: Thanks :D

I will then use the question, "How old yuh is?" and this is what happens:
User: How are you?

Bot: I'm fine thanks!

User: Happy Birthday!

Bot:
User: How old yuh is?

Bot: I am 21.

Thanks :D

If I continue with another normal  english question like "What is the time?" I will get this:
User: What is the time?
Bot: It's at the top of the page.

User: How are you?

Bot: I'm fine thanks!

User: Happy Birthday!

Bot:
User: How old yuh is?

Bot: I am 21.

Thanks :D

So the entire conversation is now confusing because of being out of order. If I use standard English question, the chatbot behaves fine. I am using the standard code provided. Is there anyway to troubleshoot these occurrences?

Error on my part, I initialise the chat_history before the inputs because of conflicts with my python interpreter. The chat_history variable was being used in the bot_inputs_ids before it was initialized and interpreter prevented me from using the chat_history variable so I initialize in the beginning with an empty input as a temporary fix.  This could most likely be the issue.

Error on my part


Sync latest 1.4.4 updates from original repo

Nothing too serious, as it is just a change that is very much needed that needs to be synced right away.

a PR is the only way I can get the fork to take in the commits from the base repository. This allows me to playtest the game and make a modification (if possible) using the seed conditions that I added in the seed conditions branch.


Add bindings for Set.xx

Here is the new PR for the methods described in #343 but each method is implemented in a separate commit. I also adjusted the line lengths and removed the whitespace where mentioned.

All green!


Add an architectural overview of bindgen to CONTRIBUTING.md

This should help new contributors who are coming to the code base for the first time get up and running.
r? @emilio

@bors-servo r+
Thanks a lot!

:pushpin: Commit 4089b3a has been approved by emilio

:hourglass: Testing commit 4089b3a1a2ee0e019940ce23a456d17d8b1e9914 with merge b349cf7ea033e5f43334b804b67010d401874a52...

Wow! Fast review :)

:sunny: Test successful - status-travis
Approved by: emilio
Pushing b349cf7ea033e5f43334b804b67010d401874a52 to master...


Update CancelableFuture.then to match the new Future.then type signature

Don't forget to publish this after you land it. 🚢


ShowLeadGenDialog.reg

For me, it was not in HKLM, it was in HKCU:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Microsoft Power BI Desktop]
"ShowLeadGenDialog"=dword:00000000

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

ID: 2a847d24-1a24-18c1-aa6e-2c977fa5e7cf
Version Independent ID: 8089b020-600d-cbf9-fac9-f8a9328a6c00
Content: How admins can manage the Power BI Desktop sign-in form - Power BI
Content Source: powerbi-docs/desktop-admin-sign-in-form.md
Service: powerbi
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Yikes - you're right! In addition, it's Microsoft Power BI Desktop (the Microsoft was missing in the key info). Sorry 'bout that, and thanks for pointing it out! Fixed in the article which will show up in the next couple of days. Thanks @sunk818 for pointing that out!


Minor: Fix bug in AND interval analysis tests (not code), and add more coverage

Which issue does this PR close?
Related to https://github.com/apache/arrow-datafusion/pull/7884/files
Rationale for this change
When I was figuring out how to add OR support for interval analysis, I noticed:

The tests were using open_open, which as shown on https://github.com/apache/arrow-datafusion/pull/7885 means all the cases actually were testing the same
There were three cases  that are not covered.

What changes are included in this PR?

Fix the test to use closed_closed
Add coverage of missing cases

Are these changes tested?

Are there any user-facing changes?

Marking as a draft until @berkaysynnada 's refactor PR has landed

Superseded  by https://github.com/apache/arrow-datafusion/pull/8276 (the whole notion of open intervals has been removed)


Do not watch information in the end of list in case sroll

Describe the bug
Do not watch the information at the end of the list in case scroll

[x] Search staking

https://github.com/Koniverse/SubWallet-Mobile/assets/117999489/2278bba2-f714-4b7c-b133-bf49959e830f

Version test: v1.0.3(165)
Devices test: IP 11
Validation passed.


How to reload M3U8 when TS file status 404 ?

If the TS file status 404,clappr always retry to load the TS file ,how can I listen the error Event? or clappr how to reload M3U8 after error.
ERROR:I/O Error while loading fragment:HTTP status:404,msg:Error #2032
live.html
WARN:retry fragment load in 1000 ms, count=0

I've tried something like this, but not work:
//PLAYER_ERROR
//PLAYBACK_ERROR
//CONTAINER_ERROR
player.on(Clappr.Events.CONTAINER_ERROR, function(){});
player.core.getCurrentContainer().on(Clappr.Events.CONTAINER_ERROR, function(){});

clappr:0.18

@devin87 Currently, Clappr only report HLS errors that are critical, when the playback fails. These retries are automatic, the player keeps trying to load a given TS file until a limit is reached, then it stops and triggers an error event.
If it's not doing that correctly, please let me know. Perhaps there's a bug in that.

@towerz Thanks. Here is the console log.
ERROR:I/O Error while loading fragment:HTTP status:404,msg:Error #2032
hls.html
WARN:retry fragment load in 4000 ms, count=2

ERROR:I/O Error while loading fragment:HTTP status:404,msg:Error #2032
hls.html
WARN:max load retry reached on last fragment of live playlist, retrying loading this one...

ERROR:I/O Error while loading fragment:HTTP status:404,msg:Error #2032
hls.html
WARN:max load retry reached on last fragment of live playlist, retrying loading this one...

...(not stops)

I do not know how to catch the exception in player (some events seems not trigger)?
HLS has timeout configuration for load the m3u8 or TS file?

Hi @devin87, I have been testing some options and adding some extra parameters to control HLS behavior.
If you use the latest version of clappr, you can now listen to the error event in case the fragment loading fails and the player stops retrying. The default behavior now is to not skip to the next fragment after reaching the maximum number of retries. Instead, it triggers an error event, which you can listen to and handle accordingly.
You can now control HLS retry behavior using the following parameters:

keyLoadMaxRetry - the maximum number of retries for loading decryption keys after a load error occurs
keyLoadMaxRetryTimeout - the maximum retry timeout (in ms) for loading decryption keys after a load error occurs
fragmentLoadMaxRetry - the maximum number of retries for loading fragments after a load error occurs
fragmentLoadMaxRetryTimeout - the maximum retry timeout (in ms) for loading fragments after a load error occurs
fragmentLoadSkipAfterMaxRetry - whether or not the player should skip to the next fragment after reaching the maximum number of retries. If set to false, an error event is triggered instead.

@towerz Thanks very much. I used some of the ways to let the player continue,some code like this.
setInterval(function(){
    if(is_playing) {
        //playback occasionally get stuck, the state still PLAYING
        if(player.core.mediaControl.container.playback.currentState == "PLAYING") do something;
        else {
            ...
            player.core.mediaControl.container.playback.firstPlay();
        }
    }
}, 2000);

I found another issue in the new version(clappr:0.1.13-0.2.5),the element(div.spinner-three-bounce)  not hidden after the player started playing.

@devin87 Can you share the source you are using? When you say the player gets stuck, you are referring to this retry loop you mentioned before? If so, on 0.2.5 the default behavior is to give up after retrying the current fragment, so you would get an error instead of the retry message.
About the spinner not hiding after playback starts, I could not reproduce. Could you please share the steps to reproduce this?

@towerz I can't test because the api server have some problems. I said the player gets stuck,not IO error, it happened on linux sometimes, I think is the decoding or graphics driver question. I mean can the player change the state when playback error?
The spinner hidden question, when the playback init, refresh the page, sometimes will ok,sometimes not. The version 0.1.8 no the problem.
Clappr is a great project (If can support to IE8 would be better, ha ha...). Thanks all of you. Here is the my code about playback.
var player;

function create_player(src) {
    if (player) player.destroy();

    player = new Clappr.Player({
        parentId: "#player",
        baseUrl: "clappr",
        source: src,
        useHardwareVideoDecoder: true,

        autoPlay: true
    });

    var timer, is_playing, last_error_time;

    player.on(Clappr.Events.PLAYER_PLAY, function () {
        is_playing = true;

        if (timer) return;

        timer = setInterval(function () {
            if (!is_playing) return;

            if (player.core.mediaControl.container.playback.currentState == "PLAYING") {
                last_error_time = 0;
            } else {
                if (!last_error_time) last_error_time = Date.now();
                else {
                    var time = Date.now();
                    if (time - last_error_time > 5000) {
                        last_error_time = time;
                        player.core.mediaControl.container.playback.firstPlay();
                    }
                }
            }
        }, 2000);
    });

    player.on(Clappr.Events.PLAYER_STOP, function () {
        is_playing = false;
    });
}

I test right now, if I change the channel,  the spinner not hidden.
create_player(src1);
create_player(src2);


Please also allow creating a minified compatibility.js

Hi,
using the minified target it is already possible to generate a minified version of pdf.js. Would you mind adding a line which also creates a standalone minified version of compatibility.js?
compatibility.js is used by pdf2htmlEX which we are packaging for Debian. Since pdf2htmlEX embeds compatibility.js into every generated HTML file, it does make sense to embed the minified version. The best binary package to supply a minified version of compatibility.js is the libjs-pdf package itself. We could carry a patch for make.js which minifies compatibility.js but would prefer to keep the amount of patches we carry low. Thus we wanted to ask you whether you could consider generating a minified version of compatibility.js in your version of make.js in addition to the minification that is already done?
Thank you for your consideration!

After PR #8102, compatibility.js is now bundled directly into the pdf.js and pdf.worker.js files to remove the need to include it manually via HTML code.
Furthermore, after PR #9093 (in preparation for the upcoming release of PDF.js version 2.0) we're no longer publishing compatibility.js as a standalone file.
Closing, since this issue is no longer relevant.


Added new ConfigAbstractFactory per issue #128

Configurable abstract factory allows creation of services via config key, see tests for usage.
Feedback greatfully received.

It's worth noting that this only works on PHP 5.6+ but as it's an optional abstract factory (I don't think we would enable it by default but open to that debate) it should be fine.

Benchmarks look "OK", but it is definitely slower:

I'm trying to figure out why this is so much slower - my limited knowledge thinks it shouldn't be, as it's only array lookups...

The slow point is argument unpacking, as I learned from this benchmark - https://gist.github.com/GeeH/ad03958521c8481be5e94e1a22556182
Personally, I put this in the realms of acceptable, I would take the performance hit for the convenience (I'm also aware I'm talking to myself).

The code looks sane to me, and I really like the feature.  The performance loss is rather minimal and neglectable.

The idea is neat, but there is one problem with it (and I do thing that it just needs testing):
Module 1:
$config = ['services' => ['config' => [ConfigAbstractFactory::class => ['foo' => ['bar', 'baz']]]]]

Module 2:
$config = ['services' => ['config' => [ConfigAbstractFactory::class => ['foo' => ['taz', 'tar']]]]]

With the current config merging semantics, this ends up being:
$config = ['services' => ['config' => [ConfigAbstractFactory::class => ['foo' => ['bar', 'baz', 'taz', 'tar']]]]]

Therefore, supporting string keys would be ideal:
Module 1:
$config = ['services' => ['config' => [ConfigAbstractFactory::class => ['foo' => ['bar' => 'bar', 'baz' => 'baz']]]]]

Module 2:
$config = ['services' => ['config' => [ConfigAbstractFactory::class => ['foo' => ['bar' => 'taz',
'bar' => 'tar']]]]]

With this config merging semantics, this ends up being (expected):
$config = ['services' => ['config' => [ConfigAbstractFactory::class => ['foo' => ['bar' => 'taz',
'bar' => 'tar']]]]]

@Ocramius I really dislike the idea of multiple ways to instantiate the same class with different parameters, for me, in that situation you would not use this abstract factory but write a "real" factory in the same way as you do currently. I feel this adds a layer of complexity that's not needed. This is the 99% use case solution, anything outside of that you wouldn't use this method.

instantiate the same class with different parameters

No, the idea is that Module 2 overrides Module 1, same as previously in ZF2. If I want to overwrite a single parameter, I need parameters to have a key.

Surely config merging would just handle this? If I override ComplexDependency::class key in the ConfigAbstractFactory::class key then config merging would override it?

Surely config merging would just handle this?

Yes, but your current implementation does not work with string config keys, only with numeric array keys (which config merging does add, not override)

Can you write me a test for that please @Ocramius?

    public function testInvokeWithStringKeyArguments()
    {
        $abstractFactory = new ConfigAbstractFactory();
        $serviceManager = new ServiceManager();
        $serviceManager->setService(
            'config',
            [
                ConfigAbstractFactory::class => [
                    InvokableObject::class => [],
                    FailingFactory::class => [],
                    SimpleDependencyObject::class => [
                        InvokableObject::class => InvokableObject::class,
                        FailingFactory::class => FailingFactory::class,
                    ],
                ]
            ]
        );
        $serviceManager->addAbstractFactory($abstractFactory);
        self::assertInstanceOf(
            SimpleDependencyObject::class,
            $abstractFactory($serviceManager, SimpleDependencyObject::class)
        );
    }

Please remember to use different test assets

This is really horrible having to have an array key makes my eyes bleed and makes me feel sick to my stomach. I don't want to do this.

That's how config merging works, @GeeH, and it's been around for at least 4 years.

I know how config merging works, I'm just thinking, @Ocramius, that it may be that if you want to overload something you just define a normal factory for it, it keeps this system clean and simple.

@geeh for you, it's a 2 LOC change. The alternative is throwing an exception when the array is not numerically indexed. As it currently stands, this test causes a fatal to be raised

@Ocramius  It's a 2 line change in the code, but makes the config massively more complex and unweildy.

@GeeH I'm fine with that decision, but then canCreate must fail when non-numeric indexes are given.
You'd need a check like following in canCreate:
$dependencies === array_values(array_map('strval', $dependencies));

Roger that, thanks for you input @Ocramius!

Closing this PR, I'm going to do some more work and reopen.

@GeeH Why not just mark it as a WIP? :smile:

@weierophinney TBH the comments all over the place are confusing my tiny mind

@GeeH reasonable. Ping me when the new PR is ready, or you've re-opened.


Added missing command help and removed linter exclusions

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

View a preview at https://prompt.ws/r/Azure/azure-cli/6321
This is an experimental preview for @microsoft users.