[tx] Handle dangling references

What should happen when the datom store starts as
[[101 :some/attr value tx]
 [102 :some/ref 101 tx]]

and then we transact [[:db/retract 101 :some/attr value]]?  The naive retraction leaves a dangling reference to an entid that no longer can be referenced.
If we need to do the equivalent of SQL's ON DELETE CASCADE, that's going to increase the cost of transacting, since it's potentially recursive and we need to maintain the authoritative transaction report.

I don't know what Datomic does in this circumstance.  @rnewman, do you?

Based on the discussion at https://groups.google.com/forum/#!topic/datomic/e4DvdR9bk2U, it appears that Datomic itself does not ensure that you don't have dangling references.  It's up to the application to use lookup-refs as appropriate.

There are a few reasons why this is this way:
Firstly, it's totally conceptually consistent for an entity to only be the object of relations. That is: retracting [101 :some/attr value tx] does not invalidate [102 :some/ref 101].
(You might rephrase your question in the reverse, retracting the other datom, and it would be just as meaningful!)
For example, consider an application that tries to figure out who the murderer was in a game of Clue. We record the killing:
[102 :clue/killedBy 101]

We assert:
[101 :clue/preferredMurderWeapon :candlestick]

then we later find out that it's not the case, and retract that new datom. We still have an entity that we use over time to refer to the killer: 101 is still the killer of 102.
Secondly, there is still a hint of the open world assumption in Datomic (even though it includes closed-world querying, retractEntity, et al). Entities aren't typed, reference attributes don't have defined type domains and ranges, and so on. "Dangling" is only really a concept under the closed world assumption.
Thirdly, Datomic entity IDs escape the store. 101 might be in use externally as the persistent identifier for some concept, be present in some message, etc.; that we're retracting the penultimate (or even the ultimate!) known datom that refers to 101 doesn't mean that it's still an entity in the realm of discourse, and more current facts might refer to it in the future. This means we can't reallocate entity IDs.
The concept of a dangling reference — that is, references to an entity ID for which no datoms have that entity in the e place — are a problem in some uses of Datomic for data modeling: ORMs (in which a dangling reference is equivalent to a dangling pointer) and closed-world relational systems with foreign key constraints (you can't have an order refer to an unknown line item; it's not useful to know that there was an item in the box, but not know what it was).
The Datomic way to enforce that the store remains in one of these valid subsets is to use database functions, as in this example. The functions can apply whatever constraints they wish: failure, cascade, synthesis, etc.

Does my comment suffice to close this, @ncalexan?

I think so.


Fix move bug on std::ofstream in driver code

Closes #110
Changes

directly open() the outfile stream instead of constructing the stream and assigning the open stream to the map

Testing

Re-ran the driver locally and was able to produce the appropriate nexus outflows

Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows project standards (link if applicable)
[x] Passes all existing automated tests
[x] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[x] Reviewers requested with the Reviewers tool :arrow_right:

Target Environment support

[x] Linux

Included in #113


Question if want to leave page

From<EMAIL_ADDRESS>on January 01, 2012 23:24:02
What steps will reproduce the problem? 1. Press back button in browser What is the expected output? What do you see instead? It should ask if I really want to leave the page because some data may not be saved.
Original issue: http://code.google.com/p/wwwsqldesigner/issues/detail?id=145

From ondrej.zara on January 01, 2012 23:34:28
What browser do you use? WWW SQL Designer indeed displays the named dialog when the page is about to be left...

From<EMAIL_ADDRESS>on January 02, 2012 05:17:31
Chrome 16

From ondrej.zara on January 03, 2012 04:52:56
Fixed in changeset 104:c702b405224d.
Status: Fixed
Owner: ondrej.zara

From<EMAIL_ADDRESS>on January 03, 2012 07:21:06
Worked perfectly! Thank you very much :)


Make package naming more consistent with skipping kn in the sub-dirs

Hmm, the package knative.dev/client-pkg/pkg/config already exists, as well. I believe, that's why I put it in here...
We should reconcile those two packages somehow. IMHO, we shouldn't be using the kn sub-package, as all of those packages are kn related, obviously.
IDK, maybe we should dump the kn sub-package, probably in a separate PR, to avoid confusion. But, that's a breaking change, so we should prepare migration as well.
WDYT on those two, already existing, config packages?
Originally posted by @cardil in https://github.com/knative/client-pkg/pull/139#discussion_r1504910909
Per the conversation on the linked PR. Let's follow-up on the package name changes.

/cc @cardil
/assign


Add ucx license in NOTICE-binary

UCX is licensed under BSD-3. They require the include of the license text included from  when redistributing binaries.
We distribute the jucx 1.8 jar with our spark-rapids jar, so adding the LICENSE from the 1.8.x branch, specifically: https://github.com/openucx/ucx/blob/84538d2d8753f9a597a6da3b5c7458b9c2bc178c/LICENSE,  to our NOTICE-binary file, which gets included into the spark-rapids jar, to comply with the redistribution in binary form clause.
When we move to the jucx 1.9+ jar, we will refresh our NOTICE-binary file, as needed.

build


feat: adjust org for tiflash_scripts repo

Adjust org for tiflash_scripts repo.

/hold
We should merge it when the repo was migrated.


Add mandatory hop

Add Builtin.hopToActor

SILGen this builtin to a mandatory hop_to_executor with an actor type
operand.

e.g.

    Task.detached {
      Builtin.hopToActor(MainActor.shared)
      await suspend()
    }

Required to fix a bug in _runAsyncMain.

@swift-ci test

Merging to unblock https://github.com/apple/swift/pull/37756
@rjmccall let me know if this is not what you had envisioned though and we can change it

lgtm!


Initial commits for basic nonspeculative FlexCPU.

This is a completish implementation of FlexCPU, based on up-to-date upstream.
There are commits that need to be rebased after the renaming refactor from SimpleDataflowCPU and I will deal with them later and create more pull requests. These are individual feature commits like branch prediction, interrupt handling, st-ld forwarding, etc.
There are known issues with stats. The basic simulator stats should be fine (ticks simulated, etc.), and most of the component stats like requests through the port should be fine too, but a few FlexCPU specific stats like histograms for average instruction lifespans between certain states aren't tracked correctly iirc, and I never got around to writing a patch for that.

I'm excited!
On Fri, May 3, 2019 at 4:46 PM Bradley<EMAIL_ADDRESS>wrote:

@animalvgamer https://github.com/animalvgamer requested your review on:
#121 https://github.com/darchr/gem5/pull/121 Initial commits for basic
nonspeculative FlexCPU..
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/darchr/gem5/pull/121#event-2318703420, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAA2YHDT7ZBNSYM7REXPTJDPTTFEBANCNFSM4HKXTZIQ
.

--
Jason Lowe-Power
Assistant Professor, Computer Science Department
University of California, Davis
3049 Kemper Hall
https://arch.cs.ucdavis.edu/

https://www.reddit.com/r/ProgrammerHumor/comments/bk8mvb/my_trash/?utm_medium=android_app&utm_source=share

More rebasing... https://gem5-review.googlesource.com/c/public/gem5/+/18579/

More rebasing... https://gem5-review.googlesource.com/c/public/gem5/+/18579/
and ... https://gem5-review.googlesource.com/c/public/gem5/+/18581

noooooooo


Recommender Protocol and Related Signature Changes

As discussed we intend to unify Strategy and Recommender
This is the first of three PRs intending to do so:

This PR

Introduce the RecommenderProtocol
Change all relevant signatures so both Strategy and Recommender are allowed under this protocol
This also required refactoring in the simulation module, Campaign.recommend and several examples
Also made select_recommender private as its an internal concept
Also performed two minor but long standing refactorings (see Azure work item 15200). @AdrianSosic @AVHopp It might be easier to assess these last two commits separately from the rest:

Make _recommend_continuous and _recommend_discrete accept their respective subspaces instead of the entire SearchSpace (2nd last commit)
Changed the signature of BayesianRecommender.recommend so it is the same as for other recommenders by making the acquisition function a private init=False field (last commit)

Upcoming:

Turn Strategies into Recommender objects under a reasonable name like eg CompositeRecommender's etc

Update docs regarding these changes

I've removed one existing deprecation as it was meddling with the cattrs structuring
I've not introduced any new deprecations. i) Its questionable whether we want to flood the codebase just for the ability to use the old strategy interface and ii) even if we wanted, its reasonable to do so after 2) and not 1)

@AdrianSosic ok what are the issues you're seeing?

@AdrianSosic so I've reverted the hanges related to the sugnature and mvoed them to Recommender. This however requires some small workaround because Strategy does not have the allow attributes but they are referenced ind simulation. Im not sure if its worth fixing this here as simulation is under reconstruction anyway AND strictly speaking the allow attributes cannot be simply set by Strategies because their recommenders could have varying stuff. This would also not be solved in the override-approach discussed. Seems to me simply simulation should not couple to the allow attributes
Ive also removed the abstract recommend method form Recommender.

