Discovery: Searching for published articles

Discovery research topic
Researching the way in which early years researchers and experienced researchers locate and use published articles
We hypothesise that
Our users may not be looking to a library catalogue to identify articles of interests as tools such as google Scholar and pubmed are often favoured for this task
We are right if we see
Researchers actively seeking article content on websites other than library catalogues
Research methods

Desk research
Interviews with 3 early years researchers and 3 advanced researchers
A survey asking specifically whether participants use articles and where they find them
Search term analysis
Library help desk

Recruiting 5 researchers who use articles and journals in their work w/c 7th December

Research Brief: https://wellcomecloud.sharepoint.com/:w:/s/wcdigitalexperience/Efh_63wWUttAgPwIpUZSpH0BYz77iAkdVu2Dgffi-ywjDQ?e=ybtOsV
Research Script: https://wellcomecloud.sharepoint.com/:w:/s/wcdigitalexperience/ERWqn8BOFHtPpZ2jGLcKWbIBdh8aRhUrii0LEH864DDIdA?e=Lmhze1


Allow passing a input slot to InputChip

Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!
I've made a mockup using my focus popup PR, slightly modified since the iframes caused document.querySelector to misbehave.
https://stackblitz.com/edit/skeletonlabs-repl-ja71ar?file=src/routes/+page.svelte
By allowing the user to provide their own input element, users can use different types of input (number etc), or listen to events on the input. Skeleton can still provide its existing input element as the fallback slot, so this would be fully backwards compatible.
I thought of this as a way to get a popup Autocomplete working for InputChips.
2 slot variables are needed, since the bindings only go from parent to slot, not the other way around (we can't bind:value). One to store the current input. value, and another to listen for the value changing. The on:submit handler on the form can be kept as is.
What type of pull request would this be?
Enhancement
Any links to similar examples or other references we should review?
No response

@Cucumberrbob as mentioned on Discord I owe you a proper response to this suggestion. I'll aim to get this asap this week

@Cucumberrbob I actually updated the Input chips to use an input property instead of a slot. This allowed us to handle what I think you were describing above. This is now merged into dev. Please feel free to review and if this meets your requirements then feel free to close this out. Otherwise we'll circle back next release.

this works almost exactly as well as allowing an input slot. The only thing you lose is the ability to have say a <input type="numeric">, but that's not a massive issue


Create Additional Informative Blocks for Resume

Description
Enhance the resume by adding additional informative blocks that present useful information in an engaging and informal manner. These blocks can include personal preferences, strengths and weaknesses, skills and hobbies, infographics, or interactive modules. Content for these blocks should be created before starting the layout design, as their sizes will impact the placement of elements on the page.
Tasks

Brainstorm and Selection:

Brainstorm potential additional blocks to include (e.g., likes and dislikes, strengths and weaknesses, skills, hobbies).
Select the most relevant and engaging blocks to include in the resume.

Content Creation:

Write content for each selected block.
Ensure the content is engaging, informative, and presented in a light-hearted manner.

Education, project experience, additional education


Add blobless-block rpc endpoint

          > Alternatively, the Tendermint block endpoint could be modified to unwrap the BlobTx into Tx before returning it.

this is an idea we can explore! thanks for the good rec @blorgon1 . We'd have to implement the "blobless" block in a separate endpoint to not also break some important downstream things ofc, but this seems like the simplest change.
Originally posted by @evan-forbes in https://github.com/celestiaorg/celestia-app/issues/2715#issuecomment-1770985006

closing in favor of a more recent #1136


Idea: long-lived federations in staging environment for testing upgrades

Once we have a release candidate that passes all upgrade tests, it would be useful to attempt upgrading a long-lived federation in a staging environment.

@dpc Assigned you since you started setting up the hetzner boxes today

Status update: the boxes are set up and deployed: https://github.com/fedimint/fedimint-infra/blob/main/hosts/fedimintd/fedimintd.nix , but I was unable to pass DKG. Might try again with more stable version of the ui that is entirely client-side.

DKG passed.
Invite code: fed11qgqzjfmhwden5te0vejkg6tdd9h8gepdxq6zuer9wchxvetyd9kkjmn59ehhyee0waej7qgpyq2hex742xy9vvt757jzv5ehm4zpw3w5ss66zs0lxpt50e6n0y8wx3gfep0


Fix output of --version

Running Godot with the --version flag would previously give the following error after outputting the version:
ERROR: Condition "int32_t(p_level) != level" is true.
   at: deinitialize_extensions (core/extension/native_extension_manager.cpp:101)

This change prevents this error message by returning early from deinitialize_extensions.

This appears to be fixed as of master fb2802578, closing.
❯ godot --version
4.0.alpha.custom_build.fb2802578

Thanks for the contribution nonetheless :slightly_smiling_face:


Tidy contributor/developer guide

Since we need to keep CONTRIBUOR.md as the contributors guide,
renamed the documentation version to Developer Guide.

Codecov Report

Merging #863 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #863   +/-   ##
=======================================
  Coverage   34.49%   34.49%
=======================================
  Files          57       57
  Lines        3902     3902
=======================================
  Hits         1346     1346
  Misses       2398     2398
  Partials      158      158

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 4984ef0...bedb3de. Read the comment docs.


Disallow teleporting across shards when combat tagged

Whole world of duping can occur if player is combattag and they spawn an npc and teleport over.  Easiest is just to never allow it to happen.

Finished, just need to upload.


common openapi data sampling strategy for kpt+kustomize

Notes started here:  go/openapi-in-kk

@monopole go link on public repo ?


command 'livePreview.start.preview.atFile' not found

how can i solve this problem?

Does this still happen when you reload the window?

Yes

Does this still happen when you reload the window?

Yes

how can i solve this problem?

I have successfully solved this for myself
First, go to uninstall dropdown and click on Install another version. Install version 0.4.2
not 0.4.7 which is the current version on 8.5.2023. Reload vs code and now you should be able to livePreview inside the vs code.
Before this, I opened the settings.json file and wrote
"livePreview.autoRefreshPreview": "On All Changes in Editor"
because my live preview wasn't live and only showed me changes in browser after I saved the code.
Hope this helps

@andreamah Yes it did for me.

When you run into the issue, what logs do you get when you go to the Output panel and go to the Extension Host channel?

Are you all on codespaces or another remote? Or is this just in vscode desktop?

I have the same problem using VSB on PortableAps  <IP_ADDRESS>. I will try the older version as mentioned above.
Version: 1.73.1
Commit:<PHONE_NUMBER>f055b99068d3688932416f2346dd3b
Date: 2022-11-09T04:27:29.066Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

Are you all on codespaces or another remote? Or is this just in vscode desktop?

hello, this happened to me and yes im running vscode on remote. my version is 0.4.8. and test several older version .4.7 .4.6 .4.5 and its work from 0.4.5 or lower only. non of 0.4.8 0.4.7 0.4.6 works.

What remote were you running on?

@andreamah , I installed mine on a USB drive under PortableApps (see my comment above) and use vscode on a laptop not connected to anything. No wifi or internet connection possible.

Does this also happen if you use the latest version of vscode?

@andreamah ,
Today I tried again.  I formatted a USB Flash drive,  downloaded and installed PortableApps.com Platform 26.2.3,
I then downloaded VSCode-win32-x64-1.84.0.zip from code.visualstudio.com/download,
unzipped that to a /temp folder. Since there is no readme file, I skimmed the license (it would take a week to read) hoping to find installation instructions (none). So I just unzipped to F:\PortableApps\vscode-portable.
PortableApps did not find VSC there.
By using File Explorer I navigated to F:\PortableApps\vscode-portable\Code.exe. That did open VSC Ver
I now have Version: 1.84.0
Commit: d037ac076cee195194f93ce6fe2bdfe2969cc82d
Date: 2023-11-01T11:29:04.398Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Yes, Installing Live Preview Ver 0.4.11 appears to work now.
Question 1: How do I tell PortableApp this is here?
Q 2: How do I set the path to save files?
Thank you.
-- Fred

how can i solve this problem?

I have successfully solved this for myself First, go to uninstall dropdown and click on Install another version. Install version 0.4.2 not 0.4.7 which is the current version on 8.5.2023. Reload vs code and now you should be able to livePreview inside the vs code. Before this, I opened the settings.json file and wrote "livePreview.autoRefreshPreview": "On All Changes in Editor" because my live preview wasn't live and only showed me changes in browser after I saved the code. Hope this helps

It works . Thank You

Are you all on codespaces or another remote? Or is this just in vscode desktop?

hello, this happened to me and yes im running vscode on remote. my version is 0.4.8. and test several older version .4.7 .4.6 .4.5 and its work from 0.4.5 or lower only. non of 0.4.8 0.4.7 0.4.6 works.

@MioJeong which remote where you on? Was it SSH or codespaces? And were other extensions working fine?

@andreamah , Thank you, ma'am.
To update, I download the new version and un-zip it in to the location.
PortableApps' menu does not show VSC.
The question is a request for instructions to have VSC appear in the menu.
Thank you. Merry Christmas.

For vscode to appear in a menu in PortableApps, you will need to consult their website- it's thrid-party, so it's not supported on this issue tracker. You can try looking at their forums? https://portableapps.com/forums

Thank you, @andreamah . A search there is how I found a working version of VSC. They also say that "The software license is fine, but being a Microsoft product I would assume there is a trademark on the name/logo as there is with Firefox - it is open source, but the name & logo are trademarked so derivative works cannot use them without permission."
Yes, I can use it from a portable USB drive by navigating to the folder.

Does the download instructions from here help?
https://code.visualstudio.com/docs/editor/portable
I am not too familiar with how PortableApps works.

@andreamah, yes, by linking to https://code.visualstudio.com/download and getting the .zip from there. "Portable mode is only supported on the Windows ZIP archive. Note as well that the Windows ZIP archive does not support auto update."

Oh okay. That should be the current limitation, then. You can try to file an issue on the main vscode repo for support on something that auto-updates, but I cannot guarantee that we will be able to support that.

In reality I don't need to update. For my purpose, any working version is fine.

Is what you currently have okay for now, then?

@andreamah , yes, ma'am.
A simple, dirty batch file works and the kids can use it. Just insert the USB stick, navigate to that drive letter, and type "go".
go.bat is
PortableApps\start.exe
rem You must click back in this window to continue:
pause
PortableApps\PortableApps\vscode-portable\vscode-portable.exe
exit

I am sorry for reviving this thread, but this problem still persists. On a fresh local desktop install it throws a livePreview.start.preview.afFile not found message but when switched to 0.4.5 it works.

I am sorry for reviving this thread, but this problem still persists. On a fresh local desktop install it throws a livePreview.start.preview.afFile not found message but when switched to 0.4.5 it works.

Hmm, that's strange. Is 0.4.5 the latest version that works for you? And this is the latest version, right?


how to change datasets and scaleLabel name together and then update the chart?

i can change the datasets and then update the chart, but i also need to change the name of the xaxes with the same change. is this possible? if yes how? or what else do i have to do to change the datasets and the xaxes labelString together?

@olisch this is possible but its not ideal. You'd need to lookup the scale in the chartInstance.scales map then change the correct stuff in the options object on the scale

i know its not ideal, but the label just changes from 'days' to 'months' (and back) with a checkbox and the yaxes stays the same.
your solution sounds good. but as i am not that much into javascript, maybe you can point me more detailled in the direction of finding the scale in the map? i managed to replace the datasets only changing this word is missing...
thank you for your help!

Closing as duplicate of #2060
To get the scales you can look at the chartInstance.scales object. The keys will be string IDs and the objects will be the scale itself. scale.options is where you make changes


chore: enable fixes in Windows 2023-10B

What type of PR is this?
/feature

What this PR does / why we need it:
enable fixes in Windows 2023-10B
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2234

Relevant Lines:
2822

💛  - Coveralls


Add an MSBuild target to set MsBuild.exe path

Fixes https://github.com/aspnet/AspNetCore-Internal/issues/1614

Updated

...of course, wait till CI checks pass. I think this should fix the only 2 remaining test failures on 2.1 PRs.

I don't know what's going on. It passes just fine for me locally. It still fails on the CI. @natemcmaster, any clue why that could be?

My guess is the problem would reproduce locally on a clean build.
<Compile Include="$(BuildVariablesGeneratedFile)" Condition="Exists('$(BuildVariablesGeneratedFile)')" />

This is evaluated statically, before the target to generate it exists, so it BuildVariablesGeneratedFile will never get added to the <Compile> item group on  CI build.


Conditional content

Is there a way to apply tags to hide content in the output Word doc if the condition isn't satisfied?
Apologies if I missed this somewhere...
For example:
{if:warrantyIncluded=yes}
This is the paragraph to show if warranty is included.
{/if}

Never mind. Sorry!


Fix new "Test updating advertising and parallel data transfer" and test its functioning on 3 devices

We're going to fix this test after fixing test server and when we will have bluetooth tests on native layer

Added some more native tests for StreamCopyingThread

The test is still not reliable on Android

I still can reproduce it on 3 samsungs

@vasilevskayaem I assume you meant that it still fails on 3 samsungs?

@yaronyg yes, I saw this failure a week ago


Add Django 3.0 support

Is your feature request related to a problem? Please describe.
I'm trying to upgrade my project (which has pinax-stripe as a dependency) from Django 2.2 to 3.0, but it looks like pinax-stripe does not yet support Django 3.0.
More specifically, pinax/stripe/models.py has the following import:
from django.utils.encoding import python_2_unicode_compatible

but this was removed in Django 3.0 due to Python 2 EOL.
Describe the solution you'd like
Since Python 2 has reached EOL, I think it would be acceptable to drop support for it. If that was done, this decorator wouldn't be necessary.
Additional context
It could be that there are other incompatibilities with Django 3.0, I have not checked beyond this issue.
Thank you for this project, I have found it very helpful!

@RevolutionTech Glad you have found this project helpful! We have a new release in process that will drop Python 2. Both @paltman and @mfonism have mentioned making updates. I'm not sure when it will be completed, but it is on our radar!

There are any news about Django 3 support?
Should I downgrade my Django project to Django 2 in order to be able to implement stripe with your package? Seems the best stripe package for Django.
Thank you, I'm looking forward to use pinax-stripe on my project.

@goromachine Unfortunately, there is not any news at the moment. @paltman and @mfonism have not been able to get to it and I'm finishing up the other parts of the release.

What is the update?

Hi, any update about this issue? is there any help needed?

This is now done for both pinax-stripe-light (soon to launch) as well as the original branch (see #645 for announcement on the split)


Bug when executing external process from Java application

These commits fixing two bugs.
The first bug was impossibility to run an external process from the Java application in the .dmg file. This was caused by a missing executable flag for a helper application named jspwanhelper.
The other fixes the JRE detection which was buggy. This leads to duplicate JRE files in the .dmg file.

Thanks. I will review soon : )

Sorry, but reworked it again. It is now faster, safer and more elegant ;)

