webpack_require.d is not a function

Bug report

What is the current behavior?
I have a big/medium sized project using webpack 5.36.2. just migrated from webpack 4.44.2. which worked fine for my team but the speed improvement between those two versions is just insane. Thank you for that.
I noticed that optimization.runtimeChunk = true gave an extra performance boost, but the resulting bundle shows an error "webpack_require.d is not a function" which seams to happen just in that project. i tried to isolate the error in a small test repo. if i set optimization.runtimeChunk = false then the error disappears, but the build time is significantly higher.
sometimes its "webpack_require.r is not a function".
If the current behavior is a bug, please provide the steps to reproduce.

clone this repo https://github.com/code1x1/webpack-require-d-is-not-a-function
run npm run start
open http://localhost:3000 in your browser
open developer console in your browser

What is the expected behavior?
optimization.runtimeChunk = true should build the bundle and the runtime.~chunk.js should contain webpack_require.d definition which is missing.

Other relevant information:
webpack version:  5.36.2
Node.js version: v12.16.3
Operating System: Debian GNU/Linux 10 (buster)
Additional tools: npm 6.14.12

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@keen%2feditorconfig - Not found
npm ERR! 404
npm ERR! 404  '<EMAIL_ADDRESS>is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/evilebottnawi/.npm/_logs/2021-05-06T12_26_03_163Z-debug.log

Can't run your example.

if i set optimization.runtimeChunk = false then the error disappears, but the build time is significantly higher.

It seems you forgot to include runtime chunk in your index.html.
Also you need<EMAIL_ADDRESS>to use multiple chunks, we are working on stable release, sorry for this

oh sorry that was private npm package i removed it.

It seems you forgot to include runtime chunk in your index.html.
the chunks are loaded correctly by the html-webpack-plugin all chunks exist but the runtime chunk doesnt contain the webpack_require.d function.

Also you need<EMAIL_ADDRESS>to use multiple chunks, we are working on stable release, sorry for this
Ok i didnt know that

in webpack v4 we don't have many optimizations, you can have three variants

one entrypoint, here you can use runtimeChunk with any values for better long term cache
multiple entrypoints on the same page, here you need set runtimeChunk: 'true', otherwise you will have multiple runtime code
multiple entrypoints on different pages, here you can use runtimeChunk with any values for better long term cache too

Don't forget you can use https://webpack.js.org/configuration/entry-context/#entry-descriptor, in most cases when you want to use multiple entry points and need runtimeChunk: 'true'you want to usedependOn`

thanks

thanks


stm32: qei to use timer low-level apis and enable time update interrupt

Tested on STM32F407VG DISCOVERY KIT

what's the goal of enabling the interrupt, if the driver doesn't use it for anything?

what's the goal of enabling the interrupt, if the driver doesn't use it for anything?

Hi @Dirbaio, It enabled user can bind their own interrupt handler on demand. In my case, I need the overflow interrupt to handle the encoder multi-rotation.

I see, thanks! in that case it should be optional, otherwise it will still fire for users who don't need it, and if they haven't set up the irq handler it will go to DefaultHandler which causes a panic.


Help to set custom style

Hi,
is there a way to style the input field just to have only the bottom border?
I don't know styled-system, I'm trying to understand if is possible, but looking to your code seems the inputLabelBorder is for all borders and is not possible to set just one.
Maybe is only my lack of knowledge on styled-system.
Thank you

@c3s4  here is example https://codesandbox.io/s/theming-datepicker-reactstyled-42pdb?fontsize=14

On the same context,
When styles have a borderRadius of 10px, like
inputLabelBorder: '1px solid rgba(226, 226, 226, 0.5)',
inputLabelBorderRadius: '10px',

Border corners are off due to components inside. Is there a way to put border-radius: 10px; on the input?


Doesn't select the first item in the completion menu when noselect is false

Checkhealth
## compe:snippet
  - INFO: snippet engine is not detected.

## compe:mapping
  - INFO: `compe#complete` is not mapped
  - OK: `compe#confirm` is mapped: (`i  <SNR>34_AutoPairsOldCRWrapper73 &@compe#confirm('<CR>')`)
  - INFO: `compe#close` is not mapped
  - OK: `compe#scroll` is mapped: (`i  <C-F>       * compe#scroll({ 'delta': +4 })`)

NOTE: even though Checkhealth shows compe#complete is not mapped, :imap <c-space> that it is mapped already.
Describe the bug
First item of the completion menu is not selected automatically even though  completeopt is "menuone,noinsert"
There was a similar issue in coc.nvim
To Reproduce

Add the default config available in README
Add keybinds in README

Actual behavior
In the completion menu, the first item is not selected

Expected behavior
When the noselect is false, the first item in the completion menu should be selected, BUT without changing the actual text in the buffer. So in below screenshot, the buffer text should be requir not require after the first item is selected

You can use preselect = 'always'. almost completion engine override completeopt. it os not an issue.

You can use preselect = 'always'. almost completion engine override completeopt. it is not an issue.

I had same issue. This solved it. Thanks!

I think it can be closed.


Collapse git and openssl build/test jobs into one

The performance of OSSNS does not give advantage to running git builds in parallel. These should be folded into a single job.

This should be fixed before git 2.32 and OpenSSL 1.1.1l and/or OpenSSL 3.0.0-beta1

OpenSSL 3.0 now builds in one job.


RegEx to validate 4CC too strict/possible characters missing

Issue
Identified by reviewing the "check" for https://github.com/MPEGGroup/FileFormatConformance/pull/83:
The "test_validate_files"-check fails because a 4CC contains a - which is not an allowed character per the RegEx ^file(?>\\.[0-9a-zA-Z]{4})*$
see https://github.com/MPEGGroup/FileFormatConformance/actions/runs/6117640706/job/16604576692 , "Validate Output", Line33
proposed solution
Quickly scrolling through mp4ra.org, the following characters are used with registered 4CCs and should be added into the RegEx:

-
+
$20
anything else?

@podborski can you verify this as well?

From ISOBMFF:

To permit ease of identification, the 32-bit compact type can be expressed as four characters from the range 0020 to 007E, inclusive, of ISO/IEC 10646 (technically identical to the Unicode standard[28]) or ISO/IEC 8859-1[34]. Each character is hence expressible in a single byte. The four individual byte values of the field are placed in order in the file. Other fields may also use this 32-bit representation, referred to as a ‘four-character code’ (4CC). The maintenance of four-character codes used in the format is defined in Annex D.

Regex should check for four characters and for the range [0x0020, 0x 007E]

Thank you, @DenizUgur and @podborski !


WIP: Introduce a new way to exclude hosts

This is a WIP.  Creating a PR to get early feedback.
Testing locally and adding test cases in progress.

https://github.com/envoyproxy/envoy/issues/9246

@mattklein123 @snowp Thanks for helping with the implementation strategy.
I took a stab at it and I would like to run some thoughts by you and seek opinions/help:

Would changing the behaviour of /healthcheck/fail endpoint to exclude hosts be considered as a breaking change for any folks that might be depending on the drain behavior for their own custom assumptions. Are you aware of any edge case use cases of the drain behavior we might be breaking?
Do you foresee any breaking behavior wrt panic routing? Draining hosts will be excluded from panic routing calculations, and i'm worried if panic routing should still consider them to prevent scenarios where membership dropping to 0.
Should a host in EXCLUDE_FROM_LB state considered healthy/unhealthy? My opinion is to treat it as unhealthy. I'm still looking for the implications of it, but seeking your opinion on it.
I'm speculating if the recovery path should include a successful healthcheck. A host which flips back to reset the exclude_from_lb state should go through a failed_active_hc and then takes usual course to become healthy. IMO it becomes easier to reason this way, but I would like to know what you feel about it.
Does envoy::data::core::v3::PASSIVE always represent a code path involving healthcheck/fail? From the code it looks so, but the name PASSIVE is probably opaque about the reason behind its occurance.

I think you'd probably want to gate this behavior on a config flag - probably on the health check config on the cluster.

2/3. Today excluded hosts aren't really healthy/unhealthy, they are completely ignored when computing the healthy/unhealthy host sets. They are only ever routed to during panic mode, where all hosts are considered regardless of health. I'd say treat these new hosts the same as how excluded hosts are treated currently - this should address both your concerns about panic calculation + panic behavior.
It might be nice to have health() return something indicating that this host is ignored, for the purpose of displaying this in the /clusters output.

Conceptually I think it would make sense to have the first HC that a host responds with that clears the immediate health check fail be treated similar to how the first health check result is. This would mean that the host either becomes health or unhealthy depending on the success of the health check.

Looks like that's the case from looking at the code, I agree that it's not super well named/documented.

I think you'd probably want to gate this behavior on a config flag - probably on the health check config on the cluster.

I could go either way on this. I really don't see any downside of having this be the way that it always works as long as it is documented, and then we can avoid new configuration. Assuming we come to agree on this, I would still have a temporary runtime kill switch that we can remove later if no one complains about the new behavior.

It might be nice to have health() return something indicating that this host is ignored, for the purpose of displaying this in the /clusters output.

This is already handled by the new enum switch for the added flag.

Today excluded hosts aren't really healthy/unhealthy, they are completely ignored when computing the healthy/unhealthy host sets.
@snowp Looks like this place considers the host Healthy by default if none of the conditions meet. We use host.health() and host.healthFlagGet in a combination to make decisions in many places(this, this, this)
I think introducing a new state here makes sense, I will look if that might break any scenarios

@jyotimahapatra I would need to analyze in more detail but you should not need to introduce any new states. The hosts will end up being excluded from panic, etc. calculations as desired. The new flag is orthogonal to health state.

@mattklein123 Thank you for your help and I do agree with your point. The question came up because we have to add the EXCLUDE_FROM_LB to one of the states here. I'm making the function return Unhealthy in this PR, and it seems to work fine. Im trying to discuss if EXCLUDE_FROM_LB should return Healthy instead (to keep it consistent with the previous exclude scenario) and its implications elsewhere where the function is used to make decisions.

It should show up in the ASSERT here: https://github.com/envoyproxy/envoy/blob/master/source/common/upstream/upstream_impl.h#L225 most likely and should not effect health state one way or the other.
/wait

/wait

closing this for now


no target overwrites source

