Cannot install Atom on win7

I tried installing Atom using the handy installer (<IP_ADDRESS>) but it stops dead in its tracks on my Windows 7 box.
It exits with the "Installation has failed" message.
I've looked around on these "forums" a bit, and I can tell you that:

My AntiVirus is Microsoft Security Essentials, with disabled real-time protection
I have full administrator rights on this machine
I did not previously try to install Atom

I will install it manually, but I think the devs need to fix this urgently as most people will not have the patience necessary to do that :)
Here is my Setup Log. I "censored" my User directory for security reasons:
2016-01-05 15:21:04> Program: Starting Squirrel Updater: --install .
2016-01-05 15:21:04> Program: Starting install, writing to C:\Users\fXXXXXX.XXXXXXXX.XXXXT\AppData\Local\SquirrelTemp
2016-01-05 15:21:04> Program: About to install to: C:\Users\fXXXXXX.XXXXXXXX.XXXXT\AppData\Local\atom
2016-01-05 15:21:04> CheckForUpdateImpl: Failed to load local releases, starting from scratch: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\fXXXXXX.XXXXXXXX.XXXXT\AppData\Local\atom\packages\RELEASES'.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at Squirrel.Utility.LoadLocalReleases(String localReleaseFile)
   at Squirrel.UpdateManager.CheckForUpdateImpl.<CheckForUpdate>d__3d.MoveNext()
2016-01-05 15:21:04> CheckForUpdateImpl: Reading RELEASES file from C:\Users\fXXXXXX.XXXXXXXX.XXXXT\AppData\Local\SquirrelTemp
2016-01-05 15:21:04> CheckForUpdateImpl: First run or local directory is corrupt, starting from scratch
2016-01-05 15:21:04> ApplyReleasesImpl: Writing files to app directory: C:\Users\fXXXXXX.XXXXXXXX.XXXXT\AppData\Local\atom\app-1.3.2
2016-01-05 15:21:09> IEnableLogger: Failed to install package to app dir: System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
   at System.IO.PathHelper.GetFullPathName()
   at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
   at System.IO.Path.GetFullPathInternal(String path)
   at System.IO.Path.GetFullPath(String path)
   at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractEntry(ZipEntry entry)
   at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractZip(Stream inputStream, String targetDirectory, Overwrite overwrite, ConfirmOverwriteDelegate confirmDelegate, String fileFilter, String directoryFilter, Boolean restoreDateTime, Boolean isStreamOwner)
   at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClassaf.<<installPackageToAppDir>b__a8>d__b8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Squirrel.Utility.<LogIfThrows>d__54`1.MoveNext()
2016-01-05 15:21:09> Unhandled exception: System.AggregateException: One or more errors occurred. ---> System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
   at System.IO.PathHelper.GetFullPathName()
   at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
   at System.IO.Path.GetFullPathInternal(String path)
   at System.IO.Path.GetFullPath(String path)
   at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractEntry(ZipEntry entry)
   at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractZip(Stream inputStream, String targetDirectory, Overwrite overwrite, ConfirmOverwriteDelegate confirmDelegate, String fileFilter, String directoryFilter, Boolean restoreDateTime, Boolean isStreamOwner)
   at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClassaf.<<installPackageToAppDir>b__a8>d__b8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Squirrel.Utility.<LogIfThrows>d__54`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Squirrel.UpdateManager.ApplyReleasesImpl.<ApplyReleases>d__78.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Squirrel.UpdateManager.<FullInstall>d__f.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Squirrel.Update.Program.<Install>d__37.MoveNext()
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait()
   at Squirrel.Update.Program.executeCommandLine(String[] args)
   at Squirrel.Update.Program.main(String[] args)