@federkasten do you think this pull request can be merged as well and new version released with all the recent changes?

@azhemoytuk Sorry for late. I will review and release in this week.


From Mrs Searle: Font needs to be changed

The font looks like a typewriter font, old fashioned and mono-space.

Easy fix, changed font to Roboto from Google fonts
before:

After:


[compiler] Added support for preserving locations of aliased identifiers

Motivation
This is a fix for a problem described in https://github.com/move-language/move/issues/84. In short, we want to preserve locations of identifiers that are aliases to modules or module-level definitions. It fixes the problem more generally (e.g., also for Pack and other AST nodes).
Have you read the Contributing Guidelines on pull requests?
Yes

Based on the wrong branch...


Fix the navbar visibility in Community & Blog pages

Description

The navigation bar of Community & Blog pages of Meshery page has gone completely blended with the background. As a result, nothing is visible on the navbar after the landing of the respective pages, but it becomes visible on scroll. This issue pertains for both desktop-view & mobile-view.
Expected Behavior
Make the navbar visible. Follow the screenshots provided below.
Screenshots
Currently the Community looks like this :~

It should be looking like this :~

& for the Blog page, it's :~

It should look like this :~

Notice the navbar in both of the above references.
Environment:

Browser: [e.g. Chrome, Firefox, Opera]
Device: [e.g. laptop, Android 10]

[Optional] To Reproduce
Steps to reproduce the behavior:

Go to Community & Blog pages
Inspect the navbar
Scroll down a bit.

Hi! I'm interested...

The issue is opened in wrong repo. I am migrating it to the correct one and assign you there you there @McZenith


ubuntu gdb Segmentation fault

run_qemu.sh  --git-qemu --rebuild=none --cxl --cxl-test --cxl-debug --gdb
/usr/local/bin/run_qemu.sh: line 1319: 288649 Segmentation fault      (core dumped) "${qcmd[@]}"

help

@shawn8172014  are you still seeing this? Can you try with the latest qemu (does your qemu branch have any modifications or was it just upstream?)

help

Can't help without versions, detailed reproduction steps and longer logs. That single line is not even enough to tell what is specifically crashing. If it's QEMU then this tracker is not the right place.

Please:

reproduce with more recent versions
share detailed steps and versions
re-open


Bring in LGTM fixes in to 9.1.x

We had a lot of fixes from the lgtm report go in to master. We should bring these back in to 9.1.x
There is a pr, https://github.com/apache/trafficserver/pull/6429, that has these all picked in which we can hold for 9.1.x

Do you mean 9.0.x? 9.1.x is not branched yet.

@masaori335 I dont know what @zwoop 's plan was, he just mentioned wanting these in 9.1. Not sure if we want to hold off for that or put them in 9.0


Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "ScaledObject" in version "keda.k8s.io/v1alpha1"

A clear and concise description of what the bug is.
Expected Behavior
On installing a release on kubernetes using helm 3.2.1. The function should get deployed automatically
helm upgrade --namespace funcapps --install --wait --create-namespace --set image.tag=placeholdertag,image.repository=acrplaceholder funreleasenam placeholderfunccharts
Actual Behavior
Getting below error on helm install of the release
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "ScaledObject" in version "keda.k8s.io/v1alpha1"
Steps to Reproduce the Problem

