Use count for buckets.

Terraform plan looks ok, except possibly this:
# google_compute_backend_bucket.firmware_artefacts_ci[0] must be replaced
-/+ resource "google_compute_backend_bucket" "firmware_artefacts_ci" {
      ~ creation_timestamp      = "2023-11-06T07:43:36.660-08:00" -> (known after apply)
      - custom_response_headers = [] -> null
      ~ description             = "Contains CI firmware artefacts for FT log" -> "Contains CI firmware artefacts for FT log 0"
      ~ id                      = "projects/1071548024491/global/backendBuckets/firmware-artefacts-ci-backend" -> (known after apply)
      ~ name                    = "firmware-artefacts-ci-backend" -> "firmware-artefacts-ci-backend-0" # forces replacement
      ~ self_link               = "https://www.googleapis.com/compute/v1/projects/armored-witness/global/backendBuckets/firmware-artefacts-ci-backend" -> (known after apply)
        # (3 unchanged attributes hidden)
    }

  # google_compute_backend_bucket.firmware_log_ci[0] must be replaced
-/+ resource "google_compute_backend_bucket" "firmware_log_ci" {
      ~ creation_timestamp      = "2023-11-06T07:43:36.438-08:00" -> (known after apply)
      - custom_response_headers = [] -> null
      ~ description             = "Contains CI firmware transparency log" -> "Contains CI firmware transparency log 0"
      ~ id                      = "projects/1071548024491/global/backendBuckets/firmware-log-ci-backend" -> (known after apply)
      ~ name                    = "firmware-log-ci-backend" -> "firmware-log-ci-backend-0" # forces replacement
      ~ self_link               = "https://www.googleapis.com/compute/v1/projects/armored-witness/global/backendBuckets/firmware-log-ci-backend" -> (known after apply)
        # (3 unchanged attributes hidden)
    }

Is the bucket name change and replacement for the backends okay?

Terraform plan looks ok, except possibly this:
# google_compute_backend_bucket.firmware_artefacts_ci[0] must be replaced
-/+ resource "google_compute_backend_bucket" "firmware_artefacts_ci" {
      ~ creation_timestamp      = "2023-11-06T07:43:36.660-08:00" -> (known after apply)
      - custom_response_headers = [] -> null
      ~ description             = "Contains CI firmware artefacts for FT log" -> "Contains CI firmware artefacts for FT log 0"
      ~ id                      = "projects/1071548024491/global/backendBuckets/firmware-artefacts-ci-backend" -> (known after apply)
      ~ name                    = "firmware-artefacts-ci-backend" -> "firmware-artefacts-ci-backend-0" # forces replacement
      ~ self_link               = "https://www.googleapis.com/compute/v1/projects/armored-witness/global/backendBuckets/firmware-artefacts-ci-backend" -> (known after apply)
        # (3 unchanged attributes hidden)
    }

  # google_compute_backend_bucket.firmware_log_ci[0] must be replaced
-/+ resource "google_compute_backend_bucket" "firmware_log_ci" {
      ~ creation_timestamp      = "2023-11-06T07:43:36.438-08:00" -> (known after apply)
      - custom_response_headers = [] -> null
      ~ description             = "Contains CI firmware transparency log" -> "Contains CI firmware transparency log 0"
      ~ id                      = "projects/1071548024491/global/backendBuckets/firmware-log-ci-backend" -> (known after apply)
      ~ name                    = "firmware-log-ci-backend" -> "firmware-log-ci-backend-0" # forces replacement
      ~ self_link               = "https://www.googleapis.com/compute/v1/projects/armored-witness/global/backendBuckets/firmware-log-ci-backend" -> (known after apply)
        # (3 unchanged attributes hidden)
    }

Is the bucket name change and replacement for the backends okay?

So long as the bucket names match the bucket resources it should be fine I think.
Do you think we'll be able to use the same count trick on the paths in the LB too?

Terraform plan looks ok, except possibly this:
# google_compute_backend_bucket.firmware_artefacts_ci[0] must be replaced
-/+ resource "google_compute_backend_bucket" "firmware_artefacts_ci" {
      ~ creation_timestamp      = "2023-11-06T07:43:36.660-08:00" -> (known after apply)
      - custom_response_headers = [] -> null
      ~ description             = "Contains CI firmware artefacts for FT log" -> "Contains CI firmware artefacts for FT log 0"
      ~ id                      = "projects/1071548024491/global/backendBuckets/firmware-artefacts-ci-backend" -> (known after apply)
      ~ name                    = "firmware-artefacts-ci-backend" -> "firmware-artefacts-ci-backend-0" # forces replacement
      ~ self_link               = "https://www.googleapis.com/compute/v1/projects/armored-witness/global/backendBuckets/firmware-artefacts-ci-backend" -> (known after apply)
        # (3 unchanged attributes hidden)
    }

  # google_compute_backend_bucket.firmware_log_ci[0] must be replaced
-/+ resource "google_compute_backend_bucket" "firmware_log_ci" {
      ~ creation_timestamp      = "2023-11-06T07:43:36.438-08:00" -> (known after apply)
      - custom_response_headers = [] -> null
      ~ description             = "Contains CI firmware transparency log" -> "Contains CI firmware transparency log 0"
      ~ id                      = "projects/1071548024491/global/backendBuckets/firmware-log-ci-backend" -> (known after apply)
      ~ name                    = "firmware-log-ci-backend" -> "firmware-log-ci-backend-0" # forces replacement
      ~ self_link               = "https://www.googleapis.com/compute/v1/projects/armored-witness/global/backendBuckets/firmware-log-ci-backend" -> (known after apply)
        # (3 unchanged attributes hidden)
    }

Is the bucket name change and replacement for the backends okay?

So long as the bucket names match the bucket resources it should be fine I think.
Do you think we'll be able to use the same count trick on the paths in the LB too?

I tried to do it for the path_rules, but got this error: The "count" object can only be used in "module", "resource", and "data" blocks, and only when the "count" argument is set. I think we'd need to figure out something smarter with path matching if it's supported by the module?


luci-mod-network: show 'Interface disabled' in status

[x] This PR is not from my main or master branch :poop:, but a separate branch :white_check_mark:
[x] Each commit has a valid :black_nib: Signed-off-by<EMAIL_ADDRESS>row (via git commit --signoff)
[x] Each commit and PR title has a valid :memo: <package name>: title first line subject for packages
[ ] Incremented :up: any PKG_VERSION in the Makefile
[x] Tested on: (armv8, openwrt 23.05, Chrome v130) :white_check_mark:
[ ] ( Preferred ) Mention: @ the original code author for feedback
[x] ( Preferred ) Screenshot or mp4 of changes:
[ ] ( Optional ) Closes: e.g. openwrt/luci#issue-number
[ ] ( Optional ) Depends on: e.g. openwrt/packages#pr-number in sister repo
[ ] Description: (describe the changes proposed in this PR)

Link to https://github.com/openwrt/luci/pull/6846

Closed by 1c61a669509c3780b0642aad07a771be8bea7e5e


[FEATURE REQUEST] Multi-Thread + RLT text + a problem

Can you add multi thread? it takes a lot of time to download the chapters, for 1500 it takes like 30mins if it's multi threaded it would be much faster
and can you make the pdf conversion support right to left text, Font changer and font size. with these three it would be perfect
I had to make all these by myself..
plus in some websites the chapter container takes some times to appear (300-1000ms)
if I make it auto detect it picks a different 'box', and when I manually select it I get no output, however that get fixed when I use a browser (chrome/firefox)
also there is a problem,
in whatever website the text is for example like this
"
Hello
Hello world
Github
"
when scraped it becomes
"
Hello
Hello world
Github
"
plus a lot of times what the text in the pre preview is like
"
Hello
e3c99b1
don't download
2h9asja
Hello world
ja012u
don't download
9012ia
"
but when I grab the chapters in txt file it becomes something like
"
Hello  e3c99b1  don't download
2h9asja
Hello world  ja012u
don't download
9012ia
'"
you get the idea, these whatever things are to protect the text, anyway they are pretty easy to remove with np++ but with the output is ruined like that it gets complicated.. very complicated.
and thank you for this great tool.

Sorry for the late reply.
Multi-Threading is not the problem why it takes so long, the main bottleneck of grabbing is the host server on the other side. If the server is slow to respond with the requested chapter then sending multiple requests will not help but make it even worse for the host server (I can seem like a DDoS attack).
I currently don't have time to work on NG so as a workaround for your PDF request you could export to EPUB and then use another, more sophisticated, program to convert and format the novel to your liking.
For the late loading container, try using the headless browser option (in manual grabbing), it uses a real browser to visit the page with better javascript (container loading etc.) coverage. Maybe that helps.
You can also blacklist certain HTML elements via css selectors which will be removed from the finished chapter to circumvent the protection.


Implement Profiles/Create Account page on 3box.io

Feature Description
We should create a separate "Create Account" page that is different from the "Sign in" flow. This page will be linked to from the Profiles and Create Account buttons in the navbar.
Needs
User Need
When a user lands on 3Box.io and attempts to sign in or create account, the flow is the same. This is great for existing users, but it's not so great for new users. We should give them more of a description as to what is happening.
Project Needs
By creating a separate page for creating a new account, we can optimize our analytics funnels to be better able to distinguish from sign ins from existing users and creating new accounts.
Design Spec

@oznekenzo can we see how this version looks?
Overview

