Migrate squirrel-update to JS

Description of the Change
Blocked on a fix for https://github.com/atom/joanna/issues/5 (in progress)
This PR migrates squirrel-update.coffee to modern JS via Babel - unlike some of my past migration attempts, this time around I'm gonna try migrating individual files in their own PRs instead of all bundled into one to try to keep the cost of review and risk of merge conflicts low.
Possible Drawbacks
This could introduce some bugs into the updater on Windows, but I didn't run into anything from my testing.
👀 @atom/feedback

This PR's waaaay out of date and I'm probably not gonna get to giving this another shot – someone should definitely try converting this to JS though!


Correctly track thisContainer for this-property-assignments in JS nested containers

Previously thisContainer (previously called containerContainer) would update on every block, not just those that could bind this.
In addition, if the constructor symbol still can't be found, then no binding happens. This is usually OK because people don't add new properties in methods too often.
Fixes #22774

@sandersn please port to release-2.8 as well.

@mhegazy @andy-ms The break introduced in #22643 is not in 2.8, so this fix does not apply to 2.8.
To port to 2.8, I'd have to port #22643 too, and it's a complex fix to a subtle problem. (The problem is that there are too many symbols created from this-assignments, which breaks rename and find-all-refs.)

thanks for the clarification. if the break is not in 2.8 we do not need to port anything.


Error while trying to create columns tree for MSSQL

Describe the bug
After connecting to MSSQL I receive the error message "Error while trying to create columns tree for MSSQL Cannot read property 'Project' of undefined"
Source: SQLTools (Extension)
To Reproduce
Steps to reproduce the behavior:

Open a SQL File
Connect to MSSQL database
Wait for error to display

Expected behavior
I shouldn't get an error
Screenshots
https://cl.ly/371beaba6456
Desktop (please complete the following information):

SQLTools Version [e.g. v0.17.17]
VSCode Version: [e.g 1.33.1]
Dialect Used: [MSSQL]
OS: [Mac]

Additional context
This wasn't happening on a previous release.

@omiba what's the name of the table that has Project column?

@omiba Also, what's the tree prop of this result query:
SELECT
  C.TABLE_NAME AS tableName,
  C.COLUMN_NAME AS columnName,
  C.DATA_TYPE AS type,
  C.CHARACTER_MAXIMUM_LENGTH AS size,
  C.TABLE_SCHEMA as tableSchema,
  C.TABLE_CATALOG AS tableCatalog,
  DB_NAME() as dbName,
  C.COLUMN_DEFAULT as defaultValue,
  C.IS_NULLABLE as isNullable,
  TC.CONSTRAINT_TYPE as constraintType,
  CONCAT(
    C.TABLE_CATALOG,
    '/',
    C.TABLE_SCHEMA,
    '/',
    (
      CASE
        WHEN T.TABLE_TYPE = 'VIEW' THEN 'views'
        ELSE 'tables'
      END
    ),
    '/',
    C.TABLE_NAME,
    '/',
    C.COLUMN_NAME
  ) AS tree
FROM
  INFORMATION_SCHEMA.COLUMNS C
  LEFT JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE AS KCU ON (
    C.TABLE_CATALOG = KCU.TABLE_CATALOG
    AND C.TABLE_NAME = KCU.TABLE_NAME
    AND C.TABLE_SCHEMA = KCU.TABLE_SCHEMA
    AND C.TABLE_CATALOG = KCU.TABLE_CATALOG
    AND C.COLUMN_NAME = KCU.COLUMN_NAME
  )
  LEFT JOIN INFORMATION_SCHEMA.TABLE_CONSTRAINTS AS TC ON (
    TC.CONSTRAINT_NAME = KCU.CONSTRAINT_NAME
    AND TC.TABLE_SCHEMA = KCU.TABLE_SCHEMA
    AND TC.TABLE_CATALOG = KCU.TABLE_CATALOG
  )
  JOIN INFORMATION_SCHEMA.TABLES AS T ON C.TABLE_NAME = T.TABLE_NAME
  AND C.TABLE_SCHEMA = T.TABLE_SCHEMA
  AND C.TABLE_CATALOG = T.TABLE_CATALOG
WHERE
  C.TABLE_CATALOG = DB_NAME()
  AND (C.COLUMN_NAME = 'Project' OR   C.TABLE_NAME = 'Project')
ORDER BY
  C.TABLE_NAME,
  C.ORDINAL_POSITION

Below is the output of your query:
"tableName","columnName","type","size","tableSchema","tableCatalog","dbName","defaultValue","isNullable","constraintType","tree" "v_CommissionList","Project","nvarchar",222,"dbo","**DATABASE**","**DATABASE**","","YES","","**DATABASE**/dbo/views/v_CommissionList/Project" "v_EX_Search","project","nvarchar",100,"dbo","**DATABASE**","**DATABASE**","","NO","","**DATABASE**/dbo/views/v_EX_Search/project" "v_TE_Search","project","nvarchar",100,"dbo","**DATABASE**","**DATABASE**","","NO","","**DATABASE**/dbo/views/v_TE_Search/project"
There are no tables that I see named "Project" in the database that's being connected to.

@omiba I'm realeasing a new version. Will be available shortly (v0.17.18).
I've changed the tree separator for something uncommon. I believe it can fix your issue. I couldn't reproduce it here.
Let me know how it goes.

Reopening. Closed by mistake

Confirmed that the issue is not happening any longer.  Thanks!

@omiba thanks!


[CI]

Current Behavior

Desired Behavior

Implementation

Acceptance Tests

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation
Meshery documentation site and source
🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack
🧪 Meshery Test Plan Spreadsheet

Spam

closed as a spam!


Pagination ,how to et a max per page value ?

I am using son-server in test , I should use the server-side features:
const response = await axios.get('users', { params: { _page: page, _sort: sort, _limit: 5 } })


Support vertical sharding for label_join and label_replace functions

Signed-off-by: Ben Ye<EMAIL_ADDRESS>

[x] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Even if the query contains label manipulation functions like label_join and label_replace, as long as there is no conflict between sharding labels and the dynamic destinations labels specified by the function, then we should be fine to shard.
For example, for query sum by (pod, dst_label) (label_join(metric, "dst_label", ",", "src_label")), dst_label is the dynamic label and we sum by (pod, dst_label), we could just shard by pod in this case.
Note: if we could push down the label_join and label_replace function to the store level while matching series, we could also support sharding dynamic labels. This could be a follow up if we think it makes sense.
Changes
Support vertical sharding for label_join and label_replace functions
Verification
Updated unit tests

@fpetkovski Thanks, this makes sense. For our current use case, current support for these label manipulation functions should be good enough. I will merge this then.


YETUS-452.
Someone will need to test jenkins-admin.py.  I think I've covered everything with releasedocmaker and shelldocs.

Looks like releasedocmaker's ranges don't work.

Thanks! I've added a symlink for pip as we discussed above. After a run I'll commit this.


New version: michidk.vscli version 0.1.11

Pull request has been created with Komac v1.11.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-Executable-Error


error: could not build Objective-C module 'Realm'

I try to build a Mac command line tool to fill a realm database I'd like to use in a iOS app.
I followed the instructions to add the Realm framework to the Mac app.
When I build directly after I have deleted the build folder everything works. When I then change something in a file which imports the Realm module I get the following error:
error: could not build Objective-C module 'Realm'
import Realm
       ^

I'm using Swift.
Deleting the build folder works but it's far from perfect. Am I missing something?
This does not happen in my iOS project (as far as I can tell).