helm repo add kedacore https://kedacore.github.io/charts
helm repo update
helm install --namespace keda --wait keda kedacore/keda
helm upgrade --namespace funcapps --install --wait --create-namespace --set image.tag=placeholdertag,image.repository=acrplaceholder funreleasenam placeholderfunccharts

SclaedObject.yaml
apiVersion: keda.k8s.io/v1alpha1
kind: ScaledObject
metadata:
  name: {{ .Chart.Name}}
  labels:
    deploymentName: {{ .Chart.Name}}
spec:
  scaleTargetRef:
    deploymentName: {{ .Chart.Name}}
  pollingInterval: 10
  cooldownPeriod: 30
  triggers:
  - type: azure-blob
    metadata:
      blobContainerName: containername
      connection: StorageConnection

Secret.yaml
stringData:
  StorageConnection: {{ .Values.secret.StorageConnection }}
  FUNCTIONS_WORKER_RUNTIME: {{ .Values.secret.FUNCTIONS_WORKER_RUNTIME }}
apiVersion: v1
kind: Secret
metadata:
  name: {{ .Chart.Name}}

Logs from KEDA operator
I1231 06:09:29.883516       1 request.go:621] Throttling request took 1.047695012s, request: GET:https://SomeIP/apis/rbac.authorization.k8s.io/v1?timeout=32s
2020-12-31T06:09:30.837Z	INFO	controller-runtime.metrics	metrics server is starting to listen	{"addr": ":8080"}
2020-12-31T06:09:30.839Z	INFO	controllers.ScaledObject	Running on Kubernetes 1.18	{"version": "v1.18.10"}
2020-12-31T06:09:30.840Z	INFO	setup	Starting manager
2020-12-31T06:09:30.840Z	INFO	setup	KEDA Version: 2.0.0
2020-12-31T06:09:30.840Z	INFO	setup	Git Commit: 50bec808f8b4656922797e4bcb7c2b61fabd6d0e
2020-12-31T06:09:30.840Z	INFO	setup	Go Version: go1.15.3
2020-12-31T06:09:30.840Z	INFO	setup	Go OS/Arch: linux/amd64
I1231 06:09:30.841824       1 leaderelection.go:242] attempting to acquire leader lease  keda/operator.keda.sh...
2020-12-31T06:09:30.842Z	INFO	controller-runtime.manager	starting metrics server	{"path": "/metrics"}
I1231 06:09:48.241480       1 leaderelection.go:252] successfully acquired lease keda/operator.keda.sh
2020-12-31T06:09:48.242Z	INFO	controller	Starting EventSource	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledJob", "controller": "scaledjob", "source": "kind source: /, Kind="}
2020-12-31T06:09:48.242Z	INFO	controller	Starting EventSource	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledObject", "controller": "scaledobject", "source": "kind source: /, Kind="}
2020-12-31T06:09:48.342Z	INFO	controller	Starting EventSource	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledObject", "controller": "scaledobject", "source": "kind source: /, Kind="}
2020-12-31T06:09:48.342Z	INFO	controller	Starting Controller	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledJob", "controller": "scaledjob"}
2020-12-31T06:09:48.443Z	INFO	controller	Starting workers	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledJob", "controller": "scaledjob", "worker count": 1}
2020-12-31T06:09:48.443Z	INFO	controller	Starting Controller	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledObject", "controller": "scaledobject"}
2020-12-31T06:09:48.443Z	INFO	controller	Starting workers	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledObject", "controller": "scaledobject", "worker count": 1}
.
Specifications

KEDA Version: 2.0.1
Platform & Version: AKS
Kubernetes Version: 1.18.10
Scaler(s): Azure Storage Blob

Observed the change in apiversion for scaled Object in release 2.0.0
from apiVersion: keda.k8s.io/v1alpha1
to apiVersion: keda.sh/v1alpha1

Just FYI - If you are using Azure Function CLI, you might want to check https://github.com/Azure/azure-functions-core-tools/pull/2289

Just FYI - If you are using Azure Function CLI, you might want to check https://github.com/Azure/azure-functions-core-tools/pull/2289


Plan overall Omni Documentation Strategy.

@dexX7 and I have been talking about and working on documentation tools.
We'd like to discuss and agree upon an overall project documentation strategy for all Omni projects.
I'd like to use the Github Pages site as the main location for technical (and white paper) documentation, but that is open for discussion.
Some of this discussion has happened around Issue #185, but I think we need a "parent" issue for the overall documentation strategy. I'll write a summary proposal in a future comment. (... before Monday)

At the very beginning all files were mixed with the Bitcoin Core files, but we started to move into src/omnicore. In terms of code, this move isn't finished, and the QT/UI related files are still in the base QT dir. At least my current strategy regarding code is to split and untangle, and later group, merge and stuff everything in packages/subdirs.
We also moved the documentation, which introduced the issue that we now have two README.md, which I don't consider as optimal, but I currently also see no really good alternative.
Our documentation is unfortunally very limited, but let me quickly list all documents we have, or currently plan to have:

README.md (duplicate)
src/omnicore/README.md
[src/omnicore/COPYING] (https://github.com/OmniLayer/omnicore/blob/052297b7ca80fbe220948465cd0836473fa8fb73/src/omnicore/COPYING)
src/omnicore/doc/configuration.md
src/omnicore/doc/rpc-api.md
src/omnicore/doc/release-notes.md
src/omnicore/doc/release-notes/

There is also the Bitcoin Core documentation in doc/ with some useful stuff in it, which we partially use, such as the build instructions or Gitian guide.
The following documentation related issues and tasks are not yet completed:

#71: Documentation for Omni Core specific options
#96: Changelog and release notes for 0.0.10
#185: Create a CONTRIBUTING.md and define project related best practises
#193: Documentation for Omni Core debug categories

I updated the README of the Github Pages site with more How To information about working on the site.
I also moved thecontent, templates, and assets directories up 2 levels to make them easier to find.

Thanks @msgilligan!
Besides converting the available documentation, we also need to finalize the "docs in progress", which are currently scattered in keywords and small descriptions in the open issues.
As note and todo, mostly for myself:

the documentation files need to be included in the Makefile.am#L20-L28
the Windows installer is generated via NSIS, and the following lines touch the documentation: src/omnicore/res/omnicore-setup-win.nsi.in#L78-L85
the deinstallation instructions for Windows are also handled via NSIS, and these parts are relevant: src/omnicore/res/omnicore-setup-win.nsi.in#L133-L137

To quote @msgilligan:

I think the documentation needs of this project are significant enough that we should create a separate documentation site. That is, we shouldn't try to present all the documentation on the Github site.
The reasons for this are:

The quantity of documentation is large and needs to be organized, indexed, etc.
There is a need for documentation of multiple releases of the software to be available simultaneously (e.g. 0.0.9/stable and 0.0.10/beta)
The repository is a clone of the Bitcoin repository which we do not control, yet we need to keep things in sync.
We want to minimize the amount of software involved in the build process for security reasons.

Which brings us back to Issue #191.
As far as the README files go, I think we should really only have one -- the one that is the project homepage on Github. It should provide a summary of the project, explain that it is a fork of Bitcoin, and provide links to other documents. The README in src/omnicore should be really short and explain what the purpose of that directory is and where to go for more information. It won't be a web landing page like the main README, though people looking at downloads/checkouts of the source might want to open it to understand what the src/omnicore directory is.

I understand your reasoning. The idea behind having the primary readme in src/omnicore was basically to have everything together, and in regards to the project structure, Omni Core is currently like a plugin to Bitcoin Core, similar to LevelDB.
I tend to agree nevertheless: the readme in the project root is the "first impression" and where users start to look first, so it makes sense to introduce the project there, too.

Closing this issue was we have made progress on documentation in recent years and there are other places to continue this discussion.


Fix formatting error message

Noticed it in the following error message:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/nomad/normalizing/metainfo.py", line 35, in normalize_section
    normalize(self.entry_archive, logger)
  File "/usr/local/lib/python3.7/site-packages/nomad/datamodel/metainfo/eln/__init__.py", line 92, in normalize
    super(ElnBaseSection, self).normalize(archive, logger)
  File "/usr/local/lib/python3.7/site-packages/nomad/datamodel/data.py", line 82, in normalize
    super(EntryData, self).normalize(archive, logger)
  File "/usr/local/lib/python3.7/site-packages/nomad/parsing/tabular.py", line 103, in normalize
    self.tabular_parser(quantity_def, archive, logger, annotation)
  File "/usr/local/lib/python3.7/site-packages/nomad/parsing/tabular.py", line 130, in tabular_parser
    parse_columns(data, self)
  File "/usr/local/lib/python3.7/site-packages/nomad/parsing/tabular.py", line 284, in parse_columns
    'The sheet name {sheet_name} doesn''t exist in the excel file')
ValueError: The sheet name {sheet_name} doesnt exist in the excel file

Even if this is not used in this specific case, I removed the use of f-string with the logger, as this pattern is discouraged.

Thanks for the PR. The change makes sense. Please have some patience as we are still figuring out how to deal with these PRs and our two git-repositories.

I will close and reopen the PR and try to trigger our new sync with the GitLab.


Fix: Link to homepage

This PR

[x] fixes the link to the package's homepage

Current state

Thanks!

