Cannot write patterns after options

If you write the following, it will not work as expected.
eslint-interactive --ext .ts,.tsx,.vue src

This is equivalent to the behavior as if .ts,.tsx,.vue and src were passed to the ext option, according to the yargs specification (https://github.com/yargs/yargs/issues/1848).
eslint-interactive --ext .ts,.tsx,.vue --ext src

This confuses for the user because it is interpreted differently than eslint.
Workaround
You can avoid this problem by always writing the directory patterns first.
eslint-interactive src --ext .ts,.tsx,.vue

related works: https://github.com/tj/commander.js/blob/master/docs/options-taking-varying-arguments.md


cmd/compile: unexpected heap allocation passing pointer to non-escaping closure

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
1.6

What operating system and processor architecture are you using (go env)?
darwin

What did you do?

  // Run with `go test -run - -bench . -benchmem -gcflags '-m -l -e'`
  func BenchmarkClosurePtrFromArg(b *testing.B) {
  	inc := func(k *int) {
  		*k++
  	}
  	for j := 0; j < b.N; j++ {
  		var i int // does escape
  		inc(&i)
  	}
	}

See https://github.com/tschottdorf/goplay/tree/master/alloc_tests

What did you expect to see?

I'd expect i to not be allocated on the heap. The following very similar examples keep it on the stack:
  func BenchmarkClosureVarFromScope(b *testing.B) {
  	for j := 0; j < b.N; j++ {
  		var i int // does not escape
  		inc := func() {
  			i++
  		}
  		inc()
  	}
  }

  func BenchmarkClosurePtrFromScope(b *testing.B) {
  	for j := 0; j < b.N; j++ {
  		var i int // does not escape
  		ptr := &i
  		inc := func() {
  			*ptr++
  		}
  		inc()
  	}
  }

  func incExt(k *int) {
  	*k++
  }

  func BenchmarkFuncPtrFromArg(b *testing.B) {
  	for j := 0; j < b.N; j++ {
  		var i int // does not escape
  		incExt(&i)
  		if i != 1 {
  			b.Fatal()
  		}
  	}
  }

What did you see instead?
i escapes to the heap.

cc @tamird

@dr2chase time for your explainer to shine!

That'd be great - there are some more cases in the linked package github.com/tschottdorf/goplay/alloc_tests.

Short answer is loop nesting depth -- assigning in-loop mem to outside-loop data results in escape
Will try explainer on it later.

That  can't be it, this still allocs:
diff --git a/alloc_tests/alloc_test.go b/alloc_tests/alloc_test.go
index a8bc976..a8ccabb 100644
--- a/alloc_tests/alloc_test.go
+++ b/alloc_tests/alloc_test.go
@@ -27,10 +27,10 @@ func BenchmarkClosurePtrFromScope(b *testing.B) {
 }

 func BenchmarkClosurePtrFromArg(b *testing.B) {
-	inc := func(k *int) {
-		*k++
-	}
 	for j := 0; j < b.N; j++ {
+		inc := func(k *int) {
+			*k++
+		}
 		var i int // does escape
 		inc(&i)
 	}

Much simpler answer: indirect call.  Escape analysis knows nothing about any constants that you might propagate, such as function bodies.  That's something that would be nice to do in the future, but right now, it's thoroughly upstream of SSA (yes, I know this is annoying).
go test -run - -bench . -benchmem -gcflags '-m -m -l -e'
# _/Users/drchase/GoogleDrive/work/tmp/ESC
./esc_bench.go:11: moved to heap: i
./esc_bench.go:12: &i escapes to heap
./esc_bench.go:12: 	from inc(&i) (parameter to indirect call) at ./esc_bench.go:12
./esc_bench.go:7: BenchmarkClosurePtrFromArg.func1 k does not escape
./esc_bench.go:6: BenchmarkClosurePtrFromArg b does not escape
./esc_bench.go:7: BenchmarkClosurePtrFromArg func literal does not escape

But, what do you think of the explainer?

Not sure I follow. Maybe an explanation why BenchmarkClosurePtrFromScope does not alloc would illustrate this nicely - I naively would've expected that to be exactly equivalent in SSA.
:+1: on the explainer (ran across it on multiple occasions). It'd be interesting to be able to use the output for code highlighting - the only missing part is giving not online line numbers, but also a char range in that line if that's possible. (something like 12:56-89 for line 12 chars 56-89).

Having the explainer explain negatives is a bit more work.  In this case, &i is not a parameter to an indirect call, so it is okay.  SSA is very much (right now) a back-end-only phase, run well after escape analysis decisions have been made.  Indirect calls are treated like they are radioactive, but we can still see that the closure itself doesn't escape, nor does it assign to globals.

@dr2chase Thanks. I'm still not really following what's going on, but I think I can just look at your explainer (which presumably would give me some ideas about what the corresponding SSA for the above example looks like). Do you have its source online somewhere?
Also, no point in keeping this issue open, correct?

The explainer is now in pre-1.7.  Build with -gcflags '-m -m' and you'll get explanations.  The code for the explainer is interspersed through esc.go, which runs upstream of SSA.
And there's no point keeping this open now, you are correct.

Excellent, thanks again.
On Wed, Mar 30, 2016 at 11:11 PM dr2chase<EMAIL_ADDRESS>wrote:

The explainer is now in pre-1.7. Build with -gcflags '-m -m' and you'll
get explanations. The code for the explainer is interspersed through
esc.go, which runs upstream of SSA.
And there's no point keeping this open now, you are correct.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/golang/go/issues/14699#issuecomment-203731393


Add /servicestatus endpoint to allow automated status monitoring.

This adds /servicestatus and /servicestatus.json endpoints. These are useful for conveniently checking the service is OK, monitoring the deployed revision and checking uptime.

Test pass locally.


CTabs event not working

<CTabs @update:activeTab="activeTab"></CTabs>
As per the https://coreui.io/vue/docs/introduction/ => V 3.0.0
has @update:activeTab event but this event is not working. I checked the GitHub code some of the versions not returning the event emit.

Yes, this feature is available only since 3.0.0-beta.11. If you have the current version it is possible that you duplicate 'activeTab' varaible

<CTab @click="someFunction"/> this is also not working @woothu

@yaswanthkoneriomni I responded for your issue https://github.com/coreui/coreui-free-vue-admin-template/issues/199


System.exit in case of an exception in KafkaProducer

https://github.com/softwaremill/reactive-kafka/blame/master/src/main/scala/kafka/producer/KafkaProducer.scala#L93
Could you handle exceptions in the producer other than System.exit?

This part of code comes from another library: https://github.com/stealthly/scala-kafka/blob/master/src/main/scala/KafkaProducer.scala, I guess I missed this weird System.exit() from the beginning.
Thanks for pointing that out, there are obviously better ways to handle this ;)


[Feature]: support ls -w to specify the width/columns

Version

[X] latest

version
❯ lsd --version
lsd 1.0.0

What OS are you seeing the problem on?
macOS
installation
brew install lsd
term
xterm-256color
ls-colors
N/A
What happened?
My terminal window is 120 characters wide.
If I do ls or lsd, then I get multiple (3) columns in my ~/git directory.
Now, if I pipe the output through less (or cat) I only get a single column.
The workaround for GNU ls is to use the -w $COLUMNS option (more conveniently defined as a shell function. The workaround for BSD ls is to export COLUMNS.
I don't think there's a workaround for lsd
What expected?
lsd should offer an option, as ls does, to preserve multiple columns even when piped.
What else?
See https://askubuntu.com/questions/89173/preserving-multi-column-output-from-ls-when-paging/89177#89177

(Btw, the "New issue" page has 2 "Bug reports" and no "Feature requests". And strangely, the "new" Bug Report form puts some of the form fields into code fences instead of being consistent and offering us full Markdown textareas)

puts some of the form fields into code fences instead of being consistent and offering us full Markdown textareas)

Hi @huyz, it is meant to be like this, this is a new feature of GitHub, which can help us gather more required information when users submit issues.
/feature

Hi @huyz, it is meant to be like this, this is a new feature of GitHub, which can help us gather more required information when users submit issues.

I figured it's intentional. However, I'm giving feedback that it doesn't work well. IMHO all textareas should be the same: either non-Markdown or all Markdown.  Otherwise, the formatting comes out all wrong with no line-wrapping and unclickable links. UX fail if you ask me


chore: tf version fix

Description
Terraform version suppport >=1.3.0 and <1.6.0
Release required?

[x] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

Fixed in this PR https://github.com/terraform-ibm-modules/terraform-ibm-client-to-site-vpn/pull/104


pdf.js showing wrong portion of images

Link to PDF file (or attach file here): https://cloud.box.com/s/3idigur8fepcqxto007ykhjca3w0x68i
Configuration:

Web browser and its version: Chrome 55
Operating system and its version: Mac OSX El Capitan
PDF.js version: 1.6.334
Is an extension: No

Steps to reproduce the problem:

Visit https://cloud.box.com/s/3idigur8fepcqxto007ykhjca3w0x68i
Go to page 6
Note image in bottom right is cropped/positioned at the wrong place compared to when file is downloaded and viewed through Chrome or Adobe Reader, which show the landscape and not just the bottom portion of the chair

What is the expected behavior? (add screenshot)
page 6 - http://www.screencast.com/t/kfdy2ftjIF
page 15 - http://www.screencast.com/t/nk6k6fLz4XI
What went wrong? (add screenshot)
page 6 - http://www.screencast.com/t/N9Pd9Hgha
page 15 - http://www.screencast.com/t/JndDKRYO8
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): https://cloud.box.com/s/3idigur8fepcqxto007ykhjca3w0x68i

I don't even see the top images on pages 6, 9 and 15 and both images on page 12 on Arch Linux, just blue squares. This may therefore also depend on the OS/browser version being used.

Oops, sorry forgot to add a step. If you don't do this step, you see the old viewer, which isn't on pdf.js.

Visit https://cloud.box.com/on/beta before any other URL

You're right, that resolves the mentioned issues for me. I do see only the cropping/positioning issue now.

