Created separate column for init values (1 or more) and current value (singular value, old 'init_value')

This will allow us to specify multiple initial values for a given cell that we could use in a special MultiInitFeaturizer or MultiOccurFeaturizer.
The old init_value is now current_value (all featurizers have been changed to reference current_value and renamed from e.g. InitFeaturizer to CurrentFeaturizer).
Also fixed a bug in InitSimFeaturizer where it wasn't computing the similarity metrics correctly between the init_value and values in the domain.

Closing this to combine with #32.


Lists implementation is missing

Is it me, or is the lists implementation really missing?
https://www.google.com/design/spec/components/lists.html

Issue #584


Crash on app start for Android 6 users

Updated to 1.4.9 and synced 2 tags but I don't have tags with 800+ datapoints to confirm. Will have to wait.

QA passed, tested with tag over 830 datapoints


" Tusk takes advantage of the build-in Markdown support that lives inside the Evernote web editor."

I can't make markdown work, neither in evernote web, neither in Tusk.
It all just shows as plain text...

Apparently, the feature has been removed by Evernote itself, which means that we will have to implement ourselves. Progress can be tracked at #8.


"cosign initialize" doesn't work

I am trying to run cosign with a local TUF root. My understanding is that I should use the initialize command like this:
cosign initialize --root /local/tuf/repo/root.json

However this fails with:
Error: initializing root client: updating from remote TUF repository: updating tuf metadata: tuf: failed to decode timestamp.json: expired at 2021-12-02 15:41:56 +0000 UTC
main.go:46: error during command execution: initializing root client: updating from remote TUF repository: updating tuf metadata: tuf: failed to decode timestamp.json: expired at 2021-12-02 15:41:56 +0000 UTC

Running without --root:
cosign initialize
Error: updating local metadata and targets: updating tuf metadata: tuf: failed to decode timestamp.json: expired at 2021-12-02 15:41:56 +0000 UTC
main.go:46: error during command execution: updating local metadata and targets: updating tuf metadata: tuf: failed to decode timestamp.json: expired at 2021-12-02 15:41:56 +0000 UTC

It appears it always fetch stuff from GCS which has an expired timestamp. I know there is a --mirror flag which can override the default GCS location but I don't want to put my stuff of GCS.

cc @asraa might know more about this?

Fixed now -- cosigns updated with the latest root, but GCS isn't synced. I'll make a fix PR to auto-update it and tag you

But why do we need GCS in the first place? Why it's not possible to use local TUF root?

But why do we need GCS in the first place? Why it's not possible to use local TUF root?

cosign initialize is a manual fetch. You don't have to run it at all, you use the local TUF root during a cosign verification. cosign initialize is just our system of allowing users to manually updating/downloading in case they want to verify with a remote.

I am not sure I understand, so I will describe what I am trying to achieve.
I have a local instance of Fulcio and CT log. When I experiment with keyless signing, I am getting an error which says that SCT signature received from Fulcio cannot be verified. This is because cosign is using ctfe.pub from its embedded TUF repo. I want to change the TUF repo and provide my own ctfe.pub. I thought the way to do this is with cosign initialize. Is this correct?

Ah, sorry, didn't realize you wanted your entire own root!
Yes, you are correct in using cosign initialize. You actually need to provide you own entire TUF root -- that would mean
cosing initialize --root $YOUR_ROOT --mirror $YOUR_MIRROR
where your_root is your own trusted root.json and mirror is the corresponding TUF repository, a collection of metadata. It is expecting a timestamp.json, snapshot.json, targets.json and root.json and the target files.

I know there is a --mirror flag which can override the default GCS location but I don't want to put my stuff of GCS.

No one else has asked me to do this which is why I haven't but I can update this so mirror can also point to a local filesystem or can fetch from a server through HTTP. That will be a fairly quick fix (expect by end of day tomorrow).
On the other hand, are you comfortable setting up your own TUF repository? You may also need to include a rekor.pub by the way, but I can also make it so that if there's no rekor.pub in your repo, we use the embedded rekor.pub target.

No one else has asked me to do this which is why I haven't but I can update this so mirror can also point to a local filesystem or can fetch from a server through HTTP. That will be a fairly quick fix (expect by end of day tomorrow).

That would be great, thanks!

On the other hand, are you comfortable setting up your own TUF repository? You may also need to include a rekor.pub by the way, but I can also make it so that if there's no rekor.pub in your repo, we use the embedded rekor.pub target.

Not really, but I am trying :) My end goal is to have local instances of Fulcio, Rekor and CT log and make cosign work with them.

Not really, but I am trying :) My end goal is to have local instances of Fulcio, Rekor and CT log and make cosign work with them.

I would be happy to help! I use the go-tuf CLI but the python one's a lot more expressive. Please feel free to ping me on slack and I'll be happy to walk through examples and speak to limitations/ways to do stuff.

I have added support for fetching TUF root over HTTP with PR #1185. With this I have been able to initialize cosign without using GCS and make it work with my local instances of Fulcio and CT log.


Cannot fully override rule in Webpack config

Version
3.0.0-beta.6
Reproduction link
https://github.com/divyamrastogi/config-override-bug-demo
Steps to reproduce
Go to App.vue to see the loading of the SVG asset. The SVG contents is displayed in the view.
What is expected?
svg-sprite-loader is not being used (setup in vue.config.js) to process SVG files. The Star data property should be an object after being processed by this loader.
What is actually happening?
The SVG is still being processed with file-loader from the default Webpack configuration and is therefore returning a string. It appears the config makes no difference to the processing of the SVG.

You probably expected the merge to replace the file loader, but webpack-merge isn't that clever - it doesn't compare test regexp's to find which rule should be replaced, it simply appends the new rule to the array of existing ones.
So: You didn't remove the file-loader that already tests for .svg itself (this one). You add the svg-sprite-loader later, it's lower priority - so file-loader processes the file, and your loader never gets any work.
But you can use webpack-chain to remove the old loader and add yours in its place:
module.exports = {
  chainWebpack: config => {
    // remove the old loader
    config.module.rules.delete('svg')

    // add the new one
    config.module.rule('svg')
      .test(/\.(svg)(\?.*)?$/)
      .use
        .loader('svg-sprite-oader')
        .options({
          name: "[name]-[hash:7]",
          prefixize: true
        })

  }
}

Relevant webpack-chain docs:  https://github.com/mozilla-neutrino/webpack-chain#config-module-rules-uses-loaders-creating

@LinusBorg I see. It seems to work thanks. How would I go about applying multiple loaders in this way? Like, svg-fill-loader and svgo-loader too? Thanks.

I'm not familiar with those loaders, how would a "normal" config look like that uses them together?

@LinusBorg Maybe we should have a cookbook reciepe specifically for the SVG loader as this question seems to come up quite a lot. What do you think?

I haven't seen this question before, so I can't say much about the relevance. But feel free to make a suggestion for the cookbook!
I'll close this issue as the original question was answered. Further discussions canhappen on forum.vuejs.org or chat.vuejs.org


The Observation Reports for MarkLogic Feature Service is used by GeoEvent Services

The Observation Reports for MarkLogic Feature Service is used by GeoEvent Services that are going to be released. This service needs to be released or the GeoEvent Input/Outputs need to be removed.
As a reminder the nsecgee is not a development machine, it is for ready to release GeoEvent content.
Service Item id:bff0a7b237e946b385bc7223d8af5ae4 Map Service
Service Item id:e1786c4738b54473982b7f0b85453643 Feature Service

@conklinbd These items have been shared with the demo review folder
https://github.com/Esri/ops-server-config/issues/1024

@lfunkhouser for you to review and release.

#1212 depends on this issue.

@conklinbd @topowright Item descriptions say "Various spot reports over California...";however, there is only one and it is in the water by Monterey. Is this "as designed"?

Map service and feature service released by DemoIntelligence

Verified.


Sync between client cache and backend cache - only request whats needed

Currently this works but needs further emphasis on sync.
Issue is client caches too fast and updates its own without deleting - backend needs to do the same maybe flatten array of items, derive the currently manipulated item then change the values.


User statistics EditComment-[cr] is confusing

As far as I can tell, the count of EditComment-c and EditComment-r entries for a user is the same, with the first referring to log entries where the target is the comment id, and the second referring to the target being the request. Rather than showing both labels on the user statistics view, I suggest only showing one, and using a clearer "Edited a comment" description instead of the internal label

As a user,
When I view https://accounts.wmflabs.org/internal.php/statistics/users/detail?user=2059
Expected result:
...
Edited a comment | 7
...

Actual result:
...
EditComment-c | 7
EditComment-r | 7
...

Yeah, this is one of the side effects of an earlier bad design choice, where log entries can only "affect" one object type, and to avoid a large join between the log and comment tables to filter by request, we decided to duplicate the log entries. This sort of problem (where one log entry is relevant for multiple objects) is becoming more prevalent, and over the years we've chosen to work around it in several different ways - for instance sending reservations - and is actually one of the things that is planned to be fixed in #607 so I'm going to close this in preference to that issue.


Feature: Show all "Get Access" property options

Right now when you look at a property we display a Get Access option.

This would likely be interprited as the only option avaliable, but really there are other options avaliable this is just what we deem the ideal option.
Make these changes to the section matching the prototype.

Reword description text
Display the 6 panels as in the prototype

icon, heading, description, badge and right arrow icon (phosphor icons)

Label each panel with colored badges based on the data

Best Option, Available, Not Available

The "Purchase as Side Yard" is a special case. It should basically be static. It's always applicable, but just for neighborhoods.
Sort the panels in this order. Best Option, Avaliable, For Neighbors, and Unavaliable.
Color code the panels to match the badges
When you click on one of these send users to the get Access Page and ideally scroll them down the associated section

@thansidwell I'd like to be assigned this please.

Hey @AZBL, currently the data are stored in a few different columns. You may have to do some basic data manipulation in JS rather than work directly with the raw data as in the filters. Conservatorship, side yard eligibility, and quick cleaning are all individual columns (the latter corresponds to tactical_urbanism), while the other three options are all found in access_process. You might consider something like concatenating them as a list of strings before passing that to the component.

Hey @nlebovits I think I need some clarification on this ticket request. For this request are the 6 cards supposed to be dynamically rendered for each property based on data we have, or should the cards look identical to the above for each property?

@AZBL Each property should have 6 cards, BUT the badge, color, and order of them should change depending on whether that access method is available, unavailable, or the best option.

@moylena, I can take this one, please feel free to shift to "In Dev"

@moylena, I can take this one, please feel free to shift to "In Dev"

hey @thansidwell / @nlebovits, I'm double checking some of the logic and could use some clarifications:

Should the "best" option should be whatever the access_process is? (either "Private Land Use Agreement", "Land Bank", or "Buy Property")

There are a few properties where the "access_process" is "Do Nothing". How should we handle these properties?