### Background Image
It should just be retiling the right side background with this image:
![flow](https://user-images.githubusercontent.com/5216274/49624264-cf211180-f99e-11e8-83a6-38d8bd156cff.png)
### Moon
Here's the png.
![ethermoon](https://user-images.githubusercontent.com/5216274/49624353-1ad3bb00-f99f-11e8-8e20-f54d486fe813.png)
### Copy Updates
Seen in the image


[fix] (bloom filter) Fix the bloom filter calculation for date and datetime (#43351)

pick from master #43351

run buildall


#675 - Remove events functionality

Preferred way is to use the on* syntax in render().
BREAKING CHANGE: Remove events spec in favour of on* attributes in render(). Implements #675.
If we ever find that similar functionality is required, it's easier to add rather than subtract API. Doing this now ensures we go into 1.0 with a clean slate.

What about events for props? (https://github.com/skatejs/skatejs#event)
Shouldn't there be the same logic?

LGTM, lots of red is good!

@nadiam84

What about events for props? (https://github.com/skatejs/skatejs#event)

That is for triggering events when the property changes. This PR removes the events constructor option for automatically binding events to the host to listen for events on the host and descendant elements through event delegation.

LGTM

LGTM


Change how Github releases are formated

There's a good format to follow: https://github.com/commitizen/cz-cli
See an example of some simple library: https://github.com/sobolevn/recase/releases

I'll take this and work on it over the next week.
Thanks,
-Gnubyte

Hi @lk-geimfari & @sobolevn
https://github.com/gnubyte/mimesis
I have added the commitizen package to my fork of the mimesis package with the default commitizen plugin, and badge addded to the readme.
Are there any plugins that you as main contributors feel need to be included?
The plugins will affect what needs updates need to be added to the contributing.md file.

Also what is the criteria for fulfilling the issue?
Thank you.

I am personally creating changelog and always update release notes on GitHub on every new release. I close this question, but I will return to it if difficulties arise.


App default credentials do not work on App Engine Managed VMs.

When running locally or on Google Compute Engine, app default credentials are used to provide authentication without needed to provide a private key. However, this does not work when deployed to Managed VMs.

Have you tried against master? We just started using google-auth-library, but haven't made a release yet.

Yes, this is against master. It's possible that managed VMs does not expose the service account from the underlying VM.

I think it should... I just came across this library which appears to provide that functionality (getting a token) from within Managed VMs.

This might be that the service account associated with the managed VM doesn't have the datastore scope. Investigating and will update.

Yeah they seem to be hitting the same endpoint as long as it's working as it should.

Okay. That is exactly the problem.

Managed VMs default service account doesn't include scopes to access datastore, pubsub, etc.
The .yaml config to add the scope isn't current documented (it's a beta setting)

Once the settings are documented, we should add some documentation here around adding scopes to MVMs/GCE to allow access.

@jonparrott Thanks for investigating! Can you open a new issue and point to the docs that helped you resolve this issue so we know how to document it for our users?

It's not currently documented :( I'll create a new issue here once I get the docs published.

Okey doke! I'll reopen this to keep tracking the issue.

The .yaml config to add the scope isn't current documented (it's a beta setting)

@jonparrott if that's documented now (?), that's probably good enough. Maybe a simple line could be added to https://github.com/GoogleCloudPlatform/gcloud-common/tree/master/authentication with something like "To enable the scopes on a managed VM, see ..."

This is a non-issue now, as all the requisite scopes for GCP APIs are now defaulted in MVMs. Users should never have to change the scopes. If they do, I consider that that's a bug on our end.

Oh, great. Thanks again!


Switched to Whisker and Band glyphs for ErrorBars and Spread

Bokeh introduced glyphs for errorbars and confidence bands a while ago, which both look better and are more efficient than the multi_line and patches implementation we were using previously. Since the categorical overhaul this is also the only way these elements will work with categorical axes.
Fixes: https://github.com/ioam/holoviews/issues/1893
Old ErrorBars:

New ErrorBars (note the addition of whiskers):

Old Spread:

New Spread (note the lack of border lines one left and right):

Makes sense to update the glyphs. Any other places where you think Bokeh might now have a more suitable glyph? Or maybe some glyph ideas could be posted as feature requests to bokeh?

Thanks for mentioning that, Area is also better written using the Band glyph. Will rebuild test data and then this will be ready to merge.

Test are now green. Merging.


Roll engine 1cada0a6dca6..f15cc3402938 (1 commits)

git@github.com:flutter/engine.git/compare/1cada0a6dca6...f15cc3402938
git log 1cada0a6dca6..f15cc3402938 --no-merges --oneline
2019-09-19<EMAIL_ADDRESS>Roll src/third_party/skia 18531cde2ab7..9a8b846baf43 (1 commits) (flutter/engine#12360)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/6437669896192000 , https://cirrus-ci.com/task/6156194919481344

Commit queue failed; closing this roll.


cv2.error: /io/opencv/modules/core/src/lda.cpp  At least two classes are needed to perform a LDA

Hello,
I'm having an issue with the training stage, using the command:
sudo docker run --rm
-v $(pwd)/resized:/root/resized
-v $(pwd)/reports:/root/reports
-v $(pwd)/catsmodel:/root/catsmodel
pathbreak/deepvisualminer
python3 /root/deepvisualminer/facerec_train.py train /root/reports/dataset.csv
80 /root/reports/testset.csv /root/catsmodel 1 1 1
The error I'm getting is shown below, any ideas?
Eigen done
Traceback (most recent call last):
File "/root/deepvisualminer/facerec_train.py", line 487, in
train( sys.argv[2], int(sys.argv[3]), sys.argv[4], sys.argv[5], bool(sys.argv[6]), bool(sys.argv[7]), bool(sys.argv[8]) )
File "/root/deepvisualminer/facerec_train.py", line 215, in train
fischer_recog.train(train_images, training_labels)
cv2.error: /io/opencv/modules/core/src/lda.cpp:1018: error: (-5) At least two classes are needed to perform a LDA. Reason: Only one class was given! in function lda
Thanks
D

@xtaylord Thank you very much for using my software and taking the time to report this !
The "At least two classes..." is referring to number of labels (cats in this case) in the dataset.
It turns out to be a bug in my software where I'm not handling the entirely common possibility that a user may have only one cat and is training the model to recognize  that single cat in photos (in my defense, I've always had more than one cat and never even tested for single cat recognition :D).
Basically, the software trains three alternative algorithms, and one of those - FischerFaces - requires a minimum of two labels/cats.
What you can do now:
Disable FischerFaces algorithm during training, testing and mining.

Training:
Use this command line (note that the second last argument is now 0 instead of 1 to disable FischerFaces):

sudo docker run --rm
-v $(pwd)/resized:/root/resized
-v $(pwd)/reports:/root/reports
-v $(pwd)/catsmodel:/root/catsmodel
pathbreak/deepvisualminer
python3 /root/deepvisualminer/facerec_train.py train /root/reports/dataset.csv
80 /root/reports/testset.csv /root/catsmodel 1 0 1

Testing:
Same change as training

sudo docker run --rm \
  -v $(pwd)/resized-334x311:$(pwd)/resized-334x311 \
  -v $(pwd)/reports:/root/reports \
  -v $(pwd)/catsmodel:/root/catsmodel \
  deepvisualminer \
  python3 /root/deepvisualminer/facerec_train.py test \
    /root/reports/testset.csv /root/catsmodel 1 0 1

Mining:
In your pipeline configuration YAML file, remove FischerFaces from  strategies and set outputlabel  to eigen or lbp or mostvotes.
Example:

- name: cat-face-recognizer
  type: recognizer
  inputs:
  - files

  params:

    # The model directory where model files were generated during training.
    model: /root/models/mycats/

    # strategies: list of recognizers to run. one or more of [eigen, fischer, lbp]
    strategies:
    - eigen
    - lbp
    # output : which labels to output. Can be one of [all, mostvotes, <strategies>] where
    #
    # "all" means outputs of all strategies
    # "mostvotes" means single output which has most votes from multiple strategies. If there'
    #       no clear majority, it'll output all.
    # "<strategies>" means output of one or more of the strategies above.
    #       For example,
    #           output:
    #           - lbp
    #           - eigen
    #       means include only outputs of lbp and eigen in the outputs.
    outputlabel:
    - eigen
...

From my side, I'll make corrections to handle single cat (or single label of any kind), but this may take some days.
Any other feedback and suggestions are very welcome.

Thanks Karthik,
I'll do some testing later in the week!
Cheers
Dan

From: Karthik Shiraly<EMAIL_ADDRESS>Sent: 01 July 2018 13:40
To: pathbreak/deepvisualminer
Cc: xtaylord; Mention
Subject: Re: [pathbreak/deepvisualminer] cv2.error: /io/opencv/modules/core/src/lda.cpp At least two classes are needed to perform a LDA (#1)
@xtaylordhttps://github.com/xtaylord Thank you very much for using my software and taking the time to report this !
The "At least two classes..." is referring to number of labels (cats in this case) in the dataset.
It turns out to be a bug in my software where I'm not handling the entirely common possibility that a user may have only one cat and is training the model to recognize that single cat in photos (in my defense, I've always had more than one cat and never even tested for single cat recognition :D).
Basically, the software trains three alternative algorithms, and one of those - FischerFaces - requires a minimum of two labels/cats.
What you can do now:
Disable FischerFaces algorithm during training, testing and mining.

Training:
Use this command line (note that the second last argument is now 0 instead of 1 to disable FischerFaces):

sudo docker run --rm
-v $(pwd)/resized:/root/resized
-v $(pwd)/reports:/root/reports
-v $(pwd)/catsmodel:/root/catsmodel
pathbreak/deepvisualminer
python3 /root/deepvisualminer/facerec_train.py train /root/reports/dataset.csv
80 /root/reports/testset.csv /root/catsmodel 1 0 1

Testing:
Same change as training

sudo docker run --rm
-v $(pwd)/resized-334x311:$(pwd)/resized-334x311
-v $(pwd)/reports:/root/reports
-v $(pwd)/catsmodel:/root/catsmodel
deepvisualminer
python3 /root/deepvisualminer/facerec_train.py test
/root/reports/testset.csv /root/catsmodel 1 0 1

Mining:
In your pipeline configuration YAML file, remove FischerFaces from strategies and set outputlabel to eigen or lbp or mostvotes.
Example:

name: cat-face-recognizer
type: recognizer
inputs:

files

params:
The model directory where model files were generated during training.
model: /root/models/mycats/
strategies: list of recognizers to run. one or more of [eigen, fischer, lbp]
strategies:

eigen
lbp

output : which labels to output. Can be one of [all, mostvotes, ] where

"all" means outputs of all strategies
"mostvotes" means single output which has most votes from multiple strategies. If there'
no clear majority, it'll output all.
"" means output of one or more of the strategies above.
For example,
output:
- lbp
- eigen
means include only outputs of lbp and eigen in the outputs.
outputlabel:

eigen
...

From my side, I'll make corrections to handle single cat (or single label of any kind), but this may take some days.
Any other feedback and suggestions are very welcome.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/pathbreak/deepvisualminer/issues/1#issuecomment-401604204, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFu2G8LobAQjs2RVjtbYWibcd-qaXgacks5uCMMngaJpZM4U9p7h.


Browser Hangs when allowing

Hi Sirkris,
I have an issue, and I don't know where to go to solve it, so I'll post it here.
I implemented the code that you have here, following all the instructions, and all the parameters are correct, but when I accept, the browser just hangs there, and doesn't do anything. No responses of such.
When I did it initially, I did get an email confirming I authorized my app to have access to my reddit account, but I don't get any tokens returned to me.
What do you think would be the cause of this?
Sincerely,
Chris Joly

Can you provide the specific code you used?

public RedditClient logIntoReddit(Dictionary<string, string> credentials = null)
{
if (credentials == null)
{
// Hard Coded API credentials
}
else {
string appId = credentials["appId"];
string appSecret = credentials["appSecret"];
string userAgent = credentials["userAgent"];
int port = int.Parse(credentials["port"]);
}

// authTokenRetriever is a variable declared at the class level
this.authTokenRetriever = new Reddit.AuthTokenRetriever.AuthTokenRetrieverLib(appId, port,"localhost", null, appSecret);
// Start the callback listener.  --Kris
// Note - Ignore the logging exception message if you see it.  You can use Console.Clear() after this call to get rid of it if you're running a console app.
authTokenRetriever.AwaitCallback();

//// Replace this with whatever you want the app to do while it waits for the user to load the auth page and click Accept.  --Kris
RedditClient rdtClient;

// Get the authorization URL

string authorizationUrl = authTokenRetriever.AuthURL();

Console.WriteLine("Please visit the following URL to authorize your application:");
OpenBrowser(authorizationUrl);
Console.WriteLine("After authorization, paste the code you received here:");

// Read the authorization code from the console input
string authorizationCode = Console.ReadLine();

// Retrieve the refresh token
try
{

    string refreshToken = authTokenRetriever.RefreshToken;
    Console.WriteLine("Your refresh token is: " + refreshToken);
}
catch (Exception ex)
{
    Console.WriteLine("An error occurred: " + ex.Message);
}

rdtClient = new RedditClient(appId, authTokenRetriever.RefreshToken, appSecret, null, userAgent);
return rdtClient;

}

It's been hanging for the past few minutes

MSVBot is the name of the application
Many-Sirs-4588 is my Username

Hmm could there be a firewall or some other routing issue?  Are you sure it's binding to port 8080 successfully?  Maybe try a different port and see what happens?

It's most likely the case! I have Norton, and their firewall is pretty robust! I have no idea how to allow ports through!
I've tried a few other ports, but no dice!
Is there a programmatic way to open the port?


/api/blocks/pages?page= time out

request '/api/blocks/pages?page=443323' time out

I've just loaded that page

Feel free to reopen if you can reproduce

SELECT "block"."id", "block"."hash", "block"."epoch_no", "block"."slot_no", "block"."block_no", "block"."previous", "block"."merkel_root", "block"."slot_leader", "block"."size", "block"."time", "block"."tx_count", "slot_leader"."hash"
FROM "block" INNER JOIN "slot_leader" ON "block"."slot_leader" = "slot_leader"."id"
WHERE NOT ("block"."slot_no" IS NULL)
ORDER BY "block"."slot_no" ASC
 LIMIT 10 OFFSET 4435560;

this sql cost 10s


ctrl+k, ctrl+d does not format code as indicated

I am looking at Default keyword shortcuts and can see two entries:
{ "key": "ctrl+k ctrl+d",
 "command": "editor.action.formatDocument",
 "when": "editorHasDocumentFormattingProvider && editorTextFocus && !editorReadonly" },
{ "key": "shift+alt+f",
  "command": "editor.action.formatDocument",
  "when": "editorHasDocumentFormattingProvider && editorTextFocus && !editorReadonly" },

Yet the first shortcut never seems to work, i tried overriding with shift+alt+ set to empty command, but that doesn't work, what do I do to make it work?
meta:

VSCode Version: Code - Insiders 1.7.0-insider (788caba5a3ca1c2b137353f4384bb0e026db1a31, 2016-10-21T23:41:55.553Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

html-snippets
abusaidm
0.0.17

htmltagwrap
bradgashler
0.0.3

vscode-stylesheet-formatter
dbalage
0.2.0

vscode-npm-script
eg2
0.0.21

auto-rename-tag
formulahendry
0.0.7

vscode-JS-CSS-HTML-formatter
lonefy
0.2.1

JasmineSnippets
xabikos
0.2.0

Steps to Reproduce:

It depends on the current file, its language, and the set of installed extensions. Note this bit of the keybinding rule: editorHasDocumentFormattingProvider. It means, that formatting is only available when a formatter has been installed. An easy quick-check is the context menu - it will only show the format document entry when a formatter for that language is available.

but "shift+alt+f" work on the same file (for example HTML)

You are right... Very funky...

Seems like there is a conflict with MoveSelectionToNextFindMatchAction. Tough call... On the one side I don't want to break an existing keybinding but on the other I think it would be good if we have common VS shortcuts.
@waderyan Do we have a VS key-map extension? That seems like a nice place to define  such a keybinding.

@jrieken VS keymap is on the roadmap. This use case is noted.

Removed label bug since we have decided to remove that keybinding

Is this released yet? Code insiders? Does the change indicate that i will have to create my own shortcut?


SIGSEGV when removing an object before commit

Hello, I am currently writing Rust wrappers for NGT, inspired by Python/Go/Ruby bindings.
During a test where I do the following:

Create new empty index
Insert an object
Remove it --> This will SIGSEGV

Here is the backtrace with gdb:
Program received signal SIGSEGV, Segmentation fault.
std::_Bit_reference::operator= (this=0x7fffffff54f0, __x=true) at /usr/include/c++/9.3.0/bits/stl_bvector.h:93
93              *_M_p |= _M_mask;
(gdb) bt
#0  std::_Bit_reference::operator= (this=0x7fffffff54f0, __x=true) at /usr/include/c++/9.3.0/bits/stl_bvector.h:93
#1  0x00007ffff7f15bab in NGT::NeighborhoodGraph::setupSeeds (this=0x555555ce3198, sc=..., seeds=..., results=std::priority_queue wrapping: std::vector of length 1, capacity 1 = {...},
    unchecked=std::priority_queue wrapping: std::vector of length 0, capacity 0, distanceChecked=...) at /home/raru/dev/workspaces/rust/ngt-rs/ngt-sys/NGT/lib/NGT/Graph.cpp:313
#2  0x00007ffff7f15f26 in NGT::NeighborhoodGraph::search (this=0x555555ce3198, sc=..., seeds=...) at /home/raru/dev/workspaces/rust/ngt-rs/ngt-sys/NGT/lib/NGT/Graph.cpp:473
#3  0x00007ffff7f3732b in NGT::GraphIndex::search (this=0x555555ce3130, sc=..., seeds=...) at /home/raru/dev/workspaces/rust/ngt-rs/ngt-sys/NGT/lib/NGT/Index.h:1117
#4  0x00007ffff7f38ebe in NGT::GraphAndTreeIndex::remove (this=0x555555ce3130, id=3, force=false) at /home/raru/dev/workspaces/rust/ngt-rs/ngt-sys/NGT/lib/NGT/Index.h:1368
#5  0x00007ffff7ec30cc in NGT::Index::remove (this=0x555555ce5960, id=3, force=false) at /home/raru/dev/workspaces/rust/ngt-rs/ngt-sys/NGT/lib/NGT/Index.h:445
#6  0x00007ffff7eda05e in ngt_remove_index (index=0x555555ce5960, id=3, error=0x555555ce3100) at /home/raru/dev/workspaces/rust/ngt-rs/ngt-sys/NGT/lib/NGT/Capi.cpp:622
#7  0x000055555575b46e in ngt::index::Index::remove (self=0x555555ce3988, id=3) at /home/raru/dev/workspaces/rust/ngt-rs/src/index.rs:241

It starts when I call ngt_remove_index. I am using NGT version 1.11.2.
Is it because we should not try to insert and delete the same object before building an index ?
In which case, would it be possible to get an error instead of SIGSEGV ?
I think this could be less surprising.

Thank you for your information. I have released v1.11.4 which fixes the bug.

@lerouxrgd
Thank you for writing Rust  wrappers for NGT! May I set a link to your repository in the NGT repository?

Thank you for fixing the issue !
Sure please go ahead and add a link to my repository! I just published it on crates.io so now it is fully usable for Rust users.


License

Could you add a license? A BSD license would make this project wonderfully useful to me.

License was added in dc9256e4a8381cbb160d9b4928f0e26c8984c385


Documentation: remove LTS references

We have decided to move away from the LTS model for Cilium, and instead have
moved to supporting the most recent three releases instead. Remove LTS
references accordingly from the documentation.
Signed-off by: Ian Vernon<EMAIL_ADDRESS>

This change is

Coverage increased (+0.007%) to 45.314% when pulling b3bfb286cf9d0af55adfca55ec00e926a9069ada on pr/ianvernon/lts-docs-removal into 4d95cc8b02ecfd1e0ee42bdd01084b721aca740a on master.

test-docs-please


[sw] Fix embedded linking not including .crt or .vectors.

Fixes #1058.

@mcy can you add a signed-off-by line to this one and ensure that CI succeeds?

Oops, accidentally hit "close".
Also, I'd really appreciate it if someone with more linker expertise can comment with a better solution: the problem I'm seeing is that, before this change, meson generates a linker call similar to
ld -o sw.elf sw.c.o \
  --no-undefined --as-needed --nostdlib
  -( /* static library dependencies as .a archives */ -)
  -rpath-link build-out/...

For reasons unclear to me, the linker script does not correctly pull the .crt section out of libcrt.a, nor the .vector section out of libirq.a. For now I've rearranged Meson so that the object files with the sections I care about are .o "input files", rather than .a libraries being linked in; however, I think that this solution is wrong and that there should be a way to do this just by pulling out specific sections out of the .a files.
@imphil do you have any clues (or know who someone who might)?

How did the linker call look with make?

Make emits .a files, but those do not participate in linking; it instead links in every .o file is builds for every binary (which is where I got my idea for this bandaid).

From what I remember, static libraries (*.a files) are only searched for undefined references. Object files are unconditionally used. So you either need to make sure that _crt is being searched for, or link the .o file. Linking crt.o is rather common, so I'd go for that. Otherwise, you can either add EXTERN(_crt) to the linker script, or add  -Wl,--undefined=_crt as linker flag.
(I did give it a try and that theory seems to be correct. It additionally runs into a problem with the /DISCARD/ : { *(*) } statement in our linker file preventing linking. I didn't debug that further; removing that statement does the trick for me, let me know if you get stuck and I'll have a look. The discard part was added to prevent the build id showing up in the binary, but that's something that we already prevent by -Wl,--build-id=none, so removing this line again shouldn't hurt.)


add key, ERROR: address  rejected

gaiacli keys add test_ledger --ledger
ERROR: address  rejected
ledger v1.6.0
cosmos app: v2.12.0
client_name: gaiacli
version: 2.0.10

Same issue with ledger 1.6.0 / cosmos app v2.14.0 / gaiacli 2.0.10

This is known issue in gaiacli:  https://github.com/cosmos/cosmos-sdk/issues/6313


Incorrect While Loop Behavior

(From Martin's Email):
Consider the following program.
h : Int -> Int
h(y) = while y<3 do y+1
f_OneState' : Int -> Int
f_OneState'(x) = let y = while x<5 do x+1 in y * h(y)
It behaves as expected:

h(5)
5

f_OneState'(1)
25

The while loop in f_OneState' returns 5, which is bound to y and then passed to h, yielding 25. But if we simply substitute the code for h, the result changes:
f_OneState : Int -> Int
f_OneState(x) = let y = while x<5 do x+1 in y * (while y<3 do y+1)

f_OneState(1)
5

It seems that the y in the while loop gets reinitialized with the value of x, which becomes clear when we use f_OneState  with different arguments.

f_OneState(2)
10

The current behavior violates referential transparency; in both cases the result should be 25. I think the error will go away once let properly introduces state, but I wanted to make you aware of this test case.
--
Martin

It seems that the y in the while loop gets reinitialized with the value of x

It does not. Both the left loop and the right loop have x = 1 in their local context. After the left loop executes, y = 5. When the right loop executes y < 3 is false, so it returns the value in its local context (x = 1). The result is y * 1 = 5, as is to be expected before let bindings can create local variables for while loops.
However, the change with let expressions will soon be in, and then the result will indeed be 25.


Collection datatype "contains" operator support (Cassandra 2.1)

From Cassandra 2.1, CQL has supported "contains" operator on the collection column (such as list, set). This operator is not implemented in cqlengine yet.
For now, to use this I have to do that:
from cqlengine import operators, statements

class CQLContainsOperator(operators.EqualsOperator):
    symbol = 'CONTAINS'
    cql_symbol = 'CONTAINS'

where = statements.WhereClause('col_name', CQLContainsOperator(), filter_val)
query = TheModel.objects.filter(where))

Please add this feature to cqlengine when you have time.
P/S: I did try to make a pull request, but can not get all the tests run success.
Thank you,

We are migrating all Github issues to the public Jira. Please find this issue in Jira: https://datastax-oss.atlassian.net/browse/PYTHON-258


Make SDX Local Controller a WSGI app

Resolves #86.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 10 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 77.103%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sdx_lc/app.py
0
10
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
978

Relevant Lines:
1215

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 11 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 77.273%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sdx_lc/app.py
0
11
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
978

Relevant Lines:
1212

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 11 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 77.273%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sdx_lc/app.py
0
11
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
978

Relevant Lines:
1212

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 18 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 77.729%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sdx_lc/app.py
0
18
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
978

Relevant Lines:
1204

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 19 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 77.671%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sdx_lc/app.py
0
19
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
978

Relevant Lines:
1205

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 19 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 77.671%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sdx_lc/app.py
0
19
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
978

Relevant Lines:
1205

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 19 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 77.671%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sdx_lc/app.py
0
19
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
978

Relevant Lines:
1205

💛  - Coveralls

ASGI vs WSGI;
Flask vs. uvicorn vs. gunicorn
FastAPI vs. swagger UI
Please write a blog for educational purpose...

@YufengXin Is that a request meant for me?
:see_no_evil: :hear_no_evil: :speak_no_evil:

@sajith Yes-:) I assume you're moving to upgrade sdx-controller too?
The justification on the choice would be nice to be included in the annual report.

This is already done on sdx-controller.
For production usage, using Flask's built-in web server directly is not a good idea, since it is single threaded and synchronous.  It is good enough during development, but it just not meant to be used in production.  It should be used in conjunction with a WSGI server (Gunicorn, uWSGI),   since it is more secure, scalable, and can work with reverse proxy web servers (such as nginx or caddy, which we will need for SSL termination).
ASGI is essentially the updated version of WSGI that understands async/await.  We are not quite there, but I liked uvicorn, which is an ASGI server, enough to make our app sort-of-ASGI with WsgiToAsgi() adaptor.  We can always switch to gunicorn or uWSGI or something else if we need to do so.

The first part is clear as we always do.
I don't know much about ASGI. So the key is the wsgi_to_asgi converter. as my naive understanding is that FASTAPI is to ASGI as Flask to WSGI. But somebody on Internet said Flask2.0 supports ASGI....
Nice upgrade. I'll read more into it.

FastAPI is an alternative to connexion and Flask, if I understood correctly.  It probably would be nicer too, but it is also very likely to come with its own set of limitations.
Since the choice has already been made, and since we're somewhat familiar with Flask and connexion, and since there is a cost (time and opportunity) to switching, I am of the opinion that we should continue working with the current setup.  Unless there is a good reason to switch to something else, of course. :-)

Also the WsgiToAsgi() call is really optional.  We can simply remove that line and use gunicorn instead of uvicorn and forget that we ever tried to use an ASGI server.

Totally agree. Let's keep it this way, because you made it work well-:)

Thank you.  There's more to be done, of course. :-)


Add full page for debugging WDCs

Add debugging tips, including info about:

The not supported debugger
Where to add breakpoints--both in the simulator page and the popup depending on the phase
Using ?src= to maintain the same connector in the simulator

Should we add default log locations as well? Not as crucial with the unsupported debugger, but still would be useful in some scenarios.

Added a wdc_debugging topic.
I made a new issue to discuss whether we want to document the log file locations.


Order ignoreCase with column date generate SQL inconsistent

Ordering with ignore case in a date field is generating an order by lower (date column) which totally bugs the sorting result, using pure Spring-JPA no problem occurs.
Spring-JPA

QueryDSL

Add "lower" ignoring the column type

Spring-JPA

QueryDSL

Add "lower" ignoring the column type

buildOrderPropertyPathFrom does not exists in QueryDSL anymore, please upgrade to a more recent version of QueryDSL.
For example:
<dependency>
    <groupId>com.querydsl</groupId>
    <artifactId>querydsl-jpa</artifactId>
    <version>4.3.1</version>
</dependency>

134/5000
I am using version 4.3.1. I'm using Sort and not QSort, the Sort is converted to OrderSpecifier using buildOrderPropertyPathFrom

Sort and QSort aren't classes in QueryDSL, and buildOrderPropertyPathFrom doesn't exist in our entire codebase: https://github.com/querydsl/querydsl/search?q=buildOrderPropertyPathFrom&unscoped_q=buildOrderPropertyPathFrom .
Are you sure this isn't an issue in Spring Data instead?
Also, please verify the dependencies you're actually using with mvn dependency:tree or anything equivalent.

Here is your bug, in Spring Data instead: https://github.com/spring-projects/spring-data-jpa/blob/e27933455efa6d1821dea23abd2bbe109b5d59a7/src/main/java/org/springframework/data/jpa/repository/support/Querydsl.java#L238-L241 . Please file an issue there 😄

Yes,

Aqui está seu bug, no Spring Data: https://github.com/spring-projects/spring-data-jpa/blob/e27933455efa6d1821dea23abd2bbe109b5d59a7/src/main/java/org/springframework/data/jpa/repository/support/ Querydsl.java # L238-L241 . Registre um problema lá😄

Yes, you are right, thank you very much, I was creating 1 test case to open the issue there!


Guessit Error when running manually

First of I would like to say thanks for you putting so much time and effort into this and when I get it working it's going to be a lifesaver.
I have just set everything up but when I try a manual run I get the following error:

File "C:\Mp4_Automater\manual.py", line 155, in guessInfo
guess = guessit.guessit(fileName)
AttributeError: 'module' object has no attribute 'guessit'

What could I have done wrong because I followed the setup exactly but just cannot get it to work !

You just need to update to the latest version of guessit


Prusa ?

Missing information about the Prusa and the correct setting to use in the PrusaSlicer.

0.20mm QUALITY  or 0.20mm SPEAD
Generic PLA
Original Prusa i3 MK3S & MK3S+ MMU2S Single


Errors in Project-swift.h

Having issues compiling in Xcode 7 beta 6 (Swift 2.0).
Getting a compile error:
Type argument 'CGImageRef' (aka 'struct CGImage *') is neither an Objective-C object nor a block type
Please see the attached screen.  This is in the autogenerated "Project-swift.h" file.
Any ideas how to fix this?  Kinda stuck here.
Thanks!

Filed a bug report for this with Apple based on a discussion thread:
https://forums.developer.apple.com/thread/16289
It seems Xcode 7 beta 6 is treating Array as a type that can be represented faithfully in Objective-C.  No bueno.
Workaround is is follows in RAMFrameItemAnimation:
@nonobjc
var animationImages : Array<CGImage> = Array()

and
@nonobjc
func playFrameAnimation(icon : UIImageView, images : Array<CGImage>)

Hope that helps someone!

Thanks for solution :+1:


Starred repo names not displayed in activity feed on Firefox

Appearance with RGH enabled on Firefox 60.0.1 (64-bit):

Appearance without RGH enabled:

@alichtman does it happen even with #1330? Git hub just made a few changes

I'd bet this is probably due to the Github UI refresh.
I haven't tried #1330, and won't have time to mess with it for a while. I just disabled the extension until the UI changes are figured out.

Yeah this is fixed by #1330


exports is not definied using @storybook/testing-library

Hi,
I have a storybook with some components that make use of Stortybook's play function and they stopped working after I set it up the storybook-addon-swc in the project.
When I open the storybook in the browser, the following error message is being displayed

When I disable the enableSwcLoader setting, the Storybook works again.
Why does it happen? is an expected behavior?
Is it possible to do something to keep using enableSwcMinify enabled? The storybook build happens faster when we use it

Here is my configuration:
const path = require('path');
const { StorybookFrontLoaderPlugin } = require('./storybookFrontLoaderPlugin');

module.exports = {
  stories: ['../**/*.stories.mdx', '../**/*.stories.@(js|jsx|ts|tsx)'],
  addons: [
    '@storybook/addon-links',
    '@storybook/addon-essentials',
    '@storybook/addon-a11y',
    '@storybook/addon-interactions',
    'storybook-addon-next-router',

    // this will give error
    'storybook-addon-swc',

    // this will work
    // {
    //   name: 'storybook-addon-swc',
    //   options: {
    //     enableSwcLoader: false,
    //   },
    // },
  ],
  framework: '@storybook/react',
  core: {
    builder: 'webpack5',
  },
  staticDirs: ['../public'],
};

Here is a example story:
// MyComponent.stories.tsx
import { ComponentStory } from '@storybook/react';
import { userEvent, within } from '@storybook/testing-library';

export default {
  title: 'MyComponent',
};

const Component = () => {
  return <input type="text" placeholder="Search..." />;
};

const Template: ComponentStory<typeof Component> = () => {
  return <Component />;
};

export const Main = Template.bind({});

Main.play = async ({ canvasElement }) => {
  const canvas = within(canvasElement);

  const input = canvas.getByPlaceholderText('Search...');

  await userEvent.type(input, 'Foo bar', {
    delay: 100,
  });
};

@drianoaz
I was able to build successfully by setting the isModule property to unknown.
Please check v1.1.6 for the fix.

@Karibash the fix you released solved the problem. Because of this I'll close this issue, ok?
Thanks so much for the help 🙏


[FIX] Close STD fds for all processes

As best practice, we should close STD fds for all processes. but I don't think it's a fd leak issue.
Resolves issue #143

@LeaYeh We have to decide if we prefer the easter egg (~) to print out instantaneous with printf() or slow with ft_printf().
The welcome message for sure with printf().


wrong status of envoy.resource_monitors.downstream_connections

does blow lines need be updated after https://github.com/envoyproxy/envoy/pull/28202/files
https://github.com/envoyproxy/envoy/blob/0682a04fa3cd255fa7d070970b5f09ead324228c/source/extensions/extensions_metadata.yaml#L1013-L1019
cc @nezdolik

cc @nezdolik as PR author @KBaichoo @RyanTheOptimist as reviewers

The status needs to be updated to alpha (as extension has not gotten much production battle testing) and security_posture is probably robust_to_untrusted_downstream_and_upstream. I cannot think of any possible attack for this extension (it just atomically increments a value and compares it against configured max), but at the same time this extension is missing fuzz tests. wdyt about security posture @KBaichoo @RyanTheOptimist.

should envoy encourage the usage of a filter still in alpha?
xref: https://github.com/istio/istio/pull/47509

should envoy encourage the usage of a filter still in alpha?
xref: istio/istio#47509

this is the real one: https://github.com/istio/istio/pull/47474

@zirain @Pawan-Bishnoi I would recommend ignoring deprecation message until next Envoy minor release. For now this extension is actually in alpha state (please see this patch) and it has been deployed into prod environment with large scale. It has not ran in prod long enough to be sure it is stable. In next minor release we will either promote the extension to stable state or fix the deprecation warning.

The status needs to be updated to alpha

+1

security_posture is probably robust_to_untrusted_downstream_and_upstream
I'm not sure what the right call here is -- I could see either data_plane_agnostic not being quite the right fit since it's on the dataplane path but doesn't really parse any of the dataplane bytes. But I also don't see it being easily exploitable besides a DoS attack capping out max number of connection leading to low availability for legitimate clients.  cc @envoyproxy/envoy-maintainers  for thoughts.

@zirain @Pawan-Bishnoi I would recommend ignoring deprecation message until next Envoy minor release. For now this extension is actually in alpha state (please see this patch) and it has been deployed into prod environment with large scale. It has not ran in prod long enough to be sure it is stable. In next minor release we will either promote the extension to stable state or fix the deprecation warning.

this's the odd thing, you should add deprecation warning when it's stable.

right, this was a human mistake, normally users are advised to move to stable only extensions. Thanks for catching this @zirain

will you revert the warning message part?

yes, the deprecation message will be patched in minor release

/assign

@KBaichoo we can close this one as monitor status has been updated to alpha and deprecation message has been removed in https://github.com/envoyproxy/envoy/pull/30620, https://github.com/envoyproxy/envoy/pull/30735.

fixed by https://github.com/envoyproxy/envoy/pull/30735


TypeError related to <class 'oxrdflib.OxigraphStore'>.bind

Hi
When I'm trying to run the code mentioned in issue 220 in the Oxigraph repository I run into the error pasted below. The code runs, however, and the output seems to be as expected so I don't know if this is really an error or more of a warning?
Could this be related to the latest release of rdflib?
Thanks in advance!
TypeError
caught a TypeError, retrying call to <class 'oxrdflib.OxigraphStore'>.bind without override, see https://github.com/RDFLib/rdflib/issues/1880 for more info
Traceback (most recent call last):
  File "/Users/milan/.pyenv/versions/prefect/lib/python3.9/site-packages/rdflib/namespace/__init__.py", line 627, in _store_bind
    return self.store.bind(prefix, namespace, override=override)
TypeError: bind() got an unexpected keyword argument 'override'
caught a TypeError, retrying call to <class 'oxrdflib.OxigraphStore'>.bind without override, see https://github.com/RDFLib/rdflib/issues/1880 for more info
Traceback (most recent call last):
  File "/Users/milan/.pyenv/versions/prefect/lib/python3.9/site-packages/rdflib/namespace/__init__.py", line 627, in _store_bind
    return self.store.bind(prefix, namespace, override=override)
TypeError: bind() got an unexpected keyword argument 'override'
caught a TypeError, retrying call to <class 'oxrdflib.OxigraphStore'>.bind without override, see https://github.com/RDFLib/rdflib/issues/1880 for more info
Traceback (most recent call last):
  File "/Users/milan/.pyenv/versions/prefect/lib/python3.9/site-packages/rdflib/namespace/__init__.py", line 627, in _store_bind
    return self.store.bind(prefix, namespace, override=override)
TypeError: bind() got an unexpected keyword argument 'override'
caught a TypeError, retrying call to <class 'oxrdflib.OxigraphStore'>.bind without override, see https://github.com/RDFLib/rdflib/issues/1880 for more info
Traceback (most recent call last):
  File "/Users/milan/.pyenv/versions/prefect/lib/python3.9/site-packages/rdflib/namespace/__init__.py", line 627, in _store_bind
    return self.store.bind(prefix, namespace, override=override)
TypeError: bind() got an unexpected keyword argument 'override'
caught a TypeError, retrying call to <class 'oxrdflib.OxigraphStore'>.bind without override, see https://github.com/RDFLib/rdflib/issues/1880 for more info
Traceback (most recent call last):
  File "/Users/milan/.pyenv/versions/prefect/lib/python3.9/site-packages/rdflib/namespace/__init__.py", line 627, in _store_bind
    return self.store.bind(prefix, namespace, override=override)
TypeError: bind() got an unexpected keyword argument 'override'

Thank you! indeed rdflib 6.2 released a few days ago added an optional parameter to the bind abstract method, breaking backward compatbility.

@milvala I have just released v0.3.2 to Pypi that should fix this error.


Plugin not working : many parse error

Hi,
Great projet! I thinks it's not easy to implement apex language.
i get a lot of parse error :(
Is this a working prototype? if yes please provide a simple apex class to parse as an example.
Thanks

Hi,
This is an example apex class.
Good Luck !
Thanks
2016-04-17 15:07 GMT+02:00 Reda Benhemmouche<EMAIL_ADDRESS>
Hi,
Great idea.
i get a lot of parse error :(
I thinks it's not easy to implement apex language.
Is this a working prototype? if yes please provide a simple apex class to
parse as an example.
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/fundacionjala/enforce-sonarqube-plugin/issues/19

--
Mounir Ben Zaied
Rennes, France
Mobile : +336 51 22 16 74
Email<EMAIL_ADDRESS>

thanks for your answer, btw  there is no attachment in your answer

Hi,
I attached 5 files, .
and now? did you receive them ?
Sorry, maybe there is a network problem !
2016-04-18 12:04 GMT+02:00 Reda Benhemmouche<EMAIL_ADDRESS>
thanks for your answer, btw there is no attachment in your answer
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/fundacionjala/enforce-sonarqube-plugin/issues/19#issuecomment-211307938

--
Mounir Ben Zaied
Rennes, France
Mobile : +336 51 22 16 74
Email<EMAIL_ADDRESS>

If you answer to this comment from your email client the attachments will be ignored by github.
You can attach the file directly in the issue 19
Thanks mounir

This is an example of apex class,
Thanks
apex example.zip

thanks for the files, those could serve for testing once grammar is completed  :)

Thank you for the effort to give us, an open source plugin to test apex
code :)
2016-04-18 16:07 GMT+02:00 eruizg<EMAIL_ADDRESS>
thanks for the files, those could serve for testing once grammar is
completed :)
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/fundacionjala/enforce-sonarqube-plugin/issues/19#issuecomment-211396354

--
Mounir Ben Zaied
Rennes, France
Mobile : +336 51 22 16 74
Email<EMAIL_ADDRESS>

thanks for the examples.

Please notify me, when the apex plugin will be ready to test my project
classes !
I'm really excited !
2016-04-20 11:27 GMT+02:00 Reda Benhemmouche<EMAIL_ADDRESS>
thanks for the examples.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/fundacionjala/enforce-sonarqube-plugin/issues/19#issuecomment-212347864

--
Mounir Ben Zaied
Rennes, France
Mobile : +336 51 22 16 74
Email<EMAIL_ADDRESS>

I will, 'testing' will be useful and, results very welcome :)

