[Bug] Unhandled exception when using --state and referring to a removed test

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Description
Hi, recently in one of our projects a generic test, which was still referenced by some models, was by coincidence removed.
If we run dbt run, we would get pretty clear error:
15:18:37    Compilation Error in test sample_test_model_a1_ (models/schema.yml)
  'test_sample_test' is undefined. This can happen when calling a macro that does not exist. Check for typos and/or install package dependencies with "dbt deps".

But, if we run dbt run --select state:modified --state previous-artifacts (which we use by default) we get:
...
  File "/Users/jaklan/.local/pipx/venvs/dbt-core/lib/python3.10/site-packages/dbt/graph/selector_methods.py", line 782, in search
    if checker(previous_node, node, **keyword_args):  # type: ignore
  File "/Users/jaklan/.local/pipx/venvs/dbt-core/lib/python3.10/site-packages/dbt/graph/selector_methods.py", line 684, in check_modified_content
    upstream_macro_change = self.check_macros_modified(new)
  File "/Users/jaklan/.local/pipx/venvs/dbt-core/lib/python3.10/site-packages/dbt/graph/selector_methods.py", line 670, in check_macros_modified
    return self.recursively_check_macros_modified(node, visited_macros)
  File "/Users/jaklan/.local/pipx/venvs/dbt-core/lib/python3.10/site-packages/dbt/graph/selector_methods.py", line 644, in recursively_check_macros_modified
    macro_node = self.manifest.macros[macro_uid]
KeyError: None

