enable custom headers for bitbucketserver integration

Custom headers can be added in app-config.yaml for the bitbucketserver integration.
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[X] A changeset describing the change and affected packages. (more info)
[X] Added or updated documentation
[X] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[X] All your commits have a Signed-off-by line in the message. (more info)

closes https://github.com/backstage/backstage/issues/11233

I miss a bit the context here on what you want to achieve with these additional headers, but I assume there are relevant for authorization. Also, I'm a bit more into the Bitbucket Cloud part.
But to share some thoughts:
There were already client implementations for Bitbucket Cloud and Bitbucket Server as part of the related catalog-backend-module-bitbucket plugin.
But there are quite a few places with hardcoded endpoints/call, etc. at other places, too, incl. integration (to share it with other modules, not needed for itself), catalog import, scaffolder (no support for Bitbucket Server yet I believe), etc.
For Bitbucket Cloud, I've created a reusable client library to interact with Bitbucket Cloud. PR pending.
I plan to move more of these calls spread across the modules into this library. The "authentication header" part of the integration will be removed eventually then as this is supposed to be handled within the client library.
Also, it can be used later to add support for managing rate limits, etc. This does not really work well if the interaction with a 3rd party is spread everywhere.

@goober as you plan to work the entity provider for Bitbucket Server, maybe you can share some thoughts, too

I miss a bit the context here on what you want to achieve with these additional headers, but I assume there are relevant for authorization. Also, I'm a bit more into the Bitbucket Cloud part.

The motivation here is that my organization requires additional request headers (i.e. cf-access-token-id and cf-access-token-secret) to reach bitbucket in a "zero-trust" setting. These headers are processed by a kubernetes ingress controller to check if a request is authorized.

I miss a bit the context here on what you want to achieve with these additional headers, but I assume there are relevant for authorization.

Yep, it is for authorization! There's more context on the linked issue.

@goober as you plan to work the entity provider for Bitbucket Server, maybe you can share some thoughts, too

I can see a use case for adding additional headers to be sent to the Bitbucket Server for authorization. However, it can be good to know that there could be more places where this needs to be implemented as @pjungermann mention.

I see that fetchApi is already part of plugin-core-api, are there plans to standardize fetchApi usage across all plugins?

With the backend system work we will most likely introduce a fetchApi that is scoped to plugins, and perhaps scoped per request so that we can automatically decorate any downstream requests with the user information etc all for free.

But it's still a work in progress right now


feat: Updates acceptance tests to use the Mobility Database Catalogs

Summary:
Closes #1143
This PR update the acceptance tests so that they use the Mobility Database Catalogs instead of the outdated Wikibase instance.
Expected behavior:
Acceptance tests should be run on the sources included in the Mobility Database Catalogs. Since the catalogs can be downloaded as a CSV file, acceptance tests should be much faster when fetching the URLs (no more waiting on the Wikibase API!). Also, the data is in greater quantity and more accurate.
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradle test to make sure you didn't break anything
[x] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
[x] Linked all relevant issues
[ ] ~Include screenshot(s) showing how this pull request works and fixes the issue(s)~

Meta comment: I don't think I'd ever looked too closely at the acceptance_test.yml script before.  This thing is a beast!   How many urls are in the old database?  I count 1300+ in the new database.  Is that an increase?  I guess the project doesn't get pull requests /too/ often, but I hadn't realized just how many feeds were being downloaded with each update to a PR.

Meta comment: I don't think I'd ever looked too closely at the acceptance_test.yml script before. This thing is a beast! How many urls are in the old database? I count 1300+ in the new database. Is that an increase? I guess the project doesn't get pull requests /too/ often, but I hadn't realized just how many feeds were being downloaded with each update to a PR.

We have 1332 GTFS Schedule sources in the Mobility Database catalogs. Previously, 1117 on the Wikibase instance (more actually, but we noticed that many were duplicates). So we will run acceptance tests on 215 additional sources.
A lot of downloads every time a PR is updated, indeed! It is possible to skip the acceptance tests by using the [acceptance test skip] string in a commit, so that the tests are only run when necessary.


Add @SafeVarargs to ExternalPluginManager.loadBuiltin

Fixes warning "Unchecked generics array creation for varargs parameter" on
loadBuiltin. This warning is trying to prevent a RuntimeException which
happens iff the varargs are modified in a particular way. Varargs are not
modified, which is guaranteed by PluginManager.loadPlugins using a Stream.
Change loadPlugins to take a Stream of Plugins. Saves a few allocations.
Allow loading of plugins that are not direct subclasses of Plugin, but
subclasses of subclasses of Plugin, etc. (fix in loadPlugins) and add a
test case that this works
Fix an iterator invalidation bug in PluginManager.topologicalSort.
Graph.sucessors is an iterator; removing nodes while iterating throws
a concurrentModificationException. Fix: add an allocation.
Fill out existing javadocs for topologicalSort

This is my first PR here. I originally imagined this PR as being simple, but went down the rabbit hole on something the Runelite devs probably don't care much about. I won't be upset if it gets closed, but I'd appreciate some explanation of what I did right/wrong here.

I don't think I see a good reason to allow Plugin subclassing, it seems like it has no advantage but just opens a can of worms? And also a construct like
abstract class BasePlugin extends Plugin{}
@PluginDescriptor(...)
class ChildPlugin extends BasePlugin{}

would trip the "Class is a plugin but has no plugin descriptor" warning.

Hm... I can't think of a good reason to do what you wrote in that example. Maybe a plugin hub plugin could extend a Runelite plugin to add some features to it. Or one author could create two versions of essentially the same plugin that extend a base plugin class also written by them. I don't perceive the same can of worms you do. Regardless, say the word and I'll revert that, but if I do, the warning for trying to load TestPluginGrandChild (as I called it in the test case I added) before this PR would have said "is not a plugin", and it should be made to say "Must extend Plugin directly"

would trip the "Class is a plugin but has no plugin descriptor" warning.

It does not trigger that warning. I didn't think it would since pluginClass.getAnnotation(PluginDescriptor.class); is based on its runtime class, but I also tested it.

It has to trip it because
		List<Class<?>> plugins = classPath.getTopLevelClassesRecursive(PLUGIN_PACKAGE).stream()
			.map(ClassInfo::load)
			.collect(Collectors.toList());

is all classes in the plugins package, and both classes are in the package.
But regardless, what is it you are trying to do that you think is best solved by having subclassing of plugins?

Nothing I am doing, nor have plans to do requires extending a class which extends Plugin. I don't need that feature, it seemed like an oversight to not allow it, but I may have been mistaken. I don't know which classes you are referring to when you say "both classes are in the package". Seems like BasePlugin and ChildPlugin I thought they were examples and do not exist in the Runelite project. And if they did exist, they could exist in a plugin hub plugin, which would not have that problem.

I made a change so as to load only direct children of Plugin in loadCorePlugins. Adam, you don't seem sold on this sub-subclassing of Plugin business, so I'm considering modifying this PR to instead issue a more specific diagnostic when trying to load a sub-subclass of plugin, but still not allow/load it. If this PR is scrapped, the change to the topologicalSort method is pretty important - iterator invalidation causes a crash if the code is slightly modified, but does not cause a crash as is, obviously.

#14668 fixed the ConcurrentModificationException bug in topologicalSort and the rest of this PR isn't worth the trouble.


Coding Language support

hello, i would like to use in python using Pycharm IDE. Im not sure if that is already possible but if not than please implement it ;D

Hi there, I've tried to create a Intellij plugin (asumming Pycharm is similar) and haven't figure it out yet.
I'm having a few things to focus on so can't working Intellij at the moment. If you like to work on it, let me know

Close due to inactivity


Trouble installing xgboost on OSX 10.14

Hi there,
I feel like I've tried everything under the sun to install xgboost on my mac (mohave), but I'm still running into dead ends.
Some things I've tried:
https://github.com/dmlc/xgboost/issues/4477
When I run the step
$ cmake ..
I get this error:
`-- The CXX compiler identification is GNU 5.5.0
-- The C compiler identification is GNU 5.5.0
-- Checking whether CXX compiler has -isysroot
-- Checking whether CXX compiler has -isysroot - yes
-- Checking whether CXX compiler supports OSX deployment target flag
-- Checking whether CXX compiler supports OSX deployment target flag - yes
-- Check for working CXX compiler: /usr/local/bin/g++-5
-- Check for working CXX compiler: /usr/local/bin/g++-5 -- broken
CMake Error at /usr/local/Cellar/cmake/3.15.4/share/cmake/Modules/CMakeTestCXXCompiler.cmake:53 (message):
The C++ compiler
"/usr/local/bin/g++-5"

is not able to compile a simple test program.
It fails with the following output:
Change Dir: /Users/camp426/xgboost/build/CMakeFiles/CMakeTmp

Run Build Command(s):/Users/camp426/anaconda3/bin/make cmTC_55296/fast && /Users/camp426/anaconda3/bin/make -f CMakeFiles/cmTC_55296.dir/build.make CMakeFiles/cmTC_55296.dir/build
make[1]: Entering directory '/Users/camp426/xgboost/build/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_55296.dir/testCXXCompiler.cxx.o
/usr/local/bin/g++-5    -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O2 -pipe -stdlib=libc++ -fvisibility-inlines-hidden -std=c++14 -fmessage-length=0  -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk -mmacosx-version-min=10.14   -o CMakeFiles/cmTC_55296.dir/testCXXCompiler.cxx.o -c /Users/camp426/xgboost/build/CMakeFiles/CMakeTmp/testCXXCompiler.cxx
g++-5: error: unrecognized command line option '-stdlib=libc++'
make[1]: *** [CMakeFiles/cmTC_55296.dir/build.make:66: CMakeFiles/cmTC_55296.dir/testCXXCompiler.cxx.o] Error 1
make[1]: Leaving directory '/Users/camp426/xgboost/build/CMakeFiles/CMakeTmp'
make: *** [Makefile:121: cmTC_55296/fast] Error 2

CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:2 (project)
-- Configuring incomplete, errors occurred!
See also "/Users/camp426/xgboost/build/CMakeFiles/CMakeOutput.log".
See also "/Users/camp426/xgboost/build/CMakeFiles/CMakeError.log".`
I have homebrew, I've updated homebrew, I've tried installing xgboost (using both pip and pip3) with gcc5, gcc8, and gcc9.2 (newest version), none work.  I get the same error:
Command "python setup.py egg_info" failed with error code 1
Which I see by the multiple issues that I found googling that this is a known issue.
I'm in dead-end land.  Help please.

I'm not an OSX user. @hcho3 could you help taking a look when you are back?
Community help is very much wanted.  We currently run osx test on Travis but it doesn't seem the tests can cover all cases.

Try brew install xgboost. The disadvantage is that multithreading will not be supported.

@bearcub Also, make sure that you installed the Command Line Tools (CLT) for Xcode.

