[DO NOT MERGE] Build system cleanup

I'm trying to clean up some things about the build system, among them the near-duplicate -proto projects (#712), but I don't actually want my changes pulled yet; I'm only creating this pull request in order to [ab]use the CI infrastructure.

Hi @SamB, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@SamB, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

By the way, I've been using this little shell script to compare the -proto projects with the normal versions;
#!/bin/sh
for i in FSharp.Build FSharp.Compiler Fsc; do
    git --no-pager diff --no-index src/fsharp/{$i/$i,$i-proto/$i-proto}.fsproj;
done

(Don't forget chmod +x; I was a little surprised that this was needed on Windows since I thought most files had execute permissions here, but for some reason I had to do that before bash autocompletion worked.)
Also, my laptop power cord is busted, plus I'm going to be visiting with a friend I haven't seen in a while, so I may be out of touch for at least the next couple of days.

Wow!!! thanks for diving into the build, you are surely a brave person.  We need all of the help we can get with making it a bit less opaque.

Oh dear, some sort of phase-crossing seems to have crept in somehow :-(

I'm generally ok with the PR as it is at the time of writing this comment - it achieves good textual alignment between Proto and non-Proto.
However it's probably enough for now?  For the reasons in this comment.

@dsyme: Hmm. That would also save me from having to figure out WTH the Configuration isn't getting set the way I'd expect in the final projects, which I was thinking might require me to add more diagnostics to MSBuild.
But if doing away with the -proto projects isn't an option (and turning them into thin wrappers around the normal projects is also out), then I guess I'd want to generate them as part of the build, so they're forced to be in sync with the main ones.  (And that it might make the logistics easier to not do it using F# code; C# would likely be simplest, or possibly VB?)

then I guess I'd want to generate them as part of the build, so they're forced to be in sync with the main ones

@SamB dont add anoter pre build step pls. ideal workflow is:

clone repo
open solution
run

there are already lots of prebuild step requirements, and build infrastructure is already weak (.bat files, multiple steps)
Maybe add a command ( .fsx? ) to generate it, so we can use it and commit generated/updated -proto proj to repo.
if we need to check sync, we can add a test to check if generated output is the same of actual file in the repo
File list not change alot, no need to recreate the -proto proj before each build

@SamB   Yes, I think the ideal for now is to still have the two project files, just have them much better aligned.

btw @SamB thx for your work, the infrastructure/build system need some love

@enricosada Hmm, yes, a manually-run script with an assert somewhere to verify freshness would certainly work.
And I've looked at trying to reduce the reliance on batch scripting in the build; in fact, I have an MSBuild .proj stashed somewhere that's meant to distill each batch of msbuild invocations in section 3 of DEVGUIDE down to just one invocation, and it seemed to work for me.  It sounds like you might appreciate it if I would polish that off and submit it sooner rather than later?

@SamB yes, that part is really annoying, i usually do appveyor.bat and a custom script but is not a solution for new contributors.
Without changing the build system, helper commands (like your msbuild proj to run bat) may help.
Or another bat file, sigh

@enricosada: Actually, it doesn't run bat, it does recursive MSBuild on all the relevant projects, including FSharp.Core and its tests for all of the different target frameworks that DEVGUIDE lists. One of the nice things about this is that it lets MSBuild summarize all of the errors at the end.

a lot better if summarize all errors :smile: ( + stop at first failing project if possible )

@enricosada: So, kind of like this?

@dsyme So is there anything else that I need to do before this bit is merged?

The requirements for cross platform will require a different approach.
Closing for now.


Include license info in the generated jar file

Licenses included due to discussions about opensourcing.

The pom.xml now list the project license.
The produced jar now includes the licenses and a dependencies-licenses.xml file

Nice addition. Thanks!


Build fails to find DbgHelp.h with Windows SDK 10.0.15xxx (installed with latest VS 2017)

Apparently DbgHelp.h has been removed from the Windows SDK. Could make it build like this, although that may not be the best possible fix:
diff --git a/src/minidump-win32.cc b/src/minidump-win32.cc
index 1efb085..9a7feac 100644
--- a/src/minidump-win32.cc
+++ b/src/minidump-win32.cc
@@ -15,6 +15,9 @@
 #ifdef _MSC_VER

 #include <windows.h>
+
+#ifndef NTDDI_WIN10_RS2
+
 #include <DbgHelp.h>

 #include "util.h"
@@ -83,5 +86,10 @@ void CreateWin32MiniDump(_EXCEPTION_POINTERS* pep) {

   Warning("minidump created: %s", temp_file);
 }
+#else // def NTDDI_WIN10_RS2
+void CreateWin32MiniDump(_EXCEPTION_POINTERS* pep) {
+  // DbgHelp appears to be gone Platform SDK
+}
+#endif

 #endif  // _MSC_VER

Seems the default install is a minimal one now. So there's a lot of stuff missing unless you hit the right checkbox on the Visual Studio 2017 installer ( see e.g. https://developercommunity.visualstudio.com/content/problem/41860/gdi32lib-missing.html ).


Generic rule false negative when secret is only letters

Describe the bug
I have a Jwt__Token with only upper and lowercase letters. It is a secret, but the generic api rule doesn't catch it. It looks like this:
"Jwt__Token" = "SomeTokenXyzabc"

To Reproduce
Steps to reproduce the behavior:

Create a file with the above snippet of code
Run gitleaks to scan the file
Gitleaks reports "no leaks found"

Expected behavior
Gitleaks should detect Jwt__Token as a secret
Screenshots
N/A
Basic Info (please complete the following information):

OS: windows 10
Gitleaks Version: 8.17.0

Additional context
Hi buddy 👋
cc @zricethezav

This one is actually strange because when I paste the generic api key regex into regex101 and paste the above secret in, it tells me there is a match. But when I run gitleaks on a file containing the secret, it doesn't find the secret. 🤔

That string probably isn't passing the Entropy check:
https://github.com/gitleaks/gitleaks/blob/06db3b91d7495a39caf0d922aef5fee0118e7538/config/gitleaks.toml#L509

@rgmz I initially had the same thought, but apparently it has shannon entropy of 3.64
https://planetcalc.com/2476/

(Also the real secret in the wild, which I didn't post above has even higher entropy)

Another weird thing: If I add a number in there anywhere, then gitleaks detects it. That is, this gets correctly flagged as a secret:
"Jwt__Token" = "SomeTokenXyzab1"

I can't find any problem with the regex itself. Starting to wonder if it's a bug in the regex library... 🤔

Not a bug w/ the regex library:
https://github.com/gitleaks/gitleaks/blob/f0dcd4d9cfe9e9f3e588acb1fd0aaad2e4328ea8/detect/detect.go#L327-L355
Basically SomeTokenXyzab isn't convincing enough. Generic secrets must contain digits otherwise too many false positives would be flagged. Closing this issue


Changes to the reinitialization reintroduced some old buggy behaviour

Changing statblocks in the input field leads to a new parsing of the data (which is good), but some data is retained between throughout the parsing (which is bad and leads to multiples of items/features/spells in the actor).

Hm, i'm not sure if thats related to the changes in reinitialization or the general refactor and the changes maybe to toObject(false), i'll have to take a look later.
@mkahvi If you have the time you could check this as well but it's not urgent. The merges are in the master branch, but not yet in a release, so you would need to check them out manually.

It's likely the re-initialization changes. I probably missed a spot where it needs to reset fully.

Simple hard fix is probably adding sbcData.resetData(true); to updatePreview()

Sorry, i missed info about how to replicate this:

Input a statblock
Change any value in the input field to trigger a re-parsing
Import the Actor
The Actor now has duplicates of some items/features/etc.

I'll test, if the PR fixes that.

I'm not seeing any duplication with the PR in use at least.


[WIP] test, don't merge

Please provide a description of this PR:

@zirain: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test release-notes

integ-security-istiodremote_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test release-notes

integ-security-istiodremote_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security-istiodremote

integ-security_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test release-notes

integ-security-istiodremote_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security-istiodremote

integ-security_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security

integ-security-multicluster_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security-istiodremote

integ-security_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security

integ-security-multicluster_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security-multicluster

release-notes_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security

integ-security-multicluster_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security-multicluster

release-notes_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test release-notes

integ-security-istiodremote_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
e0d89c03b41579c88aee459177dd3d2d5d2a5326
link
true
/test integ-security-multicluster

release-notes_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test release-notes

integ-security-istiodremote_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security-istiodremote

integ-security_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test release-notes

integ-security-istiodremote_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security-istiodremote

integ-security_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security

integ-security-multicluster_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security-istiodremote

integ-security_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security

integ-security-multicluster_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security-multicluster

release-notes_istio
f0541eb3db487224a3d33d4055beb8d9a1129c83
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security-istiodremote

integ-security_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security

integ-security-multicluster_istio
a25584d60f1e92978c16072b5fbafc583130f0d1
link
true
/test integ-security-multicluster

release-notes_istio
f0541eb3db487224a3d33d4055beb8d9a1129c83
link
true
/test release-notes

lint_istio
f0541eb3db487224a3d33d4055beb8d9a1129c83
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


How to get Current year, current month & number of days in a month ?

How to get Current year, current month & number of days in a month ?
Previously i used
let calender = FSCalendar()
CURRENT_YEAR = calendar.currentPage.fs_year
CURRENT_MONTH = calendar.currentPage.fs_month
TOTAL_DAYS = calendar.currentPage.fs_numberOfDaysInMonth
After moving to swift 3 & updated the library it's not working. Please help. Thanks.

Here are the deprecated methods for current month and year:
// Current month
calendar.month(of: calendar.currentPage)
// Current year
calendar.year(of: calendar.currentPage)

// # of Days in a month - you can replace calendar.currentPage with any Date
calendar.numberOfDates(inMonth: calendar.currentPage)

Because the current month and year are deprecated, you could use a date formatter to get what you need, example:
let dateFormatter = DateFormatter()
// Current Year:
dateFormatter.dateFormat = "YYYY"
dateFormatter.string(from: calendar.currentPage)
// Current Month
dateFormatter.dateFormat = "MMMM"
dateFormatter.string(from: calendar.currentPage)

If it's not working you can try using Calendar from Foundation API. You can get the values that you want with the following code:
let values = Calendar.current.dateComponents([Calendar.Component.month, Calendar.Component.year], from: self.calendar.currentPage)
CURRENT_YEAR = values.year
CURRENT_MONTH = values.month

let range = Calendar.current.range(of: Calendar.Component.day, in: Calendar.Component.month, for: self.calendar.currentPage)
TOTAL_DAYS = range.count

Dears,
there is problem showing in header view FS Calendar Collection View the problem years is reserved
if current date 11/2017 will show 11/2018 first item when app is support Right to left
using forceRightToLeft Semantic view
can you help me ?


v0.0.57

Supersedes #59, adds Python version constraint to meta.yaml

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks @necaris!


OJ-1960: Apply monorepo config to the infrastructure template

OJ-1960: Apply monorepo config to the infrastructure temple

Apply changes from the lambda repo template
Fix issues in the template, such as incorrect use of !Ref and !GetAtt
Apply consistent formatting to the template to simplify it and make it easier to read
Use the LanguageExtensions transform to use additional functionality, such as converting YAML object to JSON

Install the latest SAM version when running integration tests
The old version doesn't support the latest syntax and features, and the validation doesn't correctly handle newer templates.

@surajkumar the template succeeds with secure pipelines.
See the run of the deployment to dev job here:
https://github.com/govuk-one-login/ipv-cri-check-hmrc-api/actions/runs/7025310234


Flutter Engine roll presubmits queueing for 5+ hours

https://github.com/flutter/flutter/pull/93327

There was an alert for an increased number of pending tasks in infra
\cc @keyonghan can we mark this to discuss in the next SLO meeting?

There was an alert for an increased number of pending tasks in infra
\cc @keyonghan can we mark this to discuss in the next SLO meeting?

5+ hours doesn't sound quite related to the pending tasks alert. Most likely some builders are queued forever due to backend issues when calling buildbucket API to schedule.

That was my initial thoughts, but https://github.com/flutter/flutter/pull/93327/checks shows they all finished.


ValidationError: Invalid options object. Stylus Loader has been initialized using an options object that does not match the API schema.

Version
4.5.7
Environment info
"stylus-loader": "^4.1.1",

Steps to reproduce
install<EMAIL_ADDRESS>npm run serve
What is expected?
stylus compile successfully
What is actually happening?
 ERROR  Failed to compile with 1 errors                                                                                10:42:34 PM

 error  in ./src/App.vue?vue&type=style&index=0&id=7ba5bd90&lang=stylus&scoped=true

Module build failed (from ./node_modules/stylus-loader/dist/cjs.js):
ValidationError: Invalid options object. Stylus Loader has been initialized using an options object that does not match the API schema.
 - options has an unknown property 'preferPathResolver'. These properties are valid:
   object { stylusOptions?, sourceMap?, webpackImporter?, additionalData? }

Please use stylus-loader@3 at the moment.

I also encountered this problem, using stylus-loader v3 can solve it

I also encountered this problem, using stylus-loader v3 can solve it

确实有效，将stylus-loader的版本降低到3.0.2 能够成功编译

对，我也试过了，用3.0.2版本的stylus-loader就能编译通过。

- "stylus-loader": "^4.2.0",
+ "stylus-loader": "^3.0.2",

This solves it, but I believe we should ensure that v4.x is supported while bundling the app

nice

Thanks for posting the fix!

Thanks for posting the fix!


Typescript RefObjet no longer support ?

In version 1.0.1 beta we have
export declare function useAutoAnimate<T extends Element>(options?: Partial<AutoAnimateOptions> | AutoAnimationPlugin): [RefObject<T>];

// and then

const [parent] = useAutoAnimate<HTMLDivElement>({});

How can I do that with version 1.0.3 beta ?
export declare function useAutoAnimate(options: Partial<AutoAnimateOptions> | AutoAnimationPlugin): import("react").RefObject<Element>;

do I have to cast like this ?
const animationWrapperRef = useAutoAnimate({}) as RefObject<HTMLDivElement>;

why did you close this? looks like it's still an issue


Add Synergy Support for Logical Interconnect Groups

I am not able to create Logical Interconnect Groups with Terraform as described in #47
I am working to resolve this issue, though it appears there are multiple fields needed to successfully create a LIG.

I'm not sure why CI is failing.  The file it is complaining about has been run through gofmt.

Hello @adarobin,
Can you run this command and tell me if it reports any Go files?
find . -type f -name "*.go" -not -path "./vendor/*" | sed "s|^\./||" | xargs gofmt -l

@patrickdappollonio
m-c02tv2lthtd7:terraform-provider-oneview adarobin$ find . -type f -name "*.go" -not -path "./vendor/*" | sed "s|^\./||" | xargs gofmt -l
oneview/resource_ethernet_network.go
oneview/resource_fc_network.go
oneview/resource_fcoe_network.go
oneview/resource_network_set.go

Interesting that the files listed are not what is in the output from CI as having the error.  I'll fix them up and do another commit.

The only thing I'm not happy with is that I need to go back and manually set enclosure_indexes to [1] for all of my C7000 enclosures.  I'd like to make [1] the default value, but that is not possible in the version of Terraform that this plugin is linked against.

@patrickdappollonio
Now the files that were listed as needing fixed on my machine are listed in the CI.  It appears to be a difference in gofmt behavior between versions. See https://github.com/golang/go/issues/26228
m-c02tv2lthtd7:terraform-provider-oneview adarobin$ go version
go version go1.11.2 darwin/amd64

The only thing I'm not happy with is that I need to go back and manually set enclosure_indexes to [1] for all of my C7000 enclosures. I'd like to make [1] the default value, but that is not possible in the version of Terraform that this plugin is linked against.

Hello @adarobin - I agree we we should use latest Terraform version. May be we can take this as an enhancement in future.

@soodpr I tested with API version 600.


Missing volume, so retry

Description
Off-late the vol is returned as nil, and as per the code it raises raise "Volume #{nv[:volume_id]} no longer exists", however the volume does come up eventually as I can see it in the AWS console too.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@meson10

Please sign the CLA here.

This seems to be a duplicate of #255

Ah yes. You are right.

Closing this in favor of #255


[BUG] Signature is not correct

Describe the bug
The car says signature is not correct when I try to install MIB2 Toolbox 2.7.
Firmware(please complete the following information):

Brand: Audi
Hardware-type MIB2High Harmon Nvidia
Version: MU1439

Should be fixed as of now.

Should be fixed as of now.


Make cflinuxfs2 optional

Fixes #8

Not a blocker, but should the trusted certs for the cflinuxfs2 be moved under the cflinuxfs2 feature in kits.yml?  I'm okay with it being generated regardless of that feature being turned on as it will maintain backward compatibility without the need for (not-yet-supported) migration scripts.

Dear Posterity,
I have no idea why I thought this fixed #8.
❤ jhunt

(it actually fixes #74, which is nowhere NEAR #8 on the keyboard or on a number line)


Could not initialize device: TimeoutError: at Object.

Hi i got a Velux Gateway and got these errors:

homekit-controller.0
2023-06-23 07:49:59.138
warn
Device IP-25:86:3F:E3:A0:97 had too many errors, reinitialize connection

homekit-controller.0
2023-06-23 07:48:17.913
warn
IP-25:86:3F:E3:A0:97 Could not initialize device: TimeoutError: at Object. (/opt/iobroker/node_modules/@esm2cjs/p-queue/build/esm/index.js:16:22) at Module._compile (node:internal/modules/cjs/loader:1196:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10) at Module.load (node:internal/modules/cjs/loader:1074:32) at Function.Module._load (node:internal/modules/cjs/loader:909:12) at Module.require (node:internal/modules/cjs/loader:1098:19) at require (node:internal/modules/cjs/helpers:108:18) at Object. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:43:35) at Module._compile (node:internal/modules/cjs/loader:1196:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10)

When i restart the adapter, these issue is still there but i can control the windows for an couple of hours.

Please provide a full debug log. SUch log excerts are mot that helpful.
Otherwise: Did you tried powering off/on the device? Normally this error measn that the devcie i simply not responding because of bad Wifi or other issues

i placed it nearer to the access point, since 12:15 no error. thanks for the hint.


v1.5.3

Good to go.

Have a way of measuring its size with all the filtering and bucketing and
everything that might be going on?
On Mon, Feb 26, 2018 at 3:36 PM Martin Popel<EMAIL_ADDRESS>wrote:

@martinpopel commented on this pull request.
In tensor2tensor/bin/t2t_trainer.py
https://github.com/tensorflow/tensor2tensor/pull/620#discussion_r170772469
:

@@ -65,7 +65,7 @@
flags.DEFINE_string("output_dir", "", "Base output directory for run.")
flags.DEFINE_string("schedule", "continuous_train_and_eval",
"Method of Experiment to run.")

flags.DEFINE_integer("eval_steps", 10000,

flags.DEFINE_integer("eval_steps", 100,

What about silencing the end-of-sequence exception? Or what about using
0="the whole dev set" as the default and measuring its size (number of
batches) first?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensor2tensor/pull/620#discussion_r170772469,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABEGWzZiuwiC2cXiAmEWFhkhdIpLoMhWks5tY0AagaJpZM4ST6ep
.


APPS-247 Fix handling of optional block inputs

Previously, optional block inputs were ignored. This fix instead sets either a default or null value for missing optional block inputs, and throws an exception if there are any missing required block inputs.

@jdidion Would you review https://github.com/dnanexus/dxCompiler/pull/5 so we run it through the integration tests before merging?

I've migrated over changes from the PR updating to wdlTools 0.8.4 and further updated to 0.10.1, which includes another fix required to address this issue.

Hmm...I don't seem to be able to re-run the tests on this PR. Any idea why @commandlinegirl?

I re-applied the integration label to kick off the tests and it worked. Checking what's up with unit tests

BTW: this workflow instance_types is still failing (I'll check later why the test suite passes even though it fails, it doesn't look like a negative test):

I can look into that test. Looks like I should add a unit test there.

@commandlinegirl fixed now.
The reason that integration test job fails but the test passes is because the test is for dynamic selection of instance type. There is no way to access the actual instance type that was selected, other than to make an API call, which we currently don't have a way to do in the testing framework. We should add an issue to enable making assertions about attributes of the job/analysis for a test.

Unit tests are running and passing. The instance_types test is still failing, but for a different reason. I'll work on fixing that.

All integration tests passing 🎉
@commandlinegirl am I ok to merge?


Allow for multiple beforeInitialize hooks

Currently,  you have to overwrite beforeInitialize for your custom initialization code to run. This can be a problem if multiple plugins want to run initialization code.
This change makes beforeInitialize a static api for registering a callback into a list, which will be iterated through and each function called during initialization.

Could you update the README? https://github.com/videojs/videojs-contrib-dash#before-initialize-hook

Looks good to me.

Actually could we give this new API a more appropriate name and show a deprecation warning for the old behavior? That way we don't have to do a major version update just yet.

Could this also replace videojs.Html5DashJS.updateSourceData?

updateSourceData is a completely different api that I don't think will fit with this, but we could follow videojs hooks more by changing the api to take in a label and callback so users can add hooks to different parts of the lifecycle.

Ok I can see how updateSourceData can't be easily worked into this new API.

Looks good to me.


Added model sub-generator #21

This contains the model sub-generator code with tests.

Coverage increased (+1.0%) to 89.302% when pulling a7821c6228dc11ebf2a4631091858066b8dae658 on vprince1:feature-model into b3504ea200ebf63f4f475903394a407f2b8c3514 on binduwavell:master.

Awesome contribution Vijay, thanks a ton. I provided a few nit-picky comments which you are free to deal with or let me know you don't plan to act on them. I don't think anything I mentioned was required for submission. What do you think?

Couple of my tests are failing in the pull request... My branch is passing all the travis tests.. I will need to look at this further.

Coverage increased (+1.0%) to 89.358% when pulling 607c14b4097943783448c533770eed53c46933a3 on vprince1:feature-model into 1114671fd166675d4d3c9b0fcdbdb98cf34bc81d on binduwavell:master.

Coverage increased (+1.0%) to 89.358% when pulling 301b47e9511036946fc6e8b0638b9466bff29929 on vprince1:feature-model into 1114671fd166675d4d3c9b0fcdbdb98cf34bc81d on binduwavell:master.


html2canvas error

Hello
Actually i want to show pdf after click without show html view.
it is posible

Hello @sshekhawat try using html2canvas directly, something like https://stackoverflow.com/questions/20605269/screenshot-of-hidden-div-using-html2canvas. Otherwise, an codesandbox example demonstrating the problem would be nice.


Add LicensePlist

Added LicensePlist to list of Tools.
Project URL
https://github.com/mono0926/LicensePlist
Description
A license list generator of all your dependencies for iOS applications
Why it should be included to awesome-ios (optional)
A tool which generates license list automatically can definitely help the iOS community.
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Error

:no_entry_sign:
Found 1 link issue

Link issue by awesome_bot

Line
Status
Link

1765
301
https://github.com/gizmoboy7/VCFloatingActionButton redirects tohttps://github.com/giridharvc7/VCFloatingActionButton

  Generated by :no_entry_sign: Danger

thx


MM-2954: Add a separate post type for /me messages and update formatting

Summary

Added new constant in PostTypes for me posts
Added new post utility function for identifying me messages
Added extra parameter to getClass method of Post class
Added system message styling to posts of type me
Added or modified unit and integration tests where appropriate

Ticket Link
https://github.com/mattermost/mattermost-server/issues/10902
Related Pull Requests

Has server changes (https://github.com/mattermost/mattermost-server/pull/11082)
Has mobile changes (WIP)
Has redux changes (https://github.com/mattermost/mattermost-redux/pull/850)

This code looks good, but it might need changes based on my feedback on the server PR

@hmhealey I've made the changes based on your suggestions on the server PR, the build is currently failing due to relying on my PR that is up in the redux repo.


Future maintainance

@jorgebodega I left a comment in the pinned issue at the forked repo here: https://github.com/w3tecch/typeorm-seeding/issues/201#issuecomment-1094559596 but I will re-paste here as dev shops are probably wondering what to do moving forward. And since you're now added as a maintainer in the original:
@jorgebodega I agree with @nicolasrouanne, any plans to merge the forked repo back into w3tecch now that you're a maintainer? I imagine you could merge it back and cut a major release and go from there. Would like to know going forward as upgrading to the latest typeorm breaks the current version of w3tecch/typeorm-seeding.

Hi! Sorry for late response, was on vacation.
I do not want until I have, at least, permission as maintainer on repo to add some Actions to help, I don't have much time and cannot be losing more trying to deploy anything manually.
Also, I did this as the best way I can and think, but maybe the original creator don't want it that way.
Right now, I will try to maintain this fork and then will see

Hi! Sorry for late response, was on vacation.
I do not want until I have, at least, permission as maintainer on repo to add some Actions to help, I don't have much time and cannot be losing more trying to deploy anything manually.
Also, I did this as the best way I can and think, but maybe the original creator don't want it that way.
Right now, I will try to maintain this fork and then will see

Thanks for the response @jorgebodega - Cheers


Make sure the compiler module is this hex package is compiled before other dependencies

Other dependencies that have Gleam in them cannot be compiled until this package has been compiled.
Those other packages might not rely on mix_gleam if they are built in rebar.

Could you expand upon the problem? I'm not understanding I'm afraid.


Include animation.length in Animation example

The length of an Animation isn't automatically set by adding keys, and it must be set manually. The existing example only has keys up to 0.5s, so the default value of 1.0s may be acceptable. However, this results in unexpected behavior for anyone who makes an animation longer than 1.0s. Include animation.length in the example because it's important.
Also, increase the key position to 2.0s so it won't be confusing that the assignment is somewhat redundant.

Thanks!

Cherry-picked for 4.1.4.


Keylogger and Clipboard_monitor ==> File logging?

Any simple ideas how to use Empire's module to log into files?

Not at the moment. From a malicious standpoint, it isn't smart to drop files to disk if you don't have to.

Thanks alot.


Notifications Fix

include script to close alerts and notifications manually and slide up after 3 seconds

:+1:

waiting for merge.


Null target_release_timestamp on successful deploy (fix)

There was a regression with the validations branch that was merged
recently -- target_release_timestamp would retain its value after
successful deploy, causing subsequent release creation to return an
error.

Coverage remained the same at 17.637% when pulling 5304bf0df9b2dc7a47a99ca438bd43ecf6dc1730 on deploy_fix into af9877f914c5bd39481c49ec65b77f479600af21 on master.


Checking for update on startup despite disabling "Download updates automatically"

ℹ Computer information

Windows build number: Windows 10 Home 64-bit (10.0, Build 18363) (18362.19h1_release.190318-1202)
PowerToys version: v0.20.0
PowerToy module: General

📝 Reproduction steps

Set option "Download updates automatically" to off
Startup Powertoys (at boot)
The software still searches (and if found prompts to install) for updates

✔ Expected result
The software does NOT searche (and if found prompts to install) for updates
❌ Actual result
The software still searches (and if found prompts to install) for updates

@wieldon
tracked in https://github.com/microsoft/PowerToys/issues/2701


Ft/copy part

Implements upload part copy feature.
Note: THIS CONTAINS A SMALL BREAKING CHANGE.
This modifies the format in which a put part stores data.
As a consequence, the way that an MPU is completed is altered.
This means that an MPU that was initiated prior to May 2nd,
will not be able to be completed.

@ironman-machine up for this?

Hello @LaurenSpiegel,
Starting end to end procedure using the following payload:
{"DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"ft/copyPart"}
Please follow http://ci.ironmann.io/gh/scality/Integration/3231 for circle status.

👍

@ironman-machine you know you want to

Hello @LaurenSpiegel,
Starting end to end procedure using the following payload:
{"DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"ft/copyPart"}
Please follow http://ci.ironmann.io/gh/scality/Integration/3372 for circle status.

@ironman-machine up for this?

Hello @LaurenSpiegel,
Starting end to end procedure using the following payload:
{"DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"ft/copyPart"}
Please follow http://ci.ironmann.io/gh/scality/Integration/3752 for circle status.

end to end passed

@ironman-machine check it

Hello @LaurenSpiegel,
Starting end to end procedure using the following payload:
{"DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"ft/copyPart","REPO_NAME":"S3","PR_NUMBER":174,"ULTRON_URL":"connectore.ringr2.devsca.com:42000"}
Please follow http://ci.ironmann.io/gh/scality/Integration/4641 for circle status.

end to end passed.


Minor font style fixes

@cloudyyoung I didnt know what color attribute meant so i didn't do anything with it

@cloudyyoung I didnt know what color attribute meant so i didn't do anything with it

This is good. Both defining color={"primary"} or not define anything works, but needs to remove the bg thing, so it's good now.


OS X target support

Added OSX target - generate framework for OSX 10.10 target.
Tweaked DownloadTests.swift to avoid deleting entire OSX Documents directory during tearDown()
OSX Tests passing with the exception of AlamofireDownloadResponseTestCase.testDownloadRequest()

Downloaded file is saved with .json extension instead of expected \(numberOfLines) lastPathComponent. Dunno... anyone?

Please excuse the two previous pull requests I closed them myself... :blush:

This PR does not cleanly merge into master. Please resubmit with only the necessary changes.


question: mix of old-style and new-style

This documentation mentions this example:
{
  "acls": [
    {
      "action": "accept",
      "src": ["group:sre"],
      "dst": ["tag:server:*"]
    }
  ],
  "ssh": [
    {
      "action": "accept",
      "src": ["group:sre"],
      "dst": ["tag:server"],
      "users": ["ubuntu", "root"]
    }
  ]
}

In this documentation there is also this example:
resource "tailscale_acl" "sample_acl" {
  acl = jsonencode({
    acls : [
      {
        // Allow all users access to all ports.
        action = "accept",
        users  = ["*"],
        ports  = ["*:*"],
    }],
  })
}

however when using something similar, I get an error when doing a terraform apply:
│ Error: Failed to set ACL
│
│   with tailscale_acl.master_acl,
│   on main.tf line 2, in resource "tailscale_acl" "master_acl":
│    2: resource "tailscale_acl" "master_acl" {
│
│ ACLs contain a mix of old-style "users"/"ports" and new-style "src"/"dst"; use one or the other. (400)

could you clarify what old-style and new-style is?
what is this restriction exactly?
are the examples above up-to-date as well?

Please reopen if there are further questions.


Changed the order of connectors is TR server.xml

If the 443 connector is before the 3333 connector and there are no SSL certs the API will not start correctly.

I think it would be beneficial if you also submitted a PR against the 2.0 branch for this change.


[DRAFT] Declarative Port Graph

TODOS:

make it shared
connection types

encalved
delayed

This looks interesting, but could you provide a high-level description of what this is meant to do?

Closing because #51 is the small tiny rewrite


Event history database migration

Migrating Android Event History Database to use path returned by getDatabasePath() instead of cache directory
Description

Moved database migration function to common FileUtil class.
Added tests for new utility method
Changed table size raw query to prepared statement. It's not recommended to use prepared statement for SELECT query which return cursor, retaining it as is.
Changed AndroidEventHistoryDatabase to use new utility method to open or mirgate database

Related Issue
#66
Motivation and Context
Database is migrated from cache directory because of Android 12 app hibernation changes which can clear app's cache folder when user doesn't interact with app for few months.
How Has This Been Tested?
Need to add functional tests for testing AndroidEventHistoryDatabase https://github.com/adobe/aepsdk-core-android/issues/100
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Moving this to a different PR as the repo got open sourced https://github.com/adobe/aepsdk-core-android/pull/193


[BUG] Pane does not appear/disappears instantly when navigating to it

Describe the bug
When trying to navigate from a page without a cupertino pane to a page with one, the page might flash the cupertino-pane, but then it disappears.
To Reproduce
Steps to reproduce the behavior:
page1.html
<ion-content>
  <ion-button routerLink='/page2'>Login</ion-button>
</ion-content>

page2.html
<ion-content>
  <div class="main-pane">
   ...
   </div>
</ion-content>

page2.js
import { OnInit } from "@angular/core";

export class Page2 implements Oninit{
...
ngOnInit() {
    console.log("Loading Main Pane");
    this.mainPane = new CupertinoPane(".main-pane", {
      parentElement: "ion-content ",
      initialBreak: "middle",
      breaks: {
        top: { enabled: true, height: 1000 },
        middle: { enabled: true, height: 300 },
        bottom: {
          enabled: true,
          height: 30
        },
      },
      buttonClose: false,
      inverse: true,
    });

    this.mainPane.present({ animate: false });
    console.log("Main Pane loaded");
  }
...
}

CONSOLE:
Loading Main Pane
Main Pane loaded

Same issue occurs when using AfterContentInit
Expected behavior
A clear and concise description of what you expected to happen.
The cupertino pane to show as intended when navigated to the new page
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
When the page is refreshed from page2, the cupertino-pane properly shows.
Navigating back a page makes the cuperitno-pane appear. AKA when navigating, I think the cupertino-pane loads on the previous page, even though the initialization is in the first page

@akharag Thank you for issue.
It would be nice if you can provide a video with flashing, so i can explore faster.

https://user-images.githubusercontent.com/22301549/107920029-ed1e2f80-6f74-11eb-8e7b-fbc86c71e5e9.mov

@akharag try to remove parentElement: "ion-content" from settings.
this.mainPane = new CupertinoPane(".main-pane", {
      parentElement: "ion-content ", // REMOVE THIS LINE
      initialBreak: "middle",
      ...
});

You have few ion-content in DOM when you create a page, and pane rendered to wrong element.

Yes, that worked.


Bug Report for dart-sip-ua v1.0.0

Describe the Bug
In dart-sip-ua version 1.0.0, there are issues with the Hold and Speaker functionalities on multiple platforms (Android, Web, Linux). These features work correctly in version 0.6.0, but after updating to 1.0.0, Hold and Speaker do not function as expected.
To Reproduce
Steps to reproduce the issue:
Go to the call screen in the application.
During an active call, attempt to activate Hold.
Attempt to switch audio output to Speaker.
Observe the error or unexpected behavior.
Expected Behavior
The Hold button should pause the call, and the Speaker button should switch the audio output to the device's speaker.
System Information
Flutter SDK Version: 3.24.4 (Stable Channel)
Target OS and Version: Android 13, Web, Linux
Host OS and Version: Ubuntu 20.04

Yea theres another issue up for this, I'm looking into fixing it.


Add multiprocessing

Adding multiprocessing to .map
It works in 3 steps:

shard the dataset in num_proc shards
spawn one process per shard and call map on them
concatenate the resulting datasets

Example of usage:
from nlp import load_dataset

dataset = load_dataset("squad", split="train")

def function(x):
    return {"lowered": x.lower()}

processed = d.map(
    function,
    input_columns=["context"],
    num_proc=4,
    cache_file_name="playground/tmp.arrow",
    load_from_cache_file=False
)

Here it writes 4 files  depending on the process rank:

playground/tmp_00000_of_00004.arrow
playground/tmp_00001_of_00004.arrow
playground/tmp_00002_of_00004.arrow
playground/tmp_00003_of_00004.arrow

The suffix format can be specified by the user.
If the cache_file_name is not specified, it writes into separated files depending on the fingerprint, as usual.
I still need to:

write tests for this
try to improve the logging (currently it shows 4 progress bars, but if one finishes before the others, then the following messages are written over the progress bars)

Logging looks like
Done writing 21900 indices in 3854400 bytes .
Process #0 will write at playground/tmp_00000_of_00004.arrow
Done writing 21900 indices in 3854400 bytes .
Process #1 will write at playground/tmp_00001_of_00004.arrow
Done writing 21900 indices in 3854400 bytes .
Process #2 will write at playground/tmp_00002_of_00004.arrow
Done writing 21899 indices in 3854224 bytes .
Process #3 will write at playground/tmp_00003_of_00004.arrow
Spawning 4 processes
#3: 100%|████████████████████████████████████████████████| 21899/21899 [00:02<00:00, 8027.41ba/s]
#0: 100%|████████████████████████████████████████████████| 21900/21900 [00:02<00:00, 7982.87ba/s]
#1: 100%|████████████████████████████████████████████████| 21900/21900 [00:02<00:00, 7923.89ba/s]
#2: 100%|████████████████████████████████████████████████| 21900/21900 [00:02<00:00, 7920.04ba/s]
Concatenating 4 shards from multiprocessing

I added tests and improved logging.
Both map and filter support multiprocessing

A bit strange that the benchmarks on map/filter are worth than master

The benchmark also got worse in other PRs (see here for example, where we have 16sec for map fast-tokenizer batched and 18 sec for map identity)

Hi,
When I use the multiprocessing in .map:
dataset = load_dataset("text", data_files=file_path, split="train")
dataset = dataset.map(lambda ex: tokenizer(ex["text"], add_special_tokens=True,
                                      truncation=True, max_length=args.block_size), batched=True, num_proc=16)
dataset.set_format(type='torch', columns=['input_ids'])

I get the following error:
Traceback (most recent call last):
  File "src/run.py", line 373, in <module>
    main()
  File "src/run.py", line 295, in main
    get_dataset(data_args, tokenizer=tokenizer, cache_dir=model_args.cache_dir) if training_args.do_train else None
  File "src/run.py", line 153, in get_dataset
    dataset = dataset.map(lambda ex: tokenizer(ex["text"], add_special_tokens=True,
  File "/root/miniconda3/envs/py3.8/lib/python3.8/site-packages/datasets/arrow_dataset.py", line 1287, in map
    transformed_shards = [r.get() for r in results]
  File "/root/miniconda3/envs/py3.8/lib/python3.8/site-packages/datasets/arrow_dataset.py", line 1287, in <listcomp>
    transformed_shards = [r.get() for r in results]
  File "/root/miniconda3/envs/py3.8/lib/python3.8/multiprocessing/pool.py", line 771, in get
    raise self._value
    put(task)
  File "/root/miniconda3/envs/py3.8/lib/python3.8/multiprocessing/connection.py", line 206, in send
    self._send_bytes(_ForkingPickler.dumps(obj))
  File "/root/miniconda3/envs/py3.8/lib/python3.8/multiprocessing/reduction.py", line 51, in dumps
    cls(buf, protocol).dump(obj)
AttributeError: Can't pickle local object 'get_dataset.<locals>.<lambda>'

I think you should use pathos to pickle the lambda function and some others!
I change the 30 line of src/datasets/arrow_dataset.py as following:
# 30 line: from multiprocessing import Pool, RLock
import pathos
from pathos.multiprocessing import Pool
from multiprocessing import RLock

and it will works!

That's very cool indeed !
Shall we condiser adding this dependency @thomwolf ?

We already use dill so that's definitely a very interesting option indeed!

it gets stuck on debian 9 when num_proc > 1

Are you using a tokenizer ?
Did you try to set TOKENIZERS_PARALLELISM=false ?
Feel free to discuss it in #620 , we're discussing this issue

I set TOKENIZERS_PARALLELISM=false. Just the warning went away. The program was still stuck


Recent rendering changes?

Hi,
First of all, just want to say it again: this repo is pure gold. I love the work you're doing here. I'm using this repo to build my mod Radium on if that's cool with you.
Anyway, after the March 20th commits I can no longer build a DirectX 11.3 device without error messages popping up in relation to dxgi1_1.h which I'm still trying to figure out.
To get to the point, some of these commits are enormous, can you give me a breakdown on any rendering changes you've made so I know where to troubleshoot?
Edit: Also, do you have an email you'd be willing to give me? I'd like to send you a message privately.

Renderings have been modified in one of the first commits. Then, about AMD I'm-Dex asked me to check.
But this is not accurate.
:)

@Swartz27 Hi! And thanks for warm words, glad to read this :)
About issue: I have done no changes especialy for the render. So I think that we should find first affected commit at first and then try figure out the reason of the issue. Most likely the problem is linked with cmake, maybe the incude paths settings became different (e.g. for DXSDK) and now code compiles a little bit different. I can try to investigate in this, If you write how to reproduce the issue.
PS: I've opened my email at profile.

I figured out the issue: I had to manually input the Windows 10 sdk directories :P

@Swartz27 I have almost the same problem with Win SDK. Can you say how you input it, please? Absolute path or some environment variable used?

I put in the absolute path, like C:/Program Files(x86)/Windows 10 sdk/include/um or whatever

@Swartz27 Thank you!
Sadly, but i can't find some env variable for win sdk, like dx sdk does. Will use absolute path for now)


Directory::onDidChange / File::onDidChange fire twice on file save if file not empty

console.log "watching"
fired = false
entry.onDidChange ->
  console.log "fire"
  unless fired
    fired = true
    console.log "real fire"
    setTimeout (->fired = false), 1000

Output:
watching
## saving empty file
fire
real fire
## saving file with content
fire
real fire
fire

This issue was moved to atom/node-pathwatcher#74


Dilithium fails when the default PRNG (system random calls) are used

Problem discovered in 3rd party integration that did not specify any flags to the create function.

Dilithium fails if the default system calls are used to provide a PRNG (i.e. the user does not specify a PRNG with the safecrypto_create() flags parameter), if the user specifies any other PRNG it functions correctly.
No other schemes are affected.
The Dilithium testbenches use AES CTR DRBG and are unaffected.

Until resolved, it is recommended that a specific PRNG is used.
NOTE: A default PRNG other than SC_PRNG_SYSTEM should be used  - the system rand() calls are for research purposes only and should not be used in the real world. System rand() calls should NOT be the default option in any fix.

SC_PRNG_SYSTEM cannot be seeded therefore it currently can NOT be used in Dilithium where it must be used with a seed to produce a repeatable random sequence. The two changes will be as follows:

Add a seeding capability to the system PRNG.
Use AES CTR DRBG as the default PRNG.

Resolved in 0.2.0-42, the system PRNG has been removed and AES-CTR DRBG is now the default. The Dilithium testbench has been modified to use the default PRNG settings.


chipsec: 1.10.6 -> 1.13.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for chipsec is: Platform Security Assessment Framework
meta.homepage for chipsec is: https://github.com/chipsec/chipsec
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.12.7 with grep in /nix/store/w8wk0yas3awgf3hish8427p5paynni63-chipsec-1.12.7
found 1.12.7 in filename of file in /nix/store/w8wk0yas3awgf3hish8427p5paynni63-chipsec-1.12.7

Rebuild report (if merged into master) (click to expand)

41 total rebuild path(s)

41 package rebuild(s)

First fifty rebuilds by attrpath
chipsec
linuxKernel.packages.linux_4_19.chipsec
linuxKernel.packages.linux_4_19_hardened.chipsec
linuxKernel.packages.linux_5_10.chipsec
linuxKernel.packages.linux_5_10_hardened.chipsec
linuxKernel.packages.linux_5_15.chipsec
linuxKernel.packages.linux_5_15_hardened.chipsec
linuxKernel.packages.linux_5_4.chipsec
linuxKernel.packages.linux_5_4_hardened.chipsec
linuxKernel.packages.linux_6_1.chipsec
linuxKernel.packages.linux_6_1_hardened.chipsec
linuxKernel.packages.linux_6_5.chipsec
linuxKernel.packages.linux_6_5_hardened.chipsec
linuxKernel.packages.linux_6_6.chipsec
linuxKernel.packages.linux_6_6_hardened.chipsec
linuxKernel.packages.linux_6_7.chipsec
linuxKernel.packages.linux_hardened.chipsec
linuxKernel.packages.linux_latest_libre.chipsec
linuxKernel.packages.linux_libre.chipsec
linuxKernel.packages.linux_lqx.chipsec
linuxKernel.packages.linux_xanmod.chipsec
linuxKernel.packages.linux_xanmod_latest.chipsec
linuxKernel.packages.linux_xanmod_stable.chipsec
linuxKernel.packages.linux_zen.chipsec
linuxPackages-libre.chipsec
linuxPackages.chipsec
linuxPackages_4_19_hardened.chipsec
linuxPackages_5_10_hardened.chipsec
linuxPackages_5_15_hardened.chipsec
linuxPackages_5_4_hardened.chipsec
linuxPackages_6_1_hardened.chipsec
linuxPackages_6_5_hardened.chipsec
linuxPackages_6_6_hardened.chipsec
linuxPackages_hardened.chipsec
linuxPackages_latest-libre.chipsec
linuxPackages_latest.chipsec
linuxPackages_lqx.chipsec
linuxPackages_xanmod.chipsec
linuxPackages_xanmod_latest.chipsec
linuxPackages_xanmod_stable.chipsec
linuxPackages_zen.chipsec

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/w8wk0yas3awgf3hish8427p5paynni63-chipsec-1.12.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A chipsec https://github.com/r-ryantm/nixpkgs/archive/4935cc7f8dfe4df6b7568325684f4a84fae072b6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/4935cc7f8dfe4df6b7568325684f4a84fae072b6#chipsec

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/w8wk0yas3awgf3hish8427p5paynni63-chipsec-1.12.7
ls -la /nix/store/w8wk0yas3awgf3hish8427p5paynni63-chipsec-1.12.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

linuxKernel.packages.linux_4_19_hardened.chipsec

20 packages failed to build:

linuxKernel.packages.linux_4_19.chipsec
linuxKernel.packages.linux_5_10.chipsec
linuxKernel.packages.linux_5_10_hardened.chipsec
linuxKernel.packages.linux_5_15.chipsec
linuxKernel.packages.linux_5_15_hardened.chipsec
linuxKernel.packages.linux_5_4.chipsec
linuxKernel.packages.linux_5_4_hardened.chipsec
linuxKernel.packages.linux_6_1.chipsec
linuxKernel.packages.linux_hardened.chipsec (linuxKernel.packages.linux_6_1_hardened.chipsec)
linuxKernel.packages.linux_6_5.chipsec
linuxKernel.packages.linux_6_5_hardened.chipsec
linuxKernel.packages.linux_6_6.chipsec
linuxKernel.packages.linux_6_6_hardened.chipsec
linuxKernel.packages.linux_6_7.chipsec
linuxKernel.packages.linux_latest_libre.chipsec
linuxKernel.packages.linux_libre.chipsec
linuxKernel.packages.linux_lqx.chipsec
linuxKernel.packages.linux_xanmod.chipsec
linuxKernel.packages.linux_xanmod_latest.chipsec (linuxKernel.packages.linux_xanmod_stable.chipsec)
linuxKernel.packages.linux_zen.chipsec

1 package built:

chipsec

Maintainer pings
cc @JohnAZoidberg @erdnaxe for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for chipsec is: Platform Security Assessment Framework
meta.homepage for chipsec is: https://github.com/chipsec/chipsec
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.13.0 with grep in /nix/store/q26p36wdakvmzfr8afr79xkmvhynyi0s-chipsec-1.13.0
found 1.13.0 in filename of file in /nix/store/q26p36wdakvmzfr8afr79xkmvhynyi0s-chipsec-1.13.0

Rebuild report (if merged into master) (click to expand)

41 total rebuild path(s)

41 package rebuild(s)

First fifty rebuilds by attrpath
chipsec
linuxKernel.packages.linux_4_19.chipsec
linuxKernel.packages.linux_4_19_hardened.chipsec
linuxKernel.packages.linux_5_10.chipsec
linuxKernel.packages.linux_5_10_hardened.chipsec
linuxKernel.packages.linux_5_15.chipsec
linuxKernel.packages.linux_5_15_hardened.chipsec
linuxKernel.packages.linux_5_4.chipsec
linuxKernel.packages.linux_5_4_hardened.chipsec
linuxKernel.packages.linux_6_1.chipsec
linuxKernel.packages.linux_6_1_hardened.chipsec
linuxKernel.packages.linux_6_6.chipsec
linuxKernel.packages.linux_6_6_hardened.chipsec
linuxKernel.packages.linux_6_7.chipsec
linuxKernel.packages.linux_6_7_hardened.chipsec
linuxKernel.packages.linux_6_8.chipsec
linuxKernel.packages.linux_hardened.chipsec
linuxKernel.packages.linux_latest_libre.chipsec
linuxKernel.packages.linux_libre.chipsec
linuxKernel.packages.linux_lqx.chipsec
linuxKernel.packages.linux_xanmod.chipsec
linuxKernel.packages.linux_xanmod_latest.chipsec
linuxKernel.packages.linux_xanmod_stable.chipsec
linuxKernel.packages.linux_zen.chipsec
linuxPackages-libre.chipsec
linuxPackages.chipsec
linuxPackages_4_19_hardened.chipsec
linuxPackages_5_10_hardened.chipsec
linuxPackages_5_15_hardened.chipsec
linuxPackages_5_4_hardened.chipsec
linuxPackages_6_1_hardened.chipsec
linuxPackages_6_6_hardened.chipsec
linuxPackages_6_7_hardened.chipsec
linuxPackages_hardened.chipsec
linuxPackages_latest-libre.chipsec
linuxPackages_latest.chipsec
linuxPackages_lqx.chipsec
linuxPackages_xanmod.chipsec
linuxPackages_xanmod_latest.chipsec
linuxPackages_xanmod_stable.chipsec
linuxPackages_zen.chipsec

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/q26p36wdakvmzfr8afr79xkmvhynyi0s-chipsec-1.13.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A chipsec https://github.com/r-ryantm/nixpkgs/archive/fcbcdc05dbbe6e0c91095a5d7e7df55c03dec42b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/fcbcdc05dbbe6e0c91095a5d7e7df55c03dec42b#chipsec

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q26p36wdakvmzfr8afr79xkmvhynyi0s-chipsec-1.13.0
ls -la /nix/store/q26p36wdakvmzfr8afr79xkmvhynyi0s-chipsec-1.13.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 120m and timed out

Maintainer pings
cc @JohnAZoidberg @erdnaxe for testing.

Obsolete by https://github.com/NixOS/nixpkgs/pull/334626


Feature request: Expire credentials when lease is deleted or expires

This doesn't currently happen. But shouldn't it? As it stands now, you can lease a cluster and then squat on it indefinitely-- even while a new lessee uses it.
This could probably be done by provisioning a new service account for the cluster in question when it is leased. These would be the credentials returned to lessee. That same service account could be de-provisioned when the lease is either deleted or expires.

Agree, I think this is technically possible. However, we currently operate on a trusted lessee model. Do we have reason to believe that a lessee would be malicious and hijack a cluster like this?

@arschles, it doesn't even need to be malicious for this to go sideways. Suppose I lease a cluster for ten minutes and then quite innocently kick off something within that cluster that takes much longer to complete than expected... or blocks indefinitely even.
And I'm realizing now that may also be impetus to build cleanup logic into k8s-claimer... maybe logic that deletes all namespaces that aren't kube-system before returning the cluster to the pool. (I did manage to lease a very dirty cluster during my demo yesterday.)
Last, re: the notion of "trusted lessees," since this is open source, I don't want to make assumptions that anyone else hypothetically using k8s-claimer can trust all lesees. Can we even trust all of ours? Leased clusters are used to test PRs... malicious code in a PR or an accidental indefinite blocking or infinite loop could wreak havoc with a leased cluster that someone else might soon hold the lease on.

@krancour good point. I'm good with leaving this open. also note that the cleanup logic was added to k8s-claimer (https://github.com/deis/k8s-claimer/pull/68). I believe it was working at some point, but I don't know what happened to it since.


Regarding GPU flushes

Describe the bug

What is the reason F state doesn't have any possible transitions for other events while in F state -- I'm assuming it would be possible to get a requests from CPU caches at least, right?
TCC is not sending flush response (to TCP) when block-in-question is at V/W state. It does, however, send the response when the line is at I state. Is there a reason for this?

Tagging @v-ramadas based on commit 085789d
Affects version
Latest stable and develop
Additional information
There are no failing test cases so far, I'm just unable to logically reason about this. It is, however, important for my work.
@mattsinc Please let me know if these kinds of issues need to be taken elsewhere, I'd be happy to oblige :)

Hi @mysoreanoop,

Since most data cache flushes happen right before a checkpoint is taken, I assumed that the a flush is the last event before end of simulation. I haven't seen any other case in the applications I've run so far (Pannonia, heterosync, and square). Let me know if this reasoning doesn't hold true in all cases, and I will add a stall for other events (When line is in F state)
If a line is in V,W state in the TCC and it receives a flush request, it sends the cache line data to the directory before invalidating itself: https://github.com/gem5/gem5/blob/0442c9a88c5e0031d766470c76d1cd8138b313cb/src/mem/ruby/protocol/GPU_VIPER-TCC.sm#L1130
The directory flushes this data down to memory and returns a WBAck response: https://github.com/gem5/gem5/blob/0442c9a88c5e0031d766470c76d1cd8138b313cb/src/mem/ruby/protocol/MOESI_AMD_Base-dir.sm#L1601C7-L1601C7
The TCC sends an ack to the TCP after receiving the WBAck from the directory: https://github.com/gem5/gem5/blob/0442c9a88c5e0031d766470c76d1cd8138b313cb/src/mem/ruby/protocol/GPU_VIPER-TCC.sm#L1104
The TCP then completes the flush by notifying the GPUCoalescer: https://github.com/gem5/gem5/blob/0442c9a88c5e0031d766470c76d1cd8138b313cb/src/mem/ruby/protocol/GPU_VIPER-TCP.sm#L759
The flush request is marked as completed only after the GPUCoalescer receives this acknowledgment. I haven't run into any failing test cases so far but would be interested to see if there is something that breaks this.

Please let me know if this doesn't make sense or if you run into any failures or deadlocks - I'd be happy to take a look.


fix: ⚡ Switch indexer (temporary)

As the api.teia.art is not working since the update Zir0h accepted that we temporarly switch to it


Wrong vscode extension

editor page in 8.2 docs points to reason-vscode  which doesn't contain rescript syntax anymore

Should be rescript-vscode I think

Fixed on master. Thanks!


How to enable GPU inference and how t train for multiple objects

Hi,
Thank you so much for your support with my last issue.
Now I can able to run run the given code in Linux platform also.
Please let me know how to do inference with GPU.
When try to do inference using video input it is very slow. Hope GPU usage will improve the efficiency.
It is possible to train multiple objects like people, animals etc.. in a model.
Thanks and regards,
Prabhakar M

The member function Initialize accept gpu id arg... I tested 512*512 input in rtx2070s, reached 30ms for predicting. You can use better gpu cards and smaller inputs and smaller architecture....
Supports muticlass

Hi AllentDan,
I am new to deep learning. It will be helpful if I can get any hint to try this with TensorRt.

@mprabhakarece This repo may not support tensorrt in a short time. I am not quite familiar with tensorrt either.
But you can go to mmsegmentation or tensorrtx for a chance.

@AllentDan
Hope you are doing well. Still I working for codes with improved FPS for semantic segmentation. Is it possible to convert our segmentor.pt to onnx and then to TensorRT engine file.

The chance is slim.


c++14 only?

Hi,
This look good, but it appears to be c++14 only, is this correct?
Any chance it could be 'fixed' to work with c++11?
Bye!
Mark

I'll have to take a look. I really dont want to go backwards, but ill take a look. If its minimal, then yeah I'll drop the c++ 14 features.
Ill be taking a look at this today or tomorrow. If you have any suggestions, issue a PR, they are always welcome

I hit the wrong button when closing this...

Actually, I think I should be able to upgrade my project to c++14 so this
might not be necessary.
On Mon, May 1, 2017 at 2:34 PM, Scott<EMAIL_ADDRESS>wrote:

I hit the wrong button when closing this...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/smasherprog/Screen_Capture/issues/16#issuecomment-298276395,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADU3QrbpAXrjo1jk43pEFqc26QZF44sOks5r1UTDgaJpZM4NMuH9
.

Ok, great.. I am always trying to move with the latest c++ standard.

Closing this. I would like the code to be current with the standard and supported by the big three compilers, which c++14 is


"script setup" syntax has problems with importing types

Actually I'm not sure if this is more Vue 3 or Volar issue.
While importing "PropType" I'm getting warnings in IDE:
'PropType' only refers to a type, but is being used as a value here. ts(2693)
Code for reproduction:
<script setup lang="ts">
import { defineProps, PropType } from 'vue'

defineProps({
  demo: {
    type: Object as PropType<{ demo: string }>,
    required: true,
  },
})
</script>

Thing is, it looks fine without setup syntax.
<script lang="ts">
import { defineComponent, PropType } from 'vue'

export default defineComponent({
  props: {
    demo: {
      type: Object as PropType<{ demo: string }>,
      required: true,
    },
  }
})
</script>

Same thing happens for me while importing any custom types/interfaces.
import { SomeType } from '@/types/sometypes'
But I found out that warning also disappears after using "import type"
import type { SomeType } from '@/types/sometypes'
Cool, so accordingly we can also do this:
import { defineComponent } from 'vue'
import type { PropType } from 'vue'

But this shouldn't be necessary. I also did not found this in any vue docs or RFC. So why this TS warning appears with script setup?
Have a nice day :)

Hi @chojnicki, this is vue limitation, see: https://github.com/vuejs/vue-next/issues/3183
So I create this error to avoid user runtime error.

Instant reply as always, are you resting at all? 😆
Thanks for linking issue, I will stick with import type then.

I want to finish this project as soon, and then I can rest. 😅


Ligature and cursorcolumn collide

When using cursorcolumn, ligatures sometimes get "broken up".

Thanks for logging the issue, @topaxi !
Seems likely that it is a bug in our rendering layer here: https://github.com/onivim/oni/blob/master/browser/src/Renderer/CanvasRenderer.ts
If we split up the token rendering, that could break the ligature (potentially cursorcolumn could be related to this).
Just curious - is cursorcolumn set via your init.vim, or are you using the editor.cursorColumn setting in Oni's config.js?

Set via init.vim :)

Actually @badosu, the webgl renderer hasn't got ligatures yet so this won't be able to be tested quite yet.
I'll tag @Cryza who is working on the ligature support in the WebGL side of things, in case this needs any fixes on the renderer side (I expect not).


Extract subset split

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@4a586d6). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage        ?   92.68%
=======================================
  Files           ?        5
  Lines           ?      246
  Branches        ?        0
=======================================
  Hits            ?      228
  Misses          ?       18
  Partials        ?        0

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Feature Request: Support alpine 3.7

Tried to use container-structure-test in an alpine 3.7 container, got error "/bin/sh: container-structure-test: not found". (Everything works fine in Ubuntu and Redhat Linux containers).
apk add --no-cache ca-certificates
apk add --no-cache wget
wget -O container-structure-test https://storage.googleapis.com/container-structure-test/latest/container-structure-
test
chmod +x container-structure-test
container-structure-test --help
/bin/sh: container-structure-test: not found

@precompiler Issue is that is compiled with glibc. To be able to run it in alpine you need to compile it with musl-libc.
I have tested it in docker. Save following Dockerfile
FROM golang:1.9.4-alpine3.7 AS builder

RUN apk add --no-cache alpine-sdk=0.5-r0
RUN go get github.com/fsouza/go-dockerclient

# container-structure-test version
ARG CST_TAG=v0.2.0
ENV SOURCE_PATH=/go/src/github.com/GoogleCloudPlatform/container-structure-test

RUN git clone \
    --depth 1 https://github.com/GoogleCloudPlatform/container-structure-test.git \
    --branch "$CST_TAG" \
    "$SOURCE_PATH"

WORKDIR $SOURCE_PATH
RUN go test -c . -o /container-structure-test

FROM alpine:3.7
COPY --from=builder /container-structure-test /usr/local/bin

and run from that folder
docker build -t container-structure-test:alpine3.7 .

your binary is in the PATH so you can run it
docker run --rm -i container-structure-test:alpine3.7 container-structure-test --help

@zemanlx Thank you very much for your help, it works now!


Triple Dot 'More' Button Does Nothing

This is probably because the Block button is still there, but has a TODO class on it so it's hidden.

Could we hide the more button until block button is added?


package extra full

We had a discussion about adding where/how to add the ruamel.yaml dependency, which is already included in the test extra.  @oeway suggested a new extra: full
test also includes pytest, tox and mypy. so maybe adding full is justified...
Originally posted by @FynnBe in https://github.com/bioimage-io/spec-bioimage-io/issues/259#issuecomment-946493022

Hi @FynnBe I recently did some fix for another package which meant for both native and pyodide, I think the best solution so far is to use the conditional statement.
setup(
    ...,
    install_requires=[
        ...
        "ruamel.yaml;platform_system!='Emscripten'", # will be included for native python
    ],
)

See here: https://github.com/pyodide/pyodide/issues/1984#issuecomment-974888357

naive question @oeway: is there a way to test the package with pyodide in CI?

@k-dominik Sure, basically we can install a browser in CI and use that to run a webpage to test pyodide. I was doing this with playwright which also has a python version. This does mean it requires some efforts to set it up.

Issue reported by @esgomezm:
The validation command in the doc: https://github.com/bioimage-io/spec-bioimage-io#bioimageio-spec-validator does not work as expected.
This is because yaml is not included in the default installation (see discussions in this issue).
We should also somewhere add a recommendation to use bioimageio.core if one has access to  a full python installation, as this avoids many issues.

I believe we already have a solution for this using the conditional
requirement in the setup.py file. @Fynn
On Mon 29 Nov 2021 at 14:36, Constantin Pape @.***>
wrote:

Issue reported by @esgomezm https://github.com/esgomezm:
The validation command in the doc:
https://github.com/bioimage-io/spec-bioimage-io#bioimageio-spec-validator
does not work as expected.
This is because yaml is not included in the default installation (see
discussions in this issue).
We should also somewhere add a recommendation to use bioimageio.core if
one has access to a full python installation, as this avoids many issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bioimage-io/spec-bioimage-io/issues/265#issuecomment-981641410,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADU3SYCTS6UCGLEF3I4VL3UON6XBANCNFSM5GL6HSZQ
.


⚠ Bofrost.lu has degraded performance

In 0efef39, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1647 ms

Resolved: Bofrost.lu performance has improved in f99dfe8 after 8 minutes.


Uncaught TypeError: Cannot set properties of undefined (setting '$gtag')

hi
i want use this to nuxt
i created gtag.js
import Vue from 'vue'
import VueGtag from 'vue-gtag'

Vue.use(VueGtag, {
  config: { id: 'G-XXXXXXXXXX' },
})

and in nuxt.config i use
  plugins: [
    {
      src<EMAIL_ADDRESS>      ssr: true,
    }
]

but i get  this error
Uncaught TypeError: Cannot set properties of undefined (setting '$gtag')
I use vue 2

Hi @MOAB7698, I had the same issue. It looks like if you are using Vue 2 you need to install one of the previous versions of vue-gtag. There is actually an open PR to make this clearer in the V2 docs which can be found here:
https://github.com/MatteoGabriele/vue-gtag/pull/442/files
The relevant part being this line which shows which version is compatible with Vue 2:
npm install<EMAIL_ADDRESS>

That's correct. Default version is now for vue 3. you should install vue-gtag@legacy for vue 2


Couldn't start Java Language Server

Type: Bug
I ran into this error message when coding with Java files. Couldn't start the Java Language Server.  I am using Microsoft's OpenJDK 11.0.12, while JShell shows version <IP_ADDRESS>
VS Code version: Code 1.74.0 (5235c6bb189b60b01b1f49062f4ffa42384f8c91, 2022-12-05T16:38:16.075Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2419)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.77GB (8.46GB free)

Process Argv
--crash-reporter-id 878a6b85-9049-465e-849e-1cc9b3b95d57

Screen Reader
no

VM
0%

/extJava

It looks like this is caused by the Java extension. Please file the issue to the Java extension repository. Make sure to check their troubleshooting instructions and provide relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


Ionic2  How to use $watch

Hello! Thanks for opening an issue with us! As this seems like more of a support question i will urge that you ask this question on our forum (forum.ionicframework.com). Thanks for using Ionic!

OK，Thank you very much


incompatible with python 3.0 due to lib/pyaml

The library pyyaml, is out of date, and recent changes in python 3.10, makes pyyaml unable to parse yaml files.

nevermind, was my clone that was broken


How to install on FreeBSD System?

I didn't find the tutorial

If you want to install the Python version, just sudo python3 -m pip install --upgrade trzsz on the server.
If you want to install the Go version (Recommended), just go install github.com/trzsz/trzsz-go/cmd/...@latest on the server.

OK, thank you. My server does not have a Go environment. It seems that I can only install the python version. Do I need to configure environment variables after installation? Or can I use it directly after installing it with python?

I will compile the freebsd binary in the next Go version. You can download and unzip it from Go Releases to use.

Do I need to configure environment variables after installation? Or can I use it directly after installing it with python?

As long as you can find trz and tsz after installation and run them.

Okay, thank you very much.


Inconsistent rendering when using context SetZIndex()

I'm rendering some paths to a canvas context, and then adding a border/fill behind the items on the canvas. When I invoke the ctx.SetZIndex(-1) call, this is where the inconsistency starts - the final image can either be right - and most of the time it is - but some amount of the time (e.g. 16 out of 100 runs), the border isn't drawn and you just get the blue square in the middle.
If I omit the ctx.SetZIndex(-1) call, the image is consistent every time, but the border/background rectangle is covering up the previously-drawn content. In this simplified example, I could work around the issue by drawing the blue rectangle after bordered box, but in my actual use case, this isn't possible since I'm fitting the canvas to arbitrary-sized content first and then drawing a border around and background under it (unless I was to duplicate the content rendering and offset its positions etc).
Correct:   Incorrect:
package main

import (
	"fmt"

	"github.com/tdewolff/canvas"
	"github.com/tdewolff/canvas/renderers"
)

const borderWidth = 1.0

func main() {
	for i := 0; i < 100; i++ {
		c := canvas.New(100, 100)
		ctx := canvas.NewContext(c)

		// ctx.SetZIndex(0) // has no effect
		ctx.SetFill(canvas.Blue)
		ctx.DrawPath(45, 45, canvas.Rectangle(10, 10))

		border := canvas.Rectangle(c.W+borderWidth*2, c.H+borderWidth*2)
		ctx.SetStroke(canvas.Black)
		ctx.SetStrokeWidth(borderWidth)
		ctx.SetFill(canvas.White)
		ctx.SetZIndex(-1)
		ctx.DrawPath(0, 0, border)

		c.Fit(0.1)

		_ = renderers.Write(fmt.Sprintf("test-%d.png", i), c, canvas.DPMM(6))
	}
}

Run in the loop, the results vary. Each run produces different results, suggesting some form of race condition:

Thanks for raising this, I've pushed out a fix, let me know if it works!

Amazing, thanks @tdewolff - confirmed it handles the issue. Thanks for the quick fix!


NameError: name 'preds' is not defined

Hello Omar Ayman,
I find this Project very interesting so I tried it. but when the model does not detect any face then line 53 thoughts error because the 'preds' is defined inside the if condition.
Thank You :-)

Hey man,
this error appears sometimes and i can't find a reason why is this error raising but what i did is that whenever it appears i run the script again and it worked, stupid solution till i find what really causing it.

I'm exactly the same, but as much as I run the script does not work: this is my log:
Using TensorFlow backend.
2018-10-31 19:07:29.243116: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2018-10-31 19:07:29.494922: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1411] Found device 0 with properties:
name: TITAN V major: 7 minor: 0 memoryClockRate(GHz): 1.455
pciBusID: 0000:01:00.0
totalMemory: 12.00GiB freeMemory: 9.67GiB
2018-10-31 19:07:29.502864: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1490] Adding visible gpu devices: 0
2018-10-31 19:07:30.692378: I tensorflow/core/common_runtime/gpu/gpu_device.cc:971] Device interconnect StreamExecutor with strength 1 edge matrix:
2018-10-31 19:07:30.696807: I tensorflow/core/common_runtime/gpu/gpu_device.cc:977]      0
2018-10-31 19:07:30.699723: I tensorflow/core/common_runtime/gpu/gpu_device.cc:990] 0:   N
2018-10-31 19:07:30.709265: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1103] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 9272 MB memory) -> physical GPU (device: 0, name: TITAN V, pci bus id: 0000:01:00.0, compute capability: 7.0)
Traceback (most recent call last):
File "real_time_video.py", line 53, in
for (i, (emotion, prob)) in enumerate(zip(EMOTIONS, preds)):
NameError: name 'preds' is not defined

Add a line "else: continue" after the condition code "if len(faces) > 0:", then run the script and it will work.

Python code line Structure error causing this problem. the solution for this is to manage the for loop in a structured way so that it will able to read 'preds'.
Problem :

Solution :

Hope you have found what you were looking For. :)

