MSC2326: Label based filtering

Rendered

Seems generally sane to me.

Some more potential problems:

No way to list all threads in a room without crawling the entire room
history.
This could be mitigated by having the client crawl the room and
remembering/indexing the labels. Since this is also necessary for E2EE
search, it seems like a feasible solution.

The described scheme makes it difficult to build rainbow tables, but since
# labels will commonly be natural language (not random data), it will still
be quite simple to leak the labels from label hashes in most cases. For
instance, an attacker could just take a list of the 10000 most common English
words and hash them on the fly, probably uncovering most labels. Even
producing simple variations (word_word, wordword, WordWord,
Word_Word, etc) and checking them all is feasible on modern hardware.
What if the label hash was peppered and the pepper stored in the encrypted
part of the labelled event? The hash would then be calculated as Hash(label
|| roomid || pepper) instead of Hash(label || roomid), e.g.
#fun!someroom:example.com!PEPPER.

Hey @dkasak, thanks for your feedback!

Some more potential problems:

No way to list all threads in a room without crawling the entire room
history.
This could be mitigated by having the client crawl the room and
remembering/indexing the labels. Since this is also necessary for E2EE
search, it seems like a feasible solution.

FWIW crawling the entire room history isn't always a realistic expectation to have from clients, especially in big and old rooms with thousands of messages and hundreds of servers.
Another solution for this would have to spec a federation endpoint to ask each server in the room for the list of labels (or hashes) it knows about for this room, but this is also bound to create issues in big and old rooms.
I'd rather have this feature of listing every label in a room as a non-spec'd one which existence and behaviour are left as an implementation detail, in order to keep this MSC simple. If there is a need for it to be in the spec, it can also be done in a separate MSC.

The described scheme makes it difficult to build rainbow tables, but since
# labels will commonly be natural language (not random data), it will still
be quite simple to leak the labels from label hashes in most cases. For
instance, an attacker could just take a list of the 10000 most common English
words and hash them on the fly, probably uncovering most labels. Even
producing simple variations (word_word, wordword, WordWord,
Word_Word, etc) and checking them all is feasible on modern hardware.
What if the label hash was peppered and the pepper stored in the encrypted
part of the labelled event? The hash would then be calculated as Hash(label
|| roomid || pepper) instead of Hash(label || roomid), e.g.
#fun!someroom:example.com!PEPPER.

