Windows issue

Before submitting the PR, please go through the sections below and fill in what you can. If there are any items that are irrelevant for the current PR, remove the row. If a relevant option is missing, please add it as an item and add a PR comment informing that the new option should be included into this template.

All relevant items should be ticked before the PR is merged

Description

[ ] Add a summary of the changes and the related issue
[ ] Add motivation and context regarding why the change is needed
[ ] List / describe any dependencies or other changes required for this change
[ ] Fixes [link to issue / Jira issue ID]

Type of change

[ ] Documentation
[ ] Workflow
[ ] Security Alert fix
[ ] Bug fix (non-breaking)
[ ] New feature (non-breaking)
[ ] Breaking change (breaking, will cause existing functionality to not work as expected)
[ ] Tests (only)

Checklist:
General

[ ] Changelog: New row added. Not needed when PR includes only tests.
[ ] Code change

[ ] Self-review of code done
[ ] Comments added, particularly in hard-to-understand areas
[ ] Documentation is updated

Repository / Releases

[ ] Blocking PRs have been merged
[ ] Rebase / update of branch done
[ ] PR to master branch (Product Owner / Scrum Master)

[ ] The version is updated

[ ] I am bumping the major version (e.g. 1.x.x to 2.x.x)

[ ] I have made the corresponding changes to the API version

Checks

[ ] Formatting: Black & Prettier checks pass
[ ] CodeQL passes
[ ] Tests

[ ] I have added tests for the new code
[ ] The tests pass

Duplicate and original


Wiring up the PrimFunc resource_handle

@tqchen / @areusch I've spun this out of the Device API RFC for independent consideration.

@junrushao1994 @tqchen,
A friendly ping!

Will comment more later. One thing I want to note is that resource handle is a special thing for PackedCFunc signature and do not generally exists in a normal packed func(that is backed by say a GPU driver closure).
As a result, we might want to think a bit more carefully on the calling convention here. My recommendation would still be try to hide this variables from the PrimFunc interface and leverage intrinsics(such as get resource handle) to obtain the handle from the environment.
We might be able to introduce call packed c func with handle intrinsic that passes the handle around packed c func

okay I've done a bit more research on this one. Here is the thing causing tension here:

at present, tir.call_packed codegens to TVMFuncCall and TVMFuncCall does not in fact accept resource_handle as an argument. it is not possible to supply resource_handle to tir.call_packed.
however, that is not actually the ultimate goal of this PR. the ultimate goal of this PR is to supply resource_handle to tir.call_cpacked, which doesn't use TVMFuncCall and instead invokes the TVMBackendPackedCFunc directly.
this basically works in a very narrow set of use cases which meet all of these conditions:
a) when we don't need TVMFuncCall because we can get TVMBackendPackedCFunc* directly
b) when we know that we have the resource_handle that PackedFunc expects.
c) when the C interface API to AOT is used and therefore AOT Executor has a void* context to be supplied to device kernel launch PackedFunc

This really has quite a narrow use case: in the C runtime with the AOT executor and when the C interface API is used. Other use cases disqualify this usage pattern:

If the PackedFunc API is used we currently have no good way to pass the proposed TVM<Model>_Devices struct into AOTExecutor. We could pass it as OpaqueHandle if we had to.
If the C++ runtime is used, in most cases we cannot get the TVMBackendPackedCFunc* directly and must operate with the opaque TVMFunctionHandle and TVMFuncCall
It is possible that within a given compiled AOT module, we could employ tir.call_cpacked to refer to other DSO-exportable functions directly. However, this wouldn't necessarily extend to non-DSO-exportable functions, which in any case typically gain the context closure from sptr_to_self and/or a this capture. Also, doing so would hit the linker limitations discussed in https://discuss.tvm.apache.org/t/introduce-artifact-a-container-for-generated-code/11099/2.

Taken together, this means we need the following restrictions on this usage pattern:

-runtime must be c due to the final bullet point above.
-executor must be aot.
-unpacked-api must be 0. When -unpacked-api is 1, we just append this to the extern call args, correct?
-interface-api is likely c. As discussed above, this could work with packed, but the awkward OpaqueHandle dtype must be used.

Considering this altogether, this is essentially an attempt to simplify the multi-Module late-bound import system for use with resource-constrained embedded devices. The key piece of missing information needed without such a system is the context pointer. I see two routes forward here:

We add resource_handle to tir.call_cpacked and resolve the incongruity between usage for a device kernel function and the current usage in the C Runtime as Module*.
We just lower the extern schedule to a CallNode whose args includes an OpaqueHandle at a position which the driver is aware of. For instance, following the current suggestion, such OpaqueHandle would be the final arg. The question here is how to indicate to the executor that such argument should be filled from the TVMDevices struct. This could be done either as an attr of the CallNode or by introducing a new dtype (I sort of favor the former, as void* is exactly OpaqueHandle).

Since ultimately the driver must be written knowing where the "context" is going to be (either as this member or as resource_handle), the driver must also be designed around this choice. If portability between C and C++ runtimes is desired, it will need to choose an approach that works with both. While I appreciate that Module is generally overly bloated for many embedded applications, we do rely on it for the purposes of autotvm and providing the TVM RPC server. Moving away from it seems like it would add significant cognitive overhead to the design of microTVM. Given we may need resource_handle to be the Module* should TVMBackendGetFuncFromEnv need to be implemented on microTVM (admittedly, this means that the Module import mechanism is in use which is even more bloated), it kind of seems like we should avoid trying to repurpose resource_handle here and just adopt route 2 above.
Ultimately at tension here is TVMBackendGetFuncFromEnv and the need to provide a less bloated context for use with the TVM C runtime. I'm not sold on this opinion, just writing down my thoughts. Perhaps others could weigh in here. Supporting Module's import mechanism on the C runtime is indeed considerable extra complexity for questionable benefit. And, this RFC is part of a larger solution which supplants the need for Module import. Perhaps the outcome of the Article RFC (e.g. decision on what the long-term expectations of the compiler are on the module load process) also play in here as well.

@mbs-octoml @electriclillies and I discussed this at length and we followed up with @Mousius offline as well. While it is tempting to re-use resource_handle to pass a this context void* through to Device API impls, it seems like it ultimately amounts to carving out an exception case where, when targeting the C Runtime using the AOT Executor, TIR gets to control resource_handle; in any other case, it's either impossible to or requires significant runtime changes. A concern is that driver authors would ideally like a predictable programming model. Going the resource_handle route means that the programming model is more complex--two different ways to pass device_api_context depending on the targeted runtime and executor.
Given this, it seems like the best route is just to add it to the arguments list. @Mousius is going to try this and see if we run in to any other issues. According to @Mousius , past attempts to fully encapsulate the device_api_context parameter in tir::Call have maybe ran into issues with ArgBinder so we're going to see if this works and go from there.

i agree, i mean that the intrinsic translate to the implicit ctx parameters as part of fn call


Update README.md

I think theres just some linting errors to fix before we can merge this. Can you run yarn lint:fix?


[hotfix][ci] Fix hugo docs builds

The destination argument is relative to the source

Good catch. We should look into unifying the two scripts

Thx, merging!


GroupBy: Fix reducing by subset of grouper dims

[x] Tests added

Fixes yet another bug with GroupBy reductions. We weren't assigning the group index when reducing by a subset of dimensions present on the grouper
This will only pass when flox 0.7.1 reaches conda-forge.

Turns out we don't support this without flox! Marking as draft for now.


service mode

please give me the systemctl script . i need to run it as service in linux.
thanks

Systemd scripts are fairly easy to write these days:
[Unit]
StartLimitIntervalSec=5
StartLimitBurst=0

[Service]
ExecStart=/usr/local/udptunnel/udptunnel
WorkingDirectory=/usr/local/udptunnel
User=root
Group=root
Restart=on-failure

[Install]
WantedBy=multi-user.target

thanks a lot
On Fri, Jan 20, 2023, 23:24 Joe Tsai @.***> wrote:

Systemd scripts are fairly easy to write these days:
[Unit]
StartLimitIntervalSec=5
StartLimitBurst=0
[Service]
ExecStart=/usr/local/udptunnel/udptunnel
WorkingDirectory=/usr/local/udptunnel
User=root
Group=root
Restart=on-failure
[Install]
WantedBy=multi-user.target
—
Reply to this email directly, view it on GitHub
https://github.com/dsnet/udptunnel/issues/10#issuecomment-1398860901,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQWQV5XEPQJOFHGGFFGAELWTLUP7ANCNFSM6AAAAAAUBSX7NY
.
You are receiving this because you authored the thread.Message ID:
@.***>


(*feat) Migrate to EndpointSlices instead of Endpoints API

Please describe the Improvement and/or Feature Request

Stable as of Kubernetes 1.21, EndpointSlices are "a more scalable and extensible alternative to Endpoints." Specifically, they associate the pod name with its backing ip address in the manifest, AND they contain zone/node information with improvements on the way.
Scope (please mark with X where applicable)

New Functionality          [X]
Envoy Control Plane        [X]

Possible use cases

EndpointSlices would make several new features/initiatives easier, namely more robust locality load balancing as well as StatefulSet support. OSM only supports Kubernetes 1.20 and up, so EndpointSlice support is a pretty reasonable expectation for target clusters.

Going to resize this to a medium, and bring it into the Multicluster project board, as the MCS API will exclusively create endpoint slices, not endpoints


Error for resolving dependency com.crygier:graphql-jpa v.0.3-SNAPSHOT

I have cloned your project and try to import in my IDE. but an issue came to me. I could not resolve my dependency for com.crygier:graphql-jpa v.0.3-SNAPSHOT. Any solution for this issue will be helpful so much. Thank you

Hi! Have a look at: https://github.com/jcrygier/graphql-jpa
You'll want to install a local version of the master branch, which should match 0.3-snapshot. Only once that upstream project performs a release can I update my dependency, so sorry about the slight inconvenience until then.

sorry to say this, but your project is still full of error. You did not include dependency of spring boot and jpa in pom. and when I try to run by firstly creating class where the main method inside it. but still full of error. may be u can make a documentation how to work with ur project.