@hcho3 thanks for hiding the rabble rouser.    It just looks like it downloaded it, though?
(base) WE37632:~ camp426$ brew install xgboost ==> Downloading https://homebrew.bintray.com/bottles/xgboost-0.90.mojave.bottle.ta ==> Downloading from https://akamai.bintray.com/28/280fe55391f3b02fd7424afbcda34bb ######################################################################## 100.0% ==> Pouring xgboost-0.90.mojave.bottle.tar.gz 🍺  /usr/local/Cellar/xgboost/0.90: 121 files, 6.9MB
how do I test if it's working?  import xgboost in python doesn't work yet.

@bearcub It looks like brew install xgboost only installs libxgboost.dylib. The Python library will need to be installed separately:
git clone --recursive https://github.com/dmlc/xgboost -b release_0.90
cd xgboost
mkdir lib
cd lib
ln -s /usr/local/Cellar/xgboost/0.90/lib/libxgboost.dylib ./libxgboost.dylib
cd ../python-package
python3 setup.py install

After these commands, you should be able to run import xgboost.

derp. it werks now.
Thank you @hcho3 !!!!!

@bearcub No problem. Note that your XGBoost installation will only use a single CPU core (no multithreading) because issues described in #4477. If you need to use multiple CPU cores (for faster training), consider using Conda.

This solution is not always working. In my case, I just download user argument of Xcode. I think this was happening because a new version of Xcode was downloaded and the new agreement was not accepted. Right now it's working properly.

Now the latest XGBoost release (version 1.1.0) comes with a pre-built Python wheel for Mac OSX. Simply run
pip install xgboost==1.1.0

and it will install quickly. No need to worry about build failing, because we already did the build for you.

I seem to be running into this old issue. When calling pip install xgboost the build is failing with:
...
      copying xgboost/LICENSE -> build/temp.macosx-11.0-arm64-cpython-39/xgboost
      INFO:XGBoost build_ext:Building from source. /private/var/folders/ky/bqjn_gxn1xv0cn_8q5xvp3q40000gn/T/pip-install-z0v7hxaa/lib/libxgboost.dylib
      INFO:XGBoost build_ext:Run CMake command: ['cmake', 'xgboost', '-GUnix Makefiles', '-DUSE_OPENMP=1', '-DUSE_CUDA=0', '-DUSE_NCCL=0', '-DBUILD_WITH_SHARED_NCCL=0', '-DHIDE_CXX_SYMBOLS=1', '-DUSE_HDFS=0', '-DUSE_AZURE=0', '-DUSE_S3=0', '-DPLUGIN_DENSE_PARSER=0']
      error: [Errno 2] No such file or directory: 'cmake'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> xgboost

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

I have tried specifying specific versions (1.6.1, 1.6.0, 1.5.0) but those throw the same error.


Kroxylicious Release 2023-03-26

Release API version v0.1.0
Release Framework version v0.1.0

Type of change
Select the type of your PR

Release

Description
Please describe your pull request
Additional Context
Why are you making this pull request?

replaced by  https://github.com/kroxylicious/kroxylicious/pull/230


CC Task must using Rust coding?

Hi, thanks for your nice project. I have a question about the program languages, so the CC task must using Rust as the program language? if we want to follow this project

Hi Arrowflyt,
The short answer is: not necessarily.
You may write a CC task in another language and link it with Rust using FFI. However, this method fails the verification for Rust code and may require other verification methods.


Issues with the collate_sbs_results part of collate_results

collate_results uses the cached results table by default. This is good because it has preserved mutational signature data that has since gone away (namely the current mutational signature table omits SBS9 which has to be the worst one to omit from GAMBL).
However the sbs_manipulation argument effectively does nothing with the cached results because only SBS1, 8, and 9 have scaled results cached, so all the other mutational signatures have only original data preserved. Also I think expected behavior is that if the user wants scaled data returned, the function should ONLY return scaled data, not scaled + unscaled data in cryptically named columns.

This is a migration of the issue #113 from the parent repo


Implement/overhaul the landing page

The landing page will be the main point of communication regarding this initiative to help fight COVID19 through social distancing.
It could comprise of:

