withMiddlewareAuth - passing req, res to isPermitted

Feature request
Good day, is there a chance of a fast implementation, passing req, res to isPermitted (withMiddlewareAuth)?
By which it will be possible to build a little more advanced authGuard. It gives an example of what can be achieved with this and why it is so important. E.g. check if a user has a subscription and based on that give access to the panel, or send back to the subscription settings. Please let me know if we can implement this and add these 2 optional properties to isPermitted. Otherwise I will have to open a new custom project passing these properties. Needs under my project that I am writing for a client.

I think it is even better to pass supabaseClient, something like:
const supabaseClient = supabaseServerClient({ req, res })
await options.authGuard.isPermitted(authResult.user, supabaseClient)

From the next release onward, an authenticated supabase client with be returned in the isPermitted function, allowing you to run queries etc. You can already try it out with installing npm install @supabase/auth-helpers-nextjs@next and you can find the migration guide here: https://github.com/supabase/auth-helpers/blob/next/packages/nextjs/MIGRATION_GUIDE.md#migrating-to-03x


os: RemoveAll hangs on Windows when the directory tree contains files with non-UTF8-representable filenames

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

> go version
go version go1.19 windows/amd64

Does this issue reproduce with the latest release?
Probably, I haven't tested it personally.
What operating system and processor architecture are you using (go env)?
go env Output
> go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\paulh\AppData\Local\go-build
set GOENV=C:\Users\paulh\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\paulh\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\paulh\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.19
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set GOWORK=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=C:\Users\paulh\AppData\Local\Temp\go-build2524325924=/tmp/go-build -gno-record-gcc-switches

What did you do?
Called os.RemoveAll on a directory tree that contained a file with a name that is valid on Windows NTFS, but not representable in UTF-8.
A source of such files is the MSYS/Cygwin implementation of POSIX unlink in the case where the file is a running executable, e.g., an executable deleting itself or one of its DLLs, such as a pacman self-upgrade.
An example of such a call to os.RemoveAll is cleaning up temporary directories created during export of a Windows Containers filesystem layer.

TODO: Create a minimal repro. An existing unit test demonstrating this is https://github.com/microsoft/go-winio/pull/261/files#diff-fe0a7b5d46479d166aa0b717fbf33f61139084553170813c8d215edd960af249R117-R118
What did you expect to see?
The directory is deleted (or the call fails, I guess) and the code continues executing.
What did you see instead?
The same hang (infinite loop) as #36375, for roughly the same reason.
There's more details in that ticket, and particularly https://github.com/golang/go/issues/36375#issuecomment-1484123665 which explains how it applies in this case, and links on to the constellation of tickets where this issue has affected users.
In summary:

If os.RemoveAll sees IsNotExist when given a specific file, it assumes it was already deleted by some other process.

This does not return an error to the calling recursion, as it is considered "forward progress": The file is gone, as desired.

os.RemoveAll runs an unconditional for loop as long as the directory has contents and no errors were seen while deleting the contents, rescanning the directory on each iteration.
os.readdir on Windows (called via os.Readdirnames) incorrectly assumes all filenames are UTF16. Specifically, unpaired surrogates are valid in Windows NTFS filenames, but are folded into the replacement character by this assumption.
Such filenames, seen by the inner loop of os.RemoveAll, when converted back to the OS-level format are hence different from the filenames the OS knows of, and produce the IsNotExist seen in the first point, but breaking that code's assumption. and hence allowing the loop to repeat without forward progress.

The difference from #36375 is only that the reason the inner os.RemoveAll returns IsNotExist in that case was passing a too-long DOS-style path rather than an incorrect path. (As it happens, Win32 DeleteFile returns ERROR_FILE_NOT_FOUND when given a too-long path. #36375 was resolved by ensuring filenames are not too long to be passed to the Win32 DeleteFile API, but did not resolve the underlying infinite loop potential.)
I haven't tested this, but I'm pretty sure that a directory with the same kind of unusual name would trigger the same behaviour.
One amusing note is that if you delete the problematic file while the loop is hung, it'll unhang and resume without error.

A few solutions come to mind:

Detect when a filename can't be roundtripped via UTF-8 correctly, and report a failure like "Go doesn't support NTFS filenames that can't be represented in UTF-8". This could be applied across the os package's WIndows-specific code, i.e. anywhere we call syscall.UTF16ToString or similar, instead call UTF16ToStringButFailInsteadOfUsingTheReplacementCharacter.

This is the least-impactful change on behaviour, as it replaces a hang with an error, so the current range of working and non-working cases is unchanged.
This approach means callers will over time need to migrate to something like https://github.com/microsoft/go-winio/pull/261 as they receive bug reports for such filenames.
The number of places we call syscall.UTF16ToString is not small, and x/sys/windows would need to be looked at too.

Use WTF-8 as the encoding of strings created when reading or writing Windows directory entries, as this is designed as a UTF-8-like byte-oriented encoding that can represent all NTFS filenames.

This is consistent with the non-Windows platforms, which do not assume or check encoding on the byte-arrays in the dirents, but cast them directly to string, and will be least-surprising for users who are already handling the "Not UTF-8 filename" risk on other platforms.
This also provides the best chance that a caller of os.Readdir can pass the resulting file names into other os APIs successfully.
Same breadth-of-touching as the previous idea, but actually less intrusive logically as we no longer introduce a failure case for filename encoding conversion.