---> (Inner Exception #0) System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
   at System.IO.PathHelper.GetFullPathName()
   at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
   at System.IO.Path.GetFullPathInternal(String path)
   at System.IO.Path.GetFullPath(String path)
   at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractEntry(ZipEntry entry)
   at ICSharpCode.SharpZipLib.Zip.FastZip.ExtractZip(Stream inputStream, String targetDirectory, Overwrite overwrite, ConfirmOverwriteDelegate confirmDelegate, String fileFilter, String directoryFilter, Boolean restoreDateTime, Boolean isStreamOwner)
   at Squirrel.UpdateManager.ApplyReleasesImpl.<>c__DisplayClassaf.<<installPackageToAppDir>b__a8>d__b8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Squirrel.Utility.<LogIfThrows>d__54`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Squirrel.UpdateManager.ApplyReleasesImpl.<ApplyReleases>d__78.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Squirrel.UpdateManager.<FullInstall>d__f.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Squirrel.Update.Program.<Install>d__37.MoveNext()<---

System.IO.PathTooLongException

How long is your username? Does it include non-English characters?

How long is your username? Does it include non-English characters?

Exactly the amount of characters I replaced with X's
That means 22 characters, and no special ones except the dots.

Not sure if the dots are a problem. I seem to remember that others have similar usernames and installed just fine.
Is your user directly redirected to a different (network?) location by any chance?

Is your user directory redirected to a different (network?) location by any chance?

Nope. It's just a regular old directory.

Same issue here, Win7 Portuguese-BR. There's some fix for it?

This is a duplicate of #5109 - please subscribe there for updates.  There's also some workarounds there that you can try.


Need to round off netcode values so they don't have lots of decimal places

I'd add this to v0.11 since this could potentiality cause such things as delay and lag easily. The less data, the absolute better.

The new enet code should fix this but I'll review it after v0.11.  It won't impact single player mode.

New enet code resolves this.


fix: fixes transactionID isolation for GraphQL

Description
Fixes #4091 by using a JavaScript Proxy to isolate the transactionID between individual GraphQL operations instead of copying the request.
I have also fixed the missing cloning of the request for the collections/findByID resolver.

[X] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[X] Bug fix (non-breaking change which fixes an issue)

Checklist:

[X] I have added tests that prove my fix is effective or that my feature works
[X] Existing test suite passes locally with my changes

@DanRibbens Right, of course :man_facepalming: I've now gone through registerSchema and checked every resolver.
Should we expose isolateTransactionID for people to use in custom GraphQL resolvers or maybe we should handle it transparently by wrapping any custom resolver with it? The latter sounds more convenient for users and makes it impossible to forget.

Should we expose isolateTransactionID for people to use in custom GraphQL resolvers or maybe we should handle it transparently by wrapping any custom resolver with it? The latter sounds more convenient for users and makes it impossible to forget.

We never want people to have to learn these kinds of ugly details if it can be avoided. I haven't reviewed this yet but it sounds like we need to handle it.
Thanks!

I have now added a wrapper to any (top level) resolver in the custom mutations and queries. I've added a test that makes sure they are using separate transaction IDs.


Overlay plot

Hi there,
I was wondering if there is a way to do an overlay plot with Bosun? Like a week on week plot of say request per seconds
Thanks in advance and keep up the good stuff with bosun :)

Hello.
I've did a little bit of research on that topic. There's actually a lot of feature requests for it not only for Bosun, but for Grafana etc. Best effort solution for now is to use Grafana dashboards with "Time Shift" feature https://i.imgur.com/dMq8clP.png so you'll have 2 dashboards (one for current period, one with shifted one). Per-metric time shift on one graph is not currently implemented. That shouldn't be very hard to code though. Grafana is probably better suited for such functionality.

Hi Dmitry,
I finally did try grafana with openTSDB - The problem though is as you said
grafana does not allow a different timeshift for every metrics, so as you
said it has to be done on 2 dashboard - Much less convenient - I would
think a lot of people would want that, I'll ask the grafana people.
On the flip side setting up an alert based on Week on Week computation with
Bosun was very easy :)
pierre
On Tue, May 26, 2015 at 2:48 PM, Dmitry V. Medvedev <
<EMAIL_ADDRESS>wrote:

Hello.
I've did a little bit of research on that topic. There's actually a lot of
feature requests for it not only for Bosun, but for Grafana etc. Best
effort solution for now is to use Grafana dashboards with "Time Shift"
feature https://i.imgur.com/dMq8clP.png so you'll have 2 dashboards (one
for current period, one with shifted one). Per-metric time shift on one
graph is not currently implemented. That shouldn't be very hard to code
though. Grafana is probably better suited for such functionality.
—
Reply to this email directly or view it on GitHub
https://github.com/bosun-monitor/bosun/issues/985#issuecomment-105513338
.

Yes I built a Grafana dashboards like this and that isn't as useful as a
week over week style graph....
Working in bar / histogram charts currently, maybe this can be next for
visualization in bosun
On Jun 16, 2015 2:19 PM, "pmonestie"<EMAIL_ADDRESS>wrote:

Hi Dmitry,
I finally did try grafana with openTSDB - The problem though is as you said
grafana does not allow a different timeshift for every metrics, so as you
said it has to be done on 2 dashboard - Much less convenient - I would
think a lot of people would want that, I'll ask the grafana people.
On the flip side setting up an alert based on Week on Week computation with
Bosun was very easy :)
pierre
On Tue, May 26, 2015 at 2:48 PM, Dmitry V. Medvedev <
<EMAIL_ADDRESS>wrote:

Hello.
I've did a little bit of research on that topic. There's actually a lot
of
feature requests for it not only for Bosun, but for Grafana etc. Best
effort solution for now is to use Grafana dashboards with "Time Shift"
feature https://i.imgur.com/dMq8clP.png so you'll have 2 dashboards (one
for current period, one with shifted one). Per-metric time shift on one
graph is not currently implemented. That shouldn't be very hard to code
though. Grafana is probably better suited for such functionality.
—
Reply to this email directly or view it on GitHub
<
https://github.com/bosun-monitor/bosun/issues/985#issuecomment-105513338>
.

—
Reply to this email directly or view it on GitHub
https://github.com/bosun-monitor/bosun/issues/985#issuecomment-112572505
.

I would vote for it :)
At my previous company (LinkedIn) all graph we used had WoW overlay: It's
such an easy way to detect something wrong in a system to compare with last
week or last 24h data. Bosun does the job as the alerting system supports
comparing WoW, though having it in graph would be awesome.
Anyway maybe I'll try to 'hack' grafana or Bosun to get this...
On Tue, Jun 16, 2015 at 11:25 PM, Kyle Brandt<EMAIL_ADDRESS>wrote:

Yes I built a Grafana dashboards like this and that isn't as useful as a
week over week style graph....
Working in bar / histogram charts currently, maybe this can be next for
visualization in bosun
On Jun 16, 2015 2:19 PM, "pmonestie"<EMAIL_ADDRESS>wrote:

Hi Dmitry,
I finally did try grafana with openTSDB - The problem though is as you
said
grafana does not allow a different timeshift for every metrics, so as you
said it has to be done on 2 dashboard - Much less convenient - I would
think a lot of people would want that, I'll ask the grafana people.
On the flip side setting up an alert based on Week on Week computation
with
Bosun was very easy :)
pierre
On Tue, May 26, 2015 at 2:48 PM, Dmitry V. Medvedev <
<EMAIL_ADDRESS>wrote:

Hello.
I've did a little bit of research on that topic. There's actually a lot
of
feature requests for it not only for Bosun, but for Grafana etc. Best
effort solution for now is to use Grafana dashboards with "Time Shift"
feature https://i.imgur.com/dMq8clP.png so you'll have 2 dashboards
(one
for current period, one with shifted one). Per-metric time shift on one
graph is not currently implemented. That shouldn't be very hard to code
though. Grafana is probably better suited for such functionality.
—
Reply to this email directly or view it on GitHub
<
https://github.com/bosun-monitor/bosun/issues/985#issuecomment-105513338

.

—
Reply to this email directly or view it on GitHub
<
https://github.com/bosun-monitor/bosun/issues/985#issuecomment-112572505>

.

—
Reply to this email directly or view it on GitHub
https://github.com/bosun-monitor/bosun/issues/985#issuecomment-112573959
.


Creating a new app with npx react-native init exit with error

Description
I create a new protect with npx react-native init  then I run npx react-native run-ios and the following error occurs. Other projects run good
error: node_modules/react-native/Libraries/Image/ImageAnalyticsTagContext.js: Property body[6] of BlockStatement expected node to be of a type ["Statement"] but instead got "AssignmentExpression"
React Native version:
System:
OS: macOS 11.5.1
CPU: (8) arm64 Apple M1
Memory: 276.03 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.5.0 - /opt/homebrew/bin/node
Yarn: 1.22.10 - /opt/homebrew/bin/yarn
npm: 7.19.1 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.10.1 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4
Android SDK:
API Levels: 29, 30
Build Tools: 28.0.3, 29.0.2, 30.0.3, 31.0.0
System Images: android-30 | Google APIs Intel x86 Atom, android-31 | Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_282 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.2 => 0.64.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

npx react-native init
2.npx react-native run-ios

Expected Results
Describe what you expected to happen.
Run the app in iOS Simulator

#31960 see please.

node_modules/react-native/Libraries/Components/ScrollView/ScrollView.js: Property body[42] of BlockStatement expected node to be of a type ["Statement"] but instead got "AssignmentExpression"
Same issue here, I follow exactly the instructions of RN web demonstration, no way to solve it. I also checked some

#31960 see please.
the problem is due to a babel update that affected the RN project.

Hi pulnec, can you solve it? I follow exactly the RN webs demonstration, still same error show up, try all the ways I can, no useful so far.

Show your package.json

Came here to say I'm having the exact same problem

Show your package.json

{
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo start --web",
"eject": "expo eject"
},
"dependencies": {
"expo": "~42.0.1",
"expo-status-bar": "~1.0.4",
"react": "16.13.1",
"react-dom": "16.13.1",
"react-native": "https://github.com/expo/react-native/archive/sdk-42.0.0.tar.gz",
"react-native-web": "~0.13.12"
},
"devDependencies": {
"@babel/core": "^7.9.0"
},
"private": true
}
This is the exactly package.json file after app created, nothing change, even if I change the @babel/core to other version, no useful

I'm facing same problem here with react native cli and expo

Same problem here!

hi guys, same problem I had this problem while building App. I can't figure out how to fix it, can someone here help me?
error: node_modules/react-native/Libraries/Image/ImageAnalyticsTagContext.js: Property body[6] of BlockStatement expected node to be of a type ["Statement"] but instead got "AssignmentExpression"

this is a known issue caused by a bug in a newly released version of babel. it will impact all new react-native and expo apps. you can resolve it with yarn resolutions in a new project:
--- a/package.json
+++ b/package.json
@@ -25,5 +25,8 @@
   },
   "jest": {
     "preset": "react-native"
+  },
+  "resolutions": {
+    "@babel/plugin-transform-react-display-name": "7.14.5"
   }
 }

see some discussion here:

https://twitter.com/notbrent/status/1423152953876176897
https://twitter.com/notbrent/status/1423153268423790594

@brentvatne where in the project do can i add the code you shared??

package.json

@brentvatne thank you

@brentvatne would you know if by any chance this causes crashes in apps that is release in production?? or would this only affect people that are trying to build in development?

this is a known issue caused by a bug in a newly released version of babel. it will impact all new react-native and expo apps. you can resolve it with yarn resolutions in a new project:
--- a/package.json
+++ b/package.json
@@ -25,5 +25,8 @@
   },
   "jest": {
     "preset": "react-native"
+  },
+  "resolutions": {
+    "@babel/plugin-transform-react-display-name": "7.14.5"
   }
 }

see some discussion here:

https://twitter.com/notbrent/status/1423152953876176897
https://twitter.com/notbrent/status/1423153268423790594

Thanks man, works for me!

@brentvatne would you know if by any chance this causes crashes in apps that is release in production?? or would this only affect people that are trying to build in development?

it won't impact existing releases. if you're able to do a new release (the app compiles) then this particular issue will not cause any problems

It can be done by installing the project with low version of react native.
just like npx react-native init project_name --version 0.63.X

:: Solution ::
Just copy the @Babel from an Old Project and Replace it.


Review configuration options for Mbed TLS 3.0

In Mbed TLS 3.0, we want to shed weight. One aspect of shedding weight is getting rid of as many compilation options as possible. Compilation options increase the code complexity and the testing burden. The goal of this issue is to review the existing compilation option.
For each existing option in config.h:

If the option should obviously stay (e.g. MBEDTLS_xxx_C, platform capabilities), record this and move on.
Otherwise, start a discussion on the mailing list to gauge who is using it, who wants it, and weigh that against the burden of supporting the option. (A few options have been discussed already, see https://developer.trustedfirmware.org/w/mbed-tls/tech-plans-3.0/.) If the option is removed, discuss how this would work: always on or always off?
Once the discussion settles, record the outcome: if it should stay, justify why (this includes explaining how it is tested). If it should go away, is it always on or always off? What are the migrations for applications that were making use of the option?

My personal opinion on configuration options is that platform capabilities and is-it-supported options (mostly MBEDTLS_xxx_C, also a few like MBEDTLS_PKCS1_Vxx and the new PSA_WANT_xxx`) should stay unless there's a good reason. Other configuration options
This task can be split between many people since most options are independent.
As a preliminary, we need to have a central place to track progress. This is more suited to a wiki-like setup. We've started to put 3.0 plans on the TrustedFirmware wiki, but we want to move this kind of information to the Mbed TLS documentation repository.

See also #4035

Note: it's probably time for MBEDTLS_TLS_DEFAULT_ALLOW_SHA1_IN_CERTIFICATES to go. (This is just a default, if there are still people who really want to allow SHA-1 in certs - including us in tests if we still rely on a few legacy certs - they can still create a custom X.509 verification profile.)

@mpg I agree. But let's please not discuss individual options on this issue or else it'll become impossible to follow. I've created https://github.com/ARMmbed/mbedtls/issues/4171 for MBEDTLS_TLS_DEFAULT_ALLOW_SHA1_IN_CERTIFICATES.

A list of config options and the decisions made on them is being made here https://docs.google.com/spreadsheets/d/1Jc0IV0Q2q8-b7gMEJfyZZsUwhakhojZvYNpv2KDZIbQ/edit?usp=sharing.
Please feel free to review and add comments to these options for any that you want to keep/remove.

Thanks for sharing the sheet! Some initial thoughts:
Regarding RC4, so far only the ciphersuites in SSL (line 56) are being removed for sure, the crypto primitive itself is still under discussion: #4084 - I suggest referencing that discussion for ARC4_C, MD2_C, MD4_C and their _ALT counter-parts (plus _PROCESS_ALT for MD2 and MD4), which should have the same fate as the _C one.
Regarding MBEDTLS_MPI_WINDOW_SIZE: this is one of the main ways to tune RAM usage for people using RSA or Finite-Field DH. For RSA-4096, the default setting uses a table that consumes 16kB of heap, while the minimal value is 0.5kB. (Double those numbers if RSA_NO_CRT is set.) This is a very significant difference for constrained devices, for a lot of them that's the difference between usable and unusable. Arguably in the future instead of a plethora of specific (and often cryptic) options we should have more general ones such as TRADE_RAM_FOR_SPEED or TRADE_CODE_SIZE_FOR_SPEED that would apply to multiple modules. However I'm afraid it would be more design effort than what we can afford for 3.0, so might have to wait for 4.0.
Regarding PLATFORM_xxx_MACRO: I seem to remember these were introduced for experiments in running the test suites in a baremetal environment. In that use case, compile-time substitution was key to have the code build (including linking the executables) with a baremetal toolchain such as arm-none-eabi-gcc. So it would appear that we need to do be able to do this at compile-time. I think the ability to do this at runtime too is useful in some tests too. So perhaps we need both indeed (if so, this should be documented somewhere). Also, off-hand I don't remember what the difference is between PLATFORM_STD_CALLOC and PLATFORM_CALLOC_MACRO, even less why we apparently thought we needed both. Really this should be better documented.
Regarding MBEDTLS_SSL_MAX_CONTENT_LEN: I think it should go, it was kept only for compatibility reasons after the more precise IN/OUT versions were introduce.
Regarding MBEDTLS_REMOVE_3DES_CIPHERSUITES: I vote we remove this and the library should always behave as it it was enabled.

