Translate README to zh-CN (simplified Chinese)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: two sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for taking the time to contribute this localization pull request. However, we are not able to accept contributions to this historical reference repository at this time.


"PerpetualVL2019" channel doesn't seem to work for retail, only "current" does

I wasn't able to get "PerpetualVL2019" working as the channel for 2019 proplus or standard retail; I had to use "current". Is this documentation inaccurate?

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

ID: 1f5cfe20-90ad-3f7e-8ae8-ff99bd1e1b55
Version Independent ID: 97b2760a-50a2-f7c0-32ab-20b0420838d1
Content: Update Office 2019 (for IT Pros)
Content Source: DeployOffice/office2019/update.md
Product: office-perpetual-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@wmassingham -- PerpetualVL2019 is the correct channel for volume licensed versions of Office 2019. which this article is focused on. PerpetualVL2019 won't work for retail versions of Office 2019. We'll try to make that clearer in this article. Thanks for the question/feedback.


Remove vulnerabilities & avoid the CORS issue by replacing fetch with requestUrl

Hi, thank you for making this awesome plugin!
Remove vulnerabilities
npm install told me there are 2 high severity vulnerabilities.
I found obsidian is outdated (older than 1.0.0), so I updated it. Then, the vulnerabilities have gone.
Avoid the CORS issue
Sometimes, pasting a URL causes the following error:
Access to fetch at 'https://genius.com/25251' from origin 'app://obsidian.md' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

So I replaced fetch() in scrapper.ts with Obsidian API's requestUrl.

"Similar to fetch(), request a URL using HTTP/HTTPS, without any CORS restrictions."

After this change, the error message's gone.

Thanks for the PR! Sorry for the delay but it looks like this has been superseded by #91 so your fixes are in - in spirit!


[SPARK-7549] Support aggregating over nested fields.Add sum, avg, min…

…, max and count.

Can one of the admins verify this patch?

Thanks for working on this.  I'd propose that we close this issue until the design questions on the JIRA have been answered.

Can one of the admins verify this patch?


Bulk metadata update for Time Series Resource

The TimeSeriesMetaData class needs to extend the base class update() to support resource specific metadata update. This update()  function is used by REST api.

@pkdash is this still an issue given composite resource work.

This issue is old, and I don't know whether it is still relevant. I'm going to close it as stale.


Question: Any idea how to clone the Phone app of Android

This repository is nice, but the full implementation of all things in a during call UI is probably much larger.
Do you know perhaps how to clone correctly the official Phone app, or at least just the part of during the call?
I've tried here:
https://android.googlesource.com/platform/packages/apps/Dialer
But it is so messy and I don't get what to do with the folders. The IDE failed to just import it all.
However, I've found 2 repositories that have it working, though in a bit old version (Android N) of the Phone app:

https://github.com/geniusgithub/AndroidDialer/
https://github.com/xjpmauricio/dialer-nougat-release

How did they do it? Can you please show, step by step, how to import it all into a working project ?

This repository is nice, but the full implementation of all things in a during call UI is probably much larger.

It is :)

Do you know perhaps how to clone correctly the official Phone app, or at least just the part of during the call?

You might have better luck finding an answer here https://stackoverflow.com/search?q="platform%2Fpackages%2Fapps%2FDialer"
I have some notes I took last time I was downloading AOSP code to open it in Android Studio, with the intention of someday making it an answer on Stack Overflow:

At least 100GB of free disk space to checkout the code and an extra 150GB to build it.
sudo apt install repo or install with curl
[StudioProjects] mkdir aosp
[StudioProjects] cd aosp

if you choose Android M or older, you'll need JDK 7 instead of 8
[aosp] repo init -u https://android.googlesource.com/platform/manifest
repo sync

this will take about an hour (depending on your network connection), changing branches takes about 20 minutes
make, if you're low on disk space, delete .repo (more than 50 GB additional needed)
make idegen && development/tools/idegen/idegen.sh

open android.ipr in AS, this will take ???
do stuff from https://shuhaowu.com/blog/setting_up_intellij_with_aosp_development.html and https://android.googlesource.com/platform/development/+/master/tools/idegen/README

It's not possible to build it separately without modifying it heavily, sorry.

But it seems that it's what others have done, or at least on the repositories I've shown...

That's what I said :)
niedz., 14 paź 2018, 18:13 użytkownik AndroidDeveloperLB <
<EMAIL_ADDRESS>napisał:

But it seems that it's what others have done, or at least on the
repositories I've shown...
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/arekolek/simple-phone/issues/3#issuecomment-429639242,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2iXXqunORy_Cec4l4LHIopA1TE0Vvpks5uk2KrgaJpZM4XAe2C
.

No, I mean it seems they took just what's needed from the repository I've mentioned (here), and didn't clone the entire AOSP.

But what I just said is that it's not what they did.
I don't think that they cloned entire AOSP, as you wrote "more than 50 GB additional needed".
I think they only took what is needed.
My question is how did they make an order out of all the mess I've found.
There are many folders there that don't make sense.

This is not the place for such a discussion, and I've already gave you all the help that I can, even though I had no such obligation.


Provide small examples / better documentation to improve plugin developer experience

It´s sometimes really hard to work with the Gridsome API, but I think extensibility is crucial for the community to evolve and develp better plugins and for Gridsome to succeed and gain more market share.
Example:
I´m trying to find certain pages generated from one specific collection in order to delete them.
Looking at the documentation, it says

In my opinion one short sentence is not enough information for a method that accepts non-primitive arguments.
But I thought okay, Gridsome is all about providing data as GraphQL schemas, so the findPages(query) parameter must accept GraphQL for sure.
Instead it seems to be not GraphQL that it works with, but JSON objects instead. Of course having no clue how to do queries with JSON, I´ve called findPages() without any parameter so that I at least see what I´m dealing with here,
{
  id: 'f09ec8b6526ec4484b7747e4962c877e',
  path: '/tag/vuex',
  publicPath: '/tag/vuex/',
  context: {},
  internal: {
    queryVariables: {
      id: 'JYj5dxrE1dX',
      '$uid': '898f7e236d35c15953cf5116d0ca360d',
      internal: [Object],
      path: '/tag/vuex/',
      fileInfo: [Object],
      content: '',
      excerpt: '',
      title: 'Vuex',
      '$loki': 74
    },
    route: 'acfc6dd362a9186ba5312976390661e8',
    digest: '5eb49a089986ad63808187a87009e959',
    isManaged: true,
    isDynamic: false,
    query: { paginate: [Object], variables: [Object], filters: {} }
  },
  '$loki': 81
}

My next attempt was to try a simple
let data = findPages({
      path: '/tag/vuex'
    });

which worked, but I need to go deeper with my query to find relations to this tag, so I followed the object structure and tried:
 let data = findPages({
      internal: {
        queryVariables: {
          internal:{
            typeName: 'Tag'
          }
        }
        }
    });

Not working at all, aborts build with

TypeError: gridsome.server.js: fun is not a function (29:16)

