text:
Support workaround for unusable J10S SWORD URLs

Currently JScholarship (J10S) returns SWORD Deposit Receipts containing URLs in the response body that cannot be resolved, in the form of http://dspace-prod.mse.jhu.edu:8080/swordv2/.....

The .mse.jhu.edu domain is not resolvable by the public Internet
Port 8080 is not available to the public Internet

However, J10S will answer to another form of http://dspace-prod.mse.jhu.edu... URLs: https://jscholarship.library.jhu.edu/swordv2/...:

The .library.jhu.edu domain is resolvable by the public Internet
Port 443 is available to the public Internet

This PR includes a "special" hack for J10S.  If an impotent SWORD Statement URI is observed in a  SWORD Deposit Receipt (i.e. matching http://dspace-prod.mse.jhu.edu:8080/swordv2/....), the public form of the URI will be used instead (i.e. https://jscholarship.library.jhu.edu/swordv2/...).
The real solution is to fix J10S, and have it advertise resolvable URLs, whatever they may be.  Until then, this hack is in place.
The following properties are baked in as defaults, but can be overridden at runtime if desired.

jscholarship.hack.sword.statement.uri-prefix=http://dspace-prod.mse.jhu.edu:8080/swordv2/
jscholarship.hack.sword.statement.uri-replacement=https://jscholarship.library.jhu.edu/swordv2/

unless the name has changed to something like JScholarshis, we should call it J10P ;-)

authors: emetsger jrmartino

repo: OA-PASS/nihms-submission


text:
Use authz 0.3.0

Overview

Updates fcrepo image to use new model-3.1 compatible User service
Update the authz listener image to use the latest authz code as well.
Updates the ldap and idp and sp images to provide uinque-ids

To test
There is no working ember image, so these are some steps you can do without Ember

Try the user service (as various users?).  Hit https://pass.local/pass-user-service/whoami and log in to shib as one of the various test users.   (note:  for the first time, the likes of staff2, a staff member with no grants, will be let in).  Look at the README.md for a full list of plausible users.

Try looking at submissions, and making them read-only.  They're read-only when submitted.   For example, nih-user has this incomplete submission as determined by the NIHMS etl: https://pass.local/fcrepo/rest/submissions/04/4c/0a/2e/044c0a2e-43fa-4611-889a-36fd7c104161.  Feel free to change this to a terminal state (submitted=true, or submissionStatus={submitted, needs-attention, complete}.    Reload after changing this, and the edit buttons should go away to indicate that it is read-only.

you can do this on the "Update Properties" panel on the side, using RDF.  Type in the triple you want to add and delete.  For example:

    DELETE { <> pass:submissionStatus "manuscript-required" }
    INSERT { <> pass:submissionStatus "needs-attention" }
    WHERE { }

Logged in to shib as one of the various test users, try creating a submissionEvent, and verifying that it is immutable.  The easiest way to do this is to point the browser to https://pass.local/fcrepo/rest/submissionEvents, then under "Create a New Child Resource"   Select "container" from the menu, and type in any name under "identifier".    Then add an rdf type in the text box before clicking add:

    <> a  <http://oapass.org/ns/pass#SubmissionEvent> .

It'll put you on that submission event's page.  Click reload, and make sure all the edit/update boxes are gone (indicating it is read-only)
Resolves OA-PASS/pass-authz#57

@birkland I was able to perform the suggested tests and they worked, but there is a quirk that I'm not sure what to make of.  When you first log in through the whoami link, if you then go directly in and start trying to access things in https://pass.local/fcrepo/rest/, you get 403 forbidden. After a few minutes it starts working as expected. I'm not sure what causes the delay. If you "log out" (I used incognito mode), and then log back in as the same user, the 403 errors are back. Here is a snippet of the log where the 403 happens and then is ultimately resolved after a few refreshes over several minutes - you can see the error that seems to be causing the 403.
authz-test-log.txt

Ooh, that URI is not good, it should never see https://pass.local.
Digging deeper, it looks like the root cause of this is the User resource sent back from the user service.  The id is tweaked to make the host match the value from the Host header, which makes sense.  The problem is that this value is cached, and makes no sense to the internal AuthRolesProvider when it retrieves it.  So a solution is to make a defensive copy of the User.  The problem is there is not a convenient way to do that.
Maybe a change to the client model to add a copy constructor, like:
User oldUser = getUser();
User copyOfUser = new User(oldUser);

?

@birkland I'm not sure I fully understand the issue, but just to repeat back the requirement - it would be to modify the java-fedora-client model to include a copy constructor for each model object in the form of:
public User (User user) {
  this.id=user.id;
  this.firstName = user.firstName;
  ...
}

I think this would be useful - there have been a number of times I could have used that, especially when writing tests. I already have a PR in for the client, I could do one for this as well if you like and then we could include it in the same release.

Yes, the addition of such a copy constructor would allow the necessary defensive copies to be made in pass-authz order to fix the issue on the authz issue.   Placing it in the client is best, as it guarantees the copy logic is kept up-to-date with model updates and tests.  So that would be an ideal solution.

source: gharchive/pull-request

authors: birkland karenhanson

repo: OA-PASS/pass-docker

license_type: permissive

license_source: github-api


text:
on /action - turn panels into buttons?

That will make us able to do the mouseover effect right? that would be nice.

Done. Dunno why it took so long....
It is not 100% on mobile. They are not resizing properly for some reason. But it seems to be working, more or less.

Closing, and opening a new issue

source: gharchive/issue

authors: JosephMcArthur mtb-za

repo: OAButton/odb

license: mit

license_source: bigquery


text:
Parameters for Media Types

Parameters for Media Types
Media Types can support parameters.  Yet, to work with them in OpenAPI, one must define them statically against each media type.  This has the unfortunate side effect of discouraging use of media type parameters by making them clumsy to manage within the API spec.
content:
  text/plain; charset=utf-8:
    ...
  text/plain; charset=iso-8859-1:
    ...

Without a way to express the parameter, it has little or no semantic value for OpenAPI.  Minor variations look like completely different media types.  There is little room for negotiation over content parameters unless the API author takes the time to spell out each supported parameter as its own type.
Media Type parameters could be useful in some obvious ways:

