CS224W - Bag of Tricks for Node Classification with GNN - LogE Loss

Add log $\epsilon$ loss functions
Part of #9831, as described in “Bag of Tricks for Node Classification with Graph Neural Networks”, this non-convex loss is thought to be less sensitive to outliers, providing a maximal gradient at decision boundaries, but still significant signal for all misclassified examples.
Details

Implements drop-in module and functional variants corresponding to nll, cross_entropy, binary_cross_entropy, and binary_cross_entropy_with_logits
Longer term pytorch might be the best place for these to live, but we think PyG might be a good place in the meantime as the paper shows it is more effective on GNNs than MLPs
PyG does not yet have any loss functions as far as we could tell, but torch_geometric.nn.functional seemed like a reasonable place for them to live.  Happy to move to contrib as well.
Implemented as simple wrappers around pytorch losses for easy maintainability

Benchmarks

From benchmarks/citation using Colab's T4s we see it is can bring small but statistically significant gains

Seems to work well with GAT more consistently than other models

It can however, in some settings cause big losses, e.g. it seems to work very poorly with SGC, and we recommend users trying more traditional losses as well to see what works best

Validation delta is not always correlated with with test delta, but in these cases it usually does not cause too big a regression

Typically slower due to the bit of extra computation, but can be faster due to early stopping
A selection of deltas which were statistically significant on test accuracy with at least 95% confidence are included below, expressed in direction loge - nll

For Arxiv, default GAT parameters from benchmarks/citation were used with a batch norm inserted, though these are surely suboptimal settings
Full results can be viewed here

nll_command
val_acc_abs_delta
test_acc_abs_delta
duration_rel_delta

gcn.py --dataset=CiteSeer
0.73%
0.76%
2.62%

gcn.py --dataset=PubMed
0.42%
-0.47%
7.38%

gat.py --dataset=Cora
0.19%
-0.21%
2.81%

gat.py --dataset=CiteSeer
0.86%
0.70%
-6.07%

gat.py --dataset=PubMed --lr=0.01 --output_heads=8 --weight_decay=0.001
0.40%
0.18%
2.32%

gat.py --batch_norm --dataset=Arxiv --no_normalize_features --runs=20
0.73%
0.67%
-1.54%

cheb.py --dataset=Cora --num_hops=3
0.65%
0.66%
-4.62%

arma.py --dataset=Cora --num_layers=1 --num_stacks=2 --shared_weights
-0.10%
0.19%
-1.23%

arma.py --dataset=CiteSeer --num_layers=1 --num_stacks=3 --shared_weights
0.50%
0.61%
2.76%

sgc.py --K=3 --dataset=Cora --weight_decay=0.0005
-13.69%
-12.37%
-27.50%

sgc.py --K=2 --dataset=PubMed --weight_decay=0.0005
-13.00%
-15.80%
10.01%

appnp.py --alpha=0.1 --dataset=Cora
-0.38%
-0.28%
-3.66%

appnp.py --alpha=0.1 --dataset=CiteSeer
0.50%
0.53%
0.69%

lgtm!
Two remarks:

The metrics table is too much detailed - we should help the reader by writting in bold the relevant numbers - the command column is hard to read with so many numbers - we could also split the tables to make reading easier.
I believe it should be good to have a few examples (not mandatory imo tho).

Fair point! cut down the table quite a bit and linked to the test.  Still wanted to include at least a couple results for each method to show when they are consistent/inconsistent across datasets.  Could move the commands below but I think it is fairly readable now and that would make the description longer

lgtm

Closing because I can't figure out how to unlink with the PyG issue, this was just a draft for our internal review


Simplify match statement to expression

Builds and tests are OK after this changes. Hope it improves readability 😺

Looks good! Thank you :)


Poorly worded Note

The note at the beginning of this article is poorly worded: "There are many more features in the Trace parser are similar to Microsoft Dynamics AX 2012. See the Dynamics Ax Performance Team Blog for more information."
No biggie, just thought you should know

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

ID: 2ca95239-c2a9-10f0-babd-43225bf20669
Version Independent ID: 8843088d-3f83-4314-1a18-ea63e0fbda56
Content: Diagnose issues and analyze performance by using Trace parser - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/perf-test/trace-parser.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @RobinARH
Microsoft Alias: chwolf

Thank you for your feedback. @RobinARH please take a look.

Fixed. Will go live today.


Add README on build environment and how to generate website

It seems you need indeed to have fix/ or feat/ in the title of the PR to keep the labeler happy.


Plan to start time and end time on issue

When create or update an issue, we can assign a planned start time and end time.

Doesn't most workflows use Milestones? Milestones already have due-dates AFAIK :)

Milestones have due-dates but issues have not. This feature will plan the work more detail. Like a project management program.

I think this is related to  #2533

@kolaente yes, right.


Design updates to the respond-to-an-application flow

Context
There are some inconsistencies in the design around the "respond to application" flow for providers.
Changes proposed in this pull request
One by one, from the card:

Move the candidate name above the title on Confirm Rejection form consistent with placing on other forms.

✅ Done
Before

After

This introduces a bit of duplication but the UI benefit from consistency is worth it

Vertical space between 'Continue' button and cancel link (all change/reject forms) should be reduced

💪 Fixed upstream in the formbuilder and will be picked up once the release makes it to rubygems
https://github.com/DFE-Digital/govuk_design_system_formbuilder/releases/tag/v1.1.7

Respond to application error message should appear above radio group and below H1
https://ukgovernmentdfe.slack.com/files/UPWN7EC2V/F010VTG33NK/image.png

😑 Imperfectly done with a hack — see commit. Probably needs an upstream change in the form builder to be 📐.
Before

After

"Tell the candidate why their application was rejected" on Reject Application form should be a label.
https://ukgovernmentdfe.slack.com/files/UPWN7EC2V/F010J3KU0Q1/image.png

✅  It's already a label

'Change' link should be present against conditions in confirmation step: /provider/applications//offer/confirm

❌ Not done. This is tricky as we don't have an intermediate step where we store the conditions. They do exist in memory at this point but we'd have to fake a POST to get them back into the form for editing. When we come to create individual conditions we might solve this for free, so I think we should punt it for now?
Link to Trello card
https://trello.com/c/2B8lduBk/1822-design-updates-to-respond-change-reject-application
Things to check

[X] This code doesn't rely on migrations in the same Pull Request
[X] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[X] API release notes have been updated if necessary
[X] New environment variables have been added to the Azure config

This screen should be:
Caption: {{Candidate name}}
H1: Tell the candidate why you're rejecting their application
Hint: We'll send them your feedback
[textarea]

[Continue]

The button should read ‘Reject application’
Above the button should be this:

The summary list should have one row—just the reasons the provider typed on the previous page with a change link back to that page.

I've answered the comments I hope, screenshots below.
Introducing a back link for editing rejection reasons is a bit beyond scope here I think, but let's put a ticket in the backlog if it's important
Giving reasons for rejection

Confirming rejection

@adamsilver this should (finally!) be ready now. The label is now an h1, but I wasn't able to get the caption (the candidate's name) in too. This is due to the form builder. If you think captions-in-labels is enough of a thing to merit support from the form builder, I can try and get it added.
Current state:

@duncanjbrown
I think you can merge as is.

If you think captions-in-labels is enough of a thing to merit support from the form builder, I can try and get it added.

yes please


[Task] Add Pull Request Template

Just like issue templates, we should also add a pull request template.
Reference

Example: https://github.com/devspace/awesome-github-templates
Guide: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository

Please assign me this issue

Please assign me this issue

Assigned! Thanks @jfmartinz!

I'll raise PR tomorrow.

Done in #15


fix TIKA-3970

start correctly handling the onlyLatestRevision option by detecting parent property id of type ElementChildNodesOfVersionHistory and do not print those if that flag is set.
need to prevent File Node references to the same text from being printed out in the xml stream multiple times.
improve PropertyValue to have a toString so that debugging in IDE is easier.

@tballison please review for fix of https://issues.apache.org/jira/browse/TIKA-3970

@nddipiazza Many thanks!


routing function name using http message headers in aws adapter

This pull request is for the issue #1529 raised in spring native project.
For the AWS adapter, if we have multiple beans, it is unable to find the router function to route using message headers with spring.cloud.function.definition.
The code is added to resolve the issue with the AWS adapter. Let me know, if any further steps are needed.

This seems like an same issue with https://github.com/spring-cloud/spring-cloud-function/issues/829


[WIP] Initial implementation of ECP5 PLL instantiation

This is the initial implementation where I took the liberty to be inspired by the Litex implementation.
Signed-off-by: Oguz Meteer<EMAIL_ADDRESS>

I have no doubt that the implementation can be improved, but I'm not entirely sure how. My Python skills aren't the best, and there are parts that I'm a bit iffy about.
Some examples:

In register_clkin, I don't know exactly how to check that the clkin parameter is a ClockSignal.
Also in register_clkin, I had an intermediate signal self.clkin that I commented out. That actually caused me to not define a new Module in elaborate, but in __init__, since I needed to assign the clkin parameter to self.clkin combinatorially. I found that an intermediate signal is unnecessary, so I now instantiate a new Module and return in it in elaborate.
In the Litex implementation, they always feed the last clock output back into the feedback input. Maybe we should make this optional?

It's way too early to consider merging anything upstream. Let's discuss what API we want first in #425.

Of course. I just posted this just to have some code that we could look at.


fix: update danish locale

Sorry, tested the danish locale a bit further and found some better translations.

Hi,
Thank you for the improvements.
I already merged the fix/danish-locale branch.
Please open a new PR targeting the main branch.


Save release artifacts only after building from source

save_release_artifacts assumes that we have built
artifacts from source, I want to run tests without building
from source code.
SKIP_INITIALIZE is the variable used to skip building
the project from source and bootstrapping a cluster.
/cc @aliok @matzew

/test pull-knative-sandbox-eventing-kafka-broker-build-tests

/cherry-pick release-0.26


DatasetStages don't work in a MultiCohort world