Now I´m stuck. The problem is I`m not really sure if that is even possible or not, it´s not clear by looking into the documentation provided.
I´d love to see some work on that and some more clarity to improve the developer experience.

@mklueh I believe that the query should be a Loki (the internal store used by Gridsome) query - some examples here: http://techfort.github.io/LokiJS/tutorial-Query Examples.html

@thetre97 Thanks, the dependency seems to be in the project, will try that :)


404 error page in 'Häufige Fragen'

Describe the bug
A HTTP 404 error occurs when klicking on 'Häufige Fragen'
Expected behaviour
A functioning page for example https://www.bundesregierung.de/breg-de/themen/corona-warn-app/corona-warn-app-faq-1758392
Steps to reproduce the issue

Open the App and click on 'Häufige Fragen'

Load the Page

See a 404 Error Page

Link to https://www.bundesregierung.de/breg-de/themen/coronavirus/corona-warn-app-faq-1759130

Technical details
App version: 1.0.0

Samsung Galaxy S8 Plus (Virtual Device)
Moto G5s Plus
Date/Time  13:35 Mittwoch, 17. Juni 2020 (MESZ) Error Page Screenshot

Possible Fix
Replace the link https://www.bundesregierung.de/breg-de/themen/coronavirus/corona-warn-app-faq-1759130 with for example https://www.bundesregierung.de/breg-de/themen/corona-warn-app/corona-warn-app-faq-1758392
Additional context

(The 404 Page)

Excellent spot. Why is there a number at the end anyways? Is this for versioning?
Shouldn't we be linking to the non-Bundesregierung, that is project website, instead? At least the links need to be non-breaking on Bundesregierung.

Hello,
as you can see here https://github.com/corona-warn-app/cwa-app-android/blob/cacf64a4611c37bb062e7ee4d08822f9ba9d2662/Corona-Warn-App/src/main/res/values-de/strings.xml#L188
the link opened by the app does not contain any of these url markings.
The 404 you are receiving is caused by something on the bundesregierung.de website and not by the app.

Okay, this is very strange. I just tested the app on a new virtual device and the error no longer occurs.

As this is resolved I'll close this issue. Thanks for your contributing! :)

It may be worth for the SAP team to ping the Bundesregierungs-Website team.
Just because an error that sometimes occurs disappears for the person who reports doesn't mean the root cause has been fixed.
Maintainers, your feedback is requested :) @SebastianWolf-SAP @tkowark @jakobmoellersap @harambasicluka

This has been passed on to the appropriate people :)

Thank you @kolyaopahle!

Hi,
I'm one of the developers working on the CMS for www.bundesregierung.de and I looked into this issue.
As noted by @kolyaopahle the app doesn't access this URL directly, but uses a 'prettier' URL that gets redirects to the real URL by our CMS. This was done for two reasons: 1) the content structure and therefore the URL wasn't finalized when we collaborated with RKI/SAP on this, 2) it allows the editorial staff to change the content more easily without having to update the the URL in the app.
The numbers in the final URLs are actually not for load balancing, but are content-IDs, and the URL ending with -1759130 is actually the ID of a placeholder document that was used in the CMS before the App went Live, and hasn't been accessible since June 15th, so I was quiet surprised to see that this URL made it out "into the wild".
Bad news: It seems we used a 301 return code instead of a 302 for the redirect, and somehow the pre-launch URL was accessed and cached somewhere - either by @DE-Max-42's device himself or some proxy/caching infrastructure that he is accessing. Unfortunately neither the App nor the CMS can do anything to clear those cached entries, if they exist.
Good news: There doesn't seem to be a significant number of calls to the outdated URL. (according to our server logs less than 10 requests in the past 48h, with most of them seeming to come from this very github issue)
We will keep an eye on the access logs to see if there is still a significant amount of requests to the the outdated URL and if so, add a special redirect for this URL to the correct URL. And we will also change our redirect logic to send 302s instead of 301s (or add a cache-control header with a sensible ttl) so that they will no longer be cached.


user plugin function

I don't understand user plugin function.

Closing - not enough information provided to proceed further.
Please take a look at https://github.com/naver/pinpoint/blob/master/CONTRIBUTING.md and follow the instructions.


knative-kafka-broker-[receiver|dispatcher] image for s390x

Describe the bug
A clear and concise description of what the bug is.
As already mentioned in #1908 and #1948 for arm, it would be good to have the knative-kafka-broker-[receiver|dispatcher] images for s390x.
Expected behavior
A clear and concise description of what you expected to happen.
knative-kafka-broker-[receiver|dispatcher] images  are available for s390x
To Reproduce
Steps to reproduce the behavior.
Knative release version
Additional context
It would be good to piggyback us on #1968, otherwise I would like to make another PR for s390x after it.

After adding ARM support in https://github.com/knative-sandbox/eventing-kafka-broker/pull/1968 we can add support for other architectures.
Reviews for https://github.com/knative-sandbox/eventing-kafka-broker/pull/1968  is very welcome!


ENH: Proposal for model-<modelname> directory

As an auxilliary to work being done on BEP16 (DWI derivatives), we are proposing a change to the common derivatives specification to allow the creation of a sub-directory into which model parameters will be saved, together with a models.tsv metadata file to describe all the different models that are fit within a pipeline.
EDIT BY @oesteban
We arrived to this proposal as a way of partially address the issues identified by @Lestropie (see bids-standard/bids-bep016#50), building from his proposal n. 3.

See https://github.com/bids-standard/bids-bep016/issues/50 for relevant context.

I haven't really integrated this whole proposal yet, but I want to jot down some quick notes about the direction we took in FitLins, which is at least superficially quite different. Not sure if it can apply here at all...
In FitLins, we have hierarchical models (e.g., run-level -> subject-level -> dataset-level), such that you could potentially have multiple dataset-level models that build off the results in a common subject-level model. Instead of nesting models more deeply inside modalities, I've been pulling them to the top:
fitlins_derivatives/
    dataset_description.json
    node-run/
        sub-01/
        sub-02/
        ...
    node-subject/
        sub-01/
        sub-02/
        ...
    node-group/
        group_results

I imagined the node-* becoming derivative datasets in their own right, and then fitlins_derivatives becoming a super-dataset (a concept still to be defined). This would give the flexibility to, say, distribute first-level results as a standalone dataset for image-based meta-analysis.

@arokem If you want to fix up the markdown, use npm install remark; npx remark <markdown-file> -o.

Thanks for the quick comments here @effigies! Are these proposals really in conflict? I can imagine having a model-<modelname> directory within every one of the node- levels that you specified. Seems complementary to me.

@arokem If you want to fix up the markdown, use npm install remark; npx remark  -o.

Thanks! Unfortunately, working in codespaces because UT's wifi won't let me pull stuff down from GitHub :-/
I'll let @oesteban do the rest of these fixes :-)

@effigies
$ npm install remark; npx remark src/05-derivatives/01-introduction.md -o src/05-derivatives/01-introduction.md
npm WARN saveError ENOENT: no such file or directory, open '/Users/oesteban/workspace/bids-specification/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/Users/oesteban/workspace/bids-specification/package.json'
npm WARN bids-specification No description
npm WARN bids-specification No repository field.
npm WARN bids-specification No README data
npm WARN bids-specification No license field.

+<EMAIL_ADDRESS>updated 1 package and audited 94 packages in 0.764s

42 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

npx: installed 55 in 2.831s
command not found: remark

the npx remark command doesn't seem to work

I ran it. Apparently it doesn't fix everything, though...

I was wondering how this fits with the computational model BEP (if it's related/needs to)?

I was wondering how this fits with the computational model BEP (if it's related/needs to)?

As per that BEP: BIDS Computational Model files store the mathematical and computational descriptions of
computational models as well as simulation results. Based on that I'd say the only overlap would be the simulation results bit, and not entirely because this PR shies away from specifying models themselves. I believe that BEP has a very large overlap with the BIDS-statsmodel.
Instead, we want this PR to gauge the interest/position of the BIDS community in the possibility that we add the new model-<model_id>/ level to the directory hierarchy of derivatives.
There are some deeply related aspects of this PR that we intendedly left for the future:

Multi-datatype models (e.g., a model that generates derivatives from both func/ and dwi/ resources). We were entertaining ideas like allowing a folder func+dwi/ to exist, or have a more general multi/ possibility. In any case, we did not want to get into that issue here, but will come up almost immediately after this one is decided.
The actual specification of models. There's a pretty much developed proposal, very comprehensive, in BEP016 -- thanks to the persistence, attention to detail, and overall titanic effort of @Lestropie.

Those are critical elements that affect this PR, so it's good to have them in mind (and it's a likely possibility that a majority of people push towards having one or both issues covered here too, should it be going towards an accepted decision).
It'd be great to have critical reviews from @rwblair and @tsalo, and anyone else involved in the BIDS schema feat. Does this complicate things on that front?
Historically, this PR comes from bids-standard/bids-bep016#50. It does not itself fully resolve the inheritance issue described there, but it basically evolves from Option 3 there, which indirectly resolves the problem to the extent it is necessary within BEP016.

@arokem @Lestropie I have allowed myself to remove the WIP label from the title. I have made some edits to use macros and make the text more consistent with the rest of the spec.
For a render of this PR at this point, go to https://output.circle-artifacts.com/output/job/ecd7481c-1064-41ad-a51b-e362395503e4/artifacts/0/dev_docs/01-introduction.html

Dear all, by chance I stumbled on this BEP, and as I'm working on various BIDS-related software, I wanted to put my 5 cents.
My concern is sub-folders like dwi/model-DTI may confuse BIDS tools (and make difficult to develop new) as it deviates from standard BIDS naming convention (sub-<>_<entities>_<suffix>.<extension>).
From implementation point of view we will need to add a lot of tests into dataset parcing in order to index such files.
I would propose to put models into separate data-type folder together with the sidecar json and summury tsv file:
sub-abc/ses-def/models/sub-abc_ses-def_mod-DTI_model.d
sub-abc/ses-def/models/sub-abc_ses-def_mod-DTI_model.json
sub-abc/ses-def/models/sub-abc_ses-def_models.tsv
sub-abc/ses-def/models/sub-abc_ses-def_models.json

This way the model data is introduced exactly the same way as any other data file in the dataset, simplifying parsing.
The d extension is here just to point it's a folder.
With carefull selection of entities (for ex for parameter adjustments) you can see which folder correspond to what model:
sub-abc_mod-DTI_par1-00_par2-00_model.d
sub-abc_mod-DTI_par1-00_par2-01_model.d
sub-abc_mod-DTI_par1-00_par2-02_model.d

With convention that 00 means nominal/default value, and non-zero index the corresponding parameter adjustment.
Or alternatively using one entity for different parameter sets with meaningful naming.
For the group level models models folder can be moved into root directory:
root/
    models/acq-DTI_model.d
    sub-abc/

Cheers,
Nikita

My concern is sub-folders like dwi/model-DTI may confuse BIDS tools (and make difficult to develop new) as it deviates from standard BIDS naming convention (sub-<>_<entities>_<suffix>.<extension>).

I don't think there's anything in this PR that is not supported by the current specifications. It's true that the BIDS Validator may require some extra heuristic, but that's more a problem of being able to formalize BIDS rules into a schema that can be used directly by the validator.
Since this only affects BIDS-Derivatives (and that's clearly stated at a couple of places in this PR) I don't think this would break any existing software either, basically because there's no specification to break at this point.
Finally, I'll also mention that this model-<label>/ folder is basically specified like sub-<label> + participants.tsv file or the ses-<label>/ folder. So it doesn't seem to break any existing conventions for folder names.

I would propose to put models into separate data-type folder together with the sidecar json and summury tsv file:

I think these suggestions fit better in #1282. Can you check that out?
Thanks a lot for the input, happy to clarify further if the argument is not sufficiently convincing.

Since this only affects BIDS-Derivatives (and that's clearly stated at a couple of places in this PR) I don't think this would break any existing software either, basically because there's no specification to break at this point.

Indeed, the derivatives in BIDS are not regulated.
But even so, deviating from BIDS style of names can provide difficulties to use such derivatives in the analysis scripts.
If you take and example of bids-matlab (free publicity!),
it allow to parse files even if they are not in the official BIDS schema.
But the dwi/model-DTI folder will be ignores as it doesn't starts with sub-.
Imagine you want a script that compare different models inside the same dataset.
If these models folders are supported, then you just need to  query all files with suffix model,
and you have all of them.
In opposite, you need to do recursive search for the folders containing model-<name>,
and then parse the subject/session names retrieve corresponding images.
It's feasible, but requires additional code.
I'm speaking less from human and more from machine perspective.
Bids software know how to deal with bids-formatted names and structure,
so any deviations will add just more complexity.

I think these suggestions fit better in https://github.com/bids-standard/bids-specification/pull/1282. Can you check that out?

My point was about model-<name> sub-folder, not about the name of suffix.
The example I give can be changed in suffixes, entities and extensions.
But I fight for data-type folder and sub- prefix)

But even so, deviating from BIDS style

How this proposal deviates from BIDS style specifically?

If you take and example of bids-matlab (free publicity!),
it allow to parse files even if they are not in the official BIDS schema.
But the dwi/model-DTI folder will be ignores as it doesn't starts with sub-.

BIDS should remain agnostic to the decisions made by the software developer. This idea comes from the fact that scientists use folders typically to cluster the outputs of important models in their analysis. They typically group by subject first, and that's why sub-<label> is at the top. It seemed logical to offer the opportunity to encode models this way. That said, you don't need to have a model directory if you don't want (the same way you may not have the session folder).

Imagine you want a script that compare different models inside the same dataset.
If these models folders are supported, then you just need to query all files with suffix model,
and you have all of them.

Human: goes to the _models.tsv file and sees all the models with relevant info.
Software: e.g., pybids could do this tomorrow with a simple edit of the bids schema inside:
>>> layout.get_models(datatype="func")
[ list of all model identifiers under datatype func ]

From BIDS/common principles

For a data file that was collected in a given session from a given subject, the filename MUST begin with the string sub-_ses-. If the session level is omitted in the folder structure, the filename MUST begin with the string sub-, without ses-.
Note that sub- corresponds to the subject entity because it has the sub- "key" and "value", where  would in a real data file correspond to a unique identifier of that subject, such as 01. The same holds for the session entity with its ses- key and its  value.

Folder model-<name> is collected from one subject (being placed in sub- folder) but don't contain sub- entity.

Software: e.g., pybids could do this tomorrow with a simple edit of the bids schema inside:

But if it works without any edit, isn't better?
If all models for a subject are collected in datatype folder, with same naming conventions,
they could be treated as normal data and retrieving with simple query:
layout.get_data(datatype="models", type="func")

I don't use pybids so I don't know how to query individual entities.
Anyway it's just a suggestion, to take or to leave.

From BIDS/common principles

For a data file ...

This is not a data file, this is a folder. Folders do not apply the entity concatenation principle.

But if it works without any edit, isn't better?

Your proposal (or any derivative of it) will require a change in PyBIDS of exactly the same scale of changes as the one here (because you are proposing new suffices). From this perspective, there's no difference, IMHO.

I don't use pybids so I don't know how to query individual entities.

I'm not saying here we should cater to any specific project -- I don't use bids-matlab so for me the argument goes the other way around.

Making "model" a datatype is an interesting suggestion. It might cause more ambiguity than it solves, but let me follow that train of thought, if I can maybe poke and prod at the concerns about BIDS "conformity" in the most general sense.
You can conceptualise the current filesystem structure as following this hierarchy:

Single-entity-based directories (sub-<label>, ses-<label>);
One non-entity directory (datatype);
Files (must replicate entities from 1. and have a suffix).

What's being proposed can violate this structure in a couple of different ways:

Having eg. model-<label>/ as a sub-directory of eg. dwi/ breaks the ordering between 1 and 2;
Having directory names replicate entities from parent directories has no precedent.

Point 1 is what is resolved by having model as its own datatype. Point 2 is a consequence of us going for Option 3 in https://github.com/bids-standard/bids-bep016/issues/50.
Hoping that might help rather than hinder seeing where each side is coming from.

hi @oesteban @Lestropie @arokem @PeerHerholz @poldrack @adelavega @effigies
I finally had the time to look at all these proposals organized by @Lestropie  I am grateful for that.
Also, I looked over what @oesteban has proposed here, thank you @oesteban.
Furthermore, @PeerHerholz pointed out that the term model (and 'models') is already being used in the Stats Model Specification and by the Computational Models which impinge on each others.
I am starting from the principles and on the fact that we should not fix BIDS but develop a description for connectivity data:
Less is more
target easier and doable goals, finish less but get it done!
The 80/20 rule
tackle solutions that address 80% of most commonly used cases
Identify & focus on

core principles not extreme/rare cases
main ideas not specific details
creating the backbone of the BEP, avoid focus on theoretical aspects

It seems to me that we are not going to find a solution that will not have problems. Each solution will either require changes to BDIS, or (many of them) break the inheritance principle, or overlap with other datatypes or the Stats Model Spec.
I would like to suggest that instead of trying to solve this problems, the 8 of us. We advance with a BEP. We pick one option that will have problems, that it will not be perfect and bring the option to the wider community.
I also suggest that we bring it with the hope that the broader community accepts it. This is because we can gain much from having a poor BIDS spec on this and little from continuing to find a perfect way.
I am aware that what I am writing means that we will most likely later need to make changes. Yet, I would love to use the 80/20 or even a 70/30 rule here and just move forward with a proposal that will be sent to the community for feedback.
Looking at all the proposals described by @Lestropie here and the option described by @oesteban here, we attempted to make another example for functional model here
The solution seems to be OK to us. Very similar to what a Stats Model Specification but reasonable, not perfect. This approach should also allow to rewrite the Dimensionality reduction network and not affect the Connectivity Matrix description which uses an approach similar to the original DWI BEP16 approach.
I am sure we can find cases in which this fails. But 7030 ok to y'all? Can we keep this one and send it to the community, please?

@francopestilli : just making sure that I understand what you are suggesting: you want to incorporate the content of this PR into the BEP16 repo and close it here? Basically, kicking the can of the discussion on the different alternatives that @Lestropie detailed in the google doc to the discussion on the BEP? Is the idea that the other BEPs that depend on this decision wait to see how BEP16 shakes out?

I would suggest we should not merge it with BEP 16, but I also don't think we can make this decision in haste, as it has potential implications.
Alternatively, this becomes its own BEP, and BEP16 and related efforts "depend" on the model BEP. That would give people more time to review this proposal without necessarily holding anything up.

+1 for node. I think model is a very loaded word with more conceptual implications, whereas node can be more generic.

@francopestilli : just making sure that I understand what you are suggesting: you want to incorporate the content of this PR into the BEP16 repo and close it here? Basically, kicking the can of the discussion on the different alternatives that @Lestropie detailed in the google doc to the discussion on the BEP? Is the idea that the other BEPs that depend on this decision wait to see how BEP16 shakes out?

Hi @arokem actually I went over each one if the options @Lestropie proposed in the Google doc. I added also examples at the bottom of the doc of how this proposal would save func data.
I was not able to find a solution in any of the options @Lestropie reviewed and presented. Did i get that wrong? Was there any option in the doc that was a potential solution / a way forward?
Just to clarify i did follow everything rob did

We also are using node in the sense of a node in a computational graph, and I am for using it that way here. (As an aside, I note that BEP 017 is using it to refer to nodes in a connectivity graph defined by a connectivity matrix...)

I think we are talking about different nodes in a computational graph. I'm fairly confident that your node-run, or node-subject have internally more nodes of a computational subgraph inside. Here, node is used as an atomic entity that doesn't have a computational sub-graph underneath (obviously, this is mostly theoretical and arbitrary because these models will certainly be decomposable in smaller pieces).
Regarding the overlap with the connectivity BEP - I have less arguments to maintain node. Perhaps, we could go back to the root of the PR and, instead of enabling these folders to encode computational nodes (or a particular model's outcomes), think of these as a utility for the user to create "results sets" (which is the common practice of researchers this BEP is trying to enable):
└─ <pipeline_name>/
   └─ sub-<label>/
      └─ <datatype>/
         ├─ set-<label>/
         │  ├─ resultset_description.json
         │  └─ <node files>
         ├─ sub-<label>_sets.tsv
         └─ sub-<label>_sets.json

As you can see, I'm shying away from putting this higher in the hierarchy because that will open another can of worms. A less voluminous problem we intendedly avoided was multi-datatype analyses. It seems reasonable to propose allowing set-<label> folders as siblings of <datatype>/, having a new multi/ datatype folder where these resultsets can be stored or allowing composition <datatype1>+<datatype2>/. However, that is left for future PRs and debate or otherwise this one might not see a decision ever. For the same reasons, I would avoid stating in this particular PR that the folders can be used at any level of the tree structure.

?

Re "the other BEPs that depend on this" it looks like we have had several of the community discussing this issue. Would it be fair to hope that this can be accepted quickly?
-- Yes, we we would have BEPs waiting for this and one BEP (the dimensionality reduction one) has already used the 'model-' specification (it would need to be updated to the final version though).

BEPs waiting for this and one BEP (the dimensionality reduction one) has already used the 'model-' specification (it would need to be updated to the final version though).

I would encourage everyone to try not to need this feature -- I see it more as a resource to the user than as a key to unlock the progress at the complicated points of other BEPs. Otherwise, we risk rushing important changes that we will not be able to roll back (backward compatibility) and I agree with @adelavega that we do want the input of as many as possible before proceeding with this idea.

I like "result" instead of "model" ("resultset" also fine!), to avoid the already crowded space around that word. I think that "node" might confuse both because of the overloading of the term with analysis of connectivity, and because I suspect that there are many that don't think of the results they obtain in terms of nodes in a computational graph, even if that's a technically accurate description (I don't usually, unless someone/something forces me to).
@francopestilli : I am still not sure what you suggest. That we move on with the proposal in this PR? The example you added at the bottom of the google doc is not based on this PR, but based on a different variety of this idea ("alternative 3"), which does not introduce the new "results_description.json".
IIUC, one difference between "alternative 3" and the current PR is whether result/resultset metadata are stored in multiple files that are all called "resultset_description.json" (or similar) or whether we require that this be saved in files that have different names. Though formally I think that this is a minor difference, and both seem acceptable to me, I think that there might be some practical benefits to varying names across results/resultsets in minimizing confusion.
So, with minimal changes from the proposal in https://github.com/bids-standard/bids-specification/pull/1280#issuecomment-1255269988:
└─ <pipeline_name>/
   └─ sub-<label>/
      └─ <datatype>/
         ├─ set-<label>/
         │  ├─ set-<label>.json
         │  └─ <resultset files>
         ├─ set-<label>_<suffix>.json
         ├─ sub-<label>_sets.tsv
         └─ sub-<label>_sets.json

And with some additional variations (adding a suffix, pulling it up one directory)
└─ <pipeline_name>/
   └─ sub-<label>/
      └─ <datatype>/
         ├─ set-<label>_<suffix>/
         │  └─ <resultset files>
         ├─ set-<label>_<suffix>.json
         ├─ sub-<label>_sets.tsv
         └─ sub-<label>_sets.json

Could potentially go even further:
└─ <pipeline_name>/
   └─ sub-<label>/
      └─ <datatype>/
         ├─ sub-<label>_set-<label>_<suffix>/
         │  └─ <resultset files>
         ├─ sub-<label>_set-<label>_<suffix>.json
         ├─ sub-<label>_sets.tsv
         └─ sub-<label>_sets.json

Where the sub-<label> entity could then further down the line be replaced by a group-<label> entity if that makes sense, but that's probably for a future PR.

@francopestilli : You said:

I was not able to find a solution in any of the options @Lestropie reviewed and presented. Did i get that wrong? Was there any option in the doc that was a potential solution / a way forward?

Is this about functional derivatives? Is there something special about the functional derivatives that makes it impossible to store them in the way proposed in this PR or in the other alternatives in the google doc (I'll keep linking to it, so that we don't get confused about which doc)? Or -- alternatively- in one of the ways in my recent comment? I might be missing something, not being as familiar with the functional derivatives.

Thanks for the rebase.
There seems to be more agreement with the "result-set" concept, instead of model, WDYT?

I think we want to avoid that dash, right? So either "results" or "resultset"?

+1 for "results" as it's the common usage (no one ever uses "resultset" in real life)

I think we want to avoid that dash, right? So either "results" or "resultset"?

Yes, definitely.

+1 for "results" as it's the common usage (no one ever uses "resultset" in real life)

There are two things I like about "resultset":

Feels natural to use set-<label> as entity, while res-<label> is already there (for resolution in derivatives) and result-<label> has double the length.
It stresses the fact that there might be other "sets" of results under the same derivatives

However, the same way we have "participants" and sub-<label>, we could have "results" and set-<label>, and I'd be happy with this.

I agree. Result sounds good. Even though in my mind result sounds more scientific that these derivatives will be.

I agree. Result sounds good. Even though in my mind result sounds more scientific that these derivatives will be.

I see what you mean. I think this is important if we can foresee wanting to use "result" for some future derivatives that are closer to the scientific conclusions. OTOH, something even closer to the "results" section of a paper might fit into the concepts laid out here too.

I've tried to implement something along these lines in the most recent 45467f8. I don't think that we can entirely get rid of the notion of a model and the related model_id, so I didn't here. The question is whether this provides the clarity and generality we would hope for.

Hi everyone,
I would like to revive this thread and the corresponding discussion.
After a meeting with @arokem concerning the BIDS connectivity-related BEPs, we wondered about the current state of this proposal. Given its scope and aims, we consider it a very useful and important addition. For example, within the connectivity-related BEPs, BEP16 and Dimensionality reduction-based networks would both profit from a coherent way of describing what model was applied in which manner and what files were derived from that (e.g. mentioned here).
However, we are also aware that it will introduce quite a few changes regarding multiple core aspects and BEPs.

Thanks @PeerHerholz. @bids-standard/steering - perhaps some mechanism to initiate a reflection period and a deadline for making a decision would be helpful to preempt PR stagnation.

@arokem I'm going to propose a fix for the failing table, if you want to hold off on pushes for a couple minutes.

Okay, I'm done.

For the time being, I have rebased this on top of current master to facilitate more discussion of this proposal.
@tsalo : regarding your previous comment, should I add a new file called "models.yaml" in here and try to follow the example of the existing files in that folder?


Build errors with .NET 8.0 on Linux arm64

Tested versions
4.2
System information
Godot v4.2.stable.mono - Manjaro ARM #1 SMP PREEMPT Sun Oct 15 18:48:13 UTC 2023 - Wayland - GLES3 (Compatibility) - Mali-T860 (Panfrost) -  (6 Threads)
Issue description
When attempting to build a dotnet godot project on arm64 it errors with the following:
Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.Threading.ThreadPoolWorkQueue.GetOrCreateThreadLocals()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading.PortableThreadPool+WorkerThread.WorkerDoWork(System.Threading.PortableThreadPool, Boolean ByRef)
   at System.Threading.PortableThreadPool+WorkerThread.WorkerThreadStart()

output of dotnet --info:
.NET SDK:
 Version:           8.0.100
 Commit:            57efcf1350
 Workload version:  8.0.100-manifests.6c33ef20

Runtime Environment:
 OS Name:     manjaro-arm
 OS Version:
 OS Platform: Linux
 RID:         linux-arm64
 Base Path:   /usr/share/dotnet/sdk/8.0.100/

.NET workloads installed:
 Workload version: 8.0.100-manifests.6c33ef20
There are no installed workloads to display.

Host:
  Version:      8.0.0
  Architecture: arm64
  Commit:       5535e31a71

.NET SDKs installed:
  8.0.100 [/usr/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.NETCore.App 8.0.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  Not set

global.json file:
  Not found

Steps to reproduce
on arm64 device create a new project. create c# solution. attempt to build.
Minimal reproduction project (MRP)
a blank project

I can't reproduce with current master and dotnet 7.0.113, tested on Fedora 39 in ARM64 VM on M1 Mac.

But it is reproducible with dotnet 8.0.0 manually installed via https://dot.net/v1/dotnet-install.sh.

If it works with .NET 7.0 but not .NET 8.0, this is possibly an upstream bug where they'd have regressed in their Linux arm64 support.
I remember testing it a few weeks ago on a Linux environment on an arm64 Chromebook and I also got .NET working fine with Godot 4.2-beta. I tested with .NET 6.0 from the Microsoft generic tarball. https://twitter.com/Akien/status/1719693063570837779


[Backport] Ceph hostname change during upgrade

L>M has changed the hostname of our containers, therefore we
need to adapt this everywhere. Ceph was left behind, and this
is fixing the hostnames by shutting down the monitors, removing the mons,
deleting the containers, recreating them, and rejoining the cluster, all
of this in a serial way.
The ceph-mon playbook was adapted to verify the bind mount is there, in
order to avoid data loss.
Comments are added explaining what is done, and what is needed
when upgrading an environment with ceph.
This commit also ensures the generation of the facts used in the
setup-maas is properly done (explicitly asking the generation of
the facts by including our new gen-facts playbook).
Signed-off-by: Jean-Philippe Evrard<EMAIL_ADDRESS>Connected rcbops/u-suk-dev#383
(cherry picked from commit acb2491e89e163c78fe776524f31925bd008de54)

recheck_upgrade
Unrelated failure at first sight.

Should we have a release note for this change?

@alextricity25 I think we should but given that this is a backport we'll have to do it in a separate patch.

Hmmm..Another failure due to MaaS alarms in the critical state. This might be worth looking into.

@alextricity25 it's got something to do w/ rabbitmq, but I haven't been able to track it down yet :(

recheck_upgrade

I'm not exactly sure what is causing the MaaS alarms to stay in CRITICAL status on the upgrade job, but I'm currently looking into it.

recheck_upgrade

The upgrade job failed on:
20:04:28 TASK: [elasticsearch | Install pip packages] **********************************
20:04:28 ok: [jrpcaioiad-d5c_elasticsearch_container-890d3aa1] => (item=elasticsearch>=2.0.0,<3.0.0)
20:04:44 failed: [jrpcaioiad-d5c_elasticsearch_container-890d3aa1] => (item=elasticsearch-curator==4.0.4) => {"attempts": 5, "cmd": "/usr/local/bin/pip install -U elasticsearch-curator==4.0.4", "failed": true, "item": "elasticsearch-curator==4.0.4"}
20:04:44 msg: Task failed as maximum retries was encountered

I've only seen this once in my testing, and I remember it had something to do with elasticsearch pip package version 2.0.0. The pip packaged never updated to version 2.3.0, and caused the installation of elasticsearch-curator to fail. However, it doesn't happen on every upgrade. I wonder if Ansible ever tries to install elasticsearch-curator before updating elasticsearch to the latest package version.
reheck_upgrade

recheck_upgrade

recheck_upgrade

recheck_upgrade

recheck_upgrade

recheck_upgrade

recheck_upgrade

recheck_upgrade

Failed on:
04:39:43 TASK: [Verify Check & Alarm Status] *******************************************
04:57:01 failed: [jrpcaioiad-e36] => {"attempts": 8, "changed": false, "cmd": ". /openstack/venvs/maas-r13.1.0rc1/bin/activate\n /opt/rpc-openstack/scripts/rpc-maas-tool.py verify-status --entity jrpcaioiad-e36", "delta": "0:00:58.348448", "end": "2016-10-08 04:57:00.643052", "failed": true, "failed_when_result": true, "rc": 1, "start": "2016-10-08 04:56:02.294604", "stdout_lines": ["--- 2016-10-08 04:56:59.083168 ---", "Checks and Alarms with failures:", " - Entity:en2tsPErDi:jrpcaioiad-e36", "   - Check:agent.plugin:chK98NUt9T:galera_check--jrpcaioiad-e36-galera-container-5b133e57: Completed:True Status:okay", "     ! Alarm:alkAhoAXY1:innodb_deadlocks--jrpcaioiad-e36-galera-container-5b133e57:CRITICAL"], "warnings": []}
04:57:01 stdout: --- 2016-10-08 04:56:59.083168 ---
04:57:01 Checks and Alarms with failures:
04:57:01  - Entity:en2tsPErDi:jrpcaioiad-e36
04:57:01    - Check:agent.plugin:chK98NUt9T:galera_check--jrpcaioiad-e36-galera-container-5b133e57: Completed:True Status:okay
04:57:01      ! Alarm:alkAhoAXY1:innodb_deadlocks--jrpcaioiad-e36-galera-container-5b133e57:CRITICAL
04:57:01 msg: Task failed as maximum retries was encountered
04:57:01
04:57:01 FATAL: all hosts have already failed -- aborting

This is second time I've seen this failure in the last 12 hours, so doesn't look it's a completely random failure.

recheck_upgrade

It looks to me we're good to go, right? It seems the backport is good.
Can someone else than @mattt416 or @alextricity25 review?

ya, straightforward backport, meant to do this last week...


Fortify error on Android Pie

Problem
When running CHIP on Android Pie, I'm hitting the following error:
FORTIFY: sendto: prevented 40-byte read from 24-byte buffer

I've traced this to the call getifaddrs(&mAddrsList) on https://github.com/project-chip/connectedhomeip/blob/master/src/inet/InetInterface.cpp#L653
The implementation for this function (on Android) comes from:
https://github.com/project-chip/connectedhomeip/blob/master/src/inet/InetInterface.cpp#L54
I did NOT encounter this error on Android N.  Incidentally, the Fortify check for send()/sendto() was added in Android O:  https://android.googlesource.com/platform/bionic/+/master/docs/status.md
Upon reviewing the implementation for getifaddrs() in third_party/android/platform-libcore/android-platform-libcore/ifaddrs-android.h line 182, it looks like the size of the buffer is swollen by the padding and alignment macros.
Incidentally, bionic has provided its own getifaddrs() since at least Android L.
Proposed Solution
Either:

add a max-version check to InetInterface.cpp to NOT use libcore after a certain point
OR just use <ifaddrs.h> unconditionally

Here's the diff:
https://github.com/project-chip/connectedhomeip/compare/master...milezhacks:issues/12326?expand=1
Will submit PR once CI completes.

Incidentally, bionic has provided its own getifaddrs() since at least Android L

This statement is wrong.  getifaddrs() was added to Bionic in Android Nougat.  For Android L (API Level 21) this stub is, in fact, required but shouldn't be used for API levels >= 24.

Added looks critical: FORTIFY error points to invalid memory access.


Having trouble running the "Getting started" section (even the tests do not run)

Hi,
I am trying to run the KnowBert code but keep getting stuck with the following error when trying to run the tests or the "How to embed sentences or sentence pairs programmatically" snippet:
tests/evaluation/test_wic_reader.py:3: in <module>
    from kb.include_all import  WicDatasetReader
kb/include_all.py:2: in <module>
    from kb.kg_embedding import KGTupleReader, KGTupleModel
kb/kg_embedding.py:8: in <module>
    from allennlp.data import DatasetReader, Token, Vocabulary
/opt/conda/envs/knowbert/lib/python3.6/site-packages/allennlp/data/__init__.py:1: in <module>
    from allennlp.data.dataset_readers.dataset_reader import DatasetReader
/opt/conda/envs/knowbert/lib/python3.6/site-packages/allennlp/data/dataset_readers/__init__.py:10: in <module>
    from allennlp.data.dataset_readers.ccgbank import CcgBankDatasetReader
/opt/conda/envs/knowbert/lib/python3.6/site-packages/allennlp/data/dataset_readers/ccgbank.py:9: in <module>
    from allennlp.data.dataset_readers.dataset_reader import DatasetReader
/opt/conda/envs/knowbert/lib/python3.6/site-packages/allennlp/data/dataset_readers/dataset_reader.py:4: in <module>
    from allennlp.data.instance import Instance
/opt/conda/envs/knowbert/lib/python3.6/site-packages/allennlp/data/instance.py:4: in <module>
    from allennlp.data.fields import TextField, ListField, SpanField
/opt/conda/envs/knowbert/lib/python3.6/site-packages/allennlp/data/fields/__init__.py:7: in <module>
    from allennlp.data.fields.array_field import ArrayField
/opt/conda/envs/knowbert/lib/python3.6/site-packages/allennlp/data/fields/array_field.py:10: in <module>
    class ArrayField(Field[numpy.ndarray]):
/opt/conda/envs/knowbert/lib/python3.6/site-packages/allennlp/data/fields/array_field.py:45: in ArrayField
    @overrides
/opt/conda/envs/knowbert/lib/python3.6/site-packages/overrides/overrides.py:88: in overrides
    return _overrides(method, check_signature, check_at_runtime)
/opt/conda/envs/knowbert/lib/python3.6/site-packages/overrides/overrides.py:114: in _overrides
    _validate_method(method, super_class, check_signature)
/opt/conda/envs/knowbert/lib/python3.6/site-packages/overrides/overrides.py:135: in _validate_method
    ensure_signature_is_compatible(super_method, method, is_static)
/opt/conda/envs/knowbert/lib/python3.6/site-packages/overrides/signature.py:93: in ensure_signature_is_compatible
    ensure_return_type_compatibility(super_type_hints, sub_type_hints, method_name)
/opt/conda/envs/knowbert/lib/python3.6/site-packages/overrides/signature.py:288: in ensure_return_type_compatibility
    f"{method_name}: return type `{sub_return}` is not a `{super_return}`."
E   TypeError: ArrayField.empty_field: return type `None` is not a `allennlp.data.fields.field.Field`.

Steps to reproduce

Enter a clean anaconda docker container docker run -it continuumio/anaconda3
apt-get update && apt install -y g++ make
git clone https://github.com/allenai/kb.git
conda create -n knowbert python=3.6.7
source activate knowbert
pip install torch==1.2.0
pip install -r requirements.txt
python -c "import nltk; nltk.download('wordnet')"
python -m spacy download en_core_web_sm
pip install --editable .
pytest -v tests

Before running tests downgrading to overrides==3.1.0 and scikit-learn==0.22.2 solves the issue!

@lunarie16 Thanks! I´ve changed my requirements to
torch==1.4.0
Flask
waitress
ujson
spacy==2.0.18
urllib3==1.25.10
click==7.1.2
overrides==3.1.0
scikit-learn==0.22.2

and it works as expected.

Hello, have you installed the allennlp? I can't install it with the official guide

@leonodelee Hello, have you tried following the steps I give in my answers to issue #39 ? If so and you still have trouble, please provide error messages, or if there are none, a more detailed description of the abnormal behavior.

@leonodelee Hello, have you tried following the steps I give in my answers to issue #39 ? If so and you still have trouble, please provide error messages, or if there are none, a more detailed description of the abnormal behavior.

Thank you for your kindful help, I solved this problem by 'pip install allennlp==0.8.2' and other install instructions in https://github.com/allenai/kb/issues/39


cdkTextareaAutosize in textarea

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[X] support request

How to implement cdkTextareaAutosize in textarea type of material?

added support of autosize in v5.3, you can configure it through the following options:
{
  ...,
  type: 'textarea',
  templateOptions: {
    autosize: true,
    autosizeMinRows: 5,
    autosizeMaxRows: 10,
  },
},


Few improvements to PressureKernels.jl

Codecov Report
Attention: Patch coverage is 37.50000% with 5 lines in your changes missing coverage. Please review.

Files
Patch %
Lines

src/stokes/PressureKernels.jl
37.50%
5 Missing :warning:

Additional details and impacted files

:loudspeaker: Thoughts on this report? Let us know!


Add requirements.txt

Add requirements.txt, and update install.sh. I think at some point it'd be a good idea to reorganise the code into package(s), to ease the installation procedure.

LGTM.

Add requirements.txt, and update install.sh. I think at some point it'd be a good idea to reorganise the code into package(s), to ease the installation procedure.

Agreed.


Update datepicker value when received value changes

Now temporalValue is used to show the datepicker value and that value is initialized with the initial value that comes from props. But if that initial value changes, the datepicker does not updates its temporal value.
Added a useEffect to update temporalValue if 'values' props changes.
Also return selectedValue as a string to consider the timezone

^removed patch since the auto-increment action isn't quite working, and you bumped the version in the PR 🙂


Jupyter dash is now an optional package

Projector without dash has been reimplemented as default (projector.plot)
Projector with dash is moved to new function (projector.plot_with_jupyter_dash)
If Jupyter_Dash is not installed, it will raise an error when running plot_with_jupyter_dash

Please link the linear ticket or use the Linear GitHub issue ID in the future


lower_constant and lower_cast should probably return new references

Feature request
Currently @lower_constant and @lower_cast expect the implementation to return borrowed references. This makes it tricky to implement lowering constants and casts for memory managed types as you cannot just use native constructors (if available). For casting there might even be edge cases that cannot be implemented at all (#3492).
It would be great if the following naive implementation strategy for lowering constants and casts worked. Assume we have an existing (maybe memory managed) Numba type AType and a new extension type BType with a native constuctor B(a: A).
Lowering a constant B might look like:
@lower_constant(BType)
def lower_constant_b(context, builder, typ, pyval):
    a = pyval.a  # assuming B has an attribute a and constant AType can be lowered
    def lower_b_impl():
        return B(a)
    return context.compile_internal(builder, lower_b_impl, typ(), [])  # returns new ref

Casting AType to BType could be implemented like
@lower_cast(types.Number, UnitType)
def cast_a_to_b(context, builder, fromty, toty, val):
    def cast_a_b_impl(a):
        return B(a)
    return context.compile_internal(builder, lower_b_impl, totyp(fromty), [val])  # returns new ref

Withe the current refcounting conventions the implementations above will leak memory. In some cases you can avoid the memory leak by punting on the refcount pruning pass and simply call context.nrt.decref on the result of compile_internal. However, this will not work in general (for example casting tuples will not work) and crash the interpreter.

Thanks for the report. For context, some gitter chat: https://gitter.im/numba/numba?at=5d652f5e07d1ff39f8912692
Am wondering if something like the RefType indication in the decorator might help as per http://numba.pydata.org/numba-doc/latest/reference/deprecation.html#id18, but this may be too simplistic.

Based on your suggestion on the mailing list I implemented just that and opened PR #4506. Still trying to figure-out if there is a way to get my code working w/o changing the conventions in the core but does not look promising at the moment.

This was discussed at the core developer meeting on 3rd Sept 2019. General consensus was:

That at Numba IR level implicit cast should not happen and in fact making all casts explicit is neater/easier to reason about/consistent. Users should see no behavioural change.
Reuse of existing ir.Expr.cast should be fine.
Adding RefType or similar for safety and ensuring it's backwards compatible is a good idea.


Is it possible to select or filter data in different data collection?

Hi, I'm a newbie in react native, for my question, is it possible to select the different collection(not sure is it datastore's filename in here) to access? For example, I have a filename called Storage A and Storage B, so when I load the database, how can I choose which database should be loaded?
    db.loadDatabase(function (err, Storage A) {     // Callback is optional }
I'm not sure this is the correct way or not?

tou should create one db at a time and then use each one independently


Case sensitive tag search queries?

Platform:  Windows 10
Python version:  3.7.0
Pyzotero version: 1.3.15
Is it possible to do a case sensitive search query when filtering by tags?
When retrieving items via the tag, the search query seems to be case insensitive. That is, for example:
zot.items(tag = "AGENCY")
zot.items(tag = "agency")
zot.items(tag = "Agency")
all produce the same result.
Since I'm trying to specifically retrieve items via a case sensitive tag search (to replace them with proper case), it would be very helpful if there was a way to change that behaviour. I could not find any info on that in the Pyzotero or Zotero API docs. Am I missing something?

Pyzotero doesn't modify the case of search input, so I think it's the Zotero API that's ignoring case. Can you reproduce the problem using cURL? Try asking on the https://groups.google.com/forum/#!forum/zotero-dev if / when you have.

Yes, I was suspecting that. I think it's the way Zotero works with tags. I might try bringing it up there, thanks! Since it's a problem of computational efficiency and not code-breaking in my case, it might not be worth tinkering with the API itself though.
Thanks for the quick reply, and for the awesome Python package you made there! Makes my job cleaning up a couple hundred tags in a couple thousands entries so much easier.


Building bar charts with custom data using generators

I created the bar chart below using a loop and creating a new view and then adding all those views to a scrollview. I have a Wind object that stores the values you see below:

Using the view generators you extend with this library I would be able to make a new label for wind speed (the label within the bar) and the wind direction (the image view above the bar). My confusion is with populating those views with data from my Wind object: wind direction in degrees to rotate UIImage and label text as a String.
I would pass it an array of ChartPoints but ChartPoint is only aware of it's axis values. Is it possible to get an index within a view generator and grab data from Wind to populate those custom views, is there? Rough example:
Build custom view with models
        let windDirectionViewGenerator = {(chartPointModel: ChartPointLayerModel, layer: ChartPointsLayer, chart: Chart) -> UIView? in

        let image = UIImageView(image: "windDirection")

        // Get some index, somehow?
        let windAtIndex = windViewModel[i]

        // Rotate `image` with `windAtIndex.direction`

            return image
        }

Generate custom layer to be send to Chart
// Build with existing frame and axis. Pass it a new generator to build the arrow.
let windDirectionLayer = ChartPointsViewsLayer(xAxis: xAxis, yAxis: yAxis, innerFrame: innerFrame, chartPoints: [chartPoints], viewGenerator: windDirectionViewGenerator, displayDelay: 0, delayBetweenItems: 0.05)

You can get the correct type if you set the type arguments correctly, e.g. https://github.com/i-schuetz/SwiftCharts/blob/master/Examples/Examples/CandleStickInteractiveExample.swift#L100
With this the index shouldn't be necessary, but just as info, you can get it with chartPointModel.index.

I just printed the value of ChartPoint and saw index - will build the bar chart using this library now. Sorry about that, should have looked on that object before hand.
Thank you.

I should then be able to do:
let index = chartPointModel.index
let wind = wind[index]

// Build image
// Build label and set with wind.speed

Yep. As I said you also can use a ChartPoint subclass (in case you aren't doing it yet) which contains your custom data, and if you set the type parameters correctly like in the candlestick line linked, retrieve it without having to use the index or casting.


Integrate API

Hey can someone help me to integrate the OPSkins.com API?
Or another good working API

There is some issue with some API configuration guide, don't be lazy just search .

https://github.com/ztizzlegaming/CSGOWinBig/issues/85
Im the one that created the tutorial, just ask if you got any questions

This is it ! :dancer:

@Stuffa1991
The GoogleAuthenticator.php is not longer available, can you post it again?
Or maybe you can create a new wiki page

+1 Would be Great!


How to change the colors displayed on the TwitterPicker by default

I want to customize several colors displayed on TwitterPicker.
How can I do it？

The available API is colors 。。。

This should be explained more clearly. Example:
// Set some default colours
const myColors = ['#000000', '#ffffc1']
// Pass myColors into the component
<TwitterPicker colors={myColors} color={ this.state.color } onChange={ this.handleChange } />


Missing images in Solvers documentation

Describe the issue
There are empty images in the solvers documentation found here: https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/README_Solver.html

Interesting...looks like it works in 2.3 but somehow broken in MRTK_dev?
https://microsoft.github.io/MixedRealityToolkit-Unity/version/releases/2.3.0/Documentation/README_Solver.html

The name of the png I think got changed up. There's actually a number of broken links images here even within our own docs.
We should fix this once and for all by adding a validation step for this so that we don't have to manually do this.

Note that we're also not consistent with how we use  vs ()[].
I tried using ()[] hoping that docfx would validate it but it unfortunately didn't quite work, so I think we'll have to roll our own.

Another possibility is to push something to docfx but I'm not sure what the turnaround is on a change there making it to their latest nuget feed, especially in light of the issue here: https://github.com/dotnet/docfx/issues/5536

Wait, I'm wrong.

It's a case sensitive/insensitive thing. It strikes again.


Windows binary

Dear Karl,
Could you be so kind to generate .exe for the rest of us who are mere Windows users w/o compiler?

Hi, @sergeevabc.  I think this is a duplicate of issue #30 -- please see my response there.


empty output_X_X.md|txt files

not sure why but just running given commands give blank output files

Whoops! didn't provide SECRET_KEY: <FILL IN> key!

I put in my key, but I'm having the same issue. There's supposed to be a space after the : right?


Advertize Kotlin modules as Scala ones via BSP

This PR makes Kotlin modules advertize themselves as Scala modules via BSP. This allows basic support for Kotlin modules in IntelliJ, where intellij-scala seems to handle them fine this way.

Includes https://github.com/com-lihaoyi/mill/pull/3608 for now

Should preserve bin compat, unlike https://github.com/com-lihaoyi/mill/pull/3619 and https://github.com/com-lihaoyi/mill/pull/3644

@lefou https://github.com/com-lihaoyi/mill/pull/3644 restricts that workaround to IntelliJ, and only so if it seems IntelliJ lacks explicit Kotlin support over BSP. But it requires changes that break binary compatibility in BspModule.

In a similiar fashion, I'd like to propose to add the synthetic root module only when we detect we're connected to IntelliJ (that one could be made without breaking bin compat).

Can you a bit more specific? How do you detect the missing support in IDEA and why can't it be binary compatible. Or if this was discussed before plz provide a pointer.

The whole BSP implementation is far from simple, so a bit of context and explanation helps a lot.

Can you a bit more specific? How do you detect the missing support in IDEA and why can't it be binary compatible. Or if this was discussed before plz provide a pointer.

Right now, BSP support in IntelliJ is provided by intellij-scala. Intellij-scala advertizes support only for Java and Scala in its InitializeBuildParams during BSP server initialization. Yet, in practice, it supports Kotlin sources in Scala modules, as I was able to check with this project. The PR here makes Kotlin works in IntelliJ by relying on this.
Yet, advertizing Kotlin modules as Scala ones doesn't allow to pass kotlinc arguments (and other Kotlin-specific details) to the BSP client. It seems Jetbrains is working on a better solution, with explicit support for Kotlin via BSP, in the intellij-bsp project (I mean, it's formerly called "intellij-bsp", it's now part of a bigger repo). Note that intellij-scala has its own BSP implementation, that differs from the one of intellij-bsp.
@jastice said in #3619 that intellij-bsp would probabaly be used mid-term by intellij-scala too.
So in #3644, we try to detect which IntelliJ BSP implementation we talk to, and advertize Kotlin modules either as Scala ones (for intellij-scala) or as Kotlin ones (for intellij-bsp). To detect which intellij BSP implementation we talk to, inspecting the BSP InitializeBuildParams seems to work: both implementation use Intellij-BSP as "display name", but they claim support for different language sets: only Java and Scala for intellij-scala, Java, Scala, Kotlin, and more for intellij-bsp.

About the binary compatibility issue, we need details of the client InitializeBuildParams (at least, "display name" and supported languages) in BspModule.{bspBuildTarget, bspBuildTargetData}. Passing those details to these methods breaks bin compat.

The idea with the PR here is to advertize Kotlin module as Scala ones via BSP, rather than Java ones as is currently the case (as KotlinModule doesn't currently override BspModule.{bspBuildTarget, bspBuildTargetData}). That seemed to be an acceptable short-term workaround to me, until the bin compat of BspModule can be broken.

Understood.
Regarding the detection logic. The data in BspModule isn't necessarily the one we need to send to the client. I think the server could simply translate it depending on its knowledge about the client. So we could be more BSP client specific without breaking BspModule.
Technically, I'd rather avoid investing into the current monolithic BSP implementation in favor of a more modular approach, but it's currently blocked by bsp4j not being leightweight enough, https://github.com/build-server-protocol/build-server-protocol/issues/668 / https://github.com/build-server-protocol/build-server-protocol/discussions/651.

I think KotlinModule should definitely override BspModule defs to reflect its nature. This shouldn't break any compatibility.
Please note, that KotlinModule is currently unfinished. Also, I'd expect a rather poor behavior in any BSP client, since compilation of Kotlin modules isn't incremental and takes very long compared to any other languages supported by Mill. Hence, the GenIdea approach is still the go-to solution for Kotlin projects. I can't say much more about it, since I haven't finished the review of all the changes introduced lately to Mill in depth. This also includes the synthetic BSP module you mentioned.

One last note: I can't recall if I checked whether Kotlin sources alongside a Java module (as should be the case currently without this PR) were fine in Intellij. I checked as Kotlin module as done in #3644 in the general case, and as a Scala one as done here. We should able to do #3644 without breaking bin compat if it works fine alongside a Java module, by changing the KotlinBuildTarget data to JvmBuildTarget in MillBuildServer itself, rather than from the BspModule methods overrides.

So is intelli-scala ignoring modules which support Kotlin as BSP language? Or only, or is just the Kotlin part not working, but they still work as Java modules?

This constant rebasing make the review process harder than necessary. I'm going to set this PR to draft mode until PR #3608 is merged.

This repeatedly rebasing makes the review process harder than necessary. I'm going to set this PR to draft mode until PR #3608 is merged.

The last commit is the only one specific to this PR. You can just look at this one. You'll have no diff between pushes, but that commit isn't that large.

What's the relationship between this and #3644? Does one depend on the other? Or are they unrelated?

#3644 includes the PR here. It adds things to it (it actually adds Kotlin-specific data in some BSP responses, to pass kotlinc arguments to clients in particular). It adds what intellij-bsp expects for Kotlin modules, although I wasn't able to use it in practice, and it breaks binary compatibility in order to detect which IntelliJ BSP implementation it's talking to.


find the existing files

Hello,
Is there any possible way to know what are the files that exists ? (name at least)

Its done using lfs_dir_read

if we don't know the file name,  how to know what are the files that exists?

you need to open the target directory that contains the files then you just read it using a while loop.
ret = lfs_dir_open(&lfs,&dir,"/");
do
{
lfs_dir_read(&lfs,&dir,&info);
if(info.name[0]!='.')
{
BSP_LCD_DisplayStringAtLine(i,(uint8_t*)info.name); /* Displaying the file names at line i */
i++;
}
}while(info.name[0]!='\0');
ret = lfs_dir_close(&lfs,&dir);

Thank you for the code provided very much, which helped me a lot!


"Data is not available for YHOO, please retry later."

When going to the demo URL ... I get no data feed from the APIs.... what am I doing wrong?
Thanks

Yea sorry bud, they nerfed that old python library due to scraping so they could charge for the data


Fix links and grammar and shit

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description
Updated some links in some pages + fixed up some grammar

The links are to the chatterino website so they can be changed after the fact. However since this commit again contains multiple changes at once I'll close it.


Change the call to RubyProf::CallTreePrinter#print

What is that about ❓
Addresses a bug: https://github.com/rails/rails-perftest/issues/38.
There is an open PR on the original project: https://github.com/rails/rails-perftest/pull/48
Details
The interface was changed by: https://github.com/ruby-prof/ruby-prof/commit/24a267bc7b50dc743930945acdaccfdca2417e94
This is a quick fix to address just this change.
If those keep arriving maybe would be better to map printer types to
their #print interface.

 (1) [Ruby 2.5.1] Cintrouter, PanelHub, FakeProvider, TolunaRouter

 (1) [Ruby 2.5.1] Cintrouter, PanelHub, FakeProvider, TolunaRouter


[Removal]: Amateur Lead Whale

Hotspot Name
Amateur Lead Whale
Hotspot b58 Address
112j8X7J3ZGEshtrjv7eiMjs7qga6aXf6a5pN56EPSxSYKsLbRrH
Discord Handle
Marco-polo#0495
Hotspot Manufacturer
Cotx
Removal Reason
Some-one just banned my wallet without any proof, we are telecom provider
Modifications
No
Extra forwarders
No
Extra antennas
Yes
Additional Information
External 6 dbi omni, 80m tower
Great site, but all telecom towers with good earning did end up the denylist.
So i have todo this 50+ times ?
More info via PM, discord.
Regards
A 500+ telecom tower owner.

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


Learn React Better

Build the home page to the specifications we laid out in class without the css for now. I will work on this over the next week once I get VS Code set up in class today. I will learn some React and TypeScript over this next week.

Similar to #8 and #25. I Will mark this as duplicate and close this (and assign everyone to #25)


Fix auto-complete not suggesting custom class names on identifiers

Fixes #69941
In 4.x, auto-complete will suggest custom classes only when completing types, not identifiers. This makes it auto-complete for identifiers as well, as this was the behavior in 3.x.

CC @anvilfolk

Thanks!


Remove unused result warning

Use the return value from write(2).
This prevents a warning when building with crypto-mdebug.
I'm not sure perror is the best thing to put in the body of the if statement but it shouldn't be executed normally.

The code in question isn't on the 1.1.0 stable branch that I can find.


Added proper license notificaton to ALL code files...

Hye I added the license notification to all the files :)

I'm sorry but we can't accept your pull-request for two reasons: first, it's not needed to put a copyright licence over all project files, it's enough just to add one file for the licence for all the project. The second reason is that you added tabulations in some files, ruining our indentation.


Added unified configs directory

This pull request fixes this issue: https://github.com/TKazer/CS2_External/issues/60 and makes configs folder identical for any user who will launch this modification.
C:\Users\User\Documents\TKazer

@TKazer can you approve this?

bro, it won't work properly

compare your code with this one

bro, it won't work properly

Actually it does work, it already was tested by thousands of users, the code you provided is bad and not usable

bro, it won't work properly

Actually it does work, it already was tested by thousands of users, the code you provided might not work for many users

Anything is possible, but you haven’t changed the path to search for configs, in any case, I didn’t read it carefully.

bro, it won't work properly

Actually it does work, it already was tested by thousands of users, the code you provided might not work for many users

Anything is possible, but you haven’t changed the path to search for configs, in any case, I didn’t read it carefully.

Because modification by default used current folder getter which I used in output after changing the folder


Performance degradation on high frame rate devices (IPhone 14 Pro) using the latest version of flutter master

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Very noticeable performance degradation on high frame rate devices (IPhone 14 Pro)  using the latest version of flutter master (Flutter version 3.14.0-14.0.pre.274) compared with flutter stable versions (this comparison was made with 3.13.0)

Download latest version of the master branch of Wonderous app
Download Flutter version 3.14.0-14.0.pre.274
Run Wonderous app using that Flutter version on a High-end iOS device (iPhone 14 pro - IOS 16.6.1) on profile mode
Open the Performance Tab of the Flutter Dev Tools

Expected results

[Screenshot 1]: Performance Tab of Flutter Dev Tools using Flutter version 3.13.0
Janks: 6
FPS average: 113
Actual results

[Screenshot 2]: Performance Tab of Flutter Dev Tools using Flutter version 3.14.0-14.0.pre.274
Janks: 305
FPS average: 93
Code sample
Code sample
https://github.com/gskinnerTeam/flutter-wonderous-app

Screenshots or Video

Screenshots / Video demonstration
https://github.com/flutter/flutter/assets/63058517/a19f36cb-e3fc-4f99-beb1-60ebece390c2
[Upload media here]

Logs
Logs
Launching lib/main.dart on Somnio’s iPhone in profile mode...
main.dart:1
Automatically signing iOS for device deployment using specified development team in Xcode project: 33P98UGP6U
Xcode build done. 14.0s
(lldb) warning: libobjc.A.dylib is being read from process memory. This indicates that LLDB could not find the on-disk shared cache for this device. This will likely reduce debugging performance.
The Dart VM Service was not discovered after 30 seconds. This is taking much longer than expected...
process interrupt
error: Failed to halt process: Halt timed out. State = running
* thread #1, stop reason = signal SIGSTOP
frame #0: 0x00000001c8635164 dyld`_dyld_debugger_notification
dyld`:
-> 0x1c8635164 <+0>: ret
dyld`dyld4::Atlas::Bitmap::Bitmap:
0x1c8635168 <+0>: pacibsp
0x1c863516c <+4>: sub sp, sp, #0x50
0x1c8635170 <+8>: stp x24, x23, [sp, #0x10]
Target 0: (Runner) stopped.
(lldb) 2023-09-14 17:39:45.068588-0300 Runner[800:108304] [VERBOSE-2:FlutterDarwinContextMetalImpeller.mm(42)] Using the Impeller rendering backend.
flutter: bootstrap start...
flutter: Navigate to: /
flutter: Saving...
flutter: Navigate to: /home
Connecting to VM Service at ws://<IP_ADDRESS>:51985/YyRBah2wsN4=/ws
flutter: Saving...
flutter: Navigate to: /wonder/greatWall?t=0

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 3.14.0-14.0.pre.274, on macOS 13.5.2 22G91 darwin-arm64 (Rosetta), locale en-UY)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] IntelliJ IDEA Community Edition (version 2023.2.1)
[✓] VS Code (version 1.82.1)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!