#20 PR with fixing


Spyder 4.1.1:  jedi 0.15.2 dependency error

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
I get this error on starting spyder 4.1.1:

What steps reproduce the problem?

Start spyder 4.1.1

What is the expected output? What do you see instead?
jedi 0.14.1 is installed.  If I try and install jedi 0.15.2, as apparently required, spyder will be downgraded:
> conda install jedi=0.15.2
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: done

## Package Plan ##

  environment location: C:\Users\me\Miniconda3\envs\forge

  added / updated specs:
    - jedi=0.15.2

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    jedi-0.15.2                |           py37_0         738 KB
    spyder-3.3.6               |           py37_0         2.3 MB
    spyder-kernels-0.5.2       |           py37_0          71 KB
    ------------------------------------------------------------
                                           Total:         3.1 MB

The following packages will be UPDATED:

  jedi                                        0.14.1-py37_0 --> 0.15.2-py37_0

The following packages will be SUPERSEDED by a higher-priority channel:

  spyder             conda-forge::spyder-4.1.1-py37hc8dfbb~ --> pkgs/main::spyder-3.3.6-py37_0

The following packages will be DOWNGRADED:

  spyder-kernels                               1.9.0-py37_0 --> 0.5.2-py37_0

Proceed ([y]/n)? n

CondaSystemExit: Exiting.

 Please wait until new packages are generated in conda-forge.