Another example: https://privportfolio.app.box.com/s/lrtjiu6bpma0pvz2xmhnrmremcpi2i2k
Expected page 5 behavior (Chrome): https://www.screencast.com/t/XbU3f9St
Incorrect page 5 behavior (pdf.js): https://www.screencast.com/t/s6yy6TnZsy

Attached original PDF for posterity: 3203.pdf
This bug appears to be fixed by #6606.


typo: Spaces between Markdown link title and URL

@nschonni : Thanks for your contribution! The author, @HeidiSteen, has been notified to review your proposed change.

#sign-off thanks!


initial tmh.IDynamicLocale

hi, @lgalfaso, this is a simple type definition for tmhDynamicLocale as tmh.IDynamicLocale.
It currently creates the namespace tmh and the interface IDynamicLocale, with only two members: get and set. I think it's the minimal type definitions to work with typescript.

Hi, sorry for taking this long.
It would be nice to also get the type information for tmhDynamicLocaleProvider, but this is a good starts.

hi, @lgalfaso, I can take a look on tmhDynamicLocaleProvider when I have spare time.

Thanks!
On Mon, Jul 10, 2017 at 11:55 AM Gerardo Lima<EMAIL_ADDRESS>wrote:

hi, @lgalfaso https://github.com/lgalfaso, I can take a look on
tmhDynamicLocaleProvider when I have spare time.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lgalfaso/angular-dynamic-locale/pull/114#issuecomment-314060408,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAX44u1apS4FeFWqb0N4WSvI05gFRCJiks5sMfUYgaJpZM4OK6bj
.

Sorry, this will sound kind of silly but, I was trying to use angular-dynamic-locale on typescript but I cant seem to get it to work. I added the package, and tried to add tmhDynamicLocale as a service, but then on the component i tried to use it I get referenceError Angular is not defined.
Do you happened to have an example written on TS that I could look at?


Unexpected installation behavior of rail clone-source

When I run the developer installation instructions as written (running rail clone-source --package-file rail_packages.yml from within my top level rail directory), I end up with the rail ancillary packages (and rail_base!) as siblings to my rail directory.
This adds unforeseen clutter to my development area, and renders paths illogical where the classic "everything goes into the same src/ directory" behavior is expected.

Hmm.  This was the intended behavior.  It seemed natural to me to have them as siblings.-eOn Jun 27, 2023, at 7:36 PM, Olivia R. Lynn @.***> wrote:
When I run the developer installation instructions as written (running rail clone-source --package-file rail_packages.yml from within my top level rail directory), I end up with the rail ancillary packages (and rail_base!) as siblings to my rail directory.
This adds unforeseen clutter to my development area, and renders paths illogical where the classic "everything goes into the same src/ directory" behavior is expected.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

My intention was actually to have all the rail directories as siblings.    That just seems more logical to me, as they are all part of the same software release.On Jun 27, 2023, at 7:36 PM, Olivia R. Lynn @.***> wrote:
When I run the developer installation instructions as written (running rail clone-source --package-file rail_packages.yml from within my top level rail directory), I end up with the rail ancillary packages (and rail_base!) as siblings to my rail directory.
This adds unforeseen clutter to my development area, and renders paths illogical where the classic "everything goes into the same src/ directory" behavior is expected.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


add example:docker easy-container-mount-host-dir

Commit rules and code conventions are not observed.
Check with me on the Telegram.


perf: remove unnecessary chain rule and capture for 921180

921180 works fine without the chained rule. It still correctly counts and blocks duplicate HTTP parameters

The chain is not there because of detection. The chain is there to get the logdata correctly. It's a pattern we use quite a bit these days. Is the logging right without the chain if you have several parameters, but only 1 duplication (look for order of parameters).

@dune73 Everything works the same regardless of how many parameters there are and the ordering. Although now msg is empty and matched_data keeps on logging accept for some reason (As shown below), I'll push a fix in sec.
Nginx log before fix:
2024/08/06 15:34:19 [info] 263792#263792: *4 ModSecurity: Warning. Matched "Operator `Gt' with parameter `1' against variable `TX:paramcounter_ARGS_NAMES:test' (Value: `2' ) [file "/etc/modsecurity/coreruleset/rules/REQUEST-921-PROTOCOL-ATTACK.conf"] [line "445"] [id "921180"] [rev ""] [msg "HTTP Parameter Pollution ()"] [data "Matched Data: accept found within TX:paramcounter_ARGS_NAMES:test: 2"] [severity "2"] [ver "OWASP_CRS/4.6.0-dev"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "paranoia-level/3"] [tag "OWASP_CRS"] [tag "capec/1000/152/137/15/460"] [hostname "<IP_ADDRESS>"] [uri "/"] [unique_id "172292245930.753196"] [ref ""], client: <IP_ADDRESS>, server: _, request: "GET /?test=1&test=2 HTTP/1.1", host: "localhost:8080"
Apache log before fix:
[Tue Aug 06 15:33:49.523214 2024] [security2:error] [pid 263717:tid<PHONE_NUMBER>91936] [client <IP_ADDRESS>:33858] [client <IP_ADDRESS>] ModSecurity: Warning. Operator GT matched 1 at TX:paramcounter_ARGS_NAMES:test. [file "/etc/modsecurity/coreruleset/rules/REQUEST-921-PROTOCOL-ATTACK.conf"] [line "461"] [id "921180"] [msg "HTTP Parameter Pollution ()"] [data "Matched Data: accept found within TX:paramcounter_ARGS_NAMES:test: 2"] [severity "CRITICAL"] [ver "OWASP_CRS/4.6.0-dev"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "paranoia-level/3"] [tag "OWASP_CRS"] [tag "capec/1000/152/137/15/460"] [hostname "localhost"] [uri "/"] [unique_id "ZrG1veDAH1Gwyak25iJueAAAAEg"]
Nginx log after fix:
[Tue Aug 06 15:56:08.130991 2024] [security2:error] [pid 264290:tid<PHONE_NUMBER>44192] [client <IP_ADDRESS>:37830] [client <IP_ADDRESS>] ModSecurity: Warning. Operator GT matched 1 at TX:paramcounter_ARGS_NAMES:test. [file "/etc/modsecurity/coreruleset/rules/REQUEST-921-PROTOCOL-ATTACK.conf"] [line "461"] [id "921180"] [msg "HTTP Parameter Pollution (TX:paramcounter_ARGS_NAMES:test)"] [data "Matched Data: 2 found within TX:paramcounter_ARGS_NAMES:test: 2"] [severity "CRITICAL"] [ver "OWASP_CRS/4.6.0-dev"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "paranoia-level/3"] [tag "OWASP_CRS"] [tag "capec/1000/152/137/15/460"] [hostname "localhost"] [uri "/"] [unique_id "ZrG6-HpfNDnkDKy8BJvK6AAAAEA"]
Apache log after fix:
2024/08/06 15:54:25 [info] 264232#264232: *1 ModSecurity: Warning. Matched "Operator `Gt' with parameter `1' against variable `TX:paramcounter_ARGS_NAMES:test' (Value: `2' ) [file "/etc/modsecurity/coreruleset/rules/REQUEST-921-PROTOCOL-ATTACK.conf"] [line "445"] [id "921180"] [rev ""] [msg "HTTP Parameter Pollution (TX:paramcounter_ARGS_NAMES:test)"] [data "Matched Data: 2 found within TX:paramcounter_ARGS_NAMES:test: 2"] [severity "2"] [ver "OWASP_CRS/4.6.0-dev"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "paranoia-level/3"] [tag "OWASP_CRS"] [tag "capec/1000/152/137/15/460"] [hostname "<IP_ADDRESS>"] [uri "/"] [unique_id "172292366579.538854"] [ref ""], client: <IP_ADDRESS>, server: _, request: "GET /?test=1&test=2 HTTP/1.1", host: "localhost:8080"

Thanks for your extensive assessment. I realize the original implementation was broken (HTTP Parameter Pollution ()) and your fix is not fixing this. But I think you get rid of the bug via a simpler logging message and I think this is good enough. I'll let others formally approve this, but I am OK with the PR.

This is, probably, a leftover from the time when a rule was more complex.

@EsadCetiner Good catch, thanks!


Modifications/improvements

Hi, I have used this plugin for a project at my workplace and have had to support touch devices and IE9. Hence have made some modifications to support those better, and also one other change as per the request from our UX team. Sending in a pull request in case any of my changes are useful additions to the plugin. I am new to contributing, so if I need to do anything different, please let me know. Cheers!

@arathi-sreekumar Thanks for using the library and for contributing back your changes! It's preferred if you made the changes on different branches in different pull requests, since they are somewhat unrelated, so they can more easily be merged independently. I'm evaluating them now, but looks like these could help address #29 for touch zoom and #32 for IE9 scroll zoom.

@arathi-sreekumar I've merged b5d7753 into master branch, then modified afterwards. I forgot about the Event.scale property. Now that I recall it, I was able to simplify the pinch event handler significantly to not rely at all on Event.deltaX or Event.deltaY (9c9f736). Do you think this will work?

It might. I am not an expert on how much cross browser support or device support this will have. Also you might still need a ratio multiplier or it might zoom too much too soon.

@arathi-sreekumar With 239a914, can you provide more explanation what you're trying to accomplish? Seems like maybe the existing constrainZoomed option could already support your use case?

I didnt know what constrained zoom did, I'll give it a try and let you know if its the same as what I was trying to do.

I have also added some additional checks to prevent the image moving at all in the horizontal direction if its width is less than container width, and same for vertical. But this might not be needed as a generic solution in the plugin. This was just what our design team felt we needed.

Sorry, didn't notice that one. Will update it.

Released 2.1.4 to include some of these changes.

@arathi-sreekumar Thanks. Regarding the move constraining, I'd like any additional behaviors to be hidden behind options so they are at least configurable if not preferably opt-in.

@arathi-sreekumar Closing this for now, since I merged the stuff I thought was good and ready. We can handle the additional changes in future pull requests.