if access_process is not "Private Land Use Agreement", should we display "Private Land Use Agreement" as "Unavailable?". Are there any cases where "Private Land Use Agreement" should be available, even if its not stated as the access_process?

if access_process is not "Land Bank", should we display "Land Bank" as "Unavailable?". Are there any cases where "Land Bank" should be available, even if its not stated as the access_process?

The sideyard is a bit confusing — the acceptance criteria said to just leave it static yellow for neighbors, but there is a filter option for "side_yard_eligible : No" — shouldn't we display the sideyard as "Unavailable" for those properties?

What should the "Quick Cleaning" link to on the /get-access page? Seems like everything has a logical match except for that one

@paulhchoi @nlebovits
I think the access process status is calculated by looking other data, and was meant to be the only thing we would display. Now we realize it's more useful and logical to show all the options and whether you can do them or not. I wonder if we need to rework or reinterpret the data in the database. I worry they are trying to infer things from a single calculation access process when we really should just have a data point for each of these get access options as well as a best option.

Yes, the "best option" is what's in the access process.
Perhaps when the access process is "do nothing" the other options will be "unavailable" so that will just imply or clarify that you can't do anything.
I don't think you can infer if it's available or unavailable from the get access data point. It sounds like we need to rework the data, and perhaps have a simple private land use agreement column in the database.
Same here.
Oh! I forgot about that. If it is truly unavailable then we should give it the "unavailable" status.
As I said in the pull request, we haven't written the panel for "Quick Cleaning/Tactical Urbanism." @nlebovits is primarily in charge of it.

@thansidwell Thanks for the detailed response! so for 2, say for property #252158600: https://vacant-lots-proj-git-paulhchoi-50-4c3690-clean-and-green-philly.vercel.app/find-properties/252158600, the data returned is:
{
    ...
    "OPA_ID": 252158600,
    ...
    "side_yard_eligible": "Yes",
    "tactical_urbanism": "Yes",
    ...
    "access_process": "Do Nothing"
}

so even though sideyard and quick cleaning is eligible, I should take access_process of Do Nothing as the most accurate, list Do Nothing as the best option, and overwrite everything else to be "Unavailable"?

@nlebovits @brandonfcohen1 @paulhchoi
To complete how we are displaying all the get access options, Paul has to make a lot of assumptions on the data in the database. See he comments above.
I wonder if we should just rework the database to better match the data shown on the front-end. Something like this perhaps?
private land use agreement: yes/no
lank bank: yes/no
buy affordably from owner: yes/no
side yard program: yes/no
tactical urbanism: yes/no
conservatorship: yes/no

@paulhchoi  To your question, I hadn't thought of that! If it is sideyard and quick cleaning elligable we should definately be displaying that. Perhaps access process could change to best access process and Do Nothing could change to None, because, in reality, there are options, there's just no ideal option.

@nlebovits @brandonfcohen1 @paulhchoi
We want to now show all the get access options.

But many of the options we don't have individual data points in the database. For some of them we only have `access process`. Which is really the `best access process`. Perhaps we change the name?
So Paul is wondering if and how he should make assumptions on many of them based on that one data point?
I wonder if we should just rework the database to better match the data shown on the front-end. Something like this perhaps?
private land use agreement: yes
land bank: no
buy affordably from owner: no
side yard program: yes
tactical urbanism: yes
conservatorship: no

best access process: private land use agreement

will let @nlebovits answer this

Yes, we can/should rewrite the pipeline to make the database format more consistent with our new needs. @brandonfcohen1 and I can work on that this summer, along with several other changes I want to make.
The idea of the data structure was to keep mutually exclusive data in the same column, e.g., if a property is eligible for purchase from a private holder, it is by definition not available through the land bank. There is some ambiguity around this in terms of purchase vs. private land use agreement, which technically aren't mutually exclusive. But bear in mind that this tool is primarily aimed at community groups who likely will find purchases of over $1,000 financially impossible, even if they're technically feasible.
I'll pull my comment from above, which could be off base, but is how I would approach this:

Currently the data are stored in a few different columns. You may have to do some basic data manipulation in JS rather than work directly with the raw data as in the filters. Conservatorship, side yard eligibility, and quick cleaning are all individual columns (the latter corresponds to tactical_urbanism), while the other three options are all found in access_process. You might consider something like concatenating them as a list of strings before passing that to the component.

Also, @paulhchoi please change "Quick Cleaning" to "Tactical Urbanism". @thansidwell and I have talked about this and I think the correct step here is to use the technical term so that people who aren't familiar with the concept and the risks entailed don't get the impression that they can just go trespassing left and right.

closed by #538 and #551


Updated 'else' block of the advanced code solution

Current solution:
function truncateString(str, num) {
if (str.length <= num) {
return str;
} else {
return str.slice(0, num > 3 ? num - 3 : num) + '...';
}
}
Updated solution:
function truncateString(str, num) {
if (str.length <= num) {
return str;
} else {
return str.slice(0, num) + '...';
}
}
Description: The current code does not satisfy the below tests:
truncateString("A-tisket a-tasket A green and yellow basket", 8);
truncateString("Peter Piper picked a peck of pickled peppers", 11);

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@RandellDawson are you able to review and merge this pull request, please

The changes look good, but I still need to test locally before merging.  Also, with the current Pull Request backlog, you may not see a merge for a long time (1-2 months).

@hyfzur Sorry but there was already another solution merged.


[GPII-3865]: Refactor organization permission management, second try

This PR contains changes from #366 plus couple additional fixes:

It adds missing organizationAdmin role to the common SA (required to remove IAM policy bindings)
It separates :set_billing_org_perms task, with updated comments and variable piping

lgtm

You didn't specify, but I assumed the xk_infra.rake changes are the same as the last PR

@mrtyler Your assumption is correct.

You didn't remove the :

@mrtyler Ouch: https://github.com/gpii-ops/gpii-infra/pull/384

Wait, this is not the PR. Where is this comment?

What do you mean?

The comment was attached to a commit in the PR -- check out  the header on my previous comment. Anyway it looks like it worked fine. I hadn't seen that particular UI before.


Extension not loaded properly right after install

On VS Code, ensure the extension is not installed.
Go to extension page, and install the extension.
Observe the Confluent extension logo shows up on left nav.
Click on the extension logo to open the extension.
Observe the extension is not properly loaded.
Close VS Code and reopen.
Observe the extension is now properly loaded.

Happens when installing from extension marketplace as well as sideloading .vsix.

Thanks for filing this @derek1ee, I think there's definitely some deactivation-related cleanup we're missing since @Cerchie also saw odd behavior when updating in https://github.com/confluentinc/vscode/issues/520. Going to try and tackle these before our next release.


Di yeats dgug ch

Added DGUG for cgraphcommand and usersetup.

Code quality is good. Many useful data populated in the application for user testing as well.


Selecting a block doesn't work

Which operating system does the issue occur on?

Ubuntu 19.10

If on linux, are you using X11 or Wayland?

Wayland (Sway)
I can't select a block of text using Ctrl+Shift+left mouse button. In other terminals it works like this.

Have you tested the latest master?

@chrisduerr No I haven't, I'm using 0.3.3~1560809133~19.04~fdf1b7c from the deb repo - should this be fixed in latest master, or does it work for you ?

should this be fixed in latest master

Yes, that's correct.

@chrisduerr Do you mind releasing a newer version ? Latest release 0.3.3 is from Jun 16th. Thx !

We're working on it.


make ImageDataGenerator generator repeatable

We want ImageDataGenerator to be repeatable so we can 1) have repeatable research 2) so we can transform a mask and image in parallel (like in the keras docs).
In PR #3751 I made it mostly repeatable but I recently ran more tests and found problems. It's not repeatable when using flow_from_directory, and it's not repeatable if the mask and image have different number of channels.
This PR fixes that by adding np.random.seed(seed) where needed.
I have two unit tests I can add if desired?

Could someone give this a review? I found a issue in keras_retinanet that would be fixed by this, so it's still an issue. It wont take long I just added np.random.seed(seed) where needed.

I think these changes would need a unit test that demonstrates the problem that is fixed to have any chance of being merged.

I don't think resetting the random number generator to the seed for every invocation of the RNG is a good idea. You're effectively reducing it to generate one random number and repeating it a lot of times.
The proper way to solve the problem (at-least for keras-retinanet) I think is to split the generation and usage of random transformations into separate steps so that the random transformation can be used multiple times on different things (like the image and the bounding boxes).

@de-vri-es That's true, my fix is not ideal, and your proposal would be much cleaner. But it would take much longer and it seems like no one is keen to spend much time on this part of keras. Which is fair enough, perhaps it could be split into a separate package to shift the burden of keras maintainers.
@ahundt In the original posts I offered unit tests, but I deleted them since there was no interest. I could look into writing them again, but would you even want this PR if I did, or would it be a waste of my time?

@wassname Yeah probably wouldn't be merged considering it repeats values.
I think a solution like the one @de-vri-es suggested would be necessary or something like SegDataGenerator as I mentioned in the jaccard distance PR.
For other readers' reference: SegDataGenerator from Keras-FCN transforms both an image and a mask. A usage example is available in the Keras-FCN's train.py file.

I agree this was just a quick fix, sounds like we all want to leave it until there is a better solution.
Yeah SegDataGenerator is pretty nice for segmentation, I've used it and found it easy to edit too. Might be worth adapting to keras_retinanet too, thanks for the suggestion.


Added additional MC header information

This is basically a continuation of #895 and #655.
MCRunHeader information from the simtel files gets stored in the MCHeaderContainer.
The Container should now contain every information of the MCRunHeader stored in the simtel files.
Item description is mainly taken from the hessio documentation at:
https://www.mpi-hd.mpg.de/hfm/~bernlohr/sim_telarray/Documentation/hessio_refman.pdf (page 80-81)
Range arrays are stored as max and min values (e.g. shower azimuth range).
Unfortunately I do not really know how corsika works and the hessio documentation does not mention
anything about the meaning of the corsika_* parameters. Those Descriptions should probably be updated
with something more meaningful.

I think this is ready right? @MaxNoe do you still have a problem?


A100推理为啥很慢呢？是我Inference姿势不对吗？

单卡A100，一条数据inference time : 9.407606601715088

How many output tokens are there currently for inference, and could you provide a speed metric in the style of how many tokens per second, as well as the GPU utilization situation?


Incorrect Reg Key to enable via GPO

The Reg Key is
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Policy Manager\EnableNetworkProtection
not
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\Network Protection

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

ID: 673970ca-2f79-a288-978c-ceb4845c5062
Version Independent ID: 2a58449f-b0d4-bf17-1209-d7b8ec0481b6
Content: Turn on network protection
Content Source: microsoft-365/security/defender-endpoint/enable-network-protection.md
Product: m365-security
Technology: mde
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@chbreakthrough Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4702
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @chbreakthrough Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


/usr/bin/_blackbox_common.sh: line 265: cd: /dev/null: Not a directory

