Add New Item Signature Files Uses Wrong Element Type

Currently they're added as None

It should be Compile

This was fixed in 15.6.


Incorrect graph for node_disk_io_now

In the panel "Disk Detail" is a graph "Disk IOs Current In Progress".  The query it uses is:
irate(node_disk_io_now{instance=~"$node:$port",job=~"$job"}[5m])

However, node_disk_io_now is not a counter, it's a gauge:
# HELP node_disk_io_now The number of I/Os currently in progress.
# TYPE node_disk_io_now gauge

The io_now value is field 9 documented here:
Field  9 -- # of I/Os currently in progress
    The only field that should go to zero. Incremented as requests are
    given to appropriate struct request_queue and decremented as they finish.

Therefore I believe the irate(...) wrapper needs to be removed.  This is already an instantaneous snapshot of the outstanding I/O requests.

Thanks for pointing the issue, it's is fixed now.

I just checked the latest install of 1860 (node-exporter-full_rev23.json), and the panel Storage Disk > Instantaneous Queue Size still shows:
rate(node_disk_io_now{instance="$node",job="$job"}[$__rate_interval])

I believe it should be instead:
node_disk_io_now{instance="$node",job="$job"}

In addition:

The Y axis units are currently set to I/O ops/sec (iops); I think this should be Misc > none.  The metric is the queue depth, so it's "number of outstanding requests", which is dimensionless and definitely not a rate of any kind.
The Y axis label is set to "I/Os".  This is acceptable, as it can be interpreted as "number of I/Os", rather than "I/Os per second".  Maybe "Outstanding requests" would be better, but I don't mind too strongly.

The corrected panel would look like this:

This shows the number of active requests is either 0 or 1 at each sample time, which is correct.

(Aside: I can prepare a PR for this, but I have other graphs I want to check first)

Since I'm running Grafana 8.0.5, and the dashboard is for 7.3.7, the diffs turned out to be rather large, especially because large chunks of indentation have changed due to a change in panels/targets layout.
Probably best just to apply the two changes by hand:
-              "expr": "rate(node_disk_io_now{instance=\"$node\",job=\"$job\"}[$__rate_interval])",
+          "expr": "node_disk_io_now{instance=\"$node\",job=\"$job\"}",
...
-              "format": "iops",
+          "format": "none",

It was a regression on d52e0ec13cbd5bc916eedf6170f1ee99e914d889
Let me fix and check the other changes that you reported over the current dashboard.
Thanks Brian,


Feature Request : Tensor Roll

Could you add an equivalent to Numpy roll on Tensor in tensorflow in order to allow the user to roll a Tensor along one of the axis of the tensor.

We definitely would welcome pr's to implement this functionality. Thanks!

It should be easy to implement it using slice and concat. Does it need to be implemented in a C++ kernel?

Hello, I am new to open source and would like to implement this feature. How do I determine which file to implement this feature in?

Usually a feature like this will involve several files. The best thing to do is to look at a similar op (say, transpose, maybe), and find all the files that have to be touched for that op.
There will be at least some files in core/ops, core/kernels, and python/kernel_tests, plus the BUILD files.
If the op is a pure python op, you may get away with only changing/adding a file in python/ops. This is probably not a python op, unless I'm missing a simple way to construct it from existing ops.

I implemented that with existing TF operations, see here circular_pad.

I'd like try to implement this op. Should this go directly into core or somewhere in the contrib directory?

It's fine to put it in core I think, though not sure what module it should be in (tf.roll or tf.<something>.roll). Deferring to @aselle for placement.


(Fix) e2e tests with current changes on local deployment in Travis CI

e2e tests with current changes on local deployment in Travis CI

Pull Request Test Coverage Report for Build 1696

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

Totals

Change from base Build 1693:
0.0%

Covered Lines:
386

Relevant Lines:
1970

💛  - Coveralls

@dennis00010011b please let us know when e2e tests will be fixed. Then we will be able to merge this PR. And after it, e2e tests will be launching on the version of Wizard in PR, not on production link.


Command buffer submitted to wrong queue (Intel A770, Chapter 5)

When running on Intel A770, following core validation error is triggered in Chapter5:
VUID-vkQueueSubmit2-commandBuffer-03878(ERROR / SPEC): msgNum: -628003580 - Validation Error: [ VUID-vkQueueSubmit2-commandBuffer-03878 ] Object 0: handle = 0x22e857a8750, type = VK_OBJECT_TYPE_COMMAND_BUFFER; Object 1: handle = 0x22e853d52c0, type = VK_OBJECT_TYPE_QUEUE; | MessageID = 0xda916d04 | vkQueueSubmit2(): pSubmits[0].pCommandBufferInfos[0].commandBuffer Primary VkCommandBuffer 0x22e857a8750[] created in queue family 0 is being submitted on VkQueue 0x22e853d52c0[] from queue family 1. The Vulkan spec states: The commandBuffer member of any element of the pCommandBufferInfos member of any element of pSubmits must have been allocated from a VkCommandPool that was created for the same queue family queue belongs to (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/windows/1.3-extensions/vkspec.html#VUID-vkQueueSubmit2-commandBuffer-03878)
    Objects: 2
       [0]  0x22e857a8750, type: 6, name: NULL
       [1]  0x22e853d52c0, type: 4, name: NULL
A breakpoint instruction (__debugbreak() statement or a similar call) was executed in RaptorEngine_Chapter5_Debug.exe.

Command buffer created for universal queue is submitted to compute only queue.
Log regarding queues:
GPU Used: Intel(R) Arc(TM) A770M Graphics
Family 0, flags 15 queue count 1
Family 1, flags 2 queue count 1
Family 2, flags 4 queue count 1

Issue can be reproduced on NVidia by commenting those two lines (pretending that single universal queue is advertised):
        // Search for main queue that should be able to do all work (graphics, compute and transfer)
        if ( (queue_family.queueFlags & ( VK_QUEUE_GRAPHICS_BIT | VK_QUEUE_COMPUTE_BIT | VK_QUEUE_TRANSFER_BIT )) == ( VK_QUEUE_GRAPHICS_BIT | VK_QUEUE_COMPUTE_BIT | VK_QUEUE_TRANSFER_BIT ) ) {
            main_queue_family_index = fi;

            if ( queue_family.queueCount > 1 ) {
                // compute_queue_family_index = fi;
                // compute_queue_index = 1;
            }

            continue;
        }

After grepping the whole solution, I do not see vulkan_compute_queue_family being used anywhere,
Pool of vkCommandPools are created either for universal, or for transfer queues.

Thanks for merging.
Verified it with 47e8c21 on top.
Side note: On GPU's with no compute queue, there is crash when creating device.
The same is when you have two GPUs, and one without compute queue is picked.
(Family index passed is 0xFFFFFFFF)

Thanks, I'll have a look at this as well. I thought we had checks in place for that scenario, but clearly they don't cover all cases.


Update CI image before running tests

Context: Github Actions fail to install packages for older Ubuntu 18.04 images, with error messages matching the following pattern:
E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/main/c/cmake/cmake-data_3.10.2-1ubuntu<IP_ADDRESS>_all.deb  404  Not Found [IP: <IP_ADDRESS> 80]

It is necessary to update the base package list prior to installation of any dependencies.
Description of the Change: Add sudo apt-get update to Ubuntu 18.04 images.
Benefits: Github action fails no more.
Possible Drawbacks: None
Related GitHub Issues: None

Would an alternative to be just to specify to run on ubuntu-latest? We have a couple of other "Install dependencies" actions, but I guess they work because they use ubuntu-latest or ubuntu-20.04.

Yes, that may be the best idea. I didn't opt for this as it required a temporary deletion of the required tests in the the repo settings (explicitly listed 18.04 test), and then reinstate with the new version. I think updating to the 20.04 LTS release does make sense though. I'll update to this, and merged.


Added SuperJSON library

  Safely serialize JavaScript expressions to a superset of JSON, which includes Dates, BigInts, and more.

Key features

🍱 Reliable serialization and deserialization
🔐 Type safety with autocompletion
🐾 Negligible runtime footprint
💫 Framework agnostic
🛠 Perfect fix for Next.js's serialisation limitations in getServerSideProps and getInitialProps

Basic Usage
The easiest way to use Superjson is with its stringify and parse functions. If you know how to use JSON.stringify, you already know Superjson!
Easily stringify any expression you’d like:
import superjson from 'superjson';

const jsonString = superjson.stringify({ date: new Date(0) });

// jsonString === '{"json":{"date":"1970-01-01T00:00:00.000Z"},"meta":{"values":{date:"Date"}}}'

And parse your JSON like so:
const object = superjson.parse<
{ date: Date }
>(jsonString);

// object === { date: new Date(0) }

Advanced Usage
For cases where you want lower level access to the json and meta data in the output, you can use the serialize and deserialize functions.
One great use case for this is where you have an API that you want to be JSON compatible for all clients, but you still also want to transmit the meta data so clients can use superjson to fully deserialize it.
For example:
const object = {
  normal: 'string',
  timestamp: new Date(),
  test: /superjson/,
};

const { json, meta } = superjson.serialize(object);

/*
json = {
  normal: 'string',
  timestamp: "2020-06-20T04:56:50.293Z",
  test: "/superjson/",
};

// note that `normal` is not included here; `meta` only has special cases
meta = {
  values: {
    timestamp: ['Date'],
    test: ['regexp'],
  }
};
*/

Awesome, thank you @Hamza12700! +1 great library!


Changed remodel tool to use new instead of alloc,init

Changed remodel tool to use new instead of alloc,internalInit and then init
this PR eliminates 1 method (internal init) and makes the allocation of an object easier
the NS_UNAVAILABLE macros dont pick up the use ofnew here because the compiler cant see the type of casted (id)self

? ;)

