Dev bundle unable to deal with uncaught exceptions

With the dev bundle, uncaught exceptions result in a stack trace like this:

Notably, all the information about the exception that caused this is lost -- it dies trying to load java.lang.Exception before it can show anything.
With the non-dev bundle it works as expected and I get
Uncaught Error: Class$obf_1001: rte
    at helloworld.js:2

Ideally the dev bundle would do the same, only preserving type names.
I copied helloworld_dev_js.map into my html directory as well, but it is looking for HelloWorld.js.map instead which is not an artifact present in bazel-bin.
Here is my modification of the hello world example to throw a RuntimeException.  To run it, I copied helloworld_dev.js and helloworld_dev_js.map into the html directory but I did not commit them.  I note that it is looking for HelloWorld.js.map but that is not an artifact present in bazel-bin.

Thanks for the detailed report. It's helpful.
There is something fishy here. I see that it is trying to use debug loader but it shouldn't (which is slow and has bunch of problems).
By any chance you have a custom setup? Your repro also uses custom setup so it is not surprising that one is using the debug loader.

To check this with your repro, could you follow the instructions in https://github.com/google/j2cl/blob/master/docs/getting-started.md instead of custom html page?

with bazel run src/main/java/com/google/j2cl/samples/helloworld:helloworld_dev_server, I get Uncaught Error: java.lang.RuntimeException: rte as desired.
What is the correct way to use j2cl with a custom setup?

Please see j2cl_application.bzl documentation for providing/using custom host page for the dev server.
If you need use your own server, you can try to replicate those instructions (link importing <target>_dev.html) or you can manually load <target>_dev_config.js in addition to <target>_dev.js in your page.

Confirmed that adding helloworld_dev_config.js to my page fixes the problem.  Thank you!
Where would it be appropriate to mention this in the docs?

I think it depends on where you have found out about the <target>_dev.js. I think it is only documented in j2cl_application so we can improve the documentation there.

Ahh! The target in helloworld mentions it in the section starting with "It provides couple of convenient targets"
I think we should remove the mention of dev.js and point the right place (even it is not complete). I will send a patch.
#  :helloworld_dev produces the helloworld_dev.js that could be used for development (see j2cl_application for details).

Thank you!


Detect new JDK vendors

These are more recent JDK vendors that our probe service just detects as "JDK". Given this is now exposed in toolchain reports (and will be used by vendor matching), ensure we support more vendors.

@bot-gradle test QF

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

This is stale and folded into the new probe service


Update the code

There is still a few error i find using some commands

Tell me what is the error.

Tell me what is the error.

I forgot because i fixed it shortly after making this


Add fgalmeida to AWS CodePipeline plugin maintainers

Add fgalmeida, remove biagic from AWS CodePipeline plugin mauntainers
list
Description
Add fgalmeida (galmeida on github) to list of AWS CodePipeline plugin maintainers, Remove biagic from the list

https://github.com/awslabs/aws-codepipeline-plugin-for-jenkins
https://github.com/jenkinsci/aws-codepipeline-plugin

@belltimo can you please confirm my permission request?
Permissions pull request checklist
Always

[X] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

[ ] Make sure the file is created in permissions/ directory
[ ] artifactId (pom.xml) is used for name (permissions YAML file).
[ ] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[ ] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[X] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[X] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[X] All newly added users have logged in to Artifactory at least once

I confirm fgalmeida should be added and biagic removed.

Hi @daniel-beck,  I still cannot access https://github.com/orgs/jenkinsci/teams/aws-codepipeline-plugin-developers/repositories. Please let me know when can I get the permission? Thank you.

@galmeida This repo gives permission to release the plugin to the Jenkins infrastructure; it is separate from the GitHub repo permissions.
I've added you as a committer as the plugin; you should have gotten an invite from GitHub, or see a notice when you visit https://github.com/jenkinsci.

Received, tks

@galmeida https://github.com/jenkins-infra/repository-permissions-updater#about
If you have specific suggestions how to make this clearer, please let me know.

maybe you could call out in Managing Permissions > Example File that username is Jenkins LDAP username (as opposed to github username), I know you call it out at the begining of the README, but I missed that before, I just realized it when check the PR template checklist. Other than that I think the README is pretty good.
thank you.


Mutation of static backend prop on Model

I found that if we set backend on a Model and then start a session with schema.withMutations(...) (for bootstrap for instance) this will change the static backend prop setting withMutations to true. From this point on every time we make a change we are literally mutating the store.
The bug is in Model.js file
// Model.js
static getBackend() {
    if (!this._sessionData.backend) {
        const BackendClass = this.getBackendClass();
        const opts = this._getBackendOpts();

        if (this.session && this.session.withMutations) {
            // HERE! This will mutate the static prop `backend` on the Model
            opts.withMutations = true;
        }

        // ...
    }
    return this._sessionData.backend;
}

Fixed in release 0.8.3


iFrame Widget Request

Description
Embedding other websites in dash v1 is possible but very messy and hit and miss functionality.
I'd like to see a more robust dedicated iFrame widget for dash V2.
A lot of industrial applications use weather data, being able to embed a lightning / wind / storm radar weather map is a VERY frequent request we hear.
Properties
No response
Events
No response
Controls
No response
Existing Examples
No response
Have you provided an initial effort estimate for this issue?
I am no FlowFuse team member

Is there a difficulty in using ui-template for this?

Hi,
here is an example how I use iFrames with ui-emplate
Michel
<template>

        <iframe
            id="production"
            src="http://<IP_ADDRESS>/smartvisu/index.php"
            class="responsive-iframe"
            frameborder="0"
            style="border:0"
            body-fill
        >

</template>

I've just published https://flows.nodered.org/node/@flowfuse/node-red-dashboard-2-ui-iframe which covers this as a third-party widget. Closing the issue

Testing this new node and am finding that nothing shows up at all.
Nothing in the logs, no error in debug tab, nothing in the iFrame.
I have an inject at once a minute and the the full URL. Testing the URL in my browser brings up the website as expected.
Just nothing on the dash2.0 group. Not even a place holder.
Tested with both my URL of choice and https://google.com and neither show up.

Google will not work as its built with iframe blockers, and forbids use in an iframe.
Are you able to share the other URL?
I can try and do some better error catching, but I'm not sure what the browser will give me to jump onto.
The way to sanity check this is using the ui-template method I'd shared previously, and using  to be sure its the widget that's broken?

Did not know about google.com iFrame blocker, thanks for the tip.
Using https://opto22.com or https://nodered.org both show the same - nothing at all.

Opto22 site also has the iframe blocker, Node-RED does not though, so should be working:
This flow will give you a quick tester.
[
    {
        "id": "307c609f43d2b68f",
        "type": "ui-iframe",
        "z": "5141797ff72d0139",
        "name": "",
        "group": "bb21a845cf454195",
        "order": 0,
        "src": "/",
        "width": "10",
        "height": 8,
        "x": 290,
        "y": 220,
        "wires": []
    },
    {
        "id": "7ce392a0c84c4b39",
        "type": "inject",
        "z": "5141797ff72d0139",
        "name": "",
        "props": [
            {
                "p": "src",
                "v": "https://nodered.org/",
                "vt": "str"
            }
        ],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "x": 130,
        "y": 220,
        "wires": [
            [
                "307c609f43d2b68f"
            ]
        ]
    },
    {
        "id": "bb21a845cf454195",
        "type": "ui-group",
        "name": "iframe",
        "page": "85043ba28e0273fe",
        "width": "10",
        "height": "8",
        "order": -1,
        "showTitle": true,
        "className": "",
        "visible": "true",
        "disabled": "false"
    },
    {
        "id": "85043ba28e0273fe",
        "type": "ui-page",
        "name": "Third Party Widgets",
        "ui": "c2e1aa56f50f03bd",
        "path": "/third-party",
        "icon": "account-group",
        "layout": "grid",
        "theme": "129e99574def90a3",
        "order": 1,
        "className": "",
        "visible": "true",
        "disabled": "false"
    },
    {
        "id": "c2e1aa56f50f03bd",
        "type": "ui-base",
        "name": "Dashboard",
        "path": "/dashboard",
        "showPathInSidebar": true,
        "navigationStyle": "default"
    },
    {
        "id": "129e99574def90a3",
        "type": "ui-theme",
        "name": "Another Theme",
        "colors": {
            "surface": "#000000",
            "primary": "#ff4000",
            "bgPage": "#f0f0f0",
            "groupBg": "#ffffff",
            "groupOutline": "#d9d9d9"
        },
        "sizes": {
            "pagePadding": "9px",
            "groupGap": "12px",
            "groupBorderRadius": "9px",
            "widgetGap": "6px"
        }
    }
]

Thinking also, it may need a Node-RED restart after installing the third-party widget so that Dashboard can be made aware of the package.json changes and the inclusion of the third-party library

Imported, deployed, clicked inject, refreshed browser.
Blank group.

Restarted Node-RED and iframe is working as expected.
Perhaps this requirement for a restart be added to flows.nodered for this node.

@Steve-Mcl  is there a way in my package.json (or somewhere else) I can tell Node-RED to notify a user a restart may be required? I know I've seen that popup, but not sure how to configure it?


Feature Request: Scan time to be included in logs

Is this a request for help?:
NO
Is this a BUG REPORT or a FEATURE REQUEST? (choose one): FEATURE REQUEST
If this is a FEATURE REQUEST, please:

Describe the feature in detail as much as possible including possible cli and api behavior and how to test the feature.

Feature to include information in logging output for time taken for a scan.
This will help us fine tune our workflows to make sure scans complete (ex: jenkins plugin max-retries)
Also, if you are planning to add a basic metrics endpoint to the API , then the average time for scans per account would be a good metric to have

We have a bug to fix to get prometheus metrics working properly, if that were enabled and had a histogram view for the analysis time for each analyzer node, would that be sufficient, or is a log-based approach strongly preferred?

@zhill : logs would be preferred but not strongly
Any way we can get that information would work

@zhill : is the plan to add them in prometheus ?
"histogram view for the analysis time for each analyzer node, would that be sufficient" -> Yes that would work for my usecase


Hide 3.X features from 3.0 docs

IMU
Consider excluding geometry module + corresponding features in isignal types
Hide Prime Hub and Inventor Hub
Remote class

Let's keep this simple and only do it for the IDE build.

These items have been removed on the v3 branch.


When using Die as a skilling animation, the animation cannot be cancelled

The animation stops the player from visually moving, and no other animation seems to cancel the player being on the floor. It also doesn't cancel the animation when turning off the plugin.
I'm not sure if this also happens for other replacement options (combat, teleport, movement)

