Make password optional

I'm very new to both Swift and Vapor, but I'm trying my best here so sorry about any possible mistake 🙏.
I tried to add a test for this scenario but I don't know enough yet 😅.
This fixes #195 . I don't have a password on my local environment for the MySQL user and I was unable to run migrations, this is why I think this change should be addressed.
Thank you for your time and framework.

I suspect this will need to be fixed in MySQL-Kit first before being added to Fluent. I think passing an empty string is not the same as passing nothing, but it depends on how MySQL works. I'm going to hook @gwynne in here as she's done a ton of work on MySQL auth recently

Had to test this to be sure, but it turns out that no additional effort at the MySQLKit or MySQLNIO layer is required - in MySQL, "no password" and "the password is an empty string" are the same thing.
I will post a review with further comments.

On further investigation, the difference between 5.7 and 8.0 turns out to be due to 8.0 using caching_sha2_password as the default instead of mysql_native_password. The bug here is actually at the MySQLNIO layer, which incorrectly encodes a complete auth response for an empty password "", when the correct behavior for the mysql_native_password plugin is to encode no auth response at all in that case. The existing behavior is already correct for the caching SHA-2 plugin.
As such, this PR is unnecessary; I am closing it out in favor of the one I'm about to open against MySQLNIO. @Lloople Your effort and contributions are very much appreciated, and my closing this PR out is in no way intended to discourage you! Please don't hesitate to open new issues and PRs in the future; they are always welcome- this one definitely served to point me in the right direction to fix the problem!

Thank you very much for your time and for such an explanation about the issue! 😍  I'll try my best to continue helping with anything I can


Does this work with Space Exploration?

Hi, same question here. Is there any plan to update the project for SE ?

no plan for SE. if anyone work on it, i can merge it


feat(omnilock): support omnilock

This PR will support Omnilock in lumos

[x] declare API
[x] writing some demo with the declared types
[ ] request for comment
[ ] documentation
[ ] test
[ ] implement
[ ] release & merge

Close the PR due to inactivity


[Typing Issue] EventAttributes interface should require value to be string not any

https://github.com/aws/aws-amplify/blob/d5d27d622f1643251d42274333bbf1c6427404ec/packages/aws-amplify/lib/Analytics/types/Analytics.d.ts#L12-L14
https://github.com/aws/aws-amplify/blob/d5d27d622f1643251d42274333bbf1c6427404ec/packages/aws-amplify/lib/Analytics/Analytics.d.ts#L56
let attributes = { 'stringKey': { another: customObject } }
Analytics.record('customEventName', attributes)

attributes matches the [key: string]: any;
However, this fails to record the event with an error stating that the value of 'stringKey' is not a string, but the typing would lead you to believe it did not have to be.
Should probably be:
export interface EventAttributes {
     [key: string]: string;
}

Hi @gnomishperson I will take a look on your pr.
Thank you!


Import Error: Cannot import name 'get_dist_info' from mmcv.runner.utils