A Windows-specific os.RemoveAll implementation (e.g. take https://github.com/microsoft/go-winio/pull/261 upstream) would probably fix this entire class of errors by keeping the filenames in native format between reading the directory entries and recursing/deleting them. It would also take care of the long file path issue by using the \\?\ prefix naturally, rather than patching it in after-the-fact.

This doesn't help other callers, and the Path in any generated PathError would need to be converted to some byte-oriented format, which would still fail if error-handling code attempts to, e.g. os.Lstat it.

Detect in os.RemoveAll when the loop is not making forward progress in a way that is robust against why.

This fixes only this function, but would also have handled the long-filename case.
Again, turns a hang into an error, so minimised impact on behaviour.
It'd be a good idea to look into this anyway, but like the first point, it'll just force people to gradually move to external reimplementations that don't fail.

Declaring that the Go stdlib only supports UTF-8-representable filenames on Windows, and UTF-8 filenames on other platforms.

This provides the most user clarity, and requires changing no code.
This would be a nice clarity boots in the docs
Allows users to assume strings can be used to manipulate filenames freely.
This one seems like an unreasonable limitation on supported environments. an rules out Go for general systems programming.
This is here for completeness. Please don't do this one.

My preferred in-Go solution would be encoding all Windows filenames in string in WTF-8 (or a different, covers-all-possible-byte-strings encoding, of course. I'm not particularly tied to WTF-8 itself.)
I particularly dislike the options that push people to external reimplementations, as I'd prefer a solution that made https://github.com/microsoft/go-winio/pull/261 obsolete, not one that makes it widely necessarily, including requiring platform checks on multi-platform codebases.

Just to highlight, this problem only occurs on Windows because it's only on Windows that os is assuming the filenames can be roundtripped via UTF-8.
User code that attempted to implement something like os.RemoveAll or os.Walk by directly calling os.Readdir and also used strings to manipulate the filename strings would be vulnerable to similar issues on all platforms in the presence of non-UTF-8 filenames.

I think it would make sense for the syscall.UTF16 functions to convert to and from WTF-8 instead of enforcing UTF-8 validity. I expect that there would be essentially no backward-compatibility issues, since Go programs by and large do not check for UTF-8 validity explicitly and any program that uses replacement characters would end up with system calls that do not round-trip.
For backward compatibility, perhaps we could add a GODEBUG controlling this behavior.
@TBBle, shall we convert this to a proposal for a change in the Windows syscall package?

Today it is reasonably safe to [assume] that a Go string is a well-formed UTF-8.

I don't think that is actually true, though. Go's range loop over a string decodes UTF-8 runes, but nothing else requires or enforces that strings are valid UTF-8.
In particular, the os package today does not enforce UTF-8 validity for platforms other than Windows: https://go.dev/play/p/g02CkiBgUOz

Today it is reasonably safe to asume that a Go string is a well-formed UTF-8.

(2003 is RFC 3629, when encoding unpaired surrogates became invalid UTF-8 as part of shrinking Unicode from 31 bits to 21 bits. I've never checked to see if WTF-8 is just reinventing pre-2003 UTF-8, but I'd be mildly amused if that was the case.)
Also, per the documented "For information about UTF-8 strings in Go":

Some people think Go strings are always UTF-8, but they are not: only string literals are UTF-8. As we showed in the previous section, string values can contain arbitrary bytes; as we showed in this one, string literals always contain UTF-8 text as long as they have no byte-level escapes.

To summarize, strings can contain arbitrary bytes, but when constructed from string literals, those bytes are (almost always) UTF-8.

So in Go's case, they apparently intended "string can store arbitrary bytes", not "strings of unknown origin can be safely assumed to be UTF-8".

If we change syscall.UTF16 functions to work with WTF-8, then it will be unsafe to write a Go string coming from the os or syscall into an system that expects well-formed UTF-8 strings, as that property will no longer hold.

I was thinking more of a new set of functions that explicitly convert to and from WTF-8, and using those where the current UTF-16 functions are used for Windows filenames only. This is also how the Windows API works; apart from the filesystem APIs (which take raw uint16 arrays), the Win32 API is in UTF-16 (or a "globally"-specified 8-byte encoding for legacy APIs); so the only way for a non-UTF-16-valid filename to exist is by deliberately build those into a uint16 array.
Which is exactly what Cygwin has done, purely for the lolz.
In contrast, on Linux setting LC_CTYPE=ja_JP.SJIS (at the time of file creation, potentially years ago) means it's already unsafe to write a Go string coming from os.Readdir into a system that expects well-formed UTF-8 strings, and there's absolutely nothing in the POSIX API to discourage this. Heck, I downloaded a zip file containing a 2022 government document with SJIS filenames that unzip(1) will happily dump into the filesystem as-is, because today you can't tell it what encoding the filenames are in, nor what encoding you'd like.

windows.UTF16ToString and syscall.UTF16ToString are currently used in only a handful of places, and it has the property that if the UTF-16 buffer is valid UTF-16 then the result is valid UTF-8.
Its specification is:
// UTF16ToString returns the UTF-8 encoding of the UTF-16 sequence s,
// with a terminating NUL and any bytes after the NUL removed.

which to me says that the behavior for a non-UTF-16 sequence is unspecified. So I would argue that changing them to return a WTF-8 string is simply defining behavior that was previously (defined as) a programmer error — that is, the programmer failed to validate the UTF-16 string as required before passing it to UTF16ToString.

The arguments in favor of using WTF-8 in syscall.UTF16 are compelling. I'll try to prepare a CL adding an internal WTF-8 package to get some more knowledge about it.

I've submitted CL 493036 with a minimal WTF-8 implementation that has been pluged-into the syscall package. It looks good, although I had to copy a bunch of code from the utf8 package. The issue seems to be solved, though.
@kevpar @TBBle could you try CL 493036 to see if it fixes your cases? You can download it using gotip download 493036.

Good news. I confirmed a dockerd.exe built with Go 1.20.4 reproduces the hang (and unhangs when I delete the two problematic files), and when built with gotip download 493036's gotip, it no longer hangs.
Hang:
Server: Docker Desktop 4.17.1 (101757)
 Engine:
  Version:          0.0.0-dev
  API version:      1.41 (minimum version 1.24)
  Go version:       go1.20.4
  Git commit:       6051f14291-unsupported
  Built:            05/06/2023 05:02:47
  OS/Arch:          windows/amd64
  Experimental:     true

No hang:
Server: Docker Desktop 4.17.1 (101757)
 Engine:
  Version:          0.0.0-dev
  API version:      1.41 (minimum version 1.24)
  Go version:       devel go1.21-373489978b Fri May 5 18:29:34 2023 +0200
  Git commit:       6051f14291-unsupported
  Built:            05/06/2023 05:00:53
  OS/Arch:          windows/amd64
  Experimental:     true

So the fix works for me.

Is there any chance this fix will migrate backwards to older Go versions?

I'm not even sure if this will get into go1.21, code freeze is happening in a couple of weeks and this issue haven't got much traction yet.
If we backport something, IMO it shouldn't be CL 493036 but something less invasive, like avoiding the infinite recursion in os.RemoveAll.
@golang/windows  @alexbrainman

That makes sense. And just avoiding the infinite hang (with presumably some kind of error we can recognise) will give callers something to react to now.
That said, perhaps if we want a less-intrusive patch for backporting, having an "unprocessible name" error or something would be nice and explicit; this could perhaps be a round-trip-test immediately after UTF-16 decoding. A "this call got stuck" error might still have other triggers lying around, although I guess the caller would handle it the same way anyway no matter what the cause? (In the case I'm involved with, it's a cleanup that fails after a successful operation, I'm not sure we even check the error).


vscode crashes with the following error: [UtilityProcessWorker]: terminated unexpectedly with code 82, signal: unknown

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.95.3
OS Version: 22.04.2 LTS (Jammy Jellyfish)

I'm running vscode in an ubuntu container on an ubuntu linux machine. I suffer from frequent crashes, especially when resizing windows.
The easiest way to reproduce is to have 2 or 3 vscode sessions running, however, it can also occur when a single vscode session is open.
Steps to Reproduce:

Launch the first vscode session, open a project folder, open some files and maximize the window.
Launch the second vscode session, open a project folder, open some files and maximize the window.
Launch the third vscode session, open a project folder, maximize the window and open some files. It should then crash.

I'm running with the --disable-extensions option and also tried the --disable-gpu option.
When running on the machine itself outside the container, I wasn't able to reproduce the issue.
I'm attaching the crash log file to this ticket. I also have the crash dump files, however, before I attach them I will need your confirmation that they do not contain parts of my code.
Thanks,
Meir
main.log

main.log

Thanks for the log, the crash dumps are of minidump format and only contain stack memory of the VSCode application which will not have reference to your code from the editor.

Thanks. I attached them here.
crash.tar.gz

Sorry for that. I reproduced again and this time the log contains the dump files.
In this repro all 3 sessions crashed but only one of them produced the .dmp log files.
crash.tar.gz

Crash comes from unable to allocate share memory for the compositor. Please try the following and share the results,

Does the application crash when you run with --disable-dev-shm-usage
Start the application with code --verbose and share the full log without truncating when the crash happens
What is the configured size of /dev/shm in the container ?

Thanks very much.
In initial testing I wasn't able to reproduce the crash.
Currently the configured size for /dev/shm is 64MB.  What would be the recommended size for vscode to run without crashing?

We don't have recommended size defined for shm as it varies with the renderer pages and the requirement comes from the runtime. I would suggest to try with 2g.


feat: ansible 2.15.1

Which issue(s) this PR fixes

Fixes #280 and #263
Additional comments

Use ansible-core 2.15.1
Install collection dependencies on ansible_dependencies through the setup script and requirements.yml

Agreements

[x] I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004.
[x] I hereby agree to grant TOSIT a copyright license to use my contributions.

I dont think we should accept the PR as is. The instructions in the README are not in sync with the current configured submodules (even after https://github.com/TOSIT-IO/tdp-getting-started/pull/286). For example tdp plan dag is not implemented in stable.
I understand the need of the PR (add instructions for the current stable tdp-lib and ansible 2.15) but it should include the bump in the submodules as well to work.
I suggest we this PR to a dev branch, this way people who git clone master will have a working version.

@rpignolet @PaulFarault I added the dev branch where this should be merged. Also added a note on the top of README.md warning that it's a dev branch and some components may not work correctly (currently it's server and ui, but may be something different at an other point).


(Wizard2.0-Bug)  Last deployment transaction ( CrowdsaleConsole.initializeCrowdsale) failed if start/end time changed before deployment

Steps for reproduce:

Open wizard https://5ae0d38fc9659230d752d6bc--architect-coin-64174.netlify.com/
Set parameters: decimals =18, rate =1000, supply =200, others by default
Set start time(or end time) other than default.
Finish deployment

Actual result:

last transaction(Initialize Crowdsale ) reverted  https://ropsten.etherscan.io/tx/0xf3a406f832769d3dd12c44325413165fa0f543d0c4a18f4b3fe68c94df19f038
impossible to invest any amount , all transaction reverted

Expected result:

should be allowed create crowdsale with any valid parameters

If you are reporting a problem with Token Wizard, please include the following information:
Ropsten
Your answer
If you were able to create it, what is the URL of your crowdsale?
*https://5ae0d38fc9659230d752d6bc--architect-coin-64174.netlify.com/invest?exec-id=0xa93808b293b51989c05b78c971c7081f62fe7e9b30c2f7dd5e41c15025f487fb&networkID=3
*
Do you have screenshots showing the problem?

reverted purchase transactions
https://ropsten.etherscan.io/tx/0x0a7b5a6854e2757cad970a99563856521120955ab8140adaa86454473a3515b6
https://ropsten.etherscan.io/tx/0x4b1068deec49d4f8ca19fb2214166652706563068ed551495b0e8684e2606d51
https://ropsten.etherscan.io/tx/0x71c239a4ef21423e4d951b7778ae17b2f57c3e8c5aa6fd986bb83cd776b14402
Do you see errors in the dev console? If yes, please include a screenshot
No
If you see errors, please right click on them and "Save as..". Zip saved file and attach it to the Issue.
No

Yes, cause of this issue that last deployment transaction executes when the 1st tier was already started. It is not bug


Failure when creating Hello world docker

Expected behavior
for it to connect and work
Actual behavior
(HTTP code 401) unexpected - {"message":"Get https://registry-1.docker.io/v2/kitematic/hello-world-nginx/manifests/latest: unauthorized: incorrect username or password"}
Information about the Issue
I believe I have the correct password and username
Steps to reproduce the behavior

...Create the Hello World Doc
...Comes up immediately

Nevermind...I fixed it by logging in with my username instead of my email address.

closing issue


Too long

Resources take forever to load in this tutorial, why don't use simplified set of examples?
I have wasted more than half-an hour and still I'm not done. This is the perfect example of MS inefficiency, when it comes to cost of time and money.
BigQuery is much simpler.

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

ID: d26e70c3-2769-5b47-2bda-8a4a7f0239d0
Version Independent ID: 558a36bd-e151-1e4c-4427-fc52eb2d91e3
Content: Tutorial: Load data to Azure SQL Data Warehouse
Content Source: articles/sql-data-warehouse/load-data-wideworldimportersdw.md
Service: sql-data-warehouse
GitHub Login: @Ckarst
Microsoft Alias: cakarst

@bfgr Thank you very much for sharing the user experience. We are investigating this and will evaluate the tutorial for improvement.
Regards,
Mike

The tutorial could be shortened with an ARM template to consolidated the configuration process but, the tutorial itself goes over a lot of valid and useful content pertaining to the use and functionality of the product. Perhaps a short and long version, or ARM version and manual version of the tutorial would be useful here.

@mike-Ubezzi please assign to @kevinvngo

I believe the problem does not come from the amount of steps, that I actually find quite informative (i.e. creating a loader user, etc). The real problem is, this tutorial would not be able to be completed in several hours as the final steps will be churning for hours (I was using a Gen2: DW400c) , on the step "Generate millions of rows" in specific the call to the sproc Configuration_PopulateLargeSaleTable, the culprit of the performance hog is the "ORDER BY [Sale Key]" over the large dataset [wwi].[seed_Sale].
There are several things that could be done to expedite this process within minutes while still keeping a workload for the example, being the first point the one that impacts the most:

Eliminate the artificial enlargement of [wwi].[seed_Sale] through the sproc InitialSalesDataPopulation . This steps just copies over an over the table making it x8 times the initial row.
One of the goals of Configuration_PopulateLargeSaleTable, is to populate [wwi].[fact_Sale] with a pseudo rando number of rows per day, for the purpose of the example it might not be too terrible if most of those rows are similar each day (just the quantity of them would vary), so we can eliminate altogether the costly WHERE condition when inserting into the [wwi].[fact_Sale].
Reducing the call to populate roughly 10k rows per day instead of 100k, this will still render millions per year (EXEC [wwi].[Configuration_PopulateLargeSaleTable] 10000, 2001)

Lastly, depending on the SKU chosen at the beginning,  having completed a whole year of rows population through Configuration_PopulateLargeSaleTable is not really needed to progress to the next steps. Maybe we can change the step 3 under "Generate millions of rows" to provide a better view on each day processed, and put a note this process could be cancelled after a few days have been processed if needed and can progress to the next steps :
SELECT [Invoice Date Key] , COUNT(*) AS RecordsPerDay
FROM wwi.fact_Sale
GROUP BY [Invoice Date Key]
ORDER BY [Invoice Date Key]
Thanks!

@gunnarcms Thank you for the detailed explanation of this issue. I will work with the author to reduce the time to run this tutorial.

@gunnarcms @dataify Thankyou for your input on this issue. We have created a work item to track updates to this tutorial. You will be notified once we make the update. I will proceed with closing out this Git Issue, but please feel free to respond should you need anything further. Thanks!

@kevinvngo

work item

#please-close


add link to google drive folder (#349)

Look for a folder in the folder given by env variable called "FOLDER FOR HUMANS". Create it if it does not exist
Add an url redirect to human folder. This is hunt specific since we'll eventually want it that way anyways.
add button on hunt page:

now it look like this

now it look like this


Allow Comment only entries

Hi,
I tried to add a comment only entry (just took a note where I took my medication)  sadly that's not possible yet. would be very handy to have though.
Best
Amie

Thanks for the good idea Amie. I didn't think people would try that, but you proved me wrong. Might add a separate line to the graph and make it appear differently in the list.


Issues doesn't seem to be working for Objective-C

I'm working with Objective-C in Nova and I'm not seeing issues like I do in Xcode. If I open my .m file in Xcode I see issues like "Unused variable" warnings for example, popping up at the edge of the editor. But I see no such warnings in Nova. I keep switching back over to Xcode while editing so I can see the issues.
Is this supposed to be a feature of Icarus or no? Is there something else I need to do to get it working? I have Xcode and its command line tools installed.

Now that I think about it, I'm not getting any completions either in Objective C. Something is definitely not working. Syntax highlighting is good though.
Trying it out with Swift. I am seeing some issue notices in Swift, and some completions, but definitely not all that Xcode has. Maybe that's by design? Just not sure if something is wrong.

Ok nevermind, I am seeing issues appear in the sidebar at build time when there are build errors. I am not seeing them interactively as I'm editing however, like in Xcode. It seems Xcode might be continuously building in the background or something in order to show the issues.
Also suddenly started seeing some completions in Objective-C too. Not sure why they came back. Might be some intermittent issue.
I'm also seeing the language server crash often and notifying me to restart it.

Ok Objective-C seems to be working pretty consistently now, with issues showing up after build, and completions showing up. The difference seems to be that I don't have Xcode also running in the background with the same project and files open. Xcode running at the same time seems to screw it up.


Validate and update manage applications

match update app page to prototype

add working service to interact with api

update validator

add all relevant unit tests

FA-786

I don't know if those changes are going to get push back as the team might prefer your way.


Is there a static tile?

Is there a static tile for just displaying specific data?
like
header
line1
line2

or anything similar?

Hello !
Not realy, but you can query texte file with HTTP-TILE and host this file with small http server.


Problems installing with Enterprise editions

When installing Draw2Script using an Enterprise ID, the install fails with a problem in the manifest where the version does not match.
Using a personal ID on the same version of Illustrator works.

@CodeCrow Sorry for never getting back to you.
I don't have access to an Enterprise ID so I am unable to reproduce this problem.  Are you still encountering this?


Tween.delay no longer working in 2.2.0

Going from 2.1.1 to 2.2.0, Tween.delay no longer works for me. I have not tried it on other versions.

https://github.com/photonstorm/phaser/commit/02ef1555c56461f9b6fb207fc0b79ae6b2d01d66


NullPointerException while getting invalid gamemode

I get a NullPointerException when I request an invalid gamemode, while it should just return Optional.empty().
Example error:
http://pastebin.com/wYQuH9AC
This is caused by this line:
https://github.com/SpongePowered/SpongeCommon/blob/9e6acff2f9c25f346151420d368a26a0e3578a5b/src/main/java/org/spongepowered/common/registry/type/entity/GameModeRegistryModule.java#L50
Optional.of() should be replaced with Optional.ofNullable()
I did not check if this bug is in any other registry module.

See also: https://github.com/SpongePowered/SpongeCommon/issues/739

I wouldn't consider this an OCD issue, considering it actually breaks stuff, but I might be wrong.


Authenticatable Contract for User model

Hi Barry,
I have updated config so that it will map Authenticatable contract rather than UserInterface for the App\User model by default.
Thanks,
Matt

Thanks


Update porting-guides.md

Changed "Windows x86" to Win32

Docs Build status updates of commit f918b19:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/porting-guides.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Surpport the value network and policy network share the same parameters in tensorforce?

Hi all, I'm a new hand at RL, tensorforce is very good for our freshes. After trying some experiments on tensorforce, I have some puzzles as follows:

Is the value network and policy network share the same parameters except last layer for actor critic algorithm, for example PPO?  From the code, the policy network and baseline doesn't share parameters.
PPO optimization uses a multi-step optimizer, repeat optimizing a same batch n-step times. According to the paper, sampling a different minibatch from that batch at each optimizing step seems better?
Is a bug for running_standardize.py? It seems that tensor has no attribute "astype". maybe need to change the numpy code to tensorflow operation.

You can enable this by using baseline mode network
This will be changed again once memories have been moved into the Tensorflow graph (as opposed to python code use pure TensorFlow code), see our blogpost, before that sub-sampling from the batch does not integrate well into the new architecture.
Running standardize was only experimentally added recently, has not been moved into TensorFlow graph, so only normalize, standardize, grayscale, sequence, clip, divide, image_resize
are supported, but feel free to move this into the graph.

Thanks @michaelschaarschmidt reply,  I'm eager to wait for the new end-to-end architecture!


Uncaught RangeError: Maximum call stack size exceeded

When I using this array of data:
const chartDataTest = [     { from: 'User1', to: 'User2', flow: 23.67 },     { from: 'User1', to: 'User3', flow: 25.33 },     { from: 'User1', to: 'User4', flow: 41 },     { from: 'User1', to: 'User5', flow: 31.33 },     { from: 'User1', to: 'User6', flow: 11.33 },     { from: 'User1', to: 'User7', flow: 15.13 },     { from: 'User1', to: 'User8', flow: 2.67 },     { from: 'User1', to: 'User9', flow: 1.1 },     { from: 'User1', to: 'User10', flow: 8 },     { from: 'User1', to: 'User11', flow: 18.33 },     { from: 'User1', to: 'User3', flow: 52.33 },     { from: 'User1', to: 'User12', flow: 5.33 },     { from: 'User1', to: 'User13', flow: 16 },     { from: 'User1', to: 'User14', flow: 18.33 },     { from: 'User1', to: 'User7', flow: 16.67 },     { from: 'User1', to: 'User14', flow: 0.67 },     { from: 'User1', to: 'User4', flow: 0.43 },     { from: 'User1', to: 'User8', flow: 1 },     { from: 'User1', to: 'User11', flow: 4 },     { from: 'User1', to: 'User10', flow: 2.47 },     { from: 'User1', to: 'User15', flow: 48.87 },     { from: 'User1', to: 'User7', flow: 9.13 },     { from: 'User1', to: 'User12', flow: 6 },     { from: 'User1', to: 'User10', flow: 3.13 },     { from: 'User1', to: 'User14', flow: 22.67 },     { from: 'User1', to: 'User7', flow: 2.53 },     { from: 'User1', to: 'User8', flow: 3.67 },     { from: 'User1', to: 'User4', flow: 41.43 },     { from: 'User1', to: 'User5', flow: 20.33 },     { from: 'User1', to: 'User6', flow: 5.03 },     { from: 'User1', to: 'User3', flow: 52.5 },     { from: 'User1', to: 'User16', flow: 1.7 },     { from: 'User1', to: 'User1', flow: 1.33 },     { from: 'User1', to: 'User1', flow: 4.33 },     { from: 'User1', to: 'User6', flow: 15.67 },     { from: 'User1', to: 'User14', flow: 6.17 },     { from: 'User1', to: 'User9', flow: 6 },     { from: 'User4', to: 'User17', flow: 17.33 },     { from: 'User5', to: 'User12', flow: 1.33 },     { from: 'User6', to: 'User10', flow: 2.13 },     { from: 'User7', to: 'User17', flow: 19.67 },     { from: 'User9', to: 'User4', flow: 3.33 }   ];
I'm getting error:
chartjs-chart-sankey.esm.js:109 Uncaught RangeError: Maximum call stack size exceeded     at nodeCount (chartjs-chart-sankey.esm.js:109:1)     at chartjs-chart-sankey.esm.js:109:1     at Array.reduce (<anonymous>)     at nodeCount (chartjs-chart-sankey.esm.js:109:1)     at chartjs-chart-sankey.esm.js:109:1     at Array.reduce (<anonymous>)     at nodeCount (chartjs-chart-sankey.esm.js:109:1)     at chartjs-chart-sankey.esm.js:109:1     at Array.reduce (<anonymous>)     at nodeCount (chartjs-chart-sankey.esm.js:109:1)
when I reduce array in half everything works fine.

{ from: 'User1', to: 'User1', flow: 1.33 } This is very likely the problem. As it is in the latter half of the array it works when you cut it in half.

Thx @MauriceHartmann for reply, I removed that same users from and to, but still getting same error.
I'm using array that has 584 records :(

I can only test your provided example. Have you also removed { from: 'User1', to: 'User1', flow: 4.33 }?
Interestingly your example worked for me, if I set priority: {} as dataset option. That also fixed a visual bug for me. So you can try that too.

I tried, but same error, sorry I ask and I can provide you data: https://kkatusic.com/testdata.txt
you can check it and try it. Thx

Took a quick look and the data does not contain any direct loops.
I'll take a closer look with the provided data.

So the data is circular. After preventing the error, it looks like this (anonymized):


Retry on connection refused

Curl fails immediately (skipping retries) when connection on the port is refused. Might make sense to add --retry-connrefused?

@Jtalk sorry, this was meant for https://github.com/Jtalk/url-health-check-action


coconutbattery v3.3

Thank you for the contribution. It needed some fixes, so they were made in fa43f91dcd019582045a5073da5408efd843db85. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


[Codebundle] GCP Cloudrun Healthcheck

Scope
An SLI which periodically checks if a cloudrun workload is in a healthy state, returning a metric of 1 when healthy and 0 when unhealthy.
Requested By (Optional)

RunWhen

Related Integrations

GCP Cloudrun

Definition of Done

[ ] Codebundle Implementation accomplishes scope (or provide a justification for why it may differ)
[ ] Attach a screenshot of the codebundle pushing a metric locally (if an SLI) or showing a report (if a taskset)
[ ] Attach a screenshot of the SLI or Taskset running in a workspace.

Optional Comments

This codebundle request and detail history is being migrated to an internal tracking tool for authors. Please reach out to the RunWhen team if you have any questions.


Open Nuxt Example URL after clicking on Sveltekit Example Github

when user clicks on : Website - View on Github
This Redirects to Nuxt Example : Github
This should redirect to Svelte-Kit Example : Github

fixed


Improve naming & consistency for bin packing features

During the workshops that @SHKnudsen led, customers identified that the naming & consistency of BinPacking features is not very clear and should be improved.

Sample feedback

Input: Rectangles vs. rects

Name: BinPacking.Rectangles

Binpacking.Cuboid vs Pack3D

The name does not make sense: RectanglePacking or SpacePacking sounds better

Inputs: outer rectangle, number of rectangles, the rectangles (change inputs names)

Node name could be rectanglepacking.2dpacking

Bin = Container bin or outline

Rects = Rectangles or shapes or…

Input names are not clear enough (bin = container)

Consistency on order of inputs: Bin, items vs Items, Bin`

Inputs: change rects for rectangles, change bins for container/area/space

Bin terminology does not make sense (use container)

Proposed improvements

[x] rename BinPacking to Packing
[x] rename Pack2D to PackRectangles
[x] rename Pack3D to PackCuboids
[x] rename input ports : Bin>Container, rects > rectangles or items
[x] consistent order of inputs : Items, Container, (options)

Things look good in Dynamo now :

Things look good in Dynamo now :


Manually selected related products

Is your feature request related to a problem? Please describe.
Sometimes merchant should select manually the related products to show on product page.
Describe the solution you'd like
Following product object, with showcaseType === 'related', recommendations-shelf.ejs should check current product related_products array:
<%
const relatedProducts = _.state.related_products && _.state.related_products.find(relatedProducts => {
  return relatedProducts.product_ids.length
})
if (relatedProducts) {
  // do not fetch Graphs API
  // use `relatedProducts.product_ids` instead
} else {
  // keep fetching related products IDs from Graphs API
}

Describe alternatives you've considered
N/A
Additional context
Next admin release.

cc @sameoldcarlos


Configure gradle build scan plugin

This small PR configures the build-scan Gradle plugin (https://guides.gradle.org/creating-build-scans/) which yields further insight into the build, allowing the team to make informed decisions on where and when the build may be tweaked to get faster, more performant builds.
If this PR is accepted then scan generation must be enabled on the command line, like so
./gradlew build -Dscan=true

Codecov Report

Merging #132 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #132   +/-   ##
=========================================
  Coverage     80.36%   80.36%
  Complexity      242      242
=========================================
  Files            14       14
  Lines           764      764
  Branches        129      129
=========================================
  Hits            614      614
  Misses           87       87
  Partials         63       63

Continue to review full report at Codecov.

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

Codecov Report

Merging #132 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #132   +/-   ##
=========================================
  Coverage     80.36%   80.36%
  Complexity      242      242
=========================================
  Files            14       14
  Lines           764      764
  Branches        129      129
=========================================
  Hits            614      614
  Misses           87       87
  Partials         63       63

Continue to review full report at Codecov.

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

Thanks for the PR. Is it correct that the build-scan plugin does not need to be applied from Gradle 4.3 upwards? If yes, then this change is actually not necessary because we'll use at least 4.10 in the upcoming gradle-download-task 4.0.0 (see branch gradle-3.0)

Yes, that’s the case. However you have to manually accept the terms of service every single time you run a build with —scan. This defeats the purpose of running scans on CI.
Do let me know how you’d like to proceed.

OK. It seems I should read the terms of service then 😁I'll get back to you.


Sequelize v5

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6d906ef). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   69.07%
=========================================
  Files             ?        4
  Lines             ?      152
  Branches          ?        0
=========================================
  Hits              ?      105
  Misses            ?       47
  Partials          ?        0

Impacted Files
Coverage Δ

lib/backend.js
96.55% <100%> (ø)

Continue to review full report at Codecov.

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


internal error: entered unreachable code

I am getting this error at ParseToken; the value is None.
It appears here when multiple rows are returned (gets fixed by using TOP 1).

I'll try to get this reproduced.
multiple rows alone don't seem to cause this (thats covered by tests)
maybe related to multiple rows & columns and not only small data.
If you have a small query to reproduce (preferably without any tables,
e.g. just a union select, as in all test cases), that'd be helpful.

Thanks, will try.

I can confirm this is somehow related to the amount of data returned. This happens when the number of rows returned is over some threshold.

@davidpodhola
Can you test again?

Sure, but the tiberius update updated chrono too and now I am getting
the trait tiberius::types::FromColumnData<'_> is not implemented for chrono::NaiveDateTime
Any advise? Thanks!

You'll have to update chrono in your cargo.toml aswell, did you already try that?

Sorry, overlooked one, thanks. And yes, it is fixed, very happy, thank you very much!


LayoutBuilder's descendant widgets should not rebuild more than once in the same frame

  testWidgets('LayoutBuilder rebuids twice', (WidgetTester tester) async {
    int built = 0;
    final target = LayoutBuilder(
      builder: (context, constraints) {
        return Builder(builder: (context) {
          built += 1;
          MediaQuery.of(context);
          return const Placeholder();
        });
      },
    );
    expect(built, 0);

    await tester.pumpWidget(MediaQuery(
      data: const MediaQueryData(size: Size(400.0, 300.0)),
      child: Center(
        child: SizedBox(
          width: 400.0,
          child: target,
        ),
      ),
    ));
    expect(built, 1);

    await tester.pumpWidget(MediaQuery(
      data: const MediaQueryData(size: Size(300.0, 400.0)),
      child: Center(
        child: SizedBox(
          width: 300.0,
          child: target,
        ),
      ),
    ));
    expect(built, 2);
  });

The following TestFailure was thrown running a test:
Expected: <2>
Actual: <3>

This came up again in https://github.com/flutter/flutter/pull/143249: we can't use a LayoutBuilder to get the incoming constraints because a google internal test failure caused by this.
This becomes problematic when a disposable object (such as a controller) is passed down the widget tree as a widget parameter, across the LayoutBuilder boundary:
ControllerOwner -> LayoutBuilder -> IntermediateWidget -> ControllerUser.
If ControllerUser rebulids without IntermediateWidget rebuilding (as seen in the test), it may keep using an outdated / disposed controller.

I was able to replicate this using the test code provided.

 stable, master flutter doctor -v
[!] Flutter (Channel stable, 3.19.5, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.19.5 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 300451adae (4 days ago), 2024-03-27 21:54:07 -0500
    • Engine revision e76c956498
    • Dart version 3.3.3
    • DevTools version 2.31.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.22.0-5.0.pre.55, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 3.22.0-5.0.pre.55 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ddf79b755d (6 hours ago), 2024-04-07 18:34:24 -0400
    • Engine revision c10e950c66
    • Dart version 3.5.0 (build 3.5.0-18.0.dev)
    • DevTools version 2.34.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/dhs/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] IntelliJ IDEA Ultimate Edition (version 2021.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 65.1.4
    • Dart plugin version 213.7228

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.29.0

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 15.3.1 19D52
    • macOS (desktop)           • macos                                    •
      darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 109.0.5414.119

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Another case of this issue:
testWidgets('duplicate GlobalKey false positive', (WidgetTester tester) async {
  final widgetKey = GlobalKey(debugLabel: 'widget key');
  final widgetWithKey = Builder(builder: (context) {
    Directionality.of(context);
    return SizedBox(key: widgetKey);
  });

  await tester.pumpWidget(
    Directionality(
      textDirection: TextDirection.ltr,
      child: Row(
        children: [
          LayoutBuilder(
            builder: (context, constraints) => widgetWithKey,
          ),
        ],
      ),
    ),
  );

  await tester.pumpWidget(
    Directionality(
      textDirection: TextDirection.rtl,
      child: Row(
        children: [
          LayoutBuilder(
            builder: (context, constraints) => const Placeholder(),
          ),
          widgetWithKey,
        ],
      ),
    ),
  );
});

The framework would incorrectly report that there were duplicate global keys:

The following assertion was thrown while finalizing the widget tree:
Duplicate GlobalKey detected in widget tree.

because the widgetWithKey builder will run twice during the second pumpWidget.

I tried to handle cases where layoutbuilders are involved https://docs.google.com/document/d/15U1XDLrP-SXfgeu5DBBsA7MQuFpDUW005Y2ObwmYWIc/edit#heading=h.pub7jnop54q0
looks like i missed some use cases?

I tried to handle cases where layoutbuilders are involved https://docs.google.com/document/d/15U1XDLrP-SXfgeu5DBBsA7MQuFpDUW005Y2ObwmYWIc/edit#heading=h.pub7jnop54q0
looks like i missed some use cases?

I think in this case it's actually worse than an incorrect assert. The final widget tree is incorrect with the LayoutBuilder double rebuild. The example from https://github.com/flutter/flutter/issues/146379#issuecomment-2084598835 generates the following widget tree:
      └Directionality(textDirection: rtl)
       └Row(direction: horizontal, mainAxisAlignment: start, crossAxisAlignment: center, dependencies: [Directionality], renderObject: RenderFlex#860c2)
        ├LayoutBuilder(renderObject: _RenderLayoutBuilder#d1a04 relayoutBoundary=up1)
        │└Placeholder
        │ └LimitedBox(maxWidth: 400.0, maxHeight: 400.0, renderObject: RenderLimitedBox#2a215 relayoutBoundary=up2)
        │  └CustomPaint(renderObject: RenderCustomPaint#d44b0 relayoutBoundary=up3)
        └Builder(dependencies: [Directionality])

while the correct tree should look like this:
      └Directionality(textDirection: rtl)
       └Row(direction: horizontal, mainAxisAlignment: start, crossAxisAlignment: center, dependencies: [Directionality], renderObject: RenderFlex#0fc0c)
        ├LayoutBuilder(renderObject: _RenderLayoutBuilder#ac777 relayoutBoundary=up1)
        │└Placeholder
        │ └LimitedBox(maxWidth: 400.0, maxHeight: 400.0, renderObject: RenderLimitedBox#aca20 relayoutBoundary=up2)
        │  └CustomPaint(renderObject: RenderCustomPaint#09849 relayoutBoundary=up3)
        └Builder(dependencies: [Directionality])
         └SizedBox-[GlobalKey#0d1ba widget key](renderObject: RenderConstrainedBox#996dc relayoutBoundary=up1)

The LayoutBuilder stole the keyed SizedBox during the first build.

@LongCatIsLooong, I'm reopening this as the fix was reverted: https://github.com/flutter/flutter/pull/149279

FTR, the reland appears to be #149303.


[block_tree] Introduce LinkableBlock

Motivation

Introduce LinkableBlock to separate mutable and immutable parts of an executed block. So any read API could hold an Arc<ExecutedBlock> while another thread can still mutate the children set of this block since block content/result(immutable) is now separated from children(mutable). This is necessary for incoming refactoring to dedup block trees.

Replace the params of most block_tree read APIs from Arc<Block> to block_id (HashValue). Since we have Block, ExecutedBlock( Block + execution_result) and LinkableBlock( ExecutedBlock + children), we want to identify them in different context using the same identifier. As they are different forms of the same thing, Arc<T> is not a good id. But hash is.

Have you read the Contributing Guidelines on pull requests?
Y
Test Plan
CI

@dmitri-perelman You're right about the purpose. I think this PR is sent due to the constraint of Rust mutability. TBH I don't think it is a good idea to manage child relationship as another hashmap of hashmaps in the BlockTree because it breaks the encapsulation design of blocks. Previously the BlockTree in Consensus consists of too many hashmaps which is quite confusing and hard to maintain the consistency between them. For example, before #803, the remove function is like this: https://github.com/libra/libra/blob/51a7181ac49798cfe9078b2c85f6d447e16fc06c/consensus/src/chained_bft/block_storage/block_tree.rs#L120-L128
It is quite error prone if you forget one line of them.
On the other hand, even I introduced a new struct here it will only be a private struct only known and used by BlockTree itself because it is just a structural wrapper of ExecutedBlock and all public api can only get ExecutedBlock and know nothing about LinkableBlock.

And I want expose ExecutedBlock instead of Block in this PR because later I need read the execution result from it to commit to storage, which is necessary to dedup block trees.

Ok, got it! Do you mind moving the LinkableBlock to the block_tree.rs in this case? It's the only module that is currently using this struct and as you said the plan is to keep it private to the block tree anyway.

@dmitri-perelman Sounds good. I need maybe I need more polishing after this :)

@zekun000 You are right. I can split into 2 pr if necessary. To me, returning ExecutedBlock is a trivial change. As to naming, I racked my brain to come up with this. A better name is welcomed~

:sunny: Test successful - checks-circle_commit_workflow
Approved by: dmitri-perelman
Pushing 5c0bc355acd2ff42463be9bd2b6b5fb8da6d5de8 to master...


Some fixes for example/reinforcement-learning/parallel_actor_critic

Description
Does not run with python 3.x due to usage of xrange
The default environment PongDeterministic-v3 is deprecated.
Some updates to Readme needed
Checklist
Essentials

[ ] Passed code style checking (make lint)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] For user-facing API changes, API doc string has been updated. For new C++ functions in header files, their functionalities and arguments are well-documented.
[ ] To my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] example/reinforcement-learning/parallel_actor_critic/model.py uses xrange() in line 91. This has been changed to range() in python3
[ ] The default env as PongDeterministic-v3. However this is deprecated. Changed to PongDeterministic-v4
[ ] Some updates to README

Comments

I have tested on the Deep Learning AMI with Conda (Ubuntu) (ami-405ade3a)
I have verified that the change for python 3.x does not break the example on python 2.x
I have not verified the accuracy or validity of results.

Hello @loofahcus,
I was trying to run these examples but ran into some minor issues and have created this PR to fix them.
It would be great if you could quickly review my changes.
Thanks,
Meghna Baijal


add memberJoinedChannel event

Related PRs
This PR is not dependent on any other PR
What does this PR do?
Adds member_joined_channel event: https://api.slack.com/events/member_joined_channel
Description of Changes
Small changes to fields to add inviter. user, channel and team are required for new event.

I think we should also patch-version-bump this to publish a new version of the package.


error in parsing Notifications causes HC1 entities unavailable

v0.17.3 started working with Buderus WSW196iT, but HC1 entities were unavailable at all time. In debug log I saw only error related to Notifications, not HC1:
2022-02-01 11:02:29 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /notifications
2022-02-01 11:02:29 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/config/custom_components/bosch/__init__.py", line 394, in thermostat_refresh
    await self.component_update(SENSOR, event_time)
  File "/config/custom_components/bosch/__init__.py", line 373, in component_update
    await entity.bosch_object.update()
  File "/usr/local/lib/python3.9/site-packages/bosch_thermostat_client/helper.py", line 263, in update
    self.process_results(result, key)
  File "/usr/local/lib/python3.9/site-packages/bosch_thermostat_client/sensors/notification.py", line 25, in process_results
    key_suffix = "" if idx == 0 else "_" + idx
TypeError: can only concatenate str (not "int") to str

After disabling sensor.notifications in HA, HC1 entities started working, so it seems to be a cause.
As you may see in my bosh_scan.json #133, my heatpump currently reports two errors but integration shows only first of them. Is it a reason of error in HA?
Would you modify the integration to display all reported errors, please? It would be also good to show date of each error (as attribute?)
"id": "/notifications",
            "type": "errorList",
            "recordable": 0,
            "writeable": 0,
            "values": [
                {
                    "cat": "N",
                    "act": "A",
                    "dcd": "H01",
                    "ccd": 5504,
                    "orig": "8",
                    "t": "2022-01-31T11:06:06",
                    "dlv": "8",
                    "fc": "16"
                },
                {
                    "cat": "N",
                    "act": "A",
                    "dcd": "A01",
                    "ccd": 5503,
                    "orig": "8",
                    "t": "2022-01-31T11:06:06",
                    "dlv": "4",
                    "fc": "16"
                }
            ]

Is there any progress in work on this problem?

Hi, same here - and that's am important thing, cause my GB192i got massive errors (since last maintenance and another maintenance appointment...)
FYI - the readings from FHEM --> "km200"-module (I deleted most/all readings, wich were generated by the module itself)
--> and sorry - I'm not a native speaker ;-)
/dhwCircuits/dhw1/actualTemp
/dhwCircuits/dhw1/charge
/dhwCircuits/dhw1/chargeDuration
/dhwCircuits/dhw1/currentSetpoint
/dhwCircuits/dhw1/holidayMode/activated
/dhwCircuits/dhw1/operationMode
/dhwCircuits/dhw1/singleChargeSetpoint
/dhwCircuits/dhw1/status
/dhwCircuits/dhw1/switchPrograms/A/1-Mo
/dhwCircuits/dhw1/switchPrograms/A/2-Tu
/dhwCircuits/dhw1/switchPrograms/A/3-We
/dhwCircuits/dhw1/switchPrograms/A/4-Th
/dhwCircuits/dhw1/switchPrograms/A/5-Fr
/dhwCircuits/dhw1/switchPrograms/A/6-Sa
/dhwCircuits/dhw1/switchPrograms/A/7-Su
/dhwCircuits/dhw1/temperatureLevels/high
/dhwCircuits/dhw1/temperatureLevels/off
/dhwCircuits/dhw1/waterFlow
/dhwCircuits/dhw1/workingTime
/gateway/DateTime
/gateway/instAccess
/gateway/instWriteAccess
/gateway/logging/userAcceptance
/gateway/update/status
/gateway/uuid
/gateway/versionFirmware
/gateway/versionHardware
/heatSources/CHpumpModulation
/heatSources/ChimneySweeper
/heatSources/actualCHPower
/heatSources/actualDHWPower
/heatSources/actualModulation
/heatSources/actualPower
/heatSources/actualSupplyTemperature
/heatSources/applianceSupplyTemperature
/heatSources/burnerModulationSetpoint
/heatSources/burnerPowerSetpoint
/heatSources/chimneyTemperature
/heatSources/energyMonitoring/consumption
/heatSources/energyMonitoring/correctionFactor
/heatSources/energyMonitoring/maxTankLevel
/heatSources/energyMonitoring/minTankLevel
/heatSources/energyMonitoring/startDateTime
/heatSources/energyMonitoring/tankLevel
/heatSources/fanSpeed_setpoint
/heatSources/flameStatus
/heatSources/gasAirPressure
/heatSources/hs1/actualModulation
/heatSources/hs1/actualPower
/heatSources/hs1/flameStatus
/heatSources/hs1/info/01/Id
/heatSources/hs1/info/01/No
/heatSources/hs1/info/01/Tok
/heatSources/hs1/info/01/Ver
/heatSources/hs1/type
/heatSources/info/01/Id
/heatSources/info/01/No
/heatSources/info/01/Tok
/heatSources/info/01/Ver
/heatSources/nominalCHPower
/heatSources/nominalDHWPower
/heatSources/numberOfStarts
/heatSources/powerSetpoint
/heatSources/returnTemperature
/heatSources/supplyTemperatureSetpoint
/heatSources/systemPressure
/heatSources/workingTime/centralHeating
/heatSources/workingTime/secondBurner
/heatSources/workingTime/totalSystem
/heatingCircuits/hc1/activeSwitchProgram
/heatingCircuits/hc1/actualSupplyTemperature
/heatingCircuits/hc1/currentRoomSetpoint
/heatingCircuits/hc1/currentSuWiMode
/heatingCircuits/hc1/fastHeatupFactor
/heatingCircuits/hc1/holidayMode/activated
/heatingCircuits/hc1/operationMode
/heatingCircuits/hc1/pumpModulation
/heatingCircuits/hc1/roomtemperature
/heatingCircuits/hc1/status
/heatingCircuits/hc1/suWiSwitchMode
/heatingCircuits/hc1/suWiThreshold
/heatingCircuits/hc1/supplyTemperatureSetpoint
/heatingCircuits/hc1/switchProgramMode
/heatingCircuits/hc1/switchPrograms/A/1-Mo
/heatingCircuits/hc1/switchPrograms/A/2-Tu
/heatingCircuits/hc1/switchPrograms/A/3-We
/heatingCircuits/hc1/switchPrograms/A/4-Th
/heatingCircuits/hc1/switchPrograms/A/5-Fr
/heatingCircuits/hc1/switchPrograms/A/6-Sa
/heatingCircuits/hc1/switchPrograms/A/7-Su
/heatingCircuits/hc1/switchPrograms/B/1-Mo
/heatingCircuits/hc1/switchPrograms/B/2-Tu
/heatingCircuits/hc1/switchPrograms/B/3-We
/heatingCircuits/hc1/switchPrograms/B/4-Th
/heatingCircuits/hc1/switchPrograms/B/5-Fr
/heatingCircuits/hc1/switchPrograms/B/6-Sa
/heatingCircuits/hc1/switchPrograms/B/7-Su
/heatingCircuits/hc1/temperatureLevels/comfort2
/heatingCircuits/hc1/temperatureLevels/eco
/heatingCircuits/hc1/temporaryRoomSetpoint

/notifications/Error-01
/notifications/Error-02
/system/appliance/actualSupplyTemperature
/system/brand
/system/bus
/system/healthStatus
/system/holidayModes/hm1/dhwMode
/system/holidayModes/hm1/hcMode
/system/holidayModes/hm1/startStop
/system/holidayModes/hm2/dhwMode
/system/holidayModes/hm2/hcMode
/system/holidayModes/hm2/startStop
/system/holidayModes/hm3/dhwMode
/system/holidayModes/hm3/hcMode
/system/holidayModes/hm3/startStop
/system/holidayModes/hm4/dhwMode
/system/holidayModes/hm4/hcMode
/system/holidayModes/hm4/startStop
/system/holidayModes/hm5/dhwMode
/system/holidayModes/hm5/hcMode
/system/holidayModes/hm5/startStop
/system/info/01/Id
/system/info/01/No
/system/info/01/Tok
/system/info/01/Ver
/system/info/02/Id
/system/info/02/No
/system/info/02/Tok
/system/info/02/Ver
/system/info/03/Id
/system/info/03/No
/system/info/03/Tok
/system/info/03/Ver
/system/minOutdoorTemp
/system/sensors/temperatures/chimney
/system/sensors/temperatures/hotWater_t2
/system/sensors/temperatures/outdoor_t1
/system/sensors/temperatures/return
/system/sensors/temperatures/supply_t1
/system/sensors/temperatures/supply_t1_setpoint
/system/sensors/temperatures/switch
/system/systemType

Best regards
Sascha


Implement compact command

Closes #3466.
Readiness checklist

[ ] I added/updated unit tests (and they pass).
[ ] I added/updated integration/compatibility tests (and they pass).
[ ] I added/updated comments and checked rendering.
[ ] I made spot refactorings.
[ ] I updated user documentation.
[ ] I ran task all, and it passed.
[ ] I ensured that PR title is good enough for the changelog.
[ ] (for maintainers only) I set Reviewers (@FerretDB/core), Milestone (Next), Labels, Project and project's Sprint fields.
[ ] I marked all done items in this checklist.

As a side note – it always better to start a new branch from the current state of the main branch to avoid this:

@adetunjii any news? Anything we could help you with? Also, could we add a basic integration test?

:wave: @adetunjii I added basic integration tests to the implemented feature :hugs:

@chilagrow Thanks. I'll just pull the changes and resolve the conflicts on my end. I'd already worked on the fixes

@adetunjii I think the PR is good enough already. If you want to change something, please do so today; we are going to merge that PR tomorrow.

No. I’m not adding anything. Looks good to me. Thanks
Get Outlook for iOShttps://aka.ms/o0ukef

From: Alexey Palazhchenko @.>
Sent: Tuesday, October 24, 2023 9:30:26 AM
To: FerretDB/FerretDB @.>
Cc: Teej4y @.>; Mention @.>
Subject: Re: [FerretDB/FerretDB] Implement compact command (PR #3559)
@adetunjiihttps://github.com/adetunjii I think the PR is good enough already. If you want to change something, please do so today; we are going to merge that PR tomorrow.
—
Reply to this email directly, view it on GitHubhttps://github.com/FerretDB/FerretDB/pull/3559#issuecomment-1776758086, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKXTHW2DY5SUOBPFOCBY4QLYA54CFAVCNFSM6AAAAAA534IEISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZWG42TQMBYGY.
You are receiving this because you were mentioned.Message ID: @.***>

Thank you!


add note that academic licenses are available

@mstreit what should be the exact text?

Academic licenses for research or educational use can be obtained free of charge. To request an academic license, please send an email to<EMAIL_ADDRESS>@ngehlenborg @alexsb, please check the text and let us know if you want to formulate it differently.

Sounds good.

where should we put this information on the website? do we have a pricing scheme, which we want to publish on the website?
or should it just be a hint somewhere near the contact section?

I'd put it at the end of the product section:

Also extend this to:

For licensing details and pricing please send an e-mail to<EMAIL_ADDRESS>Academic licenses for research or educational use can be obtained free of charge. To request an academic license write to<EMAIL_ADDRESS>

Sounds good. Thanks for the input @alexsb.

What about the following?

Academic licenses for research or educational use can be obtained free of charge. To request an academic license or to get details and pricing please send an e-mail to<EMAIL_ADDRESS>
Then we would have the "send an e-mail to" part only once.

This lives currently in the following branch: https://github.com/datavisyn/datavisyn.github.io/tree/website_fixes
and looks like this:

or do we prefer this version for the moment?

the first version centered doesn't looks weird in my opinion.

@mstreit , what do you say?

I prefer the version with the e-mail address only once.

I agree with alex.


PHP version support?

Q
A

Bug report?
no

Feature request?
no

RFC?
?

How used?

Swiftmailer version
?

PHP version
5.3

What version of the script is compatible with PHP 5.3? I can't seem to find it in the documentation - it says the current release requires 7.0 but nothing about earlier versions.
Thanks!

Never mind - I found it by examining the composer.json files for each version. All the best.

@benkeen Note that you can also see this information on packagist.org which might be more comfortable than switching between branches/tags on GitHub.

@xabbuh - ah, much more convenient. Thanks very much!


How to export category rules

Hi,
I don't see any Export button in the category rules page. However, there is an Import button.
I now use 2 computers with BunqDesktop, and I need to copy the rules from one to another.

Currently you can only export them one at a time but I'll add a button to export them all in the next release.
Clicking the menu icon at the top right of a category rule will show the export option for that specific item.

Also, if you open the settings page you can change and/or copy the settings file location which contain your categories and category rules.
Personally I changed the location to my Google Drive folder so it automatically gets synced to my other devices


auto reload

Is your feature request related to a problem? Please describe.

Describe the solution you'd like:

Describe alternatives you've considered:

Additional context:

plz add auto reload option sir

auto reload

better question! at least extension has keybind or keymap for reloading thing?


Adds CNAME file to preserve custom domain setting

I believe this will fix an issue where the custom domain gets removed on publish to Github Pages.
Per the docs:

For your site to render at the correct domain, make sure your CNAME file still exists in the repository. For example, many static site generators force push to your repository, which can overwrite the CNAME file that was added to your repository when you configured your custom domain. If you build your site locally and push generated files to GitHub, make sure to pull the commit that added the CNAME file to your local repository first, so the file will be included in the build.

When you manually add the custom domain to the GH page settings it creates this file in a new commit. I think if we preserve this file in the webroot that's being published it'll preserve the custom domain settings.

Tugboat has finished building the preview for this pull request!
Link:

https://pr123-8duoip91bvahopqmlgm874wf6wd19su4.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/5fbbd46f479f51dd584cc78e


feat: enable verbose await-tree by default in production

Signed-off-by: Bugen Zhao<EMAIL_ADDRESS>hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Enable verbose await-tree by default in production. Also add some more instruments.
Benchmarking...
Checklist For Contributors

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[x] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[ ] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[x] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

https://buildkite.com/risingwave-test/nexmark-benchmark/builds/1156#01887b9a-f025-4b07-97c5-2183f842e0dd

No performance regression found.


Impose limit on context size

Totally dead; the NoThunks stuff has now moved to its own package. Closing!


strange interaction with autorelease: snooze and the GitHub app

I think we're seeing weirdness with the snooze functionality because the GitHub app is marking the pull request as autorelease: closed when the PR is closed (even with snoozing).
Merged release PR without autorelease: pending label
Closed, snoozed PR
updated code for 741, but update requested for 713

Then it the library tries to reopen the snoozed PR and there is an existing PR open for that branch so validation fails
Validation Failed: {"resource":"PullRequest","code":"custom","field":"state","message":"state cannot be changed. There is already an open pull request from release-please--branches--master to master."}

This issue will fall out of SLO in 6 days.


[Proposal] Add Inactive Track & Inactive Thumb color in Switch Theme

The switch in normal can have two states on and off . Right not the switch theme contains only one state color change.
Please add Inactive track and Thumb color in switch theme data.

You can already do this with the existing SwitchThemeData.
thumbColor & trackColor arenot of type Color, they use MaterialStateProperty<Color?>? instead.
This allow you to specify whatever color for each MaterialState. (disabled, hovered, pressed, active, inactive & other combination of states).
See the example below:
switchTheme: SwitchThemeData(
          thumbColor: MaterialStateProperty.resolveWith((Set<MaterialState> states) {
              if (states.contains(MaterialState.selected)) {
                return Colors.black;
              }
              if (states.contains(MaterialState.disabled)) {
                return Colors.white;
              }
              return Colors.red;
            }),
            trackColor: MaterialStateProperty.resolveWith((Set<MaterialState> states) {
              if (states.contains(MaterialState.selected)) {
                return Colors.black;
              }
              if (states.contains(MaterialState.disabled)) {
                return Colors.white;
              }
              return Colors.red;
            }),
        ),

@kirolous-nashaat your code works, but you need to check for every state, i think it should be more clear like passing parametter or statse.when / statse.mybeWhen


Do not change the default replication size

This PR removes the changing of the replication size, together with the function that did this.

Closing due to having a base branch that is no longer accessible. Will recreate.


Simple utils in Rye console

Just saw Simple utils on Lobsters and wanted to try it.
But I couldn't get it to work for me.

~/Dev/Rye
❯ rye
Welcome to Rye console. Use lc to list current or lcp and lcp\ "pri" to list parent contexts.
x> mkcc 'hn
[Context (): hn: [Context (): ] ]
x> https://hacker-news.firebaseio.com/v0/ :hn
[Uri: https://hacker-news.firebaseio.com/v0/]
x> get hn |length?
[Integer: 556271]
x> hn + "topstories.json" |get
panic: runtime error: index out of range [1] with length 1

goroutine 1 [running]:
github.com/refaktor/rye/env.NewUri(0xc00007de00, {0xc0001740ca?}, {0xc000524090, 0x2d})
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/env/object.go:290 +0x20d
github.com/refaktor/rye/evaldo.init.func47(0xc0002060e0, {0xe44130?, 0xc0004906e0?}, {0xe43a50?, 0xc0003425a0?}, {0x0?, 0x0?}, {0x0?, 0x0?}, {0x0, ...})
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/evaldo/builtins.go:1297 +0x9b4
github.com/refaktor/rye/evaldo.CallBuiltin({0xd68ca8, 0x2, {0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0}, ...}, ...)
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/evaldo/evaldo.go:1051 +0xfff
github.com/refaktor/rye/evaldo.EvalObject(0xc0002060e0, {0xe43d20, 0xc0002bd900}, {0xe44130, 0xc0004906e0}, 0x0, 0x0, 0x0, {0x0, 0x0})
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/evaldo/evaldo.go:563 +0x190
github.com/refaktor/rye/evaldo.EvalWord(0xc0002060e0, {0xe436e0, 0x12f3100}, {0xe44130, 0xc0004906e0}, 0x0, 0x0)
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/evaldo/evaldo.go:508 +0x3a6
github.com/refaktor/rye/evaldo.MaybeEvalOpwordOnRight({0xe43fa0?, 0xc0003021d0?}, 0xc0002060e0, 0x0)
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/evaldo/evaldo.go:271 +0x6c5
github.com/refaktor/rye/evaldo.EvalExpressionInj(0xc0002060e0?, {0xe43820?, 0xc00011c000?}, 0x0)
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/evaldo/evaldo.go:211 +0xb2
github.com/refaktor/rye/evaldo.EvalBlockInj(0xc000500000?, {0xe43820, 0xc00011c000}, 0x0?)
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/evaldo/evaldo.go:96 +0x4f
github.com/refaktor/rye/evaldo.(*Repl).evalLine(0xc0000ab720, 0xc0002060e0, {0xc000500000, 0x1b})
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/evaldo/repl.go:212 +0x2b1
github.com/refaktor/rye/evaldo.(*Repl).recieveLine(0xc0000ab720, {0xc000500000?, 0xc000500000?})
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/evaldo/repl.go:175 +0x2d
github.com/refaktor/rye/term.(*MLState).MicroPrompt(0xc0002f6580, {0xd0d455, 0x3}, {0x0, 0x0}, 0x1b, {0xe40530, 0xc0000ab770})
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/term/microliner.go:875 +0x55a
github.com/refaktor/rye/evaldo.DoRyeRepl(0xc0002060e0, {0xd0d275, 0x3}, 0x1)
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/evaldo/repl.go:453 +0x553
github.com/refaktor/rye/runner.main_rye_repl({0x546a96?, 0xe360c0?}, {0xc0000e7ee8?, 0x0?}, 0x1, 0x0, {0xd0d275, 0x3}, {0xe360c0, 0x1}, ...)
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/runner/runner.go:586 +0x358
github.com/refaktor/rye/runner.DoMain(0xd67758)
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/runner/runner.go:115 +0x1b9
main.main()
	/home/grimnight/Dev/GHQ/github.com/refaktor/rye/main.go:38 +0x1f

I compiled Rye from the latest commit.

Hi, thank you for testing this. I was making the asciinema demo yesterday deep into the night, also fixed a bug you came upon, and few other things,  but haven't yet committed the changes. I will be committing them now.

Yes, there are few bugs with serialisation of code. One of them is there because a language changed a little in the meantime [] vs {}, another is just bug.
This is the gist I was trying to make to explain you about this.
https://gist.github.com/refaktor/b07f35e37d0c3ac56ae32ced1027dbc3
This is a little more advanced version of these two utils (but probably too complicated for making it in asciinema)
https://gist.github.com/refaktor/cde07e01aed6809eb37e582b12c048ea

Thanks for kind words!
I am preparing a function reference, that will be online and accessible from console, which should be helpful. Even I have to look in Go source now to remember the order of arguments sometimes.  There is an old one here https://ryelang.org/basics.html, but new one should be better and more complete. It does take some time, but we have the system in place now, described here: https://ryelang.org/cookbook/improving-rye/one-source/
I fixed the save\current related bugs https://github.com/refaktor/rye/pull/384 . There were 3. Thank you for reporting and I hope to hear from you again. I am closing this issue.


vagrantfile for windows developers

Hi and thanks for the contribution :)
Can you please tell me more about the issue you're trying to solve here? I may be wrong, but I think a Vagrant file is slightly out of scope in our case: dynamic_preferences is a python/django library, and the Vagrantfile you want to merge is actually more focusing on installating Python, Virtualenv and Django themselves.
As most Django projects involve multiple libraries, it does not really make sense to me to have a Vagrantfile (or a Dockerfile, I'm not against Vagrant ;)  for each library. It's probably more efficient to have a generic Vagrantfile for Django, and to mount the libraries you need in your VM (or to install them via pip).
As far as I know, Django also works on Windows -I'm not a windows user though, so maybe there are some issues-. Dynamic_preferences should also work on Windows platforms, as I don't think we use any OS specific code. Is there any reason windows developper cannot simply use Python / Virtualenv / and pip to install all the dependencies?
Having a quick look at "big" django libraries such as django-rest-framework, or django-cms, I don't see any Vagrantfile in their repositories either.
I'd be more than happy to know more about your use case and to see what we can do to make working on dynamic-preferences easier :)

you are probably right, just wanted to make it easier for anyone to pick up the project, feel free to cancel this
maybe these files can be included in the readme if someone would find it useful

Did you have any platform-specific issues while working on your other PRs? I'm trying to figure out what are the barriers for potential contributors (apart from the Python/Django installation stuff, which are not specific to this project).
I think I'm gonna close this PR without merging it, since a full Vagrantfile seems overkill for a single library (but definitely relevant for a Django project). The contributing section of the documentation is seriously outdated though, and I'll work on that. Please tell me if you think of any specific issues you had while working on your PRs :)


E_WARNING - Undefined variable $rel_links

Hey, thanks for working on this one !
When I follow the admin link /admin/broken-links
I have this error :
E_WARNING - Undefined variable $rel_links
I follow the instruction
How can I set the $rel_links variable ?
Thanks

This plugin doesn't work fully yet.  I wouldn't consider using this plugin at this time.

ok
thanks
have a good trip

Reopening issue to track fix.


Migrate to Swift 3.0.1

Migrated the codebase to Swift 3.0.0/3.0.1 specifications and changes.
Fixed some unit test and rebuilt SourceKitten.

Travis build actually failed, even if it says that succeded. 😕

Module file was created by a newer version of the compiler:      /Users/travis/build/yopeso/Taylor/Carthage/Build/Mac/SourceKittenFramework.framework/Modules/SourceKittenFramework.swiftmodule/x86_64.swiftmodule

Remove Taylor from the name of the first commit. Also I guess you'll have to make two releases for the users of the framework to be able to use it on any Swift version. Or have separate branches and setup Carthage / SPM for that.

@S2dentik I think it makes more sense to make two different releases for different versions of Swift. Keeping a branch would make more sense when a beta version of Swift is used. It allows you to adapt the codebase to language changes.

@thelvis4 Yeah, that's for sure, I was thinking how we'll provide the versions for the consumers, and yeah, probably two tags will be enough.

Update! Check please for correctness before squash and finish

Update. Check again please :)

As mentioned earlier, Travis job is failing, even though it looks like it succeeded.
I've analyzed the logs and for some reasons, Travis uses osx10.11-xcode7.3 image. Due to the fact that dependencies (Carthage frameworks) are prebuilt using Xcode 8.1, Swift isn't happy.
I'll try different .travis.yml configurations to in order to fix this.

Current coverage is 92.81% (diff: 88.83%)

Merging #38 into master will increase coverage by 0.35%

@@             master        #38   diff @@
==========================================
  Files            60        108     +48
  Lines          1618       4245   +2627
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1496       3940   +2444
- Misses          122        305    +183
  Partials          0          0

Powered by Codecov. Last update 8e72193...fc16270

Ok, now Travis and Codecov are happy. 😊
@S2dentik if requested changes are made, I think we can proceed to merging this.

Update

@SunnyPRO looks great 👍

@SunnyPRO Great job! 👍
Thanks!


Tag expansion prompt showing unexpectedly

Sometimes when closing an HTML tag, I am prompted for tax expansion unexpectedly. This does not happen on Sublime's HTML syntax - only when using the HTML (Blade) syntax. It seems related to putting colons in attributes and then closing the tag.
Any help solving this extremely appreciated.
Below is a minimal HTML snippet to reproduce the problem.

@deathaxe do you have any thoughts on why this is happening and how to prevent it?

The only special thing of this package is a syntax specific auto_completion_selector, which intents to enable autocompletions within template tags. It would require a nonwhitespace character to be typed, to open the panel.
see: https://github.com/Medalink/laravel-blade/blob/fe4961837f6c08424eeb7850e9ca0f57a2aacb50/Syntaxes/HTML (Blade).sublime-settings#L2

What ST version is it?
What's the output of

view.settings().get("auto_complete_selector")
view.settings().get("auto_complete_triggers")

Is any language server involved?
Any other completion plugins?

Is completion panel directly opened by typing >? Maybe > was added to auto_complete_triggers by a plugin (or user customization)? I am aware of LSP manipulating view-specific auto_complete_triggers setting based on what it gets from a language servers.
I get this state only by hitting ctrl+space after the tag.

Build 4143

No LSP.

Other maybe relevant plugins I have installed: ECMAScript Syntax, PHP Companion, Vue Syntax Highlight

Did you set syntax to "HTML (Blade)" before calling view.settings().get(...)?
I'd expect
>>> view.settings().get("auto_complete_selector")
'( meta.tag | meta.embedded.directive ) - comment'

>>> view.settings().get("auto_complete_triggers")
[{'characters': '<', 'selector': 'text.html, text.xml'}, {'rhs_empty': True, 'selector': 'punctuation.accessor'}]

Listed syntaxes seem unrelated. Their code doesn't contain hints and I can't reproduce the issue, if they are installed.
You could try to log commands, to see whether anything is triggering auto_complete command when closing tags.
>>> sublime.log_commands()

Trying that I've not seen any command when typing >.

Indeed.
Blade is just inherits from ST's PHP and HTML re-using most syntax stuff and the html completion plugin. It extends core syntaxes in the same way as Vue and other packages.
Did you try to setup a completely vanilla ST with only Blade installed? Does it happen then, too?

I have been able to narrow it down to something within Livewire 3's legacy_tests/Browser directory. When that directory is removed it does not happen. It also does not happen if I tell Sublime to not index "vendor" files.
Does the Blade plugin attempt to do anything intelligent based on the Blade declarations / components in other files in the application?

This package provide plain syntax definitions and a handful of completions. There's no plugin or any other kind of black magic provided.


update github-pages gem version

When merged this pull request:

will update the github pages gem version to the latest release as of today which is v112
https://github.com/github/pages-gem/releases

Thank you for your contribution @bux578 👍 🎉


Running test environment shall persist available logs

When running the test environment only the docker logs are persisted as artifact. We want to have full insights in what happened when something went wrong. This is particularly tedious if there are so many services involved and impossible if there are missing logs.
Missing logs and their current location:

EDGARs setup logs: /opt/opendut-edgar/setup.log
EDGARs service logs: /var/log/journal/opendut-edgar.service.log
Netbird client logs: /var/log/netbird/client.log
Netbird systemd service logs: /var/log/journal/netbird.log

Added script to persist all logs from the edgar containers to a directory docker-logs:
.ci/docker/edgar/persist-edgar-logs.sh
This script is used in the run test environment workflow to publish an artifact containing all logs.


(hopefully) make the event scheduler less chaotic

I'm not 100% sure how exactly this works, but I believe this should result in less events spawning, more similar to how it was before the refactor.

I did not test a full 4 hour round, but I tried it for a bit and I think this looks fine, we are going to need to keep tweaking these numbers anyways.


openssl passwd -salt allows non-POSIX characters in salt

The openssl passwd command allows a -salt string argument:
openssl passwd -6 -salt string

However, the salt string is not checked for non-POSIX characters before calculating the hash.
An example would be:
openssl passwd -6 -salt H27GSxmlD/v++++A

where the + characters are non-POSIX compliant.
This is causing errors for us on newer Linux systems with Glibc versions>2.17 which rejects non-POSIX salts when verifying passwords.
The POSIX.1-2017 standard declares in
https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/functions/crypt.html
that only the following characters may be used in the salt:
The salt argument shall be a string of at least two bytes in length not including the null character chosen from the set:
a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9 . /

Please make the openssl passwd -salt command check the characters in the salt string and print an error message if non-POSIX characters are found.

Perhaps, don't pass non-POSIX salt characters to the passwd command?
The command itself, won't generate non-POSIX characters.

Er, are POSIX salt characters even relevant in this case?  To get the crypt() functionality, -crypt should be used rather than -6.  In the manual, -6 refers to https://www.akkadia.org/drepper/SHA-crypt.txt, is there something there that sets a limit on salt characters?
Furthermore, -crypt is only relevant for OpenSSL 1.1.x.  We've removed it for 3.0

The relevant text from that link is:

For the SHA-based methods the SALT string can be a simple string of which up to 16 characters are used.

No reference to POSIX, just characters.


issues.data.map is not a function

Before submitting your bug report

[ ] I believe this is a bug. I'll try to join the Continue Discord for questions
[ ] I'm not able to find an open issue that reports the same bug
[ ] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: w10
- Continue version: v0.8.57
- IDE version: 1.95.3
- Model:
- config.json:

{
  "models": [
    {
      "title": "Llama 3.1 8B",
      "provider": "ollama",
      "model": "llama3.1:8b"
    },
    {
      "model": "AUTODETECT",
      "title": "Ollama",
      "completionOptions": {
        "temperature": 1
      },
      "apiBase": "http://localhost:11434/v1/",
      "provider": "ollama"
    },
    {
      "model": "AUTODETECT",
      "title": "LM Studio",
      "apiBase": "http://localhost:1234/v1/",
      "provider": "lmstudio"
    }
  ],
  "customCommands": [
    {
      "name": "test",
      "prompt": "{{{ input }}}\n\nWrite a comprehensive set of unit tests for the selected code. It should setup, run tests that check for correctness including important edge cases, and teardown. Ensure that the tests are complete and sophisticated. Give the tests just as chat output, don't edit any file.",
      "description": "Write unit tests for highlighted code"
    }
  ],
  "tabAutocompleteModel": {
    "title": "Qwen2.5-Coder 1.5B",
    "provider": "ollama",
    "model": "qwen2.5-coder:1.5b"
  },
  "tabAutocompleteOptions": {
    "debounceDelay": 0
  },
  "embeddingsProvider": {
    "provider": "ollama",
    "model": "nomic-embed-text"
  },
  "contextProviders": [
    {
      "name": "url"
    },
    {
      "name": "codebase",
      "params": {
        "nRetrieve": 45,
        "nFinal": 15,
        "useReranking": true
      }
    },
    {
      "name": "docs"
    },
    {
      "name": "folder"
    },
    {
      "name": "diff"
    },
    {
      "name": "code"
    },
    {
      "name": "terminal"
    },
    {
      "name": "open",
      "params": {
        "onlyPinned": false
      }
    },
    {
      "name": "issue",
      "params": {
        "repos": [
          {
            "owner": "continuedev",
            "repo": "continue"
          }
        ],
        "githubToken": "xxx"
      }
    }
  ],
  "allowAnonymousTelemetry": false,
  "docs": [
    {
      "title": "React",
      "startUrl": "https://react.dev/reference/"
    }
  ]
}

Description
After updating continue to 0.9.4 when i open VSCode the following error is displayed: issues.data.map is not a function
To reproduce
No response
Log output
[Extension Host] Error handling webview message: {
  "msg": {
    "messageId": "50144d10-a9df-4df5-86d2-469097f0a639",
    "messageType": "context/loadSubmenuItems",
    "data": {
      "title": "issue"
    }
  }
}

TypeError: issues.data.map is not a function
uGi @ console.ts:137
notificationsAlerts.ts:42 issues.data.map is not a function
c @ notificationsAlerts.ts:42
index.js:747 Error loading items for issue: Object

Problematic code line appears to be here: ...issues.data.map((issue) => ({
If you're not actively using the Issues context provider you can just remove that from your config.json. If you are using it, can you verify that the GitHub token you're using is still valid?


Super-RMB: Overview will be opened, if you activate a menu item with LMB while holding Super

Describe the Bug
If you activate a pie menu with Super+RMB but use LMB to activate an item while holding Super, the overview will be opened after letting go of Super.
Steps to reproduce the behavior:

Open a pie menu with Super+RMB
Hold Super
Activate a menu item with LMB
Let go of Super

=> Overview will open.
Expected Behavior
Overview shouldn't open.
System

Fedora 35
Fly-Pie version: 11 (EGO)
GNOME Shell version: 41.1

Thanks for the report! I pushed a fix which should ensure that the menu does not close until Super is released. If you want to, you can test it in develop. I will publish a bug-fix release quite soon!

Thanks for the report! I pushed a fix which should finally ensure that the menu does not close until Super is released. If you want to, you can test it in develop. I will publish a bug-fix release quite soon!

Thanks, I'll give it a shot.


PYTHONPATH

Please describe.
A clear and concise description of the problem and the question at hand.
I have a vscode installation where the PYTHONPATH for local modules is set using the .env file.
cat .env
PYTHONPATH=.:./Utilities:./Utilities/Selenium:./Libs/:./Libs/Galileo:./Libs/SeleniumBase%

Is is possible to tell robotcode to use this .env file to get the PYTHONPATH for robotcode?
Thanks,
Damian.
Desktop (please complete the following information):

VS Code Version [e.g. 1.60] 1.74.3
RobotCode Version [e.g. 0.3.2]<EMAIL_ADDRESS>OS: [e.g. Windows, Linux] OSX
Python Version [e.g. 3.9.7] Python 3.10.2
RobotFramework Version [e.g. 4.0.0] Robot Framework 6.0.2
Additional tools like robocop, robotidy

At the moment, unfortunately, it is not possible to use an .env file to run robot tests in VSCode with RobotCode.
But I think there is also no common way to run robot tests on the console using this .env file, maybe you have one?
For now, you can set the PythonPath in the VSCode Settings for RobotCode. Have a look in the settings for the robotcode.robot.pythonPath setting. It corresponds to the command line switch --pythonpath of Robot.
Maybe it would be an idea to add something like this to RobotCode? Would you be interested in creating an enhancement request for it?

Is your question answered? Can I close this issue?

Thanks @d-biehl yes.


Add more example about § because most users have confusion about it

https://github.com/tekezo/Karabiner-Elements/issues/123

Thanks!


[Fix] Modify model saving behavior and unify all check do evaluation behavior

Issue #865 , if available:
Description of changes:
This PR changes the behavior of model saving and check do evaluation.

Add a can_do_model_evaluation() method in the base trainer to unify check do evaluation behavior for all subclasses.
Modify model saving behavior by forcing to do evaluation if can.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Is it possible to add a test that proves the intended behavior? Basically, we want to always honer the requested save_model_frequency regardless of eval frequency

Is it possible to add a test that proves the intended behavior? Basically, we want to always honer the requested save_model_frequency regardless of eval frequency

Yes, working on it.

Is it possible to add a test that proves the intended behavior? Basically, we want to always honer the requested save_model_frequency regardless of eval frequency

Have add a set of end2end tests to check this behavior.


[Core] Update API ref link in README

Core API reference docs link in README is currently pointing to source code rather than API.

API change check
API changes are not detected in this pull request.

/check-enforcer override


secure the app via various packages

hi @semihberkayozturk please use rebase instead merge to align your git history. Can you please fix it?