That is very interesting, I didn't test that exact config:animation combo. I wonder if it's because the "die" animation is traditionally used with removing or transporting the player back to spawn. The animation may not have a set "end frame", or at least that's my speculation.
I could possible end the animation manually after the "dying" motion finishes.
Thanks for the input, I'll take a look and hopefully have a fix for it soon.

I can confirm, this bug seems to happen only with the Die animation, and only when you try to cancel the action playing the animation. Maybe I can just make it so that if you attempt to walk (aka cancel the action and animation) it manually sets the animation to -1?

I may actually just remove the Die animation from everything except the teleport config, as I don't want to possibly cause any weird behavior from trying to manually cancel the Die animation.


Cannot install :  No module named 'setuptools_rust

How to reproduce :
docker run -it --rm python pip install snips-nlu

Hi @yellowiscool ,
We have pre-built wheels for various architectures and python versions, but for the rest the pip install snips-nlu command will install the package from source distribution. In this case, rust and the setuptools_rust python package must be installed beforehand.
Note that this can happen if, for instance, you are running Python 3.7, as it is not officially supported yet and therefore we haven't published wheels for this version yet.

Thanks for your answer. I tried the following command with success :
docker run -it --rm python:3.4 pip install snips-nlu

Maybe it could be put somewhere in the README that Python 3.7 is not officially supported yet and that prebuilt packages are not available for all python versions on linux x86_64.

Closing this issue, as it is now specified in the README that Python3.7 is not supported yet #665 .

@adrienball Sorry to bother, but is there tracking issue or what sort of issues prevent 3.7 from support
/me doesn't want to have multiple copies of python on machine


Installation with go get is deprecated

Hi! Just letting you know that the instruction for the installation is outdated. How do I intall it now? go install gives me package github.com/fufuok/balancer is not a main package.
$ go get -u github.com/fufuok/balancer
go: go.mod file not found in current directory or any parent directory.
	'go get' is no longer supported outside a module.
	To build and install a command, use 'go install' with a version,
	like 'go install example.com/cmd@latest'
	For more information, see https://golang.org/doc/go-get-install-deprecation
	or run 'go help get' or 'go help install'.

$ go install github.com/fufuok/balancer@latest
go: downloading github.com/fufuok/balancer v1.0.0
package github.com/fufuok/balancer is not a main package

Hi! It's my fault, this is the class library, not the main package, you can start like this:
demo.2211012149.zip
# go run main.go
🍒 🍒 🍒 🍋 🍒 🍋 🍒 🍋 🍉

more...


active's translated position doesn't match the drag overlay's position

I am implementing tree sorting with a few differences from the official example.
In onDragMove I use event.active.rect.current.translated and event.over.rect to decide whether an item should be moved before, inside or after another item.
I use a modifier similar to snapCenterToCursor that centers the overlay based on the pointer's position.
The problem is that event.active.rect.current.translated doesn't match the overlay's actual position. In other words the drag overlay modifiers are not applied to the translated position.
Here's a recording demonstrating that:
https://github.com/clauderic/dnd-kit/assets/2291025/e8fb2b9d-36b6-41bf-961a-08feb0fbebdd
In this example the red square matches event.active.rect.current.translated and we can see that it has a different position than the actual drag overlay which uses a snapCenterToCursor modifier.

Here's a simplified workaround I am using for now:
const translated = event.active.rect.current.translated;

const withModifier = dragOverlayModifier({
  active: event.active,
  activatorEvent: event.activatorEvent,
  draggingNodeRect: event.active.rect.current.initial,
  overlayNodeRect: translated,
  transform: { x: translated.left, y: translated.top, scaleX: 1, scaleY: 1 },
});

translated.left = withModifier.x;
translated.top = withModifier.y;


Fan entity not found

Hi
Sorry i'm really new to Home Assistant, i installed it this evening on my QNAP NAS.
I have a Comfee MDDF-20DEN7-WF dehumidifier, i have installed your integration but i can't see the fan entity

What should i do ?
Thanks for help !

Hello @Xxbz , there is a regression bug in v0.6.0-beta which fails creating fan in HA 2021.12. I've updated version to fix it. Just go to HACS and redownload beta version.

Problem solved, thanks you !
Is it possible to send request to Home Assistant with Amazon Alexa ?

Hi @Xxbz xxbz, I'd suggest for Alexa to look either https://www.home-assistant.io/integrations/alexa/ and linked pages https://www.home-assistant.io/integrations/alexa.smart_home/ - it is fairly complex though.


improve handling of HTML entities