A message which will warm the hearts of everyone who reads it.
Brilliant visual effects.
A clean and simple UI (which leads to the start game page.
Marketing information
Media information
Legal links

Just noticed that the animations could be smoother.

When a user clicks the get started button. They navigate to the start game page.


Cleans up docs/man/Dockerfile.5.md

Fixes some improper usage of ** instead of backticks
Re-arranged some things for readability.

LGTM - @fredlf @jamtur01

ping @lk4d4 is this not docs-review? you removed the label, I think it is, but @tiborvass would know best

There a lot of variance in formatting here - some Dockerfile instructions are wrapped in *, others are not. Use of  versus **command**. I think some consistency is needed.

Formatting for commands is still not consistent throughout, but his is an improvement, so LGTM.

PTAL

Found a couple more, but LGTM still.

Updated with fred's notes.

Still a handful of inconsistently formatted Dockerfile, but we have a separate ticket to deal with this issue site-wide, so I'm going to merge this. Thanks @cpuguy83 !


primary-text-color in view theme not always used

When using the theme option in a Lovelace view, some cards (such as weather-forecast) appear to pick up text colour from primary-text-color in the default theme and not the theme assigned to the view. For example:
views:

title: Weather
id: weather
icon: mdi:weather-cloudy
theme: TransparentTheme
cards:

type: weather-forecast
entity: weather.dark_sky

where the TransparentTheme theme includes:
primary-text-color: '#f2f2f2'
still renders text as black, unless the same theme is selected as the current global theme.

/move home-assistant-polymer


Define type as return value of a function

I want to define a type as being the return value of a function.
the intellisense is able to accuratly determine the return value of a function, but I cannot the returns value in other jsdoc definition.
by exemple, I would like to be able to do :
/**
    the returns value is implicit as it is complexe and I don't want
     to rewrite it in jsdoc.
*/
function createSomething() {
   //do thing
   //return something
}

const something = createSomething()

/**
    I would like to say that 'something' must be the same as
    what is returned by "createSomething"
*/
function needSomething(something) {
     //the type of 'something' is lost.
}

I think this is similar to issue #1244 and #1086.
I also need to be able to get the return value of the return value of a function, for curried function.
thank a lot

the returns value is implicit as it is complexe and I don't want to rewrite it in jsdoc.

Why do you ask here, then? This tool's whole purpose is to create offline (e.g. HTML) documentation from your inline JSDoc comments.

I would like to say that 'something' must be the same as what is returned by "createSomething"

Create a type then. It can be a dummy type, just a name, and document createSomething's return value as well as needSomething's parameter.

I agree that this issue is not related to the JSDoc tool.


Xorg driver segfaults Xorg

When I try to use the Xorg driver with xrdp I get the following stacktrace on connection:
Oct 18 14:03:27 saiph systemd-coredump[18616]: Process 18541 (Xorg) of user 1000 dumped core.

                                               Stack trace of thread 18541:
                                               #0  0x00007f1bc564d04f raise (libc.so.6)
                                               #1  0x00007f1bc564e47a abort (libc.so.6)
                                               #2  0x000000000059f40e OsAbort (Xorg)
                                               #3  0x000000000047b25c ddxGiveUp (Xorg)
                                               #4  0x00000000005a5072 n/a (Xorg)
                                               #5  0x00000000005a5e7d FatalError (Xorg)
                                               #6  0x000000000059cc8e n/a (Xorg)
                                               #7  0x00007f1bc564d0b0 __restore_rt (libc.so.6)
                                               #8  0x00007f1bc0959d15 rdpClientConCheck (libxorgxrdp.so)
                                               #9  0x000000000043b2dd WakeupHandler (Xorg)
                                               #10 0x00000000005954f9 WaitForSomething (Xorg)
                                               #11 0x000000000043656e n/a (Xorg)
                                               #12 0x000000000043a763 n/a (Xorg)
                                               #13 0x00007f1bc563a291 __libc_start_main (libc.so.6)
                                               #14 0x00000000004246e9 _start (Xorg)

                                               Stack trace of thread 18546:
                                               #0  0x00007f1bc540a10f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                               #1  0x00007f1bbf8bc583 n/a (swrast_dri.so)
                                               #2  0x00007f1bbf8bc3e7 n/a (swrast_dri.so)
                                               #3  0x00007f1bc5404454 start_thread (libpthread.so.0)
                                               #4  0x00007f1bc57027df __clone (libc.so.6)

                                               Stack trace of thread 18551:
                                               #0  0x00007f1bc540a10f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                               #1  0x00007f1bbf8bc583 n/a (swrast_dri.so)
                                               #2  0x00007f1bbf8bc3e7 n/a (swrast_dri.so)
                                               #3  0x00007f1bc5404454 start_thread (libpthread.so.0)
                                               #4  0x00007f1bc57027df __clone (libc.so.6)

                                               Stack trace of thread 18550:
                                               #0  0x00007f1bc540a10f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                               #1  0x00007f1bbf8bc583 n/a (swrast_dri.so)
                                               #2  0x00007f1bbf8bc3e7 n/a (swrast_dri.so)
                                               #3  0x00007f1bc5404454 start_thread (libpthread.so.0)
                                               #4  0x00007f1bc57027df __clone (libc.so.6)

                                               Stack trace of thread 18549:
                                               #0  0x00007f1bc540a10f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                               #1  0x00007f1bbf8bc583 n/a (swrast_dri.so)
                                               #2  0x00007f1bbf8bc3e7 n/a (swrast_dri.so)
                                               #3  0x00007f1bc5404454 start_thread (libpthread.so.0)
                                               #4  0x00007f1bc57027df __clone (libc.so.6)

                                               Stack trace of thread 18548:
                                               #0  0x00007f1bc540a10f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                               #1  0x00007f1bbf8bc583 n/a (swrast_dri.so)
                                               #2  0x00007f1bbf8bc3e7 n/a (swrast_dri.so)
                                               #3  0x00007f1bc5404454 start_thread (libpthread.so.0)
                                               #4  0x00007f1bc57027df __clone (libc.so.6)

                                               Stack trace of thread 18547:
                                               #0  0x00007f1bc540a10f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                               #1  0x00007f1bbf8bc583 n/a (swrast_dri.so)
                                               #2  0x00007f1bbf8bc3e7 n/a (swrast_dri.so)
                                               #3  0x00007f1bc5404454 start_thread (libpthread.so.0)
                                               #4  0x00007f1bc57027df __clone (libc.so.6)

Could I have a configuration setting wrong that causes the rdpClientConCheck to fail?  VNC and X11rdp connections both connect successfully.  So it seems local only to the xorg driver.

Here is the xorg.log output:
[  2089.821]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[  2089.821] X Protocol Version 11, Revision 0
[  2089.821] Build Operating System: Linux 4.5.4-1-ARCH x86_64
[  2089.821] Current Operating System: Linux saiph 4.7.6-1-ARCH #1 SMP PREEMPT Fri Sep 30 19:28:42 CEST 2016 x86_64
[  2089.821] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=06ca6cbb-bbfc-47b3-9481-f82dc4f2250a rw elevator=noop
[  2089.821] Build Date: 19 July 2016  05:54:24PM
[  2089.821]
[  2089.821] Current version of pixman: 0.34.0
[  2089.821] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  2089.821] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2089.821] (++) Log file: "/tmp/xorg.log", Time: Tue Oct 18 14:03:27 2016
[  2089.842] (++) Using config file: "/etc/X11/xrdp/xorg.conf"
[  2089.842] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  2089.842] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2089.868] (==) ServerLayout "X11 Server"
[  2089.868] (**) |-->Screen "Screen (xrdpdev)" (0)
[  2089.868] (**) |   |-->Monitor "Monitor"
[  2089.869] (**) |   |-->Device "Video Card (xrdpdev)"
[  2089.869] (**) |-->Input Device "xrdpMouse"
[  2089.869] (**) |-->Input Device "xrdpKeyboard"
[  2089.869] (**) Option "DontVTSwitch" "on"
[  2089.869] (**) Option "AutoAddDevices" "off"
[  2089.869] (**) Not automatically adding devices
[  2089.869] (==) Automatically enabling devices
[  2089.869] (==) Automatically adding GPU devices
[  2089.869] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  2089.869] (WW) The directory "/usr/X11R6/lib/X11/fonts/misc/" does not exist.
[  2089.869] 	Entry deleted from font path.
[  2089.869] (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
[  2089.869] 	Entry deleted from font path.
[  2089.869] (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
[  2089.869] 	Entry deleted from font path.
[  2089.869] (WW) The directory "/usr/X11R6/lib/X11/fonts/viewtouch" does not exist.
[  2089.869] 	Entry deleted from font path.
[  2089.869] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[  2089.869] 	Entry deleted from font path.
[  2089.869] 	(Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[  2089.869] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[  2089.869] 	Entry deleted from font path.
[  2089.869] 	(Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[  2089.869] (**) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/,
	/usr/share/fonts/OTF/,
	/usr/share/fonts/Type1/
[  2089.869] (==) ModulePath set to "/usr/lib/xorg/modules"
[  2089.869] (II) Loader magic: 0x821d40
[  2089.869] (II) Module ABI versions:
[  2089.869] 	X.Org ANSI C Emulation: 0.4
[  2089.869] 	X.Org Video Driver: 20.0
[  2089.870] 	X.Org XInput driver : 22.1
[  2089.870] 	X.Org Server Extension : 9.0
[  2089.871] (EE) systemd-logind: failed to get session: PID 18541 does not belong to any known session
[  2089.872] (II) xfree86: Adding drm device (/dev/dri/card0)
[  2089.876] (--) PCI:*(0:0:2:0) 1234:1111:1af4:1100 rev 0, Mem @ 0xfd000000/16777216, 0xfebd0000/4096, BIOS @ 0x????????/131072
[  2089.876] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[  2089.876] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[  2089.876] (II) LoadModule: "dbe"
[  2089.876] (II) Module "dbe" already built-in
[  2089.876] (II) LoadModule: "ddc"
[  2089.876] (II) Module "ddc" already built-in
[  2089.876] (II) LoadModule: "extmod"
[  2089.876] (II) Module "extmod" already built-in
[  2089.876] (II) LoadModule: "glx"
[  2089.879] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  2089.896] (II) Module glx: vendor="X.Org Foundation"
[  2089.896] 	compiled for 1.18.4, module version = 1.0.0
[  2089.896] 	ABI class: X.Org Server Extension, version 9.0
[  2089.896] (==) AIGLX enabled
[  2089.896] (II) LoadModule: "int10"
[  2089.896] (II) Loading /usr/lib/xorg/modules/libint10.so
[  2089.908] (II) Module int10: vendor="X.Org Foundation"
[  2089.908] 	compiled for 1.18.4, module version = 1.0.0
[  2089.908] 	ABI class: X.Org Video Driver, version 20.0
[  2089.908] (II) LoadModule: "record"
[  2089.908] (II) Module "record" already built-in
[  2089.908] (II) LoadModule: "vbe"
[  2089.908] (II) Loading /usr/lib/xorg/modules/libvbe.so
[  2089.911] (II) Module vbe: vendor="X.Org Foundation"
[  2089.911] 	compiled for 1.18.4, module version = 1.1.0
[  2089.911] 	ABI class: X.Org Video Driver, version 20.0
[  2089.911] (II) LoadModule: "xorgxrdp"
[  2089.911] (II) Loading /usr/lib/xorg/modules/libxorgxrdp.so
[  2089.911] (II) Module XRDPMOD: vendor="X.Org Foundation"
[  2089.911] 	compiled for 1.18.4, module version = 1.0.0
[  2089.911] 	ABI class: X.Org Video Driver, version 20.0
[  2089.911] xorgxrdpSetup:
[  2089.911] (II) LoadModule: "fb"
[  2089.912] (II) Loading /usr/lib/xorg/modules/libfb.so
[  2089.914] (II) Module fb: vendor="X.Org Foundation"
[  2089.914] 	compiled for 1.18.4, module version = 1.0.0
[  2089.914] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  2089.914] (II) LoadModule: "xrdpdev"
[  2089.914] (II) Loading /usr/lib/xorg/modules/drivers/xrdpdev_drv.so
[  2089.914] (II) Module XRDPDEV: vendor="X.Org Foundation"
[  2089.914] 	compiled for 1.18.4, module version = 1.0.0
[  2089.914] 	ABI class: X.Org Video Driver, version 20.0
[  2089.914] xrdpdevSetup:
[  2089.914] (II) LoadModule: "xrdpmouse"
[  2089.914] (II) Loading /usr/lib/xorg/modules/input/xrdpmouse_drv.so
[  2089.914] (II) Module XRDPMOUSE: vendor="X.Org Foundation"
[  2089.914] 	compiled for 1.18.4, module version = 1.0.0
[  2089.914] 	Module class: X.Org XInput Driver
[  2089.914] 	ABI class: X.Org XInput driver, version 22.1
[  2089.914] rdpmousePlug:
[  2089.914] (II) LoadModule: "xrdpkeyb"
[  2089.915] (II) Loading /usr/lib/xorg/modules/input/xrdpkeyb_drv.so
[  2089.915] (II) Module XRDPKEYB: vendor="X.Org Foundation"
[  2089.915] 	compiled for 1.18.4, module version = 1.0.0
[  2089.915] 	Module class: X.Org XInput Driver
[  2089.915] 	ABI class: X.Org XInput driver, version 22.1
[  2089.915] rdpkeybPlug:
[  2089.915] rdpIdentify:
[  2089.915] (II) XRDPDEV: driver for xrdp: XRDPDEV
[  2089.915] rdpDriverFunc: op 10
[  2089.915] (WW) Falling back to old probe method for XRDPDEV
[  2089.915] rdpProbe:
[  2089.915] (II) Loading sub module "fb"
[  2089.915] (II) LoadModule: "fb"
[  2089.915] (II) Loading /usr/lib/xorg/modules/libfb.so
[  2089.915] (II) Module fb: vendor="X.Org Foundation"
[  2089.915] 	compiled for 1.18.4, module version = 1.0.0
[  2089.915] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  2089.915] (II) XRDPDEV(0): using default device
[  2089.915] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[  2089.915] rdpPreInit:
[  2089.915] (**) XRDPDEV(0): Depth 24, (--) framebuffer bpp 32
[  2089.915] (==) XRDPDEV(0): RGB weight 888
[  2089.915] (==) XRDPDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[  2089.915] (==) XRDPDEV(0): Default visual is TrueColor
[  2089.915] (==) XRDPDEV(0): DPI set to (96, 96)
[  2089.915] (II) XRDPDEV(0): 	mode "640x480" ok
[  2089.915] (II) XRDPDEV(0): 	mode "800x600" ok
[  2089.915] (--) XRDPDEV(0): Virtual size is 800x600 (pitch 800)
[  2089.915] (**) XRDPDEV(0):  Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[  2089.915] (II) XRDPDEV(0): Modeline "800x600"x0.0   36.00  800<PHONE_NUMBER>  600 601 603 625 +hsync +vsync (35.2 kHz d)
[  2089.915] (==) Depth 24 pixmap format is 32 bpp
[  2089.916] rdpScreenInit: virtualX 800 virtualY 600 rgbBits 8 depth 24
[  2089.916] rdpScreenInit: pfbMemory bytes 1920000
[  2089.916] rdpScreenInit: pfbMemory 0x7f1bbff49010
[  2089.917] rdpSimdInit: assigning yuv functions
[  2089.917] rdpSimdInit: cpuid ax 1 cx 0 return ax 0x000206c2 bx 0x02000800 cx 0x83ba2203 dx 0x0f8bfbff
[  2089.917] rdpSimdInit: sse2 amd64 yuv functions assigned
[  2089.917] rdpXvInit: depth 24
[  2089.918] (==) XRDPDEV(0): Backing store enabled
[  2089.919] rdpScreenInit: out
[  2089.919] (==) RandR enabled
[  2089.924] (II) AIGLX: Screen 0 is not DRI2 capable
[  2089.924] (EE) AIGLX: reverting to software rendering
[  2089.944] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[  2089.945] (II) AIGLX: Loaded and initialized swrast
[  2089.945] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[  2089.991] (II) Using input driver 'XRDPMOUSE' for 'xrdpMouse'
[  2089.991] (**) Option "CorePointer"
[  2089.991] (**) xrdpMouse: always reports core events
[  2089.991] rdpmousePreInit: drv 0xaaa000 info 0xc85870, flags 0x0
[  2089.991] (II) XINPUT: Adding extended input device "xrdpMouse" (type: Mouse, id 6)
[  2089.991] rdpmouseControl: what 0
[  2089.991] rdpmouseDeviceInit:
[  2089.991] rdpmouseCtrl:
[  2089.991] rdpRegisterInputCallback: type 1 proc 0x7f1bc0322ce0
[  2089.991] (**) xrdpMouse: (accel) keeping acceleration scheme 1
[  2089.991] (**) xrdpMouse: (accel) acceleration profile 0
[  2089.991] (**) xrdpMouse: (accel) acceleration factor: 2.000
[  2089.991] (**) xrdpMouse: (accel) acceleration threshold: 4
[  2089.991] rdpmouseControl: what 1
[  2089.991] rdpmouseDeviceOn:
[  2089.991] (II) Using input driver 'XRDPKEYB' for 'xrdpKeyboard'
[  2089.991] (**) Option "CoreKeyboard"
[  2089.991] (**) xrdpKeyboard: always reports core events
[  2089.991] rdpkeybPreInit: drv 0xaaa740 info 0xe0f330, flags 0x0
[  2089.991] (II) XINPUT: Adding extended input device "xrdpKeyboard" (type: Keyboard, id 7)
[  2089.991] rdpkeybControl: what 0
[  2089.991] rdpkeybDeviceInit:
[  2090.014] rdpkeybChangeKeyboardControl:
[  2090.014] rdpkeybChangeKeyboardControl: autoRepeat on
[  2090.014] rdpRegisterInputCallback: type 0 proc 0x7f1bc011f600
[  2090.014] rdpkeybControl: what 1
[  2090.014] rdpkeybDeviceOn:
[  2090.021] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[  2090.021] (II) AutoAddDevices is off - not adding device.
[  2090.022] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[  2090.022] (II) AutoAddDevices is off - not adding device.
[  2090.022] (II) config/udev: Adding input device VirtualPS/2 VMware VMMouse (/dev/input/event3)
[  2090.022] (II) AutoAddDevices is off - not adding device.
[  2090.022] (II) config/udev: Adding input device VirtualPS/2 VMware VMMouse (/dev/input/mouse1)
[  2090.022] (II) AutoAddDevices is off - not adding device.
[  2090.023] (II) config/udev: Adding input device VirtualPS/2 VMware VMMouse (/dev/input/event2)
[  2090.023] (II) AutoAddDevices is off - not adding device.
[  2090.023] (II) config/udev: Adding input device VirtualPS/2 VMware VMMouse (/dev/input/mouse0)
[  2090.023] (II) AutoAddDevices is off - not adding device.
[  2090.027] rdpSaveScreen:
[  2090.028] rdpDeferredRandR:
[  2090.028] rdpResizeSession: width 1024 height 768
[  2090.028]   calling RRScreenSizeSet
[  2090.028] rdpRRScreenSetSize: width 1024 height 768 mmWidth 260 mmHeight 195
[  2090.028] rdpRRGetInfo:
[  2090.028]   screen resized to 1024x768
[  2090.029]   RRScreenSizeSet ok 1
[  2090.029] rdpResizeSession: width 1920 height 1080
[  2090.029]   calling RRScreenSizeSet
[  2090.029] rdpRRScreenSetSize: width 1920 height 1080 mmWidth 488 mmHeight 274
[  2090.029] rdpRRGetInfo:
[  2090.029]   screen resized to 1920x1080
[  2090.031]   RRScreenSizeSet ok 1
[  2090.045] rdpRRGetInfo:
[  2090.045] rdpRRGetInfo:
[  2090.084] rdpRRGetInfo:
[  2090.085] rdpRRGetInfo:
[  2090.114] rdpInDeferredUpdateCallback:
[  2090.114] rdpkeybChangeKeyboardControl:
[  2090.114] rdpkeybChangeKeyboardControl: autoRepeat off
[  2090.139] rdpRRGetInfo:
[  2090.139] rdpRRGetInfo:
[  2090.159] rdpRRGetInfo:
[  2090.159] rdpRRGetInfo:
[  2090.159] rdpRRGetInfo:
[  2090.159] rdpRRGetInfo:
[  2090.166] rdpRRGetInfo:
[  2090.174] rdpRRGetInfo:
[  2090.174] rdpRRGetInfo:
[  2090.175] rdpRRGetInfo:
[  2090.175] rdpkeybChangeKeyboardControl:
[  2090.175] rdpkeybChangeKeyboardControl: autoRepeat on
[  2090.175] rdpRRGetInfo:
[  2090.176] rdpkeybChangeKeyboardControl:
[  2090.176] rdpkeybChangeKeyboardControl: autoRepeat on
[  2090.178] rdpkeybChangeKeyboardControl:
[  2090.178] rdpkeybChangeKeyboardControl: autoRepeat on
[  2090.249] rdpRRGetInfo:
[  2090.249] rdpRRGetInfo:
[  2090.252] rdpRRGetInfo:
[  2090.252] rdpRRGetInfo:
[  2090.262] rdpRRGetInfo:
[  2090.262] rdpRRGetInfo:
[  2090.264] rdpRRGetInfo:
[  2090.264] rdpRRGetInfo:
[  2090.267] rdpRRGetInfo:
[  2090.268] rdpRRGetInfo:
[  2090.270] rdpRRGetInfo:
[  2090.270] rdpRRGetInfo:
[  2090.274] rdpRRGetInfo:
[  2090.274] rdpRRGetInfo:
[  2090.278] rdpInDeferredUpdateCallback:
[  2090.278] rdpkeybChangeKeyboardControl:
[  2090.278] rdpkeybChangeKeyboardControl: autoRepeat off
[  2090.287] rdpRRGetInfo:
[  2090.287] rdpRRGetInfo:
[  2090.290] rdpRRGetInfo:
[  2090.290] rdpRRGetInfo:
[  2090.294] rdpRRGetInfo:
[  2090.294] rdpRRGetInfo:
[  2090.307] rdpClientConGotConnection:
[  2090.307] rdpClientConGotConnection: g_sck_accept ok new_sck 26
[  2090.307] rdpClientConGotConnection: adding only clientCon
[  2090.307] (EE)
[  2090.307] (EE) Backtrace:
[  2090.307] (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x139) [0x59cd49]
[  2090.308] (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7f1bc564d0af]
[  2090.308] (EE) 2: /usr/lib/xorg/modules/libxorgxrdp.so (rdpClientConCheck+0x1e5) [0x7f1bc0959d15]
[  2090.333] (EE) 3: /usr/lib/xorg-server/Xorg (WakeupHandler+0x6d) [0x43b2dd]
[  2090.334] (EE) 4: /usr/lib/xorg-server/Xorg (WaitForSomething+0x1e9) [0x5954f9]
[  2090.334] (EE) 5: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x10e) [0x4365ee]
[  2090.334] (EE) 6: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x463) [0x43a7f3]
[  2090.334] (EE) 7: /usr/lib/libc.so.6 (__libc_start_main+0xf1) [0x7f1bc563a291]
[  2090.334] (EE) 8: /usr/lib/xorg-server/Xorg (_start+0x29) [0x4246e9]
[  2090.335] (EE) 9: ? (?+0x29) [0x29]
[  2090.335] (EE)
[  2090.335] (EE) Segmentation fault at address 0x7ffe7cbe3390
[  2090.335] (EE)
Fatal server error:
[  2090.335] (EE) Caught signal 11 (Segmentation fault). Server aborting
[  2090.335] (EE)
[  2090.335] (EE)
Please consult the The X.Org Foundation support
	 at http://wiki.x.org
 for help.
