Yosegi-57 Buffer overflow.

What is the necessity of this update? What is updated?
So far, we have made predictions for the block size to be created. I changed it to calculate this correctly.
This will prevent the exception due to a Buffer overflow.
How did you do the test? (Not required for updating documents)
I checked whether the calculation of data size was correct with the setting of uncompressed metadata.
It was confirmed in the unit test that the data size after addition and the size after the addition match, and the size after addition and the block size written out the match.

There is room for refactoring, but because it is another task, PR is divided.


Background() is not continuing the ticker after applying a download

[ ] identify bug
[ ] fix code
[ ] write tests

I got a problem here... to update a running process, the process has to be shutdown before. For the manually executed update functions i leave this issue to the client. when going for the automated background updating tho I have to find another solution. My ideas so far: i can either kill the process forced in the background logic, or leave a delegate to the client to execute some code like killing a process before the update is executed. Do you have any suggestions @dhcgn, @KirillSerebryakov123 , @enricopau  ?


[enhancement] Allow changing ADDR_VERSION

Currently ADDR_VERSION is fixed to 0x35
https://github.com/CityOfZion/neon-js/blob/93c5305ec668c6934ba6f3796c9ec61fb916e027/packages/neon-core/src/consts.ts#L1
However, the address version is a configurable field through the protocol.json in the neo-cli. In my case I have a private network with a different address version to ever sending to the wrong network.

Fixed by #769


Local measurements

Is your feature request related to a use case or problem? Please describe.
It is possible that subcircuits will contain measurements only intended for use locally to enable classical control logic. It would be nice to be able to make these measurements "local", such that they don't pollute the user's result data or cause naming conflicts unnecessarily.
Describe the solution you'd like
Probably an extra argument cirq.measure(q, key='a', local=True). These would be scoped to the subcircuit and not exposed outside of it.
What is the urgency from your perspective for this issue? Is it blocking important work?

P3 - I'm not really blocked by it, it is an idea I'd like to discuss / suggestion based on principle

Result size hasn't been a huge issue for us, and this has the potential to be a large change - let's not prioritize it for now.


Ability to retry failed payments

Is your feature request related to a problem? Please describe.
If the payment fails there is no way to retry or switch payment method.
Describe the solution you'd like
Add a retry button to the error status component. It could be configurable. Clicking this button could take you back to the payment method selection.
Describe alternatives you've considered
Showing a button outside the drop-in, but that looks ugly.
Additional context
v5.50.0
Using the drop-in implementation.
Example, when canceling a Swish payment from the Swish app (a retry button could be under the "payment failed" text):

Hi @jesperjohansson ,
In this case, you can opt in to set the status by yourself. You must set the setStatusAutomatically on AdyenCheckout to false. Then,  when detecting that the payment got Refused/Cancelled, you can set the status to ready by doing dropin.setStatus('ready') . This should allow for subsequent payments with the same instance and session.
The session will not be able to process a payment after ~5 refusals though, so a new session would be required then.
I hope it helps. Cheers!


Update version: FengHe.FocusNote version 2.16.2-682

Pull request has been created with WinGet Automation :melon:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/114310&drop=dogfoodAlpha

Close with reason: No changes made;


Ballot page/List page icons

These icons need to be pulled in from the actual project icons.  The places I've found this needs fixed:

My Ballot Page
Clicked into a List
Edit Distribution/Add to Ballot modal in a list
Add to Ballot modal from anywhere on projects page

My Ballot Page:

Clicking into a List:

Add To Ballot modal:

Closed in #162


fix text size in cards on mobile

https://trello.com/c/28Y5A9o1/123-text-too-small-on-cards-from-mobile

IBM Cloud toolchain: Delivery Pipeline deployed LRP-web-app to dev, including commit 4cbba138972c67e43a0b36bc87e1afc14e4dbdc8

IBM Cloud toolchain: Delivery Pipeline deployed LRP-web-app to test, including commit 4cbba138972c67e43a0b36bc87e1afc14e4dbdc8

IBM Cloud toolchain: Delivery Pipeline deployed LRP-web-app to prod, including commit 4cbba138972c67e43a0b36bc87e1afc14e4dbdc8


Update README.md

Clarification on Linux installation.
I can conglomerate Linux dependencies and streamline the install some more.
Don't know if

Look into .travis.yml file for clues.

is in the "spirit of the game" or just lazy.

Thanks for your efforts!
Full list of dependencies is written above, so it makes sense only make an exact list of commands - and it is impossible to make it generic for linux (because different distros have different packet managers).
So if you wish to expand the .travis.yml reference to something more meaningful you can do it for your distro and say something like "For example, the following commands will install all needed dependcies on Yourdistroname:".

@kremius
Sure thing.
I know some gits have distro-specific install commands written for the more commonly used distros. Probably in the line of thought that anyone who can figure out GNU and Parabola can figure out how to get all of the dependencies.
Example


Wrapper for HTCondor job submission

Fixes #8493 (until the real issue gets fixed in HTCondor, developers are already aware)
As pointed out by @bbockelm and @belforte , CRAB has to do condor submissions with a different user proxy, so they implemented this context manager class which manages proxy/environment and encapsulates the final condor submission/command in a forked process. It turns out it properly manages the memory footprint, which remains stables between different bulk submissions (tested in an ad-hoc script, around 40MB for 1k jobs submitted).
@bbockelm @belforte I'd welcome your review too. I made only minor changes to the wrapper class such that it works for CRAB and WMAgent, hopefully :)

@ticoann I am still not certain where these utils should be placed. I started creating a Utils/SubprocessUtils.py module, but since it has htcondor specific code, I moved it under the Services package. Anyways, I'm open to suggestions to make it easier/cleaner.

test this please

Thanks Alan for taking care of this. I think current location (under the service) of the file is fine. One thing we probably need to add is try except block on "import htcondor" since not all the application using WMCore/Services will have htcondor dependencies.

isn't it a matter of those using WMCore/Service/pycondor ? Those would better get an exceptoin if htcondor can't be imported.

@belforte, I think you are right it might be better to let it fail.  The thing I was worried was if any already existing application using the WMCore.Services classes has import like below. (Although that should be changed anyway)
from WMCore.Services import *

But I don't see any of those import in DBS or WmAgentScript. I think throwing exception might be better. Thanks,

Ok, then I'm not changing anything for now.
BTW, I ran some tests and it seems to be working just fine, component doesn't crash, information in bl_runjob table makes sense and memory should be stable, I'm going to submit 20k jobs now just to make sure it remains under control.
@belforte in case you want to update CRAB to start importing/using it from WMCore, please keep in mind this part of the code needs to be tested.

Excellent, thanks for tackling this @amaltaro !


How RhinoCharge works

Hello!
I'm a beginner and I am reading your code but I don't understand how RhinoCharge works.I see that RhinoChargeAbility just adds the RhinoChargeBuff to the character, but it's not clear how it allows the character to initiate a charge.
(I'm not sure if it's appropriate to post the question here, and if it isn't, I'm very sorry)

Oh I think I got it, the logic is in the GiganticAssaultController

sorry for not writing comments :p


[Feature request]   Add an option for stretching the task duration by previous end time while there is no start time

Well,it's my habit that I will use end time  to record the thing that I've just done.
So I need a timeline creating method like :when I alread have
- 13:30 Thing A
- 14:30 Thing B
- 15:30 Thing C

And the result I want is:
- ??:??-13:30 Thing A
- 13:30-14:30 Thing B
- 14:30-15:30 Thing C

I am not good at programming in js but I guess it can be easily realized.

BTW the first usually be my get-up time ,I use the timeline as something like diary but a more detailed one.So the first one can be ignored

just like we already have