Unfortunately, this is expected due to a bug in iOS introduced in version 16.6. However, we've had reports that the issue is resolved in iOS 17. It would be valuable to know whether this reproduces after updating iOS to version 17.

I had the same problem.
Is solved?

Same issue here

Hi @zanderso, thanks for the feedback. We updated to IOS 17 and ran the same test again. There is definitely some improvement but still not great, compared with Flutter stable versions.

Flutter: Channel master, 3.14.0-14.0.pre.312
Janks: 96
AVG FPS: 111

FYI @jonahwilliams

That seems great? Most frames are in budget

Should we dup this against https://github.com/flutter/flutter/issues/134959 ?

We had to lock the last issue and so I'd rather not lead more users to commenting on what you should be a technical discussion

As far as we can tell, this issue was introduced in 16.6 and fixed in 17.0 on high refresh rate devices. De-duping against https://github.com/flutter/flutter/issues/134959 for just this one iOS version.


update changelog & add ut for rpc-service & fix bug for jenkins

Codecov Report

Merging #45 into release-rc2 will increase coverage by 9.72%.
The diff coverage is 33.33%.

@@                Coverage Diff                @@
##             release-rc2      #45      +/-   ##
=================================================
+ Coverage          25.15%   34.87%   +9.72%
- Complexity            50       77      +27
=================================================
  Files                 30       30
  Lines                497      496       -1
  Branches              22       22
