FR: Allow filtering out vendor code calls in stack trace

This is more like a Sentry-wide feature request than something related to raven-js only, but let me describe it here since I use raven-js in my project and JS stack traces may be uncomfortably long with some libraries:
In Sentry app there's a switch that allows filtering out raven internal calls in the displayed stack trace.

I suggest there should be a way to define which path patterns and/or function names should be treated as "App only". Now only raven.js stack trace items are filtered out.
I'd love to exclude ionic, angular and jQuery functions from it to be readable.
Note that Chrome Dev tools already allow filtering out vendors. It's called Blackboxing.

If you use Webpack to assemble your code, Sentry server will automatically do this for you.
If you're not using Webpack, you can perform this manually by using a dataCallback to manually iterate through the stack trace frames and set in_app: false/true.

Since this is handled by includePaths, closing this issue.

@benvinegar thank you


[Spec] Improve Form Field

The FormField spec does not reflect all lates decisions:

[x] Update figma spec
[x] Add spec to ZH

✅ Specs updated & added to ZH

✅ FormField specs are now updated in Figma & ZH !


add_column adding line breaks to "json" output

When I'm making the following add_column call:
public function getData()
    {
        $users = User::leftjoin('role_user', 'role_user.user_id', '=', 'users.id')
                    ->leftjoin('roles', 'roles.id', '=', 'role_user.role_id')
                    ->select(array('users.id', 'users.username','users.email', 'roles.name as rolename', 'users.confirmed', 'users.created_at'));

        $editCore = '{{{ trans(\'button.edit\') }}}';
        $deleteCore = '@if($username == \'admin\') @else {{{ trans(\'button.delete\') }}} @endif';

        return Datatables::of($users)
        ->edit_column('confirmed','@if($confirmed) Yes @else No @endif')
        ->add_column('actions', $editCore.$deleteCore) // here's where problem is manifesting
        ->remove_column('id')
        ->make();
    }

The resulting "json" returned has line breaks in it (as viewed in both Firefox and Chrome), eg below
{"draw":0,"recordsTotal":5,"recordsFiltered":5,"data":[["admin","admin@example.org","admin"," Yes ","2015-08-28 16:36:34","Edit<\/a> "],["gold","gold@example.org","gold_user"," Yes ","2015-08-28 16:36:34","Edit<\/a> Delete<\/a> "],["silver","silver@example.org","silver_user"," Yes ","2015-08-28 16:36:34","Edit<\/a> Delete<\/a> "],["bronzeplus","bronzeplus@example.org","bronzeplus_user"," Yes ","2015-08-28 16:36:34","Edit<\/a> Delete<\/a> "],["user","user@example.org","comment"," Yes ","2015-08-28 16:36:34","Edit<\/a> Delete<\/a> "]],"queries":[{"query":"select count(*) as aggregate from (select '1' as row_count from `users` left join `role_user` on `role_user`.`user_id` = `users`.`id` left join `roles` on `roles`.`id` = `role_user`.`role_id`) count_row_table","bindings":[],"time":115.47},{"query":"select `users`.`id`, `users`.`username`, `users`.`email`, `roles`.`name` as `rolename`, `users`.`confirmed`, `users`.`created_at` from `users` left join `role_user` on `role_user`.`user_id` = `users`.`id` left join `roles` on `roles`.`id` = `role_user`.`role_id`","bindings":[],"time":5.69}],"input":{"sEcho":"1","iColumns":"6","sColumns":"","iDisplayStart":"0","iDisplayLength":"10","mDataProp_0":"0","mDataProp_1":"1","mDataProp_2":"2","mDataProp_3":"3","mDataProp_4":"4","mDataProp_5":"5","sSearch":"","bRegex":"false","sSearch_0":"","bRegex_0":"false","bSearchable_0":"true","sSearch_1":"","bRegex_1":"false","bSearchable_1":"true","sSearch_2":"","bRegex_2":"false","bSearchable_2":"true","sSearch_3":"","bRegex_3":"false","bSearchable_3":"true","sSearch_4":"","bRegex_4":"false","bSearchable_4":"true","sSearch_5":"","bRegex_5":"false","bSearchable_5":"true","iSortCol_0":"0","sSortDir_0":"asc","iSortingCols":"1","bSortable_0":"true","bSortable_1":"true","bSortable_2":"true","bSortable_3":"true","bSortable_4":"true","bSortable_5":"true","_":"1441245968700"}}

(note line breaks immediately before the href tags - as far as I can tell, this is raw output, which is causing a "JSON data from server could not be parsed" error).
When I comment out the add_column call in the getData method, the line breaks aren't added.  So what am I doing wrong?
I'm using laravel 5.1, v5.0 of laravel-datatables, and v1.9.4 of the jquery datatables plugin.

@CyberiaResurrection, You are correct about the line breaks. I checked your response using http://jsonlint.com/ and that was the culprit. Try deleting the space between a and href <a href=. There might be a new line character that mostly due to copy paste on my opinion.
On the other hand, I suggest you use DT v1.10.x. I already dropped the support for DT legacy code and the package might not work as expected on your current version.

Yeah, removing the space removes the line breaks but defeats the point of what i was using it for.
I'll try upgrading to v1.10.x and let you know if this problem recurs.

Oh, what I mean when removing the space is to clear any possible new line character and replace it with an actual space character.

Adding back a space between a and href didn't change things - output still has the line breaks.

Ok. Maybe you should use the view approach for your action. Maybe the blade compiler is causing the line break. You can use the view approach like below:
return Datatables::of($users)
    ->edit_column('confirmed','@if($confirmed) Yes @else No @endif')
    ->add_column('actions', 'path.to.action.view')
    ->remove_column('id')
    ->make();

On view, all attributes of users will be passed to their own variable. Example view
  {{ $name }}
  @if (auth()->user()->id('admin'))
  Delete
  @endif

Thanks heaps for your help so far.
I upgraded to v1.10.9 of datatables, and the error message changed to "invalid json response".
Didn't know you could drop a view in like that - let's see how that goes.

No luck - the json response still has the line breaks.
I dug around a bit further and dd'ed the datatables result - it seems the line breaks are not in the underlying json response.received from Laravel, but are added in after that.

@CyberiaResurrection
Can you paste the unformatted json response via browser > view source? I tried replicating it via Ubuntu and it resulted in my app the correct json format.

Here you are, @ChaosPower, the unformatted json response as dug out via view source - do you want/need anything more?

{"draw":0,"recordsTotal":5,"recordsFiltered":5,"data":[["admin","admin@example.org","admin"," Yes ","2015-08-28 16:36:34","Edit<\/a> "],["gold","gold@example.org","gold_user"," Yes ","2015-08-28 16:36:34","Edit<\/a>  Delete<\/a>"],["silver","silver@example.org","silver_user"," Yes ","2015-08-28 16:36:34","Edit<\/a>  Delete<\/a>"],["bronzeplus","bronzeplus@example.org","bronzeplus_user"," Yes ","2015-08-28 16:36:34","Edit<\/a>  Delete<\/a>"],["user","user@example.org","comment"," Yes ","2015-08-28 16:36:34","Edit<\/a>  Delete<\/a>"]],"queries":[{"query":"select count(*) as aggregate from (select '1' as row_count from `users` left join `role_user` on `role_user`.`user_id` = `users`.`id` left join `roles` on `roles`.`id` = `role_user`.`role_id`) count_row_table","bindings":[],"time":0.56},{"query":"select `users`.`id`, `users`.`username`, `users`.`email`, `roles`.`name` as `rolename`, `users`.`confirmed`, `users`.`created_at` from `users` left join `role_user` on `role_user`.`user_id` = `users`.`id` left join `roles` on `roles`.`id` = `role_user`.`role_id`","bindings":[],"time":0.38}],"input":[]}