Hi
It seems the issue still persists in sonar scanner 6.7.4
I am getting lot of parse errors when executing it for an apex class repository. Please confirm if the issue still exists or is there any configuration that I can do and solve the issue.
Looking for a quick response!
Thanks

I just saw that issue. Sonar version is 6.5


Handle malformed depfiles in Fingerprinter

Fingerprinter.doesFingerprintMatch() now returns false rather than
throwing if a depfile is malformed.

Fixes #17831.


Incorrect rtmdet parameters counts?

My question refers to the rtmdet model in both mmyolo and mmdetection.
I used mmyolo to train rtmdet but the mmdetection model implementation is identical as far as I know (the training, bn part differs). For instance, for the tiny version:
mmyolo

https://github.com/open-mmlab/mmyolo/blob/dev/configs/rtmdet/rtmdet_tiny_syncbn_fast_8xb32-300e_coco.py

base model: https://github.com/open-mmlab/mmyolo/blob/dev/configs/rtmdet/rtmdet_l_syncbn_fast_8xb32-300e_coco.py

mmdetection

https://github.com/open-mmlab/mmdetection/blob/main/configs/rtmdet/rtmdet_tiny_8xb32-300e_coco.py

base model: https://github.com/open-mmlab/mmdetection/blob/main/configs/rtmdet/rtmdet_l_8xb32-300e_coco.py