[  2090.335] (EE) Please also check the log file at "/tmp/xorg.log" for additional information.
[  2090.335] (EE)
[  2090.335] rdpmouseControl: what 4
[  2090.335] rdpkeybControl: what 4
[  2090.335] rdpLeaveVT:
[  2090.335] (EE) Server terminated with error (1). Closing log file.

This seemed to be an issue with my xrdp.ini file.  I removed it and used the stock one and the segfault goes away.  Not sure what caused it because I forgot to back up the file and see the diffs :(  I am going to close this issue since I cannot duplicate it anymore.


esp32: pinctrl: bring pin grouping support

This PR modifies current Espressif's pinctrl support to be based on pin groupings instead.
Thus, it also updates all esp32/s2/c3-based boards' DTS and overlays.

What is the rationale behind changing this to group-based approach after the node-based approach has just been introduced a few weeks ago?
This will break out-of-tree board implementations again, see also issue #46434.

@martinjaeger @gmarull Thanks for the comments on this PR so far. For now, I've tagged it as Draft/DNM to - if feasible - pursue a friendlier way for this migration.

@martinjaeger Indeed, this MR will require reworking on current out-of-tree overlays to keep it rolling. It is unfortunate but I hope the update on Espressif's pinctrl documentation will ease things a little (updated overlays on this PR may also work as a migration guide).
On the other side, the proposed approach will also enable conciseness when defining states on current and yet-to-come features on Espressif SoCs as defined on our roadmap.

All good, just wanted to make sure that the shift in pinctrl approach was well thought through. If it's required for future features we'll have to live with the adaptions of out-of-tree boards.


Add legacy octopush (Octopush-DM from 2011 to 2020 accounts) version

This is a small addition to handle the Octopush legacy accounts created from 2011 to 2020 which have a different API endpoint and different arguments.

Reading your code, octopushVersion = 2 and using /v1/ api. Is it correct?

Hello all,
Sorry for indentation & linter. I'll fix my env, I added this using emacs on server directly. I'll change that for the future. Thanks Saibamen !
For the rest Louislam, yes it's ok. I've named them "V1" and "V2", but it's more CURRENT and LEGACY. LEGACY use another domain name and in CURRENT they added a /v1/ to allow them to have a v2 i guess...
Maybe I should rename to :

Legacy (Octopush-DM) keyword : legacy
V1 (Octopush API v1) keyword : v1
This allow a V2 with a keyword v2 in their API implementation.

At last but not least, @AlexandreGagner should try my pull request since he has a Octopush V1 (current) integration working to see, if it's not breaking things on his side...

Hello,
I finally took some time to merge with current master and fix indentation and typo as requested.
DeeJayPee


My app keeps white screen after launch on android platform

After the flutterSDK was upgraded, my app kept a white screen after launching on the Android platform,
`Launching lib\main.dart on DUK AL20 in debug mode...
Running Gradle task 'assembleDebug'...
√  Built build\app\outputs\flutter-apk\app-debug.apk.
Installing build\app\outputs\flutter-apk\app.apk...
W/FlutterActivityAndFragmentDelegate( 2373): A splash screen was provided to Flutter, but this is deprecated. See flutter.dev/go/android-splash-migration for migration steps.

`
`[√] Flutter (Channel stable, 2.5.3, on Microsoft Windows [Version 10.0.19043.1466], locale zh-CN)
    • Flutter version 2.5.3 at E:\Android\Flutter\flutter
    • Upstream repository https://mirrors.tuna.tsinghua.edu.cn/git/flutter-sdk.git
    • Framework revision 18116933e7 (4 months ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4
    • Pub download mirror https://mirrors.tuna.tsinghua.edu.cn/dart-pub
    • Flutter download mirror https://mirrors.tuna.tsinghua.edu.cn/flutter

[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at E:\Android\Sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = E:\Android\Sdk
    • Java binary at: E:\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Users\edz\AppData\Local\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.10.4)
    • Visual Studio at d:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.10.31515.178
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2020.3)
    • Android Studio at E:\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[√] VS Code, 64-bit edition (version 1.57.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension can be installed from:
       https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[√] Connected device (4 available)
    • DUK AL20 (mobile) • <IP_ADDRESS>:7555 • android-x64    • Android 6.0.1 (API 23)
    • Windows (desktop) • windows        • windows-x64    • Microsoft Windows [Version 10.0.19043.1466]
    • Chrome (web)      • chrome         • web-javascript • Google Chrome 98.0.4758.102
    • Edge (web)        • edge           • web-javascript • Microsoft Edge 97.0.1072.62

• No issues found!

下方是android的环境版本
distributionUrl=https://services.gradle.org/distributions/gradle-6.9-all.zip
classpath 'com.android.tools.build:gradle:4.2.0'
ext.kotlin_version = '1.5.10'
compileSdkVersion 30
minSdkVersion 21
targetSdkVersion 30
`

补充一下,app运行截图

@Inisit
As mentioned in the console log you shared:
A splash screen was provided to Flutter, but this is deprecated. See flutter.dev/go/android-splash-migration for migration steps.
Since 2.5 stable version, the implementation of Splash screen has changed, so you'll need to migrate your splash screen implementation to as mentioned in the document: https://docs.flutter.dev/development/ui/advanced/splash-screen#migrating-from-manifest--activity-defined-custom-splash-screens
Once you do that, the white screen behavior should be resolved.
Closing this for now as not an issue.

我根据文档去掉了  io.flutter.embedding.android.SplashScreenDrawable 这个标签, 然后我新建了一个全新的项目,但是页面还是一直保持白屏状态, 报错日志如下:
Launching lib\main.dart on DUK AL20 in debug mode... Running Gradle task 'assembleDebug'... √  Built build\app\outputs\flutter-apk\app-debug.apk. Installing build\app\outputs\flutter-apk\app.apk... E/flutter ( 2058): [ERROR:flutter/shell/gpu/gpu_surface_gl.cc(53)] Failed to set up Skia Gr context. E/flutter ( 2058): [ERROR:flutter/shell/common/platform_view.cc(85)] Failed to create platform view rendering surface Debug service listening on ws://<IP_ADDRESS>:52374/bP14d_ctfY4=/ws Syncing files to device DUK AL20... E/flutter ( 2058): [ERROR:flutter/shell/gpu/gpu_surface_gl.cc(53)] Failed to set up Skia Gr context.
而且,我发现页面其实已经有了,我添加了日志,

当我点击这个位置的时候

会有日志输出

@darshankawar

@Inisit
Can you provide entire console log ? What's the Android api version of the device / emulator you are running on ?

i'm having same problem
tried with different flutter sdk versions (2.5.3,2.8,2.10.0,2.10.1)
tried to change target sdk(30,31,29) and compile sdk(29,30,31) and min sdk (18,19,20,21,22)
tested on sumsung s10,s10+,note10 real devices and emulators
android 10/12/11 api 29,20
tested with two different complete apps but same problem


Is there support for relasense D410 cameras?

I got the D410 camera, but when I tried RViz, I couldn't find a way to use one of the cameras as a RGB camera

[Please Ignore - RealSense system comment]

D410 has no RGB sensor. D415 has RGB camera.


Distribute season loading (or rewrite in Elixir)

This is to get past the significant slowness due to rate limiting prevention. Distributing by season_id would probably be best. Can add a flask sever and use a single REST endpoint. Or, we could re-write in Elixir, but that would make the barrier to entry for contributions higher.

Argument for this: the NBA's rate limiting is getting more aggressive. We've had to bump the time between requests to .5 to .7. See this issue: https://github.com/mpope9/nba-sql/issues/19

if you need any elixir contributions, hmu 👍

@ddresselhaus Forsure! I'm on the fence about it at the moment, but will let you know if some type of 'control' layer is in the works.


Axis labels should have a rotate_angle property

@madridnick

+1, its alot less usefull without

#343 starts dealing with this. The question is if we wrap text or rotate, do we do both?

@dmadeka , let me know where you're at with this and I can help if needed.
Here are my thoughts:

Include both, wrap text and rotate
Not sure if this makes sense but another attribute to display only certain labels (e.g,. every other --> Jan, March, May, July, etc...)

Is there a fix for this?

@ruxi, can you use my PR? This is a 1.0 goal

@dmadeka Will give it a try. Is there an example of it's usage?

This was taken care of in PR #669


Enhancement: Add extra resources for util accesstoken get

Currently when I want an accesstoken for Graph I have to run m365 util accesstoken get --resource https://graph.microsoft.com. For SharePoint I can just run m365 util accesstoken get --resource sharepoint. To me it would be useful if we add another named resource for Graph so you can use m365 util accesstoken get --resource graph to get a graph token.
Also noticed that we support sharepoint as resource value, but this isn't included in the docs. The only way to know this if you look at one of the examples. Therefore I also suggest that we also add these named resources to the description of the resource option in the docs.
Suggested resources to add:

Resource
Endpoint

graph
https://graph.microsoft.com

o365management
https://manage.office.com

powerapps
https://api.powerapps.com

powerplatform
https://api.bap.microsoft.com

That's an excellent idea! Have you considered using tokens for the resource option similar to how we use them for the m365 request command? Specifically, utilizing the @graph and @spo tokens.

That's an excellent idea! Have you considered using tokens for the resource option similar to how we use them for the m365 request command? Specifically, utilizing the @graph and @spo tokens.

Yeah, I know that you can send requests using m365 request, but I'm more a Postman guy 😊 When trying to clear things out how a certain API endpoint works, Postman is way more convenient to toggle headers, parameters, edit JSON body, ... Also support syntax highlighting etc.

That's an excellent idea! Have you considered using tokens for the resource option similar to how we use them for the m365 request command? Specifically, utilizing the @graph and @spo tokens.

Yeah, I know that you can send requests using m365 request, but I'm more a Postman guy 😊 When trying to clear things out how a certain API endpoint works, Postman is way more convenient to toggle headers, parameters, edit JSON body, ... Also support syntax highlighting etc.

What I actually mean is using the tokens in this command, for example:
m365 util accesstoken get --resource @graph
m365 util accesstoken get --resource @spo

Yes, and I'm not sure what we would gain from that setup as opposed to the autocomplete values we currently have. I'd say, let's keep those.

But I like the idea @milanholemans! Should we add autocomplete prefab values for all resources we currently expose? (PowerApps as well, for example)

But I like the idea @milanholemans! Should we add autocomplete prefab values for all resources we currently expose? (PowerApps as well, for example)

Was kinda thinking the same 🙂

But I like the idea @milanholemans! Should we add autocomplete prefab values for all resources we currently expose? (PowerApps as well, for example)

Updated the specs with some extra resources which I think are the most useful.

Should it be o365management or m365management?

Personally, I find powerapps and powerplatform not obvious. If you told me you've got this token and asked me which endpoint it uses, I wouldn't be able to tell you. Not sure if it's different with folks who use these APIs more often, but I wonder if we're not going too far here. @appieschot, any experience you could share here?

Should it be o365management or m365management?

According to the docs and Azure, it's still called O365

If you told me you've got this token and asked me which endpoints they use, I wouldn't be able to tell you. Not sure if it's different with folks who use these APIs more often, but I wonder if we're not going too far here.

Yes while writing them down, I kinda had the same feeling tbh.

We could add an explanatory section to the docs.. I'm sure that if you work with these endpoints, it's kind of easy to use it this way as soon as you know it. Plus it doesn't hinder other folks, as it's autocompleted anyway.

Personally, I find powerapps and powerplatform not obvious. If you told me you've got this token and asked me which endpoints they use, I wouldn't be able to tell you. Not sure if it's different with folks who use these APIs more often, but I wonder if we're not going too far here. @appieschot, any experience you could share here?

Purely semantics I know the difference, working in a real life scenario I spend most time working with solutions that contains Power Automate and Power Apps, having to switch would take mental effort.
Sample: work with an app that does something on button press, might want to read some props on that specific action. Could be both inline in the App or a Power Automate process that gets fired.
I do like the idea however and wouldn't be surprised is we move more to a single PowerPlatform token 💡

Purely semantics I know the difference, working in a real life scenario I spend most time working with solutions that contains Power Automate and Power Apps, having to switch would take mental effort.

In this case it's more the API to which these tokens maps. Is it obvious which one either of these tokens are mapped to?

If it's not clear enough we can remove the power platform and power apps resources. Actually I'm also in doubt that the o365 management API resource will be used.

I'd say: just add every possible resource we use and show a table in the docs how these map to apis. Why not? But maybe I'm starting to repeat myself. :)

