Error: Did not check() all arguments during call to '/Websites/update'

Hi, this is part of an app I'm currently developing...
client/modules/listWebsitesRating/listWebsitesRating.js:
Template['listWebsitesRating'].events({
    "click .ratingPlus": function (event) {
      Websites.update(this._id, {$inc: {'score': 1}});
      return false;
    },
    "click .ratingMinus": function (event) {
      Websites.update(this._id, {$inc: {'score': -1}});
      return false;
    }
});

(subscription is inside a parent module)
server/publications/WebsitesPub.js:
Meteor.publish('Websites', function () {
  return Websites.find();
});

All what this part does is that when user clicks on + or -, it changes rating (or score) of webpage. But in the server side console it throws an error:
I20150420-21:58:29.296(2)? Exception while invoking method '/Websites/update' Error: Did not check() all arguments during call to '/Websites/update'
I20150420-21:58:29.297(2)?     at [object Object]._.extend.throwUnlessAllArgumentsHaveBeenChecked (packages/check/match.js:357:1)
I20150420-21:58:29.328(2)?     at Object.Match._failIfArgumentsAreNotAllChecked (packages/check/match.js:112:1)
I20150420-21:58:29.329(2)?     at maybeAuditArgumentChecks (packages/ddp/livedata_server.js:1614:1)
I20150420-21:58:29.329(2)?     at packages/ddp/livedata_server.js:648:1
I20150420-21:58:29.329(2)?     at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
I20150420-21:58:29.329(2)?     at packages/ddp/livedata_server.js:647:1
I20150420-21:58:29.330(2)?     at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
I20150420-21:58:29.330(2)?     at [object Object]._.extend.protocol_handlers.method (packages/ddp/livedata_server.js:646:1)
I20150420-21:58:29.331(2)?     at packages/ddp/livedata_server.js:546:1

and on client side javascript console:
update failed: Internal server error

Although the app is working quite well, it's simply annoying... I've searched on the internet, found I should use check() method on server side, but I don't understand how to use it, when my published function doesn't take any arguments. Maybe the problem is that I should call update inside of the published server function instead of a client function? thx
UPDATED:
Okay... I added this peace of code to startup/methods.js (not sure if it's right place, but for now it's good enough):
Meteor.methods({
    ratingUpdate: function(id, num){
    check(id, String);
    check(num, Number);
    Websites.update(id, {$inc: {'score': num}});
    }});

Instead of directly calling Websites.update(), I'm calling this:
Meteor.call('ratingUpdate', this._id, -1, function (err, result) { if(err) { console.log(err); }});

so I'm able to handle error logging much better, but the error in server console is still the same (except the name of called function of curse). But now I at least know that this is not probably meteor-boilerplate issue, so accept my apology.

Try removing following package: matteodem:easy-security

Ok, this works for me, thanks. But what if I would like to use easy-security to add rate limit for methods? Is it bug, or am I doing anything wrong?

Yeah, it's a known bug. see https://github.com/matteodem/meteor-easy-security/issues/12


Docstrings code quality

Codecov Report

Merging #9 (ffdedff) into main (8583a46) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   81.07%   81.07%
=======================================
  Files           2        2
  Lines         280      280
=======================================
  Hits          227      227
  Misses         53       53

Impacted Files
Coverage Δ

...egment_blobs_and_things_with_membranes/__init__.py
78.96% <100.00%> (ø)

Continue to review full report at Codecov.

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

Unclear why CI tests are failing. Locally they pass The changes here do hardly change code.
https://github.com/napari/napari/issues/4797


Not a challenge

Challenge Confirm the Ending has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/601.4.4 (KHTML, like Gecko) Version/9.0.3 Safari/601.4.4.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
function end(str, target) {
  return str.endsWith(target);
}

end("Bastian", "n");

It's not a bug, but I didn't want to post what might be considered a way to cheat. Is using my ridiculously simple solution cheating, or missing the point of the challenge?

That is not the goal of the challenge. We have a bug open about this: #4764. Closing as a duplicate. Thanks and happy coding!


Serving DIGITS over https with nginx

I tried setting this up to terminate SSL at nginx, and reverse proxying to the application. The application works, but some of the link requests (built by flask url_for) are not being sent over HTTPS, but rather plain text to :443, so it seems like Flask is not using the scheme that the application is using to generate the links. The socket.io connection was hard-coded to use 'http' (see PR #1333).
Do you have any recommendations for serving the application over HTTPS?

We are happy to review changes which enable HTTPS.


[Question] Lunar Lander Trained Simulation Playback

Question
So on the Gymnasium website, this code snippet is provided:
import gymnasium as gym
env = gym.make("LunarLander-v2", render_mode="human")
observation, info = env.reset(seed=42)
for _ in range(1000):
   action = env.action_space.sample()  # this is where you would insert your policy
   observation, reward, terminated, truncated, info = env.step(action)

   if terminated or truncated:
      observation, info = env.reset()

env.close()

How do I simulate my trained lander using the code above? I used the Stable Baselines3 library PPO algorithm to train the agent, but I'm not sure how to play the trained simulation. action = env.action_space.sample()  # this is where you would insert your policy tells us to insert the policy, but I can't figure out how to.

Hey, this is an SB3 question not a gymnasium question, could you look at their documentation on how to run the policy.


Update README.md

Two links currently missing:
Build manifest
GitHub workflow
Please replace the placeholders with correct links when available.

Closing this as we generally don't accept contributions from first-time contributors which just reword the main README. Thank you for flagging up that we still reference circleCI in the readme.


Create Contract Definition/Offer

Description
As a data space partcipant
I want to write API specifications for creating a Contract definition/offer as part of Data Governance Feature Set
So that this Contract Offer could later be sent to relevant EDC connectors
In Scope
Writing API Specifications
Out of Scope
Implementation

The Create Contact Offer API specifications are available at https://confluence.catena-x.net/display/CXAR/Data+Governance+KIT%3A+REST+API+of+decentral+components

The latest API specifications can be found in the Data Governance KIT documentation at https://eclipse-tractusx.github.io/docs-kits/category/data-governance-kit


clone theme repo earlier in deployment

What does this PR do? Please provide some context
We identified a bug with deploying edx using vagrant. The issue is caused by how and when we setup the theming directory. It's likely that this bug has other ways of manifesting itself outside of vagrant.
The fix is to simply clone the theming repository earlier in the deployment procedure. This allows the edx deployment steps to "see" the theming directory. It also means that we will not need to delete the directory (which can fail) before doing the git clone.
Where should the reviewer start?
n/a. short review.
How can this be manually tested? (brief repro steps and corpnet-URL with change)
deploy onebox or STAMP
What are the relevant TFS items? (list id numbers)
109551
Definition of done:

[x] Title of the pull request is clear and informative
[x] Add pull request hyperlink to relevant TFS items
[x] For large or complex change: schedule an in-person review session
[x] This change has appropriate test coverage
[ ] Get at least two approvals

Reminders DURING merge

If you're merging from a short-term (feature) branch into a long-term branch (like dev, release, or master) then "Squash and merge" to keep our history clean.
If merging from two longterm branches (like cherry picks from upstream, dev to release, etc) then "Create merge commit" to preserve individual commits.

the current fix fails at this step edxapp : gather {{ item }} static assets with paver i'll fix the underlying problem soon


ant javaviewer

build:
[copy] Copying 2 files to /azkaban/azkaban-plugins-master/plugins/javaviewer/lib
[mkdir] Created dir: /azkaban/azkaban-plugins-master/dist/javaviewer/classes
[mkdir] Created dir: /azkaban/azkaban-plugins-master/dist/javaviewer/dust
[copy] Copying 4 files to /azkaban/azkaban-plugins-master/dist/javaviewer/classes
[javac] /azkaban/azkaban-plugins-master/plugins/javaviewer/build.xml:90: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 1 source file to /azkaban/azkaban-plugins-master/dist/javaviewer/classes
[exec] mkdir -p obj && dustc --name=stats stats.tl obj/stats.js
[exec] /bin/sh: dustc: not found
[exec] make: *** [obj/stats.js] erro 127
BUILD FAILED
/azkaban/azkaban-plugins-master/build.xml:100: The following error occurred while executing this line:
/azkaban/azkaban-plugins-master/plugins/javaviewer/build.xml:96: exec returned: 2
Total time: 55 seconds

i encounter the same issue too.

any one resolved it ?please


Indexer Refactor

[ ] research & find a better solution for the db connection inside worker threads
[ ] make eventsHandler a class and reuse code
[ ] make block query interval configurable and get rid of the hardcoded
value

done in  #202


Add service account management in the client library UI

Clean PR based on discussion and work on #1835
Adds Service Account management to the GCP API management confirmation dialog.

Library screen is unchanged

Confirmation dialog with an API that has no roles

Confirmation dialog with APIs that have roles

User chooses not to create a service account / download key

@patflynn @ivanporty please look at the updated UX above.
This is based on the mockups I demod today. Yes I know it feels a little busy and I'm thinking of how to improve that.
Almost ready for code review, will update here.

That's great, much easier to feel the connection between APIs and service accounts.
Do we enable 'Service Account' checkbox by default?
Nit: could we align text fields for "Service Account Name" and "Download Path" too?

@ivanporty I was actually working on the alignment like you mentioned. Screenshots updated.
Yes, service account checkbox is selected by default.
Also, ready for code review

For service account name, do we think it's viable to show what name is generated if nothing is specified (if it's possible to know at all)? Or maybe we're going to show the resulting service account name in final notification bubble?

@ivanporty yes - sorry forgot to mention - I'd like to confine this PR mostly to agreeing on the UI. The next PR will have the service account generation (including setting a default name, key downloading, etc.)

(screenshot updated again with slight change - added some margin between the download path field and the role table)

@patflynn - would be great if you could take a quick look at the UX too (screenshots above).

@ivanporty I think I've either fixed or commented on all your points. PTAL.

Excellent, thanks, looks great!

:+1:  I like it.  For service account name what do you guys think of defaulting to the module name?  In GCP they don't have a context that they can use to guess an appropriate name, but perhaps we do.

Yes, I like using the module name. How about module name plus a random string. e.g. my-module-[some random string] to avoid collisions (if they do it multiple times on their same module)
Henhouse creates something like this:
starting-account-j0v866a5l5q5

(or timestamp instead of a random string)

merged - I'll add the default service account name logic (plus other validation) in the next PR

Actually, service account names don't have to be unique. So the module name would work just fine. The key itself though can be the module name plus a timestamp.


added more information to package.json

Updated package.json this should remove warnings when using reselect.