After successfully converting the following RTMDet-s model to ONNX:

rtmdet_s_syncbn_fast_8xb32-300e_coco.py
rtmdet_s_syncbn_fast_8xb32-300e_coco_20221230_182329-0a8c901a.pth

I get:

onnx_opcounter rtmdet_s.onnx

Number of parameters in the model: ~11.2M
Which is quite larger than the 8.89M value reported in the documentation and the publication.

The exported ONNX model looks okay in Netron and seems to work as expected.
The number of parameters for other MMDet models I converted the same way (yolov5s, yolov8s, yolov8s-pose, etc...) do not have this issue and the parameter counts I obtain are the same as in the documentation (yolov5s, yolov8s, yolov8s-pose).
Why is there a discrepancy for the rtmdet models only? Is there an issue?
I would like someone to prove me wrong on the model size (params count), otherwise rtmdet is not as / more efficient as / than Yolov5 (and above) as claimed.

Based on:
https://github.com/open-mmlab/mmyolo/blob/main/docs/en/recommended_topics/complexity_analysis.md
python tools/analysis_tools/get_flops.py  configs/rtmdet/rtmdet_s_syncbn_fast_8xb32-300e_coco.py
returns:
==============================
Input shape: torch.Size([640, 640])
Model Flops: 14.835G
Model Parameters: 8.887M
==============================
!!!Please be cautious if you use the results in papers. You may need to check if all ops are supported and verify that the flops computation is correct.