here is what I am getting. (notice that it's single line)

{"draw":0,"recordsTotal":8,"recordsFiltered":8,"data":[["ANA","raguirre3@example.com","Administrator"," Yes ","2015-09-02 09:38:11"," ","Edit<\/a> Delete<\/a> "],["ANA","raguirre3@example.com","Registered"," Yes ","2015-09-02 09:38:11"," ","Edit<\/a> Delete<\/a> "],["ANA","raguirre3@example.com","Administrator"," Yes ","2015-09-02 09:38:11"," ","Edit<\/a> Delete<\/a> "],["acme","raguirre1@example.com","Administrator"," Yes ","2015-09-02 05:15:17"," ","Edit<\/a> Delete<\/a> "],["ANA","raguirre3@example.com","Registered"," Yes ","2015-09-02 09:38:11"," ","Edit<\/a> Delete<\/a> "],["user","raguirre2@example.com","Registered"," Yes ","2015-09-02 05:15:17"," ","Edit<\/a> Delete<\/a> "],["ANA","raguirre3@example.com","Super Administrator"," Yes ","2015-09-02 09:38:11"," ","Edit<\/a> Delete<\/a> "],["admin","raguirre@example.com","Super Administrator"," Yes ","2015-09-02 05:15:17"," ","Edit<\/a> "]],"queries":[{"query":"select count(*) as aggregate from (select '1' as row_count from users left join role_user on role_user.user_id = users.id left join roles on roles.id = role_user.role_id) count_row_table","bindings":[],"time":1.34},{"query":"select users.id, users.username, users.email, roles.name as rolename, users.confirmed, users.created_at from users left join role_user on role_user.user_id = users.id left join roles on roles.id = role_user.role_id","bindings":[],"time":2.21}],"input":[]}

May I get your testing OS?
Below is my testing route.

use App\Models\User;

Route::get('tester', function() {
    $users = User::leftjoin('role_user', 'role_user.user_id', '=', 'users.id')
        ->leftjoin('roles', 'roles.id', '=', 'role_user.role_id')
        ->select(array('users.id', 'users.username','users.email', 'roles.name as rolename', 'users.confirmed', 'users.created_at'));

    $editCore = '{{{ trans(\'button.edit\') }}}';
    $deleteCore = '@if($username == \'admin\') @else {{{ trans(\'button.delete\') }}} @endif';

    return Datatables::of($users)
        ->edit_column('confirmed','@if($confirmed) Yes @else No @endif')
        ->add_column('actions', $editCore.$deleteCore) // here's where problem is manifesting
        ->remove_column('id')
        ->make();
});

I am using Ubuntu 14.04 LTS x64 for testing.

I'm using Fedora 21 on a quad Xeon (64 bit).
I definitely haven't been getting any single-line result, it's all been multi-line.

@CyberiaResurrection
May I know your current editor? SublimeText 2 /1 PHP Storm / Vim?
I am currently downloading fedora and will install your current fedora and retry to replicate your issue. This is interesting, because ghost bugs do exist.

I'm using phpstorm 8 if that helps, with php 5.6, apache 2.4 and whatever latest version of mariadb is.

Thanks @ChaosPower and @yajra for your help  - after sleeping on it, turns out things were tripping over a deeply-buried and misconfigured minifier (that I'd forgotten about) that was merrily clobbering json output.,  Have fixed the misconfiguration, and the problem's gone.


A new Pinterest script is added to index.html at every page call

Hi,
I am using create-react-app and have added the segment snippet in the index.html (not the npm package)
Every time i call window.analytics.page() a duplicate <script> for the Pinterest snippet is added to index.html file
which then throws the following error:
Pinterest Tag Error: 'load' command was called multiple times.  Previously for tag id 'XXXXXXXXXXXXX', now for tag id 'XXXXXXXXXXXXX'.

This behavior does not happen when calling track
One other note we don't currently have the Pinterest Destination enabled
Thank you for your help

It turns out this was an issue in Google Tag Manager.  They were loading the Pinterest snippet through segment.  We fixed it by changing the "Load once Per Page" setting in Google Tag Manager


Creating a boolean field

Hello Andrew
First of all thanks for all this work you've put together. It makes my life so much easier.  I tweaked the MetaDataServiceExamples class to help me with some admin functions (deleting fields, adding fields).  I can add text fields with no issue, but when trying to add a boolean field, I get an error that 'Boolean' is an incorrect enum type.
I call this (and other methods) from the Developer Console via e.g.
MetaDataServiceExamples.createFieldTypeBoolean('Case', 'Test Boolean', 'Test_Boolean__c');
Here's my helper class:
public static void createFieldTypeBoolean(String strObject, String sLabel, String sAPI)
{
MetadataService.MetadataPort service = createService();
MetadataService.CustomField customField = new MetadataService.CustomField();
customField.fullName = strObject + '.' + sAPI;
customField.label = sLabel;
customField.type_x = 'Boolean';
    List<MetadataService.SaveResult> results =
        service.createMetadata(
            new MetadataService.Metadata[] { customField });
    handleSaveResults(results[0]);
}

I hope you can help.
Thanks,
David

I fixed my own issue.  Instead of type_x = 'Boolean', I needed to use type_x = 'Checkbox'.


Should exclude Javadoc

Javadoc is generated, so no point flagging it

Better, it should be configurable whether to scan javadoc. Maybe an 'ignore path' config parameter.

Not sure why one would ever want to scan Javadoc as well as the source from which it is generated.
There is already a way to ignore paths, but it means every project with Javadoc has to update their config.

Agreed, virtually no one wants to scan javadoc. But neither do you want the tool skipping directories because it wrongly thinks they contain javadoc.

The tool should anyway list which directories are skipped.
Note that Javadoc directory trees have a standard set of files, so should be reasonably easy to detect with few false positives


implemented load function

closes issue #130, implemented load function and updated tests, implemented save and load functions for yolov5

Just a couple of comments:

For the sake of symmetry, can we also implement a save_model function? Something like

def save_model(optimized_model: BaseInferenceLearner, path: Union[str, Path]):
    optimized_model.save(path)

We should import the load_model and save_model functions in speedster __init__.py file. In this way the user can import them directly from speedster with

from speedster import optimize_model, save_model, load_model

And don't forget to update both the readme and the documentation with the new load_model and save_model functions.


Custom database types not recognized.(Referencing an older issue on rainlab builder)

See for orinal issue https://github.com/rainlab/builder-plugin/issues/257
See if this can be implemented automatically in schemabuilder or somewhere else.
Aparently this solves it.
Db::getDoctrineSchemaManager()->getDatabasePlatform()->registerDoctrineTypeMapping('txid_snapshot', 'text');
I'll pick this up if nobody else does, and otherwise this adds an existing issue that can be referenced.

I'm not sure what this plugin would do differently, it sounds like adding support for custom doctrine type mapping is already supported through using your own plugins to register it to the global schema manager?

If you look at the original issue, you'll see that although its registered, an error message would stil popup.
So somewhere there was an issue with it still, when using non standard schema input types.
I'll see if this is still an issue in wintercms/laravel 9.
I just ported this issue here, to see if its still an issue and if I can fix it, or at least add to the documentation, for those who encounter it how to resolve it.

@tschallacka feel free to provide some edits for the docs, if the suggested fix works. I'll close this for now.


How to enable https on rasa core server

Rasa Core version:
0.12.3
Python version:
3.6.7
Operating system (windows, osx, ...):
windows 7 64 bit
Issue:
Hey guys! So my bot is running on AWS and i’m getting the reply in my browser. But it’s a “http” i.e. it’s not secure port. I need secure port to run with my web app. Whenever I enable the SSL on port 5005 and try to run the bot it gives error and says,
File “/home/ubuntu/.local/lib/python3.6/site-packages/gevent/server.py”, line 256,│
in _tcp_listener │ sock.bind(address) │
OSError: [Errno 98] Address already in use: (‘<IP_ADDRESS>’, 5005)
Now when I disable my SSL and run the bot, It runs easily and replies on http call. So how can I convert this http to https? Any help is appreciated.
Content of domain file (if used & relevant):

Hi @bikashkumars
I got error in these line and i am stucked here, Can you help me out in this.
" RedirectPermanent /rasa"
Regards
Manthan Tanna


Use getContentUri on newer Android versions

This is an attempt to fix the java.lang.IllegalArgumentException: Volume external_primary not found that we see on Crashlytics ([1], [2], [3]).
I can't replicate the problem in an emulator, but I verified that we still query all media on the phone with these changes.
The is not much to find about this problem, except one StackOverflow post.
Google is still using the constant in their generic example

But they use the getContentUri in the query the media collection example:

Can you please link the Crashlytics issues to the issues/PRs, so we can close them after the fix?
I don't see it in the console right now looking it up myself

Can you please link the Crashlytics issues to the issues/PRs, so we can close them after the fix?

I linked to the Crashlytics issues from the pull request description. I'm not sure how to link to this PR from the Crashlytics issue and Google is not telling me, do you know if that is possible?

. I'm not sure how to link to this PR from the Crashlytics issue and Google is not telling me, do you know if that is possible?

The only way is through these "notes"

It's probably a good practice to link them like so, but it's not a big deal, I mostly asked to put them in at least in PR description for me to review


fix(autoware_universe_utils): fix constParameterReference

Description
This is a fix based on cppcheck constParameterReference warnings
common/autoware_universe_utils/src/geometry/random_convex_polygon.cpp:34:70: style: Parameter 'random_double' can be declared as reference to const [constParameterReference]
  const size_t nb_vertices, std::uniform_real_distribution<double> & random_double,
                                                                     ^

common/autoware_universe_utils/src/geometry/random_convex_polygon.cpp:35:40: style: Parameter 'random_bool' can be declared as reference to const [constParameterReference]
  std::uniform_int_distribution<int> & random_bool, std::default_random_engine & random_engine)
                                       ^

Related links
Parent Issue:

Link

How was this PR tested?
Notes for reviewers
None.
Interface changes
None.

Effects on system behavior
None.

The function call operator() of std::uniform_int_distribution<int> is not a const member function and cannot be directly const.
Therefore, I chose to suppress the warning by commenting.

@soblin @TakaHoribe @takayuki5168
Please confirm the PR. Thank you very much.

@kobayu858 The ci fails due to disk space shortage. You can skip this for now until the cause is resolved.


Deploy toolchain-member-operator on staging eaas cluster

@dperaza4dustbit @hugares please review. I'm not sure how to verify these changes before merging so I may be missing some things.

/retest

@hugares please take another look. Here's some evidence of the what's changed with dev and staging by diffing the before and after of kustomize build <overlay>.
+ git checkout main
Switched to branch 'main'
Your branch is up to date with 'upstream/main'.
+ kustomize build argo-cd-apps/overlays/development
+ kustomize build argo-cd-apps/overlays/staging-downstream
+ kustomize build argo-cd-apps/overlays/konflux-public-staging
+ git checkout RHTAPWATCH-1147
Switched to branch 'RHTAPWATCH-1147'
+ kustomize build argo-cd-apps/overlays/development
+ kustomize build argo-cd-apps/overlays/staging-downstream
+ kustomize build argo-cd-apps/overlays/konflux-public-staging
+ diff -U 15 dev-original.yaml dev-new.yaml
--- dev-original.yaml   2024-07-18 11:46:06.662687312 -0400
+++ dev-new.yaml        2024-07-18 11:46:07.558692015 -0400
@@ -1,22 +1,23 @@
 apiVersion: v1
 kind: Secret
 metadata:
   labels:
     appstudio.redhat.com/host-cluster: "true"
     appstudio.redhat.com/internal-member-cluster: "true"
     appstudio.redhat.com/member-cluster: "true"
+    appstudio.redhat.com/toolchain-member: "true"
     argocd.argoproj.io/secret-type: cluster
   name: cluster-kubernetes.default.svc
   namespace: openshift-gitops
 stringData:
   config: '{"tlsClientConfig":{"insecure":false}}'
   name: in-cluster-local
   server: https://kubernetes.default.svc
 type: Opaque
 ---
 apiVersion: argoproj.io/v1alpha1
 kind: ApplicationSet
 metadata:
   name: application-api
   namespace: openshift-gitops
 spec:
+ diff -U 15 staging-ds-original.yaml staging-ds-new.yaml
--- staging-ds-original.yaml    2024-07-18 11:46:06.903688577 -0400
+++ staging-ds-new.yaml 2024-07-18 11:46:08.009694383 -0400
@@ -1796,31 +1796,31 @@
         syncOptions:
         - CreateNamespace=false
 ---
 apiVersion: argoproj.io/v1alpha1
 kind: ApplicationSet
 metadata:
   name: toolchain-member-operator
   namespace: argocd-staging
 spec:
   generators:
   - merge:
       generators:
       - clusters:
           selector:
             matchLabels:
-              appstudio.redhat.com/member-cluster: "true"
+              appstudio.redhat.com/toolchain-member: "true"
           values:
             clusterDir: ""
             environment: staging
             sourceRoot: components/sandbox/toolchain-member-operator
       - list:
           elements: []
       mergeKeys:
       - nameNormalized
   template:
     metadata:
       name: toolchain-member-operator-{{nameNormalized}}
     spec:
       destination:
         namespace: toolchain-member-operator
         server: '{{server}}'
+ diff -U 15 staging-public-original.yaml staging-public-new.yaml
--- staging-public-original.yaml        2024-07-18 11:46:07.205690162 -0400
+++ staging-public-new.yaml     2024-07-18 11:46:08.255695674 -0400
@@ -1829,31 +1829,31 @@
         syncOptions:
         - CreateNamespace=false
 ---
 apiVersion: argoproj.io/v1alpha1
 kind: ApplicationSet
 metadata:
   name: toolchain-member-operator
   namespace: konflux-public-staging
 spec:
   generators:
   - merge:
       generators:
       - clusters:
           selector:
             matchLabels:
-              appstudio.redhat.com/member-cluster: "true"
+              appstudio.redhat.com/toolchain-member: "true"
           values:
             clusterDir: ""
             environment: staging
             sourceRoot: components/sandbox/toolchain-member-operator
       - list:
           elements: []
       mergeKeys:
       - nameNormalized
   template:
     metadata:
       name: toolchain-member-operator-{{nameNormalized}}
     spec:
       destination:
         namespace: toolchain-member-operator
         server: '{{server}}'

@amisstea I checked in ArgoCD instances to make sure the new label was applied to all member clusters and the only one without it is stg-m01: https://argocd-server-konflux-public-staging.apps.appsres05ue1.pwhm.p1.openshiftapps.com/settings/clusters/https%3A%2F%2Fapi.stone-stg-m01.7ayg.p1.openshiftapps.com%3A6443
I am not sure why yet, either we forgot this one in the app-interface MR or there is a deployment/refresh issue

@hugares the stg-m01 cluster has the label now.


Fix paragraph break

Fixes #36190

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

Thanks for the edit @Potapy4 !


Added LODScacale, revamped the pagedLOD example. CullStack now inheri…

…ts from CullSettings

That would be cool to have basic unittest at least to see if there are some regression linked to pagelod. Do you have some on you apps that could be transfered to osgjs ?

It is kind of hard to test DatabasePager and/or PagedLOD in unitary tests, but I just coded a visual test in the PagedLOD example in this PR. Did you tried it?


Callbacks: accessing subcharts and setting switcher option

Hello,
i'm trying to implement show_async to have a more flexible chart. I am using the Callbacks example.
I'm wondering about two things.
1.) Accessing subcharts
When using the Callbacks example I want to create a chart including subcharts. I am struggling to access the subcharts (including their lines) after creating them in the main function. What is the best way to access them?
2.) Setting the switcher widget current option programmatically
In the example the topbar text is set
self.chart.topbar['symbol'].set(searched_string)
I am wondering if I can do the same for a switcher widget? I couldn't find any similiar way to change the current option programmatically
BR

