Nodemailer/Sendgrid on contact form not working by default on Heroku

For setting up on Heroku the contact form mailer doesn't work by default.
In addition to the Mongodb add-on, the sendgrid addon should also be added.
I simply added by doing heroku addons:create sendgrid:starter
And then I had to update user on contact.js controller from process.env.SENDGRID_USER to process.env.SENDGRID_USERNAME
It might be helpful for others to add these notes to the README?

I was able to get it to work on Heroku without the sendgrid addon in Heroku.  The developer still does need to create an account with Sendgrid.  Basically, I just did step 1 and 2 from the readme.md, and then added the environment variables the the Heroku instance (didn't need to change contact.js)
From the readme.md:

Go to https://sendgrid.com/user/signup
Sign up and confirm your account via the activation email
Then enter your SendGrid Username and Password into .env file

So instead of #3, I added the configs through the bash/command prompt via the Heroku Toolbelt/CLI by the command heroku config:set  SENDGRID_USER=[sendgridUserID] SENDGRID_PASSWORD=[sendgridPassword] .  Alternatively you can use the Environment Variables under the Settings UI tab of your Heroku instance to add the SENDGRID_USER and SENDGRID_PASSWORD
Same with Mongodb, you don't have to add a Heroku add-on, if you have an instance running somewhere already (even at mlabs), you just need to add the environment variables to your Heroku dyno instance :)


Fix running unit tests on Windows

What problem does this PR solve?
Support running unit tests on Windows again.
What is changed and how it works?

Only enable the RLimit check for Local backend on Unix, so Lightning can be built on Windows.
Inside listFiles, always convert make path use / as separator

Check List
Tests

Unit test

Side effects
Related changes

/run-all-tests

/run-all-tests

/run-all-tests tikv=a757f69592492580e657e4325594c90ac8dcf408

/run-all-tests tikv=410fb55ad2c9518f3f2262680c8ac5c643ef8a1c

/run-all-tests tikv=f5a11345d9fe72fdecfeab7f704476254ccb8cb4

/run-all-tests tikv=934d9d88515ac251f8897364619829d5e2f2cc05

/run-all-tests


[Feature] Add pagination settings

Fixes #196
Depends on #263

[ ] Tests Added

Can you fix the conflicts here?

Conflicts fixed and rebased on #263

added tests, and rebased on #263

Sorry @ahmednfwela, but can you rebase here? It is hard to make the review with multiple changes happening


ng build fails to copy to dist folder with folder names shorter than 5 characters

1. OS
Windows 10 Enterprise 64 bit
2. Versions
angular-cli: 1.0.0-beta.1
node: 6.1.0
3. Repro steps.

Create an app with angular-cli
Create i18n folder under app src\app\assets
Launch ng build

4. Log
Build failed.
EPERM: operation not permitted, unlink 'E:\projects\test angular\dist\app\assets'
Error: EPERM: operation not permitted, unlink 'E:\projects\test angular\dist\app\assets'
at Error (native)
at Object.fs.unlinkSync (fs.js:1083:18)
at TreeSync. (E:\projects\test angular\node_modules\angular-cli\node_modules\angular-cli\node_modules\tree-sync\index.js:71:21)
at Array.forEach (native)
at TreeSync.sync (E:\projects\test angular\node_modules\angular-cli\node_modules\angular-cli\node_modules\tree-sync\index.js:50:14)
at Class.module.exports.Task.extend.copyToOutputPath (E:\projects\test angular\node_modules\angular-cli\node_modules\angular-cli\lib\models\builder.js:124:10)
at E:\projects\test angular\node_modules\angular-cli\node_modules\angular-cli\lib\models\builder.js:132:21
at lib$rsvp$$internal$$tryCatch (E:\projects\test angular\node_modules\angular-cli\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1036:16)
at lib$rsvp$$internal$$invokeCallback (E:\projects\test angular\node_modules\angular-cli\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1048:17)
at E:\projects\test angular\node_modules\angular-cli\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:331:11
at lib$rsvp$asap$$flush (E:\projects\test angular\node_modules\angular-cli\node_modules\angular-cli\node_modules\rsvp\dist\rsvp.js:1198:9)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
5. More details
It seems ng build fails with folder names shorter than 5 characters.

Did you run your CMD with Administrator Permissions?

Yes, I run CMD with Administrator permissions. If I rename the folder from i18n to i18n2, ng build works correctly.

@OasisLiveForever our project has several short names ('core', 'mock', etc) and we don't have this problem.

@sgbeal This morning I tried to clean manually dist folder before building and now everything works fine. I let you know if I found a way to systematically reproduce the problem.

Thanks, this is odd. If you find a way, please file a bug with repro steps.

A TINY LITTLE HINT about where it could possibly be happening is all i'm asking for. The error clearly comes from code outside our project, but is clearly triggered by "something" in our project (which, i reiterate, builds and runs fine without the -prod flag in all angular-cli versions, and with the -prod flag in versions 0.0.34 and older, so the bug is obviously somewhere outside our code). The message is absolutely useless and precludes any chance of even beginning to find where the problem is.

It might also be coming from Broccoli, or Ember CLI, which we use extensively in our build system.
Seems to be a permission thing. Maybe your user created some files with some permission (you built once using a different user?) and the build system didn't have the permissions needed to overwrite those files?

This is all under ./tmp, which your build process creates. i regularly delete ./tmp (several times per day) because i don't like that so many files are left lying around in there. This is a single-user system and terminals are only run with admin permissions (because npm doesn't work without that). We're all at an utter loss.


Remove debug option

Removed the debug functionality and the Report type which is no longer necessary. Changes how the results are printed on the command line. Example output:
Suite "fail-check":
    - 005                                      ✓
    - Regression-86                            ✓
    - 002                                      ✓
    - 003                                      ✓
    - 004                                      ✓
    - 001                                      ✓
6/6 successful

Suite "success":
    - Regression-230b                          ✓
    - 015                                      ✓
    - 005                                      ✓
    - 009                                      ✓
    - Regression-137                           ✓
    - Regression-230                           ✓
    - 013                                      ✓
    - 002                                      ✓
    - 014                                      ✓
    - 003                                      ✓
    - 007                                      ✓
    - 008                                      ✓
    - 011                                      ✓
    - 006                                      ✓
    - 012                                      ✓
    - 004                                      ✓
    - 010                                      ✓
    - 001                                      ✓
18/18 successful

Suite "examples":
    - vect                                     ✓
    - ExpressionsCaseStudy                     ✓
    - stlc_bool                                ✓
    - ParigotEncoding                          ✓
    - evalorder                                ✓
    - classical_logic                          ✓
    - absurd                                   ✓
    - example                                  ✓
    - local_matches                            ✓
    - pi                                       ✓
    - FuStumpEncoding                          ✓
    - buffer                                   ✓
    - ChurchEncoding                           ✓
    - stlc                                     ✓
    - colist                                   ✓
    - eq                                       ✓
    - simple                                   ✓
    - ScottEncoding                            ✓
    - strong_existentials                      ✓
    - gadt                                     ✓
    - functor                                  ✓
    - refinement                               ✓
    - boolrep                                  ✓
    - neg_inverse                              ✓
    - motive                                   ✓
    - typedhole                                ✓
    - arith                                    ✓
    - comatches                                ✓
    - Webserver                                ✓
    - setoid                                   ✓
    - covect                                   ✓
    - stream                                   ✓
32/32 successful

Suite "fail-parse":
    - P-001                                    ✗

    Expected failure, got Module { uri: Url { scheme: "file", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/home/david/polarity/polarity/test/suites/fail-parse/P-001.pol", query: None, fragment: None }, items: [] }

    - Regression-underscore-expr               ✓
    - P-003                                    ✓
    - P-002                                    ✓
3/4 successful

Suite "fail-lower":
    - L-002-04                                 ✓
    - L-002-02                                 ✓
    - L-004                                    ✓
    - L-002-05                                 ✓
    - L-002-03                                 ✓
    - L-005                                    ✓
    - L-003                                    ✓
    - L-001                                    ✓
    - L-002-01                                 ✓
9/9 successful

In total: 68/69 successful

Would be nice to order the results for better readability.

Done :)


[BUG] getJavaScriptFileURLRequest doesn't work via cocoapods

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSURL initFileURLWithPath:]: nil string parameter'

AAChartKit does not support cocoapods yet

AAChartKit  supported CocoaPods ,More details in README file.


[New Port Request]

Library name:  coreutils
Library description: The GNU Core Utilities are the basic file, shell and text manipulation utilities of the GNU operating system. These are the core utilities which are expected to exist on every operating system.
Source repository URL: https://ftp.gnu.org/gnu/coreutils/coreutils-8.32.tar.xz
Project homepage (if different from the source repository): https://www.gnu.org/software/coreutils/
Anything else that is useful to know when adding (such as optional features the library may have that should be included):

Hi there, @jiangjianshan ; when/how would someone want to use coreutils as a library? Note that we don't generally intend to provide "tools" unless they are needed to build something.

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


instance with newtype?

How can I make an instance from a data type with a newtype - and flatten the newtype structure?
i.e. not _id: [ : "123456789012345678901234"] but _id: "123456789012345678901234"

Ah nvm this isn't the right thing - I'm looking for deriving (Val) from Database.MongoDB.


UnicodeDecodeError

Traceback (most recent call last):
  File "evtxtract/main.py", line 83, in <module>
  File "evtxtract/main.py", line 58, in main
  File "evtxtract/__init__.py", line 98, in extract
  File "evtxtract/templates.py", line 146, in insert_substitutions
  File "/home/user/env/lib/python2.7/re.py", line 155, in sub
UnicodeDecodeError: 'ascii' codec can't decode byte 0x80 in position 1: ordinal not in range(128)

binary type nodes were not being encoded. fixed in 88d4dc95e896d97e9f80133ce7b102c9bd74eb03, with these nodes being hex-encoded.


FIX: Fix for buffer_size=None

Closes #1507.

This is ready for review/merge as well.

thanks @Eric89GXL !


[Fix] relay onnx frontend bug when [A, B, M, N] * [1, B, N, K]

Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

Fix BUG and add test case for batch_matmul [A, B, M, N] * [1, B, N, K]
cc @Huyuwei @jwfromm @kazum @mbrookhart @siju-samuel

Will take a look later today

hi @AndrewZhaoLuo , I have fixed the comment.


[DOP-15749] - separate ReadOptions into ReadOptions and SQLOptions

Change Summary

ReadOptions and SQLOptions have been separated for JDBC connections. SQLOptions is now required for .sql method calls
Add following tests and documentation

Related issue number

Checklist

[x] Commit message and PR title is comprehensive
[x] Keep the change as small as possible
[x] Unit and integration tests for the changes exist
[x] Tests pass on CI and coverage does not decrease
[x] Documentation reflects the changes where applicable
[x] docs/changelog/next_release/<pull request or issue id>.<change type>.rst file added describing change
(see CONTRIBUTING.rst for details.)
[x] My PR is ready to review.

В unit тестах есть test_jdbc_read_options_default. Нужно сделать такой же для SQLOptions.


Co-applicant functionality

