no realtime shadows using 3dio shader with Radeon or Intel Graphic Cards

reproduce:
open this scene https://appcreator.3d.io/JugHaX?m=e
on this device (or similar)

result:
shadow is only shortly visible before lightmap gets applied ( see screencast )
lightmap-shader--vs--shadow.zip
( written by frederic )

Update: just opened scene on same device but on Safari and there is no conflict. So issue seems to be combination with Chrome (version 60.0.3112.113 (Official Build) (64-bit))

works fine on [linux]{https://manjaro.org/} firefox and chromium
works fine on galaxy s8 firefox and chrome

probably a safari issue

all last-gen MacBooks seem to be affected

wip fix: https://github.com/archilogic-com/3dio-js/commit/dc4604cabe8db03c777409127b40505c8e0af153

@Aadjou and me sat down and debugged this through and we found out:

Three.js r71 had that problem
Three.js r87 and thus A-Frame do not expose this problem
The problem is triggered by any access to texture memory before shadow calculation
When we substitute our material with a THREE.MeshPhongMaterial it works just fine

The conclusion: It is a problem in our shader and we're comparing the shaders now to see what we're missing


[RFC] Add I/O error checking for start code searches

I'm not sure if the new API and error code is the best way or not. Comments welcome.

Globally, looks fine for me.
I guess there are existing nameless errors which could be assigned to LSMASH_ERR_IO.
It's ideal you replace with if existing. :)

Sure.
Do you want me to add such commits to this pull request, or shall this be merged first?

OK. I'll merge this first. Anyway thanks.

Closing as the patches have been merged.


Call to aws cli to write kubeconfig file fails with RC 255 and output 'name'

Describe the bug
The [start_all.sh](./kic-reference-architectures/pulumi/aws/start_all.sh ) script fails at the add_kube_config() function when the user has multiple k8 custom contexts. This fails on the CLI as well as in the script.
$ aws --profile f5 --region us-west-2 eks update-kubeconfig --name XXX
<- Snip ->
2021-06-23 13:17:12,792 - MainThread - botocore.retryhandler - DEBUG - No retry needed.
2021-06-23 13:17:12,829 - MainThread - awscli.clidriver - DEBUG - Exception caught in main()
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/awscli/clidriver.py", line 217, in main
    return command_table[parsed_args.command](remaining, parsed_args)
  File "/usr/lib/python3/dist-packages/awscli/clidriver.py", line 358, in __call__
    return command_table[parsed_args.operation](remaining, parsed_globals)
  File "/usr/lib/python3/dist-packages/awscli/customizations/commands.py", line 187, in __call__
    return self._run_main(parsed_args, parsed_globals)
  File "/usr/lib/python3/dist-packages/awscli/customizations/eks/update_kubeconfig.py", line 127, in _run_main
    config = config_selector.choose_kubeconfig(
  File "/usr/lib/python3/dist-packages/awscli/customizations/eks/update_kubeconfig.py", line 214, in choose_kubeconfig
    if loaded_config.has_cluster(cluster_name):
  File "/usr/lib/python3/dist-packages/awscli/customizations/eks/kubeconfig.py", line 67, in has_cluster
    return name in [cluster['name']
  File "/usr/lib/python3/dist-packages/awscli/customizations/eks/kubeconfig.py", line 67, in <listcomp>
    return name in [cluster['name']
KeyError: 'name'
2021-06-23 13:17:12,831 - MainThread - awscli.clidriver - DEBUG - Exiting with rc 255

'name'

To Reproduce
Steps to reproduce the behavior:

Create multiple contexts that are pointed to by the KUBECONFIG variable
Attempt to update the kubeconfig using the aws eks update-kubeconfig command.
The command will fail.
Unset the KUBECONFIG variable.
Re-run the command
The command will succeed and write to the default KUBECONFIG (~/.kube/config)

Expected behavior
The information for the new cluster should be added to the currently active context file.
Your environment

Version of the repo: Commit  32f08f9
Version of KIC: 1.11.1
Version of infrastructure tooling: Pulumi
Version of executing environment: Python 3.8
OS and distribution: PopOS 20.10
Details about containerization or virtualization environment: Bare Metal install

Additional context
None

This failure also will occur of the user does not have a default config file under ~/.kube.
Thought for the fix is to validate the kubectl environment and add the config file if necessary (with user acknowledgment) - this is likely only to affect users with multiple contexts so I think that this puts the bug squarely in the realm where people who are more versed with K8 and have complex configuration will encounter.

will be addressed by #80

Will be closed by #167

Closed by #167


awsebcli: fix build and update

Motivation for this change
awsebcli was broken after cement was updated, this PR fixes that and also updates it to the latest version.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Thanks!


Chinese Client 5.5 Release Opcode Configuration

{
"C2S_ActionRequest": "0x02e0",
"C2S_ActionRequestGroundTargeted": "0x0226",
"S2C_ActionEffect01": "0x0085",
"S2C_ActionEffect08": "0x00ff",
"S2C_ActionEffect16": "0x0110",
"S2C_ActionEffect24": "0x03dc",
"S2C_ActionEffect32": "0x03d5",
"S2C_ActorCast": "0x01e6",
"S2C_ActorControl": "0x008b",
"S2C_ActorControlSelf": "0x0190",
"S2C_AddStatusEffect": "0x02d5",
"Server_IpRange": "<IP_ADDRESS>/0",
"Server_PortRange": "1-65535"
}

Note that if you share the file name too, then I can include into the release zip files.

Oh I just saw your reply. The file name is "game.CN.2<IP_ADDRESS>0.0000.json". Thanks for your development!

Thank you! I've included the file into the release.

By any chance, do you know the IP address range of all 3(?) Chinese datacenters?

Sorry I don't know how to get those IP addresses. There are 3 servers and it seems that the previous addresses were included in #43 . Btw, why do we need those addresses if we can fill in "<IP_ADDRESS>" and the program could still work properly?

The other program for non-Windows players need the IP address range to figure out which opcode definition files to use. Also, I thought that other issue only got 2 IP address ranges instead of 3.

Here are the three servers "MaoXiaoPang"（猫小胖）, "MoGuLi" （莫古力）, "LuXingNiao" （陆行鸟）from top to bottom.

Thank you!


Custom Longhorn deployment page

Possible enhancements over the previous questions.yaml:

Ensure the system can only be deployed in longhorn-system namespace
Ensure there should be only one deployment of Longhorn in the cluster.
Support multi-cluster deployment with the same longhorn-system namespace.

Other than those, Longhorn is fine with the previous questions.yml implementation. The latest questions.yml (for pre v1.0.2 release), which contains all the customizable fields, is linked here.

#1 is done already. For this ticket only need to work on #2.

Seems like when installing longhorn again it does fail gracefully. So both 1 and 2 are resolved. 3 will just be taken cared of by Fleet.

Attempt to install Longhorn using cluster explorer then trying to install it again with cluster manager will not fail gracefully and might cause confusion to the user.
Steps to reproduce:

In Rancher v2.5 Cluster Explorer dashboard, add a new chart using
https://github.com/shuo-wu/charts branch dev-v2.5
Change the following images tags to Use latest v1.1.0-RC3 images, and deploy Longhorn

Switch to Cluster Manager Dashboard.
Add a new Catalog using the following repo  https://github.com/shuo-wu/charts branch master
Move Longhorn Namespace to System project.
Try to install Longhorn v1.1.0-RC2. Don't change the images tags to RC3

Result:

In Cluster Manager: Longhorn App Seems to be in Active State

In Cluster Explorer: In installed apps, a new longhorn-system app appear alongside with already existing longhorn and longhorn-crd apps.

@meldafrawi Can you try if we can install it in Cluster Manager first then Cluster Explorer?

Won't fix


[Lark Documents]  Can not browse to document

Extension – Lark Documents
Author: @tmk

Description
Can not navigate to the doc
Steps To Reproduce

Seach with query words, and the result appears
press enter for opening the document

The current behavior
Raycast window disappeared, then noting happened.
The expected behavior
Raycast window disappeared, browser opened the selected document.
Raycast version

1.32.1
Note
document's that its url has wiki word all failed, but which has docs or docx all succeeded.
https://bytedance.feishu.cn/wiki/wikcn*******
https://bytedance.feishu.cn/docs/doccn*******
https://bytedance.feishu.cn/docx/doxcn*******
My ByteDance email<EMAIL_ADDRESS>

I've tested and it works, could you please provide an approach to reproduce this bug?
BTW, I did not receive the notification because my username is tmkx

@tmkx Sorry about the name, I found the bug has been fixed at recently version. Thank you for your replying.


Event priority and persistence in Objective-C?

It appears there is no way to set event priority and persistence (MSFlagsPersistenceNormal, MSFlagsPersistenceCritical) when using Objective C.  The "flags" option is missing from [MSAnalytics trackEvent:withProperties:].  Is this correct?  Or is the documentation simply lacking.

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

ID: ea43ae40-337d-83b4-8129-85ff1a8c6ede
Version Independent ID: d37ccc38-a4bc-5368-9b58-8720995f8bc2
Content: App Center Analytics for iOS - Visual Studio App Center
Content Source: docs/sdk/analytics/ios.md
Service: vs-appcenter
GitHub Login: @elamalani
Microsoft Alias: emalani

@iiAtlas I'll ask the PM to respond. Also, please keep in mind that App Center support is provided directly from within the App Center portal. Any time you need help, just click the blue chat button in the lower-right corner of any page and our dedicated support team will respond. For additional information, see the App Center Help Center.

Thanks! Sorry if this was the wrong place to comment..

@iiAtlas No, it isn't, no worries. If the docs are lacking, this is the place to ask. I just pointed that out in case you were in a hurry for the answer as support is probably faster than a docs response.

@jwargo Excellent!  Thank you for your wonderful support!

@iiAtlas You can set event priority and persistence in Objective-C as well. Here is the doc link -
https://docs.microsoft.com/en-us/appcenter/sdk/analytics/ios#event-priority-and-persistence

@elamalani The documentation you've provided (and which I commented on) is only showing Swift code.  The relevant method does not seem to exist in Objective-C!

@iiAtlas You can switch the language to Objective-C by using the dropdown on the upper right of the docs page.  Here is the code snippet:

Hi @elamalani , thanks for the tip on how to change the language -- that helps!  I was just going to comment on how the method [MSAnalytics trackEvent: withProperties: flags:] did not exist in the latest AppCenter SDK version, then I checked and noticed I was on 1.6.1 rather than the latest 1.14.  I've since found the method.
Thank you both!


[ISSUE#1534] Fix Removing an overridden User ID doesn't remove the overridden User ID in conversations

Fixes #1534
Description
This PR fixes the issue when removing an overridden User ID doesn't remove the overridden User ID in conversations
Changes made
In order to handle this as clean as possible, we added a basic configuration file for all the conversations in which there's an stable userId, that'll be used when there's not userId  set from the Settings Page.
By doing this, there's an inmutable set of data and mantains consistency through sessions.
Functionality changes
To implement this feature we made the following changes:

Add new file conversationDefaults that has the userId and documentId stable values.
Update appSettingsEditor.tsx file to set the userGUID as empty instead of null when the UserID from the Settings' Page is disabled.
Update emulator.tsx file to import conversationDefaults values and use it instead of props.document.userID that is not being overriden on stableId variable declaration.

Hey guys! I am pushing the fix of the button right now, but we are still trying to reproduce the ID issue, we will push that asap.

@tonyanziano we are not being able to repro the issue, is what we are showing in this gif ok? Are we missing anything?

After, doing a wipe & a clean build of everything, I can no longer repro the issue using the steps I provided.
However, I was able to produce some incorrect behavior by starting a new live chat session very quickly after submitting my custom user id.
I'm not able to produce the same behavior on the most recent nightly.

Hi @tonyanziano , after running a few tests, we were able to reproduce this behavior that you are mentioning. We believe that it's not caused by the userid itself but by the restart conversation functionality. If it's ok, we'll create a new separate issue to solve it.

@denscollo That sounds reasonable to me!


PHP: 5.6
MariaDB: 10.0.24
Fixed database session update.

Thanks, @malkesh !


Remove File class

Deprecate and then remove File class.
The deprecated commits can be (were) used to check dependent projects for uses of File or the deprecated Filesystem methods that used File. Once they were updated, it became safe to remove the File class and associated methods.
Reference: #904

Be careful leaving [[deprecate]] attributes hanging around. MSVC treats any use of features marked deprecated in this way as an error in all cases instead of a warning like the standard suggests. It's good for enforcing a "do not use, this will be removed in the future" notation but there better be an alternative in place before marking the old one deprecated or the feature will become unusable in Visual Studio.

That's ultimately why I just outright removed stuff in the next two commits. You may notice the failed build after the first two commits deprecating stuff.

Resolved merge conflict with recently merged change.


i can not this library import my project

Hi my friend;
Thank you for this library.
i use Keil 5 and STM32F030
but i can not import this library..
can you help me?
Regards....

Hi @enrique15241524,
I have written this library for a low power project of mine, so I included support for a STM32L1 device originally as an example. You can find in commit 421a5c760d4ca736ee5f318db306a5fe73e6eafa a SPI class for STM32F0 devices which I backported to this repository from another project. Please note that I did not test this class in combination with this library, so there might be communication issues. Also, this library has a focus on the RFM69 part and tries not to support all STM32 families, variants and libraries. The latter part should be done by the user/developer because he knows his hardware best.
As to importing the library... Sorry, I cannot help you there. I willingly did not include any project files or Makefiles because there are so many IDEs, toolchains and configurations out there and I cannot support them. Try to provide the functions I referenced in the "Usage" part in the README and use the SPI class for STM32F0 devices.
Kind regards,
André


feat: toggle

I added a reverse modifier to reverse the display order. Now you can have the label on the left too, i'm pretty sure that will be required at some point.


generate black image

when i use StableDiffusionControlNetPipeline,  Sometimes I get black images. But when I reduced the number of steps to 3, I obtained an image.
May I ask how to solve this problem and reduce the generation of black images.

new


Type check rule expr during parsing to fix incorrect error line number

Fixes #2014

@fabxc
Can you take a quick look at this fix for issue #2014.
Essentially the bug was caused by type checking after all the parsing had completed which would result in the lexer pointing to the end of the file rather than the line where the parse error was actually detected.
I fixed the issue by type checking during parsing rather than afterwards, however it now always reports the correct line number +1 when a parse error is encountered. (For example, if the line with the parse error is on line 4, it'll now report line 5 etc.)
I’ve written a bit of a workaround to circumvent this by moving the lexer back one line when these errors are detected but I was wondering if you had any ideas as how to handle it in a better way?
I can elaborate further on the nature of this issue and what I did if need be.

Is this still relevant with the new rule format?

I quickly tested with 2.0 and this still appears to be an issue.
E.g.
groups:
- name: alert.rule
  rules:
  - alert: InstanceDown
    expr: up == 0
    for: 5m
    labels:
      severity: page
    annotations:
      description: '{{ $labels.instance }} of job {{ $labels.job }} has been down
        for more than 5 minutes.'
      summary: Instance {{ $labels.instance }} down
  - alert: InstanceUp
    expr: increase(prolematic-expr[5m]) > 0
    for: 1m
    labels:
      severity: page
    annotations:
      description: '{{ $labels.instance }} of job {{ $labels.job }} has been down
        for more than 5 minutes.'
      summary: Instance {{ $labels.instance }} down

Produces the error:

level=error ts=2017-12-01T14:39:02.305129605Z caller=manager.go:487 component="rule manager" msg="loading groups failed" err="group "alert.rule", rule 1: could not parse expression: parse error at char 41: binary expression must contain only scalar and instant vector types"

Which reports the incorrect rule and incorrect character position.

That looks like zero-based numbering, so it is correct. We may be able to make it a bit clearer though.

Tested with the same error in what would be rule 0 which resulted in same error.

I'll open a PR improving this error message next week to include the name of the alerting/recording rule.

This is obsolete.


Document the font-end codebase of MDN Web Docs

This is currently underway in this project and can be viewed at:
https://mdn.github.io/mdn-fiori/
This will cover(not finite):
General

Code style
Editor configuration

CSS

Best practise (cross pollinate with other teams on this)
Syntax standard for both CSS and SaSS
Documentation of linting rules we follow

JavaScript

Best practise (cross pollinate with other teams on this)
Syntax standard
Documentation of linting rules we follow

HTML

Best practise (cross pollinate with other teams on this)
Syntax standard

Frontend Workflow

General documentation of the front-end tool chain.

Components
Common components found in the MDN Web Docs code base with:

A live example of the module
The required HTML, CSS and JS as applicable

Tasks

[ ] Make a back-up of the currently documented work before merging the Storybook PR
[ ] Create issues for components
[ ] Define typography
[ ] Define colour scheme
[ ] Break components down using Atomic Design principals

Given the large size estimate, could this issue be converted to an epic, and decomposed into issues of <=5 days each?

Yup, that makes total sense.

@schalkneethling is this issue still applicable or redundant based on the new tasks we added?

@schalkneethling is this issue still applicable or redundant based on the new tasks we added?

Redundant. Closing.


Update ActiveMQ and JSM supported versions

Description
The ActiveMQ version compatibility is not clearly stated in [1]
Possible values for parameter.jms_spec_version does not include 2.0 in [2]
[1] https://mi.docs.wso2.com/en/latest/install-and-setup/setup/brokers/configure-with-activemq/
[2] https://mi.docs.wso2.com/en/latest/reference/synapse-properties/transport-parameters/jms-transport-parameters/
Version
4.3.0/ 4.4.0

Support for JMS 2 needs to be tested and verified as a separate effort. This will be tracked in https://github.com/wso2/product-micro-integrator/issues/3839

Fixed with below PRs:
4.3.0: #1190
4.4.0: #1196


plugin structure

Hello,
It's nice how powerlevel9k get's more and more custom segments.. but we should maybe think about outsourcing them into plugins or and working on a way to handle these plugins. This way we could keep our powerline clean and fast and adding more plugins would be more easy.
What do you guys think about this step?

Hi @shibumi !
Phew. That's some big topics you are talking about. ;) I'll try to answer them:
Speed
Well, the speed of the prompt is a product of the complexity of the base-functions (like printing colors, joining segments, printing icons, etc.) and the configured segments. Yes, all segments get slower if we add more base-functionality to the theme. And it gets slower if the user configures slow segments. We try to address that by calling the segments asynchronously.. Outsourcing the segments won't help at this point. If the user did not configure a specific segment, it won't slow down the prompt (it won't get called).
Simplicity of developing new segments
Is it hard to develop new segments (I might be blind on that spot)? Well, you need to know how to call $1_prompt_segment, but once you got that it is quite easy, no? It would be easier to handle each segment like custom segments, so that you just have to echo your contents. But that would clutter the information needed to draw the segment (like content, icon, colors).
Improving DX
@bhilburn and I talked about moving the segments into its own file (or even into separate files). But that is just cosmetics so that we don't need to scroll so much.. I am planning this to do after #344 gets merged into next. Before that it would get too complicated to keep the branches in sync.
Plugin architecture
A "real" plugin architecture would need a plugin manager. There are a few out there for ZSH, but we want to keep the segments as easy as possible to use, and as less dependencies as possible.
External repo
Do you have in mind to create a separate repo with custom segments? For now we try to merge as many as possible to upstream, so it would be easy to turn segments just on and off. IMHO the installation is currently complicated enough and that won't make it easier..

Hey @shibumi! Interesting idea!
So, generally, I'm definitely a fan of breaking the segments out of the primary powerlevel9k.zsh-theme file that they currently sit in. When @dritter and I met up in Brussels a couple of months ago, we discussed this exact point and definitely agree with you. As he mentioned, our plan is to give each segment its own file in the future. I think this will make it easier to add & maintain segments for everyone, including us!
Usually, when I think of 'plugins', I think of more than just what typically goes into P9k segment code. What did you have in mind for what would be included in a plugin? Is there anything there that would simplify the installation of segments?

Hello @dritter and @bhilburn,
I thought about this a lot and I think the best solution is just to put the segments into an own directory and we just load all files in the directory into our main script. This way a user could create a custom segment, move it to the segment-directory and it will be instantly loaded without editing his .zshrc file. A nice side effect would be that the user keeps his .zshrc clean, because all custom segments will be in an own directory.
Thats more or less what I thought about 'plugins'.

@shibumi - Oh, great idea! So, basically, P9k will glob a directory and pick up any segments in that directory. And yes, I really like the idea of being able to keep zshrc and the P9k source file clean.

Okay, this work has been picked up by @dritter in his async branch and some by @onaforeignshore, which is based on the async branch. Closing this issue to track progress in #476.


DnsRecordCname doesn't find record when target ends with '.'

Problem description
When putting a full FQDN value on property HostNameAlias, the Test function is not able to find an existing record.
Verbose logs
"[OBFUSCATED]:                            [[DnsRecordCname]DirectResourceAccess] A matching DNS resource record not found.",
"[OBFUSCATED]:                            [[DnsRecordCname]DirectResourceAccess] DNS record property 'Ensure' is not correct. Expected 'Present', actual 'Absent'.",
"[OBFUSCATED]:                            [[DnsRecordCname]DirectResourceAccess] DNS record is NOT in the desired state.",
"[OBFUSCATED]: LCM:  [ End    Test     ]  [[DnsRecordCname]DirectResourceAccess] False in 4.7190 seconds."

DSC configuration
DnsRecordCname 'alias'
        {
            Name   = 'alias'
            HostNameAlias = 'desiredfqdn.zonename.com.'
            ZoneName = 'zonename.local'
            Ensure = 'Present'
            DnsServer = 'obfuscated.zonename.local'
        }

Suggested solution
I think the issue is in line 57 of source/Classes/002.DnsRecordCname.ps1. The filter adds a '.' to the property HostNameAlias:
$_.RecordData.HostNameAlias -eq "$($this.HostnameAlias).
This makes the filter skip the good record.
The solution could be: determining first if the variable 'HostNameAlias' already is a proper FQDN with a dot in the end.
Operating system the target node is running
OsName               : Microsoft Windows 10 Pro
OsOperatingSystemSKU : 48
OsArchitecture       : 64-bit
WindowsVersion       : 2004
WindowsBuildLabEx    : 19041.1.amd64fre.vb_release.191206-1406
OsLanguage           : en-US
OsMuiLanguages       : {en-US}

PowerShell version and build the target node is running
Name                           Value
----                           -----
PSVersion                      5.1.19041.1023
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1023
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

DnsServerDsc version
Name         Version Path
----         ------- ----
DnsServerDsc 3.0.0   C:\Program Files\WindowsPowerShell\Modules\DnsServerDsc\3.0.0\DnsServerDsc.psd1

Thanks for reporting this! Happy to review a PR that solves this.


How to install ? http://alcatraz.io/ not available

How to install ?
http://alcatraz.io/ not available|
Copy and run project doesn't work as well.

+1

+1

+1


change productIndex text templete to a relative path

This PR is related to the issue 2114

Current coverage is 83.36% (diff: 100%)

Merging #2115 into master will not change coverage

@@             master      #2115   diff @@
==========================================
  Files           302        302
  Lines         15047      15047
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits          12544      12544
  Misses         2503       2503
  Partials          0          0

Diff Coverage
File Path

•••••••••• 100%
src/oscar/apps/search/search_indexes.py

Powered by Codecov. Last update 74c4e41...0d829a1

Thanks for the contribution.


VehicleWheel sinks into other colliders

Godot version:
3.2.3-stable
OS/device including version:
Linux
Issue description:
Anytime I use VehicleWheel, it sinks into the ground as seen here:

The wheel is made to fit the mesh like so:

Steps to reproduce:

Start Godot's truck town demo
Select the truck to drive
Observe it sink into the ground

Minimal reproduction project:
Truck town has it all over:
https://github.com/godotengine/godot-demo-projects/tree/master/3d/truck_town

Once confirmed, worth to mention it in https://github.com/godotengine/godot/issues/45333

Once confirmed, worth to mention it in https://github.com/godotengine/godot/issues/45333

Confirmed in 3.2.3 stable and 3.2.4 beta 6.
Bullet: wheels sink into the ground as described.
Godot Physics: the truck doesn't move forward.

Confirmed in 3.2.3 stable and 3.2.4 beta 6.
Bullet: wheels sink into the ground as described.
Godot Physics: the truck doesn't move forward.

Isn't limited to the truck, btw - a standard 4 wheel car also has the wheels partly sinking - I thought it was just a graphical glitch until I saw this report.

Isn't limited to the truck, btw - a standard 4 wheel car also has the wheels partly sinking - I thought it was just a graphical glitch until I saw this report.

Also present in Godot 3.4.

So, I previously thought this was an issue with the engine in 3.4 (currently using), but I think it may be the documentation that is incorrect on how to use it, and the default values may just not be relevant to the example project mentioned.
The answer to this question( https://godotengine.org/qa/83746/confusion-about-vehiclebody ) helped me solve my issues with not understanding how the wheels actually worked, and the clipping I experienced went away.
They suggest watching this video (https://www.youtube.com/watch?v=B5vE-nNszxA) where the settings are explained a bit more in detail. In particular it's noted that the 'y-value' of the wheel transform should be equal to the 'rest_length' to compensate for the fact that the center of the wheel is actually where the spring mounts to the vehicle, so the visual representation of the spring being drawn upwards is somewhat confusing as rest_length increases.
some other things which were an issue was too low of settings for max force, and travel being way too high (should be equal or lower than rest_length). And increasing stiffness helped the movement feel more smooth.
I suggest the documentation be looked into being made clearer. When I have time I'll try to look into how I might contribute to that, but if someone tackles it before me, grazie.

Whoa, thanks for saying that y of wheel should be equal to rest_length - I was one of the people mislead by the visual spring...

@qaptoR @Zireael07  I'm trying to replicate this but am not successful with it. Do you have an example project to share? Then I can apply the fix the Truck Town demo.

I don't have a minimal project, unfortunately. I think the issue went away at some point, or became so unnoticeable that I just don't notice it

Another more minimal MRP from #65739:
WheelTest.zip

Makes me wonder:
If the rest_length and the wheel's y value should always be equal, then what's the point of having to set both? It's unwieldy and error prone. Either the implementation should infer the rest_length from the y, or the rest_length should work on its own regardless of the y.
Unless I'm missing something...
Also, according to @BastiaanOlij, the suspension travel shouldn't be higher than the rest_length, so wouldn't it be easier to work with if the travel was a percentage instead?
As it is, changing the rest_length always requires that you also change two other values, which isn't ideal, in my opinion.

As I had the same Issue, I looked into the Code. It seems like the spring length is being calculated incorrectly. I made an own issue, as I originally thought this was just a visual glitch.

The original btRaycastVehicle https://github.com/bulletphysics/bullet3/blob/6bb8d1123d8a55d407b19fd3357c724d0f5c9d3c/src/BulletDynamics/Vehicle/btRaycastVehicle.cpp#L160 from Bullet does a raycast from the wheel's world position down to a point of distance raylen = suspension_rest_length + wheel_radius below the wheel. When the ray hits a point at distance hit_distance from its starting point, it makes sense to set suspension_length = hit_distance - wheel_radius. The PR https://github.com/godotengine/godot/pull/47412 restores that behavior from Bullet. It also simplifies the calculation of hit_distance and makes it a bit more precise, under the restriction in Godot that the raycast doesn't return the value of the line parameter param (the number between 0.0 and 1.0 that indicates where the raycast hit occurred), which was calculated manually instead. (In fact with this approach the whole param and depth variables can be removed and the method can be made to return void as the return value is never used.)
Now, the vehicle body code in Godot was changed 10 years ago in 1a2cb75 (around Godot 1.0) to move the starting point of the raycast up to a point of distance wheel_radius above the wheel (and keeping the endpoint the same as before, so increasing the length of the ray). My guess is that this was done to fix issues like what @Calinou reports in https://github.com/godotengine/godot/pull/47412#pullrequestreview-1910032892. The issue with that fix was that suspension_length is then computed incorrectly, as the meaning of hit_distance changed. To keep the hit_distance relative to the wheel's world position, it should be e.g. (as the only change on top of master):
diff --git a/scene/3d/vehicle_body_3d.cpp b/scene/3d/vehicle_body_3d.cpp
index c23032d3b9..36e428c648 100644
--- a/scene/3d/vehicle_body_3d.cpp
+++ b/scene/3d/vehicle_body_3d.cpp
@@ -425,7 +425,7 @@ real_t VehicleBody3D::_ray_cast(int p_idx, PhysicsDirectBodyState3D *s) {
                        wheel.m_raycastInfo.m_groundObject = Object::cast_to<PhysicsBody3D>(rr.collider);
                }

-               real_t hitDistance = param * raylen;
+               real_t hitDistance = param * (raylen + wheel.m_wheelRadius) - wheel.m_wheelRadius;
                wheel.m_raycastInfo.m_suspensionLength = hitDistance - wheel.m_wheelRadius;
                //clamp on max suspension travel

The difference is param * wheel_radius - wheel_radius = (param - 1.0) * wheel_radius. This is small when param is close to 1.0 (which was also made more likely by moving the ray up and increasing its length), but often visibly nonzero as in this issue. The patch above combines "move the ray up" (already in master) and "calculate the hit distance correctly", whereas https://github.com/godotengine/godot/pull/47412 undoes "move the ray up" but does "calculate the hit distance correctly".
The problem (probably) with the above patch is that hit_distance can be negative, which may cause weird physics behavior (maybe worth testing).
To resolve this issue I think somebody should look at how some popular implementation of a car with raycasts solves this problem, and implement it in Godot.

how some popular implementation of a car with raycasts solves this problem, and implement it in Godot.

Other than Bullet, I think you mean, as Godot's implementation is pretty much Bullet's...

Jolt has a pretty complete vehicle implementation which also has more features (such as gears and RPM), but it'll need to be core so it can be plugged in VehicleBody/VehicleWheel. We could technically have properties that have no effect when using GodotPhysics, but it's not ideal to have properties that have no effect until you install an extension (e.g. VideoStreamPlayer seeking).


set_region_of_interest too slow

Required Info

Camera Model
D400

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win7/10

Kernel Version (Linux Only)

Platform
PC

SDK Version
2.22

Language
C++

Segment

Issue Description
I set ROI for color sensor, it worked, but the set_region_of_interest function is a bit slow for me (140ms) , what should I do to improve it?
Here is part of my code:
pipeline *pipe;
rs2::config *s_cfg = new rs2::config;
s_cfg->enable_stream(RS2_STREAM_COLOR, 640, 480, RS2_FORMAT_BGR8, 30);
s_cfg->enable_stream(RS2_STREAM_DEPTH, 640, 480, RS2_FORMAT_Z16, 30);
rs2::pipeline_profile profile = pipe->start(s_cfg);
auto sensors = profile.get_device().query_sensors();
sensors[1].set_option(rs2_option::RS2_OPTION_ENABLE_AUTO_EXPOSURE, 1);
region_of_interest org_region= ((roi_sensor)sensors[1]).get_region_of_interest();
DWORD startTime = GetTickCount();
((roi_sensor)ros).set_region_of_interest(org_region);
DWORD endTime = GetTickCount();
printf("set ROI used time %d\n",endTime-startTime);

Hi @ChenXinThales   Your stated librealsense version is very old (SDK 2.22.0 from May 2019.  You may get some benefit if you update your project to a modern librealsense version if possible so that you can benefit from advancements made to the SDK since May 2019.
Also, I note that you use the term DOWRD.  Do you mean DWORD ?

Hi @ChenXinThales Your stated librealsense version is very old (SDK 2.22.0 from May 2019. You may get some benefit if you update your project to a modern librealsense version if possible so that you can benefit from advancements made to the SDK since May 2019.
Also, I note that you use the term DOWRD for the timer variables. Do you mean DWORD ?

Yes, I mean DWORD, I wrote it wrong. Besides updating SDK version, is there any other way to reduce setting ROI time?

I'm not sure that the method that you are using to measure start to finish processing time is the best one.  I would recommend trying std::chrono::high_resolution_clock.  The link below has a C++ example that demonstrates measuring the time of a process using this method.
https://github.com/IntelRealSense/librealsense/issues/4633
Also, if you are building librealsense from source code with CMake instead of a Windows SDK installer file, I would recommend using the term  -DCMAKE_BUILD_TYPE=release in the build statement if not doing so already, so that you build librealsense as a Release build that has optimizations instead of a Debug build.

Hi @ChenXinThales
Updating Auto-Exposure ROI will take couple of frames to kick-in. There is nothing I know you can do to speed it up. @agrunnet - do you have any suggestion?

I'm not sure that the method that you are using to measure start to finish processing time is the best one. I would recommend trying std::chrono::high_resolution_clock. The link below has a C++ example that demonstrates measuring the time of a process using this method.
#4633
Also, if you are building librealsense from source code with CMake instead of a Windows SDK installer file, I would recommend using the term -DCMAKE_BUILD_TYPE=release in the build statement if not doing so already, so that you build librealsense as a Release build that has optimizations instead of a Debug build.

I have updated SDK version to 2.36 and used std::chrono::high_resolution_clock to measure time, but the result was still about 142ms.

@ChenXinThales   Okay, thanks very much for trying the std::chrono::high_resolution_clock method.  At least you can have confidence in the accuracy of the time measurement, then.

Case closed due to no further comments received.


Reminder: After everything is finished, merge pipeline branch with the main branch for JSDocs update

Prerequisites:
Every other issues
Context
SInce direct push to the main branch is forbidden, the generation of JSDocs is pushed to pipelien branch.
Description of what's needed
Merge pipeline branch into the main branch. Remember to update the pipeline branch first with the main branch.
Location
Pipelne

Finished


Error in creating dbcontext

I tried using .net interactive and creating dbcontext from my sqllocaldb with this command:
#!connect mssql --create-dbcontext True --kernel-name eshop "Integrated Security=true; Initial Catalog=eShopDashboard; Data Source=(LocalDb)\\MSSQLLocalDB;"
it fails throwing this error:
Error: System.InvalidOperationException: Path to SQL Tools Service executable was not provided.
at Microsoft.DotNet.Interactive.ExtensionLab.MsSqlServiceClient.StartProcessAndRedirectIO()
at Microsoft.DotNet.Interactive.ExtensionLab.MsSqlServiceClient.Initialize()
at Microsoft.DotNet.Interactive.ExtensionLab.MsSqlKernel..ctor(String name, String connectionString)
at Microsoft.DotNet.Interactive.ExtensionLab.MsSqlKernelConnection.CreateKernelAsync(MsSqlConnectionOptions options, KernelInvocationContext context)
at Microsoft.DotNet.Interactive.CompositeKernel.<>c__DisplayClass26_0`1.<<AddKernelConnection>b__0>d.MoveNext() in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\CompositeKernel.cs:line 319
--- End of stack trace from previous location where exception was thrown ---
at System.CommandLine.Invocation.CommandHandler.GetResultCodeAsync(Object value, InvocationContext context)
at System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass19_0.<<UseMiddleware>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass23_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.CommandLine.Invocation.InvocationPipeline.InvokeAsync(IConsole console)
at System.CommandLine.Parsing.ParseResultExtensions.InvokeAsync(ParseResult parseResult, IConsole console)
at Microsoft.DotNet.Interactive.Commands.DirectiveCommand.InvokeAsync(KernelInvocationContext context) in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\Commands\DirectiveCommand.cs:line 35
at Microsoft.DotNet.Interactive.Kernel.<AddDirectiveMiddlewareAndCommonCommandHandlers>b__21_0(KernelCommand originalCommand, KernelInvocationContext context, KernelPipelineContinuation next) in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\Kernel.cs:line 134
at Microsoft.DotNet.Interactive.KernelCommandPipeline.<>c__DisplayClass6_1.<<BuildPipeline>b__3>d.MoveNext() in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\KernelCommandPipeline.cs:line 75
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.DotNet.Interactive.Kernel.SetKernel(KernelCommand command, KernelInvocationContext context, KernelPipelineContinuation next) in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\Kernel.cs:line 219
at Microsoft.DotNet.Interactive.KernelCommandPipeline.<>c__DisplayClass6_1.<<BuildPipeline>b__3>d.MoveNext() in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\KernelCommandPipeline.cs:line 75
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.DotNet.Interactive.Kernel.<>c.<<AddCaptureConsoleMiddleware>b__20_0>d.MoveNext() in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\Kernel.cs:line 101
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.DotNet.Interactive.KernelCommandPipeline.<>c__DisplayClass6_0.<<BuildPipeline>g__Combine|2>d.MoveNext() in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\KernelCommandPipeline.cs:line 76
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.DotNet.Interactive.KernelCommandPipeline.<>c__DisplayClass6_0.<<BuildPipeline>g__Combine|2>d.MoveNext() in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\KernelCommandPipeline.cs:line 76
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.DotNet.Interactive.KernelCommandPipeline.<>c__DisplayClass6_0.<<BuildPipeline>g__Combine|2>d.MoveNext() in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\KernelCommandPipeline.cs:line 76
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.DotNet.Interactive.KernelCommandPipeline.SendAsync(KernelCommand command, KernelInvocationContext context) in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\KernelCommandPipeline.cs:line 48

.Net Interactive version: 1.0.156101+537f46e89a1690a55315d805eb90a5877aff9de2
OS: Windows 10
Frontend: Visual Studio Code

Screenshots
If applicable, add screenshots to help explain your problem.

We're working on providing the SQL Tool Service executable via a NuGet package, at which point this will be a lot smoother, but for the moment you can do this to work around it:

Download and unzip the SQL Tools Service
Store the path to MicrosoftSqlToolsServiceLayer.exe in an environment variable called DOTNET_SQLTOOLSSERVICE

DOTNET_SQLTOOLSSERVICE

Thanks Jon for the help.
but now it's throwing another error: Access is Denied
I'm trying to connect to my (LocalDb)\MSSQLLocalDB whe I'm receiving this error. is there any limitation?
I tried with SQL Login and Integrated Security, same error for both:
Error: System.ComponentModel.Win32Exception (5): Access is denied.
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at Microsoft.DotNet.Interactive.ExtensionLab.MsSqlServiceClient.StartProcessAndRedirectIO()
at Microsoft.DotNet.Interactive.ExtensionLab.MsSqlServiceClient.Initialize()
at Microsoft.DotNet.Interactive.ExtensionLab.MsSqlKernel..ctor(String name, String connectionString)
at Microsoft.DotNet.Interactive.ExtensionLab.MsSqlKernelConnection.CreateKernelAsync(MsSqlConnectionOptions options, KernelInvocationContext context)
at Microsoft.DotNet.Interactive.CompositeKernel.<>c__DisplayClass26_0`1.<<AddKernelConnection>b__0>d.MoveNext() in F:\workspace\_work\1\s\src\Microsoft.DotNet.Interactive\CompositeKernel.cs:line 319

I haven't tried this with LocalDB.
@chlafreniere @corivera Any ideas?

Looks like that error is from failing to start MicrosoftSqlToolsServiceLayer.exe. That's before we open any connections.
https://github.com/dotnet/interactive/blob/main/src/Microsoft.DotNet.Interactive.ExtensionLab/MsSqlServiceClient.cs#L53

This should now work using the latest packages from our CI feeds:
#i "nuget:https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json"
#i "nuget:https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet5/nuget/v3/index.json"
#r "nuget:Microsoft.DotNet.Interactive.ExtensionLab,*-*"


Feature request: Add support for editing rich text

My current use case is a twitter post like edit box which highlights certain words with a different color. eg:

Duplicate of #12675


About the tunnel about IPV6 address

At present, calico does not support vxlan tunnel of ipv6, but ipv6 already supports vxlan tunnel. Is there any concern that calico does not support vxlan mode of ipv6 separately?

Closing as a duplicate of https://github.com/projectcalico/libcalico-go/issues/996
We don't yet support IPv6 in our encap modes. This is a known enhancement.


[W5.7][W17-2]Edric Teo Jin Kai

Work in progress

Good job @etjk.
Could modify helpCommand as well as you add a new command.


add more documentation to interpret-community website, including a contributing guide

More improvements to the interpret-community website, including:

Added a contributing and code formatting guide
Added LIME explainer to list of supported explainers
Fixed responsible-ai-toolbox link
Fixed width/size of several tables in the website, so they would be more readable

Codecov Report

Merging #522 (4430778) into master (6487b98) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 4430778 differs from pull request most recent head 0258a7f. Consider uploading reports for the commit 0258a7f to get more accurate results

@@           Coverage Diff           @@
##           master     #522   +/-   ##
=======================================
  Coverage   86.70%   86.70%
=======================================
  Files          62       62
  Lines        4063     4063
=======================================
  Hits         3523     3523
  Misses        540      540

Flag
Coverage Δ

unittests
86.70% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 6487b98...0258a7f. Read the comment docs.


Reaction.product now accepts a list of Species

Proposed changes
This PR fixes #702 by allowing users to give a list of Species for the product of a Reaction.
This gives us the ability to implement reactions of the type:
A + B <-> C + D
Need to merge #703 first since the tests use some of the functionality....
Types of changes
What types of changes does your code introduce to FESTIM?

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Code refactoring
[ ] Documentation Update (if none of the other choices apply)
[ ] New tests

Checklist

[ ] Black formatted
[ ] Unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

@jhdark this is now ready for review


Please provide a JSON example for --service-endpoint-configuration using an aks (azure kubernetes service)

I dont know which information is needed.

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

ID: 6ecb62a2-f74c-a539-d3a8-c8fde7c2de06
Version Independent ID: 5760936e-90a1-4129-6f6f-6dd4194bb73c
Content: az devops service-endpoint
Content Source: latest/docs-ref-autogen/ext/azure-devops/devops/service-endpoint.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

BTW, I just figured out that the --service-endpoint-configuration has the same content that the value send throw POST request on the DevOps Portal/Platform application when you are adding a service-connection from there.

devops

Someone have a example how to create a Kubernetes service connection from Azure CLI ?

I added a new issue with a payload example here https://github.com/Azure/azure-cli-extensions/issues/5385

@survivant You should be able to use the command like this az devops service-endpoint create --service-endpoint-configuration ./aksServiceConnection.json --org "https://dev.azure.com/issue1698Org" --project "Issue1698Project"
.
You can create a file using the request body mentioned in issue #5385. We will add the same in azure samples. (Adding different kind of json template in the actual document will be difficult).


Move watch loop of watcher to lifecycle manager

Blocked until

Watch stabilised
first iteration of watcher is working / integrated (e2e tested)
dependency between watcher to module-manager is resolved


addBabelPlugin with typescript project

I'm using Object.fromEntries with typescript and want to enable it during the babel transpile. I have the following config-overrides.js (most is commented out):
/* eslint-disable */
const path = require('path');
const { override: ccOverride, babelInclude, removeModuleScopePlugin, addBabelPlugin } = require('customize-cra');

module.exports = function override(config, env) {
  ccOverride(
    // removeModuleScopePlugin(),
    // babelInclude([path.resolve('src'), path.resolve(__dirname, '../../shared')]),
    addBabelPlugin('transform-object-from-entries'),
  )(config, env);
  // if (process.env.NODE_ENV !== 'production') {
  //   const rewireReactHotLoader = require('react-app-rewire-hot-loader');
  //   config = rewireReactHotLoader(config, env);
  //   config.resolve.alias = {
  //     ...config.resolve.alias,
  //     'react-dom': '@hot-loader/react-dom',
  //   };
  // }
  return config;
};

and am getting the following error:
Creating an optimized production build...
Failed to compile.

./src/index.tsx 1:535
Module parse failed: Unexpected token (1:535)
File was processed with these loaders:
 * ./node_modules/babel-loader/lib/index.js
 * ./node_modules/eslint-loader/dist/cjs.js
You may need an additional loader to handle the result of these loaders.
> import React from'react';import ReactDOM from'react-dom';import{setAppElement}from'react-modal';import winston from'winston';import*as Sentry from'@sentry/browser';import{winstonBaseLoggerOptions}from'../../../shared/utils/winston';import publicEnvs from'../../../shared/envs/public';import{isAxiosError,serializeAxiosError}from'../../../shared/utils/errors';import App from'./App';import*as serviceWorker from'./serviceWorker';(winstonBaseLoggerOptions);if(process.env.NODE_ENV==='production'){({dsn:publicEnvs.sentryDSN,environment:(),beforeSend:function beforeSend(event,hint){if(!event.extra){event.extra={};}if(hint&&hint.originalException&&typeof hint.originalException!=='string'&&(hint.originalException)){event.extra.axios=(hint.originalException);}return event;}});}('body');((App,null),('root'));// If you want your app to work offline and load faster, you can change
| // unregister() to register() below. Note this comes with some pitfalls.
| // Learn more about service workers: https://bit.ly/CRA-PWA

I don't think I'm doing anything special here.

nvm. I believe it was an issue with the babel plugn itself.


2 workers in 2 different queues - sharing the same key_suffix doesnt work

Hey, we have 2 different workers that should be throttled via the same key-suffix (contacting the same end service).
They run in different queues as one type of action is prioritised over a different type of action (so queues have different weights).
While they share the same key-suffix, it doesnt seem to work. That means, we are getting double the required concurrency:
E.g. Say our desired max concurrency for both workers was 10. We configured the same concurrency limit with the same suffix in both workers, and now we have 20 concurrent workers.
Any idea how to get them to play nice?

Can you please provide a simple example - bsically just want to see sidekiq_options and sidekiq_throttle options.

class Worker A
sidekiq_throttle({ concurrency: { limit: 10 },  key_suffix: 'some_lock' })
sidekiq_options queue: :queue_a
end
class Worker B
sidekiq_throttle({ concurrency: { limit: 10 },  key_suffix: 'some_lock' })
sidekiq_options queue: :queue_b
end

This configuration will make overall concurrency of 20. If you want  two workers to share configuration you need shared strategy for them:
# somewhere in initialization

Sidekiq::Throttled::Registry.add(:some_throttling_strategy, {
 :concurrency => { :limit => 10 }
})

# in workers

class WorkerA
  sidekiq_throttle_as :some_throttling_startegy
  # ...
end

class WorkerB
  sidekiq_throttle_as :some_throttling_startegy
  # ...
end

Any place I can read about what is Registry? I havent found any documentation about this.
And in our case, should the  strategy should look like the code below?
Sidekiq::Throttled::Registry.add(:some_throttling_strategy, {
 :concurrency => { :limit => 10 }, :key_suffix => 'some_lock'
})

Mm... Documentation is something this gem definitely lack of. :D I guess the only place where Registry is mentioned is in API docs of sidekiq_throttle_as method. And, some API docs of Registry.
If you need :key_suffix then yes, you should pass it too. So basically, second argument of Regisrty.add is same as what you pass to sidekiq_throttle.

Works. Thanks @ixti


Development/test automation plugin

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: VeithMetro:white_check_mark: pwielders:x: Volkan AslanVolkan Aslan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


fix(ScrollArea): prevent content overflow when using ellipsis

Fixes content overflow when using text-overflow: ellipsis
Fixes #1163
Added a new snapshot with the changes.
Added new stories
All tests are successful:

Seems related to https://github.com/radix-vue/radix-vue/pull/97#pullrequestreview-2201017892 - I see that this PR removes display: table, so hopefully it fixes my case.


Make services more configurable at runtime and dump-time

Is your feature request related to a problem? Please describe.
placeholder:
@gabe-l-hart has some deets
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context about the feature request here.

How does https://github.com/caikit/caikit/issues/380 differ?

I think #380 is the simple on/off flag for grpc and http interfaces
I think what @gabe-l-hart was talking about is a more fine-grained configuration like turning specific services (inference, training + training mgmt, model-runtime) on and off, or even going deeper and disabling specific training algorithms if you don't have a trainer that supports them

(plus maybe we refactor a bit of the file generation so that we can stick all the proto defs from the same package into one file, etc.)


Add math operators

This adds +, -, * and /, all the way from parse to runtime, with the MissingOperand, UnrecognizedOperator and DivideByZero errors. The basic design:

Operator Parsing: Instead of recognizing operators specifically, we read any run of operator symbols as a single operator. ++ is "++", not "+"; "+-" is not "+" followed by "-". If this doesn't cause us too many problems, we'll end up defining a host of "syntax" symbols (Unicode has a list we could use) that are valid in operators, and allowing any combination of those.
"Fixity"--binary vs. unary: We decide whether an operator is binary ("infix") or unary ("prefix" and "postfix") by context: an operator at the beginning of the expression is prefix, an operator between two integers is infix, and an operator at the end is postfix. This means that the only case where we can presently have "missing operand" is if there is an operator with no integers: "+" for example.
Late Operator Recognition: We recognize operators (and decide whether "operator not found") later, in the runtime phase. This is experimental, but is meant to future-proof us and allow any operator sequence to be defined programmatically (like, if you want to define +- to mean "plus or minus," as in an error range, it could break existing programs that used a+-b to mean the same thing as a-b).
Flat Syntax Tree: We simply store integers and operators in the order we find them, without any parent or child pointers. When we need a tree, we walk the integers operators and evaluate them in order. We'll reevaluate this, but the intent is to keep memory consumption down without unduly sacrificing performance.
Precedence Out Of Order Error: As we evaluate, we check precedence: if our forward-only evaluation would go against precedence expectations, we (for now) error and tell the user to add parentheses. This means that 1*2+3 will work, and 1+2*3 would error out. There are ways to handle both precedence and parentheses here, but there are multiple ways to handle grouping in Berg and it's worth seeing how far we can go with this.
Rationals: The "platonic runtime" is designed to tell you precisely what you are doing with numbers, and as such, it stores and operates on all numbers as BigRational (arbitrary-precision rationals). This means that all floating-point, integer, multiplication and division can be represented exactly with no numeric loss.
No Type Checking: Very deliberately, the system doesn't yet let you write anything other than integers, so there is only one type. Therefore you don't have to worry (yet) about what to do when + is fed something other than an integer.

On a side note, I am coming to realize the PlatonicRuntime is really a PlatonicTypeChecker, but will change that in the near future when we do something more sophisticated than integer math.

Merged after review with @benbp and Torrent.


Adds SeqGRU

Adds SeqGRU adapted from @guillitte's version for torch-rnn.
Fixes #235

@nicholas-leonard This is almost done, two tests are still failing. These are the ones on line 6218 and line 6277. I will not have time for the two weeks to figure out what's wrong here.

@JoostvDoorn I fixed those last bugs (issue was that I need to explicitly mask the backward part where LSTM doesn't require this).
Thanks for submitting this awesome PR. Really appreciate :)


upgrade FITS version

install 0.10.1, test

http://projects.iq.harvard.edu/fits/downloads

None of the FITS 0.10.x versions works correctly with heliotrope as of today. I wonder if hydra-derivatives and/or hydra-file_characterization are compatible with the most recent FITS releases. Heliotrope is on hydra-derivatives 3.0.1 and hydra-file_characterization 0.3.3. I have not tested FITS 0.9.x, but 0.8.4 works for sure, so I'm declaring a dependency on that version for now.

I created a ticket in hydra-derivatives asking for clarification about which versions of FITS are compatible with the current release of hydra-derivatives:  https://github.com/projecthydra/hydra-derivatives/issues/100

Justin's original report:
I saw stuff in the logs about not being able to run DROID on Java 8, so I would think that (FITS) 0.10.1 would have fixed that.

According to Mike Giarlo, who just closed https://github.com/projecthydra/hydra-derivatives/issues/100, hydra-derivatives is known to support FITS 0.8.x (specifically 0.8.5) - see the updated readme here: https://github.com/projecthydra/hydra-derivatives#dependencies

I tested both FITS 0.8.6 (installed via home-brew) and FITS 0.10.2 (installed manually) and both work without issue in both alexandria and heliotrope.
It would be worth launching rescue-web to ensure that jobs are being processed without errors - for the manual install I needed to symlink fits.sh to fits and hardcode FITS_HOME in fits-env.sh:
#!/bin/bash
#
# Sets up the environment for launching a FITS instance via
# either the fits.sh launcher, or the fits-ngserver.sh Nailgun server

#FITS_HOME=`dirname "$0"`
FITS_HOME="/usr/local/lib/fits-0.10.2"
export FITS_HOME
... #etc.

Though I'd think that if the 0.8.x ansible does this, it would work the same way for 0.10.x,, but it might be worth checking.

Mark's approach works beautifully:
Copy the unzipped fits directory in its entirety to /usr/local/lib/fits-{{ fits_version }}, symlink /usr/local/lib/fits-{{ fits_version }}/fits to /usr/local/bin/fits and to /usr/local/bin/fits.sh; edit /usr/local/lib/fits-{{ fits_version }}/fits-env.sh to point FITS_HOME to the /usr/local/lib/fits-{{ fits_version }} directory, then symlink the edited fits-env.sh to /usr/local/bin/fits-env.sh.
I've updated the Ansible scripts to install fits this way and press.curationexperts.com upgraded to 0.10.2.
As a breadcrumb for others, if you see
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/usr/local/bin/lib/slf4j-log4j12-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/local/bin/lib/tika-app-1.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]

this method of installing fits will circumvent the issue. The older version of the Tika jar may be installed by Solr or ImageMagick.


Does not preserve $

With PHP, variables start with the $ character. It would be great if this character was not stripped by change-case.
For instance:
$postID becomes post_id instead of $post_id

This is intentional. Closing for https://github.com/blakeembrey/change-case/issues/19. Though this seems like an extremely special case. Why can't you change case without a the $ instead and add it back?


What's the difference between CC0 and public domain?

From the Creative Commons CC0 info page:

The person who associated a work with this deed [CC0] has dedicated the work to the public domain by waiving all of his or her rights to the work worldwide under copyright law, including all related and neighboring rights, to the extent allowed by law.

So, functionally, what's the difference between a work explicitly licensed with CC0 and a work "free of known copyright restrictions"?
Should the two categories be merged, or is it worth keeping the distinction?

Good point. I will be looking at the list organisation over the next few days so I will bear this in mind.
I initially separated the two because one was a more formal approach than the other. If anyone has any input on this I'm all ears.

Also FWIW, the SpaceX Photos are released under CC0 but are categorized as public domain on this list.

Thanks for the heads up. I'll get this sorted ASAP

I've decided to keep the separation as it is for now. I think having the license free images separate is important as to not have any ambiguity.


gotify-server: 2.0.20 -> 2.0.21

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for gotify-server is: "A simple server for sending and receiving messages in real-time per WebSocket"
meta.homepage for gotify-server is: "https://gotify.net"
meta.changelog for gotify-server is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.0.21 with grep in /nix/store/aiyc3knpfk7gkl8rpq9anncw4jf1ayym-gotify-server-2.0.21

directory tree listing: https://gist.github.com/aec373da4a52e705b759818406c4265b

du listing: https://gist.github.com/ae64637f6b01408a2056771940a1837d

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
gotify-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/aiyc3knpfk7gkl8rpq9anncw4jf1ayym-gotify-server-2.0.21 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gotify-server https://github.com/r-ryantm/nixpkgs/archive/825d180ca2d7a048395220885deadf52391416f7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/aiyc3knpfk7gkl8rpq9anncw4jf1ayym-gotify-server-2.0.21
ls -la /nix/store/aiyc3knpfk7gkl8rpq9anncw4jf1ayym-gotify-server-2.0.21/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

gotify-server

Maintainer pings
cc @doronbehar @kalbasit for testing.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108642 run on x86_64-darwin 1

1 package failed to build and are new build failure:

gotify-server: log was empty

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108642 run on x86_64-darwin 1

1 package failed to build and are new build failure:

gotify-server: log was empty

Fails on darwin for me with `
sandbox-exec: pattern serialization length 130150 exceeds maximum (65535)

Fails on darwin for me with `
sandbox-exec: pattern serialization length 130150 exceeds maximum (65535)


diagnostics: Add event queue details screen. Fixes: #3022

Fixes: #3022

We absolutely need to improve the 'debuggability' of the app... but I don't think doing it this way is effective or optimal.
There are two big issues for me in this approach:

a lot of noise added to the logs by adding EVENT_NEW_EVENT_QUEUE_EVENT on every server event!
a lot of custom code (and even strings to translate) but resulting in very little added information

Another issue - this being so custom, also makes it incompatible with the (soon coming, almost ready) two queue approach... I am also not convinced that the added data is helpful in debugging the exact issue we are having about a dead queue.
That is why I suggested this in the issue you had filed: 'export the whole session state'. That would be way shorter code-wise, would be compatible with any future changes, and would not add noise to our state management.
When debugging and gathering diagnostics data we need to be as broad as possible. We have no idea what is needed. Also, we need to keep this out of the state.
Have a look at the timing.js diagnostics, to see how a much simpler approach is just as effective.
In order to debug the queue issues (and possibly most other issues), I suggest we implement the following two things:

a more general state display - so the session state but also any other key we want
an exception/error display - that is way more important when debugging the queue and possibly a lot of other issues
custom logging display - we can sprinkle some logs in places we want, maybe things like 'the queue was dead so I restarted', etc.


Create Secrets Manager helper and methods for META tokens

As part of the chatbot API requests (callback token validation + sending WhatsApp messages via Meta's API), a "secrets_manager" helper is needed, so that it can fetch a Secret with the necessary WhatsApp/Meta tokens, and the corresponding URLs can be invoked with the right authN/authZ.

Functionality added with the help of backend/common/helpers/secrets_helper.py, in these commits:

598505e06cd8b5c351eb641964b935439d10149e
f987f445f9d51c54c7a55c9b02f440778c8e415e


cpu-o3: reg arb smaller value hignher priority

before: bigger value get higher priority, bru will reject alu
after: smaller value get higher priority, alu will reject bru


evaluation.sh requires python2

I tried to run the evaluation script (tools/amr-evaluation-tool-enhanced/evaluation.sh), but when it was run in a environment without Python 2 (or, there doesn't exist an executable python2 in PATH), it results in a error like "python2: command not found".  This message was also shown during the training.  Could you write that the evaluation needs Python 2 in the README.md?

Thanks!
A note has been added to README.


Unify appearance of native controls on unsupported platforms

Currently we have a box with some text in it across the board, but it's not consistent:
WebView: "WebView requires a mobile target"
MapView: "MapView requires a mobile target"
CameraView: "CameraView is only supported on iOS and Android"
DatePicker/TimePicker: "GraphicsAppearance for DatePicker not implemented!"
This should be unified in some way, both in text and appearance.
My suggestion follows:
<Rectangle Color="White" StrokeColor="Black" StrokeWidth="1">
	<StackPanel Alignment="Center">
		<Text Font="Bold" Value="CONTROL_NAME" TextAlignment="Center"/>
		<Text Font="Thin" Value="Unsupported platform" Color="#AAA" TextAlignment="Center"/>
	</StackPanel>
</Rectangle>

I think this is a good idea. Perhaps we could even make some kind of StubElement-class that we instantiate so we can have the appearance defined in a central location?


Update DeveloperGuide (Show Status)

Details

Edited formatting and presentation of the Show Status Component.

Codecov Report

Merging #183 (0585e83) into master (9cb9568) will decrease coverage by 1.54%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #183      +/-   ##
============================================
- Coverage     48.89%   47.34%   -1.55%
  Complexity      355      355
============================================
  Files            87       89       +2
  Lines          1632     1679      +47
  Branches        186      184       -2
============================================
- Hits            798      795       -3
- Misses          765      815      +50
  Partials         69       69

Impacted Files
Coverage Δ

.../java/seedu/trackermon/logic/parser/CliSyntax.java
85.71% <0.00%> (-5.20%)
:arrow_down:

...rc/main/java/seedu/trackermon/model/show/Show.java
83.72% <0.00%> (-4.09%)
:arrow_down:

.../main/java/seedu/trackermon/model/show/Rating.java
42.85% <0.00%> (-2.15%)
:arrow_down:

...va/seedu/trackermon/logic/commands/AddCommand.java
100.00% <0.00%> (ø)

...a/seedu/trackermon/logic/commands/SortCommand.java
0.00% <0.00%> (ø)

...edu/trackermon/logic/parser/SortCommandParser.java
0.00% <0.00%> (ø)

...ava/seedu/trackermon/model/show/TagComparator.java
0.00% <0.00%> (ø)

.../seedu/trackermon/model/show/RatingComparator.java
0.00% <0.00%> (ø)

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 9cb9568...0585e83. Read the comment docs.


Added ToC

Added ToC
Todo: Link ToC items to headers

Your PR seems to have a conflict. Can you rebase your PR?

I was just looking. I have no idea what is the problem.
Tell me what I need to do and I'll try to fix.

Your update is based on an older version of the Readme. So it is missing a previously merged update.
Pull the laatst develop branch and reapply your update. 🤘🏻

Aah ok.

Made a new one


Feat: optimize component-pod template to displaying podStatus

Description of your changes
Add the podStatus field in the velaql template component-pod to display the aggregated status of pod containers.
copilot:all

Fixes #
I have:

[x] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[x] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

Please pass the linter


5.7.0: Fails to start with "CHIP Error 0x000000C1: Endpoint pool full"

I upgraded from 5.6.0 to 5.7.0 (using the Docker image) and PMS fails to start in my environment:
2024-02-29 16:12:32 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
[1709223152.260661][1:1] CHIP:CTL: Setting attestation nonce to random value
[1709223152.260913][1:1] CHIP:CTL: Setting CSR nonce to random value
2024-02-29 16:12:32 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
2024-02-29 16:12:32 (MainThread) CHIP_ERROR [chip.native.DL] Failed to get WiFi interface
2024-02-29 16:12:32 (MainThread) CHIP_ERROR [chip.native.DL] Failed to reset WiFi statistic counts
2024-02-29 16:12:32 (MainThread) WARNING [PersistentStorage] Initializing persistent storage from file: /data/chip.json
2024-02-29 16:12:32 (MainThread) WARNING [PersistentStorage] Loading configuration from /data/chip.json...
2024-02-29 16:12:32 (MainThread) ERROR [root] Uncaught exception
Traceback (most recent call last):
  File "/usr/local/bin/matter-server", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/__main__.py", line 171, in main
    server = MatterServer(
             ^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/server.py", line 115, in __init__
    self.stack = MatterStack(self)
                 ^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/stack.py", line 98, in __init__
    self._chip_stack = ChipStack(
                       ^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/chip/ChipStack.py", line 64, in wrapper
    instance[0] = cls(*args, **kwargs)
                  ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/chip/ChipStack.py", line 271, in __init__
    res.raise_on_error()
  File "/usr/local/lib/python3.11/site-packages/chip/native/__init__.py", line 67, in raise_on_error
    raise self.to_exception()
chip.exceptions.ChipStackError: src/system/SystemLayerImplSelect.cpp:376: CHIP Error 0x000000C1: Endpoint pool full

Downgrading to 5.6.0 again allows the server to come back up again.

Same thing, but I got shot down because I run in Docker.

Sorry, we do not provide user support here, nor do we officially support the docker image to run the matter server.
So basically you're on your own with regards to support. I trult advise to run the Matter server add-on. You can even run HA as virtual machine if you want, we provide several images for that.
We did see this in the past and in those cases it was related to the amount of containers (running on host networking). If the issue dissapears when you shutdown a few containers there's a hint there.
Something to try is maybe use a macvlan/bridge for the networking part. As you run docker yourself, you have a bit more influence on that.

For what it's worth, switching to BR0 on my Unraid box gets 5.7.0 to work.  Not sure what changed between 5.6 and 5.7, but I can live with this.

Goof to know that switching to bridge networking works. Maybe the recent additions for mdns browsing was just enough to push it over the edge, there's a lot of sockets opened in the SDK and its surroundings.

In this case I'm running in Kubernetes, and the container uses host networking so it can get at the real network interfaces. If the issue is the number of interfaces, can't the SDK be adjusted to deal with that again like it used to work?
Failing that I'd have to set up something like Multus with OVN so the pod gets a real IP on my local network via a bridge. That's a lot of extra complication for something that used to just work.

I'm using Home Assistant Supervised with the Matter add-on and seeing this error as well, I'm not running any additional software in Docker, just Home Assistant.
The workaround described here doesn't work for me, since I cannot change the network settings of a specific add-on in Home Assistant.
I've reported this error directly on the Home Assistant add-on repository, hopefully, it won't be closed like all other issues mentioning this error since that one is a supported installation method.
https://github.com/home-assistant/addons/issues/3496

@fcastilloec I'm sorry but supervised is also not a supported installation method. Everywhere in our documentation we mention that the ONLY officially supported method is Home Assistant OS with the Matter server add-on.

Actually we found something so this will be fixed in the next update. Still the comments about the supported setup remain. Matter (especially with Thread) is complicated and has a lot of dependencies on the host OS. Home Assistant OS is carefully tweaked to handle that optimally. This is not just another container you can start and forget, hence all our precautions.

I can confirm 5.8.0 works, thanks!


cam_microsoft.launch problem solved

Solves #18

@naishadhparmar You have sent the PR to mayank-devel-arduino branch which is now stale. It would be better to send the PR to master branch instead.


Windows support

Currently, gitbucket-ci-plugin makes build script as build.sh, so it doesn't work on Windows.  If GitBucket is working on Windows, should it make build.bat instead?

Git for Windows https://git-for-windows.github.io/ can also install Git Bash, so no need for a BAT file.


[explore] make new detect + fulfill endpoint

add new endpoint that does detection and fulfillment

thanks for the review!


chore(build-lib): scripts to create lib JS and ES content

we should add corresponding watch tasks as well.

Feel free to add it and rebase @weaintplastic


Element in iteration expect to have v-bind:key

I have the problem at src/components/Grib.vue

In 2.2.0+, when using v-for with a component, a key is now required.
How to fix it? Thank you!
https://vuejs.org/v2/guide/list.html#range

Please check https://github.com/wxs77577/rest-admin

Thank you very much!


(#48) session status

#48
Changes include:

An alert box for success statuses whenever an entity is updated.
This box comes with a cross button that will hide the box with a fade-out animation.
Once an entity is created, the user is redirected to it's edit page with the success message.

@nishanth-kd done with the feedback. have a look.


Samvera 101

Alisha Evans<EMAIL_ADDRESS>Shana Moore
New to Samvera? Welcome! We understand how steep the learning curve may seem when getting started.
Samvera 101 is an introductory presentation that will cover fundamental principles with a sampling of common topics and definitions used within the Samvera stack and community.
Framework topics include discussions around: Rails, Sidekiq, Data Stores, Fedora, Solr, Blacklight, etc. While application level topics include discussions around: Avalon, Hyrax, Hyku, etc.
Like a prerequisite class, this talk is designed to prepare developers and community members for success! Attendees will leave having a greater understanding of Samvera's components and how they come together to create a Samvera application.

If this is to be accepted, please can we insist on a title change.  "Samvera 101" with their description makes Samvera look like it's all tech.  "Samvera tech 101" (or similar) would be more acceptable to me.


Breadcrumb support

WIP

[Current coverage][cc-pull] is 77.44%

Merging [#757][cc-pull] into [master][cc-base-branch] will increase coverage by +0.62%

@@           master    #757   diff @@
=====================================
  Files          86      87     +1
  Lines        3252    3427   +175
  Methods         0       0
  Branches        0       0
=====================================
+ Hits         2498    2654   +156
- Misses        754     773    +19
  Partials        0       0

[][cc-pull]

Powered by Codecov. Last updated by 76108ea
[cc-base-branch]: https://codecov.io/gh/getsentry/raven-python/branch/master?src=pr
[cc-pull]: https://codecov.io/gh/getsentry/raven-python/pull/757?src=pr

[Current coverage][cc-pull] is 77.20%

Merging [#757][cc-pull] into [master][cc-base-branch] will increase coverage by +0.38%

@@           master       #757   diff @@
========================================
  Files          86         87     +1
  Lines        3252       3496   +244
  Methods         0          0
  Branches        0          0
========================================
+ Hits         2498       2699   +201
- Misses        754        797    +43
  Partials        0          0

[][cc-pull]

Powered by Codecov. Last updated by c9001b2
[cc-base-branch]: https://codecov.io/gh/getsentry/raven-python/branch/master?src=pr
[cc-pull]: https://codecov.io/gh/getsentry/raven-python/pull/757?src=pr