extend query and query continuation expansion matches

more for #39

There are still some problems with some query strings like ?list&, but for now I can live with it ;)
See the commented asserts.

Done.
I'm :sleeping:, bye ;)

Me too - I'll check it out properly in the morning when I won't break anything through tiredness! :smile:

I'm going to go ahead and merge so we can start seeing how it works in Freya, etc. :smile: Thanks for these changes!


[TVMC] AttributeError: module 'tvm.auto_scheduler._ffi_api' has no attribute 'RandomModel'

while running
tvmc compile --target "llvm" --output resnet50-v2-7-tvm.tar resnet50-v2-7.onnx
, I got a runtime error:
AttributeError: module 'tvm.auto_scheduler._ffi_api' has no
attribute 'RandomModel'
Error is in python/tvm/auto_scheduler/cost_model/cost_model.py", line 37
@tvm._ffi.register_object("auto_scheduler.RandomModel")
class RandomModel(CostModel):
"""A model that returns random estimation for all inputs"""
def init(self):
self.init_handle_by_constructor(_ffi_api.RandomModel)
Any idea ?

The build platform is Mac (but I reproduce the same error on Centos)
Darwin MAC1 18.2.0 Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64 x86_64
$ clang --version
Apple LLVM version 10.0.1 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

ful stack trace:
File "/Users/dan/tvm/python/tvm/driver/tvmc/init.py", line 22, in
from . import autotuner
File "/Users/dan/tvm/python/tvm/driver/tvmc/autotuner.py", line 26, in
from tvm import autotvm, auto_scheduler
File "/Users/dan/tvm/python/tvm/auto_scheduler/init.py", line 21, in
from . import dispatcher
File "/Users/dan/tvm/python/tvm/auto_scheduler/dispatcher.py", line 36, in
from .search_policy import PreloadMeasuredStates, SketchPolicy
File "/Users/dan/tvm/python/tvm/auto_scheduler/search_policy.py", line 151, in
class SketchPolicy(SearchPolicy):
File "/Users/dan/tvm/python/tvm/auto_scheduler/search_policy.py", line 199, in SketchPolicy
program_cost_model=RandomModel(),
File "/Users/dan/tvm/python/tvm/auto_scheduler/cost_model/cost_model.py", line 37, in init
self.init_handle_by_constructor(_ffi_api.RandomModel)
AttributeError: module 'tvm.auto_scheduler._ffi_api' has no attribute 'RandomModel'

@leandron

I couldn't reproduce the issue on my local TVM, current pointing at 1fb32b055171f7b82b506b0f8e3096db1acc180c, the last commit as I write this. Can you point me to the specific git revision you're using?
I have my TVM installed following the guidance on https://tvm.apache.org/docs/install/from_source.html. Then, running the tvmc command line as you pointed above, it produces the output file correctly.
This is the list of packages on my virtualenv:
$ pip list
Package           Version  Location
----------------- -------- -----------------------------------------------
attrs             20.3.0
cloudpickle       1.6.0
decorator         5.0.7
numpy             1.19.5
onnx              1.8.1
pip               21.0.1
pkg-resources     0.0.0
protobuf          3.15.8
psutil            5.8.0
pyxir             0.0.1
scipy             1.5.4
setuptools        56.0.0
six               1.15.0
synr              0.3
tornado           6.1
tvm               0.8.dev0 [path to my tvm, 1fb32b055171f7b82b506b0f8e3096db1acc180c]
typing-extensions <IP_ADDRESS>
wheel             0.36.2

It is interesting that you can reproduce the issue on two different machines. The real issue seems to happening outside tvmc, within the call for from tvm import autotvm, auto_scheduler.
@comaniac any idea on what could be going on here?

Thanks @leandron for investigating.
Git is from branch main and revision 1fb32b055171f7b82b506b0f8e3096db1acc180c
$ pip list
Package     Version

certifi     2020.12.5
chardet     4.0.0
cloudpickle 1.6.0
idna        2.10
lxml        4.6.2
numpy       1.20.2
pip         21.0.1
psutil      5.8.0
requests    2.25.1
scipy       1.6.2
setuptools  49.2.1
tornado     6.1
tvm         0.8.dev878+g1fb32b055
urllib3     1.26.3
xgboost     1.4.0

I have done some more tests and managed to get it working via conda on Ubuntu only. with conda build of tvm, I had the same issue on Mac.

It's not related to tvmc as @leandron mentioned. Could you:

Simply run from tvm import auto_scheduler to see if the error can be reproduced.
Make sure you're using the right dynamic library. Specifically, whether the TVM python package you're running is using the built library of the same version. It may happen when you have multiply TVM builds on your environment.

Thanks for the great discussion, normally we handle this type of questions on https://discuss.tvm.apache.org/ I would suggest us move the conversation there by opening a new trouble shooting thread

It's not related to tvmc as @leandron mentioned. Could you:

Simply run from tvm import auto_scheduler to see if the error can be reproduced.
Make sure you're using the right dynamic library. Specifically, whether the TVM python package you're running is using the built library of the same version. It may happen when you have multiply TVM builds on your environment.

I can reproduce indeed just by running python and tvm import auto_scheduler
not sure how to debug this one and find  the actual used dynamic library used by TVM.

Anyway that's a progress. Thanks


Practice problems Unit 2 Pathway 1: Android Basics with Compose

A ---
name: Practice problems unit 2 pathway 1 issue template
about: Issue template for Unit 1 | Pathway 1 | Practice Problems
title: 'Practice problems Unit 2 Pathway 1: Android Basics with Compose'
labels: ''
assignees: ''

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-kotlin-fundamentals-practice-problems?hl=ko&continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-2-pathway-1%3Fhl%3Dko%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-kotlin-fundamentals-practice-problems#3
In which task and step of the codelab can this issue be found?
println("$initialMeasurement degrees $initialUnit is $finalMeasurement degrees $finalTemperature.")
$finalTemperature is wrong
Describe the problem
fix the $finalTemperature to $finalUnit
Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version:
API version of the emulator:
Additional information
Include screenshots if they would be useful in clarifying the problem.

This issue has been resolved.


how to oneline fetch a row

hello. i am having some trouble with writing a function that I will use to fetch a single row from my database. I have been able to make my code work with then()  (promise like) but not with async/await
https://gist.github.com/skrite/2ba6ac549ac1653405b3322acc25a12b
this returns undefined, but the console.log( from function) is working. Shouldn't the return statement happen after the console.log operation?
sorry about the gist, i was not able to get the formatting working right.
also, from things I have read, the then() after the query builder is actually what executes the code, does it return a Promise or a Promise like object?
basically, what I am after is a single await line of code that will return a single row of the database.
thanks

Thanks, i understand!  However, I have to wrap the function to be able to pass variables to it, right?

By autowrap I mean that async functions return promise even if you don't; if you return your own promise, it doesn't get additionally wrapped. And you only need function to be async if you do await calls inside of it, which you don't, so you would be fine removing async and just returning the promise chain.


Show warning if Pages artifact size is greater than 1 GB

Assuming it is possible to get the artifact size of an in-progress workflow run without downloading that artifact to a runner, it would be a nice improvement to check the size of the Pages artifact to-be-deployed and then issue a warning message (but not outright fail, at least within the current major version of this action) if the Pages Terms of Service limit of 1 GB is exceeded.
Related:

https://github.com/actions/upload-pages-artifact/issues/59

Looks like we could probably get the size of the artifact when inspecting the response we are already retrieving during the getSignedArtifactUrl call
e.g. the mocked response from the @actions/artifact client tests includes a size property:
https://github.com/actions/toolkit/blob/457303960f03375db6f033e214b9f90d79c3fe5c/packages/artifact/__tests__/download.test.ts#L255-L277
So I'm thinking our current line of
  const artifactRawUrl = data?.value?.find(artifact => artifact.name === artifactName)?.url

Could become something like:
  const artifact = data?.value?.find(artifact => artifact.name === artifactName)
  const artifactRawUrl = artifact?.url
  const ONE_GIGABYTE =<PHONE_NUMBER>
  if (artifact?.size > ONE_GIGABYTE) {
    core.warn('Uploaded artifact exceeds the allowed size for Pages deployments')
  }

I don't love mixing that into the api-client.js vs. keeping it with the business logic of deployment.js but it's probably reasonable. Otherwise we will also need to refactor the shape of the return value from the getSignedArtifactUrl function (and its references) to be an object including both the signed URL and the size. 🤔

I was more concerned with ensuring the endpoint attributes are named properly. PR is in for this under the assumption that the API response includes a size attribute under data.


Feature request: in mac os, when tapping notification, should bring app to foreground

This is what I think all other apps do.

Can you try this if you know how to do it ? https://github.com/yakyak/yakyak/pull/256
If not, just wait, it should be in the next pre-release build if @davibe merges it, and you'll be able to give it a try.

I don't know how to do it. But this issue looks like a dupe of that other
one, so feel free to close it
On Wed, Jun 22, 2016 at 3:06 PM, Arnaud Riu<EMAIL_ADDRESS>wrote:

Can you try this if you know how to do it ? #256
https://github.com/yakyak/yakyak/pull/256
If not, just wait, it should be in the next pre-release
https://github.com/yakyak/yakyak/releases build if @davibe
https://github.com/davibe merges it, and you'll be able to give it a
try.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/yakyak/yakyak/issues/261#issuecomment-227891765, or mute
the thread
https://github.com/notifications/unsubscribe/AAOdmfxx6Gn4WRMlXHLmNqMiONwqvEPzks5qObHQgaJpZM4I8P8N
.

--
Cheers,
Lowell

I can confirm I fixed this in #256

#256 is now merged so this can be closed.


Add retries to the end-2-end tests.

This PR adds the ability to do a limited number of retries (3) for end2end tests. Often the windows tests will fail during CI (an error about the event loop being closed) crashing the whole end2end ci pipeline.
As these are flaky, not broken, re-running the failed tests often fixes the problem. But this is annoying to have to get and email and click re-run each time it happens. This new version will rerun failed tests automatically, logging when a test that passed needed multiple tires. Hopefully this makes the windows issue less annoying going forward.
Related to https://github.com/r-three/git-theta/issues/249, need to verify the retries work/make windows more reliable before we close it.

The new retries work, in this run, the smudge test would have crashed the pipeline. Instead it was re-run, worked, and the pipeline passed.
closes https://github.com/r-three/git-theta/issues/249


Set up pre-commit hook and CI to run Markdown linter

Currently, there is no linter to check Markdown files automatically. It's better to lint Markdown files for both reviewers' time and time of authors of pull requests. It's challenging to maintain the style of the format. Manually checking by humans can be exhausting. This PR addresses the issue by setting up pre-commit hook and CI to run a Markdown linter, markdownlint-cli2. Also, this PR fixes issues found by the linter to keep the CI build green (mostly just break too long lines into multiple lines)
Note that the project specific configuration is configured in .pre-commit-config.yaml. More configuration can be added based on code owner's preference. For now, the configuration file only contains the line length limit to 88, blindly following the line length for Python code.