Traveling right now.. I'll return March 6th. Until then I'm without a PC.
Downside currently is that I depend on a snapshot version of the library
you found, so if you can get him to do a release then you can upgrade the
dependency to the new version.
On Feb 13, 2017 3:24 PM, "Muhammad Iskandar Dzulqornain" <
<EMAIL_ADDRESS>wrote:

sorry to say this, but your project is still full of error. You did not
include dependency of spring boot and jpa in pom. and when I try to run by
firstly creating class where the main method inside it. but still full of
error. may be u can make a documentation how to work with ur project.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/timtebeek/graphql-jpa-spring-boot-starter/issues/1#issuecomment-279477320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-tBsXuGTu6F0omousuQyYmjerH-Dh9ks5rcJ_BgaJpZM4Ly5jn
.

Following jcrygier/graphql-jpa#20 I've been able to address most of your issues in 438101ae2a4ea2bd5f36d4d7dc90424067504f1c.
If you would still like me to expand the documentation please let me know. By now you should just be able to add the starter as a dependency without any further tweaks get a functioning graphql endpoint.


Issues with shared Github Actions workflows

Hi @zgosalvez
Firstly, thanks a lot for this Action, I use it every day.
I'm currently sharing my day-to-day workflows on a this repository and your Action currently fails with the new syntax (see https://docs.github.com/en/actions/learn-github-actions/reusing-workflows#calling-a-reusable-workflow) (if you need more information, here is the failed job).
Furthermore, I think we can ensure that theses shared workflow should be pinned like other uses fields.

Finally, GitHub allows for reusing workflows. This is very new, and I'll need time to learn the changes and review the code to support the new syntax. Hopefully, we can have version 2 released soon, but any PR is welcome!

@zgosalvez I made a PR to add compatibility with this new Github feature


unify cli and web tailwind config colors with figma colors

woops thanks. going with the alt syntax rather than replacing all instances of blue


Restrict struct warning suppression to clang only

Fixes the warnings recently reported by @DanielGibson in #45. It seems that -Wgnu-anonymous-struct is a flag for clang only, since gcc and g++ apparently support anonymous structs out of the box.
As a side note, our Travis is set up to build in both clang and g++, and the clang build showed no warnings even before #45 was merged. (And this is with -Wall enabled.)

Also, you can see the warnings @DanielGibson reported if you expand the "make" section of this Travis build (from the commit before this PR): https://travis-ci.org/StrangeZak/Handmade-Math/jobs/189034388.
You can confirm that those warnings are not present on either the clang or g++ builds for this PR: https://travis-ci.org/StrangeZak/Handmade-Math/builds/192038881

Is this good to be merged in?

I think so – it's just compiler warnings, after all, and Travis shows that they don't show up in gcc any more.

I am getting the anonymous struct warning with the MinGW G++ compiler, does anyone know how to properly suppress it?

Ive never used G++ so im not sure how to do it in the file, but i can look after the work day, for a temporary fix -Wno- should work as a compiler switch to disable anonymous struct warning

My understanding was that anonymous structs are actually non-standard functionality that were implemented in gcc and g++ and, although unspecified, are used everywhere anyway.
https://stackoverflow.com/questions/14248044/are-anonymous-structs-standard-and-really-what-are-they

Which is to say, I'm not sure why MinGW G++ would be complaining, since it's basically a G++ feature anyway.

It might care about portability and standards conformance more than some other compilers.. you'd probably not get the warning when building with -std=gnu++03 or gnu++11. I /think/ gnu extensions are enabled by default on Linux, maybe they're disabled by default in MinGW (so MinGW might default to -std=c++11 instead of gnu++11)?
Either way, we should probably find out, what the exact error name in GCC is, what versions support it and then suppress it for them - as I wrote elsewhere, at least GCC 5.4 doesn't know -Wgnu-anonymous-struct and produces a warning when using that in #pragma GCC diagnostic ignored. Maybe the warning has another name in GCC (vs clang), or maybe it's only supported in 6.0 and newer or something.

I can confirm the following don't work:
-std=gnu++03
-std=gnu++11
-std=c++11
-fms-extensions (recommended here)
The exact warning is:
warning: ISO C++ prohibits anonymous structs [-Wpedantic]

ok, maybe don't use -Wpedantic then? It complains about everything that's not 100% standard-conforming, which is not very practical, as you can see..

It really sucks that these are standard in C, but not C++ not sure what the committee is doing over there to not allow anonymous structs.

@DanielGibson that's my current solution!

Ok just to close this off, it seems that disabling pedantic is simply the only way to use anonymous structs on MinGW. It's the only accepted answer to this SO question and it's GLM's solution too. Hopefully it'll be legal C++ in the future. ¯_(ツ)_/¯


Feature/33 decode barcodes csv error

Closes #33

Coverage increased (+1.9%) to 60.338% when pulling 4da5a5951dd51cf1d14fdfd83a24ef09af459647 on feature/33-decode_barcodes-csv-error into 041e638c9383b9106c9118c0777edaaf6cad3bfa on master.


this._webHook.open is not a function

I'm getting this error when I try to run webhook with this code, which is a derivate of this code:
C:\Users\venta\projects\node\node_modules\node-telegram-bot-api\lib\telegram.js:
304
    return this._webHook.open();
                         ^

TypeError: this._webHook.open is not a function
    at TelegramBot.openWebHook (C:\Users\venta\projects\node\node_modules\node-telegram-bot-api\lib\telegram.js:304:26)
    at new TelegramBot (C:\Users\venta\projects\node\node_modules\node-telegram-bot-api\lib\telegram.js:93:14)
    at Object.<anonymous> (C:\Users\venta\projects\node\ngroktest.js:29:13)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:425:7)
    at startup (bootstrap_node.js:146:9)
    at bootstrap_node.js:540:3

I have no idea what it means or how to fix it or reproduce it with simple code, so I'll just leave it to you.

_webHook is not intended to be accessed that way. _ means that is private.
If you want to create a webHook, you should provide TelegramBot constructor webHook options.

!CLOSE

why: Since we can not reproduce, we can neither confirm this bug nor fix it. Sorry, please provide us with more information (for reproduction), if you wish to re-open the issue.


Leetcode Question Number 3

Leetcode Question Number 3 soultion needs to be added in the repo .
The link for the question is this.
Accepted Languages C++ / JAVA .
You Only need to add the  class Solution in the file.
Make Sure you have read the contributions guidelines before creating an PR.

@amanv8060 please assign me this issue under hacktoberfest.

@amanv8060 please assign me this issue under hacktoberfest.


refactor: remove settooltip

CATEGORY
Choose one

[x] Refactor

SUMMARY
Historically, setTooltip hook was pass from Superset to visualization components. The visualization components call this function and let tooltip rendering be handled by ChartRenderer.jsx. This has been used by the deck.gl plugins only.
The recent changes in
https://github.com/apache-superset/superset-ui-plugins-deckgl/pull/12 and
https://github.com/apache-superset/superset-ui-plugins-deckgl/pull/13
make the deck.gl charts handle their own tooltips within components.
There is no longer needed for this setTooltip mechanism after #9325 (bump version) is merged.
TEST PLAN
Run locally
REVIEWERS
@etr2460 @ktmud

Ping for review.


custom report template & non-SVG figure format

be able to pass the path of the custom report template to qs.reports.html
support figure formats such as png, jpeg etc. in report html

Thanks.

:+1:  Looking forward to this feature !


Ability to specify Tags across all resources

We have a common set of tags that we apply to all of our AWS resources where possible. These tags are normally used for organisation purposes, such as cost allocation.
Is it possible to define a set of tags that could be applied to all resources that support them? Ideally we'd like an API that looked something like this
export default class Stack extends cdk.Stack {
  constructor (parent: cdk.App, name: string, props?: cdk.StackProps) {
    super(parent, name, props)
    this.setGlobalTags({ ComponentName: 'MyComponent', ChargeCode: 'S-XXX' })
  }
}

I've read through an issue (https://github.com/awslabs/aws-cdk/issues/91) but it's unclear to me if:

Something exists for our use case
If it does exist, how it can be used

Thanks in advance 😄

Resolved by #1451


Add schema inheritance support feature

background
Add feature to support schema inheritance

@hieuk09 I've just addressed your comment, could you take a look? 🙇
The schema seems to be rendered correctly in react-jsonschema-form

I will check with AP team whether the library they're using can support this, if not, we can merge all schemas from allOf in BE before returning to FE as you mentioned
caveat
For the ref schema parser, currently I'm doing a hack to skip the key schema from the loaded $ref schema, cuz the form can't be rendered with it. Not sure if this is the right way to handle such the case


Resolve is broken?

❯ rim resolve release
thread 'main' panicked at 'byte index 8 is out of bounds of `release`', src/macos.rs:429:35
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Fixed.


Customizing form field isn't clear

Could you please provide more extended example?

Hello, current docs are a little bit out of date about that. I'll update them soon.
Basically components are styleable via react-stylesheet:
import {styleComponent} from 'react-stylesheet'
import {Field, Label} from 'react-forms'

let StyledField = styleComponent(Field, {
  Label(props) {
    return <Label {...props} className="customClassname" />
  }
})

Ok. Thanks. Looking forward to updated docs


Retrieving stats when running with --no-web

What is the recommended way of retrieving stats from locust when running with '--no-web'?
I am currently running a load test programmatically and with the web interface disabled, I am unable to poll stats/requests/csv while the test is running.
I tried using the log file with '--print-stats' but the stats are not printed to the log.
Thanks!

If you have set the --loglevel greater than info , you will not be able to capture the stats !
Thanks