No problem, @Andreyco!


Main synced to 111

Latest version of react-native-webrtc, which is using webrtc 111 and software encode/decode for Android.
Android codecs:
In hardware: H.264 (high, baseline)
In software: VP8, VP9, AV1
Bugs that have been fixed with this version:

Android is respecting the simulcast, sending multiple layers. We are using VP8 as codec.
Android is respecting when just changing the maxQuality, to send the right layer, respecting also the resolution and FPS, which was not respecting before.
No changes on iOS. Layer 01 is always using  scaleResolutionDownBy 1 and frameRate 30.   And Layer 00 is always using  scaleResolutionDownBy 2 and frameRate 30. The bitrate is respected by both layers.

I still intend to profile android CPU usage, and compare with the previous version.

The amount of memory that we are using has not changed that much, but the CPU, we are consuming almost 02 times more than before.
One thing to consider, is that now we are sending 02 layers, before, even if we had the simulcast defined, android was sending only 01 layer.
Old version of react-native-webrtc, using hardware codecs:

New version, using software codecs:


Fixes issue #84 - docs link dead in README

@pjbreaux @andrewjjenkins
Fixes #84
All instances of the old dead link have been updated with the new Read the Docs URL.

Looks good. Merging.


Verify that spp server still works

it boots and monitor reports its running status ok, but it must be tested live. But can be closed, as this was just to verify i boots,


Error while checking pod status: timed out waiting for the condition

Hi,
I've been following the official docs to have bootkube-install working with matchbox,
My environment
OS
Virtual instance running Fedora 25,
kernel 4.9.8-201.fc25.x86_64
EDIT(maintainer): openstack VMs
bootkube version
Version: v0.3.5
rkt version
rkt Version: 1.24.0
appc Version: 0.8.10
Go Version: go1.7.3
docker version
Client:
Version:         1.12.6
Server:
Version:         1.12.6
matchbox
latest release v0.5.0
Coreos
1235.9.0
virsh version
Compiled against library: libvirt 2.2.0
Using library: libvirt 2.2.0
Using API: QEMU 2.2.0
Running hypervisor: QEMU 2.7.1
VM's provisioned with ./scripts/libvirt (accesible with ssh)
virsh list
 Id    Name                           State
----------------------------------------------------
 1     node1                          running
 2     node2                          running
 3     node3                          running

ERROR
sudo systemctl start bootkube

after a few minutes bootkube err:
Feb 14 17:28:28 node1.example.com bootkube-start[1100]: [ 2335.222024] bootkube[5]: Error: error while checking pod status: timed out waiting for the condition
Feb 14 17:28:28 node1.example.com bootkube-start[1100]: [ 2335.289855] bootkube[5]: error while checking pod status: timed out waiting for the condition
Feb 14 17:28:32 node1.example.com systemd[1]: bootkube.service: Main process exited, code=exited, status=1/FAILURE
Feb 14 17:28:32 node1.example.com systemd[1]: bootkube.service: Unit entered failed state.
Feb 14 17:28:32 node1.example.com systemd[1]: bootkube.service: Failed with result 'exit-code'.

Catching some logs
Some connections refused
Feb 14 17:18:54 node1.example.com bootkube-start[1100]: [ 1761.735483] bootkube[5]: E0214 17:18:54.919495       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/admission/serviceaccount/admission.go:103: Failed to list *api.ServiceAccount: Get http://<IP_ADDRESS>:8080/api/v1/serviceaccounts?resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 14 17:18:55 node1.example.com bootkube-start[1100]: [ 1761.839362] bootkube[5]: E0214 17:18:55.023444       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/admission/serviceaccount/admission.go:119: Failed to list *api.Secret: Get http://<IP_ADDRESS>:8080/api/v1/secrets?fieldSelector=type%3Dkubernetes.io%2Fservice-account-token&resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 14 17:19:01 node1.example.com bootkube-start[1100]: [ 1767.943696] bootkube[5]: E0214 17:19:01.125779       5 reflector.go:199] github.com/kubernetes-incubator/bootkube/vendor/k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:473: Failed to list *api.ReplicationController: Get http://<IP_ADDRESS>:8080/api/v1/replicationcontrollers?resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
Feb 14 17:19:01 node1.example.com bootkube-start[1100]: [ 1768.044563] bootkube[5]: E0214 17:19:01.229589       5 leaderelection.go:228] error retrieving resource lock kube-system/kube-controller-manager: Get http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused

Then no nodes available to schedule pods
Feb 14 17:20:04 node1.example.com bootkube-start[1100]: [ 1831.507538] bootkube[5]: I0214 17:20:04.316525       5 event.go:217] Event(api.ObjectReference{Kind:"ReplicaSet", Namespace:"kube-system", Name:"kube-controller-manager-3654003418", UID:"d154d156-f2d9-11e6-a393-525400a19cae", APIVersion:"extensions", ResourceVersion:"63", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: kube-controller-manager-3654003418-b9506
Feb 14 17:20:04 node1.example.com bootkube-start[1100]: [ 1831.554533] bootkube[5]: I0214 17:20:04.325467       5 event.go:217] Event(api.ObjectReference{Kind:"Pod", Namespace:"kube-system", Name:"kube-controller-manager-3654003418-b9506", UID:"d22663e4-f2d9-11e6-a393-525400a19cae", APIVersion:"v1", ResourceVersion:"66", FieldPath:""}): type: 'Warning' reason: 'FailedScheduling' no nodes available to schedule pods
Feb 14 17:20:04 node1.example.com bootkube-start[1100]: [ 1831.699032] bootkube[5]: I0214 17:20:04.884216       5 trace.go:61] Trace "Update /apis/extensions/v1beta1/namespaces/kube-system/deployments/kube-controller-manager/status" (started 2017-02-14 17:20:03.507098734 +0000 UTC)
Feb 14 17:22:01 node1.example.com bootkube-start[1100]: [ 1948.547078] bootkube[5]: I0214 17:22:01.363229       5 event.go:217] Event(api.ObjectReference{Kind:"Pod", Namespace:"kube-system", Name:"kube-scheduler-850181384-lh05p", UID:"eaf484c4-f2d9-11e6-a393-525400a19cae", APIVersion:"v1", ResourceVersion:"144", FieldPath:""}): type: 'Warning' reason: 'FailedScheduling' no nodes available to schedule pods

Inside the node1 bootkube and kubelet
core@node1 ~ $ rkt list
UUID		APP		IMAGE NAME					STATE	CREATED		STARTED		NETWORKS
3f975913	bootkube	quay.io/coreos/bootkube:v0.3.5			exited	31 minutes ago	31 minutes ago
e97d3dbf	hyperkube	quay.io/coreos/hyperkube:v1.5.2_coreos.0	running	18 minutes ago	18 minutes ago

kubelet status
core@node1 ~ $ systemctl status kubelet
● kubelet.service - Kubelet via Hyperkube ACI
   Loaded: loaded (/etc/systemd/system/kubelet.service; disabled; vendor preset: disabled)
   Active: active (running) since Tue 2017-02-14 17:10:08 UTC; 41min ago
  Process: 1035 ExecStartPre=/usr/bin/rkt rm --uuid-file=/var/run/kubelet-pod.uuid (code=exited, status=254)
  Process: 1032 ExecStartPre=/bin/mkdir -p /var/lib/cni (code=exited, status=0/SUCCESS)
  Process: 1029 ExecStartPre=/bin/mkdir -p /etc/kubernetes/cni/net.d (code=exited, status=0/SUCCESS)
  Process: 1026 ExecStartPre=/bin/mkdir -p /etc/kubernetes/checkpoint-secrets (code=exited, status=0/SUCCESS)
  Process: 1023 ExecStartPre=/bin/mkdir -p /srv/kubernetes/manifests (code=exited, status=0/SUCCESS)
  Process: 1013 ExecStartPre=/bin/mkdir -p /etc/kubernetes/manifests (code=exited, status=0/SUCCESS)
 Main PID: 1045 (kubelet)
    Tasks: 17
   Memory: 703.0M
      CPU: 16min 6.635s
   CGroup: /system.slice/kubelet.service
           ├─1045 /kubelet --kubeconfig=/etc/kubernetes/kubeconfig --require-kubeconfig --cni-conf-dir=/etc/kubernetes/cni/net.d --network-pl
           └─1263 journalctl -k -f

Feb 14 17:51:06 node1.example.com kubelet-wrapper[1045]: E0214 17:51:06.355191    1045 cni.go:163] error updating cni config: No networks fou
Feb 14 17:51:06 node1.example.com kubelet-wrapper[1045]: E0214 17:51:06.863566    1045 reflector.go:188] pkg/kubelet/kubelet.go:386: Failed t
Feb 14 17:51:06 node1.example.com kubelet-wrapper[1045]: E0214 17:51:06.920691    1045 reflector.go:188] pkg/kubelet/kubelet.go:378: Failed t

Tested the same error using matchbox with Docker.
Maybe I'm not seeing something obvious here.
Best Regards