Hey
In your API callback class, the attribute chart will be dynamically updated to the chart or subchart that was responsible for emitting the callback.
There is no way to programatically change a switcher after the chart has been loaded, however you can set the inital value of the switcher when defining it.

Thank you @louisnw01 for the reply. It makes sense to have it like that.
In my case I am using the switcher widget to move my "chart area" one day further. It's not working as intended because it can only be triggered once.

Ah I see. So I think you want to be able to click a switcher more than once?
Perhaps a seperate 'button' widget may be of benefit.

Yes, basicly I want to use it as a button. Another widget of that kind would be perfect.


Modify coreum-osmosis IBC information

After discussion with Osmosis team, a new IBC client was created raising the trust treshhold to 2/3 for better security.
We created a new client and new connection so we need to modify this information.

I think this is possible because it was only just created yesterday


No longer needed to mark the filter job as completed

What
Don't mark a filter job as complete
How to review
Review the code
Who can review
anyone

test


Readme confusion

It reads: "For a live demonstration, open this site on Safari.". However, Safari appears to be the only browser NOT supported by this plugin. WAT?

You can open Safari as a demo to see how it "gracefully degrades".

Oh, I get it now.


Add y-labels to statistical example

I am unsure why the diff decided everything was changed...
It is actually just two lines (and two images), which specify the y-label, which Anja Vrečko noticed was missing (bottom example).
The y-label is now NDVI mean.

I am unsure why the diff decided everything was changed... It is actually just two lines (and two images)

Images are rendered as a strings in the diff, and the amount of change is probably over Github's threshold of showing details.

I am unsure why the diff decided everything was changed... It is actually just two lines (and two images)

Images are rendered as a strings in the diff, and the amount of change is probably over Github's threshold of showing details.

It actually worked fine until i reverted some changes in VSCode :upside_down_face: so weird...


tf.image.resize with bilinear breaks mixed precision

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):YES
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Ubuntu 18.04
TensorFlow installed from (source or binary):conda
TensorFlow version (use command below):2.x
Python version:3.7
CUDA/cuDNN version:10.1
GPU model and memory:v100 32GB

Use tf.image.resize with BILINEAR upsampling breaks mixed precision and makes the speed much slower than fp32. Change to NEAREST_NEIGHBOR works

@edwardyehuang
Please update the issue template with exact tensorflow version and sample code for us to replicate the issue faced or if possible share colab gist with error to analyse.

@Saduf2019
https://colab.research.google.com/drive/1G78SCjm9UVvZGHsqM6ki4LfdT-1dHDJJ?usp=sharing
Make sure you are using Tesla T4 in colab to test mixed precision.
Adjust "ENABLE_MIXED_PRECISION" to verify the effect.
FP32 2s/img vs FP16 4s/img

@reedwm I see that you fixed this for tf 2.4 which is great.
I was seeing the same effect in my networks and I hadn't pinned it down to upsampling.
Another problem I am noticing is that after a certain (large) number of iterations, nans start appearing in my trainig (I haven't figured out where first yet). Could this be related and should this fix the nan issue?

@zaccharieramzi this fix does not affect NaNs or numerical stability, so unfortunately it's unlikely the NaN issue will be fixed. Unfortunately, NaN issues that only appear after a certain number of iterations are difficult to debug. Try making the loss of the model run in float32 if it doesn't already. Additionally, if the model ends in softmax, run the softmax in float32 as well. You can also try saving a checkpoint on the step before you get a NaN. Then you will be able to load the checkpoint and reproduce the NaN by just running one step.


Should jitter RNG use salt for nonce generation?

In
https://github.com/openssl/openssl/blob/012353bdf21b98def920ac317b94c4a9ed501b79/crypto/rand/prov_seed.c#L114
salt is being passed in.
But in
https://github.com/openssl/openssl/blob/012353bdf21b98def920ac317b94c4a9ed501b79/providers/implementations/rands/seed_src_jitter.c#L170
addin is not used at all.
Should it be added to the pool at least the same way as it is done here in this non-EVP get_nonce implementation?
https://github.com/openssl/openssl/blob/012353bdf21b98def920ac317b94c4a9ed501b79/crypto/rand/prov_seed.c#L91

I'm not sure if this should be treated as a bug or a feature request: if the RNG is working, the salt isn't doing anything useful.
Still, it won't cause any harm adding the salt so we should do it at some point.


feat(icon): add color prop to the icon component

Summary
Icon
GitHub ticket: #336
The  new color prop accepts one of the following values, which are defined in the defaultTheme.ts file:

"beta"
"gray"
"primary"
"secondary"
"info"
"success"
"warning"
"error"

However, these values can be modified through the use of custom themes created by products.
Checklist

[x] Default Story in Storybook
[x] LivePreview Story in Storybook
[x] Test Story in Storybook
[x] Tests written
[x] Variables from defaultTheme.ts used wherever possible
[x] If updating an existing component, depreciate flag has been used where necessary
[ ] Chromatic build verified by @chanzuckerberg/sds-design

Conceptually the idea is there and works great! However I think we should provide more flexibility to folks so they can use any color from the library and aren't limited to the -400 variants of them. See my comment in Chromatic for more details.

A new prop named shade has been added to the Icon component, which can be used to set the color shade of the icon to 100, 200, 300, 400, 500 or 600.


Add sweet alert for non-bootstrap users.

A possible suggestion before the package becomes too large due to "Please add support for X framework" requests.
Seperate the renderer out to it's own package.
then a user can pull in a renderer e.g. genealabs/laravel-messenger-bootstrap4 which will require genealabs/laravel-messenger.
This abstraction would also allow the community to add support for any number of rendering methods.

Thank you, that's a good point. I will delve into this down the road and explore this more. :)


ADD Currency Conversion Toggle [tool]

Currency Conversion Toggle:
Add a toggle to view crypto prices in different fiat currencies, like USD, EUR, and GBP.
This would be as simple as adding a currency conversion API and allowing users to select their preferred currency in the settings.

Currency Conversion Toggle:
Add a toggle to view crypto prices in different fiat currencies, like USD, EUR, and GBP. This would be as simple as adding a currency conversion API and allowing users to select their preferred currency in the settings.

sorry write now whatever that issue i am creating by some reason maintainer can not add label so i am raising my pr this is issue
@vanshchauhan21


pubish umd to npm mk II

This doesn't include the manual media changes

@codingjoe any update on this?

@graingert did you give me access yet for the npm package?

@graingert codingjoe ;)

@codingjoe any update on this?

Travis is currently not working. I will tag this once it's working again and check if it releases correctly. If I forget please ping me again ;)

@codingjoe awesome thanks

Ah your commit actually broke the travis config. I missed that. I should be working now. I am just waiting for the deploy to succeed.

Released in 6.3.0

ok @graingert, I think you will need to put a bit more love into this
https://travis-ci.org/applegrew/django-select2/jobs/419135968

Looks like you need to 'skip_cleanup' to deploy build artifacts:
Cleaning up git repository with git stash --all. If you need build
artifacts for deployment, set deploy.skip_cleanup: true. See
https://docs.travis-ci.com/user/deployment#Uploading-Files-and-skip_cleanup.
On Wed, 22 Aug 2018, 13:01 Johannes Hoppe<EMAIL_ADDRESS>wrote:

ok @graingert https://github.com/graingert, I think you will need to
put a bit more love into this
https://travis-ci.org/applegrew/django-select2/jobs/419135968
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/applegrew/django-select2/pull/479#issuecomment-415008120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZQTEJXXvcKxwNxHLDR6QwNyF652aTIks5uTUgWgaJpZM4UETxO
.

@graingert I can't wait for your pull-request 👍


Fixed an error when using rows in tabs

@z-song Could you try these changes? My tests were correct but it would be good if you could verify it.
Displayed correctly:

Thanks, I'll verify this later

thanks to you for this amazing project.

@luischavez Please could you look into this for me https://github.com/z-song/laravel-admin/issues/5645 thank you


