Middleware topic+sample update

Addresses #5495
Fixes #8071
Internal Review Topic
UE pass includes ...

xref API links.
Topic links updated to xref format.
Gerunds removed from section headings.
💐 Table Beautification 🌷

Samples converted to snapshots because ...

There are only a couple of examples here.
The examples are trivial.
The code hasn't changed 1.x to 2.x, nor is it likely to change going forward (e.g., 3.0).
The current samples are 🤦♂ project.json/xproj-based 🙈, and we haven't heard a peep out of the community on these samps not working. AFAICT nobody is using these trivial samples.

I don't see any changes to ASP.NET Core Middleware


N region in plot

Hi,
I found that haphic plot deal with signal in N region in a wrong way,
here is haphic plot (N region is so heat),

it should be

Heat signal in N region may misleading readers some times, I think.
Best,
Kun

Hi Kun,
This issue may be raised by KR normalization. Could you please try using the parameter --normalization none ?
Best regards,
Xiaofei

Hi Xiaofei,
Yes, the heat signal in N region disappeared when using parameter --normalization none.
Best,
Kun

I'll fix the problem soon. Thanks!

By the way, log10 normalization seem not work well for my data, do you know why?
KR

none

log10

Best,
Kun

This phenomenon is quite normal. Log10 compresses the range of Hi-C links, causing the interaction intensity within chromosomes to resemble the interaction intensity between chromosomes. In general, it is not recommended to use Log10 for normalization purposes.

I see, thank very much.

I have fixed this bug in the latest commit, you could give it a try. Thanks again!

It is OK now. You can close this issue as the bug has been fixed.


Please Register Loot Tables to allow LootTweaker Integration (suggestion)

In developing my modpack I discovered that NetherEX was not registering any loot tables for the mobs it adds. This is an issue because without appropriately registered loot tables the modpack development tool LootTweaker cannot edit the drops for a mob. I would love to use LootTweaker to add drops to the various NetherEX mobs as they make very frightening adversaries and they should have rewards that are appropriate for their difficulty, but unfortunately with unregistered loot tables I cannot do that.
To confirm that this wasn't a mod interaction with another mod in my pack, I made a new instance with the following details:
Minecraft v1.12.2
Forge v<IP_ADDRESS>95
CraftTweaker v4.1.13
LibEx v1.0.8
LootTweaker v0.0.8
NetherEX v2.0.8
In this instance, I created a new world and used the command "/ct loottables all" to dump all registered loot tables. I then checked in the "[Instance]\dumps\loot_tables" directory and confirmed that no loot tables were dumped that originated from NetherEX.
In the mean time, if you cannot push an update that registers this mod's loot tables for whatever reason, if you could post the locations of the loot tables within the mod I could potentially use that to hack together a way to edit the loot tables. Currently LootTweaker cannot do this, but in their upcoming 0.0.9 release they're adding a way to edit an unregistered loot table, but only if you already know its directory path. Without knowing where to write to that feature is insufficient - I need your help to find the directory path.
Thank you for your time and understanding.

I also understand that this would help enable integration with Just Enough Resources, a JEI addon that displays monster and chest loot. Like LootTweaker, JER finds the data it displays by using the list of registered loot tables, so if your loot tables are unregistered it cannot detect them. I'm not certain if it's automatic past that point or not, there may be another step, but I know getting the loot table registered is one of the steps.

I'm working on, I hope the PR will be ready soon.

It looks like JER can't read modded mobs' loottables properly, as a guy from ModdedMC Discord told me. And I can't get anything working using jei+jer api.
If you have an example of mod that made custom mob loottables, please tell me

I got it!

I can't get the loottables. When I dump all tables with looktweaker, there is no folder for netherex. Am I doing something differently?

This will be fixed in upcoming release.


Build integration - Allow addition of priorly uploaded artifacts to bill-of-materials

Hi,
Currently it's not possible to add priorly uploaded artifacts to the local bill-of-materials. In our use-case,  uploading of artifacts doesn't happen through the CLI and neither do we use the related features available in some of the CI tools (e.g. Jenkins, Bamboo, etc.). To be able to leverage the benefits of Build Integration we would thus either have to manually create the build info JSON, or would have to add support for such a use-case to the CLI.
Feature request is thus to add support for adding already uploaded artifacts to the local BOM. Would this be a welcome addition to the tool?
Thanks!

@rein-achten,
To help us better understand your use case, can you share with us how your artifacts are deployed to Artifactory? Are you using a specific build or deployment tool to upload the files?

@eyalbe4
Other than what I mentioned in https://github.com/JFrogDev/jfrog-cli-go/pull/77#issuecomment-321158939, we're using CMake in combination with Ivy to manage C++ binary dependencies.


Fix MUMPS libraries link sequence

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#4214
@adam-sim-dev
@v-dobrev
@johnbowen42 + @psocratis + @v-dobrev
3/27/24
4/12/24
⌛due 4/17/24

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Should we include in this PR the changes mentioned in this comment: https://github.com/mfem/mfem/pull/3922#issuecomment-2023779007?

Should we include in this PR the changes mentioned in this comment: https://github.com/mfem/mfem/pull/3922#issuecomment-2023779007?

My vote is yes.

Lets make the changes from #3922 (comment) here, @adam-sim-dev can you do that?

@adam-sim-dev, let me know if you need help with this, e.g. the CMake updates.

Lets make the changes from #3922 (comment) here, @adam-sim-dev can you do that?

@adam-sim-dev, let me know if you need help with this, e.g. the CMake updates.

Which variable (like MFEM_USE_SINGLE) should I use in FindMUMPS.cmake?

@johnbowen42, can you help with the CMake modifications here as we discussed earlier?

Merged in next for testing...

@johnbowen42, thank you for the CMake updates!
@psocratis, there were some more changes after you approved -- take another look if you want.
@adam-sim-dev, thank you for the fixes. If you use CMake, can you confirm that @johnbowen42's updates in CMake work for you?

By the way, I tested this PR with both GNU make and CMake and both single and double precision -- everything seems to work as expected.

Re-merged in next for testing...


Fix declaration file

It seems like tsconfig extends no longer extend the exlcude field properly.

Codecov Report

Merging #1354 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1354      +/-   ##
==========================================
+ Coverage   99.32%   99.33%   +<.01%
==========================================
  Files         373      373
  Lines        9251     9258       +7
  Branches     2238     2242       +4
==========================================
+ Hits         9189     9196       +7
  Misses         62       62

Impacted Files
Coverage Δ

...ackages/react-vapor/src/components/title/Title.tsx
100% <0%> (ø)
:arrow_up:

...c/components/refresh/ButtonWithRefreshCallback.tsx
96.42% <0%> (+0.59%)
:arrow_up:

Continue to review full report at Codecov.

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


Re-register as sole voter causes Drep retirement

Context & versions
staging.sanchonet
Steps to reproduce

Be a retired sole voter that's registered as a DRep
Un-Retire as a Sole Voter

Actual behavior
DRep card shows "you are retired as a DRep"
https://www.loom.com/share/365a8d4ce779472cac0a9faafa352011?sid=ac020b5a-9c99-4972-b2b2-9e34de960627
Expected behavior
Drep card doesn't show "you are retired as a Drep" DRep card shows default (unregistered) version.

This scenario and others like it warrant more investigation. As users change roles, we need to track what the interface says, as their history can become complicated. We seem to have designed for one change of roles ok, but as multiple roles change, this system breaks.
The above is why for the time being this is assigned to @m-i-k-e

Closed as not an issue now


Cannot deploy to Heroku