Generally, It was not noticed during MR, because in our MR pipelines we run a mix of dbt parse + dbt-checkpoint to identify only changed models and avoid compiling the full project - and that obviously doesn't cover the issues like above. However, I wonder whether such issue shouldn't be identified already during parsing?
Anyway, back to the problem - when playing a bit with debugger, we can see such node:
(GenericTestNode(database='memory',
                 schema='_jaklan_dbt_test__audit',
                 name='sample_test_model_a1_',
                 resource_type=<NodeType.Test: 'test'>,
                 package_name='project_a',
                 path='sample_test_model_a1_.sql',
                 original_file_path='models/schema.yml',
                 unique_id='test.project_a.sample_test_model_a1_.77f8cfc6f6',
                 fqn=['project_a', 'sample_test_model_a1_'],
                 alias='sample_test_model_a1_',
                 ...
                 depends_on=DependsOn(macros=[None,
                                              'macro.dbt.get_where_subquery'],
                                      nodes=['model.project_a.model_a1']),

The issue is with the macros=[None, ...] part - that None is then retrieved as macro_uid and fails dictionary look-up: macro_node = self.manifest.macros[macro_uid].
Imho the easiest solution would be to add a try-except to raise the concrete error like:
{node.name} depends on macro or test, which doesn't exist anymore
unless you want to handle it in more sophisticated way.
Environment
- OS: macOS
- Python: 3.10
- dbt: 1.8.5

Which database adapter are you using with dbt?
redshift, duckdb (doesn't matter)

Thanks for reporting this @jaklan !
I was able to reproduce the error you got with the files and commands below.

Reprex

models/my_model.sql
select 1 as id

tests/generic/my_unique.sql
{% test my_unique(model, column_name) %}

-- custom generic test
with validation_errors as (

    select {{ column_name }}
    from {{ model }}
    group by {{ column_name }}
    having count(*) > 1

)

select *
from validation_errors

{% endtest %}

models/_models.yml
models:
  - name: my_model
    columns:
      - name: id
        tests:
          # custom generic test
          - my_unique

Run these commands:
dbt parse --target-path previous-artifacts
mv tests/generic/my_unique.sql tests/generic/my_unique.sql.x
dbt compile
dbt run --select state:modified --state previous-artifacts

Get this output:
$ dbt parse --target-path previous-artifacts
mv tests/generic/my_unique.sql tests/generic/my_unique.sql.x
dbt compile
dbt run --select state:modified --state previous-artifacts

19:56:23  Running with dbt=1.8.0
19:56:26  Registered adapter: duckdb=1.8.3
19:56:27  Performance info: /Users/dbeatty/projects/copier-templates/duckdb-core-10630/previous-artifacts/perf_info.json
19:56:28  Running with dbt=1.8.0
19:56:29  Registered adapter: duckdb=1.8.3
19:56:29  Found 1 model, 1 test, 411 macros
19:56:29
19:56:29  Concurrency: 1 threads (target='dev')
19:56:29
19:56:29  Encountered an error:
Runtime Error
  Compilation Error in test my_unique_my_model_id (models/_models.yml)
    'test_my_unique' is undefined. This can happen when calling a macro that does not exist. Check for typos and/or install package dependencies with "dbt deps".
19:56:30  Running with dbt=1.8.0
19:56:31  Registered adapter: duckdb=1.8.3
19:56:31  Found 1 model, 1 test, 411 macros
19:56:31  Encountered an error:
None
19:56:31  Traceback (most recent call last):
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/cli/requires.py", line 138, in wrapper
    result, success = func(*args, **kwargs)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/cli/requires.py", line 101, in wrapper
    return func(*args, **kwargs)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/cli/requires.py", line 218, in wrapper
    return func(*args, **kwargs)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/cli/requires.py", line 247, in wrapper
    return func(*args, **kwargs)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/cli/requires.py", line 294, in wrapper
    return func(*args, **kwargs)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/cli/requires.py", line 332, in wrapper
    return func(*args, **kwargs)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/cli/main.py", line 568, in run
    results = task.run()
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/task/runnable.py", line 506, in run
    self._runtime_initialize()
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/task/compile.py", line 125, in _runtime_initialize
    super()._runtime_initialize()
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/task/runnable.py", line 151, in _runtime_initialize
    self.job_queue = self.get_graph_queue()
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/task/runnable.py", line 144, in get_graph_queue
    return selector.get_graph_queue(spec)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 331, in get_graph_queue
    selected_nodes = self.get_selected(spec)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 321, in get_selected
    selected_nodes, indirect_only = self.select_nodes(spec)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 160, in select_nodes
    direct_nodes, indirect_nodes = self.select_nodes_recursively(spec)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 132, in select_nodes_recursively
    bundles = [self.select_nodes_recursively(component) for component in spec]
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 132, in <listcomp>
    bundles = [self.select_nodes_recursively(component) for component in spec]
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 132, in select_nodes_recursively
    bundles = [self.select_nodes_recursively(component) for component in spec]
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 132, in <listcomp>
    bundles = [self.select_nodes_recursively(component) for component in spec]
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 132, in select_nodes_recursively
    bundles = [self.select_nodes_recursively(component) for component in spec]
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 132, in <listcomp>
    bundles = [self.select_nodes_recursively(component) for component in spec]
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 130, in select_nodes_recursively
    direct_nodes, indirect_nodes = self.get_nodes_from_criteria(spec)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 84, in get_nodes_from_criteria
    collected = self.select_included(nodes, spec)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector.py", line 70, in select_included
    return set(method.search(included_nodes, spec.value))
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector_methods.py", line 782, in search
    if checker(previous_node, node, **keyword_args):  # type: ignore
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector_methods.py", line 684, in check_modified_content
    upstream_macro_change = self.check_macros_modified(new)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector_methods.py", line 670, in check_macros_modified
    return self.recursively_check_macros_modified(node, visited_macros)
  File "/Users/dbeatty/projects/environments/dbt_1.8/lib/python3.10/site-packages/dbt/graph/selector_methods.py", line 644, in recursively_check_macros_modified
    macro_node = self.manifest.macros[macro_uid]
KeyError: None

I have tried one more thing today - to run:
dbt run --select state:modified,package:this --state previous-artifacts

instead of:
dbt run --select state:modified --state previous-artifacts

when the removed test was only affecting an upstream package, but not the current one. Unfortunately, the result is the same.

Looks like this happens semi-frequently, we should provide a better error message in this case

@ChenyuLInx that's a "quick fix", but the real one would be to discover already during parsing that model refers to non-existing test


Adding direct NPM support

This looks nice but if I want to integrate this with an ongoing project its a headache to integrate.
Could you make it an npm package so it installs with npm install revodropdown ? Way easier to set and go! Is there any way to integrate this dropdowns with my project easyer than cloning the whole project?
Thanks

Hello @aldakata, it's present on npm from the beginning:
https://www.npmjs.com/package/@revolist/revo-dropdown


DBZ-5492 Checkout to base branch of the PR for building debezium core

https://issues.redhat.com/browse/DBZ-5492

@ani-sha Could you please take a look at https://github.com/debezium/debezium-connector-db2/runs/7764470017?check_suite_focus=true ?
I merged the change only for this repo as a testbed and it seems that the main on the core repo is still used.

@jpechane Not sure, why it didn't happen as expected. I will take another look into it.


Write button_configuration

Write [docs/button_configuration.md](docs/button_configuration.md)
Suggestions for content:

[ ] General concept, explaining eventtypes
[x] Numbering of buttons
[ ] Label & Toplabel
[ ] Eventtypes:
[x] Label, with example
[x] Toplabel, with example
[x] Click, with example
[x] Longclick, with example
[x] Click Release, with example
[x] Blue/Red/Green LED, with example
[x] RGB Led
[x] Led
[ ] Brightness

working on it


fix: export SummaryBoxHeading and SummaryBoxContent

Summary
Adds the exports from external PR #2098

@all-contributors please add @lpsinger for bugs,code

@all-contributors please add @lpsinger for bug and code

Once more, with feeling.
@all-contributors please add @lpsinger for bug and code


Channel override: PhET Interactive Simulations (es)

Channel ID: Pending...
Styling:

[ ] Custom primary color?: #136D91
[ ] Custom secondary color? #136D91
[ ] Custom header color? #613863
[ ] Custom thumbnail? https://www.dropbox.com/sh/t24n9xqjm0jciab/AAC8o7Vg-uwo5Zw1i1TuZgvXa?dl=0
[ ] Custom icon? https://www.dropbox.com/sh/t24n9xqjm0jciab/AAC8o7Vg-uwo5Zw1i1TuZgvXa?dl=0

Options:

[ ] Has carousel section? NO
[ ] Has dark header? YES
[ ] Display logo in header? YES

PhET (es) channel token is: gobaz-fakin
I'm not sure how to find the Channel ID but here is the URL when viewing in Kolibri Studio. I'm assuming it is one of the long numbers at the end?
https://studio.learningequality.org/en/channels/8fa678af1dd05329bf3218c549b84996/#/d3ed15b53a6042a5affb2db979491d9b

@hydrolet thanks! Comparing the URLs from studio with the online instace channel ID bit, I think it's  this bit:
https://studio.learningequality.org/en/channels/ 8fa678af1dd05329bf3218c549b84996/ #/d3ed15b53a6042a5affb2db979491d9b

@manuq the English and Spanish versions can share the presentation

@jofilizola from now on when reusing a presentation you can remove all the placeholder text (except ID) and say "like that other channel".

The English Channel as I can see on the online instance has the wrong background color, since they are reusing the presentation I imagine both have the same problem.
Custom header color should be #613863 for:

[ ]  197934f144305350b5820c7c4dd8e194
[ ]  8fa678af1dd05329bf3218c549b84996

@jofilizola that is

for the color, right? The text is white should that remain?

Let's open a new ticket with the follow ups from above.

Follow up ticket: https://github.com/endlessm/kolibri-explore-plugin/issues/712


Core tests: transform

Also, feel free to make a lot of small functions that are more focused (you can keep the existing longer functions of course)


Can't swipe on points on the sample page charts anymore

Not sure if this existed before or not but it seems like a pretty new bug. I used to be able to change points across a chart in the sample pages from my memory.

If you long-press on the chart, it will take handle the ongoing touches, otherwise, PageView will handle the swipes, it was the default behavior.

Fair enough, thanks! I see that the pan gets interrupted by the pageview but the longpress does not. To test the panning I had to just remove the pageview temporarily (or reduce it to one page).

No problem.
Thanks!


Test Bug 113

Summary
Short summary of what is going on or to provide context.
Steps To Reproduce:

This is step 1.
This is step 2. All steps should start with '1.'

Expected result
Describe what should have happened.
Actual result
Describe what actually happened instead.
Additional information
Feel free to attach a screenshot.
Salesforce Extension Version in VS Code: 60.13.0
Salesforce CLI Version: @salesforce/cli/2.37.2 darwin-arm64 node-v18.18.2
OS and version: MacOS Sonoma
VS Code version: 1.83.4
Most recent version of the extensions where this was working: it never worked

Thank you for filing this issue.  We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.


draft of heapwords size estimate of utxos

In order to be able to gauge how much ada must be in a UTxO, we need to estimate the size of the UTxO
This draft PR uses HeapWords to get estimates of the sizes of real UTxO entries with the purpose of using the numbers produced by the heapWords function to create an somewhat accurate and transparent calculation of the min-ada-value (without actually using the exact size of the UTxO)
With the following simplifications:

instead of defining HeapWords for each kind of address, look at the average case - the Shelley-type base address, made up of stake and payment addresses of 28 bytes
count each policy ID and each asset name (instead of counting asset IDs)
no overhead due to adding new UTxO map entry (only the size of the data in the UTxO itself)

Closing this in favour of #2101

Closing this in favour of #2101


change secret ARNs to 6 random chars at end

Fixes  #5199

It looks like the CI tests ran on an old commit, prior to me fixing linting and force pushing. How do I retrigger the CI?

Well, I figured I could remove just the spaces using the Github UI. Didn't expect it to remove the new line completely.
Hopefully at least the linter is happy now.


debian OK

I appreciate your effort in attempting to contribute to this Ansible role.
However, at the moment, I don't have any plans to maintain the Debian/Ubuntu distro due to the lack of automated testing.
Additionally, this pull request does not include any changes to the information in the README, and the uninstallation part remains untouched. Therefore, I cannot accept this pull request as the quality is not up to the required standard.


Flooding of "Permanently added  to the list of known hosts"

At some stage of development, I'm getting a flood of
[INFO] Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.

which also seems to have impact on performance.
Is this something we could avoid or why is this happening?

Isn't this a duplicate of #101?


feat(extras): improve ruby extra by letting user chose

What is this PR for?
Shopify started working on its own LSP (https://github.com/Shopify/ruby-lsp) and it performs way better than Solargraph which has a lot of limitations. This paired with sorbet gives better IntelliSense when navigating the code.
This PR follows the same approach as Python and lets the user configure through vim.g options the lsp and formatter for ruby, without overriding any configuration.
Does this PR fix an existing issue?
One caveat though is that RubyLsp does not work very well with NeoVim < 0.10 https://github.com/Shopify/ruby-lsp/blob/main/EDITORS.md#neovim
Checklist

[x] I've read the CONTRIBUTING guidelines.

Removed sorbet because if your ruby project does not have it setup you'd get warnings so it's better if you add it yourself

Can you change it similar to how it's done for python?
So add a doc section to the top and a vim.g var to chose.
I'm fine with that flag defaulting to rubylsp on NEovim >= 0.10

Can you change it similar to how it's done for python? So add a doc section to the top and a vim.g var to chose. I'm fine with that flag defaulting to rubylsp on NEovim >= 0.10

Thank you for the idea @folke this is soo much better i took the opportunity to also make the formatter use this

ty!

how to make rails model validation auto completion work?


Remove search field autofocus

Autofocusing fields gives bad user experience on mobile and tablet devices with soft keyboard.
Please ref #854 for discussion.

Hi @miohtama, it looks like this is already being addressed in #985.

Closed via #985


[test] Count profiler renders not passive effects

Uses React.Profiler instead of useEffect to count commits (implementation in https://github.com/eps1lon/material-ui/blob/af74ef1e9fcbbc40d23b0fd6f05fb05fac42689e/test/utils/components.js#L45-L63). useEffect will have slightly different semantics in React 18. See https://github.com/reactwg/react-18/discussions/18 for more context.
/cc @oliviertassinari and @dtassone. I think one of you asked me a while back how to test render count.

Thanks for the ping, we do count commits with a useEffect in https://github.com/mui-org/material-ui-x/blob/45093913e390b9c71b89a3debf76a58a46e68a2f/packages/grid/x-grid/src/tests/sorting.XGrid.test.tsx#L232-L241.

Thanks for the ping, we do count commits with a useEffect

Yep, that'll no longer work in React 18. You should start migrating to React.Profiler when you get the chance.

@eps1lon Reading this thread https://github.com/reactwg/react-18/discussions/19, it seems that we could measure renders with a useEffect if we disable the strict mode for a specific test (not saying that we should do it, but to make sure I got it right).
@dtassone I have opened this umbrella issue for React 18: https://github.com/mui-org/material-ui-x/issues/1870.

No that could still fail once Offscreen APIs get implemented

No that could still fail once Offscreen APIs get implemented

@eps1lon Oh sure, right. I meant for the tests specifically. All good


collection gallery

site and student sections

site section includes all published collections, with separate columns with clickable cards for 'dataset' and 'place' collections
student section includes all student place collections nominated by group leaders and accepted by WHG editorial staff
TBD?

search? keywords column? map?

completed - for now


Deploy to AWS with Spot Pricing (ECS, EFS) - Template Linked

Hi, this probably isn't the best place to bring this up... but here goes!
I've put together a CloudFormation template to perform a complete deployment of a Factorio server to AWS using your docker images. Scenarios won't work at present, as this isn't something I've looked at yet.
Optionally it can use spot instances rather than on-demand, here in Australia they're generally super cheap and very reliable. State is persisted to EFS, so the server itself is ephemeral.
I'm currently using this template to run an 0.17 server for me and a few friends. I shut it down when not in use to save on running costs.
Anyway, take a look, if you're interested I can submit a PR updating the readme with links to my repo.
https://github.com/m-chandler/factorio-spot-pricing

I think this is worthy of a link from our readme to your github.

Closing, this has been merged.


[tool_crash] StateError: Bad state: Future already completed

Command
flutter --no-color attach --machine --device-id=RZ8MB0N9A9P lib\main.dart

Steps to Reproduce

...
...
...

Logs
StateError: Bad state: Future already completed
#0      _AsyncCompleter.complete (dart:async/future_impl.dart:35:31)
#1      FlutterDevice.connect.<anonymous closure> (package:flutter_tools/src/resident_runner.dart:338:17)
<asynchronous suspension>

[!] Flutter (Channel stable, 3.7.12, on Microsoft Windows [Version 10.0.18362.113], locale en-IN)
    • Flutter version 3.7.12 on channel stable at C:\Users\PC\Downloads\flutter_windows_3.7.12-stable\flutter
    ! The flutter binary is not on your path. Consider adding C:\Users\PC\Downloads\flutter_windows_3.7.12-stable\flutter\bin to your path.
    ! The dart binary is not on your path. Consider adding C:\Users\PC\Downloads\flutter_windows_3.7.12-stable\flutter\bin to your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4d9e56e694 (3 months ago), 2023-04-17 21:47:46 -0400
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at C:\Users\PC\AppData\Local\Android\sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✗] Visual Studio - develop for Windows
    ✗ Visual Studio not installed; this is necessary for Windows development.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

[✓] Android Studio (version 2022.2)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-b2043.56-9586694)

[✓] VS Code (version 1.80.0)
    • VS Code at C:\Users\PC\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • SM A307FN (mobile) • RZ8MB0N9A9P • android-arm64  • Android 11 (API 30)
    • Windows (desktop)  • windows     • windows-x64    • Microsoft Windows [Version 10.0.18362.113]
    • Chrome (web)       • chrome      • web-javascript • Google Chrome 114.0.5735.199
    • Edge (web)         • edge        • web-javascript • Microsoft Edge 114.0.1823.58

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 3 categories.

Flutter Application Metadata
Type: app
Version: 1.0.4+16
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 4b12645012342076800eb701bcdfe18f87da21cf
Plugins
cloud_firestore-4.8.0
cloud_firestore_web-3.6.0
device_info_plus-9.0.1
file_selector_linux-0.9.1+3
file_selector_macos-0.9.2
file_selector_windows-0.9.2
firebase_auth-4.6.1
firebase_auth_web-5.5.1
firebase_core-2.14.0
firebase_core_web-2.6.0
firebase_crashlytics-3.3.1
firebase_dynamic_links-5.3.3
firebase_messaging-14.6.1
firebase_messaging_web-3.5.1
firebase_remote_config-4.2.1
firebase_remote_config_web-1.4.1
flutter_local_notifications-14.1.1
flutter_plugin_android_lifecycle-2.0.15
fluttertoast-8.2.1
google_mobile_ads-3.0.0
google_sign_in-6.1.0
google_sign_in_android-6.1.14
google_sign_in_ios-5.6.2
google_sign_in_web-0.12.0
image_cropper-4.0.1
image_cropper_for_web-2.0.0
image_gallery_saver-1.7.1
image_picker-0.8.9
image_picker_android-0.8.7+3
image_picker_for_web-2.2.0
image_picker_ios-0.8.8
image_picker_linux-0.2.1
image_picker_macos-0.2.1
image_picker_windows-0.2.1
in_app_purchase-3.1.5
in_app_purchase_android-0.2.5+4
in_app_purchase_storekit-0.3.6+3
in_app_review-2.0.6
in_app_update-4.0.1
package_info_plus-4.0.0
path_provider-2.0.15
path_provider_android-2.0.27
path_provider_foundation-2.2.3
path_provider_linux-2.1.10
path_provider_windows-2.1.6
permission_handler-10.2.0
permission_handler_android-10.2.1
permission_handler_apple-9.0.8
permission_handler_windows-0.1.2
share_plus-7.0.0
shared_preferences-2.1.1
shared_preferences_android-2.1.4
shared_preferences_foundation-2.2.2
shared_preferences_linux-2.2.0
shared_preferences_web-2.1.0
shared_preferences_windows-2.2.0
sign_in_with_apple-4.3.0
sign_in_with_apple_web-1.0.1
speech_to_text-6.1.1
speech_to_text_macos-1.0.2
sqflite-2.2.8+4
url_launcher-6.1.11
url_launcher_android-6.0.34
url_launcher_ios-6.1.4
url_launcher_linux-3.0.5
url_launcher_macos-3.0.5
url_launcher_web-2.0.16
url_launcher_windows-3.0.6
webview_flutter-4.2.0
webview_flutter_android-3.7.0
webview_flutter_wkwebview-3.4.3

Hi @Hirenpar. I see there's an open issue addressing the case you described. #77581
Please follow up on that issue, I'm closing the current one as a duplicate.
Thank you


Status code "Bad request" status code instead of "Not Found"

When I try to run the last test for the Foody app - "Try to Delete a Non-existing Food" the status code should be Bad request(400) and the error message should be: "Unable to delete this food revue!", but it throws Not Found(404) and the message is: "No food revues...".

When the database is empty it returns different message and different status code, the test as it is conditionally passes only if there is at least one entry in the database at that time.


Javascript not working after page transition

Hi there
I am quite new to highway.js and got stuck with reloading of JavaScript  after page transition. The only problem I am facing is that my JavaScript is not working after the transition. I tried to workout with renderers but it did  not worked out, I am sure I am missing something but what I do not know. Can someone help me how to reload JavaScript pls. I will really appreciate your help.
Regards,
Shehzad Asif

Page specific JS gets called in the renderers.
My guess is you have not correctly setup a renderer for your page.
Also don't forget to call the done() function after transitioning as this invokes the renderer.

Hi Michael
Glad someone replied to my question. It would be very kind if you could
just provide a simple example to load the in page js and how to remove out
page js. I am quite new to highway and could not figure it out through the
docs. That's why I need help.
Regards,
Shehzad Asif
On Mon, Dec 14, 2020 at 3:26 PM Michael Koelewijn<EMAIL_ADDRESS>wrote:

Page specific JS gets called in the renderers.
My guess is you have not correctly setup a renderer for your page.
Also don't forget to call the done() function after transitioning as this
invokes the renderer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Dogstudio/highway/issues/99#issuecomment-744342639,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APQYRBQ44BLBVBO6UHBYPQDSUXR3VANCNFSM4UGQYL4A
.


login is lasting only as a request and not like a session :(

https://gph.is/g/ZWoyM1D

the bug was caused bc of the logout function, so it was removed and i'll implement the function later.

:(


Plots

Adds some plotting functionality, we should discuss what else needs to be added here.

Thanks @gidden for this really nice plotting library!


[FLINK-26945][table] add DATE_SUB function.

What is the purpose of the change
add DATE_SUB function
Brief change log

SELECT DATE_SUB('2018-05-01',INTERVAL '1' YEAR/MONTH/DAY);

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: ( no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs)

after this https://github.com/apache/flink/pull/22050 fixed, the unit test will be passed.
so when it be merged, i wll rebase


Different "Board Serial Number" in the "System" and "Serial"

v3.4.2 displays different "Board Serial Number" in the "System" (which looks correct, at least it is the same as in the config) and "Serial" tabs of the "System" tab

Sorry, found that "Serial" is intended to generate )


There are some error log about fastjson

There are some error log about fastjson
haluo-error.zip
apk file :https://wap.pp.cn/app/dl/fs08/2021/08/23/5/106_6b852528162327c9f056dd40f2ce9ce7.apk

Thanks for reporting! I found the issue and fixed it accordingly.
I will reply here again as soon as the changes are online :)
The issue is in these lines:
String elementTypeA = a.substring(as);
String elementTypeB = a.substring(bs);

As one can see, elementTypeB uses the String a, which is of course not what we want.
So, I've just changed it to b and your APK is decompiling perfectly fine for me now :)

The new build is being deployed right now. v25 should be available via releases


Godot runs slower with GLES2 than GLES3

Godot version:
Recent master:
26058376aa180f70e152070b3b69272287a710a8
OS/device including version:
OS:  Ubuntu 18.04 with many things removed for performance
Hardware: Intel Atom x5-8350, 2Gb ram. Integrated GPU ("HD Graphics (Cherry Trail)")
Issue description:
Yes, I'm aware that this is a very low spec piece of hardware. I was not expecting it to run well, and actually, the fact that Godot ran at all was a pleasant surprise. The other surprise was:

When running with --video-driver GLES3 --print-fps the result is around 34 FPS
When running with --video-driver GLES2 --print-fps the result is around 18 FPS

Description of the scene:

One directional lamp with shadow
About 10-20 objects, all with "normal" spatial shaders. Two materials have a single texture.
A GUI

I'm not sure if this is an issue, or if it's just myself misunderstanding the purpose of GLES2 mode, so:
Should GLES2 have better performance than GLES3

#24466 pointed it too

No difference with 3c999ae1a1f897716041b45606a4506790da1e91 FPS is still slower on GLES2

I also have noticed a drop in FPS and a high CPU usage when using the GLES2 (not always) compared to GLES3. Godot2 was way too fast for 3D, I thought it was because Godot3's GLES2 looks better.
I also have noticed that using multithreading causes more lag even if you get 10-40 FPS.

on this 1039ba9 and before, i seen 50-55 FPS on android GLES2 devices,
after this #24445 has been fixed i noticed FPS has drop to 9-10 FPS.

Guys. Help pliz. I have on gles3 albedo strange displays. On gles2 it seems normal. This is only on the node Shader. On the usual - all is well. What might be the problem? I have linux mint.

@segamanov Please open a new issue for this. Make sure to attach a minimal reproduction project along the way.

My English is bad. Even worse I know your site)) Unfortunately, I deleted everything...11.08.2020, 19:19, "Hugo Locurcio"<EMAIL_ADDRESS>@segamanov Please open a new issue for this. Make sure to attach a minimal reproduction project along the way.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.


Use Microprofile BOM/POM

See https://github.com/eclipse/microprofile-samples/issues/35
This applied the 1.0.0 BOM

@kwsutter Was there an issue with this preventing to merge it?

@jclingan @kwsutter What exactly is blocking the use of an already published BOM?
If they no longer reflect the current developments in projects and features, those vendor-neutral samples become pretty irrelevant and every vendor does their own things. Maybe that's the idea, can't tell, but if not, it would be great if they reflect the 1.0 BOM which was published in April before a 1.1 BOM or POMs eventually come out first. http://microprofile.io/projects also points to this project, in fact it is one of the first, so people see it when they visit the site.

With MicroProfle 1.2 out now, is it possible to use the dependency as written in the main pdf on http://microprofile.io/:
<dependency> <groupId>org.eclipse.microprofile</groupId> <artifactId>microprofile</artifactId> <version>1.2</version> <type>pom</type> <scope>provided</scope> </dependency>
?

Could do, but it is extremely sad having missed a proper release cycle under https://github.com/eclipse/microprofile-samples/releases for 1.1.
Do you want to skip it and go right to 1.2 or do 1.1 properly first and then upgrade these samples?


Make behavior of protected system drives more obvious to user

This came out of a discussion on Gitter, but I wanted to materialize it here for tracking.

@alexandrosm: @WasabiFan in general I wonder if instead of not showing system drives at all, instead Etcher should just not auto-select them, de-emphasise them on the selection menu, and if the user actively selects it, it gives a warning, but ultimately goes ahead.
@alexandrosm: in other words treat the system drive heuristic as a heuristic instead of as a law as it does now

@WasabiFan: Yeah, I like that. Or maybe gray them out and then put the "unsafe mode" checkbox on the selection screen (something like "Allow selection of system drives").
This would make it much easier for users to understand why their drives aren't showing up.

In general, the idea would be to make the filtering out of "system" drives visible to the user, so that they can see what is being filtered out and why.

One more thing to highlight, I like the idea of moving things out of the
"garbage dump" settings page and into the specific screens they are
relevant on. If unsafe mode makes more sense in the drive selection, let's
move it in there.
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Mon, Nov 21, 2016 at 8:33 PM, Wasabi Fan<EMAIL_ADDRESS>wrote:

This came out of a discussion on Gitter, but I wanted to materialize it
here for tracking.
@alexandrosm https://github.com/alexandrosm: @WasabiFan
https://github.com/WasabiFan in general I wonder if instead of not
showing system drives at all, instead Etcher should just not auto-select
them, de-emphasise them on the selection menu, and if the user actively
selects it, it gives a warning, but ultimately goes ahead.
@alexandrosm https://github.com/alexandrosm: in other words treat the
system drive heuristic as a heuristic instead of as a law as it does now
@WasabiFan https://github.com/WasabiFan: Yeah, I like that. Or maybe
gray them out and then put the "unsafe mode" checkbox on the selection
screen (something like "Allow selection of system drives").
This would make it much easier for users to understand why their drives
aren't showing up.
In general, the idea would be to make the filtering out of "system" drives
visible to the user, so that they can see what is being filtered out and
why.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/issues/888, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCEIPET_NEdeG2FqNqMShOI3jjLLRks5rAnCPgaJpZM4K4_1J
.

Agreed, especially if in doing so that checkbox gets a better name! It would be great to see "settings" become something more like "preferences" (logging, telemetry, debugging, etc.).

Sounds cool. Lets put a "system drive" badge as we do for locked, or small devices, and disable them as well. Once that's done, we can move the checkbox there.

Yeah, overlaying badges on different types of drives is also something that we discussed with @taahirisaacs and @konmouz at the Summit. I think we decided that removable drives (that we don't detect as "system") should always be displayed at the top of the list.
IMHO if we're going to be displaying "System" drives to the user (with 'just' a simple tickbox to enable writing to them) then perhaps we also ought to attempt to identify "boot" drives, and never allow those to be overwritten? And we could/should also filter "source" drives, as mentioned in #830
So, there'd then be:

Removable drives - always okay to write
"System" drives - writable if the user enables "unsafe mode" (or whatever it gets renamed to)
"Boot" drives (e.g. where the current Operating System was loaded from - should we also try detecting swap / pagefile drives currently being used?) - we should prevent the user writing to here

And then any of the above drives can also be:

"Source" drives where the disk image is currently being read from - we should prevent the user writing to here
"Locked" drives (e.g. SD cards with the read-only switch enabled) - non-writable at the hardware level
"Small" drives where the capacity is less than the currently-selected image - should we allow these to be written to in "unsafe mode"?

Any other categories? :)

I would recommend avoiding attempting to detect "boot drives". I suspect that Etcher wouldn't be able to do it reliably, and if it isn't reliable I don't think that it should be used at all. For example, on one of my PCs, I had my user folder stored on one drive while the system was on another; applications were stored on the same drive as my user folder. How would this be detected? I'd bet that edge cases like that would render this sort of "protection" unreliable at best and outright dangerous at worst. I'd favor just detecting generic "system" drives and putting protections in place there.

we discussed this today with @konmouz in person, and he has some sleek
designs, i suspect he might post them here for further comment
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Mon, Nov 28, 2016 at 6:55 PM, Wasabi Fan<EMAIL_ADDRESS>wrote:

I would recommend avoiding attempting to detect "boot drives". I suspect
that Etcher wouldn't be able to do it reliably, and if it isn't reliable I
don't think that it should be used at all. For example, on one of my PCs, I
had my user folder stored on one drive while the system was on another;
applications were stored on the same drive as my user folder. How would
this be detected? I'd bet that edge cases like that would render this sort
of "protection" unreliable at best and outright dangerous at worst. I'd
favor just detecting generic "system" drives and putting protections in
place there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/issues/888#issuecomment-263359586,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCJCOZUL64_PG68z8HtrdkA8KLn27ks5rCyOqgaJpZM4K4_1J
.

Yes, I will upload soon, I just want to recap with @taahirisaacs to sync the designs.
The idea is that there will be a pill label for system drives (drive selection modal). All drives, including system ones, are always selectable without enabling 'unsafe mode' (this option will be removed). However, if the user selects a system drive, there will be some sort of alert before continuing (also color change of button). In addition, after clicking 'Flash', user will get another alert modal to re-confirm that flashing a system drive is intended. So practically, it is quite impossible to flash a system drive accidentally.
As an advance setting, we could let users deactivate the final alert to speed up the process. However, I don't think that this will be a frequent use case so probably doesn't really worth it.
Finally, the boot drives concept sounds really good. If this can be implemented reliably it would be great.

IMHO if we're going to be displaying "System" drives to the user (with 'just' a simple tickbox to enable writing to them) then perhaps we also ought to attempt to identify "boot" drives, and never allow those to be overwritten? And we could/should also filter "source" drives, as mentioned in #830

It sounds difficult to get right, but we could get almost there by detecting drives containing partitions mounted at /, /boot, /home, etc in the case of UNIX, and drives containing drive letters that match %SYSTEMDRIVE% and %HOMEPATH% in Windows.

Yeah, that's what I was thinking. And we could also scan /proc/cmdline on Linux for root=. And possibly also check for %PROGRAMFILES% on Windows?

Sounds good. @lurch Do you mind opening a new issue in drivelist to track this?

Done https://github.com/resin-io-modules/drivelist/issues/126

@taahirisaacs and I had a meeting earlier today, so we end up with the following Ui flow:
State after selecting an image:

If only one removable drive is connected, it will be automatically selected
Else, if no removable drive or more than one is connected, 'Browse Drives' CTA will be highlighted

Select drive modal:

All drives are selectable, however, system drives have a clear label (hopefully boot drives as well)

Select drive modal:

If a removable drive is selected, 'Continue' CTA will be highlighted in the usual blue color
If a system drive is selected, 'Continue' CTA will be highlighted in a red color along with an 'alert' icon and a short confirmation message
Regarding double click selection, we can implement it only on removable drives

If a system drive is selected, a small 'alert' icon is placed next to the drive name
If the drive name or the icon is clicked, a small modal appears containing all the info relevant to the drive

Flash:

If user clicks 'Flash' while a system drive is selected, a new confirmation modal appears displaying the selected drive and double-checking if flashing a system drive is an intended action
User can confirm flashing or directly change the selected drive

Looks very nice :grinning:

...and WRT #884 , it's not explicitly spelled out above, but if we're always displaying system drives, then I guess the drive-list will never be empty (since there'll always be at least one system drive), and so the "connect a drive" button will never appear.

Looks very cool! What about sorting? Should we sort the available drives so that the system one always get below?

@lurch Yes, exactly. System drives are always displayed. Currently, the only case where Etcher selects a drive automatically is when only one removable drive is connected. 'Unsafe mode' has been completely removed (and therefore advanced settings as well).
@jviotti That would make sense since selecting a removable drive should be more often

the "connect a drive" button will never appear.

This feels wrong. Isn't the idea that only removable drives are auto-selected?

I certainly thing system drives should go to the bottom, and potentially
should be grayed out and need a special checkbox/modal to be selected.
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Wed, Nov 30, 2016 at 6:04 PM, Wasabi Fan<EMAIL_ADDRESS>wrote:

the "connect a drive" button will never appear.
This feels wrong. Isn't the idea that only removable drives are
auto-selected?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/issues/888#issuecomment-263947518,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCBxfnN3k5XHPtb4SPwKUrG4zcEDQks5rDbq7gaJpZM4K4_1J
.

@konmouz 's design already requires the user to explicitly confirm twice before system drives will be written to. Not sure an extra tickbox to 'enable' system drives to be selectable is really necessary? *shrug*

@WasabiFan, indeed only removable drives are auto-selected. If only a system drive is available, user will get the 'browse drivers' CTA and has to select it manually.
@alexandrosm, I agree with @lurch. We don't need an extra checkbox to confirm. Currently are notifying user in 4 ways. Red pill label, confirmation with alert icon, alert icon on main Ui page (next to drive) and final confirmation before flashing.

fair enough.
How about having system/boot drives at the bottom of the list and somehow
de-emphasised? (grayed out?)
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Thu, Dec 1, 2016 at 9:37 AM, Konstantinos Mouzakis <
<EMAIL_ADDRESS>wrote:

@WasabiFan https://github.com/WasabiFan, indeed only removable drives
are auto-selected. If only a system drive is available, user will get the
'browse drivers' CTA and has to select it manually.
@alexandrosm https://github.com/alexandrosm, I agree with @lurch
https://github.com/lurch. We don't need an extra checkbox to confirm.
Currently are notifying user in 4 ways. Red pill label, confirmation with
alert icon, alert icon on main Ui page (next to drive) and final
confirmation before flashing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/issues/888#issuecomment-264125062,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCDsvW8vLZ_NZHEmTeXyjbIyB7UzSks5rDpU-gaJpZM4K4_1J
.

The other thing to be careful about is the relevant text. Due to the fact
that we're still not 100% on this, we shouldn't say "This is a system
drive, are you sure you want to write to it" but something closer to
"Etcher has identified this as a system drive, are you sure you want to
write to it?". It's a small difference but important to communicate the
level of certainty.
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Thu, Dec 1, 2016 at 9:50 AM, Alexandros Marinos<EMAIL_ADDRESS>wrote:

fair enough.
How about having system/boot drives at the bottom of the list and somehow
de-emphasised? (grayed out?)
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Thu, Dec 1, 2016 at 9:37 AM, Konstantinos Mouzakis <
<EMAIL_ADDRESS>wrote:

@WasabiFan https://github.com/WasabiFan, indeed only removable drives
are auto-selected. If only a system drive is available, user will get the
'browse drivers' CTA and has to select it manually.
@alexandrosm https://github.com/alexandrosm, I agree with @lurch
https://github.com/lurch. We don't need an extra checkbox to confirm.
Currently are notifying user in 4 ways. Red pill label, confirmation with
alert icon, alert icon on main Ui page (next to drive) and final
confirmation before flashing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/issues/888#issuecomment-264125062,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCDsvW8vLZ_NZHEmTeXyjbIyB7UzSks5rDpU-gaJpZM4K4_1J
.

Good point, I think we can rephrase. Regarding drives' sorting, I agree that removable disks should be on top and system/boot drives at the bottom. We can try de-emphasising them, the only concern is that they might look appear as unavailable.

As discussed earlier, I guess there'll effectively be three "levels" of drives:

Drives always writable (Removable drives)
Drives only writable to after user-confirmation (System drives)
Drives never writable (Boot drives, Too-small drives, Locked/Read-only drives, Source drives)

IMHO they should be displayed in that order, with the bottom category never selectable, and with drives within each category sorted from smallest-to-largest in terms of capacity.
And I also agree with @alexandrosm 's distinction :+1:

What about the behaviour of plugging a removable drive in while Etcher is running? Should that then become the selected drive, if there are only system drives available otherwise?

Assuming the user hasn't already specifically selected a drive, then yes. (IIRC it's what the current behaviour does)