Ive nut put default values in the protoco... dont you think thats weird?
its also strange to me that this is allowed, now Recommender derives from RecommenderProtocol but doesnt implement the protocol...


Adding a version number to URL to force browser to re-request file

Currently, I use a mod_rewrite rule like this:
RewriteRule ^(.*?)\.v[0-9]+\.js$ /js/$1.js [L,E=VERSIONED_FILE:1]
Header add "Expires" "Mon, 28 Jul 2014 23:30:00 GMT" env=VERSIONED_FILE
Header add "Cache-Control" "max-age=315360000" env=VERSIONED_FILE

So I can request my JavaScript file at /js/myjavascript.js as /js/myjavascript.v15.js which forces clients to re-download a new version if I make any important changes. This is great, but I would love to have an easy way to do this with Minified-on-the-fly requests (something like /min/f=/js/myjavascript.js;v15).
I could add a variable to the query string, but some browsers and proxies do not cache resources that contain a query string.

Just add "&" and a number to the URL to trigger far-future Expires. E.g. /min/f=file.js&1

Boom, awesome. That is exactly what I was hoping for. Thanks!


⚠ Bofrost.de has degraded performance

In 8b03bc4, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 965 ms

Resolved: Bofrost.de performance has improved in 1dbe117.


Correct the imports in examples

The package is published as @lune-climate/lune.

Yeah I can add that to this PR


[BEAM-13285][Playground] Add steps to playgroundPrecommit gradle tasks

The output of this task is the following:

A task that deletes any existing build directory in the playground/frontend directory
A task that runs "buf lint" inside the playground directory

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

I'll merge this for now, since ths PR has passing tests. Let's fix tem in a follow up?


EST?

Since when is EST Egypt Standard Time? Isn't is Eastern Standard Time?

@rcidt feel free to contribute


lang/python: add additional checks

Related: #2180, #2193
A few questions and a comment:

Should line 8 be an assertion? Is python not being installed a blocker?
I realize these doctor checks are all checking for global installations of various packages. How does this conflict with the various virtualenv solutions people are using?
How do you determine where to put intermixed dependencies? For example, should the editor module also check if python is enabled and warn about black?
Finally, I settled on using the format of "couldn't find $executable. $feature will not work". Doom seems to be a little bit inconsistent here, but this format seemed to be most common.

1. Should line 8 be an assertion? Is `python` not being installed a blocker?

It probably should be, yeah.

2. I realize these doctor checks are all checking for global installations of various packages. How does this conflict with the various virtualenv solutions people are using?

I'm afraid there is no simple solution to this problem. We can only check for global installs and rely on heuristics. User's can ignore its warnings if they know better. I'm open to suggestions.

3. How do you determine where to put intermixed dependencies? For example, should the `editor` module also check if `python` is enabled and warn about `black`?

Good question. The provider should do the checks, rather than the consumer. i.e. It should be checked for in the :editor format module, wrapped in (when (featurep! :lang python) ...). I've put it in the python module because :editor format is overdue a rewrite (possibly with the reformatter.el package instead).

4. Finally, I settled on using the format of "couldn't find $executable. $feature will not work". Doom seems to be a little bit inconsistent here, but this format seemed to be most common.

Very true. I have a rewrite of the doctor system in the works to standardize these checks (and make following up on specific warnings/errors easier, through a doom doctor --describe ERRCODE command or similar). In any case, this is just fine for the time being.

Sorry for the late response. This looks good to me. Thanks for your help!


Enable build on macOS

Since all the supposed linux-only functionality is in fact POSIX, it's easy to make this compilable on macOS as well, at least x86_64

Thanks for your pull request. MacOS is not officially supported. In the newest release (V2.4.2) we replaced #ifdef linux by #ifndef _MSC_VER to be more compatible.


Revert "fix: Remove NetworkPolicies created to relax SMCP policies"

Reverts opendatahub-io/odh-model-controller#136
This change opendatahub-io/odh-model-controller#136 together with https://github.com/opendatahub-io/opendatahub-operator/pull/798 break Serverless that expects these NP to be there. So we are reverting both opendatahub-io/odh-model-controller#136 and https://github.com/opendatahub-io/opendatahub-operator/pull/798. In the meantime, we'll work on short-term solution https://issues.redhat.com/browse/RHOAIENG-1955. See https://issues.redhat.com/browse/SRVKS-1189.
For additional context, see Slack threads:

https://redhat-internal.slack.com/archives/C065ARTVA80/p1705573610546289
https://redhat-internal.slack.com/archives/C065ARTVA80/p1705331979411859
https://redhat-internal.slack.com/archives/C067G701YP6/p1705496234916619

/lgtm

/approve


Release to open source: checklist

I'm going to share https://github.com/githubtraining/training-manual with the world. The following are items that we need to take care of to get this repository in shape for the open! @githubtraining/trainers, @beardofedu, @amyschoen, if you're able to help with any of these, that would be very helpful 🙇 (cc @matthewmccullough, @BonnieC)
Before we make this public, we need to complete the following:
Coordination

[x] The repo is visible to the teams below (typically all employees should have read access pre-open-source)

In progress: https://github.com/github/entitlements/pull/10424/

[x] Discuss with @github/legal if there are any licensing or other legal concerns.

In progress: https://github.com/github/open-source-releases/issues/120

[x] Discuss with @github/public-relations if it make sense to do any press around the release.

In progress: https://github.com/github/open-source-releases/issues/120

[x] Discuss with @github/marketing if it makes sense write about this project on the GitHub blog.

In progress: https://github.com/github/open-source-releases/issues/120

Open an issue in github/creative to request a snazzy logo We have been using an image from the Octodex for this org and plan to continue with it

Preparation

[x] It has a name that is easy to remember, gives some idea what the project does, and does not conflict with an existing project or infringe on any trademarks.
[x] It uses consistent code conventions, clear function/method/variable names, and a sensible public API.
[x] The code is clearly commented, documenting intentions and edge cases.
[x] The distribution mechanism is as convenient, standard, and low-overhead as possible (RubyGems, Homebrew, Bower, Maven, NuGet, etc.).
[x] I have opened an issue in the oss-legal-review repo regarding how we use (or do not use) encryption in this repository. Please put a link to that issue in the comments on this issue.

In progress: https://github.com/github/oss-legal-review/issues/382

[x] There are no sensitive materials in the revision history, issues, or pull requests.

If any sensitive content or commit messages are found in commits, consider squashing the revision history.
If we wish to preserve sensitive history or we wish the public repo to have zero non-commit history, rename the private repo and create a new blank slate repo with the intended public name and any commit history intended to be public.

[x] It has a CONTRIBUTING.md based on this template.

In progress: https://github.com/githubtraining/training-manual/pull/207

<EMAIL_ADDRESS>is provided as a maintainer contact (e.g., in the .gemspec email field for Ruby gems).
[x] It has a LICENSE; which one documented at licenses for GitHub open source projects.

In progress: https://github.com/githubtraining/training-manual/pull/205
[x] All dependencies (including transitive) are under compatible open source licenses (License Finder may be useful to do a spot check)
[x] It is a library/will not be shipped as an application (eg desktop, mobile, or server package), or if it is, it is released with user-available license and credits information (desktop or mobile; see legal eagle) or includes license and credits information for a bill of materials (server; see licensed).

[x] It has a CODE_OF_CONDUCT.md; use http://contributor-covenant.org/version/1/4/code-of-conduct.md and fill in<EMAIL_ADDRESS>as the email address.

In progress: https://github.com/githubtraining/training-manual/pull/206

[x] It has a SECURITY.md; use https://github.com/actions/.github/blob/master/SECURITY.md or equivalent for the org it is being released in.

In progress: https://github.com/githubtraining/training-manual/pull/210

README.md