RFP - Samsung NVMExpress

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL :
https://www.samsung.com/semiconductor/minisite/ssd/download/tools/
Direct download URL for the software / installer :
https://s3.ap-northeast-2.amazonaws.com/global.semi.static/SamsungNVMExpressDriver3.3/7322A6707A720E1A71EF11A3BE1EED819E011D317626415F0281A78151C/Samsung_NVM_Express_Driver_3.3.exe
Software summary / short description:
Samsung Driver for M.2 NVMe drive. Made by Samsung.

Status: Review
https://chocolatey.org/packages/samsung-nvme-driver
@EpsilonsQc: It needs to have the drive connected to install the package so I am not able to test. Is it possible for you to uninstall your current driver, restart your computer and test this Chocolatey package:
choco install samsung-nvme-driver --pre --version="3.3"
If it doesn't work, you will have to re-install manually your Samsung NVMe driver.

@EpsilonsQc: It needs to have the drive connected to install the package so I am not able to test. Is it possible for you to uninstall your current driver, restart your computer and test this Chocolatey package:
choco install samsung-nvme-driver --pre --version="3.3"
If it doesn't work, you will have to re-install manually your Samsung NVMe driver.

Tried to install the package but the console gave me this error :
PS C:\Users\Epsilons> choco install samsung-nvme-driver --pre --version="3.3"
Chocolatey v0.10.15
samsung-nvme-driver
By installing you accept licenses for the packages.
Progress: Downloading samsung-nvme-driver 3.3... 100%

samsung-nvme-driver v3.3 - Possibly broken
samsung-nvme-driver package files install completed. Performing other installation steps.
Downloading samsung-nvme-driver
  from 'https://s3.ap-northeast-2.amazonaws.com/global.semi.static/SamsungNVMExpressDriver3.3/7322A6707A720E1A71EF11A3BE1EED819E011D317626415F0281A78151C/Samsung_NVM_Express_Driver_3.3.exe'
Progress: 100% - Completed download of C:\Users\Epsilons\AppData\Local\Temp\chocolatey\samsung-nvme-driver\3.3\Samsung_NVM_Express_Driver_3.3.exe (4.72 MB).
Download of Samsung_NVM_Express_Driver_3.3.exe (4.72 MB) completed.
Hashes match.
Installing samsung-nvme-driver...
ERROR: Running ["C:\Users\Epsilons\AppData\Local\Temp\chocolatey\samsung-nvme-driver\3.3\Samsung_NVM_Express_Driver_3.3.exe" /q ] was not successful. Exit code was '3010'. See log for possible error messages.
  samsung-nvme-driver may be able to be automatically uninstalled.
 The install of samsung-nvme-driver was successful.
  Software installed as 'exe', install location is likely default.

Chocolatey installed 1/1 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Packages requiring reboot:
 - samsung-nvme-driver (exit code 3010)

The recent package changes indicate a reboot is necessary.
 Please reboot at your earliest convenience.

@EpsilonsQc
Exit code was '3010', it means "Pending restart".
I added 3010 as valid exit code.
Could you try again?

Uninstall your current driver
Restart your computer
Test this Chocolatey package:
choco install samsung-nvme-driver --pre --version="3.3"
Test if the driver works as expected after the installation.

If it doesn't work, you will have to re-install manually your Samsung NVMe driver.

@chtof The installation worked flawlessly and this is what I received from the console (note that the last 2 lines were in bold red) :
Chocolatey v0.10.15
Installing the following packages:
samsung-nvme-driver
By installing you accept licenses for the packages.
Progress: Downloading samsung-nvme-driver 3.3... 100%

samsung-nvme-driver v3.3 - Possibly broken
samsung-nvme-driver package files install completed. Performing other installation steps.
Downloading samsung-nvme-driver
  from 'https://s3.ap-northeast-2.amazonaws.com/global.semi.static/SamsungNVMExpressDriver3.3/7322A6707A720E1A71EF11A3BE1EED819E011D317626415F0281A78151C/Samsung_NVM_Express_Driver_3.3.exe'
Progress: 100% - Completed download of C:\Users\Epsilons\AppData\Local\Temp\chocolatey\samsung-nvme-driver\3.3\Samsung_NVM_Express_Driver_3.3.exe (4.72 MB).
Download of Samsung_NVM_Express_Driver_3.3.exe (4.72 MB) completed.
Hashes match.
Installing samsung-nvme-driver...
samsung-nvme-driver has been installed.
  samsung-nvme-driver may be able to be automatically uninstalled.
 The install of samsung-nvme-driver was successful.
  Software installed as 'exe', install location is likely default.

Chocolatey installed 1/1 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Packages requiring reboot:
 - samsung-nvme-driver (exit code 3010)

The recent package changes indicate a reboot is necessary.
 Please reboot at your earliest convenience.

@EpsilonsQc Is the driver working as expected with the disk after the installation and the required reboot?

@EpsilonsQc Is the driver working as expected with the disk after the installation and the required reboot?

@chtof yes.


Inverse quantile algorithm is non-contiguous

Not only it gives strange results at the end (and indeed, python implementation fixes that; sorry, not fluent at Java), but also the ranges that are covered as q goes up are non-contiguous.
I propose the following changes:
t <- 0, q <- $1 + q (\sum c_i.count - 1)$
for i <- 1..m
  if q \leq t + c_i.count
    if i = 1 : return c_i.mean
    if i = m : return c_i.mean
    low <- (c_{i-1}.mean + c_i.mean)/2
    high <- (c_{i+1}.mean + c_i.mean)/2
    return low + (high - low) * (q - t)/c_i.count

This has the property of being contiguous and returning precise values for $q = 0, 1$.

I think that this algorithm doesn't account for situations with small
counts well. Whenever a centroid has a single sample, we know that the
quantile increments discontinuously exactly at the mean value for the
centroid.
Also, there are two approaches for thinking about quantiles in a q-digest
framework. In one approach (yours), the thought is that the samples for a
centroid are uniformly spaced from some minimum value to a maximum value.
The question becomes how we decide what the minimum and maximum are. One
way to do this is to assume that the extent of a centroid on one side is
proportional to the number of samples in that centroid, scaled by the total
number of samples in that centroid and the next centroid on that side. Note
that the centroid will no longer necessarily be in the center of this
distribution. I think it is also good practice to account for a small gap
between centroids which also coincidentally deals with the fact that n
samples should properly be considered to be n-1 units wide.
The second approach would be to consider the samples to be uniform between
centroids. This means that we know what the upper and lower bounds are. We
can then assume that there are (n_left -1)/2 + (n_right - 1)/2 samples plus
a gap.
Which approach is better is not clear to me.
On Mon, Sep 19, 2016 at 5:29 PM, Alexander Sedov<EMAIL_ADDRESS>wrote:

Not only it gives strange results at the end (and indeed, python
implementation fixes that; sorry, not fluent at Java), but also the ranges
that are covered as q goes up are non-contiguous.
I propose the following changes:
t <- 0, q <- $1 + q (\sum c_i.count - 1)$
for i <- 1..m
if q \leq t + c_i.count
if i = 1 : return c_i.mean
if i = m : return c_i.mean
low <- (c_{i-1}.mean + c_i.mean)/2
high <- (c_{i+1}.mean + c_i.mean)/2
return low + (high - low) * (q - t)/c_i.count
This has the property of being contiguous and returning precise values for
$q = 0, 1$.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tdunning/t-digest/issues/72, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPSeiXRTQn94Wu_w-a1uSu1hF-0xGPMks5qrqpGgaJpZM4KAn8h
.

That’s all fine and dandy, but your formulae don’t reflect your approach of it being uniform between centroids, as you still center it on the centroid.
And while I can understand it being non-contiguous, it being non-monotonic (which it currently is) is completely beyond me.

20 сент. 2016 г., в 14:38, Ted Dunning<EMAIL_ADDRESS>написал(а):
I think that this algorithm doesn't account for situations with small
counts well. Whenever a centroid has a single sample, we know that the
quantile increments discontinuously exactly at the mean value for the
centroid.
Also, there are two approaches for thinking about quantiles in a q-digest
framework. In one approach (yours), the thought is that the samples for a
centroid are uniformly spaced from some minimum value to a maximum value.
The question becomes how we decide what the minimum and maximum are. One
way to do this is to assume that the extent of a centroid on one side is
proportional to the number of samples in that centroid, scaled by the total
number of samples in that centroid and the next centroid on that side. Note
that the centroid will no longer necessarily be in the center of this
distribution. I think it is also good practice to account for a small gap
between centroids which also coincidentally deals with the fact that n
samples should properly be considered to be n-1 units wide.
The second approach would be to consider the samples to be uniform between
centroids. This means that we know what the upper and lower bounds are. We
can then assume that there are (n_left -1)/2 + (n_right - 1)/2 samples plus
a gap.
Which approach is better is not clear to me.
On Mon, Sep 19, 2016 at 5:29 PM, Alexander Sedov<EMAIL_ADDRESS>wrote:

Not only it gives strange results at the end (and indeed, python
implementation fixes that; sorry, not fluent at Java), but also the ranges
that are covered as q goes up are non-contiguous.
I propose the following changes:
t <- 0, q <- $1 + q (\sum c_i.count - 1)$
for i <- 1..m
if q \leq t + c_i.count
if i = 1 : return c_i.mean
if i = m : return c_i.mean
low <- (c_{i-1}.mean + c_i.mean)/2
high <- (c_{i+1}.mean + c_i.mean)/2
return low + (high - low) * (q - t)/c_i.count
This has the property of being contiguous and returning precise values for
$q = 0, 1$.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tdunning/t-digest/issues/72, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPSeiXRTQn94Wu_w-a1uSu1hF-0xGPMks5qrqpGgaJpZM4KAn8h
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/tdunning/t-digest/issues/72#issuecomment-248276857, or mute the thread https://github.com/notifications/unsubscribe-auth/AAW_XUeZAIo8lMWtoh3tRg0jC0Jq3OKSks5qr8W_gaJpZM4KAn8h.

On Tue, Sep 20, 2016 at 1:56 PM, Alexander Sedov<EMAIL_ADDRESS>wrote:

it being non-monotonic (which it currently is) is completely beyond me.

non-monotonic is not the intent.
Need to check that.

Alex,
The latest implementation is considerable better behaved. I am working towards a release soon and will include a test for your pathology.
The new quantile/cdf algorithm uses the following diagram as an intuitive basis:

The fundamental idea here is that the solid red line represents our desired result. At the extremes, we interpolate between the first (or last) centroid and the recorded min and max values ever seen. It is assumed that each centroid is collocated with the median of the original data for the centroid and that the data is uniformly distributed between the centroids.
By definition, this form should give monotonic functions for both x -> quantile and quantile -> x.


Initial Landing Page

Create an initial landing page with a description of the project for users to view and understand the project.

@sachindumalshan I created a task for you. I will give you the info.


Forbid nesting a Track into a Track or automatically insert a Stack in between

Feature Request
Proposed Change to existing Behavior
Description
Appending a Track into a Track makes no sense if a Stack isn't inserted as a parent of an appended Track.
We could either decide to forbid appending a Track to a Track or automatically insert a Stack in between.
Context
from opentimelineio.schema import Track

track = Track()
track.append(Track())  # This shouldn't be allowed

track.append(Stack(Track()))  # This could be automatically done

Why should inserting a track inside a track be an error?  We allow nesting both tracks inside tracks and stacks inside stacks.

Yes I know you allow it, I'm just raising that it doesn't make sense to me, for the Track > Track for sure, not sure about the Stack > Stack.
How would you represent into an editing software to have a Track inside a Track? In an architecture schema?

This has examples of nested compositions:
https://opentimelineio.readthedocs.io/en/latest/tutorials/otio-timeline-structure.html
I don't see one on there for a track with a nested track specifically, but we could add that.  A track contains a sequence of items ordered in time such that one follows the next.  One of those items could itself be a track containing more items sequentially ordered in time.
Some examples from third party NLEs:
Documentation for premiere pro on nested sequences:
https://helpx.adobe.com/premiere-pro/how-to/premiere-pro-nesting-sequence-cc.html
Looks like FCPX calls them 'compound clips':
https://support.apple.com/guide/final-cut-pro/intro-to-compound-clips-verbbd3496b/mac

Here is a relevant unit test:
https://github.com/PixarAnimationStudios/OpenTimelineIO/blob/b566b316b2fa4cb9254f0b5d4af4ed636513d0d3/tests/test_composition.py#L1144

Media composer calls them "single layer submaster".

Ah yes, here: https://resources.avid.com/SupportFiles/attach/MCEffects.pdf
search for "submaster"

I completely understand what you mean, but all your examples show a Stack having several Tracks with their clips and put inside a "bigger" Track. That's my original point, saying: "I wantTracks into a Track" would actually mean "I want a Track to contain a Stack with numerous Tracks in it".
That being said, we could consider a Track is a Stack with only one single Track in it, but to me, it's open to interpretation and then error-prone.
After some thoughts, storing a Stack into a Stack has the same conceptual problem, as a Stack refers to something with layers (= Track) then being able to have a Clip or a Stack directly in a Stack is quite the same as wanting to append a Clip to another Clip.
If you append two Clips to a Stack, which one should be displayed? By order of appending? Is this supposed to represent layers, then Tracks? If yes, why not having actual Track between the Stack and the Clip? I may want to mean: "If two clips are in a stack, they are supposed to be mixed in equality, every pixel takes 50% of each clip, or we addition the pixels values as it does for sound...", and then I must have a "rule" of compositing for video clips into a Stack. Forcing to have a Track inside a Stack before adding any entity makes it, IMO, stronger.

That's my original point, saying: "I want Tracks into a Track" would actually mean "I want a Track to contain a Stack with numerous Tracks in it".
These are two separate concepts to us.  A stack and a track both compose their children in time.   Having a stack with three clips in it rather than three tracks each with one clip would render to the same thing but could mean something different organizationally.  You could also have two clips and a track containing three more clips in order.  Similarly, a track could contain three clips, or three tracks each that contain one clip, or three stacks that contain a track that contain a clip.  These all could mean different things depending on a workflow but flatten/render to the same result.  Each intermediate scope could have effects and metadata placed on it, for example.

If you append two Clips to a Stack, which one should be displayed?
This is well defined.  Unfortunately, when we ported to C++ we lost some of the verbose documentation that was embedded in the pydocs.  I think there is an issue to bring the documentation back?  @reinecke might know.   In any case, this explains the compositing order of a stack:
https://github.com/PixarAnimationStudios/OpenTimelineIO/blob/cc78a7c5e9b10808d524edd00a09f8a11b21ce1a/opentimelineio/schema/stack.py#L32

It would be good to ensure that this is somewhere in RTD as well, but I'm a bit short on time.

Is this supposed to represent layers, then Tracks?
Stacks and Tracks both can contain child tracks, stacks, clips and gaps.  Tracks can additionally contain transitions.  Each of these objects has a temporal coordinate system and a well defined (hopefully) way of interpreting further nesting.  So the contents of a stack are objects with a temporal coordinate system whose starting coordinate lines up with the start of the track.  They could be tracks, with further sequencing, or just clips.

Might be easier to discuss on slack or in a TSC meeting, in real time.

I think the summary you came up with, "stacks are temporarily coincident (i.e. things that start playing at the same time)" and "tracks are temporally adjacent (i.e. things that play one after the other, with a sneaky twist for blends)" is a really nice way to summarize it. This conception allows thinking more easily about a timeline composition as a flow graph. The choice of the terms "track" in particular in retrospect is probably not as good a term as "sequence". Tracks in OTIO coincidentally look an awful lot like a track in an NLE, but the term doesn't necessarily frame the data structure intuitively, or correspond to a track in an NLE. "OTIO Stacks group things that start at the same time, Tracks group things that start one after the other" really helps.

I think there is an issue to bring the documentation back? @reinecke might know.

There is one I believe yes. BTW, I've been doing work on the python docs, and bringing back the docs that was lost in translation is part of the things I'm working on.

Awesome!  That will be a huge help!  Thanks!

"stacks are temporarily coincident (i.e. things that start playing at the same time)" and "tracks are temporally adjacent (i.e. things that play one after the other, with a sneaky twist for blends)"

"OTIO Stacks group things that start at the same time, Tracks group things that start one after the other"

I agree this helps a lot and completely makes sense. My first wonder was because I was thinking about it spatially, like a bookshelf, where the Stack is the support and the Track is the shelf, then putting a shelf on a shelf doesn't make sense and may require a support first. I came up with that because that's how NLE editors represent the editing.
Actually, putting it in a time based approach makes more sense. Thinking about Track like a music track, with events following each others is helpful.
I still think this gives too much freedom to implementation in different softwares and then weakens the standard, but I don't know if this is something we could completely get rid of.
I agree the doc lacks of description, use cases and examples. But this is something which takes time and the whole thing is still young.
No problem to further discuss it on Slack or in live.

It might be helpful to share a little more background on the design choices that lead to how OTIO is now. We considered several different options on how the composition structure works when designing Timeline, Stack, and Track.
In one extreme which is most similar to how NLE user interfaces are presented, Timeline and Stack could be the same thing, (e.g. a Timeline has a list of Tracks) and the schema could be limited so that Tracks only ever appear as direct children of a Timeline. This would mean that any nesting would be accomplished by adding a Timeline as an item within a Track, and the nested Timeline would always have a list of Tracks (starting with just 1). In the terms of our class hierarchy, Timeline would then be a subclass of Composable (and an Item, I think).
In the other extreme, which is what we chose for OTIO, the notion of Track and Stack are kept separate, and each of those two classes is only responsible for the way their child items are composed. Tracks arrange their children sequentially in time (in fact we renamed "Sequence" to "Track" early on). Stacks arrange their children vertically for compositing (video), or summation (audio). The only functional difference between the two is in the duration() computation, and the range_of_child() computation.
We chose to go with the 2nd approach on the basis that there would be other scenarios where these concepts would be useful to reuse, and that the composition logic would be simpler to implement and reason about. We saw the node graph within RV as a good example of this. RV has "Sequence" and "Stack" objects in their graph.
In practice, we've seen cases with EDL-based tools, and some of our in-house playback tools where nesting is available but there is only 1 media track, and so nesting a Track within a Track comes up there - though it could be accommodated in the other design as well. We have also considered situations like multi-cam clips, or representations of the streams within a single media file, where these choices could be reconsidered.

Joshua Minor (he-him)
OpenTimelineIO Technical Steering Committee Chairperson
@.***

On Dec 9, 2021, at 1:00 AM, Félix David @.***> wrote:
"stacks are temporarily coincident (i.e. things that start playing at the same time)" and "tracks are temporally adjacent (i.e. things that play one after the other, with a sneaky twist for blends)"
"OTIO Stacks group things that start at the same time, Tracks group things that start one after the other"
I agree this helps a lot and completely makes sense. My first wonder was because I was thinking about it spatially, like a bookshelf, where the Stack is the support and the Track is the shelf, then putting a shelf on a shelf doesn't make sense and may require a support first. I came up with that because that's how NLE editors represent the editing.
Actually, putting it in a time based approach makes more sense. Thinking about Track like a music track, with events following each others is helpful.
I still think this gives too much freedom to implementation in different softwares and then weakens the standard, but I don't know if this is something we could completely get rid of.
I agree the doc lacks of description, use cases and examples. But this is something which takes time and the whole thing is still young.
No problem to further discuss it on Slack or in live.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/PixarAnimationStudios/OpenTimelineIO/issues/1171#issuecomment-989645112, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABJM76RUQ5EVDLY6LARBVDUQBVZRANCNFSM5JUGXXJA.

Hi @Tilix4 - did this discussion help to clarify how OTIO works? If so, I'm inclined to close this issue, but I wanted to check with you first.

Hi @jminor, it actually helped yes, thanks!


allow initialization of resources before starting server

Connected to #474.

@0xbase12: Please check that this implementation of the resource initialization will work for you.  In particular, the initialization will take place before the server is started; this presumes that in the initialization, no calls to the server itself are done. There's also quite a bit of refactoring in anticipation of the namespace loading being used for other purposes.


Help in Handling Exceptions with SPQR