I like how the hive mind is working here :)
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Thu, Dec 1, 2016 at 11:26 AM, Andrew Scheller<EMAIL_ADDRESS>wrote:

Assuming the user hasn't already specifically selected a drive, then yes.
(IIRC it's what the current behaviour does)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/issues/888#issuecomment-264147617,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCCX-CC2YCZiPB9hM3pI_bgLkjBIlks5rDq7YgaJpZM4K4_1J
.

Example of list of drives, sorted as discussed (+ overflow).

Changed to @alexandrosm's suggestion. I am wondering -just to reduce words- if it makes sense to completely remove the question and keep only "Etcher has identified this as a system drive.", since we do make clear that this will erase your data in the last stage modal.

We can try de-emphasising them, the only concern is that they might look appear as unavailable.

Yeah, "SYSTEM DRIVE" and "BOOT DRIVE" now look equally un-selectable, even though one is and one isn't :-/

if it makes sense to completely remove the question and keep only "Etcher has identified this as a system drive."

Yeah, that's a good point - clicking "Continue" here doesn't actually write to the drive, so it probably makes sense to only mention "are you sure you want to write to it?" when we're actually about to write to the drive. Or we could even make the text say "Warning: Etcher has identified this as a system drive." (would that still fit on a single line?)

We also provide the 'warning icon' so I think it is enough.

Actually it fits, just test it. So it is still an option.

How does the warning look if there are enough drives to force scrolling (i.e. They've got the bottom of the list control)?

I am wondering -just to reduce words- if it makes sense to completely remove the question and keep only "Etcher has identified this as a system drive.", since we do make clear that this will erase your data in the last stage modal.

I'm all for reducing the amount of modals we use!

Looks good! I think the disabled "boot drive" should be greyed out though.

So you can not select your Boot Drive in any case, is that right? In this case we should also remove the greyed out 'tick' on the right.

Yep, I believe that's right.

@konmouz -- the interaction as designed implies there will only be one
drive selected, which will change with multi-write. Any ideas for how to
alter this to not insert the single-drive assumption?
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Fri, Dec 2, 2016 at 7:00 PM, Wasabi Fan<EMAIL_ADDRESS>wrote:

Yep, I believe that's right.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/issues/888#issuecomment-264534017,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCLvWKmAKs8M9ozdcv5djOsa_qX-Lks5rEGq2gaJpZM4K4_1J
.

@konmouz Nice idea on removing the 'tick' for boot / locked drives :+1:
For multi-writes I guess we could change the text to something like "Warning: Etcher has identified some of the drives you've selected as system drives." ?

yeah, something of that type.
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Sat, Dec 3, 2016 at 2:31 AM, Andrew Scheller<EMAIL_ADDRESS>wrote:

@konmouz https://github.com/konmouz Nice idea on removing the 'tick'
for boot / locked drives 👍
For multi-writes I guess we could change the text to something like
"Warning: Etcher has identified some of the drives you've selected as
system drives." ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/issues/888#issuecomment-264609843,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCPq14BMPh_APwq9KrwBxW4O8kPo_ks5rENR5gaJpZM4K4_1J
.

@alexandrosm, regarding multi-writes, we might need to alter the modal or the whole UI. The drives space is two small for this purpose. Image selecting 10 drive, it is very difficult to have an overview of your selections.

We should seriously consider what that new modal would look like and try to
see if we can make our modifications go in that direction, as I'd hate to
have to re-do a bunch of stuff when we get there.
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Mon, Dec 5, 2016 at 9:39 AM, Konstantinos Mouzakis <
<EMAIL_ADDRESS>wrote:

@alexandrosm https://github.com/alexandrosm, regarding multi-writes, we
might need to alter the modal or the whole UI. The drives space is two
small for this purpose. Image selecting 10 drive, it is very difficult to
have an overview of your selections.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/issues/888#issuecomment-264807690,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCMIMvXcm1j3PUem0a686KXxg2TMZks5rE9vAgaJpZM4K4_1J
.

Sure, I'll prepare some sketches.

While Etcher only supports writing to one drive I wonder if it makes sense to keep the current scrollable-list UI, and when Etcher switches to supporting multiple drives perhaps we could switch to using a 2D grid-layout (instead of a 1D list) so that all the drives are visible at once, without having to scroll?

on a somewhat-related note, doesn't it feel like the green tick should be
on the left of the drive name etc?
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Mon, Dec 5, 2016 at 11:35 AM, Andrew Scheller<EMAIL_ADDRESS>wrote:

While Etcher only supports writing to one drive I wonder if it makes sense
to keep the current scrollable-list UI, and when Etcher switches to
supporting multiple drives perhaps we could switch to using a 2D
grid-layout (instead of a 1D list) so that all the drives are visible at
once, without having to scroll?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/issues/888#issuecomment-264832525,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCIbodC3vc-FMdVAtU5LOPUyMoq9vks5rE_cUgaJpZM4K4_1J
.

and maybe "continue" should be "select these 2 drives"?
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Mon, Dec 5, 2016 at 11:13 PM, Alexandros Marinos<EMAIL_ADDRESS>wrote:

on a somewhat-related note, doesn't it feel like the green tick should be
on the left of the drive name etc?
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Mon, Dec 5, 2016 at 11:35 AM, Andrew Scheller<EMAIL_ADDRESS>
wrote:

While Etcher only supports writing to one drive I wonder if it makes
sense to keep the current scrollable-list UI, and when Etcher switches to
supporting multiple drives perhaps we could switch to using a 2D
grid-layout (instead of a 1D list) so that all the drives are visible at
once, without having to scroll?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/issues/888#issuecomment-264832525,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCIbodC3vc-FMdVAtU5LOPUyMoq9vks5rE_cUgaJpZM4K4_1J
.

Something else I've been meaning to suggest / ask for ages, but keep forgetting to:
Does it "make sense" that while the drive-selection modal is open, changes made in the modal are instantly reflected in the parent Etcher window visible behind the modal (e.g. the "Flash" button changing state)? Would it be better if the parent Etcher window only updated once the "Continue" button had been clicked on? (this is similar to https://github.com/resin-io/etcher/issues/729#issuecomment-256057600 )

Agree with both @alexandrosm's and @lurch's points.

Update:

Tick on the LHS
'Select drives (amount of drives)' CTA and 'Available (or detected) drives' as modal window name
I tried to de-emphasize the system drives (I think they still look selectable, especially compared to the boot drive that has no tick available and also is greyed out)
If drive's directory is too long, we can use a tooltip

My initial feeling on this one is that the nuanced grey shades won't be clearly distinct to all users (not just normal ones, but visually impaired ones too and people with low-contrast/brightness displays). It took me a bit to figure out what was going on (although to be fair I'm so tired I lost my phone in my own hand).

I see your point. In addition, since we have a bold visual warning when selecting a system drive, I am not sure if it really worth trying to de-emphasize them.

@konmouz

Just to be clear, is the multiple drive selection a feature for the current version or for v.1?
(For v.1 I am exploring a modal window free approach)

This will come after v1. Is a "nice to have" for v1, but I doubt we'll ship with it, since there are still some technical details to sort out.

Just to be clear, is the multiple drive selection a feature for the current version or for v.1?

Current version of Etcher only supports selecting a single drive at a time. When we do have multiple drive selection, for the case where the user has only ticked one drive, would the button say "Select drive" or "Select drives (1)" ?
Hmm, that leads on to another interesting question: When Etcher supports writing to multiple drives at once, will that feature always be available (it might be confusing for newbies to accidentally select multiple drives, instead of automatically unselecting the previously-selected drive?), or would it only be available after enabling it in the settings screen?
Agreed the the labelling on the boot drive in the last image is possibly too-light of a grey.
@konmouz Only a small feature, but could you re-order the drives in that last image so that the Removable Drives are ordered smallest (8.0GB) to biggest (120.8GB) ?

Current version of Etcher only supports selecting a single drive at a time. When we do have multiple drive selection, for the case where the user has only ticked one drive, would the button say "Select drive" or "Select drives (1)" ?
"Select drives (1)" would be better, since it always implies multi-selection
Hmm, that leads on to another interesting question: When Etcher supports writing to multiple drives at once, will that feature always be available (it might be confusing for newbies to accidentally select multiple drives, instead of automatically unselecting the previously-selected drive?), or would it only be available after enabling it in the settings screen?
We can use the same functionality with Gdrive's list view.
Only a small feature, but could you re-order the drives in that last image so that the Removable Drives are ordered smallest (8.0GB) to biggest (120.8GB) ?
No problem

When Etcher supports writing to multiple drives at once, will that feature always be available, or would it only be available after enabling it in the settings screen?

We can use the same functionality with Gdrive's list view.

Not sure what you mean there (not being a Gdrive user) - could you post some screenshots? :)

Check this video:
https://www.youtube.com/watch?v=ZxAZfs4dqLs

Only a small feature, but could you re-order the drives in that last image so that the Removable Drives are ordered smallest (8.0GB) to biggest (120.8GB) ?

What is the advantage of re-ordering by size?

Ah-ha! The classic Shift-select / Ctrl-select technique (which nearly all file-managers use, not just limited to GDrive).
I'm not sure how well that would work when selecting multiple items out of a scrollable list though? Might be too easy to click-select (and therefore unselecting previously-selected drives that are scrolled out of view) instead of shift-selecting? I'd been expecting that when Etcher supports multi-drive-selection, it'd work like a traditional tickbox-list, i.e. click a drive to select it, click it again to unselect it.
Whereas at the moment (with just single-drive selection) it works like a traditional radiobox-list.
I may be barking up the wrong tree, but I think newbies would expect Etcher to work in a radiobox-list fashion (as it does now), and it's only advanced users who'll want to use multi-drive-selection, and they'll probably want it to work in a tickbox-list fashion (rather than shift-selecting), which is why I was suggesting there might need to be a settings-button to change the modes?
Sorry for rambling...

What is the advantage of re-ordering by size?

a) Always nice to have a persistent sort-mode, rather than having the drives appearing in a random order each time you start the application
b) I was thinking that a user is more likely to want to flash an image onto their 8GB SD card, than it is they'll want to flash an image to their 500GB removable harddrive? Therefore it probably makes sense to move the most-likely option (which I'm assuming is smallest drive) to the top of the list?