which is consistent with the documentation
So
get_flops.py  =/= PyTorch   and
get_flops.py  =/= onnx_opcounter   but
PyTorch == onnx_opcounter
Something does not look right...
Considering the warning message above, could there be an issue with the advertised values?

I would like someone to prove me wrong on the model size (params count), otherwise rtmdet is not as / more efficient as / than Yolov5 (and above) as claimed.

RTMDet uses SepBNHead which shares conv weights between different feature scales. For more details please refer to the 4.3 section of the tech report and the code.
The reason why the onnx model is larger than the PyTorch model is that when exporting to onnx, the program will fuse the Conv and BN layers. As a result, the same convolution is combined with different BN layers to generate different parameters. This is a limitation of the deployment code.

@RangiLyu Thanks a lot for the explanation, I get it now! So beside the larger size for exported ONNX, the inference speed should not be affected since the number of operations for remains the same? Is that right, just to make sure I'm not missing something again.Thanks.


SqlServerDsc: Fix inconsistent parameter names in all resources

Pull Request (PR) description
This pull request will fix all inconsistent parameter names so that InstanceName is the parameter used to set the name of the instance to configure, and ServerName is used to specify the NetBios or FQDN name where the instance can be found.
This Pull Request (PR) fixes the following issues:
Fixes #308
Task list:

[x] Change details added to Unreleased section of CHANGELOG.md?
[x] Added/updated documentation, comment-based help and descriptions in .schema.mof files where appropriate?
[x] Examples appropriately updated?
[x] New/changed code adheres to Style Guidelines?
[x] Unit and (optional) Integration tests created/updated where possible?

This change is

@randomnote1 @nabrond If you have time, then please help me review this one. 😄 I really need a second pair of eyes on this one. It's hard to be objective of ones own code. 😄
@PlagueHO If you get bored on your mini-holiday, then you can help out reviewing this one. Haha 😉

Codecov Report

Merging #917 into dev will not change coverage.
The diff coverage is 99%.

@@         Coverage Diff         @@
##            dev   #917   +/-   ##
===================================
  Coverage    96%    96%
===================================
  Files        32     32
  Lines      3513   3513
===================================
  Hits       3393   3393
  Misses      120    120

Reviewed 15 of 129 files at r1.
Review status: 15 of 129 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

@johlju, I noticed that no helper functions were included in this PR. Functions like Connect-SQLServer are still utilizing the "old" parameters. Do you think it is too ambitious to bring them into scope of this pull?

Comments from Reviewable

Reviewed 7 of 129 files at r1.
Review status: 22 of 129 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 6 of 129 files at r1.
Review status: 28 of 129 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 129 files at r1.
Review status: 29 of 129 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

@nabrond I thought about it, but I didn't want to do that in this PR since it can be done later without a breaking change (was a lot of work getting all the tests working any way 😄 ). But I will make sure to add an issue for that so it doesn't get forgotten.

Reviewed 2 of 129 files at r1.
Review status: 31 of 129 files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Reviewed 15 of 129 files at r1.
Review status: 44 of 129 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

DSCResources/MSFT_SqlDatabaseRole/MSFT_SqlDatabaseRole.psm1, line 129 at r1 (raw file):

        Name            = $Name
        ServerName      = $ServerName
        InstanceName = $InstanceName

Fix formatting