Regarding MBEDTLS_REMOVE_3DES_CIPHERSUITES: I vote we remove this and the library should always behave as it it was enabled.

+1 vote on that.

Now that the spreadsheet has been created, options have been discussed and issues have been created for each option we wish to remove I am closing this issue as it is finished.


Auto-search on CMD+SHIFT+F

Issue Type: Feature Request
Previously pressing CMD+SHIFT+F while highlighting text would automatically search for the text. Now I have to press that and press return to search.
VS Code version: Code 1.43.0 (78a4c91400152c0f27ba4d363eb56d2835f9903a, 2020-03-09T19:34:44.548Z)
OS version: Darwin x64 19.3.0

/duplicate #91901


Fix changelog url using the github api one instead of the github link

https://github.com/FTL-14/actions-testing/commit/23a7ed0e2f1c7bd1ae029ee1a7878ccb20112cda
commit to prove it works


Not work in Edge

Work really slow in Edge and IE11

plz check this
https://github.com/angular/material/issues/8329


[B03663] Implement and utilize Jobs

Coverage increased (+0.4%) to 24.334% when pulling 9ac509bebe8eda0ac26d307b07a3bd9488492e18 on sprint-sep18-b03663-implement_job into ba5e9aef8f2abca89def018a9f8e2a00cf9c9ac0 on sept-dame-sprint-staging.


Fix ErrorCode for validation rules

We're not assigning the ErrorCode correctly. We should use validation API from GreenEnergyHub.Messaging.Validation (poor man package)


New version: ElijahLopez.MusicCaster version 5.6.5

Pull request has been automatically created using 🛫 WinGet Releaser.
Microsoft Reviewers: Open in CodeFlow

Is it possible to never get mentioned by this bot?

cc @denelon

Is it possible to never get mentioned by this bot?

@elibroftw You are the first to ask this. We use the mention via @msftbot so users get notified when something is happening. It was also part of personalizing the messages from the bot.
What would you like to see different?

I'd like to have an option that I am not notified unless a reviewer @ me. Telling me that my pr needs to be approved is redundant since I manually allowed msftbot to make PRs on my behalf, so I know what will occur. A year or two ago, I would release multiple updates in a single day, so imagine the notifications I'd get then.


Create a packaged release after every merge into main

As a product owner, I would like to be able to have a recent build so that I can demo the latest changes to platform.bible.
Glenn asked for us to release the project after each update into main (or at least that's what we think he's asking for).  We can do this manually, but we should setup the github jobs to do it automatically.

Recommendation: I would leave the existing .github\workflows\publish.yml manual release as is for offical releases that get properly archived as GitHub Releases and add another mechanism running off merges to the main branch. These would exist only as GitHub Action artifacts for a limited time (and not in GitHub Releases).

No need to preserve artefacts.


Added test to verify required features coupling

Fixes #1366 according to task description.

Merging as discussed in the November 5th teleconference.


Error on Windows 10

I get the following errors when i start it on Windows 10.

After hitting continue the apps opens, but if I try to change wallpaper. I see the following SSL/TLS error.
Note - I do have VC++ 2015-2019 Redistributable installed on my PC.

Try my fork https://github.com/qwertydog/Reddit-Wallpaper-Changer


Amend error response to indicate that we return additional error info.

Staring in this preview version, we now return additionalInfo in our error objects. We need to add this here to fix Swagger correctness errors filed against our service.

Approve this PR as it is in preview version.


sendPhoto with notification disabled throws an error

Using bot.sendPhoto with the notify: false option throws the following error:
_http_outgoing.js:456
    throw new TypeError('First argument must be a string or Buffer');
    ^

TypeError: First argument must be a string or Buffer
    at ClientRequest.OutgoingMessage.write (_http_outgoing.js:456:11)
    at Request.write (/tmp/telebot/node_modules/request/request.js:1387:27)
    at FormData.ondata (stream.js:31:26)
    at emitOne (events.js:96:13)
    at FormData.emit (events.js:188:7)
    at FormData.CombinedStream.write (/tmp/telebot/node_modules/combined-stream/lib/combined_stream.js:118:8)
    at FormData.CombinedStream._pipeNext (/tmp/telebot/node_modules/combined-stream/lib/combined_stream.js:106:8)
    at FormData.CombinedStream._getNext (/tmp/telebot/node_modules/combined-stream/lib/combined_stream.js:79:10)
    at FormData.CombinedStream._pipeNext (/tmp/telebot/node_modules/combined-stream/lib/combined_stream.js:107:8)
    at FormData.CombinedStream._getNext (/tmp/telebot/node_modules/combined-stream/lib/combined_stream.js:79:10)

I tracked the error down to methods.js#L289 where form gets passed as data instead of form (according to telebot.js#L262). Changing the line to
return this.request(`/${ url }`, form);

will result in the request going through and the photo being send like expected, but will make the tests fail so i'm sure that's not the root cause. Unfortunately, i'm not familiar enough with the lib to pinpoint it myself.
To reproduce:
const TeleBot = require('telebot');
let t = new TeleBot("TOKEN");
t.sendPhoto("CHAT_ID", "https://telegram.org/img/t_logo.png", {
    notify: false
});

I'm using node v6.7.0, npm v3.10.8 & telebot v1.0.6.

Hi, thank you for your report!
For some reason request library don't like booleans in formData 😕


Generation: combining and string matchers for android

This PR aims to move the combining matchers (and, or, not, etc) to the generated code.
On my machine the tests pass, would love for anyone to verify.

@rotemmiz could you review this?


Update to 6.2

Hi! Cant live w/o your plugin! Do you plan to update?

It cannot use in 6.2 now？

Yea, it didnt work for me last time, said it was outdated and ask to wait for update

can it be used in 6.2 now?

It works, thanks!


fix: Update requirements.txt

Updating the xarray to the latest version

This change is

Looks like we might have to update the Docker image to Ubuntu 20 to pass CI, assuming that's what's holding pip back from finding the latest xarray version. I don't mind updating the base image tomorrow, but feel free to give it a go if you'd like!

It seems that xarray 2022.6 requires python>=3.8, so we need to wait until my other PR lands in master.

Roger that, waiting on #125 .


Test bot fails when brew git is tested

We've been merging failing git builds for far too long - ideally we wouldn't be merging anything that's red. Here is an example failure from git - please ignore the brew test failure here as that is something specific to that version bump. I'm talking about this at the end:
==> brew uninstall --force gettext pcre2

==> git -C homebrew/homebrew-core checkout master -f
==> FAILED
dyld: Library not loaded: /usr/local/opt/pcre2/lib/libpcre2-8.0.dylib
  Referenced from: /usr/local/bin/git
  Reason: image not found
dyld: Library not loaded: /usr/local/opt/pcre2/lib/libpcre2-8.0.dylib
  Referenced from: /usr/local/bin/git
  Reason: image not found

==> git -C homebrew/homebrew-core reset --hard origin/master
==> FAILED
dyld: Library not loaded: /usr/local/opt/pcre2/lib/libpcre2-8.0.dylib
  Referenced from: /usr/local/bin/git
  Reason: image not found