...and just to clarify, I'm only suggesting displaying removable-drives (smallest to largest), then system-drives (smallest to largest) and finally boot-drives (smallest to largest), and not sorting by size regardless of the 'type' of a drive ;-)

Should an external HDD count as some sort of protected drive as well? I think it's safe to assume that users generally don't want to write to a medium that is usually used for backups. I swear this was discussed during the summit but I can't find any issues pertaining to it.
Anyway I should probably have a PR up with some preliminary changes for this issue soon today.

But I guess it may be hard to tell the difference between a small external HDD, and a large SD card or large USB flash drive? (if it just appears as a generic "USB Mass Storage Device")

We could potentially make the assumption that if it's very large even an SD card or flash drive is most likely a backup medium, and treat it as protected too. The only obvious problem I see with this is when users want to write to many such cards the warning modals could get annoying, but that could be mitigated by the multi-write or auto-write functionality.

I guess you're effectively proposing an additional "large drive" category, which would work in a similar way to the design for "system drive" above, i.e. display a modal asking something like "The drive you're about to write is XX GB. Are you sure you want to continue?" before actually writing to the drive?
Always tricky to know where to draw that "large drive" boundary though... :-/

Always tricky to know where to draw that "large drive" boundary though... :-/

Yeah, I propose to stick with that the operating system says and try to have as few heuristics as possible here.