I'm using the following command line which I'm assuming uses the default log level of INFO:
locust --no-web -c 100 -r 100 -f scripts/main.py --logfile=./test.log
I see no stats in test.log :(

i see '--print-stats ' option missing .. try below command
locust --no-web -c 100 -r 100 -f scripts/main.py --logfile=./test.log --print-stats

Yeah I tried that but sadly nothing is written to the log file :( This was the reason I created a pull request to allow you to print out stats to a separate file.

@rktbear you must mean this pull request: #291
:+1: on this idea! I like that I can save a csv file of results from the web interface. I'd love it if locust could save the csv file automatically when you run it with --no-web.

This has become an issue for me too. I'd like to run locust with pytest and capture the stats in a usable format. Any progress on this PR? Anything I can help with?

I have been using this pull request locally for all my load testing at work and it's been super useful especially when passed through a matplotlib script for plotting an analysis.

@rktbear Any chance you can share that matplotlib script? I foresee having to do a similar thing and it would be great to see your approach.

@robcowie I made a slight mistake in my last message, I've actually been using a slightly different approach to pull out requests data that is different to the pull request.
You can find my docker file and associated matplotlib script here https://github.com/rktbear/docker-locust.
It would probably be easy to retrofit the script to work with my pull requests too!
Hope this helps :)

Up up pl
@robcowie https://github.com/robcowie I made a slight mistake in my last
message, I've actually been using a slightly different approach to pull out
requests data that is different to the pull request.
You can find my docker file and associated matplotlib script here
https://github.com/rktbear/docker-locust.
It would probably be easy to retrofit the script to work with my pull
requests too!
Hope this helps :)
—
Reply to this email directly or view it on GitHub
https://github.com/locustio/locust/issues/290#issuecomment-121064450.

:+1:  for this PR, can't wait to see it in the production code

There are at least couple PRs regarding to retrieving CSV files when using --noweb option. Any news about when that kind of feature might be coming to release version? It is quite useful when doing automated tests and trying to do trend graphing with that data. In this kind of scenarios CSV import option in console is very critical feature.

Any updates ?

At the moment there is following work around what we have used in test automation purposes.
nohup locust -f test.py &
LOCUST_PID=$!
echo $LOCUST_PID
sleep 2
curl --data "hatch_rate=5&locust_count=60" http://localhost:8089/swarm
sleep 60
curl localhost:8089/stats/requests/csv -o requests_stats.csv
kill -9 $LOCUST_PID

I've been using Jenkins to run the Locust command and that will print out the console results to a log for me.  Then I ship the metrics using logstash (using a logstash pattern) to elasticsearch to be visualized in Kibana in near real time.

Shouldn't this issue be closed now that --only-summary and --csv=outputName flags are present?


Markdown

Add mapping for markdown, possible just to insert the emoji itself?

This should do the trick? https://github.com/idleberg/vscode-emoji-code/pull/3


[Proposal] Use implicit ambassadors when detecting cross-node --link

Ambassadors being described as the official, preferred (and only) way to handle cross-node links, I wonder if it would worth to hack around it, while native overlay networks and cross-node container-graph db lands in docker itself.
I know about #251, and I know swarm without --link is not that useful (pardon me :)).
I've implemented a rough POC back when fig was not docker-compose yet.
Is it something that would worth adding? Do you have another solution, until this feature lands natively?
Thanks :)

I think we should wait to have this feature natively.
Soon, Swarm will reschedule containers on host failure.
This will get very complicated with ambassadors.
Networking is moving very fast on the engine side.
Let's revisit the question in a few weeks.
Thanks.

@vieux thanks for the fast answer. good to hear that networking is going well :)
I'm still wondering how the graph will be stored, since it currently a sqlite db, local to each node.
Anyway, thanks for the awesome work!

duplicate of  #221.


CLRAssemblies, ASym Key, Sym Key checks in Database.Assertions.ps1 Incorrect

Bug Report
General Troubleshooting steps

[x] Verified running the latest release of dbachecks?
DBAChecks 2.0.3
DBATools 1.0.114
Pester 4.10.1
PSFramework 1.1.59

Does (Find-Module dbachecks).Version match (Get-Module dbachecks).Version.ToString()

[x] Verified errors are not related to permissions?
[x] Can duplicate in new/clean PowerShell session (clean = powershell -NoProfile)?

Version Information

Operating System (Name|Version): Server 2012 R2 & Server 2016 Standard
PowerShell Version: 5.1 or 7.0.1
SQL Server (Edition|Version): Range from 2005 to 2017

Steps to Reproduce
<--
PLEASE include as much information as possible if this is a bug report.
The more you include the faster we can identify the problem and get it fixed.
-->

[ ] Attach any screenshots (if possible/allowed)
[ ] Attach output from PowerShell console (if possible/allowed)

Description of Bug
<--
PLEASE include as much information as possible if this is a bug
Explain what it does that you would like it not to do
or
What it doesnt do that you would like it to do :-)
-->
The checks for these seem to be completly wrong for CLR or just need a tweak for the keys issue, below is more detail but I cant seem to get the CLR check to work correctly, maybe someone with more PoSh SMO skills can see the error in my ways on the code
Line 89 is using Get-DbaDbEncryption to check for Symmetric Keys when this check is for CLR Assemblies.
I believe the line should be below but it is not filtering out correctly, maybe some one can tweak this to be correct
@(Get-DbaDbAssembly -SqlInstance $Instance -Database $Database | Where-Object {$_.IsSystemObject -eq "False" -and $_.SecurityLevel -ne "Safe_Access"}).Count | Should be 0 .......
Line 97 is checking for Symmetric keys in the Asymmetric key check, believe it should be
@(Get-DbaDbEncryption -SqlInstance $Instance -Database $Database | Where-Object {$_.Encryption -eq "Asymmetric Key" -and $_.KeyLength -LT 2048}).Count | Should -Be 0 -Because "Symmetric keys should have a key length greater than or equal to 2048"
Line 105 is checking for Asymmetric keys in the Symmetric key check, believe it should be
@(Get-DbaDbEncryption -SqlInstance $Instance -Database $Database | Where-Object {$_.Encryption -eq "Symmetric Key" -and $_.EncryptionAlgrothim -notin "AES_128","AES_192","AES_256"}).Count  | Should -Be 0 -Because "Asymmetric keys should have an encryption algrothim of at least AES_128"

#784

I fixed this in a PR


Add profile feature steamworks

Add Profile button visible in the lethal Admin panel to allow the host to add players as friends or ease future connectivity.
Apologies to the maintainer for visual studio messing with the deletions and additions. (CRLF to LF issues)
I will thoroughly test this, albeit for the time being seems to work just fine.

I don't really see a reason for adding this as it's already part of the base game. You can open someones profile by pressing the button next to their name in the pause menu (circled in red in the image), and as far as I know this still works with mods like BiggerLobby.

I don't really see a reason for adding this as it's already part of the base game. You can open someones profile by pressing the button next to their name in the pause menu (circled in red in the image), and as far as I know this still works with mods like BiggerLobby.

Unfortunately neither BiggerLobby nor MoreCompany have a working profile button.
Bigger lobby works, however messes up the index of the player, while MoreCompany entirely disables the feature.
From my perspective, an admin tool, once encountering a cheater should be able to locate his steam profile, and report aforementioned person.
Whether or not this is something you would like to include, is entirely up to you.

Ah I thought it did work, but seeing as it doesn't this would actually be something that's nice to have


[Bug]: js_run_devserver() leaks .sh in file name

What happened?
The js_run_devserver() target (on Linux) creates an executable file with the name %{name}.sh, which leaks the fact that this is implemented with Bash under the hood and forces any other scripts which call it via runfiles to add .sh to the filenames. This also likely complicates cross-platform support, since the filename is different for both.
$ bazel query --output build //common/testing:webdriver_test_server
INFO: Invocation ID: ed977d5a-d7cf-47bb-9839-fd2d99d08555
# /home/doug/Source/rules_prerender/common/testing/BUILD.bazel:268:24
js_run_devserver(
  name = "webdriver_test_server",
  tags = ["ibazel_notify_changes"],
  generator_name = "webdriver_test_server",
  generator_function = "web_resources_devserver",
  generator_location = "common/testing/BUILD.bazel:268:24",
  testonly = True,
  data = ["//common/testing:webdriver_test_resources"],
  entry_point = "@aspect_rules_js//js/private:js_devserver_entrypoint",
  enable_runfiles = select({"@aspect_rules_js//js/private:enable_runfiles": True, "//conditions:default": False}),
  tool = "//common/testing:webdriver_test_server_baked_server",
)

$ bazel build //common/testing:webdriver_test_server
INFO: Invocation ID: 9315b831-1936-4983-9a2e-14a064f1e6fa
INFO: Analyzed target //common/testing:webdriver_test_server (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //common/testing:webdriver_test_server up-to-date:
  dist/bin/common/testing/webdriver_test_server.sh
INFO: Elapsed time: 0.207s, Critical Path: 0.01s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action

Version
Host is WSL2 in Windows 10.
$ bazel --version
bazel 5.1.1

Using @aspect_rules_js version 1.16.0 via WORKSPACE.
How to reproduce
load("@npm_rules_js//:http-server/package_json.bzl", http_server_bin = "bin")

http_server_bin.http_server_binary(
    name = "server",
)

js_run_devserver(
    name = "devserver",
    tool = ":server",
)

# Omitting runfiles setup...
sh_binary(
    name = "executor",
    srcs = ["executor.sh"],
    data = [":devserver"],
)

# Error: `devserver` does not exist in runfiles.
$(rlocation devserver)

# Works.
$(rlocation devserver.sh)

Any other information?
Ideally the binary file should always be generated with the same name as the target. This is more intuitive to use and more accurately abstracts away the underlying implementation so it can be changed without breaking existing API contracts.
Fund our work

[ ] Sponsor our open source work by donating a bug bounty

Hmmm. Adding .sh has been our standard practice for rules with bash wrappers. js_binary creates an <name>.sh entry point as well. I do see your point that having the binary rule entry point named the same as the target is nice. @alexeagle wdyt?

Hmmm. Adding .sh has been our standard practice for rules with bash wrappers. js_binary creates an <name>.sh entry point as well. I do see your point that having the binary rule entry point named the same as the target is nice. @alexeagle wdyt?

We had no .sh extension at first on js_binary but then added it back later to make migrations easier