Hello @kaqqao / SPQR team,
I am trying to implement SPQR in my project, it is a great tool that allows running graphql without schema.
I am having an issue in configuring exception handling with this. I went through all the issues/examples and found some solutions. But don't know that is not working.
See, here is how I configured my graphQL
@Autowired
    public GraphqlController(BookResolver bookResolver) {
        GraphQLSchema schema = new GraphQLSchemaGenerator()
                .withBasePackages("com.graphql.learn")
                .withOperationsFromSingleton(bookResolver)
                .generate();
        this.graphQL = new GraphQL.Builder(schema)
                .queryExecutionStrategy(new AsyncExecutionStrategy(new CustomExceptionHandler()))
                .mutationExecutionStrategy(new AsyncExecutionStrategy(new CustomExceptionHandler()))
                .build();
    }
    @PostMapping(value = "/graphql")
    public Map<String, Object> execute(@RequestBody Map<String, String> request, HttpServletRequest raw)
            throws GraphQLException {
        ExecutionResult result = graphQL.execute(request.get("query"));
        return result.getData();
    }

This is the resolver I made (Here, I am intentionally throwing an exception)
@GraphQLQuery
    public List<Book> books(){
        if(true){
            throw new NullPointerException("Null pointer exception");
        }
        return bookService.getAll();
    }

And Here is how I created CustomExceptionHandler
 @Component
public class CustomExceptionHandler implements DataFetcherExceptionHandler {

    private DataFetcherExceptionHandlerResult onExceptionHandler(DataFetcherExceptionHandlerParameters handlerParameters) {

        Throwable exception = handlerParameters.getException();

        // do something with exception

        GraphQLError error = GraphqlErrorBuilder
                .newError()
                .message(exception.getMessage())
                .build();

        return DataFetcherExceptionHandlerResult
                .newResult()
                .error(error)
                .build();
    }

    @Override
    public CompletableFuture<DataFetcherExceptionHandlerResult> handleException(DataFetcherExceptionHandlerParameters handlerParameters) {
        DataFetcherExceptionHandlerResult result = onExceptionHandler(handlerParameters);
        return CompletableFuture.completedFuture(result);
    }
}

**And Here What I get for the query result **

Request

query{
    books{
        id,
        title
    }
}

Response

{
    "books": null
}

Please show me how can I configure in a way so that I get proper exception message in response.
To get the access of whole implementation you can refer to this branch -> https://github.com/Hardikraja/graphql-learning/tree/with-spqr

Thanks.

I found the answer of the above question,
@PostMapping(value = "/graphql")
    public Map<String, Object> execute(@RequestBody Map<String, String> request, HttpServletRequest raw)
            throws GraphQLException {
        ExecutionResult result = graphQL.execute(request.get("query"));
        return result; // it should return executionResult as it is
    }

Earlier, I was returning executionResult.getData() instead of executionResult - that is why it was not working.
Thanks.


Android compute particles sample not working properly

There's an issue where the particle simulation on Android does not work properly on initial startup. It's probably due to invalid handling of the app life-cycle.
Current workaround to get the simulation running properly is to simply suspend and resume the sample. For example:

Start the sample app
Navigate to another app
Navigate back to the sample app

Is there anything else to look out for? Can't seem to get any of the examples to run on my Nougat test device (which runs other non-Vulkan apps in Debug mode fine). It flashes the screen for a second and then closes. I tried putting breaks in OnCreate(0 and Initialize(), but doesn't get there. Navigating to another app and back doesn't help either.

Are you testing on a physical device or emulator? If physical, which device more specifically?

Hey, yeah it's a physical device. Huawei Honor 8.


Colab feature_columns.ipynb cannot save and reload Keras model

Gist issue from Colab feature_columns.ipynb
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version (use command below):
Python version:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
2020-11-03 01:52:53.863478: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
v2.3.0-0-gb36436b087 2.3.0

Describe the current behavior
Cannot reload a model saved in keras format
ValueError: You are trying to load a weight file containing 4 layers into a model with 0 layers.

Describe the expected behavior
Being able to reload the previously saved model
Standalone code to reproduce the issue
gist
Steps:

Run Colab feature_columns.ipynb
Add one cell

model.save('pet_finder.h5', include_optimizer=False)
reload_keras_model = tf.keras.models.load_model('pet_finder.h5')

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-75-876b76fb8d70> in <module>()
      1 model.save('pet_finder.h5', include_optimizer=False)
----> 2 reload_keras_model = tf.keras.models.load_model('pet_finder.h5')
      3 loss, accuracy = reload_keras_model.evaluate(test_ds)
      4 print("Accuracy", accuracy)

2 frames
/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/saving/hdf5_format.py in load_weights_from_hdf5_group(f, layers)
    684                      'containing ' + str(len(layer_names)) +
    685                      ' layers into a model with ' + str(len(filtered_layers)) +
--> 686                      ' layers.')
    687
    688   # We batch weight value assignments in a single backend call

ValueError: You are trying to load a weight file containing 4 layers into a model with 0 layers.

Thank you.

@Silb78dg
Please share the tf version used

It's in the description
2020-11-03 01:52:53.863478: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
v2.3.0-0-gb36436b087 2.3.0

tf 2.3.0. That the version in Colab.
I can also reproduce locally with tf version 2.3.1.
Thank you.

@Silb78dg
Please share a simple stand alone code such that we can replicate the issue faced or if possible share a colab gist with the issue reported.

@Saduf2019 Don't you have access to the gist I already shared?

@Silb78dg
We ask for simple stand alone code such that we can replicate the issue faced, or if possible share a gist with the code and the error reported.

@Saduf2019 I don't understand.
Have you ever read the description?
I have provided the gist link twice!
Can you please tell me if you have access to the link I provided in the first line of the description (the gist's link not the colab's link)?
Just in case, I can provided again: https://colab.research.google.com/gist/Silb78dg/ec40d3472e6b67ad399c24320d671973/feature_columns.ipynb
What can be better than a bug reproduced using a tutorial? If we don't make the tutorial working properly, that is a really poor user experience.

@ymodak
I am able to replicate the error reported, Please find the gist here.

Saving your model in default tf format  and loading is successful.
model.save('pet_finder', include_optimizer=False)
reload_keras_model = tf.keras.models.load_model('pet_finder')


Groups works incorrect

What steps will reproduce the problem?
Add into RouterFactory
        $router = (new RouterFactory(new FastRouteFactory(), $routes))($container);
        $router->addGroup('/blog', static function (RouteCollectorInterface $r) use (&$container) {
            $r->addRoute(
                Route::get('/index')
                     ->to(new ActionCaller(SiteController::class, 'index', $container))
                     ->name('blog/index')
            );
        });
        return $router;

Go to /blog/index
What is the expected result?
Response with HTTP 200 and index page
What do you get instead?
Response with HTTP 405
Additional info
Works strange with next code:
$router->addGroup('/blog', ... $r->addRoute(Route::get('/') ...) # /blog/

Performs as path /

Related to yiisoft/router#16


mup failing with Error: spawn ENOENT since 0.10.8

I have this problem since 0.10.8, I've reverted back to 0.10.7 and it works, so my directories are named correctly.
| => node -v
v0.10.36
`Meteor Up: Production Quality Meteor Deployments
“ Checkout Kadira!
It's the best way to monitor performance of your app.
Visit: https://kadira.io/mup ”
Building Started: /Users/zzzzzzzz/workspace/zzzzz-mobile/mobile
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:1011:11)
at Process.ChildProcess._handle.onexit (child_process.js:802:34)

| ~/workspace/zzzzz-mobile/mobile @ Clarences-MacBook-Pro (zzzzzzzz)
| => sudo npm install -g<EMAIL_ADDRESS>| ~/workspace/zzzzz-mobile/mobile @ Clarences-MacBook-Pro (zzzzzzzz)
| => mup deploy
Meteor Up: Production Quality Meteor Deployments
“ Checkout Kadira!
It's the best way to monitor performance of your app.
Visit: https://kadira.io/mup ”
Building Started: /Users/zzzzzzzz/workspace/zzzzz-mobile/mobile
The Android platform is not installed; skipping build for it.
Started TaskList: Deploy app 'zzzzz-mobile' (linux)
[xxx.xxx.xxx.xxx] - Uploading bundle
[xxx.xxx.xxx.xxx] - Uploading bundle: SUCCESS
[xxx.xxx.xxx.xxx] - Setting up Environment Variables
[xxx.xxx.xxx.xxx] - Setting up Environment Variables: SUCCESS
[xxx.xxx.xxx.xxx] - Invoking deployment process
[xxx.xxx.xxx.xxx] - Invoking deployment process: SUCCESS
`

I've tried to match your environment, but unfortunately, I'm still getting the same error you had, even with mup 0.10.7. I'm wondering if the way you solved this was related to something else?
# mup deploy

Meteor Up: Production Quality Meteor Deployments
------------------------------------------------

“ Checkout Kadira!
  It's the best way to monitor performance of your app.
  Visit: https://kadira.io/mup ”

Building Started: /root/zoomlisting

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:1011:11)
    at Process.ChildProcess._handle.onexit (child_process.js:802:34)

I'm using node 0.10.36, ubuntu 14.04, and mup 0.10.7.

Also, I tried looking at the logs, but unfortunately, this is what comes up:
[x.x.x.x] tail: cannot open ‘/var/log/upstart/zoomlisting.log’ for reading[x.x.x.x] : No such file or directory

Maybe check if upstart is installed via?
initctl --version

Yep, upstart is installed.