When trying to deploy via TeamCity with blackbox_postdeply, above error is emitted.
Setting up bash -x to give debug info, REPOBASE is being set as /dev/null.  There isn't a .git subdirectory in the project directory.

The issue seems to be:
If blackbox fails outside of a Git/Svn/Hg repo.  As a user, I want to be able to decrypt files when they've been copied out of a repo.

This patch fixes it: 4a5787c
Waiting for verification.

I can confirm that this change solves my issue.  Thanks Tom!


Clumit light mode screen development (2) - Etc.

Replace color codes used on screens other than the listed below with CSS variables: Event, Detection, Triage, AI Model
ex) Sign In, Home, Dashboard, Report, Admin, K-MITRE, etc.

Relates to #181


Unable to login or reset password

I migrated the database with seed and I found there are 2 users I trying to login and see the system. but I not know password .Then  I try to fergot password link it was not working even I set the smtp settings. So how to run and use the system.
Please guide.

Solved
its nothing but the placeholder values given both username and password.


Fix zoomTo/zoomBy with ref point and immediately to true. Fix #800

I broke the tests. I am not sure what is going on yet.
Anyway the tests were checking for very odd zoom values (-1 and 0) which we should reject in the first place I think.

Ok, test fixed.
It turns out that setting defaultZoomLevel after opening the viewer does not work.
The tests were passing before because there was a special case for the first zoom level tested (-1).

Awesome, thank you for taking this one on! Good to have the tests cleaned up like that as well.
Just one super minor style point, if you want to fix that. Otherwise I think this is ready to land!

@avandecreme Thanks again for fixing this!

Ha, you didn't give me enough time for the little fix :)

Sorry... just got caught up in a bunch of OSD stuff I was doing :)


Security issue: missing return value check when invoking ocall_mbedtls_net_accept

I found a implementation issue in ocall_mbedtls_net_accept that will casue a vulnerability.
This is the definition in EDL.
int ocall_mbedtls_net_accept( [in] mbedtls_net_context *bind_ctx, [out] mbedtls_net_context *client_ctx, [out, size=buf_size] void *client_ip, size_t buf_size, [out] size_t *ip_len );