In determining the full scope of the Partner role, has come up a few times that the ability to have "co-applicants" would be nice to have. @frjo suggested that both applicants and staff could assign the co-applicant and would provide the email of the intended co-applicant. In selecting, staff would receive a list of possible users & suggestions (similar to assigning a partner/reviewer) but the applicant would not to preserve the privacy of existing users in the system.
I imagine the user being assigned as co-applicant should have some option to actually accept being a co-applicant, along with the ability to remove themselves from the application if any applicant can do this assigning.

this is a huge "nice-to-have" - not a current priority or something that is being heavily requested


Map moss

This pull request maps the moss carpets and moss blocks added in 21w05a.

Shouldnt this also include the moss blocks in Blocks.java? I only see the items for the new moss blocks

That isn't necessary since they are auto-mapped based on the string passed to the register method.

oh wait, yarn is way smarter than i thought


Improved overview screen on data exploration

Describe the bug
Tile UI doesn't show data features too repeatedly Need improvement

If data is of type datasource, the first dashboard thumbnail is shown. (removed)
'No data' notification label required when no data
The font size of the title is too large. (I think 22px seems reasonable) => it's a publishing issue.
Header(Exploration header, search area) replacement - remove intro the header (move to another issue #2894)
Catalog panel changed

Caroussel UI
If there is no 1depth, no path should be indicated (In case of 'favorite catalog')
'All catalog' panel is activated on first entry

To Reproduce
Steps to reproduce the behavior:

Go to 'Exploration > Data'

Expected behavior
Screenshots

@AnnieHwang
1)If data is of type datasource, the first dashboard thumbnail is shown.
-Is this a bug? or Do you mean display thumbnail of first dashboard of datasource  if type is datasource?

Header(Exploration header, search area) replacement - remove intro the header

can you explain more about this?

@thinkcsww 1) Deleted once. I will tell you after registering a new issue.
4) It's a new issue. # 2894

@AnnieHwang
Then in this issue todos are

No data' notification label required when no data
The font size of the title is too large. (I think 22px seems reasonable) => it's a publishing issue.
Catalog panel changed
Caroussel UI
If there is no 1depth, no path should be indicated (In case of 'favorite catalog')
'All catalog' panel is activated on first entry

Is it Right?

@thinkcsww The design is complete. Please, check it.

@AnnieHwang
The number is for which feature?

@thinkcsww This number is the number of metadata belonging to the catalog.

@thinkcsww
Metadata numbers in catalog favorites are not included in the API. How are you counting the numbers?

@ufoscw
It is not counting. Must be provided in api

@eltriny
Please develop without counting.
It will be added to the API later.


Xiaomi crash java.lang.SecurityException SYSTEM_ALERT_WINDOW

Crash on myMethodWithPermissionCheck() when use @NeedsPermission(Manifest.permission.SYSTEM_ALERT_WINDOW)
Library version : 3.3.1 with kapt processor
Devices affected : Only Xiaomi Mi A1
Stacktrace:
Fatal Exception: java.lang.SecurityException: com.obscience.imamma from uid 10012 not allowed to perform SYSTEM_ALERT_WINDOW
       at android.app.AppOpsManager.noteOp(AppOpsManager.java:1837)
       at android.app.AppOpsManager.noteOp(AppOpsManager.java:1654)
       at android.support.v4.app.AppOpsManagerCompat.noteOp(AppOpsManagerCompat.java:106)
       at permissions.dispatcher.PermissionUtils.hasSelfPermissionForXiaomi(PermissionUtils.java:111)
       at permissions.dispatcher.PermissionUtils.hasSelfPermission(PermissionUtils.java:96)
       at permissions.dispatcher.PermissionUtils.hasSelfPermissions(PermissionUtils.java:76)
       at com.obscience.imamma.AbstractMainActivityPermissionsDispatcher.startBubbleServiceWithPermissionCheck(AbstractMainActivityPermissionsDispatcher.java:41)
       at com.obscience.imamma.AbstractMainActivity.startOrUpdateBubble(AbstractMainActivity.java:476)
       at com.obscience.imamma.AbstractMainActivity.onCreateMenu(AbstractMainActivity.java:466)
       at com.obscience.imamma.AbstractMainActivity$$Lambda$0.onClick(Unknown Source:4)
       at com.android.internal.app.AlertController$ButtonHandler.handleMessage(AlertController.java:166)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:172)
       at android.app.ActivityThread.main(ActivityThread.java:6590)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

Seems Xiaomi doesn't support SYSTEM_ALERT_WINDOW? 🤔

@francescobonni if you don't use the library can you deal with the problem? 👀(thank you for your report and sorry for being late 🙇 )

No problem, I'm trying to find a Xiaomi MI A1 to perform the test without using the library and check if the problem is in the library or device. I will give you updates on the problem as soon as possible

any update?🙏

@francescobonni any update? 🙇

@hotchemi I'm sorry I had a lot of problems, but I found the device, this weekend I send you updates.

@hotchemi
Finally I have updates, I tested with a clean application, the system overlay request and I found the behavior to replicate the crash on xiaomi mi a1 (now on Fabric i see same crash with redmi note 4 and android 6).
The crash occurs only if you use the library, step to reproduce the crash:

Activate the permission for the overlay through the app
I open the app information (eg through the launcher) and revoke the permission for the overlay
Return to the app and try to activate the permission again
Crash
Reopen app and retry to activate
Crash
Close app from recent
Open and retry to activate
Crash
I install the same app with manual permissions, everything works
I try in my Nexus 6P, everything works, both permission dispatcher and manual permissions

If you want I can put on my github the sample project I used, but it's very simple, a button that requires overlay permissions

@francescobonni oh it's happening on Android 6 as well..could you give us your sample project if possible? 🙇 Weird.. 👁

This is the sample project
I'm new on github, I did not know how to do things correctly, in the project at the moment you find 2 branches in addition to master (the first for the test without using the library and the second to test the library)

@francescobonni Thank you!

**News:
Device afflicted update:

Xiaomi Mi A1    (Android 8.1 & Android 8.0)
Xiaomi Mi A2 Lite (Android 8.1)
Xiaomi Redmi Note 4 (Android 6)

Sorry for the late. I think the cause is in https://github.com/permissions-dispatcher/PermissionsDispatcher/blob/1564313f8b253685dc7189b0fbb31a42b2e86796/library/src/main/java/permissions/dispatcher/PermissionUtils.java#L95
May be we don't need to have a workaround for SYSTEM_ALERT_WINDOW 🤔
@francescobonni Do you think the same thing would happen with WRITE_SETTINGS? 👀

@hotchemi this weekend I'll try the WRITE_SETTINGS and update you

I guess you never tried it that weekend

Yes, I'm so sorry, but today I tried the write settings, same problem

ooh thank you. I'll address.

Let us know your opinion https://github.com/permissions-dispatcher/PermissionsDispatcher/issues/544

Since we've already removed Xiaomi support from the lib let us close the issue.
@francescobonni thank you for your dedicated contribution 🙇
ref: https://github.com/permissions-dispatcher/PermissionsDispatcher/pull/548


avoid deprecated methods since sbt 0.13.13

http://www.scala-sbt.org/0.13/docs/Migrating-from-sbt-012x.html

Thank you for the contribution @xuwei-k !  I will add you to the contributors when we release 1.3 soon.


Generate and export named event responses for ethers v5