Resolved merge conflicts.


[91] Hiring staff can view their own vacancies

 Hiring staff viewing a hiring_stagg/vacancy falls over


Polybar on login: it won't appear until I refresh i3.

I've noticed when I start my machine polybar won't appear until I do a manual refresh of i3-gaps after I log in. I am unsure as to why this is the case. I used the script provided in the wiki, along with the command recommended in the i3gaps config file. I even tried adding the script to my .xinitrc to run after i3 was finished loading. Any ideas? I'll include a copy of the script and my gaps config, as well as the polybar config. Any help would be greatly appreciated.
Sincerely,
JohnABS
P.S. Sorry I'm posting on rather trivial topics, I'm kinda new to all of this, and to Github in general. Thank you for your patience.
i3config
polybarconfig
poly.sh

Hey! I had the same issue and used this workaround that someone else with the same problem had. Add the following line to .xinitrc, placing it right before exec i3 like so:
(sleep 5; ~/scripts/polybar.sh) &
exec i3

You can play around with the sleep length based on how fast your system starts i3. I use the same startup script provided by the wiki. Not sure if this is the best solution but it works!

I have i3 start the bars for me directly with the following in ~/.config/i3/config:
exec_always --no-startup-id $polybar

for an appropriately defined $polybar launch script.

I'm seeing this as well.
In order for polybar to see the monitors, I have to delay it's start a little bit.
~/.config/i3/config
exec_always --no-startup-id "$HOME/.config/i3/startup"

~/.config/i3/startup
#!/usr/bin/env bash
killall polybar
(sleep 2; polybar example -r) &


MINIFICPP-1309 - RAII based resourceClaim management

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file?
[ ] If applicable, have you updated the NOTICE file?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Is the Windows (GitHub actions) test failure related to this change?  It doesn't look like one of the usual flaky tests.

Indeed I don't remember seeing RepoTests fail, although on my fork's CI run it did not fail

:eyes:


Define a schema for validation of AEDT configuration files.

Description of the current limitations
The Configurations() class in \pyaedt\generic\configurations.py uses *.json as the format to save and read configurations for AEDT. In order to help ensure robustness and complex workflows it would be helpful to provide a json schema against which the *.json files can be validated.
Code sample expected
hfss = pyaedt.Hfss()
json_file = "/user/my/config.json"
if hfss.configurations.valid_config(json_file):
   hfss.configurations.import_config(conf_file)
else:
   raise ...

Useful links and references
https://json-schema.org/learn/getting-started-step-by-step

Resolved in #3994


Add managed endpoint count to status command

Occasionally there can be problems come up in clusters where the initial Cilium installation was unsuccessful, so when users create pods, Cilium does not actually manage the endpoints but they are managed by some other plugin (kubenet or another CNI).
The cilium status command currently prints a bunch of useful statistics around Cilium pods and whether they are ready or not, maybe we could add another line something like:
Cluster Pods:  10/10 managed by Cilium

The first number can be derived from $ kubectl get ciliumendpoints --all-namespaces -o json | jq '.items | length'.
The second number can be derived from $ kubectl get pods --all-namespaces -o json | jq '[.items[] | select(.spec.hostNetwork |.==null)] | length'.
If the counts are not equal, then we should consider that to be a warning sign.

/assign


T3 simulator source code seems not right

Hello,
I downloaded the simulator term 3 source code and after I opened it, I found it was actually Term 1 simulator. The T3 simulator should be for the path planning project, right?
Could you upload the correct T3 simulator source code please? If I did not open the source correctly, would someone guide me how to use the source code?
Any advice would be greatly appreciated.

@citlaligm Can you check on the Term 3 source code?


C/C++ flowgraph support

After reading the syntax description for flowcharts i am not sure if it is possible to generate flowgraphs for C/C++. (Flowgraphs do summarize process steps into process blocks in comparison with flowcharts which represent each statement as block.) The representation of the process blocks and the decision blocks itself is no problem. But the linking of the blocks and decision points with "arrows" to control structures (while loop, do while loop, for loop, if/else if/else, switch, etc.) could...

It might depend on how much details you try to squeeze in there. :)

What is the definition and where is the specification for C/C++ flowgraph?

The general definition (which ist not specific to C/C++) can be found on the wikipedia site "control flow graph". I think I found the best explanation and distinction between flow graphs and flow charts in "Software Testing Techniques" ISBN:0-442-20672-0.

Given how long ago this issue's activity died out, I'm closing it.
This allows us to maintain a fresh list of issues the community is interested in.


Generate scgpt cross check genes module

Changelog
Cross check genes component added
Issue ticket number and link
Closes #747
Checklist before requesting a review

[x] I have performed a self-review of my code

[ ] Conforms to the Contributor's guide

Check the correct box. Does this PR contain:

[ ] Breaking changes
[x] New functionality
[ ] Major changes
[ ] Minor changes
[ ] Documentation
[ ] Bug fixes

[x] Proposed changes are described in the CHANGELOG.md

[x] CI tests succeed!

Thanks a lot Jakub 🙏 👍
From my side things looks good when these adjustment to use a subsampled test dataset are made

Could you also merge the scgpt branch into 747-generate-scgpt-cross_check_genes-module?


Saving (repeatedly) with syntax errors causes code to be deleted and/or broken

I am re-reporting the issue from #109530 with additional info because I think there was a miscommunication about the severity of this issue and it was closed before I could provide more info. I cannot imagine that this very destructive and unexpected behavior is intended.
When tsconfig allowUnreachableCode is false (the default) and "editor.codeActionsOnSave": { "source.fixAll": true } is set, VSCode will delete code in an unpredictable way as a result of syntax errors because of error code 7027. On the other hand, it does not delete other "unused code" errors like 6196 (the interface Nothing in the example).

Additionally, it will continue to delete other parts of the code every time it is saved, as shown in the example gif. In a real world case, we have a utilities.ts file, and any time we save with a relevant syntax error, it will delete the next function on every repeated save, until the file is empty.
Additionally, it only partially deletes code where the to-be-deleted code has comments, which introduces additional syntax errors caused by VSCode, as shown by the // return\n} fragment in the example gif.
Accidental syntax errors are a common part of programming, and I don't think that VSCode deleting and breaking valid code as a result of a common mistake is good behavior for a code editor! It is not uncommon for us to save a file with an accidental syntax issue and not realize that code was deleted until we're trying to track down webpack errors.
I do not remember this ever happening until the last few weeks. I am not sure what changed to cause it. We have minimal changes to our configuration except for the VSCode updates and upgrading TypeScript to 4.0.3.

VSCode Version: 1.50.1
OS Version: 10.14.6
TypeScript: 4.0.3

Steps to Reproduce:

Create a file with this code:

export function anyFunc () => {
  // The return statement here with this syntax error triggers error 7027
  // which causes everything after it to be DELETED on save
  return
}

export const will_be_removed_on_first_save = () =>
  // return
}

export const will_be_removed_on_next_save = () => {
  return
}

interface Nothing {}

Save the file, and observe that the first export const is partially deleted, leaving // return and }
Save again and observe that the second export const is removed, leaving the previous partially deleted fragment intact, which creates a new syntax error
Save again and observe that the 6196 "unused code" error on Nothing is not automatically removed.

Does this issue occur when all extensions are disabled?: Yes

I already explained how this behavior is not enabled by default (and can be easily disabled) and how, if your code is not syntactically valid, we can't make an guarantees that anything will work

I am not concerned about the setting value, I am reporting that the behavior of the "all inclusive" settings is breaking things in a really bad way. I'm very confused how you are suggesting that this is acceptable behavior for a code editor. The demo video shows how much of a drastic breaking change it is to code.

Additionally, it is only deleting code partially, leaving some "unused code" behind. This behavior is internally inconsistent.

Your code is already broken. We make a best effort attempt to work with invalid code but will not get this right all the time.
If you don't like this happening on save, disable the setting


Build error on openSUSE in examples/osmium_convert.cpp

CMake output:
-- The C compiler identification is GNU 4.8.1
-- The CXX compiler identification is GNU 4.8.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test HAS_KEEP_INLINE_FUNCTIONS
-- Performing Test HAS_KEEP_INLINE_FUNCTIONS - Success
-- Boost version: 1.53.0
-- Found ZLIB: /usr/lib64/libz.so (found version "1.2.8")
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found EXPAT: /usr/lib64/libexpat.so (found version "2.1.0")
-- Found BZip2: /usr/lib64/libbz2.so (found version "1.0.6")
-- Looking for BZ2_bzCompressInit in /usr/lib64/libbz2.so
-- Looking for BZ2_bzCompressInit in /usr/lib64/libbz2.so - found
-- Found GDAL: /usr/lib64/libgdal.so
-- Looking for C++ include sys/types.h
-- Looking for C++ include sys/types.h - found
-- Looking for C++ include stdint.h
-- Looking for C++ include stdint.h - found
-- Looking for C++ include stddef.h
-- Looking for C++ include stddef.h - found
-- Check size of google::sparsetable::size_type
-- Check size of google::sparsetable::size_type - done
-- Found Osmium: include
-- Use C++ version: c++11
-- Configuring unit tests
-- Configuring unit tests - done
-- Looking for cppcheck
-- Looking for cppcheck - not found
--   Build target 'cppcheck' will not be available.
-- Configuring examples
-- Boost version: 1.53.0
-- Found the following Boost libraries:
--   program_options
-- Configuring examples - Building these examples:
--   - osmium_area_test
--   - osmium_convert
--   - osmium_count
--   - osmium_create_node_cache
--   - osmium_debug
--   - osmium_index
--   - osmium_read
--   - osmium_serdump
--   - osmium_toogr
--   - osmium_toogr2
--   - osmium_toogr2_exp
--   - osmium_use_node_cache
-- Configuring examples - done
-- Configuring documentation
-- Looking for doxygen
-- Found Doxygen: /usr/bin/doxygen (found version "1.8.5")
-- Looking for doxygen - found
-- Configuring documentation - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/eike/repos/build/osmium
$ make osmium_convert 2>&1 | head -n 20
[ 50%] Building CXX object examples/CMakeFiles/osmium_convert.dir/osmium_convert.cpp.o
In file included from /usr/include/boost/iterator/transform_iterator.hpp:23:0,
from /home/eike/repos/OSM/libosmium/include/osmium/io/detail/pbf_output_format.hpp:50,
from /home/eike/repos/OSM/libosmium/include/osmium/io/pbf_output.hpp:46,
from /home/eike/repos/OSM/libosmium/include/osmium/io/any_output.hpp:50,
from /home/eike/repos/OSM/libosmium/examples/osmium_convert.cpp:14:
/usr/include/boost/utility/result_of.hpp: In instantiation of ‘struct boost::detail::result_of_nested_result<const osmium::io::detail::PBFOutputFormat::relation(const osmium::Relation&)::__lambda23, const osmium::io::detail::PBFOutputFormat::relation(const osmium::Relation&)::__lambda23(const osmium::RelationMember&)>’:
/usr/include/boost/utility/result_of.hpp:170:8:   required from ‘struct boost::detail::tr1_result_of_impl<const osmium::io::detail::PBFOutputFormat::relation(const osmium::Relation&)::__lambda23, const osmium::io::detail::PBFOutputFormat::relation(const osmium::Relation&)::__lambda23(const osmium::RelationMember&), false>’
/usr/include/boost/utility/detail/result_of_iterate.hpp:27:8:   required from ‘struct boost::tr1_result_of<const osmium::io::detail::PBFOutputFormat::relation(const osmium::Relation&)::__lambda23(const osmium::RelationMember&)>’
/usr/include/boost/utility/detail/result_of_iterate.hpp:146:8:   required from ‘struct boost::result_of<const osmium::io::detail::PBFOutputFormat::relation(const osmium::Relation&)::__lambda23(const osmium::RelationMember&)>’
/usr/include/boost/mpl/eval_if.hpp:38:31:   required from ‘struct boost::mpl::eval_if<boost::is_same<boost::use_default, boost::use_default>, boost::result_of<const osmium::io::detail::PBFOutputFormat::relation(const osmium::Relation&)::__lambda23(const osmium::RelationMember&)>, boost::mpl::identityboost::use_default >’
/usr/include/boost/iterator/iterator_adaptor.hpp:160:12:   required from ‘struct boost::detail::ia_dflt_help<boost::use_default, boost::result_of<const osmium::io::detail::PBFOutputFormat::relation(const osmium::Relation&)::__lambda23(const osmium::RelationMember&)> >’
/usr/include/boost/iterator/transform_iterator.hpp:50:17:   required from ‘struct boost::detail::transform_iterator_base<osmium::io::detail::PBFOutputFormat::relation(const osmium::Relation&)::__lambda23, osmium::memory::CollectionIterator, boost::use_default, boost::use_default>’
/usr/include/boost/iterator/transform_iterator.hpp:74:9:   required from ‘class boost::transform_iterator<osmium::io::detail::PBFOutputFormat::relation(const osmium::Relation&)::__lambda23, osmium::memory::CollectionIterator, boost::use_default, boost::use_default>’
/home/eike/repos/OSM/libosmium/include/osmium/io/detail/pbf_output_format.hpp:547:99:   required from here
/usr/include/boost/utility/result_of.hpp:166:8: error: no class template named ‘result’ in ‘const struct osmium::io::detail::PBFOutputFormat::relation(const osmium::Relation&)::__lambda23’
struct result_of_nested_result : F::template result
^
In file included from /usr/include/boost/iterator/iterator_categories.hpp:15:0,
from /usr/include/boost/iterator/iterator_adaptor.hpp:14,