https://batch.hail.populationgenomics.org.au/batches/471684/jobs/1
This run contains 14 Cohorts, and ~15 Datasets, but when it got to the AnnotateDataset DatasetStage it was trying to queue ~150 different DatasetStages. This is because the current implementation of DatasetStage when using a MultiCohort is done by iterating over each Cohort, then over each Dataset in each Cohort.
https://github.com/populationgenomics/production-pipelines/blob/a3dfe6172d8c3ff191b17ca49756225564aceadb/cpg_workflows/workflow.py#L1386-L1391
This needs to be restructured so that each DatasetStage runs once per Dataset (collected across all Cohorts). This is because the Dataset concept is not hierarchically 'below' the Cohort, it's a different type of grouping, so when finding Datasets we shouldn't be looking one Cohort at a time, we should be looking across all samples in this analysis, i.e.
MultiCohort contains COH1 & COH2

COH1 contains
- Dataset1: CPGA, CPGB
- Dataset2: CPGC

COH2 contains
- Dataset1: CPGD, CPGE
- Dataset2: CPGF

When a DatasetStage runs, it should run:
- once on Dataset1, the collection of SGs [CPGA, CPGB, CPGD, CPGE]
- once on Dataset2, the collection of SGs [CPGC, CPGF]

Instead of the current behaviour:

- once on Dataset1, SGs [CPGA, CPGB]
- again on Dataset1, SGs [CPGD, CPGE]
- once on Dataset2, the collection of SGs [CPGC]
- again Dataset2, SGs [CPGF]

I've poked around in this, and it's actually going to be a lot of work to resolve...
Currently the structure we have is
MultiCohort {1}
-- Cohort {1, many}
---- Dataset {1, many}
------ SequencingGroup {1, many}

(IMO) This needs to be restructured to
MultiCohort {1}
-- Cohort {1, many}
---- SequencingGroup {1, many}
-- Dataset {1, many}
---- SequencingGroup {1, many}

Reflecting that both DatasetStages and CohortStages run on a subset of the overall MultiCohort SG group. We do not need to run them in the context of each other (i.e. DatasetStage will never run on 'the portion of this Cohort which is also in this Dataset'. Likewise a CohortStage will run on all SGIDs in the Cohort, crossing all Dataset boundaries).
The concept of building Targets/Inputs for the pipeline is built around the MultiCohort > Cohort > Dataset > SGID structure, which has some complications:

Currently a Dataset has a self.Cohort attribute, instead of a self.MultiCohort attribute, so it does not have a connection with the top of the Hierarchy
When populating SG IDs in the analysis we query for each Cohort, then bin the results by Dataset. The only way (currently) to add new SGIDs into an analysis is as a property of a Dataset object