Currently TypeChain generates types similar to the following:
class ContractAbc extends Contract {
...
  filters: {
    TemplateCreated(
      templateId: BytesLike | null,
      airnodeId: null,
      endpointId: null,
      parameters: null
    ): TypedEventFilter<
      [string, string, string, string],
      {
        templateId: string;
        airnodeId: string;
        endpointId: string;
        parameters: string;
      }
    >;
    ...

The problem is that I can't use filters to query my event. Instead I want to pass tx.hash, and parse the logs myself. However at that point I would like to cast my event response to the Type generated by TypeChain.
For example, this code:
    contractAbc.provider.once(tx.hash, (tx) => {
      const parsedLog = airnodeRrp.interface.parseLog(tx.logs[0]);
      resolve(parsedLog.args.templateId); // This is untyped (args is basically any)
    })

Instead I would like to have a code like this:
    contractAbc.provider.once(tx.hash, (tx) => {
      const parsedLog = airnodeRrp.interface.parseLog(tx.logs[0]).args as TemplateCreatedEvent;
      resolve(parsedLog.templateId); // parsedLog should be typed
    })

Slightly related: https://github.com/ethereum-ts/TypeChain/issues/249

It would be cool to have the possibility to explicitly say in the typechain export moment which interface use for types so also those interfaces would be exported and be usable on the frontend side directly

Done in https://github.com/dethcrypto/TypeChain/releases/tag/%40typechain%2Fethers-v5%407.1.0
Duplicate of: https://github.com/dethcrypto/TypeChain/issues/398

damn cool!


[Question] Spectral Linting Step Shows warnings and all tests are failed

Release version
5.1.1
Question Details
Extractor Pipelines shows error for Spectral linting. Is this OK if there are some errors/warnings for this step.
If Yes then can I disable these steps
Install Node.js
Install Spectral
Run Spectral Linting
Linting results for API
Expected behavior
All steps for extractor pipeline should work without any error/warnings
Actual behavior
Extractor pipeline shows error/warnings for Spectral linting steps
Reproduction Steps
Run the Extractor pipeline against DEV-APIM

Hi @Arslan007,
This Spectral linting step just allows you to check if your swagger respects the Open API rules (you can find reference here: https://docs.stoplight.io/docs/spectral/4dec24461f3af-open-api-rules).
It will not prevent you from extracting your api, creating a PR for the main branch and to push it to higher apim environment.
It is just showing a warning if the step is not completed without errors.
If you don't need these steps, feel free to comment or delete the mentioned steps.


Menu doesn't highlight properly with 6 mounts

Describe the bug
When I have 5 mounts bound, the menu highlights properly.  When I have all 6 bound, it highlights the wrong mount upon mouseover.  Upon releasing the button, it seems to work properly, as the mount the mouse is over gets selected.
To Reproduce
Steps to reproduce the behavior:

Hold overlay bind.
Hover over mount desired.
It highlights the next mount clockwise from it.

Expected behavior
I expect the mount the mouse is over to be highlighted.
Screenshots
Album for ya: https://imgur.com/a/GtsZ4RC
System configuration (please fill in):
Windows 10
AMD R9-380 4G
No chainloading, I do use TacO from time to time.
Additional context
Also happens with uncentered binding.

Duplicate of #28


Consider stdout/stderr outputs

E.g. for afni 3dinfo
CWL also has this option

Implemented in 4a22848c8d6069cebf79eac373707ab60ee1d5f1


AWS Plugin Roadmap

This is a break down of how the AWS plugin will be developed. The tasks were largely broken down based on my estimated sizing of PRs. I'm hoping to keep each task around <1k loc (hopefully less) to keep it more manageable for reviewers. Happy to hear thoughts if this could be done better.

Resource creation (VMs only)
Permit list rules addition (within single VPC/namespace) and deletion
Permit list rules addition (NAT gateways for public IPs, peering for intra-cloud inter-namespace connections)
Multicloud connections including (VPN gateway setup, integration with orchestrator)
Docs and cleanup (quickstart example)
K8s
Private endpoints
Brownfield deployments

@seankimkdy you want to make this into subtasks with - [ ]? GitHub allows you to selectively turn those into separate issues and or keep them inline and manually mark them as done.


dev fails with a websocket redirect error

🐛 Bug Report
Environment

operating system: macos
output of rustc -V: 1.47.0
output of node -v: v14.15.1
output of wrangler -V: 1.12.3 / master
contents of wrangler.toml

name = "service_id"
type = "webpack"
account_id = "..."
workers_dev = true
route = "some_domain.net/*"
zone_id = "..."

kv_namespaces = [
  { binding = "KV", id = "...", preview_id = "..." }
]

Steps to reproduce
wrangler dev

What did you expect to see?
Service to start up
What did you see instead?
thread 'tokio-runtime-worker' panicked at 'Failed to connect to devtools instance: Http(302)', src/commands/dev/socket.rs:30:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
👂  Listening on http://<IP_ADDRESS>:8787
Error: panic

This is triggered in src/commands/dev/socket.rs:28 / wrangler::commands::dev::socket::listen::{{closure}}
Unfortunately due to tokio-tungstenite returning only the status, I don't know exactly what the contents are.
It may be related however due to us using access authentication on the domain. If I print out the url wrangler is trying to connect to (https://some_domain.net/cdn-cgi/workers/preview/inspector?f_workers_preview_token=...) and try to curl it, I can see:
< HTTP/2 302
...
< location: https://....cloudflareaccess.com/cdn-cgi/access/login/some_domain.net

which I expect is the same redirect wrangler sees.

I was able to work around this issue by not simultaneously specifying both zone_id and workers_dev when running wrangler dev.
A configuration like this works:
name = "service_id"
type = "webpack"
account_id = "..."
route = "some_domain.net/*"

kv_namespaces = [
  { binding = "KV", id = "...", preview_id = "..." }
]

[env.dev]
workers_dev = true

[env.prod]
zone_id = "..."

We made some updates to websockets support.. is this still an issue?


fix(#303): Update README with compatibility info

Fixes #303

@ayuwono, what's the easiest way to run Node.js Client API tests on the earliest and latest versions of ML8? I would like to substantiate that the upcoming release works on all versions of 8, and proving that it works on the earliest and latest would be strong proof of this. I've actually already run the tests on 8.0-6.3, so what I'm really looking for is the first version of ML8.

@jmakeig, here's what we get in the current docs generation when we use  @since):

It would be great to add that info across the API docs. It would take some sleuthing to determine each method came into being.

At this stage, you can probably get away with tagging everything with 1.0, except what's new in 2.0-1. The whole API was new for 8.0-1, and while there were a few functional changes (like being able to pass multiple URIs to Documents.remove), I don't think any new functions or interfaces were added in 8.0-x.
The thing I always wonder about with a feature like this (we get requests for the XQuery docs, too) is what is the contract, really? Like in the example I gave above, Documents.remove was there from the beginning, but had its functionality extended. Does that get a version bump or not? Just one of those "inquiring minds want to know" things. :)

@wooldridge, are you looking for the earliest version of ML8 (like 8.0-6.1)? You can find it at /project/engineering/builds/

I've updated the JSDoc information with  @since tags. All methods and namespaces are marked version 1.0 except for the following:
documents.protect()
documents.wipe()
documents.protectResult()
documents.wipeResult()
patchBuilder.patchBuilderMetadataValues
patchBuilderMetadataValues.add()
patchBuilderMetadataValues.remove()
patchBuilderMetadataValues.replace()
queryBuilder.falseQuery()
queryBuilder.geospatialRegion()
queryBuilder.minDistance()
queryBuilder.trueQuery()
queryBuilder.MinDistanceParam

I also updated the README to specify that 2.0.1 has been tested successfully with 8.0-6.3 and 9.0-1, which is true.  I discussed this with @ehennum, and he said this aligns with the rolling upgrade requirements for the client APIs: MarkLogic must offer clients that work with the latest release of the current version (e.g. 9.0-1) and the latest release of the previous version (e.g. 8.0-6.3).
Erik and I also discussed the need for specifying version compatibility with each our tests for more efficient testing of API compatibility with MarkLogic versions. I could then run 2.0.1 on ML 8.0-6.3 and have it skip the tests for new features in 9.0-1.

I'm going to merge this and close the associated issue (#303). We can fine tune the README as @jmakeig prepares release notes (https://github.com/marklogic/node-client-api/issues/327).


Avoid searching SDK references in DTAR

Avoid searching SDK references in DTAR
SDK references return "assembly" as their Reference.Type for compatibility reasons. We should looking at them as we're only looking at assemblies.
Hit this as part of: https://github.com/dotnet/roslyn-project-system/issues/1555.

tag @dotnet/project-system


chore: release main

:robot: I have created a release beep boop
@markdown-confluence/cli: 5.2.5
5.2.5 (2023-05-10)
Miscellaneous Chores

@markdown-confluence/cli: Synchronize obsidian packages versions

Dependencies

The following workspace dependencies were updated

devDependencies

@markdown-confluence/lib bumped from 5.2.4 to 5.2.5
@markdown-confluence/mermaid-puppeteer-renderer bumped from 5.2.4 to 5.2.5

@markdown-confluence/lib: 5.2.5
5.2.5 (2023-05-10)
Miscellaneous Chores

@markdown-confluence/lib: Synchronize obsidian packages versions

@markdown-confluence/mermaid-electron-renderer: 5.2.5
5.2.5 (2023-05-10)
Miscellaneous Chores

@markdown-confluence/mermaid-electron-renderer: Synchronize obsidian packages versions

Dependencies

The following workspace dependencies were updated

dependencies

@markdown-confluence/lib bumped from 5.2.4 to 5.2.5

@markdown-confluence/mermaid-puppeteer-renderer: 5.2.5
5.2.5 (2023-05-10)
Miscellaneous Chores

@markdown-confluence/mermaid-puppeteer-renderer: Synchronize obsidian packages versions

Dependencies

The following workspace dependencies were updated

dependencies

@markdown-confluence/lib bumped from 5.2.4 to 5.2.5

obsidian-confluence: 5.2.5
5.2.5 (2023-05-10)
Bug Fixes

Only load CSS that exists for obsidian styles (c825559)

Dependencies

The following workspace dependencies were updated

dependencies

@markdown-confluence/lib bumped from 5.2.4 to 5.2.5
@markdown-confluence/mermaid-electron-renderer bumped from 5.2.4 to 5.2.5

obsidian-confluence-root: 5.2.5
5.2.5 (2023-05-10)
Bug Fixes

Only load CSS that exists for obsidian styles (c825559)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/markdown-confluence/markdown-confluence/releases/tag/obsidian-confluence-v5.2.5 :sunflower:

:robot: Release is at https://github.com/markdown-confluence/markdown-confluence/releases/tag/%40markdown-confluence/lib-v5.2.5 :sunflower:

:robot: Release is at https://github.com/markdown-confluence/markdown-confluence/releases/tag/%40markdown-confluence/mermaid-electron-renderer-v5.2.5 :sunflower:

:robot: Release is at https://github.com/markdown-confluence/markdown-confluence/releases/tag/%40markdown-confluence/cli-v5.2.5 :sunflower:

:robot: Release is at https://github.com/markdown-confluence/markdown-confluence/releases/tag/%40markdown-confluence/mermaid-puppeteer-renderer-v5.2.5 :sunflower:

:robot: Release is at https://github.com/markdown-confluence/markdown-confluence/releases/tag/obsidian-confluence-root-v5.2.5 :sunflower:


Gatus: Add ability to use existing Secret in extraVolumeMounts list

This PR adds the ability to use an existing secret in the extraVolumeMounts list. An example of how to do this is in the values file, however its basically the same as using a configMap.
E.G.
  - name: extra-volume-3
    mountPath: /mnt/volume3
    readOnly: true
    existingSecret: secret-name

When specified, the volume for that list item will use secret.secretName.

@avakarev Can we get this reviewed and merged up?
I am also happy to bump the chart.yaml version and the gatus appVersion as well (since there are newer builds).

@PurseChicken thank you for your contribution


Fix example docs on embedded_asset macro

Objective
The derive macro wasn't doc-commented, so it showed up in the generated doc as follow:
#[derive(Asset, TypePath)]
let shader = asset_server.load::<Shader>("embedded://bevy_rock/render/rock.wgsl");

Which is very confusing
Solution
Comment the derive attribute as well

Merging as trivial.


Docs refactor

Add a ditamap to replace the old HTML TOC.
Replace {{}} styled links with absolute or relative links.
Change internal links to .markdown.
Use GitHub flavored ATX headings (#).
Add backticks to code examples with [] characters.
Add H1s to all docs.
Add a small GitHub action to test for docs issues on PRs.

Added a Github action to fire off the docs branches. We'll need to add the relevant secrets for that.


[bug] Fail to sign protoc sidecar with Azure Trusted Signing

[!IMPORTANT]
The issue was that the sidecar binary was read-only but Tauri silenced the permission error. See https://github.com/tauri-apps/tauri/issues/11778#issuecomment-2495504198 for more info.

Describe the bug
I'm trying to get Azure Trusted Signing working for my app github.com/mountain-loop/yaak. It signs the main .exe correctly, and correctly skips the already-signed NodeJS sidecar. However, it seems to fail on the unsigned protoc sidecar.
Here is the output from https://github.com/mountain-loop/yaak/actions/runs/11976760384/job/33393142512
Finished `release` profile [optimized] target(s) in 11m 48s
warning: the following packages contain code that will be rejected by a future version of Rust: iso8601 v0.3.0, nom v4.2.3
note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1`
    Built application at: D:\a\yaak\yaak\src-tauri\target\release\yaak-app.exe
    Signing D:\a\yaak\yaak\src-tauri\target\release\yaak-app.exe
    Signing D:\a\yaak\yaak\src-tauri\target\release\yaak-app.exe with a custom signing command
    Info "[\r\n  {\r\n    \"cloudName\": \"AzureCloud\",\r\n    \"homeTenantId\": \"***\",\r\n    \"id\": \"b045e283-89f9-42ff-bd9a-95f6e7a9b035\",\r\n    \"isDefault\": true,\r\n    \"managedByTenants\": [],\r\n    \"name\": \"Yaak Subscription\",\r\n    \"state\": \"Enabled\",\r\n    \"tenantId\": \"***\",\r\n    \"user\": {\r\n      \"name\": \"***\",\r\n      \"type\": \"servicePrincipal\"\r\n    }\r\n  }\r\n]\r\n\r\nTrusted Signing\r\n\r\nVersion: 1.0.60\r\n\r\n\"Metadata\": {\r\n  \"Endpoint\": \"[https://eus.codesigning.azure.net/\](https://eus.codesigning.azure.net//)",\r\n  \"CodeSigningAccountName\": \"Yaak\",\r\n  \"CertificateProfileName\": \"yaakapp\",\r\n  \"ExcludeCredentials\": []\r\n}\r\n\r\nSubmitting digest for signing...\r\n\r\nOperationId 1eb5fd2a-01d6-45e8-b43a-bacda9cd5f54: InProgress\r\n\r\nSigning completed with status 'Succeeded' in 1.6176595s\r\n\r\nSuccessfully signed: D:\\a\\yaak\\yaak\\src-tauri\\target\\release\\yaak-app.exe\r\r\n\r\nNumber of files successfully Signed: 1\r\r\nNumber of warnings: 0\r\r\nNumber of errors: 0\r\r\n"
File: vendored\node\yaaknode-x86_64-pc-windows-msvc.exe
Index  Algorithm  Timestamp
========================================
0      sha256     RFC3161

Successfully verified: vendored\node\yaaknode-x86_64-pc-windows-msvc.exe

    Info sidecar at "vendored\node\yaaknode-x86_64-pc-windows-msvc.exe" already signed. Skipping...
File: vendored\protoc\yaakprotoc-x86_64-pc-windows-msvc.exe
Index  Algorithm  Timestamp
========================================
SignTool Error: No signature found.

Number of errors: 1

    Signing vendored\protoc\yaakprotoc-x86_64-pc-windows-msvc.exe
    Signing vendored\protoc\yaakprotoc-x86_64-pc-windows-msvc.exe with a custom signing command
failed to bundle project: `failed to run trusted-signing-cli`
    Error failed to bundle project: `failed to run trusted-signing-cli`
Error: Command failed with exit code 1: npm run tauri build

Reproduction
As seen in the tauri.conf.json#L82, the sign command I'm using is:
"windows": {
  "signCommand": "trusted-signing-cli -e https://eus.codesigning.azure.net/ -a Yaak -c yaakapp %1"
}

To debug this, I created a new workflow to simply run this command on the protoc binary (committed it directly to the repo for simplicity), and it succeeded: https://github.com/mountain-loop/yaak/actions/runs/11975020946/job/33387429516
- name: Sign files
  run: trusted-signing-cli -e https://eus.codesigning.azure.net/ -a Yaak -c yaakapp yaakprotoc-x86_64-pc-windows-msvc.exe
  env:
    AZURE_CLIENT_ID: ${{ matrix.platform == 'windows-latest' && secrets.AZURE_CLIENT_ID }}
    AZURE_CLIENT_SECRET: ${{ matrix.platform == 'windows-latest' && secrets.AZURE_CLIENT_SECRET }}
    AZURE_TENANT_ID: ${{ matrix.platform == 'windows-latest' && secrets.AZURE_TENANT_ID }}

Expected behavior
protoc binary should sign successfully during tauri-action build
Full tauri info output
[✔] Environment
    - OS: Mac OS 15.1.1 arm64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
    ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 22.8.0
    - npm: 10.8.2
    - deno: deno 1.44.0

[-] Packages
    - tauri 🦀: 2.1.1
    - tauri-build 🦀: 2.0.3
    - wry 🦀: 0.47.0
    - tao 🦀: 0.30.8
    - @tauri-apps/api : 2.0.2 (outdated, latest: 2.1.1)
    - @tauri-apps/cli : 2.1.0

[-] Plugins
    - tauri-plugin-dialog 🦀: 2.0.3
    - @tauri-apps/plugin-dialog : 2.0.0 (outdated, latest: 2.0.1)
    - tauri-plugin-updater 🦀: 2.0.2
    - @tauri-apps/plugin-updater : not installed!
    - tauri-plugin-log 🦀: 2.0.1
    - @tauri-apps/plugin-log : 2.0.0
    - tauri-plugin-window-state 🦀: 2.0.1
    - @tauri-apps/plugin-window-state : not installed!
    - tauri-plugin-os 🦀: 2.0.1
    - @tauri-apps/plugin-os : 2.0.0
    - tauri-plugin-fs 🦀: 2.0.3
    - @tauri-apps/plugin-fs : 2.0.0 (outdated, latest: 2.0.2)
    - tauri-plugin-shell 🦀: 2.0.2
    - @tauri-apps/plugin-shell : 2.0.0 (outdated, latest: 2.0.1)

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React

Stack trace
No response
Additional context
No response

Okay, it looks like this was indeed my fault. However, it seems that Tauri did not surface the error that would have helped me fix it.
Running the sign command directly worked, because I committed the binary directly to the repo. I did this on macOS.
However, signing the full app downloads and extracts the protoc binary from a GitHub release. The issue was that it extracts with a read-only permission.
I adjusted the test workflow to use the download script and got this helpful error: https://github.com/mountain-loop/yaak/actions/runs/11987805359/job/33422398760
[
  {
    "cloudName": "AzureCloud",
    "homeTenantId": "***",
    "id": "b045e283-89f9-42ff-bd9a-95f6e7a9b035",
    "isDefault": true,
    "managedByTenants": [],
    "name": "Yaak Subscription",
    "state": "Enabled",
    "tenantId": "***",
    "user": {
      "name": "***",
      "type": "servicePrincipal"
    }
  }
]

SignTool Error: Access is denied.
Number of files successfully Signed: 0
SignTool Error: An error occurred while attempting to sign: src-tauri/vendored/protoc/yaakprotoc-x86_64-pc-windows-msvc.exe

Number of warnings: 0

Number of errors: 1

thread 'main' panicked at C:\Users\runneradmin/.cargo\registry\src\index.crates.io-6f17d22bba15001f\trusted-signing-cli-0.3.0\src/main.rs:157:10:
called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "command [\"C:\\\\Program Files (x86)\\\\Windows Kits\\\\10\\\\bin\\\\10.0.22000.0\\\\x64\\\\signtool.exe\", \"sign\", \"/v\", \"/fd\", \"SHA256\", \"/tr\", \"[http://timestamp.acs.microsoft.com\](http://timestamp.acs.microsoft.com/)", \"/td\", \"SHA256\", \"/dlib\", \"C:\\\\Users\\\\runneradmin\\\\.trusted-signing-cli\\\\lib\\\\bin\\\\x64\\\\Azure.CodeSigning.Dlib.dll\", \"/dmdf\", \"C:\\\\Users\\\\runneradmin\\\\.trusted-signing-cli\\\\metadata.json\", \"src-tauri/vendored/protoc/yaakprotoc-x86_64-pc-windows-msvc.exe\"] exited with code 1" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Process completed with exit code 1.

So it seems that Tauri is silencing stderr of the custom sign command?

So it seems that Tauri is silencing stderr of the custom sign command?

It may be hidden behind the --verbose flag (or -vv / -vvv, not sure if the verbosity level matters here) 🤔

Which command would that flag be on?

tauri build --verbose, or in tauri-action args: --verbose. The signCommand will be executed the same way, we'd just check if the tauri cli is hiding some command output from us.

Ah great, I will give this a try, thanks!


feat: add gatsby-tinacms-mdx package

This is an active WIP. @ncphillips helped me a little bit but we figured it might be better to start with a draft PR to get some help asynchronously. (I've been too busy with a new job to coordinate outside work. I think this might be easiest.)
Summary
The goal of this PR is to add a new package called gatsby-tinacms-mdx to the tinaCMS/Gatsby package family so that users can use tinaCMS with their Gatsby/MDX sites similar to how they can use it with Markdown.
I struggled to get my local dev env working well to develop this plugin so I ended up developing it in isolation here.
Approach
I essentially copied the exact same approach in gatsby-tinacms-remark but for mdx specifically. That seemed to work for the most part but this isn't 100% complete and is not a fully-functioning state.
What I Need Help With

Guidance on testing this locally in the monorepo and in a Gatsby demo site (I haven't had much luck following the instructions in the README/CONTRIBUTING hence why I broke it into a separate repo)
Feedback on what might be missing to get this fully-functioning
Any other support that can help us get this ready for the community

Many thanks in advance ❤

I'm thinking I will merge this into a separate branch, and add you as a collaborator on the repo. That way you won't have to work off the fork, and the CI can run on the changes.

Merging this into a new branch and will open a new PR to keep workin on it!

https://github.com/tinacms/tinacms/pull/713 --> the new PR


Usage of OFM Tiles

hi christian, great Job, can i specify the tile url somewhere to use OFM Tiles?
Oliver

Great idea. I remeber that I was looking into this a while ago but couldn't really find a documentation of their public API (and if they offer one). I've just sent them an email, though, referring to your request and asking them if they have a public API and how it could be accessed.
If it is not possible, there seems to be the possibility to download their map tile data and serve them locally, which would make the setup of FSKneeboard much more complicated. But it might be an option... Let's see if the OFM team responds to my request and what their advice looks like!

Hi Chris,
i´m the core developer of OFM, we´ll find a way 😉
Von: Chris @.>
Gesendet: Samstag, 5. Juni 2021 21:42
An: Christian1984/vfrmap-for-vr @.>
Cc: Oliver Vorderegger @.>; Author @.>
Betreff: Re: [Christian1984/vfrmap-for-vr] Usage of OFM Tiles (#18)
Great idea. I remeber that I was looking into this a while ago but couldn't really find a documentation of their public API (and if they offer one). I've just sent them an email, though, referring to your request and asking them if they have a public API and how it could be accessed.
If it is not possible, there seems to be the possibility to download their map tile data and serve them locally, which would make the setup of FSKneeboard much more complicated. But it might be an option... Let's see if the OFM team responds to my request and what their advice looks like!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Christian1984/vfrmap-for-vr/issues/18#issuecomment-855286464, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC54AY6LNMCR73UMTRNCPY3TRJ4Y7ANCNFSM456XB6LQ.

neway data AG
Landstrasse 105 | 9490 Vaduz | Fürstentum Liechtenstein
[https://storage.googleapis.com/storage.newaydata.com/email/cube.JPG]

Oliver Vorderegger
+436649254114
@.***
neway data AG
Landstrasse 105 | 9490 Vaduz | Fürstentum Liechtenstein
[https://storage.googleapis.com/storage.newaydata.com/email/cube.JPG]

Wow, that's awesome :-) Love OFM. I used it a lot when I learned flying on VATSIM on the "flatscreen"!!! So, yeah, I'd love to add it to FSKneeboard.
The TileLayers are defined in maps.js:210ff. - All the data is currently pulled from public APIs.
I see two options using OFM tiles:
Option 1: Download them and put them in a local folder inside the FSKneeboard server's directory. Say /maps/ofmtiles for example. Then the local webserver (which is there already anyways) could simply server them. That would require the user, however, to download the latest map tiles manually.
Option 2: Simply refer to a public API on your server. That way we could always serve the latest and most up to date tiles that you publish on your OFM project page anyways. That would be awesome, but would obviously create some server load on your end...
Let me know what you think is the best approach!

Lets use the server api directly, there is one issue though:
We need to give the corresponding airac cycle to the api, as new cycles need quite a while to render and that happens when the old cycle is still valid.
The function to calc the current airac cycle is:
public getCurrAiracId(dateVal: Date): number {
let cDate = new Date(2003, 0, 23);

let counter = 0;

let lastCount = 0;

let year = dateVal.getFullYear();

while (cDate.getTime() < dateVal.getTime()) {

    if (cDate.getFullYear() === dateVal.getFullYear()-1) {

        lastCount++

    };

    if (cDate.getFullYear() === dateVal.getFullYear()) {

        counter++

    };

    cDate.setDate(cDate.getDate() + 28);

};

if (counter == 0) {

    year -= 1;

    counter = lastCount;

};

const id = (parseFloat(year.toString().substring(2, 4)) * 100) + counter

return id;

};
https://nwy-tiles-api.prod.newaydata.com/tiles/9/255/173.png?path={airac}/aero/latest https://nwy-tiles-api.prod.newaydata.com/tiles/9/255/173.png?path={airac}/aero/latest
the {airac} needs to be replaced by the above calculated string, which currently will be “2105”.
That’s how we ensure the smooth switch from one airac to another with out intermediate tiles showing up.
Can you check that code in, i´ll be happy to test it today in the evening.
Btw: where are you from, maybe we could write in german too 😊
Von: Chris @.>
Gesendet: Sonntag, 6. Juni 2021 10:39
An: Christian1984/vfrmap-for-vr @.>
Cc: Oliver Vorderegger @.>; Author @.>
Betreff: Re: [Christian1984/vfrmap-for-vr] Usage of OFM Tiles (#18)
Wow, that's awesome :-) Love OFM. I used it a lot when I learned flying on VATSIM on the "flatscreen"!!! So, yeah, I'd love to add it to FSKneeboard.
The TileLayers are defined in maps.js:210ff. - All the data is currently pulled from public APIs.
I see two options using OFM tiles:
Option 1: Download them and put them in a local folder inside the FSKneeboard server's directory. Say /maps/ofmtiles for example. Then the local webserver (which is there already anyways) could simply server them. That would require the user, however, to download the latest map tiles manually.
Option 2: Simply refer to a public API on your server. That way we could always serve the latest and most up to date tiles that you publish on your OFM project page anyways. That would be awesome, but would obviously create some server load on your end...
Let me know what you think is the best approach!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Christian1984/vfrmap-for-vr/issues/18#issuecomment-855362088 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AC54AY5FKFSS663JY4GARZTTRMX2ZANCNFSM456XB6LQ .  https://github.com/notifications/beacon/AC54AY647Q7T5XFG6ITZUVTTRMX2ZA5CNFSM456XB6L2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGL54UKA.gif

neway data AG
Landstrasse 105 | 9490 Vaduz | Fürstentum Liechtenstein
https://storage.googleapis.com/storage.newaydata.com/email/cube.JPG

Yes, I'm German, too! If you like, we can discuss details in german via Discord!? I have launched a new FSKneeboard-Discord-Server the other day. You can find the invite at https://discord.fskneeboard.com and we have a dedicated german channel over there :-)

@ovord Can you please share some information on the license implications of using OFM tiles in FSKneeboard? What license is the tile data published under?

servus Chris,
das läuft unter der OFM Gerneral Users License: https://www.openflightmaps.org/live/downloads/20150306-GUL.pdf
LG

Really nice, Oliver :-)
Ich würde in der Attributions-Section im Readme dann https://www.openflightmaps.org/ verlinken. Passt dir das so?

sehr cool, testen ich will!

Sehr gern! Ich kann dir ne Preview-Version schicken. Magst du mir mal eine E-Mail an<EMAIL_ADDRESS>von einer Adresse schicken, an die ich das senden kann? Oder du kommst in den Discord :-)

hi chris, hast mir schon mail geschrieben? nix gefunden :(

Hab ich!  Ich hab dir dann am 11.06. ne Nachricht per Discord geschickt (mit nem Dropbox-Link) :-) Schau mal, ob die angekommen ist!

Ahja, jetzt seh ichs, ich werds gleich mal testen heute 😉
thx
Von: Chris @.>
Gesendet: Samstag, 19. Juni 2021 12:39
An: Christian1984/vfrmap-for-vr @.>
Cc: Oliver Vorderegger @.>; Mention @.>
Betreff: Re: [Christian1984/vfrmap-for-vr] Usage of OFM Tiles (#18)
Hab ich!  Ich hab dir dann am 11.06. ne Nachricht per Discord geschickt (mit nem Dropbox-Link) :-) Schau mal, ob die angekommen ist!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Christian1984/vfrmap-for-vr/issues/18#issuecomment-864388538 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AC54AY2GRERFVUCLLUSFJDLTTRXTVANCNFSM456XB6LQ .  https://github.com/notifications/beacon/AC54AYZY5S7BAKE4CTKFJ3LTTRXTVA5CNFSM456XB6L2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGOCYLOQ.gif

neway data AG
Landstrasse 105 | 9490 Vaduz | Fürstentum Liechtenstein
https://storage.googleapis.com/storage.newaydata.com/email/cube.JPG

hab gebuildet und installiert, aber jein ofm 😟
sent from mobile, please excuse typos and autocorrection mistakes.

From: Chris @.>
Sent: Saturday, June 19, 2021 12:38:50 PM
To: Christian1984/vfrmap-for-vr @.>
Cc: Oliver Vorderegger @.>; Mention @.>
Subject: Re: [Christian1984/vfrmap-for-vr] Usage of OFM Tiles (#18)
Hab ich!  Ich hab dir dann am 11.06. ne Nachricht per Discord geschickt (mit nem Dropbox-Link) :-) Schau mal, ob die angekommen ist!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Christian1984/vfrmap-for-vr/issues/18#issuecomment-864388538, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC54AY2GRERFVUCLLUSFJDLTTRXTVANCNFSM456XB6LQ.

neway data AG
Landstrasse 105 | 9490 Vaduz | Fürstentum Liechtenstein
[https://storage.googleapis.com/storage.newaydata.com/email/cube.JPG]

Oliver Vorderegger
+436649254114
@.***
neway data AG
Landstrasse 105 | 9490 Vaduz | Fürstentum Liechtenstein
[https://storage.googleapis.com/storage.newaydata.com/email/cube.JPG]

Also wenn du das Repo clonen und selber bauen willst, dann musst du den Branch post-1-3-0 auschecken. OFM ist im master noch nicht drin. Der master ist immer auf dem Stand des letzten Releases...
Ansonsten benutz doch einfach den server und das Panel aus dem zip-File. Das sind ja schon die gebauten Binaries der Preview.
Wichtig ist, dass du beides, Server und Panel aus dem Preview-Zip benutzt.

so einfach 😀, jetzt hats geklappt 👍. sieht super aus!
sent from mobile, please excuse typos and autocorrection mistakes.

From: Chris @.>
Sent: Sunday, June 20, 2021 2:02:26 PM
To: Christian1984/vfrmap-for-vr @.>
Cc: Oliver Vorderegger @.>; Mention @.>
Subject: Re: [Christian1984/vfrmap-for-vr] Usage of OFM Tiles (#18)
Also wenn du das Repo clonen und selber bauen willst, dann musst du den Branch post-1-3-0 auschecken. OFM ist im master noch nicht drin. Der master ist immer auf dem Stand des letzten Releases...
Ansonsten benutz doch einfach den server und das Panel aus dem zip-File. Das sind ja schon die gebauten Binaries der Preview.
Wichtig ist, dass du beides, Server und Panel aus dem Preview-Zip benutzt.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Christian1984/vfrmap-for-vr/issues/18#issuecomment-864543419, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC54AY7EILADB3SBU2SWTV3TTXKFFANCNFSM456XB6LQ.

neway data AG
Landstrasse 105 | 9490 Vaduz | Fürstentum Liechtenstein
[https://storage.googleapis.com/storage.newaydata.com/email/cube.JPG]

Oliver Vorderegger
+436649254114
@.***
neway data AG
Landstrasse 105 | 9490 Vaduz | Fürstentum Liechtenstein
[https://storage.googleapis.com/storage.newaydata.com/email/cube.JPG]

done, will be released with v1.4


hangs on android when signing up for account

I am trying to use this plugin and it works fine in the web, I don't know about ios because I am not using that but in android I can sign in a user but when I try to sign up it just keeps showing the loading progress bar and never actually signs the user up. if you have any advice of something I am maybe doing wrong that would be great.
thank you for your time

update, it works in an actual device just not in the emulator

Ok i was testing on a device too, ill see if i can figure out why the emulator doesnt work. Does it require google play services to be available?
Does it actually signup the user on the backend though? Also are you using the latest from the repo? I made some changes to the sign up process

Im pretty sure my emulator has google play services in it, it does not sign up the user on the backend.  Im using the package from pub.dev, im very new to flutter

For reference you can install pub packages from git too. But I can send out a new update. I’ll do some tests and see if I can reproduce this


mockRejectedValue is not a sugar function to mockImplementation(() => Promise.reject(value))

you are using the latest version of Jest: Yes
try re-installing your node_modules folder: Yes
run Jest once with --no-cache to see if that fixes the problem you are experiencing. : Yes

Do you want to request a feature or report a bug?
bug
What is the current behavior?
In the documentation for mockRejectedValue, it states that it is a sugar function to mockImplementation(() => Promise.reject(value)), however as can be seen in the repl.it demo below, it is not. mockRejectedValue assumes that the rejection is handled immediately in the current event loop cycle, if it is not, it will cause the test to fail even though the rejection is handled in later cycles.
Repro
repl.it demo. Although the documentation say it's only available in 22.2.0+ and repl.it's jest version is 22.1.2, I have tried it locally with 22.4.2 and I am seeing the same issue.
What is the expected behavior?
Follow what the documentation states, "Simple sugar function for: jest.fn().mockImplementationOnce(() => Promise.reject(value));".
Please provide your exact Jest configuration
{
  "testRegex": ".*-test\\.js$",
  "testEnvironment": "node"
}

Run npx envinfo --preset jest in your project directory and paste the
results here
System:
    OS: Windows 10
    CPU: x64 Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
  Binaries:
    Node: 9.4.0
    Yarn: 1.3.2
    npm: 5.6.0

The docs are wrong here, this was changed in https://github.com/facebook/jest/pull/5720 which hasn't been released yet
Fixed in the above PR, sorry for the confusion @rongduan-zhu!

Cool! Thank you @rickhanlonii


home-assistant: 0.62.1 -> 0.63

Motivation for this change
https://home-assistant.io/blog/2018/02/10/release-63/
Things done

[z] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

/cc @FRidh

Success on x86_64-linux (full log)
Partial log (click to expand)
tests/components/test_init.py ............                               [ 71%]
tests/components/test_introduction.py .                                  [ 72%]
tests/components/test_logger.py ....                                     [ 75%]
tests/components/test_script.py .....                                    [ 78%]
tests/components/test_shell_command.py ......                            [ 81%]
tests/components/test_system_log.py ...............                      [ 91%]
tests/components/test_websocket_api.py ..............                    [100%]

========================= 160 passed in 11.41 seconds ==========================
/nix/store/g2s18b2d0g1pmq0assinksb238xns151-homeassistant-0.63

Success on aarch64-linux (full log)
Partial log (click to expand)
tests/components/test_init.py ............                               [ 71%]
tests/components/test_introduction.py .                                  [ 72%]
tests/components/test_logger.py ....                                     [ 75%]
tests/components/test_script.py .....                                    [ 78%]
tests/components/test_shell_command.py ......                            [ 81%]
tests/components/test_system_log.py ...............                      [ 91%]
tests/components/test_websocket_api.py ..............                    [100%]

========================= 160 passed in 26.75 seconds ==========================
/nix/store/b95m1z5pb4l6280hbypiq8lry4rzvzga-homeassistant-0.63


Deleted dependency detected

I'm a Cyber Security researcher and developer of PackjGuard [1] to address open-source software supply chain attacks.
Issue
During my research, I found that this repo is vulnerable to attack due to deleted dependency from the public PyPI registry.
Details
Specifically, file requirements.txt lists hubspain as one of the dependencies. However, it has been deleted from public PyPI. As such, an external bad actor can claim that name and register a malicious package, which will be then installed with pip install command, resulting in arbitrary remote code execution.
Impact
Not only your apps/services using https://github.com/flowese/CreateHub-Imagine repo code are vulnerable to this attack, but the users of your open-source Github repo could also fall victim.
You could read more about such attacks here<EMAIL_ADDRESS>Remediation
Please manually register a placeholder hubspain package on PyPI immediately or remove hubspain dependency from requirements.txt to fix this vulnerability.
To automatically fix such issues in future, please install PackjGuard Github app [1].
Thanks!

PackjGuard is a Github app that monitors your repos 24x7, detects vulnerable/malicious/risky open-source dependencies, and creates pull requests for auto remediation: https://github.com/marketplace/packjguard

Sorry about this false positive.


Logic apps Visual Studio 2022?

Can these instructions be updated to include the latest version of VS ?   Cloud explore is gone, inherited some logic apps and need to pull them into the fold.. TY

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

ID: 2650bd13-3b48-c09d-e0bc-bcad6605a4b7
Version Independent ID: 644aabda-c85b-88b9-deb8-4cb38b49ad4f
Content: Edit and manage logic apps using Visual Studio - Azure Logic Apps
Content Source: articles/logic-apps/manage-logic-apps-with-visual-studio.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

Hi @Mrachek,
Thank you for your feedback! The doc still accurately says that the Azure Logic Apps Tools extension is currently unavailable for Visual Studio 2022. Please add your vote to the customer feedback item here: Azure Logic Apps Tools does not Support Visual Studio 2022

@Mrachek
Thanks for your feedback! We will investigate and update as appropriate.

@RamanathanChinnappan-MSFT and @JananiRamesh-MSFT: I already replied that the doc is still accurate and directed the customer to vote on adding Azure Logic Apps Tools extension support to Visual Studio 2022. So, I'll close this issue now.
#please-close

#assign:ecfan


Firebase Auth Setup

Notes 📝

[x] Setup interfaces with Firebase auth, client-side
[x] Added base Login, Register, and Home component for testing. (Navigation with Navbar component <= should be refactored)
[x] Added Firebase base configuration for auth and Firestore
[x] Fixed typo in .gitignore files
[x] Added .env.template to setup local environment
[x] Fixed deprecated packages in api/

⚠

Must run yarn in client and API directories and setup local environment variables

lgtm


[python] Support ingest of H5AD dense X as SOMA sparse X

Issue and/or context: Some very common and very small datasets -- e.g. the ubiquitious pbmc3k_processed -- have their X stored as dense (numpy.ndarray). Ingesting these as dense makes them more awkward to query.

Codecov Report
Patch coverage: 100.00% and no project coverage change

Comparison is base (c571022) 91.25% compared to head (653168c) 91.25%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1061   +/-   ##
=======================================
  Coverage   91.25%   91.25%
=======================================
  Files          30       30
  Lines        2263     2264    +1
=======================================
+ Hits         2065     2066    +1
  Misses        198      198

Flag
Coverage Δ

python
91.25% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

apis/python/src/tiledbsoma/io/ingest.py
84.71% <100.00%> (+0.03%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Product of count of bits of each element in array is added

Have you read the Contributing Guidelines on Pull Requests?
(Yes)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(#256 )

Please review sir @HarshCasper @iamrajiv @ankitaggarwal23 @atarax665 @gat786

All changes done sir @iamrajiv

Changes done sir @atarax665


OpenAtom crashes during launch at startup on BlueWaters using master charm (again)

Original issue: https://charm.cs.illinois.edu/redmine/issues/1630

OpenAtom ran fine on 75ea9d902febb0552170ab61ff79d14588494d7c
But crashes during application startup with current master when run on 32 nodes using water_256M_70Ry.
Currently bisecting, time consuming due to the ridiculous (40 minutes+) time to build charm on bluewaters.

Original date: 2017-07-14 18:08:40

Edison dies with a topology error at higher node counts.  Unclear if this is actually a related bug, or a different issue. 32 nodes works, 45 nodes crashes thusly:
------------- Processor 0 Exiting: Called CmiAbort ------------
Reason: ST_RecursivePartition:: Increase bitset size to match size of largest to
pology dimension
------------- Processor 8 Exiting: Called CmiAbort ------------
Reason: ST_RecursivePartition:: Increase bitset size to match size of largest to
pology dimension
... etc

Original date: 2017-07-14 18:10:08

That wouldn't happen on Blue Waters.

Original date: 2017-07-14 18:23:45

Opened new issue for that here: https://charm.cs.illinois.edu/redmine/issues/1632
Fix coming soon.

Original date: 2017-07-14 22:00:02

Like I said, these shouldn't be related at all, since the error on Edison would not appear on Blue Waters.

Original date: 2017-07-14 22:06:04

The relationship linkage is their discovery - a link in the comments here doesn't indicate over there where #1632 came from. Not meant to indicate anything more

Original date: 2017-07-14 22:06:33

Also, one hopes that fixing #1632 will make debugging this issue faster

Original date: 2017-07-14 22:08:47

Sounds reasonable, I agree.

Original date: 2017-07-17 04:07:30

I built latest charm master branch on BW (up to 58f6f16077535e24f5c474cc1ee7ea8aaa059bb2: Bug #1632: ST_RecursivePartition crashes with large node counts without topo info)
with ./build charm++ gni-crayxe smp --enable-error-checking -O0 -g
And built OpenAtom against this, and ran water_256M_70Ry like this:
./tidy water
aprun -n 256 -N 4 -d 8 ~/openatom/build-O0-g/OpenAtom cpaimd_config.1024.smart.topo  water.input +ppn 7 +commap 0,8,16,24 +pemap 1-7,9-15,17-23,25-31
and it ran without issues.
I then ran with 32 nodes and got:
Before control_new_mapping_function user mem 8.369904 MB
Before make_rho_runs user mem 8.369904 MB
tempering output dir TEMPER_OUT
Temperature exchange frequency set to 1000
TemperController for Tempers 1 and beads 1
expected energies 1
Initializing TopoManager
After Init topoManager user mem 8.370239 MB
Choose a larger Gstates_per_pe than 1 such that { (no. of processors [896] / no. of Instances [1]) / (no. of states [1024] / Gstates_per_pe [1]) } is > 0
OpenAtom: ../src_charm_driver/main/cpaimd.C:523: main::main(CkArgMsg*): Assertion `pm > 0' failed.
_pmiu_daemon(SIGCHLD): [NID 08508] [c14-9c0s1n0] [Sun Jul 16 22:31:25 2017] PE RANK 0 exit signal Aborted
[NID 08508] 2017-07-16 22:31:26 Apid 59517080: initiated application termination
Application 59517080 exit codes: 134
Application 59517080 exit signals: Killed
Application 59517080 resources: utime ~66s, stime ~55s, Rss ~62192, inblocks ~1183088, outblocks ~3600973

But this just looks like a ran with incorrect input.

Original date: 2017-07-17 14:41:14

I managed to halfway automate the bisect process and have reproduced Juan's finding.  Binaries produced by current charm master and openatom master do not have this bug.  Best guess is that there must have been some residual cruft in the build tree used in the original process. I have started building a test of a fresh build using the charm version implicated in the original bug, in the hopes of trying to learn a bit more about the original issue.  Regardless, I'm rejecting this redmine issue, as it is not reproducible.

Original date: 2017-07-18 15:43:58

Run of openatom build with charm version that produced the original failure v6.8.0-beta1-295-g8b554d0, now runs to completion. Mystery unsolved, but unlikely to learn anything useful in further digging.


Boolean value in file is not read properly

Hello,
Another problem I am facing now is that I am reading a table with boolean values (true and false). I know for sure from reading in the database with a php interface that the values in the table seem to be correct.
However, when I am extracting these values with mksqlite with a call like follows
    res = mksqlite(['select ts, onoffstate from ' tableIdTmp{j} ' where ...']);

all the fields onoffstate in the structure res are empty instead of taking the true or false value.
I was using mksqlite 1.14 on MAC with matlab 2014b and also tried on Windows 7 with matlab 2014a and mksqlite 2.0
Any ideas why this happens ?
Best
Tomasz

Hi Tomasz,
seems you try to open a non-sqlite database? sqlite knows no boolean type, just INTEGER, TEXT, BLOB and REAL.
But you may easily cast it to an integer, that should work:
res = mksqlite(['select ts, CAST(onoffstate AS INTEGER) AS onoffstate from ' tableIdTmp{j} ' where ...']);
The "AS onoffstate" is necessary, bcause sqlite would return the result with column name "CAST(onoffstate..." which is not a proper MATLAB variable syntax, so mksqlite will change it to something like "CAST_onoffstate_...", not what you want.
Best
Andreas

Hi,
It was a sqlite database and you were right. Just made a silly mistake.
Thx for the help
Tomasz
---- Andreas Martin a écrit ----
Hi Tomasz,
seems you try to open a non-sqlite database? sqlite knows no boolean type, just INTEGER, TEXT, BLOB and REAL.
But you may easily cast it to an integer, that should work:
res = mksqlite(['select ts, CAST(onoffstate AS INTEGER) AS onoffstate from ' tableIdTmp{j} ' where ...']);
The "AS onoffstate" is necessary, bcause sqlite would return the result with column name "CAST(onoffstate..." which is not a proper MATLAB variable syntax, so mksqlite will change it to something like "CAST_onoffstate_...", not what you want.
Best
Andreas
—
Reply to this email directly or view it on GitHubhttps://github.com/AndreasMartin72/mksqlite/issues/2#issuecomment-124215665.


workflows: mention new ocrd_wrap and ocrd_segment processors

In addition to #104 IMHO the following new processors should at least be mentioned (if not recommended) in the workflow guide:

ocrd-preprocess-image along with potential / example tools (replacing ocrd-olena-binarize, replacing ocrd-im6convert, simulating textcleaner and other IM scripts)
ocrd-skimage-normalize
ocrd-skimage-denoise-raw
ocrd-skimage-binarize
ocrd-skimage-denoise
ocrd-segment-replace-original (to re-base PAGE coordinates to "new original")

solved by https://github.com/OCR-D/ocrd-website/pull/121


can not create-react-app

Describe the bug
I crreate react app along with the document, but i can't go through the first step.
Environment
macbook pro m4,
nodejs: 22.12.0
npm: 10.9.0

Steps to reproduce
I have tried to add force flag to the command, although it can create the folder, but it can not start.
ig: npx --legacy-peer-deps create-react-app
The start error screenshot is:

Then, i try to npm audit fix --force and  remove react dependencies and reinstall react with npm install react@18 react-dom@18,  it finally works.
But i think it maybe has some potential issue.   I wonder what's the right way to run create-react-app?

Same error here. Using node v22.12.0 and npx 10.9.0, with nvm 0.40.1. On Mac OS 15.2 with M1 processor.

This is a duplicate of #13721.

Had the same issue when creating a typescript app. I ran the npm install manually with some updated package versions:
npm install --no-audit --save \
<EMAIL_ADDRESS>\
<EMAIL_ADDRESS>\
<EMAIL_ADDRESS>\
<EMAIL_ADDRESS>\
<EMAIL_ADDRESS>\
<EMAIL_ADDRESS>\
<EMAIL_ADDRESS>\
<EMAIL_ADDRESS>\
<EMAIL_ADDRESS>
typescript 5.x does not work though because the latest react-scripts 5.0.1 has deps on typescript < 5.x

I too faced the same error and i have resolved it by adding this command "npm install web-vitals"

This problem seems to have been happening for weeks. I don't know why it still hasn't been fixed, but based on the issue here:
https://github.com/facebook/react/issues/31701
Using the following command could be a temporary fix if it's really urgent:
yarn create react-app module

Did not solve npx create-react-app app_name but solved it by manually changing the @testing-library/react to version 16.1.0 works for me. Seems like it's the compatible version with react 19
rm -rf node_modules package-lock.json
"dependencies": {
    "@testing-library/react": "^16.1.0",
    "cra-template": "1.2.0",
    "react": "^19.0.0",
    "react-dom": "^19.0.0",
    "react-scripts": "5.0.1",
  },

npm install
no errors on this

There are two solutions to the compatibility issue caused by using react19 version.

-> First remove the package lock file and node_modules
rm package-lock.json
rm -rf node_modules
-> Change the react deps from "^19.0.0" to "^18.0.0"
"react": "^18.0.0",
"react-dom": "^18.0.0",
->
npm i
->
npm install --save web-vitals
npm install --save-dev @testing-library/jest-dom @testing-library/react @testing-library/user-event

yarn create react-app my-app

rm package-lock.json
rm -rf node_modules
you are able to use  create-react-app but since it is a legacy code it will give you many errors on intalling and initializing the app.
After the error do cd nameYouCreated for the create react app.
Then inside the created-react-app you can do npm i and npm init.  so you can continue the Process.
This code is too old and non-compatible with the versions of  React that we have available. Unfortunately older version of react that would be compatible are no longer available,

Guys no point trying to resolve this because its not really maintained. Not worth it. Above solutions did not work for me. Just use vite create-react-ts - https://vite.dev/guide/

I have the same issue
Installing template dependencies using npm...
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving<EMAIL_ADDRESS>npm error Found<EMAIL_ADDRESS>npm error node_modules/react
npm error<EMAIL_ADDRESS>from the root project
npm error
npm error Could not resolve dependency:
npm error peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm error node_modules/@testing-library/react
npm error<EMAIL_ADDRESS>from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error C:\Users\zangn\AppData\Local\npm-cache_logs\2024-12-25T07_28_48_384Z-eresolve-report.txt
npm error A complete log of this run can be found in: C:\Users\zangn\AppData\Local\npm-cache_logs\2024-12-25T07_28_48_384Z-debug-0.log
npm install --no-audit --save<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>failed
PS E:\src\frontend-movie4>

Wrong repository, the problem is not for React Scripts, is Testing Library for React: https://github.com/testing-library/react-testing-library/issues/1372


Support reorder between sections

Adds support for showing sections and reordering rows between sections

It's still giving a crash when i drag a cell from section 1 to 0
Invalid update: invalid number of rows in section 0.  The number of rows contained in an existing section after the update (5) must be equal to the number of rows contained in that section before the update (5), plus or minus the number of rows inserted or deleted from that section (1 inserted, 0 deleted) and plus or minus the number of rows moved into or out of that section (0 moved in, 0 moved out).

It's been long time ago I used it and tested it.
I don't work on that app anymore.
So you can cancel my PR probably.


Switched to official docker-engine API

Hi !
This shall solve issues with docker compose discussed in bug #59

This is a good idea.  It would pay off to no longer be held back by the samalba library.

Hi.
As docker switched on golang I think third party go binding are going to be deprecated. That's the reason why I decided to integrate the official binding.
For your bug I didn't checked the dockerfile only the tests and the Travis.
I'll check tonight but maybe this is due to the version of golang or godep used in the dockerfile

Try change the first line and replace 1.4.1 by 1.6.2

Ignore my above error.  The golang version change didn't fix it, but the master branch Dockerfile also doesn't build for me.

@aacebedo why add the vendor folder?  can these dependencies not be build as godeps?

Godep is a third party tool created to cope with the weak dependency system of golang until 1.6. This version introduced a new standard solution to deal with dependencies which is the vendor folder. The latest version of Godep I used to rebuild the dependencies created the vendor folder because I think they decided to make their tool compatible with this new mechanism

Corrected the dockerfile @james-nesbitt

LGTM


Realm: MultiAffineAccessors are not thread safe

If MultiAffineAccessors are not marked as a constant variable, they implement a caching algorithm that remembers the last accessed affine piece. This mechanism is not thread-safe and using the accessors in OpenMP parallelized loops may lead to undefined behavior.
The current known solution is to mark the accessors as firstprivate in the OpenMP loop header.
Probably a more robust solution is required.

I was looking at this code tonight and there is a related bug: the member methods of Realm::MultiAffineAccessor (e.g. read and write) are marked as REALM_CUDA_HD, but the data structure that is used for the cache is not (to the best of my ability to tell) placed in zero-copy memory or copied down to the device when using the accessor on the device.

An accessor can be copied by value (e.g. by passing it as an argument to a CUDA kernel launch) and the copy will have a cache that is now distinct from the original accessor's cache.  There is no global storage for the cache and there should be no problems with device accessors unless somebody puts one in shared memory.
@mariodirenzo we can make the cpu-side one thread safe, but it will add locking overhead on every use, which seems bad.  I can add another template parameter to MultiAffineAccessor, but we'd need @lightsighter to plumb it through the legion interfaces I think?  I'm not wild about this approach though, because anybody who knows enough about the problem to opt for the slower-but-thread-safe version already knows what they need to know to avoid the problem (e.g. firstprivate for openmp).

If it is complicated, I am ok with keeping things as they are. However, it would be nice to have some kind of guards that check if someone is using the  MultiAffineAccessor in openMP loops in an unsafe way.
Another option is to give a template parameter that deactivates the cache system by declaring the Realm accessor as constant.  If you need to access a few points in the sparse compact instance, the performance penalty might be small.

Another option is to give a template parameter that deactivates the cache system by declaring the Realm accessor as constant.

I think that is exactly what @streichler already proposed here:

I can add another template parameter to MultiAffineAccessor...  I'm not wild about this approach though, because anybody who knows enough about the problem to opt for the slower-but-thread-safe version already knows what they need to know to avoid the problem (e.g. firstprivate for openmp).

I'm not a big fan of that either for the reasons above.
Let me float an alternative solution: @streichler can we just remove the cache from the MultiAffineAccessor? It seems like the common case where it would be valuable would be in the case where users are accessing all the elements in one piece before moving onto the next piece. If they're doing that, they really shouldn't be using the MultiAffineAccessor at all in the first place anyway as they should be using a PieceIterator to iterate over the pieces, and making normal AffineAccessors for each piece.
I also think the lack of thread safety is problematic for the GPU in addition to the OpenMP case as many threads in the same thread block could be using the same MultiAffineAccessor in the parameter space of the kernel at the same time and racing on the cache there as well. Removing the cache would just fix all those problems.
I also think just making accessors "stateless" and thread-safe feels better to me from a design principle standpoint.

I suppose you could have const and non-const versions of all the methods with the non-const methods using the cache and the const ones ignoring it. The entire object itself though would need to be marked const though in order to use it. Legion would almost certainly need another template parameter to control that.

did you have performance data for your specific gpu kernels with/without the cache?

I do not have performance data right now but I can get them in the next few days

I believe we have thread safety on the device because each GPU thread has its own copy of the accessor.

That's definitely not true. Here's a counter example:
#include <cstdio>
#include "cuda_runtime.h"

class Accessor {
public:
  __device__ __forceinline__
  void access(void)
  {
    printf("Thread %d of block %d reading accessor %p with value %d\n",
      threadIdx.x, blockIdx.x, this, val);
  }
public:
  int val;
};

__global__
void kernel(Accessor accessor)
{
  accessor.access();
}

int main(void)
{
  Accessor a;
  a.val = 4;

  kernel<<<10,1>>>(a);
  cudaDeviceSynchronize();

  return 0;
}

And the output:
Thread 0 of block 3 reading accessor 0x7f3405fffd1c with value 4
Thread 0 of block 9 reading accessor 0x7f3405fffd1c with value 4
Thread 0 of block 0 reading accessor 0x7f3405fffd1c with value 4
Thread 0 of block 6 reading accessor 0x7f3405fffd1c with value 4
Thread 0 of block 4 reading accessor 0x7f3405fffd1c with value 4
Thread 0 of block 2 reading accessor 0x7f3405fffd1c with value 4
Thread 0 of block 8 reading accessor 0x7f3405fffd1c with value 4
Thread 0 of block 1 reading accessor 0x7f3405fffd1c with value 4
Thread 0 of block 7 reading accessor 0x7f3405fffd1c with value 4
Thread 0 of block 5 reading accessor 0x7f3405fffd1c with value 4
...

All the threads see the same accessor in the parameter space of the kernel and they can all dispatch non-const methods on it. To be clear, I think it's ridiculous that CUDA lets anything non-const go in the parameter space of the kernel, but that is the way that is seems to be at the moment.
We also have a related issue: the Legion FieldAccessor instantiations with MultiAffineAccessor are currently marking those accessors as mutable (I don't remember why this is the case, but I remember it was for something that @mariodirenzo wanted). So you can pass in a const FieldAccessor<...., MultiAffineAcessor<...>> as an argument to a kernel and the compiler will happily put that in the global parameter space of the kernel shared by all the threads in the kernel. When they use the accessor though, they'll be invoking the non-const member methods and racing on the cache. At a minimum I think I will probably get rid of all those mutable annotations on the Legion side unless @mariodirenzo gives me a reason not to, which will disable the cache for all uses of the MultiAffineAccessor in Legion.
Curious to see what the performance data shows as well.

Here's an example: https://godbolt.org/#z:OYLghAFBqd5QCxAYwPYBMCmBRdBLAF1QCcAaPECAMzwBtMA7AQwFtMQByARg9KtQYEAysib0QXACx8BBAKoBnTAAUAHpwAMvAFYTStJg1DIAruiakl9ZATwDKjdAGFUtEywYgA7KUcAZPAZMADl3ACNMYgkuUgAHVAVCOwYXNw9vOISkgQCg0JYIqK4Yq0wbZKECJmICVPdPH1LygUrqglyQ8MjoyyqauvTGvvbAzoLu4oBKS1QTYmR2DmQDBQUAagBBZAXVkjWAUi8AIX2NDbW12JMw2jxkEFPzi7XAgjXVfYBmE7PntYB9f5YABud0wgLWwNQeHQaxYJiqBEwEFeawAnpMDsd3gcAEwnT4AEXRXyOWMJj0OFO%2BlLOgOAtFQYTEEKhMLWAGtIkFaBAtjsFHsLC9BGsAFSxSaU46PP54KgQAgIYiYJjoACS6FUADpVAciV9iRopb8/msmNr4YjkVwpTTTRdAQo0QwbMrVegFBA7T8nhcJfriRaPvaNlSONNaJwAKy8TwcLSkVCcJxyQnnJz7fFZsmCuYLPGfHikAiaCPTDkgT6fbXVuv1hsANn0nEkcbLSc4vAUIA0JbL0zgsCQaBYsTokXIlFH4/oUQYwO2XFxMRBYIAanhMAB3ADysUYHZotCRxB7EDCHbCgWqaM4xevzGIaN3YW0ZVL3F4o7Ygl3DFoO8E14LAWEMBlFkTfAVXKYFMB7YDfFUMoEUWYtXkwKNENuMJiFvFwsA7AhiDwFh7wjPgDGABRNx3fdDy/GRBBEMR2CkJj5CUNQO10GIDCMFAzAsHCe0gaZUFiWwBAQ7tMI/ZIHAYZxXHqPR/FGfJCj0eJEiklIVPSGIdOyBgOk0iZLDk5oGFafoDM8EorL02yRjyLoil6NoBgczyajM9yJGmPN5jYyMY3bRDkw4NZgnXJwnDWZdtS4bUNDWCBcEIPYsyLSZeE/LRJgrKsawbMq62bLC21IeNEyi7te37YDBxgRAQDXBYpwgGcJ2IYJWEWWL4sS3FktSkDMFBBYQGUAAVAANXx8CIEj0D0fhmNEcR2I2ziVHURDeMs6w9MU5S0h89S3PGDzjL07ztKyPT/JuvQmmc4YHsck6KmGF6tJKT77Lev6NIC20SxVTAYV7MKOFjGqOyiwlJrBNZaO3SIYrihKkpStKMuW7LcSLUg1hcMdesLW18oHYrq1rcqypbDhqtq3h6ssRqCvLFncQiuquyawrpjgs8FMkIA%3D%3D
One thread modifies the accessor and then there's a syncthreads, but you can see in the ptx that the modified value is never written anywhere the other threads can see it before the syncthreads.

We also have a related issue: the Legion FieldAccessor instantiations with MultiAffineAccessor are currently marking those accessors as mutable (I don't remember why this is the case, but I remember it was for something that @mariodirenzo wanted).

One thread modifies the accessor and then there's a syncthreads, but you can see in the ptx that the modified value is never written anywhere the other threads can see it before the syncthreads.

That's pretty insane. The compiler suddenly making copy-on-write copies of arguments is just bonkers.

At that time I was not using padded space and the caching inside the MultiAffineAccessor was helping performance (I can't find the file with the actual numbers). Now I have fewer accesses to the sparse compact instances and I suspect that the benefit of caching is not that large. I'll try to get quantitative measurements though.

Ok, I'll wait to see the performance numbers before switching anything.

HTR performance - 20 iterations using @mariodirenzo supplied test + htr (Develop branch, commit bfcbd9af)
Legion without  'mutable' (commented out in legion.inl) -> 34.176 seconds
Legion with  'mutable' -> 22.015 seconds

Right so we already have marked all the MultiAffineAccessor uses in the templates as mutable for performance (which I'm still not wild about since it's different than other cases). However, that solution is not actually safe if you're going to use the MultiAffineAccessor in a task running on an OpenMP processor. The question is whether we are willing to require users to use firstprivate when using these kinds of accessors (but not other kinds of accessors) when using them with OpenMP processors.

The same HTR tests @mariodirenzo supplied for this shows no performance improvement on CPUs with/without mutable for MultiAffineAccessor. On GPUs there is a performance improvement as described earlier

If the trend that @seemamirch has seen is confirmed for other use cases, one solution could be to avoid (or add a bool template parameter) the mutable keyword for the CPU version of the accessor, making them threadsafe. The GPU version could keep having the mutable Realm accessor

The same HTR tests @mariodirenzo supplied for this shows no performance improvement on CPUs with/without mutable for MultiAffineAccessor

Was that with LOC_PROC or OMP_PROC processors? If the latter, how many threads per processor? How did you guarantee thread safety?

avoid the mutable keyword for the CPU version of the accessor, making them threadsafe. The GPU version could keep having the mutable Realm accessor

That's not actually a safe thing to do for CUDA. The host side representation of the structure needs to be identical to the device side representation. If you don't you can get undefined behavior. Now theoretically mutable shouldn't change the layout so it might be ok. However, I've seen issues with differences between the mutable keyword on the host and device before (e.g. with the Domain class in Legion).

or add a bool template parameter

We would be forcing that template parameter onto all FieldAccessor users for all Realm accessor kinds. That seems overkill to me and overly burdensome on the common case.

OMP_PROC processors, 8 threads per processor. It uses firstprivate for multi affine accessors

Do the tasks linearly walk the memory for the compact-sparse instances or is it random-access look up in the compact sparse instances?

Do the tasks linearly walk the memory for the compact-sparse instances or is it random-access look up in the compact sparse instances?

They linearly walk through the compact-sparse instances


Feature Request: Forge-Snapshots-Analyzer for Comparing Gas Snapshots 🕵

Component
Forge
Describe the feature you would like
Description:
Hi there! While auditing some projects using Foundry, I couldn't find a feature that could be incredibly beneficial to many users. Specifically, I noticed the absence of a way to compare gas snapshots for quickly assessing the overall effects of gas optimizations in test cases.
To fill this gap, I've created some bash scripts that perform this analysis. You can find the code and an overview of the functionality in my repository:
Forge-Snapshots-Analyzer
https://github.com/CarlosAlegreUr/Forge-Snapshots-Analyzer
Proposed Enhancement:
I propose rewriting my analyzer in Rust and integrating it directly into Forge. This would provide a native, efficient way to perform gas comparisons within the framework. Such a feature could help developers to quickly asses the impact of their changes.
Benefits:

Faster insight into gas consumption across different code versions or optimizations.
A unified toolset within Forge for gas analysis, enhancing usability.
Encouraging best practices in optimizing gas consumption.

Next Steps:
I would enjoy contributing with this feature to Forge and would be happy to collaborate on the design and implementation if there's interest.
What are your thoughts?
Looking forward to hearing from you, and happy to provide more details if needed!
Best,
Carlos Alegre Urquizú
Additional context
This is how my analyzer currently displays results

Hi @CarlosAlegreUr thanks for your suggestion
Marking this as resolved as we currently have a forge snapshot --diff <SNAPSHOT_NAME> command to get the difference between different snapshots in percentage terms
forge snapshot --diff
[⠊] Compiling...
No files changed, compilation skipped

Ran 2 tests for test/Counter.t.sol:CounterTest
[PASS] testFuzz_SetNumber(uint256) (runs: 256, μ: 30977, ~: 31288)
[PASS] test_Increment() (gas: 31303)
Suite result: ok. 2 passed; 0 failed; 0 skipped; finished in 11.27ms (10.92ms CPU time)

Ran 1 test suite in 272.87ms (11.27ms CPU time): 2 tests passed, 0 failed, 0 skipped (2 total tests)
testFuzz_SetNumber(uint256) (gas: 0 (0.000%))
test_Increment() (gas: 0 (0.000%))
Overall gas change: 0 (0.000%)


INCOMPLETE: External Metrics & deps

First, let me start by saying that I'm not (yet) a golang developer, so some of this code may not be proper idiomatic go code and overall some of the approach might be incorrect.
This PR is 100% not even close to being ready to merge, but I wanted to go ahead and submit it to open up discussion on the topic and get some feedback early on before I spend a ton of time on it.
I'm aware that I didn't bring up the possibility of submitting a PR for issue #65 before submitting this, so I won't be offended if your not interested in my working on it.
So, without further ado, here's what you'll find below:

I set up project dependencies using dep. Currently the only dependency listed is for the http://github.com/kubernetes-incubator/custom-metrics-apiserver project, which you've already updated to include boilerplate for External Metrics.
I updated the code, as necessary, to correct any build errors related to the movement of several of the types out of the apimachinery namespace and into the metrics namespace.
I updated the return type on NewPrometheusProvider to return the new CustomMetricsProvider interface (the old interface no longer exists in the boilerplate).
I've renamed the prometheusProvider type to customPrometheusProvider provider to distinguish it from the newly created externalPrometheusProvider.
I created an externalPrometheusProvider to implement the ExternalMetricsProvider interface.
I stubbed out some rudimentary work in the externalPrometheusProvider type littered with incomplete work and //TODOs.

If you have the time, I'm interested in hearing your feedback on the work so far before I apply too much more time to it.
Additional Notes
I was having a lot of difficulty building the project "out-of-the-box" due to type confusion issues around vendored dependencies. It seemed like no matter what I did I couldn't squash them all. Switching to dep trivialized all of that and got me up and running.
As a funny aside--the project is using glide.
Glide suggests using godeps instead.
Godeps suggests using dep.
So that's how I wound up with dep.
Cheers!

Oh--I should add this:
I didn't make any updates to the Makefile or .travis.yml files.
I've been building by executing:
dep ensure
go build ./pkg/custom-provider
(I'm working on Windows, so there are some hoops I'll need to jump through to be able to use the Makefile that I haven't jumped through yet.)

Hi!  Thanks for this work!  I've just merged a non-trivial refactor.  One of the things that it does is update the dependencies to Kubernetes 1.11 and switch over to dep :-).  If you can rebase your work on top of the latest master, I'd be happy to review it, and eventually merge.

I may have to scrap this and start over.
I've irreversibly ruined this branch from the looks of things.

I've created PR #79 to replace this one.
It's much cleaner.


Add support for decimal places in currency filter

I know @yyx990803 has little intention to extend these core functionality, but IMHO you either support something fully or you don't at all. So…
Currently the "currency" filter only accepts one argument: the currency symbol. The number of decimal places is fixed as 2. This can cause troubles with several currencies out there whose number of decimal places can be 0 (e.g. Japanese Yen or Vietnamese Dong) or 3 (e.g. Jordanian Dinar).
This commit modifies the filter to accept an extra optional argument: decimal places, which defaults to 2. With this, one can write {{ 1234 | currency '¥' 0 }} to properly display a Yen value. Backward compatibility is maintained.
(Just realized there's a StackOverflow question about this very issue, where the OP was recommended to create a new filter, which is anti-DRY IMO).

I still think this should be a separate filter,  called precision.  It had way more use cases,  and can be chained with this.

I personally don't think precision needs to be a filter – it's a mere toFixed() call after all – or if the users want to, they can create it easily. This commit on the other hand extends what Vue currently has.

Also, decimal places is certainly a currency property and should be implemented so.

I agree to some extent with your argument,  I suppose this is down to how @yyx990803 sees it best implemented.


Update README

Pull Request Test Coverage Report for Build 37

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 16.284%

Totals

Change from base Build 36:
0.0%

Covered Lines:
85

Relevant Lines:
522

💛  - Coveralls


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_7db143c9-562c-41f5-ac3f-454b47939d1b/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_7db143c9-562c-41f5-ac3f-454b47939d1b.git

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

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-05-12-06-44-12 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-05-12-06-44-12

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