Sending cdi version with requests

The library should send the CDI version it uses with each request to make sure that it uses a version both support.

I added sorting to SupportedApiVersions because the code below depends on it being in descending order, and it seems too easy to make a mistake and have them in ascending order.
Of course, I'm happy to move this into a comment if that's your preference or into GetApiVersionAsync itself.

Looks fine to me. To be honest, I started to rethink the structure of the API client after having started to use it and the complexity of needing the CDI version. I had brainstormed a refactor where the CDI version becomes an internal implementation detail of the API client, and then the method signatures drop the explicit CDI version argument. (Essentially, push this whole API version container concept into the API client.) I couldn't really brainstorm a reason why a caller would want to explicitly choose an older/different CDI version, and moving it inside would make using the API client much simpler (wouldn't have to access the API version container and the API client, could just simply depend on the API client). I believe I started to experiment with some of this on my wip branch. Let me know if this is interesting, and maybe this conversation could shift over to a GitHub issue for further development or refinement.

Moving the APIContainer into the API client is a great idea; I just didn't want to change the structure too much.

No worries. A refactor like that would be a much bigger change. This at least gets the correct API client behavior implemented!


Typo in version of Remote Desktop client

The Microsoft Store client's "latest version" is listed as 1.2.1810. It should be 10.2.1817.

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

ID: 86f7187f-7e2e-da7f-6f46-46568be43db7
Version Independent ID: 49714e7e-ecfb-dba3-f43a-17b6ca677fa6
Content: Remote Desktop clients
Content Source: WindowsServerDocs/remote/remote-desktop-services/clients/remote-desktop-clients.md
Product: windows-server
Technology: remote-desktop-services
GitHub Login: @Heidilohr
Microsoft Alias: helohr

Hey ldoron,
Thanks again for contacting Microsoft. We value your feedback.
Updates have occurred during the time this issue was opened and new information about the Windows Store client for RDS can be found here: https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/windows-whatsnew
We will now be closing this thread. Thank you and have a most pleasant day.
#please-close


As a  ui-developer, I want to stylize URLs in the data table so that they can be clicked

As a  ui-developer, I want to stylize URLs in the data table so that they can be clicked
Expected behavior

When the data table contains any URL it automatically shows up as a clickable link

Actual behavior
Currently no such functionality exists
Steps to reproduce the behavior

has been fixed for awhile


dep: bump alloy to 0.3.6

#55  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @prestwich and the rest of your teammates on  Graphite


All 'snabb lwaftr' apps should be run by CI

It can be a token test to just make sure they do something trivial without crashing, but it should be run on every pull request. Being able to do this even when they require hardware is one reason we moved to snabbbot from travis-ci.

Snabb-bot runs all selftest.sh scripts in the code base and all Lua files which contain a selftest function. It actually runs several lwAFTR apps, but only those one which contain a selftest. For instance:
TEST      apps.lwaftr.dump
TEST      apps.lwaftr.lwdebug
TEST      apps.lwaftr.ndp
TEST      apps.lwaftr.fragmentv4_test
TEST      apps.lwaftr.fragmentv4_hardened
TEST      apps.lwaftr.V4V6
TEST      apps.lwaftr.conf
TEST      apps.lwaftr.fragmentv6_hardened
TEST      apps.lwaftr.rangemap
TEST      apps.lwaftr.channel
TEST      apps.lwaftr.podhashmap

https://gist.github.com/lwaftr-igalia/c64c25845f7a13c9bf7822c4feddf033

Yeah, that's not good enough - the test suite should be testing more, including the front ends, not just random unit testy bits.

Besides the Lua unit tests, Snabb-bot also runs all selftest.sh scripts in the code base. This is useful for writing more sophisticated tests, for instance tests that run a Snabb tool, setup a VM, run system tools, etc (an example of a test like this is the SnabbNFV test).
If we extended Snabb-bot to parse all the tools in program/lwaftr and simply run them, likely the output would be the help of those tools. It won't detect that a tool is broken, like happened the other day with "lwaftr query" because specifically in that case testing certain parts of its code involved having a running lwaftr instance (I believe this is true for other lwaftr tools). A test like this can be written as a selftest.sh script. If a tool doesn't involve such complexity it can be tested by adding a selftest() function that runs function "run()" with certain parameters. For instance that could be the case of "lwaftr check" which doesn't depend on other external tool.
Summarizing, if we want to test "lwaftr" apps front-ends we just need to write tests for them.

Obviously we don't want to just run the tools with no arguments after automatically detecting they exist and get the help...
I agree that invoking the front ends from selftest.sh scripts is a reasonable mechanism. The point is that we have to actually do that.

This task can be very time consuming for one person. I think it's better to split it in several subtasks, one selftest per UI tool, and let people work in one test at a time (instead of assigning all the tests to one single person). We need UI tests for the following tools:

[ ] lwaftr bench selftest.
[ ] lwaftr check selftest.
[ ] lwaftr loadtest selftest.
[ ] lwaftr monitor selftest.
[x] lwaftr query selftest.
[ ] lwaftr run selftest.

There's now a selftest for lwaftr query (#711), which can serve as reference. There are also UI tests for the snabb config subcommands (#658).
IMHO, the most important tests to have are lwaftr run and lwaftr loadtest.

I agree. Let's use this as a grouping issue and create new specific issues for each selftest when we get around to creating them.

Current situation:

some initial tests in src/program/lwaftr/selftest.sh;
config tests in src/program/lwaftr/tests/config/;
query tests in src/program/lwaftr/query/tests/;

They use separate support code and different subcommand models.
In #736 I put some common code in src/program/lwaftr/tests/common.sh, and then used it when refactoring the config tests (#740) and the query tests (#741). Future tests will use it too.

Subcommand selftests have been implemented in Python using the infrastructure described in #749.

This is now complete.

Woo, well done! Thank you @teknico !


Support for BSDs

I tried to install this on my FreeBSD environment and I received the error:
freebsd-x64 is not currently a supported platform
Would be love to see this platform supported - is there anything I can do to help?

@No9  have you tried installing from git ?  We package prebuilt binaries on the npm install and don't support freebsd currently but it should install and build for you if you install from this repo

@tobespc Thanks I will give that a look

@tobespc Just an update - looks like https://github.com/RuntimeTools/omr-agentcore needs a port implemented for BSD https://github.com/RuntimeTools/omr-agentcore/tree/master/src/ibmras/common/port

I am trying to install on FreeBSD also and I have the same issue.
omr-agentcore seems to be incompatible

We don't have any plans to add this in the near future (and don't actually have any machines with BSD installed on them) so I'm adding the ice box label, although we are open to PRs if anyone is interested in doing the work.


rxdb 13 breaks lazy collection creation

Lazy collection creation is broken when rxdb 13 is used. This means that data from collections that have been created retroactively are not picked up.

Confirm. I just started to play around with these hooks and nothing works :sweat: Direct db calls like:
await db.transactions.find().sort("createdAt").exec()

work fine.


Release 1.1

Adds release notes for the next version.
Depends on https://github.com/scylladb/sphinx-scylladb-theme/pull/230 and https://github.com/scylladb/sphinx-scylladb-theme/pull/178

We'll complete https://github.com/scylladb/sphinx-scylladb-theme/projects/2?card_filter_query=milestone%3A1.1 before merging this PR.


Consider Using Coverband and Sorbet

Consider use of Coverband to measure production usage of code: https://github.com/danmayer/coverband
Consider use of Sorbet to emulate statically typed language in Ruby: https://github.com/sorbet/sorbet
This would be adding to a development toolset that already includes:

Rspec, FactoryBot & Faker
SimpleCov & Codecov
Rubocop
Brakeman

Prefer not to use Sorbet, not because it isn't interesting and worth a look, but because dynamic typing is what Ruby developers are more familiar with. As the project is Open Source, we want to keep the codebase as readable and familiar to new users/contributors/developers as possible.


Add support for python3

Hi
is possible add support for python3?
greetings

is possible to ask why ?

from py website

Note that Python 3.5+ cannot be used on Windows XP or earlier.

bytheway this why not

is possible to ask why ?

what is the real problem make a dual python support like other programs/libs?

It's more a pita to maintain.

A really big pain. Python 2 and Python 3 share the same fundamental design, but are very different. You're basically asking a person who does this in their free time to double their work.

and when python 2 reatches its EOL?
https://www.python.org/dev/peps/pep-0373/

When it reaches its EOL, then you update the code to Python 3 and you don't have to manage two separate languages doing the same thing.

like now? i'm linux user, need both pythons because need keep older version of python for programs like this

nope, no time to do it. I'm accepting pull request if someone can do it (and it doesn't break anything).
I'm using windows and python 2.7.x only.

hi, i'm trying on my fork so it can be able to run on python3. until this commit https://github.com/rachmadaniHaryono/PixivUtil2/commit/edcf06f301674f69799ac7f61d2705a782335e26 i have sucessfully download single image id by copy the session value from browser.
here are some difficulties, when trying to port it:

i skip setting system default encoding based on this recommendation https://stackoverflow.com/questions/3828723/why-should-we-not-use-sys-setdefaultencodingutf-8-in-a-py-script
also skip print_progress. may or may not related to python3 port
usage of file keyword. use open to replace it. related stackoverflow https://stackoverflow.com/questions/24942358/is-file-a-keyword-in-python
use in instead of has_key to check key on dict
i use six to fix some compatibility.

because unicode is replace with six.u, some check with isinstance have to be change to six.text_type instead of unicode
some module that use this

httplib.BadStatusLine
urllib2.URLError
urllib2.HTTPError
reload
unichr
unicode
raw_input
htmlparser
urllib2
ConfigParser

there are already config for pylint and pep8, but both have not max-line-length defined, so i just made one based on the max line length i found (210).
mechanize

mechanize is not available python3, i'm using mechanicalsoup to replace it. i haven't check all the pixivutil feature, but there is already mechanize feature, which is not yet on mechanical soup (see open_novisit below)
mechanicalsoup don't have open_novisit method. for temporary fix, i skip the filesize check and use python3's urlopen to get response for Request object.
method to replace unenscape_charref is also skipped. not quite sure if the fix also needed on python3 or even mechanicalsoup
return value of Browser.open is now quite different. it return requests.models.Response obj.
some setting on Browser is skipped, because it is not implemented on mechanicalsoup (set_handle_redirect, set_handle_referer, set_handle_robots, set_debug_http)

BeautifulSoup: for this i use BeautifulSoup4 to use it with python3

there are some warning, which caused by non existent parser argument
there are some change with html tag checking
when parsing tag (ParseTags(self, page)), tag['class'] return list instead of string

print function is one of the most changed on the program. there are 2 problem with current print usage on the program