All in progress: https://github.com/githubtraining/training-manual/pull/212
[x] It starts with a one-line description that explains what the project is about, who might be interested in it, what language its written in, and how it might be different from similar projects.
[x] It includes a list of features and limitations.
[x] It states the goals and scope of the project to help set expectations and filter proposed changes down the line.
[x] It includes the current status (e.g., proof of concept, used in production, active development, orphaned, etc.)
[x] It includes a description of the kind of environment required to run the software and instructions for setting it up.
[x] It clearly states the external dependencies and directions for installing them.
[x] It includes a high-level development roadmap or link to open issues/milestones.
[x] It explicitly asks for contributions, if you want them, with a link to CONTRIBUTING.md.
[x] It has a License section that states the license and if any GitHub logos are used, the line When using the GitHub logos, be sure to follow the [GitHub logo guidelines](https://github.com/logos).

Maintenance

[x] At least one Hubber is committed to managing community interactions by triaging and responding to issues, giving feedback and merging pull requests, and releasing new versions. This will be handled by the @githubtraining/programs team as a part of our existing comms duty.

Next steps

[ ] Update the issue in the github/open-source-releases repository
[ ] Make the repository public
[ ] Change the name of the repository to github-training-manual
[ ] Change the owner to github
[ ] Implement redirection solution (create training-manual repository that links via README.md and gh-pages to the new manual?)
[ ] Change the name

🎉 🚢


Documentation: update Quick Install guide

Fix broken link to external etcd configuration guide
Link directly to Kubernetes requirements instead of duplicating that
information in the guide, as it was stale. Linking to a single place with
requirements ensures we do not have duplicate information spread across our
guides that gets out-of-sync.

Signed-off by: Ian Vernon<EMAIL_ADDRESS>

This change is

test-docs-please

Coverage increased (+0.002%) to 44.148% when pulling cd26416e3cbcb4a851f89a863b252368118f73ee on pr/ianvernon/self-managed-quick-install-docs-fixes into 9a9aa413d4b8fde1c1efd14e373f75026383d437 on master.


edit icon

👷 Deploy Preview for adoring-leavitt-e31a11 processing.
🔨 Explore the source changes: 061128bcb806b059843c4bee903c43f50c2ae31b
🔍 Inspect the deploy log: https://app.netlify.com/sites/adoring-leavitt-e31a11/deploys/6223d0771d8bf30007be84ec


Please create a changelog for 5.6.36

Please create a changelog for 5.6.36

Can you create a PR for that?

I will do it


tablet-unstable-v2 support

I'm losing motivation to work on this on my own, so I'm opening the PR, for a bit of feedback and pressure :)
This implements the tablet-unstable-v2 protocol from wayland-protocols for wlroots, and uses it in rootston.
The most notable changes:

wlr_tablet_* has been expanded to contain any information required for tablet-v2
the libinput backend builds the new table objects completly

Edit: Cleaned this part a bit, and clarified what I mean.
Planed for this PR:

~Inert resources/resource destruction~
General cleaning sweep over the changes
~all axis events~
~Clean up serial handling~

Follow up issues:

wayland backend client implementation
(Maybe) give tablet a dedicated cursor/focus
~Use relative movements for Mouse (and Lens?) tools [by default]~
Implement grabs (and the send/notify duality)

Thanks for the initial feedback :)
I just remembered what I was stuck on earlier:
How are serials managed in wlroots? And who has ownership in general? rootston or wlroots?
tablet-v2 has a somewhat ugly situation where we are supposed to send button events for all held buttons on proximity_in, but each of them requires a serial.
Should this be pushed into rootston so the compositor can keep track of serials, or contain it in the implementation (since it's forced), and then store the serials in the wlr_ structs that are exposed?

(Re-establish) pointer fallback semantics (currently tablet support is required for input)

How does this work in practice? Do clients like Xwayland and GTK+ have a proper tablet protocol support?

strings /bin/Xwayland | grep tablet shows nothing. So at least current arch's Xwayland doesn't support it.
gnome-terminal supports it. There's some corner cases that don't work properly, but that's issues on the GTK side of things.
Any other client I should test?

strings /bin/Xwayland | grep tablet shows nothing. So at least current arch's Xwayland doesn't support it.

My Xwayland seems to support it.

s/current/last week's/
ok, current Xwayland supports tablet. Krita "worked", I think there might be a bug with the pressure axis in my code (or libinput backend), I'll investigate that

Did not exhaustively review the code but the approach looks good to me and I tested it with krita, seems to work.

How're we looking here guys

This is a massive PR, so I don't think I'll be able to review it very carefully. Give me time to check the rest of the protocol implementation though. I think we should just check that it works properly after that.
I'm still not happy with tool_tool though.

What about the tool_tool rename?

Can you rebase this? Let's get it merged.

 I think I had a wrong sizeof in there, should be fixed.

 Can you resolve conflicts?

Thanks!

This one was quite the ordeal!
Thanks for the patience and reviews :)


How to run the manhattan data？

Please ask whether the manhattan data in the project MPLight is built based on cityflow,
and whether there is a docker file similar to colight in the project MPLight？
Thank you very much!

Please check this repo

你好，我是宣传部的乔嗣尧，已收到您的来信，我会及时查收并回复。如果您有急事，请联系我：<PHONE_NUMBER>7  或<PHONE_NUMBER>6


deleted every file with cv2 display

deleted the 2 routined of display_cv2 and the conf file that used the cv2 display #68

@ItayHoresh i deleted the files, there weren't any imports for this files in any other files. can you approve?


2548: Split up web feedback at the first level into two smileys again

Short description

The municipalities have been receiving way less feedback since we made some changes there about half a year ago. In this PR, I changed the sidebar in web desktop / the footer in web mobile to show the two smileys instead of the button saying Feedback.
Proposed changes

Instead of showing the FeedbackIcon in the sidebar / footer, this shows the HappySmileyIcon and the SadSmileyIcon
A click on either of those icons opens the feedback overlay with the clicked icon selected
I added a Portal around the sidebar in web desktop to avoid the sidebar poking through when the language selection screen is open

Side effects

If the device is narrower than 408px, the sad smiley jumps to a new row. Do we have a minimum width that we support?

Testing

Check that sending feedback still works
Check that the sidebar isn't hidden behind things it shouldn't be
Check that the sidebar isn't hiding other things that it shouldn't be hiding

Resolved issues

Fixes: #2548

here's how it looks from my device...

Oooooh, good catch, thanks!


Support facebook/dataloader in GraphQL schema

Hello
I was playing around with this plugin a bit. I was wondering if it is possible to include https://github.com/facebook/dataloader in the context for single requests to reduce the amount of database requests due to cached queries.
Thank you.

This would be a great feature. Hasura and PostGraphile implemented this pattern.


BT-771-Lot can -> may

"late-all": "At the discretion of the buyer, all missing tenderer-related documents may be submitted later.",
"late-none": "No documents can be submitted later.",
"late-some": "At the discretion of the buyer, some missing tenderer-related documents may be submitted later.",
change "submissionMethodDetails": "All missing tenderer-related documents can be submitted later." to
"submissionMethodDetails": "At the discretion of the buyer, all missing tenderer-related documents may be submitted later."

@odscjen In the example, use the verbatim label from the authority table (we only fix normative language in our own codelists, etc.).

This is the link that I'm using https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/missing-info-submission

cc @duncandewhurst

The text that was in the example appears to be from an older version of the codelist. I'll update it


crash after LTN tries to find a location that supplies a resource but cant find any

Error Log :
The mod LTN Manager [ALPHA] (0.3.1) caused a non-recoverable error.
Please report this error to the mod author.
Error while running event LtnManager::on_tick (ID 0)
LtnManager/scripts/ltn-data.lua:289: attempt to compare two nil values
stack traceback:
LtnManager/scripts/ltn-data.lua:289: in function <LtnManager/scripts/ltn-data.lua:288>
[C]: in function 'sort'
LtnManager/scripts/ltn-data.lua:288: in function 'callback'
flib/table.lua:196: in function <flib/table.lua:169>
(...tail calls...)
LtnManager/scripts/ltn-data.lua:506: in function 'iterate'
LtnManager/control.lua:157: in function <LtnManager/control.lua:153>

Please follow the bug report template and provide all of that information. It exists for a reason.

Hi, i dont know if i have the same or a different Bug. It look´s a kind of the same error message:

I´m not sure at the moment what caused the problem to happen but i will try to reporduce it and will give you some feadback as soon as i figured it out.

