text:
Additional requirements on formulas

In https://github.com/Materials-Consortia/optimade-python-tools/pull/986 I have proposed two additional requirements for formulas (chemical_formula_reduced, chemical_formula_hill and chemical_formula_anonymous) dictated by my personal "common sense":

Formulas MUST NOT be empty strings. If a formula is unknown, null value MUST be used. Empty formula therefore looks as if the structure in question does not have any atoms, and I do not think this is something that should be allowed.
Formulas MUST NOT contain element proportions equal to 0. Trivially, if no such element exists in a structure, it MUST be excluded. If, however, minute proportion of a certain element is observed, it MUST NOT be rounded to 0 (specification requires rounding to integers for chemical_formula_reduced and chemical_formula_anonymous). I think a better approach than rounding would be to multiply all proportions by some number to eliminate fractional proportions.

This seems related to #361.

I am however wondering what counts as a minute amount.

In my proposal I meant > 0. So if element exists in the structure, it has to be mentioned in formula no matter the actual amount.

I would find it rather ugly to have very large element proportions.

I agree that large proportions are ugly, but they retain the information.

If an element is only present as a dopant, I would allow this element to not be in the formula.

If we all can agree on a formal definition for a dopant, then I guess such elements could in principle be excluded. However, element exclusion negatively affects queries which might be interested in dopants.

On second thought, dopants are probably not such a problem as the composition is made on pupose and in that sense it is intended as a material on it self. It is also likely that there is data on the pure material as well.
For experimental systems it could be more problemetic as a material can have impurities and defects. In that case a material may have a composition like Ca198Na2O199
Do we want users to be able to find this material if they look for CaO?  I think it should be found.
So I would place CaO in the chemical_formula_reduced field and Ca198Na2O199 in the Chemical Formula descriptive field to show that the material was impure.
There is also the elements ratio field that does keep the exect ratios between the elements and this field can therefore also be used to find doped materials. So we would not lose information if we rounded the amount of an element in the chemical_formula_reduced field.

For experimental systems it could be more problemetic as a material can have impurities and defects. In that case a material may have a composition like Ca198Na2O199 Do we want users to be able to find this material if they look for CaO? I think it should be found.

Fair enough. This can be achieved now by querying elements HAS ONLY [ "Ca", "O" ] no matter what conventions for formulas are used.

So I would place CaO in the chemical_formula_reduced field and Ca198Na2O199 in the Chemical Formula descriptive field to show that the material was impure.

Could you propose a programmatic way to arrive to CaO from Ca198Na2O199?

Formulas MUST NOT be empty strings. If a formula is unknown, null value MUST be used. Empty formula therefore looks as if the structure in question does not have any atoms, and I do not think this is something that should be allowed.

Nothing right now forbids a structure without any atoms (i.e., unit cell but no coordinates), and I think the reasonable chemical formula for that is the empty string. Does it not make sense to allow that? I suppose I can try to come up with some scenarios where it can be useful. You could possibly modify your proposed requirement to more be a clarification that empty formulas MUST only appear for structures without any atoms. (However - eh - how was it with those non-specifically placed hydrogens? Since I don't use this, I don't quite remember everything they make possible - is it perhaps possible to come up with a pathological example of only unspecifically placed hydrogens which should have an empty chemical_formula_descriptive?)
I think I agree with the limitation that, e.g. Na0 (0 = zero, not oxygen) should not be used to indicate disordered systems with very small concentrations, but I suppose the question is what one should do for those cases.

Just to join up this conversation with https://github.com/Materials-Consortia/OPTIMADE/issues/361, which approaches a similar problem from the elements and elements_ratios side.
One suggestion for impurities with vanishing/unknown concentration is to add them to the elements and elements_ ratios lists but exclude them from chemical_formula_reduced. I am more comfortable with elements_ratios being zero for one species (as all the normal filtering semantics on floats would work) compared to adding it to formulae where it would break string matching.
In this case, it might even be sensible to add a new structure_feature tag to such an entry so that it can be filtered easily (impurity?). We would just need to define the rules for when this tag should be added (e.g. a minimum elements_ratios). The only problem I can see is that we would be treating adatom and substitutional impurities differently from vacancies and stoichiometry-preserving defects which might be misleading for users. The alternative would be for queries that want to return only pristine structures to add something like elements_ratios HAS ALL > 0.01 (which I do not think is well-supported).

Could you propose a programmatic way to arrive to CaO from Ca198Na2O199?

A query that could return Ca198Na2O199 and related structures around CaO could be:
elements:elements_ratios HAS ALL "Ca":>0.49, "O":>0.49.

Although this is an optional filter feature, a database serving defected structures should probably implement it... With the additional suggestion above of adding the Na defect with elements_ratios = [0.5, 0, 0.5], the query above would become
elements:elements_ratios HAS ALL "Ca":=0.5, "O":=0.5 (where more awkward ratios would provide problems).

Fair enough. This can be achieved now by querying elements HAS ONLY [ "Ca", "O" ] no matter what conventions for formulas are used.
This would also return calcium peroxide CaO2. (and "O2" and "Ca" but you can prevent that with 'HAS ALL ["Ca","O"] AND nelements=2')

@Ratino I guess you could consider a vacuum a material in some respects. If a database contains data on the polarizability of different materials, they may include vacuum, as it also has a measurable polarizability.
Perhaps a small PR can already be created about the things about which we agree:

If the reduced chemical formula is unknown, it should be null.
Elements proportions MUST not be 0.

We can then turn the discussion about how to handle impurities into a separate topic.
Do databases have information about the purity of their structures? If not, it is not really useful to have such a discussion here.

Fair enough. This can be achieved now by querying elements HAS ONLY [ "Ca", "O" ] no matter what conventions for formulas are used.

This would also return calcium peroxide CaO2. (and "O2" and "Ca" but you can prevent that with 'HAS ALL ["Ca","O"] AND nelements=2')

Right, elements HAS ONLY [ "Ca", "O" ] will return CaO2, but so would elements HAS ALL ["Ca","O"] AND nelements=2. To filter out CaO2 one would need to query for elements:elements_ratios HAS ALL "Ca":>0.49, "O":>0.49, like @ml-evs pointed out.

@ratino I guess you could consider a vacuum a material in some respects. If a database contains data on the polarizability of different materials, they may include vacuum, as it also has a measurable polarizability.

Not sure if current specification is ready to describe such structures, but why not introduce them in the future.

Perhaps a small PR can already be created about the things about which we agree:

If the reduced chemical formula is unknown, it should be null.
Elements proportions MUST not be 0.

Agree. Shall we add that formulas MUST be empty strings only for vacuum? Structures with inspecifically placed hydrogen atoms would still have hydrogen atoms in formulas, I guess. Not sure, though, what to do about structures built from subatomic particles, for example, sole electrons, if only such exist.

We can then turn the discussion about how to handle impurities into a separate topic. Do databases have information about the purity of their structures? If not, it is not really useful to have such a discussion here.

At least experimental structural databases have information about impurities of sites.

Agree. Shall we add that formulas MUST be empty strings only for vacuum? Structures with inspecifically placed hydrogen atoms would still have hydrogen atoms in formulas, I guess. Not sure, though, what to do about structures built from subatomic particles, for example, sole electrons, if only such exist.