Hoover highlights

adding visual interaction updates

these were color adjustments (which could be shortened with a few functions)... need to re-add any subtitle pop-ups or labels for nodes... then branch into secondary svg/div articulations of node imagery and node text.


Themis 0.14

Getting ready for the next release. Let's see how many things I forgot to update this time.
release-0.14-prep branch is in the main repo, feel free to throw in changes there directly.
Checklist

[X] Change is covered by automated tests
[X] Changelog is updated
[X] Versions are updated
[X] Provisional 0.14.0 tag points to this branch

Published documentation pending review:

[x] CHANGELOG.md
[x] README.md
[x] gothemis/README.md
[x] src/wrappers/themis/jsthemis/README.md
[x] src/wrappers/themis/python/README.md
[x] src/wrappers/themis/rust/README.md
[x] src/wrappers/themis/rust/libthemis-sys/README.md
[x] src/wrappers/themis/wasm/README.md

Packaging files that will be updated later:

PKGBUILD.MSYS2 – once we have a stable tag and source tarball
Package.swift – once we have a binary release ready
docs/examples, tools – once release is published

While rereading changelogs for 0.13, I have noticed that we have one more change to CocoaPods subspecs to make. Don't be too quick to merge this PR, I have one extra thing to add to release/0.14 before this one.