This will create problems where we currently have CohortStage -> DatasetStage.
The main instances of this I can see are in seqr_loader (where the CohortStages are really MultiCohortStages, they just haven't been updated yet), and gCNV where there really are CohortStage -> DatasetStage transitions.
in seqr_loader this can be fixed by updating the code
in gCNV we can either temporarily patch the code to be MultiCohort stages consistently (on the basis that it's only run one Cohort at a time), or we can implement a merging step so the CNV VCFs from each separate Cohort are combined in a MultiCohort Stage, then the aggregate result is split out by Dataset (this is on the roadmap, we're planning to use Jasmine to pseudo-joint-call)

Doc here with a fleshed out description of the issues which currently exist on main
https://docs.google.com/document/d/1Zu4QFxuR44M1alRZtA5M9WGROLEUg74gQWorDQjOvTs/edit


WIP: multiplatform support

Signed-off-by: Erik Sipsma<EMAIL_ADDRESS>This is highly WIP, the most invasive change has been updating the graphql server to enable passing ambient state through the execution graph, which is a lot less straightforward than it seems like it should be. The current solution is not coherent and broke some code that isn't in the path I need to test stuff currently.
However, in the middle of all this I think I discovered a clean approach, so please ignore all the weirdness with Parent for the moment if you are perusing, should be cleaned up soon.
The actual multiplatform support has worked out nicely so far (fingers crossed). Starting out here with support for qemu-emulated execution and multiplatform image support. Cross-compilation is also going to be important to try out, but I suspect will be more straightforward.
The general idea here is that:

There's a top level field under query withPlatform(platform: String!): Query!, which enables you to wrap entire queries with a default platform setting. If you don't use this, platform defaults to the buildkit host platform.

Setting the platform applies to everything it can in buildkit (execops run with that platform, pulled images use it, etc.)
I haven't yet implemented passing this through when a non-core extension is invoked (i.e. if an extension sends its own query, it will default to the platform in its ambient context), but that will be a straightforward addition on top of the idea here.
Extensions will also be able to override the platform too when making their own queries. One example of where this may be helpful is if an extension knows that it want something to execute using the host platform (i.e. it's invoking something that uses cross compilation)
The final piece of the puzzle is that if you do something that creates a new layer on top of an existing layer, the platform needs to be inherited. This is the behavior of client/llb already, but I need to make sure it still works across a marshal/unmarshal cycle (if it doesn't it should be trivial to recreate that behavior)

For multiplatform exports

I just added a top-level pushMultiplatformImage field to core for now as a temporary solution. It's okay but a likely better approach would be to create some abstraction that lets you bundle different platform versions of a filesystem together and then add a pushImage field to that. That will make sense to do as part of the upcoming overall API refactor.
It's also important that you can individually reference platform specific versions of a given filesystem (i.e. they don't always have to be bundled together). This enables use cases like local exports where you may want to export binaries built for each platform to different local directories.

Overall, the above sounds really complicated, and to extent that's inherent to multiplatform, but if my imagination is correct it should work out so that multiplatform config usually does what you want by default and you only have to think hard about it when you're doing something inherently complicated.
The only way to verify that will be to try out various scenarios and ensure they go smoothly (started describing some of those here), so that will be my main focus besides just cleaning up the code here and adding the final missing features.

moved to here https://github.com/dagger/dagger/pull/3119


add tests for undefined id

I would like to re-propose these test. These were removed from https://github.com/jashkenas/backbone/pull/3936 under the impression that there is no need to ensure support for unreasonable values. I believe backbone should be un-opinionated about what values are legitimate. Examples are contrived, until they're not. The second test in particular is important to ensure _byId doesn't evaluate for an undefined return.

Added a guard to only treat obj as an id if it is a string or number.

I believe backbone should be un-opinionated about what values are legitimate. Examples are contrived, until they're not.

get has a contract. You may call that opinionated, but we've said again and again that developers shouldn't be using arbitrary values as ids. Particularly for a hot code path like get, it'd be best to keep the logic as un-cluttered as possible.

get has a contract that accepts a wide range of values. I am a fan of ensuring it is prudent about the path it takes given the specific value that is passed in, and without opinion following that path to the end.
That said, I understand where you are coming from. Thanks!


[meta] Client refactor or rewrite

Currently, the client is heavily DOM-dependent and written in ES5-compatible syntax.
Testing - although some great improvements with Jest and puppeteer have been made - is still hard to do.
We cannot currently make use of real Promise or await functionality and other ES6 goodies. The justification for sticking with older source code syntax has been laid out in https://github.com/posativ/isso/pull/834, but this is not official policy but rather the opinion of 1 maintainer, subject to change.
Things to think about:

Compatibility with older browsers
Increasing complexity of developer setup (installing too many packages, handling too many configs)
Notoriously unreliable and insecure JS/npm ecosystem
Bundle size
Performance with many comments, memory leaks when leaving page open (setTimeout)
Single-Page-Applications (SPA) and carrying state

New or improved features

Editing buttons to insert Markdown elements like ** around the cursor (like GitHub, remark42, ...) (idea: cursor)
Editing help (inline, as a little popover or modal that slides out)
Editing name/website (and possibly email), tracked in https://github.com/posativ/isso/issues/111
Re-using more front-end functionality in the admin interface
Cleaning up CSS (tracked in https://github.com/posativ/isso/issues/859)
Auto-sizing <textarea>
Better feedback on errors (e.g. https://github.com/posativ/isso/issues/673)

See also

An experimental rewrite of the client, with some new ideas for extensibility
Discussion in https://github.com/posativ/isso/pull/887#issuecomment-1140321229

Continuing from the discussion in my PR

TS sure looks like a nice addition, but we might also be limiting ourselves in the contributors we get - they'd have to know TS as well. This kind of feels a bit like the "sprinkle some async" fad in python to me. Maybe start with better test coverage and work from there?

Better test coverage is a great start. TypeScript is very similar to JavaScript; it looks to me that it would be easy enough to understand quickly, especially if the contributor is familiar with other static/strongly typed languages.
I tried to look into TypeScript's popularity, and according to GitHub, TypeScript is 4th, while JavaScript is 1st. Stack Overflow's developer survey lists TypeScript as the 3rd most loved language, behind Rust and Clojure, and JavaScript is 15th.
I won't look into that too much because it's a very opinionated point. But it is cool to see.

I'm already kind of annoyed at all the Javascript packages constantly jumping sub-revisions (e.g. Jest and puppeteer all jumped several since I added them, and they need to be kept in sync with system chromium version if you don't use the .local-chromium version). You're never quite sure if something just broke because of a version change of a dep when re-installing or you broke something yourself. webpack is already quite a moving target and has not been pleasant to set up. I'm not really looking forward to spending maintainer time accepting PRs bumping revisions from bots every few days (new tsc release here, new babel release there, ...). It's not too much to do, but death by a thousand cuts.

I feel that with the proper tests, then using dependabot and pinning the dependencies to an exact version would be good. Ideally, the CI could run the tests on dependabot pull requests, which would catch any behavior differences the new package adds. That combined with the screenshot tests would hopefully mean that you don't have to do any manual testing on the new dependency.
There should only be pull requests for the top-level dependencies (in this case, webpack, webpack-cli, jest, and jest-environment-jsdom, plus one or two more if using TS) if using dependabot. There wouldn't be pull requests for dependencies of dependencies (and so on).

If we're going to want to start using ES6 features, TypeScript would allow us to use them, but transpile an ES5 JS output. We could also use classes, types, and interfaces to represent data in a more object oriented and organized way.
I don't know if I'm really explaining this well, maybe I'll have to play around with it first before I can.
See also:

TypeScript for JavaScript Programmers
Classes - TypeScript

While looking at the experimental client code, I think I sort of see how prototype is used to create classes. To me, this is really messy and hard to understand. I tried to make a quick example of what I think the example you put in the README.md.

JS
var App = function(conf) {
  this.conf = conf;
}
App.prototype.initWidget = function() {
  var self = this; // Preserve App object instance context
  renderSomething(self.conf);
  // [...]
}

// later, in other file:
var app = new app.App('conf');
app.initWidget()

TS
class App {
  constructor(conf) {
    this.conf = conf;
  }
  initWidget() {
    var self = this; // Preserve App object instance context
    renderSomething(self.conf);
    // [...]
  }
}

// later, in other file:
var app = new app.App('conf');
app.initWidget()

To me the TypeScript example is a lot cleaner and more familiar. I actually feel like TypeScript would be easier for people to learn if they don't know JavaScript at all. Another advantage is that editors (such as Visual Studio Code) can give much better suggestions because of the static nature of TS.
I asked a few friends who do web development and they told me that your JS example is the normal way to do it in JS, but also that TS would be worth it. Hopefully I can learn some more soon.
I think I might still try experimenting a bit with my own version in TypeScript since it might be easier to learn that way instead of trying to rewrite an experimental rewrite. Then hopefully I'll have more knowledge to know what the best solution is.

That TS only pulls in one mono-package (plus a few for ts-loader) looks very appealing to me. You can progressively start using TS/modern features and use TS to compile back to ES5.
If it's that easy and we can skip adding all the babel-related bloat, I'm all for using TS.
I added you as a collaborator to the repo, feel free to push.

I've been taking a look and I feel like the way the experimental rewrite is structured is more complicated or harder to understand than the original source here. And I don't know if rewriting it in TS is as worth it as I thought. Currently I'm trying to figure out if I can make my own version in React & TS to see if it can bring any better structure (hopefully without making it too complicated either), but it'll be a bit before I can know for sure.
I'm also worried about whether rewriting anything is worth it, compared to just gradually improving the existing code.

I share your hesitation with rewriting things from scratch. You'll notice that the experimental client still shares most of its code with the stock one, so a "rewrite" is probably not the correct term to use.
I had to make a few structural changes to accommodate the following issues (which I still don't consider fixed):

A lot of places rely on the config object/instance. The config, however, needs to be fetched from the server first (or rather, the overrides).
The api needs to know its own endpoint, so it has to be instantiated or behave object-y, if we don't want to let it scrape the endpoint from script tags on every API invocation
The postbox and comment renderers can insert instances of each other, i.e. the a "comment" needs to be able to insert a postbox for replying and a postbox needs to insert comments once they're submitted.
There are a lot of periodic tasks (updating ago datetime to human representation) to be done, all very similar. They should be handled in a "clock tick" fashion and not each run on their own (else we'd have a setTimeout timer for each) They should vanish as soon as the underlying DOM object is gone.
Everything that translates things needs an i18n instance, which in turn needs to have a config instance for language and pluralforms selection
All template rendering needs a config and readily-configured i18n instance
init() and fetchComments() both need to wait for the config to be fetched from the server. And they need a sort of locking/waiting mechanism to block until that is done, or defer those actions that rely on config until it is fetched. Also, init needs to be able to tell fetchComments to start working, so sharing some sort of mutex is needed.

So a lot of hen-and-egg problems, where we'd need some kind of central arbiter that listeners can register with, that is responsible for keeping state.
If adding a framework such as React helps with that or enforces some common best practices, I'm all for it. But I'd rather avoid adding too many dependencies and forcing us into some patterns before we've each deemed that change beneficial and necessary.
I'd propose we each do some more research, experiment a bit and then revisit this topic.

Interesting news, IE is now out of support as of today. And it was really the only reason we weren't using more modern features like CSS variables and ES6 right?
What do you think about updating some of the CSS and JS in the near future?

M$ unilaterally declaring something out-of-date doesn't magically make people stop using it.
The decision to maybe wait a bit on "modern" features such as CSS vars etc was based on percentages from caniuse, so not only IE versions, but all browsers that end users currently (still) use.
That being said, if we get ES5 compat "for free" when using TypeScript, I'm all for that.
CSS vars: Caniuse currently states 94% browser support.
I don't think we necessarily need a "technical" solution to that issue (mismatching/disarrayed use of "random" colors).
What if we listed all used (main) colors on top of the file as comments and only expressed opacity-reduced usage as rgba()? (rrggbbaa isn't well-supported, clean that up as well)


Office 2016/2019 UI

Hi!
Thanks for this great work.
Is there a way to change the style by a more modern Office UI (2016 or 2019)? If not, how can I contribute to this project?
Thanks in advance.

2019 style is not available yet. You can fork this project and contribute by submitting a pull request. After that you will be invited to join the team. There you can submit your code directly into the repository.


Unable to text parse version PDF-1.7

I have been working on a project to read PDF forms. PDF's of version <= 1.6 work just fine. For 1.7 pdf's I can't seem to get any text of the pdf, or any of the form fields, except for the two signature fields. I'm reluctant to upload the PDF, since it's not mine. Is there any guidance on how to look into the logs/debug or a known issue with 1.7 pdf's?
If I had to take a guess after spending the last 8 hours becoming familiar with the PDF language, it seems to be something wrong with decoding(?) the streams.
As a side note, dumppdf.py seems to find bits of the text, so I know it's parseable, I just don't know how to debug and fix the main miner.

the same problem, anyone figured out a fix ?

It is quite hard for us to understand the problem without having an example pdf, stack trace and example code. Let alone we are able to propose a fix.
If this is still relevant to you, could you supply the error message with the stack trace? Also, give an example of the code you are using. If possible, also upload the pdf. This makes testing and fixing a lot easier.


[go_router_builder] Add go_router v5 support to go_router_builder

go_router_builder should support  new feature added into go_router_v5
These include

shellRoute API
async and buildcontext redirect.

@chunhtai made PR https://github.com/flutter/packages/pull/2672

@hawkkiller thanks!

Do we have any idea on when this might be supported?  I'd love to start using shell routes in my enterprise app!

Will this also introduce a way to write redirect methods inside ShellRouteData? Or is it already possible to define a redirect function on shell routes?

Maybe bump this up to v6?

This is a show stopper for using go_router_builder for me.

Looks like this is complete? https://github.com/flutter/packages/pull/2977

@ClaireDavis no it isn't; this is also about ShellRoute which - to my knowledge - isn't available to the builder

@ClaireDavis, as @lucavenir wrote, it isn't for sure. We hope to switch to go_router_builder after mentioned PR merged, but unfortunately not. That is why for now, go_router_builder is useless if you want to get all go_router functionality.


[Windows] Improve console IO redirection.

Improves console IO redirection and Unicode handling.

Operation
Console Wrapper
subsystem=windows
subsystem=console
Comments

Godot print to console
✅
✅
✅

Godot print to file/pipe
✅
✅
✅
Rich print write escape sequences to the file.

Godot get_stdin_string from console
✅
❌
✅
Hangs waiting for input, probably not fixable.

Godot get_stdin_string from file/pipe
✅
✅
✅

C printf/std::cout to console
✅
✅
✅

C printf/std::cout to file/pipe
✅
✅
✅
Rich print write escape sequences to the file.

C printf/std::cout in GDExtension to console
✅
✅
✅

C printf/std::cout in GDExtension to file/pipe
✅
✅
✅

Unicode characters seems to be working in all tested cases (both input and output), IO redirected to/from file/pipe expect and write text as UTF-8 without BOM (same as other platforms).
Fixes https://github.com/godotengine/godot/issues/87591
Fixes https://github.com/godotengine/godot/issues/91002

CC @hhyyrylainen

So I didn't manage to export my game with this branch because I couldn't get the compiled mono assemblies to match up (presumably I would need to setup that local nuget repo that the docs mention, or somehow force the built Godot editor to use the dev5 sdk version suffix), but I did get so far as to see that my game now outputs ERROR: Mono Cache: Managed callback for 'DisposablesTracker_OnGodotShuttingDown' is null. which if it is triggered after the redirection is setup, would mean that these changes work for my use case.

Rich print write escape sequences to the file.

https://github.com/godotengine/godot/pull/90900 could be applied to stdout if non-TTY output is detected, or when the NO_COLOR=1 environment variable is used, like I did in https://github.com/godotengine/godot/pull/77261.

Thanks!

Do we still need the console wrapper after all this?

I would keep it since it's still a more convenient way to start the editor with console output from the UI. As well as providing a bit more consistent behavior than windows subsystem binary when using from console and scripting (shell will properly wait for all spawned precesses, and won't show command prompt in the middle of output if you input something). Also, the only way to get input from console working.


Adding new container for mock web services

Description
Adding new container for development time use to provide mock web service endpoints, such as for ESRI. It's able to deal with other possible endpoints in the future so we don't have to make multiple different containers.
It's a very light Flask app that just serves up specific json responses based on a handful of known inputs. I built it to mimic that FakeEsriService.java file so they can be used interchangeably. Everything is plumbed into the build with a container already.
Checklist
General

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Alternative approach we may want to consider (that would also work for the staging deployments): add a FakeESRIClient akin to https://github.com/civiform/civiform/blob/main/server/app/auth/FakeAdminClient.java

Alternative approach we may want to consider: add a FakeESRIClient akin to https://github.com/civiform/civiform/blob/main/server/app/auth/FakeAdminClient.java
Would be a lot simpler to integrate (don't need to touch any of the docker stuff) and would work on the staging deployments because the fake client would be included in the main civiform server docker image

Thanks for sharing this, @avrittrohwer. This seems like a great alternative and should be simple enough to inject into ApplicantService and set as the esriClient if FakeEsriClient.canEnable(host) is true.

Oh, I like FakeAdminClient idea much better. Good catch

@gwendolyngoetz Okay to close this since we have the fake esri client now?

No, Sean's document planned on keeping it. Needs to be updated.

There doesn't appear to be any docs on usage of the FakeEsriClient so I'll write something up for both.


USHIFT-4924: Measure bootc build time and include build log in junit for failed builds

/test ?

/test e2e-aws-tests-bootc

/test e2e-aws-tests-bootc

/test e2e-aws-tests-bootc

/test e2e-aws-tests-bootc

/lgtm


15390 - Fon - Incorrect song lat-lon for 2319

Location from liner notes is Medetènu (Allada region), Benin. Current lat-lon is right in the center of Benin. Can't find coordinates for Medetènu, but Allada is in Southern Benin, which fits with the society. Changing lat-lon to Allada, Benin (6.65, 2.15).

Done


python312Packages.simpleaudio crash

Describe the bug
simpleaudio in python312Packages crashes after playing a sound. It works in python311Packages
Steps To Reproduce
shell.nix:
{ pkgs ? import (fetchTarball {
  url = "https://github.com/NixOS/nixpkgs/archive/59b1aef59071cae6e87859dc65de973d2cc595c0.tar.gz";
  sha256 = "0kla405dbqmgbpq59svgbfv7q01z2nnpmq8q2x614r9rrfwfyyrn";
}) {} }:

pkgs.mkShell {
  packages = [
    (pkgs.python312.withPackages (ps: [
      ps.simpleaudio
    ]))
  ];
}

Run
nix-shell
python
import simpleaudio as sa
w = sa.WaveObject.from_wave_file("w.wav")
w.play()
<simpleaudio.shiny.PlayObject object at 0x7f0bab03dbb0>
Segmentation fault (core dumped)

Notify maintainers
@lucus16

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.48, NixOS, 24.05 (Uakari), 24.05.4469.6e99f2a27d60`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.5`
 - channels(root): `"nixos-24.05, unstable"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

I think it's coming from upstream: https://github.com/hamiltron/py-simple-audio/issues/72
Possibly fixed here: https://github.com/wasertech/py-simple-audio/pull/1


feat: Document sensitive info rule

This is the first draft of the docs.
I still want to do one more pass first though and add a bit more content about the custom detect function, but its like 90% of the way there.
I also need to remove shield from all of the examples. Will have this more polished tomorrow morning.

I made a few minor tweaks to the Bun quick start and reference, but this is ready to copy over to the other frameworks now.

Copied that across


Support added for kafka-broker on ppc64le

Signed-off-by: Valen Mascarenhas<EMAIL_ADDRESS>
Which issue(s) this PR fixes:
Fixes
This PR adds nightly CI testing job for kafka-broker on ppc64le hardware

/ok-to-test


--args does not like the ":" character

Version: 0.13.1
Using Cocoapods for installation
Template
"{{ argument.url }}"

Running
$PODS_ROOT/Sourcery/bin/sourcery --sources . --templates ./Sourcery/Templates --args url="https://www.url.com" --output ./output-dir

will produce
""

Running (notice the lack of :)
$PODS_ROOT/Sourcery/bin/sourcery --sources . --templates ./Sourcery/Templates --args url="https//www.url.com" --output ./output-dir

will produce
"https//www.url.com"

This does not seem to be a Stencil issue as I tried cloning https://github.com/stencilproject/Stencil and running those tests supplying "https://www.url.com" into templates and it rendered fine.
I am not entirely sure what is going on. I have spent a bit of time looking through the source code, but unable to devote any further time looking into it. I suspect the cause is some sort of parsing / validation where the character : is either removed or used as a marking point in the string for parsing causing this unexpected behavior.
Is this the intended behavior? I am perfectly ok working around it for now, it could be good to document it somewhere.

@daviskoh I think the problem is not in code but in how arguments with quotes are decoded by Foundation - if you use " they will be removed from string, which will lead to value arg= https://www.url.com which will be parsed by extracting everything before : to argument name, so it will be url=https and its value will be //www.url.com. But if you escape it with \" quotes will stay and argument will be parsed correctly.

@ilyapuchka so Sourcery is using : as a marker point to parse args?

It uses the same function as for annotations where : is a namespace separator. But it ignores colons in strings surrounded by "
Ilya Puchka
Отправлено с iPhone

On 25 мая 2018 г., at 1:14, Davis Koh @daviskoh<EMAIL_ADDRESS>wrote:
@ilyapuchka so Sourcery is using : as a marker point to parse args?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Master main first fixes

adding these as the first commits, they are essential to start things rolling

Sorry, I am not sure.

OK, thanks.
And now?, which branch is that I should use for testing?

At the moment both master and master_main_first_fixes have the core of my changes / introductions. I'm very eager to start implementing things like code style, but first the expected functionality must be restored.
I'm still not at the point where I can say I know what all features do or should be doing, without a manual I rely on the code and comparing the code with the older versions.

OK, in this case I will use the master_main_first_fixes (but how do you change the font?) with blender 273, and point to problems there (in the proper issue #).

master should now support all version 2.68 - 2.7x , the import code attempts to offer a generic solution.
Change which font? in these threads? using the symbol that looks like single quote mark, but is called a 'back tick'
one of these ` not one of these '

more info about how to format the text: https://guides.github.com/features/mastering-markdown/


Realm: barrier assertion

I'm seeing the following assertion when running S3D on Frontier:
s3d.x: /lustre/orion/cmb103/scratch/seshuy/legion_s3d_tdb/legion/runtime/realm/barrier_impl.cc:1259: static void Realm:
:BarrierTriggerMessage::handle_message(Realm::NodeID, const Realm::BarrierTriggerMessage&, const void*, size_t, Realm::
TimeLimit): Assertion `datalen == (impl->redop->sizeof_lhs * (trigger_args.internal.trigger_gen - trigger_args.internal
.previous_gen))' failed.

It seems to happen when I turn on profiling as my run without profiling succeeded.

Also I am running on the onepool branch.

The critical path profiling requires the use of Realm barrier reductions which are not used when you are not profiling. What are the values of datalen, impl->redop->sizeof_lhs, trigger_args.internal.trigger_gen, trigger_args.internal.previous_gen, and trigger_args.internal.first_gen?

If you want to avoid this error for now and you don't mind not having critical path profiling then you can run with -lg:prof_no_critical_paths.
I'll also note that this doesn't have anything to do with onepool and will happen in the master branch as well.

Yep that is certainly a bug due to my recent merge of the notification broadcast. That will be fixed at the earliest convenience.


DEV: glib 2.56

update glib version

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

The new pinning automatically gets this package linking with glib 2.56, so this PR is no longer needed.


.PL ccTLD support

.PL ccTLD support
The Registrar format is pretty horrible to parse.
Most importantly all nameservers are detected now.

Hello @DSpeichert
Thanks for your works！


DAVE Sprint 23

Hello @pbalm! Thanks for submitting the PR.

In the file src/main/python/server.py, following are the PEP8 issues :

Line 57:121: E501 line too long (121 > 120 characters)
Line 63:13: E128 continuation line under-indented for visual indent
Line 64:13: E126 continuation line over-indented for hanging indent
Line 70:13: E128 continuation line under-indented for visual indent
Line 71:13: E126 continuation line over-indented for hanging indent
Line 77:13: E128 continuation line under-indented for visual indent
Line 78:13: E126 continuation line over-indented for hanging indent
Line 84:13: E128 continuation line under-indented for visual indent
Line 85:13: E126 continuation line over-indented for hanging indent
Line 91:13: E128 continuation line under-indented for visual indent
Line 92:13: E126 continuation line over-indented for hanging indent
Line 98:13: E128 continuation line under-indented for visual indent
Line 104:13: E128 continuation line under-indented for visual indent
Line 110:13: E128 continuation line under-indented for visual indent
Line 111:13: E126 continuation line over-indented for hanging indent
Line 119:13: E128 continuation line under-indented for visual indent
Line 120:13: E126 continuation line over-indented for hanging indent
Line 128:13: E128 continuation line under-indented for visual indent
Line 129:13: E126 continuation line over-indented for hanging indent
Line 139:13: E128 continuation line under-indented for visual indent
Line 140:13: E126 continuation line over-indented for hanging indent

In the file src/main/python/utils/dave_endpoint.py, following are the PEP8 issues :

Line 42:1: E265 block comment should start with '# '
Line 43:1: E302 expected 2 blank lines, found 1
Line 59:35: E261 at least two spaces before inline comment
Line 213:121: E501 line too long (121 > 120 characters)
Line 266:121: E501 line too long (126 > 120 characters)
Line 309:33: E127 continuation line over-indented for visual indent
Line 338:49: E128 continuation line under-indented for visual indent
Line 346:33: E127 continuation line over-indented for visual indent
Line 374:49: E127 continuation line over-indented for visual indent
Line 385:4: E111 indentation is not a multiple of four
Line 386:4: E111 indentation is not a multiple of four
Line 387:8: E111 indentation is not a multiple of four
Line 389:4: E111 indentation is not a multiple of four
Line 390:4: E111 indentation is not a multiple of four
Line 391:8: E111 indentation is not a multiple of four
Line 392:8: E111 indentation is not a multiple of four
Line 393:12: E111 indentation is not a multiple of four
Line 395:4: E111 indentation is not a multiple of four
Line 396:4: E111 indentation is not a multiple of four
Line 397:8: E111 indentation is not a multiple of four
Line 398:8: E111 indentation is not a multiple of four
Line 399:12: E111 indentation is not a multiple of four
Line 401:4: E111 indentation is not a multiple of four
Line 402:4: E111 indentation is not a multiple of four
Line 403:8: E111 indentation is not a multiple of four
Line 405:4: E111 indentation is not a multiple of four
Line 406:4: E111 indentation is not a multiple of four
Line 407:8: E111 indentation is not a multiple of four
Line 408:8: E111 indentation is not a multiple of four
Line 409:12: E111 indentation is not a multiple of four
Line 411:4: E111 indentation is not a multiple of four
Line 412:4: E111 indentation is not a multiple of four
Line 413:8: E111 indentation is not a multiple of four
Line 414:8: E111 indentation is not a multiple of four
Line 415:12: E111 indentation is not a multiple of four
Line 417:4: E111 indentation is not a multiple of four
Line 418:4: E111 indentation is not a multiple of four
Line 419:4: E111 indentation is not a multiple of four
Line 420:4: E111 indentation is not a multiple of four
Line 421:4: E111 indentation is not a multiple of four
Line 422:4: E111 indentation is not a multiple of four
Line 423:4: E111 indentation is not a multiple of four
Line 424:4: E111 indentation is not a multiple of four
Line 425:4: E111 indentation is not a multiple of four
Line 426:4: E111 indentation is not a multiple of four
Line 427:4: E111 indentation is not a multiple of four
Line 428:4: E111 indentation is not a multiple of four
Line 429:4: E111 indentation is not a multiple of four
Line 430:4: E111 indentation is not a multiple of four
Line 431:4: E111 indentation is not a multiple of four
Line 432:4: E111 indentation is not a multiple of four
Line 434:4: E111 indentation is not a multiple of four
Line 438:4: E111 indentation is not a multiple of four
Line 440:4: E111 indentation is not a multiple of four

In the file src/main/python/utils/dave_engine.py, following are the PEP8 issues :

Line 47:17: E265 block comment should start with '# '
Line 52:13: E265 block comment should start with '# '
Line 85:56: E226 missing whitespace around arithmetic operator
Line 85:121: E501 line too long (124 > 120 characters)
Line 86:85: E128 continuation line under-indented for visual indent
Line 87:85: E128 continuation line under-indented for visual indent
Line 98:55: E261 at least two spaces before inline comment
Line 99:50: E261 at least two spaces before inline comment
Line 252:121: E501 line too long (128 > 120 characters)
Line 263:13: E265 block comment should start with '# '
Line 272:9: E265 block comment should start with '# '
Line 279:59: E703 statement ends with a semicolon
Line 281:41: E262 inline comment should start with '# '
Line 282:37: E262 inline comment should start with '# '
Line 283:45: E262 inline comment should start with '# '
Line 352:1: E265 block comment should start with '# '
Line 388:13: E265 block comment should start with '# '
Line 393:121: E501 line too long (121 > 120 characters)
Line 403:121: E501 line too long (142 > 120 characters)
Line 465:44: E261 at least two spaces before inline comment
Line 468:73: E226 missing whitespace around arithmetic operator
Line 468:121: E501 line too long (157 > 120 characters)
Line 468:126: E226 missing whitespace around arithmetic operator
Line 475:48: E225 missing whitespace around operator
Line 476:60: E225 missing whitespace around operator
Line 505:1: E265 block comment should start with '# '
Line 525:13: E265 block comment should start with '# '
Line 532:121: E501 line too long (159 > 120 characters)
Line 533:77: E128 continuation line under-indented for visual indent
Line 564:33: E127 continuation line over-indented for visual indent
Line 594:40: E211 whitespace before '('
Line 613:20: E711 comparison to None should be 'if cond is not None:'
Line 650:33: E127 continuation line over-indented for visual indent
Line 677:40: E211 whitespace before '('
Line 685:16: E711 comparison to None should be 'if cond is not None:'
Line 688:25: E711 comparison to None should be 'if cond is not None:'
Line 710:20: E711 comparison to None should be 'if cond is not None:'
Line 794:41: E211 whitespace before '('
Line 806:41: E211 whitespace before '('
Line 813:27: E711 comparison to None should be 'if cond is not None:'
Line 814:27: E711 comparison to None should be 'if cond is not None:'
Line 826:9: E265 block comment should start with '# '
Line 845:13: E265 block comment should start with '# '
Line 850:21: E711 comparison to None should be 'if cond is not None:'
Line 852:21: E711 comparison to None should be 'if cond is not None:'
Line 877:1: E265 block comment should start with '# '
Line 889:26: E225 missing whitespace around operator
Line 911:80: E703 statement ends with a semicolon
Line 912:48: E226 missing whitespace around arithmetic operator
Line 940:5: E265 block comment should start with '# '
Line 986:26: E211 whitespace before '('
Line 993:41: E211 whitespace before '('
Line 995:36: E261 at least two spaces before inline comment
Line 997:48: E225 missing whitespace around operator
Line 1010:26: E211 whitespace before '('
Line 1037:9: E125 continuation line with same indent as next logical line
Line 1043:121: E501 line too long (140 > 120 characters)
Line 1047:9: E265 block comment should start with '# '
Line 1049:40: E211 whitespace before '('
Line 1069:47: E211 whitespace before '('
Line 1069:121: E501 line too long (123 > 120 characters)
Line 1073:121: E501 line too long (127 > 120 characters)
Line 1107:30: E211 whitespace before '('
Line 1112:59: E211 whitespace before '('
Line 1116:1: E302 expected 2 blank lines, found 1


Update Paramiko

Paramiko is really old and currently has an issue with reading rsa keys
in the new format. While they haven't fixed this issue yet, it should be
updated to use the latest.
Signed-off-by: Will Johnson<EMAIL_ADDRESS>

@johnsonw looks like there are a few failing checks on this patch.

Looks like it failed to download a component:
error: component download failed for rust-std-x86_64-unknown-linux-gnu

Maybe I can kick it off again.

Looks like they passed this time.


Add Vsync

What feature do you want to get added on the base engine?
Add Vertical Sync to the graphics settings, they fix screen tearing but they impact on performance, trust me I get screen tearing in the engine
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor, 6K+ support, and winning icons.

long story short: you can't, the game engine limits you because VSync is tied to the compilation of the game, there's ways around the issue but most of them involve messing with the compiler, and it would force you to restart the game every time you change the setting

force it through your graphics card settings

Project.xml hmmm how do i find this
On Fri, Nov 3, 2023 at 10:19 PM CharlesCatYT @.***>
wrote:

there is a configuration for VSync in the window settings in Project.xml
[image: image]
https://user-images.githubusercontent.com/62410083/280439813-198fd9f7-fa8c-4295-a434-38826dcbfab6.png
but either way, since VSync is tied to the compilation, you should at
least force it through the configurations of your GPU
—
Reply to this email directly, view it on GitHub
https://github.com/ShadowMario/FNF-PsychEngine/issues/13457#issuecomment-1793306857,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYXIAF3WZA3SYDDEXOWVJ3DYCWQ4FAVCNFSM6AAAAAA6BIFI7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTGMYDMOBVG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

I hear there are window settings, that should probably fix low texture quality in full screen when I change it

On flixel, you can't change VSync in mid-game/runtime.


Simplify code for emitting comments.

Also, always emit pinned comments, even when the 'removeComments' compiler
option is provided.

:+1:

Why do we ever force the removal of non-pinned/triple-slash comments instead of just respecting the compiler flag?


Freecam switches when closing gamemode switcher (F3+F4)

When I use the gamemode switcher (F3+F4) and then release the F3 key, the freecam also switches on/off. I'm not sure whether F4 is the default key for toggling Freecam, but at least with my configuration this happens.
I don't think that this is intended behavior, and it should be possible to fix.

I've reproduced this on Freecam 1.2.0 (old version) and also 1.2.3 (latest version).
This only happens when releasing F3 before F4.
The intended way to use the gamemode switcher is to hold F3 like a modifier key and then tap F4 before releasing F3.
Notably, holding F4 and tapping F3 does not activate the gamemode switcher at all.
When used as intended, the gamemode switcher does not toggle Freecam.
It's also harder to reproduce this issue on the latest Freecam versions because #126 introduced a half-second timeout for how long F4 can be held before it is ignored.
If this issue is bothering you, there's a few workaround:

Change Freecam's toggle key mapping
Use gamemode switcher in the "intended" way (release F4 first)
Hold F4 for at least half a second (10 ticks)

I'll look into a proper solution, but this might end up being marked as "won't fix".

I've reproduced this on Freecam 1.2.0 (old version) and also 1.2.3 (latest version).
This only happens when releasing F3 before F4.
The intended way to use the gamemode switcher is to hold F3 like a modifier key and then tap F4 before releasing F3.
Notably, holding F4 and tapping F3 does not activate the gamemode switcher at all.
When used as intended, the gamemode switcher does not toggle Freecam.
It's also harder to reproduce this issue on the latest Freecam versions because #126 introduced a half-second timeout for how long F4 can be held before it is ignored.
If this issue is bothering you, there's a few workaround:

Change Freecam's toggle key mapping
Use gamemode switcher in the "intended" way (release F4 first)
Hold F4 for at least half a second (10 ticks)

I'll look into a proper solution, but this might end up being marked as "won't fix".

For me it's kind of the opposite. When using the gamemode switcher normally, as you have described, it actuall still triggers the freecam for me.

When using the gamemode switcher normally, as you have described, it actuall still triggers the freecam for me.

Strange.  Could you let me know what versions you're using?

Freecam (e.g. 1.2.3)
Minecraft (e.g. 1.20.4)
Mod platform (e.g. Fabric)

When using the gamemode switcher normally, as you have described, it actually still triggers the freecam for me.

Strange.  Could you let me know what versions you're using?

Freecam (e.g. 1.2.3)
Minecraft (e.g. 1.20.4)
Mod platform (e.g. Fabric)

I only don't know the version of the mod. I'll check once I'm home.

When using the gamemode switcher normally, as you have described, it actuall still triggers the freecam for me.

Strange. Could you let me know what versions you're using?

Freecam (e.g. 1.2.3)
Minecraft (e.g. 1.20.4)
Mod platform (e.g. Fabric)

Freecam: 1.2.1
Minecraft: 1.20.1
Mod platform: Quilt 0.23.1


Mono: Fixes annotated signal loading in exported binaries

Fixes #19563 can you review this @hpvb. I've tested on windows 10 so far so good.

Please squash the commits together, see http://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html#mastering-the-pr-workflow-the-rebase

@akien-mga I have no idea how to rebase this when git forced that merge with master as it won't show all changes. Should I just create a new branch with the changes based off master?

If you squash and rebase exts:export_signals on top of godotengine:master, it should have all changes included in the squash commit, which you can force push to exts:export_signals.

Man I screwed something up because like I said when I rebased HEAD~10 it did not show anything after https://github.com/godotengine/godot/pull/19872/commits/54eb4a38b4bfb5dbce6e2e7e5614b1dc2e6e18cc this commit.  I'm just going to create a new PR this is frustrating.

LGTM

Alright I believe I made the necessary changes you requested @neikeq

Thanks!


test(interval): 🧪 use shorthand Size constructors

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1121

Relevant Lines:
1121

💛  - Coveralls


do not enforce optimizations

Thanks for the patch!
The code in place currently is a short-term fix to a bigger problem: OpenCV, in the current ROS version, does not compile if you have architecture flags on.
Do you think you could change this to use the user CFlags without the machine flags?

do you mean -march and -mtune?

Yeah, those. Super obnoxious that it breaks things, but it does.

totally unsure about this, can I have a sample of a build failure?

Other than that, this looks good. Much better than what I had.


EXC_BAD_ACCESS at getColorCode

In method (from UIImage+FloodFill.m)
In iPhone its working like charm but when I tried it on iPad its giving error EXC_BAD_ACCCESS exception in getColorCode method.
I'm getting error on "unsigned int red   = imageData[byteIndex]" line.
Suggestion in #23 not worked at all.

Hi,
I am getting issue too when filling with color. On the same row.
And it returns thread issue, how have you fixed this problem for you?


Download Bug

https://twitter.com/AndrejArh/status/753657512407228416

There is no bug, it works fine. :)

Thanks, going to close this as I also couldn't sort it out :/


quic: move quic flags to use envoy runtime API

Commit Message: Before this change, QUIC flags are directly fetched from the flag list. This change introduced a layer of indirection at Envoy Runtime. This enables us to override quic reloadable flags during runtime.
Additional Description:
Risk Level: Low
Testing: unit test
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A
Fixes #9435

/retest

Seems like https://github.com/envoyproxy/envoy/pull/16151 implements the alternate approach.

Closing this one since #16151 has merged.


chore: bdd-spring-1587760243 to 0.0.1

chore: Promote bdd-spring-1587760243 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


M365 Defender Connector - Missing Consent - Invalid License

Testing environment in a new environment with M365 E5 licenses enabled. I believe I might be missing either a license to enable the Azure Sentinel data connector or maybe just a few settings in MDE to enable the connection with the SIEM

We had similar problem. Activated E5 preview, which made the License available under the same pane as the one you screenshotted.
However we still experience:
{
    "status": "Failed",
    "error": {
        "code": "InvalidLicense",
        "message": "Missing consent"
    }
}

I suspect it may be related to the template also trying to configure the 'Advanced Hunting', which require the M365 defender preview connector - but not sure.
@Cyb3rWard0g : Were you able to resolve the issue?

@Cyb3rWard0g @ReneRebsdorf I am experiencing the same issue with postman.
{
    "error": {
        "code": "InvalidLicense",
        "message": "Missing consent"
    }
}

I assume that you both are using the api-version=2020-01-01 correct? @ReneRebsdorf, the json response that you provided is slightly different.
I had tried this api back in 8/20/2021 when I was integrating the other Microsoft data connectors. I was able to connect O365 just fine.

@julivanespi Yes we are using the 2020-01-01 API.
Our bicep template looks like this:
resource mdatp 'Microsoft.SecurityInsights/dataConnectors@2020-01-01' = {
  scope: logAnalytics
  name: 'mdatp'
  kind: 'MicrosoftDefenderAdvancedThreatProtection'
  properties: {
    tenantId: tenantId
    dataTypes: {
      alerts: {
        state: 'Enabled'
      }
    }
  }
}

This the template we use btwe: https://github.com/OTRF/Microsoft-Sentinel2Go/blob/master/microsoft-sentinel/linkedtemplates/data-connectors/allConnectors.json
I use API version 2019-01-01-preview since that's what the portal was using when doing it manually. I just tested it again today and it worked fine:

@julivanespi @ReneRebsdorf @Dabuek are you still having issues with the data connectors?

@Cyb3rWard0g I'll make sure to test next week.

@Cyb3rWard0g
Strangely I still I am unable to get it to work, I tried API versions:

2019-01-01-preview
2020-01-01
2021-03-01-preview
2021-09-01-preview

Still gives error:
{
    "status": "Failed",
    "error": {
        "code": "InvalidLicense",
        "message": "Missing consent"
    }
}

If I enable the the connector manually and run the code I do not get the error, but this is not ideal for initial configuration, nor for dev environments.
Bicep template is the same as in my reply from the 14th of December 2021 in this thread
Is there perhaps something else you've been able to do, that resolved the issue for you?

The weird thing is that it works sometimes and sometimes it doesn't. 🤔

I contacted Microsoft support about this and they confirmed it is a current limitation but have no immediate solution.
The issue is related to an additional API call that to the security API that enables the Sentinel integration on the Defender end. As soon as this setting is enabled you can deploy without issue, but the bicep or arm deployment will fail if it is not set correctly.

I contacted Microsoft support about this and they confirmed it is a current limitation but have no immediate solution.
The issue is related to an additional API call to the security API, that enables the Sentinel integration on the Defender end. As soon as this setting is enabled you can deploy without issue, but the bicep or arm deployment will fail if it is not set correctly.

I wonder if this call could be made using a deploymentScript?
Ugh, this sounds like things the backend should take care of for us.
We declare what we need through a template, and the resource provider should take care of dependencies...

I contacted Microsoft support about this and they confirmed it is a current limitation but have no immediate solution.
The issue is related to an additional API call to the security API, that enables the Sentinel integration on the Defender end. As soon as this setting is enabled you can deploy without issue, but the bicep or arm deployment will fail if it is not set correctly.

Hello @f-bader ! Thank you for the additional information. Do you remember who you talked to about it? I will send a private message to get more information and see if we could expedite something on our end. Thank you in advance!

MicrosoftThreatProtection
{"error":{"code":"InvalidLicense","message":"License is invalid"}}
401
Getting same error here , I am using below api-version=2022-07-01-preview  . I am deploying it using invoke-azrestMethod
Any update on this.

Hi Team, any update on the same a we are also facing the same problem
MicrosoftAdvanceedThreatProtection
{"error":{"code":"InvalidLicense","message":"License is invalid"}}
401

Same when deploying from Terraform. @Microsoft any clowns available in the MSFT circus to look at this ?
Anyone with a workaround ?

@microsoft We also experience this issue for the following data connectors: 'MicrosoftThreatProtection' and 'MicrosoftDefenderAdvancedThreatProtection'. It seems that this issue is open for a long time and there is no solution still.
Same issues:

https://techcommunity.microsoft.com/t5/microsoft-sentinel/quot-missing-consent-invalid-license-quot-defender-for-endpoint/m-p/3027212
https://github.com/Azure/Azure-Sentinel/issues/5007

Next to this issue I see almost no development on the data connectors API, is there some news to be spread how to enable data connectors automated in the future, since it seems to be moving to Content Hub. It is hard to find any docs about how to deploy this for example via Bicep!?

@AlfredSchreuder
I have raised another support issue but got the same response not supported...
https://github.com/Azure/Azure-Sentinel/issues/9986#issuecomment-2082325311


Add uframe glider track routes

Adds glider tracks route for uframe.

do not merge due to get_json change. going to keep original get_json


Changes required to remove ASID as the Service ID in HealthcareService FHIR resource

Further investigation into the use of SDS and SSP for routing has highlighted that the ASID cannot be more granular than org level i.e. it cannot be used below ODS org code level, and so not usable for specific services below.
Therefore it has been decided that for this API to work another lower-level service id must be used from an agreed service directory.  In the case of UEC Appointment Booking in the pilot we will use the DOS Service ID.
The updates in this pull request reflect the required changes.

Updated incorrect example profile in appointment.md


Use cargo insta in CI

I'm sure it's intentional to not run everything in CI. I felt it might be helpful especially for the CLI to fully run.

Have you considered using nextest? For rye's small test suite the difference isn't big yet, but for uv it makes difference.
$ hyperfine --runs 5 "cargo nextest run" "cargo test"
Benchmark 1: cargo nextest run
  Time (mean ± σ):     11.164 s ±  0.091 s    [User: 7.781 s, System: 2.562 s]
  Range (min … max):   11.088 s … 11.313 s    5 runs

Benchmark 2: cargo test
  Time (mean ± σ):     17.686 s ±  0.532 s    [User: 7.825 s, System: 2.837 s]
  Range (min … max):   16.968 s … 18.447 s    5 runs

Summary
  cargo nextest run ran
    1.58 ± 0.05 times faster than cargo test

Have you considered using nextest? For rye's small test suite the difference isn't big yet, but for uv it makes difference.

I haven't used nextest yet personally, although I've known of it. I've been playing around a little bit with the uv tests just to look around, and I've liked nextest so far.
I'd be happy to add to check that out for this PR.

I would prefer that the CI invokes a makefile command. Other than that we can try this.


Vitality Pack Overflow error when dropping VIT boosting item

When trying to drop a VIT boosting item (Of Fury), with max VIT, I received a "Vitality Pack Overflow" error
Confirm Transaction
TRANSACTION DETAILS
drop
FEE ESTIMATION FAILED
RPC: starknet_estimateFee with params { "request": [ { "type": "INVOKE", "sender_address": "0x41fba169d9d499aa00efd623f0eadefd32bb53282015af0cc1985a7bd56d6fd", "calldata": [ "0x1", "0x6895c9bf18e1070eba58fc23dede9e23f0e883aac61852d40ae75218b3debe2", "0x3297c61b5c92ef107ffd30cd56affe5a273e841d202d87dff9baf0090116b99", "0x3", "0x52", "0x1", "0x14" ], "version": "0x100000000000000000000000000000001", "signature": [], "nonce": "0x0", "max_fee": "0x0" } ], "block_id": "pending", "simulation_flags": [ "SKIP_VALIDATE" ] } 41: Transaction execution error: {"execution_error":"Error in the called contract (0x041fba169d9d499aa00efd623f0eadefd32bb53282015af0cc1985a7bd56d6fd):\nError at pc=0:10379:\nGot an exception while executing a hint: Execution failed. Failure reason: 0x766974616c697479207061636b206f766572666c6f77 ('vitality pack overflow').\nCairo traceback (most recent call last):\nUnknown location (pc=0:351)\nUnknown location (pc=0:3593)\n\nError in the called contract (0x06895c9bf18e1070eba58fc23dede9e23f0e883aac61852d40ae75218b3debe2):\nExecution failed. Failure reason: 0x766974616c697479207061636b206f766572666c6f77 ('vitality pack overflow').\n","transaction_index":0}
Work around is to move item to bag and then drop it

Also experienced this during a beast battle when trying to drop all items:
Confirm Transaction
TRANSACTION DETAILS
drop
FEE ESTIMATION FAILED
RPC: starknet_estimateFee with params { "request": [ { "type": "INVOKE", "sender_address": "0x41fba169d9d499aa00efd623f0eadefd32bb53282015af0cc1985a7bd56d6fd", "calldata": [ "0x1", "0x6895c9bf18e1070eba58fc23dede9e23f0e883aac61852d40ae75218b3debe2", "0x3297c61b5c92ef107ffd30cd56affe5a273e841d202d87dff9baf0090116b99", "0xa", "0x52", "0x8", "0x48", "0x4d", "0x52", "0x57", "0x5c", "0x61", "0x2", "0x7" ], "version": "0x100000000000000000000000000000001", "signature": [], "nonce": "0x0", "max_fee": "0x0" } ], "block_id": "pending", "simulation_flags": [ "SKIP_VALIDATE" ] } 41: Transaction execution error: {"execution_error":"Error in the called contract (0x041fba169d9d499aa00efd623f0eadefd32bb53282015af0cc1985a7bd56d6fd):\nError at pc=0:10379:\nGot an exception while executing a hint: Execution failed. Failure reason: 0x737472656e677468207061636b206f766572666c6f77 ('strength pack overflow').\nCairo traceback (most recent call last):\nUnknown location (pc=0:351)\nUnknown location (pc=0:3593)\n\nError in the called contract (0x06895c9bf18e1070eba58fc23dede9e23f0e883aac61852d40ae75218b3debe2):\nExecution failed. Failure reason: 0x737472656e677468207061636b206f766572666c6f77 ('strength pack overflow').\n","transaction_index":0}


Comparison to PyTransit

Added curves for PyTransit to the figures where we are comparing to batman. Still working on a more general comparison to the Gimenez code, but you can see how much better we do in the figure showing the results for the N=15 nonlinear limb-darkening case.
Also started adding proofs to some of the equations.

Is this the Gimenez' computation?   It looks like starry is no longer being compared?

@ericagol That's right. PyTransit uses Mandel & Agol to do quadratic (top plot) and Gimenez to do arbitrary order limb darkening (bottom plot). For the bottom plot, I'm computing the PyTransit flux in a similar way to how we're doing it with limbdark: i.e., I'm fitting for the 15th order coefficients of the limb darkening law that best approximate the nonlinear law's intensity.

I removed the starry lines for now while I work on speeding up my code. I'll add them back in eventually.

Also, the last purple point is missing in the bottom plot because PyTransit keeps segfaulting on Travis. I spent several hours trying to debug this and then just gave up!

@ericagol Hmm, that's not the issue. My guess is the segfault is due to the code using 2-byte integers to index the arrays; these max out at about 33,000, so time arrays longer than that cause trouble. Let me see if I can force it to use larger integers.


ci: update base directory for sonar

TL;DR
Updated sonar-project.properties to specify the source directory for analysis.
What changed?
The sonar.sources property in the sonar-project.properties file has been uncommented and set to src/. This change directs SonarQube to analyze the source code located in the src/ directory.
How to test?

Run a SonarQube analysis on the project.
Verify that the analysis only includes files from the src/ directory.
Ensure that no files outside of the src/ directory are being analyzed.

Why make this change?
This change helps to focus the SonarQube analysis on the relevant source code by explicitly specifying the source directory. It prevents unnecessary analysis of non-source files, potentially improving the accuracy and efficiency of the code quality assessment.

Merge activity

Oct 11, 3:29 PM EDT: A user started a stack merge that includes this pull request via Graphite.


forward proxy mode: a connect is opened to the original site?

Problem Description
when i want to change a request but the URL has a port, it looks like the socket to the original host is still opened
Steps to reproduce the behavior:
$ mitmdump --flow-detail 3 -v -p 8080 -k -s helper-scripts/redirect_learn.py --ssl-insecure --set console_eventlog_verbosity:debug --listen-host <IP_ADDRESS>
Loading script helper-scripts/redirect_learn.py
before request
Proxy server listening at http://<IP_ADDRESS>:8080
<IP_ADDRESS>:34864: clientconnect
<IP_ADDRESS>:34864: request
  -> Request(GET www.popularsite.de:80/)
starting request flow
FQDN Name to redirect:www.popularsite.de
url pfad:/
replaced path to redirect:/
<IP_ADDRESS>:34864: Set new server address: www.popularsite.de:80
<IP_ADDRESS>:34864: serverconnect
  -> ('www.popularsite.de', 80)
<IP_ADDRESS>:34864: response
  -> Response(200, text/html, 10k)
<IP_ADDRESS>:34864: GET http://www.popularsite.de/
    Host: www.popularsite.de
    User-Agent: curl/7.58.0
    Accept: */*
    Proxy-Connection: Keep-Alive
 << 200 Coming Up 10k
    Accept-Ranges: bytes
    Server: Gatling/0.16
    Content-Type: text/html
    Content-Length: 10240
    Date: Fri, 11 Dec 2020 13:06:02 GMT
    Last-Modified: Thu, 26 Nov 2020 15:42:24 GMT
    Connection: keep-alive
<IP_ADDRESS>:34864: serverdisconnect
  -> ('www.popularsite.de', 80)
<IP_ADDRESS>:34864: clientdisconnect
<IP_ADDRESS>:34866: clientconnect
<IP_ADDRESS>:34866: Set new server address: internal.domain.private.tld:9988
<IP_ADDRESS>:34866: Establish TLS with client
<IP_ADDRESS>:34866: ALPN for client: b'http/1.1'
<IP_ADDRESS>:34866: Failed to send error response to client: ProtocolException('Server connection to (\'internal.domain.private.tld\', 9988) failed: Error connecting to "internal.domain.private.tld": [Errno 111] Connection refused')
<IP_ADDRESS>:34866: CONNECT internal.domain.private.tld:9988
    Host: internal.domain.private.tld:9988
    User-Agent: curl/7.58.0
    Proxy-Connection: Keep-Alive
 << Server connection to ('internal.domain.private.tld', 9988) failed: Error connecting to "internal.domain.private.tld": [Errno 111] Connection refused
<IP_ADDRESS>:34866: clientdisconnect

I first open popularsite which is not changed, and everything works. but  when i go to internal.domain.private.tld which i want to connect to another IP and Host, it still opens a socket to that fqdn, which will not work.
i think this only happens, if there's a port in the URL. what can i do to stop that? is there a bug? is there an example, how to change this before openeing the socket?

This is also the case, when the scheme is https and therefore the port is 443 instead of 80?

It's not really clear what you are trying to do here, what does your script look like?


error in tf.concat

Hi I was trying the example you gave with an image size of (none, 128, 128, 3)
it's giving an error here:
tf.concat(1, [convSummary, miniBatchSummary])
Shapes (2, ?, 1) and () are incompatible
also, I didn't understand why are you concating with 1!! please let me know if I am missing something!!

Hi I was trying the example you gave with an image size of (none, 128, 128, 3)
it's giving an error here:
tf.concat(1, [convSummary, miniBatchSummary])
Shapes (2, ?, 1) and () are incompatible
also, I didn't understand why are you concating with 1!! please let me know if I am missing something!!

I think it should be tf.concat([convSummary, miniBatchSummary], axis = 1)

This small demo is based on a tensorflow version that is quite old. The API has changed quite a bit since then, especially with the move to 2.0. I suspect that's the source of the issue, but don't have the time to really dig into at the moment.
Thanks for the suggestion.


Add debt package

Resolves #53
New classes added:
Debt
Description, Money
New test classes added:
DebtTest, DescriptionTest, MoneyTest
New test utility classes added:
DebtBuilder, TypicalDebts
Notable implementation details:

The money parameter can accept negative numbers, should I disable this?
Edit: This has been disabled.
The description parameter can only accept alphanumerics, not sure how to work the regex to accept anything that is not only whitespace.
Comment: Probably best to open a new low priority issue for v1.2b on reworking this (if needed) so we can quickly start working on the new commands that are dependent on Debt.
2 Debt objects are "equal" if their description and money amount are equal, we may need to implement additional measures of equality if someone wants to add multiple debts of the same description and money to a person (eg the guy (non-binary) eats the same meal at mcdonalds everyday and uses your money every time)

For point 1, I think we should not accept negative values of money. If we wish to extend to the user's own debts, we can make another class called credit, or something similar.
For point 2, try "^\S.$" , or "^\S.$" if Java needs another escape character. This should accept any non-null string input. You can refer to https://regex101.com/ to craft and experiment with regex.

@WR3nd3 The regex you provided does not work, the following test cases will fail:
assertTrue(Description.isValidDescription("McDonald's")); // contains non-alphanumeric characters
assertTrue(Description.isValidDescription("^")); // only non-alphanumeric characters

Codecov Report
Base: 72.15% // Head: 71.93% // Decreases project coverage by -0.22% :warning:

Coverage data is based on head (119f1b4) compared to base (6a4bdb5).
Patch coverage: 65.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #61      +/-   ##
============================================
- Coverage     72.15%   71.93%   -0.23%
- Complexity      399      415      +16
============================================
  Files            70       73       +3
  Lines          1232     1272      +40
  Branches        125      130       +5
============================================
+ Hits            889      915      +26
- Misses          311      321      +10
- Partials         32       36       +4

Impacted Files
Coverage Δ

src/main/java/paymelah/model/debt/Description.java
60.00% <60.00%> (ø)

src/main/java/paymelah/model/debt/Money.java
60.00% <60.00%> (ø)

src/main/java/paymelah/model/debt/Debt.java
70.00% <70.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@WR3nd3 @TheSoggy Found something that works, let me know if you want to add any test cases to DescriptionTest. Should resolve #62?


[Bug report]:

Version
1.0.0
Description
Today I managed to migrate my IOTA funds to Stardust. The backup password was saved in Notepad format and the file won't load to recover my funds. Please help me understand what I should do next. Thanks in advance! Best regards, Rodica
Expected behaviour
I don't know what should have opened.
Actual behaviour
The SeedVault backup password, saved in Notepad, is not loading.
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
I need to convert the Notepad document to .kdbx format, but I don't know how. I need help. Please
Operating System
Windows
Diagnostics
Version 1.0.0
Language: en
Currency: USD
Node selection: Automatic
Platform: win32
Platform Version: 10.0.22631
Platform Architecture: x64
CPU Count: 2
Total Memory: 8001.7 MB
Free Memory: 2610.3 MB

Profile Type
Software (Stronghold)
Crash Status
None of the above
Error Messages
Version 1.0.0
Language: en
Currency: USD
Node selection: Automatic
Platform: win32
Platform Version: 10.0.22631
Platform Architecture: x64
CPU Count: 2
Total Memory: 8001.7 MB
Free Memory: 2610.3 MB
Error Logs

Duplicate declaration

[x] I have searched the issues tracker this issue and there is none

Code of Conduct

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

Hello @begonaalvarezd  A support ticket has been opened for you. Kindly Talk to Support on the Live support page so that your issue can be looked into. CLICK HERE


Establishing connection without knowing remote Public Key

This is in context of IPFS
I'm looking for a way to establish a connection to the swarm (ipfs swarm connect "/ip6/${addr}/tcp/4001/ipfs/${pubkey}") without knowing the pubkey.
Reason:
Im looking at a way to establish a swarm connection in an offline environment (where bootstraps cannot be reached) in a mesh like network where neighbours nodes are known (such as CJDNS, Yggdrasil or ip6 neighbor where a list neighbor peers are available)
Currently to establish a connection there needs to be an out-of-band method of communicating the public peer of the remote node (example Code being used now)
I looked at DNSADDR as a method of establishing connections without the need of known public keys however

IP Addresses are attempted to be resolved by DNS :-1:
It was mentioned that a TXT record is still required holding the public key :confused: (Does not read so in the docs, not sure if this is accurate)

Keeping things in-band would allow peering of nodes without 3rd party software needed to be run.
Possible solutions:

Learn of public key via some sort of handshake. IE connect to remote server and ask it for its pub key
Some sort of multi-address that would not require pub keys to establish a connection
Other suggestions ??

REF: https://github.com/tomeshnet/prototype-cjdns-pi/issues/177

Note that this is more of an implementation issue. Rust-libp2p allows doing that.

Note that this is more of an implementation issue. Rust-libp2p allows doing that.

I wasn't sure if this was the right place to put it.  I'm not sure which implementation IPFS uses. Im going to guess GO-IPFS ?
Should this topic be moved to the go-libp2p implementation?

Should this topic be moved to the go-libp2p implementation?

Probably. Unfortunately, fixing it is a bit tricky and probably won't happen for a while, if ever, as all the interfaces are built around connecting to peers by peer ID. Hacking in a fix would be easy but finding a nice way to fit this into the current abstractions is not.

Maybe a "easier" work around would be to have some how make the pubkey available? Maybe a udp broadcast asking for active IPFS servers, and a response with the pubkey.

Actually, that brings up a good point, does MDNS not work over CJDNS? That's our current discovery protocol.
Otherwise, you could hack together a tool that directly connects to a node and asks for it's public key, then turn around and use it to connect to that peer. However, that's not exactly efficient (but probably not an issue given the use-case).

Im not sure what the status of MDNS is in IPFS, i know when i looked at it, it was not working.
As for a hacked together tool, Yes that would be better then what we currently have.   However i'm not sure what the IPFS protocol is, is there any docs on it or point to a place in the code i can reverse engineer it?

is this topic cannot be a security breach?


[SSR] (docs) show Lit html dependency in SSR docs examples

Not sure if intentional, but noticed that the SSR examples weren't showing where the html tagged template comes from, which presumably was meant to be from the lit package, e.g.
import {html} from 'lit';

As a side-effect, there was already an const html = ... variable being used in the examples, so just to avoid confusion, renamed it to const contents = ..., but I am happy to change it whatever you would prefer.

/gcbrun


TypeError: Cannot read property 'targetId' of undefined

More info:
https://sentry.comunes.org/democracy-earth/votest-democracy-earth/issues/761/
TypeError: Cannot read property 'targetId' of undefined
  at targetId (meteor://💻app/imports/ui/templates/components/decision/fork/fork.js:212:89)
  at None (/packages/blaze.js:3775:20)
  at Function.Template._withTemplateInstanceFunc (/packages/blaze.js:3744:12)
  at Blaze.View.<anonymous> (/packages/blaze.js:3774:25)
  at None (/packages/blaze.js:2617:30)
...
(6 additional frame(s) were not displayed)

More related errors:
https://sentry.comunes.org/democracy-earth/votest-democracy-earth/issues/745/


Prep for alpha release

This PR includes changes to prepare for an alpha release. I have been using the source branch for this PR to test release tooling. Current release testing results:

Github pages web site: https://frreiss.github.io/tep-fred/
Github repo page: https://github.com/frreiss/tep-fred/tree/branch-alpha
Package: https://test.pypi.org/project/text-extensions-for-pandas/0.1a4/

Main changes in this PR:

Created a (stub) web site for Github pages under docs  (Github pages requires the web site to be either at the root of the repo or in a subdirectory called docs)
Moved the API docs that used to be at docs to api_docs
Fixed some minor problems with project metadata
Rewrote most of README.md
Created a readme for the PyPI page: package.md

Merging these changes to master as soon as CI finishes.


Error in subpopulations (missing/duplicated) of downloaded data (v2)

What you did:
I downloaded the gnomAD data for the genes listed above from v2.1.1 website by going to the "export variants to csv" button
e.g., https://gnomad.broadinstitute.org/gene/ENSG00000117400?dataset=gnomad_r2_1
What you expected to see after you did that:
<!-- I opened up the document downloaded using excel and reviewed the subpopulations for the variant.

### What you actually saw after you did that:

<!--I expected there to be all the subpopulations listed. However, the african american subpop data was listed twice and the latino/admixed subpopulations were missing.

<!--

Any of the following information will be helpful:

[gnomAD_v2.1.1_ENST00000372470_2024_01_22_11_42_42.csv](https://github.com/broadinstitute/gnomad-browser/files/14013728/gnomAD_v2.1.1_ENST00000372470_2024_01_22_11_42_42.csv)

[gnomAD_v2.1.1_ENST00000268206_2024_01_22_12_54_51.csv](https://github.com/broadinstitute/gnomad-browser/files/14013741/gnomAD_v2.1.1_ENST00000268206_2024_01_22_12_54_51.csv)

Hiya @michellepaczosa, thanks for filing this issue. Could you take a look at this issue filed recently #1393 and see if that encompasses the issue? If so, I'll close this issue as a duplicate in favor the #1393. Let us know!
Thanks

Hi,
Thank you for reaching out. Yes, that ticket appears to be for the same
issue I created a ticket for.
Thanks,
Michelle
On Mon, Jan 22, 2024, 3:51 PM Riley Grant @.***> wrote:

Hiya @michellepaczosa https://github.com/michellepaczosa, thanks for
filing this issue. Could you take a look at this issue filed recently
#1393 https://github.com/broadinstitute/gnomad-browser/issues/1393 and
see if that encompasses the issue? If so, I'll close this issue as a
duplicate in favor the #1393
https://github.com/broadinstitute/gnomad-browser/issues/1393. Let us
know!
Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/broadinstitute/gnomad-browser/issues/1394#issuecomment-1904785609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A67VNYDPC5QXMEQ44C5MWNLYP3GNLAVCNFSM6AAAAABCFUA2A6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUG44DKNRQHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Great, thanks @michellepaczosa. We'll look into fixing this, and I'll close this issue as a duplicate of #1393.
Thank you!


Licencia PiOS (PiOS License)

https://github.com/Solido/awesome-flutter

@Hanzhafiz

https://github.com/Solido/awesome-flutter

[ ]
@Hanzhafiz


got an unexpected keyword argument 'items'

I've just installed it, getting an error when opening the app: posting.

macos
kitty terminal
python 3.12.3

Whoops! My bad.
1.0.0b39 was broken - I've yanked that release. 1.0.0b40 should fix the issue.

thanks! I'll give it a try, first impression is looking very good!
It is possible to create a custom theme?

Custom themes aren't possible yet but they will come soon

Custom themes aren't possible yet but they will come soon

may not be difficult to implement, right? a theme directory can be assigned for import the files, those files could export this data format: https://github.com/darrenburns/posting/blob/8da732112d7323bbad3e988adb84a925df6b5466/src/posting/app.py#L559
I've created themes for some well-known terminal apps. I'd like to create a port of my neofusion theme for posting.

Yup, should be pretty straightforward 🙂
This feature will probably arrive this week or next week.


autoconvert legacy VAEs

This draft PR implements a system in which if a diffusers model is loaded, and the model manager detects that the user tried to assign a legacy checkpoint VAE to the model, the checkpoint will be converted to a diffusers VAE in RAM.
It is draft because it has not been carefully tested yet, and there are some edge cases that are not handled properly.

Haven't run it but the code looks solid.

@lstein since this is 2.3, should we close it out?

@lstein since this is 2.3, should we close it out?

Just reviewed it again myself and it still works quite well. Minor quality of life improvement, but still...


Apply Kobo Forma's Fullscreen Reading CSS to older firmware's patch

As the title indicates, why not port kobo forma's no footer/header CSS to kao and other devices?

kao now has latest firmware, can be closed.


[BUG] Remove client track specific code coverage and javadoc build targets from the aggregate pom structure files

The root pom ./pom.xml was modified to have jacoco and javadoc build rules for client track libraries and every client track ServiceDirectory/pom.xml was modified to have jacoco build rules for client track libraries. The reason why this is a problem is that these now contain actual artifact tags for the plugins which do not get verified as part of the pom file verification because only things that have the pom client parent are verified due to too many random track 1 poms that we can't verify. Because of this, there are issues with version updates not correctly being done which other people are running into that are causing a lot of confusion.
The root ./pom.xml and ServiceDirectory level pom.xml files are not supposed to contain anything other than aggregation which is to say everything in the  tags and nothing more.
The service directory pom files are being used to create the code coverage rollup and the root ./pom.xml is being used to also create a coverage rollup as well as a docs rollup. What needs to happen is something similar to what we're doing for the FromSource runs which is to generate the POM file on the fly. This will also eliminate the plugin version discrepancies. The generate_from_source_pom.py script is an example that should be close enough to steal most things from but since you're going to require a specific artifacts list, the usage of verify_release_set.ps1 inside of the archtype-java-release-batch.yml is a good example of passing in the full artifacts list to a script.

This appears to have been fixed by @srnagar with his changes in the following PR


Request for actively maintained fork of WordNet

Project description
There exists a better maintained fork of the original English WordNet from https://wordnet.princeton.edu/ over at https://github.com/globalwordnet/english-wordnet
Metadata

homepage URL: https://en-word.net/
source URL: https://github.com/globalwordnet/english-wordnet
license: CC-BY 4.0
platforms: unix, linux, darwin, ...

The package is unmaintained. The closest thing it has to a maintainer is @trofi.


Bump version

Codecov Report

Merging #156 (9239b3b) into main (480fee1) will decrease coverage by 1.36%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #156      +/-   ##
==========================================
- Coverage   90.95%   89.58%   -1.37%
==========================================
  Files          10       10
  Lines         829      826       -3
==========================================
- Hits          754      740      -14
- Misses         75       86      +11

Impacted Files
Coverage Δ

weather_command/_tui.py
59.74% <100.00%> (ø)

weather_command/main.py
80.00% <100.00%> (ø)

weather_command/_builder.py
95.49% <0.00%> (-4.51%)
:arrow_down:

weather_command/_weather.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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