=================================================
+ Hits                 125      173      +48
+ Misses               365      313      -52
- Partials               7       10       +3

Impacted Files
Coverage Δ
Complexity Δ

...m/webank/wecrosssdk/rpc/common/ResourceDetail.java
11.11% <ø> (+1.58%)
1.00 <0.00> (ø)

.../com/webank/wecrosssdk/rpc/service/Connection.java
64.28% <ø> (ø)
5.00 <0.00> (?)

...bank/wecrosssdk/rpc/service/WeCrossRPCService.java
10.98% <ø> (+8.79%)
3.00 <0.00> (+2.00)

...ava/com/webank/wecrosssdk/utils/KeyCertLoader.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...n/java/com/webank/wecrosssdk/rpc/common/Stubs.java
60.00% <33.33%> (+60.00%)
2.00 <1.00> (+2.00)

...java/com/webank/wecrosssdk/rpc/common/Receipt.java
31.57% <100.00%> (+14.91%)
4.00 <0.00> (+1.00)

...ain/java/com/webank/wecrosssdk/utils/RPCUtils.java
46.15% <0.00%> (+7.69%)
2.00% <0.00%> (+1.00%)

...ava/com/webank/wecrosssdk/rpc/methods/Request.java
74.07% <0.00%> (+33.33%)
9.00% <0.00%> (+6.00%)