Cool, thank you!

Thanks for merging. Could you publish a new version of the reselect that the changes are reflected on https://www.npmjs.com/package/reselect

I can't, but I know a man who can! @faassen

I just did a 0.0.2 release. I also gave @ellbee access to do releases on npm. For some reason the README.md doesn't show up on the npm repo, I don't know why but I'll create an issue for it.

Everything is fine just took a bit longer: https://www.npmjs.com/package/reselect


SW-5673 Don't update all project countries

Fix a bug in project accelerator details editing that caused the country codes of
all projects to be updated.

#2214  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sgrimm and the rest of your teammates on  Graphite


Unable to build Android app

This happened after I ran ./gradlew buildRelease in android folder.
> Configure project :react-native-reanimated
No AAR for react-native-reanimated found. Attempting to build from source.
Android gradle plugin: 4.2.2
Gradle: 6.9

> Task :app:bundleReleaseJsAndAssets
warning: the transform cache was reset.
                    Welcome to Metro!
              Fast - Scalable - Integrated

Failed to construct transformer:  Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:69:19)
    at Object.createHash (node:crypto:138:10)
    at stableHash (F:\sides\navigator-app\node_modules\metro-cache\src\stableHash.js:19:8)
    at Object.getCacheKey (F:\sides\navigator-app\node_modules\metro-transform-worker\src\index.js:593:7)
    at getTransformCacheKey (F:\sides\navigator-app\node_modules\metro\src\DeltaBundler\getTransformCacheKey.js:24:19)
    at new Transformer (F:\sides\navigator-app\node_modules\metro\src\DeltaBundler\Transformer.js:48:9)
    at F:\sides\navigator-app\node_modules\metro\src\Bundler.js:22:29
    at runNextTicks (node:internal/process/task_queues:60:5)
    at process.processTimers (node:internal/timers:511:9) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
error Cannot read properties of undefined (reading 'transformFile').
TypeError: Cannot read properties of undefined (reading 'transformFile')
    at Bundler.transformFile (F:\sides\navigator-app\node_modules\metro\src\Bundler.js:48:30)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at process.processTimers (node:internal/timers:511:9)
    at async Object.transform (F:\sides\navigator-app\node_modules\metro\src\lib\transformHelpers.js:101:12)
    at async processModule (F:\sides\navigator-app\node_modules\metro\src\DeltaBundler\traverseDependencies.js:137:18)
    at async traverseDependenciesForSingleFile (F:\sides\navigator-app\node_modules\metro\src\DeltaBundler\traverseDependencies.js:131:3)
    at async Promise.all (index 0)
    at async initialTraverseDependencies (F:\sides\navigator-app\node_modules\metro\src\DeltaBundler\traverseDependencies.js:114:3)
    at async DeltaCalculator._getChangedDependencies (F:\sides\navigator-app\node_modules\metro\src\DeltaBundler\DeltaCalculator.js:164:25)
    at async DeltaCalculator.getDelta (F:\sides\navigator-app\node_modules\metro\src\DeltaBundler\DeltaCalculator.js:94:16)
info Run CLI with --verbose flag for more details.

> Task :app:bundleReleaseJsAndAssets FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:bundleReleaseJsAndAssets'.
> Process 'command 'cmd'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Need help please.

Try using node version 14 or 16 @Qoyyuum


UE 5.5 Upgrade Blocked

Description
Upgrading the UDCore plugin to support Unreal Engine 5.5 is currently blocked due to an engine change.
In the UEditorActorSubsystem.h file, UNREALED_API was removed from the Initialize function, causing the following LNK2001 error --
Module.UDCoreEditor.cpp.obj: Error LNK2001 : unresolved external symbol "public: virtual void __cdecl UEditorActorSubsystem::Initialize(class FSubsystemCollectionBase &)" (?Initialize@UEditorActorSubsystem@@UEAAXAEAVFSubsystemCollectionBase@@@Z)

While Initialize isn't being used in the conflicting UDCoreEditorActorSubsystem header file, the linker error persists.
I am currently looking into addressing this issue.
Additional Information
Essentially, the missing UNREALED_API macro is causing the linker error.
Pre Unreal Engine 5.5
UNREALED_API virtual void Initialize(FSubsystemCollectionBase& Collection) override;

Unreal Engine 5.5
virtual void Initialize(FSubsystemCollectionBase& Collection) override;

Temporary Solution
If you are not using the UDCoreEditorActorSubsystem, you may comment out the code in UDCoreEditorActorSubsystem.h and UDCoreEditorActorSubsystem.cpp to bypass this linker error.

While there's most likely a new dependency/include that is required for the change, I have not been able to hunt it down.
Regardless, I've submitted a pull request to revert the change engine side.


Same pipeline for Vanilla USD plugins?

Hello,
We are currently building our own file format plugins for omniverse using this as a base.
Ideally, those plugins would also be working on vanilla USD for our work pipeline.
Is it possible to configure this so that it can  also build native USD plugins from the same codebase?
I'm talking about fileformat plugins to be exact.
Thank you

Apologies for the super-late response! I was not getting notifications for the repository until recently. We are working on some buildsystem boilerplate that makes it possible to build with various flavors of USD (and are also working on deprecating nv-usd so that OV at large can be compiled with stock OpenUSD). No concrete timeframe for public release yet, but thanks for your interest!

(Read too quickly) -- the file format plugins in this repository should work with stock OpenUSD v23.05 already-- internal buildsystem work is underway to make it work with a range of stock OpenUSD vYY.MM 🙏🏼


First push of new content for Phantom

This first pull of content has the Indicator Enrichment objects and the new response plans being developed for my principal project. - socologize (Rob Gresham)

closed the pull request to due to two issues with playbook folders and spec schema for the response_tasks.

closed the pull request to due to two issues with playbook folders and spec schema for the response_tasks.


Recurring payments must also include the currency feature

The user must be given an option to add recurring expenses in a currency of their choice from the list of currencies.

The feature was added successfully and the currency conversion was working as expected.


Generate and publish Maven documentation

What issue?!?

@hugotavares
I'm sorry, I don't understand your comment.

@highsource hugotavares was referring to this page:
https://github.com/highsource/maven-jaxb2-plugin/wiki/Maven-Documentation
that states we should check "this issue", that links here.
So basically, where is the documentation?

https://github.com/highsource/maven-jaxb2-plugin/wiki
Maven documentation is the scope of this issue.


typeguards for JSX elements/components

I have this component:
   class If extends React.Component<{ it: boolean; }> {
        render() {
             return this.props.it ? <>{this.props.children}<> : null;
        }
   }

here is how i use it:
   <If it={shouldBeRendered}>

Here I am

   </If>

unfortunately i cannot do the following, because the results of narrowing do not get imposed on the underlying context
    <If it={data !== null}>
         <MyComponent {...data}> // <-- data can still be `null`, doesn't typecheck
    </If>

suggestion: propagate the results of  type narrowing though the JSX markup

In the example, <MyComponent {...data}> gets evaluated before If.prototype.render is even called, so narrowing would not be correct.  What do you propose to do about that?

i am not aware of the order in which react evaluates components in the JSX tree, intuitively if sets the context for the enclosed component to be rendered or not, that's my naive understanding how it should work

The emitted code for the example is like this:
React.createElement(If, { it: data !== null },
    React.createElement(MyComponent, __assign({}, data)));

The element gets created regardless of the data !== null condition (and if you had an expression like data.x, it would crash if data is null), but the element only gets rendered if If decides to render it.  So TypeScript would have to not narrow data during the element creation, but keep track of the fact that it is non-null if the it prop to If is true.  Do you have a proposal for exactly what reasoning should be supported?

I guess it means bad luck to the idea. Too bad, because conditional rendering is essential, an the only way to do it as it turns out is to switch to awkward JS expressions.