Can you check the travis CI build? Seems like its not working

Looks like you need to update the acceptance tests. ./bin/runAcceptanceTests

ah I see the problem. I updated paths to be relative to %root%/bin/ but it should be relative to %root% - ill revert it

it doesnt run any unit tests if not run from ./bin but it only runs acceptance tests if not run from bin :D

travis doesnt like me: "There was an error while trying to fetch the log."

travis is green but half the test didnt run and some failed ;) our test setup only checks acceptance tests. buildtests fail :( unitTests are not run -- DONT accept this :)

Awesome, thanks for that! That helper method was somewhat of a hack.. so is the cast I guess, but that's way better :)


UI: Added Cards for Course Detail Page

Issue Number
fixes #5
Describe the changes you've made
Added a Card Component for Course Detail Page, also added a wrapper container for horizontal scrolling list.
Checklist

[x] My code follows the code style of this project.
[x] All new and existing tests passed.

@Abhishek-kumar09 @KeenWarrior Please review this PR.

@Abhishek-kumar09 I have copied the exact whole package-lock file from the repo's latest commit it still shows that it has been edited but has the exact same content now.


Some indexes could not be updated.

I get this error, how to fix it?
Some indexes could not be updated. Get "https://raw.githubusercontent.com/stm32duino/BoardManagerFiles/main/package_stmicroelectronics_index.json": dial tcp: lookup raw.githubusercontent.com: getaddrinfow: The requested name is valid, but no data of the requested type was found.: https://github.com/stm32duino/BoardManagerFiles/raw/main/package_stmicroelectronics_index.json

Hi @13992133
The file is simply hosted by GitHub. You probably have an issue with your network (proxy, antivir,...) or with Arduino IDE.
Unfortunately, we can't do nothing.


Build in Windows platform under Visual Studio prompt will fail

Build Environment:

scipy-0.17.0.tar.gz
In Windows platform, both Win8.1 and Win10
In Visual Studio 2012 prompt (Developer Command Prompt for VS2012)
Also put both "BLAS.lib" and "LAPACK.lib" into the Python libs path. These 2 libraries were downloaded from http://icl.cs.utk.edu/lapack-for-windows/lapack/
Build cmd:
Python setup.py build
Build Result:
...
...
Found executable C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\amd6
4\link.exe
_vq.obj : warning LNK4197: export 'init_vq' specified multiple times; using firs
t specification
Creating library build\temp.win-amd64-2.7\Release\scipy\cluster_vq.lib and o
bject build\temp.win-amd64-2.7\Release\scipy\cluster_vq.exp
_vq.obj : error LNK2019: unresolved external symbol __imp_free referenced in fun
ction __Pyx_ReleaseBuffer
_vq.obj : error LNK2019: unresolved external symbol __imp_malloc referenced in f
unction pyx_pf_5numpy_7ndarray___getbuffer
vq.obj : error LNK2019: unresolved external symbol sgemm referenced in functio
n __pyx_fuse_0__pyx_f_5scipy_7cluster_3_vq_cal_M
vq.obj : error LNK2019: unresolved external symbol dgemm referenced in functio
n __pyx_fuse_1__pyx_f_5scipy_7cluster_3_vq_cal_M
_vq.obj : error LNK2019: unresolved external symbol sqrt referenced in function
__pyx_fuse_0__pyx_f_5scipy_7cluster_3_vq__vq
_vq.obj : error LNK2001: unresolved external symbol _fltused
LINK : error LNK2001: unresolved external symbol _DllMainCRTStartup
build\lib.win-amd64-2.7\scipy\cluster_vq.pyd : fatal error LNK1120: 7 unresolve
d externals
error: Command "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\amd64
\link.exe /DLL /nologo /INCREMENTAL:NO /LIBPATH:C:\Software\SoftwareDev\Python27
\libs /LIBPATH:C:\Software\SoftwareDev\cygwin64\lib\gcc\x86_64-pc-cygwin\5.3.0 /
LIBPATH:C:\Software\SoftwareDev\Python27\libs /LIBPATH:C:\Software\SoftwareDev\P
ython27\PCbuild\amd64 /LIBPATH:C:\Software\SoftwareDev\Python27\PC\VS9.0\amd64 /
LIBPATH:build\temp.win-amd64-2.7 /LIBPATH:C:\Software\SoftwareDev\Python27\libs
/LIBPATH:C:\Software\SoftwareDev\Python27\PCbuild\amd64 /LIBPATH:C:\Software\Sof
twareDev\Python27\PC\VS9.0\amd64 /LIBPATH:build\temp.win-amd64-2.7 lapack.lib la
pack.lib blas.lib blas.lib /EXPORT:init_vq build\temp.win-amd64-2.7\Release\scip
y\cluster_vq.obj /OUT:build\lib.win-amd64-2.7\scipy\cluster_vq.pyd /IMPLIB:bui
ld\temp.win-amd64-2.7\Release\scipy\cluster_vq.lib /MANIFESTFILE:build\temp.win
-amd64-2.7\Release\scipy\cluster_vq.pyd.manifest" failed with exit status 1120

from the error log, I know that I may missing some dependent libraries, but I don't know what are they.

You need to use the same MSVC version as was used to build Python itself with. See http://mingwpy.github.io/issues.html#choice-of-msvc-runtime for which MSVC version matches your Python version.
Then keep in mind that you can only build Scipy with MSVC if you also have the Intel Fortran compiler.
Once you have those things right and still run into issues, please provide the complete build log.

@rgommers , got you, this time seems clear. I will have a try and thank you for your kind and clear explanation!

@kevin-coder @rgommers Hi everyone, I am getting into the same situation. So @kevin-coder did you get any luck on using the Intel Fortran compiler? or you have other suggestions?
What I would like to do is to build scipy for Python that is shipped with Autodesk Maya (2016). It is  Python 2.7.6 built with MSC v.1700 64 bit.

@paranoidpixel then you want to build with MSVC 1700 or icc + Intel Fortran, should work. Intel keeps their own build instructions quite well up-to-date: https://software.intel.com/en-us/articles/building-numpyscipy-with-intel-mkl-and-intel-fortran-on-windows

@rgommers thanks a lot for your prompt response! I will give it a try.

@rgommers Now I made it work and I can confirm the steps from the Intel link are good (and very easy to do as well). Thanks a lot.
p.s. The numpy can pass most of the tests, but the scipy can't. It will crash the interpreter before finishing. However I am able to use all the modules that I need (mostly linalg and sparse.linalg) and they works properly. I am suspicious because I am using a different version of Python include files and libraries (current the native Python 2.7 installed on my machine, it is because Autodesk Maya's release doesn't include the devel files). Maybe I should rebuild Python 2.7.6 from source and get those files.

I am suspicious because I am using a different version of Python include files and libraries (current the native Python 2.7 installed on my machine, it is because Autodesk Maya's release doesn't include the devel files).

Yes, that does sound like an unhealthy idea.

Maybe I should rebuild Python 2.7.6 from source and get those files.

If that doesn't solve the crash, you can open a new scipy issue (preferably with a gdb traceback).

@rgommers I have built Python 2.7.6 with the same compiler, scipy.test still crashes. Now I know the problem is at qhull, at scipy/spatial/tests/test_qhull.py. I am building a debug version of scipy to get more info out of it, however the building process stops at the following:
ifort.exe:f77: scipy\integrate\tests\banded5x5.f
ifort: command line error: option '/g' is ambiguous
error: Command "C:\Program Files (x86)\IntelSWTools\compilers_and_libraries\windows\bin\intel64\ifort.exe /nologo /MD /nbs/names:lowercase /assume:underscore /O1  -g -DSCIPY_MKL_H -DHAVE_CBLAS -I"C:\Program Files (x86)\IntelSWTools\compilers_and_libraries\windows\mkl\include" -Ibuild\src.win-amd64-2.7 -I"c:\Program Files\Autodesk\Maya2016\Python\lib\site-packages\numpy-1.12.0.dev0+b2d4951-py2.7-w
in-amd64.egg\numpy\core\include" -I"c:\Program Files\Autodesk\Maya2016\Python\include" -I"c:\Program Files\Autodesk\Maya2016\Python\PC" -c /c  scipy\integrate\tests\banded5x5.f /Fobuild\temp.win-amd64-2.7\Debug\scipy\integrate\tests\banded5x5.o" failed with exit status 1
Any thought on this?

So you got a bit further, past the cluster issue. The qhull crash is probably gh-6316, there's a proposed fix in https://github.com/scipy/scipy/issues/6316#issuecomment-229482576 that seems to work.

@rgommers yes I confirmed that solves the problem. Thank you very much!

Excellent. Thanks for the bug report and following up.


D203 and D211 are in conflict

I tried a lot of commits and changes to the code and then after googling I realized that it is mentioned in the pydocstyle issues that D203 and D211 i.e.
D203: 1 blank line required before class docstring1
D211: No blank lines allowed before class docstring
are conflicting and one of them should be disabled and hence any of the pull requests were not up to the standards and showing some or the other checks as failed.

@geekquad, @plazzy99 please look at this issue.

Hey @psyduck1203, the webhooks we were using were not trained and thus were throwing errors.
Please try again and you will be good to go.
Let me know if you face any difficulties.


Unable to check whether a RichTextBlock is empty

When you use RichTextBlock in a template – especially when it’s in a StructBlock – you sometimes need to do something like this:
{% if value.description %}

    {{ value.description }}