Are you using these docs example from examples/bootkube or examples/bootkube-install?
'FailedScheduling' no nodes available to schedule pods
I've seen this when nodes cannot register with the controller or report a name which doesn't resolve. Can you inspect the kublet flags (hostname-override) in use on worker nodes? Can you also inspect the kubeconfig file for the server field?
Host
$ sudo ./scripts/devnet create bootkube
$ sudo rkt list
UUID            APP             IMAGE NAME                      STATE   CREATED         STARTED         NETWORKS
3b700943        matchbox        quay.io/coreos/matchbox:latest  running 6 seconds ago   6 seconds ago   metal0:ip4=<IP_ADDRESS>, default-restricted:ip4=<IP_ADDRESS>
fdfa3e2f        dnsmasq         coreos.com/dnsmasq:v0.3.0       running 6 seconds ago   5 seconds ago   metal0:ip4=<IP_ADDRESS>, default-restricted:ip4=<IP_ADDRESS>

VMs
$ ssh<EMAIL_ADDRESS>$ systemctl cat kubelet           # e.g. --hostname-override=node1.example.com
$ cat /etc/kubernetes/kubeconfig  # e.g. server: https://node1.example.com:443
$ dig node1.example.com

You might look further up in the bootkube logs (which are actually apiserver logs) for registration attempts. They can be quite noisy unfortunately.

Hi, thanks for having a look so quickly, Yeah I'm using that exactly documentation,
trying right now with examples/bootkube-install
dnsmasq is working ok also matchbox container is up
HOST
$ rkt list
UUID		APP		IMAGE NAME			STATE	CREATED		STARTED		NETWORKS
eb73dc5c	dnsmasq		coreos.com/dnsmasq:v0.3.0	running	4 hours ago	4 hours ago	metal0:ip4=<IP_ADDRESS>, default-restricted:ip4=<IP_ADDRESS>
faddeb95	matchbox	quay.io/coreos/matchbox:latest	running	4 hours ago	4 hours ago	metal0:ip4=<IP_ADDRESS>, default-restricted:ip4=<IP_ADDRESS>

From node3 dig to node1.example.com and matchbox.foo
core@node3 ~ $ dig node1.example.com

; <<>> DiG 9.10.2-P4 <<>> node1.example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24474
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;node1.example.com.		IN	A

;; ANSWER SECTION:
node1.example.com.	0	IN	A	<IP_ADDRESS>

;; Query time: 6 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Tue Feb 14 21:00:57 UTC 2017
;; MSG SIZE  rcvd: 51

dig to matchbox.foo
core@node3 ~ $ dig matchbox.foo

; <<>> DiG 9.10.2-P4 <<>> matchbox.foo
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22416
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;matchbox.foo.			 I went through the bootkube examples this afternoon and didn't encounter any issues.
The missing flannel.conf file on node1 is a clue, it should be present on all nodes after the kube-flannel daemonset pods start. I bet the install-cni container in kube-flannel is failing for some reason. You could use the assets/auth/kubeconfig to get pods while bootstrapping is occurring to try to debug.
kubectl logs kube-flannel-cl8kn -n kube-system -c install-cni
+ TMP=/etc/cni/net.d/.tmp-flannel-cfg
+ cp /etc/kube-flannel/cni-conf.json /etc/cni/net.d/.tmp-flannel-cfg
+ mv /etc/cni/net.d/.tmp-flannel-cfg /etc/cni/net.d/10-flannel.conf
+ :
+ sleep 3600

However, if bootkube can't bootstrap a real apiserver after 10 minutes it will give up and your kubectl will stop working. This gets into the details of bootkube and the self-hosted flannel changes. https://github.com/kubernetes-incubator/bootkube/blob/master/pkg/asset/internal/templates.go#L640

:(
I'd give it a try using bootkube instead of bootkube-install, btw what's the difference between those ?
I noticed bootkube-install do an extra reboot.
I've been searching of possible causes, and found this
PR#247
Aaron Levy mentioned something I think is relevant to me

Flannel will guess which interface based on the default route -- unfortunately, the default route for virtualbox is an interface which is not routable between nodes.

and my VM is actually an Openstack instance.
Any known workaround?
Tried to do some troubleshooting as you suggested:
KUBECONFIG=assets/auth/kubeconfig

kubectl logs kube-flannel-kgk5z -n kube-system -c install-cni
Error from server (NotFound): the server could not find the requested resource
kubectl get pods -n kube-system
the server doesn't have a resource type "pods"

same for nodes, svc, etc

Hm, the examples are for QEMU/KVM or bare-metal and don't get tested against openstack. Though there's no specific reason they wouldn't work and you've made it pretty far.
Flanneld allows you to specify the interface in a systemd dropin if you like FLANNELD_IFACE. https://github.com/coreos/flannel/blob/master/network/manager.go#L57
bootkube PXE boots a cluster. bootkube-install PXE boots, installs to disk, and reboots before becoming a cluster. The install examples are generally what I'd use on physical machines, but both clusters should be self-hosted Kubernetes clusters.

Two other things we discussed.
Can you check the health of etcd on the controller? Its unusual the temporary apiserver can't tell you the node or pod listing, even if its empty.
etcdctl cluster-health

If your network connection is slow, that 10 minute timeout can be problematic. I can be helpful to wait until the kubelet's have started (i.e. downloaded hyperkube ~240MB) before systemctl start bootkube.

Just tested with bootkube instead of bootkube-install and got the same results,
I'll have a look at that flannel config
This is the status of the etcd cluster
core@node2 ~ $ etcdctl cluster-health
member 7e40ec9559c0d4da is healthy: got healthy result from http://node1.example.com:2379
cluster is healthy

I'll inspect the logs of the docker containers,  there are some running
core@node2 ~ $ docker ps
CONTAINER ID        IMAGE                                      COMMAND                  CREATED             STATUS              PORTS               NAMES
63abf7512205        busybox                                    "/bin/sh -c 'set -e -"   2 hours ago         Up 2 hours                              k8s_install-cni.d4188cb1_kube-flannel-kgk5z_kube-system_83484551-f313-11e6-9a11-525400a19cae_8e050959
2d7961e1a5ef        gcr.io/google_containers/pause-amd64:3.0   "/pause"                 2 hours ago         Up 2 hours                              k8s_POD.d8dbe16c_kube-flannel-kgk5z_kube-system_83484551-f313-11e6-9a11-525400a19cae_fcbd74f2
58fab30a31b0        gcr.io/google_containers/pause-amd64:3.0   "/pause"                 2 hours ago         Up 2 hours                              k8s_POD.d8dbe16c_kube-proxy-kmlf1_kube-system_83201b3a-f313-11e6-9a11-525400a19cae_562a9b0d

I was able to inspect the kube-flannel containers
From ...cni.d4188cb1_kube-flannel-kgk5z...
$ docker logs --details 63abf7512205
 + TMP=/etc/cni/net.d/.tmp-flannel-cfg
 + cp /etc/kube-flannel/cni-conf.json /etc/cni/net.d/.tmp-flannel-cfg
 + mv /etc/cni/net.d/.tmp-flannel-cfg /etc/cni/net.d/10-flannel.conf
 + :
 + sleep 3600
 + :
 + sleep 3600
 + :
 + sleep 3600

From ....POD.d8dbe16c_kube-flannel-kgk5z...
core@node2 ~ $ docker logs --details 120c9963fe28
 E0215 02:54:57.431617       1 main.go:127] Failed to create SubnetManager: error retrieving pod spec for 'kube-system/kube-flannel-kgk5z': Get https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system/pods/kube-flannel-kgk5z: dial tcp <IP_ADDRESS>:443: i/o timeout

10-flannel.conf
$ docker exec -ti 63abf7512205 cat /etc/cni/net.d/10-flannel.conf
{
  "name": "cbr0",
  "type": "flannel",
  "delegate": {
    "isDefaultGateway": true
  }
}

So far everything is pointing that the cni interface is causing my issue.

Actually, when bootkube started deploying flannel as a pod a few weeks ago (rather than running flannel as a systemd service on nodes), the FLANNELD_IFACE option isn't what you want anymore.
You'd probably want to try something different here, I wonder if maybe the IP it is detecting isn't right for your situation. You could tweak that manifest file produced by bootkube render perhaps. This is more a detail of the pods bootkube deploys so it might be more valuable to start an upstream discussion.
That dial dial tcp <IP_ADDRESS>:443 error indicates the flannel pod can't speak to the apiserver. It might be a trailing line from the end since launching the apiserver failed.

You might also be able to hop back in time and use the examples/bootkube and docs from when bootkube v0.3.1 and see if that unblocks your cluster bringup for right now. Before, flannel was run by systemd on host, not as a pod with CNI.
https://github.com/coreos/matchbox/commit/b9f0f61bd5a75049579a95d91874dbc7bec27fb3