Okay, merged in the subspec change and moved the provisional 0.14.0 tag to the updated branch so that podspec validation should actually succeed. Waiting on CI...

haha, we had tests for boringssl!

haha, we had tests for boringssl!

Not funny ☹ I'll save the jokes for the next PR.
Stand by, I need to unfuck my Ruby installation first to get CocoaPods to install dependencies, to test BoringSSL removal.

And once again 🤞 Third time's the charm, right?


can not download business account info

I enter the business path but when I click enter with credential, it just all blank.-> resolve

still issue persist.


ts-reset for DOM lib

Hey @mattpocock, thanks for ts-reset. I've been thinking about making something similar for DOM specs. Several APIs say they exist, but they do not work across all browsers.
My plan on how to solve this is to use something like Playwright, inspect all DOM APIs and check that they exist and write a JSON object out towards the end of the test runner and then make a diff and where the APIs don't work across browser make the API optional, and append some docs with notes around which browsers support what.
What do you think about this being a part of or an extension of ts-reset?

This would really help avoid footguns in certain cases and (as an outside observer) feels like it's very much in the spirit of this project.
The only concern I have is that it's a much more empirical approach than what's already done here. It could easily be its own project.
However, my feeling is that it's much better for the ecosystem (especially new devs) to have one simple answer to this problem rather than dividing it across multiple projects. Since the project is modular, people don't need to use it if they don't want to.
Regardless if this ends up being a separate project or integrated to this one, I'd be happy to help if you want a partner in crime @lifeiscontent ✌
TLDR; I would love to see this become a part of ts-reset and an happy to help!