It would be nice to prevent user from accidentally flashing a backup drive, however we can't use too many labels and alerts. Users will just ignore them after a point. At the moment, we have a clear distinction of removable drives (free to flash), system drives (alert to flash) and boot drives (can't flash).

...and there's also readonly drives and too-small drives, which are (can't flash) too.

...and there's also readonly drives and too-small drives, which are (can't flash) too.

and locked SD cards

Yeah, I was including "locked SD cards" inside "readonly drives" :)
I agree it makes sense for all (can't flash) drives to be treated the same as the "boot drives" in the earlier UI/UX discussions.
(with the obvious exception that if the user chooses a smaller image, a drive that was previously too small may now be big enough)

@jviotti can we find out the percentage of users that do flash a system drive?

We don't have any directly available data for that sadly, given that we don't send data about drives (whether they are a system one or not, etc) apart from the size.
We plan to do this at some point (for drive usage analytics), but it needs to be done carefully, since it could annoy some people. I know our current analytics model kinda suck, which affects your UX decision making process, so maybe we should start prioritizing that.
In any case, flashing to a system drive usually signals that we didn't detect a drive type correctly (since flashing to a real system drive makes no sense except in incredibly particular cases), so I'm pretty sure the number is quite low.

We should also allow users to bypass any size checks and only flash the amount of data that fits the drive, like dd does, which is particularly useful for re flashing backed up images that contain a lot of unnecessary right padding.
Maybe an "ignore, proceed anyway" message somewhere?

...for reference, I am posting Etcher v02 behaviour.


Update client-go

https://github.com/openshift/ocs-operator/blob/4803a10dce0199efe39f92720d01c807ab2e5cff/go.mod#L31
The referenced client-go version is very out of date. Please update it

You're better off filing a BZ, we don't track GitHub issues.

client-gov12 is the latest release, you're probably thinking of k8s api libs which are at v20: https://github.com/openshift/ocs-operator/blob/4803a10dce0199efe39f92720d01c807ab2e5cff/go.mod#L28


New workflow to generate a new version of the library

We could also use an alternative to use the Makefile instead of keeping all scripts into the workflow.


invalid the before token after anthor user auth?

how can i do this ? tks~

Can you elaborate on what you're trying to achieve? Cheers.

Thank you very much for your concern.My problem has been solved.
My problem is:
I use dingo and OAuth 2.0 to configure my system，
After a user login will get a token1, when the user in another client login, the user will get a new token2, I hope that the previous token1 expired invalid
My solution is to update the database under the expiration of the time, if can configure the configuration of the configuration file，that will better
@jasonlewis


Issue when copying huge amount of data to a blob container

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
10.20.1
Which platform are you using? (ex: Windows, Mac, Linux)
Linux
What command did you run?
export AZCOPY_AUTO_LOGIN_TYPE=MSI
export AZCOPY_REQUEST_TRY_TIMEOUT=720
tar --use-compress-program="pigz -6 -p 12" -c -f - * | azcopy cp "https://xxx.blob.core.windows.net/container/file.tar.gz" --from-to PipeBlob --cap-mbps 3200
I don't have any azcopy job log since we're using --from-to option.
What problem was encountered?
Command runs for a 2-3 hours (due to the compression we can easily check when it's running) and gets stuck at some point, no more activity on the source machine. Nevertheless, command still runs (apparently) and I have to ctrl-c to get access back.
How can we reproduce the problem in the simplest way?
Try to compress and send 17TB of data to a blob container with the above command.
Have you found a mitigation/solution?
No mitigation/solution so far.

As the file size is huge, can you set higher block size in "azcopy copy" command and retry. "block-size-mb=500" is the cli option you can try with this. You can also enable log-info to get insight on what is happening in azcopy and share those logs.

Thanks @vibhansa-msft, adding parameter --block-size-mb seems to have solved our issue, copy operation is now in success.


Add base-url config option to run server on subpath

Addresses issue #48

@rickbergfalk Closing this for now, will reopen when it's ready for review.

Thanks @willwest! I'll get this merged and published sometime tomorrow.
I agree with supporting the cli flag --base-url to align with the matching env var. Feel free to make the change if you'd like otherwise I can take care of it after the merge.
Thanks again!

@rickbergfalk Cool, thanks! I'll make that change and do a little more testing before we merge. Since there's no automated testing (yet), and this change touches almost every part of the code, I want to confirm that this doesn't introduce any new bugs.

@willwest Perfect! I can help test as well - I'll plan on running the changes on my local SqlPad instance prior to publish.
Automated testing is something that's on my todo list for the summer. If you have any ideas, experience, or preferences on that let me know.

@willwest did some testing and discovered the user signup/signin stuff wasn't fully considering baseUrl.
I think I got it mostly working. Sadly my git skills aren't that strong. Is there a way I can amend your pull request with the changes? Or are you able to pull them in from the branch I (well the GitHub app) created?
see this commit for details:
https://github.com/rickbergfalk/sqlpad/commit/8661deb6360763c17a832237ca4006abe2a59c99

@willwest Any updates on this?
If everyone's alright with the approach, I can merge this in and apply a couple fixes post merge. If anyone has a more preferable way of managing this let me know :)

@rickbergfalk Sorry I've been absent on this. Still want to take a closer look before merging, but expect a comment / maybe some updates this week. Hopefully will have more time to work on this repo gradually over the next few weeks.

@rickbergfalk Are the changes in 8661deb6360763c17a832237ca4006abe2a59c99 the only ones needed to make this work? I'll cherrypick the commit onto this PR, and we can merge them in together. Wouldn't be good to have an unstable build in master, even if it's for a short amount of time.

@willwest I believe so. The only case I didn't test was the google OAuth authentication.

I'll be taking another look this weekend and will try to test out OAuth. Hope to merge by monday. Thanks again @willwest for diving into this one!

Finally got around to testing OAuth - see https://github.com/willwest/sqlpad/pull/1

Woo! Thanks @willwest!


Make the RaveWaver-Database persistent

Done after 1 day tinkering --> dependency as always @devnnys @bellachesney


Add missing  @CheckReturnValue

Summary
@CheckReturnValue allows to detect invalid AssertJ usage
Pull Requests
Two PR needed one for 2.x branch and one the master branch where only Java 8 assertions must be covered (the PR 2.x branch will cover the remaining assertions once merged and 2.x is merged into master).

I'm wondering if we can add the annotation in the parent class/interface only ... that would reduce the amount of work.

Maybe I miss something, but the new  methods added by the 2.x pull request do not need @CheckReturnValue. The annotations added in https://github.com/joel-costigliola/assertj-core/commit/46c04cbb546ff45548d64323bda9be1c4ca3d434 are incorrect, so I removed them in https://github.com/joel-costigliola/assertj-core/commits/2.x

Yeah I realized that when I added containsAnyOf for arrays but I haven't yet pushed the commits.
Thanks for fixing this anyway !
I'm also working on this issue, I have found a few places where @CheckReturnValue was missing.

I have found a few places where @CheckReturnValue was missing.

great :+1:


"F" and "D" were changed and the version should be bumped

The table in the preface has not received enough attention - for example the floating
point specification changed materially, including this paragraph
+Apart from transfer operations described in the previous paragraph,
+all other floating-point operations on narrower $n$-bit operations,
+\mbox{$n<$ FLEN}, check if the input operands are correctly NaN-boxed,
+i.e., all upper FLEN$-n$ bits are 1.  If so, the $n$ least-significant
+bits of the input are used as the input value, otherwise the input
+value is treated as an $n$-bit canonical NaN.

An compliant 2.0 implementation prior to this update will not pass the current tests.
Clearly that means that this is an incompatible change and we must bump the version.
I haven't combed the rest of them to see if there are others that need correction.

I think we should've actually bumped the version twice, since the NaN-boxing scheme adopted in v2.2 of the spec was also backwards incompatible (and much more obviously so).

I think we should've actually bumped the version twice, since the NaN-boxing scheme adopted in v2.2 of the spec was also backwards incompatible (and much more obviously so).

Resolved by eb7817141bbbaa94157d65ef10c33a280dba1434 -- thanks for bringing this up.


ButtonNextInterface exported instead of ButtonNextProps

pure-react-carousel version: 1.23.0
react version: 16.11
browser used: Chrome
node version: 12.11.1

Relevant code or config:
import React from 'react';
import { ButtonNextProps } from 'pure-react-carousel';
 interface ButtonNextProps {
    style?: React.CSSProperties;
  }

What you did:
I want to make a type check for style, and was unable to do it for ButtonNext.
What happened:
Property 'style' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<Component<ButtonNextProps, any, any>> & Readonly & Readonly<{ children?: ReactNode; }>'
Reproduction:
<ButtonNext
        style={buttonStyle()}
 >
    {"Some text here I guess"}
</ButtonNext>

Problem description:
I am unable to extend ButtonNextProps to add type check for style.
Suggested solution:
Export ButtonNextProps instead of ButtonNextInterface
Can you help us fix this issue by submitting a pull request?
Yes

Awesome, thanks for pointing this out! We don't use TypeScript internally, so could you go ahead and submit the PR for this to help us out? Thanks!


Align experimental feature disclaimers in docs

We currently have a few different versions of experimental disclaimers in our docs:

https://noir-lang.org/docs/dev/noir/concepts/oracles/
https://noir-lang.org/docs/dev/noir/standard_library/containers/vec/
https://noir-lang.org/docs/dev/noir/concepts/data_bus/
https://noir-lang.org/docs/dev/noir/concepts/data_types/slices/

We should update them and consistently use one.

ok will love to do it

🫡 Docusaurus's docs if it helps: https://docusaurus.io/docs/
PR welcome!

Yes, I even know how to use Docusaurus, so there won't be a problem with that.
What you want me to do is remove where their are two disclaimer modules, right?

like a reusable component that will be imported in the  doc page


Testing SELinux in enforcing mode

What this PR does / why we need it
Testing enabling selinux in enforcing mode from cluster chart: https://github.com/giantswarm/cluster/pull/170
Towards https://github.com/giantswarm/giantswarm/issues/30605

/run cluster-test-suites

/run cluster-test-suites

Standard & upgrade e2e tests are fine, the ones in the private cluster hit the "app stuck in pending-install/pending-upgrade" issue so they will probably fail, but it's not an SELinux dependent issue.
I've tested the creation of a cluster with SELinux in enforcing mode on golem successfully (simply setting global.components.selinux.mode: enforcing  in the cluster userconfig configmap).


Handle Anonymous ops

closes #235, #264
Breaking changes

made operationName nullable because anonymous operations are allowed

Fixes / Enhancements

Fixed anonymous { foo  { bar } } queries (were broken)
Added an _identifier to RawOperationData (maybe a bit redundant with the document in the toKey as well
Cleaned up unit tests some

LGTM

:tada: This PR is included in version 1.0.1-beta.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add instructions to "test with Che" in the registry contributing guide

What does this PR do?:
Update CONTRIBUTING.md with the instructions to test stacks and samples with online Che (workspaces.openshift.com).
Which issue(s) this PR fixes:
N/A
PR acceptance criteria:

[x] Contributing guide
[x] Documentation

How to test changes / Special notes to the reviewer:

/retest


df little update proposal for mac.

on this platform, capacity column is also displayed.

Also, please update the commit message to make it more explicit :)
"little update" isn't explicit enough! thanks

Just need a test to land, thanks :)

thanks!


[Feature Request] Print to PDF

+2
Related to Benjamin_Loison/firefox#9 and #11.
Prerequisites

[X] I searched for any existing report about this feature request to avoid opening a duplicate.

Is this feature request related to a problem?
Yes
Feature Request Description
I do not believe that it is not possible.

Screenshots
No response
Additional Context
No response

What difference with #11?


New page content doesn't save

When creating a new page from the admin panel and clicking save, none of the content entered gets saved. This happens in both viewing the page from the public end and editing the page in the admin panel.
v7.0.0-beta.4
To Reproduce
Steps to reproduce the behavior:

Go to Admin page
Click on Pages/links
Create a new page
Enter some content in the content section
Click save
Return to pages
Open the page that was just created
Observe nothing in the content was saved

When clicking save, the page content should be written to the website, but upon viewing the page on the public end, nothing is rendered, nor when clicking edit does any previous content show in the content editor.

I've tested this again and it seems to work now lol


Take the current PEN-WEIGHT into account when drawing points

Also, use CIRCLE instead of RECT -- that's what users will expect to see with bigger values of PEN-WEIGHT anyways.
Fixes #46.

Hey, thanks! Could it be changed so that RECT is still used for size 1? CIRCLE is generating more triangles.

I think that might not be desired for size 1 as well due to transforms, as even with size 1 it might be larger on screen after applying the view matrix.

mmmm. let's go with the circle then. once stroke caps are implemented, maybe we can make that switch between circle/rect


Revisions Page - Tabs - Values

Users will be able to see the configuration file (YAML), diff with the previous one or from a selected revision (number input)
- The users will be able to select to see only the user-defined changes by a toggle button

@chad11111
I would love to take this one.


I want to Make Good UI design for about us and also add to show stats of website on scrolling up.

Is your feature request related to a problem? Please describe.
No, it is a feature mainly :- I want to Make Good UI design for about us and also add to show stats of website on scrolling up.
Additional context

https://github.com/user-attachments/assets/57b7a2ae-39dd-4797-a3c4-54a54c323d80

Hello yatulearn Team,
My name is Ishan, and I am a 4th-year BTech student with experience in full-stack development. I would love to contribute to your project. Here is my LinkedIn profile: https://www.linkedin.com/in/ishanguptaofficial/.
Could you please assign me to this issue? Looking forward to your response.
Best regards,
Ishan


update to twitter bootstrap 2.0

Updated to Twitter Bootstrap 2.0 with responsive design.

Is there an ETA on this? If it's more than a few days, I'd be glad to make it happen.

Alright, I got the latest code and ran the packager.  You can find the theme at: https://github.com/gdagley/theme-twitter-2.0  Thanks.

@plusjade I don't mind maintaining the official twitter-2.0 JB compatible theme.  If it becomes too much for me to keep up with, then I can hand it off to you.  I am always willing to help out where I can.  Thanks.

Sounds good, I'll be sure to notify you when I get it on http://themes.jekyllbootstrap.com/


endpoint: separate code in regenerate() into separate functions

This makes the code easier to read and more maintainable.
Signed-off by: Ian Vernon<EMAIL_ADDRESS>

This change is

Coverage decreased (-0.04%) to 43.506% when pulling 1f99c918ec22eb1b29851fe9363e0d698b1d526c on pr/ianvernon/split-up-endpoint-regenerate-fn into 38e678d7555f2bc6256803471fef194ca34b66b2 on master.

test-me-please

test-me-please

test-me-please


Ignore syncing individual attributes?

Is there some way I could mark certain attributes to not sync to CloudKit? I have an "order" field for sorting items, but want each device to be able to sort on its own. Any advice would be appreciated, thanks!

Hmm, field-specific masking sounds like a whole new feature, where the conversion from managed object to CloudKit record takes into account a list of fields to ignore.
Short of that, one approach would be to define a new entity type that just contains the order and a weak reference (e.g. uuid) to the original item, and with no CloudKit sync info.  But then you'd need to detect when new items are received to then generate local sort entities for them.
I'm curious what the use case is for this?

I'm not sure how else to store the order of items on a sortable list. The user can manually rearrange items so I need to record that somehow but I want them to be able to manually sort across different devices without it syncing that order. Field masking seems like the easiest solution but maybe there's a method I'm not considering?

@dippnerd fwiw, I finally got around to maskable attributes as part of cacheable assets, see PR #28


Overriding nixpkgs and R when mach-nix used as a flake

My apologies, this may not be an issue with mach-nix but rather me using it incorrectly. I'd be happy to contribute an example configuration if this is just me using things incorrectly.
I'm configuring a development environment that uses mach-nix via flakes. My flake.nix looks like:
  inputs = {
    mach-nix.url = "mach-nix/3.4.0";
  };

  outputs = { self, nixpkgs, mach-nix }:
      let
        l = nixpkgs.lib // builtins;
        supportedSystems = [ "x86_64-linux" "x86_64-darwin" ];
        forAllSystems = f: l.genAttrs supportedSystems
          (system: f system (import nixpkgs {inherit system;}));
      in
        {
          devShell = forAllSystems (system: pkgs:
            let
              python-env = mach-nix.lib."${system}".mkPython {
                python = "python39";
                requirements = ''
numpy
scipy
...
'';
              };
            in
              pkgs.mkShell {
                buildInputs =  [
                  python-env
                ];
              });
        };
}