... and 6 more

Continue to review full report at Codecov.

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


Examples do not contain WORKSPACE files

Lack of workspace files makes it difficult to copy the example directories and have them compile as is.

I'm still not convinced this is better for users, and I'm quite sure it makes it harder for us as maintainers. Deferring to after 1.0

One data point: My experience with examples in bazel repos is having a copy-paste-able WORKSPACE file makes it easier to get up and running. Otherwise it's necessary to have a fair amount of bazel knowledge to write the WORKSPACE file by hand. I have given up a few times trying to get rules_nodejs examples to work in the past because the WORKSPACE files were written for the rule developers & didn't work when copy pasted into a fresh git repo.
I can certainly see it being more work for maintainers.

We now include a fully functioning WORKSPACE snippet on every release notes and point there for "how to install", do you think that's sufficient?

It's not quite as user friendly because the casual user must know where to look to hunt down the right WORKSPACE snippet. I would also expect some examples to depend on libraries other than rules_ts, so the user would need to hunt those down.
I'm not sure what the easy-to-maintain solution is, but as a user I just want all of the files within an example directory to be able to be copied into a fresh git repo and built with bazel build //... && bazel test //....

I see, that's how it works in our https://github.com/aspect-build/bazel-examples repo.
I don't imagine individual test cases of ts_project being useful as a seed to start a new project, they're very small scope and you wouldn't get enough WORKSPACE content to expand from there to make something useful.