Ironically it made the migration a little harder in this case: https://github.com/dgp1130/rules_prerender/commit/c0065dc2598be72120abb9ecc9bea8af20aed1ff.
That might be specific to js_run_devserver() though, and calling that as a subprocess is probably on the rarer side. Compatibility with rules_nodejs might be better for now. Maybe this is more of a v2 breaking change to consider?

I'll queue it up for 2.0. It may be breaking for some users so may as well throw it in with a release where breaking changes are expected.

Fixed on the 2.x branch and to be released with rules_js 2.0


Where are the downloads?

Hi,
Could you tell me where are the files downloaded in my phone? I click on download but can't find the files.
Thank you.

Hi,
do you have enabled the storage permission for the app?
If yes, the download should open when clicking the download notification and be in your download

do you have enabled the storage permission for the app?

Hum, sorry for this. You were right I didn't enable the storage permission...

No problem. Actually the app should ask you to allow the storage permission, but thats not working currently


Extend custom parser interfaces to include pre-insertion cleanup methods to support reindexing

The current custom parser direction requires devs to build their own indexer methods. This provides flexibility to allow custom datasets to be introduced. However, since we are using gorm with relational models, we will want to provide the interfaces with a pre-index callable method to allow cleaning up old datasets if they exist. This will be called before custom dataset insertions during reindex.

Cancelling this one for now. Each custom parser interface for messages and blocks contains a Index* method that contains the entire parsed dataset. This method can be used to do pre-insertion cleanups if needed. We can revisit this if it becomes a burden to force the functionality to be implemented in the Index* method.


Tarjan's Algorithm

Describe the algorithm/code
I want to add Tarjan's Algorithm  .
Please assign me this task under Hactoberfest 2023 tag.
Do you want to work on this feature?

[x] I am willing to implement this feature.

Hi @pankajsingh92533 ! 👋🏻
You can start working on this issue! Do let me know if you need any help. ✨

i have written code with proper explanations.
Please review it..

Create a PR.
I will check but make sure that the code is accepting dynamic input


Add a test for the scan status within SubmissionViewModel.kt

Checklist