homebrew-test-bot uses whatever git is in the path (or Xcode.app if there's nothing). At the point of failure above, brew git is installed but non-functional because pcre2 is uninstalled. This uninstall is intentional as if there is subsequent formulae being built then we want a cleaner environment, and to also make better use of disk space. The git formula isn't uninstalled to avoid rebuilds if there was a dependent due to be tested in the same job.
In addition to the situation above, the situation is worsened in the event that a git build is cancelled. This doesn't have to be manual - adding another commit to the pull request or force-pushing will trigger a cancellation. If it is cancelled in the middle of cleanup, the brew git install might not be wiped. This issue resulted in mojave_orka_1 having to be taken offline earlier today as homebrew-test-bot currently cannot reach the point of wiping previous installs without a functional git. It requires manually going in and cleaning it up yourself - something I had hoped to have done by now if I wasn't having issues connecting to the Orka service endpoint.
Here is me brainstorming possible solutions:

Always directly invoke system git. There's a few possible approaches:

Directly use /usr/bin/git in homebrew-test-bot.

This will not work on systems without the CLT. That's not an issue for our machines but may be for others using this tap.
It could somewhere else on Linux like /usr/local/bin/git.

Have homebrew-test-bot do the above and also search other locations (including Xcode.app) in the path that are not a part of Homebrew:

This would just end up as a reimplementation of the git shim so I'm not a fan of this approach of duplicating code.

Modify the git shim in brew to have an option or environment variable to alter the search and make brew git a last resort.

I suggest not just making this the default to reduce the chance of breakages.

Notably, git-filter-repo requires a newer git so its tests may fail if we change the default as it may go through the shim.
On Linux, the system git situation seems to be hit or miss at times so best to just avoid that.

How rigourous would we want this? A simple check for a git binary in HOMEBREW_PREFIX/"bin" or more advanced checks to see whether this is actually a brew-installed git rather than one installed from another location?

The shim is a shell script, so doing a more advanced check is a little more tricky than in Ruby and probably requires symlink checking.

Adding an option or environment variable feels a bit like a hack specific to homebrew-test-bot, but maybe there's some legitimate use cases in other scenarios.
Nevertheless, it's currently my preferred option on this list I reckon.

Avoid invoking git in cleanup_after before the brew git is wiped.

This approach might not fix all cases. The wipe only occurs at the very end. What if another formula is tested after git in the same job but said formula invokes git as a part of its download & install process?

git-specific hacks in homebrew-test-bot to uninstall brew git immediately

Problematic if a dependent is built in the same job - need to rebuild again.
Any hack like this probably won't even cover all edge cases - what if that dependent then uses git to download its sources (which should be after git is reinstalled again)?

Other options I haven't thought of?

I can do some work on this and send a pull request if you want.

I've been been thinking about this too but I don't know anything about the internals of testbot. Would it be possible to always use system git in case of a brewed git test?

Directly use /usr/bin/git in homebrew-test-bot.

I reckon this is the best approach for us 👍

I can do some work on this and send a pull request if you want.

That would be great, thanks!

Thinking about it again, a quick fix could be to just do HOMEBREW_GIT_PATH=/usr/bin/git as a part of the Jenkins config. Ideally we'd do it before the test-bot code is invoked - to deal with the case that cleanup wasn't performed - since we run brew update-reset etc. first, but if you think it's better as a part of the codebase somewhere I can do that.

but if you think it's better as a part of the codebase somewhere I can do that.

Yeh, I think so 👍

Ok, will do.
Not sure if the case of mojave_orka_1 has happened before so is probably not very common scenario anyway.

Yeh and even then it should be repaired by this fix I believe.

Well, what caused mojave_orka_1 to collapse was a previous build was cancelled between pcre2 uninstall and cleanup. This meant that a broken brew git was still installed, and git is invoked right from the start for future builds - before brew test-bot is even reached - notably when running brew update-reset and actually also Jenkin's own git cloning (which is configurable). So while changing homebrew-test-bot will fix the much more common case of it simply failing at the end, it probably wouldn't have prevented mojave_orka_1 breaking.

It would have resulted in a broken build but the brew test-bot cleanup stuff would be able to successfully run git and clean up the broken packages at that point. Arguably brew test-bot --cleanup or something could be run before we attempt to run brew update-reset or brew update but given Jenkins isn't long for this world I'm not sure it's worth it.


[WIP][SPARK-4476][SQL] Use MapType for dict in json which has unique keys in each row.

This PR introduces the following changes:

Users can provide a schema with MapTypes to a JSON dataset.
Users can use spark.sql.schema.convertStructToMap to control if we will try to convert a StructType with too many fields (the number of fields is greater than or equal to the threshold set by park.sql.schema.convertStructToMapThreshold) with same data type or a tightest common data type for these field data types exist (using HiveTypeCoercion.findTightestCommonType). Right now, this conversion will not be applied to the schema itself (the top level StructType). Only inner structs are candidate for this auto conversion.
I am introducing one new private[sql] method to DataType (transformUp) and one new private[sql] method to StructType (transformFieldTypeUp). These two can be used to transform data types based the given partial function. My implementation of struct to map conversion is based on these two methods. Another example is nullTypeToStringType in JsonRDD, which transforms all NullTypes to StringTypes for a given StructType.

This is a WIP patch. I will add more unit tests and complete newly added ones later.
JIRA: https://issues.apache.org/jira/browse/SPARK-4476
@davies @marmbrus @willb

I will close it for now. Will get back to it later.


What is the roadmap towards Azure AD Graph API free?

I guess it is good to add a note to the documentation with regards to becoming fully Azure AD Graph API free.
Is the stable version of Az.Resources already Azure AD Graph API free?
During Ignite there was an announcement with a call to action to test out the latest prelease which contains a full move to Microsoft Graph API:
https://techcommunity.microsoft.com/t5/azure-tools/azure-powershell-ignite-release/ba-p/2907139
I am confused. Now it seems that there are still Azure AD Graph APIs being called in the stable version.

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

ID: 769e99f9-0175-083c-f084-d823233b5ba3
Version Independent ID: 8f52d00e-14b5-7fce-c982-2d28b66403f7
Content: Azure AD to Microsoft Graph migration changes in Azure PowerShell
Content Source: docs-conceptual/azps-6.6.0/azps-msgraph-migration-changes.md
Service: azure-powershell
GitHub Login: @mikefrobbins
Microsoft Alias: mirobb

@cveld we'll review your feedback and get back to you shortly. Thanks.

I am not sure if your pointer is helpful. My question is really asking about clarification:

is 5.0.0-preview the only version that is providing a non Azure AD Graph implementation currently?
4.4.1; the latest stable therefore is still using Azure AD Graph.

https://www.powershellgallery.com/packages/Az.Resources

I am not sure if your pointer is helpful. My question is really asking about clarification:

is 5.0.0-preview the only version that is providing a non Azure AD Graph implementation currently?
4.4.1; the latest stable therefore is still using Azure AD Graph.

https://www.powershellgallery.com/packages/Az.Resources

Correct for both questions.

The non Azure AD Graph implementation will become generally available with our next major release of the Az PowerShell module, version 7.x in December of 2021.


FEATURE: Use Scryfall instead of MythicSpoiler API

Scryfall doesn't have a spoilers endpoint, and I can't think of a way to do this easily otherwise (we could query by set and compare but that would require knowing in advance what sets are going to be called...).
Until Scryfall has a dedicated latest spoilers endpoint I'm closing this issue


Style the assessment page

The assessment page is not yet styled/laid out according to the wireframes. The UX needs to be improved and made consistent with the wireframes and other pages.

http://odmat.herokuapp.com/assessments/13/questions/6
Styling is a bit broken? I am using Chrome

Is it that the styles don't match the wireframes or do you think it's something that's not working in chrome?

Actually the issue is covered by #118. Formatting problems are caused by the error message


feat: build manylinux compatible builds

Description
Start building wheels that a manylinux compatible
Fixes #1402
Type of change
Please delete options that are not relevant and/or add your own.

New feature (non-breaking change which adds functionality)

status :
If I don't have torch and tensorrt installed and I run pip install -i https://test.pypi.org/simple/ torch-tensorrt, I get the error
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 20.3/20.3 MB 7.1 MB/s eta 0:00:00
  Downloading https://test-files.pythonhosted.org/packages/3a/1e/bbd08b7b2ef7f96cd4351054deab66457834f4e1436ccb169037e71a39e7/torch-tensorrt-0.0.0.tar.gz (8.9 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [13 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-h8cldzod/torch-tensorrt_f8be91da1be844129bb09646e54b371f/setup.py", line 125, in <module>
          raise RuntimeError(open("ERROR.txt", "r").read())
      RuntimeError:

If they are installed, I don't and it works


20fps Static and 60fps Static 1.1.1 are same files

They are actually 20 fps mod

File is still wrong unfortunately.
There are two extra lines at the bottom in your 60fps file compared to the original file

Ye, i finally fixed it in the 1.6.5, failed in the 1.6.4 sorry
It is good now ?

Yes the file is correct now! Thanks for keeping this collecting up to speed.
Godsent for the current totk situation :)

yw, i'm closing this issue now


Can't load components

(I've temporary disabled CommonChunks to try Carte Blanche)
When I've added a variation to my Button component, I get:
warning.js:44Warning: Failed propType: Invalid prop `component` of type `object` supplied to `Playground`, expected `function`.
common.js.js:1 Uncaught SyntaxError: Unexpected token <
warning.js:44 Warning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components).
invariant.js:38 Uncaught Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.
ReactCompositeComponent.js:772 Uncaught TypeError: Cannot read property '_currentElement' of null

My Carte Blanche configuration is:
new CarteBlanche({
      componentRoot: './app/components',
      plugins: [
        new ReactPlugin({ injectTags: [''] }),
      ],
    }),

My Button component is:
/**
 *
 * Button
 *
 */

import React, { PropTypes } from 'react';
import styleguide from './styleguide';

// Component styling
import CSSModules from 'react-css-modules';
import styles from './styles.styl';

// Component class
@CSSModules(styles, { allowMultiple: true })
class Button extends React.Component {
  static styleguide = styleguide;

  // Default component properties
  static defaultProps = {
    type: 'button',
    primary: false,
  };

  render() {
    // Style of Button's inner element
    let innerStyleName = 'Button__inner';
    if (this.props.primary) innerStyleName += ` ${innerStyleName}--primary`;

    // Type of the button
    const type = this.props.type;

    return (
      <button
        type={type}
        styleName='Button'
        className={this.props.className}
        onClick={this.props.onClick}
      >

          {this.props.children}

      </button>
    );
  }
}

// propTypes definition
Button.propTypes = {
  // The HTML tag button type
  type: PropTypes.oneOf(['button', 'submit', 'reset']),

  // Defines if Button will have the `primary` style
  primary: PropTypes.bool,

  // Function executed on click
  onClick: PropTypes.func,

  // Optional className applied to Button
  className: PropTypes.string,

  // This is the content of Button (usually text)
  children: PropTypes.node.isRequired,
};

export default Button;

I'm using as base react-boilerplate.

Try removing the link to the common.js.js files, I think that's what's throwing the error. (as seen by the line saying common.js.js:1 Uncaught SyntaxError: Unexpected token <)

Removing that line I get:

I'm getting this too. I'm not using commonjs. I wish I could be more helpful but I don't have any idea where to start looking with this one :(
Warning: Failed propType: Invalid prop 'component' of type 'object' supplied to 'Playground', expected 'function'.

Warning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components).

This might have something to do with either webpack 2.0 or react-hot-loader 3.0

I'm also seeing this with webpack 2, (no hot-loader 3)

That's a really annoying bug. :confused: Could one of you possibly provide a stripped down test project so we can replicate this?

I'll make a note to produce a minimal case. Won't get to it until tomorrow though.

Awesome, thanks!

I've been digging a bit and currently tracing back from here where
resources.compiledComponent(componentFile)

is an empty object {}, which is why componentData.getCompiledComponent is returning an empty object as well.
Right now I think this points to the source of the issue.

@ChristopherBiscardi oh wow, thanks for digging in!
If I understand that correctly, an if (componentFile) {} should fix that? /cc @nikgraf

I'm not so sure, componentFile is well defined (in this case app/mark/Test.js), and resources.compiledComponent seems to be working as intended. The value in the contextual require is an empty object. IMO it seems similar to cyclic dependency issues I've seen in the past, where the loaded file is loaded as {} instead of the content of the module.
Everything seems to be pointing at the right location except this is included at the bottom of the Test.js module:
	/* unused harmony default export */ var _unused_webpack_default_export = Test;