fix: fix fetching updated targets from TUF root (based off of #1921)

Summary

This change refactors the cosign TUF client and hopefully aims to simplify the logic behind embedded TUF repository and targets, and the writeable on-disk/in-memory repository and targets. Roughly, I structured this so that the cosign TUF client contains (1) A client.LocalStore to hold TUF repository metadata updates and (2) A targetImpl to hold downloaded and cached target files.
Previously, the two were "out of sync" -- when starting with an embedded workflow, we would create an embedded root repository and an embedded targetImpl. However, the embedded targetImpl ONLY retrieved embedded targets, not the updated ones!
https://github.com/sigstore/cosign/blob/5f09c424d541cf22fd3d891ccadc7f7d6c762f72/pkg/cosign/tuf/client.go#L548
Embedded workflows never used their updated targets, despite writing them to the underlying storage, and failed to retrieve new targets referenced by updated metadata.
Conceptually now, there are 4 main objects in the TUF client:

An memoryCache targetImpl: A map that stores target files by name.
A diskCache targetImpl: Stores targets on disk.
An embeddedWrapper targetImpl: This wraps the underlying (memory, disk) cache. By default it Gets embedded targets. If any targets were downloaded and Set, then Get transfers to retrieving from the underlying cache.
An embeddedLocalStore that wraps either a MemoryLocalStore or FileLocalStore. Similar to above, by default it gets embedded repo metadata, until any new metadata needed to be downloaded and set. Then any GetMeta operations get the cached metadata.

Other:

To make testing easier, interfaced the default embedded repo and default remote mirror.
Tested the addition of a new target in an update. The same test at HEAD fails to find the target.
I tested this against a binary of cosign that pointed to the default mirror as brokenv3's GCS bucket and it successfully found the new target fulcio_interemediate_v1.crt.pem

If this design looks good, I will continue to add testing and clean-up test code. It's a pain to manually write out TUF updates, so I'd like to unify those functions and also add testing for consistent snapshotting (note brokenv3 enabled that so I'm 90% sure that works with this fix).
Ticket Link

Fixes https://github.com/sigstore/cosign/issues/1899
Release Note

* bug fix: Fixes bug in retrieving newly added verification material from TUF root.

Codecov Report

Merging #1932 (605175c) into main (5f09c42) will decrease coverage by 0.04%.
The diff coverage is 57.98%.

@@            Coverage Diff             @@
##             main    #1932      +/-   ##
==========================================
- Coverage   34.01%   33.96%   -0.05%
==========================================
  Files         153      153
  Lines        9977     9971       -6
==========================================
- Hits         3394     3387       -7
- Misses       6202     6205       +3
+ Partials      381      379       -2

Impacted Files
Coverage Δ

cmd/cosign/cli/fulcio/fulcioroots/fulcioroots.go
36.36% <0.00%> (ø)

pkg/cosign/tlog.go
29.18% <16.66%> (-0.53%)
:arrow_down:

pkg/cosign/tuf/client.go
62.18% <66.00%> (+0.50%)
:arrow_up:

pkg/cosign/tuf/store.go
73.33% <0.00%> (-6.67%)
:arrow_down:

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 5f09c42...605175c. Read the comment docs.

Looks like the Windows tests are unhappy with this:
--- FAIL: TestGetRekorPubKeys (0.21s)
    tlog_test.go:25: Unexpected error calling GetRekorPubs, expected nil: getting trusted root: open repository\root.json: file does not exist
    tlog_test.go:28: expected 1 or more keys, got 0
Repository initialized
Staged snapshot.json metadata with expiration date: 2022-06-06 08:58:35 +0000 UTC
Staged timestamp.json metadata with expiration date: 2022-05-31 08:58:35 +0000 UTC
Committed successfully

Maybe a path separator issue? Seems to work on everything else just fine.

Nice work @vaikas and @asraa!
When @asraa looks we can just merge this one.

I cribbed the PR subject / description from #1921 here in case this is what we end up merging.

Actually can we hold off a day on merging this? I think #1921 is pretty close

This PR does a lot, and I don't want to submit this without submitting https://github.com/sigstore/cosign/pull/1921 first. We can't rush this large PR through to unblock tests, there's a risk with breaking something else accidentally.

Hey! FWIW they're the same PR, so #1921 incorporates the CI fixes from @vaikas

This PR does a lot, and I don't want to submit this without submitting #1921 first. We can't rush this large PR through to unblock tests, there's a risk with breaking something else accidentally.

Hey! FWIW they're the same PR, so #1921 incorporates the CI fixes from @vaikas

Yep - we only need to merge one of them. We do need to get one of them merged though as this is holding up a pretty large release.

Totally fair, but I also want to make sure we take our time reviewing the PR to not introduce other subtle bugs.

Some folks are concerned that this might be just hiding a test failure, let's take the time to review this in depth in the original PR #1921. @lukehinds @bobcallaway for another pair of eyes. What is the release timeline, we should be able to make that one.

We can close this one now, the commits got merged in with #1921.
FWIW they were always the same PR as @asraa noted, it was just done to expedite getting the tests fixed because this was blocking the release.


Compile the extension as separate typescript projects

Treat the extension as 3 separate projects:

UI Extension code

This excludes debugger code (that runs in a separate process)
This excludes our tests

Extension Debugger Code

This excludes debugger code (that runs in a separate process)
This excludes our tests

Tests

Just compile everything, for tests

Why the separation

We can let the compiler pick up bugs in our code
I.e. compiler can ensure extension does NOT use code from the debugger

I.e. fixes https://github.com/Microsoft/vscode-python/issues/3939

I.e. compiler can ensure extension does NOT use code from our tests

I.e. fixes https://github.com/Microsoft/vscode-python/issues/1758
We still have this happening today, now its leaking in because WebPack pulls stuff in silently..

setTimeout issues in node.js and browser world.

Compiler can get confused with what setTimeout returns. A number of Nodejs.timer! This is because the extension uses both types, to compile DS code and extension code.

Summary

Two issues can be traditionally solved in a complicated way using linters, refactoring, etc, when it can easily be solved via a compilation step.
Cheaper option.

Closing as stale


ESMValTool 2.2.0 code freeze

Now that the conda build is fixed, we can resume the release procedure.
I will suggest to do the code freeze tomorrow at 16:00 to give us a bit more time to do the reviews that both the issues with the core release and the conda build problems prevented us to focus on. Any objections
@ESMValGroup/esmvaltool-coreteam

If you postpone the code freeze, I would recommend also postponing the release by the same amount, to make sure we have a full week of testing.

Now that the conda build is fixed,

I noticed that there is no mention in the documentation that the conda package will only work for Python 3.7 and up. I think it would be good to add that.

Now that the conda build is fixed,

I noticed that there is no mention in the documentation that the conda package will only work for Python 3.7 and up. I think it would be good to add that.

good call, I'll add that right now :+1:

If you postpone the code freeze, I would recommend also postponing the release by the same amount, to make sure we have a full week of testing.

That was my intention. I should have made it explicit, though

Code freeze done!  The branch release_2.2.0 is now available for testing.
Please, edit this comment with the recipes that you are going to test to avoid duplication of efforts. It will be nice if you also specify where are you testing them.
List of recipes to test:

[ ] recipe_albedolandcover.yml
[ ] recipe_anav13jclim.yml
[ ] recipe_arctic_ocean.yml
[ ] recipe_autoassess_radiation_rms_Amon_all.yml
[ ] recipe_autoassess_radiation_rms_Amon_obs.yml
[ ] recipe_autoassess_radiation_rms_cfMon_all.yml
[ ] recipe_autoassess_stratosphere.yml
[ ] recipe_capacity_factor.yml
[ ] recipe_carvalhais14nat.yml
[ ] recipe_climwip_test_basic.yml
[ ] recipe_climwip_test_performance_sigma.yml
[ ] recipe_clouds_bias.yml
[ ] recipe_clouds_ipcc.yml
[ ] recipe_collins13ipcc.yml
[ ] recipe_combined_indices.yml
[ ] recipe_consecdrydays.yml
[ ] recipe_cox18nature.yml
[ ] recipe_cvdp.yml
[ ] recipe_deangelis15nat.yml
[ ] recipe_diurnal_temperature_index.yml
[ ] recipe_eady_growth_rate.yml
[ ] recipe_ecs.yml
[ ] recipe_ecs_constraints.yml
[ ] recipe_ecs_scatter.yml
[ ] recipe_ensclus.yml
[ ] recipe_extreme_events.yml
[ ] recipe_extreme_index.yml
[ ] recipe_eyring06jgr.yml
[ ] recipe_eyring13jgr_12.yml
[ ] recipe_flato13ipcc.yml
[ ] recipe_gier2020bg.yml
[ ] recipe_heatwaves_coldwaves.yml
[ ] recipe_hyint.yml
[ ] recipe_hyint_extreme_events.yml
[ ] recipe_kcs.yml
[ ] recipe_landcover.yml
[ ] recipe_lauer13jclim.yml
[ ] recipe_li17natcc.yml
[ ] recipe_martin18grl.yml
[ ] recipe_miles_block.yml
[ ] recipe_miles_eof.yml
[ ] recipe_miles_regimes.yml
[ ] recipe_modes_of_variability.yml
[ ] recipe_multimodel_products.yml
[ ] recipe_ocean_Landschuetzer2016.yml
[ ] recipe_ocean_amoc.yml
[ ] recipe_ocean_bgc.yml
[ ] recipe_ocean_example.yml
[ ] recipe_ocean_ice_extent.yml
[ ] recipe_ocean_multimap.yml
[ ] recipe_ocean_quadmap.yml
[ ] recipe_ocean_scalar_fields.yml
[ ] recipe_perfmetrics_CMIP5.yml
[ ] recipe_perfmetrics_CMIP5_4cds.yml
[ ] recipe_perfmetrics_land_CMIP5.yml
[ ] recipe_quantilebias.yml
[ ] recipe_rainfarm.yml
[ ] recipe_runoff_et.yml
[ ] recipe_russell18jgr.yml
[ ] recipe_schlund20esd.yml
[ ] recipe_seaice.yml
[ ] recipe_seaice_drift.yml (@jvegasbsc , Jasmin)
[ ] recipe_seaice_feedback.yml (@jvegasbsc , Jasmin)
[ ] recipe_shapeselect.yml
[ ] recipe_smpi.yml
[ ] recipe_smpi_4cds.yml
[ ] recipe_snowalbedo.yml
[ ] recipe_spei.yml
[ ] recipe_tcr.yml
[ ] recipe_thermodyn_diagtool.yml
[ ] recipe_toymodel.yml
[ ] recipe_validation.yml
[ ] recipe_validation_CMIP6.yml
[ ] recipe_wenzel14jgr.yml
[ ] recipe_wenzel16jclim.yml
[ ] recipe_wenzel16nat.yml
[ ] recipe_williams09climdyn_CREM.yml
[ ] recipe_zmnam.yml

Cmorizers

[ ] cmorizers/recipe_era5-land.yml
[ ] cmorizers/recipe_era5.yml

Examples

[ ] examples/recipe_check_obs.yml
[ ] examples/recipe_concatenate_exps.yml
[ ] examples/recipe_correlation.yml
[ ] examples/recipe_extract_shape.yml
[ ] examples/recipe_julia.yml
[ ] examples/recipe_my_personal_diagnostic.yml
[ ] examples/recipe_ncl.yml
[ ] examples/recipe_preprocessor_derive_test.yml
[ ] examples/recipe_preprocessor_test.yml
[ ] examples/recipe_python.yml
[ ] examples/recipe_r.yml
[ ] examples/recipe_variable_groups.yml

Hydrology

[ ] hydrology/recipe_hype.yml
[ ] hydrology/recipe_lisflood.yml
[ ] hydrology/recipe_marrmot.yml
[ ] hydrology/recipe_pcrglobwb.yml
[ ] hydrology/recipe_wflow.yml

Schlund20Jgr

[ ] schlund20jgr/recipe_schlund20jgr_gpp_abs_rcp85.yml
[ ] schlund20jgr/recipe_schlund20jgr_gpp_change_1pct.yml
[ ] schlund20jgr/recipe_schlund20jgr_gpp_change_rcp85.yml

@ESMValGroup/esmvaltool-developmentteam we have now entered the testing phase before v2.2.0 release, and we have frozen the code (insert song from Frozen here :grin: ) so we'd very much appreciate it if you could run your favourite recipe from the list above, and tell Javi which one you will be running by adding your name against the recipe(s) in the comment. Cheers muchly in advance :beer:

The hydrology recipes run using master branch were successful. For more info, please see issue #2034.

I'm getting an error for the recipe_validation.yml which appears while running the zonal_mean diagnostic. Here is the end of the zonal_mean/log.txt:
2021-02-22 09:32:25,218 [11970] INFO     _validation.py,49      Observations dataset(s) ['CERES-EBAF']
2021-02-22 09:32:25,218 [11970] INFO     validation.py,159      Loading /mnt/lustre01/scratch/b/b309192/runs/tests/esmvaltool_output/recipe_validation_2\
0210222_093105/preproc/validation_with_CERES-EBAF/rsut/CMIP5_MPI-ESM-LR_Amon_historical_r1i1p1_rsut_2001-2005.nc for seasonal extraction
2021-02-22 09:32:25,329 [11970] WARNING  py.warnings,109        /work/bd0854/b309192/soft/miniconda3/envs/test_tool_release/lib/python3.9/site-packages/\
iris/coords.py:1960: UserWarning: Collapsing a non-contiguous coordinate. Metadata may not be fully descriptive for 'time'.
  warnings.warn(msg.format(self.name()))

Traceback (most recent call last):
  File "/mnt/lustre01/pf/b/b309192/code/ESMValTool/esmvaltool/diag_scripts/validation.py", line 335, in <module>
    main(config)
  File "/mnt/lustre01/pf/b/b309192/code/ESMValTool/esmvaltool/diag_scripts/validation.py", line 291, in main
    ctrl_seasons = apply_seasons(ctrl)
  File "/mnt/lustre01/pf/b/b309192/code/ESMValTool/esmvaltool/diag_scripts/validation.py", line 163, in apply_seasons
    season_meaned_cubes = [
  File "/mnt/lustre01/pf/b/b309192/code/ESMValTool/esmvaltool/diag_scripts/validation.py", line 164, in <listcomp>
    season_cube.collapsed('time', iris.analysis.MEAN)
AttributeError: 'NoneType' object has no attribute 'collapsed'

The same issue occurs with meridional_mean. Is this something known? It seems this recipe was succesfully tested for the last release.

cheers @remi-kazeroni - lemme have a look into this :+1:

right - I replicated your issue @remi-kazeroni and found the bugger - the implementation of extract_season is an absolute turkey and am after the one who's dunnit this badly as we speak, all we have to do is pass meteorological seasons = ["DJF", "MAM", "JJA", "SON"] and that's it, but as it is now the seasons look like seasons = ['DJF', 'MAMJJASON']

@jvegasbsc that's an issue introduced in https://github.com/ESMValGroup/ESMValCore/pull/247/files#diff-ec2da1a859c8d6359e23421a3de9d444e455ed3008152eaa67bbdd01f4cadfb8 - how did that pass review and how did it not have a test attached to it to reveal its flaw in functionality?

@remi-kazeroni , this should be fixed with ESMValGroup/ESMValCore#1019. Do we need a 2.2.1 release of the core or we just modify the code? To make it work you just need to add manually the clim_season and season_year coords manually using
iris.coord_categorisation.add_season(cube, 'time', name='clim_season')
iris.coord_categorisation.add_season_year(cube, 'time', name='season_year')

before calling extract_season

We have done quite a nice bit of testing and only found the issue with the validation_recipe. Once #2054 is merged, which I want to do after the bot finishes or somebody can confirm that it works at DKRZ, I think we can proceed with the release

v2.2.0 is now published on PyPI and conda. I will proceed to test the conda package, as for some reason the installation is not as smooth as we would like, to make sure that it is functional and then will close the issue. If any of you can also test it, I will be very grateful

Ok.  So we can say that v2.2.0 is officially released. Thanks to all for your effort, and specially to V!


Attempted import error: 'celoCannoli' is not exported from 'viem/chains' (imported as 'celoCannoli').

It seems this chain is no longer available on viem/chains

@Zagorodnyi cannoli network is no longer supported, here's a list of available networks.

@Zagorodnyi cannoli network is no longer supported, here's a list of available networks.

Importing anything from packages/rainbowkit-celo/chains/index.ts will cause the error from this issue.
Cannoli is still present in the rainbowkit codebase.

Great catch @Zagorodnyi, that's our bad. I removed Cannoli from viem, but forgot to remove it here:

https://github.com/wevm/viem/pull/1462

Thanks for opening a PR 💯

Thanks for opening a PR 💯


explorer:  Generate Folder image thumbnail

📝 Provide a description of the new feature
What is the expected behavior of the proposed feature?  What is the scenario this would be used?
I can print a big preview of all the photos in the folder.

Specifies the Width/Height(px) or Ratio(1:1 / 3:2 / 2:3 / 9:16 / 16:9 ...) of each image
Specifies the interval(vertical/horizontal by px) between each image
Specify how many rows/column
The maximum width of the generated image
The maximum height of the generated image. If the height is exceeded, the remainder will continue to be generated in the new one.
Can select the information presented. For example, it can only view thumbnails no any text. Or display the file name below the image.

Similar third-party tools:

FastStone Image Viewer
Pictureflect Photo Viewer + Scroll to capture

If you'd like to see this feature implemented, add a 👍 reaction to this post.

if i understand the ask, explorer already does this for previewing (see screenshot).    If you want small images, why won't image resizer work for you?

Oh, my description might have been misinterpreted. I mean it can generate a preview of the contents of the folder .don't need user  Scroll screenshot to do this. Finally, generate a poster that looks like a gallery.
I want to generate a gallery like this:

2.

Although, this is my hypothetical effect. This is actually my screenshot in wallhaven.cc
But u can imagine that I have hundreds of photos in my folder. The program will help me create a poster full of photos. I'm specifying how many column,  rows, poster width, Extreme poster height.( If you exceed the length, it will turn into 2 posters, just like the one above )
this is different from the way the explorer.
FastStone Image Viewer have a features that looks something like this:

that's what I wanted

But it is based on of the print size and is not easy to control.

I can't see the PowerToys team creating this.  I'd suggest using those tools you listed above.


client not returning specified example even when "Prefer" header specified

Describe the bug
Title says it all: client not returning specified example even when prefer header specified.
followed the docs at https://meta.stoplight.io/docs/prism/docs/guides/01-mocking.md#response-examples
To Reproduce
I have created a small demo project to highlight this. This is available at https://github.com/hpl002/prismdebug

install packages and run 'test' script

Expected behavior
expected the specified example to get returned but instead get the first example, which is the default behavior.
Environment:
"@stoplight/prism-cli": "^4.0.1",
"@stoplight/prism-http": "^4.0.1"

Here is the .js file.
//To run: yarn; yarn test

const fs = require("fs");
const {
  createClientFromOperations,
} = require("@stoplight/prism-http/dist/client");
const {
  getHttpOperationsFromSpec,
} = require("@stoplight/prism-cli/dist/operations");

const initiateSandbox = async () => {
  const operations = await getHttpOperationsFromSpec("bundle.json");
  /* write operations to file for easy debugging */
  fs.writeFileSync("operations.json", JSON.stringify(operations));
  const client = createClientFromOperations(operations, {
    mock: true,
    validateRequest: false,
    validateResponse: false,
  });
  return client;
};

initiateSandbox().then((client) => {
  client
    .request("/accounts", {
      method: "get",
      headers: {
        Prefer: "example=scenario-3",
      },
    })
    .then((response) => console.log(response.data));
});

//Docs: https://meta.stoplight.io/docs/prism/docs/guides/01-mocking.md#response-examples
//should have returned the scenario 3 example. This example was declared in bundle.json and also carried over to the operations obj

Hey @hpl002,
this is indeed on purpose. The Http Server is the piece of code doing the actual extraction of the data from the header and it's a commodity for the Prism Http package.
If you want to do the same thing from the Http package directly, you need to feed the explicit option
Essentially, you need to modify your example to be:
client
  .request("/accounts", { method: "get" }, { mock: { exampleKey: "scenario-3", dynamic: false } })
  .then(response => console.log(response.data));

I'll open a PR to clarify the documentation — in meantime, let me know if this works and feel free to reopen in case it does not.


Fix error: Only iterables may be used in a SetType

Hello, I encountered this issue: data.allowed_mentions.users: Only iterables may be used in a SetType
content.allowedMentions should be content.allowed_mentions in payload.
Edit: errr just noticed this pr shouldn't be here. I'll go to the interactions branch x.x

Catboi8#68


Add my config to README

nice! But why not merge it into QMK?

Ok, will do!

Awesome! Closing this one then.


Non-directional damage tilting is wrong

When taking non-directional damage, such as from fire or drowning, the screen will always tilt left (as it does in vanilla without the fix). However, this is not correct - originally, the screen would randomly tilt either left or right when taking non-directional damage. It seems this code was actually removed at one point, so it no longer works even with the main damage tilt fix.

Interesting


浮点数例外（核心已转储）

感谢百度开源！
在用Taskflow的question_answering时，执行以下代码：
from paddlenlp import Tasflow
qa = Taskflow("question_answering", home_path="/data1/.paddlenlp")
qa("中国最大的河流是？")

如果在cpu上，设置device_id=-1，代码可以执行
如果在gpu上，设置device_id=0，代码出现以下错误

....
Prefix dict has been built successfuly.
浮点数例外（核心已转储）

然后程序直接退出！
版本、环境信息
1）PaddleNLP和PaddlePaddle版本：PaddleNLP 2.3.3，PaddlePaddle-gpu 2.3.0
2）系统环境：Linux
3）python版本 3.85

@cingtiye 您好，可以参考这里检查下paddlepaddle gpu版本是否正确安装：https://www.paddlepaddle.org.cn/documentation/docs/zh/api/paddle/utils/run_check_cn.html#run-check

@cingtiye 您好，可以参考这里检查下paddlepaddle gpu版本是否正确安装：https://www.paddlepaddle.org.cn/documentation/docs/zh/api/paddle/utils/run_check_cn.html#run-check

您好，我测试了一下，上面说是在一个GPU是被正确安装了，目前我的机器上有两个GPU。
>>> import paddle
>>> paddle.utils.run_check()
Running verify PaddlePaddle program ...
PaddlePaddle works well on 1 GPU.
W0914 09:27:02.323796 183442 fuse_all_reduce_op_pass.cc:76] Find all_reduce operators: 2. To make the speed faster, some all_reduce ops are fused during training, after fusion, the number of all_reduce ops is 2.
WARNING:root:PaddlePaddle meets some problem with 2 GPUs. This may be caused by:
 1. There is not enough GPUs visible on your system
 2. Some GPUs are occupied by other process now
 3. NVIDIA-NCCL2 is not installed correctly on your system. Please follow instruction on https://github.com/NVIDIA/nccl-tests
 to test your NCCL, or reinstall it following https://docs.nvidia.com/deeplearning/sdk/nccl-install-guide/index.html
WARNING:root:
 Original Error is: (External) CUDA error(209), no kernel image is available for execution on the device.
  [Hint: 'cudaErrorNoKernelImageForDevice'. This indicates that there is no kernel image available that is suitable for the device. This can occur when a user specifiescode generation options for a particular CUDA source file that do not include the corresponding device configuration.] (at /paddle/paddle/fluid/framework/details/all_reduce_op_handle.cc:299)

PaddlePaddle is installed successfully ONLY for single GPU! Let's start deep learning with PaddlePaddle now.

您的CUDA版本是多少？

您的CUDA版本是多少？

11.3

@cingtiye 您好，可以参考这里检查下paddlepaddle gpu版本是否正确安装：https://www.paddlepaddle.org.cn/documentation/docs/zh/api/paddle/utils/run_check_cn.html#run-check

您好，我测试了一下，上面说是在一个GPU是被正确安装了，目前我的机器上有两个GPU。
>>> import paddle
>>> paddle.utils.run_check()
Running verify PaddlePaddle program ...
PaddlePaddle works well on 1 GPU.
W0914 09:27:02.323796 183442 fuse_all_reduce_op_pass.cc:76] Find all_reduce operators: 2. To make the speed faster, some all_reduce ops are fused during training, after fusion, the number of all_reduce ops is 2.
WARNING:root:PaddlePaddle meets some problem with 2 GPUs. This may be caused by:
 1. There is not enough GPUs visible on your system
 2. Some GPUs are occupied by other process now
 3. NVIDIA-NCCL2 is not installed correctly on your system. Please follow instruction on https://github.com/NVIDIA/nccl-tests
 to test your NCCL, or reinstall it following https://docs.nvidia.com/deeplearning/sdk/nccl-install-guide/index.html
WARNING:root:
 Original Error is: (External) CUDA error(209), no kernel image is available for execution on the device.
  [Hint: 'cudaErrorNoKernelImageForDevice'. This indicates that there is no kernel image available that is suitable for the device. This can occur when a user specifiescode generation options for a particular CUDA source file that do not include the corresponding device configuration.] (at /paddle/paddle/fluid/framework/details/all_reduce_op_handle.cc:299)

PaddlePaddle is installed successfully ONLY for single GPU! Let's start deep learning with PaddlePaddle now.

是不是有个显卡是集显？

两张都是A100

@cingtiye 您好，可以参考这里检查下paddlepaddle gpu版本是否正确安装：https://www.paddlepaddle.org.cn/documentation/docs/zh/api/paddle/utils/run_check_cn.html#run-check

您好，我测试了一下，上面说是在一个GPU是被正确安装了，目前我的机器上有两个GPU。
>>> import paddle
>>> paddle.utils.run_check()
Running verify PaddlePaddle program ...
PaddlePaddle works well on 1 GPU.
W0914 09:27:02.323796 183442 fuse_all_reduce_op_pass.cc:76] Find all_reduce operators: 2. To make the speed faster, some all_reduce ops are fused during training, after fusion, the number of all_reduce ops is 2.
WARNING:root:PaddlePaddle meets some problem with 2 GPUs. This may be caused by:
 1. There is not enough GPUs visible on your system
 2. Some GPUs are occupied by other process now
 3. NVIDIA-NCCL2 is not installed correctly on your system. Please follow instruction on https://github.com/NVIDIA/nccl-tests
 to test your NCCL, or reinstall it following https://docs.nvidia.com/deeplearning/sdk/nccl-install-guide/index.html