DSCResources/MSFT_SqlDatabaseRole/MSFT_SqlDatabaseRole.psm1, line 342 at r1 (raw file):

    $getTargetResourceParameters = @{
        InstanceName = $PSBoundParameters.InstanceName

Fix formatting

Examples/Resources/SqlDatabasePermission/1-GrantDatabasePermissions.ps1, line 23 at r1 (raw file):

            Name                 = 'CONTOSO\SQLAdmin'
            LoginType            = 'WindowsUser'
            ServerName           = 'sqltest.company.local'

Just curious...Why did you update this to an FQDN?

Comments from Reviewable

Reviewed 11 of 129 files at r1.
Review status: 55 of 129 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

Comments from Reviewable

Review status: 55 of 129 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

Examples/Resources/SqlDatabasePermission/1-GrantDatabasePermissions.ps1, line 23 at r1 (raw file):
Previously, randomnote1 (Dan Reist) wrote…
Just curious...Why did you update this to an FQDN?

It said 'SQLServer' before so it was messing with my search and replace, and when changing the name I just wrote FQDN by habit. :smile:  I can change it back to NetBIOS if you like.

Comments from Reviewable

Reviewed 16 of 129 files at r1.
Review status: 71 of 129 files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

Examples/Resources/SqlDatabasePermission/1-GrantDatabasePermissions.ps1, line 23 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
It said 'SQLServer' before so it was messing with my search and replace, and when changing the name I just wrote FQDN by habit. :smile:  I can change it back to NetBIOS if you like.

Ahh, that makes sense. No big deal. Like I said, I was just curious!

Tests/Unit/MSFT_SqlServerLogin.Tests.ps1, line 58 at r1 (raw file):

        $instanceParameters = @{
            InstanceName = 'MSSQLSERVER'
            ServerName = 'Server1'

Hash table should be formatted with the appropriate spacing.

Comments from Reviewable

Reviewed 26 of 129 files at r1.
Review status: 97 of 129 files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

Comments from Reviewable

@johlju, There are only a few formatting issues. Other than that, I think this looks good.

Reviewed 30 of 129 files at r1.
Review status: 127 of 129 files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

Comments from Reviewable

Review status: 127 of 129 files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

Examples/Resources/SqlDatabasePermission/1-GrantDatabasePermissions.ps1, line 23 at r1 (raw file):
Previously, randomnote1 (Dan Reist) wrote…
Ahh, that makes sense. No big deal. Like I said, I was just curious!

Comments from Reviewable

Many thanks for reviewing! This was a big one! :smile: All comments should be resolved. Please sign off on them.
Also opened more issues regarding rename, please comment on those to see if we should do them (or not) before release.

Review status: 124 of 129 files reviewed at latest revision, 4 unresolved discussions.

DSCResources/MSFT_SqlDatabaseRole/MSFT_SqlDatabaseRole.psm1, line 129 at r1 (raw file):
Previously, randomnote1 (Dan Reist) wrote…
Fix formatting

Done.

DSCResources/MSFT_SqlDatabaseRole/MSFT_SqlDatabaseRole.psm1, line 342 at r1 (raw file):
Previously, randomnote1 (Dan Reist) wrote…
Fix formatting

Done.

Examples/Resources/SqlDatabasePermission/1-GrantDatabasePermissions.ps1, line 23 at r1 (raw file):
Previously, randomnote1 (Dan Reist) wrote…
:lgtm:

Done.

Tests/Unit/MSFT_SqlServerLogin.Tests.ps1, line 58 at r1 (raw file):
Previously, randomnote1 (Dan Reist) wrote…
Hash table should be formatted with the appropriate spacing.

Done. For some reason auto-formatting did not touch this one. I moved it manually.

Comments from Reviewable

Glad to help! Just one more thing I missed earlier and it should be good to go.

Reviewed 2 of 3 files at r2, 2 of 2 files at r3.
Review status: 128 of 129 files reviewed at latest revision, 1 unresolved discussion.

CHANGELOG.md, line 8 at r3 (raw file):

  ([issue #916](https://github.com/PowerShell/SqlServerDsc/issues/916)).
- BREAKING CHANGE: Significant rename to reduce length of resource names
  - See [issue #851](https://github.com/PowerShell/xSQLServer/issues/851) for a

Should be https://github.com/PowerShell/SqlServerDsc/issues here and throughout the rest of the Unreleased section.
Or should it be throughout the whole file?

Comments from Reviewable

Good catch - totally missed that! Can you please sign off on the last changes. :smile:

Review status: 128 of 129 files reviewed at latest revision, 1 unresolved discussion.

CHANGELOG.md, line 8 at r3 (raw file):
Previously, randomnote1 (Dan Reist) wrote…
Should be https://github.com/PowerShell/SqlServerDsc/issues here and throughout the rest of the Unreleased section.
Or should it be throughout the whole file?

Done.

Comments from Reviewable

Review status: 128 of 129 files reviewed at latest revision, 1 unresolved discussion.

CHANGELOG.md, line 8 at r3 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
Done.

Still says xSQLServer on this line

Comments from Reviewable

Review status: 128 of 129 files reviewed at latest revision, 1 unresolved discussion.

CHANGELOG.md, line 8 at r3 (raw file):
Previously, randomnote1 (Dan Reist) wrote…
Still says xSQLServer on this line

Done. Really this time. :smile: I looked over this twice to make sure, and still managed to miss one. :s

Comments from Reviewable

Looks good!

Reviewed 1 of 1 files at r4.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

@randomnote1 Awesome thank you! Waiting for the tests to pass and I will merge this one.


explain_prediction is confusing for binary classifiers

Currently we're always showing contributions for positive class, not for predicted class:

Maybe it makes sense to show y=0 for the above example, with positive BIAS and score.

It's even more confusing without proba... This makes sense, I agree! 👍


Allow Question Help Text to Not Require $this

When creating a question that is tied to an enumerator you are currently required to include the text $this in both the question text and the help text.
Seattle is requesting that the help text use $this if provided, but only require it for the question text.

When looking at this for Matt I had this working by removing these lines https://github.com/civiform/civiform/blob/04e199cf52dda29d79fdb1b1d2714109d183927f/server/app/services/question/types/QuestionDefinition.java#L428-L430
There likely isn't much left to do other than update tests.

This makes sense to me! We'll take a quick look to make sure there aren't any less obvious constraints and follow up here.


Read-only members of a workspace cannot connect to datasets and How RLS can apply ?

I can see two contradicting statement , Please clarify

Read-only members of a workspace cannot connect to datasets  - ok
You have mentioned RLS will be applied - as per https://docs.microsoft.com/en-us/power-bi/service-admin-rls   ->  members have edit permissions, the RLS roles will not be applied to them. Users will be able to see all of the data.

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

ID: a1cce347-2064-d2b3-d7dd-008ecdb36013
Version Independent ID: 6abb84b5-1657-c8b1-62ef-641883c0e4b9
Content: Connect to datasets in the Power BI service from Power BI Desktop - Power BI
Content Source: powerbi-docs/desktop-report-lifecycle-datasets.md
Service: powerbi
GitHub Login: @davidiseminger
Microsoft Alias: davidi

@BigDataenthu Thank you for your feedback! We will investigate and get back to you with the relevant info.

Sorry for any confusion, we believe those comments are correct.
Your best venue for getting further clarification or feedback on your question is from the community (https://community.powerbi.com) or from support at https://support.powerbi.com. You can also provide feedback using the Give Product Feedback button at the bottom of the article page.


Fix handling of OrderedDict with optree and related documentation.

The tree API had specific but contradicting documentation calling out the handling of OrderedDicts. However, the behavior of the optree implementation did not honor this documentation (using the key order, not the sequence order) for flatten, although it did for pack_sequence_as. The result was that not only did flatten not behave the same with optree and dm-tree, but also pack_sequence_as(flatten(...)) was not idempotent. The optree implementation did have all the machinery needed to handle OrderedDicts per spec, which was used for pack_sequence_as, but not flatten. This also fixes the discrepancy in the behavior for namedtuples.

Fixed contradicting documentation in flatten and pack_sequence_as related to the handling of OrderedDicts.
Fixed references to unflatten_as, which doesn't exist.
Removed most if optree tests in tree_test.py, which should not exist for consistency between optree and dm-tree.
Fixed unit tests which were incorrectly flattening the result of flatten_with_path.
Fixed unintented use of tree instead of keras.tree in unit test.
Ran unit tests for all backends with dm-tree uninstalled.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 59.98%. Comparing base (b0b9d04) to head (def69ec).

:exclamation:  There is a different number of reports uploaded between BASE (b0b9d04) and HEAD (def69ec). Click for more details.
HEAD has 6 uploads less than BASE

Flag
BASE (b0b9d04)
HEAD (def69ec)

keras
4
1

keras-torch
1
0

keras-tensorflow
1
0

keras-jax
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #20481       +/-   ##
===========================================
- Coverage   82.07%   59.98%   -22.10%
===========================================
  Files         515      515
  Lines       47504    47512        +8
  Branches     7454     7457        +3
===========================================
- Hits        38991    28498    -10493
- Misses       6703    17260    +10557
+ Partials     1810     1754       -56

Flag
Coverage Δ

keras
59.98% <100.00%> (-21.96%)
:arrow_down:

keras-jax
?

keras-numpy
59.98% <100.00%> (+<0.01%)
:arrow_up:

keras-tensorflow
?

keras-torch
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Wouldn't it be better to wrap OrderedDict rather than re-implement flatten, which is written in C++ in optree?
e.g.:
from collections import OrderedDict
import optree
from keras import tree

class WrappedOrderedDict(OrderedDict):
  pass

def flatten(d):
  values = []
  keys = []
  for key in sorted(d.keys()):
    values.append(d[key])
    keys.append(key)
  return values, list(d.keys()), keys

def unflatten(metadata, children):
  index = {key: i for i, key in enumerate(sorted(metadata))}
  return OrderedDict({key: children[index[key]] for key in metadata})

optree.register_pytree_node(
    WrappedOrderedDict,
    flatten,
    unflatten,
    namespace="keras",
)

def ordereddict_pytree_test():
  # Create an OrderedDict with deliberately unsorted keys
  ordered_d = OrderedDict([('c', 3), ('a', 1), ('b', 2)])

  def wrap(s):
    if isinstance(s, OrderedDict):
      return WrappedOrderedDict(s)
    return None

  def unwrap(s):
    if isinstance(s, WrappedOrderedDict):
      return OrderedDict(s)
    return None

  d = tree.traverse(wrap, ordered_d, top_down=False)
  flat_d = tree.flatten(d)
  flat_d_paths = tree.flatten_with_path(d)
  assert flat_d == [1, 2, 3]
  assert [p[0] for p, v in flat_d_paths] == ["a", "b", "c"]

  tree_struct = tree.traverse(wrap, ordered_d, top_down=False)
  wrapped_d = tree.pack_sequence_as(tree_struct, flat_d)
  orig_d = tree.traverse(unwrap, wrapped_d, top_down=False)
  assert isinstance(orig_d, OrderedDict)
  assert list(orig_d.keys()) == list(ordered_d.keys())
  assert list(orig_d.values()) == list(ordered_d.values())

ordereddict_pytree_test()

Wouldn't it be better to wrap OrderedDict rather than re-implement flatten, which is written in C++ in optree?

Hi Nicolas,
Thank you for the suggestion. I actually completely scratched this PR and decided to use a different approach. The optree behavior will be the reference behavior. The goal is indeed to maximize the use of the C++ implementation of optree since it is the default and dm-tree is only a fallback.


LSP starts language-server several times after project change

As the title says, pyls is started several times when opening a new project.
Steps to reproduce:

Open a project in ST.
Install ProjectManager package
Open a python file to start one pyls instance.
Call "Project Manager: Open Project" from command pallet and select another python project
Have a look to the console

Not being a Project Manager user, does the "Open Project" command open a new window or does it replace the project of the current window?

It replaces the open project in the existing window, which seems to be the reason. ST's Quick Switch Project function works properly. I did not yet find a point to start searching for the trigger of this issue.

In these lines
https://github.com/tomv564/LSP/blob/78647441c861eb59d1d25bd6284a2814903a7783/plugin/core/main.py#L199-L207
when is a new client inserted into clients?
For me LSP starts a new language server process every time I unfocus and focus the window (on the current master commit that's linked).

Ah, I see, add_window_client(). And mine is not getting called because it's in handle_initialize_result() and there's an initialisation problem with the server I'm trying to get working.

Good find, but the failure to initialise should have been visible from the status bar. If you can share where the initialisation failed we can at least fix that!


While retraining a model I get worse values for MSE from the last  epoch of last trainment to the first of the next

Im using a Sequential model to make a model based on regresion.
This is the code im using for training:
def massTrain(self):

        csvs = listdir('Data')

        for i ,csv in enumerate(csvs):

            print(f'\nTraining with {csv}\n')

            if i < len(csvs) - 1:
                self.setData(csv, 1)
            else:
                self.setData(csv, 0.9)

            if (test_data):
                self.predictions = self.test(test_data)

                y_test = self.dataset[self.training_data_len:, :]

                self.mse = mean_squared_error(y_test, self.predictions)
                self.rmse = sqrt(self.mse)

                print(f"\nRMSE was: {self.rmse}\n")

def train(self, train_data):

        # Split data into x_train and y_train data sets
        x_train = []
        y_train = []

        for i in range(self.input_shape, len(train_data)):
            x_train.append(train_data[i - self.input_shape:i, 0])
            y_train.append(train_data[i, 0])

        # Convert x_train and y_train to NP arrays
        x_train,y_train = np.array(x_train), np.array(y_train)

        # Reshape the data
        x_train = np.reshape(x_train, (x_train.shape[0], x_train.shape[1], 1))

        # Train the model
        earlystopping = callbacks.EarlyStopping(monitor="loss",mode="min",patience=6,restore_best_weights=True)

        self.model.fit(x_train , y_train, batch_size=16, epochs=50, callbacks=[earlystopping])

The rest of the code is irrelevant because its able to train and save and plot graphs after training.
Im using 10 csv files that holds data, so I iterate over them using listdir() to get all the files, I then train the model using all those files, for the last train dataset I just use 90% of the data for then testing the model with the other 10% and ploting a graph.
What im getting is that for example, when training the modle with the first dataset, on the last epoch of the trainment I get a MSE of 7e-4, and then in the, when using the next dataset I get on the first epoch 0.0012, which is a lot more actually, 5e-4 more, that is a 58% less acuracy.
Is there something im doing wrong when retraining the model, because the only thing I think it could be is that the weights are not being stored after fitting the model and its starting from scratch every time, and therefore all the fitting is useless.

I updated the code because it wasnt right, I took it from my test file on accident and it was not the one Im running, mainly beacuse it wouldnt work.
Now, to add some usefull data, heres the compilation of the model:
# Compile the model
model.compile(optimizer='adam', loss='mean_squared_error', metrics=[RootMeanSquaredError()])

And here is the REAL data from the training Im doing right now and as im using a callback Earlystopper that retakes the best value Im going to include 3 rows for first dataset training.
First dataset training:

First epoch result: 448/448 [==============================] - 36s 69ms/step - loss: 0.0012 - root_mean_squared_error: 0.0339
Last epoch result: 448/448 [==============================] - 31s 69ms/step - loss: 2.3723e-04 - root_mean_squared_error: 0.0154
Best epoch result: 448/448 [==============================] - 30s 67ms/step - loss: 2.3116e-04 - root_mean_squared_error: 0.0152

Next dataset training:

First epoch result: 448/448 [==============================] - 31s 69ms/step - loss: 5.3316e-04 - root_mean_squared_error: 0.0231

@Dtar380 I have a few questions, it would help me understand your issue better

how and where is the train function being called?
This would make sure the model is not getting reinitialized in a loop somewhere
Where is model.compile() being done? you might be unintentionally resetting the weights if you are compiling somewhere in a loop
Is your data normalized? I am wondering if the data looks different in the first CSV file and the last


Why is ignite new MyProject not using latest react-native?

I found that ignite created the project with "react-native": "0.42.0", why is that? Why not creating the project with 0.44?

Because ignite is a collection of components and those components all need to play nicely together. And sometimes they don't all cooperate when React Native's version increases.
Luckily, it's your call though.  ignite new HoldMyBeer --react-native-version 0.45.0-rc.2

Great, that option looks promising.
Just one more question, do I have all corresponding dependencies being installed properly with this option? Will I have RN 0.45 + corresponding React version installed?
P.S. Asides from this answer,  I've just tried manually execute npm i react-native@latest --save and npm i<EMAIL_ADDRESS>--save and those worked well; just want to make some notes.

Yup!  That option you set feeds directly into react-native init --version xxx.  So you're setting up 0.45.0-rc.2 and it's dependencies (react@16.0.0-alpha.12).
I added that pass thru for the same reasons you're asking about.  Sometimes you just wanna forge ahead, dependencies-be-damned.  =)
Glad it's working for ya.

Greeeeeat! Thanks, and dependencies-be-damned +1!

Latest version (almost ready to be released) will use 0.45.1.


flist mounter for the filesystem components

Quick demo: https://asciinema.org/a/IstNZ1xSYNvD3AgQZZ31kSq2b

First version released: https://github.com/threefoldtech/quantum-storage/releases/tag/v0.0.1


fix: typo carousel indicators component

Closes #1102
Description
This is a modified comment within the carousel indicator component.
Is this a breaking change (Yes/No):
No
Additional Information

Thanks!


Added code to enable Sorting feature for blog posts

Hi Shazwazza,
I have added a code for sorting the blog post based on certain parameters in UmbracoHelperExtensions.

Closing this PR due to inactivity.


client.addEventSync()

Is it possible to call addEvent synchronously?
For example:
window.onbeforeunload = function() {
  client.addEventSync('my-collection');
}

this is now possible in v3.2 by passing a fourth 'null' argument to a#addEven. just be sure to check the changelog for updates to the single callback pattern. thanks for suggesting this feature!

that's #addEvent ^ mobile typo :)

It would be nice if this worked for addEvents() too


Project name conflict

Just an FYI, but the name neon has been around for a long while for this project: http://www.webdav.org/neon/ .

@davidblewett Are you suggesting neon (this project) to be renamed to something else? Rust (the language) share the same name as the video game: https://en.wikipedia.org/wiki/Rust_(video_game)
Folks are smart enough to tell the difference.

Thanks for the heads-up. I don't want to step on anyone's toes, but I think there's room for software projects in significantly difference spaces to have the same name. Note that there's already another neon project in npm as well, so this is certainly not the first. I appreciate your bringing this to my attention, and I'll close for now.


Make effect peerDependency

Effect is currently loaded via utils as a dependency while it should be loaded as peerDependency. Linking libs as deps is generally unadvisable for any dependency but poses a critical risk for effect (and its ecosystem packages) in particular given that it doesn't work if multiple copies are loaded.
https://github.com/contentlayerdev/contentlayer/blob/main/packages/%40contentlayer/utils/package.json#L43
Note that multiple copies will be loaded any time a user of the lib installs a different version of effect (even a patch) in a child project, that isn't the case for peerDependencies with a set range of acceptable versions

Addressed by #7193a37


arc: fix the coverity issuse in thread.c

fix coverity CID: 187905
issue fixes #9765
Signed-off-by: Wayne Ren<EMAIL_ADDRESS>

Codecov Report

Merging #11130 into master will decrease coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11130      +/-   ##
==========================================
- Coverage    53.1%   52.96%   -0.14%
==========================================
  Files         218      218
  Lines       26853    26840      -13
  Branches     5950     5949       -1
==========================================
- Hits        14259    14217      -42
- Misses      10162    10187      +25
- Partials     2432     2436       +4

Impacted Files
Coverage Δ

subsys/logging/log_output.c
63.9% <0%> (-8.79%)
:arrow_down:

subsys/logging/log_core.c
68.05% <0%> (-3.63%)
:arrow_down:

misc/printk.c
85.45% <0%> (-3.1%)
:arrow_down:

include/logging/log_msg.h
89.09% <0%> (-1.82%)
:arrow_down:

include/logging/log_core.h
100% <0%> (ø)
: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 de65924...a0df56e. Read the comment docs.


Add an example of how to use complex configuration in performance reporting

Add an example of how to use complex configuration in performance reporting.
Right now it doesn't contain such

updated


DRAFT: Add min dependencies of min dependencies tests

testing min_dependencies of min dependencies

Closing this for now, will circle back in the future.


Docs updates relating to testnet

Updates the clarity language reference, which is auto-generated from core
update Jekyll version. This fixed an issue where the docs weren't auto-reloading after I would update a page
Added some docs for @blockstack/connect

@agraebe @markmhx I've started a first draft for running a Neon miner, given @lgalabru 's guidance this morning.
It should be readable at https://deploy-preview-540--docsproduction.netlify.com/core/smart/neon-node.html (if the deploy works)

We need to update the Clarity docs to refer to the staged authenticator instead of prod until we have transaction signing ready for prod.

Did we want to push the node tutorial live given it has TODO sections still marked for completion? https://docs.blockstack.org/core/smart/neon-node.html

Separately, as mentioned in my review notes shared with @hstove and @agraebe via Paper, I got blocked trying the Clarity "Hello World" tutorial when npm init clarity-starter because the template wasn't available.

Yes, intentional on adding the neon-node tutorial - it's not linked anywhere in the nav, so not discoverable ATM.


Roles

I don't know if this is not within the scope of LaraParse but I am setting a three level website (users, managers and administrators) and Roles play a huge part in this.
I have modified the code on the Registrar to look like this:
/**
 * Create a new user instance after a valid registration.
 *
 * Assign Administrator Role if wanted/needed.
 *
 * @param  array $data
 *
 * @param  bool $isAdmin
 *
 * @return User
 */
public function create(array $data, $isAdmin = false)
{
    $userSubclass   = ParseObject::getRegisteredSubclass('_User');
    $user           = new $userSubclass;
    $user->username = $data['email'];
    $user->email    = $data['email'];
    $user->password = $data['password'];
    if(isset($data['name'])){
        $fullName = explode(" ", $data['name']);
        $user->name = $fullName[0];
        $user->lastname = $fullName[1];
    }
    if(isset($data['id'])){
        $user->facebookId = $data['id'];
        $user->pictureURL = $data['avatar'];
        $user->name = $data['first_name'];
        $user->lastname = $data['last_name'];
    }
    $user->signUp();

    if(!$isAdmin){
        $query = new ParseQuery('_Role');
        $adminRole = new ParseRole();
        $adminRole = $query->equalTo("name", "Administrator")->first(true);
        $adminRole->getUsers()->add($user);
        $adminRole->save(true);
    }

    return $user;
}

I don't know if this is the best implementation, so if anyone has a suggestion (mostly on security), since this is my first time working with the Parse SDK, I would greatly appreciate it.
If not, I hope this can help someone get the Roles working quickly.

This implementation isn't something we'll do exactly, as it's very specific to your use case. But I'm hoping to get to roles at some point.

I would love to help in any way I can when that time comes.
Cheers
On Wed, Jun 10, 2015 at 1:12 AM, Caleb Fidecaro<EMAIL_ADDRESS>wrote:

This implementation isn't something we'll do exactly, as it's very
specific to your use case. But I'm hoping to get to roles at some point.
—
Reply to this email directly or view it on GitHub
https://github.com/HipsterJazzbo/LaraParse/issues/18#issuecomment-110529544
.


Remove Traffic Monitor dependency on CRConfig data

This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components:

Traffic Monitor

Current behavior:
As of https://github.com/apache/trafficcontrol/pull/6443, TM will no longer overwrite its monitoring.json snapshot data with corresponding CRConfig snapshot data if the monitoring.json contains IP addresses for the TMs, meaning it now has parity with the CRConfig data. However, it still needs the CRConfig in order to filter out delivery services from monitoring.json which aren't present in the CRConfig. That was fixed in #6443 in that the monitoring.json no longer contains delivery services from other CDNs to which the TM doesn't belong.
New behavior:
Once ATC 6.1 is released with the changes from #6443, we should be able to remove this fallback behavior from TM (and possibly its reliance on the CRConfig altogether) in the next major/minor release. That is because monitoring.json snapshots as of TO 6.1 will contain all the necessary data and will no longer need to rely on the CRConfig snapshot.

@rawlinp any idea what the impact and effort of this improvement is?


Upgrade spacy to 2.1.0

Not sure what the proper way to upgrade is, since upgrading to 2.1 requires using the spacy-nightly package

Oh, this is going to be annoying - any tests which use the checked in models are going to fail, because the models are backward incompatible for this version. Ugh.

I think given that we don't actually use the full model (you're only using the tokenizer one, right?) we can just delete it and the test which uses it.

yeah, i was just trying to figure out the best way to handle this. I'm going to see if I can just delete them and the tests that require them

There were a bunch of tests that were actually using the whole model, it seemed easier for now to just replace the combined_all_model with the new one, and then figure out what to do with the tests later

sure sounds good - I really want to remove all those models, it's the first thing that i'll do once we have an actual release that we can install in scigraph

yeah, agreed