Pinned Column Overlap Non Pinned Column

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
I have both checkbox and row menu column pinned on left side but as you can see from the picture below my "Role" column gets bit of hidden behind row menu column.
Expected behavior 🤔
No need to explain!
Steps to reproduce 🕹

Context 🔦
No response
Your environment 🌎

`npx @mui/envinfo`
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://material-ui.com/r/issue-template-latest), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

It doesn't look like this bug report has enough info for one of us to reproduce it. Please provide a CodeSandbox (https://material-ui.com/r/issue-template-latest), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem. Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

I've attached the link of code


URLs and keys are hard-coded in some labs.

Can we update the Node lab to use either dotenv or something similar to provide environmental variables rather than hard-coding a default option? In particular this involves:

Lab 2, with the LUIS model URL
Lab 3, with the Azure Search information

Sure. Our plan was to remove the keys before releasing the labs and replace them with placeholders. However, using dotenv might be a better option.

https://github.com/GeekTrainer/help-desk-bot-lab/commit/66693abb857144279d65e9debf8ea4c620966c98
https://github.com/GeekTrainer/help-desk-bot-lab/commit/7d30a006fba6fc89abf2fbe285ed79bdcb0de931

👍


Recovery mechanism in stellar.AccountConfigurator

Currently in case of crash during account configuration, the process will not be resumed after restart.

Bifrost has been deprecated and removed.


Governance UI fixes

Hi @H34D , here are a few small UI fixes that aren't flow related and not urgent, but should be added at some point:
Create a Proposal (screenshot attached)

[x] 1. Please change warning message design
[x] 2. Please change Title and Description design  - grey box with dark text.
[x] 3.  Title and Description box isn’t scrollable - I can’t read whole description

Proposals table (screenshot attached)

[x] 1.  Please align date & time in proposal details to be "columns" as it is Zeplin

Thank you!

[ ]  There is a small bug - grey box doesn't reach the edge of the table

that is a duplicate of #334

originally in design the positions were supposed to be expandable and not scrollable table. Is this a mistake or it's something that was decided to be?

that is a duplicate of #285

fixed


Gradient Color & Background Color not converted when PPT to PDF converted

Hello, When i am trying to convert PPT to PDF, it is converted sucessfully but gradient color is not display in pdf & some times background is not converted. plz suggest me how to solve.

Hi nkarale
All conversions including Powerpoint are handled by third party open-source libraries which are not perfect by themselves. I have to apologise as I have limited control on the output.
I'm not sure about your operating system. If you are using Linux, you can use Libreoffice to handle the conversion instead like here.

Thanks for replying.. I have done in core java it is fine, but I have to developed for android some jar files are conflicts. Please help me, which jar files includes for this projects..

Err, I'm not sure if I understand. Are you using my library under Android?  I neglected to mention but the libraries I use may not be compatible with Android. Because for some of them, the libraries may create more objects than Dalvik can handle.
Can you screenshot the problem?


Licence

Just to be sure, does the "Stability AI Community License Agreement" apply to both the models and the inference code? What are the implications of that for the inference code?

We've updated the inference code to be MIT License :)


Dispaly error message in platform setting

We add two bcode errors in oam-dev/kubevela#3623
Please help to display the error message in FE.

12011: there is no dex connector, direct users to the integration management page.
14010: the admin email is empty, direct users to the user management page.


A number of changes focused on getting random polymer builds working

A number of changes to get random polymer builds working, plus a few other things that came up along the way.

examples/generate_random_structures/get_initial_structure.py is revised for building, including cleaning up some units issues. Torsion forces must be off, for some reason - it results in nan forces even when the torsion force constant (and resulting energies) are zero. However, the structures run fine with torsion potentials added in.   Seem to only be a problem at the beginning.

Several example .pdbs built with various numbers of backbone and sidechains
It is not particularly fast or efficient; when a monomer fails to place, it goes back to the beginning, and it probably should back up recursively instead.  But it's OK for builds < 30 for some patterns, and at least 10-12 for others within a few min.
For some reason, the build must be run with torsions off, or it will crash.

in cgmodel.py, some fixes to the get force parameter calls that were screwed up before, along with some extra format cleaning to make it more concise.
Most of the changes in utilities/util.py.  I tried to streamline in quite a bit and add in comments, and added a little randomness in the directions.  I removed some error outputting where it really shouldn't reach, and removed extra code in a few functions that wasn't being used (like the positions argument in the collisions helper function.

I kept the logic mostly the same for the random build, though removed some steps. Logic is explained better in comments there.
I'm sure this could be further cleaned up - this is just to the point that it can produce oligomers of different shapes for testing.
Many of the code paths have not really been touched.

Ah, yes, sb definitely a typo.  uploaded fix.

These changes look ok to merge.  I had the torsion force issue too, not sure what is causing that either. Most of the example structures built in a few tries - only the 12mer 2b2s was very slow for me (~80 attempts).
The algorithm fails for 3b3s, it is stuck after only 1 or 2 monomers. If we're running energy minimization and short MD anyway, my thought is to just build more complex chains in a fully extended conformation.

Also there is a crash if we set sidechain beads to 0.
Assigning particle positions for monomer #0 Traceback (most recent call last):   File "get_initial_structure.py", line 99, in <module>     random_positions=random_positions,   File "/projects/chwa2399/software/anaconda/envs/cg_openmm_5_29/lib/python3.6/site-packages/foldamers-1.12-py3.6.egg/foldamers/cg_model/cgmodel.py", line 390, in __init__     self.positions = get_random_positions(self, use_library=use_structure_library)   File "/projects/chwa2399/software/anaconda/envs/cg_openmm_5_29/lib/python3.6/site-packages/foldamers-1.12-py3.6.egg/foldamers/utilities/util.py", line 747, in get_random_positions     cgmodel.positions = trial_positions UnboundLocalError: local variable 'trial_positions' referenced before assignment srun: error: shas0606: task 0: Exited with exit code 1

I agree that building in fully extended is the next thing to do.  Now that we have a pseudorandom builder, then adapting it to make an extended builder may be the next thing.   I'll file an issue and assign it to you :)

Also there is a crash if we set sidechain beads to 0.

I'll take a look at that today and decide if we disallow that case, or adjust the code to make it build.  My instinct is to disallow for now, but leave it as an issue to potentially support in the future.  If it's easy to adjust, though, I'll add that.

Interestingly enough, n backbones / 0 sidechains works fine as long as n =/= 1 (tested up through 4), so for now, I'll probably just add an error message that explains how to get monomers.  We can always work with even numbers of monomers if we just have simple unbranched polymers.


Why is there a requirement that 'cvXX' feature has the same number of variants for all glyphs?

Quoting the spec:

Within each 'cvXX' feature, the number of variants should be identical for all glyphs.

That requirement seems to be peculiar, what is the rationale behind this and is there any implementation that actually enforce this requirement? I have built several fonts with cvXX features and hadn’t paid attention to this requirement, do I need to revise my fonts?

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

ID: 4da11419-0864-96ff-7f67-296680843fc1
Version Independent ID: 1d46dac1-d559-ce3e-2f6f-f47cf8cd9e0f
Content: Registered features, a-e (OpenType 1.8.4) - Typography
Content Source: typographydocs/opentype/spec/features_ae.md
Product: typography
GitHub Login: @PeterCon
Microsoft Alias: alib

I am very interested in this topic and hope it won't be forgotten. I suppose the purpose of this requirement is to encourage font makers to design rationally, so there should be matching variants on all design axes. An example posted in a discussion of my JuniusX font was the way Charis SIL handles v with hook, where there are matching variants for lowercase, uppercase, modifier, and small cap on cv62:
sub uni028B from [uni028B.StraightLft uni028B.StraightLftHighHook];
sub uni1DB9 from [uni1DB9.StraightLft uni1DB9.StraightLftHighHook];
sub uni01B2 from [uni01B2.StraightLft uni01B2.StraightLftHighHook];
sub uni028B.sc from [uni028B.StraightLft.sc uni028B.StraightLftHighHook.sc];

But I work in the Middle Ages, where the material doesn’t always cooperate. For example, the Medieval Unicode Font Initiative (MUFI) specification has upper- and lowercase variants of “Insular A,” but not of “Uncial A,” “Open-Top A,” etc. A designer could supply the missing variants so as to make the cvNN features correct, but that would be a little foolish, since the reason they don’t appear in the MUFI spec is that they don’t occur in medieval manuscripts, and so they would (probably) never get used.
I tied myself in knots trying to come up with a way to conform to the OpenType spec while dealing with the MUFI situation, and ended up pleasing no one—so for now JuniusX doesn’t conform to the OpenType spec. I’d like to know if the font will break in some future software environment.

The requirement is that for each input glyph in an individual cvxx feature, there should be the same number of output variant glyphs. The rationale is two-fold: a) the features are intended for variants of individual characters, not for sets of characters (for which the ssxx features would be appropriate), so are expected to be used for e.g. uppercase A and its diacritic forms, and not for both upper- and lowercase characters; and b) having the same number of variants for each input glyph in the feature allows for the feature to be applied across a body of text with the same enumerated variant producing predictable results on all glyphs affected by the feature.
If you find yourself dealing with characters that have different numbers of variants, that is an indication that they do not belong in the same Character Variant feature.

@khaledhosny Can you provide examples of your use of cvxx features with different numbers of variants for the input glyphs in a single cvxx feature? I’m having trouble understanding what sort of things would go into such a feature.
It may be that there is a gap between cvxx and ssxx—ignoring the practical issue of the limited number of registered ssxx features—in terms of design. The cvxx features are defined in terms of input—‘What character-related glyphs share one or more variant forms?’—, and the ssxx features are defined in terms of output—‘What set of non-character-related glyphs share a related variant form?’ There isn’t an obvious place to answer ‘What set of non-character-related glyphs share one or more variant forms?’