For me it is ok to specify that formulas MUST be empty strings only for vacuum.
In my opinion, inspecifically placed hydrogen atoms MUST appear in the chemical formula.
Good point about the (solvated electrons)[https://en.wikipedia.org/wiki/Solvated_electron]/(electrides)[https://en.wikipedia.org/wiki/Electride]. At low temperature they can be quite stable. The most logical would be to use the small letter "e". I guess we could use the centre of the electron density as the position. Although, I am not sure how to define the positions for a metallic electride. It would definitively be a good idea to add this to the standard, although this would affect more than just the elements field, so I think it would be better to create a separate issue about this.

Electrons and neutrons could be marked as e and n respectively, if only we mandate that such symbols appear in the beginning of the formula. This way no capital letter will appear before e and n if these elements appear in the formula.
However, I am not sure this is not an overkill. Will there be structures made up from electrons or neutrons entirely?

I do not see how a structure could be made of just electrons and neutrons. Neutrons that are not bound in atomic nuclei will decay quickly, and they can not form bound states. Electrons repel each other. So I do not see how you can form a chemical structure with just electrons and neutrons.
The only scenario I can think of with both free electrons and neutrons is when you would study the effect of (neutron/beta)radiation on a material. In that case, when an unbound neutron is "fired" at a material, an atom could get ionized. In that case, the trajectory would also contain a separate electron. Other than that, I do not see how an unbound neutron could appear in a trajectory or structure.

One of the most important papers for DFT, the Ceperley-Alder Monte Carlo simulations that more or less all LDA correlation functionals are based on
[ http://dx.doi.org/10.1103/PhysRevLett.45.566 ; 11k citations] deals with "structures" of only electrons. When you get down to low densities, you get something called a Wigner crystal, and the high density limit is the famous uniform electron gas.
If these can be called "materials" can be discussed, but I suppose it could be relevant to be able to represent them...

Thanks for a link, @rartino. So having electron (I suggest e) as possible chemical symbol makes sense. I just want to make sure e would not break anything in formulas:

In chemical_formula_reduced, elements are ordered alphabetically. e < A, thus there should be no problems.
In chemical_formula_hill, using Hill formula notation, e could be written on the leftmost position in the formula. This way it will appear before any capital letter.

I highly doubt IUPAC will ever standardize a chemical symbol starting with minor letter. A small fraction of 26^2 possible double letter symbols is already taken.

I'm not sure why it is a good idea to indicate extra subatomic particles in the chemical formulas at all? Are there any examples of anyone doing that? My vote is to skip the e+n extension until someone shows up with a relevant use case for that.
And then, rather than to relate an empty chemical formula to specifically vacuum, just say that an empty chemical formula MUST only occur for a structure with no atoms. Does that work?

I agree with @rartino, there is no need to over-complicate right now.

I'm not sure why it is a good idea to indicate extra subatomic particles in the chemical formulas at all? Are there any examples of anyone doing that? My vote is to skip the e+n extension until someone shows up with a relevant use case for that.

These are some examples of chemical formula's with electrons:
[Ca24Al28O68]4+4e- https://pubs.acs.org/doi/10.1021/ol701885p
[Na(NH3)6]+e−  (https://en.wikipedia.org/wiki/Electride)
[La8Sr2(SiO4)6]4+:4e– https://www.nature.com/articles/s41535-017-0053-4
Leaving the electrons out will give you a different material with different properties. It would also make it more difficult to find electrides in the databases.
It would probably be good to also have a field for the charge distribution on the atoms, as different charge distributions will give different materials.

@JPBergsma Fair enough, but your examples only make sense because they charge balance the ^{N+} in those formulas - which is a notation we also do not support, not even in chemical_formula_descriptive. Should we then support that as well? And,  does the separate e:s add anything to those formulas that isn't already communicated with the ^{N+} notation?

These are some examples of chemical formula's with electrons:
[Ca24Al28O68]4+4e- https://pubs.acs.org/doi/10.1021/ol701885p
[Na(NH3)6]+e− (https://en.wikipedia.org/wiki/Electride)
[La8Sr2(SiO4)6]4+:4e– https://www.nature.com/articles/s41535-017-0053-4
Leaving the electrons out will give you a different material with different properties. It would also make it more difficult to find electrides in the databases. It would probably be good to also have a field for the charge distribution on the atoms, as different charge distributions will give different materials.

Neither of the formulas considered in the initial post on this issue support charges. While having ionic composition formulas would be nice to have, I think this is out of scope for this particular issue.

I would like to revive the thread. There have been some nice future-proof suggestions, but how about introducing just the constraints expressed in my original post, for the time being? Non-empty formula and non-zero element proportion constraints have already been implemented in optimade-python-tools (see https://github.com/Materials-Consortia/optimade-python-tools/pull/986) and are suggested to be included into OpenAPI schemas (see https://github.com/Materials-Consortia/schemas/pull/8).
I understand that some structures will become non-expressable (vacuum structures; structures with very tiny proportions of some element), but at the time being the specification does not say how such formulas should be interpreted.

Echoing what I said previously, I want to be allowed to have a zero length cartesian_site_positions and then set the chemical formulas to the empty string. It may sound silly, but can be the outcome of certain automatic processes that generate structures, and I see no reason to disallow them from being represented.
I am in favor of stating that the proportion constant must be strictly a positive number.

I'm perhaps slightly more reticent to allow empty strings than others, as I think it goes against the spirit of what we laid out in the description of chemical_formula_x fields (Is a periodic box of vacuum a chemical? Is jellium?), but I would not be against explicitly loosening the spec in this regard. I think my standpoint is similar to (my intrepretation, at least) of Andrius' (@merkys), i.e., the constraints on non-empty strings and non-zero proportions are implied by the current spec, but that we could consider loosening this for 1.2 (i.e., simply changing the regex we would be introducing for the OPTIMADE v1.1 schema in https://github.com/Materials-Consortia/schemas/pull/8 and adding example values for these edge cases). Of course, if we really think the specification as it stands allows such empty formulae then we can just manually alter the optimade-python-tools-produced schema for 1.1 and drop the regex altogether.

@ml-evs If you say it these constraints are implied in the current specification, what passage of text do you support this on? Personally I would say our requirements/conventions are just simply unclear on this (which is why this issue is good - it should be clarified either way). However, I would also generally argue when it comes to schemas that unclear = allowed.
If we are moving this to a semantic discussion ("what is a chemical?") it should probably start with whether an OPTMADE structure generalizes to systems of zero atoms. I'd argue that I want them to, both based on semantics and utility. Then it follows:

If structures of zero atoms are not allowed, I think we needs quite a bit of clarification also for other fields (e.g., nelements > 0, nsites > 0, length of cartesian_site_positions > 0, etc.)
If structures of zero atoms are allowed, then what should I set the chemical formulas to? We specifically disallow null, so, empty string seems as the only viable choice for these systems?

I agree that "nonempty formula" part of this discussion boils down to whether OPTIMADE allows structures with 0 atoms or not. To me it seems that for structures with 0 atoms, structural properties like lattice_vectors and space_group_* have no sense.

It sounds like empty formulae are desirable after all, so I have just relaxed the constraint on non-empty formulae in optimade-python-tools (pending a review). (Re-reading my original comment I don't see anywhere in the spec that implies they cannot be empty, beyond the semantics of the term 'chemical' which I agree is not a relevant discussion to have here!)
The "0-proportion" elements is sensible though, so I have left that in.
Do we need a PR to tighten the wording in the spec on this, or can this be closed?

authors: JPBergsma merkys ml-evs rartino

repo: Materials-Consortia/OPTIMADE


text:
numpy.AxisError: axis 2 is out of bounds for array of dimension 2

Hi,
Thank you for a very interesting tool. I just installed the rc7 version and I'm trying to get the first example to run.
It runs well until after the Rigid registration but then fails regardless of what images I feed it. Below is the error output.
Thank you for the help!
`
======== Rigid registration complete in 18.376 seconds
/home/jovyan/venvs/valis/lib/python3.8/site-packages/valis/valtils.py:75: UserWarning: axis 2 is out of bounds for array of dimension 2
warnings.warn(warning_msg, warning_type)
Traceback (most recent call last):
File "/home/jovyan/venvs/valis/lib/python3.8/site-packages/valis/registration.py", line 3064, in register
rigid_registrar = self.rigid_register()
File "/home/jovyan/venvs/valis/lib/python3.8/site-packages/valis/registration.py", line 2324, in rigid_register
slide_obj.get_bg_color_px_pos()
File "/home/jovyan/venvs/valis/lib/python3.8/site-packages/valis/registration.py", line 551, in get_bg_color_px_pos
sum_img = self.image.sum(axis=2)
File "/home/jovyan/venvs/valis/lib/python3.8/site-packages/numpy/core/_methods.py", line 48, in _sum
return umr_sum(a, axis, dtype, out, keepdims, initial, where)
numpy.AxisError: axis 2 is out of bounds for array of dimension 2
`

Running with debug output I see that it shows the following error:
DEBUG:pyvips.error:Error  image: no property named `affine'
I have tested this with vips version 8.12.2 and 8.11.4 and the error is the same.
The final debug line is:
/home/jovyan/venvs/valis/lib/python3.8/site-packages/valis/valtils.py:75: UserWarning: list assignment index out of range
warnings.warn(warning_msg, warning_type)

Hello @MNM-TB ,
Thank you for bringing this to my attention. Could you tell me a bit more about the images you are working with? Are they by chance single channel images, maybe greyscale/processed versions of RGB images, or DAPI channels? It looks like maybe what is happening is that valis is trying to determine the background color of a multichannel image, but the image itself is single channel (hence why it doesn't have a 3rd axis, i.e. axis=2).  I was able to recreate this error when registering greyscale images, and so it's something I'll need to fix. But please let me know if your images are multichannel, since that fix might not address your issue.
Best,
-Chandler

Hi, You are absolutely right! They are monochrome grayscale images. It is Spatial sequencing samples where we use the cDNA fluorescence in each sequencing cycle and I'm looking at Valis as means to coregister them to remove drift. It would be excellent if it would be possible to use with single-channel images as well.

Hi @MNM-TB ,
Relieved to hear that was the probably issue :) I've updated the code to be compatible with single channel images (1.0.0rc8). Sounds like a very interesting dataset and looking forward to hearing how it works out. If there are issues, please let me know. I'd love to get VALIS to work with this sort of data.
Best,
-Chandler

Hi, Thank you for fixing this. Now it completes the registration but I'm wondering if I'm doing something wrong as my registrations are way off. My test images are resonably well alignes from the start. They are off my 40 µm or so and rotation 0.9°.  However after the VALIS registration one is rotated 45° or so. The files I'm trying to register is an inverted H&E to cDNA labeled with Cy3.
I'm using pretty much your standard code i.e.,:
slide_src_dir = export_path + "TestHE"
results_dst_dir = export_path + "TestHEout"
registered_slide_dst_dir = export_path + "intermediates"
reference_slide = "MNM_509_D1_cDNA_Crop_coReg.ome.tif"

# Create a Valis object and use it to register the slides in slide_src_dir, aligning towards the reference slide.
registrar = registration.Valis(slide_src_dir, results_dst_dir, reference_img_f=reference_slide)
rigid_registrar, non_rigid_registrar, error_df = registrar.register()

# Perform micro-registration on higher resolution images, aligning directly to the reference image
registrar.register_micro(max_non_rigid_registartion_dim_px=2000, align_to_reference=True)

I cannot attach my original files as they are about 4gb each but I attach a couple of the output thumbnails. Let me know if you need any additional information. Thanks'

Hi @MNM-TB ,
Glad to hear Valis is at least kind of working with your single channel images. I think maybe the problem with these registrations has to do with the preprocessing. In the thumbnails above, one is white on black (cDNA?) and the other black on white (inverted H&E?). They're essentially opposites, which I think might be the problem.
Do you happen to have the original RGB H&E image? Valis can register brightfield images to IF images, so it should automatically process the original RGB image to look like the cDNA image. The code is setup to use the default processing methods, but it would also be possible to do some color deconvolution on the H&E image to make it more closely resemble the cDNA image. Either way, the processed H&E image used for registration would be white on a black background, which should look more like the cDNA image. However, I'm assuming that 1st thumbnail is the cDNA image, and the 2nd is the inverted H&E, so please correct me if I'm wrong.
Valis also does adaptive histogram equalization on the IF images, but in this case it may be that it's too much, as the images are turning out pretty noisy. You could also try skipping that EQ step by passing {"adaptive_eq": False} to the "if_processing_kwargs" argument when calling registrar.register() and registrar.register_micro().
Finally, if you have small thumbnails of the original images you could share I wouldn't mind playing around a bit to see if I can get this to work better. They wouldn't have to be large, as an image with max dimension less than 1000px would be enough to test with. These could either be png (or similar), or you could use valis to read the slide (see the README for an example), rescale it ( warp_tools.rescale_img() ), and then save it as a png (warp_tools.save_img).
Let me know if any of these sound like good options and/or work out for you. If not, let me know and maybe we can try to come up with something else.
Best,
-Chandler

source: gharchive/issue

authors: MNM-TB cdgatenbee

repo: MathOnco/valis

license: MIT

license_type: permissive

license_source: github-api


text:
Move error on login screen

Fejlbeskeden flyttes på login siden, så den ikke havner ved siden af formularen
Før:

Efter:

Jeg har villet fikse det her for evigt - tak fordi du gjorde det :D

source: gharchive/pull-request

authors: MatiasGadeberg gaardee

repo: MatiasGadeberg/fiske-spillet


text:
🛑 Ticketing App is down

In 898e153, Ticketing App (https://rt.greenpeace.org.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ticketing App is back up in abe546f after 11 hours, 2 minutes.


text:
🛑 Inventario App is down

In f64eaeb, Inventario App (https://inventario.voluntariosgreenpeace.cl/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Inventario App is back up in 8898b18 after 11 hours, 32 minutes.


text:
Clean Makefile

A little bonus, you can run make in parallel (make -j2) to have both outputs faster.
The dependencies are handled better.

LGTM

LGTM

authors: mbunkus retokromer robUx4

repo: Matroska-Org/ebml-specification


text:
It's WordPress, dangit!

It should be WordPress, not Wordpress. The community is pretty serious about this. :)
Fixes: https://github.com/MaxCDN/bootstrap-cdn/issues/668

Good catch, thank you! Merging releasing to our staging server and once @jdorfman +1's I'll release to prod.
Cheers!

authors: HardeepAsrani jmervine

repo: MaxCDN/bootstrap-cdn

license: mit

license_source: bigquery


text:
fix Celestial-Enlightened

fixed enlightened celestial by replacing elytra with enchanted book in upgrade path

I think enchanted book is too cheap.Maybe we should use something more expensive,for example,lodestone?

honestly an enchanted book makes sense
eg. enlightened -> knowledge from books?
but yeah, that might work too

I've changed the upgrade logic to use the primary power key instead of use.

authors: EDTmagiclab Maxmani alpenstorm

repo: Maxmani/touhou-origins


text:
Database creation and connection

Creation and connection to the database.
Added test posts to the database with PHPmyAdmin.
Time : half a day.

OLD / First version of this blog, you can see it in the branch : ProjetBlog_v1
ProjetBlog_MVC is the newer / better version.


text:
Advance task - completed - Nikhila K S

Greetings @ruqaiyasattar @jafsia
I have completed the advance task of implementing Audio recorder and recorded audio player.
looking for some feedback, suggestions 🙏🏽
https://user-images.githubusercontent.com/100426366/226027689-fcec8259-8404-47e9-abe1-a21567099e61.mp4

impressive effort

authors: Nikhila-KS ruqaiyasattar


text:
Tanks forgetting connections to EIO on reload

Summery:
Every time i unload a world, such as quitting the game, then reload it EIO does not reattach to DeepResonance tanks until i change the input\output mode of one of the tank's faces.

Issue:
DR tanks are rendered defunct to anything other than DR blocks after world reload until manually reset.
Other DR blocks, such as Smelters, are seemingly unaffected.

Steps to reproduce:

Get two empty DR tanks, either crafted or obtained by other means
Place the two tanks vertically, with at least 1 block space between them
place a fluid conduit from EIO as to bridge the divide
set the Input/output mode of the tanks via right-clicking with empty hand
quit to title
a.or restart Minecraft, makes no difference
Reload world, observe
a. This occurs regardless to if the world was freshly generated or existing.

Useful information:
DR version 1.1x-1.4.5 built against 1.11/ 0254505c4d2d063fecbb6846d5134c09e2b6e243
mcjtylib version1.1x-2.3.7.jar (from Curse)
EnderIO version 1.10.2-3.1.168 (from Curse)
Minecraft version 1.10.2
Forge Version 12.18.3.2221

It is possible that this bug will be fixed next release

repo: McJty/DeepResonance


text:
Issue with waila ?

This appears in the log : Could not find class com.mcjty.rftools.apideps.WailaCompatibility
RFTools 1.73

Ah oops. I think I know what's wrong. I'll fix it.

Fixed in upcoming release (in a moment)

Nice ! thanks :D

repo: McJty/RFTools


text:
List of not edited normal mobs.

Iron golems, fishes, turtles, foxes, wolves, donkeys, creepers, phantoms, zombified piglins, silverfish, piglins. hoglins, zoglins, vexes, allays, skeletons, wither skeletons, slimes, magma cubes, endermites and wandering traders aren't changed at all.

All these will be added. Just not quite yet since I'm trying to decide what stats to change for them.

Newest version will include every mob. Updating in 10-30 minutes.


text:
Defense FeedBack

What does this PR do?

Implements feedback from my first cp defence with Mark

Description of Task to be completed?

Fix Search input
Fix NavBar
Write Client Test
Reduce the number of action files

Coverage decreased (-0.2%) to 79.417% when pulling dc0d92f78df692a3a7669bffae594f4f5746f0e8 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling b53275c50e727b3e32200cc29397fed11d732f6a on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling 7966e75a98318c07c4e3a4229ee95cd6904a6f45 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling 890d539998e2252eb24bfd9a45e589dcb98e52f1 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling 74cf28252fdb88a8879403e8d67a774e731105c4 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling d5b4411bfbf6cb22c24fc9279eb435608b303920 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling 5ec2cec35358b59cdc438a91837690ff716ed4f2 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling 7c077af621035001699600c0b5628bb78f0d7d45 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling 7cfb0b35bcedcbe81b25034442a127237ab05ce1 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling 4bdd7662d5ac74c85a138873096d3932c9e51319 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling e1644fe6cfe60b47e6f3192cd2dfffe19a87d4c2 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling 67cf01b370a607f3d9b154029dcafa3b40c29a2d on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage decreased (-0.2%) to 79.417% when pulling 7a69a30986fa4be7eda15c75ff6f7c93a0051c58 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage increased (+0.8%) to 80.389% when pulling 2eacd0b7929150225f6624d073996a92124cc2b2 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage increased (+0.8%) to 80.389% when pulling 31cf259b6dba9f1573e63c22bd7fab6b6314e974 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage increased (+0.8%) to 80.389% when pulling 3ad12222bfec071c13cd9eb96efadb627c6327ed on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage increased (+0.8%) to 80.389% when pulling 00d6bfbd4f3b6cf2f85c1c53e9f58e60186b3ed0 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage increased (+0.8%) to 80.389% when pulling 04803e008b6aef1e40c7e63466a486721b64275b on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage increased (+0.8%) to 80.389% when pulling db0f3c055b8522bd1834a7eed3d99d18e6e7f409 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage increased (+0.8%) to 80.389% when pulling 64684b8e893425ff8758b0e0812aa5f3080b9136 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage increased (+0.9%) to 80.519% when pulling 93fb0d2ae4ac3fb27fd281066d43db071006624a on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage increased (+0.9%) to 80.519% when pulling d57df7cff3c61b6f799f81c459a036e787c11fc9 on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Coverage increased (+2.3%) to 81.954% when pulling 66c8539bbc6b1a83e57435489970c364dd98259b on development into 596e0c84db6bd62dbd1d2ff27f12148c88053140 on master.

Changes Unknown when pulling 23eb0b879798db37d7094c5a1f370e93cae99943 on development into ** on master**.

Changes Unknown when pulling 23eb0b879798db37d7094c5a1f370e93cae99943 on development into ** on master**.

Changes Unknown when pulling 84500c85e743b1f24d0cbfe224afc8f679473771 on development into ** on master**.

Changes Unknown when pulling cc19c2523449aa31cf6758c89d6b108a6f032e9a on development into ** on master**.


text:
[MAT-7639] Remove extraneous label on DateTimeField component

Update vulnerable versions of node-sass to sass. increment minor version
Update yml file with correct directories for running scripts
Use simplified default working directory
Update workspace reference since default workspace does not work for pascalgn script
modified select stories, and removed unnecessary error prop to mui select and helpertext
Updated version number
Updated npm publish with publish_command
bumped package version
Add MadieDiscardDialog, unit test, styles, stories
run linter
Bump react version
Update publish command to use npm:
Add ReadOnlyTextField
Add storybook and remove focus border
add test
Bump package version to 1.0.16
Add madie-alert component and stories
Add styling and tests for component
Add MUI icons and update dependencies
Bump package version
AutoComplete component
bump up version
move rest of the props of select box all the way down to last so that we can override props if needed
bunmp version
Added aria label for site footer
Added proptypes for madie alert component
MAT-4925 508 compliance
update versions
update Select
fixed test cases for madie alert component
Bumped up version
update version
MAT-4921 alt text for madie logo
Select: associate label with aria-labelledby and helper text with aria-describedby
update version
add aria-label to IconButton instead
update version
MAT-4923 508: Link Items Per Page Drop Down With Label
bump release version
MAT-4923 revert package json
MAT-4931 508: Discard Changes Modal
bump release version
Update button style to use a new variant=action
Update styles, fix disabled state
Bump file version
Updated button styles and added a new variant outline secondary
MAT-4669 global link color
audit fix
Added outline filled variant for buttons
updated package version
update version
revert previous change for new requirement
Created a new component AutoComplete along with few stories
Created a new component AutoComplete along with few stories
ran prettier command
removed unnecessary comments
Incremneted package version
Updated color for error state
Removed comments
exported the component
testing build
changed package-lock.json
changed package.json
changed package.json
changed package.json
changed package.json
changed package.json
adding modal for deleting
added styles
made sure formik onchange is not overwritten by custom onChange
audit fixes
added test cases
Updated package lock
Revereted audit fix
Updated background color for disabled state
updated package-lock
increased package version
Updated disabled background color for autocomplete
Added disabelled style for Select
updated package version
Updated package lock
MAT-4923 508: Link Items Per Page Drop Down With Label
added popover
MAT4923 508: Link Items Per Page Drop Down With Label
bumped the version
made rendering more generic
fixed storybook rendering
reversed changes
Add warning and info to toast
adjust sizing
add coverage
version bump
version bump
Make placeholder and text inputs complant for contrast
Add missing opacity, bump version
Update Textfield and Select
Update autocomplete, update some dependencies
Update dependencies, audit fix, kill unused depricated jwt that breaks downstream apps without old react versions. manually update @cmsgov design system dependency
Update popover to take multiple props along side some canEdit locked props
nosec line
nosec
remove nosec
Update test for popover and button
Add unit tests for all the svg icons.
Update coverage for Select
Add coverage for TextField
Update coverage for Pagination
Update accordian test
Remove lgacy modal
Remove unused components hardcoded to QPP logic.
Format test
Update version package number
Empty-Commit
fix: angular/package.json & angular/package-lock.json to reduce vulnerabilities
Add TextArea component
Add scss for TextArea
fix: Dockerfile to reduce vulnerabilities
Update Dockerfile
add Node 18 to tests
Implement 4 types of reusable navigations
Update propTypes
Remove console.log
Fix test error. audit fix dependency
Commit missing tab export
Update Tabs from feedback. bump version
Added new reusable radio button component
Removed top div for RadioButtons Component
Disabling radio group option based on supplied prop
updating lock file
added date field component
removed unwanted lines
added packages
updated stylings
updated proptypes
updated styling for placeholder
updated stylings
updated stylings
styling change
modified test case
updated version
update to new stylings
update to new stylings
merged develop
updated version number
testing build no code change
added date time field
updated packages
added test case and updated version number
changed variable datatype
minor style change on text area to make it level with other textfields.
changed the labels
fixed can edit
upgraded the version
removed unwanted declarations
MAT-5828 time field
try resolve vulnerability
try resolve vulnerability
added extra params for mutiselect
updated package-lock.json
audit fix
fix: shared/package.json & shared/package-lock.json to reduce vulnerabilities
fixed properties of popover
updated version
decouple the design system with shared.
update sass
bump version
update git ignore
update story
Exported TimeField component
Updating Time Field Component to accept additional props, and enabled TimePicker
update dateTimeField component to use utc adapter.
fix input label
bump package version
update to use utc from adapter
fix package
run install
revert packag
fixing date bug
fixed audit issues
removed the issue causing line
merged develop and increased the version
MAT-6418 fix vulnerabilities
MAT-6418 updated package version
MAT-6431: update for 508 compliance
bump versions
MAT-6431, fix compliance issues with autocomplete, bump version.
Update chip styling to happen as a styleRule instead of a chip prop.
Fix compliance issues with dividers and borders. bump version.
bump version. fix readOnly textfield
MAT-6459: Resolve critical dependencies outside of React
MAT-6459: Resolve critical dependencies outside of React
MAT-6459: Run preliminary audit fix
MAT-6488: Add required prop to add a required indicator on dialogs
audit dependencies
Update color
update color
MAT-6488: Normalize slight variation in hight for Select, TextField, ReadOnlyTextField
fix: react/package.json & react/package-lock.json to reduce vulnerabilities
Update unit_test_coverage.yml
MAT-6488: Add tooltip for textfields. lint source, fix media transformer.
MAT-6488: Dynamically add inputProps when not present
MAT-6488: add proptypes reference for inputProps
MAT-6488: Modify style format so build doesn't break
MAT-6740 set max width on dynamic text fields
MAT-6346 Verify dependencies/dev-dependencies for madie-design-system
MAT-6346 dependency updates
MAT-6346 dependency updates
MAT-6346 reverting dependency updates
MAT-6346 reverting dependency updates
MAT-6346 revert dependency changes
MAT-6346 depenedency updates
MAT-6346 build fix, disabled cache
MAT-6346 Updated lock file
MAT-6346 build fix, enable cache
MAT-6346 removed node 18 actions/upload-artifact@v4 does not support matrix strategy
MAT-6346 revert git action v4
MAT-6346 downgrade actions from v4 to v3
MAT-6346 put back node 18
MAT-6432: Implementing behavior of DateField to support changes in madie-measure
MAT-6432: Fixing an issue with timezone for testing
MAT-6432: Fixing an issue with timezone for testing
MAT-6432: Fixing an issue with workflow for npm-publish
MAT-6432: Release 1.2.10 - updating to fix some dependency issues and trying to figure out what is causing hte npm publish issue
MAT-6432: Release 1.2.11 - regenerating package-lock.json
MAT-6432: Release 1.2.11 - audit for CI workflow
MAT-6432: Release 1.2.11 - audit fix for axios -> follow-redirect
MAT-6432: Release 1.2.11 trying Yarn for npmjs publish
MAT-6432: Release 1.2.11a trying Yarn for npmjs publish
MAT-6432: Release 1.2.12 trying Yarn for npmjs publish
MAT-6432: Release 1.2.13 trying npm for publishing; maybe commands were wrong before
MAT-6432: Release 1.2.14 still trying to fix deploy
MAT-6432: Release 1.2.14 - changed to TEMP_NPM_TOKEN; still trying to fix deploy
MAT-6864 Change Multiselect checkbox to grow with many selected
MAT-6864 Version bump
MAT-6432: Bumping x-date-pickers version to match madie-measure
MAT-6432: Bumping to vesrion 1.2.15
MAT-6432: Bumping to vesrion 1.2.15 ..npm publish
MAT-6432: Bumping to vesrion 1.2.16
MAT-6432: Bumping to vesrion 1.2.17
MAT-6432: Bumping to vesrion 1.2.16-temp trying to fix npm_publish
MAT-6432: Bumping to vesrion 1.2.16-tempb trying to fix npm_publish
slack/FixingNpmPublish
slack/FixingNpmPublish: Bumping version
slack/FixingNpmPublish: Bumping version with prerelease beta tag
Release 1.2.17-beta.0
npm publish with correct working directory
MAT-7015: add onBlur that is called for DateField's inner components of TextField as well as calendar popup; add some minor styling tweaks and override capabilities; version bump
MAT-7015: DateField label style updates for required
MAT-7015: fix DateField lint issue
MAT-7151 Adding a new Component for Input type number
MAT-7151 Updated NumberInput component with custom configs
MAT-7151 Updated package version
MAT-7151 Simple Audit fixes
Update unit_test_coverage.yml
MAT-7151 Updated Number TextField to allow hypen(-) for negative numbers
MAT-7335 preventdefault on tooltip onclick
MAT-6393: Fix data-testId to non harcoded dynamic values
MAT-6939: bump package
MAT-7428 MadieDialogs can be dragged around
MAT-7428: PropTypes maybe
MAT-7428 add -A
MAT-7248 install package in right place
Fixing Z-index on ToolTip
Hat to update styling for tooltop in qppds as these syles are overriding the styles from styles directory
MAT-7462 bump axios version to address vulnerability
MAT-7462 bump release version
MAT-7462 update lock json file
MAT-6188 add option to copy madie alert text with button
MAT-6188 remove a console log
npm audit fix?
test fix?
test attempt
MAT-6188 remove unneeded code
MAT-7462 updated axios version
MAT-6188 cover edge cases, write tests
MAT-6188 make copyText a state variable
MAT-6188 adjust spacing a little
MAT-6188 remove unneeded import
MAT-6188 undo change
MAT-6188 undo change 2
MAT-7594 update docker file
MAT-7364: Dependency Audit
MAT-7366: Revert dependency change. add override
MAT-7366: Hopefully update sync
MAT-7364: revert against main
MAT-7364: Bump lock
MAT-6188 check format
MAT-6188 version bump
Trigger Release 1.2.26
MAT-6188 add toast and tooltip
Trigger Release 1.2.27
MAT-6188 delicous kebab
Trigger Release 1.2.27
MAT-6188 fix newlines
remove testing counter
Trigger Release 1.2.28
Fix security issues
MAT-7639: Remove extra label from DateTimeField.
MAT-7639: Update styling to ensure consistent field height with other inputs

MADiE PR
Jira Ticket: MAT-0000
(Optional) Related Tickets:
Summary
All Submissions

[ ] This PR has the JIRA linked.
[ ] Required tests are included.
[ ] No extemporaneous files are included (i.e Complied files or testing results).
[ ] This PR is merging into the correct branch.
[ ] All Documentation needed for this PR is Complete (or noted in a TODO or other Ticket).
[ ] Any breaking changes or failing automations are noted by placing a comment on this PR.

DevSecOps
If there is a question if this PR has a security or infrastructure impact, please contact the Security or DevOps engineer assigned to this project to discuss it further.

[ ] This PR has NO significant security impact (i.e Changing auth methods, Adding a new user type, Adding a required but vulnerable package).
[ ] All CDN/Web dependencies are hosted internally (i.e MADiE-Root Repo).

Reviewers
By Approving this PR you are attesting to the following:

Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose.
The tests appropriately test the new code, including edge cases.
If you have any concerns they are brought up either to the developer assigned, security engineer, or leads.

wrong branch...


text:
Add PBCore, Mediatrace and image sequence CLI help

Here's my best guess at what these should look like..

thanks!

authors: JeromeMartinez kieranjol

repo: MediaArea/MediaInfo


text:
Windows GUI: Use older API for getting system DPI

Use older API to get system DPI for taking DPI scaling into account when setting window size so that it works on older Windows versions.

In theory LOGPIXELSY should be used for the height but I guess this is a corner case, but not blocking.

In theory LOGPIXELSY should be used for the height but I guess this is a corner case, but not blocking.

Isn't X or Y having same DPI? There is only one DPI setting.

Isn't X or Y having same DPI? There is only one DPI setting.

I bet that in practice they are same for 99.999% of devices but my understanding of the theory is that you can get 2 different values between width and height with this API.

There is only one DPI setting.

With this API there are 2, LOGPIXELSX ("Number of pixels per logical inch along the screen width.") and LOGPIXELSY ("Number of pixels per logical inch along the screen height.")

With this API there are 2, LOGPIXELSX ("Number of pixels per logical inch along the screen width.") and LOGPIXELSY ("Number of pixels per logical inch along the screen height.")

As far as I know, there is no way in Windows to set different DPI for X and Y. So I don't know if it is possible to have two different values for that API. Wonder why it has two though.

Wonder why it has two though.

I bet that they expected to manage non square pixels (it is currently part of the past for TV only but it could return one day in computer screens... Or not) at some point and that it was abandoned in the meantime.

I bet that they expected to manage non square pixels (it is currently part of the past for TV only but it could return one day in computer screens... Or not) at some point and that it was abandoned in the meantime.

Probably because it seems this API can be used for printers too. Maybe printers can have different X and Y.

Tested on a single monitor at 100 - 200% DPI scale and it works the same as when using the other API.

Please update with #858 (comment) ASAP, then I merge and do a new public version.

Alright.

Argh the space and tab issue again. 😓

@cjee21 FYI https://github.com/MediaArea/MediaInfo/pull/860#issuecomment-2142503257.


text:
🛑 MediaNext is down

In 252f6a2, MediaNext (https://the-bot.thein321.repl.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MediaNext is back up in a7b9e2a.

repo: MediaPlay-Discord/status


text:
Remove hardcoded values from PortScanner.py

Instead of using the hard coded values for common ports, port services and os detection ports. Use the values from the files in temp_files instead.

Hey @MeetRajput00 I am new to open source. I saw this issue on a quick search. I would be verry happy to contribute this project. Can you give me a little guide?

Sure thing @SahanY099. I have added a Contributions.md file in this project, you can use this file as a reference to make contributions in this project. It's steps are generalized and you can use them to make contributions to any projects.
If you get stuck on any step, feel free to reach out.

Ok @MeetRajput00. I'll do my best to improve this project 😊.

Cool. Keep learning ✅

Hey, I noticed that in the os_detection_ports.txt uses just a raw dictionary like data format. How about using a json file to store those data?. There we can load that into the os_dict.

Hmm, good idea. Go for it.

👍 I am working on it.

Hey @MeetRajput00, I created a pull request for this issue. Can you please take a look that 😊.

Hi @SahanY099, great work with the pr. There are just some issues which I've commented out in your pr, can you please check them?

I'll look at it. Thanks for your attention 👍


text:
BUG Issue

环境
1.系统环境：Ubuntu16.04
2.MegEngine版本：0.3.1
3.python版本：3.6
你好，我在用 MegEngine 写代码的时候遇到了一个 Bug。跑下面这段代码时，显存不断增加，感觉木有释放。Bug 代码如下：
`import megengine as mge
import megengine.module as M
import numpy as np
class Net(M.Module):
def __init__(self):
    self.fc0 = M.Linear(2, 100)

def forward(self, inp):
    return self.fc0(inp)

net = Net()
for i in range(100000):
data = mge.tensor(
np.random.rand(64, 2).astype(np.float32) * 2 - 1
)
net(data)
`
这个 Bug 很奇怪，后来又反复看了几遍官网的教程和几个示例，我把下面这段代码放到循环外。
data = mge.tensor(         np.random.rand(64, 2).astype(np.float32)     )
然后在循环里使用 set_value 对 tensor 进行赋值才算解决显存问题。
`import megengine as mge
import megengine.module as M
import numpy as np
class Net(M.Module):
def __init__(self):
    self.fc0 = M.Linear(2, 100)

def forward(self, inp):
    return self.fc0(inp)

net = Net()
data = mge.tensor(
np.random.rand(64, 2).astype(np.float32)
)
for i in range(100000):
data.set_value(np.random.rand(64, 2) * 2 -1)
# data.set_value(data * 2 - 1)
net(data)`
但还是不理解为什么无法直接在循环里使用 mge.tensor？而是一定要用 set_value？
希望官方能解答一下呀

https://github.com/MegEngine/MegEngine/issues/5
看起来是alpha版本的已知问题

感谢您对MegEngine的关注，该问题是本次版本的已知问题https://github.com/MegEngine/MegEngine/issues/5，该问题的深层次原因是动态图机制实现还比较原始，无法正确进行引用计数，导致显存无法释放。暂时的规避方式是您说的这样，通过 set_value 来复用 tensor。问题有详细的解决进展后我们会更新到该issue下面，也欢迎您参加天元开发者交流群1029741705，及时获得最新进展！

TESTIMONY ON HOW I BECAME INSTANT MILLIONAIRE WITH THE HELP OF THE ILLUMINATI. MAIL THE COUNCIL AT ( illuminatiofficialverified.org@gmail.com )
Hello everyone, i have to write this testimony because of people out there who also will like to join the Illuminati, because i am really happy to be member of Illuminati cult society today, i have been searching for the right hand to join this organization of Illuminati i finally got this nice Prof.Monday and Barr. Mikhail ,who help me in joining even when i was asked to buy all the items my self which i did for the initiation. though it cost me some money, but every thing went out successfully, and an instant sum of 1,000,000,000.00 US dollars was given to me with a free home of my choice in CALIFORNIA USA. And also, power, influence, good position fame including $300,000,000.00 dollars monthly as a salary for me. If you are interested contact the Illuminati full membership council through this email address above . Today my family and i are  happy for following the Light. See you there. You may WHATSAPP CHAT HELPING MEMBERS  at +13252429274 for special information on how to be a full member

authors: MrsWhitney amusi lcxywfe megvii-mge

repo: MegEngine/MegEngine


text:
mini-coco128 数据集 建议增加国内网盘

https://yolox.readthedocs.io/en/latest/train_custom_data.html
For example:
If you download the mini-coco128 and unzip it to the datasets, you can direct run the following training code.
mini-coco128 数据集 应该放  国内网盘
google网盘不能访问！

Is this link accessible? https://github.com/ultralytics/yolov5/releases/download/v1.0/coco128.zip

I download it recently, upload it to baidu netdisk, wish it is helpful
链接: https://pan.baidu.com/s/1fcaBAUgJxhKYP774KJwjqQ  密码: 9hst

@monkeycc I think it has been resolved, so please close it.

Is this link accessible? https://github.com/ultralytics/yolov5/releases/download/v1.0/coco128.zip

coco128 from Yolov5 is yolo format but coco format is needed. Baidu netdisk version from @hopesala is right (coco format).

authors: Keiku Shua-Kang hopesala monkeycc

repo: Megvii-BaseDetection/YOLOX


text:
集成walle之后，高德地图白屏

我是安卓开发者，项目里用到了高德地图
集成了walle之后，我项目的高德地图运行即白屏
更狗血的是，我回退了git版本之后，地图依然白屏
因此我怀疑walle改变了我项目的文件内容或结构
据我了解，高德地图使用了自定义View，并且使用了Asset资源文件，
并且不兼容某些自定义打包工具，
高德官方的三种解决办法全试过了，不管用：
http://lbs.amap.com/faq/android/android-map/349

由于walle给我项目结构造成的不可逆的改变，我现在的开发工作陷入停滞
因此我没有别的要求，只希望教我“如何彻底清除walle插件”，并恢复项目到集成之前的状态就行

要相信科学，如果不想用全部revert，代码都是开源的，哪里有对项目结构做成不可逆的改变？

6aG555uu5byA5rqQ77yM5L2/55So6Ieq5oS/77yM5Lia5Yqh5LiN57K+77yM5a6b6Iul5pm66Zqc44CC

已解决
已确认不是walle造成的问题，这个锅该高德地图背
高德地图上周四更新了最新版本之后，我从那以后安装的包就全都是白屏了
但是我经过三天申诉和发工单咨询之后，都得知了否定的答案，我不得不转回来问walle的大家
但是刚才！我回退了一下高德地图的依赖，让他依赖于旧版本jar包，而不是跟随在线的最新版本
再重新安装，看地图，一切都正常了
高德地图开发团队，自己挖的坑，官网没有任何提示，甚至官方技术咨询都否认新版本存在问题，真的很坑

authors: achellies macouen zyktojo

repo: Meituan-Dianping/walle


text:
Ipsec compatibility

*IPsec unaware configuration added
*IPsec test added

attended to said issues, please review again


text:
getting error when running mellplayer

hi
when i try to run mellplayer, i get this error
Traceback (most recent call last):
  File "/usr/local/bin/mellplayer", line 11, in <module>
    load_entry_point('MellPlayer==0.1.1.1', 'console_scripts', 'mellplayer')()
  File "/home/moein/.local/lib/python3.5/site-packages/pkg_resources/__init__.py", line 564, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/home/moein/.local/lib/python3.5/site-packages/pkg_resources/__init__.py", line 2608, in load_entry_point
    return ep.load()
  File "/home/moein/.local/lib/python3.5/site-packages/pkg_resources/__init__.py", line 2268, in load
    return self.resolve()
  File "/home/moein/.local/lib/python3.5/site-packages/pkg_resources/__init__.py", line 2274, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/local/lib/python3.5/dist-packages/mellplayer/start.py", line 11, in <module>
    from mellplayer.controller import mell_ui, initial_player
  File "/usr/local/lib/python3.5/dist-packages/mellplayer/controller.py", line 12, in <module>
    from mellplayer.player import mell_player
  File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 315, in <module>
    mell_player = Player(log_handler=player_logger, ytdl=True)
  File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 43, in __init__
    self.volume = 100
  File "/usr/local/lib/python3.5/dist-packages/mellplayer/utils/mpv.py", line 918, in <lambda>
    setter = lambda self, value: self._set_property(name, value, proptype)
  File "/usr/local/lib/python3.5/dist-packages/mellplayer/utils/mpv.py", line 692, in _set_property
    _mpv_set_property_string(self.handle, ename, str(proptype(value)).encode('utf-8'))
  File "/usr/local/lib/python3.5/dist-packages/mellplayer/utils/mpv.py", line 95, in raise_for_ec
    raise ex(ec, *args)
mellplayer.utils.mpv.PropertyUnavailableError: ('mpv property is not available', -10, (<MpvHandle object at 0x7fa6a35d48c8>, b'volume', b'100.0'))

@moeinrahimi hi, can you tell me your environment. There are some bugs and I will fix it soon

@Mellcap I'm on Linux Xubuntu 64bit

@moeinrahimi This problem has been solved, when you can search MellPlayer(0.1.1.2), run
[sudo] pip3 install MellPlayer --upgrade

@Mellcap
now I'm getting this message :
     MellPlayer
  ➣  榜单          加载歌曲中...
     流行
     摇滚
     民谣
     说唱
     轻音乐
     爵士
     乡村
     古典
     电子
     舞曲
     另类/独立
     学习
     工作
     午休
     下午茶
     清晨
     夜晚
     华语
     欧美
     日语
Fatal Python error: Cannot recover from stack overflow.

                                                       Thread 0x00007fb1eb7fe700 (most recent call first):
                            File "/usr/lib/python3.5/threading.py", line 293 in wait
      File "/usr/lib/python3.5/queue.py", line 164 in get
                                                           File "/usr/local/lib/python3.5/dist-packages/mellplayer/watcher.py", line 55 in k_executor
                                                                       File "/usr/lib/python3.5/threading.py", line 862 in run
                                                File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
                                      File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap

                    Thread 0x00007fb1ebfff700 (most recent call first):
                                                                         File "/usr/local/lib/python3.5/dist-packages/mellplayer/utils/getch.py", line 40 in __call__
       File "/usr/local/lib/python3.5/dist-packages/mellplayer/utils/getch.py", line 24 in __call__
                     File "/usr/local/lib/python3.5/dist-packages/mellplayer/watcher.py", line 47 in k_watcher
                                File "/usr/lib/python3.5/threading.py", line 862 in run
         File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
                                                                               File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap

                                                             Thread 0x00007fb1f8de9700 (most recent call first):
                                  File "/usr/local/lib/python3.5/dist-packages/mellplayer/watcher.py", line 89 in t_watcher
                                             File "/usr/lib/python3.5/threading.py", line 862 in run
                      File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
            File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap

                                                                          Current thread 0x00007fb1f95ea700 (most recent call first):
                                                       File "/usr/lib/python3.5/genericpath.py", line 124 in _splitext
                                        File "/usr/lib/python3.5/posixpath.py", line 122 in splitext
                      File "/usr/lib/python3.5/logging/__init__.py", line 278 in __init__
           File "/usr/lib/python3.5/logging/__init__.py", line 1384 in makeRecord
   File "/usr/lib/python3.5/logging/__init__.py", line 1414 in _log
                                                                     File "/usr/lib/python3.5/logging/__init__.py", line 1308 in error
                                                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 232 in run_player
                                                                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                                              File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                          File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                      File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
  File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                              File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                          File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
      File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                  File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                              File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
          File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                      File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                                  File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
              File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                          File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                                      File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                  File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                              File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                                          File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                      File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                  File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                                              File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                          File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                      File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
  File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                              File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                          File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
      File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                  File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                        File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                                              File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                                                    File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
          File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 69 in next_song
                                      File "/usr/local/lib/python3.5/dist-packages/mellplayer/deco.py", line 23 in wrapper
                                            File "/usr/local/lib/python3.5/dist-packages/mellplayer/player.py", line 233 in run_player
                                                        ...

                                                           Thread 0x00007fb1f9ff1700 (most recent call first):
                                File "/usr/local/lib/python3.5/dist-packages/mellplayer/utils/mpv.py", line 360 in _event_generator
                                                     File "/usr/local/lib/python3.5/dist-packages/mellplayer/utils/mpv.py", line 372 in _event_loop
                                                                     File "/usr/lib/python3.5/threading.py", line 862 in run
                                              File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
                                    File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap

                  Thread 0x00007fb21a68b700 (most recent call first):
                                                                       File "/usr/lib/python3.5/threading.py", line 1070 in _wait_for_tstate_lock
                                                                   File "/usr/lib/python3.5/threading.py", line 1054 in join
                                              File "/usr/local/lib/python3.5/dist-packages/mellplayer/watcher.py", line 69 in key_watcher
                                                           File "/usr/local/lib/python3.5/dist-packages/mellplayer/start.py", line 18 in main
                                                               File "/usr/local/bin/mellplayer", line 11 in <module>
                                    [1]    14984 abort (core dumped)  mellplayer

@moeinrahimi yes, the song API only supports the Chinese Mainland visit, or you may need to set the proxy yourself, you can see #6

@moeinrahimi This bug has been fixed and have a friendly show. You can see #8

authors: Mellcap moeinrahimi

repo: Mellcap/MellPlayer


text:
Documentation: detail docker-in-docker requirements

I'd recommend documenting the requirements for running this wrapper if you're already running meltano in docker. This is possible, but requires the /tmp directory to be mounted from the host to the meltano container.
This ensures that /tmp/config.json can be accessed, as the python script uses mktemp to create a directory in /tmp such as /tmp/tmp.BNlf296WXX, which can then be mapped down to the airbyte container. Due to the way docker-in-docker works, the volume mounts are mounts that exist on the host, not the meltano container, so it needs to be bind-mounted for it to show up in the airbyte image.

Hello!
Just want to add here that I had no issues with /tmp because looks like it's mounted automatically (works with docker in docker as well, as far as my implementation).
But I had issues with the user that runs everything, due to the UID / ownership and permissions, because apparently Airbyte images (at least for postgres) are using root user, so the container creates some files (the state file for instance) and the wrapper throws an error about permission (complains about being read only).
My workaround currently was to run meltano as root.
I'm not sure if this could also be your issue.

@sabino When I run meltano in docker, which then runs the tap-airbyte-wrapper, I specify the top-level docker run command myself. The Tap is mounting /tmp, but meltano needs to first have /tmp mounted, because it puts the config files into /tmp and then runs the docker run for the tap. I've verified this in a couple of environments, and the tap has no control over this.
Are you running meltano itself as a docker container, or running it directly?
I haven't hit permissions issues yet, but that seems to be in-line with what I'd expect in that instance, and it'll help me if I come to using the airbyte taps for postgres!

I'm running meltano outside docker in our production environment, but we also have a devcontainer setup in VScode that installs everything and since it's a container it runs meltano insider docker. So we have both setups, and both of them works.
Here is our current (partial, because I've omitted some things) implementation using tap-postgres (airbyte variant).

meltano.yml
version: 1
send_anonymous_usage_stats: false
env:
  MELTANO_SNOWPLOW_COLLECTOR_ENDPOINTS: []
include_paths:
- ./environments/*.meltano.yml
- ./extract/*.meltano.yml
- ./mappers/*.meltano.yml
- ./load/*.meltano.yml
- ./transform/*.meltano.yml
- ./orchestrate/*.meltano.yml
- ./utilities/*.meltano.yml

default_environment: dev

extract/extractors.meltano.yml
plugins:
  extractors:

  - name: tap-postgres
    variant: airbyte
  # Pointing to my fork temporarily (until PR gets merged)
    pip_url: git+https://github.com/sabino/tap-airbyte-wrapper.git

  # This is the LOG BASED Extractor
  # It requires Docker to work because it is
  # a wrapper around the airbyte CDC implementation
  - name: tap-postgres-log
    inherit_from: tap-postgres
    variant: airbyte
    pip_url: git+https://github.com/sabino/tap-airbyte-wrapper.git
    config:
      airbyte_spec:
        image: airbyte/source-postgres
        tag: 3.3.10
      airbyte_config:
        ssl_mode.mode: require
        replication_method.method: CDC
        replication_method.plugin: pgoutput
        replication_method.publication: ext__pub
        replication_method.replication_slot: ext__slot
      flattening_max_depth: 0
      docker_mounts:
      - type: bind
        source: /var/run/docker.sock
        target: /var/run/docker.sock
    select:
    - '*.*'
    metadata:
      '*':
        replication-method: LOG_BASED
        replication-key: _ab_cdc_lsn

  - name: tap__rds_db
    inherit_from: tap-postgres-log

extract/databases.meltano.yml
plugins:
  extractors:

  # Database X
  - name: raw__database_x
    inherit_from: tap__rds_db
    config:
      airbyte_config:
        database: database_x

load/loaders.meltano.yml
plugins:
  loaders:
  # Used to output things locally
  - name: target-local
    inherit_from: target-duckdb
    variant: jwills
    pip_url: target-duckdb~=0.4
    config:
      filepath: ${OUTPUT_DB_PATH}
      add_metadata_columns: true

  - name: target-bigquery
    variant: z3z1ma
    pip_url: git+https://github.com/z3z1ma/target-bigquery.git
    config:
      column_name_transforms:
        add_underscore_when_invalid: true
        lower: true
        quote: false
        snake_case: true
      cluster_on_key_properties: false
      credentials_path: ${GOOGLE_APPLICATION_CREDENTIALS}
      dataset: ${MELTANO_EXTRACT__LOAD_SCHEMA}
      project: ${BIGQUERY_PROJECT_ID}
      flattening_enabled: false
      flattening_max_depth: 0
      upsert: false
      overwrite: false
      denormalized: true
      method: storage_write_api
      schema_resolver_version: 2
      options:
        storage_write_batch_mode: true

With that I just set the PORT, USER and PASSWORD using env vars and usually set to the top level from the hierarchy (which I called tap-postgres-log in my case) if they are the same downstream.
Set HOST on tap__rds_db (and all other connections we have, I've omitted but we have a lot of instances we are reading from).
And just run:
meltano install
Test with:
meltano invoke raw__database_x --test
Extract with:
meltano run raw__database_x target-bigquery

I imagine we might be seeing a difference that devcontainer is hiding - perhaps it mounts /tmp by default?
I'm running meltano in AWS Batch (a layer over AWS ECS), which spins up the meltano/meltano:v3.2.0 docker image. In that, I need to mount /tmp, otherwise it doesn't work. In order to do that, I also need to be running on EC2 instances, but that's fine.
The same fix was needed for local - -v /tmp:/tmp, otherwise I get:
https://gist.github.com/alexmaras/58300ecaa3cecd83e53070ea84c3bb47
If I just add in -v /tmp:/tmp, everything works. This is because this wrapper uses /tmp to store the config and passes that to the docker container by mounting with -v /tmp:/tmp.
If that docker run is run within a container, the container is run on the host machine. However, if you didn't mount /tmp to the first container with docker run meltano, then the file won't be present on the host filesystem - it'll only be in the first containers' /tmp.

I added this env var in main, AIRBYTE_MOUNT_DIR so you can choose the directory inside the container that is mounted into. By default it is /tmp so behavior is unchanged unless you set this var.

authors: alexmaras sabino z3z1ma

repo: MeltanoLabs/tap-airbyte-wrapper


text:
Yaml, where for art thou Yaml???

After conda installing a yaml, we can't find our yaml:
Traceback (most recent call last):
  File "/Users/kevin.donkers/opt/miniconda3/envs/forestmaster/bin/forest-tutorial", line 5, in <module>
    from forest.tutorial.main import main
  File "/Users/kevin.donkers/opt/miniconda3/envs/forestmaster/lib/python3.7/site-packages/forest/__init__.py", line 33, in <module>
    from .config import *
  File "/Users/kevin.donkers/opt/miniconda3/envs/forestmaster/lib/python3.7/site-packages/forest/config.py", line 25, in <module>
    import yaml
ModuleNotFoundError: No module named 'yaml'

Do we need to install pyyaml instead?

Solved by conda installing pyyaml

repo: MetOffice/forest


text:
🛑 API MTTK IPFS is down

In 10e49b0, API MTTK IPFS (https://api.mttk.net/post/ipfs/QmSr94SdMEdCgGTKyJYTwMdVEzZ28sRiLqfQ7S7c2t8C5h) was down:

HTTP code: 0
Response time: 0 ms

Resolved: API MTTK IPFS is back up in 21a01f6.

repo: Meta-Network/upptime


text:
Conditional execution

Hey everyone,
Meta txes are supposed to be submitted to the network immediately by relayers. It'd be however possible to delay their execution, and make it conditional, e.g. on time, state or events. This could allow "automating" actions like revealing votes and bids, or claiming rewards, etc.
There are two main questions however:

Whether they can be added to the meta tx standard, with an acceptable complexity overhead. It'd be amazing to have insight from @kosecki123 or @lsaether on this.
Whether it's desirable to add them to this standard, or they should rather be a different standard.

TL;DR We discuss adding (uint conditionType, bytes condition) to executable signed messages, and employing these fields to enable meta txes conditioned on EVM events.
Note: Conditional execution is costlier in terms of gas, but this shouldn't add much overhead to non-conditional txes.
Modifications to executable signed messages
As there are multiple ways to make transactions conditional, including by time, by checking state or by occurence of events, in addition to the data necessary for specifying the condition, we could add a condition type, which specifies how to parse the condition data.
Condition type

ConditionType
Purpose

0x0
Not conditional (default)

0x1
Time-based condition

0x2
EventLog occurence

Condition data
For EventLogs, the condition could be the RLP-encoded concatenation of (address emitter, bytes32 eventTopic).
Relayer
Relayers would store conditional meta txes, and when the event specified by one of the meta txes is emitted, they compute a proof for the receipt that contains the event log, and send it along with the block header and index of log in receipt to the smart contract.
On-chain verification
For an incoming meta transaction which has a conditionType == 0x2:

Block header sent by relayer is parsed to get block number and receiptHash.
Hash of block header should be equal to blockhash(blockNumber).
Proof sent by relayer for receipt should be verified against receiptHash.
Log is extracted from receipt (according to logIndex).
emitter and eventTopic should match those of extracted log.
Smart contract executes meta transactions.

Example for verifying proof.

repo: Meta-tx/Harbour-MVP


text:
[Bug] clash meta for Android 应用包列表不能检测小米系统自带的app

Verify steps

[X] I have read the documentation and understand the meaning of all configuration items I have written, avoiding a large number of seemingly useful options or default values.
[X] I have not reviewed the documentation and resolve this issue.
[X] I have not searched the Issue Tracker  for the problem I am going to raise.
[X] I have tested with the latest Alpha branch version, and the issue still persists.
[X] I have provided server and client configuration files and processes that can reproduce the issue locally, rather than a desensitized complex client configuration file.
[X] I have provided the simplest configuration that can reproduce the error I reported, rather than relying on remote servers, TUN, graphical client interfaces, or other closed-source software.
[X] I have provided complete configuration files and logs, rather than providing only parts that I believe are useful due to confidence in my own intelligence.

Operating System
Android
System Version
MIUI 14.0.6
Mihomo Version
Clash Meta for
Android
2.10.1.Meta
Meta-Alpha-0c384b1-240
208
Configuration File
无

Description
设置 > 网络 > 访问控制应用包列表 无法看到小米自带的app，例如应用商店 com.xiaomi.market，而clash for Android可以看到
Reproduction Steps
打开 设置 > 网络 > 访问控制应用包列表 ，搜索应用商店
Logs
手机上不方便看，应该和问题无关

能解释一下为什么invalid吗

@shui-dun https://github.com/MetaCubeX/mihomo/issues/1049

repo: MetaCubeX/mihomo


text:
[Update Snap] Hedera Wallet

Checklist
All items in the list below needs to be satisfied.

[ ] Is the summary of the change documented in this ticket?
[ ] Has a MetaMask Snaps team member reviewed whether the changes need to be vetted?
[ ] If there are changes that need to be vetted, attach a description and the relevant fixes/remediations to this issue.
[ ] The corresponding pull request in this repo has been merged.

This update fixes an issue whereby sometimes, hbars couldn't be sent on mainnet due to a network issue, by changing how the Hedera client is imported and the update frequency of the network https://github.com/hashgraph/hedera-metamask-snaps/commit/0ef63b9176ef6686c39f8145806227c86e0af1e3
The new version is 0.1.3

repo: MetaMask/snaps-registry


text:
P2PK addresses

Hi,
Why is there no way to create an address from a P2PK script?
For example, how to transform this script
020e46e79a2a8d12b9b5d12c7a91adb4e454edfae43c0a0cb805427d2ac7613fd9 OP_CHECKSIG
into
1P3rU1Nk1pmc2BiWC8dEy9bZa1ZbMp5jfg
as displayed by a bitcoin core node.
GetDestinationAddress won't create it and it doesn't seem like there is a function to create one from the public key I can extract from the script.

That's because P2PK scripts were before than bitcoin addresses, that's why p2pk cannot be represented by bitcoin address. In fact, if you send bitcoins to that address 1P3rU1Nk1pmc2BiWC8dEy9bZa1ZbMp5jfg, you will not be able to spend it with the private key which your public key (020e46e79a2a8d12b9b5d12c7a91adb4e454edfae43c0a0cb805427d2ac7613fd9) was derived from.
Just to show were that bitcoin address come from:
Console.WriteLine(
    new Script("020e46e79a2a8d12b9b5d12c7a91adb4e454edfae43c0a0cb805427d2ac7613fd9 OP_CHECKSIG")
    .GetDestinationPublicKeys().First()
    .GetAddress(Network.Main);
    .ToString());

It you follow this code you will see that it exract the first public key in the script (the only one there) and then it hashes it and creates a p2pkh address!. By carefull with this.

It works thanks!

Just for the record: i didn't provided you a solution. I've just gave you an explanation about why that piece of code is 100% WRONG and can make you loose money (you shouldn't use it at all).

This code is simply to be able to display an address from a script and won't be used to create new addresses (and send money to them). I understand this is not a correct way to create addresses but it looks like this is the way bitcoin core chose to display old P2PK scripts.

authors: AntoineXBTO lontivero

repo: MetacoSA/NBitcoin


text:
Port seed data from bitcoin core

Wasabi wallet users using Tail OS and similars (sorry I don't remember the names) cannot connect to the bitcoin p2p network because NBitcoin is not able to discover peers using the DNS seeds given that those systems cannot have access to the clear net, only Tor connections are possible.
One of those cases was the trigger to create this issue: https://github.com/MetacoSA/NBitcoin/issues/977 however, recently other users have reported a the problem that they cannot use Wasabi: https://github.com/zkSNACKs/WalletWasabi/issues/5512
NBitcoin uses two mechanism to bootstrap the initial list of node:

DNS seeds and,
Fixed addresses

This PR simply imports the list of fixed addresses from bitcoin core which includes onion v2 and v3 addresses that can be used to connect to those and get more addresses.
@nopara73 is going to work in resolving dns lookups though Tor in case the application is using socks (Tor)

The code LGTM, utACK

Hi @NicolasDorier
Do the altcoins also need to update the seed data since the pnSeeds array is now converted differently?
I can send a PR to replace https://github.com/MetacoSA/NBitcoin/blob/master/NBitcoin.Altcoins/Groestlcoin.cs#L197-L283 with https://github.com/Groestlcoin/groestlcoin/blob/master/src/chainparamsseeds.h#L9-L104
Please advice

I think altcoin does not need to update it if nobody uses it. Those seeds are used for a very specific case, which, as far as I know, only Wasabi ever needed.

authors: NicolasDorier adamPetho gruve-p lontivero


text:
Implement tags that show which leaderboard a question is in

We used to have tags like these to show which leaderboard every question is, but now no longer do.

Working on this now

authors: lsabor ryooan

repo: Metaculus/metaculus


text:
Merge master + libnetwork-release

This branch is a version of libnetwork-release with master merged in.

Can one of the admins verify this patch?

LGTM

authors: calico-jenkins caseydavenport tomdee

repo: Metaswitch/calico-docker


text:
Do not use port 0 to mean all ports

Actually, this is valid and required for some protocols, but not tcp, sctp,
udp or udplite where the only way to specify a port of "any" is to give an
explicit port range.
Fixes bug #207.

@matthewdupre, are you OK to merge this now? No huge hurry to be honest, just keen to get it off the list.

repo: Metaswitch/calico


text:
Test PR

This is a test PR, to demo the PR functionality

Test PR no longer needed :slightly_smiling_face:

repo: MeteoSwiss-APN/spack-mch


text:
Solidify the implementation of adding new objects

Concerns #395, #483, #484
Adding new objects would be one of two things:

Adding new tag paths after RMB in the viewport
Inserting new path commands after RMB in the viewport or using the shortcuts

We need some special logic for adding tags or path commands at a position, the regular logic won't do:

Adding a new line at (x,y) should make it so the second handle is at (x + 1, y)
Adding a new curve path command at should generate the control points between the start and the end, similar to how Convert To currently behaves.

Moreover, this special logic needs to run every frame. Seemingly, we'll need to implement a temporary_add() kind of function in a lot of places, one that doesn't concern UndoRedo, but that still updates the text, until the object is really added at the end.
When it comes to cancelling these changes, I believe what we actually need is to solidify some logic for cancelling actions, which needs its own proposal.

Would be really good to get this right before the next alpha.

repo: MewPurPur/GodSVG


text:
Request: Drag and rearrange

I would like to request for an option to enable the dragging of rows to rearrange the array.
~ Great & essential addon, this definitely should be in core AOR in my opinion.

Second this feature request!

:+1:  for the feature request.
This month, unfortunately I don't have time to implement new features :disappointed:, but Pull requests are  always welcome :grin: .

authors: MhdSyrwan berge616 bfintal

repo: MhdSyrwan/aor-embedded-array


text:
Sandbox = relaxed on NixOS?

When running nixpkgs-review today, I noticed that the nix CLI it runs in the process includes --option build-use-sandbox relaxed.
I'm not sure whether it does anything because I haven't set myself as a trusted user but it's safe to say that this is rather unexpected.
https://github.com/Mic92/nixpkgs-review/pull/161 was supposed to disable it on Darwin but it actually adds those options on Linux. Was that intended @SuperSandro2000?

Before that PR it was set on all platforms and after it the option is only set on Linux because it does not work reliable on Darwin.

I see.
Why would nixpkgs-review want to weaken sandboxing on Linux though?

Right now it does not really change anything practically. We don't have the sandbox set to relaxed for any Linux nix package. There only 1-2 darwin builds in nixpkgs using it.

Fixed-output drvs run without sandboxing when relaxed. This isn't really a concern for r13y since their output is indeed fixed but might break some and could be a potential security issue.
Why does the sandbox need to be set different from the environment in the first place though?

The sandbox on darwin is not ready yet to be always enabled.

That's why it's disabled by default; in the environment. My question is why nixpkgs-review needs to change anything about that setting.

Fixed-output drvs run without sandboxing when relaxed. This isn't really a concern for r13y since their output is indeed fixed but might break some and could be a potential security issue.
Why does the sandbox need to be set different from the environment in the first place though?

afaik only if __noChroot is set https://github.com/NixOS/nix/blob/69eb65403ad3e877300a7c0c96411d9d9e27dc69/src/libstore/build/local-derivation-goal.cc#L416
which affects only two packages in nixpkgs.

That's why it's disabled by default; in the environment. My question is why nixpkgs-review needs to change anything about that setting.

It should be consistent for everyone. If someone happens to configured it's nix to use no sandbox it should be obvious. I am fine with enabling it on Linux again and keep it disabled on macOS. We only had the relaxed sandbox because someone wanted it on macOS in the first place.

Also please don't use nixpkgs-review on untrusted input. In a fixed input derivations it is possible to access the local network or do some other malicious stuff. Everything gets sourced in a nix-shell that also allows code execution without a sandbox.


text:
Use correct object in browser context

Fixes #2011 by not using the global object but rather the correct window object in the browser context of the module initialisation

Warnings

:warning:

Please include an updated CHANGELOG.md file.This way we can keep track of all the contributions.

  Generated by :no_entry_sign: dangerJS

authors: MagicMirrorBot rejas

repo: MichMich/MagicMirror


text:
Alternative description

A JS package built on Vue for building a docs site using a base index.html, a configured theme and all your pages as markdown files.

Docsify works great on GH Pages. It is an alternative to Jekyll though - you have to set a .nojekyll value to prevent the site rendering through Jekyll (same as if you have a React site built to a gh-pages branch using a build step, though Docsify doesn't need have a build step)
It supports some advanced things but generally I find I get a professional docs site than out writing any includes or layouts like one has to in Jekyll. (Yes you can use a theme in a Jekyll but I think every time I switch a theme something breaks or needs installing or configuring, docsify has 4 themes but it is only one line change to switch between them).
it is accessible as it doesn't need Ruby or Jekyll and you don't even need a local install step. Docsify gets fetched in the browser.

Docsify works great on GH Pages. It is an alternative to Jekyll though - you have to set a .nojekyll value to prevent the site rendering through Jekyll (same as if you have a React site built to a gh-pages branch using a build step, though Docsify doesn't need have a build step)
It supports some advanced things but generally I find I get a professional docs site than out writing any includes or layouts like one has to in Jekyll. (Yes you can use a theme in a Jekyll but I think every time I switch a theme something breaks or needs installing or configuring, docsify has 4 themes but it is only one line change to switch between them).
it is accessible as it doesn't need Ruby or Jekyll and you don't even need a local install step. Docsify gets fetched in the browser.

repo: MichaelCurrin/docsify-js-tutorial


text:
Gradle build error

Hello, my Gradle build crashes whenever using this library. Removing it fixed the issue.
Caused by: java.lang.ArrayIndexOutOfBoundsException
I am also using ProGuard 6.2.2

Hi @tommyzat and thank you for the report. Could you run the Gradle build with the follong command and send me gradle.log file:
./gradlew assembleDebug --info --stacktrace --console plain > gradle.log 2>&1

authors: MichaelRocks tommyzat

repo: MichaelRocks/paranoid