Traceback (most recent call last):
File "tools/train.py", line 9, in
from mmdet.apis import (get_root_logger, init_dist, set_random_seed,train_detector)
File "/home/hdc/anaconda3/envs/mmdetection/lib/python3.6/site-packages/mmdet/apis/init.py", line 2, in
from .inference import (inference_detector, init_detector, show_result,
File "/home/hdc/anaconda3/envs/mmdetection/lib/python3.6/site-packages/mmdet/apis/inference.py", line 11, in
from mmdet.core import get_classes
File "/home/hdc/anaconda3/envs/mmdetection/lib/python3.6/site-packages/mmdet/core/init.py", line 3, in
from .evaluation import *  # noqa: F401, F403
File "/home/hdc/anaconda3/envs/mmdetection/lib/python3.6/site-packages/mmdet/core/evaluation/init.py", line 5, in
from .eval_hooks import (CocoDistEvalmAPHook, CocoDistEvalRecallHook,
File "/home/hdc/anaconda3/envs/mmdetection/lib/python3.6/site-packages/mmdet/core/evaluation/eval_hooks.py", line 13, in
from mmdet import datasets
File "/home/hdc/anaconda3/envs/mmdetection/lib/python3.6/site-packages/mmdet/datasets/init.py", line 6, in
from .loader import DistributedGroupSampler, GroupSampler, build_dataloader
File "/home/hdc/anaconda3/envs/mmdetection/lib/python3.6/site-packages/mmdet/datasets/loader/init.py", line 1, in
from .build_loader import build_dataloader
File "/home/hdc/anaconda3/envs/mmdetection/lib/python3.6/site-packages/mmdet/datasets/loader/build_loader.py", line 8, in
from .sampler import DistributedGroupSampler, DistributedSampler, GroupSampler
File "/home/hdc/anaconda3/envs/mmdetection/lib/python3.6/site-packages/mmdet/datasets/loader/sampler.py", line 6, in
from mmcv.runner.utils import get_dist_info
ImportError: cannot import name 'get_dist_info'
##########################################
I have already update mmcv to the latest version(0.2.15), and mmdetection is the latest version too.
Still this error, anyone know why and how to fix? Thanks very much!

https://github.com/open-mmlab/mmdetection/issues/1811


Codegen + fragmants

Environment

Operating System: Darwin
Node Version:     v16.17.0
Nuxt Version:     3.7.4
CLI Version:      3.9.0
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      extends, nitro
Runtime Modules:  -
Build Modules:    -

Describe the bug
When codegen is disabled fragments can't be found. The fragments are working fine when the codegen is turned on.
Here is the error message: "Unknown fragment "CartFragment"."
 'graphql-client': {
    codegen: false
  },

Expected behaviour
Fragments should work regardless of whether code generation is on or off.

Is anyone else having this issue? 🤔

I have a similar error, but due to the fact that the fragments and queries are in the Layer that connects to nuxt.config.ts in extends key.

Yes, same here!
@Diizzayy do you know a solution?

the same issue


Set page titles & meta tags with react-helmet

From 2.20.23 slack feedback:

can you use something like react-helmet to set the page titles and meta tags for social previews,
Home should be set to blogContract.title which is going to be fetched async so stub that out for now and hardcode something as a standin


Image classifier Error in python3.6

metrics = custommodel.evaluate(data)   "/Users/dhruvkumarpatel/Desktop/ImageClassification.app/Contents/Resources/lib/python3.6/site-packages/turicreate/toolkits/image_classifier/image_classifier.py", line 802, in evaluate evaluation_result['sorted_labels'] = hclusterSort(vectors, l2Dist)[0]['name'].split("|")
  File "/Users/dhruvkumarpatel/Desktop/ImageClassification.app/Contents/Resources/lib/python3.6/site-packages/turicreate/toolkits/image_classifier/image_classifier.py", line 731, in hclusterSort     vecs = vectors[:]
 TypeError: 'map' object is not subscriptable

@abhishekpratapa - I think you should fix this one. Let's fix this for the next release.
You could just change vectors to list(vector), but if it works, it's probably better to use copy.copy. Also would be great to have a unit test to cover this bug.

I am deploying a solution and can you tell me which turicreate version I should use meanwhile which doesn't have this bug?

 turicreate==5.2.1 works fine for me.

I ended up going into the image_classifier.py source code found in the error and turning vecs into a list with "list()" before hand and all worked. This was in turicreate 5.5.


template idea : basic server with express

IP as QR code using qrcode-terminal as suggested by @R4ph3rd in #12 and #11
mount a static folder on /public
add nodemon and live reloading of the static folder

will have look into hapi because express is struggling[1] to adopt http2.
[1]: I'm assuming due to its large userbase


use jmeter to test go2sky performance, error like this

go2sky-gRPC2021/09/14 03:07:36 send segment error EOF
go2sky-gRPC2021/09/14 03:07:36 send closing error rpc error: code = Internal desc = stream terminated by RST_STREAM with error code: PROTOCOL_ERROR
go2sky-gRPC2021/09/14 03:07:42 send segment error EOF
go2sky-gRPC2021/09/14 03:07:42 send closing error rpc error: code = Unknown desc = unexpected HTTP status code received from server: 413 (Request Entity Too Large); transport: received unexpected content-type "text/html"
go2sky-gRPC2021/09/14 03:07:44 send segment error EOF
go2sky-gRPC2021/09/14 03:07:44 send closing error rpc error: code = Unknown desc = unexpected HTTP status code received from server: 413 (Request Entity Too Large); transport: received unexpected content-type "text/html"
go2sky-gRPC2021/09/14 03:07:46 send segment error EOF
go2sky-gRPC2021/09/14 03:07:46 send closing error rpc error: code = Unknown desc = unexpected HTTP status code received from server: 413 (Request Entity Too Large); transport: received unexpected content-type "text/html"
go2sky-gRPC2021/09/14 03:07:48 send segment error EOF
go2sky-gRPC2021/09/14 03:07:48 send closing error rpc error: code = Unknown desc = unexpected HTTP status code received from server: 413 (Request Entity Too Large); transport: received unexpected content-type "text/html"
go2sky-gRPC2021/09/14 03:07:50 send segment error EOF
go2sky-gRPC2021/09/14 03:07:50 send closing error rpc error: code = Unknown desc = unexpected HTTP status code received from server: 413 (Request Entity Too Large); transport: received unexpected content-type "text/html"
go2sky-gRPC2021/09/14 03:07:52 send segment error EOF
go2sky-gRPC2021/09/14 03:07:52 send closing error rpc error: code = Unknown desc = unexpected HTTP status code received from server: 413 (Request Entity Too Large); transport: received unexpected content-type "text/html"
go2sky-gRPC2021/09/14 03:07:54 send segment error EOF
go2sky-gRPC2021/09/14 03:07:54 send closing error rpc error: code = Unknown desc = unexpected HTTP status code received from server: 413 (Request Entity Too Large); transport: received unexpected content-type "text/html"
go2sky-gRPC2021/09/14 03:07:57 send segment error EOF
go2sky-gRPC2021/09/14 03:07:57 send closing error rpc error: code = Unknown desc = unexpected HTTP status code received from server: 413 (Request Entity Too Large); transport: received unexpected content-type "text/html"

This seems like your OAP server doesn't have enough resources to support the traffic. Maybe because of storage, cluster size, etc.


Added a option to disable debug agent

This PR also change the default address of metrics to localhost:9567
Closes #325

@davies Apparently juicefs mount doesn't know about this parameter so no way to set it from /etc/fstab

Fixed in d749382


[stable/nginx-ingress] Add an ability to provide custom nginx template and dhparam

@mgoodness: have you had a chance to look at this? Due to the breaking change in 1.8 that I go into detail in https://github.com/kubernetes/ingress-nginx/issues/1622, it would be really handy to override the nginx template in order to allow ELBs to offload TLS, at least until there's a proper solution from the ingress-nginx folks.

I figured custom template have already made it in. I'm closing this now. Again sorry for the delay. Please open a new PR for dhparam if you like. Thanks.


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit 6e322ad:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-02-22-06-52-26 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-02-22-06-52-26

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add multi language support

To-Do List

Language Translation

Consider using packages that can read English labels and translate them to other languages like Spanish, German, etc.
Alternatively, use GPT for quick translation. I've got a Laravel command ready for this.

Label Updates

Update all labels and output strings to use Laravel's __ or trans function.

Language Selector

Add a dropdown for language selection in the top navigation.
Automatically detect the browser's default language.

Reference

Laravel Localization Documentation

Concur. If someone has a use case for multi-language, like they want to run their own instance of this app, then perhaps they'd be willing to put in the work to make it a thing.  Or, they could fork the work and add that in.
We don't have a use case, so our time is likely spent on scratching our own itches.

Along these lines, an accessibility review would probably be a more immediate use case.
Does Laravel have a lot of core accessibility built into the views by default?

It does not have anything in the core - but we could be more conscious about accessibility when creating new templates moving forward.


Add class (non instance) properties support

Coverage remained the same at 50.0% when pulling 54c2b9cefe0e6adef31352fee6b8c34ffb19d0ee on feature/support-class-properties into cc4a025e6d255d049e4100e239f41b26ebdc5a32 on master.

Coverage remained the same at 50.0% when pulling a71404187ebded9f39ffc0347601250d679ab020 on feature/support-class-properties into cc4a025e6d255d049e4100e239f41b26ebdc5a32 on master.

Coverage remained the same at 50.0% when pulling 6553eca85d862aa22075ec20d2f81dc521584a5f on feature/support-class-properties into cc4a025e6d255d049e4100e239f41b26ebdc5a32 on master.


the best player for now

i hope to add more future in this project soon

Thanks, it was meant to be a simple project to share on codepen, but I'll see if I can get some new features added to it.


org settings: Fix real time sync.

Commits for real-time syncing:
org settings: Refactor the discard changes function.
This extract the logic of resetting the value of a single property element
at a time so that we can reuse this for real-time-syncing.
org settings: Handle dependent sub settings manually.
This replaces the previous logic of triggering change() event.
(Also, when we trigger the change() event whole path for detecting
changes in a subsection are triggered which isn't good.)
org settings: Add real-time syncing for property changes.
Minor bug found during changes:
org settings: Fix discard changes for realm_create_stream_permission.
On discarding changes made for realm_create_stream_permission always
"by_admin_user_with_custom_time" get selected because
create_stream_by_admins_only isn't a valid page_param.
Small refactor:
org settings: Use disable_sub_setting_onchange for dependent checkbox.
This makes use of settings_ui.disable_sub_setting_onchange for
handling dependent id_realm_disallow_disposable_email_addresses
checkbox when id_realm_restricted_to_domain is changed.
I want to know how does this below commit sounds to you because when I found that this function should be extended I can only figure out the cases for success_continuation. So my point is rather than using this function for custom success function I think one will directly make a call using channel.post to prevent complexity in providing arguments.
settings_ui: Revert extension for success callback in do_settings_change
This reverts success callback extension for do_settings_change function
because it seems it is better to make the request directly rather
than calling do_settings_change.
And hence error callback extension is also removed  for the same
reason, but a error_continuation is added to do additional tasks when
errors happened.

Another thing: for small bugs like above is this okay to send them to next PR or should I create a new PR for every bug.

This looks great, merged, thanks @shubhamdhama!
This approach of doing a branch that fixes several bugs in a page is the way to go.  You want one commit per independent fix (as you've done), but doing separate PRs often leads to your changes merge-conflicting with each other.


Naive aggregation strategy

Add the "naive" attestation aggregation strategy to phase 0.

add mechanism for selecting which proposers are supposed to aggregate and broadcast
add wrapper object AggregateAndProof for broadcasting aggregates that includes a "proof" that the aggregator was selected to aggregate
add notes and validation conditions about aggregate and attestation subnet gossip channels
rename some topics and vars to reflect new functionality
add to and modify some FAQ

addressed your comments @hwwhww !


Relayer submits actual proof data to smart contracts

This PR gets the relayer to send over the proofs as needed. They likely don't all work, but still valuable to start with this and merge it in. Parachain merkle proofs are still missing/todo as in the other PR.

@philipstanislaus merging this in now but plz review for any comments/audit concerns


Testing Swag Bot for Gridder

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Fancy baselines hyperparameter attribute errors

Provide a general description of the issue
Description
Traceback:
I0426 04:49:02.559688<PHONE_NUMBER>24000 submission_runner.py:251] After Initializing model: RAM USED (GB) 8.337543168
I0426 04:49:02.559894<PHONE_NUMBER>24000 submission_runner.py:252] Initializing optimizer.
Traceback (most recent call last):
  File "submission_runner.py", line 629, in <module>
    app.run(main)
  File "/usr/local/lib/python3.8/dist-packages/absl/app.py", line 312, in run
    _run_main(main, args)
  File "/usr/local/lib/python3.8/dist-packages/absl/app.py", line 258, in _run_main
    sys.exit(main(argv))
  File "submission_runner.py", line 602, in main
    score = score_submission_on_workload(workload,
  File "submission_runner.py", line 537, in score_submission_on_workload
    timing, metrics = train_once(workload, global_batch_size,
  File "submission_runner.py", line 254, in train_once
    optimizer_state = init_optimizer_state(workload,
  File "/algorithmic-efficiency/baselines/lamb/jax/submission.py", line 52, in init_optimizer_state
    b1=hyperparameters.beta1,
AttributeError: 'Hyperparameters' object has no attribute 'beta1'

Steps to Reproduce
Run
python submission_runner.py \
        --framework=jax  \
        --workload=criteo1tb \
        --submission_path=baselines/lamb/jax/submission.py  \
        --tuning_search_space=baselines/lamb/tuning_search_space.json  \
        --data_dir=/home/${USER}/data \
        --num_tuning_trials=1  \
        --experiment_dir=/home/$USER/experiments  \
        --experiment_name=lamb

Source or Possible Fix
The hyper parameter names in algorithmic-efficiency/baselines/lamb/tuning_search_space.json don't match the ones in the basesines/lamb/jax/submission.py.

jax baselines should be fixed by https://github.com/mlcommons/algorithmic-efficiency/pull/380 and https://github.com/mlcommons/algorithmic-efficiency/pull/382


Allow selecting multiple scenes or scripts in "Quick Open ..." for opening

The ability to select multiple scenes or scripts in "Quick Open Scene" and "Quick Open Script" would help increase productivity.
Use cases:

Open all your scripts at once
Open all the scripts in a folder (since the scripts are sorted by name, this is easy)
Open just 2-3 scripts, without using the menu 2-3 times

Anyone wants to give it a spin?
https://github.com/godotengine/godot/blob/master/tools/editor/quick_open.cpp


Fixed #31073 -- Prevented CheckboxInput.get_context() from mutating attrs.

Ticket 31073
I chose modifying the SplitArrayWidget over the CheckboxInput to keep the potential negative impact to a minimum, but would appreciate guidance if that was the correct choice. I'm unsure because no other widget modifies the passed-in attrs dictionary, so avoiding that in CheckboxInput may be preferable instead.

@PeteAndersen Thanks for this patch :+1: IMO we should change CheckboxInput.get_context() because other multi-widgets are also affected, e.g.  MultipleHiddenInput or MultiWidget. CheckboxInput shouldn't mutate arguments
diff --git a/django/forms/widgets.py b/django/forms/widgets.py
index 6fe220bea7..5dd074673a 100644
--- a/django/forms/widgets.py
+++ b/django/forms/widgets.py
@@ -522,8 +522,7 @@ class CheckboxInput(Input):

     def get_context(self, name, value, attrs):
         if self.check_test(value):
-            if attrs is None:
-                attrs = {}
+            attrs = {**(attrs or {})}
             attrs['checked'] = True
         return super().get_context(name, value, attrs)

Could even go for:
attrs = {**(attrs or {}), 'checked': True}

Thanks for the comments, code has been updated. If you would like, I can also add a unit test to all widgets to ensure they don't mutate attrs.

I am unable to recreate the reported test failure and it appears to be unrelated to my changes - when running the failed test, it never calls into get_context() of CheckboxInput

@PeteAndersen Thanks for updates :+1: Welcome aboard :boat:
I pushed minor edits and partly restored test_checkbox_get_context_attrs() (because it tests reported issue). I was able to reproduce this issue with added tests (also on a test project).


Revert "[SMALLFIX] ignore JournalShutdownIntegerationTest for now"

Reverts Alluxio/alluxio#7331

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/19834/
Test FAILed.


Aaron Plocharczyk created his project update 1 post

This includes a trinket, a short narration, and an updated milestones list.

The second commit added my old milestones to the post.


Error When Trying To Fetch Webhooks List

Issue summary
Error when trying to fetch current webhooks.
Expected behavior
It should have returned a JSON response containing a list of webhooks
Actual behavior
we get this error:
Fatal error: Uncaught TypeError: Argument 1 passed to Shopify\Utils::loadCurrentSession() must be of the type array, null given, called in /www/doc/www.example.com/www/script/index.php on line 45 and defined in /www/doc/www.example.com/www/script/vendor/shopify/shopify-api/src/Utils.php:158 Stack trace: #0 /www/doc/www.example.com/www/script/index.php(45): Shopify\Utils::loadCurrentSession(NULL, NULL, NULL) #1 {main} thrown in /www/doc/www.example.com/www/script/vendor/shopify/shopify-api/src/Utils.php on line 158
Steps to reproduce the problem

Include the library:

require("vendor/autoload.php");

use Shopify\Auth\FileSessionStorage;
use Shopify\Auth\Session;
use Shopify\Rest\Admin2022_10\Customer;
use Shopify\Rest\Admin2022_10\Webhookv2;
use Shopify\Utils;

Initialize:

Shopify\Context::initialize(
    'apiKey',
    'apiSecretKey',
    'read_analytics, read_assigned_fulfillment_orders, read_customers, read_draft_orders, read_merchant_managed_fulfillment_orders, read_order_edits, read_orders, read_script_tags, read_third_party_fulfillment_orders',
    'https://sozialstar.de/script/',
    new FileSessionStorage('/tmp/php_sessions'),
    '2022-10',
);

Request webhook list:

$this->test_session = Utils::loadCurrentSession(
    $requestHeaders,
    $requestCookies,
    $isOnline
);
Webhookv2::webhooks(
    $this->test_session, // Session
    [], // Url Ids
    [], // Params
);

P.S.
You can view it live here.

$requestHeaders = array('api_version'=>'2022-10', 'X-Shopify-Access-Token'=>'mytokenhere'); $requestCookies = array(); $isOnline = true;
Abose is the value of the 3 variables and I still get the following error:
Fatal error: Uncaught Shopify\Exception\MissingArgumentException: Missing Authorization key in headers array in /www/doc/www.sozialstar.de/www/script/vendor/shopify/shopify-api/src/Auth/OAuth.php:226 Stack trace: #0 /www/doc/www.sozialstar.de/www/script/vendor/shopify/shopify-api/src/Utils.php(160): Shopify\Auth\OAuth::getCurrentSessionId(Array, Array, true) #1 /www/doc/www.sozialstar.de/www/script/shopifytest.php(29): Shopify\Utils::loadCurrentSession(Array, Array, true) #2 {main} thrown in /www/doc/www.sozialstar.de/www/script/vendor/shopify/shopify-api/src/Auth/OAuth.php on line 226

So the error changed, what's happening now is that you have access without valid authorization.
In that case, you can accept the request, get the $request->query("shop"), and redirect the user to your login page with the shop in the URL.
If your customer already has the app installed, the login page will generate another valid authorization and redirect the customer to the app's page. If the customer doesn't have the app installed, an installation request must pop-up.

This is not a public app, its my own private admin custom app for my own shopify store for my personal use. I don't want to redirect a user, I just want to subscribe to new webhook orders/create. By the way, thank you for your help so far I appreciate it. Could you tell me how I would proceed in this scenario?

This is not a public app, its my own private admin custom app for my own shopify store for my personal use. I don't want to redirect a user, I just want to subscribe to new webhook orders/create. By the way, thank you for your help so far I appreciate it. Could you tell me how I would proceed in this scenario?


PSA: Fixed configure.py boolean option handling in 64386aad49c73fee69e199c7b4894b648c204736

Fix broken boolean options

This commit allows calling
```
configure.py --opt1 --no-opt2
```
to enable opt1 and disable op2 from their defaults.

Previous boolean handling was utterly broken.

This does not yet solve the "symlink retriggering world compilation"-problem yet as reading through the symlink breaks libstdc++ detection ...

@giuseros note this may change the way you enable apl (just use --alp from now on)


Documentation structure

Revise the structure of the documentation. What should be in the about section et cetera.

This was addressed in the version submitted for review to Bioinformatics.


Not work with php 8

Hi there,
Before asking question, I'd like to thank you for making very useful plugin for Laravel community.
I've just installed your package but it does not seems to work with my current php8.2 and laravel 10.
Here is the full errors from my composer:
 Problem 1
    - ashallendesign/laravel-executor[v0.1.0, ..., v0.3.0, v1.0.0, ..., v1.1.0, v2.0.0, ..., v2.1.1]
    require php ^7.2 -> your php version (8.2.6) does not satisfy that requirement.

    - ashallendesign/laravel-executor v2.2.0 requires illuminate/container ^6.0|^7.0|^8.0
    -> found illuminate/container[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27]
     but these were not loaded, likely because it conflicts with another require.

    - Root composer.json requires ashallendesign/laravel-executor *
    -> satisfiable by ashallendesign/laravel-executor[v0.1.0, ..., v0.3.0, v1.0.0, v1.0.1, v1.1.0,
     v2.0.0, v2.1.0, v2.1.1, v2.2.0].

Can you please help?
Thank you,
Quy

Hey @quyle92! Thanks for the kind words 😄
Unfortunately, I've not been keeping this package up to date because it never gained any traction. So I don't really have any plans to update this to work with the latest versions of PHP or Laravel, sorry.
I hope you manage to find an alternative solution though for your project! 😄


refer to "using directive" as appropriate

Address incorrect use of "using statement" to refer to a "using directive".

@mrlacey : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@gewarren : Thanks for your contribution! The author(s) have been notified to review your proposed change.


dart:io websocket reconnect no response

In my case no response，my code below：
I want to know the correct way，thx
 _connect() {
    WebSocket.connect(Address.SOCKET_BASE_URL_RELEASE).then((webSocket) {
      _webSocket = webSocket;
      _webSocket.add(getHistoryDealParam());
      _webSocket.add(getRealTimeDeal());
      _webSocket.listen(onData, onError: (e) {
        reConnect();
      }, onDone: () {
        reConnect();
      }, cancelOnError: true);
    }, onError: (e) {
      reConnect();
    });
  }

 void reConnect() async {
    await Future.delayed(Duration(milliseconds: 2000));
//    _connect();
    if (_webSocket != null && _webSocket.readyState == WebSocket.open) {
      _webSocket.add(getHistoryDealParam());
      _webSocket.add(getRealTimeDeal());
    } else {
      _connect();
    }
  }

This is a question better suited for StackOverflow, since there doesn’t seem to be anything wrong with Flutter itself, but related to the implementation. Closing, as this is not an issue report. See https://flutter.dev/community for support options.
If you disagree, feel free to comment and I will reopen the issue right away.


[BUG] Seedfarmer 4.0.4 doesn't cache information on AWS if it was provided as environment variables

Describe the bug
The following error occurs in case if module that uses environment variable was deleted and enviroment variable was unset
seedfarmer.errors.seedfarmer_errors.InvalidManifestError: The environment variable (TEST_VARIABLE) is not available
To Reproduce
Steps to reproduce the behavior:

Have project with the only one module that uses environment variable TEST_VARIABLE
export TEST_VARIABLE="some_value"
Create inital deployment with seedfarmer apply
unset TEST_VARIABLE and delete the module from yaml
Do seedfarmer apply again
See the error descibed above

Expected behavior
It was expected that seedfarmer will remember the values of yaml parameters on AWS if they were provided via environment variables

In agreement here, not sure this behaviour should be changed unless there's some compelling use case that warrants it.


disableStrictSSL with http

If you use both http protocol and disableStrictSSL:true, it will cause a request error.
The disableStrictSSL option should be applied only in the case of https

This is a small optimization

Hi @rxxy  !
As hot fix, you can add this to your codegen config
const http = require('http')

let config = {
   requestOptions: {
      agent: new http.Agent({
         rejectUnauthorized: false,
      }),
   }
}

@rxxy also I suggest you to use path (require("path")) for resolving paths for output and templates

@rxxy should be fixed in 12.0.1


Hang on world save phase with the fusion crafter placed in world?

I've been having this strange issue with my world getting stuck at the world save phase each time after quitting, which forced me to close the game from task manager. I've asked around and people said it may of been FTB Backups causing it. Yesterday all of a sudden the world started to save as normal after a few seconds, and let me return to main screen, but it turns out the fusion crafter and the packagers connected to the ME were straight up removed from the world. Could this be related?
PackagedDraconic <IP_ADDRESS>
PackagedAuto <IP_ADDRESS>
AE2 11.7.0
FML 40.2.0
(debug uploaded as compressed as it's around 40 megs in size, weirdly enough)
debug-2.log.gz
I can provide further information if requested.

Coming with an update, i went on a test world and tested the exact same setup, hooked to a ME and requesting random craft through the fusion crafter, attempting to quit to menu will make the client hang and sit at the saving world phase. Breaking the fusion crafter and the packagers assembly will let me quit to main menu without a hang.
video of bug reproduction: check description for time stamp https://youtu.be/NZyDXSH5JQs
debug log of latest instance
debug-2.log.gz

Should be fixed


chore(deps): update module github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper to v1.37.0

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.36.0 -> v1.37.0

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.37.0
Compare Source
Features

allow deep folders in stack config path (#851) (fd252ef)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

:tada: This issue has been resolved in version 1.2.10 :tada:
The release is available on:

GitHub release
v1.2.10

Your semantic-release bot :package::rocket:


Atmos gas selling needs to be nerfed again

Description

I didn't realise it was still possible, but I just experienced a round where atmos made cargo literally millionaires.
Screenshots

Repeat 100x of me saying it needs removing.

Atmos players when frezon gets nerfed/removed so now they can quit after setting up distro (They have nothing left to do anymore)

i think this is the result of a PR being merged a long while ago that raised the frezon price again, 0.3/mol was a good figure that worked and that i and notafet agreed on; making frezon sell for 0 would be overkill

besides bankrolling cargo atmos has absolutely 0 gameplay if frezon and n2o were made worthless atmos techs would just cryo after setting up distro

yes so lower frezon/n2o to 0.3/0.1 $/mol respectively, this should make it balanced

there are not a lot such professional atmos players, so cargo don't have millions every round, which i think is quite okay have you discussed that with other maints?

no thats why i made an issue, so it can be discussed. there is SOME sort of issue, just idk the best way to solve it

I have 0 atmos experience so someone else chime in, but wouldn't adding gas bounties "fix" both departments on this? It could give more variety on what atmos needs to do, while letting cargo still make money from them without it feeling like an exploit.

I have 0 atmos experience so someone else chime in, but wouldn't adding gas bounties "fix" both departments on this? It could give more variety on what atmos needs to do, while letting cargo still make money from them without it feeling like an exploit.

Ok bounties for certain gasses sound hella cool

an idea for a gas bounty is 28 mols of plasma, referencing the trivial ss13 traitor objective

I can't believe I killed atmos. Sorry to all the atmosians out there. I should have hid our true power.


Linux OS.window_maximized again give only false

Godot versions:
3.2.3 - 3.3.1rc
OS/device including version:
Linux 5.9.16-1-MANJARO, GeForce GTX 960M
Issue description:
When I use OS.window_maximized  = true - window set maximized (it's ok), but when I try return to normal windows size  OS.window_maximized  = false  - nothing happens.
Ps: OS.window_maximized never changes on Linux. It eq false, but on Windows all work.
PsPs: Sorry about my English.
test_bug.zip

confirm PopOS 21.04
# doesn't toggles back to normal size
OS.window_maximized = !OS.window_maximized


Creative Commons License

I'm picking the Attribution 4.0 International by Creative Commons, in Markdown Form thanks to this repo.
Related to: https://github.com/tecnoyucas/meta/issues/12

Is this CC-BY?

@schoettler yes! Why?


Include compiled file with npm package

Ok, lot's of stuff here. Decided to switch to react-scripts for the demo app, cleaned up a lot of outdated dependencies, and now include a bundled .js file with the npm package which should solve a lot of outstanding issue.
It would be good to get a sanity check on this before merging. Any thoughts? I'm going to go ahead and publish v1.0.8 on npm so we can see if it resolves issues like #21.

I tried using version 1.0.8, but it seems to be completely broken.
Even with the simplest possible usage
import React from "react";
import PropTypes from "prop-types";
import ImageUploader from 'react-images-upload';

export default class ImageFileWidget extends PureComponent {
  constructor(props) {
    super(props);
  }

  onChange = fileDataURLs => {
  };

  render() {
    return (
      <div>
        <ImageUploader
          withIcon
          onChange={this.onChange}/>
      </div>
    );
  }
}

I get this error when the component is loaded

Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

Ok, I actually tested v1.0.95 in a create-react-app project and it works fine now. This should resolve #85.

I'll give the new version a try on Monday

@JakeHartnell the packing problems appear to be fixed in v1.0.95


chore: bump reset IAM to use TF 1.4.x

Current constraint requires >= 1.4.4

The LINT errors are pre-existing and not critical, now surfacing due to https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/pull/1484


test_inference.py is broken

Test_inference.py is giving me inappropriate results for models, like 5.8 when ooba's ppl tester gives me 4.9. Not sure what would be the cause of that.

Are you sure it's exactly the same test data?

It's also wikitext but it might be different since ooba uses an arrow file and not parquet.

Wikitext has a number of different splits, and it also matters how much of the dataset you use and how you format it. Not sure how TGW does it, but it's probably not the same defaults.

I'd have to somehow convert it to parquet to know for sure ig.

I still don't know which datasets ooba uses. They're supposed to be wikitext2-v1 1.0.0 but the format and size are completely mismatched with the ones on HF.

Ok, trying 5 rows (as in exl1) at equivalent context length instead of the two defaults finally gave me some good results.

Ok, no, this script just doesn't want to work with me. Completely different results than ooba and I can't even get the same results as the one from the first repo. Too confusing.

I'm a little unclear on what you're trying to do.
It does appear that there was an error setting the alpha value from the command line. Apparently I renamed the config entry at one point and forgot to update model_init.init() accordingly. It's been fixed with the latest commit. Thanks for noticing that. :+1:
If it helps with the comparisons to ExLlamaV1, I wrote a script for it that implements the exact same tokenization and perplexity test logic as V2:
from model import ExLlama, ExLlamaCache, ExLlamaConfig
from tokenizer import ExLlamaTokenizer
from generator import ExLlamaGenerator

import argparse, os, math, glob
import pandas, fastparquet
import torch
import torch.nn.functional as F

import sys
import json

parser = argparse.ArgumentParser(description = "Test inference on model")
parser.add_argument("-m", "--model_dir", type = str, help = "Model directory", default = "")
parser.add_argument("-ed", "--eval_dataset", type = str, help = "Perplexity evaluation dataset (.parquet file)")
parser.add_argument("-er", "--eval_rows", type = int, default = 128, help = "Number of rows to apply from dataset")
parser.add_argument("-el", "--eval_length", type = int, default = 2048, help = "Max no. tokens per sample")

args = parser.parse_args()

# Directory containing model, tokenizer, generator

model_directory =  args.model_dir

# Locate files we need within that directory

tokenizer_path = os.path.join(model_directory, "tokenizer.model")
model_config_path = os.path.join(model_directory, "config.json")
st_pattern = os.path.join(model_directory, "*.safetensors")
model_path = glob.glob(st_pattern)[0]

# Create config, model, tokenizer and generator

config = ExLlamaConfig(model_config_path)               # create config from config.json
config.model_path = model_path                          # supply path to model weights file

model = ExLlama(config)                                 # create ExLlama instance and load the weights
tokenizer = ExLlamaTokenizer(tokenizer_path)            # create tokenizer from tokenizer model file

cache = ExLlamaCache(model)                             # create cache for inference

def get_tokens(num_rows, length, filename, tokenizer):

    min_tokens = num_rows * length

    df = pandas.read_parquet(filename, engine = "fastparquet")
    df['concatenated'] = df.apply(lambda r: ' '.join([str(v) for v in r.values]), axis = 1)

    all_tokens = torch.empty((1,0), dtype = torch.long)

    for _, row in df['concatenated'].items():
        tokens = tokenizer.encode(row)
        all_tokens = torch.cat((all_tokens, tokens), dim = -1)
        if all_tokens.shape[-1] >= min_tokens: break

    if all_tokens.shape[-1] < min_tokens:
        print(f" ** Warning: Not enough sample data in {filename}")

    all_tokens = all_tokens.flatten()[:min_tokens]
    all_tokens = all_tokens.view((num_rows, length))

    num_print_tokens = 50
    data_sample = all_tokens[0, :num_print_tokens]
    print(f" -- First {num_print_tokens} tokens of dataset:")
    print(f"    {repr(tokenizer.decode(data_sample))}")
    data_sample = all_tokens[-1, -num_print_tokens:]
    print(f" -- Last {num_print_tokens} tokens of dataset:")
    print(f"    {repr(tokenizer.decode(data_sample))}")

    return all_tokens

# Test perplexity

if args.eval_dataset is not None:

    with torch.inference_mode():

        eval_dataset = args.eval_dataset
        eval_rows = args.eval_rows
        eval_length = args.eval_length

        print(f" -- Running perplexity test")
        print(f" -- Dataset: {eval_dataset}")
        print(f" -- Tokenizing eval data, {eval_rows} rows x {eval_length} tokens...")

        eval_tokens = get_tokens(eval_rows, eval_length, eval_dataset, tokenizer)

        print(f" -- Inference", end = "")
        sys.stdout.flush()

        logprob_sum = 0.0
        logprob_count = 0

        for i in range(eval_tokens.shape[0]):

            if i % 10 == 0: print(".", end = "")
            sys.stdout.flush()

            input_ids = eval_tokens[i:i+1, :]
            cache.current_seq_len = 0
            logits = model.forward(input_ids, cache, last_id_only = False)

            target_ids = input_ids[:, 1:].to("cuda:0")
            logits = logits[:, :-1, :].to("cuda:0")

            log_probs = F.log_softmax(logits, dim=-1)
            token_log_probs = log_probs.gather(-1, target_ids.unsqueeze(-1)).squeeze(-1)
            logprob_sum += token_log_probs.sum().item()
            logprob_count += target_ids.numel()

        print()

        mean_log_prob = logprob_sum / logprob_count
        perplexity = math.exp(-mean_log_prob)

        print(f" -- Evaluation perplexity: {perplexity:.4f}")

        xx = 0

I've confirmed that it gives the same results for the same model and dataset.

Oh. Thank you. I'll check it out.

Something like:
python test_inference.py -m <model> -ed <dataset> -l 6144 -er 16 -el 6144 -ra 1.7

-l sets the max sequence length for the model. Only relevant for the ppl test because it determines the size of the RoPE embedding table.
-ed is the evaluation dataset
-er is the number of rows to use from the dataset
-el is the length of each row
-ra sets the alpha value

Now I get a "TypeError: q_attn_forward_1(): incompatible function arguments. The following argument types are supported:
1. (arg0: int, arg1: torch.Tensor, arg2: int, arg3: int, arg4: int, arg5: torch.Tensor, arg6: torch.Tensor, arg7: torch.Tensor, arg8: torch.Tensor, arg9: torch.Tensor, arg10: torch.Tensor) -> None" error with the script.

You probably have the prebuilt wheel installed? Cause I don't know what else would cause that. In any case probably best to stick with the JIT version and not running setup.py if you're cloning the repo.

Got it running but nope, no, used your script and got 40ppl when it should be 4.5.
Two different datasets, same thing. Even increased alpha to make sure it's not it.

Could you explain exactly what you're doing to get this behavior?

Exactly the command you gave with one of my merges and wikitext. It works perfectly on ooba so I dunno.

Does the model maybe require every sequence to begin in <s>? This seems to be a feature of some finetunes, that they either must see a BOS token, or they must not see a BOS token, in order to produce meaningful output.

Maybe? But why would ooba do it okay, then? Or for that matter the exl1 script if it's a GPTQ version of it?

Closing some stale issues.


Blockchain network (by default) setting gets overwritten

Altme version: 2.18.2 (555)
Device: iPhone12
I changed the network setting to "Tezos Ghostnet". However, after changing account without closing Altme the setting gets overwritten and I will be asked again to change the network to "Tezos Gostnet". I'm not sure yet what exactly causes the overwrite.

Are you using an enterprise profile or the default one @dansan566 ?

2.18.2  is a beta which has some blocking issues and we will publish a release candidate this afternoon.

@hawkbee1 default

2.18.5


CI not creating correct launcher version numbers for release candidates

In particular this line
FILEVERSION=$(echo ${{ env.NORTHSTAR_VERSION }} | tr '.' ',' | tr -d '[:alpha:]')

has the issue that it incorrectly generates version numbers for release candidates.
As an example v1.6.4-rc2  gets turned into 1,6,4-2 which during compilation turns into 1,6,2.
As a solution, we should just strip -rcX from version number if exists.

Aight, this is an issue together with the version gating introduced in v1.6.0 as it create a version number that is counted as invalid on master server. In particular a rc1 on a new minor version, like v1.7.0-rc1 turns into R2Northstar/1.7.-1 for the User-Agent, which fails on master server here.
So we cannot make working release candidates for versions ending in .0 until fixed :c


no relife tab opens when I open osu,

I launch osu and relife run as admin thing appears as normal, but no HWID spoofer panel comes up, Osu just launches normally so i deleted and reinstalled everything, still having the same problem. !

same

I had this problem before and the way I fixed it was by going to windows run type %localappdata% and search file relife_profiles.ini, open with notepad, delete all text and copy-paste this:
[custom]
m_164532E4570B.90B7C207E207.184C02EE2C0D.FFBD27B4FA16.
h_61EBAE0E72CD
u_9687F090-A68C-403B-8627-E5CD663346CF
s_bancho
save and run osu, click random to generate a new random IDs and it's done :D

I had this problem before and the way I fixed it was by going to windows run type %localappdata% and search file relife_profiles.ini, open with notepad, delete all text and copy-paste this: [custom] m_164532E4570B.90B7C207E207.184C02EE2C0D.FFBD27B4FA16. h_61EBAE0E72CD u_9687F090-A68C-403B-8627-E5CD663346CF s_bancho
save and run osu, click random to generate a new random IDs and it's done :D

just delet the file


OOM Exception after project load

See #820. I updated to VS2015 Update 2. Now I eventually receive a OOM error after opening the project, even if I just open a project and let VS sit for ~5 mins.
System.OutOfMemoryException was unhandled Message: An unhandled exception of type 'System.OutOfMemoryException' occurred in Microsoft.NodejsTools.Analysis.dll
Event log:
Log Name:      Application
Source:        .NET Runtime
Date:          04/13/16 09:47:32
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxxx
Description:
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
   at Microsoft.NodejsTools.Analysis.AnalysisSetDetails.AnalysisHashSet.EnsureSize(Int32)
   at Microsoft.NodejsTools.Analysis.AnalysisSetDetails.AnalysisHashSet.CheckGrow()
   at Microsoft.NodejsTools.Analysis.AnalysisSetDetails.AnalysisHashSet.AddOne(Microsoft.NodejsTools.Analysis.AnalysisProxy)
   at Microsoft.NodejsTools.Analysis.AnalysisSetDetails.AnalysisHashSet.Union(System.Collections.Generic.IEnumerable`1<Microsoft.NodejsTools.Analysis.AnalysisProxy>, Boolean ByRef)
   at Microsoft.NodejsTools.Analysis.AnalysisSet.Create(System.Collections.Generic.IEnumerable`1<Microsoft.NodejsTools.Analysis.AnalysisProxy>)
   at Microsoft.NodejsTools.Analysis.Analyzer.DependentKeyValue.AddTypes(Microsoft.NodejsTools.Analysis.ProjectEntry, Microsoft.NodejsTools.Analysis.JsAnalyzer, Microsoft.NodejsTools.Analysis.IAnalysisSet, Microsoft.NodejsTools.Analysis.IAnalysisSet, Boolean)
   at Microsoft.NodejsTools.Analysis.Values.ExpandoValue.SetIndex(Microsoft.NodejsTools.Parsing.Node, Microsoft.NodejsTools.Analysis.AnalysisUnit, Microsoft.NodejsTools.Analysis.IAnalysisSet, Microsoft.NodejsTools.Analysis.IAnalysisSet)
   at Microsoft.NodejsTools.Analysis.AnalysisSetExtensions.SetIndex(Microsoft.NodejsTools.Analysis.IAnalysisSet, Microsoft.NodejsTools.Parsing.Node, Microsoft.NodejsTools.Analysis.AnalysisUnit, Microsoft.NodejsTools.Analysis.IAnalysisSet, Microsoft.NodejsTools.Analysis.IAnalysisSet)
   at Microsoft.NodejsTools.Analysis.Analyzer.ExpressionEvaluator.AssignTo(Microsoft.NodejsTools.Parsing.Node, Microsoft.NodejsTools.Parsing.Expression, Microsoft.NodejsTools.Analysis.IAnalysisSet)
   at Microsoft.NodejsTools.Analysis.Analyzer.ExpressionEvaluator.EvaluateBinary(Microsoft.NodejsTools.Analysis.Analyzer.ExpressionEvaluator, Microsoft.NodejsTools.Parsing.Node)
   at Microsoft.NodejsTools.Analysis.Analyzer.ExpressionEvaluator.EvaluateWorker(Microsoft.NodejsTools.Parsing.Node)
   at Microsoft.NodejsTools.Analysis.Analyzer.DDG.Walk(Microsoft.NodejsTools.Parsing.ExpressionStatement)
   at Microsoft.NodejsTools.Parsing.ExpressionStatement.Walk(Microsoft.NodejsTools.Parsing.AstVisitor)
   at Microsoft.NodejsTools.Analysis.Analyzer.DDG.Walk(Microsoft.NodejsTools.Parsing.Block)
   at Microsoft.NodejsTools.Parsing.Block.Walk(Microsoft.NodejsTools.Parsing.AstVisitor)
   at Microsoft.NodejsTools.Analysis.Analyzer.DDG.Walk(Microsoft.NodejsTools.Parsing.IfNode)
   at Microsoft.NodejsTools.Parsing.IfNode.Walk(Microsoft.NodejsTools.Parsing.AstVisitor)
   at Microsoft.NodejsTools.Analysis.Analyzer.DDG.Walk(Microsoft.NodejsTools.Parsing.Block)
   at Microsoft.NodejsTools.Parsing.Block.Walk(Microsoft.NodejsTools.Parsing.AstVisitor)
   at Microsoft.NodejsTools.Analysis.Analyzer.FunctionAnalysisUnit.AnalyzeWorker(Microsoft.NodejsTools.Analysis.Analyzer.DDG, System.Threading.CancellationToken)
   at Microsoft.NodejsTools.Analysis.Analyzer.DDG.Analyze(Microsoft.NodejsTools.Analysis.Deque`1<Microsoft.NodejsTools.Analysis.AnalysisUnit>, System.Threading.CancellationToken)
   at Microsoft.NodejsTools.Analysis.JsAnalyzer.AnalyzeQueuedEntries(System.Threading.CancellationToken)
   at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer+AnalysisQueue+GroupAnalysis.Analyze(System.Threading.CancellationToken)
   at Microsoft.NodejsTools.Intellisense.VsProjectAnalyzer+AnalysisQueue.Worker(System.Object)
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart(System.Object)

Microsoft Visual Studio Professional 2015
Version 14.0.25123.00 Update 2
Microsoft .NET Framework
Version 4.6.01055

Node.js Tools   1.1.31117.00
Node.js Tools - Profiling   1.1.31117.00

Think I'll pull the source and check it out.

Thanks for the report. It looks like there may be a memory leak in the analysis engine.
Here are the Build instructions of NTVS. If you are working on NTVS 1.1, make sure to checkout the v1.1.x branch for testing. Master has the NTVS 1.2 Alpha code now. Please let me know if you run into any problems getting setup.
I'd start by trying to reproduce the issue with a local build. Then, using the the [Visual Studio Diagnostic Tools](visual studio diagnostic tools external code), you should also be able to observe memory usage over time, and take memory snapshots and memory diffs to see what objects are being leaked. The NTVS analysis engine code is complicated, but using the memory diagnostics tools will give you a good starting point for investigation.
Did you get a chance to try out the NTVS 1.2 Alpha as well? I suspect that using the ES6 Intellisense Preview option may work around this issue.

I took down the source and was able to build--the test projects failed though. I could not get included or latest versions of VSTestHost to install/work properly. I might have time later this week but I can only attempt during any down time at work.
However, I did try 1.2 Alpha, and no problems so far.

Thanks you trying to look into this.
Yes, VSTestHost is only required for the (ui based) tests. If you build the full solution, there will be VSTestHost related build errors, but the NTVS extension should build and run just fine without it installed. I've run into a similar problem installing the included VSTestHost MSI recently on a Win10 VM and will look into updating the included installer.
No rush looking into the issue, and please let me know if you run into any other problems or could use any help with the investigation. Also, if the build instructions are unclear in any way, feel free to update them or let me know.

In the last 15 mins, I had 4 restarts of VS launching the same project which just has 4 ts files. Not sure if all of the errors in the event viewer are errors from NodeJS tools itself.

Event Viewer export.
VSCrash.zip
This is my VS configuration:
Microsoft Visual Studio Enterprise 2015
Version 14.0.25123.00 Update 2
Microsoft .NET Framework
Version 4.6.01038
Installed Version: Enterprise
Architecture and Modeling Tools   00322-90000-92003-AA742
Microsoft Architecture and Modeling Tools
UML® and Unified Modeling Language™ are trademarks or registered trademarks of the Object Management Group, Inc. in the United States and other countries.
Visual Basic 2015   00322-90000-92003-AA742
Microsoft Visual Basic 2015
Visual C# 2015   00322-90000-92003-AA742
Microsoft Visual C# 2015
Visual C++ 2015   00322-90000-92003-AA742
Microsoft Visual C++ 2015
Visual F# 2015   00322-90000-92003-AA742
Microsoft Visual F# 2015
Windows Phone SDK 8.0 - ENU   00322-90000-92003-AA742
Windows Phone SDK 8.0 - ENU
Application Insights Tools for Visual Studio Package   5.208.60602.2
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 2015 (RC1 Update 1)   14.1.11106.0
ASP.NET and Web Tools 2015 (RC1 Update 1)
ASP.NET Web Frameworks and Tools 2012.2   4.1.41102.0
For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563
ASP.NET Web Frameworks and Tools 2013   5.2.40314.0
For additional information, visit http://www.asp.net/
Clang with Microsoft CodeGen   14.0.25317
Clang with Microsoft CodeGen
Common Azure Tools   1.7
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
JavaScript Language Service   2.0
JavaScript Language Service
JavaScript Project System   2.0
JavaScript Project System
KofePackagePackage Extension   1.0
KofePackagePackage Visual Studio Extension Detailed Info
Microsoft Azure HDInsight HQL Service   2.0.2900.0
Language service for Hive query
Microsoft Azure HDInsight Tools for Visual Studio   2.0.2900.0
An integrated development environment for HDInsight application development.
Microsoft Azure Mobile Services Tools   1.4
Microsoft Azure Mobile Services Tools
Microsoft Azure Tools   2.8
Microsoft Azure Tools for Microsoft Visual Studio 2015 - v2.8.40211.2
Microsoft MI-Based Debugger   1.0
Provides support for connecting Visual Studio to MI compatible debuggers
Node.js Tools   1.2.40329.01
Adds support for developing and debugging Node.js apps in Visual Studio
Node.js Tools - Profiling   1.2.40329.01
Profiling support for Node.js projects.
NuGet Package Manager   3.4.4
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
PreEmptive Analytics Visualizer   1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.
Python Tools for Visual Studio   2.2.40315.00
Python Tools for Visual Studio provides IntelliSense, projects, templates, Interactive windows, and other support for Python developers.
Python Tools for Visual Studio - Django Integration   2.2.40315.00
Provides templates and integration for the Django web framework.
Python Tools for Visual Studio - Profiling Support   2.2.40315.00
Profiling support for Python projects.
SQL Server Data Tools   14.0.60311.1
Microsoft SQL Server Data Tools
TypeScript   <IP_ADDRESS>
TypeScript tools for Visual Studio
Visual C++ for Cross Platform Mobile Development (Android)   14.0.25116.00
Visual C++ for Cross Platform Mobile Development (Android)
Visual C++ for Cross Platform Mobile Development (iOS)   14.0.25116.00
Visual C++ for Cross Platform Mobile Development (iOS)
Visual Studio Spell Checker   VSSpellChecker
An editor extension that checks the spelling of comments, strings, and plain text as you type.
https://GitHub.com/EWSoftware/VSSpellChecker
Visual Studio Tools for Apache Cordova   Update 9
Visual Studio Tools for Apache Cordova
Visual Studio Tools for Universal Windows Apps   14.0.25219.00
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10 Software Development Kit.
Web Essentials 2015.2   2.0.214
Adds many useful features to Visual Studio for web developers. Requires Visual Studio 2015
Windows Installer XML Toolset   <IP_ADDRESS>6
Windows Installer XML Toolset version <IP_ADDRESS>6
Copyright (c) Outercurve Foundation. All rights reserved.
Xamarin   <IP_ADDRESS> (0dd817c)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android   <IP_ADDRESS> (a94a03b)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS   <IP_ADDRESS> (3a25bf1)
Visual Studio extension to enable development for Xamarin.iOS.

After deleting the .ntvs_analysis.dat, and relaunching VS it didn't crash.

Issues like this with the analyzer should be fixed in NTVS 1.2. This release switches to a new IntelliSense engine by default that is much more performant and also offers better support for modern ES6 code. We do not have the resources to attempt to fixing the high memory usage on 1.1 with the old analysis engine.
If you run into any performance problems with NTVS 1.2, please open new issues to track these. Thanks.

@mjbvz Unless I am not mistaken, I was using NTVS 1.2 Alpha based on the version info above. Are you suggesting they will go away in the future ? or already fixed in the existing 1.2 Alpha

@rkavalap Sorry, that comment was based on nearwood's original report.
What IntelliSense level are you on? This should only show up in NTVS 1.2 if you are using Full/quick IntelliSense, instead of ES6 preview IntelliSense. ES6 IntelliSense is the default with NTVS 1.2.

@mjbvz  Thanks for the update. Yes I use full Intellisense.


feat(vscode): externalize connection parameterization

Please check if the PR fulfills these requirements

[X] The commit message follows our guidelines
[X] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? feature

What is the current behavior? when creating managed, function, and API connections, resource ID values are hardcoded in connections.json

What is the new behavior (if this is a feature change)? when creating managed, function, and API connections, resource ID values are parameterized in connections.json, references appsettings and parameters

Does this PR introduce a breaking change? no

Please Include Screenshots or Videos of the intended change:

@preetriti1 Can you please take a look at this?


Rename branches to be in line with silverstripe framework

Mark and I were discussing about renaming branches and where future versions should be developed.
Currently we have:

master → 1.x development branch
2.0 → 2.x development branch
1.0 → old 1.0 version
0.9 → Version compatible with SilverStripe 2.4

I think develop-2.0 has become obsolete? I don't know about the other branches…
SilverStripe (framework) seems to use master for the most up to date version, so that would (currently) be 4.x. Development on 3.x goes into 3, minor versions go into 3.1, 3.2, 3.3 etc. for patch level releases.
If we were to adopt this pattern, our branches would look like this:

master → 2.x development branch
1 → 1.x development branch
1.0 → 1.0 development (probably not gonna happen)
0.9 → 0.9 development (probably not gonna happen)

If needed, we can also create branches for 1.1, 1.2 etc. and work on patch level releases, such as 1.2.x. At the moment tags seem to be sufficient for this though.
Thoughts?

My current preference would be to leave things as they are until 2.0 becomes the main development target (maybe over the summer some time?). Right now, I'd prefer to have most pull requests go into the next 1.x release unless they represent breaking changes. I could be easily persuaded otherwise though.

@bummzack Has this been tidied up enough? At this stage I think focusing on 2.X and ongoing rather than 1.2.x would be most practical.

@wilr Yeah, master is currently meant for 2.x development and there's a 1 branch for further development that should go into 1.x. As soon as we start on features for 3.x we can branch current master into 2 for 2.x and use master for 3.x…
master should always be the future development branch.


More RBAC permissions support

Updated RBAC permissions support and added 403 to the openapi spec files.

Codecov Report

Merging #108 into master will increase coverage by 20.66%.
The diff coverage is 87.34%.

@@             Coverage Diff             @@
##           master     #108       +/-   ##
===========================================
+ Coverage   50.14%   70.80%   +20.66%
===========================================
  Files          13       13
  Lines         357      411       +54
===========================================
+ Hits          179      291      +112
+ Misses        178      120       -58

Impacted Files
Coverage Δ

historical_system_profiles/deleter.py
0.00% <0.00%> (ø)

historical_system_profiles/listener_logging.py
0.00% <ø> (ø)

historical_system_profiles/archiver.py
72.00% <85.18%> (+72.00%)
:arrow_up:

historical_system_profiles/views/v1.py
96.15% <90.32%> (+29.48%)
:arrow_up:

historical_system_profiles/config.py
100.00% <100.00%> (+6.06%)
:arrow_up:

historical_system_profiles/db_interface.py
80.43% <100.00%> (+13.76%)
:arrow_up:

historical_system_profiles/listener_metrics.py
100.00% <100.00%> (+100.00%)
:arrow_up:

historical_system_profiles/models.py
98.11% <100.00%> (+27.74%)
:arrow_up:

... and 3 more

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 bc119c2...6511d33. Read the comment docs.


Test auto closer

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Version [e.g. 22]

Works as expected closing it.


Add publish step to swift-toolbox in CI/CD

This PR adds automated publishing of the binary tools in console_backend whenever there is a tag.
However, I have a few remaining questions:

what's the best way to test this? just create a new tag and see if it works?
Once I have confirmed this is working, whats the best way to have it post to the package registry for releases that have already happened.
Is there value in having the headless console packaged as one of the tools?

Frontend and Release Workflow Started here

Frontend and Release Workflow Started here

Frontend and Release Workflow Started here

Frontend and Release Workflow Started here

Frontend and Release Workflow Started here

Frontend and Release Workflow Started here

also should this be done on the private CI side where releases are created (and just add an extra step to build additional binaries and hook to package registry) https://github.com/swift-nav/swift-toolbox-ci/blob/ed55ef50a99e661845a0c9527d9430191831f86a/.github/workflows/distribute.yml#L52

Doing this in https://github.com/swift-nav/swift-toolbox-ci could work, but it's not necessary since we don't need to use any of the lab machines

also should this be done on the private CI side where releases are created (and just add an extra step to build additional binaries and hook to package registry) https://github.com/swift-nav/swift-toolbox-ci/blob/ed55ef50a99e661845a0c9527d9430191831f86a/.github/workflows/distribute.yml#L52

Doing this in https://github.com/swift-nav/swift-toolbox-ci could work, but it's not necessary since we don't need to use any of the lab machines

Also, we'd have to introduce new architectures into the matrix there anyway, so I think it's a bit cleaner to just do the Swift Toolbox CLI stuff in it's own CI workflow.

Frontend and Release Workflow Started here

I simplified this PR to just contain the makefile changes necessary to make this happen. The CI/CD will live elsewhere.


.env file

I would suggest that there was a .env-model file to sample an example .env file

Thx for your feedback, .env.example is created.


Package access doesn't follow the rules in config.yaml

My reason:
I have been trying to limit access to a single user and have been able to do that with the  max_users: -1 setting after logging one user in (now I can only login to my registry with that one user).
Then I wanted to avoid other users from installing the package. I set package access only for $authenticated in my config.yaml.
But still a not-authenticated user can install my package by accessing the registry and doing:
 npm install name_of_package
I would suppose "access" means being able to retrieve the content of the package? Or am I wrong?
Steps to reproduce:
My config.yaml packages configuration looks like this:
 packages:
 	'**':
    	access: $authenticated
    	publish: $authenticated

My whole config.yaml file:
storage: ./storage

auth:
  htpasswd:
    file: ./htpasswd
    max_users: -1

uplinks:
  npmjs:
    url: https://registry.npmjs.org/

packages:
  '@*/*':
    access: $authenticated
    publish: $authenticated
    proxy: npmjs

  '**':
    access: $authenticated
    publish: $authenticated
    proxy: npmjs

logs:
  - {type: stdout, format: pretty, level: http}

listen:
  - <IP_ADDRESS>:4873  # listen on all addresses (INADDR_ANY)

@c4sh Could you define verdaccio version?

Version is 2.1.5.

I can't reproduce this issue, did you try restart verdaccio after edit configure file?

Yes I did restart verdaccio after changing config.yaml .

I can't figure out what's happed with your verdaccio, here is my configure file:
storage: ./storage

auth:
  htpasswd:
    file: ./htpasswd

uplinks:
  npmjs:
    url: https://registry.npmjs.org/

packages:
  '@*/*':
    access: $authenticated
    publish: $authenticated
    proxy: npmjs

  '**':
    access: $authenticated
    publish: $authenticated

    proxy: npmjs

logs:
  - {type: stdout, format: pretty, level: http}

I got 403 forbidden after remove auth information from .npmrc

I have emptied my .npmrc to no avail.
Are there any other config files that may induce verdaccio to think my machine is authenticated?
When I do npm whoami, I get
npm ERR! code ENEEDAUTH

npm ERR! need auth this command requires you to be logged in.
npm ERR! need auth You need to authorize this machine using `npm adduser`

Verdaccio just generate the auth token, either npm or yarn is the responsable to handle the auth in the client side.

Ok, but the access to the packages should be restricted based on whether the user is authorized with npm adduser or not, right?

Did you edit right configure file? It should not allow access if user is undefined(Anonymous access) and access permission set as authenticated
Linux: ~/.config/verdaccio/config.yaml
Windows: %AppData%\verdaccio\config.yaml

Oh. Just realized something. Was executing with nohup and not seeing the response of verdaccio at the logs. It turns out when I npm view and npm install my package I'm actually getting 403 in the verdaccio log:
 http  <-- 403, user: undefined, req: 'GET /name-of-my-package', error: unregistered users are not allowed to access package name-of-my-package
 http  <-- 403, user: undefined, req: 'GET /name-of-my-package', error: unregistered users are not allowed to access package name-of-my-package
 http  <-- 403, user: undefined, req: 'GET /some-dependency', error: unregistered users are not allowed to access package some-dependency
 http  <-- 403, user: undefined, req: 'GET /another-dependency', error: unregistered users are not allowed to access package another-dependency
 http  <-- 403, user: undefined, req: 'GET /third-dependency', error: unregistered users are not allowed to access package third-dependency

but I can see the package at my shell using view and I get the content of the package after npm install anyway. Could npm be fetching it from any other "cache" ?

Check ~/.npm, it's npm local cache directory.
BTW: It's better to use pm2 or forever to keep node application running

Ok that was it, thanks a lot !!
Inside ~/.npm I had some of the versions of the package itself and its dependencies, including the latest, as well as a cache.json with the whole description (I guess npm view was checking that one).
So verdaccio was behaving correctly, but my npm was trying with the cache content after failing to retrieve it from the registry. Removing the cached contents made everything work as expected (giving back access denied).
Sorry about that, but it's nice to know how the inner parts work anyway!
PD: Tried before with forever before going for nohup, couldn't get it to work. Verdaccio seemed to be active and fine but got no answer when calling the registry. Maybe I'll try again later.


Trigger workflows on pull request

To (hopefully) allow workflows to run on PRs from forks.

Closed by #56.


trainning for word task on a custom datatset for ner

Hi, I was running the following command and I face the error bellow, do you have any idea about it?
python experiments/run_word_task.py train_configs/word-task/Llama2-bi-mntp.json
  File "/workspace/llm2vec/experiments/run_word_task.py", line 740, in <module>     main()   File "/workspace/llm2vec/experiments/run_word_task.py", line 736, in main     trainer.train()   File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 1885, in train     return inner_training_loop(   File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 2216, in _inner_training_loop     tr_loss_step = self.training_step(model, inputs)   File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 3238, in training_step     loss = self.compute_loss(model, inputs)   File "/usr/local/lib/python3.10/dist-packages/transformers/trainer.py", line 3264, in compute_loss     outputs = model(**inputs)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1501, in _call_impl     return forward_call(*args, **kwargs)   File "/workspace/llm2vec/experiments/run_word_task.py", line 93, in forward     outputs = self.model(   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1501, in _call_impl     return forward_call(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/peft/peft_model.py", line 642, in forward     return self.get_base_model()(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1501, in _call_impl     return forward_call(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/transformers/models/llama/modeling_llama.py", line 940, in forward     causal_mask = self._update_causal_mask( TypeError: LlamaBiModel._update_causal_mask() takes from 4 to 5 positional arguments but 6 were give

Hi @SGidentification,
Are you using the latest version of llm2vec? We had pushed a fix for this issue (5492ca5) when it was raised in #33.

thanks I changed the version of transformers to "transformers_version": "4.40.0" and llm2vec to 0.1.5 and now it is working


Adding codeonwers file

Related issue
Fixes #51
⚠ This PR should be merged before the next release in order to avoid notifications due to the latest improvements to be finished in this repo.

bors merge


[QUESTION] (dev/update-skia) Wrong naming in new SkColorType members?

The dev/update-skia branch has new SkColorType members:
	public enum SKColorType
	{
		Unknown = 0,
		Alpha8 = 1,
		Rgb565 = 2,
		Argb4444 = 3,
		Rgba8888 = 4,
		Rgb888x = 5,
		Bgra8888 = 6,
		Rgba1010102 = 7,
		Rgb101010x = 8,
		Gray8 = 9,
		RgbaF16 = 10,
                // vvv NEW vvv
		RgbaF16Normalized = 11,
		RgbaF32 = 12,
		R8g8Unnormalized = 13,
		A16Float = 14,
		R16g16Float = 15,
		A16Unnormalized = 16,
		R16g16Unnormalized = 17,
		R16g16b16a16Unnormalized = 18,
	}

These correspond to Skia's
enum SkColorType {
    kUnknown_SkColorType,      //!< uninitialized
    kAlpha_8_SkColorType,      //!< pixel with alpha in 8-bit byte
    kRGB_565_SkColorType,      //!< pixel with 5 bits red, 6 bits green, 5 bits blue, in 16-bit word
    kARGB_4444_SkColorType,    //!< pixel with 4 bits for alpha, red, green, blue; in 16-bit word
    kRGBA_8888_SkColorType,    //!< pixel with 8 bits for red, green, blue, alpha; in 32-bit word
    kRGB_888x_SkColorType,     //!< pixel with 8 bits each for red, green, blue; in 32-bit word
    kBGRA_8888_SkColorType,    //!< pixel with 8 bits for blue, green, red, alpha; in 32-bit word
    kRGBA_1010102_SkColorType, //!< 10 bits for red, green, blue; 2 bits for alpha; in 32-bit word
    kBGRA_1010102_SkColorType, //!< 10 bits for blue, green, red; 2 bits for alpha; in 32-bit word
    kRGB_101010x_SkColorType,  //!< pixel with 10 bits each for red, green, blue; in 32-bit word
    kBGR_101010x_SkColorType,  //!< pixel with 10 bits each for blue, green, red; in 32-bit word
    kGray_8_SkColorType,       //!< pixel with grayscale level in 8-bit byte
    kRGBA_F16Norm_SkColorType, //!< pixel with half floats in [0,1] for red, green, blue, alpha; in 64-bit word
    kRGBA_F16_SkColorType,     //!< pixel with half floats for red, green, blue, alpha; in 64-bit word
    kRGBA_F32_SkColorType,     //!< pixel using C float for red, green, blue, alpha; in 128-bit word

    // The following 6 colortypes are just for reading from - not for rendering to
    kR8G8_unorm_SkColorType,   //<! pixel with a uint8_t for red and green

    kA16_float_SkColorType,    //<! pixel with a half float for alpha
    kR16G16_float_SkColorType, //<! pixel with a half float for red and green

    kA16_unorm_SkColorType,    //<! pixel with a little endian uint16_t for alpha
    kR16G16_unorm_SkColorType, //<! pixel with a little endian uint16_t for red and green
    kR16G16B16A16_unorm_SkColorType,//<! pixel with a little endian uint16_t for red, green, blue, and alpha

However, the unorm in the C++ Skia API means unsigned normalized, not un-normalized
Maybe Unnormalized means unsigned normalized, but in the industry, UNORM and SNORM are the naming conventions.
Also - at least in OpenGL - UNORM is the standard, so not explicitly mentioned. SNORM is non-standard, and explicitly mentioned.
The existing color types in  SkiaSharp v1.68 are actually all UNORM, but this is not mentioned in the name. E.g.  Bgra8888 is actually an UNORM 8-bit unsigned integer.
One exception though, the SkColorType.RgbaF16 in v1.68 is actually not normalized at all... The new RgbaF16Normalized is, but normalized here means something different, since the floating point numbers are not normalized, but rather just clamped between [0..1]...  So maybe SkColorType.RgbaF16Clamped would be a better way to describe this? I'm not 100% sure this is correct, maybe kRGBA_F16Norm_SkColorType does something different...
Since the new members are not yet in master, maybe the C# API could use a more consistent naming? I would just drop the unnormalized in the name, but I'm not sure what to do with the floating point related members...
Tricky.

Ah, thanks for pointing this out! The naming is not yet set in stone.
It is a bit weird that they suddenly added unorm to the new colors. Maybe they wanted to be more explicit in the naming...
I actually like your idea of maybe dropping unorm. For the floats, we can use the existing convention of F16 of F32.
 Things keep changing.   Haha.

IMO it's not that bad :)
Yeah, the new Skia color types seem to follow the DirectX conventions a bit more, e.g. DXGI_FORMAT_R8G8B8A8_UNORM, DXGI_FORMAT_R32G32B32A32_FLOAT, ...
I missed the bit-size part, indeed, Skia also changed that one...

I'm having a look at this now and interesting what you said:

So maybe SkColorType.RgbaF16Clamped would be a better way to describe this?

static constexpr SkColorType GrColorTypeToSkColorType(GrColorType ct) {
    switch (ct) {
        case GrColorType::kUnknown:          return kUnknown_SkColorType;
        case GrColorType::kAlpha_8:          return kAlpha_8_SkColorType;
        case GrColorType::kBGR_565:          return kRGB_565_SkColorType;
        case GrColorType::kABGR_4444:        return kARGB_4444_SkColorType;
        case GrColorType::kRGBA_8888:        return kRGBA_8888_SkColorType;
        // Once we add kRGBA_8888_SRGB_SkColorType we should return that here.
        case GrColorType::kRGBA_8888_SRGB:   return kRGBA_8888_SkColorType;
        case GrColorType::kRGB_888x:         return kRGB_888x_SkColorType;
        case GrColorType::kRG_88:            return kR8G8_unorm_SkColorType;
        case GrColorType::kBGRA_8888:        return kBGRA_8888_SkColorType;
        case GrColorType::kRGBA_1010102:     return kRGBA_1010102_SkColorType;
        case GrColorType::kGray_8:           return kGray_8_SkColorType;
        case GrColorType::kAlpha_F16:        return kA16_float_SkColorType;
        case GrColorType::kRGBA_F16:         return kRGBA_F16_SkColorType;
        case GrColorType::kRGBA_F16_Clamped: return kRGBA_F16Norm_SkColorType;
        case GrColorType::kRGBA_F32:         return kRGBA_F32_SkColorType;
        case GrColorType::kAlpha_8xxx:       return kUnknown_SkColorType;
        case GrColorType::kAlpha_F32xxx:     return kUnknown_SkColorType;
        case GrColorType::kGray_8xxx:        return kUnknown_SkColorType;
        case GrColorType::kAlpha_16:         return kA16_unorm_SkColorType;
        case GrColorType::kRG_1616:          return kR16G16_unorm_SkColorType;
        case GrColorType::kRGBA_16161616:    return kR16G16B16A16_unorm_SkColorType;
        case GrColorType::kRG_F16:           return kR16G16_float_SkColorType;
        case GrColorType::kRGB_888:          return kUnknown_SkColorType;
        case GrColorType::kR_8:              return kUnknown_SkColorType;
        case GrColorType::kR_16:             return kUnknown_SkColorType;
        case GrColorType::kR_F16:            return kUnknown_SkColorType;
        case GrColorType::kGray_F16:         return kUnknown_SkColorType;
    }
    SkUNREACHABLE;
}

I think I am going with your suggestions.

Closing this as it is now merged into develop: https://github.com/mono/SkiaSharp/commit/6baf53f3ab59813e208c211b13fe078a4f0f4729


create tenant error

I wanted to create a tenant, but during the creation process, an error was reported
err_msg: com.amazonaws.services.s3.model.AmazonS3Exception: Status Code: 403, AWS Service: Amazon S3, AWS Request ID: B71325BD915C5E7C, AWS Error Code: null, AWS Error Message: Forbidden
There is no problem with my key, I can access S3 through Boto3
The partial configuration is as follows

终端节点不需要配置桶名


Use openjdk for travis checks

Changing the jdk for travis to use to be openjdk, rather than oraclejdk. Travis seems to be having trouble installing oracle jdk on xenial.

@BenjaminPerryRoss


Use HTTPS where possible

I’ve also cleaned up the HTML a bit by removing unneeded attribute/value pairs.

Will do a deploy today, thanks @mathiasbynens!

Please let me know when it’s deployed. Thanks!

Done as of yesterday afternoon
On Sat, Jan 23, 2016 at 1:56 AM, Mathias Bynens<EMAIL_ADDRESS>wrote:

Please let me know when it’s deployed. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/elsigh/browserscope/pull/2#issuecomment-174166573.

Actually, done as of right now - I needed to change the default version, derp. ;)

:+1:


normalise the docs for key generation to bring in line with the official docs

The docs relating to the key generation are subtly different to the official documentation
openssl docs

https://www.openssl.org/docs/man3.2/man1/openssl-genpkey.html
https://www.openssl.org/docs/man3.2/man1/openssl-genrsa.html
https://www.openssl.org/docs/man3.2/man1/openssl-rsa.html

this prototype
openssl genrsa -out private.pem 2048
openssl rsa -in private.pem -pubout

official docs
openssl genpkey -algorithm RSA -out private_key.pem -pkeyopt rsa_keygen_bits:2048
openssl rsa -pubout -in private_key.pem -out public_key.pem

Use the same commands as the official documentation and link to the official documentation https://docs.sign-in.service.gov.uk/before-integrating/generate-a-key/

ignore any local pem files for safety


Disallow access to tree when file handle is closed

This fixes #406. This also serves as a definitive answer to and closes #168. This seems like the safest approach in order to avoid inadvertently accessing memory mapped array data that is no longer available.
cc @Cadair

Coverage decreased (-0.002%) to 95.145% when pulling e544a62b4abd0615cb80ce691dfc6f8ee5444f1f on drdavella:strict-context-handler into 01e14dd2d123bcc14e1c20b74410456009d0d536 on spacetelescope:master.

Coverage decreased (-0.002%) to 95.145% when pulling 3be375d96b66172cb725dd895dfae21666ca1714 on drdavella:strict-context-handler into 01e14dd2d123bcc14e1c20b74410456009d0d536 on spacetelescope:master.


[Bug]: Dead link to STEPSS model

Is there an existing issue for this?

[X] There are no existing issues

Priority of this issue

[ ] high
[ ] medium
[X] low

What browsers are you seeing the problem on?
Firefox
Contact Details
No response
Describe the current behaviour
There is a dead link to the STEPSS model in the table at the bottom of this page:
https://colib.net/pages/testCases/converterDrivenStability/4VSCSystem/
Describe the expected behaviour
No response
Steps to Reproduce
No response

Fixed the issue reported


Term request: 'platelet-poor plasma preparation' and 'platelet-poor plasma'

label: platelet-poor plasma preparation
definition: A material component separation process in which (1) whole blood is first centrifuged to separate red blood cells from blood plasma, which forms the supernatant, and (2) the blood plasma is then centrifuged to separate platelets from the plasm.
editor-preferred term: platelet-poor plasma preparation process
label: platelet-poor plasma
definition: A blood plasma specimen that is the output of some platelet-poor plasma preparation and is the portion of plasma that contains fewer than 10,000 platelets per microliter.

Discussed on 2020-08-17. @dillerm to add these terms with minor changes:
label: platelet-poor plasma preparation process
parent: OBI:0600014 material component separation
action: add to src/ontology/obi-edit.owl
label: platelet-poor plasma specimen
parent: OBI:0100016 blood plasma specimen
action: add to src/ontology/obi-edit.owl


Added documentation for regenerate certificates.

As discussed in #109 here is a PR that adds documentation for how to regenerate certificates for the Dinghy VM.
Closes #109

Please rebase this onto the master branch as outlined in https://github.com/codekitchen/dinghy/blob/latest/CONTRIBUTING.md , thanks


Catch getView exception

I want to throw exceptions from getView on data fetching errors. Such as the user entered an invalid ID or doesn't have the permission. They are recoverable error of the current view, not application bugs so I think ErrorBoundary is not suitable. How can I catch them in navi and display an error page for users?

One option would be to use try/catch and then emit the errors via the route's data property, or pass them to a prop on the view element.

I just don't want to wrap every getView with try/catch.
My current solution is wrap with a custom function:
export function defineRoute(getViewFunction: Resolvable<React.ReactNode>) {
  return route({
    async getView() {
      try {
        return await getViewFunction.apply(this, arguments);
      } catch (e) {
        if (e instanceof RouteError) return <ErrorPage {...e} />;

        if (!(e instanceof Error)) e = new Error(String(e));
        return <ErrorPage uncaughtError={e} message={null} options={null} />;
      }
    }
  });
}


Add nebar:open-proxy command for menu customization

Reference Issues or PRs
A step towards https://github.com/nebari-dev/nebari/issues/2217
What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[x] Did you test the pull request locally?
[x] Did you add new tests?

Documentation
Documented in README

I will merge and release a new version to make review of https://github.com/nebari-dev/nebari/pull/2267 (which depends on this one) easier.


Error: "save"  doesn't exist in the new version of Prisma Migrate.

Bug description
Command: npx prisma migrate save --experimental
Error information:
Environment variables loaded from .env
Error: The current command "save" doesn't exist in the new version of Prisma Migrate.
Read more about how to upgrade: https://pris.ly/d/migrate-upgrade

Expected behavior
pass

Prisma information
schema.prisma
datasource db {
  provider = "sqlite"
  url      = "file:./dev.db"
}

generator client {
  provider = "prisma-client-js"
}

// 3
model Link {
  id          Int      @id @default(autoincrement())
  createdAt   DateTime @default(now())
  description String
  url         String
}

schema.graphql
type Query {
  info: String!
  feed: [Link!]!
}

type Mutation {
  post(url: String!, description: String!): Link!
}

type Link {
  id: ID!
  description: String!
  url: String!
}

Environment & setup

OS:  Mac OS
Database:  SQLite
Node.js version:  v14.15.0
Prisma version:  npx prisma -v

@prisma/cli          : 2.14.0
@prisma/client       : Not found
Current platform     : darwin
Query Engine         : query-engine 5d491261d382a2a5ffdc71de17072b0e409f1cc1 (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 5d491261d382a2a5ffdc71de17072b0e409f1cc1 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 5d491261d382a2a5ffdc71de17072b0e409f1cc1 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 5d491261d382a2a5ffdc71de17072b0e409f1cc1 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Studio               : 0.332.0

Please click the link in the error message and read what it says - the old save command does not exist any more in the new Preview Migrate and you will need to use the new commands.

Please click the link in the error message and read what it says - the old save command does not exist any more in the new Preview Migrate and you will need to use the new commands.

"you will need to use the new commands."
what is new command?

See https://www.prisma.io/docs/reference/api-reference/command-reference + https://www.prisma.io/docs/concepts/components/prisma-migrate


Update decline to 2.3.0

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.monovore", artifactId = "decline" } ]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #458.


PUBLIC URL reference gets added twice in the CRA build, static resources fails to load

Website created using CRA. To build a feature branch running this command. export PUBLIC_URL=pr-preview/pr-${{ github.event.number }} && npx react-scripts build.
In the build file, index.html It is already adding pr-preview/pr-number before static resource path. But while loading, it is referring to the path twice (attached screenshot).

You are referencing your scripts with relative paths e.g.:
<script src="pr-preview/pr-8/static/script.js"></script>

A script src that doesn't start with a slash is relative to the current path: https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_is_a_URL#absolute_urls_vs_relative_urls
The current path is /pr-preview/pr-8/, so that would resolve to /pr-preview/pr-8/pr-preview/pr-8/static/..., as you experienced.
To access https://<domain>/pr-preview/pr-8/static/script.js from /pr-preview/pr-8/, your script src needs to be either /pr-preview/pr-8/static/script.js (with a leading slash to make it absolute with an implicit domain), or static/script.js (without a leading slash, to be relative to the current path).
I haven't used create-react-app or even React, so unfortunately I can't help you achieve that in that framework.

Noting that I'm closing this issue as it's not a bug with this Action, but please feel free to respond and I'll help as best I can.


bug for "html.format.wrapAttributes": indentation of html is broken

VSCode Version: 1.10.1
OS Version: windows 10 x64 1607

Steps to Reproduce:

In vscode settings: "html.format.wrapAttributes": "force", (or force-align)
formatting html or vue files:

the indentation is all broken.

turns out that it works fine without any other plugins. seems not vscode's bug. :)


error in generatemode demo

https://babitmf.github.io/docs/bmf/multiple_features/graph_mode/generatemode/
when run the demo in it, AttributeError happen, 'bmf.lib._bmf.sdk.Packet' object has no attribute 'to_ndarray'

Hello, I'm really sorry. The code version in the document is the version we use internally and is relatively old. Please try the code I gave you first. The function is exactly the same and see if it can solve your problem. Document I will update the content later
pkts = (
     bmf. graph()
         .decode({'input_path': "../files/img.mp4"})['video']
         .ff_filter('scale', 299, 299) # or you can use '.scale(299, 299)'
         .start() # this will return a packet generator
)

for i, pkt in enumerate(pkts):
    # convert frame to a nd array
    if pkt.is_(bmf.VideoFrame):
        vf = pkt.get(bmf.VideoFrame)
        rgb = mp.PixelInfo(mp.kPF_RGB24)
        np_vf = vf.reformat(rgb).frame().plane(0).numpy()
        # we can add some more processing here, e.g. predicting
        print("frame", i, "shape", np_vf.shape)
    else:
        break

Thanks you a lot. The demo you give can work. And I have another two question to ask. I wish to decode videos which is yuv420p format, and get the v channel of them. The code shown in the first block. The parameters threads can help the frame extract faster. With a lot of videos to decode, any other methods can help speed the decode process? with cpu only.
video =  graph.decode({
                    'input_path': input_path,
                    "log_level":"quiet",
                    "dec_params": {"threads": "12"},
                })['video'].start() # this will return a packet generator

    for i, pkt in enumerate(video):
        # convert frame to a nd array
        if pkt.is_(bmf.VideoFrame):
            vf = pkt.get(bmf.VideoFrame)
            np_vf = vf.frame().plane(2).numpy()
        elsee
            break

What's more, when run the code, I find that a lot of info are output in the stdout, shown in the next block. the  "log_level" only works with logs related to ffmpeg. How to make it quiet. I think it can also help speed.
[2023-09-15 14:56:58.436] [info] c_ffmpeg_decoder c++ /root/mambaforge-pypy3/envs/BabitMF/lib/python3.7/site-packages/bmf/lib/libbuiltin_modules.so libbuiltin_modules.CFFDecoder
[2023-09-15 14:56:58.437] [info] Module info c_ffmpeg_decoder c++ libbuiltin_modules.CFFDecoder /root/mambaforge-pypy3/envs/BabitMF/lib/python3.7/site-packages/bmf/lib/libbuiltin_modules.so
[2023-09-15 14:56:58.441] [info] Constructing c++ module
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from './720p.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf59.27.100
  Duration: 00:01:00.03, start: 0.000000, bitrate: 2229 kb/s
    Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 720x1280 [SAR 1:1 DAR 9:16], 2087 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 59.94 tbc (default)
    Metadata:
      handler_name    : ?Mainconcept Video Media Handler
      encoder         : Lavc59.37.100 libx264
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 133 kb/s (default)
    Metadata:
      handler_name    : #Mainconcept MP4 Sound Media Handler
[2023-09-15 14:56:58.461] [info] c++ module constructed
[2023-09-15 14:56:58.461] [info] BMF Version: 0.0.8
[2023-09-15 14:56:58.461] [info] BMF Commit: af1b35a
[2023-09-15 14:56:58.461] [info] start init graph
[2023-09-15 14:56:58.461] [info] scheduler count1
debug queue size, node 0, queue size: 5
[2023-09-15 14:56:58.461] [info] node:c_ffmpeg_decoder 0 scheduler 0
[2023-09-15 14:57:01.763] [info] node id:0 decode flushing
[2023-09-15 14:57:01.763] [info] node id:0 Process node end
[2023-09-15 14:57:01.767] [info] node id:0 close node
[2023-09-15 14:57:01.767] [info] node 0 close report, closed count: 1
[2023-09-15 14:57:01.767] [info] node id:-1 eof received
[2023-09-15 14:57:01.768] [info] node id:-1 eof processed, remove node from scheduler
[2023-09-15 14:57:01.768] [info] schedule queue 0 start to join thread
[2023-09-15 14:57:01.768] [info] schedule queue 0 thread quit
[2023-09-15 14:57:01.768] [info] schedule queue 0 closed
[2023-09-15 14:57:01.768] [info] all scheduling threads were joint

Thanks you a lot. The demo you give can work. And I have another two question to ask. I wish to decode videos which is yuv420p format, and get the v channel of them. The code shown in the first block. The parameters threads can help the frame extract faster. With a lot of videos to decode, any other methods can help speed the decode process? with cpu only.
video =  graph.decode({
                    'input_path': input_path,
                    "log_level":"quiet",
                    "dec_params": {"threads": "12"},
                })['video'].start() # this will return a packet generator

    for i, pkt in enumerate(video):
        # convert frame to a nd array
        if pkt.is_(bmf.VideoFrame):
            vf = pkt.get(bmf.VideoFrame)
            np_vf = vf.frame().plane(2).numpy()
        elsee
            break

What's more, when run the code, I find that a lot of info are output in the stdout, shown in the next block. the "log_level" only works with logs related to ffmpeg. How to make it quiet. I think it can also help speed.
[2023-09-15 14:56:58.436] [info] c_ffmpeg_decoder c++ /root/mambaforge-pypy3/envs/BabitMF/lib/python3.7/site-packages/bmf/lib/libbuiltin_modules.so libbuiltin_modules.CFFDecoder
[2023-09-15 14:56:58.437] [info] Module info c_ffmpeg_decoder c++ libbuiltin_modules.CFFDecoder /root/mambaforge-pypy3/envs/BabitMF/lib/python3.7/site-packages/bmf/lib/libbuiltin_modules.so
[2023-09-15 14:56:58.441] [info] Constructing c++ module
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from './720p.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf59.27.100
  Duration: 00:01:00.03, start: 0.000000, bitrate: 2229 kb/s
    Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 720x1280 [SAR 1:1 DAR 9:16], 2087 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 59.94 tbc (default)
    Metadata:
      handler_name    : ?Mainconcept Video Media Handler
      encoder         : Lavc59.37.100 libx264
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 133 kb/s (default)
    Metadata:
      handler_name    : #Mainconcept MP4 Sound Media Handler
[2023-09-15 14:56:58.461] [info] c++ module constructed
[2023-09-15 14:56:58.461] [info] BMF Version: 0.0.8
[2023-09-15 14:56:58.461] [info] BMF Commit: af1b35a
[2023-09-15 14:56:58.461] [info] start init graph
[2023-09-15 14:56:58.461] [info] scheduler count1
debug queue size, node 0, queue size: 5
[2023-09-15 14:56:58.461] [info] node:c_ffmpeg_decoder 0 scheduler 0
[2023-09-15 14:57:01.763] [info] node id:0 decode flushing
[2023-09-15 14:57:01.763] [info] node id:0 Process node end
[2023-09-15 14:57:01.767] [info] node id:0 close node
[2023-09-15 14:57:01.767] [info] node 0 close report, closed count: 1
[2023-09-15 14:57:01.767] [info] node id:-1 eof received
[2023-09-15 14:57:01.768] [info] node id:-1 eof processed, remove node from scheduler
[2023-09-15 14:57:01.768] [info] schedule queue 0 start to join thread
[2023-09-15 14:57:01.768] [info] schedule queue 0 thread quit
[2023-09-15 14:57:01.768] [info] schedule queue 0 closed
[2023-09-15 14:57:01.768] [info] all scheduling threads were joint

if you want to speed up the decoding step, you can use cuda to accelerate. Please refer to document
the log_level is used to pass log parameter into ffmpeg, you can set environment variable to disable the BMF logs, please refer to document