WARNING:root:
 Original Error is: (External) CUDA error(209), no kernel image is available for execution on the device.
  [Hint: 'cudaErrorNoKernelImageForDevice'. This indicates that there is no kernel image available that is suitable for the device. This can occur when a user specifiescode generation options for a particular CUDA source file that do not include the corresponding device configuration.] (at /paddle/paddle/fluid/framework/details/all_reduce_op_handle.cc:299)

PaddlePaddle is installed successfully ONLY for single GPU! Let's start deep learning with PaddlePaddle now.

是不是有个显卡是集显？

两张都是A100

试试安装指定CUDA11.2版本的paddlepaddle
python -m pip install paddlepaddle-gpu==2.3.2.post112 -f https://www.paddlepaddle.org.cn/whl/linux/mkl/avx/stable.html

试试安装指定CUDA11.2版本的paddlepaddle
python -m pip install paddlepaddle-gpu==2.3.2.post112 -f https://www.paddlepaddle.org.cn/whl/linux/mkl/avx/stable.html

不行 放弃了 我换了个环境（版本都一样）和卡 （A100换成V100）现在可以了
谢谢~


Fix typo

Wrong package name was being used for grpc-gen.

LGTM assuming tests pass

Current coverage is 75.16% (diff: 100%)

Merging #54 into master will not change coverage