This looks very much like the boost library version is too old and doesn't support C++11 lambdas yet. Boost 1.55 works. We might have to set this as the minimum version required unless we can find a workaround.
Might be related to http://stackoverflow.com/questions/12672372/boost-transform-iterator-and-c11-lambda


newProjectLink

Here you can propose a link to a Free/OpenSource project that you think is new-contributers-friendly.

what about Openstack https://wiki.openstack.org/wiki/How_To_Contribute

Nice one !


how to setup config not to use Pusher?

it’s still relying on the pusher for the broadcast message service? In the config file, there’s pusher configuration, how do I disable pusher and use local messaging service via Redis or something ?
config/websockets.php
'apps' => [
        [
            'id' => env('PUSHER_APP_ID'),
            'name' => env('APP_NAME'),
            'key' => env('PUSHER_APP_KEY'),
            'secret' => env('PUSHER_APP_SECRET'),
            'enable_client_messages' => false,
            'enable_statistics' => true,
        ],
    ],

After reading Freeks blog post https://freek.dev/1228-introducing-laravel-websockets-an-easy-to-use-websocket-server-implemented-in-php I understand better why pusher is still there.
It's a drop-in replacement. So they implement the pusher API in your Laravel App. That's why they use the pusher variables by default.

Does this mean we register a Pusher account then use the config provided by Pusher in .env file..?
Have tried that and am getting the exception:
Exception `BeyondCode\LaravelWebSockets\WebSockets\Exceptions\UnknownAppKey` thrown: `Could not find app key `xxxxxxxxxxxxxxxxxxxx`.`
Unknown app id: exception `BeyondCode\LaravelWebSockets\WebSockets\Exceptions\UnknownAppKey` thrown: `Could not find app key `xxxxxxxxxxxxxxxxxxxx`.`.

Any help is appreciated, thanks.

Does this mean we register a Pusher account then use the config provided by Pusher in .env file..?
Have tried that and am getting the exception:
Exception `BeyondCode\LaravelWebSockets\WebSockets\Exceptions\UnknownAppKey` thrown: `Could not find app key `xxxxxxxxxxxxxxxxxxxx`.`
Unknown app id: exception `BeyondCode\LaravelWebSockets\WebSockets\Exceptions\UnknownAppKey` thrown: `Could not find app key `xxxxxxxxxxxxxxxxxxxx`.`.

Any help is appreciated, thanks.

Killed and restarted the websocket server and it now works as expected :-)
The server was already running when I updated the pusher .env variables, so guess I had to restart it so it makes use of the updated configuration.


It is already implemented, webpack-cli init, soon we will implement more templates

          > It is already implemented, `webpack-cli init`, soon we will implement more templates

Yes, I discovered him later, perhaps because he was not placed in the most prominent position on the official website: Quick Start, which made users want to use webpack quickly and encountered doubts.
Originally posted by @RSS1102 in https://github.com/webpack/webpack/issues/18295#issuecomment-2045744027

good idea


[Tabs]why when i click a tab, tabs before will also load data, but tabs after this tab will not？

Closing this for lack of information.

Please refer to https://github.com/tintin1343/material-ui/blob/master/CONTRIBUTING.md if you need help in posting any issue.


Can't install some instrumentations after installing opentelemetry-sdk 1.3

I don't have a full list because I've only tested some of the instrumentation we use at my company, but I've found the following behaviour for Sinatra, Sidekiq and Faraday.

Resolving dependencies...
Fetching gem metadata from https://rubygems.org/..
Resolving dependencies...
Fetching opentelemetry-api 1.2.0
Installing opentelemetry-api 1.2.0
Fetching opentelemetry-common 0.20.0
Fetching opentelemetry-registry 0.3.0
Fetching opentelemetry-semantic_conventions 1.10.0
Installing opentelemetry-common 0.20.0
Installing opentelemetry-registry 0.3.0
Installing opentelemetry-semantic_conventions 1.10.0
Fetching opentelemetry-sdk 1.3.0
Installing opentelemetry-sdk 1.3.0

root@8b1cc27be6c8:/test# bundle add opentelemetry-instrumentation-sidekiq
Fetching gem metadata from https://rubygems.org/..
Resolving dependencies...
Could not find compatible versions

Because opentelemetry-instrumentation-sidekiq < 0.7.0 depends on opentelemetry-api ~> 0.0
  and opentelemetry-instrumentation-sidekiq >= 0.7.0, < 0.8.0 depends on opentelemetry-api ~> 0.7.0,
  opentelemetry-instrumentation-sidekiq < 0.8.0 requires opentelemetry-api >= 0.0, < 1.A.
And because opentelemetry-instrumentation-sidekiq >= 0.8.0, < 0.9.0 depends on opentelemetry-api ~> 0.8.0
  and opentelemetry-instrumentation-sidekiq >= 0.9.0, < 0.10.0 depends on opentelemetry-api ~> 0.9.0,
  opentelemetry-instrumentation-sidekiq < 0.10.0 requires opentelemetry-api >= 0.0, < 1.A.
And because opentelemetry-instrumentation-sidekiq >= 0.10.0, < 0.11.0 depends on opentelemetry-api ~> 0.10.0
  and opentelemetry-instrumentation-sidekiq >= 0.11.0, < 0.12.0 depends on opentelemetry-api ~> 0.11.0,
  opentelemetry-instrumentation-sidekiq < 0.12.0 requires opentelemetry-api >= 0.0, < 1.A.
And because opentelemetry-instrumentation-sidekiq >= 0.12.0, < 0.13.0 depends on opentelemetry-api ~> 0.12.0
  and opentelemetry-instrumentation-sidekiq >= 0.13.0, < 0.14.0 depends on opentelemetry-common ~> 0.13.0,
  opentelemetry-instrumentation-sidekiq < 0.14.0 requires opentelemetry-api >= 0.0, < 1.A or opentelemetry-common ~> 0.13.0.
And because opentelemetry-instrumentation-sidekiq >= 0.14.0, < 0.15.0 depends on opentelemetry-common ~> 0.14.0
  and opentelemetry-instrumentation-sidekiq >= 0.15.0, < 0.16.0 depends on opentelemetry-common ~> 0.15.0,
  opentelemetry-instrumentation-sidekiq < 0.16.0 requires opentelemetry-api >= 0.0, < 1.A or opentelemetry-common ~> 0.13.0 OR ~> 0.14.0 OR ~> 0.15.0.

And because opentelemetry-instrumentation-sidekiq >= 0.20.2 depends on opentelemetry-common ~> 0.19.3
  and opentelemetry-sdk >= 1.2.0 depends on opentelemetry-api ~> 1.1,
  opentelemetry-sdk >= 1.2.0 requires opentelemetry-common ~> 0.13.0 OR ~> 0.14.0 OR ~> 0.15.0 OR ~> 0.16.0 OR ~> 0.17.0 OR ~> 0.18.0 OR >= 0.19.0, < 0.20.A.
So, because opentelemetry-sdk >= 1.3.0 depends on opentelemetry-common ~> 0.20
  and Gemfile depends on opentelemetry-sdk ~> 1.3,
  version solving has failed.

Please note that opentelemetry-sdk 1.3.0 was installed.
Installing both gems in one go with bundle add opentelemetry-sdk opentelemetry-instrumentation-sidekiq works, and it also works if you install the instrumentation before the SDK, but in both cases the SDK version installed is 1.2.1, which must be the highest compatible version that Bundler finds.
Is this something that needs to be dealt with? Or will it get "auto-solved" with the next release...? Don't know what the process is, but happy to help with bumping versions and testing if needed.

Thanks for making us aware of this gem dependency problem.
This looks like a tangled mess where the SDK depends on a specific version of the common gem but the instrumentations are pessimistically locking on that version, however the instrumentations don't have a dependency in the SDK.
I'll take a look later today to see if we can get a fix out asap

Hmm... While debugging locally, I have noticed that, for instance, opentelemetry-instrumentation-sidekiq fails to install from Rubygems but can be installed from the local copy with --path.
I see that the current version 0.24.1 in Rubygems depends on opentelemetry-common ~> 0.19.3, while in the repo that dependency has already been updated to ~> 0.20.0, and the gem version remains at 0.24.1.
Same thing happens for Faraday, Rack and Sinatra, from the small group I've tested.
Does this mean that this is just a matter of releasing the gems? (And I guess during the release process is when you bump versions...? Like Sidekiq 0.24.1 to 0.24.2 for example)