Dear Grobid team,
I had some trouble with Grobid not properly escaping XML special characters in the xml:id attribute when generating biblStructs.
Also I noticed a typo in the part of the TextUtilities.HTMLEncode method that tries to prevent double encoding of HTML entities (it was checking for &quote; instead of ".
Let me know what you think!
All the best,
Fabian

Hi Fabian,
Many thanks for your fixes! This is all very absolutely correct and correct my errors.
All the best!
Patrice


After update to 2.10, now plaintext!!

PHP Version: 5.5.9-1ubuntu4.14
Server Software: Linux
Enlighter Plugin Version: 2.10
EnlighterJS Version: 2.10.0
Cache writeable: true
JSON Extension: installed
Wordpress 4.3.1 Diarjo Lite theme
I tried to uninstall and reinstall plugin, nothing change, all my text are in plaintext.
I enabled debug, but there aren't any relevant issue in log.
Help

Dear Federico,
do you have tried to click "save changes" on the plugin settings page ?
can you provide a link to your website - i think the initialization script or maybe some other javascript files are missing.

maybe, on the enlighters settings Page Options >	Initialization> "Enlighter Config" is deselected. in this case just select "inline" and click on save changes.
two options of these dropdown menu have been removed in v2.10.

Dear Federico,
thank's for you report. i've identified a bug which affects users when upgrading to 2.10:
the dropdown menu Options > Initialization> "Enlighter Config" is initialized with a wrong default value (none) which will not initialize the highlighting.
please just select "inline" and click save - this will fix the issue!
i will release a fixed version asap!
best regards, Andi

bug is fixed in v2.11! the update is released on GitHub and WordPress.org

Hi Andi,
thank's a lot for your fast fast fix.
Now works!

Federico Fiordoliva
Roma - Italia
Gtalk<EMAIL_ADDRESS>Skype: federico.fiordoliva
2015-11-19 22:45 GMT+01:00 Andi Dittrich<EMAIL_ADDRESS>
Closed #21 https://github.com/AndiDittrich/WordPress.Enlighter/issues/21
.
—
Reply to this email directly or view it on GitHub
https://github.com/AndiDittrich/WordPress.Enlighter/issues/21#event-469720153
.


Azure Sql db

the example does not work on Azure SQL DB

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

ID: 3b79d736-c8b0-a460-501a-71c590092bc9
Version Independent ID: f5c34ba9-0a5d-0af5-c4e5-c99d5572e6d5
Content: CREATE EVENT SESSION (Transact-SQL) - SQL Server
Content Source: docs/t-sql/statements/create-event-session-transact-sql.md
Product: sql
Technology: t-sql
GitHub Login: @CarlRabeler
Microsoft Alias: carlrab

@HenrikStaunPoulsen The article has been changed to add relevant information that address the concern described here in Issue 2211 (PR 10427).  The change should be visible on live Docs by Thursday May/30.
Thank you.
I am now closing this Issue as fixed.


758 resource identifier

https://github.com/uwlib-cams/MARC2RDA/blob/main/Working Documents/7XX.csv

https://docs.google.com/spreadsheets/d/1_E3wrUKGZaNpkPkPyylp2JFLnq8hNjzwunpGHFb2GL0/edit#gid=523701703
Hello Everyone,
Please see the first pass for field code 758  Resource Identifier (R). Could anyone take a look?
Thanks.
Best,
Alice

Mapping $4 and $1 seems pretty straightforward: if $4 is an RDA WEMI property, map it as such with the $1 URI as the object.
$a and $0 seem trickier, because they are nomens associated with the object identified in $1. I don't see a way of determining what type of RDA entity that object is, which is how we would determine what property to use when mapping $a and $0.

@cspayne and colleagues: I agree that there is a straightforward transform for some of the instance data, based on the use of an RDA property.
If we assume that the property value is correct and valid, then the condition for an RDA property can be simplified to a generic function: position(subfield, 'rdaregistry.info') > 0. This tests if the IRI contains 'rdaregistry.info'. Anything more elaborate is a form of validation.
Complications :-(

758 subfield $4 says: 'Code or URI that specifies the relationship from the entity described in the record to the entity referenced in the field.'

This implies that only one entity is described in 'the record'. (Unless I am misinterpreting US English :-)
Subfield $i says '... the resource described in field 758 and the resource described in the 1XX/245 of the record'.
This indicates that the 'resource' or entity is determined by 1XX/245.
In the example for subfield $a, there are two occurrences of the field, one for a manifestation and one for a work. This appears to contradict the implication that only one entity is being described.
The complication for the transform is:
Which entity is the subject of the 'record'/field 758/transformed statement:
   .
Is  'the' instance of manifestation being described, or 'the' instance of work that is embodied by the manifestation? This is further complicated when whole-part manifestations and aggregates (multiple embodied works) are being described.

The domain of the RDA property recorded in subfield 4 is the class of entity that is the subject of the statement. The range of the property is the class of the related entity.

This is a strong declaration. If we assume that the data is valid, I think that this should have a high priority if there is a collision with the transform of other fields. That is, if there is doubt about the classes of instances that are generated by the transform overall, field 758 should be a deciding factor. I am thinking particularly of expressions rather the the work/manifestation associations implied by the manual.

Subfield $0 can be mapped to an RDA identifier recording method for the property that is used. So the same straightforward transform can include either or both of subfields $0 and $1.

If the RDA property is a canonical property, it can be transformed to a datatype property (for subfield $0) or an object property (for subfield $1) using a simple process:
If exists($0) replace($4, '/P', '/datatype/P')
If exists($1) replace($4, '/P', '/object/P')
[The Registry and namespaces were designed for this purpose.]

If an RDA property is not used, then we may be able to develop an approach based on the work with relationship properties in other 7XX fields. That is, use a mapping from the other property to an RDA property.

Uncomplications :-)
Subfield $a seems straightforward. We know that it is a label for the related entity, but we don't know what kind and there is no way of automatically determining if a string is an authorized access point or title, etc. So the transform should use a general RDA appellation property for the entity of subfield $1:
<$1>  "$a" .
In the MARC manual example:
http://www.wikidata.org/entity/Q1613936 rdamd:P30277 "Bored of the Rings" . // property determined by the range of $4
http://id.loc.gov/authorities/names/no97079452 rdawd:P10329 "Tolkien, J. R. R. (John Ronald Reuel), 1892-1973. Lord of the rings" . // property determined by the range of $4
Is this in scope? Should we add RDA properties to existing instances, or leave them encapsulated for de-referencing? Similar (non-RDA) properties are attached to the existing instances ("label" in wikidata, the aap in LC authorities).
It is clearly in scope for instances that are minted in the transform, but such minting is triggered by other fields so is not directly relevant to this field.

At the BIBFRAME Update Forum Jan. 22, Jeff Mixter of OCLC said they would start adding WorldCat Entity URIs to Worldcat records at the end of January (so presumably they are going in now) for Works.  I asked in the Q/A what the WorldCat definition for "Work" was, and was told it aligned with BIBFRAME Work.
Since various people at LC have stated that a BIBFRAME Work is equivalent to RDA Expression with some RDA Work characteristics included (I'd have to hunt down references to this in print...), would this support taking the position that the entity being related most closely corresponds to an RDA Expression, and that what it is related to is the RDA Manifestation whose description is the focus of the record?
Jeff said they would use a 758 field but didn't show an example.  While we can't assume everyone using 758 will follow OCLC's pattern in that use, as soon as this is documented, we should analyze it and the property asserted.
@GordonDunsire hate to say it but your use of the word instance befuddles me because I'm entangled with BIBFRAME now for another project and bf:instance is a thing.  Hard to find words that haven't been used elsewhere with a different meaning these days!

@lake44me: I use the word 'instance' in its RDF sense, which is based on the vernacular use as 'an example or single occurrence of something': a single occurrence of a thing (i.e. of a class). RDF Schema (RDFS), since 2004, uses the term frequently and consistently: 'The members of a class are known as instances of the class'. I think this usage predates that of BIBFRAME. BF could easily have used the term "manifestation", which is used elsewhere with the same meaning, but chose to use a befuddling term instead. I don't speak BF at all, but I know a little RDF/LRM and I think that's more appropriate for an RDA project :-)

@CECSpecialistI Could we see if someone is willing to take this mapping from me and complete it? I'm afraid I won't have time to.

@cspayne: What needs to be done? I can analyze further the field from an RDA pov, in light of discussions on headings, etc. since February. Does this Issue thread constitute the documentation on what has already been done (that needs to be completed) or is there relevant information elsewhere?

@GordonDunsire
Yes, all discussion that was done is in this issue. We need to decide how we want to map each of these subfields and fill out the Google Sheet so that it can be moved to ready for review.

@cspayne and others: I don't want to get entangled in the Google Sheet, but here's my further analysis:
$a is a nomen [string] for a resource entity (WEMI).
$0 is an identifier for the same resource entity.
$1 is the same resource entity.
$2 is controlled and indicates the authority of the nomen for the resource entity.
$i is uncontrolled.
$4 is controlled. RDA properties are easily identifiable.
$3 and $5 are difficult to map to RDA.
Further discussion:
Mapping of 1xx/245 to RDA WEM entities has been resolved in the context of phase 1. A work and a manifestation will always be minted, so there is always more than one entity identified by the 1xx/245 values. The complications of aggregates and diachronc resources are only relevant as context and future development.
The RDA entity that is the domain of the RDA entity in $4 is a priority in determining the entities transformed from 1xx/245.
Mapping of $a, $0, $1, $2 has been resolved. This includes approval of $1 sources to avoid range entity-collision with $4. (This also supersedes my note 3 above.)
Therefore the transform is primarily dependent on whether $4 is an RDA property. If it is not, then we need to determine a default.
The cases of an unconstrained RDA property, and an original and official RDA label in $i, are dealt with elsewhere (I'm not sure of the current status of the relationship labels work).
Transform:
If either of $3, $5 are present, drop the field.
If $4 (string) contains 'rdaregistry.info' and does not contain 'rdaregistry.info/Elements/u' then:

mint an entity for the domain of the property or re-use *** the appropriate work or expression minted by 1xx/245
select the entity or value for the range of the property. Process $a, $0, $1, and $3 the same as for heading fields.
output the statement (domain entity) objectified($4) (minted range entity) or (domain entity) datatyped($4) 'range string' as appropriate. (The datatyped and objectified functions generate the datatype and object versions of the RDA elements.)
Ignore $i.

If $4 (string) does not contain 'rdaregistry.info' or contains 'rdaregistry.info/Elements/u' then output a note on manifestation with the contents of the field as a structured string. There is no easy way of determining the domain or range in phase 1.
If $4 is missing, transform $i as for other 7xx fields.
*** I'm sill wondering if we can de-duplicate the primary WE that are minted for each resource. The big problems are augmentation aggregates, which are likely to have the same 1xx/245 values as a non-aggregate, and the lack of an authority source. In this case, however, we could make the assumption that the WE referenced in field 758 are the same as the WE minted from 1xx/245, if aggregates are excluded. That is, if an RDA Work or Expression element is used in $4, then use the instance of W or E that is minted from 1xx/245.


Syntax Error: Expected end of line, etc. but found identifier

Thank you, this is just what I was looking for.  👍
However, I cannot start it, I get the following error, once I run the script:

Syntax Error: Expected end of line, etc. but found identifier

The offending line seems to be
tell application "Evernote" to set f to exists notebook bName -- does notebook exist?

where bName is highlighted.
I don't know AppleScript at all, so I have no clue where to start here...
macOS: 11.2
Evernote: Version 7.14.1

Hello ping13
Thanks for opening this issue. I just tried to re-create it. But the script ran without problems. I re-downloaded the source from GitHub, as you did no doubt. Then I opened it in macOS Script Editor and ran it without problems.  I'm on macOS 11.2.2 and Evernote 7.14.
I've had the problem you describe with several scripts over the past year. I found that it was some sort of random parsing bug in Script Editor that surfaces during a compile. I was able to work around it by making a trivial change to the source code (or sometimes more than one change).
The source code line you cited in your post is valid as written. I think it's this random bug in Script Editor's compile.
When you first open the downloaded file Notebook Export Manager.applescript, you've opened the source code.  When you run it, Script Editor forces a compile.  Or you can compile manually (without running it) by clicking Script > Compile or ⌘-k or clicking on the hammer icon in the tool bar.
So, I suggest you make one or two trivial changes to the source code and try to compile it. In AppleScript, the double dash (--) marks the start of an inline comment.  So, throughout the source file, any text to the right of a double dash is a comment.  You can change them at will.  For example, about 20 lines into the source code, you'll see these lines:
global logProgress -- switch to control Log statements for debugging
set logProgress to false -- run Log commands for debugging USER SETTING

The Script Editor will show the comments in light gray text.  Just delete some of the words in the comments or make some other minor change:
global logProgress -- switch to control Log
set logProgress to false -- run Log commands (for debugging) USER SETTING

Then, try to compile it (see above) or simply run it.  If this works, then you too have hit this random compile bug (and worked past it).  If not, please let me know.

Thanks so much for the explanation and your time devoted to this issue!
What a nightmare this editor is! It really seems like a non-deterministric error. Your suggesstion didn't work. But I copied and pasted portions of the code and I got it to compile, at least with some other errors (see below). However, on various attempts, I was never able to fully get a correct compilation.
This is frustrating, not because of you, but because of this Script Editor. Is there a way to distribute a compiled version?
Error: date parsing problems

offendling line:
set ExportDate to date "Saturday, January 1, 2000 at 12:00:00 AM" -- No exports have been done yet

I can fix this one by using "2020-01-01" as a date (I'm on a non-US language setting here, but this should work universally).
Error: ambiguous path

offending line:
set myPListFullPath to POSIX path of ((path to preferences as text) & "com.lake91.nem.plist")

Thanks for this additional information.
Yes, the Script Editor is really disappointing. Conceptually, it's a great idea. But Apple has really neglected it.  My next (hobby) project is going to be in Swift.
Yes, this compile bug in Script Editor does seem to be non-deterministic.
Regarding the date syntax errors, I have about 6 statements like this in the script. In every case, I'm just trying to initialize a date value in either the distant past or future. I guess I shouldn't be shocked that the Script Editor source code is dependent on locale. I can create a fix for these issues, however.  It will take me a few hours to implement, test and upload a new version.
I was able to recreate the second syntax error ("path to" is ambiguous because it is imported from...). At the very start of the script, there's a statement that says:
use scripting additions
This is a compiler directive that tells AppleScript where to find additional commands. This statement can appear only once.  Perhaps, in trying to cut & paste, did your script end up with two of these?  If so, delete one of them.  In my script, there's one on Line 13 and an irrelevant comment:
-- tell application "Finder"  (adding class furl below fixed this)
near the start of the writeIndex routine.  That comment doesn't matter.  Please let me know if my guess is correct about the second "use scripting additions" statement.
I will post an updated version of the script, later today (I hope) to fix the date problems.
Yes, there is a way to distribute a compiled version. The Script Editor can save scripts in a compiled version as an .app bundle (ie, macOS executable app).  However, in Catalina and Big Sur (and perhaps earlier), these files need to be signed with an Apple Developer ID.  I can investigate how to do that. it would certainly simplify distribution.  I also need to figure out if/how Github can distribute executables. This is my first posted open source project, so I'm learning as I go with Github.

Thanks so much for your time. Please don't stress yourself, there is more in life than an AppleScript for a niche use case.
But I still appreciate your effort very much! Keep up the good work.

I've updated the source file for the script to use a different method of initializing date constants. This new source file may also (accidentally) fix the Issue originally posted here.  But it should almost certainly fix the date issue.  I created a new GitHub Issue to track the date problem separately.

Just found this script, and tried to compile, but faced the same issues as reported in this issue. :( Did you ever establish a way to distribute a compiled version? Seems such a shame for this utility to be compromised by a Script Editor issue...

I did not yet create an executable, but I will take a look at it this weekend.  I’m away from home (and from my Mac) for a few days.

The only Mac I have now is a new M1 MacBook Pro running macOS Monterey (12.0.1). So, I can't test with prior versions. I set up a test environment on my new machine and the script did not get the error cited in this issue.
However, I do get that error in one particular circumstance:  when the script attempts to compile (just prior to running) and the installed "Evernote" application is not version 7.14.  For example, if you have installed the 7.14 version in Applications and it's called something like Evernote Old (ie, anything other than Evernote), then you can get this spurious syntax error. This could happen if you have the legacy app (7.14) and the new app (10.x) is the one called Evernote.  If this situation occurs, just stop all running copies of Evernote.  Rename the Evernote applications as needed so that the 7.14 version is called Evernote (actually Evernote.app, but many people don't choose for macOS to display all file type qualifiers).  Then try to run the script again.
BTW, I fixed a problem (Issue 3) that came up in macOS Monterey (12.0.1).
Please let me know if this application name change resolves the syntax error.

Hello
I’m new to GitHub and I wasn’t sure whether you’d see my update to the Issue.
I was able to set up a test environment on my new M1 Mac running Monterey and legacy Evernote 7.14.  I updated the GitHub Issue with my findings:  It’s critical that the legacy Evernote version 7.14 be in place in the ~/Applications folder, with the name “Evernote” (actually it would show as Evernote.app, if you’ve told macOS to always display file extensions in Finder).
If the Script Editor goes to compile the script and doesn’t find the expected SDEF file (scripting definition), then the compile fails with the (misleading) error message that you got (see attached screen caps).  (Maybe you know this, but the SDEF is inside the app package, in the <app_name>/Contents/Resources/ folder and is typically named <app_name>.sdef)
So, if you’re running both the legacy 7.14 version and the newer 10.x versions of Evernote, then be sure to get the legacy one in place as ~/Applications/Evernote.app before you attempt to run the script.
If this doesn’t resolve your issue, please let me know and I’ll look into creating an executable. As you may know, that entails getting an Apple developer account and submitting the app to them for review and signing.
Bill

On Nov 25, 2021, at 4:54 AM, Jacob Sam-La Rose @.***> wrote:
Just found this script, and tried to compile, but faced the same issues as reported in this issue. :( Did you ever establish a way to distribute a compiled version? Seems such a shame for this utility to be compromised by a Script Editor issue...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/BitRancher/notebook-export-manager/issues/2#issuecomment-979044921, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHRCDB2WP2Y7RJYT7WQJHP3UNYBVPANCNFSM4YJ7QCFQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

In my email below, I indicated that Evernote should be in ~/Applications. That’s wrong. It should be in the main system Applications folder (along with all the usual apps).

On Nov 30, 2021, at 9:28 AM, Bill Jacob @.***> wrote:
Hello
I’m new to GitHub and I wasn’t sure whether you’d see my update to the Issue.
I was able to set up a test environment on my new M1 Mac running Monterey and legacy Evernote 7.14.  I updated the GitHub Issue with my findings:  It’s critical that the legacy Evernote version 7.14 be in place in the ~/Applications folder, with the name “Evernote” (actually it would show as Evernote.app, if you’ve told macOS to always display file extensions in Finder).
If the Script Editor goes to compile the script and doesn’t find the expected SDEF file (scripting definition), then the compile fails with the (misleading) error message that you got (see attached screen caps).  (Maybe you know this, but the SDEF is inside the app package, in the <app_name>/Contents/Resources/ folder and is typically named <app_name>.sdef)
So, if you’re running both the legacy 7.14 version and the newer 10.x versions of Evernote, then be sure to get the legacy one in place as ~/Applications/Evernote.app before you attempt to run the script.
If this doesn’t resolve your issue, please let me know and I’ll look into creating an executable. As you may know, that entails getting an Apple developer account and submitting the app to them for review and signing.
Bill

On Nov 25, 2021, at 4:54 AM, Jacob Sam-La Rose @.*** @.***>> wrote:
Just found this script, and tried to compile, but faced the same issues as reported in this issue. :( Did you ever establish a way to distribute a compiled version? Seems such a shame for this utility to be compromised by a Script Editor issue...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/BitRancher/notebook-export-manager/issues/2#issuecomment-979044921, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHRCDB2WP2Y7RJYT7WQJHP3UNYBVPANCNFSM4YJ7QCFQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thanks for the updates! I've got two versions of Evernote installed— the most recent release, and Evernote Legacy 7.14.1. From the sounds of what you've suggested, that might be the issue. I'll test these suggestions out and let you know...


SIFT Install - Ubuntu 14.04

So I have created a snapshot prior to installing SIFT on my VM, however I keep running into an issue. After installing SIFT and rebooting, I login and get an empty Desktop. I have tried several times, but am not getting anywhere. I installed it from a terminal in the GUI.
I've tried sudo -su and sudo -s and sudo wget ...... without any luck. Has anyone seen this before or have any idea what the fix is for this?

Please provide the following information:

Exact steps you are taking
The sift-install.log file in your home directory
Any additional information you might feel is relevant.

@blackice7 if you are still having issues please feel free to re-open.


Incompatible libraries

When I finetune GPT-2 with DP using fine-tune-dp.py in dp-transformers/research/synthetic-text-generation-with-DP. An error occurred: TypeError: read_csv() got an unexpected keyword argument 'mangle_dupe_cols'
Seems like the error is caused by the versioning of datasets, if I upgrade datasets to the latest version (2.14.6), the error disappeared, but another error occurred: ValueError: math domain error
I checked the source code and believe that this error should come from math.log(1 / q - 1) in the prv_accountant package, which is a part of dp_transformers. I was trying to upgrade df_transformers, but df_transformers requires datasets<=2.6.1,>=2.0.0, which will cause the TypeError mentioned before.
Any suggestion to avoid the incompatible libraries problem will be appreciated.
Thank you!

Hi @fangyiyu, very recently we updated our repo, which now uses probably latest version of everything but indeed the research project synthetic-text-generation-with-DP is still based on the previous version. Though I don't think datasets package version is very critical for us in fine-tune-dp.py so it's okay to upgrade it.
In my opinion, the error you are getting from the prv_accountant package is totally independent of the datasets and most likely it has to do with your privacy parameters. If you could please let us know what you set as the target_epsilon (or noise multiplier) and your dataset size along with the effective batch size you'd like to use and the number of epochs, then we can see why we are getting a problem with prv_accountant package.

Hi @huseyinatahaninan, thank you for the reply. I'm following the script for finetuning with DP on this page, though I only have one GPU instead of 8. Below is my script for finetuning, where you can see the target_epsilon is set to 4, training batch size is 32, validation batch size is 64. I'm using a very small dataset for preliminary experiment, the training dataset contains 100 instances with an average of 47 tokens in each instance, and the validation set contains 10 instances with the an average of 114 tokens in each instance.
python3 fine-tune-dp.py \
    --data_dir data \
    --output_dir output \
    --model_name gpt2 \
    --per_device_train_batch_size 32 \
    --gradient_accumulation_steps 16 \
    --evaluation_strategy epoch \
    --save_strategy epoch \
    --log_level info \
    --per_device_eval_batch_size 64 \
    --eval_accumulation_steps 1 \
    --seed 42 \
    --target_epsilon 4.0 \
    --per_sample_max_grad_norm 1.0 \
    --weight_decay 0.01 \
    --remove_unused_columns False \
    --num_train_epochs 50 \
    --logging_steps 10 \
    --max_grad_norm 0 \
    --sequence_len 128 \
    --learning_rate 0.0001 \
    --lr_scheduler_type constant \
    --dataloader_num_workers 2 \
    --disable_tqdm True \
    --load_best_model_at_end True \

Thank you for your time and hope to hear from you soon.

Hi @fangyiyu, please note that the effective batch size is (number of GPUs x per_device_train_batch_size x gradient_accumulation_steps) and since you set --per_device_train_batch_size 32 and --gradient_accumulation_steps 16 your effective batch size is 32*64, which is more than the training dataset that contains 100 instances. I'd suggest you pick the effective batch size at most 10% of the training data so perhaps you can set something like --per_device_train_batch_size 8 and --gradient_accumulation_steps 1 and let me know if you are still getting an error.
If your training dataset that contains 100 instances is only for preliminary experiment that's okay but note that for better privacy-utility trade-off, you'd rather use much larger training datasets.

Thank you for the reply. I can successfully fine-tune GPT-2 using the latest dp-transformer library that implements PEFT now.


⚠ Spryr has degraded performance

In 3784fda, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3115 ms

Resolved: Spryr performance has improved in 05462ad after 7 minutes.


Add support for basic blockHandlers and transactionHandlers in manifests

This adds blockHandlers and transactionHandlers the subgraph manifest schema and includes them in the subgraph validation.
Open question: Should we introduce a new mapping kind alias called ethereum/contract for ethereum/event, since we're now supporting more than events?
Resolves #229.

Tests are only failing because of Node 11 in Travis acting up. The Node 10 tests pass fine.

@olibearo This is ready. Do you want to take another look?


Verify contributing guide mentions the DCO requirement

And if it doesn't, please add it. Don't surprise people with it after they've already committed and sent over a PR.

l3afd contributing guide mentions DCO and we will use that as template for the other repos.


Fixed cards image hover

When hovering over a card, image will lower its transparency and the background will start to show. This will create a nice color over effect. Hover effect color is easily changeable. Also, added a cursor pointer for hovering over the card.

@Doppelganger113 I like this. Merging it now.


Functions using kustomize library should not drop resource with local-config annotation

For example, https://github.com/GoogleContainerTools/kpt/tree/87191859fdef443395741d85e134e5aa1cd0f877/package-examples/pipeline-validate this package has 4 input resources (2 normal resources + 2 local-config resources for gatekeeper)
After running fn set-labels, it drops the 2 local-config resources that are for gatekeeper.
Fn gatekeeper doesn't find any constraints specified, and always return success.
The functions that use NewResMapFromRNodeSlice from kustomize repo to convert []*yaml.RNode to ResMap, will drop resources with local-config annotation and there is no way to control this behavior currently: https://github.com/kubernetes-sigs/kustomize/blob/api/v0.8.9/api/resource/factory.go#L205-L236
One potential downstream fix is https://github.com/GoogleContainerTools/kpt-functions-catalog/pull/285.
We can also try to change the behavior in upstream kustmoze repo by allowing an option to control this behavior. @Shell32-Natsu said he will take a look at this upstream.

@mengqiy https://github.com/kubernetes-sigs/kustomize/pull/3940 has updated the kustomize resource factory to have an option to include local-config file. You can update the functions.

fixed in https://github.com/GoogleContainerTools/kpt-functions-catalog/pull/382


Clean up RNN tests

This PR cleans up hard-coded tests of six different cases in RNN backend calls.


Can't center align Social Embeds

I already submitted a ticket saying I can't change the width of the Social Embeds, hence I can't make it fill a Div to '100%'.
When I wrap the Social Embed into a <div>, I can't get it to align in the center.
Only TikTok seems to auto-align and fill the screen. Although the TikTok Embed is narrow and it has a white background color behind the video itself that fills the full width of the parent container.

We might be able to get around this by setting a width on the embed and putting it in a div with display flex and justify content center. I'll play around with sizing a bit and see if I can get things working.

Just to be clear, this is an example of what I'm seeing.
I have a parent container with a red background color and two embeds inside.
`
<TwitterEmbed
width={'100%'}
url='https://twitter.com/PixelAndBracket/status/1356633038717923333'
/>
<TikTokEmbed
width={'100%'}
url='https://www.tiktok.com/@epicgardening/video/7055411162212633903?is_copy_url=1&is_from_webapp=v1'
/>

`
Look at how the TikTok does fill the full width, but it does with the parent container holding the TikTok iframe I'm assuming.

@timomak TikTok is a little tricky because the iframe has a white background. This is TikTok, not me. But I was able to work around that by surrounding the embed in a div, centering the contents, and sizing the embed to a width of 325. I also added a border radius to the div, too, to match TikTok's. This seems to have done the trick.

Beatiful! That worked!!

Badass. 💪


Replacing PROJECT_SPOTS and MCQUANT by more optimized method

PR checklist
The main feature of this PR is to replace the PROJECT_SPOTS and MCQUANT modules with a new module (SPOTS2CELL, temporary name). The new module needs only a fraction of the time and RAM to process the same data.
Addresses #11

[x] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/molkart branch on the nf-core/test-datasets repository.
[x] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[x] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

@kbestak : Currently still contains commented out portions for PROJECT_SPOTS and MCQUANT!

LGTM! Closes #11


feat: add math/base/special/ahaversinf

Resolves #649.
Description

What is the purpose of this pull request?

This pull request:

Resolves part of #649 by adding C implementation for math/base/special/ahaversinf

Related Issues

Does this pull request have any related issues?

This pull request:

resolves #649

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

Open to reviews!!
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

ready for review @Planeshifter !

kindly let me know if i should add @stdlib/number/float64/base/to-float32 to manifest.json, thank you for your time.


I don't get errors on Windows, but I get errors in Docker. Why

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f7c765d690f, pid=1, tid=0x00007f7cb84c6700
#
# JRE version: OpenJDK Runtime Environment (8.0_412-b08) (build 1.8.0_412-b08)
# Java VM: OpenJDK 64-Bit Server VM (25.412-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libscip.so.9.1+0x61790f]  SCIPisPackingPartitioningOrbitope+0x16f
#
# Core dump written. Default location: //core or core.1
#
# If you would like to submit a bug report, please visit:
#   https://access.redhat.com/support/cases/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

Without more details on what you are trying to do:

What distribution are you on? The bug report link sounds like RHEL, is that it? Which version?
Are you using the latest JSCIP from git master? (You should.) Or if not, which revision?
Which version of SCIP are you using? (If you used a different version at compile time than at runtime, then please mention both versions. That should technically work, but there may be bugs limiting the binary compatibility. So recompiling against the version used at runtime would be the first thing I would try in that case.)
Can you share a minimal testcase that reproduces the crash for you? I am not asking for your whole application, especially not if it is proprietary, but for a test case that is as small as possible and still reproduces the crash. (In particular, the test case should be compilable so I can try to reproduce the crash with it.)

I cannot really help you, so please provide the missing information. (I am using JSCIP on GNU/Linux and it does not crash for me. And I doubt the Docker container makes any difference there.)

Can you please provide the missing information? Otherwise, I will have to close this report as non-reproducible.

I cannot reproduce this bug. Insufficient details were provided.


Updated readme

Test request changes: elaborate on image, machine type, zone, and region variables.


Update create cluster examples

What would you like to be documented:
Cover all available parameters in some examples
Why is this needed:
our examples don't cover all the options. It would be good if we can provide an example usage of all available parameters. It doesn't all have to be in a single example but rather all parameters must be used at least once across all the provided examples.

too generic to action upon right now. As we come up with specific examples we will add issues.


Issue 253

Fix for issue-253
I switched the demo picker to use an object as it's ItemSource to demonstrate.
The fix is based on infomation from microsoft docs

Not sure if this is the best way, but it seems to work.

It seems ok, let me change base branch to 2.5, we can release it as patch version of 2.5

I'll get it with cherry-pick later. thanks for your contribution 💚


chore: Proposal for 1.0.1

I think you will need to regenerate the package-lock.json file after updating the version in package.json. I usually just delete it, then run
npm install --package-lock-only

@markdirish
I've updated the package-lock.json in https://github.com/IBM/nodejs-itoolkit/pull/360/commits/ede9d15e65319b8b6d983d955f4341ef81ea896c


IOLoop timer not work with IPC::Run3 on Windows

Mojolicious version: 7.34
Perl version: 5.20
Operating system: Win7, Active Perl

Steps to reproduce the behavior
use strict; use warnings; use 5.012;
use Mojo::IOLoop::ForkCall;
use IPC::Run3;
use POSIX;
Mojo::IOLoop->singleton->timer(1, sub { say '1s' });
my $pid = fork;
if ( ! $pid ) {
run3('perl -e "sleep 10"', undef, \ my $stdout, \ my $stderr);
#system('perl -e "sleep 10"');
exit;
}
Mojo::IOLoop->singleton->recurring(1, sub { waitpid $pid, WNOHANG and Mojo::IOLoop->singleton->stop });
Mojo::IOLoop->singleton->start;
Expected behavior
print following to screen:
1s
Actual behavior
timer no work, NOTHING got on screen
If replace run3 with system, it will be OK.

This example is very confusing. You import Mojo::IOLoop::ForkCall though you don't use it. You fork manually but don't do important parts of ForkCall (or Mojo::IOLoop::Subprocess that make it DWYM) and windows is always a problem for forking since windows "fork" is emulated by threads. I highly recommend you just use Mojo::IOLoop::Subprocess to do this work since it really isn't trivial.

Subprocess and ForkCall use almost the same mechanism though perhaps you are right, the communication method for Subprocess I guess does exclude (native) Windows (though you can use WSL and Subprocess). The important parts include things like checking for process completion (without blocking) resetting the ioloop in the child, ignoring spurious handle closes etc etc. If you choose to do it on your own, please read the code of Subprocess and ForkCall carefully. Anyway, why not use ForkCall? Anyway Mojolicious really cannot support forking on (native) Windows.

@jberger, That's fine, I finally use system(1, @cmd) to do non-blocking sub-process in (native) windows, and wait the pid with WNOHANG in a ioloop timer, get the result through file, no fork and no pipe, which seems worked  well for me. On linux, i still use ForkCall. Thank you .


ca: Update NewRootCA to validate both the root cert and the root key

The root certs should not just be self-signed, but should be currently valid and not expired.
The root CA key should be a supported key type.  CFSSL only generates ECDSA keys that are P256, P384, and P512 (otherwise for P224 it seems to result in a certificate using SHA1), so we should only accept those types of keys.
Also support RSA keys.
This is necessary because if we support root CA rotation, we need to make sure we only accept certain types of certs and keys.

Current coverage is 54.06% (diff: 100%)

Merging #1902 into master will increase coverage by 0.30%

@@             master      #1902   diff @@
==========================================
  Files           106        106
  Lines         18367      18386    +19
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           9873       9940    +67
+ Misses         7282       7231    -51
- Partials       1212       1215     +3

Powered by Codecov. Last update f5a96ef...b7ba062

LGTM

cc @diogomonica

LGTM

Rebased to make sure there are no semantic conflicts.  Merging.


[hotfix] run mvn spotless to fix code style violations.

Currently, there is no spotless violation in flink-cdc-pipeline-connectors. When run mvn spotless:apply  locally , will throw Exception.

@PatrickRen , CC


ci: use --locked for MSRV cargo-ndk install

A transitive dependency of cargo-ndk, regex-automata,increased its MSRV and so installing cargo-ndk at version 2.12.7 breaks in the MSRV CI task unless we use the pinned Cargo.lock version, or upgrade our MSRV in turn.
See https://github.com/rustls/rustls-platform-verifier/pull/30 for previous struggles related to cargo-ndk and maintaining a MSRV of 1.64.
Resolves https://github.com/rustls/rustls-platform-verifier/issues/37.

Am I the only one seeing the "Merge without waiting for requirements to be met" box in GitHub's UI? This looks like a previously unknown side effect of the branch protection experiments in #33. I guess that needs revisited, again.

Am I the only one seeing the "Merge without waiting for requirements to be met" box in GitHub's UI?

I can confirm I'm seeing the same thing.

This looks like a previously unknown side effect of the branch protection experiments in https://github.com/rustls/rustls-platform-verifier/pull/33. I guess that needs revisited, again.

Ah bummer. I can take a closer look ~Monday. In the mean time I'll just break-glass merge to fix the CI job.


Feature Request: Progress bar

Gamification makes everything better. I use iBom in soldering workshops, there positive reinforcement ("you managed to place half of the parts") helps participants.
For large BOMs. that don't render fully on the screen without scrolling, this would be a nice indicator on how far one has already progressed in the assembly.

There is one already, tucked into the stats menu.


For #111 : dynamic layers in Wegue format

Introduces a new Wegue Layer type LAYERCOLLECTION which is mainly a URL pointing to a remote endpoint (or file local to the Wegue App) that contains an array of Wegue Layers (which in theory could even again contain LAYERCOLLECTIONs).

As the loading of the URL (via fetch()) is asynchronous, several functions are now async/await (ES2015 syntax).
test added, NB final version needs to point to Wegue GH link

Later similar "expanding layer types" could be added for WMS, WFS etc (via GetCapabilities) and even OGC OpenAPI Features ("WFSv3").

@chrismayer sorry, your questions escaped me.
ad 1) test/unit/specs/ol/Map.spec.js was a duplicate of test/unit/specs/components/ol/Map.spec.js.
ad 2) me = this is uneccessary in ES2015 with arrow functions
Ok strictly not part of issue, but cleanup which I considered too minor for issue/PR.

Thanks for clarification.
One further point: Due to asynchronous handling the position in the mapLayers array is not resprected for type LAYERCOLLECTION. In the app-conf.json the demo layer for a LAYERCOLLECTION is laced somewhere in the middle of the mapLayers array but is rendered topmost in the layer stack.

Hmm, yes. The Layers coming from the LAYERCOLLECTION are reversed as to have them internally added bottom to top just like the regular Layers. But yes, the async nature could lead these always added as last/topmost. Tough problem to solve, if ever a problem in practice: 1) usually the entire app is configured from a single LAYERCOLLECTION or the latter is a series of overlay Layers on top of regularly configured baselayers (Geolicious use case).
Solution would be to "stack" any remaining regular Layers (not adding them) after the LAYERCOLLECTION and add them after the async finishes. Would be interesting with multiple LAYERCOLLECTIONs....
As an alternative, for progress, we could merge this PR and open a new issue for "LAYERCOLLECTION  messes up Layer stack ordering"...


Candidate -> document shortcut

This adds a document field to Candidate that is automatically populated during extraction by climbing up the context hierarchy until we arrive at the doc parent. This is useful for doc-level information tasks where our goal is to eventually reconstruct document-level labels, but we frame it as an extraction task over sub-doc-level candidates (Span, Sentence, etc.).
These commits also add an index on Candidate.type which speeds up stuff when running multiple extraction tasks with different Candidate-subclasses, which we'll reference in a later PR.

Seems like tests rely on spouse.db and its schema. Would be a lot easier if that wasn't the case. This means we somehow have to figure out how to update the test schema every time we make a change that affects schema.

Seems like tests rely on spouses.db and its schema. Would be a lot easier if that wasn't the case. This means we somehow have to figure out how to update the test schema every time we make a change that affects schema.

@ajratner Is the code you used to generate spouses.db somewhere in there so we can just re-run that with the new stuff in SQLAlchemy tree and won't have to migrate the schema manually? I imagine it's just more or less the db generated by one of the tutorials?

Yeah it should just be the one from the intro tutorial!
On Thu, Aug 16, 2018 at 3:56 PM Catalin Voss<EMAIL_ADDRESS>wrote:

@ajratner https://github.com/ajratner Is the code you used to generate
spouses.db somewhere in there so we can just re-run that with the new
stuff in SQLAlchemy tree and won't have to migrate the schema manually? I
imagine it's just more or less the db generated by one of the tutorials?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/snorkel/pull/1013#issuecomment-413708652,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABgw_ZF19NVStWbLfYIDQ7S2GweUadkPks5uRfiegaJpZM4WAa0B
.

@ajratner I re-ran, Intro Tutorial 1 and 2, but the output snorkel.db is now 272.4 MB, so too big to put onto git. 😞 Looks like we also have to recreate crowdsourcing.db in the tensorflow dir. I don't have a pyspark setup on my laptop, so could you look into re-running that or we can look tomorrow?

@stephenbach any chance you could push the scripts you used to generate the test data?  @CatalinVoss

@CatalinVoss can you just try re-running on your fork?  I don't have pyspark currently installed either but is quick to install.  Then you can just filter the number of docs (for intro tutorial, n_docs=500 or similar)?  Is there a reason this wouldn't work?

Hi @CatalinVoss, we've moved the information extraction version of Snorkel (v0.7) to https://github.com/snorkel-team/snorkel-extraction. Feel free to reopen this PR there!

We're no longer using snorkel. But happy to see the new stuff


naming a memory broken

enter a number
click '->M1'
click 'M=' to open memory editor
click pencil icon next to M1
type 'seven'
click 'save'

expect: the name to appear below the number in M1
actual: no text there at all

Fixed by 4d708a417174951294be8b5dcaeacf59ff4899df


Playground not loading on my local machine

This issue pertains to:

[ ] GraphQL Playground Middleware

What OS and OS version are you experiencing the issue(s) on?
Mac High Sierra
What version of graphql-playground(-electron/-middleware) are you experience the issue(s) on?
graphql-playground-middleware: ^1.1.0
What is the expected behavior?
The Playground loads without any issues.
What is the actual behavior?
Playground never completes loading.
Throws error:
GET<EMAIL_ADDRESS>net::ERR_CONTENT_DECODING_FAILED
Should the GET request for middleware.js go to an https:// location instead of http://?
What steps may we take to reproduce the behavior?
I'm attempting to use the Playground with the serverless-graphql-apollo stack here: https://github.com/graphcool/graphql-playground

Maybe @sid88in could take a look?

@JstnEdr we merged a fix for graphql playground yesterday https://github.com/serverless/serverless-graphql-apollo/pull/192 and it works fine. There is a minor issue while running on sls offline  https://github.com/graphcool/graphql-playground/issues/278 and @timsuchanek is already looking into https://github.com/graphcool/graphql-playground/issues/278 (reported by others too)

@JstnEdr thanks for reporting!
It seems that you're trying to use the graphql-playground-middleware package, but we split it into multiple separate packages, for lambda it's graphql-playground-middleware-lambda.
Sorry for the incorrect docs there, that should be updated:
https://github.com/serverless/serverless-graphql-apollo/blob/master/app-backend/rest-api/handler.js
You can also refer to this part of our docs to see how to include it in your serverless application:
https://github.com/graphcool/graphql-playground#as-serverless-handler
Does that help?

Yes that helps. Playground appears to be working now, but there's something up with the graphql endpoint. I'm now getting the error Schema could not be fetched. with a 404 on the /graphql route. I'll keep an eye on #278

I'm not exactly sure if this is a problem with GraphQL Playground, but I'm still having trouble accessing the Playground in the browser. Any clues as to how to resolve this?

@JstnEdr still same version?

Thanks for the reply @Huvik! I've tried different versions. The screenshot shows I'm attempting to access version 1.3.6.
I've got "graphql-playground-middleware-lambda": "^1.3.6", in my package.json file.

Fixed in the latest version. Please let us know if you still have that issue, then we reopen it!

see also: https://github.com/apollographql/apollo-server/issues/1421

I had the exact same issue. What fixed it was changing my browser from Firefox to Chrome.


Top nav resource grouping

Allows resources to be grouped and labelled for ease of use, in the top navigation dropdown. The code for splitting resources into groups and rendering groups separately was already there, I just tweaked it to make the groups user-configurable and added labels :)
Adds a new option for a resource to define which group it belongs to, eg:
defmodule MyApp.ElementStep do
  use Ash.Resource, data_layer: AshPostgres.DataLayer, extensions: [AshAdmin.Resource]

  admin do
    resource_group(:elements)
  end
end

And also adds a new option for an API, to define human descriptions for each group, eg:
defmodule MyApp.Api do
  use Ash.Api, extensions: [AshAdmin.Api]

  admin do
    show?(true)
    resource_group_labels(elements: "Heading goes here")
  end
end

In practice it looks like this:

All resources that don't have a group defined get listed at the end as usual; these can also have a label configured by adding eg. nil: "Everything else" in the resource_group_labels list. Missing labels are also just omitted.
I'm not sure if there's a great way within LiveView/Surface to easily conditionally render content - so I kinda hacked it in with a no_content helper function 😊

Looks great!
We can use the #if directive in surface to conditionally render content. https://surface-ui.org/template_syntax#{#if-...}
Additionally, you'll need to run mix ash.formatter to update the .formatter.exs file with your new DSL change.

Oh cool. I'll look at fixing those issues in the morning :)


Remove conformance to Decodable/Encodable.

This is related to issue #21.
Relying on the synthesized implementations for Decodable and Encodable restricts the ability of library users to implement custom decoding for this type. The impact this has downstream is significant:
Any of my types that have a NonEmpty property on them must now have a custom Decodable init, because NonEmpty does not support decoding from an array in a JSON response. If I were able to add this conformance in my own project, then I could write a single initializer that works with an array, which would allow me to rely on synthesized Decodable inits for my types that contain NonEmpty properties.
This PR removes both Decodable and Encodable with the intent of allowing downstream users to implement whatever support they need in their apps.

Do you have a specific SSCCE of why the current conformance is undesirable?

“SSCCE”
I do not know what that acronym means.

https://lmgtfy.com/?q=SSCCE

https://lmgtfy.com/?q=SSCCE

@BenLeggiero there are more effective ways to communicate than random acronyms and expecting people to look them up.
I explained in the PR description and the issue why this synthesized conformance is a detriment to users of the library. If there is something unclear, please let me know.

The explanations are sound, and I have read them. However, they have no examples of what cannot be currently done, which this PR addresses and makes possible.

Consider the following JSON:
{
  "id": 434,
  "name": "some name",
  "items": [
    "at least one item"
  ]
}

I can model that in Swift with:
struct Model: Decodable {
  let id: Int
  let name: String
  let items: NonEmpty<String>
}

However, because NonEmpty provides only default conformance to Decodable, I cannot use a synthesized decodable init here. Instead, I have to write my own. This will be true of any type that contains a NonEmpty property.

Also, it's quicker, easier, and a better learning experience to type "SSCCE" into your browser's search bar, than to write a message explaining that you don't know what it is. It also respects your conversation partner's time. Better for everyone 👍

It is good conversation etiquette to introduce an acronym before using it. Expecting your conversation partner and everyone else that reads this conversation to have to perform a search is not good etiquette. Explaining an acronym is a good teaching opportunity. Cheers!

Closing in favor of #14.


Attribution Wizard: Prevent empty attributions

Summary of changes
The apply button is disabled as long as the generated purl is invalid. This includes empty attributions but also ensures that a truthy package name is given. Additionally, booleans indicating whether a package name, namespace, or version is selected are removed since these are always true due to pre-selection.
Context and reason for change
Empty attributions are forbidden and should be avoided.
How can the changes be tested
Open the attribution wizard and select empty package name.
Fix: #1451

@antonbauhofer regarding your comment.

In the summary, you write that version etc. are always true due to pre-selection. Can you elaborate on that?

The wizard is opened via the context menu of a manual attribution. The package attributes of this manual attribution like name, namespace, and version are pre-selected in the corresponding lists in the wizard (the - entry if the attribute is empty). Therefore, it is not possible that no item in a list is selected. The corresponding flags are therefore always true and hence unnecessary.


[Python] Failure to send a tensor of < 4 bytes to host

Problem description
The following python code will fail with the following error
Traceback (most recent call last):
  File "/home/quinn/model_testing/only_conv.py", line 116, in <module>
    print(iree_output.to_host())
          ^^^^^^^^^^^^^^^^^^^^^
  File "/home/quinn/iree-build/runtime/bindings/python/iree/runtime/array_interop.py", line 107, in to_host
    self._transfer_to_host(False)
  File "/home/quinn/iree-build/runtime/bindings/python/iree/runtime/array_interop.py", line 135, in _transfer_to_host
    self._host_array = self._copy_to_host()
                       ^^^^^^^^^^^^^^^^^^^^
  File "/home/quinn/iree-build/runtime/bindings/python/iree/runtime/array_interop.py", line 162, in _copy_to_host
    self._device.queue_copy(
ValueError: Source and target buffer length must match and it does not. Please check allocations

import torch

module = """
#map = affine_map<(d0, d1) -> (d0, d1)>
#map1 = affine_map<(d0, d1) -> (d0)>
module {
  func.func @forward(%arg0: tensor<1x?xf16>) -> tensor<1xf16> {
    %c1 = arith.constant 1 : index
    %dim = tensor.dim %arg0, %c1 : tensor<1x?xf16>
    %0 = tensor.empty(%dim) : tensor<1x?xf16>
    %c1_0 = arith.constant 1 : index
    %dim_1 = tensor.dim %arg0, %c1_0 : tensor<1x?xf16>
    %1 = tensor.empty() : tensor<1xf16>
    %cst = arith.constant -6.550400e+04 : f16
    %res = flow.dispatch.region -> (tensor<1xf16>) {
      %2 = linalg.fill ins(%cst : f16) outs(%1 : tensor<1xf16>) -> tensor<1xf16>
      %3 = linalg.generic {indexing_maps = [#map, #map1], iterator_types = ["parallel", "reduction"]} ins(%arg0 : tensor<1x?xf16>) outs(%2 : tensor<1xf16>) {
      ^bb0(%in: f16, %out: f16):
        %7 = arith.maximumf %in, %out : f16
        linalg.yield %7 : f16
      } -> tensor<1xf16>
      %cst_2 = arith.constant 0.000000e+00 : f16
      %4 = linalg.fill ins(%cst_2 : f16) outs(%1 : tensor<1xf16>) -> tensor<1xf16>
      %5 = linalg.generic {indexing_maps = [#map, #map1, #map1], iterator_types = ["parallel", "reduction"]} ins(%arg0, %3 : tensor<1x?xf16>, tensor<1xf16>) outs(%4 : tensor<1xf16>) {
      ^bb0(%in: f16, %in_3: f16, %out: f16):
        %7 = arith.subf %in, %in_3 : f16
        %8 = math.exp %7 : f16
        %9 = arith.addf %8, %out : f16
        linalg.yield %9 : f16
      } -> tensor<1xf16>
      flow.return %5 : tensor<1xf16>
    }
    return %res : tensor<1xf16>
  }
}
"""

example_input = torch.FloatTensor([[2.0, 0.0]]).half()

# Run through IREE vulkan
import iree.runtime as ireert
from iree.runtime import get_driver, get_device
import iree.compiler as ireec

device = "vulkan"
runtime_device = "vulkan"

flatbuffer = ireec.compile_str(
    module,
    target_backends=[device],
    extra_args=[
        "--iree-vulkan-target-triple=rdna3-unknown-linux",
        "--iree-stream-resource-index-bits=64",
        "--iree-vm-target-index-bits=64",
        ],
)

config = ireert.Config(driver_name=runtime_device)
vm_module = ireert.VmModule.from_flatbuffer(config.vm_instance, flatbuffer)
ctx = ireert.SystemContext(config=config)
ctx.add_vm_module(vm_module)
forward = ctx.modules.module["forward"]
iree_output = forward(example_input.numpy())

# Fails due to a size mismatch between the source and target buffer
print(iree_output.to_host())

Investigation
The source (device) buffer will be 2 bytes for the single f16, however when trying to allocate the host buffer to copy into (https://github.com/openxla/iree/blob/d991dc9330d486b804a204e6e18f8287c256def1/runtime/bindings/python/iree/runtime/array_interop.py#L153), it ends up padding the allocation to 4 bytes, causing the sizes to mismatch.

maybe could change the check in hal.cc #590 to instead take min(source_length, target_length) until the TODO in there for providing offsets/length is done

maybe could change the check in hal.cc #590 to instead take min(source_length, target_length) until the TODO in there for providing offsets/length is done

That works for my case, but there are actual tests for this https://github.com/openxla/iree/blob/13de9f3bf706938027fcac9cccc89a02ff7d2ac6/runtime/bindings/python/tests/hal_test.py#L294
Is there some way to get the expected alignment for a buffer like this?

Actually I see the byte offset and length is already on the iree_hal_buffer_t https://github.com/openxla/iree/blob/13de9f3bf706938027fcac9cccc89a02ff7d2ac6/runtime/src/iree/hal/buffer.h#L856
And the HalBuffer class looks a reference to an iree_hal_buffer_t https://github.com/openxla/iree/blob/13de9f3bf706938027fcac9cccc89a02ff7d2ac6/runtime/bindings/python/hal.h#L175
How hard would it be to just use the offsets/lengths directly.

I can look when at my desk. I don't think alignment will be a problem. An allocation sufficient for a 4byte transaction will always be sufficient for a two byte one.

I can look when at my desk. I don't think alignment will be a problem. An allocation sufficient for a 4byte transaction will always be sufficient for a two byte one.

Makes sense, just trying to understand the reasoning behind the original check. If source < target is always fine then that works for me.


FIX: do not error our when checking comparison with non-Header

Power-cycled to run against new GitHub Actions CI.

Found the issue, fixed it for you.

Thanks!


Greenkeeper/monorepo.enzyme 1.8.0

:tada: This PR is included in version 5.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add support for HTTP Bearer Security Scheme

Uses the existing accessToken function for the bearer scheme.
I've added tests but not sure what else needs tweaking if anything

Wow thanks @mrlubos ! Thanks for the awesome project 😄
Yes we have an external API we're looking to build a client for, which uses JWT:
JWT:
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: A JWT that was previous generated

I also have another PR in the works so I will see if I can get that through too!

Feel free to connect with me on LinkedIn/Discord/email if you need any input before it's ready. Otherwise, Happy New Year!


Empty File

hi, think you for your code its awsome, im using it to connect to Ftps server, rename and delete is working fine but when i try to upload a file from my folder to ftps files are always empty, i find them on the the FTP server but with size 0
this is my code plz help me i cant find a solution
Private Sub GetCsvFiles()
        Try
            Dim ftps = New FtpClient
            ftps.Host = "111.222.333.444"
            ftps.Credentials = New Net.NetworkCredential("aaaa", "bbbb")

            ftps.Port = 990
           ftps.DataConnectionType = FtpDataConnectionType.PASVEX

            AddHandler ftps.ValidateCertificate, AddressOf OnValidateCertificate

            ftps.EncryptionMode = FtpEncryptionMode.Implicit

            ftps.Connect()

            ftps.UploadFile("C:\envoisgtms\20212220.zip", "/testt/20212220.zip", FtpRemoteExists.Overwrite, FtpVerify.Retry)
            ftps.DownloadFile("C:\envoisgtms\test3.txt", "/testt/test3.txt")
                ftps.DeleteFile("/testt/20211230.zip")

            If ftps.IsConnected Then
                  ftps.Disconnect()
            End If
        Catch ex As Exception
            Console.WriteLine(ex.Message)
            MsgBox(ex.Message)
        End Try

If you want to accept all certs just use ValidateAnyCertificate = True rather than AddHandler ftps.ValidateCertificate, AddressOf OnValidateCertificate.

I have also empty file on remote ftp when I use UploadBytesAsync

@svarga91  Please make a new issue and add the detailed FTP logs so we can figure it out.

@svarga91 Is this issue still open on your side?
We need a full verbose log to find out why the uploaded file is empty. Perhaps the server is producing some error message, so a server log is also always a good idea in such a situation.
At least also state what version of FluentFTP you are using? Or get the current newest version which has more debugging messages in a verbose log.


[Protobuf] Array of integer other than i32 or u32 are not working

with version<EMAIL_ADDRESS>all
// @ts-ignore: decorator
@massaExport()
export function testArray3(arg1: Array<i8>): Array<i8> {
  return arg1;
}

// @ts-ignore: decorator
@massaExport()
export function testArray4(arg1: Array<i16>): Array<i16> {
  return arg1;
}

// @ts-ignore: decorator
@massaExport()
export function testArray7(arg1: Array<i64>): Array<i64> {
  return arg1;
}

// @ts-ignore: decorator
@massaExport()
export function test9(arg1: Array<u128>): Array<u256> {
  return arg1.map<u256>((arg) => arg.toU256());
}

are failing to build

@Ben-Rey
Simple arrays, event those of custom_types (i.e. u128 / u256) seems to work correctly on as-transformer side: .proto and helpers are looking good.
array of array are not supported: quite some more work is required and it has to be based upon #291
Impact of cli side has to be measured


feat: update website to use gatsby-carbon-theme

WhAt in tarnation happened here

Are you okay

Are you okay

Nope

WhAt in tarnation happened here

trying to get CircleCI to work 😭

@alisonjoseph Can you try the circleci/node10 image for CircleCI? And see if you can bump up memory on the instances? We build gatsbyjs.org with that image and GATSBY_CPU_COUNT=8 env

You might want to hard code it to GATSBY_CPU_COUNT=2 or GATSBY_CPU_COUNT=1 if you have the default instances on CircleCI
We set it to GATSBY_CPU_COUNT=8 for the xxlarge ones I think


Out of memory - GTX 1650 4G

What is the issue?
CUDA error: out of memory
current device: 0, in function ggml_cuda_pool_malloc_vmm at C:\Users\jmorg\git\ollama\llm\llama.cpp\ggml-cuda.cu:8583
cuMemCreate(&handle, reserve_size, &prop, 0)
GGML_ASSERT: C:\Users\jmorg\git\ollama\llm\llama.cpp\ggml-cuda.cu:256: !"CUDA error"
What did you expect to see?

Steps to reproduce
No response
Are there any recent changes that introduced the issue?
No response
OS
Windows
Architecture
x86
Platform
No response
Ollama version
0.1.28
GPU
Nvidia
GPU info

CPU
Intel
Other software
No response

I'm encountering the same issue when loading images into LLaVA : latest. GTX 1650, 4gb.
I'm getting server errors that I suspect are from the CUDA error.
PROMPT & RESPONSE:

What's in this image? \img.png
Added image '\img.png'
Error: Post "http://<IP_ADDRESS>:11434/api/chat": read tcp <IP_ADDRESS>:52531-><IP_ADDRESS>:11434: wsarecv: An existing connection was forcibly closed by the remote host.

SERVER LOG:
...
encode_image_with_clip: image encoded in  1229.16 ms by CLIP (    2.13 ms per image patch)
CUDA error: out of memory
current device: 0, in function ggml_cuda_pool_malloc_vmm at C:\Users\jeff\git\ollama\llm\llama.cpp\ggml-cuda.cu:8658
cuMemSetAccess(g_cuda_pool_addr[device] + g_cuda_pool_size[device], reserve_size, &access, 1)
GGML_ASSERT: C:\Users\jeff\git\ollama\llm\llama.cpp\ggml-cuda.cu:256: !"CUDA error"

i have a similiar issue on rtx3060 and win 11:
CUDA error: out of memory
current device: 0, in function ggml_cuda_pool_malloc_vmm at C:\Users\jeff\git\ollama\llm\llama.cpp\ggml-cuda.cu:8644
cuMemAddressReserve(&g_cuda_pool_addr[device], CUDA_POOL_VMM_MAX_SIZE, 0, 0, 0)
GGML_ASSERT: C:\Users\jeff\git\ollama\llm\llama.cpp\ggml-cuda.cu:256: !"CUDA error"
The Error occures after passing a few inputs to a running chatmodel. I populate embeddings to a vectordb before chatting with the model. Not sure if that is relevant, but just in case.

This should be improved as of 0.1.32 - please let me know if you're still seeing an error!


[SPARK-20738][BUILD] Hide building of docs in sbt behind an option.

sbt publish-local tries to build the docs along with other artifacts
and as the codebase is being updated with no build checks for sbt docs build.
It appears to be difficult to upkeep the correct building of docs with sbt.
An alternative is, we hide building of docs behind an option -Dbuild.docs=false.
This is also useful, if someone uses sbt publish and does not need the building of docs
as it is generally time consuming.
The default behavior is unchanged. If the option is not set, the docs are built by default.
How was this patch tested?
Manually running the build with and without the option.

Test build #76934 has started for PR 17983 at commit a43159e.

Test build #76934 has finished for PR 17983 at commit a43159e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76934/
Test PASSed.

@srowen Can you please take a look !


Is Producer 300 ms Connect time to a Broker normal when network time is 50 - 60 ms?

Description
When a message arrives to the producer for a Broker that is not connected yet it takes around 300 ms to connect to the brokers (connect, apiversion queries, metadata queries included). The network time is something like 50 ms - 60 ms. Is 300 ms a normal connect time? Is there anything we can do to get this down closer to the normal rtt time for produce requests?
How to reproduce

Have a Kafka cluster with 5 brokers.
Have a topic with 32 partitions.
Send message to the producer in a loop - eventually you will hit a broker that is not connected yet.
Observer that this first time connect takes around 300 ms (connect, apiversion\metadata queries).
Latency for this first message is around 360 ms (300 ms connec time + usual 60 ms produce time).

KafkaReconnectTest.zip
broker_first_time_connect.txt
Checklist
Please provide the following information:

[x] A complete (i.e. we can run it), minimal program demonstrating the problem. No need to supply a project file.
[x] Confluent.Kafka nuget version.
v1.4.3
[x] Apache Kafka version.
kafka_2.12-2.3.0
[x] Client configuration.
[x] Operating system.
Producer client running on Windows 10 pro, 12 cores
[x] Provide logs (with "debug" : "..." as necessary in configuration).
Attached.
[ ] Provide broker log excerpts.
[ ] Critical issue.

following on from #1308
The time cost should be entirely due to the network RTT (cost on broker should be negligible). 300ms seems a bit higher than i'd guess given a 60ms RTT - since (i think) you need to pay that only three times, but it's in the same ballpark.

I don't think non-sparse connections is the proper way to fix connect latency, it will just increase the load on the cluster and further increase connect latency (via @edenhill).

Number of connections has negligible impact on load unless you have thousands of them (based on my own testing). Connection establishment (particularly SSL) is more expensive, and will have a greater impact on server load if occurring frequently. In the above scenario, it seems reasonable to me that you might legitimately prefer a setup where connections stay primed. For higher throughput applications sparse connections will pretty much have no impact on p99 latency. But if you have a super low throughput application (which I think we should be accommodative of), you're going to pay a big price on average latency. Especially if your clients are distant from your brokers (which i would guess is more likely that people would want in super low throughput use cases). This definitely shouldn't be on by default! I'm just saying there are some cases where it seems to make sense to me (based on what I can see atm).

Number of connections has negligible impact on load unless you have thousands of them

That stance is client-centric though, from a broker perspective it will have an impact, and consequently also impact the clients, thus a system-wide concern.
enable.sparse..=off will bring other problems, such as the Azure load balancer idle disconnects that are not discovered until a request times out (60s by default), and even with more standard environments these connections will be idle-reaped and increase the load on the cluster.

@edenhill @mhowlett Thank you both for your responses.

@edenhill Yes if we set enable.sparse.connections=fasle - we could get even worse latency or at least no improvement because at low throughput after 4 or 5 minutes azure will silently kill them and the next metadata refresh, or message for that killed broker connection will take 20 seconds (still not sure why it is always 20 seconds as we are at default socket.timeout.ms?, but in any case a long time relatively speaking).

In the attached logs I see 3 or 4 places where the 300 ms is spent:

Am guessing this is the connect (seems to be ballpark 3 rtt's - 3 x 60 ms ~ 200 ms)?:
[Debug] [2020-06-08 12:28:18.773] name: rdkafka#producer-1, facility: BROADCAST, level: Debug, message: [thrd:kafkabk2.something.com:9092/boots]: Broadcasting state change
[Debug] [2020-06-08 12:28:18.920] name: rdkafka#producer-1, facility: CONNECT, level: Debug, message: [thrd:kafkabk2.something.com:9092/boots]: kafkabk2.something.com:9092/2: Connecting to ipv4#<IP_ADDRESS>:9092 (plaintext) with socket 2020

QRYLEADER - 18 ms. Should this take 18 ms - is there any IO here? Looks like we haven't finished connecting to broker yet here.
[Debug] [2020-06-08 12:28:18.920] name: rdkafka#producer-1, facility: TOPPAR, level: Debug, message: [thrd:kafkabk2.something.com:9092/boots]: kafkabk2.something.com:9092/2: 32-part-test-topic [20] 1 message(s) queued but broker not up
[Debug] [2020-06-08 12:28:18.938] name: rdkafka#producer-1, facility: QRYLEADER, level: Debug, message: [thrd:main]: Topic 32-part-test-topic [0]: broker is down: re-query

Additional 60 ms. Not sure why. Is some other operation blocking us here? I see there is a metadata request happening on kafkabk0 at the same time.
[Debug] [2020-06-08 12:28:18.920] name: rdkafka#producer-1, facility: CONNECT, level: Debug, message: [thrd:kafkabk2.something.com:9092/boots]: kafkabk2.something.com:9092/2: Connecting to ipv4#<IP_ADDRESS>:9092 (plaintext) with socket 2020
[Debug] [2020-06-08 12:28:18.984] name: rdkafka#producer-1, facility: CONNECT, level: Debug, message: [thrd:kafkabk2.something.com:9092/boots]: kafkabk2.something.com:9092/2: Connected to ipv4#<IP_ADDRESS>:9092

Then we have 2 x APIVersion Request\Response ~ 120 ms. This makes sense - although is there some way to do only 1 here?

The final produce request. As expected ~ 50 ms.

Could you please provide feedback on the above. Thank you very much.

What is your machine specs? Is it a shared instance? How many vcores? What is the CPU and system load?


Inline whenever to let Mockito's UnfinishedStubbing messages work

When Mockito detects unfinished stubbing, it will spit out an error containing:
Unfinished stubbing detected here:
-> at com.nhaarman.mockitokotlin2.OngoingStubbingKt.whenever(OngoingStubbing.kt:42)

This is not useful in helping users track down unfinished stubbing.  Instead, we inline whenever
to make it read as:
Unfinished stubbing detected here:
-> at com.MyTest.testMyThing(MyTest.kt:785)

Nice one, thanks!


Link .NET Core 3.0 SDK or later must point to the latest download

Link ".NET Core 3.0 SDK or later" is https://dotnet.microsoft.com/download/dotnet-core/3.0 that has 3.0.1 version while the latest is 3.1 which is correctly pointed to in output of "dotnet --info" and is
https://dotnet.microsoft.com/download - has 3.1.
This is important, because having 3.0.1 then leads to failure install EF framework on the next step of tutorial.

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

ID: a25bf940-8977-fec4-461b-542a9f550fc8
Version Independent ID: 5492c641-af15-64b8-beaa-ddf511be73e6
Content: Tutorial: Get started with Razor Pages in ASP.NET Core
Content Source: aspnetcore/tutorials/razor-pages/razor-pages-start.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

This is important, because having 3.0.1 then leads to failure install EF framework on the next step of tutorial.

It works fine with 3.0.100

I couldn't make it work with 3.0.101 as "dotnet tool install --global dotnet-ef" attempted installing EF version 3.1 (the latest version available) which failed complaining about incompatibility with 3.0.101 SDK.


Add a .npmignore file

Going though npm packages I use and making them lighter.

Much more should be added, namely .jshintrc, .npmignore and History.md.
A files entry in package.json could also be a solution.

A long time I know, but how's that?

Thanks!


New config entries

I added two new config entries.
One for the atomic disassembler energy usage for request #2146.
The second for the ethylene burn time as I always felt that ethylene produced too much gross power compared to how much is produced from a single piece of wheat. Lowering to burn time from 40 to 20 or even 10 seemed to make a better balance on the servers I have run.

Excellent PR, thanks


Loot tables

There should be a way to declare an inventory as a loot table, causing it to be populated with loot when it is opened. This most certainly requires item stamps to be done better.

Here's a proposed idea on how it'll work.

Loot tables can roll into other loot tables.
For each loot table, the individual items / loot tables can be given a weight.
The amount of times to roll for can be specified within a loot table, as well as whether replacements are allowed.


update the pull request url in index.js

this should theoretically work, i didn't test this at all cuz i don't use javascript

oops


Make tests faster to run and easier to write

Split Ordinal, Height, Epoch stuff into its own crate. Will be fast to compile and run unit tests. No I/O or state.
Figure out how to unit-test server. Should be able to run and test in-process for speed. The blockchain explorer can be tested against blocks and transactions that we construct, and doesn't need its own bitcoin core node. Bring back the fake RPC server.
The wallet does need to talk to bitcoind, however, for tests which are about logic and error handling, create a separate crate (or just struct or whatever) that takes all information that it needs to construct a transaction or perform a function, and returns a result, without doing I/O, and we can intensively test that, and as long as we call it correctly, things will work.

Done!


wallet storage adapter butchers objects in node

The SDK should support a wallet storage adapter without the enduser having to wrap it, see:
So locaforage butchers objects it stores, and returns not what was passed to it. To make it work, there's a small wrapper needed
Here's the wrapper code:
  constructor() {
    this.forage = localforage;
    this.isConfig = false;
  }

  config() {
    this.isConfig = true;
  }

  async setItem(key, item) {
    console.log('setItem', key, item);
    if (typeof item === 'object') {
      await this.forage.setItem(key, JSON.stringify(item));
    } else {
      await this.forage.setItem(key, item);
    }

    return item;
  }

  async getItem(key) {
    console.log('get item', key);
    const item = await this.forage.getItem(key);
    let res;
    try {
      res = JSON.parse(item);
    } catch (e) {
      res = item;
    }
    return res || null;
  }
}

@dashameter thank you for the details.
The butchering of the storage items should've been resolved in<EMAIL_ADDRESS>Here's a relevant pull request

please retest

retest passed