Mh, sorry i failed to reporduce it. :(
When i had the error i just placed some new ghost trains on the rail track to add them to the LTN Network. I did the same again but no error happend the 2nd time.

Step to reproduced:
Simply dismantle a train in one of the train depots if it has already been assigned an active order.

@Hellspawnxxx That error is was also reported by someone else, and while I was also unable to reproduce it, I am reasonably confident that I have fixed it.
@gintsligotnis Please provide me with the save file that your error occured on, as well as you factorio-current.log and in-game username.

Closing due to lack of response from @gintsligotnis.


refactor: resolver methods

Summary by CodeRabbit

New Features

Enhanced the batch processing functionality for better clarity and error handling.
Improved asynchronous call management with a more explicit promise resolution.

Bug Fixes

Streamlined error handling to ensure correct population of results during batch calls.

Tests

Updated test cases to use a structured object format for function calls, improving clarity and flexibility.

Codecov Report
Attention: Patch coverage is 95.23810% with 1 line in your changes missing coverage. Please review.

Project coverage is 99.30%. Comparing base (3011ab5) to head (cc8f381).

Files
Patch %
Lines

batch/accumulate.ts
95.23%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #10   +/-   ##
=======================================
  Coverage   99.29%   99.30%
=======================================
  Files           1        1
  Lines         141      143    +2
  Branches       19       17    -2
=======================================
+ Hits          140      142    +2
  Misses          1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Dox and split

Contains the dox help system and most of the relevant documentation for the genesis command
Also contains tuning of the merge of the ci split pipeline code that was added in PR #108

Please split this PR into two separate changesets - one for adding documentation and the help system, and another for the CI pipeline changes.

Splitting up into multiple PRs


Create a new molecular_type field in the molecular inventory

The molecular_type field should replace all the followings: is_protein, is_lipid, is_ion, is_solvant.
Default value for molecular_type could be unknown. Possible values could be protein, ion, solvant or lipid.

I re-opened this issue.
@KarinDuong could you make a PR an update tests?

Can we also close this issue ?


Two parsing changes to handle input from Azure AD

Hi again,
So, I've gotten around to hooking our system up to Azure AD, and it turns out they have two peculiarities which the other providers don't have.
First: their metadata file has a byte-order mark, which OpenSaml will not accept.
Second: their LogoutResponse is deflated, so it needs to be inflated before we can validate it.
This pull request handles these peculiarities.
If you have any questions or suggestions, I'd be happy to hear them.
Kind regards

Thanks for your comments! I've got commits that address them ready, but I currently only have access to my local environment. Tomorrow, I'll check them on a non-localhost before I push them.
Kind regards

Good comments about the methods - I think some refactoring is clearly needed here. But not in the context of this PR. Also, instinctively I'd say that if we need to start mocking servlet requests maybe it means that the whole SamlClient class needs to be split into easier to test parts. But that's a discussion for the future 😄

That sounds fair. Thank you for making time to review this!


Compression: support FOR & replace Delta with DeltaFOR

What problem does this PR solve?
Issue Number: ref #8982
Problem Summary:
What is changed and how it works?
FOR: https://dbms-arch.fandom.com/wiki/Frame_of_Reference_(Compression_Scheme)
Delta is not a compression algorithm, but Delta + FOR be.
Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/hold

/unhold


Instructions for section "RBAC - Shared from another tenant" don't work

I copied the PowerShell instructions from the section called "RBAC - Shared from another tenant" and ran them locally. All the steps succeed up until the last step where it tries to create the VM. The VM creation step tries to pull the image from Tenant1 with the username that is only valid in Tenant2. How can I specify that I want to pull the image from the gallery with one account but build the VM with the other account?
Both accounts are successfully signed into the Powershell session. This is the full error if it helps but I replaced my username and subscriptions:
ErrorCode: LinkedAuthorizationFailed
ErrorMessage: The client 'username2' with object id 'b4df41b4-37b9-4b1b-bea6-f7be8f933b8e' has permission to perform action 'Microsoft.Compute/virtualMachines/write' on scope 'subscription2 where I want to create the VM'; however, it does not have permission to perform action 'read' on the linked scope(s) 'gallery in subscription1 where the image is stored' or the linked scope(s) are invalid.
ErrorTarget:
StatusCode: 403
ReasonPhrase: Forbidden
OperationID : 693ce883-7e7f-4b91-beba-37e7812612a8

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

ID: c95cf419-74ae-f6d1-5c3e-01f988fdd9c4
Version Independent ID: 6dfe7480-2c45-2be9-3f3d-8ee97f62cc62
Content: Create a VM from a generalized image in a gallery - Azure Virtual Machines
Content Source: articles/virtual-machines/vm-generalized-image-version.md
Service: virtual-machines
Sub-service: gallery
GitHub Login: @sandeepraichura
Microsoft Alias: saraic

@cesar-younes
Thanks for your feedback! We will investigate and update as appropriate.

@cesar-younes
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

@sandeepraichura please review it.

Thanks for your contribution to our documentation
We are moving to a new user feedback system. As part of that effort, we are creating a content request in our backlog to address this gap and are closing this GitHub issue. The updated content will be published shortly.

Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


OSD-22507: POC first pass at new rotate command (draft)

First pass at OSD-22507. Attempting to consolidate previous bash, osdctl, additional SOP steps to into a single command/context to help users rotate Osd Admin user(s)' IAM creds and related secrets.

Big thanks @iamkirkbater for the review and comments. Most recent commit should contain these suggestions as well as support -o yaml/json to stdout (logs to stderr) for the 'describe' specific commands.

/test lint

/test lint


Merge Result Wrapper into issue-24/master

So I can stop pulling these changes into every issue-24 branch :)

I've added an additional update to the wrapper here based on some changes I've found useful while re-implementing leaky subscription fixes.

Added javadocs and updated names!
Writing docs for these methods is tricky :sweat_smile: Should we can nested streams matryoshkas? :P

Thanks for the PR!

Really excited to see these design issues and potentially bugs resolved. Thanks for your patience iterating to set up a good precedent!


Check if this audio is already added to RetroStudio.

[X] The audio is not already in game.

Is this for the main-menu playlist?

[ ] Add to main-menu playlist.

Is this song from an old Roblox era or a sound effect?

[X] This song is from old Roblox or is a sound effect.

A link to the audio on Roblox
https://www.roblox.com/library/164322288/Sample2
A link to the audio file to download.
https://cdn.discordapp.com/attachments/1031048192617365585/1146280408590340096/164322288.ogg?ex=65a744d2&is=6594cfd2&hm=13ffa36a2e205dc9773111b2b3f71a09a98ccf446214898de49755d8b8ff9cb9&
Notes
No response

Sample3 is completely banned off Roblox.


CAMEL-19842: fix not creating/refreshing seda queues

Removing the cached queue references caused a regression in camel-zookeeper-master. This brings back the cached references (reverts: d66469d6ac7243f0ae790c41a500965b885d3180)
Avoid keeping cached stalled references (ref: CAMEL-19815)

@oscerd yeah, I am on top of that one.

Obs.: we need to backport this to 4.0.1 was well. The same test is also failing there (for the same reasons).


eas build fails because build file cannot be found: Firebase config files saved in expo secrets not being transferred correctly

Build/Submit details page URL
https://expo.dev/accounts/tmi/projects/AeonPass-Scanner/builds/a861555b-82bb-4617-bed1-b568e8dc44b7
Summary
I want to make sure that I do not have to check my google-services.json & GoogleService-Info.plist files into my git repo. I uploaded each as a secret file in my expo project. I then followed the docs doing the following ...
expo: {
    owner: "tmi",
    name: "AeonPass-Scanner",
    slug: "AeonPass-Scanner",
    version: "1.0.0",
    orientation: "portrait",
    icon: "./src/assets/icon.png",
    userInterfaceStyle: "light",
    splash: {
      image: "./src/assets/splash.png",
      resizeMode: "cover",
      backgroundColor: "#ffffff",
    },
    assetBundlePatterns: ["**/*"],
    jsEngine: "hermes",
    ios: {
      supportsTablet: true,
      bundleIdentifier: "com.tmitboules.AeonPassScanner",
      jsEngine: "hermes",
      googleServicesFile:
        process.env.GOOGLE_SERVICE_INFO_PLIST || "./GoogleService-Info.plist",
    },
    android: {
      googleServicesFile:
        process.env.GOOGLE_SERVICES_JSON || "./google-services.json",
      adaptiveIcon: {
        foregroundImage: "./src/assets/adaptive-icon.png",
        backgroundColor: "#ffffff",
      },
      package: "com.tmitboules.AeonPassScanner",
    },
    web: {
      favicon: "./assets/favicon.png",
    },
    extra: {
      eas: {
        projectId: "5824acd0-ca7a-4eff-9050-9b3836458c87",
      },
    },
    runtimeVersion: "exposdk:48.0.0",
    updates: {
      url: "https://u.expo.dev/5824acd0-ca7a-4eff-9050-9b3836458c87",
    },
    plugins: [
      "@react-native-firebase/app",
      "@react-native-firebase/auth",
      [
        "expo-build-properties",
        {
          ios: {
            useFrameworks: "static",
          },
        },
      ],
    ],
  },

When I run locally this works just fine obviously. But when it builds, it can't find the file, although I see when it reads my config, it correctly links each env variable to the file in my expo secrets.
When building I get the following error
error: Build input file cannot be found: '/Users/expo/workingdir/build/ios/AeonPassScanner/GoogleService-Info.plist'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it? (in target 'AeonPassScanner' from project 'AeonPassScanner')
Managed or bare?
Bare I guess, although I do not manage any native code. Just using plugins
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.2.1
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
Yarn: 1.22.19 - ~/.yarn/bin/yarn
npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK:
API Levels: 30, 31, 33
Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0, 33.0.0
System Images: android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7784292
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
npmPackages:
expo: ~48.0.15 => 48.0.15
react: 18.2.0 => 18.2.0
react-native: 0.71.7 => 0.71.7
npmGlobalPackages:
eas-cli: 3.10.0
expo-cli: 6.3.2
Expo Workflow: bare
templates-MacBook-Pro:AeonPass-Scanner tony.boules$ expo doctor