I kicked off a release request but there wasn't anything pending a release other than ottrace propagators. I still need some time to look into this.

I've been looking at the release request logs and how Toys works, and I think the problem might be that only chore commits have been added since the last release for the affected gems.
Does that make sense, before I bury you in specific logs and pointers to Toys code? If yes, keep reading. If not, don't bother :)
From the logs:
[2023-07-19 20:12:03  INFO]  New version of opentelemetry-instrumentation-sidekiq is 0.24.2 by commit message analysis
...
[2023-07-19 20:12:05  INFO]  Starting with 43 gems in the release list
[2023-07-19 20:12:05  INFO]  1 gems remain after pruning those with no changes
...

In the Toys code I see that pruning happens when the CHANGELOG has been deemed not to have new entries (code), and new entries are added for fix|feat|docs commits, not chore (which makes all the sense) (code and code)
Commits for opentelemetry-instrumentation-sidekiq since last release:
* b12ea6d2 chore(deps-dev): update rubocop to ~> 1.54.1 in multiple gems (#555) (9 days ago) Robb Kidd
* cc244b9a chore(deps): update opentelemetry-common from 0.19.3 to 0.20.0 (#537) (3 weeks ago) Robb Kidd
* 72e1ab9c (... tag: opentelemetry-instrumentation-sidekiq/v0.24.1 ...)

For opentelemetry-propagator-ottrace there's a docs commit that, as expected, generates an entry in the Changelog in #571.
The rest of chore commits don't generate entries.
* b12ea6d2 chore(deps-dev): update rubocop to ~> 1.54.1 in multiple gems (#555) (9 days ago) Robb Kidd
* 0f868b78 docs: Add some clarity to ottrace docs (#522) (12 days ago) Ariel Valentin
* b25ceafb chore: Combine dependabot rubocop bumps (#496) (7 weeks ago) Eric Mustin
* 499983c4 chore(deps-dev): update rubocop requirement from ~> 1.49.0 to ~> 1.50.2 in multiple gems (#437) (3 months ago) Robb Kidd
* 1b955ac8 (... tag: opentelemetry-propagator-ottrace/v0.21.0 ...)

This release request should fix this: https://github.com/open-telemetry/opentelemetry-ruby-contrib/issues/569

Awesome, the instrumentations in the OP now get installed correctly after the SDK.
I'm closing the issue as this is solved. Maybe we can talk somewhere else about testing the installation (if deemed necessary).
Thanks!

@bolandoboy Thank you for verifying. I started a PR to run installs on latest versions of releases to try and avoid this problem and would appreciate your feedback on it.
https://github.com/open-telemetry/opentelemetry-ruby-contrib/pull/578


Fix Prometheus naming convention issues

There are a number of metrics that have Prometheus naming issues, for example counters missing _total.

CC @repl-mike-roest

These were the ones mismatched discovered in #411
elasticsearch_breakers_overhead counter metrics should have "_total" suffix
elasticsearch_breakers_tripped counter metrics should have "_total" suffix
elasticsearch_cluster_health_json_parse_failures counter metrics should have "_total" suffix
elasticsearch_cluster_health_total_scrapes counter metrics should have "_total" suffix
elasticsearch_clustersettings_stats_json_parse_failures counter metrics should have "_total" suffix
elasticsearch_clustersettings_stats_total_scrapes counter metrics should have "_total" suffix
elasticsearch_filesystem_io_stats_device_operations_count counter metrics should have "_total" suffix
elasticsearch_filesystem_io_stats_device_read_operations_count counter metrics should have "_total" suffix
elasticsearch_filesystem_io_stats_device_read_size_kilobytes_sum counter metrics should have "_total" suffix
elasticsearch_filesystem_io_stats_device_write_operations_count counter metrics should have "_total" suffix
elasticsearch_filesystem_io_stats_device_write_size_kilobytes_sum counter metrics should have "_total" suffix
elasticsearch_index_stats_json_parse_failures counter metrics should have "_total" suffix
elasticsearch_indices_completion_size_in_bytes counter metrics should have "_total" suffix
elasticsearch_indices_docs_total non-counter metrics should not have "_total" suffix
elasticsearch_indices_fielddata_evictions counter metrics should have "_total" suffix
elasticsearch_indices_filter_cache_evictions counter metrics should have "_total" suffix
elasticsearch_indices_flush_time_seconds counter metrics should have "_total" suffix
elasticsearch_indices_get_exists_time_seconds counter metrics should have "_total" suffix
elasticsearch_indices_get_time_seconds counter metrics should have "_total" suffix
elasticsearch_indices_query_miss_count counter metrics should have "_total" suffix
elasticsearch_node_stats_total_scrapes counter metrics should have "_total" suffix
elasticsearch_indices_mappings_stats_field_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_indices_request_miss_count counter metrics should have "_total" suffix
elasticsearch_indices_deleted_docs_total non-counter metrics should not have "_total" suffix

elasticsearch_indices_query_miss_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_indices_search_query_time_seconds counter metrics should have "_total" suffix
elasticsearch_indices_request_miss_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_indices_search_suggest_time_seconds counter metrics should have "_total" suffix
elasticsearch_indices_segment_count_total non-counter metrics should not have "_total" suffix
elasticsearch_indices_segment_fields_memory_bytes_total non-counter metrics should not have "_total" suffix
elasticsearch_indices_settings_stats_total_scrapes counter metrics should have "_total" suffix
elasticsearch_indices_segment_points_memory_bytes_total non-counter metrics should not have "_total" suffix
elasticsearch_indices_translog_operations counter metrics should have "_total" suffix
elasticsearch_jvm_gc_collection_seconds_count counter metrics should have "_total" suffix
elasticsearch_snapshot_stats_json_parse_failures counter metrics should have "_total" suffix
elasticsearch_indices_segment_index_writer_memory_bytes_total non-counter metrics should not have "_total" suffix
elasticsearch_indices_segment_memory_bytes_total non-counter metrics should not have "_total" suffix
elasticsearch_indices_segment_version_map_memory_bytes_total non-counter metrics should not have "_total" suffix
elasticsearch_filesystem_io_stats_device_operations_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_filesystem_io_stats_device_read_operations_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_filesystem_io_stats_device_write_operations_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_indices_segment_terms_memory_total non-counter metrics should not have "_total" suffix
elasticsearch_indices_segments_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_jvm_gc_collection_seconds_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_filesystem_io_stats_device_write_size_kilobytes_sum non-histogram and non-summary metrics should not have "_sum" suffix
elasticsearch_filesystem_io_stats_device_write_size_kilobytes_sum use base unit "bytes" instead of "kilobytes"
elasticsearch_index_stats_total_scrapes counter metrics should have "_total" suffix
elasticsearch_indices_get_missing_time_seconds counter metrics should have "_total" suffix
elasticsearch_indices_query_cache_count counter metrics should have "_total" suffix
elasticsearch_indices_query_cache_evictions counter metrics should have "_total" suffix
elasticsearch_indices_request_cache_count counter metrics should have "_total" suffix
elasticsearch_indices_request_cache_evictions counter metrics should have "_total" suffix
elasticsearch_indices_search_fetch_time_seconds counter metrics should have "_total" suffix
elasticsearch_indices_search_scroll_time_seconds counter metrics should have "_total" suffix
elasticsearch_indices_translog_size_in_bytes counter metrics should have "_total" suffix
elasticsearch_jvm_gc_collection_seconds_sum counter metrics should have "_total" suffix
elasticsearch_indices_segment_norms_memory_bytes_total non-counter metrics should not have "_total" suffix
elasticsearch_indices_settings_stats_json_parse_failures counter metrics should have "_total" suffix
elasticsearch_jvm_memory_pool_max_bytes counter metrics should have "_total" suffix
elasticsearch_jvm_memory_pool_peak_max_bytes counter metrics should have "_total" suffix
elasticsearch_jvm_memory_pool_peak_used_bytes counter metrics should have "_total" suffix
elasticsearch_node_stats_json_parse_failures counter metrics should have "_total" suffix
elasticsearch_process_cpu_time_seconds_sum counter metrics should have "_total" suffix
elasticsearch_thread_pool_rejected_count counter metrics should have "_total" suffix
elasticsearch_indices_query_cache_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_snapshot_stats_total_scrapes counter metrics should have "_total" suffix
elasticsearch_indices_completion_bytes_total non-counter metrics should not have "_total" suffix
elasticsearch_indices_request_cache_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_indices_segment_doc_values_memory_bytes_total non-counter metrics should not have "_total" suffix
elasticsearch_indices_segment_fixed_bit_set_memory_bytes_total non-counter metrics should not have "_total" suffix
elasticsearch_indices_store_size_bytes_total non-counter metrics should not have "_total" suffix
elasticsearch_process_open_files_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_thread_pool_active_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_thread_pool_largest_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_thread_pool_queue_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_thread_pool_rejected_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_thread_pool_threads_count non-histogram and non-summary metrics should not have "_count" suffix
elasticsearch_filesystem_io_stats_device_read_size_kilobytes_sum non-histogram and non-summary metrics should not have "_sum" suffix
elasticsearch_jvm_gc_collection_seconds_sum non-histogram and non-summary metrics should not have "_sum" suffix
elasticsearch_process_cpu_time_seconds_sum non-histogram and non-summary metrics should not have "_sum" suffix
elasticsearch_filesystem_io_stats_device_read_size_kilobytes_sum use base unit "bytes" instead of "kilobytes"
elasticsearch_thread_pool_completed_count counter metrics should have "_total" suffix
elasticsearch_thread_pool_completed_count non-histogram and non-summary metrics should not have "_count" suffix


Does Client.users not update on its own with respect to User.game?

I wrote some sample code to print out the games of all the users in my channel using the bot's users cache, but the games don't update when they change (although the cache seems to update when users go online/offline).  Is this intended?  I know that the presence event exists, but I didn't know if it was as easy as calling bot.users.update(presenceVar1, presenceVar2) and if that was even necessary.
Thanks!  Keep up the great work. :)

what version of discord.js?

package.json says 8.0.0.

Latest is 8.1.0, try that

Upgrading to 8.1.0 did fix the issue!  Apologies, I should have tried that first.  Thank you for your help!


Progress bars for steps (integration of tqdm)

Is there a way to use tqdm inside a step (especially a foreach task)?
I want to have a progress bar for each parallel task.
Currently I am only able to see progress bars when a task has already successfully finished.

I am not familiar how logging is handled in metaflow but here are some examples from tqdm that could be helpful to make the progress bar work:
https://github.com/tqdm/tqdm/blob/master/examples/parallel_bars.py
https://github.com/tqdm/tqdm/blob/master/examples/redirect_print.py
In general, it looks like messages are only printed when the task completed.
This makes the use of tqdm pointless.
Is there a way to immediately print to console?
Here is the source code for the example from the gif:
from metaflow import FlowSpec, step

class HelloFlow(FlowSpec):
    """
    A flow where Metaflow prints 'Hi'.

    Run this flow to validate that Metaflow is installed correctly.

    """
    @step
    def start(self):
        """
        This is the 'start' step. All flows must have a step named 'start' that
        is the first step in the flow.

        """
        print("HelloFlow is starting.")
        self.multi_processing = list(range(4))
        self.next(self.hello, foreach="multi_processing")

    @step
    def hello(self):
        """
        A step with parallel processing that should be monitored with tqdm.

        """

        from tqdm import tqdm
        from time import sleep
        from random import random

        interval = random() * 0.001
        for _ in tqdm(range(10000)):
            sleep(interval)

        self.next(self.join)

    @step
    def join(self, inputs):
        """
        Join our parallel branches and merge results.

        """

        self.next(self.end)

    @step
    def end(self):
        """
        This is the 'end' step. All flows must have an 'end' step, which is the
        last step in the flow.

        """

        print("HelloFlow is all done.")

if __name__ == '__main__':
    HelloFlow()

Thank you for the very elaborate description (with screencasts :))
Will take a look and get back to you.

Sorry for not having an update on this. We are looking into it internally and seeing if there is a way we can make this work. From the screencast you've pasted, clearly the log lines from tqdm are:

Getting buffered (and hence seeing it later)
Not seeing updates of progress - this is the one I need to spend more time debugging if there is a way to make it work with our log buffering + multiprocessing solution.

@seeravikiran Do you have any update on this?

The buffering issue happened to me with lightgbm training output. The training results are not printed every iteration, but at the end.

Unfortunately I don't have an update on this yet. Apologies for that.

@seeravikiran Do you have any update on this?

I don't have any new updates about this. Few related comments though -

We are reworking our log streaming (and tailing) solution internally; and we hope to announce it externally as well after converging the codebases. We hope to make log tailing using the metaflow client so issues w.r.t buffering and tailing should be better after that.
Specifically for observing progress of foreach tasks and making it work with tqdm, have you considered doing the progress tracking outside of Metaflow - probably in a separate wrapper script; by outputting special lines perhaps after each iteration like print("<SHOW PROGRESS 1%>").
I don't know tqdm well enough to know if you can use special log lines to bump up the progress.

Curious to hear to your response? I also apologize for extremely slow response rate from my front on this issue.

I have also stumbled into this issue. Have tried various methods for forceably releasing the buffer on each iteration but I clearly don't understand enough about how metaflow is capturing logs to identify a workaround.

I think tqdm might be messing with buffer flushing in unexpected ways. Running the below flow with and without tqdm set in the for loop def shows that all print output is witheld until the end of the step only when tqdm is used:
from metaflow import FlowSpec, step
import tqdm
from time import sleep

class TQDMFlow(FlowSpec):

    @step
    def start(self):
        print('Training...')
        for t in tqdm.tqdm(range(100)):
            print(t)
            sleep(0.004)
        sleep(5)
        self.next(self.end)

    @step
    def end(self):
        pass

if __name__ == '__main__':
    TQDMFlow()

more discussions here https://outerbounds-community.slack.com/archives/C020U025QJK/p1624953736201700
here's a workaround https://share.getcloudapp.com/4guneg9E
https://gist.github.com/tuulos/ca8029e3d2ce8141226e4b7a474f4750

@jonaschn I came up with a solution which is a little less intrusive: https://stackoverflow.com/questions/68225881/how-to-show-tqdm-progress-in-metaflow
@tuulos Is there a way to make MetaFlow show stderr output instead of hiding it


Local development: Trace error

When developing locally, I get this error.
The error mentions project<PHONE_NUMBER>9 is.
It is not the number of the one I am currently developing for. I have no idea what this error is about.
ERROR:@google/cloud-trace: TraceWriter: error:  403 { [Error: Stackdriver Trace API has not been used in project<PHONE_NUMBER>9 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/cloudtrace/overview?project=32555940559 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.]
  code: 403,
  errors:
   [ { message: 'Stackdriver Trace API has not been used in project<PHONE_NUMBER>9 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/cloudtrace/overview?project=32555940559 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.',
       domain: 'global',
       reason: 'forbidden' } ] }

This is because you used gcloud auth login. The project number:<PHONE_NUMBER>9 is gcloud project number. You should use: gcloud beta auth application-default login. Once you did that, the issue should go away.

This is local development, I do not want to use Trace locally so I would prefer not have to do the auth step.
Also, the error message could be much better: How I am supposed to know that<PHONE_NUMBER>9 is gcloud project number?

If you would like to disable trace locally you can set the GCLOUD_TRACE_DISABLE environment variable. The error message is coming from the trace service and they already have a bug tracking the improvement of this message.

We now have documentation of the mechanisms for disabling the agent for local development (#259). I'll close this for now but please reopen if there are further improvements to be made.


Update gitattributes

Some FSharp files have been misidentified as Forth.

The source branch is no longer live, closing the PR.


issue with tfrecord example that has mutliple boxes

Hi,
I have an issue of incompatible shape when I want to fine tune the model with a tfrecord which has been build with examples images containing mutliple boxes.
You can reproduce the error with this small tfrecord file : [train_1.zip]
and use train.py with it.
You will see the error below :
Cannot batch tensors with different shapes in component 1. First element had shape [2,5] and element 1 had shape [3,5]
(https://github.com/zzh8829/yolov3-tf2/files/4818311/train_1.zip)
Can someone spot what doesn't work with this?
Many thanks

Did you find the solution?


[zh] sync admission-controllers.md

Sync with en text:
content/zh-cn/docs/reference/access-authn-authz/admission-controllers.md

See preview please.

/approve


Make a navigation drawer divider by group

Idea Description
Make DrawerGroup and add it in DrawerItem for inserting divider.
like this,
DrawerItem.Sessions(DrawerGroup.Session, R.string.title_sessions, Icons.Default.Event, SessionsNavGraph.sessionRoute),

Currently, this feature is implemented by a if statement in NavigationDrawerItem
if (drawerItem == DrawerItem.Sessions || drawerItem == DrawerItem.Map) {

Reference images and links

Figma

screenshot

🙋♂

Thanks! Assigned ➗

@Kaito-Dogi How's it going?

@takahirom
Sorry for the delay, got caught up in figuring out how to implement this, sorry!
I have submitted a pull request #542 , please check back.


Backport of IndexServiceTest

Summary of the changes / Why this improves CrateDB
Backport of IndexServiceTest and depending https://github.com/elastic/elasticsearch/commit/3c352a85963f47a8272025e1969982bbe64c6a87
See individual commits.
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

This needs one more iteration.

Ready for review.

retest this please

The squashing went wrong, one moment.

Ok, ready for review. Last flaky test is also fixed.


Add prow configs for eks-kubeflow-workshop

Issue #, if available:
#76
Description of changes:
This is for eks-kubeflow-workshop
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/lgtm


[Mi Account support]

Can Mi Cloud be added so that all photos and albums can be synced to an AOSP ROM from an Mi Account or it's already been added.
If it's added, how Mi Cloud can be installed and activated there.
Thanks in advance!

@reiryuki Explain why you're closing every issue I made - do you maybe have an personal problems with these type of questions or what
Sorry but I cannot understand your reactions - I've alsobtried to use Discussions tab but it seems that no one is using it and the only thing that gets an attention is this issues tab
So please explain. Thanks!


OAuth2AuthorizationServerConsentTests fails when trying to retrieve buttons

This is my first time submitting an issue.  I hope I have followed the guidelines correctly. There was no need to submit a working example in this case, as the bug is reproducible as-is.
Describe the bug
The following lines fail in OAuth2AuthorizationServerConsentTests with a NullPointerException.
In whenUserConsentsToAllScopesThenReturnAuthorizationCode():
DomElement submitConsentButton = consentPage.querySelector("button[id='submit-consent']");

In whenUserCancelsConsentThenReturnAccessDeniedError():
DomElement cancelConsentButton = consentPage.querySelector("button[id='cancel-consent']");

To Reproduce
I output the consentPage as XML:
final HtmlPage consentPage = this.webClient.getPage(this.authorizationRequestUri);
System.out.println(consentPage.asXml());

Here are the relevant lines from the output. You can see that neither of the buttons contains an id.

    <button class="btn btn-primary btn-lg" type="submit">
        Submit Consent
    </button>

    <button class="btn btn-link regular" type="reset">
        Cancel
    </button>

Expected Behavior
The buttons are retrieved from the consent page correctly

obviously your OAuth2AuthorizationEndpointFilter.java is not lastest:

there is my test:

So make sure you CODE LASTEST.


classloader error when updating local lib while keeping sbt running

steps to reproduce

git clone https://github.com/mpollmeier/sbt-publishlocal-bug.git
open two terminals, one in library, one in service
in library: sbt publishLocal
in service: start sbt, run compile (everything compiles fine), keep sbt open
in library: change anything, e.g. echo "object A" >> src/main/scala/Library.scala
in library: sbt publishLocal
in service: run compile again

Result
Fails to load the jar, with different error messages, depending on god knows why. These ones I've seen so far:
[error] error while loading Library, invalid stored block lengths

[error] error while loading Library, ZIP_Read: error reading zip file

[error] error while loading Library, class file '/home/mp/.ivy2/local/sbttest/library_2.12/0.1-SNAPSHOT/jars/library_2.12.jar(Library.class)' is broken
[error] (class java.lang.ArrayIndexOutOfBoundsException/627)

error while loading Library, read error
[error] /home/mp/tmp/sbt-publishlocal-bug/service/src/main/scala/Service.scala:3: Library does not have a constructor

followed by:
[error] /home/mp/tmp/sbt-publishlocal-bug/service/src/main/scala/Service.scala:3:11: Library does not have a constructor
[error]   println(new Library().foo)
[error]           ^
[error] two errors found

This problem exists in sbt 0.13.16 and 1.0.2, with both publishLocal and publishM2.
I searched around and the only related issue I found was https://github.com/sbt/sbt/issues/892 , which is about sbt plugins, and suggests that this is a jvm classloader issue, and that in general, sbt can cache/reuse class loaders, but it only currently does this for Scala jars, the loaders are behind SoftReferences, and it checks the last modified time before reusing the class loader.
Since this is such a common use case, I am surprised that there's not more people talking about it - or am I doing something wrong?
If not, it would really be great if we could provide a workaround, e.g. by catching this error and reloading the classloader. I'm happy to help with the implementation if you point me in the right direction.

I have been running up against this issue for several months now.  I was assuming I was doing something wrong when I didn't see anyone else with the issue and it seemed like such a common use case.
In the past I would essentially continually run ~publishLocal from one project and ~run in another and I could edit any file without worrying which project it was from.   I have been using this mode of development for several years and it only stopped working recently; so it has worked in the past.  However, there were several big jumps that I moves that happened at the same time and I thought it could be related to any of the following changes:

moved from scala-2.11 to scala-2.12
moved from sbt-0.13.14  to sbt-0.13.16 (and 1.0.2)
moved from jdk7 to jdk8

If I have time; I will try to roll back to a set of versions that I did work.

Your first idea was right: the problem doesn't exist with scala 2.11.11, which suggests that this isn't actually an sbt problem...

Interesting you have the same issue.  I’m very surprised no one else has run into this.   I was able to verify that my environment does work with jdk8, sbt-0.13.6 and scala-2.11.11 so it seems like a 2.12 related issue.
Additionally, to reproduce the 2.12 errors, I had to make changes in the upstream project file that depended on classes that have changed in the downstream .  In other words a 2.12 push worked if the there were no dependent changes.  However,  a “clean; publishLocal” always causes a break.

I just bisected the officially released scala versions and found that 2.12.0-M3 is the last working version, and 2.12.0-M4 is the first version with this bug. Next step: trace it down to the actual commit.

Unfortunately back then the sbt build of the scala repo wasn't as good as it is today. I can run sbt publishLocal on the (e.g. revision d0ca6ed277) and it publishes as 2.12.0-SNAPSHOT, but my sample projects don't find it. For later scala versions the same process works just fine :(

I'm not sure, but seems like scala changes the way how it loads jar files. Wierd things start to happen if jar file is modified in place. Looks like it somhow uses old ZipEntry pointers to access updated jar content. This seems relevant: #3090

I used git bisect and traced it down to this commit: https://github.com/scala/scala/commit/6cb50acfb5ee4df342e83d8505116d4607
It introduces a VirtualDirectoryFlatClassPath, so we're getting closer. I filed a separate issue: https://github.com/scala/bug/issues/10541

Using sbt-1.1.0-RC1 it seems to work now.  I tested it with scala-2.12.4  If it was a scala issues, maybe sbt server now reloads the entire jar file in memory.

thanks @drxcc, I can confirm that it's fixed in 1.1.0-RC1 in combination with scala 2.12.4. I first tested with 2.12.3 and there it is/was still broken. anyway, from my perspective we can close this.


Schedule is always turned on when away mode is turned off

First: thank you for writing this, it works great!  With the recent Nest announcements, I ditched it and bought a thermostat with local control.  Everything works great now that I updated to 0.7, however I don't make use of the schedule functionality.
9194fa3e0d510ff05d88823eb41571e01e2990d7 introduced the behavior that turning away off, the schedule always gets turned on.  The comments say that you can't set away mode to 'on' when a schedule is also set, but this doesn't seem to be the case on my Venstar. See curl output below, and information about my API version.
Is this fixed in my firmware's API version? Or did you encounter this behavior on a different thermostat? I have a T7850.
I'm happy to open a PR but not sure what the best way to fix it is. Thoughts?

Could we rely on the end user of this library to call set_schedule themselves before/after caling set_away?  This would be my preference, by having the user of the library overcome the quirk in whatever firmware does this, rather than assuming all users want schedules turned on.

Could we only do this behavior on affected Thermostat firmwares?

{
    "api_ver": 7,
    "type": "residential",
    "model": "COLORTOUCH",
    "firmware": "5.10"
}

Schedule is on, away is off:
$ curl -s http://thermostat.home.bitbin.de/query/info | jq '{schedule: .schedule, away: .away}'
{
  "schedule": 1,
  "away": 0
}
$ curl -d "away=1" -X POST http://thermostat.home.bitbin.de/settings
{"success":true}
$ curl -s http://thermostat.home.bitbin.de/query/info | jq '{schedule: .schedule, away: .away}'
{
  "schedule": 1,
  "away": 1
}

I was able to confirm that my unit operates the same as yours when I use the curl commands.  I need to try it in HomeAssistant to see if I can reproduce what I was seeing back in October that caused me to make those changes in the first place.  I can only do it when I'm out at the place with the thermostat though.  I'll get back to you when I've had a chance.

This was addressed in PR #10

Thanks

@stbenjam I'm assuming that if you are hitting this issue, you are likely using this lib with Home Assistant. If so, build this as 0.8 and apply the following patch to the Venstar component to make  preset_mode/hold_mode fully functional: https://github.com/nkaminski/home-assistant/tree/venstar-0.8pre

I have a patch locally already that works but it would be good to get an official update in Home Assistant 0.97.
@hpeyerl would you mind releasing 0.8 to PyPi when you have a chance?

I can release a 0.8 anytime.  I have to think about what this is going to do to my HomeAssistant.  I want it to go on-schedule when I turn off 'Away'.


Unavailable device_tracker causes map to not draw anything

Issue description:
When device_tracker has state Unavailable, no map is drawn at all
Expected:
Map is drawn still but without the unavailable device_trackers (same behavior as with the HA included Map Card)
Symptom: ha-map-card shows "Error found in first run. check Console"
Console highlights map-card.js line https://github.com/nathan-gs/ha-map-card/blob/1cd63018e7a8723f6da54b29b62505471a033915/src/components/MapCard.js#L240
238     // Get lat lng
239      let latLng = HaMapUtilities.getEntityLatLng(configEntity.id, hass.states);
240      const latitude = latLng[0] ?? null;
241      const longitude = latLng[1] ?? null;

map card configuration:
type: custom:map-card
title: Location history 24h
card_size: 6
zoom: 19
x: "11.000000"
"y": "48.000000"
tile_layer_url: >-
  https://server.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer/tile/{z}/{y}/{x}
tile_layer_attribution: >-
  Tiles © Esri — Source: Esri, i-cubed, USDA, USGS, AEX, GeoEye,
  Getmapping, Aerogrid, IGN, IGP, UPR-EGP, and the GIS User Community
tile_layer_options:
  maxZoom: 19
  referrerPolicy: strict-origin-when-cross-origin
theme_mode: light
entities:
  - entity: device_tracker.uwb_anchor_a1
    display: marker
    size: 16
    color: grey
    z_index_offset: 0
  - entity: device_tracker.uwb_anchor_a3
    display: marker
    size: 16
    color: grey
    z_index_offset: 0
  - entity: device_tracker.uwb_anchor_a4
    display: marker
    size: 16
    color: grey
    z_index_offset: 0
  - entity: device_tracker.uwb_tag
    history_start: 1 hours ago
    focus_on_fit: false
    display: marker
    size: 20
    color: green
    z_index_offset: 40
    fallback_x: "11.00000"
    fallback_y: "48.00000"

@realzoulou what behavior would you prefer? Ignore items without lat/long? The current idea is to give a quick error.

@nathan-gs
Imho the card should post a message in console & show available entities.
If none of them can be shown -> show a home position.
Use case:
Assume there are meteorological data (temperature, pressure) provided by some integrations; and sensors have latiture/longitude.
Then I would ad on a card zone.my_castle & sensors with meteo data in this region.
Due to some reasons, this meteo integration does not create a sensor (or it becomes unavailable) -> a card does not show available data (or at least my castle).

@nathan-gs I would not necessarily need to see any error message indicating a sensor is not available. But agree with @ildar170975  that for some use cases it would be beneficial to get some sort of indication about why the card is not showing expected data.

I would choose a "log a message to console" - but a user (esp. a beginner) may not notice it if a Code inspector (or whatever it is called in a particular browser) is not shown.
Another way could be displaying an error badge on a map:

with a tooltip like "Some errors, check browser's console for details".


Compatibility with boon table plugin

added calls to options_windows()
added e8 export
added Log window, to show what is printed with e3/e8
added e5 export for default colors

I have changed what you wanted and also added the creation of addons/arcdps folders, so my plugin can save it's settings :)
If you have anything else say so, otherwise it is ready to get merged.


Adding integration tests to demonstrate roundtripping containers and binaries

Adding tests demonstrating import/export of:

Metadata (including typed literals, references to other repository resources, hash URI resources)
LDP Containers including Direct and Indirect
Binaries (including external content redirects)

Fixes https://jira.duraspace.org/browse/FCREPO-2192

Now you are just showing off, @escowles. These tests are deluxe.
:+1:


fix: modify lc mnlp sampling

Codecov Report

Merging #6 (c963d2e) into main (0082f7e) will decrease coverage by 3.32%.
The diff coverage is 78.94%.

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   73.47%   70.14%   -3.33%
==========================================
  Files           9       11       +2
  Lines         475      556      +81
==========================================
+ Hits          349      390      +41
- Misses        126      166      +40

Impacted Files
Coverage Δ

seqal/tagger.py
61.01% <61.01%> (ø)

seqal/query_strategies.py
45.96% <91.66%> (-1.69%)
:arrow_down:

seqal/active_learner.py
61.29% <100.00%> (ø)

tests/conftest.py
71.69% <100.00%> (-16.04%)
:arrow_down:

tests/test_query_strategies.py
100.00% <100.00%> (ø)

tests/test_tagger.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


[TF] Remove GPE-related dead code from TensorFlow.

This PR removes dead code from the TensorFlow library that was initially added only for GPE. For context, GPE was removed by #24418.

Remove _ExpressibleByTensorFlowOp.

Remove most @inline(__always) from TensorFlow APIs, which were added in early 2018 when GPE deabstraction was not able to recursively inline all functions that use #tfops.

Remove TensorSendableReceivable and its conformances, which were added in early 2018 when GPE send/receive was being developed.

Remove functions and protocol requirements added for scalar promotion. Scalar promotion was a feature introduced in early 2018 that was able to turn code like Tensor(x.sum()) into send/receive-free data flow in a TensorFlow graph. It was already disabled a long time ago. The following are removed:

Protocol requirements _getScalarOrDie(_:) and _getScalar(_:) in _TensorFlowDataTypeCompatible
Functions _TFGetScalarOrDie(_:) and _TFGetScalar(_:)

Remove functions and protocol requirements added for code hoisting for partitioning (more specifically, hoisting code before the "tensor start point" in a partitioning region). These were added in early 2018, because GPE at the time did not support send/receive, and that host-only random initializers would require send/receive if they appeared inside a partitioning region.

Protocol requirement _hoistableClosure(_:) in _TensorFlowDataTypeCompatible
Function _TFHoistable(_:)

Remove compiler-known functions for constant tensor initialization. They were used for enabling the partitioning pass to transform array literals intro Const nodes in TensorFlow graphs to avoid copies. The following are removed:

_TFTensorFromScalars(_:shape:)
_TFTensorFromScalars1D(_:)
_TFTensorFromScalar(_:)
_TFStringTensorFromStrings(_:shape:)
_TFStringTensorFromStrings1D(_:)
_TFStringTensorFromString(_:)

@swift-ci please test tensorflow

This is all fine with me.


"Compressed" CompositeBasis

As discussed in #39, It would be great for CompositeBasis to efficiently store contiguous strings of N of the same basis tensored together so that Basis^N takes O(1). If something like that is implemented, then we can have something like const NQubitBasis(N) = SpinBasis(1//2)^N.

I'm not sure I understand the utility of this. I think there are advantages to having an explicit list of bases in CompositeBasis. How about introducing AbstractCompositeBasis and having a subtype that does this "compression"?

I was imagining that once we define the interface for composite bases appropriately (#40 currently introduces the bases method to get the list of bases, but in #39 I'm working with implementing Base.getindex instead), then so long as we respect the interface, we can experiment with different ways of storing composite basis information depending on the use case and give options for more efficient ones.
I think this has utility in any package that subtypes AbstractState and AbstractOperator, and hence should implement  the basis method, and furthermore has a representation which scales is efficiently with the number of modes involved (such as Gabs or QuantumClifford). Then the overhead of keeping an explicit list of bases might not be so negligible.
I guess the question is whether it makes sense to have some AbstractCompositeBasis type or just have a method interface that every basis must conform to which allows for querying it's tensor decomposition and thus one could view every basis as essentially a composite basis? For example we could add a .modes field to every basis so that no CompositeBasis is necessary to express homogeneous tensor products of the same basis.


System migration compatibility with DataModels

System migrations are currently asynchronous and called from a "ready" hook. In order for full adoption of actor and item TypeDataModels the system frame needs to be adapted. The current hazy plan is:

TypeDataField#migrateSource overrides should check the document's schema version: if lower than a certain cutoff point, data-model migrations are skipped.
System asynchronous migrations operate on the document, catching it up to the schema version cutoff.
The document's TypeDataField is notified to recheck and run migrations for schema versions past the cutoff point, which are exclusively synchronous.
A no-diff update is made for each migrated document, synchronizing the data maintained by the server and what is found in #_source.

Questions/challenges:

Will unlinked tokens suddenly have ballooned delta with the no-diff update? If so, how can this be avoided?
Though we may wish to avoid it in the future, there may be a very strong perceived need for later asynchronous migrations. Should this be anticipated as inevitable and somehow accommodated?

I asked openly in the discord, but would #2 work if a data model exists for the document? @In3luki was under the impression that it will not because the source data will be altered by the data model, and that v12 has not changed in this regard. There was no clarification otherwise in dev-general.

Though we may wish to avoid it in the future, there may be a very strong perceived need for later asynchronous migrations. Should this be anticipated as inevitable and somehow accommodated?

This can only be addressed in core, but one advantage of sync migrations and duplicating the data we're overwriting to make that work is that we don't have to be afraid of future updates to the source data. This thing we did was inherently unsafe and its good that we have to avoid it.
One potential compromise that occurred to me though was flagging an item as "needs refresh". This could skip all later migrations and then asynchronously update the item afterwards. Skipping later migrations would avoid the problem scenario of updating an item to its most recent version, then running a migration that assumes an older version, which is a potential problem of our current structure.


Feature: Matplotlib Dark Mode

Problem
Would be nice to have a dark mode for the plots.
References

https://matplotlib.org/stable/gallery/style_sheets/dark_background.html

Implemented with: a87611f2a3045a4627f5e44ab4edb86a63692caa


Multiple Strategies/Datas works well with a funded account?

Hi,
I'm asking because I'm a non-US resident and need to send 30k to test this ;)
Using multiple datas does work for me with a paper account and the alpaca feed, but it takes quite a well before all datas are live (several minutes for ~10 datas)... Can you work live on a minute timeframe with ~100 datas when you have a funded account + polygon feed?

Hi,
The feeds should work the same way for the live account.
I would go to the slack channels and ask a question there, getting the opinions of many traders that are trading live and might have more insights for you


fix php 8.1 issue. Return type of Zend_Soap_Client_Common::__doRequest($request, $location, $action, $version, $oneWay = false)

fix php 8.1 issue. Return type of Zend_Soap_Client_Common::__doRequest($request, $location, $action, $version, $oneWay = false) should either be compatible with SoapClient::__doRequest(string $request, string $location, string $action, int $version, bool $oneWay = false): ?string, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Can you change the comment block to have $oneWay as just a bool, not a bool|int. Just to match https://www.php.net/manual/en/class.soapclient.php

@Shardj Sure, thx for the hint. I've fixed the commit.

is this really necessary, the error said to add #[\ReturnTypeWillChange], but that's already present in master

necessary? no
we can leave it as it is for backwards compatibility and close the PR.


Images are displayed small

I know that the user agent is dynamically, but the images are displayed in a little box when I want to see the details of the picture.

Thanks for the report. Duplicate of #44.


Correct Projection Issues For CVM-S4.26

Reason:

Original Fortran conversion code by Chen and Lee had bug in it whereby new easting and northing for the top-left-most corner were calculated incorrectly. The easting was changed first and then the new northing was calculated off of the changed easting not the original easting. Therefore the northing was off.
Original lat, lon to UTM code from Chen and Lee included a simplification in the project code borrowed from John Snyder, Map Projections Used By The USGS (https://pubs.usgs.gov/bul/1532/report.pdf), which listed a finite set of terms as a proxy for the infinite series. This led to errors in the UTM coordinates on the order of 70m. This is a systemic offset mostly, although the offset grows as you get further and further away from the equator. So the offset may be 70m at 40 latitude but only 60m at 30 latitude, e.g..
Science side: be accurate with projections; software: remove Fortran dependency

Steps to Fix:

Converted Po and En-Jui’s FD_GRID Fortran script into Python
Script is located at ucvm/bin/internal/_ucvm_calculate_box_for_inversion
New script uses Proj.4 instead of Po and En-Jui’s SPECFEM Fortran code

Findings:

Some slight changes to corners both in UTM and corresponding lat/lorn
Off less than 100m in both X and Y
Recommended removing Fortran code, using Proj.4

Decisions Made:

Switched buggy Fortran code to Proj.4 DG Yes CG Not Verified
Adjusted four corners for CVM-S4.26 using _ucvm_calculate_box_for_inversion

Action Items:

Ensure that all future tomography inversions use Proj.4, not the old Fortran code

_ucvm_calculate_box_for_inversion script is finished.
TL;DR see http://hypocenter.usc.edu/research/ucvm/gitissues/github_13.tar.gz for the grid points and output.
I have run it with both the CVM-S4.26 and CCA input files. The grids that I get back appear to be good. The script:

Calculates the four corners according to PC, EL method but with Proj.4 not Fortran code
Verifies the distances of the BL, BR and TL, TR side are equal, and ensures that the distances between the BL, TL and BR, TR sides are equal
Verifies that the rotation angles of the BL, BR point and TL, BL (the sides) match so that way it is a perfect rectangle
Generates the grid using Proj.4 using a simple point rotation and adding it to the origin
Verifies that the four corners MATCH with the four corners that were calculated before

I have attached the outputs of running the commands.
Steps to Reproduce:
Execute python3 _ucvm_calculate_box_for_inversion -f CCA06_box.inp to get the CCA box and python3 _ucvm_calculate_box_for_inversion -f CVMS426_box.inp for the CVM-S4.26 box. You will see the calculation output and also the data files included will be generated.

This grid has been sent off to the scientists for use. I am considering this to be closed.

Added in capability for the script to merge the downloaded Mira data with the newly generated grid. The resulting file is X-fast. The final columns are:
X, Y, Z, UTM X, UTM Y, LON, LAT, DEPTH, VP, VS, DENSITY
This represents the final "master model" for CVM-S4.26.

This file has now been uploaded to Mira at /gpfs/mira-home/davidgil/cvms426_final_model.txt.
To regenerate this file, download the original S4.26 tomographic slices from Mira locally (e.g. to ~/Tomography). Then run the command:
_ucvm_calculate_box_for_inversion -f CVMS426_box.inp -d ~/Tomography
This will output a file called generated_grid.txt which matches the final model.
Commit f8aa5a4f91953c67188847e329a7220c0c1cf479 added this capability in.
I am considering this ticket closed again.


Update query button label

Rename the button
Update the UI docs

First commit is the result of running mvn clean install -DskipTests on my local.


Add 'Potential fix' docs for easy errors in WebApp

In the ideal state for each error occurring during an ORT run we should offer documentation how the ORT user can potentially resolve them.  Obviously we can not offer docs for every potential error but it should be doable for some of the easy ones like "No source URL".
Porposal: start adding 'Potential fix' docs starting with errors that are caused by broken OSS metadata and then expand from there.

This feature was implemented by allowing setting a howToFix MarkDown text for policy rules.


QRcode Activity: Dropdown button UI enhancement

Hey @llaske
I have fixed the dropdown UI button issue in QRcode Activity please review it .
Refer issue:https://github.com/llaske/sugarizer/issues/1253
Before

After

Okay. Thanks


Fixing Renovate to update only within LTS

Renovate is raising MR for non-LTS node images https://github.com/juancarlosjr97/release-it-containerized/pull/32

Fixed https://github.com/juancarlosjr97/release-it-containerized/commit/00d4d06549e6decfe047617f708c737068d82430 and MR updated https://github.com/juancarlosjr97/release-it-containerized/pull/32


add gateway for admeme

About the PR
closes #17579
adds gateway and gateway [destination], the former you map the latter you set up in VV then check enabled and it can used
see video for usage
it no longer contains linq but i spent a min making this so not putting it to waste

i dont plan to touch anything exped related in this
TODO:

[X] add cool sound
[X] show how long the portal will be open for
[X] actually make portal work
[ ] fix funny clipping draw order thing

Media
https://github.com/space-wizards/space-station-14/assets/39013340/d5b94baa-807a-496a-82e8-ea048ec0f75f

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

add: Added the gateway, currently for admins to teleport you to funny places.

hypothetical code for exped would be
var uid = Spawn("GatewayDestination");
var dest = Comp<GatewayDestinationComponent>(uid);
dest.Name = planetName;
dest.OpenTime = mission.Time;
dest.Cooldown = failCooldown; // change it to success cooldown when mission is completed

@DogZeroX does this need anything else

Don't think so?

@metalgearsloth for future whats the point of adding TimeOffsetSerialializer when serializing times makes mapping funnies

Hi, we've been making an experimental map built on your gate.
https://github.com/space-syndicate/space-station-14/pull/1408
Everything worked fine, but after the last update, the portals work a little broken: Now it is necessary that any of the players first download and see the destination portal, and then lose sight of the sending portal. Only after that, the portal can be used for its intended purpose.
Unfortunately, our card cannot function well in this state. Can you find out what the problem is?

@metalgearsloth for future whats the point of adding TimeOffsetSerialializer when serializing times makes mapping funnies

If the game is saved and loaded it needs to be able to resume as is and the only alternative is keeping an accumulator around tracking time every tick. This is fine sometimes but if you're networking then it wastes significant bandwidth having to send it every tick (this is how gun code avoids having an update loop entirely on the server).

Unfortunately, our card cannot function well in this state. Can you find out what the problem is?

Net entities somewhere.

Net entities somewhere.

Unfortunately, this does not explain to me how to fix this problem. Can you explain or in more detail, or leave a link where it is explained what kind of Net entity, and what to do with them?

ill look at it in a bit using net entities instead of entityuids should fix the needing to see it issue


unmounting a mapview in motion crashes the app

Putting a mapview in a navigator and popping it while the mapview animates leads to this:
* thread #1: tid = 0x274690, 0x3375df46 libobjc.A.dylib`objc_msgSend + 6, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0xd000000c)
    frame #0: 0x3375df46 libobjc.A.dylib`objc_msgSend + 6
    frame #1: 0x26842082 MapKit`-[MKMapView mapLayer:didChangeRegionAnimated:] + 98
    frame #2: 0x308e6332 VectorKit`-[VKMapCameraController stopPanningAtPoint:] + 118
    frame #3: 0x2686b71a MapKit`__36-[MKMapGestureController handlePan:]_block_invoke193 + 274
    frame #4: 0x28954fa4 UIKit`__47+[_UIDynamicAnimation _updateAnimations:timer:]_block_invoke + 28
    frame #5: 0x24fc5fde CoreFoundation`__53-[__NSArrayM enumerateObjectsWithOptions:usingBlock:]_block_invoke + 86
    frame #6: 0x24fc5f08 CoreFoundation`-[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 248
    frame #7: 0x289543f8 UIKit`+[_UIDynamicAnimation _updateAnimations:timer:] + 80
    frame #8: 0x281827da QuartzCore`CA::Display::DisplayLinkItem::dispatch() + 98
    frame #9: 0x28182642 QuartzCore`CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) + 366
    frame #10: 0x2d089c06 IOMobileFramebuffer`IOMobileFramebufferVsyncNotifyFunc + 90
    frame #11: 0x2601f000 IOKit`IODispatchCalloutFromCFMessage + 256
    frame #12: 0x2505602c CoreFoundation`__CFMachPortPerform + 132
    frame #13: 0x250665aa CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 34
    frame #14: 0x25066546 CoreFoundation`__CFRunLoopDoSource1 + 346
    frame #15: 0x25064b48 CoreFoundation`__CFRunLoopRun + 1608
    frame #16: 0x24fb0f30 CoreFoundation`CFRunLoopRunSpecific + 476
    frame #17: 0x24fb0d42 CoreFoundation`CFRunLoopRunInMode + 106
    frame #18: 0x2ca8b200 GraphicsServices`GSEventRunModal + 136
    frame #19: 0x28782878 UIKit`UIApplicationMain + 1440
  * frame #20: 0x0004b33c kietsy`main(argc=1, argv=0x00311afc) + 108 at main.m:16

Could you test this on latest iOS and let us know if this is still occurring?

@facebook-github-bot label Needs More Information

@facebook-github-bot no-reply

I  have the same problem in the React Native 0.28

@shawnXiao I didn't. I don't have a react-native project at the moment. If it does impair you at the moment you could provide a minimal example and I'm sure this can be reopened.

The method to reproduce the bug is quite simple at iOS8, just put a mapview in a navigator and popping it while the mapview animates and then go to the mapview again.

@shawnXiao I meant a Short, Self Contained, Correct (Compilable), Example. Just a repo with a freshly-generated, up-to-date app with only the navigator and mapview, and some instruction. So that someone looking into this just needs to clone the repo npm i && npm start. 🙂


Design for the front end

Wireframing and prototype for the front end with the following pages

[x] Landing page
[x] Login/Register
[x] User's dashboard
[x] Bill creation flow
[x] Final bill or print/share bill page
[ ] History of all bills
[ ] Edit bills flow

Current Status

Landing page
Login/Register
User's dashboard
Bill creation flow
Final bill or print/share bill page
History of all bills
Edit bills flow
Bill PDF template

 Design BE


Use flickity to display panoramas

TIL that a component called a carousel exists and there are libraries for it. This uses one of said libraries, "Flickity" to (hopefully) make the panoramas display a little better.


added check for libpython_version#m.dylib present in some virtual env…

…ironments

Sweet, thanks for the PR :)


[RFC][data-migration] selectableRequirementChoices -> optOut

Summary
This PR implements the data migration script that will migrate the selectableRequirementChoices into the new format where all the user choices are unified under the concept of override: opt-in and opt-out.
We originally think everything can be categorized into opt-out and opt-in, but the running result shown above indicates that we might need 3, which I propose below:
type OverrideChoiceForCourse = {
  /* unchanged */
  optOut: Requirement[];
  /**
   * same as opt-in as we discussed in previous meetings.
   * It's for attaching completely unknown courses to a requirement
   * (e.g. opt-in CS 2112 for history requirement)
   */
  arbitraryOptIn: Record<Requirement, slot[]>
  /* See discussion below */
  acknowledgedCheckerWarningOptIn: Requirement[];
}

acknowledgedCheckerWarningOptIn is for requirements that have a checker warning. e.g. tech elective in CS. In the old flow, they are considered more like self-checks, and never picked as default choice. For example, when you add CS 4120, the following thing will happen in the old system:

CS elective chosen as default choice
Allow you to choose tech elective, advisor approved elective, etc (those with broad, imprecise checker) as alternative choice, but never selected by default
opt-in not implemented yet, so that's irrelevant

For the new system and the 3 category thing I proposed, the default choice would be:
choice = { optOut: [], arbitraryOptIn: {}, acknowledgedCheckerWarningOptIn: null };

which corresponds to CS 4120 being connected to CS elective only and not to any broad requirements. It fits the general philosophy of the new flow: during add time, we don't make complicated computation to decide eligibility, and the default choice should be safe, non-confusing.
It's not only satisfying philosophically, but it's also necessary. It's important to distinguish between arbitrary opt-in and acknowledgedCheckerWarningOptIn, since the former is a complete escape hatch and the system knows nothing about where it should be without user intervention, the latter we do exactly know which slot it should go to (we are just unsure whether it can be safely assigned to a requirement)

[x] Dry-run proof of concept
[ ] Dry-run consolidated
[ ] Runnable on staging site
[ ] Run on staging site
[ ] Run on production site

Test Plan
TODO
Notes
Once the data migration script is completed, it should not be run and deployed to production immediately. We need a second part of this migration project, which makes the frontend saves data to both selectableRequirementChoices and optOut while still making selectableRequirementChoices the source of truth, so that we can safely deploy this to prod and the prod will start consistency generating data of the new format. Then in a future deploy to prod when we are ready, we can switch to use the new format to be the source of truth.

@hahnbeelee

And when you say that optOut is the same as it is in the system are you referring to Ben's unused optOut code?

No, I'm referring to the discussion when we first established that all user choices are modeled as opt-in/opt-out.

Not sure if you need to fix this here but this type is deprecated. (in requirement-graph-builder-from-user-data)

I intentionally mark is as deprecated. The replacement type is FirestoreCourseOptInOptOutChoices. Full removal of that deprecated type is pending on the migration.

I feel we can rename arbitraryOptIn to optIn because the existence of acknowledgedCheckerWarningOptIn kinda implies that the other optIn is arbitrary.

I feel we can rename arbitraryOptIn to optIn because the existence of acknowledgedCheckerWarningOptIn kinda implies that the other optIn is arbitrary.

This is still pending whether we go with default opt-in or opt-out. If we default by opt-out, there will be another kind of opt-in lol.

How do the updates from #522 affect this?

How do the updates from #522 affect this PR?

No change for now. The two graph approach will only be implemented after we have the design. Currently it's ok with one graph because we know existing data does not have any constraint violations.

Planning to merge once the release PR is merged.


Redmi Android 9 java.io.FileNotFoundException: /data/system/theme_config/theme_compatibility.xm

Hello. i use ubuntu 20.04
What i got:
1 apt install scrcpy
2 root@vmi523325:~# adb devices
List of devices attached
0c53a0b59906	device
3 root@vmi523325:~# scrcpy
INFO: scrcpy 1.12.1 https://github.com/Genymobile/scrcpy
/usr/share/scrcpy/scrcpy-server: 1 file pushed. 0.1 MB/s (24773 bytes in 0.221s)
java.io.FileNotFoundException: /data/system/theme_config/theme_compatibility.xml (No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:231)
at java.io.FileInputStream.(FileInputStream.java:165)
at java.io.FileInputStream.(FileInputStream.java:112)
at java.io.FileReader.(FileReader.java:58)
at miui.content.res.ThemeCompatibilityLoader.getVersion(ThemeCompatibilityLoader.java:108)
at miui.content.res.ThemeCompatibilityLoader.getConfigDocumentTree(ThemeCompatibilityLoader.java:126)
at miui.content.res.ThemeCompatibilityLoader.loadConfig(ThemeCompatibilityLoader.java:59)
at miui.content.res.ThemeCompatibility.(ThemeCompatibility.java:31)
at miui.content.res.ThemeCompatibility.isThemeEnabled(ThemeCompatibility.java:111)
at android.content.res.MiuiResourcesImpl.(MiuiResourcesImpl.java:40)
at android.content.res.Resources.(Resources.java:267)
at android.content.res.MiuiResources.(MiuiResources.java:49)
at android.content.res.Resources.getSystem(Resources.java:190)
at android.app.LoadedApk.(LoadedApk.java:211)
at android.app.ContextImpl.createSystemContext(ContextImpl.java:2331)
at android.app.ActivityThread.getSystemContext(ActivityThread.java:2190)
at java.lang.reflect.Method.invoke(Native Method)
at com.genymobile.scrcpy.Workarounds.fillAppInfo(Workarounds.java:66)
at com.genymobile.scrcpy.ScreenEncoder.streamScreen(ScreenEncoder.java:56)
at com.genymobile.scrcpy.Server.scrcpy(Server.java:34)
at com.genymobile.scrcpy.Server.main(Server.java:163)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:388)
any tips? thanks!

That error message is not a problem, you can ignore it. It has been silented in later versions.

That error message is not a problem, you can ignore it. It has been silented in later versions.

thank you for the answer. I am trying to run scrpy first time. and this maybe is not all.
wnen i write
root@vmi523325:~# scrcpy
INFO: scrcpy 1.12.1 https://github.com/Genymobile/scrcpy
/usr/share/scrcpy/scrcpy-server: 1 file pushed. 0.1 MB/s (24773 bytes in 0.221s)
i don't see any windows apearing, My terminal window just does something in background, no any error messages, no loading indicator and etc. Maybe i run scrcopy wrong? Looks like this hangups. So question is: what i should see after this command:
root@vmi523325:~# scrcpy
thanks

Do not run scrcpy as root
If it hangs here, please post the logcat

adb logcat -c  # clean
scrcpy  # then kill
adb logcat -d > logcat.txt

what was the problem:
error: XDG_RUNTIME_DIR not set in the environment.
CRITICAL: Could not initialize SDL: No available video device
Looks like i cannot use this tool on my VPS server :\ .. or it still possible?