Thanks, John, this is very helpful. I was taking the most permissive possible understanding of this passage:

In practice, if a variation applies to a character in a bicameral script, then the casing-pair character may have the same variation. Also, Unicode includes pre-composed characters for certain base + mark combinations, hence a single abstract character may be incorporated into a number of Unicode characters. Therefore, a variation for a particular abstract character may be applicable to several related Unicode characters. The Character Variant features can be used for sets of related characters in these cases.

But it's going to be more complicated in some cases, and I have a concern about how all this is going to look to a user. For example, here are all the variants for Aa in the MUFI spec:

Now it appears that I should have three CVXX features for this system: one for case 1, where you have both an upper- and a lowercase variant, one for cases 2-5, where you have only lowercase variants, and one for cases 6-7, where you have only uppercase variants. It's going to look complicated to the end user.
But to be fair, what I've got now is also complicated, maybe irrational, and I care a good bit about your second rationale, allowing "for the feature to be applied across a body of text with the same enumerated variant producing predictable results on all glyphs affected by the feature."
There doesn't appear to be a solution lacking a downside to the problems presented by (e.g.) MUFI.

I think you only need two cvxx features: one for uppercase A with three variants and one for lowercase a with five variants. Yes, one of the variants in each case happens to be of similar form, but this doesn’t mean you must put them in the same feature, only that you could, all else being equal. In this case, I would say that the unequivalent variant sets overrides the option to put upper- and lowercase in the same cvxx feature.

Okay, that makes sense. So the A system might look like this:

By grouping variants that are part of case-pairs at the beginning of each sequence one can coordinate their indexes and introduce a little more rationality to the system.

is there any implementation that actually enforce this requirement?

It's a recommendation, not a requirement. As such, no implementation should ever be enforcing this.
The feature was recorded as having been registered by Microsoft, but it was originally requested by SIL. @tiroj has captured the gist of the reasoning behind the recommendation: When SIL was creating fonts with broad Latin coverage (Gentium, Doulos, etc.), they had glyph variants for several characters, including cases in which, say, "a" (my hypothetical) plus all of the precomposed accented forms had a systematic set of variants; or "b" and it's barred forms; etc. For sake of discussion, let me refer to these as shared-base sets. And they knew that, for some language's orthography some mix of these variants would be preferred, but they couldn't predict what languages might need what mix. So they wanted a set of features that could be defined  on a per-shared-base-set basis, with the feature(s) applied across entire documents. That way, e.g., "a" and any of its precomposed accented forms would get the appropriate variants throughout the document.
If anyone thinks the description of the features can be improved, please suggest wording.

Thanks, @PeterConstable, for the explanation, and for the interesting background re: SIL.
I don't know if there's a widely shared understanding of words like "should" in technical specifications. Several of us have misunderstood the sentence quoted by @khaledhosny above as stating a requirement, not a recommendation. Perhaps there would be less misunderstanding if it read, "It is recommended that the number of variants be identical for all glyphs within each 'cvXX' feature."

@PeterConstable Is it defined anywhere what the behaviour should be if the number of enumerated variants in a cvxx feature is not the same for the input glyphs in the lookup? So, for example, if these lower- and uppercase variants were included in a single cvxx feature

what would be the correct output if a block of text containing both |a| and |A| characters were selected and the character variant feature applied with the enumerated variant 4 or 5? Which form of the uppercase |A| should be displayed in that situation, the default form because there is no corresponding enumerated variant? or the enumerated variant 3 because that is the highest, closest enumerated variant for that character?

I don't know if there's a widely shared understanding of words like "should" in technical specifications... Perhaps there would be less misunderstanding if it read, "It is recommended..."

In general, I'd say there's a widely shared understanding: "should" is used for recommendations; requirements are typically stated with words like "must" or "shall". The OT spec consistently (AFAIK) uses "must" and "should" in these ways. Saying "it is recommended" for every recommendation would be verbose.

Is it defined anywhere what the behaviour should be if the number of enumerated variants in a cvxx feature is not the same for the input glyphs in the lookup?

If it's not stated in the feature description, or logically implied, then it's not defined anywhere.
IIRC, the idea SIL was after was that entire documents could be marked up to indicate particular alternates from particular 'cvXX' features. E.g., for 'cv01', use the fourth alternate throughout. Two lines of reasoning follow:

That would really only work if, in 'cv01', all of the starting glyphs have the same number of alternates and the alternates are consistently arranged—e.g., the fourth alternates of all glyphs are the same kind of alternate and should always co-occur.

