Markdown-it attributes with wysiwyg editor doesn't add attributes

Version
1.3.1
Test Environment
Google Chrome 72.0.3626.119, Windows 10, Asp.Net MVC Razor page, Parcel bundler JS-component
Current Behavior
We are trying to add markdown-it-attr extension to our editor to support HTML element attributes. It works in the markdown editor now. The only issue we have with it is that need to support Wysiwyg editors in our app and the plugin does not go well with that. Example below
In markdown editor the following # Title {.section-title} translates correctly to

Title
 but when switched to Wysiwyg editor it shows Title {.section-title} so the attribute part is rendered raw. Should it work like this? Is there a way we could fix this? I tried to create a custom converter for this but it turned out to quite a burden.
This is how we add markdownItAttrs plugin.
const markdownItAttrs = require("markdown-it-attrs");
const tuiEditor = require("tui-editor");
tuiEditor.markdownitHighlight.use(markdownItAttrs);

Expected Behavior
I would expect Wysiwyg render the attributes to HTML and not display the markdown code for them.
Cheers!

@suomiton Currently there is no way to not display markdown code in Wysiwyg. When use markdown extension, I'm sorry to not support every case.
In this cause, you can use 'wysiwygSetValueAfter' event. This event occur when convert to Wysiwyg from markdown. So when this event occur, you can remove {.section-title} in Wysiwyg. For removing {.section-title}, you need a root element of Wysiwyg. You can obtain Wysiwyg instance by calling getSquire of editor instance API and then get the root element by getRoot Squire instance API. I hope this method will help you.
If you have a problem, please leave a question or suggest a more comfortable one. Currently, I am thinking about making API that is more convenient for this situation.


uses java

its a gulp plugin use javascript not java

Thanks for your proposal. Maybe the other plugins can do that, but this plugin requires Java to use vnu.jar that is used in w3c. I don't have a plan to get rid of it so far in this plugin since vnu.jar is rad. Sorry, but let me say won't fix.
Could you please try other plugins then?

https://www.npmjs.com/search?q=gulp+html+lint


Use correct language on Danger message when documentation is modified

The danger message text was inverted and was asking to modify then English documentation when had to ask to modify the Chinese one and the other way around.

Messages

:book:
macOS: 	 Executed 283 tests, with 0 failures (0 unexpected) in 16.009 (16.493) seconds

:book:
tvOS: 	 Executed 283 tests, with 0 failures (0 unexpected) in 13.440 (13.970) seconds

:book:
iOS: 	 Executed 283 tests, with 0 failures (0 unexpected) in 13.315 (13.812) seconds

  Generated by :no_entry_sign: Danger Swift against cc4dbe5c33df8bfa7c33fe5e8b680a8d41119723

Codecov Report

Merging #2017 into master will decrease coverage by 1.67%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2017      +/-   ##
==========================================
- Coverage   94.23%   92.55%   -1.68%
==========================================
  Files          26       26
  Lines         954      887      -67
==========================================
- Hits          899      821      -78
- Misses         55       66      +11

Impacted Files
Coverage Δ

Sources/RxMoya/Single+Response.swift
87.5% <0%> (-12.5%)
:arrow_down:

Sources/ReactiveMoya/SignalProducer+Response.swift
84.84% <0%> (-9.1%)
:arrow_down:

Sources/RxMoya/Observable+Response.swift
53.84% <0%> (-7.7%)
:arrow_down:

Sources/Moya/Response.swift
90.69% <0%> (-4.71%)
:arrow_down:

Sources/Moya/Plugins/AccessTokenPlugin.swift
91.66% <0%> (-1.67%)
:arrow_down:

Sources/Moya/MoyaProvider+Defaults.swift
77.27% <0%> (-0.99%)
:arrow_down:

Sources/Moya/Plugins/NetworkLoggerPlugin.swift
96.34% <0%> (-0.54%)
:arrow_down:

Sources/RxMoya/MoyaProvider+Rx.swift
96.42% <0%> (-0.45%)
:arrow_down:

Sources/ReactiveMoya/MoyaProvider+Reactive.swift
96.55% <0%> (-0.42%)
:arrow_down:

Sources/Moya/MoyaProvider.swift
91.3% <0%> (-0.37%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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


CrashReporting with wrong build number

From my experience: If an app has crashed and is first opened again after updating the app, the pending crash report will be sent with the build number of the updated app, and not the build number the crash actually happened in.

Hey @Silkjaer, will look into it.
Looks like there is no workaround for this at this point, so sorry.

Hey @Silkjaer, we've decided to deprecate Crash Reporting at Parse, so there are no updates going to be made to it. We sent out an email to active users of Parse Crash Reporting earlier today. Here is a copy of that email:

Update to Parse Crash Reporting
Hi there,
At Parse, we're always working to improve your developer experience. Last December, we launched Parse Crash Reporting with the goals of recognizing, tracking, and ultimately resolving crashes in your app.
In the time since, we've seen huge strides being made within the industry's native solutions. These native experiences have the advantage of being more tightly integrated into your build and release process, offering a more robust, streamlined, and frictionless development experience for you.
The Parse Crash Reporting tool is now being deprecated in favor of these great native solutions. We will continue supporting Parse Crash Reporting until March 1, 2016.
Here's how you can smoothly switch from Parse Crash Reporting to Apple or Google's offerings:
Apple Docs
Google Docs
We're constantly tackling new challenges to help you build better than ever before. Please reach out if you have any questions or concerns to<EMAIL_ADDRESS>The Parse Team


Update progress.mdx

Option not shown which may affect many people. This is to fix and show the option for allowSwimming?: boolean

Hi @thelindat
Please see


Container-name lookup results are case-sensitive.

Hi!
It turns out, some programs (including Postman) will garble hostnames by force-lowercasing them before querying. I'm not ready to start judging if they're right or wrong in doing that; just RFC 4343 alone tryies to clarify the whole "case-insensitivity in DNS" topic.
The fact is, DPS chokes on that. For repro, run with MG_REGISTER_CONTAINER_NAMES=1 and:
$ docker run -d --name fooBar alpine sleep infinity
6799e0325f4146dd79f8c977a2c6f7fd0170439b1412627d765605d9d00aa8b8

$ ping fooBar.docker
PING fooBar.docker (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=1 ttl=64 time=0.077 ms
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=2 ttl=64 time=0.136 ms
^C
--- fooBar.docker ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.077/0.106/0.136/0.029 ms

$ ping foobar.docker
ping: foobar.docker: Name or service not known

To the poor Postman, this manifests as ENOTFOUND from getaddrinfo("foobar.docker") with no way to workaround:

Regardless of the perhaps-broken client (which simply exposes the issue) — I believe, the DNS server portion of DPS is expected to make comparisons case-insensitively against its internal name db. Quoting from the original 1987 DNS RFC:

By convention, domain names can be stored with arbitrary case, but
domain name comparisons for all present domain functions are done in a
case-insensitive manner, assuming an ASCII character set, and a high
order zero bit.

DPS version: 2.19.0

It turns out, some programs (including Postman) will garble hostnames by force-lowercasing them before querying.

Yeah, it's not recommended by the RFC to Postman do that, anyway I will work on DPS to be compliance with the RFC .

Fixed on #332, will be release as 3.5.3, CD will release this version package  as soon as Github Actions goes back

Thanks!
пт, 3 бер. 2023, 02:00 користувач Elvis Souza @.***>
пише:

Closed #218 https://github.com/mageddo/dns-proxy-server/issues/218 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/mageddo/dns-proxy-server/issues/218#event-8655279912,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACZGGVTLM7PKCUXAQ77ONTW2E7CBANCNFSM42ENIHWQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


How to convert the generated npy file into an image

Thanks you for your work.
How to convert the generated npy file into an image?
I look forward to your reply. Thank you.

For example:
from torchvision.utils import save_image
import torch
import matplotlib.pyplot as plt
import numpy as np
import math

# load npy
logit = np.load(npy_filename)
C, H, W = logit.shape

# normalize
logit = torch.from_numpy(logit)[None]  # (1,C,H,W) in [-inf,+inf]
prob = logit.softmax(dim=1)[0]         # (C,H,W) in [0,1]

# save as images
for c in range(C):
    save_image(prob[c], f"class_{c}.png")

# or visualize w/ matplotlib
n = math.ceil(C**0.5)
fig, ax = plt.subplots(nrows=n, ncols=n, constrained_layout=True)
ax = ax.flatten()
[a.axis("off") for a in ax]
for c in range(C):
    ax[c].set_title(f"class {c}")
    ax[c].imshow(prob[c])
plt.show()

Thank you for your help.Actually,  I want to ask how the images of dataset test to be submitted to PASCAL VOC's official website for testing were converted from npy to images. I have been puzzled for a long time and look forward to your reply. Thank you very much!

PR #108 reported in issue #77 may help you.

thank you!


[Feature Request] Changing existing column descriptions

We received an anonymous feature request on April 18th via the DataPLANT Helpdesk.
"When annotating assays/studies in ARCitect, I repeatedly create several columns and fill them out. Later during the process I realize, a different column type/description is more adequate and want then to change the coulmn type/descroption without changing the data in that column. I think this is not possible so far. I realize I can make a new column, copy the data and delete the old one but thats cumbersome. It would be handy to simple change the type/description of the existing one."

I just came across the same issue that you can't change the column type or description later on. Maybe it would be nice to add these two options to the column dropdown menu where you can also change from term to unit cell and so on.

Not entirely sure what "description" refers to, but i will add the option to change column type 👍

Done, will be part of the next release! Can be found in the context menu


Do not download notes multiple times

My Voicenotes obsidian workflow is as follows:

record audio notes via Voicenotes
Voicenotes Sync does not remove them in Voicenotes due to Voicenotes' features like "Ask my AI"
Process my downloaded notes in Obsidian, which often results in moving the note some place else or removing it.

Once Voicenotes Sync is again syncing with Voicenotes, notes that have already been moved or removed in Obsidian occur again, which completely breaks my workflow. A single download of each note is the feature I seek.
Suggested technical steps: Is it possible for Voicenotes Sync to add a tag synced_with_obsidian to notes in Voicenotes when they are being downloaded, instead of removing the notes? And then configuring Voicenotes Sync to not download any notes from Voicenotes that already have the tag synced_with_obsidian?

Yes David, I vote for this request.
I'm not sure if 'voicenotes sync' can write back the tags to Voicenotes using the available API?

Yes, I don't know either. I looked at the code and it seems the REST verb DELETE can be used, but I haven't seen CREATE.
If it happens that tags cannot be created but deleted, a workaround would be to somehow have Voicenotes always create the tag to-be-synced-with-obsidian, and Voicenotes Sync downloads only those and removes that tag.


Convert Timer to WPF

The design should remain the same. If no project is added the description text is vertically centered.

[x] Description autocomplete
[x] project-client label
[x] tag and billable label
[x] duration label
[x] Start button
[x] If project is added and entry not started there is an x that when clicked clears the selected project

All features are implemented. Testing and possible polish is still needed. Code currently on win-wpf-timer.

[ ] Description placeholder not hidden when just hitting start
[ ] Replace tag and billable icons with higher resolution icons
https://github.com/toggl/toggldesktop/blob/master/src/ui/osx/TogglDesktop/icon-billable%402x.png
https://github.com/toggl/toggldesktop/blob/master/src/ui/osx/TogglDesktop/icon-tags%402x.png
[ ] Make keyboard shortcuts work ( shown in cog menu )

Shortcuts work for me. Will investigate this more as part of #1314.
Closing as wpf timer was merged into master.


[Inference LLM] Support Qwen2_Moe Inference Model

PR types
New features
PR changes
Models
Description
Support Qwen2 Moe Inference Model

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.root seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[FEATURE] Add tailwind code for gradient background generator

Description
The button has been added to copy tailwind code, but it doesn't have the actual code added to it, the tasks:

[ ] Add tailwind equivalent code for the gradient background (all you need to do is actually convert the CSS https://github.com/Dun-sin/Code-Magic/blob/eb705d0cbc8c1c5e4ea71ef8179ff368ea485d20/src/lib/packages.ts#L169-L173 to Tailwind and add it to the appropriate case here -> https://github.com/Dun-sin/Code-Magic/blob/eb705d0cbc8c1c5e4ea71ef8179ff368ea485d20/src/lib/packages.ts#L270)
[ ] Test that it works with tailwind

Screenshots
No response
Additional information
If you notice any change you want to add, not related to this Issue, please raise an issue for it instead of adding it to the PR
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
None

Hey Dunsin! Can I be assigned this issue?

Hey Dunsin! Can I be assigned this issue?

Definitely, thanks for wanting to contribute, Make sure you follow the rules 👉🏽here👈🏽, else your PR will not be accepted and will be closed.
Good Luck. Feel free to ask questions if you need to

@JayRKyd an update on this?

Need a bit of assistance if you're free

Need a bit of assistance if you're free

Sure, what do you need it with, be clear please

how exactly do i covert the said code to tailwind? I'm a bit lost on that part

how exactly do i covert the said code to tailwind? I'm a bit lost on that part

Do you know anything about Tailwind? You can check the other PRs merged that are similar to this issue

:tada: This issue has been resolved in version 2.61.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Reproducible squashfs

Issue description
The version of mksquashfs in nixpkgs is nondeterministic (even when passing -no-fragments and -processors 1). Squashfs images produced by it are not reproducible. This affects NixOS directly, as iso and netboot images are produced by mksquashfs.
The Reproducible Builds projects recommends three patches that are present in the squashfskit fork of squashfs. It looks like the squashfskit repository is a fork of squashfs-tools at 3de1687d74 (one commit after the version currently in nixpkgs), with many patches applied collected from various places, that never got upstreamed to squashfs-tools. In the mean time there was also some activity on squashfs-tools, and the two have diverged.
What would be the best course of action here? Replace squashfs-tools with squashfskit? Or cherry-pick the reproducibility patches from squashfskit and apply them on top of squashfs-tools?
Steps to reproduce
Here is an example that builds a squashfs image. The filesystem contents are reproducible, yet the image file itself is not.
git clone https://github.com/ruuda/miniserver
cd miniserver
git checkout d23dedc48e6981cf589d50231338655f77dac8cb
nix-build image.nix
nix-build --check image.nix

After replacing squashfs-tools with squashfskit like below, the image did become reproducible.
squashfsTools.overrideDerivation (oldAttrs: {
  src = fetchFromGitHub {
    owner = "squashfskit";
    repo = "squashfskit";
    sha256 = "1qampwl0ywiy9g2abv4jxnq33kddzdsq742ng5apkmn3gn12njqd";
    rev = "3f97efa7d88b2b3deb6d37ac7a5ddfc517e9ce98";
  };
})

Technical details

system: "x86_64-linux"
host os: Linux 4.16.6-1-ARCH, Ubuntu, 16.04.4 LTS (Xenial Xerus)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.0.2
channels(root): "nixpkgs-18.09pre139198.9d0b6b9dfc9"
nixpkgs: /root/.nix-defexpr/channels/nixpkgs

Any ideas why they haven't been included in squashfs-tools? That would probably help us making that decision. I would say for now just applying the patches make sense although it would be good to see it eventually included as an option in squashfs.

Two of the patches were proposed on a mailing list but received no reply as far as I can see. The squashfs-tools author said in a different thread:

The repo at kernel.org is the official repo.  It hasn't been updated in a while
simply because the tools are considered stable, and I have not had a burning
desire to add new features for a while.

I cannot find any attempt to upstream the third patch.
I’ll try to contact the squashfs-tools author and ask if these patches can be included. In the mean time I’ll try to make a pull request to apply them separately in nixpkgs.


Port master fixes for documentation

Purpose
This PR fixes the following issues.

Removes Choreo connect section from the Key Concepts doc.
https://github.com/wso2/docs-apim/issues/7748
https://github.com/wso2/docs-apim/issues/7815

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Support bool type for predicate in

@zacw7 What's the use case for this? IN(true) should be rewritten to IS TRUE, IN(false) to IS FALSE and IN (true, false) should be dropped altogether. We should not need IN (true).

Thanks for your pointer. It sounds to me that the rewrite is not working properly because we've observed some query failures due to this.

For constant list, as @mbasmanova mentioned, a simple optimization can be used to avoid the in-efficient eval of IN(bool):

x IN (TRUE) => X IS TRUE
x IN (FALSE) => X IS FALSE
x IN (TRUE, FALSE) => be dropped.

For non-constant list, supporting bool type for predicate IN is still needed since the values would be dynamic.

Drop IN predicate when both TRUE and FALSE values are present in Presto: https://github.com/prestodb/presto/pull/20285

As per disussion in https://github.com/prestodb/presto/pull/20285
This rewrite becomes complex for null cases. Also there is value in velox supporting IN for all types irrespective of some optimizations in edge cases.

Thanks folks for the reviews and suggestions!


I had increase open file limit but still exception "Device or resource busy"?

With Logs
Mar  3 09:32:32 loadtest-v2 locust: thread_result.set(func(*args, **kwargs))
Mar  3 09:32:32 loadtest-v2 locust: [2020-03-03 09:32:32,558] loadtest-v2/ERROR/stderr:
Mar  3 09:32:32 loadtest-v2 locust: [2020-03-03 09:32:32,558] loadtest-v2/ERROR/stderr: OSError: [Errno 16] Device or resource busy
Mar  3 09:32:32 loadtest-v2 locust: [2020-03-03 09:32:32,558] loadtest-v2/ERROR/stderr:
Mar  3 09:32:32 loadtest-v2 locust: [2020-03-03 09:32:32,558] loadtest-v2/ERROR/stderr: 2020-03-03T02:32:32Z
Mar  3 09:32:32 loadtest-v2 locust: [2020-03-03 09:32:32,559] loadtest-v2/ERROR/stderr:
Mar  3 09:32:32 loadtest-v2 locust: [2020-03-03 09:32:32,559] loadtest-v2/ERROR/stderr: (<ThreadPoolWorker at 0x7f6f9aa7ccc0 thread_ident=0x7f6f8dbe5700 hub=<Hub at 0x7f6f93947588 thread_ident=0x7f6fa2693740>>, <built-in function getaddrinfo>) failed with OSError
Mar  3 09:32:32 loadtest-v2 locust: [2020-03-03 09:32:32,559] loadtest-v2/ERROR/stderr: Traceback (most recent call last):
Mar  3 09:33:11 loadtest-v2 locust: [2020-03-03 09:33:11,683] loadtest-v2/WARNING/urllib3.connectionpool: Connection pool is full, discarding connection: ...

I did a quick search and found that this is most likely related to gevent's DNS resolving.
Are you using a very high number of clients/users (above maybe 1000 per process) or high rampup (above maybe 100/s per locust process)?
Would it be possible for you to use ip-adresses instead of names?
Maybe you can try one of gevent's other name resolving strategies http://www.gevent.org/dns.html
Or (probably even better) try using the new FastHttpLocust instead of the regular one.


Store.all doesn't load any records

store.all returns a live record-array but it's initially populated by source.retrieve which hit's the source's cache rather than querying for records. This means that to load a live array of all records you have to do:
store.find('type')
var populatedLiveArrayForType = store.all('type');

Is this intentional? Perhaps it would be better to initialize the record-array with source.find('type') and then use retrieve from that point on?
On a more general note, given orbit's style I expected all, filter and find to return live arrays as standard (seems more in line with orbit.js' style). I can see that there might be value in having some live and others not live though but I think the API should make this distinction clearer.

This is definitely intentional. find is asynchronous and returns a static record array. all is synchronous and returns a live record array. This allows for maximum flexibility and control.
When combined, you can return a live record array only after find completes. For instance: return store.find('type').then(function() { return store.all('type'); });. It's also valid to just return the result from find if you want to capture all the records of a type at a particular moment in time. If find always returned all, then this distinction wouldn't be possible. Another valid use case is to bind a collection to the all live array - you don't need to immediately trigger the async find to do so.
I'm not saying that I'm opposed to adding convenience methods (findAll perhaps?) that merge functionality, but I want to keep the distinction as well.
This section of the README clarifies which methods are synchronous and which are asynchronous. All the synchronous methods provide immediate access to a store's current contents, while all the asynchronous methods flow through Orbit's requestable interface.

That does seem reasonable. I suspect I would use findAll far more often than all so yes that would be a nice addition. I'm working on a firebase Source at the moment but I'd be happy to put a PR together once I've got that out the way.

You can now query a store (store.query) to engage with an Orbit Coordinator and remote sources (if configured). Or you can query a store's cache (store.cache.query) to only get results presently in memory.


In Profile, the last year in the slider should appear on the right if none are shown

fixed by changing the colors of the text label in v.2.3.128


Don't merge! Regression pull request perf test for no metavalidation

Docs Build status updates of commit 108d2a1:
:clock10: Pending: waiting for processors (19 builds ahead of you)
:warning: Docs Build is busy, currently there are 19 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 108d2a1:
:clock10: Full build: the average full build time is 6 min(s) 2 sec(s), this is based on the last 539 build(s) for this repository.

Docs Build status updates of commit 108d2a1:
:warning: Validation status: warnings

File
Status
Preview URL
Details
Dependent Files

docs-ref-conceptual/TestingPullRequest.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
[Warning] the value invalid_type is undefined for metadata content_type
[Warning] the value invalid_type is undefined for metadata content_type
Line 7: [Warning] Invalid file link:(~/nonexisted1.md).
Line 7: [Warning] Invalid file link:(~/nonexisted1.md).
Line 7: [Warning] Invalid file link:(~/nonexisted1.md).
Line 8: [Warning] Invalid file link:(~/nonexisted2.md).
Line 8: [Warning] Invalid file link:(~/nonexisted2.md).
Line 8: [Warning] Invalid file link:(~/nonexisted2.md).
Line 9: [Warning] Invalid file link:(~/nonexisted3.md).
Line 9: [Warning] Invalid file link:(~/nonexisted3.md).
Line 9: [Warning] Invalid file link:(~/nonexisted3.md).

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.


nanopb: fix build by resolving name collision

Description of changes
Closes https://github.com/NixOS/nixpkgs/issues/337012
AFAICT the executable search order was changed by https://github.com/NixOS/nixpkgs/pull/318226 so now generator/protoc is found before the protoc in $PATH.
We could either apply the following patch
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 273a841..db4c25e 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -16,7 +16,7 @@ option(nanopb_MSVC_STATIC_RUNTIME "Link static runtime libraries" ON)

 set(nanopb_PYTHON_INSTDIR_OVERRIDE "" CACHE PATH "Override the default python installation directory with the given path")

-find_program(nanopb_PROTOC_PATH protoc HINTS generator-bin generator)
+find_program(nanopb_PROTOC_PATH protoc)
 if(NOT EXISTS ${nanopb_PROTOC_PATH})
     message(FATAL_ERROR "protoc compiler not found")
 endif()

or just remove the files that cause the collision.
I went with the second one, though I'm not 100% sure if this is the better f the two options.

Other changes:

format with nixfmt
remove python3 from nativeBuildInputs
use python3.sitePackages instead of hardcoding a path
use placeholder "out" in cmakeFlags instead of using $out in postConfigure

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 337119 run on x86_64-linux 1

5 packages built:

criterion
criterion.dev
nanopb
nanopbMalloc
siril

cc @emilazy @SomeoneSerge  for cmake strictDeps fallout


Install python modules required for embedded ansible credentials

We install these into a new venv so that we don't conflict with
appliance python packages.
This list is taken directly from
https://raw.githubusercontent.com/ansible/awx/c7bb0f10e10476e10df8a7e7b26732eb60958ca1/requirements/requirements_ansible.txt
which is the result of resolving the dependencies from
https://github.com/ansible/awx/blob/c7bb0f10e10476e10df8a7e7b26732eb60958ca1/requirements/requirements_ansible.in
I feel like taking the resolved file first is safer since pip doesn't
do true dependency resolution (pypa/pip#988)
Replacement for https://github.com/ManageIQ/manageiq-appliance-build/pull/340
Looking for input on places to put the list of packages. I felt like people wouldn't go looking for this list in manageiq-appliance, but it needs to live on disk somewhere ...
I could put it in manageiq core, but this seemed like a better place to start since it's really a build-time concern.
https://bugzilla.redhat.com/show_bug.cgi?id=1734129

So I made all the changes needed to get pip install to succeed without warnings or errors on the appliance while keeping as many of the modules as I could.
Unfortunately, now, a significant number are different from what is listed in awx and also from what is shipped in the tower rpm. Plus we added a few additional rpms.
Not sure what option we want to go with here. I can always revert this PR to its original state though if we think that's better. @simaishi @NickLaMuro @Fryguy ?

@carbonin Yeah, I don't know.  Personally, I would rather we be as close to downstream as possible, or there eventually will be someone who tries fixing/replicating a bug on upstream and then turns out it is an issue with these packages and fixing it in one spot doesn't solve it in the other.
I am going to have to come back to this, but this how I started evaluating it:

Took a look at what changed from the first pass (using awx versus the Tower rpm):
https://github.com/carbonin/manageiq-appliance-build/compare/9bb4516...f367e74
Which looks pretty bad, but when looking at

The changes that got the "straight from tower" list to our new our current list (starting one commit up):
https://github.com/carbonin/manageiq-appliance-build/compare/cab28a77...f367e74
There is mostly removals from the list.

So I want to take a finer look at the about, but have to work on a few of my own TODO items first.

Yeah, I came to the same conclusion @NickLaMuro I think we're closer to the downstream set with what we have here even though it required a bunch of workarounds vs the upstream set.
I'm going to un-wip this and if we need to follow up on it we can do that after. Better to just get cloud modules working more quickly.

I'll leave it up to @carbonin and @NickLaMuro for what should be included in requirements.txt, the rest looks good to me.

@simaishi brought up that ansible and ansible-runner are not actually present in the tower rpm. I was using the list from pip freeze to create this, but that also seems to be listing modules installed at the system level (not just the ones in the venv). I can re-work this to try to just install the modules included in the venv in the rpm (not using pip freeze) ... thoughts?

pip freeze -l is a thing. So now I have a new an updated list of modules that are actually installed using the tower venv rpm. Updating this PR to use that list.

well, this got a lot simpler :joy:

Ivanchuk backport details:
$ git log -1
commit df94d2e90f0942d9458a831ecd3f4199ca121603
Author: Jason Frey<EMAIL_ADDRESS>Date:   Fri Aug 9 14:49:45 2019 -0400

    Merge pull request #341 from carbonin/install_python_modules

    Install python modules required for embedded ansible credentials

    (cherry picked from commit 441d102a558b8a29df35532cf5ecec21f77083f6)

    https://bugzilla.redhat.com/show_bug.cgi?id=1734129


add feature GH template

Related to  #62

Would anyone mind if I mived this to cnoe-io/.github?

Would anyone mind if I moved this to cnoe-io/.github?

Nope. As long as templates are used for feature requests. I think this one is generic enough that we can reuse.

https://github.com/cnoe-io/.github/pull/2


Update sql-agent-extension-troubleshoot-known-issues.md

Ado task from Amitabh: https://msdata.visualstudio.com/Database Systems/_workitems/edit/2287624
Updated the doc to cover this scenario. @bluefooted for review.

@adbadram

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks @ujpat ! Mades some suggestions for the wording, let me know if that looks OK.

@bluefooted - saw your email. when this is ready, you can sign off... PRMerger will throw an error, but we'll see it and review/merge. thanks.

This PR will be replaced by an internal PR.


Actually support republishing

https://trello.com/c/KNWv9Dgx/258-migrate-legacy-email-signup-pages-for-service-manual-formats
Previously we had a "republish" rake task that would publish
a "major" change when invoked. Since a "major" change becomes
part of the content history, and can lead to email alerts, we
should try to use a "republish" update type instead. This does
that, consolidates the existing code, and makes it more flexible.
Please see the commits for more details.

Update: the inaccurate email_alert_signup links, for topics and the service standard, seem to have vanished by themselves. This is probably because the linked content items are unpublished, and any other publishing that triggered a link expansion will automatically compacted them away.
However, they are still present in the Publishing API, so we should still republish the content items to remove the redundant links. I've added a commit to support doing that.


[stable/grafana] Upgrade to Grafana 6.5.2

Is this a new chart
No
What this PR does / why we need it:
Upgrade to Grafana 6.5.2 - https://github.com/grafana/grafana/releases/tag/v6.5.2
Which issue this PR fixes
n/a
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

Signed-off-by: Dave Henderson<EMAIL_ADDRESS>

/assign

@zanhsieh version bumped - PTAL!

Ok, version updated in README.md too (and rebased) - PTAL @davidkarlsen @zanhsieh 😁

/ok-to-test
/assign
/lgtm


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
64fc718 -> 4b7c77b

github.com/gruntwork-io/terratest
require
minor
v0.46.16 -> v0.47.0

Release Notes

gruntwork-io/terratest (github.com/gruntwork-io/terratest)
v0.47.0
Compare Source
Modules affected

packer
aws
helm
azure

Description

Added support for Packer 1.10
Fixed error checking in Azure
Fixed tests and documentation for helm, aws, packer modules

Related links

https://github.com/gruntwork-io/terratest/pull/1395
https://github.com/gruntwork-io/terratest/pull/1419

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

:tada: This issue has been resolved in version 2.11.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


support for Mongoid 7

@frodsan @gr4y @chancancode @prasadsurase @rmm5t can we get this merged please and have a new gem out? Would be fantastic to be able to use mongoid-minitest with the new Mongoid 7. Thank you!

@rmm5t updated, ready for a merge. Thank you.

v1.2.0 just released
Thanks for the help! 🍻

Great, thank you!


Readme: fix example for running on other repos

thanks for that, I knew it was wrong but didn't get around to fixing!


chore: remove readme trusted issuer ext

What this PR changes/adds
After https://github.com/eclipse-edc/GradlePlugins/pull/192 was merged we can not autodoc partitioned stile configuration and remove the README file
Why it does that
documentation

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (8c3013a) 71.77% compared to head (adbcf2a) 4.70%.

:exclamation: Current head adbcf2a differs from pull request most recent head 2ef065f. Consider uploading reports for the commit 2ef065f to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main   #3622       +/-   ##
============================================
- Coverage     71.77%   4.70%   -67.08%
- Complexity        0     243      +243
============================================
  Files           909     909
  Lines         18127   18127
  Branches       1033    1033
============================================
- Hits          13011     853    -12158
- Misses         4672   17254    +12582
+ Partials        444      20      -424

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


chan(epson-inkjet-printer-stylus-nx110-series): added repology

Fails on everything not ubuntu:latest. Add incompatible.


Preclude initiative data to cause downstream tasks

In some situations we need to load all data from underlying table thus we would choise the init option in cdc connector. Well it is a very nice design however these initiative data would cause downstream tasks that would make a duplicated ETL for the sake of that we had scheduled a batch ETL application before this cdc application. And there is latest option in cdc connector but this is not forward to our expectation because we need all the data from underlying table. So is there any way to load initiative data and preclude the downstream tasks which would be caused by them ?

Closing this issue because it was created before version 2.3.0 (2022-11-10). Please try the latest version of Flink CDC to see if the issue has been resolved. If the issue is still valid, kindly report it on Apache Jira under project Flink with component tag Flink CDC. Thank you!


File input styling issue with high DPI

Firefox 83
Windows 10
175% DPI

Chromium Edge doesn't have the exact issue; there's still a white background but it's smaller.
Noticed it while viewing the Cheatcheet. I'm not sure if there's something we can do as it seems a browser issue with high DPI and rounding.

can i do this


Publish Mongodb 4 image

Hi team,
Do we have an estimated date to be published Mongodb 4 image?

Hi,
this github repos contains files for three types of images: RHEL7, Centos7 and Fedora.
To request addition of a new Red Hat Software Collection please use http://bugzilla.redhat.com/. A new centos based image is added basically after rebuild of released RHSCL packages.
So now only Fedora based image for Mongodb 4.0 could be added. If you are looking for Fedora based variant, then I could add it.
If not, I would wait for RHEL variant. It's because of the fact, that automated building of fedora images is not working well right now and it has to be done manually. So a lot of fedora images is outdated. I'm currently working on it, so I would wait with adding image with only fedora variant till having working rebuild process.

I have opened a ticket at redhat for this https://bugzilla.redhat.com/show_bug.cgi?id=1705905

I'm sorry, but since the MongoDB upstream changed a license to SSPL for the server, we cannot add any further versions to the Fedora and RHEL. More information also available in https://fedoraproject.org/wiki/Changes/MongoDB_Removal.

Thank you @hhorak for posting this link.
Please correct me if I'm wrong: But shouldn't this repository be marked as deprecated or non supported? If I understand the MongDB removal from Fedora correctly it means that no version will ever receive any update ever again. Also not minor bug-fix updates.
I think this is quite an important point. users should aware of this when browsing this repo, wouldn't you agree?
For me it means that this repo mongodb-container is not suitable for long term use as it's not supported anymore. So I will need to search for alternatives.
Please correct me, in case I understood something wrong. I'm pretty new to openshift / k8 😄

Hi @BorntraegerMarc
there will be no new MongoDB versions (= no MongoDB 4.0 and onwards), but existing RHSCLs will still be supported according to their lifecycle. As long as the RHSCL RPMs are supported, the images will not get deprecated either.
Note that this is applies to CentOS and RHEL versions of images. Fedora versions will be quickly deprecated when there is no Fedora version that has MongoDB available.


Declarative Rendering

Hi guys, i have a problem related declarative rendering.
I am adding value (numbers) to  tags .  tags are editable.

and then i send to database. When it saves, i change the date at datepicker.

After date changed, Planned data is come on the page with AJAX request. This data is show with {{ ... }}
But data that i add on the page, some td tags can't change with data that come.

My code is below. I'm waiting your answers.

Hello! Please use our forum or Discord for questions like this.

Okay.


Upgrade Dask version

This PR moves us closer to a new coiled-runtime release
Closes https://github.com/coiled/coiled-runtime/issues/100

Software environment creation seems to be stalled for Python 3.10... I'm going to cancel the build it's it's already been going for over 1.5 hours

Okay, looks like we can't upgrade to the latest click=8.1.3 release as it's causing us to pull in an older version of coiled because coiled requires click>=7.1,<=8.0 to prevent versions of distributed<2022.04.0 from failing due to https://github.com/dask/distributed/issues/6013.
@dchudz @shughes-uk @ntabris question, thoughts on:

Updating the minimum version of distributed in coiled to be 2022.04.0? This would remove the need for pinning click at all in coiled, but my guess is this is too restrictive for all coiled users
Changing the click pin in coiled  to be click>=7.1,<8.1. This would allow us to install click=8.0.4 (which has a Python 3.10 build on conda-forge) with coiled while continuing to avoid https://github.com/dask/distributed/issues/6013

(1) seems way too restrictive! It's hard to imagine going from "we don't recommend anything later than 2022.01" to "you must use at least 2022.04.0" in one leap.
any downsides to (2)?

@jrbourbeau @dchudz -- Suggest we wait for 2022.05.1

(1) seems way too restrictive!

Yep, thought so but still wanted to jot the option down

any downsides to (2)?

Not that I'm aware of

Suggest we wait for 2022.05.1

This PR isn't the actual release, but does add handling around dropping Python 3.7 and adding Python 3.10 with more recent Dask releases. We can always bump the dask / distributed version again before releasing

See https://github.com/conda-forge/coiled-feedstock/pull/96 for the latest coiled=0.2.1 release which should resolve the issues we're seeing in CI here by updating the click version constraint for coiled

@ncclementi this PR should be ready for review -- could you take a look whenever you get a chance?


sample app 404

sample-app in the first step of Create local Python app (https://github.com/Azure-Samples/djangoapp.git) is not available.

Dokumentinformasjon
⚠ Ikke rediger denne delen. Den kreves for koblingen docs.microsoft.com ➟ GitHub-problem.

ID: 791bd216-532f-7f28-fa51-d95798397310
Version Independent ID: 4f7ff676-e4a5-cc41-6a43-ecb8fa1095fb
Content: Build a Python web app with PostgreSQL on Linux - Azure App Service
Content Source: articles/app-service/containers/tutorial-python-postgresql-app.md
Service: app-service-web
GitHub Login: @cephalin
Microsoft Alias: beverst;cephalin

@JoarGjersund Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @BryanTrach-MSFT,
I had the same issue as above when I was following the tutorial at https://docs.microsoft.com/en-us/azure/app-service/containers/tutorial-python-postgresql-app
I searched the Github page and found the following repo, which linked to the tutorial. https://github.com/Azure-Samples/flask-postgresql-app
This repo does not appear to match the tutorial, which it links to, however, as the repo is for a flask app, and the tutorial is for a Django app.
When I searched for a Django app, on GitHub, I could only find two more repos, both of which did not match the tutorial.
On the tutorial page, I looked at the last author @cephalin, and found another repo on his page, which did match the tutorial https://github.com/cephalin/djangoapp
After I cloned that and went through the tutorial, it worked.

@JoarGjersund @AndrewDitty https://github.com/Azure-Samples/djangoapp.git has now been made public. Sorry for the inconvenience and thanks for reporting.
#please-close


Question: generated entityview class does not use inherited fields

Given a POJO from a library code base:
class Pojo {
    private String id;
    public String getId() { return id; }
    public void setId(String id) { this.id = id; }
}

I would like to fill this POJO using entity views, so that I do not have to write verbose code to copy properties from my entity view to the libraries Pojo. So I came up with the following:
@EntityView(MyEntity.class)
abstract class PojoView extends Pojo {
     @Override @IdMapping public abstract getId();
}

To my own enthusiasm this works perfectly fine, but there is one thing that bothers me: the id field is recreated within the Pojo class. So in debuggers etc. the field lists up twice, once with a null value.
Is it perhaps an idea to use existing fields if available for entity view classes that extend abstract classes?

Description

Expected behavior

Actual behavior

Steps to reproduce

Environment

Version:
JPA-Provider:
DBMS:
Application Server:

Usually, the integration with existing models is done by using constructor injection like
@EntityView(MyEntity.class)
abstract class PojoView extends Pojo {
  PojoView(@IdMapping String id) {
    setId(id);
  }
}

The problem with reusing the existing field is when it comes to updatable entity views, as we aren't in control of the write access anymore if we use a foreign field.
I'm not sure if it would actually be possible to use the field in this case. It is private and since the getter that exposes the field is shadowed by the abstract getter, I don't think it's possible to implement proper field access. Or do you have an idea?

I don't think it is possible indeed. I remember calling the super of overridden default methods on interfaces, but it was quite a big hack and I don't think it'll work for classes.
Does the constructor mapping approach work for updatable entities? Do you somehow figure out the property name based on the parameter name (which should not work prior to Java 8)? Or are these fields simply not included in the changes tracked?
The constructor approach works for me, but I find it just slightly hard to see what mapping belongs to which field, especially with long annotations such as correlation mappings.
Alternatives that I can think of, but by no means are considered to be "better":

Allow non-abstract methods in entity view classes, that are expected to be bean property accessors (i.e. call super method). Obviously though, we can't really enforce/check that behaviour so possibly quite some weird stuff can happen here.
Introduction of an annotation that allows to add mappings on properties on a type level (somewhat similar to AttributeOverride in JPA I suppose). Getting this right may not be really trivial, because Mapping, IdMapping and other mapping annotations do not share a common type.
Accessing the field through reflection with the setAccessible(true) hack, but I think it would not really be appropriate to bypass the accessors, and I am not sure whether this use of reflection will remain supported.
Only reusing this for (package) protected or public fields, but this would seem fairly inconsistent.


Handle edge cases in 'authorized'

always recognize the original db author as authorized
recognize others as authorized when the only head is by the author in question

forgot to standard!


After everything is settled and updated, I'll open another PR to follow up with a switch to go mod.

(this is still in progress while I figure out the changes that need to be done for API registration, specifically:

componentconfig install
api install
descheduler scheme

all of which are done with outdated patterns using the k8s.io/apimachinery/pkg/apimachinery/announced and k8s.io/apimachinery/pkg/apimachinery/registered packages which are now deprecated)

Squashed this into more reasonable commits, it was green so hopefully it still is and ready for review

@damemi thanks for this PR and updating descheduler to 1.16. Its been pending for long long time so thanks a lot to you on working on this. It lgtm. Lets see if others have any feedback, and based on that we can merge this PR. Also once this PR is merged, i will cut a new descheduler release too.

/lgtm
again as I joined the org now.

bump, any more review for this?
cc @krmayankk @ravisantoshgudimetla

/lgtm

Feedback added, thanks. this will need another lgtm tag if that's all

@damemi  is it good to go?

@aveshagarwal all good from me if you can approve it!

/hold cancel
/lgtm
/approve

Awesome super cool thanks for your work


C3: Add bun support

Fixes #3941.
What this PR solves / how to test:
Adds support for bun along with e2e coverage.
Associated docs issue(s)/PR(s):

[insert associated docs issue(s)/PR(s)]

Author has included the following, where applicable:

[ x ] Tests
[ x ] Changeset (Changeset guidelines)

Reviewer is to perform the following, as applicable:

Checked for inclusion of relevant tests
Checked for inclusion of a relevant changeset
Checked for creation of associated docs updates
Manually pulled down the changes and spot-tested

Note for PR author:
We want to celebrate and highlight awesome PR review! If you think this PR received a particularly high-caliber review, please assign it the label highlight pr review so future reviewers can take inspiration and learn from it.

Quick question.... I think that bun is not really supported on windows right now, and only its runtime is available? (https://bun.sh/docs/installation#windows)
Should we add some checks to provide a graceful error message for users trying to use C3 with bun on windows?
(Or can we just ignore the bun windows incompatibility and if things don't work for windows users we just blame bun?)
PS: I don't have a windows machine so I haven't really tested the above 😅


Tor: ability to reuse tor process

@setnicka lately i've been reusing Tor process for multiple downloads since the starting of Tor was a big failure point in ulozto-streamer.
I made the re-use configurable, but latest changes will force me to create a new Tor process for each download.
Reusing is helpful when downloading a lot of files nonstop, otherwise i would start the Tor process each time.
https://github.com/setnicka/ulozto-downloader/blob/40a7720ce4ad7454490ad7d1376c1ac8b24fd9f1/uldlib/downloader.py#L70
I cleanup Tor for each download if property for Tor reuse is not set:
https://github.com/SpiReCZ/ulozto-streamer/blob/c2284fae5476308b4948c3e63999cba7ebb0d2fc/ulozto-streamer.py#L87

Sorry for the late reply, I have only a little time for this project alongside other work.
I will try to solve this in the next release, probably sometime during the Christmas holiday.

thx

I just published version 3.3.0 where this should be fixed (Downloader class not longer calling stop() method, it is documented now as caller responsibility).
Closing as fixed.


Remove "-M"/"print_mac" option.

This global option was specific to one network backend,
irrespective of it being configured via -s.
It is also uncertain that a VM will get a the same MAC
address on a second invocation, so the usefulness of the
option is questionable.
Signed-off-by: Rolf Neugebauer<EMAIL_ADDRESS>

It was also improperly indented, which is its biggest sin IMHO :-)
LGTM

Indeed...and undocumented


Cannot connect to the container from SSMS nor Azure Data Studio

Microsoft.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=95790; handshake=0;
Docker is up and running.
The container is up and running
Can exec into the container through the bash shell
This had been working as of winver 1909.  I am at windows version  2004 and now have these issues.
Pull the latest SQL Server 2019 Ubuntu image
docker pull mcr.microsoft.com/mssql/server:2019-latest
Verify that the docker image is on your system
docker image ls -a
Run the command below to start the container as is with no changes if you would like.
docker container run --name sql19 -p 13001:1433 -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=MyPassword" -e  "MSSQL_LOG_DIR=/var/opt/mssql/log/" -e  "MSSQL_BACKUP_DIR=/var/opt/mssql/backup/" -e  "MSSQL_AGENT_ENABLED=true" -h csci331-server -d mcr.microsoft.com/mssql/server:2019-latest
Check that your container is started
docker container ls -a

The client service was disabled by my internet security


Exponential backoff wip

@xethorn added an exponential backoff for swf throttling errors to try. we've noticed a lot of SWF throttling that the Workers eventually recover from, but produce a lot of Sentry alarms. This change will make these throttle exception alerting less noisy & reduce false positives alarms sent to monitoring tools.
I will add unit testing but wanted to get general feedback first

Coverage decreased (-1.2%) to 93.171% when pulling b3c23d967d3ca943af711876017405db3c599ad8 on someboredkiddo:exponential_backoff into 291cfa4d613f5cb9408d7ef14fb6d1bef51e0ce0 on xethorn:master.

Coverage decreased (-1.2%) to 93.171% when pulling 51d494435d7f2022b1140231153dc2745ef5eb0e on someboredkiddo:exponential_backoff into 291cfa4d613f5cb9408d7ef14fb6d1bef51e0ce0 on xethorn:master.


Doesn't compile on react native 0.66.4

No description provided.

add /node_modules/react-native/Libraries/Components/ScrollResponder.js from RN 0.63.4 to your project path(/node_modules/react-native/Libraries/Components/).
because ScrollResponder.js has been removed in RN 66


Improve performance of PrivateSymbolAnalysis

After integration of #10258, PrivateSymbolAnalysis compiler pass remains the most expensive compiler pass. Let's speed it up.

This is still the case as of Sep 20, 2024. Snapshot taken from a single Enso process invoked as part of sbt buildEngineDistribution.

As of 2fbd0aa92b7cb0c557dc37480ddb267ce8ad1fb9 the compilation of Standard.Base run with
enso --profiling-path base-compilation.nps --no-global-cache --no-ir-caches --no-compile-dependencies --no-read-ir-caches --log-level INFO --no-log-masking --compile built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/lib/Standard/Base/0.0.0-dev/

reveals that PrivateSymbolAnalysis is no longer a problem:

Similar results can also be seen when compiling Standard.Table.
Closing this issue as no-longer an issue.


Chronocam

The added module allows for accessing the chronocam device.
additionally python bindings are added.

I merged this request by command line and performed a squashed commit to remove unwanted excess files


[App Service] get-external-ip command doesn't support standard "name" parameter

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here: pip nightly
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here:
azure-cli (2.0.3+1.dev20170419)
acr (2.0.1+1.dev20170419)
acs (2.0.3+1.dev20170419)
appservice (0.1.3+1.dev20170419)
batch (2.0.1+1.dev20170419)
cloud (2.0.1+1.dev20170419)
component (2.0.1+1.dev20170419)
configure (2.0.3+1.dev20170419)
container (0.1.3+1.dev20170419)
core (2.0.3+1.dev20170419)
documentdb (0.1.3+1.dev20170419)
feedback (2.0.1+1.dev20170419)
find (0.1.2rc1+1.dev20170312)
iot (0.1.3+1.dev20170419)
keyvault (2.0.1+1.dev20170419)
lab (0.0.2+1.dev20170419)
monitor (0.0.2+1.dev20170419)
network (2.0.3+1.dev20170419)
nspkg (2.0.0+1.dev20170419)
profile (2.0.3+1.dev20170419)
redis (0.2.0+1.dev20170419)
resource (2.0.3+1.dev20170419)
role (2.0.2+1.dev20170419)
sql (2.0.1+1.dev20170419)
storage (2.0.3+1.dev20170419)
vm (2.0.3+1.dev20170419)
Python (Darwin) 2.7.13 (default, Apr  4 2017, 08:47:57)
[GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.38)]
OS Version: What OS and version are you using?
Answer here: macOS
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here: bash

Description
The az appservice web config hostname get-external-ip has a --webapp-name parameter, instead of --name, which is inconsistent, but more importantly, means that it doesn't naturally pick up a default web setting like all of the other az appservice web commands do.

Same thing like #2947. I would vote to fix it.


Improve lists in monitor.sh

When I try to provision a new device I don't know which one is new.
In monitor.sh the failed devices should be sorted by the time.
Alternatively a timestamp can be shown next to each device.

Feature request approved.


Kevincox hanging no executor fix 2

Merge in https://github.com/apache/spark/pull/7716
@angelini @solackerman @kmtaylor-github

He used a really great commit message /s
:boat:


Upgrade Hadoop from version 2.6.3 to 3.0.2

This patch updates the Hadoop version from 2.6.3 to 3.0.2 to match the version Accumulo is currently using and reap the bug fix benefits.

@ctubbsii I'd be happy to do the extra work and get some experience on that too but I'm clueless about the conflicts, would you care to elaborate? Does this have something to do with the Guava dependencies? Sorry for not being more knowledgeable right now.

You could look at the Accumulo history to see what they did, but basically, it's regarding the fact that Hadoop 3 packages its jars differently. Instead of a hadoop-client, there's a hadoop-client-api and a hadoop-client-runtime. There may also be other differences. Accumulo created a "hadoop.profile" property and different Hadoop profiles to handle the different options. I'm not sure if that is needed for Fluo or not, but it will give you a sense of what the differences are between Hadoop 2 and Hadoop 3. Fluo's dependency on Hadoop might be much simpler, and that might not be necessary. I'm not sure.

@ctubbsii Thank you for the guidance, I'll definitely  do that. I need to get more familiar with Accumulo anyways and sounds like there is a good model to follow.


Check for ico file in daily install script

PR Summary
Fixes https://github.com/PowerShell/PowerShell/issues/13077.
We now only try to set the icon for pwsh.exe when the ico file is in the payload.
PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

Dup #13060?

Closing in favour of #13060


fix typo in link to Github repository

fixed a typo in link to the GitHub repository

Moved PR to https://github.com/scikit-bio/scikit-bio/pull/2030


"npx<EMAIL_ADDRESS>fails

2017-10-02T08_43_52_006Z-debug.log
Maybe this is a bug with npm or npx, but I'm unable to start the franchise-client.
OS is macOS Sierra Version 10.12.6, node version is v8.6.0 and npm version is v5.3.0.
MacBook-Air:SomeDir$ LANG=en npx<EMAIL_ADDRESS>npm ERR! path /Users/heiko/.npm/_npx/6099/lib/node_modules/franchise-client/lib/server.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/heiko/.npm/_npx/6099/lib/node_modules/franchise-client/lib/server.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm E
2017-10-02T08_43_52_006Z-debug.log
RR!     /Users/heiko/.npm/_logs/2017-10-02T08_43_52_006Z-debug.log
Install for<EMAIL_ADDRESS>failed with code 254
The directory /Users/heiko/.npm/_npx/ is completely empty.

npm install -g franchise-client fails with the same error

This should be fixed with franchise-client version 0.2.7
The UI has been updated with the new version number.


fix(opencl-language-server): loose versioning

@mason-org/triage
 🤖 This is an automated comment.    📖 Source code


Fix for category check

since data structure looks like this:
array(3) {
  ["name"]=>
  string(10) "{}category"
  ["value"]=>
  string(15) "Foo bar"
  ["attributes"]=>
  array(2) {
    ["domain"]=>
    string(8) "category"
    ["nicename"]=>
    string(15) "foo-bar"
  }
}

you were checking on the wrong level and categories were imported into tags. After this small change, everything is imported as expected.

i think too much was merged - i don't get it - maybe it's because i asked to merge master from my fork? don't quite get how github works regarding pull requests...
i.e. this shouldn't be merged since it's a hack to fix migration of image captions provided as shortcode in WP:
https://github.com/lury/Scupltor/commit/e934a999a77cb43fcd114ec3f05126b47ee9895f

Damn serves me right for merging pull-requests when tired... pulling that commit out...

Okay fixed! Man it's a while since I've fudged git history like that!
Thanks for the patch!


Fix XEP-0080 geoloc extensions elements formating

XEP-0080 states that lon,lat,error,alt,accuracy,bearing and speed are
decimal values, and thus should either be present as decimal, or not present
at all (as they are optional elements).
Usage of String.valueOf(value) in code lead to creating a "null"
string in case number was not present, thus creating an element with
"null" content, which is not a valid decimal value.

Coverage remained the same at 36.18% when pulling 88d31facd9705cbb17dc79381e6dd1ae49239edf on dant3:XEP-0080 into 5272680d477937b96c11353e320847a8fe8dc6c7 on Flowdalic:master.

Thanks. Picked as cf2027fce7828edce0aa59b46ce3df7d17eca793


Error: videojs-contrib-ads has not seen a loadstart event 5 seconds after being initialized

We are implementing prebid to generate our adTagUrl. The ima plugin is initialised after the adTagUrl is generated.  We've never seen the error before this, through multiple implementations using ad tags from different sources.  We've attempted to fix the issue via code changes in our code base to no avail.
The basic flow of our code looks like this:
const player = videojs('my-player', options);
auction(options, (adTagUrl) => {
  const imaOptions = {};
  player.ima(imaOptions);
});

Setup:
Video.Js 7.4.1
videojs-contrib-ads 6.6.4
videojs-ima 1.6.0

Hi,
It seems that you're having issues with your pre-bid implementation, I was not able to reproduce the behavior using the advanced example sample. Have you tried reproducing the behavior after upgrading to the latest version of the plugin?

So it turns out it was in fact our implementation.  We managed to get it sorted right before closing up shop for the weekend.
Prebid delayed the init long enough to cause issues.  We changed the order of implementation and it sorted itself out.
Thanks for your help and quick reply!


Use RgxGen to cope with StackOverFlow

fixes #1091

I don't think we can depend on snapshot versions. If they publish a new version, we would have no idea what kind of code we get into our library. I don't think this would be an acceptable  situation.

based on the commit history they are not going to do it...
the latest commit was more than 8 months ago...

I don't really care how often they release, I care that we don't depend on snapshots for production releases. Maybe they change the api in a year, then it would break every Datafaker release depending on the snapshot, including older versions. If they would introduce something malicious, we would download this too automatically. So no, let's not do this.

Wouldn't that be true of any dependency?

it is already a a part of the PR or do you mean something else?

All good, I totally overlooked it 🤦♂

2.0.0 has been released!

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.29%. Comparing base (b37c566) to head (9ee5015).
Report is 12 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1092      +/-   ##
============================================
- Coverage     92.35%   92.29%   -0.06%
+ Complexity     2821     2820       -1
============================================
  Files           292      292
  Lines          5609     5610       +1
  Branches        599      598       -1
============================================
- Hits           5180     5178       -2
- Misses          275      278       +3
  Partials        154      154

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

thanks for letting know, updated to use released version

Merging since now there is no SNAPSHOT version in deps


chore(#207): v5-dev branch becomes main branch

[ ] (In Progress) Replace all v5-dev references by main
[ ] Change the v5-dev into main in the settings
[ ] Verify that the PRs whose target was v5-dev were automatically updated
[ ] CI jobs now have to be green in this PR
[ ] Merge me!
[ ] Modify the Wiki
[ ] Remove the master branch (which contains the same thing than v3-dev

The next time we will execute npm run release, the following files will have their header modified with https://github.com/orange-opensource/orange-boosted-bootstrap/blob/main/LICENSE:
	modified :         config.yml
	modified :         dist/js/boosted.bundle.js
	modified :         dist/js/boosted.bundle.min.js
	modified :         dist/js/boosted.esm.js
	modified :         dist/js/boosted.esm.min.js
	modified :         dist/js/boosted.js
	modified :         dist/js/boosted.min.js
	modified :         js/dist/alert.js
	modified :         js/dist/base-component.js
	modified :         js/dist/button.js
	modified :         js/dist/carousel.js
	modified :         js/dist/collapse.js
	modified :         js/dist/dom/data.js
	modified :         js/dist/dom/event-handler.js
	modified :         js/dist/dom/manipulator.js
	modified :         js/dist/dom/selector-engine.js
	modified :         js/dist/dropdown.js
	modified :         js/dist/modal.js
	modified :         js/dist/offcanvas.js
	modified :         js/dist/popover.js
	modified :         js/dist/scrollspy.js
	modified :         js/dist/tab.js
	modified :         js/dist/toast.js
	modified :         js/dist/tooltip.js

But this is not the case for dist/css/*.css and dist/css/*.css.map files. Haven't figured out yet if I have to modify them manually one time or not.

If I run npm run release, the last remaining v5-dev reference is within js/dist/dom/polyfill.js. Is it normal to have this file, this is the only one in this repository to be in v5.0.0-beta2 (and that doesn't exist in Bootstrap: https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/v5-dev/js/dist/dom vs https://github.com/twbs/bootstrap/tree/main/js/dist/dom)?
Is it removable?

In some files, we have some
/**
   * --------------------------------------------------------------------------
   * Bootstrap (v5.1.0): util/backdrop.js
   * Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE)
   * --------------------------------------------------------------------------
   */

Must verify if it is normal since their master branch doesn't exist anymore

If I run npm run release, the last remaining v5-dev reference is within js/dist/dom/polyfill.js. Is it normal to have this file, this is the only one in this repository to be in v5.0.0-beta2 (and that doesn't exist in Bootstrap: https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/tree/v5-dev/js/dist/dom vs https://github.com/twbs/bootstrap/tree/main/js/dist/dom)?
Is it removable?

Did some archeology.
Removed via https://github.com/twbs/bootstrap/pull/32057/commits/d3809443c96f9261820e35171cff1e68c054e559 and after that with https://github.com/twbs/bootstrap/pull/32310/commits/e01d74d0bdeb25701a7e466f86f52e1982632fb0.
We don't use or import this JavaScript file so I think it is safe to remove it (done via https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/pull/792/commits/1dfda1e1cf7868e62431a75c018c736be9f668e3).

In some files, we have some
/**
   * --------------------------------------------------------------------------
   * Bootstrap (v5.1.0): util/backdrop.js
   * Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE)
   * --------------------------------------------------------------------------
   */

Must verify if it is normal since their master branch doesn't exist anymore

They've got the same problem so it has no impact for this PR. This is "normal".

Ready for a code review 🤓 before working on the next steps in the description.


Support for Regex Validation of Text Inputs

When using Dialog to gather information via textfields, it would be helpful to have the option to validate a user's input at the time they submit the form. This can improve accuracy by only recording data provided in an expected format (for example, in scenarios where a provided input should align to a standard). This can also reduce frustration by avoiding the need to re-display the form should a provided value not be formatted as expected, allowing the user to see the error prior to the window closing and allowing them to edit what they provided and try again.
This might be accomplished by checked the provided value against a regex string at the time the user clicks the default button. If validation is successful, Dialog outputs the values and exits 0.
If validation fails, Dialog would follow a similar functionality as when a required field is left blank. The window would not close and the field would be highlighted.
Suggesting two optional properties be added to textfield for this:
validation : Accepts regex patterns
validationerror : (Nice to have) Accepts a string so an admin may define custom error text to display above or below the field that failed validation. If not provided, could default to something like "{Textfield Name} is not in the correct format."
Example (validating if technician provided Asset Tag value is a six digit string:
dialog --textfield "Asset Tag",required,prompt="000000",validation='^\d{6}$',validationerror="The asset tag provided is not valid."
{
  "textfield" : [
    {"title" : "Asset Tag",
     "required" : true,
     "prompt" : "000000",
     "validation" : "^\\d{6}$",
     "validationerror" : "The asset tag provided is not valid."}
  ]
}

@saladd-bu let me know what you think of this:

I haven't settled on the name of the fields yet. ("validation" or "regex" etc)

Addressed in https://github.com/bartreardon/swiftDialog/commit/9c098796b9638aaa570d508656a90aff419a53b4
Merged into dev branch and will tweak a little but this will be a feature release in v1.11

Apologies for the second reply, but I encountered a potential character issue. If a regex contains commas, using command line parameters will cause an unexpected behavior in which:

The field name becomes the last string chunk following the last comma in the regex
Validation fails since the regex is not valid anymore

This does not occur when using -jsonfile
Sample for comparison:
--textfield "Asset Tag",prompt="000000",regex='^\d{6}$',regexerror='Asset tag must be a six digit number.' \
--textfield "Computer Name",prompt="IST-CSS-ML-0000",regex='(^\\w{2,5}-(\\w{1,4}-)?[Mm]([Ll]|[Dd]|[Kk])-\\d{3,4}$)|(^(LNR|lnr|SPR|spr|TST|tst|RSV|rsv)-\\w{11,12}$)',regexError="Computer name does not align with CTS standard."

{
  "textfield" : [
    {
      "title" : "Asset Tag",
      "required" : true,
      "prompt" : "000000",
      "regex" : "^\\d{6}$",
      "regexerror" : "Asset tag must be a six digit number."
    },
    {
      "title" : "Computer Name",
      "required" : true,
      "prompt" : "IST-CSS-ML-0000",
      "regex" : "(^\\w{2,5}-(\\w{1,4}-)?[Mm]([Ll]|[Dd]|[Kk])-\\d{3,4}$)|(^(LNR|lnr|SPR|spr|TST|tst|RSV|rsv)-\\w{11,12}$)",
      "regexerror" : "Computer name does not align with CTS standard."
    }
  ]
}

hmm - ok, I can look at that. It will be because , is being used as the field separator in the argument so  will see (^\w{2,5} and break the regex command after the 2. Will have a tinker and see what I can come up with.

json of course doesn't have that issue as it's json, not a string of text being interpreted as CSV

+1
I learned today that most of our Asset Tags are seven-digits, so it'd be nice if I could get ^[0-9].{6,}$ to work.

ok - I think I have a neat way to handle this without requiting any syntax changes. Will post a preview build to the swiftdialog slack later today

available in 1.11


The --java-version option doesn't prevent "gradle init" from entering interactive mode, as expected

Current Behavior
The gradle init --java-version option doesn't work as expected since gradle still enters the interactive mode and ask for the Java version (which defeats the purpose of this option)
Expected Behavior
When the --java-version option is used, gradle init should not enter interactive mode to ask for the Java version
Context (optional)
No response
Steps to Reproduce
Everything to reproduce is described in details here
https://github.com/gradle/gradle/issues/26598#issuecomment-1869513296
Gradle version
8.5
Build scan URL (optional)
No response
Your Environment (optional)
The most important info about the environment are  described in the link provided above through SDKMAN commands

Some more info to help debug.
When using the --java-version option, grade not only asks (in interactive mode) for the "Java version" but also for the "new API" question. When you provide a value through stdin gradle doesn't enter interactive mode at all, even though only one answer is provided.
The command below does not enter interactive mode
echo 'no' | gradle init --type java-application --dsl groovy --project-name s3onezoneexpress --package com.teevity.sandbox.s3onezoneexpress --test-framework junit-jupiter

Not sure how this can help but as it doesn't seem very consistent, it probably does

I can confirm this issue with Gradle 8.5.

Thank you for providing a valid report.
The issue is in the backlog of the relevant team and is prioritized by them.

This indeed should skip interactive mode, I'll take a look.

This was already fixed by https://github.com/gradle/gradle/pull/27408 which is part of 8.6 RC1.


Some WLM uploads have null country code

Summary:
This was discovered by @neslihanturan , I am just documenting it here. Some of her uploads return a null country code, both when geotagged and when not geotagged. Thanks to #4574 we will not actually be putting out templates with null country codes, however this bug does mean that when it happens, the user's upload will not be included in the WLM 2021 contest and will not generate templates. So we should fix this ASAP.
Steps to reproduce:
I have not been able to reproduce the issue.

Closing this as I believe we are not supporting the current WLMs.


Setting for validate "on_post_save"

For Sublime's own files (e.g. .sublime-settings) comments are allowed like this:
{
    "setting1": true,
    // "setting2": true,
    "setting3": true
}

As there is no setting to stop the plugin from validating on save, it always gives a JSON error.
Adding
16:    auto_val = s.get("validate_on_save", False) // or True
17:    if auto_val and "JSON" in view.settings().get('syntax'):

to PrettyJsonListeners.py should be an easy-to-implement solution to turn off post save validation, if a user is willing to do so

sorry mate, will bring out setting to turn it off. thanks for raising

put "validate_on_save": false into your user settings. thank you again for reporting this

Thanks for the quick response and implementation!


Suggestions: Admin Manager

#1 -- Make it so admins of a certain amount of permissions cannot edit those with higher amounts of permissions. For example, someone with 5 permissions shouldn't be able to edit someone with 10 permissions. Perhaps have a toggle where in addition to managing admins, there can be an additional one granting access to managing permissions for said admins. Could reduce the amount of abuse.
#2 -- Sort "Admins" based on their access levels (highest to lowest) in the admin manager.
#3 -- Design a template system for big servers where we can select from drop-down permissions that all one rank should have in the server.
#4 -- Long-term idea, for communities and organizations that run multiple of the same style server, perhaps have a way to connect them through an API so you can add one user to say, three different servers for example.

Item 4 is ready.
You just have to run fxserver multiple times with different profile names, and the admins will be synced.

Item 4 is ready.
You just have to run fxserver multiple times with different profile names, and the admins will be synced.

So this is great if they're all on the same machine, but not ideal for large organizations that run on separate dedicated environments, such as us for example.

Kinda of an edge scenario.
Set one server to be the "master one", and then configure a tool like rsync to auto sync the admins.json from that server to the other ones.
Should work.

Kinda of an edge scenario.
Set one server to be the "master one", and then configure a tool like rsync to auto sync the admins.json from that server to the other ones.
Should work.

Hmm. You actually just gave me an idea of keeping it in sync using Git.


Reported doubling times in table have strange intervals

At the time of writing, Table 1 on https://epiforecasts.io/covid/posts/global/ has some bizarre entries, such as Australia's doubling time of -71 (7 – -6), or Austria's of 440 (15 – -16). Belgium has -14 (-22 – -10), which indicates the issue might be the way doubling/halving times are reported back to the table when the interval contains 0.
Cameroon is 110 (15 – -21) and the estimate is not contained within the interval at all. Same with Cote d'Ivoire, 51 (9.7 – -16). Croatia is -10 (15 – -3.8). Bahrain is 200 (17 – -20). These are reflected in the national summaries, e.g. https://epiforecasts.io/covid/posts/national/cameroon/ and it's clear that there's something wrong when converting from growth rates to doubling/halving times.

The crux of the issue there is that the doubling time is calculated from the growth parameter and when this is 0 the doubling time is infinite, and when the growth parameter is close to 0 the doubling time tends towards a signed infinity based on the sign of the growth parameter.
To fix the plotting, a daily overplotted linerange (similar to Figure 1 here could replace the ribbon visualisation of time-varying doubling time.
To fix the reporting of doubling time in the table, the mean should be replaced by the median as it's guaranteed to be within the 90% interval and for most settings the mean and median will be similar. Also the doubling time is calculated after the summary statistics which is fine for quantiles but not moments. So perhaps the mean ought to be calculated separately and cbinded on.

The error occurs in doubling time data in all rows in which there is a negative in the credible interval, as observed today (7/2) at https://epiforecasts.io/covid/posts/national/united-states/.  If one terminus of the credible interval is <0, then the reported mean value falls very far outside the reported credible interval.  It's possible for a mean value to fall outside the credible interval, but it seems very unlikely this would only occur with negative credible termini, and it seems unlikely it would always be so far outside the range.  Replacing with median might correct a data presentation problem, but I am suspicious there is an  underlying assumption problem.

Hi @hutchenm ,
Thanks for flagging this. As the doubling time is an inversion of the growth rate as the growth rate approaches 0 the doubling time approaches infinity. Then when the growth rate cross 0 the doubling time becomes -Inf and then decreases. This means that the CI should be understood as going via Inf and not through 0.

Aha, I get it - the center of the interval is infinity.  There might be a way to notate that in the chart, as it's an unusual way to have an interval presented in medical data science.  Or maybe what you are doing is just standard and I should learn.

Diagrams on doubling time look very scrambled when the country moves around R_t=1, meaning if there is a frequent crossing above and below 1 that results in vertical bars when the doubling time jumps from pos. infinity to neg. infinity and back. These graphical elements give no extra content to the reader, but only distract from the important facts. Therefore my proposal is (hopefully not too complex to implement) not to display these vertical bars and filter the R_t = 1 crossings out from the doubling time diagram. Doubling times of e.g. more than two months are not interesting, as the usual range which is shown is +-40 days.

Good discussion on this. We are moving to an updated approach an no longer report the doubling time over time so closing this.


⚠ Bofrost.be has degraded performance

In 8d881dd, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 923 ms

Resolved: Bofrost.be performance has improved in dcc9e53 after 13 minutes.