Does the path to the log file that's missing exist too?
/var/log/upstart/*.log
try...
mkdir -p /var/log/upstart

Yep, I tried that, no dice.
root@xxx:~/xxx# mupx deploy

Meteor Up: Production Quality Meteor Deployments
------------------------------------------------
Configuration file : mup.json
Settings file      : settings.json

“ Checkout Kadira!
  It's the best way to monitor performance of your app.
  Visit: https://kadira.io/mup ”

Meteor app path    : /root/xxx
Using buildOptions : {}
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: spawn meteor ENOENT
    at exports._errnoException (util.js:746:11)
    at Process.ChildProcess._handle.onexit (child_process.js:1053:32)
    at child_process.js:1144:20
    at process._tickCallback (node.js:355:11)
    at Function.Module.runMain (module.js:503:11)
    at startup (node.js:129:16)
    at node.js:814:3

I switched to mupx, and I'm still seeing this message.

hmm, this is the only result on google for this error. I wonder what to do.

Yeah, I was still seeing this when I tried deploying on DO. I'm thinking either of trying a different VPS provider or manually using a Docker container.

I got mine fixed when tried to just run the app with meteor, the way you would on your local machine. Turned out I hadn't set my locale and MongoDB couldn't start. I suggest you run meteor too.

Most people have had app path issues relating to this ENOENT ("no file or directory") error.
Usually it's wrong or not fully qualified, maybe permissions, etc?

Ya tried every version of the, even a relative one. Permissions, maybe if under the hood it was running under a different user, but sudo didn't work either.
I now have this issue again with Meteor 1.2

I found a workaround, and it's a pain, so here goes - it involves hacking your mup files a bit each time unfortunately.
look in build.js - line 34 is the culprit
var meteor = spawn(executable, args, options );

if you console log that you will see
/usr/local/bin/meteor --debug [ 'build',
  '--directory',
  '/var/folders/g2/sjmmz3w13q54sgwfbwnxjh_00000gn/T/58659e57-d261-4e29-9db1-d52f1b586f8c',
  '--server',
  'http://localhost:3000' ] { pwd: '/Users/clarencel/workspace/liveaudit/liveaudit/' }

If you know the NodeJS spawn function, basically it's calling:
/usr/local/bin/meteor --debug build --directory /var/folders/g2/sjmmz3w13q54sgwfbwnxjh_00000gn/T/58659e57-d261-4e29-9db1-d52f1b586f8c --server http://localhost:3000

With the options set to {cwd: Your mup.json 'app' field}
Now here's the weird part! I can go to my app directory, and run that command directly and it works!

Ok so how do we get it to work?  Basically every time mup starts it'll build the bundle in that directory, now, each time that folder is different:
actions.js - line 104
var buildLocation = path.resolve(os.tmpdir(), uuid.v4());

It uses a uuid.v4(), your os.tmpdir() won't change during a process so you can leave that alone, but change the uuid.v4() to something static, I used clarencel-meteor
Literally hacking
// use whatever static folder you want
var buildLocation = path.resolve(os.tmpdir(), 'clarencel-meteor');

Ok now save that file, then go to your command line, from your app directory, run that command earlier to bundle it, but this time use your folder name
/usr/local/bin/meteor --debug build --directory /var/folders/g2/sjmmz3w13q54sgwfbwnxjh_00000gn/T/clarencel-meteor --server http://localhost:3000

That should work, and hey if it doesn't, it'll tell you exactly why the build didn't work! I actually had accidentally added the android platform, and didn't have ANDROID_HOME setup, so I just removed that platform, alas mup didn't work, so must be something else. But I didn't dwell on that much longer, who cares if I can get that above command to bundle, I'm set.
Ok so now you have the bundle built and in that folder
Now I hacked mup, to NOT build the bundle
  // comment all this out
  /*
  var options = {cwd: appPath};
  var meteor = spawn(executable, args, options);
  var stdout = "";
  var stderr = "";

  meteor.stdout.pipe(process.stdout, {end: false});
  meteor.stderr.pipe(process.stderr, {end: false});

  meteor.on('close', callback);
  */
  callback(0);

Normally it'll spawn the process call meteor build, wait for it to finish and then call the callback, 0 on success. So we'll just skip straight to that.
If you followed this properly it should work now, or at least you can run the build process separately and troubleshoot there.

If there's something I can test to see why that command works directly in the term, but not through NodeJS's spawn that'd be awesome. I'm on v0.10.40 too.

You can use SSH to access the deployment server and execute manually stepping through the scripts etc to track down errors.

I've narrowed it down the to the debug switch, in the term:
/usr/local/bin/meteor --debug build --directory /var/folders/g2/sjmmz3w13q54sgwfbwnxjh_00000gn/T/58659e57-d261-4e29-9db1-d52f1b586f8c --server http://localhost:3000
works, however in mup the --debug flag there breaks it, maybe the order, it should come after build? But I don't have access to the spawn args array.

Verified it is the order of build and --debug, so apparently before Meteor 1.2 - I could put in the mup.json
"meteorBinary": "/usr/local/bin/meteor --debug"

However now that no longer works for some reason, I have added a pull request to mup, for the debug flag, which I added, setting "debug": true, will achieve the same thing now.

It could be disabling ECMAScript works to help here, but it will eventually be fixed (by meteor I belive) so updating meteor should eventually fix this problem.


Track panic in Unit early.

This is an alternate solution for #5445. It ensures that panic is cleared in the Profile for "for_host" targets (proc-macro/plugin/build-scripts) and dependencies. This helps avoid unnecessary recompiles in some situations (though does add extra units in some situations, see below).
Some examples where extra rebuilds are now avoided:

A workspace with a dependency shared with normal and build-deps.  build --all should build everything, and then build -p foo was causing a recompile because the shared dep was no longer in the used_in_plugin set. Now it should not recompile.
panic=abort, with a shared dependency in build and dev, build would cause that shared dependency to be built twice (exactly the same without panic set). Now it should only build once.

Some examples where panic is now set correctly:

panic=abort, with a binary with a shared dependency in build and normal, test would cause that shared dependency to be built twice (exactly the same without panic set).  Now it is still built twice, but the one for the normal (bin) dependency will correctly have panic set.

Some examples where new units are now generated:

panic=abort, with shared dependency between normal and proc-macro or build. Previously the shared dependency was built once with panic=unwind. Now it is built separately (once with panic, once without). I feel like that this is more correct behavior — that now the normal dependency avoids adding landing pads.
For panic=abort cross-compiling, this makes no difference in compile time since it was already built twice.

Additional notes:

I left build-scripts with the old behavior where panic is cleared for it and all its dependencies. There could be arguments made to change that (#5436), but it doesn't seem important to me.
Renamed and refactored ProfileFor to UnitFor. I expect this API to continue to evolve in the future.

Closes #6143, closes #6154.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+
These seem like good tradeoffs to me and good to fix these bugs, thanks so much for digging into this @ehuss!

:pushpin: Commit 86489946d0828af1617ba921d3cc16146a9e0e53 has been approved by alexcrichton

:hourglass: Testing commit 86489946d0828af1617ba921d3cc16146a9e0e53 with merge 571a542639e59bb9dc7f6624367afb008d0d86c8...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 571a542639e59bb9dc7f6624367afb008d0d86c8 to master...


ConsumerMessage.delivery and .basic_properties should not be options

A message can carry no payload but it will always have delivery metadata (e.g. delivery tag) and its own metadata (basic properties). So it does not make sense to use Option<t> for them.

Yes, see #68

OK, I'll assume this is a duplicate.


Event time sending failure

Hi!
I found out that a lot of events i'm sending through CAPI via my server side GTM implementation are failing, and i pinpointed the issue to the event_time parameter.
It seems that a lot of clients are sending timestamps (generated by the getTimeMillis() / 1000 in the event params) in the future.
Is this a common issue that can be mitigated in some way?
Thanks!

Hi @Zsavajji!
I got the same error message many times in Facebook's Events Manager. However, when I looked at the total events affected, it was always < 1% of the total events, so I assumed they were caused by networking / connectivity issues when sending the event data instead of a bug with getTimestampMillis().
Is that your case? Could you please show an screenshot of the error you are seeing in Events Manager or elsewhere?
Thanks a lot!

I am not seeing errors in the events manager, in fact I am looking for the root cause of a mismatch in the report of Purchase events of an ecommerce website which we manage. There is a big discrepancy between the number of purchase events reported to Google Analytics and the number of purchase events registered by the FB business manager.
The trigger is attached to the same frontend event, so i don't really understand where it's losing this information.
BTW, the error I am seeing is easily visualized by putting a log when the CAPI response is not 200 in the tag template.
Since the GTM implementation gets no body when the request fails, i made some requests with the same payloads and they failed with "Provided timestamp is in the future".

There is a big discrepancy between the number of purchase events reported to Google Analytics and the number of purchase events registered by the FB business manager.
Please be aware that Google Analytics and Facebook have different attribution models. While Facebook will count a Purchase anytime the user clicked on an ad before ordering (in a given time window), Analytics will only attribute that order to Facebook if, of all the channels the user came from to our website, Facebook is the last one non-direct. This used to be the default behavior, not sure if now it's different. Also, Facebook and Analytics could have different attribution time windows too. I would dare to say that your discrepancies are more likely caused because of that than the event_time error.

That said, it's true that I can also see some errors on Facebook Events Manager about timestamp being in the future. As they were really scarce, I assumed it was a network/connectivity error as I said, but I'll investigate this issue further. What I don't understand is how can you repeat the same payload and get "Provided timestamp is in the future", when you actually used the same payload so the event_time should be from the past. If you are able to reproduce that error, could you copy-paste the event_time in this website and check which date it returns?
Thank you a lot for your time and help, btw!

Please be aware that Google Analytics and Facebook have different attribution models. While Facebook will count a Purchase anytime the user clicked on an ad before ordering (in a given time window), Analytics will only attribute that order to Facebook if, of all the channels the user came from to our website, Facebook is the last one non-direct. This used to be the default behavior, not sure if now it's different.

So you're telling me that the orders reported in the business manager are only the orders coming from an AD attribution and not all the orders made by my customers? I'm no analytics specialist so i don't know for sure :)
By the way, i could reproduce it because some of the timestamps are WAY more in the future than it could be caused from networking errors, i'm talking from 10mins to half an hour. I guess that since the timestamps are made in the client container they could be indicators of wrong time settings of the client itself.
Thank you!

So you're telling me that the orders reported in the business manager are only the orders coming from an AD attribution and not all the orders made by my customers? I'm no analytics specialist so i don't know for sure :)

About this, I'm not expert either, but I think I'm right if I tell you that:

In Facebook's Ads Manager, you will only see Purchases that came from a campaign click / view.
In Facebook's Events Manager, you will see all Purchase events, no matter if they originated from a click on an ad or not.

By the way, i could reproduce it because some of the timestamps are WAY more in the future than it could be caused from networking errors, i'm talking from 10mins to half an hour. I guess that since the timestamps are made in the client container they could be indicators of wrong time settings of the client itself.

I modified the Date & Time settings on my OS (Ubuntu 20.04) and I set the clock +2 hours from the current time. And guess what, the timestamp generated by the GTM tag was also +2 hours from the real time. So, it turns out that the API method on the template to generate the timestamp (getTimestampMillis()) takes into account the system's clock (just as browser's Date.now()). Could that be the source of the problem on your side?