{% endif %}

However, the test always evaluates to True because value.description is a RichText object that only implements a __str__ method. This __str__ always returns at least '

'.
The solution is to add a __bool__ method like this:
    def __bool__(self):
        return bool(self.source)

Another solution may consist in adding this

 only if the block is not empty.

@BertrandBordage That makes sense, thanks! I wonder if this also affects our ability to set required=True...
(The one thing I'm not sure about - can we rely on the rich text widget to reliably return an empty string, rather than

? I guess that's something we can deal with separately, though.)

From what I saw in the current release (1.4rc1), saving an empty RichTextBlock always returns an empty string, but I know I saw the

 issue on RichTextField in the past. The solution would be to clean the field as I did in my projects, but we of course need to make this robust and handle similar cases like

,

,
[any space here, non-breaking, narrow non breaking, etc]
.

another awesome reason that HTML is a poor storage format for richtext.

@JoshBarr But if we store it in another format, we have to chose between these solutions:

parse HTML in order to store data, and a renderer for displaying it
directly store the non-HTML form (JSON), and render it in Python for the front office and JavaScript for the back office
directly store the JSON, and render it in Python on the front and back office, using AJAX for the back office while typing...

All three solutions will introduce more issues than fix. And I don't even think that would be easier to parse. HTML is complex and horrible for a reason: layout also is. How would you convert to JSON something as simple as this:
a b
?

Fixed in #2729

In case anyone's interested, we've worked around the

 stuff using a custom template tag:
from html.parser import HTMLParser
from django import template

register = template.Library()

class TextExtractor(HTMLParser):

    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.text = ""

    def handle_starttag(self, tag, attrs):
        return

    def handle_endtag(self, tag):
        return

    def handle_data(self, data):
        self.text += data

    @classmethod
    def extract_text(cls, data):
        self = cls()
        self.feed(data)
        self.close()
        return self.text

@register.filter
def dehtmlize(value):
    return TextExtractor.extract_text(value)

The html module is available only in Python 3. Use like this:
{% if value.content.source | dehtmlize %} ...


Comelit simplebus1 protocol

Ciao, great work!
My intercom uses Comelit simplebus1 protocol.
There's some work done by vvigilante https://github.com/vvigilante/comelit-simplebus1 to make it "smart".
Any chance your board could work with it? Thanks

Ciao giuppi!
As for the software, there is a development branch on this project that will be moved to Main in the next few days. It manages to perform simplebus 1 reading and decoding without problems
The transmission software part has also been implemented. I had to add an additional dedicated transmission stage to allow for much more energetic transmission that the Simplebus 1 requires.
The problem of the simplebus 1 is the power supply: during data transmission the bus is almost shorted and there is not enough residual power to power the wemos, for this reason the Simplebus 1 may need external power.
I have developed a new hardware version 2.6 which includes the new transmission section for SimpleBus 1, and a reception section with 9 selectable sensitivity levels, to allow the circuit to adapt to the various cases.
There is also a new pcb suitable for Simplebus 1 4-wire door phone kits (two for bus and two for 24V power supply)
In the next few days I will upload the updated documentation. Meanwhile, the first V2.6 PCBs are already under construction

Great news!
Thank for the detailed update.


Update EF to 6.5.1 to get a newer System.Data.SqlClient version

fix for #34

@jbogard Smth wrong with the Nuget API key?
Pushing AutoMapper.EF<IP_ADDRESS>.nupkg to 'https://www.nuget.org/api/v2/package'...
PUT https://www.nuget.org/api/v2/package/
Forbidden https://www.nuget.org/api/v2/package/ 247ms
error: Response status code does not indicate success: 403 (The specified API key is invalid, has expired, or does not have permission to access the specified package.).
https://github.com/AutoMapper/AutoMapper.EF6/actions/runs/10448484757/job/28929030874#step:5:12

Yep, it expired. I uploaded a new one, should be good now.


travis: Ensure quilt-tester files compile

@kklin Did you mean to include commit f073f29 ?

Sorry @luise, that commit was for testing Travis. I'll ping you when it's ready for review and I've removed the commit

ok @luise, it's ready


Issue credits to Evan

Issue 3000 credits to @gnomevan.

 Follow up
On Sunday, 24-Mar-24 03:17:46 UTC by Gov4Git dev
Issued 3000 credits to member @gnomevan.


Invalid comments just disappear

Describe the bug
Posting a comment on obs detail that is invalid removes all the text that you wrote, so you lose all your work
To Reproduce
Steps to reproduce the behavior:

Go to an observation detail page
Leave a comment that is more than 5000 characters
You'll get a validation error and then your comment will disappear

Expected behavior
I would expect my work not to be lost so I can edit it until it becomes valid
IMO, minimum fix would be

[ ] If a comment or ident is invalid on submission, leave the UI alone so the user can fix the problem
[ ] Don't allow text areas to have more text than is allowed

Ideally:

[ ] Have some UI-alert about validation issues like length when they happen, before submission. I'm not sure if a character count is necessary for comments, but maybe a notice or tip should appear when you exceed the limit.

FYI, this got rolled into Markdown support. Since tony requested that we wait for the apps to support Markdown before we start enabling / encouraging it on the web, this is currently pending completion of https://github.com/inaturalist/INaturalistIOS/issues/553 (pretty much supported in Android, just pending some QA / QC: https://github.com/inaturalist/iNaturalistAndroid/issues/809)

Can this be added to other comments, such as those on journal posts and flags?

What I did was add the hard cap on number of characters for the text area in the non-React identification editor, post editor, and comment field, but no additional warning UI.


Fixes libjpeg-turbo dependecy under Ubuntu 16.04

Description
Currently we cannot build mxnet on ubuntu 16.04 with USE_LIBJPEG_TURBO=1 because the library was compiled without PIC in the libturbo-jpeg library. Another package libjpegturbo fixes this issue.
see this.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes
Adds libjpeg-turbo dependency to ubuntu based builds appropriately.
Adds libjpeg-turbo flag to ubuntu builds. This is inline with the build flags used in the shipped version of mxnet, for instance,  see this.
Now the CI and CD will be slightly more congruent.

@perdasilva Thanks for your contribution!
@mxnet-label-bot [ pr-work-in-progress ]

@mxnet-label-bot [ pr-awaiting-review ]

@mxnet-label-bot remove [pr-work-in-progress]

Should we maybe only turn it on for a few builds to increase the diversity?

I'm happy to have it only for certain ones. Do you guys have any suggestions based on your experience?
I would just like to have as much parity as possible between what we test and what we ship.
Currently, LIB_JPEG_TURBO is enabled for the pip builds:
grep -r "TURBO" make/pip                                                                                ✘ 130 master ✭ ✱ ◼
make/pip/pip_linux_cpu.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu90.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu91.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu90mkl.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu80mkl.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu80.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu75mkl.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_mkl.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu92.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu100.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_darwin_mkl.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu100mkl.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_darwin_cpu.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu91mkl.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu75.mk:USE_LIBJPEG_TURBO = 1
make/pip/pip_linux_cu92mkl.mk:USE_LIBJPEG_TURBO = 1


ISPN-9863 Fix testsuite thread leaks

https://issues.jboss.org/browse/ISPN-9863
https://issues.jboss.org/browse/ISPN-8610
https://issues.jboss.org/browse/ISPN-9882
https://issues.jboss.org/browse/ISPN-9884
https://issues.jboss.org/browse/ISPN-9898
https://issues.jboss.org/browse/ISPN-9933

Rebased and added fix for https://issues.jboss.org/browse/ISPN-9933 + ignore thread leak caused by https://issues.jboss.org/browse/ISPN-9935

@danberindei It seems there are still some related failures.

I finally got back to this @ryanemerson
The unset-* "leaks" were from tests that didn't extend AbstractInfinispanTest and so never set the test name for the thread. The one in the router module was an actual leak in the test.

@danberindei So close! But SampleRemoteCacheTest.springTestContextAfterTestClass still has a leak.

@ryanemerson it wasn't a leak really, H2 starts a thread and only waits 400ms for it to finish (allegedly it normally takes < 200ms), so I added it to the whitelist in ThreadLeakChecker.

The new leak is caused by https://issues.jboss.org/browse/ISPN-9988, I'll fix it in a separate PR @ryanemerson

Soo many Jiras to resolve :smile: Thanks @danberindei

Yeah, this is one PR where I can really say that I did not intent for it to grow nearly as big :))
Thanks Ryan!


kernel: timer: Call user handler without spinlock

Add spinlock unlocking before calling timer expiration
handler. Locking was introduced by dde3d6c.
Fixes #40000.
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

@chen-png opened this before looking closer into your proposal. If simple unlocking is not enough i will close it.

@nordic-krch - it appears that this bug would also likely be in v2.7-branch. Is that correct?


New charts

Hey! Great library.
Would it be cool if I made a PR for some new charts at some point?
e.g.

scatter plot
waffle plot
box plot

Thanks for the interest! It is very welcomed. But currently there are some duplications and other issues in the code, I will tidy up the code as soon as possible.  When it is ready to accept PR I will inform you.
Is it OK to assign issues about the new chart types you mentioned?

@timqian no worries! And yes, feel free to tag me :)

@timqian if you want help, I would love to help out for a sankey diagram... not even sure what charting library you're using :)

@WriteCodeEveryday looks like everything is wrapping d3


change energy production to energy transformation

#77
Do we still need the issue after the merge?

@akleinau could you help me with the merge conflict?

I agree with @l-emele. You could delete it now temporarily and I can open a new issue for the subclasses with some ideas for them if you like.