@@             master        #54   diff @@
==========================================
  Files            30         30
  Lines          1083       1083
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            814        814
  Misses          269        269
  Partials          0          0

Powered by Codecov. Last update d47a1fd...6f05e21


metadata_db: Remove unnecessary mutex lock on snapshotD map

Signed-off-by: Gaurav Singh<EMAIL_ADDRESS>Don't need a lock on snapshotD since every goroutine is updating a unique snapshot

Appears the file isn't properly gofmted:
##[error]metadata/db.go:333: File is not `gofmt`-ed with `-s` (gofmt)

@estesp thanks for pointing out. Its fixed now.

I'm going to close this one since we can't merge it as is. There is probably still improvements that could be made here if interested. Please include benchmarks/profiling along with the change to show the improvement as lock-free designs often have their own set of trade-offs.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_2ec8ed0f-d7e2-42e7-b8bc-a0f389f79dee/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_2ec8ed0f-d7e2-42e7-b8bc-a0f389f79dee.git

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

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_main_2022-05-25-11-42-14 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[ISSUE 6444]Optimize task node helper document in workflow toolbar

relevant ISSUE:https://github.com/apache/dolphinscheduler/issues/6444
Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Codecov Report

Merging #7226 (4c9dd34) into dev (ff9bc80) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #7226      +/-   ##
============================================
+ Coverage     40.37%   40.40%   +0.02%
- Complexity     3679     3680       +1
============================================
  Files           648      648
  Lines         27065    27065
  Branches       3035     3035
============================================
+ Hits          10928    10936       +8
+ Misses        15101    15091      -10
- Partials       1036     1038       +2

Impacted Files
Coverage Δ

...r/plugin/registry/zookeeper/ZookeeperRegistry.java
54.54% <0.00%> (+7.27%)
:arrow_up:

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 ff9bc80...4c9dd34. Read the comment docs.

LGTM

LGTM


added fluxible-immutable-utils to libraries page

CLA is valid!

Can we just add it to the docsCleanup branch in fluxible?

This is done now.


Doesn't seem to work in multi-node swarm

I'm using caprover in cluster mode (multi-node swarm).
Here is the spec for a service:
TaskTemplate:
  ContainerSpec:
    Labels:
      chadburn.enabled: "true"
      chadburn.job-exec.drush-cron.command: "drush --uri=https://www.mysite.com cron-run"
      chadburn.job-exec.drush-cron.schedule: "@every 10m"

The task is not being executed (or it's erroring out and not showing in the logs).
I tried to set chadburn to run only in a manager node to see if that was the issue, but I got the same results.

For anyone else wondering how to get it working for swarms:
I'm using this instead:
https://github.com/funkyfuture/deck-chores
And it works excellently on swarm environments.

@fidelix.
I'll take a look at that project source for inspiration for upcoming version 2.x of Chadburn. Thanks!


[JetChat] Improve screen-reader behavior

Refactor top app bars into the topAppBar parameter of a nested Scaffold.
This correctly clips accessibility focus rects that overlap with the top
of the screen.

Refactor the text field's padding and placeholder text into the
decorationBox parameter of BasicTextField.  This merges the text
field into a single, correctly-sized a11y-focusable element.

Add contentDescription to the profile icons.

On Emulator Pixel 5 API 30 the app bar seems too high:

The tall app bar looks preexisting (introduced by one of the recent Material3 patches).  Here is a screenshot of Pixel 5 API30 emulator at 525eb753a without any of my changes applied.


Cannot track new navigation container while another one is still tracked

Steps to reproduce the issue:
After integrated dataDog SDK, I am getting this Crash in "Crash free sessions by version" in UX Monitoring => [RUM Applications] and Application dashboard. But App is not crashing
Describe what you expected:
Without this error
Additional context
"@datadog/mobile-react-native": "^1.0.0-rc5",
"@datadog/mobile-react-navigation": "^1.0.0-rc5"

Hello @govarthananve! This error doesn't lead to the crash. Can you please share the code showing how our @datadog/mobile-react-navigation package is integrated? Do you have calls to DdRumReactNavigationTracking.startTrackingViews for different navigation containers?

only one using this in App.js file
import {DdRumReactNavigationTracking} from '@datadog/mobile-react-navigation';
<NavigationContainer
ref={navigationRef}
onReady={() => {
DdRumReactNavigationTracking.startTrackingViews(navigationRef.current);
}}
>
...

Hi @govarthananve!
We figured this error was triggered when Android users closed their app using the phone's hardware back button. We released a fix in version 1.0.0-rc7, so you should not see this error pop up anymore if you update.
I'm closing the issue for now, feel free to reopen it if you still encounter the issue with version 1.0.0-rc7 :)

I also get this when I set ddConfig.verbosity = SdkVerbosity.WARN and refresh the app during development. I removed that and the local error went away (i.e. was hidden), though it would be nice to have the logs on without getting this bogus one. (My NavigationContainer props are the same as above.)

Hi @blwinters,
Thanks for reporting it! We'll look into it and see if we can remove this warning in development mode while keeping the warning in relevant times.
I'll keep you updated once we make progress on this.


ImageryLayer remount warning even when using useMemo

I am working on an application where our imageryProvider layers are variable based on some user. I use the useMemo hook as suggested in the documentation to handle this but I still get this warning every time the layers string changes.
Warning: <ImageryLayer> is remounted because read only props have been updated: imageryProvider
The code looks something like this, where the layers will be a string that changes based on user selections.
const LayerRender = (props: Props) => {
	const { layers, show } = props;

	const imageryProvider = useMemo(
		() =>
			new WebMapServiceImageryProvider({
				url: `${some_url}`,
				layers,
				parameters: {
					transparent: 'true',
					format: 'image/png',
				},
			}),
		[layers],
	);

	return <ImageryLayer imageryProvider={imageryProvider} show={show} />;
};

Hmmm it is strange, but there is no doubt layers prop changes every render.

After updating resium version we no longer have this problem. Closing.

I am using the latest versions but I am facing this issue. In my case, nothing is variable in imageryProvider, I am just using show prop of imagery layer to on and off them.
<ImageryLayer show={checkedItems.layer} imageryProvider={WMSprovider("layer")} />
const WMSprovider = (layerName) => {
return new WebMapServiceImageryProvider({
url: geoserverUrl,
layers: ${storeName}:${layerName},
parameters: {
transparent: true,
format: "image/png",
},
});
};


Build python3 pynipap package

Also update debian packaging standards version.
Fixes #875

I haven't checked what buildrpm does, not sure if this is an issue

I'm not convinced the travis failures are mine....

Nice, thanks for PR :)
Travis-CI complains though, seems like python-pynipap wasn't built - https://travis-ci.org/SpriteLink/NIPAP/jobs/105397083#L1214
buildrpm has been in there, kind of dormant, since day 1. Never used it to build official RPMs or anything like that so I don't care if you've broken it since it wasn't really working before anyway ;) Should fix that some day...