bzlmod with Bazel 6 should should make it much easier for users to get up and running. rules_js & rules_ts now both support bzlmod.

I can't imagine we'll ever find time to dig into whether we want to make a change, and then actually make it across all our rules repos.


Cannot assign null to property Webklex\PHPIMAP\Address::$host of type string

Describe the bug
Hello, @Webklex
I have a problem reading messages from an inbox where the email was sent only to bbc without a proper "To".
When it happens the email header comes with the information below, being an invalid email address:
To: "Undisclosed Recipients" <>

'To' parsed with 'Webklex\PHPIMAP\Message->parseRawHeader()':
'to' =>
    array (
      0 =>
      (object) array(
         'mailbox' => 'Undisclosed Recipients',
         'host' => 'UNKNOWN',
      ),
      1 =>
      (object) array(
         'mailbox' => 'UNEXPECTED_DATA_AFTER_ADDRESS',
         'host' => '.SYNTAX-ERROR.',
      ),
    ),

These errors are showing in my log:
Uncaught ErrorException: PHP Request Shutdown: Unexpected characters at end of address: <> (errflg=3) in Unknown:0

Cannot assign null to property Webklex\PHPIMAP\Address::$host of type string

Thank you.
Code to Reproduce
The troubling code section which produces the reported bug.
$query = $folder
                ->query()
                ->setFetchOrderDesc()
                ->limit(50);
 $messages = $query->get();