┌─────────────────────────────────────────────────────────────────────────┐
│                                                                         │
│   There is a new version of expo-cli available (6.3.7).                 │
│   You are currently using expo-cli 6.3.2                                │
│   Install expo-cli globally using the package manager of your choice;   │
│   for example: npm install -g expo-cli to get the latest version      │
│                                                                         │
└─────────────────────────────────────────────────────────────────────────┘
🎉 Didn't find any issues with the project!
Error output
error: Build input file cannot be found: '/Users/expo/workingdir/build/ios/AeonPassScanner/GoogleService-Info.plist'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it? (in target 'AeonPassScanner' from project 'AeonPassScanner')
Reproducible demo or steps to reproduce from a blank project
install deps
package json
{
  "name": "aeonpass-scanner",
  "version": "1.0.0",
  "scripts": {

    "start": "expo start --dev-client",
    "android": "expo run:android",
    "ios": "expo run:ios",
    "web": "expo start --web",
    "update_test": "eas update --branch test"
  },
  "dependencies": {
    "@react-native-firebase/app": "^17.4.3",
    "@react-native-firebase/auth": "^17.4.3",
    "@react-navigation/native": "^6.1.6",
    "@react-navigation/native-stack": "^6.9.12",
    "expo": "~48.0.15",
    "expo-build-properties": "~0.6.0",
    "expo-dev-client": "~2.2.1",
    "expo-font": "~11.1.1",
    "expo-splash-screen": "~0.18.2",
    "expo-status-bar": "~1.4.4",
    "expo-updates": "~0.16.4",
    "react": "18.2.0",
    "react-native": "0.71.7",
    "react-native-safe-area-context": "4.5.0",
    "react-native-screens": "~3.20.0"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "@types/react": "~18.0.14",
    "@types/react-native": "^0.71.6",
    "babel-plugin-inline-dotenv": "^1.7.0",
    "typescript": "^4.9.4"
  },
  "private": true
}

configure app
module.exports = {
  expo: {
    owner: "company",
    name: "app",
    slug: "app",
    version: "1.0.0",
    orientation: "portrait",
    icon: "./src/assets/icon.png",
    userInterfaceStyle: "light",
    splash: {
      image: "./src/assets/splash.png",
      resizeMode: "cover",
      backgroundColor: "#ffffff",
    },
    assetBundlePatterns: ["**/*"],
    jsEngine: "hermes",
    ios: {
      supportsTablet: true,
      bundleIdentifier: "com.example.app",
      jsEngine: "hermes",
      googleServicesFile:
        process.env.GOOGLE_SERVICE_INFO_PLIST || "./GoogleService-Info.plist",
    },
    android: {
      googleServicesFile:
        process.env.GOOGLE_SERVICES_JSON || "./google-services.json",
      adaptiveIcon: {
        foregroundImage: "./src/assets/adaptive-icon.png",
        backgroundColor: "#ffffff",
      },
      package: "com.example.app",
    },
    web: {
      favicon: "./assets/favicon.png",
    },
    extra: {
      eas: {
        projectId: "5824acd0-ca7a-4eff-9050-9b3836458c87",
      },
    },
    runtimeVersion: "exposdk:48.0.0",
    updates: {
      url: "https://u.expo.dev/5824acd0-ca7a-4eff-9050-9b3836458c87",
    },
    plugins: [
      "@react-native-firebase/app",
      "@react-native-firebase/auth",
      [
        "expo-build-properties",
        {
          ios: {
            useFrameworks: "static",
          },
        },
      ],
    ],
  },
};

generate android and ios config files from firebase
put them at the root of the project
save files as secrets in expo
configure eas build and run a build

If you have bare project you need to follow instructions for react native apps not expo for third party libraries. Stuff like plugins or most of the values in app.json only take effect when you run expo prebuild, but EAS Build does not run it for bare projects. So in your case, secrets get uploaded, app.config.js resolves the path correctly, but native code is not aware of those files, because prebuild was not run.
If you don't need it to be a bare project just delete android and ios directories(or add it to gitgnore if you want to keep using it for local native development)
If you need to stay on bare you need to configure your native xcode/android project to use  files from secrets, or write post install hooks to copy secrets into appropriate locations in android/ios projects.


all-in-one crossplane creation failed

https://github.com/cloud-pak-gitops/instana-gitops/tree/main/config/argocd-apps/all-in-one

not a provlem now, as we need to install crossplane+provider first and then install instana.


from_db_value() missing 1 required positional argument: 'context'

Describe the problem
Im using DB backend(mysql).
I see this error in the django admin in the constance section.
TypeError at /admin/constance/config/
from_db_value() missing 1 required positional argument: 'context'

Steps to reproduce
First I see all the constants in the admin with the default values setted, I see in the DB and there is no data in the constance_config table. Until here is all normal I think that is the default behivor.
Second I press save without modify any constant and all the constants are saved in the DB, after this action I can't see the admin again and this error is raised:
TypeError at /admin/constance/config/
from_db_value() missing 1 required positional argument: 'context'
System configuration

Django version: 3.1.4
Python version: 3.8
Django-Constance version: 2.8.0

Confirming the same issue for DB backend with PostgreSQL 13.2.

Actually, the problem only appears with django-picklefield versions prior to 2.0 after which the "context" argument was removed from the from_db_value field method. This ensures compatibility with Django 2.0 and upper versions.
So the solution is to upgrade django-picklefield 2.0 and higher.

Actually, the problem only appears with django-picklefield versions prior to 2.0 after which the "context" argument was removed from the from_db_value field method. This ensures compatibility with Django 2.0 and upper versions.
So the solution is to upgrade django-picklefield 2.0 and higher.

totally, I upgrade django-picklefield to the last version and it works! thanks!


chore: bump kcl-openapi version to v0.4.2 and add it into kusion release bundles.

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

chore: bump kcl-openapi version to v0.4.2 and add it into kusion release bundles.

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[x] Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 73.664%

Files with Coverage Reduction
New Missed Lines
%

pkg/engine/operation/parser/parser.go
3
75.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
4509

Relevant Lines:
6121

💛  - Coveralls


fix necessary panic if no content in response;

If a resource claim itself JSON but actually contain zero length buffer in the body, httpie-go will panic, which should be unnecessary.

Thanks for the PR! This is a bug in the formatter.
I have investigated this issue, and found that there are other cases that would cause a panic, besides the case that you pointed out. Since fixing this problem requires tweaking a complicated part of the formatter, can I fix it on my hands?

Sure. Thanks for fixing it properly.


open editors can't rename file name

VSCode Version:1.81.1
OS Version:win 10

Steps to Reproduce:
1.Open a file in any place, such as a.txt on desktop
2.and then this file will appear in the file list of the "open editors"
3.When you click the right button on the file, there is no function to rename the file.

Does this issue occur when all extensions are disabled?: Yes

This can be done in the explorer.
In the open editors view by designe we decided not to allow this.
We could consider opneing the open editros view to extensions so each extension can contribute actions here, but I believe there is already an issue for this. Thus closing this one as designed.
@kieferrm just fyi I own the explorer and open editors so assign issues like this to me in the future - thanks a lot!


Feature Request: Add OTP for Email in Auth