Runs perfectly on localhost.
Heroku error logs
2014-11-26T21:12:22.141799+00:00 heroku[web.1]: State changed from crashed to starting
2014-11-26T21:12:32.932667+00:00 heroku[web.1]: Starting process with command `bundle exec thin start -R config.ru -e production -p 23294`
2014-11-26T21:12:40.618062+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/1.9.1/io/open.rb:2:in `close': Bad file descriptor - /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/1.9.1/io/open.rb (Errno::EBADF)
2014-11-26T21:12:40.618144+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/1.9.1/io/open.rb:2:in `<top (required)>'
2014-11-26T21:12:40.618185+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require_with_backports'
2014-11-26T21:12:40.618165+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require'
2014-11-26T21:12:40.618206+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:22:in `block in require_relative_dir'
2014-11-26T21:12:40.618123+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/1.9.1/io/open.rb:2:in `open'
2014-11-26T21:12:40.618261+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/1.9.1/io.rb:3:in `<top (required)>'
2014-11-26T21:12:40.618392+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require'
2014-11-26T21:12:40.618224+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:21:in `each'
2014-11-26T21:12:40.618243+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:21:in `require_relative_dir'
2014-11-26T21:12:40.618299+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require_with_backports'
2014-11-26T21:12:40.618318+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:22:in `block in require_relative_dir'
2014-11-26T21:12:40.618430+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/1.9.2.rb:2:in `<top (required)>'
2014-11-26T21:12:40.618410+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require_with_backports'
2014-11-26T21:12:40.618336+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:21:in `each'
2014-11-26T21:12:40.618280+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require'
2014-11-26T21:12:40.618355+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:21:in `require_relative_dir'
2014-11-26T21:12:40.618373+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/1.9.1.rb:3:in `<top (required)>'
2014-11-26T21:12:40.618467+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require_with_backports'
2014-11-26T21:12:40.618448+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require'
2014-11-26T21:12:40.618485+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/1.9.3.rb:2:in `<top (required)>'
2014-11-26T21:12:40.618504+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require'
2014-11-26T21:12:40.618541+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/1.9.rb:2:in `<top (required)>'
2014-11-26T21:12:40.618522+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require_with_backports'
2014-11-26T21:12:40.618559+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require'
2014-11-26T21:12:40.618634+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require_with_backports'
2014-11-26T21:12:40.618653+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/2.0.rb:2:in `<top (required)>'
2014-11-26T21:12:40.618672+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require'
2014-11-26T21:12:40.618578+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require_with_backports'
2014-11-26T21:12:40.618596+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/2.0.0.rb:2:in `<top (required)>'
2014-11-26T21:12:40.618616+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require'
2014-11-26T21:12:40.618690+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require_with_backports'
2014-11-26T21:12:40.618709+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/2.1.0.rb:2:in `<top (required)>'
2014-11-26T21:12:40.618803+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require_with_backports'
2014-11-26T21:12:40.618763+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/2.1.rb:2:in `<top (required)>'
2014-11-26T21:12:40.618784+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require'
2014-11-26T21:12:40.618820+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports.rb:3:in `<top (required)>'
2014-11-26T21:12:40.618745+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require_with_backports'
2014-11-26T21:12:40.618727+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/backports-3.6.0/lib/backports/tools.rb:343:in `require'
2014-11-26T21:12:40.618857+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/sinatra-contrib-1.4.2/lib/sinatra/capture.rb:3:in `<top (required)>'
2014-11-26T21:12:40.618876+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/sinatra-contrib-1.4.2/lib/sinatra/content_for.rb:2:in `require'
2014-11-26T21:12:40.618839+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/sinatra-contrib-1.4.2/lib/sinatra/capture.rb:3:in `require'
2014-11-26T21:12:40.618894+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/sinatra-contrib-1.4.2/lib/sinatra/content_for.rb:2:in `<top (required)>'
2014-11-26T21:12:40.618951+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/dashing-1.3.4/lib/dashing.rb:3:in `require'
2014-11-26T21:12:40.618913+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/dashing-1.3.4/lib/dashing/app.rb:3:in `require'
2014-11-26T21:12:40.618969+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/dashing-1.3.4/lib/dashing.rb:3:in `<top (required)>'
2014-11-26T21:12:40.618990+00:00 app[web.1]: 	from config.ru:1:in `require'
2014-11-26T21:12:40.618932+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/dashing-1.3.4/lib/dashing/app.rb:3:in `<top (required)>'
2014-11-26T21:12:40.619046+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `initialize'
2014-11-26T21:12:40.619008+00:00 app[web.1]: 	from config.ru:1:in `block in <main>'
2014-11-26T21:12:40.619028+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `instance_eval'
2014-11-26T21:12:40.619065+00:00 app[web.1]: 	from config.ru:1:in `new'
2014-11-26T21:12:40.619102+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/rack/adapter/loader.rb:33:in `eval'
2014-11-26T21:12:40.619084+00:00 app[web.1]: 	from config.ru:1:in `<main>'
2014-11-26T21:12:40.619120+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/rack/adapter/loader.rb:33:in `load'
2014-11-26T21:12:40.619211+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/thin/runner.rb:155:in `run!'
2014-11-26T21:12:40.619230+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/bin/thin:6:in `<top (required)>'
2014-11-26T21:12:40.619157+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/thin/controllers/controller.rb:72:in `start'
2014-11-26T21:12:40.619193+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/thin/runner.rb:199:in `run_command'
2014-11-26T21:12:40.619249+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/bin/thin:23:in `load'
2014-11-26T21:12:40.619268+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/bin/thin:23:in `<main>'
2014-11-26T21:12:40.619139+00:00 app[web.1]: 	from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.2/lib/thin/controllers/controller.rb:182:in `load_rackup_config'
2014-11-26T21:12:41.561471+00:00 heroku[web.1]: State changed from starting to crashed

Seems to have been answered here too:
http://stackoverflow.com/questions/27167440/dashing-does-not-run-on-heroku

@tylermauthe thanks I will give it a try

I fixed this by running:
bundle update back ports
and making sure my Gemfile.lock was updated and committed.

Closing for now. If @tylermauthe's suggestion doesn't work, just re-open.


[Feature] Please support EfficientDet.

What's the feature?
EfficientDet is a well-known model.
Please help support this model.
Any other context?
No response

We do have plans in the following few months. EfficientNet is already supported.

We do have plans in the following few months. EfficientNet is already supported.

[OK]

I guess this issue is solved by this PR: https://github.com/open-mmlab/mmdetection/pull/9810.


重新运行时报无法将view.dll复制到bin文件夹下

重新运行时报无法将view.dll复制到bin文件夹下

Not enough details about the issue for us to be able to help.


Remove support for downloading CSVs from Google Docs

The Google version hasn't been kept up to date with the version in the repo, and it's a bit weird to still have this anyway.
Fixes #496

There is one bug fix in the google sheet which hasn't made it to an MR yet - @francislaus are you planning to do that?
I'm not planning to remove the google sheet as maintaining the CSV without it will be a real pain, we'll need a flow for doing that (possibly to/fromyaml) first.

You can edit the CSV directly using a CSV editor no? I don't see any features except for colours that are used in the Google Doc that aren't preserved in the CSV.
Here's one I like in VSCode:

It's write format doesn't quite match what Google Docs outputs (Google outputs ,"", for empty fields), but they seem to be on their own there. LibreOffice and Gnumeric and that extension just do ,, so I'd suggest just switching to that.

I also think it's time to change the source of truth to be the repository. I can also edit the CSV as a table in Intellij:

We could convert it to YAML to make it easier to edit, but I'm not sure that's really necessary?


Class-Friendly Device

Allows the subclassing of Device and adding tasks/threads via the Device.task and Device.thread decorators.
TODO: Add documentation.

I've had a play with this, and it significantly improves upon the previous method - really good job! 🥳
I'd still like to have a reserved method for initiating global/self variables (e.g. __init__(self):).
I had an issue with a neopixel where I use a function call to fade it in and then another function call to fade it out - however, when running the second function, it does a very brief OFF (presumedly because I need to re-instantiate the Pin). I resolved that by naming the Pin before defining methods:
device = belay.Device('/dev/cu.SLAB_USBtoUART', 115200)
device("from neopixel import NeoPixel; np = NeoPixel(Pin(2), 12, bpp=4)")

I haven't tested this with the new class device though - I can check tomorrow.
I had a feeling it would also improve timing precision, but from brief testing (only with the on-board LED on RPi Pico W) it doesn't seem so.
Regardless, having reserved space for defining variables and pins would be super valuable. 😊

I'll see what I can do for the globals in another PR; for now I'm going to update some docs and merge this.


Arrays with length > MAX_INT

We allow arrays creation with length > MAX_INT, but it breaks logic in many places.
Here's test that shows bad behavior:
// we create 2D array, total nr. of elements is 2.4B elements, > MAX_INT
INDArray huge = Nd4j.rand(8000000, 300);

// we apply element-wise scalar ops, just to make sure stuff still works
huge.subi(0.5).divi(2);

// now we're checking different rows, they should NOT equal
INDArray row0 = huge.getRow(100001);
INDArray row1 = huge.getRow(100002);
assertNotEquals(row0, row1);

// same idea, but this code is broken: rowA and rowB will be pointing to the same offset
INDArray rowA = huge.getRow(huge.rows() - 3);
INDArray rowB = huge.getRow(huge.rows() - 10);

// safety check, to see if we're really working on the same offset.
rowA.addi(1.0);

// and this fails, so rowA and rowB are pointing to the same offset, despite different getRow() arguments were used
assertNotEquals(rowA, rowB);

Follow up from this issue: https://github.com/deeplearning4j/nd4j/issues/1644

Essentially what happens behind the scene: offset used everywhere is int value.

@raver119 isn't this a consequence of #1107 #1026 ?

Fixed

@raver119 👏


Orchestrator: delete resources, containers and images after some time

We shouldn't delete them right away, because logs will then be inaccessible. Another option would be to connect execution container to loki, then logs will be persisted.
Also, after image is built, we can delete cloned resources. Alternatively, implement #118 instead

retention tasks


WorkflowRunsOperations.list arguments top and filter not working?

Dear,
I'm trying to use the list method of the WorkflowRunsOperations, but when I specify top=5 for example, I still seem to be getting all runs. It's as if the top argument is not taken into account?
Additionally, I'm trying to use the filter on StartTime, but keeps giving a "not valid or not supported" error. Things I've tried so far:

filter="StartTime>2021-11-23 00:00:00"
filter="StartTime>2021-11-23Z00:00:00"
filter="StartTime>'2021-11-23Z00:00:00'"
filter="StartTime>'2021-11-23'"
filter="StartTime>2021-11-23"

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

ID: 8321b046-0079-e62b-2006-b0c58b90eadf
Version Independent ID: 62407551-e186-893d-8143-5b4aad731031
Content: azure.mgmt.logic.operations.WorkflowRunsOperations class
Content Source: docs-ref-autogen/azure-mgmt-logic/azure.mgmt.logic.operations.WorkflowRunsOperations.yml
GitHub Login: @lmazuel
Microsoft Alias: lmazuel

For the "filter" argument, the right syntax seems to be:
StartTime gt 2021-11-23T00:00:00Z
For the "top" argument, still not picking up the integer value, also tried passing it as string.

@c4g-wv Thanks for your feedback, we'll investigate asap.

@c4g-wv Would you mind providing the code snippet you are using to get the results ?

@SaurabhSharma-MSFT test code could look something like this:
logicClient = LogicManagementClient(DefaultAzureCredential(), *sanitized subscr id*)
it = logicClient.workflow_runs.list(*sanitized rg name*,*logic app name*,top=1)
for i in it:
	print(i)

fyi: tested it on python 3.8 and 3.9

@c4g-wv I have tested this in my environment and you are correct filter works with the time format - 2021-11-23T00:00:00Z.

Also, I have also tried with using top but it does not work for me either.
Though I have tested the Workflow-Runs rest API and it worked fine with REST endpoint.
https://management.azure.com/subscriptions/{{subscriptionId}}/resourceGroups/{{resourceGroupName}}/providers/Microsoft.Logic/workflows/{{workflowName}}/runs?api-version=2016-06-01&$filter=StartTime ge 2021-11-23T00:00:00Z&$top=2
I am checking internally on the same and get back to you.
Thanks
Saurabh

@c4g-wv the list method here returns an object of type AsyncItemPaged which basically iterates through all the pages until there are none. The top parameter is actually working here but you end looping through pages of 5 entries. Either you could use a regular for loop and it.next() the fixed number of times like this
logicClient = LogicManagementClient(DefaultAzureCredential(), "sub-id")
it = logicClient.workflow_runs.list("rg-name", "la-name", top = 5)
for i in range(0, 5):
    curr = it.next()
    print(curr)

Or just loop through the first page like this
logicClient = LogicManagementClient(DefaultAzureCredential(), "sub-id")
pages = logicClient.workflow_runs.list("rg-name", "la-name", top = 5).by_page()
for i in pages.next():
    print(i)

@PramodValavala-MSFT : thanks for looking into it. I agree, there are workarounds, but it's not how I expect it to work. Through REST API, it is properly giving 1 result back. Also, the "filter" argument is giving a proper reduced list (both in REST API and logicClient.workflow_runs.list function), so I'm not quite clear why it would have to be different for the "top" argument.

@c4g-wv You are right. In fact, the first response does return just five results, but the problem seems to be that the service returns a nextLink which the SDK uses to fetch consequent pages when iterating. AFAIK it should not be set when using top but either way, I will share this feedback with the concerning team and get back to you.

@c4g-wv Please let us know if you have any additional questions else we will proceed with the closure of this issue.

@SaurabhSharma-MSFT : Personally, I don't consider the issue closed. There is a workaround, I agree, but the parameter does not behave the way it's supposed to behave. Though, if the development team has decided not to fix it, then you can go ahead with closure.

Given the linked PR was closed as completed. I will close this one. Please feel free to reopen it if it is not solved.


Build arm64

Adds support for building and pushing arm64 Docker images
Updates kubectl to v1.13.1

Since Quay does not currently support "fat manifests", the images are tagged the same way with the addition of the -arm64 suffix for the new architecture.
Tested on my Kubernetes 1.13.1 Pine64 cluster.
time="2018-12-27T22:48:54Z" level=info msg="Kubernetes Reboot Daemon: build-arm64-114c349"
time="2018-12-27T22:48:54Z" level=info msg="Node ID: kube-node-1"
time="2018-12-27T22:48:54Z" level=info msg="Lock Annotation: kube-system/kured:weave.works/kured-node-lock"
time="2018-12-27T22:48:54Z" level=info msg="Reboot Sentinel: /var/run/reboot-required every 1h0m0s"

Would you mind removing the kubectl version update? I'd prefer to do that in a separate PR as it's also necessary to updatek8s.io/client-go and transitive deps...

@bboreham Agreed.  My first pass is basically just to get it working.  I am new to make so will need to play around with things but I should be able to dedicate some time this weekend to DRYing it.

@awh I reverted to 1.12.1, will that work or is 1.12.4 better?

1.12.1 is good thanks that's what's on current master :+1:

@bboreham @awh Ping?

Is there anything we can do to progress this PR along?

Needs rebase, at least.
If it ended with a multi-arch manifest we wouldn't need the sed bit in the instructions.

It should be easier to do this now that we removed the kubectl binary from kured.


make windows without decorations resizable and movable in macos

fixes #368
The subclassing logic was copied from servo's fork of glutin:
https://github.com/servo/glutin/blob/63026a0f4c8ba8bdc40787f8305ab008e5eb45e3/src/api/cocoa/mod.rs#L418

The window is not movable at that point.
I'm not 100% sure what kind of behavior we want to achieve here. Like… how will drag-to-move work, or should we keep the window buttons, the rounded corner and the shadow.
But maybe adding these masks will make the window look better?
NSBorderlessWindowMask
NSTitledWindowMask
NSResizableWindowMask
NSFullSizeContentViewWindowMask
NSClosableWindowMask
NSMiniaturizableWindowMask

To be clear, this behavior is with and explicit with_decorations(false). I have it running this way in a local build of alacritty, and it's exactly what I want. I think granular control of those masks makes more sense as platform attributes. I use a separate program to move/resize windows (hammerspoon), and I like the square corners and no border look.

how will drag-to-move work

I've tested with
        .with_movable_by_window_background(true)
        .with_decorations(false)

and that creates an undecorated window that is movable by dragging anywhere in the window.
Maybe it makes sense for most or all of those separate masks to be granularly configurable as separate platform attribute methods, with with_decorations(false) resolving to some sane default preset combination of those methods?
I'd be happy to add that to this PR if that's the direction we want to go. I think it makes the configuration story for downstream projects a little complicated, though. E.g., currently alacritty just exposes a platform-agnostic boolean decorations field. I'm not sure how alacritty would expose these platform specific attributes through its config yaml file, or if @jwilm would event want to expose that level of granularity. I'll let him weigh in if he'd like.

So there are 3 different setups:

titlebar + window controls + round borders
window controls + round borders
nothing + no round borders

winit only have one switch. So we need to pick between window controls or nothing.
Let's go for the current setup (nothing).
If anyone wants to add back the window controls, they can use WindowExt::get_nswindow() to reset the mask. In Alacritty, you could expose these 3 options.

You moved from NSFullSizeContentViewWindowMask to NSBorderlessWindowMask and removed the closable and miniaturizable masks. Can you explain exactly why these were necessary?

NSFullSizeContentViewWindowMask to NSBorderlessWindowMask

My understanding of NSFullSizeContentViewWindowMask is that it's for extending the content view into the title bar area. In my testing, it doesn't appear to have any effect when there is no title bar. The closable and miniaturizable masks also don't appear to have any effect when there's no title bar. If they were there for some reason I missed, I'd be happy to add them back.

So I think this PR achieves:

nothing + no round borders

While https://github.com/tomaka/winit/pull/389 would allow:

window controls + round borders

Ok. That works for me.
@tomaka happy with these changes?

Are we sure this behavior is something we want implicitly true with the with_decorations flag?  This is also inconsistent with other platforms - I know resizing a borderless window isn't allowed in Windows, at least right now.

@Osspial fair question. I guess it depends on what decorations means to wininit. I interpreted it to refer purely to the existence of visual elements, not behavior.
Also, iiuc, #389 would offer more granular controls over the masks such that you could still achieve non-resizeable borderless windows.

Are we sure this behavior is something we want implicitly true
I don't want to lose the ability to do that on OSX

Both scenario are covered. Both scenario are valid. It's a matter of what we do by default, what the expectation is.
I would recommend to land this as it is, and in #389 add enough documentation / examples to explain how to achieve both behaviors.

Anything blocking this from merging? @tomaka ?

I'm okay with adding an option to make borderless windows resizable, but my biggest issue is that it both changes the current default behavior and makes the default behavior inconsistent across platforms. Also, I could be reading the diff incorrectly, but there doesn't seem to be a way to configure it to use the current behavior, which seems like an important thing to have.

My understanding is that borderless windows on windows and linux are resizable through other means, just not by dragging the borders (because the borders aren't there). Please correct me if I'm wrong.
If this is the case, then I think neither behavior is perfectly consistent across platforms. In fact, I'm not sure it's possible to achieve this in macos (i.e. borderless windows that are not resizeable by dragging the edges of the window, but resizeable through other means, like a window manager).
The more granular control is represented by #389, not this PR.

Testing it, it looks like borderless windows on Windows are completely unresizable (or at least, I can't figure out a way to do it, even with keyboard shortcuts).
On Linux, it seems to depend on the window manager. I tested in with Xfce, and was able to resize borderless windows with Alt+Right-Click, but it still couldn't be resized with border dragging. Despite this, the behavior is still mostly consistent across platforms - borderless windows can't be resized by dragging on the edges.

Note that under X11, it is technically impossible for a client to prevent the window manager from resizing its windows however it likes, so the existence of the possibility under some particular state shouldn't be read into too heavily.

.with_decorations(false) (current):

platform
resizable by dragging
resizable by window manager
borders

windows
no
no
no

linux
no
yes
no

macos
no
no
no

.with_decorations(false) (proposed in this PR):

platform
resizable by dragging
resizable by window manager
borders

windows
no
no
no

linux
no
yes
no

macos
yes
yes
no

@Osspial I can see your point about it being slightly more consistent behavior across
platforms. However, it still seems to me that it depends on what the meaning of
"decorations" is. I interpret it to refer purely to aesthetic concerns. For a
flag that concerns the behavior that you're talking about, I think a different
flag that refers specifically to the behavior would be more appropriate, e.g.
something like .resizable(bool).
You're right that #389 doesn't have the settings for controlling this specifically, but I think it shows us how to use the window builder extension to expose all the granular settings that we would need to to allow it.

@tomaka would love your input on this. If this is not acceptable as is, I would like to get started on the WindowBuilderExt work to get the resizable window with no titlebar that I want.

@tomaka Hmmm, ok, so whom do I need to convince to get this merged or rejected?

I'm just a user but I sure do hope that this get's merged as I would love to have borderless windows that I can move around and resize (with external programs in macOS).
On that note @sodiumjoe If you could cut a release of your alacritty (with this change) that would be amazing.

@oschrenk you just need to clone alacritty, glutin, and winit, then reference your local copy of winit from glutin, and glutin from alacritty:
glutin's Cargo.toml's [dependencies] block:
winit = { path = "../winit" }

in alacritty's Cargo.toml's [dependencies] block:
glutin = { path = "../glutin" }

I've been using this build of alacritty since I started this PR and really enjoying it.

Maybe split this PR in 2. The WinitWindow subclass is necessary no matter what.
Then as what to do with the mask, it doesn't really matter, you can always do that via WindowExt::get_nswindow() I believe.

@paulrouget @Osspial @tomaka I've added a commit removing the resizable mask from an undecorated window. I believe that was the only remaining objection to this PR.

@sodiumjoe if you remove NSResizableWindowMask, you can't resize with the mouse anymore.

I'm still trying to understand what we want here… I'm confused.

Subclassing is necessary otherwise resizing is not possible, even by changing the mask via WindowExt::get_nswindow(). So, subclassing is 100% needed.
So let's have a PR just for that.
As for the default behavior, by adding the subclass, it makes the initial mask configuration work. So the window will be resizable as initially intended.

@paulrouget maybe I'm confused too, I believe the current state of the PR represents what you described, i.e. it adds the subclassing, but leaves resizability as it was before this PR, i.e. no with_decorations(false) windows are not resizable by any means. That last bit was the most recent commit.
The rest of the delta is just removing masks that have no effect on a window with no titlebar.
It sounds like you're disagreeing with @Osspial about whether a with_decorations(false) window should be resizable by default. I disagree too, but I'd rather just get this merged and get resizability by other means (WindowExt::get_nswindow() as you suggested).
I have a working build of alacritty doing exactly that with the following code:
        use glutin::os::macos::WindowExt;
        use self::cocoa::base::id;
        use window::cocoa::appkit::NSWindow;
        let nswindow = self.window.get_nswindow();
        unsafe {
            (nswindow as id).setStyleMask_((nswindow as id).styleMask() | cocoa::appkit::NSWindowStyleMask::NSResizableWindowMask);
        }

The unfortunate part of this is that it means dependents that want to use get_nswindow() also have to pull in cocoa.
My plan is to work on a PR along the lines of #389 to offer more granular control over the masks that a consumer can use. But it's not clear to me what that api should look like, how it will apply to other platforms, or how a consuming application like alacritty would expose those options to users. Maybe @jwilm can chime in about that part, so we can get an idea of what would be a good api for consumers of winit.

Going around in circles :) I'm happy with this change.
@tomaka this is an improvement and the initial behavior doesn't change, can we land this?

I made a PR to @robertgzr 's branch for #389 to add another WindowBuilderExt method to hide the titlebar, but keep resizability: https://github.com/robertgzr/winit/pull/1
But it depends on this one getting merged first.

@tomaka I believe all the objections to this PR have been resolved.

@tomaka anything else necessary here?

Needs a rebase or a merge, and I'll merge!

@tomaka merged, thanks!

I just tried testing this on macos and this seems to break the multiwindow.rs example (I use this quite a lot downstream). Here's the backtrace:
   Compiling winit v0.11.2 (file:///Users/joshuabatty/Documents/Code/rust/winit)
    Finished dev [unoptimized + debuginfo] target(s) in 1.81 secs
     Running `target/debug/examples/multiwindow`
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/libcore/option.rs:335:21
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::panicking::default_hook::{{closure}}
             at src/libstd/sys_common/backtrace.rs:68
             at src/libstd/sys_common/backtrace.rs:57
             at src/libstd/panicking.rs:381
   2: std::panicking::default_hook
             at src/libstd/panicking.rs:397
   3: std::panicking::begin_panic
             at src/libstd/panicking.rs:577
   4: std::panicking::begin_panic
             at src/libstd/panicking.rs:538
   5: std::panicking::try::do_call
             at src/libstd/panicking.rs:522
   6: std::panicking::try::do_call
             at src/libstd/panicking.rs:498
   7: <core::ops::range::Range<Idx> as core::fmt::Debug>::fmt
             at src/libcore/panicking.rs:71
   8: <core::ops::range::Range<Idx> as core::fmt::Debug>::fmt
             at src/libcore/panicking.rs:51
   9: <core::option::Option<T>>::unwrap
             at /Users/travis/build/rust-lang/rust/src/libcore/macros.rs:20
  10: winit::platform::platform::window::Window2::create_window
             at src/platform/macos/window.rs:443
  11: winit::platform::platform::window::Window2::new
             at src/platform/macos/window.rs:321
  12: winit::platform::platform::Window::new
             at src/platform/macos/mod.rs:32
  13: <core::option::Option<T> as core::ops::try::Try>::into_result
             at src/window.rs:119
  14: winit::window::<impl winit::Window>::new
             at ./src/window.rs:135
  15: multiwindow::main
             at examples/multiwindow.rs:7
  16: std::rt::lang_start::{{closure}}
             at /Users/travis/build/rust-lang/rust/src/libstd/rt.rs:74
  17: std::panicking::try::do_call
             at src/libstd/rt.rs:59
             at src/libstd/panicking.rs:480
  18: panic_unwind::dwarf::eh::read_encoded_pointer
             at src/libpanic_unwind/lib.rs:101
  19: std::sys_common::bytestring::debug_fmt_bytestring
             at src/libstd/panicking.rs:459
             at src/libstd/panic.rs:365
             at src/libstd/rt.rs:58
  20: std::rt::lang_start
             at /Users/travis/build/rust-lang/rust/src/libstd/rt.rs:74
  21: multiwindow::main

I can repro, I'll check it out

@mitchmindtree fixed, can you verify?

@mitchmindtree awesome, thanks for the quick verification! Anything else I need to do to get this merged?

@tomaka just my weekly check-in on this PR 😄

@sodiumjoe this should have a CHANGELOG entry.

@francesca64 done!

The change should go under the Unreleased heading
Please try to better conform to the style of the rest of the CHANGELOG (i.e. don't add those additional line breaks, and in general)

Ok, how does it look now?

@sodiumjoe Looks good, thanks!
While I'm able to merge this, I'm not sure how comfortable @tomaka is with me merging things. With how busy he is, I want to do as much to help out with winit as I can, so I'm hoping for some clarification on his policy.
...that said, since he already approved this, I'll merge it.


[Starfish] Add db attributes to database span's span data

To get an overview of this work across all SDKs, please visit:
https://github.com/orgs/getsentry/projects/135
Parent issue: https://github.com/getsentry/team-sdks/issues/19
For the starfish db module it was determined that we need extra database attributes.
db.name should be set if possible, but is not required. db.system should match the list in OpenTelemetry's well known conventions.

Attribute
Type
Description
Examples
Requirement Level

db.system
string
An identifier for the database management system (DBMS) product being used.
sqlite
Required

db.name
string
This attribute is used to report the name of the database being accessed. For commands that switch the database, this should be set to the target database (even if the command fails).
customers; main
Conditionally Required: If applicable.

These values should be set on span.data.
Motivation
This is being done for the Sentry's new performance views for databases. See a WIP example of the view below:

Should these attributes also be set on spans for opening/closing db? or strictly only for queries

@buenaflor preferably only on the query span, but it's also fine to duplicate the attributes among all db related spans.


Vispy

Hi,
Is there any way to use VisPy with a Kivy backend?

I'm not aware of anyone having written the code for it, but I'm fairly sure it should be possible if anyone wants to try. I had a look at it once but never spent enough time to get very far. I think I was going the route of trying a Kivy window backend for Vispy, but that's not the only possibility.

Do you have any code from the time when you were trying to use kivy's backend? Alternatively, would you know of any other way to have interactive/real-time graphs built in? Matplotlib is pretty terrible and kivy doesn't yet support web views for python3 to try and go the Bokeh route (CEFpython doesn't support python3).

I don't think I had any useful code, even if I still have the branch
somewhere.
I think the main direction of what I was trying was to add a Vispy
window provider. Vispy's system for choosing this provider is fairly
clear in their source code, so it shouldn't be too hard to slot this in.
As I remember, the window code was supposed to set up the window then
run Vispy's eventloop passing in the window events. I was trying to use
Kivy's Clock for this, so that Kivy could pass Vispy the necessary
events, but then Vispy could run within an existing Kivy window.
I'm afraid I don't know of a better solution for fancy dynamic plots.
On 12/01/17 14:58, Vlad Jiman wrote:

Do you have any code from the time when you were trying to use kivy's
backend? Alternatively, would you know of any other way to have
interactive/real-time graphs built in? Matplotlib is pretty terrible and
kivy doesn't yet support web views for python3 to try and go the Bokeh
route (CEFpython doesn't support python3).
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/kivy/kivy/issues/4910#issuecomment-272184466, or
mute the thread
https://github.com/notifications/unsubscribe-auth/ABNQm5bBakU-2sftb-oDiFsxWl3Vuh0Iks5rRj-NgaJpZM4LgaVn.


add support for ODroid-C1

ODroid-C1 is a very competitively priced single board computer, and very powerful for it's price. I'd like to support this board as well, so it needs a new driver. I've ordered one with stock Ubuntu 14.04, and create a driver and see how it performs.

Initial implementation pushed to odroid-dev branch

Initial support for this board has been added. It is known to self-identify, and analog inputs are known to work. Further testing required,


Fix samples for JavaScript

Use // instead of # for comments in .js files
Add the term bundle as this is a keyword many people might look for

I just noticed this, thanks!

:heart:


Reference (source) PackageRepository in Package CR

Describe the problem/challenge you have
For client tooling, it'd be helpful if the PackageRepository that a Package CR came from was written into the Package object. I don't think we need a new field in the API (could be an annotation) but either could work.

Some things to consider:

can packages map to more than one package repository?
can packages be changed (such as being updated with another package repository)?

Some thoughts here, so they are not lost:

Packages are keyed by metadata.name
A Package with a name xyz can be contributed by multiple PackageRepositories, so names are not trully unique
Multiple PackageRepositories can have Packages defined with the same metadata.name. There needs to exist some conflict resolution mechanism in kapp-controller.
A Package installed on the cluster needs to have a way to prove the provenance. The PackageRepository that contributed it. IMHO this should be in the status of the Package, since it seems more related to where the Package came from rather than in the metadata or spec.
A PackageReposiory needs to have a list of the Packages that have in the source repository and the status of whether they are contributed to the cluster or not, by any conflict

This summarizes some of the topics in a conversation on Slack.

note from IPM:

dk: "feels like an annotation" (human, not machine-automation)

but also we should check that what we do will meet TMC's book keeping needs.

How does a packageCR reference a pkgr -- the 'global namespace' shows up in all other namespaces, so the pkgr reference would need to consider namespace access issues - you may be able to see a ref to a pkgr that you can't actually view.

This was shipped in v0.33.1.


LayoutXLM model Special tokens have been added in the vocabulary.

Describe
Model I am using LayoutXLM
I am trying to fine-tune the model with Question-Answer pair.
When I use "microsoft/layoutlmv2-base-uncased", there is no problem with the model or data. When I switched to "microsoft/layoutxlm-base" I got this "Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained" warning. Once I start tokenization I got "ValueError: Id not recognized" error at this point encoding = tokenizer(         questions,         words,         boxes,         max_length=max_length,         padding="max_length",         truncation=True,         # add_special_tokens=False     )
If I add "add_special_tokens=False" this as encoding = tokenizer(         questions,         words,         boxes,         max_length=max_length,         padding="max_length",         truncation=True,         add_special_tokens=False     )
I got "ValueError: 250005 is not in list" error.

When I used
"tokenizer = LayoutXLMTokenizer.from_pretrained(model_checkpoint_xml)"  instead of
"tokenizer = AutoTokenizer.from_pretrained(model_checkpoint_xml)"
I dont see above error. However now I don't get sequence_ids since it says "ValueError: sequence_ids() is not available when using Python-based tokenizers". When I use LayoutMv2Tokenizer, it gives me sequence_ids. Not sure what I am missing here.


ConnectToPort() needs to Dup() its VirtioSocketConnection

Describe the bug
The VirtioSocketConnection created through ConnectToPort() is closed after its completion handler returns.
To Reproduce
https://github.com/cfergeau/vz/commit/fd9f5ccf924cf836506c0edb70194b94537628b5
Expected behavior
The VirtioSocketConnection created through ConnectToPort() can be used outside of its completion hander.
Environment (please complete the following information):

macOS Version: 12.6
Go Version: 1.19

Additional context
https://github.com/Code-Hex/vz/pull/53 has a proposed fix for this

I think we should fix this problem to use net.FileConn because of this API. uses nonblocking connection and syscall dup.

I looked at net.FileConn, and with respects to v3, I  would recommend removing func (v *VirtioSocketConnection) FileDescriptor() uintptr from the API. We would need more code to support it together with net.FileConn, and I don't think it's needed now that VirtioSocketConnection implements net.Conn

I think we should fix this problem to use net.FileConn

I've tried this, this solves this bug, and this allows for some nice code simplifications. I've put these changes in https://github.com/cfergeau/vz/tree/vsock-upstream
Let me know if/when you want a PR for this.

@cfergeau Exactly, I want the code but a little bit needs to fix a point.
I would be happy to accept this amount of change. Could you send PR?


--push-images flag doesn't work (at least on OS X)

from https://medium.com/bigdatarepublic/pachyderm-for-data-scientists-d1d1dff3a2fa

...
using --push-images one can have that done automatically. So let’s update our pipeline accordingly:
$ pachctl update-pipeline -f iris.json --push-images
error parsing auth: Failed to read authentication from dockercfg, try running `docker login`
$ docker login
Authenticating with existing credentials...
Login Succeeded
$ pachctl update-pipeline -f iris.json --push-images
error parsing auth: Failed to read authentication from dockercfg, try running `docker login`

Unfortunately that doesn’t work as expected, at least not on my machine. Let’s do it ourselves:
...

looks like this may be the same issue as #2446?

Seems the root of this issue is that the go-dockerclient library doesn't support creds stored in oxskeychain (more details here, among other places)
This should probably be addressed with a PR against that lib, but can be worked around by embedding the docker creds in the ~/.docker/config.json file (as is done on Linux)
by default, that file will look something like this:
{
  "stackOrchestrator" : "swarm",
  "auths" : {
    "https://index.docker.io/v1/" : {

    }
  },
  "credSstore" : "osxkeychain"
}

you can generate a string containing your dockerhub creds by running
echo -n "username:password" | base64

and paste the resulting string into the config file's auths section:
{
  "stackOrchestrator" : "swarm",
  "auths" : {
    "https://index.docker.io/v1/" : {
      "auth": "<YOUR CREDS STRING HERE>"
    }
  },
  "credSstore" : "osxkeychain"
}

There seem to be two issues going on here.
Without any changes, I'm hitting the same issue as #2446.
With the config change, if I do pachctl update-pipeline -f edges.json --push-images, it fails, because it tries to push the image to [system user]/[repo] rather than [docker user]/[repo]. It appears that this is pachctl's default behavior when a user is not explicitly specified. Is this intended? Or should we instead default to the docker user?

I'll go ahead and open a PR with the fix. We can just not merge the PR if defaulting to system user is expected behavior.

@gabrielgrant confirmed that your fix, in tandem with #3322, allows you to push images in macOS.

Sure, that makes sense. Do we have an idea of how frequently --push-images is employed? That would help decide whether it makes sense to just print a friendly error message, or build a full workaround.

well, given how broken it seems it was, i doubt it has been used much to date :package:
so yea, maybe just checking for the existence of ~/.docker/config.json's ["auths"]["https://index.docker.io/v1/"]["auth"] key and printing a warning message pointing to this workaroud if that key doesn't exist?


Upgrade taker http API

Upgrade taker http API to allow to take new offers

@klochowicz : I think we are solving this at the same time as #2460


the TryHandleException method should change to the TryHandleAsync method

Description
In this doc, the TryHandleException method should change to the TryHandleAsync method.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/error-handling?view=aspnetcore-8.0&WT.mc_id=DT-MVP-4015686
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/error-handling.md
Document ID
38515dfb-91a5-b395-db9d-084bbaf095c8
Article author
@tdykstra

Related #32594

@doggy8088 Thanks for reporting this!


Misalignment of radio buttons

Actual Behaviour
When clicked on the GENERATE WEBAPP button, the radio buttons get misaligned w.r.t. each other.
Expected Behaviour
There should be no misalignment between the radio buttons.
Screenshots of the issue

Would you like to work on the issue?
Yes

Upload via FTP button seems to be moving from its place when we add a zip file otherwise I don't see any kind of issue when we click on GENERATE WEBAPP.
If you can tell me more about this the issue that would help me.

Upload via FTP button seems to be moving from its place when we add a zip file otherwise I don't see any kind of issue when we click on GENERATE WEBAPP.
If you can tell me more about this issue then that would help me.

Please see the above screenshot mentioned in the issue description.
When you click on GENERATE WEBAPP, without filling all the required fields, the radio buttons under the Choose Session Styles get misaligned and the validator error message doesn't have red font color.
Please see if you can solve the issue.

Would this work?

Would this work?

LGTM. Can you pls file a pr for the above changes?

Will do.

Pull request has been generated.

Can you also help me to choose which type of zip files because there seems to be problem while extracting the zip file.

Can you also help me to choose which type of zip files because there seems to be problem while extracting the zip file.

Can you share the complete logs?

ZIP mode isn't working already

Hey @Dishebh, are you actively looking to the issue?

No

Alright, actually this issue can be closed as this problem won't arise after #2335  is addressed. In 2335, the pre-selection would never let such case occur[the alignment issue caused to both radio buttons both being unselected]. Hope it makes sense.


#666 Disable failing tests to make it easier to detect regressions

Used the following (imperfect, but good enough) script to disable tests based on test run results: https://github.com/mousetraps/disable-failing-mstests
I suspect there may still be some lingering issues, so I plan to iterate after the test run completes. Additionally I plan to update #646 with priorities re: re-enabling tests. For instance, many of our debugger tests are failing due to an external issue in Node.js that is preventing us from detecting the end of program execution.
close #666

I disabled all the tests that were broken locally, and now I'm working through some of the CI-specific issues. Baby steps :smiley:


Navigator wrongly affecting colour of Scaffold beneath transparent Widget

Steps to Reproduce
Please check the DartPad here.
Notes:

I've determined that this issue is the Navigator object wrapping my _page property in the above DartPad.
This exact code was rendering as expected on Flutter V2
Upgraded to V3 and the bug is present.
There is a comment on this StackOverflow question by someone who ran it on V2 and said it was fine.

Note: Bug result is same on iOS 15 and Android 12 physical devices
To see the wrong/right render:

Load the above DarPad.
Toggle L.156 commented / uncommented
Run
Observe that the render of the Scaffold blue colour is not consistent.

Expected results:
I expected:

there to be no discernible line or shading between the BottomNavigationBar and the Scaffold underneath
the blue colour to be fully opaque, not somewhat "transparent" as it appears.

Actual results:

the blue colour of the underlying Scaffold is somewhat "transparent".

Screenshots:
Bad:

Good:

Davids-MacBook-Pro:moodment daveshirman$ flutter doctor -v
[✓] Flutter (Channel stable, 3.0.1, on macOS 11.6.6 20G624 darwin-x64, locale en-GB)
    • Flutter version 3.0.1 at /Users/daveshirman/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fb57da5f94 (3 weeks ago), 2022-05-19 15:50:29 -0700
    • Engine revision caaafc5604
    • Dart version 2.17.1
    • DevTools version 2.12.2

[!] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/daveshirman/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] VS Code (version 1.67.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (1 available)
    • iPhone 13 mini (mobile) • FCD4F8E9-8E88-4C8C-B901-46D70A186315 • ios • com.apple.CoreSimulator.SimRuntime.iOS-15-2 (simulator)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

One possible fix would be adding extendBody: true to the Scaffold that contains the bottomNavigationBar

Thanks. So I knew already that adding that property would make it "seem"
fixed, but it wouldn't be in reality.
This is because the behaviour is clearly changed from V2 to V3.
If I make a Scaffold background transparent, I expect the widget behind to
show its full colour.
On Thu, 9 Jun 2022, 18:36 Jason Simmons, @.***> wrote:

One possible fix would be adding extendBody: true to the Scaffold that
contains the bottomNavigationBar
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/105738#issuecomment-1151684602,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADM6KXREGJD7HD3FSQ5MHADVOJWWLANCNFSM5YLKTTXA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Issue is reproducible on the latest stable and master, but not stable 2.10.5.
I played around with the code a bit, and it looks like this is due to the CupertinoPageRoute and not the Navigator. It seems like this is due to the Navigator because when you change from CupertinoPageRoute to MaterialPageRoute and hot reload, there are no visual changes, but when you hot-restart, you see that it works as expected. See the video below.
Leaving this for further insight from the team.

video and screenshot
Screenshots

stable 2.10.5
flutter 3

Video
https://user-images.githubusercontent.com/88313112/173036346-875107d7-fddd-4ff7-895c-d22748030461.mov

code sample
import 'package:flutter/material.dart';
import 'package:flutter/cupertino.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      title: _title,
      home: App(),
    );
  }
}

class App extends StatefulWidget {
  const App({Key? key}) : super(key: key);

  @override
  State<StatefulWidget> createState() => AppState();
}

class AppState extends State<App> {
  // this is static property so other widget throughout the app
  // can access it simply by AppState.currentTab

  static int currentTab = 0;

  // list tabs here
  final List<TabItem> tabs = [
    TabItem(
      tabName: "Home 1".toUpperCase(),
      page: const PageHome(),
    ),
    TabItem(
      tabName: "Home 2".toUpperCase(),
      page: const PageHome(),
    ),
  ];

  AppState() {
    // indexing is necessary for proper functionality
    // of determining which tab is active
    tabs.asMap().forEach((i, item) => item.setIndex(i));
  }

  @override
  void initState() {
    super.initState();
  }

  // sets current tab index
  // and update state
  void _selectTab(int index) {
    if (index == currentTab) {
      // pop to first route
      // if the user taps on the active tab
      tabs[index].key.currentState!.popUntil((route) => route.isFirst);
    } else {
      // update the state
      // in order to repaint
      if (mounted) {
        currentTab = index;
        _updateView();
      }
    }
  }

  void _updateView() {
    if (mounted) {
      setState(() {});
    }
  }

  void resetToHomeTab() {
    currentTab = 0;
  }

  @override
  Widget build(BuildContext context) {
    Widget body = Scaffold(
      backgroundColor: Colors.transparent,
      body: IndexedStack(
        index: currentTab,
        children: tabs.map((e) => e.page).toList(),
      ),
      bottomNavigationBar: BottomNavigation(
        onSelectTab: _selectTab,
        tabs: tabs,
      ),
    );

    // Background of the tab view
    Widget wrap = Container(
      width: double.infinity,
      height: double.infinity,
      color: Colors.blue,
      child: body,
    );

    // WillPopScope handle android back btn
    return WillPopScope(
      onWillPop: () async {
        final isFirstRouteInCurrentTab =
            !await tabs[currentTab].key.currentState!.maybePop();
        if (isFirstRouteInCurrentTab) {
          // if not on the 'main' tab
          if (currentTab != 0) {
            // select 'main' tab
            _selectTab(0);
            // back button handled by app
            return false;
          }
        }
        // let system handle back button if we're on the first route
        return isFirstRouteInCurrentTab;
      },
      // this is the base scaffold
      // don't put appbar in here otherwise you might end up
      // with multiple appbars on one screen
      // eventually breaking the app
      child: wrap,
    );
  }
}

class TabItem {
  final String tabName;
  final GlobalKey<NavigatorState> key = GlobalKey<NavigatorState>();
  int _index = 0;
  Widget? _page;
  TabItem({
    required this.tabName,
    required Widget page,
  }) {
    _page = page;
  }

  void setIndex(int i) {
    _index = i;
  }

  int getIndex() => _index;

  Widget get page {
    // If you toggle between the two return statements below, you can see the transparency
    // not working as expected when the page is wrapped in the Navigator

    // return _page!;

    return Visibility(
      visible: _index == AppState.currentTab,
      maintainState: true,
      // child: _page!,
      child: Navigator(
        key: key,
        onGenerateRoute: (routeSettings) {
          return CupertinoPageRoute(
            builder: (_) {
              return (_page != null) ? _page! : const SizedBox();
            },
          );
        },
      ),
    );
  }
}

class BottomNavigation extends StatelessWidget {
  const BottomNavigation({
    required this.onSelectTab,
    required this.tabs,
    Key? key
  }) : super(key: key);
  final ValueChanged<int> onSelectTab;
  final List<TabItem> tabs;

  @override
  Widget build(BuildContext context) {
    return BottomNavigationBar(
      elevation: 0,
      showSelectedLabels: true,
      showUnselectedLabels: true,
      backgroundColor: Colors.transparent,
      fixedColor: Colors.white,
      type: BottomNavigationBarType.fixed,
      items: tabs.map((e) => _buildItem(e.getIndex(), e.tabName)).toList(),
      onTap: (index) => onSelectTab(
        index,
      ),
      currentIndex: AppState.currentTab,
    );
  }

  BottomNavigationBarItem _buildItem(int index, String tabName) {
    return BottomNavigationBarItem(
      icon: const Padding(
        padding: EdgeInsets.only(bottom: 4),
        child: Icon(Icons.home),
      ),
      label: tabName,
    );
  }
}

class PageHome extends StatelessWidget {
  const PageHome({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const Scaffold(
      backgroundColor: Colors.transparent,
      body: Center(
        child: Text("Home page"),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel unknown, 2.10.5, on macOS 12.3.1 21E258 darwin-arm, locale en-GB)
    • Flutter version 2.10.5 at /Users/nexus/dev/sdks/flutter_rc/flutter
    • Upstream repository unknown
    • Framework revision 5464c5bac7 (8 weeks ago), 2022-04-18 09:55:37 -0700
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.67.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (3 available)
    • iPhone 13 (mobile) • DBB48503-41CE-4969-9043-3261726E438A • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-4 (simulator)
    • macOS (desktop)    • macos                                • darwin-arm64   • macOS 12.3.1 21E258 darwin-arm
    • Chrome (web)       • chrome                               • web-javascript • Google Chrome 102.0.5005.61
    ! Error: Nexus is not connected. Xcode will continue when Nexus is connected. (code -13)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel stable, 3.0.1, on macOS 12.3.1 21E258 darwin-arm, locale en-GB)
    • Flutter version 3.0.1 at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fb57da5f94 (3 weeks ago), 2022-05-19 15:50:29 -0700
    • Engine revision caaafc5604
    • Dart version 2.17.1
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.67.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (3 available)
    • iPhone 13 (mobile) • DBB48503-41CE-4969-9043-3261726E438A • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-4 (simulator)
    • macOS (desktop)    • macos                                • darwin-arm64   • macOS 12.3.1 21E258 darwin-arm
    • Chrome (web)       • chrome                               • web-javascript • Google Chrome 102.0.5005.61
    ! Error: Nexus is not connected. Xcode will continue when Nexus is connected. (code -13)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 3.1.0-0.0.pre.1211, on macOS 12.3.1 21E258 darwin-arm, locale en-GB)
    • Flutter version 3.1.0-0.0.pre.1211 at /Users/nexus/dev/sdks/flutters
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 9d46e7800f (6 hours ago), 2022-06-09 23:43:08 -0400
    • Engine revision a4cdb1e232
    • Dart version 2.18.0 (build 2.18.0-174.0.dev)
    • DevTools version 2.14.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] VS Code (version 1.67.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (3 available)
    • iPhone 13 (mobile) • DBB48503-41CE-4969-9043-3261726E438A • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-4 (simulator)
    • macOS (desktop)    • macos                                • darwin-arm64   • macOS 12.3.1 21E258 darwin-arm
    • Chrome (web)       • chrome                               • web-javascript • Google Chrome 102.0.5005.61
    ! Error: Nexus is not connected. Xcode will continue when Nexus is connected. (code -13)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

The "somewhat transparent" color visible here is the barrierColor introduced in https://github.com/flutter/flutter/pull/95537
I'm not sure why it is visible here maybe @willlockwood knows the answer?


[Bug] Check failed: (it != type_key2index_.end()) is false: Cannot find type relax.dpl.StructInfoPattern. Did you forget to register the node by TVM_REGISTER_NODE_TYPE

🐛 Bug
I'm trying to follow the instructions in https://llm.mlc.ai/docs/deploy/android.html (the version with using the prebuilt android.jar).
When reaching the ./prepare_libs.sh, I'm getting the error as in the title.
To Reproduce
Steps to reproduce the behavior:

Follow the instructions above, downloading the compiled android.jar.
Run ./prepare_libs.sh.
You'll get the following stacktrace:

Traceback (most recent call last):
  File "/home/sygi/code/mlc-llm2/android/library/prepare_model_lib.py", line 3, in <module>
    from tvm.contrib import ndk
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/python/tvm/__init__.py", line 82, in <module>
    from . import relax
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/python/tvm/relax/__init__.py", line 92, in <module>
    from .pipeline import get_pipeline
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/python/tvm/relax/pipeline.py", line 27, in <module>
    from . import transform, backend
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/python/tvm/relax/transform/__init__.py", line 19, in <module>
    from .transform import (
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/python/tvm/relax/transform/transform.py", line 28, in <module>
    from tvm.relax.dpl import DFPattern
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/python/tvm/relax/dpl/__init__.py", line 20, in <module>
    from .pattern import *
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/python/tvm/relax/dpl/pattern.py", line 582, in <module>
    class StructInfoPattern(DFPattern):
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/python/tvm/relax/dpl/pattern.py", line 48, in register_df_node
    return tvm_ffi.register_object("relax.dpl." + type_key.__name__)(type_key)
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/python/tvm/_ffi/registry.py", line 69, in register
    check_call(_LIB.TVMObjectTypeKey2Index(c_str(object_name), ctypes.byref(tidx)))
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/python/tvm/_ffi/base.py", line 496, in check_call
    raise_last_ffi_error()
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/python/tvm/_ffi/base.py", line 481, in raise_last_ffi_error
    raise py_err
tvm.error.InternalError: Traceback (most recent call last):
  68: 0xffffffffffffffff
  67: _start
  66: Py_BytesMain
  65: Py_RunMain
  64: 0x0000653cfb02ee54
  63: 0x0000653cfb0289ca
  62: 0x0000653cfb02f107
  61: PyEval_EvalCode
  60: 0x0000653cfaf0e9c5
  59: PyImport_ImportModuleLevelObject
  58: 0x0000653cfaf28dc8
  57: 0x0000653cfaf2910d
  56: 0x0000653cfaf4db67
  55: PyImport_ImportModuleLevelObject
  54: 0x0000653cfaf28dc8
  53: 0x0000653cfaf29c58
  52: 0x0000653cfb009e2c
  51: PyEval_EvalCode
  50: 0x0000653cfaf0e9c5
  49: PyImport_ImportModuleLevelObject
  48: 0x0000653cfaf28dc8
  47: 0x0000653cfaf2910d
  46: 0x0000653cfaf4db67
  45: PyImport_ImportModuleLevelObject
  44: 0x0000653cfaf28dc8
  43: 0x0000653cfaf29c58
  42: 0x0000653cfb009e2c
  41: PyEval_EvalCode
  40: 0x0000653cfaf0e9c5
  39: PyImport_ImportModuleLevelObject
  38: 0x0000653cfaf28dc8
  37: 0x0000653cfaf29c58
  36: 0x0000653cfb009e2c
  35: PyEval_EvalCode
  34: 0x0000653cfaf0e9c5
  33: PyImport_ImportModuleLevelObject
  32: 0x0000653cfaf28dc8
  31: 0x0000653cfaf2910d
  30: 0x0000653cfaf4db67
  29: PyImport_ImportModuleLevelObject
  28: 0x0000653cfaf28dc8
  27: 0x0000653cfaf29c58
  26: 0x0000653cfb009e2c
  25: PyEval_EvalCode
  24: 0x0000653cfaf0e9c5
  23: PyImport_ImportModuleLevelObject
  22: 0x0000653cfaf28dc8
  21: 0x0000653cfaf29c58
  20: 0x0000653cfb009e2c
  19: PyEval_EvalCode
  18: 0x0000653cfaf0e9c5
  17: PyImport_ImportModuleLevelObject
  16: 0x0000653cfaf28dc8
  15: 0x0000653cfaf29c58
  14: 0x0000653cfb009e2c
  13: PyEval_EvalCode
  12: 0x0000653cfaf0e9c5
  11: PyImport_ImportModuleLevelObject
  10: 0x0000653cfaf28dc8
  9: 0x0000653cfaf29c58
  8: 0x0000653cfb009e2c
  7: PyEval_EvalCode
  6: 0x0000653cfaf0e9c5
  5: 0x000075593f9c79ff
  4: 0x000075593f9c83e8
  3: 0x000075593fc32492
  2: 0x000075593fc35e2d
  1: TVMObjectTypeKey2Index
  0: tvm::runtime::Object::TypeKey2Index(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)
  File "/home/sygi/code/mlc-llm/3rdparty/tvm/src/runtime/object.cc", line 165
InternalError: Check failed: (it != type_key2index_.end()) is false: Cannot find type relax.dpl.StructInfoPattern. Did you forget to register the node by TVM_REGISTER_NODE_TYPE ?

Expected behavior
This should build the libraries to attach.
Environment

Platform: Android
Operating system (e.g. Ubuntu/Windows/MacOS/...): Ubuntu 22.04 LTS
Device (e.g. iPhone 12 Pro, PC+RTX 3090, ...): this is before getting to the device
How you installed MLC-LLM (conda, source): no, using the sources
How you installed TVM-Unity (pip, source): from the 3rd party sources
Python version (e.g. 3.10): 3.10.12
GPU driver version (if applicable): not applicable
CUDA/cuDNN version (if applicable): not applicable
TVM Unity Hash Tag (python -c "import tvm; print('\n'.join(f'{k}: {v}' for k, v in tvm.support.libinfo().items()))", applicable if you compile models): gives the same error as the above.
Any other relevant information:

Additional context
I was able to progress further with a code version from the last month but there were some other incompatibilities so I recreated the project from scratch to make sure everything is clean (this means any dependencies should be there).

Nevermind, I found my error (not refreshing the venv). I am still getting some new errors, let me report them :P


Search input not working

Search input not working when open the picker in bootstrap modal. I can't click the  input event i change z-index in css.

i've remove tabindex="-1" from modal and solved thankyou


Request: documentation example for a write-only derived atom

There are a few examples in the official documentation page:

https://jotai.org/docs/integrations/immer

However, no example for a write-only derived atom, which is probably the main reason for using Immer – updating a complex and deep state.
I'm a bit lost here, so I believe it would be nice to have an example in the official docs.

I think jotai-immer is mainly for primitive atoms. It can't be used with write-only atoms.
Though, it might be easy to use produce from immer without jotai-immer.
const objAtom = atom({});
const updateAtom = atom(null, (get, set, updater) => {
  set(objAtom, produce(updater));
});

Okay, thanks.


Workers not auto starting in spring boot starter

Issue in io.temporal:temporal-spring-boot-starter-alpha:1.18.1
Expected Behavior
Workers should start and workflows should be processed.
Actual Behavior
Workflows don't execute and time out. No errors in the spring logs.
Steps to Reproduce the Problem

Get a spring boot starter alpha based flow working with version 1.17.0 . Use start-workers flag
Change version to 1.18.1 and restart application

Specifications

Version: 1.18.1
Platform: amd64

Spring Config
spring.temporal:
  start-workers: true
  workers:
    - task-queue: z_res_proc_int
      capacity:
        max-concurrent-workflow-task-executors: 10
        max-concurrent-activity-executors: 20
        max-concurrent-local-activity-executors: 2
        max-concurrent-workflow-task-pollers: 3
        max-concurrent-activity-task-pollers: 3
      rate-limits:
        max-worker-activities-per-second: 5.0
        max-task-queue-activities-per-second: 5.0
    - task-queue: z_hc_exec
      capacity:
        max-concurrent-workflow-task-executors: 20
        max-concurrent-activity-executors: 50
        max-concurrent-local-activity-executors: 5
        max-concurrent-workflow-task-pollers: 3
        max-concurrent-activity-task-pollers: 3
      rate-limits:
        max-worker-activities-per-second: 5.0
        max-task-queue-activities-per-second: 5.0
    - task-queue: z_infra_ops
      capacity:
        max-concurrent-workflow-task-executors: 5
        max-concurrent-activity-executors: 1
        max-concurrent-local-activity-executors: 1
        max-concurrent-workflow-task-pollers: 1
        max-concurrent-activity-task-pollers: 1
      rate-limits:
        max-worker-activities-per-second: 5.0
        max-task-queue-activities-per-second: 5.0
  workflow-cache:
      max-instances: 10
      max-threads: 10
  connection:
    target: local
  workers-auto-discovery:
    packages:
      - com.sample

Since version 1.18.x ApplicationContext.start needs to be called for workers to auto-start. If your application has a concept of start, it's the right thing to do anyway.
https://github.com/temporalio/sdk-java/blob/master/temporal-spring-boot-autoconfigure-alpha/README.md?plain=1#L206


SOLR-17352: Remove deprecated options from CLI

https://issues.apache.org/jira/browse/SOLR-17352
Description
Time to remove options deprecated in 9x.
Solution
Removing code!  Trying to do it one by one by area.
Tests
Updating tests, but otherwise shouldn't require anything new.

I hope in the future solr.cmd doesn't have helper methods like parse_config_args

I am leaving SolrCLI#getOptionWithDeprecatedAndDefault but adding some docs about what it's for, since I suspect we will have another deprecation soon!

for "AuthTool uses flags with Boolean arguments, should be deprecated and changed before 10" we should make another ticket.

@janhoy  in commit 2f3c0ef959b6a1f921217ef30da5347ec17a5b5f I removed the passing of the -j (Jetty options) into the RunExampleTool because it was an option that was ignored.   You added the line in the bin/solr so wanted to flag this to you in case you think we need to someone add this capability to RunExampleTool!

I think I am done and ready for more review.  I clearly was NOT done when I thought I was the first time!!!
I love that while we added 176 lines we remove 1092!!!!

I also anticipate that post this merge and some of the other inflight PR's, that we will want to reach out and ask the community for another round of testing on LInux and windows ;-)

I'd love to get this merged today if anyone can give it a quick pass.  I am sure there is more we can do, but would like to unblock some other PR's.

Looks good to me, there were a lot of changes and we definitely have a few more places we can reduce a few more lines. But that's for another PR.
@epugh It seems that the changes from #2816 that were already merged are not included here. Is this a problem?

Just pushed up the latest updates from main to pick up #2816.


Missing License

I wanted to upload the "fixed" version to the marketplace but I can't seem to find a license, meaning I'm not allowed to do so.
@W95Psp Could you please add a License?

That's done for the license, and I've re-uploaded the extension, so the marketplace version should be working properly now :)
Tell me if anything is wrong.

That's done for the license, and I've re-uploaded the extension, so the marketplace version should be working properly now :)
Tell me if anything is wrong.


how to change default max=200 to arbitrary value in the last yolo layer in  conv_lbbox

If the objects to detect in the image are more than 200, I need to add max=1000 e.g. in the last yolo layer in .cfg from AlexeyAB.
How to add this line in tensorflow framework? I checked the def convolutional  in common.py, but max is not a paramter for convolutional definition.
Could you please give me some hint? Thanks.

@hunglc007 Could you please give me some hint?


Fix file links not opening in Notebooks on Mac

This PR fixes https://github.com/microsoft/azuredatastudio/issues/18021
The fix is similar to the fix for images not working https://github.com/microsoft/azuredatastudio/pull/18160.
We need to convert the vscode-file URI to file URI when opening. It is still not clear to me why the URI is vscode-file only on Mac and not Windows.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 48.282%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
14766

Relevant Lines:
29039

💛  - Coveralls

@lucyzhang929 let's get this in today if possible. Anything else left to do here?


Synthesis failed for Google.Cloud.Dlp.V2

Hello! Autosynth couldn't regenerate Google.Cloud.Dlp.V2. :broken_heart:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the Google.Cloud.Dlp.V2 API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-19 22:43:26,669 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/Google.Cloud.Dlp.V2
2021-03-19 22:43:27,222 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2021-03-19 22:43:27,226 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2021-03-19 22:43:27,230 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2021-03-19 22:43:27,233 autosynth [DEBUG] > Running: git config push.default simple
2021-03-19 22:43:27,237 autosynth [DEBUG] > Running: git branch -f autosynth-Google.Cloud.Dlp.V2
2021-03-19 22:43:27,241 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.Dlp.V2
Switched to branch 'autosynth-Google.Cloud.Dlp.V2'
2021-03-19 22:43:27,446 autosynth [DEBUG] > Running: git rev-parse --show-toplevel
2021-03-19 22:43:27,453 autosynth [DEBUG] > Running: git log -1 --pretty=%H
2021-03-19 22:43:27,457 autosynth [DEBUG] > Running: git remote get-url origin
2021-03-19 22:43:27,494 synthtool [ERROR] > Failed executing git checkout master:

error: Your local changes to the following files would be overwritten by checkout:
	google/cloud/dialogflow/v2/answer_record.proto
	google/cloud/dialogflow/v2/conversation.proto
	google/cloud/dialogflow/v2/conversation_profile.proto
	google/cloud/dialogflow/v2/participant.proto
Please commit your changes or stash them before you switch branches.
Aborting

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 312, in _inner_main
    git_source.enumerate_versions(sources, pathlib.Path(temp_dir))
  File "/tmpfs/src/github/synthtool/autosynth/git_source.py", line 202, in enumerate_versions
    source_versions = enumerate_versions_for_source(git_source, temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/git_source.py", line 166, in enumerate_versions_for_source
    local_repo_dir = str(synthtool_git.clone(remote))
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 85, in clone
    shell.run(["git", "checkout", "master"], cwd=str(dest), check=True)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'checkout', 'master']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


External scaler connection errors ignored, the HPA is missing metrics

Report
When I install a Helm chart containing both an external scaler GRPC service and a ScaledObject, the resulting HPA has an empty list of metrics (K8s inserts the default 80% CPU utilization metric in that case). It then remains in that state even after the external scaler GRPC service has been initialized (I can manually force it to re-reconcile by editing the ScaledObject).
This is happening because Helm installs the external scaler service and the ScaledObject at the same time. The external scaler's GRPC server isn't available immediately (it takes ~1 sec for the pod to start), and KEDA runs the reconciliation of the ScaledObject before the external scaler is available, ignoring the GRPC connection error.
Expected Behavior
In my opinion, it would probably be better if KEDA were to re-queue the reconciliation request in these situations. For example, Reconcile() in scaledobject_controller.go could be returning ctrl.Result{RequeueAfter: time.Minute} if a GRPC connection error was observed.
Actual Behavior
KEDA doesn't update the HPA even after the external scaler is available.
Steps to Reproduce the Problem

Install a ScaledObject resource using an external scaler
Install the external scaler's GRPC service (1 and 2 should happen roughly at the same time, e.g., by being installed as part of the same Helm chart)
Now notice that the HorizonalPodAutoscaler created by KEDA is missing the metric specified in the ScaledObject

Logs from KEDA operator
No response
KEDA Version
None
Kubernetes Version
None
Platform
Any
Scaler Details
No response
Anything else?
No response

Hello,
What KEDA version are you using? this error shouldn't happen because KEDA tries to reconcille the ScaledObjects automatically. Do you see any error in KEDA ooperator logs?

@JorTurFer I'm on 2.14.0 (but I tested the main branch yesterday and the problem occurred too).
This is the ScaledObject definition:
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  labels:
    app.kubernetes.io/managed-by: Helm
    scaledobject.keda.sh/name: scaledobject-workers
  name: scaledobject-workers
  namespace: default
spec:
  scaleTargetRef:
    kind: Deployment
    name: scheduler
  triggers:
  - metadata:
      scalerAddress: scheduler-scaler.default.svc.cluster.local:8080
    type: external-push

And this is the HPA that gets created - notice that the list of metrics only contains a CPU-based metric (this is the default one inserted by K8s):
apiVersion: v1
items:
- apiVersion: autoscaling/v2
  kind: HorizontalPodAutoscaler
  metadata:
    annotations:
      meta.helm.sh/release-name: scheduler
      meta.helm.sh/release-namespace: default
    creationTimestamp: "2024-05-08T14:49:33Z"
    labels:
      app.kubernetes.io/managed-by: Helm
      app.kubernetes.io/name: keda-hpa-scaledobject-workers
      app.kubernetes.io/part-of: scaledobject-workers
      app.kubernetes.io/version: 2.14.0
      scaledobject.keda.sh/name: scaledobject-workers
    name: keda-hpa-scaledobject-workers
    namespace: default
    ownerReferences:
    - apiVersion: keda.sh/v1alpha1
      blockOwnerDeletion: true
      controller: true
      kind: ScaledObject
      name: scaledobject-workers
      uid: 1c21176d-71bc-4de2-9740-9fe03f5f66d7
    resourceVersion: "2777064"
    uid: a272a347-f011-499f-92e5-fa08d650f985
  spec:
    maxReplicas: 100
    metrics:
    - resource:
        name: cpu
        target:
          averageUtilization: 80
          type: Utilization
      type: Resource
    minReplicas: 1
    scaleTargetRef:
      apiVersion: apps/v1
      kind: Deployment
      name: scheduler
  status:
    conditions:
    - lastTransitionTime: "2024-05-08T14:49:48Z"
      message: the HPA controller was able to get the target's current scale
      reason: SucceededGetScale
      status: "True"
      type: AbleToScale
    - lastTransitionTime: "2024-05-08T14:49:48Z"
      message: 'the HPA was unable to compute the replica count: failed to get cpu
        utilization: unable to get metrics for resource cpu: unable to fetch metrics
        from resource metrics API: the server could not find the requested resource
        (get pods.metrics.k8s.io)'
      reason: FailedGetResourceMetric
      status: "False"
      type: ScalingActive
    currentMetrics: null
    currentReplicas: 1
    desiredReplicas: 0
kind: List
metadata:
  resourceVersion: ""

I'm also attaching logs from the operator pod:
keda-operator-logs.txt
Now, for example, if I edit the ScaledObject (with kubectl edit scaledobject ...), KEDA's Reconcile() method in scaledobject_controller.go will be re-run and update the HPA resource with the expected changes. It seems to be happening because the GRPC connection error is ignored when the GRPC service isn't available yet, and when it becomes available, KEDA doesn't retry the GRPC call.

I'm going to try to reproduce this.
From your example, I understand that I can deploy the ScaledObject and then, after some seconds, the external gRPC server and it'd be almost your use case, right? I want to find where we are hiding the connection error

@JorTurFer That's correct, the gRPC server with the external scaler should be down for some time after a ScaledObject is installed