I'd say: just add every possible resource we use and show a table in the docs how these map to apis. Why not? But maybe I'm starting to repeat myself. :)

Also fine for me 😅

I'd say: just add every possible resource we use and show a table in the docs how these map to apis. Why not?

Why should we? Just because we use an API, doesn't mean that folks will use it either. If we need a table of mappings between resources and tokens, do we make things easier or harder? I wouldn't add tokens just for the sake of adding them. I suggest that we start with those that we see being used the most and add more when the need arises.

I'd say: just add every possible resource we use and show a table in the docs how these map to apis. Why not?

Why should we? Just because we use an API, doesn't mean that folks will use it either. If we need a table of mappings between resources and tokens, do we make things easier or harder? I wouldn't add tokens just for the sake of adding them. I suggest that we start with those that we see being used the most and add more when the need arises.

I that case, we only add Graph as resource right? We could also add O365 management API endpoint, but according to me, this will never be used (used to fetch audit logs).

I that case, we only add Graph as resource right? We could also add O365 management API endpoint, but according to me, this will never be used (used to fetch audit logs).

In this case, I suggest we rely on user demand and wait until someone asks for other resources and can share a use case that we don't address with a specific command already.

Updated the specs, thank you!

Can I work on this?

yes definitely @dojcsakj!

Please, discard abeecd0 - sorry.


FAM Tools front-end error after IDIR login before seeing post-login page.

Describe the bug
Post-login error on page https://tools-fam-user-pool-domain.auth.ca-central-1.amazoncognito.com/error?error=redirect_mismatch&client_id=52k0amgo04bdaam3hc488fakv0
Go to FAM Tools (fam-tools URL). Pick Login IDIR
To Reproduce
Steps to reproduce the behavior:

Go to FAM Tools (fam-tools URL)
Pick Login IDIR
Complete IDIR login
Get an error page before being returned to FAM

Expected behavior
No error
Screenshots


⚠ Bofrost.com has degraded performance

In 01770c8, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1045 ms

Resolved: Bofrost.com performance has improved in a6686d7 after 10 minutes.


Add WebKit support (once available) for E2E testing

https://github.com/o1-labs/snarkyjs/issues/415

Issue in another repo has been created.


package.json: Removes upper version limit on node & npm engines

The maximum version constrain set on the node & npm engines makes the package unusable with the recent node versions. This PR removes that upper limit.

Thanks! Will merge it now and release new version 👍 more PRs welcome ;)


[workflow][api][SIMS #1200] End Application soft archive

Created an environment variable to store number of days passed.
Created new boolean column in applications table to flag archived applications.
Implemented functionality to set archived column to true when an institution user submits a scholastic standing event.
Implemented functionality to throw an error / fail gracefully when either an institution user or student user tries to submit a scholastic standing event / appeal on an archived application.
Created a new end point to set archived column to true in applications table when 43 days have passed end of study period.
Created a new scheduler workflow to consume the new end point above.

Nice and clean work @henryoforeh-aot . Had the same comments what other devs mentioned. Please have a look.


404 on npm run serve

I ran
npm i
npm run serve

and got the following result:

I just ran into the same problem. But when you start the server, the correct path is: http://localhost:8000/dev
You should now see the component with the count button.

I see. Thank you.


Catch missing intent attribute

Procedure arguments should have intent attributes. Default is intent(inout), this could be an auto-fix. In principle it should also be possible to work out if this could be more specifically intent(in) or intent(out), based on whether the arguments are only ever read from/written to

Good idea, but I'd be wary of auto-fixing it to intent(inout) unless we can guarantee that that was actually the intent. I've seen code where intent(in) should have been obvious but the author either forgot to add intent, didn't know about intent, or was too lazy to add it.


tuple sum

tuple_sum in pythonic/include/builtin/sum.hpp should merge tuple types instead of taking the first one:
def foo(a):
    return sum(a)

with a = (1, 3.3, 4)

Cannot reproduce the issue, the tuple is computed in a dynamic fashion, and the bug is not reproduced


fix(rust): Changed Argument name.

Current behavior

currently the variable name is VAULT.
Proposed changes
the variable name is changed from VAULTto VAULT_NAME
and a doc string referring to same has also been added

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] There are no Merge commits in this Pull Request. Ockam repo maintains a linear commit history. We merge Pull Requests by rebasing them onto the develop branch. Rebasing to the latest develop branch and force pushing to your Pull Request branch is okay.
[x] I have read and accept the Ockam Community Code of Conduct.
[x] I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

