[BUG] Errors compiling on Windows

Bug description:
I'm getting errors while building-without-installer the default configuration in Windows.
How to reproduce:
Run .\build.ps1.
Expected behavior:
No errors.
Errors and logs:
Here's the first error that I get:
121>tsduck\src\libtsduck\plugins\plugins\tsAbstractDuplicateRemapPlugin.cpp(69,5): error C2672: 'ts::Args::getIntValues': no matching overloaded function found [tsduck\scripts\msvc\tsducklib.vcxproj]
   tsduck\src\libtsduck\base\app\tsArgs.h(936,14): message : could be 'void ts::Args::getIntValues(ts::CompactBitSet<BITS,nullptr> &,const ts::UChar *,bool) const' (compiling source file tsduck\src\libtsduck\plugins\plugins\tsAbstractDuplicateRemapPlugin.cpp) [tsduck\scripts\msvc\tsducklib.vcxproj]
   tsduck\src\libtsduck\plugins\plugins\tsAbstractDuplicateRemapPlugin.cpp(69,5): message : 'void ts::Args::getIntValues(ts::CompactBitSet<BITS,nullptr> &,const ts::UChar *,bool) const': could not deduce templateargument for 'ts::CompactBitSet<BITS,nullptr> &' from 'ts::TSPacketLabelSet' [tsduck\scripts\msvc\tsducklib.vcxproj]
   tsduck\src\libtsduck\base\app\tsArgs.h(921,14): message : or       'void ts::Args::getIntValues(std::bitset<_Bits> &,const ts::UChar *,bool) const' (compiling source file tsduck\src\libtsduck\plugins\plugins\tsAbstractDuplicateRemapPlugin.cpp) [tsduck\scripts\msvc\tsducklib.vcxproj]
   tsduck\src\libtsduck\plugins\plugins\tsAbstractDuplicateRemapPlugin.cpp(69,5): message : 'void ts::Args::getIntValues(std::bitset<_Bits> &,const ts::UChar *,bool) const': could not deduce template argument for'std::bitset<_Bits> &' from 'ts::TSPacketLabelSet' [tsduck\scripts\msvc\tsducklib.vcxproj]
     tsDebugPlugin.cpp
   tsduck\src\libtsduck\base\app\tsArgs.h(906,14): message : or       'void ts::Args::getIntValues(std::set<INT,std::less<_Ty>,std::allocator<_Ty>> &,const ts::UChar *) const' (compiling source file tsduck\src\libtsduck\plugins\plugins\tsAbstractDuplicateRemapPlugin.cpp) [tsduck\scripts\msvc\tsducklib.vcxproj]
   tsduck\src\libtsduck\plugins\plugins\tsAbstractDuplicateRemapPlugin.cpp(69,5): message : 'void ts::Args::getIntValues(std::set<INT,std::less<_Ty>,std::allocator<_Ty>> &,const ts::UChar *) const': could not deduce template argument for 'std::set<INT,std::less<_Ty>,std::allocator<_Ty>> &' from 'ts::TSPacketLabelSet' [tsduck\scripts\msvc\tsducklib.vcxproj]
   tsduck\src\libtsduck\base\app\tsArgs.h(894,14): message : or       'void ts::Args::getIntValues(std::vector<CHARTYPE,std::allocator<_Ty>> &,const ts::UChar *) const' (compiling source file tsduck\src\libtsduck\plugins\plugins\tsAbstractDuplicateRemapPlugin.cpp) [tsduck\scripts\msvc\tsducklib.vcxproj]
     tsDropOutputPlugin.cpp
   tsduck\src\libtsduck\plugins\plugins\tsAbstractDuplicateRemapPlugin.cpp(69,5): message : 'void ts::Args::getIntValues(std::vector<CHARTYPE,std::allocator<_Ty>> &,const ts::UChar *) const': could not deduce template argument for 'std::vector<CHARTYPE,std::allocator<_Ty>> &' from 'ts::TSPacketLabelSet' [tsduck\scripts\msvc\tsducklib.vcxproj]

Environment:

OS: Windows
OS version: 10
TSDuck full version: 3.37-3670 (latest tag)
Installation type: Rebuilt binary

Additional information:
Visual Studio Professional 2022 (64-bit) - LTSC 17.6.

On an up-to-date Windows system, TSDuck tag v3.37-3670 compiles correctly. Executing build.ps1 compiles the Win64 and Win32 versions without problem. I just tested it.
The configuration is Windows 11 with Visual Studio 2022 Community Edition, version 17.10.3, containing MSVC 19.40.33811.00.
I don't think that Windows 10 vs. 11 matters. But the MSVC compiler is very unstable. Over the years, I have seen many bugs being created, then fixed. Especially when it comes to cryptic overloading interpretations as seen in your error messages.
When TSDuck version 3.37-3670 was built (official build), it used MSVC 19.39.33522.00 (see tsversion --version=all), which is not much different from the latest one. I don't remember which Visual Studio version it was. The compiler can only identify itself during the compilation, not the Visual Studio environment.
From Visual Studio, it is difficult to get the real compiler version. In your environment, get the value of the macro _MSC_FULL_VER (type it in a source file and hover over it to display the value). For instance, for MSVC 19.40.33811.00, _MSC_FULL_VER is 194033811.
If your version is lower than 193933522, the version which was used to build TSDuck v3.37-3670, you probably have a compiler bug and you need to upgrade to the latest version. As a rule of thumb, I have seen so many bugs in MSVC that I recommend to always upgrade to the latest version. Except in the rare cases where the latest version introduces a new bug. It happens...
Otherwise, the same TSDuck source code compiles quite well with all versions of clang and gcc versions 11 and higher (again, gcc versions 8 to 10 had bugs which prevented the compilation of recent versions of TSDuck).
I remove the "bug" tag since this is not a TSDuck bug.

For _MSC_FULL_VER, I get 193632544 for LTSC 17.6.11. Upgrading to the latest on LTSC, 17.6.16, yields 193632546 for _MSC_FULL_VER, so not much help.
I have a requirement to stay on LTSC, so what do you suggest in this case?

BTW, if I use the prebuilt x64 Release library from the installer, then I get this error when linking in a test app:
error LNK2001: unresolved external symbol "private: static class ts::CerrReport * ts::CerrReport::_instance" (?_instance@CerrReport@ts@@0REAV12@EA) fatal error LNK1120: 1 unresolved externals
Could this also be related to the compiler version, or is it something else that I'm missing? I doubt I should define that static myself.

I have a requirement to stay on LTSC, so what do you suggest in this case?

If you have the requirement to stay with a buggy compiler instead of one that works, there is nothing I can do for you. I have worked long enough in the industry to understand that such requirement may exist. It is difficult to make management understand that such decision is only counter-productive.
At best, you could install an up-to-date compiler on some other PC, even a personal one, and build an installer (and portable one if you need it). And then install these installers on your dev systems.

Having the prebuilt TSDuck 3.37-3670 installed, I can link a sample test application which uses CerrReport. Moreover, the symbol which is in error for you is actually exported by tsduck.dll:
PS C:\> tsversion
3.37-3670
PS C:\> dumpbin /exports "C:\Program Files\TSDuck\bin\tsduck.dll" | Select-String _instance@CerrReport@ts@@0REAV12@EA

       7620 1DC3 011BD340 ?_instance@CerrReport@ts@@0REAV12@EA

So, the symbol is exported. I don't think that the compiler version is to blame since the right symbol is looked for.

Try the dumpbin command on your system. To check that the installation is correct.

Yes, it's there in the DLL:
dumpbin /exports "tsduck.dll" | grep _instance@CerrReport@ts@@0REAV12@EA
       7620 1DC3 011BD340 ?_instance@CerrReport@ts@@0REAV12@EA

However, I don't think the liker looks at the DLL, but only at the LIB. And for that, I get:
dumpbin /exports "tsduck.lib" | grep _instance@CerrReport@ts@@0REAV12@EA
                  ?_instance@CerrReport@ts@@0REAV12@EA (private: static class ts::CerrReport * ts::CerrReport::_instance)

@mihaicodrean

That could work, thanks for the idea, although another approach is to understand what exactly is the MS compiler missing and assist it.

I fully support the idea of understanding first, instead of trying something else. However, your have two distinct issues.

You definitely need to understand why you have the missing symbol during the link. This is not normal, even with your compiler.
However, the other problem, the inability to find the right overload resolution, is clearly a bug in the compiler C++ front end. This kind of thing cannot be fixed without scrapping the buggy compiler and get a fixed one.

In the second case, you get the error while compiling TSDuck. If you rebuild it elsewhere with a good compiler and install it, you should be safe on the short term. However, the overload failure is on common classes of the TSDuck public API. There is still a risk that you run into a similar problem some day with your applications.
From my experience, the MSVC compiler can be extremely dangerous. Over the years, I ran into multiple compilation bugs. When they are obvious, an error message and a failing compilation, as you get, it is not too dangerous because you see it. However, in at least one occurrence, I got a silent code generation bug. This is the developer's nightmare, your source code is correct, your binary works with other compilers and on other OS, but it fails on Windows. After I reported that bug, it took one year for MS to start working on it, and an additional year to get a fix. This is why I consider MSVC as a time bomb and I absolutely recommend to upgrade to the latest version.

@mihaicodrean

However, I don't think the liker looks at the DLL, but only at the LIB. And for that, I get:

Good point. But, as you observed, the symbol is there and the linker should find it.

I'm actually not using CerrReport directly, but have only added a call to ts::IPInitialize().*

OK, but ts::IPInitialize() uses an optional parameter which defaults to CERR, a macro which expands to the CerrReport singleton instance. So, your binary code references it.

I fully support the idea of understanding first, instead of trying something else.

I think the compiler fails to determine the value of the template argument N from the CompactBitSet<N> parameter.
template <std::size_t N>
void ts::Args::getIntValues(CompactBitSet<N>& values, const UChar* name, bool defValue) const

For the call:
getIntValues(_setLabels, u"set-label");

_setLabels is TSPacketLabelSet, which is:
using TSPacketLabelSet = CompactBitSet<32>;

So if I change the call to the following, then at least IntelliSense is happy:
getIntValues<32>(_setLabels, u"set-label");

Interesting. So, I think we all agree to call that a "compiler bug", right ?

So, I think we all agree to call that a "compiler bug", right ?

I have a feeling that the CompactBitSet is missing something, because there are no issues with bitset, for example:
using PIDSet = std::bitset<PID_MAX>;
PIDSet             _pids {};
args.getIntValues(_pids, u"pid");

template <std::size_t N>
void ts::Args::getIntValues(std::bitset<N>& values, const UChar* name, bool defValue) const

Or vice-versa actually, something in CompactBitSet that the compiler doesn't quite understand. For example, if I remove the following from the template definition, then the compiler is pleased:
typename std::enable_if<(BITS > 0)>::type* = nullptr