Ok let's do that. I think, it is better to discuss the subclasses from scratch.

@akleinau could you help me with the merge conflict?
edit: I think I resolved it and hope that I didn't destroy even more...

I don't see any merge damage so must have worked fine :)


Feature/create delete components cu e53aej

After merging:

Correct placing of AddComponent() and ExistsComponent() inside GameObject.h and .cpp

I also corrected the ImGuizmo Scale task in the same push, as it was just a line.
Forced the popup windows to be unresizable.

¿Por qué has eliminado los CollapsingHeaders?

Los he generalizado en PanelInspector.cpp. Junto con el botón y popup de las Opciones de los components.


WIP #980 - Use undojoin + nvim_call_atomic for atomic undo

WIP for #980 to have rename (and other workspace edits, like formatting) undoable with a single gesture.

This solves the general case (at least, for a single file), but there is a problem if you undo and then start a new rename - we get an error that undojoin can't be called after an undo. We might need to find a way to clear the latest undo state, in this case?

Based on this thread: https://www.mail-archive.com/search?l=vim_dev@googlegroups.com&q=subject:"undojoin+after+an+undo"&o=newest&f=1
Seems like maybe silent! undojoin is a reasonable solution. It would ignore the error case, but still function correctly for the later cases.

Addresses #980 (at least for a single buffer)


Workflow

Description
This PR adds the ability to register a workflow to the database and pull options from the database if the workflow is already registered.
It also starts addressing torsions that are not fully rotatable.
Todos

[x] Register workflow to database
[x] Get options for functions from registered workflow
[x] Find torsions that are in double bonds and rings
[ ] Generate input for restricted torsion scans

Questions

[ ] How far should restricted torsion scans go out of equilibrium? Should that cutoff be different for double bond and rings?
[ ] What is the best workflow for restricted torsion scans? Should we generate the input configuration with OpenEye and then do a geometry optimization with the torsion restrained?

Status

[ ] Ready to go

@ChayaSt

@dgasmith, all tests pass locally. I commented out the workflow tests because those will rely on qcportal.

Codecov Report

Merging #19 into master will decrease coverage by 13.32%.
The diff coverage is 12.35%.


Wrap calls to choco install in Start-NativeExecution

Hi @vors, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Sergei Vorobev). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


[DOC] Add info on where to add additional compose file

simply ad an in .ddev/ to avoid confusion for new users where to place the additional docker-compose.mongo.yaml

Thanks!


assigned chirality wrongly (SDF -> SMILES)

I tried to distinguish these two molecules in a SDF file.

  C[C@@H](O)N

  5  4  0  0  0  0            999 V2000
    0.0000    0.0000    0.0000 C   0  0  2  0  0  0
    0.0000    0.0000    0.0000 C   0  0
    0.0000    0.0000    0.0000 N   0  0
    0.0000    0.0000    0.0000 O   0  0
    0.0000    0.0000    0.0000 H   0  0
  1  2  1  0
  1  3  1  0
  1  4  1  0
  1  5  1  1
M  END

$$$$

  C[C@H](O)N

  5  4  0  0  0  0            999 V2000
    0.0000    0.0000    0.0000 C   0  0  1  0  0  0
    0.0000    0.0000    0.0000 C   0  0
    0.0000    0.0000    0.0000 N   0  0
    0.0000    0.0000    0.0000 O   0  0
    0.0000    0.0000    0.0000 H   0  0
  1  2  1  0
  1  3  1  0
  1  4  1  0
  1  5  1  1
M  END

$$$$

these two molecules have different chirality (expressed as an atom information), however, MolToSmiles(mol, isomericSmiles=True) shows same results.
I also checked openbabel's output, it returns different chirality.
My environment is:

RDKit Version: 2017.09.2
Python Version: 2.7.13 (Anaconda custom (64-bit))
Platform: Linux (SUSE Linux Enterprise Server 12 SP2)

It would be relatively easy to support this flag in cases where the coordinates are all zero, but it's not currently done.

Thank you for your comment. I understand RDKit does not parse it currently.
I faced the problem when I parse a compound library provided by a compound vendor, thus I hope RDKit will support it.


Use autogenerated slug+shorthash on question urls

tasks

create a slug db prop as index
on thread creation generete slug with format ${toSlug(question)}-${nanoid()}. both imported from lib
update getThreadLink
update (browse)/category/[threadId]/page to query using slush
use supabase server client

Update:
I am closing this issue for the following reasons:

The MB Search Branch is no longer in the route path.
The MB alpha branch is no longer in the route path.

Note: A similar strategy is already on the current route path


Disable staging-fuel.ignitionrobotics.org test

Summary
Disables tests being caused by https://github.com/gazebosim/gz-fuel-tools/issues/254.
Checklist

[x] Signed all commits for DCO
[x] Added (actually removed) tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Forward port to Fortress in

https://github.com/gazebosim/gz-fuel-tools/pull/260


Download/pdf.html.twig needs html tag

Just a little thing:
InvoicingPlugin/src/Resources/views/Invoice/Download/pdf.html.twig
To work with footer and header there must be the <!DOCTYPE html> tag.
With footer and header - there will be errors in rendering the *pdf. Like no header, but footer or no footer, but header or all white.... especially if there is lot of content (more than one side).
{% set shopBillingData = invoice.shopBillingData %}
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="utf-8">
    <style>

Hello TELLO0815!
I've read a bit of knp_snappy-related issues and it's a known issue of this package. I'm afraid that it's impossible to avoid it for now.


Implement quick movement for system navigation

Adding a fixed scrollbar to quickly move to a given section, and adding page up/page down actions will greatly improve the speed at which users traverse large libraries.

Tackled with #44.


Add async Python HTTP Clients

At the moment only sync Python HTTP clients is defined as bot, in this PR, I add detection of async clients aiohttp and httpx.

Thanks a lot for your contribution!

Thanks a lot for your contribution!


Update to 2024 beta

Update requirement.txt and Pipfile to use the 2024 version of imported modules. (Not phoenix 6)

I'm not sure what to do with the CTRE current version number. I thought the 2024 is now called phoenix6, and we are using that later. If we use the 2023.1.0 CTRE it would have conflict with other dependencies as all the other dependencies it requires are 2023. (obviously)

I'm not sure what to do with the CTRE current version number. I thought the 2024 is now called phoenix6

We need to update to the 2024 beta version of Phoenix 5 first.

Robot moves in sim