[x] Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
[x] If this PR comes from a fork, please Allow edits from maintainers
[x] Set a speaking title. Format: {task_name} (closes #{issue_number}). For example: Use logger (closes # 41)
[x] Link your Pull Request to an issue (if applicable)
[x] Create Work In Progress [WIP] pull requests only if you need clarification or an explicit review before you can continue your work item.
[x] Make sure that your PR is not introducing unnecessary reformatting (e.g., introduced by on-save hooks in your IDE)
[x] Make sure that your PR does not contain changes in strings.xml (see issue #72)
[x] Make sure that your PR does not contain compiled sources (already set by the default .gitignore) and / or binary files

Description

This PR adds a test for the scan status of the SubmissionViewModel. It tests whether the scan status changes to the right status after starting and when the validateAndStoreTestGUID gets a valid or invalid guid passed.

Is anything missing here so this can be merged?


Update request and request-promise

These address several security vulnerabilities:
https://nodesecurity.io/advisories/525
https://nodesecurity.io/advisories/577
https://nodesecurity.io/advisories/566

Closing all issues since this repo is being archived and replaced by office-toolbox.


Make build work on Mono

PCL profiles are a problem on Mono. The build we run on Linux should exclude them. see: https://github.com/aspnet/KRuntime/issues/277

@glennc still applicable?

Closing because we are not planning to make changes to this or it is no longer needed.


Rename a branch on the github.com web UI

when working on github we get all kind of automation which creates branches and works on our repo.
since I dont own most of this automation I have no influence on the naming of the branches.
e.g. Dependabot creates branch names like dependabot-npm_and_yarn-simplebar-5.0.3 which contains . characters, which are a problem for our further processing.
would it be possible to add a feature to refined github, so we will be able to rename a branch on github.com directly, without the need of a clone/fork and the git cli commands etc...?

Please also send this feature request to GitHub<EMAIL_ADDRESS>

Done

Renaming isn’t a safe operation, any PRs open on that branch will be disconnected, not transferred as one would expect.
I’d prefer #2895 instead. One more click (“Delete”), but less broken expectations.


Using compound types for keys and action data

Here are some examples:
struct vlan_aware_mac_t {
    bit<12> vid;
    bit<48> mac_addr;
}

table dmac {
   key = {
        vlan_aware_mac : exact;   /* vlan_aware_mac_t vlan_aware_mac = { hdr.vlan_tag.vid, hdr.ether.dmac}; */
   }
   . . .
}

(Yes, I do understand that not all match types would work, but both exact and ternary certainly would work nicely)
struct nexthop_t {
    mac_addr_t dmac;
    PortId_t port;
}

action set_nexthop(nexthop_t nh) {
    hdr.ethernet.dst_addr = nh.dmac;
    standard_metadata.egress_spec = nh.port;
}

I cannot see anything in the spec that prohibits that, but the compiler is definitely not happy: it insists that the key fields must have scalar types and that action data must be too.
Any thoughts?
Personally, I think that if we want to allow people to write reusable code, both would be quite nice, but at the same time the implications (esp. to the API) are significant.

These are bmv2 limitations, the spec allows that.

Thanks, @mbudiu-vmw. That's good.
I am afraid that the checks might've ended up in the common frontend code, though.
@antoninbas  -- what do you think P4Runtime-wise? Are you interested?

Can you provide a complete, runnable example so folks can more easily
verify and debug with p4test?
On Tue, Mar 10, 2020 at 4:53 PM Vladimir Gurevich<EMAIL_ADDRESS>wrote:

Thanks, @mbudiu-vmw https://github.com/mbudiu-vmw. That's good.
I am afraid that the checks might've ended up in the common frontend code,
though.
@antoninbas https://github.com/antoninbas -- what do you think
P4Runtime-wise? Are you interested?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/p4lang/p4-spec/issues/829?email_source=notifications&email_token=AAOCFUXNFGRHXSUUVPWOF4DRG2SDVA5CNFSM4LFHTSZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEONDLXA#issuecomment-597308892,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOCFUTIAE5PR5UP3QVGYMLRG2SDVANCNFSM4LFHTSZA
.

@jnfoster -- Given that the compiler does not  seem to support that yet and neither do the APIs, I can provide only a theoretical example.
This is more like a forward-looking thing -- I am trying to decide what to do with the APIs,  and how to write more modular/reusable code (if you remember my previous discussions on a  related topic).

The compiler has no problems supporting this on targets that offer this capability.

OK, let me check internally, but my feeling was that the errors were coming from the frontend:
simple_l3_struct.p4(146): [--Werror=type-error] error: Key hdr.ipv4.dst_addr field type must be a scalar type; it cannot be struct ipv4_addr_t
        key = { hdr.ipv4.dst_addr : exact; }
                ^^^^^^^^^^^^^^^^^
simple_l3_struct.p4(129): [--Werror=legacy] error: Action parameter data has a type which is not bit<>, int<>, bool, type or serializable enum
    action send(send_t data) {
                       ^^^^

The first error is from the typeChecker, which is indeed in the front-end. I guess that the idea is that keys can have multiple fields, so there is no point allowing a key which is a struct: you can create fields for each struct field.
We can certainly add some syntactic sugar to allow structured-valued keys; the most important question is what happens to the control-plane API for this case.
The second error is from the p4 runtime serializer.

Attached is a complete example that tries to use a struct variable as a table key field, and p4test with no bmv2 back end nor P4Runtime API back end gives the indicated error message:
$ p4c --version
p4c 1.2.0 (SHA: 62fd40a0)

$ p4test try-struct-as-table-key.p4
try-struct-as-table-key.p4(72): [--Werror=type-error] error: Key s1 field type must be a scalar type; it cannot be struct my_struct1_t
            s1 : exact;
            ^^

try-struct-as-table-key.p4.txt

Thanks, @mbudiu-vmw .
The point is that if this is allowed and supported and makes sense (from the standpoint of practical development) then we can push the APIs to support that (e.g. by allowing fields of the type struct).  Ultimately, I think this will be helpful, although I understand that there will be work involved.

The P4Runtime API versions up through 1.1 made an explicit design choice, probably starting around early 2018 (I don't recall exactly when), to limit it to table key fields and action parameters with type bit<W>, or a few other very similar things (see the complete list in Section 21 "Known Limitations of Current P4Runtime Version" if you are curious -- https://p4.org/p4runtime/spec/v1.1.0/P4Runtime-Spec.html#sec-architecture-specific-table-extensions ) in order to get the first version out the door more quickly.
It is well known by the P4API working group members how to generalize this -- "just" change some of the Protobuf messages contents/formats.
The main decision point in doing this is: should it be done in a backwards compatible way, or should it be allowed to break backwards compatibility?
If it is done in a backwards compatible way, there is a software engineering concern that the message formats, documentation, and parts of the P4Runtime implementation code will contain cases for the current bit<W> restriction, while also handling the new more general types, side by side.
If it is done in a backwards incompatible way, then special cases for supporting bit<W> can be eliminated, keeping only the more general handling of a large set of P4_16 value types.  The main down side there are the software engineering and system deployment concerns of dealing with two incompatible versions of the API, where the older version 1.x would not disappear for some time after 2.x was introduced, and both would need to be supported for some unknown time.
Others in the P4 API working group would be better to ask what they think is the best way to go.  Me, I personally lean towards the "maintain backwards compatibility" as the lesser of two annoyances, but I'm not implementing that code :-)

@jafingerhut  -- thanks! That's what I suspected.
My view is fairly simple: if there is a language feature that is useful, it's probably better if the control plane API supports it :)  Given that there are talks about big new change(s) in P4Runtime, it might make sense to put it on the radar (that's why I was mentioning @antoninbas before). As you can see, I am looking at other stuff, such as type annotations, etc. that I believe will lead to better control plane APIs and tools.
For now, the important things for me is to make sure that the spec is supportive (it is) and that the compiler front-end is supportive (looks like not quite yet). If P4Runtime folks decide to get onboard -- great, but that's independent, since there are other control plane APIs I need to worry about :)

@vgurevich I don't know the implementation details of p4c here terribly well, but note that at least some ways of implementing this in p4c would 'flatten' the struct into its separate fields before generating the control plane API.  If that approach was taken, no control plane API changes would be needed to support structs, because they would just be the separate fields as far as the control plane API was concerned.  You do get into questions of what the names of those fields ought to be by default, then, e.g. should it be "mystructA.field1", "mystructA.field2", "mystructA.nestedStructB.fieldX", "mystructA.nestedStructB.fieldY", etc.?
The other primary alternative is to "keep the structs around" in p4c's intermediate representation, at least up to the point that the control plane API is generated.  Then you need more general type support in the control plane API(s).

@jafingerhut -- correct. As @mbudiu-vmw said, it will be mostly syntactic sugar, but very useful one.
But it is important not to flatten early, in my opinion :) or at least provide a choice. I would prefer the second option therefore.

Note that this "not flattening too early" is very similar to the P4runtime translation annotation on type types.  You don't want the types to be forgotten by the compiler before the control plane API is generated, even if they are forgotten in the compiler's internals after that point.  Again, I do not know all of the ins and outs and possibilities here, so something better than what we have today for P4runtime translation is almost certainly possible -- just not always easy to see which ways avoid gotchas and corner cases.

@jafingerhut -- precisely.

Closing this one in favor of #836. It will be linked from there.


Added Biomes O' Plenty support for Farming Station

Added Biomes O' Plenty saplings to FarmersRegistry.java. Modified TreeHarvestUtil.java and TreeFarmer.java because Biomes O' Plenty trees don't inherit from vanilla Minecraft's BlockLeaves. Also added support to harvest drops from BoP apple and persimmon trees. Modified ItemDarkSteelAxe.java where it called methods in TreeHarvestUtil class. Cleaned up commit history and closed previous pull request.

No action on this, closing. Might revisit myself.


Missing cluster-info ConfigMap in TenantControlPlane

On latest image, the cluster-info ConfigMap in TenantControlPlane is missing:
$ kubectl --kubeconfig=${TENANT_NAMESPACE}-${TENANT_NAME}.kubeconfig get cm -A
NAMESPACE         NAME                                 DATA   AGE
default           kube-root-ca.crt                     1      47m
kube-node-lease   kube-root-ca.crt                     1      47m
kube-public       kube-root-ca.crt                     1      47m
kube-system       coredns                              1      47m
kube-system       extension-apiserver-authentication   1      48m
kube-system       kube-root-ca.crt                     1      47m
kube-system       kubeadm-config                       1      47m
kube-system       kubelet-config-1.23                  1      47m

On the release image:
$ kubectl --kubeconfig tenants-fks-tnt-00.kubeconfig get cm -A
NAMESPACE         NAME                                 DATA   AGE
default           kube-root-ca.crt                     1      18d
kube-node-lease   kube-root-ca.crt                     1      18d
kube-public       cluster-info                         1      18d
kube-public       kube-root-ca.crt                     1      18d
kube-system       calico-config                        4      18d
kube-system       coredns                              1      18d
kube-system       extension-apiserver-authentication   1      18d
kube-system       kube-proxy                           2      18d
kube-system       kube-root-ca.crt                     1      18d
kube-system       kubeadm-config                       1      18d
kube-system       kubelet-config-1.23                  1      18d

As a side effect, it is not possible to join a worker node because this cm is necessary (I can't get ride of it)

The bug has been introduced with #7 and #40 has the same side effect.

latest image is older than #7, from docker hub and quay.io (And they are not aligned)
Current master branch produces the configmap. I have pushed the image I am testing (from master) to docker hub.

A new release candidate has been pushed with the current status of master branch:
https://hub.docker.com/layers/kamaji/clastix/kamaji/v0.0.2-rc0/images/sha256-f7dab8b6d778c5e0d73df4ada08b46376d54fa6849ca0564f7b2554d2b07fdd2?context=explore

@merlindorin could I ask you to perform a test again in order to test if it fixed your issues?

@prometherion, "it works!" 👍

The first release was a bit of a rush, glad it's ok now!
Closing the issue, feel free to open it back for any case!

Would it be possible to update the latest image OR change the getting started guide so it doesn't use the latest tag? I'm hitting this issue now when following the guide.
This is the guide I'm referring to. And here it is using the latest tag (maybe also other places).

Thanks for pointing this, @lentzi90.
Honestly, I'd like to avoid using latest since it's an anti-pattern and doesn't provide immutability, especially when dealing with debugging.
We have to improve the documentation and the overall visibility, I'll try to catch up on everything in the upcoming issues.
tl;dr; just aligned latest with the last stable release


[UI] Vmware deploy-as-is instances are not receiving the properties values

ISSUE TYPE

Bug Report

COMPONENT NAME
UI

CLOUDSTACK VERSION
4.17, 4.18

CONFIGURATION
Register a VMware vApp template selecting the option 'Read settings from OVA'. Deploy VM and input property values
OS / ENVIRONMENT
Vmware vApps containing properties
SUMMARY
vApp properties values are not passed to the deployVirtualMachine API after the Vue3 upgrade on: https://github.com/apache/cloudstack/pull/5151
STEPS TO REPRODUCE
- Register a vApp template containing vApp properties on CloudStack, selecting the 'Read setting from OVA' option
- On the Deploy Instance wizard, select the template and complete the values for the vApp properties
- Deploy VM

EXPECTED RESULTS
The deployVirtualMachine API includes the properties set

ACTUAL RESULTS
The properties parameter is not set for the deployVirtualMachine API

Fixed by #8072


Catch manifests up with latest GCE/Kubernetes requirements.

Add a metadata.name field
Shorten port names to 15 chars or less.

LGTM


Light mode on mobile has bad contrast between profile text and background

Profile section text (i.e. name, job, location) have bad contrast with background gradient (black on light-ish green and darker blue

).

Fixed! Thanks for reporting @maxeisen <3


Add Bobabeam docs

:clipboard: Add associated issues, tickets, docs URL here.
Overview
Describe what your Pull Request is about in a few sentences.
Add Bobabeam docs
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Add Bobabeam docs
Add deployment files

Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.

@java-spaces can you proof read pls?


Traverse recursively condition tree components

This should fix jailbreaking dependencies inside conditionals.

This has fixed Agda build for me on nixpkgs master and GHC 7.8

Ouch, I had't done enough research before making a PR and saw https://github.com/peti/jailbreak-cabal/commit/99eac40deb481b185fd93fd307625369ff5e1ec0 now. I guess that means this change is out of question then! Maybe we can mention this in the README to prevent future misunderstandings?

There's also https://github.com/peti/jailbreak-cabal/issues/7 and https://github.com/peti/jailbreak-cabal/pull/4. This issue seems to come up frequently. I guess we should document the rationale for the current behavior in the readme or the source code.

What about a simple comment, like this?

Very good. Thank you!


GUI Issues?

I followed the instructions and downloaded the latest version, but I can't find anybody who has this same problem, let alone even having a recording of installing it. Can you help me? Thanks.
-S4ndst0ne

Tried the Mediafire link, didn't work.


Inertia Testing does not load eager loaded relations properly

Hey guys,
for managing permission and roles we are using the awesome laravel-permission package from Spatie.
When we send a User-Model to the frontend (we are using react), we want roles.permissions to be attached always.
Therefore we added the following to our User-Model:

If we inspect with React Devtools in Frontend, we see the following:

Now we wrote the following test to assert, that this is happening properly:

But the test fails and says the following:

And if we dd() the response we see this:

Somehow the permissions are not loaded with the roles but seperate in the test. Is this functionality missing for the Inertia-Testing feature or am I doing it wrong somehow?
Any help appreciated!
Greetings Felix

Did you check both documentations? Did you remove 0 and tested it again?
How can we reproduce this?

How you pass the object to frontend? Do you use api resource which is created by php artisan make:resource.
It is possible to that converting the object to json may be differs when it is handled by laravel.
As I see, in your frontend root object which is auth is an object. But in your backend it is an array.

you can use API Resource

Hey there,
We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel to open up a new issue if you're still experiencing this problem.


I am facing issue while upgrading Laravel 5.4 from 5.3

Recently i have upgraded laravel 5.4 from 5.3 and i have gone through the upgrade guide. I face below issue, Please help me out.
[2018-05-09 13:16:07] production.ERROR: ErrorException: Illegal offset type in unset in /opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Container/Container.php:1035
Stack trace:
#0/opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Container/Container.php(1035): Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(2, 'Illegal offset ...', '/opt/lampp/htdo...', 1035, Array)
#1/opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Container/Container.php(205): Illuminate\Container\Container->dropStaleInstances(Object(Closure))
#2/opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Container/Container.php(311): Illuminate\Container\Container->bind(Object(Closure), NULL, true)
#3 /opt/lampp/htdocs/MYPROJ/vendor/lucasromanojf/laravel5-pdf/src/Ignited/Pdf/PdfServiceProvider.php(38): Illuminate\Container\Container->singleton(Object(Closure))
#4/opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(574): Ignited\Pdf\PdfServiceProvider->register()
#5/opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php(75): Illuminate\Foundation\Application->register(Object(Ignited\Pdf\PdfServiceProvider))
#6/opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(549): Illuminate\Foundation\ProviderRepository->load(Array)
#7/opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/RegisterProviders.php(17): Illuminate\Foundation\Application->registerConfiguredProviders()
#8/opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(208): Illuminate\Foundation\Bootstrap\RegisterProviders->bootstrap(Object(Illuminate\Foundation\Application))
#9/opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(162): Illuminate\Foundation\Application->bootstrapWith(Array)
#10/opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(146): Illuminate\Foundation\Http\Kernel->bootstrap()
#11/opt/lampp/htdocs/MYPROJ/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(116): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#12/opt/lampp/htdocs/MYPROJ/public/index.php(52): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#13{main}

Your stack trace clearly suggests that the problem lies in the lucasromanojf/laravel5-pdf package.
This repo is for tracking bugs in the framework, not for supporting third-party packages. Please post on the forums or slack channel for help with ugprading your app.


react to new registration type for semantic tokens

Fixes #397
Reference commit for latest vscode client: https://github.com/microsoft/vscode-languageserver-node/commit/bb85e80617c7f0cb64dad9dad852219e2da7c4c9
LSP reference: https://github.com/microsoft/language-server-protocol/issues/1107

cc @anthony-c-martin

cc @NTaylorMullen @ajaybhargavb

Merging in for now, no real breaking changes except for the new client that causes issues.


[BUG] UI: volume creation date is invalid

Describe the bug
In Longhorn UI, created column displaying  Invalid date
To Reproduce
Steps to reproduce the behavior:

Create a volume
2, Check Created column

Expected behavior
Created column shouldn't display Invalid date for volume, it should display volume creation date and time
Log

You can also attach a Support Bundle here. You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment:

Longhorn version: v1.2.x
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: rke2

Number of management node in the cluster: 1
Number of worker node in the cluster: 3

Node config

OS type and version: Ubuntu 20.04
CPU per node: 4
Memory per node: 8
Disk type(e.g. SSD/NVMe): ssd
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster: 1

Additional context
Add any other context about the problem here.

It looks like the backend returning the created date, so the frontend just represents it via the below function.
http://github.com/longhorn/longhorn-ui/blob/b246299732815ce1cf996ee277d5974aeb34d950/src/utils/formatDate.js#L5-L12
cc @kaxing

For the reference, I am not able to reproduce with longhorn-manager latest master branch(20211005-2pm) and v1.2.x branch(ui:84c0f41)

I did see this issue on @meldafrawi test system but it disappeared after a while, maybe cache issue or different representation from websocket/api response. I did not look into this at the time I saw it.

cc @smallteeths

Same issue here with 1.2.2

Stumbled upon same bug, but it appears to me only in firefox. Chrome works fine.

Fixed in this issue https://github.com/longhorn/longhorn/issues/3230.


Export the node data to an xml

Hi I am trying to use angular-tree-component for editing an xml, so that it can allow users to update it on UI. My Question is will we be able to export the node data to an xml, is that possible using angular-tree-component api? Once I am done adding a new node and have a export button where I can export as a file/xml . Kindly suggest.

Hi,
you can use the models API to iterate over the nodes and get all the data you need.
Check out ITreeModel and ITreeNode here:
https://angular2-tree.readme.io/docs/api


disable offset_start and offset_end in IncludeGuiMetaData

Add new parameter to IncludeGuiMetaData to disable the creation of offset_start and offset_end because they would be only valid in the main Stream.
This has to be used in :

everything that creates a new BytesIO Stream (cs.Tunnel, cs.Prefixed, cs.FixedSized, cs.NullTerminated, cs.NullStripped, cs.RestreamData, ...)
when changing from byte to bit level, which also creates a new BytesIO Stream (cs.Restreamed & cs.Transformed)

fixed in next release


Deploy Checklist: Expensify.cash 2021-03-18

Release Version: 1.0.2-80
Compare Changes: https://github.com/Expensify/Expensify.cash/compare/1.0.2-79...1.0.2-80
This release contains changes from the following pull requests:

[ ] https://github.com/Expensify/Expensify.cash/pull/1879

cc @Expensify/applauseleads

@Expensify/applauseleads ignore, this is still just a test


Use Http/2 by default in Kiota

Fix issue https://github.com/microsoft/kiota-http-dotnet/issues/231

Thanks for catching this @dev-tony-hu!
I think you just need to accept the license policy and we should be good to go here.

accept

@microsoft-github-policy-service agree [company="AvePoint"]
Options:
(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"

@microsoft-github-policy-service agree company="AvePoint"
@microsoft-github-policy-service agree

@microsoft-github-policy-service agree company="AvePoint"

@dev-tony-hu the command you issued was incorrect. Please try again.
Examples are:
@microsoft-github-policy-service agree

and
@microsoft-github-policy-service agree company="your company"

@microsoft-github-policy-service agree company="AvePoint"

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree company="AvePoint"


Feature/xinnanli/naming empty string

Critical Changes
Changes
Fixes household naming bug when all the data in a contact is empty. Use comma instead of "and" to connect names from different contacts
Issues Closed
Fixes #553
New Metadata
Deleted Metadata
Testing Notes
(In addition to other household naming regression testing)

Go to HEDA setting page
Enable automatic household naming. Choose household as default account model, "Other" as Household Account Name Format. Fill in the other format with: {!Salutation} {!FirstName} Family.
Create a contact: Salutation = "Mr.", FirstName = "TestFN", LastName = "TestLN"
Make sure the household account name is Mr. TestFN Family
Create another contact under the same household account: Salutation = "", FirstName = "", LastName = "TestLN2"
Make sure the household account name is still Mr. TestFN Family
Update the second contact to: Salutation = "Ms.", FirstName = "TestFN2", LastName = "TestLN2"
Make sure the household account name is now Mr. TestFN and Ms. TestFN2 Family
Create another contact under the same household account: Salutation = "Mrs", FirstName = "TestFN3", LastName = "TestLN3"
Make sure the household account name is now Mr. TestFN, Ms. TestFN2 and Mrs. TestFN3 Family
Make sure other household account naming testing works too

While the results are inconsistent with the AC's in the PR, the extra "and" has been removed. Therefore, after discussion with team, we'll be closing this Work Item / PR and opening a "Spec/Spike" to determine expected behavior for HH naming (and by extension Administrative Account naming) in terms of syntax, added name order, etc. See testing notes : https://salesforce.quip.com/4QHyA3dabxqK#CUIACAfM5fo

Hi @juliesnow, I noticed this PR's release note had not been reviewed yet. Would you mind take a look please? Thank you! :)

Hi @juliesnow, I added a bullet point to the release note, fyi


merge latest development release into master

Coverage remained the same at 100.0% when pulling c6b11f5a1dd3aca3ab9adf0c1a5faeac4acce769 on develop into eee6bf7bb1832f7c90a006c97cf3f562877dc1e5 on master.


Windows and Bash

Hi! Thanks for rpassword! Currently using it in a cross-platform CLI application.
When on Windows, using cmd or Powershell, all is well. Similarly, macOS and GNU/Linux with bash work fine.
When running on Windows via bash, e.g. Git Bash, calls to read_password_from_stdin fail because there's no Windows console available.
I've used the following really hacky workaround, but I'm curious if you have any ideas for a better solution. I did try enabling the Unix module when compiling rpassword on Windows, but libc for Windows naturally doesn't implement many of the required functions or constants, e.g. tcsetattr, so it fails to compile.
Here's the hack which spawns bash to read the password, for anyone else that may be stuck on this issue:
            #[cfg(windows)]
            let windows_git_bash_shell = env::var("SHELL").unwrap_or_default();

            #[cfg(not(windows))]
            let windows_git_bash_shell = "".to_string();

            if windows_git_bash_shell.ends_with("bash.exe") {
                // For some reason, this fails unless read is done twice.
                let password = Command::new(windows_git_bash_shell)
                    .stdin(Stdio::inherit())
                    .arg("-c")
                    .arg("{ read -s password || read -s password; } && echo -n \"$password\"")
                    .output()
                    .ok()
                    .and_then(|output| str::from_utf8(&output.stdout).ok().map(|s| s.to_string()))
                    .unwrap_or_default();

                self.output("\r\n");

                password
            } else {
                rpassword::read_password().unwrap_or_default()
            }
}

Sorry for the slow response @conradkdotcom. To confirm, yes, this happens on master.

Hello @longshorej ! Are you still interested in getting this fixed ? Otherwise, I'll have to close this issue, as unfortunately, I don't have time to invest in Windows support for this.

I'll close it - the workaround above has us moving forward. I don't think that should belong in library code though, better to keep the hacks in the applications :smile:


Reflections

a. What went well
Lauren: We were all very clear about which user stories we were working on and regularly communicated our status on the user stories to make sure that everyone knew what everyone else was doing and no one was stepping on each other's toes. We worked on merge conflicts as a team and explained important pull requests to each other before deciding on which prs to merge first and which code to keep in merge conflicts.
Alex: Assigning the tasks, helping each other when blockers met, code reviews for pull requests done in group while only one person is responsible for merging the requests, get good at git commands. The app idea was delivered.
Ellen: Biggest take away was the importance of advanced planning, communication and project management through through tools like trello. It not only streamlined the project process, but also minimized risks or merge conflicts. Also our work flow and allocation worked effectively.
b. Workflow to reproduce for future projects
Lauren: I will definitely apply our work with Trello to keep track of our progress and the way we communicated to each other during class and after class. Also making sure that every new idea is kept track of in a user story that is added explicitly to Trello.
Alex: Planning save development time, monitoring progress in Trello gives and idea of what is done and what is not, morning standups with reviewing pull requests planning for the day
Ellen: Definitely would like to repeat the planning and time/project management processes in future projects. Also frequent commits, pushes and merges (after team review)!
c. What did not go so well
Lauren: There was a moment where we were not getting the Google authentication working on our different machines, but it was a quick fix once we realized we had different Google client ids and secrets on our local machines!
Alex: We had only one blocker - issue with env keys for Google authenticator. Sleep more!
Ellen: Nothing major, but technical issues surrounding google o-auth and heroku.
d. Prevention for future projects
Lauren: In the future, it'll be helpful to make sure everyone's ENV files look the same, since that is one file that is not getting pushed/pulled through GitHub
Alex: Double checking
Ellen: I think this won't be an issue as we learned what were the issues!

Allela Ltd. (Lauren, Ellen, Alex)
Heroku https://alella-theme-generator-49b5c35126f2.herokuapp.com/
PROJECT PASSED
Instructional Glow: README, minimalist styling works very well, auth, meaningful CRUD application, UI is clean and polished.
Instructional Grow: Centering users on index page, Small media query pushes content down and nav should be at top for mobile views (tablet and smaller -<960)
Chat API query should be enhanced to only provide light font colors if the background is dark. Code readability suffers on night-mode themes.


Project does not build when configured payload-plugin-oauth plugin

I'm using node v16.17.0, Payload v1.6.26 and payload-plugin-oauth v0.2.0.
This is the configuration from the ~/app-payload/src/payload.config.ts file:
import { buildConfig } from 'payload/config';
import { oAuthPlugin } from 'payload-plugin-oauth'
import path from 'path';
// import Examples from './collections/Examples';
import Users from './collections/Users';

require('dotenv').config();

export default buildConfig({
  serverURL: 'http://localhost:3000',
  admin: {
    user: Users.slug,
  },
  collections: [
    Users,
    // Add Collections here
    // Examples,
  ],
  plugins: [
    oAuthPlugin({
      clientID: process.env.CLIENT_ID,
      clientSecret: process.env.CLIENT_SECRET,
      authorizationURL: process.env.OAUTH_SERVER + '/oauth2/default/v1/authorize',
      tokenURL: process.env.OAUTH_SERVER + '/oauth2/default/v1/token',
      callbackURL: process.env.SERVER_URL + '/authorization-code/callback',
      scope: 'openid profile email',
      async userinfo(accessToken) {
        const response = await fetch(`${process.env.OAUTH_SERVER}/oauth2/default/v1/userinfo?access_token=${accessToken}`);
        const user = await response.json();
        return {
          sub: user.ID,

          // Custom fields to fill in if user is created
          name: user.display_name || user.user_nicename || 'Naamloos',
          email: user.user_email,
          role: user.capabilities?.administrator ? 'admin' : 'user',
        }
      },
    }),
  ],
  typescript: {
    outputFile: path.resolve(__dirname, 'payload-types.ts'),
  },
  graphQL: {
    schemaOutputFile: path.resolve(__dirname, 'generated-schema.graphql'),
  },
});

After running the npm run build command, it returns the error:
ERROR in main
Module not found: Error: Can't resolve './src' in ' ~/app-payload'
resolve './src' in ' ~/app-payload'
  using description file:  ~/app-payload/package.json (relative path: .)
    Field 'browser' doesn't contain a valid alias configuration
    using description file:  ~/app-payload/package.json (relative path: ./src)
      no extension
        Field 'browser' doesn't contain a valid alias configuration
         ~/app-payload/src is not a file
      .js
        Field 'browser' doesn't contain a valid alias configuration
         ~/app-payload/src.js doesn't exist
      .json
        Field 'browser' doesn't contain a valid alias configuration
         ~/app-payload/src.json doesn't exist
      .wasm
        Field 'browser' doesn't contain a valid alias configuration
         ~/app-payload/src.wasm doesn't exist
      as directory
        existing directory  ~/app-payload/src
          using description file:  ~/app-payload/package.json (relative path: ./src)
            using path:  ~/app-payload/src/index
              using description file:  ~/app-payload/package.json (relative path: ./src/index)
                no extension
                  Field 'browser' doesn't contain a valid alias configuration
                   ~/app-payload/src/index doesn't exist
                .js
                  Field 'browser' doesn't contain a valid alias configuration
                   ~/app-payload/src/index.js doesn't exist
                .json
                  Field 'browser' doesn't contain a valid alias configuration
                   ~/app-payload/src/index.json doesn't exist
                .wasm
                  Field 'browser' doesn't contain a valid alias configuration
                   ~/app-payload/src/index.wasm doesn't exist

webpack 5.76.3 compiled with 1 error and 1 warning in 275 ms

Any idea what could be going on?

At the suggestion of a Discord group member, I added the line of code below to the ~/app-payload/src/payload.config.ts. This allowed executing the project construction command without error.
admin: {
     user: Users.slug,
     webpack: (a) => a, // line of code added
   },

But when running the npm run dev command, it opens a blank screen with the below error in the browser console.
Uncaught TypeError: __webpack_require__(...).config is not a function
     at ./src/payload.config.ts (payload.config.ts:7:25)
     at __webpack_require__ (bootstrap:24:1)
     at fn (hot module replacement:62:1)
     at fn (hot module replacement:62:1)
     at ./node_modules/payload/dist/admin/Root.js (Root.js:8:42)
     at __webpack_require__ (bootstrap:24:1)
     at fn (hot module replacement:62:1)
     at fn (hot module replacement:62:1)
     at ./node_modules/payload/dist/admin/index.js (index.js:10:32)
     at __webpack_require__ (bootstrap:24:1)

Is there anything else I can do?

Hmm, that could be because I'm adding some dependencies to resolve.alias:
axios: false,
'passport-oauth2': false,
'express-session': false,
passport: false,

Do you use axios in the frontend? I removed the alias in v0.3.0 so it shouldn't be a problem anymore.
v0.3.0 has been refactored to not need a special password field. It may result in a slightly different user token tough.

hello im using node 18.12.1 "payload": "^1.8.3", "payload-plugin-oauth": "^0.3.1", i added the webpack: (a) => a, // line of code added
and when i try to build the app, it just stays building the app forever

I'm unable to reproduce, can you post a minimal example repository?


search for text feilds with like operator

@nolanlawson
hi
i need to find docs based on some fields and i need the 'contains' or 'like' operator.
how can i achieve that with find plugin?

solution to your problem is $regex, see the couchdb docs

This issue was moved to pouchdb/pouchdb#6253


FR: native handling of MappingProxyType

https://docs.python.org/3/library/types.html#types.MappingProxyType
Currently in order to use that one must set https://docs.pydantic.dev/dev-v2/usage/model_config/#arbitrary-types-allowed
Selected Assignee: @davidhewitt
Selected Assignee: @hramezani
Selected Assignee: @samuelcolvin

You could probably implement this all in the pydantic side if you wanted to. I don't think (not sure) that there's a C API for this stuff so it's unlikely to be orders of magnitude faster in Rust or anything like that. Let me know if you want pointers on how you'd do it in Python.

There actually is a C API and a PyO3 PR (unfinished) to support mappingproxy at https://github.com/PyO3/pyo3/pull/2435
Given I assume we will just call types.MappingProxyType(validated_dict) as a post-processing step, the amount of effort to move this to Rust may not be worth the minimal perf benefit. If someone was really interested in writing this in Rust I wouldn't stop them of course 😉

If the goal is to convert all dicts to mappingproxys, I'll just note that the recent changes to allow a custom GenerateSchema might be sufficient? Not sure if we have exposed the ability to override dict_schema or just str_schema at this point.

My PR in the other repository inadvertently closed this, can you please re-open?

done.

If the goal is to convert all dicts to mappingproxys, I'll just note that the recent changes to allow a custom GenerateSchema might be sufficient? Not sure if we have exposed the ability to override dict_schema or just str_schema at this point.

This didn't get merged in the end, we're still working on how to make it possible.


feat: Add support for Neotest

https://github.com/nvim-neotest/neotest/
:wave: I'm switching to the Neotest runner and instead of adding theme support to my own set up I figured I'd add it to the plugin directly. I matched the colors roughly to those used by default in the plugin. I'd appreciate any suggestions to make the color selections better align with the intentions of the theme and anything else needed to merge (e.g., do I need add to the transparency_highlights list as well?). Thanks!

Thank you for adding support for a new plugin! I trust your judgement on the colours but if you want to share a screenshot I can perhaps give feedback. For the transparency highlights, these shouldn't be necessary for this PR—there only seems to be one new highlight that has a background colour anyways :)

Hi @mvllow,
I think it looks pretty good and with some of the recent changes aligns with colors from other rose-pine plugins. But please let me know if you have any suggestions. A few screenshots below. The "has the expected schedule" is a focused test; the "schedule geocode properties" is a marked test; neotest-rspec is the adapter/runner. Thanks!
w/ passing tests

w/ tests running

w/ failing tests

I love, wonderful job. I don’t think I’d change anything


Allow target to be determined based on request

very generic in readme but lets you use stuff like https://www.npmjs.com/package/http-proxy-rules

moved to #8


Change button in the navbar to be route-aware and make logo clickable

In Landing page, button should be Dashboard not logout and logo should be clickable to redirect user back to landing

lgtm


Groups in Profiles disappearing visually if gamemode is set to All

My normal page (when gamemode is ctb):

Allmode:

enjoy your banner till this bug lasts

https://github.com/Osekai/osekai/blob/849020e1ef038b9b1000bb52c0812ec5ab3bd9d8/profiles/js/functions.js#L260-L262
Is this code really necessary? If it removed, this problem should be solved.


Create .gitattributes

As suggested in https://github.com/caskroom/homebrew-fonts/pull/391#issuecomment-141640776.
If there are no objections, might as well add it to every repo.

Need to add .gitattributes to test/layout_test.rb.

Thank you. Added.

Any reason on this not being merged yet?

No, just that I forgot about it. Thank you for the bump.


Charging controller

Sorry to ask that, but I wish to know if the symbol besides controller 1 means that it is charging. I want to know if there is any way to charge the controller on PC. And just for the record, when a bunch of [?????] shows instead of the bar, what is the meaning? I'm sorry for my bad english

Yes, that is a primitive charging animation. If it cycles to fill the bar it means it's charging. If there are question marks it could mean 2 things: the charge value couldn't be read, or your console encoding is not supporting the characters used for the animation.
Cheers

Thank you very much, Nefarius. This is such a great work of yours! Conrgrats, man!

See #18


[stable/traefik] Confusing Prerequisites for Traefik chart

The README for the Traefik chart lists the following under "Prerequisites", among others:

You are deploying the chart to a cluster with a cloud provider capable of provisioning an external load balancer (e.g. AWS or GKE)
You control DNS for the domain(s) you intend to route through Traefik

However, I don't see how these are true..
For the first point it seems Traefik can be the loadbalancer itself since that is what it is after-all. The README later mentions that if you use it behind a LB and want the client's real IP you should enable Proxy protocol on both ends, but that doesn't make a cloud-provider LB a prerequisite.
ACME only requires control over DNS if using the dns-01 validator, if you use http-01 then you don't have to have full control over DNS, the record just has to point to your endpoint IP which is an obvious requirement. I see no reason that Traefik couldn't use http-01 validator on Kubernetes.
Please let me know if I missed something, but if not I'd be happy to make corrections in a PR.

knock knock


[chore] Add anchors to individual attributes in a markdown table #1041

This allows users to link directly to the attribute by its name.
Fixes #1041
Changes
The line  creates an anchor link for the attribute.
{{ attrs.name(attribute) | lower | replace(' ', '-') }}  ensures that the ID is in lowercase and any spaces are replaced with hyphens (-), making it a valid and consistent HTML ID.
This allows users to link directly to the attribute by its name.
The rest of the line {{ attrs.name(attribute) }} ensures that the attribute's name is still displayed as before, but now it’s wrapped in an anchor..
Merge requirement checklist

[ ] CONTRIBUTING.md guidelines followed.
[ ] Change log entry added, according to the guidelines in When to add a changelog entry.

If your PR does not need a change log, start the PR title with [chore]

[ ] schema-next.yaml updated with changes to existing conventions.

Should the "links" be clickable? Nothing happens to me, so not sure how one can get the "link" to link to it 🤔


Calling phone number fails with " Call end reason: code: 500, subcode: 511404"

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

cloned repo
cd communication-services-web-calling-tutorial/Project
npm install
npm run build
npm run start
entered my personal cell phone number into "Destination Phone Identity or Phone Identities" input field
entered another personal cell phone (my wife's number) into "Alternate Caller Id (For calling phone numbers only)" input field
clicked Place Call
I can't find any guidance on how to enter phone numbers.  Should I include region code like +1 for US or not?  Neither seems to work, and including +1 vs 1 doesn't seem to help.

Any log messages given by the failure

Red error alert box appears with text: "Call end reason: code: 500, subcode: 511404"

Expected/desired behavior

Phone call completes

OS and Version?

Windows 10.

Versions

Node version 12.13.1.  npm version 6.12.1

Mention any other details that might be useful

Thanks! We'll be in touch soon.

+1

"Alternate Caller Id (For calling phone numbers only)" is the phone number associated with your azure resource connection string.
"Destination Phone Identity or Phone Identities" is the phone number you are calling to


New patch bugs/balance feedback

You are probably aware of these but the Raincoat rework and Shrine player count scaling options are broken.
Also, I've done a few more runs and I think some of the healing items are too strong, Seed and Scythe in particular. I felt pretty much unkillable with like 40 hp/s on kill from scythe by stage 5 and the 5% base lifesteal from Seed. I think Seed would be fine with just a number nerf down to like 3-4% (+2% per stack) or something, but I thought Scythe would be cool with regen on crit instead of on kill. For instance like 1-2 h/s on crit for a couple seconds, using the same stacking cap as it has for the on-kill currently. Also probably doesn't need the base 5% crit chance anymore since it gives crit on kill.
Anyway I don't think the patch broke anything else, cheers

Currently working on fixing the mod for the latest update, it came at a bad time since I was in the middle of some other major changes that I haven't been able to thoroughly playtest.

Leeching Seed is getting changed so that it only scales off of initial damage (damage used for proccing) instead of the final total damage dealt, so no more Crit/Crystal synergy since it ended up being too much.
I'll probably leave scythe as-is for now. It's in a weird spot where it heals a lot but doesn't feel like it's healing a lot. If I were to swap it back to heal-on-crit, I'd just go with the Vanilla behavior for the sake of simplicity rather than making it conditional. The 5% crit chance is mainly there since people are used to taking Scythes+Predatory for passive crit, and I want to keep that behavior.

Also I dont think the moon pillar drop chance configs are working right. I'm trying to make them only drop lunar items and I have the overwrite chance set to 100, but I only get white items.

I'll take a look at that.

Forgot to mention this in the patchnotes, but the Lunar bug is fixed now. Been changed from an overwrite chance into just a normal drop chance.


⚠ Bofrost.be has degraded performance

In 369c2a1, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1574 ms

Resolved: Bofrost.be performance has improved in b399876 after 8 minutes.


Fix a PHP Invoker bug where spaces in folder name would kill it.

Codecov Report

Merging #5 into staging will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           staging     #5   +/-   ##
======================================
  Coverage      100%   100%
======================================
  Files            9     10    +1
  Lines           65     69    +4
======================================
+ Hits            65     69    +4

Impacted Files
Coverage Δ

src/invoker/PhpInvoker.js
100% <100%> (ø)
:arrow_up:

src/index.js
100% <0%> (ø)

Continue to review full report at Codecov.

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


Hosting Provider

I am considering initially hosting Bookmark on AWS using the following:

2x T2 micro for serving sites
1x T2 micro for Bookmark Mercury
1x M3 medium for ElastiCache
1x M4 large for MySQL
S3
Elastic Load Balancing
As Bookmark grows we can scale by increasing the number of T2 micro instances and upgrading the MySQL and ElastiCache monolith...

Database sharding may be considered depending on daily peak expected load.

A much cheaper alternative would be to use Linode:

2x Linode 2GB ($10/mo each) for serving sites
1x Linode 1GB ($10/mo) for Bookmark Mercury
1x Linode 8GB ($40/mo) for MySQL
1x Linode 2GB ($10/mo) for caching (may be scaled up if we need it)
1x Linode NodeBalancing ($20/mo)

Total price: $100/mo

OVH is also feasible but we would need multiple nodes in different data-centers. I'm skeptical of due to OVH's spotty availability.

NodeBalancers are capable of hitting 10k concurrent requests according to Linode. I think that is more than the upper limit of what we should initially expect.

Add another $40 a month for ElasticSearch.

We may not need NodeBalancing if we use a single Varnish as our load balancer for backend hits. Multiple caching nodes will of course need to be load balanced.

We will need an additional host for Bookmark's auth server.

We also need another host for a shared redis store. See #36


Switch from json to nuon

As suggested on discord, nuon is just a superset of json, there will be no significant difference but the whole project will be even more nu :)

Solved by https://github.com/skelly37/nupac/pull/16


spirv-val: not validating matching RelaxedPrecision in passing arguments to formal parameters

From https://github.com/KhronosGroup/glslang/issues/2293.
Glslang is fixed (theoretically) now for this, such that a mismatch requires going an extra layer of copying.  From the PR:

There are 3 dimensions here: precision setting on the calling argument, precision setting on the formal parameter, and pass-by-value versus pass-by-address.

I'm not sure what if any checks the validator is applying, but it seems like it should be invalid to pass a either by value or by address a mismatch in RelaxedPrecision.

First, let's establish this is not a "before HLSL legalization case", which relaxes some rules in anticipation of successfully running HLSL legalization passes.
Ok, then the validator checks that each argument to the function call has the same type as the corresponding parameter type  in the called function's type.
OpFunctionCall says:  "Argument N is the object to copy to parameter N of Function."
OpFunctionParameter says : "This instruction must immediately follow an OpFunction or OpFunctionParameter instruction. The order of contiguous OpFunctionParameter instructions is the same order arguments will be listed in an OpFunctionCall instruction to this function. It is also the same order in which Parameter Type operands are listed in the OpTypeFunction of the Function Type operand for this function’s OpFunction instruction."
I take the "object to copy to parameter ..." to mean we use the same rules as for OpCopyObject, which is: "Result Type must equal Operand type. There are no other restrictions on the types."
The RelaxedPrecision decoration is not a part of the type, so there should be no obligation or expectation to require a function call operand and corresponding function call parameter match in that decoration.

I can see a legalistic reading of the spec saying this is not required, but I'm questioning if that's the right answer.
If it's not the right answer (e.g., if it is better that the calling arg and receiving formal param have the same RelaxedPrecision decorations), then I agree both the specification and the validation should agree on that.  I had not yet convinced myself which way the specification says, but am asking to consider having both validation and specification want these to match.
This does relate to improving what happens with other transforms when the decorations don't match, and I'm pursuing an improvement in the ecosystem here that impacts multiple components.
Glslang is now fixed to have these match, to help the goals of using SPIR-V.
On the specification litigation side:

"object to copy to parameter ..." to mean we use the same rules as for OpCopyObject

I don't see that as a given, we certainly don't say those two are equivalent, but even if so, I'm not sure what the rules would be for OpCopyObject.  What we do say is a copy from an intermediate to memory can sanitize the RelaxedPrecision decoration, but I don't see parameter passing "copy" as necessarily being a round-trip through memory, and that's the issue (maybe for OpCopyObject too).  The spec. might simply have not gotten this clear, but the issues around it are real.

To put this in more accurate perspective, I fixed two levels of problems in glslang:

The more serious one, reported as an issue, was in unnecessarily upgrading a RelaxedPrecision value to a non-RelaxedPrecision value, on the way to passing it as an argument to a function.  This can be a performance hit, and it would be nice if there were tools that caught, reported, and/or corrected such things.

The secondary one was in removing mismatches in precision between the calling argument and the receiving parameter, because that just seemed wrong, and possibly could be a correctness issue, which I assume is almost always currently masked by all the inlining everyone does.

So, 2 is what this SPIRV-Tools issue is about, though there is certainly room for tools ("SPIR-V tools"?) to help with 1.  I agree it's not 100% straightforward to prove what's right or wrong here, but at the time of posting the issue wasn't questioning at all that if a caller called with one precision and a callee expected another, that that would be bad.  I can see other interpretations are possible, but perhaps less explicit/performant.


minification middleware

Just for fun and see how slow it could be:

JavaScript
CSS
Others?

I tried a minifyJsWithEsbuild middleware but instead of having to add esbuild as a dependency, I prefered to create 2 middlewares that could be combined to to it:

check if responseBody is of a given content-type https://github.com/hsablonniere/hititipi/pull/65
transform the response body as a string https://github.com/hsablonniere/hititipi/pull/66


Trigger a restart of the Drupal and/or Nginx pods when the configuration changes

Use hashing of the configmaps like in https://github.com/StatCan/charts/blob/master/stable/varnish/templates/deploy/varnish.yaml#L22 to trigger an automatic restart of the pods on configuration change.

@zachomedia this look right?