The 'cvXX' feature description recommends use of type 3 lookups (alternate substitution). If for one starting glyph there are four or more alternates but for another starting glyph there are only three or less, what should be application do for the latter when the fourth alternate is being requested? The GSUB spec doesn't define what behaviour is expected. I suspect that's because it was assumed no app would ever request the nth alternate when n is past the last alternate. (I don't know whether it was assumed that type 3 lookups would always be accompanied by a glyph palette UI.)

In general, I'd say there's a widely shared understanding: "should" is used for recommendations

In this case no revision is necessary, if a recommendation is your intention. But you seem also to be saying that there is no defined behavior when a font doesn't follow the recommendation, so I wonder if it should be "must" or "shall."
In the cases @tiroj is talking about, Harfbuzz displays the default character instead of the last in the sequence, but I don't know about the other engines.

If a font was created with a different number of alternates within a given 'cvXX' feature, it could be workable if the content author knew the details and marked up individual runs as needed rather than the entire document. Still workable, but not the ideal.

It's sounding deeply inadvisable. This is the kind of guidance I was hoping for. Thanks!

In the cases @tiroj is talking about, Harfbuzz displays the default character instead of the last in the sequence, but I don't know about the other engines.

I think that is the most sensible approach and a good general principle: if the requested enumerated variant of a glyph is not available in the font, display the default form. This produces predictable results not only in the case under discussion here but also if a user changes to a different font.

Thanks everyone. I think I have now a clearer understanding of how cvXX features are supposed to be used. I think I was using them more like salt feature, which I know see would make them rather redundant.

To help clarify, the follow revision is proposed for OT 1.9:

Recommended implementation: A 'cvXX' lookup table maps the GID for the default form of a character to the GIDs for stylistic alternatives of that character. Each 'cvXX' feature uses alternate (GSUB lookup type 3) substitutions. (If there is only one variant for a character, a single-substitution lookup, type 1, can also be used.). A given 'cvXX' feature acts on a single glyph or on multiple glyphs for closely-related characters that have corresponding variants. Within each 'cvXX' feature, the number of variants should be identical for all glyphs, and the ordering of glyphs in lookup arrays should correspond such that the nth variants of all glyphs are corresponding variants.

Addressed in OpenType 1.9. Closing.


[SPARK-34647][CORE] Use ZSTD JNI NoFinalizer classes and bump to 1.4.8-7

What changes were proposed in this pull request?
This PR aims to use ZstdInputStreamNoFinalizer and ZstdOutputStreamNoFinalizer classes and upgrade ZSTD JNI to 1.4.8-7.
Why are the changes needed?
This improves the performance.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.

Test build #135823 has started for PR 31762 at commit 0192e3c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40405/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40405/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40405/

Test build #135823 has finished for PR 31762 at commit 0192e3c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135823/

The Jenkins passed and GitHub CI's Python failure is a known flaky one.

Could you review this again, @maropu and @viirya ?

Hi, @kiszk . Could you review this PR please?

Thank you, @kiszk and @viirya !

late lgtm


CB-14110 we shouldn't limit the custom template upgrades with the DH …

…upgrade entitlement
If the CDP_RUNTIME_UPGRADE_DATAHUB entitlement is granted we shouldn't limit the type
of customer templates that can be upgraded. Neither the version nor the type of services
should be limited.
See detailed description in the commit message.

This is a backport from master. The 2.48 branch was created slightly faster than it was merged.


500 internal error using PaaS, working fine on local

Hi!
I am developing a tool that takes songs of Youtube and creates a playlists in Spotify. I have run the application succesfully in local, but I get an error when I try it in Elastic Beanstalk, the PaaS of Amazon.
I am using a Flask server and the Spotipy python library. I think that the problem is related with the redirect_uri, but I have no idea of what I should do. I create two spotipy objects in my code. The first one, using Client Credentials Flow, works perfectly online. However, when I try to use another one with Authorization Code Flow, I get the error. I can even create it, but when I call to any function, even to search tracks, I get the 500 internal server error. I assume that the redirect_uri has to be the same url where the app is launched.
Thanks in advance!

Hi, does this help?  https://github.com/plamere/spotipy/blob/master/FAQ.md#how-do-i-obtain-authorization-in-a-headlessbrowserless-environment

Not really. I think that now it works locally because it has the token in the cache. Do you know how can I force to delete it?

TTthere should be a hidden file starting with .cache in your project folder. You can delete it using rm

Okay, I've gotten it to work in a bit of a "dirty" way. Calling SpotifyOAuth () I pass the variable cache_path = '. Mycache' to it, then I upload it to aws and it works, but I think this is just a temporary solution. I attach the link so you can see the work:
http://ys5-env.eba-mjmi37yf.eu-west-1.elasticbeanstalk.com/
Example videos that work:
https://www.youtube.com/watch?v=5lthiQoQiRA&t=2953s&ab_channel=HÖRBERLIN
https://www.youtube.com/watch?v=4utKO75DtBE&t=637s&ab_channel=BE-AT.TV
You can click the title and you will find a playlist with all the songs, you can click a song and the spotify link will open, you can move the mouse over the covers and it will be heard.

I'm not sure what bug you are describing. You should provide the code for a minimal reproducible example, current behaviour with a full stack trace of the 500 you get and behaviour you would expect.

I pass the variable cache_path = '. Mycache' to it, then I upload it to aws and it works, but I think this is just a temporary solution

I think you are right, it's not a good solution and could be improved.
What I've been doing in my own app is to persist new tokens into a DB and then read from that DB every time I need the token. See https://github.com/resident-archive/resident-archive/blob/a869b73f1f64538343be1604d43693b6165cc58a/functions/to-spotify/main.py#L129..L157
I'm going to close your issue as you found a temporary solution, and the improvement above can be discussed here https://github.com/plamere/spotipy/issues/51


Added new Game Smash Monty Mole

Project-Guidance! 🎊🎈
Welcome! 🎉
Thank you for visiting our repository! We're excited to have you here. If you find this project useful, please consider giving it a star! ⭐
🎉 Have you reviewed the Contributing Guidelines? 🤔 (Required)

[x] YES
[ ] NO

📝 Description
Added the dir of the game in intermediate folder of web dev directory.
The game involves clicking on randomly appearing moles to score points while avoiding randomly appearing piranha plants, as clicking on a plant ends the game. Moles and plants appear at random intervals on a 3x3 grid, and the score updates dynamically based on player actions.
🔧 Fixes #1379

🏷 Initiative Participation (Required)
This pull request is associated with the following initiative. Please choose the one you are contributing to:

[x] 🌸 GSSoC (Girl Script Summer of Code)
[x] 🌼 GSSoC 2024 Extd.
[x] 🍂 Hacktoberfest 2024
[ ] ❄ Script Winter of Code (SWoC)
[ ] ⛄ Winter of Blockchain (WoB)
[ ] 🙋♂ Personal
[ ] 📌 Other (please specify): _______________

so shld i make a new pr after doing the updated changes @Kushal997-das  ?


Force to string before using localeCompare

This follows the suggestion in #232, which seems sensible to me.

We may want to revisit it once we've figured out #231, but this certainly beats the current behavior.
Thanks for your contribution.


Request failed with status code 404 with REST API

Hello,

The following queries work fine using the Document API:

    const restClient = await createClient({
      astraDatabaseId: process.env.ASTRA_DB_ID,
      astraDatabaseRegion: process.env.ASTRA_DB_REGION,
      applicationToken: process.env.ASTRA_DB_APPLICATION_TOKEN
    });
    const basePath = `/api/rest/v2/namespaces/${process.env.ASTRA_DB_KEYSPACE}/collections/users`;
    const { data, status } = await restClient.get(`${basePath}`, {});

The equivalent requests should return the same results using basePath (where the members here is a table, and users is a collection):
const basePath = `/api/rest/v2/keyspaces/${process.env.ASTRA_DB_KEYSPACE}/members`;

The docs uses the path /collections/members which throws the error: Request failed with status code 404... right?
1- The first request returns only one document, shouldn't be returning all documents?

The following axios requests work fine for both queries (Document API & REST API):

    const axios = require('axios');
    //...

    let members = [];

    const instance = axios.create({
      // Document API
      // baseURL: `https://${process.env.ASTRA_DB_ID}-${process.env.ASTRA_DB_REGION}.apps.astra.datastax.com/api/rest/v2/namespaces/${process.env.ASTRA_DB_KEYSPACE}/collections/`,
      // REST API
      baseURL: `https://${process.env.ASTRA_DB_ID}-${process.env.ASTRA_DB_REGION}.apps.astra.datastax.com/api/rest/v2/keyspaces/${process.env.ASTRA_DB_KEYSPACE}/`,
      timeout: 30000,
      headers: {
        'X-Cassandra-Token': process.env.ASTRA_DB_APPLICATION_TOKEN,
        'Content-Type': 'application/json'
      }
    })

    // members = await instance.get('users') // Document API (only one document returned)
    // members = await instance.get('users/5ea53e52-dd0c-49af-82c2-f3e210530e2f') // Document API
    members = await instance.get('members/5ea53e52-dd0c-49af-82c2-f3e210530e2f') // REST API
      .then((results) => {
        return results.data;
      });

2- Where users is a document (no predefined schema), and members is a cassandra table (schema previously defined), however, in both queries there is no way to get the list of collection (or rows), they always return only the first document (unless the id specified), is there any way to retrieve all rows?
P.S. The results.data contains data as an array of object, so we you must use result.data.data to get the array back from results which is weird, is that behavior expected?
Regards

Heya, when querying document collections that haven't been written to yet, you will get a 404.
The default page size from the GET is 1, so that is why you are only seeing one result. You can increase this with the url parameter page-size=20
result.data.data is expected, the request body has the data wrapped in a key called data. You can remove this if desired with the url parameter raw =true
Have a nice day!

Thank you Chris, the only tricky param was page-state not really obvious one!


Firedrake-Netgen: Curved mesh creation sometimes fails in parallel

MFE below:
from firedrake import *
from firedrake.output import VTKFile
from netgen.occ import *

box = Box(Pnt(0, 0, 0), Pnt(1, 1, 1))
body = box.MakeFillet(box.edges, 0.1)
geo = OCCGeometry(body)
ngmesh = geo.GenerateMesh(maxh=0.1)
mesh = Mesh(Mesh(ngmesh).curve_field(2))
VTKFile("mesh.pvd").write(mesh)

Running this code in serial, the mesh is created with no issues.
But running it in parallel (e.g. mpiexec -n 2 python3 test.py) results in the following warning:
firedrake:WARNING Not able to curve element 4724, residual is: 0.18171646033208677

So it seems some of the elements are not being curved in this case.

The fix is two-parted. You need to use PR #29 and the Netgen MR mirrored here.
Also, you need to change your code:
from firedrake import *
from firedrake.output import VTKFile
from netgen.occ import *
import netgen

if COMM_WORLD.rank == 0:
    box = Box(Pnt(0, 0, 0), Pnt(1, 1, 1))
    body = box.MakeFillet(box.edges, 0.1)
    geo = OCCGeometry(body)
    ngmesh = geo.GenerateMesh(maxh=0.1)
else:
    ngmesh = netgen.libngpy._meshing.Mesh(3)
mesh = Mesh(Mesh(ngmesh).curve_field(2))
VTKFile("mesh.pvd").write(mesh)


Write boundary ghosts in plot files

This ensures that the boundary ghosts are written to the plot files so that they can restart as for checkpoint files (e.g. for post-processing).
In principle, only the boundary ghosts need to be written (the others can be filled via a ghost exchange) but this amendment writes them all. This is somewhat inefficient and we may want to change it in the future, but the performance hit is not significant so the effort required to do it properly outweighed the potential gain :-) !

Before I approve this, do you think it's worth adding an [optional] parameter [with a default argument] specifying whether you want to output plot ghosts or not?

Yes, this is a good suggestion. I think it should probably be defaulted to on though, as without them you get segfaults in the postprocessing tool. Do you want to add this?

Done!

Ah very nice solution! Ok, if you want to approve and merge this go ahead :-)


Update grpcio dependency to include future versions

Fixes #72

Yes I was gonna suggest a change just like this to prevent this issue again.
Thanks


Fix broken links

This PR fixes broken links.
Checklist

[x] I've added at least one test that validates that my change is working, if appropriate
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

Thanks, @taka1068! This was addressed in #1.


Create Test.md

Temp

Docs Build status updates of commit 277a8c1:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/media/AccessabilityByDesign/Test.md
:warning:Warning
View
Details

Community/media/AccessabilityByDesign/Test.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 1, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 1, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 1, Column 1: [Suggestion-manager-missing] Missing required attribute: 'manager'. Add a valid Microsoft alias for the author's manager.
Line 1, Column 1: [Suggestion-audience-missing] Missing required attribute: 'audience'.
Line 1, Column 1: [Suggestion-ms-topic-missing] Missing required attribute: 'ms.topic'. Add a valid value to indicate the article type.
Line 1, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 31c7917:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/media/AccessabilityByDesign/Test.md
:warning:Warning
View
Details

Community/media/AccessabilityByDesign/Word Options.png
:white_check_mark:Succeeded
View

Community/media/AccessabilityByDesign/Test.md

Line 0, Column 0: [Warning-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
Line 1, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 1, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 1, Column 1: [Suggestion-manager-missing] Missing required attribute: 'manager'. Add a valid Microsoft alias for the author's manager.
Line 1, Column 1: [Suggestion-audience-missing] Missing required attribute: 'audience'.
Line 1, Column 1: [Suggestion-ms-topic-missing] Missing required attribute: 'ms.topic'. Add a valid value to indicate the article type.
Line 1, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 4873f39:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/media/AccessabilityByDesign/Word Options.png
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Update owners

remove github handles that moved on
add owners for /sdk/maps

/check-enforcer override


Create codeql-analysis.yml

Fixes Issue
Fixes #49

Changes proposed

[x] Added a code scanning workflow.

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] My Code require change in the github actions.
[ ] I have updated the github actions accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

@khushalbhardwaj-0111 fix this error in deployment.


Add documentation for io.cilium/shared-service

The current clustermesh documentation doesn't describe the shared-service annotation or how it can be used. The code comments describe what it does, but users are not likely to look there. It would likely make sense to add a short section to address this in the docs.

Hi @joestringer, I would like to take this up. Can you please point me to the code section?

Awesome, @chowmean ! Here's the relevant code (found via git grep shared-service):
https://github.com/cilium/cilium/blob/cf5f475eab64680045bdce05da4274fcbe077c7e/pkg/annotation/k8s.go#L56-L61


added probability distribution for displaced thermal distribution

adding the probability distribution for a displaced thermal distribution. Taken from this paper

Re n_alpha: NB what @JackMTB has here is consistent with what we do elsewhere in this file so is fine by me!

Haven't looked at the tests, but otherwise fine from my side.


[MM-45758] Change verbiage of post-downgrade banner

Summary
Change verbiage from Your trial has ended. Upgrade to regain access to paid features to Your workspace now has restrictions and some data have been archived
Ticket Link
https://mattermost.atlassian.net/browse/MM-45758
Related Pull Requests

Has server changes (please link here)
Has mobile changes (please link here)