Although I agree with your point, and like your solution, the whole point of using hashes instead of e.g. random opaque strings is to ensure that two clients can only use the same identifier for the same label text. Bearing in mind that we need to be able to use the label identifiers to filter the history of the room server-side (because we're not expecting clients to know about the whole history of the room, see my first point above), opaque strings had the following downsides, all originating from the fact that nothing would prevent 1000 clients from using each a different identifier:

filtering would have serious performances issues in E2EE rooms, as the server would need to return all events it knows about which label identifier is any of the 1000 identifiers provided by the client, which is quite expensive to do (even when using PostgreSQL with the right indexing strategy).
it would be impossible for a filtered /message (or /sync) request to include every event matching the desired label because we can't expect a client to know about every identifier that has been used in the whole history of the room, or about the fact that another client might suddenly decide to use another identifier for the same label text, and include those identifiers in its filtered request.

Although what your proposing isn't using a random opaque string, it would still end up having different identifiers for a same label, which would end up causing the issues with filtering I've already mentioned. This hash(label + room_id) solution is the best compromise we've come up with between enabling filtering and hiding the actual label as much as possible from servers.
I realise that this explanation belongs to an "Alternative solutions" section of the MSC which I've actually forgotten to add, I'll update the proposal with it.

@Half-shot:

It's important to note here that the ID + text label is used to mainain
consistency of the key without having access to history. E.g. a random new
joiner without history could compute the same hash for the same label as
another client.

This was indeed the part I was missing, but I'm less clear on why this ability
is useful.
I suppose the intent is to enable users wanting to talk about (e.g.) cats to
simply start sending messages labelled with #cats. However, the room might
have an existing thread for talking about cats -- yet it is called #Cats or
#cats![*] but the user is unaware of them. Furthermore, the new #cats
thread might also be entirely contextually unrelated to the old one (except
sharing a name coincidentally), but a user has no way of knowing this without
the ability to inspect the old thread's content.
In essence, continuing an old thread seems primarily useful when you have the
ability to access the old content. But if you can access the old content, then
you also have access to the corresponding pepper to continue that particular
thread.
I suppose the desired scenario might be to make labelling a message with
a particular label (or, to put it differently, putting the message in
a particular "bin") cheap, while making only the retrieval potentially costly
(due to having to walk the room's history). Is this the design goal you had in
mind? In that case, I can see how the unpeppered system provides an advantage.
However, I still consider this ability to be of limited value if one is unable
to inspect either the set of all labels or the content behind them.
My main concern is that just hashing the labels has a rather large downside of
simply obscuring them from casual glances but doing nothing to truly hide them.
They are effectively public information, but this is made unobvious by the fact
that they are hashed.
[*]: Which makes me think of another problem: is ! disallowed in labels due
to it also being used as a separator? More generally, which characters are
allowed?

[*]: Which makes me think of another problem: is ! disallowed in labels due
to it also being used as a separator? More generally, which characters are
allowed?

On second thought, there's probably no problem with any character here since there's no parsing involved.

Again, that is not an issue with this MSC, and this MSC doesn't aim to solve it.

I realized I haven't said so earlier, so just to be sure: I'm not advocating for this MSC to gain the ability to list all labels.

The labels are not public information in E2EE rooms, which is the only scenario in which hashing happens (and is also the reason hashing happens).

Yes, sorry, my wording was not the best. What I meant is that the server will be able to reverse the hashes (and hence read the labels) easily in a very large number of cases, if it wants to. I wouldn't had considered this to be the case for E2EE rooms intuitively, had I not seen this MSC.
That is, unless people start naming their threads with peppers embedded in them. ;)
(also, sorry, I didn't understand Travis' comment; is there a Github threading feature I'm not aware of or was that tongue-in-cheek?)

Line comments on the diff rather than using the comment box here are threads. Trying to track down what people are talking about here is way too difficult, which is why we require people to use threads.

Is there a length limit for labels?

Is there a length limit for labels?

Good catch, I've added one in https://github.com/matrix-org/matrix-doc/pull/2326/commits/45225af7b205a83b307d25810d3fa9cb5d1602a5 to a maximum of 100 chars, which should be a decent enough length.

Would this be applicable for threaded messages as well or is the general consensus to leave this up to MSC1849 and MSC1198? Ex, it could be possible to set the label to an event ID. The issue is that syncing for threaded messages for every message in the displayed history could be costly.

Would this be applicable for threaded messages as well or is the general consensus to leave this up to MSC1849 and MSC1198? Ex, it could be possible to set the label to an event ID.

The reason for the labels being freeform text is to allow as many use cases as possible, so yes that's very much a possible use of this feature (though as highlighted in your comment and the MSC itself it's a minimalistic approach and other MSCs might want to take it further).

The issue is that syncing for threaded messages for every message in the displayed history could be costly.

As long as you have the label text you should be able to just give the right filter to /messages or /sync and the server should be able to handle it just fine.
Also, as highlighted in a previous discussion, if you have further remarks/questions can please you do so in a thread (by adding an inline comment in the PR's diff (on whichever line feels relevant, or the first one), which seems to be the only way to do threads in GitHub).

Seeing as this MSC has become quite developed and already had some approving looks from other spec core team members, I'm going to propose a final comment period:
@mscbot fcp merge

In terms of Synapse implem, there's some basic support as https://github.com/matrix-org/synapse/pull/6301, and https://github.com/matrix-org/synapse/issues/6288 tracks other remaining items related to this feature.

I was discussing a different topic with @anoadragon453 yesterday for which this might be a solution as well, so I wanted to mention that here.
Telegram has an overview of shared content per chat-room, it looks like this:

This is really handy for finding stuff, especially the images and links part. As this indexing needs to be done server side and also in encrypted rooms we'd need a way to attach labels to messages, which state, this message contains an image/at least one link/an attachement/etc.
The labels for this would need to be interpreted by the server, so for encrypted rooms we'd need to use a set of well-known labels.
This will obviously leak metadata, so this would probably need to be an optional feature for encrypted rooms.

I was discussing a different topic with @anoadragon453 yesterday for which this might be a solution as well, so I wanted to mention that here.
Telegram has an overview of shared content per chat-room, it looks like this:

This is really handy for finding stuff, especially the images and links part. As this indexing needs to be done server side and also in encrypted rooms we'd need a way to attach labels to messages, which state, this message contains an image/at least one link/an attachement/etc.
The labels for this would need to be interpreted by the server, so for encrypted rooms we'd need to use a set of well-known labels.
This will obviously leak metadata, so this would probably need to be an optional feature for encrypted rooms.

@mscbot concern This needs a client implementation to see how all this works.
@mscbot concern Server-side implementation(s) needs linking in the PR description.

@mscbot concern this talks about edits, so we can't get this through FCP until #1849 is done.

@mscbot concern hashing the labels in encrypted rooms provides a very false sense of security. i think we should add a pepper to the hash, which can be sent to new users in an encrypted msg when they're invited to the room (if the new users need to know about the existing labels).

This seems to have lots of outstanding concerns, and is generally looking a bit unloved, so I don't think it's ready for FCP generally.
@mscbot fcp cancel


installing units in clean project in RStudio - libudunits2.so not found!

user gets the error:
  libudunits2.so not found!

  If the udunits2 library is installed in a non-standard location, use:
    --configure-args='--with-udunits2-lib=/usr/local/lib'
  for example, if the library was not found, and/or
    --configure-args='--with-udunits2-include=/usr/include/udunits2'
  if the header was not found, replacing paths with appropriate values for your
  installation. You can alternatively use the UDUNITS2_INCLUDE and UDUNITS2_LIBS
  environment variables.

  If udunits2 is not installed, please install it.
  It is required for this package.
--------------------------------------------------------------------------------```
this could be solved by adding:
```libudunits2-dev```
to `files/apt_packages`

work around here: https://github.com/r-quantities/units/issues/1#issuecomment-330435512


Rename repo

The name is confusing since we rarely use this for building styles that are hosted on Mapbox or use Mapbox's current libraries. Mainly we use Maplibre so we should make the name more generic, something like gl-style-build.

There are also a ton of public (if not publicized) Stamen repos with similar names that should also be renamed:

lint-mapbox-gl-style-action
mapbox-gl-style-remove-defaults
mapbox-gl-style-diff
mapbox-gl-style-performance-linter
mapbox-gl-style-linter
mapbox-gl-style-recurse
mapbox-gl-style-format

Just noting that before we change the names, we should confirm Github can gracefully handle the name change in a backwards compatible way for previous versions.
Similarly, we will need to check in on the behavior regarding whether pulling in tags previous to the name change require the old name or not.


Would be cool to have an explainer for an object detection pipeline as well

Good suggestion! Currently CNN Explainer only supports the Tiny-VGG architecture. We will consider explaining more model types in the future.
I will close this issue for now. Feel free to reply or reopen it if you need further help :)


Remove dependencies for EKS Distro version upgrade step

The EKS Distro upgrade step is added as a "final stage" to the upgrader buildspec because it isn't a project in the projects folder so doesn't get added along with other projects in the loop. The generate script usually adds all the previous stages as dependencies to this final stage, but in this case, there is no actual dependency, so we are removing the dependencies from the buildspec.
This also avoids the problem of the EKS Distro upgrade step being skipped (unnecessarily) when any of the other project upgrades fail.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/lgtm
/approve


feat: OIDC auth-type SERVICE_PRINCIPAL using msi + Entity type Environment - fork test

Description
Do not merge, final (same) code will be implemented in a branch
Ref #2092

Pipeline Reference

Pipeline

Type of Change

[ ] Update to CI Environment or utilities (Non-module affecting changes)
[ ] Azure Verified Module updates:

[ ] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

Checklist

[ ] I'm sure there are no other open Pull Requests for the same update/change
[ ] I have run Set-AVMModule locally to generate the supporting module files.
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings

Closing in favor of #2792


Exception: object_mask expects strings (ArgumentError)

According to: http://sldn.softlayer.com/article/ruby, the object mask should be specified as:
object_mask = {
     "hardware" => {
        "operatingSystem" => {
            "passwords" => "",
        },
        "networkComponents" => "",
        "datacenter" => "",
        "processorCount" => ""
    }
}

I got the exception: object_mask': object_mask expects strings (ArgumentError)
The code that I tried:
require 'softlayer_api'
require 'pp'

user_id = "your user id"
 api_key = "your API key"

object_mask = {"orderItem" => {"order" => {"userRecord" => {"username" =>   ""}}},
"invoiceItem" => {"totalRecurringAmount" => ""}}

billing = SoftLayer::Service.new("SoftLayer_Account",:username => user_id,:api_key => api_key)
user_bill=billing.object_mask(object_mask).getNextInvoiceTopLevelBillingItems

pp user_bill

I solved my problem using:
object_mask = "mask[orderItem[order[userRecord[username]]], invoiceItem[totalRecurringAmount]]"
but, this kind of object mask is no longer supported?

Right, only string object masks are supported since April of 2014, so that article is really old. However, hash-tree object mask could come back with a PR.


Setting user properties

Hi @kaesonho,
Would you be willing to integrate methods in this spirit -> https://github.com/adlenafane/react-i13n-mixpanel/pull/1/files
Or would you rather have the user update / re-instantiate the plugin

Opening the PR

thanks @adlenafane , the code looks good to me, however I'm thinking if users should access ga plugin instance directly and do whatever they need?
for example
var instance = ReactI13nGoogleAnalytics.getInstance();
instance.command( // do whatever they need


Update custom image search Node.js properties

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-ruby

Published to https://www.npmjs.com/package/azure-arm-monitor/v/3.0.0.

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go


[Language Codes] How are models named?

For example,
In,
cmn+cn+yue+ze_zh+zh_cn+zh_CN+zh_HK+zh_tw+zh_TW+zh_yue+zhs+zht+zh-de
Is there a table or some other source for what zh_HK, zh_yue, yue, etc. represent?
Is  zh_yue is different than yue?
is zh_cn different than cn somehow?
Thanks in advance!

This is a problem of OPUS which is, unfortunately, not always very consistent in the use of language IDs. Some corpora use different variants of regional variants or upper-case letters in the region code ro 3-letter language codes instead of 2-letter ISO-639-1 codes that I use otherwise. The thing is that I should fix consistencies in OPUS and that is a major thing to do. An intermediate solution would be to find a mapping before training the OPUS-MT models. Also not very easy ....

Would you mind if on the transformers side we named that model zh-de or zh_group-de, and document the original name on in a model card?
Do you foresee a naming collision?

Difficult to say whether this will be the best solution. There is not always a straightforward group name and there may be slightly different selections in something that could end up with a similar or the same group name. For example, assume that I train a new multilingual model for Celtic languages to English and I include or exclude a language for various reasons (too little data, new data ...) compared to previous models. That could be a problem if the model is called celtic-en.
By the way, how will you handle new versions of the same model? I use the package date to name the models. How will this be done at huggingface?

for group names, we would make sure that the model name is a perfect match for the group name. Else,  we would either (a) not post it or (b) replace all '+' symbols with 0 or some other separator character that S3 is OK with.

for 2, good question.
I propose an aliasing system where:

'en-fr' points to the latest en-fr model, and if a user specifies 'en-fr-{date}' that points to a path that never changes, but I'm open to other ideas. We shouldn't require the user to know which date you trained the model, IMO.

I will try to see if I can use some other naming conventions in the future. I could possibly introduce some kind of reasonable group names as well. Having all the language IDs in the path name make it easier to see explicitly the languages that are supported but I can understand that this becomes a bit tedious as well.
about 2: how do you handle new versions of other models at this point? I can assume that this happens for other LMs as well as things improve and change rapidly. Or do people simply create a new model with a completely new name? For example, improved language-specific models might get some updates etc. At least for the MT models I will try to release as quickly as possible to make things available but that may lead to various updates of existing models. Is that a problem?

Versioning: We don't have a standard way. It's up to the poster
Some people just tag them with v1 like Musixmatch/umberto-commoncrawl-cased-v1`, but I could add some of the aliasing code to make it more like a pip install, where users get the latest, but people who want compatibility can pin stuff.
Updating: Nothing will auto update at the moment, but I can do it semi-manually if you'd like.


Wrong evaluation reply using ChatGPT

Hi,
When I use my output.json and the repo's test_eval.json, it worked the first two times. However, now I see ChatGPT replies such as:

I would rate your answer as 10.

which leads to the following error:
evaluation/0 [0]:  File "/workspace/evaluation.py", line 194, in <module>
evaluation/0 [0]:    output = evaluation.evaluation()
evaluation/0 [0]:  File "/workspace/evaluation.py", line 153, in evaluation
evaluation/0 [0]:    scores["match"] = self.eval_match()
evaluation/0 [0]:  File "/workspace/evaluation.py", line 71, in eval_match
evaluation/0 [0]:    outs2 = self.eval_chatGPT(self.match["GPT"])
evaluation/0 [0]:  File "/workspace/evaluation.py", line 46, in eval_chatGPT
evaluation/0 [0]:    scores = list(map(float, scores))
evaluation/0 [0]:ValueError: could not convert string to float: 'I would rate your answer as 10.'

Based on previous issues https://github.com/OpenDriveLab/DriveLM/issues/92, https://github.com/OpenDriveLab/DriveLM/issues/53, it seems like this should have been fixed, but I'm still facing this issue.
Can someone help me out?

Thank you for your interest. Are you running eval on your local env or our test server?


Add installation support for Laravel 5.3

Now that Laravel 5.3 has officially been released, it would be awesome if this package could be updated to be installable in new projects.
Currently, running composer require hieu-le/active in a new Laravel project errors out with dependency failures.
Thanks, dude! 😃

Hi,
I updated the composer.json file so that you can install this package with Laravel 5.3 now.
composer require hieu-le/active
If you cannot see the version 3.3.x is loaded, run this command
composer require hieu-le/active:^3.3

Awesome! It worked.
Thanks and keep up the good work 😃


feat: update to ESM

I updated this project to be ESM and use ESM dependencies, including rdf/js environment

Would actually wait to include https://github.com/rdf-ext/rdf-transform-triple-to-quad/pull/2 too


fix(split-pane): allow menu to be wrapped in a custom component

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (npm run build) was run locally and any changes were pushed
[x] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: fixes https://github.com/ionic-team/ionic/issues/20681
What is the new behavior?

Update CSS and JS to allow for more flexibility in ion-menu location

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

I fixed the previous issues discussed offline. Dev build: 5.1.0-dev.202005121549.a2bb106.

@liamdebeasi I'll test this out soon.


[Icon] Icon are resolved as text on IE

Icon are resolved as text on IE:
With IE :
Secondary action

:red_circle: Fail
Scroll to top:

:red_circle: Fail
With Firefox:
Secondary action

:large_orange_diamond: Still a z-index problem with Block component
Scroll to top:

:white_check_mark: Success

Maybe a specific font file is missing. IE uses other fonts

https://google.github.io/material-design-icons/#icon-images-for-the-web

@Bernardstanislas  @Tommass Any opinion on that?

Suggestion create a component Icon for ie9 with a mapping on components

:+1:

For Info, I have the bug with the version 11 of IE

Maybe the probem is your server which does not know how to serve this specific font file...
Font awesome provide sevral fonts.

Maybe you can check https://github.com/google/material-design-icons/tree/master/iconfont which should be in the associated package.json file

https://github.com/google/material-design-icons/issues/205

<link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons">

This works on ie

Was working in our localhost and recette environment.
Still working in localhost but not in recette environement.

@Jerom138 maybe it is the same problem for old FF

@durandx Google has indeed published a new mdl lite version, we didn't upgrade in foocus components.

@pierbrisson

Got the issue on both IE and FF, what do i have to do to fix this ?

Hi, I just updated focus-core and focus-components, and my icons are still not displayed on IE in recette environment (it works in localhost).

did you add this line in the header of your index.html or JSP file  ?
<link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons">

Sorry, now it's resolved.
The problem was that I didn't add material-design-icons-iconfont for IE compatibility.

Please can you explain what did you do in detail ?

I added the node.js module material-design-icon-iconfont to my project.
I imported the module in a js file with
import 'material-design-icons-iconfont/dist/material-design-icons.scss';

and then it worked.

We have switched to webpack (from brunch) 2 or 3 month ago, and the font is now correctly inlined in the css along with some localhost:3000/xx.eot url. With Chrome and Firefox, the inlined is taken, but with IE11 (and 10) the font use the localhost:3000 url.
@xuaveneg Does your solution is working with IE 11 ?

@durandx I helped @JRLK with a similar issue last week it was due to webpack config.
Maybe @JRLK can comment the solution on this issue.

@pierr We work only with Chrome not with IE.
The issue we looked together was about absolute and relative path to access to the fonts.
I don't think the issue @durandx is talking about is the same.

Linked to : https://github.com/KleeGroup/focus-components/issues/1125

Solution here : https://github.com/KleeGroup/webpack-focus/issues/9


Image path corrected

Fixes #1

[x]     Cover and Project Admin's images are corrected and visible.
[x]     </a> near to the Cover Image removed.
[x]     Unnecessary dashed line in-between Project Admin's image and Visitors count are removed.

After

Before

Fork hosted in : https://jishnukoliyadan.github.io/Open-Source-Programs/

Thanks for the correction and rectifying it. Kudos to your initiation. 👍👌@jishnukoliyadan

Thanks for merging it 🙂


Error when using pmap and plan_fft!

Version info:
julia> versioninfo()
Julia Version 1.7.2
Commit bf53498635 (2022-02-06 15:21 UTC)
Platform Info:
  OS: Windows (x86_64-w64-mingw32)
  CPU: Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-12.0.1 (ORCJIT, skylake)
Environment:
  JULIA_HOME = C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\bin
  JULIA_NUM_THREADS = 3
  JULIA_PKG_SERVER = https://mirrors.tuna.tsinghua.edu.cn/julia
julia> using FFTW

julia> FFTW.get_provider()
"fftw"

Code to reproduce:
using Distributed
using ClusterManagers
addprocs(2)
@everywhere begin
    using FFTW
    FFTW.set_num_threads(1)
    ##
    N=round(Int, 2048)
    ##
    Tpx=plan_fft(rand(ComplexF64,N))
    ##
    function mapfunc(Tpx)
        test2->Tpx* test2
    end
    f=mapfunc(Tpx)
end
##
test2=[rand(ComplexF64,N), rand(ComplexF64,N)]
F=pmap(f,test2)
print(F)
##

Error message:
julia debug.jl
      From worker 2:
      From worker 2:    Please submit a bug report with steps to reproduce this fault, and any error messages that follow (in their entirety). Thanks.
      From worker 2:    Exception: EXCEPTION_ACCESS_VIOLATION at 0x54496564 -- .text at C:\Users\dell\.julia\artifacts\b7dd1809d0626eac3bf6f97ba8ccfbb6cc63c509\bin\libfftw3-3.dll (unknown line)
      From worker 2:    in expression starting at none:0
      From worker 2:    .text at C:\Users\dell\.julia\artifacts\b7dd1809d0626eac3bf6f97ba8ccfbb6cc63c509\bin\libfftw3-3.dll (unknown line)
      From worker 2:    unsafe_execute! at C:\Users\dell\.julia\packages\FFTW\SDUwi\src\fft.jl:466 [inlined]
      From worker 2:    * at C:\Users\dell\.julia\packages\FFTW\SDUwi\src\fft.jl:721 [inlined]
      From worker 2:    #3 at F:\Simulation\Trap simulation\2layers trap\BEM2Layers\ElectronTrapPost\DC_1D\th2\debug.jl:13
      From worker 2:    unknown function (ip:<PHONE_NUMBER>d93c66)
      From worker 2:    jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined]
      From worker 2:    do_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\builtins.c:713
      From worker 2:    #106 at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:278
      From worker 2:    run_work_thunk at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:63
      From worker 2:    macro expansion at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:278 [inlined]
      From worker 2:    #105 at .\task.jl:423
      From worker 2:    unknown function (ip:<PHONE_NUMBER>d858a3)
      From worker 2:    jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined]
      From worker 2:    start_task at /cygdrive/c/buildbot/worker/package_win64/build/src\task.c:877
      From worker 2:    Allocations: 7967560 (Pool: 7964384; Big: 3176); GC: 10
      From worker 3:
      From worker 3:    Please submit a bug report with steps to reproduce this fault, and any error messages that follow (in their entirety). Thanks.
      From worker 3:    Exception: EXCEPTION_ACCESS_VIOLATION at 0x544e6564 -- .text at C:\Users\dell\.julia\artifacts\b7dd1809d0626eac3bf6f97ba8ccfbb6cc63c509\bin\libfftw3-3.dll (unknown line)
      From worker 3:    in expression starting at none:0
      From worker 3:    .text at C:\Users\dell\.julia\artifacts\b7dd1809d0626eac3bf6f97ba8ccfbb6cc63c509\bin\libfftw3-3.dll (unknown line)
      From worker 3:    unsafe_execute! at C:\Users\dell\.julia\packages\FFTW\SDUwi\src\fft.jl:466 [inlined]
      From worker 3:    * at C:\Users\dell\.julia\packages\FFTW\SDUwi\src\fft.jl:721 [inlined]
      From worker 3:    #3 at F:\Simulation\Trap simulation\2layers trap\BEM2Layers\ElectronTrapPost\DC_1D\th2\debug.jl:13
      From worker 3:    unknown function (ip:<PHONE_NUMBER>df4566)
      From worker 3:    jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined]
      From worker 3:    do_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\builtins.c:713
      From worker 3:    #106 at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:278
      From worker 3:    run_work_thunk at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:63
      From worker 3:    macro expansion at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:278 [inlined]
      From worker 3:    #105 at .\task.jl:423
      From worker 3:    unknown function (ip:<PHONE_NUMBER>de61a3)
      From worker 3:    jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined]
      From worker 3:    start_task at /cygdrive/c/buildbot/worker/package_win64/build/src\task.c:877
      From worker 3:    Allocations: 7968181 (Pool: 7965007; Big: 3174); GC: 10