Maybe we can just change the way we strech tasks by the previous end time if it has no start time
It may just need adding a option button (if there's no other similiar feature to add)

I believe you can already do this by slightly adjusting your habit of data entry.
Just shift all your time entries up.
Add an entry for Thing A when you start working on it, then your Thing A "end time" becomes the start time for Thing B.
The effort to tweak this tiny behavior would likely be less than to change the logic of the plugin.


nil pointer dereference in the 1.18 compiler when dealing with generic types

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

$ go version
go version go1.18beta1 darwin/amd64

and

$ go version
go version devel go1.18-95b240b Mon Jan 3 23:45:12 2022 +0000 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/pcostanz/Library/Caches/go-build"
GOENV="/Users/pcostanz/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/pcostanz/go/pkg/mod"
GONOPROXY=/*set but not revealed*/
GONOSUMDB=/*set but not revealed*/
GOOS="darwin"
GOPATH="/Users/pcostanz/go"
GOPRIVATE=/*set but not revealed*/
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/Users/pcostanz/sdk/gotip"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/Users/pcostanz/sdk/gotip/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="devel go1.18-95b240b Mon Jan 3 23:45:12 2022 +0000"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/z2/j1tgwrsx2cdcpr780wzjk6tw0000gq/T/go-build154765131=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
It is very difficult to reproduce the issue. I am currently developing a set of three libraries depending on each other, using generic types in current go 1.18 beta / development versions. (library A depends on B, library B depends on C) The bug occurs when I try to build library A, and it seems to be triggered by an instantiation of a generic function from library B.

What did you expect to see?
I believe the source code to be correct. go1.18beta1 vet *.go and gotip vet *.go don't report any issues.
What did you see instead?
See above.

A reproducer (even if not minimized, assuming it's not 100k lines of code) could be useful.
cc @danscales @randall77 in the meantime.

I am fully aware that something to reproduce this bug would be useful, and I'm working on it. ;)
Some more information: The nil dereference is triggered in line 758 of stencil.go. I have added a fmt.Println(nameNode) before line 756. The output that corresponds with the nil dereference looks like this:

LibraryB.nofunc.(*computedObject[bool,bool,int]).getElement

None of the other outputs until that point mention "nofunc" in their names. From elsewhere in the compiler sources, "nofunc" seems to suggest that it has something to do with "shape types." Could you tell me what a "shape type" is? Maybe this will give me a clue what I need to pay attention to to be able to create something to reproduce the bug.
Thanks,
Pascal

More information: I have a method that looks as follows.

func (m *comp[D]) asMask() (result structure, ok bool) {
	m.initialized.Wait()
	switch m := any(m).(type) {
	case *comp[bool]:
		return m.resultStructure.construct(func(i int) bool {
			result, ok := m.getElement(i)
			return ok && result
		}), true
	default:
		return
	}
}

The bug seems to be triggered by m.getElement(i). When I change this as follows, the problem disappears:

func (m *comp[D]) asMask() (result structure, ok bool) {
	m.initialized.Wait()
	switch any(m).(type) {
	case *comp[bool]:
		return m.resultStructure.construct(func(i int) bool {
			result, ok := m.getElement(i)
			return ok && any(result).(bool)
		}), true
	default:
		return
	}
}

Thanks for the issue report!
A simple example of your above code (a type switch on the receiver, where each case is instantiated types) seems to work fine.  If there are no confidentiality issues and you are able to package things up reasonable, feel free to point to the entire large failure case, via a github tree, a gzipped archive, etc.  Of course, a smaller repro is also welcome.
For info on shape types, see here.    Basically, we group types into gcshape groups, and only create one instantiation of a specific generic function/type for all types in a group.  (Our gcshape groups in Go 1.18 are finer-grain than the ones described in the proposal.)  This is to reduce the number of instantiations we create and avoid possible code explosion.  A shape type is the representative type in a gcshape group that we use when compiling an instantiation.  I'm not sure if knowledge of shape types will necessarily help you create a smaller reproduction.

It also looks like noder has not been placed under the usual panic handler (which hides panics when there are type errors in the program, and otherwise prints a nice 'internal error' report). It should be. The compiler should never just dump a Go panic like in the report.

I see what happened. In the C version of the compiler the fault handler was subtly different from hidePanic. In the case where there were no errors printed, it called what amounts today to base.Fatalf("fault"), so that the compiler would print the 'Please file a bug report' text.
That's what's missing. And Fatalf already has the right logic (half duplicating hidePanic), so I think hidePanic  can be simplfied to
func hidePanic() {
	if err := recover(); err != nil {
		base.Fatalf("panic: %v", err)
	}
}

And probably at that point should be renamed to handlePanic.

I downloaded the newest version of gotip today, and now the issue doesn't occur anymore. Thanks a lot!

OK, great, not sure what change fixed it.  Still happy to have some version of your code as a test case if you're willing, but I realize that may be infeasible.  Closing the issue.

The code where this issue occurred is finally open sourced. You can find the libraries depending on each other at:

https://github.com/intel/forGoParallel
https://github.com/intel/forGraphBLASGo
https://github.com/intel/forLAGraphGo

Alas, the code has also changed considerably since the bug report above, and what triggered the bug isn't even in the repositories anymore. But maybe you still find this interesting...


Don’t load sprites from idb when no-sw is set

If we do this, the no-sw flag should be renamed no-cache.

Agreed.
Blocked on #105


Values in the portfolio aren't matching wallet amounts for some users

Example: https://discord.com/channels/737780518313000960/1019711310788833330/1019917751831232610
"the amount which appear on portfolio is wrong, i have different amont on polkadot js"

Need more information about the problem.


Feat/media

Added uploading an image functionality

The backend code is already deployed in master so feel free to merge if @horacioh reviews and its ok

@horacioh could you review this PR please?


Support opening workspace as a new native tab in existing window from CLI

VSCode Version: Version 1.12.2 (1.12.2)
OS Version: 10.12.1

Steps to Reproduce:

Have a window open with multiple workspaces open as a native tab
In a terminal, cd to a new workspace location.
Run code .

I would expect that if you are using native tabs, the workspace should open as a new tab in the last used vscode window. Currently it will open a new window. The -r and -n options don't work. -r will replace one of the currently open tabs and -n will create a new window.

@RoarkeRandall maybe check our tab settings in the OS:

Hey @bpasero, I already have those settings relating to tabs.

@RoarkeRandall with the above setting mentioned by bpasero and "window.nativeTabs": true in your User Settings JSON, the code . command will open a new native tab.

Any luck with this? It's kinda odd. I had it working for awhile, but after the upgrade to 1.19.0 and messing with my settings a little (un-related to native tabs though) this behavior started up again.

I feel like this should be driven by the macOS options as outlined in https://github.com/Microsoft/vscode/issues/27305#issuecomment-304199062 and not via a CLI argument. Closing - the issues around rendering native tabs are all resolved by now.


Add Excel Export

Please take a look at #121

Deployed in version 2.10.0.
Contributed by @henry2man.

@mehdigharibi  Recently deployed feature will let you export a CSV file. If you change the extension to .xls Excel will try to open it. Even if it is a flat file, it will recognize and import it as if it were a complex Excel file.
If you're satisfied with this feature, we can consider this issue as closed.

The brand new pluto_grid_export package incudes support for excel-like sheet, including UTF-8 (non ascii). You'll need to use this snippet:
import 'package:pluto_grid_export/pluto_grid_export.dart' as pgexport;
....
var exportCSV = pgexport.PlutoGridExport.exportCSV(state,
        fieldDelimiter: ";",
        textDelimiter: "",
        textEndDelimiter: "",
        eol: "\r\n");
    //FIXES https://github.com/bosskmk/pluto_grid/issues/428
    var bytes = const Utf8Encoder().convert(
        // FIX Add starting \u{FEFF} / 0xEF, 0xBB, 0xBF
        // This allows open the file in Excel with proper character interpretation
        // See https://stackoverflow.com/a/155176
        '\u{FEFF}$exportCSV');


Error loading pluin

I'm receiving the following error when trying to load the ring-alarm plugin after a successful install. Other plugins load just fine. JSON is valid. Everything launches just fine if plugin Is uninstalled. Node v10.5.0. I appreciate the help.
Loaded plugin: homebridge-ring-alarm
/usr/local/lib/node_modules/homebridge/lib/server.js:166
plugin.initializer(this._api);
^
TypeError: plugin.initializer is not a function
at Server. (/usr/local/lib/node_modules/homebridge/lib/server.js:166:14)
at Array.forEach (:null:null)
at Server._loadPlugins (/usr/local/lib/node_modules/homebridge/lib/server.js:140:22)
at new Server (/usr/local/lib/node_modules/homebridge/lib/server.js:57:24)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:28:16)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (internal/modules/cjs/loader.js:702:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:713:10)
at Module.load (internal/modules/cjs/loader.js:612:32)
at tryModuleLoad (internal/modules/cjs/loader.js:551:12)
at Function.Module._load (internal/modules/cjs/loader.js:543:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:744:10)
at startup (internal/bootstrap/node.js:240:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:564:3)

Have you tried the latest version of homebridge?  Looks like this might have been fixed in v0.4.46 https://github.com/nfarina/homebridge/commit/9b87762d2e9056c61f664316445b31d54ae1a79b

Great, glad to hear that!


Uncaught (in promise) Error: Unable to fetch protocol negotiation info: URL returned [201]

Search terms you've used
Based on firefox devtools console output
Uncaught (in promise) Error: Unable to fetch protocol negotiation info: <redacted URL> returned [201]
Bug description

When using WebsocketNotification and calling .connect(), negotiation fails.
The server responds with "201 Created", but execution of the client library stops there.
Debugging in Browser shows me the following Request payload for POSTing to e.g. https://solid.mydomain.com/storage/:
{"protocols":["ws"],"features":[]}

Uncaught (in promise) Error: Unable to fetch protocol negotiation info: https://solid.mydomain.com/storage returned [201]

To Reproduce

Use Community Solid Server 7 as your POD software
Set up a webid profile
Try to subscribe to any SolidDataset location
Check server response to be HTTP 201 instead of HTTP 200 (I don't know what the solid spec says should be the right code)

Minimal reproduction
      const resourceUrl = new URL('https://solid.mydomain.com/storage/')
      const websocket = new WebsocketNotification(resourceUrl.href, {
        // fetch is an authenticated instance
        fetch,
      })
      websocket.connect()

Expected result

Do not fail on HTTP Status code 201
Actual result

Fails on HTTP Status code 201
Environment

$ npx envinfo --system --npmPackages --binaries --npmGlobalPackages --browsers
  System:
    ...
  Binaries:
    Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
    bun: 1.0.25 - ~/.bun/bin/bun
  npmPackages:
    @hexagon6/svelte-solid-store: ^0.3.2 => 0.3.2
    @hexagon6/svelte-solid-webid-check: ^0.4.0 => 0.4.0
    @histoire/plugin-svelte: ^0.17.9 => 0.17.9
    @inrupt/solid-client: ^1.27.0 => 1.30.2
    @inrupt/solid-client-authn-browser: ^1.15.0 => 1.17.5
    @inrupt/solid-client-authn-node: ^1.15.0 => 1.17.5
    @inrupt/solid-client-notifications: ^2.0.0 => 2.0.0
    @inrupt/vocab-common-rdf: ^1.0.5 => 1.0.5
    @inrupt/vocab-solid: ^1.0.4 => 1.0.4
    @lukeapage/pretty-quick: ^4.0.1 => 4.0.1
    @playwright/test: ~1.32 => 1.32.3
    @sveltejs/adapter-auto: ^3.1.1 => 3.1.1
    @sveltejs/adapter-static: ^3.0.1 => 3.0.1
    @sveltejs/kit: ^2.5.0 => 2.5.0
    @types/cookie: ^0.5.1 => 0.5.4
    ava: ^5.1.0 => 5.3.1
    buffer: ^6.0.3 => 6.0.3
    eslint: ^8.27.0 => 8.54.0
    eslint-config-prettier: ^9.0.0 => 9.0.0
    eslint-plugin-fp: ^2.3.0 => 2.3.0
    eslint-plugin-svelte: ^2.32.4 => 2.35.0
    esm-module-alias: ^2.0.2 => 2.1.0
    histoire: ^0.17.9 => 0.17.9
    husky: ^8.0.3 => 8.0.3
    localforage: ^1.10.0 => 1.10.0
    node-stdlib-browser: ^1.2.0 => 1.2.0
    prettier: ^3.0.3 => 3.1.0
    prettier-plugin-svelte: ^3.0.3 => 3.1.1
    ramda: ^0.29.0 => 0.29.1
    svelte: ^4.2.9 => 4.2.9
    svelte-check: ^3.6.3 => 3.6.3
    typescript: ^5.3.3 => 5.3.3
    uuid: ^9.0.0 => 9.0.1
    vite: ^5.0.0 => 5.0.12
  npmGlobalPackages:
    corepack: 0.23.0
    npm: 10.2.4

Additional information

Hi @hexagon6 , thanks for reaching out!
I think the core issue here is that the notification protocol implemented by the client library here is pre-specification, so it isn't aligned with the CSS protocol. It is on the roadmap to eventually catch up with the specification, but hasn't been done yet. I'm afraid until this is done, CSS is not supported for notifications.

How can I help? I've implemented a current-specification for web sockets in my application, which is probably not so trivial to generalize, but I know the steps needed to get it working. Is the roadmap publicly available?

Hi @hexagon6 , thanks for reaching out! I think the core issue here is that the notification protocol implemented by the client library here is pre-specification, so it isn't aligned with the CSS protocol. It is on the roadmap to eventually catch up with the specification, but hasn't been done yet. I'm afraid until this is done, CSS is not supported for notifications.

@NSeydoux Also considering that<EMAIL_ADDRESS>uses now StreamingHTTPChannel2023¶ instead of WebSocketChannel2023¶ is this also planned?

Hi @hexagon6 ,
Unfortunately, we don't have a public-facing representation of the roadmap. If you want to fork the repository and add support for the latest notifications API, I'll be happy to provide feedback and to see that it can be merged in main.

Also considering that<EMAIL_ADDRESS>uses now StreamingHTTPChannel2023¶ instead of WebSocketChannel2023¶ is this also planned?

For the time being, the general plan is to bring ESS and the client libraries up-to-speed with the current spec when we start that effort, so the scope will depend on the timing I reckon.


making balances method can handle parameters

Currently balances method does not handle paramters. This pull request make the balances method handle parameters.
Please refer bellow url for the detail of parameters for balances method.
https://ripple.com/build/ripple-rest/#get-account-balances

Please review and merge this pull request.

Thank you


Catch xml parsing exceptions

Description
Fix an uncatched exception on the pdf parser where lxml had to parse wrongly syntaxed xml files.
Fix #255
Type of change

[x] :bug: Bug fix (Add Fix #(issue) to your PR)

:+1: nice work


Will invoking of external bash command throw exception?

The lines bellow should catch an exception?
I had wrote Powershell for months, It's not Powershell way.
try {
  "/opt/oozie-build/oozie/bin/mkdistro.sh -DskipTests >/tmp/tmpJylOol.tmp 2>&1" | Invoke-Expression
}
 catch {
            $Error | Write-HostIfInTesting
 }

Or

try {
  "/opt/oozie-build/oozie/bin/mkdistro.sh -DskipTests" | Invoke-Expression
}
 catch {
            $Error | Write-HostIfInTesting
 }

Even invoke code like this, it won't throw an exception. Does Powershell handle Java thread special?
try { "bash xx" | Invoke-Expression} catch { "yyy"}

External commands can't throw exceptions. They can only write to the error stream and return an exit code. If the exit code is non-zero then the value of $? will be false. The specific exit code is available in the variable $EXITCODE. Also, you don't need to use Invoke-Expression to execute an external command. You can execute them directly as in
bash -c "exit 1" ; if ( -not $?) { "Cmd exited with an error status" }
(NOTE: In general, Invoke-Expression should be avoided except for a few rare cases since it opens the doors to script injection attacks.)


Feedback for "What's New for SAP Business Application Studio"

https://help.sap.com/products/SAP Business Application Studio/9d1db9835307451daa8c930fbd9ab264/ed631d4ee2214e9f932b03d40b2c7e41.html?locale=en-US
If I hit edit it has a dead end.
What I also want to ask if the coumn deploy to ABAP is the correct wording. Shouldn't it named deploy to Netweaver Stack?

Hi,
We go with the term Deploy to ABAP.
As per the what;s new edit link, I will look into it. Thank you for letting us know!!!

The Edit button issue has been fixed.


Make the inspector handle widgets with non-invertible transforms gracefully.

proxy_box.dart also has to use a try block to avoid throwing when hit testing non-invertible matrices.
It could be a good idea to add a Matrix4 method that returns null instead of throwing when inverting a matrix so that users who are pausing on all thrown exceptions don't pause on these breakpoints.
This fixes  https://github.com/flutter/flutter-intellij/issues/1948


Add update popup and release notes

fixes #260

What do you think about only showing this once per release? Perhaps storing the "I have seen the release notes" version in localStorage when they close the modal.

IMHO, I think for all new components we should add storybook files.

@ashu8912 Can you share a gif of the update UX, and instructions on how to simulate the update?
I am not 100% sure since I haven't tried it yet but I think the update notification should probably follow the snackbar notifications we have for cluster actions.

Hi @ashu8912 , I have just tried the builds you did for testing this new feature.
Nice work. Here's a couple of comments:

When clicking More, we should open the system's browser and not a window of the app with the new release. (The reason is that it feels more natural + the user can stop Headlamp at any point without stopping the ongoing download of the new version + the user can see the progress for the download if it's using the regular browser)
Since the notification keeps getting shown, maybe we need a way to shut it forever. How about we make the buttons as:

[ More ] [ Do not notify again ] [ X ]

X should be a cross/close icon.
This should be disabled for flatpak BTW. You can maybe just disable this if the FLATPAK_ID env var is set ().

(Pressed the button too soon.)
I am not confident on the workflow for keeping the release diff which is being shown when the app's new version is first run.
IMO, until we have a better plan for showing the release notes within the app, I think we should just show a notification (once!) saying "You have upgraded to version X.Y.Z [ Close ]"
X.Y.Z is a link to the release notes for the tag on github, again opening in the external browser.


Raven changed to Sentry SDK

…/migration/raven-to-sentry-sdk/
from -  Issue starting Celery in generated APP #50
2024-07-17 18:49:15 Unable to load celery application.
2024-07-17 18:49:15 'pydantic_core._pydantic_core.url' object has no attribute 'strip'
the apparent cause was from worker/tests.py starting up the worker:
raven was failing due to dependency on pydantic 1 where url inherits from string
it was confirmed that sentry was receiving messages via from sentry_sdk import capture_message which was omited for PR
info on migration from raven to sentry_sdk below
https://docs.sentry.io/platforms/python/migration/raven-to-sentry-sdk/

Thanks for working on this! Could you add in the sentry package to the pyproject.toml and then remove the raven package as well?


feat: add pipeline steps

@notzilly please expose the new pipeline step service through packages/sdks/javascript/src/DevopnessApiClient.ts.
See #568 as a reference.


Fix parameters schematron in r4. Add missing parameters schematron to STU3 resources.

This schematron was broken/missing, so Parameters resources could not be validated using the Schematron validator as noted in #1291
Corresponding change requests have been made on hl7.org to address the incorrect & missing files there:
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=21153&start=0
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=21180&start=0

This is receiving no attention, I guess it's not a problem for anyone else.


Can not set border to FloatingActionButton

Problem description
I try to set border to FloatingActionButton,
Which props should I use to set  border.
Also how to disabled hover effect,
 overlayWhenHovered: {
      backgroundColor: fade(iconColor, 0.4),
    },

Link to with code,
https://codepen.io/palaniichukdmytro/pen/NgQmve

Versions

Material-UI: v0.18.6

We have been porting the component on the v1-alpha branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it.
Still, we will accept PR fixes until v1-alpha takes over the master branch.


Error on closing PayPal window

An error occurs after closing PayPal's payment window during initializing.
Here is the screenshot:
http://pasteboard.co/7ENhaxhkY.jpg

So, just to be clear -- you're clicking the paypal button, but closing the window before it loads?

Exactly ;)

OK. This error was designed for iframe use-cases, in case the element is removed -- I'll probably disable this for the popup though, since it would need to be closed by the user.
Thanks for the catch.

Fixed and ready for deploy.

Pushed.


Adaptive cards in tabs, light color is white

When I use:
{
            "type": "TextBlock",
            "text": "${description}",
            "wrap": true,
            "color": "Light"
        },

The text doesn't show up, as it's white (not gray). Is there a way for the msteams team to fix this bug?
Thanks

@guillewu - Thanks for reporting your issue.
We will check this at our end and will get back to you.

@sayali-MSFT thanks, looking forward to the fix

@guillewu -Got the reply from engneering teams that "The behaviour is inline with the expectation from adaptivecard.io"
Changing the theme to Microsoft Teams, it seems the behaviour is inline with adaptivecard.io.

@sayali-MSFT thank you for your reply. However, I don't understand your answer. Does that mean that in "light" mode, there is no option for a light color that results in a light gray font color?

@guillewu -Unfortunately, as of now, the same is not possible out of the box. As mentioned above, the light grey behaviour is from Bot Framework Chat theme. In Microsoft Teams theme in the portal itself we can see that white color is used.


version extension

Update https://github.com/stac-extensions/version with https://github.com/radiantearth/stac-spec/tree/3a83d75aec7f16ae597ee9779777a97e83ff46a4/extensions/version

This is done and needs a review before releasing.

I'm going to review it.


Problems with Mulberry charts not being able to be plotted

scSLAT can't plot the mulberry diagram described in the article, hopefully this will be fixed.

Hi, can you provide more details ?

This issue was closed because it has been stalled for long time with no activity. Feel free to reopen it.


[8.x] Add getLineLoaded Function

JSON Provides a hierarchy style for the key value. This means that value can be an array too.
For some organizing work, you would need to write __("foo.bar") and load it from the JSON file.
This function provides you with the ability to assign the value of the key "foo" to be an array
that contains a key called "bar" with a string value.
It doesn't affect the old style of writing and processing the function.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Handle uglyURLs ambiguity in Permalink

Link to repo  - this includes the following:
I find this working: create a /section/index.md in a section and it renders to /section/index.html in that same section in the public folder.

index.md or foo.md is content and metadata for the single pages,

I like to have an index-file in each content subdirectory as every webserver I know will deliver this when a user uses an address like http://domain.tld/section/.
All works fine so far.
I use  the following structure:
.
├── config.toml
├── archetypes
├── content
|   ├── _index.md
|   ├── womo
|   |   ├── index.md
|   |   ├── fahrgestell.md
|   |   ├── aufbau.md
|   |   ├── einrichtung.md
|   |   └── {more pages}.md
|   ├── hund
|   ├── blog
|   └── kontakt
├── static
├── data
├── layouts
└── themes

and this renders to
.
└── public
    ├── index.html
    ├── womo.html
    ├── womo
    |   ├── index.html
    |   ├── fahrgestell.html
    |   ├── aufbau.html
    |   ├── einrichtung.html
    |   └── {more pages}.html
    ├── hund.html
    ├── hund
    ├── blog.html
    ├── blog
    ├── kontakt.html
    └── kontakt

which is ok so far - and as expected following @bep 's definition.
Now I use the following code to produce a sidenav within the womo section.

            {{ $act_section := .Section}}
            {{ range where .Site.Pages "Section" $act_section }}

{{- .LinkTitle -}}

            {{ end }}

It ends up like this:

Einführung

Fahrgestell

Aufbau

Einrichtung

which obviously is wrong since the first line should be like

Einführung

So at least for creating the menue index.md is NOT treated as content and metadata for a single page.
Hugo uses linktitle from the frontmatter of /section/index.md but the created link instead points to /section.html which gives a simple list but not the content of /section/index.md.
That's why I used to rename /section/index.md to something else like /section/intro.md in the snapshots above and everything worked fine

The repo you link to does not look like the site you describe (no motorhome).

sorry, but all the site is in german.
motorhome would be "womo"
dogs would be "hund"
contact would be "kontakt"
I hope this will solve this - I translated the excerpts for the convenience of the readers as the support forum is in english. But translate all of the site - I hope this will not be necessary ...

I updated the structure above to match the actual repo. Readme.md is also updated.
Sorry for the confusion.

OK, I see it now, but I'm not sure how to solve it. Maybe others will.
There is an uglyURLs ambiguity here, but we seem to have gotten it right when we wrote the file to disk, so ...

The page starts out with the URL "womo/index.html"
The logic to make that ugly "womo/index.html" => "womo.html"

That said, a workaround that should work for you is to put a url override in your womo/index.md:
url = "womo/index.html"

Thanks - I did not know about that override - will test it.


Sanitized and reported to the client as: Match failed [400]

In the Pagination chapter there is the following code:
Meteor.publish('posts', function(options) {
  check(options, {
    sort: Object,
    limit: Number
  });
  return Posts.find({}, options);
});

The check() function creates a Meteor error:
I20150216-11:35:38.893(-8)? Exception from sub LMiCJQKiFpnLh6fWu Error: Match error: Expected object, got undefined
I20150216-11:35:38.894(-8)?     at checkSubtree (packages/check/match.js:275:1)
I20150216-11:35:38.894(-8)?     at check (packages/check/match.js:32:1)
I20150216-11:35:38.894(-8)?     at [object Object]._handler (app\server\publications.js:4:5)
I20150216-11:35:38.894(-8)?     at packages/check/match.js:109:1
I20150216-11:35:38.894(-8)?     at Object.Match._failIfArgumentsAreNotAllChecked (packages/check/match.js:108:1)
I20150216-11:35:38.894(-8)?     at maybeAuditArgumentChecks (packages/ddp/livedata_server.js:1597:1)
I20150216-11:35:38.894(-8)?     at [object Object]._.extend._runHandler (packages/ddp/livedata_server.js:943:1)
I20150216-11:35:38.894(-8)?     at [object Object]._.extend._startSubscription (packages/ddp/livedata_server.js:769:1)
I20150216-11:35:38.894(-8)?     at [object Object]._.extend.protocol_handlers.sub (packages/ddp/livedata_server.js:582:1)
I20150216-11:35:38.894(-8)?     at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
I20150216-11:35:38.896(-8)? Sanitized and reported to the client as: Match failed [400]

If I use console.log('options: '+options) before check() I get two executions of this with the first one always resulting in undefined (specifically, I get two executions when I refresh the page but when Meteor recompiles I get only one and it is undefined.)
I'm not quite well-versed enough with Meteor to know why this is running twice nor why the first time it is undefined. (On the second run i get the expected data [object Object].)
To sum up, this is the output I have with the added console.log() statement (see first and last lines.)
I20150216-11:52:08.388(-8)? options: undefined
I20150216-11:52:08.389(-8)? Exception from sub XjqT8wyJTvKe6cnTW Error: Match error: Expected object, got undefined
I20150216-11:52:08.389(-8)?     at checkSubtree (packages/check/match.js:275:1)
I20150216-11:52:08.389(-8)?     at check (packages/check/match.js:32:1)
I20150216-11:52:08.389(-8)?     at [object Object]._handler (app\server\publications.js:5:5)
I20150216-11:52:08.389(-8)?     at packages/check/match.js:109:1
I20150216-11:52:08.389(-8)?     at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
I20150216-11:52:08.389(-8)?     at Object.Match._failIfArgumentsAreNotAllChecked (packages/check/match.js:108:1)
I20150216-11:52:08.389(-8)?     at maybeAuditArgumentChecks (packages/ddp/livedata_server.js:1597:1)
I20150216-11:52:08.389(-8)?     at [object Object]._.extend._runHandler (packages/ddp/livedata_server.js:943:1)
I20150216-11:52:08.390(-8)?     at [object Object]._.extend._startSubscription (packages/ddp/livedata_server.js:769:1)
I20150216-11:52:08.390(-8)?     at [object Object]._.extend.protocol_handlers.sub (packages/ddp/livedata_server.js:582:1)
I20150216-11:52:08.400(-8)?
I20150216-11:52:08.399(-8)? Sanitized and reported to the client as: Match failed [400]
I20150216-11:52:08.427(-8)? options: [object Object]

I won't be surprised if this ends up being a typo somewhere on my part but I've looked over the code several times and can't find any place where I have deviated incorrectly.

I am facing the same problem. Any fix for this?

I'm at work right now so I can't check this (and haven't worked on this since around the time I opened this) but on the Pagination page search for return Meteor.subscribe('posts' and make sure that your code is exactly like what is in the book at every instance where you find a match.
I looked at the code again and in each instance, where the publication is used, the subscription appears to be passing the correct object structure. It's possible that I had deviated from their instructions somehow and didn't notice it.
Also, instead of a plain console.log() statement, like I originally wrote above, you can dig into the options variable a little more with this: console.log(JSON.stringify(options)). That can show you what's in the object rather than just identifying it as Object.

Thanks for the pointers. I found the problem. I had left the
Meteor.Subscribe('posts') inside Router.configure. This caused the error.
After removing this subscription, it works perfect.
On Tue, Apr 7, 2015 at 2:31 AM GiraffeSlacks<EMAIL_ADDRESS>wrote:

I'm at work right now so I can't check this (and haven't worked on this
since around the time I opened this) but on the Pagination page search for return
Meteor.subscribe('posts' and make sure that your code is exactly like
what is in the book at every instance where you find a match.
I looked at the code again and in each instance, where the publication is
used, the subscription appears to be passing the correct object structure.
It's possible that I had deviated from their instructions somehow and
didn't notice it.
Also, instead of a plain console.log() statement, like I originally wrote
above, you can dig into the options variable a little more with this:
console.log(JSON.stringify(options)). That can show you what's in the
object rather than just identifying it as Object.
—
Reply to this email directly or view it on GitHub
https://github.com/DiscoverMeteor/Microscope/issues/204#issuecomment-90296568
.

@GiraffeSlacks - I would say most likely this is your issue also -- you probably missed the fact that you have to remove the older Meteor.subscribe('posts') that we added in an earlier chapter.
Let me know if that's not it.

@tmeasday That's very possible. I did find it hard to identify code that was removed. The problem with the code is sometimes it's disorienting and not obvious exactly where you're supposed to be (in a file). Also, when code is removed it's just a matter of not being present in the new code (as I recall) rather than explicitly being shown as removed. (I know the code is available on Github. I think there is room for improvement in the book.)

Hmm, ok makes sense @GiraffeSlacks. Thanks for the feedback.

I'm getting something similar on this same chapter.  so far everything has been flawless... i can't seem to figure out what is going wrong here.  i have literally copied everything directly from the github repo for this chapter.  I'm kind of at a loss here.
    I20150528-09:34:12.733(-5)? Exception from sub posts id QZwdEnztd6oHASbNs Error: Match error: Expected object, got string
    I20150528-09:34:12.733(-5)?     at checkSubtree (packages/check/match.js:275:1)
    I20150528-09:34:12.733(-5)?     at check (packages/check/match.js:32:1)
    I20150528-09:34:12.733(-5)?     at [object Object].Meteor.publish.Comments.find.postId [as _handler] (app/server/publications.js:2:5)
    I20150528-09:34:12.733(-5)?     at maybeAuditArgumentChecks (packages/ddp/livedata_server.js:1617:1)
    I20150528-09:34:12.733(-5)?     at [object Object]._.extend._runHandler (packages/ddp/livedata_server.js:950:1)
    I20150528-09:34:12.733(-5)?     at [object Object]._.extend._startSubscription (packages/ddp/livedata_server.js:769:1)
    I20150528-09:34:12.734(-5)?     at [object Object]._.extend.protocol_handlers.sub (packages/ddp/livedata_server.js:582:1)
    I20150528-09:34:12.734(-5)?     at packages/ddp/livedata_server.js:546:1
    I20150528-09:34:12.734(-5)? Sanitized and reported to the client as: Match failed [400]
    I20150528-09:34:12.734(-5)?

Maybe add a console.log() before the check() to see what exactly you're passing that's causing the problem?

you know what, it turns out i had not removed the line "Meteor.subscribe('posts', 'bob-smith');" from the main.js file in a previous section.  I must have missed it.
sorry about that.  I guess to GiraffeSlacks point, it can be easy to miss something like that.  Not sure how you'd fix it... overall i find this tutorial really really great.  don't know if maybe at the end of each chapter there could be a terminal command you could run that would just pull down that instance from github and just overwrite your files?  But, honestly, it's really solid.


fix(presets): update init templates for 4.0 release

Update the VueJS, react and angular presets for the 4.0 release.

I've updated the presets in this PR. There is however an issue with the vuejs preset.
The VueJS preset is quite old. It actually is not compatible with the vue cli. If you want to get your vue cli project to work with Stryker, your best chance at the moment is to look at our e2e tests (so either vue-cli-javascript-jest or vue-cli-typescript-mocha depending on which test runner you are using). I think we might want to add better vue support in the future, but especially with mocha, that isn't easy.
But, what to do with the vue preset in the meantime? 🤷♂

neat! So much code went out

E2E tests are working with VUE, and not much needs to be done.

I disagree. Quite a lot needs to be done to make vue work with mocha actually.

Create a custom "webpack.test.config.js" with this content:const conf = require('@vue/cli-service/webpack.config.js');
conf.entry = {
  tests: ['./test.js']
}
module.exports = conf;

Create a custom "test.js" with the following content:require('./test/setup.js'); // your setup file here.

// Then we find all the tests.
const context = require.context('./src', true, /\.spec\.ts$/);
// And load the modules.
context.keys().map(context);

Install "webpack-cli" (vue-cli projects don't have this installed out-of-the-box)
Create a "stryker.conf.json" with the following content:{
 "buildCommand": "webpack --config webpack.test.config.js",
 "mochaOptions": {
    "require": [
<EMAIL_ADDRESS>    ],
    "spec": ["dist/js/chunk-vendors.js", "dist/js/tests.js"]
  },
}

Run stryker with NODE_ENV=test VUE_CLI_BABEL_TARGET_NODE=true stryker run (needs to be reworked)

Even with this, it might not work as expected, because there are still differences between Stryker's way of running the tests and vue-cli way of running it.
Basically, vue-cli it is a big mess IMHO. Vue cli uses mocha-pack with additional stuff. mocha-pack uses webpack and mocha with additional stuff. No fun for Stryker.
At this point, I feel like we have 3 options.

Drop support for Vue CLI during stryker init altogether. Just point people to our e2e test setup in docs.
Or do a PR on the vue cli itself to improve the mess they made.

Oww... i havent checked Mocha yet. Only Jest since we have jest tests for vue :/

@nicojs Does the situation improve now Vue v3 is live?

Nope they're still using the mochapack spaghetti

I think we should just make another E2E

What's wrong with the existing one?

"Quite a lot needs to be done to make vue work with mocha actually."
Maybe we both misunderstand each other. :x What i am saying is that we should make it easy to go from E2E mocha-vue to user app (small changes in configs and it works)

I've updated the vuejs guide: https://github.com/stryker-mutator/stryker-handbook/blob/master/stryker/guides/vuejs.md#vuejs and I've updated the vue templates that are generated when a user chooses mocha.
I've managed to remove step 2: "Create a custom "test.js" with the following content: ", but I'm still not happy with the result. At least it does work with a standard vue-cli project a.t.m.
IMO we can release v4 with this... I guess.

What i am saying is that we should make it easy to go from E2E mocha-vue to user app (small changes in configs and it works)

I tried my best, but I cannot bend steel with my bare hands 😑


Fix close drain error callback.

This fixes the incorrect error callback that returns a Map literal.

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.

Note that this repository uses Gerrit for code reviews. Your pull request will be automatically converted into a Gerrit CL and a link to the CL written into this PR. The review will happen on Gerrit but you can also push additional commits to this PR to update the code review.

Thanks for the contribution! I took a liberty to approve CL given that @brianquinlan is out. It is in CQ now and will land shortly.

(In the future if you have a regression test for a specific issue you are fixing - I encourage you to submit that alongside the fix!)


gauge chart not working

Hello Team,
tried several times angular2 - highcharts including gauge chart options below but not working.
we are using system.config.js I included highcharts,angular2-highcharts,highcharts more stock solid gauge libraries but still not working.
fyi.. column chart working fine, for below if we removed te type prop it will bind but as column :)
would you please help!
html
<chart [options]="options">
ts..
constructor() {
this.options = {
   chart: {
        type: 'gauge',
        plotBackgroundColor: null,
        plotBackgroundImage: null,
        plotBorderWidth: 0,
        plotShadow: false
    },

    title: {
        text: 'Speedometer'
    },

    pane: {
        startAngle: -150,
        endAngle: 150,
        background: [{
            backgroundColor: {
                linearGradient: { x1: 0, y1: 0, x2: 0, y2: 1 },
                stops: [
                    [0, '#FFF'],
                    [1, '#333']
                ]
            },
            borderWidth: 0,
            outerRadius: '109%'
        }, {
            backgroundColor: {
                linearGradient: { x1: 0, y1: 0, x2: 0, y2: 1 },
                stops: [
                    [0, '#333'],
                    [1, '#FFF']
                ]
            },
            borderWidth: 1,
            outerRadius: '107%'
        }, {
            // default background
        }, {
            backgroundColor: '#DDD',
            borderWidth: 0,
            outerRadius: '105%',
            innerRadius: '103%'
        }]
    },

    // the value axis
    yAxis: {
        min: 0,
        max: 200,

        minorTickInterval: 'auto',
        minorTickWidth: 1,
        minorTickLength: 10,
        minorTickPosition: 'inside',
        minorTickColor: '#666',

        tickPixelInterval: 30,
        tickWidth: 2,
        tickPosition: 'inside',
        tickLength: 10,
        tickColor: '#666',
        labels: {
            step: 2,
            rotation: 'auto'
        },
        title: {
            text: 'km/h'
        },
        plotBands: [{
            from: 0,
            to: 120,
            color: '#55BF3B' // green
        }, {
            from: 120,
            to: 160,
            color: '#DDDF0D' // yellow
        }, {
            from: 160,
            to: 200,
            color: '#DF5353' // red
        }]
    },

    series: [{
        name: 'Speed',
        data: [80],
        tooltip: {
            valueSuffix: ' km/h'
        }
    }]

}
options: Object;

}
regards,
Sameh

Make sure you plugged appropriate highcharts module (see the readme)


Certain mapOptions don't seem to work

Here are the props passed into the component:

And yet, the map still renders with type control and zoom control:

Not quite sure what's causing it, as those props match the options provided here:
https://developers.google.com/maps/documentation/javascript/3.exp/reference#MapOptions
Other properties like center and zoom are respected, however.
Am I doing something wrong?
PS here's the code in question:
          <GoogleMapLoader
            containerElement={
              <div
                style={{
                  height: "100%"
                }} />
            }
            googleMapElement={
              <GoogleMap
                ref={(map) => (this._map = map)}
                center={center}
                zoom={store.zoom}
                minZoom={5}
                onDragend={this.dragEnded.bind(this)}
                onZoomChanged={this.zoomHasChanged.bind(this)}
                zoomControl={false}
                scaleControl={false}
                mapTypeControl={false}>

              </GoogleMap>
            }
          />

Never mind, sorry, I really should have read "Rule 4". Putting them in the options object helped.
But I guess my question is, why an options object?

Thanks @mtimofiiv Im not an expert on this, but my notion says its to achieve a better handling on them.


Manage customers' dex instances using dex-operator

related: https://github.com/giantswarm/roadmap/issues/902

related: https://github.com/giantswarm/roadmap/issues/2272

This was more interesting in the past, unclear if this will stay relevant, could be replaced with identity alternative.
Customers could already use dex-operator, but would need to provide highly privileged (i.e. create app registrations) credentials for their Azure AD and rotate them.


Prescriptive Entity Structures - Private Classes and Methods

I particularly like the way the AspNet.Identity apis are structured using generics.  This allows people to use all kinds of data types as ids for their objects.  This is not so with the Azure Mobile SDK that forces string as the id (where the default value is a GUID) and clustering around CreatedAt field.
I agree that generics can add a certain layer of complexity, so the onus can be put on each team to do all the necessary remapping and implement its own SQLGenerator.
We have succeeded in doing this but have hit a roadblock.  We cannot inherit from the existing EntityDomainManager`1 easily because a number of methods are private. The alternative is to reimplement the entire class in our specific project.
We really need to get at the Lookup(string id, bool includeDeleted) method to cast/convert the id from string to what is used in our database and prevent the EF query from failing.
In the Microsoft.Azure.Mobile.Server assembly:
Can they be made protected internal at least?  ie Lookup, UpdateAsync, VerifyUpdatedKey.
Also can the following classes be made public: CommonResources, EFResources, and EntityUtils?

This feature will not be added.
If you need a new DomainManager, implement IDomainManager - the EntityDomainManager has resitrictions that make the service work.

Do you care to provide a little more detail as to why?


Channels near tip of probe often classified as "out of brain"

We've found that for most of our data sorted with this capsule, some channels at the tip of almost every probe are classified as "out of brain" and excluded from further processing. Surprisingly, the channels that we know are outside of the brain (at the top of the probe) are rarely classified as "out of brain".
This might be caused by a couple of different issues I found in the capsule and in the spikeinterface code itself.

in Spikeinterface, prepocessing/detect_bad_channels.py, this is the description of how "out of brain" channels are determined:
* Out of brain channels are contigious regions of channels dissimilar to the median of all channels
at the top end of the probe (i.e. large channel number)

However, in detect_bad_channels_ibl(), which does the bulk of the bad channel detection:
# the channels outside of the brains are the contiguous channels below the threshold on the trend coherency
# the chanels outide need to be at either extremes of the probe
It would make sense to only allow channels with higher numbers to be classified as "out of brain", otherwise this is confusing and potentially preventing us from detecting some units.

in the capsule, bad channel detection occurs before common average referencing.

Since we are tip referencing our probes, if there is a strong signal being detected by the tip, the channels near the tip are relatively quiet, while the channels farther away, including those we know are outside of the brain, have a strong signal.
Before detecting channels that are outside of the brain, we need to correct for tip referencing, whether this is through common average reference or some other method. Otherwise, the wrong channels may be classified as out of brain.
I understand you probably want to avoid using bad channels in the CAR. Maybe CAR needs to happen twice - once over all channels to find the correct "out of brain" and noise channels, and a second time after excluding those channels.

Hi Ethan! Thanks for reporting this.

I agree that in case of the tip reference the bottom electrodes could look quite silent, so it makes total sense to add a "top" | "bottom" | "both" option to the detect_bad_channels. Opened an issue on SI here: https://github.com/SpikeInterface/spikeinterface/issues/2190

We could add this alternative processing as an option. It might make sense to use this double CMR as default. Let's discuss this over a call!

@egmcbride
The SpikeInterface side is merged (https://github.com/SpikeInterface/spikeinterface/issues/2190), but for this repo we prefer to pin to released versions.
With #19 you can now use the --no-remove-out-channels to skip out channels removal as a workaround.
@jtyoung84 how can one pass arguments to a capsule via the service?

@alejoe91 Probably the easiest way is to put the processing configs in a file (yaml, json, ini, etc) in a consistent place and have the capsule search for that file to override defaults. That way, it should also be relatively straightforward to know which parameters were used during the processing. For clarity, somebody would put the spike sorting processing parameters in a file together with the raw data before uploading it to s3.

That would be neat, but if we want to change parameters to re-run processing, we'll need to be able to modify a file that lives in the raw data bucket (not that I have a problem with that).

I can add a feature request to allow a user to define a capusle/pipeline id and an associated set of parameters in the transfer service.

@dyf Any thoughts?

I think we should have a spot in the raw data (say, in the ecephys folder) that describes intended processing parameters.  This would be immutable - it only describe the initial intention.
If you want to re-run the pipeline with different settings, just hop into the UI, tweak the parameters in the app panel, and re-run.

If you want to re-run the pipeline with different settings, just hop into the UI, tweak the parameters in the app panel, and re-run.

I'm not too keen on this for when we need to re-run on 100+ sessions!
We've been wanting to send parameters via the API to other capsules too.. Wouldn't it be a better solution in the long run if CodeOcean could add it?

Code Ocean has a REST API that allows someone to run a capsule with different input parameters. We also have a repository, aind-codeocean-api which is a thin python wrapper around their REST API.

Code Ocean has a REST API that allows someone to run a capsule with different input parameters.

Is that an undocumented feature that you know works?
There are parameters listed as data_assets here, but the document type is string, and the examples show key-values for a single asset, not a list of assets:
https://docs.codeocean.com/user-guide/code-ocean-api/capsule-api

We also have a repository, aind-codeocean-api which is a thin python wrapper around their REST API.

We're using it all the time - thanks!

Code Ocean has  some swagger documentation that I found a little more useful, although it sill lacks examples: https://docs.codeocean.com/user-guide/v/v2.15.0/code-ocean-api/swagger-documentation
I haven't tested the api fully. I've been mostly serializing capsule parameters into a json string using
parameters_to_send = [json.dumps(params)]
and then de-serializing them in the capsule code as something like
parameters_to_use_in_capsule = json.loads(params[0])
But I haven't tested passing in lists of data assets and lists of parameters and whether they correspond to each other. I usually just send one request per (data_asset, parameter_set) pair.

That's very cool - thanks both!


install the package

  building 'dtw._dtw_utils' extension
  error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
  [end of output]

I'm trying to install the package. I keep getting error with pip install --use-pep517 dwt-python==1.1.6
I'm wondering  Microsoft Visual C++ required.
Also, what python version can install package. I have 3.11.8

from the error message, it looks like you'll need to install Microsoft Visual C++
I've used this library with python 3.9 and only tried it on Linux/OSX - hope that helps


tokenv3 send and receive

Implements TokenV3

[x] Update NUT-00 (done)
[ ] Write tests (for all old formats)
[x] Change "legacy" to tokenv2

Codecov Report
Patch coverage: 71.96% and project coverage change: +0.17 :tada:

Comparison is base (258de87) 51.51% compared to head (3d24801) 51.68%.

:exclamation: Current head 3d24801 differs from pull request most recent head 6e7afdb. Consider uploading reports for the commit 6e7afdb to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #149      +/-   ##
==========================================
+ Coverage   51.51%   51.68%   +0.17%
==========================================
  Files          36       36
  Lines        2780     2825      +45
==========================================
+ Hits         1432     1460      +28
- Misses       1348     1365      +17

Impacted Files
Coverage Δ

cashu/mint/startup.py
0.00% <ø> (ø)

cashu/wallet/cli/cli.py
50.00% <46.66%> (+0.77%)
:arrow_up:

cashu/wallet/cli/cli_helpers.py
41.81% <64.51%> (-0.34%)
:arrow_down:

cashu/wallet/wallet.py
80.98% <77.77%> (-2.51%)
:arrow_down:

cashu/core/base.py
95.18% <93.75%> (-1.49%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Required field ignored in case of allOf

I have a MyType with a date field marked as a required. Unfortunately this requirement is mistakenly ignored by orval.
Example:
MyAnotherType:
    type: object
    properties:
      myProp:
        type: string
MyType:
  required:
    - date # ignored
  allOf:
    - $ref: '#/components/schemas/MyAnotherType'
    - type: object
      properties:
        date:
          type: string

Produces:
export interface MyAnotherType {
  myProp?: string;
}

export type MyTypeAllOf = {
  date?: string;
};

// Here MyType['date'] will be an optional field
export type MyType = MyAnotherType & MyTypeAllOf;

the required work at the schema level right now in the allOf. Don't know if it should also work there but probably

the required work at the schema level right now in the allOf. Don't know if it should also work there but probably

I think that it should because yaml compiles without any errors.


feat: add jwks access type to external token handler

Hey, I just made a Pull Request!

This pull request builds on BEP-07 to expand the ExternalTokenHandler to support a configured JWKS auth strategy. This allows external callers to use 3rd party authentication via JWKS, enabling greater flexibility in providing ways to auth with Backstage via signed tokens.
A potential area of improvement for future PRs would be to move the TokenFactory used in the tests into the backend-test-utils plugin, since it is used with near-identical patterns in the jwks.test.ts file, as well as plugins/auth-node/src/identity/DefaultIdentityClient.test.ts, and plugins/auth-node/src/identity/IdentityClient.test.ts.
:heavy_check_mark: Checklist

[X] A changeset describing the change and affected packages. (more info)
[X] Added or updated documentation
[X] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[X] All your commits have a Signed-off-by line in the message. (more info)

Will re-open with cleaner git history 😄


Remove briefcase specific workarounds

Needed by https://github.com/napari/napari/pull/5743
This removes Briefcase specific workarounds that were lingering in the code base, not needed anymore after https://github.com/napari/napari/pull/5804

The --prefix removal is straightforward. It would never be applied because running_as_bundled_app(check_conda=False) would always return False outside of a briefcase install.
The env var part is a bit more strange, but the gist is that it relied on $PREFIX/plugins being the install path for napari plugins, which is not the case anymore if we are not using briefcase installs.

cc @Czaki

Two re-runs made it pass heh

Two re-runs made it pass heh

But I suggest fixing it, as it may happen in any PR. You may try to check the approach from the main repository (fixtures that will detect dangling threads/processes_


permission denied error in hub container

Hello,
when creating a minikube with more than one node, I keep getting the below error:
$kubectl get pod
NAME READY STATUS RESTARTS AGE
hub-7dd77cd747-29sd5 0/1 CrashLoopBackOff 3 (37s ago) 2m10s
proxy-bffbd5c54-5x62h 1/1 Running 0 2m10s

$kubectl logs pod/hub-7dd77cd747-29sd5
[D 2023-12-12 11:33:46.056 JupyterHub application:902] Looking for /usr/local/etc/jupyterhub/jupyterhub_config in /srv/jupyterhub
Loading /usr/local/etc/jupyterhub/secret/values.yaml
No config at /usr/local/etc/jupyterhub/existing-secret/values.yaml
Loading extra config: 00-extra-config
[E 2023-12-12 11:33:46.468 JupyterHub app:3382]
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/jupyterhub/app.py", line 3379, in launch_instance_async
await self.initialize(argv)
File "/usr/local/lib/python3.11/site-packages/jupyterhub/app.py", line 2857, in initialize
self.load_config_file(self.config_file)
File "/usr/local/lib/python3.11/site-packages/traitlets/config/application.py", line 113, in inner
return method(app, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/traitlets/config/application.py", line 950, in load_config_file
for (config, fname) in self._load_config_files(
File "/usr/local/lib/python3.11/site-packages/traitlets/config/application.py", line 909, in _load_config_files
config = loader.load_config()
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/traitlets/config/loader.py", line 626, in load_config
self._read_file_as_dict()
File "/usr/local/lib/python3.11/site-packages/traitlets/config/loader.py", line 659, in _read_file_as_dict
exec(compile(f.read(), conf_filename, "exec"), namespace, namespace) # noqa
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/etc/jupyterhub/jupyterhub_config.py", line 497, in
exec(config_py)
File "", line 174, in
File "", line 215, in makedirs
File "", line 225, in makedirs
PermissionError: [Errno 13] Permission denied: '/mnt/exchange/course1'

best

Hey @bpfrd
that's a known issue of minikube. Please check out this post.
Basically you have to disables/enables some addons in minikube. Then you will also have to update your values.yaml, to use the csi-hostpath-sc storageclass.


Refactor virt controller template machine volumes

What this PR does / why we need it:
This PR refactors the virt-controller templating service, introducing a builder pattern to generate volume specification.
The ad-hoc generation of volumes for the virt-launcher pod is replaced by a builder pattern, allowing the customization of the launcher spec via options.
It provides a simpler, more explicit way to achieve the same thing - volume spec generation becomes easier to write, and a lot easier to read / reason about. Going forward, it even defines a solid ground to expand the functionality of volume spec generation, instead of forcing the developer to find the appropriate nested if else and put his adapter copied code there.
Finally, the added unit tests are a chance to clearly document how to configure each of the relevant options.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Following up on #7534.
Release note:

NONE

/uncc @rmohr
/uncc @vatsalparekh
/cc @brybacki

It is all good. I only have two meaningful comments. One about
			if _, isHotplugVolume := hotplugVolumes(vmiVolumeStatus, vmiSpecVolumes)[volume.Name]; isHotplugVolume {
and another about:
func addPVCToLaunchManifest(pvcStore cache.Store, volume v1.Volume, claimName string, namespace string, volumeMounts *[]k8sv1.VolumeMount, volumeDevices *[]k8sv1.VolumeDevice) error {

/retest

/cc

I see at least one place where emptyDirVolume() could be used: https://github.com/maiqueb/kubevirt/blob/e9ad1544a02b5a587f4be5cb791d035c25b727d8/pkg/virt-controller/services/template.go#L1170 Might as well tackle all the occurrences, WDYT?

Will do. Good catch.

/retest

/lgtm

/sig code-quality

/test pull-kubevirt-e2e-k8s-1.23-sig-compute-cgroupsv2

/test pull-kubevirt-e2e-k8s-1.23-sig-compute-migrations


Update llvm-sys and cargo_metadata.

rustc seems to be using llvm 8
rustc 1.35.0 (3c235d560 2019-05-20)
binary: rustc
commit-hash: 3c235d5600393dfe6c36eeed34042efad8d4f26e
commit-date: 2019-05-20
host: x86_64-unknown-linux-gnu
release: 1.35.0
LLVM version: 8.0

and i was getting build errors with cargo_metadata so I updated that too
error: proc-macro derive panicked
   --> /home/devel/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo_metadata-0.6.0/src/lib.rs:224:35
    |
224 | #[derive(Clone, Debug, Serialize, Deserialize)]
    |                                   ^^^^^^^^^^^
    |
    = help: message: unknown serde container attribute `transparent`

Interesting, I wasn't able to reproduce the error locally with the latest nightly. But anyway, dependencies maintenance is usually helpful! Thank you, I've published v0.1.10


the new .pb isn't work well

I do follow the way that Readme showed, but my new .pb is not work as same as .h5,I do not know the reason and also do not know how to fix it...It seems like no matter what image is delievered into the .pb，there is only one same output.

have you solved the problem? I also confused about this issue@yihengCoding

have you solved the problem? I also confused about this issue@yihengCoding

Yes, I made it. The reason is versons of python, keras, etc. are incompatible. Maybe u can check it for sure. Good luck!

@98-Jane

A lot of thanks! I will check it~@yihengCoding


Bundle error in build-storybook

Hi!,
I try to use storybook with my application, but when i use the build-storybook something wrong occurs. I must to say that npm run start-storybook works great, it's only a build fault.

I thought it was for my own configuration, but i pull this repository (concretly the official-storybook example in master), after an npm install, do an npm run build-storybook and try to open index.html with a webserver.
I don't know if i'm doing something wrong 😢

try to open index.html with a webserver

What exactly is the command that you use for it?

@Hypnosphi, I'm using Chrome Extension webserver.

Weird, works OK for me. You said "open index.html", but this extention only allows to specify directory

yep, i mean specified the bundle's directory and check the option "automatically show index.html" or open the url "/index.html".

Which npm version are you using?
npm -v

5.7.1

Yes, I use the same. But actually the correct way to build this example is this:
yarn install # using yarn is important because we use yarn workspaces feature
yarn bootstrap --core
cd examples/official-storybook
yarn build-storybook

$ yarn install && yarn bootstrap --core
yarn install v1.5.1
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
[3/5] 🚚  Fetching packages...
[4/5] 🔗  Linking dependencies...
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "jest-preset-angular ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^3.0.0 || ^4.0.0".
warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 > @storybook/addon-graphql ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.7.0 || ^0.8.0-b || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0".
warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 > @storybook/vue ><EMAIL_ADDRESS>has unmet peer dependency "css-loader@*".
warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 > angular-cli ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS><2.7".
warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 > @storybook/addon-graphql > graphiql ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.11.0".
warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 > @storybook/addon-knobs > style-loader ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^3.0.0 || ^4.0.0".
warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 > @storybook/addon-graphql > graphiql > codemirror-graphql ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.11.0 || ^0.12.0".
warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 > @storybook/addon-graphql > graphiql > codemirror-graphql > graphql-language-service-interface ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.11.0 || ^0.12.0".
warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 > @storybook/addon-graphql > graphiql > codemirror-graphql > graphql-language-service-interface ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.11.0 || ^0.12.0".
warning "workspace-aggregator-c018064b-82a5-4db0-9df1-dabae469d9a5 > @storybook/addon-graphql > graphiql > codemirror-graphql > graphql-language-service-parser ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.11.0".
[5/5] 📃  Building fresh packages...
✨  Done in 812.98s.
yarn run v1.5.1
$ node ./scripts/bootstrap.js --core
storybook info bootstrap Core & Examples (core)
storybook info bootstrap yarn workspace
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
success Already up-to-date.
storybook info bootstrap prepare
lerna info version 2.5.1
lerna WARN ECYCLE Encountered a cycle in the dependency graph.This may cause instability! Packages in cycle are: "@storybook/addon-a11y", "@storybook/addon-actions", "@storybook/addon-graphql", "@storybook/addon-info", "@storybook/addon-jest", "@storybook/addon-knobs", "@storybook/addon-links", "@storybook/addon-notes", "@storybook/addon-options", "@storybook/addon-storyshots", "@storybook/addon-storysource", "@storybook/addon-viewport", "@storybook/angular", "@storybook/polymer", "@storybook/react-native", "@storybook/react", "@storybook/vue", "@storybook/components", "@storybook/core", "@storybook/ui"
lerna WARN ECYCLE Encountered a cycle in the dependency graph.This may cause instability! Packages in cycle are: "@storybook/addon-a11y", "@storybook/addon-actions", "@storybook/addon-info", "@storybook/addon-jest", "@storybook/addon-knobs", "@storybook/addon-links", "@storybook/addon-storyshots", "@storybook/addon-storysource", "@storybook/addon-viewport", "@storybook/angular", "@storybook/polymer", "@storybook/react-native", "@storybook/vue", "@storybook/components", "@storybook/core", "@storybook/ui"
Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>Built<EMAIL_ADDRESS>lerna success run Ran npm script 'prepare' in packages:
lerna success - @storybook/addon-a11y
lerna success - @storybook/addon-actions
lerna success - @storybook/addon-backgrounds
lerna success - @storybook/addon-centered
lerna success - @storybook/addon-events
lerna success - @storybook/addon-graphql
lerna success - @storybook/addon-info
lerna success - @storybook/addon-jest
lerna success - @storybook/addon-knobs
lerna success - @storybook/addon-links
lerna success - @storybook/addon-notes
lerna success - @storybook/addon-options
lerna success - @storybook/addon-storyshots
lerna success - @storybook/addon-storysource
lerna success - @storybook/addon-viewport
lerna success - @storybook/angular
lerna success - @storybook/polymer
lerna success - @storybook/react-native
lerna success - @storybook/react
lerna success - @storybook/vue
lerna success - @storybook/addons
lerna success - @storybook/channel-postmessage
lerna success - @storybook/channel-websocket
lerna success - @storybook/channels
lerna success - @storybook/client-logger
lerna success - @storybook/codemod
lerna success - @storybook/components
lerna success - @storybook/core
lerna success - @storybook/node-logger
lerna success - @storybook/ui
✨  Done in 178.11s.

$ cd examples/
$ cd official-storybook/
$ yarn build-storybook
yarn run v1.5.1
$ build-storybook -c ./ -s built-storybooks
info @storybook/react v3.4.0-rc.3
info
info => Loading custom addons config.
info => Loading custom webpack config (extending mode).
info => Copying static files from: built-storybooks
cp: no such file or directory: built-storybooks/angular-cli
cp: no such file or directory: built-storybooks/cra-kitchen-sink
cp: no such file or directory: built-storybooks/polymer-cli
cp: no such file or directory: built-storybooks/vue-kitchen-sink
info Building storybook ...
info Building storybook completed.
✨  Done in 47.33s.

And i have the same result :S
here are my versions:
$ npm -v
5.7.1
$ yarn -v
1.5.1
$ node -v
v9.4.0

i detect other interesting thing:

Like you see in the image, if i go to iframe.html with specifics query params, works great.

In another case, adding some query params, the page breaks like i explained before

That's super weird. Which browser and OS is that? Can you please share what's shown in network tab of your devtools?

i know :S... Yep is chrome in MacOs.
Ofc, here it is:

I solve the error :S the webserver mod-rewrite was activated (for SPA)
Now works Perfectly

Thanks so much for you help!! and sorry for troubles :D

This error is happening on MacOS safari Version 11.1 (136<IP_ADDRESS>.4)
Storybook 3.4.8
It happens when serving the storyboard-static file using serve
serve -s storybook-static

@awgeorge You might already have found a solution for your issue, but for those still having problems:
go to the folder you want to serve and only run serve.
serve -s storybook-static rewrite all not-found requests to storybook-static/index.html and for some raison breaks Storybook rendering.


Increase pv with commodore configuration

Context
To increase elastic storage we currently need to

increase storage in commodore config and
increase pvc to actually increase the storage per CSI

Alternatives
If possible it would be nice if the commodore component increased the pv as well.

In either case, It would be nice to have this documented in a HowTo page

@DebakelOrakel @mhutter Does https://github.com/appuio/openshift4-docs/pull/151 solve your needs in this issue? It's available here: https://kb.vshn.ch/oc4/how-tos/logging/increase-elasticsearch-storage-size.html

That should do it


NuGet 4.0 RTM release notes and Known Issues

Committed them to master previously as opposed to 'live' branch. So merging changes to 'live' branch now.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/Release-Notes/Index.md
:white_check_mark:Succeeded

docs/Release-Notes/Known-Issues.md
:white_check_mark:Succeeded

docs/Release-Notes/NuGet-4.0-RTM.md
:white_check_mark:Succeeded

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


[C++] ReadTable status "not implemented"

Describe the usage question you have. Please include as many useful details as  possible.
Try load parquet file table with this code
arrow::MemoryPool* pool = arrow::default_memory_pool();
std::shared_ptr<arrow::io::RandomAccessFile> input;
ARROW_ASSIGN_OR_RAISE(input, arrow::io::ReadableFile::Open(fullpath));
// Open Parquet file reader
std::unique_ptr<parquet::arrow::FileReader> arrow_reader;
ARROW_RETURN_NOT_OK(parquet::arrow::OpenFile(input, pool, &arrow_reader));
// Read entire file as a single Arrow table
std::shared_ptr<arrow::Table> table;
auto res = arrow_reader->ReadTable(&table);
// ARROW_RETURN_NOT_OK(arrow_reader->ReadTable(&table));

ReadTable returns status Not Implemented. Arrow lib built as static with this options
cmake .. -DARROW_PARQUET=ON -DARROW_BUILD_STATIC="ON" -DARROW_BUILD_SHARED="OFF"  -DARROW_DEPENDENCY_SOURCE=BUNDLED -DARROW_DEPENDENCY_USE_SHARED=OFF -DARROW_FILESYSTEM=ON -DPARQUET_BUILD_EXAMPLES=ON

Default examples work fine.
Component(s)
C++

Could you show full error message?
I think that it include what is "not implemented".

Yes, there is message about gzip. It is not built.


Needs test for relative imports in a stache file

Need to add a test to make sure relative imports work, for example:
<can-import from="./app-state" />

Fixed in https://github.com/canjs/can-ssr/pull/35


Need to manually import ObjectExt

See e.g. https://github.com/sdroege/gstreamer-rs/blob/master/examples/src/bin/gtksink.rs#L6
It is re-exported from src/lib.rs, so not sure what is missing.

Strange, it imports fine for me with both use glib::* and use glib::prelude::* on stable and nightly.
I used .get_type() and .has_property("height", None) for test

Hm. As I remember Gst also have ObjectExt, try switch use.

It's re-exported as GstObjectExt though. But that's indeed the problem.
Niko suggested this is a compiler bug. So trying to create a test case now

Maybe for the time being, I'll just not autogenerate ObjectExt and rename it directly.

Same problem with ApplicationExt from GtkApplication and GApplication it seems...

Maybe we need add config trait_name to Gir?

I guess so

I'll probably get to that next week

Let's consider that closed then, as part of https://github.com/gtk-rs/gir/pull/430


nose and requests_mock required only for tests

Having these in install_requires means this program will not run without them installed. These could be added with tests_require, but I haven't seen a project use that.

Realized I broke the Travis build -- fixed now.


Change to not translate unique names

Same as #23964
An incorrect translation has been made in the localized version by machine translation.
※ Machine translation translates property name
Evidence: https://github.com/MicrosoftDocs/azure-docs.ja-jp/blob/live/articles/azure-monitor/insights/service-map.md
In the following files, it was made not to make mistranslation by putting proper names in "`".
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/role-based-access-control/custom-roles.md
This change(enclose property names by "`") has no negative effect on the English version.
Please accept this change so that property names are not mistranslated in each language in each localized version.
🙏

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

#sign-off

@changeworld - thanks for catching this!


Small amendment to DataLabelViewModel

The problem
The current DataLabel only allows accessing the Instance. While this is mostly sufficient, I was hoping it could store a ChartPoint instead, so that we can get more info such as Participation. The change is minor, mostly changing the code point.Instance to point in each of the series and a bit of refactoring. e.g. for ColumnSeries.
Thanks,
Enigmatrix

I like it, previous commit should add this feature and will be included since 0.9.7, plus you can also access the instance from a ChartPoint.


Workflow restore/load/import breaks after be08b0f

Getting the following error for any commits after be08b0f on my persistent workflow.
Loading aborted due to error reloading workflow data
TypeError: self.groupData.oldToNewWidgetMap[n] is undefined

GroupNodeHandler/this.node.onNodeCreated@http://<IP_ADDRESS>:8188/extensions/core/groupNode.js:922:26
createNode@http://<IP_ADDRESS>:8188/lib/litegraph.core.js:478:22
init/LiteGraph.createNode@http://<IP_ADDRESS>:8188/extensions/cg-use-everywhere/use_everywhere.js:260:35
LGraph.prototype.configure@http://<IP_ADDRESS>:8188/lib/litegraph.core.js:2215:38
#addConfigureHandler/LGraph.prototype.configure@http://<IP_ADDRESS>:8188/scripts/app.js:1416:22
init/LGraph.prototype.configure@http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/js/reroutePrimitive.js:14:29
init/LGraph.prototype.configure@http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/js/snapToGrid.js:69:21
loadGraphData@http://<IP_ADDRESS>:8188/scripts/app.js:1900:15

This may be due to the following script:
/extensions/core/groupNode.js

Reverting back to be08b0f via
git reset be08b0f --hard
fixes it but any subsequent update will break it again.
I am using multiple impact workflow components using rgthree in their innards and having to unpack every one, then repack, then fix inputs and outputs is a major undertaking.
Is there any way convert the bugging old version data to new version data by editing the json instead?

Hmmm.. I'm not sure why that change would cause an error here. Though, I'm not too surprised ComfyUI's groupNodes are where the error lies.
I don't really use the groupNodes in ComfyUI, but I just tried adding some with and without my nodes, but can't recreate this error.
Is it possible you could trim down your workflow into just a fews nodes that seem to cause the issue?

I apologize for it taking so long, I managed to trim the workflow down to a single component.
I've added packed and unpacked variants. The unpacked one loads with the newest rgthree - no problem.
The packed one however breaks and fails to even render the view properly and prevents all other nodes and components from loading.
workflow-1component - packed and unpacked.zip

I honestly don't know how you're using the comfy Group Nodes. They have never seemed to work for me. Even just now trying to get just a simple seed value passed through with an otherwise clean workflow doesn't work. I don't want to recommend you not use them directly, but I don't trust them to work myself.
Anyway, I did find the issue of why its not loading, thanks for the example. ComfyUI's Group Node code doesn't like that your example workflow has a groupNode configuration that has the Any Switch inputs marked as hidden. This is likely due to a recent change so the Any Switch, Context Switch and Context Merge now have dynamic inputs allow you to add infinite number of inputs to switch against, rather than the hardcoded limit at five.
Unfortunately, I can't fix it forward from rgthree-comfy since the issue is directly in ComfyUI's group nodes. I'm sorry, but you'll have to edit the JSON directly to remove the configuration data for these inputs.
In the workflow JSON, under the group's config JS object, you'll see something like this (where "4" here is the link id the group node has for the Any Switch):
"4": {
  "input": {
    "any_03": {
      "visible": false
    },
    "any_04": {
      "visible": false
    },
    "any_05": {
      "visible": false
    }
  }
},

Since these are now dynamic, the groupNode code doesn't like that they're styled too. You'll want to remove the entire "input" data object.

Alternatively, you could edit comfyui's code directly to allow your workflows with this issue to load by opening /comfyui/web/extensions/core/groupNode.js and find the line that looks like this (for me, it's line 922):
const widgetName = self.groupData.oldToNewWidgetMap[n][w];

And add a ?. in between the [n] and the [w] so it becomes:
const widgetName = self.groupData.oldToNewWidgetMap[n]?.[w];

Note, if there's an update to this line in the future, you may need to undo this change before git lets you update it, as it would think there's a conflict.

Thank you very much for the exhaustive explanation, I really appreciate it.
I was using the group nodes to minimize the screen space and links that certain sections require, hide the unneeded fields and inputs and make an overall cleaner look compartmentalizing functionally separate zones. It also helps me reduce connection line clutter which is so bad in my case that when I un-hide the connection lines the whole thing slows to a crawl and I can't stand that.
After considering how technically limiting using these groups is, however, and taking into account the new n-number of any switches and in the name of future compatibility I guess I'll just un-group them and stash their inner workings beyond the workflows borders. This will break importing previously generated images but at least will guarantee that future ones will not break like that. I'll just keep a frozen copy of the version that still loads them and be done with that.
Once again, thanks for taking time to look into this and for making this essential node collection as well.


Geographic feature clarify structure of zip files required.

I have a folder containing shapefile components.  I zipped this folder and tried to load it.  This did not load.  I was returned to the Create Resources page without any error message.  If it is required that shapefile components not be in a folder, then this needs to be documented and the system needs to generate an error message.

@dtarb
Good point! Current implementation requires the shapefiles not be in a folder. We need to change it. Most users have their shapefiles stored in folders and then zip up the folder directly since shapefiles are multiple files. Thanks.

This was fixed a while ago.


scroll bars should have larger minimum size

Currently scrollbars can be very small. They should have some minimum size, especially once they are interactive. I would take a look at some existing gui toolkits for guidance picking those sizes.

Fixed in https://github.com/linebender/druid/pull/688


C#: Implement readonly-ness in Array and Dictionary

Implement support for setting Arrays as readonly

Added to Core in https://github.com/godotengine/godot/pull/61127.
Expose IsReadOnly property that checks the read_only ptr in the engine array.
Add MakeReadOnly method.

There's precedent in System.Text.Json for a method MakeReadOnly that makes the JsonSerializerOptions readonly, there's no way to make it writable again.

Calls that mutate the Array when it's read-only will throw an InvalidOperationException like other read-only collections in .NET.

Implement support for setting Dictionaries as readonly

Added to Core in https://github.com/godotengine/godot/pull/61087.
Expose IsReadOnly property that checks the read_only ptr in the engine dictionary.
Add MakeReadOnly method.

Just like with Array, it makes the collection immutable but cannot make it mutable again after that.

Calls that mutate the Dictionary when it's read-only will throw an InvalidOperationException like other read-only collections in .NET.

This is pending changes to Core that may requisite changing the implementation of this PR (see https://github.com/godotengine/godot/pull/71845#issuecomment-1403715259).

Thanks!


Sync with the upstream

Fix to the following issues

https://github.com/servicemesher/istio-official-translation/issues/321
https://github.com/servicemesher/istio-official-translation/issues/316
https://github.com/servicemesher/istio-official-translation/issues/314
https://github.com/servicemesher/istio-official-translation/issues/311
https://github.com/servicemesher/istio-official-translation/issues/310
https://github.com/servicemesher/istio-official-translation/issues/309
https://github.com/servicemesher/istio-official-translation/issues/307
https://github.com/servicemesher/istio-official-translation/issues/306

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rootsongjc
If they are not already assigned, you can assign the PR to them by writing /assign @rootsongjc in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content_zh/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approve
/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fleeto
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content_zh/OWNERS [fleeto]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Clarify what occurs when basic.ack is sent for a message received by a consumer in 'no-ack' mode

Minor documentation omission in the AMQP protocol pages.
This might be a documentation omission for rabbitmq-server itself, I am not sure.
The protocol documentation (either quick reference or full reference) should clarify what behavior occurs when a basic.ack is sent for a message received by a consumer that is operating in no-ack mode.
Does this cause a failure? Is the basic.ack ignored? Even if this behavior is explicitly undefined/untrustable, a note should be added indicating that this is the case.

It results in a channel-level exception saying that a delivery tag isn't known to the channel.
Both protocol documents aren't updated any more and I don't think this is something that belongs to the errata page. I suspect we need a separate documentation page for consumer confirms.

That seems reasonable, thanks for the quick reply!
I've observed the failures on the versions of RabbitMQ I've used. I was mostly after documentation so that I and others can be a little more sure that the behavior will not switch from "error" to "undefined" in a future version.


[Core] Fix Race Conditions in CMsgSubscriber

Properly implement destructor (in inherited classes)! -> Destroy may not be called in base CMsgSubscriber class as this can lead to stack unwinding (most likely causes an exception in destructor, or leads to already deleted functions of derived class being called when they are already deleted)
Correct order of RemReceiveCallback and resetting internal pointer
protect function pointer with mutex.
Make testcase "harder" to more easily trigger race conditions.

Cherry-pick to

5.11 (old stable)
5.12 (current stable)

Fixes #1318


The structure of the dataset

Could you show how the stureture of the dataset should be? When I run your code, I alwayes encounter data loading problem as below:

You can see the structure of the dataset in the README as follows:
dataset
│
└───visual_genome
│   │
│   └───images
│       train.json
│       val.json
│       test.json
│       rel.json
│
└───open-imagev6
    │
    └───images
        annotations

Please note that all 100K images are in dataset/visual_genome/images.