Desktop / Server (please complete the following information):

OS: MacOS
PHP: 8.2
Version 5.0.1
Provider Postfix Server

Additional context
Cannot assign null to property Webklex\PHPIMAP\Address::$host of type string
Level
CRITICAL
Code
0
File
/var/task/vendor/webklex/php-imap/src/Address.php
Line
43
Trace
#0 /var/task/vendor/webklex/php-imap/src/Header.php(603): Webklex\PHPIMAP\Address->__construct()
#1 /var/task/vendor/webklex/php-imap/src/Header.php(558): Webklex\PHPIMAP\Header->parseAddresses()
#2 /var/task/vendor/webklex/php-imap/src/Header.php(182): Webklex\PHPIMAP\Header->extractAddresses()
#3 /var/task/vendor/webklex/php-imap/src/Header.php(64): Webklex\PHPIMAP\Header->parse()
#4 /var/task/vendor/webklex/php-imap/src/Message.php(512): Webklex\PHPIMAP\Header->__construct()
#5 /var/task/vendor/webklex/php-imap/src/Message.php(286): Webklex\PHPIMAP\Message->parseRawHeader()
#6 /var/task/vendor/webklex/php-imap/src/Query/Query.php(277): Webklex\PHPIMAP\Message::make()
#7 /var/task/vendor/webklex/php-imap/src/Query/Query.php(353): Webklex\PHPIMAP\Query\Query->make()
#8 /var/task/vendor/webklex/php-imap/src/Query/Query.php(315): Webklex\PHPIMAP\Query\Query->populate()
#9 /var/task/vendor/webklex/php-imap/src/Query/Query.php(378): Webklex\PHPIMAP\Query\Query->curate_messages()
#10 /var/task/app/Services/ImapService.php(141): Webklex\PHPIMAP\Query\Query->get()