Worker 2 terminated.
ERROR: LoadError: Worker 3 terminated.ProcessExitedException
(2)
Stacktrace:
  [1] (::Base.var"#892#894")(x::Task)
    @ Base .\asyncmap.jl:177
  [2] foreach(f::Base.var"#892#894", itr::Vector{Any})
    @ Base .\abstractarray.jl:2694
  [3] maptwice(wrapped_f::Function, chnl::Channel{Any}, worker_tasks::Vector{Any}, c::Vector{Vector{ComplexF64}})
    @ Base .\asyncmap.jl:177
  [4] wrap_n_exec_twice
    @ .\asyncmap.jl:153 [inlined]
  [5] #async_usemap#877
    @ .\asyncmap.jl:103 [inlined]
  [6] #asyncmap#876
    @ .\asyncmap.jl:81 [inlined]
  [7] pmap(f::Function, p::WorkerPool, c::Vector{Vector{ComplexF64}}; distributed::Bool, batch_size::Int64, on_error::Nothing, retry_delays::Vector{Any}, retry_check::Nothing)
    @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\pmap.jl:126
  [8] pmap(f::Function, p::WorkerPool, c::Vector{Vector{ComplexF64}})
    @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\pmap.jl:101
  [9] pmap(f::Function, c::Vector{Vector{ComplexF64}}; kwargs::Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
    @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\pmap.jl:156
 [10] pmap(f::Function, c::Vector{Vector{ComplexF64}})
    @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\pmap.jl:156
 [11] top-level scope
    @ F:\Simulation\Trap simulation\2layers trap\BEM2Layers\ElectronTrapPost\DC_1D\th2\debug.jl:19
in expression starting at F:\Simulation\Trap simulation\2layers trap\BEM2Layers\ElectronTrapPost\DC_1D\th2\debug.jl:19
Unhandled Task ERROR: EOFError: read end of file
Stacktrace:
 [1] (::Base.var"#wait_locked#645")(s::Sockets.TCPSocket, buf::IOBuffer, nb::Int64)
   @ Base .\stream.jl:892
 [2] unsafe_read(s::Sockets.TCPSocket, p::Ptr{UInt8}, nb::UInt64)
   @ Base .\stream.jl:900
 [3] unsafe_read
   @ .\io.jl:724 [inlined]
 [4] unsafe_read(s::Sockets.TCPSocket, p::Base.RefValue{NTuple{4, Int64}}, n::Int64)
   @ Base .\io.jl:723
 [5] read!
   @ .\io.jl:725 [inlined]
 [6] deserialize_hdr_raw
   @ C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\messages.jl:167 [inlined]
 [7] message_handler_loop(r_stream::Sockets.TCPSocket, w_stream::Sockets.TCPSocket, incoming::Bool)
   @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:165
 [8] process_tcp_streams(r_stream::Sockets.TCPSocket, w_stream::Sockets.TCPSocket, incoming::Bool)
   @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:126
 [9] (::Distributed.var"#99#100"{Sockets.TCPSocket, Sockets.TCPSocket, Bool})()
   @ Distributed .\task.jl:423
Unhandled Task ERROR: EOFError: read end of file
Stacktrace:
 [1] (::Base.var"#wait_locked#645")(s::Sockets.TCPSocket, buf::IOBuffer, nb::Int64)
   @ Base .\stream.jl:892
 [2] unsafe_read(s::Sockets.TCPSocket, p::Ptr{UInt8}, nb::UInt64)
   @ Base .\stream.jl:900
 [3] unsafe_read
   @ .\io.jl:724 [inlined]
 [4] unsafe_read(s::Sockets.TCPSocket, p::Base.RefValue{NTuple{4, Int64}}, n::Int64)
   @ Base .\io.jl:723
 [5] read!
   @ .\io.jl:725 [inlined]
 [6] deserialize_hdr_raw
   @ C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\messages.jl:167 [inlined]
 [7] message_handler_loop(r_stream::Sockets.TCPSocket, w_stream::Sockets.TCPSocket, incoming::Bool)
   @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:165
 [8] process_tcp_streams(r_stream::Sockets.TCPSocket, w_stream::Sockets.TCPSocket, incoming::Bool)
   @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:126
 [9] (::Distributed.var"#99#100"{Sockets.TCPSocket, Sockets.TCPSocket, Bool})()
   @ Distributed .\task.jl:423

Without FFTW but with an anoymous function, works good
using Distributed
using ClusterManagers
addprocs(2)
@everywhere begin
    ##
    N=2048
    Tpx=1
    ##
    function mapfunc(Tpx)
        test2->Tpx * test2
    end
    f=mapfunc(Tpx)
end
##
test2=[rand(ComplexF64,N), rand(ComplexF64,N)]
F=pmap(f,test2)
print("Completed")
##

julia debug.jl
Completed

With FFTW without anoymous function, works good too
using Distributed
using ClusterManagers
addprocs(2)
@everywhere begin
    using FFTW
    FFTW.set_num_threads(1)
    ##
    N=round(Int, 2048)
    ##
    Tpx=plan_fft(rand(ComplexF64,N))
    ##
    # function mapfunc(Tpx)
    #     test2->Tpx* test2
    # end
    f(test2)=Tpx* test2
end
##
test2=[rand(ComplexF64,N), rand(ComplexF64,N)]
F=pmap(f,test2)
print("Completed")
##

julia debug.jl
Completed

With FFTW and anoymous function, same error again
using Distributed
using ClusterManagers
addprocs(2)
@everywhere begin
    using FFTW
    FFTW.set_num_threads(1)
    ##
    N=round(Int, 2048)
    ##
    Tpx=plan_fft(rand(ComplexF64,N))
    ##
    function mapfunc(Tpx)
        test2->Tpx* test2
    end
    f=mapfunc(Tpx)
end
##
test2=[rand(ComplexF64,N), rand(ComplexF64,N)]
F=pmap(f,test2)
print("Completed")
##

julia debug.jl
      From worker 3:
      From worker 3:    Please submit a bug report with steps to reproduce this fault, and any error messages that follow (in their entirety). Thanks.
      From worker 2:
      From worker 2:    Please submit a bug report with steps to reproduce this fault, and any error messages that follow (in their entirety). Thanks.
      From worker 3:    Exception: EXCEPTION_ACCESS_VIOLATION at 0x54486564 -- .text at C:\Users\dell\.julia\artifacts\b7dd1809d0626eac3bf6f97ba8ccfbb6cc63c509\bin\libfftw3-3.dll (unknown line)
      From worker 3:    in expression starting at none:0
      From worker 3:    .text at C:\Users\dell\.julia\artifacts\b7dd1809d0626eac3bf6f97ba8ccfbb6cc63c509\bin\libfftw3-3.dll (unknown line)
      From worker 2:    Exception: EXCEPTION_ACCESS_VIOLATION at 0x54496564 -- .text at C:\Users\dell\.julia\artifacts\b7dd1809d0626eac3bf6f97ba8ccfbb6cc63c509\bin\libfftw3-3.dll (unknown line)
      From worker 2:    in expression starting at none:0
      From worker 2:    .text at C:\Users\dell\.julia\artifacts\b7dd1809d0626eac3bf6f97ba8ccfbb6cc63c509\bin\libfftw3-3.dll (unknown line)
      From worker 2:    unsafe_execute! at C:\Users\dell\.julia\packages\FFTW\SDUwi\src\fft.jl:466 [inlined]
      From worker 2:    * at C:\Users\dell\.julia\packages\FFTW\SDUwi\src\fft.jl:721 [inlined]
      From worker 2:    #3 at F:\Simulation\Trap simulation\2layers trap\BEM2Layers\ElectronTrapPost\DC_1D\th2\debug.jl:13
      From worker 2:    unknown function (ip:<PHONE_NUMBER>d93c66)
      From worker 3:    unsafe_execute! at C:\Users\dell\.julia\packages\FFTW\SDUwi\src\fft.jl:466 [inlined]
      From worker 3:    * at C:\Users\dell\.julia\packages\FFTW\SDUwi\src\fft.jl:721 [inlined]
      From worker 3:    #3 at F:\Simulation\Trap simulation\2layers trap\BEM2Layers\ElectronTrapPost\DC_1D\th2\debug.jl:13
      From worker 3:    unknown function (ip:<PHONE_NUMBER>d94566)
      From worker 3:    jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined]
      From worker 3:    do_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\builtins.c:713
      From worker 3:    #106 at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:278
      From worker 3:    run_work_thunk at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:63
      From worker 3:    macro expansion at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:278 [inlined]
      From worker 3:    #105 at .\task.jl:423
      From worker 3:    unknown function (ip:<PHONE_NUMBER>d861a3)
      From worker 2:    jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined]
      From worker 2:    do_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\builtins.c:713
      From worker 3:    jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined]
      From worker 3:    start_task at /cygdrive/c/buildbot/worker/package_win64/build/src\task.c:877
      From worker 3:    Allocations: 7966979 (Pool: 7963802; Big: 3177); GC: 10
      From worker 2:    #106 at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:278
      From worker 2:    run_work_thunk at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:63
      From worker 2:    macro expansion at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:278 [inlined]
      From worker 2:    #105 at .\task.jl:423
      From worker 2:    unknown function (ip:<PHONE_NUMBER>d858a3)
      From worker 2:    jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined]
      From worker 2:    start_task at /cygdrive/c/buildbot/worker/package_win64/build/src\task.c:877
      From worker 2:    Allocations: 7967560 (Pool: 7964384; Big: 3176); GC: 10