Screenshots
incoming, having env issues since coming back from PTO.
Release Note

None

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.


Can't use Chinses input in terminal

Environment
Windows build number: [run "ver" at a command prompt]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Expected behavior

Actual behavior

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.239]
Windows Terminal version (if applicable):

Any other software?
Microsoft Pinyin
Sogou Pinyin

Steps to reproduce
1、open the terminal
2、choose cmd or powershell
3、input something

Expected behavior

Actual behavior

This is a dupe of #2213


Clean up load test from huge-serivce variables

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Huge-service related variables are removed from the load test. This PR is a successor to https://github.com/kubernetes/perf-tests/pull/1975.
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
/assign @mborsz
Does this PR introduce a user-facing change?:

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/lgtm


Show all possible information for inputs && outputs

Currently wallet only shows very basic information for inputs and outputs.
Another function that would show all that lwk produces for transaction inputs and outputs would be a great addition.
One example of the information that could be shown is
      {
        "asset": "144c654344aa716d6f3abcc1ca90e5641e4e2a7f633bc09fe3baf64585819a49",
        "asset_bf": "4ca6956f687d9f9782f66b1c1bd7fca4f00dcb223b284709cbe2231504635ecf",
        "redeem_script": "00149d5600b470f19766b5e274593032ff95ec89dcaf",
        "txid": "57a4eeffc0661bc1c1d8d17991c3b2873e5d71fccc1bb0bb56066e84c6cd2a5b",
        "value": 9500,
        "value_bf": "6004bdb33395f514d8eff59a68dbd8020c5c0e9898bab1add1d5063edfc45772",
        "vout": 2
      }