/***/ },
/* 349 */
/***/ function(module, exports, __webpack_require__) {

	"use strict";
	/* harmony import */ var __WEBPACK_IMPORTED_MODULE_0_react__ = __webpack_require__(8);
	/* harmony import */ var __WEBPACK_IMPORTED_MODULE_0_react___default = __WEBPACK_IMPORTED_MODULE_0_react__ && __WEBPACK_IMPORTED_MODULE_0_react__.__esModule ? function() { return __WEBPACK_IMPORTED_MODULE_0_react__['default'] } : function() { return __WEBPACK_IMPORTED_MODULE_0_react__; };
	/* harmony import */ Object.defineProperty(__WEBPACK_IMPORTED_MODULE_0_react___default, 'a', { get: __WEBPACK_IMPORTED_MODULE_0_react___default });
	var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();

	function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }

	function _possibleConstructorReturn(self, call) { if (!self) { throw new ReferenceError("this hasn't been initialised - super() hasn't been called"); } return call && (typeof call === "object" || typeof call === "function") ? call : self; }

	function _inherits(subClass, superClass) { if (typeof superClass !== "function" && superClass !== null) { throw new TypeError("Super expression must either be null or a function, not " + typeof superClass); } subClass.prototype = Object.create(superClass && superClass.prototype, { constructor: { value: subClass, enumerable: false, writable: true, configurable: true } }); if (superClass) Object.setPrototypeOf ? Object.setPrototypeOf(subClass, superClass) : subClass.__proto__ = superClass; }

	var Test = function (_Component) {
	  _inherits(Test, _Component);

	  function Test() {
	    _classCallCheck(this, Test);

	    return _possibleConstructorReturn(this, Object.getPrototypeOf(Test).apply(this, arguments));
	  }

	  _createClass(Test, [{
	    key: 'render',
	    value: function render() {
	      return __WEBPACK_IMPORTED_MODULE_0_react___default.a.createElement(
	        'div',
	        null,
	        this.props.title
	      );
	    }
	  }]);

	  return Test;
	}(__WEBPACK_IMPORTED_MODULE_0_react__["Component"]);

	Test.propTypes = {
	  title: __WEBPACK_IMPORTED_MODULE_0_react___default.a.PropTypes.string.isRequired
	};
	/* unused harmony default export */ var _unused_webpack_default_export = Test;

IE: it seems that webpack doesn't think Test.js is being used and attempts to shake it off the tree as a result.

Temporary fix is to use module.exports instead of export default
-- Bug
import React, { Component } from 'react';

export default class Test extends Component {
  static propTypes = {
    title: React.PropTypes.string.isRequired
  }
  render() {
    return (

{this.props.title}

    )
  }
}

-- Good
import React, { Component } from 'react';

module.exports =  class Test extends Component {
  static propTypes = {
    title: React.PropTypes.string.isRequired
  }
  render() {
    return (

{this.props.title}

    )
  }
}