Is your feature request related to a problem? Please describe.
Currently, for Auth you only allow an OTP code (6 digit number) to be sent by SMS. However, there is no way to send this code to a user's email to facilitate a login. This is not ideal because, for various reasons, virtually all auth systems now, will also allow for OTP verification and login with a code that can also be sent to an email. In fact, generally the user is given a choice to send the OTP to email or phone.
Describe the solution you'd like
While it's not necessary to offer a choice per above, there should at least be an option to send an OTP code to an email. I imagine the code is exactly the same as is used for an SMS. It's just that the code is sent by email and not SMS. So I don't see that this will entail alot of changes, though admittingly I have not looked at Auth code at all in NHost.
Describe alternatives you've considered
Nhost comes with a Magic Link, but magic links are not a great solution particularly given the reluctance nowadays to not want to click on any link. Just sending the Magic Link code in the email, instead of the link is a terrible UI, because the code is unintelligible to the user and so virtually impossible to remember. This means that you would have to cut/paste the code into the website, which is a bad UI and also in certain instances not possible. One of the benefits of OTP codes, in general,  is precisely that they obviate these UI issues, as most people can easily remember a 6 digit number and just type it in immediately.
Additional context
OTP codes are commonplace now in virtually every single Auth application nowadays (see Shopify's new Customer Accounts API, which just sends a code). At the same time, Magic Links actually have never really taken off, and I doubt they ever will, given concerns of clicking on links. Offering the OTP code to an email also, in addition to the SMS, will bring the Auth library up to speed with other providers.

Thanks for the detailed feature request, we will look into it when planning future work.

Curious if you guys plan on implementing this?

Yes, this is something we will certainly want to add.

there is no way we want to tether our application to a bunch of links and redirects

Remember you can already use codes (even though longer). I know you prefer 6-digits codes but as a temporary solution it might be easier than using clerk as migrating from clerk might be difficult.
In any case, if what you want is security and convenience nothing beats weabuthn/keypass so you might want to look into that instead.

This:
https://github.com/nhost/nhost/discussions/2642#discussioncomment-9041323
So basically what you are describing can already be implemented by tweaking the email template. The difference between your proposal and what we are providing already is that you want a 6 digits code (or similar) and what we offer is a more difficult to guess uuid.

Yes, the expectation in this case would be to copy & paste.

So we've done a ton of testing on various email clients, and firewall/anti-virus and have consistently run into problems with email clients invalidating links, even when you use your own app to do a redirect. Ultimately, it requires constant tweaking of code to battle these clients and provide a good UX.
My suggestion, which would be simple and completely backwards compatible, is to simply replace the uuidv4() which you use everywhere for generating the ticket code to a different code which just generates a random 6 digit number. See the example below. By doing it this way, nothing will break for anyone still using links because there is still a code. At the same time, anyone who wants to move away from links, and provide an OTP-like form can easily do so by grabbing the digits and creating the OTP form. Incidentally, if you do it this way, you are in good company, as this is exactly how Cloudflare Pages now does it's Access for dev pages. They generate a link with a 6-digit code as the code, so you can use the link (presumably for backwards compatibility), but actually their frontend now has a form, where you type in the 6-digit code.
Example
https://github.com/nhost/hasura-auth/blob/main/src/utils/user/email-verification.ts
line 117
const ticket = `verifyEmail:${uuidv4()}`;
Change this to:
import { generateRandomString, alphabet } from "oslo/crypto"; //obviously you don't have to use this library and you can just create your own way to generate random digits
const code = generateRandomString(6, alphabet("0-9"));
const ticket = `verifyEmail:${code}`;

There are a few places where you'd have to implement this fix, https://github.com/nhost/hasura-auth/blob/155357345a10b785c69e19cb5522818ed6cd56c5/src/routes/user/email/send-verification-email.ts
line 51 and https://github.com/nhost/hasura-auth/blob/155357345a10b785c69e19cb5522818ed6cd56c5/src/routes/user/password-reset.ts#L44
Line 44

Hi,
thanks for the suggestion. Unfortunately the solution isn't as simple. Two reasons:

Users may want to retain the more secure option of using a uuid, so this should be configurable at the very least, most likely it will need to be a new endpoint due to the next point.
We need to asses its security considerations/impact as we are vastly reducing the robustness against brute-force attacks/collissions. For instance, at the very least it'd require a new parameter to the verify endpoint to request the email, which we don't today and would be a breaking change.

Regards

Thanks for the quick reply. My counterpoints are below.

A properly generated random 6 digit number is no less secure than a UUID for the purposes of email verification. Of course, in other use cases a UUID is more secure, but not for this use case. If it was how is it that every single auth company uses this nowadays for verification instead of UUID's, including companies like Cloudflare who entire business revolves around security. The new ID.me from the US government for verifying identity, probably the most targeted service in the world, is also entirely based around digits vs UUIDs, though they require 8 digit code. You also use OTP for SMS. Fact is that if you use a good crypto library and hash the code in the database (that's what the oslo package does, by the way), have an expiration, there is no security difference whatsoever between a UUID and 6 digit code for this particular use case. I don't see why anyone would ever prefer a UUID over a 6-digit (or 8 digit) code.

There is zero security impact using a random 6 or 8 digit code vs UUID if done properly, and it in no way reduces the robustness of brute force. I don't even understand this point actually, as the protection against brute force attacks would follow the same exact pattern as you currently have. Is your OTP with SMS subject vastly reducing the robustness against brute force and undermining your security? If you can send OTP via SMS, you can send it via email. There is no difference. Probably you can just copy your code for OTP with SMS and instead of sending via SMS, send via email and it would be fine. But I haven't looked at your OTP for SMS code yet, to be sure this is possible.

At the end of the day, using links with UUID is a thing of the past and any auth system that uses it will be abandoned in due time (I give it about a year). Everybody is moving away from it. Users are increasingly less likely to click on links for fear of phishing attacks, and increasingly filters block emails with them or send them to spam. Just yesterday, I had 2 phishing attacks myself with fake magic links from Asana.

Given #3 above, it is really crucial for Nhost Auth to make the change and move away from clicking links. If it means, you need to create another enpoint, of course, that's a perfectly viable solution, but I think the implementation is much easier than that, especially since you already have OTP with SMS.

if done properly

That's the thing, there are a lot of considerations so it isn't as simple as just replacing a uuid with a 6 digit number. Nobody is arguing against the proposal, just saying it isn't as simple as replacing one type with another

OK, thanks. BTW, I did look at the code quickly. You have a function getNewOneTimePasswordData in otp.ts that generates the OTP. Upon quick glance it seems perfectly fine and follows all the best practices. You then use it in sms.ts to send the sms. Why couldn't you just duplicate the sms.ts file and instead of twilioClient.messages.create, just have a postmark message sent or some other email provider? How is sending this by SMS any different than email? it's just a different API for sending, but the underlying OTP functionality is the same.

From my previous message:

For instance, at the very least it'd require a new parameter to the verify endpoint to request the email, which we don't today and would be a breaking change

We basically need a new endpoint as this will need to work more like the otp endpoint and less like the verify ticket endpoint

Thanks. Yeah, after reviewing the code a bit more, I see that now that new endpoint is needed.

Hey guys, do you have any updates on this?
I'm having to figure out a way around sending a 6-digit code to the user.
I would love to just add a copy to the clipboard button to the body of the email, but there is no way to guarantee that javascript will work.

Not yet, if nothing major happens and if our priorities don't change we may be able so schedule this for September.

This was certainly delayed "a bit" but work on this is quite far ahead and should be released before end of the month.

This is now released.
https://docs.nhost.io/guides/auth/sign-in-otp


added some notes related to building on mac os x.

A few questions on the docs branch:

There are a bunch of *.md files under docs but they don't seem to be included in the default page when you run jekyll serve --watch. What I see is the following:

![screen shot 2015-10-29 at 9 57 20 am]
(https://cloud.githubusercontent.com/assets/146453/10825860/1abd83d4-7e24-11e5-9afc-792f8bc06bb1.png)
Should the default page provide a list of contents of something that includes these .md files?

+1.

On Windows, it works fine.

Here is what I'm seeing under my local gearpump repo
Output is:
$ jekyll serve --watch
Configuration file: none
            Source: /Users/kamkasravi/gearpump
       Destination: /Users/kamkasravi/gearpump/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
     Build Warning: Layout 'global' requested in docs/basic-concepts.md does not exist.
     Build Warning: Layout 'global' requested in docs/commandline.md does not exist.
     Build Warning: Layout 'global' requested in docs/deployment-configuration.md does not exist.
     Build Warning: Layout 'global' requested in docs/deployment-ha.md does not exist.
     Build Warning: Layout 'global' requested in docs/deployment-local.md does not exist.
     Build Warning: Layout 'global' requested in docs/deployment-security.md does not exist.
     Build Warning: Layout 'global' requested in docs/deployment-standalone.md does not exist.
     Build Warning: Layout 'global' requested in docs/dev-custom-serializer.md does not exist.
     Build Warning: Layout 'global' requested in docs/dev-ide-setup.md does not exist.
     Build Warning: Layout 'global' requested in docs/dev-non-streaming-example.md does not exist.
     Build Warning: Layout 'global' requested in docs/dev-rest-api.md does not exist.
     Build Warning: Layout 'global' requested in docs/dev-write-1st-app.md does not exist.
     Build Warning: Layout 'global' requested in docs/faq.md does not exist.
     Build Warning: Layout 'global' requested in docs/features.md does not exist.
     Build Warning: Layout 'global' requested in docs/gearpump-internals.md does not exist.
     Build Warning: Layout 'global' requested in docs/get-gearpump-distribution.md does not exist.
     Build Warning: Layout 'global' requested in docs/hardware-requirement.md does not exist.
     Build Warning: Layout 'global' requested in docs/index.md does not exist.
     Build Warning: Layout 'global' requested in docs/maven-setting.md does not exist.
     Build Warning: Layout 'global' requested in docs/performance-report.md does not exist.
     Build Warning: Layout 'global' requested in docs/submit-your-1st-application.md does not exist.
     Build Warning: Layout 'global' requested in docs/usecases.md does not exist.
                    done in 76.496 seconds.
 Auto-regeneration: enabled for '/Users/kamkasravi/gearpump'
Configuration file: none
    Server address: http://<IP_ADDRESS>:4000/
  Server running... press ctrl-c to stop.

Browser shows:

If i select docs subdirectory in the browser I see

It looks like similar pages are shown under gearpump and gearpump.github.io (expected) - although under gearpump the default page doesn't render correctly yet. My understanding from slack is that gearpump should contain most of the documentation from gearpump.github.io and gearpump.github.io should contain more general information, blogs, publications, release history, etc?
Additional question: Should the doc builds be automated in travis? Is there a requirement/expectation that we should autogenerate a build under gearpump.github.io when we release/publish under gearpump?

@kkasravi

You shall run jekyll serve --watch under docs directory instead of root directory of gearpump.
Your understanding about gearpump.io and gearpump doc is correct. For gearpump.io, I have no strong idea about how to layout the content. So, please feel free to modify the structure as you want.
We can have it inside Travis. Though, I am a little doubt the purpose of it.

@kkasravi try cd docs; jekyll build. It also seems we need remove directory doc.


AVFilterLink.frame_rate removed since 7.1

See https://github.com/FFmpeg/FFmpeg/blob/n7.1/libavfilter/avfilter.h#L557C8-L557C20
../../.version-fox/temp/1729094400-53635/golang/packages/pkg/mod/github.com/asticode/go-astiav@v0.23.0/filter_link.go:32:30: l.c.frame_rate undefined (type *_Ctype_AVFilterLink has no field or method frame_rate)
See history: https://github.com/FFmpeg/FFmpeg/commits/n7.1/libavfilter/avfilter.h , it has more changes.

FYI I've made the necessary (breaking) changes so that go-astiav is compatible both with n7.0 and n7.1 👍  It's available with version v0.24.0. Can you confirm this fixes your problem?

Great, I'll close the issue for now, but feel free to reopen it in case of problems 👍


Setup v1 of site that has pages from test WordPress instance and new layouts using design system components

Homepage should use feature card
All other pages should use statewide and site header and footers

Initial versions of these pages have been created using a new layout. Dependencies are installed to use design system components.


misc clean up and fixes

@shiqin-liu at some point in your transition to the new Docker repo, the FROM command was changed from continuumio/miniconda3 to my old personal repo. If we're transferring the image from a personal account to an org account, we don't want it to depend on that old personal account. This PR changes the FROM back to its old value, corrects the line endings (which seem to have been saved as Windows-style), and performs a few other misc clean-ups. cc @carlhiggs.

In d6ebca0 I pinned the key dependency versions in requirements.txt to the minor versions that we had in the Docker image at the start of this year. Version pinning will allow a consistent environment even if the image needs to be rebuilt for some reason.

@shiqin-liu at some point in your transition to the new Docker repo, the FROM command was changed from continuumio/miniconda3 to my old personal repo. If we're transferring the image from a personal account to an org account, we don't want it to depend on that old personal account. This PR changes the FROM back to its old value, corrects the line endings (which seem to have been saved as Windows-style), and performs a few other misc clean-ups. cc @carlhiggs.

Thanks Geoff! I was experiencing some versioning issues at the beginning when rebuilding the image, so I tried with the personal repo and see if I can get the correct dependency... Thanks for correcting that and the requirements.txt.

I just pushed all the images/tags to the team Docker Hub. So now it is exactly the same as the old personal account. The command looked like this:
docker pull gboeing/global-indicators:latest | docker tag gboeing/global-indicators:latest globalhealthyliveablecities/global-indicators:latest | docker push globalhealthyliveablecities/global-indicators:latest
docker pull gboeing/global-indicators:20201103 | docker tag gboeing/global-indicators:20201103 globalhealthyliveablecities/global-indicators:20201103 | docker push globalhealthyliveablecities/global-indicators:20201103
docker pull gboeing/global-indicators:20200612 | docker tag gboeing/global-indicators:20200612 globalhealthyliveablecities/global-indicators:20200612 | docker push globalhealthyliveablecities/global-indicators:20200612
docker pull gboeing/global-indicators:20200123 | docker tag gboeing/global-indicators:20200123 globalhealthyliveablecities/global-indicators:20200123 | docker push globalhealthyliveablecities/global-indicators:20200123
docker pull gboeing/global-indicators:20200318 | docker tag gboeing/global-indicators:20200318 globalhealthyliveablecities/global-indicators:20200318 | docker push globalhealthyliveablecities/global-indicators:20200318

@shiqin-liu ok, so now the new team account should be an exact replica of the images on the old personal account. When this PR is merged, I will delete the old personal repository. First, can you docker pull globalhealthyliveablecities/global-indicators:latest, run the indicators, and make sure we're getting the same results as before? Once you've confirmed that the image gives us reproducible analytics, we can merge.

I just finished running the indicators (my computer crash in the middle during the first run, so it took longer than expected), but all good now. I can confirm that the resulting indicators are exactly the same as before. This should be good to merge

Hi @shiqin-liu and @gboeing , I just received a warning for a security vulnerability possibly related to this code update (Pillow is set to be 8.0.*, but there's a vulnerability so it should be 8.1.1 apparently).
I just lodged an issue here https://github.com/global-healthy-liveable-cities/global-indicators/issues/116 , but it only occured to me after the fact to '@' you both (so wasn't sure if you'd get the message in the edited version), and that I could respond here.
So responding here just in case!  I've drafted a fix, but just double checking that you are okay for me to push it up to Github/DockerHub.

And apologies --- i just realised I made these changes directly to 'main' instead of the new branch i created... That wasn't my intention, but they have been pushed up now.  I'll leave things until I expect you are both back on board tomorrow!


Enum Field Usage for linking Main / SubPage

Description:
If the Records of a SubPage and Main Page are linked via a Enum Field, the System does not correctly populate the values in the SubPage and the Client also does not show the Enum Values, if a Tablerelation was defined.

ALProject10.zip
I have attached a Sample Project.
Versions:

AL Langauge: 3.0.102444
Business Central:14.0.28823

Have you tried the setting PopulateAllFields?

Even, if it should not be necessary to set PopulateAllFields - I have tried it with PopulateAllFields = true, but the Behaviour is the same - the Field MyField1 in the SubPage has no Value and in the DropDown-Box no Enum Values are shown.

This is a serious bug that makes enums not able to replace optionstrings. I am experiencing this same behavior in the spring release. This I believe is also related to a bug with enums and GetFilter and Evaluate.
This also does not work if you do page variables and record setranges like below. There is no filter set on the opened page.
tableA.SetRange("Enum Field 1", "EnumValue1");
listPageA.SetTableView(TableA);
listPageA.Run();

Please, move this bug higher on the queue, because it is already known many months and not solved. We cannot use ENUM till this is solved, because any page using enums is not behaving as option regarding auto-filling the values based on the filters and this is BIG BLOCKING BUG to adopt enums!
If you want example of the difference, I can send you simple app I made to test that.

Fixed in the 2019 Wave 2 release and the upcoming CU of the Wave 1 release


lapack/testlapack: rewrite and extend test for Dgecon

Now that we understand that a mismatch between the exact and estimated condition number is normal, the logging of the mismatch can be removed.
In general in lapack I prefer randomized tests.
I don't know what I was thinking when I wrote the Dpbcon test.

Please take a look.

Now that we understand that a mismatch between the exact and estimated condition number is normal, the logging of the mismatch can be removed.

Is there a reference for this?


double free issue about notification

Hi ,
please have a look.
in function np2srv_ntf_clb end, it will free ntf,
but, in np2srv_ntf_send, if call op_filter_get_tree_from_data failed, it would free ntf also.
in this case, the ntf would be freed twice. it would case crash.

Codecov Report

Merging #209 into devel-server will increase coverage by <.01%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           devel-server     #209      +/-   ##
================================================
+ Coverage         41.07%   41.08%   +<.01%
================================================
  Files                25       25
  Lines              6276     6275       -1
  Branches           1248     1248
================================================
  Hits               2578     2578
+ Misses             3201     3200       -1
  Partials            497      497

Impacted Files
Coverage Δ

server/op_notifications.c
50.66% <ø> (+0.16%)
:arrow_up:

Continue to review full report at Codecov.

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


[Action] SLAP, Stanford Student Org, Protests at Palantir

https://slate.com/technology/2019/08/stanford-tech-students-backlash-google-facebook-palantir.html
@organizejs What do you think? We included a SLAP action in the past but they're not technically tech workers.

maybe we should include it and expand the definition of tech workers to include the pipeline into tech workers (so ppl in school + bootcamps).


[KARAF-6183] Fix override for classified artifacts.

We take now the pattern from override.properties, which
matches best (i.e. has the biggest length), not the last one

:+1:


erorr on 0.31

error on 0.31

getCurrentActivity() or reactContext.getCurrentActivity()
all error.

yes, I may face the same problem, I am 0.31,too
Usage says, add this --> new OrientationPackage()
but, the compiler says:
错误: 无法将类 OrientationPackage中的构造器 OrientationPackage应用
到给定类型;
new OrientationPackage()
^
需要: Activity
找到: 没有参数
原因: 实际参数列表和形式参数列表长度不同
1 个错误
:app:compileDebugJavaWithJavac FAILED

I have same issue with react 0.31. Package require new OrientationPackage(Activity) on MainApplication.java but mentioned add without Activity instance as follow:
@Override
protected List getPackages() {
return Arrays.asList(
new MainReactPackage(),
new OrientationPackage()      <------- Add this
);
}
what is the solution? Please help me out.

https://github.com/yamill/react-native-orientation/blob/master/android/src/main/java/com/github/yamill/orientation/OrientationModule.java
public OrientationModule(ReactApplicationContext reactContext) {
super(reactContext);
Activity activity=reactContext.getCurrentActivity();
}

Not able to find method getCurrentActivity()

Hey, someone resolved this problem ? I'm on it too, I would handle this fast

Hey, I resolved it.
you can npm remove react-native-orientation --save
then download the latest source from github.com and unzip into your
node_modules
after that, react-native link react-native-orientation, then it will
automatically rewrite setting.gradle and bundle.gradle
last, update MainApplication.java and MainActivity.java, then you can use
it in your js files
2016-08-26 21:27 GMT+08:00 Pierre Monge<EMAIL_ADDRESS>
Hey, someone resolved this problem ? I'm on it too, I would handle this
fast
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/yamill/react-native-orientation/issues/96#issuecomment-242734877,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANG18JW5UhVUmYZc3ggTh6RSpoose6pks5qjum3gaJpZM4JtOsv
.

--
Alex Xiong
Mobile: +86<PHONE_NUMBER>2

Hey, I resolved it too :)
Npm package was not updated with github ! 👍

greetings!
2016-08-26 22:35 GMT+08:00 Pierre Monge<EMAIL_ADDRESS>
Hey, I resolved it too :)
Npm package was not updated with github ! 👍
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/yamill/react-native-orientation/issues/96#issuecomment-242752866,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANG1y4OY6_9wbf_o2k5mOhjkuDO86Ivks5qjvnIgaJpZM4JtOsv
.