This version of the flake works great, but I'm having some trouble extending and overriding various attributes.

What's the correct way to make sure that my flake and the mach-nix flake both use the same version of nixpkgs? I tried adding inputs.mach-nix.inputs.nixpkgs.follows = "nixpkgs" to my flake, but then nix develop errors with

error: The pypiDataRev seems to be older than the nixpkgs which is currently used.
Because of this, mach-nix might lack dependency information for some python packages in nixpkgs.
This can degrade the quality of the generated environment or result in failing builds.
It is recommended to pass a newer pypiDataRev to mach-nix during import.
For flakes users: Update the pypi-deps-db input of mach-nix.

I tried also setting inputs.mach-nix.inputs.pypi-deps-db.inputs.nixpkgs.follows = "nixpkgs"; but the error persisted.

What's the correct way to override the version of R that's used by mach-nix when installing rpy2? I have an R environment defined in my flake that's of the form nixpkgs.rWrapper.override { packages = [ myRPackages ]; } and I'd like to pass this R to rpy2 in my mach-nix mkPython call. If this isn't possible, what would be the recommended way to get both R and a mach-nix python environment with rpy2 that shares the same set of R packages?

I have a similar confusion. Trying to follow this advice: For flakes users: Update the pypi-deps-db input of mach-nix., I run nix flake update. However I find that this updates my mach-nix dependency, but not mach-nix's dependency on pypi-deps-db, which remains pinned to whatever it was in the flake.lock file of mach-nix.

