LocatorJ._setValue(@NotNull HasValue<?, V> self, @Nullable V value, boolean fromClient) should be public

It's the only method in LocatorJ that is package-private and thus cannot be used in tests.
Nevertheless the documentation mentions that one should use it when isFromClient needs to be true to test a code reacting to such events.
https://github.com/mvysny/karibu-testing/tree/master/karibu-testing-v10#changing-values

Must be something I accidentally omitted, sorry about that :) Will be fixed in Karibu-Testing 2.2.1


no-magic-numbers: Make condition lazy (don't call .getText() for every number literal in the file)

PR checklist

[ ] Addresses an existing issue: #0000
[ ] New feature, bugfix, or enhancement

[ ] Includes tests

[ ] Documentation update
[X] Enable CircleCI for your fork (https://circleci.com/add-projects)

What changes did you make?
Changed to avoid calling node.getText() for every number literal.

lgtm, thanks!


Create child orders in IgniteOrderLoaderMain created less than expected due to method is not threadsafe

in IgniteOrderLoaderMain
It loops to create parent Orders and child order (random * 100 - 250) in multiple threads
OrdersModel.createChild it creates child order with an incremental child order id (which is not threadsafe)
hence some child orders are not "new" child order but "update" existing child order

Hi @keikeicheung ,  Wendy would like to take a look into this if it hasn't been picked by others yet.

Hi  @junaidzm13, @keikeicheung , could you help review the code?


[docs] Update v4.1.3 link in README.rst

I Believe it will be easier for users that want to use v4.1.3 is to redirect them to the release tag rather than the branch readme.

Could you clarify why https://github.com/robotframework/robotframework/releases/tag/v4.1.3 would be better than https://github.com/robotframework/robotframework/tree/v4.1.3#readme?

You aren't supposed to download that version, it's just a package containing the whole repository content created by GitHub. The recommended approach to install v4.1.3 is pip install robotframework==4.1.3. If you want to download an installer, you should get the version we've uploaded to PyPI.
The above information is missing from the v4.1.3 branch because it was left to the state it was when v5.0 development started.. Because it's a branch, the README there could be enhanced, though.


Name conflict Error when publishing to an existing publish profile

Describe the bug
When I try to deploy my bot to an existing publish profile, if I had already deployed the same lu file before, I will get the following name conflict error.

The name field is used to identify the abs and luis resource,  so I can't fix this by just update the name, I need to go to luis portal to find and delete the existing app.

Version

Browser

[ ] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Additional context

@zidaneymar can you please take a look at this?

There is a ticket here https://github.com/microsoft/botframework-cli/issues/1044 tracking the name conflict issue in bf luis build, but it's in R12 plan. After the issue fixed in bf-lu side and composer consume the new bf-lu package, this error will go away since luis application names with only case differences will be recognized as same app so it will update the existing app instead creating a new one that already exists. Will keep posted.

Closed this issue since luis build has been fixed https://github.com/microsoft/botframework-cli/pull/1045.


[docs-only] [adr] New decision was made to use kql

Description
Change our query language ADR to reflect the outcome of our last discussion.
Related Issue

Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

test environment:
test case 1:
test case 2:
...

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (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 change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

@felix-schwarz weh should add that aspect here. Will do.

@felix-schwarz
I added this aspect in the context of "can be easily extended"


Supported Sony cameras

The list of supported Sony cameras is incomplete. All recent cameras writing the "Focus Location" meta data tag are supported.
Pull request is coming

thank you


Fix formatter comment reordering inside euid and on if-then-else

Description of changes
Fix #787 and a similar comment reordering issue I found for if-then-else expressions.
Based on the existing tests and some time running the formatter fuzz target locally, I'm fairly confident that not adding end_comment in VariableDef won't break anything, but review is of course appreciated.
As a side effect of the VariableDef change, a line break is introduced in the policy scope for some policies in test.cedar. I don't understand how that was introduced, but I'm willing to accept it.
Checklist for requesting a review
The change in this PR is (choose one, and delete the other options):

[x] A backwards-compatible change requiring a minor version bump to cedar-policy (e.g., addition of a new API).

I confirm that this PR (choose one, and delete the other options):

[x] Updates the "Unreleased" section of the CHANGELOG with a description of my change (required for major/minor version bumps).

I confirm that cedar-spec (choose one, and delete the other options):

[x] Does not require updates because my change does not impact the Cedar formal model or DRT infrastructure.

It'd great if we can update the fuzzing target to test that there are no reorderings.

It'd great if we can update the fuzzing target to test that there are no reorderings.

Found the if reordering bug after doing just that. Will post next week.


Proof of concept: add logic to automatically format Rust generic types

Examples:
'type vector' -> 'Vec<>'
'type vector eye thirty two' -> 'Vec<i32>'
'type hash map borrowed mute eye thirty two string' -> 'HashMap<&mut i32, String>'
'type borrowed mute hash map eye thirty two string' -> '&mut HashMap<i32, String>'
'type tuple eye thirty two character string' -> '(i32, char, String)'
'type hash map tuple boolean boolean finish string' -> 'HashMap<(boolean, boolean), String)>'

I'm new to Talon, so I'd appreciate advice for how to allow users to extend the list of types + their generic arg counts in an idiomatic way, without just editing this file. (A bigger project would be pulling in-scope types from VSCode & Jetbrains and automatically populating these lists, but I have no idea how possible that is.)

@auscompgeek How would you recommend exposing the list of types + arities for extension? Just a capture, like generic_type here?
Also is there a good way to export helper functions throughout talon extensions lol

I don't think I was necessarily expecting adding a capture or anything, just a plain old Python module with that function.


unable to invoke subcommand swift-build

i’m running into build failures for swift-json on some windows + swift combinations besides the (Windows 2019, swift 5.4.2) example. (logs). are these combinations supported?
 compnerd.org Swift version 5.3.3-dev (LLVM 3093af41dd, Swift 266905108e)
Target: x86_64-unknown-windows-msvc
error: unable to invoke subcommand: C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\swift-build ()

as it turns out, SPM didn’t start supporting Windows until 5.4. limiting the build matrix to swift 5.4 and above fixed the problem.


[Feature] Triqler output with decoys

Adds decoys when triqler is enabled.
PR checklist

[x] This comment contains a description of changes (with reason)
[x] CHANGELOG.md is updated
[x] If you've fixed a bug or added code that should be tested, add tests!
[x] Documentation in docs is updated
[x] If necessary, also make a PR on the nf-core/proteomicslfq branch on the nf-core/test-datasets repo

You can merge the PR @jpfeuffer


A problem occured configuring project ':app' Could not find com.google.android.gms:play-services-auth:9.2.1.

Here is my android\app\build.gradle
dependencies {
    compile project(':react-native-vector-icons')
    compile fileTree(dir: "libs", include: ["*.jar"])
    compile "com.android.support:appcompat-v7:23.0.1"
    compile 'com.airbnb.android:react-native-maps:0.6.0'
    compile "com.facebook.react:react-native:+"  // From node_modules
    compile(project(":react-native-google-signin")){
        exclude group: "com.google.android.gms"
    }
    compile 'com.google.android.gms:play-services-auth:9.2.1'
}

Here is the build.gradle
dependencies {
        classpath 'com.android.tools.build:gradle:2.1.2'
        classpath 'com.google.gms:google-services:3.0.0'
    }

Here is the settings.gradle
include ':app'
include ':react-native-google-signin'
project(':react-native-google-signin').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-google-signin/android')

Here is gradle-wrapper.properties
distributionUrl=https://services.gradle.org/distributions/gradle-2.14-all.zip
before it was 2.4
Here is the snap of console

can anybody help me out why i am getting the error what is going wrong?

you need to install the latest Google Play services from the android sdk manager (run android from the console)
have a look at https://github.com/devfd/react-native-google-signin/blob/master/img/android-req.png to make sure all packages are installed

hey @devfd  now after updating all required things i am getting this error. How can i come over it?

yes related to #47 but I don't have access to a windows machine so any help would be appreciated

Hi, I have the same issue (play-services & firebase). I have installed and updated all packages needed.
Could you please help me?

In an effort to clean the issues up, this is being closed. Please open a new issue if you're still experiencing a problem.


List acceptable enchantments for a given item

Enchantments should be shown on the screen in a list when placing an item in the slot.

Load a list of enchantments from the registry and filter using the item.
Render the list on the screen.

Added to dev 08059fd87c4463e0da4ffbdc18e0489c17d3cc7b

Updated in dev f70155dcf9902a722993be64fce374a1ac393b4a

Clears the list when the item is removed


When the last feature layer is turned off it still displays the data

(from tdepuyt)
This was an issue with the JavaScript Application as well.  The last layer turned off still displays its data.
The only known user workaround is to turn off the service layer if they want all layers to be turned off.

This was not related to the widgets.  There were S-57 objects not defined in the service's S52DisplayProperties.xml that prevented the features from turning off.


bug: can not over set default keymap

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.9.4
Operating system/version
macos 13.2
Describe the bug
vim.keymap.set("n", "f", "<C-f>", { remap = true })
this command not work
Steps To Reproduce

write config init.lua
this words：vim.keymap.set("n", "f", "<C-f>", { remap = true })
not working

Expected Behavior
real work
Repro
-- bootstrap lazy.nvim, LazyVim and your plugins
require("config.lazy")

vim.keymap.set("n", "s", "<cmd>w<cr><esc>", { desc = "Save file" })
vim.keymap.set("n", "f", "<C-f>", { remap = true })
vim.keymap.set("n", "e", "<C-u>", { remap = true })
vim.keymap.set("n", "<f3>", "<leader>fc", { remap = true })
vim.keymap.set("n", ".", "<leader>e", { remap = true })
vim.o.guifont = "Monaco Nerd Font:h18"

@j2wyatt 如果你想要修改快捷键, 请看文档
因为你使用 vim.keymap.set 这个API, 给的参数不对, neovim 的API没有 remap 这个选项,
你可以在neovim中 :help vim.keymap.set 可以查看文档,
这个选项是 lazyvim 提供的, 换句话说: 你必须按照 lazyvim 的配置文件, 使用 keys 选项才可以使用这个 remap 这个选项,
所以你这样执行是不行的 vim.keymap.set("n", "f", "<C-f>", { remap = true })
这是我的配置, 你可以参考下, 希望更可以帮到你

The following vim.keymap.set("n", "f", "<C-f>", { remap = true }) worked fine for me if you put it in /lua/config/keymaps.lua.

The following vim.keymap.set("n", "f", "<C-f>", { remap = true }) worked fine for me if you put it in /lua/config/keymaps.lua.

Thank you very much. Although I have already guessed in my heart, I just don’t want to admit that init.lua and keymaps.lua may be different, [crying]

The following vim.keymap.set("n", "f", "<C-f>", { remap = true }) worked fine for me if you put it in /lua/config/keymaps.lua.

Also I would really like to know more about this feature, do you know where I can find it?

Sorry, I was referring to why init.lua and keymaps.lua have different effects. Where can I see such documents?

My guess is that it has something to do with the way Lazyvim loads the different files in /lua/config/. In Lazyvim f is used by flash.nvim. But if you put it in your init.lua it will get overwritten by the plugin's configuration, which is loaded after the init.lua is loaded. So, if you put the keymap in /lua/config/keymaps.lua it is ensured that it takes precedence over plugin's configuration. I don't really know any good docs to point you except from reading the code itself in /lua/config/lazy.lua.

Also do you mind closing the issue since it's been resolved?

thanks


Feature/feedin split

Fixes #135
Changes proposed in this pull request:

splits actual feed-in to grid into asset origins, i.e. PV, V2G and battery

[x] Adding separate function
[x] Adding values to result csv file
[ ] Add Aggregate values to result json file

The following steps were realized (required):

[x] Correct linting with flake8 path_to_script
[ ] Check if tests pass locally with python -m pytest tests/

Also the following steps were realized (if applies):

[x] Write docstrings to your code
[ ] Explain new functionalities in readthedocs => required if docstring is present? @TabeaMaria
[ ] Write test(s) for new patch of code
[ ] Check building of documentation with doc/make html

Further TODO:

[ ] adapt for changing key and variable names in #160

Preliminary results as below:

Todos:

[x] feetin values should be negative


[BLD]: Adding org scope to package.json (GH release)

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

#2341  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tazarov and the rest of your teammates on  Graphite

@codetheweb, we'll need to do the same when making an official release to GH (release-javascript-client.yml), but let's see this succeed first.


New generation Pjax variations

I recently had to work on a web app wherein the previous developer had chosen to use this module on a project (even though the project in particular was started in 2020). While totally fine to do, I wanted to stop by here are inform those of you watching this repository or interested in leveraging the pjax approach in your web apps that you can find maintained alternatives without the jQuery dependency and maybe for some cases it is better to adopt the alternatives.
This module has served web applications for many years now and has done a beautiful job but please consider the new generation variants.

@brixtol/pjax
@hotwired/turbo
pjax.js
MoOx Pjax
InstantClick

Feel free to add on this list.

I just started learning JS and thanks for such analogies


feat(vendor): update etcd package

What this PR does / why we need it:

Does this PR need to be backport to the previous release branch?:

master
3.9
/cc @swordqiu @ioito
/area util
/hold

3.9 PR: https://github.com/yunionio/cloudpods/pull/13547

/lgtm


[Discusion] Display Old reactions wich are no longer Allowed (y/n)

This issue colect options of the gitea communety about title topic

IMHO the only reason to remove a reaction type is because it's causing problems. So, the reaction itself should disappear from the history if that's the case. Having said that, I don't like that idea; I'd rather let the admin have some moderating tools to manage that, but we don't want Gitea to become a social network (and it's a lot of work to do that properly), so... Tough choice.

I think if possible it'd be better to leave the DB intact and just not display it.
Then, if an admin decides to revert it later (or it was a mistake in the first place) they will display again.

I created an poll: :D

My opinion is to leav old reaction untoched but only allow deletion of not alowed one ...
If a reaction is realy so harmfull a `DELETE FROM reaction WHERE Type like "harmefull"  ...

@go-gitea/maintainers poll your option if you have not ... and then wee will see :)

The poll is clear about this ... I'll send a PR

We should have a more accurate meaning about the config.
; All available reactions. Allow users react with different emoji's
: For the whole list look at https://gitea.com/gitea/gitea.com/issues/8
REACTIONS = +1, -1, laugh, hooray, confused, heart, rocket, eyes

There are two meaning about REACTIONS. One is what reactions you will see, another is what reactions you can use. Most of the time they are the same. But when you change it serval times, it will not.
Or maybe we should have two options here. :)

@lunny about secound setting option:

think this will be rare used
can iretate ...

PR is here: #9387


Log warnings in Swift 3 + XCode 8

Just migrated my project that uses this library to Swift 3.0, it works but I have these warnings:
2016-09-21 12:43:37.621 MyApp[261:22982] the behavior of the UICollectionViewFlowLayout is not defined because:
2016-09-21 12:43:37.622 MyApp[261:22982] the item height must be less than the height of the UICollectionView minus the section insets top and bottom values, minus the content insets top and bottom values.
2016-09-21 12:43:37.622 MyApp[261:22982] Please check the values return by the delegate.
2016-09-21 12:43:37.624 MyApp[261:22982] The relevant UICollectionViewFlowLayout instance is <_TtC18AKPickerView_SwiftP33_5835361EBAB06A1606BA941DE6A5477B22AKCollectionViewLayout: 0x16ed3e10>, and it is attached to <UICollectionView: 0x170e6000; frame = (0 0; 691 50); clipsToBounds = YES; autoresize = W+H; gestureRecognizers = <NSArray: 0x16d64f20>; layer = <CALayer: 0x16d65240>; contentOffset: {0, 0}; contentSize: {0, 0}> collection view layout: <_TtC18AKPickerView_SwiftP33_5835361EBAB06A1606BA941DE6A5477B22AKCollectionViewLayout: 0x16ed3e10>.
2016-09-21 12:43:37.624 MyApp[261:22982] Make a symbolic breakpoint at UICollectionViewFlowLayoutBreakForInvalidSizes to catch this in the debugger.

+1

@allemattio Did it work on Swift 3 ? did u migrate it by your own?


help?

Please check for duplicates, similar issues or closed issues with the same problem, as well performing simple troubleshooting steps (such as deleting the export folder if it's an issue with compiling, reinstalling Kade Engine) before submitting an issue.
If you are playing a downloaded version of the game, what operating system are you using?
Windows (x86), Windows (x86_64), Linux, or macOS? Specify below.
What version of the game are you using? Look in the bottom left corner of the main menu.
???
Have you identified any steps to reproduce the bug? If so, please describe them below. Use images if possible.
????
Please describe your issue. Provide extensive detail and images if possible.
even by installing haxe 4.2.5 and running easysetup.bat i get this shit:
D:/haxerepos/hscript-improved/git/hscript/macros/ClassExtendMacro.hx:30: characters 4-89 : Warning : switchTo is deprecated, use startOutro
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodExprEx.hx:63: characters 11-16 : Unmatched patterns: EAlreadyExistingClass | EInvalidClass
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:223: characters 19-45 : Object requires field depth
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:223: characters 19-45 : ... For function argument 'x'
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:225: characters 19-30 : Object requires field depth
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:225: characters 19-30 : ... For function argument 'value'
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:286: characters 37-49 : Object requires field depth
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:286: characters 37-49 : ... For function argument 'value'
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:347: characters 21-53 : Object requires field depth
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:347: characters 21-53 : ... For function argument 'x'
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:349: characters 24-27 : { r : (args : Array<Dynamic>) -> Unknown<0> } should be { r : Dynamic, depth : Int }
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:349: characters 24-27 : ... { r : (args : Array<Dynamic>) -> Unknown<0> } has no field depth
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:349: characters 24-27 : ... For function argument 'value'
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:350: characters 32-35 : { r : (args : Array<Dynamic>) -> Unknown<0> } should be Null<{ r : Dynamic, depth : Int }>
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:350: characters 32-35 : ... { r : (args : Array<Dynamic>) -> Unknown<0> } has no field depth
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:350: characters 32-35 : ... For function argument 'value'
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:610: characters 20-27 : Field resolve overrides parent class with different or incomplete type
D:/haxerepos/hscript-improved/git/hscript/Interp.hx:444: characters 18-25 : ... Base field is defined here
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:610: characters 20-27 : ... Different number of function arguments
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:362: characters 20-32 : Field makeIterator overrides parent class with different or incomplete type
D:/haxerepos/hscript-improved/git/hscript/Interp.hx:919: characters 11-23 : ... Base field is defined here
D:/haxerepos/polymod/git/polymod/hscript/_internal/PolymodInterpEx.hx:362: characters 20-32 : ... Different number of function arguments

install haxe 4.3.5

didnt do anything :/


[HZ-1333] Fixing nulls for all rows after first null (backport of #184)

Backport of #184.

Backport with no conflict -> merging with one approval


Update dead URL in documentation

Hi! This script is amazing. So many tips and tricks to find. Thank you for making it!
While I was rooting around, I noticed that this URL in the documentation was dead. This PR updates the URL to point to the new location of the referenced article.

Thanks for catching this!


Version 1.1.4 needs to be released on PyPI

Last release on PyPI is 1.1.3. It needs to be updated.

I'll be releasing it after I finish testing all the functionality of the API.

https://pypi.org/project/youtube-scraping-api/1.1.4/


Update readme with information on configuring optional modules

Since some modules have been made optional, the samples that use them do not build unless modules are enabled. This PR adds steps on enabling LZ4 module to LZ4 compression sample and a general note to the modules section of the documentation

@afeinman-snap fix the compliance issue and update the commit message to follow the contribution guidelines, as mentioned by the greeter bot.

Also, amend fixup commits and force push your latest changes.

Also, amend fixup commits and force push your latest changes.

I was just doing that :)

I've learned how to run compliance checks locally and ran them. Should be good to go now


Missing instruction to compile kotlin and a variable type in CenteredTextManager.kt causing build failure and wrong variable type. #3681

There are no instruction for compiling kotlin files in RTNCenteredText/android/build.gradle. After adding those instruction in gradle it compiles the kotlin files.
But now we get error in the file CenteredTextManager.kt at line no 14 where the variable delegate has type RTNCenteredTextManagerDelegate<CenteredText> and this RTNCenteredTextManagerDelegate asks for second type.
So i just replaced it with ViewManagerDelegate and it worked. I have replace RTNCenteredTextManagerDelegate with ViewManagerDelegate in docs.
private val delegate: ViewManagerDelegate<CenteredText> = RTNCenteredTextManagerDelegate(this)

Hi all, I had the same issue and I tried this and it seemed to allow compilation to work, so thanks very much for that. But when I load the centered text component in my RN app, I see no text or component. It is just an empty view. Can we verify that this change does not break something else causing an issue like an empty view to be rendered?

I am using Kotlin, is my issue maybe because I need to make the build.gradle change as well so that my Kotlin files get compiled?

Ah wait, I see the comment about tabbed approach. I followed that and used the build.gradle that is currently on the website so i think I am good.
So still question remains, does this change break something that causes an empty View to get rendered?

Closing as this has already been fixed


新版用字表，加速試驗

Coverage remained the same at 43.972% when pulling 9e5797529194053f1249161f23a55f15fb0688c3 on 新版用字表，加速試驗 into 630ee608e1de64679c6a122104d9288dd1fc957c on master.


Add clear_schedule

Objective
Adds clear_schedule method to State.
Closes #3932

bors r+

bors r+

bors r+


Pub build should fail early or keep what it has already build

This issue was originally filed by @zoechi

What steps will reproduce the problem?
1.
I'm currently porting polymer-elements to Dart.
This project has an example page for every element (almost 40)
2.
I start pub build and it takes a while to get finished.
3.
When it's finished I get a message "Build failed" and the build directory is empty.
What is the expected output? What do you see instead?
I would rather have at least all successfully built files in build or alterantively
pub build should fail and stop immediately when it encounters an error (or at least when it has finished the failing entry point to get as all possible error messages)
What version of the product are you using? On what operating system?
Dart VM version: <IP_ADDRESS>_r30187 (Tue Nov 12 00:09:52 2013) on "linux_x64"
Please provide any additional information below.

This issue has been moved to dart-lang/pub#724.


remove path in config view

:tada: This PR is included in version 1.9.12 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Make transformSrc type optional

I've made the transformSrc an optional parameter, as mentioned here https://github.com/robinscholz/svelte-inline-svg/issues/25#issuecomment-1125485105. I've also realised that the reason the types are playing up - besides the missing entry in the package.json files key, which you fixed - is that the last release didn't include the dist folder in the package at all. It seems like a manual process, so I think it's just something to check before publishing.

@james-camilleri Good catch, not sure how I missed this tbh. Sorry for the troubles. I’d still like to rewrite the entire package with typescript, but need to find the time for that.

I'd love to help out as soon as I get a free second, but I'm currently so unbelievably swamped I barely have time to eat alas. I'll let you know if I find time to help out. Thanks for this in the meantime though!


[Task]: Update app by app JSON including module instances

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
No response

Covered in #26469


chore: create alert button padding bottom on iOS devices

The type of this PR is: Enhancement

Description
Screenshots
Android
||||||
|---|---|---|---|
||||||
iOS
|8|12|13Pro|13mini|
|---|---|---|---|---|
||||||

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

safeareaview in create alert filter button - gkartalis

Android user-facing changes

Dev changes

This PR contains the following changes:

iOS user-facing changes (safeareaview in create alert filter button - gkartalis)

  Generated by :no_entry_sign: dangerJS against a9780de4cfc3bf9d13854a176839ba9ddf71aa16


Set default ZarrPlugin prefix to /zarr

Closes #182

@jhamman I might need some Zarr help here. It looks like it's failing as the non-dimension coordinate order isn't matching in the metadata tests.
I haven't been able to replicate it against Python 3.9.15, Xarray 2023.4.2,  Zarr  2.14.2 (or 2.11.3 before I bumped Zarr to see if that was mismatched) locally. I didn't see anything in Xarray or Zarr's changelog that made me think that there would be a change in either that would affect the ordering of lat and lon.

I re-triggered the failed CI and things past. Not sure what was up with the previous failed run but I'm wondering if it had picked up an old/malformed cache.

Oh, do we need some doc updates with this?

It just failed the same way when landing the pydata-theme PR. I'm going to try explicitly sorting the coord names to see if that helps make the ordering of coords predictable at least from Xpublish's side.
And yes, because I had big doc changes in flight I'm going to make the updates there #180.

Ok, so we are sorting coordinates, but Xarray/Zarr isn't?

And that also passes when run again.

It looks like xarray sets the value here, and I can't make out any sorting which would make it stable. https://github.com/pydata/xarray/blob/25d9a28e12141b9b5e4a79454eb76ddd2ee2bc4d/xarray/conventions.py#L690-L697


Roll Engine from ee2ac2a5afc3 to 36a9451a4f58 (4 revisions)

https://github.com/flutter/engine/compare/ee2ac2a5afc3...36a9451a4f58
2021-01-14<EMAIL_ADDRESS>Add support for rendering using Metal on macOS (flutter/engine#23599)
2021-01-14<EMAIL_ADDRESS>Remove unused fml::Message serializer (flutter/engine#23669)
2021-01-14<EMAIL_ADDRESS>SkParagraph: enable the ICU breaker cache (flutter/engine#23667)
2021-01-14<EMAIL_ADDRESS>Add winuwp as one of the choices in --target-os.
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.

Commit queue failed; closing this roll.


Need to run LeNet with integer type input from ComputeLibrary

Hi:
ComputeLibrary LetNet example only supports float32. When I changed the data type argument to integer (e.g., 32 bit, 16 bit or 8 bit), I got error message from one of the lower level functions. I wonder if there is major effort to change the LeNet example to support these data types. Anyone who has had it working, please give advice.  I think there should be an easy way, however, I am new to the library and have not studied deep enough to draw conclusion.
Thanks, David

Manuel, I have tried two data types: type=QASYMM8, and type=F16. I am running LeNet example and runs the Compute Library's graph API. The first type triggers error from graph_lenet.cpp:59:
QASYMM8 not supported for this graph!!!!
When I tried the second type, the graph configuration is ok, but the data type is not supported in NEON/kernels/NEIm2ColKernel.cpp:
Threads : 1
Target : NEON
Data type : F16
Data layout : NHWC
Tuner enabled? : false
Tuner file :
Fast math enabled? : false
Data path : /home/pi/projects/LeNet/LeNet/model
Image file : /home/pi/projects/LeNet/LeNet/images/0/00.ppm
Labels file : /home/pi/projects/LeNet/LeNet/images/labels.txt
!!!!!!!!!!!!!!!!!!!!!!!!!!!
ERROR in configure src/core/NEON/kernels/NEIm2ColKernel.cpp:391: Data type not supported
!!!!!!!!!!!!!!!!!!!!!!!!!!!
Test FAILED
Please advice if all the lower level supporting functions for integer types and Float 16 are available.  Please also tell how much effort in making changes from the LeNet example to demonstrate different types of integer and their operations.
Thanks, David

Hi @davidchaozhang ,
QASYMM8 is actually supported by all the layers used in the network, but we don't have quantitized coefficients. So, you can just remove ARM_COMPUTE_EXIT_ON_MSG() in the example but you need to provide your own coeffs.
For the F16 data type we need to know running environment and your scons command. F16 is supported on NEON, but only for architectures v8.2 or above. So scons should have arch=arm64-v8.2-a and cpu architecture of the device your are running the program v8.2 or above.
Thanks,
Manuel

Hi, Manuel:
Thanks for the prompt reply. I am using Raspberry Pi 3+ as a platform to build  and test ComputeLibrary. The arm architecture I used is Armv7a, which is Arm's release OS on Pi3+. I believe it doesn't support F16 based on your input. However, Pi3+ has 64-bit ARM processors, ideally, the hardware should support arm64 compilers. I am going to download Ubuntu Mate for PI and build with arm64-v8x. If you have experience on that, please give me suggestions.
Further question on QASYMM8, is the integer 8 support NEON only in all the layers? Or does this data type also support OPENCL? Does ComputeLibrary support both NEON and OPENCL running at the same time?
I removed  ARM_COMPUTE_EXIT_ON_MSG() in the example and had an error message in one of the lower level library calls. I will send you details in the next message after collect it from Pi.
Thanks, David

Hi @davidchaozhang ,
NEON doesn't support F16, but if you run the graph example with OpenCL you can use F16.
We actually have a blog post that goes step by step on running AlexNet on a Raspberry Pi 2 or 3 with Ubuntu Mate 16.04.02:
https://community.arm.com/processors/b/blog/posts/running-alexnet-on-raspberry-pi-with-compute-library
It should help you out in setting up the environment. QASYMM8 seems to be supported by all the operators in LeNet.
Theoretically you can use OpenCL and NEON at the same time, but you have to create an adhoc network and manage the tensors. For simplicity we propose our graph_example which will use NEON or OpenCL layers.
Thanks,
Manuel

Manuel:
Thanks for the blog. I read it and think it is helpful. A few questions as I study more of the library. Please bear with me on these basic questions:

To support QASYMM8, do I need to generate an integer typed weight files (such as conv1_w.npy, etc)? Can I still use the float32 weight files? I think you said I need to provide my own coefs. Can you elaborate on how to do that?

I converted LeNet weight files from a pretrained tensorflow weights. The shape is {FilterN, Channel, W, H}. Does this match with DataLayout::NCHW? If you have a npy weight file I can try, please let me know.
Thanks for your help,
David

You have to convert the float32 weights to QASYMM8 and then give them to the network. You'll probably have to work a bit to find the best offset/scale. Right now our lenet example is provided and has been tested only with float32 weights
We only have the weights that we are proposing in our example. About how we handle the dimensions in NCHW and NHWC please refer to this function:
https://github.com/ARM-software/ComputeLibrary/blob/master/src/graph/Utils.cpp#L124

Manuel, Thanks for the reply. I am using r = S(q-Z) to convert float r to the quantized q. I have also found functions in Types.h and QAsymm8.inl to perform the conversion. I assume the scale S and offset Z is estimated per convolution, per pooling, per activation layer. Let me know if my understanding is correct. Also scale and offset need to be carried as data input in npy file. I assume LeNet example has not programmed to take in these extra parameters (QuantizationInfo in and out). Is there other examples in ComputeLibrary that supports the QAsymm8 data input?
Also for data layout, regardless input/output data, and weights, ComputeLibrary uses NCHW format, right?
Thanks, David

Our MobileNet example is proposed also using QASYMM8 with the coefficients already quantitized:
https://github.com/ARM-software/ComputeLibrary/blob/master/examples/graph_mobilenet.cpp#L177
As you can see the weight files contains the data and the quantization info is hard coded.
The LeNet example currently doesn't have any quantization info.
You can set the format of the input tensor and (if supported) the layer will be able to carry out the operation. If it cannot it should throw a runtime error during validation
Best,
Manuel

Closing for inactivity, feel free to reopen otherwise

advice

Dear Manub,
I want to run AlexNet, GoogleNet, MobileNet, ResNet, and SqueezeNet graphs in quantized mode. I already run these graphs with dummy input and weights data and measure their performance. Now I want to run them with dummy data in quantized u8 or int8 and measure their performance. Is it possible to run with quantization on CPU and GPU? if Yes, would you please let me know how could I do that?
Best,
Ehsan


remove FF for OSV and Target Auto-Detect STO-7324

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screenshot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6601ddc074004e4559c7fe20--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6601e335398f2b4b107736cd--harness-developer.netlify.app


[NEW] Add support for initial Rich Messaging(ButtonAction as Attachment)

@RocketChat/android
This PR adds support for initail Rich Messaging (ButtonActions as Attachment)
Test it with SDK : https://github.com/RocketChat/Rocket.Chat.Kotlin.SDK/pull/203
And follow this to test it: https://github.com/WideChat/Rocket.Chat.Android/wiki/(WIP)--Rich-Messaging-Acceptance-Test
Spec: https://github.com/WideChat/Rocket.Chat.Android/wiki/Buttons-Inside-Attachment-Object-Spec
Demo : https://photos.app.goo.gl/okir1oP776cAcZ279

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@Shailesh351 Could you please sign the CLA so we can review this PR?

@Shailesh351 Do you mind resolving the conflicts here please?

@luciofm @filipedelimabrito I have updated PR with requested changes. Please have a look.
Thank you

@luciofm Made requested changes and I'm able to successfully compile the PR now. Still latest develop branch is not building successfully so haven't merged it yet.

@Shailesh351 you need to use Android Studio 3.3.0-alpha5 or 3.2.0-beta5, don't use 3.3.0-alpha6 because it has issues.

@luciofm I tried with Android Studio 3.2 RC 1 but develop branch is giving error while building.
Cannot access class 'Lkotlinx.coroutines.experimental.android.HandlerContext;'. Check your module classpath for missing or conflicting dependencies

@luciofm Done!!!. PR is ready.

Merged with https://github.com/RocketChat/Rocket.Chat.Android/pull/1620


Refactored detection of arguments in question in MiKo_3109

Refactored the MiKo_3109_TestAssertsHaveMessageAnalyzer to use a ConcurrentDictionary for mapping method names to expected argument indices, improving maintainability and performance.
Removed the GetExpectedMessageParameterIndices method, simplifying the codebase.
Added comprehensive tests for the Pair class, covering Object.Equals and GetHashCode methods to ensure correct behavior.
Suppressed TFM support build warnings in the BenchmarkConsole project file to clean up build output.

Title
Refactored detection of arguments in question in MiKo_3109

User description
@CodiumAI-Agent /describe

PR Type
Enhancement, Tests

Description

Refactored the MiKo_3109_TestAssertsHaveMessageAnalyzer to use a ConcurrentDictionary for mapping method names to expected argument indices, improving maintainability and performance.
Removed the GetExpectedMessageParameterIndices method, simplifying the codebase.
Added comprehensive tests for the Pair class, covering Object.Equals and GetHashCode methods to ensure correct behavior.
Suppressed TFM support build warnings in the BenchmarkConsole project file to clean up build output.

Changes walkthrough 📝
Relevant filesEnhancement

MiKo_3109_TestAssertsHaveMessageAnalyzer.csRefactor argument detection using ConcurrentDictionary

MiKo.Analyzer.Shared/Rules/Maintainability/MiKo_3109_TestAssertsHaveMessageAnalyzer.cs
Introduced a ConcurrentDictionary for method name to argument indices mapping.  Refactored HasMessageParameter method to utilize the new dictionary.  Removed the GetExpectedMessageParameterIndices method.

+100/-94

Tests

PairTests.csAdd equality and hash code tests for Pair class

MiKo.Analyzer.Tests/PairTests.cs
Added tests for Object.Equals method for Pair class.  Added tests for GetHashCode method for Pair class.

+39/-0

Configuration changes

BenchmarkConsole.csprojSuppress TFM support build warnings in project file

BenchmarkConsole/BenchmarkConsole.csproj

Suppressed TFM support build warnings.

+1/-0

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

@CodiumAI-Agent /describe

Title
Refactored detection of arguments in question in MiKo_3109

User description

Refactored the MiKo_3109_TestAssertsHaveMessageAnalyzer to use a ConcurrentDictionary for mapping method names to expected argument indices, improving maintainability and performance.
Removed the GetExpectedMessageParameterIndices method, simplifying the codebase.
Added comprehensive tests for the Pair class, covering Object.Equals and GetHashCode methods to ensure correct behavior.
Suppressed TFM support build warnings in the BenchmarkConsole project file to clean up build output.

PR Type
Enhancement, Tests, Configuration changes

Description

Refactored MiKo_3109_TestAssertsHaveMessageAnalyzer to use a ConcurrentDictionary for mapping method names to expected argument indices, improving maintainability and performance.
Enhanced Except method in EnumerableExtensions to accept any IReadOnlyCollection.
Added comprehensive tests for the Pair class, covering Object.Equals and GetHashCode methods to ensure correct behavior.
Suppressed TFM support build warnings in the BenchmarkConsole project file to clean up build output.

Changes walkthrough 📝
Relevant filesEnhancement

EnumerableExtensions.csEnhance `Except` method to support `IReadOnlyCollection`

MiKo.Analyzer.Shared/Extensions/EnumerableExtensions.cs
Modified Except method to accept IReadOnlyCollection instead of List.

+1/-1

MiKo_3109_TestAssertsHaveMessageAnalyzer.csRefactor argument detection using `ConcurrentDictionary`

MiKo.Analyzer.Shared/Rules/Maintainability/MiKo_3109_TestAssertsHaveMessageAnalyzer.cs
Replaced GetExpectedMessageParameterIndices method with a ConcurrentDictionary.  Improved performance and maintainability by using ConcurrentDictionary.  Refactored HasMessageParameter method to use the new dictionary.

+100/-94

Tests

PairTests.csAdd tests for `Pair` class methods

MiKo.Analyzer.Tests/PairTests.cs
Added tests for Object.Equals method.  Added tests for GetHashCode method.

+39/-0

Configuration changes

BenchmarkConsole.csprojSuppress TFM support build warnings in project file

BenchmarkConsole/BenchmarkConsole.csproj

Suppressed TFM support build warnings.

+1/-0

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information


Where is the code?

I really want to play this game but cannot find the code.

I uploaded the codes and I will add the playable demo soon.


Use regular click event

I believe the m-* events are not longer used in melt/bitsui/shadcn-svelte?

Thank you!


Fix dead links to the kubelet configuration

Those links are dead, pointing at what I assume in the previous place for the Kubelet TLS bootstrapping documentation.
Update them with the new location!

/lgtm
/approve


make level random seed visibel and allow to replay a level

This will allow to try to play a level better than last time.

implemented in v1.2.1


ExperimentalScanner: Always scan the full repository

Always scan the full repository, even if a VCS path is set. This makes
the initial scan slower if a VCS path is set, because more files are
scanned, but it also has several advantages:

There is exactly one scan result in the storage for each repository
and revision, not multiple for different VCS paths.
Changing the VCS path via a curation does not require a new scan,
instead the existing result can be reused and filtered appropriately.
Only one scan of a repository revision is required, no matter how many
packages where published from it.

packages where published from it.

Nit: "were"


Update version to 0.6.0

@jerryshao @xunliu @yuqi1129  Could you help me review this pull request?


Error requireUncached is not defined

When switching a working example from require(...) to requireUncached(...) I get this error:
ReferenceError: requireUncached is not defined
    at Object.action (/Users/.../http/.httpyac.js:31:20)
    at be.trigger (/Users/.../http/node_modules/httpyac/dist/index.js:1:3409)
    at async ie (/Users/.../http/node_modules/httpyac/dist/index.js:1:14784)
    at async $e.trigger (/Users/.../http/node_modules/httpyac/dist/index.js:1:3392)
    at async we (/Users/.../http/node_modules/httpyac/dist/index.js:1:21944)
    at async Va (/Users/.../http/node_modules/httpyac/dist/index.js:115:19709)
    at async Qt (/Users/.../http/node_modules/httpyac/dist/index.js:115:19085)
    at async Object.Ja (/Users/.../http/node_modules/httpyac/dist/index.js:139:3468)
ExecuteHook: httpClient failed

Both on CLI and VS-Code plugin,  node version v17.0.1

requireUncached is not needed while using cli. The require cache is only in memory and does not survive a restart of the app. Does not fix the bug, but it should be not your initial problem.
Try using Javascript Debugger Terminal in VSCode with the httpyac cli. You could debug the .httpyac.js and all requires code.

Right, requireUncached  is for CLI  not required and that's what I'm using now when developing the flows. The build-in debugger I never used before, but figured it out now.. cool stuff thx

I have a hard time providing the requireUncached method. I use the correct Module.createRequire to load the plugins, because I need to run the packages in the context of package.json. The solution using vm.runInContext might work, however I already know that I need/want to switch to esm soon. Many important dependencies (chalk, globby, got) already use esm and this does not allow clearing the require cache anymore.
Currently, it would be easy to pass the method as an API method, but I would have to mark it as deprecated.

IMHO it's fine to deprecated it. I actually didn't miss it, only tried it as I found it in the guide. I'd rather replace it with the guidance you gave me to use the cli while developing to avoid any caching..

I think for the ticket there is nothing more to do currently. I will probably throw out requireUncached with the next major release.


Semantic versioning pre release allowing dot

http://semver.org/#spec-item-9 specifies that a pre-release can contain a dot.  Updating the regex to conform.
This was found when using the gulp bump command to bump the pre-release with a preId.  It was creating the version 1.0.0-build.1, which was failing NuGet SemVer validation.

Hi @BertCotton, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@BertCotton, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

Has there been any conversation/assignment around this?  We are wanting to use the npm gulp-bump package to be able to update our versions but that is not possible because NuGet doesn't conform to SemVer.
Does NuGet have a command line option that will bump the local version of a project?

@BertCotton we're working on adding SemVer 2.0.0 support to NuGet 3.x (NuGet/NuGet.Client). There is no plan currently to put SemVer 2.0.0 support into the older version here.
This PR would keep NuGet from failing on labels with dots, but it doesn't give it the full support needed to properly sort numeric labels, and parse the metadata field after #.
You can see the NuGet 3.x library for SemVer here: https://github.com/NuGet/NuGet.Client/tree/dev/src/NuGet.Core/NuGet.Versioning

SemVer 2.0.0 support has been added.


Reorganization for 2016

I wanted to write some notes on this now while the course is still fresh. I'd propose the following:
I would take over the first lecture that would incorporate the more biological material from "competition" and from "flu". This would aim to give an overview of different sorts of pathogens, and their strategies to escape immunity. Would touch on flu, HIV, malaria, HPV, rhinoviruses, etc...
You'd follow with a biological oriented immunity lecture that would be basically the B cell lecture from day 3, but would cover T cells and adaptive immunity as well.
I feel like my weakest link was actually the BEAST exercise. A large proportion of people had done exactly this exercise the week before. And I didn't like the step-by-step nature it entails. Better to tell people it exists and they can do it on their own time. This would free up some time.
I'd propose replacing "serology" with a more general "antigenic evolution" section. I could cover serology and you could cover things like the Hensley age distribution story you talked about here.
I'm propose to end with a "synthesis" discussion / exercise where students are given timeseries, trees, antigenic maps for say EV 71 and they're supposed to come to some conclusions about what's going on. Or maybe have people break up into groups and each group studies a particular pathogen and then reports to the class. We'd supply figures for each pathogen. So everything would be interpretation rather than data gathering.
Notice also that this makes it so you don't have a completely full day 1 and I don't have a completely full day 2.
Day 1

Session A: Biological lecture on pathogens (Trevor)
Session B: Biological lecture on immunity (Sarah)
Session C: Epi Models (Sarah)
Session D: Fitting (Sarah)

Day 2

Session A: SSR (Sarah)
Session B: Coalescent (Trevor)
Session C: Phylogenetics (Trevor)
Session D: Selection (Trevor)

Day 3

Session A: Antigenic evolution (Both)
Session B: Synthesis (Both)

Excellent ideas!
The only change I might make to your proposal is to extend the epi fitting over two sessions, perhaps focusing on population time series in Session D of Day 1 and on longitudinal data in Session A of Day 2. It may not be worth spending time fitting population data if MIF remains the obvious choice, however. (I am performing head-to-head competitions of methods this summer, so I should have a better sense if this is the case in a few months.) Covering inference well seems more important than SSR.
I also plan to include more small quizzes and exercises throughout my sessions.
It might be worth framing each session in the first two days in the most problem-oriented way possible, e.g., "This pathogen has a lot of types/high genetic diversity/fast turnover. How do we know if immune-mediated selection is a cause?" We then discuss population genetic measures, inference from mechanistic models, etc., in the context of major hypotheses. We could even assign pathogens to groups randomly on the first day (without providing the data then) so people listen with a specific context in mind. It might even make sense to provide data incrementally, e.g., some pertinent immunology after the immunology session, time series after the time series session, etc., if it wouldn't fragment the day too much.

I like the idea of group exercises on different pathogens interspersed throughout the module, with updates on different data / biological aspects in tune with the lecture material. These sessions could be just within-group discussion. The final session could be groups presenting a synthesis to the rest of the class.
My thoughts on fitting are as follows:
I'm not sure there's a lot of time to fully ingest how to do proper timeseries fitting. Like the BEAST module, people should just take the POMP module to cover this fully. Spending time on how we learn about competition between species via timeseries is, I think, key. This certainly includes mechanistic fits, but could also be basic things like general patterns of interference (H3 vs H1 flu seasons). Longitudinal infection / serological data seems extremely helpful for this as well. I wouldn't expect to teach how to do these fits, but you could look at some of the results that people have. One example is:
http://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.1002082
Although it's not actually longitudinal, it's the sort of fit that should be quite informative of strain interactions.

Those are good ideas. In general, it sounds like a broader integration of
different methods for inferring strain interaction, including longitudinal,
time series, and cross-sectional data, would be useful; pathogens differ in
the kinds of data available, creating different puzzles. This will be fun
to put together.

Sarah Cobey, PhD
Assistant Professor
Ecology & Evolution
University of Chicago
(617) 756-7204 (cell)
sarahcobey (Skype)
cobeylab.uchicago.edu
On Thu, Jul 23, 2015 at 6:52 PM, Trevor Bedford<EMAIL_ADDRESS>wrote:

I like the idea of group exercises on different pathogens interspersed
throughout the module, with updates on different data / biological aspects
in tune with the lecture material. These sessions could be just
within-group discussion. The final session could be groups presenting a
synthesis to the rest of the class.
My thoughts on fitting are as follows:
I'm not sure there's a lot of time to fully ingest how to do proper
timeseries fitting. Like the BEAST module, people should just take the POMP
module to cover this fully. Spending time on how we learn about competition
between species via timeseries is, I think, key. This certainly includes
mechanistic fits, but could also be basic things like general patterns of
interference (H3 vs H1 flu seasons). Longitudinal infection / serological
data seems extremely helpful for this as well. I wouldn't expect to teach
how to do these fits, but you could look at some of the results that people
have. One example is:
http://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.1002082
Although it's not actually longitudinal, it's the sort of fit that should
be quite informative of strain interactions.
—
Reply to this email directly or view it on GitHub
https://github.com/trvrb/sismid/issues/9#issuecomment-124271668.

Day 1

Session A: Biological lecture on pathogens (Trevor)
Session B: Biological lecture on immunity (Sarah)
Session C: Serology and antigenic evolution (Trevor)
Session D: Epi Models (Sarah)

Day 2

Session A: Timeseries and fitting (Sarah)
Session B: The Coalescent and phylogenetics (Trevor)
Session C: Selection (Trevor)
Session D: Forecasting (Sarah mostly)

Day 3

Session A: Synthesis (Both)
Session B: B cell (Sarah)

@sarahCobey ---
I'm going to start in on this reorganization. This will take the form of moving slides around to fit the above outline. I have a question about how to treat the pathogen presentations, but I'm going to thread this in issue #11.

That's the basic reorganization. I think we should plan for Forecasting to be a short section as the other three things happening on day 2 are already quite time consuming. I agree that it's a good angle. I'm going to open issues on specific sections that need to be padded out.

I think we're there with the basic reorganization. There are pieces that could be improved, but I'll leave these to separate issues.


Create TwilML parser

Changes Unknown when pulling 2942df78a7904366d04417c73eb6efff50d48deb on feature/issue-1-create-twilml-parser into ** on develop**.

:+1: on landing and iterating from here. A few general comments:

We should perhaps use Twisted's trial.unittest instead of unittest since this is going to be Twisted based.
It seems like there should be a cleaner way to assert on the exceptions (perhaps a combination of Twisted's f = self.assertRaises(...) or just a helper function).

@hodgestar I've addressed your comments. Ready for another review

:+1: !


add:Readme.md file

Description

[ ] I have added a folder(Named it as my GitHub user id)
[ ] I have added a Readme.md file inside the folder
[ ] I understand the GitHub Forking Concept fully

add:Readme.md file

commit

again


MariaDB_AWS_Bug_Fixes

Balram, could you resolve the conflicts? We'll merge afterwards. Thank you!

Balram, could you resolve the conflicts? We'll merge afterwards. Thank you!

Hi Tal, Conflicts has been resolved. Thanks!


Expose ONNX type, size, and name constants in OMTensor

Signed-off-by: Gong Su<EMAIL_ADDRESS>

This is the only file in Java that has the list. C/C++ has its own list but that is completely unrelated to the Java list.

No the two lists are independent of each other so they don't have to be in sync. However, since they are both from the standard ONNX types they naturally tend to be the same.

Jenkins Linux s390x Build #3848 [push] Expose ONNX type, size, ... started at 11:57

Jenkins Linux amd64 Build #3857 [push] Expose ONNX type, size, ... started at 10:57

Jenkins Linux ppc64le Build #2964 [push] Expose ONNX type, size, ... started at 11:58

Jenkins Linux s390x Build #3848 [push] Expose ONNX type, size, ... passed after 43 min

Jenkins Linux ppc64le Build #2964 [push] Expose ONNX type, size, ... passed after 51 min

Jenkins Linux amd64 Build #3857 [push] Expose ONNX type, size, ... passed after 55 min


Update minerfund addresses for numbers upgrade

Use new minerfund addresses for numbers upgrade and change the way they're handled so that they select only one output, iteratively, per block. This avoids having tons of tiny tiny outputs.

Confirmed for lotus_16PSJLMtCuFnyMb3rz4zbbhAtJgppp8GiY5NpGGev

Confirmed


WIP: Audit mode

Implements #9986. Extremely WIP.

@phiggins @tas50 hello! this is really awesome, just wanted to point out that @chef-davin did some really great work recently to add the inspec_waiver_file resource in a PR: https://github.com/chef-cookbooks/audit/pull/439 - I just want to make sure this isn't overlooked b/c it would really help make this more complete and delightful for our customers

@phiggins @tas50 hello! this is really awesome, just wanted to point out that @chef-davin did some really great work recently to add the inspec_waiver_file resource in a PR: chef-cookbooks/audit#439 - I just want to make sure this isn't overlooked b/c it would really help make this more complete and delightful for our customers

@dbright. I need to check the one I put in for the audit cookbook, I think I had a bunch more review that I worked through with @phiggins in chef/chef#10098.  I need to make sure the version I have in the audit cookbook matches the PR I have in chef-client.  I'll try to do that this evening.

hey @phiggins, I have a customer who still has this issue with the Audit cookbook, hoping we can make sure it's resolved after pulling everything into the Chef Client proper:
 Running handlers:
       [2020-10-20T20:15:35+00:00] WARN: Use of a hash array for the node['audit']['profiles'] is deprecated. Please refer to the README and use a hash of hashes.
       [2020-10-20T20:15:52+00:00] WARN: DEPRECATION: InSpec Attributes are being renamed to InSpec Inputs to avoid confusion with Chef Attributes. Use :inputs in your ki
tchen.yml verifier config instead of :attributes.

@cookiecurse ^

hey @phiggins, I have a customer who still has this issue with the Audit cookbook, hoping we can make sure it's resolved after pulling everything into the Chef Client proper:
 Running handlers:
       [2020-10-20T20:15:35+00:00] WARN: Use of a hash array for the node['audit']['profiles'] is deprecated. Please refer to the README and use a hash of hashes.
       [2020-10-20T20:15:52+00:00] WARN: DEPRECATION: InSpec Attributes are being renamed to InSpec Inputs to avoid confusion with Chef Attributes. Use :inputs in your ki
tchen.yml verifier config instead of :attributes.

@cookiecurse ^

Thanks Daniel! @phiggins the interesting find here is that if you set the attribute to something else, the warning for hash of hashes doesn't appear.
Error appears when setting up attribute like this:
default['audit']['profiles'] = [
    {
      name: 'Windows 2019 Baseline',
      compliance: 'admin/windows-2019-baseline',
    },
  ]

Which will create an attribute and display it in Automate like this:
- audit" : {
  - "profiles" : [
    - "0" : {
         "compliance" : "admin/windows-2019-baseline",
         "name" : "Windows 2019 Baseline"
       }
     ]
}

Running Chef Client 16.6.14
And instead of the default['audit']['profiles']
if you specify something like:
default['Aaudit']['profiles']
Screnshots: https://chef-success.slack.com/archives/C0DSYCWRZ/p1604422553038900?thread_ts=1603226660.015900&cid=C0DSYCWRZ
James Massardo mentioned that the correct attribute setup is:
default['audit']['profiles']['<profile name>'] = {
  compliance: 'admin/windows-patch-baseline'
}

But while without some more changes this is not working for me since my nodes stopped checking for compliance altogether so I might have missed something else.
Hope that helps! If there is anything you need me to clarify or test please let me know!

@danielcbright @cookiecurse I appreciate your concern, but this is not a good place to report bugs with audit cookbook. The priority is to get some subset of audit cookbook functionality working in chef-client and then iterate. There is lots of half-broken and old, deprecated stuff in audit cookbook and I cannot hope to fix all of it. Has an issue been filed for this on audit cookbook?

@cookiecurse Revisiting this and wanted to make sure I understood your request.
First, in two places you have default['Aaudit']['profiles'], with an extra "A" in front of "audit". You mentioned things not working with that, could it be this typo is fouling things up?
Second, you're correct, the audit-cookbook handles multiple styles of specifying inspec profiles but in this PR I plan to support only the hash of hashes style you mentioned (like in the audit-cookbook README here https://github.com/chef-cookbooks/audit#configure-node). Since the presence of profiles specified in the node attributes is how this PR is deciding whether to activate audit mode, I plan to add code to explicitly fail if that is not in the expected format. Do you have thoughts on that?

FWIW a Cinc build using this branch seems to work fine :+1:


Update Weekly External Release manifest

Update weekly manifest

Improper Commit Message
Proper Tracked on value is not present in commit message,make sure Tracked-on: jira-ticket is present


Remove unique ROID suffixes requirement

This makes the requirement of having a unique Roid suffix per tld
optional. A new parameter has been added added to config module called
"requireUniqueRoidSuffixes" which will allow setting this feature.
Possible todo: This has not been added to the CreateOrUpdateCommand
as Donuts doesn't use this feature.

I'm fixing this for you in a different way that doesn't require the addition of a config option.  You'll see that commit soon.  The gist of it is that RoidSuffixes.roidSuffixMapCache is a BiMap for historical reasons only, and can be changed to support non-unique ROID suffixes simply by making it a normal Map, which I have now done.  So this PR will be closed and not merged, but you'll get your desired functionality a simpler way.

That works. Thank you.

Merged in spirit in f7e84b56a034a9501cad584918385bab16407927.


[Bug] Button to switch between HTML preview and console

The round blue button to switch between HTML preview and console is only visible when the device orientation is in portrait mode (at least on my really wide screen smartphone)

Thank you for reporting this issue. I've fixed it.


Unify license into one file

For some reason we have a rst version of the license file. However, this file is not even used in the docs so there seems to be no point to have that so remove and just use the regular license file.
Update copyright year as well

Bors merge


Remove --etcd-quorum-read from apiserver manifests

bootstrap-apiserver logs:
Flag --etcd-quorum-read has been deprecated, This flag is deprecated and the ability to switch off quorum read will be removed in a future release.
I0127 00:51:47.792802       1 server.go:121] Version: v1.9.2

This was mentioned in the 1.9 Release Notes: Deprecation, API Machinery.

/assign @rphillips


With typescript, type inference is lost if the json returned is not an object but an array

What version of Hono are you using?
4.3.11"
What runtime/platform is your app running on?
node
What steps can reproduce the bug?
const app = new Hono()
  .get("/", async (c) => {
    const data = await readData();
    return c.json(data);
  })
  .get(
    "/filtration",
    zValidator(
      "query",
      z.object({
        pageSize: z.number().default(10),
      })
    ),
    async (c) => {
      const { pageSize } = c.req.valid("query");
      const data = await readData();
      const result = await splitArrayBySize(data, pageSize);
      return c.json(result);
    }
  );

export default app;

  client.api.issues.filtration.$get({ query: {} }).then((res) => {
    const value = res.json();
// never
  });

What is the expected behavior?
Hopefully, the result will be returned correctly
What do you see instead?
No response
Additional information
If you return objects instead, everything is fine
const app = new Hono()
  .get("/", async (c) => {
    const data = await readData();
    return c.json(data);
  })
  .get(
    "/filtration",
    zValidator(
      "query",
      z.object({
        pageSize: z.number().default(10),
      })
    ),
    async (c) => {
      const { pageSize } = c.req.valid("query");
      const data = await readData();
      const result = await splitArrayBySize(data, pageSize);
      return c.json({result});
    }
  );

export default app;

Hi, @bosens-China
I can't reproduce it. Could you provide the minimal project to reproduce it?

@yusukebe
bug like

@bosens-China Thank you!
This problem caused by result type - [number, IssuesDaum[]][] will be treated by never:

@NamesMT What do you think of this matter? [number, IssuesDaum[]][] should be valid JSON type?


Move the dependabot to weekly

We don't need to move that fast

Honestly even weekly feels fast, but it's already an improvement. At some point we were talking about moving to renovate right? So that we might also batch some of the minor version bumps etc.


Strange lines in console

Good night! Please tell me, when starting the SD, these lines appear in the console every time.
Is this normal or can I fix it somehow? when the sd-dynamic-prompts extension is disabled, these lines disappear.

Me too, these things look really annoying

That isn't a bug but I agree that it is excessively noisy.

Hmmh, that should only happen when there are out-of-date dependencies, not every time.

It happens to me every time I start((

Same happens every time for me as well.


Auth ViewSet

Hello !
Thanks for sharing this fantastic app !
Is there an open source ViewSet available for to manage auth.User (with set password like in django admin) or can this be contributed upstream ?
Thanks

The only reason I still use admin is to manage existing users, so if we could have a built in ViewSet for default User which we can adjust to our needs - that would be just perfect.

If it is possible for you, you can try to create ./templates/account/base.html, extending material/frontend/base_lockscreen.html.
{% extends "material/frontend/base_lockscreen.html" %}


Vue throws error if binding path is null

I have a dynamic component which is activated when user clicks the reset button (this button set the currentForm = 'reset'). In the reset password component template, I display error message with data from ajax call. I have ajax call inside the activate hook. To my surprise, activate hook is invoked after compiled hook and also vue throws "Uncaught TypeError: Cannot read property 'alert' of undefined" because data is not ready.
Why does Vue throws error if data is null? and also, shouldn't activate hook invoke before compiled hook? I thought it's a hook for incoming component to perform some asynchronous operation before it should be swapped in.
I'm on 1.0.10.
thanks in advance
// parent component template
components: {
        "reset": function (resolve) {
            require(['../forms/user.password.reset'], resolve)
        }
}

//html
component(:is="currentForm" keep-alive)

//child component
{
 activate:function(done) {
        var self = this;
        restApi.getMessage()..done((data)=>{
            self.validCode = data.status === 'OK';
            self.$set("i18n", data.messages);
            done();
        }).fail(()=>{
        });
    }
}

// html
   .alert.alert-success(v-if="validCode")
        h3(v-text="i18n.alert.almost.there") Almost there...

activate is fired after the component is compiled and about to be inserted. Its purpose is to control the timing of the DOM manipulation. So the hook order is compiled -> activate -> ready.
Best practice for writing expressions with potential unset property is doing a conditional check:
h3(v-text="i18n && i18n.alert.almost.there")

didn't know you can do that, that's easy. Could you explain why vue is designed to throw exception if expression binding contains null object?

It's not because it's null.
If you run this in js:
var a = null
var b = a.alert.almost.there

You get an error. Same for expressions in Vue templates.


Switch provisioners to install Go from GitHub releases on Windows

Install go versions from github releases in agent tools directory.
tested builds:

windows16
windows19

Note: for now we use json manifest from tested github repo with releases.

Why do we need two scripts to install and set variables? Can we delete Install-Go.ps1 script and move all to the Install-Toolset.ps1?

It was discussed, that Go and Boost installation scripts will be merged with Install-Toolset, in scope of the other feature.


Add support for contrast-adaptive sharpening in 3D (GLES3 only)

3.x version of https://github.com/godotengine/godot/pull/47401.
This is an older, easier to implement variant of CAS as a pure fragment shader. It doesn't support upscaling, but we won't make use of it (at least for now).
The sharpening intensity can be adjusted on a per-Viewport basis. For the root viewport, it can be adjusted in the Project Settings.
Since textureLodOffset() isn't available in GLES2, there is no way to support contrast-adaptive sharpening in GLES2.
Preview
FXAA is enabled on both screenshots.
Slider comparison
Sharpening disabled

Sharpening enabled (intensity 1.0)

This PR likely suffers from the same HDR issue as the Vulkan version, so I'll mark it as a draft until we find a way to fix it.

As before, I think the code looks fine, but we absolutely need a test scene that utilizes CAS properly to verify that it is working correctly. We can't merge graphics features without testing them.
A proper test scene for CAS is one that has textures with high frequency detail that get blurred out by FXAA. Upon turning CAS on it should restore some of the high-frequency detail while maintaining the edge antialiasing. A test scene with untextured blocks only shows that CAS adds some amount of aliasing to edges. We need a test scene that shows that this implementation of CAS sharpens high-frequency textures more than it aliases edges.

I think CAS needs to run in its own pass after tonemapping for 2 reasons:

It needs to read the output after FXAA is applied (currently only the central pixel "e" uses the FXAA colour)
It needs the input to be linear and 0-1 range otherwise we will get ringing artifacts.

For the Vulkan version you can avoid the extra pass by writing out the results to local memory and placing a barrier after tonemapping. For GLES3, you will need to break it into 2 passes. First pass should run as normal, but write to an intermediate buffer, then the second pass should apply CAS by itself.

@clayjohn Thanks for the insight :slightly_smiling_face:
Unfortunately, I don't know how to use local memory and barriers (I have no actual Vulkan exeprience).
As for running CAS in a second pass in GLES3, wouldn't that decrease performance noticeably? It also doesn't sound easy to introduce multi-pass post-processing shaders in Godot right now.
Due to this, I'll need to have someone else finish this feature if we want it to be merged in a reasonable timeframe. (Personally, I would consider the current state of this feature to be "good enough", but that's just me :slightly_smiling_face:)

There are some style issues to fix, and docs to sync. Otherwise is this ready to merge / get tested for 3.4?

I rebased and added documentation.

Thanks!

I might have merged a bit fast since I'm not sure @clayjohn's feedback was addressed. But since this is opt in, I guess we can get it tested and bugfix/adapt the implementation based on user reports in 3.4 betas?

I might have merged a bit fast since I'm not sure @clayjohn's feedback was addressed. But since this is opt in, I guess we can get it tested and bugfix/adapt the implementation based on user reports in 3.4 betas?

clayjohn's feedback doesn't seem to be essential to get working CAS (even with FXAA enabled), but it would look more correct in certain situations. From my testing, CAS looked good enough already, so I would wait and see if anyone has problems with the current implementation.

For future reference, I pushed a 3.x-compatible version of the testing project: https://github.com/Calinou/test_contrast_adaptive_sharpening/tree/3.x


FIX: Cleaner logging of baselines

Closes #2236.
Streamlines our logging messages about baselines a bit. Now it's done once per object, during instantiation / creation.

On this PR:
145 matching events found
Applying baseline correction (mode: mean)
Created an SSP operator (subspace dimension = 4)
4 projection items activated
Reading 514 ... 619  =      3.423 ...     4.122 secs...
    Rejecting  epoch based on EEG : [u'EEG 001', u'EEG 002', u'EEG 003', u'EEG 007']
Reading 712 ... 817  =      4.742 ...     5.441 secs...
Reading 933 ... 1038  =      6.214 ...     6.913 secs...
Reading 1132 ... 1237  =      7.539 ...     8.238 secs...
Reading 1330 ... 1435  =      8.858 ...     9.557 secs...
Reading 1545 ... 1650  =     10.289 ...    10.989 secs...
Reading 1753 ... 1858  =     11.675 ...    12.374 secs...
Reading 1948 ... 2053  =     12.973 ...    13.673 secs...
Reading 2153 ... 2258  =     14.339 ...    15.038 secs...
    Rejecting  epoch based on EEG : [u'EEG 001', u'EEG 002', u'EEG 003', u'EEG 004', u'EEG 005', u'EEG 006', u'EEG 007']
Reading 2377 ... 2482  =     15.830 ...    16.530 secs...

@agramfort maybe we should actually remove the Reading ...  lines altogether. Instead we can just have when big loads are to be done (e.g., during preload) Preloading data (this can take a while).... It seems a bit cleaner than always spitting out data-reading messages, which AFAICT get mostly ignored.

Actually, if we did get rid of those messages, I might actually start using set_log_level('INFO') instead of set_log_level('WARNING') since it would become actually informative / usable to have it set that way.

What would be the rationale for having/keeping the Reading... lines? Cause it seems like a no-brainer to me to lose them.

Sometimes the reads can take a long time. But I suspect we can get around that by putting in explicit messages when that is expected to occur, e.g. when doing epochs.get_data(), raw.load_data(), epochs.load_data(), etc.

Public function restored. Will work on the Reading... bits soon hopefully.

Okay this is the output for Epochs(..., preload=True, verbose=True) now, which is much more readable and informative than before -- you get a message at the beginning saying data will be loaded, then you see rejection messages:
145 matching events found
Applying baseline correction (mode: mean)
Created an SSP operator (subspace dimension = 4)
4 projection items activated
Loading data from for 145 events and 106 original time points ...
    Rejecting  epoch based on EEG : [u'EEG 001', u'EEG 002', u'EEG 003', u'EEG 007']
    Rejecting  epoch based on EEG : [u'EEG 001', u'EEG 002', u'EEG 003', u'EEG 004', u'EEG 005', u'EEG 006', u'EEG 007']
    [29 similar lines...]
    Rejecting  epoch based on EEG : [u'EEG 001', u'EEG 002', u'EEG 003', u'EEG 004', u'EEG 007']
    Rejecting  epoch based on EEG : [u'EEG 001', u'EEG 007']
33 bad epochs dropped

Ready for review/merge from my end.

LGTM

@dengemann @jona-sassenhagen @jasmainak you happy with this form of output?

Yes nice work! +1 for merge.


Issue/3055 notification badge

Description
This uses the newly proposed folder architecture with Slices.
closes #3055
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Code is clear and sufficiently documented
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches master, iso5 in cac87078ccd2852a056d487ae476e198bcd8eaab


Updated subgraph for DAO new address

Dao Delegator Address : 0x39312C0bD4a7b9C0435a1bf4dD873AB0D379CbEc
Timelock deployed to: 0x77265e364a467366e638bd40F61538A6F3Cd321b
GovernorBravoDelegate deployed to: 0x39312C0bD4a7b9C0435a1bf4dD873AB0D379CbEc
GovernorBravoDelegator deployed to: 0x4670EB36c324c871224F719097c30770eff169e8

@wsdt can you please help me to publish the boba/register once with changes from this PR?

sure @sk-enya just let me know once you are ready.


Remote Debugging Fails

When I try to turn on remote debugging I get a "The remote server returned an error: (403) Forbidden" when it tries to configure the scaleset. I'm running VS 2019 in admin mode. The scale sets are 2019-Datacenter-Core-with-Containers.

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

ID: e8adfa1c-0bb9-c112-3463-0d655a3e7cd1
Version Independent ID: ef09b17d-cebf-56ca-7f59-71dba2dc3123
Content: Debug your application in Visual Studio - Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-debugging-your-application.md
Service: service-fabric
GitHub Login: @vturecek
Microsoft Alias: vturecek

@festivus
Thanks for the feedback! We are currently investigating and will update you shortly.

@festivus I tried in my environment and i am unable to reproduce your issue. But i used VS2017
Are you still facing the issue?

@festivus I tried in my environment and i am unable to reproduce your issue. But i used VS2017
Are you still facing the issue?

@jakaruna-MSFT Sometimes. I did get it work, but I'd say this happens about 50% of the time. You can close it if you want.

I'm having the same problem:
When I try to turn on remote debugging I get a "The remote server returned an error: (403) Forbidden" when it tries to configure the scaleset. I'm running VS 2019 in admin mode.

Send your subscription id to this email id<EMAIL_ADDRESS>I will enable a one time free support ticket for you.  In the email include this github issues url and the title in the subject.  Append "for jakaruna-msft" in the subject.
Once your issue is resolved, Then post the resolution here.

I have received no messages in regard to the support ticket.  Please Advise.
Glenn
On Wed, Mar 4, 2020 at 2:30 AM jakaruna-MSFT<EMAIL_ADDRESS>wrote:

Send your subscription id to this email id<EMAIL_ADDRESS>I will enable a one time free support ticket for you. In the email include
this github issues url and the title in the subject. Append "for
jakaruna-msft" in the subject.
Once your issue is resolved, Then post the resolution here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/48521?email_source=notifications&email_token=ACDHE5XT2RFXLY2NTMM6BBDRFYUUFA5CNFSM4KYFYV3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENXHR7Q#issuecomment-594442494,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDHE5U2N4YR6HW7GH2MTGDRFYUUFANCNFSM4KYFYV3A
.

@festivus I didnt get any email.
If you have sent one, Please share the subject of the email so that i can search and find the email

@festivus i didnt get any email from you.
Feel free to send a email when you are ready.
I will close this out for now. If you need additional help please open a new issue


Chapter 1: Provide explicit directions to change the version of Vuetify

I'm, currently, in a workshop and many of the participants had issues with properly implementing vuetify.  There is a note that your dependencies should look like this:
"dependencies": {
  "vue": "^2.5.2",
  "vuetify": "1.2.9"
},

but codesandbox.io installs the latest version of vuetify (2.0.4) which is incompatible with the code we are provided.  It caused all the screens to become blank.
We had to explain that it needed to be changed, to 1.2.9, but I'm not sure if it's easier to update the code or to provide an explicit note such as "Check the versions and make sure your code looks like this."

Excellent note, we need to either
1 - pin to an older version of Vuetify
2 - redo our instructions
or
3 - remove Vuetify

We have decided to do #2 - no pun in tended...
https://codesandbox.io/s/vue-template-new-vuetify-bootstrap-qkd84?fontsize=14
We can instruct folks to add a plugins folder and a script file. It's not a big change
Note, we need to change the German translation as well, and the /projects repo needs fixing too.

sorted!


Implements missing methods in Key.go

You're mixing gx dependencies and non-gx dependencies. You'll need to either run gx-go rw --fix in your project to unrewrite the paths or run gx import github.com/libp2p/go-libp2p-crypto to import this package into your package.json file.


Adding simple guides for PBjam hackday

Added:
Examples/example_docstrings.rst
Examples/example_unittests.rst
Examples/example_githubworkflow.rst
Also updated the CONTRIBUTING.rst a bit.

Someone has turned all the tests into strings with ''', I think this conflicted with the ''' from the docstrings for the tests, causing the checks to fail.
Still doesn't seem to complete the checks through, whatever they are.

@grd349 can you merge this? I don't have permission.
Then I can send round the update email about the hackday.

Done @nielsenmb


Compile error

Hi all,
I am a novice trying to use the clarity analyzer as the data replay parser. I successfully use mvn package to compile the program but when I tried to run the program I encounter compile error.
JarClassLoader: Warning: javax/servlet/ServletRequest.class in lib/security-api-1.1-rev-1.jar is hidden by lib/servlet-api-3.0-alpha-1.jar (with different bytecode)
JarClassLoader: Warning: Null manifest from input stream associated with: lib/jaxrpc-api-1.1.jar
JarClassLoader: Warning: javax/servlet/ServletException.class in lib/jsp-api-2.1-rev-1.jar is hidden by lib/servlet-api-3.0-alpha-1.jar (with different bytecode)
JarClassLoader: Warning: javax/servlet/ServletRequest.class in lib/jsp-api-2.1-rev-1.jar is hidden by lib/servlet-api-3.0-alpha-1.jar (with different bytecode)
JarClassLoader: Warning: javax/servlet/ServletContext.class in lib/jsp-api-2.1-rev-1.jar is hidden by lib/servlet-api-3.0-alpha-1.jar (with different bytecode)
JarClassLoader: Warning: javax/servlet/ServletException.class in lib/jstl-api-1.2-rev-1.jar is hidden by lib/servlet-api-3.0-alpha-1.jar (with different bytecode)
JarClassLoader: Warning: javax/servlet/ServletRequest.class in lib/jstl-api-1.2-rev-1.jar is hidden by lib/servlet-api-3.0-alpha-1.jar (with different bytecode)
JarClassLoader: Warning: javax/servlet/ServletContext.class in lib/jstl-api-1.2-rev-1.jar is hidden by lib/servlet-api-3.0-alpha-1.jar (with different bytecode)
Exception in thread "main" java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at com.simontuffs.onejar.Boot.run(Boot.java:340)
at com.simontuffs.onejar.Boot.main(Boot.java:166)
Caused by: java.lang.Error: Unresolved compilation problem:
The method launch(String[]) is undefined for the type Main
    at skadistats.clarity.analyzer.Main.main(Main.java:31)
    ... 6 more

Plz help, thanks!

Using JDK 8 might help...

@spheenik I'm currently using <IP_ADDRESS>1 but it's still failing to compile

Please upload the resulting jar somewhere so I can have a look at it.


Supporting vendor specific metadata on Span

As this topic keeps re-emerging, I'd like to kick-off a discussion about providing a formal way to provide vendor-specific metadata on spans.
I am advocating for a formal way / a dedicated property because it would make sure that a span is still well defined and typed, even if vendors want to use it as a container for some proprietary use cases.
As far as I understand it, the use case is that
As a vendor I want to put data on a span and I want this data to be exported to my backend later.
Am I right, that this does not include propagating this metadata?
FYI @rochdev

While correct, I feel the statement is incomplete. The requirement also includes things like propagation, and sometimes might not even be related at all to the exporter. The idea is that vendors should be able to attach arbitrary data to the span at any point, and alter or recover it at any point, regardless of the current state of the span lifecycle. This should be implemented in a way that won't impact the tracer itself or other vendors.

@rochdev, would it be possible for you to sketch out an API surface that would fulfill that?

I feel having some kind of Interceptor API on the different lifecycle's event of the span would allow for this behavior.
First list of event that comes to my mind:

create
end
serialized (for propagation)
deserialized (for propagation)
export

Hooks were discussed on one our meeting on 2019-07-17 and I agree that this would be great to have.
I am not sure if it would solve the metadata topic. I would more think of a 'vendor' property that can contain anything a vendor wants to pass along. Ideally indexed by some namespace like a vendor prefix.

I agree these are 2 different topics. Basically I would expect the hooks to interact with the metadata, but it's unrelated to having an explicit API for the metadata.
Maybe it could be as simple as some kind of setVendorMetadata(name: Symbol, meta: unknown) method. By using a Symbol we would ensure there is no conflict.

That sounds good to me @rochdev. I will see if other languages would want that as well.

@dyladan, what was the idea behind adding the label?
To me, this sounds like span attributes that have API. Additionally, there's

Custom SpanProcessors which can change Spans however way anyone pleases,
Resource API which can achieve adding vendor specific attributes.

Closing this for now. Daniel will reopen as he sees fit.


Constrain type parameter of RootSpanBuilder::on_request_end with actix_web::body::MessageBody

Is it possible to change the API to change the following in RootSpanBuilder:
fn on_request_end<B>(span: Span, outcome: &Result<ServiceResponse<B>, Error>);

to the following?:
fn on_request_end<B: MessageBody>(span: Span, outcome: &Result<ServiceResponse<B>, Error>);

This will allow using methods defined for MessageBody when creating custom RootSpanBuilders, such as MessageBody::size. The root span is always called on MessageBodys anyway, as seen here:
https://github.com/LukeMathWalker/tracing-actix-web/blob/c95a781204e8075ebb8b6116f280f0cfdb88dcb5/src/middleware.rs#L181-L198
I can create a PR if this is fine.

Yes, a PR would be welcome!

Merged and released as 0.7.0 - thanks!


Email signup style updates

Makes some small tweaks to email signup styles, mostly related to H3 header and inline disclaimer options
Changes

Inline disclaimer and button sit on same baseline
Inset email signup gets 15px left/right padding at 320px & below
Inline disclaimer display starts above 320px
On browse pages, inset email takes up 4 of 9 columns above 650px
Email signup label drops to 16px on mobile (it's currently styled as an H4, but we now have the option for an H3 header on the signup, which drops to H4 on mobile)

Testing

Check out branch
Run gulp build
Create a browse page. Add a full width text module with an inset email that has an inline disclaimer
Verify email signup displays as expected across page widths

Screenshots
Inline disclaimer/button positioning

Inset email at 320px breakpoint

Inset email at 4/9 columns on browse pages

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the development playbook
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ ] Project documentation has been updated
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist
Browsers

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Internet Explorer 8, 9, 10, and 11
[ ] Edge
[ ] iOS Safari
[ ] Chrome for Android

Accessibility

[ ] Keyboard friendly
[ ] Screen reader friendly

Other

[ ] Is useable without CSS
[ ] Is useable without JS
[ ] Flexible from small to large screens
[ ] No linting errors or warnings
[ ] JavaScript tests are passing

@virginiacc What's the status on this PR? Is it still useful? If so, let's get it updated/reviewed. Thanks!

Thanks for reviewing, @jimmynotjim!


wired-card calls non-existing this._requestRender()

<wired-card> calls this._requestRender() when the slotchange event is fired. However, that method does not exist on the elemnt.
https://github.com/wiredjs/wired-elements/blob/da4f150c04a336df41e228b794f14663f54b6d6f/packages/wired-card/wired-card.js#L55
<wired-card> depends on Lit Element ^0.5.1. I've checked the source code of Lit Element, and it looks like they renamed it to this.requestRender():
https://github.com/Polymer/lit-element/blob/fb90e7640777cab01c9eac2006cde558c34b041d/src/lit-element.ts#L261
(I did a quick search and noticed a few more places that call _requestRender().
I was using <wired-card> by importing it form unpkg:
<script type='module' src='https://unpkg.com/wired-card@0.6.0/wired-card.js?module'></script>

Sure enough, lit-element changed their API in 0.5.2 and that version is getting picked up. They should have used 0.6 for breaking changes fo semVer to work.
In the short term, if you can explicitly depend on lit-element 0.5.1, you may avoid running into this issue.

Resolved by upgrading to latest lit-element and adjusting code accordingly:
https://github.com/wiredjs/wired-elements/pull/32
Fix in v0.6.5

Thanks 🙂
Now featuring Wired JS in the custom cards example for Home Assistant https://developers.home-assistant.io/docs/en/lovelace_custom_card.html#defining-your-card

@balloob looks cool