@lifeiscontent I agree that there are some DOM API's that could be typed better. It's definitely in scope for ts-reset to work on those. Happy to accept issues and PR's in that vein, for individual improvements.
However, I don't want to go down the road of typing API's that TS hasn't managed to yet. I trust TS's process - it sounds similar to yours, except that it uses API data from caniuse.com to only type things which have support in 2+ browsers.

@mattpocock i wasn't planning on typing anything that the TS team hasn't already typed for us, but more like narrowing those types to showcase APIs that may not work across browsers (that currently exist in the DOM types)
Does that align with you?

@lifeiscontent Could you give me an example?

@mattpocock yes, for example all aria* attributes on an element do not work in Firefox.

I think I'd prefer not to get into that particular territory - sounds like a maintenance nightmare to keep all that stuff up-to-date, and I think TS does a good enough job.

@lifeiscontent are you interested in making this a separate project?


Using open or export does not make names accessible for extended field notation (dot notation)

Description
If you try to use open or export to import names to use for dot notation, it does not work. Confusingly, you can have String.a "x" succeed but "x".a fail.
Context
Zulip thread where this was brought up, during an Advent of Code problem.
Steps to Reproduce
Observe that "x".a produces an error in the following
namespace Common
namespace String

def a (s : String) : Nat := s.length