When I add inputs.pypi-deps-db.follows = "nixpkgs"; to this template
    pypi-deps-db = {
      url = "github:DavHau/pypi-deps-db";
      inputs.nixpkgs.follows = "nixpkgs";
      inputs.mach-nix.follows = "mach-nix";
      follows = "nixpkgs";
    };

then it seems to solve the “error: The pypiDataRev seems to be older than the nixpkgs which is currently used.” (But then I have other errors).

This is probably a stale issue by now, but I just came into this issue myself and it seems like the pypi-deps-db has stopped updating: https://github.com/DavHau/pypi-deps-db/issues/16. For me, pinning to a nix package version before 8th December 2022 works.


dashboard unicode

In Czech, utf8, there are wrong displayed unicode signs in dashboard. All other pages are OK.

Thank you.

It's encoding issue, please read Troubleshoot on README.md


Feature Request for Intel MKL backend

...

Closing this. We can run intel mkl via updating the alternatives and using the net lib blas backend.


rpc: add BadBlock type to debug_getbadblocks return type

This PR adds BadBlock as a new type and adds it to the return type to debug_getBadBlocks. Addresses https://github.com/alloy-rs/alloy/issues/1560

Motivation

Solution

PR Checklist

[ ] Added Tests
[ ] Added Documentation
[ ] Breaking changes