Hey @AkhileshJyotishi , your PR will be merged through https://github.com/build-trust/ockam/pull/6799
You are added as a coauthor, so you get full credit for your contribution 🚀


Ato 266 docs update

Proposed changes:
Update the documentation for Buttons using messages with '/'. It wrongly stated that messages with '/' bypass NLU, which is not the case.
Status (please check what you already did):

[x] updated the documentation
[x] updated the changelog (please check changelog for instructions)

@ancalita ,
Thanks for the quick review of the other PR!
Instead of rebasing, it was easiest to create a new branch and a new PR.
I also added the changelog.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.9.272",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5b3a9a2be59478b013a430ac57b0f3d65471b071"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "5b3a9a2be59478b013a430ac57b0f3d65471b071",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "ext4: fix bug on in ext4_es_cache_extent as ext4_split_extent_at failed\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.9.272 by commit 5b3a9a2be59478b013a430ac57b0f3d65471b071, it was introduced in version  by commit . For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1000723


Missing Error

Hello, I am a newbee to replicate-python and I met a missing error without telling me which fields are missing:
Here is error message:
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
Executing tests from //Data:IntelligenceCenter_test
-----------------------------------------------------------------------------
E
======================================================================
ERROR: test_llama2 (__main__.TestNewsNum)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/private/var/tmp/_bazel_javieryu/aaf029806d53299ea7c92c3aeb5caf78/sandbox/darwin-sandbox/39/execroot/__main__/bazel-out/darwin-fastbuild/bin/Data/IntelligenceCenter_test.runfiles/__main__/Data/IntelligenceCenter_test.py", line 31, in test_llama2
    response = agent.Generate("How do you feel about the weather today?")
  File "/private/var/tmp/_bazel_javieryu/aaf029806d53299ea7c92c3aeb5caf78/sandbox/darwin-sandbox/39/execroot/__main__/bazel-out/darwin-fastbuild/bin/Data/IntelligenceCenter_test.runfiles/__main__/Data/IntelligenceCenter.py", line 89, in Generate
    output = replicate.run("replicate/llama-7b:ac808388e2e9d8ed35a5bf2eaa7d83f0ad53f9e3df31a42e4eb0a0c3249b3165",input={"prompt": final_input})
  File "/opt/miniconda3/lib/python3.7/site-packages/replicate/client.py", line 127, in run
    prediction = self.predictions.create(version=version, **kwargs)
  File "/opt/miniconda3/lib/python3.7/site-packages/replicate/prediction.py", line 85, in create
    return self.prepare_model(obj)
  File "/opt/miniconda3/lib/python3.7/site-packages/replicate/collection.py", line 33, in prepare_model
    model = self.model(**attrs)
  File "/opt/miniconda3/lib/python3.7/site-packages/pydantic/main.py", line 165, in __init__
    __pydantic_self__.__pydantic_validator__.validate_python(data, self_instance=__pydantic_self__)
pydantic_core._pydantic_core.ValidationError: 3 validation errors for Prediction
output
  Field required [type=missing, input_value={'id': 'aqykwezb7wkthhaui...ezb7wkthhauiba4t6sh2e'}}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.3/v/missing
started_at
  Field required [type=missing, input_value={'id': 'aqykwezb7wkthhaui...ezb7wkthhauiba4t6sh2e'}}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.3/v/missing
completed_at
  Field required [type=missing, input_value={'id': 'aqykwezb7wkthhaui...ezb7wkthhauiba4t6sh2e'}}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.3/v/missing

----------------------------------------------------------------------
Ran 1 test in 0.350s

FAILED (errors=1)

Here is my code:
class Llama2Agent(Agent):
    def __init__(self, name:str):
        self.name = name
        os.environ["REPLICATE_API_TOKEN"] = llama2_api_key

    def Generate(self,query:str):
        pre_prompt = "You are a professional stock analyst. You do not respond as 'User' or pretend to be 'User'. You only respond once as a professional stock analyst."
        final_input = pre_prompt + " " + query
        output = replicate.run("replicate/llama-7b:ac808388e2e9d8ed35a5bf2eaa7d83f0ad53f9e3df31a42e4eb0a0c3249b3165",input={"prompt": final_input})
        for item in output:
            # https://replicate.com/a16z-infra/llama-2-13b-chat/versions/9dff94b1bed5af738655d4a7cbcdcde2bd503aa85c94334fe1f42af7f3dd5ee3/api#output-schema
            print(item)
        return outputp[0]`

Here is my unit test:
def test_llama2(self):
        agent = Llama2Agent("Sam")
        response = agent.Generate("How do you feel about the weather today?")
        print("Llama2 response", response)
        self.assertNotEqual(response, "")

Any idea what are missing right here?

Hi @yjianpen. It looks like this is an issue with Pydantic 2 (see #121). I also see that you're using Python 3.7, which isn't supported. Could you please update to Python >= 3.8 and confirm that you're using the latest release of replicate-python?

@yjianpen Please let me know if the suggested fix doesn't work for you, and I'd be happy to reopen. Thanks!


fix(plots): Polished and fixed multiple plots

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Workaround for Cannot read property 'contents' of undefined

Easy workaround for issue https://github.com/gruntjs/grunt-contrib-imagemin/issues/325

Should be fixed via https://github.com/gruntjs/grunt-contrib-imagemin/pull/329

Yes, thanks, Forcing 4.0.0 imagemin package for grunt-contrib-imagemin works.

Yay!

#329 did the trick form me


:back: activate back button for book-appointment

:rocket: deployed to http://profiles-pr-41.dev.c2s.nhschoices.net

:rocket: deployed to http://profiles-pr-41.dev.c2s.nhschoices.net

I tried to be clever with my previous commit comments whilst rebasing and I seem to have removed them all :see_no_evil:

@ajthomascouk What do you think to this way of doing the back link rather than hardcoding it with JS in the view? I should have branched rather than overwriting yours! Sorry.

:rocket: deployed to http://profiles-pr-41.dev.c2s.nhschoices.net

:rocket: deployed to http://profiles-pr-41.dev.c2s.nhschoices.net

:rocket: deployed to http://profiles-pr-41.dev.c2s.nhschoices.net

@st3v3nhunt wrote:

What do you think to this way of doing the back link rather than hardcoding it with JS in the view?
To be fair I tried that way first, but couldn't get it to pass Travis.


Refs #6573 Example Log migration to FastDDS.

Example code of migration guide:
https://gitlab.intranet.eprosima.com/eProsima/fastrtps/wikis/deprecation
This unneeded and small PR should be done eventually. Doing so as the migration guide example is very useful for learning purposes.

Updating guide and splitting commits.

Build status:

Linux
Mac
Windows
Performance


[IONQ] Vendor Transformer adoption

Summarize the task
With broader changes to devices (https://github.com/quantumlib/Cirq/issues/4744) and optimizers/trasnformers (https://github.com/quantumlib/Cirq/issues/4722), vendors might need to update device decomposition to use the newest transformer APIs. At first glance it looks like:

cirq-ionq has their own devices and should be in a good position to consolidate any missing device info into the metadata fields as well as adapt decompose_to_device into a proper transformer.
https://github.com/quantumlib/Cirq/blob/45624ff7259f53589c2139c97108d8bf11502173/cirq-ionq/cirq_ionq/ionq_devices.py#L106
@ColemanCollins @nakardo @gmauricio
Acceptance criteria - when is the task considered done?

Related
Related issues: #4901 , #5127

@Cynocracy (who should probably be added to the owners)

Adding comment so this can be assigned to me


add .vscode/ to .gitignore

When VS Code used for project editing, changing the VS Code project settings will cause VS Code write the new settings to .vscode directory. Therefore untrack this directory.

Discussion of the generalized version of this PR in #111 and I'm going to leave this open and un-merged until we come to a consensus there first.

I suggest decoupling the change to this cookiecutter repo from the change to the generated project.

@Lnaden - we talked about adding .vscode - could this PR be added to the 2023 review?


aiotnb - Python network library

Project Details
How would you describe your project?
The Project ("aiotnb") is a reimplementation of the thenewboston Python library using asyncio coroutines, a robust HTTP response object system (instead of simply returning JSON data or raising on an error), and fully-checked type annotations.
What problem does this project solve?

Asyncio coroutines
The Python library currently in use relies on standard functions ("sync") for the API calls. These functions all run in series, meaning a function that takes a long time to complete will block everything else until it has completed.
Using asyncio coroutines ("async") alleviates this issue as coroutines hand back control while they are waiting on something (ie. a network request or file read). This allows a significantly greater number of blocking calls (such as API calls) to be made in the same time span.

HTTP response object system
By validating and parsing the response JSON into a Python class, we can ensure that all API responses are 100% covered and no errant typos in data make their way downstream to the end-user.

Fully-checked type annotations
By utilizing a static type checker, it is possible to catch and correct a myriad of possible errata in software before it even runs. By properly annotating types, the software also becomes self-documenting, in that an IDE can read the type annotations and provide information immediately while editing.

Who is the target market?
TNB tool developers, TNB integration developers, and anyone else who might use the current Python library.
How will this project benefit the network and/or the community?
This will be a significant improvement in developer experience for anyone writing Python software connecting to the TNB network, both in actual programming, via coroutines and the object response system, as well as improved documentation from the fully-checked types. Developer time should also improve because developers are no longer spending time parsing and validating the API responses themselves.
How is this project centered around thenewboston?
This project is a library that directly utilizes the primary network APIs (Bank, Validator, Confirmation Validator).
What is the estimated completion date for this project? (rough estimates are acceptable)
Since this project relies on the network API, it must be updated as the network is updated, meaning no actual completion date can be given.
That said, full functional status (tests, documentation, etc) with the network in its current state should be accomplished in 4-5 months. (This relies heavily on developer time commitments, as there are only two of us for now).
All estimates are doubled to allow for real-life intervention and other priorities.
Please include a detailed roadmap for your project below. This must include a list of all milestones where payments will be awarded upon completion of each.

Library Core

HTTP

flexible system to be created once and use for all API calls

Exceptions

exception base classes
exceptions likely to be needed

Type-checking
Validation

abstract validator to take schema, return result

Testing

HTTP
Validator

Performance benchmark

Comparing synchronous library to async

Bank API Implementation

HTTP calls to all bank endpoints
Type-checking
Documentation
Validation
Testing

Primary Validator API Implementation

HTTP calls to all PV endpoints
Type-checking
Documentation
Validation
Testing

Confirmation Validator API Implementation

HTTP calls to all CV endpoints
Type-checking
Documentation
Validation
Testing

Fully-functional Example

Documentation
Should-fail and should-pass tests
Exact details TBD

Publish

Final documentation proofing
Final test checks and validation
Publish documentation to readthedocs.io
Publish python package to pip

What is your Discord username?
AnonymousDapper#7467 (aareon#0913 as collaborator)
Additional files and documentation including architectural diagrams, wireframes, research documents, visuals, etc… (optional)
N/A
Milestone Details
Please include a detailed breakdown of the first milestone including a list of all quantifiable objectives. Upon
completion of the milestone, each objective will be reviewed by thenewboston team and once all objectives have been
verified as completed, coins will then be rewarded.
Note that all future detailed milestone breakdowns will be written as a separate GitHub issue. Only the first milestone
is included in this project proposal.

First Milestone Description
Library core implementation includes the frameworks that underpin the user-facing components of the library. This includes an HTTP client, an exceptions library, a JSON schema validator, and component stubs to be implemented at later milestones.
(Exceptions library is not exhaustive and more exception types may be discovered to be necessary later on down the line.)
First Milestone Objectives

#
Objective
How can auditors verify milestone?
Estimated TNBC Value

1
HTTP client system
Check/run core http tests in git repo
10,000

2
Exceptions library
View exceptions library source in git repo
4,000

3
Type checking
Run mypy (python type checker) on the project
6,000

4
JSON validation
Run JSON validation tests in git repo
10,000

5
Testing
Run test suite in git repo
6,000

6
Performance benchmark
Run benchmark and see improved throughput
4,000

Estimated total milestone value: 40,000 TNBC
How long do you estimate this first milestone will take to complete?
4 weeks
Project Wallet
16c9d5010701093e4427b12d3674024346a6ac90f7cc3cbebc6d3d041d435fdd

Hello AnonymousDapper, please be sure to follow the updated templates (you should not have Estimated TNBC Value column and the Estimated total milestone value). Please remove those and we will continue reviewing this project proposal

Whoops, I just looked at the other proposal and saw it had the estimated values.
Edits completed as requested.

Hello @AnonymousDapper we have approved your project and the first milestone!
We have decided to value the first milestone to be 35,000 coins upon completion.
Also, please do keep in mind that we will be releasing beta version of the network soon, which will significantly change a lot of the existing codebase.

Thank you!
@angle943 I did have some questions/suggestions about the actual network code as well. I'd appreciate it if you could point me to a place to direct those.

@AnonymousDapper

thenewboston-python - This library contains all of the core logic, shared functionality, and constants used by both the Bank and Validator
Bank
Validator

@buckyroberts I appreciate the rapid response. I've looked at the network library (and the node servers a little bit), and I actually had questions regarding some design choices. Are you the person to ask these? Where should I ask?

@AnonymousDapper you can ask in our Discord server https://discord.gg/thenewboston we have a channel called #back-end which is under our TEAMS category.


recovery: PTO per packet number space

This makes PTO consistent with loss detection, which is already per
packet number space.
Besides aligning the implementation to the -recovery draft, this also
fixes some recovery bugs that were introduced in 5c99278, which caused
some packets to not be retransmitted when lost during the handshake.

I tested this manually using the http3-client and http3-server examples, and qvalve with the following scripts:
> h1 drop

< i1 drop

< h2 drop

Though it's pretty obvious the recovery code needs tests. I'll make a separate PR for that once I figure out how to do it.

Silenced a clippy warning that is not helpful...


test quick question: quick question button with layout controls

Testing #188542
When I set "chat.experimental.defaultMode": "quickQuestion", I was really confused on where the button was, since I disabled layout controls on my title bar. Eventually, I found it, but it was a little confusing. I'm not too sure if it should be toggled on and off by the "Layout Controls`