I was looking for this, too. Would be an awesome feature, but it does look like a pretty fundamental limitation. Too bad :(.


Trying to add parameters to image request within TEI Publisher

Hello everyone,
I’m not sure it will be possible to answer my questions here, but I’ll try anyway.
I’m part of a team working to create a digital edition of a medieval manuscript. We’re using a tool called TEI Publisher  to arrange and present our edition, and TEI Publisher uses OpenSeaDragon to display the facsimile images of the manuscript. We’re trying to find a way to apply region parameters to our image requests, in order to crop out some extraneous space from the original images. IIIF provides guidelines  for how to add these region parameters to a URI string, and I’ve been able to construct a few on my own that function perfectly well when pasted into a web browser (for example, see this https://ids.lib.harvard.edu/ids/iiif/8311653/full/full/0/default.jpg  for the original image, and this https://ids.lib.harvard.edu/ids/iiif/8311653/pct:3,4,63,93/max/0/default.jpg  for the cropped version).
According to the IIIF guidelines, applying these parameters to an image request is as simple as adding the appropriate components to the end of the URI string - after the image ID but before the file format designator (in the above URLs, the “/full/full/0/default” and “pct:3,4,63,93/max/0/default” serve this function). So I originally expected that adding similar parameters to our digital edition would be simple. Except that, we haven’t been able to find a way to add these parameters within the actual edition, mainly because we can’t find any complete URI strings anywhere in our files. As best as I can figure it, TEI Publisher has split the component parts of the URI string into two pieces, each of which is being kept in a separate document. When OpenSeaDragon sends out an image request for our facsimile images, then, I suspect that it must be stitching together these component parts to get a complete string.
The first part of the request string is in our HTML template. The line of code that pertains to the facsimile images is , within which is a property called “base-URI,” which provides three of the four required pieces that make up a IIIF image request string: the scheme (https) the server (ids.lib.harvard.edu) and the prefix (ids/iiif).
<pb-facsimile id="facsimile" base-uri="https://ids.lib.harvard.edu/ids/iiif/" default-zoom-level="2" show-navigation-control="show-navigation-control" show-navigator="show-navigator" subscribe="transcription"/>
The TEI Publisher devs did confirm for me that OSD does rely on the “base-uri” element when sending out image requests. I also noticed that some of the other properties applied in this same line equate to the customizable features I see in your documentation (such as default-zoom-level, show-navigation-control, and show-navigator), which would seem to confirm that this line is key to how OSD is incorporated into TEI Publisher.
The only piece missing to make this a complete URI string, however, is the unique image identifier, which appears only in our XML code under page break tags. Each  in the XML has a property “facs”, which provides the image ID for the facsimile. For example, this is the  tag for page one of our manuscript:
<pb facs="iiif:8311653"/>
My first thought, when I first approached this problem, was to add the region parameters to this “facs” property, with the expectation that those extra characters would be added to the URI string along with the image ID, and that OSD would then process the parameters as part of the image request. However, adding anything to this tag element only results in a 404 error.
This is particularly strange, because at present our image IDs don’t end with a file designation, which sets them apart from all examples I’ve seen from IIIF, TEI Publisher, and yourselves. Based on both the guidelines from IIIF and the example code I’ve seen, it seems that any IIIF image request strings must end with a file format designation – either something like “.jpg” for an image request or “.json” for an image information request. But if I attempt to add any kind of file designation to the image IDs, or any of the parameters specified in the IIIF guidelines, to the “facs” XML element, I’m met with a 404 error.
I am very aware that my troubles in figuring out this problem likely stem from a misunderstanding of what’s going on within TEI Publisher. And I’ve tried to ask for more clarification from the TEI Publisher devs, but they seem unwilling to explain things further. They have simply identified OSD as the tool being used to request and display images, and suggested that OSD does not support IIIF’s region parameters. That explanation seems inadequate to me, given how adding parameters is portrayed in the IIIF guidelines as a standard part of an image request – and given that at least one user  has posted on this GitHub page previously about how he was able to incorporate such parameters into his IIIF request. But I don’t know how else to go about testing my theories since the code I’m working with from within TEI Publisher looks so different from that of your guidelines and documentation.
If there’s anything you notice about what I’ve written here that might suggest how OSD is managing image requests within this platform, or where I might be going wrong in my understanding of the image request process, I would greatly appreciate any help or insight.
One final piece of the puzzle I should mention is a line in our ODD (or “One Document Does it all,” which is the file that instructs the TEI Publisher viewer on how to render specific XML tags within the viewer interface). In this file, there is an element specification related to the  element in our XML, describing how these page breaks should be rendered:
<elementSpec ident="pb" mode="change">
                    <model output="epub" behaviour="break" useSourceRendition="true">
            <param name="type" value="'pagebreak'"/>
            <param name="label" value="(concat(if(@n) then concat(@n,' ') else '',if(@facs) then concat('@',@facs) else ''))"/>
        </model>
                    <model predicate="starts-with(@facs, 'iiif:')" behaviour="webcomponent">
            <param name="name" value="'pb-facs-link'"/>
            <param name="content" value="@n"/>
            <param name="facs" value="replace(@facs, '^iiif:(.*)$', '$1')"/>
            <outputRendition xml:space="preserve">
                            font-size: 16px;
                            color: #888888;
                            cursor: pointer;
                            display: inline;
                            display: block;
                            margin-right: -32px;
                            float: right;
            </outputRendition>
        </model>
                </elementSpec>

Although I don’t know enough about how the XML code in an ODD file works, it appears to me like the line <param name="facs" value="replace(@facs, '^iiif:(.*)$', '$1')"/> may have something to do with how OSD knows to add the image ids to the base URI to construct a complete image request.

Thank you for writing up such thorough notes!
Judging by issue https://github.com/openseadragon/openseadragon/issues/1793, OSD does not yet support passing through selectors like pct:3,4,63,93. Evidently there is some interest in that, but no one has stepped up to implement it.
One of the suggestions from that issue could point a way to getting the result you want, though... you could load the full image and then use OSD's clipping feature to crop out the bits you don't want. It looks like the numbers in pct:3,4,63,93 are percentages for left, top, width, height, so those can be used to generate the clip. Here's an example:
var url = 'https://ids.lib.harvard.edu/ids/iiif/8311653/info.json';
var leftFactor = 0.03;
var topFactor = 0.04;
var widthFactor = 0.63;
var heightFactor = 0.93;

viewer.open(url);

// We have to wait until the viewer has opened the image in order to access the image and get its size
viewer.addHandler('open', function() {
    // Get the image; there's only one so we know it's item 0
    var tiledImage = viewer.world.getItemAt(0);

    // Find out the image's full size in pixels
    var size = tiledImage.getContentSize();

    // Figure out the clipping bounds in image coordinates
    var left = Math.round(size.x * leftFactor);
    var top = Math.round(size.y * topFactor);
    var width = Math.round(size.x * widthFactor);
    var height = Math.round(size.y * heightFactor);
    var clipBounds = new OpenSeadragon.Rect(left, top, width, height);
    tiledImage.setClip(clipBounds);

    // Now that we've clipped it, the new home bounds are matched to the visible area; we can use
    // goHome to take us there (passing true to bypass the usual animation)
    viewer.viewport.goHome(true);
});

That's in vanilla OSD, of course... I'm not familiar with TEI at all, so I can't say how to integrate it there.
One thing to be aware of with this technique is that you're still sending the data for the bits that have been clipped out, so it's a little less efficient than just grabbing the region of interest, but I think in practice it won't make that much difference in terms of loading speed.
BTW, you pointed to https://github.com/openseadragon/openseadragon/issues/1400 as someone who had used the pct successfully. The way they did it is to ignore the tile pyramid that IIIF provides and instead load the entire full-res image as a single tile using the "simple image" tile source rather than the IIIF tile source. You can do that like so if you want:
viewer.open({
  type: 'image',
  url: 'https://ids.lib.harvard.edu/ids/iiif/8311653/pct:3,4,63,93/max/0/default.jpg'
});

This has the disadvantage of loading the entire image at once, which can be slow for big images. The image above is only 2268 × 3591 pixels, so it's probably not too big of a deal, as long as you're just showing one of these pages at a time. If you do have larger images or if you're planning on showing a number of them at the same time, you wouldn't want that.
One halfway point would be to use the legacy tile source, which allows you to manually specify a pyramid, but not individual tiles at any layer in the pyramid. This might make sense if you have a lot of images you want to show at the same time; you can specify a low-res pyramid level for when you are zoomed out looking at all of them. You would need to already know the dimensions of the image before loading the image, and you would need to know how to tell the IIIF server to give you low-res versions.
I hope this gives you some possible leads to work with!

Thank you so much for the detailed response!
Thanks for bringing my attention to issue #1793 – I only wish I were proficient enough with any of these tools to volunteer to work on this!
Both suggestions you make (calling the full image and using OSD to crop it, and loading the entire image as a single tile) sound like they could work for the purposes of my team’s project - assuming, as you mentioned, that TEI Publisher can support it. As I don’t know much about its inner workings either, I’ll have to take what you’ve given me and show it to them to see what the possibilities are.
Regardless, I really appreciate the help!

Sounds like a plan... good luck!


Missing references

Even after adding every single DLL from the latest release of Nuclex Framework on CodePlex archive, as well as a port of NuclearWinter for MonoGame, multiple types fail to be identified in Visual Studio 2017.
Missing types include:

MeshInstance
MeshInstanceGroup
Scene
PointLight
Model (Microsoft.Xna.Framework.Model does not work: "'Model' does not contain a definition for 'MeshInstanceGroups' [...]")

I find no other way to contact you. Could you ping me a message for closer collaboration and questioning if that wouldn't be too much of an intrusion? I am under the pump for a small game for a project and would like to have a good brain to pick as the deadline is rather close.

<EMAIL_ADDRESS>is a good starting point for contact. If you pop me a message, I'll also send you my Discord tag or other means of contact depending on what works for you.

Hey @oasis9 were you able find a solution for the missing references? I'm trying to port it to Monogame, and I'm encountering the same issues, please let me know if you were able to figure anything out.
Cheers!


Unsupported config option for services service: 'nodechrome' on linux

When I tried to do a docker-compose up in the checkout repo I git the error:
$ docker-compose --verbose up
Unsupported config option for services service: 'nodechrome'

it turned out that the error resulted from a too old docker-compose version.
After upgrading my docker-compose version I could run the example.
$ docker-compose -v
docker-compose version: 1.3.1
CPython version: 2.7.10
OpenSSL version: OpenSSL 1.0.2d 9 Jul 2015

to:
$ docker-compose -v
docker-compose version 1.6.2, build 4d72027

Fixed with docker-compose upgrade.


[move-prover] warn on unused global invariants

If the prover finds that a global invariant is not checked
in any function, throw a warning for that invariant.
The the new unused_global_invariant.move test case for the effect of
this checking.
This fixes #9167.
Motivation
This warning is good to have and helps filter out unused specs.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
CI, new test cases added

/land

bors not picking up the command, CI build-dev step timed out on a reason does not seem to have a relation to this PR, try landing again.
/land


[AutoPR containerservice/resource-manager] ACS Python update

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5853

(message created by the CI based on PR content)

Codecov Report

Merging #5067 into restapi_auto_containerservice/resource-manager will decrease coverage by <.01%.
The diff coverage is 39.18%.

@@                                Coverage Diff                                 @@
##           restapi_auto_containerservice/resource-manager    #5067      +/-   ##
==================================================================================
- Coverage                                           49.13%   49.13%   -0.01%
==================================================================================
  Files                                                6486     6490       +4
  Lines                                              182096   182170      +74
==================================================================================
+ Hits                                                89478    89507      +29
- Misses                                              92618    92663      +45

Impacted Files
Coverage Δ

.../mgmt/containerservice/container_service_client.py
46.6% <0%> (-0.93%)
:arrow_down:

...ontainerservice/v2019_04_30/operations/__init__.py
100% <100%> (ø)
:arrow_up:

..._04_30/operations/container_services_operations.py
27.27% <27.27%> (ø)

...9_04_30/models/orchestrator_version_profile_py3.py
45.45% <45.45%> (ø)

...nerservice/v2019_04_30/container_service_client.py
40% <50%> (+0.6%)
:arrow_up:

...ls/orchestrator_version_profile_list_result_py3.py
50% <50%> (ø)

...mt/containerservice/v2019_04_30/models/__init__.py
53.48% <50%> (-0.27%)
:arrow_down:

...ice/v2019_04_30/models/orchestrator_profile_py3.py
55.55% <55.55%> (ø)

... and 2 more

Continue to review full report at Codecov.

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

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/5009


decimal to binary calculator added

Decimal to Binary conversion

in this calculator we can convert positive decimal number in to binary.
this calculator made by using html, css and js.

Similar one is already there!
please find this message: https://github.com/vasu-1/CalcHub/pull/372#issuecomment-1296073646


Combine nanopb scripts into a single location

This PR does 2 things:

Unites all nanopb generation scripts into one folder, with the exception of Firestore.
Fixes the generator to always use repo-relative includes, eg. #include "x.nanopb.h" => FirebaseX/Nanopb/x.nanopb.h. This fixed a problem in FirebaseSessions include

Firestore has a much more complicated setup that I didn't have time to figure out. Most products have 1 or 2 protos, but Firestore has many, and they seem to be hooked up to CMake in some way.
Validation
To validate all these scripts produce the same code, I deleted all the resulting .nanopb.c/h files, and ran the generators for all the affected SDKs. The only changes should be in copyright headers and the version of nanopb used. The generated source should stay the same.

# Ran the following:

./Crashlytics/ProtoSupport/generate_crashlytics_protos.sh &&
./FirebaseInAppMessaging/ProtoSupport/generate_nanopb_protos.sh &&
FirebaseMessaging/ProtoSupport/generate_protos.sh &&
FirebasePerformance/ProtoSupport/generate_protos.sh &&
FirebaseSessions/generate_protos.sh

The resulting changes have been included in this PR
There is one change in the FIAM proto, that I've commented about below
#no-changelog

Need to do Firestore too

Looks like FIAM wasn't updated when others were.

@paulb777 do you mean that it wasn't updated to a new nanopb version? Do you have any worries with that ENUM => UENUM change?

No concerns. Your change aligns the proto generation with the library being linked with.


[UIE-94] Fix package imports by building packages with Vite

Alternative to #4114.
Background
We want to publish Terra UI packages as "dual packages" with both ES Module and CommonJS versions. Currently, we do that, with ES Modules in lib/es and CommonJS in lib/cjs.
What we have works well enough for Vite, which we use for building Terra UI. It doesn't work out of the box with Webpack, but it can be made to work with some Webpack configuration as we found in https://github.com/all-of-us/workbench/pull/7868.
However, it does not work with Node's module resolution. Terra UI packages can neither be imported nor required from Node. That's unfortunate because the Node REPL is a nice place for devs to explore packages. And it's a problem because other tools may rely on Node's module resolution (TypeScript with moduleResolution set to NodeNext, etc).
Node distinguishes ES Modules from CommonJS modules by file extension. .mjs files contain ES Modules, .cjs files CommonJS. The default for .js files is determined by the type field in package.json. By default, .js files are CommonJS, with type: "module" in package.json, they are treated as ES Modules.
Currently, we have type: "module" set in package.json, but all files (both ESM and CommonJS) have .js extensions. This prevents requireing Terra UI packages in Node (see error below).
Also, ES Modules require fully specified imports (imports must have file extensions). Extensions are currently omitted from imports in the package source files, so importing Terra UI packages also fails (see error below).
Both of those issues are related to our use of tsc to build packages. See #4114 for a description of how they are related and how they can be worked around while still using tsc.
Why not tsc?
The tsc solution in #4114 has some issues. Specifying .js extensions for imports from .ts files is confusing for developers and incompatible with some tools, such as ESLint's import/extensions rule. Jest also can't resolve them. Those issues can be worked around with a custom ESLint rule and Jest resolver, but it's a sign that that approach makes the entire dev stack more brittle.
Vite
Unlike tsc, other tools such as Vite can output to different file names and rewrite imports. Using Vite, we can write ES Modules to .js files and CommonJS modules to .cjs files.
This PR changes packages to be built with Vite. Since the Vite configuration to do so ended being non-trivial, it is placed in a shared build-utils package that other packages depend on.
The basics of the Vite configuration are taken from Vite's "Library Mode" documentation. I chose to deviate from the default setup by not bundling or minifying the build output. This required some configuration in the rollupOptions section. This makes the build output easier to read if consumers looks at the code in their node_modules directory, make stack traces clearer, and generally make it easier for consumers to understand the Terra UI packages.
Next, TypeScript type declarations are added to the build output using @rollup/plugin-typescript. This actually ends up generating the type declarations twice (once for the ESM build and once for the CommonJS build). Alternatively, we could generate type declarations using tsc. But keeping it in the Vite configuration makes it easier to share between packages, makes build/dev scripts simpler, allows us to take advantage of Vite's watching to rebuild types when source files change, and allows us to fail the Vite build if there are type errors.
Since these packages are intended to be consumed via NPM as part of an application with it's own build/bundle process, we want to mark all packages dependencies as "external" so that they're not included in the build output. I ran into an issue where the build output would contain resolved paths to dependencies (import { ... } from '/path/to/terra-ui/.yarn/cache/.../node_modules/package/index.js';) instead of the original import (import { ... } from 'package';). I didn't dig too much into this, I assumed it's related to using Yarn PnP. I found some related StackOverflow posts and adapted those into a Vite plugin to preserve the original imports. This does affect cases where we import a specific file from within a 3rd party library (lodash/fp the most common place we do this). The original import is preserved, but it needs a file extension to work in ES Modules. As a workaround, this uses the output.paths configuration to rewrite imports from lodash/fp to lodash/fp.js.
Note
This impacts the development workflow. yarn start no longer watches and rebuilds packages as well as the app. Each package being worked on must be watched separately using for exampleyarn workspace '@terra-ui-packages/components' dev.
Before
$ yarn node
Welcome to Node.js v18.10.0.
Type ".help" for more information.
> await import('@terra-ui-packages/components')
Uncaught:
Error: Qualified path resolution failed: we looked for the following paths, but none could be accessed.

Source path: /Users/nwatts/workspace/terra-ui/.yarn/__virtual__/@terra-ui-packages-components-virtual-3cbce82a85/1/packages/components/lib/es/Interactive
Not found: /Users/nwatts/workspace/terra-ui/.yarn/__virtual__/@terra-ui-packages-components-virtual-3cbce82a85/1/packages/components/lib/es/Interactive

    at makeError (/Users/nwatts/workspace/terra-ui/.pnp.cjs:26071:34)
    at resolveUnqualified (/Users/nwatts/workspace/terra-ui/.pnp.cjs:27843:13)
    at resolveRequest (/Users/nwatts/workspace/terra-ui/.pnp.cjs:27884:14)
    at Object.resolveRequest (/Users/nwatts/workspace/terra-ui/.pnp.cjs:27940:26)
    at resolve$1 (file:///Users/nwatts/workspace/terra-ui/.pnp.loader.mjs:1989:21)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:837:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
> require('@terra-ui-packages/components')
Uncaught:
Error: require() of ES Module<EMAIL_ADDRESS>not supported.
Instead change the require of index.js in null to a dynamic import() which is available in all CommonJS modules.
    at require$$0.Module._extensions..js (/Users/nwatts/workspace/terra-ui/.pnp.cjs:26323:15)
    at Module.load (node:internal/modules/cjs/loader:1027:32)
    at Module._load (node:internal/modules/cjs/loader:868:12)
    at require$$0.Module._load (/Users/nwatts/workspace/terra-ui/.pnp.cjs:26172:31)
    at Module.require (node:internal/modules/cjs/loader:1051:19)
    at require (node:internal/modules/cjs/helpers:103:18) {
  code: 'ERR_REQUIRE_ESM'
}

After
$ yarn node
Welcome to Node.js v18.10.0.
Type ".help" for more information.
> await import('@terra-ui-packages/components')
[Module: null prototype] {
  Interactive: {
    '$$typeof': Symbol(react.forward_ref),
    render: [Function (anonymous)]
  }
}
> require('@terra-ui-packages/components')
{ Interactive: [Getter] }
>

Should update wiki about new way of watching for changes.

Added a note about this to https://github.com/DataBiosphere/terra-ui/wiki/Getting-started#running-terra-ui.


[FEATURE] Runtime Timeout Warning Notifications not implemented

Is your feature request related to a problem? Please describe.
JobsHealth and JobsHealthRules are implemented in the Bundles Model but are missing from Brickflows Util Core (src/core/brickflow_utils.py) this means that Brickflow cannot be used to implement runtime timeout warning notifications.
Cloud Information

[x] AWS
[ ] Azure
[ ] GCP
[ ] Other
Description:
It would be nice if Brickflow Util Core included these options in the workflow and task definitions.

Describe alternatives you've considered
The alternative to this would be to not use brickflow
Additional context
health: Optional[JobsHealth] = None

Submitted https://github.com/Nike-Inc/brickflow/pull/58


Incorrect docs for modals.closeModals()

Hello,
The docs state that the first parameter for closeModals() is the options object but it's actually the target so in order to pass the options object it needs to be called like this: modals.closeModals(null, options)
Thanks for the work!

Good catch! Updated the way the script works and that one slipped through the cracks. Will update.

Fixed

https://github.com/cferdinandi/modals/pull/22


Using generator in the code gives error.

I currently started using gulp-babel in our project. so far so good, nice work.
In the gulp task
all.javascripts().pipe(babel()).pipe(gulp.dest(paths.dist));

When i used generator

var gen = function*(start, end, step){
// code...
}

in my code the compiled code give me  this error
regeneratorRuntime is not defined.

How to use babel fullest. this code works on babel editor. I see they include some polyfill.
How to tell gulp-babel to include one.
Can't this be made automatic. if Code requires some polyfill, it will do it automatically?

You can read more about the polyfill in the docs here. There's nothing special about it's usage with grunt-babel and there shouldn't really be anything specific anyway.

Can't this be made automatic. if Code requires some polyfill, it will do it automatically?

The heuristics for determining if a polyfill is required is extremely muddled. It's up to the user to specify it and it should not be an opinion imposed by default.
If you have any further questions or support queries feel free to checkout some of the resources included in the Babel README:

For questions and support please visit the Slack community or StackOverflow.

Thanks! :blush:

Thanks for the info.
This can be great value for the end user if the required polyfill will be
available by default.
naive user like me come to know about this by surprise, when they see error.
On Thu, Aug 13, 2015 at 6:07 PM, Sebastian McKenzie <
<EMAIL_ADDRESS>wrote:

You can read more about the polyfill in the docs here
https://babeljs.io/docs/usage/polyfill/. There's nothing special about
it's usage with grunt-babel and there shouldn't really be anything
specific anyway.
Can't this be made automatic. if Code requires some polyfill, it will do
it automatically?
The heuristics for determining if a polyfill is required is extremely
muddled. It's up to the user to specify it and it should not be an opinion
imposed by default.
If you have any further questions or support queries feel free to checkout
some of the resources included in the Babel README
https://github.com/babel/babel#readme:
For questions and support please visit the Slack community
https://babel-slack.herokuapp.com or StackOverflow
http://stackoverflow.com/questions/tagged/babeljs.
Thanks! [image: :blush:]
—
Reply to this email directly or view it on GitHub
https://github.com/babel/gulp-babel/issues/36#issuecomment-130654023.

--
Lokesh kumar Jain
ReachLocal Services Pvt. Ltd.
5-B | Express Zone Towers  |  Patel Vanika |  Western Express Highway |
Goregaon (E) | Mumbai – 400097
www.reachlocal.com | www.reachservices.co.in


Generate events when nodes are approved/rejected

When nodes are approved or rejected,  or connected/disconnected, the system may want to respond to these events by creating new evaluations, or cancelling previous tasks.
This PR adds an event emitter which allows implementations of NodeEventHandler to receive events that are one of:
NodeEventApproved
NodeEventRejected
NodeEventDeleted
NodeEventConnected
NodeEventDisconnected

all events are delivered in a goroutine, and so it is the recipients responsibility to handle the event quickly, or to create a new goroutine and return immediately.
Currently this PR delivers events to an event listener in the manager package which currently logs that it has received and event.  In future, we will want to modify this behaviour to create new evaluations, or stop current executions based on the node info that is delivered with the event, the job types currently deployed,  and the type of event.  To enable this, the NodeEventListener is provided with a reference to the evaluation broker and the jobstore.

@rossjones I have implemented a fix for the NodeInfo overwrite bug here: https://github.com/bacalhau-project/bacalhau/pull/3785
It was a very large mechanical change to make and sadly touched a lot of files. If it looks good to you, could we land your change  (this PR) after it to avoid conflicts? I suspect it will be easier to resolved conflicts from your change here than the other way around. However if you spot any significant issues with https://github.com/bacalhau-project/bacalhau/pull/3785 go ahead and merge this and I'll sort the conflicts on my end.

@frrist are you owning this PR now? what do we need to do to unblock it and merge it?


Support for mismatched key_padding_mask and attn_mask is deprecated

How to fix this warning ?

Warning is called in this file
models\parseq\modules.py
In your DecoderLayer class, the forward_stream function calls self.self_attn and self.cross_attn, which are instances of nn.MultiheadAttention. These functions take attn_mask and key_padding_mask as arguments. The warning indicates that the types of these masks must be the same.


Bug 1739322: Fix plugin_sysctl for tuned 2.11

Tuned 2.11 prior to commit a8f2a830 doesn't handle sysctl plugin with '<' '>'
modifiers properly resulting in program traceback and malfunction (see Red Hat
BZ1739418 for detail).
This PR adds a patch to address the issue.

The same fix worked for 4.2.0-0.nightly-2019-08-14-211610 and tuned-2.11.0-5, merging.

why was this merged without explicit cherry pick approval?

spoke with @jwforres , moving forward, this should have still done normal process.

@derekwaynecarr, /cherrypick ended up with conflicts and I had to create a normal PR against the 4.1 branch. Since the move from RHEL7.6 to RHEL7.7 broke NTO's operand due to buggy tuned 2.11, this merge could only do good rather than harm.  I wanted to have a working operator + logging that depends on it in 4.1.12, but realize I should've asked architect's approval first though -- sorry about that.

@jmencak the problem is that you clicked the 'merge' button. Do not EVER click the merge button in release-* branches. If you have some emergency in a release-* branch and believe special handling is needed please get help in #warroom-release in slack reach out to Jessica, Derek, Alex, or myself. Do not use the merge button.
If this is done again you will lose write access to all repos.

@eparis understood and appreciate the help on #warroom-op-pipeline about this issue!


Anyone can take tokens from GnosisSafeRegistry

There is no workflow that causes anything of value to end up on the GnosisSafeRegistry, so this is minor, but this can/does happen in the wild so it's worth mentioning
https://github.com/AugurProject/augur/blob/67c0fec95e65fca8d27751f28a6c06e5247978c6/packages/augur-core/source/contracts/GnosisSafeRegistry.sol#L33
The callRegister, while intended to be delegatedTo from a GnosisSafe, can be executed from the GnosisSafeRegistry itself. Since all actions are taken from parameters, this means you can ask the GnosisSafeRegistry to call the following functions on any contract you want, with any parameters you want (such as your own address).

approve
setApprovalForAll
register
setFingerprint
setReferrer

Gonna wont-fix this. No funds should ever be in this contract.


Added support of fixed localhost port

Details
Added support of specify preferred localhost TCP port to use by website service
Remove node --prefix option
Pull request checklist

[ ] Addresses an existing issue: Fixes #0000
[x] Added relevant unit test for your changes. (yarn test)
[ ] Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
[ ] Ran precheckin (yarn precheckin)

Codecov Report

Merging #592 (4bac712) into main (bbadd7b) will increase coverage by 0.09%.
The diff coverage is 90.00%.

@@            Coverage Diff             @@
##             main     #592      +/-   ##
==========================================
+ Coverage   92.54%   92.63%   +0.09%
==========================================
  Files          25       25
  Lines         550      557       +7
  Branches       51       53       +2
==========================================
+ Hits          509      516       +7
  Misses         29       29
  Partials       12       12

Impacted Files
Coverage Δ

src/task-config.ts
93.47% <75.00%> (+0.29%)
:arrow_up:

src/local-file-server.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Implemented the HomeKit Data Stream protocol

This is part one of two PRs (Spoiler alter: part two will add support for Siri remotes. I'm finishing the last bits on that one).
This PR implements full support for HomeKit Data Streams.
The API is currently intended as follows:

Step 1: You would create a new instance of the DataStreamManagement class and add the service returned by getService() to your accessory
Step 2: finished

If an HomeKit Hub detects a combination of supported services it will create a connection.
You could then create some listeners for certain event messages with the respective protocol name (for example the whoami event message of the targetControl protocol. This is what the SiriRemote uses to identify DataStream sessions) or listen to more general events like CONNECTION_OPENED or CONNECTION_CLOSED to get a reference to an open data stream connection.
Once you got a reference to an DataStreamConnection you can add protocol handlers to that specific connection or send event, request or response messages.
As the HomeKit DataStream protocol supports different sized ints (int8, int16, int32, int64) I introduced some wrapper classes in DataStreamParser.ts (and also for some other data types) to mark how to encode the javascript number type. By default a number is encoded in the smallest possible type.
Also, as we have a minimum requirement of node v4 for the project currently, writing int64 isn't really supported. And also reading is a bit hacky but it seems to work (however we only really support 53 bit ints). The javascript bigint type is only support for node v10. The end goal would be to move to that data type (maybe?).
But feedback for any better solution to this problem is welcomed.

rebased onto master

rebased onto master (again)

Looks really cool ^^ Regarding int64 problem, if we really want, maybe expose those as Decimal using the bundled decimal.js?

And thanks for implementing HDS 🙏


zooming/panning keys should work in all tool modes

In the slice views, we have ctrl+click to zoom and shift+click to pan. That's great but it seems to turn off we select the zoom tool or the pan tool respectively. So:

if the zoom tool is selected, then ctrl+click no longer works for zooming
if the pan tool is selected, then shift+click no longer works for panning

Sure when the tool is selected you don't strictly need the extra hotkey for it, but the hotkey should still work because people will naturally try to use it.

Additionally, combined (interleaved) action of zooming and panning is difficult as its not mapped to mouse keys (have to switch between them using toolbox or switching between ctrl / shift is not intuitive).
This is just a suggestion but the default mouse actions could be as follows:

left click drag - fast scrolling
middle click drag - panning
right click drag - window/level grayscale adjustment
ctrl + left click drag - zooming
wheel - slow scrolling

Of course, this assumes that a full featured mouse is available. For the rare cases when someone is using a touchpad / laptop, individual toolbox buttons are still available.

https://www.radiantviewer.com/dicom-viewer-manual/mouse_functions.html
https://www.medfordradiology.com/wp-content/uploads/2017/06/IT-Synapse_4_4_Quick_Guide.pdf

Related to #207 for documenting mouse controls.

Also look at:

OsiriX vewer
OHIF (for 2D views)
meddream softneta web dicom viewer


Support for Openshift 3.7+ (kube 1.7/1.9)

Openshift 3.7 / 3.9 has integrated prometheus. will it be supported?

@alekonko As long as the exporters within the openshift k8s environment are present it should function correctly


Implicit cast from any-object

TypeScript Version:  2.2.2 / test also in www.typescriptlang.org/play
Code
// There is code in 3rd party js-source:
//
// ThirdPartyType = function () {};
// ThirdPartyType.prototype.method1 = function() {};
// function ThirdPartyGlobalFunction(thirdPartyTypeVariable) {
//    thirdPartyTypeVariable.method1();
// }
//

declare class ThirdPartyType { }

declare function ThirdPartyGlobalFunction(p: ThirdPartyType);

class MyType extends ThirdPartyType {
    field1: number;
}

function foo(bar: MyType) {
    ThirdPartyGlobalFunction(bar); // There will be error because bar is not ThirdPartyType and do not have "method1"
}

function fooOverride(a: number) {
    foo({ field1: a });
}

Expected behavior:
Actual behavior:
function fooOverride compiles into:
function fooOverride(a) {
    foo({ field1: a }); // There is should be implicit cast to MyType
}

https://github.com/Microsoft/TypeScript/wiki/FAQ#what-is-structural-typing

I'm not entirely sure what you were expecting here, but the actual code you wrote is passing an object literal to foo. That works because as far as TypeScript is concerned, it's looking for something with the same shape as a MyType, which is anything that has a field1 property of type number. For more details, look at @HerringtonDarkholme's link.
If you were expecting TypeScript would instantiate a MyType for you and initialize field1 with a, that's actually not something that TypeScript does. Specifically, TypeScript avoids type-driven emit. You may need to familiarize yourself with JavaScript classes to get a better handle on this as well.

I write more simple example
class MyType {
    field1: number = 0;
}

function foo(bar: MyType) {
    console.dir(bar);
}

foo(new MyType());
foo({ field1: 1 });

Console output: https://i.imgur.com/E1t3kGv.png
I understand about "structural typing" in TypeScript. But what is the point talk that "new MyType()" and "{ field1: 1}" is the same type in TypeScript if after compilation in JS second object lost relation to MyType?
It's "succesfull compilation"-trap.


Detox Recorder can't read configuration from detox.config.js

Describe the Bug
DetoxRecorder only search package.json for configuration
To Reproduce
When the detox configuration is not in package.json but in detox.config.js, the detox recorder command can't find the configuration and return failure.
Expected Behavior
Detox Recorder can read configuration from different configuration files as described here
Actual Behavior
detox recorder --configuration "ios" --outputTestFile "./e2e/RecordedTest.js" --testName "DetoxRecordedTest" --record
Unable to find “detox” object in package.json. See “detox recorder --help” for usage.

Hmm, will take a look, thanks. Recorder is supposed to be familiar with all the config files Detox can work with.
https://github.com/wix/DetoxRecorder/blob/b219928ebc3532ae3be8650c0a27c5ff2c8b317d/DetoxRecorder/DetoxRecorderCLI/main.swift#L134

Hmm, will take a look, thanks. Recorder is supposed to be familiar with all the config files Detox can work with.
https://github.com/wix/DetoxRecorder/blob/b219928ebc3532ae3be8650c0a27c5ff2c8b317d/DetoxRecorder/DetoxRecorderCLI/main.swift#L134

Could you please run the following command in a separate Terminal and paste the output?
log stream --level debug --style compact --predicate "subsystem=='DetoxRecorder'"

Thanks

Could you please run the following command in a separate Terminal and paste the output?
log stream --level debug --style compact --predicate "subsystem=='DetoxRecorder'"

Thanks

Ping
Thanks

Ping
Thanks

hi,
below are the output:
log stream --level debug --style compact --predicate "subsystem=='DetoxRecorder'"
Filtering the log data using "subsystem == "DetoxRecorder""
Timestamp               Ty Process[PID:TID]
2021-01-26 14:23:49.401 I  DetoxRecorderCLI[66458:821b34] [DetoxRecorder:CLI] Parsing arguments
2021-01-26 14:23:49.402 I  DetoxRecorderCLI[66458:821b34] [DetoxRecorder:CLI] Attempting to discover Detox config file

hi,
below are the output:
log stream --level debug --style compact --predicate "subsystem=='DetoxRecorder'"
Filtering the log data using "subsystem == "DetoxRecorder""
Timestamp               Ty Process[PID:TID]
2021-01-26 14:23:49.401 I  DetoxRecorderCLI[66458:821b34] [DetoxRecorder:CLI] Parsing arguments
2021-01-26 14:23:49.402 I  DetoxRecorderCLI[66458:821b34] [DetoxRecorder:CLI] Attempting to discover Detox config file

What folder are you running the detox recorder command?

What folder are you running the detox recorder command?

the project root folder, where there are package.json and detox.config.js

the project root folder, where there are package.json and detox.config.js

I'm having the same issue 'Unable to find “detox” object in package.json. See “detox recorder --help” for usage.'.
In my situation, the configuration is in .detoxrc.js
With copying the device configuration to package.json I managed to make it work for now. But I do prefer not to have this configuration in package.json as we have a lot of devices, so it is nicer to generate the configurations from several arrays

I will take a look now. Apologies for the delay.

Can you please post your config file? If it's not a valid JSON file, Detox Recorder cannot read it.

I stripped it down to this snippet and even with that is does not work:
`const configurations = {
"ios.sim.debug": {
"binaryPath": "ios/build/Build/Products/Debug-iphonesimulator/tmobileBenReactNative Test.app",
"build": "xcodebuild -workspace ios/tmobileBenReactnative.xcworkspace -scheme "tmobileBenReactnative Test" -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build",
"type": "ios.simulator",
"device": {
"type": "iPhone 11 Pro"
}
},
};
const exportConfigs = {
configurations: {
...configurations,
}
}
module.exports = exportConfigs;`

stripping out all the javascript and replacing it by the resulting json did make the recorder able to run it. So does the .js files get executed before they are checked?

That is not a valid json file.
Your config file needs to pass this:
http://json.parser.online.fr/
Detox Recorder is not a JS environment. It reads the configuration file as a JSON file, and if unable to parse it, it stops. I will improve the error to explain why it fails.

normal detox does allow the config file to be javascript, so why is there this difference?

Because Detox runs in Node, while Detox Recorder is a native macOS CLI tool, no JS environment.

The following error will be presented when attempting to read an unsupported JSON file:
Unable to read /Users/lnatan/Desktop/Code/Detox/detox/test/detox.config.js: The data couldn’t be read because it isn’t in the correct format. The config file must be in JSON format. See “detox recorder --help” for usage.

1.0.150 out with the error above.

Hi everyone,
Were you able to resolve this issue?


Update Code - Proof_Of_Contribution.md

Thanks for the contribution. Next time include the hour request at the same time as the code contribution. Se best practices.
https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS README FIRST!/8.Code Contributor Best Practices.md

There is a merge conflict. I'll merge this manually.


Login splash screen text change

@aleffert  please review.

:+1: In the future, new UI strings will need comments for translators. I have a PR coming that adds them to all existing comments.


1.21.0 services list doesn't have console option

Question:
Version 1.21.0
Services list doesn't have console option.
1.21.0:

There used to be a console option on it which is very useful.
1.20.2:

Was this a bug or remove on purpose? Thanks.

Hi there,
That was a bug in previous versions of Portainer (described here #2765 ) that was fixed in the latest version. You need to connect to an agent 'type' endpoint for you to use these options, they will not show when connected to the Docker socket on a 'local' endpoint.


Responsiveness

Not responsive in all the devices

Can you provide a screenshot?

The second file is altered as I was working on it....but yes landscape mode
has issues
On Mon, 8 Jun, 2020, 2:21 pm Urmil Shroff<EMAIL_ADDRESS>wrote:

Can you provide a screenshot?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nowmozillaclub/eldersconnect-senior/issues/14#issuecomment-640464661,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APXKSIMQPX2RLPBA4LTXGJLRVSRBRANCNFSM4NWELKKA
.

Is this being worked on or is it done?

Working on it
On Sat, 4 Jul, 2020, 6:18 am Varun Khatri<EMAIL_ADDRESS>wrote:

Is this being worked on or is it done?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nowmozillaclub/eldersconnect-senior/issues/14#issuecomment-653702269,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APXKSIMN6KAW4FWHOCCJZB3RZZ36RANCNFSM4NWELKKA
.


Release v1.3.0

Codecov Report

Merging #88 (c9dbbc5) into main (c3ef9da) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #88   +/-   ##
=======================================
  Coverage   99.94%   99.94%
=======================================
  Files          25       25
  Lines        1820     1857   +37
=======================================
+ Hits         1819     1856   +37
  Misses          1        1

Impacted Files
Coverage Δ

tests/test_fields.py
100.00% <ø> (ø)

rumydata/__init__.py
100.00% <100.00%> (ø)

rumydata/field.py
99.21% <100.00%> (ø)

rumydata/rules/cell.py
100.00% <100.00%> (ø)

rumydata/table.py
100.00% <100.00%> (ø)

tests/test_rules_cell.py
100.00% <100.00%> (ø)

tests/test_table.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Benchmarking utility

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
This might be too early, but I am curious on how software benchmarking is handled. I got to know redis has a redis-benchmark utility. Can we have benchmarking utility for dice as well. This feature might not be urgent but I am curious to look into this.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

We are leveraging Go Benchmarking utility and developed lot many benchmarking test cases. Closing this issue.


Workbench: optional generator startup

Workbench changes:

add --no-generator to start-cluster, to skip the automatic tx-generator startup
add --help to start-cluster

We should work in increasing familiarity with the workbench inside the team -- including its concepts and principles.
It's easy to misinterpret things otherwise.

bors r+


No information found for components with a group

My CycloneDX includes components like
    {
        "type": "library",
        "bom-ref": "<EMAIL_ADDRESS>        "group": "@emotion",
        "name": "react",
        "version": "11.11.3",
        "purl"<EMAIL_ADDRESS>    },

Parly doesn't find any information for this component when using ecosystems enrich.
For other components like
    {
        "type": "library",
        "bom-ref"<EMAIL_ADDRESS>        "name": "regenerator-runtime",
        "version": "0.14.1",
        "purl"<EMAIL_ADDRESS>    },

Parlay finds additional information.
The only differences is the group in the first kind of components. Do you have any idea, why it is not working with the group?

Hey @StefanFl just letting you know that we've identified the bug and opened a PR to fix this, which we will merge and release soon. Thanks for reporting this!

This has now been released in https://github.com/snyk/parlay/releases/tag/v0.2.3.

Awesome, thank you very much


[Improvement] Periodically output a list of running apps in coordinator side

Code of Conduct

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

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
Periodically output a list of running apps in coordinator side, for better finding the running apps to analyze
How should we improve?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Feel free to pick up this ~

There may be many applications in the production environment. It's a risky operation.


[BUG] InterpreterError when executing the tutorial

Required prerequisites

[X] I have read the documentation https://camel-ai.github.io/camel/camel.html.
[X] I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
[X] Consider asking first in a Discussion.

What version of camel are you using?
0.1.1
System information
print(sys.version, sys.platform):
3.10.13 | packaged by Anaconda, Inc. | (main, Sep 11 2023, 13:24:38) [MSC v.1916 64 bit (AMD64)] win32
print(camel.__version__):
0.1.1
Problem description
The full error print is: InterpreterError: Evaluation of the code stopped at node 2. See: The variable print is not defined. when executing the example of Introduction to CodePrompt Class executing the code step.
I have installed Camel with conda following the instructions of the README. I understand what the error says, it mistakes print with a variable. But, why does it happen? I have searched over the web and haven't found anything.
Reproducible example code
The Python snippets:
from camel.prompts import CodePrompt

code_prompt = CodePrompt("a = 1 + 1\nb = a + 1\nprint(a,b)", code_type="python")
output = code_prompt.execute()

Steps to reproduce:

Import library
Define code prompt
Execute code

Traceback
---------------------------------------------------------------------------
InterpreterError                          Traceback (most recent call last)
File c:\Users\Adem.ait\AppData\Local\miniconda3\envs\camel\lib\site-packages\camel\utils\python_interpreter.py:128, in PythonInterpreter.execute(self, code, state, fuzz_state, keep_state)
    127 try:
--> 128     line_result = self._execute_ast(node)
    129 except InterpreterError as e:

File c:\Users\Adem.ait\AppData\Local\miniconda3\envs\camel\lib\site-packages\camel\utils\python_interpreter.py:185, in PythonInterpreter._execute_ast(self, expression)
    183 elif isinstance(expression, ast.Expr):
    184     # Expression -> evaluate the content
--> 185     return self._execute_ast(expression.value)
    186 elif isinstance(expression, ast.For):

File c:\Users\Adem.ait\AppData\Local\miniconda3\envs\camel\lib\site-packages\camel\utils\python_interpreter.py:167, in PythonInterpreter._execute_ast(self, expression)
    165 elif isinstance(expression, ast.Call):
    166     # Function call -> return the value of the function call
--> 167     return self._execute_call(expression)
    168 elif isinstance(expression, ast.Compare):
    169     # Compare -> return True or False

File c:\Users\Adem.ait\AppData\Local\miniconda3\envs\camel\lib\site-packages\camel\utils\python_interpreter.py:255, in PythonInterpreter._execute_call(self, call)
    254 def _execute_call(self, call: ast.Call) -> Any:
--> 255     callable_func = self._execute_ast(call.func)
    257     # Todo deal with args

File c:\Users\Adem.ait\AppData\Local\miniconda3\envs\camel\lib\site-packages\camel\utils\python_interpreter.py:213, in PythonInterpreter._execute_ast(self, expression)
    211 elif isinstance(expression, ast.Name):
    212     # Name -> pick up the value in the state
--> 213     return self._execute_name(expression)
    214 elif isinstance(expression, ast.Subscript):
    215     # Subscript -> return the value of the indexing

File c:\Users\Adem.ait\AppData\Local\miniconda3\envs\camel\lib\site-packages\camel\utils\python_interpreter.py:290, in PythonInterpreter._execute_name(self, name)
    289 elif isinstance(name.ctx, ast.Load):
--> 290     return self._get_value_from_state(name.id)
    291 else:

File c:\Users\Adem.ait\AppData\Local\miniconda3\envs\camel\lib\site-packages\camel\utils\python_interpreter.py:435, in PythonInterpreter._get_value_from_state(self, key)
    434 else:
--> 435     raise InterpreterError(f"The variable `{key}` is not defined.")

InterpreterError: The variable `print` is not defined.

During handling of the above exception, another exception occurred:

InterpreterError                          Traceback (most recent call last)
Cell In[11], line 2
      1 code_prompt = CodePrompt("a = 1 + 1\nb = a + 1\nprint(a,b)", code_type="python")
----> 2 output = code_prompt.execute()

File c:\Users\Adem.ait\AppData\Local\miniconda3\envs\camel\lib\site-packages\camel\prompts\base.py:61, in return_prompt_wrapper.<locals>.wrapper(*args, **kwargs)
     50 def wrapper(*args: Any, **kwargs: Any) -> Union[Any, str]:
     51     r"""Wrapper function that performs the conversion to :obj:`TextPrompt`
     52         instance.
     53
   (...)
     59         Union[Any, str]: The converted return value.
     60     """
---> 61     result = func(*args, **kwargs)
     62     if isinstance(result, str) and not isinstance(result, cls):
     63         return cls(result)

File c:\Users\Adem.ait\AppData\Local\miniconda3\envs\camel\lib\site-packages\camel\prompts\base.py:197, in CodePrompt.execute(self, interpreter, user_variable)
    195 if not interpreter:
    196     interpreter = PythonInterpreter(action_space=globals())
--> 197 execution_res = interpreter.execute(self, fuzz_state=user_variable,
    198                                     keep_state=True)
    199 return execution_res, interpreter

File c:\Users\Adem.ait\AppData\Local\miniconda3\envs\camel\lib\site-packages\camel\utils\python_interpreter.py:136, in PythonInterpreter.execute(self, code, state, fuzz_state, keep_state)
    132     msg = (f"Evaluation of the code stopped at node {idx}. "
    133            f"See:\n{e}")
    134     # More information can be provided by `ast.unparse()`,
    135     # which is new in python 3.9.
--> 136     raise InterpreterError(msg)
    137 if line_result is not None:
    138     result = line_result

InterpreterError: Evaluation of the code stopped at node 2. See:
The variable `print` is not defined.

Expected behavior
The expected behavior should be, as the tutorial shows, the following:
code_prompt = CodePrompt("a = 1 + 1\nb = a + 1\nprint(a,b)", code_type="python")
output = code_prompt.execute()
# Running code? [Y/n]: y
print(output)
# >>> 2 3

Additional context
No response

Hey @ademait ,
thanks for the issue, seems the code was not executed in a standard Python environment, please take a try with our recommended poetry install as below
# Make sure your python version is later than 3.9
# You can use pyenv to manage multiple python verisons in your sytstem

# Clone github repo
git clone https://github.com/camel-ai/camel.git

# Change directory into project directory
cd camel

# Activate camel virtual environment
poetry shell

# Install camel from source
# It takes about 90 seconds to resolve dependencies
poetry install

# Or if you want to use all other extra packages
poetry install --with dev,docs -E all

# Run your code

# Exit the virtual environment
exit

Hey @ademait ,
I will close this issue, if it's still not working you can re-open it, thanks!


to_openmm combine_nonbonded_forces docstring default out-of-date

Description
Just passing by and noticed a kwarg default was out-of-date in the docstring:
https://github.com/openforcefield/openff-interchange/blob/d5ecdb7e6def38984fb213eed4929d21f5609a47/openff/interchange/components/interchange.py#L410-L419

Thanks! I thought pydocstyle detected this mismatch, but now I'm not so sure ...


Cache file system, and file contents

File system data and contents can be cached. Is blocked by the requirement to open and refresh the file tree :)
Also needs additional permission UX flow.

Your session has been reloaded <button className="solid small success">Refresh file tree</button><button className="solid small default">Reset session</button>


Add word Abduct

Add all the definitions of 'Abduct' in a file named Abduct.json in folder A.

Can I please be assigned this issue?


Add a command line "batch" mode

I need to process a folder with lots of files. In this case, I am not really interested in the generated XML files, but I want to have a report of all the warnings.
I was going to write some tmp code to do that, but why not making this available in the library instead?
It will probably use a conf file (simpe properties file) and use multi-threading to speed things up...

Done, all the code is in a single class: BatchProcessor.
Here is an example of how to run it:
java -cp naaccr-xml-x.x-all.jar org.naaccr.xml.BatchProcessor options.properties
See the code itself for a description of the properties.
I want to add this in the readme file before closing the issue...

Done.


We need some method to track which Cantus IDs have been merged

Directly related to https://github.com/DDMAL/CantusDB/issues/877. For each Chant object in the database, it would be a good idea to keep track of each cantus_id it has had in the past. In case there is a problem with Cantus Index's https://cantusindex.org/json-merged-chants API, this would allow us to roll back erroneous changes.
There are several ways I can imagine setting this up.
One way would be to create a CantusIDMergeEvent model. I imagine it looking something like:
class CantusIDMergeEvent(BaseModel):
    old_cantus_id = CharField() # or ForeignKey to CantusIdentifier model?
    new_cantus_id = CharField() # or ForeignKey to CantusIdentifier model?
    applied = BoolField() # has the merge been applied yet, y/n
    date_applied = DateTimeField() # if this merge has been applied, when did it happen
    ci_timestamp = CharField() # we've asked Jan to attach a timestamp to each merge event in the
        # json-merged-chants API, which we're hoping we can use as a unique identifier. This would
        # be the time that the merge was submitted on CantusIndex, i.e., when it was posted in the
        # json-merged-chants API
    applied_by = ForeignKey(model=User)

    chants = OneToMany(model=Chant)
    sequences = OneToMany(model=Sequence)
    # when a merge occurs, we use these two fields to record which chants/sequences were affected

    # we could consider adding a apply() and revert() methods, which would switch the `cantus_id` of
    # chant/sequence in the `chants`/`sequences` from `old_cantus_id` to `new_cantus_id` and back

    # N.B.: an apply() method would certainly require more thought - is `chants` calculated when a new
    # merger gets posted to CI's API, or when we commit the merge?
    # In any case, you get the general idea.

Since we're worried about Cantus IDs being changed programmatically when new merge events get posted to https://cantusindex.org/json-merged-chants (see https://github.com/DDMAL/CantusDB/pull/1141#issuecomment-1812749551 etc.), it would be easy to create a view that lists all the chants/sequences that would be affected by a given Merge Event, and would allow Debra to approve the merge. I'm hoping this would not be too much work for Debra to press "approve" on CD as well as on CI, and this would ensure that there's always a human in the loop when we're applying changes specified by Cantus Index.
Worth noting: this record will need to be attached to individual Chant/Sequence objects, and not to CantusIdentifier objects themselves (in case we go ahead with implementing them - see https://github.com/DDMAL/CantusDB/pull/1141 and https://github.com/DDMAL/CantusDB/issues/410). In case mutiple IDs get folded into a single ID and we need to roll back a single merge event, we'll need to know which of the chants associated with the new ID needs to be reset to the earlier ID.

This looks very complicated to get right.
Store the chant ids as strings.
Use Django reversion to store model changes.
If something goes wrong, the history can be seen through the version history and reverted.
You can create a non-model based view that will analyze the output of the merge API and give a list of chants to be updated. Nothing actually needs to be stored in the database for this to happen. Simply query your database for chants matching the old id, and offer to update the chant to the new id. You could do “bulk approve” if you want, otherwise an “update chant” next to each change would serve as an implicit approval (I’m hoping only certain users would have access to this view)

I asked Debra about a bulk approve page for each merger, and she said that it wouldn't work for her workflow.

Store the chant ids as strings.

i.e., you're suggesting that we do create a CantusIDMergeEvent, but that we keep track of the chants that were affected as a list of strings?

Use Django reversion to store model changes.

i.e., if we have the list of IDs, a someone could look at all the chants and set them back to what they were before the merge event? This would also reset any other edits that may have been made since, correct?


bug: api.ListAllImages not returning all active images

Describe the bug
Before when calling the api.ListAllImages function it would return all active images, now it returns duplicates and only a fraction of the active images
To Reproduce

call function
examine values to see duplicates

Expected behavior
a unique list of all active images
Please complete the following information):

OS: macOS Monterey 12.4
Version v0.38.0

Hi @aircraft-cerier, thanks for raising this. We've raised a ticket internally to look at this. https://lacework.atlassian.net/browse/ALLY-908

Closing as this relates to deprecated api v1


Windows 11 Runner fails to Activate Unity License.

Bug description
When attempting to run a session on a windows runner, the license server fails to connect for some reason.

How to reproduce

Setup a Windows machine as a Github Runner.
Remove the 'c:' prefix from --workDir argument in the docker command for game-ci/builder
(please see my PR here: https://github.com/game-ci/unity-builder/pull/668)
Run a git action to build a simple game in Unity.
Observe licensing errors.

Expected behavior
Unity should connect and authenticate to the licensing servers and continue with the build.
Additional details
There are some potentially related issues to this here:

https://github.com/game-ci/unity-builder/issues/651
https://github.com/game-ci/unity-builder/issues/569

Hi everyone,
I encountered the same issue where the Unity licensing server fails to connect when running a session on a Windows runner using Docker. The problem seems to be due to DNS resolution issues within Windows containers.
Solution:
You need to explicitly set the DNS servers in Docker Desktop's configuration to fix this:
Open Docker Desktop Settings:
Click on the Docker icon in your system tray and select "Settings".
Edit the Docker Engine Configuration:
Navigate to the "Docker Engine" tab.
Add the "dns" configuration to the JSON settings:
Copy code
{
  "dns": ["<IP_ADDRESS>", "<IP_ADDRESS>"]
}

Note: If there are existing settings, ensure you maintain valid JSON syntax by adding commas where necessary.
Apply and Restart Docker Desktop:
Click "Apply & Restart" to save the changes.
After restarting, the containers should correctly resolve DNS queries, allowing Unity to connect to the licensing servers and proceed with the build.
Related Issues:
This fix might also help with these issues:
Windows IL2CPP build failing to activate intermittently #651
Windows IL2CPP build failing to activate ULF License #569
Hope this helps!

Hey guys,
After doing some digging, I now understand the root cause of this issue - at least for me. I decided to do some tests on Docker to see if I can directly connect to the Unity licensing Servers and alas! It fails to connect when running a session on a Windows runner using Docker. The problem seems to be due to DNS resolution issues within Windows containers.
Solution:
You need to explicitly set the DNS servers in Docker Desktop's configuration to fix this:

Open Docker Desktop Settings.
Click on the Docker icon in your system tray and select "Settings".
Navigate to the "Docker Engine" tab.
Edit the Docker Engine Configuration:

Add the "dns" configuration to the JSON settings:
{
  "dns": ["<IP_ADDRESS>", "<IP_ADDRESS>"]
}

Note: If there are existing settings, ensure you maintain valid JSON syntax by adding commas where necessary.

Click "Apply & Restart" to save the changes.

After restarting, the containers should correctly resolve DNS queries, allowing Unity to connect to the licensing servers and proceed with the build! 😄


Add consider-subscription-resource-trust

"authoritiesm" was a typo of "authorities". In any case, I removed the mention of discovered through because it is not the most important part - after all, it is really about the subscription resource.


Doesn't build on linux-5.4

Here is the last part of the error from build:
make[4]: Entering directory /usr/src/kernel/linux-stable' Building for linux_2.6   CC [M]  /usr/src/kernel/drivers/os-tools/qat/qat-1.7/quickassist/lookaside/access_layer/src/linux/icp_qa_module.o   LD [M]  /usr/src/kernel/drivers/os-tools/qat/qat-1.7/quickassist/lookaside/access_layer/src/qat_api.o   AR      /usr/src/kernel/drivers/os-tools/qat/qat-1.7/quickassist/lookaside/access_layer/src/lib.a   EXPORTS /usr/src/kernel/drivers/os-tools/qat/qat-1.7/quickassist/lookaside/access_layer/src/lib-ksyms.o   AR      /usr/src/kernel/drivers/os-tools/qat/qat-1.7/quickassist/lookaside/access_layer/src/built-in.a Building for linux_2.6   Building modules, stage 2.   MODPOST 1 modules ERROR: "osalCryptoInterfaceInit" [/usr/src/kernel/drivers/os-tools/qat/qat-1.7/quickassist/lookaside/access_layer/src/qat_api.ko] undefined! ERROR: "osalCryptoInterfaceExit" [/usr/src/kernel/drivers/os-tools/qat/qat-1.7/quickassist/lookaside/access_layer/src/qat_api.ko] undefined! ERROR: "adf_module_unload" [/usr/src/kernel/drivers/os-tools/qat/qat-1.7/quickassist/lookaside/access_layer/src/qat_api.ko] undefined! ERROR: "icpSetProcessName" [/usr/src/kernel/drivers/os-tools/qat/qat-1.7/quickassist/lookaside/access_layer/src/qat_api.ko] undefined! ERROR: "adf_module_load" [/usr/src/kernel/drivers/os-tools/qat/qat-1.7/quickassist/lookaside/access_layer/src/qat_api.ko] undefined! make[6]: *** [__modpost] Error 1 make[5]: *** [modules] Error 2 make[4]: *** [sub-make] Error 2 make[4]: Leaving directory /usr/src/kernel/linux-stable'
Copying outputs to build/linux_2.6/kernel_space
make[3]: Leaving directory `/usr/src/kernel/drivers/os-tools/qat/qat-1.7/quickassist/lookaside/access_layer/src'

Hi
Looking at the output that you provide, this looks like a QAT driver issue rather than a QAT Engine issue.  I shall refer this issue to one of my colleagues who will address it.
Regards,
paulturx

Hello,
The current QAT driver release available on 01.org  (4.7.0) does not include support for the 5.x kernel.  The next QAT driver release  (4.8.0) adds support for 5.x kernels.  This release should be posted within the next two weeks.
Best regards,
Joel

Hello,
The 4.8.0 package has been posted to 01.org.  This release should resolve the issues with the 5.x kernels.
Best regards,
Joel


refactor(e2e): improve e2e tests

Coverage remained the same at 88.052% when pulling 000d3b29d54e18dd704b4aabb8ad025c0c357817 on refactor-e2e-tests into 7fc07a7a2d610c61c27987235569be7a542e10fa on master.


AWS Aurora Serverless Data API

AWS Aurora Serverless have now a DATA API that you can execute sql statements over HTTPS
Blog
Usage
Javascript SDK Documentation
It's an EXTREMELY useful feature that many serverless developers were waiting for literally years. It's solves the problem of connections pools and counts and now serverless trend can fully embrace mysql.
How is this gonna happen? Any plan to support? Can users configure by themselves it without any update(i am stranger to insights of themysql package)

This package implements the MySQL protocol, which is defined by Oracle. What you've linked to looks like a different HTTP-based protocol, which is outside the scope of this module. I hope that answers your question :)

Yes actually you are right. This is a client for mysql protocol in a way. Thanks.


Torchscript super-resolution model  inference not working

I'm trying to use tch-rs to do inference on a model I trained in Python and successfully used for inference with the C++ API after compiling it with Torchscript. However, when doing the exact same steps on the exact same traced model with tch-rust I obtain a quite strange looking results. Here's the comparison:
C++ API

tch-rs API

model
Example: model rewritten with sequential to make sure it was as straightforward as possible:
import torch
from torch import nn

model = nn.Sequential(
        nn.Conv2d(in_channels=1, out_channels=64, kernel_size=5, padding=2),
        nn.PReLU(num_parameters=64),
        nn.Conv2d(in_channels=64, out_channels=52, kernel_size=3, padding=1),
        nn.PReLU(num_parameters=52),
        nn.Conv2d(in_channels=52, out_channels=40, kernel_size=3, padding=1),
        nn.PReLU(num_parameters=40),
        nn.Conv2d(in_channels=40, out_channels=28, kernel_size=3, padding=1),
        nn.PReLU(num_parameters=28),
        nn.Conv2d(in_channels=28, out_channels=16, kernel_size=3, padding=1),
        nn.PixelShuffle(upscale_factor=4)
    )

model.load_state_dict(torch.load("./model.pth"))
model.eval()
example = torch.rand(1, 1, 1000, 1000)
traced_script_module = torch.jit.trace(model, example)
traced_script_module.save("traced_model.pth")

inference
Rust
Example: inference relevant Rust lines
let tensor = tch::Tensor::of_slice(v32in.as_slice());
let shape: Vec<i64> = vec![1, 1, h, w];
let input = tensor.reshape(&shape);
let model = tch::CModule::load("/traced_model.pth").unwrap();
let output = input.apply(&model).squeeze();

For tch-rust I tried inference with both let output = model.forward_ts(&[input]).unwrap().squeeze(); and let output = input.apply(&model).squeeze();, with the same result.
C++
Example: inference relevant C++ lines
at::Tensor x_tensor = torch::from_blob(f32img.data, {1, 1, height, width}, torch::kFloat);
std::vector<torch::jit::IValue> inputs;
inputs.push_back(x_tensor);
at::Tensor outputs = model.forward(inputs).toTensor().squeeze();

In both cases the images are single channel 16 bit images which I convert to f32 and normalize. In both cases I make sure that I can reconstruct the same image if don't pass it to the model, so the issue isn't in the pre or post processing steps. The traced model file I use is the same, as well as the input image of course. I also checked that the input, output, as well as the weights are effectively f32, and they are.
I ran the examples without issues, so the problem must be on the way this architecture is loaded I guess (maybe the issue could be the pixelshuffle layer?).
infos

OS: Ubuntu (WSL)
rustc: 1.66.1
tch: 0.10.1
libtorch: 1.13.0

Thank you 😊

The torchscript bits of tch should actually just be thin wrappers around the C++ version so it's indeed suprising to have such discrepancies. It might be that image loading doesn't do exactly the same thing, e.g. one generates pixel fvalues from 0 to 255 and the other from 0 to 1 or something like this (also not sure how well grayscale works in tch), I guess you'll probably want to print some of the intermediate tensors to check if things line up well.

As I said, I convert the input to f32/float and normalize it (so, interval [0,1]), and I check both the type and the intervals in the input on both C++ and tch-rs. The grayscale is just a one-channel image or a 3 channels image where all channels have the same value. As I said, in my case it's a single channel image. The issue must be how the model is loaded or how it run the forward pass, since the values explode there:
C++ input max value:
std::cout << "min in: " <<  torch::min(input) << "\n" << "max in: " <<  torch::max(input) << std::endl;
at::Tensor output = model.forward(input).toTensor().squeeze();
std::cout << "min out: " <<  torch::min(output) << "\n" << "max out: " << torch::max(output) << std::endl;

output:
min in: 0
max in: 0.929091
min out: -0.0858269
max out: 0.960142

tch-rs input max value:
println!("min in: {:?}\nmax in {:?}", tch::Tensor::min(&input), tch::Tensor::max(&input));
let output = input.apply(&model).squeeze();
println!("min out: {:?}\nmax out: {:?}", tch::Tensor::min(&output), tch::Tensor::max(&output));

output:
min in: 0
max in: 0.92900654296875
min out: -2.4308676719665527
max out: 2.8395004272460938

the only difference is the forward line...


Permutesystems

Allows changing the ordering of the subsystems in composite systems. Implemented for dense, sparse and lazy operators as well as for states and bases.

Coverage remained the same at 0.0% when pulling 1dceb50d21fc781899d4c75677d7dfffb1f39def on permutesystems into a9df93425d259871e5083bae0db9cd807229be59 on master.


⚠ Samsung has degraded performance

In 13fdd30, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2538 ms

Resolved: Samsung performance has improved in f6d101a.


Update 010-performance-tuning-introduction.md

This is my first edit to the documentation

@saurabhmahapatra94 can you address review comments?

Thank you for the pull request.  If you'd like to revisit it, please open a new pull request against the apache/drill-site repo.