As we known, all the value OCALL returns is untrusted. mbedtls_net_accept_ocall is a wrapper function of OCALL function ocall_mbedtls_net_accept. mbedtls_net_accept_ocall should have checked  whether the value returned from ocall_mbedtls_net_accept is valid, E.g., the ip_len should always less than or equal to buf_size.
Missing the check means the callee takes the responsibility to check returned value. Unfortunately, in example/enclave/s_server.c, the sample code doesn't check the value returned from mbedtls_net_accept_ocall, which will cause a stack memory leak.
int ssl_server()
{
    ...
    unsigned char client_ip[16] = { 0 };
    ...
    if( ( ret = mbedtls_net_accept_ocall( &listen_fd, &client_fd,
                    client_ip, sizeof( client_ip ), &cliip_len ) ) != 0 )
    ...
#if defined(MBEDTLS_SSL_DTLS_HELLO_VERIFY)
    if( opt.transport == MBEDTLS_SSL_TRANSPORT_DATAGRAM )
    {
        if( ( ret = mbedtls_ssl_set_client_transport_id( &ssl,
                        client_ip, cliip_len ) ) != 0 )
    ...
}

The code above invokes mbedtls_net_accept_ocall to get client_ip and cliip_len at first, then it invokes mbedtls_ssl_set_client_transport_id to store client_ip with length of cliip_len. The cliip_len is returned from OCALL and there is no check on it. If the attacker returns cliip_len that is larger than sizeof(client_ip), mbedtls_ssl_set_client_transport_id will store larger size of contents than client_ip should be. That's a stack memory leak.
To fix this issue, we can implement a wrapper function in enclave. It invokes mbedtls_net_accept_ocall and check returned ip_len.

Thanks. Good catch. Would you like to fix it and submit a PR?


Typescript definitions for ,

Looks like these type definitions are missing.

Tried the PR. Looks like onDismiss, stackAnimation, stackPresentation props are not available on Screen.


SteamVR not playing games properly

I have an issue where some games (HelloVR.exe and Keep talking and nobody explodes) will work (but only very "jumpy" (View jumps around in the scene a lot), but other apps like InCellVR or the SteamDesktopTheater will leave me with an image of fading blue on my HDK 1.4's screen. Does smobody have a similar issue? Any fixes?

I am going to close this issue as it is discussed in issue #48


First cut of Info Msg changes

First cut of Info message restructing. I made the changes that I think are suitable. Looking to get a good review / Discussion on these changes before we merge up. I have not yet compiled this. Will do once we agree on the final cut of the API.
Please note - we will transition into this API gradually. No Existing fields will be removed / changed immediately. They are only marked as DEPRECATED. Device will send both OLD and NEW fields.
We need to figure out how we can make cloud handle both versions of Eve.
Some Choices:

Should we use a Version field?

Cloud knows how to handle different versions of Eve
Remove Support for old version after a few months.
Once Cloud is upgraded to handle new version, Eve can remove support for old version
This is the right method to handle API changes

Should we first upgrade all field devices to new Eve and then upgrade cloud?
- Cloud work will start after all such devices are upgraded
- Any remaining Older devices will not display the status information correctly in this case
- Once Cloud transition is done, Eve will remove support for older devices.

Please note - we will transition into this API gradually. No Existing fields will be removed / changed immediately. They are only marked as DEPRECATED. Device will send both OLD and NEW fields. We need to figure out how we can make cloud handle both versions of Eve.

Please add @bharani-zededa to this conversation, he had the following comment on one of my PRs:

There will always be cases where zedcloud and device will be running different versions. For instance, zedcloud is updated to latest where as there may be a bunch of devices still running older version. The opposite is also possible although I would expect that only in alpha. More specifically, the change below is changing the type of the field for protobuf tag value 1. We should never be re-using tags. Please deprecate the old fields and add new tag values for new fields.

@kalyan-nidumolu, I think we can never remove the deprecated fields (and thereby re-using it's number) as there can always be a possibility of some edge node running an old version.  It is not only zedCloud, going forward we need to consider ADAM too. What I am trying to say is that, it is tough to guarantee that all edge nodes have moved ahead to a particular version - we simply don't have a way to find that out, yet.

Please note - we will transition into this API gradually. No Existing fields will be removed / changed immediately. They are only marked as DEPRECATED. Device will send both OLD and NEW fields. We need to figure out how we can make cloud handle both versions of Eve.

Please add @bharani-zededa to this conversation, he had the following comment on one of my PRs:

There will always be cases where zedcloud and device will be running different versions. For instance, zedcloud is updated to latest where as there may be a bunch of devices still running older version. The opposite is also possible although I would expect that only in alpha. More specifically, the change below is changing the type of the field for protobuf tag value 1. We should never be re-using tags. Please deprecate the old fields and add new tag values for new fields.

@kalyan-nidumolu, I think we can never remove the deprecated fields (and thereby re-using it's number) as there can always be a possibility of some edge node running an old version. It is not only zedCloud, going forward we need to consider ADAM too. What I am trying to say is that, it is tough to guarantee that all edge nodes have moved ahead to a particular version - we simply don't have a way to find that out, yet.

@cshari-zededa ---- We will always have a window of supported releases. After that window is done, we can remove it. It is not realistic to guarantee that all the old releases will keep working with a controller - whether Adam or ZedCloud or any other. Software needs to keep evolving - even open source projects and that means dropping support for older releases. Currently, our window is 3 months. We will adjust it as we go along as we see fit. But once that window is over, we can remove the deprecated fields.
When I say we can remove the deprecated fields - we can keep the number of the field reserved with a comment - but remove the field itself.. This means, old devices cannot corrupt the controller - but we do not need the controller to support the old devices.

When I say we can remove the deprecated fields - we can keep the number of the field reserved with a comment - but remove the field itself.. This means, old devices cannot corrupt the controller - but we do not need the controller to support the old devices.

@kalyan-nidumolu  Thanks for this clarification, it is clear to me now. As long as the number is reserved, I don't see any issue in dropping the support for deprecated fields.

Hey @kalyan-nidumolu @nordmark -- this has been outstanding for a long time. What's the status of this work?

Hey @kalyan-nidumolu @nordmark -- I'm about to close this PR tomorrow unless I hear otherwise


can i ask what version is your numpy？

When I run the code from this repo, I always get numpy related issues and other conflicts. So can i ask what version is you numpy? Or give me a requirements.txt.Thank you.

Hi ZevineXu,
Thank you for pointing out version issues in this repo!
I updated requirements.txt files at the recent commit.

snu-mllab/DiscreteBlockBayesAttack/protein_attack/requirements.txt: ad7c85e2e2b7ecb69b7996d250eed387886703b9
badeok0716/TextAttack/requirements.txt: b572c80c4c45a6cc924e4145d1a7d04a0d9adec7

Please follow the instructions in the README.md files of the recent commits.


Default tokens don't work anymore [BUG]

These tokens provided in repo's readme doesn't work anymore:
"CLIENT LAUNCHER TOKEN" => "MzQ0NmNkNzI2OTRjNGE0NDg1ZDgxYjc3YWRiYjIxNDE6OTIwOWQ0YTVlMjVhNDU3ZmI5YjA3NDg5ZDMxM2I0MWE="
"FORTNITE CLIENT TOKEN" => "ZWM2ODRiOGM2ODdmNDc5ZmFkZWEzY2IyYWQ4M2Y1YzY6ZTFmMzFjMjExZjI4NDEzMTg2MjYyZDM3YTEzZmM4NGQ="
Error message: "Please enter good credentials (Login/Username/Launcher Token)".
The account's password and username remained the same.
Full error message:
Error: {"message":"Please enter good credentials (Login/Username/Launcher Token)","err":{"message":"Request failed with status code 400","name":"Error","stack":"Error: Request failed with status code 400\n    at createError (E:\novos-graphql-server\node_modules\axios\lib\core\createError.js:16:15)\n    at settle (E:\novos-graphql-server\node_modules\axios\lib\core\settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (E:\novos-graphql-server\node_modules\axios\lib\adapters\http.js:237:11)\n    at IncomingMessage.emit (events.js:203:15)\n    at IncomingMessage.EventEmitter.emit (domain.js:448:20)\n    at endReadableNT (_stream_readable.js:1145:12)\n    at process._tickCallback (internal/process/next_tick.js:63:19)","config":{"url":"https://account-public-service-prod03.ol.epicgames.com/account/api/oauth/token","method":"post","data":"grant_type=password&username=myaccount&password=mypassword&includePerms=true","headers":{"Accept":"application/json, text/plain, /","Content-Type":"application/x-www-form-urlencoded","Authorization":"basic MzQ0NmNkNzI2OTRjNGE0NDg1ZDgxYjc3YWRiYjIxNDE6OTIwOWQ0YTVlMjVhNDU3ZmI5YjA3NDg5ZDMxM2I0MWE=","User-Agent":"axios/0.19.0","Content-Length":75},"transformRequest":[null],"transformResponse":[null],"timeout":0,"responseType":"json","xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1}}}

algun token que sirva para mi codigo php?  https://i.imgur.com/CAdaoO8.png
Do you think this php code works if I get the token?

The fortnite API endpoints have changed. Check my fork of this repo for the working copy


Implement new RSS Builder

The currently RSS library used by Librarian is quite old. We need to update to a more modern option that doesn't bring too many dependencies in.
In addition to updating to a newer RSS Builder library, implement an RSS Service to provide rss feeds for both the dynamic and static versions (web command and build command respectively). Currently the code is duplicated in these two commands.

I'm working on it!

Is there any way to identify if the version used is the dynamic or static?

Is there anything else needed for this @williamtrevisan?

Is there anything else needed for this @williamtrevisan?

I don't think so. It's done.
Should I close this?

I don't think so, it's done. Should I close this?

If that's already done, yeah, you can close it!


Seahub always says it's starting on port 8000 even though  SEAHUB_PORT is set

As discussed in #13 starting Seahub with a given port only affect display.
What matters is the binding in gunicorn.conf.py which is handled fine.
Nevertheless it's still a bug and could be confusing, but it's really far from my priorities so it will stay as wontfix atm.

Fixed in eaeaf0216fbfe0c31c032c39c419f2d280ec3d00


How to update state into particle options in real-time while preventing re-rendering?

Hello, I am developing with React and using @tsparticles/react 3.0.0. I am trying to pass a state that updates in real-time as a prop to the Particle component so that it can dynamically change the options, such as the number value or animation speed.
The issue I'm facing is that when I pass the state as a prop, the Particle component re-renders whenever the state updates, which results in the particle effect being completely restarted. I would like the particle effect to smoothly update its options without restarting the animation each time the state changes.
Are there any recommended approaches or best practices to achieve this behavior?
Any help would be greatly appreciated!

Hello, I am developing with React and using @tsparticles/react 3.0.0. I am trying to pass a state that updates in real-time as a prop to the Particle component so that it can dynamically change the options, such as the number value or animation speed.
The issue I'm facing is that when I pass the state as a prop, the Particle component re-renders whenever the state updates, which results in the particle effect being completely restarted. I would like the particle effect to smoothly update its options without restarting the animation each time the state changes.
Are there any recommended approaches or best practices to achieve this behavior?
Any help would be greatly appreciated!

If you change the options, the particles will restart because many values are cached to improve performance. If you need custom behaviors, like changing particles in real-time consider an emitter with particles that have life options or a custom plugin.

Hello, I am developing with React and using @tsparticles/react 3.0.0. I am trying to pass a state that updates in real-time as a prop to the Particle component so that it can dynamically change the options, such as the number value or animation speed.
The issue I'm facing is that when I pass the state as a prop, the Particle component re-renders whenever the state updates, which results in the particle effect being completely restarted. I would like the particle effect to smoothly update its options without restarting the animation each time the state changes.
Are there any recommended approaches or best practices to achieve this behavior?
Any help would be greatly appreciated!

If you change the options, the particles will restart because many values are cached to improve performance. If you need custom behaviors, like changing particles in real-time consider an emitter with particles that have life options or a custom plugin.

Thanks for the explanation.
I understood that constantly passing external state to update the particle option would not prevent restarts.
Using an emitter would allow me to adjust the animation with external state?
Is there any example code or guide on how to implement an emitter or custom plugin to modify particle behaviour in real-time without restarting?
Thanks in advance for your help.

You can check a sample of an emitter here: https://codepen.io/matteobruni/pen/WNVdyVG
You can configure how fast and how many particles needs to be added, but it's done on a regular interval of time, you need to remove other particles or set a limit to prevent too many particles on screen.
About custom plugins you can check existing ones here: https://github.com/tsparticles/tsparticles/tree/main/plugins
But this arguments are now off topic here, since it's more inherent to main library than React.
Alternatively, you can use the particlesLoaded property, the parameter is the instance that is responsible for the whole animation, you can access its .particles property where you can find .addParticle (https://github.com/tsparticles/tsparticles/blob/71d3278f86cac209dc5e851aa6eefb70b2665b40/engine/src/Core/Particles.ts#L104) and .remove (https://github.com/tsparticles/tsparticles/blob/71d3278f86cac209dc5e851aa6eefb70b2665b40/engine/src/Core/Particles.ts#L270) which let you programmatically handle particles. For accessing the particles array use .filter(lambda condition), .find(lambda condition) or .get(index)

I'm sorry for repeatedly asking for help, and appreciate your support.
I've tried to implement the addParticle method within a useEffect so that particles are added each time the specefic button is clicked (i.e., when the state changes). However, Particles animation still rerender when the state updates.
Is it impossible to modify particles in real-time based on state changes without causing a rerender of the particle animation? I was wondering if there are any code examples that reflect changes in state to particles in real-time.

Why the <Particles /> component is inside the <button>? I'd say to split the component in two, one for the particles and one for the button, handling the particlesLoaded with a function coming from the parent, or something like that.

Why the <Particles /> component is inside the <button>? I'd say to split the component in two, one for the particles and one for the button, handling the particlesLoaded with a function coming from the parent, or something like that.

My mistake, as the code was for a simple test implementation.
Due to the deadline of my project, I've decided to implement the functionality into another library for now. Thanks for your continued help.


Configure svelte as an optional peer dependency

Description
Does it make sense to mark svelte as an optional peer dependency as it is for eslint-plugin-svelte?
I have an eslint config that conditionally depends on svelte and its plugins, so in some cases it's not installed. However, I can't seem to suppress pnpm's missing peer deps warning with any configuration on my end.
I assume that pnpm's output indicates that the warning is propagating upwards from svelte-eslint-parser:
 WARN  Issues with peer dependencies found
.
└─┬ @theurgi/eslint-config 1.3.0
  ├── ✕ missing peer svelte@"*"
  └─┬ eslint-plugin-svelte 2.18.0
    ├── ✕ missing peer<EMAIL_ADDRESS>    └─┬ svelte-eslint-parser 0.23.0
      └── ✕ missing peer<EMAIL_ADDRESS>Peer dependencies that should be installed:
<EMAIL_ADDRESS><4.0.0"

In my package: @theurgi/eslint-config, I have svelte set as optional:
"peerDependenciesMeta": {
  "svelte": {
    "optional": true
 },

But this does not silence the warning when using pnpm. Any package that depends on my shareable config inherits this warning.
Interestingly, I get no warning when installing with npm. I haven't tried yarn.
Thank you 🙏

Does it make sense to mark svelte as an optional peer dependency as it is for eslint-plugin-svelte?

I think it makes sense.
I think you should ignore the warning or install svelte.

Thanks for your reply.
What I mean is, does it make sense to add peerDependenciesMeta.svelte.optional: true to svelte-eslint-parser's package.json? I'm happy to submit the pull request if you don't consider it an undesirable configuration.
Because, unless I'm mistaken, that is where the warning stems from. There seems to be nothing more I can do within my package to suppress this warning.
Specifically, it appears that the warning propagates from svelte-eslint-parser → eslint-plugin-svelte → @theurgi/eslint-config.
Though both eslint-plugin-svelte and @theurgi/eslint-config have peerDependenciesMeta.svelte.optional: true set, this does not suppress the warning.
The other option is to simply remove svelte from peerDependencies within both svelte-eslint-parser and eslint-plugin-svelte; for example, eslint-plugin-vue does not have vue as a peer dependency and thus it produces no warning. The same is true of eslint-plugin-react.
But I don't know if removing the peer dependency on svelte is feasible for this project.
If there's no other recourse, I'll have no choice but to ignore the warning but it was worth a shot to try to resolve this issue at its root (if indeed this is the root of the issue).

The parser depends on the svelte package. The parser will not work if svelte is not present.
If you can create a similar parser that doesn't depend on the svelte package, please create and publish it.

The parser will not work if svelte is not present.

Of course. I did not suggest otherwise. I expect the parser not to work when svelte is not present and that is precisely the case I'm referring to.
To clarify my use case:
@theurgi/eslint-config depends on eslint plugins for multiple frameworks and conditionally extends them based on file extension and whether the framework package ( in this case svelte) is a dependency of the project. This allows for a single shareable config that works across all projects, capable of linting any combination of tooling: Svelte with TypeScript; Svelte without TypeScript; React with and without TypeScript; An Astro monorepo with JSX, Vue, Svelte, and Prettier; and so on...
This approach is in contrast to the popular eslint-config-alloy which asks the user to...

Please choose the following configuration based on the technology stack used by your project:

Built-in
React
Vue
TypeScript
TypeScript React
TypeScript Vue

... and then requires them to install and configure, for example:
npm install --save-dev @babel/core @babel/eslint-parser @typescript-eslint/eslint-plugin @typescript-eslint/parser @vue/eslint-config-typescript eslint eslint-config-alloy eslint-plugin-vue vue-eslint-parser

In addition to linting multiple frameworks,@theurgi/eslint-config also resolves this Support having plugins as dependencies in shareable config issue without having to wait for the new ESLint config succeed its experimental phase.
Don't get me wrong, I'm not here to advocate for my personal eslint configuration preference. I'm just trying to describe a scenario where one may want to install, but not necessarily use, a tool (svelte-eslint-parser) which has a peer dependency (svelte) yet does not want to satisfy that peer dependency and would like the ability to suppress its irrelevant warning which otherwise propagates to all dependents.

The parser depends on the svelte package.

Strictly speaking, it does not. It has a peer dependency of the svelte package which is a deferral to the user to satisfy the dependency.
But of course, it is assumed to be the case that if a user is installing svelte-eslint-parser they are also installing svelte.
Nevertheless, listing svelte as a peer dependency is relevant because it specifies a version range.
And that is why my request was to first add peerDependenciesMeta.svelte.optional: true. With npm and this setting, I can suppress the warning myself by adding it higher in the tree. But with pnpm, apparently I can not; it seems to propagate the warning regardless and instead offers as a solution pnpm.peerDependencyRules.ignoreMissing. But this is not a publishable setting, it has to be added in the package manifest of every dependent project. Suboptimal.

If you can create a similar parser that doesn't depend on the svelte package, please create and publish it.

Is this a necessary statement?
I admire and appreciate your work. I realize you may consider this a trivial matter. If my argument to make this non-functional change has not convinced you and you disagree, that is fine, just say so. I'm not sure what GitHub issues are for if not to deliberate on collaborative source code and to collectively reap the benefit of doing so.

I'm not sure what you mean by this issue. (It may be because I don't understand English very well 😓)
This package depends on the svelte package. If it's a problem to be warned, I think you should install the svelte package. Are there any other solutions?

Forgive me if I was not clear.
There is a difference in the way that npm and pnpm emit warnings in regards to missing peer dependencies.
A demonstration
npm

As you can see, no warnings are emitted.
pnpm

And here we have warnings despite the fact that all packages installed are identical to those installed with npm.
Why I consider this a problem
The context
As I described in my previous comment, @theurgi/eslint-config extends, and strictly depends on, eslint plugins for React, Vue, Svelte, TypeScript, Astro, Prettier, and more.
The benefit of doing this is that with a single shareable eslint config (only one package to maintain, only one package to install), I can lint any combination of JavaScript tooling.
I discovered this architecture here: privatenumber/eslint-config and of all the ways I have seen to create a shareable eslint config, this, in my opinion, is the best.
The problem
I intend to use @theurgi/eslint-config in various different JavaScript projects. But, when the project I am working on is, for example, a Next.js/React project, I would prefer not to have warnings emitted about a missing svelte peer dependency every time I, or someone else, runs pnpm install ....
And I certainly don't want to install svelte and have it listed as a dependency in the package.json of a Next.js/React project just for the sake of suppressing this warning—that would be very misleading.
How I've attempted to address this issue
Initially, I opened this issue with pnpm.
Despite what the maintainer of pnpm proposed as a solution, I was not able to suppress warnings emitted by dependencies of @theurgi/eslint-config by including any combination of the following in its package.json.
"peerDependencies": {
  "eslint": "*",
  "svelte": "*"
},
"peerDependenciesMeta": {
  "svelte": {
    "optional": true
}

My next logical assumption was that with pnpm, missing dependency warnings must be suppressed at their root: i.e. svelte-eslint-parser.
Considering that the maintainer of pnpm dismissed my issue, my next option was to see if you, the maintainer of this project, would be willing to include the above code in your package.json. I did not know at the time whether this would work; I was partially asking if you knew, and partially asking if you would consider testing it.
Where we are now
After additional tests, I am now convinced that even if you did include peerDependenciesMeta.svelte.optional: true in svelte-eslint-parser's package.json, it would not suppress the warning. It doesn't seem to matter where this property is set in the dependency tree.
Therefore the only option left to suppress such warnings is to include the following in the package.json of every project that depends on @theurgi/eslint-config:
"pnpm": {
  "peerDependencyRules": {
    "ignoreMissing": ["svelte", "..."]
  }
}

This is not something I can include in @theurgi/eslint-config's package.json itself—pnpm publish removes all pnpm properties from published configs. Furthermore, it only reads this setting in a project's root package.json.
This was the least desirable option to fix this issue in my opinion and I wanted to exhaust all other options before resorting to it.
That is all.
So, thank you again for your open source contributions. Thank you for your time and consideration. Hopefully our exchange was not entirely futile for you. And judging by the documentation you have written, your English is very good.
🙏

Thank you for explaining it all over again!
I must apologize. I had a very big wrong understanding.
I totally thought that svelte-eslint-parser already included peerDependenciesMeta. But that was not the case. We need to add peerDependenciesMeta.
  "peerDependenciesMeta": {
    "svelte": {
      "optional": true
    }
  },


Instructions need to be updated for XCode 11 without Application Loader

Xcode 11 removed Application Loader so these instructions no longer apply. We need instructions on how to upload a Xamarin app from a windows machine with the absence of Application Loader.
This is a blocking issue for our team.

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

ID: bb327a64-010d-dba8-5ebc-546892d739af
Version Independent ID: 48a24297-7b8f-b1b2-7b25-44f40fe33eac
Content: Publishing Xamarin.iOS apps to the App Store - Xamarin
Content Source: docs/ios/deploy-test/app-distribution/app-store-distribution/publishing-to-the-app-store.md
Product: xamarin
Technology: xamarin-ios
GitHub Login: @conceptdev
Microsoft Alias: crdun

Thanks for the feedback @wadebaird.
As you mentioned, Application Loader is no longer included in Xcode 11 (mentioned in the release notes). One option that page offers is using xcodebuild or xcrun altool from the Terminal on macOS.
There are some forum mentions, and the usage is available from the command line. I have not yet used this myself, I just want to offer some alternatives while we get the documentation updated.
$ xcrun altool
Copyright (c) 2009-2019, Apple Inc. Version 4.00.1181

Usage: altool --validate-app -f <file> -t <platform> -u <username> {[-p <password>] | --apiKey <api_key> --apiIssuer <issuer_id>}
       altool --upload-app -f <file> -t <platform> -u <username> {[-p <password>] | --apiKey <api_key> --apiIssuer <issuer_id>}
       altool --notarize-app -f <file> --primary-bundle-id <bundle_id> -u <username> {[-p <password>] | --apiKey <api_key> --apiIssuer <issuer_id>} [--asc-provider <provider_shortname>]
       altool --notarization-info <uuid> -u <username> {[-p <password>] | --apiKey <api_key> --apiIssuer <issuer_id>}
       altool --notarization-history <page> -u <username> {[-p <password>] | --apiKey <api_key> --apiIssuer <issuer_id>} [--asc-provider <provider_shortname>]
       altool --list-apps -u <username> {[-p <password>] | --apiKey <api_key> --apiIssuer <issuer_id>}
       altool --store-password-in-keychain-item <name_for_keychain_item> -u <username> -p <password>

@wadebaird the documentation has now been updated:
https://docs.microsoft.com/xamarin/ios/deploy-test/app-distribution/app-store-distribution/publishing-to-the-app-store?tabs=macos#build-and-submit-your-app
It describes a new feature in the latest version of Visual Studio for Mac that replaces Application Loader. The Windows information has not yet been updated, but you should be able to complete your submission in macOS.

Its probably premature to close this as it really isn't fixed nor addressed in any realistic manner.

We added a publishing workflow to Visual Studio 2019 that replaces the need for Application Loader.
The docs have been updated to describe the new workflow: https://docs.microsoft.com/xamarin/ios/deploy-test/app-distribution/app-store-distribution/publishing-to-the-app-store#build-and-submit-your-app

I appreciate the updates, however after a successful Archive of an iOS app, the Distribute button is not present. Any ideas?


Tcs experimental sd

Texts modified. Modified color of the gripper svg and background dots.

Please move icons changes to separate PR. Because this branch will be not merged since there will be conflicts with settings-redesign branch.


Tooltip not rendered when wrapping Pulsar

Right now this results in a console error and no Tooltip being rendered on hover:
<Tooltip content="Example tooltip content">
  <Pulsar position={Position.TOP_LEFT} />
</Tooltip>

Warning: Function components cannot be given refs. Attempts to access this ref will fail. Did you mean to use React.forwardRef()?

Check the render method of `Stack`.
    at eval (https://pvtkqq.csb.app/node_modules/evergreen-ui/esm/pulsar/src/Pulsar.js:53:30)
    at Stack (https://pvtkqq.csb.app/node_modules/evergreen-ui/esm/stack/src/Stack.js:13:23)
    at Positioner (https://pvtkqq.csb.app/node_modules/evergreen-ui/esm/positioner/src/Positioner.js:50:22)
    at Tooltip (https://pvtkqq.csb.app/node_modules/evergreen-ui/esm/tooltip/src/Tooltip.js:60:33)
    at div
    at eval (https://pvtkqq.csb.app/node_modules/ui-box/dist/src/box.js:21:11)
    at Pane (https://pvtkqq.csb.app/node_modules/evergreen-ui/esm/layers/src/Pane.js:57:31)
    at div
    at eval (https://pvtkqq.csb.app/node_modules/ui-box/dist/src/box.js:21:11)
    at Pane (https://pvtkqq.csb.app/node_modules/evergreen-ui/esm/layers/src/Pane.js:57:31)
    at App

I think the Pulsar component needs to forward its ref and additional box props that are cloned onto it by the Tooltip component (i.e. onMouseEnter, onMouseLeave)
Originally posted by @brandongregoryscott in https://github.com/segmentio/evergreen/pull/1558#discussion_r1039007519

Resolved with #1565


Cross network favorites

Can we make favorites viewable across networks? Currently seeing no favorites if on a different network. Means we're asking users to manage multiple favorites lists.
Browser metadata
Path:      /home?dao=eth:0xD26c85D435F02DaB8B220cd4D2d398f6f646e235
Browser:   Firefox 125.0 on Mac OS 10.15
Viewport:  1402 x 912 @2x
Language:  en-US
Cookies:   Enabled

Open in BrowserStack

Open Deploy Preview · Mark as Resolved
Originally posted by @nicolaus-sherrill in https://github.com/decentdao/fractal-interface/issues/1578#issuecomment-2101014045

I think this is outside of the scope of the reskin, but a good idea regardless. Will require more design and engineering brains to implement though.

yep not to bad actually. You've set up the ground work with the new query. and wouldn't be much to sort and reorg the list into a object by network. then just add a label between each section? We have the patterns for 'labels' with the Wallet Menu so could be a easy win.

Word!
To @Da-Colon 's point, two quick solutions:

Add network icon to Favorite list item
Segment list by network

Even though we're going to be removing the DAO index from the home page, this same functionality is intended there too. User should be able to view DAOs across chains & possibly filter down (let's us display more DAOs in the index at once = better look for BD).

This is completed


[doc] Fix store_last_results description in redshift

store_last_results in redshift isn't BOOLEAN.
The valid value is first. all and false.
I copied this fix from pg operator.
Should I add false?

@muga Thank you for the review. Please take a look when you have time.

Thank you! Merged.


Fixed #32620 -- Allowed subclasses of Big/SmallAutoField for DEFAULT_AUTO_FIELD.

ticket-32620

Added test and changed release note 👍

@adamchainz Thanks :+1:


StateProvider is missing AutoDisposeFamily

Describe the bug
StateProvider.family.autoDispose does not exist
Version: 0.6.0-dev+2

Intersting. There is .autoDispose.family

Ohhhhh, i was always using family.autoDispose on other providers, haha.

I'll add it anyway for consistency


packaged Udev Rules for Steam-Devices Gaming Controllers in a NixPkg

Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

steam already contains these.
Read https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md for your future contributions
steam-devices/default.nix isn't being called anywhere so it wouldn't be available

a hardware.steam-devices.enable module to automatically call it is next on my list of things to do btw :)

This is still a draft

a hardware.steam-devices.enable module to automatically call it is next on my list of things to do btw :)

There's already a option for the steam rules so make it use  this slimmer package
The package file should be in the same dir as steam

yeah, I'm sorry @Artturin, this is my first PR here on GitHub and i expected a pop-up explaining me, what i was about to do. After i converted it away from a draft, i didn't find the button to re-draft it, so i assumed that only repo-owners can mark something as a draft. found it now and fixed it ✌🏼
god, Githubs Docs are actually good. short and precise.

you mean hardware.steam-hardware.enable?
yeah, i realized by now that that was and is what i was trying to do from the beginning.
but in my opinion it has 2 flaws:

like you said, it seems to be a larger package than mine
it's labelled incorrectly:
the name is steam-hardware instead of the correct and widely used steam-devices and, more importantly:
the description suggests it only works for first-party hardware such as the HTC Vive and the Steam Controller, when the Steam-Devices Repo actually also contains multiple other devices such as the Nintendo switch pro Controller

wouldn't it be smarter to make a new, correctly labeled module and depreciate the old one?
or should i just change the description of it for the sake of legacy compatibility?
i would suggest to make a new one, as the same package in other distros / repos is also called steam-devices (i.e. Fedora Linux) and that's how it gets recommended and referred to in the Linux Gaming community

should i make it pkgs.steam-devices or pkgs.steamPkgs.steam-devices?


Styles are not working as expected with bootstrap

I was toying around with alpinejs-component and some simple bootstrap styles and I'm running into the issues, that inside alpinejs components, the styles and their overwrites are not working as expected if styles="global" is used.
Check this simple Codepen that demos the problem:
https://codepen.io/theomega/pen/JjVXjxG

The code tries to wrap a simple bootstrap button with the following classes inside a component:
<button type="button" class="btn btn-primary">Click Me</button>

while using styles="global" to get the Bootstrap styles copied over.
Notice, that in this case the background color of the button is lost somehow. Funnily, everything else still works, including the mouse over hover (with the correct color).
One workaround that I found is not using any styles on the x-component but rather copy the bootstrap css stylesheet link a second time and into the template of the component. Not idea, but at least works. I'm also opening this issue to document this.
Not sure where the issue lies here...

Yep, I noticed this as well. I checked both Safari and Chrome (both on Mac OSX) and the behaviour is consistent.

Hmm, it's odd! I'm trying to think of stuff to try but I don't want the solution to be a workaround for Bootstrap specifically.

Done some more digging and cannot find a solution for this. Will add the "help wanted" label and hope it gets picked up by someone way smarter than me! 🤞

I'm trying to use styles="global" with Tailwind CDN and it's throwing an error in component.min.js saying
Uncaught DOMException: An invalid or illegal string was specified
This is what it points to in the debugger. Not sure how helpful it is.
(()=>{function p(e,n){let l=(n.includes("global")?[...document.styleSheets]:[...document.styleSheets].filter(({title:t})=>n.includes(t))).flatMap(({cssRules:t})=>[...t]),o=new CSSStyleSheet;for(let t of l)t instanceof CSSStyleRule&&t.selectorText===":root"||o.insertRule(t.cssText);e.adoptedStyleSheets=[o]}async function u(e,n,s){function i(o){let t=document.getElementById(o),a=new DOMParser().parseFromString(t.innerHTML,"text/html").body.firstChild;return Promise.resolve(a)}let l=await i(n);s.appendChild(l),e.initTree(s)}async function h(e,n,s){let l=await(await fetch(n)).text(),o=new DOMParser().parseFromString(l,"text/html").body.firstChild;s.appendChild(o),e.initTree(s)}function d(e){class n extends HTMLElement{connectedCallback(){if(this._hasInit)return;let i=this.attachShadow({mode:"open"}),l=this.hasAttribute(":template"),o=this.hasAttribute(":url");(l||o)&&e.initTree(this);let{template:t={value:""},url:a={value:""},styles:f={value:""}}=this.attributes,c=t.value,m=a.value,r=f.value.split(",");c.length&&u(e,c,i),m.length&&h(e,m,i),r.length&&p(i,r),this._hasInit=!0}}window.customElements.get("x-component")||(customElements.define("x-component",n),new n)}document.addEventListener("alpine:init",()=>window.Alpine.plugin(d));})();

The error goes away when I switch it to a capital G styles="Global", but neither option allows the Tailwind to actually style the component.

It doesn't work with the CDN but it does work when compiled #25 #24


Resolve conflict in code editor is not working: 404 Not Found

if there is a merge conflict, e.g. in Edit in Editor, then resolving it does not work with a 404 Not found error. No further errors are mentioned at the moment, the error also does not occur in the server logs.
https://artemis.ase.in.tum.de/api/test-repository/1165/reset

It seems that this only occurs for test repositories, because those do not have a participation id


Standalone version

Have you ever thought or had any plans of producing a stand-alone version of this?  I'm not sure how tightly coupled to Meteor this is, but it strikes me as a very good and easy to use ORM for node and mongo-based apps.
thanks,
Cliff

Yep at some point I though about it. However, now I changed my mind and honestly I think ORMs are only good for very simple CRUD operations and for everything else you can write queries manually. It's especially easy with MongoDB. I'm sold on the idea of code generators, especially for SQL and GraphQL.


Krill key is not created on group if Krill host is not first on l3_routers

Hello,
First of all, thank you for this incredible platform! I'm using it with student, they like it!
I used old version (2019 or 2020) and I just updated it to the last one to have the website, rpki ...
I had an issue with config files that cause me headache.
It seems that the Krill host should be put in first in the l3_routers config file. Otherwise the key is not created into the group folder.
This works:
GENE    DNS krill:miniinterneteth/d_krill       vtysh
LOND    MATRIX	routinator:miniinterneteth/d_routinator	vtysh
ZURI    MATRIX_TARGET host:miniinterneteth/d_host	vtysh

This does not work (for me):
LOND    MATRIX	routinator:miniinterneteth/d_routinator	vtysh
ZURI    MATRIX_TARGET host:miniinterneteth/d_host	vtysh
GENE    DNS krill:miniinterneteth/d_krill       vtysh

I get
./setup/container_setup.sh: line 180: /home/xxxx/groups/g1/krill/kill_token.txt: No such file or directory
and, juste before, during the rpki_config.sh script, it creates only the groups/rpki/root.key
That's quite strange. It didn't get through the code since it's way above my knowledge.
I hope I can help to make this platform even better with my little contribution :)
Have a nice day

Hi. We are glad if the students like it :-) and sorry about the headache! :pray:
I fixed the problem, you can see the fix in this commit.
Thanks for reporting it! (and please let us know if you experience other issues)


Add a Cromwell workflow test for SmartSeq2 to CirclerCI

Purpose

Adding a test to the circle ci tests
Changes

cromwell workflow tests for SmartSeq2 has been added to CirclerCI
Review Instructions

No instructions.

Wow, pullapprove, how rude.


Add test-suite running TestU01

SplitMix32 doesn't pass Crush, but does well.
SplitMix64 passes all tests.
========= Summary results of Crush =========

 Version:          TestU01 1.2.3
 Generator:        SplitMix32
 Number of statistics:  144
 Total CPU time:   01:41:35.26
 The following tests gave p-values outside [0.001, 0.9990]:
 (eps  means a value < 1.0e-300):
 (eps1 means a value < 1.0e-15):

       Test                          p-value
 ----------------------------------------------
 41  MaxOft, t = 5                  1 - 4.7e-10
 42  MaxOft, t = 10                 1 - 6.4e-14
 43  MaxOft, t = 20                 1 - 9.8e-15
 44  MaxOft, t = 30                 1 - 1.1e-15
 75  Fourier3, r = 20                0.9998
 ----------------------------------------------
 All other tests were passed

========= Summary results of Crush =========

 Version:          TestU01 1.2.3
 Generator:        SplitMix32 (Double)
 Number of statistics:  144
 Total CPU time:   02:07:08.55
 The following tests gave p-values outside [0.001, 0.9990]:
 (eps  means a value < 1.0e-300):
 (eps1 means a value < 1.0e-15):

       Test                          p-value
 ----------------------------------------------
 41  MaxOft, t = 5                  1 -  2.2e-8
 42  MaxOft, t = 10                 1 - eps1
 43  MaxOft, t = 20                 1 - 4.6e-10
 44  MaxOft, t = 30                 1 - eps1
 ----------------------------------------------
 All other tests were passed

For random 1.2, we tested splitmix (64-bit version) thoroughly.

Results: relevant output files start with splitmix-
Description of "split sequences": details on "L"/"R"/"LR" sequences used to test the quality of split


PYIC-4189: handled to the new property 'issuers' and changed response IPV_IDENTITY_ISSUED event for fail return code

Proposed changes
What changed
D&A need to have access to metrics around Failure Codes, however, it is important that they are not only able to see how many failure codes have been raised, but they also need to be able to see what CRI’s resulted in those Failure codes.
This story builds on the existing feature to add information about which CRI’s produced failure codes to the event sent to TxMA
Why did it change
To facilitate future analysis around the performance of the CRI’s and more specifically which ones are resulting in certain failure codes
Issue tracking

PYIC-4189

Checklists
Environment variables or secrets

[ ] No environment variables or secrets were added or changed

[ ] Documented in the README
[ ] Added to deployment repository
[ ] Added to local startup repository

Other considerations

[ ] Update README with any new instructions or tasks

Just a comment on maybe not needing one of the test, otherwise I think this is good. I'm going to deploy it to my dev env to check it out.
We'll also need to think about the acceptance tests - this change will break them. Should be a pretty straightforward fix though. It'll need to be ready before this is merged though or we'll block the pipeline.

Have deployed to my dev env, but we need the stub to be able to test this before merging.


Is this library still maintained?

Hi @jrmarino, I'm currently trying to tidy up the bindings linked on the libsodium website. If this library is still maintained, then please let me know; otherwise, the link to this library will likely be removed from the bindings page to help users find up to date and maintained bindings.

It is still maintained.
On Tue, Mar 15, 2022 at 3:32 PM Samuel Lucas @.***>
wrote:

Hi @jrmarino https://github.com/jrmarino, I'm currently trying to tidy
up the bindings linked on the libsodium website. If this library is still
maintained, then please let me know; otherwise, the link to this library
will likely
https://github.com/jedisct1/libsodium-doc/pull/156#issuecomment-1067834246
be removed from the bindings
https://doc.libsodium.org/bindings_for_other_languages page to help
users find up to date and maintained bindings.
—
Reply to this email directly, view it on GitHub
https://github.com/jrmarino/libsodium-ada/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAISZ5VTRIRE73HXUF3XUJLVADXU5ANCNFSM5QZ3PSSQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks for getting back to me. May I ask why there hasn't been a commit since 2016?

Nobody has needed anything more, but the repo is open for pull requests.
On Tue, Mar 22, 2022 at 7:32 AM Samuel Lucas @.***> wrote:

Thanks for getting back to me. May I ask why there hasn't been a commit since 2016?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Ah, so is it in maintenance only mode rather than being actively developed? I need to discuss with Frank what to do about maintenance only repos.

I did not realize such a binding existed. I made and actively trying to
wrap up another set of bindings to libsodium:
https://gitlab.com/ada23/sodiumada.git
srini
On Tue, Mar 22, 2022 at 9:58 AM jrmarino @.***> wrote:

well, the project I personally was using libsodium for is currently
dormant. If that picks up again, and I find the bindings are now
insufficient, then I would actively develop it. I'm available to
evaluate contributed code so from that POV the bindings are not abandoned.
On Tue, Mar 22, 2022 at 8:54 AM Samuel Lucas @.***>
wrote:

Ah, so is it in maintenance only mode rather than being actively
developed? I need to discuss with Frank what to do about maintenance only
repos.
—
Reply to this email directly, view it on GitHub
<
https://github.com/jrmarino/libsodium-ada/issues/1#issuecomment-1075210608
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAISZ5TNTM4OKD32SQCMMHDVBHGLFANCNFSM5QZ3PSSQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/jrmarino/libsodium-ada/issues/1#issuecomment-1075214797,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACZJWNESBZABFQXKIRE6YNLVBHGYPANCNFSM5QZ3PSSQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Gradient of an L2 / DG solution

Hi there,
I am trying to calculate the gradient of a DG solution I obtained from example 14.
My initial thought was to project the gradient using a GradientGridFunctionCoefficient onto an RT space, with code like this:
RT_FECollection rt_fec(order, dim);
FiniteElementSpace rt_fespace(&mesh, &rt_fec);
mfem::GridFunction gradx(&rt_fespace);
mfem::GradientGridFunctionCoefficient gradx_coeff(&x);
gradx.ProjectCoefficient(gradx_coeff);

An example problem is the unit square [0,1]x[0,1], with homogeneous Dirichlet boundary conditions ($u=0$), and the manufactured problem $u(x,y)=\sin(\pi x)\sin(\pi y)$, such that the source term $f(x,y)=2\pi^2\sin(\pi x)\sin(\pi y)$. If I use degree 1 L2 elements, the solution and its gradient look reasonable:

But when I use piecewise constant L2 elements, the gradient becomes 0:

This makes kind-of sense to me: the gradient of a piecewise constant L2 element is of course 0. But obviously this is not the most optimal approximation of the gradient: clearly there is information about the gradient hidden in the trace jumps. The same problem is encountered when GridFunction::GetDerivative is used, as suggested in #2867.
One idea, also suggested in #2867, would be to interpolate the solution onto a H1 space, and then take the gradient. Is this the optimal route? In particular, this sentence from Sun&Wheeler 2005 (Symmetric and Nonsymmetric Discontinuous Galerkin Methods for Reactive Transport in Porous Media, doi: 10.1137/S003614290241708X) struck me as important:

As a valuable property, DG schemes possess element-wise mass conservation.
OBB-DG satisfies local conservation strictly, whereas SIPG, NIPG, and IIPG are
locally conservative if the concentration jump term is considered as part of the
computed diffusive flux:

So, apparently, in order to calculate the flux, the concentration jump needs to be taken into account? Is there a simple way of obtaining these jumps? In #2294 it is suggested to "use the jumps as the dofs of RT_0", but I am unsure on how to do that.
-- Background --
I am mainly looking into this, because I am trying to understand local and global conservation properties of various FEM schemes (see also issue #4086). For that, I am comparing example 0, example 8 and example 14. In all of these I need to calculate the boundary flux in a way that is consistent with the discretization. If I just project the gradient onto an RT space, there is no conservation, so clearly something more sophisticated is needed. But I am not sure if the intermediate step via an H1 projection is the correct way of doing this. Perhaps I need a second solve to compute the numerical flux as a postprocessing step?
Perhaps a final related question: what is exactly the DG scheme used in example 14? I think SIPG, is that correct?

Update: I have a sort-of working solution. I project the gradient of the L2 solution onto an RT space, and after that I substract the trace jump multiplied by the stabilization factor: $\kappa [[u_h]]$, as suggested for example in 10.1016/j.apnum.2006.09.010, eq 27.
Now I get the following as the gradient of the piecewise constant L2 elements shown above:

I used the following bit of code:
// 12b. Calculate grad u_h
RT_FECollection rt_fec(order, dim);
FiniteElementSpace rt_fespace(&mesh, &rt_fec);
mfem::GridFunction gradx(&rt_fespace);
mfem::GradientGridFunctionCoefficient gradx_coeff(&x);
gradx.ProjectCoefficient(gradx_coeff);

// 12c. Calculate and subtract kappa * [[u_h]]
mfem::ElementTransformation *face_elem_transf;
mfem::ElementTransformation *transf;
for(int i = 0; i<mesh.GetNumFaces(); i++){

   //Obtain the physical locations of the RT face dofs
   const FiniteElement * elem = rt_fespace.GetFaceElement(i);
   const IntegrationRule & ir = elem->GetNodes();
   ElementTransformation * T = mesh.GetFaceTransformation(i);
   DenseMatrix P;
   T->Transform(ir, P);

   //Get elements left and right of the face of interest
   int elem1 = -1;
   int elem2 = -1;
   mesh.GetFaceElements(i,&elem1,&elem2);

   mfem::Array<int> face_dofs;
   rt_fespace.GetFaceDofs(i,face_dofs);

   mfem::IntegrationPoint ip;
   //Calculate the jumps
   for(int j = 0; j<ir.Size(); j++){

      mfem::Vector pos(P.GetColumn(j),dim);
      double jump = 0.0;

      //Get value for element 1
      if (elem1 >= 0)
      {
         // side 1
         face_elem_transf = mesh.GetElementTransformation(elem1);
         face_elem_transf->TransformBack(pos,ip);
         jump += x.GetValue(elem1,ip);
      }

      if (elem2 >= 0)
      {
         // side 2. Will be skipped if the face is a boundary fce
         face_elem_transf = mesh.GetElementTransformation(elem2);
         face_elem_transf->TransformBack(pos,ip);
         jump -= x.GetValue(elem2,ip);
      }

      //Account for orientation (face_dofs[j] might be negative)
      int index   = (face_dofs[j]<0) ? -face_dofs[j]-1 : face_dofs[j];
      double sign = (face_dofs[j]<0) ? 1.0 : -1.0;
      gradx[index] += sign*kappa*jump;
   }
}

Is this a reasonable and robust way of approaching this? Would you foresee any problems with this approach? Is there maybe a more standard way of doing this?

One way of doing this is to use the idea in DG of a numerical flux.
Let $V$ be the scalar DG space, and $W = [V]^d$ be the vector-valued DG space.
Let $u : \Omega \to \mathbb{R}$ be given. On a single element $\kappa$, we can consider the $L^2$ projection of $\nabla u$ onto $W$ by finding $\sigma \in W$ such that, for all $\tau \in W$,
$$\int_{\kappa} \sigma \cdot \tau ~ dx = \int_{\kappa} \nabla u \cdot \tau ~ dx.$$
Integrating the right-hand side by parts, you obtain
$$ \int_{\kappa} \sigma \cdot \tau ~ dx = - \int_{\kappa} u \nabla \cdot \tau ~ dx + \int_{\partial \kappa} u \tau \cdot n ~ ds $$
where $n$ is the outward facing normal from $\kappa$.
At this point, since the given $u$ is actually a DG function, we need to introduce a single-valued numerical flux $\hat{u}$ on element interfaces. Replacing $u$ with its numerical flux $\hat{u}$ in the surface integral and summing over all mesh elements, you arrive at
$$ \int_\Omega \sigma \cdot \tau ~ dx = - \int_{\kappa} u \nabla_h \cdot \tau ~ dx + \int_\Gamma \hat{u} [ \tau ]~ds $$
where the jump is defined by $[\tau] = \tau_1 n_1 + \tau_2 n_2$ and $\Gamma$ represents the mesh skeleton.
In MFEM, you can assemble the right-hand side, and solve the system with the (vector) DG mass matrix. As far as I know, MFEM doesn't have built-in integrators that compute exactly the RHS above. You could use something like the following:

Code for linear form integrators (click to expand)
class DomainLFDivIntegrator : public LinearFormIntegrator
{
private:
   Coefficient &Q;
public:
   DomainLFDivIntegrator(Coefficient &Q_) : Q(Q_) { }

   void AssembleRHSElementVect(const FiniteElement &el,
                               ElementTransformation &Tr,
                               Vector &elvect) override
   {
      const int dim = el.GetDim();
      const int ndof = el.GetDof();

      DenseMatrix dshape(ndof, dim);

      const IntegrationRule *ir = IntRule;
      if (ir == NULL)
      {
         int intorder = 2 * el.GetOrder();
         ir = &IntRules.Get(el.GetGeomType(), intorder);
      }

      elvect.SetSize(ndof * dim);
      elvect = 0.0;

      for (int i = 0; i < ir->GetNPoints(); i++)
      {
         const IntegrationPoint &ip = ir->IntPoint(i);

         Tr.SetIntPoint (&ip);
         real_t w = ip.weight * Tr.Weight() * Q.Eval(Tr, ip);
         el.CalcPhysDShape(Tr, dshape);

         for (int j = 0; j < ndof; ++j)
         {
            for (int d = 0; d < dim; ++d)
            {
               elvect[j + ndof*d] -= w * dshape(j, d);
            }
         }
      }
   }
};

class VectorDGPenaltyIntegrator : public BilinearFormIntegrator
{
protected:
   const double kappa;

   Vector shape1, shape2, nor, nh, ni;
   DenseMatrix jmat, mq, adjJ;

public:
   VectorDGPenaltyIntegrator(const double kappa_) : kappa(kappa_) { }
   virtual void AssembleFaceMatrix( const FiniteElement &el1,
                                    const FiniteElement &el2,
                                    FaceElementTransformations &Trans,
                                    DenseMatrix &full_elmat);
};

class FaceLFAverageNormalIntegral : public LinearFormIntegrator
{
private:
   Coefficient &Q;
public:
   FaceLFAverageNormalIntegral(Coefficient &Q_) : Q(Q_) { }

   void AssembleRHSElementVect(const FiniteElement &el,
                               ElementTransformation &Tr,
                               Vector &elvect) override
   {
      MFEM_ABORT("");
   }

   void AssembleRHSElementVect(
      const FiniteElement &el1,
      const FiniteElement &el2,
      FaceElementTransformations &Tr,
      Vector &elvect) override
   {
      const int dim = el1.GetDim();
      const int ndof1 = el1.GetDof();
      const int ndof2 = (Tr.Elem2No >= 0) ? el2.GetDof() : 0;

      Vector shape1(ndof1);
      Vector shape2(ndof2);
      Vector normal(dim);

      const IntegrationRule *ir = IntRule;
      if (ir == NULL)
      {
         int intorder = 2 * el1.GetOrder();
         ir = &IntRules.Get(el1.GetGeomType(), intorder);
      }

      elvect.SetSize((ndof1 + ndof2) * dim);
      elvect = 0.0;

      for (int i = 0; i < ir->GetNPoints(); i++)
      {
         const IntegrationPoint &ip = ir->IntPoint(i);

         Tr.SetAllIntPoints(&ip);
         const IntegrationPoint &eip1 = Tr.GetElement1IntPoint();

         if (dim > 1) { CalcOrtho(Tr.Jacobian(), normal); }
         else { normal[0] = 1.0; }

         el1.CalcShape(eip1, shape1);

         real_t q = Q.Eval(*Tr.Elem1, eip1);

         if (ndof2)
         {
            const IntegrationPoint &eip2 = Tr.GetElement2IntPoint();
            el2.CalcShape(eip2, shape2);

            const real_t q2 = Q.Eval(*Tr.Elem2, eip2);
            q = 0.5*(q + q2);
         }
         const real_t w = ip.weight*q;

         for (int d = 0; d < dim; ++d)
         {
            const real_t w_d = normal[d] * w;
            for (int j = 0; j < ndof1; ++j)
            {
               elvect[j + d*ndof1] += shape1[j] * w_d;
            }
            for (int j = 0; j < ndof2; ++j)
            {
               elvect[j + d*ndof2 + dim*ndof1] -= shape2[j] * w_d;
            }
         }
      }
   }

   void AssembleRHSElementVect(
      const FiniteElement &el,
      FaceElementTransformations &Tr,
      Vector &elvect) override
   {
      AssembleRHSElementVect(el, el, Tr, elvect);
   }
};

The system is then solved like this:
GridFunctionCoefficient u_coeff(&u);

FiniteElementSpace vec_fespace(&mesh, &fec, mesh.Dimension());

LinearForm grad_lf(&vec_fespace);
grad_lf.AddDomainIntegrator(new DomainLFDivIntegrator(u_coeff));
grad_lf.AddInteriorFaceIntegrator(new FaceLFAverageNormalIntegral(u_coeff));
grad_lf.AddBdrFaceIntegrator(new FaceLFAverageNormalIntegral(u_coeff));
grad_lf.Assemble();

BilinearForm mass(&vec_fespace);
mass.AddDomainIntegrator(new VectorMassIntegrator);
mass.Assemble();
mass.Finalize();

SparseMatrix &M = mass.SpMat();
DSmoother D(M);

GridFunction grad_u(&vec_fespace);

PCG(M, D, grad_lf, grad_u, 1, 20000, 1e-12, 0.0);

Another approach that is independent of any DG formulation is to use the so-call weak gradient from L2 to H(div) which is basically the transpose of the divergence, or more precisely it is defined by the same equation as the one above for $\sigma$, however, now both $\sigma$ and $\tau$ are in H(div) conforming space (e.g. using RT_FECollection). Both linear forms on r.h.s. are available in MFEM: VectorFEDomainLFDivIntegrator and VectorFEBoundaryFluxLFIntegrator (only terms at the domain boundary are non-zero), see https://mfem.org/lininteg/.

Hi @v-dobrev, thanks for chiming in!!
You mean like so?
RT_FECollection rt_fec(order, dim);
FiniteElementSpace rt_fespace(&mesh, &rt_fec);
GridFunctionCoefficient u_coeff(&x);

LinearForm grad_lf(&rt_fespace);
grad_lf.AddDomainIntegrator(new VectorFEDomainLFDivIntegrator(u_coeff));
grad_lf.AddBoundaryIntegrator(new VectorFEBoundaryFluxLFIntegrator(u_coeff));
grad_lf.Assemble();

BilinearForm mass(&rt_fespace);
mass.AddDomainIntegrator(new VectorFEMassIntegrator);
mass.Assemble();
mass.Finalize();

SparseMatrix &M = mass.SpMat();
DSmoother D(M);
GridFunction gradx(&rt_fespace);
PCG(M, D, grad_lf, gradx, 1, 20000, 1e-12, 0.0);

This once again seems to work okay for higher element orders (let's say degree 2 and higher), but when using -o 0 the boundary values are clearly incorrect:

I suspect the issue is that the coefficient in the VectorFEDomainLFDivIntegrator should be -u, not u because the form implements $l(v) = (Q, \nabla\cdot v)$.

Hmm yes, I considered this as well. And while it does improve the results a bit, it still doesn't look right:

I don't know if this is still an issue in the code or this is to be expected for order = 0. If you can post the code you are running, I can take a quick look for any other issues and try to run it myself to try to figure out if there is still an issue.

Thank you @v-dobrev, that would be very helpful!
I added all code mentioned throughout this issue to this zip: issue_4535.zip. I also added the relevant pieces of CMakeLists.txt and the mesh that I used (ref-square.mesh). You will find three versions of the code:

ex14_conservation_test_v1.cpp: my own attempt, see this comment.
ex14_conservation_test_v2.cpp: version with method suggested by @pazner, in this comment
ex14_conservation_test_v3.cpp: version with method suggested by you.

In all these scripts I calculate the error for u_h and the error in the Flux. I also calculate the global conservation:
$$\iint_\Omega f dS = \oint_\Gamma \hat{n} \cdot \nabla u dl$$
Only ex14_conservation_test_v1.cpp shows a gradient that seems correct for -o 0, and that shows global conservation up to machine precision for all orders. But once again I am not convinced of its generality and robustness. I have not tested this approach with unstructured triangular meshes for example.

Hi @Rickbude,
First some general comments/questions about approximating the gradient of a DG function that does not necessarily come from a DG discretization of the Laplacian:
Does the method you describe work if you don't have prescribed Dirichlet boundary values for $u$? i.e. if you're given an arbitrary $u_h \in V_h$, does it give you a good approximation to the gradient?
I agree that for piecewise constant data, the values at the boundary will be inaccurate with the method I described unless you can incorporate additional information (just think of it in terms of finite difference stencils — if you want an accurate derivative at the boundary, you will need to use one-sided stencils, which are not really natural to do in the finite element context). If you have additional Dirichlet data they can be incorporated into the numerical flux.
I don't think there's necessarily a "right answer" about whether to use $[L^2]^d$ vs $\mathrm{RT}$. But with DG methods, the flux and the scalar are approximated in $L^2$, so it seemed natural to do the same.
The penalty term is needed to ensure stability of the DG bilinear form, but it is not needed just to recover the gradient.

In the case of recovering the flux from the solution $u_h$ of a DG discretization of the Laplacian, there is a well-defined answer to your question. The flux $\sigma_h \in [V_h]^d$ satisfies equation (3.4) from the "unified analysis" paper that you cited in your previous response; since the numerical flux $\hat{u}$ is single-valued, this simplifies to
$$ \int_\Omega \sigma_h \cdot \tau ~ dx = -\int_\Omega u_h \nabla_h \cdot \tau~dx + \int_{\Gamma^0} \hat{u} [\tau] ~ ds. $$
The IPDG method follows by choosing $\hat{u} = { u_h }$ and $\hat{\sigma} = \{ \nabla_h u_h \} - \mu [ u_h ]$.
Inserting the numerical flux $\hat{u}$ into the variational form for $\sigma_h$ you obtain the expression that I included in my previous response.
If you are interested in the conservation properties of the method, those are stated in terms of the numerical flux $\hat{\sigma}$ on the element faces (see equation (3.2) of the paper). For the IPDG method, the numerical fluxes are given by the above expression, $\hat{\sigma} = \{ \nabla_h u_h \} - \mu [ u_h ]$. I believe these should be expressible in MFEM using the RT_Trace_FECollection.

Thanks @pazner for these insights.

Does the method you describe work if you don't have prescribed Dirichlet boundary values for $u$?

I have not tried this yet, but I think no. The code I proposed assumes homogeneous Dirichlet boundary conditions at the complete boundary. I suspect that I would need to do something like this for the Interior, Dirichlet and Neumann edges respectively 10.1016/j.apnum.2006.09.010:

I did some further testing, and noticed that none of the methods above seem to be able to produce a satisfactory plot of the gradient on a triangular mesh, with piecewise elements. I.e. -o 0 -r 2:

With higher order elements the results are better for method 1 and 3. I.e. -o 2 -r 0:

None of the methods shows conservation.
I should mention I keep saying "gradient", but in this case I think I am actually more interested in the flux, because I want to check local and global conservation claims.
In a "real" simulation of the Poisson equation, where we solve for the potential $\phi$, I would be more interested in the electric field $\vec{E}=-\nabla \phi$, which would be input to other physical equations. I wonder how valid it would be to calculate the electric flux $\vec{D}$ first using the expression for the numerical flux you mentioned, and then approximate $\vec{E}=\frac{1}{\epsilon}\vec{D}$. Instead of using the discrete divergence directly for $\vec{E}$, which would be $\vec{0}$ for degree 0 elements.
By the way: the reason I am so interested in piecewise constant $L_2$ elements, is because I want to compare this FEM discretization to an equivalent Finite Volume discretization. Which is, as I understand it, basically the same as a DG formulation with degree 0 elements.

FWIW, $p=0$ with IPDG will not generally be convergent (even in $L^2$ norm). You will have to pick the penalty parameter very carefully, and there may be additional restrictions on the mesh. (For $p > 0$, the penalty parameter simply needs to be "sufficiently large", and the mesh can be general). See this question and the related discussion for more details.
For $p > 0$, basically all of the DG methods (IPDG, LDG, etc.) are conservative in the sense that
$$ \int_{\partial\kappa} \hat{\sigma} \cdot n ~ ds = -\int_{\kappa} f ~ dx $$
for all mesh elements $\kappa$. (If you are seeing problems with conversation in your numerical examples, my guess would be that the way you are computing $\hat{\sigma}$ is not consistent with what is happening inside the DG integrator).

Hmm in the comments under the very stackexchange post you mentioned, it is said that SIPG, which I suppose is what is used by default in example 14, has convergence of the order $h^{p+1}$. This seems to come from Hartman 2008  "Numerical Analysis of Higher Order Discontinuous Galerkin Finite Element Methods", eq 264. So then even with $p=0$, first order convergence should be expected, right?
And this is also (I think) what I observe: I do not experience convergence problems in the scalar potential $u_h$ itself with $p=0$, that just works as expected. Only the flux/gradient reconstruction is giving me headaches.
If the numerical flux is incorrect/inconsistent, what should it be? Note that I am just using the stock example 14: I only added a source in the right-hand side, and I am trying to get a decent approximation of the flux/gradient. So nothing fancy.

Indeed the $L^2$ order of convergence for IPDG is $\mathcal{O}(h^{p+1})$. The convergence behavior of various DG methods is summarized in this table:

However, note that this result holds for $p \geq 1$. The standard reference for these methods is the "unified analysis" paper referenced earlier; see the paragraph above equation (1.2) for the statement of the condition that $p \geq 1$.
The $L^2$ error estimates are derived using the standard duality argument ("Nitsche's trick"), as described in the beginning of section 5.1 of the paper. This argument requires that the piecewise linear interpolant of the true solution lies in the finite element space. For $p = 0$ DG this is not the case, and the argument doesn't go through.
To see an example of lack of convergence, simply change the kappa (penalty parameter) value — by default, MFEM sets $\kappa = (p+1)^2$, so when $p = 0$, $\kappa = 1$. If you override this choice, you should see lack of convergence. (Write out the method in 1D and you will see that it does not make sense except for specially chosen $\kappa$ to recover a finite volume-type method).

Closing for now. @Rickbude, please re-open if you have any other questions.