If you run this command in Windows, it overwrites the last file in the directory you are trying to check your source against. RIP to my data
rling C:\source.txt C:/test2/*
Example:
C:\test2>dir
Volume in drive C is 465GB
Volume Serial Number is
Directory of C:\test2
06/04/2021  04:37 PM              .
06/04/2021  04:37 PM              ..
06/04/2021  04:37 PM                 0 test1.txt
06/04/2021  04:36 PM                 0 test2.txt
06/04/2021  04:36 PM                 0 test3.txt
3 File(s)              0 bytes
2 Dir(s)  91,923,488,768 bytes free
C:>rling C:\source.txt C:/test2/*
Reading "C:\source.txt"...0 bytes total in 0.0075 seconds
Counting lines...Found 0 lines in 0.0013 seconds
Optimal HashPrime is 1543
Estimated memory required: 104,869,976 (100.01Mbytes)
Processing input list... 0 unique (0 duplicate lines) in 0.0009 seconds
Occupancy is 0/1543 0.0000%, Maxdepth=0
Removing from "C:/test2/test2.txt"... 0 removed
0 total lines removed in 0.0031 seconds
Writing to "C:/test2/test1.txt"
Wrote 0 lines in 0.0009 seconds
Total runtime 0.0201 seconds

This is, in fact, how it is intended to work, and I can see no way to fix the user behavior to prevent it.  I'm happy to listen to suggestions, though.

ok, I'll bite. I can't get my head around how this could be intended.
C:\test1>dir L:\test2
Volume in drive L has no label.
Volume Serial Number is CA00
Directory of L:\test2
06/04/2021  05:43 PM              .
06/04/2021  05:43 PM              ..
06/04/2021  05:43 PM                 0 test2.log
06/04/2021  04:47 PM            95,658 test3.log
06/04/2021  04:51 PM            52,612 test4.log
06/04/2021  05:40 PM                 5 test5.log
4 File(s)        148,275 bytes
2 Dir(s)  1,260,088,832,000 bytes free
C:\test1>rling "test1.txt" l:/test2/*
Reading "test1.txt"...4 bytes total in 0.0021 seconds
Counting lines...Found 1 line in 0.0012 seconds
Optimal HashPrime is 1543
Estimated memory required: 104,869,996 (100.01Mbytes)
Processing input list... 1 unique (0 duplicate lines) in 0.0025 seconds
Occupancy is 1/1543 0.0648%, Maxdepth=0
Removing from "l:/test2/test3.log"... 0 removed
Removing from "l:/test2/test4.log"... 0 removed
Removing from "l:/test2/test5.log"... 1 removed
1 total line removed in 0.0094 seconds
Writing to "l:/test2/test2.log"
Wrote 0 lines in 0.0013 seconds
Total runtime 0.0214 seconds
C:\test1>
Thoughts:

why did it pick the first file to overwrite? How does it know which one to pick?
why is it comparing all the files in the directory and overwriting the first file? Why is it taking both actions
If this is "intended", could a parameter be added so that when the second parameter is a directory, it doesn't compare against the directory and pick a file to overwrite that already exists? This should be default behavior IMO


Update framework version to 1.0.1

First eight commits are pulled from upstream
The last commit just adds a Try in Appbuilder button
Ping @Icenium/core

:+1:  after ignore .tnsproject


Unable to migrate from angular 16 to 17!

Command
update
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
I did ng update to migrate all the dependencies of angular from 16 to 17, and the update command has also migrated all deps to 17 (I have attached a screenshot), but when I am trying to build project, it is throwing me error that This version of CLI is only compatible with Angular versions ^16.0.0,
Minimal Reproduction

Exception or Error
No response
Your Environment
_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 17.3.10
Node: 18.18.1
Package Manager: npm 9.8.1
OS: linux x64

Angular: 17.3.12
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1703.10
@angular-devkit/build-angular   17.3.10
@angular-devkit/core            17.3.10
@angular-devkit/schematics      17.3.10
@angular/cdk                    17.3.10
@angular/cli                    17.3.10
@angular/material               17.3.10
@schematics/angular             17.3.10
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.10

Anything else relevant?
No response

Likely your global version of the Angular CLI is outdated.
Can you try to use ng command directly without using npx?

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.


api

Is it possible to have another directory called weapi in the core section next to the stores directory to work with apis, to cash apis and work with them easily. It has exactly the same structure as stores. The second question is that there is more than one store for each core. Some of the logics are complicated

If you ONLY want that core using those web api's, then that package could be placed there. That is the criteria. If this is a package that will be used by all core packages, put it under foundation and follow those policy rules. If this package will only be used by that particular core package, put it under.

This directory is not supposed to be used only for connection, it is supposed to have APIs required by core, implemented like a store, for example, we will implement the api to get the flight list, the packages required for connection will be implemented in foundation

Again, the decision needs to be made based on the reusability of the package. It seems like this can live in a layer under the core package like the storage layer. Try that first and see how it feels. You can always move it later.


Allows PKs with dashes and alphanumeric digits

This way they can be hex numbers, UUIDs, slugs and so on.
Closes #77.

Coverage remained the same at 96.037% when pulling e52333b92617c266623746f4ac6195d98843ff9f on CraveFood:hex-ids into a4994eb922c252371449363daae2d5f563b56a33 on toastdriven:master.

Coverage remained the same at 96.037% when pulling e52333b92617c266623746f4ac6195d98843ff9f on CraveFood:hex-ids into a4994eb922c252371449363daae2d5f563b56a33 on toastdriven:master.

Coverage decreased (-4.7%) to 91.375% when pulling f166e4d52f13b52bb0f59d952f0f4becebcc548e on CraveFood:hex-ids into a4994eb922c252371449363daae2d5f563b56a33 on toastdriven:master.

Coverage decreased (-4.7%) to 91.375% when pulling f94c50039dd5503548a875bede15643f5ec7d79f on CraveFood:hex-ids into a4994eb922c252371449363daae2d5f563b56a33 on toastdriven:master.

Dropping django.conf.urls.patterns, which closes #79 as well.


compensate for multiple dex files for single jars

When creating the dex jar, the jar name (directory) is extracted from
the path of a predexed dependency, although a jar can contain multiple
dexes, which will be mapped to the same jar and cause a duplicate entry
error.

thanks


VSTS Service Fabric deployment task very rarely successfully completing

Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Environment

Server - VSTS
Account Name: ebiquity-na
Team project: Hyperion
Build definition: Hyperion Full Cluster
Release numbers:
Release-185, attempts 1-4
Release-186, attempt 1 (worked on attempt 2)
Release-187, attempts 1-7
Release-189
Release-190, attempts 1-2
Release-191
Release-192
Release-193, attempt 1 (worked on attempt 2)
Release-195

Agent - Hosted or Private:
Private agent, Windows server 2016 standard, agent version 2.138.6 (upgraded after release 192 or so, previously 2.134.2)

Issue Description
Using the Service Fabric deployment task built into VSTS, I've consistently seeing that the deployment works fine up to stage 3 (actual deployment) at which point it gets to "Copying application to image store..." and never moves on. If I specify a timeout for the deployment, it will eventually hit that timeout and fail. If I don't specify a timeout, it'll almost always indefinitely sit on that step (longest time running is 19 hours thus far).
I only have started observing this issue in the last week - I haven't experienced this in the last year of using VSTS and didn't change the definition in any way prior to this starting to happen. I have a support ticket open about it,<PHONE_NUMBER>12701, but we're not making much headway apart from seeing richer logs still indicating that it gets there and stops.
Halfway through the week, I attempting upgrading to the latest version of Service Fabric and it didn't make a difference. I upgraded the VSTS agent on my build server, I found similar issues raised in this repo and modified my release definition to specifically include the timeouts I already had defined in my cloud.xml file, and to enable diff releases and compressed file copy. No significant change noticed (it worked once after making the change yesterday and I haven't been able to successfully deploy since).
For the last year, a brand new deployment takes about 8 minutes to complete (if the application doesn't exist in the cluster already) and an upgrade takes about 24 minutes to complete. Looking at the service fabric cluster itself, it never registers that anything is attempting to perform an upgrade or copy files, so as far as I can tell, VSTS never actually starts the file transfer. As a result, all my logs indicate that I cancelled after half an hour or longer when I looked at the cluster, didn't see a deployment in progress and it was still pending in VSTS, so I could retry. This didn't really have an impact on the failures.
Error logs
2018-08-25T22:02:51.1333266Z ##[debug]Leaving New-DiffPackage.
2018-08-25T22:02:51.3927998Z Service fabric SDK version: <IP_ADDRESS>94.
2018-08-25T22:04:20.2931505Z ##[debug]Join-Path "C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code" "ServiceFabricServiceModel.xsd"
2018-08-25T22:04:20.3039173Z ##[debug]C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code\ServiceFabricServiceModel.xsd
2018-08-25T22:04:20.3069561Z ##[debug]Length: 94
2018-08-25T22:04:20.3099711Z ##[debug]
2018-08-25T22:04:20.3146099Z ##[debug]Test-Path "C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code\ServiceFabricServiceModel.xsd"
2018-08-25T22:04:20.3619249Z ##[debug]True
2018-08-25T22:04:20.3651149Z ##[debug]
2018-08-25T22:05:01.5760455Z Copying application to image store...
...
And then after half an hour or long of no progress being made
...
2018-08-25T22:35:15.7445675Z ##[debug]Re-evaluate condition on job cancellation for step: 'Deploy Service Fabric Application'.
2018-08-25T22:35:26.2119865Z ##[error]The operation was canceled.
2018-08-25T22:35:26.2216621Z ##[debug]System.OperationCanceledException: The operation was canceled.
at System.Threading.CancellationToken.ThrowOperationCanceledException()
at Microsoft.VisualStudio.Services.Agent.Util.ProcessInvoker.d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.Agent.ProcessInvokerWrapper.d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.Agent.Worker.Handlers.DefaultStepHost.d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.Agent.Worker.Handlers.PowerShell3Handler.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.Agent.Worker.TaskRunner.d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.Agent.Worker.StepsRunner.d__1.MoveNext()
2018-08-25T22:35:26.2225561Z ##[section]Finishing: Deploy Service Fabric Application
All my error logs resemble this - I've submitted all the debug errors to the support ticket<PHONE_NUMBER>12701 and would be happy to email them to someone in particular if you want a copy.
As a result, of the 20ish attempts I've made to update my cluster, only two have been successful. This is a major blocker for me as I cannot reliably deploy anything via VSTS's continuous integration into my cluster and haven't now for over a week. I appreciate you taking a look into this.

Following up on this, I'm able to deploy without issue from my development machine within Visual Studio 2017 Enterprise.
I've toggled just about all the options related to this in the release task - I've tried enabling/disabling compression, diff releases, setting the timeout values, not setting them and using the defaults, and manually setting the MaxMessageSize fabric setting on the service fabric instance to 10 MB (per the guidance at https://github.com/Azure/service-fabric-issues/issues/1170).
Looking at the VSTS agent logs on my build machine, it appears that VSTS just stops interacting with the SF instance. In the deployment step, I see the following:
[2018-08-25 00:09:32Z INFO ProcessInvoker] Starting process:
[2018-08-25 00:09:32Z INFO ProcessInvoker]   File name: 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe'
[2018-08-25 00:09:32Z INFO ProcessInvoker]   Arguments: '-NoLogo -Sta -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". ([scriptblock]::Create('if (!$PSHOME) { $null = Get-Item -LiteralPath ''variable:PSHOME'' } else { Import-Module -Name ([System.IO.Path]::Combine($PSHOME, ''Modules\Microsoft.PowerShell.Management\Microsoft.PowerShell.Management.psd1'')) ; Import-Module -Name ([System.IO.Path]::Combine($PSHOME, ''Modules\Microsoft.PowerShell.Utility\Microsoft.PowerShell.Utility.psd1'')) }')) 2>&1 | ForEach-Object { Write-Verbose $_.Exception.Message -Verbose } ; Import-Module -Name 'C:\vsts-agent-win-x64-2.134.2_work_tasks\ServiceFabricDeploy_c6650aa0-185b-11e6-a47d-df93e7a34c64\1.7.21\ps_modules\VstsTaskSdk\VstsTaskSdk.psd1' -ArgumentList @{ NonInteractive = $true } -ErrorAction Stop ; $VerbosePreference = 'Continue' ; $DebugPreference = 'Continue' ; Invoke-VstsTaskScript -ScriptBlock ([scriptblock]::Create('. ''C:\vsts-agent-win-x64-2.134.2_work_tasks\ServiceFabricDeploy_c6650aa0-185b-11e6-a47d-df93e7a34c64\1.7.21\deploy.ps1'''))"'
[2018-08-25 00:09:32Z INFO ProcessInvoker]   Working directory: 'C:\vsts-agent-win-x64-2.134.2_work_tasks\ServiceFabricDeploy_c6650aa0-185b-11e6-a47d-df93e7a34c64\1.7.21'
[2018-08-25 00:09:32Z INFO ProcessInvoker]   Require exit code zero: 'True'
[2018-08-25 00:09:32Z INFO ProcessInvoker]   Encoding web name:  ; code page: ''
[2018-08-25 00:09:32Z INFO ProcessInvoker]   Force kill process on cancellation: 'False'
[2018-08-25 00:09:32Z INFO ProcessInvoker]   Lines to send through STDIN: '0'
[2018-08-25 00:09:33Z INFO ProcessInvoker] Process started with process id 1120, waiting for process exit.
[2018-08-25 00:09:33Z INFO JobServerQueue] Try to append 6 batches web console lines for record '1e912ee4-6793-4bec-ba67-643980ce67ad', success rate: 6/6.
[2018-08-25 00:09:34Z INFO JobServerQueue] Try to append 6 batches web console lines for record '1e912ee4-6793-4bec-ba67-643980ce67ad', success rate: 6/6.
[2018-08-25 00:09:35Z INFO JobServerQueue] Try to append 6 batches web console lines for record '1e912ee4-6793-4bec-ba67-643980ce67ad', success rate: 6/6.
[2018-08-25 00:09:36Z INFO JobServerQueue] Try to append 6 batches web console lines for record '1e912ee4-6793-4bec-ba67-643980ce67ad', success rate: 6/6.
[2018-08-25 00:09:37Z INFO JobServerQueue] Try to append 6 batches web console lines for record '1e912ee4-6793-4bec-ba67-643980ce67ad', success rate: 6/6.
[2018-08-25 00:09:38Z INFO JobServerQueue] Try to append 6 batches web console lines for record '1e912ee4-6793-4bec-ba67-643980ce67ad', success rate: 6/6.
[2018-08-25 00:09:38Z INFO JobServerQueue] Try to append 6 batches web console lines for record '1e912ee4-6793-4bec-ba67-643980ce67ad', success rate: 6/6.
[2018-08-25 00:09:39Z INFO JobServerQueue] Try to upload 2 log files or attachments, success rate: 2/2.
[2018-08-25 00:09:39Z INFO JobServerQueue] Try to append 6 batches web console lines for record '1e912ee4-6793-4bec-ba67-643980ce67ad', success rate: 6/6.
[2018-08-25 00:09:40Z INFO JobServerQueue] Try to append 5 batches web console lines for record '1e912ee4-6793-4bec-ba67-643980ce67ad', success rate: 5/5.
[2018-08-25 00:09:40Z INFO JobServerQueue] Try to append 1 batches web console lines for record '9aa8df33-d57c-4478-be71-6d27f1eec411', success rate: 1/1.
[2018-08-25 00:09:41Z INFO JobServerQueue] Try to append 2 batches web console lines for record '9aa8df33-d57c-4478-be71-6d27f1eec411', success rate: 2/2.
[2018-08-25 00:09:41Z INFO JobServerQueue] Try to upload 1 log files or attachments, success rate: 1/1.
[2018-08-25 00:09:42Z INFO JobServerQueue] Try to append 1 batches web console lines for record '9aa8df33-d57c-4478-be71-6d27f1eec411', success rate: 1/1.
[2018-08-25 00:09:43Z INFO JobServerQueue] Try to append 1 batches web console lines for record '9aa8df33-d57c-4478-be71-6d27f1eec411', success rate: 1/1.
[2018-08-25 00:10:08Z INFO JobServerQueue] Try to append 1 batches web console lines for record '9aa8df33-d57c-4478-be71-6d27f1eec411', success rate: 1/1.
[2018-08-25 00:10:54Z INFO JobServerQueue] Try to append 1 batches web console lines for record '9aa8df33-d57c-4478-be71-6d27f1eec411', success rate: 1/1.
[2018-08-25 00:10:55Z INFO JobServerQueue] Try to append 1 batches web console lines for record '9aa8df33-d57c-4478-be71-6d27f1eec411', success rate: 1/1.
[2018-08-25 00:11:20Z INFO JobServerQueue] Try to append 1 batches web console lines for record '9aa8df33-d57c-4478-be71-6d27f1eec411', success rate: 1/1.
[2018-08-25 00:12:07Z INFO JobServerQueue] Try to append 1 batches web console lines for record '9aa8df33-d57c-4478-be71-6d27f1eec411', success rate: 1/1.
[2018-08-25 03:27:56Z INFO Worker] Cancellation/Shutdown message received.
I cancelled after 3 hours when I noticed that the cluster wasn't registering that an upgrade or file transfer was in progress. Typically though, this would completely deploy within 25 minutes or so, so taking 3 hours was a sign unto itself.

@bishal-pdMSFT Don't know what to tell you - it's been working great deploying from VSTS for over a year and this cluster instance hasn't given me a problem for the last month it's been around either. All of a sudden last week, I can't deploy successfully but 5% of the time, if that.
Works fine if I deploy from my dev machine itself.
I found several issues in the Service Fabric repo that match the issue I'm having, so perhaps it's something more to do with the large application package I've got than VSTS itself, but so far I'm hitting a brick wall on resolving it.

@bishal-pdMSFT I do have such debug-level logs available, but I'd feel better about sharing them (or others) with you directly rather than posting them in this public context and having to redact each one.
I've attached one of the "Deploy Service Fabric Application" step both when it works and when it doesn't.
notworking.txt
working.txt

@oanapl To address the possible issues you listed at https://github.com/Azure/service-fabric-issues/issues/1170:

The cluster is properly set up to my knowledge. I can deploy to it fine from my local machine, two weeks, I could deploy without issue from my build server via VSTS (and have been for the last year) and the application runs fine once it's there.

@WhitWaldo one thing I noticed from task logs is that SF SDK version is different for the two runs. Successful one ran with SDK version 3.1.274.9494 and failed one ran with SDK <IP_ADDRESS>94. These twi might have run on different agents or SF SDK might have been re-installed on agent.
The task versions are same and hence there is no change in task behavior.

@WhitWaldo , the fastest way to make progress is to open a support ticket. We will need Service Fabric traces from the cluster and the client machine (where the VSTS agent is running). If you don't know how to collect them, you will get instructions as part of the ticket processing.
If you have the traces, you can also send them to me directly at oanapl at microsoft.com

@WhitWaldo , Hope you are taking up this with SF team. Can we close this issue?

@rgovardhms Yes, I'm currently engaged in a support ticket about this now. This issue can be closed here.

What was the solution here? We've been struggleing with this for months :(

Can you provide more details on the failure you are seeing and consider opening a new issue?

@tudorsibiu90 Ultimately we concluded it was an occasional failure of my network connection. I resolved it by switching from an onsite build server to one hosted in Azure.


IMUSensor returns Angular Acceleration

Describe the bug
An IMU measures linear acceleration, I believe holodeck code is setup to return angular acceleration instead (wrong). From IMUSensor.cpp:
void UIMUSensor::CalculateAccelerationVector(float DeltaTime) {
	VelocityThen = VelocityNow;
	VelocityNow = Parent->GetPhysicsAngularVelocityInDegrees();

	RotationNow = this->GetAttachParent()->GetComponentRotation();

	LinearAccelerationVector = VelocityNow - VelocityThen;
	LinearAccelerationVector /= DeltaTime;

	LinearAccelerationVector += FVector(0.0, 0.0, -WorldGravity);

	LinearAccelerationVector = RotationNow.UnrotateVector(LinearAccelerationVector); //changes world axis to local axis
}

This issue is being worked on BYU-PCCL/holodeck-engine#219


Add support for --device mps option for MacOS

Currently, the --device flag only supports two options: cpu and cuda. However, cuda is not available on MacOS, leaving cpu as the only option, which is significantly slower.
MacOS users can leverage the Metal Performance Shaders (MPS) backend for GPU acceleration, which greatly speeds up processing.
Please add support for --device mps to enable GPU acceleration on MacOS.
As a temporary solution, I am manually hardcoding the value in the environment folder, but this is a dirty hack and not maintainable.
Adding mps support natively would improve usability and performance for MacOS users.

Can you share your hack? I'd like to try it out.

https://github.com/Softcatala/whisper-ctranslate2/blob/1a4b8ee8dfd2999f77628b9e39dd5ddf4cf7fe82/src/whisper_ctranslate2/diarization.py#L38
Here I changed self.device to mps.


Branch not covered in code coverage

I am getting “branch not covered” in code coverage report for constructor() in my angular project:
I am using:
Jest: 25.5.4
ts-jest: 25.5.1
Any suggestions?

Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions. You'll find more on Jest docs help page. Thank you :)

Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions. You'll find more on Jest docs help page. Thank you :)


Resolve the default authentication service type based on environment

I expect this to fail building, as systemtest clients will not be authenticated. I'm pondering if the ideal way to do this is to skip deploying keycloak for the systemtests until we have systemtest support for creating the roles etc.


v2 cluster management has cluster greyed out even after they are active

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Spin up rancher on the latest master-head
Create a cluster infrastructure provider/import/custom form cluster explorer --> cluster management
On the tope left corner, click on the three vertical lines next to local and under local, all the clusters are greyed out even when they are active

Result:
Clusters should not be greyed out and users should be able to access as for local cluster
Other details that may be helpful:

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
master-90dc82bfc7ff26f3b3f8922595d491cbf8c9d3dd-head
Installation option (single install/HA): Single

still seeing this on master-head (91a6f51)

Verified on master-360edaec8f7e236611fdd30e6798874bac267d5b-head

Spin up rancher on the version of master-head mentioned above.
Create a custom cluster and on an AWS node run the registration command with all roles enabled.
Once the node gets active, from the explore cluster --> click on the cluster created above and is redirected to the cluster dashboard
Create a DO cluster 1 node all roles node driver, once it gets active, repeated step3


confusion regarding parameters used in Excel sheet

Is there any explanation of how the benchmarking is done? so as to know the exact parameters which are focussed and then can be a better insight. I am very much interested to know how deepbench is working and would also want to know the P and Q parameters in the convolution results.

P and Q are calculated using the input parameters to determine the height and width of the output tensor. These are useful in calculating the computational FLOPS. This paper describes how P and Q are calculated: https://arxiv.org/pdf/1410.0759v3.pdf
For convolutions, the input parameters are:
W,H: width, height of input
C: channels in input
N: Batch size
K:Number of filters
R,S: Width, height of the filter
pad: padding height and width
stride: vertical and horizontal stride
All the other columns are either observed through the benchmark or calculated. Hope this helps. Let me know if you have any other questions.

This is surely making more sense now. Thanks.
Is there any way i could proceed with Batch size = 1?
I guess changing the cuda code for the same?

Yes, changing N in the tuple will allow you to run the benchmark for batch size of 1.

Thanks a lot @sharannarang. Bdw are there any more benchmarks for convolutions on the Intel hardware?

@hit101 - do you mean other libraries for convolutions on Intel HW ?

@dmudiger No i mean are there more configurations for NHCW for which convolution was tried on Intel HW?

@dmudiger :- Are there any merged results available apart from that mentioned in the Excel file?

@hit1001 , The excel sheet lists all the results available for different kernels. We don't have any other results besides those.


Taking ownership as agreed with Stephen de Vries.

great stuff, @zeroXten go for it :)
Let us know if you need any help


[Welcome to Foundation 6] Foundation Documentation Links Broken

Expected Behavior

https://get.foundation/sites/docs/xy-grid
...
Current Behavior

Links are absolute paths. They are linking from a root expectation and should be /sites/docs/[LINKNAME]
https://get.foundation/xy-grid
...
Possible Solution

Make links either relative or add /sites/docs/[LINKNAME]
...
Test Case and/or Steps to Reproduce (for bugs)

Test Case:

How to reproduce:

Use the left sidebar https://get.foundation/sites/docs/. All links are broken 404s. Should be an easy fix.

Context

...
Your Environment

Foundation version(s) used:
Browser(s) name and version(s):
Device, Operating System and version:
Link to your project:

Checklist

[ ] I have read and follow the CONTRIBUTING.md document.
[ ] This is a bug report or a feature request.
[ ] There are no other issues similar to this one.
[ ] The issue title and template are correctly filled.

dup #12578


Continuous Deployment Pipeline for Website

Build and implement a Dagger function to automate the process of building and deploying the Rawkode Academy website to Cloudflare upon every merge to the main branch.
The task includes:

Setting up a Dagger pipeline that triggers on merges to the main branch.
Configuring the build process for the website within the Dagger function.
Integrating deployment to Cloudflare as the final step in the pipeline.
Ensuring that the entire process is automated and reliable, with appropriate error handling and notifications.

I can take a look


Missingmaps

Add links to Missing Maps

Thanks, @dalekunce!!

woot, thanks, sorry for the typo. Loving OSMcha the more I get into it.

Woohoo, glad to see this! 🎉


Improved file logging verbosity

Added a --file-log-verbosity={0,1} option to allow users to change levels of verbosity in src/_pytest/logging.py

verbosity=0 is the default behavior
verbosity=1 shows the location of each test in the beginning of each session

LGTM


SNOW-1865997: Use docstrings folder for DatetimeIndex methods and properties

Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
<!---
In this section, please add a Snowflake Jira issue number.
<p>Note that if a corresponding GitHub issue exists, you should still include
the Snowflake Jira issue number. For example, for GitHub issue
https://github.com/snowflakedb/snowpark-python/issues/1400, you should
add "SNOW-1335071" here.
--->
Fixes SNOW-1865997

Fill out the following pre-review checklist:

[ ] I am adding a new automated test(s) to verify correctness of my new code

[ ] If this test skips Local Testing mode, I'm requesting review from @snowflakedb/local-testing

[ ] I am adding new logging messages
[ ] I am adding a new telemetry message
[ ] I am adding new credentials
[ ] I am adding a new dependency
[ ] If this is a new feature/behavior, I'm adding the Local Testing parity changes.
[ ] I acknowledge that I have ensured my changes to be thread-safe. Follow the link for more information: Thread-safe Developer Guidelines

Please describe how your code solves the related issue.
Use docstrings folder for DatetimeIndex methods and properties. Docstrings for TimedeltaIndex will be treated similarly in a follow-up PR

I verified that the generated docs before and after the change are the same. Also verified that help(pd.DatatimeIndex.<method/property>) work as expected and its output look the same for the few methods/properties that I tested.


Add eager mode support of TED based models

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

It doesn't improve the test time of policies but brings a lot of difficulty to the TensorFlow models.


ResolveField 중복 호출 수정

Describe the problem and solution
admin 서버 내의 problem.service.ts 및 problem.resolver.ts 중 ResolveField 및 prisma include로 인한 DB 중복호출 건을 수정합니다.
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines
[X] Check that there isn't already an issue

Changed the connected Notion task status to not-started
 TAS-623 ResolveField 중복 호출 수정


[Navigation] Sometimes crash occurs while hiding the dialog

Description
I see some crash reports in Firebase. It seems there is a state when the anchors are not calculated, and we navigate away from the dialog.
Fatal Exception: java.lang.IllegalArgumentException: The target value must have an associated anchor.
       at androidx.compose.material.SwipeableState$snapTo$$inlined$collect$1.emit(Collect.kt:136)
       at kotlinx.coroutines.flow.FlowKt__LimitKt.emitAbort$FlowKt__LimitKt(Limit.kt:73)
       at kotlinx.coroutines.flow.FlowKt__LimitKt.access$emitAbort$FlowKt__LimitKt(Limit.kt:1)
       at kotlinx.coroutines.flow.FlowKt__LimitKt$take$lambda-7$$inlined$collect$1.emit(Collect.kt:138)
       at androidx.compose.material.SwipeableState$special$$inlined$filter$1$2.emit(Collect.kt:137)
       at kotlinx.coroutines.flow.internal.SafeCollectorKt$emitFun$1.invoke(SafeCollector.kt:15)
       at kotlinx.coroutines.flow.internal.SafeCollector.emit(SafeCollector.kt:77)
       at kotlinx.coroutines.flow.internal.SafeCollector.emit(SafeCollector.kt:59)
       at androidx.compose.runtime.SnapshotStateKt$snapshotFlow$1.invokeSuspend(SnapshotState.kt:891)
       at androidx.compose.runtime.SnapshotStateKt$snapshotFlow$1.invoke(SnapshotState.kt:2)
       at kotlinx.coroutines.flow.SafeFlow.collectSafely(SafeFlow.java:61)
       at kotlinx.coroutines.flow.AbstractFlow.collect(Flow.kt:212)
       at androidx.compose.material.SwipeableState$special$$inlined$filter$1.collect(SafeCollector.common.kt:114)
       at kotlinx.coroutines.flow.FlowKt__LimitKt$take$$inlined$unsafeFlow$1.collect(SafeCollector.common.kt:116)
       at androidx.compose.material.SwipeableState.snapTo(SwipeableState.java:943)
       at com.google.accompanist.navigation.material.SheetContentHostKt.internalHide(SheetContentHostKt.java:188)
       at com.google.accompanist.navigation.material.SheetContentHostKt.access$internalHide(SheetContentHostKt.java:1)
       at com.google.accompanist.navigation.material.SheetContentHostKt$SheetContentHost$2$2$1.invokeSuspend(SheetContentHost.kt:145)
       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
       at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:81)
       at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch(AndroidUiDispatcher.android.kt:41)
       at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.run(AndroidUiDispatcher.android.kt:57)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loopOnce(Looper.java:201)
       at android.os.Looper.loop(Looper.java:288)
       at android.app.ActivityThread.main(ActivityThread.java:7838)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)

Steps to reproduce
I could not create a reproducing code, yet.
Expected behavior
This code is already wrapped in a try block, maybe it should catch all exceptions just to be sure.

@WonderCsabo Thanks for the report. Do you have the exception that's thrown by chance?

@jossiwolf sorry for the late response. I edited the stacktrace!

I just realized this might be a duplicate, we also discussed it here: https://github.com/google/accompanist/issues/910#issuecomment-1041872681.

This issue is still happening very frequently according to our Crashlytics reports.

Still happenning.

This is still happening.

This is still happening.

This is still happening.

@jossiwolf can you reopen this, please?

Upstream issue for the root cause: https://issuetracker.google.com/issues/167966118
We're working on it but it will still take some time to address.

v0.28.1 addresses this issue. Please let us know if you can still reproduce it with this version.

Hey @jossiwolf - it seems that v0.28.1 has not been released yet - wanted to ask if this is expected

Apologies, it's v0.29.0-alpha.


Improved background handling.

It is possible to reset one's background
and to combine a special color and a
background.

Looks good! Thanks Ark


Do not call auction::slash contract when no validator was slashed.

This PR:

removes run_auction boolean from the StepRequest. It was unnecessary as we always run it (it was always set to true as well).
does not call Auction::slash endpoint if there are no validators to slash.

Closes https://github.com/casper-network/casper-node/issues/2309

bors merge


Can't use nullable boolean fields

Describe the bug

Define boolean field and mark it as nullable (default type will be tinyint in mysql)
Assign false to the field
flush em and look to database

The field is stored as 'null' instead of 0.
Versions
3.0.0-rc.2

Fixed in 3.0.0-rc.3.

I still have this issue in 4.5.9


[Feature Request] Avoiding Content Security Policy (CSP) issues

Is your feature request related to a problem? Please describe.
We are unable to deploy the Docker image of Temporal Web UI due to our restrictive Content Security Policy disallowing the use of eval.
Describe the solution you'd like
According to the documentation of Vue.js, it should be possible to avoid this being an issue by producing a runtime-only build. Please see CSP environments. My knowledge of Vue.js is limited, but it would be ideal if we didn't have to resort to introducing an unsafe Content Security Policy for the sake of running the Temporal Web UI Docker image.
Additional context
The following warnings are presented in the browser (along with a blank screen):
vue.esm.js:628 [Vue warn]: It seems you are using the standalone build of Vue.js in an environment with Content Security Policy that prohibits unsafe-eval. The template compiler cannot work in this environment. Consider relaxing the policy to allow unsafe-eval or pre-compiling your templates into render functions.

vue.esm.js:628 [Vue warn]: Failed to generate render function:

EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' 'unsafe-inline'".
 in

with(this){return _c('App')}

(found in <Root>)

is this something you are absolutely blocked on? ideally would like to resolve this with the next version of UI http://github.com/temporalio/ui

@tszucs-stripe there is no timeline for the UI v2
I'll take a look into this issue in the current UI


Welcome page does not have sufficient contrast

I think you should review accessibility of the welcome page. Light green text on white background is very hard to read for some users. It's also the case for all the doc at https://v3.nuxtjs.org

I think also a new green would be better.
I don't know why NuxtJS use it's own green and not the official Vue green?.
Nuxt logo:

light green: #80EEC0
dark green: #00DC82

Vue logo: #42b883
With Vue logo color and nuxt logo dark green:

Source code:
<svg fill="none" height="124" width="124" xmlns="http://www.w3.org/2000/svg"><path clip-rule="evenodd" d="m55.75 27.155c-3.222-5.54-11.278-5.54-14.5 0l-35.116 60.38c-3.222 5.54.806 12.465 7.25 12.465h27.413c-2.753-2.407-3.773-6.57-1.69-10.142l26.597-45.588z" fill="#00DC82" fill-rule="evenodd"/><path d="m78 40.4c2.667-4.533 9.333-4.533 12 0l29.06 49.4c2.667 4.533-.666 10.199-5.999 10.199h-58.123c-5.333 0-8.666-5.666-6-10.199z" fill="#42b883"/></svg>

Using a darker green could solve this a11y issue.

This pull request aims to solve these issues: https://github.com/nuxt/ui/pull/62


Agent not using the tool

i have a tool for the vector store.
The agent's action is the correct tool for the vector store but it is not actually using that tool to find the answer.

@dosu-bot sure, i am using RetrievalQA chain as a tool to the zeroshot agent. The agent is picking the tool correctly as the action but not utilizing it


Display upcoming COVID status changes on the results page

Trello: https://trello.com/c/7sslimxM
What's changed?
Displays a warning on the Check Travel During Coronavirus results page if the COVID status of a country is changing.
Expected changes
Rendered version

Before
After

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

Replaced by #5731


Automate dependencies for Linux and Windows

When building the MAVLink test suite setup fails on Windows and Linux because there are missing dependencies. As discussed  here it would be better if the SDK is able to install its own dependencies.
@julianoes Just a reminder :-)

I understand the issue for the MAVLink test suite, but I kind of disagree on the solution here. I would say that the MAVLink test suite should find_package(DronecodeSDK REQUIRED) instead of building it itself.
This said, I'm working on moving the dependencies out of the SDK CMakeLists and having some kind of helper to build them if necessary (but relying on find_package everywhere). And at the same time my goal is to go towards depending on the SDK with find_package(DronecodeSDK REQUIRED), which would solve this issue.

@JonasVautherin I don't mind where or how the issue is solved, but it has to be solved in either the test suite or here :-). Work it out with @julianoes and let me know :-)
In the short term, this could just be addition to the readme in the test suite.


Np 94/adding drivers configuration

@kgrgreer @jlhughes
Please take a look.
Thank you
Ticket:
https://nanopay.atlassian.net/browse/NP-94

fixing it


Unused variables - option to turn off for public variables

As it can't really be guaranteed they're not used from some other package.

yea, should add it
default should be report error, as public variables are not good, https://github.com/SAP/styleguides/blob/master/clean-abap/CleanABAP.md#members-private-by-default-protected-only-if-needed

before this can be implemented, a bit more infrastructure is required to be able to determine what is public vars

https://github.com/abaplint/abaplint/issues/2091


AdminLTE on Laravel. Switching default Laravel Boilerplate/Scaffolding to adminLTE with adminlte-laravel package

Hi all,
First of all congratulations @almasaeed2010 for this awesome template. Very impressive!
At:
https://github.com/acacha/adminlte-laravel
You can find my contribution, a Laravel package to install adminLTE on Laravel overwriting default auth  Laravel pages, home page and error pages in few steps:
First install Laravel (http://laravel.com/docs/5.0/installation) and then Create a new Laravel project:

 $ laravel new laravel-with-admin-lte
 $ cd laravel-with-admin-lte

Add admint-lte Laravel package with:

 $ composer require "acacha/admin-lte-template-laravel:0.*"

Register ServiceProvider editing config/app.php file and adding to providers array:

 // AdminLTE template provider
 'Acacha\AdminLTETemplateLaravel\app\Providers\AdminLTETemplateServiceProvider',

Publish files with:

 $ php artisan vendor:publish --force --provider="Acacha\AdminLTETemplateLaravel\app\Providers\AdminLTETemplateServiceProvider"

Kind regards,
Sergi Tur Badenas

This sounds interesting. I hope some us benefit of it. Thanks for sharing!


LFS-60: Turn off npm install when using -Pquick

When running -Pquick, npm install is no longer run. This may cause issues if someone adds npm dependencies but tries to use -Pquick.

On further testing, it seems like this also restricts -Pquick to when you're installing particular modules. I'm investigating it further now.

Should be working as expected now. I've moved the functionality over to mvn install -Pskip-npm on Marta's advice.

Given #19, npm is no longer used, yarn is. So, replace all npm references with yarn.


having a property of type IReadOnlyDictionary<String!, Object> crashes graphql

Product
Hot Chocolate
Version
13.8.1
Link to minimal reproduction
xxx
Steps to reproduce
I have a Type that has a property of Type IReadOnlyDictionary<String!, Object> and I get This error:
Unable to resolve type reference IReadOnlyDictionary<String!, Object> (Output). (HotChocolate.Types.InterfaceType<xxx>)
I Allready tried
.AddInterfaceType<IReadOnlyDictionary<string, object?>>()
.BindRuntimeType<IReadOnlyDictionary<string, object>, AnyType>()
.BindRuntimeType<IReadOnlyDictionary<string, object?>, AnyType>()
but it just keeps crashing
What is expected?
it just works
What is actually happening?
it makes me sad
Relevant log output
No response
Additional context
No response

.BindRuntimeType<IReadOnlyDictionary<string, object>, AnyType>() seems to be the culprit removing it fixed the query execution


Support type uuid for Postgresql Database

At the moment track tables on Postgresql DB fail if the table has a uuid defined column?
Would be great if you can add the uuid type for the schema creation to make track possible out of the box.
For now, I've followed your advice and added the table via mission control without any filed definition, so it was added schemaless.

@sharadregoti this should be a fairly straightforward process.

Done


Use CameraController in 3d_gizmos example

Objective

Make it easier to see how the 3d gizmos work by letting the viewer control the camera.
This was suggested by someone in Discord or in a GitHub comment but I couldn't find the original source. I thought it was a good idea too so decided to make a PR.

Solution

Use the camera controller helper instead of the automatic rotation system.

Testing
cargo run --example 3d_gizmos

And confirmed the freecam controls work.
Screenshots
Initial view:

Above:

Below:

@alice-i-cecile  This broke the 3d_gizmos example, which relies on many of the same key bindings to demonstrate it's functionality.


Update main.tf

Description
Fixes #000.

TODOs
Read the Gruntwork contribution guidelines.

[x] Update the docs.
[x] Run the relevant tests successfully, including pre-commit checks.
[x] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
[x] Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added / Removed / Updated [X].
Migration Guide

Not sure how much value this PR adds


On example pages, redirect to https

Chrome no longer supports getUserMedia on pages served over http, so use a simple javascript page to force over to https for the example pages.

I was going to PR this, but couldn't figure out how you were managing GH pages branch - should I modify the examples directly, or do you have a script to update the GH pages branch from dev?

Thanks for bringing this to my attention! I wasn't aware that Chrome had disabled getUserMedia over http already. Do you happen to know if Firefox, Safari or IE is planning to do the same thing?
I don't have a script to update gh-pages, so modifying the examples directly is fine. A bit unsure whether to enforce https via javascript in the examples though, as it won't work in most cases when serving from localhost. Maybe add an extra case for localhost? I'll update the links in the readme to point to https.

@auduno Serving from localhost is actually fine over http - it's the only exception to the HTTPS rule. So there are two options:

Have a code exclusion for localhost to prevent the https redirect, or
Add simple instructions for serving localhost over https.

I can help with either. My preferred method is 2, and I have a couple different very simple methods for this if you're interested.

After some thought, I think we need to add a script to redirect to https as you suggested. I think it's fine to add an exclusion for localhost, i.e.
if (window.location.hostname !== "localhost" && window.location.protocol !== "https:"){
  window.location.protocol = "https";
}

but which methods do you suggest for serving localhost over https?

 Something like this - https://github.com/xdumaine/stupid-simple-node-server/blob/master/index.js


Crash on Samsung Galaxy tablet, Android 9.0

Reproduced only on Samsung Galaxy tablet S5e 10.5 SM-T725 with Android 9.0
We use 1.8.0 library version
After call TransitionManager.endTransitions() we have exception:
file: Transition.java,
method: void forceToEnd(@Nullable ViewGroup sceneRoot) {
line: AnimationInfo info = runningAnimators.valueAt(i);
exception: java.lang.ArrayIndexOutOfBoundsException: length=0; index=19

Hi!
The current version of Transitions-Everywhere is based on androidx.transition library and this bug was fixed there as part of the version 1.1.0-rc02 here: https://android.googlesource.com/platform/frameworks/support/+/8b1665dd70b2c3bda327d44d8228b60f0dd3c399
Unfortunately I am not going to maintain 1.8.0 version of Transitions-Everywhere so I would suggest you to migrate to the newest version (please note that it could mean you need to migrate from support libraries to AndroidX if you didn't already)


dependencies

What is the math library used? My build fails like:
./atmosphere/reference/definitions.h:53:10: fatal error: math/angle.h: No such file or directory
#include "math/angle.h"

These are git submodules. You need to do "git submodule init" and "git submodule update" (in the root directory) to get them.

ok thanks!


python3Packages.accelerate: disable problematic tests on aarch64-linux

Description of changes
https://hydra.nixos.org/build/259069358
ZHF #309482
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build python311Packages.accelerate

Quite odd. It seems like the build sandbox does not mount the required sysfs bits, and psutil takes a different path for resolving core count on arm vs x86.


Fix: Upload nested json file to s3.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Just the first object key is uploaded to the s3 bucket.
Describe the solution you'd like
Write a file with a nested JSON inside the s3 bucket
Additional context
The for inside index.js should be fixed.

The last commit 07b604c fixes this issue because we were created a new function called upload_file, this file already includes several json objects.

The last commit 07b604c fixes this issue because we were created a new function called upload_file, this file already includes several json objects.


syntax: Add support for JavaScript template strings

Template literals are part of JavaScript since version ES2015.
They add a new way of defining multi-line strings, for example:
  `string text`

  `line 1
   line 2`

  `string text ${expression} string text`

This patch adds syntax support for this new standard, which is currently
not handled by Vim and results in bad highlight coloring.

Am 2016-09-07 14:35, schrieb Adrien Vergé:

Template literals are part of JavaScript since version ES2015 [1].
They add a new way of defining multi-line strings, for example:
string text
line 1    line 2
string text ${expression} string text
This patch adds syntax support for this new standard, which is
currently
not handled by Vim and results in bad highlight coloring.

As said in the neovim bugtracker, this should be directed to the syntax
file
maintainer, as seen on the top of the file.
However, the current syntax file maintainer is known to be unresponsive,
so perhaps it would be good if someone volunteered to become a new
maintainer.
Also, how does this relate to #1022, which does also does seem to
include template literalls?
CC @daingun for comments.
Thanks,
Christian

It would be great to have string template support in Vim.

In my pull request #1022 I also added a basic template literals support.
I do not think our changes will be considered since the maintainer is no more active. So I had to install pangloss/vim-javascript plugin to have proper javascript support in vim.
I may suggest the vim developers to switch maintainer, maybe ask to the people of vim-javascript if they can provide a basic syntax file.

Well, if anybody wants to volunteer, just go ahead change the header of the file and add yourself as new maintainer, move the current maintainer to "Previous Maintainer" (perhaps make a note of your repository and mention the license) and send the complete file to Bram for inclusion with Vim.
Also, I'll ping the pangloss/javascript guys, if they want to contribute.

@chrisbra - I'd be interested in volunteering, but I need to know more about what's involved. Can you give me some pointers/background? Thanks

There is no real formal process and becoming a maintainer is usually not much work. Basically, you should react to bugreports and perhaps react to user questions. Bugs should be fixed in your master version. Once in a while (when you think your version is stable enough or a new major Vim release is coming up) you would send an updated syntax file to Bram for inclusion with Vim.
Of course it helps, if you actually use javascript (and Vim of course!) so you notice any problems yourself or you can include newly added keywords to the language file.
First it would be good to look at the existing javascript bugs here in the issue tracker and PR, check whether they are still valid and try to come up with a consolidated file, that fixes those issues.
Then you would make those changes (e.g. add yourself as the maintainer to the file, moving the current Maintainer line to a Previous Maintainer, make a note of your master repository and perhaps mention the license) and send the file to Bram for inclusion and finally ping me here or at the relevant issues, if they can be closed.
Once this is done, the usual work is just minor, try to fix reported bugs, react to questions would be nice and once in a while adopt the syntax file to changes in Vim (this happens only very seldom) and that's basically it. The work actually depends on how many people use it and report actually problems.

I would be interested in maintaining this.
Are there ways of adding tests for syntax files and is there any documentation on the correct way to contribute to vim?
Thanks!

It is not that hard. I would go from the file that is currently living in the github repository, e.g. runtime/syntax/javascript.vim
First change the header, move the current maintainer to the previous maintainer line and add your self as Maintainer. If you intend to maintain the file in a public repository you can mention it there too, so people know where to submit issues/pr or ask questions, etc.
Once you have that, I would go through the various issues here: https://github.com/vim/vim/issues/388, https://github.com/vim/vim/issues/113, https://github.com/vim/vim/pull/2175, https://github.com/vim/vim/pull/1047, https://github.com/vim/vim/pull/1022
Check if those are still valid and if so try to fix them or try to evaluate if it is worth fixing those (or including them for PRs). Note, fixing some of the issues might require some proficient knowledge of Vim regular expressions and syntax priorities. But all of that is documented in the help (Check out :h syntax.txt and :h pattern.txt)
Testing is currently left to be done by the maintainers. Until now, there was no real good way to test them, so I usually just use a couple of test files and check, that they still look valid or the required changes take effect.
If you want to get sophisticated, you could use the newly introduced term_dump...() functions to create automatic testcases however. There are some samples in the src/testdir/test_terminal.vim test of the vim repository. But that is certainly only icing on the cake and not required.
Once you are satisfied with your state, you would basically send the complete syntax file for inclusion with the next Vim runtime file update. The first time, you should however mention that you are stepping up and will be contributing the javascript syntax file from now on. Bram usually has some test script running checking some basics of the vim script files. (i have never seen that however.)
Note: As Bram just included #2802 but has not yet published those changes, you might want to wait until the next runtime file update to include that change in your version as well.
If you have questions, you can always ask on the vim mailinglist.

Joe Reynolds wrote:

I would be interested in maintaining this.
Are there ways of adding tests for syntax files and is there any
documentation on the correct way to contribute to vim?

Thanks for stepping in!
The simple way is to send me the updated file by email.  Update the
header to put you in as the maintainer, and move the previous maintainer
to a previous maintainer field.
So far testing syntax files has been left to the maintainer.  But now
that we have the terminal dump facility, this should be a lot simpler.
See ":help terminal-diff".  There is no such test for a syntax file yet,
thus some exploring is still to be done.
The main goal for syntax tests would be that a change doesn't break any
existing highlighting.  But it can also show off what has been added.
And just having an example of the filetype is already illustrating.
Normal users don't need syntax tests, thus we need to put these in a
separate place, not under runtime/syntax.  Perhaps just under
src/testdir, so that they get run with any "make test" invocation.
--
$ echo pizza > /dev/oven
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Please move this problem forward...

@vitaly-zdanevich from what I see in master branch, the fix was applied in July 2018 by @brammool in commit 91f84f6 (Update runtime files). Maybe it will get included in a next release?

Hm, I hope, template literals in JS nowadays supported by all modern browsers, thank you.

This was already included.


Kilometer-scale volcano tutorial

This branch:

Represents geophysical and geological data provided by local observatories and academics at the local scale. Models are in UTM.
Shows how to represent time-dependent seismicity within existing volcanic models.
Maybe too long, could be splitted.

test failed for added comma in make.jl

Closing pull and revising

Re-test compatibility of the branch

Note that you do not need to close a PR if you spot a mistake; simply push an update to your branch and it will automatically rerun the tests

In addition, please note that we (just) added the UTMData structure, which allows directly importing data with UTM coordinates (and convert it to GeoData for visualization).
See the tutorial as well.
It would be good if you can utilise that in your tutorial as well (you may have to push the latest update of main back into your branch).

Ok, will work on adapting the tutorial

Thanks, this will be a great tutorial. Some comments:

The code under step 4 does not work as given, as it is called depth instead of depthUTM, so change the line

julia> depth =   data[:,3];

to
julia> depthUTM =   data[:,3];

Isn't the data you read from the file modvPS.dat given in UTM coordinates? If so, I don't understand the line

julia> Data_set_Cartesian  =   CartData(we, sn, depth, (vp = Vp3d * (km / s), vs = Vs3d * (km / s), vpvs = Vp_Vs3d,))

I think it is clearer if you read it in as UTM:
julia> Data_set_UTM  =   UTMData(we, sn, depth, 33, true, (vp = Vp3d * (km / s), vs = Vs3d * (km / s), vpvs = Vp_Vs3d,))

In case you want to convert this to Cartesian data (that has the coordinate axis in km's, which is what we use in LaMEM), you need to define a ProjectionPoint around which the Cartesian data will be centered. A ProjectionPoint can be defined with Lat/Lon coordinates, or (in your case easier) with UTM data, in which case we also need to specify the zone & whether we are on the northern hemisphere
julia> proj = ProjectionPoint(mean(Data_set_UTM.EW.val),mean(Data_set_UTM.NS.val),33,true)
ProjectionPoint(40.81783289893781, 14.144736955784808, 427873.0, 4.518887e6, 33, true)

Next, you can convert this to CartData using
julia> Convert2CartData(Data_set_UTM,proj)
CartData
    size : (116, 96, 7)
    x    ϵ [ -5.75 km : 5.75 km]
    y    ϵ [ -4.75 km : 4.75 km]
    z    ϵ [ -4.2 km : 0.6 km]
    fields : (:vp, :vs, :vpvs)

In section 5, julia>   name_vts        = name[24:26]; should be julia>   name_vts        = nameFile[24:26];
You can combine various statements within a single findall statement using:

ind           = findall( (WE .>= 419000) .& (WE.<=435000) .& (SN.>=4514000) .& (SN.<=4528000) );

Do I understand it correctly that you are plotting time-dependent tomographic data? If so, it would be great if you could simply push the play button in Paraview and visualise that. Internally, we are using the great writeVTK package to write paraview data, and this has the option to write .pvd files. It would be fantastic if we can use that here as well (and write a *.pvd file). To be tested

The code under step 4 does not work as given, as it is called depth instead of depthUTM, so change the line
Corrected

Isn't the data you read from the file modvPS.dat given in UTM coordinates? If so, I don't understand the line

julia> Data_set_Cartesian  =   CartData(we, sn, depth, (vp = Vp3d * (km / s), vs = Vs3d * (km / s), vpvs = Vp_Vs3d,))

I am unable to read the shape files containing coastline and morphology using the UTM routines. These shape files are readable in Julia via Shape Shapefile.jl, but there is no way to save them. I have tried using ArchGDAL.jl and GDAL.jl with no success. See the discussion here. Together with UTMdata I also use CartData, so that I can read them in a simple XYZ environment - ProjectionPoint does not solve my issue as the shape files are in UTM. MY Paraview is broken at present, so I cannot recreate the figures. But I agree that a tutorial with ProjectPoint would be useful.

In section 5, julia>   name_vts        = name[24:26]; should be julia>   name_vts        = nameFile[24:26];

Corrected

You can combine various statements within a single findall statement using:

Done

Do I understand it correctly that you are plotting time-dependent tomographic data? If so, it would be great if you could simply push the play button in Paraview and visualise that. Internally, we are using the great writeVTK package to write paraview data, and this has the option to write .pvd files. It would be fantastic if we can use that here as well (and write a *.pvd file). To be tested

No, I plot seismicity with time - this allows me to reproduce the results of this paper. I will try creating a movie where. earthquakes evolve through time as soon as the branch passes the tests and is merged.

all right, fair enough. Thanks for your contribution!


Number of duplicate entries in SST train set are 10 and not one

Sir,
I think there is a small typo in sst_01_overview.ipynb.
According to the output of code cell 7, there are 8544 instances in train_df, and according to code cell 10 there are 8534 instances in dup_train_df which has duplicate entries removed. So in the markdown cell just below cell 10, the number of duplicate entries should be 8544-8534=10, and not one.
This is a screenshot:

Thank you, LGTM.
https://xcs224u-scpd.slack.com/archives/C02B3BT8T47/p1631018699037600

@saniya-m Thanks so much for this! It looks like my math was off by a factor of 10!


Detect Elixir code (http://elixir-lang.org/)

Elixir is a programming language built on top of the Erlang VM. As Erlang, it is a functional language built to support distributed, fault-tolerant, non-stop applications with hot code swapping.
Learn more at: http://elixir-lang.org/
The lexer is already on pygments:
https://bitbucket.org/birkenfeld/pygments-main/pull-request/57/add-elixir-and-elixir-console-lexers
/cc @josevalim

OMG!! \o/
+1 :heart:

:+1: :heart:

+1 <3

+1 :+1: :heart:

+1

+1

+1 <3

+1

+1


RDM pattern_descriptors- not auto generated

The RDM pattern_descriptors field seems to be incorrect in its current form. There should be one descriptor per RDM value, and ideally they contain info about the condition pair (e.g. condition 1 vs 2) that the according dissimilarity value in the RDM reflects. However, these are not auto-generated, and instead contain an index of size # conditions.
I don't think the user should be responsible for generating these descriptors. Thoughts?

Well the descriptors as they are right now are intended as descriptors per pattern/stimulus, not per pair. That is intended.
Do you need these pair_descriptors you describe somewhere?

Ah I see, thanks Heiko! Are these necessary in the rdm object? My confusion originated with the intended size descried in rdms.py under pattern_descriptors, where they are noted as descriptors with 1 value per RDM column (since each column is a dissimilarity value, not a pattern per-se). Is there a reason these descriptors are named something different than the same field in the dataset object (obs_descriptor)?
I don't need the pair_descriptors for anything at the moment.

Hi! they can be something different than the obs_descriptors as often more than one observation can enter the pattern estimate for one pattern.
As the description was confusing: Feel free to change it with your documentation updates! It was meant to mean row/column of the actual matrix.


UCP: Refactor the JavaScript code by TypeScript

Description
We mix the JavaScript and TypeScript code together, so this task is to refactor the JavaScript code by TypeScript.
Score

605

Mentor(s)

@baurine

Contact the mentors: #tidb-challenge-program channel in TiDB Community  Slack Workspace
Recommended Skills

React
TypeScript

/pick-up-challenge

Finish most by PR #469


Copy list for grading to 10

We really only need the top 10, but some stats can be harvested from the original 50.
Copy the list, only return the top 10

Fix "squares" comment to be "square of squares" to match the code.


Create questions don't belong Question List?

First, thanks for your work! I'm finding out your survey.
Currently, I want to create some general questions like: What's your name? How old are you?...before enter to Survey Questions. However, questions're always begin from one, this makes confused.
Let me know if there is a way to resolve this problem.
Thanks!

@quangnd As I understand, you want to be able to have the question visible, but do not want them to be count, am I right?
Do you want to have this values to be stored in the survey result?
The current solution: Create a simple form with two inputs (name and age) and one button: start survey. You may start/show survey after a user enter the data and click on the button: "Start Survey".
A perfect solution - have a survey staring page. We do not have it right now.

Thanks for fast reply @andrewtelnov !
Actually, I'm using your dxsurvey and I forgot to mention about this in my question. As I understand, your service don't support this at the moment.
That's ok! I just want to know. Thanks again!

@quangnd  Yes, it makes sense. I have added: https://github.com/andrewtelnov/surveyjs/issues/93
Unfortunately, I could not make any estimates for this feature. Definitely, we will keep it in mind.
Thank you,
Andrew

please go to  #93


cross sell product and related product fixed

Issue Reference
#7410

Fix limit for related /cross-sell products in products view page

@vijay-webkul
In the related products, it is still showing only 4 products.Here

@Amitk-webkul,
please check the screenshot here:

@vijay-webkul
now It is working fine.

@vijay-webkul
This is working fine. please find the screenshot Here

It should be done from the configuration not hardcoded one.

@Amitk-webkul
I have changed in feature configuration, please check screenshot:-

|


[WIP] Add handling possible short mentions tags to ExpensiMark

This is WIP
Details
The purpose of this PR is to add handling of (possible) short mention tags to ExpensiMark. The PR is work in progress but already handling most cases, but we need further discussions to finish this.
why "possible" short mentions
The only way for us to actually render short-mentions inside live-markdown (and other code using expensimark) we need to have a list of all possible mentions.
This list is not and should not be shared in any way to ExpensiMark, as this is just a parser. However in order to try to match a short mention to a list of actual users, we need some kind of output from ExpensiMark from parsing.
In this PR we define "short-mention" as anything after @ character that would be a valid email prefix.
However this creates multiple edge cases, because text that in the past would be considered just normal text, might now be a short mention.
Current edge cases (based on tests)

test<EMAIL_ADDRESS>
prev return: "test@<a href=\"mailto:here<EMAIL_ADDRESS>now returns: "test<EMAIL_ADDRESS>

test<EMAIL_ADDRESS>
prev: test<EMAIL_ADDRESS>now: test<EMAIL_ADDRESS>

Some other cases can be seen in tests.
CC @puneetlath @tomekzaw @BartoszGrajdek
Fixed Issues
$ https://github.com/Expensify/App/issues/38025
Tests

What unit/integration tests cover your change? What autoQA tests cover your change?
What tests did you perform that validates your changed worked?

QA

What does QA need to do to validate your changes?
What areas to they need to test for regressions?

I have read the CLA Document and I hereby sign the CLA


:dependent => :destroy, the parent is destroyed but the children are neither nullified nor destroyed

I'm using mongomapper and everything works but :dependent => :destroy.
class Parent
include MongoMapper::Document
many :children, :dependent => :destroy (I tried with has_many also)
end
class Child
include MongoMapper::Document
belongs_to :parent
end
The parent is destroyed but the children are neither nullyfied nor destroyed.
ruby: 1.9.3, mongodb: 1.8.2 (mongohq), mongomapper: 0.10.1
Thanks for you help.

Can you provide a snippet of code that shows the :dependent not destroying?

Sorry, I did @company.delete instead of @company.destroy, this is why is didn't work, my bad.

No problem!  Glad to hear the trouble is over.


more compact and informative logging by default

I've made some changes that make the logging output more informative to me as an end user as well as less cluttered. Similar behavior to the original can be enabled by setting verbose to true in the function arguments. The proposed new default output is as follows:
julia> d, clusters, aims = OpenADMIXTURE.run_admixture(filename, 4; T=Float64, use_gpu=false, rng=MersenneTwister(7856));
Performing 5 EM steps for priming
EM Iteration 1 (0.152715371 sec): Loglikelihood = -1.6585565266198235e7
EM Iteration 2 (0.184933523 sec): Loglikelihood = -1.6007521238366533e7
EM Iteration 3 (0.142413634 sec): Loglikelihood = -1.5916445495428987e7
EM Iteration 4 (0.175262876 sec): Loglikelihood = -1.587417626747727e7
EM Iteration 5 (0.158595219 sec): Loglikelihood = -1.5844784297993343e7
initial ll: -1.5844784297993343e7
Starting main algorithm
Iteration 1 (14.293972724 sec): LogLikelihood = -1.5661966737375751e7, reldiff = 0.011538027730724302
    LogLikelihoods: Previous = -1.5844784297993343e7, QN = -1.5661966737375751e7, Basic = -1.5658797780233778e7
Iteration 2 (10.456170418 sec): LogLikelihood = -1.5605199791986194e7, reldiff = 0.0036245093825980914
    LogLikelihoods: Previous = -1.5661966737375751e7, QN = -1.5605199791986194e7, Basic = -1.5609040036582384e7
Iteration 3 (9.546737437 sec): LogLikelihood = -1.5586228372093504e7, reldiff = 0.0012157114388520478
    LogLikelihoods: Previous = -1.5605199791986194e7, QN = -1.5586228372093504e7, Basic = -1.558989311248903e7
Iteration 4 (9.245080639 sec): LogLikelihood = -1.557902813062439e7, reldiff = 0.00046196175862575915
    LogLikelihoods: Previous = -1.5586228372093504e7, QN = -1.557902813062439e7, Basic = -1.557593892598145e7
Iteration 5 (9.110568684 sec): LogLikelihood = -1.5567066087137524e7, reldiff = 0.0007678298919912029
    LogLikelihoods: Previous = -1.557902813062439e7, QN = -1.5567066087137524e7, Basic = -1.5566929427850641e7
Iteration 6 (9.327391913 sec): LogLikelihood = -1.5561476004841125e7, reldiff = 0.000359096715149059
    LogLikelihoods: Previous = -1.5567066087137524e7, QN = -1.5561476004841125e7, Basic = -1.556264024120358e7
Iteration 7 (10.00942772 sec): LogLikelihood = -1.5558616674667932e7, reldiff = 0.00018374414948190118
    LogLikelihoods: Previous = -1.5561476004841125e7, QN = -1.5558616674667932e7, Basic = -1.5558483191215409e7
Iteration 8 (10.512415633 sec): LogLikelihood = -1.5556607054798864e7, reldiff = 0.00012916443094457538
    LogLikelihoods: Previous = -1.5558616674667932e7, QN = -1.5556607054798864e7, Basic = -1.555656394773972e7
Iteration 9 (9.690703713 sec): LogLikelihood = -1.5555028877712639e7, reldiff = 0.00010144738378141057
    LogLikelihoods: Previous = -1.5556607054798864e7, QN = -1.5555028877712639e7, Basic = -1.5555272556777712e7
Iteration 10 (9.594756342 sec): LogLikelihood = -1.5554389948288705e7, reldiff = 4.107542512179528e-5
    LogLikelihoods: Previous = -1.5555028877712639e7, QN = -1.5572307162296195e7, Basic = -1.5554389948288705e7
Iteration 11 (9.39072147 sec): LogLikelihood = -1.5553867013950767e7, reldiff = 3.361972662873465e-5
    LogLikelihoods: Previous = -1.5554389948288705e7, QN = -1.5562818039977925e7, Basic = -1.5553867013950767e7
Iteration 12 (8.895711263 sec): LogLikelihood = -1.5553428107705034e7, reldiff = 2.8218464600411636e-5
    LogLikelihoods: Previous = -1.5553867013950767e7, QN = -1.5559131012878079e7, Basic = -1.5553428107705034e7
Iteration 13 (9.072996228 sec): LogLikelihood = -1.5553067050573548e7, reldiff = 2.3213990445434272e-5
    LogLikelihoods: Previous = -1.5553428107705034e7, QN = -1.5554525394768834e7, Basic = -1.5553067050573548e7
Iteration 14 (9.523288256 sec): LogLikelihood = -1.555278497410975e7, reldiff = 1.8136388332978923e-5
    LogLikelihoods: Previous = -1.5553067050573548e7, QN = -1.5553105606121972e7, Basic = -1.555278497410975e7
Iteration 15 (9.298866998 sec): LogLikelihood = -1.5552639211087858e7, reldiff = 9.372149241089872e-6
    LogLikelihoods: Previous = -1.555278497410975e7, QN = -1.5552639211087858e7, Basic = -1.5552595414835572e7
Iteration 16 (8.900257679 sec): LogLikelihood = -1.5552328125458859e7, reldiff = 2.000211184591851e-5
    LogLikelihoods: Previous = -1.5552639211087858e7, QN = -1.5552328125458859e7, Basic = -1.5552311626407882e7
Iteration 17 (8.672770113 sec): LogLikelihood = -1.5552259885576095e7, reldiff = 4.387759968346335e-6
    LogLikelihoods: Previous = -1.5552328125458859e7, QN = -1.5552259885576095e7, Basic = -1.5552266154130427e7
Iteration 18 (8.736132223 sec): LogLikelihood = -1.5552230063723285e7, reldiff = 1.917525364808176e-6
    LogLikelihoods: Previous = -1.5552259885576095e7, QN = -1.5552230063723285e7, Basic = -1.5552235725528445e7
Iteration 19 (8.653978879 sec): LogLikelihood = -1.5552216346354242e7, reldiff = 8.820194265473032e-7
    LogLikelihoods: Previous = -1.5552230063723285e7, QN = -1.5552216346354242e7, Basic = -1.555222164931152e7
Iteration 20 (8.722446271 sec): LogLikelihood = -1.5552207512250777e7, reldiff = 5.680285863018589e-7
    LogLikelihoods: Previous = -1.5552216346354242e7, QN = -1.5552207512250777e7, Basic = -1.5552210406862404e7
Iteration 21 (8.746605755 sec): LogLikelihood = -1.5552200611477997e7, reldiff = 4.437166090244169e-7
    LogLikelihoods: Previous = -1.5552207512250777e7, QN = -1.5552200611477997e7, Basic = -1.5552204951377708e7
Iteration 22 (8.630398232 sec): LogLikelihood = -1.5552197336867832e7, reldiff = 2.1055606517124269e-7
    LogLikelihoods: Previous = -1.5552200611477997e7, QN = -1.5552197336867832e7, Basic = -1.5552198775938418e7
Iteration 23 (8.730630149 sec): LogLikelihood = -1.5552194868097581e7, reldiff = 1.587409288349003e-7
    LogLikelihoods: Previous = -1.5552197336867832e7, QN = -1.5552194868097581e7, Basic = -1.5552196340740334e7
Iteration 24 (9.131821986 sec): LogLikelihood = -1.5552193929721253e7, reldiff = 6.033722802055984e-8
    LogLikelihoods: Previous = -1.5552194868097581e7, QN = -1.5552193929721253e7, Basic = -1.5552194288014418e7
Main algorithm converged in 24 iterations over<PHONE_NUMBER>42 sec.

I am also working on a command-line interface and docker/singularity container at BEFH/docker_OpenADMIXTURE, but it's not ready yet for prime-time.

 I was unable to update the manifest because I am using the LTS version.

Excellent improvement 👍

Thank you for the nice improvement. I will review and merge it later this week.

Thanks! While I have you here, how do I project genotypes for new individuals with the same variants onto the model generated?
I know this is possible using the Q matrix, but I cannot figure out how (ADMIXTURE does this). I assume it's similar to projecting PCs using SNP loadings.

I have added fix_p and fix_q keywords to qn_admixture!() function. For now, you can run five steps of EM with the new genotype file, then load the p matrix to the AdmixData object, then run qn_admixture!() with fix_p = true. I will add a more user-friendly interface later this month.

@BEFH To the function run_admixture(), I have added boolean fix_q, fix_p keyword arguments (true means q or p will not be updated) and init_q,  init_p keyword arguments for setting initial values of d.q and d.p for an internal AdmixData object d.

Perfect. I should probably add that to my command line interface script and share with you.


Fix passing flag --discovery-token-unsafe-skip-ca-verification to kubeadm join

Address the comment in https://github.com/kubernetes/kubernetes-anywhere/pull/488/files#r153078767
I have tested the changes in my local gce environment and it has passed for "$KUBEADM_VERSION" == "stable"
/cc @xiangpengzhao @luxas @pipejakob

/assign @pipejakob

I now got merge rights here (woot!) so merging

https://github.com/kubernetes/kubernetes/issues/56091 is green. Thanks @shashidharatd ! :+1:


[Bug] Unable to add documents to subcollections using the functions shell

I can't seem to be able to add data to subcollections in firestore using the functions shell emulator
Environment details

OS: Mac OS Catalin
Node.js version: v8.15.0
npm version: 6.7.0
@google-cloud/firestore version: "firebase-admin": "8.7.0"

Steps to reproduce

Create a simple script that you can run in Firebase shell (ex):

admin.initializeApp({...});
const db = admin.firestore();

const run = async () => {
  await db.collection('papers')
      .doc(docId)
      .collection('pens')
      .add({x: 'a'});
};
run();

Run the above script through the emulator (ex):

firebase functions:shell < script.js

Expected Result:
This code should run without any issues and add the object {x: 'a'} to the pens subcollection
Actual Result:
This code fails when run through the functions:shell but runs fine when added as a cloud function and run through the cloud function
Error Stack
(node:90760) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'constructor' of null
    at extractBaseClassName (/.../functions/node_modules/@google-cloud/firestore/build/src/validate.js:35:33)
    at Object.customObjectMessage (/.../functions/node_modules/@google-cloud/firestore/build/src/validate.js:55:26)
    at Object.validateDocumentData (/.../functions/node_modules/@google-cloud/firestore/build/src/write-batch.js:608:36)
    at CollectionReference.add (/.../functions/node_modules/@google-cloud/firestore/build/src/reference.js:1765:23)
    at runB (repl:43:6)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Stackoverflow Question:
https://stackoverflow.com/questions/59013268/unable-to-add-new-documents-to-a-collection-in-firestore-using-functionsshell

I'm guessing this has been recorded as a bug considering that the "bug" label was added. Looking forward to the fix. If I can help let me know

@schmidt-sebastian any thoughts on this one?

@DeveloperUX This does not reproduce for me. I wonder if this might be caused by a package that is rewriting some parts of the prototype chain. For what it is worth, the input {x: 'a'} should not even invoke customObjectMessage().
export function validateDocumentData(
  arg: string | number,
  obj: unknown,
  allowDeletes: boolean
): void {
  if (!isPlainObject(obj)) {
    throw new Error(customObjectMessage(arg, obj));  // This should be true
  }
  ...
}

function isPlainObject(input: unknown): input is DocumentData {
  return (
   Object.prototype.toString.call(input) === '[object Object]' &&
    (Object.getPrototypeOf(input) === Object.prototype ||
      Object.getPrototypeOf(input) === null)
  );
}

isPlainObject({x: 'a'}) returns true for me.
Can you send us a small self-contained reproduction (including your package.json) so we can investigate further?

Closing this due to inactivity. We can re-open this issue if we receive a repro.

I've run into the same issue. Object.getPrototypeOf(input) === Object.prototype is the problem.
When edit that line of code in serializer.js in my node_modules to log out Object.getPrototypeOf(input) === Object.prototype it returns false. But when I log the exact same line in my own project's code it returns true.

Fix is coming!


fix: set language to the chat message

Bug Fix
Proposed Changes

[x] Migrates language field from Chat to ChatMessage
[x] Adds language to converse endpoint

Associated Issue

Fixes #126

Associated PR

Related frontend PR: coronasafe/ayushma_fe#13

@cp-Coder no need to call the translate APIs in the migration. We can just leave blanks, we don't have to have any backwards compatibility for now. Also can you rather than having message for the original message and translated_message for the translated message have message for the translated message and original_message for the english version?


fetch-versions: Cleanups the testing logics and make it more robust

add CURL_OPTIONS so we can debug curl command if needed
set -e and set -u
read the github json from the temporary file...
make sure to --failearly with curl when trying url if needed

(second try with commented logic to get nightly so we try getting the releases)
Signed-off-by: Chmouel Boudjnah<EMAIL_ADDRESS>

/lgtm


Fix Error in README

The README gives the following example TOML entry to include a favicon.
[site]
icon = "/media/icon.ico"

However, blog_emt emits the favicon link as relative to the root of the website, so this path would be emitted as //media/favicon.ico which is invalid.
This should be a relative path from the source/ directory.

Fixed.


add api that exposes uptime info

please add an api which allows farmers to get the uptime for their node

Please define uptime.
What exactly is the information you want to see ?
Uptime as the number of second the node is up since it booted ?
Or uptime as the percentage the node has been up over the last month ?

definition: minimum one ping a day means the node is online for that day in our current model
would be good to give access to all pings we get from a node via the api. then the farmer can build her/his own representation of uptime

give access to all pings we get from a node via the api

I don't see how we would provide that...a list of timestamp ?
This list would grow forever, this is not something we can either store nor return in an API.

maybe just give them the ping/timestamp when it happens? so we do not store but give them access to the same data we get


For the conditional singleton or the singleton registered with AnyKey - should we create a new singleton per condition or the resolution key?

MS.DI Keyed Services #608 are adding to the boiling pot.

yes, we would and doing this.