Thanks for the information,
Yesterday I ended up modifying the manifest of the kube-controller-manager rendered by bootkube 0.3.5, but no luck so far,  but I'll give it a try with 0.3.1,
Work on that today and I'll come back if found something, and file an issue on bootkube upstream if needed.
btw just tested on VMware fusion and Vbox , and I got the same results, just curious what you guys are using to test matchbox on a virtual env ?
I noticed this when bootkube is running, so the the kube-controller manager is never deployed.
kubectl --kubeconfig=assets/auth/kubeconfig get pods --all-namespaces
NAMESPACE     NAME                                       READY     STATUS    RESTARTS   AGE
kube-system   kube-controller-manager-3654003418-ggbn9   0/1       Pending   0          3m
kube-system   kube-controller-manager-3654003418-rqwwb   0/1       Pending   0          3m
kube-system   kube-dns-4101612645-nz31t                  0/4       Pending   0          2m
kube-system   kube-flannel-tlx0q                         0/2       Pending   0          7s
kube-system   kube-proxy-7tj5m                           0/1       Pending   0          8s
kube-system   kube-scheduler-850181384-60f0r             0/1       Pending   0          49s
kube-system   kube-scheduler-850181384-hc9j0             0/1       Pending   0          50s

after 3 or 5 minutes
$ kubectl --kubeconfig=assets/auth/kubeconfig get nodes --all-namespaces
Unable to connect to the server: net/http: TLS handshake timeout
[root@localhost matchbox]# ../sources/kubectl --kubeconfig=assets/auth/kubeconfig get nodes --all-namespaces
Unable to connect to the server: net/http: TLS handshake timeout

Its tested on bare-metal hardware and in QEMU/KVM via libvirt. You can find a setup for QEMU/KVM in the tutorials.

It is tested on bare-metal hardware and in QEMU/KVM. Bare-metal is the focus with QEMU/KVM being setup in a way to PXE boot to mirror how bare-metal works as closely as possible.

@yazpik if you kubectl describe pod <podname> it should give some more information about pending state (can it download image, are there no nodes available?). Based on all of those remaining in a pending state, I'm guessing no nodes have registered (kubectl get nodes?).
As an asside, all of those pods also rely on the pod-network, which won't be deployed until that kube-flannel pod is run. So in a working state you should see kube-flannel start running, then the other pods also start after that.
So maybe start with checking why kube-flannel is staying in a pending state:
kubectl describe pod kube-flannel-tlx0q --namespace=kube-system

I'm testing right now
bootkube 0.3.1
hyperkube <IP_ADDRESS>
coreos-baremetal instead of matchbox
coreos 1185.3.0
The status is permanent to ContainerCreating, this version is not building flannel container, and the pods are successfully assigned to nodes, but failing now trying to mount volumes
coreos-baremetal]# ../sources/kubectl --kubeconfig=assets/auth/kubeconfig get pods --all-namespaces
NAMESPACE     NAME                                       READY     STATUS              RESTARTS   AGE
kube-system   kube-controller-manager-2751499733-09stp   0/1       ContainerCreating   0          27m
kube-system   kube-controller-manager-2751499733-13wr0   0/1       ContainerCreating   0          27m
kube-system   kube-dns-4101612645-4lfmg                  0/4       ContainerCreating   0          27m
kube-system   kube-proxy-qqlps                           0/1       ContainerCreating   0          27m
kube-system   kube-proxy-scw90                           0/1       ErrImagePull        0          27m
kube-system   kube-scheduler-694795526-mcxsm             0/1       ContainerCreating   0          27m
kube-system   kube-scheduler-694795526-xmgx6             0/1       ContainerCreating   0          27m

I see kube-controller-manager is failing trying to mount "secrets" by connection refused
coreos-baremetal]# ../sources/kubectl --kubeconfig=assets/auth/kubeconfig describe pod kube-controller-manager-2751499733-09stp --namespace=kube-system

-snippet output--
 FirstSeen	LastSeen	Count	From				SubobjectPath	Type		Reason		Message
  ---------	--------	-----	----				-------------	--------	------		-------
  35m		35m		1	{default-scheduler }				Normal		Scheduled	Successfully assigned kube-controller-manager-2751499733-09stp to node2.example.com
  27m		9m		17	{kubelet node2.example.com}			Warning		FailedMount	MountVolume.SetUp failed for volume "kubernetes.io/secret/fa4ed426-f481-11e6-9eb3-525400a19cae-default-token-qgh8g" (spec.Name: "default-token-qgh8g") pod "fa4ed426-f481-11e6-9eb3-525400a19cae" (UID: "fa4ed426-f481-11e6-9eb3-525400a19cae") with: Get https://node1.example.com:443/api/v1/namespaces/kube-system/secrets/default-token-qgh8g: dial tcp <IP_ADDRESS>:443: getsockopt: connection refused
  27m		9m		17	{kubelet node2.example.com}			Warning		FailedMount	MountVolume.SetUp failed for volume "kubernetes.io/secret/fa4ed426-f481-11e6-9eb3-525400a19cae-secrets" (spec.Name: "secrets") pod "fa4ed426-f481-11e6-9eb3-525400a19cae" (UID: "fa4ed426-f481-11e6-9eb3-525400a19cae") with: Get https://node1.example.com:443/api/v1/namespaces/kube-system/secrets/kube-controller-manager: dial tcp <IP_ADDRESS>:443: getsockopt: connection refused
  34m		21s		66	{kubelet node2.example.com}			Warning		FailedSync	Error syncing pod, skipping: failed to "SetupNetwork" for "kube-controller-manager-2751499733-09stp_kube-system" with SetupNetworkError: "Failed to setup network for pod \**"kube-controller-manager-2751499733-09stp_kube-system(fa4ed426-f481-11e6-9eb3-525400a19cae)\" using network plugins \"cni\": cni config unintialized; Skipping pod"**

ncat is succeed to node1.example.com
 nc -vvz node1.example.com 443