end String
end Common

open Common (String.a)

#eval String.a "x"

/-
invalid field 'a', the environment does not contain 'String.a'
  "x"
has type
  String
-/
#eval "x".a

export Common (String.a)

/-
invalid field notation, function 'Common.String.a' does not have argument
with type (Common.String ...) that can be used, it must be explicit or
implicit with a unique name
-/
#eval "x".a

Expected behavior: The second and third #evals have the same interpretation as the first.
Actual behavior: Only the first succeeds. The second #eval (when the name is just open) doesn't see String.a at all, and the third #eval (when the name is exported) it sees it but then fails to process it correctly.
Versions
MacOS arm64
/- "4.3.0-rc2" -/
#eval Lean.versionString

Impact
Add :+1: to issues you consider important. If others are impacted by this issue, please ask them to add :+1: to it.

I would love this feature, it would be a way to avoid the name-clash-inducing practice of defining functions outside the project namespace so that you get dot notation on types you don't own.

I think this is an RFC :) . It is a sensible enhancement suggestion but it is not an accidental oversight in the implementation.

I should also mention a much older proposal of allowing any top-level name in scope as a target for extended field notation. This is especially interesting for typeclasses where it would allow us to use x.toString uniformly instead of the status quo where it only works sometimes depending on whether that exact declaration name was used to construct the instance. It is similar to how in Rust you need to use a trait to get dot access to its members.
It might be that these two proposals are independent(ly desirable) but they are similar enough that I wanted to mention this one in case we say that it would be confusing to have both.