I have a feeling that the CompactBitSet is missing something, because there are no issues with bitset, for example

There must be something different but I wouldn't say missing. The idea of TSDuck dev is to test on each push on 3 different OS, 3 compilers, 2 levels of C++ standard (17 and 20), 2 architectures (Intel and Arm), 32000 assertions in unit tests, 2000 high-level tests. So, when everything pass everywhere, we may have some confidence that the code is correct, both on a language and functional perspective. If you add that recent versions of MSVC have changed their behaviour and now correctly resolve the overloading, that clearly means that the component which has something missing is the compiler. Whether it is called "long term support contract" is just the demonstration that LTSC is just BS***

I tend to agree that this is probably a compiler bug after all, because the underlying cause seems to be the condition in the enable_if construct, (BITS > 0). If I change that to (1 > 0), for example, then the type is found.

Wow, I cannot believe how many bug reports are there for SFINAE / enable_if for MSVC. Case closed then.
What about the issue with the singleton? Shall I create another issue for it, to discuss it further?

I cannot believe how many bug reports are there for SFINAE / enable_if for MSVC.

😆😆😆 I told you, MSVC is crap...

What about the issue with the singleton? Shall I create another issue for it, to discuss it further?

Let's continue here.

Did you recompile your test application after installing the new TSDuck version?
Is there many other references to TSDuck in the application? What about dumpbin /symbols on the application object file? Especially dumpbin /symbols xxx.obj | Select-String _VERSION_.
Can you reproduce this on a new empty application referencing TSDuck? Just using IPInitialize for instance.

Did you recompile your test application after installing the new TSDuck version?

Yes. I even tried with a local build, once I removed the problematic-for-my-compiler std::enable_if.

Is there many other references to TSDuck in the application?

No, I'm just starting to use TSDuck, and stumbled upon that linker error.
BTW, the issue is not with just that singleton, but with any of them, for example ts::UID::Instance() triggers a similar complaint:
error LNK2001: unresolved external symbol "private: static class ts::UID * ts::UID::_instance" (?_instance@UID@ts@@0REAV12@EA)

What about dumpbin /symbols on the application object file? Especially dumpbin /symbols xxx.obj | Select-String VERSION.

I don't get "VERSION" there.

Can you reproduce this on a new empty application referencing TSDuck? Just using IPInitialize for instance.

I'll try that evetually.

My bad - I haven't had "tsduck.props" referenced properly. With that addressed, the linker error(s) are gone. Thanks for all the help & patience!

Did you follow the instructions from here?
Namely, did you reference tsduck.props in your VS project file?

Yes, of course. Strangely, that error does not occur in Release|x86 with my local build of TSDuck, but only in Release|x64, with the library provided by the public installer.

I am confused now by the timeline of messages in this thread, as if they were presented in the wrong order. What is the status now? Any remaining error with tsduck.props? What does work and what does not?

There are three items that we have discussed in this umbrella issue:

[SOLVED] The VS 2022 17.6 LTSC compiler bug when using std::enable_if in one use case, that I removed to be able to build the 32-bit TSDuck
[SOLVED] The linker issue with the singletons, that was due to my incorrect import of tsduck.props
The STL issue when including "tsUString.h", that happens in x64, but not x86.

The STL issue when including "tsUString.h", that happens in x64, but not x86.

Is this the prebuilt binary for x64 vs. your build for x86? The two were built using different compilers (including a buggy one).
Or are the two from your builds? In which case it is a platform issue, not a compiler issue.
The important point is that the missing symbol of a private method in std::basic_string. So, this not something that can be called by you or TSDuck. It must be called from an inline or template method in the MSVC header files for std::basic_string. And it must be declared in the same header as basic_string.
In my case, this is header xstring in C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.40.33807\include
I do not find any reference to a private method named _Start_element_lifetimes here.
You could probably look into your headers and you will probably find this private method. But that would mean a major runtime incompatibility between your compiler and subsequent versions.
That would not be surprising (I told you it was crap). This recently emerged as a major breakage of the GitHub CI Windows runners (still not fixed), putting thousands of developers in trouble. The problem was a defective and inconsistent runner image by GitHub folks. But the upper root cause was a major incompatibility between versions of the MSVC runtime.

My recommendations, in this order:

Drop so-called LTSC versions of the MSVC compiler and stick to the latest versions. Always. Stay up-to-date.
Drop the whole thing and move to Linux or macOS. The clang compiler is extremely robust. GCC is fine too, but is ageing.

Probably not realistic in your case, but quite pragmatic.

About the major GitHub runner breakage because of the mess which was created by incompatible versions of the C++ runtime, you may read the following reports:
https://github.com/actions/runner-images/issues/10004
https://github.com/actions/runner-images/issues/10020
https://github.com/actions/runner-images/issues/10055
Some of them were closed but the problem remains at least on JNI code (affecting TSDuck as well).
You may also find hundredths of reports affecting that many repositories, which reference the issues above. The amount of lost troubleshooting time over hundredths of organizations is above several men x years. And the problem is not over yet.
All because of the MSVC runtime crap...

Is this the prebuilt binary for x64 vs. your build for x86?

Tried with both the prebuilt x64, and also with my own x64 build - same deal. My x86 build is fine.

Or are the two from your builds? In which case it is a platform issue, not a compiler issue.

No, see above. But to confirm, my builds match the Platform Toolset and the Windows SDK Version for both the TSDuck library & the test application.

In my case, this is header xstring in C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.40.33807\include

Mine is: c:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.36.32532\include\

I do not find any reference to a private method named _Start_element_lifetimes here.

It looks like this on my end:
private:
    static constexpr void _Start_element_lifetimes(_Elem* const _Ptr, const size_type _Size) {
        // Start element lifetimes to avoid UB. This is a more general mechanism than _String_val::_Activate_SSO_buffer,
        // but likely more impactful to throughput.
#if _HAS_CXX20
        if (_STD is_constant_evaluated()) {
            for (size_type _Idx = 0; _Idx < _Size; ++_Idx) {
                _STD construct_at(_Ptr + _Idx);
            }
        }
#else // ^^^ C++20-or-later / pre-C++20 vvv
        (void) _Ptr;
        (void) _Size;
#endif // _HAS_CXX20
    }

The test application's obj contains these symbols for the x64 build:
External    | ?_Start_element_lifetimes@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@$$FCAXQEAD_K@Z (private: static void __cdecl std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::_Start_element_lifetimes(char * const,unsigned __int64))
External    | __t2m@?_Start_element_lifetimes@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@CAXQEAD_K@Z ([T2M] private: static void __cdecl std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::_Start_element_lifetimes(char * const,unsigned __int64))
External    | __m2mep@?_Start_element_lifetimes@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@$$FCAXQEAD_K@Z ([M2MEP] private: static void __cdecl std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::_Start_element_lifetimes(char * const,unsigned __int64))
External    | __mep@?_Start_element_lifetimes@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@$$FCAXQEAD_K@Z ([MEP] private: static void __cdecl std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::_Start_element_lifetimes(char * const,unsigned __int64))

Notice how they all have char * const as the first parameter, as opposed to char16_t * const from the error message.

Interesting.
Your version of the compiler and its header files use a static method which is no longer used in subsequent versions. OK, why not. Since this is a template class, with template parameters in the profile of the method, the compiler is supposed to generate the code for that method alongside the application (but shall include only one instance in the link).
The problem is that a header file declares and defines a template method and the corresponding instance is not generated. That is a compiler bug. That's all.
I am not sure if the difference you noted on parameter types matters. The ts::UString class is just an enriched subclass of std::u16string, which uses char16_t* pointers. The symbols which are referenced in your object file (using char* parameters) are not declared as unresolved by the linker. So, this template code must have been generated somehow.
The other problem with other symbols is probably different. When the linker (or the linker-support part of the compiler) generates the template instance, it apparently forget to generate the missing method.
The fact that you don't have the problem with x86 is also interesting. If you look at the gigantic mess of the Windows GitHub runners with the MSVC runtime (see links in my previous post), we see the same symptom: no problem with x86. It seems that there is no longer any change on x86 (quite understandable since this is an obsolete target) and that all changes occur on x64. With a very bad change management policy, since it creates a lot of mess.
I can only have the same recommendation again: get away from that version of the compiler, use the latest version, and stay up-to-date all the time. Not only for TSDuck, for your own applications as well.

Just for reference, that method was added here: https://github.com/microsoft/STL/commit/72229ffd5bf3d5a74e3d68ebed00a0919eb7f071 and removed here: https://github.com/microsoft/STL/commit/29fc1c9158404a09dc2a8296208405f9a3115711.

And there is a bug in the compiler, failing to properly generate the instance code, at least in some cases. So, removing the static template may have have only hidden the compiler bug (unless an independent fix in the compiler was also added in the meantime).


Backport UI support for AssociatePublicIPAddress to 2.1

Backport UI support for AssociatePublicIPAddress to 2.1:  https://github.com/rancher/rancher/issues/16090

will be ready for test when new rc is created >v2.1.1-rc2

Available in v2.1.1-rc3

Version - 2.1.1 rc5
Verified fixed


Validation incorrectly indicates that input html tag cannot be self closing

Info

Platform: Windows 8
Vetur version: 0.8.6
VSCode version: 1.13.1

Problem
Validation incorrectly indicates that input html tag cannot be self closing

https://github.com/vuejs/eslint-plugin-vue/pull/54

Fixed in https://github.com/octref/vetur/pull/294


Looking for a contributor to configure the webpack setup

While I'm continuing the development stage of modules, I'm looking for someone who will configure the @webpack for the build setup. Who would I assign this task to him?

I'll create the bundle setup next week.

This is done via webpack configuration


Update dependencies

This fixes a dependabot alert about a vulnerability in gatsby-plugin-mdx

Approval is hold.
With this change, build(npm start) is failed. need to figure out and fix first then merged.

I think it's not a good idea to update all dependent package version at this time. Issues are keep coming out from dependent package. not easy to fix at this time.
It's just documentation page. so Why don't we just updating gatsby-plugin-mdx version only to 2.14.1
(3.x major version also cause a problem.. )
only updating that  package,  I confirmed the build work properly.

Already done in a different PR. Closing...


BKSF mapper fails on LiH example

Environment

Qiskit Nature version: 0.3.0
Python version:
Operating system:

What is happening?
BKSF mapper fails on LiH example due to mult missing from SparsePauliOp:

~/mambaforge/envs/qiskit/lib/python3.8/site-packages/qiskit_nature/converters/second_quantization/qubit_converter.py in _map(self, second_q_op)
    339
    340     def _map(self, second_q_op: SecondQuantizedOp) -> PauliSumOp:
--> 341         return self._mapper.map(second_q_op)
    342
    343     def _two_qubit_reduce(

~/mambaforge/envs/qiskit/lib/python3.8/site-packages/qiskit_nature/mappers/second_quantization/bksf.py in map(self, second_q_op)
     47
     48         edge_list = _bksf_edge_list_fermionic_op(second_q_op)
---> 49         sparse_pauli = _convert_operator(second_q_op, edge_list)
     50
     51         ## Simplify and sort the result

~/mambaforge/envs/qiskit/lib/python3.8/site-packages/qiskit_nature/mappers/second_quantization/bksf.py in _convert_operator(ferm_op, edge_list)
    123                 # Note that h2_pqrs is not divided by 2 here, as in the aqua code
    124                 sparse_pauli = _add_sparse_pauli(
--> 125                     sparse_pauli, _number_excitation(edge_list, p, q, r, s, h2_pqrs)
    126                 )
    127             else:

~/mambaforge/envs/qiskit/lib/python3.8/site-packages/qiskit_nature/mappers/second_quantization/bksf.py in _number_excitation(edge_list, p, q, r, s, h2_pqrs)
    343         a_pr = _edge_operator_aij(edge_list, p, r)
    344         a_pr = -a_pr if r < p else a_pr
--> 345         qubit_op = (a_pr * b_r + b_p * a_pr) * (id_op - b_q)
    346         final_coeff = 1j * 0.25
    347     else:

TypeError: unsupported operand type(s) for *: 'SparsePauliOp' and 'SparsePauliOp'

How can we reproduce the issue?
Just follow along here:
https://github.com/IBM-Quantum-Technical-Enablement/Fraunhofer-Dec-13-2021/blob/main/applications/qiskit-nature.ipynb
and replace JW mapper with BKSF (BK and Parity mappers work).
What should happen?
Should work
Any suggestions?
No response

It looks like the test code for BKSF does not include a Hamiltonian that multiplies two SparsePauliOp. This is called composition and uses the symbol &. I'll make a PR to fix this.


[Bug] [Module Name] Bug title

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
Until now I still haven't trans data from mysql to hive;
then i tried  mysql to hdfs，Although the process is complex, it is effective；
but i have to refresh table command ;
the  question: when I import using hdfs, do I need to import hive again like sqoop?
SeaTunnel Version
2.1.0
SeaTunnel Config
normal

Running Command
success

Error Exception
xx

Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Please provide your config, and execption message

Closed due to no response.


Fix custom Equal assertion so that numeric types aren't so finicky

Currently statements like this fail:
func foo() float24 {
  return 24.0
}
assert.Equal(foo(), 24)

Use reflect to figure out the type of the actual value and cast the expected value to that type.
This will cause the previous statement to pass.

This is working, but the custom assertions have a variety of other problems now too. Most notably showing the library line number and no stack trace on assertion failures.


Allow direct assignment of current user to conn

For applications that use addict, it is often useful to be able to create tests with a logged in user, without creating a session. With this change, if a test sets :current_user in conn.assigns, the plug does nothing, and the test will proceed as if :current_user is logged in.
It is assumed that this would only affect tests, as production application code would not be setting this.
This addresses (at least in part) issue https://github.com/trenpixster/addict/issues/84. Perhaps an example is still needed to better document this feature.

@tomfbiz have you tried using Plug.Test. init_test_session/2. Here's what I've been doing in the test setup:
user = %{ email<EMAIL_ADDRESS>name: "something" }
conn = Plug.Test. init_test_session(build_conn(), %{current_user: user})

Would this work for you? Maybe it's worth adding this to the documentation or adding a specific Addict helper?

@trenpixster Your solution is more elegant. No need for test specific code in production.
I'm closing this, but I do think that explanation of how to set up tests using Addict would be beneficial.
Maybe some additional helpers and tests in the sample app would solve the problem?
I could try to tackle that if you agree that is the way to go.


[Bug]: Firefox : Clicking on white space near any property on property pane do not focus it

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

Steps To Reproduce
On chrome and safari if we click on white space beside any property it focus on that property but the same do not happen on firefox. In firefox browser user has to click on the property for focus.
Use Case: If any user click on any property and try to use keyboard accessibility then user will face difference in UX on firefox.
Environment
Production
Version
Cloud

@vuiets Should we resolve this on Property pane improvement epic?

@aswathkk wondering if this is a design issue? Do we need a focus state for the Property Pane controls before we may pick this up?

@vuiets We need a design for the focus state for some components like the property title, copy button etc. I've created a separate issue for that.
This issue is more about inconsistencies in the firefox browser's behaviour.
In chrome, if we click on a white area near to property title and pressing Tab moves the focus to the property title. But, that's not the case in Firefox.

Sounds good. Let's pick this up as a part of #8845 | Property Pane Improvements 👍

@ankurrsinghal are you working on this right now?

@vuiets Checked on the latest version of Firefox (Version 98.0.2 (64-bit)) and not able to repro it currently.


Little changes to make life easier working Prefect 1.3

This change implements support for a name parameter to @materialize tasks which makes its way into task names before the Prefect flow is constructed.
It is not a big enough change to release separately and mention it in CHANGELOG.rst.
Checklist

[x] Added a CHANGELOG.rst entry

Port for postgres is changed in docker-compose.yml used in testing from 5432->6543 in order to avoid collision with the postgres database started by prefect server start


cmake: add optional static and shared build options

refs #771

many thanks, this looks like a good and flexible approach.
it also does not require any user changes, which is good for Juha's project.

I think we can merge this now ...

I pulled latest re:
/usr/src/libbaresip-android$ grep SHARED re/CMakeLists.txt
option(LIBRE_BUILD_SHARED "Build shared library" ON)
if(LIBRE_BUILD_SHARED)
  add_library(re-shared SHARED $<TARGET_OBJECTS:re-objs>)
if(LIBRE_BUILD_SHARED)

and made libre Android build:
/usr/src/libbaresip-android$ make libre.a
cd re && \
rm -rf build && rm -rf .cache && mkdir build && cd build && \
cmake .. \
	-DANDROID=ON -DANDROID_PLATFORM=23 -DCMAKE_SYSTEM_NAME=Android -DCMAKE_SYSTEM_VERSION=23 -DCMAKE_TOOLCHAIN_FILE=/opt/Android/ndk/25.2.9519653/build/cmake/android.toolchain.cmake -DANDROID_ABI=arm64-v8a -DCMAKE_ANDROID_ARCH_ABI=arm64-v8a -DCMAKE_SKIP_INSTALL_RPATH=ON -DCMAKE_C_COMPILER=aarch64-linux-android23-clang -DCMAKE_CXX_COMPILER=aarch64-linux-android23-clang++ -DCMAKE_POSITION_INDEPENDENT_CODE=ON -DCMAKE_BUILD_TYPE=Release \
	-DCMAKE_FIND_ROOT_PATH="/opt/Android/ndk/25.2.9519653;/usr/src/libbaresip-android/openssl" \
	-DOPENSSL_VERSION_MAJOR=3 \
	-DOPENSSL_ROOT_DIR=/usr/src/libbaresip-android/openssl && \
cmake --build . --target re -j
-- The C compiler identification is Clang 14.0.7
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /opt/Android/ndk/25.2.9519653/toolchains/llvm/prebuilt/linux-x86_64/bin/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Performing Test COMPILER_SUPPORTS_WATOMIC
-- Performing Test COMPILER_SUPPORTS_WATOMIC - Success
-- Looking for backtrace
-- Looking for backtrace - not found
-- Could NOT find Backtrace (missing: Backtrace_LIBRARY)
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - not found
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- Found ZLIB: /opt/Android/ndk/25.2.9519653/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/lib/aarch64-linux-android/23/libz.so (found version "1.2.12")
-- Found OpenSSL: /usr/src/libbaresip-android/openssl/libcrypto.a (found suitable version "3.1.0", minimum required is "1.1.1")
-- Looking for arc4random
-- Looking for arc4random - found
-- Looking for syslog.h
-- Looking for syslog.h - found
-- Looking for getopt.h
-- Looking for getopt.h - found
-- Looking for unistd.h
-- Looking for unistd.h - found
-- Looking for res_ninit
-- Looking for res_ninit - not found
-- Looking for thrd_create
-- Looking for thrd_create - not found
-- Looking for accept4
-- Looking for accept4 - found
-- Looking for epoll_create
-- Looking for epoll_create - found
-- Looking for kqueue
-- Looking for kqueue - not found
-- Looking for sys/prctl.h
-- Looking for sys/prctl.h - found
-- Could NOT find Backtrace (missing: Backtrace_LIBRARY)
-- Configuring done
-- Generating done
-- Build files have been written to: /usr/src/libbaresip-android/re/build
...
gmake[4]: Entering directory '/usr/src/libbaresip-android/re/build'
[  1%] Building C object CMakeFiles/re-objs.dir/src/async/async.c.o
...

[100%] Building C object CMakeFiles/re-objs.dir/rem/vidmix/vidmix.c.o
gmake[4]: Leaving directory '/usr/src/libbaresip-android/re/build'
[100%] Built target re-objs
gmake[4]: Entering directory '/usr/src/libbaresip-android/re/build'
[100%] Linking C static library libre.a
gmake[4]: Leaving directory '/usr/src/libbaresip-android/re/build'
[100%] Built target re
gmake[3]: Leaving directory '/usr/src/libbaresip-android/re/build'

And the result was that (like before) only static lib was build.  I don't need shared libs, but I am just wondering.

hi Juha,
in your cmake command line options you can now select which type of libs your want to build:
option(LIBRE_BUILD_SHARED "Build shared library" ON)
option(LIBRE_BUILD_STATIC "Build static library" ON)

$ cmake -DLIBRE_BUILD_SHARED=OFF .
$ make

i.e. you can skip the target if you want.


[Feature Request] Add "Leaked" Blue Vine

Surprisingly, I haven't seen a mod recreate that conceptual plant since the release, but it would seem fitting for a mod as this. Any consideration to include the blue morning glory vine from that "leaked" image?

@xenornithos come on😭😭😭😭😭😭😭


feat(lint): add eslint config and initial ci config

add eslint and use standard style
ignore f7 folder for now, because it has standalone config in f7 repo, if we need to custom it for further enhancement, we could open it
fix some code style errors
add a simple config for trivas build, just run linter and dev-build

Thanks ❤


Implement blockdownloader for p2p

The BlockDownloader is responsible for handling download requests
https://github.com/paradigmxyz/reth/blob/83cbcb99aebcb8bdcfce549ab2912e033b402f51/crates/engine/tree/src/download.rs#L8-L8
this new trait, effectively does the same as a subset of the existing type:
https://github.com/paradigmxyz/reth/blob/83cbcb99aebcb8bdcfce549ab2912e033b402f51/crates/consensus/beacon/src/engine/sync.rs#L35-L39
minus the engine part:
https://github.com/paradigmxyz/reth/blob/83cbcb99aebcb8bdcfce549ab2912e033b402f51/crates/consensus/beacon/src/engine/sync.rs#L42-L43
so that the new type only needs:
https://github.com/paradigmxyz/reth/blob/83cbcb99aebcb8bdcfce549ab2912e033b402f51/crates/consensus/beacon/src/engine/sync.rs#L68-L68
TODO

add a standalone BlockDownloader struct with trait impl for the new engine design that only downloads blocks. most of the logic can be reused
we can duplicate this for new in the new engine/tree crate, not worth refactoring the existing code in EngineSyncController because we expect to remove all of this eventually.

hi, @mattsse , is this part of https://github.com/paradigmxyz/reth/issues/8213, will it implement the automatically manage the peers and decide to fetch/download block from the best peers.?

this will eventually be usuable for this feature yes.
currently this functionality is encapsulated in
https://github.com/paradigmxyz/reth/blob/de6332b51e9d4bdf9d3e75a1523ff1cdfb862686/crates/consensus/beacon/src/engine/sync.rs#L35-L35
the network implementation already manages the peers and decides where to download from


Updated simulator

Two things

Corrected small bug in integrate class. If someone used lsoda but not analytic_jacob defaults were not properly set.

Updated simulator class to shrink overhead for large number of simulations. Basically just moved function calls out of long loops.

Requesting merge with Lolab-VU/pysb branch.


A lot of files in assets folder

Aftr command execution, there are "all" CSS and JS files and also a lot of files from dependent assets. Is this normal?

It depends how have you configured bundles. Please check this article:
http://www.yiiframework.com/doc-2.0/guide-structure-assets.html#using-the-asset-command

I configured it exactly how it described in documentation. If you will see FileHelper's source code, you will find very strange behavior with file names filtering, which causes this problem


[VS Code] Joining collaboration session: The host's network conditions are poor or they are no longer connected to the Live Share cloud relay. Ask them to check their network conditions, restart the collaboration session, and try again.

Error:
Joining collaboration session: The host's network conditions are poor or they are no longer connected to the Live Share cloud relay. Ask them to check their network conditions, restart the collaboration session, and try again.
Steps to Reproduce:
1.
2.

Version Data

extensionName
VSLS

extensionVersion
1.0.614

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.36.1

platformName
Windows

platformVersion
10.0.18362

Closing this due to inactivity. Please reopen it if you’re still encountering the issue. Thanks!


Wrong formating highlights.

Hi I am using your extension on vscode with datamodel.prisma file.
Here is my schema and the formater is saying its not right.
type Link{
	id: ID! @id
	createdAt: DateTime! @createdAt
	description: String!
	url: String!
}

its puts a red line under type says model declaration need to be marked with word Model. this is not right.

Hi @ChiragThesia
This extension is meant to be used with Prisma 2 models. Please rename your file to datamodel.graphql and use https://marketplace.visualstudio.com/items?itemName=Prisma.vscode-graphql plugin for highlighting.


349 make nodeengine systemd compatible

Fixes #349

Tested both the systemd for NodeEngine and Net-Manager (PR 185) with AWX Testbed and manually. Works smoothly on VMs but fail on devices xavier1, xavier2, raspi4-base reporting the errors shown:

It seems that an absolute path is required for ExecStart and the service logs does not support the append keyword (this applies to both /etc/systemd/system/nodeengine.service and /etc/systemd/system/netmanager.service). As a workaround, using the following configuration seems to work (example for nodeengine.service):
[Unit]
Description=Oakestra NodeEngine Service
After=network.target
StartLimitIntervalSec=10
[Service]
Type=simple
Restart=always
RestartSec=5
User=root
ExecStart=/bin/nodeengined
StandardOutput=file:/var/log/oakestra/nodeengine.log
StandardError=file:/var/log/oakestra/nodeengine.log

[Install]
WantedBy=multi-user.target

NB: The file option overwrites the log file with each service start, while append adds new log entries to the existing file without overwriting.

@TheDarkPyotr what about now? It looks like its working on my side. Tested on a raspberry pi running on Debian GNU/Linux 11 (bullseye)

Error persisting: tested automatically on Testbed and succeed on VMs, failed on xavier1 and xavier2. Also manually tested on xavier1, recap system info :
Description: Ubuntu 18.04.6 LTS
Release: 18.04
Codename: bionic
Architecture:        aarch64
Byte Order:          Little Endian
CPU(s):              8
On-line CPU(s) list: 0-7
Thread(s) per core:  1
Core(s) per socket:  2
Socket(s):           4
Vendor ID:           Nvidia
Model:               0
Model name:          ARMv8 Processor rev 0 (v8l)
-----------------------------------------------------------------------------------------------
H/W path        Device          Class      Description
======================================================
                                system     Jetson-AGX
/0                              bus        Motherboard
/0/0                            processor  cpu
/0/0/0                          memory     64KiB L1 Cache
/0/1                            processor  cpu
/0/1/0                          memory     64KiB L1 Cache
/0/2                            processor  cpu
/0/2/0                          memory     64KiB L1 Cache
/0/3                            processor  cpu
/0/3/0                          memory     64KiB L1 Cache
/0/4                            processor  cpu
/0/4/0                          memory     64KiB L1 Cache
/0/5                            processor  cpu
/0/5/0                          memory     64KiB L1 Cache
/0/6                            processor  cpu
/0/6/0                          memory     64KiB L1 Cache
/0/7                            processor  cpu
/0/7/0                          memory     64KiB L1 Cache
/0/8                            processor  cpu_cluster_power_states
/0/9                            processor  cpu_core_power_states
/0/a                            processor  cpu_crossover_thresholds
/0/b                            processor  cpu-map
/0/c                            memory     31GiB System memory
/0/100                          bridge     NVIDIA Corporation
/0/100/0                        storage    Micron/Crucial Technology
/0/100/0/0      /dev/nvme0      storage    CT500P5PSSD8
/0/100/0/0/1    /dev/nvme0n1    disk       500GB NVMe namespace
/0/100/0/0/1/1  /dev/nvme0n1p1  volume     465GiB EXT4 volume
/0/101                          bridge     NVIDIA Corporation
/0/101/0                        storage    Marvell Technology Group Ltd.
/0/d                            generic    Virtual I/O device
/1              usb1            bus        xHCI Host Controller
/2              usb2            bus        xHCI Host Controller
/3              dummy0          network    Ethernet interface
/4              eth0            network    Ethernet interface
/5              usb0            network    Ethernet interface
/6              rndis0          network    Ethernet interface

The error on xavier1 is still the same as previously:

.
Tried to build and execute the NetManager systemd replicating your setup on RPi 3B+ with:
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye
Architecture:                    armv7l
Byte Order:                      Little Endian
CPU(s):                          4
On-line CPU(s) list:             0-3
Thread(s) per core:              1
Core(s) per socket:              4
Socket(s):                       1
Vendor ID:                       ARM
Model:                           4
Model name:                      Cortex-A53
-----------------------------------------------------------------------
H/W path        Device          Class      Description
========================================
                  system     Raspberry Pi 3 Model B Plus Rev 1.3
/0                bus        Motherboard
/0/0              processor  cpu
/0/0/0            memory     32KiB L1 Cache
/0/1              processor  cpu
/0/1/0            memory     32KiB L1 Cache
/0/2              processor  cpu
/0/2/0            memory     32KiB L1 Cache
/0/3              processor  cpu
/0/3/0            memory     32KiB L1 Cache
/0/4              processor  l2-cache0
/0/5              memory     921MiB System memory
/1        usb1    bus        DWC OTG Controller
/1/1              bus        USB 2.0 Hub
/1/1/1            bus        USB 2.0 Hub
/1/1/1/1  eth0    network    Ethernet interface
/1/1/3            input      USB Receiver
/2        wlan0   network    Wireless interface

with Go version go version go1.23.2 linux/arm but the executable seems to fail (both as systemd or binary exec):
 with systemd journal log:
Nov 02 15:29:59 raspberrypi systemd[7509]: netmanager.service: Failed at step EXEC spawning NetManager: Exec format error
░░ Subject: Process NetManager could not be executed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The process NetManager could not be executed and failed.
░░
░░ The error number returned by this process is ERRNO.
Nov 02 15:29:59 raspberrypi systemd[1]: netmanager.service: Main process exited, code=exited, status=203/EXEC
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit netmanager.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 203.
Nov 02 15:29:59 raspberrypi systemd[1]: netmanager.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit netmanager.service has entered the 'failed' state with result 'exit-code'.

Same errors for NodeEngine. The setup seems to be the same, I'm missing something?

I was able to replicate the issue on xavier1. I updated the systemd service file using absolute paths, this should fix the issue.
Tho, on RPi 3B+ I think the issue might be different, that device uses armv7l, by default our golang binaries are built for arm64 (RPi 4 and newer). This can be fixed adding GOARM=7 in the NodeEngine and NetManager build script. Resulting in a command like:
env GOOS=linux GOARCH=arm64 GOARM=7 go build -ldflags="-X 'go_node_engine/cmd.Version=$version'" -o NodeEngine_arm64 ../NodeEngine.go

If you confirm that this worked, we can finalize the review and merge it ;)