Yes, i'm talking about the Events Manager reporting, which is where i am "losing" some Purchase events.
I added some logging on the template to send the purchase events to the container logs, and i noticed that Facebook is discarding the events which report the iOS user agent. I now think that this is the default behavior for the iOS sent events, disregarding the fact that there has been an opt-out by the user (since there is no way for them to know anything about it).
I'm pretty sure that the events with the future timestamp are caused by system settings of the users, so i don't think that it's to be considered a bug.
Thank you :)

I added some logging on the template to send the purchase events to the container logs, and i noticed that Facebook is discarding the events which report the iOS user agent. I now think that this is the default behavior for the iOS sent events, disregarding the fact that there has been an opt-out by the user (since there is no way for them to know anything about it).

Oh, that's quite interesting, thanks for letting me know about that behavior. I guess it comes from all changes that iOS14 brought to privacy and tracking.

I'm pretty sure that the events with the future timestamp are caused by system settings of the users, so i don't think that it's to be considered a bug.

Agree!
Thanks for opening this issue, it helped me understand better that kind of errors. I will close it if there's nothing else to discuss about this issue, but of course feel free to open another one whenever you see fit :)

Yeah, thank you for this discussion, it's been really helpful to understand the technical side of these implementations, which are always considered a matter of web marketing with little to none technical discussion available!


fix(deploy scripts): deploy.js bug while using custom wallet

this is a bug of hardhat framework:
while using custom wallet, it can't calculate gasLimit of contract call tx correctly

Codecov Report

Merging #1 (550c4cc) into fix-eth-deploy-out-of-gas (b4847f9) will increase coverage by 46.86%.
The diff coverage is n/a.

@@                      Coverage Diff                       @@
##           fix-eth-deploy-out-of-gas       #1       +/-   ##
==============================================================
+ Coverage                       8.42%   55.29%   +46.86%
==============================================================
  Files                             22       23        +1
  Lines                           4309     1011     -3298
  Branches                           0      167      +167
==============================================================
+ Hits                             363      559      +196
+ Misses                          3946      452     -3494

Impacted Files
Coverage Δ

...racts/lib/eth-bridge-typescript-lib/src/adapter.rs

...ts/lib/eth-recipient-typescript-lib/src/actions.rs

ckb-contracts/eth-spv-lib/src/ethspv.rs

...tracts/lib/eth-recipient-typescript-lib/src/lib.rs

ckb-contracts/types/src/generated/witness.rs

...racts/lib/eth-bridge-lockscript-lib/src/adapter.rs

...contracts/lib/eth-bridge-lockscript-lib/src/lib.rs

...tracts/types/src/generated/eth_bridge_type_cell.rs

...b-contracts/types/src/generated/eth_header_cell.rs

ckb-contracts/eth-spv-lib/src/eth_types.rs

... and 35 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b4847f9...550c4cc. Read the comment docs.


Clearable Causes onBlur

In my code, I am using react-datepicker as the date part of a date/time field. We wish to implement onFocus/onBlur-onBlurChange functionality.
This is the sequence expected within our setup along with what should be triggering at which point:

Click Datepicker, select a date. Field Gains Focus
Hit Tab. Enter a Hour.
Hit Tab. Enter a Minute.
Hit Tab. Select AM/PM.
Hit Tab. Field Loses Focus and Change

Alternatively, if no values were entered or selected and you just tabbed through, field would Lose Focus at step 5.
However, Clearable is causing problems with that sequence. What happens instead is;

Click Datepicker, select a date. Field Gains Focus
Hit Tab. Field Loses Focus on Change  (This is where Clearable seems to be)
Hit Tab. Enter a Hour.
Hit Tab. Enter a Minute.
Hit Tab. Select AM/PM.
Hit Tab to exit field.

I have attempted to remove Clearable(seen below) and it will tab through appropriately.

Thank you in advance, I feel this might be a desired fix beyond just our means.

As a workaround to get the exact semantics that you want, I suggest implementing clearable externally from this component, i.e. a button that clears the selected date in your state.

Yes, thank you for the suggestion, but we're looking to keep the interface of our field somewhat clean and not cluttered with extra buttons, so it would be the most ideal case that the 'clearable' button would work for us if changed.
I understand this may be a long shot, but we wanted to give it a shot.


🐛 BUG: New SvelteKit project created by C3 rejects all POSTs

Which Cloudflare product(s) does this pertain to?
C3, Miniflare
What version(s) of the tool(s) are you using?
3.23.0 [Wrangler], 2.9.2 [C3]
What version of Node are you using?
20.11.0
What operating system are you using?
Linux
Describe the Bug
In a newly-created SvelteKit project, all POST requests fail with {"message":"Cross-site POST form submissions are forbidden"}
To reproduce:

Run c3.
Choose to create a Svelte app.
Tell SvelteKit's create tool to create the demo app.
Run the app and browse to it.
Go to the "sverdle" tab in the app.
Try to submit an answer. The submission POST request will be blocked.

This appears to be due to this code in SvelteKit:
https://github.com/sveltejs/kit/blob/043ad0fb7c9247313542253599cd06d6da00a6bf/packages/kit/src/runtime/server/respond.js#L64-L76
I believe in particular request.headers.get('origin') !== url.origin is evaluating true. The reason is, the browser thinks the origin is localhost:8788, but by the time the request reaches workerd, the URL has been rewritten to localhost:5173, which doesn't match.
I'm not familiar with the architecture here but I assume this happens because there's a proxy sitting between the browser and workerd. It seems the proxy is rewriting the Host header when it forwards the HTTP request. If we could convince the proxy not to do that, I think it would solve the problem. That is, the proxy should forward the request with the Host header value it received from the browser, rather than rewrite it to match the workerd socket address.
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
No response

The issue appears to be related to the fact that this is the type of pages:dev script we generate:
wrangler pages dev --compatibility-date=2024-01-17 --proxy 5173 -- npm run dev

Since if you build you application and run it through wrangler pages dev then POSTs seem to be working fine:

We've already discussed the use of wrangler pages dev with the proxying functionality on the team and I think we all agree that we should move away from it, since it is not perfect and it can introduce invalid behaviors such as this one.
I think we need to update the Svelte scripts (and probably all of the other frameworks too) to be something like what we have in Next (source), basically remove pages:dev and allow people to use the standard svelte dev command, then provide to them a pages:preview script that they can use to actually preview their application using wrangler pages dev.
That is in my opinion the best option here (I am not familiar how the proxy works either, but since we already know that it is not the optimal solution, instead of trying to fix it there I'd advocate for just not using it (which is something that we were already planning to do in any case))
One caveat here is that with the standard Svelte dev script (vite dev) currently people can't access their Bindings (as SvelteKit itself documents), I hope that that can change soon: https://github.com/sveltejs/kit/pull/11323

I believe that this is actually a problem with the "other" proxy that is being used by the wrangler pages dev --proxy command to send requests to the vite dev command rather than run then using workerd.
I tried following the reproductions steps above (thanks @kentonv) and I can see the problem both with the current Wrangler+MIniflare releases but also with<EMAIL_ADDRESS>which is before the current wrangler dev proxy was implemented, and even<EMAIL_ADDRESS>which was before we moved over to workerd in Miniflare.

Indeed debugging into this we have this code when wrangler pages dev is proxying requests to a third party dev server (as is the case here):
https://github.com/cloudflare/workers-sdk/blob/0de1e1612cd35cfcb8394dc00961fa79cae83ae5/packages/wrangler/src/miniflare-cli/assets.ts#L41-L46
The call to fetch will follow the HTTP fetch spec with regards to CORS and Origin header - i.e. it will overwrite the header on the request with the origin from the request.url.
Perhaps there is an option we can pass to Undici's fetch to override this? For example I see in the Undici code it checks for request.responseTainting === "cors" before doing the overwrite and/or the request.referrerPolicy.

The proxy provided by Pages used in this issue is not easy to fix for the scenario set out here. Really this is not its correct use anyway. The original idea of this proxy was for SPA frameworks, like React (not full-stack, like Svelte), which had a dev server that hosted client side assets and was able to engage in things like incremental builds and hot-module reloading. In that case it makes sense for Pages to delegate the hosting of the static assets to such a dev server to avoid having to manage that itself. The idea was that code in Pages Functions would be handled by Wrangler (i.e. workerd) and static assets would be handled by the 3rd party dev server.
This doesn't really make sense for full stack frameworks, where the dev server actually wants to (and can) handle the server side behaviour as well as the static asset hosting. So going forward we are recommending the following approach.
Simple 3rd party dev server
Use the built in dev server to do day-to-day development with fast feedback cycles.
This will use the 3rd party's dev tooling to build and serve both the static (client-side) assets, and the server-side actions.
Note that in this scenario you are not running you code in an actual Cloudflare Worker nor do you have access to any Cloudflare bindings. But this is the simplest and fastest way to get started.
In the case of the Sveltekit project built by C3 this is just running npm dev, which can be seen to work as expected in the reproduction.
3rd party dev server + getBindingsProxy() helper
This is the same as the first option but additionally configuring the full-stack framework to get a proxy (agh yet another one!) but this time a JS Proxy Object that gives the node.js code running the server-side code access to real Cloudflare Worker bindings hosted by Miniflare locally.
We are working with each full-stack framework to make this as easy as possible to set up. As an example here are the docs on how to do this with Next-on-pages: https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev.
3rd party build + wrangler pages dev
This last option has the highest fidelity to what will be deployed. It involves building the Pages application (incorporating any full-stack framework adaptors for Cloudflare) into a Worker and then running that locally via wrangler pages dev. Wrangler hosts both the client-side static assets and also the server-side code inside a local Worker. This Worker has full access to local bindings just like in normal Worker local development.
The downside to this approach is that on each change to the code you must rebuild the Worker and restart Wrangler, which slows down the development feedback cycle.
With these three options available, we should change the C3 starter to avoid encouraging the Pages proxy setup and document clearly how to use these options. Once that is done I think we can close this issue as won't fix.

Nice work @mrbbot - I can reproduce this locally by patching miniflare to use Unidic's request rather than fetch although I haven't worked out quite the right incantation (it has a bit of a different API) to get it to work for all requests.

Although #4850 does solve the original problem described above  Let's also see if we can fix wrangler pages dev's proxy server as well using one of the suggested approaches discussed here.

@petebacondarwin shall we rename the issue then so not to potentially confuse people?
(maybe I'm overthinking it 😅)

I'm going to work on a fix this week. So hopefully no need to overthink this.


Update drawing usage in web service tests

If we update to System.Drawing.Common to 6.0.0, we get the following error on the build server:
System.TypeInitializationException: The type initializer for 'Gdip' threw an exception. ---> System.PlatformNotSupportedException: System.Drawing.Common is not supported on non-Windows platforms.
See https://aka.ms/systemdrawingnonwindows for more information.
We likely need to move off System.Drawing.Common.

May have been an agent issue


Will not the install instruction be cached?

This link - https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#/apt-get says that apt-get install should be used with apt-get update for cache busting. Will not the install command also be cached along with update instruction?  I understand that version pinning will help but not sure how mixing the install and update commands will help the cache busting.

if you put them on separate lines, e.g.
RUN apt-get update
RUN apt-get install -y foobar

and change the install line, to, eg
RUN apt-get install -y foobar baz

then the apt-get update will not be executed again, and use the cached version for that.
since "update" and "install" are tightly related, it's better to combine them, so that changing the "install" will run both the "update", and "install" again.
I'll close this issue because this is a question, not a bug report, but feel free to continue the discussion

Hey, ya i understand that. Document says "Using RUN apt-get update && apt-get install -y ensures your Dockerfile installs the latest package versions with no further coding or manual intervention. This technique is known as cache busting" and this is giving not giving an essence that package names also should be changed for preventing cache busting.


x/tools/gopls: version upgrade fails when go.mod files change on disk

From a report on Slack: https://gophers.slack.com/archives/CJZH85XCZ/p1595965705370500.

I set up a small(er) reproduction of what I saw in this repo: https://github.com/danp/go-40456. Note this is not using vendoring as the project I mentioned in Slack is.
The main branch starts with k8s.io/client-go at v0.0.0-20190802021151-fdb3fbe99e1d and the change branch updates it to v0.18.6. The change branch also changes main.go to add the initial context.Context argument to List that v0.18.6 expects.
On changing from main to change, the call to List is highlighted with an error as if gopls/etc still expect the first (and only) arg to List to be a metav1.ListOptions.
Log from gopls with -rpc.trace attached. 09:08:xx is loading up main.go on the main branch, the entries beginning at 09:09:10.407 are when I changed to the change branch and the error appeared.

Thank you so much for the repro case! We'll take a look.

(Please let me know if you'd prefer this feedback on the CL)
I gave https://golang.org/cl/245779 a try with my repro and I'm still seeing the same behavior. Was wondering if it somehow relied on me having go.mod open but that didn't seem to matter. Added some quick logging around here to see what currentFH values appear and it was only ever related to main.go (with Kind == source.Go).

I remember you had mentioned on Slack that you disabled file watching in some cases? You will need it enabled for your client to send gopls notifications when you switch branches. The problem no longer reproduces for me in your repro when using VS Code.

It's correct that I had been disabling file watching for the original project I saw this in. Since it uses vendoring there are many files so I get the prompt asking whether I want to watch them all.
However, the reproduction project is much smaller and (I think) everything is watched by default as I'm not prompted. The testing/logging/etc I did above was done in the reproduction project.
Digging and debugging more, it's now looking like this has uncovered an issue in lsp-mode. It doesn't seem to be liking the glob change originally made in https://github.com/golang/tools/commit/fd294ab11aed8d198f7a12a86dfe0a970fdab143. After changing GlobPattern back to **.go and add a second FileSystemWatcher for **.mod, I'm getting the lsp-mode and gopls debug logging I expect.
Will open an lsp-mode issue for the globbing trouble. Thanks!


Filter to exclude summits not currently valid

Is it possible to filter the map to hide summits not currently valid (e.g. deleted summits)? I've had a good search through the settings, am I missing something?

Thank you. I feel foolish for not having seen this now. Thanks for your efforts with such a great resource.


Claude 2.1

The current API will provide access to claude 2.1.  I assume the modification needs to be here:
// view.ts

export const ANTHROPIC_MODELS = ["claude-instant-1.2", "claude-2.0"];

TIA!

Let me know if claude-2.1 is working, thanks

2.1 is working. thanks man. I will send you a tip for your efforts.
On Saturday, December 9th, 2023 at 5:54 PM, Long Huynh @.***> wrote:

Let me know if claude-2.1 is working, thanks
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Cancel Scheduled Sends formatting issue

This page renders slightly off under the "Batch IDs" header: https://sendgrid.com/docs/API_Reference/Web_API_v3/cancel_schedule_send.html
screenshot: https://www.dropbox.com/s/oij1h9cn1qgqmr2/Screenshot 2015-10-26 11.21.52.png?dl=0
I was going to submit a PR but the source looks fine:
https://github.com/sendgrid/docs/blob/develop/source/API_Reference/Web_API_v3/cancel_schedule_send.apiblueprint#L14-L20

Hello @dtjm,Thanks for your suggestion or question! In an attempt to clear out our backlog,                                              we are closing out issues over 90 days old.                                             If this is still an issue, please feel free to reopen it.                                             Team SendGrid DX-Docs


Font colors sporadically changes itself after reload

VSCode Version: 1.43
OS Version: Ubuntu 19.10

Since upgrading to 1.43, font colors seem to be automatically changing a few seconds after reload.
Demonstration
Initially with preferred colors.
After 3-5 seconds they change.
Additionally, the colors seem to apply in a weird, non-logical way.

In the screenshot, I'm using Material Theme.
If I change to any other theme (VSCode inbuilt, incl.), the problem remains, however, the actual colors are different.
Does this issue occur when all extensions are disabled?: Yes, it still occurs.

Happening here as well. The colors change right after the TS server's initialization.

+1 here. Using the Electron theme it goes from the correct theme
 To an entirely different theme:

This happens after initializing.

+1 here, it all started when I installed the latest update...

+1 here. I am also using Material Theme, but it also happens on other themes even with all extensions disabled.

https://stackoverflow.com/a/60623984/2631715

How do you customize the semantically highlighted keywords?
Before:

After:

I can see how this can be helpful to differentiate the variable types, but I would like to saturate the colors more so the function invocations don't look so similar to the function definitions.
Theme used

See https://github.com/microsoft/vscode/issues/92308#issuecomment-597208066

/duplicate


Add documentation to use private registry.

What would you like to be added:
Why is this needed:

Maybe also add test for airgap environments.

needed for private repo


Add missing sandcastle thumbnails

Description
When testing #11805 I realized a bunch of our sandcastles didn't have thumbnails which made them a little hard to tell apart in the gallery.

Added images for all sandcastles that didn't have one
Resized existing images to set a standardized width of 255px which is what the majority already used (this also reduced file sizes)
Deleted development/Clamp to Ground Modes as it was identical to development/BillboardClampToGround

Issue number and link
no issue

Testing plan

npm start
Open local sandcastle and scroll through the gallery
There should not be any missing images. you should not see the default Cesium placeholder image

Author checklist

[ ] I have submitted a Contributor License Agreement
[ ] I have added my name to CONTRIBUTORS.md
[ ] I have updated CHANGES.md with a short summary of my change
[ ] I have added or updated unit tests to ensure consistent code coverage
[ ] I have update the inline documentation, and included code examples where relevant
[ ] I have performed a self-review of my code

Awesome, thanks @jjspace!


Setting withResourceName results in an empty ParamBag for Includes.

When \League\Fractal\TransformerAbstract::callIncludeMethod calls the \League\Fractal\Scope::getIdentifier method the resulting identifier is "incorrect" IF \Spatie\Fractalistic\Fractal::withResourceName was called to set a "top level identifier". It's "incorrect" in the sense that \League\Fractal\Manager::getIncludeParams method has no entry for the resulting identifier.
Code example:
url: /api/v1/abcd/users/36?include=comments:status_in(deleted)
...
return fractal($user, $transformer, new JsonApiSerializer($base_url))
                ->withResourceName('abcd-users')
                ->respond($status, $headers);

Then in \League\Fractal\TransformerAbstract::callIncludeMethod
protected function callIncludeMethod(Scope $scope, $includeName, $data)
    {
        $scopeIdentifier = $scope->getIdentifier($includeName);
        // resulting `$scopeIdentifer` is `abcd-users.comments`
        $params = $scope->getManager()->getIncludeParams($scopeIdentifier);
        // `$params` is empty as the manager only has `includeParams` for `comments` (not `abcd-users.comments`).
       ...
}

Closed as I think the issue better belongs to be opened in the  Spatie\Fractalistic\Fractal repo:
https://github.com/spatie/fractalistic/issues/49


set up webpack raw loader

close #13 set up webpack raw loader for better D.R.Y. with fallback code


Swiping a change to delete it produces an error

(see email for the text, or swipe left on a debug build)

Fixed in 2.0.


drop MiqExpression#supports_memcached?

We no longer need to control memcached
This was dropped in https://github.com/ManageIQ/manageiq/pull/21366 (thanks the the aggressive work of @agrare )
I was not able to find any other references to MiqMemcached

Can you fix the title and commit message?  You wrote MiqExpression, but think you mean MiqEnvironment

update:

fixed commit message to properly state the class

sigh, random issue is causing build to break

kicking


Mrs.d.com

Mrs.d.com
Great day Job in Pakistan
Originally posted by @Mohsinmrs in https://github.com/github/docs/issues/19869#issuecomment-1221622901

Thank you