Ncat: Version 7.40 ( https://nmap.org/ncat )
libnsock nsock_iod_new2(): nsock_iod_new (IOD #1)
libnsock nsock_connect_tcp(): TCP connection requested to <IP_ADDRESS>:443 (IOD #1) EID 8
libnsock nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 8 [<IP_ADDRESS>:443]
Ncat: Connected to <IP_ADDRESS>:443.

I'm about to test this on a baremetal server, I will keep this updated.

The errors about secrets could be transient (based on the last seen timestamps). During the bootstrap there are times it may not have been able to contact the api-server.
The last message is about skipping launching the pod because there is no pod network yet ("cni config uninitialized; Skipping pod"). This is what flannel is responsible for (dropping the cni config in place, then the kubelet will be able to start the rest of the pods). So if flannel is not being launched on the node - only host-network pods will start.

All right, it took less than 5 minutes to bootkube to have it ready on baremetal+QEMU/KVM
This is the status
Feb 16 22:37:29 node1.example.com bootkube-start[1710]: [  309.970792] bootkube[5]:         Pod Status: kube-controller-manager        Running
Feb 16 22:37:29 node1.example.com bootkube-start[1710]: [  309.971031] bootkube[5]: All self-hosted control plane components successfully started

and
~/matchbox# ./kubectl --kubeconfig=assets/auth/kubeconfig get pods --all-namespaces
NAMESPACE     NAME                                       READY     STATUS    RESTARTS   AGE
kube-system   checkpoint-installer-bwtg9                 1/1       Running   0          6m
kube-system   kube-apiserver-1bdw0                       1/1       Running   2          6m
kube-system   kube-controller-manager-3654003418-g85ld   1/1       Running   0          6m
kube-system   kube-controller-manager-3654003418-wqv9h   1/1       Running   0          6m
kube-system   kube-dns-4101612645-0mhtm                  4/4       Running   0          6m
kube-system   kube-flannel-6sp77                         2/2       Running   1          6m
kube-system   kube-flannel-8kjnk                         2/2       Running   1          6m
kube-system   kube-flannel-wvm41                         2/2       Running   1          6m
kube-system   kube-proxy-dxl0v                           1/1       Running   0          6m
kube-system   kube-proxy-k0p1c                           1/1       Running   0          6m
kube-system   kube-proxy-pqbdk                           1/1       Running   0          6m
kube-system   kube-scheduler-850181384-ns8pp             1/1       Running   0          6m
kube-system   kube-scheduler-850181384-zqm78             1/1       Running   0          6m
kube-system   pod-checkpointer-node1.example.com         1/1       Running   0          5m

So.. I believe then there is a bug for virtual environments (vbox, vmware fusion, and openstack instances), should I file an issue on bootkube upstream ?or do you think is matchbox related ?

Yay, ok. :) Perhaps file it upstream and they can decide on whether its in scope?
matchbox aims to focus on bare-metal for now and those hypervisors (esp. paid ones) won't be in scope. Our use of QEMU/KVM isn't even how one would natively use KVM, its intentionally setup to mirror PXE booting and installing to a disk as closely as possible. The crux of the issue is probably figuring out how to get a similar bare-metal like environment on those hypervisors.
Thank you for your patience trying the various setups.

thanks for all your help guys.

@yazpik fwiw - one thing I've noticed in vbox is that the default network interface (eth0) is not actually routable between nodes - and you must update various k8s manifests to use the correct interface (flannel being a key one, for example).
Some of the assumptions made in this repo may not directly translate to a working installation with these hypervisors (as @dghubble mentioned). However, in the bootkube repo itself there is an example of using vagrant/vbox+bootkube: https://github.com/kubernetes-incubator/bootkube/tree/master/hack/multi-node

Thanks @aaronlevy ,
I've been searching of possible causes, and actually found that you already made that point on
PR#247

Flannel will guess which interface based on the default route -- unfortunately, the default route for virtualbox is an interface which is not routable between nodes.

The point of my lab was focused to try Matchbox and deploy bootkube,
if I do vagrant/vbox+bootkube I'll skipping matchbox right ?
I was able to understand and test a bit matchbox using a baremetal server and booting the controllers and workers from  QEMU/KVM instances, it worked pretty well at the first time.

Unfortunately, I'm not super familiar with matchbox - but assuming these environments support pxe/etc. then you could continue using matchbox - but you might need to make some modifications to the deployed manifests so it supports the network environment.


Various speed optimizations

Check to see whether compressed data matches already before recompressing if PRECOMPRESS_OVERWRITE is enabled
Don't compress tiny files - controlled by PRECOMPRESS_MIN_SIZE, defaults 20
Use multiprocessing.pool to run multiple compression threads

Multiprocessing code based on https://gitlab.com/bryanbrattlof/pelican-htmlmin

Hey Ryan! Thanks for submitting this.
I'm excited about the code -- it cuts my own site generation down from ten minutes to five minutes, and that's a huge time saver! However, the unit tests don't run anymore. I've identified a few issues that need to be addressed.

The inclusion of __init__.py breaks the unit tests. I'm assuming that you needed to add that file because you've cloned the git repo and are including the repo director itself in your Pelican plugins list, rather than installing it into a virtual environment? I can take the patch, but I can't keep __init__.py in the repo.

After removing __init_.py some of the unit tests run, but then one hangs indefinitely. I haven't worked through the details, but it may be related to pyfakefs / multiprocessing.

It looks like there are no additional unit tests for the new code. I see a few opportunities for the new code to crash. For example, if the plugin opens a .br or .gz file that is corrupt it will immediately crash because no exceptions are caught during decoding. Also, if .br files are encountered but the brotli module isn't installed this will result in a crash as well.

I really like this patch. I'm going to work to fix and update the unit tests before merging.

I think I've resolved all of the things I mentioned above. These are now merged into the develop branch of this repository and will be included in the next release of pelican-precompress.
In addition to fixing the unit tests I also added support for disabling the minimum file size by setting it to 0.
I'm not sure how to get GitHub to notice that your commits are now merged into the (now-default) develop branch so I'm manually closing.
Thanks for this commit! I'll put out a new release soon with these changes. Please submit more fixes or improvements as you come up with them! =)

@ryancdotorg I've pushed a new release. Thanks so much for your work on this!

@kurtmckee Thanks for getting it merged, I'm thrilled it saved so much time on your builds, and glad you were able to fix the issues.
I had an issue with my mail server config that was causing emails from GitHub to be dropped, so unfortunately I didn't see your comments here until just now.
I briefly tried to get the testing framework up and running, but had some problems with that. I see you've now added a requirements-dev.txt, which should certainly make that easier in the future.
You're correct that I added the __init__.py file to make it work without installing explicitly in the virtualenv. I'm still a bit ignorant of the finer points of python packaging. Is pip install --editable . what I'd want to use for that?

@ryancdotorg, please let me know if you encounter more issues with the test environment. I may have inadvertently tuned it to my own system so if you're not able to run commands like this to get it up and running please let me know!
$ python -m venv venv
$ source venv/bin/activate
(venv) $ pip install -r requirements-dev.txt
(venv) $ tox

This creates a venv directory that contains scripts/libraries/etc for Python, and when you want to develop in it just run source venv/bin/activate again.
You may be able to skip explicitly installing it; you can add the git repository directory to the list of plugin directories in Pelican, and then add the filename as a string for Pelican to hunt for and load. For example, I uninstalled the plugin from my virtual environment and then tested that this configuration works as desired.
# pelicanconf.py
PLUGIN_PATHS = ['/home/user/git-repos/pelican-precompress']
PLUGINS = ['pelican_precompress']

Pelican will do the work of hunting down the right file from there.
I'm not familiar with the --editable option but I also tested running these commands:
$ # If you use a virtual environment for Pelican, activate it first.
$ # Otherwise, just run these commands.
$ cd /home/user/git-repos/pelican-precompress
$ python setup.py install

That'll install the package to your Pelican virtual environment or to your Python global library directory, depending on if you activated a virtual environment beforehand.

@ryancdotorg please let me know if that worked, or if you have follow-up questions. =)


Program | General Improvements

Duration from yml file

start date and end date automatically populate from duration

Remove pandas warnings. Search and fix them. (See below)
debug vs. info
Use Colorama for printing text (positive messages green, negative messages red).

Duration from yml file

start date and end date automatically populate from duration

Remove pandas warnings. Search and fix them. (See below)

debug vs. info

Use Colorama for printing text (positive messages green, negative messages red).

@vamseeachanta
Fixed following sir :

Duration from yaml
Pandas warnings in teh terminal
debug vs info


Inconsistent rounding of significant digits

Background

Common rounding rules say simply that you round up if the digit is 5 or above.
Scientific rounding rules are a little more complex. These rules are defined in ASTM E29 sections 6.4.1 through 6.4.4.

While I wouldn't expect d3-format to support scientific rounding rules, I would expect that it would apply a consistent set of rules. I know that this is a difficult problem to solve, partly due to the binary representation of floating point numbers.
Test Cases
All of these examples use the format function returned by
d3.format('.3r')

All of the x.45500 cases return the common rounding result:

Input
Output
Common
Scientific

1.45500
1.46
1.46:heavy_check_mark:
1.45

2.45500
2.46
2.46:heavy_check_mark:
2.45

3.45500
3.46
3.46:heavy_check_mark:
3.45

4.45500
4.46
4.46:heavy_check_mark:
4.45

5.45500
5.46
5.46:heavy_check_mark:
5.45

6.45500
6.46
6.46:heavy_check_mark:
6.45

7.45500
7.46
7.46:heavy_check_mark:
7.45

8.45500
8.46
8.46:heavy_check_mark:
8.45

9.45500
9.46
9.46:heavy_check_mark:
9.45

The x.55500 cases return a mix of common and scientific rounding results:

Input
Output
Common
Scientific

1.55500
1.55
1.56
1.55:heavy_check_mark:

2.55500
2.56
2.56:heavy_check_mark:
2.55

3.55500
3.56
3.56:heavy_check_mark:
3.55

4.55500
4.55
4.56
4.55:heavy_check_mark:

5.55500
5.55
5.56
5.55:heavy_check_mark:

6.55500
6.55
6.56
6.55:heavy_check_mark:

7.55500
7.55
7.56
7.55:heavy_check_mark:

8.55500
8.55
8.56
8.55:heavy_check_mark:

9.55500
9.55
9.56
9.55:heavy_check_mark:

All of the x.55501 cases return the correct result, which is the same for common and scientific rounding methods:

Input
Output
Common
Scientific

1.55501
1.56
1.56:heavy_check_mark:
1.56:heavy_check_mark:

2.55501
2.56
2.56:heavy_check_mark:
2.56:heavy_check_mark:

3.55501
3.56
3.56:heavy_check_mark:
3.56:heavy_check_mark:

4.55501
4.56
4.56:heavy_check_mark:
4.56:heavy_check_mark:

5.55501
5.56
5.56:heavy_check_mark:
5.56:heavy_check_mark:

6.55501
6.56
6.56:heavy_check_mark:
6.56:heavy_check_mark:

7.55501
7.56
7.56:heavy_check_mark:
7.56:heavy_check_mark:

8.55501
8.56
8.56:heavy_check_mark:
8.56:heavy_check_mark:

9.55501
9.56
9.56:heavy_check_mark:
9.56:heavy_check_mark:

The values you are using cannot be represented exactly by JavaScript numbers due to the nature of IEEE 754 floating point. More precise representations of the values you are using, as computed by number.toFixed(20), are:

1.55500 ↦ 1.55499999999999993783
2.55500 ↦ 2.55500000000000015987
3.55500 ↦ 3.55500000000000015987
4.55500 ↦ 4.55499999999999971578
5.55500 ↦ 5.55499999999999971578
6.55500 ↦ 6.55499999999999971578
7.55500 ↦ 7.55499999999999971578
8.55500 ↦ 8.55499999999999971578
9.55500 ↦ 9.55499999999999971578

As you can see, the two values that you consider to exhibit inconsistent behavior in D3 are the two values that are greater than the desired exact values, while the other values are all slightly less than the desired exact values.
For more on this topic, see http://0.30000000000000004.com/.

But String(1.55499999999999993783) returns 1.555, as does toPrecision(16). JavaScript's String<->Number coercion understands that double precision floating point is only accurate to a precision of 16 digits.
Here's a modified formatDecimal.js that makes the results of r formatting consistent (with common rounding) up to .15r. If you'd consider implementing this sort of a fix, I'll happily submit a PR that also fixes e, f, and g.
// Computes the decimal coefficient and exponent of the specified number x with
// significant digits p, where x is positive and p is in [1, 21] or undefined.
// For example, formatDecimal(1.23) returns ["123", 0].
export default function(x, p) {
  if (x == null || isNaN(x) || x === Infinity || x === -Infinity) { return null; }

  var [mantissa, exponent='0'] = String(x).split('e');
  exponent = +exponent;
  var [whole, fractional=''] = mantissa.split('.');
  var digits = whole + fractional;

  digits = digits.replace(/^0+/, function (match) {
    exponent -= match.length;
    return '';
  });

  if (digits.length < p) {
    digits += Array(p - digits.length + 1).join('0');
  }

  digits = digits.slice(0, p) + '.' + digits.slice(p);
  digits = String(Math.round(digits));

  if (digits === '0') {
    digits = Array(p).join('0');
  }

  return [
    digits,
    exponent + whole.length - 1
  ];
}

You don’t need to coerce to a string to see that JavaScript (IEEE 754) considers 1.555 and 1.55499999999999993783 to be equal. But that does not mean that mathematically the value is exactly 1.555. If you read the ECMAScript specification, you will see that JavaScript uses the minimum number of digits to uniquely identify a value, and so since these two values are the same from the context of floating point, the shorter representation is chosen. But this is arguably misleading in this context because it gives you a less accurate representation that using 20 digits. (Though naturally since IEEE 754 is binary and not decimal, 20 digits are not enough for an exact representation, either.)
So, your implementation effectively performs rounding twice, first by coercing to a string and then according to the desired behavior in D3. That means that you are treating the value 1.555 as exactly 1.555 (because this is the shortest unique decimal representation in IEEE 754) rather than its natural value of 1.55499999999999993783. Normally I would say this is bad in the context of mathematical operations, but perhaps it makes sense in the context of formatting values? It’s hard to say.

Here’s further evidence that changing this behavior would be bad. Look at the native behavior of number.toPrecision:
(0.555).toPrecision(2) // "0.56" ⚠
(1.555).toPrecision(3) // "1.55"
(2.555).toPrecision(3) // "2.56" ⚠
(3.555).toPrecision(3) // "3.56" ⚠
(4.555).toPrecision(3) // "4.55"
(5.555).toPrecision(3) // "5.55"
(6.555).toPrecision(3) // "6.55"
(7.555).toPrecision(3) // "7.55"
(8.555).toPrecision(3) // "8.55"
(9.555).toPrecision(3) // "9.55"

This is related to https://github.com/d3/d3-path/issues/10#issuecomment-262577521.
There are two valid approaches to decimal rounding. The first approach treats the input value x as its “natural” value in binary floating point. The second approach treats the input value x as the shortest-equivalent decimal value, as in the mathematical quantity represented by the result of calling number.toString.
The built-in methods number.toFixed and number.toPrecision chose the first approach, so the result of +(1.555).toFixed(2) is 1.55 because 1.555 is more precisely represented as 1.55499999999999993783 in binary floating point, which is less than 1.555, and thus rounds down.
If you instead interpret 1.555 as its shortest-equivalent decimal value, then it represents exactly 1.555, and thus should round up. And furthermore, it is possible to implement this technique in JavaScript, but it requires string concatentation: +(Math.round(1.555 + "e2") + "e-2") is 1.56. (See also round10.)
As @drosen0 stated, rounding should behave consistently. Applying decimal rounding rules to binary floating point values is perhaps surprising, but it is self-consistent (assuming there’s no implementation bug, which there does not appear to be), and furthermore is consistent with JavaScript’s built-in methods such as number.toFixed and number.toPrecision.

Hi guys.
Tell me what could be the problem,
it rounds d3 like that, or I didn't understand inverse functions correctly.
const value = 0.00000000000001;
const position = yScale(value);
const valueRevers = yScale.invert(yScale(position) )
// valueRevers === 9.967582315084656e-14

Does any one know if there is a fork of d3.format that uses Math.round?  I love the expressive range of d3.format syntax and its wide use in leading libraries, and get why it is the way it is now.  One use of the library is to format numbers for human consumption, who would expect $8.995 to round to $9.99 either simply (ties-round-up) or scientific round-to-even.  It's harder to explain that $8.995 is numerically the same as $8.9949999999999992 and thus should round down.


Add screen-math extension

Description

This extension helps you quickly sum up the numbers on the screen without copying them to a file. It uses the Vision framework to convert the text to numbers.
Screencast

https://github.com/raycast/extensions/assets/5788410/4d3f95c7-d417-4dbc-ac73-feb9dc3825dc
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi 👋
Thanks for your contribution 💪
I have now tested your extension, and I have some feedback ready for you:
I just tested this and can't get it to work, when opening the extension I get the selection tool, when selecting numbers nothing else happens.
It might be because it needs a unique structure, could you look at how swift files are placed in Coler Picker
I'm looking forward to testing this extension again 🔥
Request a new review when you are ready. Feel free to contact me here or at Slack if you have any questions.

Hi @pernielsentikaer
Thanks for your feedback.
Do you see a notification in HUD display after selecting the numbers?
Or right after selecting the area can you trigger the Raycast to see the numbers?
I couldn't find a way to re-trigger the raycast window to display the number so I'm using HUD to display the total but they are also available right after the screenshot is taken.

@pernielsentikaer
Also not sure why but I'm getting this error. My email is<EMAIL_ADDRESS>

@pernielsentikaer I updated to code to reopen the ray cast window after the screenshot, which should be more user-friendly now.

This still fails if you have pop to root search set to immediately - maybe a HUD like color picker (and copy to clipboard) is the best way for now, or maybe combine with a menubar with the results?

@pernielsentikaer Interesting. showHUD doesn't run when pop to root is set to immediately and command mode is set to view. Not sure if this is an internal bug but I will do more research what I can do.
I will let you know when it is ready. Thanks for your feedback.

Not sure how it's done, but it seems to work fine in Pick Color actually, also with that pop to root value

Not sure how it's done, but it seems to work fine in Pick Color actually, also with that pop to root value

Pick Color doesn't display a view after the color is picked. It uses no-view for the pick color command.
I would like to display the numbers that are being recognized after the screenshot is taken. (if possible :) )