Alternatively, one can remove es2015-webpack in favor of the full es2015 babel preset (for example, if you're using react-boilerplate 3. This uses babel to transpile the imports and you lose tree-shaking. One idea is to use es2015 when running carte and es2015-webpack when compiling for prod using .babelrc's support for envs.

That's annoying though, we shouldn't be forcing people to change their webpack config for carte blanche.
Thanks so much for digging in @ChristopherBiscardi! We'll have to think about how to fix this properly then, any ideas?

It seems that webpack is handling require.context correctly in a minimal test repo. Nothing gets shaken from the context require while other files get properly shaken.
The place I'm looking right now is the dynamic-resolve loader (dynamic-resolve should probably be renamed to -loader, right?), which is responsible for replacing the placeholder file with the code that returns the empty object.
One technique that may work is scooping up the files and injecting them as an array instead of injecting the require.context. I don't actually know if that would work, but it's one way I've handled situations like this without using .context in the past.
const components = [
  require('Test.js'),
  require('OtherComponent.js')
]

Is user-bundle being processed twice?

I'm using es2015 I guess:
  babel: {
    presets: ['es2015', 'react', 'stage-0'],
  },

But I still have the problem.

Alright, with CommonsChunkPlugin and express.js support done (released as 0.2), this is (I think) the last thing to fix for it to be compatible with react-boilerplate. Again, thanks for the investigation @ChristopherBiscardi, that's really really helpful!
Ideally, we wouldn't require people to adapt their code or configs to Carte Blanche. It should _just work_™.
I understand this is quite a hard requirement, and I also think swapping out es2015-webpack for es2015 in development is a fair drawback but I'd rather not people have to do it. Any ideas how we could avoid this issue without people adapting their config?

@mxstbr https://github.com/carteb/carte-blanche/issues/288#issuecomment-224372030 is this a viable solution in your opinion?


Weird 'all day' event in a Nuxt project (with demo)

I did not expect nuxt to not server Dayspan-vuetify properly. I need your help.
Here is the minimal setting that I'm testing with:

https://github.com/chulman444/dayspan-vuetify-nuxt-bug-demo

The all-day events, no matter the duration, takes the whole width of the v-content, located at the top of v-content (right below the v-toolbar), located on top of each other. When the v-navigation-drawer is hidden, it takes the whole width of the application. Dragging doesn't work properly either.
However, events less than 24 hours doesn't seem to have any problems. Again, Vue-served dayspan-vuetify has no problem for me.
I even compared the css of the nuxt-served and vue-served dayspan-vuetify but there doesn't seem no difference.
Please help!

I don't know anything about nuxt so I'm afraid I can't be of any help here. My only goals for this library are for Vue & Vuetify support. I don't have time for much else!
If you find a solution please share and I will see if I can make it in this library without interrupting the expected uses.


Rotate digits of a number by K

number => 123456
k => 2 (rotate clockwise | shift left)
result => 345612
is this is what's needed

i can work on this

@micky2001 Are you still working on this or should I assign it to @mahendra1290 ?

@amritansh22 if @Badal-Jha is not working on this issue, please assign this issue to me.

@AKSHATNEMA Done

@amritansh22  Can I submit my approach ? I have a better solution than the one provided since the merged one is not an IN-PLACE SOLUTION (which is the ideal one)
I can do this using Juggling Algorithm without creating EXTRA SPACE

Please assign this issue to me.


request:  Discord slash commands palette for bots support

Is your feature request related to a problem? Please describe.
Sometimes I forget the exact format of a command. Discord has introduced bot commands to the / palette with the latest update, as described here from their last changelog:

Postulated new slash commands for bots. Performing actions with bots is easier than ever. Now, developers can have a list of commands available for their bots accessible by the slash key (/). You won’t have to remember bot commands anymore and get laughed at when you get the command wrong :( !help…..!help….please

Describe the solution you'd like
Implementation of the feature described here, with consideration for any limits of the functionality or use for specific commands only.

New palette as-is:

That's called slash command, it's in our roadmap to support them, but we don't have the facility to do so with version 5 (due to limitations with current Skyra Core and Klasa).
I will add this to the version 6 roadmap, as this and many other features will be possible since then.


Add Gov-Client-Browser-JS-User-Agent header to HMRC

Description of what's changing
Add Gov-Client-Browser-JS-User-Agent header to HMRC
Which issue does this PR relate to?
Solves #124
Checklist
[ ] Tests are written and maintain or improve code coverage
[ ] I've tested this in my application using yarn link (if applicable)
[ ] You consent to and are confident this change can be released with no regression

@skodamarthi Mind adding hacktoberfest-accepted label on the merged PR?


Build failed

Hi,
When im open the code in XCode6.3.1 I got an Issue in STableViewController.
Please find the Below Issue.
ld: -pie can only be used when targeting iOS 4.2 or later
clang: error: linker command failed with exit code 1 (use -v to see invocation)

@Nandulucky This library has been deprecated in favor of SKStatefulTableViewController


Improve mechanism features

Currently, the mechanisms are behind feature flags, but most of them are enabled by default via the default-mechanisms feature.  The Mechanism enum always contains all mechanisms, not depending on the activated features.
This approach has some problems:

Mechanisms from the default-mechanisms feature set cannot be disabled as soon as one crate in the dependency tree pulls in trussed without disabling the default features.
Failure to enable a required mechanism leads to a potentially hard to debug runtime error instead of a compiler error.
It is hard to synchronize the mechanism set between different crates.  How can a custom backend detect whether it uses the same mechanism set as the trussed crate?

I’m not sure what the best solution would look like.  I want to suggest the following as a basis for discussion:

All mechanism features are disabled by default.  Clients need to explicitly enable the mechanisms they require.  This ensures that only the required mechanisms are actually enabled, improving binary size and stack usage.
The Mechanism enum only contains the enabled mechanisms.  This ensures that missing mechanism features lead to a compiler error in the client.
We introduce a Mechanisms helper struct (see below) that can be used to trigger a compiler error if a backend or the firmware does not have the same mechanism set as Trussed.

Mechanisms
In Trussed:
#[non_exhaustive]
pub struct Mechanisms {
    #[cfg(feature = "aes256-cbc")]
    pub aes256_cbc: bool,
    #[cfg(feature = "ed255")]
    pub ed255: bool,
    // ...
}

impl Mechanisms {
    pub const fn new() -> Self {
        Self {
            #[cfg(feature = "aes256-cbc")]
            aes256_cbc: false,
            #[cfg(feature = "ed255")]
            ed255: false,
        }
    }

    pub const fn all_supported(&self) -> bool {
        let mut all_supported = true;
        #[cfg(feature = "aes256-cbc")]
        all_supported = all_supported && self.aes256_cbc;
        #[cfg(feature = "ed255")]
        all_supported = all_supported && self.ed255;
        all_supported
    }
}

In a backend or runner:
const _ENSURE_MECHANISMS_SUPPORTED: () = {
    let mut mechanisms = trussed::Mechanisms::new();
    #[cfg(feature = "aes256-cbc")]
    mechanisms.aes256_cbc = true;
    #[cfg(feature = "ed255")]
    mechanisms.ed255 = true;
    assert!(mechanisms.all_supported());
};

This would be a significant breaking change but I like it.
I also like that the required mechanisms are not one more trait bound. Maybe the const assertion in the backend or runner can be created through a macro.

On second thought, a simpler solution instead of (3) would be to just add an ExhaustiveMechanism enum that implements From<Mechanism> and is documented to not follow semver.

Actually, there is a much simpler approach:  have a Mechanism::ALL constant with the activated mechanisms.  You can then iterate and match over the elements of this constant in a const assertion and panic if there is an unexpected entry.


scope_where_ids_in for large collections

I've just been stepping through the code of what happens when I run chewy:update[my_index] and it looks a bit dicey to me, if you've got a large amount of documents to be indexed. For example, I have a  collection that is ~ 350k documents. It appears to be the case that chewy selects the ids of all documents into a 350k array. This works out to be nearly 30MB in size. It then sends this 30MB array over the wire as part of a single in query.....
My database needs an :ambulance: .  :smile:

Got it, I'm working on it :) I've just decided to use default scope in more obvious manner, so it would be possible to restrict the scope in indexed document for particular index completely. And actually I'be got an idea of subquery using for activerecord instead of fetching ids, but it seems like I would have the same effect in mongoid as well, so I've just decided to use subquery in AR and to fetch ids in mongoid in batches. Would implement this really soon, thanks for the report.

Could you try current master please? It should be just fine.

Yeah this is better. Thanks.


YouTube icon lettering is uneven

Particularly the b in Tube. The lettering is also pretty jagged.

Yup - a consequence of minimisation. I'd be grateful if you can find a way to improve it :-)

It seems like the icon you're supposed to use is actually https://www.youtube.com/yt/about/media/images/brand-resources/icons/YouTube-icon-our_icon.png anyway; maybe switch to that?

Aha! A much better idea. Do you know if there's an SVG somewhere for reference?

Seems like the only files they give for reference are in
here (from https://www.youtube.com/yt/about/brand-resources/#logos-icons-colors under "The YouTube Icon"), and most of them are .png with no .svg in sight. Sorry...

There's an EPS there I can use as a vector. Thanks!


Javascript VM BYTE opcode bug

Environment:

https://remix.ethereum.org
solidity 0.4.20
JavaScript VM
pragma solidity ^0.4.20;

contract Varint {
   event PrintB(string _name, uint8 _value);

   function decode(bytes bs) public returns (uint8) {
     uint8 v;
     assembly {
         v := byte(0, mload(add(bs, 32)))
     }

     PrintB("v", v);
     return v;
   }

Investigation

I looked through the debug trace, the VM dies at BYTE opcode. The stack is clean and the input parameters to BYTE opcode is correct. I suspect this is related to implementation of BYTE on java script VM.

I can confirm this. It is especially bad, because it prevents libraries from being deployed, because they all have a check that uses the byte opcode.

remix.ethereum.org has been updated with latest ethereumjs-vm version, that should be ok now


Getting timeout: context deadline exceeded for aws_dax_cluster related controls

Describe the bug

The error Getting timeout: context deadline exceeded was due to the long retry for the unsupported region issue in Dax Clusters. This PR contains the fix, It will be released soon.


error downloading daprd binary: stream error: stream ID 1; PROTOCOL_ERROR; received from peer

root@ubuntu:~/dapr# dapr init
⌛  Making the jump to hyperspace...
ℹ  Installing runtime version 1.6.0
→  Downloading binaries and setting up components...
↓  Downloading binaries and setting up components...
↑  Downloading binaries and setting up components...
→  Downloading binaries and setting up components...
↓  Downloading binaries and setting up components...
❌  Downloading binaries and setting up components...
❌  error downloading daprd binary: stream error: stream ID 1; PROTOCOL_ERROR; received from peer

It seems to be a network problem. Could you re-produce this problem?


Multi-store support

Just want to ask if this powerful application is capable of handling multi-store e-commerce similar to aliexpress? If not, please is there any ongoing plan for that?

It is possible to set it up with partners for each store, and even django sites for each store.
Also see https://github.com/django-oscar/django-oscar-stores , and especially https://github.com/django-oscar/django-oscar-stores/issues/127

Hi there. We use Github only for managing bugs and feature requests, and not for support. We recommend that you ask for help on Stack Overflow using the django-oscar tag, or joining our slack workspace and asking a question there. Oscar has all the scaffolding you would need to set up a platform with multiple merchants.


Using audit endpoint

I have a problem with using endpoint /diagnosiskeys/audit/download/{date}/{batchTag}.
If some country uploads two set of keys in the same moment, this keys will be pushed to one batch tag. Afert that I download this batch I call audit endpoint and it serves me two autdits for the same country with different other data.
How I can validate downloaded EfgsProto.DiagnosisKeyBatch with downloaded AuditEntry?
You provided example code to using but this algorithm can't work with multiple audits from from the same country.

To validate the audits correctly, you have to use the amount in the audit response. You can find an example here:
https://github.com/SchulzeS/efgs-federation-gateway/blob/feat/extendedauditingtest/src/test/java/eu/interop/federationgateway/auditing/BatchAuditor.java
This calculates the signature out of the given diagnosiskeys and compares it to the audit entries. This works also for multiple entries of the same country.

@TomaszMolenda do you have any further questions or can we close this issue?

@TomaszMolenda do you have any further questions or can we close this issue?

You can close it


Mythic Metals Platinum not showing in REI??

No idea

Is platinum ore generation disabled? When disabled all Platinum items from MM are automatically hidden in REI, since they cannot be obtained normally anymore

yes it is, although I want the block to be shown

I might look into a better solution for the REI hiding, though I do want to point out Platinum does not have a tool & armor set.
If Star Platinum gear is being hidden by this, then that is a bug, and will be fixed.

Well, I can use kubejs worldgen events to circumvent this. But for now, this technically isnt a bug so ill close it


Body data type file as binary body

Describe the bug
In my API I have an endpoint that accept octa-stream with a binary body file.
I tried to define it like:
// @Summary Image file upload
// @Tags image
// @Accept octet-stream
// @Param file body file true "Image file"
// @Success...

But the CLI does not recognise file as data type:
ParseComment error in file /..../main.go cannot find type definition: file

Could it be that Swagger is not able to support file upload without multipart form?
To Reproduce
Steps to reproduce the behavior:

Place the above mentioned spec in a file
Run swag init
See error log

Expected behavior
That file will be resolved and that I can select a file in the swagger ui using the generated swagger json.
Your swag version
e.g. v1.8.12
Your go version
e.g. 1.20.2
Desktop (please complete the following information):

OS: MacOS
Version: 13.3.1 (22E261)

// @Param file formdata file true "Image file"

I ran into the same problem and used this as a workaround
//	@Param	Content	body	os.File	true
If you do not want to upload the file as application/formdata
OpenAPI Spec 2.0 does not support specifying the raw file as the payload
See in the FAQ on the bottom

Uploads where the payload is just the raw file contents are not supported in Swagger 2.0, because they are not multipart/form-data. That is, Swagger 2.0 does NOT support something like:

curl --upload-file archive.zip http://example.com/upload

@mariusgassen Thank you for the response and your workaround suggestion.


Provide utility class to provide portal user info

This PR adds a utility class, that will provide an optional PortalUser with user information, so that the app can list user based project information.

 E01.05: Create class that holds logged-in user information

@KochTobi thanks a lot, addressed your requests


Want to add back to top option

I want to add back to top option to make it easy for the user.
Please assign this issue to me under gssoc-ectd and hacktoberfest.

someone already working on this issue


WIP - v0.3 - 3/4" Tubing U-bend Adapters

PR for the creation of custom 3/4 inch tubing adapters for flow tubing to filters.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: martukas:x: tijanimYou have signed the CLA already but the status is still pending? Let us recheck it.


Dom update 2020-03-18

For 3.9
There are a lot of baseline changes with this one because the type of console.log changes from (message?: any, ...optionalArguments: any[]) to (...data: any[]), which is more sensible anyway. I don't think the first argument is different from the rest.

@orta reviewers list isn't working, so I'm tagging you this way in case you're interested. I'll merge after CI is green.


Write a R program to print diamond pattern

Description
Write a R program to print diamond pattern
Input  : 5

Output :
    *
   ***
  *****
 *******
*********
 *******
  *****
   ***
    *

How to contribute

Save the solution in program/print_diamond_pattern.r file
Add print_diamond_pattern.r file in print-diamond-pattern folder

!assign

do check #4785


Refactor integration tests for clarity and speed

The current integration tests have too much boilerplate that can be
refactored with some new APIs. Additionally, the integration tests are
incredibly slow due to all the forking and creation of new VMs. This
fixes both of these issues.
The new integration test API creates a new runCLI function, accepting
an array of string arguments (with a new "args" string interpolator to
make specifying this array easier), various execution parameters, a
function that contains the normal Expect logic all our of integration
tests already use, and finally the expected exit code.
A new path function is created to help deal with paths in a OS
agnostic manner.
New withTempFile and withTempDirectory functions are added to help
with creating temporary files in a special temporary daffodil directory,
and to ensure they are cleaned up when the test is complete.
A new withSysProp function is used to temporarily change and restore
system properties, helping to avoid changes that might interfere with
other tests.
With these new functions, integration tests now look something like
this:
    val schema = path("path/to/schema.dfdl.xsd")
    runCLI(args"parse -s $schema") { cli =>
      cli.send("data to parse", inputDone = true)
      cli.expect("<data>string to expect</data>")
    } (ExitCode.Success)

The runCLI function supports executing Daffodil in either a new process
or thread, defaulting to thread unless a test requires a separator
process (e.g. classpath changes). Streams are setup for handling
stdin/out/err. When threaded, the thread calls the
org.apache.daffodil.Main run function, and configures Main and log4j to
output to these streams. When using a new processing, the daffodil
sh/bat script is directly executed.
A new Expect instance is configured so that it can read/write to these
streams and validate the output, with a new CLITester class used to
provide helper wrappers around Expect to make logic a bit less
verbose.
Multiple changes were also made to Main and the Debugger to ensure they
always use the specified streams instead of always using stdin/out/err.
This is really only needed for this integration testing, but could
potentially be useful in other use cases where stdin/out/err need need
to be mimicked without forking a new process.
Note that the thread approach isn't thread safe, but integration tests
are already not run in parallel. By using threads instead of spawning
new processes where possible, we drastically decrease the overhead, with
test suites now taking a number of seconds instead of a number of
minutes, averaging and order of magnitude speed up.
This also tweaks various CLI tests to not expect data from files,
instead hardcoding what to expect in each test. This is a bit less
exact, but it make the logic simpler and more consistent, and allows us
to remove many files from the repo. Also found and removed many debugger
command files that are never actually used.
This also enables the blob CLI tests but adds an assumption so that they
are skipped if the large input files have not been generated. This gives
us a reminder that those tests exist and we can periodically ensure they
work by generating the files.
This also ensures coverage is enabled in the github workflow every time
we execute SBT. Otherwise, changes of coverage enablement cause a
recompile. By doing this we avoid recompiling the same files multiple
times which saves a couple of minutes overall. Note that we originally
disabled coverage on some steps because it caused failures, but whatever
caused that seems to have been fixed.
DAFFODIL-2381

I've completed the refactor using a new API and address all comments, I think this is ready for a full review.

Looks like the PR checks finished in 17-25, with most taking about 20 mins. Compared to the most recent merged commit which took between 30-60 averaging on the higher end, this is a nice speed up.

This will be post 3.4.0, i.e., on the 3.5.0 branch yes?

This will be post 3.4.0, i.e., on the 3.5.0 branch yes?

Correct, once this gets the +1's, I'll hold off merging until 3.4.0 is released.

We also may need to increase code coverage (this pull request currently hits only 65% code coverage).

I didn't really add any new code except in couple minor places. I think lack of coverage in this PR is because I've made changes to printlns that were just already missing coverage.
In the  past I know I've hesitated to add new CLI tests to get coverage because of the high overhead. But now that integration tests are much quicker, we may want to consider adding new tests to improve our CLI coverage. I think that's out of scope for this PR though, since this is more about just improving the CLI test infrastructure.

When this says 64% coverage, is that the unit tests plus the CLI tests? Or just the CLI tests alone?

I believe it's both unit tests + CLI tests. But most of the lines missing coverage are println's in Main.scala that can only be tested with he CLI/Integration tests.

Something doesn't add up.
We were at roughly 80% coverage on a 110K-lines code base.
We dropped to 64% coverage.  That's a 16% drop, meaning 17K-lines are no longer covered that were.
That's can't be explained by println statements in the Main/CLI code.
So I'm assuming my arithmetic here doesn't make sense. But I clearly don't understand what we mean by 80+% dropping to 64% coverage.

I think that 64% is just the the coverage of this PR, not the coverage of the entire codebase. So of the lines this PR changed to src/main, 64% of those lines have a test that hit them. The overall coverage is still about 80%.
Here's the codecov page for this PR that makes it a bit more clear:
https://app.codecov.io/gh/apache/daffodil/pull/865

Ok. Then I suggest adding a ticket to enhance code coverage here. But I wouldn't hold up committing this much improvement for that.

DAFFODIL-2746 added to improve CLI code coverage.


Restrict the version of connection

Verison 0.2.6 of the connection library switched from Handles to
Sockets which resulted in a number of bizarre unintended side
effects like data leaking from TLS connections into HTTP responses.
Until 0.2.6 is fixed, we will lock connection to the previous
version.

Connection fix. Looks like only the autoscaling tests failed.

Both tests look like they were rate limited.
@nhibberd This mean 8.0 is fixed?

Looks like it

So , good to merge?

I can't see a reason not too, @charleso ?

👍


An error occurred while Style/TrailingCommaInArguments cop was inspecting...

Expected behavior
RuboCop reports offenses (if any) without any unknown error.
Actual behavior
RuboCop reports no offenses but ends with an unknown error.
Steps to reproduce the problem
$ cat test.rb
foo.bar(
  x: 1,
)&.fetch(:y)

$ bundle exec rubocop test.rb
Inspecting 1 file
An error occurred while Style/TrailingCommaInArguments cop was inspecting /Users/domon/src/elements-revenue-period-finalizer/test.rb:1:0.
To see the complete backtrace run rubocop -d.
.

1 file inspected, no offenses detected

1 error occurred:
An error occurred while Style/TrailingCommaInArguments cop was inspecting /Users/domon/src/elements-revenue-period-finalizer/test.rb:1:0.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
https://github.com/rubocop-hq/rubocop/issues

Mention the following information in the issue report:
0.64.0 (using Parser <IP_ADDRESS>, running on ruby 2.6.0 x86_64-darwin18)

RuboCop version
$ bundle exec rubocop -V
0.64.0 (using Parser <IP_ADDRESS>, running on ruby 2.6.0 x86_64-darwin18)

What is your configured TargetRubyVersion? To be able to parse the lonely operator (&.), it needs to be 2.3 or higher.

Hi @Drenmi 👋
I can reproduce the error with TargetRubyVersion: 2.6 with RuboCop 0.64.0.
The following is my minimal .rubocop.yml to reproduce the error.
AllCops:
  TargetRubyVersion: 2.6
Style/TrailingCommaInArguments:
  EnforcedStyleForMultiline: comma
Style/FrozenStringLiteralComment:
  Enabled: false

Thanks! I was able to reproduce the issue on master with the settings you provided. 🙇


create-cluster-kubeadm: fix typo in "master" label

A prior change to modify the command for control plane
untaint introduced a typo "control-master-". Fix it,
as it should be "master-".
https://github.com/kubernetes/website/pull/31391/commits/806518df130f7fa1daa0a82dd51499daa94e9591#diff-3f8a89709e5cc8ce9dd6404c2b29d0aef5ab2a9797ddbd2889299661f6f635a0R293
/cc @sftim

/sig cluster-lifecycle
/kind bug

/approve

/lgtm


MacOS and/or Linux support

Are there any plans to create servers for MacOS or Linux? It would be great.

We are working on it but it takes time.

I was also interested in this at first, but considering that there is a great web client available, why not focus on this instead?
Eg. a "linux" client could even just be an electron app packaged with the web client which would probably work great already imho.
I feel like instead effort would be better put into supporting many of the other proposed features 🤔

I would also love a Linux server.
In the meantime, I found this alternative https://stream-pi.com/ which works OK but it is not as polished as Macro-Deck. Don't let the "pi" fool you, you don't need Raspberry pi, it works on any OS.  I use it with Linux on my laptop as server with OBS, and an Android app client.

If you need a linux tester, i`m in.
Any progress??

Hi,
I use this here currently:
https://controlpage.gitlab.io/controlpage-docs/
Currently only for tech-savy people unfortunately, as this requires you to use some other service that accepts http rest requests and then controls the actual device,...
This can f.e. be combined with ioBroker. As this is where my smarthome stuff is all already connected anyway. This way I can easily control my lights.
Or Hacking together some python (flask) yourself (with a little gpt help ;)) and then use tools like xdotool to do the desktop control part.


Tests: refactor trainer

What does this PR do?
Fixes # (issue).
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Hello @Borda! Thanks for updating this PR.

In the file tests/base/eval_model_train_steps.py:

Line 44:22: W292 no newline at end of file


1.14

Basic 1.14/18w43b support. Joining works. Items, BlockStates and Entity Ids are remapped. ~BlockLight and SkyLight is not send, I guess the client is awaiting this information and is only rendering chunks after you mine/place a block.~ Lights are send in the new Light Update Packet ;)
Block Id and Biome Id mappings are still missing.

so this would work with protocolsupport ?

so this would work with protocolsupport ?

It should.


[New Feature]: Auto Commenting when an Issue is Closed

🎮 feature Request
Contributors may feel neglected or uncertain about the status of their issues if they are closed without any feedback or acknowledgment. This can lead to frustration and a decrease in motivation to contribute further.
The solution is to automatically post a comment on the issue whenever it gets closed. This comment should thank the issue creator for their contribution and inform them that their issue has been closed. The message can include the issue number and a friendly greeting to make it more personal. This automation ensures that every closed issue receives a consistent and timely response, improving communication and contributor experience.

Point down the features
This feature aims to solve the problem of poor communication and lack of acknowledgment when issues are closed. By automatically commenting on closed issues, it ensures that contributors are informed about the closure and are thanked for their efforts. This helps maintain a positive and engaging community atmosphere, encouraging continued contributions and fostering good relationships between maintainers and contributors.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

@Durgesh4993 please assign me this issue

Please raise any other issue, i'll assign you...
If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created separate channals for all projects...
Thank you :)


RunId link shows blank page for completed child workflows

Repro:

Run a parent workflow with child workflow
Open parent workflow page
Under ChildWorkflowExecutionStarted event press RunId link

Expected:

Child workflow page is opened

Actual:

Blank page

doesn't reproduce anymore. This was likely fixed by this change https://github.com/temporalio/web/pull/122

this was actually fixed here https://github.com/temporalio/web/pull/151


Excuse me, how to count() Many-to-Many?

Sys_role.find()
.where({id: roleid})
.populate('users', {where: where, skip: start, limit: pageSize, sort: sort})
.exec(function (err, obj) {
});//paginate
How to count the number of users to meet the conditions? Without query()

and ...How to query the user in addition to the above conditions?
.populate('users', {where: {'!',where}, skip: start, limit: pageSize, sort: sort}) ?..


EuropaPark

Updating EuropaPark request and response

Closed : fix mandatory for node v0.8

New PR with fix : #28


Disjunction Regression in v0.5.0-beta.5

What version of CUE are you using (cue version)?
$ cue version
cue version v0.0.0-20230211165554-7d89acd5c44b

go version go1.19.5
       -compiler gc
     CGO_ENABLED 1
          GOARCH arm64
            GOOS darwin
             vcs git
    vcs.revision 7d89acd5c44bca0c756f76089436ee9913818b03
        vcs.time 2023-02-11T16:55:54Z
    vcs.modified false

Does this issue reproduce with the latest stable release?
The latest stable release (v0.4.3) works as expected.
What did you do?
Consider the following:
metrics: [...#Metric]

metrics: [{
	id:  "foo"
	avg: 60
}, {
	id:    "bar"
	value: 80
}, {
	uri: "baz"
	avg: 70
}, {
	uri:   "qux"
	value: 90
}]

#Metric: {
	#Source
	#Target
}

#Source:
	#IDSource |
	#URISource

#Target:
	#TargetAverage |
	#TargetValue

#IDSource: {
	id: string
}

#URISource: {
	uri: string
}

#TargetAverage: {
	avg: number
}

#TargetValue: {
	value: number
}

What did you expect to see?
{
    "metrics": [
        {
            "id": "foo",
            "avg": 60
        },
        {
            "id": "bar",
            "value": 80
        },
        {
            "uri": "baz",
            "avg": 70
        },
        {
            "uri": "qux",
            "value": 90
        }
    ]
}

This is the case when using either of the following CUE versions:

v0.4.3
v0.5.0-beta.2

What did you see instead?
Errors pertaining to errors in empty disjunction and field not allowed.
I managed to bisect this down to https://review.gerrithub.io/c/cue-lang/cue/+/549079 (5a6bd1910821112123897c2b553b848c15f6eae2).

Error
metrics.0: 2 errors in empty disjunction:
metrics.0.avg: field not allowed:
    ./repro.cue:1:11
    ./repro.cue:1:14
    ./repro.cue:5:2
    ./repro.cue:17:10
    ./repro.cue:18:2
    ./repro.cue:23:2
    ./repro.cue:30:12
metrics.0.id: field not allowed:
    ./repro.cue:1:11
    ./repro.cue:1:14
    ./repro.cue:4:2
    ./repro.cue:17:10
    ./repro.cue:18:2
    ./repro.cue:24:2
    ./repro.cue:34:13
metrics.1: 2 errors in empty disjunction:
metrics.1.id: field not allowed:
    ./repro.cue:1:11
    ./repro.cue:1:14
    ./repro.cue:7:2
    ./repro.cue:17:10
    ./repro.cue:18:2
    ./repro.cue:24:2
    ./repro.cue:34:13
metrics.1.value: field not allowed:
    ./repro.cue:1:11
    ./repro.cue:1:14
    ./repro.cue:8:2
    ./repro.cue:17:10
    ./repro.cue:18:2
    ./repro.cue:23:2
    ./repro.cue:30:12
metrics.2: 2 errors in empty disjunction:
metrics.2.avg: field not allowed:
    ./repro.cue:1:11
    ./repro.cue:1:14
    ./repro.cue:11:2
    ./repro.cue:17:10
    ./repro.cue:18:2
    ./repro.cue:24:2
    ./repro.cue:34:13
metrics.2.uri: field not allowed:
    ./repro.cue:1:11
    ./repro.cue:1:14
    ./repro.cue:10:2
    ./repro.cue:17:10
    ./repro.cue:18:2
    ./repro.cue:23:2
    ./repro.cue:30:12
metrics.3: 2 errors in empty disjunction:
metrics.3.uri: field not allowed:
    ./repro.cue:1:11
    ./repro.cue:1:14
    ./repro.cue:13:2
    ./repro.cue:17:10
    ./repro.cue:18:2
    ./repro.cue:23:2
    ./repro.cue:30:12
metrics.3.value: field not allowed:
    ./repro.cue:1:11
    ./repro.cue:1:14
    ./repro.cue:14:2
    ./repro.cue:17:10
    ./repro.cue:18:2
    ./repro.cue:24:2
    ./repro.cue:34:13

If I make the following change, the result works, as expected:
@@ -19,22 +19,16 @@ metrics: [{
 	#Target
 }

-#Source:
-	#IDSource |
-	#URISource
+#Source: {
+	id: string
+} | {
+	uri: string
+}

 #Target:
 	#TargetAverage |
 	#TargetValue

-#IDSource: {
-	id: string
-}
-
-#URISource: {
-	uri: string
-}
-
 #TargetAverage: {
 	avg: number
 }

This might well be a duplicate of https://github.com/cue-lang/cue/issues/2246, given that the bisect points to exactly the same CL, one of your errors is also "field not allowed", and both use disjunctions with definitions in a very similar way.
It's probably worth keeping this open as a separate issue in case my suspicion is wrong, but we should see if fixing the previously reported regression also fixes this.


Husky to simple-git-hooks migration in mrm

mrm recently migrarted from husky to simple-git-hooks. I updated the text according to these changes.
This mrm migration brought  these benefits to users:

simple-git-hooks has 0 dependencies and took 10 KB of node_modules space compared to 1 MB of husky 4.
simple-git-hooks doesn’t read config on every pre-commit hook call which increases the performance. It uses the husky 5 model when you need explicitly to call a script on config changes. But it is a good trade-off for lint-staged case. It should give around a 0.5 second performance boost for pre-commit.

Comparison with husky 5:

We can start having all husky 5 benefits (performance, small size) without waiting for MIT license for husky 5.
simple-git-hooks is smaller than husky 5.
husky 5 requires extra scripts in package.json.
husky 5 requires an extra pinst dependency for Yarn 2. simple-git-hooks has out-of-the box Yarn 2 support.

I already tested simple-git-hooks on Autoprefixer, PostCSS, Browserslist, and my commercial projects (with a big team). Everything works great. Other people reported about successful migration too. @toplenboren simple-git-hooks maintainer is always open for the changes and answers quickly.

@ai thanks for the PR!

This looks great indeed. I didn't know about this package.


tsvector/tsquery column types

Maybe it can also be beneficial to add tsvector and tsquery to the supported types for fulltext search.
https://www.postgresql.org/docs/10/datatype-textsearch.html

Do you know any use case? A tsvector is always dependent on a language, so normally you save the raw text and create a tsvector index for a language. I have never seen a tsvector or tsquery saved in a table. But maybe there are use cases i am not aware of 🤷♂

Not so sure about tsquery but I’ve added some generated columns of type tsvector in a recent project. Should improve performance rather than doing it on the fly.

A generated tsvector column sounds like a good use case. Bit i am not sure whether an index can be used in this approach. A tsvector is always dependent on a language which can be changed all the time by the default_text_search_config setting. I will have to try if this approach is index supportable in the next days. I keep you updated.

In my case, I know that my content will be in English, so I hardcoded that in. Just checked one of my queries with EXPLAIN ANALYSE and it did use my GIN index.

You are correct, an index can be used without any problem. When someone changes the default_text_search_config the stemming of the vector may not be correct for the query, but that's a problem for the developer. 🤷♂


[Feature request] Word counter on the statusbar please

It'd just be nice to be reminded of how long the document is.
Just something that lists how many words are in the document. Counting the spaces.
While we're on the topic, it might be useful to try counting sentences and paragraphs?

I have no plan to add this feature and even if I add it, it will be part of utility tools instead of showing it as built-in or by default. I am planning to add "utility" button in right click context menu and it will offer some most used features like "string <=> base64", "Json validator/formatter", "Search with ..." etc.. I will definitely consider word count as well.


Move some files into models' sub packages

[x] Move release, collbrator, Upload to models/repository
[x] Move action, notification, ActivityStats, Statistic, Heatmap to models/activities
[x] Move task to models/admin
[x] Move Tokens to models/auth
[x] Move MiniOrg to models/organization

Unit tests fails

@lafriks Fixed.

Codecov Report

Merging #20262 (0332b03) into main (9e0c437) will increase coverage by 0.03%.
The diff coverage is 51.79%.

@@            Coverage Diff             @@
##             main   #20262      +/-   ##
==========================================
+ Coverage   47.03%   47.06%   +0.03%
==========================================
  Files         993      997       +4
  Lines      136484   136478       -6
==========================================
+ Hits        64198    64239      +41
+ Misses      64402    64356      -46
+ Partials     7884     7883       -1

Impacted Files
Coverage Δ

cmd/admin.go
0.00% <0.00%> (ø)

models/activities/action_list.go
74.28% <ø> (ø)

models/activities/notification.go
62.22% <0.00%> (ø)

models/activities/statistic.go
0.00% <0.00%> (ø)

models/admin/task.go
34.00% <ø> (ø)

models/error.go
44.11% <ø> (+5.45%)
:arrow_up:

models/org.go
45.33% <ø> (-17.66%)
:arrow_down:

models/repo/repo.go
61.73% <0.00%> (-0.89%)
:arrow_down:

models/repo/upload.go
2.08% <0.00%> (ø)

models/repo_collaboration.go
51.02% <ø> (-2.83%)
:arrow_down:

... and 109 more

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


Example doesn't work? [Bug on Domain class]

I tried to reproduce this example from the docs locally
from fuzzylogic.classes import Domain
from fuzzylogic.functions import bounded_sigmoid

T = Domain("temperature", 0, 100)
T.cold = bounded_sigmoid(5,15, inverse=True)
T.cold.plot()
T.hot = bounded_sigmoid(20, 40)
T.hot.plot()
T.warm = ~T.hot & ~T.cold
T.warm.plot()
T(10)

The docs are deprecated, as the package is now called fuzzylogic instead of fuzzy but when I tried to execute this code I got this exception:
Traceback (most recent call last):

  File "/Users/suporte/miniconda3/envs/image-quality-lib/lib/python3.7/site-packages/IPython/core/interactiveshell.py", line 3437, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)

  File "<ipython-input-27-4457960f5d30>", line 1, in <module>
    from fuzzylogic.classes import Domain

  File "/Users/suporte/miniconda3/envs/image-quality-lib/lib/python3.7/site-packages/fuzzylogic/classes.py", line 420
    if (x := min(actual_values[k] for k in K if k in actual_values)) > 0]
          ^
SyntaxError: invalid syntax

Is there any solution or alternative for the class package?

Hi,
it's not a bug. The walrus operator was introduced in python 3.8, you're using 3.7 which doesn't support this syntax.
It's not a crucial detail, I could change the implementation to be backwards compatible or I could update the requirements, which do you prefer?

Hi @amogorkon ! Thanks for the fast reply! I don't have any problem with updating my python to 3.8. Maybe being backwards compatible could expand which projects can use your lib so it's up to you ;)

Well, 3.8 is pretty much standard in python3 land currently, so it's easiest to update requirements.

Can we close the issue?


alembic.run uses non-existing command

Seems like alembic.run command uses python.run_python command which is not presented in python module

@LeonidMalin should be fixed in this version https://github.com/saritasa-nest/saritasa-python-invocations/releases/tag/0.4.0


Change Travis config

TravisCI should only run in one single container. This should decrease build times

done with #65