PR ready for review.
How to test it:
1- clone NetManager from this branch: 181-make-netmanager-systemd-compatible
2- Install the NetManager moving inside node-net-manaber/build and running ./build.sh && ./install.sh $(dpkg --print-architecture) (You don't need to configure anything else if your workers are part of the same network)
3- Install the propose NodeEngine by moving to the go_node_engine/build directory and running ./build.sh && ./install.sh $(dpkg --print-architecture)
3.5 - If you tested this on a previous version of the branch, please use sudo NodeEngine config default to re-generate the default node configuration
4- Start NodeEngine and NetManager by simply running sudo NodeEngine -a <cluster address> -d
You can check the NodeEngine status using:
NodeEngine status
You can check the NodeEngine logs using:
NodeEngine logs
Tested and got following status using NodeEngine status

Got two apps running on the node:

There might be a blind spot:

I.e. the command with "off" or "on" works, but if I type nothing an error occurs - but the CLI should show the help instead

I initially started the NodeEngine with the default config - I was able to start the default SLA app with the nginx and curl services.
FLOps did not work as expected because the builder addon support was not yet active- I activated it via " sudo NodeEngine config addon imageBuilder on" it is shown as active - but it does not work yet - I assume I need to restart the NodeEngine first.
Is there some recommended way of doing so ? - In general, I do not see a stop, restart command - or should we simply do it via systemctl ?

There might be a blind spot:

I.e. the command with "off" or "on" works, but if I type nothing an error occurs - but the CLI should show the help instead

fixed

I initially started the NodeEngine with the default config - I was able to start the default SLA app with the nginx and curl services.
FLOps did not work - which was expected - because the builder addon support was not yet active- I activated it via " sudo NodeEngine config addon imageBuilder on" it is shown as active - but it does not work yet - I assume I need to restart the NodeEngine first. Is there some recommended way of doing so ? - In general, I do not see a stop, restart command - or should we simply do it via systemctl ?
Update: it worked after I ran "sudo systemctl restart nodeengine.service"

Yes either systemctl restart or NodeEngine stop and then you start it up again

I think the Addon "StartUp" might not be working properly yet.
FLOps managed to do the build part correct but the learners were not able to connect to the ML Data Sidecar,

I think the reason is that this sidecar does not even exist - i.e. it did not get spawned as it should during the NodeEngine start/activities:

I think the Addon "StartUp" might not be working properly yet.
FLOps managed to do the build part correct but the learners were not able to connect to the ML Data Sidecar,
I think the reason is that this sidecar does not even exist - i.e. it did not get spawned as it should during the NodeEngine start/activities:

You're right, there was a bug in the addon init function. I also added some INFO logs so that at startup the user can actually check if an addon is being loaded or not (or at least we can better help users debugging things)

Looks good now - FLOps and the default workflows are also now working


Petstore sample's updatePetWithForm does not change pet data

As in the java-jaxrs sample source code, the changes are not saved actually, is it expected?
(migrated from swagger-api/swagger-codegen#656)

@fehguy FYI. I tested http://petstore.swagger.io/#!/pet/updatePetWithForm but still the update failed. My guess is that the server has not picked up the latest change.

@wing328 - it's not deployed yet. will be deployed with an official release.

@webron ok understood.

@wing328 I've pushed the updated petstore now, it should work.  There was a delay, we merged a PR and caused a spec problem.

@fehguy I performed a test via http://petstore.swagger.io/#!/pet/updatePetWithForm and confirm updatePetWithForm now works fine :smile:


⚠  Simplify DetailLogger

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] PR title follows the guidelines defined in  https://github.com/ossf/scorecard/blob/main/CONTRIBUTING.md#pr-process

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Part of #1393

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.

Codecov Report

Merging #1628 (737146b) into main (38be00c) will increase coverage by 0.29%.
The diff coverage is 83.90%.

@@            Coverage Diff             @@
##             main    #1628      +/-   ##
==========================================
+ Coverage   55.34%   55.64%   +0.29%
==========================================
  Files          72       72
  Lines        6441     6513      +72
==========================================
+ Hits         3565     3624      +59
- Misses       2634     2647      +13
  Partials      242      242


[5.2] Last executed query helper function

Little helper function to dump the last executed query and exit. Name comes from the action Dump & Die with the last DB query.
Needs query logging to be enabled (DB::enableQueryLog()) for it to work, but I didn't think it wise to force that here.

All requested formatting changes have been made

@mrk-j Good shout - I've put that in

Going to hold off on including this in the core I think.


Support creating a workspace from multiple top-level files

The existing constructor for frontend::Workspace only accepts a single file path. That makes it awkward to construct a workspace from multiple top-level files, e.g., when importing multiple standard library files. One has to parse each of them individually and then merge the workspaces, which also results in a lot of duplicated parsing when the files have common dependencies.
The code to do this efficiently is already embedded in the implementation of Workspace::construct_with_all_deps(), it just needs to be exposed as part of the public interface.

This should be super straightforward! We can just make the method pub and create a new minor release. @bcarlet want to take a shot?


[camera] Android Preview Orientation Issues

Hi,
When starting the example app in the camera plugin on the Android Emulator (Pixel 5 API 31) even though the phone is in portrait mode the preview is in landscape. I initially thought this has to do with preview size, but placing the preview in a sized box and changing the width/height had no effect on the orientation.
I'm not completely sure if this is a bug or expected behaviour. Furthermore, browsing the code I see that CameraValue has some orientation-related properties, but none seems related to this.
Is there a way to change preview orientation without changing device orientation?
Thanks,
Fouad

Hi @fmardini, can you provide the version of camera you're experiencing this with, along with the output of flutter doctor -v and a complete minimal reproducible code sample?
Kindly also check if https://github.com/flutter/flutter/issues/94045 is similar to the issue you're facing.
Thank you

Thanks @danagbemava-nc
This is on the sample app coming with the camera plugin, latest git checkout. What is not clear to me, is whether the behaviour of the sample app is intended or buggy.
Yes indeed it seems very related to the issue you linked.

flutter doctor -v
[✓] Flutter (Channel stable, 2.10.1, on Mac OS X 10.15.7 19H1715 darwin-x64, locale en-GB)
    • Flutter version 2.10.1 at /usr/local/Caskroom/flutter/2.10.1/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision db747aa133 (8 weeks ago), 2022-02-09 13:57:35 -0600
    • Engine revision ab46186b24
    • Dart version 2.16.1
    • DevTools version 2.9.2
[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
• Android SDK at /Users/fmardini/Library/Android/sdk
• Platform android-32, build-tools 32.1.0-rc1
• Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
• All Android licenses accepted.
[!] Xcode - develop for iOS and macOS (Xcode 12.4)
• Xcode at /Applications/Xcode.app/Contents/Developer
! Flutter recommends a minimum Xcode version of 13.
Download the latest version or update via the Mac App Store.
• CocoaPods version 1.11.3
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2021.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
[✓] VS Code (version 1.66.0)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.38.0
[✓] Connected device (2 available)
• sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 12 (API 31) (emulator)
• Chrome (web)                 • chrome        • web-javascript • Google Chrome 99.0.4844.84
[✓] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 1 category.

What is not clear to me, is whether the behaviour of the sample app is intended or buggy.

From what I can see, the camera sample doesn't do anything to the preview orientation, so the issue may lie within the plugin code.
Also, the issue I linked seems related to startImageStream but the camera sample doesn't use startImageStream so it's possible there's something else going on here.
Can you share a sample that shows how you determined that the orientation on android was "off"? Some logs would also be helpful and any screenshots or recordings as well.
Thank you

Here's a screenshot of the app running in the emulator. I would have expected the the preview to be rotated 90 CCW

Hi @fmardini, I take it you're using the webcam of your host system as the camera for the emulator. In that case, this is not an issue with the camera package, but rather with the emulator itself. You can test this by opening the camera app of the emulator, it should also be rotated. See screenshot below

screenshot

@danagbemava-nc Thank you. I confirmed the orientation is correct when running on device. I also confirmed by running the Camera2 samples from https://github.com/android/camera-samples
On the other hand, is it possible to change the orientation of the preview? Simply using a Flutter RotatedBox gives wrong aspect ratio.
Thanks,
Fouad

Hi @fmardini, I don't think it is necessary for you to do that.
From what I see in the code for the preview, the preview is already rotated, taking into account the aspect ratio, but if you are so inclined, you can check the code for the preview and modify it to suit your needs. The code can be found here https://github.com/flutter/plugins/blob/main/packages/camera/camera/lib/src/camera_preview.dart

Yeah thanks, I've seen that. But was just wondering if there were an option to set it up relative to current orientation. Many thanks


Compatible with non-standard sharedStrings

@pbnjay
please merge

hi @bugstark can you provide more details/an example of this? what produces files with these non-standard values?


Cannot interpret asset as BitmapDescriptor

Steps to reproduce
Using:
google_maps_flutter: 2.5.0
google_maps_flutter_platform_interface: 2.7.0

Calling this works and the image displays on the map:
final config = createLocalImageConfiguration(context);
BitmapDescriptor.fromAssetImage(config, 'assets/images/lock.png');

Calling this:
final config = createLocalImageConfiguration(context);
BitmapDescriptor.asset(config, 'assets/images/lock.png');

Throws this:
PlatformException(error, Cannot interpret [asset, {bitmapScaling=auto, assetName=assets/images/lock.png, imagePixelRatio=1.0}] as BitmapDescriptor, null, java.lang.IllegalArgumentException: Cannot interpret [asset, {bitmapScaling=auto, assetName=assets/images/lock.png, imagePixelRatio=1.0}] as BitmapDescriptor

My assets and pubspec file haven't changed in both cases.
The BitmapDescriptor.asset method calls AssetMapBitmap.create internally. According to the docs for that method, I'm supposed to do this:
Future<void> _getAssetMapBitmap(BuildContext context) async {
   final ImageConfiguration imageConfiguration = createLocalImageConfiguration(
    context,
  );
  AssetMapBitmap assetMapBitmap = await AssetMapBitmap.create(
    imageConfiguration,
    'assets/images/map_icon.png',
  );
  return assetMapBitmap;
}

I'm following the directions, so why am I getting an error?
Expected results
No PlatformException
Actual results
PlatformException
Code sample
Code sample
BitmapDescriptor.asset(config, 'assets/images/lock.png');

Flutter Doctor output
Doctor output
[!] Flutter (Channel [user-branch], 3.22.0, on Microsoft Windows [Version 10.0.19045.4291], locale en-CA)
    ! Flutter version 3.22.0 on channel [user-branch] at F:\Coding\Languages\flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/docs/get-started/install.
    ! Upstream repository unknown source is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
    • Framework revision 5dcb86f68f (3 weeks ago), 2024-05-09 07:39:20 -0500
    • Engine revision f6344b75dc
    • Dart version 3.4.0
    • DevTools version 2.34.3
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 35.0.0-rc1)
    • Android SDK at C:\Coding\IDEs\Android\AndroidSDK
    • Platform android-34, build-tools 35.0.0-rc1
    • ANDROID_HOME = C:\Coding\IDEs\Android\AndroidSDK
    • Java binary at: C:\Coding\IDEs\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0--11185874)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop Windows apps (Visual Studio Professional 2022 17.9.2)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Professional
    • Visual Studio Professional 2022 version 17.9.34622.214
    • Windows 10 SDK version 10.0.22000.0

[√] Android Studio (version 2023.2)
    • Android Studio at C:\Coding\IDEs\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
    • android-studio-dir = C:\Coding\IDEs\Android\Android Studio
    • Java version OpenJDK Runtime Environment (build 17.0.9+0--11185874)

[√] IntelliJ IDEA Community Edition (version 2021.2)
    • IntelliJ at F:\Coding\IDEs\IntelliJ IDEA Community Edition 2021.2.2
    • 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

[√] Connected device (4 available)
    • SM G990W2 (mobile) • R5CTC13W9MM • android-arm64  • Android 14 (API 34)
    • Windows (desktop)  • windows     • windows-x64    • Microsoft Windows [Version 10.0.19045.4291]
    • Chrome (web)       • chrome      • web-javascript • Google Chrome 124.0.6367.158
    • Edge (web)         • edge        • web-javascript • Microsoft Edge 125.0.2535.67

[√] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Thanks for the report. However, there is already one similar issue to this at https://github.com/flutter/flutter/issues/149183. Closing this as a duplicate, please follow that issue for updates.

Getting the same error in showing Asset marker.


WSL Ubuntu aliases stop working after update to 1.31

Prerequisites

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
My aliases to open Atom in Ubuntu Windows Subsystem for Linux stop working after updating from 1.30 to 1.31. Using commands like "atom ." instead give me the following error:
net.js:200
    this._handle.open(options.fd);
                 ^

Error: EINVAL: invalid argument, uv_pipe_open
    at new Socket (net.js:200:18)
    at createWritableStdioStream (internal/process/stdio.js:164:16)
    at process.getStdout [as stdout] (internal/process/stdio.js:14:14)
    at console.js:246:38
    at NativeModule.compile (bootstrap_node.js:596:7)
    at Function.NativeModule.require (bootstrap_node.js:541:18)
    at setupGlobalConsole (bootstrap_node.js:310:41)
    at startup (bootstrap_node.js:70:7)
    at bootstrap_node.js:608:3

my alias for opening atom in WSL Ubuntu is: alias atom='/mnt/c/Windows/System32/cmd.exe /c "atom"'.
Steps to Reproduce
Updating to 1.31 produces this issue. Rolling back to 1.30 resolves this until atom updates to 1.31.
Versions
Atom    : 1.31.0
Electron: 2.0.7
Chrome  : 61.0.3163.100
Node    : 8.9.3
I'm running Windows 10.

Thanks for the report - confirming that I can reproduce with 1.31.0 and 1.32.0-beta0 , and the error isn't present in 1.30.

Glad this isn't just me, been pulling my hair out all day trying to figure out what was going on.
I'm seeing this too, although it only appears to be occurring in 16.04, not 18.04.

The same for WSL Debian.

I also have this error. Thank you for reporting

Ditto.
Ubuntu 16.04.5 LTS.

Also getting this error.
Atom: 1.31
Ubuntu: 16.04.3 LTS
If you still have version 1.30.0 on your machine, you can roll back the atom command with this:
%LocalAppData%\atom\app-1.30.0\atom.exe --squirrel-install 1.30.0
It will point the command back to your old version so long as you still have it installed in the default location.

When I run this:
%LocalAppData%\atom\app-1.30.0\atom.exe --squirrel-install 1.30.0
I get:
-bash: fg: %LocalAppData%atomapp-1.30.0atom.exe: no such job
Any ideas on what I can do?

When I run this:
%LocalAppData%\atom\app-1.30.0\atom.exe --squirrel-install 1.30.0
I get:
-bash: fg: %LocalAppData%atomapp-1.30.0atom.exe: no such job
Any ideas on what I can do?

If you use cmd, it will work. And before enter the command %LocalAppData%\atom\app-1.30.0\atom.exe --squirrel-install 1.30.0 which @thomasmarkrea said, check where %LocalAppData%\atom\app-1.30.0\atom.exe exactly locate.
"%LocalAppData%" usually means C:\\users\\username\\AppData\\Local\\   .

So I should run cmd %LocalAppData%\atom\app-1.30.0\atom.exe --squirrel-install 1.30.0
?

@seano424 You should open the Windows command line ("DOS Prompt") and enter this command. Or in PowerShell use & "$env:LocalAppData\atom\app-1.30.0\atom.exe" --squirrel-install 1.30.0. By the way, I notice that on my machine the folder for 1.30.0 has disappeared.

This appears to be kind of fixed in Atom 1.31.2, but now when I run my atom alias it hangs and forces me to close out of the terminal and open a new one (ctrl+c doesn't even work)

Also sure to turn off automatic updates by clicking on the squirrel icon in the bottom right-hand corner and then unselecting the automatic updates box.

Any status update on this? Been over a month at this point.

Adding this to the bash rc file is a very simple workaround:
alias atom='powershell.exe start atom'

@JacobDB
Your solution Microsoft/wsl#1832 under WSL is a good work around still. This can also work with any problem opening apm under WSL which I've had trouble with as well.
Copied here:

I figured this out :) Here's a guide:

Open ~/.bashrc in a text editor
At the bottom, add a new function:function atom() {
     /mnt/c/System32/cmd.exe /C atom.cmd $1
 }

Save the file and exit the text editor
Run . ~/.bashrc

The command atom will now work properly!

@GuttermanA I just did some experimentation and came up with a solution for the second half. If you run the program in the background, it works correctly. Like so:
atom() {
    target_path=$(wslpath -a -w $(readlink -f $1)) # resolve the path
    (/mnt/c/Windows/System32/cmd.exe /C "atom.cmd $target_path" &) # open the path
}

Adding this to the bash rc file is a very simple workaround:
alias atom='powershell.exe start atom'

confirmed this method works, but you have to bear with looking at powershell window for a split second.


Release pypi

Changes:

Update python versions
Add version.py file. Starting on v0.6.3, since the latest on https://github.com/mbr/flask-kvsession is 0.6.2
Named according to issue: inveniosoftware/Flask-KVSession-Invenio

Tests are passing: https://travis-ci.org/github/ppanero/flask-kvsession/builds/683756756 Will eventually pass here when travis has time.
Closes https://github.com/inveniosoftware/flask-kvsession/issues/3

Apparently @lnielsen was faster :facepalm:


Examples seem to be broken

I'm not sure if I'm the problem lies between (my) chair and keyboard, but to me it seems like the ol-marker -directive is broken in the 0.0.2 release and the online examples.
Marker(s) not visible:
http://tombatossals.github.io/angular-openlayers-directive/examples/060-marker-example.html
http://tombatossals.github.io/angular-openlayers-directive/examples/061-markers-add-remove-example.html
Marker not visible, label visible:
http://tombatossals.github.io/angular-openlayers-directive/examples/062-markers-label-example.html
Markers not visible, showOnMouseOver has no effect:
http://tombatossals.github.io/angular-openlayers-directive/examples/063-markers-properties-example.html
Markers not visible, otherwise seems to work as intended:
http://tombatossals.github.io/angular-openlayers-directive/examples/064-markers-render-html-inside-labels-example.html
Marker not visible:
http://tombatossals.github.io/angular-openlayers-directive/examples/065-markers-static-image-layer-example.html

Hi @zzats, you're totally right, the new library version was not uploaded to the "gh-pages" branch, which is the one used on github public pages.
Now it seems to work well again.
Thanks for reporting!

Thank you @tombatossals for the quick fix! Still a follow-up: the examples still have issues with static images and markers with pixel projection
http://tombatossals.github.io/angular-openlayers-directive/examples/065-markers-static-image-layer-example.html

Totally right, it was a bug with the new features I'm implementing of drawing paths that affected the markers in the pixel projection.
Now it's working, thanks!!!


Add support for Taildrop (file sharing)

A very low-hanging fruit here. This PR just adds support for Taildrop (tailscale filesharing, https://tailscale.com/kb/1106/taildrop/)

Implements #118

FWIW you can do HTTP stuff at a UNIX domain socket with net/http:
        socClient := http.Client{
                Transport: &http.Transport{
                        DialContext: func(_ context.Context, _, _ string) (net.Conn, error) {
                                return net.Dial("unix", "/tmp/sockpost.sock")
                        },
                },
        }

        var res *http.Response
        res, err := socClient.Post("http://unix/place/stuff", "application/octet-stream", fileReader)
        if err != nil {
                log.Fatal(err)
        }

This would eliminate the need for an external dependency on curl.

This would eliminate the need for an external dependency on curl.

I am afraid we can't. We execute curl inside the container where we run Tailscale.

Looks good


Update version and cli URI

Adds the app.Version setting used in upstream urfave/cli built in --version/-v and --help/-h options, which can be used for proper version checking.
Also updates the URL of the CLI library to their new URL, bringing it into consistency with the other CLI binary.
Due to the app.Version missing, the following --help looks like this:
NAME:
supergiant-server - Supergiant server v0.14.3
USAGE:
supergiant-server-linux-amd64 [global options] command [command options] [arguments...]
VERSION:
0.0.0
COMMANDS:
GLOBAL OPTIONS:
--sqlite-file    SQLite3 database (.db) file
--psql-host      PostgreSQL host
--psql-db        PostgreSQL database name
--psql-user      PostgreSQL database user
--psql-pass      PostgreSQL database password
--publish-host   Host that can be used to connect to this Supergiant server remotely
--http-port      HTTP port for the web interfaces
--ui-enabled     Enabled UI
--https-port     HTTPS (SSL) port for the web interfaces
--ssl-cert-file  SSL certificate file
--ssl-key-file   SSL key file
--log-file       Log output filepath
--log-level      Log level
--config-file    JSON config filepath (command line arguments will override the values set here)
--help, -h       show help
--version, -v    print the version
and --version looks like this:
supergiant-server version 0.0.0

Second commit removes deprecated code from vendor.json and vendor

lgtm

lgtm


exclude node_modules on some loaders

Coverage remained the same at 100.0% when pulling 72d867a5a6ad5af3bd52958e69656ae7831e697a on refactoring into d1140d68d2ec433b625b881f08231e38aa0f8e30 on master.

Coverage remained the same at 100.0% when pulling db0668e37ae7a82e35fb27e3145527e7c79be143 on refactoring into d1140d68d2ec433b625b881f08231e38aa0f8e30 on master.

Coverage remained the same at 100.0% when pulling b5e420042a9426d096473df2649aff9949aeed1d on refactoring into d1140d68d2ec433b625b881f08231e38aa0f8e30 on master.


Fixed tests with Ruby 3.2 and moved CI to Github Actions

I had all tests passing on ruby 1.9 -> 3.2
https://github.com/mathieujobin/writeexcel/actions/runs/7355229189
but after rebasing with recent changes, it fails for ruby 2.3 -> 2.7
https://github.com/mathieujobin/writeexcel/actions/runs/7355272420
So, I think I will make 3.0 the minimum version.

I got the thing to pass on ruby 3.3 now, I will open a new PR after this one is merged.
https://github.com/mathieujobin/writeexcel/actions/runs/7355549423/job/20024324115


Master to Live

Docs Build status updates of commit 3873837:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

README.md
:white_check_mark:Succeeded

exchange/docs-conceptual/exchange-online-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Clear-MobileDevice.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-MobileDevice.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-MobileDeviceMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-MobileDeviceStatistics.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/New-MobileDeviceMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Remove-MobileDevice.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Remove-MobileDeviceMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-MobileDeviceMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

repo_docs/ADVANCED.md
:white_check_mark:Succeeded

repo_docs/NEW_CMDLETS.md
:white_check_mark:Succeeded

repo_docs/UPDATE_CMDLETS.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Wait for localstack to be ready

Hi everybody,
we use quarkus.aws.devservices.localstack.init-scripts-folder to initialize localstack before starting tests (e.g. to write SSM parameters).
When the tests are executed, however, localstack may not yet be ready because the script has not yet been executed to completion. For example, the SSM parameters cannot yet be found.
I have a reproducer for the problem here: https://github.com/dagrammy/ssm-devservices-test
As a workaround we currently use a @QuarkusTestResource' and the localstack endpoint /_localstack/init` to wait for localstack until it is ready.
Could something like this be built directly into the start of localstack or the dev services?
I would like to have a look at this myself, maybe someone can point me in the right direction. 🙂

You should be able to wait for message with quarkus.aws.devservices.localstack.init-completion-msg
We do something similar here https://github.com/quarkiverse/quarkus-amazon-services/tree/main/integration-tests/src/test/resources

Thank you, I overlooked this configuration property in the documentation. 🤦
quarkus.aws.devservices.localstack.init-completion-msg works perfectly for this use case!


Missing parameters for request

Closes #34

Please add also a docs for those changes.

It could be a new chapter about how to add parameters to query string or inside query. If there is not ready one.

Documentation added.


fix olive-editor-nightly (fixes #660)

This fixes olive-editor-nightly install by updating the download URL following the new standards on their repo. Also removes the workaround for extracting the .zip.zip file, as that's no longer needed.

Closes #660

[x] I have read the Contributing Guide.

/verify

/verify

@rmobis do you mind typing /verify. It seems me and @rasa are unable to do so for your manifest.

/verify

Oh sorry, I forgot to change the commit name, should be olive-editor-nightly: Fix checkver and installation (fixes #660)


.

.

I'm having this issue too ("Play" function does not work when playlist contains Local Songs), I'm assuming this is an issue on Spotify's end? (I know you can't stream offline media to devices natively)

You can't use the Spotify API to play local songs, but maybe it's possible to play only the nonlocal songs from a playlist. I haven't worked on this in a while, and can't commit to looking into this issue at the moment, but I'd certainly accept a PR!


Add an option to add custom css

We should add an option to let the user choose the custom CSS file from their system and then inject it into the app. This option would be useful for users who don't like the certain design and want to override the default styling.

Yeah, I have seen this feature in a couple of the electron apps, it's an easy feature to implement.

Added in https://github.com/zulip/zulip-electron/commit/a90dc0c82fed7fb7a10fb54fadaa3aa91e2f8bbb.


add unified tools for filter arana inner table.

What would you like to be added:
Why is this needed:

ref  #393 .


Voxelsdk for arm version

Hi sir,
I'm compiling voxelsdk to raspberry pi for arm based platform (kernel version 4.1.9+ & gcc version (Raspbian 4.7.3-11+rpi1) 4.7.3, & g++ version (Raspbian 4.9.2-10) 4.9.2 )). after make command, I found error below. Any suggestion? thx. & lt also looks the libpcl-all is not able to install onto RPI system. not sure is it related to the erroe or not. see below...
pi@raspberrypi ~/voxelsdk/build $ make
[  1%] Building CXX object Voxel/CMakeFiles/voxel.dir/Device.cpp.o
c++: error: unrecognized command line option '-msse2'
make[2]: *** [Voxel/CMakeFiles/voxel.dir/Device.cpp.o] Error 1
make[1]: *** [Voxel/CMakeFiles/voxel.dir/all] Error 2
make: *** [all] Error 2
BR Kenny

Hi sir,
I compiled the voxelsdk w/o problem but while I run the executable in App folder. I found below message. not sure which camera libray is not loaded? The VoxelCLI has same message output. thank you.
pi@ubuntu:~/voxelsdk/build/App$ ./SimpleVoxelViewer
WARNING: CameraSystem: No depth camera library found or loaded.
SimplePCLViewer: Could not find a compatible device.
pi@ubuntu:~/voxelsdk/build/App$

Never mind it, I forget set set 3 variables paths.
but it now looks no depth data observed in CLI or Simple viewer.

@userkenny:  What ARM processor were you running?  Were there any error messages from the VoxelCLI or SimpleViewer?

I'm looking into cross compile alternative for my raspberrypi (RPI) under Ubuntu 14.04 64bits environment. It is because If I directly compiled on RPI, it did not have big ram to compile voxelsdk till the end & throw out of memory error message in the middle.
But I failed to cross compiled for RPI under several cmake-gui setting trials. Any ideas to cross compile for an embed arm system, like RPI? thx.
Regards, Kenny

Direct compiling due to ram limitation, try turn on swap.  When I built voxelsdk for Pandaboard I had to turn on 2G+ swap.
I haven't tried cross-compiling, your challenge may be coming  from the dependencies, such as swig3.0, pcl, etc, which voxel-sdk needs access to at least the headers.
I found this link which may be helpful, if you haven't seen it already.  http://www.openframeworks.cc/setup/raspberrypi/Raspberry-Pi-Cross-compiling-guide.html
Make sure cmake is using the right CC, etc... so it's pointing to the cross tool.

Hi Larrylisky,
I choice to enlarge the swap space as 2G bytes. but I found below error while directly make compiling in RPI. any idea?
[ 75%] Building CXX object TI3DToF/CMakeFiles/ti3dtof.dir/ToFCrossTalkFilter.cpp.o
Linking CXX shared library libti3dtof.so
[ 75%] Built target ti3dtof
[ 76%] Building CXX object TI3DToF/boards/HaddockCDK/CMakeFiles/haddockcdk.dir/HaddockCDKCamera.cpp.o
[ 77%] Building CXX object TI3DToF/boards/HaddockCDK/CMakeFiles/haddockcdk.dir/HaddockCDKCameraFactory.cpp.o
Linking CXX shared library ../../libhaddockcdk.so
[ 77%] Built target haddockcdk
[ 78%] Building CXX object TI3DToF/boards/TintinCDK/CMakeFiles/tintincdk.dir/TintinCDKCamera.cpp.o
[ 79%] Building CXX object TI3DToF/boards/TintinCDK/CMakeFiles/tintincdk.dir/TintinCDKCameraFactory.cpp.o
[ 80%] Building CXX object TI3DToF/boards/TintinCDK/CMakeFiles/tintincdk.dir/TintinCDKDownloaderFactory.cpp.o
[ 81%] Building CXX object TI3DToF/boards/TintinCDK/CMakeFiles/tintincdk.dir/TintinEEPROMDownloader.cpp.o
/home/pi/voxelsdk/TI3DToF/boards/TintinCDK/TintinEEPROMDownloader.cpp: In member function 'virtual bool Voxel::TI::TintinEEPROMDownloader::_configureForDownload()':
/home/pi/voxelsdk/TI3DToF/boards/TintinCDK/TintinEEPROMDownloader.cpp:47:36: error: converting to 'const SlaveAddressToByteMap {aka const std::unordered_map<unsigned int, unsigned int, std::hash, std::equal_to, std::allocator<std::pair<const unsigned int, unsigned int> > >}' from initializer list would use explicit constructor 'std::unordered_map<_Key, _Tp, _Hash, _Pred, _Alloc>::unordered_map(std::unordered_map<_Key, _Tp, _Hash, _Pred, _Alloc>::size_type, const hasher&, const key_equal&, const allocator_type&) [with _Key = unsigned int; _Tp = unsigned int; _Hash = std::hash; _Pred = std::equal_to; _Alloc = std::allocator<std::pair<const unsigned int, unsigned int> >; std::unordered_map<_Key, _Tp, _Hash, _Pred, _Alloc>::size_type = unsigned int; std::unordered_map<_Key, _Tp, _Hash, _Pred, _Alloc>::hasher = std::hash; std::unordered_map<_Key, _Tp, _Hash, _Pred, _Alloc>::key_equal = std::equal_to; std::unordered_map<_Key, _Tp, _Hash, _Pred, _Alloc>::allocator_type = std::allocator<std::pair<const unsigned int, unsigned int> >]'
VoxelXUProgrammer p({}, _device);
^
make[2]: *** [TI3DToF/boards/TintinCDK/CMakeFiles/tintincdk.dir/TintinEEPROMDownloader.cpp.o] Error 1
make[1]: *** [TI3DToF/boards/TintinCDK/CMakeFiles/tintincdk.dir/all] Error 2
make: *** [all] Error 2

I've seen this before.  Sometimes you just have to run 'make' again without deleting anything in the build directory, and make will continue and complete.  This cause is likely memory limitation.   Turn swap on perhaps to a larger size may help also.

Here is a link to prebuilts for voxelsdk and pcl for armhf.
https://github.com/3dtof/prebuilt

This is really cool! Thanks, Larry!
~ Prasad Bhat
On 01-Dec-2015 8:22 PM, "Larry Li"<EMAIL_ADDRESS>wrote:

Here is a link to prebuilts for voxelsdk and pcl for armhf.
https://github.com/3dtof/prebuilt
—
Reply to this email directly or view it on GitHub
https://github.com/3dtof/voxelsdk/issues/35#issuecomment-160989206.

@userkenny  Can I please know which variable paths have you setup in one of your above comments which reads as follows

I too am getting CameraSystem: No depth camera library found or loaded. error

Hi,
I'm sorry & I'm kind of long time away from that message.
2016-10-07 5:52 GMT-07:00 ashokbugude<EMAIL_ADDRESS>
@userkenny https://github.com/userkenny Can I please know which
variable paths have you setup in one of your above comments which reads as
follows
[image: voxel]
https://cloud.githubusercontent.com/assets/10016848/19190368/cd9165f2-8cba-11e6-8dc0-f2151ab327f2.png
I too am getting CameraSystem: No depth camera library found or loaded.
error
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/3dtof/voxelsdk/issues/35#issuecomment-252244151, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANAt6YBN1HKAxwf74exgSz7Azo1yvN6yks5qxkCAgaJpZM4GIY2D
.


fix: don't override WEB_CONCURRENCY if set

@jordanmaguire wanted to get the existance of these repos in front of your eyes, we will be discussing more next week https://3.basecamp.com/3601722/buckets/1937663/todos/3862709740

@dirkkelly This seems like a bug in the buildpack to me - are we intending to create a PR back into the source?

@jordanmaguire yeah agreed it seems like a bug in the heroku buildpack, going to create a PR if we're happy with the change on our side.

@jordanmaguire usually we just use the heroku/nodejs default, eg:
$ heroku buildpacks -a app

=== app Buildpack URLs
1. heroku/nodejs
2. heroku/ruby

On the branch within our system where we're testing this alternative buildpack that has been changed to point to this branch.
$ heroku buildpacks -a app-pr-123

=== app-pr-123 Buildpack URLs
1. https://github.com/interexchange/heroku-buildpack-nodejs.git#fix-web-concurrency
2. heroku/ruby

We can make the decision to wait to update our environments until this is merged or temporarily use our branch / repo while we wait for the heroku official to update (which would require keeping up-to-date with upstream).
I think best next step is to create a PR on the Heroku repo and see what the maintainers have to say.

Created a PR on Heroku's upstream https://github.com/heroku/heroku-buildpack-nodejs/pull/926


Support Feed Me 2

This has now been implemented as part of the Feed Me Helpers repository. Download the commentshelper and install as a regular plugin.
Please also note you'll need the latest master of the comments plugin.


Failed to clone demo/gaps

Thanks for your great work and the repo
I ran into an issue when following the installation instruciton that I'm not able to access the gap repo;
Submodule 'demo/gaps' (git@github.com:tomfunkhouser/gaps.git) registered for path 'demo/gaps'
Cloning into 'C:/Users/Egdivad/source/repos/Github/dg_fork_openscene/demo/gaps'...
Host key verification failed.
fatal: Could not read from remote repository.

Do you know what I'm doing wrong? Thanks

Are you able to do it already? If not, consider directly git clone or download from the official repo, and then following the instruction to install our demo.
Best
Songyou


How to use custom chat page(e.g. html page) in place of bot emulator to communicate with bot in local IIS?

Pre-flight checklist

[x] I posted a question about this issue on Stack Overflow using the tag botframework.
[x] I have searched the existing issues before logging a new one.

System Information (Required)

SDK Platform:
SDK Version:
Development Environment: localhost | Azure Bot Service | Azure App Service | other

Issue Description
Describe the issue here.
Example Code
The complete bot code that reproduces the issue.
Steps to Reproduce

Expected Behavior
What you expected to happen.
Actual Results
What actually happened. Please give examples and support it with screenshots, copied output or error messages.

Are you using .NET or Node SDK?

@Harshjaswal If you would like to embed the chat in your website, use the BotFramework-WebChat project.

Thanks...but the thing is I don't want to use azure for it..as we use bot
emulator to chat with bot application,  i want to use a custom chat page
created in html...means i want to know can we connect our bot application
with simple html page to communicate..if yes plz tell me how. Thanku
On 23-May-2017 11:18 pm, "Nils"<EMAIL_ADDRESS>wrote:

@Harshjaswal https://github.com/harshjaswal If you would like to embed
the chat in your website, use the BotFramework-WebChat
https://github.com/Microsoft/BotFramework-WebChat project.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/2814#issuecomment-303479548,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbUhiQ-Xtqwf3iVi5QVMhHeRVdPzSRD4ks5r8xwCgaJpZM4NjcDb
.

I am using. Net
On 23-May-2017 10:05 pm, "Nils"<EMAIL_ADDRESS>wrote:

Are you using .NET or Node SDK?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/2814#issuecomment-303459525,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbUhidaFR5Hi9hhrSzmOz7n2BVrU4hImks5r8wqtgaJpZM4NjcDb
.


Disable DHT values and providers by default

Will need to be enabled explicitly via routing-discovery-propagate p2p config option
Motivation
Mitigation of excess DHT traffic due to spammy routing discovery propagation
Changes
DHT values and providers feature needs to be enabled explicitly via routing-discovery-propagate option
Test Plan
Tested using a mainnet node

Turned out not to be necessary


Bazzite portal isn't downloading or installing anything on a fresh install on my Steam Deck

I have installed Bazzite on my Steam Deck and the portal prompted me to install the necessary apps. I clicked on which ones I wanted to install but when I clicked next and went to show console, everything was getting an error, something with distrobox not having podman or docker. I tried the next section with trying to install other apps such as web browsers, streaming etc. Again, all errors. Nothing is getting installed.

Somehow, it magically worked just by connecting to my wi-fi instead. No clue why.

+1 - I'm getting the exact same issue.

Thanks for the report, this should be fixed in the latest version.

Yep, everything works fine now! Thank you once again!


[Event Request] Table 39 "Purchase Line" - OnBeforeOnValidateQtyToInvoice

We are migrating our code from NAV 2018 to BC16.4. In the table 39 Purchase Line, in the trigger OnValidate in the field 17 "Qty. To Invoice", we used to add a lot of our code. To do so, we need a IsHandled Flag and an event publisher. We would prefer this to the trigger OnBeforeOnValidate because we would like to launch the trigger OnValidate on a condition. If the condition is not fulfilled, then we exit the trigger OnValidate thanks to IsHandled. Like this :

With this integration event :

Do you think it could be possible ?
Thank you for your work.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Fix travis docker image pulling for docs

What does this PR do?
Travis sometimes fails because it fails to pull docker images when building docs.
This PR allows trying to pull images 10 times instead of once.
It removes fails that look like this:
$ if [ "$TRAVIS_PULL_REQUEST" != "false" ]; then make docs; fi
make -C ./docs docs
make[1]: Entering directory '/home/travis/build/traefik/traefik/docs'
rm -rf /home/travis/build/traefik/traefik/docs/site
docker build -t traefik-docs -f docs.Dockerfile ./
Sending build context to Docker daemon  6.612MB
Step 1/6 : FROM alpine:3.13
3.13: Pulling from library/alpine

age configuration: unexpected EOF
make[1]: *** [docs-image] Error 1
make[1]: Leaving directory '/home/travis/build/traefik/traefik/docs'
make: *** [docs] Error 2
The command "if [ "$TRAVIS_PULL_REQUEST" != "false" ]; then make docs; fi" exited with 2.

Motivation
Make the CI fail less often.
More

[X] Added/updated tests
- [ ] Added/updated documentation

Hello @ldez,
What do you think about this ?


test-branch/execute-job/quoted-authorization/c4fcab30-5976-420b-8136-48c9e8d49da1

PR for testing abac5b9888067ff720ed0c2370110eca53d8fe4f

/canonical/self-hosted-runners/run-workflows abac5b9888067ff720ed0c2370110eca53d8fe4f


Separate windows from Rebound project into individual projects

Does this mean the UAC prompt is gonna be in a separate project and all that?

Yes, unless you want it to be part of the cpl project which would make sense. I want the CPL project to also be a collection of miscellaneous settings; OR we could organise a Rebound.Control.* namespace inside a Visual Studio folder so it sort-of appears as one project and the solution explorer isn't too cluttered and neither is the repo.

The second option should do the trick


Make macroexpansion work in fireplace

Fireplace calls clojure.walk/macroexpand-all to expand macros. For Hy, calling macroexpand should be enough. Since the expression that is to be expanded is part of the command, we can't use the current implementation of workarounds.

Fixed in 2fe8efe.


Login with OTP doesn't work because you are redirected to the wrong url

Describe the issue:

The login using the OTP as password ends with an error.
On the browser we are redirected at the following url:
https://dsotp-dev.digitalgrid.it/accountrecoveryendpoint/confirmrecovery.do?client_id=gVWBVK0pdX4pg2Yk3fFbBjKe1aUa&commonAuthCallerPath=%2Foauth2%2Fauthorize&forceAuth=false&nonce=eMpRGZ2HmgHcXhvgavgzd-vxKDYeyTCNZOImNQjQemI&passiveAuth=false&redirect_uri=https%3A%2F%2Fdsotp-dev.digitalgrid.it%2Flogin%2Foauth2%2Fcode%2Fwso2&response_type=code&scope=openid&state=P7R0WCAAFN6erHiAOuDHCGpie2MRlAp7Z3Vl3Onyqm0%3D&tenantDomain=carbon.super&sessionDataKey=94e6cb26-faa5-47a4-a787-b7adbce9218b&relyingParty=gVWBVK0pdX4pg2Yk3fFbBjKe1aUa&type=oidc&sp=ng-dms-gateway&isSaaSApp=true&username=mario.rossi%40ngdms.com&tenantdomain=ngdms.com&confirmation=ZPSXNU&callback=%2Fauthenticationendpoint%2Flogin.do%3Fclient_id%3DgVWBVK0pdX4pg2Yk3fFbBjKe1aUa%26commonAuthCallerPath%3D%252Foauth2%252Fauthorize%26forceAuth%3Dfalse%26nonce%3DeMpRGZ2HmgHcXhvgavgzd-vxKDYeyTCNZOImNQjQemI%26passiveAuth%3Dfalse%26redirect_uri%3Dhttps%253A%252F%252Fdsotp-dev.digitalgrid.it%252Flogin%252Foauth2%252Fcode%252Fwso2%26response_type%3Dcode%26scope%3Dopenid%26state%3DP7R0WCAAFN6erHiAOuDHCGpie2MRlAp7Z3Vl3Onyqm0%253D%26tenantDomain%3Dcarbon.super%26sessionDataKey%3D94e6cb26-faa5-47a4-a787-b7adbce9218b%26relyingParty%3DgVWBVK0pdX4pg2Yk3fFbBjKe1aUa%26type%3Doidc%26sp%3Dng-dms-gateway%26isSaaSApp%3Dtrue%26authenticators%3DBasicAuthenticator%3ALOCAL&reason=ADMIN_FORCED_PASSWORD_RESET_VIA_OTP
The following is the screenshot of the result obtained on the browser:

Replacing in the url of the error page the tenant carbon.super with our custom tenant ngdms.com, the first login with OTP works and, as showed in the following screenshot, it's possible to set a new password:

Why this replacing is necessary? I don't understand why carbon.super tenant is in the url instead of our custom tenant ngdms.com .
What can be done to fix it?
How to reproduce:

Create a service provider on carbon.super tenant (SaaS);
Create a custom tenant @ngdms.com;
Create an user<EMAIL_ADDRESS>in the custom tenant with OTP enabled;
Generate an OTP for the user<EMAIL_ADDRESS>Login with the user<EMAIL_ADDRESS>using the OTP.

Expected behavior:
The login using the OTP as password ends successful and then it's possible to create a new password.
Environment information:

Product Version: IS 5.11.0
OS: Mac
Database: PostgreSQL
Userstore: JPA

Optional Fields
Related issues:
https://github.com/wso2/product-is/issues/11555

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


generic noarch support

Hey folks, I'm going to be spitballing here, so please bear with me.
I've come to appreciate recently, thanks in part to @mingwandroid, that noarch: python packages are generally not a good idea yet. There are some reliability issues associated with them. The key detail is this: because the file layout for Windows and Unix differs, and because the file layouts differ with Python versions, these packages must programmatically put the files into their proper positions. This is of course as opposed to original-style, arch-dependent conda packages, which can simply be unpacked in place.
Now, noarch: generic packages are not like this: they assume that the file layout is platform independent. This is perfect for packages that truly can live in the same place on every installation.
What I'd like to suggest here, then, is that somehow Intake makes it possible to deploy its data packages as noarch: generic packages, even if they contain some sort of Python module inside of them. This would effectively mean that Intake is instructed to look in a particular location in addition to the standard Python path for such modules, a location that is fixed in the directory tree regardless of Python version and architecture.
Obviously, one general solution to the noarch: python problem would be that we could hack Python itself to look in an arch-independent location for site packages. That's not likely to happen. Doing this specifically for intake packages, however, seems like a prudent move, because I think we would really want to encourage data package builders to make them noarch of a sort.
I'm not sure how feasible this even is, though. I mean, it certainly breaks the clean python setup.py install approach to building the conda package in the first place. There would need to be some sort of special instruction for data packages to facilitate the placement of the files into the proper location.

Is it fair to say that the two-package approach (one for the data and catalog files), and one for the interpreter code, was conceived because of this issue? If so then basically what I'm proposing is a path to unifying those two packages into one. I'll take a look at those docs when I get the chance; my plane is in descent