#6189 implements this along with @Kha's suggestion.
New rule: given x : S, then x.f tries resolving S.f with respect to the root namespace. If there are no names, then it tries it with each parent in the resolution order of S as well, if S is a structure.
Additionally, as a last resort, after all attempts of unfolding S to find a resolution, it looks for f in the root namespace (either as an exact match or as an alias) and then does f S. I made it pay no attention to open, since I couldn't think of any examples where you would want that, but it does resolve x.toString to toString x since toString is exported.


Fix collecting github stats after timezone-migration

I need to check how to test this the best possible way

I need to check how to test this the best possible way

I were able to reproduce the error locally, and the change fixes it.

I were able to reproduce the error locally, and the change fixes it.

@pietroalbini  this could be a fix, but it doesn't add tests to the previously untested code.
I'm not sure what the strategy for these tests will be (mocking? some other technique?), if that's decided I could provide tests in the next days.
Question is if we want to wait with this fix for the tests.

@pietroalbini  this could be a fix, but it doesn't add tests to the previously untested code.
I'm not sure what the strategy for these tests will be (mocking? some other technique?), if that's decided I could provide tests in the next days.
Question is if we want to wait with this fix for the tests.

I don't think this should be blocked on tests, I see it as the same sort of issue as #822 where the tests need some design.

I don't think this should be blocked on tests, I see it as the same sort of issue as #822 where the tests need some design.