Fix API reference

This PR fixes lots of Doxygen broken links and errors that have probably been accumulating over time.

This PR fixes lots of Doxygen broken links and errors that have been probably accumulating over the years.
Here is a summary of the errors and how errors in each category were fixed:

Reference to Concept that doesn't exist in doxygen.
Searching for .../boost/beast/http/message_generator.hpp:56: warning: unable to resolve reference to 'BuffersGenerator' for \\ref command

Generating XML output for class .../boost/libs/beast/include/boost/beast/core/buffers_generator.hpp:139: warning: unable to resolve reference to 'BuffersGenerator' for \ref command

Doxygen does not support concepts. It seems like some people use @interface as a workaround to document concepts, but that requires the toolchain to understand we are doing that.

Doxygen required the fully qualified name at some points.
Parsing file .../boost/libs/beast/include/boost/beast/core/buffers\_range.hpp...../boost/libs/beast/include/boost/beast/core/buffers\_range.hpp:123: warning: unbalanced grouping commands

Searching for .../boost/beast/http/fields.hpp:102: warning: unable to resolve reference to 'field::unknown' for \\ref command

Searching for .../boost/beast/http/fields.hpp:638: warning: @copybrief or @copydoc target 'basic\_fields::equal\_range(boost::beast::http::field) const' not found

Generating docs for compound boost::beast::http::chunk_.../boost/libs/beast/include/boost/beast/websocket/error.hpp:20: warning: unable to resolve reference to 'beast::websocket::stream' for \\ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:287: warning: unable to resolve reference to 'async_base' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:300: warning: unable to resolve reference to 'async_base' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:335: warning: unable to resolve reference to 'complete' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:335: warning: unable to resolve reference to 'complete_now' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:337: warning: unable to resolve reference to 'beast::allocate_stable' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:344: warning: unable to resolve reference to 'complete_now' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:376: warning: unable to resolve reference to 'complete' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:376: warning: unable to resolve reference to 'complete_now' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:378: warning: unable to resolve reference to 'beast::allocate_stable' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:194: warning: unable to resolve reference to 'async_base' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:278: warning: unable to resolve reference to 'async_base' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:427: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:445: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:468: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:484: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:501: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:427: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:445: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:468: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:484: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:501: warning: unable to resolve reference to 'string_view' for \ref command

Maybe there's a way to make Doxygen better understand relative references, but I'm not aware of such an option.

Type has changed in a previous commit.
Searching for .../boost/beast/http/span_body.hpp:24: warning: unable to resolve reference to 'span' for \\ref command

@param name mismatch. Whenever this happened, I've updated the @param from the function declaration instead of updating the declaration.
Generating XML output for class boo.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:235: warning: argument 'ioc' of command @param is not found in the argument list of boost::beast::test::basic_stream< Executor >::basic_stream(ExecutionContext &context, typename std::enable_if< std::is_convertible< ExecutionContext &, net::execution_context & >::value >::type *=0)

.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:235: warning: The following parameter of boost::beast::test::basic_stream::basic_stream(ExecutionContext &context, typename std::enable_if< std::is_convertible< ExecutionContext &, net::execution_context & >::value >::type *=0) is not documented:
parameter 'context'

.../boost/libs/beast/include/boost/beast/core/buffers_generator.hpp:138: warning: argument 'handler' of command @param is not found in the argument list of boost::beast::async_write(AsyncWriteStream &stream, BuffersGenerator generator, CompletionToken &&token) -> typename net::async_result< typename std::decay< CompletionToken >::type, void(error_code, std::size_t)>::return_type

.../boost/libs/beast/include/boost/beast/core/buffers_generator.hpp:138: warning: The following parameter of boost::beast::async_write(AsyncWriteStream &stream, BuffersGenerator generator, CompletionToken &&token) -> typename net::async_result< typename std::decay< CompletionToken >::type, void(error_code, std::size_t)>::return_type is not documented:
parameter 'token'

Macros that weren't being properly replaced in Doxygen. I've adjusted doc/Jamfile to make Doxygen understand these.
.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:439: warning: argument 'handler' of command @param is not found in the argument list of boost::beast::test::basic_stream< Executor >::async_read_some(MutableBufferSequence const &buffers, ReadHandler &&handler BOOST_ASIO_DEFAULT_COMPLETION_TOKENexecutor_type)

.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:439: warning: The following parameter of boost::beast::test::basic_stream::async_read_some(MutableBufferSequence const &buffers, ReadHandler &&handler BOOST_ASIO_DEFAULT_COMPLETION_TOKENexecutor_type) is not documented:
parameter 'BOOST_ASIO_DEFAULT_COMPLETION_TOKEN'

.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:519: warning: argument 'handler' of command @param is not found in the argument list of boost::beast::test::basic_stream< Executor >::async_write_some(ConstBufferSequence const &buffers, WriteHandler &&handler BOOST_ASIO_DEFAULT_COMPLETION_TOKENexecutor_type)

.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:519: warning: The following parameter of boost::beast::test::basic_stream::async_write_some(ConstBufferSequence const &buffers, WriteHandler &&handler BOOST_ASIO_DEFAULT_COMPLETION_TOKENexecutor_type) is not documented:
parameter 'BOOST_ASIO_DEFAULT_COMPLETION_TOKEN'

An extra error we got was
xslt-xsltproc-dir libs/beast/doc/html/beast_HTML.manifest
Error: no ID for constraint linkend: "beast.ref.".

I have no idea where this is coming from.

@evanlenz any idea about that last one?

The 4.8 issue is fixed, merging. Clearly fixing a bunch of things, the last one can be a separate issue.


Update cloud & namespace token logic

Fixes GDT-57

Current dependencies on/for this PR:

main

PR #32   👈

This stack of pull requests is managed by Graphite.

No idea what happened here when I tried to fix merge conflicts -_- maybe the changes got merged separately in a different PR?


R innov10

@dal1234,
Can I merge this pull request? I wrote up a post hyping the next release of RInno because it is more than just a hot fix. 0.1.0 is up on CRAN! :)


WinUI Gallery crashes on start

Describe the bug
When I start the application, nothing happens.  In Windows Application Log the following error is reported:
Faulting application name: WinUIGallery.DesktopWap.exe, version: <IP_ADDRESS>, time stamp: 0x62571213
Faulting module name: CoreMessagingXP.dll, version: 10.0.22621.1000, time stamp: 0xc93a5eeb
Exception code: 0xc000027b
Fault offset: 0x0000000000090e1c
Faulting process id: 0x20b8
Faulting application start time: 0x01d87a56a744175c
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WinUI3ControlsGallery_<IP_ADDRESS>_x64__8wekyb3d8bbwe\WinUIGallery.DesktopWap\WinUIGallery.DesktopWap.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.1_1000.516.2156.0_x64__8wekyb3d8bbwe\CoreMessagingXP.dll
Report Id: 5988c9c5-12f9-465c-bac4-f272b57da6ec
Faulting package full name: Microsoft.WinUI3ControlsGallery_<IP_ADDRESS>_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Steps to reproduce the bug
Install the latest version of WinUI gallery.  Along I have Visual Studio 2022 17.2.3 with Windows App Sdk installed.  Trying to start WinUI gallery causes the app to crash.  I tried repair, reset, uninstall and install, nothing worked.
Expected behavior
The application should start normally.
WinUI version:

[x] WinUI3 / WinAppSDK 1.1

Windows 11 version:

[ ] Windows 11 22H2 (22621)

Device form factor:

[ ] Desktop

I see that the version of the package is 1.3.13.  An update (1.3.14) was released yesterday to resolve this issue. Check the store for the update.


feat: default pod security standards

Describe the feature
Currently we don't allow users to specify any pod security relevant properties (securityContext on pod and container level). By default we should deliver the capsule installation with all the necessary configuration, to run within a common pod security profile environment. Preferably, all components should be executable in a restricted profile.
What would the new user story look like?
Add pod security and ingress options to make the default installation of capsule as secure as possible by default.

Running the manager with the following securityContext (Container):
securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            drop:
            - ALL
          readOnlyRootFilesystem: true
          runAsGroup: 1002
          runAsNonRoot: true
          runAsUser: 1002

Does not allow to run Capsule. It seems the tls-controller needs more privileges. The logs look like this:
{"level":"info","ts":"2023-01-09T11:11:46.239Z","logger":"setup","msg":"Capsule Version v0.1.3 b61db25.dev.dirty"}
{"level":"info","ts":"2023-01-09T11:11:46.239Z","logger":"setup","msg":"Build from: git@github.com:clastix/capsule.git"}
{"level":"info","ts":"2023-01-09T11:11:46.239Z","logger":"setup","msg":"Build date: 2023-01-05T23:52:03"}
{"level":"info","ts":"2023-01-09T11:11:46.239Z","logger":"setup","msg":"Go Version: go1.18.9"}
{"level":"info","ts":"2023-01-09T11:11:46.239Z","logger":"setup","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":"2023-01-09T11:11:46.347Z","logger":"controller-runtime.metrics","msg":"Metrics server is starting to listen","addr":":8080"}
{"level":"info","ts":"2023-01-09T11:11:46.444Z","logger":"controllers.TLS","msg":"Generating new TLS certificate"}
{"level":"error","ts":"2023-01-09T11:12:24.342Z","logger":"controllers.TLS","msg":"cannot update Capsule TLS","error":"client rate limiter Wait returned an error: context canceled","stacktrace":"main.main\n\t/workspace/main.go:192\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"}
{"level":"error","ts":"2023-01-09T11:12:24.343Z","logger":"setup","msg":"unable to reconcile Capsule TLS secret","error":"client rate limiter Wait returned an error: context canceled","stacktrace":"main.main\n\t/workspace/main.go:193\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"}