@dasdom sorry for the delay in getting back to you. Could you please verify that your FRAMEWORK_SEARCH_PATHS in Xcode are correct and include the path to the OS X version of Realm.framework (and that they don't include the path to the iOS framework)?

I'm having the same issue when Realm is added via cocoapods, even though I followed the steps in the documentation:

In your Podfile, add pod "Realm" to your app target and pod "Realm.Headers" to your test target (see “Testing Realm Apps”) for details.
From the command line, run pod install.
Use the .xcworkspace file generated by CocoaPods to work on your project!
Follow these additional steps if you use Swift:
Download the latest release of Realm and extract the zip.
Drag the file at Swift/RLMSupport.swift into the File Navigator of your Xcode project, checking the Copy items if needed checkbox.

This is the error I'm getting:

My Podfile:
source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
inhibit_all_warnings!
pod 'Realm', '0.89.2'

The swift support file is there:

Let me know if I can provide more information.

I was able to reproduce this issue. It happens because the generated umbrella header imports some of the underlying private headers on first install, which is not supposed to happen. It seems like this is an issue with the Realm.podspec in combination with the executed prepare_command, which only appears for integration with frameworks.
@dasdom @ldiqual: For now, you should be able to workaround the issue by just running pod install again.

@mrackwitz Ran pod install twice but it didn't fix the issue. I'll wait on https://github.com/realm/realm-cocoa/pull/1358/files to be merged.

Just curious: when will the podspec be updated on cocoapods and what's the underlying process behind the push?

@segiddins Sorry for the late reply I was busy with other stuff. I have update to 0.90.1 and checked again. The Problem remains. The Framework Search Path points to the OS X Realm framework.
I'm not using cocoapods. I installed Realm following the steps in Manual Installation.

@dasdom in an effort to not conflate the distinct issues discussed in this thread, could you provide steps to reproduce the problem you're facing? Are you saying that following the "Manual Installation" steps listed here for an iOS Objective-C app yields a compilation error "error: could not build Objective-C module 'Realm'"?

@jpsim No, sorry, I'm talking about a command line Swift OS X application which I use to populate my realm database. I followed the manual installation steps you linked in your comment (http://realm.io/docs/cocoa/0.90.2/#installation).

I'm having the same issue, this is my Podfile:
platform :ios, '8.0'
inhibit_all_warnings!
use_frameworks!
target 'MyApp' do
  pod 'Fabric'
  pod 'Crashlytics'
  pod 'Alamofire'
  pod 'AlamofireObjectMapper'
  pod 'Moya'
  pod 'Moya-ObjectMapper'
  pod 'Firebase'
  pod 'OAStackView'
  pod 'RealmSwift'
  pod 'MMDrawerController'
  pod 'UIColor_Hex_Swift'
end

/Build/Intermediates/Pods.build/Debug-iphoneos/Realm.build/module.modulemap:2:21: error: umbrella header 'Realm.h' not found
    umbrella header "Realm.h"
                    ^
/Pods/RealmSwift/RealmSwift/Aliases.swift:20:8: error: could not build Objective-C module 'Realm'
import Realm

Any ideas?

+1 @Legoless

@Legoless @pkalinowski: Sorry for my late response here. Have you tried meanwhile to update to the latest version of Realm and the latest prerelease of CocoaPods? This should fix this issue.

Hey, guys. I had some similar issues. The problem was that when CI server is a windows machine, and the build nodes are macs, in the process of server side checkout, it messed up line endings.

@rKrums: Good to keep in mind. Thanks for bringing to attention here!

@rKrums "check if you're using different OS in the process of building something " how to check?

I was getting this same error. I tried clearing derived data, cleaning, and running pod install again but no luck. I then tried updating Cocoapods itself and repeating those steps, but got the same error. I also tried pod update but it didn't help.
Finally, I tried deleting my whole 'Pods' folder, ran pod install, cleared derived data, cleaned, and then the error went away.

I have to create a new project and everything's fine.Seems some problems
with my build settings.
On Thu, May 12, 2016 at 11:25 PM, Christian Howland <
<EMAIL_ADDRESS>wrote:

I was getting this same error. I tried clearing derived data, cleaning,
and running pod install again but no luck. I then tried updating Cocoapods
itself and repeating those steps, but got the same error. I also tried pod
update but it didn't help.
Finally, I tried deleting my whole 'Pods' folder, ran pod install, cleared
derived data, cleaned, and then the error went away.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/realm/realm-cocoa/issues/1280#issuecomment-218792416

Hi,
Error adding Realm to a Swift project - "Umbrella header 'Realm.h' not found"
I algo got this error, installed realm the first time, v.0.93.2, XCode 6.3.2
I have a multitarget project (OSX/iOS) and I'm using a bridging header for both.

The same issue in my project.

It was working for me (latest version of Pods and Realm) but then I moved the part of my project that uses Realm to a separate framework (target), modified my podfile accordingly and now I get this error.

Please file a new issue, providing all of the details requested in the new issue template, rather than commenting on an issue that's been closed since January of last year.


save values in autarky & ratio

Hi,
thanks for you card. I really like it!
Is it possible to save the 'autarky' & 'ratio' values in a sensor? I want to put them in my influxdb.
Thanks!

Duplicate of #54

Hi there 👋 ,
I sadly have to inform you that this simply isn't possible for me atm. I don't know if there are endpoints available to custom cards which allow this kind of support but I doubt it tbh. Since you are the second person to ask, i will get in contect with the frontend devs and look at the available options.

Jonah

https://discord.com/channels/330944238910963714/351047592588869643/813721902635548693
Sadly not possible.


ocamlPackages_latest.ocaml: 4.07.0 -> 4.07.1

Motivation for this change
Bugfix release.
Things done

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

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

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

@GrahamcOfBorg build ocamlPackages_latest.merlin

Failure on x86_64-darwin (full log)
Attempted: ocamlPackages_latest.merlin
Partial log (click to expand)
File "src/ocaml/typer/typing/typecore.ml", line 3308, characters 10-22:
Error: The constructor Ignored_bool expects 1 argument(s),
       but is applied here to 0 argument(s)
make[2]: *** [OCamlMakefile:1079: src/ocaml/typer/typing/typecore.cmx] Error 2
make[2]: Leaving directory '/private/tmp/nix-build-merlin-3.1.0.drv-0/source'
make[1]: *** [OCamlMakefile:780: native-code] Error 2
make[1]: Leaving directory '/private/tmp/nix-build-merlin-3.1.0.drv-0/source'
make: *** [Makefile:59: ocamlmerlin-server] Error 2
builder for '/nix/store/kw7pp449666hrr40bzj4hkwpbkzsg85d-merlin-3.1.0.drv' failed with exit code 2
error: build of '/nix/store/kw7pp449666hrr40bzj4hkwpbkzsg85d-merlin-3.1.0.drv' failed

Failure on aarch64-linux (full log)
Attempted: ocamlPackages_latest.merlin
Partial log (click to expand)
File "src/ocaml/typer/typing/typecore.ml", line 3308, characters 10-22:
Error: The constructor Ignored_bool expects 1 argument(s),
       but is applied here to 0 argument(s)
make[2]: *** [OCamlMakefile:1079: src/ocaml/typer/typing/typecore.cmx] Error 2
make[2]: Leaving directory '/build/source'
make[1]: *** [OCamlMakefile:780: native-code] Error 2
make[1]: Leaving directory '/build/source'
make: *** [Makefile:59: ocamlmerlin-server] Error 2
builder for '/nix/store/llnx9mfna04z6i4s1mx7yh5p8snlqk1r-merlin-3.1.0.drv' failed with exit code 2
error: build of '/nix/store/llnx9mfna04z6i4s1mx7yh5p8snlqk1r-merlin-3.1.0.drv' failed

Failure on x86_64-linux (full log)
Attempted: ocamlPackages_latest.merlin
Partial log (click to expand)
File "src/ocaml/typer/typing/typecore.ml", line 3308, characters 10-22:
Error: The constructor Ignored_bool expects 1 argument(s),
       but is applied here to 0 argument(s)
make[2]: *** [OCamlMakefile:1079: src/ocaml/typer/typing/typecore.cmx] Error 2
make[2]: Leaving directory '/build/source'
make[1]: *** [OCamlMakefile:780: native-code] Error 2
make[1]: Leaving directory '/build/source'
make: *** [Makefile:59: ocamlmerlin-server] Error 2
builder for '/nix/store/60x759lbw61j5yqxnab38vbf5xyh9ldg-merlin-3.1.0.drv' failed with exit code 2
error: build of '/nix/store/60x759lbw61j5yqxnab38vbf5xyh9ldg-merlin-3.1.0.drv' failed

@vbgl rebuild?

What do you mean?

I thought this couldn't be merged because of failed build before merlin update.

That’s right. There are a few other things that break (e.g. camlp5) but it’s probably not blocking (and tricky to fix).


update readme to add new plugins in the list

like google search by justin walker etc ...

see PR #102

hello there! If this isn't handled, can I work on it?

Hi, I am new to open source and this issue would be a great way to start. Is this still open? Let me know, please.

Hi, I am new to open source and this issue would be a great way to start. Is this still open? Let me know, please.

@pratheekcr This repo is our old repo. Please refer to github.com/pyhoneybot/honeybot which is the new repo

@pratheekcr This repo is our old repo. Please refer to github.com/pyhoneybot/honeybot which is the new repo


The Eigenzeit command is not found

After installing with Lazy, without any additional config, I see the message "Eigenzeit is running" but the Eigenzeit command is not present. I'm also unable to find in your code where you would register the command.

Sorry dude, but this was intended to be used by anyone.


Create CONTRIBUTING.md and fill it with corresponding content

would like to contribute if theres still a issue


Add percentage support for error_if, warn_if

resolves #4723, in collaboration with @ehmartens
Description
Adds support for using percentages in the error_if and warn_if configurations.
We'd love some feedback on the following:

Whether the method is too 'hacky' and/or if there are alternate ways of going about this.
Where to add tests — we took a look but couldn't find exactly where the configs are currently tested, and additionally noted that the tests are currently moving between two frameworks

Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

I played with some code in #5214. It doesn't handle the rendering bit yet, but thought I'd get feedback on whether this is what we're thinking of.

Hey @gshank, are you able to provide any guidance on how to test your changes in #5214 in conjunction with our current branch?

I took another look at this, and we're creating the same strings in the generic_test_builder, and rendering them in 'add_rendered_test_kwargs'. Then at compilation time they are added to the context with the top-level key "_dbt_generic_test_kwargs", and the key 'model'. So I'm wondering if we can use that instead making a new function.
That rendered 'model' string is used by 'build_raw_sql' in the generic_test_builder which builds the test sql.

@gshank Really good point! This "just works" for me if I start storing _dbt_generic_test_kwargs on the test node (which seems easier than trying to pass it through the different Jinja contexts).
https://github.com/dbt-labs/dbt-core/commit/f0dc98a7802f7fc3a8c86bd98a7f069db2164faf
Granted, I'm taking a pretty simple approach here, and just overwriting the raw test_metadata.kwargs with the compiled versions. Is there a reason we shouldn't do that? Doesn't it feel... better? We're not doing anything with the raw versions, not even using it for the same_contents comparison method that powers state:modified.
version: 2
models:
  - name: my_model
    columns:
      - name: id
        tests:
          - unique:
              warn_if: "=5%"
          - not_null:
              config:
                where: 1=1
                error_if: ">5%"

At runtime (using BigQuery):
  select
      count(*) as failures,
      count(*)  != 0 as should_warn,
      count(*) / (select count(*) from (select * from `dbt-test-env`.`dbt_jcohen`.`my_model` where 1=1) dbt_subquery) * 100 >5 as should_error
...
    select
      count(*) as failures,
      count(*) / (select count(*) from `dbt-test-env`.`dbt_jcohen`.`my_model`) * 100 =5 as should_warn,
      count(*)  != 0 as should_error

I'm going to close this PR for now, since we're not actively working on it.

Hi All, I found a workaround with this by writing a generic test in dbt and then referencing it in the yml files like any other ordinary relationships test:
This one has a 1% error threshold and works for BigQuery. Feel free to change as you see fit.
{% test relationships_with_1_pct_error_threshold(model, column_name, field, to) %}

with parent as (
    select
        {{ field }} as id
    from {{ to }}
),

child as (
    select
        {{ column_name }} as id
    from {{ model }}
),

error_threshold as (
    select
        cast(count(distinct id) * .01 as int) as num
    from parent
)

select distinct id
from child
where id is not null
    and id not in (select id from parent)
    and (
        select count(distinct id)
        from child
        where id is not null
            and id not in (select id from parent)
        ) > (select num from error_threshold)

{% endtest %}


Make the Google sheet URLs in the map a prop

instead of hardcoded in the map component
fetch( "https://docs.google.com/spreadsheets/d/e/2PACX-1vQ4l7bRcBIgwsEPGM_s9zF9csIeTgE2No_4tA6MuDCBUbfmWY_e9mAfzPpCJTsIK_hUzOyJ8CmdGMsX/pub?gid=641305740&single=true&output=csv") is hard coded in the map component.
We should fetch this and pass it into the map component as a prop

I would wait on this until we have a spreadsheet from @mvictor55. That URL refers to a single tab (identified by the gid=641305740 param) of a Google Sheet (identified the the 2PACX-...GMsX path). So, if we end up with a single sheet with a tab for each chamber, we might need two URLs.
See also https://github.com/codeforboston/advocacy-maps/issues/21#issuecomment-768686875.

I would wait on this until we have a spreadsheet from @mvictor55. That URL refers to a single tab (identified by the gid=641305740 param) of a Google Sheet (identified the the 2PACX-...GMsX path). So, if we end up with a single sheet with a tab for each chamber, we might need two URLs.
See also https://github.com/codeforboston/advocacy-maps/issues/21#issuecomment-768686875.

I still got this.


[test] Be more verbose about errors in test Interpreter/SDK/libc.swift.

We're trying to track down an intermittent failure.
rdar://26960623

@swift-ci please smoke test


[main] Update actions

Cron -knative-prow-robot
/cc knative-sandbox/eventing-writers
/assign knative-sandbox/eventing-writers
Produced by: knative-sandbox/knobots/actions/update-actions
Details:

/retest-required


Make the testing output more verbose

    Non-blocking question: Can we make the output more verbose?

The CI logs contain only the output from line 33:
Checking hello_world exercise...
Checking leap exercise...
Checking reverse_string exercise...
Checking space_age exercise...

So it's not fully reassuring that the every test case does actually run. It would be nice to not just rely on the exit code.
Originally posted by @ee7 in https://github.com/exercism/vlang/pull/10#discussion_r1020584938

Might be able to use something like v test . for this?


Restler engine failed

Description
using the current latest from git main branch the engine crashes
2022-10-06 12:07:03.572: Initializing: Garbage collection every 30 seconds.
2022-10-06 12:07:03.610: Generation: 1
2022-10-06 12:08:41.424: Terminating garbage collection. Waiting for max 300 seconds.
Traceback (most recent call last):
  File "/home/joachim/src/restler-fuzzer/restler_bin/engine/engine/core/fuzzer.py", line 43, in run
    self._num_total_sequences = driver.generate_sequences(
  File "/home/joachim/src/restler-fuzzer/restler_bin/engine/engine/core/driver.py", line 711, in generate_sequences
    seq_collection = render_with_cache(seq_collection, fuzzing_pool, checkers,
  File "/home/joachim/src/restler-fuzzer/restler_bin/engine/engine/core/driver.py", line 462, in render_with_cache
    valid_renderings = render_one(prefix_seq_to_render, sequences_count, checkers, generation, global_lock, garbage_collector)
  File "/home/joachim/src/restler-fuzzer/restler_bin/engine/engine/core/driver.py", line 210, in render_one
    renderings = current_seq.render(candidate_values_pool, global_lock)
  File "/home/joachim/src/restler-fuzzer/restler_bin/engine/engine/core/sequences.py", line 557, in render
    response = request_utilities.send_request_data(rendered_data)
  File "/home/joachim/src/restler-fuzzer/restler_bin/engine/engine/core/request_utilities.py", line 316, in send_request_data
    success, response = main_sock.sendRecv(rendered_data,
  File "/home/joachim/src/restler-fuzzer/restler_bin/engine/engine/transport_layer/messaging.py", line 110, in sendRecv
    self._sendRequest(message)
  File "/home/joachim/src/restler-fuzzer/restler_bin/engine/engine/transport_layer/messaging.py", line 187, in _sendRequest
    contentlen = len(message[_get_start_of_body(message):])
  File "/home/joachim/src/restler-fuzzer/restler_bin/engine/engine/transport_layer/messaging.py", line 180, in _get_start_of_body
    return _get_end_of_header(message) + len(DELIM)
  File "/home/joachim/src/restler-fuzzer/restler_bin/engine/engine/transport_layer/messaging.py", line 177, in _get_end_of_header
    return message.index(DELIM)
ValueError: substring not found

the engine settings:
{
  "per_resource_settings": {},
  "ignore_decoding_failures": true,
  "no_ssl": false,
  "disable_cert_validation": true,
  "time_budget": 3.00,
  "max_combinations": 6000,
  "checkers": {
    "useafterfree": {
      "mode": "exhaustive"
    },
    "leakagerule": {
      "mode": "exhaustive"
    },
    "invaliddynamicobject": {
      "mode": "exhaustive"
    },
    "payloadbody": {
      "mode": "exhaustive"
    },
    "resourcehierarchy": {
      "mode": "exhaustive"
    }
  }
}

Python 3.10.6
dotnet 6.0.400
RESTler version: 9.1.0
Linux Debian
Steps to reproduce
...
thanks for any pointers
Expected results
No response
Actual results
No response
Environment details
No response

Hi @jbauernberger,
This call stack unfortunately does not have enough info to diagnose the issue - I would need the grammar for the failing request.
From recent changes, my guess is that this could be due to commit c1ace0ce97e6906835a1f04f092d904c9f69335e.  If you cannot share the grammar, could you please try removing this commit locally and seeing if this resolves the crash?
Thanks,
Marina

Hi @marina-p, thanks for getting back. Indeed I'm unfortunately unable to share the grammar :( ... trying to go back to c1ace0c didn't solve the issue sadly.

@marina-p I've found a way to reduce the openapi spec / grammar so that no relevant info is shared but still be able to generate the crash. The grammar json/py contain:
{
  "Requests": [
    {
      "id": {
        "endpoint": "/Ping",
        "method": "Post"
      },
      "method": "Post",
      "basePath": "",
      "path": [
        {
          "Constant": [
            "String",
            "Ping"
          ]
        }
      ],
      "queryParameters": [
        [
          "Schema",
          {
            "ParameterList": []
          }
        ]
      ],
      "bodyParameters": [
        [
          "Schema",
          {
            "ParameterList": [
              {
                "name": "__body__",
                "payload": {
                  "LeafNode": {
                    "name": "",
                    "payload": {
                      "Fuzzable": {
                        "primitiveType": "String",
                        "defaultValue": "fuzzstring",
                        "exampleValue": "\\\"\\\""
                      }
                    },
                    "isRequired": true,
                    "isReadOnly": false
                  }
                }
              }
            ]
          }
        ]
      ],
      "headerParameters": [
        [
          "Schema",
          {
            "ParameterList": [
              {
                "name": "Content-Type",
                "payload": {
                  "LeafNode": {
                    "name": "",
                    "payload": {
                      "Fuzzable": {
                        "primitiveType": "String",
                        "defaultValue": "fuzzstring",
                        "exampleValue": "application/json"
                      }
                    },
                    "isRequired": false,
                    "isReadOnly": false
                  }
                }
              }
            ]
          }
        ],
        [
          "DictionaryCustomPayload",
          {
            "ParameterList": [
              {
                "name": "Content-Type",
                "payload": {
                  "LeafNode": {
                    "name": "",
                    "payload": {
                      "Constant": [
                        "String",
                        "application/json"
                      ]
                    },
                    "isRequired": true,
                    "isReadOnly": false
                  }
                }
              }
            ]
          }
        ]
      ],
      "token": "Refreshable",
      "headers": [
        [
          "Accept",
          "application/json"
        ],
        [
          "Host",
          "{{fums-reporting}}"
        ]
      ],
      "httpVersion": "1.1",
      "requestMetadata": {
        "isLongRunningOperation": false
      }
    },
    {
      "id": {
        "endpoint": "/Ping",
        "method": "Get"
      },
      "method": "Get",
      "basePath": "",
      "path": [
        {
          "Constant": [
            "String",
            "Ping"
          ]
        }
      ],
      "queryParameters": [
        [
          "Schema",
          {
            "ParameterList": []
          }
        ]
      ],
      "bodyParameters": [
        [
          "Schema",
          {
            "ParameterList": []
          }
        ]
      ],
      "headerParameters": [
        [
          "Schema",
          {
            "ParameterList": [
              {
                "name": "Content-Type",
                "payload": {
                  "LeafNode": {
                    "name": "",
                    "payload": {
                      "Fuzzable": {
                        "primitiveType": "String",
                        "defaultValue": "fuzzstring",
                        "exampleValue": "application/json"
                      }
                    },
                    "isRequired": false,
                    "isReadOnly": false
                  }
                }
              }
            ]
          }
        ],
        [
          "DictionaryCustomPayload",
          {
            "ParameterList": []
          }
        ]
      ],
      "token": "Refreshable",
      "headers": [
        [
          "Accept",
          "application/json"
        ],
        [
          "Host",
          "{{fums-reporting}}"
        ]
      ],
      "httpVersion": "1.1",
      "requestMetadata": {
        "isLongRunningOperation": false
      }
    }
  ]
}

and
""" THIS IS AN AUTOMATICALLY GENERATED FILE!"""
from __future__ import print_function
import json
from engine import primitives
from engine.core import requests
from engine.errors import ResponseParsingException
from engine import dependencies
req_collection = requests.RequestCollection([])
# Endpoint: /Ping, method: Post
request = requests.Request([
    primitives.restler_static_string("POST "),
    primitives.restler_basepath(""),
    primitives.restler_static_string("/"),
    primitives.restler_static_string("Ping"),
    primitives.restler_static_string(" HTTP/1.1\r\n"),
    primitives.restler_static_string("Accept: application/json\r\n"),
    primitives.restler_static_string("Host: {{fums-reporting}}\r\n"),
    primitives.restler_static_string("Content-Type: "),
    primitives.restler_fuzzable_string("fuzzstring", quoted=False, examples=["application/json"]),
    primitives.restler_static_string("\r\n"),
    primitives.restler_static_string("Content-Type: "),
    primitives.restler_static_string("application/json"),
    primitives.restler_static_string("\r\n"),
    primitives.restler_refreshable_authentication_token("authentication_token_tag"),
    primitives.restler_static_string("\r\n"),
    primitives.restler_fuzzable_string("fuzzstring", quoted=True, examples=["""\"\""""]),
    primitives.restler_static_string("\r\n"),

],
requestId="/Ping"
)
req_collection.add_request(request)

# Endpoint: /Ping, method: Get
request = requests.Request([
    primitives.restler_static_string("GET "),
    primitives.restler_basepath(""),
    primitives.restler_static_string("/"),
    primitives.restler_static_string("Ping"),
    primitives.restler_static_string(" HTTP/1.1\r\n"),
    primitives.restler_static_string("Accept: application/json\r\n"),
    primitives.restler_static_string("Host: {{fums-reporting}}\r\n"),
    primitives.restler_static_string("Content-Type: "),
    primitives.restler_fuzzable_string("fuzzstring", quoted=False, examples=["application/json"]),
    primitives.restler_static_string("\r\n"),
    primitives.restler_refreshable_authentication_token("authentication_token_tag"),
    primitives.restler_static_string("\r\n"),

],
requestId="/Ping"
)
req_collection.add_request(request)

Hello @jbauernberger,
Thank you, the repro was very helpful.   The fix is merged.
Thanks,
Marina

thanks @marina-p - this solved it :)


Added face_recognition.pytorch

Hi! Added link to implementation of various trending FR methods such as CenterLoss, CosFace, ArcFace.

add face recognition.pytorch by grib0ed0v


Allow agent reuse for ClientSSLSecurity if forever option is set

It should be possible for SSL connections to reuse the tls session. Every request, the https agent is recreated.
This PR changes this:
If the forever flag is set in the options per request (3rd parameter) or by default when setting the security (4th parameter), it should reuse the same agent as the previous requests also using forever.
The request-Module handles everything else, like setting the keep-alive-flag to the agent and the https module will cache the tls-session to the agent. Because of this, it is important that the same agent is used.
Tests added

Coverage increased (+0.02%) to 93.536% when pulling c8492b1cae5bfc4e9d4f30b0b1a4164f9a198a95 on Mik13:forever into 6a7a49aa7abf91eee4438222dcfea023faa8bfe9 on vpulim:master.

thanks a lot @Mik13 - could you please document the feature in our README.md file too? 👍

You're welcome @herom. I've changed the test description and added a short documentation to the readme. I hope this works

Coverage increased (+0.03%) to 93.539% when pulling faf498e3dce10306ae931007137d0d29bd398b85 on Mik13:forever into 6a7a49aa7abf91eee4438222dcfea023faa8bfe9 on vpulim:master.

Awesome 💛 Thanks a ton @Mik13 😸


Remove duplicate lines

It may happen that the set of installed packages require packages that declare same installation path. This causes the same path to be output multiple times into the generated .gitignore file.
This minor non-BC change is fixing that.

Awesome, thanks alot


[TRT] (Unnamed Layer* 0) [Convolution]: at least 4 dimensions are required for input

Thanks for your great work.
I have successfully complied the project, and got the libyoloPlugin.so and excetable bin file:TensorRTYOLOV3.
Then I follow your instruction, use (TensorRT-ROOT/samples/python/yolov3_onnx) to convert the yolov3 model to  yolov3.onnx. and then use seralizeEngineFromPythonAPI.py to convert it to trt model. But I met the following error:

[TRT] (Unnamed Layer* 0) [Convolution]: at least 4 dimensions are required for input
I have checked the yolov3.cfg, and sure that the input size is (1,3,608,608).
Could you please help me to solve the problem?

I use Onnx 1.5.0
TensroRT <IP_ADDRESS>
I have convert the 416X416 version yolov3 ok!
608 has not tested, but should also ok.
The SampleYolov3.cpp now can directly parse the yolov3.onnx, serialize it and run inference.
you 608 version some parameters should be modified.


Crash with RuboCop 0.47.0

When I update RuboCop from 0.46.0 to 0.47.0 on the project https://github.com/braingourmets/crud and run bin/rake haml_lint, I get a crash:
klee@gonzales:~/src/ruby/crud$ bin/rake haml_lint
Running via Spring preloader in process 4652
haml-lint app/views/
/home/klee/.rvm/gems/ruby-2.4.0/gems/haml_lint-0.19.0/lib/haml_lint/ruby_parser.rb:2:in `require': cannot load such file -- rubocop/ast_node/builder (LoadError)
        from /home/klee/.rvm/gems/ruby-2.4.0/gems/haml_lint-0.19.0/lib/haml_lint/ruby_parser.rb:2:in `<top (required)>'
        from /home/klee/.rvm/gems/ruby-2.4.0/gems/haml_lint-0.19.0/lib/haml_lint.rb:12:in `require'
        from /home/klee/.rvm/gems/ruby-2.4.0/gems/haml_lint-0.19.0/lib/haml_lint.rb:12:in `<top (required)>'
        from /home/klee/.rvm/gems/ruby-2.4.0/gems/haml_lint-0.19.0/bin/haml-lint:3:in `require'
        from /home/klee/.rvm/gems/ruby-2.4.0/gems/haml_lint-0.19.0/bin/haml-lint:3:in `<top (required)>'
        from /home/klee/.rvm/gems/ruby-2.4.0/bin/haml-lint:22:in `load'
        from /home/klee/.rvm/gems/ruby-2.4.0/bin/haml-lint:22:in `<main>'
        from /home/klee/.rvm/gems/ruby-2.4.0/bin/ruby_executable_hooks:15:in `eval'
        from /home/klee/.rvm/gems/ruby-2.4.0/bin/ruby_executable_hooks:15:in `<main>'
rake aborted!
Command failed with status (1): [haml-lint app/views/...]
/home/klee/src/ruby/crud/Rakefile:31:in `block in <top (required)>'
/home/klee/.rvm/gems/ruby-2.4.0/gems/activesupport-5.0.1/lib/active_support/dependencies.rb:287:in `load'
/home/klee/.rvm/gems/ruby-2.4.0/gems/activesupport-5.0.1/lib/active_support/dependencies.rb:287:in `block in load'
/home/klee/.rvm/gems/ruby-2.4.0/gems/activesupport-5.0.1/lib/active_support/dependencies.rb:259:in `load_dependency'
/home/klee/.rvm/gems/ruby-2.4.0/gems/activesupport-5.0.1/lib/active_support/dependencies.rb:287:in `load'
-e:1:in `<main>'
Tasks: TOP => haml_lint
(See full trace by running task with --trace)

The crash does not occur with rubocop 0.47.0.

Hi, since today, I retrieve the same error during my CI build.
$ gem install haml_lint --no-ri --no-rdoc
Successfully installed tilt-2.0.5

HEADS UP! Haml 4.0 has many improvements, but also has changes that may break
your application:

* Support for Ruby 1.8.6 dropped
* Support for Rails 2 dropped
* Sass filter now always outputs <style> tags
* Data attributes are now hyphenated, not underscored
* html2haml utility moved to the html2haml gem
* Textile and Maruku filters moved to the haml-contrib gem

For more info see:

http://rubydoc.info/github/haml/haml/file/CHANGELOG.md

Successfully installed haml-4.0.7
Building native extensions.  This could take a while...
Successfully installed rainbow-2.2.1
Successfully installed ast-2.3.0
Successfully installed parser-<IP_ADDRESS>
Successfully installed powerpack-0.1.1
Successfully installed ruby-progressbar-1.8.1
Successfully installed unicode-display_width-1.1.3
Successfully installed rubocop-0.47.0
Successfully installed sysexits-1.2.0
Successfully installed haml_lint-0.19.0
11 gems installed
$ haml-lint app/views/
/usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- rubocop/ast_node/builder (LoadError)
	from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/bundle/gems/haml_lint-0.19.0/lib/haml_lint/ruby_parser.rb:2:in `<top (required)>'
	from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/bundle/gems/haml_lint-0.19.0/lib/haml_lint.rb:12:in `<top (required)>'
	from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/bundle/gems/haml_lint-0.19.0/bin/haml-lint:3:in `<top (required)>'
	from /usr/local/bundle/bin/haml-lint:22:in `load'
	from /usr/local/bundle/bin/haml-lint:22:in `<main>'
ERROR: Build failed: exit code 1

https://github.com/brigade/haml-lint/blob/0276a78ecd3f3f66a11f0ee205818fa5fa6e6b89/lib/haml_lint/ruby_parser.rb#L2
ast_node has been renamed to ast, see https://github.com/bbatsov/rubocop/commit/48f1637eb36575a95b2004fecd3212d848d64f59

Thanks for the report, @oliverklee, and for digging into the underlying cause, @Bjoernsen.
Fixed in 3ce86baf.

@sds Thanks! :heart:


Virtual env name won't appear in the prompt

Description
First of all, thanks SO MUCH for this project! I was looking for something exactly like this, being a Python's virtualenv enthusiast.
Small issue I found: When I activate a new pacman-venv, the name of the virtual environment will not appear in the prompt to indicate it's active.
It still seems to be working fine, since both pacman and yay binaries are the ones from the venv.
❯ which yay
/home/matmat/dev/3d-gaussian-splat/pacvenv/pacman-venv-shims/yay

❯ which pacman
/home/matmat/dev/3d-gaussian-splat/pacvenv/pacman-venv-shims/pacman

For the record, python's virtualenv show up as expected in the prompt.
❯ python3 -m virtualenv python-venv-test
❯ source python-venv-test/bin/activate

To Reproduce
Create new virtual env pacvenv: pacman-venv pacvenv
Activate it running source pacvenv/bin/pacman-venv-activate
Notice that the virtual env name does not show up in the prompt (although it's active).
Expected Behavior
No response
Version
No response
Additional context
No response

Glad you enjoy it! What shell are you using? Also, can you share the prompt you are using (the PS1 variable)? It probably is an issue to do with multiline prompts.
As a note, this project isn’t working very well right now (hence still being in 0.X). I haven’t had much time to work on it lately, but hopefully resolving #9 will improve the project significantly.

I'm using bash with startship prompt.
Looking forward to future updates, it has already been useful for organizing a dependency heavy repo :)

Hey @matorsoni, any updates to my previous comment?

Oh hey sorry for the late reply. Just tested it and works like a charm!
~/dev/3d-gaussian-splat
❯ source pacvenv/bin/pacman-venv-activate

~/dev/3d-gaussian-splat [pacvenv]
❯


Export interfaces used by useSWRInfinite

Rationale: Extending these interfaces in a TypeScript project when composing your own hooks using SWR.
You can already do this with config/response interfaces used by useSWR as these are already exposed.

@shuding No problem! Love the library and am glad to contribute 😄
Would you prefer the interfaces to be renamed internally as well, or just renamed while being exported?

Thanks for this PR! It would be great to rename them to SWRInfiniteConfigInterface and SWRInfiniteResponseInterface, so it's more clear to the users.

for other types in types.ts, do we need to have the prefix SWR as well? what do you think?

Would you prefer the interfaces to be renamed internally as well, or just renamed while being exported?

Let's rename them internally as well, no harm in being consistent.

for other types in types.ts, do we need to have the prefix SWR as well?

Not in this PR, at least, since this would be a breaking change for anyone relying on those types. If you'd like, feel free to open a PR with these changes and we can discuss there.

Sounds good to me 👍


Add pyproject.toml for Custom Node Registry

Hey! My name is HaoHao and I'm from comfy-org! We would love to have you join the Comfy Registry, a public collection of custom nodes which lets authors publish nodes by version and automate testing against existing workflows.
Eventually, the registry will be integrated as a backend for the UI-manager where all nodes will go through a security scan. Nodes that pass these checks will have a verification flag (✅) beside their name on the UI-manager. Feel free to read up more on the registry here
Action Required:

[ ] Go to the registry. Login and create a publisher id (everything after the @ sign on your registry profile).
[ ] Add the publisher id into the pyproject.toml file.
[ ] Merge the separate Github Actions PR, then merge this PR.

If you want to publish the node manually, install the cli by running pip install comfy-cli, then run comfy node publish
Otherwise, if you have any questions, please message me on discord at haohao_81202 or join our server!

Hi @haohaocreates. I'm working with Kijai and another person to integrate these changes into their main node. So the idea is that the KJ node would support CUDA and MPS and my node would cease to be.
I'm happy to put my node in the registry, but I feel like it's probably better to avoid clutter in the registry. Judging by the current rate of progress I assume it would be at most a couple of weeks before Kijai's node has everything that mine has, and it might even just be a couple of days since they've already put work into it.

@Grant-CP, wondering if there's any way we can support you on this PR!


Ctrl-c in matlab command line kills both matlab and nix-shell

Dear Jorsn:
I am very happy using matlab with this. There's only one problem that bothers me.

The effect is in the following gif:
https://imgur.com/O40JHCL
Is there any way to solve this?
Thank you!

LOL, I kind of solve it in an ad hoc way:
kill -INT $(xprop | grep PID | cut -d ' ' -f3 | xargs -I {} pstree -p "{}" | grep -i "nodesktop" | cut -d ' ' -f 9)

basically directly send SIGINT to matlab based on process ID, and get that process ID by xprop clicking.


Improve chat readability

Make the chat easier to read. Using the Python client, a few easy suggestions that would already help a lot:
-make the names/clan/flag right aligned
-add ":" after the name, before the message
Example to show that it does make it easier to visually match names with messages:
Python:

Java:

Feedback/suggestions:

Remove the flags: they are redundant (this info can be seen elsewhere and it only needs to be checked rarely, not important enough to be shown next to each message) and call for too much attention (taking away from the actual content)
Adjust username font-weight (remove bold): username is calling too much attention to itself distracting from what's important (the actual message), also avatars can already be used to visually identify users which furthermore diminishes importance of the username in visual hierarchy
Cut off usernames that are too long so that message content always lines up

I think the username is much easier to tell apart from the message in Java client than in python client (thanks to being bold, space between clan and name, no colon, message position is aligned more often). I don't agree that it takes too much attention, i think that is a matter of being used to it or not.
I think Java client looks kinda bad because the distance between name and message is quite big sometimes, so it creates a visual disconnect.
An alternative suggestion:
Give every second message a slightly different grey background (css: even/odd) so that you end up with rows that are easy to see. The python client kind prevented the visual disconnect with the coloring of the text and by putting name and message close together (which is imo the only reason it needs the ugly colon in the first place).
In general:
Whenever there is a discussion about visual style, a bunch of people tend to show up that claim that the python client looks better in every little detail and want to bring that exact style to the Java client. People like what they are used to (which is why there is always complaints when any software in the world changes its style here and there).
So please keep in mind that a lot of people use the Java client and are used to how it looks right now. Any style changes should really have a good argument why the readability is improved (and "i just think it looks better" is not a valid argument).
And taking a look at how other software solves this problem before changing style (and thinking if we can use that for us) is always a good idea as well.

bold vs normal plus colon is debatable and probably down to what you are used to seeing. But right aligned user name is important to not have these big gaps with short user names. Avatar (and flag if you want to keep it) should probably stay left aligned to create a clean visual border to the left of the client.
Different background for rows could be nice but I don't consider it as an alternative.
Also it would be really nice if the timestamp only shows when the time incremented.
Also thumbs up from me for username cutoff


Is it possible to render html from the raw content?

I want to know that if it's possible to save the raw content into the database and then get it to render as html.

@yiyangli0118
I know it's a few years late.... but!
I urge you to check out my comment on another issue here.
https://github.com/efloti/draft-js-mathjax-plugin/issues/11#issuecomment-586968622
hopefully it could help :)


CI not implemented

Delivery automation is important. We need to create a CI pipeline which will execute tests before merging a branch into master.

This issue was practically solved by PR #3 .


Fully Leave the tarmac in autonomous

Description
Need to fully leave the tarmac in autonomous or we get 0 points
Steps to Reproduce

Go into auto
See that we don't leave tarmac

Expected behavior: [What you expected to happen]
Leave tarmac
Actual behavior: [What actually happened]
Didn't leave it
Required Information

What tag/branch/release of Robot code are you using?
0.1.2

Dupe of #116


Correction under testing in Azure

Under the following section - please note that there a missing part in the URL - see below:
Test your function in Azure
the format: http://.azurewebsites.net/orchestrators/HelloOrchestrator should be changed to: http://.azurewebsites.net/api/orchestrators/HelloOrchestrator

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

ID: 53a281e3-ce27-a305-40bb-1299e854547b
Version Independent ID: 7f54fe69-fd8c-8f5e-fa7d-2fa5681c290b
Content: Create your first durable function in Azure using Python
Content Source: articles/azure-functions/durable/quickstart-python-vscode.md
Service: azure-functions
GitHub Login: @anthonychu
Microsoft Alias: glenga

Hello @mohsin-ac,
Thank you for your feedback! We will review and update as appropriate.

Hello @mohsin-ac, Thank you for the feedback. I have made a PR to rectify the url, and is currently pending Doc author's approval. We will now proceed to close this issue out. Please tag me in your response if there are any additional concerns. Thank you!


Inconsistency regarding multiple authorization modules

This is a Bug Report

Problem:
I found inconsistent information regarding how a multiplicity of authorization modules is handled.  https://kubernetes.io/docs/reference/access-authn-authz/authorization/#determine-whether-a-request-is-allowed-or-denied says the first one to make a decision wins.  https://kubernetes.io/docs/reference/access-authn-authz/controlling-access/#authorization says the request is allowed if any authorization module allows it.
Proposed Solution:
Consistently document the truth.
Page to Update:
https://kubernetes.io/docs/reference/access-authn-authz/controlling-access/
https://kubernetes.io/docs/reference/access-authn-authz/authorization/

1.17

says the first one to make a decision wins

Which line told this? I don't see this meaning in that page.
/language en
/triage support

@Colstuwjx : "When multiple authorization modules are configured, each is checked in sequence. If any authorizer approves or denies a request, that decision is immediately returned and no other authorizer is consulted."

Looking at the code, it appears to me that the truth of the matter is as follows.  Each Authorizer has an Authorize method that inspects a request's Attributes and returns a Decision --- which can be DecisionDeny, DecisionAllow, or DecisionNoOpinion.  If all the configured Authorizers return DecisionNoOpinion then the request is rejected.  Most Authorizers eschew DecisionDeny, choosing between only DecisionAllow and DecisionNoOpinion.  The lone exception is the one for webhooks; it relays whatever the remote server decided.

Here is another related doc bug: https://kubernetes.io/docs/reference/access-authn-authz/rbac/#parallel-authorizers says that RBAC decides to deny in some cases.  But that is not true.  RBAC only returns DecisionAllow or DecisionNoOpinion.

When multiple authorization modules are configured, each is checked in sequence. If any authorizer approves or denies a request, that decision is immediately returned and no other authorizer is consulted. If all modules have no opinion on the request, then the request is denied. A deny returns an HTTP status code 403.

If more than one authorization modules are configured, Kubernetes checks each module, and if any module authorizes the request, then the request can proceed. If all of the modules deny the request, then the request is denied (HTTP status code 403).

I think these two expresses the same meaning, for multiple authorization modules, it checks each module, and if one of them denied or approved, it would immediately returned, otherwise, if all modules no opinion, it also return 403. I don't think there is an inconsistency.

There is an inconsistency because an authorization module returns one of three decisions: DecisionAllow, DecisionDeny, or DecisionNoOpinion.  With that in mind, those two passages describe different behavior.
In other news, nowhere does it clearly say that an authorization module makes one of three decisions.

Also, the text in https://kubernetes.io/docs/reference/access-authn-authz/controlling-access/#authorization is a bit awkward and outdated.  The second paragraph says

The request is authorized if an existing policy declares that the user has permissions to complete the requested action.

At this point the reader has not been told that there are policies.  Even more to the point, "policy" is redolent of ABAC --- which is no longer the only option.  This introductory text continues with ABAC specific content, and does not even identify it as such.  Only in the last paragraph is it mentioned that there are other options besides ABAC.

Also: https://kubernetes.io/docs/reference/access-authn-authz/authorization/#authorization-modules lists some of the available "modes" but not all of them.

/kind bug
/remove-triage support

/sig auth

/triage accepted
/remove-lifecycle stale

/remove-lifecycle rotten

/kind documentation

/remove-lifecycle rotten


Introduce Sublime Text plugin LSP-promql

It's already been in the official package control channel. 🎉

Thanks for this PR! Great to see more editors offering PromQL support.

Thanks!


Android app not building when upgrading from 1.1.0 to 4.0.6 [🐛]

Description
Explain the bug in as much detail as possible
I am trying to upgrade the library from 1.1.0 to 4.0.6. My react native version is 0.63.3. When i am trying to do npm run android. I am getting this error. But the app is running normally on ios.
I have checked my enviroment setup, tried cleaning gradle, cleaning cache.
> Task :app:compileDebugJavaWithJavac FAILED
406 actionable tasks: 2 executed, 404 up-to-date
C:\Users\Ralph\Desktop\workspace\mentorcliq-mobile\android\app\src\main\java\com\mentorcliq\Linking\LinkingModule.java:23: error: cannot find symbol
import com.imagepicker.FileProvider;
                      ^
  symbol:   class FileProvider
  location: package com.imagepicker
C:\Users\Ralph\Desktop\workspace\mentorcliq-mobile\android\app\src\main\java\com\mentorcliq\Linking\LinkingModule.java:93: error: cannot find symbol
            Uri fileUri = FileProvider.getUriForFile(getReactApplicationContext(),
                          ^
  symbol:   variable FileProvider
  location: class LinkingModule
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
2 errors

* What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

How to repeat issue and example

have your react native version 0.63.3
have your react-native-image-picker version 4.0.76 (upgrading from 1.1.0)
run npm run android

Solution
What needs to be done to address this issue?
Additional Information

Image Picker version: [4.0.6]
React Native version: [0.63.3]
Platform: [Android]
Development Operating System: [Windows]
Dev tools: [Android SDK version target 29. minimum: 21] navigation crash for Android

I'm having the same issue, were you able to fix it?

Same Issue here, Any solution please? @ralphhovsepian

same here


Add example to click-tracking

forgot the example
Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @jacobmovingfwd,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Add support for VK_NV_linear_color_attachment

Description
Adds support for VK_NV_linear_color_attachment, which functionally is a noop for RenderDoc because it already supports the full Vulkan color attachment functionality, of which VK_NV_linear_color_attachment is a subset.

These changes look good to me as adding pure support, though can you squash the formatting commit into the original changes?

Done.

I'm also wondering though what testing you've done with this.

I've spot-tested this change with a simple test app to determine that a) the extension is allow-listed and my test application that requires it works b) a framebuffer with linear images can be created and used. I've tried several of the RenderDoc features like the Texture View and Resource Inspector and they all work. I see no evidence of RenderDoc internally swapping the image tiling between linear and optimal.

OK thanks - could you try expanding your test app to do MRT with multiple colour attachments and then run the pixel history on one of them? I'm worried that will break due to substituting only one of the image views in the framebuffer.

That is something that at least the pixel history does, to find the full-float-precision output from shaders. Does that work with this extension unmodified?

I did not test pixel history, and now I see that's your right, this does have a problem. I'm going to put this change on hold (draft) until I can figure out how best to move forward.

Closing this PR as I'm not able to put more time into this in the foreseeable future.


Checks for undefined process correctly

;)

+1 :thumbsup:

I somehow didn't see this one and popped a fix in myself. But thanks!


cartocss should have precedence over tile_style when layer model is created

Not entirely sure how it should be handled internally, but in the layers data set in the editor the layer has both tile_style and cartocss, but inspecting the model it only has cartocss set with the value of tile_style, so I guess there is some internal parsing of the data that causes it to not have the expected value.

Here's some testing I did:
> var layer = vis.map.createCartoDBLayer({
  sql: 'something',
  cartocss: 'cartocss',
  tile_style: 'tile_style'
}, {
  silent: true
})
> console.log(layer.get('cartocss'), layer.get('tile_style')
=> cartocss tile_style

This seems to work fine...
@viddo can you provide some code to reproduce what you're describing? Thx

Found the culprit, it's actually the data on the vizJSON that's not correct (overriding the cartocss with the tile_style value instead)… so closing this one, sorry for the inconvenience

:+1:


Add stable chart repo link to README

Is this a request for help?:

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Version of Helm and Kubernetes:
Which chart:
What happened:
How do I enable the Incubator repository?
To add the Incubator charts for your local client, run helm repo add:
$ helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com/
"incubator" has been added to your repositories

You can then run helm search incubator to see the charts.
We should have a section telling customer how to add the stable repo.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

/assign @gyliu513

The stable repo is added automatically. You just do helm init and are good to go.

Except when it doesn't? Helm 3.
$ helm init
...prints just help...
$ helm repo update
Error: no repositories found. You must add one before updating

helm init ought to be enough for anybody 🙄

Helm init was removed. I feel like @Ciantic has a point with helm repo add stable https://kubernetes-charts.storage.googleapis.com

helm init was removed wasn't it? I feel like @Ciantic has a point with helm repo add stable https://kubernetes-charts.storage.googleapis.com

solves Error: no repositories found. You must add one before updating after fresh helm 3 install on helm repo update


TypeError: Cannot read properties of undefined (reading 'startsWith')

Getting this error trying to use this library in my toy project:
TypeError: Cannot read properties of undefined (reading 'startsWith')
    at getCallerDirname (/Users/chad/src/tally/node_modules/.pnpm/import-sync@2.2.2/node_modules/import-sync/dist/cjs/files.js:27:50)
    at Module.importSync (/Users/chad/src/tally/node_modules/.pnpm/import-sync@2.2.2/node_modules/import-sync/dist/cjs/import.js:41:108)
    at loadConfigFromFile (/Users/chad/src/tally/packages/typedconfig/src/load.ts:66:41)
    at loadAllConfigFiles (/Users/chad/src/tally/packages/typedconfig/src/load.ts:19:8)
    at Module.loadConfig (/Users/chad/src/tally/packages/typedconfig/src/load.ts:12:16)
    at eval (/Users/chad/src/tally/apps/web/app/config.ts:12:43)
    at async instantiateModule (file:///Users/chad/src/tally/node_modules/.pnpm/vite@5.4.7_@types+node@22.5.5/node_modules/vite/dist/node/chunks/dep-DG6Lorbi.js:52914:5)

Under debug, it looks like stack[1].getFileName(); is returning undefined but stack[1].getEvalOrigin() returns /Users/chad/src/tally/packages/typedconfig/src/load.ts (this is probably what we want here?)
I don't know why getFileName() is returning undefined. I'm using remix so maybe it has something to do with it being bundled?

Hi @chadxz,
Which package are you trying to import specifically?
Or is it any package in general under your current environment/setup?
As an aside, I would also suggest looking into

https://nodejs.org/api/modules.html#loading-ecmascript-modules-using-require
if you are on the latest node version.

I'm trying to import a file in my project, i.e. https://github.com/chadxz/tally/blob/add805d165f26a1a2932587ee31cd869b75b9241/packages/typedconfig/src/load.ts#L41 would import https://github.com/chadxz/tally/blob/main/apps/web/config/default.ts
I can try using the built in support again. I'm using remix for the first time so there's a bunch of moving parts there I'm unfamiliar with. I think I will have to pass the experimental flag in a NODE_OPTIONS env var to remix-serve and vite.
Anyway, I understand this package will soon be unneeded so it's unlikely to get changes. I'll see what I can do. Thx

Something you could try is removing the extension from the path and see if it would be picked up, e.g.
function loadConfigFromFile(path: string): NestedConfig {
  try {
    return importSync(path.replace(/\.[^/.]+$/, ""));
  } catch (e) {
    return {};
  }
}

Is it possible to use a serialised format like JSON for the config?
Then you can do [fs.readFileSync](https://nodejs.org/api/fs.html#fsreadfilesyncpath-options) to load the config, for example, and use something like zod for validation/parsing.

Was trying to give develop-time syntax highlighting and code completion for the config, so JSON wouldn't work unless I generated some sort of JSON Schema from the Zod definition. I don't think I want that sort of build step in the mix.


Add Azure AI Document Intelligence loader

Looking at this, I think we need to make loaders configurable in flowsettings.py, what do you think ?

Looking at this, I think we need to make loaders configurable in flowsettings.py, what do you think ?

@lone17 I did thought about this. However, it would means that kotaemon-related component will depend on flowsettings.py, which is meant for ktem. So I think it would be more reasonable to not assume flowsettings.py in kotaemon. And let the pipeline creator for ktem to decide the loader configurations for their pipeline in flowsettings.py

Looking at this, I think we need to make loaders configurable in flowsettings.py, what do you think ?

@lone17 I did think about this. However, it would means that kotaemon-related component will depend on flowsettings.py, which is meant for ktem. So I think it would be more reasonable to not assume flowsettings.py in kotaemon. And let the pipeline creator for ktem to decide the loader configurations for their pipeline in flowsettings.py

Looking at this, I think we need to make loaders configurable in flowsettings.py, what do you think ?

@lone17 I did think about this. However, it would means that kotaemon-related component will depend on flowsettings.py, which is meant for ktem. So I think it would be more reasonable to not assume flowsettings.py in kotaemon. And let the pipeline creator for ktem to decide the loader configurations for their pipeline in flowsettings.py

@trducng why would kotaemon's components depend on flowsettings.py ? kotaemon defines the reader class and logic, then flowsettings.py will be used to configure which readers are available just like LLMs, Embedding models, etc.

@lone17 Then what you mention is the same as this one.

So I think it would be more reasonable to not assume flowsettings.py in kotaemon. And let the pipeline creator for ktem to decide the loader configurations for their pipeline in flowsettings.py

And that will depend on the settings of ktem and pipeline creator, which doesn't really relate to this PR

yes not related to this one, just a comment, hence I didn't make a review.


Ditto malformed "e" tags

client initiating action
Ditto (or whatever client Alex Gleason uses nostr with)
what happens
Ditto adds "e" tags markers (root,reply) at index 2 instead of 3 where relay url should be.
suggestion
add an empty string to tag array if no relay url is found.
example: note1k3tu38rz8gkfjgddm9hm4jcluu9xt9l2nmcp4agkmns3mvnneklqy38pqp

@alexgleason

Whoops! Thank you for the heads up, I will fix this. cc @patrickreiis

Fixed by https://gitlab.com/soapbox-pub/ditto/-/merge_requests/413
Here is a new event to demonstrate it working: https://njump.me/nevent1qqswd0t3d2nnfx759wrra3y40ava22nx5aquqhhh6k7mc2swzr6q2vszyqzxrl97e3xrxazrnyeddw83zf5uekmue9e667js4cmzmvf4536d6m576vz
I also took the opportunity to add relay hints throughout.
Thank you very much for discovering and reporting this @eskema !


Man page generation

We need to decide what documentation system to use.  I assume we want support for man pages, which means we can either roll our own generator (like in ripgrep, which, last I checked, first generates an AsciiDoc file in build.rs) or use something like Sphinx, which is used in uutils/coreutils.

clap is working on generating man page: https://github.com/clap-rs/clap_generate/pull/1
But it just started, hopefully will be usable in months. Let's check it later.

We (CLI-WG) released v0.1.0 of the man crate today. Perhaps it fits your needs? https://github.com/rust-clique/man
If it doesn't we'd love to hear from you!

Thank you. My concern is that there are tens of cli tools in our project, maintaining their man pages and args parser are painful. Do you think it's worth waiting for clap 3? Is there any estimated time for this feature in clap 3?

Do you think it's worth waiting for clap 3? Is there any estimated time for this feature in clap 3?

I don't have an exact timeline, but I believe Clap 3 is being targeted for this fall/winter - with an alpha probably coming out before that.

IMO we should just wait until Clap 3 unless we want to write some sort of system that generates the Clap stuff and the man page stuff at the same time (so basically wrap both Clap and man).  It looks to me like man is probably more suited for libraries that generate man pages as part of whatever they do (like Clap) rather than use by the end user directly.


Support for shadow sync

Currently, this code sets the core shadow sync to false. There does not appear to be any way to specify other options. Perhaps this could be a command line argument? Or the provisioner could read in some sort of configuration file.

I know this can be done for Greengrass devices, but I think you're right about this. Are you planning on storing state in the group's main shadow?

I'm interested in setting the shadow of the Greengrass Core, not necessarily connected devices. I was planning on using the core shadow for some of the docker work I'm doing. I don't really need a shadow of the group, just the Core's shadow.

Oops, didn't mean to close this. Let me know if the new default works for you. Then I'll close this.

I actually implemented this in another commit. I'm running integration tests now.

Works great with the docker code I was working on. Thanks!


WIP: Added converters from ParentElement

Source: https://github.com/ianmacgillivray/Json-NET-for-Unity/tree/master/Source/Newtonsoft.Json/Converters

Closed in favor of #8 due to switched source branch


Test on python 3.12

Enforce cffi>=1.17 (updated for python 3.12, avoid weird errors for dependencies relying on C code)
Update time limits to avoid errors with ubuntu + python 12: It seems ortools gets slower in its latest release 9.11 on ubuntu...
Fix LP_MRCPSP_GUROBI for python 3.12: we have a crash when using gurobi.Model.addConstrs with a quicksum on a list rather than on a generator. In other words, we need to get rid of []. See https://support.gurobi.com/hc/en-us/community/posts/28192464443281-model-addConstrs-breaking-sometimes-after-Python-version-change for more details.
Add a test dedicated to LP_MRCPSP_GUROBI.

Interesting, in the link you provide they suggest that they no longer advise to use addConstrs, it seems they prefer something more manual it's fine to me, maybe we'll do that in the future


[ci] Backport Ubuntu-image update

Issue and/or context: #1335
Changes: See PR diff
Notes for Reviewer:
Following on @eddelbuettel 's comments on #1506 -- in my tiptoe into backport-bot for TileDB-SOMA, I thought to imitate core as closely as possible (since known-good), then tweak versions after. However we found that ubuntu-18.04 actually resulted in launch failures so let's try ubuntu-20.04.

Codecov Report
Patch coverage has no change and project coverage change: -11.37 :warning:

Comparison is base (57b5e5e) 64.54% compared to head (584dbca) 53.17%.

:exclamation: Current head 584dbca differs from pull request most recent head 8d24d3c. Consider uploading reports for the commit 8d24d3c to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1510       +/-   ##
===========================================
- Coverage   64.54%   53.17%   -11.37%
===========================================
  Files         102       72       -30
  Lines        8348     5837     -2511
===========================================
- Hits         5388     3104     -2284
+ Misses       2960     2733      -227

Flag
Coverage Δ

python
?

r
53.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 30 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Testing now with this very PR, and branch release-1.2


improper cropping

cropping different portion from selected cropping are of image.
if i set cropView to some portion, it will crop different portion of image.

resolved.


python solution

Solved issue #308
In Language- Python

[x] Updated README Link
[x] Added code with comments

Will you please resolve conflicts of your previous pull requests so that they can be merged.

Please add proper comments.

Please check


[🐛 Bug]: vercel not found during next-on-pages 1.5.1 build

next-on-pages environment related information
error Command "vercel" not found.
Description
When running a build, there is an error saying that vercel is not found.
Reproduction
This has occurred through multiple builds executed via GitHub Actions. No changes to config have occurred, issue only started happening today.
Pages Deployment Method
Pages CI (GitHub/GitLab integration)
Pages Deployment ID
11ab859
Additional Information
package version
node version: v18.17.1
yran version: 1.22.17
10:17:12.318 | ⚡ @cloudflare/next-on-pages CLI v.1.5.1
-- | --
10:17:12.899 | ⚡ Detected Package Manager: yarn (classic)
10:17:12.899 | ⚡ Preparing project...
10:17:12.902 | ⚡ Project is ready
10:17:13.585 | ⚡ Building project...
10:17:13.893 | ▲  yarn run v1.22.17
10:17:13.946 | ▲  error Command "vercel" not found.
10:17:13.946 | ▲  info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
10:17:13.963 |
10:17:13.963 | ⚡ The Vercel build (`yarn vercel build`) command failed. For more details see the Vercel logs above.
10:17:13.963 | ⚡ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.
10:17:13.964 |
10:17:14.013 | Failed: Error while executing user command. Exited with error code: 1
10:17:14.024 | Failed: build command exited with code: 1
10:17:15.014 | Failed: error occurred while running build command

Would you like to help?

[x] Would you like to help fixing this bug?

Happening on Node v18.16.0, yarn v1.22.17. Started suddenly, no new packages added. Just pushed a regular commit.

Hi @zionfuo, thank you for the issue :slightly_smiling_face:
The bug should have already been fixed by 1.6.0 could you please try to give that version a go and let me know how it goes? :pray:
(@operfildoluiz same for you, please give 1.6.0 a try :slightly_smiling_face:)

@dario-piotrowicz updating to 1.6.0 alone didn't fix it. Had to add vercel as a dev dependency, then it started working again :)

@operfildoluiz are you completely sure you were using 1.6.0? did you double check the version in the command logs? :sweat:

Hi @zionfuo, thank you for the issue 🙂
The bug should have already been fixed by 1.6.0 could you please try to give that version a go and let me know how it goes? 🙏
(@operfildoluiz same for you, please give 1.6.0 a try 🙂)

@dario-piotrowicz The current version is already 1.6, but it seems that the build failure is due to the JavaScript exceeding 500KB.
Build log
2023-08-29T00:22:06.515351Z	Cloning repository...
2023-08-29T00:22:07.900119Z	From https://github.com/moepool/moe-web
2023-08-29T00:22:07.900819Z	 * branch            527243b1f172fb33fadfb285db10ec6c48fad50a -> FETCH_HEAD
2023-08-29T00:22:07.901009Z
2023-08-29T00:22:09.011382Z	HEAD is now at 527243b Update .babelrc
2023-08-29T00:22:09.012275Z
2023-08-29T00:22:09.142423Z
2023-08-29T00:22:09.178364Z	Success: Finished cloning repository files
2023-08-29T00:22:11.142Z	Detected the following tools from environment<EMAIL_ADDRESS><EMAIL_ADDRESS>2023-08-29T00:22:11.143558Z	Installing nodejs 18.17.1
2023-08-29T00:22:11.80658Z	Trying to update node-build... ok
2023-08-29T00:22:12.088955Z	Downloading node-v18.17.1-linux-x64.tar.gz...
2023-08-29T00:22:12.089323Z	-> https://nodejs.org/dist/v18.17.1/node-v18.17.1-linux-x64.tar.gz
2023-08-29T00:22:13.954756Z	Installing node-v18.17.1-linux-x64...
2023-08-29T00:22:15.550954Z	Installed node-v18.17.1-linux-x64 to /opt/buildhome/.asdf/installs/nodejs/18.17.1
2023-08-29T00:22:15.551542Z
2023-08-29T00:22:17.479682Z	Preparing<EMAIL_ADDRESS>for immediate activation...
2023-08-29T00:22:18.353541Z	Installing project dependencies: yarn --pure-lockfile --no-progress --emoji false
2023-08-29T00:22:19.054915Z	yarn install v1.22.19
2023-08-29T00:22:19.158256Z	[1/4] Resolving packages...
2023-08-29T00:22:19.527902Z	[2/4] Fetching packages...
2023-08-29T00:22:56.897685Z	[3/4] Linking dependencies...
2023-08-29T00:22:56.8997Z	warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>2023-08-29T00:22:56.901796Z	warning " ><EMAIL_ADDRESS>has unmet peer dependency "@mdx-js/react@*".
2023-08-29T00:22:56.910342Z	warning "next-pwa ><EMAIL_ADDRESS>has unmet peer dependency "webpack@>=2".
2023-08-29T00:22:56.910719Z	warning "next-pwa ><EMAIL_ADDRESS>has unmet peer dependency "webpack@*".
2023-08-29T00:22:56.911086Z	warning "next-pwa ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>2023-08-29T00:22:56.911432Z	warning "next-pwa ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.9.0".
2023-08-29T00:22:56.91204Z	warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
2023-08-29T00:22:56.912588Z	warning " ><EMAIL_ADDRESS>has unmet peer dependency "react-is@>= 16.8.0".
2023-08-29T00:22:56.914857Z	warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
2023-08-29T00:23:33.215289Z	[4/4] Building fresh packages...
2023-08-29T00:23:35.61997Z	$ husky install
2023-08-29T00:23:35.740344Z	husky - Git hooks installed
2023-08-29T00:23:35.750683Z	Done in 76.70s.
2023-08-29T00:23:35.836919Z	Executing user command: npx @cloudflare/next-on-pages@1
2023-08-29T00:23:39.099136Z	npm WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>2023-08-29T00:23:45.470821Z	npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject.
2023-08-29T00:23:45.583464Z	npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
2023-08-29T00:23:50.461282Z	⚡ @cloudflare/next-on-pages CLI v.1.6.0
2023-08-29T00:23:51.02466Z	⚡ Detected Package Manager: yarn (classic)
2023-08-29T00:23:51.02524Z	⚡ Preparing project...
2023-08-29T00:23:51.028556Z	⚡ Project is ready
2023-08-29T00:23:51.971668Z	⚡ vercel dev dependency missing, installing vercel as a dev dependency with 'yarn add vercel -D'...
2023-08-29T00:23:52.272992Z	▲  yarn add v1.22.19
2023-08-29T00:23:52.397668Z	▲  [1/4] Resolving packages...
2023-08-29T00:23:53.991705Z	▲  [2/4] Fetching packages...
2023-08-29T00:23:59.816216Z	▲  [3/4] Linking dependencies...
2023-08-29T00:23:59.817745Z	▲  warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>2023-08-29T00:23:59.819475Z	▲  warning " ><EMAIL_ADDRESS>has unmet peer dependency "@mdx-js/react@*".
2023-08-29T00:23:59.826563Z	▲  warning "next-pwa ><EMAIL_ADDRESS>has unmet peer dependency "webpack@>=2".
2023-08-29T00:23:59.82691Z	▲  warning "next-pwa ><EMAIL_ADDRESS>has unmet peer dependency "webpack@*".
2023-08-29T00:23:59.827319Z	▲  warning "next-pwa ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>2023-08-29T00:23:59.827567Z	▲  warning "next-pwa ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.9.0".
2023-08-29T00:23:59.827751Z	▲  warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
2023-08-29T00:23:59.828124Z	▲  warning " ><EMAIL_ADDRESS>has unmet peer dependency "react-is@>= 16.8.0".
2023-08-29T00:23:59.830281Z	▲  warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
2023-08-29T00:24:14.038966Z	▲  [4/4] Building fresh packages...
2023-08-29T00:24:14.403695Z	▲  success Saved lockfile.
2023-08-29T00:24:14.553207Z	▲  success Saved 70 new dependencies.
2023-08-29T00:24:14.554639Z	▲  info Direct dependencies
2023-08-29T00:24:14.554877Z	▲  └─<EMAIL_ADDRESS>2023-08-29T00:24:14.55505Z	▲  info All dependencies
2023-08-29T00:24:14.55519Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.555554Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.555839Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.556018Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.556193Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.556327Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.556454Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.556596Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.556729Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.556855Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.556995Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.557143Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.557272Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.557404Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.557538Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.557681Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.557811Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.557936Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.558078Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.55821Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.558335Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.558461Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.558598Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.558725Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.558857Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.558982Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.559245Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.559385Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.559521Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.55965Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.559776Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.559898Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.560019Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.560168Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.560293Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.560416Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.560555Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.560682Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.560806Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.56093Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.561067Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.561197Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.561328Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.561457Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.561604Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.561731Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.561858Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.561993Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.562137Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.562266Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.562391Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.562523Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.562649Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.562773Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.5629Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.563023Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.563164Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.563293Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.563421Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.563553Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.563679Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.563802Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.563935Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.56408Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.564237Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.564365Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.564495Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.56463Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.564757Z	▲  ├─<EMAIL_ADDRESS>2023-08-29T00:24:14.56488Z	▲  └─<EMAIL_ADDRESS>2023-08-29T00:24:14.57736Z	▲  $ husky install
2023-08-29T00:24:14.696494Z	▲  husky - Git hooks installed
2023-08-29T00:24:14.705925Z	▲  Done in 22.44s.
2023-08-29T00:24:14.776204Z	⚡ Install completed
2023-08-29T00:24:14.776639Z	⚡ Building project...
2023-08-29T00:24:15.091572Z	▲  yarn run v1.22.19
2023-08-29T00:24:15.138665Z	▲  $ /opt/buildhome/repo/node_modules/.bin/vercel build
2023-08-29T00:24:15.780883Z	▲  Vercel CLI 32.1.0
2023-08-29T00:24:17.017756Z	▲  Installing dependencies...
2023-08-29T00:24:17.380063Z	▲  [1/4] Resolving packages...
2023-08-29T00:24:17.78207Z	▲  success Already up-to-date.
2023-08-29T00:24:17.800353Z	▲  $ husky install
2023-08-29T00:24:17.919461Z	▲  husky - Git hooks installed
2023-08-29T00:24:17.957507Z	▲  Detected Next.js version: 12.1.0
2023-08-29T00:24:17.961356Z	▲  Running "yarn run build"
2023-08-29T00:24:18.238342Z	▲  $ next build
2023-08-29T00:24:18.885208Z	▲  info  - Loaded env from /opt/buildhome/repo/.env
2023-08-29T00:24:20.315887Z	▲  Attention: Next.js now collects completely anonymous telemetry regarding usage.
2023-08-29T00:24:20.31709Z	▲  This information is used to shape Next.js' roadmap and prioritize features.
2023-08-29T00:24:20.317533Z	▲  You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
2023-08-29T00:24:20.317814Z	▲  https://nextjs.org/telemetry
2023-08-29T00:24:20.511394Z	▲  info  - Checking validity of types...
2023-08-29T00:24:52.773906Z	▲  ./src/pages/MinerDashboard/Settings/PayoutSettings/ThresholdInput.tsx
2023-08-29T00:24:52.774499Z	▲  40:6  Warning: React Hook useMemo has a missing dependency: 'isBTC'. Either include it or remove the dependency array.  react-hooks/exhaustive-deps
2023-08-29T00:24:52.774697Z	▲
2023-08-29T00:24:52.774844Z	▲  info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
2023-08-29T00:24:52.782045Z	▲  info  - Creating an optimized production build...
2023-08-29T00:24:52.790551Z	▲  warn  - using beta Middleware (not covered by semver) - https://nextjs.org/docs/messages/beta-middleware
2023-08-29T00:24:52.816375Z	▲  info  - Disabled SWC as replacement for Babel because of custom Babel configuration ".babelrc" https://nextjs.org/docs/messages/swc-disabled
2023-08-29T00:24:52.866905Z	▲  > [PWA] Compile client (static)
2023-08-29T00:24:52.870182Z	▲  > [PWA] Custom worker found: /opt/buildhome/repo/worker/index.js
2023-08-29T00:24:52.870521Z	▲  > [PWA] Build custom worker: /opt/buildhome/repo/public/worker-W1Jpcd3wq34nT8gb0WN0p.js
2023-08-29T00:24:52.949625Z	▲  > [PWA] Auto register service worker with: /opt/buildhome/repo/node_modules/next-pwa/register.js
2023-08-29T00:24:52.950085Z	▲  > [PWA] Service worker: /opt/buildhome/repo/public/service-worker.js
2023-08-29T00:24:52.950407Z	▲  > [PWA]   url: /service-worker.js
2023-08-29T00:24:52.950633Z	▲  > [PWA]   scope: /
2023-08-29T00:24:53.432321Z	▲  > [PWA] Compile server
2023-08-29T00:24:53.941121Z	▲  info  - Using external babel configuration from /opt/buildhome/repo/.babelrc
2023-08-29T00:25:43.959485Z	▲  [BABEL] Note: The code generator has deoptimised the styling of<EMAIL_ADDRESS>as it exceeds the max of 500KB.
2023-08-29T00:26:25.625651Z	▲  Failed to compile.
2023-08-29T00:26:25.626287Z	▲
2023-08-29T00:26:25.626501Z	▲  ./src/pages/GetStarted/Nicehash/assets/nh_1.jpg
2023-08-29T00:26:25.626654Z	▲  TypeError: Failed to parse URL from /opt/buildhome/repo/node_modules/next/dist/server/lib/squoosh/mozjpeg/mozjpeg_node_dec.wasm
2023-08-29T00:26:25.62679Z	▲  at Object.fetch (node:internal/deps/undici/undici:11576:11)
2023-08-29T00:26:25.626919Z	▲
2023-08-29T00:26:25.627063Z	▲  Import trace for requested module:
2023-08-29T00:26:25.627198Z	▲  ./src/pages/GetStarted/Nicehash/NicehashGuide.page.tsx
2023-08-29T00:26:25.627332Z	▲  ./pages/get-started/[ticker]/nicehash.tsx
2023-08-29T00:26:25.627485Z	▲
2023-08-29T00:26:25.627619Z	▲  ./src/pages/GetStarted/Nicehash/assets/nh_2.jpg
2023-08-29T00:26:25.62776Z	▲  TypeError: Failed to parse URL from /opt/buildhome/repo/node_modules/next/dist/server/lib/squoosh/mozjpeg/mozjpeg_node_dec.wasm
2023-08-29T00:26:25.627891Z	▲  at Object.fetch (node:internal/deps/undici/undici:11576:11)
2023-08-29T00:26:25.628018Z	▲
2023-08-29T00:26:25.628173Z	▲  Import trace for requested module:
2023-08-29T00:26:25.628302Z	▲  ./src/pages/GetStarted/Nicehash/NicehashGuide.page.tsx
2023-08-29T00:26:25.628436Z	▲  ./pages/get-started/[ticker]/nicehash.tsx
2023-08-29T00:26:25.628565Z	▲
2023-08-29T00:26:25.628704Z	▲  ./src/pages/GetStarted/Nicehash/assets/nh_3.jpg
2023-08-29T00:26:25.628833Z	▲  TypeError: Failed to parse URL from /opt/buildhome/repo/node_modules/next/dist/server/lib/squoosh/mozjpeg/mozjpeg_node_dec.wasm
2023-08-29T00:26:25.628958Z	▲  at Object.fetch (node:internal/deps/undici/undici:11576:11)
2023-08-29T00:26:25.629108Z	▲
2023-08-29T00:26:25.62924Z	▲  Import trace for requested module:
2023-08-29T00:26:25.62937Z	▲  ./src/pages/GetStarted/Nicehash/NicehashGuide.page.tsx
2023-08-29T00:26:25.629508Z	▲  ./pages/get-started/[ticker]/nicehash.tsx
2023-08-29T00:26:25.629714Z	▲
2023-08-29T00:26:25.629892Z	▲  > Build failed because of webpack errors
2023-08-29T00:26:25.73127Z	▲  error Command failed with exit code 1.
2023-08-29T00:26:25.731661Z	▲  info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2023-08-29T00:26:25.761825Z	▲  Error: Command "yarn run build" exited with 1
2023-08-29T00:26:25.864449Z	▲  error Command failed with exit code 1.
2023-08-29T00:26:25.865051Z	▲  info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2023-08-29T00:26:25.883323Z
2023-08-29T00:26:25.883791Z	⚡ The Vercel build (`yarn vercel build`) command failed. For more details see the Vercel logs above.
2023-08-29T00:26:25.884116Z	⚡ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.
2023-08-29T00:26:25.884398Z
2023-08-29T00:26:25.900198Z	npm notice
2023-08-29T00:26:25.900798Z	npm notice New minor version of npm available! 9.6.7 -> 9.8.1
2023-08-29T00:26:25.901249Z	npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.8.1>
2023-08-29T00:26:25.901558Z	npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
2023-08-29T00:26:25.901736Z	npm notice
2023-08-29T00:26:25.925016Z	Failed: Error while executing user command. Exited with error code: 1
2023-08-29T00:26:25.940674Z	Failed: build command exited with code: 1
2023-08-29T00:26:27.192084Z	Failed: error occurred while running build command

I'm getting a similar error when building with next-on-pages in CI (have only just encountered this, but this may be because we were previously just using next build to upload a static site, and I'm migrating to next-on-pages to leverage some of the edge stuff).
Running locally with yarn install and then yarn next-on-pages works fine, but when I do the same in the docker container that we use in CI I get the following error:
⚡ @cloudflare/next-on-pages CLI v.1.6.0
⚡ Detected Package Manager: yarn (classic)
⚡ Preparing project...
⚡ Project is ready
⚡ Building project...
▲  error Command "vercel" not found.
▲  info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

⚡ The Vercel build (`yarn vercel build`) command failed. For more details see the Vercel logs above.
⚡ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.

Here's the (stripped down for privacy) dockerfile we're using:

FROM alpine

RUN apk add --no-cache \
    yarn \
    nodejs-current

COPY /package.json /yarn.lock /

RUN --mount=type=cache,target=/usr/local/share/.cache/yarn/v6 \
    yarn install --network-timeout 240000 \

ENV PATH="${PATH}:/node_modules/.bin"

CMD ["/bin/bash"]

This unusual setup means that /node_modules is in a different location than the working directory (/code).  We do it in order to cache node_modules/ and not have to reinstall in every ci run.  I think next-on-pages is then failing to find and execute the vercel script from this non-standard location - but next-on-pages ran fine because we had explicitly added it to our path.
Our solution to fix the error was adding a step to our build script.  After mounting our /code directory, we create a symbolic link to the root /node_modules folder.  I'm not sure if our error is strictly the fault of next-on-pages, but I hope this observation helps others with debugging.

@zionfuo the 500kb issue you're getting seems to come from Babel: https://github.com/babel/babel/blob/5d1fb54c6b295c973942cdb34ecb01bf49bc2a7d/packages/babel-generator/src/index.ts#L107-L108
I am not really too familiar with Babel but it looks like you should be able to fix that by setting this compact flag in your .babelrc file: https://babeljs.io/docs/options#compact
did you try that?

I think that the original issue has been resolved a while back, so I'm closing this
@zionfuo if you still have some issues (like the 500KB one) please feel free to open a new issue for that 🙏


[QUESTION] Athena Hudi Time Travel Queries

Just a quick question that might even end up as yes/no.
I've been looking into having a Hudi table queried by Athena. And wondering about the compatibility of time travel queries.
To my understanding, there is functionality with presto/spark but this isn't supported in hive. in order to build the time travel query use _hoodie_commit_time. What is the efficiency like in using this method and would it be best practice?
I was scanning some of the older issues and would an example like the following be appropriate? (note the project has developed a bit since then and wanted to make sure this is still the case)
https://github.com/apache/hudi/issues/2201

As you can imagine, there is already a "hacky" way to achieve time travel using the following methodology : select * from table where _hoodie_commit_time <= point_in_time. Obviously, this is not very efficient and can also lead to inconsistent results since the point_in_time might be different that the hoodie def~instant-time.

https://cwiki.apache.org/confluence/display/HUDI/RFC+-+07+%3A+Point+in+time+Time-Travel+queries+on+Hudi+table
A clear and concise description of what you expected to happen.
Environment Description

Hudi version : 0.10.0

Hive version : Glue Catalogue / Athena

I have a similar business need:
Imagine that you have a fact table containing the sales of a given period. So you have the salesman id , the product id and at which price the product was sold and a timestamp of the sale.
|salesman_id|product_id|price_sold|sales_timestamp  |
|    fedsp      |    10001    |    0.99     |2022-01-15 13:10|
At the end of each month, the department calculates a bonus for each salesman based on the sales data.
After 3 months, a salesman complained that in october 2021 the bonus was not calculated properlly, but here comes the issue: The sales table can be updated anytime. Then we need to see not the current data for october 2021, but how the data was in november1st, the day where the bonus was calculated.
There are several ways to do it, but often does ways envolves hacky ways that lead to more maintenance, non optimized data storage (lots of duplicated data) and adding additional columns in the data which originally was not needed.

We did add time travel query support few versions back. Please refer here for example.

@fedsp : I assume "as of instant" query work for you. If not , can you elaborate bit more.

But as far as I understood, this applies for spark contexts only, right?
There is any equivalent which I can use in a standard sql query? My usecase uses a prestodb database (more specifically, aws athena)

@fedsp this is a feature to be added to support spark sql read path
https://issues.apache.org/jira/browse/HUDI-3221

Awesome, glad to hear! If you want a beta tester to test it and simulate a real business case scenario count on me! My username on confluence is @fedsp as well.

@fedsp done! let's keep collaborating on this

Awesome, glad to hear! If you want a beta tester to test it and simulate a real business case scenario count on me! My username on confluence is @fedsp as well.

cc @XuQianJin-Stars @YannByron

awesome @fedsp, sure. appreciate it. As we have a tracking jira, let's continue discussions in the jira so that it will help in bookkeeping. Feel free to subscribe to the jira.
If you don't have any more questions/clarifications, we can close out the github issue.

Closing this as we have a tracking jira. thanks!

Implementation https://github.com/apache/hudi/pull/4720/

Hi,
Is this accessible today via AWS Athena? Any one who has tried it ?

+1 On AWS Athena

Any idea from the dev community?
On Mon, Jan 2, 2023, 21:21 IvyIvy1109 @.***> wrote:

+1 On AWS Athena
—
Reply to this email directly, view it on GitHub
https://github.com/apache/hudi/issues/4502#issuecomment-1369186532, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2SEX2W4NTCE5KM65WV22DWQM2EVANCNFSM5LGGYPLQ
.
You are receiving this because you commented.Message ID:
@.***>


Spirv opt uses optimizer class

This builds on https://github.com/KhronosGroup/SPIRV-Tools/pull/612

Thanks for approval.  I'll fix the order of the using decl, keep approval. Then I'll submit after the bots come back green.

Rebased. Keeping approval. No need for review.  :-)


Kubernetes API is unreachable without being connected to a router

Hello, I am facing a problem with kubernetes API not being reachable whenever the network gets disconnected. Moreover, by network i don't mean internet connection. It becomes reachable again the moment I connect it to a router even without internet connection! here are some logs showing the kubernetes API being unreachable even though it is running.
kubectl -n kube-system logs cilium-operator-774f85cdd8-bbxx6 | tail
level=info msg="Establishing connection to apiserver" host="https://<IP_ADDRESS>:443" subsys=k8s
level=error msg="Unable to contact k8s api-server" error="Get https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system: dial tcp <IP_ADDRESS>:443: connect: network is unreachable" ipAddr="https://<IP_ADDRESS>:443" subsys=k8s
level=fatal msg="Unable to connect to Kubernetes apiserver" error="unable to create k8s client: unable to create k8s client: Get https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system: dial tcp <IP_ADDRESS>:443: connect: network is unreachable" subsys=cilium-operator

the output for sudo iptables -t nat -L -n -v in the attachements
iptables-output.txt
the generated tarball from microk8s inspect in the attachments
inspection-report-20201117_104726.tar.gz
microk8s version 1.19.2

any updates here?