Hi @felipehertzer ,
thanks for the excellent report. Please update to v5.1 and give it another try.
The "PHP Notice:  PHP Request Shutdown: Unexpected characters at end of address: <> (errflg=3) in Unknown on line 0" however, will persist and is caused by this line:
https://github.com/Webklex/php-imap/blob/5.1.0/src/Header.php#L233
If you have an idea on how to make it stop, please feel welcome to push a pull request :)
Best regards,

Hi @Webklex, thank you for the fast reply, It is working now.
It seems that is only possible handle that errors with IMAP functions using the PHP functions:
imap_errors();
imap_alerts();

I will do some tests, if I can find other solution I will send a pull request.
Thank you.


Add Istituto Tecnico Tecnologico "Allievi-Sangallo"

Add Istituto Tecnico Tecnologico "Allievi-Sangallo"
url : https://www.ittterni.edu.it/
gsuite for edu : @ittterni.org

@rmam09 Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Tab completion not working, without running any gitlab-ci-local command beforehand

Probably a very nice-to-have feature/bug-fix.
But auto completion does not work, if you bump the tag reference of a include statement. You need to run a command such as gitlab-ci-local --list before tab completion begins to work again.
It would be nice if the auto completion script would pull the required dependencies if they were missing, when trying to auto complete.

How often should the "includes" be re-fetched when in "tab-completion" mode.
We can't do it on every tab, since it would delay the result display quiet a bit.

A perfect solution that is both always correct and fast, is probably not possible. But I still think we should extend the normal behaviour for tab to the initial tab also.
So I propose that the only time that the files are fetched in tab-completion mode, is when the files are not present.
The current behaviour of tab-completion could be argued to already be implemented this way, since files are never refetched in tab-completion mode. And this only add an initial fetch, and none refetches.


Wrong cursor icons in transform Control

I am using transformControl with rotation to transform a polygon. After rotation of polygon the cursor  over resize handler is displayed incorrect. e.g. Is shows possibility to resize up/down, but in fact it should be left/right. I think problem is that the cursor icon is assigned to the point, and it does not care whether point is on the left or on top (after rotation). Is should be improved somehow.
Here is screen:
http://img713.imageshack.us/img713/7716/resizebugol.png

fixed


Added module support

Coverage: 93.827% (-1.2%) from 95.04% when pulling c334137e71e0c098df4a52960c8bcc4a762a734f on module-support into d57cb862844dab38bb2d031fe2cf91ec2056bd11 on main.


Investigate listening on GCSRepository Secrets

If a user is connecting to a GCS Backup Repository, then they have to provide a secret that contains the GCS credentials as a file. We should investigate whether we need to restart the Solr Pod if this GCS credential is updated.
The gcs-repository implementation might re-load the credentials everytime it is used. If that's the case, then the Secrets should be auto-updated by kubernetes within the Pod, so we won't have to restart the Pods.
If the gcs-repository does not reload the credentials ever, then we will need to restart the Solr Pods to propagate the new credentials values. This can be done by setting a hash of the secret value as an annotation for the Pod. We do it for other secrets, we might just need to make the current logic more generic to accept more secrets.

Relates to #301

@gerlowskija , I think you know the gcs-repository code the best. Once you are back (don't want to interrupt your break), could you look into this and see whether the credentials are re-loaded throughout the solr lifecycle or just when the GCSRepository is used for the first time.


ImportError: No module named 'crunchyroll'

Hello,
I got error when trying to call script.
`
C:\Users\Matias\Desktop\anime_dl>python main.py -i "http://www.crunchyroll.com/i-cant-understand-what-my-husband-is-saying/episode-13-happy-days-678059" -u "XXX" -p "XXX"
Traceback (most recent call last):
File "main.py", line 8, in
from AnimeDL import *
File "C:\Users\Matias\Desktop\anime_dl\AnimeDL.py", line 8, in
import sites
File "C:\Users\Matias\Desktop\anime_dl\sites_init_.py", line 1, in
import crunchyroll
ImportError: No module named 'crunchyroll'
C:\Users\Matias\Desktop\anime_dl>pause
Presione una tecla para continuar . . .
`
`C:\Users\Matias>python
Python 3.4.0 (v3.4.0:04f714765c13, Mar 16 2014, 19:25:23) [MSC v.1600 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

`
Thanks

Please try with python 2, if possible. There seems to be this issue with python 3