The button isn't there anymore and is instead in the Command Center when opened.


Results of subtypes of list, returns Array, rather than PyObject

Consider the example python (in example.py)
class CustomList(list):
    def twice_len(self):
        return 2*len(self)

def get_c_list():
    return CustomList(["foo","bar"])

If I call in from julia:
using PyCall
unshift!(PyVector(pyimport("sys")["path"]), "");
@pyimport example
xs=example.get_c_list()

Then xs is not of type PyObject
IN[2]>xs
OUT[2]:> 2-element Array{Any,1}:
 "foo"
 "bar"

and its special method is not available:
IN[3]> xs.twice_len()
OUT[3]> type Array has no field twice_len
while loading In[3], in expression starting on line 1

This is a MWE.
It is a more serious issue in the python NLTK, which extends list often, in significant ways (Including using it to implement Trees).

You can always inhibit conversion to a Array by using pycall to specify the desired return type.  e.g. example = pyimport("example") followed by pycall(example["c_list"], PyVector).
There is a tension here between automatically converting Python objects to corresponding native Julia types, which are convenient for subsequent use in Julia, vs. leaving them as something closer to the native Python type, which is more convenient for subsequent use in Python.  Manual intervention (to specify the desired type) is likely to always be required in some cases if we guess wrong.
(Do you have a suggestion for how to pick a better default?)

Thanks.
I worked that out just as you were posting this.
Now I have a new issue of what types Iterators/generators return, when Iterated in Julia.
I will again construct a MWE with my new knowledge and create another issue if I can't work it out.


modules: mcuboot: automatic build from git

Add an option to automatically override the build version number with the numeric equivalent of the first 8 characters of the git commit hash.

The PR title is misleading. It sounds very mcuboot-specific but most of the git changes are completely generic.
This should probably be 2 PRs: one for reviewers who don't care about mcuboot and the other PR for those who do.
https://docs.zephyrproject.org/latest/contribute/contributor_expectations.html#defining-smaller-prs

As you say this is two logical chunks of work, but the first doesn't have much reason to exist without the second.
If they were split, the second PR would still have the commits of the first as it is required to test the implementation.
So we would still have this PR (the second), plus another one with just the first commits.
If reviewers have no interest in mcuboot, they are free to review just the version infrastructure changes. From the same page

Partial reviews are permitted, but the reviewer must add a comment indicating what portion of the PR they reviewed. Examples of useful partial reviews include:

If you would still like a dedicated PR with just the first commits, I'm happy to create it, but this PR isn't going away.

If they were split, the second PR would still have the commits of the first as it is required to test the implementation.

Yes I meant separate and "consecutive", sorry for being too vague.

If reviewers have no interest in mcuboot, they are free to review just the version infrastructure changes.

That's assuming they ever notice it in the first place in the tide of Github notifications which is very unlikely given such an mcuboot-specific title that refers only to the second part (I opened this only because you linked it from closed #73380, thanks for that). If want a single, 2-in-1 PR then you need at least a "double" title.


Windows - crash enabling prometheus_process_collector

Using Windows Server 2012 R2, rabbitmq 3.6.15, erlang OTP 20.2, with plugins from <IP_ADDRESS> release.  Get the following error in console when enabling the plugin.  Rabbitmq is installed as a service and the user which runs the service has full control of the plugin expand directory.
C:\Program Files (x86)\RabbitMQ Server\rabbitmq_server-3.6.15\sbin>rabbitmq-plugins.bat enable prometheus_process_collector
The following plugins have been enabled:
prometheus_process_collector
Applying plugin configuration to<EMAIL_ADDRESS>failed.
Error: {plugin_module_unloadable,"prometheus_process_collector",
{error,on_load_failure}}
I am unable to restart rabbitmq if the plugin is in enabled status.  The following is generated in the rabbitmq.log:
=WARNING REPORT==== 27-Feb-2018::13:24:12 ===
The on_load function for module prometheus_process_collector returned:
{error,{load_failed,"Failed to load NIF library<EMAIL_ADDRESS>'The specified module could not be found.'"}}
=INFO REPORT==== 27-Feb-2018::13:24:12 ===
Error description:
{plugin_module_unloadable,"prometheus_process_collector",
{error,on_load_failure}}
Log files (may contain more information):
<EMAIL_ADDRESS><EMAIL_ADDRESS>Stack trace:
[{rabbit_plugins,prepare_dir_plugin,1,
[{file,"src/rabbit_plugins.erl"},{line,249}]},
{rabbit_plugins,'-prepare_plugins/1-lc$^0/1-0-',2,
[{file,"src/rabbit_plugins.erl"},{line,213}]},
{rabbit_plugins,prepare_plugins,1,
[{file,"src/rabbit_plugins.erl"},{line,213}]},
{rabbit,broker_start,0,[{file,"src/rabbit.erl"},{line,300}]},
{rabbit,start_it,1,[{file,"src/rabbit.erl"},{line,424}]},
{init,start_em,1,[{file,"init.erl"},{line,1085}]},
{init,do_boot,3,[{file,"init.erl"},{line,793}]}]

I also tried replacing only the prometheus_process_collector plugin with version 1.1.0 and receive the same errors.

Hi, unfortunately process collector currently supports Linux, OSX, and FreeBSD, but not Windows.

Closing this issue, if you'd like you can watch https://github.com/deadtrickster/prometheus_process_collector repo, hopefully it'll get Windows support at some point.


feat/setup a web socket.io on the server

worked on setting up a web socket.io on the server-side and public rendering a mock client

@Alao-Abiodun
Kindly fix the merge conflict


Support MQTT-5: Request problem information

Motivation
See the tracker: #369
Modifications

Support MQTT-5: Request problem information

Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation

[x] no-need-doc

Codecov Report

Merging #655 (55bcfcf) into master (0d0af93) will decrease coverage by 0.17%.
The diff coverage is 34.32%.

:exclamation: Current head 55bcfcf differs from pull request most recent head 54e5714. Consider uploading reports for the commit 54e5714 to get more accurate results

@@             Coverage Diff              @@
##             master     #655      +/-   ##
============================================
- Coverage     77.97%   77.80%   -0.18%
- Complexity      910      912       +2
============================================
  Files           108      108
  Lines          3923     3928       +5
  Branches        276      287      +11
============================================
- Hits           3059     3056       -3
- Misses          702      709       +7
- Partials        162      163       +1

Impacted Files
Coverage Δ

...s/mqtt/proxy/MQTTProxyProtocolMethodProcessor.java
77.89% <0.00%> (-0.86%)
:arrow_down:

...lsar/handlers/mqtt/support/Qos1PublishHandler.java
64.81% <0.00%> (ø)

...qtt/support/MQTTBrokerProtocolMethodProcessor.java
78.84% <41.17%> (-0.99%)
:arrow_down:

...lsar/handlers/mqtt/messages/MqttPropertyUtils.java
89.47% <100.00%> (-0.78%)
:arrow_down:

.../pulsar/handlers/mqtt/messages/ack/MqttPubAck.java
87.80% <100.00%> (+0.30%)
:arrow_up:

...handlers/mqtt/restrictions/ClientRestrictions.java
68.00% <100.00%> (+1.33%)
:arrow_up:

...pulsar/handlers/mqtt/MQTTCommonInboundHandler.java
77.94% <0.00%> (-4.42%)
:arrow_down:

...e/pulsar/handlers/mqtt/utils/PulsarTopicUtils.java
78.26% <0.00%> (+1.73%)
:arrow_up:

Continue to review full report at Codecov.

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


Add TruffleRuby to CI?