versioning of the media type
specifying a 'profile' for the media type as described in RFC6906
negotiating support for embedded resources (i.e. HAL (https://tools.ietf.org/html/draft-kelly-json-hal-08)) , hypermedia style, or level of completeness of a representation.

Private and vendor media types might better manage breaking changes by supporting multiple versions of representation without ever changing endpoints and methods.  Perhaps there could be benefits to QA and regression test tooling, being able to validate support for the diversity of representation styles in the API contract.  This could be had without having to iterate every parameter combination as a separate media type.
Examples
Versioning
Accept: application/vnd.example-schema+json; version=1.0.4

content:
  application/vnd.example-schema+json:
    parameters:
      version:
        type: string
        required: false
        description: |
          The version of the representation.
        default: 1.1.0
        enum:
          - 1.0.3
          - 1.0.4
          - 1.1.0
    schema:
    	$ref: "https://schemas.example.com/example"

Profile identification
Accept: application/vnd.example-schema+json; profile=https://schemas.example.com/example/profiles/bob

content:
  application/vnd.example-schema+json:
    parameters:
      profile:
        type: string
        required: false
        description: |
          The profile (rfc6906) for the representation.
        default: "https://schemas.example.com/example/profiles/alice"
        enum:
          - "https://schemas.example.com/example/profiles/alice"
          - "https://schemas.example.com/example/profiles/bob"
    schema:
    	$ref: "https://schemas.example.com/example"

Hypermedia style selection
Accept: application/vnd.example-schema+json; hypermedia=HAL

content:
  application/vnd.example-schema+json:
    parameters:
      hypermedia:
        type: string
        required: false
        description: |
          Hypermedia Style.  Indicates whether links and other supplemental
          resource detail are provided in the representation.
        default: JSON_HYPERSCHEMA
        enum:
          hypermedia:
            - NONE
            - HAL
            - JSON_HYPERSCHEMA
    schema:
    	$ref: "https://schemas.example.com/example"

Added after the original issue report
I am inspired by what I read on Roy Fielding's blog entry "REST APIs must be Hypertext Driven".

"A REST API should spend almost all of its descriptive effort in defining the media type(s) used for representing resources and driving application state, or in defining extended relation names and/or hypertext-enabled mark-up for existing standard media types. Any effort spent describing what methods to use on what URIs of interest should be entirely defined within the scope of the processing rules for a media type (and, in most cases, already defined by existing media types). [Failure here implies that out-of-band information is driving interaction instead of hypertext.]"

If I understand him correctly, enriching OpenAPI's ability to semantically express media type parameters would improve its ability to convey the kinds of interactions Mr. Fielding expected to be inherent in the resource or resource representation, rather than in other parts of the HTTP message.  Conversely, not supporting media type parameters might limit OpenAPI's ability to articulate a nuanced RESTful concept.

I'm right there with you on parameters and your examples for versioning and profile identification,  but I think the hypermedia selection stuff is non-standard and we don't want to add anything non-standard to OpenAPI thats going to live in the users actual API.
If we stick the a general mechanism for adding parameters to a media type, I think this could be a great idea. charset, version, etc are all good things to be able to describe as possible in an API.

Thanks Phil.
You're right, the hypermedia example is flawed.  I'm happy to remove it from the issue or provide other examples if it's helpful.

For consistency, if someone does take this to a PR, fields like type and enum should be wrapped within a standard schema field of type schemaObject.

Right. All of the examples need work.
The operation parameters field may be the best thing to compare for consistency.
Guessing at the changes that might be needed:

A new Media Type Parameter Object.  Or possibly a subset of the existing Parameters Object?
Add parameters to the Media Type Object whose type would be Map[Media Type Parameter Object | Reference Object].
JSON Schema updates.  Happy to propose these; would be looking for advice on norms for contributing to the project beyond issue contributions.

Revised Examples
Versioning
Accept: application/vnd.example-schema+json; version=1.0.4

content:
  application/vnd.example-schema+json:
    parameters:
      - name: version
         description:  Media type version for the representation.
         required: false
         deprecated: false
         schema:
           type: string
           default: 1.1.0
           enum:
             - 1.0.3
             - 1.0.4
             - 1.1.0
         examples:
           priorVersion:
             summary:  The most recent prior version.
             value: 1.0.4
           currentVersion:
             summary:  The current version.
             value: 1.1.0

or
content:
  application/vnd.example-schema+json:
    parameters:
      - $ref: "https://schemas.example.com/example/MediaTypeVersion"

Profile identification
Accept: application/vnd.example-schema+json; profile=https://schemas.example.com/example/profiles/bob

content:
  application/vnd.example-schema+json:
    parameters:
      - name: profile
       description: The profile (rfc6906) for the media type
       required: false
       deprecated: false
       schema:
         type: string
         default: "https://schemas.example.com/example/profiles/alice"
         enum:
           - "https://schemas.example.com/example/profiles/alice"
           - "https://schemas.example.com/example/profiles/bob"
        examples:
          BobProfile:
            summary:  The classic Bob profile we all know and love.
            value: "https://schemas.example.com/example/profiles/bob"
          AliceProfile:
            summary:  The new and improved.
            value: "https://schemas.example.com/example/profiles/alice"

Use of value, not externalValue, as the value is intended to be the URL string, not the profile schema to which the URL refers.  Interested if there are disagreements.
or
content:
  application/vnd.example-schema+json:
    parameters:
      - $ref: "https://schemas.example.com/example"

My initial reaction to Phil's tweet, was "OMG No!" .  The opaque media type identifier was by design.  However,  having read this issue and seeing the examples, I am warming up to the idea.
The parameters array is nice for enumerating the possible parameters and the providing the syntax.  I have to admit I can never remember the syntax of application/json;odata.metadata=full.
However, once we get into the territory of profile and version parameters, we get to a point where we almost need to be able to have different schemas and examples based on the parameter values.  What's the point of documenting profiles if you can't also document the shape that the profile identifies.   I'm not sure how you could add that cleanly.

Looking at non-structured media types may put parameters in a different light.
Drawing from the media type registration for PCMU audio.  I'm ignoring the fact that the registration assumed PCMU's use in RTP;  the same media type might be used to interact with stored audio prompts, songs, etc. via HTTP.
GET /songs/happy-birthday
Accept: audio/PCMU;rate=44100;channels=2;q=0.9, audio/PCMU;rate=8000;q=0.8, audio/*;q=0.5

content:
  audio/PCMU:
    parameters:
      - name: rate
        description: The bitrate for the audio
        required: true
        schema:
           type: string
           default: "8000"
           enum:
             - "6000"
             - "8000"
             - "11025"
             - "16000"
             - "22050"
             - "32000"
             - "44100"
             - "48000"
             - "64000"
             - "88200"
             - "96000"
             - "176400"
             - "192000"
      - name: channels
        description: The number of audio channels
        required: false
        schema:
          type: integer
          default: 1
          enum:
            - 1
            - 2

Benefit to API Author and Client Developer
To be realistic, I took the options in the bitrate enum come from Adobe Audition. With thirteen bitrate options and a mono/stereo option, OpenAPI 3.0 requires twenty-six independent media types to express the options. Not only is it inefficient, but it implicitly and wrongly suggests that the multiple media types are different. They are not.
On the client side, the cost of reducing the options into meaningful handling is higher than it ought to be. In this example, not being able to express this aspect of HTTP forces the author to either take on inefficiency or solve the same problem by other means. Query parameters are probably the next best option, but if the media type authors intended for clients to interact with the resource and representations using parameters, why force the API author to develop an alternative?
Addressing Examples
The examples question is interesting. Using the plural examples: object, one has the opportunity to name each example. There isn't explicit mapping (yet proposed). Authors have always had to question how far to go with examples. JSON already provides so much flexibility that documenting all permutations may be unrealistic. I'm not sure mapping the examples to parameters is a problem that must be solved; maybe OpenAPI already has what it needs for examples.
The Value of Versioning
Versioning and profiles are just examples. It may not even be good practice to version some media types; I've seen commentary in this direction. But having versioning could enable organizations offering SLA-supported API products to gracefully revise their APIs' private media types and schemas without changing the API structurally. In this case, media type parameters would enable client developers to step through schema updates gracefully, selecting the supported earlier representation while being informed of updates.
I hope we can improve OpenAPI's semantic support for Content Negotiation, one of HTTP's most powerful features. Best practices for defining media types will continue to evolve, and our examples are probably just scratching the surface.  Looking back to Roy Fielding's statement on media types, I believe this is consistent with his intent.

authors: MikeRalphson cjaccino darrelmiller philsturgeon

repo: OAI/OpenAPI-Specification


text:
Agenda for September 28th, 2022

Remembering what we do

Minutes of Meeting:
Attending:
David O'Neill
Nick Denny
Andrew Brown
Stu Waldron
Frank Kilcommins
Shai Sachs

initial review of where we were up to after summer recess

housekeeping discussion - David O'Neill will be stepping back as champion with Andrew Brown stepping up

ACTION: Frank to onboard Andrew + Shai with access to the services they need

Next steps agreed:
a) Meeting October 12 to be for a review of the current spec and identify gaps and holes and assign actions for filling them - FK to undertake some housekeeping on TBD items and other gaps
b) Post review - goal to define some sample YAML of it's use - DON will interact with openID connect providers for example
c) Feedback to go into spec
d) take spec at that point to TSC for review

there being no other items, the meeting was adjourned.

authors: davidapimetrics ndenny

repo: OAI/sig-workflows


text:
ubuntu 16.04 下编译出错：Tengine-Convert-Tools/tools/oneflow/oneflow/core/actor/act_event.pb.cc: No such file or directory

尝试在ubuntu 16.04下编译时报错：
Tengine-Convert-Tools/tools/oneflow/oneflow/core/actor/act_event.pb.cc: No such file or directory
cmake版本：3.11.1
protobuf版本:3.14.0
报错截图：

可以通过添加编译选项 cmake -DBUILD_ONEFLOW_SERIALIZER=OFF .. 暂时关闭再试试。

repo: OAID/Tengine-Convert-Tools


text:
num_MSA_sequences

Does num_MSA_sequences affect the final result? I retrained proteinnpt on assay IF1_ECOLI_Kelsic_2016 with msat, but got spearman 0.614.

Hi @ZhummCrow -- num_MSA_sequences (default 384) will have an impact on the embeddings obtained for each sequence -- it corresponds to the number of sequence sampled from the MSA that is input in MSA Transformer. We use the default MSA Transformer hyperparameter values here. If not running into GPU mem bottlenecks, you may be able to get higher performance by increasing that value to a larger value.
Also note that the final performance you obtain (eg., 0.614 spearman) will vary significantly dependently depending on the particular cross validation scheme you are looking at (eg., random, modulo, contiguous).
Best,
Pascal

Ho @ZhummCrow -- closing this issue as I believe the above addressed your question. Feel free to re-open as needed.
Kind regards,
Pascal

authors: ZhummCrow pascalnotin

repo: OATML-Markslab/ProteinNPT

license: MIT


text:
Complete the Lesson: 'Ontology: Fundamentals' https://oboacademy.github.io/obook/lesson/ontology-fundamentals/

Some items in the “Learning objectives” section are not discussed in the "Preparation" section or elsewhere:

OWL ontology serializations ("formats")
What is a module?
Extraction methods: MIREOT vs. SLME

The OpenHPI course indicated Week 5: Ontology Engineering videos 5.1, 5.2, and 5.4 - 5.6, describe in general, the strategies and methodologies for ontology engineering. Nothing is mentioned about the 3 items above.
Many thanks for the great materials in these OBO books
https://orcid.org/0000-0002-0819-0473

@matentzn At the moment I am just a beginner in the subject, so I prefer not to make myself the modifications. I contacted @nicolevasilevsky about this issue and she may be interested in completing the lacking information. Thank you for the great material!

to do: for OWL ontology serializations ("formats"), point to https://oboacademy.github.io/obook/reference/formatting-license/

authors: nicolevasilevsky paulacalipho

repo: OBOAcademy/obook


text:
Add old functionality back

Here is a curated list of functionality that should be present in the first release of the installer API

[x] partitioning
[x] formatting
[x] fstab
[x] installing base system
[x] chrooting into base system
[x] configuring root
[x] setting up a user
[x] configuring packages for the user
[x] supporting custom packages

Additional info
*All drives should be detected.

Partitions of a drive should be found
Exisiting boot partitions should be found
LUKS should be a possibility
Custom software should be easily installable
Default values for settings should be clear and easy.

All of the checks are completed. Thus this issue is now resolved

repo: ODEX-TOS/tos-installer-backend


text:
使用否定词去搜索的话结果有问题

在这个体验页面，搜索“戴眼镜的猫”与“没戴眼镜的猫”结果出来的都是戴眼镜的猫。这个问题可以解决吗？

您好，这个确实是一类需要优化的问题，我们也会考虑如何进行否定词query的效果优化。如果有一些正负例的样本，是否finetune一下能够提升一些效果呢？

在自己的公司的业务上做了测试，发现的这个问题。
然后试了一下你们的DEMO，也是存在这样的问题。

这个问题会考虑解决吗？

请问这个问题有好的解决办法吗@starinskycc

authors: starinskycc xuboot yangapku

repo: OFA-Sys/Chinese-CLIP


text:
There's similar work here, open-source code, data, models, and it's two months ahead.

https://github.com/Minami-su/character_AI_open

Looks good. Cant wait for your latest progress.

authors: Lukeming-tsinghua Minami-su

repo: OFA-Sys/Ditto


text:
Overhaul mango examples

simple_agent.py and tcp_container_example.py have become quite dated and should be updated.

with #106

repo: OFFIS-DAI/mango


text:
fix: Preserve the viewportId values

Context
Try to be consistent in teh usage of viewportId, re-using the id's whenever possible.
Changes & Results
Assign gridId instead of viewportId for the unique location specific viewport identifier, and generate a simple viewportId if none is provided, but prefer using the one provided.
Testing
Change layouts, hanging protocols, double click, test various layouts to see if a display set fails to render, or if it is possible to cause exceptions on the viewports by repeating viewportId.
Create a hanging protocol which specifies viewportId, and test that those viewportId's are used.
Create a stage of that HP that just reorganizes the viewports, leaving the viewportId's
a) Unchanged by position
b) Moved to the new position that matches
c) Re-used for entirely different series.
Checklist
PR

[] My Pull Request title is descriptive, accurate and follows the
semantic-release format and guidelines.

Code

[] My code has been well-documented (function documentation, inline comments,
etc.)

Public Documentation Updates

[] The documentation page has been updated as necessary for any public API
additions or removals.

Tested Environment

[] "OS:
[] "Node version:
[] "Browser:

I found this issue...

Launch study StudyInstanceUIDs=1.3.6.1.4.1.25403.345050719074.3824.20170125095722.1
Switch to 1x2 layout (i.e. 1 row, 2 columns)
Double click the top-left viewport to one up.
Double click back to 1x2.
Double click the top-right viewport to one up.
Swap in the first series (i.e. the one that was in the top-left viewport when in 1x2).
Double click back to 1x2 layout.
Notice that the top-left viewport is now blank but should not be and both viewports should show the same series.

https://user-images.githubusercontent.com/109477394/233479964-a0673047-6475-47f7-8d1a-fb3d9ca8f0fb.mp4

I found another significant issue...

Launch OHIF with a study with two or more reconstructable series.
Swap in one of the reconstructable series.
Launch MPR.
Double click one of the orientations to one-up.
Swap in a different reconstructable series.
Double click to exit one-up.
The same orientation is displayed in each viewport and should not be.

https://user-images.githubusercontent.com/109477394/234083507-1a96d7ff-3169-4c3e-b5c6-b2a54cfb5f93.mp4

Yet another, I am sorry to say...

Launch in TMTV mode.
Double click the middle/center viewport to one up.
Double click back.
The series ALL changed to sagittal.

https://user-images.githubusercontent.com/109477394/234084960-9d9b7f9b-f69e-47c2-9416-358a96d1a8f2.mp4

When exiting MPR via a click to the MPR toggle button, the view should be returned to that which existed prior to launching MPR. Here is one scenario where it does not.

Switch the grid layout to something other than 1x1.
Double click a reconstructable series to 1x1.
Launch MPR.
Toggle MPR off.
The series should be the one from step 2, but is not.

Double clicking with crosshairs turned causes the following exception...
\dev\cornerstone3D-beta\packages\tools\src\tools\CrosshairsTool.ts:1660 Uncaught TypeError: Cannot read properties of undefined (reading 'id')
    at C:\dev\cornerstone3D-beta\packages\tools\src\tools\CrosshairsTool.ts:1660:1
    at Array.filter (<anonymous>)
    at CrosshairsTool._filterAnnotationsByUniqueViewportOrientations (C:\dev\cornerstone3D-beta\packages\tools\src\tools\CrosshairsTool.ts:1656:1)
    at CrosshairsTool.renderAnnotation (C:\dev\cornerstone3D-beta\packages\tools\src\tools\CrosshairsTool.ts:783:1)
    at handleDrawSvg (C:\dev\cornerstone3D-beta\packages\tools\src\utilities\triggerAnnotationRender.ts:188:1)
    at Array.forEach (<anonymous>)
    at C:\dev\cornerstone3D-beta\packages\tools\src\utilities\triggerAnnotationRender.ts:202:1
    at draw (C:\dev\cornerstone3D-beta\packages\tools\src\drawingSvg\draw.ts:10:1)
    at AnnotationRenderingEngine._triggerRender (C:\dev\cornerstone3D-beta\packages\tools\src\utilities\triggerAnnotationRender.ts:184:1)
    at AnnotationRenderingEngine._renderFlaggedViewports (C:\dev\cornerstone3D-beta\packages\tools\src\utilities\triggerAnnotationRender.ts:93:1)
(

Be mindful of this issue https://github.com/OHIF/Viewers/issues/3340 which I believe is not related to the viewport id fix.

Switching layouts does not preserve stack navigation position.

Switch to 2x2 layout
Navigate one of the stacks on screen.
Switch to 3x3 layout.
The stack navigated has been reset to the first image of the stack.

There are e2e tests failing.

I am still able to reproduce the following issues that were previously documented in this PR...

https://github.com/OHIF/Viewers/pull/3333#issuecomment-1523404817

The same steps reproduce the problem, and notice that the viewport navigated is correct, but other viewports navigated too

https://github.com/OHIF/Viewers/pull/3333#issuecomment-1523398749

The same steps reproduce the problem.
Note that there is perhaps a related issue  #3340 that is NOT related to the viewport ID changes, but I what I logged here MIGHT considering it does NOT occur in v3-stable

https://github.com/OHIF/Viewers/pull/3333#issuecomment-1520641356

Perform the steps and things appear fine, but then double clicking the top-left viewport to enter one-up and double clicking again to exit results in blank viewports

I found this issue related to tracked measurements...

Go to https://deploy-preview-3333--ohif-platform-viewer.netlify.app/viewer?StudyInstanceUIDs=1.3.6.1.4.1.14519.5.2.1.7311.5101.158323547117540061132729905711
Double click to view the SR and answer yes to tracking the measurements when prompted.
Switch to 1x3 layout
Drag in the second series to the middle viewport.
Use the measurement nav arrows (i.e. <>) to navigate to a markup.
Click MPR. The resulting view is NOT MPR.

There are just too many issues with this PR right now to think that it is likely to get fixed in teh short term.

I"m reopening this for further investigation

I have a fix i will open another PR

authors: jbocce sedghi wayfarer3130

repo: OHIF/Viewers


text:
Add ClearML logger

reference: https://github.com/OML-Team/open-metric-learning/issues/509

Hi. I'm working on it.

@Fissium great!

authors: AlekseySh Fissium

repo: OML-Team/open-metric-learning


text:
Update eng_wales_pre_process.py

scripts fails if the the folder is not present already, therefore this will help create the folder if it does not exist
Pull Request submission
the folder is expected to be present but if its not the scripts fails, hence this patch will take care of the folder

Not required


text:
Improve performance

Motivation and Context
The performance of the action creation based on action plans and action rules, was very bad. The Action Service placed a very heavy CPU and database demands on the infrastructure for a 24 hour period around the time of the action 'trigger', which was completely unnecessary - it wasn't needed to continuously retrieve massive amounts of case data, when we had no intention of acting on it.
The complexity of action rules, action plans, action jobs and cases with a individual action plan start and end dates, was totally over-engineered for a simple requirement, which is to be able to create actions for cases at a specific date and time.
What has changed
This refactoring simplifies the logic and improves the performance by doing the work once and once only, on the specific date and time specified by the action rule - the trigger - and then does not do the work again.
The cases which are 'in-scope' at the time the action was specified to take effect, are the ones which are executed. These cases - 300,000 or more - are rapidly processed using a stream of data from the database and vastly simplified logic.
How to test?
Load a large sample and watch the messages get sent to the ActionExporter Printer queue.
Links
Trello: https://trello.com/c/qXyBliYL/615-increase-performance-of-action-creation

 Increase performance of action creation

Made unverified commits by accident so created another branch

repo: ONSdigital/census-rm-action-service


text:
fieldset__legend markup and margin still shows even when not used in macro

fieldset__legend markup and margin still shows even when not used in macro
Originally posted by @jrbarnes9 in https://github.com/ONSdigital/design-system/discussions/56#discussioncomment-234593

Legend param needs to be provided for radios

Legend param needs to be provided for radios

I think we should make this a condition, so radios won't render is a legend hasn't been set, unless they're using dontWrap. Otherwise this won't stop happening.

repo: ONSdigital/design-system


text:
Allow Autosuggest to alternatively use a json 'blob' instead of external file

Currently it appears that you can only use an 'external' json file for the autosuggest 'list'.
Could this be enhanced to allow it to alternatively use a json 'blob' instead? This would allow for the option to dynamically build the autosuggest list from dynamic query data, ie if the UI running the DS received a dynamic set of data about different surveys, the autosuggest should be able to receive a json blob containing the different surveys in the dynamic data, rather than being forced to have a predetermined json file.
Whilst it could be possible to generate a dynamic json output at a fixed url, it would be easier to be able to pass the json directly to the autosuggest component
Originally posted by @Paul-Joel in https://github.com/ONSdigital/design-system/discussions/894#discussioncomment-2969266

Is this definitely still needed?

Spoke with Paul regarding this, who mentioned it would be a nice to have but can't remember specific circumstances. Agreed as team this is low priority as autosuggest component working as suggested with current implementation. Adding low priority tag.

authors: jrbarnes9 willcAND yatesn


text:
Typeahead examples not working

Describe the bug
Examples not working
Console errors cause by blocking of fetch due to CORS policy.

Access to fetch at 'https://ons-typeahead-prototypes.herokuapp.com/country-of-birth?query=fr&lang=en' from origin 'https://ons-design-system.netlify.com' 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.

To Reproduce
Steps to reproduce the behavior:

Go to https://ons-design-system.netlify.com/components/typeahead/examples/country-of-birth/
Click on the input field and start entering a country name
See error listed in console.

Expected behavior
On typing in the input field suggested matches are returned as a selectable list
Desktop (please complete the following information):

OS: All
Browser (e.g. chrome, safari) - not browser dependant
Version (e.g. 22) n/a

No longer an issue

authors: armstrongb rmccar


text:
Fix button icon colour

What is the context of this PR?
This PR is to fix the problem with icons when added to buttons always being black.

It also reduces the whitespace around button text in the HTML and fixes an error in the button param docs
How to review
Add icons to regular and secondary buttons and make sure they are the correct colour

 Fix button icon colour


text:
Update the browser support list to match GDS

Remove test for browsers we no longer support
Update browserlist for autoprefixer and webpack

 Update browser support list to reflect GDS

We need to upgrade our browserstack plan to automate mobile before this can be merged


text:
fix mobilenumber input type width

What is the context of this PR?
The mobilenumber type input field is only wide enough for 8 characters so will not fit a full mobile number especially if you suffix it with "+44". This will up the width to 15
How to review

Open test_multiple_answers schema
Enter "+44 0000 000000" into the mobile number field and see that the mobile number field is now wide enough for a full mobile number

Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

 Mobilenumber input type not wide enough for full mobile number

Was it like this in census 🤔

I don't think so, I did some work on the DS a while ago to make the width value match up with the number of characters you expect in the input which is why this is now wrong but I think that was after census

repo: ONSdigital/eq-questionnaire-runner


text:
Census: When 'No' is selected for first 2 questions and 0 visitors then the navigation is not correct

Expected behaviour
Must directly take you to confirm Number of visitors page?
Actual behaviour
Taking the user to Question.5 Does your household own or rent this accommodation
Steps to reproduce the behaviour
Launch a Census Survey from RH
Answer 'No' for Question 1 Does anyone live here?
Answer 'No' for Question 1a is there anyone else who live here?
Answer '0' for Number of visitors
Answer Household questions till question 4 and click save and continue.
Technical information
Browser
All
Browser
Operating System
Screenshot

Defect passed retest

repo: ONSdigital/eq-survey-runner


text:
Cannot install or build fpga driver, error: ‘struct erase_info’ has no member named

Hello,
I am trying to follow the installation guide.
But I am stuck at the very beginning when installing the drivers, it fails with the same error with the .deb package or when building it from sources:
The machine is a debian 10 (buster)
$ sudo dpkg -i ~/Downloads/opae-intel-fpga-driver-1.3.0-2.x86_64.deb
(Reading database ... 60161 files and directories currently installed.)
Preparing to unpack .../opae-intel-fpga-driver-1.3.0-2.x86_64.deb ...
-e
-e Uninstall of intel-fpga module (version 1.3.0-2) beginning:

------------------------------
Deleting module version: 1.3.0-2
completely from the DKMS tree.
------------------------------
Done.
-e Force regeneration of new initramfs
/var/lib/dpkg/info/opae-intel-fpga-driver.prerm: 16: /var/lib/dpkg/info/opae-intel-fpga-driver.prerm: dracut: not found
Unpacking opae-intel-fpga-driver (1.3.0-2) over (1.3.0-2) ...
Setting up opae-intel-fpga-driver (1.3.0-2) ...
Add module source to dkms

Creating symlink /var/lib/dkms/intel-fpga/1.3.0-2/source ->
                 /usr/src/intel-fpga-1.3.0-2

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j48 KERNELRELEASE=4.19.0-6-amd64 KERNELDIR=/lib/modules/4.19.0-6-amd64/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.19.0-6-amd64 (x86_64)
Consult /var/lib/dkms/intel-fpga/1.3.0-2/build/make.log for more information.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j48 KERNELRELEASE=4.19.0-6-amd64 KERNELDIR=/lib/modules/4.19.0-6-amd64/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.19.0-6-amd64 (x86_64)
Consult /var/lib/dkms/intel-fpga/1.3.0-2/build/make.log for more information.
$ cat /var/lib/dkms/intel-fpga/1.3.0-2/build/make.log
DKMS make.log for intel-fpga-1.3.0-2 for kernel 4.19.0-6-amd64 (x86_64)
Fri 15 Nov 2019 02:26:31 PM CET
make -C /lib/modules/4.19.0-6-amd64/build M=/var/lib/dkms/intel-fpga/1.3.0-2/build modules
make[1]: Entering directory '/usr/src/linux-headers-4.19.0-6-amd64'
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/altera-asmip2.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/misc/avmmi-bmc.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/fpga-mgr.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/uuid_mod.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/pcie.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/pcie_check.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/feature-dev.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/fme-pr.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/fme-iperf.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/fme-dperf.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/fme-error.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/fme-main.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/backport.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/afu.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/region.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/dma-region.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/afu-error.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/afu-check.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/intel-fpga-pac-hssi.o
  CC [M]  /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/fpga/intel/intel-fpga-pac-iopll.o
/var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.c: In function ‘mtd_erase_callback’:
/var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.c:55:11: error: ‘struct erase_info’ has no member named ‘mtd’
  if (instr->mtd->_erase == part_erase) {
           ^~
/var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.c:56:37: error: ‘struct erase_info’ has no member named ‘mtd’
   struct mtd_part *part = PART(instr->mtd);
                                     ^~
/var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.c:36:39: note: in definition of macro ‘PART’
 #define PART(x)  ((struct mtd_part *)(x))
                                       ^
/var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.c:62:11: error: ‘struct erase_info’ has no member named ‘callback’
  if (instr->callback)
           ^~
/var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.c:63:8: error: ‘struct erase_info’ has no member named ‘callback’
   instr->callback(instr);
        ^~
/var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.c: In function ‘spi_nor_erase’:
/var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.c:589:7: error: ‘struct erase_info’ has no member named ‘state’
  instr->state = ret ? MTD_ERASE_FAILED : MTD_ERASE_DONE;
       ^~
/var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.c:589:23: error: ‘MTD_ERASE_FAILED’ undeclared (first use in this function); did you mean ‘MTD_WRITEABLE’?
  instr->state = ret ? MTD_ERASE_FAILED : MTD_ERASE_DONE;
                       ^~~~~~~~~~~~~~~~
                       MTD_WRITEABLE
/var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.c:589:23: note: each undeclared identifier is reported only once for each function it appears in
/var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.c:589:42: error: ‘MTD_ERASE_DONE’ undeclared (first use in this function); did you mean ‘DL_STATE_NONE’?
  instr->state = ret ? MTD_ERASE_FAILED : MTD_ERASE_DONE;
                                          ^~~~~~~~~~~~~~
                                          DL_STATE_NONE
make[4]: *** [/usr/src/linux-headers-4.19.0-6-common/scripts/Makefile.build:309: /var/lib/dkms/intel-fpga/1.3.0-2/build/drivers/mtd/spi-nor/spi-nor.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [/usr/src/linux-headers-4.19.0-6-common/Makefile:1534: _module_/var/lib/dkms/intel-fpga/1.3.0-2/build] Error 2
make[2]: *** [Makefile:146: sub-make] Error 2
make[1]: *** [Makefile:8: all] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.19.0-6-amd64'
make: *** [Makefile:53: all] Error 2

Does anyone knows how to fix this ?
Best regards,

Hello, we are sorry that you are running into trouble building the drivers.  Unfortunately, for release 1.3.0, only kernel versions 3.10 and 4.7 are officially tested/supported.  Support for more recent kernel versions requires some amount of porting effort.

The spi-nor source was taken directly from the 4.12 kernel. It is being carried in the installation package because the spi-nor module is not included in the 3.10 kernel. Try removing this module from your build - it should already be there in the 4.19 kernel.

Hi, I did not try to remove this module from build, but I saw that the new release  https://github.com/OPAE/opae-sdk/releases/tag/1.4.0-1 adds support to the "community 4.19 LTS kernels" hence with this release there is no issue installing the driver package.
Thank you @tswhison & @rweight for your help.

authors: rweight thierryfischer tswhison

repo: OPAE/opae-sdk


text:
DocsArchive-15.0.0.0Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_38a26a18-ca41-4c96-ac62-5ae27695add8/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_38a26a18-ca41-4c96-ac62-5ae27695add8.git

Docs Build status updates of commit 4001abf:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-06-10-08-16-22 has been deleted or has been force pushed

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


text:
DocsArchive-15.0.0.0Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/984 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit 6fa10e6:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

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


text:
DocsArchive-1.0.0.0Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/3 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 0359c39:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

archvieSourceFolder/TOC.yml
:white_check_mark:Succeeded

archvieSourceFolder/content/someContent.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

authors: VSC-Service-Account v-alji


text:
[Feat]: CI yml file

What feature?
Smooth flow of the update in the project
Show us the magic with screenshots
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

@Vaishnavi-Patil2211 please assign me

repo: OSCode-Community/OSCodeCommunitySite


text:
SLIM-1443 Deletes result type from findEvents

SLIM-1443

All is well.

repo: OSGP/Shared


text:
CI: put build.gradle in the workflow

This make project root clean.
Signed-off-by: Hiroshi Miura miurahr@linux.com

@miurahr
私の方、Java関係は知見が乏しいですが、差分を見る限り、マージして問題ないように思いました。

@miurahr
私の方、Java関係は知見が乏しいですが、差分を見る限り、マージして問題ないように思いました。

マージしました。これで、プロジェクトのルートフォルダに、java関係がなくなったので、すっきりしました。

マージしました。これで、プロジェクトのルートフォルダに、java関係がなくなったので、すっきりしました。

authors: miurahr sanak

repo: OSGeo-jp/OSGeoLive-doc-omegat


text:
How can I index the previous timestep's latitude and longitude

I am trying to write an unbeaching kernel that will essentially "bounce" a particle back to it's previous position then advect it using a different (alongshore) velocity field. Is there a way to index the previous longitude and latitude so I can reset the coordinates?
particle.lon = #index previous longitude here
particle.lat = #index previous latitude here
I've been playing with indexing U and V using xi, yi, zi, and ti, but there doesn't seem to be a way to find a straightforward way to index coordinates inside a kernel.

Hi @hkhirsh,
If you create a subclass of a JITParticle or ScipyParticle like in In[26] of this tutorial, you can add a Variable like prev_lat and prev_lon:
class UnbeachingParticle(JITParticle):
    prev_lat = Variable('prev_lat', initial=0., to_write=False)
    prev_lon = Variable('prev_lon', initial=0., to_write=False)

You can then store the coordinates before advecting in a kernel using
particle.prev_lat = particle.lat
particle.prev_lon = particle.lon

The array of particle variables is created after the simulation by combining the output written at different timesteps and therefore not available within the simulation.
Does this answer your question?

Hi @reint-fischer,
Thank you! I think this did answer my question. I was able to store the coordinates in my advection kernel (before advecting) then call on them in a "bounce" kernel in order to send particles back to their previous position.
It seems I have another unbeaching issue now. I can tell that the "bounce" and "unbeaching" kernels are working because I no longer have particles stuck in the middle of my landmass (Guam) or passing over/through the landmass entirely. But it looks like particles build up on the landward side of the outermost "land" cells. This doesn't make sense to me because my beaching detection kernel should be recognizing those positions as zero velocity and tagging the particles to bounce back out.

My kernel logic is as follows:

Advection (any non-beached particle advects for one timestep)
Diffusion (any particle that has advected now diffuses)
BeachTesting (identified beached particles if u=0.00 and v=0.00)
Bounce (beached particles are returned to their previous coordinates)
UnbeachAlongshore (particles that were bounced now advect using a new velocity field where I have modified the cells closest to land so that particles advect with a longshore current. Basically if the particles are close enough to land to beach with the original velocity field then I replace the original advection with a new advection step that uses a velocity field that redirects particles alongshore).

I'm new to both Python and OceanParcels, so I apologize if I'm missing something really straightforward!
Thank you for your help with the "bounce" to the previous coordinates!

From the figure you show, I think it has to do with testing when the particle is on land. Whether you're on land is now tested using u=0 and v=0, but depending on your type of Arakawa grid, the interpolation may cause velocities to be nonzero even when you're already on land. You could try to construct a new 2D stationary field corresponding to a land mask. If you then use nearest-neighbor interpolation specifically on that land mask field, you will have a more accurate test of whether you're on land. When adding a field, you can individually pass an interp_method argument and set that to nearest for your mask.

I agree with @reint-fischer here - recently created a script for some training data for my MSc student where I needed to skip-out the on-land particles, and the most robust coming out was the particle.prev_lat <-> particle.lat and particle.prev_lon <-> particle.lon check.
"""
class TemporalParticles_JIT(JITParticle):
valid = Variable('valid', dtype=np.int32, initial=-1, to_write=True)
age = Variable('age', dtype=np.float64, initial=0.0, to_write=True)
pre_lon = Variable('pre_lon', dtype=np.float32, initial=0., to_write=False)
pre_lat = Variable('pre_lat', dtype=np.float32, initial=0., to_write=False)
class TemporalParticles_SciPy(ScipyParticle):
valid = Variable('valid', dtype=np.int32, initial=-1, to_write=True)
age = Variable('age', dtype=np.float64, initial=0.0, to_write=True)
pre_lon = Variable('pre_lon', dtype=np.float32, initial=0., to_write=False)
pre_lat = Variable('pre_lat', dtype=np.float32, initial=0., to_write=False)
def TemporalAging(particle, fieldset, time):
if particle.state == StateCode.Evaluate:
particle.age = particle.age + math.fabs(particle.dt)
def validate(particle, fieldset, time):
if particle.valid < 0:
particle.pre_lon = particle.lon
particle.pre_lat = particle.lat
if (math.isnan(particle.time) == True):
particle.valid = 0
else:
particle.valid = 1
else:
if ((particle.lon == particle.pre_lon) and (particle.lat == particle.pre_lat)):
particle.valid = 0
else:
if(math.isnan(particle.time) == True):
particle.valid = 0
else:
particle.valid = 1
particle.pre_lon = particle.lon
particle.pre_lat = particle.lat
"""
That's the actual function I used.
@daanreijnders (u==0, v==0) may also work, but it's really hard to track what xarray does or how it converts the fill value in the file to array values in the numpy array accessed by Parcels. As long as that conversion is not clear to me, I'd personally refrain from assuming (u==0, v==0) on land.

authors: CKehl daanreijnders hkhirsh reint-fischer

repo: OceanParcels/parcels


text:
Request to yuml.me fails

Hi,
Good day.
Request to yuml.me site to generate chart fails.
Regards.

@jarrettj send a patch: it is very likely that the yuml.me format changed.

authors: Ocramius jarrettj

repo: Ocramius/OcraServiceManager


text:
Dragging the floating player should not toggle Play state

Drag the floating player ... every time we release, the Play state toggles.

Upgrading to 7.15.4 was the culprit.  Something in our code needs updating.

repo: OdyseeTeam/odysee-frontend


text:
integrate Microsoft teams meeting room function

Our springboot system needs to integrate Microsoft teams meeting room function, is what we need in our springboot system to add the function of the meeting, what should I do?Have related demo?

@zsoftbuilder -Are you developing Microsoft Teams APP?

Not the APP, just in the existing springboot system integration teams function

@zsoftbuilder - Please have look at this document-
1.https://docs.microsoft.com/en-us/microsoftteams/rooms/third-party-join?msclkid=36a9b9cfd11b11eca80f4e8eee634858
2.https://docs.microsoft.com/en-us/MicrosoftTeams/rooms/rooms-deploy?msclkid=36aa938fd11b11ec93ccb4bd108cc66b

@zsoftbuilder - Could you please confirm if your issue has resolved with above suggestion or still looking for any help?

We are closing this issue for now, please feel free to reopen it, if required.

repo: OfficeDev/Microsoft-Teams-Samples


text:
How to suppress read receipt request?

How to suppress read receipt request when I mark an item as read? Is there anything equivalent to this C# counterpart?

I found it in EmailMessage class. Just need to call suppressReadReceipt() before setting read flag.
message.suppressReadReceipt();
message.setIsRead(true);
message.update(ConflictResolutionMode.AutoResolve);

Hope someone will find it useful.

repo: OfficeDev/ews-java-api


text:
Issue Deploying FAQPlus Experts app to Teams

Was able to successfully upload the FAQ Plus app but received an error when deploying the FAQ Plus Experts app.
Screen shot of error and app zip file used for the upload are attached.
faqplus-experts.zip.zip

Looks like you have a typing issue in manifest

Excellent, thank you! I was able to correct the issue and successfully uploaded the app.

repo: OfficeDev/microsoft-teams-apps-faqplus


text:
Language settings ignored during EPT import (Microsoft.ProjectServer.Client)

Unsure if this is a suitable place to post this issue, if not please point me in the right direction.
I'm using the Microsoft.ProjectServer.Client.EnterpriseProjectTypeCreationInformation class to build an EPT before adding to and updating the server, as can be seen in screenshot below -

My issue is that no matter what settings we change, the default site template language selected is German for all imported EPTs.
As can be seen in the screenshot, LCID of 1033 is being explicitly set on the EPT model, and no references to German can be found anywhere in our import artefacts.
We're pretty stumped, and have no idea what to check next. All language and region settings for Sharepoint and PWA are confirmed set to English.

Thanks Sam - we will take a look.

I do notice that German is top of the drop-down list - so I'm wondering if this is a display issue.  I know we used to have a display issue before the language drop down was added where the Catalan Lloc de projecte site template would always be shown even when the English was really used.  I'll see if I can repro.

I do repro Sam - but only if I have not defined a SiteCreationURL - so I suspect that the settings for site are not getting preserved with a missing URL.  I also noticed that if I opened my programmatically created EPT and manually changed the language it would complain that no URL was set.  I'll check with the team where the real bug might be here (should the call fail if URL is not set when certain other options are).  I successfully created an EPT for both English and French which created correct language sites when used for project creation.

Hi Sam, the product group have reviewed this and have decided not to fix this issue at this time.  The workaround of setting the SiteCreationURL looks to be the perfect solution - as not including it will leave the EPT in a bad state anyway - as if you edit you cannot save until setting the URL.  I will also take the action to update the documentation.  Thanks for raising this issue with us and I hope the workaround described is satisfactory for you.
Best regards,
Brian

authors: LunchWithaLens wallissam

repo: OfficeDev/project-dev-docs


text:
Adicionando novos itens em diversas categorias

Categorias: "Canais no Youtube", "Hosting", "Estudos", "IDE Cloud" e "Freebies"

Espero ter resolvido tudo corretamente.
Desculpo-me antecipadamente por qualquer possível erro cometido 😅

repo: OfficialMarinho/Links-uteis


text:
add blind steps for tournament

In non cash game tournament the blinds raising after a predefined period of time.

The blinds, ante and time of blind-rate must be defined.
The tournament needs a start-activation and the blind-rates must follow the time conditions

Out Of Scope:

Pause
Manuel Changes during the tournament

Predefined pause is included

repo: OfflinePoker/Tournament


text:
Are there Middleware achievement plan ?

This is a nice framework, i want to use in our web project, but after my overview, i dont find Middleware function achievement.  I think this is useful in authorization webservice. I dont know if you have this plan?
:)
Thanks.

Hi! Thank your for your suggestion. Rustful is currently not middleware oriented and there are currently no concrete plans for it. There is, however, support for "filters", which works like a subgroup of middleware, but they have been neglected for a while and their design isn't necessarily great.
The reason why it hasn't yet been made middleware oriented is that the same functionality often can be achieved using good old function calls. Something like:
fn my_handler(context: Context, response: Response) {
    let (context, response) = if let Some(res) = auth_or_fail(context, response) {
        res
    } else {
        return;
    }

    //...
}

This can be made less verbose with a try! like macro:
fn my_handler(context: Context, response: Response) {
    let (context, response) = expect!(auth_or_fail(context, response));

    //...
}

This doesn't mean that the door is closed for middleware. Just that there hasn't been any work on it. Thinking about it, making handlers return Option<(Context, Response)> would make them quite easy to stack... hmm...

Hi, Ogeon, Thanks very much. I think function auth_or_fail is also can solve my problem.

Alright. Note that auth_or_fail is purely hypothetical and you may need something more advanced. Feel free to reopen if you want to go any further with this.

authors: Ogeon inxi-pc

repo: Ogeon/rustful


text:
satellite imagery

HI,
There is repository of satellite imagery available on below link
https://csc.lsu.edu/~saikat/deepsat/
How can we make it compatible with ImageAI?

Your email has been received. Will review and revert.

authors: OlafenwaMoses jaigsingla

repo: OlafenwaMoses/ImageAI


text:
ValueError: a must be greater than 0 unless no samples are taken

I'm getting errors when trying to run custom training model code taken from documentation with my own dataset.
`from imageai.Detection.Custom import DetectionModelTrainer
trainer = DetectionModelTrainer()
trainer.setModelTypeAsYOLOv3()
trainer.setDataDirectory(data_directory="keycaps")
trainer.setTrainConfig(object_names_array=["a-key"], batch_size=4, num_experiments=200, train_from_pretrained_model="yolov3.pt")
trainer.trainModel()`
Here is the issue I'm facing when running the code above:
`Warning (from warnings module):
File "C:\Users\shaun\AppData\Local\Programs\Python\Python39\lib\site-packages\numpy\core_methods.py", line 264
ret = _var(a, axis=axis, dtype=dtype, out=out, ddof=ddof,
RuntimeWarning: Degrees of freedom <= 0 for slice
Warning (from warnings module):
File "C:\Users\shaun\AppData\Local\Programs\Python\Python39\lib\site-packages\numpy\core_methods.py", line 222
arrmean = um.true_divide(arrmean, div, out=arrmean, casting='unsafe',
RuntimeWarning: invalid value encountered in true_divide
Warning (from warnings module):
File "C:\Users\shaun\AppData\Local\Programs\Python\Python39\lib\site-packages\numpy\core_methods.py", line 253
ret = um.true_divide(
RuntimeWarning: invalid value encountered in true_divide
Traceback (most recent call last):
File "C:\Users\shaun\workspace\imageAI-python\DetectionTrainer.py", line 7, in
trainer.trainModel()
File "C:\Users\shaun\AppData\Local\Programs\Python\Python39\lib\site-packages\imageai\Detection\Custom_init_.py", line 229, in trainModel
self.__set_training_param(self._epochs, accumulate)
File "C:\Users\shaun\AppData\Local\Programs\Python\Python39\lib\site-packages\imageai\Detection\Custom_init.py", line 62, in __set_training_param
self.__anchors = generate_anchors(
File "C:\Users\shaun\AppData\Local\Programs\Python\Python39\lib\site-packages\imageai\Detection\Custom\yolo\custom_anchors.py", line 58, in generate_anchors
k, dist = kmeans(wh / s, n, iter=30)  # points, mean distance
File "C:\Users\shaun\AppData\Local\Programs\Python\Python39\lib\site-packages\scipy\cluster\vq.py", line 475, in kmeans
guess = _kpoints(obs, k, rng)
File "C:\Users\shaun\AppData\Local\Programs\Python\Python39\lib\site-packages\scipy\cluster\vq.py", line 503, in _kpoints
idx = rng.choice(data.shape[0], size=k, replace=False)
File "mtrand.pyx", line 909, in numpy.random.mtrand.RandomState.choice
ValueError: a must be greater than 0 unless no samples are taken`

Hi.
I've got same errors too, but I've solved it.
Using PascalVOC format will cause an error, you need to convert your dataset to YOLO format.
https://github.com/OlafenwaMoses/ImageAI/blob/master/BACKEND_MIGRATION.md#convert-pascal-voc-dataset-to-yolo-format
Link to converter script: https://github.com/OlafenwaMoses/ImageAI/blob/master/scripts/pascal_voc_to_yolo.py


text:
Fix cors error thrown by browsers

See https://github.com/apollographql/apollo-server/issues/514
and https://github.com/apollographql/apollo-server/pull/523
It'd be great if you could cut a new release after merge so that I could upate graphiql-workspace-app.

nice, thanks!

Published https://github.com/OlegIlyenko/graphiql-workspace/releases/tag/v1.1.2

Yay, thanks!

authors: OlegIlyenko kachkaev

repo: OlegIlyenko/graphiql-workspace


text:
В nvidia.md обновил версию драйверов, добавил про фреймбуфер. В Obsidian добавил переменные для epm версии

Изменил актуальную версию nvidia драйверов
Добавил описание новой фичи -- фреймбуфер от nvidia. Добавил предупреждение что фича экспериментальная.
Добавил для epm версии obsidian один из вариантов включения wayland режима
Добавил для epm версии obsidian описание отключения аппартаного ускорения

@vlad196 А почему нельзя просто скорректировать ярлык запуска через PinApp

У меня есть некоторые вопросы.

А точно ли приложения подхватывают переменные окружения из .bashrc?
Мне кажется немного небезопасным устанавливать переменные окружения с Wayland глобально. Вдруг некоторые приложения просто не адаптированы под его работу?

Более целесообразным будет изменять .desktop файл определённого приложения, через тот же PinApp, например.
Правда здесь тоже есть нюанс, обновления приложения могут его перезаписать и его обновлять придётся заново.

Можно, я просто описал протестированным мною способ, а с pinapp не знаком.
Могу под pinapp, но тогда уже завтра у себя проверю и перепишу. Тогда просто коммит с obsidian можно пока не принимать

@vlad196 Я сейчас напишу.

Протестируй с PinApp, потом дополни PR)

repo: OlegShchavelev/ALTRegularGnomeWiki


text:
Missing changelog between 4.3 and 5.1

Hi!
First of all thanks for creating this package, we use it in production to great results.
We currently use 4.3, but I see the latest version is 5.1.
That, to me, implies a breaking change in the public API, but cannot figure out what changed exactly and so can't blindly update.
Could someone sum up the changes made between the two versions?

I can't quite remember, but from having a look through the delta https://github.com/Olical/EventEmitter/compare/v4.3.0...v5.1.0 I don't think much changed. I think the big thing was looping over events in a normal manner, instead of backwards. I think while (i--) used to be faster in some browsers when I originally wrote this? I fell for jsperf microbenchmarks in those days :(
I can't really see anything else, I'm sorry I forgot to document it.
In this unreleased master diff https://github.com/Olical/EventEmitter/compare/v4.3.0...master there is an extra type check, but that should be fine. Honestly hardly anything changed. I think I bumped major because I changed the execution order. This could change program behavior, although I'd hope not!

Thank for the swift answer!
I should've probably just started with comparing the two versions myself.
That seems absolutely fine to me 👍

authors: Olical ZeeCoder

repo: Olical/EventEmitter

license: unlicense


text:
python repl result ends with extra '^M'  (CTRL-M)

Dear conjure developers,
I run conjure on windows 10 with treesitter installed. Both fennel and python client work, while every line of python output ends with extra '^M', and there's an extra line contains 'None^M'.  I guess it's a CRLF problem. Sorry for my poor English.

related config including:
Plug 'Olical/conjure'
let g:conjure#client#python#stdio#command = "python -iq"

system version
版本	Windows 10 专业版
版本号	22H2
安装日期	2021/4/4
操作系统内部版本	19045.2251
体验	Windows Feature Experience Pack 120.2212.4180.0

Here are outputs of :version
NVIM v0.8.0-1210-gd367ed9b2
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compiled by runneradmin@fv-az177-603

Here are outputs of  :healthcheck
nvim-treesitter: require("nvim-treesitter.health").check()

## Installation
  - WARNING: `tree-sitter` executable not found (parser generator, only needed for :TSInstallFromGrammar, not required for :TSInstall)
  - OK: `node` found v16.17.0 (only needed for :TSInstallFromGrammar)
  - OK: `git` executable found.
  - OK: `zig` executable found. Selected from { "zig" }
    Version: info: Usage: zig [command] [options]
  - OK: Neovim was compiled with tree-sitter runtime ABI version 14 (required >=13). Parsers must be compatible with runtime ABI.

## Parser/Features H L F I J
  - python         ✓ ✓ ✓ ✓ .
  - lua            ✓ ✓ ✓ ✓ ✓
  - rust           ✓ ✓ ✓ ✓ ✓

  Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
         +) multiple parsers found, only one will be used
         x) errors found in the query, try to run :TSUpdate {lang}

provider: health#provider#check

## Clipboard (optional)
  - OK: Clipboard tool found: win32yank

## Python 3 provider (optional)
  - INFO: Using: g:python3_host_prog = "python"
  - INFO: Executable: C:\Program Files\Python37\python.EXE
  - INFO: Python version: 3.7.5
  - INFO: pynvim version: 0.4.3
  - OK: Latest pynvim is installed.

Thank you for reporting this! And there is no need to apologise for your English, it's good and I understand the issue 🙂
I think this is because the Python REPL is printing \r\n whereas most REPLs on other OSs print \n (which Conjure splits lines on). So I think I need to split lines by \r\n on Windows for some REPLs.
I'll try to fix the Python client for now, to fix your problem, but maybe I'll need to fix other clients in the future.

I've pushed a fix to the develop branch, I hope that works for you! I can't reproduce the issue on my machine since I don't have any development tools on my Windows PC. Please let me know if it helps. Thanks!

Thank you for reporting this! And there is no need to apologise for your English, it's good and I understand the issue 🙂
I think this is because the Python REPL is printing \r\n whereas most REPLs on other OSs print \n (which Conjure splits lines on). So I think I need to split lines by \r\n on Windows for some REPLs.
I'll try to fix the Python client for now, to fix your problem, but maybe I'll need to fix other clients in the future.

Thanks. It works, all '^M' go away.  Both on windows and linux
there is a line contains "None" after I input \eb , is this in line with expectations?

That's great! And yes, None is expected since I think that's what print returns.

authors: Appalled Olical

repo: Olical/conjure

license: Unlicense


text:
[WIP] Optimizer planning

This is a WIP, still need to (and appreciate any help or suggestions for):

[x] more flatMap examples
[x] merge example
[ ] composition examples: tail-shareable mixed with always-shareable
[ ] quick look at imitate example
[ ] algorithmic considerations

@OlivierBlanvillain When you discuss the example of val out = rx1.dropIf(_ % 2 == 0)(-1).merge(rx2.dropIf(_ % 2 == 0)(-1)), are you assuming the dropIf rxs may be registered at different times than the merge rx? If so, I can easily see how this could give rise to issues, though in the example I pushed where they are all at the same time, I do not see how it can be any worse than tail-shareable. Still, I guess we must always assume "non-temporally transparency", but I am just curious.

I just tried, I could't make an trace for that example that would be worse than tail-shareable. I must have messed up at the time, which means it might compose better than I thought :smile:

are you assuming the dropIf rxs may be registered at different times than the merge rx?

That would be impossible, out is a "Rx expression" that can only be interpreted at a single point of time, as a whole. There is no way to "register" a sub expression of a Rx and use the result as part of a bigger "Rx expression": it would break RT.

Right, I get that different registration points can't exist for this particular expression contained in out; maybe it gets more complicated when we break down the expressions individually, which would allow certain time delays to happen between the registration of the various rxs, which is what I was thinking when I said non-temporally transparent (which I guess is just another way of saying not always-shareable).

There is no way to "register" a sub expression of a Rx and use the result as part of a bigger "Rx expression": it would break RT.

OK, I understand the sentiment but I think I'm still missing something. Isn't that essentially what we are doing with showing different registration points in these marble diagrams? I suppose one way to do that in code would be to have different threads, with different delays (artificially performed with Thread.sleep(x), but more likely due to user input or network latency in the wild).

That wouldn't be only thing that falls apart if someone uses the current implementation from multiple thread, thankfully that's not an issue on js :smile:

@OlivierBlanvillain Oh right, I proved to myself that the right way to do this in JS is probably using setTimeout. I added an example for merge in the latest commit - let me know what you think about the slight test restructuring. If that's all good, I can think of two things to do next:

Create a test using ScalaCheck (never tried it) showing that tail-shareable composition is still tail-shareable OR prove it OR ignore it for now :)
Then move on to algorithmic considerations

I'm working on a proof (it doesn't look that hard), I just found an interesting example to shows why we need to wait for at least two emitted elements before sharing:
val numbers: Rx[Int]
val odd: Rx[Int] = numbers.dropIf(_ % 2 == 0)(-1).dropRepeats
// numbers =>    0       0   3   4        5   7 ...
// odd1    =>       •5       3            5   7 ...
// odd2    =>                       •5        7 ...

(it doesn't look that hard)
I'm glad you think so! I wouldn't mind trying it but I'm sure it would be slow going for me anyway for more than one reason :smile:

That's certainly an interesting example, particularly since dropRepeats is always-shareable.

Here what I have, it's not very polished but I think it works.
Definition: a Rx is tail-shareable if any two interpretation i1 and i2 of that Rx are equivalent after they emitted their first value. Two interpretation are equivalent if there is no observable difference between canceling i1 or canceling i2.
Lemma 1: Values emitted by interpretations of Rx composed of map, merge, collect and Vars are either 1. the first value of that interpretation or 2. triggered by an update from one of the Vars.
Proof: by structural induction on Rx with the above structure. Vars form the base case and Map, Merge and Collect the inductive case. We inspect the implementation:

The of interpretation Vars forwards to the underlying foreach which implements what is stated in the Lemma.
case leaf: Var[A] =>
leaf.foreach(effect)

Map interprets the underlying Rx with a pure function: holds by induction hypothesis
case Map(self, f) =>
run(self)(x => effect(f(x)))

Merge discards the first value of the other Rx, then holds by induction hypothesis
case Merge(self, other) =>
val c1 = run(self)(effect)
var discard = true
val c2 = run(other) { x =>
if (discard) discard = false
else effect(x)
}
Cancelable { () => c1.cancel; c2.cancel

Collect first value is either fallback or comes from the underlying Rxm then it holds by induction hypothesis
case Collect(self, f, fallback) =>
var first = true
run(self) { a =>
val out =
if (f.isDefinedAt(a))
effect(f(a))
else if(first)
effect(fallback)
else ()
first = false
out
}

Lemma 2: The interpretation of Rx composed of map, merge, collect and Vars is either pure (no var/mutation) or effectively pure after emitting the first value (it has two states, one to emit the first value and another one for all subsequent values).
Proof: by structural induction on Rx with the above structure. Vars form the base case and Map, Merge and Collect the inductive case. We inspect the implementation:

Vars: no var/mutation (one also has to look inside the implementation of foreach)
case leaf: Var[A] =>
leaf.foreach(effect)

Map: no var/mutation
case Map(self, f) =>
run(self)(x => effect(f(x)))

Merge: discard stays false after the first element
case Merge(self, other) =>
val c1 = run(self)(effect)
var discard = true
val c2 = run(other) { x =>
if (discard) discard = false
else effect(x)
}
Cancelable { () => c1.cancel; c2.cancel

Collect: first stays false after the first element
case Collect(self, f, fallback) =>
var first = true
run(self) { a =>
val out =
if (f.isDefinedAt(a))
effect(f(a))
else if(first)
effect(fallback)
else ()
first = false
out
}

Theorem: Rx composed of map, merge, collectandVars` are tail-shareable.
Proof: Given two interpretation i1 and i2 of such Rx, consider any non first value emitted by i1. By Lemma 1, this value is triggered by an update from one of the Vars, which by constructions must necessarily be at leaf position. By Lemma 2, both interpretation are effectively pure, meaning that i2 will necessarily produce the same result i1. In other words, i1 and i2 are equivalent, and the Rx is tail-shareable.

@OlivierBlanvillain One issue is that having sharing at every node might generate unwanted overhead for large Rx graphs; ideally, we could bypass the issue if the interpreter could find out when an Rx node in a graph has multiple dependent Rxs; but it looks like there is probably no way to do this, without adding additional overhead to the Rx, so probably not worthwhile (at least in the first pass). Though the overhead might be minimal, something like subscribers for Var, but only a reference count:
object Rx {
  //...
  var refCount = 0

  // Then each rx method can increment like:
  def collect[B](f: PartialFunction[A, B])(b: B): Rx[B] = {this.refCount+=1; Collect[A, B](this, f, b)}
}

However, I'm not exactly sure how to deal with decrements to refCount, which I guess would only happen whenever a particular Rx is gc'd.

I'm not sure I follow, could you give a concrete example?

@OlivierBlanvillain Something like this, where each dashed, black line (other than the first, which is a Var) is an ordinary Rx that can be shared (shared = blue circles). If the optimizer simply places them anywhere possible, then we wind up with something like the right figure, I think, where ideally, we only need something like the left.

I think the algorithm I have in mind would do the optimal thing in your example. One implementation would be to have a global mutable map from node to interpretation (modulo the sharability logic), whenever an edge is interpreted the global map is first checked for shareable instances, if none is found, then a new interpretation is created for that node and added to the map.

Tree the user wrote: (| edges are rx nodes)

 var
  |
  |
/   \
|   |
|   |

1st interpretation:

 var
  |
  |x
/
|
|y
run on the left leaf

2nd interpretation: (! are edges shared with previous interpretations)

  !x
    \
    |
    |z
   run on the right left

3rd interpretation:

!y
run on the left leaf

4th interpretation:

    !z
run on the right leaf

This means that the runtime actually has a single "interpreted" copy of the graph:
 var
  |
  |x
/   \
|   |
|y  |z

Where x y and z have more than one callback attached to them.

This sounds good to me in general, but would this be prone to memory leaks? I assume we'll have a mechanism from removing entries from the mutable map when there are zero callbacks, but more on that below:
Drilling down to the details a bit:

whenever an edge is interpreted the global map is first checked for shareable instances

There still needs to be a way to see if we even need to create a shareable instance, i.e., how does the first or second interpretation in the example above know that x (for instance) has more than one callback? What are callbacks in this case (I assume these are not something currently in monadic-rx that go by another name, unless we mean the effects)?

@bbarker This global mutable map thing is just the first idea than came to my mind, I didn't really think it through. Let me try to answer your questions (brainstorming):

but would this be prone to memory leaks

This should be fine, there is already a mechanism in place to deal with that, I don't see why it couldn't be extended to this sharing thing.

What are callbacks in this case

Yes, I'm talking about what I've called effect in the current implementation.

There still needs to be a way to see if we even need to create a shareable instance

Indeed this is something that I completely overlooked. The naive solution is to create a dummy shareable node for every actual node, but this might result in quite a bit of wasted resources. (I see that this is what you draw on your right hand side diagram, I get it now!)
An alternative that comes to my mind: keep track of the current callback inserted on every node (in a mutable field). Whenever a second traversal hits on a node to be shared, then create the sharing node on the fly, and "path" the previous callback to go thought that new sharing node instead.

An alternative that comes to my mind:

@OlivierBlanvillain That sounds pretty solid to me; I think the refCount variable, mentioned above would still be used in this case; I don't anticipate any use cases where we would have a number of references on the order where integer overflow would occur ... but I guess one never knows, but at least I think we can ignore that issue for now.
I have more questions, but at this point I think it might be more clear to try and code something up to see how it goes, so will try to do that soon.

@OlivierBlanvillain As a quick sanity check before moving on to other Rxs, just wanted to run this by you (it passes Rx tests):
    case rx @ Map(self, f) => {
      var refCount = 0
      if (refCount == 0) {
        run(self){x => refCount += 1; effect(f(x))}
      }
      else {
        val shared = rx.impure.sharing
        run(shared)(effect)
      }
    }

authors: OlivierBlanvillain bbarker

repo: OlivierBlanvillain/monadic-html


text:
🛑 Helix Intranet API - Dev is down

In f8f9237, Helix Intranet API - Dev (https://hbi-intranet-backend.onrender.com/status) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Helix Intranet API - Dev is back up in bdeb6d2 after 9 minutes.

repo: OluwaninsolaAO/uptime-monitoring


text:
added my name

scott created

Can you close this PR and make another PR.
Reason: lot of unwanted files

Good evening. But it reads closed

You should open another one.

Be sure to change only names.txt

Make a separate branch for your changes and

Do not use the first or last line.

authors: Oluwasetemi scottobiaya tobisupreme

repo: Oluwasetemi/altschool-opensource-names


text:
Max emma

I added my name, Maxwell Emmanuel

Please I am sorry for all the trouble we have caused you but count it all joy. Your PR is about to be merged and you will be able to see your name on this url.
To enable me to do this, READ the README again carefully, update your code with the latest and push the update. I am here for you for the next 6 hours before I close the PR so you can initiate a fresh PR which will be easier to merge.

authors: Oluwasetemi maxsphinix


text:
stebin ben to cpp and html

Description

Types of changes

[x] Bug fix or improving code quality
[ ] New language
[x] New feature

Checklist:

[x] My code follows the code style of this project.
[x] I have updated the documentation accordingly.

added data succesfully

repo: Omkar-Ajnadkar/Hello-World


text:
Filter large database list in Postgresql

I'm running a heroku instance with a Postgres add-on.  The server has ~2000 databases.  I can't find a way to filter to only show my database, is there a feature in OmniDB for that?

I don't think so. Note the same is true for a lot of schemas, or a lot of tables/functions/views or anything within a single schema really.
As I see it, even though intended differently, my feature idea #1233 would implicitly help with this issue as well. (At least is you define a separate connection for every database you actively care about.)
Regards
pgaro

authors: BinarySpike pgaro

repo: OmniDB/OmniDB


text:
Consensus hash divergence with newer boost (>=1.65.0)

There is a bug that causes checkpoint failure at block 310000 (https://github.com/mpugach/docker_omnicored/issues/2).
It happens because:
https://github.com/OmniLayer/omnicore/blob/c0738a96b587c80a73f93cb653c032e1cc95b6f4/src/omnicore/log.cpp#L55
https://github.com/OmniLayer/omnicore/blob/c0738a96b587c80a73f93cb653c032e1cc95b6f4/src/omnicore/tx.cpp#L528
https://github.com/OmniLayer/omnicore/blob/c0738a96b587c80a73f93cb653c032e1cc95b6f4/src/omnicore/tx.cpp#L539
Certain deadline dates are not valid, like in tx 5c183d6c1c9b8a617dbdcd1afa876eec14b46a2aa45d471e8381b287ccba731d
With new versions of boost (>= 1.65.0), boost::posix_time::from_time_t() throws an exception on invalid datetime.
2019-01-26 16:38:09 parseTransaction(block=306906, 2014-06-20 22:34:22 idx= 705); txid: b7c66175a99ca0e7b1691905d50a46165adb7a8012d9ec5e1ecf8239f859df6d
2019-01-26 16:38:09     ------------------------------
2019-01-26 16:38:09              version: 1, class B
2019-01-26 16:38:09                 type: 51 (Create Property - Variable)
2019-01-26 16:38:09            ecosystem: 2
2019-01-26 16:38:09        property type: 2 (divisible)
2019-01-26 16:38:09     prev property id: 0
2019-01-26 16:38:09             category: Testing
2019-01-26 16:38:09          subcategory: Crowdsale Demo
2019-01-26 16:38:09                 name: OmpaLoompa
2019-01-26 16:38:09                  url: http://www.themulticurrencycrowdsale.com
2019-01-26 16:38:09                 data: This awesome crowdsale supports multiple currencies!
2019-01-26 16:38:09     property desired: 2 (TOMNI)
2019-01-26 16:38:09      tokens per unit: 0.00000100
2019-01-26 16:38:09
************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_9gregorian8bad_yearEEEEE
Year is out of valid range: 1400..10000
bitcoin in ProcessMessages()

deadline here would be printed on old boost as:
2019-01-26 18:05:05             deadline: 1940-01-02 19:46:56 (146bc793d2b0)

When the same exception is caught while processing local blocks, omni core exits.
(https://github.com/OmniLayer/omnicore/issues/788, https://github.com/OmniLayer/omnicore/issues/731)
But when the node gets the block and transactions from the peer, this exception happens
in the context of ProcessMessages(), and does not result in shutdown -
there are code in ProcessMessages() that catches exception, and then just does PrintExceptionContinue(&e, "ProcessMessages()");
The crowdsale CROWDSALE id: 2147483679 value: 100 property: 2
was not registered due to this exception, but the processing continued.
Later, in tx 938a160cdb20c4103d2e5fc4922bd85be701797f41e64326f652469b7c8006d3, this causes
2019-01-26 16:41:07 logicMath_SimpleSend(): rejected: sender 1KF9yZ2gnwgR4mu6d3ZA6yLJARhhGfBope has insufficient balance of property 2147483679 [0.00000000 < 8.58757932]

That results in consensus hash calculations to diverge from the clients that is running with old boost.
Because consensus hash diverged, checkpoint at block 310000 does not match, and omni core stops.
The danger here is that exceptions in consensus-critical code are ignored.
The checkpoint catched the bug, but the consensus hash diverged.
Here it happened with date formatting, but it may be other aspects of boost or other libs, and considering that some debug log flags are on by default, the code that outputs this debug logging messages might not consider that it might affect consensus hash.
Such mismatches can be discovered only after the node is restarted, and dies when it tries to process the data that was skipped when the exception was catched and ignored.
Are debug logging flags really necessary to be turned on by default ?
Should omni processing code catch own exceptions itself, and die on them ? That would turn impact of such bugs to denial of service, but not consensus divergence.

After full sync with custom-patched omnicored (that catches the exceptions within DateTimeStrFormat and prints them, for the purpose of logging all the exceptions), as of block 561350, the last seen exception was in parseTransaction(block=420551, 2016-07-13 11:57:14 idx= 451); txid: 5b81b20508c98a9bda3de68d6b3872f52efd02ebe2cb9b114cfb3a3225f33dd1
This does not mean that such exceptions cannot happen in affected instances with future transactions.
All the exceptions catched since block 300000 to 561350: https://gist.github.com/dgpv/6b880893e4f310bbf81e3626ff94b027

The last block that had the exception is block=420551 mined 2016-07-13
Boost version 1.65.0 is released 19 Aug 2017
So the probability of these old exceptions causing actual live consensus hash divergence is very low, because for this to happen, someone needs to get omnicored built after 19 Aug 2017 with boost 1.65.0, but use directory with blockchain data that was synced no later than block 420550, 10 months old directory.
Looking at omni core release notes, there should be a checkpoint at block 460000, which was added in Omni Core 0.2.0, so even that exception would be catched by the checkpoint.
This makes the probability of live consensus hash divergence even lower, because then it have to be pre-0.2.0 instance that got past all the checkpoints.
The potential danger is only in exceptions happening in new blocks.

This was resolved with 0.4.0. Thank you so much again @dgpv!

repo: OmniLayer/omnicore


text:
Dap initialization and request issues.

I am trying to use Dap Client to interact with nodejs debug adapter.
But cannot successfully call the initialization request. After confirming that the server received the initialization request and returned the result, the client code was stuck in this step.
public async Task Initialize(CancellationToken token)
        {
            await DebugAdapterEventingHelper.Run(
                _initializeDelegates,
                (handler, ct) => handler(this, ClientSettings, ct),
                _initializeHandlers.Union(_collection.Select(z => z.Handler).OfType<IOnDebugAdapterClientInitialize>()),
                (handler, ct) => handler.OnInitialize(this, ClientSettings, ct),
                _concurrency,
                token
            ).ConfigureAwait(false);

            RegisterCapabilities(ClientSettings);

            _connection.Open();
            var serverParams = await this.RequestDebugAdapterInitialize(ClientSettings, token).ConfigureAwait(false);

            ServerSettings = serverParams;

            await DebugAdapterEventingHelper.Run(
                _initializedDelegates,
                (handler, ct) => handler(this, ClientSettings, ServerSettings, ct),
                _initializedHandlers.Union(_collection.Select(z => z.Handler).OfType<IOnDebugAdapterClientInitialized>()),
                (handler, ct) => handler.OnInitialized(this, ClientSettings, ServerSettings, ct),
                _concurrency,
                token
            ).ConfigureAwait(false);

            _receiver.Initialized();

            //await _initializedComplete.ToTask(token);

            await DebugAdapterEventingHelper.Run(
                _startedDelegates,
                (handler, ct) => handler(this, ct),
                _startedHandlers.Union(_collection.Select(z => z.Handler).OfType<IOnDebugAdapterClientStarted>()),
                (handler, ct) => handler.OnStarted(this, ct),
                _concurrency,
                token
            ).ConfigureAwait(false);

            _instanceHasStarted.Started = true;
        }

In the comment statement on line 24:
await _initializedComplete.ToTask(token);

the value of token is always false, so the program just waits here and cannot continue.
I have obtained the data returned by the server in the client.ServerSettings property, which should indicate that the server has successfully responded to the request.
There is another problem. When I called the 'Launch' request, the 'noDebug' parameter was passed, but the server did not receive the parameter. I don't know what happened in the middle.
var breakResponse = await client.SetBreakpoints(new SetBreakpointsArguments() {
                Source = source,
                Breakpoints = breakPoints,
                SourceModified = false
            });

var launchResponse = await client.Launch(new LaunchRequestArguments() {
                NoDebug = false,
            });

It is also the first time for me to use DAP protocol for communication. This process is more difficult for me
So sometimes I cannot find out whether the problem is on the client side or on the server side. If possible, can you try to test the communication with the Vscode-node-debug2 debug server?
Thanks in advance!
Since I cannot upload some screenshots on the company’s intranet, please let me know if you need more information
More Information:
Dap Client: Omnisharp Dap Client(v0.19.0-beta.4)
Dap Server: vscode-node-debug2(v1.42.5)

So the server should be sending the InitializedEvent back which should complete that task, so if the server never sends that task... things break down.  I'll review and reply back shortly.

So it's getting stuck at the initialized event as I figured.
Problem is I don't know the "right" way to fix this.  The spec says it's an required event.  We could simply ignore the initialized event or timeout after a certain time but then the server is in an unknown state at least from the client perspective.

The only thing I think might help is moving up a few lines to just after RequestDebugAdapterInitialize.
https://github.com/OmniSharp/csharp-language-server-protocol/blob/32a135922dcf794158588fdacd66213b102ea5c4/src/Dap.Client/DebugAdapterClient.cs#L149

Thank you for your reply!The nodejs debugging server has been used in Vscode. Maybe we can look at its source code reference to the correct processing method。In addition, can Dap Client be used for product development now? Next year we may need to use Dap Client to support code debugging on .net projects.I don't know if the communication failure is caused by the difference of various debugging adapters
Thanks!

I think it can be, obviously we might run into bugs from time to time.  I haven't gone and pushed a 1.0 just yet because I'm waiting to make sure that there aren't any other breaking changes that might need to be made.

I think it can be, obviously we might run into bugs from time to time.  I haven't gone and pushed a 1.0 just yet because I'm waiting to make sure that there aren't any other breaking changes that might need to be made.


text:
Update omnisharp-node-client for using the latest omnisharp-roslyn binary

Inside Eclipse CHE we are using omnisharp-node-client language server. I see that the latest release works with dotnet 1.0.4 projects, but it doesn't work with dotnet 2.0. Can you update this omnisharp-node-client to the latest omnisharp-roslyn binary, (seems it should resolve this problem)?

It also seems like the current version in omnisharp-node-client does embed a version of OmniSharp-Roslyn with the following issue: https://github.com/OmniSharp/omnisharp-vscode/issues/786 .

I'll jump on it this weekend!

Which version/commit of omnisharp-roslyn does bring support for dotnet 2.0?
Omnisharp-node-client currently uses omnisharp-roslym 1.22 which seems to be the latest release. Is the upcoming 1.23 going to provide full support for dotnet 2.0 ? What would be the prerequisites for it to work on Linux?

1.23.1 should work with the latest dotnet core 2.0.  I'll be pushing an update with the related fixes tonight.

Hurray! I tried the latest release v7.1.2 which uses omnisharp-roslyn 1.23.1 and it worked well on Fedora 26 with a version recent of dotnet-core 2.0 and no dependency on mono!
I believe it's a pretty satisfying result from integrator and user POV, so we can close this issue.
Thanks for your assistance!

repo: OmniSharp/omnisharp-node-client


text:
Code fixes with additional files not working

It looks like code fixes from a roslyn analyzer aren't actually being applied.
Minimal repro project: Archive.zip. Open in VS Code with analyzers enabled ("omnisharp.enableRoslynAnalyzers": true)
This project is using Roslyn's PublicAPI analyzer. Among other things, it adds some custom code fixes to the quick-fix drop down. This is populating correctly in the UI.
But, when I execute the code fixes, nothing happens.

The log (log.txt) shows
[info]: OmniSharp.Roslyn.CSharp.Services.Refactoring.V2.RunCodeActionService
        Applying code action: Add Class1 to public API

This should have made a change to the PublicAPI.Unshipped.txt file, but it didn't.

This code fix works correctly in Visual Studio 2019.
Details
Omnisharp version: 1.34.3-beta.22
VS Code: 1.37.1
C# extension: 1.21.1
OS: macOS Mojave
Mono: 5.18.1
dotnet: 2.2.105

Thanks for the report and the repro.
The problem here is two-fold:
a) OmniSharp doesn't apply changes to additional documents (non core source documents) when running code actions.
b) changes to additional documents are not reflected in Workspace state, which means even when a) is handled, an invoked code fix which modifies the API surface document wouldn't be picked up by analyzer engine and the diagnostic wouldn't go away
Both seem reasonably easy to fix, I think - in fact I put together a quick PoC on my machine and it seems to work fine. I will PR this in the coming days.
Thanks again for reporting.

Any update on this? Still having the same issue today. Thanks!

The branch is here https://github.com/OmniSharp/omnisharp-roslyn/tree/feature/respect-additional-files
it has to be updated to latest master, and we need to add some tests.
It hasn't been the highest priority to be honest due to other work.

any update on this? my entire dept is suffering a lack of ability to generate api documentation without using a windows machine and visual studio IDE as we've switched to Macs for developers

any update on this? my entire dept is suffering a lack of ability to generate api documentation without using a windows machine and visual studio IDE as we've switched to Macs for developers

no update

no update

I'm also running into this issue with the Roslyn release-tracking analysers.

The branch is here https://github.com/OmniSharp/omnisharp-roslyn/tree/feature/respect-additional-files
it has to be updated to latest master, and we need to add some tests.
It hasn't been the highest priority to be honest due to other work.

I've updated the branch to the latest master in #2146. If you tell me what tests are needed I can also at least attempt to add them.
I can't have this feature fast enough! :sweat_smile:

For anyone interested, we ended up executing the analyzer through dotnet format, which has actually worked out better for us overall:
dotnet format --fix-analyzers warn --diagnostics RS0016

authors: ChrisMiskowiecPL FiniteReality aj0413 filipw natemcmaster tobias-tengler

repo: OmniSharp/omnisharp-roslyn


text:
Signature Help for Local Functions

Fixes #https://github.com/OmniSharp/omnisharp-vscode/issues/1715
The issue has been fixed with the change in #1030 . Added a test to check for the same.
Please review @DustinCampbell @TheRealPiotrP @rchande

Sigh... hit update branch instead of merge...  Will merge later once CI does its thing.


text:
Support text changes for rename and code actions

This PR adds support for text changes to the rename and code actions route such that they can return a list of text changes instead of the new buffer. The idea is that with text changes editor can update without flickering and without losing scroll positions etc. The changes go like this:

Add WantsTextChanges flag to the CodeActionRequest and RenameRequest as well as adding a Changes field to their responses
Move around and reuse the text change logic we already have to formatting
Modify the rename and code actions controllers such that they either produce text changes or new buffers
Update RenameFacts to also check for valid text changes

LGTM

:+1:

thanks

authors: jrieken nosami


text:
Enable LSIF indexer in Azure Pipelines

cc @david-driscoll @arjun27

Closing. Let's reopen once we figure out the details with authenticating with the LSIF service from a PR build.

Thanks @mholo65, we are working on this fix and I will get back to you.