OpenSearch Dashboards port ?

any interest in porting your plugin to opensearch dashboards?

Any volunteer to port plugin for Opensearch dashboards?
I’m ready to collaborate.

Hi @fbaligand,
great job with this plugin!! I've been using it for the last year with kibana and opendistro releases. Now we're migrating to opensearch and I'm also interested in continuing to use your plugin.
I'm already started to adapt the code to opensearch dashboard naming convections following this guide:
https://github.com/opensearch-project/opensearch-plugins/blob/main/UPGRADING.md#opensearch-dashboards-plugins
Also build and deploy the plugin in my opensearch instance. Plugin visualization types are display correctly for selection but seems to be an error creating one of them:
this error is displayed on the visualization frame:
Error
Error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at kl (https://kibanajc:5601/1/bundles/osd-ui-shared-deps/osd-ui-shared-deps.js:434:109914)
    at h (https://kibanajc:5601/1/bundles/osd-ui-shared-deps/osd-ui-shared-deps.js:434:54426)
    at g (https://kibanajc:5601/1/bundles/osd-ui-shared-deps/osd-ui-shared-deps.js:434:55696)
    at https://kibanajc:5601/1/bundles/osd-ui-shared-deps/osd-ui-shared-deps.js:434:57709
    at $a (https://kibanajc:5601/1/bundles/osd-ui-shared-deps/osd-ui-shared-deps.js:434:66589)
    at Ms (https://kibanajc:5601/1/bundles/osd-ui-shared-deps/osd-ui-shared-deps.js:434:106652)
    at gl (https://kibanajc:5601/1/bundles/osd-ui-shared-deps/osd-ui-shared-deps.js:434:90018)
    at fl (https://kibanajc:5601/1/bundles/osd-ui-shared-deps/osd-ui-shared-deps.js:434:89943)
    at ol (https://kibanajc:5601/1/bundles/osd-ui-shared-deps/osd-ui-shared-deps.js:434:87291)
    at https://kibanajc:5601/1/bundles/osd-ui-shared-deps/osd-ui-shared-deps.js:434:45733

And this one is displayed in a pop-up:
TypeError: getSearchSessionId is not a function
at _callee$ (https://kibana.jc:5601/1/bundles/plugin/enhancedTable/enhancedTable.plugin.js:14:1344869)
at tryCatch (https://kibana.jc:5601/1/bundles/plugin/queryWorkbenchDashboards/queryWorkbenchDashboards.plugin.js:1:33827)
at Generator.invoke [as _invoke] (https://kibana.jc:5601/1/bundles/plugin/queryWorkbenchDashboards/queryWorkbenchDashboards.plugin.js:1:37778)
at Generator.next (https://kibana.jc:5601/1/bundles/plugin/queryWorkbenchDashboards/queryWorkbenchDashboards.plugin.js:1:34966)
at visualization_fn_asyncGeneratorStep (https://kibana.jc:5601/1/bundles/plugin/enhancedTable/enhancedTable.plugin.js:14:1340577)
at _next (https://kibana.jc:5601/1/bundles/plugin/enhancedTable/enhancedTable.plugin.js:14:1340904)

Maybe you can create a new repo called something like opensearch-dashboards-enhanced-table, I can share with you code customizations.
Thanks for your help.

Hi,
As you asked, I just created a branch for Dashboards:
https://github.com/fbaligand/kibana-enhanced-table/tree/opensearch-dashboards
To my known, Dashboards is a fork of Kibana 7.10, so the branch I created is a copy of my "7.9" branch that works with Kibana 7.9, 7.10 and 7.11.
That said, concerning your error:

getSearchSessionId is not used in my branch for Kibana 7.9-7.11 (so opensearch-dashboards branch)
I guess that you forked master branch, that is for Kibana 7.15
So I recommend you to fork from "opensearch-dashboards" branch, and restart your migration work

Fabien

Hi @fbaligand ,
I'm working in the migration using the branch "opensearch-dashboards" you've created. These are the steps I've followed:

Replace in order, all files:
kibana -> opensearchDashboards
Kibana -> OpenSearchDashboards
KIBANA -> OPENSEARCH_DASHBOARDS
kbn -> osd
Kbn -> Osd
KBN -> OSD
opensearchDashboards_legacy -> opensearch_dashboards_legacy
opensearchDashboards_utils -> opensearch_dashboards_utils
opensearchDashboards_cloned_code -> opensearch_dashboards_cloned_code

Rename folder public/src/kibana_cloned_code to public/src/opensearch_dashboards_cloned_code.

Rename kibana.json -> opensearch_dashboards.json and change required plugins names:
{
"id": "enhancedTable",
"version": "1.11.2",
"server": false,
"ui": true,
"requiredPlugins": [
"visualizations",
"data",
"inspector",
"opensearchDashboardsLegacy",
"opensearchDashboardsUtils",
"opensearchDashboardsReact",
"share",
"charts"
]
}

Fix paths and scripts names package.json:

{
"name": "enhanced-table",
"version": "1.11.2",
"description": "This visualization plugin is like a Data Table, but with enhanced features like computed columns, filter bar and pivot table",
"license": "Apache-2.0",
"opensearchDashboards": {
"version": "1.2.0",
"templateVersion": "1.0.0"
},
"scripts": {
"preinstall": "node ../../preinstall_check",
"opensearch": "node ../../scripts/opensearch",
"osd": "node ../../scripts/osd",
"lint": "../../scripts/eslint .",
"start": "cd ../.. && node scripts/opensearch_dashboards --dev --oss",
"debug": "node --nolazy --inspect ../../scripts/opensearch_dashboards --dev",
"build": "../../plugin-helpers build",
"compile-and-build": "node ../../scripts/plugin_helpers.js build",
"compile": "rm -rf ./target && node ../../scripts/build_opensearch_dashboards_platform_plugins.js --scan-dir . --filter enhancedTable"
},
"dependencies": {
"expr-eval": "2.0.2"
},
"devDependencies": {
"dragula": "3.7.2",
"ui-select": "0.19.8"
}
}

Run "yarn" command for dependencies isntallation

Compile and build with command "yarn compile-and-build"

I build the plugin zip and tested for OpenSearch-Dashboards version 1.0.0 and 1.2.0. After deployment we get this error accesing OpenSearch:

Debugging seems that _ref doesn't contains any variable named expressions :(

I don't know if this error is going backwards from the getSearchSessionId that appeared when yo try to create/open any visualization type of this plugin or we are progressing.
Maybe you can helps us. I can upload the code if you want.
Diego.

Well to debug in nice conditions, I invite you to run OpenDashboards in dev mode with enhanced table plugin.
So:

execute these commands

git clone https://github.com/opensearch-project/OpenSearch-Dashboards
cd OpenSearch-Dashboards
git reset --hard X.Y.Z # replace 'X.Y.Z' by desired OpenSearch-Dashboards version
mkdir plugins
cd plugins
git clone https://github.com/fbaligand/kibana-enhanced-table.git enhancedTable

install the version of Node.js listed in the OpenSearch-Dashboards/.node-version file
ensure that node binary is both in PATH environment variable and in OpenSearch-Dashboards/node folder
install the latest version of yarn
execute these commands :

cd OpenSearch-Dashboards
yarn opensearch bootstrap
cd plugins/enhancedTable
yarn install
yarn start

in your browser, call http://localhost:5601

Hi @diego2glez ,
would it be possible for you to make the fork with your changes public, such that other people could try it out and help?
Thanks!

Hi,
For information, @jbgachot wrote a commit that adds Opensearch-Dashboards compatibility.
It should be soon merged on opensearch-dashboards branch.
Here is the discussion about that:
https://github.com/fbaligand/kibana-enhanced-table/discussions/211

Hi @fbaligand @jbgachot, I'm on opensearch team, thanks for your great effort on porting this plugin to opensearch dashboards!
Just want to say hi and let you know that we are here to support, feel free to ping me if you see any issues when porting the plugin to opensearch, and I will help with troubleshooting!

Hi @CCongWang,
Thanks to offer your help!
As you can see, @jbgachot has done a commit that works with open search 1.2.
it should be become a PR and then be merged on opensearch-dashboard branch.
So a enhanced-table version for OSD should soon arrive.

Hi all,
Great news: enhanced-table is now compatible with OpenSearch Dashboards!
You can get enhanced-table package for OSD in last release (v1.13.1) here:
https://github.com/fbaligand/kibana-enhanced-table/releases/tag/v1.13.1
All packages for OSD are suffixed by "_osd-X.Y.Z.zip", where "X.Y.Z" is OSD version.

Super excited to try this out in Dashboards, thanks @fbaligand!

Happy that you enjoy it! :)

hello I am tring to install in osd 1.2 but when I try to install have this error:
bin/opensearch-dashboards-plugin install enhancedTable --allow-root
Attempting to transfer from enhancedTable
Attempting to transfer from https://artifacts.opensearch.org/downloads/kibana-plugins/enhancedTable/enhancedTable-1.2.0.zip
Plugin installation was unsuccessful due to error "No valid url specified."

Hi all,
For information, I just published a package for OpenSearch Dashboards 2.0.0.
You can get it here:
https://github.com/fbaligand/kibana-enhanced-table/releases/tag/v1.13.1

@fbaligand Could you please share how did you build distributable archive for/under OpenSearch Dashboards 2.2.0?
I tried
To build a distributable archive, execute this command :

yarn build --kibana-version X.Y.Z # replace 'X.Y.Z' by 2.2.0

But I'm getting strange errors like:
$ yarn build --kibana-version 2.2.0
yarn run v1.22.17
$ ../../node_modules/.bin/plugin-helpers build --kibana-version 2.2.0
/bin/sh: ../../node_modules/.bin/plugin-helpers: No such file or directory

IIUC, one would need opensearch_dashboards.json (which gears towards OSD) instead of kibana.json in order to build under OpenSearch Dashboards 2.2.0. Am I right?

Hi @duhang,
First, if you just want Enhanced Table "as is" for OpenSearch Dashboards, you don't have to build it, you can simply download the right package here:
https://github.com/fbaligand/kibana-enhanced-table/releases/tag/v1.13.1
The package name is:  enhanced-table-1.13.1_osd-<OSD_VERSION>.zip
Then, if you want to build it for yourself, I realize that "Development" documentation section was a bit wrong.
So I just did a commit on osd branch to fix that: https://github.com/fbaligand/kibana-enhanced-table/commit/495fa80fc8f8e9b9ff87048c44c7c8561348fc27
Finally, I invite you to pull "osd" branch, and to follow updated "Development" section:
https://github.com/fbaligand/kibana-enhanced-table/tree/osd#development

Cool, it totally just worked from "osd" branch:
$ node ../../scripts/plugin_helpers.js build --opensearch-dashboards-version 1.2.0
 info deleting the build and target directories
 info running @osd/optimizer
 │ info initialized, 0 bundles cached
 │ info starting worker [1 bundle]
 │ succ 1 bundles compiled successfully after 113 sec
 info copying assets from `public/assets` to build
 info copying server source into the build and converting with babel
 info compressing plugin into [enhancedTable-1.2.0.zip]
✨  Done in 116.50s.

A tiny suggestion though:
One can use --opensearch-dashboards-version flag of "yarn compile-and-build" to specify OSD_VERSION,
thus avoid from having to manually enter it.
yarn compile-and-build --opensearch-dashboards-version <OSD_VERSION>

Indeed, this is a bit easier.
I just updated documentation:
https://github.com/fbaligand/kibana-enhanced-table/tree/osd#development
And happy to see that you appreciate enhanced-table plugin :)

i have installed 1.3.2 version of plugin in opensearch dashboards , i can see plugin is installed successfully ,but i am unable to see enhancedTable or its functionality in dashboards, I am trying this in Kubernetes enviroment,
so i will not be able to restart dashboards pod , i tried the troubleshooting steps , but could not get it working  ,please could you help if i am missing some step ,  @fbaligand

ignore i could get it working , had to run --optimize command in the Dockerfile after the plugin is installed,
thankyou @fbaligand


Enable integration tests on CI

Still work in progress, I'll sort it later.

Turns out that I need to send a PR from inside of a repository to get access to the secret variables. This is okay, so I'll reopen the PR from another repository now.


Card Stop work 2024.7.0b0

After new HA Beta card stop work

I can confirm the same here

same. no matter which weather entity


⚠ Bofrost.at has degraded performance

In d11c5ec, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1792 ms

Resolved: Bofrost.at performance has improved in f5a03e2 after 2 hours, 22 minutes.


Forms - Number Field

Feature Request
Description

Create a first class number input form field.

first class number input field can be created using HTML form input with having value number for type attribute. it can be like extension of terra-form-input along with additional props like

max : The maximum value to accept for this input
min : The minimum value to accept for this input
step : specifies the number intervals between min and max

in addition to terra-form-input number field will have up and down arrows to adjust the value as shown below.
Before proceeding with Technical Design would like to clarify following things with respect to number field.
I found that terra-form-input can be used as number field too by passing number as a value for type property as shown in this example of hookshoot : Window Bound Hookshot - Attachment Margin in Px here they have used input field with number type the only difference would be the min and max property of number input so would like to know is this new number field is only for having min and max property..?  because for min and max property number input displays up and down arrow button on input field which is not consistent across the browser as listed below :

up and down arrows displays differently in different browsers like shown below do we need to handle this to keep uniformity among the browsers or do we need to go with the default behaviors of browser.
Chrome :  up and down arrows will appear when input receives focus

Mozila and Safari :  up and down arrows will display by always

IE 11 and Edge :  up and down arrows will not be displayed for number inputs

up and down arrow keys changes the value between given min and max value when we press it but this doesn't seems to work in IE (tested with IE 11) we might need to handle up and down key press manually to enable number input functionality.

Below are the Existing Issues of HTML number input that's need to be fix to keep the same functionality across the browser.
Google Chrome :
1. Allows character ‘e’ in numeric text box
FireFox :
1. Allows non-numeric characters in numeric text box
2. Doesn’t re-initialize to numeric value on click of down arrow and up arrow / on keyboard down
and up key.
Safari :
1. Allows non-numeric characters in numeric text box
Internet Explorer 11 :
1. Allows non-numeric characters in numeric text box
2. Up arrow and down arrow is not displayed in numeric input
3. Min and max value is not honered
4. Value doesn’t changes on click of down arrow and up arrow / on keyboard down and up key
5. Doesn’t re-initialize to numeric value on click of down arrow and up arrow / on keyboard down
and up key
Edge :
1. Allows non-numeric characters in numeric text box
2. Up arrow and down arrow is not displayed in numeric input

Nice work on the research for this. Let's make the type attribute a first class prop on Input/InputField. We'll use that to allow people to set type="number" in Input/InputField. We're fine with the cross-browser variances of input[type="number"].

input (terra-form-input) has already got first class prop defined for it :code and here is an existing example for input with type as number : Window Bound Hookshot - Attachment Margin in Px in this example Terra-input field has been used with inputAttrs props like :
<InputField
label="Attachment Margin in Px"
inputId={getId('hookshotAttachmentMargin')}
inputAttrs={{ name: 'hookshotAttachmentMargin', type: 'number' }}
defaultValue={this.state.hookshotAttachmentMargin}
style={{ width: '200px' }}
onChange={this.handleInputChange}
/>
I think this would do meet the requirement of input number field mentioned above.

Do we require Type as first class prop in terra-input-field also..?
By doing this consumer can directly set value for Type prop in input-field instead of adding it through inputAttrs.
Got this thought while going through the issue #2283 where disabled is being added as first class prop for form-field components to resolve confusion among consumers.

Yes let’s make type itself a first class prop.

@bjankord @ryanthemanuel Shouldn't we not handle the Min, Max  and step values through separate props for these controls when the type="number" ?
And also why can't we have a separate new control for the number input built upon current form input field with form input field type hardcoded to 'number' always and along with above mentioned props ?.


from: can't read /var/mail/keras.datasets

Describe the bug:
Running an simple MNIST data classification.
I was able to run for the first time. Next day, I tried to run the same program, I got this error message
(asr) maybe@maybe1:/data/jugs/asr/languageclf$ ./trainalutokeras.py
from: can't read /var/mail/keras.datasets
from: can't read /var/mail/autokeras.classifier
./trainalutokeras.py: line 5: syntax error near unexpected token `,'
./trainalutokeras.py: line 5: `  (x_train, y_train),(x_test, y_test) = mnist.load_data()'

Setup Details:
Any details about your local setup that might be helpful in troubleshooting. Include the details about the versions of:

OS type and version: Ubuntu 16.04
Python: 3.6
scikit-learn: 0.19
numpy: 1.14.x
keras: 2.1.6
scipy: 1.0.1
tensorflow: 1.6

I think this is a Keras related issue.
Since it is not calling the autokeras code yet before it crashes.
If you feel it is not, you can reopen the issue.
Thank you for your contribution.


Added an html() method to the Dashboard class

As per the title: added an html() method to the Dashboard class to support displaying dashboards in other notebook platforms e.g. Databricks.

Thanks for the commit, we add your changes to the project! The only point I want to draw your attention to is embedding the generation of our html in other modules (especially at this stage of the project😅). In this case, some collisions are possible, styles or some sections of the report may not be displayed correctly.


Test with token balance sizes

[ ] gas use at 64 bit
[ ] gas use at 32 bit
[ ] Make a blogpost about performance

No advantage without packed structs


Suggestion - Node Module

Would be cool. Could use PathItemObjects as a standard
https://swagger.io/specification/#pathItemObject

I'm not quite sure what you mean with this? The generated swagger file which is used for the /docs endpoint provides a json that describes all endpoints.


Create pipeline and pipeline version selector and change pipeline run creation page

JIRA:
RHOAIENG-266
RHOAIENG-268
Description

This PR creates a selector for both pipeline and pipeline versions that could be used in many places. Here in this PR, we add this selector to the pipeline runs creation form.
When no pipeline is selected, the version selector is disabled

Now you could select the pipeline, if the number is less than 10, we will not show the View more button

After the pipeline is selected, the default version will be automatically selected

If the number is more than 10, it will show the badge of the visible options and the total size

Clicking on it will load more options

If the name is truncated, the tooltip will show up. If the version has a description, another tooltip will show on the side

The Updated column is sortable, the sort is based on ALL options, but not only the visible options

The search input could be used to filter the pipelines or pipeline versions

How Has This Been Tested?

Upload several versions to one pipeline (better to be more than 10 to test the View more function). If you don't know how to upload, you could enable the kubeflow pipeline UI following the instructions here https://github.com/opendatahub-io/data-science-pipelines-operator#ml-pipelines-ui. Then you could upload a version to a specific pipeline. A version is the same YAML file as the pipeline you uploaded before.
Go to the create run page, and test the dropdowns for both pipeline and pipeline version

Test Impact

Created a unit test to test the selector to see whether it could show the correct number and badge and search.
Request review criteria:

Self checklist (all need to be checked):

[ ] The developer has manually tested the changes and verified that the changes work
[ ] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

cc @yannnz Could you please check the UI?

Pipeline with no version:

Updated search helper text:

@manaswinidas Could you check again?


test stub_supports redirection

This is just the test changes for #22976
That PR broke manageiq-ui-classic build.
This PR is trying to debug that.
@miq-bot cross-repo-test manageiq-ui-classic

well, got what I want:

cross repo is failing in same way. so the failures are not related to this PR
tests are failing showing that the code improvements of that PR fixes stubbing issues.


All shortcuts are gone after enabling settings sync

Simplified steps to repro:

From Machine 1 (say MacOS), Set "settingsSync.keybindingsPerPlatform": false
From Machine 1 Make some keyboard shortcuts
From Machine 1 Enable Settings Sync
From Machine 2 (say Windows), enable settings sync

🐛 Keyboard shortcuts are reset

Original steps from author:

VS Code Version:

Version: 1.56.2
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-12T16:45:26.313Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.8.0-50-generic snap

OS Version: Ubuntu 20.04

Steps to Reproduce:

Make some custom shortcuts
(not sure if necessary) Set "settingsSync.keybindingsPerPlatform": false
Enable settings sync
(not sure if necessary) Enable settings sync on another host

See how all custom shortcuts are gone. /home/mmatrosov/.config/Code/User/keybindings.json file contains an empty array: [].

Another host VS Code Version:

Version: 1.56.2 (user setup)
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-12T17:13:13.157Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.18363

Another host OS Version: Windows 10, v1909

Then I tried to add custom shortcuts again, and they are synced successfully in both directions, I can see how keybindings.json is being updated automatically. Which is nice, but is there a way I can bring old mappings back? I only backed up Settings.json file, and seems they are not stored there...

Can you please open the Sync Activity (Remote) view using the command Settings Sync: Show Synced Data and see which machine of yours is pushing empty keybindings to remote?

I've done as you've said, and here is the only relevant change that I see:

It is not clear if the empty settings were pushed or overwritten by this change, but here you go.
Anyway, it seems like all the history is there! I wish I tried this earlier! Thanks!

It means that your current machine has pushed empty keybindings to remote while syncing. Can you please give me the content for the following 3 entries (Keyboard Shortcuts, Settings, Keyboard Shortcuts)

Please right click on the folder entry and run action get the raw JSON data and share it

Same issue on two macs: keybindings on one of them are overwritten by a smaller version from the other.
On the mac with older bindings i see sync event from the other, but that does not include any changes. So this mac gets old bindings and then they are synced back to the mac where there were more, deleting the changes there.
It is almost as the mac with all the bindings does not sync right  - doesnt have the write permissions.
That i see on the mac with less bindings:

That is on the mac with rewritten bindings:

/verified I think? I always get a 'merge' settings dialog whenever a sync doesn't match.

Yeah you will be asked to merge if there are any merges involved.


Update parameters

These changes allows us to populate the parameters struct in FFMPEG and set the extradata field on it as well.

@flavioroth addressed all but one. Should be good to merge.


Support compiling bevy_rapier on bevy_ecs without the rest of bevy

Would it be possible to support compiling and running this library with only bevy_ecs (https://crates.io/crates/bevy_ecs) as dependency, instead of the whole bevy engine, or are there some festures from other bevy components which the crate requires?

Just from a quick glance, it makes use of bevy_app(plugins and events), bevy_transform and bevy_render and I don't see anything that can't be put behind feature gates.


Added hello world in qbasic and bubble sort in python

This PR contains hello world program written in QBasic programming language and a bubble sorting algorithm written in python

Thanks for your contribution @cryskram


wrong word

(https://github.com/MicrosoftDocs/msix-docs/tree/main/msix-src/package)/create-app-package-with-makeappx-tool.md
There is a wrone in line 28
"ar64" should be"arm64"

(https://github.com/MicrosoftDocs/msix-docs/tree/main/msix-src/package)/create-app-package-with-makeappx-tool.md There is a wrong in line 28 "ar64" should be"arm64"

Docs fixed, thank you for the feedback


Multiple Base URLs

Hi,
First off congratulations on this project, I've been messing around with it and it's great!
I've got a quick question regarding the base URL: is there a way to set a second, less important one such that the video URLs would still work with it?
Here's the problem I'm facing: I've set up Streama on a desktop on my network at home. I've set up a port-forward so that I could access Streama from anywhere using my external IP address. In order for this to work, my base URL has to be X.X.X.X:3000, where X.X.X.X is my external IP address (using port 3000).
However, with my base URL set to my external IP address, I obviously can no longer read any videos on my local network though because my external IP is inaccessible when I'm on it. So is there a way that I could set a second less important base URL so that all video links would work with X.X.X.X:3000 (external IP address) and Y.Y.Y.Y:3000 (internal IP address)? I haven't dived into the code so I'm not sure how possible this is but I thought I would ask anyway!
In the meantime, the quick fix for others running into a similar problem is simply manually changing the base URL from the internal/external IP address every time you access it from your local network or outside of it. It's a bit of a pain (and you can't forget to do it before leaving the house or you're locked out!) but it works.
Thanks again for all of your hard work!

Hi!
This is an interesting issue and a very clever solution. I've always set up streama on a remote server so I've never run into this problem, but I like your use case, it seems a logical one for the application, and so I'll do my best to come up with a solution.
I think, maybe the whole idea of the base path is faulty. If you can access the application, then that is your base path right there. So it should be variable. It's a long time ago now so I don't remember why it was necessary for the video playback, but I'll look into it and let you know :)

That's great, thanks. I do agree that the whole base path config doesn't make complete sense to me, since to get onto Stream you are accessing that base path and you could just use that for all of the video playback URLs. But I haven't properly dived into the code so there might be a reason behind it.
Please keep me posted!

yes it would be dandy if the base url could be configured -- I had to set up a reverse proxy because I have multiple IP's and it couldn't pick one from my hostname.

@dularion
Hello
First of all congratulations on this project, I've been using your program and it's great!
I want to ask you a question: How do I change the base URL so that I can access Streama from anywhere using my external IP?
I have dynamic IP.
I use Streama v 1.1
Default URL http: // localhost: 8080
Thanks again for your hard work.

Right now there is no way of handling dynamic IPs within Streama, you’ll have to look up your dynamic IP when you want to watch it and change it within the admin section to that.
Julien
From: dtejedavilleda<EMAIL_ADDRESS>Reply-To: dularion/streama<EMAIL_ADDRESS>Date: Wednesday, June 28, 2017 at 18:31
To: dularion/streama<EMAIL_ADDRESS>Cc: Julien Guerinet<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [dularion/streama] Multiple Base URLs (#282)
@dularionhttps://github.com/dularion
Hello
First of all congratulations on this project, I've been using your program and it's great!
I want to ask you a question: How do I change the base URL so that I can access Streama from anywhere using my external IP?
I have dynamic IP.
I use Streama v 1.1
Default URL http: // localhost: 8080
Thanks again for your hard work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dularion/streama/issues/282#issuecomment-311810605, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFLAKcLZJQg985vdgqbNYwP8Y5VPnb0xks5sItQqgaJpZM4LwrGR.

Hello
I made the change in the Admin section and did not save the change.

Hello
I made the change in the Admin section and did not save the change.
I share screenshots of my computer.
[image: Imágenes integradas 4][image: Imágenes integradas 3]
Thank you.
2017-06-28 20:36 GMT-05:00 Julien Guerinet<EMAIL_ADDRESS>
Right now there is no way of handling dynamic IPs within Streama, you’ll
have to look up your dynamic IP when you want to watch it and change it
within the admin section to that.
Julien
From: dtejedavilleda<EMAIL_ADDRESS>Reply-To: dularion/streama<EMAIL_ADDRESS>Date: Wednesday, June 28, 2017 at 18:31
To: dularion/streama<EMAIL_ADDRESS>Cc: Julien Guerinet<EMAIL_ADDRESS>Author <
<EMAIL_ADDRESS>Subject: Re: [dularion/streama] Multiple Base URLs (#282)
@dularionhttps://github.com/dularion
Hello
First of all congratulations on this project, I've been using your program
and it's great!
I want to ask you a question: How do I change the base URL so that I can
access Streama from anywhere using my external IP?
I have dynamic IP.
I use Streama v 1.1
Default URL http: // localhost: 8080
Thanks again for your hard work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://github.com/
dularion/streama/issues/282#issuecomment-311810605>, or mute the thread<
https://github.com/notifications/unsubscribe-auth/
AFLAKcLZJQg985vdgqbNYwP8Y5VPnb0xks5sItQqgaJpZM4LwrGR>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dularion/streama/issues/282#issuecomment-311837916,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXZi5BhLy8m6uVDcBQDTzhcT45IFA0toks5sIv-xgaJpZM4LwrGR
.

--
Saludos Daniel Tejeda.

Hi,
I can't see your screenshots unfortunately. However, I can maybe guess what problem you're experiencing as I believe I had the same thing at first. When you change the IP address in the admin section, do you scroll back up to the top of the page and click on "Save"? Clicking on the check mark next to the Base Url field doesn't actually save the change, it just verifies that it's a valid Url. In order to save the change, make sure you scroll to the top of the page and Click on the Save button in the top right corner.

Hello
Thanks for answering. Click on "Save" and it shows "Settings saved"

So even after saving your settings, the IP changes back to the default one?

Hi.
I followed the steps you indicated, then opened port 8080 on the router and did the test.
It works! At port 8080.
I used port 3000 and 9000 and the router could not open them.
Thank you very much for your help and support.

Hi could you record a video/gif that shows this?

Hello Thanks for responding, Streama already works on my computer. Thank
you very much.
2017-06-30 1:41 GMT-05:00 Antonia Engfors<EMAIL_ADDRESS>
Hi could you record a video/gif that shows this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dularion/streama/issues/282#issuecomment-312188467,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXZi5Ntl1EdWzZlXo1HyXfelkR-1FBgkks5sJJipgaJpZM4LwrGR
.

--
Saludos Daniel Tejeda.


Popup desappears

Hi! It seems there is a bug with popups. If animation option is set to false and any popup has been opened then after zoom (even if this marker keeps outside any cluster) popup desappears. It's easily reproduced in 'real world example' https://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-realworld.388.html  by adding this option to markerClusterGroup. Sorry for my english.

I'm having this or a similar issue: if markers are being spiderified because of max-zoom-level, clicking on a spiderified marker hides the popup because the marker hides right after clicking on it. Is there a recommended work-around for this?


add(tools): Chai Builder

Name
Link

Chai Builder
cloud.chaibuilder.com

Chai builder is a Tailwind CSS based website builder that allows users to rapidly create web pages. No coding required.

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] My item is in line with the Tailwind brand usage guidelines
[x] I have read and followed the contribution guidelines

Closed because this PR was abandoned.

@joshmanders Chai builder is a Tailwind CSS specific page builder


Refactor dbux 3 button new

This PR includes a lot of differences that aren't related to buttons at all. And I don't get the relation to https://github.com/db-ui/core/pull/107 – maybe it would be easier to target this branch for this PR.


Report errors in bootstrap.js to the debugger

We should call reportFatalErrorBeforeShutdown() if there was a syntax error or runtime (e.g. wrong require before we enter UIApplicationMain) when executing bootstrap.js so the debugger can be notified.

Fixed in https://github.com/NativeScript/ios-runtime/commit/de3092aa03904d8862af34c8f70120eb6ca52f00


Make HTML statistics page

currently only uploads to pastehtml

That looks cool :+1:

example http://captainelliott.github.io/tests/cardinalstatistics

:+1:

@CaptainElliott The flairs show up as ? on your transcript. Might want to fix that

@ryanw-ny I planned to do that later and other cosmetic things. I plan on making the teams use colours and perhaps use players avatars

@CaptainElliott rad!

@ryanw-ny rad?

Cool

Do you wil create a page for 1 match or just will work like in Overcast?

Commit merged manually


don't click that link i dare you

pertains to #31
@savetheclocktower let us know if you'd got any less-dated references you'd like to see in this one.

I haven't done dupontCAPS in years. Maybe point out that I spend my day job git blame-ing lines that turn out to have been written by @pifantastic and @SlexAxton. Otherwise this is just fine.
Also, I just realized I haven't changed my Twitter profile description in like eight years, so I fixed that.

updated!

👍

👍
i shoulda written more code for you to git blame i guess

Rude

brb updating my linkedin career goals to include getting my code git blame'd by @savetheclocktower


Is it possible to limit a week and/or song to a certain difficulty within the LUA version of Psych Engine?

What is your question?
I think the title is pretty self explanatory. I have a set of charts that are intended to only be played on hard mode. Obviously the game would crash if another difficulty is chosen. Also, I know that this is easy to do via the source code, but I've been slowly moving to the LUA version as I think It's better practice for this engine specifically.

Check the week editor, there is a field for difficulties

Didn't see that haha, thanks for the help I appreciate it!


Published package lacks dist folder

Hey! Really excited to use and implement this package for Storybook. Would love to test it out right away, but I noticed that the package published on npm lacks the dist folder making it unusable. You can see it here https://www.npmjs.com/package/storybook-vue-addon?activeTab=explore
Can you please republish it with the dist? @tobiasdiez

Thanks for bringing this to my attention. Should be fixed now.


New warning without warning?

Why does the new command prompt now say
"Warning
You are now about to paste text that contains multiple lines. If you paste this text into your shell, it may result in the unexpected execution of commands. Do you wish to continue?"
This is not necessary and I was enjoying using this software as my primary putty replacement until this warning was put in to "help" me.
I cannot find out how to remove this warning and it was added randomly in a background update.
How do you remove this? It is really annoying because it doesn't happen just once, it happens every time I paste something that dares to have multiple lines.
I need to be able to paste multiple lines dozens, maybe hundreds of times throughout my working day and I would appreciate being able to turn it off.
Thank you

If you take a look at the docs, you'll find the following setting will do what you want:
"largePasteWarning": false


Not enough Permission to share

Client error: POST https://api.linkedin.com/v2/ugcPosts resulted in a 403 Forbidden response: {"serviceErrorCode":100,"message":"Not enough permissions to access: POST /ugcPosts","status":403}

maybe you need set sopes write_public

am having the same problem even after i added write-public still the same problem. What should i do


Allow hourly calculation and added user summary at the end of the report

Codecov Report

Merging #1 into master will decrease coverage by 3.45%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master       #1      +/-   ##
==========================================
- Coverage   24.74%   21.28%   -3.46%
==========================================
  Files          13       13
  Lines         481      559      +78
==========================================
  Hits          119      119
- Misses        360      438      +78
  Partials        2        2


Update links to new path

Changes in this pull request

Fixed broken links in README.md and CHANGELOG.md
Also updated to use relative links

Pull request checklist

[x] All tests pass. Demo project builds and runs.
[x] I added tests, an experiment, or detailed why my change isn't tested.
[x] I have reviewed the contributing guide

Thanks @Sherlouk ! 🙌


Cannot Delete an Entity which has Relationships

Describe the bug
If you attempt to delete an Entity which has existing relationships, the Delete page will hang indefinitely and you will not be able to complete the deletion or exit the page.
To Reproduce
Steps to reproduce the behavior:

Find an Entity which has at least one relationship (e.g. a Publication linked to a Person, or a Person linked to a Publication)
Login as an Admin
Edit that Entity
Go to the "Status" tab
Click "Permanently delete" button
You will see the "Delete Item" page.  But, you will be unable to interact with the system any longer. The page will become unresponsive and the buttons at the bottom & links in the header will no longer work.

At this point, you have to close your tab/window to interact with the application again.

This issue ONLY impacts 8.x and is reproducible on https://sandbox.dspace.org/
Deletion of Entities works fine on https://demo.dspace.org/ (running 7.6.x)
Expected behavior
It should be possible to delete Entities that have relationships, just as you could in 7.x

@alexandrevryghem and @artlowel : Pinging you on this new issue as it may be semi-related to #3060 .  This bug is not about creation of relationships though, but rather about deletion.  If you want to claim it, let me know.  I think we have to fix this in 8.0 as it's no longer possible to delete Entities until you first remove all relationships.

@tdonohue I investigated this issue. You're right in saying that it's similar to https://github.com/DSpace/dspace-angular/pull/3060, but unfortunately the fix will also be similar in scale. We basically need to refactor item-delete.component.html to get all the direct function calls out of it. Calling functions from HTML always used to be problematic for performance, so I don't think this is a new bug in DSpace 8, but it seems that with the update to Angular 17 these sorts of issues have become more severe. It used to be slow, now it breaks the page.
I won't have time to work on this before OR. I could try to get it on Alex's plate for next week, but given the complexity I wouldn't expect a PR before the second half of next week


Create a minimum/maximum window size parameter

I would like to know if there are any plans to add a minimum/maximum size to the window to prevent the user from going too small or too large.

I would like this functionality as well

Implemented on the webview-x branch, please have a look.


[BUG] [xcb] Unknown request in queue while dequeuing

Describe the bug
Crash
To Reproduce
Unknown
Client Log:
N/A
Server Log:
https://gist.github.com/nurdism/7063bbfacfa889d576e0f845f4350c79

2680a1f should of fixed this


SDK-as-Modules refactor + Python Support

Goals

Get Python SDK-as-Module working
Simplify SDK-as-Module development+packaging process to extent possible
Setup builtin SDKs to be usable without hard dependency on internet (i.e. pulling images from dockerhub)

Overview of modified approach
(This has lots of overlap with previous iteration, not a mutually exclusive description)

dagger.json only has an sdk field, which is either the name of a built-in SDK ("go", "python", etc.) OR a module reference (no longer container image references)

ATM just assuming they are fixed references, have TODO for re-integrating moving references

Go SDK is the one special SDK which is not implemented as a Module

The Go codegen binary is packaged up in a container w/ the go runtime and then included in the engine image as tarball
That container is loaded by the engine and used to run Codegen and ModuleRuntime implementations, coded in core/schema/sdk.go as the goSDK struct

All other SDKs are Modules that must implement Codegen and ModuleRuntime Functions

There is still a notion of "builtin" SDKs, which is intended to consist of our "official" SDKs that we bundle w/ the Engine image (to prevent hard deps on the internet, though finishing the full implementation of that requirement is a TODO)
Builtin SDKs besides Go are still Modules though, they just are loaded from source that is packaged in the engine image

An SDK-as-Module has to choose its own SDK for its Module. This can be any Module, builtin or external

Python chooses Go because it's the second SDK in existence and thus has no other choice
You can thus think of a DAG of SDK Modules, where all paths eventually lead back to Go

TODOs:

[x] Verify a custom module using the Python SDK actually works

I can successfully run dagger mod init --sdk python --name test as long as I have a minimal pyproject.toml and empty main.py file and obtain what looks like the expected codegen output (under sdk/)
So it seems the ModuleRuntime and Codegen functions from the PythonSDK Module are basically working
However, I'm not sure where to go from here as I don't know how to write a module using the Python SDK :-) cc @helderco
EDIT: with Helder's help and some fixes we've got it working!

[x] General cleanup+dedupe with older code, commenting new code more, etc.
[x] Fix weird incongruity between builtin sdk dagger.json values and hardcoded paths in core/schema/sdk.go. Need to just honor dagger.json at all times.
[x] Add integ-test coverage for Python
[x] Fix include/exclude paths for non-Go sdks (link)
[x] Re-add use of container labels to point to paths in modules (or equivalent, have some variations on idea in mind) (link)

Realized this actually already worked as is; core no longer has any reliance on any particular paths, it just uses the workdir and entrypoint set on the container returned by ModuleRuntime, so we're good to go

[x] Include module name as inputs to Codegen/ModuleRuntime (or possibly just give them the whole pre-loaded Module config?)

Did this by adding ModuleConfig to our actual API, so SDK modules that need more metadata can load it as needed. Commit
This feels a bit more re-usable and nicer long-term than having SDK modules implementations update the opts they accept whenever some new need arises (or worst case and that doesn't end up being a problem, it's harmless)

Follow-ups:

Support for pinning moving references to SDK modules

I am going to save this for a follow-up I think; for now we will just leave SDK module references as specified by the user. I think pinning support is good, but there should be a way to also dagger mod sync --upgrade-sdk or something to "unpin" and update. That starts getting way out of scope here, better for follow-up.

Get the "no-internet" requirement fully working; need to include tarball w/ python interpreter, vendor modules/deps, etc.

I realized that this is probably best solved by something much more generic than just "include relevant base image for SDK". This is because built-in SDKs often need "base image + some commands + vendored deps" (i.e. python:3.10+apk add git + pip install)
The approach I have in mind is to use another optional Function on SDK Modules, Base, that returns a Container with everything needed to run the Module w/out internet deps. Then, we can add a mechanism to our CI for calling those, exporting to a local cache and including that cache in the engine image.
That should result in the simplest SDK dev process I think, in addition to perhaps being a useful feature outside just SDK development
However, this is getting way out of scope of this PR, so better for follow-up

Fix host directory ".." restriction (or adjust working dir of modules) (link) (discord discussion)

This is important but also not a blocker since there's a quick workaround; lifting the .. restriction is worth it's own discussion so I'm disentangling from this PR

Think this is good enough to go, marked as ready for review.
I ended up trimming some stuff that can be saved for follow-ups; mentioned in the description. Also updated the description with more details on how I fixed the various TODOs when relevant, may be helpful for context.
cc @vito @helderco @jedevc

I was the unlucky one to hit new trivy vuln scan failures first I think, I included fixes in this PR but then decided to spin those out to a separate one since it probably is gonna block everyone else trying to open PRs until fixed https://github.com/dagger/dagger/pull/5906

@wingyplus any ideas on the elixir codegen failure here? https://github.com/dagger/dagger/actions/runs/6541674992/job/17763524119?pr=5900#step:4:1067
== Compilation error in file lib/dagger/gen/client.ex ==
** (KeyError) key :selection not found
    expanding struct: Dagger.ModuleConfig.__struct__/1
    lib/dagger/gen/client.ex:362: Dagger.Client.module_config/3

@wingyplus any ideas on the elixir codegen failure here? https://github.com/dagger/dagger/actions/runs/6541674992/job/17763524119?pr=5900#step:4:1067
== Compilation error in file lib/dagger/gen/client.ex ==
** (KeyError) key :selection not found
    expanding struct: Dagger.ModuleConfig.__struct__/1
    lib/dagger/gen/client.ex:362: Dagger.Client.module_config/3

Let me take a look at this tonight. 🫡

@sipsma I have done some hacks on the Elixir codegen to make it pass. I have a plan to rework the Elixir codegen but it needs time to work on it. So in this way, it should not be a blocker on your PR now.

Thank you for the fixes @wingyplus!

On a separate note, I had some commits related to the otel upgrades in here previously, but ended up splitting that out into a separate PR because it's a whole separate can of worms https://github.com/dagger/dagger/pull/5906
So I removed them from here. Provided the only CI failure remaining is the scanner, I'll override and merge. CI on main is already failing due to the scanner (we pick up new vulns "out-of-band" and thus can get failures on main at any time), so shouldn't cause any harm.


🚀 Feature: Fill in remaining tsutils functions (that don't exist on TypeScript)

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
I'm filing this as a catch-all issue for anybody interested in contributing! 👋
tsutils has a lot of functions in it. Many of them are now available as part of this package. But some of them aren't. Welcoming contributions to add functions to this package that exist in tsutils but not yet in ts-api-tools.
The one exception to this is type guards such as isBinaryExpression that now exist on TypeScript itself. tsutils contains a lot of those functions for backwards compatibility with old tsutils+typescript versions - but this package doesn't need to.
Additional Info
Any new file whose contents are essentially a copy & paste of a tsutils file should have the same licensing header as other source files of that nature:
// Code largely based on https://github.com/ajafff/tsutils
// Original license: https://github.com/ajafff/tsutils/blob/26b195358ec36d59f00333115aa3ffd9611ca78b/LICENSE

@all-contributors please add @joshuakgoldberg for ideas.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙


Version updates

Update of the following versions:

alpine 3.12 -> 3.14
restic 0.12.0 -> 0.12.1
rclone 1.54.0 -> 1.56.0

Added Package:

gzip

to allow the use of the --rsyncable argument
for more efficient backup space management

see https://github.com/JsBergbau/Verschiedenes/issues/2 for more details

creating a new clean PR based on this master branch


Update portrait and parallel plot examples for mean climate

Update portrait and parallel plot examples for mean climate to use archived raw json from https://github.com/PCMDI/pcmdi_metrics_results_archive, instead of tar.gz

@lee1043 This got lost in my inbox! I saw it's merged so I'll pull main and give it a final test.

@acordonez it was a small minor change only on notebook so I was thinking it may be good to go, but additional test is always appreciated! Thank you :)

@lee1043 I get 404 Not Found errors for the JSON downloads in parallel_coordinate_plot_mean_clim.ipynb and portrait_plot_mean_clim.ipynb.
I was able to run the notebooks by changing the url text "https://raw.githubusercontent.com/PCMDI/pcmdi_metrics_results_archive/archive_raw_json/" to "https://raw.githubusercontent.com/PCMDI/pcmdi_metrics_results_archive/main/" in the download cell. Does that point to the right files?

@acordonez thank you for checking! Yes, main is correct. I might missed to update notebook after I merge branch in the PMP result repo.

@acordonez could you please upload your patched notebook via a new PR?


setup votequorum for ubuntu 14.04 lts, needed it configured so to get a ...

...quorum
This is what I had to do to get things working on:
pacemaker       1.1.10+git20 amd64
corosync        2.3.3-1ubuntu
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04 LTS
Release:	14.04
Codename:	trusty
I am not sure what the node config is for, for the vote quorum maybe a redhat thing? comments welcome.

Could you update the spec tests since the template contents have changed? Thanks!

There are a number of other settings in votequorum(5) that could be passed through, but the most useful (to me, and I expect a number of other people) would be the two_node flag. It'd be good to see that exposed in the manifests too, and it fits in with this change.

This has been hanging for over a year. I'm closing this in favour of #126 #178


chore: Fix an unaligned indent

What type of PR is this?

/kind cleanup
What this PR does / why we need it:
chore: Fix an unaligned indent
Which issue(s) this PR fixes:

NONE
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

What are the benchmark results of this change?

/assign


Add warnings for Undo/Redo history changes

Currently OpenRefine does not warn the user about losing a portion of their workflow history.  It is non-obvious if a user attempts to rollback and undo some changes, and then apply some new changes, they will silently lose any forward changes without a warning.  We should warn users about destroying forward history and not let them be surprised or reading details in our docs.
Proposed solution
A confirm dialog could appear before the very next Change operation a user does that will overwrite history after the chosen undo step:

User chooses to undo 3 steps
User attempts to do a new Transform on a column of text
A warning appears saying:

You have Undo/Redo changes after this point in your workflow history that will be lost and replaced with this operation.
Are you sure you want to change the workflow history?
[Yes] / [No]
[ x ] disable this warning in future

Alternatives considered

Additional context

@thadguidry @ostephens what do you think of the following dialog?

Erasure feels too formal. Maybe just delete?
Also if they get dialog that has 50 entries then need slightly larger and make it a scroll area to keep the bottom options always in view.

Replying to @elebitzero's comment on the PR:

Other applications like document editors, IDEs, MS Excel, etc. which have a stack of changes and have redo/undo, do not pop up a warning like this if you undo a few changes, and then start making new changes. The user is expected to know what they are doing in this case.

You are right that this behaviour is common in many other tools. That being said, I really agree with @thadguidry's perspective here, for the following reasons:

One important difference between OR and tools like Excel is that we have long-running operations (which can often take a very long time to execute) or operations which require a lot of manual reviewing (like the clustering dialog). Discarding the work of such operations by mistake is a lot more frustrating than discarding a few manual edits in some Excel spreadsheet
Our history stack is unbounded, so users can very easily go a few hundred operations back in time. That means it is also easy to discard any number of operations by mistake, and that's pretty bad. This is typically the case when people invest a lot of manual effort in reviewing reconciliation candidates, for instance.
From my personal experiences with the tool, and talking to other people doing trainings, I know that this lack of warning can currently be a big source of frustration, especially when you have been told that "everything you do is versioned so you can always go back and will not lose data". I think I remember @magdmartin saying that this frustration was currently a mandatory step in learning OpenRefine for a lot of people. I think this dialog can help with this learning process, avoiding the associated frustration.

For someone that knows how it works, it would be potentially confusing to have this warning dialog pop up.

I am curious how someone who knows how the history stack works would be confused by such a dialog. Surely it would only confirm what they already know, no? If you mean that they are annoyed by the dialog, we have the checkbox for them so that they are able to see it only once. That seems like a very reasonable annoyance, no?

A +1 for "overwrite" as a more intuitive term if the feature is implemented as described.
I'm not convinced about the use of an undoable "Remove"/"Rewind" operation here - I may not be envisaging it correctly but it feels like the operation history could become harder to read, understand and navigate with this added.
What I think could be useful (and what I do when I am nervous about losing work) is an option to make a duplicate of the project with the old operation history. But I suspect that's a separate feature and probably needs some discussion to work out if it's desirable and if so, how it would be best presented.
I think the change suggested, with the use of "overwrite" rather than "erase", and the checkbox option to let the user suppress the dialog in future is a good step delivering a small usability improvement.

@ostephens If you think of the history as a tree with branches... or Git... then it is certainly doable.
/ Project Created
├── mass update column 1
├── mass update column 1
│   └── transform column 2
│       ├── add column based on column 2
│       └── transform column 2
├── mass update column 3
└── mass update column 4
    ├── add column based on column 4
    ├── fetch URLs with column 4
    └── transform column 5 (fetch results)
        └── add column 6 based on column 5
            ├── move column 6 to beginning
            └── delete column 5

Each branch (or Git tag) is basically a path of different operations, a hard fork (OpenRefine operation dependency on previous operations).
A newer history undo/redo would simply have to version control both data|operations along the timeline (top to bottom) to store the entire history of a Project's evolution or alternative paths that the user took.  Where some of those paths (branches) might actually live on as being "stale" and not applicable to the final state of data.  Still, those alternative paths, are sometimes very useful when it comes to reproducibility of a project.  Like sharing a full Git repo and all it's indexing of history.
A user can then choose to see the data and results of an operation at each branch (or tag of a dependent operation).
There can even be 0 zero loss of data... you just "make a branch" or "tag the operation with lots of metadata".
You can imagine that before an operation actually performs any work we just... "make a branch" which we already do actually but not without the needed extra metadata we really need.  @wetneb is working on that basically as a 1st goal.
That usability workflow where all history is recorded (maybe forever, or maybe not and stale "branches" can purged) does have one downside... a potentially MUCH larger OpenRefine project filesize which of course @wetneb had some ideas on how to compress or even use different formats and technology (Snappy, Parquet, etc.) to account for a versioned set of Changes along History.  In RDBMS land, it's called a CDC, change data capture.  Which is another systemic way to handle a record of changes with pros/cons.
What was much more difficult to accomplish was the idea of reordering ordered sets of Changes along History (and giving a UX for it).  Certainly, doable when you can track (branch/version) each Change to know it's dependencies.  Fully knowing and mapping dependent operations is the ultimate goal I think to address if anyone wants to implement the idea of reordering sets of Changes along History.

@tfmorris, your idea is definitely an interesting one! I had never thought about this possibility.
I agree with @ostephens that, if we display this "rewind operation" like others (meaning, it has its own entry in the project's history), this is likely going to be an awkward UX: for instance, if I click on an earlier stage of my project, the light blue line which marks my position in the history would not jump back to where I clicked, but instead append a rewind operation at the end. Also, the project history would grow quite large (since one would never be able to delete any entry) and it would be difficult to see which entries were actually used to get to the final state of the project.
@thadguidry offering a history tree, instead of a history stack, where the history would branch off into distinct sequences of operations when applying an operation from an earlier state, is very much something we can consider.
I think this can be a useful feature if we can manage to design a reasonable UX for it.
It's well beyond the scope of this particular issue, but definitely achievable technically and in scope for the reproducibility project.
But, what I find very interesting is that Tom's rewind operation provides, in a way, a method to encode a history tree as a history stack. Given a list of normal operations intertwined with rewind operations, one can draw the corresponding history tree. Conversely, one can browse a history tree and convert it to a list of operations with rewinds (which is not unique, because it depends on the order in which you browse the tree).
In any case: by proposing to implement this dialog, I have really no intention to set the current behavior in stone. I very much intend to make the history more flexible, so that applying a change from an earlier state could, for instance:

branch off, turning the history into a tree as suggested by @thadguidry
keep the history linear but trigger a recomputation of the operations whose dependencies are affected by the change
other behaviours?

In those cases, the dialog may be reused to give the user a choice between various options, or it could be deleted entirely.
Perhaps the main purpose of this dialog is actually to spark discussions about the structure of project history and I think that's already a win!

Rolling back a project to a change and discarding all changes after that is a major operation. It is unusual that just by clicking on a history change does this rollback.
If I compare that to viewing the Git log in my IDE, clicking on a commit does not revert all commits after it. I have to explicitly invoke revert or reset if I want to do that.
Usability suggestions:

Selecting a row in the history just selects it and nothing else (selection may not even be necessary). The user will have to directly invoke the action 'Revert to here' on a history row to change the workspace. This can popup a confirmation dialog similar to the warning dialog which @wetneb is showing.

After the user confirms, they will immediately see the discarded changes disappear from the history, and a UI notification should be shown: 'Reset workspace to #3 -- 3 changes discarded  -- Undo'.
Currently, when you click on a history change no notification is shown and the discarded future entries remain 'greyed out' in the history until you perform another change. Delaying the truncation and warning until then is not as intuitive.

If the most common operation is to undo the last change, we should have an Undo button the user can click.

If the user clicks Undo, it reverts the last history change, and a notification shows: 'Undo - Reconcile cells in column Shrt_Desc to type Q2095  --  Undo'.
That seems easier than scrolling the history to the last entry, and selecting the (n-1)th row to undo the last change.

Rolling back a project to a change and discarding all changes after that is a major operation. It is unusual that just by clicking on a history change does this rollback.

Well that is currently not the case, right? If you click on a history entry in the past, OpenRefine will not discard the following entries. It will only do so if you then apply a change from that position.
I think it is generally useful to delay the deletion of the history entries to the application of a new change, because one might want to use the undo feature to check an earlier state of the project and then go back to the latest one, with no intention of deleting any history entry.

Selecting a row in the history just selects it and nothing else (selection may not even be necessary). The user will have to directly invoke the action 'Revert to here' on a history row to change the workspace. This can popup a confirmation dialog similar to the warning dialog which @wetneb is showing.

I generally like the idea of having multiple options available for a given history entry: to go back to this state, to undo this change only but preserve as many of the following changes as possible, to edit the settings of that operation and re-run it…
But at the moment there is really only one thing you can do in the history tab when selecting an entry, so it would feel a bit awkward to introduce this additional click to obtain the existing rewind functionality, especially because it is non-destructive at that stage. But then again, this dialog is not meant to stay on for ever and is only meant to be an easy fix for the current functionality.

If the most common operation is to undo the last change, we should have an Undo button the user can click.

We already have such a link in the notification generated by a change. We could totally have it elsewhere, so that it remains accessible even after the notification disappears. But that feels like a fairly independent change, no?

Rolling back a project to a change and discarding all changes after that is a major operation. It is unusual that just by clicking on a history change does this rollback.

It may depend on what you mean by "discarding" but I would say that this isn't how OpenRefine currently works nor is it proposed by this issue. Steps are only "discarded" from the history if the user rewinds one or more steps AND THEN does some other action that changes the data in the project. I have often used this fact to create/modify facets (creating a facet doesn't affect the history) while rewinding/forwarding the history to compare the facet before and after some set of changes.
However it is true that clicking on a history change does immediately apply the rollback - and I'd probably agree that this functionality could be made more obvious to the user. But I think that's a separate issue to what is being proposed here.

If the most common operation is to undo the last change, we should have an Undo button the user can click.
I'd agree that an Undo option that is more obvious would be nice - while we do display an 'undo' immediately the action has been taken, it doesn't persist.

But I agree with @wetneb these changes are independent of the change proposed here (which simply adds a clear warning for the existing behaviour)


What type of SharePoint Site?

I think it would help those new to Viva Learn to describe the type of SharePoint site that should be created e.g. should it be a Group Connected Team Site, Communication Site or a Team Site without a Microsoft Group etc.

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

ID: 3055d301-6a49-ab29-5fd0-2bdf1b4076d6
Version Independent ID: 3055d301-6a49-ab29-5fd0-2bdf1b4076d6
Content: Add SharePoint as a learning content source for Microsoft Viva Learning
Content Source: Viva/learning/configure-sharepoint-content-source.md
Service: viva
Sub-service: viva-learning
GitHub Login: @daisyfell
Microsoft Alias: daisyfeller

Hi @buildbod, thank you for your feedback.
I think there is no need to specify that as it could be any site type. I have tried to create the repository in a Teams site and Communication site successfully.

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


3.7.1 & 3.7.2 changelog?

It appears 3.7.1 and 3.7.2 are released on NPM, but I can't seem to find any history about the changes/releases. Can we get these documented in the CHANGELOG?
cc @flippmoke @artemp

Ah, found the 3.7.2 commit here: https://github.com/mapnik/node-mapnik/pull/869/files
@GretaCB would you mind updating the CHANGELOG when you have a chance?

Those releases were made from the 3.0.x branch. 3.7.1 has a changelog but 3.7.2 doesn't.

Thanks @Algunenano - will be good to get these in sync, since 3.0.x branch naming scheme doesn't match 3.7.x.


sg.txt

Add Saigon University

@lveme Regrettably, this request has signs of fraud. I have to close it without merging. If you are a student of this school, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


Specific binary classification option

Is your feature request related to a problem? Please describe.
Currently model builder treats all classification problems as multiclass even if the label for the data being provided is binary.  For whatever reason this doesn't seem to produce as good of model results as running it through the AutoML platform using a binary classification experiment.  Additionally running binary data as multiclass hides many of the useful metrics that get generated when running the binary classification experiment in AutoML
Describe the solution you'd like
Have a simple checkbox to indicate that your data is binary and should be run through a binary classification experiment
Describe alternatives you've considered
The current alternative is to build your own application based on using the BinaryClassification_AutoML sample or similar https://github.com/dotnet/machinelearning-samples/tree/master/samples/csharp/getting-started/BinaryClassification_AutoML

@briacht  for notification
After @beccamc 's proposal on ColumnDataType being implemented, we should be able to treat Multi-classification and Binary-classification differently through Advance Data option.

@LittleLittleCloud You're saying if the data kind of the label column is bool we can automatically run binary instead of multiclass? I'm planning to make that change this week. Is this something you could on the backend add before we ship in March?

@LittleLittleCloud Is this in the changes you've made for private preview? Or are we doing it later?

@beccamc No I haven't made any change related to this issue yet. But maybe I'll start soon

After model builder starts inferring the column with {0,1} as a numeric type instead of a boolean, all parts for this work has been completed and it is a good time to start this thread. Even though misformat label problem still exists, this problem is not that severe anymore because the most confusing part (label with 0/1 because false/true) is not the default behavior now. And the other parts (label with T/F, True/False => true/false) are not that confusing.
After this change has been made, there's still a way for users if they want to keep their label format in the output by change label type from boolean to string. And we should update in the doc that if label type is boolean, binary classification will be made and output label type will be boolean type too, which is a feature instead of a bug.

Created dotnet/docs#25922 to track and update docs accordingly.


Numba future feature flag design

For the migration from reflected list to typed list, we need to have toggle-able feature flags that Numba users and library authors can opt into without affecting the entire applications.  In Python, this is done with the from __future__ import X mechanism, which enables backward incompatible features to be turned on at the module level.  This mechanism doesn't seem to be extensible to usage by other libraries, so we need to do our own thing.
This proposal is to have 3 layers of feature flag setting:

Package level
Module level
Decorator level (only for testing purposes)

The mechanism for package level and module level will be the same.  We will have a numba.__future__ module that will contain attributes like disable_reflected_list which correspond to a particular configurable feature.  In order to opt into this feature early (which will become mandatory in a future release) can import the symbol at global scope in their module
from numba.__future__ import disable_reflected_list

As with Python, we will never remove things from the numba.__future__ module, even once they stop having an effect because the future feature has become mandatory.
Numba will scan the globals for each function compiles for these special feature flag values, and modify the compilation behavior accordingly.  This allows the future behavior to be enabled in scripts, notebooks, and packages on a module-by-module basis.
As a convenience for package authors, if a future flag is imported in the top-level __init__.py for the package, it will apply to all functions in the entire package tree.
For testing purposes, we may introduce private flags (prefixed with _) to turn on and off future features in individual functions, but we advise 3rd party code not to use those flags as we will remove them without warning in future releases.
Open questions:

Does this cover everything?
Is the package level setting introducing needless complexity?  Walking up the import tree might not be worth it to save a package from having to import the future feature in each of the files where they define compiled functions.

make future symbols (like disable_reflected_list) a callable so that people can call it to make their linters happy.  The actual call will have no effect.

Also, after some discussion, we are going to drop the package-level future flags.  Each source file needs to import the future flag.  If code is being generated some other creative way, it may need to be injected into the globals to exec.

Implemented by #4883

closing this issue since this was juts for design discussion.  Feature can be tracked in #4883.


ArangoDeployment .id is missing from docs

fwiw, <group>.id is also missing from docs ref https://github.com/arangodb/kube-arangodb/issues/1141#issuecomment-1274286483
Originally posted by @ddelange in https://github.com/arangodb/docs/issues/1141#issuecomment-1274955619
in our cluster, I needed to edit this one-time pod to allow it to run on our tainted arm nodes and finish the new cluster's boot sequence

This and other options appear to be missing indeed. Some might be used internally only, but this is to be answered by the responsible team. I'm waiting for their clarification.


Update to liveview 1.0

The first commit closes #404 and the following one format the code to use the new template interpolation with brackets.

Setting it as a draft because the demo app needs an override for the phoenix_live_view because sentry dependency isn't compatible yet.

Thanks! <3 I will take a look tomorrow.
We will probably do the 0.9 release without this and a 0.10 release with LiveView 1.0 support shortly after.

FYI Sentry has been updated to use LiveView 1.0 . Would love to see Backpex on LiveView 1.0 ;)


fix: (#4091) model size not displaying

Describe Your Changes

Model size not displayed.

Self Checklist

[ ] Added relevant comments, esp in complex areas
[ ] Updated docs (for bug fixes / features)
[ ] Created issues for follow-up changes or refactoring needed

It works


rsbep-backup: init at 2010.06.14

Things done

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

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

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

@erikarvstedt You need to add yourself to https://github.com/NixOS/nixpkgs/blob/master/lib/maintainers.nix.

Oh, sorry, my other introductory PR fixes this, but it's still pending.

Is there a reason not to use https://www.thanassis.space/rsbep-0.1.0-ttsiodras.tar.bz2 as the source?
And I think the package should just be called "rsbep".

I've changed the name to rsbep.
The differences to the tar version don't affect any code. Nonetheless, I'd prefer to reference a source tree that's in version control; for transparency and future maintainability. If you strongly recommend the tar version, I'll change it.

Done.

Change: I've used the more technical description from the debian manpages

@GrahamcOfBorg build rsbep

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘fuse-2.9.7’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/os-specific/linux/fuse/common.nix:77 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/ivs8icf1ngk99gs86ljpqy2229zlvg9j-rsbep-0.1.0/bin/rsbep_chopper
shrinking /nix/store/ivs8icf1ngk99gs86ljpqy2229zlvg9j-rsbep-0.1.0/bin/rsbep
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/ivs8icf1ngk99gs86ljpqy2229zlvg9j-rsbep-0.1.0/bin
patching script interpreter paths in /nix/store/ivs8icf1ngk99gs86ljpqy2229zlvg9j-rsbep-0.1.0
/nix/store/ivs8icf1ngk99gs86ljpqy2229zlvg9j-rsbep-0.1.0/bin/melt.sh: interpreter directive changed from "/bin/sh" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/sh"
/nix/store/ivs8icf1ngk99gs86ljpqy2229zlvg9j-rsbep-0.1.0/bin/poorZFS.py: interpreter directive changed from "/usr/bin/env python" to "/nix/store/g91hijypiqyfd1h11lsz0x75aymn3jdn-python-2.7.14-env/bin/python"
/nix/store/ivs8icf1ngk99gs86ljpqy2229zlvg9j-rsbep-0.1.0/bin/freeze.sh: interpreter directive changed from "/bin/sh" to "/nix/store/zqh3l3lyw32q1ayb15bnvg9f24j5v2p0-bash-4.4-p12/bin/sh"
checking for references to /tmp/nix-build-rsbep-0.1.0.drv-0 in /nix/store/ivs8icf1ngk99gs86ljpqy2229zlvg9j-rsbep-0.1.0...
/nix/store/ivs8icf1ngk99gs86ljpqy2229zlvg9j-rsbep-0.1.0

Success on aarch64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/bwvizpl2ygqyszlqmdjicvqbghp6n0p9-rsbep-0.1.0/bin/rsbep_chopper
shrinking /nix/store/bwvizpl2ygqyszlqmdjicvqbghp6n0p9-rsbep-0.1.0/bin/rsbep
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/bwvizpl2ygqyszlqmdjicvqbghp6n0p9-rsbep-0.1.0/bin
patching script interpreter paths in /nix/store/bwvizpl2ygqyszlqmdjicvqbghp6n0p9-rsbep-0.1.0
/nix/store/bwvizpl2ygqyszlqmdjicvqbghp6n0p9-rsbep-0.1.0/bin/poorZFS.py: interpreter directive changed from "/usr/bin/env python" to "/nix/store/arcajcjh1j23pbdfcmdjl7l3dhaf4miw-python-2.7.14-env/bin/python"
/nix/store/bwvizpl2ygqyszlqmdjicvqbghp6n0p9-rsbep-0.1.0/bin/freeze.sh: interpreter directive changed from "/bin/sh" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/sh"
/nix/store/bwvizpl2ygqyszlqmdjicvqbghp6n0p9-rsbep-0.1.0/bin/melt.sh: interpreter directive changed from "/bin/sh" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/sh"
checking for references to /build in /nix/store/bwvizpl2ygqyszlqmdjicvqbghp6n0p9-rsbep-0.1.0...
/nix/store/bwvizpl2ygqyszlqmdjicvqbghp6n0p9-rsbep-0.1.0

For Darwin, I could disable poorZFS.py with its failing fuse depenency. Would this make sense?

I could also remove it alltogether. I think the author wrote it as a proof of concept and not for real world use on a modern UNIX.

What does this script?

Quoting the author:
This command will mount a FUSE-based filesystem in /strong (using the /reed-solomoned-data directory to store the actual files and their "shielded" versions). Any file you create in /strong, will in fact exist under /reed-solomoned-data and will also be shielded there (via freeze.sh). When opening for reading any file in /strong, data corruption is detected (via melt.sh) and in case of corruption the file will be corrected using the Reed-Solomon "shielded" version of the file (which is stored alongside the original, and named as originalFilename.frozen.RS). The .frozen.RS versions of the files are not visible in the /strong directory, and are automatically created (in /reed-solomoned-data) when a file (opened for writing or appending) is closed.
I coded this mini-fs using Python-FUSE in a couple of hours on a boring Sunday afternoon, so don't trust your bank account data with it... It's just a proof of concept (not to mention dog-slow - due to the necessary data interleaving). Still, if your machine is only equipped with one drive, this will in fact transparently shield you against bad sectors, faulty power supplies, messy IDE cabling, etc.

Note: I coded this filesystem adding 20 or so lines of Python (spawning my freeze/melt scripts) into the Python/FUSE basic example. Anyone who has ever coded a filesystem driver for Windows knows why this justifies a heart attack - FUSE (and Python/FUSE) rock!

There are obviously much better alternatives to this.

@erikarvstedt I guess we don't need it badly.

Here's a branch without poorZFS.py. Merge what you prefer. (I'd vote for removing it.)


v1.1 UI updates

@/components/ui

[x] <Accordion /> 🆕
[x] <Avatar /> 🆕
[x] <Badge />

Add type: "text" | "number" prop (number has smaller x-padding)
Add type-checked intent="black" and intent="white" variants
Add data attribute data-length-one if children implements .toString() and returns length 1
Update variant="primary"'s dark:text-white and text-black to just text-white for accessibility and consistency (inverted for intent="warning")
Update variant="secondary"'s text-*-9 to text-*-11 for accessibility and consistency
Render <Badge /> as <span> instead of <div>
Ensure <Badge /> has a minimum aspect ratio of 1 / 1
Refactor intent="primary" $\rightarrow$ intent="info"

[x] <Button />

Add <ButtonGroup /> 🆕 and corresponding interactive styles (hover:* and focus-visible:*)
Add default newTab=false
Add type-checked variant="solid" & { intent="black" | "white" } variants
Add button-left-icon="", button-right-icon="", and button-content="" selectors
Update variant="primary"'s dark:text-white and text-black to just text-white for accessibility and consistency (inverted for intent="warning")
Update variant="outline" | "ghost" | "text"'s text-*-9 to text-*-11 and add bg-transparent for accessibility and consistency
Update size="xl"'s rounded to rounded-md
Remove cursor-not-allowed and add pointer-events-none to disabled=true variants
Refactor intent="primary" $\rightarrow$ intent="info"

[x] <Checkbox /> 🆕
[x] <CodeBlock />

Add logo, breakLines, and switcher props
Add diff syntax highlighting
Refactor "copy to clipboard" button to ./actions w/ source switcher
Animate <Copy />/<Check /> icons on copy
Display closable, `intent="success" toast on copy

[x] <Command /> 🆕
[x] <Dialog /> 🆕

Bump @radix-ui/react-dialog ^1.0.4 $\rightarrow$ ^1.0.5 (latest)

[x] <Drawer /> 🆕
[x] <Dropdown /> 🆕
[x] <Form /> 🆕
[x] <HoverCard />

Bump @radix-ui/react-hover-card ^1.0.6 $\rightarrow$ ^1.0.7 (latest)
Add inPortal, triggerProps, defaultOpen, open, onOpenChange as props to preserve component API

[x] <IconButton />

Inherit all styles from <Button /> for consistency and code cleanliness
Refactor intent="primary" $\rightarrow$ intent="info"

[x] <Input /> 🆕
[x] <Popover /> 🆕
[x] <Radio /> 🆕
[x] <Select />

Inherit all styles from <Button /> for consistency and code cleanliness
Add comments for pl-*, pr-*, and right-* values
Add fullWidth prop
Add type-checked variant="solid" & { intent="black" | "white" } variants
Add select-content="" selector
Update variant="primary"'s dark:text-white and text-black to just text-white for accessibility and consistency (inverted for intent="warning")
Update variant="outline" | "ghost"'s text-*-9 to text-*-11 for accessibility and consistency
Remove <Select.Item /> (in favor of the HTML-native <option>)
Make the component a React.ForwardedRef
Refactor intent="primary" $\rightarrow$ intent="info"

[x] <Switch /> 🆕
[x] <Table /> 🆕
[x] <Tabs /> 🆕

Bump @radix-ui/react-tabs ^1.0.3 $\rightarrow$ ^1.0.4 (latest)

[x] <TextArea /> 🆕
[x] <Toaster /> and toast

Refactor intent="primary" $\rightarrow$ intent="info"
Refactor @/components/ui/toaster $\rightarrow$ @/components/ui/toast
Refactor useToast $\rightarrow$ toast and imports
Replace @radix-ui/react-toast with sonner for smoother animations and performance (see Sonner docs for API changes)
action now takes the form of ReactNode | Action, where type Action = { label: string; onClick: () => void }
Place <Toaster /> higher in the component tree
Add hasCloseButton prop (note: this button will show on hover if on a non-touchscreen device, and always be displayed otherwise)

[x] <Tooltip />

Bump @radix-ui/react-tooltip ^1.0.5 $\rightarrow$ ^1.0.7 (latest)
Add inPortal, triggerProps, defaultOpen, open, onOpenChange as props to preserve component API

Miscellaneous

Update code convention

Remove imports for React types (e.g. FC $\rightarrow$ React.FC)
Remove unnecessary displayNames
Add exports comment divider in @/components/ui/*/index.tsxs

Update dependencies
Update <Logo /> hover styles to border color indicator
Fix <Logo /> focus state
Apply focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-blue-9 to button in globals.css

lgtm


H5py 2.10

Use h5py with pip. This breaks using the same version for pip and conda but we do get a version that is actually supported for python 3.8, has wheels and we can thus remove the last build dependencies

Looks like there are currently only windows wheels for 3.8 so this will have to wait a bit


add some details about renv, style of fail, unit testing to write_a_check

Closes #171

I believe in my heart of hearts that outlining 4 different ways of installing the package from devel in the readme is truly overkill.  I'd suggest updating to just have the r open sci link and maybe install_github with ref="devel" at most.  Other ways of using install_github just seem instructive on how that function works.

Ok- how about including one example with install_github, and use comments and/or a link to the source function doc in the README?

👍

Thanks for this update @sarabodach !!!


Mapbox should render beyond tile boundaries

Duplicate: https://github.com/aperture-sh/tank/issues/11