Culprit: https://travis-ci.org/SpriteLink/NIPAP/jobs/105397083#L788
dh_auto_clean: unable to load build system class 'pybuild': Can't locate Debian/Debhelper/Buildsystem/pybuild.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at (eval 5) line 2.
BEGIN failed--compilation aborted at (eval 5) line 2.
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
debuild: fatal error at line 1350:
dpkg-buildpackage -rfakeroot -D -us -uc failed
make[1]: *** [builddeb] Error 29
make[1]: Leaving directory `/home/travis/build/SpriteLink/NIPAP/pynipap'

Ah, missing dependency. I'll fix that

...dh-python is newer than 12.04. dammit travis.

Maybe it's time to have a look at the new environments that Travis has to offer. We are still on their old/legacy platform. They introduced a sudo-less container environment that we can't use since we need root to install postgres extensions et al but now they also have some in between environment that I think runs on GCE and that gives you sudo. Or maybe it's possible to use a different distro even in the legacy environment.

I found https://docs.travis-ci.com/user/trusty-ci-environment/ but yeah, looking at the travis.yml file it would be good to get it a bit "updated"

I'll fix it so it runs on trust (14.04) instead. Please hold :)

Ok, I've merged that stuff to master so builds are now using 14.04. Can you rebase your branch on master and hopefully it should start working :)

Awesome :)
Now, don't suppose I can get a python3-pynipap deb in the repo now...  (yay for restrictive deployments)

I'm working on that but since the last deploy I've moved machines so I need to dig out my pgp key and stuff. Also need to figure out what version to release this as. Usually we keep all packages in sync but I can't just build new 0.28 packages from master since there are more major changes that should bump to 0.29, yet I don't want to release v0.29.0 right now since other stuff should go in there.
Correct way would be to backport to 0.28.x-branch but that involves cherry-picking which is PITA when there are more than 1 commits ;)
Think I can fake it a bit by circumventing parts of the build process and only do a 0.28.4 for python3-pynipap but first I need to have lunch.

I totally understand, no worries if you can't do it


In your description you use the word 'inpracticle' which is not a word.

You likely meant impractical. The typo in your summary makes me question the quality of the library.

Fixed, thanks!


allow provider to report updated prompt?

We have a framework that generates prompts on the fly (https://github.com/microsoft/genaiscript) which means that the prompt files built on the fly and sent to the LLM (This works great with the custom javascript provider model and we were able to integrate nicely with promptfoo)
This is problematic for the prompt source because it always ends up being the javascript source instead of the generated prompt, which disables a number of assertions that rely on the input.
Would there be a way to also provide the opportunity for the api provider to return the prompt it actually as part of the response? With a couple pointers, I would be happy to produce a PR.

This request definitely makes sense - I'm thinking about the best way to implement and will provide some pointers.


Typo in README

Do you want to request a feature or report a bug?
N/A

What is the current behavior?
N/A
If the current behavior is a bug, please provide the steps to reproduce.
N/A

What is the expected behavior?
N/A
If this is a feature request, what is motivation or use case for changing the behavior?
N/A
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
N/A
I think there might be a small typo under the Other Backers and Sponsors section of the README.

We want to acknowledge these sponsors and backers, but donations were not public and we are not sure of donors want to stay anonymous

... should instead read, "... and we are not sure if donors want to stay anonymous."
Just something that caught my eye. If it's too trivial, I can send in a PR and you guys can merge it at a later date along with other minor updates.
/cc @bebraw (because I think you're in charge of documentation)

Yeah, PR please. 👍

I will submit a PR as soon as I get off work!
Another thing that I noticed is that the links to the backers are a bit-off. For eg., Addy Osmani's picture redirects you to Cory House's profile. Just thought I should give you a heads-up for that as well.

@yeskunall I wonder if that's fixable too... The problem might be on Open Collective's side.

@bebraw you are right, it looks like it's a fault on OpenCollective's end. I think it'd be wise to let the guys at OpenCollective know about this. Maybe open up an issue on their repo?

@yeskunall Please do that. https://github.com/OpenCollective/opencollective-website might be the right place. 👍

Will do, @bebraw. As for the grammatical fix, like I said, the PR will be in ASAP. ❤

Hey @bebraw, so the PR is in. #4728. ❤


[Bug] Could not resolve zrender dependency (pnpm/workspace)

Version
5.5.1
Link to Minimal Reproduction
https://github.com/danielleroux/pnpm-angular-issue
Steps to Reproduce

Clone https://github.com/danielleroux/pnpm-angular-issue
Execute pnpm install
Execute pnpm build

Current Behavior
Import echarts in app.module.ts leads to the following error stack:
my-demo-module:build: ✘ [ERROR] Could not resolve "zrender/lib/core/util.js"
my-demo-module:build:
my-demo-module:build:     node_modules/echarts/lib/visual/visualDefault.js:45:24:
my-demo-module:build:       45 │ import * as zrUtil from 'zrender/lib/core/util.js';
my-demo-module:build:          ╵                         ~~~~~~~~~~~~~~~~~~~~~~~~~~
my-demo-module:build:
my-demo-module:build:   You can mark the path "zrender/lib/core/util.js" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.
my-demo-module:build:
my-demo-module:build:
my-demo-module:build: ✘ [ERROR] Could not resolve "zrender/lib/core/util.js"
my-demo-module:build:
my-demo-module:build:     node_modules/echarts/lib/visual/visualSolution.js:45:24:
my-demo-module:build:       45 │ import * as zrUtil from 'zrender/lib/core/util.js';
my-demo-module:build:          ╵                         ~~~~~~~~~~~~~~~~~~~~~~~~~~
my-demo-module:build:
my-demo-module:build:   You can mark the path "zrender/lib/core/util.js" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.

Expected Behavior
ECharts needs to resolve dependency inside a workspace (pnpm)
Environment
- OS: macOS

Any additional comments?
No response

same issue here, any updates?


Empty folders don't appear in trash

Since folders are ignored in the file copy logic, dragging an empty folder to the trash just removes it and doesn't actually move to the trash.

This happens across the board for all file actions.


Automate releases on GitHub

This automates generation of blueprint release by using GitHub Actions feature.
This is triggered only when a git tag with proper folder name is created.
For example:
Suppose you want to now create a new release for self building factory v6.0.2

Git tag should be self-building-factory-6.0.2.
This workflow will then search for self-building-factory folder & build (encode) the blueprint using fatul.
Encoded blueprint file name will be self-building-fatory-6.0.2.txt
Once encoding/building is done, it will automatically create a github release with the name Self Building Factory 6.0.2 & attach the blueprint file

Here is how it will look

I have added the new regex.
Along with that, I modified the workflow to include latest changelog whenever a new release gets published.
Additionally I fixed the formatting to one Changelog file & moved json files of brians-train-auxilary into book subfolder.
This should be now good to go 🤔


[Feature Request] Toggle to Disable Joystick's "Double-tap to Sprint?"

Hello! I love Controllable (and use it all of the time), but I find that the joystick's "double-tap to sprint" mechanic is quite sensitive. While I'm digging underwater, I often end up accidentally activating swimming mode, and since I'm facing the ground, I involuntarily start swimming downwards. This makes it difficult to swim back up to the surface to catch my breath, unless I take a second to rotate the camera all the way back up. I was wondering if a toggle to disable double-tap to sprint could be implemented? If you can't implement that, could you at least increase the time between double-tapping that it takes to activate swimming mode while underwater in a future update? Thanks in advance!

Absolutely second this. Double tap to sprint is incredibly frustrating and it would be amazing to have the option to disable.


specify postgres version in installation?

@macintoshhelper  I'm not sure whether this is necessary, or if apt-get will automatically take the most recent version?
But since students in FAC10 have had issues before, with having a version that was too old to use some postgres syntax, it might be prudent to specify sudo apt-get -y install postgresql-9.6 in place of this in setup.md:

sudo apt-get -y install postgresql postgresql-contrib

Note: the docs suggest that postgresql-contrib-9.6 automatically comes with apt-get install postgresql-9.6

If people do apt-get update, it should update their package lists to have the latest version. It's probably best to avoid installing specific versions to avoid the need for frequent updates or being out-of-date.
I believe this may be caused by having outdated Ubuntu versions. apt often has outdated software packages, so I'll add instructions for setting up PostgreSQL's apt repository.

Beautiful :heart:


Implement 'config' CLI command.

Overview
Renames config to generate-config and implements a new config command that generates the configuration file based on the current state instead of printing a static string.
Fixes #375, #366.

@codysoyland was the work done here your intention with #375?
it seems like you weren't expecting pilosa config to take any arguments (other than host i suppose?), but at that point it becomes a client to a running pilosa server. I think that's causing confusion with @linhvo as well.

Coverage increased (+0.01%) to 66.714% when pulling 3960345fe0d0ebf949da44a7be06bec66ec96b33 on benbjohnson:375-config into 4a14e38ebeffe1a1a3f1a38069f21e7394e7032e on pilosa:master.

The way that @benbjohnson implemented this is the way I expected it to work. It seems that there is a misunderstanding over intended functionality. If I understand correctly, @linhvo expects that pilosa config (with no arguments) will connect to a running pilosa server and fetch and print out the configuration (correct me if I'm wrong). The reason it prints out the default configuration is because it's not connecting to the existing server and it's not started with the --config flag to tell it what config file to use as a base. @benbjohnson's example with flags works for me: pilosa --config /tmp/pilosa.conf config --data-dir "/foo/bar". We just need to document this clearly. I can see the value in having a client be able to fetch the config from the server, but that would be a separate project.
To summarize:

Behavior #1: pilosa [--config $file] config --arguments takes the same arguments as pilosa server and prints the "final" configuration values.
Behavior #2: pilosa config connects to existing pilosa server as a client, fetches the config values, and prints them.

Behavior #1 is my preference.
I did notice a small bug in this though -- the time values produced by pilosa config are large integers without units. Unsure the reason for this. If I write it out to a file and try to use it, it results in Error: time: missing unit in duration<PHONE_NUMBER>00.

@codysoyland: Oh I see, I expected behavior number 2 as you mentioned, as I understand from reading ticket #375. Sorry if I missed read it. If behavior 1 is expected then what Ben implemented work then

@codysoyland Fixed the duration encoding in 788386b. It looks like pelletier/go-toml has its own Marshaler interface. https://godoc.org/github.com/pelletier/go-toml#Marshaler
@linhvo Let me know if there's anything else that needs to be fixed.

Coverage decreased (-0.007%) to 66.704% when pulling 788386b49acabd637d17cdee9e7b713e6fc56d72 on benbjohnson:375-config into 7693fc42113feaf1dd08983bf93ce76611f2a25d on pilosa:master.


Automated Package Upgrade

:tada: This PR is included in version 5.0.438 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


New opa policies v1 sto 6934

Previews:

STO doc > Use STO > Stop builds based on scan results > Use governance policies and security scan results to stop STO pipelines automatically
STO release notes > Version TBD
Platform docs > Governance > Policy samples > Security Tests policy samples

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d903311d98156566d89c10--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d90c5cc4acfb60dc8569fe--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d9136961370c64e687c8aa--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65de6ed8334cc45cf164a1e1--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65de6f9f6a01e15885d89c59--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65e003b0b3e646b1d20e7cda--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65e00454ff26f9b5c8066c2a--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65e09e7234cac811224ae278--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65e0ffaa782a513bcc30ffe1--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65e208648e48ce023b96d1d8--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65e22e37d8f1941236a768d1--harness-developer.netlify.app


Support whenMatched().deleteAndInsertAll() for merge command

My goal is to perform the following sequence of actions in single merge transaction:

Join source DF with target Delta table on id column
Delete any existing IDs from the target table
Append the source DF into the target table

If my ID column was unique, this could have been achieved with a merge on id, followed by whenMatched().updateAll().whenNotMatched().insertAll(). However, in my use-case it is very common that I'd have several rows with the same ID, and I can't add any more columns to the merge clause to make it unique. Here's an example to illustrate:
import io.delta.tables._
case class MetricRow(id: Integer, key: String, value: Double)

val initialDF = spark.createDataFrame(Seq(
    MetricRow(1, "x", 1),
    MetricRow(1, "y", 2))
)
initialDF.write.format("delta").save("/tmp/delta_merge_example")

val mergeDF = spark.createDataFrame(Seq(
    MetricRow(1, "x", 3),
    MetricRow(1, "z", 4),
    MetricRow(1, "w", 5))
)
DeltaTable.forPath("/tmp/delta_merge_example").alias("T")
    .merge(mergeDF.alias("S"), "S.id=T.id")
    .whenNotMatched().insertAll()
    .whenMatched().updateAll()  // this is where the problem lies
    .execute()

This will raise an UnsupportedOperationException:
Cannot perform MERGE as multiple source rows matched and attempted to update the same
target row in the Delta table. By SQL semantics of merge, when multiple source rows match
on the same target row, the update operation is ambiguous as it is unclear which source
should be used to update the matching target row.
You can preprocess the source table to eliminate the possibility of multiple matches.

Since I can't deduplication and update are not an option, I thought about adding support for .deleteAndInsertAll() command after .whenMatched(), because I don't want to delete the files in one transaction, and then insert them in another (due to consistency concerns). It should be logically equivalent to the following code:
DeltaTable.forPath("/tmp/delta_merge_example").alias("T")
    .merge(mergeDF.alias("S"), "S.id=T.id")
    .whenMatched().delete()
    .execute()
mergeDF.write.format("delta").mode("append").save("tmp/delta_merge_example")

Is it possible to do both of these actions in a single merge command?

I think you're looking for an arbitrary replaceWhere which is being worked on here:
https://github.com/delta-io/delta/pull/436

Thanks @brkyvz, that's exactly what I need :)
I'll close this issue and monitor the PR you mentioned closely.


Adjust the team

Currently we are missing some people from the group, and some people are still listed as active members when they have moved on from the group. We need to add Egor and Aishwarya to the current team, and we need to move Liam from the active team.
This opens up a question of how do we want to classify people who have left the team? Should we separate past members and alumni? Any thoughts are welcome.

Also add Jinghao - maybe as a dual affiliation or something with his home lab.

Currently we are missing some people from the group, and some people are still listed as active members when they have moved on from the group. We need to add Egor and Aishwarya to the current team, and we need to move Liam from the active team.
This opens up a question of how do we want to classify people who have left the team? Should we separate past members and alumni? Any thoughts are welcome.

I usually see them listed as Alumni in other websites. Lets follow this convention


Cannot access a disposed object. Object name: 'Square.OkHttp3.OkHttpClient'.

I am seeing the following exception occurring often in Android 9.0 devices. It was not occurring in v 3.4.2 of the package. There was an update made for OkHttp3 nuget package in v 3.4.3. Is that causing this?
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'Square.OkHttp3.OkHttpClient'.
at Java.Interop.JniPeerMembers.AssertSelf (Java.Interop.IJavaPeerable self) [0x00029] in :0
at Java.Interop.JniPeerMembers+JniInstanceMethods.InvokeVirtualObjectMethod (System.String encodedMember, Java.Interop.IJavaPeerable self, Java.Interop.JniArgumentValue* parameters) [0x00000] in :0
at Square.OkHttp3.OkHttpClient.CookieJar () [0x0000a] in <33fa226edb0e455ab4097ae9978172a6>:0
at ModernHttpClient.NativeMessageHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x001ad] in <1b85d0c61a414b069649f869d567f362>:0

Let me try to reproduce the issue.


Export ignore

The main topic of this PR is removing scripts, RELEASE.md and Git-related files from release tarballs.
It also includes minor changes to the make-release script.

Closing here. I added relevant commit from this PR to # 7.


Make at least pinot-admin.sh work with BusyBox (/bin/sh)

Particularly in Docker, we're a bit better off when we can use a limited shell like BusyBox to perform commands instead of relying on bash. For example, this allows either Alpine or Distroless+BusyBox to be used.
Right now, if you try to use pinot-admin.sh with BusyBox (as /bin/sh), it fails for what's likely a resolvable thing.
./bin/pinot-admin.sh: line 32: syntax error: unexpected word (expecting ")")

you can see that using distroless + busybox with little modifications otherwise shaves a significant amount off the image size:
$ docker images |grep pinot
pinot                                     test                e1c4f1f12d71        5 minutes ago       339MB
apachepinot/pinot                         0.4.0               8c4112171ff7        7 weeks ago         661MB

FROM apachepinot/pinot:0.4.0 as pinot

FROM openzipkin/jre-full:14.0.2-14.29.23

ENV PINOT_HOME=/opt/pinot

VOLUME ["${PINOT_HOME}/configs", "${PINOT_HOME}/data"]

COPY --from=pinot ${PINOT_HOME} ${PINOT_HOME}

# expose ports for controller/broker/server/admin
EXPOSE 9000 8099 8098 8097 8096 9514

WORKDIR ${PINOT_HOME}

ENTRYPOINT ["/bin/sh", "./bin/pinot-admin.sh"]

CMD ["run"]

ps don't get too distracted about the JRE 14 the issue is in the shell script not the JRE, and 1.8 is even smaller ex basing on openzipkin/jre-full:1.8.0_252
pinot                                     test                9d7aabf0de28        33 seconds ago      244MB

Current Pinot image is based on image: openjdk:8-jdk-slim ( https://github.com/apache/incubator-pinot/blob/master/docker/images/pinot/Dockerfile#L62)
pinot-admin.sh is a bash script generated from the template: https://github.com/apache/incubator-pinot/blob/master/pinot-tools/src/main/resources/appAssemblerScriptTemplate

https://github.com/apache/incubator-pinot/pull/5818
If you want a smaller image also, we can do that in another change. This just makes a smaller one possible. I tested it locally.


Older Production Library URL version

Isn't the latest cdn link for office js library have version 1.1? https://appsforoffice.microsoft.com/lib/1.1/hosted/office.js.

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

ID: 3c7080b5-9791-e1ca-ff77-ae3dbe5f10cc
Version Independent ID: 1207aec0-6183-53bb-2768-ebb39d09ed99
Content: Excel JavaScript API requirement sets - Office Add-ins
Content Source: docs/reference/requirement-sets/excel-api-requirement-sets.md
Product: excel
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

Hi @zakhan4,
Thanks for the question. I'll look into the difference between the /1/ and /1.1/ CDN endpoints. Both are regularly updated and should have the libraries you need.


Possibly a wrong parameter in prjxray/util.py

Should part_mapping here be res_mapping instead? Because get_part_resources() does not have a variable called part_mapping.
https://github.com/SymbiFlow/prjxray/blob/5349556bc2c230801d6df0cf11bccb9cfd171639/prjxray/util.py#L67
At the moment I don't know what tool calls this function though, so I can't test out yet.

Yes, it looks like a cut-and-paste error from line 48.   @acomodi what do you think?

Update:
Yep, it's definitely wrong. I altered get_part_resources() to look like this (manually set part to an invalid value "blah"):
def get_part_resources(file_path, part):
    filename = os.path.join(file_path, "resources.yaml")
    assert os.path.isfile(filename), \
        "Mapping file {} does not exists".format(filename)
    with open(filename, 'r') as stream:
        res_mapping = yaml.load(stream, Loader=yaml.FullLoader)
    part="blah"
    res = res_mapping.get(part, None)
    assert res, "Part {} not found in {}".format(part, part_mapping)
    return res

Then ran source settings/spartan7.sh and got this:
Traceback (most recent call last):
  File "/home/test/prjxray/utils/create_environment.py", line 66, in <module>
    main()
  File "/home/test/prjxray/utils/create_environment.py", line 59, in main
    environment = get_environment_variables()
  File "/home/test/prjxray/utils/create_environment.py", line 39, in get_environment_variables
    resources = get_part_resources(res_path, os.environ['XRAY_PART'])
  File "/home/test/prjxray/prjxray/util.py", line 68, in get_part_resources
    assert res, "Part {} not found in {}".format(part, part_mapping)
NameError: name 'part_mapping' is not defined

By changing part_mapping to res_mapping, I got the expected assertion error:
Traceback (most recent call last):
  File "/home/test/prjxray/utils/create_environment.py", line 66, in <module>
    main()
  File "/home/test/prjxray/utils/create_environment.py", line 59, in main
    environment = get_environment_variables()
  File "/home/test/prjxray/utils/create_environment.py", line 39, in get_environment_variables
    resources = get_part_resources(res_path, os.environ['XRAY_PART'])
  File "/home/test/prjxray/prjxray/util.py", line 68, in get_part_resources
    assert res, "Part {} not found in {}".format(part, res_mapping)
AssertionError: Part blah not found in {'xc7s50csga324-1': {'pins': {0: 'P14', 1: 'L13', 2: 'C12', 3: 'J5'}}, 'xc7s50csga324-1IL': {'pins': {0: 'P14', 1: 'L13', 2: 'C12', 3: 'J5'}}, 'xc7s50csga324-2': {'pins': {0: 'P14', 1: 'L13', 2: 'C12', 3: 'J5'}}, 'xc7s50fgga484-1': {'pins': {0: 'U20', 1: 'N15', 2: 'C15', 3: 'R3'}}, 'xc7s50fgga484-1IL': {'pins': {0: 'U20', 1: 'N15', 2: 'C15', 3: 'R3'}}, 'xc7s50fgga484-2': {'pins': {0: 'U20', 1: 'N15', 2: 'C15', 3: 'R3'}}, 'xc7s50ftgb196-1': {'pins': {0: 'D14', 1: 'E11', 2: 'B6', 3: 'L5'}}, 'xc7s50ftgb196-1IL': {'pins': {0: 'D14', 1: 'E11', 2: 'B6', 3: 'L5'}}, 'xc7s50ftgb196-2': {'pins': {0: 'D14', 1: 'E11', 2: 'B6', 3: 'L5'}}}

I guess nobody reported this before because the resources.yaml file generated by update_resources.py is always correct, which makes the assertion always true, so the part_mapping mistake never shows. On the bright side, this proves that update_resources.py is very robust!


Idea: bots can join battlefields and arenas

Would be great if bots could fill up into the battlefield or arena

I think that's already the intent, (There's even a video of the Ike3 bots in either BG/arena don't remember which functioning quite well) but as of right now, they just have stability issues that need ironing out to get them in the instances.

Thank you for share the idea! Yes, this is already supported and should work once the other issues with the bots are all resolved.