[📚] "Improve iOS Build Times" specify incorrect pod version for Flutter 2.0

The Improve iOS Build Times documentation suggests to specify the FirebaseFirestore pod using version 6.26.0.
When building with Flutter 2.0 & the latest Firebase depdency versions, this causes the following build failure:

Resolving dependencies of Podfile
CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_0_3_5.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.6.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_5_d_c.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/5/d/c/Mantle/2.1.6/Mantle.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_e_9_d.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/9/d/SDWebImageWebPCoder/0.8.2/SDWebImageWebPCoder.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_d_4_0.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/d/4/0/GoogleSignIn/5.0.2/GoogleSignIn.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_6_d_6.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/6/d/6/libPhoneNumber-iOS/0.9.15/libPhoneNumber-iOS.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_f_4_e.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/f/4/e/FMDB/2.7.5/FMDB.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_b_3_c.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/b/3/c/FBSDKLoginKit/9.0.1/FBSDKLoginKit.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_3_7_4.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/3/7/4/TOCropViewController/2.6.0/TOCropViewController.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_f_2_a.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/f/2/a/FirebaseRemoteConfig/7.6.0/FirebaseRemoteConfig.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/f/2/a/FirebaseRemoteConfig/7.3.0/FirebaseRemoteConfig.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_d_c_1.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/d/c/1/FirebaseABTesting/7.6.0/FirebaseABTesting.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_8_b_d.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/8/b/d/FirebaseCore/7.6.0/FirebaseCore.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_2_f_7.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/2/f/7/FirebaseInstallations/7.6.0/FirebaseInstallations.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_0_8_4.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.2.2/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.0.0/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.1.0/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.1.1/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.2.0/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.2.2/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.0.0/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.1.0/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.1.1/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.2.0/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.2.2/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_3_c_c.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/3/c/c/FirebaseStorage/7.6.0/FirebaseStorage.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_2_d_6.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/2/d/6/FirebaseMessaging/7.6.0/FirebaseMessaging.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/f/4/e/FMDB/2.7.5/FMDB.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/f/4/e/FMDB/2.7.5/FMDB.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_e_5_6.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/5/6/FirebasePerformance/7.6.0/FirebasePerformance.podspec.json exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: all_pods_versions_e_7_d.txt exists! Returning local because checking is only perfomed in repo update
CDN: trunk Relative path: Specs/e/7/d/FirebaseCrashlytics/7.6.0/FirebaseCrashlytics.podspec.json exists! Returning local because checking is only perfomed in repo update
[!] CocoaPods could not find compatible versions for pod "FirebaseFirestore":
In Podfile:
FirebaseFirestore (from https://github.com/invertase/firestore-ios-sdk-frameworks.git, tag 6.26.0)
    cloud_firestore (from `.symlinks/plugins/cloud_firestore/ios`) was resolved to 1.0.0, which depends on
      Firebase/Firestore (= 7.3.0) was resolved to 7.3.0, which depends on
        FirebaseFirestore (~> 7.3.0)

Updating the pod version from 6.26.0 to 7.3.0 fixes the issue, so maybe this should be mentioned in the documentation?

The iOS version has been updated to 7.3.0 in the documentation. Thanks for the feedback!


Vim not able to make on Travis CI

Hi
I noticed that my custom build is failing due to im_is_active
Here is what the build is doing
git clone https://github.com/vim/vim
./configure --with-features=huge --enable-rubyinterp --enable-pythoninterp
make -j4

Here is what I got today; I am not sure in each patch this started
mbyte.c: In function ‘im_set_active’:
mbyte.c:5925:6: error: ‘im_is_active’ undeclared (first use in this function)
      im_is_active = active;
      ^
mbyte.c:5925:6: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [objects/mbyte.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory `/home/travis/build/mboughaba/vim-lessmess/vim/src'
make: *** [first] Error 2

This is strange because it is well declared in mbyte
void im_set_active(int active_arg)

Cheers,
Mo

Thank you so very much, build is green again.
On a project of this scale, this is the fastest reaction I've ever saw :+1:
Cheers,
Mo.


3.0 architecture revamp/9274/adapt ted policy

Proposed changes:

fix https://github.com/RasaHQ/rasa/issues/9274
adapt Policy interface to GraphComponent interface

adapt persistence to use ModelStorage and Resources
add required parameters to create, load and the constructor
move featurizer instantiation within policy (was done in PolicyEnsemble before)

adapt TEDPolicy to `GraphComponent interface

adapt persistence to use ModelStorage and Resources
add required parameters to create, load and the constructor

adapt PolicyTestCollection to change Policy interface
adapt all TEDPolicy unit tests to work with new policy

Things you shouldn't have a look at ⛔

please don't have a look at the modules prefixed with _ as they only contain the old but duplicated code

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

Please discontinue these emails!!!
Lorraine (Lou) Y. Pawlivsky-Love
@.***
tel<PHONE_NUMBER>
http://www.silverquill.org

On Aug 10, 2021, at 3:33 AM, Tobias Wochinger @.***> wrote:

@wochinge commented on this pull request.
In rasa/core/policies/policy.py:

@@ -272,43 +295,6 @@ def _featurize_for_prediction(
== SupportedData.ML_DATA,
)

def train(
I deleted them since there is no rule what a graph component receives as parameter during training or running (this only depends on the needs section)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@Silverquillgrp Sorry, I've no clue why GitHub subscribed you this PR. Commenting probably made it even worse 🙈 You can unsubscribe with the button shown in the screenshot

Another reason why you might get notifications for this repository is maybe that you clicked on watch (if you scroll all they way up then there is a button on the top right corner)

Thanks...I was under the impression that I was participating in the Apple letter about privacy concerns....cheers, Lorraine

@aeshky @ka-bu @joejuzl Could you please give this PR a code review so that I can merge it? 🙌🏻


Batch assign function for Issues

Some sort of higher level check box to select and assign many issues to depts/people so PMs don't have to open every issue and assign.
Thanks Bye

Expect that this won't be done in time for beta will push to 1.0.0 release.

Great ideal @lewbager would save a lot of time going through each item.

This is partly done now, but I still want to ideally add assigning issues to this which will be a little more complex, hopefully get it done in the next few days.


Price Data Changes

[x] Strip decimals past 2 or 3 places.

[x] Only give me an array with one set of price info.

[ ] Timestamp needs to include hour/min/sec.

H/M/S is dropped since we're displaying daily price.

Swap to MM/DD/YY format.


Grammatical mistake

Chapter 1, Index Page
import Head from 'next/head';
const Index = () => (

      <title>Index page</title>
      <meta name="description" content="This is description of Index page" />

Content on Index page

);

export default Index;

<meta name="description" content="This is description of Index page" />
Should be re-written to 'This is the description of the Index page'
I realise this is a very trivial improvement, but my hope is that it simply adds to the overall professionalism of the book, which is otherwise very high.
I have noticed other small typos; please let me know if and how you would like these submitted/corrected.
Best wishes,
Rick

@whitefire0 thanks for pointing out these fixes! We welcome any improvement to our book.
I will update the text in the book. Would you like to create a pull request to fix this line in the code for the book (/book folder of our repo)?
I see that it appears in these 2 places:
https://github.com/builderbook/builderbook/blob/master/book/1-end/pages/index.js
https://github.com/builderbook/builderbook/blob/master/book/2-end/pages/index.js
If you see anything else that can be improved, feel free to create another issue or submit a pull request.


feat: define single prop and emit macro

Description

This PR will add 2 new macros to the project, defineProp & defineEmit.
This will allow users to define props & emits multiple times and also organize better the code
Linked Issues
Fix #294
Additional context

I use defineProps package as a base to create these macros, so please check if is everything ok with file/folder structure and other definitions like packages.json name, tags, etc..,

Thanks for your awesome work! It has been released as v1.10.2, but there are no docs about it yet. Would you like to add some docs?

Thanks for your awesome work! It has been released as v1.10.2, but there are no docs about it yet. Would you like to add some docs?

Sure I will make it on the weekend


Updated version for task and extension. Added change log to readme.

Looks good. We should think a bit more on how to maintain changelogs (I think it is a nice idea :+1:)


[GTK4] support

Hello,
do you plan to create GTK 4 bindings after GTK 3.90 release, or will be a branch following GTK 4 development?

We don't have any specific plans for GTK 4 and I'm not sure there's enough information to plan anything at this point. Personally, I'd give them time to make all the breaking changes first and look into this closer to the stable 4.6 release. 3.90 doesn't seem like an interesting target to me. Regrettably, we haven't even embraced 3.18-3.22 yet.

@gkoz The stable release will be GTK 4.0 not 4.6. I think it will be 3.90, 3.92, 3,94 and the stable 4.0, but it 4.0 maybe happen after 3.92.

Has anything changed since "Gtk 4.0 is not Gtk 4"?

@gkoz Yes, here is the latest. latest I think
https://blog.gtk.org/2016/09/01/versioning-and-long-term-stability-promise-in-gtk/

Thanks for the link, I wasn't aware of that change. Putting aside version number specifics, the stable release still isn't on the roadmap and targeting unstable ones doesn't feel like a priority.

@gkoz Technically 3.9x isn't unstable, it is not a stable API, similar to the whole 3.xx cycle anyway. For example GNOME will update their apps on 3.9x.
The point of 4.0 is a stable API and LTS, and then it will be GTK 5.0

Well, on most distribution, it still GTK 3.x and I don't think they'll switch anytime soon unfortunately.

@GuillaumeGomez They wont switch. GTK3 and GTK4 play in parallel, there are different headers. Fedora (26) and Arch for sure will ship GTK4 when GNOME 3.24 is out. It is like dependency :)

Oh, I see. My bad, I thought it was the next "step".

@GuillaumeGomez I have some comments from developers about GTK4 porting here
https://plus.google.com/+WorldofGnomeOrg/posts/FbtcRMHuJny
And this video shows GTK4 running together with GTK3 on JHBuild, which is exactly like /usr enviroment
https://www.youtube.com/watch?v=mq5JiY_W2N0

Any updates on this now that Gtk+ 3.90 has been released?

@dariost: Absolutely not. I'll need to check this out.


Add a search interface to the Postgres DB.

First start Postgres, e.g. with docker/serve.sh. Then start the web server with ./serve.sh. A demo is currently running at http://<IP_ADDRESS>:8080/
The user interface design is not final; it is just meant to demonstrate the query semantics. Those semantics are modeled in a machine-friendly form with a new class in query.py called "Predicate".
The full query structure is maintained in the URL so results can be hyperlinked.
This introduces a new dependency on jQuery-UI to make the little similarity threshold slider.

In general I think the interface could be simplified by mirroring the predicate structure (which I like) in the UI. For instance, the top-level choice would be (1) reaction ID, (2) reaction SMARTS, or (3) inputs/outputs.
The inputs/outputs tab/section would have a list of predicates (w/ add/remove options)---each input/output predicate would be independent, representing a single molecule, and have selectors for (a) input/output, (b) exact/substructure/similarity, (c) similarity threshold.

I'd like to take another pass on the predicate logic on the backend; @antonkast-google and I discussed and it might be simplest to merge this and edit rather than trying to merge PRs.
Anton: Please pull the latest changes into your branch so this can be merged into main and then I'll merge. Thanks!


Updated README with new screenshots and content

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

v0.101.0
GitHub release

Your semantic-release bot :package::rocket:


feat: Init HPA workaround

HPA workaround
Case A: Default case. .Values.glueSingleton.enabled = false then
app:
  glueSingleton:
    enabled: false
  hpa:
    enabled: false
    maxReplicas: 10
    minReplicas: 5
  image:
    repository: wandb/local-dev
    tag: 0.60.0-pre-hpa.0

The app deployment is created with GLUE_ENABLED = true which is a no-op
The app pod will not set ONLY_SERVICE
The glue deployment not created

This is a noop for existing deployments.

Case B: This is the case where we want to run the glue container in addition  to the app container. .Values.glueSingleton.enabled = true then:
app:
  glueSingleton:
    enabled: true
  hpa:
    enabled: true
    maxReplicas: 10
    minReplicas: 5
  image:
    repository: wandb/local-dev
    tag: 0.60.0-pre-hpa.0

The app deployment is created with GLUE_ENABLED = false
The app pod will not set ONLY_SERVICE
The glue deployment is created with GLUE_ENABLED = true
The glue pod will set ONLY_SERVICE = "gorilla-glue"

HPA note
HPA will only be enabled if both of these are set to true. So it is possible to run glue separately from the app pod and both of them be singletons. The glue pod will always be a singleton.
app:
  glueSingleton:
    enabled: false
  hpa:
    enabled: false

Final notes
To make this work we will be dependent on the next release of the wandb/local image.
There is a pre-image that can be used for testing as shown above.

Looks like linting has been broken for a while.

@jsbroks, do we need the kubernetes cluster for the wandb legacy chart?

@zacharyblasczyk I'm gonna need a little bit of time to spin up on HPA to understand this PR fully. I'll be reading up on that today. If it's more urgent please ping me and I'll prioritize my +1


Clicking create game before entering player

When entering the last player it's very easy to click start game when you have a name still ready to add
We should add a dialog to confirm you want to create the game or add the player before creating the game

was fixed in https://github.com/Eddcakes/mini-golf-scores/pull/15


Issue with k8s.io/docs/user-guide/walkthrough/

This is a...

[x] Feature Request
[ ] Bug Report

Problem:
The docs give the following command:
$ kubectl create -f docs/user-guide/walkthrough/pod-nginx.yaml
However, there is no YAML file with this name in kubernetes/examples
There are multiple ways I can work around this (copy from clipboard above, or click on the link to download), but the lack of this file from the kubernetes repo made me think I did something wrong in a previous step. I noticed that the file path given matches the link URL:
https://kubernetes.io/docs/user-guide/walkthrough/pod-nginx.yaml
...so I was confused about why I couldn't find it in my cloned copy of the docs.
I included my terminal log below so you can see what I was trying to do.
Proposed Solution:
At the top where it says "make sure you have the example directory locally", provide specific instructions (git clone ...) Is there a separate docs repo I should have cloned instead of the kubernetes main repo to get the walkthrough files? If so, it should be referenced here.
If the path given in the docs for this YAML file is incorrect or out of date, the docs should also be updated to reflect this.
Page to Update:
https://kubernetes.io/docs/user-guide/walkthrough/

I looked for this YAML file on both the master branch and release-1.10

rmorrise@rmorrise-003936 MINGW64 /d/src/github
$ git clone https://github.com/kubernetes/kubernetes.git
Cloning into 'kubernetes'...
remote: Counting objects: 728506, done.
remote: Compressing objects: 100% (138/138), done.
remote: Total 728506 (delta 78), reused 61 (delta 60), pack-reused 728308
Receiving objects: 100% (728506/728506), 528.49 MiB | 25.48 MiB/s, done.
Resolving deltas: 100% (497121/497121), done.
Checking connectivity... done.
Checking out files: 100% (16499/16499), done.

rmorrise@rmorrise-003936 MINGW64 /d/src/github
$ cd kubernetes/examples/

rmorrise@rmorrise-003936 MINGW64 /d/src/github/kubernetes/examples (master)
$ kubectl create -f docs/user-guide/walkthrough/pod-nginx.yaml
error: the path "docs/user-guide/walkthrough/pod-nginx.yaml" does not exist

rmorrise@rmorrise-003936 MINGW64 /d/src/github/kubernetes/examples (master)
$ cd ..

rmorrise@rmorrise-003936 MINGW64 /d/src/github/kubernetes (master)
$ kubectl create -f docs/user-guide/walkthrough/pod-nginx.yaml
error: the path "docs/user-guide/walkthrough/pod-nginx.yaml" does not exist

rmorrise@rmorrise-003936 MINGW64 /d/src/github/kubernetes (master)
$ find . -name "pod-nginx.yaml"

rmorrise@rmorrise-003936 MINGW64 /d/src/github/kubernetes (master)

@rmorrise The yamls used in https://kubernetes.io are in repo https://github.com/kubernetes/website.git.

@islinwb OK, thanks! Can the docs be updated to mention this?

Ran into the same issue and ended up running examples/https-nginx/nginx-app.yaml.
I suggest proposing to clone the website repo or as an alternative for users with svn:
svn export https://github.com/kubernetes/website/trunk/docs/user-guide/walkthrough


[Feature Request] el-link loading

Existing Component
Yes
Component Name
el-link
Description
Hi,
Is there a way to set loading attribute to display loading status just like el-button?
Thanks.

Hope to achieve the effect like this 😆

Do it like this
https://codepen.io/anon/pen/rgRjZK


Cannot define a module for a specific file extension in 2.4.1

TypeScript Version:  2.4.1
Code
// A *self-contained* demonstration of the problem follows...
declare module "*.vue" {
  import Vue from 'vue'
  export default typeof Vue
}

Expected behavior:
A file with the above content used to work when importing .vue files.
In 2.4.1 It looks like the file is not taken into account as every .vue file gets imported as "string"?
Actual behavior:
Everything seems to be imported as string?

That file is perfectly working in 2.3.4

The right hand side of an export default is an expression not a type. typeof Vue is just calling the regular JS typeof operator on the reference Vue; and that happens to be a string all the time..
This should have been an error to have an expression in an ambient context. the only possible value should be an identifier name. files https://github.com/Microsoft/TypeScript/issues/17991 to track it.
so for this definition, you need to change your declaration to be:
declare module "*.vue" {
    import Vue from 'vue'
    const _: typeof Vue;
    export default _;
}

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


Some problems when generating the dataset

Hello, thank you for your incredible work, I am working on rebuild a new dataset base on your method: Change the DATAGEN environment variable to 1 and run the leaderboard_evaluator_local.py to collect data. And I'd like to ask you for some advice.
However, the result shows the data_agent still get crashed during the simulation. I wonder whether this situation is common or not. If not, what can I do to avoid this bug? By the way, given that currently I can only find the collision after simulation, I'd like to know if the code could give me a feedback in time, so that I can split the dataset and use the valid part.
The route file I used is routes_training.xml
The agent I used is data_agent.py

I assume you mean vehicle crashes (and not software crashes here).
Yes the data_agent is not a perfect driver is also gets some collisions (as you can see in Table 6 and 7 under the Veh metric).
We skip those episodes during training by only considering data with 100 DS, see here.
There is no way to stop data collection on crashed routes in the released code.
You could implement it yourself if you want to, should not be too hard.
You can check the amount of routes where the vehicle crashed in the released dataset by running a training.
The value gets printed here.

Thank you for your advice! I will take your advice into consideration and proceed with another experiments to collect data.


Generic Error in GDI+ Crash

Scanner refuses to scan either weapons nor artifacts. It opens the tab and immediatly closes the menu afterwards.
Error log:
Erro genérico de GDI+.
em System.Drawing.Image.Save(String filename, ImageCodecInfo encoder, EncoderParameters encoderParams)
em System.Drawing.Image.Save(String filename, ImageFormat format)
em System.Drawing.Image.Save(String filename)
em InventoryKamera.WeaponScraper.GetPageOfItems()
em InventoryKamera.WeaponScraper.ScanWeapons(Int32 count)
em InventoryKamera.InventoryKamera.GatherData()
Erro genérico de GDI+.
em System.Drawing.Image.Save(String filename, ImageCodecInfo encoder, EncoderParameters encoderParams)
em System.Drawing.Image.Save(String filename, ImageFormat format)
em System.Drawing.Image.Save(String filename)
em InventoryKamera.ArtifactScraper.GetPageOfItems()
em InventoryKamera.ArtifactScraper.ScanArtifacts(Int32 count)
em InventoryKamera.InventoryKamera.GatherData()
(Translating, goes as "Generic error in GDI+". Replace all "em" for "in")

Also, I'm scanning at 1280x720 windoned. I use a 1366*768 monitor, so I slide the windows bottom bar to the left, so the whole game's window is visible on screen.
Whats funny tho is that 2 weeks ago, the last time I ran the app in 1.2.0, worked flawlesly. Tried to run at 1.2.0, the program crashed on the 6th weapon (in wich case is a lv 90 rust). Downloaded the last release version (1.2.2) and the program didnt crashed, but had it ignored and produced the error log above.

This is a strange one. I will have to see if I can reproduce this at all.


feat: add COJ info

Info icon next to COJ label

Mouseover the icon will give information about COJ

TIS21-6487
TIS21-6538

Hello Doris. I'm getting something a bit odd happening with the layout: 🤷

(You might be able to fix it just by adding something like
z-index: 100;
to the style :)

Wide screen:

Narrow screen:

I have also moved the tooltip box on the top so users can see the tooltip and COJ details at the same time.


Many symbols are lost when linking

"_IOServiceNameMatching", referenced from:
+[GPUUtilization utilizeDictionary] in GPUUtilization.o
"_IOIteratorNext", referenced from:
+[GPUUtilization utilizeDictionary] in GPUUtilization.o
"_IORegistryEntryGetChildIterator", referenced from:
+[GPUUtilization utilizeDictionary] in GPUUtilization.o
"_kIOMasterPortDefault", referenced from:
+[GPUUtilization utilizeDictionary] in GPUUtilization.o
"_IORegistryEntryCreateCFProperties", referenced from:
+[GPUUtilization utilizeDictionary] in GPUUtilization.o
"_IOServiceGetMatchingServices", referenced from:
+[GPUUtilization utilizeDictionary] in GPUUtilization.o
"_IOObjectRelease", referenced from:
+[GPUUtilization utilizeDictionary] in GPUUtilization.o
ios13.1.3

Sorry, just forgot to link the IOKit framework manually


Pinniped CLI version command should match kubectl version

I believe that pinniped version was meant to mirror kubectl version originally, but kubectl version behavior has significantly changed, starting with 1.28.
kubectl 1.27 behavior
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.4", GitCommit:"fa3d7990104d7c1f16943a67f11b154b71f6a132", GitTreeState:"clean", BuildDate:"2023-08-18T21:01:24Z", GoVersion:"go1.20.6", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.3", GitCommit:"25b4e43193bcda6c7328a6d147b1fb73a33f1598", GitTreeState:"clean", BuildDate:"2023-06-15T00:36:28Z", GoVersion:"go1.20.5", Compiler:"gc", Platform:"linux/amd64"}
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.

kubectl 1.28 behavior
$ kubectl version
Client Version: v1.28.0
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.3
$ kubectl version -o json
{
  "clientVersion": {
    "major": "1",
    "minor": "28",
    "gitVersion": "v1.28.0",
    "gitCommit": "855e7c48de7388eb330da0f8d9d2394ee818fb8d",
    "gitTreeState": "clean",
    "buildDate": "2023-08-15T10:15:49Z",
    "goVersion": "go1.20.7",
    "compiler": "gc",
    "platform": "darwin/amd64"
  },
  "kustomizeVersion": "v5.0.4-0.20230601165947-6ce0bf390ce3",
  "serverVersion": {
    "major": "1",
    "minor": "27",
    "gitVersion": "v1.27.3",
    "gitCommit": "25b4e43193bcda6c7328a6d147b1fb73a33f1598",
    "gitTreeState": "clean",
    "buildDate": "2023-06-15T00:36:28Z",
    "goVersion": "go1.20.5",
    "compiler": "gc",
    "platform": "linux/amd64"
  }
}

Proposed interaction for pinniped version:
$ pinniped version
v1.2.3
$ pinniped version -o json
{
  "major": "1",
  "minor": "2",
  "gitVersion": "v1.2.3",
  "gitCommit": "abc123",
  "gitTreeState": "clean",
  "buildDate": "2023-08-15T10:15:49Z",
  "goVersion": "go1.20.7",
  "compiler": "gc",
  "platform": "darwin/amd64"
}

NOTE: edited to include major and minor in the output.
Example showing the ease of implementation
// gitVersion is set using a linker flag:
// -ldflags "-X 'go.pinniped.dev/cmd/pinniped/cmd.gitVersion=v9.8.7'"
var gitVersion string

func printOtherInfo(writer io.Writer) {
	info := apimachineryversion.Info{
		GitVersion:   gitVersion,
		GitCommit:    "",
		GitTreeState: "clean",
		BuildDate:    "",
		GoVersion:    runtime.Version(),
		Compiler:     runtime.Compiler,
		Platform:     fmt.Sprintf("%s/%s", runtime.GOOS, runtime.GOARCH),
	}

	if debugBuildInfo, ok := debug.ReadBuildInfo(); ok {
		for _, buildSetting := range debugBuildInfo.Settings {

			switch buildSetting.Key {
			case "vcs.revision":
				info.GitCommit = buildSetting.Value
			case "vcs.time":
				info.BuildDate = buildSetting.Value
			case "vcs.modified":
				info.GitTreeState = "dirty"
			}
			fmt.Printf("buildSetting: %s=%s\n", buildSetting.Key, buildSetting.Value)
		}
	}

	fmt.Fprintf(writer, "%#v\n", info)
}

Note that this example provides output in the original (deprecated) format, but shows that the data values are set correctly.

For reference, the current pinniped version output looks like:
pinniped version
version.Info{Major:"0", Minor:"25", GitVersion:"v0.25.0", GitCommit:"c7b49d9b93d9f293f81f270054e9f67c2ba7f181", GitTreeState:"clean", BuildDate:"", GoVersion:"go1.20.7", Compiler:"gc", Platform:"darwin/amd64"}

Here's how this simplification might look at build time.
Building without any linker flags at all
% pinniped_binary=`mktemp`
% go build -o $pinniped_binary ./cmd/pinniped
% $pinniped_binary version
v0.0.0-38485095-dirty
% $pinniped_binary version -o json
{
  "major": "0",
  "minor": "0",
  "gitVersion": "v0.0.0-38485095-dirty",
  "gitCommit": "384850953501b7d66d466b4ca4d13a81bc54a7c3",
  "gitTreeState": "dirty",
  "buildDate": "2023-08-22T22:06:17Z",
  "goVersion": "go1.21.0",
  "compiler": "gc",
  "platform": "darwin/amd64"
}
% $pinniped_binary version -o yaml
buildDate: "2023-08-22T22:06:17Z"
compiler: gc
gitCommit:<PHONE_NUMBER>01b7d66d466b4ca4d13a81bc54a7c3
gitTreeState: dirty
gitVersion: v0.0.0-38485095-dirty
goVersion: go1.21.0
major: "0"
minor: "0"
platform: darwin/amd64

Building with just the one single linker flag
% pinniped_binary=`mktemp`
% go build -o $pinniped_binary -ldflags "-X 'go.pinniped.dev/internal/pversion.gitVersion=v9.8.7'" ./cmd/pinniped
% $pinniped_binary version
v9.8.7
% $pinniped_binary version -o json
{
  "major": "9",
  "minor": "8",
  "gitVersion": "v9.8.7",
  "gitCommit": "384850953501b7d66d466b4ca4d13a81bc54a7c3",
  "gitTreeState": "dirty",
  "buildDate": "2023-08-22T22:06:17Z",
  "goVersion": "go1.21.0",
  "compiler": "gc",
  "platform": "darwin/amd64"
}
% $pinniped_binary version -o yaml
buildDate: "2023-08-22T22:06:17Z"
compiler: gc
gitCommit:<PHONE_NUMBER>01b7d66d466b4ca4d13a81bc54a7c3
gitTreeState: dirty
gitVersion: v9.8.7
goVersion: go1.21.0
major: "9"
minor: "8"
platform: darwin/amd64


Move docs into the main project and autogen

We'd like our python and JS docs to always be up to date with a released branch.
Right now it requires manual updating the docs and running the update scripts.
This ideally would be automatically done each release (not main)

move docs so that code and docs can be merged together in a PR
maybe we do this via running a simple script for actual deployment <-- add to the release process .md file


Volume for current time frame is always 0

Hi,
First of all, thanks for sharing this repository!
I have been trying to use it for trading a paper alpaca account, but it does not buy anything since it returns 0 volume for the latest tick for all stocks. The volume_checker function inside stock_analysis.py always returns 0, so,  when calling the daytrading_stock_analyzer from runner.py the IF condition is not satisfied as the stock_score is 0.
I have checked the module stock_data_gather.py and noticed that the volume for the latest interval from the historical_stock_data is 0. The other values are okay, however as the latest tick is 0 the volume stored in stock_data is also 0. This value is the one used inside the volume_checker later.
Sorry if I am being confusing, but I would appreciate it if someone could help me with this issue.
Thank you in advance!

Hi,
First of all, thanks for sharing this repository!
I have been trying to use it for trading a paper alpaca account, but it does not buy anything since it returns 0 volume for the latest tick for all stocks. The volume_checker function inside stock_analysis.py always returns 0, so,  when calling the daytrading_stock_analyzer from runner.py the IF condition is not satisfied as the stock_score is 0.
I have checked the module stock_data_gather.py and noticed that the volume for the latest interval from the historical_stock_data is 0. The other values are okay, however as the latest tick is 0 the volume stored in stock_data is also 0. This value is the one used inside the volume_checker later.
Sorry if I am being confusing, but I would appreciate it if someone could help me with this issue.
Thank you in advance!

Sure, will look into this today / tomorrow.

Ok, so took a look at the code. When I run it, the volume is not showing up as 0. There actually is no function that is just telling you the volume, the function inside stock_data_gatherer.py is get_volume_slope which just checks the last n minutes of data and sees whether it's gone up, stayed close to the same, or gone down. Similarly, there is a get_price_slope which can give you info on whether the price has gone up, down, or stayed relatively the same. The idea with this strategy is that if both the volume and the stock price are going up together, that may be an indicator that the stock is one that should be purchased. Similarly, if the stock price is going down and the volume is high, then it is time to sell.

Will close this issue if this is resolved


Batch process?

Would it be possible to include an option to batch-process an entire folder of XCF files?

This is not currently supported by the plug-in out of the box.
You could try the following script:
import os

for root, dirs, files in os.walk(r'path/to/your/directory'):
    for filename in files:
        filepath = os.path.join(root, filename)
        image = pdb.gimp_file_load(filepath, filename)

        # Or simply use r'path/to/output/directory'
        # if you want to put all images in the same directory.
        output_dirpath = os.path.join(
            r'path/to/output/directory', os.path.splitext(filename)[0])

        # Modify the parameters (file extension, etc.) as needed.
        # For more information, type 'plug-in-export-layers' in
        # `Help -> Procedure Browser`.
        pdb.plug_in_export_layers(image, 'png', output_dirpath, None, 0)

        # This will not remove any image from the disk,
        # only the currently loaded image in the memory.
        pdb.gimp_image_delete(image)

Paste the code into Filters -> Python-Fu -> Console and adjust directory paths and other parameters as needed.
For other settings visible in the plug-in dialog (such as Only visible layers or other constraints or procedures), save the settings first in the dialog (Settings -> Save Settings).

Thank you!!
On Thu, Nov 7, 2019 at 11:34 AM khalim19<EMAIL_ADDRESS>wrote:

This is not currently supported by the plug-in out of the box.
You could try the following script:
import os
for root, dirs, files in os.walk(r'path/to/your/directory'):
for filename in files:
filepath = os.path.join(root, filename)
image = pdb.gimp_file_load(filepath, filename)
    # Or simply use r'path/to/output/directory'
    # if you want to put all images in the same directory.
    output_dirpath = os.path.join(
        r'path/to/output/directory', os.path.splitext(filename)[0])

    # Modify the parameters (file extension, etc.) as needed.
    # For more information, type 'plug-in-export-layers' in
    # `Help -> Procedure Browser`.
    pdb.plug_in_export_layers(image, 'png', output_dirpath, None, 0)

    # This will not remove any image from the disk,
    # only the currently loaded image in the memory.
    pdb.gimp_image_delete(image)

Paste the code into Filters -> Python-Fu -> Console and adjust directory
paths and other parameters as needed.
For other settings visible in the plug-in dialog (such as Only visible
layers or other constraints or procedures), save the settings first in
the dialog (Settings -> Save Settings).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/khalim19/gimp-plugin-export-layers/issues/79?email_source=notifications&email_token=AAE66P55BGZUYKGPNR53KKTQSRNU3A5CNFSM4JKKHCPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDNMC5A#issuecomment-551207284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE66P32QOXCQMNNL4FW5JLQSRNU3ANCNFSM4JKKHCPA
.


Support multiple styles in the OperationDefinition rule

Is your feature request related to a problem? Please describe.
My project has operation names that are either in camelCase or PascalCase. I want to enforce this using eslint.
graphql-eslint does not support checking against multiple styles in a one of manner.
Describe the solution you'd like
Add support to check the operation name style against multiple options
so something like
rules:
      '@graphql-eslint/naming-convention':
        - error
        - OperationDefinition:
            style:
             - camelCase
             - PascalCase

Sorry, but I don't want to include this to default rule


Speculative: Wildcard support for resources

Originally posted by @bryanaknight in https://github.com/authzed/spicedb/issues/1#issuecomment-973357174
I ran into a use-case (for GitHub) that is related to this.
Scenario: We have specially privileged users (e.g. staff) that have permissions for lots of different objects in our schema. These users and permissions are not tied to any sort of high-level container like an organization.
I asked about this not wanting to have to embed some sort of a "staff" relation into every single object where these users have permission, and the recommendation was

generally, the recommendation in that case is to have some sort of root type, like system or platform
connect your items to that, and then place the staff user permission on the root object
so say you had resource -> organization
you could add resource -> organization -> platform
it means attaching every org to the platform, but that should be fairly minimal vs attaching to every resource
it also means you can tenant out these kinds of "global" permissions later, if you decide you want a "partially 'global'" staff member

This is working for us but as it states it still means we have a lot of relationships that we need to generate between the organization and any other resource owner(e.g. uesr, business) and the platform. The schema I came up with looks something like:
definition platform {
  relation administrator: user
  permission admin = administrator
}

definition organization {
  relation platform: platform
  permission platform_admin = platform->admin
}

definition repository {
  relation owner: user | organization

  permission delete = owner + owner->platform_admin
}

Not that these platform admins don't have every single permission available on the platform, but they do have a large set of permissions spanning lots of different resource types.
This sparked the idea of utilizing the public type to solve this more efficiently. The current proposal for public is to allow something like resource:someresource#viewer@user:*, which states that any user can view a specific resource. We could theoretically do the inverse of that for this use case resource:*#viewer@user:staffgal, which states that any resource can be viewed (or some other permission) by a specific user.

We have a similar use case where we'd like to assign a relation to all resources of a given type. In our platform we model something similar to AWS Permission Boundaries (permission boundaries specify the policy that governs the maximum level of permissions you can have). In our platform we call these access levels. An access level includes one or more access level permissions.
We have a model like this:
definition workfront/user {
    relation tenant: workfront/tenant

    relation accesslevel: workfront/accesslevel
}

definition workfront/accesslevel {
    relation granted: workfront/user
}

definition workfront/accesslevelpermission {
    relation view_permission: workfront/accesslevel#granted
    relation edit_permission: workfront/accesslevel#granted
    relation manage_permission: workfront/accesslevel#granted

    permission view = view_permission + edit
    permission edit = edit_permission + manage
    permission manage = manage_permission
}

definition workfront/portfolio {
    relation accesslevelpermission: workfront/accesslevelpermission

    relation viewer: workfront/user
    relation editor: workfront/user
    relation manager: workfront/user

    permission view = (viewer + edit) & accesslevelpermission->view
    permission edit = (editor + manage) & accesslevelpermission->edit
    permission manage = manager & accesslevelpermission->manage
}

Every time we write a workfront/portfolio object we have to create the corresponding relationship to the accesslevelpermission. For example,
workfront/accesslevelpermission:portfolio#manage_permission@workfront/accesslevel:planner#granted
workfront/accesslevelpermission:portfolio#edit_permission@workfront/accesslevel:planner#granted

workfront/accesslevel:planner#granted@workfront/user:fred

workfront/portfolio:portfolio1#accesslevelpermission@workfront/accesslevelpermission:portfolio
workfront/portfolio:portfolio2#accesslevelpermission@workfront/accesslevelpermission:portfolio
... etc

It'd be nice if we could just write a single static relationship such as
workfront/portfolio:*#accesslevelpermission@workfront/accesslevelpermission:portfolio

This would eliminate the need to write an additional relationship per object for the association between the object and the access level permissions governing it.

+1 on this from my side as well. We have a use-case where we'd like to effectively do access checks of certain microservices towards one another. For instance, a certain service should have blanket permission on all resources of a certain type when not acting on behalf of a user. We'd basically like to create a new (empty) definition "service", then create a single subject per service, and give each of the services a set of relationships like resource_type_this_service_has_access_to:*#permission_the_service_has@service:some_microservice
Since these kinds of checks are pretty easy to implement in custom logic this is not an urgent requirement, but it would be nice to have a single source of truth for all permissions. Doing it in SpiceDB would currently require materializing the set of relationships from each service to each newly created resource, which is not ideal. Anyway, I thought I'd add my 2 cents here.

+1 as well! We have a lot of resources that do not cleanly fit into a hierarchical structure, so we're being forced to relate each individual resource back to a platform (ie resource:1#platform@my_platform, resource:2#platform@my_platform, ... resource:n#platform@my_platform)  even though it feels redundant. Wildcard object IDs in relationship declarations (or even allowing static relations in the resource definitions) would solve this / be greatly appreciated.

+1 for this feature

@kindy's static relation proposal offers a very interesting (and powerful) alternative to this idea: https://github.com/authzed/spicedb/issues/1266

+1 for this feature
I think this would be a great feature to reduce the friction for people to adopt SpiceDB. Im explore authZ as a service for our internal services and for the initial prototype/iteration, wildcard resource or static relation would be a great place to start with.

+1 for this feature

This would solve some significant issues on my end. +1

Also, I'm not sure that the static relationships is 1:1 with the problem this solves. I'm sure there's overlap, but the semantics differ.


Remove uses of #[allow(dead_code) in favor of names starting with  _

TLDR is that we have some code (such as referenced below) that uses #[allow(dead_code)]  to permit a field that is only present so its Drop (destructor) can run.
          Apparently this can be also written without disabling a lint:

    _reservation: MemoryReservation,

#[allow(dead_code)] has disadvantage that it can be retained in the code even if the field becomes used
_reservation has disadvantage that it doesn't look pretty

Originally posted by @findepi in https://github.com/apache/datafusion/pull/13227#discussion_r1826521890
@drauschenbach  notes: https://github.com/apache/datafusion/pull/13227#discussion_r1826582516

Pretty or not, _reservation is the language-appropriate idiom.

Thus it would be great to update the code to use _reservation in the case above, and potentially look in the codebase for other similar uses of #[allow(dead_code)] and use the _ prefix

take


fix hive create-via annotation

Signed-off-by: liuwei<EMAIL_ADDRESS>

refer to https://github.com/open-cluster-management/backlog/issues/17177

/lgtm


Rework a lot of the cmake configuration to use the cmake library link…

…ing system instead of raw CXXFLAGS

@redboltz Please cancel the dependbot CI jobs

@redboltz Please cancel the dependbot CI jobs

done.

Having problems with this.
Will resubmit later.


⚠ ClamAV has degraded performance

In bd06779, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 74 ms

Resolved: ClamAV performance has improved in 238356c.


Updating supported OS for Ubuntu and Debian

Adding Debian and Ubuntu supported versions to align with the following document: https://puppet.com/docs/pe/2017.3/installing/supported_operating_systems.html.

LGTM once Travis gives the nod


[Feature Request] Add "Read More" button to "Recent"

I understand we can set "showRecent = true " to add Recent Post in homepage. I think it's good to see a button that lead user to view all the post.
Regards.

@miawithcode thanks for the suggestion. The current version already allows the configuration of how many articles users want to show in the recent section. I'll take a look at how this could work for a future version.


Bump version of Cairo/cvec?

I'm building a cross-platform GUI application which will use the gtk-rs bindings for linux. However, bringing in gtk in as a platform specific dependency runs into this bug in cargo:
https://github.com/rust-lang/cargo/issues/3512
It looks like the newest version of the cairo crate no longer has this dylib specification in the Cargo.toml. I realize this is a cargo bug, but since you mentioned you may be doing a new release soon according to #451, could you bump the required version of cvec in cairo, then bump the version of cairo here?

Version already bumped https://github.com/gtk-rs/cairo/commit/4112003b5f08e498c73284d9bd033c69d1edc5f8

Fixed now that #451 is resolved, thanks!


We found potential security vulnerabilities in your dependencies.

Unfortunatly the generator package is affected by the issue related to the "event-stream" incident. Are you already in preparations to fix this issue or shell try to make an pr?

Do you mean the package itself or the repository which is the result of the package output?
If you can quickly prepare a PR would be just awesome!

The result of the package output. PR is coming.

I closed this issue, due to the upcoming release mentioned in https://github.com/Rebilly/swagger-repo/pull/10#issuecomment-445185438.


Windows Defender flagged the exe file as a threat

I'm sure that this is false positive detection mainly because the app is new and still in development
https://imgur.com/a/msuTMki

yup, if you still feel uncomfortable using it you can build the exe


 The error seems to be related to our CI setup. I will check with my team on what should be our next steps here. Maybe we have to tweak the CI, maybe move this project to Podman instead.

Ok, thanks !


Introduce a "no sources are available" curation

The curation should add a flag no_sources_available analog to is_metadata_only with analog handling, e.g.
if true no attempt to download or scan the package's source code.
Motivation:

Resolving via a boolean flag is better than via a resolution, for same reason as for is_metadata_only [1], [2].
curations with dedicated semantics provide a better matching based on identifier instead of regex, and have clear
semantics as opposed to free text resolution messages. So, the curations provide more information which can be
useful for automated consumption from e.g. the policy rules.
Why not merge is_metadata_only and no_sources_available
-> Because it provides more information enabling use cases like: for packages with is_metadata_only=true  it's ok if
the    package does not have license, while for no_sources_available it isn't.

[1] https://github.com/oss-review-toolkit/ort/pull/2939
[2] https://github.com/oss-review-toolkit/ort/issues/2897

no attempt to download or scan the package's source code.

Just to capture some thought's from today's Kotlin Dev meeting: Basically we already have the skip_concluded mechanism for this. However, skip_concluded can only be enabled globally, and there could be cases where a concluded_license should be combined with detected copyrights from existing scan results. This would requite to copy these detected copyrights to authors in package curations currently, which might be undesired. A work-around for this could be to looks for existing copyrights in the scan storage before skip_concluded is interpreted.

Use case:
As a lawyer reviewing scan result in context of license compliance, I want to know the set of packages for which the report blindly trusts the provided license info (e.g. declared license or SBOM), without verification (running a license scanner against the codebase), in order to better understand the risks.
(I guess security would also have a use case for such flag)

I'm having trouble understanding how "blindly trust the provided license info" equals the "no sources are available" semantics because there could be cases where the source code is available, but you still decide to not take scan results into account (or scan at all) just for simplicity of the process.

I'm having trouble understanding how "blindly trust the provided license info" equals the "no sources are available" semantics because there could be cases where the source code is available, but you still decide to not take scan results into account (or scan at all) just for simplicity of the process.

In that use case, scanning the source if available is required, in order to reduce the risk.


Fix test path builder.

Using strings.Trim has unintended consequences, since all characters in nameToTrim are dropped from both ends of the string. This will break tests if the root directory includes any characters in nameToTrim. This patch only replaces nameToTrim at the end of the path.

Hi Joshua,
thanks for all your PR, we need to process them through our internal process and will try to merge them ASAP.


Fix invalid self-closing  tag incompatible with jQuery 3.5

To close a cross-site scripting vulnerability, jQuery 3.5.0 disabled an insecure htmlPrefilter that previously fixed up invalid self-closing tags. Fix our HTML not to rely on that.
https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/
Fixes #558.

@bgrins any chance we can get this merged soon? The jQuery 3.5 patch release is a security patch and it exposed a regression in this plugin.

We've only just updated to jQuery 3.5.1 and I was searching for hours for a solution. Thanks for the fix.

Thanks for the patch, and sorry for the delay. I'll merge it now and tag a release later.

1.8.1 has been tagged and published. I've also updated the docs page at https://bgrins.github.io/spectrum/ to use jQuery 3.5.1.


Allow for version 0 which is a valid version usually from Ledger hard…

…wallet signatures
Source: https://yos.io/2018/11/16/ethereum-signatures/

@se3000 just wanted to get your eyes on this

Hey there, just realized also that seems like Catalina breaks this as mentioned in https://github.com/se3000/ruby-eth/issues/47 so I can't actually run it on my computer. Can you approve this and get this new version published?

Mind adding a test with an example signature?

@se3000 added the spec!


build optimizations

This CL is a mixture of changes to optimize the build.
A sample build can be seen here: https://github.com/google/android-fhir/actions/runs/2633666016
Where we compile & test the project ~3 minutes (when no code changed). Emulator tests are still slow :(
List of changes:

move the CI setup into 2 actions, each use a common action to setup the machine

build and test on host machine (on linux)
run emulator tests (mac)

enabled gradle caching (this is where the main win happens)
set gradle.properties similar to andoridx, removed ci properties
removed buildToolsVersion, which is deprecated
run device tests in 1 gradle execution, to avoid killing and re-creating the emulator between each run
added --scan to all gradle invocations. Scan results are added to the build summary
moved code generation into buildSrc and made it a cacheable task. This is the other major win wrt caching because changing sources while building will mess up caching.  (we should never write to input directories)
another nice win related to codegen is that, we no longer commit generated files
code generator was hitting "method too big"error, so changed it to divide into sub-methods
limited memory for test runs. they get forked from current process so easily starve the device.

Honestly this is so amazing we love you Yigit!


_fetchTables recursive must match signature

This recursive call to _fetchTables recursively adds to the list of tables, and I think the second parameter should be the list.

Good catch @rambler.  Thank you!

Published in v0.1.7


add dark mode theme

add dark theme for web users.

Dark Theme? This repo contains play specific examples, I think your issue is unrelated.


Add Seat to commercial products

Here is a screenshot with devtools activated https://monosnap.com/file/2PrNXOmxJ8uRbBB4mvlIopm7VMFnZ2

Thanks for your quick reply @kazupon !
What do you mean by explanation page?
To give more details: the app is built with Vue.js on the frontend and RoR on the backend. Although the homepage and account management is rendered server-side via RoR, the actual team collaboration workspaces (show on the screenshot here: https://monosnap.com/file/2PrNXOmxJ8uRbBB4mvlIopm7VMFnZ2) are is an SPA entirely built using Vue.js. Please let me know if that answers your question.

Oh, sorry, my bad.  🙇
It' a okay.


PVWatts5_1ts shading

This adds a shading_percent parameter to the PVWatts5_1ts model.

@dguittet

Uh oh. It looks like Travis didn't like it. Any idea why?


Auto suggest names not visible in Black,Midnight,Mosaic themes

Operating system: Linux (Fedora 24)
Messenger for Desktop version: v2.0.9-stable

This is more of a UI glitch than a real bug, but the colour of the auto-suggest box for when you want to mention someone in a group chat (type @ then the persons name) is conflicting with the text colour, resulting in you not being able to see the persons name.
This only occurs with the Midnight and Mosaic themes. The Black theme also has a similar glitch.
The Dark theme works perfect, so maybe you can change the colourscheme for the boxes in Black,Midnight,Mosaic to be the same as the Dark theme.

Also did a report on this in #1274


Shows the root folder after uploading a new image

When you try to upload an image to the selected folder, the image is uploaded to the specified folder, but the current view changes to the root folder. The breadcrumbs still display the selected one, not the root one.
Steps to reproduce the behavior:

Click "Insert image from media library".
Switch current folder to any inner folder.
Click "Add more assets" and select image files.
After uploading files your current location switched to root folder.

Expected behavior
It was expected that my current location would not change and I would immediately see the downloaded files in the current folder.
Screenshots

plugin version 1.1.3
strapi version 4.14.3
node version 16.15

I assume that the problem is due to incorrect substitution of the folder id in the path.
Response after upload new assets:

Trying open folder with incorrect params:

The parameter value should be "&filters[$and][0][folderPath][$eq]=/4" instead of &filters[$and][0][folderPath][$eq]=/&folder=4

I found same issues with Strapi Media Dialog:
https://github.com/strapi/strapi/issues/18555
https://github.com/strapi/strapi/issues/18540
It looks like a problem in the core of strapi


"noAudit()"-flag on the initiation of Mats flows.

When considering auditing ("event sourcing"-style) of all messages, one quickly realizes that there are very many messages that aren't that interesting to log. These are pure getters employed to show information to users, and in particular "are you up?" health checks.
It would be good if the initiator could mark a message as such: "You will gain no historic insight in logging the following message flow!". This flag should NOT be set for ANY messages that (can potentially) change state in any part of the total system (i.e. "permanent state", e.g. a row in a database). More subtle, the flag should also not be set for "getters" that are performed to decide upon a state - e.g. for validation of new orders: The getter that checks credit should be audited. If such a getter is a part of a Mats flow, this should not be a problem, as the initiator of the "add order" Mats flow would obviously not set noAudit(). However, if it is coded as multiple "stop and go" flows, i.e. add the order to some incoming order table. Then a next, separate Mats flow is validation: That getter should be audited.

Note: It might be interesting to log that such messages actually happened, but not the content of them. This is to be able to tally them, i.e. "WebService.healtCheck is invoking AccountService.webStatus 52389052 times per day" - both to see that it is probably a bit excessive, and to see that there is traffic there at all (since AccountService.webStatus seems to be a pretty specific endpoint). However, there is probably not much use in storing the contents of such calls - and maybe not retain the calls for more than a few months.


stdin.lineMode = false throws on Windows

When setting stdin.lineMode to false on Windows, I am getting an exception. Example main.dart:
import 'dart:io';

main() {
  stdin.lineMode = false;
}

If I run this on windows with dart.exe main.dart, I am getting the following error:
Unhandled exception:
StdinException: Error setting terminal line mode, OS Error: The parameter is incorrect.
, errno = 87
#0      Stdin.lineMode= (dart:io-patch/stdio_patch.dart:82)
#1      main (file:///C:/Users/goderbauer/Desktop/main.dart:4:8)
#2      _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:261)
#3      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:148)

From Microsoft's documentation (https://msdn.microsoft.com/en-us/library/ms686033) it looks like enabling and disabling lineMode is supported on the platform (see ENABLE_LINE_INPUT value). Therefore, the exception is unexpected.
I am encountering the error while making Flutter work on Windows (https://github.com/flutter/flutter/issues/138).

On Windows, echoMode can't be used without lineMode enabled. One fix would be to do:
import 'dart:io';

main() {
  stdin.echoMode = false;
  stdin.lineMode = false;
}

When enabling echoMode, you'd need:
stdin.lineMode = true;
stdin.echoMode = true;

Let me know if this works for you!

Thanks for looking into it. That should work for us. Might be worth documenting these platform-specific differences in the dart docs?

Getting this error in Windows 10 on v1.23.0!!!! Not sure how to fix it.

This should not be closed as this issue exists in 2020.

@leonardoInf see the explanation in this comment https://github.com/dart-lang/sdk/issues/28599#issuecomment-277370165. You need to disable echoMode first. This is documented in the docs (see https://api.dart.dev/dev/2.9.0-1.0.dev/dart-io/Stdin/lineMode.html)

On Windows this mode can only be disabled if echoMode is disabled as well.


Error: fatal: bad revision

After startup of Brackets I've the following error. Note that I simply checkout my branch.
ErrorNotification.js:125 [brackets-git] call: git rev-list --left-right --count bracketron/fix-folders-tree...@{0} --
Error: fatal: bad revision 'bracketron/fix-folders-tree...@{0}'
    at Object.exports.toError (file:///C:/Users/***/AppData/Roaming/Brackets/extensions/user/zaggino.brackets-git/src/ErrorHandler.js:157:19)
    at NodeConnection.<anonymous> (file:///C:/Users/<username>/AppData/Roaming/Brackets/extensions/user/zaggino.brackets-git/src/Cli.js:185:44)
    at j (file:///C:/Program%20Files%20(x86)/Brackets/dev/src/thirdparty/jquery-2.1.3.min.js:2:26911)
    at Object.k.fireWith (file:///C:/Program%20Files%20(x86)/Brackets/dev/src/thirdparty/jquery-2.1.3.min.js:2:27724)
    at NodeConnection._receive (file:///C:/Program%20Files%20(x86)/Brackets/dev/src/utils/NodeConnection.js:498:34)

I see bracketron in the error. I don't know if it is beacuse I've three remotes.
$ git remote -v
bracketron      https://github.com/zaggino/brackets-electron (fetch)
bracketron      https://github.com/zaggino/brackets-electron (push)
origin  https://github.com/ficristo/brackets.git (fetch)
origin  https://github.com/ficristo/brackets.git (push)
upstream        https://github.com/adobe/brackets.git (fetch)
upstream        https://github.com/adobe/brackets.git (push)

Possibly related to https://github.com/zaggino/brackets-git/issues/1272 and https://github.com/zaggino/brackets-git/issues/1299.

Changing the remote through the GUI fixed it.
But I have a similar problem when I test some PR:
call: git rev-list --left-right --count origin/pull-12041...@{0} --
Error: fatal: bad revision 'origin/pull-12041...@{0}'

[brackets-git] call: git rev-list --left-right --count origin/issue_#184...@{0} --
Error: fatal: bad revision 'origin/issue_#184...@{0}'
    at Object.exports.toError (file://~/.config/Brackets/extensions/user/zaggino.brackets-git/src/ErrorHandler.js:158:19)
    at NodeConnection.<anonymous> (file://~/.config/Brackets/extensions/user/zaggino.brackets-git/src/Cli.js:185:44)
    at j (file:///opt/brackets/www/thirdparty/thirdparty.min.js:19:26911)
    at Object.k.fireWith (file:///opt/brackets/www/thirdparty/thirdparty.min.js:19:27724)
    at NodeConnection._receive (/utils/NodeConnection.js:498:34) Utils.js:350


the examples dont work on either chrome or firefox

hi, thanks for writing this reactjs library. im quite excited to use it but the examples on https://www.react-magic-motion.com/applications do not work for me even when i made sure the the animations button on the screen is turned on
ive seen how the todo list animation should work in the demo video so i can say for sure it is not working on my side on different browsers
ive also tried it in incognito so that extensions are disabled and it doesnt work too
there are no msgs in the console
what could be the problem here...?

The issue is that you probably have prefers-reduced-motion on in your operating system settings. This settings turns off the animations.
You can look at this stack overflow post to see how to turn off prefers-reduced-motion
https://stackoverflow.com/a/59709067

The issue is that you probably have prefers-reduced-motion on in your operating system settings. This settings turns off the animations.
You can look at this stack overflow post to see how to turn off prefers-reduced-motion https://stackoverflow.com/a/59709067

wow thanks for narrowing down the problem i had so quickly, all working now including in my own project!


Unable to create project - project type (.mproj) is not supported...

I'm unable to even create a project (either a data connector or a PQ file).
I first had these problems on my local machine, whereupon I tried to isolate the issue by setting up a VM - same symptoms:
I did a clean install of Visual Studio 2017 (15.2.26430.13) onto an Azure VM (SQL Server 2016), installing only the data tools (15.1.61702.140) and nothing else. Then I installed the Power Query SDK (<IP_ADDRESS>).
I then tried to create a new data connector project. When I try to create the project in Visual Studio (File / New / Project / Power Query / Data Connector Project / OK) I get the following error message: "'C:\Users...\project.mproj' cannot be opened because its project type (.mproj) is not supported by this version of the application.  To open it, please use a version that supports this type of project."
A folder is created for the solution, but the .sln file is empty.
Are there other components that I need to install in Visual Studio?
Thanks,

Jen

hey! Try downloading this version instead:
https://www.dropbox.com/s/rxq60jdkgwkld82/PowerQuerySdk.vsix?dl=0
the new version that is available on the store is having issues, but I downloaded this one prior to it. Be sure to delete the installed extension, restart your VM and then installing this new one.

That worked, thanks Miguel!


[Coverity CID :195847]Memory - corruptions in /tests/net/traffic_class/src/main.c

Static code scan issues seen in File: /tests/net/traffic_class/src/main.c
Category: Memory - corruptions
Function: traffic_class_send_data_mix
Component: Tests
CID: 195847
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

Duplicate of #14404


Complexity of Coinbase Pro API Passphrase Arbitarily Limited by Input Validation

Coinbase allows manual input of the API passphrase, complex strings including uppercase, lowercase, numbers, and special characters are permitted. For example n3by9t338097^%YGAKUDLID! is permitted.
This regex, found on models/CoinbasePro.py line 67, is used to validate the API passphrase input:
^[a-z0-9]{10,11}$
This arbitarily limits the API passphrase to 11 characters with only lowercase and numbers possible. I haven't made a pull request for an alternative regex as I'm not sure what the actual limits for the field on Coinbase are or whether the currently configured limit is important when the value is used elsewhere in the script and am not sure what would be a still safe but looser regex.
I realise this is a very trivial issue in an awesome project but thought I should point it out in case it helps anyone who might be wondering why their custom passphrase isn't accepted.

I didn't realise Coinbase Pro allowed you to specify your own keys. That makes things a little challenging. I will include the special chars you mention above as a start. I will also allow a wider range in key size. We can start with that and see how it goes.

A PR was put through to allow this. Can you confirm it's working now?

The changes from the PR don't seem to be merged, behaviour hasn't changed.

@eatsleeproute, this should be fixed now. Can you please confirm?

I've implemented this. I allowed keyboard characters greater with a length between 8 and 32. That should give enough flexibility.
p = re.compile(r"^[A-z0-9#$%=@!{},`~&*()<>?.:;_|^/+[]]{8,32}$")


Add NOME-Seq to Chromatin Accessibility

Add NOME-Seq to Chromatin Accessibility.

spec moved to ecosystem.


Deletion on Flickr Side

Hello,
Sorry if you answered this before but I couldn't find it in the readme.
If I delete a file from Flickr, will it:

Stay on local but not be uploaded again (unless I do some specific things such as reset my database
Be uploaded again then next time the script launches
Be deleted from the matching local folder

I think it is option 1 but before trying I wanted to check with you.
Specifically, I have a video which is being processed for over a month now and I read on a forum that if this message lasts longer than 10min, one should simply delete and upload again.
Thx
PS: you wrote flicr.com in the readme

Sounds good to me for now, I just wanted to make sure that it wouldn't be 3 :)


Link VerticalAlignment property to XlVAlign enum

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

VBA/Excel-VBA/articles/range-verticalalignment-property-excel.md
:white_check_mark:Succeeded

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

VBA/Excel-VBA/articles/range-verticalalignment-property-excel.md
:white_check_mark:Succeeded

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

All content in this repository has been migrated to a new repository (https://github.com/MicrosoftDocs/VBA-Docs). The changes in this PR have been applied in the new repository, so this PR is being closed. The changes will be published to the live docs soon. Thank you for your contribution!


cmd/go: module fetch errors are unclear

What version of Go are you using (go version)?
go version devel +5f5402b Tue Jul 24 23:54:08 2018 +0000 linux/amd64
What did you do?
go mod init -module example.com/mod
go get github.com/google/go-cloud

This produced the following output:
go: finding github.com/google/go-cloud v0.1.0
go: finding github.com/tidwall/gjson v1.1.2
go: finding github.com/aws/aws-xray-sdk-go v1.0.0-rc.5
go: finding github.com/fsnotify/fsnotify v1.4.7
go: finding github.com/gorilla/context v1.1.1
go: finding github.com/dnaeon/go-vcr v0.0.0-20180504081357-f8a7e8b9c630
go: finding github.com/aws/aws-sdk-go v1.13.20
go: finding go.opencensus.io v0.12.0
go: finding google.golang.org/grpc v1.13.0
go: finding contrib.go.opencensus.io/exporter/stackdriver v0.0.0-20180421005815-665cf5131b71
go: finding cloud.google.com/go v0.25.0
go: finding github.com/tidwall/sjson v1.0.0
go: finding github.com/smartystreets/assertions v0.0.0-20180301161246-7678a5452ebe
go: finding github.com/googleapis/gax-go v1.0.0
go: finding golang.org/x/sys v0.0.0-20180329131831-378d26f46672
go: finding github.com/gopherjs/gopherjs v0.0.0-20180424202546-8dffc02ea1cb
go: finding golang.org/x/sync v0.0.0-20180314180146-1d60e4601c6f
go: finding golang.org/x/text v0.3.0
go: finding golang.org/x/net v0.0.0-20180702212446-ed29d75add3d
go: finding gopkg.in/ini.v1 v1.37.0
go: finding github.com/go-ini/ini v1.37.0
go: finding github.com/golang/protobuf v1.1.0
go: finding github.com/jmespath/go-jmespath v0.0.0-20180206201540-c2b33e8439af
go: finding github.com/census-ecosystem/opencensus-go-exporter-aws v0.0.0-20180411051634-41633bc1ff6b
go: finding golang.org/x/tools v0.0.0-20180314180217-d853e8088c62
go: finding github.com/go-sql-driver/mysql v0.0.0-20180308100310-1a676ac6e4dc
go: finding github.com/golang/glog v0.0.0-20160126235308-23def4e6c14b
go<EMAIL_ADDRESS>git fetch -f --depth=1 origin c2b33e8439af944379acbdd9c3a5fe0bc44bd8a5:refs/dummy in /home/rog/src/go/src/mod/cache/vcs/7b1106ecb177564b0bc9784f963c6c785e31d09dcd9f08114684d32af620443f: exit status 1
go: finding golang.org/x/oauth2 v0.0.0-20180603041954-1e0a3fa8ba9a
go<EMAIL_ADDRESS>git fetch -f --depth=1 origin 41633bc1ff6bd23f2beb03aafb533465f3e774d8:refs/dummy in /home/rog/src/go/src/mod/cache/vcs/28c9bbc7175856813846e87fcbc6da1a390ca3679ea2b8f3e8aa0698f2334be7: exit status 1
go: finding github.com/jtolds/gls v0.0.0-20170503224851-77f18212c9c7
go: finding gopkg.in/yaml.v2 v2.2.1
go<EMAIL_ADDRESS>git fetch -f --depth=1 origin 23def4e6c14b4da8ac2ed8007337bc5eb5007998:refs/dummy in /home/rog/src/go/src/mod/cache/vcs/0dac7c3b21e56acaa4cfab3e2c4d83e362d33743d1e198c0d546115da37bae02: exit status 1
go: finding github.com/smartystreets/gunit v0.0.0-20180314194857-6f0d6275bdcd
go: finding google.golang.org/genproto v0.0.0-20180627194029-ff3583edef7d
go: finding github.com/stretchr/testify v1.2.1
go: finding google.golang.org/api v0.0.0-20180606215403-8e9de5a6de6d
go<EMAIL_ADDRESS>git fetch -f --depth=1 origin 6f0d6275bdcdd4411ad1c9b3b69eda55eea5b2db:refs/dummy in /home/rog/src/go/src/mod/cache/vcs/8b17522217382c37f84409229f7711408129a6c273254893129c5df1940e85cc: exit status 1
go: finding github.com/gorilla/mux v1.6.1
go: finding github.com/tidwall/match v0.0.0-20171002075945-1731857f09b1
go<EMAIL_ADDRESS>git fetch -f --depth=1 https://github.com/tidwall/match 1731857f09b1f38450e2c12409748407822dc6be:refs/dummy in /home/rog/src/go/src/mod/cache/vcs/94ba56ba5b973670f7952b0a5b76feea7af42eb6e1f973fdb61999862b84c7a7: exit status 1
go: finding google.golang.org/appengine v1.1.0
go: finding github.com/smartystreets/goconvey v0.0.0-20180222194500-ef6db91d284a
go: finding github.com/GoogleCloudPlatform/cloudsql-proxy v0.0.0-20180321230639-1e456b1c68cb
go<EMAIL_ADDRESS>git fetch -f --depth=1 origin ef6db91d284a0e7badaa1f0c404c30aa7dee3aed:refs/dummy in /home/rog/src/go/src/mod/cache/vcs/1693d9c59c0c1838de53cecb8601eec3084f084265b72c82e78de941f1c8f58c: exit status 1

go: error loading module requirements

It's clear that some of the git fetch commands failed, but because all the actual error output is discarded, it's not possible to see why. "exit status 1" doesn't convey any significantly useful info, so it's hard to know what went wrong and hence how the problem might be resolved.

If you're on an older versison of Git, this might be https://github.com/golang/go/issues/26501. But I agree that the errors should be clearer.

#26501 is now closed, but adding some suggestions from that issue that could help future troubleshooting:
Consider extending what gets emitted by -v (https://github.com/golang/go/issues/26501#issuecomment-406655517 by @rudis)

I stumbled over the same issue and I found the fact that go doesn't report anything about a failing command troublesome. I needed to use strace to figure out what's going on because even with -v nothing was printed about the failing command.
If possible please also extend -v's output to include for example failing commands to help debugging such issues.

And/or address TODO from modload (https://github.com/golang/go/issues/26501#issuecomment-407370781 from @rogpeppe):

I encountered this issue today (I'm using a stock version of Ubuntu 16.04). It's made harder to diagnose by the fact that this TODO from src/cmd/go/internal/modload.go remains unaddressed:
// TODO(rsc): It would be nice to return a specific error encountered
// during the loop above if possible, but it's not clear how to pick
// out the right one.
This means that we don't get to see the actual error encountered (unknown revision refs/tags/v1.0.1) in my case. Even that error isn't ideal when the actual error printed by git is fatal: unrecognised argument: --no-show-signature. Perhaps that output could be shown when using the -v flag?
My git version is 2.7.4.

I just tried one of those git commands and as it happens it does return exit code 1 without printing any error, so perhaps the problem is with git itself. I am using git 2.7.4.

I could move off git 2.7.4 but as it's the default version you get when using Ubuntu 16.04 I think it's important that Go works correctly with that version.

BTW I just tried with a newer version of git (2.18.0) and everything works OK.

I'm not sure what more to do here. I would like to turn off the finding prints by default, although I worry that people will think the go command is just stuck if it's not printing those. But this is very precise:
go<EMAIL_ADDRESS>git fetch -f --depth=1 origin c2b33e8439af944379acbdd9c3a5fe0bc44bd8a5:refs/dummy in /home/rog/src/go/src/mod/cache/vcs/7b1106ecb177564b0bc9784f963c6c785e31d09dcd9f08114684d32af620443f: exit status 1

It contains enough information to repeat the command, and as you found, something is wrong with that git command. I suppose we could make it say "cd dir && git fetch" instead of "git fetch ... in dir". What's unclear is git here, I think.
Does anyone have any idea what is wrong with git 2.7.4? Does it not support --depth=1?

I'm not sure what more to do here.
I assume stdout/err would have more info.

This is not conclusive, but --depth=<depth> at least shows up in git's Documentation/fetch-options.txt for 2.7.4:
https://github.com/git/git/blob/v2.7.4/Documentation/fetch-options.txt#L10
--depth=<depth>::
	Limit fetching to the specified number of commits from the tip of
	each remote branch history. If fetching to a 'shallow' repository
	created by `git clone` with `--depth=<depth>` option (see
	linkgit:git-clone[1]), deepen or shorten the history to the specified
	number of commits. Tags for the deepened commits are not fetched.

for what its worth 2.7.4 since I run the same ubuntu and go head works fine for me.
➜  httpstat git:(master) ✗ go mod -init -module github.com/davecheney/httpstat
go: creating new go.mod: module github.com/davecheney/httpstat
go: copying requirements from Gopkg.lock
➜  httpstat git:(master) ✗ go build
go: finding github.com/fatih/color v1.5.0
go: finding github.com/mattn/go-isatty v0.0.3
go: finding github.com/mattn/go-colorable v0.0.9
go: finding golang.org/x/text v0.0.0-20170915090833-1cbadb444a80
go: finding golang.org/x/sys v0.0.0-20170922123423-429f518978ab
go: finding golang.org/x/net v0.0.0-20170922011244-0744d001aa84
go: downloading github.com/fatih/color v1.5.0
go: downloading golang.org/x/net v0.0.0-20170922011244-0744d001aa84
go: downloading github.com/mattn/go-colorable v0.0.9
go: downloading github.com/mattn/go-isatty v0.0.3
go: downloading golang.org/x/text v0.0.0-20170915090833-1cbadb444a80
➜  httpstat git:(master) ✗ git --version
git version 2.7.4
➜  httpstat git:(master) ✗ go version
go version devel +e5b1340 Wed Jul 25 23:53:54 2018 +0000 linux/amd64

@rogpeppe can you try running one of the git commands with some of these verbose env vars set
https://stackoverflow.com/questions/6178401/how-can-i-debug-git-git-shell-related-problems

@gopherbot, please add label help wanted

https://github.com/golang/go/issues/25982#issuecomment-411068491 is related here. Whilst as @rsc notes in https://github.com/golang/go/issues/26594#issuecomment-407869083 we shouldn't/don't have to log the finding statements, we can log the output in case of error.

This issue #26594 is slightly complicated by the fact that apparently here outputting errors from git would not have helped here (because here git was silent), but it seems outputting errors from git would have helped other issues, e.g., see https://github.com/golang/go/issues/26594#issuecomment-407797257

@thepudds is there any thoughts on when running go in verbose mode running git fetch with one of those verbose flags mentioned in my link? Just thinking about how we can give people the tools they need to debug these issues without filing an issue every time.
https://stackoverflow.com/questions/6178401/how-can-i-debug-git-git-shell-related-problems

@mvdan has the answer 🎖
This particular case appears to be affected by the use of an ssh-based git remote.
Using git 2.11.0 (because this particular command is not a problem with more recent git versions) and assuming an appropriate ssh setup:
cd $(mktemp -d)
git init
git remote add origin git@github.com:neelance/astrewrite
git fetch -f --depth=1 origin 99348263ae862cc230986ce88deaddbf7edcc034:refs/dummy

gives exit code 1 and no output.
Using an https-based remote:
cd $(mktemp -d)
git init
git remote add origin https://github.com/neelance/astrewrite
git fetch -f --depth=1 origin 99348263ae862cc230986ce88deaddbf7edcc034:refs/dummy

gives exit code 128 and the following output (which is what we want/need):
error: no such remote ref 99348263ae862cc230986ce88deaddbf7edcc034

I haven't looked into possible solutions, so this is just to note findings so far.

Sorry, another message in this thread
I'm seeing the aforementioned behaviour on CircleCI v2 (which has git 2.11.0), so not an uncommon setup people will be using. CircleCI globally sets url.ssh://git@github.com.insteadof=https://github.com, hence how this comes about.

We fixed this particular error, which was really git's fault.


kimera-vio-ros gtsam build fails on Ubuntu 20.04

I've added support for Ubuntu 20.04 to Kimera and wanted to submit a PR, but hit a snag regarding GTSAM.
Kimera-vio-ros currently does not build for two reasons:

The image_undistort node does not compile with the c++-11 flag. I have filed a PR against the repo: https://github.com/ethz-asl/image_undistort/pull/64 so hopefully this will be fixed at some point.

The "master" branch of gtsam does not compile because it has a broken CMakeLists.txt file in the "wrap" subdirectory (some matlab wrappers):

CMake Error at /home/pfrommer/Documents/kimera/src/gtsam/wrap/CMakeLists.txt:32 (target_link_libraries):
  The "debug" argument must be followed by a library.

This has been fixed with the latest gtsam release 4.0.3. Alas, gtsam v4.0.3 does not build on ubuntu 14.04 (trusty), because for that very same fix it requires cmake > 3.0.0, whereas trusty has only 2.8.12. In a pinch people can install cmake 3 on Ubuntu 14.04, so there is a workaround: https://askubuntu.com/questions/610291/how-to-install-cmake-3-2-on-ubuntu
Question: how important is it for you to keep support for Ubuntu 14.04?

Hi @berndpfrommer,
We only test for >=16.04, so 14.04 is not officially supported.
Thanks for the detailed issue!
We could add a build to our CI server with 20.04 and git checkout 4.0.3 in gtsam.
We could then just update the install readme.
Note though that I have no CI with the ROS wrapper:

There is an open PR for it here: https://github.com/MIT-SPARK/Kimera-VIO-ROS/pull/32

Feel free to open a PR.

Hi @berndpfrommer ,
i tired to install kimera-vio ros in Ubuntu 20. Your suggested modifications have been addressed now, but build fails. Have you managed to build this project in ubuntu 20?


how to extract unity3d 5.x ??

hi
is it possible extract only the source code ??

Which source code do you mention?
To get source code of a project you can use ILDasm or similar tool on Assembly-CSharp.dll

im pretty sure he means source code from unity 5

You can just use NET Reflector and extract the source code that way.

I made PR which I want to test, please look at https://github.com/ata4/disunity/pull/150 , you can test it from my fork.

iOS builds of Unity 5 games removed the DLL files since they are useless. iOS cannot interpret DLL so instead Unity compiles the source code into native code. Decompiling and getting the source code has nothing to do with this project. This project only concerns assets.


CC2652R wont join after a reset

I moved my CC2652R stick flashed with the 1.0.0 router firmware, and it refused to reconnect to zigbee2mqtt, nothin in the logs showing it even trying.
I have tried:
Removing it an re-adding it (Never shows in logs)
A touch link reset which fails:
Jan 28 16:18:40 raspberrypi npm[29463]: Zigbee2MQTT:info  2021-01-28 16:18:40: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"reset_started","meta":{"status":"started"},"type":"touchlink"}'
Jan 28 16:18:51 raspberrypi npm[29463]: Zigbee2MQTT:warn  2021-01-28 16:18:51: Failed to factory reset device through Touchlink
Jan 28 16:18:51 raspberrypi npm[29463]: Zigbee2MQTT:info  2021-01-28 16:18:51: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"reset_failed","meta":{"status":"failed"},"type":"touchlink"}'

and re-flashing and resetting, which again fails.
I have also left it unplugged over night to see if it would force the network to 'forget' the device and allow it to be reset.
I don't have a spare CC2531 (yet) to flash with the sniffer firmware, is there anything else I can try?
Willing to re-do from scratch and re-pair everything if that is necessary
thanks :)
edit, running the dev branch of zigbee2mqtt

If nothing shows in the log the only way to debug is to sniff :(

If nothing shows in the log the only way to debug is to sniff :(

Ok, ill get another cc2531 ordered, then Ill report back
any tips on how to sniff/what to look for?

Ok, ill get another cc2531 ordered, then Ill report back
any tips on how to sniff/what to look for?

Just send me the whole sniff when pressing the button on the CC2652R: https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html

Just send me the whole sniff when pressing the button on the CC2652R: https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html

Should be here monday, Ill take a look then :) thanks!

Should be here monday, Ill take a look then :) thanks!

My LAUNCHXL-CC26xR1 does this too. Flashed the router firmware 2-3 times. Also erased entire flash via UniFlash.
Here's my log from sniffing. In the log I pressed the button a few times. Also re-plugged it a lot.
log.zip

@copystring try pairing the device close to the coordinator. In your sniff it's trying to join through a Philips device 0x0017880108556c81 but it's not sending the network key.

Nice. Works now.

Mine is now also working thanks, I was unable to get the sniffer to work under windows, but moved it closer to the coordinator and it managed to eventually join :)


no such element: Unable to locate element: {"method":"css selector","selector":"[id="ius-userid"]"}

As of yesterday ...
What version of MintAPI are you using?
1.63
What command[s] did you run / steps to reproduce?
mint = mintapi.Mint(userid, pw,
	headless=True,
	wait_for_sync=True,
	mfa_method='soft-token',
	mfa_token=token,
)

Stacktrace/error received:
Message: no such element: Unable to locate element: {"method":"css selector","selector":"[id="ius-userid"]"}
  (Session info: headless chrome=99.0.4844.51)
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/mintapi/api.py", line 235, in login_and_get_token
    self.status_message, self.token = sign_in(
  File "/usr/local/lib/python3.9/site-packages/mintapi/signIn.py", line 313, in sign_in
    handle_same_page_username_password(driver, email, password)
  File "/usr/local/lib/python3.9/site-packages/mintapi/signIn.py", line 360, in handle_same_page_username_password
    email_input = driver.find_element_by_id("ius-userid")
  File "/usr/local/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 360, in find_element_by_id
    return self.find_element(by=By.ID, value=id_)
  File "/usr/local/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 976, in find_element
    return self.execute(Command.FIND_ELEMENT, {
  File "/usr/local/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 321, in execute
    self.error_handler.check_response(response)
  File "/usr/local/lib/python3.9/site-packages/selenium/webdriver/remote/errorhandler.py", line 242, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"css selector","selector":"[id="ius-userid"]"}
  (Session info: headless chrome=99.0.4844.51)

Hi @dzg ! It looks like this is a duplicate issue. Please see #405 for updates to this issue. To

@burkematthew - I see that this issue was marked as resolved. However, it appears that I'm still having trouble with it. Do I need to uninstall and reinstall mintapi through the terminal for the changes to take effect?
Message: no such element: Unable to locate element: {"method":"css selector","selector":"[id="ius-userid"]"}
  (Session info: chrome=99.0.4844.51)
Traceback (most recent call last):
  File "/Users/deepak.krishnan/Library/Python/3.8/lib/python/site-packages/mintapi/api.py", line 235, in login_and_get_token
    self.status_message, self.token = sign_in(
  File "/Users/deepak.krishnan/Library/Python/3.8/lib/python/site-packages/mintapi/signIn.py", line 313, in sign_in
    handle_same_page_username_password(driver, email, password)
  File "/Users/deepak.krishnan/Library/Python/3.8/lib/python/site-packages/mintapi/signIn.py", line 360, in handle_same_page_username_password
    email_input = driver.find_element_by_id("ius-userid")
  File "/Users/deepak.krishnan/Library/Python/3.8/lib/python/site-packages/selenium/webdriver/remote/webdriver.py", line 360, in find_element_by_id
    return self.find_element(by=By.ID, value=id_)
  File "/Users/deepak.krishnan/Library/Python/3.8/lib/python/site-packages/selenium/webdriver/remote/webdriver.py", line 976, in find_element
    return self.execute(Command.FIND_ELEMENT, {
  File "/Users/deepak.krishnan/Library/Python/3.8/lib/python/site-packages/selenium/webdriver/remote/webdriver.py", line 321, in execute
    self.error_handler.check_response(response)
  File "/Users/deepak.krishnan/Library/Python/3.8/lib/python/site-packages/selenium/webdriver/remote/errorhandler.py", line 242, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"css selector","selector":"[id="ius-userid"]"}
  (Session info: chrome=99.0.4844.51)

Hi @Deepak-01 ! You need to upgrade to mintapi 1.64 however you installed it. Probably pip install --upgrade mintapi

That fixed it. Thanks a lot!


Specify CVXPY version to use '*' for matrix multiplication

pip install pulls the latest version of CVXPY, version 1.1.15. Using the the BRCG algorithm with this version results in the following run time warning several times that cannot be filtered.
UserWarning: This use of ``*`` has resulted in matrix multiplication.
Using ``*`` for matrix multiplication has been deprecated since CVXPY 1.1.
    Use ``*`` for matrix-scalar and vector-scalar multiplication.
    Use ``@`` for matrix-matrix and matrix-vector multiplication.
    Use ``multiply`` for elementwise multiplication.

Reverting to an older version, by specifying a version in setup.py allows for this deprecated use. Assumes CVXPY isn't used by other algorithms in the toolkit.

Thanks @rahulnair23


LineRange on NotePosition should include omitempty

When trying to create a Merge Request Discussion and Note, the LineRange should be allowed to be empty for notes that occur on a single line not a range.

Feel free to create a PR to fix it...


Issue #218 - Update to Spring-Data 2.1.2.RELEASE and Spring Framework 5.1.2.RELEAS

This PR merges all code & all changes from all parties to give credit to everyone!

Codecov Report

Merging #223 into master will increase coverage by 0.19%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #223      +/-   ##
===========================================
+ Coverage     65.21%   65.4%   +0.19%
- Complexity      598     600       +2
===========================================
  Files            77      77
  Lines          2038    2038
  Branches        374     374
===========================================
+ Hits           1329    1333       +4
+ Misses          554     550       -4
  Partials        155     155

Impacted Files
Coverage Δ
Complexity Δ

.../repository/support/DynamoDBRepositoryFactory.java
85.1% <ø> (ø)
20 <0> (ø)
:arrow_down:

.../data/dynamodb/mapping/DynamoDBMappingContext.java
75% <0%> (+25%)
8% <0%> (+2%)
: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 9356e42...82285cf. Read the comment docs.

@boostchicken I'm sorry I'm not following.
Which lines are you referring to that should be removed in PartTreeDynamoDBQueryUnitTest.java?
I'm afraid now that the merge missed something?


[webpack] switched buildprocess to webpack

Pull Request Test Coverage Report for Build 329

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 325:
0.0%

Covered Lines:
372

Relevant Lines:
372

💛  - Coveralls


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
Checklist

[x] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

XTroptions.Gold

Please submit the correct information, invalid information will cause the issue to close


Update ADOPTERS.md

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

Codecov Report

Merging #1009 (d6e4765) into main (05ce4ad) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1009      +/-   ##
============================================
- Coverage     39.84%   39.83%   -0.02%
- Complexity      149      150       +1
============================================
  Files           146      146
  Lines         23554    23554
  Branches        422      422
============================================
- Hits           9385     9382       -3
- Misses        12874    12876       +2
- Partials       1295     1296       +1

Impacted Files
Coverage Δ

pkg/vfs/reader.go
63.86% <0.00%> (-2.19%)
:arrow_down:

pkg/meta/redis.go
69.27% <0.00%> (-0.22%)
:arrow_down:

pkg/meta/sql.go
66.96% <0.00%> (+0.10%)
:arrow_up:

.../src/main/java/io/juicefs/JuiceFileSystemImpl.java
58.33% <0.00%> (+1.17%)
: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 05ce4ad...d6e4765. Read the comment docs.