fix(chat): GPT model answer on wrong questions if use it after the model/application/addon with custom content (Issue#1024)

Description:
Revert messages array in the hardLimitMessages function to forth it to take latest user message instead of first.
Issues:

Issue #1024

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

Hey there and thank you for opening this pull request! 👋🏼
We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Details:
No release type found in pull request title "Fix/1024 gpt model answer on wrong questions". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - fix
 - hotfix
 - feat
 - feature
 - chore

/deploy-review


select the cell by using api

select the cell by using api, need a api select the cell for quick movement instead of cell.

@gudipudipradeep you can just use this api
https://ruilisi.github.io/fortune-sheet-demo/?path=/story/api--set-selection

@gazedreamily  How we can make sure as part of sheet loading as selected column. like open any excel sheet first column as selected column

@gudipudipradeep Sorry, I can't understand it

we close this. @gazedreamily


SVG  issue

In case an inline SVG has a  element, smoothState won't load the content of the SVG ( will be empty) and will append that title's content to the page title.

I can reproduce this problem.

@FabianGabor @webholics fixed! Closing, for now, but let me know if this is still an issue.


Failing to download from nvd.nist.gov due to certificate error

Describe the bug
OWASP Dependency check failing and giving error that unable to download files because of some certificate error mentioned below thread.
$ wget -c https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.meta
--2023-07-21 06:43:24--  https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.meta
Resolving nvd.nist.gov (nvd.nist.gov)... <IP_ADDRESS>, 2600:1f18:268d:1ddd:fd96:dcaa:cf17:f2b2
Connecting to nvd.nist.gov (nvd.nist.gov)|<IP_ADDRESS>|:443... connected.
ERROR: The certificate of 'nvd.nist.gov' is not trusted.
ERROR: The certificate of 'nvd.nist.gov' doesn't have a known issuer.

Version of dependency-check used
dependency-check-maven:8.3.1
Log file

[ERROR] Unable to continue dependency-check analysis.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  04:38 min
[INFO] Finished at: 2023-07-21T13:36:06Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.owasp:dependency-check-maven:8.2.1:check (default) on project core: Fatal exception(s) analyzing core: One or more exceptions occurred during analysis:
[ERROR] 	UpdateException: Unable to download meta file: https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.meta
[ERROR] 		caused by DownloadFailedException: Download failed, unable to retrieve 'https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.meta'; Error downloading file https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.meta; unable to connect.
[ERROR] 		caused by DownloadFailedException: Error downloading file https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.meta; unable to connect.
[ERROR] 		caused by SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[ERROR] 		caused by ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[ERROR] 		caused by SunCertPathBuilderException: unable to find valid certification path to requested target
[ERROR] 	NoDataException: No documents exist

To Reproduce
Steps to reproduce the behavior:
wget -c https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.meta
--2023-07-21 06:43:24--  https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.meta
Resolving nvd.nist.gov (nvd.nist.gov)... <IP_ADDRESS>, 2600:1f18:268d:1ddd:fd96:dcaa:cf17:f2b2
Connecting to nvd.nist.gov (nvd.nist.gov)|<IP_ADDRESS>|:443... connected.
ERROR: The certificate of 'nvd.nist.gov' is not trusted.
ERROR: The certificate of 'nvd.nist.gov' doesn't have a known issuer.

Expected behavior
While running the jenkins the toll should able to download the mentioned files from nvd.nist.gov site.

Looks like you rin in an environment that doesn't have CA trust for NVD's CA (Let's Encrypt R3, signed by ISRG Root X1)

@mandarpimplapure That image works perfectly fine in my direct-connected environment
root@8cd2a4cbc2d9:/# wget -c https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.meta
--2023-07-28 13:56:34--  https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.meta
Resolving nvd.nist.gov (nvd.nist.gov)... <IP_ADDRESS>, 2600:1f18:268d:1ddd:fd96:dcaa:cf17:f2b2
Connecting to nvd.nist.gov (nvd.nist.gov)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 162 [text/plain]
Saving to: ‘nvdcve-1.1-modified.meta’

nvdcve-1.1-modified 100%[===================>]     162  --.-KB/s    in 0s

2023-07-28 13:56:34 (12.6 MB/s) - ‘nvdcve-1.1-modified.meta’ saved [162/162]

So best guess is that your container environment is somehow routing through a TLS-intercepting man-in-the-middle proxy
Can you check on your side the output of
openssl s_client -connect nvd.nist.gov:443 -showcerts
The expected output is
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = *.nist.gov
verify return:1
---
Certificate chain
 0 s:CN = *.nist.gov
   i:C = US, O = Let's Encrypt, CN = R3
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
 1 s:C = US, O = Let's Encrypt, CN = R3
   i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
---
Server certificate
subject=CN = *.nist.gov

issuer=C = US, O = Let's Encrypt, CN = R3

---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA-PSS
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 4576 bytes and written 384 bytes
Verification: OK
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 2048 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
---
...


Expose container hostname

I've got an LXC image named centos6 and run it as lxc start centos6, and hostname from inside also prints centos6, but.. I can not use this name to ping container from the host. Only copy/pasting IP from lxc list works:
➜ ping centos6
ping: centos6: Name or service not known
➜ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.

Is it possible to expose container hostname for easy access?

Short answer, no. Long answer is that it depends on your DNS resolver, NSS config and a bunch more things.
@simos' blog post is a good starting point: https://blog.simos.info/how-to-use-lxd-container-hostnames-on-the-host-in-ubuntu-18-04/

Why shouldn this work?
lxc list
+-------------+---------+-----------------------+-----------------------------------------------+------------+-----------+
|    NAME     |  STATE  |         IPV4          |                     IPV6                      |    TYPE    | SNAPSHOTS |
+-------------+---------+-----------------------+-----------------------------------------------+------------+-----------+
| bckp-cont01 | RUNNING | <IP_ADDRESS> (eth0)   |                                               | PERSISTENT | 0         |
+-------------+---------+-----------------------+-----------------------------------------------+------------+-----------+

ping bckp-cont01
PING bckp-cont01.lxd (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.076 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.115 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.091 ms
^C


/* stylelint-disable */ doesn't work

I am running the pure setup from the readme and due to #55 I want to temporarily disable the rule, but this doesn't seem to work either?
I admit this is also my first time using stylelint, but I have checked quite thoroughly and it seems that I'm doing everything right, and the most likely thing is that it's this parser causing trouble?
Here is my code that acts up with
 11:3  ✖  Unexpected duplicate "undefined"   declaration-block-no-duplicate-properties
 12:3  ✖  Unexpected duplicate "undefined"   declaration-block-no-duplicate-properties

:
/* stylelint-disable declaration-block-no-duplicate-properties */
import React from 'react';
import styled from 'styled-components';

import { media } from '/styles/functions';

const Wrapper = styled.div`
  color: ${props => props.theme.gnarlesGreen};
  background-color: blue;
  ${media.desktop`background-color: red;`}
  ${media.tablet`background-color: yellow;`}
  ${media.phone`background-color: purple;`}
`;

export default () => <Wrapper>Hello World!</Wrapper>;

Hi @emilgoldsmith. The stylelint comments can only be picked up by stylelint if you put them with your css rules like so:
import React from 'react';
import styled from 'styled-components';

import { media } from '/styles/functions';

const Wrapper = styled.div`
  /* stylelint-disable declaration-block-no-duplicate-properties */
  color: ${props => props.theme.gnarlesGreen};
  background-color: blue;
  ${media.desktop`background-color: red;`}
  ${media.tablet`background-color: yellow;`}
  ${media.phone`background-color: purple;`}
`;

export default () => <Wrapper>Hello World!</Wrapper>;

That should solve it.

Okay thanks, should I just submit a quick PR that adds that to the readme?

@emilgoldsmith Ah yes that would be nice. Thanks!


AdMob Rewarded Video (Help!!!!)

here is my code
func adMobDidRewardUser(rewardAmount rewardAmount: Int) {
       let rewardAmount = 20

       let defaults = NSUserDefaults.standardUserDefaults()
       var Rounds = defaults.integerForKey("Currency") as Int

       Rounds += rewardAmount

       defaults.setValue(Rounds, forKey: "Currency")
       defaults.synchronize()
   }

i don't get the rounds

i got a question, if i make a rewarded interstitial ad on admob and use that adunitid. do you see a video ad then

Hey,
If you are in test mode and use the testAdUnitID than you get a black screen. I haven't figured out a way yet to test reward videos.
To use them you need a mediation partner, (I use Chartboost) because adMob itself does not offer reward videos. I am explaining this in the instructions.

how do i use chartboost i have made a account on it and a "app" on chartboost

with admob

Read the instructions on their website and on AdMobs website, there are links in the instructions. You cannot expect me too remember all or read through it again. You will have to do some work yourself.

https://firebase.google.com/docs/admob/ios/mediation-networks
https://firebase.google.com/docs/admob/ios/rewarded-video
https://answers.chartboost.com/hc/en-us/articles/209756523-Mediation-AdMob

yeah know that but i only can code swift i do not understand any objective-c

There is no coding with mediation. You need to sign up for Chartboost and install the SDK in your project. Than you need to read the AdMob instructions to set up Chartboost as mediation network.

i have imported the chart boost but i do not understand what i have do do now

do i have need to do this
# Chartboost for iOS

*Version 6.4.4*

The Chartboost iOS SDK is the cornerstone of the Chartboost network. It
provides the functionality for showing interstitials, More-Apps pages, and
tracking in-app purchase revenue.

### Usage

Integrating Chartboost takes two easy steps:

 1. Add the Chartboost.framework into your Xcode project's Frameworks folder.

 2. Instantiate the Chartboost SDK in your application AppDelegate.m, like this:

 ```objective-c
     #import <Chartboost/Chartboost.h>

     - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
     {
         // initialize the Chartboost library
         [Chartboost startWithAppId:@"YOUR_CHARTBOOST_APP_ID"
         			  appSignature:@"YOUR_CHARTBOOST_APP_SIGNATURE"
         			      delegate:self];

         // Show an interstitial ad
         [Chartboost showInterstitial:CBLocationHomeScreen];
     }

It is NOT RECOMMENDED that you call:

+ (void)showInterstitial:(CBLocation)location;

from within your AppDelegate's:
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions;

as depicted above.  It is shown as is for example purposes only.
Dive deeper
For more common use cases, visit our online documentation.
Check out our header file Chartboost.h for the full API
specification.
If you encounter any issues, do not hesitate to contact our happy support team
at<EMAIL_ADDRESS>

https://firebase.google.com/docs/admob/ios/mediation#1_integrate_admob_ads
https://answers.chartboost.com/hc/en-us/articles/205853276-Download-Integrate-the-Chartboost-SDK-for-iOS-Swift
In the chartboost instructions you can ignore step 4 and 5.

You can google this yourself because thats what I am doing.

i doing that the whole time

thanks i doesn't saw that you can scroll down on the chart boost page

#facepalm

thanks again

No worries. It took me a while to figure it out myself. I am no expert in this I can only follow the instructions as well.

I have the video working but when it's ended i dont get a reward

I gonna type my code tomorrow (it's night where i live)

You need to call AdMob.sharedInstance.delegate = self in your relevant SKScenes DidMoveToView

or the delegate and thus the protocol method adMobDidRewardUser will not get called

That not needed anymore but i tryed that but then for chartboost

Yes it is needed. This is how protocols work in swift

Do you know a code for that (in swift for chartboost)

You have code for chartboost?

Yes but i use chartboost now for rewarded video

Srry bad english

you are not listening to me so I am getting frustrated now. The AdMob code for reward videos will only work with Mediation (mediation is another adProvider such as Chartboost). If you set up mediation correctly you can use the AdMob code to show the Chartboost reward code.
If you are using Chartboost code than you need to use their methods.
In my 2 games on the appStore I have 4 adProviders in total. AdMob is the main one and the other 3 is used with mediation through AdMob (Chartboost, AppLovin and iAd). I only use the AdMob code.
If I dont use mediation I would need to use code for all 4 and clearly thats not good.
If you want help for Chartboost code than you need to read their documents. With this helper I dont want to use different code, I just want to use the adMob.swift code for iOS

Ok :)

I dont recomment that you use the chartboost code. Go to your adMob account and add an mediation partner to your current app. Its quite easy.
Your way is fine but than you will have to manager AdMob code, Chartboost code and eventually in the future you will have a mess.
Read this again
https://support.google.com/admob/answer/3124703?hl=en-GB&ref_topic=3063091
https://support.google.com/admob/answer/3063564?hl=en-GB

i have the adapter installed and all the SDKs

And? Whats the issue? You need to now go to your adMob account and add Chartboost reward videos to your app. Than you need to run your app in release mode to test the ads as adMob will only show a black screen when testing reward Videos.

thanks thats what i want to know

In the build menu where you are selecting your devices to test you can click edit Scheme at the bottom.
On the left side bar select run and than on the right at the top go to the info tab. There you can change your target from Debug to Release. You want to test your app in general there before you release it.


BFS benchmarks implemented

JET is not precompiling for some reason, I removed it from the tests for now


Installation and operation

Thanks for your efforts in developing TensorFlowOnSpark and making it opensource. I have two doubts regarding this new confluence of 2 most popular paradigms:-

Would my cluster work if have only Spark and Tensorflow without Hadoop?

How does the cluster behave if one of the node fails? Would the whole operation fail or is the cluster fault-tolerant?

@chaitanya2692 Very good questions.

TFoS should work without Hadoop, although we have not verify such settings. You could try it per GetStarted_standalone.

The answer to your 2nd question really depends on the usage. If you are using TFoS CLI, a server failure should be recovered by Spark. TFoS Python API level, however, might not be able to deal with such failures.

I just confirmed that TFoS works without hadoop. See the revised GetStarted_standalone. We will also remove some unwanted script from repo (PR #27).

I close this issue now that we have updated user guide w/o Hadoop dependency. For general discussion, please use mailing list.


无法恢复系统 默认文件资源管理器

Description

Files 版本：<IP_ADDRESS>
windows版本信息

版本	Windows 10 专业版
版本号	22H2
安装日期	2021/9/15
操作系统内部版本	19045.3693
体验	Windows Feature Experience Pack 1000.19053.1000.0

在Files -- 设置 -- 高级选项 -- 把 将Files设置为默认文件管理器 打开了；之后关闭了；系统无法恢复默认的文件管理器
尝试了 #7210 问题的所有方法了，都无法恢复系统默认的文件管理器
求助 我应该怎么恢复回来，使用win10 默认的文件管理器

Steps To Reproduce

Files 版本：<IP_ADDRESS>
windows版本信息

版本	Windows 10 专业版
版本号	22H2
安装日期	2021/9/15
操作系统内部版本	19045.3693
体验	Windows Feature Experience Pack 1000.19053.1000.0

在Files -- 设置 -- 高级选项 -- 把 将Files设置为默认文件管理器 打开了；之后关闭了；系统无法恢复默认的文件管理器
尝试了 #7210 问题的所有方法了，都无法恢复系统默认的文件管理器
求助 我应该怎么恢复回来，使用win10 默认的文件管理器

Requirements

e.g. Fix crash that occurs when...

Files Version
<IP_ADDRESS>
Windows Version
10.0.19045.3693
Log File
2023-11-17 14:46:31.1594|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 14:46:31.3774|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 14:46:53.1447|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 14:46:53.2431|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 14:48:47.8054|Information|App activated. Activated args type: IInspectable
2023-11-17 16:32:07.7802|Information|App activated. Activated args type: IInspectable
2023-11-17 16:32:52.0469|Information|STORE: Checking for updates...
2023-11-17 16:32:52.2854|Information|App activated. Activated args type: LaunchActivatedEventArgs
2023-11-17 16:32:55.2352|Warning|repository path 'Y:/h700/longan/' is not owned by current user
2023-11-17 16:32:55.4274|Warning|repository path 'Y:/h700/longan/' is not owned by current user
2023-11-17 16:32:56.7224|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 16:32:56.8019|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:02:20.3379|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:02:20.3762|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:02:26.5662|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:02:26.6360|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:02:30.7252|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:02:30.7837|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:02:32.9959|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:02:33.2525|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:36:35.4322|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:36:35.4555|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:36:43.1111|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:36:43.2479|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:36:50.8563|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:36:50.9426|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:36:54.8436|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:36:54.8873|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:36:58.7278|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-17 18:36:58.7968|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:11.6089|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:11.6703|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:13.8294|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:14.5684|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:30.7796|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:30.8793|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:34.7202|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:34.7572|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:39.5469|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:39.5874|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:53.3770|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:18:53.4140|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:23:35.7794|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:23:35.8033|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:23:49.2236|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:23:49.3210|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:23:51.1181|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:23:51.4331|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:23:57.6744|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:23:57.7124|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:23:59.1092|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:23:59.1658|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:24:10.5006|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:24:10.5324|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:24:25.9894|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:24:26.0701|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:25:12.9895|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:25:13.0519|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:44:34.9998|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:44:35.0457|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:44:38.2400|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 10:44:38.2849|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 15:45:50.2493|Information|App activated. Activated args type: IInspectable
2023-11-18 15:46:38.9917|Information|App activated. Activated args type: IInspectable
2023-11-18 17:52:30.8011|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 17:52:30.8075|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 17:52:34.2760|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 17:52:34.3536|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 17:52:39.0065|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 17:52:39.0254|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 17:52:44.6844|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 17:52:44.7056|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 17:52:47.7385|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 17:52:47.7534|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-18 17:53:03.8173|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 11:17:16.1722|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 11:17:16.1796|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 11:17:22.6827|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 11:17:22.7183|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 11:17:26.1099|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 11:17:26.1396|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 15:24:58.6907|Information|App activated. Activated args type: IInspectable
2023-11-20 15:30:24.1365|Information|App activated. Activated args type: IInspectable
2023-11-20 15:30:24.4229|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 15:30:24.8893|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:03:24.9718|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:03:25.0624|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:03:27.6968|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:03:27.7525|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:04:18.7322|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:04:19.1569|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:05:49.6604|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:05:49.7143|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:05:52.7950|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:05:52.8746|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:10:08.2396|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:10:08.2914|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:10:14.9181|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:10:14.9851|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-20 17:52:21.2191|Information|App activated. Activated args type: IInspectable
2023-11-21 09:31:00.1869|Information|App launched. Launch args type: LaunchActivatedEventArgs
2023-11-21 09:31:07.9544|Information|Adding cloud provider "OneDrive" mapped to C:\Users\MK\OneDrive
2023-11-21 09:31:09.0290|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 09:31:09.0619|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 09:31:09.1089|Information|Running on ARM: False
2023-11-21 09:31:11.2811|Information|App activated. Activated args type: IInspectable
2023-11-21 09:31:13.7636|Warning|repository path 'Y:/h700/longan/' is not owned by current user
2023-11-21 09:31:14.1168|Warning|repository path 'Y:/h700/longan/' is not owned by current user
2023-11-21 09:31:20.9662|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 09:31:21.0718|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 09:31:22.8682|Information|Drive added: C:\, Fixed
2023-11-21 09:31:23.0937|Information|Drive added: D:\, Fixed
2023-11-21 09:31:23.1942|Information|Drive added: H:\, Fixed
2023-11-21 09:31:23.2351|Information|Drive added: I:\, Fixed
2023-11-21 09:31:23.2920|Information|Drive added: W:\, Network
2023-11-21 09:31:23.3418|Information|Drive added: Y:\, Network
2023-11-21 09:31:23.3877|Information|Drive added: Z:\, Network
2023-11-21 09:31:27.1293|Information|STORE: Checking for updates...
2023-11-21 09:37:16.2644|Error|System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. ()
 ---> System.Runtime.InteropServices.COMException (0x80240438)
   at Files.App.Services.UpdateService.GetUpdatePackagesAsync()
   at Files.App.Services.UpdateService.CheckForUpdatesAsync()
   at Files.App.App.CheckForRequiredUpdatesAsync()
   at Files.App.App.InitializeAppComponentsAsync()
   --- End of inner exception stack trace ---
2023-11-21 11:23:44.8767|Information|App activated. Activated args type: IInspectable
2023-11-21 11:23:51.2373|Information|App activated. Activated args type: IInspectable
2023-11-21 14:06:18.4237|Information|STORE: Checking for updates...
2023-11-21 14:06:18.8078|Information|App activated. Activated args type: LaunchActivatedEventArgs
2023-11-21 14:06:20.8308|Warning|repository path 'Y:/h700/longan/' is not owned by current user
2023-11-21 14:06:22.1918|Warning|repository path 'Y:/h700/longan/' is not owned by current user
2023-11-21 14:06:27.8348|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:06:27.9475|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:06:31.8682|Information|Files.App.Launcher updated.
2023-11-21 14:06:47.9161|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:06:47.9574|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:12:34.8961|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:12:34.9366|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:12:39.7417|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:12:39.7821|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:12:42.1999|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:12:42.2541|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:12:46.4343|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:12:46.4835|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:14:25.3322|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:14:25.3872|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:14:30.7516|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:14:30.8160|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:14:55.4168|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:14:55.5205|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 14:36:56.9624|Information|App activated. Activated args type: IInspectable
2023-11-21 14:37:02.4185|Information|App activated. Activated args type: IInspectable
2023-11-21 14:39:37.1195|Information|App activated. Activated args type: IInspectable
2023-11-21 15:10:52.0578|Information|STORE: Checking for updates...
2023-11-21 15:10:52.4260|Information|App activated. Activated args type: LaunchActivatedEventArgs
2023-11-21 15:10:52.9423|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 15:10:53.0306|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 15:11:32.1774|Information|STORE: Checking for updates...
2023-11-21 15:11:32.3948|Information|App activated. Activated args type: LaunchActivatedEventArgs
2023-11-21 15:11:32.8974|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 15:11:33.1804|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 15:13:07.8327|Information|App activated. Activated args type: IInspectable
2023-11-21 16:21:14.4309|Information|STORE: Checking for updates...
2023-11-21 16:21:14.8491|Information|App activated. Activated args type: LaunchActivatedEventArgs
2023-11-21 16:21:15.5929|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 16:21:15.6981|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 16:29:20.4439|Information|STORE: Checking for updates...
2023-11-21 16:29:20.6366|Information|App activated. Activated args type: LaunchActivatedEventArgs
2023-11-21 16:29:21.3399|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 16:29:21.4317|Warning|repository path 'H:/easitek/' is not owned by current user
2023-11-21 16:40:29.1680|Information|App activated. Activated args type: IInspectable
2023-11-21 16:40:35.5131|Information|App activated. Activated args type: IInspectable
2023-11-21 16:40:38.0276|Information|App activated. Activated args type: IInspectable
2023-11-21 16:40:42.9292|Information|App activated. Activated args type: IInspectable
2023-11-21 16:40:45.7452|Information|App activated. Activated args type: IInspectable
2023-11-21 16:40:51.8998|Information|App activated. Activated args type: IInspectable
2023-11-21 16:42:48.1247|Information|App activated. Activated args type: IInspectable
2023-11-21 16:42:56.4242|Information|App activated. Activated args type: IInspectable
2023-11-21 16:43:04.8695|Information|App activated. Activated args type: IInspectable

Download UnsetFilesAsDefault.zip > Extract and run > See if you can open Windows File Explorer from the start menu.

我的问题解决了，我自己的问题。是我打开File的同时也打开了Q-Dir 这个软件导致的，使用#7210  提供的方法修改注册表，然后在Q-Dir文件中进行如下设置

下面截图的 全部都不勾选就可以恢复默认的文件管理器了


[WIP] [POC] Flight SQL

Introduction
This proof-of-concept in progress illustrates how Flight SQL can be implemented. This follows designs proposed in the Flight SQL proposal socialized last year. You can find the original proposal here. Since this is still a proof-of-concept, design feedback and suggestions are very much appreciated.
An Overview of this PR

This PR adds a new module within Flight called flight-sql.
flight-sql is a new Flight API that provides a standard way for clients and servers to communicate with SQL-like semantics.
Like other Flight APIs, flight-sql does not provide implementation details that dictate how a client and server communicates with each other, it simply provides the SQL semantics and apply them onto the Flight API.

A Walkthrough of the New Module

FlightSQL.proto introduces new SQL protobuf objects.
FlightSQLProducer introduces a new FlightProducer API that adapts classic Flight requests into SQL operations.
FlighSQLExample is a sample FlightSQL server implementation.

As a proof-of-concept, this isn't complete yet. There are a few TODO items:

FlightSQLExample is not completed yet.
As of now, all flight-sql client related operations are I FlightSQLClientUtils. I would like to break this utility class apart and offer an API for a FlightSQLClient add-on.

Small style nit:  Generally camel casing even for acronyms is preferred.

Small style nit:  Generally camel casing even for acronyms is preferred.

Thank you for the PR.  I think since there isn't a fully implementation example yet for the all the features it would make this easier to review if we cut down the FlightSql proto to what is implemented and focus on each use-case in a separate PR.  I think it makes sense to handle read, write and metadata operations separately?

Like other Flight APIs, flight-sql does not provide implementation details that dictate how a client and server communicates with each other, it simply provides the SQL semantics and apply them onto the Flight API.

IMO, I think we should be be trying to specify more about how client and server interact with each other in terms of error handling and retries, these are important aspects and without it I think some of the utility of standardization will be diminished.

Thank you for the PR.  I think since there isn't a fully implementation example yet for the all the features it would make this easier to review if we cut down the FlightSql proto to what is implemented and focus on each use-case in a separate PR.  I think it makes sense to handle read, write and metadata operations separately?

Like other Flight APIs, flight-sql does not provide implementation details that dictate how a client and server communicates with each other, it simply provides the SQL semantics and apply them onto the Flight API.

IMO, I think we should be be trying to specify more about how client and server interact with each other in terms of error handling and retries, these are important aspects and without it I think some of the utility of standardization will be diminished.

Thinking about this a bit more I think an alternative to a lot of the metadata querying is to define a minimal sql table schema and querying capabilities for it.  I'll expand more in a little bit

Thinking about this a bit more I think an alternative to a lot of the metadata querying is to define a minimal sql table schema and querying capabilities for it. I'll expand more in a little bit

I did a rough sketch on how the metadata layer could be modeled as pseudo-columns as comments on the proto.  I think this addresses some uneasiner I had with the existing model:

It uses one consistent data model for tabular data (the arrow model).
It makes query semantics clearer instead of trying to model them in an ad-hoc manner through protobufs

This comes at slightly more complex for server implementations.  And potential confusion on limitations for specific tables.  This might be limited to some extend if we had a different GetMetadata action so implementations know to expect a query to specific pseudo-table.  I expect we would provide library wrappers over JDBC to also ease implementation.

This comes at slightly more complex for server implementations. And potential confusion on limitations for specific tables. This might be limited to some extend if we had a different GetMetadata action so implementations know to expect a query to specific pseudo-table. I expect we would provide library wrappers over JDBC to also ease implementation.

We don't have a GetMetadata action, but we could encode it in GetFlightInfo by sending a different command payload. That would let us cleanly namespace the special tables and the actual tables.

We don't have a GetMetadata action, but we could encode it in GetFlightInfo by sending a different command payload. That would let us cleanly namespace the special tables and the actual tables.

Sorry need to reacquaint myself with all the flight specific nomenclature, this sounds like what I was thinking.

Following up here @tifflhl, is there interest in trying to get this in for 5.0.0 perhaps?

Hi David,
Our resources are a bit limited right now and can't really say if we would
have the bandwidth to work on flight-sql for v5.0.0. When we have some more
clearance on when the work can resume, we will definitely notify the dev
mailing list.
Cheers,
Tiffany
On Wed, Apr 14, 2021 at 11:03 AM David Li @.***> wrote:

Following up here @tifflhl https://github.com/tifflhl, is there
interest in trying to get this in for 5.0.0 perhaps?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/arrow/pull/9368#issuecomment-819722798, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB35GBV4LK7XPD6SBK7VEWLTIXKGPANCNFSM4WZ2VVYA
.

--
Tiffany Lam (She/Her)

Thank you for the PR. I think since there isn't a fully implementation example yet for the all the features it would make this easier to review if we cut down the FlightSql proto to what is implemented and focus on each use-case in a separate PR. I think it makes sense to handle read, write and metadata operations separately?

Like other Flight APIs, flight-sql does not provide implementation details that dictate how a client and server communicates with each other, it simply provides the SQL semantics and apply them onto the Flight API.

IMO, I think we should be be trying to specify more about how client and server interact with each other in terms of error handling and retries, these are important aspects and without it I think some of the utility of standardization will be diminished.

Thinking about this a bit more I think an alternative to a lot of the metadata querying is to define a minimal sql table schema and querying capabilities for it. I'll expand more in a little bit

I did a rough sketch on how the metadata layer could be modeled as pseudo-tables as comments on the proto. I think this addresses some uneasiner I had with the existing model:

It uses one consistent data model for tabular data (the arrow model).
It makes query semantics clearer instead of trying to model them in an ad-hoc manner through protobufs

This comes at slightly more complex for server implementations. And potential confusion on limitations for specific tables. This might be limited to some extend if we had a different GetMetadata action so implementations know to expect a query to specific pseudo-table. I expect we would provide library wrappers over JDBC to also ease implementation.

To clarify, are you suggesting something similar to INFORMATION_SCHEMA?
I am very much in favour of returning the data more like a standard query result. The existing protobuf definitions don't allow vendors to supply extra metadata with their catalog results. (ODBC and JDBC let you add extra columns to getTables() calls).
I am hesitant about using pseudo-tables -- backend databases may not have catalog information in a form that can be transformed by the rest of their SQL engine. It opens up complexity from an implementor's perspective and I'm not sure how beneficial it is from a user perspective.
I'm also OK with making the catalog information accessible with a limited query syntax rather than pseudo-tables (eg SHOW TABLES WHERE ...)

@emkornfield @lidavidm - @jduo and myself will be working on moving this forward - hence the discussions around the metadata aspects. I think once we have that sorted out it should be fairly easy to get this into the next release.
The only other aspect to consider would be output/io parameters.

Thanks for picking this up again. Note the 5.0.0 timeline is soon-ish. It looks like we are nearing consensus on most issues raised so it would be helpful to see an updated document that could perhaps be submitted for a vote.

@lidavidm - that would be the goal. Am working to get this finalized, restrictions are just on time that can be made available.

@lidavidm - the proto has been updated (nothing else) to reflect what I think is the most recent understanding - if you want to take a look and let me know if there are any other thoughts. Will update the actual examples after the fact.

@lidavidm - I think we've gotten agreement on everything pending the removal of custom_info - if so then I'll start work on updating the examples to adhere to the updated proto.

@kylepbit yes, agreed. Thanks for the updates!
I'll try and remember to approve/kick off the CI when updated but also feel free to ping me to do so.
I'll note that Micah left one comment way at the top about naming the file FlightSql.proto instead of FlightSQL.proto for consistency (I think doing that rename might lose the comments so now is probably an OK time to do it).

@lidavidm - thanks for the reminder, I'll do that since I've already fixed the casing everywhere else.

@lidavidm @wesm - how should we try to move this towards getting merged - do you want one PR (this one) where the Java client/server are there, and the test has a working example, or should we try and split it up?

I think it's OK to have one PR with the format changes and a working client/server and test (that's how Flight itself was originally added, looking at it: https://github.com/apache/arrow/commit/db0ef22dd68ae00e11f09da40b6734c1d9770b57). Then we can put it up for a vote. Having the implementation will be useful so people voting can evaluate it as well.

Just FYI: most CI pipelines will skip so long as you have the WIP in the PR title, feel free to remove that (keeping it in Draft if desired) when you're ready for CI to run.

@lidavidm - just as an update, work is progressing here on a separate branch that'll be merged in. I think we'll ultimately end up with a separate PR as Tiffany has left, so we can't alter this. Will put a link to the new PR once created here for tracing.

@kylepbit Sounds good, thanks for the update.

Closing in favor of #10906


style: clippy's variable inlining in format! macros

Simply makes the suggested changes from clippy for inline variables in string templates.
Can be closed if undesired but maybe worth to be discussed.

Just checked and this does not affect the MSRV (1.60.0) it seems, we can discuss it.
Formatting job has failed, can you fix it?


NetworkPolicy has no effect

Environmental Info:
K3s Version: v1.28.5+k3s1

Node(s) CPU architecture, OS, and Version:

Linux s1 6.1.0-17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux
Cluster Configuration:

3 servers
Describe the bug:

My cluster is dual stack, and the config for each node looks something like this:
--flannel-iface bond0
--node-ip fda5:9812:1b23:310::10,<IP_ADDRESS>
--node-external-ip 2605:1234:8978:342e:a9::10,<IP_ADDRESS>
--cluster-cidr fda5:1234:c::0/64,<IP_ADDRESS>/17
--kube-controller-manager-arg node-cidr-mask-size-ipv4=24
--kube-controller-manager-arg node-cidr-mask-size-ipv6=80
--service-cidr fda5:1234:5::0/112,<IP_ADDRESS>/18
--cluster-dns fda5:1234:5::10
--flannel-ipv6-masq
--bind-address fda5:9812:1b23:310::10
--advertise-address fda5:9812:1b23:310::10
--kube-cloud-controller-manager-arg webhook-bind-address=fda5:9812:1b23:310::10
--disable traefik
--disable servicelb

I created the following NetworkPolicy:
kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
  name: default-deny
  namespace: mynamespace
spec:
  podSelector: {}
  policyTypes:
  - Ingress
  - Egress

However, the pods in mynamespace are still able to reach out to the internet and each other like normal. No other NetworkPolicy exists.
Expected behavior:
I expect the result of applying that NetworkPolicy to be no inbound or outbound traffic allowed on any pod in the mynamespace namespace.
Actual behavior:
The NetworkPolicy appears to do nothing.
I have come across issues like https://github.com/k3s-io/k3s/discussions/5314 that lead me to believe this might have something to do with dual stack, but @brandond's comment there leads me to believe that k3s' network policy controller should be able to handle dual stack now. I'm not sure how to troubleshoot further, any help would be appreciated.

Can you attach:

The complete logs from the k3s service on this node: journald -u k3s --no-pager &> k3s.log
The output of kubectl get networkpolicy -A
The output of iptables-save
The output of ipset save

cc @manuelbuil

Okay I created a minimal reproducer and.... it worked :thinking: . Still poking a bit, but this is starting to look like I am the problem.

Yeah I'm not sure what happened here, but I can't duplicate now. I will re-open if I figure it out. Thanks @brandond!


Cropped Result Window using Pixel counts

Currently the test window (result window) is cropped by specifying a smaller window that actual in the config file.
This places the result window in the reference image based upon pixel count. The actually physical dimensions associated with this
will be different depending upon the resolution.
It is currently unclear how scale and resolution of reference image is related to the camera image.
Concern is that the crop may depend upon resolution of the camera if based upon pixels.

Dip will start taking a look at whether we can use a higher res ref image somehow - if not for all actions, perhaps it can be possible to downscale the ref image for the sake of the live analysis, but use the higher res for mapping

This may be better left to cassettes with less spatial variability than our current COVID LFA

This may be better left to cassettes with less spatial variability than our current COVID LFA


Slight mismatch in task for installing Egeria server

In the readme for task-installing-egeria.md we say that within the 'server' directory there is a a directory for the OMAG Server Platform.
The example command is shown as 'cd servers/omag-server*' (note tha plural 'servers').
In my egeria-install I unpack the tar.gz and I have an 'egeria-omag-0.3-SNAPSHOT/server' directory, which directly contains the server-chassis-spring-0.3-SNAPSHOT.jar.

That was one of my fixes -- @mandy-chessell are the tutorials in an update-able state for PRs against these kinds of points, or still working on further areas and we should continue to hold off?

Its ok to correct the install tutorial - working on the admin text to break down the descriptions to cover the different OMAG server "personalities".  Had to put it to one side to finish all of the changed needed for release 1.


Flot instance never updates

The core setupFlotChart method is scheduled for execution on dataChanged and optionsChanged lifecycle events, but these don't seem to be referenced anywhere else in the codebase.
Shouldn't this be didUpdateAttrs, the canonical way to watch for a change in input?

Yes, it should, and thanks for pointing this out. You saved me a tonne of wasted time trying to figure out why my chart wasn't updating. The maintainer should merge your pull request.


Fix SparseDenseCwise's broadcasting issue

This fix tries to address the issue raised in #24072. In sparse_dense_cwise_mul/add operations the broadcasting only support dense to sparse, though the validation was not captured.
This fix fixes the validation in SparseDenseBinaryOpShared so that error could be thrown correctly.
This fix fixes #24072.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

Also ping @rmlarsen to take a look. Thanks for all the help so far!

@yongtang Thanks for the contribution. I will review this tomorrow.


Diff syntax highlighting HTML spilling into content

https://try.gitea.io/silverwind/updates/commit/9f342114d7a6bb087ff777a983d0e03b41873b07
https://github.com/silverwind/updates/commit/9f342114d7a6bb087ff777a983d0e03b41873b07
On Line 88 of test.js the parts nx"> and k"> related to syntax highlighting markup should not be visible. Source HTML:
<span class="nx">resultValue

<span class="k">typeof

cc: @mrsdizzie

Good catch, this is side effect from #12205
Made a PR that should fix this if you could please test


Authenticode Hashing

We should be able to compute the hash that authenticode produces for portable executables. This is taken from Microsoft's open specification:

To calculate the hash value

Load the image header into memory.
Initialize a hash algorithm context.
Hash the image header from its base to immediately before the start of the checksum address, as specified in Optional Header Windows-Specific Fields.
Skip over the checksum, which is a 4-byte field.
Hash everything from the end of the checksum field to immediately before the start of the Certificate Table entry, as specified in Optional Header Data Directories.
Get the Attribute Certificate Table address and size from the Certificate Table entry. For details, see section 5.7 of the PE/COFF specification.
Exclude the Certificate Table entry from the calculation and hash everything from the end of the Certificate Table entry to the end of image header, including Section Table (headers).The Certificate Table entry is 8 bytes long, as specified in Optional Header Data Directories.
Create a counter called SUM_OF_BYTES_HASHED, which is not part of the signature. Set this counter to the SizeOfHeaders field, as specified in Optional Header Windows-Specific Field.
Build a temporary table of pointers to all of the section headers in the image. The NumberOfSections field of COFF File Header indicates how big the table should be. Do not include any section headers in the table whose SizeOfRawData field is zero.
Using the PointerToRawData field (offset 20) in the referenced SectionHeader structure as a key, arrange the table's elements in ascending order. In other words, sort the section headers in ascending order according to the disk-file offset of the sections.
Walk through the sorted table, load the corresponding section into memory, and hash the entire section. Use the SizeOfRawData field in the SectionHeader structure to determine the amount of data to hash.
Add the section’s SizeOfRawData value to SUM_OF_BYTES_HASHED.
Repeat steps 11 and 12 for all of the sections in the sorted table.
Create a value called FILE_SIZE, which is not part of the signature. Set this value to the image’s file size, acquired from the underlying file system. If FILE_SIZE is greater than SUM_OF_BYTES_HASHED, the file contains extra data that must be added to the hash. This data begins at the SUM_OF_BYTES_HASHED file offset, and its length is:
(File Size) – ((Size of AttributeCertificateTable) + SUM_OF_BYTES_HASHED)

Note: The size of Attribute Certificate Table is specified in the second ULONG value in the Certificate Table entry (32 bit: offset 132, 64 bit: offset 148) in Optional Header Data Directories.
15.	Finalize the hash algorithm context.

Microsoft's Hash implementation in .NET Core is dumb. It doesn't provide an update / finalize API for computing the hash. It can either compute the hash of an entire byte[] (not feasible due to the memory)  or a Stream. It looks like we need to create a stream type that returns the bytes that should be hashed.
Lame.

#68 addresses the update / finalize issue. Unblocked.

We should be able to make our own DIGEST_FUNCTION in ImageGetDigestStream and see what parts of the PE it expects us to hash. Need Windows for this though.


Issue: Update sample apps

BasicMasterBindings: Add PropsFromEnvSettings
Advanced: Move input folder to standard path for other samples
This work item was migrated from CodePlex
CodePlex work item ID: '10102'
Assigned to: 'tfabraham'
Vote count: '1'

[UnknownUser@5/9/2013]
Resolved with changeset 72822: Minor updates to Advanced and BasicMasterBindings sample apps (#10102)

[UnknownUser@5/16/2013]


added explainations to Dev and Prod usage in README

Signed-off-by: Kininaru<EMAIL_ADDRESS>Fix: https://github.com/casbin/casdoor/issues/20

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Move eigenfunctions.py out of the root folder

Move eigenfunctions.py out of the root folder.

Fixed with b60988a