The changes in #977, released in Dalli 3.2.7, started using a feature of Ruby that released versions of TruffleRuby do not support (the connect_timeout keyword argument in TCPSocket#initialize). This is entirely a compatibility issue on the TruffleRuby side, but it's had the unfortunate effect of breaking applications in a patch update of Dalli. We have a PR open adding the missing support to TruffleRuby, which should make its way into the next release.
Since the usage of connect_timeout is already conditional based on a Ruby version check, this particular problem could be avoided by augmenting the check. I may open a PR for that.
Would the team be open to adding TruffleRuby to the project's CI? Our compatibility with CRuby is quite high, but obviously there are some holes. The team is quite responsive though and I don't anticipate it being a burden for Dalli. I can do the work, but didn't want to open a PR without checking first.

@nirvdrum So I would, provided there's someone on the TruffleRuby side who steps up to be a point of contact for issues.  I've seen TruffleRuby issues languish in other repos (although not recently) so I'd want to know "who to call" in case of an issue.
With that commitment I'd be open to adding it to CI on a probationary basis, with the intention that it become permanent if everything works out.
A good start would be a PR that augments the connect_timeout check and then a separate, follow up PR that adds TruffleRuby to CI.  Does that sound like a plan?

@petergoldstein I'd certainly respond and I'm sure @eregon would as well. I don't want to blow this issue up, but please send me any languishing issues you've seen. We're pretty responsive to issues we know about.
Your plan sounds good. I've already worked up the changes for the connect_timeout. I'm going through the rest of the suite as well.


Generaged Logo

User Story
AS a freelance web developer,
I WANT to generate a simple logo for my projects,
SO THAT I don't have to pay a graphic designer.

Acceptance Criteria
GIVEN a command-line application that accepts user input,
WHEN I have entered input for all the prompts,
THEN an SVG file is created named `logo.svg`,
AND the output text "Generated logo.svg" is printed in the command line,
WHEN I open the `logo.svg` file in a browser,
THEN I am shown a 300x200 pixel image that matches the criteria I entered.

Complete. See PR https://github.com/nestibry/umnbc-mod10-svg-logo-maker/pull/10


Implemented battery voltage measurement for Heltec WiFi LoRa 32 V3

ADC input switch (active low) controlled by GPIO37
ADC input at pin A0 / GPIO1 (see https://github.com/espressif/arduino-esp32/blob/master/variants/heltec_wifi_lora_32_V3/pins_arduino.h)
Voltage divider  R17=100k, R14=390k => 100k / (100k + 390 k) => UBATT_DIV = 0.2041;

Hi @matthias-bs,
i'll try to do some test in the next few days.
If you need specific test, let me know.
Davide

@evon800c Could you please check the battery voltage measurement with and without a battery? I'm not sure if VBAT equals VUSB / VDD_5V in the latter case.

Hi, @matthias-bs
Could you please tell me the pins and headers (j3/j2) where you want me to take the measurement?
https://resource.heltec.cn/download/WiFi_LoRa_32_V3/HTIT-WB32LA(F)_V3.png
I imagine that the battery is the one connected to the connector below.
davide

Hi @evon800c ,
the battery connector is a white JST connector on the bottom side of the PCB.

If unconnected, the supply voltage from USB should be reported correctly and the device should not enter sleep mode immediately for battery deep-discharge protection.
If a battery (or lab power supply with an appropriate voltage) is connected, this should be measured correctly, too.

The second case can only be tested if USB is not connected (otherwise you will still see the voltage coming from USB), which means you cannot check it in the debug output. Instead you have to check the LoRaWAN uplink payload.
I have recently added some documentation and the payload formatters, so you can hopefully use this without too much effort.
Best regards and a happy May Day,
Matthias

Hi, @matthias-bs
you have perfectly described what i have in mind.
I'll try to explain what is my lab environment at the moment. I have 2 heltec board with the same code, that are in power on. Both of them are receiving data from the same weather station. I'm doing some test to understand the better way to manage the energy... batteries, solar power panel size and and so on.
Both boards are not connected to pc usb, so as you correctly say, i can't see any info from debug side. I observe data only from uplink "supply_v" field.
node 1
is connect with usb to power line, has no battery attached and as you can see from image 1 has more or less the same supply_v value ~ 3.9V, on my tester i see 4118/9mv.
node 2
is connect with jst board connector to a 18650 (3.7V 2600mh), has no other external power atteched. and as you can see from image node 1 the value go down as i expected.
During the night at ~4:00 AM change the sleeping time to 900s.
From my point of view, all is working fine.
At "2024-05-02 11:45:45 GMT+2" the uplink supply_v show 3325, while on tester i can see 3516, i suppose that some adjust is need to be done.
I have attached the usb supply on node 2, also with battery attached (this board can charge the battery when powered with usb)
on tester i can see 3890 in increasing. I'm waiting for other uplink value to read the supply_v value.
At "2024-05-02 12:00:58 GMT+2" the uplink supply_v show 3995, while on tester i can see 4112.
The new voltage level permit to change sleep value and as we can see in the images ... supply_v increase as expected.
At "2024-05-02 13:44:58 GMT+2" the uplink supply_v show 4020, while on tester i can see 4196.
I hope this information can be useful to you. For any other test and/or consideration, i'm here.
Thanks a lot Davide
image 1

image 2

image 3

Hi @evon800c,
thank you very much for testing! The difference in voltage measurements between the ADC readings and your tester is a little bit concerning. 100...200mV difference means a lot when measuring a li-ion battery voltage. I think the usual effects like tolerances and voltage drop across the supply connections are not big enough to cause such a difference.
Maybe this is caused by the weird implementation of the voltage divider as described in https://github.com/matthias-bs/BresserWeatherSensorLW/issues/4#issuecomment-2070626966. If this is the case, the accuracy could be improved by using a lower attenuation of the ADC input.
Best regards,
Matthias
BTW: You seem to use InfluxDB & Grafana for processing and displaying the data. If you like, you could add a short tutorial on how to set this up to the project...

Hi @matthias-bs,
I don't know if it can be useful... but I did some tests by varying the attenuation by inserting "analogSetPinAttenuation(ADC_CTRL, ADC_XXdb)" before the "delay (100)" in the reading of the value for the "heltec".
I report the values detected. they are not very precise but they can be a starting point.
ADC_0db    multimeter=4151 supply_v=4065 diff=86
ADC_2_5db  multimeter=4162 supply_v=4088 diff=74
ADC_6db    multimeter=4157 supply_v=3972 diff=185
ADC_11db   multimeter=4157 supply_v=3935 diff=222

cheers, Davide

Hi @evon800c ,
great finding! I thought it were more complicated. I'll add it in the next release!
Thanks and have a nice evening!
Matthias

Should be analogSetPinAttenuation(PIN_ADC_IN, ADC_0db), right?

yes correct,
I set analogSetPinAttenuation(ADC_CTRL, ADC_2_5db); //ADC_2_5db, ADC_6db, ADC_11db to remeber the other possible values.
There is also another command "analogSetAttenuation(ADC_2_5db);" that can be used in the same way, but in that case the attenuation are applied to all pin

Hmm, I mean it should be applied to the ADC input pin, not the ADC control pin (which is just used as digital output to switch the MOSFET between VBAT and the ADC input).
I just added the line to the main branch.

mmmm correct


9318 DEV Add migration query to deprecate AWS_IAM integration in master_integrations.sql

https://github.com/Shippable/pm/issues/9318

This is complete.
Closing.


Implement a setup_logger function

Currently, a user has to manually set up a logger function. For example:
def setup_logger(level=logging.INFO) -> None:
    """Setup the logger from the openeo_gfmap package to the assigned level."""
    global pipeline_log
    pipeline_log = logging.getLogger("pipeline_sar")

    pipeline_log.setLevel(level)

    stream_handler = logging.StreamHandler()
    pipeline_log.addHandler(stream_handler)

    formatter = logging.Formatter("%(asctime)s|%(name)s|%(levelname)s:  %(message)s")
    stream_handler.setFormatter(formatter)

    # Exclude the other loggers from other libraries
    class ManagerLoggerFilter(logging.Filter):
        """Filter to only accept the OpenEO-GFMAP manager logs."""

        def filter(self, record):
            return record.name in [pipeline_log.name]

    stream_handler.addFilter(ManagerLoggerFilter())

We could provide a basic setup_logger function like this in GFMap, such that the user only needs to specify the loglevel.

I might be missing some context, but some quick feedback
global pipeline_log

It shouldn't be necessary to use globals here.
logging.getLogger("pipeline_sar") will return the same object even if called from different places, so no need to pass things around with globals.
That ManagerLoggerFilter pattern looks a bit dangerous because it will suppress everything (warnings and errors) from other components, which might hide actual problems.

I think something like the following has the same intent, but will not hide warnings/errors:
import logging

logging.basicConfig(level=logging.INFO)  # you can also specify a custom format here
# Set default log level to warning ...
logging.getLogger().setLevel(logging.WARNING)
# ... but use INFO level for our own logs
logging.getLogger("pipeline_sar").setLevel(logging.INFO)


[CP] Please partially merge #17f62d3f3ae56a1d76cbcb4410ea0ca884677c45 into stable channel

commit(s) to merge: 17f62d3f3ae56a1d76cbcb4410ea0ca884677c45
merge instructions: https://dart-review.googlesource.com/c/sdk/+/148127 - to limit cherry pick to a single line flag change
reason: This change addresses regression in stack trace quality on Flutter stable channel - without this change users will see "optimized out" instead of function names for some of the frames in the stack trace.
/cc @dgrove @kevmoo @mit-mit @whesse @athomas @vsmenon  @frankyow @pcsosinski

/cc @mkustermann @sstrickl

Approved: regression, low risk
Wait for join approval, do not merge yet

flutter eng approval +1

closing


Closes #36: Ensure formData are properly validated when schema is updated

Refs and supersedes #36.
@fangj, could you please check the diff and see if that addresses your initial issue? Thanks!

Very good, r+ :)


Does GRUtopia support multi-agent interaction?

Great work！I'm inquisitive if the GRUtopia supports multi-agent interactions?

Hi @zchoi,
Thank you for your interest in our project!
We currently offer a framework for customizing a multi-agent scenario, which you can refer to in the example provided at https://github.com/OpenRobotLab/GRUtopia/blob/main/demo/h1_npc.py. This example should serve as a helpful starting point for creating your own multi-agent interactions.
Please feel free to reach out if you have any questions or need further assistance.

Got it. 👍


Weird behavior in vi mode

In insert mode, the plugin doesn't react to delimiters at all.
In normal mode, it works, but makes fish go in insert mode while somehow not updating my prompt to reflect that...

In this gif, you can see the Starship prompt which normally points to the left in normal mode and to the right in insert mode.
What I would expect:
Plugin doesn't react in normal mode and doesn't switch modes.
Plugin works in insert mode.

@GitSquared Thanks so much for reporting. Just fixed this now. We were using --sets-mode (which sets the mode), instead of --mode, which specifies the bind mode that the bind will be used in (what we want). 💯
You can update to the latest deployment using:
$ fisher update jorgebucaran/autopair.fish

Thanks, the fix works great! And thanks for making Fisher, too ;)

Thank you for using it!