(this is what sideswap requires for them to produce a pset as shown in https://sideswap.io/docs/#uploading-swap-inputs)

Hey! I have made some notes to help understand how the entire project is structured:
https://github.com/SatoshiPortal/lwk-dart/blob/trunk/docs/structure.md
Currently, as a contributor you will not be able to build binaries (even for unit-tests). You can however there are a few manual steps to get them to work in dart.
You can still make a significant contribution by focussing just on adding functionality to the api.rs file and types.rs, running codegen, ensure that there are no errors in rust or dart and finally updating root.dart to create the final dart class.
It would also help if you could just write some tests in rusts that show what functionality you require from lwk, and for now I can take care of the rest for you until you get familiarized with the library and we have a better process for contributors to complete the whole flow.

in api.rs at the bottom you will find the test module:
#[cfg(test)]
mod test {
    use elements::{Address, AddressParams};

    use super::*;
    #[test]
    fn test_api(){
    }

    // create a new function

    fn test_new_functions(){
    // use lwk here and make comments on exactly what you require
    }

This would be a great start and I should be able to bind your requirements into dart for now.

#[derive(Clone, Debug, PartialEq)]
pub struct OutPoint {
    pub txid: String,
    pub vout: u32,
}

#[derive(Clone, Debug, PartialEq)]
pub struct TxOut {
    pub script_pubkey: String,
    pub outpoint: OutPoint,
    pub height: Option<u32>,
    pub unblinded: TxOutSecrets,
}

#[derive(Clone, Debug, PartialEq)]
pub struct TxOutSecrets{
    pub value: u64,
    pub value_bf: String,
    pub asset: String,
    pub asset_bf: String,
}

#[derive(Clone, Debug, PartialEq)]
pub struct Tx {
    pub timestamp: u32,
    pub kind: String,
    pub balances: Balances,
    pub txid: String,
    pub outputs: Vec<TxOut>,
    pub inputs: Vec<TxOut>,
    pub fee: u64,
}

impl From<WalletTx> for Tx {
    fn from(wallet_tx: WalletTx) -> Self {
        let mut outputs: Vec<TxOut> = Vec::new();
        let mut inputs: Vec<TxOut> = Vec::new();

        for output in wallet_tx.outputs {
            if output.is_some() { // safe to unwrap
                let script_pubkey = output.clone().unwrap().script_pubkey;
                let amount = output.clone().unwrap().unblinded.value;
                outputs.push(TxOut {
                    script_pubkey:script_pubkey.to_string(),
                    height: output.clone().unwrap().height,
                    unblinded: TxOutSecrets {
                        value: output.clone().unwrap().unblinded.value,
                        value_bf: output.clone().unwrap().unblinded.value_bf.to_string(),
                        asset: output.clone().unwrap().unblinded.asset.to_string(),
                        asset_bf: output.clone().unwrap().unblinded.asset_bf.to_string(),
                    },
                    outpoint: OutPoint {
                        txid: output.clone().unwrap().outpoint.txid.to_string(),
                        vout: output.clone().unwrap().outpoint.vout,
                    } ,
                })
            }
        }

        for input in wallet_tx.inputs {
            if input.is_some() { // safe to unwrap
                let script_pubkey = input.clone().unwrap().script_pubkey;
                let amount = input.clone().unwrap().unblinded.value;
                inputs.push(TxOut {
                    script_pubkey:script_pubkey.to_string(),
                    height: input.clone().unwrap().height,
                    unblinded: TxOutSecrets {
                        value: input.clone().unwrap().unblinded.value,
                        value_bf: input.clone().unwrap().unblinded.value_bf.to_string(),
                        asset: input.clone().unwrap().unblinded.asset.to_string(),
                        asset_bf: input.clone().unwrap().unblinded.asset_bf.to_string(),
                    },
                    outpoint: OutPoint {
                        txid: input.clone().unwrap().outpoint.txid.to_string(),
                        vout: input.clone().unwrap().outpoint.vout,
                    } ,
                })
            }
        }
        Tx {
            kind: wallet_tx.type_,
            balances: Balances::from(AssetIdMapInt(wallet_tx
                .balance)),
            txid: wallet_tx.tx.txid().to_string(),
            outputs: outputs,
            inputs: inputs,
            fee: wallet_tx.fee,
            timestamp: wallet_tx.timestamp.unwrap(),
        }
    }
}

Just updated the Transaction struct to more closely align with : https://docs.rs/lwk_wollet/latest/lwk_wollet/struct.WalletTx.html

Will have to add suport to convert script_pubkey to address as a separate struct. Will do that in the next release.

Issue done


Fetch up to date Dune statistics

Without using their API due to costs.

The statistics are here: https://dune.com/davy42/turkiye-earthquake-donations
I'm going to close this one as I don't think their API would worth the price.


Gcs filesystem test part 1

@mihaimaruseac
This PR ports some tests from //tensorflow/core/platform/cloud:gcs_file_system_test

Internal build (clang compiler) fails with
tensorflow/c/experimental/filesystem/plugins/gcs/gcs_filesystem.cc:456:7: error: field 'block_size' will be initialized after field 'block_cache_lock' [-Werror,-Wreorder-ctor]
      block_size(block_size),
      ^
1 error generated.

The initializers on a constructor must come in the same order as the class members are declared

Thank you !


bug: nginx-ingress migrate to apisix-ingress problem

Issue description
apisix-ingress is different from nginx-ingress in the same ingress.yaml. the issue is different path translation:

In nginx-ingress, "path: /" means "path: /" and "path: /*"
we can access http://url/aaa
In apisix-ingress,"path: /" means "path: /" only.
we can't access http://url/aaa, and got a error msg"{"error_msg":"404 Route Not Found"}"

Environment
[root@man01 kubesphere]# kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.4", GitCommit:"e87da0bd6e03ec3fea7933c4b5263d151aafd07c", GitTreeState:"clean", BuildDate:"2021-02-18T16:12:00Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.4", GitCommit:"e87da0bd6e03ec3fea7933c4b5263d151aafd07c", GitTreeState:"clean", BuildDate:"2021-02-18T16:03:00Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
[root@man01 kubesphere]# uname -a
Linux man01 5.4.132-1.el7.elrepo.x86_64 #1 SMP Wed Jul 14 07:42:43 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux
[root@man01 kubesphere]# kubectl get deployments.apps -n ingress-apisix  -o wide
NAME                        READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS           IMAGES                                   SELECTOR
apisix                      3/3     3            3           69m   apisix               apache/apisix:2.9-alpine                 app.kubernetes.io/instance=apisix,app.kubernetes.io/name=apisix
apisix-dashboard            1/1     1            1           59m   apisix-dashboard     apache/apisix-dashboard:2.8              app.kubernetes.io/instance=apisix-dashboard,app.kubernetes.io/name=apisix-dashboard
apisix-ingress-controller   1/1     1            1           69m   ingress-controller   apache/apisix-ingress-controller:1.2.0   app.kubernetes.io/instance=apisix,app.kubernetes.io/name=ingress-controller
Minimal test code / Steps to reproduce the issue
1.Apply the the same ingress.yaml with annotations: apisix
kind: Ingress
apiVersion: extensions/v1beta1
metadata:
name: nginx-8y63fw
namespace: dev
labels:
app.kubernetes.io/instance: nginx-8y63fw
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: nginx
app.kubesphere.io/instance: nginx-8y63fw
helm.sh/chart: nginx-1.3.5
annotations:
kubernetes.io/ingress.class: apisix
kubesphere.io/creator: admin
meta.helm.sh/release-name: nginx-8y63fw
meta.helm.sh/release-namespace: dev
spec:
rules:
- host: nginx.local
http:
paths:
- path: /
pathType: ImplementationSpecific
backend:
serviceName: nginx-8y63fw
servicePort: http

curl different url between apisix-ingress and nginx-ingress
（1）In apisix-ingress
[root@man01 kubesphere]# kubectl get svc -A | grep gate
ingress-apisix                 apisix-gateway                               NodePort       <IP_ADDRESS>           80:6208/TCP                       72m

[root@man01 kubesphere]#  curl http://<IP_ADDRESS>/ -H 'host: nginx.local'

Welcome to nginx!

Welcome to nginx!
If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.
For online documentation and support please refer to
nginx.org.
Commercial support is available at
nginx.com.
Thank you for using nginx.

[root@man01 kubesphere]#  curl http://<IP_ADDRESS>/aaa -H 'host: nginx.local'
{"error_msg":"404 Route Not Found"}
(2)in nginx-ingress
[root@man01 kubesphere]#  curl http://<IP_ADDRESS>/ -H 'host: nginx.local'

Welcome to nginx!

Welcome to nginx!
If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.
For online documentation and support please refer to
nginx.org.
Commercial support is available at
nginx.com.
Thank you for using nginx.

[root@man01 kubesphere]#  curl http://<IP_ADDRESS>/aaa -H 'host: nginx.local'

404 Not Found

404 Not Found
nginx/1.19.2

apisix-dashboard
1.show route setting
{
  "uri": "/",
  "name": "ingress_nginx.local_/",
  "desc": "Created by apisix-ingress-controller, DO NOT modify it manually",
  "host": "nginx.local",
  "upstream_id": "f763ff22",
  "labels": {
    "managed-by": "apisix-ingress-controller"
  },
  "status": 1
}
2. show upstream setting

@macaty ImplementationSpecific path type is not handled specially, you may try to use the Prefix.

thnx

close issue now, feel free to reopen.


more friendly error message(s) when offline

Testing #141296
When I am offline and search the marketplace, I get the message Error while fetching extensions. XHR failed.  We know we are offline, suggest to have a friendlier error message here.
Unable to search the Marketplace when offline, please check your connection. or something like that.

@joaomoreno / @deepak1556 Is there an API to know if VS Code is offline?
At present, the internal request service does not provide any info about this.

In the renderer process you can use the navigator.onLine property and in the main process you can use net.isOnline method.

I see this in insiders.vscode.dev (PWA and web) still:

It works for me in insiders.vscode.dev - I turned off wifi for eg.,


A calculator to find all deciles of given list of numbers

I want to add a calculator to find all deciles of a list of numbers

Go ahead
Deadline 22 May,2021


Add utils.invalidate_cached_property()

Sometimes you need to invalidate your cached properties. This makes it possible.

Makes sense, looks good. I just released 0.15, so you'll need to rebase this and move the changelog to the 1.0.0 section.

@davidism: rebased!


GitHub Flavored Markdown

The markdown preview window doesn’t render some GitHub Flavoured Markdown properly.
Roses are red
Violets are blue
In Atom, these lines don’t break, which is correct Markdown behaviour but not correct GitHub Flavoured Markdown behaviour.
Furthermore, references are not being auto-linked.

SHA: a5c3785ed8d6a35868bc169f07e40e889087fd2e
User@SHA: jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e
User/Repository@SHA: jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e
#Num: #26
GH-Num: GH-26
User#Num: jlord#26
User/Repository#Num: jlord/sheetsee.js#26

This issue was moved to atom/markdown-preview#201


feat: Improve native explain

Which issue does this PR close?

N/A
Rationale for this change

I wanted to improve the developer experience when viewing the native plans.
What changes are included in this PR?

Add a new config specifically for enabling the native explain feature
Improve CometScan output to show the source of the scan e.g. parquet read, or broadcast/shuffle (ScanExec: source=[BroadcastExchange (unknown)])

Here is example output:
ProjectionExec: expr=[col_0@0 as col_0], metrics=[output_rows=1, elapsed_compute=625ns]
  ProjectionExec: expr=[col_0@1 as col_0, col_0@0 as col_0], metrics=[output_rows=1, elapsed_compute=1.542µs]
    HashJoinExec: mode=Partitioned, join_type=Inner, on=[(col_0@0, col_0@0)], metrics=[output_rows=1, input_batches=1, build_input_rows=5, build_input_batches=5, input_rows=1, output_batches=1, build_mem_used=992, join_time=478.875µs, build_time=898.125µs]
      CopyExec, metrics=[output_rows=5, elapsed_compute=32.123µs]
        ScanExec: source=[BroadcastExchange (unknown)], schema=[col_0: Int32], metrics=[output_rows=5, elapsed_compute=10.999µs]
      CopyExec, metrics=[output_rows=1, elapsed_compute=4.666µs]
        FilterExec: col_0@0 IS NOT NULL, metrics=[output_rows=1, elapsed_compute=14.792µs]
          ScanExec: source=[CometScan parquet  (unknown)], schema=[col_0: Int32], metrics=[output_rows=1, elapsed_compute=1.542µs]

How are these changes tested?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 33.70%. Comparing base (c4bd3db) to head (339b551).
Report is 2 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #795      +/-   ##
============================================
- Coverage     33.74%   33.70%   -0.04%
- Complexity      856      869      +13
============================================
  Files           112      112
  Lines         42730    42845     +115
  Branches       9435     9436       +1
============================================
+ Hits          14419    14442      +23
- Misses        25331    25427      +96
+ Partials       2980     2976       -4

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


Drill 4236: ExternalSort should use the new allocator functionality to better manage it's memory usage

@StevenMPhillips can you please review ?

+1 LGTM

Thanks @StevenMPhillips , I will squash the commits, run one final round of tests and commit to master


langsmith 0.0.39

Current package info

Channel
Downloads
Version
Platforms
License

conda-forge

Changelog: https://github.com/langchain-ai/langsmith-sdk/releases
License: https://github.com/langchain-ai/langsmith-sdk/blob/v0.0.39/LICENSE
Requirements: https://github.com/langchain-ai/langsmith-sdk/blob/v0.0.39/python/pyproject.toml
Actions:

Clean up noarch python
Add --no-deps --no-build-isolation to script
Update in run: pydantic >=1.0.0,<3.0.0
Fix doc_url

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:22: missing_wheel: For pypi packages, wheel should be present in the host section
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:22: missing_wheel: For pypi packages, wheel should be present in the host section
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:22: missing_wheel: For pypi packages, wheel should be present in the host section
Errors were found


Update google-cloud-pubsub to 1.123.17

About this PR
📦 Updates com.google.cloud:google-cloud-pubsub from 1.107.0 to 1.123.17
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-pubsub" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.cloud", artifactId = "google-cloud-pubsub" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #355.


add data deploy

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

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

🛡 Security Policy

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

📝 Describe your problem
my example

github
deploy use deta

step:

git clone
npm run setup
use webstorm_rebuild_movefile -> /index.js
add deta.json

but
Bad Gateway
The micro ran into an error while processing the request.

If you are the owner of the micro, please check your logs.

🐻 Uptime-Kuma Version
latest
💻 Operating System and Arch
macos
🌐 Browser
chrome latest
🐋 Docker Version
No response
🟩 NodeJS Version
18 lts

Hope to add this deployment scheme

Can you add a function? For example, I have a Web service. I can link directly through the intranet, but I want to share the extranet links with others. Repeated addition will be a bit messy.

I can share the status page with my friends, so there is the possibility that the other person wants to visit my website, but visiting from the intranet can reduce some network broadband consumption.


fix(table): 修复数据变化时,吸底滚动条位置没有变化的问题

🤔 这个 PR 的性质是？

[x] 日常 bug 修复
[ ] 新特性提交
[ ] 文档改进
[ ] 演示代码改进
[ ] 组件样式/交互改进
[ ] CI/CD 改进
[ ] 重构
[ ] 代码风格优化
[ ] 测试用例
[ ] 分支合并
[ ] 其他

🔗 相关 Issue

#1437
💡 需求背景和解决方案

📝 更新日志

fix(table): 修复数据变化时,吸底滚动条位置没有变化的问题

[ ] 本条 PR 不需要纳入 Changelog

☑ 请求合并前的自查清单
⚠ 请自检并全部勾选全部选项。⚠

[x] 文档已补充或无须补充
[x] 代码演示已提供或无须提供
[x] TypeScript 定义已补充或无须补充
[x] Changelog 已提供或无须提供

Codecov Report

Merging #1535 (76a123a) into develop (492d477) will increase coverage by 3.99%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #1535      +/-   ##
===========================================
+ Coverage    57.94%   61.94%   +3.99%
===========================================
  Files          407      655     +248
  Lines        15371    15835     +464
  Branches      2931     2826     -105
===========================================
+ Hits          8907     9809     +902
+ Misses        6187     5735     -452
- Partials       277      291      +14

Impacted Files
Coverage Δ

src/range-input/range-input-popup-props.ts
25.00% <0.00%> (-75.00%)
:arrow_down:

src/grid/row-props.ts
71.42% <0.00%> (-28.58%)
:arrow_down:

src/select/util.ts
65.00% <0.00%> (-26.67%)
:arrow_down:

src/select/props.ts
54.54% <0.00%> (-20.46%)
:arrow_down:

src/date-picker/props.ts
53.84% <0.00%> (-16.16%)
:arrow_down:

src/date-picker/date-range-picker-props.ts
42.85% <0.00%> (-11.69%)
:arrow_down:

src/select/optionGroup.tsx
31.57% <0.00%> (-9.60%)
:arrow_down:

src/cascader/props.ts
55.55% <0.00%> (-8.74%)
:arrow_down:

src/upload/dragger.tsx
27.27% <0.00%> (-7.51%)
:arrow_down:

src/cascader/cascader.tsx
56.89% <0.00%> (-7.11%)
:arrow_down:

... and 440 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Docker compatible spec options.

Currently containerd default spec is mounting /run as tmpfs.
However, this may break the compatibility with docker, the newly mounted /run will probably overwrite the original content inside the image.
Forked from https://github.com/containerd/containerd/pull/1333#issuecomment-321833241.
We may want a group of docker compatible spec option settings, e.g.:
GenerateSpec(dockercompat.WithDockerDefault, dockercompat.WithPrivileged)

@mlaventure should we create a separate repo under the containerd org, for now, and move some of the compatibility Opts into it?
cc @stevvooe @dmcgowan

@crosbymichael sgtm until Docker/moby can figure out where they want this to be

@crosbymichael @stevvooe
That new repo might be good to add importer for docker save as well? (https://github.com/containerd/containerd/issues/1229)

Should we name the repo github.com/containerd/compat ? Then it could have subdirs with docker and other things like that?

I think we have solved a lot of this with the apparmor and seccomp packages as well as the oci spec package.
I don't think this should be address in the containerd core for many of these docker specific options, we will just have to wait and see how Docker refactors some of these in the repo to take advantage of them.


fix: Fixing test_spectrum_decimal_cast test

Feature or Bugfix

Bugfix

Detail

Fixing test_spectrum_decimal_cast test. It was failing due to an issue where the indices for both rows in the Frame were 0 when running in distributed mode.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 40dafe225d41244da20d4be58d5d0f740eb214c0
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 40dafe225d41244da20d4be58d5d0f740eb214c0
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 68b8fa7f6c77c50c155869698a035bac0269fef5
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 68b8fa7f6c77c50c155869698a035bac0269fef5
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


gradle syntax breaks preview

Reproduction steps

Put this in some .mdx file:

 ```gradle
  buildscript {
    // ...
  }
  ```

Try to open that .mdx file using Local Preview feature. It should not work.

This is similar to #232
I think some error reporting should be present. I understand that not all file formats are handled, but the current experience of Preview silently failing is really not intuitive.

Thanks will take a look - we're in the process of updating the internals and will put some form of error alert system in place.

Weirdly there is no syntax highlighting for gradle: https://github.com/shikijs/shiki/blob/main/docs/languages.md#all-languages

We'll have to figure out a nicer way to handle these error messages - bit tricky as they can arise from many places.

Weirdly there is no syntax highlighting for gradle: https://github.com/shikijs/shiki/blob/main/docs/languages.md#all-languages

I copy-pasted the gradle snippet from integration_test's README, and it's somewhat syntax-highlighted there.

Gradle is groovy on Shiki, maybe we can alias gradle -> groovy


32 misleading field name weo estimates

This pull request includes changes to update the version and fix field names in the WEO importer. The most important changes include updating the version in pyproject.toml, modifying the CHANGELOG.md, and renaming a misleading column in the WEO importer and its corresponding test.
Version update:

pyproject.toml: Updated the version from 0.1.1 to 0.2.0.

Changelog update:

CHANGELOG.md: Added a new entry for version 0.2.0 to document the fix for field names in the WEO importer.

Field name fixes:

src/bblocks_data_importers/imf/weo.py: Renamed the column estimates_start_year to last_actual_date to fix misleading field names.
tests/test_imf/test_weo.py: Updated the test to reflect the renaming of the column estimates_start_year to last_actual_date.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.51%. Comparing base (b60340d) to head (80277a7).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #34   +/-   ##
=======================================
  Coverage   94.51%   94.51%
=======================================
  Files          10       10
  Lines         602      602
=======================================
  Hits          569      569
  Misses         33       33

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


[Removal]:

Hotspot Name
big-gauze-viper
Hotspot b58 Address
11VWSfRZ6JLzfqWbtBtus8ZZ8DZ6yAyN6hgQGYsGdEz35S26YKX
Discord Handle
No response
Hotspot Manufacturer
Pisces Miner
Removal Reason
they are real installed, what's going on?
Modifications
No
Extra forwarders
Yes
Extra antennas
No
Additional Information
they are real installed, what's going on?

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


ZEIT Now => Vercel

Change occurrences of ZEIT or ZEIT Now to Vercel 🤗

📝Changed routes:

/

(view full size)

Commit 80d05fc63a718a47115f65e0a08030c0e6e6daf9 (https://title-site-git-fork-ryanccn-master.vercel.now.sh).

Obviously this PR is stale...


Working with react native

Has anyone tried this package with react native expo and does it work?

Hi @britisharmy! json-schema-form is vanilla javascript so it should work well with any javascript framework. We at Remote use React :) Let us know how it goes!


Address XS code hygiene tasks

part of #4968

Changelog Entry

Description
Address the first 3 suggestions from #4968
Design

Specific Changes
List of changes:

[x] XS: Do not use React FC/VFC types, use Props instead
[ ] XS: Mark all props as read-only, also any arrays and objects under it
[ ] XS: Prefer import { type ABC } over import type { ABC }

As we remove FC/VFC I thought it'd be nice to add ReactNode return type basically to:

Serve as an additional hint that the function follows React Component signature
Limit usage of unsupported by React runtime return types

-

[ ] I have added tests and executed them locally
[ ] I have updated CHANGELOG.md
[ ] I have updated documentation

Review Checklist

This section is for contributors to review your work.

[ ] Accessibility reviewed (tab order, content readability, alt text, color contrast)
[ ] Browser and platform compatibilities reviewed
[ ] CSS styles reviewed (minimal rules, no z-index)
[ ] Documents reviewed (docs, samples, live demo)
[ ] Internationalization reviewed (strings, unit formatting)
[ ] package.json and package-lock.json reviewed
[ ] Security reviewed (no data URIs, check for nonce leak)
[ ] Tests reviewed (coverage, legitimacy)

Thanks William, good catch indead. I'll recreate the PR under the webchat repo for the CI PR pipeline to work


Transaction builder allows clear immutable flag

Which will either be a no-op if immutable flag is false, or a failure if immutable is true.

Good point -- under no circumstance would/can you ever clear an Authorization Immutable flag


Fix the misspelling in README.md

Fix the misspelling in README.md, word "Futher" to word "Further"

Hey anyone, this PR just failed for no reason...


Preparing the next release

There are currently a few issues open related to the latest haddock-api being incompatible with GHC 8.0.2. Can we cut a next release? Either 2.17.4 or <IP_ADDRESS> (probably the later if all it contains is the one compatibility change). I can prepare the code (cherry-pick the commit, update cabal file etc). But somebody with upload access to hackage would have to complete the release. Is anybody feeling responsible?

Tomas Carnecky<EMAIL_ADDRESS>writes:

There are currently a few issues open related to the latest
haddock-api being incompatible with GHC 8.0.2. Can we cut a next
release? Either 2.17.4 or <IP_ADDRESS> (probably the later if all it
contains is the one compatibility change). I can prepare the code
(cherry-pick the commit, update cabal file etc). But somebody with
upload access to hackage would have to complete the release. Is
anybody feeling responsible?

@Helkafen is currently the maintainer of record but we haven't heard
much from him recently. I can certainly upload the release if necessary.

I'm waiting on haddock-api working with 8.0.2 for an upgrade and would appreciate a new release.

This has been fixed with the upload of haddock-api-<IP_ADDRESS> (see also #571).


Fix the problem of instanceof test always return true.

If these variables are not null, their instanceof test always return true.
They may be failed to be initialized, it would be better to do a null test rather than an instanceof test.
http://findbugs.sourceforge.net/bugDescriptions.html#BC_VACUOUS_INSTANCEOF

Could you please squash the commits?

This PR is wrong - we should not just do whatever findbugs says as its false reports sometimes.
Those instances may not be CamelContextAware.

Can you close this PR


Adds a cff file for GitHub autogenerated citations

This PR adds a citation file format (cff) file to activate GitHub's (relatively) new citation generation feature.

There needs to be an authors section, so I've currently added Stephanie as the author. The exact list (or a group name) can be used instead if that's what we want to do.

Closing this one in favor of the citation on the hatchet source repo, thanks!


Shifted augumented segmentation mask

I am getting shifted segmentation mask. It keeps proportions, which is good but is shifted....
Why such weird behavior ?

Which operations are you using? Do you have example code how you call them with your data? Usually, segmentation masks and images should match.

My fault, I had bug in the code. Im using segmentation mask and works 100%. Sorry for trouble.


General description for senD2-sai

The senD2-sai simulation is based on the refD2 experiment but with a modified specified stratospheric aerosol distribution reflecting increased stratospheric aerosol amounts from stratospheric aerosol injection (SAI). Sea ice and sea surface temperatures (SSTs) are specified to follow a repeating annual cycle taken from those used by the same model for their refD2 experiment over 2020 - 2030, the period when SAI is assumed to have been initiated.

"template" catalogue record https://catalogue.ceda.ac.uk/uuid/1fcf16f9d33348589d4e8431083470d0


Allow external links in top menu

In the top menu, links to external sites should be possible.
To allow this:

add the "external" property on each link in the top_menu settings
adapt the code for the top menu

An external link should open in a new window.

This works already.  Chrome is smart enough to figure the link out based on /whatever or http(s)://whatever.


Access current locale when resolving templates

I am not sure whether it should be a concern of this library, but at some point it make sense to me to have entire templates translated, with rules like in rails, so a {{partial "my-thing"}} will be resolved (assuming locale is en-us) to the first available of

-my-thing-en-us.hbs
-my-thing-en.hbs
and finally the non-localized -my-thing.hbs.

This is very similar to what rails does with templates.
Of course it is not possible to inject 'intl' in the resolver (as it is outside of the container), and I have found no pointer to solve this, it seems that it is a non-issue for many.
Would you think that it would be possible to have a Resolver mixin, searching for the templates with the suffix, like
// intl-template-resolver.js
export default Ember.Mixin.create({
  getTemplateSuffixes() {
    // some magic here?
  },

  resolveTemplate: function(parsedName) {
    let suffixes = this.getTemplateSuffixes();

    while (suffixes.length) {
      let suffix = suffixes.pop();
      let found = this._super(`${parsedName}-${suffix}`);
      if (found) {
        return found
      }
    }

    return this._super(parsedName);
  }
});

How I've dealt with this in the past, at the component level, is make layout a computed property.
// components/x-foo/component.js
layout: computed('i18n.locale', function() {
  const locale = get(this, 'i18n.locale');

  return getOwner(this).lookup(`template:components/x-foo/layouts/${locale}`);
})

It might make sense to create an addon for this that is agnostic to both ember-intl/ember-i18n.  That said, I'm not against using the resolver for this, I just haven't ventured down that far in my previous attempt to get this working in a project.

If you have any idea of how to get the magic in the resolver, I would be very happy to make the implementation.

@stefanpenner any suggestions?


Fix #106: make legend a little taller so it doesn't scroll in chrome

Fixes #106
After the change:

Before this change:

Overflow:hidden doesn't work here for accessibility reasons - if the user has a larger minimum font size set in their browser, the text will just be cut off if overflow: hidden is set. Right now, if the text is larger than expected due to the user's accessibility settings on their browser, the text will scroll but still be usable.

Thanks so much for the fix and the detailed explanation!


Move legacy to config subpackage

What does this PR do?

Move pkg/legacy to pkg/config/legacy
Create a LegacyConfigConverter authorizing set

Motivation
Make set private in the end

Codecov Report

Merging #2559 into master will decrease coverage by <.01%.
The diff coverage is 47.22%.

@@            Coverage Diff             @@
##           master    #2559      +/-   ##
==========================================
- Coverage   56.43%   56.42%   -0.01%
==========================================
  Files         379      380       +1
  Lines       24014    24026      +12
==========================================
+ Hits        13552    13557       +5
- Misses       9547     9554       +7
  Partials      915      915

Impacted Files
Coverage Δ

pkg/config/legacy/no_docker.go
0% <ø> (ø)

pkg/config/legacy/trace-agent.go
0% <ø> (ø)

pkg/config/legacy/importer.go
68.08% <ø> (ø)

pkg/config/legacy/process-agent.go
0% <ø> (ø)

pkg/config/legacy_converter.go
0% <0%> (ø)

pkg/config/legacy/docker.go
72.3% <100%> (ø)

pkg/config/legacy/converter.go
63.05% <29.26%> (ø)

pkg/config/legacy/kubernetes.go
79.38% <94.11%> (ø)

pkg/forwarder/transaction.go
82.9% <0%> (+0.85%)
:arrow_up:

+1 For the callback solution, it would allow to easily change things from the other agents sides


remove unnecessary symbol filelock in IndexFile.java

What is the purpose of the change
trivial cleanups: remove unnecessary symbol filelock in IndexFile.java
Brief changelog
remove unnecessary symbol filelock in IndexFile.java, only remain annotation for intention of this symbol
Verifying this change
simple code review
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

@zhouxinyu please help me review this code. And result of code check is straight


fail to auth MS ActiveDirectory with ldap-auth

i try to auth my user with mode ldap-auth.but i cant login successful. pls help me check my configuretion.Are there some thing wrong in this?
my harbor config:

the info is ok  in nginx-ldap-auth:
url ldap://xxxx:389/OU=总部,OU=enterprise,DC=intra,DC=nsfocus,DC=com?samaccountname?sub?(objectClass=user);
binddn<EMAIL_ADDRESS>binddn_passwd xxxx;
group_attribute uniquemember;
group_attribute_is_dn on;
}
i got error:
LDAP search errorLDAP Result Code 32 "No Such Object": 0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
Dec  8 03:10:43 <IP_ADDRESS> ui[21757]: #011'OU=²¿,OU=Enterprise,DC=intra,DC=nsfocus,DC=com'
Dec  8 03:10:43 <IP_ADDRESS> ui[21757]:
Dec  8 03:10:43 <IP_ADDRESS> ui[21757]: 2017-12-08T03:10:43Z [WARNING] ldap search fail: LDAP Result Code 32 "No Such Object": 0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:

probably because the OU has Chinese characters?

I dont know，but i had configre this information in another system ,Its worked. do you wanna fixed it?

We need to understand what's the root cause first, could you try with a DN without Chinese?

I reslove this problem.i found that sAMAccountName is option.i change my config to that。As shown below.

i test the problem by ldapadmin tools. i can login DN without OU.and then i try to do this in harbor,too。the big problem is LDAP UID。i has been failed in uid/cn/email。


add TF/third_party/xla into bazelrc

This could be used for enable XLA tests under TF

no need to


Minimap plugin does not pick up colours

The plugin minimap (and other plugins that add the same functionality) do not display the colours of this theme in the scrollbar.
So far this is the only theme I know to do this. And unfortunately my favourite theme as well
I have no clue why though, just wanted to mention it.

Hey lavandongen,
Update 1.07 now supports the minimap plugin. Also, better support for third-party extensions.

That's great! Back to using my favourite theme! Thanks so much :)


Make a module for making comparison ops (==, <, >=, etc) chaining

Back when I nailed down 007's operator precedence, I chose not to borrow Perl 6's "chaining associativity"; the thing that makes
0 == 0 == 0

come out as True (because all these things are equal) rather than a falsy value as in 007 (because it parses as (0 == 0) == 0).
$ bin/007 -e='say(0 == 0 == 0)'
0                                                         # note: that's False for you, see #157

At the time, it felt like it added extra complexity without giving much back. But now, it'd be a pretty neat demonstration of what macros could do.
In this case, the macro would need to detect "adjacent" operators on the infix:<==> precedence level, and turn them into something different. Note that it should trigger on
x == y == z

But not on
(x == y) == z

Currently these come out the same in the Qtree, so I guess this is another strike for making circumfix:<()> a thing. (The first strike being some speculation in #163.)
What would x == y == z translate to? It'd translate to something like this:
(sub (a1, a2, a3) {
    if a1 != a2 { return 0 };
    if a2 != a3 { return 0 };
    return 1
})(x, y, z)

Hm, no. That won't cut it — we evaluate all of x, y, z at most once (which is correct), but we don't short-circuit properly. (z shouldn't even evaluate if x != y.) Let's try again.
(sub () {
    my a2 = y;
    if x != a2 {
        return False;
    }
    else if a2 != z {
        return False;
    else {
        return True;
    }
})()

There we go.
Note that this code very much has to be built with the original chain as input. This might be the first really good use case for parametric code that we've found.
I note that every time I come up with "what should this generate"-type code, there's a sub in there functioning as a computation boundary, in the sense that I like to lean on the early returns. There's some lesson in there, I'm sure.
Other things worth thinking about:

There should be a nice, sensible API for saying "give me all the 3-or-more-chains of the comparison ops (that is, ops on the infix:<==> precedence level)".
Of course, this search should DTRT even if there's a custom op on that level that participates in the chain.
...no matter whether the custom op was added before or after the chaining pragma was pulled in, as long as they're both active in the same scope.
...even if the custom op was pulled in via a separate module.
Also, I bet someone wouldn't mind having a really neat API for creating that chain of if/else if/else statements. Recall that they look linear in the code, but they actually nest more and more deeply in the Q. Having a builder API there could eliminate some of the manual bookkeeping.
That a2 variable needs to be symbol-ish enough that it doesn't collide with any real variable from the comparison. Guess we might need symbols after all.

It's interesting to evaluate this issue in the light of the new contextual macros #349. It feels to me that this would need to be a "transformer macro", basically a match on a context but without the corresponding inner macro to trigger on.

In this case, the macro would need to detect "adjacent" operators on the infix:<==> precedence level

Well, we have that with my eqPrec = new Context { node: Q::Expr, level: infix:<==> };. This will find us the topmost node with that precedence. (Or will it? The expression parser is still working bottom-up... It could just as well find the leftmost, for example. But I'd rather it find the topmost.)
From it, since that precedence level is left-associative, we just scan down the lhs-es for as many operators at that precedence level as we can find. That's our chain. We can return early if we find a "chain" of just 1 infix.

Of course, this search should DTRT even if there's a custom op on that level that participates in the chain.

The above algorithm does that.

...no matter whether the custom op was added before or after the chaining pragma was pulled in, as long as they're both active in the same scope.

These kinds of worries afflict one before one gets the model right. 😄
It is interesting to ask whether this kind of chaining thing should affect chains above the use chaining; but still in the same scope.
Once we have the chain... well, let's take this as a concrete example: 0 < x == y <= 10. The AST now looks like this:
       <=
      /  \
    ==    10
   /  \
  <    y
 / \
0   x

We could easily also pull out an array of all the terms, which are always N+1, one more than the chain of infixes. Now we traverse each of the infixes, creating code to do the following:

Evaluate the lhs — or, if this is not the first infix, grab it from where we already stored it
Evaluate the rhs, and — unless this is the last infix — store it for later
Compare them according to the infix
Return the comparison value if (a) it's falsy or (b) this is the last infix

Herb Sutter in this talk (and a talk prior to that) explains how he implemented chaining operators in cpp2 but only the ones that make transitive sense. In other words, min <= x < max but not a >= b < c or d != e != f.
I'm still not sure how I feel about that, but I wanted to mention it as an option.


virtual-device-testing-for-ios 0.9.11

https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/releases/0.9.11
New Pull Request Checklist
Please mark the points which you did / accept.

[x] I will not move an already shared step version's tag to another commit
[x] I read the Step Development Guideline
[x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

Hi @shams-ahmed !
Unfortunately there is no new GitHub release for the original git repository.(https://github.com/bitrise-steplib/steps-virtual-device-testing-for-ios/releases/0.9.11)
This way I am unable to merge. Although the changes are great, please send us a PR for the step repo itself, with the step.yml changes.
Thanks!


how to confirm image distribution is happening form peer nodes?

Question
when i verified confirm image download happening from peer, pieceSize:0 pieceNum:0. Is this an error?. Is there any other way to confirm P2P networking is happening?.

here is the method to check: https://github.com/dragonflyoss/Dragonfly/blob/master/FAQ.md#how-to-check-if-block-piece-is-distributed-among-dfgets-nodes


feat: get in queue requests

Now the gw_get_transaction/gw_get_withdrawal RPC calls will return
{ "status": "in_queue", ... }

instead of null for in queue transactions/withdrawals.
On a full node gw_get_transaction/gw_get_withdrawal will be almost
always accurate.
Readonly nodes when well connected to the full node via the p2p network
will be notified about in queue request changes, so they will also
return
{ "status": "in_queue", ... }

for requests that they know are in queue.
But due to network delay or connectivity issues they may still return
inaccurate answers, e.g. they may return null for some in queue
requests, or they may return “in queue” or null for actually
pending/committed requests.

This PR introduce too many cost to the protocol compares to the benefit. We should give a better solution.


🚧 WeakDictionary<TKey, TValue> and dictionary stuff

Add a dictionary type that holds weak references to its values (Dictionary<TKey, WeakReference<TValue>>, essentially). Consider adding a ConcurrentWeakDictionary<TKey, TValue> as well.
May also add some dictionary-related utilities and extensions, for example, extensions for converting KeyValuePair<TKey, TValue> to DictionaryEntry and back.

I was initially going to use weak dictionaries as cache, but now I realized that they're a bad choice for stuff like that. The garbage collector doesn't have a fixed behaviour, so it kinda doesn't make sense to rely on it for freeing the cached items. I'll keep the dictionary-related extensions though.


Version 3.0.0 can produce wrong results

Hi,
when I use jiwer version 3.0.0 with the following commands:
wer_transform = jiwer.Compose(
    [
        jiwer.ToLowerCase(),
        jiwer.RemoveMultipleSpaces(),
        jiwer.Strip(),
        jiwer.ReduceToListOfListOfWords(),
    ]
    )
wer = jiwer.wer(
        truth = 'This is a short Sentence with a few Words with upper and Lower cases',
        hypothesis = 'His is a short Sentence with a few Words with upper and Lower cases',
        truth_transform = wer_transform,
        hypothesis_transform = wer_transform,
        )

I get wer=0.0714, which is the expected result based on the WER formula.
But when I use the non-deprecated keywords 'reference' and 'reference_transform' instead of 'truth' and 'truth_transform':
wer = jiwer.wer(
        reference = 'This is a short Sentence with a few Words with upper and Lower cases',
        hypothesis = 'His is a short Sentence with a few Words with upper and Lower cases',
        reference_transform = wer_transform,
        hypothesis_transform = wer_transform,
        )

I get wer=0.2857, which is clearly wrong.
This does not happen if the 'jiwer.ToLowerCase()' transform is removed from the transformation, thus I expect the bug to be related to that.
Cheers,
Paul

Thanks for noticing! Fixed in release 3.0.1.


Update setup-ros to 0.6 and action-ros-ci to 0.3

Goign to try and deal with this by setting up dependabot.


Consider addressing buffer alignment in a more robust way

See #155 and and #171 (specifically https://github.com/hannobraun/inotify-rs/pull/171#pullrequestreview-655632788) for context.

Would it be acceptable to NOT align the byte buffer? That would save a lot of potential new code (for example, custom structs wrapping the buffer and enforcing alignment) and maybe not break as easily.
With this proposed approach, the key would be std::ptr::read_unaligned which lets us read the inotify_event data from the unaligned buffer.
Contrast with the * pointer dereference:
https://github.com/hannobraun/inotify-rs/blob/b68d62fd56ecedcefce1827e6cf2d62a08e0aa91/src/events.rs#L172
Which is not allowed (UB) according to the pointer docs:

Raw pointers can be unaligned or null. However, when a raw pointer is dereferenced (using the * operator), it must be non-null and aligned.

Since that * dereference seems to be the problematic part, maybe we can just fix that line instead of enforcing buffer alignment throughout the library? I'm assuming the performance cost reading a struct from unaligned memory, and adding one copy operation, would be negligible.
Here is what this approach looks like: https://github.com/hannobraun/inotify-rs/compare/master...talklittle:inotify-rs:allow-unaligned-buffers?expand=1
Note that it largely reverts #171. Also verified that it stops Miri from reporting the UB alignment error.
I can create a pull request if it makes sense.

Thank you for looking into this, @talklittle! Based on the documentation you linked and the Miri result, this looks like a viable way to do it. A pull request would be appreciated!


Errors when running example

I'm having some issues running the example:
[max@goma OrthomosaicSLAM]$ python3 main.py -i images/campus_1 -o testout
[INFO] Importing Images...
[INFO] Importing Complete
[INFO] 29 Images have been loaded
(3200, 4800, 3)
13
(3724, 5272, 3)
20
(5277, 5543, 3)
25
(5920, 5658, 3)
25
(3200, 4800, 3)
32
(3836, 5248, 3)
39
(4229, 5421, 3)
1
Traceback (most recent call last):
  File "/home/max/src/OrthomosaicSLAM/main.py", line 148, in <module>
    tester.mixer()
  File "/home/max/src/OrthomosaicSLAM/main.py", line 56, in mixer
    self.temp_image = self.sticher(self.temp_image,self.images[x+1])
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/max/src/OrthomosaicSLAM/main.py", line 103, in sticher
    M, _ = cv2.findHomography(src_pts, dst_pts, cv2.RANSAC, 5.0)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cv2.error: OpenCV(4.5.5) /io/opencv/modules/calib3d/src/fundam.cpp:385: error: (-28:Unknown error code -28) The input arrays should have at least 4 corresponding point sets to calculate Homography in function 'findHomography'

if I change MIN_MATCH_COUNT to 4 it proceeds but then crashes again...
[max@goma OrthomosaicSLAM]$ python3 main.py -i images/campus_1 -o testout
[INFO] Importing Images...
[INFO] Importing Complete
[INFO] 29 Images have been loaded
(3200, 4800, 3)
13
(3724, 5272, 3)
20
(5277, 5543, 3)
25
(5920, 5658, 3)
25
(3200, 4800, 3)
32
(3836, 5248, 3)
39
(4229, 5421, 3)
1
Error
Traceback (most recent call last):
  File "/home/max/src/OrthomosaicSLAM/main.py", line 148, in <module>
    tester.mixer()
  File "/home/max/src/OrthomosaicSLAM/main.py", line 56, in mixer
    self.temp_image = self.sticher(self.temp_image,self.images[x+1])
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/max/src/OrthomosaicSLAM/main.py", line 72, in sticher
    print(self.image1.shape)
          ^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'shape'

Hi @maxogden, thank you for trying out the repo. There indeed seems to be a problem with the campus_1 dataset. The images were supposed to be from DSC05984.JPG to DSC06014.JPG, but a few images after DSC05993.JPG seem to be missing until  DSC05996.JPG. When we try to stitch them, this causes a sudden decrease in the overlap between  DSC05993.JPG and  DSC05996.JPG, which is why the code fails.
I will split the dataset into campus_1 and campus_2 as I no longer have the original images.
Here is campus_1 when run at scale_percent = 80

And here is campus_2 when run at scale_percent = 50

scale_percentage can be changed from line 33 in main.py


Breaking changes to VSMenuModHelper cause the game to crash on startup

Mod version: v1.0.5
Game version: 1.6.104
Melon loader version: v0.6.1
Issue: Breaking changes to VSMenuModHelper cause the game to crash on startup
Latest.log

There was this but the reason I set it to alpha was because I knew that this was in the works so I will update when I can but that won't be for a day or two as I am very busy working on projects.

So is this mod not being worked on anymore?


Allow FUZZING_ENGINE=fsanitize_fuzzer for fresh clang

Addresses #45. My tests on this haven't finished, but based on the way they fail I think it's because of my clang version.
I kept the status quo of also using fsanitize=address, which is the default behavior for other options.

My tests on this haven't finished, but based on the way they fail I think it's because of my clang version.
Is this working now?

I haven't been working on using this, I think @kcc had


Hiding and showing the map

I render GoogleMapReact in a hidden div. When I show the div, the map is absent. How to make it show?
http://jsfiddle.net/L3k4ktdj/1/
As I understand, as the div state (hidden/shown) is in the component state, it is rerendered after the state is updated. However, that doesn't really happen. I am just learning react, so maybe the error on my side. I'd appreciate you help with this, thanks.

How about using the state directly like this? http://jsfiddle.net/L3k4ktdj/2/


Updates for FFmpeg 4

@barzamin Thank you! Seeing as this repo is not being updated very often, and the crates.io crate is wayy out of date, I think we should think about switching to a different repo

Yeah, I'm strongly considering forking this over somewhere else and applying all the patches that make it Actually Build on modern systems

Does anyone want to be added as contributor and to crates.io for the time being?

@meh I'm a little busy, but I would be happy to help out as long as someone takes the lead of maintaining the crate.

@meh i would be open to acting as an interim maintainer of the crate

@meh Thought about this a bit more and I definitely have the time to do the (relatively small!) amount of work needed to bring this all up to date and maintain the crate; if you could add me as a co-maintainer, that would be awesome!

@barzamin go for it, please use squash/rebase instead of merge if possible, I don't like merge commits unless they make sense (i.e. feature branch or whatever).
Thanks.


🔎 The example in the documentation is broken

I encountered errors when running the code from the documentation here: https://clouddrift.org/usage.html.
There's a typo in the variable name (id in the dataset is lowercase, but it's retrieved as .ID).
There might be other errors as well.
In my experience, keeping a static documentation in sync with the code can be very challenging.
I suggest either running the code and producing the output when you compile the documentation or using doctest to ensure the hardcoded outputs match the current code.
I'll give it another go and provide feedback on the content once the usage code is fixed.
JOSS: https://github.com/openjournals/joss-reviews/issues/6742

OK, the usage example looks good now.
Consider running doctests in the CI. I tried it, and it needs some fix here and there:
pytest --doctest-glob="*.rst" docs/


Support Fahrenheit

Would this be possible as an option?

Seconded. It would be nice to be able to toggle this.

Yes, please!

Please!

Resolved in https://github.com/DanielStormApps/Fanny/commit/cec8011c7d7f9460afbb530b689594232208bad8 👍