@pernielsentikaer
I changed the extension to use no-view like Pick Color until I find a solution for displaying the numbers on Raycast Detail view.
After the calculation, it shows HUD and copies all the numbers (along with the total) to the clipboard.
I hope this meets the requirements. Please let me know if there is anything else I need to change.

@pernielsentikaer Is there anything else I need to do to get this PR moving?

@pernielsentikaer Can you test this in stable macOS version to see if that's working?


[Bug] kompile - kompile crashes with z3 4.8.9

This is with the latest master branch of K.
Description
When the installed version of z3 is equal to 4.8.9, kompile will crash with errors in z3 arising from the type inferencer that look like the following:
line 230 column 208: invalid named expression, declaration already defined with this name constraint1_Sort#RuleBody

This can be reproduced with any K definition, as the error is manifested when parsing the K prelude.

This seems to be the result of an upstream regression in z3 in version 4.8.9. I have reported it upstream here: Z3Prover/z3#4701. In the meantime, we should think about directing users on arch linux and Mac OS to install z3 4.8.8 manually somehow.

This is fixed upstream and should work in z3 4.8.10, assuming no further regressions. Should we add a known issues warning to the install page for K? Or do you guys think it is worth coming up with a solution that works on z3 4.8.9?

Given that z3 has binary releases as zipfiles, we could direct the user to download the 4.8.8 release zipfile, unzip it, and put it first in their path. Alternatively, we could provide a script that does this. Thoughts?

BTW, it appears that our packaging CI builds are failing due to this bug.
From what I can tell, depending on execution order, either the Homebrew or Arch package test fails with this z3 error.
Given that we are still months out likely from a new release, I think we should either modify the Arch/Homebrew CI build process to make sure that the correct version of z3 is on the path when tests are run (or) disable the tests temporarily while this gets fixed.
Thoughts?

Well, in theory this bug happens because we pop a symbol that was declared, then push a different symbol with the same name. It ought to be possible to change the code for z3 type inferencing so that we never reuse the same symbol name inside the same process. As a result of which, you could have z3 4.8.9 installed and the bug wouldn't be triggered. I'd rather explore such a solution instead of decreasing test coverage or modifying the CI. But if this bug is really so serious, oughtn't we at least talk to Nikolaj Bjorner first and ask for some kind of bugfix release? It seems bad to have the latest release of z3 to just be unusable for six months.

Ultimately, I think it's your call, since you know how the inferencer works better than anybody else and what would be needed to make the change. But I agree, there is no harm in asking for a bugfix release from upstream.


Update scalafmt-core to 2.6.4

Updates org.scalameta:scalafmt-core from 2.5.3 to 2.6.4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-minor

#92


Select an Index input box, can you write a time function?

Index defines itself by time, different points per day, index_today's time
Select an Index input box, can you write a time function?

Please follow the issue submission guideline and fill all required fields.


Carbon v10.25.0 style bug: select

Detailed description
It seems that some of our expressive components are having positioning and spacing issues after applying Carbon v10.25.0. The problems are seen here:
https://percy.io/538fc19a/Carbon-Expressive-Theme/builds/7956640
For the select component seen here:
[image]
The select component is stretching to full span.

Seems to have been caused by carbon-design-system/carbon#7267, and seems intentional.

Working as designed.


JSX Editor in documentation need more padding bottom

in every LIVE JSX EDITOR which have scroll, last line is hidden.

this is not showed ReactDOM.render(<Timer />, mountNode);

i am working on it