Pod runs into Crashloopbackoff. I will take a very wild guess, that it has something to do with the random algorithem to generate the certificate. because if the TLS certificate is created correctly, it's not failing (since no update has to be done). My initial assumption was, that we have to deal with a privileged operation on the random device, so requiring following capability:
CAP_SYS_ADMIN
             ....
              * perform privileged [ioctl(2)](https://man7.org/linux/man-pages/man2/ioctl.2.html) operations on the
                /dev/random device (see [random(4)](https://man7.org/linux/man-pages/man4/random.4.html));
             ...

But testing with that capability, didnt really change anything:
securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            add:
            - SYS_ADMIN
            drop:
            - ALL
          readOnlyRootFilesystem: true
          runAsGroup: 1002
          runAsNonRoot: true
          runAsUser: 1002

I will have to dig deeper.

Runs with:
          capabilities:
            add:
            - NET_BROADCAST
            - NET_BIND_SERVICE
            - SYS_CHROOT
            - SYS_PTRACE
            - SYS_BOOT
            - LEASE
            - SETFCAP
            drop:
            - ALL


Update ID verify pass/fail email messages

Update automated pass/fail email messages to include Experian, as relevant. These emails appear as a follow up to the sign up ID verification flow pass/fail messages.

Linking to #1538 #2019

Linking to #2020

Email language here: https://docs.google.com/document/d/1RTKcBR7eFRkrVlxFXtzffWr69vLsuiCj/edit


CI binaries don't work

./zabbix-tree-cli_linux_amd64: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.34' not found (required by ./zabbix-tree-cli_linux_amd64)
./zabbix-tree-cli_linux_amd64: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.33' not found (required by ./zabbix-tree-cli_linux_amd64)
./zabbix-tree-cli_linux_amd64: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by ./zabbix-tree-cli_linux_amd64)
./zabbix-tree-cli_linux_amd64: /lib/x86_64-linux-gnu/libm.so.6: version GLIBC_2.35' not found (required by ./zabbix-tree-cli_linux_amd64)
Seems like there is an issue when building binaries in ci.

Resolved by adding the following flag to the go build command to build static binaries.
--ldflags '-extldflags "-static"'

Source : https://github.com/goccy/go-graphviz/issues/43#issuecomment-1102255205


add refactoring report

I want a number to get bigger every time we port some legacy code to the new service architecture, so I made this :D
refs #1358

Warnings

:warning:

This PR modified package.json, but not package-lock.json - Perhaps you need to run npm install?

:warning:

This PR added helper modules in lib/ but not accompanying tests. Generally helper modules should have their own tests.

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS


Tests are failing after upgrading react native from 0.69.6 to 0.71.0

Description
Hello! After the update I started getting the following errors:
TypeError: Cannot redefine property: performance

      at Object.<anonymous> (node_modules/react-native/jest/setup.js:404:20)

TypeError: Cannot redefine property: window

      at Object.<anonymous> (node_modules/react-native/jest/setup.js:405:15)

Everything works fine if I comment out the appropriate lines in file node_modules/react-native/jest/setup.js:
...
global.__DEV__ = true;

// global.performance = {
//   now: jest.fn(Date.now),
// };

global.regeneratorRuntime = jest.requireActual('regenerator-runtime/runtime');
// global.window = global;

global.requestAnimationFrame = function (callback) {
  return setTimeout(callback, 0);
};
...

React Native Version
0.71.0
Output of npx react-native info
System:
    OS: macOS 13.2.1
    CPU: (8) x64 Apple M1
    Memory: 16.64 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 19.7.0 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 9.5.0 - /usr/local/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.12.0 - /Users/user/.rvm/gems/ruby-2.7.6/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
    Android SDK:
      API Levels: 28, 29, 30, 31, 32, 33
      Build Tools: 29.0.2, 29.0.3, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 33.0.0
      System Images: android-29 | Intel x86 Atom_64, android-31 | Google APIs ARM 64 v8a, android-32 | Google APIs ARM 64 v8a
      Android NDK: Not Found
  IDEs:
    Android Studio: 2022.1 AI-221.6008.13.2211.9619390
    Xcode: 14.2/14C18 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.11 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0
    react-native: 0.71.0 => 0.71.0
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce
Upgrade the RN version
Snack, code example, screenshot, or link to a repository
...
global.__DEV__ = true;

// global.performance = {
//   now: jest.fn(Date.now),
// };

global.regeneratorRuntime = jest.requireActual('regenerator-runtime/runtime');
// global.window = global;

global.requestAnimationFrame = function (callback) {
  return setTimeout(callback, 0);
};
...

I am also getting this error on a clean install of the Ignite boilerplate. My react-native version is 0.70.5.

I rollback to the previous LTS node version (18) and the issue was resolved for me. Probably, the cause was in the latest node version (19). Looks like the jest setup file of RN is not compatible with that version

That was it! Thank you for saving me banging my head against a wall for the next hour. :)
FYI, put something like this in your package.json to prevent your fellow engineers from running into the same problem and to help document it:
"node": ">= 16.0.0 <19.0.0"

Then once React Native supports Node 19+, make sure to update this to reflect the new "max" version of Node.

I have the same problem and also found locking down to 18.15 was the fix.

I've been able to replicate this with the current node 18 LTS version (18.16.0) switching back to 18.15.0 seems to work for now.

Do we have a fix for this issue. This just hit us after upgrading to 18.16.0

Had same issue had to lock our Node to 18.15.0, is a pr incoming for this?

I have this issue too.
node --version = 18.16.0

It looks like this was fixed in Node.js 18.17.0 (and 19.9.0) by https://github.com/nodejs/node/commit/fb90b6b3fbec0da04be9c6560397a190a329dda0. See also https://github.com/nodejs/node/issues/47563.
Could anyone who was seeing the problem confirm it's fixed in the latest 18.x?


Performance: Unwatch some resource types on cluster dashboard and nodes pages

Fixes #6431
This PR exposes forgetType as an action and adds in un-watching of the type as well.
It wires this into the cluster dashboard and nodes page, un-watching Steve types that are used in those pages.
In particular, the cluster dashboard page watches events - which can be changing quite regularly, so if you then change to another page, we still get event messages, even though  we're not showing them anywhere.
On the nodes page, we fetch pods, which can also be changing a lot. These will now also be un-watched. Other pages do use pods, so the downside is that if you are looking at deployments and go to nodes, when you go back, the pods will have to re-load - but this should not block the page, just the time taken for certain columns to have the pod data to be able to update.
Reducing the number of types being actively watched seems like a good thing to do - less load on the backend and less load on the frontend, which has to process the web socket messages for those updates and add then to the store.
To test:

Open up the browser dev tools, go to networking, show web sockets only and select web socket 1 (or whichever is the Steve web scoket)
Go to the cluster dashboard page for a cluster (local or downstream)
Verify that the events table shows data correctly
In dev tools, verify that you see messages to watch events and nodes - they look like { "resourceType": "event", "resourceVersion": "<NUMBER>"}
Go to the projects/namespaces view
In dev tools, verify that you see messages to un-watch events and nodes - they look like { "resourceType": "event", "resourceVersion": "<NUMBER>", "stop": true}
Go back to the cluster dashboard page and verify that the events table loads correctly
Repeat the above for the nodes table, checking that the node and pod resource types are correctly un-watched

@richard-cox Great find - I have updated the PR with a fix - the issue is that there may be resource updates in the pending queue for the type that is being forgotten - the flush timer then processes them after we've removed the type.
Fix is to remove these update messages from the pending queue.


Created a changelog website

Hi, I'm the creator of Openchangelog and a big fan of the whole laravel ecosystem.
I saw that this repo uses the keep a changelog format so I thought I would create a changelog website which you can check out at laravel-frame.openchangelog.com.
It automatically stays in sync with your CHANGELOG.md file.
Would love to have this linked in your README. After all who really wants to read a CHANGELOG.md file when they could have a beautiful, styled website.
The badge I created for the README is just an idea, if you have a different idea or don't want the link in the repo just let me know.

I saw that this repo uses the keep a changelog format

Does it tho? I'm not sure if your site is supposed to add some functionality compared to the .md on GitHub, but maybe it doesn't work because the changelog here doesn't actually follow the format. Currently it looks like a slightly different design and that's it.

@tontonsb if you don't see much value in it, that's fine for me. Just wanted to share it🤷♂

laravel-frame.openchangelog.com.

Why "frame"? Does the sub domain have a character limit? If that's the case, just "laravel" should do fine.
Apart from that, it looks very much like the releases overview page so where's the benefit?

No plans to add atm.


ENH: Add GIfTI output for STC

Wanted to get thoughts from others who may find this feature useful, and insights into possible straightforward ways to implement.
Describe the new feature or enhancement
In an effort to compare/overlay results in fMRI and EEG/MEG, several of us are seeking an easy way to export MNE source results to GIFTI (and potentially NIFTI in the future).  GIFTI would allow other programs (e.g. AFNI, Freesurfer) to then work with source-space data in useful ways (e.g. constrain solutions based on fMRI, make pretty pictures).
Describe your proposed implementation
Add options to mne.SourceSpaces.save( ) or better - a new method .export( ) to allow the export of GIFTI images.  For added convenience, with option for hemisphere, time-window of interest, and overwrite.  Wrapper for nibabel's GIFTI implementation with nuances for writing the relevant data in.
https://nipy.org/nibabel/reference/nibabel.gifti.html
Additional comments
This would be decently useful for folks trying to do EEG-fMRI simultaneous, MEG & fMRI joint analysis, or anyone interested in taking the source estimates from MNE into other softwares (FieldTrip and BrainStorm both have GIFTI imports).

I think it's worth trying. Now we need to see how to handle the fact stc
subsample the high resolution
surfaces of freesurfer. Not sure how to handle this with gifti unless we
upsample creating very
large files.

I'm interesting in joining these discussions, how might I join? I see a standing zoom room in your second link, should I simply join at the appropriate time?

@pmolfese the code is not the best. It relies on the fact that a .stc file is basically a set of concatenated Freesurfer paint (.w) files. With the old MNE-C (2.7.4, ca. 2016), I was using mne_make_movie to extract the surface at the time of interest and export it to a .w file, then freesurfer's mri_surf2vol to convert the .w file to a nifti file.  For gifti I think you could use mri_surf2surf.  To avoid the old code you can set  ftype=w when you save the SourceEstimate in mne-python.

I will add my name to the linked discussion point too. For MNE-nirs I want to move to source reconstruction next and was planning to integrate tightly with nilearn.

@pmolfese why did you prefer to export as GIFTI? I am just curious as Im new to this topic. Some of the fNIRS software exports as NIFTI, and wondered if there was a specific reason for choosing between the two?

@rob-luke - GIFTI mostly comfort in handling source data from other software.  There are programs for converting between NIFTI and GIFTI for sure. I suspect ultimately both would be useful.

@jbteves you pinged me with an email for a status update here -- so far there has been some progress at the nibabel end. I think our plan is basically to wait for nibabel to make SurfaceImage available, then allow something like stc.as_gifti or something to export a SurfaceImage class from our SourceEstimate class in MNE. (Or maybe someday SourceEstimate can be a wrapper for SurfaceImage -- but that would be more work.) In any case, I think any Gifti export would hopefully come from going STC->SurfaceImage (implemented at the MNE end) then SurfaceImage->Gifti (implemented at the nibabel end).
So I think at this point the bottleneck is at the nibabel end, maybe there is some way you could help their effort?
https://nipy.discourse.group/t/preliminary-notes-on-surface-representations/57
https://nipy.discourse.group/t/surface-api-follow-up-meetings/79
https://github.com/nipy/nibabel/pull/1056
Looks like the next meeting is scheduled for 9AM EST Jan 28th if you want to join and discuss!

Alright, thanks for letting me know!

Hi @larsoner, we're pretty eager to get this working and happy to help the nibabel efforts. From the nibabel meeting this morning and our own poking around in the codebase, we have some questions:
for building the geometry we have found the necessary vertices on the decimated surfaces, but we cannot seem to find the triangles necessary to complete the geometry and thus get ready to build the matching GIFTIs for export.
Any help or pointers you could provide on finding the decimated triangles would be much appreciated!
-Pete (and @jbteves).

for building the geometry we have found the necessary vertices on the decimated surfaces, but we cannot seem to find the triangles necessary to complete the geometry and thus get ready to build the matching GIFTIs for export.

Where did you find the decimated vertices? From stc.vertices?
Typically that stc.vertices will correspond to some src[0]['vertno'] from a SourceSpaces instance. If you look at that instance, it should have what you want, e.g.:
>>> import numpy as np
>>> import mne
>>> src = mne.read_source_spaces(mne.datasets.sample.data_path() + '/subjects/sample/bem/sample-oct-6-src.fif')
>>> src[0]['tris'].shape  # high-density
(310810, 3)
>>> src[0]['use_tris'].shape  # subsampled
(8192, 3)
>>> src[0]['vertno'].shape  # vertex numbers
(4098,)
>>> np.array_equal(np.unique(src[0]['use_tris']), np.sort(src[0]['vertno']))
True

Thanks for the response! Sorry, I may be misunderstanding something. We use something like this:
>>> se_rh = mne.read_source_estimate("sub-stc-rh.stc")
>>> right_vert = se_rh.right_verno

To index into the source vertices. However, there are the triangles that represent the faces to create a complete mesh/surface in the high-resolution sample. How might we get those triangles for the low-resolution surface?

We use something like this:

Your stc.rh_vertices should correspond to src[1]['vertno'] in my code above, as long as no vertices were removed during forward computation. Each STC corresponds to some SourceSpaces instance (the one that is preserved in fwd['src'] when it's computed, and inv['src'] when it's computed), and that SourceSpaces instance will (usually) contain both the full-resolution triangulation (src[0]['tris'] for left and src[1]['tris'] for right) and the decimated, low-resolution triangulation (src[0]['use_tris'] and src[1]['use_tris']).
In other words, what I was trying to express with the commands above is "tris is the dense triangulation, use_tris is the decimated one, and the set of vertex numbers in the decimated one match exactly the vertno attribute", and the implied part that is probably the missing link for you is that "the vertno key of the two source space elements should match the stc.vertices", which in code would be something like (for a STC that has no "holes" / missing vertices):
assert np.array_equal(src[0]['vertno'], stc.vertices[0])
assert np.array_equal(src[1]['vertno'], stc.vertices[[1])

@larsoner ah, thanks so much! That makes things much more clear for me. I'll hopefully get some toy code together for this soon.

I imagine some version of src2subsurf (everything before line 50) with a suitable API and naming scheme could live in mne/source_space.py. Are you interested in doing this @jbteves ?
For an API/naming, perhaps mne.source_space.get_decimated_surfaces(src) that returned len(surf_source_spaces) (usually == 2) dicts, each with 'rr' and 'tris' keys would be general enough? The list of dict rather than list of list allows us to later add other entries (e.g., nn) for each surface source space if we realize they're helpful.

Opened #10421 for you to take a look.

Should this be reopened? I think we're still missing the "write to gifti" part.

I think the "partially addresses #XYZ" was misread by GitHub, agreed we should reopen

Thanks! For the GIFTI part should I add another function, or are we wanting to wait for the surface API changes?

I think we want nibabel to do the heavy lifting on that, so we'll need to wait at the MNE end for them to have GIFTI export.
One idea of a backward and forward compatible way for us to get this very easily would be to make BaseSourceEstimate a subclass of nibabel's surface API class. If this works it might be a nice way to transition

Wondering if we can revisit this since it's been over a year. Trying to make sure perfect doesn't stand in the way of progress.
We have a working prototype in our specific use cases that may need to be broadened a bit: https://github.com/nimh-cmn/stc2gii_hack

Agreed I think the nibabel stuff has stalled (?) and in theory as long as we set the API up decently enough we're future compatible with using their code anyway. So +1 for adding a new method stc.export_gifti(fname, subject=None, subjects_dir=None) to the SourceEstimate class. Then maybe we want a mne.source_estimate.read_gifti(fname, subject=None) or so? That way you could do round-trip testing that a save-load round-trip of the Gifti you get the same data, vertices, etc. (or as much information as you can).
Feel free to open a PR to integrate the "hack" (nice name :smile: ) code into MNE

Thanks @larsoner! We'll also need a method to save the decimated surface as GIFTI as well. Any preferences on a name (and namespace) for that?

Maybe if you pass fname='something.gii' we should automatically create 'something-lh.gii' for the decimated left surf and `'something-rh.gii'' with the decimated right hemi surf. Would that be a reasonable workflow? If not feel free to propose something that would work better / make more sense -- the use case isn't totally clear to me, I've never used or thought much about gifti and what it can/can't do as a format...

Ah sorry I'm not typing clear enough even for me!
In Gifti (I believe) there's the geometry surface file that has the shape, and then we overlay the functional data on top of it. These correspond in MNE terms Source Space and STC, respectfully. That functional data (STC here) doesn't have shape, just the nodes that those time data map onto the geometry. For the STCs, I agree with stc.export_gifti( ) for the saving the functional data.
But for the downsampled surfaces / geometry I think we'll need to add a case to mne.write_source_spaces( ) as well. Like a format =  where folks can specify either FIF or GIFTI. Can attempt to get the mne.read_source_space to also read these downsampled surfaces eventually as well.


Invalid literal for int() in AFNISkullStripWorkflow

Running mriqc_0.10.0 (latest singularity container on sherlock):
more crash-20180219-223807-jdurnez-skullstrip.a0-fd7decb7-03b1-4057-8627-3b078d699d4e.txt
Node: workflow_enumerator.anatMRIQCT2w.AFNISkullStripWorkflow.skullstrip
Working directory: /lscratch/jdurnez/workflow_enumerator/anatMRIQCT2w/AFNISkullStripWorkflow/_in_file_..oak..stanford..groups..russpold..data..Psychosis..0.0.2..sub-S9184VMG..anat..sub-S9184VMG_run-1_T2w.nii.
gz/skullstrip

Node inputs:

args = <undefined>
environ = {}
ignore_exception = False
in_file = /lscratch/jdurnez/workflow_enumerator/anatMRIQCT2w/AFNISkullStripWorkflow/_in_file_..oak..stanford..groups..russpold..data..Psychosis..0.0.2..sub-S9184VMG..anat..sub-S9184VMG_run-1_T2w.nii.gz/inu_n4
/sub-S9184VMG_run-1_T2w_conformed_corrected.nii.gz
num_threads = 1
out_file = <undefined>

outputtype = NIFTI_GZ
terminal_output = <undefined>

Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/plugins/multiproc.py", line 51, in run_node
    result['result'] = node.run(updatehash=updatehash)
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 407, in run
    self._run_interface()
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 517, in _run_interface
    self._result = self._run_command(execute)
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 650, in _run_command
    result = self._interface.run()
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/interfaces/base.py", line 1062, in run
    env['DISPLAY'] = config.get_display()
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/utils/config.py", line 283, in get_display
    ndisp = int(sysdisplay.split(':')[-1])
ValueError: invalid literal for int() with base 10: '18.0'

Seems to be a duplicate of https://github.com/poldracklab/mriqc/issues/672

Also - this should be fixed in 0.10.1 since it included nipype update: https://github.com/nipy/nipype/pull/2363

Tried 0.10.2 and problem is indeed fixed.  Thanks !


Improving documentation

Add list of plotting methods to methods that make use of Results classes.
Add more examples to demonstrate how to use plot methods.
Update some functions explainations

AppVeyor is collecting different versions from Pandas in Python3.6 and Python3.7/3.8.

Environment 3.6 uses Pandas 1.1.5
Environment 3.7 and 3.8 uses Pandas 1.2.0

Each version has a diferent style to output the DataFrame. This is why it's raising an error.

AppVeyor is collecting different versions from Pandas in Python3.6 and Python3.7/3.8.

Environment 3.6 uses Pandas 1.1.5
Environment 3.7 and 3.8 uses Pandas 1.2.0

Each version has a diferent style to output the DataFrame. This is why it's raising an error.

AppVeyor is collecting different versions from Pandas in Python3.6 and Python3.7/3.8.
* Environment 3.6 uses Pandas 1.1.5

* Environment 3.7 and 3.8 uses Pandas 1.2.0

Each version has a diferent style to output the DataFrame. This is why it's raising an error.

Pandas 1.2.0 has support to Python 3.7.1 and above. That's why the Python 3.6 test matrix installs Pandas 1.1.5. So I'm thinking about changing the example to add a # doctest: +ELLIPSIS.

AppVeyor is collecting different versions from Pandas in Python3.6 and Python3.7/3.8.
* Environment 3.6 uses Pandas 1.1.5

* Environment 3.7 and 3.8 uses Pandas 1.2.0

Each version has a diferent style to output the DataFrame. This is why it's raising an error.

Pandas 1.2.0 has support to Python 3.7.1 and above. That's why the Python 3.6 test matrix installs Pandas 1.1.5. So I'm thinking about changing the example to add a # doctest: +ELLIPSIS.


[ROCm] Fix num_threads in DeformConv GPU kernel for ROCm

The default value of num threads per group on ROCm is 256. This PR sets correct value of that parameter in DeformConv GPU kernel while running on ROCm.
cc: @fmassa @ezyang @jeffdaily

LGTM


FVM and VSCode integration problem

Hello,
I noticed a problem in FVM and VSCode integration, when I change the environment in VSCode it doesn't change the version and the project has a problem:
Example:
I'm working on VSCode's CMD on version 3.7.5 and I make a global fvm for stable..
It changes to stable but flutter --version remains in 3.7.5 all commands stay in 3.7.5.
If I do the same thing in the default CDM of the operating system, this doesn't happen.
Here's an example video
Video Example:
https://www.youtube.com/watch?v=miHC82YcvJ0

I believe he is fixing the version in the project that was used in flutter create...
If I did flutter create with version 3.7.5 for example, it does not accept the global fvm <new_version>

Did you tried setting "dart.addSdkToTerminalPath": false?

Did you try setting "dart.addSdkToTerminalPath": false?

For some reason, I kept having a path to an older version of Flutter "/Users/myname/fvm/versions/3.3.5" even though I had the 3.10.5 in global. I had never set the 3.3.5 path to my PATH (after checking for hours in .zshrc, .zprofile...)
Outside of VS Code echo $PATH never had the 3.3.5 path. In VS Code It had it.
Using what @quyenlv-unicloud wrote fix the "automatic" set in PATH of the 3.3.5 path.

As @quyenlv-unicloud mentioned flutter vscode extension does add the configured flutterSDK in the settings to the path. That could be causing the issue.

Closing as 3.0 has been released. Check again and reopen the issue if needed.


"Călugărești" is listed in the drop-down menu

Description:
When user writes "Călugărești" the location appears in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Călugărești"

Expected results
The location appears in the drop-down menu as "Călugărești, Alba (Avram Iancu)"


Parameters of type body not being displayed

I have entries with parameters where in equals body, but none of them are being displayed in the HTML output.
Here's an excerpt of the JSON:
    "paths": {
        "/thingy": {
            "post": {
                "summary": "Create new thingys.",
                "tags": [
                    "Thingys",
                    "Back-End Only"
                ],
                "description": "Adds new thingys to the database, assigning them IDs and setting their last modification date/time to now.\n",
                "parameters": [
                    {
                        "name": "thingys",
                        "in": "body",
                        "schema": {
                            "type": "array",
                            "items": {
                                "$ref": "#/definitions/Thingy"
                            },
                            "minItems": 1
                        },
                        "description": "An array of thingys to add to the database.\n"
                    }
                ],
                "responses": {
                    "200": {
                        "description": "The thingys successfully inserted, complete with IDs and last modification fields.\n",
                        "schema": {
                            "type": "array",
                            "items": {
                                "$ref": "#/definitions/Thingy"
                            },
                            "minItems": 1
                        }
                    },
                    "400": {
                        "$ref": "#/responses/bad_request"
                    },
                    "403": {
                        "$ref": "#/responses/unauthorized"
                    }
                }
            }
        }

BTW, the definitions are being expanded using swagger-expand-refs prior to submission to bootprint-swagger since they were causing issues.
When I generate the HTML, the Request Parameters section is simply not displayed at all, it goes straight from Description to Response Body.

Thank you for the report. I've just created a new version or bootprint-swagger (0.6.4). It should solve the problem. It would be great if you could verify.
In version 0.6.3, the request body and the whole section around it, is only displayed if a consumes-property is present in the operation-object. I actually think, your operation should have one, but I have relaxed the condition, so that either a consumes-property or a body-parameter must be present.

According to the swagger spec, the main object can contain global consumes and produces entries that apply to all paths and operations unless overriden. So requiring a consumes at the operation level should not be necessary.

Just confirmed that 0.6.4 did solve the issue, thank you very much! :)

I've created issue #20 to display the global default values. I'm not sure about the best way to display them. If you have an oppinion, you could comment there. That would be great

I'd add something at the very top, before the operations summary, that covers this and the authentication/security options.

Cool, thanks.

Could you post your whole JSON here as well? I would like to add support for the response-$refs.

As soon as I make it public (in a week or two), I will post the link here. Meanwhile, more than happy to share it privately with you so you can conduct testing with it, provided you don't make it public anywhere.

I guess bootprint-swagger will survive the next two weeks without being able to display response-refs. I can also create my own example. It's just less work for me if someone else does it.
For me, testing means including a spec as test-fixture in the project and writing a unit test. Maybe a dedicated fixture is better suited for this task anyway.

How about this one?
{
    "swagger": "2.0",
    "info": {
        "title": "Test API",
        "version": "v1-beta"
    },
    "host": "api.contoso.com",
    "schemes": [
        "https"
    ],
    "basePath": "/api/v1-beta",
    "securityDefinitions": {
        "api_key": {
            "name": "X-API-KEY",
            "type": "apiKey",
            "in": "header"
        }
    },
    "security": [
        {
            "api_key": []
        }
    ],
    "consumes": [
        "application/json"
    ],
    "produces": [
        "application/json"
    ],
    "paths": {
        "/tagged_things": {
            "get": {
                "summary": "List tagged things.",
                "tags": [
                    "Alerts"
                ],
                "description": "Lists all tagged things accessible to the API key owner.\n",
                "responses": {
                    "200": {
                        "description": "An array of tagged things",
                        "schema": {
                            "type": "array",
                            "items": {
                                "type": "object",
                                "required": [
                                    "tags"
                                ],
                                "properties": {
                                    "tags": {
                                        "type": "array",
                                        "items": {
                                            "type": "string",
                                            "enum": [
                                                "option1.blah",
                                                "option2.bleh"
                                            ],
                                            "minLength": 1,
                                            "maxLength": 64
                                        },
                                        "uniqueItems": true,
                                        "description": "Array containing one or more tags.\n"
                                    }
                                }
                            }
                        }
                    },
                    "400": {
                        "$ref": "#/responses/bad_request"
                    },
                    "403": {
                        "$ref": "#/responses/unauthorized"
                    }
                }
            }
        }
    },
    "responses": {
        "bad_request": {
            "description": "The request violated the specification and was rejected. The reason string should contain more details on the specific error."
        },
        "unauthorized": {
            "description": "Operation was not allowed due to an invalid API key, insufficient privileges or trying to reference an entity that does not exist. We have purposedfully combined non-existance and lack of privileges into this error code to avoid enumeration attacks."
        }
    }
}

That's great. Thanks. Just to make sure that's OK. I have included your other samples in my test fixtures:
body-without-consume.json, missing-items.json, so that was like putting them under MIT-license with the rest of the bootprint-swagger-code. There is no good way to include a licensing-comment in JSON, so I will put an extra file somewhere in the project mentioning you as author somehow.
I would just to ask for permission to do this. If you say "take them out again" I will do that and create my own. Same for the JSON you just posted.
Is it OK to include them in the project under the MIT-License?

Yes, feel free to add those examples into the project under MIT License. I'm glad I was able to help. :)


Chanhe ourdated Cliqz by Ublock origin extension or by integrating and enabling "adguard dns" doh dns over https (or quad9 dns) to blocks ads and malware and crypto jacking mining

Hello, it seems that Cliqz the browser and the search engine is sadly no more developed :
https://cliqz.com/en/magazine/farewell-from-cliqz
and  description of Quark player says  : "AdBlocker (provided by Cliqz)"
may be it wll be good to replace cliqz adblocker by the famous extesion adblocker "ublock origin"
https://ublockorigin.com/
or by activating by default in Quark player the doh dns over https of adguard dns which is not an aggressive dns and it avoids false postiives and should be compatible with the majority of sites and services while blocking ads and malwares and crypto mining  , or add option to enbale quad9 dns which
https://adguard-dns.io/en/public-dns.html
Thank you !
EDIT : boosted with artificlele intelligence which is the most powerful dns in the world to block malware according to a study by blocking 97% of threats while the second dns in the ranking of this scientific study only blocks 57% of threats!
our dream is to have quad9 dns combined with ad blocking lists but apparently some companies that fund quad9 are funded by ads.....but that said the pure android quad9 application will allow importing custom lists ....but as long as quad9 does not block ads, I think it is better to integrate in Quak Player an option to activate "adguard dns" because the comfort in a video player is to be able to enjoy videos without ads.....

@trimechee While Cliqz is no longer around, it was acquired by Ghostery, which makes Ghostery Browser and adblock extension. https://www.ghostery.com/ The npm package is just still named Cliqz-adblock for backwards compatibility, but it is still getting updates and is the best adblocker for Electron https://www.npmjs.com/package/@cliqz/adblocker. Using Ublock origin would require alot of work and needlessly complicate the app, because Electron doesn't have support for Chromium Extensions, which makes you have to use something like https://github.com/ramboxapp/electron-chrome-extensions

Ohh if there is the famous adblock extension of Ghostery, then there is no need for ublock origin! thank you so much for implementing this feature! I close the issue :)


Not working on desktop

Hi the camera opens up on my desktop app but nothing happens when I put a barcode in front of it, however when I create the app for Android it works fine. Could you help?
I don't mind paying for your time
Thanks

Hi,
I am caught up with some other work, but I will have a look as soon as possible.

Ok thanks for the quick reply. Do you think the quality of the camera
affects if it can read the barcode
On Tue, Mar 12, 2024, 14:22 Kunchok Tashi @.***> wrote:

Hi,
I am caught up with some other work, but I will have a look as soon as
possible.
—
Reply to this email directly, view it on GitHub
https://github.com/CodingWithTashi/simple_barcode_scanner/issues/49#issuecomment-1991639683,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK4FUFEBZ6DX2VPVJBAE6N3YX36N3AVCNFSM6AAAAABESGUSWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJRGYZTSNRYGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

@mogbebs
Reading barcode not only depend on camera, but also with qr/barcode as well. some scanner does not support certain barcode. If you could share me barcode, snippet or video of what you are scanning and what you are getting, that would be easier for me to check. Also mention version you are using.

Is this same issue as this? https://github.com/CodingWithTashi/simple_barcode_scanner/issues/46

No it's not. With mine the scanning window comes up but nothing happens.
The red line doesn't go up and down. It's just the scanning window but
nothing happens. I tried.
Here is a link to the video. https://we.tl/t-AKuGAKLSWp - It was too big to
email to you.
On Tue, Mar 12, 2024, 20:54 Kunchok Tashi @.***> wrote:

Is this same issue as this? #46
https://github.com/CodingWithTashi/simple_barcode_scanner/issues/46
—
Reply to this email directly, view it on GitHub
https://github.com/CodingWithTashi/simple_barcode_scanner/issues/49#issuecomment-1992442001,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK4FUFCTL3UAABUDX5ALHTLYX5MK7AVCNFSM6AAAAABESGUSWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJSGQ2DEMBQGE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Delete Database Update-Database not working

Deleted database using SSOX.
Run this as instructed:
PM> Update-Database
Build started...
Build succeeded.
Done.
PM>
But Movie database was not re-added.

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

ID: 01013ef6-c55c-ff58-571c-ddc4435993af
Version Independent ID: 24699fe5-9744-1796-0798-f7b211ec0f2f
Content: Add a new field to a Razor Page in ASP.NET Core
Content Source: aspnetcore/tutorials/razor-pages/new-field.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

P.s. I cannot proceed, I have no database.

Hello! Thanks for contacting us. This sounds like a general question about using ASP.NET Core. While we try to look at and respond to all issues, for questions like this we recommend posting to a community support group like Stack Overflow with the asp.net-core tag.

No, it is a specific question about following the tutorial page instructions.
Alan<EMAIL_ADDRESS>On Tuesday, January 7, 2020, 12:53:59 p.m. EST, Rick Anderson<EMAIL_ADDRESS>wrote:

Hello! Thanks for contacting us. This sounds like a general question about using ASP.NET Core. While we try to look at and respond to all issues, for questions like this we recommend posting to a community support group like Stack Overflow with the asp.net-core tag.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

PM> Update-Database
Works. Are you sure it wasn't created?

100%.  It used to be here, it isn't back.  And running the program gives an SQL execption for missing database.


QT wallet need to validate network and coin values in the payload

After rebase wallets will add coin and network information into the slates. We need to check those optional fields at QT wallet.
It is related to file operations.

Done with a slatepack integration.
Testing:

try send/receive files and slatepacks between floonet/mainnet. You should see the error
Try the same for tor.
For MQS that problem should be caught on address level, probably QT wallet will catch that.
Try swaps. One wallet on mainnet,  another of floonet.

Done with a slatepack integration.
Testing:

try send/receive files and slatepacks between floonet/mainnet. You should see the error
Try the same for tor.
For MQS that problem should be caught on address level, probably QT wallet will catch that.
Try swaps. One wallet on mainnet,  another of floonet.

Verified the possible combinations, hence closing this ticket.

Verified the possible combinations, hence closing this ticket.


Page freeze after modal close or error prevented submission

After closing the pop or after the error message is show. nothing else on the entire page is clickable. Any idea how we could fix this?

Sorry for a late reply, could you share your props configuration and the file you are trying to upload? Could you try the latest versions (>4 for react 18 or >3 for React 17) and see if it's still the case?

Because this issue is quite old, I will close it. Please reopen if it's still a problem.


Add beat to pulsar-hub

Add v0.1.0 version beat to pulsar hub

I have fixed comment @Anonymitaet, @Huanli-Meng PTAL

@Huanli-Meng Can you please take a look at this issue? If it is ready, can you please merge it?


License?

Hey,
I'd be interested in using your project as a dependency in my Speaker Recognition project as one of the methods used in a comparison of various methods available.
Would you mind to specify the license that your modifications are under?
I see that the original project used an Apache License, but I am unsure whether you intended your changes to be under that license as well.
Thanks,
Mikołaj

Sure, Apache License added


Hide QR Code area at Mobile Screens

As possible implementation: Vaadin accordion

No reason to hide it. It is pretty functional.


Host endpoints passwords are visible

When we add an Host with an endpoint that need password, this password is actually visible on Host list.
Exemple: http://user:pass@<IP_ADDRESS>:1880
this endpoint should be visible like:
http://user:***@<IP_ADDRESS>:1880
Open question: how to print Host endpoint with password on edition form?

Best would be to change the host url.
Why not when we create a host request host (from the vm list ? ), port (from the service ?), login, password, protocol (http/https)....

@lvenier can we link a host with this kind of service?


Browser Requests Incorrect Path for JavaScript File After Build

I have the following file structure:
.
└── src/
    └── index.html
    └── main.ts

In my index.html, I try to use .
When building it with your provided example script, main.ts and index.html get correctly converted, however now the browser tries to reach url/main.js which doesn't exist, instead of url/dist/main.js.
Trying to set a <base href="/dist/"> in index.html doesn't work, as now the HTMLParsers looks for ./src/dist/, which obviously doesn't exist. Neither does requesting <src="../src/main.ts". Maybe the tool could change occurrences of entry point to outdir/entrypoint?
I presume this is my own misunderstanding, but I'd be very grateful if you could take the time and run me through how to do this properly :)

Thank you for the bug report! Sorry for not getting to you sooner.
I cannot reproduce this as of v2.1.0, maybe that fixed this? It was a complete rewrite. Used the following setup to attempt to reproduce this.
src/index.html

        <meta charset="utf-8">
        <meta name="viewport" content="width=device-width, initial-scale=1">
        <title>Hello World!</title>

Hello World

src/main.ts
console.log('hello world!');

build.ts
import html from 'bun-plugin-html'
import { $ } from 'bun'

await $`rm -rf ./dist`

await Bun.build({
    entrypoints: ['src/index.html'],
    outdir: 'dist',
    plugins: [html()]
})

index.ts
Bun.serve({
    fetch(req) {
        const filePath = './dist' + new URL(req.url).pathname;
        const file = Bun.file(filePath);
        return new Response(file);
    },
    error() {
        return new Response(null, { status: 404 });
    },
    port: 3000
})


Cannot install Serilog.Sinks.Sentry.AspNetCore 2.0.1

Hi,
It seems there is an issue with the Core project's csproj. When i try to install the sink to a .Net Core 1.1 project i get :
Installing Serilog.Sinks.Sentry.AspNetCore 2.0.1.
Package Serilog.Sinks.Sentry.AspNetCore 2.0.1 is not compatible with netcoreapp1.1 (.NETCoreApp,Version=v1.1). Package Serilog.Sinks.Sentry.AspNetCore 2.0.1 supports: net451 (.NETFramework,Version=v4.5.1)
I checked the csproj and i think i see the issue :
line 7 :
<TargetFramework>net451</TargetFramework>
Thanks.
Narcil

Hi @Narcil,
This is a known issue.
The sink doesn't support Core 1.x, because of this issue https://github.com/getsentry/raven-csharp/issues/125

Ok thanks somehow i missed that. The NuGet description is Microsoft.AspNetCore.Http (>= 1.0.0)


Add ntfs-3g to packages

Most of the users who use some kind of external hard drive have them formatted to ntfs. Adding the following package will allow users to use external hard drives for storing games, media and allowing transfer of files from windows PC's.

The current ntfs driver in the kernel should be able to mount drives in r/w, what is the problem exactly?


ENH: Updating remote module PolarTransform for new options

Make use of PR #14 of ITKPolarTransform: https://github.com/InsightSoftwareConsortium/ITKPolarTransform/pull/14

Sure, as you see fit. The PR can just serve as a reminder. I solved the use of the new additions by first pulling the new commits, which seems to work fine:
https://github.com/romangrothausmann/ITK-CLIs/blob/9a6170cc377f42e9273876480e4953a033d6df6d/Dockerfile#L22-L24
In addition, I think CartesianToPolarTransform and PolarToCartesianTransform or a Transform combining both deserve to be included in main ITK, as they represent the pendant to AzimuthElevationToCartesianTransform (i.e. cylindrical vs. spherical transform):
https://github.com/InsightSoftwareConsortium/ITKPolarTransform/pull/15#issuecomment-588861617

superseded by #1671


failed to run e2e_test/streaming/now.slt

Describe the bug
# In madsim test, we cannot spawn process.
skipif madsim
# In parallel test, we cannot get the DB name.
skipif parallel
# TODO: Later if we introduce a new `now()`-like function that returns the time of statement execution,
# we'll be able to directly create MV without `./risedev psql` and so that we can remove these `skipif`.
system ok
./risedev psql -c "
create materialized view mv as
select * from generate_series(
    to_timestamp($(date +%s)) - interval '10 second',
    now(),
    interval '1 second'
);
"

skipif madsim
skipif parallel
statement ok
flush;

skipif madsim
skipif parallel
query I
select count(*) >= 10 from mv;
----
t

Error message/log
Caused by:
2024-06-24 16:16:39 UTC	    query failed: db error: ERROR: Failed to run the query
2024-06-24 16:16:39 UTC
2024-06-24 16:16:39 UTC	    Caused by these errors (recent errors listed first):
2024-06-24 16:16:39 UTC	      1: Catalog error
2024-06-24 16:16:39 UTC	      2: table or source not found: mv
2024-06-24 16:16:39 UTC
2024-06-24 16:16:39 UTC	    [SQL] select count(*) >= 10 from mv;
2024-06-24 16:16:39 UTC	    at e2e_test/streaming/now.slt:24

### To Reproduce

_No response_

### Expected behavior

_No response_

### How did you deploy RisingWave?

_No response_

### The version of RisingWave

_No response_

### Additional context

https://buildkite.com/risingwavelabs/main-cron/builds/2682#

This buildkite test's name is called "end-to-end test (parallel, in-memory) (release)"

Is the test expected to be skipped due to `skipif parallel`?

Is this fixed by #17435? @stdrc

Is this fixed by #17435? @stdrc

Yes, should be.


Remove Event Hubs project reference temporarily

Summary
Unblocking a release by removing version conflicts.

API change check
API changes are not detected in this pull request.


chore(main): release 0.55.0

:robot: I have created a release beep boop
0.55.0 (2024-11-26)
Features

Pipelines notifications (#865) (c18503b)

Bug Fixes

deps: update dependency @sentry/nextjs to v8.40.0 (#884) (e5e837c)
deps: update dependency @types/node to v22.10.0 (#895) (cd9fc48)
deps: update dependency @types/node to v22.9.2 (#890) (aeec8e0)
deps: update dependency @types/node to v22.9.3 (#891) (1779d53)
deps: update dependency @types/node to v22.9.4 (#894) (d469cc5)
deps: update dependency cronstrue to v2.52.0 (#883) (a925cf3)
deps: update dependency i18next to v23.16.7 (#880) (d48bcd7)
deps: update dependency i18next to v23.16.8 (#882) (db39382)
deps: update dependency i18next to v24 (#888) (16be047)
deps: update dependency i18next to v24.0.2 (#892) (2b5dd51)
deps: update dependency next-i18next to v15.4.0 (#885) (867501b)
deps: update dependency react-i18next to v15.1.2 (#898) (17468a3)
deps: update dependency typescript to v5.7.2 (#887) (abf79ba)
Legacy: The redirection when user had not the workpaces flag was wrong and the two pages were not exposed (ff61a15)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

0.55.0
:sunflower:


Request for installation

Hello,
I need some information for installation, or "how to" documentation.
Thanks.
Alain

Hi Alain. I assume you're using Atom already, right?  The following page has some basic instructions on what are Atom packages and how to install them. Atom Packages
hope it helps!

Ok, I Try it.
Thanks (Merci).
http://www.aforp.fr/entreprises/votre-taxe-dapprentissage-pour-soutenir-une-formation-hors-du-commun
[cid:jpo2018_6217a9f2-29b5-4b99-b423-a4562758f517.jpg]https://goo.gl/rvwjxx   [cid:TA2018_0088615f-f838-4a97-a5ff-dfcb44153713.jpg] https://goo.gl/ZmbTK2
De : Diogo<EMAIL_ADDRESS>Envoyé : lundi 11 décembre 2017 12:38
À : DiogoAndre/language-cisco<EMAIL_ADDRESS>Cc : DUPERCHE Alain<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Objet : Re: [DiogoAndre/language-cisco] Request for installation (#7)
Hi Alain. I assume you're using Atom already, right? The following page has some basic instructions on what are Atom packages and how to install them. Atom Packageshttps://flight-manual.atom.io/using-atom/sections/atom-packages/
hope it helps!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/DiogoAndre/language-cisco/issues/7#issuecomment-350699935, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Ag2KI7WBspD-b7g2ccUHcVfDRQ7QiThSks5s_RP8gaJpZM4Q9MNV.


Adding a Placeholder

Wondering if there is a way to add a placeholder text like an input element.
Thanks in advance

Just thought I'd drop a comment about monkey patching this:
Lines 408
            // Create the type_zone input using custom class and contenteditable attribute
            self.$type_zone = $( document.createElement( "input" ) )
                             .addClass( self.config[ "type-zone-class" ] )
                             .attr( "contenteditable", true )
                             .attr("placeholder", "New Tag");

I imagine you could do something like:
.attr("placeholder", self.config[ "type-zone-placeholder" ] )
If I find that i need customized placeholders in my project and I end up doing this Ill paste the results/pull request


As mentioned in #385, this can cause problems if your containers don't expose their ports using the EXPOSE directive.
This aims to fix what #385 was trying to fix, but hopefully do it in a way that will not break.

LGTM!
Thanks @download13 :)
/cc @vdemeester

LGTM 🐱


Add support to Task

Description
Support Task
Issues Resolved
Check List

[ ] New functionality includes testing.

[ ]  All tests pass for go 1.11 + gofmt checks.

[ ] New functionality has been documented in the README if applicable.

[ ] New functionality has been thoroughly documented in the examples (please include helpful comments).
[ ] New endpoints supported are updated in the endpoints-support.md file.

[ ] Changes are documented in the CHANGELOG.

Add the docs

Done


Remove --use-wheel in tests, now deprecated

This is a follow-up from #39, which fixes wheel tests for pip, which has now deprecated the --use-wheel option: https://pip.pypa.io/en/stable/news/#b1-2018-03-31

Looks like LongPathTestCase is still failing... Might be because of the difference in Travis test environments from last year (Ubuntu 12.04) till today (Ubuntu 14.04).
Any ideas on how to fix LongPathTestCase?

Ahh interesting, this was some workaround code we had to add in because of a bug in distutils but I believe they've fixed it upstream. I have just tested and it works with long paths now.
Happy for you to remove that entire LongPathTestCase as part of this PR.

Hi @sjkingo, the tests are passing again, please help to review it once again!
Since the upstream bug is fixed, I suppose the workaround introduced in #31 is no longer needed. However I think we could just leave it as it is, unless there are other concerns with python -m pip?


Support command shorthands

fixes #372

I have read the CLA Document and I hereby sign the CLA

recheck

@jzelinskie please take a look


Update upgradeMetaDataTable.sql

The create script doesn't have the vr_idx or ir_idx. When it runs upgrade script it fails.

Yes it does: https://github.com/flyway/flyway/blob/flyway-3.2.1/flyway-core/src/main/resources/org/flywaydb/core/internal/dbsupport/postgresql/createMetaDataTable.sql


Add Note Regarding Content Orientation/Navigability

From the accessibility guide:
https://github.com/ucsb-wsg/web-accessibility/blob/master/web-accessibility-guidelines.md#9-provide-mechanisms-to-help-users-find-content-orient-themselves-within-it-and-navigate-through-it

Such mechanisms may include site specific search engines, site outlines, tree diagrams, and the use of proper HTML techniques such as tagging elements as tables, headers, lists and forms.

When using tables, title each frame to facilitate navigation and describe the frame and their relationship to the other frames in the table if it is not readily apparent.

Avoid ambiguous navigation tags such as: "Click here", "More info", or "Skip intro". Wherever possible, use a "title" attribute to further clarify the destination of a link.
It is also helpful to allow users to skip redundant navigation links (i.e. identical links that appear at the top of every subpage). While a visual user can simply skip over these links, a person using a screen reader must tab through each link before they can access content.
One technique is to make an anchor at the start of your content:
Then make the first link on the page a link to this anchor. This page can be white on white if needed to preserve graphical design issues: Skip to Page Content
Any links which use the same text should go to the same page (i.e. "Link to Our Home Page" or "Link to Email Us").

This is a pretty hefty recommendation: I think we should split it up. I'll create separate issues.

Since this is covered by separate issues, I'm going to close this one.


use_snake_case_for_server_api

What problem are you trying to solve?
The server API uses camelCase for all attributes when it should returns snake_case. The serde serialization for the node is using camelCase, which is what we expect in rules for JavaScript code. We need to have the conversion in the server to use snake_case.

@raczosala please tell me if this fixes the issue with the server.


Sampling strategies

[ ] This only affects the JavaScript OpenTelemetry library
[x] This may affect other libraries, but I would like to get opinions here first

Are other sampling strategies in the works such as rate limiting and adaptive sampling?

I think more advanced sampling is planned for the future, but for now it is just simple sampling while we are in alpha. This is a question for the spec.

Thanks, I'll bring it up there!


Breaks when parent has CSS transform property

If I animate parent with VelocityJS if leaves stuff like this behind transform: translateY(0px); which causes Stickyfill break.
transform value could be anything f.e. scale(1).
Test case:
https://jsfiddle.net/p56bgp4j/
Browser: latest Chrome.

Fixed positioning doesn't work inside transformed elements as expected, see this stackoverflow answer. Stickyfill is properly switching the state to fixed, but it doesn't do anything, and I don't know of any working solutions to this problem.

@jozan your fiddle has messed up code.
.sticky {
}
  position: -webkit-sticky;

This way it will work nowhere. But fixing this it only works in FF as you say.

Ah, right. I wasn't aware of transform creates new local coordinate system. That explains this issue. Thanks!
/J

On 07 Dec 2015, at 12:22, Oleg Korsunsky<EMAIL_ADDRESS>wrote:
Fixed positioning doesn't work inside transformed elements as expected, see this stackoverflow answer. Stickyfill is properly switching the state to fixed, but it doesn't do anything, and I don't know of any working solutions to this problem.
—
Reply to this email directly or view it on GitHub.


Exception levée SampleTga.exe

it's about the c sample opening a tga.The tga file is loaded and there is an exception at line:
xtga_ManagedArray* Image = xtga_TGAFile_GetImageRGBA(MyFile, &AlphaType, &err);
Visual studio 2019 say bug is in dll: codecs.cpp line 2261:

if (!obuffer)
{
obuffer = (uchar*)malloc((addressable)w * h * depth);
for (addressable i = 0; i < (addressable)w * h * depth; ++i)
{
((uchar*)obuffer)[i] = ((uchar*)buffer)[i];       //<<<<<<<<<< here
}
}
I join the sample

sample.zip

Hi there! Sorry for the late reply, the problem has been fixed with 0663ec5 , I will be creating a release in a few minutes as well :-)
Thanks for reporting the problem and attaching a project to make it easy to test.


There is a problem of interruption of flow

Hello,
To investigate this issue I need rust logs alongside of a pcap file.

environment: Windows(<IP_ADDRESS>)+WSL-ubuntu
program:  examples/tun2
Execute on Windows: iperf3 -s
Execute on WSL:  cargo run --release --example tun2 -- --server_addr <IP_ADDRESS>:5201
Execute on WSL:  iperf3 -c <IP_ADDRESS> -R
This way, we can reproduce the problem

I recently wrote a TCP/IP user-space protocol stack library. Feedback and discussions for improvement are welcome! https://github.com/rustp2p/tcp_ip

Is there any progress on the project? The issue with the write flow break might be caused by the send window being too small, causing the entire protocol processing to be stuck in waiting.
https://github.com/narrowlink/ipstack/blob/10cf7fedabf94186dba1cae25df7f95a53771024/src/stream/tcp.rs#L403

Initial writes being too fast can cause the receiver's window to shrink rapidly, eventually reducing to zero.

It seems there is also an issue with handling sequence number wraparound.

Is there any progress on the project? The issue with the write flow break might be caused by the send window being too small, causing the entire protocol processing to be stuck in waiting.
https://github.com/narrowlink/ipstack/blob/10cf7fedabf94186dba1cae25df7f95a53771024/src/stream/tcp.rs#L403

Due to time constraints related to my PhD, I have temporarily limited my involvement in this work to addressing critical issues (e.g., security concerns). I plan to resume development when time allows and welcome contributions, including PRs, to help address this issue.

Initial writes being too fast can cause the receiver's window to shrink rapidly, eventually reducing to zero.

To provide some context that may help troubleshoot:
Initially, ipstack relied on iperf for benchmarking. However, I realized that iperf alone was insufficient to evaluate efficiency comprehensively. Other crucial aspects, such as handling “TCP Zero Window,” needed to be considered. To address this, I implemented a mechanism to tackle the issue. While this solution improved real-world runtime functionality, it negatively impacted iperf results.


[Audit_RV] Inconsistent sign for 0 in BalanceUpdate

The following code could result in Increase(0) which could cause false failure in balance updates, for example, the hub asset liquidity update in Line 993 of PR445.
https://github.com/galacticcouncil/HydraDX-math/blob/f4dab244bb5d57971325f0ba6fbb8f6c1353beeb/src/omnipool/types.rs#L74
https://github.com/galacticcouncil/HydraDX-math/blob/f4dab244bb5d57971325f0ba6fbb8f6c1353beeb/src/omnipool/types.rs#L98
https://github.com/galacticcouncil/HydraDX-math/blob/f4dab244bb5d57971325f0ba6fbb8f6c1353beeb/src/omnipool/types.rs#L116

Added special of increase(0) to avoid false failures.

fixed #61


Expand all descriptions in Glossary terms

Is your feature request related to a problem? Please describe.
In the current version of Metadata v1.2 the button "Expand all" in Glossary doesn't allow to see the whole description.
Describe the solution you'd like
We decided to use Glossary to govern product event. In our company it is crucial to navigate in them via images, so we would like to see all the glossary term descriptions in their entirety.
I have two ideas how it can be implemented:

When user clicks on the button "Expand all" (as it is on screenshot) - all descriptions will be presented (not only the hierarchy of terms will be expanded but also every description of term). So there will be no necessity to click "More" in every description.
You can add new button to expand all descriptions of terms at the same time.

@LiubovPasechnik what happens if the description has 10 lines in each term. That won't be fitting in a row

Also we understand that for better display it is also possible to add an option to expand descriptions only for a particular branch of the hierarchy of terms.

Dear @chirag-madlani and @karanh37,
I can clarify my request:

It is possible to add a button "Expand all descriptions" near the current location of button "Expand all". So there will be two buttons: one to expand all hierarchies of terms and another to expand all descriptions.
Also we would like to be able to expand all descriptions only in the particular branch of terms. So for instance it is possible to put such button where the star is located at the screenshot:

we don't want to add yet another button to do this. @LiubovPasechnik how often this action is performed and are all of your users will do this operation?


Add default rules on proc.name changes

Our default rule-set relies heavily on proc.name. Since processes can change their names easily we should also include some default rules alerting if a process changes its name in other to avoid the rules we have defined.

Thanks for filing this--it's been on the todo list for a while but I guess it didn't have a tracking issue until now.


suddenly it doesn't work, haven't used firebase's latest mechanism/API?

Since September 4, 2024 until now, there are no more notifications from Firebase, even though nothing has changed from coding, and I think there is already the latest API from Firebase, have you used the last API?

https://github.com/gg-innovative/larafirebase

thank you, this works great


Create dark theme for logger

Clarification Question:
Does dark theme mean a dark styling for logger output, i.e. dark terminal background & colors changed accordingly?

Do we want to provide a generic template that will let others extend with their own color scheme - or are we just providing an alternate.

Does dark theme mean a dark styling for logger output, i.e. dark terminal background & colors changed accordingly?
yes

Do we want to provide a generic template that will let others extend with their own color scheme - or are we just providing an alternate.
I would say lets just provide an alternate. The logger got too complex last time because we tried to be overly clever.


removed empty cref links

ECMA2Yaml tool has been updated and empty cref links will cause build errors. This PR is to fix that.

Build seems stuck. Closing and reopening this one.


deps: update lodash deps to v4.1.0

Lodash v3 is no longer being supported.
lodash.padright is now lodash.padstart
lodash.padleft is now lodash.padend
Update dependencies and modify require's as neccessary

It is worth mentioning that a handful of the recursive dependencies that are not getting deduped from the tree are no longer present after this update.
This includes

lodash._basetostring
lodash._createpadding

:+1:

Merged as 84bdb63

And released in v1.2.6

I mean, except for the padstart/padend change =D

Actually merged as f8c4b15 & v1.2.7


Fix for KeyVaultAuthBase request.session TypeError failure

This is a fix for issue https://github.com/Azure/azure-sdk-for-python/issues/1157.   It also introduces the intended change of honoring the environment variables 'REQUESTS_CA_BUNDLE' and 'CURL_CA_BUNDLE'

Codecov Report

Merging #1158 into master will increase coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #1158      +/-   ##
==========================================
+ Coverage   55.15%   55.15%   +<.01%
==========================================
  Files        2170     2170
  Lines       60458    60459       +1
==========================================
+ Hits        33344    33345       +1
  Misses      27114    27114

Impacted Files
Coverage Δ

.../azure/keyvault/custom/key_vault_authentication.py
66.66% <50%> (+0.95%)
:arrow_up:

Continue to review full report at Codecov.

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

Cross reference this discussion as well: https://github.com/Azure/azure-sdk-for-python/issues/1159


[BUG] All points in Scatter chart are of the same color but I passed an array of colors

https://codepen.io/anon/pen/BYpgrP

Chart.js version: 2.7.1
Browser name and version: Google Chrome | 63.0.3239.132

@Nakilon the label of colours is applied, it's just that the colours are very similar. See https://codepen.io/anon/pen/gvmXgx


.NET API Browser: include nuget package which contains the API

On the .NET API Browser, the namespace and assemblies including APIs are mentioned. However, the nuget package containing the API is arguably much more important than the assembly.
For example, looking at HttpUtility.ParseQueryString() on .NET Core, nothing tells me which nuget package I need to install in order to get the API (Microsoft.AspNetCore.WebUtilities).

@rloutlaw Can you please take a look at this issue?

I'm closing as duplicate of #72


📥 Prefer frontmatter downloads over exports

Here's a start to consume the new downloads available in project/page frontmatter (https://github.com/executablebooks/mystmd/pull/1049)
Where we previously built a download list from exports we now look to see if downloads is defined. If so, the theme uses that instead. If downloads is not defined, it still falls back to exports for backwards compatibility.
This also makes a couple tweaks so download format may be undefined - since we allow downloads to be of arbitrary format, we need to handle unknown formats.

This PR so far addresses the article-theme, how should the book-theme be handling these given they are defined on the project?

I've aligned DownloadsDropdown in frontmatter with your changes to the article theme - this addresses book theme since it uses that component.
The only difference is frontmatter does not depend on @remix-run/react so it does not use Link for the internal links. Not sure if there's any implications to adding that dep to frontmatter?

@fwkoch yeah let's keep Link out of frontmatter and just use a there


Issue installing haskell_cudd (Ambiguous occurrence `unsafeForeignPtrToPtr')

I am running Fedora 21 64bit
I installed cudd, cudd-extras and cudd-devel via yum.
When I try cabal install cudd I get "Missing C library: st"
Continuing with cabal install cudd --extra-lib-dirs=/lib64/cudd, where Fedora installs the cudd libraries, I get 'dddmp.h not found.
Continuing with cabal install cudd --extra-lib-dirs=/lib64/cudd --extra-include-dirs=/usr/include/cudd/, where the header-files are installed
[ 1 of 11] Compiling Cudd.ForeignHelpers ( Cudd/ForeignHelpers.hs, dist/build/Cudd/ForeignHelpers.o )
Cudd/ForeignHelpers.hs:20:18:
Ambiguous occurrence `unsafeForeignPtrToPtr'
It could refer to either `Foreign.unsafeForeignPtrToPtr',
                         imported from `Foreign' at Cudd/ForeignHelpers.hs:9:1-14
                         (and originally defined in `Foreign.ForeignPtr')
                      or `Foreign.ForeignPtr.Unsafe.unsafeForeignPtrToPtr',
                         imported from `Foreign.ForeignPtr.Unsafe' at Cudd/ForeignHelpers.hs:11:1-32
                         (and originally defined in `GHC.ForeignPtr')
Failed to install cudd-<IP_ADDRESS>

I tried to look into that issue myself but strange enough, when I try  cabal install --extra-lib-dirs=/lib64/cudd --extra-include-dirs=/usr/include/cudd/ within the cloned git repository, I get an Could not find module 'Cudd.File'-error.
Do you have any Idea how I might get the cudd-bindings running?

It is strange that you have to manually add standard lib and include directories manually. Not sure how to fix that.
Are you using ghc 7.6? base version 4.6 exports unsafeForeignPtrToPTr from Foreign whereas later versions dont. This is probably whats causing the problem. I should have set a lower bound on the version of base to prevent this.
In that case, the solution would be to upgrade ghc. If thats not possible, I can look at making it work for older versions.

Yeah, that thing with the libraries is strange enough but including the paths is no real issue, I think. I was just stating those things for completeness.
I am using ghc 7.6.3 from the Fedora21 repository. Again, I wouldn't mind giving fixing it myself a shot but executing cabal install --extra-lib-dirs=/lib64/cudd --extra-include-dirs=/usr/include/cudd/ in the haskell_cudd repository clone doesn't work with a module-not-found error for Cudd.File.

I cloned the repo and tried the same thing. It also failed for me in the same way. I noticed that in the dist directory it hadnt built File.hs from File.chs for some reason. File.chs is definitely there so I have no idea why it cant find it.
Then, I deleted the dist directory that cabal makes at the root of the repository and tried again. This time everything worked.
In my experience, cabal is a very flakey piece of software. Wiping the dist directory and starting again might work for you too.

You're right. The File.hs-issue fixes itself. It all works from my hiding branch (pull request is referenced). Thanks :)


Hardfork countdown support

Issue Number

#1917
Overview

[x] I have extended ApiNetworkParameters
[x] I have updated swagger accordingly
[x] I have updated core TypeSpec
[x] I have extended NetworkParameters
[x] I have extended DB schema and addressed DB migrations
[x] I have used QueryAnytimeShelley EraStart from CardanoQuery to get value
[x] I have tested the above

Comments

To move forward I need https://github.com/input-output-hk/cardano-wallet/pull/1909 to be merged.
As,
QueryAnyTimeShelley EraStart :: Query CardanoBlock

bors try

bors try

I will need to wait for mainnet test when https://github.com/input-output-hk/cardano-wallet/pull/1943 is merged - to my best knowledge

setup: cardano-wallet-shelley conneted to the mainnet
before 18:30 UTC :
cardano-wallet-shelley network parameters
no  "hardfork_at" in repsonse

after 18:30 UTC:
     "hardfork_at": {
        "epoch_start_time": "2020-07-29T21:44:51Z",
        "epoch_number": 208
    },

Thanks @Anviking  and @piotr-iohk  with helping in verifying this!

bors r+

Unit tests running OOM. Reported in the spreadsheet, hopefully fixed by #1954.