Thank you, @mattsse. Have addressed the comments.

Fixing clippy now.


key_end!='\0' should be *key_end!='\0'

This bug was highlighted in the boost review but is still there on master:
cenv.hpp:104
while(*key_end!='=' && key_end!='\0')
should be
while(*key_end!='=' && *key_end!='\0')

Fixed here: https://github.com/artyom-beilis/nowide/pull/39

Already fixed in review branch: #14

This library is in process of integration of Boost - it is work in progress. There are many changes in review branch including API breaking.


Which Image to use?

Hello All,
I'm wishing to pick up logs from k8s deployments and push them to a grafana loki instance.
I'm aware of the loki plugin.
Though, what image version would you recommend for me to use for this purpose?
E.g:
fluent/fluentd-kubernetes-daemonset:v1.13.1-debian-elasticsearch7-3.0
Thank you in advance for any help
Bear.

As there is no image which contains grafana loki plugin, you need to build your custom own image.
If you use fluentd-kubernetes-daemonset/ as a template, you can do it by yourself like this(maybe):

Add grafana-loki to templates/Gemfile.erb
Add image name to X86_IMAGES target
Execute make src DOCKERFILE=v1.13/debian-grafana VERSION=v1.13.2-debian-grafana-amd64-1.0 TAGS=v1.13.2-debian-grafana-amd64-1.0,v1.13-debian-grafana-amd64-1
Execute docker build -t fluent/fluentd:v1.13.2-debian-grafana-amd64-1.0 docker-image/v1.13/debian-grafana

hello @kenhys,
Thanks, appreciate the reply.
I have been using fluent/fluentd-kubernetes-daemonset:v1.12.4-debian-elasticsearch6-1.1 - and executing the loki plugin on startup. Seems to work fine.
Is there any concern using an ES image?
Cheers for any further info.

thanks a bunch @kenhys


Add support for “callable” message option

Inspired by #16, I decided we could add support for a callable :message option. This feature is defined in README.md.

Looks good! :+1:


typo on website - modules - backgroundSync - if/is

Can't find a way to edit the page so I'm submitting it here in case it can make its way to the right people.
https://developers.google.com/web/tools/workbox/modules
Typo: if / is
workbox.backgroundSync
Use background sync to reliably make a network request even if the user if offline.

Thanks for letting us know! I've fixed it in https://github.com/google/WebFundamentals/pull/8343


New release to fix Python 3.6+ support?

I noticed that my bpython package in Mageia 8 (Python 3 flavour) is throwing this error:
Traceback (most recent call last):
  File "/usr/bin/bpython", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3241, in <module>
    @_call_aside
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3225, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3254, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 583, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'typing' distribution was not found and is required by curtsies

I packaged curtsies 0.3.0 which is the last stable releases. Commit https://github.com/bpython/curtsies/commit/217b4f83e954837f8adc4c549c1f2f9f2bb272a7 done after 0.3.0 fixes the issue, but has yet to be included in a stable release.
As Python 2 is going to be phased out and Python 3.6+ is now mostly ubiquitous, a new release might be in order.

@thomasballinger Could you please prepare a new release?

sure thing, can look at this tonight

Curtsies 0.3.1 has been released included this fix, please let me know if there are any issues


H2 :: Fix schema name quoting

I continued trying to work with H2 and I met an error saying that table "snapshot" did not exist. So I investigate and figured out that double quotes were missing into the h2-schema.sql.
I fixed it and now it works fine.

Thanks very much!


lint error preventing commits to the repo

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
v16.1.0
Amplify CLI Version
7.6.23
What operating system are you using?
Ubuntu (WSL2)
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
When I run lint in the project after checkout the latest (without making any code change), I am getting around 18 K lint errors. This prevents me from submitting any features to the repo.
Expected behavior
The default checkout should not give any lint errors.
Reproduction steps

Checkout the repo
Run yarn setup-dev
Run yarn eslint .

GraphQL schema(s)
NA
Log output
eslint log output (last line)

67588 problems (63348 errors, 4240 warnings)
18174 errors and 64 warnings potentially fixable with the --fix option.

Additional information
No response

Hey @vinodsr :wave: thanks for raising this! I would refer to the two lint-fix command in the root package.json for linting purposes, which has recently been updated to run against only changed files.
"lint-fix": "git diff --name-only --cached --diff-filter d | grep -E '\\.(js|jsx|ts|tsx)$' | xargs eslint --fix --quiet",

This command is also ran as a pre-commit git hook:
"pre-commit": "yarn verify-commit && yarn lint-fix"

In the end, we can have ESLint enabled in our editor to catch lint errors as we write, and when we're ready to contribute and commit this command will automatically be run for us. Please let me know if that helps

Thanks for the reply Josef.
I am confused with the lint errors that are not  part of my change. I can’t
commit my change unless I fix about 80+ lint errors in two files. (Not
related to my change)
On Fri, 11 Mar 2022 at 7:18 PM, josef @.***> wrote:

Hey @vinodsr https://github.com/vinodsr 👋 thanks for raising this! I
would refer to the two lint-fix command in the root package.json for
linting purposes, which has recently been updated to run against only
changed files.
"lint-fix": "git diff --name-only --cached --diff-filter d | grep -E '\.(js|jsx|ts|tsx)$' | xargs eslint --fix --quiet",
This command is also ran as a pre-commit git hook:
"pre-commit": "yarn verify-commit && yarn lint-fix"
In the end, we can have ESLint enabled in our editor to catch lint errors
as we write, and when we're ready to contribute and commit this command
will automatically be run for us. Please let me know if that helps
—
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-cli/issues/9962#issuecomment-1065129776,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADQ6OBO7FZ66DLMED2TF7LU7NFJXANCNFSM5QOVLW2A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Vinod Surendran R
tenthsone.com
tenthsone.com/adspot (new)
tenthsone.com/junk
talk.tenthstone.com [beta]

We recently made a change that would make the linting more aggressive for any files that you would have touched. If you want to ignore the errors, you can still make changes and then patch in the changes you want to stage (git add -p).

I could finally able to push changed using the --no-verify arg.
Thanks


Error: Converting circular structure to JSON

I used the Azure Static Web Apps extension for the first time last week (v0.11.4).  I love it!  I successfully created a static website with this tool.
However, when I attempted to create another static website...the operation failed:
5:54:18 PM: Error: Converting circular structure to JSON
    --> starting at object with constructor 'AzureAccountTreeItem'
    |     property '_cachedChildren' -> object with constructor 'Array'
    |     index 0 -> object with constructor 'SubscriptionTreeItem'
    --- property 'parent' closes the circle

How can this be fixed?  It has occurred repeatedly.
Also, when I hit the "RESOURCES remote" refresh button, a pop-up appears in the bottom right corner of VSCode which says Only Static Web Apps linked to Github are supported at this time.
Here is VSCode "About" information:
Version: 1.74.3 (system setup)
Commit: 97dec172d3256f8ca4bfb2143f3f76b503ca0534
Date: 2023-01-09T16:59:02.252Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

I used the Azure Static Web Apps extension for the first time last week (v0.11.4). I love it! I successfully created a static website with this tool.

Thank you! Your feedback is appreciated.

How can this be fixed? It has occurred repeatedly.

As a workaround, try reloading VS Code and then trying again.
I've experienced this issue as well. However, I've had a hard time consistently reproducing it. Thank you for providing a detailed issue report so we can investigate.

@brentarias, after investigating this issue I can confirm that this will be fixed in an upcoming release of the Azure Resources extension. We plan on releasing by the end of February.
The bug happens when Static Web Apps isn't activated yet. So some workarounds are:

Activate the extension (run a command from the palette by pressing F1, or expand a Static Web App tree item)
Run the "Create Static Web App..." command from the palette directly. (Access the command palette by pressing F1)