--
Alex Xiong
Mobile: +86<PHONE_NUMBER>2

@yamill could you update npm version to stable master?

@xiongzhend Is your solution the same as changing the apps package.json to point to github?
"react-native-orientation": "git+https://github.com/yamill/react-native-orientation",
I think this should be the same.  However it is still not working for me on Android.
I will try your solution to download the latest source from github.com and unzip into my
node_modules

Exactly ! This is the best way to make this module works

I tried to change "react-native-orientation"<EMAIL_ADDRESS>but still not working.../Users/luca/workspace/pillsy/android/app/src/main/java/com/pillsy/MainApplication.java:27: error: constructor OrientationPackage in class OrientationPackage cannot be applied to given types;
new OrientationPackage(this)
^
required: no arguments
found:
reason: actual and formal argument lists differ in length
1 error
:app:compileDebugJavaWithJavac FAILED

Please refer to updated documentation. NPM's version of the package is outdated. you should install it directly from GitHub.

Hey - I'm installing directly from Github, but Orientation is still locked to Portrait on Android devices. Help??


org settings: Unexport and rename some functions.

This has some renaming suggested in https://github.com/zulip/zulip/pull/8899#pullrequestreview-108505223.
Also, it has a small followup of https://github.com/zulip/zulip/pull/8865#issuecomment-377264935.

I'm adding another commit of refactoring here.

While working on another task find this refactor, so I think get_property_value function name is more generic here.

Sounds good.  Merged, thanks @shubhamdhama!


Use verify instead of clean install

As Robert Scholte keeps repeating, using clean install is a bad habit from the past ;-)
clean is not required any more by almost all plugins, as they support incremental builds. You rob them from their chance to optimize by blindly forcing them to redo everything.
install is also not necessary if you only need a verified artifact in your target folder. Just use verify and skip the installation to your local .m2 repository.
This would be a minimal change, but the speed improvement can be small but noticeable when doing it several times a minute.

+1 I will target that for the next release

As Robert Scholte keeps repeating, using clean install is a bad habit from the past ;-)
clean is not required any more by almost all plugins, as they support incremental builds. You rob them from their chance to optimize by blindly forcing them to redo everything.
install is also not necessary if you only need a verified artifact in your target folder. Just use verify and skip the installation to your local .m2 repository.
This would be a minimal change, but the speed improvement can be small but noticeable when doing it several times a minute.

Thanks for the tip! I had no idea I should not be cleaning and installing so often. It makes sense when you put it like that.


Mapped error stack traces

Hi,
is there any way to get mapped stack traces when error is thrown?
I tried following example code and ended with source maps generated, but it would be nice if these source maps could be used to map error stack traces to original locations. Is there any way to achieve that?
I read this article describing how to achieve that with babel transpiler. I tried the same with traceur but it didn't work.
gulp.task('default', function () {
    return gulp.src('src/*.js')
        .pipe(sourcemaps.init())
        .pipe(traceur())
        .pipe(sourcemaps.write('.'))
        .pipe(gulp.dest('dist'));
});

Thanks for reply.

That should be handled by Traceur, not this plugin.
https://github.com/google/traceur-compiler/issues


make list_files recursive

This is rare, but when license(s) are hosted in a folder that is not the root directory of the repository, Gimie currently does not pick them up.
fix should include changing the list-files function to look inside "license-like" folders, instead of only the root dir.
Rest of the script should remain pretty untouched.

suggestion: list_files should probably not look for license-specific folder names, as it is a general method. It could just work recursively up to a fixed depth.

Agreed, had not yet updated this issue after our train conversation. Recursion limit definitely seems smart. If someone puts a license more than 3 layers deep it's their own fault for making it so hard to find.
use case I'm scared of without recursion limit is something like zarr folder structure, where the hierarchy of data is represented as folders within folders.

Another idea: Recursion limit + exclude-list for the file format. If I'm a imaging tool, I might not put a mp4 of cell microscopy footage in 4k in the root folder, but I could provide it as an example in a example folder. If we limit to look only in files which are some sort of text-format, we could bypass most of my fears I think, and we would only deal with "number of files" as a danger. Optionally, a file size limit to max a few kb...
and that too, we could cover with a if statement - only look through this folder, if the folder has less than 100 files (or 568, for the edge edge edge case where someone incorporates all 568 unique spdx licenses) in it or something. it's a bit dirty but should catch 99% of cases?

I think filtering on file-type should be the job of the consumer (e.g. filtering for a license-like filename, or a specific extension).
list_files() returns Resources which only have the name and the pointer to read the file.
The size of a Resource is therefore independent on file size, still I see how it could cause an issue in the parser function if the file takes ages to parse. FIltering on file-size make sense if this is available from GitHub/GitLab's GraphQL API, but not if we need to download the file to know their size.
I agree that the number of files might be an issue. I suspect GraphQL responses are already paginated to 50 or 100, btw.
I guess the method could then look something like:
def list_files(self, max_n_files=100, max_file_size_kb=2048) -> List[Resource]

To provide an explicit example, I tried to expand on what a consumer may look like here: https://github.com/SDSC-ORD/gimie/issues/72#issuecomment-1772207044

@rmfranken while I agree that list_files should be recursive, it seems that for licenses, the recommended practice is to put the license at the root folder, moreover some repositories (e.g. kafka) store their dependencies' licenses in a folder.
For this reason, I would advise not to look for licenses in directories, at the risk of having a few false negatives.

Haha! Some midnight inspiration?
I am also tempted - especially because false-negatives are much less consequential in our context than false positives. I also have not had much time for it lately - so the lower priority is fine for me. :)
I also guess there are bigger fish we can fry to provide end-user value than to go from 95 to 100% on licenses. CFF parser, ML Code quality scoring, input/output file format extraction (that one is probably very tricky, but very useful).


Cherry-pick to 'live': Add documentation for input validation #315

Microsoft Reviewers: Open in CodeFlow

Docs Build status updates of commit 3ea7f7d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/authoring-cards/input-validation.md
:white_check_mark:Succeeded

AdaptiveCards/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Unrecognized commands provide no feedback.

Entering a command that doesn’t exactly match the expected input has no response. E.g. I left the path to the aurora config file off from the aurora job create … command, and there was error message from the client telling me what I did wrong.

done! I will update the demo


More updates

Updats and additions for comments from Clouditor branch (https://github.com/clouditor/clouditor/pull/1305):

Add DataHasValue
Update proto types
Ignore object and data properties with "prop:parent"
Use label names instead of IRIs
Start message comment with "X is an entity in our Cloud ontology"
Add proto type map  for "xsd:java.util.Map<String, String>"

We should rename the tool to owl2proto.

We should rename the tool to owl2proto.

Good idea


Build failure with GHC 8.0 and 8.2

I'm seeing this build failure:
[ 7 of 20] Compiling Data.Metrics.Reservoir.Uniform ( src/Data/Metrics/Reservoir/Uniform.hs, dist/build/Data/Metrics/Reservoir/Uniform.o )

src/Data/Metrics/Reservoir/Uniform.hs:46:1: error:
    • Illegal instance declaration for
        ‘HasInnerReservoir UniformReservoir a’
        The coverage condition fails in class ‘HasInnerReservoir’
          for functional dependency: ‘s -> a’
        Reason: lhs type ‘UniformReservoir’ does not determine rhs type ‘a’
        Un-determined variable: a_aukW
        Using UndecidableInstances might help
    • In the instance declaration for
        ‘HasInnerReservoir UniformReservoir a_aukW’
   |
46 | makeFields ''UniformReservoir
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

@snoyberg is there anywhere I can see the failure publicly? I've built metrics locally on two separate machines using GHC 8.0 and 8.2, so I'm a little confused about what your configuration is doing differently.

I was able to reproduce with:
stack build --resolver nightly-2017-08-08 metrics-<IP_ADDRESS>

OK, thanks. Should be legitimately fixed in metrics-<IP_ADDRESS>