first is the parenthesis, which mostly non existent
second is trailing comma on some print usage, see this related stackoverflow https://stackoverflow.com/questions/4009672/python-trailing-comma-after-print-executes-next-instruction. this require an if/else to fix it (maybe there is better way?)

some misc thing

PixivUtil2module

PixivArtist is not used
ERROR_SUCCESS is imported twice

finished setting a travis test on test.PixivModel.py

it used pytest as test framework

it report `test.PixivModel.py as invalid filename.

solution: symlink it to test_PixivModel.py on travis

on installation phase the config for python3.3 failed because Numpy 1.14.2 require either python2.7 or minimum python3.4
py2/py3

re.findall don't accept bytes, so solution for using six's unicode not work directly.

solution: currently recast it to str on python3

re.findall result also can't compared to integer. on python3 it will return list

test module (test.PixivModel.py)

with python3 which require bs4, there will be warning when no parser is not defined.

solution: create new class which inherit BeautifulSoup. current parser is set to html.parser

some test is set to xfail. should compare it with python2.7 test result and if possible fix it. current number of xfail is 33 (at the time of writing)

@Nandaka can you check if this branch test result is accurate https://travis-ci.org/rachmadaniHaryono/PixivUtil2/builds/355791687 ?

get the latest (089c17163eddc3b30dd5e99ce9d9a3790ff318a2), I've changed some of the test cases, it should be ok, I think

I'm not on pc now, but I see you have added Travis config.
Do you want add all test to Travis?

i'm trying a new strategy with this branch  https://github.com/rachmadaniHaryono/PixivUtil2/tree/feature/py3
rules:

do least minimum changes
use six lib as much as possible
use mypy when required (not happen, but may be used later)
notes:
on debugging i met line where module have to be wrapped with socks module. i don't know how to test it for python3, so i will skip it for urllib and urllib2. httplib have direct alias in six (six.moves.http_client)
it maybe better to isolate python3 function/method and let it raise error when debugging active (wip). see case below

so when this happen
Trying to log in with saved cookie
Error at doLogin(): (<class 'AttributeError'>, AttributeError("'Response' object has no attribute 'read'",), <traceback object at 0x7f863a363048>)
Cannot Login!
press enter to exit.

do this:

set if-else branch where the function is called
copy doLogin function to doLoginOnPython3
(optional) call the original function
on error check if env vars for debug is enabled (something like PIXIVUTIL2_DEBUG).

if it is, raise actual error and print trace back
if not, use default error handler

To further this, @Nandaka, python 2 EOL is at the end of this year.  a python 3 branch should probably be the top priority.


@charterafrica Community page

Description
This PR implements /opportunities/community page per designs.
Type of change

[x] New feature (non-breaking change which adds functionality)

Screenshots

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas

Looks good to me.
Just a small one.
When you add more than one community platforms, text is overlapped.

The current design dimensions (especially width) only works up to the maximum of 3 items @koechkevin.
Unfortunately, relationship field doesn't support max config similar to array field. Our options appear to be:
i. Custom validation in the back-end to limit only up to 3,
ii. slice up to 3 items on the front-end regardless of how many items we receive from the back-end,
iii. New suggestion.
What are your thoughts?

iii. Fix number of columns to 3 but allow unlimited number of rows.

I think this is better @kilemensi @koechkevin

If the number of cards isn't a multiple of 3 @kelvinkipruto / @koechkevin , there will be a bit of empty space left.


Unable to update chromedriver

I get the following error on Ubuntu, works on local but fails on codeship build:
Updating selenium standalone
downloading http://selenium-release.storage.googleapis.com/2.42/selenium-server-standalone-2.42.2.jar...
Updating chromedriver
downloading http://chromedriver.storage.googleapis.com/2.10/chromedriver_linux64.zip...
chromedriver_2.10.zip downloaded to /home/rof/src/github.com/emartech/trend-reporting/node_modules/grunt-protractor-runner/node_modules/protractor/selenium/chromedriver_2.10.zip

Invalid or unsupported zip format. No END header found

It still happens - but seems to be a random issue. Running webdriver-manager update multiple times will eventually succeed at some point in time (atleast it was like that for me).


How about generate mode from pulsar admin openapi (swagger)

Just a question for generate mode from openapi, it can reduce manual maintenance pressure.

I think it's possible. But pulsar's swagger yaml has some problems. Like operationId conflict. In a sense, it's hard work, and no one is working on it right now.


add rust lang

Signed-off-by: Keming<EMAIL_ADDRESS>

Thanks for your contribution! :tada: :+1:


fix: do not modify options object, use defaultScopes

Regenerated the library using
gapic-generator-typescript
v1.2.1.

This is weird:

@skuruppu Do you have any idea what may be causing this difference?


Extract the weights of a layer

Please make sure that the boxes below are checked before you submit your issue. If your issue is an implementation question, please ask your question on StackOverflow or join the Keras Slack channel and ask there instead of filing a GitHub issue.
Thank you!

[ ] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps

[ ] If running on TensorFlow, check that you are up-to-date with the latest version. The installation instructions can be found here.

[ ] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[ ] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

I want to extract the weights of a layer.When i use save_weights and load_weights,I must use it in a model.This is not what i want. I need to extract the weights of the Dense layer and make it into a fully convolution  layers.Please tell me how to do it if you guys know.

https://github.com/fchollet/keras/issues/91


[BRIDGE-1215] don't make unsubstantiated claims

tremor results will NOT appear in the dashboard

looks good


Custom dataset training

Very great project!!!
I used InstantAvatar's preprocessing method to get data similar to People Snapshot Dataset with simple modifications can be trained in your project, but my trained characters are very unclear and hands can't be displayed. I would like to ask what causes this and when the custom data script will be released?
Regards.

Hi, you need set pose_op_start_iter=10 (10 epochs for initial training) to let pose refinement start.

Hi, you need set pose_op_start_iter=10 (10 epochs for initial training) to let pose refinement start.

Thanks for the reply.
After I tried to modify pose_op_start_iter=10 it is still training very fuzzy, I have compared the processed data and found that only smpl makes a difference. May I ask what method you are using to estimate smpl?
Kind regards

Just the same as you.
I directly employ the preprocessing scripts in InstantAvatar.
I will run the code again to find out whether i miss something or not.

Just the same as you. I directly employ the preprocessing scripts in InstantAvatar. I will run the code again to find out whether i miss something or not.

By comparing the result of instantavatar preprocessing and your demo data, I found that instantavatar uses romp to estimate the smpl. romp will not have hand pose in the prediction result (the author fills it with zeros), but your demo data does have hand pose. I would like to ask how to get the hand pose

Just the same as you. I directly employ the preprocessing scripts in InstantAvatar. I will run the code again to find out whether i miss something or not.

By comparing the result of instantavatar preprocessing and your demo data, I found that instantavatar uses romp to estimate the smpl. romp will not have hand pose in the prediction result (the author fills it with zeros), but your demo data does have hand pose. I would like to ask how to get the hand pose

We use [ProxyCap](https://s based on [Przhangyux15.github.io/ProxyCapV2/) to estimate SMPL-X, but it is not open source yet.
I recommend you to use PyMAF-X.

Just the same as you. I directly employ the preprocessing scripts in InstantAvatar. I will run the code again to find out whether i miss something or not.

By comparing the result of instantavatar preprocessing and your demo data, I found that instantavatar uses romp to estimate the smpl. romp will not have hand pose in the prediction result (the author fills it with zeros), but your demo data does have hand pose. I would like to ask how to get the hand pose

We use ProxyCap to estimate SMPL-X, but it is not open source yet. I recommend you to use PyMAF-X.

thanks,I will try it

Just the same as you. I directly employ the preprocessing scripts in InstantAvatar. I will run the code again to find out whether i miss something or not.

By comparing the result of instantavatar preprocessing and your demo data, I found that instantavatar uses romp to estimate the smpl. romp will not have hand pose in the prediction result (the author fills it with zeros), but your demo data does have hand pose. I would like to ask how to get the hand pose

We use ProxyCap to estimate SMPL-X, but it is not open source yet. I recommend you to use PyMAF-X.

thanks,I will try it

I know why the results are unclear, you need to set lpips_start_iter=10~30 (when to use lpips loss).
Sorry~

Just the same as you. I directly employ the preprocessing scripts in InstantAvatar. I will run the code again to find out whether i miss something or not.

By comparing the result of instantavatar preprocessing and your demo data, I found that instantavatar uses romp to estimate the smpl. romp will not have hand pose in the prediction result (the author fills it with zeros), but your demo data does have hand pose. I would like to ask how to get the hand pose

We use ProxyCap to estimate SMPL-X, but it is not open source yet. I recommend you to use PyMAF-X.

thanks,I will try it

I know why the results are unclear, you need to set lpips_start_iter=10-30 (when to use lpips loss). Sorry
Yes, I also found this problem Also I found that the pose obtained with the ReFit project includes hand information I compared the pose from the People Snapshot Dataset and found that the matrices are exactly the same If you train with the pose obtained from ReFit you might get better results.

Just the same as you. I directly employ the preprocessing scripts in InstantAvatar. I will run the code again to find out whether i miss something or not.

By comparing the result of instantavatar preprocessing and your demo data, I found that instantavatar uses romp to estimate the smpl. romp will not have hand pose in the prediction result (the author fills it with zeros), but your demo data does have hand pose. I would like to ask how to get the hand pose

We use ProxyCap to estimate SMPL-X, but it is not open source yet. I recommend you to use PyMAF-X.

thanks,I will try it

I know why the results are unclear, you need to set lpips_start_iter=10-30 (when to use lpips loss). Sorry
Yes, I also found this problem Also I found that the pose obtained with the ReFit project includes hand information I compared the pose from the People Snapshot Dataset and found that the matrices are exactly the same If you train with the pose obtained from ReFit you might get better results.

Thanks!

Just the same as you. I directly employ the preprocessing scripts in InstantAvatar. I will run the code again to find out whether i miss something or not.

By comparing the result of instantavatar preprocessing and your demo data, I found that instantavatar uses romp to estimate the smpl. romp will not have hand pose in the prediction result (the author fills it with zeros), but your demo data does have hand pose. I would like to ask how to get the hand pose

We use ProxyCap to estimate SMPL-X, but it is not open source yet. I recommend you to use PyMAF-X.

thanks,I will try it

I know why the results are unclear, you need to set lpips_start_iter=10-30 (when to use lpips loss). Sorry
Yes, I also found this problem Also I found that the pose obtained with the ReFit project includes hand information I compared the pose from the People Snapshot Dataset and found that the matrices are exactly the same If you train with the pose obtained from ReFit you might get better results.

sorry to disturb you, I  also want to refine the hand pose for the [PyMAF-X], can you share the pretrain model of the partial_mesh files .
Download the pre-trained model  for the author's provided links are not available. thanks very much


Check compatibility with Vert.x 4.5

See https://vertx.io/blog/whats-new-in-vert-x-4-5/

The build on CI fails for JDK 22 because of this issue: https://github.com/eclipse-vertx/vertx-sql-client/issues/1379


An error occurred (ModelError) when calling the InvokeEndpoint operation: Received server error (500) from model with message "[Errno 2] No such file or directory: '/.sagemaker/mms/models/model/model.pth'".

Can someone help?
I have created a deep learning model using sagemaker using PyTorch framework. I have uploaded the model artifacts into S3 and deployed the model using the following commands.
from sagemaker.pytorch import PyTorchModel
from sagemaker import get_execution_role
role = get_execution_role()
import boto3
import numpy as np
pytorch_model = PyTorchModel(model_data='s3://pytorchexample/model.tar.gz', role=role, entry_point='inference.py', framework_version='1.4')
predictor = pytorch_model.deploy(instance_type='ml.t2.medium', initial_instance_count=1)
the endpoints gets created but while testing the model I get the following error:
An error occurred (ModelError) when calling the InvokeEndpoint operation: Received server error (500) from model with message "[Errno 2] No such file or directory: '/.sagemaker/mms/models/model/model.pth'". See https://us-east-1.console.aws.amazon.com/cloudwatch/home
I am not sure why PyTorch is looking for sagemaker folder for the model.pth file. It resides in the S3 bucket.

@ChandanVerma would you able to resolve it? facing the same issue... a comment would be appreciated.

Same issue. I think model source location and hosting server path are two different thing.
So, it has nothing to do with model_data path. The problem is that once sagemaker copies a model.tar.gz from s3 to sagemaker hosting server, it can't find when it is. It is possible that this might be related to bug.  Normally model file is located in /opt/ml/model/ but Pytorch container is just different with no apparent reason.

@ChandanVerma have you fixed the issue? I have got the same error when I put a wrong name to the model file.
Also SageMaker endpoint to work, it is possible NOT to define model_fn, the SageMaker will use the default model_fn implementation which expect "model.ph" or "model.pth". If file name is different, this error will be raised.
So the check point will be.

If the model fils is in the root of .tar.gz.
If the filename is Pytorch defaults (pytorch_model.bin) or SageMaker default (model.pth, model.ph).

It is annoying AWS does not provide detail information on how it works especially the new MMS they recently switched to.

Sorry about replying so late...No the issue wasn't solved and I had limited time, so I started using PyTorch wrapper provided by sagemaker for training the model and deployed it using their API Gateway services.

Are there any updates about this issue? I'm facing the same problem.


fix: optimize message receive for big messages

related to https://github.com/NativeScript/nativescript-cli/issues/4226
Seems that the following code causes 100% CPU usage:
memcpy(temp, result, final_length);
memcpy(temp + final_length, buffer, bytes_read);

so the code is refactored to use std::string

Awesome work!


Try circleci convenience images

Testing

Fails

:no_entry_sign:
Yarn Audit Issues Found:
high - Prototype Pollution in JSON5 via Parse Method
Package json5
Patched in >=2.2.2
Dependency of @trussworks/react-file-viewer
Path @trussworks/react-file-viewer > pdfjs-dist > worker-loader > loader-utils > json5
More info https://github.com/advisories/GHSA-9c47-m6qq-7p4h
1 high vulnerabilities and 0 critical vulnerabilities found

Warnings

:warning:
Please include a description of your PR changes.

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 52432dcc8ef51bac921e2b419f4d62131a217113


Non-integer decimal numbers lose precision

Parsing a non-integer decimal number with more than about 16 digits will truncate the precision of the number to the what can be represented by a float64:
$ echo 0.123456789012345678901234567890 | gojq '. | tojson'
"0.12345678901234568"

In comparison, jq will preserve all of the decimal precision for non-arithmetic operations (e.g. . and tojson):
$ echo 0.123456789012345678901234567890 | jq '. | tojson'
"0.123456789012345678901234567890"

gojq currently supports arbitrary precision for integer values, including integer arithmetic operations. It would be great if it also supported arbitrary precision for non-integer decimal values for "passthrough" operations, and possibly arithmetic operations.

This is related to the issue #212 and will be resolved by the json-number branch.

@itchyny for clarity, that would solve the pass thru part but not doing operations?
For reference @matthewdale did a draft PR for decimal support in the fq fork https://github.com/wader/gojq/pull/1 but i'm a bit reluctant to add more difference to upstream unless it can be done in a easy rebase-able and maintainable way


Sort by date not program id

This is already on my to-do list. Please refer to Trello for minor things like this.
https://trello.com/c/53L5ILJH/25-order-contests-entries-by-date-created


Put up message when voyage time seems inaccurate

Quick fix for when the wrong voyage time is reported. This occurs when there is an unresolved dilemma and the player hasn't opened the game. The voyage timer keeps counting. This can be detected by using another counter log_index which only updates while the game is open. Hence if these two measures are either side of a dilemma it is highly probable that this bug has occurred.
I am working on a fix that could correct the bug which will be part of the voyage-bugfixes PR but I think this needs a quick fix as it can result in hugely inaccurate estimates which would erode trust in the calculator. I have attached a player.json that replicates the bug: voyage_bug.txt

This is a quick fix until PR #320 is approved.


thenWhile ?

How would you go with bringing while loops to promises? I've tried
extension Promise {
    func thenWhile(test: Void -> Bool, promise: Promise<Void>) -> Promise<Void> {
        return Promise<Void> { resolve, reject in
            if (test()) {
                return resolve()
            }
            return promise.then { body in
                return self.thenWhile(test, promise: promise)
            }
        }
    }
}

but that's not good :)

Could you provide a usage example showing what you want?

Sure. For instance.
somePromiseStuff
.thenWhile(thereIsNotEnoughItemLoaded, loadMoreItems)
.then(...)

Where thereIsNotEnoughItemLoaded would check if there's enough items loaded and loadMoreItems would be a promise that does an API call and fetch some more items.

somePromiseStuff.then { _ -> Promise<Void> in
    return Promise { fulfill, _ in
        func go() {
            if thereIsNotEnoughItemsLoaded {
                load().then(go)
            } else {
                fulfill()
            }
        }
        go()
    }
}

There could be API added for this.

Yup sure enough. But it'd be great to use promise to remove some of what I see as async boilerplate.
I think that'd go well with the idea behind promise that is to make all the async things much more natural :)

It seems to me this an adaption of our current Queue open issue where instead of specifying a maximum concurrency, you provide a function that decides when to stop.

Yeah, in terms of #449 it would be:
when(
    AnyGenerator<Promise<Void>> {
        return thereIsEnoughItemsLoaded ? nil : after(0.1)
    }
)
.then { _ -> Void in
    // ..
}

Merged: e50dc323c154f110a8defc819b916c09377e102e


examples: move examples from crossplane repo

Description of your changes

Same as https://github.com/crossplaneio/stack-gcp/pull/105
Checklist

I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[x] Updated any relevant documentation, examples, or release notes.
[x] Updated the dependencies in app.yaml to include any new role permissions.

@hasheddan does there need to be any update to the main crossplane docs to update any references to these moved examples?  e.g. maybe the provider setup script?

@jbw976 not yet as the examples directory still exists in the main repo, but I will make sure to update the docs when removing the examples from main repo following the merge of PR's on all stacks!


make-texture-from-id doc is substandard

thanks Baggers. while you're at it, it seems at least the docs for make-texture-from-id could use an update, too. trying to wrap the cl-fond texture and it complains about mipmap-levels and samples, neither of which are mentioned (directly) in the docs

It wasnt just the docs, the function had bugs too. They are fixed on a branch and being merged in soon


change npm run build:combined to npm run build:release

Tips

Thanks very much for contributing to Apache DolphinScheduler.
Please review https://dolphinscheduler.apache.org/en-us/community/index.html before opening a pull request.

What is the purpose of the pull request
change npm run build:combined to npm run build:release
Brief change log
change npm run build:combined to npm run build:release

Add maven-checkstyle-plugin to root pom.xml

Verify this pull request
cd dolphinscheduler-ui execute npm run build:release

Codecov Report

Merging #1504 into dev will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##             dev   #1504   +/-   ##
=====================================
  Coverage   2.77%   2.77%
=====================================
  Files        272     272
  Lines      13598   13598
  Branches    2158    2158
=====================================
  Hits         378     378
  Misses     13201   13201
  Partials      19      19

Continue to review full report at Codecov.

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


Add support for anonymous receivers in saltpack encrypt

@maxtaco I've amended this PR with your suggestion. One problem: The ability to write a unit test is to unit test this as the engine package doesn't have access to the saltpack codec decoding and header parsing. I've added an engine.TestSaltpackAnonymousEncrypt test, but I haven't been able to get it to connect to a local keybase server:
common_test.go:87: API network error: Post http://localhost:3000/_/api/1.0/signup.json: dial tcp [::1]:3000: getsockopt: connection refused

@jacobhaven this looks great.  We don't have a full story for third parties running our integration tests. We haven't made the server API code public yet, so you can't run a copy on localhost, as we do on our dev machines. However, we still have a staging server that we should open up for people to run tests one-off.
Go leads us to be a little bit stingy in exporting data structures, since the linter will complain if we don't comment them, and too may exported structures gum up the godocs. But your test makes a good case that we should export the packet specifications.
One last design issue: the word anonymous might be a little overloaded here, since there's a different capability in saltpack for the sender to hide his identity even to the receivers (also unexposed as of your).  It's an orthogonal feature to the one you implemented, so I wonder if the flag should be called --hide-recipients rather than --anonymous.

So some small nits, otherwise looks great

Looks good to me, with the nits above. Thanks for putting this together! So awesome.

@maxtaco @oconnor663 I think I've addressed all the comments and updated the integration test (Could you please run go test -run "TestSaltpackEncryptHideRecipients" ./go/engine/against your staging server?

It almost worked, but a few things were wrong:

Jack's idea to panic in ToKID was ill-advised, since we need it for receiver de-duping in checkReceivers
You had to encode as binary, not armored.
You have to double-decode the header, since it's double-decoded.  We do this in the spec to allow for convenient computation of hashes over the header.

Otherwise, it worked!
Fixes are here: https://github.com/keybase/client/tree/jacobhaven-tweaks

@maxtaco added those changes to the PR Thanks :)

Jack's idea to panic in ToKID was ill-advised

The illest!

How is your Travis configured such that travis-ci/push passes but /travis-ci/pr fails? That's quite odd...

Seems like had a C/I bug, we're playing with scripts today.  I'll rerun that failed build.

(Push tests your branch by itself, and PR tests the merge of your branch onto master, and it turns out we broke CI on master just now, so that's why PR fails but push doesn't. Fixed in master now, and the PR one is rerunning.)

@cjb @maxtaco I've rebased off of master, but there still appear to be issues with the CI. Docker isn't finding the kbweb image.

We're scratching our heads on why Circle CI is in the mix now. We had that on about ~3 months ago but disabled it.

Circle CI is probably building because I'm pushing to my jacobhaven/client fork and not the main keybase organization one.

@cjb do you have any thoughts on why this PR is wreaking havoc on CI?  I guess because it's being pushed from a different repo.  FWIW, the tests run fine on my local machine...

The Travis run includes the error Error parsing reference: "/kbweb" is not a valid repository/tag. It looks like that comes from the expression $CI_HOST/kbweb in our .travis.yml. I'm guessing we define $CI_HOST in our Travis settings, and no one else does?

I just pushed https://github.com/keybase/client/tree/jack/pull2023 with the same tip as this PR (8193d4cd101f4894c910873b39f681968e92634c). Hopefully this build will work: https://travis-ci.org/keybase/client/builds/109766916

Looks good from here?


Change 'Arm Home' to 'Arm Stay'

Hi,
I've had 3 different people accidentally set off the alarm by hitting the 'Arm Home' button and then opening the door and triggering the countdown when they left.  It appears that 'Arm Home' to the average person not used to the system means 'arm the house'.   Is it possible for me to change the button text to 'Arm Stay' and if so, how?

The alarm states are defined by Home Assistant, so they are out of my control.
Although I don't like the naming convention either (especially regarding armed_custom_bypass and pending states), we will have to live with it.
The labels on the buttons in the card (I assume you're talking about the Alarmo Card), are also internally in HA defined and translated to over 30 languages.
So a short answer to your question is: no, its not possible to have the arm buttons changed.
I think its easier to explain your family members how the alarm works and which button does what.
You could also opt for avoiding the "Armed Home" state and only use "Armed Away" and "Armed Night". IMO these labels are pretty easy to distinguish and in my personal use-case sufficient for my needs.

Thanks for the response.  The issue I have is with those who wouldn't be using the system regularly, i.e. cleaning service or contractors despite my explicit instructions for them to press 'Arm Away' when they're leaving.  I think I'll take your advice and just remove 'Arm Home' and keep 'Arm Night' since like you said, it is essentially the same thing.


python312Packages.peco: 0.0.30 -> 0.1.1

Changelog: https://github.com/IceBotYT/peco-outage-api/releases/tag/0.1.1
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

5 packages built:

home-assistant-component-tests.peco
python311Packages.peco
python311Packages.peco.dist
python312Packages.peco
python312Packages.peco.dist


APNs: Accept 1.6-format payloads in bouncer.

This is just enough of a quick fix to work with a stock Zulip 1.6
server.  We should really also make this robust to arbitrary input
from the remote Zulip server, even though it'll be a little tedious.

Can you add a test for this?  I would probably do something that just uses a copy of a 1.6 era payload and passes it into this function and compares it against a current payload.
Would this allow us to support APNS with a server running 1.6?  We can probably test using e.g. zulip.sagemath.org or chat.fhir.org.  If it does work, we should probably update the docs to say this works with Zulip 1.6.
I guess probably we should deploy to prod, verify, and then update the docs.

Yeah, I'll add a test but proper testing probably means also deploying to prod, or at least stage.

Yeah I think it's reasonable to test-deploy this before merging to master.  Would do staging if easy, but probably going to prod is fine.

(Test added.)

Test looks good.

Well, I deployed this in production, but then realized the way we'll know it's working is mostly a failure to see more exceptions.  I think we'll be pretty sure whether exceptions are still firing at this time tomorrow.

Merged after updating the docs, thanks @gnprice!


login in app using facebook

i am accessing in login page using horseman but unable to get the website image after login
var horseman = new Horseman({ phantomPath: phantomjs.path});
// login in zarpo using facebook
horseman
    .userAgent('Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0')
    .open('https://m.zarpo.com.br/customer/account/login/')
    .click('[class="fb_button"]')
    .waitForNextPage()
    .switchToTab(1)
    .type('input[name="email"]', 'email')
    .type('input[name="pass"]', 'password')
    .click('[name="login"]')
    .screenshot('abc.png')
    .switchToTab(0)
    .url()
    .then(function(url){
        console.log(url)
    })
    .reload()
    // .wait(5000)
    .screenshot('abc1.png')
    .close();

when redirecting the url on previous page here in abc1.png i got the same image as i click at first time

Please run with BLUEBIRID_DEBUG=1 and DEBUG='horseman*' set, then post the output log (you can redact your username and password first) and the screenshots generated.

here this is the output what i got from DEBUG='horseman*' BLUEBIRD_DEBUG=1 node index.js

horseman using PhantomJS from phantomjs-prebuilt module +0ms
horseman .setup() creating phantom instance 1 +216ms
horseman phantom created +187ms
horseman phantom version 2.1.1 +16ms
horseman page created +9ms
horseman phantomjs onLoadFinished triggered +9ms success NaN
horseman injected jQuery +17ms
horseman .userAgent() set +12ms Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0
horseman .open() +1ms https://m.zarpo.com.br/customer/account/login/
horseman phantomjs onLoadFinished triggered +8s success 1
horseman jQuery not injected - already exists on page +4ms
horseman .click() +4ms [class="fb_button"]
horseman page created +37ms
horseman .click() done +2ms
horseman .waitForNextPage() +0ms
horseman:verbose onConsoleMessage +3s
.d8888b.  888                       888
d88P  Y88b 888                       888
Y88b.      888                       888    Este é um recurso de navegador voltado
"Y888b.   888888  .d88b.  88888b.   888    para desenvolvedores. Se alguém disse
"Y88b. 888    d88""88b 888 "88b  888    para você copiar e colar algo aqui para
"888 888    888  888 888  888  Y8P    ativar um recurso do Facebook ou "invadir"
Y88b  d88P Y88b.  Y88..88P 888 d88P         a conta de outra pessoa, isso é uma fraude
"Y8888P"   "Y888  "Y88P"  88888P"   888    e você dará a ele acesso à sua conta.
888
888
888
Consulte https://www.facebook.com/selfxss para obter mais informações.
line: undefined in undefined 1
horseman phantomjs onLoadFinished triggered +1ms success 2
horseman injected jQuery +12ms
horseman .waitForNextPage() completed successfully +55ms
horseman .type() +1ms input[name="email"]<EMAIL_ADDRESS>undefined
horseman .keyboardEvent() +16ms keypress e null
horseman .keyboardEvent() +4ms keypress t null
horseman .keyboardEvent() +3ms keypress e null
horseman .keyboardEvent() +5ms keypress c null
horseman .keyboardEvent() +8ms keypress h null
horseman .keyboardEvent() +4ms keypress m null
horseman .keyboardEvent() +3ms keypress u null
horseman .keyboardEvent() +4ms keypress s null
horseman .keyboardEvent() +4ms keypress i null
horseman .keyboardEvent() +6ms keypress c null
horseman .keyboardEvent() +7ms keypress 8 null
horseman .keyboardEvent() +3ms keypress @ null
horseman .keyboardEvent() +4ms keypress g null
horseman .keyboardEvent() +5ms keypress m null
horseman .keyboardEvent() +4ms keypress a null
horseman .keyboardEvent() +3ms keypress i null
horseman .keyboardEvent() +4ms keypress l null
horseman .keyboardEvent() +6ms keypress . null
horseman .keyboardEvent() +5ms keypress c null
horseman .keyboardEvent() +5ms keypress o null
horseman .keyboardEvent() +3ms keypress m null
horseman .type() +1ms input[name="pass"] password undefined
horseman .keyboardEvent() +22ms keypress p null
horseman .keyboardEvent() +5ms keypress a null
horseman .keyboardEvent() +4ms keypress s null
horseman .keyboardEvent() +4ms keypress s null
horseman .keyboardEvent() +3ms keypress w null
horseman .keyboardEvent() +3ms keypress o null
horseman .keyboardEvent() +5ms keypress r null
horseman .keyboardEvent() +5ms keypress d null
horseman .click() +0ms [name="login"]
horseman .click() done +20ms
horseman .screenshot() +1ms abc.png
horseman .url() +32ms
https://m.zarpo.com.br/customer/account/login/
horseman .reload() +6ms
horseman .screenshot() +6ms abc1.png
horseman .close(). +98ms

Nothing is actually being typed into either the email or password boxes.
I think your selectors could be wrong. When I visited the site, the name of the email box was "step1[email]", not "email". If I were you I would double-check all the CSS selectors being used.

I think you are not understanding what  i have to do , actually i have to login in app using Facebook so these are steps which i have to follow:
1) click on Facebook button first(.click('[class="fb_button"]'))
2) then a new tab open i.e facebook tab
3) write the emailid their and password(.type('input[name="email"]', 'email')
.type('input[name="pass"]', 'password'))
4) click on the login button(.click('[name="login"]'))
5) then this page loads and redirect to tab 1, i want that when i
return to app page, then at that time, login in app is done.i.e screenshot after login

What does the screenshot of the other tab look like?
Also, it seems an error gets printed to the console after the first .waitForNextPage(), but it is not in English so I do not know what it is about.

the screenshot of other tab looks like this

but i think there is no issue for .waitForNextPage(), can you please help me out how i login with facebok in my app

Judging by the screenshot, it doesn't look like your email was actually typed in.

i write "username" only for demo, otherwise its having the email whatever i type

Try putting a .wait(500) or something between .click('[name="login"]') and .screenshot('abc.png') to give the page time to respond to the click.

i already try that but it's not working . if  i use .wait(500) then i got the same image in output .or if i use .wait(5000) then error comes

Unhandled rejection Error: jQuery injection failed
at /usr/lib/node_modules/node-horseman/lib/index.js:307:18
at PassThroughHandlerContext.finallyHandler (/usr/lib/node_modules/node-horseman/node_modules/bluebird/js/release/finally.js:56:23)
at PassThroughHandlerContext.tryCatcher (/usr/lib/node_modules/node-horseman/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/usr/lib/node_modules/node-horseman/node_modules/bluebird/js/release/promise.js:510:31)
at Promise._settlePromise (/usr/lib/node_modules/node-horseman/node_modules/bluebird/js/release/promise.js:567:18)
at Promise._settlePromise0 (/usr/lib/node_modules/node-horseman/node_modules/bluebird/js/release/promise.js:612:10)
at Promise._settlePromises (/usr/lib/node_modules/node-horseman/node_modules/bluebird/js/release/promise.js:691:18)
at Promise._fulfill (/usr/lib/node_modules/node-horseman/node_modules/bluebird/js/release/promise.js:636:18)
at /usr/lib/node_modules/node-horseman/node_modules/bluebird/js/release/nodeback.js:42:21
at /usr/lib/node_modules/node-horseman/node_modules/node-phantom-simple/node-phantom-simple.js:60:18
at IncomingMessage. (/usr/lib/node_modules/node-horseman/node_modules/node-phantom-simple/node-phantom-simple.js:645:9)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
this is because when we click on the facebook page to login then it's redirects to tab 1 and close automatically.


Memory sharing

Hi there. During training, I found memory cost often increases which may break the training procedure. In addition, I only have a PC of 4×12GB GPUs, I cannot train large models such as swinT even using samples_per_gpu=1. So can I use these 4 GPUs to share just 1 image when training? In other words, I assume using samples_per_gpu=1 on 4 GPUs leads to batch_size=4, but can I training on these GPUs using total batchsize=1? Thanks in advance.

Sorry, mmdetection does not support model parallelism yet.

Sorry, mmdetection does not support model parallelism yet.

OK, thanks.


README: add missing build dependency, apache2-dev

I need this additional package to build the software, please review
Signed-off-by: 林博仁<EMAIL_ADDRESS>

thanks!

Also the discount software has been included in software archive as least in Ubuntu 16.04, you may want to mention it in the README


⚠ Spryr has degraded performance

In 072f821, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4359 ms

Resolved: Spryr performance has improved in 3d5e1f7 after 8 minutes.


More improvements

#9 Fixed

@israelins85 I've added you as a contributor of the project, so you can push your changes directly.


Measure analyzer footprint in the wild

We want to collect measurements of analyzer's footprint (memory) in the wild. We want to know if there is a systemic issue when running and supporting the Atom plugin.
There's a lot we can do after we start measuring the number.  (correlate with size of project? uptime?) But let's get the number measured and reported first.
Once we're collecting the info, we can put it on the dashboard.

Might help with https://github.com/flutter/flutter/issues/4384

Given that we've not done anything with this in 16 months, is there any value in continuing to track this bug?

Since nobody responded, I'm going to take that as a no.


WIP: Aggregation methods for object-type array

[x] Tests added / passed
[x] Passes flake8 dask
[x] Fully documented, including docs/source/changelog.rst for all changes
and one of the docs/source/*-api.rst files for new API

This fixes #3133.
As the current assert_eq looks unable to take care

nan-included arrays
scalar
I added assert_nan_eq function in test_reductions.py, but there should be better ways to do this.

I appreciate any suggestions.

Looks good to me. Thanks @fujiisoup! Merging.


Revert "Add checks to 3d bubble problem. Add ClimaCoreVTK and ClimaCorePlots to Project"

Reverts CliMA/ClimaAtmos.jl#173

bors r+


Add some basic tests for Altair validator guide

Check a few high-level invariants from the validator guide.
~Found a minor typing issue when making the code executable, but no substantive changes.~
~Note: only 1 test now but plan to add a couple more tomorrow. Not a draft, but will also follow up w/ more soon~
edit: blocked on incorporating a new version of remerkleable with this: https://github.com/ethereum/eth2.0-specs/pull/2311#discussion_r610241135

The non-test-vector-output tests are under unittests folder. So tests/core/pyspec/eth2spec/test/altair/validator/test_validator.py should be moved to tests/core/pyspec/eth2spec/test/altair/unittests/validator/test_validator.py.

update: @hwwhww thanks for the feedback, that was very helpful! i've addressed most of it i believe and everything should work now -- the CI is still failing but should pass once we rebase onto a version of the pyspec w/ the new version of remerkleable that @protolambda is working on

@ralexstokes new remerkleable release with fix: https://pypi.org/project/remerkleable/0.1.19/


Compatibility with CentOS 8

Closes #367. Based on comment of @choonge 👍 ( https://github.com/dotless-de/vagrant-vbguest/issues/367#issuecomment-602494723 )
@fnordfish 🥇

@pedrofurtado Thank you very much for your work. There's a very long-standing discussion where I don't like Installers to upgrade kernels. I realize that with CentOS, that's especially annoying. But I still stand to this descension. However, since with CentOS there seems no other way, I'm starting give up a bit.
Here's my compromise. Let's make that "upgrade kernel" an opt-in flag on the Installer:
VagrantVbguest::Installers::CentOS.allow_kernel_upgrade = true

# or as a new machine specific option:

Vagrant.configure("2") do |config|
  vagrant_config.vm.define name do |config|
    config.box = "centos/8"
    config.vbguest.installer_options = { allow_kernel_upgrade: true }
  end
end

Another thing is rebooting via shutdown -r now, this way Vagrant has no chance to redo it's setup stuff (network configs and what not). Have you tried if you can trigger a reboot like this:
module VagrantVbguest
  module Installers
    class CentOS < RedHat
      def reboot_after_install?; true end
    end
  end
end

@fnordfish  Thanks for feedback! 🍻
Really cool that already exists a method called reboot_after_install, I did'nt realize 😆
I will make this change (and test here) related to reboot_after_install instead of use of direct command shutdown -r now.
But a doubt: Did you plan put this flag allow_kernel_upgrade in what file in the plugin? I will read the source code again, to make it more familiar to me. But feel free to change the code of this PR, so lets code together 🤝  👍

@fnordfish Bad news: it is necessary the direct command shutdown -r now. If i remove it, and override the method reboot_after_install? with true, it gives me following error log:
Copy iso file C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
mount: /mnt: WARNING: device write-protected, mounted read-only.
Installing Virtualbox Guest Additions 6.1.6 - guest version is unknown
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.6 Guest Additions for Linux........
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Kernel headers not found for target kernel
4.18.0-147.3.1.el8_1.x86_64. Please install them and execute
  /sbin/rcvboxadd setup
modprobe vboxguest failed
The log file /var/log/vboxadd-setup.log may contain further information.
An error occurred during installation of VirtualBox Guest Additions 6.1.6. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
Redirecting to /bin/systemctl start vboxadd.service
Job for vboxadd.service failed because the control process exited with error code.
See "systemctl status vboxadd.service" and "journalctl -xe" for details.
Unmounting Virtualbox Guest Additions ISO from: /mnt
Restarting VM to apply changes...
==> default: Attempting graceful shutdown of VM...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: No guest additions were detected on the base box for this VM! Guest
    default: additions are required for forwarded ports, shared folders, host only
    default: networking, and more. If SSH fails on this machine, please install
    default: the guest additions and repackage the box to continue.
    default:
    default: This is not an error message; everything may continue to work properly,
    default: in which case you may ignore this message.
==> default: Mounting shared folders...
    default: /vagrant => C:/Users/pfelipe/Desktop/repos/boa-vontade-play
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

The error output from the command was:

/sbin/mount.vboxsf: mounting failed with the error: No such device

@fnordfish But the PR, with the current code, works well 🏗

Using this PR, vagrant up et al works again with CentOS 8.
$ vboxmanage --version
6.1.6r137129
$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.15.4
BuildVersion:   19E287
$ vagrant --version
Vagrant 2.2.7
$ vagrant box list centos
centos/8 (virtualbox, 1905.1)

@pedrofurtado So, I've build on your work and came up with this: https://github.com/dotless-de/vagrant-vbguest/compare/pedrofurtado-patch-1
There's is now an opt-in switch config.vbguest.installer_options = { allow_kernel_upgrade: true } for CentOS only. This allows older CentOS boxes to use the same thing.
I also changed the place where the class decides if to do an kernel upgrade or "cross fingers and install dependencies" - I hope that doesn't break anything. It' looking good for me, but please double check.
I've realized why reboot_after_install? didn't work - the box needs an reboot right away after installing the new kernel. And there's no other way to do that right now.

@fnordfish Thank you so much for your help and code! I will test tomorrow your code, to confirm if everything works well. But, in the case of PR, the code should be like that below (for example), right?
Vagrant.configure('2') do |config|
  config.vagrant.plugins = ['vagrant-vbguest']
  config.vbguest.auto_update = true
  config.vbguest.installer_options = { allow_kernel_upgrade: true, reboot_timeout: 5000 }
  config.vm.box = 'centos/8'

  # I think this line turn optional, with the new code, right? But in tests i can keep it.
  config.vm.box_url = 'https://cloud.centos.org/centos/8/x86_64/images/CentOS-8-Vagrant-8.1.1911-20200113.3.x86_64.vagrant-virtualbox.box'
end

@pedrofurtado I will update the PR after the tests 🎉  and thanks again for fast feedback and help @fnordfish  🤝  !

@pedrofurtado So, I've build on your work and came up with this: https://github.com/dotless-de/vagrant-vbguest/compare/pedrofurtado-patch-1
There's is now an opt-in switch config.vbguest.installer_options = { allow_kernel_upgrade: true } for CentOS only. This allows older CentOS boxes to use the same thing.
I also changed the place where the class decides if to do an kernel upgrade or "cross fingers and install dependencies" - I hope that doesn't break anything. It' looking good for me, but please double check.
I've realized why reboot_after_install? didn't work - the box needs an reboot right away after installing the new kernel. And there's no other way to do that right now.

I think that is not complete yet. But we are almost there 🤝
I dont know why, the allow_kernel_upgrade is always false, even I define it as true in Vagrantfile. I tried your code but is didn't work.
Here is the code that I tested:
# https://github.com/dotless-de/vagrant-vbguest/issues/367
# https://github.com/dotless-de/vagrant-vbguest/pull/373
if defined?(VagrantVbguest)
  # arquivo 1
  module VagrantVbguest

    class Config < Vagrant.plugin("2", :config)

      module Attributes
        attr_accessor :auto_update, :auto_reboot, :no_install, :no_remote,
                      :installer, :installer_arguments, :installer_options,
                      :allow_downgrade,
                      :iso_path, :iso_upload_path, :iso_mount_point, :yes
      end

      class << self
        include Attributes

        def auto_update; @auto_update.nil? ? true  : @auto_update end
        def auto_reboot; @auto_reboot.nil? ? true  : @auto_reboot end
        def no_install;  @no_install.nil?  ? false : @no_install  end
        def no_remote;   @no_remote.nil?   ? false : @no_remote   end
        def installer_arguments; @installer_arguments.nil? ? '--nox11' : @installer_arguments end
        def yes; @yes.nil? ? true : @yes end

        def iso_path
          return nil if !@iso_path || @iso_path == :auto
          @iso_path
        end

        def allow_downgrade; @allow_downgrade.nil? ? false : @allow_downgrade end
      end

      include Attributes

      def auto_update; @auto_update.nil? ? self.class.auto_update : @auto_update end
      def auto_reboot; @auto_reboot.nil? ? self.class.auto_reboot : @auto_reboot end
      def no_install;  @no_install.nil?  ? self.class.no_install  : @no_install  end
      def no_remote;   @no_remote.nil?   ? self.class.no_remote   : @no_remote   end
      def installer_arguments; @installer_arguments.nil? ? self.class.installer_arguments : @installer_arguments end
      def yes; @yes.nil? ? self.class.yes : @yes end

      def iso_path
        return self.class.iso_path if !@iso_path || @iso_path == :auto
        @iso_path
      end

      def allow_downgrade; @allow_downgrade.nil? ? self.class.allow_downgrade : @allow_downgrade end

      # explicit hash, to get symbols in hash keys
      def to_hash
        {
          :installer => installer,
          :installer_arguments => installer_arguments,
          :installer_options => installer_options,
          :iso_path => iso_path,
          :iso_upload_path => iso_upload_path,
          :iso_mount_point => iso_mount_point,
          :auto_update => auto_update,
          :auto_reboot => auto_reboot,
          :no_install => no_install,
          :no_remote => no_remote,
          :yes => yes,
          :allow_downgrade => allow_downgrade
        }
      end

    end
  end

  # arquivo 2
  module VagrantVbguest
    module Installers
      class Error < Vagrant::Errors::VagrantError
        error_namespace "vagrant_vbguest.errors.installer"
      end

      # This is the base class all installers must inherit from
      # It defines the basic structure of an Installer and should
      # never be used directly
      class Base
        include VagrantVbguest::Helpers::VmCompatible

        # Tests whether this installer class is applicable to the
        # current environment. Usually, testing for a specific OS.
        # Subclasses must override this method and return `true` if
        # they wish to handle.
        #
        # This method will be called only when an Installer detection
        # is run. It is ignored, when passing an Installer class
        # directly as an config (`installer`) option.
        #
        # @param vm [Vagrant::VM]
        # @return [Boolean]
        def self.match?(vm)
          false
        end

        # A helper method to cache the result of {Vagrant::Guest::Base#distro_dispatch}
        # which speeds up Installer detection runs a lot,
        # when having lots of Linux based Installer classes
        # to check.
        #
        # @see {Vagrant::Guest::Linux#distro_dispatch}
        # @return [Symbol] One of `:debian`, `:ubuntu`, `:gentoo`, `:fedora`, `:redhat`, `:suse`, `:arch`, `:windows`, `:amazon`
        def self.distro(vm)
          @@distro ||= {}
          @@distro[ vm_id(vm) ] ||= distro_name vm
        end

        attr_reader :env, :vm, :options, :host

        def initialize(vm, options=nil)
          @vm = vm
          @env = vm.env
          @options = options

          @host = VagrantVbguest::Hosts::VirtualBox.new(vm, options)
        end

        # The absolute file path of the GuestAdditions iso file should
        # be uploaded into the guest.
        # Subclasses must override this method!
        #
        # @return [String]
        def tmp_path
        end

        # The mountpoint path
        # Subclasses shall override this method, if they need to mount the uploaded file!
        #
        # @return [String]
        def mount_point
        end

        # Handles the installation process.
        # All necessary steps for an installation must be defined here.
        # This includes uploading the iso into the box, mounting,
        # installing and cleaning up.
        # The path to the local iso file should be obtained by calling +iso_file+
        # Subclasses must override this method!
        #
        # @param opts [Hash] Optional options Hash wich meight get passed to {Vagrant::Communication::SSH#execute} and firends
        # @yield [type, data] Takes a Block like {Vagrant::Communication::Base#execute} for realtime output of the command being executed
        # @yieldparam [String] type Type of the output, `:stdout`, `:stderr`, etc.
        # @yieldparam [String] data Data for the given output.
        def install(opts=nil, &block)
        end

        # Handels the rebuild of allready running GuestAdditions
        # It may happen, that the guest has the correct GuestAdditions
        # version running, but not the kernel module is not running.
        # This method should perform a rebuild or try to reload the
        # kernel module _without_ the GuestAdditions iso file.
        # If there is no way of rebuidling or reloading the
        # GuestAdditions on a specific system, this method should left
        # empty.
        # Subclasses should override this method.
        #
        # @param opts [Hash] Optional options Hash wich meight get passed to {Vagrant::Communication::SSH#execute} and firends
        # @yield [type, data] Takes a Block like {Vagrant::Communication::Base#execute} for realtime output of the command being executed
        # @yieldparam [String] type Type of the output, `:stdout`, `:stderr`, etc.
        # @yieldparam [String] data Data for the given output.
        def rebuild(opts=nil, &block)
        end

        # Restarts the allready installed GuestAdditions
        # It may happen, that the guest has the correct GuestAdditions
        # version installed, but for some reason are not (yet) runnig.
        # This method should execute the GuestAdditions system specific
        # init script in order to start it manually.
        # If there is no way of doing this on a specific system,
        # this method should left empty.
        # Subclasses should override this method.
        #
        # @param opts [Hash] Optional options Hash wich meight get passed to {Vagrant::Communication::SSH#execute} and firends
        # @yield [type, data] Takes a Block like {Vagrant::Communication::Base#execute} for realtime output of the command being executed
        # @yieldparam [String] type Type of the output, `:stdout`, `:stderr`, etc.
        # @yieldparam [String] data Data for the given output.
        def start(opts=nil, &block)
        end

        # Determinates if the GuestAdditions kernel module is loaded.
        # This method tests if there is a working GuestAdditions
        # kernel module. If there is none, {#rebuild} is being called.
        # If there is no way of telling if there is a working
        # GuestAddition for a specific system, this method should
        # return `true`.
        # Subclasses should override this method.
        #
        # @return [Boolean] `true` if the kernel module is loaded (and thus seems to work), `false` otherwise.
        def running?(opts=nil, &block)
          true
        end

        # This manipulate the run-list of a the vbguest machine.
        #
        # @return [Boolean]
        def reboot_after_install?
          false
        end

        # Does the guest installer provide tooling to manually start or rebuild guest additions?
        #
        # @return [Boolean]
        def provides_vboxadd_tools?
          false
        end

        # Is the tooling to manually start or rebuild guest additions installed on the guest?
        #
        # @return [Boolean]
        def vboxadd_tools_available?
          raise NotImplementedError
        end

        # Determinates the GuestAdditions version installed on the
        # guest system.
        #
        # @param reload [Boolean] Whether to read the value again or use
        #                  the cached value form an earlier call.
        # @return [Gem::Version] The version code of the VirtualBox Guest Additions
        #                  available on the guest, or `nil` if none installed.
        def guest_version(reload=false)
          return @guest_version if @guest_version && !reload

          @guest_version =<EMAIL_ADDRESS>        end

        # Determinates the host (eg VirtualBox) version
        # @param reload [Boolean] Whether to read the value again or use
        #                  the cached value form an earlier call.
        # @return [Gem::Version] The version code of the host provider
        def host_version(reload=false)
          return @host_version if @host_version && !reload

          @host_version =<EMAIL_ADDRESS>        end

        # Determinates the version of the GuestAdditions installer in use
        #
        # @return [Gem::Version] The version code of the GuestAdditions installer
        def installer_version(path_to_installer)
          version = nil
          communicate.sudo("#{path_to_installer} --info", :error_check => false) do |type, data|
            v = VagrantVbguest::Version(data, /\AIdentification.*\s(\d+\.\d+.\d+)/i)
            version = v if v
          end
          version
        end

        def installer_options
          options[:installer_options] || {}
        end

        # Helper to yield a warning message to the user, that the installation
        # will start _now_.
        # The message includes the host and installer version strings.
        def yield_installation_warning(path_to_installer)
          @env.ui.warn I18n.t("vagrant_vbguest.installing#{@options[:force] ? '_forced' : ''}",
            :guest_version     => (guest_version || I18n.t("vagrant_vbguest.unknown")),
            :installer_version => installer_version(path_to_installer) || I18n.t("vagrant_vbguest.unknown"))
        end

        # Helper to yield a warning message to the user, that the installation
        # will be rebuild using the installed GuestAdditions.
        # The message includes the host and installer version strings.
        def yield_rebuild_warning
          @env.ui.warn I18n.t("vagrant_vbguest.rebuild#{@options[:force] ? '_forced' : ''}",
            :guest_version => guest_version(true),
            :host_version => @host.version)
        end

        # Helper to yield a warning message to the user in the event that the
        # installer returned a non-zero exit status. Because lack of a window
        # system will cause this result in VirtualBox 4.2.8+, we don't want to
        # kill the entire boot process, but we do want to make sure the user
        # knows there could be a problem. The message includles the installer
        # version.
        def yield_installation_error_warning(path_to_installer)
          @env.ui.warn I18n.t("vagrant_vbguest.install_error",
            :installer_version => installer_version(path_to_installer) || I18n.t("vagrant_vbguest.unknown"))
        end
        # alias to old method name (containing a typo) for backwards compatibility
        alias_method :yield_installation_waring, :yield_installation_error_warning

        def iso_file
          @host.additions_file
        end
        alias_method :additions_file, :iso_file

        # A helper method to handle the GuestAdditions iso file upload
        # into the guest box.
        # The file will uploaded to the location given by the +temp_path+ method.
        #
        # @example Default upload
        #    upload(file)
        #
        # @param file [String] Path of the file to upload to the +tmp_path*
        def upload(file)
          env.ui.info(I18n.t("vagrant_vbguest.start_copy_iso", :from => file, :to => tmp_path))
          communicate.upload(file, tmp_path)
        end

        # A helper method to delete the uploaded GuestAdditions iso file
        # from the guest box
        def cleanup
          unless options[:no_cleanup]
            @host.cleanup
            communicate.execute("test -f #{tmp_path} && rm #{tmp_path}", :error_check => false) do |type, data|
              env.ui.error(data.chomp, :prefix => false)
            end
          end
        end
      end
    end
  end

  # arquivo 3
  module VagrantVbguest
    module Installers
      class CentOS < RedHat

        def self.match?(vm)
          super && communicate_to(vm).test('test -f /etc/centos-release')
        end

        # Install missing deps and yield up to regular linux installation
        def install(opts=nil, &block)
          install_kernel_deps(opts, &block)
          super
        end

        def installer_options
          @installer_options ||= {
            allow_kernel_upgrade: false,
            reboot_timeout: 300
          }.merge!(super)
        end

        protected

        def upgrade_kernel?
          raise 'TEST HERE. IT WILL BE FALSE ... ' + (installer_options[:allow_kernel_upgrade] ? 'TRUE!' : 'FALSE!')
        end

        def install_kernel_deps(opts=nil, &block)
          unless has_kernel_devel_info?
            update_release_repos(opts, &block)
            install_kernel_devel(opts, &block)
          end
        end

        def has_kernel_devel_info?
          unless instance_variable_defined?(:@has_kernel_devel_info)
            @has_kernel_devel_info = communicate.test('yum info kernel-devel-`uname -r`', sudo: true)
          end
          @has_kernel_devel_info
        end

        def has_rel_repo?
          unless instance_variable_defined?(:@has_rel_repo)
            rel = release_version
            @has_rel_repo = communicate.test(upgrade_kernel? ? 'yum repolist' : "yum repolist --enablerepo=C#{rel}-base --enablerepo=C#{rel}-updates")
          end
          @has_rel_repo
        end

        def release_version
          unless instance_variable_defined?(:@release_version)
            @release_version = nil
            version_pattern = /(\d+\.\d+(\.\d+)?)/
            communicate.sudo('cat /etc/centos-release') do |type, data|
              v = VagrantVbguest::Version(data, version_pattern)
              @release_version = v if v
            end
          end
          @release_version
        end

        def update_release_repos(opts=nil, &block)
          communicate.sudo('yum install -y centos-release', opts, &block)
        end

        def install_kernel_devel(opts=nil, &block)
          if upgrade_kernel?
            communicate.sudo('yum update -y kernel', opts, &block)
            communicate.sudo('yum install -y kernel-devel', opts, &block)
            communicate.sudo('shutdown -r now', opts, &block)

            begin
              sleep 10
            end until @vm.communicate.ready?
          else
            rel = has_rel_repo? ? release_version : '*'
            cmd = "yum install -y kernel-devel-`uname -r` --enablerepo=C#{rel}-base --enablerepo=C#{rel}-updates"
            communicate.sudo(cmd, opts, &block)
          end
        end

        def dependencies
          if has_kernel_devel_info?
            # keep the original redhat dependencies
            super
          else
            # we should have installed kernel-devel-`uname -r` via install_kernel_devel
            ['gcc', 'binutils', 'make', 'perl', 'bzip2', 'elfutils-libelf-devel'].join(' ')
          end
        end
      end
    end
  end

end

Vagrant.configure('2') do |config|
  config.vagrant.plugins = ['vagrant-vbguest']
  config.vm.box = 'centos/8'
  config.vbguest.installer_options = { allow_kernel_upgrade: true, reboot_timeout: 5000 }
end

Weird, I just ran it locally (build a gem and installed that one, just to be sure) and your Vagrantfile worked.
I'm going to simply merge your PR, put my stuff on top and release a beta version.

0.24.0.beta1 is now available

@fnordfish Tests is coming 👷  with the beta version 🤝

@fnordfish It works like a charm! 🎉 🍻
Vagrantfiles for example:
CentOS 8: Done ✅
Vagrant.configure('2') do |config|
  config.vagrant.plugins = {"vagrant-vbguest" => {"version" => "0.24.0.beta1"}}
  config.vm.box = 'centos/8'
  config.vm.synced_folder '.', '/vagrant', type: 'virtualbox'
  config.vbguest.installer_options = { allow_kernel_upgrade: true, reboot_timeout: 5000 }
end

CentOS 7: Done ✅
Vagrant.configure('2') do |config|
  config.vagrant.plugins = {"vagrant-vbguest" => {"version" => "0.24.0.beta1"}}
  config.vm.box = 'centos/7'
  config.vm.synced_folder '.', '/vagrant', type: 'virtualbox'
  config.vbguest.installer_options = { allow_kernel_upgrade: true, reboot_timeout: 5000 }
end

@fnordfish Happy to see a oficial release of this great plugin, now working great with Centos 7 & 8 👍 🎖

Any instructions on how to test beta releases?
I still get Stderr from the command: Error: Unknown repo: 'C*-base' with the code below (full Vagrantfile at https://github.com/konstruktoid/ansible-role-hardening/blob/master/Vagrantfile), and it seems you can't install specific versions (e.g vagrant plugin install vagrant-vbguest==0.24.0.beta1 or vagrant plugin install vagrant-vbguest=0.24.0.beta1).
  config.vm.define "centos" do |centos|
    centos.vagrant.plugins = {"vagrant-vbguest" => {"version" => "0.24.0.beta1"}}
    centos.vm.box = "centos/8"
    centos.ssh.insert_key = true
    centos.vm.network "private_network", ip: "<IP_ADDRESS>"
    centos.vm.provider "virtualbox" do |c|
      c.default_nic_type = "82543GC"
    end
    centos.vm.hostname = "centos"
    centos.vm.provision "shell",
      inline: "dnf install -y epel-release && dnf install -y ansible python3"
    centos.vm.provision "ansible" do |a|
      a.verbose = "v"
      a.limit = "all"
      a.playbook = "tests/test.yml"
      a.extra_vars = {
        "sshd_admin_net" => "<IP_ADDRESS>/0",
        "sshd_allow_groups" => "vagrant sudo",
        "ansible_python_interpreter" => "/usr/bin/python3"
      }
    end
  end

$ git diff Vagrantfile
diff --git a/Vagrantfile b/Vagrantfile
index 037abdc..57e1165 100644
--- a/Vagrantfile
+++ b/Vagrantfile
@@ -1,4 +1,5 @@
 Vagrant.configure("2") do |config|
+  config.vagrant.plugins = {"vagrant-vbguest" => {"version" => "0.24.0.beta1"}}
   config.vm.provider "virtualbox" do |v|
     v.default_nic_type = "Am79C973"
   end

$ vagrant up centos
Bringing machine 'centos' up with 'virtualbox' provider...
==> centos: Importing base box 'centos/8'...
[...]
Complete!
Error: Unknown repo: 'C*-base'
==> centos: Checking for guest additions in VM...
    centos: No guest additions were detected on the base box for this VM! Guest
    centos: additions are required for forwarded ports, shared folders, host only
    centos: networking, and more. If SSH fails on this machine, please install
    centos: the guest additions and repackage the box to continue.
    centos:
    centos: This is not an error message; everything may continue to work properly,
    centos: in which case you may ignore this message.
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

yum install -y kernel-devel-`uname -r` --enablerepo=C*-base --enablerepo=C*-updates

Stdout from the command:

Stderr from the command:

Error: Unknown repo: 'C*-base'

You will need the  config.vbguest.installer_options = { allow_kernel_upgrade: true } stuff

Replacing with ~/.vagrant.d/gems/2.4.9/gems/vagrant-vbguest-0.23.0/lib/vagrant-vbguest/installers/centos.rb with https://raw.githubusercontent.com/pedrofurtado/vagrant-vbguest/1e4f6e36b20f6f8941d4df0556e9327232c0866d/lib/vagrant-vbguest/installers/centos.rb does work, but specifying the beta release as you've given example of above doesn't.
$ ls  ~/.vagrant.d/gems/2.4.9/gems/
micromachine-3.0.0  vagrant-scp-0.5.7  vagrant-vbguest-0.23.0  vagrant-vbguest-0.24.0.beta1
$ git diff Vagrantfile
diff --git a/Vagrantfile b/Vagrantfile
index 037abdc..8465be4 100644
--- a/Vagrantfile
+++ b/Vagrantfile
@@ -1,4 +1,6 @@
 Vagrant.configure("2") do |config|
+  config.vagrant.plugins = {"vagrant-vbguest" => {"version" => "0.24.0.beta1"}}
+  config.vbguest.installer_options = { allow_kernel_upgrade: true, reboot_timeout: 5000 }
   config.vm.provider "virtualbox" do |v|
     v.default_nic_type = "Am79C973"
   end
$ vagrant validate
There are errors in the configuration of this machine. Please fix
the following errors and try again:

VagrantVbguest::Config:
* The following settings shouldn't exist: installer_options

VagrantVbguest::Config:

The following settings shouldn't exist: installer_options

... suggest that the beta is not used, but the „old“ 0.23.0

@konstruktoid To avoid problems with cache of gems, remove the plugin vbguest globally from your machine and also locally removing the folder .vagrant in your machine.
I did this, and the version 0.24.0.beta1 works very well. 🤝
Anyway, let us know if everything worked well 👍

Exactly, so how do I enable the beta properly, and not by doing wget -O ~/.vagrant.d/gems/2.4.9/gems/vagrant-vbguest-0.23.0/lib/vagrant-vbguest/installers/centos.rb  https://raw.githubusercontent.com/pedrofurtado/vagrant-vbguesta/1e4f6e36b20f6f8941d4df0556e9327232c0866d/lib/vagrant-vbguest/installers/centos.rb?

Just to put it out there: vagrant plugin install vagrant-vbguest --plugin-version=0.24.0.beta1

Thanks @fnordfish, that did it.
$ vagrant plugin install vagrant-vbguest --plugin-version=0.24.0.beta1
Installing the 'vagrant-vbguest --version '0.24.0.beta1'' plugin. This can take a few minutes...
Fetching: vagrant-vbguest-0.24.0.beta1.gem (100%)
Successfully uninstalled vagrant-vbguest-0.23.0
Installed the plugin 'vagrant-vbguest (0.24.0.beta1)'!

Seems to be working just fine for multiple people and centos versions. released as 0.24.0
Happy vagrant plugin update vagrant-vbguest


Use Python 2.6 compatibile format() strings

Fixes #2.

Coverage remained the same at 92.62% when pulling 194ee678fb76d642f82a8b9a55e228ea652eff51 on mkoistinen-feature/fix_format_for_py26 into 802f4a87c446ca74def842d7c4a8f499aafc066b on develop.

Coverage decreased (-92.62%) to 0.0% when pulling eaf29e31c841fb9747ef09ee61c71293a89a7c80 on mkoistinen-feature/fix_format_for_py26 into 802f4a87c446ca74def842d7c4a8f499aafc066b on develop.

Coverage decreased (-10.66%) to 81.97% when pulling eaf29e31c841fb9747ef09ee61c71293a89a7c80 on mkoistinen-feature/fix_format_for_py26 into 802f4a87c446ca74def842d7c4a8f499aafc066b on develop.


Add TLE&RE status in test judge

Summary

This PR adds TLE&RE status in test judge (examples are as follows).
This code is a tentative implementation and only works with docker version.

I would like to discuss the pros and cons of this PR.
In addition, I would like to discuss how to implement this function.

example1 (TLE):
$ acd abc100/abc100_a/ test
Running test on Container mode

Case 1: AC
Time: 183.3928ms

Case 2: TLE
Time: 3.0005138s

Case 3: TLE
Time: 3.00023s

example2 (RE):
$ acd abc100/abc100_a/ test
Running test on Container mode

Case 1: RE
Input:
5 4

Expected:
Yay!

Actually:

Exit with: 2
Time: 97.095ms

Log:
panic: runtime error: integer divide by zero

goroutine 1 [running]:
main.main()
        /src/main.go:14 +0x21b

Case 2: RE
Input:
8 8

Expected:
Yay!

Actually:

Exit with: 2
Time: 92.107ms

Log:
panic: runtime error: integer divide by zero

goroutine 1 [running]:
main.main()
        /src/main.go:14 +0x21b

Case 3: RE
Input:
11 4

Expected:
:(

Actually:

Exit with: 2
Time: 99.3583ms

Log:
panic: runtime error: integer divide by zero

goroutine 1 [running]:
main.main()
        /src/main.go:14 +0x21b

@m0ch1m0ch1  Thank you! I think it's very good!
Native mode is not used, at least not by me. I think it's a useless feature.
I prefer AC-Deck to focus on running in containers, so I don't mind if it doesn't support native mode.
I don't mind if it doesn't support native mode.


Store credentials when app is deleted and reinstalled

Hello, right now a large issue I'm facing is that when you delete the app and reinstall it, the credentials are all gone.
Is there a way to migrate this so that the credentials are stored in the keychain and not deleted?

Had a request along these lines previously: https://github.com/flutter-institute/webauthn/issues/20
Technically the private keys are still around in the Secure Storage on the local device (because there's no way I could find to do clean up on uninstall), but we lose the metadata (rpid, username, etc) that was stored in the local app storage in SQL Lite.
I've considered moving the metadata into secure storage, as well as some basic key lookup info, but it felt like abusing the system a little bit.
What's the use case that you're trying to build around here?

My use case would be when the user deletes the app and reinstalls it, they are still able to log into the service as normal. Otherwise, each time they deleted and reinstalled they'd need to keep getting new credentials and there could be hundreds etc for one device theoretically. In a dream world it would be as sleek as passing persistent: true to the credential safe or something.

Any thoughts here?

Hey just following up here @killermonk

Happy to sponsor this feature request as well


in mac os, keybase does not show up under /volumes when accessing it via the finder

Using mac os 10.15, I noticed that the keybase volume does not show up even after typing the terminal command to install the keybase fs. I changed the permissions on the folder after going to the folder by hand by typing /volumes in the go dialogue in the finder itself. I then tried to open the volume but got the error that I did not have permissions to open. My permission were indeed set to custom. I set them to read and right via the inspector, but now I don't see the public, private and teams folder I should be seeing. In fact I did an ls in the directory, and there is indeed nothing there.
Thanks.
my log id: 6657f35f5d9fa73af496431c

It seems like your kernel extension still isn't installed or enabled for some reason.  If you're the same user from reddit, did you run the keybase install command suggested there, or find the button in settings?
If the former, I wonder if adding "helper" might fix it for you, like:
keybase install -c helper,fuse,kbfs,mountdir,redirector

I am the same user, yes. Restarting the computer did fix it, I had to
restart anyway due to some other issues like a keyboard that
malfunctioned during class, all is working now, almost. The almost part
I think I might be able to troubleshoot on my own as I think I know what
might have happened.
Can the command given be put somewhere in the docs on the keybase fs
install section for mac os? That would be good as well in case the
reddit thread goes for some odd reason.
Thanks.

Ok great.  Yeah we have an ongoing project to revamp our docs, so hopefully we can get this in there.  Thanks for your patience!


Contributing link is outdated in the HACKING file

nice catch, thanks!

released in 1.5.9, thanks!


HOSTEDCP-1560: Create AWS STS Role for the hypershift/hcp cli

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #HOSTEDCP-1560
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/retest-required

/test e2e-azure

I think a delete role command would also be nice?

/cherry-pick release-4.16


Traceback (most recent call last):

Activating virtual environment...
Dependencies already installed, skipping installation.
Skipping .env copying
Starting the bot...
Traceback (most recent call last):
File "C:\Users\x\Desktop\Cats Bot\main.py", line 5, in
from bot.utils import logger
File "C:\Users\x\Desktop\Cats Bot\bot\utils_init_.py", line 2, in
from . import launcher
File "C:\Users\x\Desktop\Cats Bot\bot\utils\launcher.py", line 9, in
from bot.core.tapper import run_tapper
File "C:\Users\x\Desktop\Cats Bot\bot\core\tapper.py", line 22, in
from ..utils.tg_manager.TGSession import TGSession
ModuleNotFoundError: No module named 'bot.utils.tg_manager.TGSession'
done
PLEASE EDIT .ENV FILE
Press any key to continue . . .

Use python 3.10

I am using python 3.11 and have same problem.

I am using version 3.11

Please, check README, you need to use only python 3.10 for this bot


feat(containers): Ensure users cannot create privileged containers via the API

close #4065

tests:

[ ] without RBAC

[x] Cannot create the stack below using a non-admin user
[x] Can create the stack below using an admin user
[ ] Cannot create a privileged container via API using a non-admin user
[ ] Can create a privileged container via API using an admin user

[ ] with RBAC

[ ] Cannot create the stack using a non-admin user
[ ] Can create the stack below using an admin user
[ ] Can create the stack below using an endpoint-admin user
[ ] Cannot create a privileged container via API using a non-admin user
[ ] Can create a privileged container via API using an admin user
[ ] Can create a privileged container via API using an endpoint-admin user

version: '2'

services:
  web:
    image: nginx:alpine
    privileged: true


Bug: Issue Not being able to use the Motion Sensor on C100

I am having issues with the C100 camera not being able to get the sensor Entity to appear. I have deleted the cameras and re-added the camera and still the same with no entities. I have disabled and reenabled the motion detector on the camera and still no luck.
Camera

Device Model: C100
FW: [e.g. 1.0.17 Build 201112 Rel.29622n (4555)

Using stream component
yes
Camera has all attributes filled out properly in developer tools
yes
HASS Environment
Running On a VM
It was working perfectly but now I cant make them show up.

Follow instructions in troubleshooting and see other duplicates of this.


authkit-js refresh token requests 400

From the timeout
https://github.com/workos/authkit-js/blob/cdef77b7c38479897d7ebc7e446c7d47dc69d9a4/src/create-client.ts#L159

hey @paulfalgout , could you give a bit more context? (how to reproduce, what type of environment, etc.).

Having this same issue... Looks like this only happens when devMode={false}

@paulfalgout we need to do a better job with that error.
For security reasons, we rely on passing the refresh token in an http only cookie to the WorkOS API in production.
What’s likely happening is that you haven’t yet set up a custom domain, so some browsers are blocking your WorkOS session cookie as a 3rd party cookie (this is the reason we use the localstorage in development — we want to avoid that 3rd party cookie blocking).

And then modify apiHostname in the createClientOptions like await createClient(clientId, { apiHostname: authenticationapi.com }); ?

Facing the same issue in testing environments when devMode is false. Look at this snap, the refresh token goes empty in the api request.

I have not setup custom domain for my environment but I have allowed 3rd party cookies for api.workos.com. Can you provide any solution for this @cmatheson @southgate

Confirming this is still an issue even when setting a custom domain for us.
I received the response below on 10/21:
There’s an issue at the intersection of session cookies, custom domains, and staging environments that means the session cookie doesn’t get set.

The fix for this is likely some weeks out. If you run this in a Production environment, though, it should behave as expected.

Seeing this also. It's an issue on production that we don't see in development. Going to try older versions.

hey everyone, i'm going to close this issue, but i wanted to clarify what is happening and what is expected:

It is more secure to use the session cookie instead of a refresh token in localStorage. For this reason, we depend on a cookie being set when devMode={false}.
The session cookie is only set when a custom domain is enabled. Additionally, you should specify the custom host domain in AuthKitProvider (<AuthKitProvider apiHostname={auth.foo-corp.com} />)
Because we don't currently offer custom domains for our staging environments, you should use devMode={true} when developing against your staging environment (this is automatically set when you're developing locally).


react/jsx-runtime should be an external

The bundle includes both react/jsx-runtime, production and development.
vite v4.3.9 building for production...
✓ 17 modules transformed.
dist/style.css                               5.71 kB │ gzip: 1.75 kB
dist/vite-component-library-template.es.js  21.88 kB │ gzip: 6.64 kB
dist/vite-component-library-template.umd.js  14.54 kB │ gzip: 5.77 kB

[vite:dts] Start generate declaration files...
✓ built in 1.86s
[vite:dts] Declaration files built in 1437ms.

Both should be excluded from bundle:
rollupOptions: {
  external: ['react', 'react/jsx-runtime', 'react-dom', 'tailwindcss'],
  output: {
    globals: {
      react: 'React',
      'react/jsx-runtime': 'react/jsx-runtime',
      'react-dom': 'ReactDOM',
      tailwindcss: 'tailwindcss',
    },
  },
},

Resulting in:
vite v4.3.9 building for production...
✓ 9 modules transformed.
dist/style.css                              5.71 kB │ gzip: 1.75 kB
dist/vite-component-library-template.es.js  0.87 kB │ gzip: 0.50 kB
dist/vite-component-library-template.umd.js  1.05 kB │ gzip: 0.62 kB

[vite:dts] Start generate declaration files...
✓ built in 1.63s
[vite:dts] Declaration files built in 1368ms.
 ``

Hey! thanks for opening this and for demonstrating interest in the repo!
Could you explain a bit more why this is not needed in the bundle? Please attach any url, blog post, or news that explain it, as I was not able to find any 🙂🙏🏻

@IgnacioNMiranda as I was looking for examples, how to properly bundle a react component library I found this repo. Since I was wondering, why my setup was including the jsx-runtime, I checked the dist output of your repo and it was also including the runtime.
The library package has specified react & react-dom as peerDependencies, which includes the JSX runtime. As I understand, a library bundle is meant to be consumed by another project which needs react installed as dependency, so it solves the required peerDependencies. When the library component is consumed by the project, it receives/uses the JSX runtime from the projects dependencis. That's why there is no need to include the runtime in the component library.
"peerDependencies": {
  "react": "18.2.0",
  "react-dom": "18.2.0"
},

I found this related issue, explaining that the cause is that vite is using the automatic JSX runtime (not classic). And this stackoverflow thread, providing the same information and fix.
I added the fix, run build, then pnpm pack in the vite-component-library-template root and installed the package as local dependency inside another react project. I used import { AtButton } from 'vite-component-library-template' and run dev/build without any problems.

Thanks @jrson83! I've done some more research and this seems logical to me. Thanks for having taken a look into it!

@IgnacioNMiranda great, if you experience any problems, please let me know.


[Example] R-Hello-World

See https://drive.google.com/drive/u/1/folders/1WMba3yWHJ8a2ywLb-y4oEV6frF1DBEzS

Needs a bit of tidying up:
https://docs.bacalhau.org/examples/workload-onboarding/r-hello-world/


Setup proper error handling

Here are some things I need to do for this issue.

[x] Fix dealing with null parent fields, like the Sydney data
[x] Deal with unwrap() sections.

Used new methods using ? to validate API data which return Some or None. Also able to remove unwrap() from MQTT publishing. However, because I used the ? methods, I needed to use Copy, Clone in the struct definitions, which do not work on Strings. Wind direction is a string so that field has needed to be removed.