Worker 3 terminated.
ERROR: LoadError: Worker 2 terminated.ProcessExitedException
(2)
Stacktrace:
  [1] (::Base.var"#892#894")(x::Task)
    @ Base .\asyncmap.jl:177
  [2] foreach(f::Base.var"#892#894", itr::Vector{Any})
    @ Base .\abstractarray.jl:2694
  [3] maptwice(wrapped_f::Function, chnl::Channel{Any}, worker_tasks::Vector{Any}, c::Vector{Vector{ComplexF64}})
    @ Base .\asyncmap.jl:177
  [4] wrap_n_exec_twice
    @ .\asyncmap.jl:153 [inlined]
  [5] #async_usemap#877
    @ .\asyncmap.jl:103 [inlined]
  [6] #asyncmap#876
    @ .\asyncmap.jl:81 [inlined]
  [7] pmap(f::Function, p::WorkerPool, c::Vector{Vector{ComplexF64}}; distributed::Bool, batch_size::Int64, on_error::Nothing, retry_delays::Vector{Any}, retry_check::Nothing)
    @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\pmap.jl:126
  [8] pmap(f::Function, p::WorkerPool, c::Vector{Vector{ComplexF64}})
    @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\pmap.jl:101
  [9] pmap(f::Function, c::Vector{Vector{ComplexF64}}; kwargs::Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
    @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\pmap.jl:156
 [10] pmap(f::Function, c::Vector{Vector{ComplexF64}})
    @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\pmap.jl:156
 [11] top-level scope
    @ Unhandled Task ERROR: EOFError: read end of file
Stacktrace:
 [1] (::Base.var"#wait_locked#645")(s::Sockets.TCPSocket, buf::IOBuffer, nb::Int64)
   @ Base .\stream.jl:892
 [2] unsafe_read(s::Sockets.TCPSocket, p::Ptr{UInt8}, nb::UInt64)
   @ Base .\stream.jl:900
 [3] unsafe_read
   @ .\io.jl:724 [inlined]
 [4] unsafe_read(s::Sockets.TCPSocket, p::Base.RefValue{NTuple{4, Int64}}, n::Int64)
   @ Base .\io.jl:723
 [5] read!
   @ .\io.jl:725 [inlined]
 [6] deserialize_hdr_raw
   @ C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\messages.jl:167 [inlined]
 [7] message_handler_loop(r_stream::Sockets.TCPSocket, w_stream::Sockets.TCPSocket, incoming::Bool)
   @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:165
 [8] process_tcp_streams(r_stream::Sockets.TCPSocket, w_stream::Sockets.TCPSocket, incoming::Bool)
   @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:126
 [9] (::Distributed.var"#99#100"{Sockets.TCPSocket, Sockets.TCPSocket, Bool})()
   @ Distributed .\task.jl:423
Unhandled Task ERROR: EOFError: read end of file
Stacktrace:
 [1] (::Base.var"#wait_locked#645")(s::Sockets.TCPSocket, buf::IOBuffer, nb::Int64)
   @ Base .\stream.jl:892
 [2] unsafe_read(s::Sockets.TCPSocket, p::Ptr{UInt8}, nb::UInt64)
   @ Base .\stream.jl:900
 [3] unsafe_read
   @ .\io.jl:724 [inlined]
 [4] unsafe_read(s::Sockets.TCPSocket, p::Base.RefValue{NTuple{4, Int64}}, n::Int64)
   @ Base .\io.jl:723
 [5] read!
   @ .\io.jl:725 [inlined]
 [6] deserialize_hdr_raw
   @ C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\messages.jl:167 [inlined]
 [7] message_handler_loop(r_stream::Sockets.TCPSocket, w_stream::Sockets.TCPSocket, incoming::Bool)
   @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:165
 [8] process_tcp_streams(r_stream::Sockets.TCPSocket, w_stream::Sockets.TCPSocket, incoming::Bool)
   @ Distributed C:\Users\dell\AppData\Local\Programs\Julia-1.7.2\share\julia\stdlib\v1.7\Distributed\src\process_messages.jl:126
 [9] (::Distributed.var"#99#100"{Sockets.TCPSocket, Sockets.TCPSocket, Bool})()
   @ Distributed .\task.jl:423
F:\Simulation\Trap simulation\2layers trap\BEM2Layers\ElectronTrapPost\DC_1D\th2\debug.jl:19
in expression starting at F:\Simulation\Trap simulation\2layers trap\BEM2Layers\ElectronTrapPost\DC_1D\th2\debug.jl:19

For the record, this issue has been cross-posted at https://github.com/JuliaLang/julia/issues/45406

Sorry for that I just think it may relative to package Distributed and FFTW, so I posted it at two places

It's always a good practice to leave a references when you cross-post issues, to avoid multiple people wasting their times independently, instead of together in a single place.

(copying from Slack)
I think it's because you're communicating plans between workers, which you're not allowed to do (https://discourse.julialang.org/t/fft-plan-cant-be-sent-between-processes/877). The function f that you pass to pmap uses the Tpx defined on the root processor, not the workers, so you'd wanna fix that.
When I ran into this issue I just hacked up this to make my life easier, although it's not necessarily the best option if you want more control over your plans: https://github.com/gaurav-arya/WavePropagation.jl/blob/main/src/planned_fft.jl

I know your point, but
What makes these two fs below different to pmap?
@everywhere begin
    function mapfunc(Tpx)
        test2->Tpx* test2
    end
    f=mapfunc(Tpx)
end

@everywhere f(test2)=Tpx* test2

Seems like this package should add some checks to make sure the plan isn't a C_NULL pointer


Add openpty

Lemme know if anything needs to be fixed

So it's only failing on aarch64, because apparently some iotctl used in openpty() isn't implemented on it. Should I just add a #[cfg(not(target_arch="aarch64"))] to the test?

So it's only failing on aarch64, because apparently some iotctl used in openpty() isn't implemented on it. Should I just add a #[cfg(not(target_arch="aarch64"))] to the test?

I think our preference would be to work with libc upstream to fix aarch64.  Or are you saying that openpty isn't supported at all on aarch64?

I'm not sure; the test run is failing with test test_pty::test_openpty ... Unsupported ioctl: cmd=0x80045430 (which is TIOCGPTN for future reference), and returning Sys(ENOSYS), which means "unimplemented" according to the man pages. So it's either in libc using the wrong syscalls on this platform (I'm guessing pretty unlikely), the aarch64 kernel not implementing it (also unlikely), or the QEMU emulation of the system not implementing it (probably this one?). Do you have any ideas on how to figure out which versions of these things are being run?

I think you may have hit https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg04286.html.

Do you have any ideas on how to figure out which versions of these things are being run?
@posborne do you know offhand the version of qemu that's in your docker image?

@posborne do you know offhand the version of qemu that's in your docker image?

Unfortunately, no.  The base image I built stuff off of at the time was 15.10.

I think it's 0.10.50? I have no idea how Docker works, but I think I managed to pull the Docker image and start a container, and from inside a shell in that container:
docker pull posborne/rust-cross:android
# there was a lot of messing around between these two commands, but I think you only need these two
docker run --rm -it --name foo -p 5000:80 posborne/rust-cross:android /bin/sh

/android/sdk/tools/emulator-arm -qemu -version gave me
QEMU PC emulator version 0.10.50Android, Copyright (c) 2003-2008 Fabrice Bellard

Yeah, we can certainly bump.  I would really like to move the CI to something like https://github.com/japaric/trust

/cc @japaric

@posborne I could take a stab at getting trust CI up and running for nix.  I'd like to learn more about it for my own projects anyway.

@posborne I could take a stab at getting trust CI up and running for nix. I'd like to learn more about it for my own projects anyway.

@berkowski That would be awesome.

@cactorium Can you rebase this so we can give it a run through now that we're testing code on more platforms?

Can do!

@cactorium Sorry I didn't notice this the first time, but it looks like this should really be one commit, as you have a few smaller fixing commits. Can you squash this down into one? That would help me review it.
I'm also curious how this will end up interacting with #527. @cactorium Can you take a look at that issue, it kind of exploded into talking about how best to deal with the termios in nix? I don't want to merge this or that other one until we really know what we're getting ourselves into.
@berkowski If you have time can you take a look over this as well? This is probably of interest to you.

 Would you guys have any advice on cleaning up the commit history? I'll look at the other PR in a bit

Do a git reset upstream/master --hard or use origin if that's what you called the nix-rust/nix repo.
Then cherry-pick your 3 main commits like cherry-pick 397840a 0e3fcdb 75f44c9.

Then you can squash them with git rebase -i and force-push again.

@cactorium Can you please also add an entry to the CHANGELOG?

Can you add another test using a valid winsize argument? I can't easily figure out what that struct is, but it'd be nice to have verification that that works as well.

Well, that sets the size of the terminal window, and there's AFAIK really no nice way to test for it that doesn't involve ioctl

Alright, then let's skip it.

Soo all's good then?

Yes, but I'd like to wait til #590 is resolved before merging any new features.

:umbrella: The latest upstream changes (presumably ba5c837) made this pull request unmergeable. Please resolve the merge conflicts.

@cactorium Can you rebase this now that #556 just merged?

Done

Sorry for taking so long to push changes, it's been a busy few weeks

Didn't notice the build fail, it's fixed now

Looks good. Now just blocking on #590.

@cactorium Can you rebase this on HEAD now that our new testing framework has merged? This is RTM after it passes those tests.

Done

@asomers Can you check into why your FreeBSD buildbot isn't running?

Isn't that just disabled? It's got that DISABLE_TESTS=1 flag on all the recent builds I looked at: https://travis-ci.org/nix-rust/nix/builds

It's not run through Travis CI. We have a separate build server that runs tests on FreeBSD. @asomers runs it.

Buildbot saw the most recent change, yet did not decide to do a build.  I'll dig deeper after I get home tonight.

I couldn't find anything obviously wrong with the BuildBot server.  I've written to the mailing list for help.  but in the meantime, I suggest we don't hold up PRs waiting for it to complete.  Let's go ahead and merge anything compiles for i686-unknown-freebsd, which is done through Travis.

bors r+


Package missing from npm ?

Hey there.
The package seems to be missing from NPM : https://www.npmjs.com/package/pixi-particles
No error reported from the npm status page when writing this issue.
This is awkward as the npm search page list the page as being updated 1 month ago with version 4.3.1
Any reason for this ?

The page seems to be there for me?
On Tue, Jul 6, 2021, 6:11 AM Nicolas Chesné @.***>
wrote:

Hey there.
The package seems to be missing from NPM :
https://www.npmjs.com/package/pixi-particles
No error reported from the npm status page when writing this issue.
This is awkward as the npm search page list the page as being updated 1
month ago with version 4.3.1
Any reason for this ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pixijs/pixi-particles/issues/155, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN3N52FVHZ74UBL45SHZSDTWLJFTANCNFSM474ICZ5A
.


[Ubuntu 23.10] Microsoft.Data.SqlClient is not supported on this platform.

Describe the bug
After upgrade from Ubuntu 23.04 to 23.10, the package Microsoft.Data.SqlClient is not working anymore.
Exception message:
      System.PlatformNotSupportedException: Microsoft.Data.SqlClient is not supported on this platform.
Stack trace:
         at Microsoft.Data.SqlClient.SqlConnection..ctor(String connectionString)
         at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.CreateDbConnection()
         at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.get_DbConnection()
         at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenAsync(CancellationToken cancellationToken, Boolean errorsExpected)
         at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
         at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
         at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.ExecuteAsync(IEnumerable`1 commandBatches, IRelationalConnection connection, CancellationToken cancellationToken)
         at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(IList`1 entriesToSave, CancellationToken cancellationToken)
         at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChangesAsync(StateManager stateManager, Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
         at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func`4 operation, Func`4 verifySucceeded, CancellationToken cancellationToken)
         at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)
         at Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync(Boolean acceptAllChangesOnSuccess, CancellationToken cancellationToken)

To reproduce
Simple .net 7 console application, only with Microsoft.Data.SqlClient nuget package.
using Microsoft.Data.SqlClient;
new SqlConnection("");

Expected behavior
Not receiving the System.PlatformNotSupportedException exception.
Further technical details
Microsoft.Data.SqlClient version: 5.1.1 (tested 5.2.0-preview3.23201.1 with the same outcome)
dotnet --info
.NET SDK:
 Version:   7.0.112
 Commit:    c972157895

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  23.10
 OS Platform: Linux
 RID:         ubuntu.23.04-x64
 Base Path:   /usr/lib/dotnet/sdk/7.0.112/

Host:
  Version:      7.0.12
  Architecture: x64
  Commit:       4a824ef37c

.NET SDKs installed:
  6.0.123 [/usr/lib/dotnet/sdk]
  7.0.112 [/usr/lib/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.23 [/usr/lib/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 7.0.12 [/usr/lib/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.23 [/usr/lib/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.12 [/usr/lib/dotnet/shared/Microsoft.NETCore.App]

@olibos I just installed an Ubuntu Server 23.10

and added a simple application to connect to a server and open a connection and had no issues.

and here is the csproj file:

Did I miss anything on the steps to repro?

the only difference I see is the SDK version.

It was the SDK version! All my dot net packages were still on lunar instead of mantic.
If anyone had the same problem, I followed these steps: My Linux distribution provides .NET packages, and I want to use them

Remove the existing .NET packages from your distribution. You want to start over and ensure that you don't install them from the wrong repository.

sudo apt remove 'dotnet*' 'aspnet*' 'netstandard*'

Create /etc/apt/preferences, if it doesn't already exist.

touch /etc/apt/preferences

Open /etc/apt/preferences in an editor and add the following settings, which prevents packages that start with dotnet, aspnetcore, or netstandard from being sourced from the Microsoft repository:
```text
Package: dotnet* aspnet* netstandard*
Pin: origin "packages.microsoft.com"
Pin-Priority: -10

Reinstall .NET from the distribution's package feed. For more information, see Install .NET on Linux.


Add attribute to exclude druid spans from kafka exporter

Description
We don't want to export druid spans to kafka. Added attribute to handle this case. See link for more info.

Actually, we may be able to avoid any code change and use environment variables to set this. Are we using autoconfigure in the druid extension? If so you could just set the environment variable in the helm deployment.
OTEL_RESOURCE_ATTRIBUTES=exporter.trace.kafka=exclude

I've tested this approach locally, it works, so we don't need set attributes from the code


[Bug] FastForward breaks portal.azure.com

Body
If you try to launch portal.azure.com with FastForward enabled the page will not load.
Version
Manifest-v2
What browser(s) are you seeing the problem on?
Firefox browsers
What platform are you seeing the problem on?
Computer (Windows, Linux, MacOS)
Anything else?
No response

https://github.com/FastForwardTeam/FastForward/assets/12257112/dbd7a762-fc24-4ae8-bcd7-03808b28dca4

Can you reproduce this on chrome?


First cut, very low-quality draft for Dev Containers

I have written about 98% of what I know. Let's all contribute to strengthen this document. Thanks.

Wow, I had not noticed this. Thanks.
May I merge it?

By all means - I think it's good enough to publish. Please check that what I've written is actually true. though. Thanks.


Not mounting any target

Hi guys,
I do have Raspberry PI 4 8 GB with fully updated Ubuntu Mate 20.04.2 LTS.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.2 LTS
Release:        20.04
Codename:       focal

domy@domy-pi:~$ zramctl
domy@domy-pi:~$

domy@domy-pi:~$ systemctl status zram-config.service
● zram-config.service - zram-config
     Loaded: loaded (/etc/systemd/system/zram-config.service; enabled; vendor preset: enabled)
     Active: active (exited) since Sat 2021-05-29 20:32:33 CEST; 10min ago
       Docs: https://github.com/ecdye/zram-config/blob/main/README.md
    Process: 1918 ExecStart=/usr/local/sbin/zram-config start (code=exited, status=0/SUCCESS)
   Main PID: 1918 (code=exited, status=0/SUCCESS)

May 29 20:32:33 domy-pi systemd[1]: Started zram-config.
May 29 20:32:33 domy-pi zram-config[1923]: zram-config start 2021-05-29-20:32:33
May 29 20:32:34 domy-pi zram-config[1961]: zramctl: /dev/zram0: failed to reset: Device or resource busy

domy@domy-pi:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0         7:0    0 127.1M  1 loop /snap/chromium/1595
loop1         7:1    0  48.9M  1 loop /snap/core18/1949
loop2         7:2    0 145.4M  1 loop /snap/gnome-3-28-1804/147
loop3         7:3    0  65.1M  1 loop /snap/gtk-common-themes/1515
loop4         7:4    0  48.9M  1 loop /snap/core18/2068
loop5         7:5    0  59.6M  1 loop /snap/lxd/20330
loop6         7:6    0  61.6M  1 loop /snap/lxd/19040
loop7         7:7    0  27.9M  1 loop /snap/snapd/11843
loop8         7:8    0    27M  1 loop /snap/snapd/10709
loop9         7:9    0    16K  1 loop /snap/software-boutique/56
loop10        7:10   0  15.2M  1 loop /snap/ubuntu-mate-welcome/627
mmcblk0     179:0    0 119.1G  0 disk
|-mmcblk0p1 179:1    0   256M  0 part /boot/firmware
`-mmcblk0p2 179:2    0 118.9G  0 part /

domy@domy-pi:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            3.7G     0  3.7G   0% /dev
tmpfs           782M   30M  752M   4% /run
/dev/mmcblk0p2  117G  6.4G  106G   6% /
tmpfs           3.9G     0  3.9G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/loop0      128M  128M     0 100% /snap/chromium/1595
/dev/loop1       49M   49M     0 100% /snap/core18/1949
/dev/loop2      146M  146M     0 100% /snap/gnome-3-28-1804/147
/dev/loop3       66M   66M     0 100% /snap/gtk-common-themes/1515
/dev/loop4       49M   49M     0 100% /snap/core18/2068
/dev/loop9      128K  128K     0 100% /snap/software-boutique/56
/dev/loop6       62M   62M     0 100% /snap/lxd/19040
/dev/loop7       28M   28M     0 100% /snap/snapd/11843
/dev/loop5       60M   60M     0 100% /snap/lxd/20330
/dev/loop8       27M   27M     0 100% /snap/snapd/10709
/dev/loop10      16M   16M     0 100% /snap/ubuntu-mate-welcome/627
/dev/mmcblk0p1  253M  128M  125M  51% /boot/firmware
tmpfs           782M   16K  782M   1% /run/user/1000

domy@domy-pi:~$ swapon -s
domy@domy-pi:~$

Log file is attached, a little bit long for this. zram-config.log
Configuration file /etc/ztab has not been changed yet.
Can someone please explain me how to get this thing working? And is it possible to include /tmp directory with this tool or I do need to use /etc/fstab?
Thank you in advance and I wish you all the best!

Alright, I am not surprised that you have had issues with this. First off, RPi 4 8GB does not always work correctly with zram right now. This is due to a Linux Kernel issue that is ongoing. While not a part of this project, this post on the openHAB forum has some details. For the moment there are no real good ways to enable zram on a RPi 4 8GB it may be possible but I won't try and support it as the methods used would be very hacky.
Second, it should not be necessary to put the /tmp directory on zram please read the Performance section of the README to get more details.
I will make sure to make a note in the README so that people know that the RPi 8GB is not currently working with zram due to this issue.

Alright, I am not surprised that you have had issues with this. First off, RPi 4 8GB does not always work correctly with zram right now. This is due to a Linux Kernel issue that is ongoing. While not a part of this project, this post on the openHAB forum has some details. For the moment there are no real good ways to enable zram on a RPi 4 8GB it may be possible but I won't try and support it as the methods used would be very hacky.

Aaahh, I see, I didn't even think about that, lol.

Second, it should not be necessary to put the /tmp directory on zram please read the Performance section of the README to get more details.

I saw this section but my /tmp is not mounted in RAM but in the root.
domy@domy-pi:~$ df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p2  117G  6.4G  106G   6% /
domy@domy-pi:~$

I will make sure to make a note in the README so that people know that the RPi 8GB is not currently working with zram due to this issue.

Thanks for your time!
Anyhow, I do have around 5 MB writes per day, it's not that urgent, I'll wait for a fix.

Ahh, well then you would likely be better suited with using /etc/fstab to mount your /tmp directory on ram rather than zram.

Actually, I've found that tmp.mount is not enabled by default, we need to copy *.mount file and enable it.
sudo cp -v /usr/share/systemd/tmp.mount /etc/systemd/system/
sudo systemctl enable tmp.mount

So, I will close this issue, there is nothing we can do right now.
Best regards!


feat: add CoeFun Instance for PiLp

This instance should make things easier to read and avoid defeq abuse. That is, given a term x : PiLp p α (or for instance x : EuclideanSpace 𝕜 n), we can ensure that Lean interprets this is a function by writing ⇑x. This shouldn't be a FunLike instance because then the coercion ⇑ would get unfolded to FunLike.coe instead of WithLp.equiv.

I suggested this to Jon, so I won't merge it myself.
maintainer merge

This shouldn't be a FunLike instance because then the coercion ⇑ would get unfolded to FunLike.coe instead of WithLp.equiv.

Can you put this comment in the source code for future readers?

@eric-wieser: I included the suggested comment. Thanks!

@j-loreaux : I added the suggested quotation marks.

Great. When you complete the changes, as you just did, you should mark the PR awaiting-review again.

@JonBannon it seems the work from your other PR infected this. Can you remove the bit about Matrix.toEuclideanLin?


[FLINK-34484][state] Split 'state.backend.local-recovery' into two options for checkpointing and recovery

What is the purpose of the change
This pull request split 'state.backend.local-recovery' into two options: "execution.checkpointing.local-backup.enabled" and "execution.state-recovery.from-local".  The "execution.checkpointing.local-backup.enabled" indicates whether to do checkpoint on local disk; while "execution.state-recovery.from-local" option specifies whether to recover from local.
Brief change log

Move LOCAL_RECOVERY config from CheckpointingOptions to StateRecoveryOptions
Split 'state.backend.local-recovery' into two options for checkpointing and recovery
Add UT/IT tests to verify localBackup and localRecovery configs

Verifying this change
The added tests and existing tests can cover this change, which can be verified as follows:

TaskExecutorLocalStateStoresManagerTest#testStateStoreDirectoryCreateAndDeleteWithLocalRecoveryEnabled and testStateStoreDirectoryCreateAndDeleteWithLocalBackupEnabled   (added tests)
TaskLocalStateStoreImplTest#TaskLocalStateStoreImplTest  (added tests)
LocalRecoveryITCase & TaskExecutorLocalStateStoresManagerTest &  TaskLocalStateStoreImplTest (existing tests )

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): yes
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: yes
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? docs

FYI, https://github.com/apache/flink/pull/24470 has been merged, could you please help to rebase this PR?

The pr has been rebased on master branch.


Update CONTRIBUTORS.csv

Current behavior

Proposed changes

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] There are no Merge commits in this Pull Request. Ockam repo maintains a linear commit history. We merge Pull Requests by rebasing them onto the develop branch. Rebasing to the latest develop branch and force pushing to your Pull Request branch is okay.
[x] I have read and accept the Ockam Community Code of Conduct.
[x] I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

@sayyedarib W'll merge this shortly.
Thank you for accepting the CLA and taking time to contribute!!
Welcome to the Ockam Community 🥳
If you have questions, as you explore, join us on the contributors discord channel https://discord.gg/bewvnm6zqS

@metaclips please enqueue this when you get a chance.


Head tracks incorrectly during reprojection

Description
In my setup, reprojection during lag spikes extremely overcompensates head movement in every program, it feels like it overcompensates the movement of my head by around 4 times, creating a very nauseating effect which doesn't necessarily last a very long time but is regardless very stressful to experience.
General Troubleshooting

[X] I carefully followed the instructions in the README and successfully completed the setup wizard
[X] I read the ALVR Wikis here and here

Environment
Hardware
CPU: AMD Ryzen 5 4600H
GPU: AMD Radeon(TM) RX 5600M
Audio: AMD/Realtek High Definition Audio
Installation
ALVR Version: v18.2.3
SteamVR Version: beta 1.23.6
Install Type:

[X] Packaged (exe, deb, rpm, etc)
[ ] Portable (zip)
[ ] Source

OS Name and Version: Windows 11 (21H2; 22000.795)

there's no field for it, but I use the SideQuest ALVR client on a Quest 2.

Can you please provide a screenshot of the ALVR server status page?

I think i know what you mean, and this is very likely to be fixed in v19. Cant promise though, i myself wait to use it (using ALXR)


Make new JVM APIs internal for 6.7

So we can follow up (#14467) before making them public.
After this merged on release, I'll directly revert it for 6.8 and do the binary compatibility check+release nightly dance

@bot-gradle QF

Sorry I don't understand what you said, please type @bot-gradle help to get help.

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.


Have you seen these related projects?

https://github.com/amueller/patsylearn
by @mueller
https://github.com/paulgb/sklearn-pandas
Maybe good ideas or best to combine forces?

Yes, I'm aware of both.
This pkg intends to cover R's model.frame like functionality and intends to cover other packages which has sklearn like API ( xgboost is under work in #44 )
I'm interested in patsylearn, but not look into its detail yet.
sklearn-pandas has smaller set of functionality and doesn't cover my needs.


segment fault on k4abt_tracker_create

Describe the bug
segment fault when launch the application by IDE(Qt creator), but work fine if simply launch it by the executable file
*
* the issue (segment fault) happened after execute k4abt_tracker_create (found on using debugging tool)
To Reproduce

download and install Qt creator 5.13.0

installation detail

download and unzip the test project (it's about 480MB, because the whole SDKs is in it)
open the project by double click the file bodytrackingTest.pro

detail when first open this project

do as the figure
do as the figure
use the debug tool
it should be like this after execute line #65

which is after execute k4abt_tracker_create

Expected behavior
launch the application by IDE without crush
Logs
none
Screenshots
check Reproduce steps
Desktop (please complete the following information):

OS with Version: Windows 1809
SDK Version:  0.9.1
Firmware version:  1.1.0

Additional context
none

Just a quick guess would be that the IDE starts the application in another folder (not the Debug folder where you placed the dll files) so that the IDE can't find the model and/or dll files.
Maybe you can check what your current working directory is when starting the application via IDE.
C++ 17 has a simple way to do it I think:
https://en.cppreference.com/w/cpp/filesystem/current_path

Just a quick guess would be that the IDE starts the application in another folder (not the Debug folder where you placed the dll files) so that the application can't find the model and/or dll files.
Maybe you can check what your current working directory is when starting the application via IDE.
C++ 17 has a simple way to do it I think:
https://en.cppreference.com/w/cpp/filesystem/current_path

nope, not likely, because

if i just use the sensor SDK, then every thing work fine
mark the code which execute k4abt_tracker_create, and then it can launch by IDE without crush

Hi @alfredyu0911 , the guess from @RoseFlunder might be right. Because:

The sensor SDK is totally separate from the body tracking SDK. So running sensor SDK correctly doesn't mean anything to the body tracking SDK.
All the other dll dependencies are delay loaded in Windows. So if you comment out the body tracking SDK code, it won't hit any dependency issue.

Start from the 0.9.2 version, the SDK will dynamically check the dependency existence. If they are not existed at the expected folder, it will fail to create the tracker and log the error instead of crashing. Could you give it a try to see whether it is the case?

Hi @alfredyu0911 , the guess from @RoseFlunder might be right. Because:

The sensor SDK is totally separate from the body tracking SDK. So running sensor SDK correctly doesn't mean anything to the body tracking SDK.
All the other dll dependencies are delay loaded in Windows. So if you comment out the body tracking SDK code, it won't hit any dependency issue.

Start from the 0.9.2 version, the SDK will dynamically check the dependency existence. If they are not existed at the expected folder, it will fail to create the tracker and log the error instead of crashing. Could you give it a try to see whether it is the case?

Hi @yijiew, thank you and @RoseFlunder :
I tried to change the working directory, and it did work, sorry that i didn't try it in the first place.
Thank you for your support.
FYI, the file dnn_model.onnx isn't checked dynamically (version  0.9.2), should i close this issue anyway?

@alfredyu0911 I am glad it solves your problem :D When you say "the file dnn_model.onnx isn't checked dynamically", do you mean if you don't have the dnn_model.onnx file at the correct location, it will still crash instead of just return error when you create the tracker?

@alfredyu0911 I am glad it solves your problem :D When you say "the file dnn_model.onnx isn't checked dynamically", do you mean if you don't have the dnn_model.onnx file at the correct location, it will still crash instead of just return error when you create the tracker?

@yijiew it return error when create the tracker,
sorry, i read again and just realize it's not a issue, sorry to bother.
thank you.

Thanks @alfredyu0911 !


Regex to exclude partial file compilation

Hi,
Just trying out Atom for the first time, and found your useful plugin. I know others have mentioned this, but using comments for partials is kind of burdensome.
You mentioned you were open to other approaches. The sublime save on build package allows a user regex string that it then tests file names against to determine if they should be excluded.
My standard, and I think it's pretty common, is to prefix partial files with an underscore, like _partial.scss. The following regex would cover that: /^_.*\.scss/g.
So, allowing a custom regex filter would probably solve this for a lot of people. It seems like a better solution, but I know nothing about developing for atom. If it's not possible, or not popular, that's fine too!

Hey! Have a look at this issue. I think, it's the same problem, but I must say, that your idea is smarter than my current solution!
I will let this request opened and I will see how to include this feature!

Thanks for looking into this!
It is the same issue, and I think taking underscores into account would be fine, a regex for it is probably overkill.
According to the sass documentation, that's the way you're supposed to do declare partials, so it'd work pretty well for this tool:
http://sass-lang.com/guide#topic-4

In regard to Partials, you are right. But your idea is great, if there is a need for more features which are based on filenames. At the moment, there is no reason to integrate it, but who knows what's coming next ;)

Yeah, that's a great point, a custom regex would be super flexible. I think the sublime plugin did that because it supported 'save on build' for any build you were doing. To make it easier, you could have two options. A checkbox for the traditional partial, and then a second field allowing a custom regex.


Set engagement end date when auto_create_context with import/reimport API

Hi,
I'm facing the need to customize the end date of an engagement created with auto_create_context=true when using the import/reimport API endpoints.
It would be very convenient to be able to pass an additional engagement_end_date parameter for this.
"curl --location --request POST <...>/api/v2/reimport-scan
            ...
            --form 'engagement_name=xxx'
            --form 'engagement_end_date=2022-12-31'
            --form 'auto_create_context=true'
            ...

In the codebase. the created engagement's end date is mandatory and a hardcoded value of 365 (one year) is used...
So it should make sense to have a parameter for this one ?
https://github.com/DefectDojo/django-DefectDojo/blob/1bb23ddc071bfa947c9e9e840ea428e6cbfb2984/dojo/importers/reimporter/utils.py#L215
It might be a hassle to do date validation (eg. not before start date), so passing the number of days in a engagement_period_days parameter is fine too.

@ctrung I implemented this in #7181 as we required this for having engagements for >2 years. Does this fix the issue for you?

Thx @italvi for the PR and sorry for the late reply.
I just checked it on the 2.18.0 version and works like as expected, both with or without a date.


Add Fade-In background color option

When the modal is placed in a nested view, rather than a top-level view, it only takes up the space of the nested view. Also, padding styles of parent views are affecting the effect. I have not tried to see if this can be fixed yet, but changing the background color of the effect is one approach. On following example, the action sheet is placed in a Dropbox component, and several Dropboxes within a view.  See the screenshots for the described effect.
With default black background:

With overridden background:

@eyaleizenberg any comment on this?


jd-gui: 0.3.5 -> 1.4.0

Motivation for this change
Bump jd-gui to 1.4.0, which is now available on GitHub, is GPL3, and is buildable from source.
The project uses Gradle, so an incantation was lifted from the mucommander derivation to add all Maven dependencies to a fixed-output derivation.
Rather than rewrite the build script to apply the local dependency repo, I use Gradle's --init-script option for a more robust approach.
cc maintainer: @thoughtpolice
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: jd-gui
Partial log (click to expand)
Cannot nix-instantiate `jd-gui' because:
error: callPackage_i686 not supported on system 'aarch64-linux'

Success on x86_64-linux (full log)
Attempted: jd-gui
Partial log (click to expand)
BUILD SUCCESSFUL

Total time: 14.433 secs
Stopped 1 compiler daemon(s).
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/4vb6i65w7xqx4j7lwygw3vqi7pydj95i-jd-gui-1.4.0
patching script interpreter paths in /nix/store/4vb6i65w7xqx4j7lwygw3vqi7pydj95i-jd-gui-1.4.0
checking for references to /build in /nix/store/4vb6i65w7xqx4j7lwygw3vqi7pydj95i-jd-gui-1.4.0...
/nix/store/4vb6i65w7xqx4j7lwygw3vqi7pydj95i-jd-gui-1.4.0

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: jd-gui
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: jd-gui
Partial log (click to expand)
BUILD SUCCESSFUL

Total time: 17.719 secs
Stopped 1 compiler daemon(s).
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/hpsbwxyrs5fvzvjvbi83nh9pmbg0m48j-jd-gui-1.4.0
patching script interpreter paths in /nix/store/hpsbwxyrs5fvzvjvbi83nh9pmbg0m48j-jd-gui-1.4.0
checking for references to /build in /nix/store/hpsbwxyrs5fvzvjvbi83nh9pmbg0m48j-jd-gui-1.4.0...
/nix/store/hpsbwxyrs5fvzvjvbi83nh9pmbg0m48j-jd-gui-1.4.0


PostgreIntervalValueHandler.bindParameter can better throw DBCException

Description
PostgreIntervalValueHandler.bindParameter throws SQLException. The other similar methods throw DBCException. The following methods are examples:
PostgreDateTimeValueHandler.bindValueObject()
PostgreContentJSON.bindParameter()
DBeaver Version
dev
Operating System
No response
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

We're open for contributions.

There is no update on this issue, nor any PR from the reported, so I'm closing it as it's a stale now.


How to import svg and fonts?

Hi everyone! This isn't a bug. But I'm a bit confused.
This is my project structure:

Font issue:
When I import a font with url in my sass file an error is shown in the build:
Module not found: Error: Can't resolve '../../fonts/BebasNeueBook.woff2'
Then in a .scss file (styles/base/reset.scss):
@font-face {
  font-family: 'BebasNeueBook';
  src: url('../../fonts/BebasNeueBook.woff2') format('woff2');
}

SVG issue:
I use the svg as follow:
<svg class="icon-menu">
    <use xlink:href="/icons/icons.svg#icon-menu"></use>
</svg>

But I can show this error in the dev tools console:
vue.esm.js?65d7:5819 GET http://localhost:9080/icons/icons.svg

Tell me about your development environment.

Node version: 8.0.0
NPM version: 5.3.0
vue-cli version: 2.8.2
Operating System: MacOS 10.12.6

Thanks for any help you can give me!
Regards!

i think the path to fonts is wrong. im not sure. it should be
@font-face {   font-family: 'BebasNeueBook';   src: url('../fonts/BebasNeueBook.woff2') format('woff2'); }

@algil
For the font issue, you could try using the webpack alias with something like url(~@/assets/fonts/BebasNeueBook.woff2), where the @ provides you a reference to the src/ directory.
As for the SVG issue, you will not be able to use the xlink:href approach as vue-loader won't treat that as a require statement. You could either alt for using a <img> tag, or place your icons within the static/ directory and access from there.

For future Googlers, that's what worked for me.

If use quote it doesn't work
Fonts under /src/assets/fonts
Other formats were available (as SVG, for example), but when applied the font was ignored – so check every file format

@font-face {
    font-family: 'fontName';
    src:
<EMAIL_ADDRESS>format('woff2'),
<EMAIL_ADDRESS>format('woff'),
<EMAIL_ADDRESS>format('truetype');
    font-weight: normal;
    font-style: normal;
}

@hmaesta
Removing the SVG source url is what did the trick for me. Cheers!

It's very very very bad news about SVG sprites. symbolic sprites the most convenient way for dev. I can't leave it like this

<EMAIL_ADDRESS>Thats why you can't import svg files as fonts, only as images.

So, for svg rule you should just change fonts -> img.

/*!
 * Font Awesome Pro 5.9.0 by @fontawesome - https://fontawesome.com
 * License - https://fontawesome.com/license (Commercial License)
 */
@font-face{
    font-family:"Font Awesome 5 Pro";
    font-style:normal;
    font-weight:400;
    font-display:auto;
    src:url(~@/assets/fonts/fa-regular-400.eot);
    src:url(~@/assets/fonts/fa-regular-400.eot?#iefix) format("embedded-opentype"),
<EMAIL_ADDRESS>format("woff2"),
<EMAIL_ADDRESS>format("woff"),
<EMAIL_ADDRESS>format("truetype"),
<EMAIL_ADDRESS>format("svg");
}
.far{
    font-family:"Font Awesome 5 Pro";
    font-weight:400;
}

Fonts under assets/fonts or assets/img
That's what you gonna get in output:
@font-face {
	font-family: Font Awesome\ 5 Pro;
	font-style: normal;
	font-weight: 400;
	font-display: auto;
	src: url(../fonts/fa-regular-400.8367c7f8.eot);
	src: url(../fonts/fa-regular-400.8367c7f8.eot?#iefix) format("embedded-opentype"),
	url(../fonts/fa-regular-400.bc70ae3f.woff2) format("woff2"),
	url(../fonts/fa-regular-400.9d318325.woff) format("woff"),
	url(../fonts/fa-regular-400.caf8defa.ttf) format("truetype"),
	url(../img/fa-regular-400.8e0462b9.svg#fontawesome) format("svg")
}

.far {
	font-family: Font Awesome\ 5 Pro;
	font-weight: 400
}


properly handle optional _json property

fixes #196

@daffl @ekryski does this look good to you guys?

@nyaaao yup this is great! Thanks! 😄

v0.7.7 published with the fix. Thanks again @nyaaao!


Format Documentation Token Values

Is your feature request related to a problem? Please describe.
Currently when applying documenting tokens using 'Value', the plugin applies the JSON in-line.
Describe the solution you'd like:

Option to automatically format the JSON (line-wrapping etc)
Option to display the value in YAML format (more readable) (e.g. fontSize: {fontSize.displayXL})

Screenshots:

Key information:
This is also applicable when documenting Composition and Border token types.

I'd say we should add something to Settings that lets users configure how to treat complex tokens in Documentation, and possibly have a section about Documentation values. Users have mentioned they'd like some control over the output of values.
Documentation tokens
- Composition tokens: [Raw JSON (current), JSON with line wrapping, YAML]

There'd be more options for e.g. how colors are treated, in the future.

Migrated to Featurebase

Migrated to Featurebase


WIP - Simple HTML-enabling fix

This is not the be-all-end-all solution. We need to progress (longer term) the templates idea from SendGrid.

extended models to add HTML field
updated view models affected by HTML
updated email confirmation to set HTML
updated service to push HTML out with email

Fixes 359

@dpaquette and @tonysurma: End-to-end confirmed:

Message is queued
HTML is set correctly (although the message should be prettied up)
Message arrives as HTML and is clickable
Controller picks up and processes confirmation as sent to user

This looks good. As @MisterJames mentioned, we do need to refine the actual messages we are sending but at least this gives us the structure we need to send both Html and Plain Text emails.
:shipit:

Excellent, thanks


Mohammad-create-Milestone-Component

As a trainee, I want to see whhich Module Currently I am in and see the deadline for the Module.
As user I want to see how many day I have untill deadline

I create branch

Done


xvm: open module failed undefined symbol: sqrt

Brief of the issue
deploy go wasm contract failed, found undefined symbol: sqrt in log
Your environment
OS: ubuntu 18.04
GO: 1.12.6
Repo steps
Describe how to reproduce this issue.
Expected behaviours
Describe what you expected to happen.
What actually happened
Describe what actually happened. Include the full traceback if there was an exception.
Additional information
If possible, include a minimal, complete, and verifiable example to help us identify the issue. This also helps check that the issue is not with your own code.

close as fixed #139


Webhook is not work on collaborations

Gogs version (or commit ref): <IP_ADDRESS>3
Git version:  2.1.4
Operating system: debian
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist (usually found in log/gogs.log):
No errors.

Webhook is only work on repositories in real time, but dont work on collaborations. If we restart the gogs daemon, then the collaboration webhook is work at start procedure. So we need always restart the gogs daemon for collaboration webhook is fired.

Hi,
Define "collaboration webhook"?

Sorry! Collaboration mean organization.

Ah.. thanks for clarifying. But why can't you reproduce on demo site?

I cant reproduce on demo site.


Do you need to fit mapie on a calibrated data set which is different from the training set?

Is your documentation request related to a problem? Please describe.
I recently read this Medium post: https://towardsdatascience.com/mapie-explained-exactly-how-you-wished-someone-explained-to-you-78fb8ce81ff3
The author fits mapie on an extra dataset which was splitted from the training data, I guess in order to have independent confidence intervals. The tutorials in the documentation on the other hand fit Mapie directly on the training set.
Which is the right thing to do? Is Mapie doing this split for calibrated data in the background? How much data is used for the calibrated dataset? Would be nice to know since I have less samples to train on if thats the case
Best regards

The only thing referring to this in the docs, which I found is this graphic of yours, which creates even more questions, because I can not really figure out what the right thing to do is. Splitting my data into three sets like training, calibrated and test or just going with the old approach for estimators.
It would also be nice to know if there are any hints how big the calibrated dataset has to be, since I subtract it from my samples in the training set. Maybe 10% of the original data? Or sample size depenendent like 10000+ is enough maybe?


Update the game over message

Update on the game over message feature

please help me... how do i commit suggestion


New port: (Savant Ascent)

New Port for { Savant Ascent }
Game Information

Title: { Savant Ascent }
URL: { https://store.steampowered.com/app/259530/Savant__Ascent/ }

Submission Requirements
CFW Tests
Ensure your game has been tested on all major CFWs:

[X] AmberELEC
[X] ArkOS
[X] JELOS

Resolution Tests
Test all major resolutions:

[X] 480x320
[X] 640x480
[X] 720x720 (RGB30)
[X] Higher resolutions (e.g., 1280x720)

File Structure

Your port should have the following structure:

portname/

port.json
README.md
screenshot.jpg
cover.jpg
Port Name.sh
portname/

Additional Resources
For an in-depth guide on creating a pull request, refer to: PortMaster Game Packaging Guide

Fixed .sh file
Different screenshot to show gameplay

Thanks for the feedback guys :)


uploaded MiEx_helper addon

adds basic addon for prepping and setting up the MiEx .usd worlds in blender

adds auto animate textures (basic implementation, no animation offset etc.)
resize of the world to a more reasonable size
note: addon will only add an operator and nothing more -> execution by selecting the world empty, looking for the miex.prep operator in the searchbar and execute it

added information about this addon to the readme file

Thanks for you reply!
I made the changes that you asked for and moved the corresponding file to the extras/Blender/BlenderAddon/ directory. A new README and LICENSE file for the Blender addon also has been created. Updating the addon to your proposed idea should also be no problem when the foundations of the .json file are established. Might just take a little while for that.


feat(rulesets): add event action field

I was noticing an issue with my first iteration on this. In order to execute a step, it must pass the purge process and the skip process. In order to respect scoped events (pull_request:opened for example), I needed to change the build.Event value to that here. This is not ideal. Not only does it require splitting logic all over to respect various event gatekeeping, it also changes the environment variable VELA_BUILD_EVENT, which is used by many end users.
To get around this, I decided to add a new field, EventAction (open to new name suggestions). This lays the ground work for future event action handling (such as PR review events). It also makes handling comment event scoping seamless, which I've also added to this PR.
The obvious drawback to this method is two fold:

another column in the database
that column will be a duplicate of the event column for push, deploy, and tag events.

Another strategy here would be to change EventAction to Action, and handle the events without actions as nil. I chose the more verbose option for now but am more than willing to pursue that route instead if we wanted.

I decided to go with storing just Action to avoid redundancy in columns and parity with what GitHub gives us as the action


signal: 11, SIGSEGV: invalid memory reference

The following code compiles and cargo test foo1 succeeds, but cargo test fails with:
process didn't exit successfully: /home/foo/target/debug/deps/opencl3-594da37a386292da (signal: 11, SIGSEGV: invalid memory reference)
Cargo.toml
[package]
name = "opencl3"
version = "0.1.0"
edition = "2021"
[dependencies]
opencl3 = "0.8.1"

main.rs
use opencl3::device::{get_all_devices, Device, CL_DEVICE_TYPE_GPU};
use opencl3::Result;

fn main() {
    println!("Hello, world!");
}

fn bar() -> Result<Device> {
    let device_id = *get_all_devices(CL_DEVICE_TYPE_GPU)?
        .first()
        .expect("no GPU found in platform");
    Ok(Device::new(device_id))
}

#[cfg(test)]
mod tests {
    use crate::bar;

    #[test]
    fn foo1() {
        bar().expect("the unexpected");
    }

    #[test]
    fn foo2() {
        bar().expect("the unexpected");
    }
}

Do you also get the fault when running the tests in single-threaded mode?
I.e.:
cargo test -- --test-threads=1


Automatically Validate and/or Bump Version

Is your proposal related to a problem?
There is a tool version listed in both docker-compose.yml and tool_controller.py. When you release a version (which automatically gets Dockerized, thanks to our nifty ci.yml workflow), there is nothing to make sure that the version named in the tag matches the version listed in these files (it should!)
Describe the solution you'd like
If it is possible, it would be nice if the tag workflow could check that the version mentioned in the tag actually matches the version listed in these files.
It would also be nice if the tag workflow could automatically bump the version in these files after each release. E.g., after you release version 1.2.3, it automatically commits new versions of docker-compose.yml and tool_controller.py with 1.2.4 as the new version number. I think bumpversion does something like this.

While I like the general idea for an internal project, we need to be mindful about introducing additional complexity and potentially unexpected automatic behavior - especially automatic commits - to the GH repositories of the example tools.
Also, there is no way to know that the next release version after 1.2.3 will be 1.2.4. It could as well be 1.3.0 or 2.0.0. How would you address this?


"Switch To Release Version" error when no release version available

Testing #138068

/duplicate
https://github.com/microsoft/vscode/issues/138231


Fix or remove bowlby-hosted build artifact links

I am no longer in the mastercard github organisation, so it might be the case that the API token that is currently being used to make build artifacts (those linked from https://mastercard.github.io/flow/ and from the summary of each action run) browsable will stop working soon.
If the links do break, we should do either of:

Have someone still in mastercard provision a new bowlby instance and fix all the links to point to that
Remove the links when they eventually break

I can run someone through what I did to get the current instance going, but the second option is a completely valid choice too.

I think we can try setting up an instance of bowlby, if that doesn't work out to be maintainable, we can go with the second option. I'll get back to you at the earliest to get this setup.


Retrieving status of non-existing task returns internal server error "cannot cast id: Attribute error"

It would be nice if this would return a 404 not found instead.

@Jascha-N I looked into this issue, but the main issue is that the underlying task scheduling library I use (bokchoy) has a bug.  See this issue I created to the project: https://github.com/thoas/bokchoy/issues/31
For the time being, I have to fork this project and make my own fix (given that the author of this project doesn't seem to be very active on this project).  Anyway, it is at least fixed by now.  If the task doesn't exist, it returns 404.  See this API document for more information.