Instance_Del  -  Foreign Key violation

DBADash Version: <IP_ADDRESS>
When running:
EXEC dbo.Instance_Del @InstanceID = 1, @HardDelete = 1
When there are records in the dbo.IdentityColumns table or the dbo.IdentityColumnsHistory tables for that InstanceID, the following foreign key violations will be generated.
Msg 547, Level 16, State 0, Procedure dbo.Instance_Del, Line 414 [Batch Start Line 2]
The DELETE statement conflicted with the REFERENCE constraint "FK__IdentityC__Datab__1E3A7A34". The conflict occurred in database "DBADashDB", table "dbo.IdentityColumns", column 'DatabaseID'.
Msg 547, Level 16, State 0, Procedure dbo.Instance_Del, Line 418 [Batch Start Line 2]
The DELETE statement conflicted with the REFERENCE constraint "FK__IdentityC__Datab__2022C2A6". The conflict occurred in database "DBADashDB", table "dbo.IdentityColumnsHistory", column 'DatabaseID'.
The following delete commands:
DELETE dbo.IdentityColumnsHistory
WHERE InstanceID = @InstanceID
DELETE dbo.IdentityColumns
WHERE InstanceID = @InstanceID

need to be added prior to:
DELETE dbo.Databases
WHERE InstanceID = @InstanceID

Cheers,
Stephen Schissler

Thanks for reporting this issue!  If you are interested in contributing, you could create a pull request to fix this issue.  If not I'll probably take a look at it next week.  Either way thanks for the detailed report and fix. 😊

Sure, I'm new to the GIT process.  I'll do a pull request with the change.
Thanks for making this application open source.
-Stephen
On Fri, Dec 1, 2023, 5:19 PM David Wiseman @.***> wrote:

Thanks for reporting this issue! If you are interested in contributing,
you could create a pull request to fix this issue. If not I'll probably
take a look at it next week. Either way thanks for the detailed report and
fix. 😊
—
Reply to this email directly, view it on GitHub
https://github.com/trimble-oss/dba-dash/issues/777#issuecomment-1836855411,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BEMTH7LB6N7TSDANNR5QVXLYHJJVZAVCNFSM6AAAAABADIB2K6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZWHA2TKNBRGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks.  It's worthwhile learning Git as pretty much all software development relies on it now. It's also useful for DBAs that support those development teams.  If you need help, let me know.
I'll also look at adding a test to the GitHub actions to hopefully prevent it from getting broken in the future.  #780

Hi, let me know if you are still interested in doing a PR for this.  If not, I'm happy to do it.  I've created a test for it that should prevent it getting broken again in future.

Hi David,
I have not had time to look into how to do the pull request, so you should
probably do it.
Thanks!
Stephen
On Wed, Dec 13, 2023 at 3:21 AM David Wiseman @.***>
wrote:

Hi, let me know if you are still interested in doing a PR for this. If
not, I'm happy to do it. I've created a test for it that should prevent it
getting broken again in future.
—
Reply to this email directly, view it on GitHub
https://github.com/trimble-oss/dba-dash/issues/777#issuecomment-1853458583,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BEMTH7PLUITYHB27OU6JEM3YJFQRJAVCNFSM6AAAAABADIB2K6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJTGQ2TQNJYGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

No problem.  The fix will be included in the next release.

This is included in version 3.0.  Note, that there is an upgrade to .NET 8.  🚀


denoising strenght

Hi,
Is there a way to define the denoising strength ?
Thanks,

Hi!
You can control the strength of the edit with the guidance parameters. The following command controls the parameters:
--pipeline.guidance-scale 7.5 --pipeline.image-guidance-scale 1.5
guidance-scale refers to the text guidance scale, so if you would like your edit to change more, increase the guidance scale or decrease the image guidance scale.
To actually change the denoising strength, we define the range of T from 0.02 to 0.98. We find that this selection of T leads to the best results. If you would like to play with that, the parameters are as follows:
--pipeline.lower-bound 0.02 --pipeline.upper-bound 0.98


Menu Search

Issue Type: Feature Request
Hi,
Thanks for the Good work on ADS.
It would be nice to have a Search field on the title bar of ADS. like VS 2017, for searching in the menus command names, and executing the found menu comman.
Regards.
Azure Data Studio version: azuredatastudio 1.0.0 (cab8f3e37c9ac4367e0dacef5185da08bd8021c2, 2018-09-20T22:04:35.897Z)
OS version: Windows_NT x64 10.0.17134

Found it, under Command Pallette (Ctrl+Shift+P).


Can captured samples be amplified before written to file?

I'm trying to find a way to amplify the samples as it's being received because I know that my audio is inherently low. Reading through the Docs, I found a reference to the use of WaveBuffer. I was hoping that something like this would work (my simple brain's first thought):
m_CaptureDevice.DataAvailable += (s, a) =>
{
var buffer = new WaveBuffer(a.Buffer);
// interpret as 32 bit floating point audio
for (int index = 0; index < a.BytesRecorded / 4; index++)
{
// Boost input the received samples
buffer.FloatBuffer[index] = buffer.FloatBuffer[index] * 1.1f;  // Doesn't work
}
m_WavWriter.Write((byte[])buffer, 0, a.BytesRecorded);
};
But it doesn't. I am providing the user with the ability to boost the playing level at play back time, but I also would like to provide the user the opportunity to amplify the audio as it's being recorded. Is there a simple way to do this? Thank you.

You can only interpret the incoming data as 32 bit floating point if that's what it actually is. And so I expect you're recording 16 bit audio. The WaveFormat of m_CaptureDevice will tell you

Thanks Mark. That was it. No more garbled audio after fixing the bits per sample.


Book models missing summary property

All of the Book models and Book entity is missing a property of a Summary; a short description where a publisher can give an insight to the book's content.

Should the summary field participate in search queries?

Hmm. No. I don't think it should 🤔


Kubelabs 101 "Deep dive into Kubernetes Architecture" link broken

On this page, it appears that the link Deep Dive into Kubernetes Architecture is broken.
Is this document missing or is the link broken perchance?

@mkrupczak3  Please refer https://github.com/collabnix/dockerlabs/kubernetes for labs as of now. We are migrating the labs from dockerlabs to kubelabs.

Ah, thanks.
Cheers


⚠ Mobitopup has degraded performance

In d4c9820, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 22771 ms

Resolved: Mobitopup performance has improved in 4f2c2f5.


wai-app-file-cgi mentions non-existant attribute

The common haskell configuration file defines some overrides for wai-app-file-cgi but the override for http-client no longer exists. I'm unsure whether the right thing to do is to delete the line or a more intricate fix is required.
https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/haskell-modules/configuration-common.nix#L1097

I think a simple replacement with http-client_0_5_5 should work (that exists in pkgs/development/haskell-modules/hackage-packages.nix).


Fix audioEngine interface to include methods

A fix for an issue I'm getting when I'm using the ES6 version with webpack
Propery 'connectToAnalyser' does not exist on 'IAudioEngine'

There is a lint issue else all good

Whops, forgot to mention - fixed!

Thanks!


[catloop] Performance counters

This PR closes #895.
Commits:

99c7132fe2483bcfbe3da2b865e3171bc3f2b93c - Inserting the profiler annotations.
1a237ee653ced5e4b75d48d45dae095450e0a7d2 - Fixing a typo.

@carvalhof would you remove the profiling from asynchronous code? Those we want to measure from application side. @iyzhang please jump in if you disagree.

@carvalhof would you remove the profiling from asynchronous code? Those we want to measure from application side. @iyzhang please jump in if you disagree.

Done in d167329a623ef8134656a257ec1c828d0cf9f70b


Use components onChange

Coverage increased (+0.1%) to 71.21% when pulling 25ab3c642869ad36d0b0d80ee301614db1ae2c0c on eatonphil:use-component-onchange into fccc7b1b496334f36f6374985d3da2bbb90f1ef0 on linode:develop.


query: Allow specifying what downsampling resolution you want to use.

Useful for debugging purposes as well as data accuracy knowledge.

https://github.com/improbable-eng/thanos/pull/349


Danger should keep violations order

Report
What did you do?
Run danger.
What did you expect to happen?
The comment should report violations in the same order as they were reported. This could be related to previous runs of Danger.
What happened instead?
It didn't respect the order. See the report on CI vs the comment on the PR.
Your Environment

Which CI are you running on? Circle
Are you running the latest version of Danger? Yep, 4.0.5
What is your Dangerfile? https://github.com/marcelofabri/SwiftLint/blob/35209910b74c94731cfbb20376876ef6b8d4002d/Dangerfile

Maybe we need a timestamp on the creation of a violation?

I think this is a simpler issue than that - see that in the Circle log the violations are shown in the expected order. Something between that and reporting have changed it (maybe https://github.com/danger/danger/blob/master/lib/danger/request_sources/github.rb#L136-L139?)

I've opened https://github.com/realm/SwiftLint/pull/1230 which did a fresh run and it showed the same problem, so it's not an issue edit problem.

@marcelofabri @orta is this still actual?
I created Dangerfile that simply prints your messages:
message('Linting Alamofire with this PR took 3.33s vs 3.32s on master (0% slower)')
message('Linting swift with this PR took 11.55s vs 11.55s on master (0% slower)')
message('Linting Aerial with this PR took 0.43s vs 0.43s on master (0% slower)')
message('Linting SourceKitten with this PR took 1.55s vs 1.54s on master (0% slower)')
message('Linting Sourcery with this PR took 2.27s vs 2.31s on master (1% faster)')
message('Linting ios-oss with this PR took 17.73s vs 17.47s on master (1% slower)')
message('Linting Moya with this PR took 0.47s vs 0.44s on master (6% slower)')
message('Linting firefox-ios with this PR took 16.59s vs 16.57s on master (0% slower)')
message('Linting Nimble with this PR took 1.77s vs 1.8s on master (1% faster)')
message('Linting Quick with this PR took 0.53s vs 0.54s on master (1% faster)')
message('Linting realm-cocoa with this PR took 3.66s vs 3.65s on master (0% slower)')
message('Linting WordPress-iOS with this PR took 7.51s vs 7.48s on master (0% slower)')

and result:

@marcelofabri can you please recheck this with latest version of danger?

Hrm, there's potential that the output for the script generating these results could be passing the messages through in a different order ( as they may take different amounts of time? )

Hrm, there's potential that the output for the script generating these results could be passing the messages through in a different order ( as they may take different amounts of time? )

The operations aren't parallel, so I can't see how this would be the case. Also, the order was right when Danger prints the violations to stdout (see https://circleci.com/gh/realm/SwiftLint/276).

@marcelofabri can you please recheck this with latest version of danger?

I'll try it later, but feel free to try to reproduce it on SwiftLint repo.

Don't think so. @marcelofabri Dangerfile look quite synchronous and explicit
@repos.each do |repo|
    # some code that calculates values
    message "Linting #{repo_name} with this PR took #{branch_duration}s " \
            "vs #{master_duration}s on master (#{percent_change.to_i}\% #{faster_slower})"
  end

@marcelofabri thank u, I'll test.

@orta oh, I find it
Here we sort violations, then we send inline comments and remove them from sorted arrays. But to github we push without original order.
I think we can just select inline comments and pass them to submit_inline_comments! and we will note care about arrays mutation. What do you think about it?
Also i wonder why i can't reproduce this for my example, so I will debug this more in evening.

@orta fix for this https://github.com/danger/danger/pull/813


correct spelling mistake

Thank you!

Coverage remained the same at 100.0% when pulling db4c6c2811d1e3b3b007b1d0e6af51867874ee95 on EdwardBetts:patch-1 into e6981206fdcd1dacae44c22c172148043da01562 on NextThought:master.


Update code

Update code to edition 2021 and dependencies.
Make it could run.
Fix clippy warnings.

Also change the content of Paragraph:

@orhun


[BUG] Erro with docker build

When build HugeCTR  with Merlin docker, https://github.com/NVIDIA-Merlin/Merlin/blob/main/docker/training/dockerfile.tf
according to this wiki https://nvidia-merlin.github.io/HugeCTR/master/hugectr_contributor_guide.html#set-up-the-development-environment-with-merlin-containers
After make and install, i try to import hugectr in python, an error occurs.

Hi @AtekiRyu , sorry for late reply. "dockerfile.tf" is just made for tensorflow users and supported with sok (HugeCTR tf plugin).

To use native HugeCTR APIs (import hugectr) you'd better to use https://github.com/NVIDIA-Merlin/Merlin/blob/main/docker/training/dockerfile.ctr
To use sok you may want to follow these instructions and import sparse_operation_kit as sok

Please let us know if you have further questions.

@jershi425 @shijieliu For our contribution guide

[ ] In the session of Build HugeCTR from Source we need to specify that the instructions are only for https://github.com/NVIDIA-Merlin/Merlin/blob/main/docker/training/dockerfile.ctr

[ ] In the session of https://nvidia-merlin.github.io/HugeCTR/master/hugectr_contributor_guide.html#build-hugectr-from-source we need to specify that the instructions are only for https://github.com/NVIDIA-Merlin/Merlin/blob/main/docker/training/dockerfile.tf

[ ] We need to add instructions of how to build Inference container.

Thanks, i will try it with your instructions.


Add CODEOWNERS starting point

Anyone else want in on this?

EF Team: @AndriySvyryd @bricelam @divega @roji @lajones @maumar @smitpatel Is this something we want? (To me it seems like extra metadata to maintain with little real benefit.)

Not needed, too few owners

To me it seems like extra metadata to maintain with little real benefit.

I appreciate knowing what's changing in the eng/ folder across all of our repos. Do you object to me creating the file as-is?

Not sure we'd really benefit, but it could maybe help bring PRs to each area's owner a bit more quickly...
That said no apparent harm in having it for eng either I think...

@dougbu Would this also require you to sign off on the PRs or have we disabled that aspect of ownership?

@bricelam no sign-off needed. I'll get invited as a review but that's it.


r11s-driver: add ability to sample performance telemetry

#7061 rightfully pointed out that R11s driver creates a lot of telemetry when operating in "shredded summary" mode. This new telemetrySampling driver policy will allow the host to sample all, some, or no events based on specific rules. An example use could be like so:
{
  telemetrySampling: [
    // Only log 1% of readBlob performance telemetry
    { rate: [1, 100], eventName: "readBlob", category: "performance" },
    // Only log 10% of other performance telemetry
    { rate: [1, 10], category: "performance" },
  ],
}

I'd strongly advice not to go that path. You will have really hard time investigating bugs that way, where quite often you need to zero in on particular session and see everting that happen in this session.
In my experience, sampling works at session level. I.e. either whole session is sampled out or not.
The other direction to look at (which is not ideal) - only generating "summary" telemetry data points for some sub-system. I.e. keep accumulating data and flushing it either on a timer or on some threshold. Or record date about every 100th call (for example, that's how we track ping times - we do not record every ping only every 100th or so)

Closing in favor of #8434


How do I create a frameless/tiltlebarless window?

As neutrino windows can have a theme which does not always match frame and titlebar (especially for MS windows) I woluld like to open a window without frame and titlebar so that everything is completly customizable (if necessary a custom titlebar could be created out of a small container with an image (app-icon), a label titlebartext) and 3 small buttons (minimize, maximize, close) - or whatever you like to have here) and even frame could follw the chosen theme. What do I have to do, to get such a window?

web_view::builder()
        .frameless(false)

Should do the trick, using web-view v0.6 though

Bumped dependency versions and added window.set_frameless()

Not exactly neutrino issue, but I would like to know how, if at all, did you get around the drag issues?
I added a custom title bar but am seemingly unable to drag.


[Feature] Adding 'Home' Button in each calculator section for Navigation Consistency.

Description
Currently, the project lacks a direct way for users to return to the home page after navigating to other sections of calculators. This can create a less intuitive user experience, especially for first-time users or those who are not familiar with the site structure.
Proposed Change:
I propose adding a 'Home' button to the interface that will be visible from every section of calculators of the project. This button will:
Improve Navigation: Provide users with a consistent and easy way to return to the main page from any section.
Enhance User Experience: Reduce the need for users to manually navigate back to the home page, thus simplifying their interaction with the site.
Increase Accessibility: Make the home page accessible from all parts of the application, ensuring users can easily find and use the main content.
Benefits:

Streamlined user flow.
Enhanced user satisfaction and engagement.
Better overall usability of the application.

The button should be added such that it will be clearly visible and understandle by users.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

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

@Rakesh9100 please assign this issue to me under gssoc.

@Rakesh9100 this issue can be assigned

Do you want to add a home button to each calculator page @jessicachawla

Do you want to add a home button to each calculator page @shraddhha

Yes, I can add a home button to each calculator page ensuring consistent styling and functionality. Please assign this issue to me I assure you to complete it as soon as possible.

Since new calculators are added frequently, it's unnecessary to include a home button on each calculator page. Each calculator already opens in a new tab, allowing users to return to the previous tab if needed @shraddhha


Update to todays wasm-pack

I don't think this is quite correct.
A lot of apps are designed to be run in the browser, so running the tests in Node will fail.

Ideally this should be fixed in wasm-pack, so we can just run wasm-pack test and it will choose which runners to use at runtime, rather than needing to pass in flags.

Well that might be true, however they decided to change the flag from --headless to --node for some reason unknown to me.

@dns2utf8 Where did you hear that?

I got an error message when using the command:
$ wasm-pack test --headless
Error: Must specify at least one of `--node`, `--chrome`, `--firefox`, or `--safari`

@dns2utf8 Yes, that is correct, you must specify at least one of those options, like so:
wasm-pack test --headless --chrome
wasm-pack test --headless --firefox
wasm-pack test --headless --safari

Or you can combine multiple together:
wasm-pack test --headless --chrome --firefox --safari

Note that the --headless is in addition to the other options. Wasm-pack has always worked that way, nothing has changed recently.
As for this template specifically, you can use npm test -- --chrome (and similarly for the other browsers).
It was setup that way because different people will have different browsers, so that lets you choose which browsers to run the tests in.


fix: getServerSession returning null for authenticated users

Closes # .
Checklist:

[ ] issue number linked above after pound (#)

replace "Closes " with "Contributes to" or other if this PR does not close the issue

[x] manually checked my feature / checking not applicable
[x] wrote tests / testing not applicable
[x] attached screenshots / screenshot not applicable

I've implemeneted my own solution to fix getServerSession as told. I require additional confirmation since I'm unsure if you expect an identical response from next-auth.


Fix an incorrect calculation of group plugin's pivot

don't store pivot in plugin state as this shouldn't be saved to the graph (yet)

when calculating the averaged center of objects, only use state.position rather than object3d.position which would also include the pivot's contribution and cause accumulation

lgtm


Data Processing - no filtering on dynamic columns

add note warning readers that filtering cannot be used on dynamic columns

Thanks!


Improve the readme

Any improvements to the readme.md are welcome!

I'd like to contribute to this issue. Please assign it to me.


llm loses track of plugins when upgraded (with uv)

This may not be an llm issue, but could have to do with the interaction of the plugin mechanism with python packaging tooling.
I have llm installed (on MacOS) via uv tool install llm.  When I update llm with uv tool upgrade llm, it forgets about all of its installed plugins:
~ > llm plugins
[
  {
    "name": "llm-claude-3",
    "hooks": [
      "register_models"
    ],
    "version": "0.4.1"
  },
  {
    "name": "llm-llamafile",
    "hooks": [
      "register_models"
    ],
    "version": "0.1"
  },
  {
    "name": "llm-perplexity",
    "hooks": [
      "register_models"
    ],
    "version": "0.9"
  },
  {
    "name": "llm-ollama",
    "hooks": [
      "register_commands",
      "register_models"
    ],
    "version": "0.5.0"
  },
  {
    "name": "llm-cmd",
    "hooks": [
      "register_commands"
    ],
    "version": "0.2a0"
  },
  {
    "name": "llm-claude",
    "hooks": [
      "register_models"
    ],
    "version": "0.4.0"
  },
  {
    "name": "llm-mistral",
    "hooks": [
      "register_commands",
      "register_embedding_models",
      "register_models"
    ],
    "version": "0.5"
  }
]

Now I update:
~ > uv tool upgrade llm
Modified llm environment
 - anthropic==0.34.2
 - charset-normalizer==3.3.2
 - filelock==3.16.0
 - fsspec==2024.9.0
 - httpx-sse==0.4.0
 - huggingface-hub==0.24.7
 - llm-claude==0.4.0
 - llm-claude-3==0.4.1
 - llm-cmd==0.2a0
 - llm-llamafile==0.1
 - llm-mistral==0.5
 - llm-ollama==0.5.0
 - llm-perplexity==0.9
 - ollama==0.3.3
 - packaging==24.1
 - prompt-toolkit==3.0.47
 - pygments==2.18.0
 - requests==2.32.3
 - tokenizers==0.20.0
 - urllib3==2.2.3
 - wcwidth==0.2.13

Now, no more plugins
~ > llm plugins
[]

Having saved the JSON of plugins, I can re-install them, and it appears that everything is installed from the cache.  Is this because llm install is using pip or something similar, and uv handles things differently?

You are right, llm installs plugins with pip into the same environment it runs in. uv does not know about these dependencies and will remove them when upgrading the package llm.
A workaround is to install llm plugins as additional Python dependencies with uv install --extra <llm-plugin> llm, as documented here.
One caveat though, you cannot add additional dependencies this way. You always have to provide the full list of extra dependencies with multiple --extra options.


hello,when I build,a error appear :error: static assertion failed

ubuntu 18.04
console output：

Errors     << pcl_catkin:make /home/lzw/resplendent_code/voxblox_pp_ws/logs/pcl_catkin/build.make.004.log
In file included from /usr/local/include/eigen3/Eigen/Core:153:0,
from /home/lzw/resplendent_code/voxblox_pp_ws/build/pcl_catkin/pcl_src-prefix/src/pcl_src/common/include/pcl/impl/point_types.hpp:46,
from /home/lzw/resplendent_code/voxblox_pp_ws/build/pcl_catkin/pcl_src-prefix/src/pcl_src/common/include/pcl/point_types.h:359,
from /home/lzw/resplendent_code/voxblox_pp_ws/build/pcl_catkin/pcl_src-prefix/src/pcl_src/filters/include/pcl/filters/frustum_culling.h:42,
from /home/lzw/resplendent_code/voxblox_pp_ws/build/pcl_catkin/pcl_src-prefix/src/pcl_src/filters/include/pcl/filters/impl/frustum_culling.hpp:41,
from /home/lzw/resplendent_code/voxblox_pp_ws/build/pcl_catkin/pcl_src-prefix/src/pcl_src/filters/src/frustum_culling.cpp:38:
/usr/local/include/eigen3/Eigen/src/Core/Dot.h: In instantiation of ‘typename Eigen::ScalarBinaryOpTraits<typename Eigen::internal::traits::Scalar, typename Eigen::internal::traits::Scalar>::ReturnType Eigen::MatrixBase::dot(const Eigen::MatrixBase&) const [with OtherDerived = Eigen::Block<Eigen::Matrix<float, 4, 1>, -1, -1, false>; Derived = Eigen::Matrix<float, 3, 1>; typename Eigen::ScalarBinaryOpTraits<typename Eigen::internal::traits::Scalar, typename Eigen::internal::traits::Scalar>::ReturnType = float]’:
/home/lzw/resplendent_code/voxblox_pp_ws/build/pcl_catkin/pcl_src-prefix/src/pcl_src/filters/include/pcl/filters/impl/frustum_culling.hpp:113:24:   required from ‘void pcl::FrustumCulling::applyFilter(std::vector&) [with PointT = pcl::PointXYZ]’
/home/lzw/resplendent_code/voxblox_pp_ws/build/pcl_catkin/pcl_src-prefix/src/pcl_src/filters/src/frustum_culling.cpp:44:1:   required from here
/usr/local/include/eigen3/Eigen/src/Core/Dot.h:75:3: error: static assertion failed: YOU_TRIED_CALLING_A_VECTOR_METHOD_ON_A_MATRIX
EIGEN_STATIC_ASSERT_VECTOR_ONLY(OtherDerived)
^
make[5]: *** [filters/CMakeFiles/pcl_filters.dir/src/frustum_culling.cpp.o] Error 1
make[4]: *** [filters/CMakeFiles/pcl_filters.dir/all] Error 2
make[3]: *** [all] Error 2
make[2]: *** [pcl_src-prefix/src/pcl_src-stamp/pcl_src-build] Error 2
make[1]: *** [CMakeFiles/pcl_src.dir/all] Error 2
make: *** [all] Error 2

@resplendent-star it seems a known issue from the PCL library: https://github.com/PointCloudLibrary/pcl/pull/2786
Since the issue should be fixed starting from PCL 1.10 (so far Voxblox++ was fetching PCL 1.9.1) I have merged in a PR to request PCL 1.10.1, see https://github.com/ethz-asl/voxblox-plusplus/pull/68
For this to take effect on your machine you should pull the latest voxblox++ master, then wstool merge -t . voxblox-plusplus/voxblox-plusplus_https.rosinstall
It should ask something along the lines of:
$ wstool merge -t . voxblox-plusplus/voxblox-plusplus_https.rosinstall

     Change details of element (Use --merge-keep or --merge-replace to change):
  pcl_catkin

Continue: (y)es, (n)o, (v)erbosity, (a)dvanced options:

After answering yes, run wstool update.
Else, you can just manually checkout the branch fix/advance_perception_pcl in the pcl_catkin folder.
Let me know if the issue persists.

wstool merge -t . voxblox-plusplus/voxblox-plusplus_https.rosinstall
ERROR in config: /home/lzw/resplendent_code/voxblox_pp_ws has no workspace configuration file '.rosinstall'

@resplendent-star it seems a known issue from the PCL library: PointCloudLibrary/pcl#2786
Since the issue should be fixed starting from PCL 1.10 (so far Voxblox++ was fetching PCL 1.9.1) I have merged in a PR to request PCL 1.10.1, see #68
For this to take effect on your machine you should pull the latest voxblox++ master, then wstool merge -t . voxblox-plusplus/voxblox-plusplus_https.rosinstall
It should ask something along the lines of:
$ wstool merge -t . voxblox-plusplus/voxblox-plusplus_https.rosinstall

     Change details of element (Use --merge-keep or --merge-replace to change):
  pcl_catkin

Continue: (y)es, (n)o, (v)erbosity, (a)dvanced options:

After answering yes, run wstool update.
Else, you can just manually checkout the branch fix/advance_perception_pcl in the pcl_catkin folder.
Let me know if the issue persists.

lzw@resplendent-star:~/resplendent_code/voxblox_pp_ws/src$  wstool merge -t . voxblox-plusplus/voxblox-plusplus_https.rosinstall
Merge caused no change, no new elements found

Please try to manually checkout the master branch in the pcl_catkin package.

If all else fails, just delete your voxblox++ workspace and try a clean install.

Please try to manually checkout the master branch in the pcl_catkin package.

If all else fails, just delete your voxblox++ workspace and try a clean install.

hello,I  try all  this command  in  old pal_catkin
return "fatal: not a git repository (or any parent directory): .git"
and  then  I  creat  a new  voxblox++ workspace,when do catkin build
still  return  "EIGEN_STATIC_ASSERT_VECTOR_ONLY(OtherDerived)"
then I  use  "git checkout master"
still return "fatal: not a git repository (or any parent directory): .git"

That is not an error I can help you resolve as it just seems you are running the commands from the wrong folder.
Did you do a complete wipe of the workspace and newly cloned the voxblox++ repository? If yes, and the issue still persists then can you post the output of $ git branch run from the pcl_catkin folder.

That is not an error I can help you resolve as it just seems you are running the commands from the wrong folder.
Did you do a complete wipe of the workspace and newly cloned the voxblox++ repository? If yes, and the issue still persists then can you post the output of $ git branch run from the pcl_catkin folder.

hello
,this  output
1)
lzw@resplendent-star:~/resplendent_code/voxblox_pp_ws/build/pcl_catkin$ git checkout master
fatal: 不是一个 git 仓库（或者任何父目录）：.git
this info in english is:[fatal: not a git repository (or any parent directory): .git]
2)lzw@resplendent-star:~/resplendent_code/voxblox_pp_ws/build/pcl_catkin$ git branch
fatal: 不是一个 git 仓库（或者任何父目录）：.git
this info in english is:[fatal: not a git repository (or any parent directory): .git]

Finally, I see what is the problem: you are not supposed to work from the build space but from the src folder in your workspace.
That is, not from ~/resplendent_code/voxblox_pp_ws/build/pcl_catkin but from ~/resplendent_code/voxblox_pp_ws/src/pcl_catkin.
If you want to use Voxblox++ but you are not familiar with ROS and catkin, I would first highly encourage you to learn about them here and here.

Finally, I see what is the problem: you are not supposed to work from the build space but from the src folder in your workspace.
That is, not from ~/resplendent_code/voxblox_pp_ws/build/pcl_catkin but from ~/resplendent_code/voxblox_pp_ws/src/pcl_catkin.
If you want to use Voxblox++ but you are not familiar with ROS and catkin, I would first highly encourage you to learn about them here and here.

thank you
(base) lzw@resplendent-star:~/resplendent_code/voxblox_pp_ws/src/pcl_catkin$ git checkout master
切换到分支 'master'
您的分支与上游分支 'origin/master' 一致。
(base) lzw@resplendent-star:~/resplendent_code/voxblox_pp_ws/src/pcl_catkin$ git pull origin master
remote: Enumerating objects: 13, done.
remote: Counting objects: 100% (13/13), done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 13 (delta 5), reused 8 (delta 3), pack-reused 0
展开对象中: 100% (13/13), 完成.
来自 https://github.com/ethz-asl/pcl_catkin

branch            master     -> FETCH_HEAD
23a38b5..2a70959  master     -> origin/master
Fetching submodule perception_pcl
来自 https://github.com/ethz-asl/perception_pcl
c58e92c..6d7afe2  melodic-devel -> origin/melodic-devel
更新 23a38b5..2a70959
Fast-forward
pcl_catkin/CMakeLists.txt            | 4 ++--
pcl_catkin/cmake/pcl-extras.cmake.in | 4 ++--
pcl_catkin/package.xml               | 2 +-
perception_pcl                       | 2 +-
4 files changed, 6 insertions(+), 6 deletions(-)
(base) lzw@resplendent-star:~/resplendent_code/voxblox_pp_ws/src/pcl_catkin$

I hope this solved the PCL build issue. Closing, feel free to reopen if the issue persists.


Add dictionary support

Allow Dictionaries with key of string and value one of the supported CLR AMQP primitives to be created in a Value message. Convert these dictionaries to/from AmqpMap within Service Bus.

/azp run net - servicebus - tests

/azp run net - servicebus - tests

/azp run net - servicebus - tests

/azp run net - servicebus - tests

/azp run net - servicebus - tests


Updates to the Readme

This can be merged in once the feature work on Studio has been completed

@emosbaugh fixed!


Use Set-DisplayResolution to match the display resolution of the client Mac

Set-DisplayResolution -Width 2560 -Height 1600 -Force

https://docs.microsoft.com/en-us/powershell/module/servercore/set-displayresolution?view=win10-ps

closing this as it seems the parsec client sets the resolution (incorrectly) on connection


Add focus points for smart thumbnailing

With this PR, we allow the user to set a focal point on a media that is uploaded using the media upload API. Also, the focal point data is returned in the entity after the call.

Sure, will do! Thx for the feedback.


Add raw format to better support pipelining

Please see: #4320

@keradus I did changes according to review notes, please check


reference sequence 0 out of range

What did you do?
I executed a query
What did you expect to see?
the result of the query
What did you see instead? Under which circumstances?
error message "reference sequence 0 out of range"
I have been running two Prometheus instances in Docker containers for about 2 years.
Since the end of August 2018 Prometheus starts to produce the error "reference sequence 0 out of range" frequently (on average once per week, sometimes it happens two days in a row, sometimes it happens after 10 days).
I have updated the OS from Ubuntu 16.04 to 18.04 not long before the problems started, but I have no real indication, that the OS upgrade is related (no other problems in the system or other Dockers).
After I get the error message for the first time, all queries fail with this error.
Once the problem has started, then there is nothing I can do to solve it, but restart the entire machine - restarting the Docker containers or even the Docker daemon has no effect.
I have two Prometheus instances, one for short term data and one for long term data with a big scrape interval. The configs are almost identical, the main differences are, that the short term instance has alert rules and the long term instance reads old data from a third Prometheus v1.8.2 instance (also in a Docker, but not scraping or accessed directly, just for access to the old data via the long term instance).
The problem usually happens on both instances simultaneously, but today I noticed for the first time, that the problem is only occurring on the long term instance.
The  metrics are stored on a NAS which is accessed via NFS.
I thought that the NFS mount may be the problem and tried different configs for that, but none helped. Note that the NFS shares worked w/o any problem for over a year and the fact, that currently one instance works while the other has the problem, kind of rules out an NFS problem (the metrics for both instances are on the same NFS share).
Once the problem starts, it can be reproduced by entering any query in Prometheus' web interface: It will then always show the error message "Error executing query: reference sequence 0 out of range" in a red box.
I usually notice that the problem has started, when I access Grafana, which shows no data but an exclamation mark in an orange triangle, which shows the error message "reference sequence 0 out of range" when the mouse pointer touches it.
The log contains a line like
level=error ts=2018-11-08T19:21:52.880918076Z caller=engine.go:554 component="query engine" msg="error expanding series set" err="reference sequence 0 out of range"

for each query that is made. All queries fail, once the problem has started.
Environment

System information:

Prometheus is running inside Docker, the image is currently:
REPOSITORY                             TAG                              IMAGE ID            CREATED             SIZE
prom/prometheus                        latest                           42e450d926a8        2 days ago          99.8MB

I update the image frequently
Linux 4.15.0-38-generic x86_64

Prometheus version:

prometheus, version 2.5.0 (branch: HEAD, revision: 67dc912ac8b24f94a1fc478f352d25179c94ab9b)
  build user:       root@578ab108d0b9
  build date:       20181106-11:40:44
  go version:       go1.11.1

also earlier versions, since end of August 2018

Prometheus configuration file:
This is for the long term instance, there are no rules in the configured directory.

global:
  scrape_interval: 1h
  scrape_timeout: 10s
  evaluation_interval: 1h
rule_files:
- "/etc/prometheus/rules/*.rule"
scrape_configs:
  - job_name: 'node'
    static_configs:
      - targets:
         - gytha:9100
         - server01.vpn:9100
  - job_name: 'pushGateway'
    static_configs:
      - targets:
         - gytha:9091
  - job_name: 'blackbox'
    metrics_path: /probe
    params:
      module: [http_2xx]
    static_configs:
      - targets:
        - www.xyz.com
    relabel_configs:
      - source_labels: [__address__]
        regex: (.*)(:80)?
        target_label: __param_target
        replacement: ${1}
      - source_labels: [__param_target]
        regex: (.*)
        target_label: instance
        replacement: ${1}
      - source_labels: []
        regex: .*
        target_label: __address__
        replacement: gytha:9115  # Blackbox exporter.
alerting:
  alertmanagers:
  - static_configs:
    - targets:
      - gytha.lancre:9093
remote_read:
  - url: "http://gytha.lancre:9094/api/v1/read"

Logs:

level=info ts=2018-11-08T19:21:45.284666262Z caller=main.go:244 msg="Starting Prometheus" version="(version=2.5.0, branch=HEAD, revision=67dc912ac8b24f94a1fc478f352d25179c94ab9b)"
level=info ts=2018-11-08T19:21:45.284710328Z caller=main.go:245 build_context="(go=go1.11.1, user=root@578ab108d0b9, date=20181106-11:40:44)"
level=info ts=2018-11-08T19:21:45.284728051Z caller=main.go:246 host_details="(Linux 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 d7d517dac246 (none))"
level=info ts=2018-11-08T19:21:45.284743573Z caller=main.go:247 fd_limits="(soft=1048576, hard=1048576)"
level=info ts=2018-11-08T19:21:45.28476792Z caller=main.go:248 vm_limits="(soft=unlimited, hard=unlimited)"
level=info ts=2018-11-08T19:21:45.285177959Z caller=main.go:562 msg="Starting TSDB ..."

level=error ts=2018-11-08T19:21:52.880918076Z caller=engine.go:554 component="query engine" msg="error expanding series set" err="reference sequence 0 out of range"

this is the docker-compose.yml used to start all the dockers:
  image: "prom/alertmanager:latest"
  container_name: "alertmanager"
  volumes:
    - "/etc/prometheus/alertmanager:/etc/alertmanager"
    - "/opt/prometheus/alertmanager:/alertmanager"
  ports:
    - "9093:9093"
  restart: always
  command: --config.file=/etc/alertmanager/config.yml --storage.path=/alertmanager --web.external-url http://gytha.lancre:9093

blackboxExporter:
  image: "prom/blackbox-exporter:latest"
  container_name: "blackboxExporter"
  volumes:
    - "/etc/prometheus:/config"
  ports:
    - "9115:9115"
  restart: always
  command: --config.file=/config/blackbox.yml

pushgateway:
  image: "prom/pushgateway:latest"
  container_name: "pushgateway"
  ports:
    - "9091:9091"
  restart: always

prometheusShort:
  image: "prom/prometheus:latest"
  container_name: "prometheusShort"
  volumes:
    - "/etc/prometheus/prometheusShort.yml:/etc/prometheus/prometheus.yml"
    - "/etc/prometheus/rulesShort:/etc/prometheus/rules"
    - "/file02/Data/prometheus/short/metrics:/prometheus"
  ports:
    - "9090:9090"
  restart: always
  command: --config.file=/etc/prometheus/prometheus.yml --storage.tsdb.path=/prometheus --storage.tsdb.retention=100d --web.external-url http://gytha.lancre:9090

prometheusLong:
  image: "prom/prometheus:latest"
  container_name: "prometheusLong"
  volumes:
    - "/etc/prometheus/prometheusLong.yml:/etc/prometheus/prometheus.yml"
    - "/etc/prometheus/rulesLong:/etc/prometheus/rules"
    - "/file02/Data/prometheus/long/metrics:/prometheus"
  ports:
    - "9290:9090"
  restart: always
  command: --config.file=/etc/prometheus/prometheus.yml --storage.tsdb.path=/prometheus --storage.tsdb.retention=100y --web.external-url http://gytha.lancre:9290

prometheusLong.v1.8:
  image: "prom/prometheus:v1.8.2"
  container_name: "prometheusLong.v1.8"
  volumes:
    - "/etc/prometheus/prometheusLong.old.nonScrape.yml:/etc/prometheus/prometheus.yml"
    - "/etc/prometheus/rulesLong:/etc/prometheus/rules"
    - "/file02/Data/prometheus/long/metrics.old:/prometheus"
  ports:
    - "9094:9094"
  restart: always
  command: -alertmanager.url http://gytha:9093 -config.file=/etc/prometheus/prometheus.yml -storage.local.path=/prometheus -storage.local.retention=876000h -web.console.libraries=/etc/prometheus/console_libraries -web.console.templates=/etc/prometheus/consoles -web.listen-address :9094

The metrics are stored on a NAS which is accessed via NFS.
I thought that the NFS mount may be the problem and tried different configs for that, but none helped. Note that the NFS shares worked w/o any problem for over a year and the fact, that currently one instance works while the other has the problem, kind of rules out an NFS problem (the metrics for both instances are on the same NFS share).

There's been numerous problems reported due to NFS. The fact that the issue vanishes after restarting the machine seems to indicate that the data on disk isn't corrupted.

I forgot to mention, that data is stored correctly while the problem exists i.e. after I restart the machine, I can see data from the time period, where queries returned the "reference sequence 0 out of range" error.

You can try to run promtool debug all ... and attach the output here. But as I wrote in my first comment, running Prometheus on top of NFS isn't recommended.

Thanks for the tip with NFS. I have switched back from NFS 4 to NFS 3 for now (tried CIFS, but the permissions drove me crazy).
I'll test it for some time and will report back.

@theRealAJR still facing any issues after switching?

no - but I need to run it for a little longer to be sure.
I had one instance running with NFS V3 and one with NFS V4 and the V4 instance had the problem again this week, but the V3 instance did not. So switched the all instances to V3. Now I have to let it run for two weeks or so, to be sure it's working with NFS V3.

Closing for now. Note that using NFS for storing Prometheus data is inherently buggy.

Running Prometheus and Grafana on top of Kubernetes and get the same issue periodically.  I just checked and my NFS mounts are v4.  Is falling back to v3 a viable workaround?

Yes, I have no problems any more in NFS V3.

@theRealAJR Thanks, just made the switch.  I will report back if any issues.


Update WEB BROWSER command to OPEN BROWSER.

@kameranis I reverted your contribution with a force push. I didn't realize that you don't even set your git username properly.
We don't like to see messy commit history.


Bad Gradient !!

Description
The gradient used all over the UI doesn't look appealing, rather looks cheap. As having a good experience of design , i would like to suggest changes in the gradient.
Screenshots

Additional information
No response
Do you want to work on this issue?

[X] I want to work on this issue.

suggest changes PRACTICALLY @prash240303

Hi, Practicality would be solved by others too, I am someone who likes a good UI and wishes to improve the UI /styling of your project, I was also looking for other issues regarding the UI. I think a good UI and front-end are also important, rather than just a crappy-looking project even if it's fully functional. Rest is your choice as the maintainer.

still do not answer my question. would need exact changes as in colour or whatever rather than ambiguity suggestions


Support for set_security_user ingest processor

I was going to use document-level security feature, but stuck with the fact that I cannot restrict users to access only their documents.
Such use case is described here: Pre-processing documents to add security details. And it turns out that set_security_user feature seems not implemented in OpenDistro:
PUT _ingest/pipeline/my-pipeline-id
description: set user
processors:
  - set_security_user:
      field: user
---
error:
  root_cause:
  - type: "parse_exception"
    reason: "No processor type exists with name [set_security_user]"
    header:
      processor_type: "set_security_user"
  type: "parse_exception"
  reason: "No processor type exists with name [set_security_user]"
  header:
    processor_type: "set_security_user"
status: 400

Would it possible to implement this processor? Is there any workaround?

@dpotapov You should also restrict write permissions and only allow user to write their own document.
Closing issue. If this doesn't solve your problem, please reopen.


ES Performance debug messages have incorrect parameter

The second parameter in the following two debug event messages are incorrect:
        CFE_EVS_SendEvent(CFE_ES_PERF_FILTMSKCMD_EID, CFE_EVS_DEBUG,
                    "Set Performance Filter Mask Cmd rcvd, num %d, val 0x%x",
        (int)cmd->FilterMaskNum,(unsigned int)cmd->FilterMaskNum);

        CFE_EVS_SendEvent(CFE_ES_PERF_TRIGMSKCMD_EID, CFE_EVS_DEBUG,
                  "Set Performance Trigger Mask Cmd rcvd,num %d, val 0x%x",
               (int)cmd->TriggerMaskNum,(int)cmd->TriggerMaskNum);

In both cases "Num" should be removed from the second parameter variable. The casting should also be examined.

Imported from trac issue 284.  Created by dcmccom3 on 2019-04-29T15:43:15, last modified: 2019-05-23T16:43:54

Trac comment by dcmccom3 on 2019-04-30 07:16:07:
It's not simply removing "Num" to solve the problem. It requires indexing the appropriate variable which will be obvious in the code.


TimeZoneNames 3.4.0 not working with TimeZoneConverter 3.0.0

Yep.  Will be a couple of days, I'm on vacation.  Thanks.

Thank you for the fast reply and enjoy your vacation!

This is complete in version 4.0.0.  Thanks.


Auto-Inline keyboard based on settings in admin (Easy-Keyboard) - /cmds liefert Fehlermeldung

"/cmds" liefert nix
im LOG:
(5477) Error: ETELEGRAM: 400 Bad Request: field "keyboard" of the ReplyKeyboardMarkup must be an Array of Arrays
bin auf auf stable 1.5.5 zurück , da gehts noch.
LG

I have the same issue... maybe reopen it again

seems to be fixed in latest now
thx


How to delete unlinked nodes?

How should I correctly delete nodes, that were created via TXMLDocument:NewElemet(), but were not inserted?
The best I've found is to call pair - InsertEndChild(node); DeleteChild(node);
But I want just to delete node without any insertions.

Addressed in #559

You can use DeleteNode(), or wait for the XMLDocument to go out of scope. Fixed in #560


Mobile activity tab

can we please fix this, its looking ugly

css migration?

@yangwao i dont think so, reported similar problem months ago


(javascript) params for => functions are not detected properly

Hi, could es6 be supported please?

I rewrite what @ldct said in other issues:
We can review and merge PRs with language implementations but won't be able to actually implement all the requested languages.
Please see http://highlightjs.readthedocs.io/en/latest/language-requests.html for more details.

Please provide a specific example of "ES6" syntax that you wish to be supported that is not presently.

@yyyc514 hi, here's some examples:
      promises.push(this._getFiles().then(filesByPath => {
        this._filesByPath = filesByPath;
      }));

      promises.push(this._getLoggedIn().then(loggedIn => {
        return this._loggedIn = loggedIn;
      }).then(loggedIn => {
        if (!loggedIn) { return; }

        return this._getReviewedFiles().then(reviewed => {
          this._reviewed = reviewed;
        });
      }));

      const magicFilesExcluded = files.filter(files => {
        return files.__path !== '/COMMIT_MSG' && files.__path !== '/MERGE_LIST';
      });

    _calculatePatchChange(files) {
    ....
    }

    _forEachDiff(fn) {
      const diffs = this.diffs;
      for (let i = 0; i < diffs.length; i++) {
        fn(diffs[i]);
      }
    },

The promises should be highlighted and then files, filesByPath and loggedIn should be highlighted.
The fn should be highlighted including diffs....
Variables after const/let or var should be highlighted too.
So e.g const test = ...

Variables after const/let or var should be highlighted too.

Should they?  Traditionally we don't highlight variables.  Does the grammar do that now with non ES6 variables?

Nope. Just it looks nice!

promises should be highlighted

I'm not sure what this means.

Closing for inactivity.


Formatting changes

addresses the K's

Please remove imagemagick-stable/imagemagick-stable_6.9.7_source.tar.bz2

some changes (and conflicts against master):

minetests & moon-buggy & tyrant: it doesn't follow the source, "source options", plugin order
also, please remove source-type: git when possible (minetest, moon-buggy, mp, tyrant)
mpv part is after ffmepg, shouldn't we declaret the ffmepg part first then?
tyrant has a line break between the 2 apps. Also build-packages is before stage-packages
ubuntukylin-icon-theme: plugs could all be in one line I think.
ubuntukylin-icon-theme:

   source: lp:ubuntukylin-theme
   source-type: bzr

-> can that be autodetected? (lp: is bzr specific)
ubuntukylin-icon-theme: after: can be in one line IMHO

ubuntukylin-icon-theme: I would put slots: before parts: (but isn't that plugs: btw?)

I've actually looked at the detection code in Snapcraft for a PR I'm working on, and it does detect lp:.

So, from the current state, I would see remaining to get fixed:

moon-buggy: I would put build-packages: last here
mpv (ffmpeg part): still has an source-type.
ubuntu-clock-app: configflags after plugin and source-type is unecessary
ubuntu-kylin-icon-theme: slots: is plugs: (even if I'm unsure the interface still exist) and it should be before parts:

@wandrewkeech @didrocks :+1:

LGTM as well, big thanks! Merging :)


[bug].net core 2.1,Identity will throw exception while implement IdentityUser. But .net core 2.0 is Ok.

I am using asp net core Identity Framework on core 2.1, and I implement my  ApplicationUser : IdentityUser .Then there will throw Exception like the screenshot .
But I found that, the same code is Ok on core 2.0, or I just user IdentityUser not my own ApplicationUser is also ok while services.AddIdentity<TUser, TRole>.
Is it's a core 2.1 bug?

This issue was moved to aspnet/Identity#1872


Fix for mid date interpolation

steps[0, 1:-1:2] = steps[0, 2::2] = (x[:-1] + x[1:]) / 2
This does not work for interpolating datetimes. This is because adding date does not makes sense and Numpy will throw an error
TypeError: ufunc add cannot use operands with types dtype('<M8[us]') and dtype('<M8[us]')
By changing it to an equivalent form
steps[0, 1:-1:2] = steps[0, 2::2] = x[:-1] + (x[1:] - x[:-1])/2
it adds a datetime and a delta datetime.
This works equally well for numbers.
With a bit of help I could also write tests.

Very clever!  Thanks for the fix!  The failing test doesn't seem related?

I've been puzzling over this for a while so this is great. Do the pre- and post-step function need similar fixes or do they already work with datetimes?

For the other interpolations datetimes should just work. I think I have tested this in the past but have just had a look and I think the others just use indexing and do not need to calculate a mid-point.

Great thanks. It would be great to add some tests for this in tests/operation/testoperation.py. They'd look something like:
    def test_interpolate_datetime_curve_mid(self):
        datetimes = ...
        values = ...
        interpolated = interpolate_curve(Curve((datetimes, values)), interpolation='steps-mid')
        curve = Curve(...)
        self.assertEqual(interpolated, curve)

I've made some other changes by casting the data to ints/floats before applying the interpolation and then casting back. This has the benefit that it also works for pandas period types and others, but may mess with types that cannot be represented with a datetime64[ns] type. In any case, it's a major improvement and I've also added tests.

If we find types that don't work, maybe we can add some exception-handling fallback to try another approach in those cases.

Made another change, it'll now use the native resolution if possible and only fall back to nanosecond resolution if the data is not a datetime64 type.

I promise I was going to add tests. However, you are wise in not waiting, it would take me a while before I got the time. Thank you.

I promise I was going to add tests. However, you are wise in not waiting, it would take me a while before I got the time.

Haha, no problem, I know how it is and I thought it would be nice to get this into 1.10.6.

This is an observation not a suggestion to change anything.  If you are now casting to number before the interpolation then the fix I gave might not be necessary. As I did not know the greater context, I think I avoided casting in an attempt to touch as little code as possible and easier to fit in.  However, your method will be a better fit within with the project.

Thanks, I think we're fine leaving it the way it is now. Ready to review/merge.

Now also correctly handled additional value dimensions.

PR build failure can be ignored, it's not pulling the latest data for some reason.

PR build failure can be ignored, it's not pulling the latest data for some reason.

Agreed and the PR looks good. Thanks @douglasmacdonald!


Name margin variables consistently

Margin variables sometimes appear as <position>-margin and sometimes as margin-<position>. It would be a lot easier to use these variables if they followed the same pattern throughout. The pattern that is most consistent with other variable names is margin-<position>.
This affects the following variables:

$alert-bottom-margin
$form-label-bottom-margin
$header-bottom-margin
$header-top-margin
$inline-list-bottom-margin
$inline-list-top-margin
$subheader-bottom-margin
$subheader-top-margin
$switch-bottom-margin

Maybe a change for Foundation 6?

Agreed! This has been addressed in Foundation 6. In addition to the naming, there are fewer of these variables and they are set to a $global-margin out of the box.

That's great news! I'm curious, though, where is Foundation 6. I checked master before filing the issue and I saw the same issue. (https://github.com/zurb/foundation/blob/master/scss/foundation/components/_type.scss#L15).

@rafibomb can get this one?


[BUG] Missing token icons at the pools table

Describe the bug
There are missing token icons at the pools table
To Reproduce

Go to the pools page
Look at the tables in V3+2

Expected behavior
All tokens have icons
Attach a file with part of the missing icons
Icons SVG.zip

added


Dark/light images in MD

Hello,
Tried discord, search and couldn't find anything or get anyone to reply me so I though i'd post here. Can anybody explain how you use a dark image in an MD when the theme is switched to dark and automatically switch to a light version of that image when the theme is set to light?
Thanks

Hi,
This problem is not specific to docusaurus but is related to dark mode support in general for server-rendered apps.

You can add a non-alpha opaque background to your image
You can try to convert it to svg and read css variables of the theme to color it
You can append 2 images in the html, and use CSS queries to display one or the other
You can render the image only on the client, based on theme, with the BrowserOnly docusaurus component

Example using CSS to select a theme-specific image:
img.dark, img.light {
  display: none;
}

html[data-theme='dark'] img.dark {
   display:
}

html[data-theme='light'] img.light {
   display:
}

This is pseudo-code, can't guarantee it will work but it's worth trying


AAD authentication by providing access token

Is your feature request related to a problem? Please describe.
The current AAD authentication does not allow the client to submit an auth token directly to connect to a database. Instead it provides ways to generate the token and then connect to the DB.
Describe the solution you'd like
Supply the auth token in the connection string to connect to the DB.
Describe alternatives you've considered
The existing mechanism is the alternative, however, it does not allow one to directly submit an auth token.
Additional context
None.

Issue cloned from: https://github.com/denisenkom/go-mssqldb/issues/752

I can't 100% speak for the original owners' intent, but I think the use of the specific connector today is based on a few considerations:

A connection string is inherently static, while a token is inherently dynamic.
The driver packages are designed to minimize the dependencies an app brings in based on its use case. If an app doesn't need "full" AAD, and it has some external mechanism to get a token, it can simply use the existing token-based connector instead of the azuread connector. How it gets the actual token at runtime is up to the application.
Early binding to the token in the connection string doesn't align to many real-world scenarios, as most tokens expire within an hour while the app can run some arbitrary amount of time.  Using a callback allows the app to provide non-expired tokens when needed.

There's a similar split between SSPI/integrated authentication and AAD authentication in the driver already. Apps using integrated authentication use a different connector than apps using AAD authentication.
This model is somewhat unlike that of other SQL client drivers like ADO.Net or ODBC where the connection string provides every possible parameter for every possible connection type. However, I don't know of any other SQL client driver that includes the token in the connection string. In ADO.Net you can programmatically set the token on the SqlConnection object or you can implement a SqlAuthenticationProvider callback to provide the token on connect.

@shueybubbles how about this then:
Interface for the clients
mssqlConnector, err := azuread.NewConnectorWithAccessTokenProvider(connString, tokenProvider)
conn := sql.OpenDB(mssqlConnector)

Changes in the driver
func NewConnectorWithAccessTokenProvider(dsn string, tokenProvider func(ctx context.Context) (string, error)) (*mssql.Connector, error) {

	config, err := parse(dsn)
	if err != nil {
		return nil, err
	}

	return mssql.NewSecurityTokenConnector(
		config.mssqlConfig,
		tokenProvider,
	)
}

The above change goes next to azuread.NewConnector(...). Refer: https://github.com/microsoft/go-mssqldb/blob/f21bac1629ad5381453368da0a8160fc40abec64/azuread/driver.go#L34
I've tested this change, sounds good?

Why wouldn't the app just use msdsn.Parse and mssql.NewSecurityTokenConnector directly instead of routing it through azuread and pulling in that extra code? We could put this new method in mssql instead just to make the Parse call on behalf of the client, I guess.

@shueybubbles done. PTAL at PR #26.

thx. Our team reviews issues and PRs on Thursdays, stay tuned.

@shueybubbles sure. FYI: closed #26 and created a duplicate #28 to re-sign the CLA.

Closed #26 and re-created as #28 to re-sign the CLA.

@shueybubbles ping, didn't get a review on this.


there is a problem when I set crop_type to "five"

Hi, thanks for sharing your code!
There is a problem when I set crop_type to "five". As is shown in picture.

I think you should run crop_datasets.py to generate cropped images first.

Thanks for the tip！


refactor: fixes to material on sheaves and stalks

Mostly this is installing the Opposite.rec' induction principle as the default @[eliminator], but also many other fixes and removing unnecessary steps from proofs.

[x] depends on: #4558

This PR/issue depends on:

leanprover-community/mathlib4#4558
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#4558
By Dependent Issues (🤖). Happy coding!


Response 500

Question
Hi All
I try to use tusd to  upload large file( ~1G)
After  100% completed  was shown in  browser console , http 500 error returned. (and upload failed)
[tusd] 2021/01/19 11:36:45 event="UploadCreated" id="98754d0a85dd5a81d3cb839c34c803ef+g_ZoA05ZqjmE87ULQPuXk4VgkjyO1di6oddh9IsPYlda8j4PYNfVPeH6u2_zExxsM2vnmUbpM4FVqJJXikfeahcW71RjDCTAlXj8I7zlRiU-" size="751566392" url="http://localhost:8005/api/v1/files/98754d0a85dd5a81d3cb839c34c803ef+g_ZoA05ZqjmE87ULQPuXk4VgkjyO1di6oddh9IsPYlda8j4PYNfVPeH6u2_zExxsM2vnmUbpM4FVqJJXikfeahcW71RjDCTAlXj8I7zlRiU-"
2021/01/19/ 11:36:45.108741537  [Info] vvv/pkg/upload.invokeHookSync 157 id:98754d0a85dd5a81d3cb839c34c803ef+g_ZoA05ZqjmE87ULQPuXk4VgkjyO1di6oddh9IsPYlda8j4PYNfVPeH6u2_zExxsM2vnmUbpM4FVqJJXikfeahcW71RjDCTAlXj8I7zlRiU-,size:%!s(int64=751566392),name:post-create
[tusd] 2021/01/19 11:36:45 event="ResponseOutgoing" status="500" method="POST" path="" error="Multiple errors occurred:
        NoSuchKey: The specified key does not exist.
        status code: 404, request id: BFA2563C1B12B816, host id: m1ORcd4vo91gwKa0nQUSIHdJ5YDMGQaz0Qk6nUpWkwMC5/HeZ8k+uDWQ9z23d12lIOQiBQTuQLQ=
        NoSuchKey: The specified key does not exist.
        status code: 404, request id: 856AEEF3BF64CEC4, host id: Nu3Kog6n1emh+jCxsGeD7rthWKCu+tg8Lhd+LanY98eGlrYvdFy1Z8hqFGySeUOOPV0HQomnb7E=
        NoSuchKey: The specified key does not exist.
        status code: 404, request id: A16815EA2028BBE7, host id: lkmxp+x7ABFV0U8Sed17dgNItIlFzuwU07qtrbGc+4fmvXKDfX/Mfmwtpb/3x+debQ+QhRXifZk=
        NoSuchKey: The specified key does not exist.
        status code: 404, request id: F7727AA847FFD4DF, host id: x4ISE39HlUifWbOjlR8lIUGXSjnJbwCiLPfgCMKGKn/VfePqmRMIG9wTY2fciUCVp5YZZXfj/2M=
        NoSuchKey: The specified key does not exist.
        status code: 404, request id: 07F90B6A975ED60D, host id: aAV70VSQXfqm/B0HKVgaFCVJzfaK0hqZw2F3ng6FS80THfkVlFeUc47PPT9gh0bwUdJWJCjP4Fs=
        NoSuchKey: The specified key does not exist.
        status code: 404, request id: 6N3T1MFJBSAS9K7P, host id: 2lbdEiwfuepqI8DlpsJinsEmR7ZiexnV5Y6jeGNzEEglKyNYehIUExfYGCmqNlIBEgL61+6oVSU=
        NoSuchKey: The specified key does not exist.
        status code: 404, request id: 9974A9571698FD21, host id: 2QD3+sXg5tHNve2eKtXYsiZkOwXNlz1XrEM0Y+wOc1If4gYzhnNewQ4Mgd9gI7AYlcNY5inStpA=
        NoSuchKey: The specified key does not exist.
        status code: 404, request id: CFEA3505F4598A05, host id: xeQI3QIjrkf+J+8ZjIzV1+OoUIp+VWkMsSxmqYBsO6Wa0yDiSo8rvfngQKoh4ujnjCVttSneqpc=
        NoSuchKey: The specified key does not exist.
        status code: 404, request id: 7A832F3FC2EDE7D6, host id: Q1IsLiylSlaxxNuXQwaHjl8SPXecgNwzAK8qFwtWaMycjKl9QXuRgrzqwk+CRjsNtR8p/LBwUBM=
        NoSuchKey: The specified key does not exist.
        status code: 404, request id: 63E0983E28DE0700, host id: Y3DQpPt2hAjaUnQ1n6TwKdkNPylBlbFXQxRWaKOY+bYX/98OmziLfACGwnaSvjrqFAsEW7hAN1Y=
" requestId=""

Setup details
Please provide following details, if applicable to your situation:
data flow : tus-js-client > https > ec2[nginx > tusd@8005 ] > s3
I just start the server in programmatically and using S3Composer as following ,leaving the default setting.
func S3Composer(s3EndPoint string,s3Bucket string,s3ObjectPrefix string) *tusd.StoreComposer { composer := tusd.NewStoreComposer() s3Config := aws.NewConfig() log.Infof("Using '%s/%s' as S3 endpoint and bucket for storage.\n", s3EndPoint, s3Bucket) s3Config = s3Config.WithEndpoint(s3EndPoint).WithS3ForcePathStyle(true) sess := session.Must(session.NewSessionWithOptions(session.Options{ 	SharedConfigState: session.SharedConfigEnable, })) store := s3store.New(s3Bucket, s3.New(sess, s3Config)) store.ObjectPrefix = s3ObjectPrefix store.UseIn(composer) locker := memorylocker.New() locker.UseIn(composer) return composer }

The errors from the logs is this:

NoSuchKey: The specified key does not exist

So you didn't configure aws.NewConfig() with the correct S3 credentials.

The errors from the logs is this:

NoSuchKey: The specified key does not exist

So you didn't configure aws.NewConfig() with the correct S3 credentials.

I alse meet this problem when i was trying to upload one 2.5G file, really hope there be a solution to this problen!

I alse meet this problem when i was trying to upload one 2.5G file, really hope there be a solution to this problen!

The errors from the logs is this:

NoSuchKey: The specified key does not exist

So you didn't configure aws.NewConfig() with the correct S3 credentials.

Thanks for replying.
I think I have configed ec2 with the correct S3 credentials because I succeed to upload small files to S3 , such as png file or pdf file.

The errors from the logs is this:

NoSuchKey: The specified key does not exist

So you didn't configure aws.NewConfig() with the correct S3 credentials.

Thanks for replying.
I think I have configed ec2 with the correct S3 credentials because I succeed to upload small files to S3 , such as png file or pdf file.

Ok, what does your tus-js-client code look like?

Ok, what does your tus-js-client code look like?

I believe I'm also seeing this same error. I'm using tus-js-client and writing to minio with s3 store. The client code simply has parallelUploads set to 2 and I've tried to remove as much as possible from the server side. My upload works for a small 10 MB video file and I see that there are 3 info files and 3 regular files with two being 5 MB and the last one 10 MB as expected. However when I try to perform an upload with a 677 MB file I end up with the same expected 4 partial files (info and content) and simply a new .info file for each post request that the client retries sends to concatenate the parts.
NoSuchKey: The specified key does not exist.
status code: 404, request id: 16FFE9C72F880F1E, host id:
NoSuchKey: The specified key does not exist.
status code: 404, request id: 16FFE9C72F8A8975, host id:

@RobertVillalba Can you test more file sizes and see if files smaller than 10MB work and files bigger than 10MB fail? tusd has two different method for concatenating uploads, depending on whether all partial uploads are bigger than 5MB.

I believe that you are correct. I created some zip files and was able to upload things smaller than 10MB (tested up to 9.6MB) but 10.6MB broke the upload concatenation. I also tried specifying a chunk size of 1MB as well for a final test to see if the behavior would change, but it did not.

I think I may have found the error. The CopySource does not take into account the store object prefix. After adding this in it seems that the uploads complete as expected (tested up to a 1 GB upload).

@RobertVillalba Your patch will be in this release: https://github.com/tus/tusd/releases/tag/v1.9.1


Added optional parameter "length" so that callers can specify length of range

Initially added for linter-jshint, make the display more accurate. Hope other linter providers can utilize this new parameter.

Hey @gekowa the code looks interesting, would you mind adding a few specs before this is merged in?

Whoops, forgot the specs, adding them now.

I'm curious what the entire point of this is... if you have a starting point and a length why do you need rangeFromLineNumber at all? Why not just generate a range directly from that information?

Can I say that the idea of having rangeFromLineNumber was given a starting point of specific line and return the rest of the line as the range?

That's the general idea behind it, yes... but if you have a starting point and a length the end point is easily calculated so a range can be generated just from that. There is no need to call a function to add two numbers 😛.

The idea is clear. What confuses me was line 163 from this file, range = Helpers.rangeFromLineNumber(textEditor, line, character), just can't figure out why calling rangeFromLineNumber to mark the rest of the line if only one word is the problem.

Because most linters only give a single (line, column) for a message, with no end point or length. Before this function was created linters were simply highlighting a single character, since that's all you could know was there from that information.
The problem with that is that it isn't very visible to the user, if the linter even bothered to show a single character (some just did a 0 length range which had no highlight at all). With this function you can pass it an editor, a line, and optionally a starting column and it will generate a range highlighting the entire line starting at the given point, leading to much better visibility to the user that something is wrong.
Ideally all linters would give a starting and end point for where a problem lies, but virtually none do that unfortunately so guessing like this is necessary. If you have a starting point and how far to go from there though, there is no need to guess so there is no need to call this function.

@gekowa Do you have a reason this functionality still needs to be added? Otherwise I think this should just be closed.

Thank you for the explanation, closing this one.


Update showcase.md

thank you for what you did!

hey, thanks for the contrib! we've gotten a lot of requests to be added to the showcase but can't accept everyone, we're mostly still looking for contributions that showcase something new that other sites in the showcase haven't yet


SWND not available now

Hi, @mikesprague
Udacity previously closed Senior Web Developer Nanodegree program, this program is closed currently, and will come back later in a brand new form.
Is Senior Web Developer Nanodegree discontinued?

@SiqingYu Thanks for catching that! I verified that all courses are still available (and still free of charge) so I have left them but noted that the nanodegree is no longer listed.


Add support for backup root certificate

Google states that they may switch certificates without warning to the backup certificate.
It would be great if this was supported.

@raphael-bmec-co FYI, this has been added to the ESP8266 example and hopefully the certificate tool for the MKR1000 is installing both certs. Just need to get it into ESP32 now :)


App.Metrics.Reporting.GrafanaCloudHostedMetrics add extra params to customise request

Thanks for helping out :+1:
Before submitting a pull request, please have a quick read through the contribution guidelines and provide the following information, where appropriate replace the [ ] with a [X]
The issue or feature being addressed
https://github.com/AppMetrics/AppMetrics/issues/688
#688
Details on the issue fix or feature implementation

allow customisation the request pipeline by passing the http request handler.
The parameter is optional so this won't be a breaking change.

Confirm the following

[x] I have ensured that I have merged the latest changes from the dev branch
[x] I have successfully run a local build
[x] I have included unit tests for the issue/feature
[x] I have included the github issue number in my commits

Could you create the PR on branch features/4.3.0 please


ffmpeg: Update to version 4.1.3

Supressed by scoopinstaller/scoop-main@80cd3e2c241f02bc6f6e58a386daf09e6f6d2455


Add to an in-progress job

Currently, calling backgroundFetch.fetch(tag, requests) will reject if there's already an in-progress job with that tag name.
Should it be possible to add to an in-progress job. This may great weirdness in UI.

Case 1
Let's make a case of downloading live transmission so it is possible to watch it later. Video transmission via DASH or HSL is actually just files, but many of them instead of one long. It's because of that they disappear after a while, but that solely depends on the service - I'm just trying to make it more believable.
You have video in chunks then, so you make multiple background-fetches and you do not know upfront amount of chunks that will be used to store it, cause it is live video. Presenting this task as many downloads is a bad idea, but without a possibility to append new jobs to already existing tag, you cannot group them.
Case 2
It can also be a reverse situation. You are grabbing video on the device and want to schedule sending this video in background, because even with small vids it may take some time or with networkType you want to make sure that sending will occur only cheap or free wifi. To save some time you want to send each chunk as soon it is ready.
You do not know how many chunks you will produce and you have to add them after they are done.
As implementation of background-fetch would probably made it so you loose access to request you want to send, like with Transferables when sending messages between workers, so they can be stored, without a need to update them afterwards, that could mean also freeing memory which may be huge deal with recording a video which means additional incentive to do it like I described.

I'm worried about the UI here. In either case you can have progress jumping around all over the place.
With case 1 you've got a race where the download may be one bgfetch job, but if the job completes before it'd added to, it becomes a new job.
With case2, you're in the foreground anyway, so bgfetch probably doesn't make sense. Once the user has stopped recording, if you still have 100mb to upload, you could schedule a bgfetch for that.

@jakearchibald
case 1 - if download of a chunk is finished before other starts - yes. That is true. However if their download overlaps - UI would be forced to display many entries for the same task as understood by a user.
case 2 - by mentioning workers I did not mean that in this task I'm uploading from a worker, but that Transferables have this property of disappearing from original context.
100mb chunk might be fifth produced in a row. Sending after recording means allocating 500mb. Crashing a tab means loosing all video. Just storing video while on poor connection would mean sending data after reopening application. From what I understand starting bgFetchJob right away would secure both video recordings AND sending them while user is away from the PWA.


FancyZones - let window span multiple zones

TLDR:
use windows+arrows to position window into one tile, then hold shift (windows+shift+arrow) to let it span multiple tiles
Example:
Gnome gtiles has this solution, you can setup pretty small tiles and then let window take multiple or all of them. (But it lacks other features from FancyZones, so....)
https://extensions.gnome.org/extension/28/gtile/
My usage:
Sometimes I'd need 6 windows on my secondary screen, sometimes I'd like to have only two, or three, this would give me option to set what I need on the fly without thinking if I have any layout already set for this. It will be much distraction free option for everyday use.

Read the documentation https://docs.microsoft.com/en-us/windows/powertoys/fancyzones#snapping-a-window-to-two-or-more-zones


Demos suspended

Looks like a great library! I wanted to see it work, but the demo's host account is suspended....

Demos are in demo/build folder, I just opened index.html locally and they're all there.

@somewebmedia Can you host the demos using GitHub pages?

Demos moved to gh pages: http://somewebmedia.github.io/hc-sticky/


How to approve GitHub OAuth access to Tugboat

I worked with a client today to figure out why a new GitHub organization would not show up in Tugboat's list when selecting a new Repository. Turns out, the default settings for a new organization require approval for OAuth apps, which is a good thing.
The problem in this case is that the user had already authorized Tugboat, and created a new org after the fact. That does not trigger any sort of "refresh" when re-authenticating with GitHub, and I couldn't find a way to force that programmatically.
The "fix" is for the user to go into their authorized OAuth apps, and either request or grant access (depending on their permission level in the org) to Tugboat.
This should probably be noted in the documentation, as I'm sure it's going to come up again sometime.

https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps
https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization

Here's CircleCI's documentation on the issue: https://support.circleci.com/hc/en-us/articles/115014599088-My-GitHub-organization-is-not-listed

Do we think the Troubleshooting section is the appropriate place for this? Or in the section about connecting with git providers? https://docs.tugboat.qa/setting-up-tugboat/connect-with-your-provider/
(Or maybe both? Spell out details in connecting with providers, and then adding a troubleshooting question about why can't I see an organization in the list when selecting a new repository, linked to instructions? And maybe also a callout to the details in the "Add repos to the project" page...)

I think Troubleshooting makes more sense. This only applies to orgs that are created after you've already gone through the provider connection steps.
Also, the comment on that CircleCI article gave me an idea on how to maybe incorporate this into the UI.


ARM Cortex-R52 doesn't have SPSR_hyp

Describe the bug
I think I have found an issue with the startup code for the Cortex-R52, specifically this line: https://github.com/zephyrproject-rtos/zephyr/blob/fd0767557439d04c4a220a9857e901d8d71498db/arch/arm/core/aarch32/cortex_a_r/reset.S#L68
I think the Cortex-R52 doesn't support spsr access through the spsr_hyp register. I did some research and found the following:

The Arm® Cortex®-R52 Processor Technical Reference Manual Revision r1p3 (https://developer.arm.com/documentation/100026/0103) doesn't mention spsr_hyp at all.

The ARM Architecture Reference Manual Supplement - ARMv8, for the ARMv8-R AArch32 architecture profile (https://developer.arm.com/documentation/ddi0568/latest) references it for example on page H1-274 while describing aarch32/functions/system/SPSRaccessValid, which explains how an SPSR access is determined valid. It indicates that the access to SPSR_hyp is invalid if the accessing mode is not monitor mode.

The Arm Architecture Reference Manual for A-profile architecture (https://developer.arm.com/documentation/ddi0487/latest) says on page G8-9401: "SPSR_hyp is accessible only in Monitor mode". I think this is also valid for the R52 because nothing specific is mentioned in the Reference Suplement which has an entire section on the differences between Armv8-A and Armv8-R.

In conclusion, I think this line should be "msr SPSR, r0" since the Cortex-R52 doesn't support monitor mode.
Additional context

I came across this because I'm trying to implement the Cortex-R52 in Qemu and a bunch of stuff breaks if you try to execute this instruction.
I know that the Zephyr executes on the ARM fast models, but is there a chance it shouldn't?
I don't have any physical hardware to test this so I was wondering if anyone could confirm or deny this.

Hi @julien-massot ,
Thanks for the quick reply!
I checked the Bare-metal_examples that you mentioned and can confirm that they use the same instruction. Do you know if Zephyr was started in EL2 when it ran on physical hardware? Otherwise, it wouldn't get to that instruction, right?
I guess the case is pretty clear if this runs on physical hardware, I'll have to change Qemu to handle this accordingly.

Hi @julien-massot ,
Thanks for the quick reply!
I checked the Bare-metal_examples that you mentioned and can confirm that they use the same instruction. Do you know if Zephyr was started in EL2 when it ran on physical hardware? Otherwise, it wouldn't get to that instruction, right?
The processor always start in Hypervisor mode, if Zephyr is the first system then it will be started in Hyp mode/EL2.

In case we are not started in Hyp mode we jump to the EL1 reset handler:
https://github.com/zephyrproject-rtos/zephyr/blob/fd0767557439d04c4a220a9857e901d8d71498db/arch/arm/core/aarch32/cortex_a_r/reset.S#L54

yes it was, and pretty convenient when restarting zephyr with gdb without doing a cold reset:)

In conclusion, I think this line should be "msr SPSR, r0" since the Cortex-R52 doesn't support monitor mode.

Since hyp mode is the highest exception level and no monitor mode for v8r aarch32, EL2(hyp) can assess spsr_hyp seems reasonable.

Okay, I guess that resolves this. Weird that it isn't described in more detail in the docs.

So the Qemu supports the spsr_hyp? I am sure FVP supports it. But always, some implementations are different between Qemu and FVP and even real hardware, especially for this kind of "new core"

Hi; I was pointed to this issue since Tobias has posted his patches to add R52 support to the QEMU mailing list.
The behaviour of "msr spsr_hyp, r0" when executed from anything except Monitor mode is architecturally UNPREDICTABLE, and this doesn't change for v8R. You can see this in the v8R Supplement pseudocode function aarch32/functions/system/SPSRaccessValid:
when '11110' // SPSR_hyp
    if !HaveEL(EL2) || mode != M32_Monitor then UNPREDICTABLE;

The use of this instruction in the Developer Studio sample code is a bug in that sample code, that went unnoticed because the FVP and the Cortex-R52 hardware happen to choose to handle this UNPREDICTABLE case as "allow the access". I've reported this bug and it should be fixed in some future DS version.
The fix is simple: since you know the code is executing in Hyp mode, just use "msr spsr, r0".

Hi; I was pointed to this issue since Tobias has posted his patches to add R52 support to the QEMU mailing list.
The behaviour of "msr spsr_hyp, r0" when executed from anything except Monitor mode is architecturally UNPREDICTABLE, and this doesn't change for v8R. You can see this in the v8R Supplement pseudocode function aarch32/functions/system/SPSRaccessValid:
when '11110' // SPSR_hyp
    if !HaveEL(EL2) || mode != M32_Monitor then UNPREDICTABLE;

The use of this instruction in the Developer Studio sample code is a bug in that sample code, that went unnoticed because the FVP and the Cortex-R52 hardware happen to choose to handle this UNPREDICTABLE case as "allow the access". I've reported this bug and it should be fixed in some future DS version.
The fix is simple: since you know the code is executing in Hyp mode, just use "msr spsr, r0".

Thanks for your clarification, would you like to mention in your reported ticket that FVP doesn't handle the msr spsr, r0? So far we cannot change it to "msr spsr, r0".
Specifically, I have tried "msr spsr, r0" in FVP_BaseR_Cortex-R52x1 FVP (version 11.17.3 (Jan 23 2022)), after "msr spsr, r0", the SPSR.E bit won't be set to 0, so that the core work as big-endian instead of little-endian and will crash.

@pm215 Really appreciate it if you would like to have a look

FVP: FVP_BaseR_Cortex-R52x1 with version 11.17.3 (Jan 23 2022)

command: FVP_BaseR_Cortex-R52x1 -C bp.sram.enable_atomic_ops=1 -C bp.refcounter.non_arch_start_at_default=1 -C bp.pl011_uart0.out_file=- -C bp.pl011_uart0.unbuffered_output=1 -C bp.terminal_0.start_telnet=0 -C bp.pl011_uart1.out_file=- -C bp.pl011_uart1.unbuffered_output=1 -C bp.terminal_1.start_telnet=0 -C bp.pl011_uart2.out_file=- -C bp.pl011_uart2.unbuffered_output=1 -C bp.terminal_2.start_telnet=0 -C bp.pl011_uart3.out_file=- -C bp.pl011_uart3.unbuffered_output=1 -C bp.terminal_3.start_telnet=0 -C bp.vis.disable_visualisation=1 -C bp.vis.rate_limit-enable=0 -a /path/to/zephyr.elf
/path/to/zephyr.elf should be the right path of the zephyr image

diff:

diff --git a/arch/arm/core/aarch32/cortex_a_r/reset.S b/arch/arm/core/aarch32/cortex_a_r/reset.S
index d6232cb949..bfa76e4f09 100644
--- a/arch/arm/core/aarch32/cortex_a_r/reset.S
+++ b/arch/arm/core/aarch32/cortex_a_r/reset.S
@@ -65,7 +65,7 @@ SECTION_SUBSEC_FUNC(TEXT, _reset_section, __start)
     mrs r0, cpsr
     bic r0, #MODE_MASK
     orr r0, #MODE_SVC
-    msr spsr_hyp, r0
+    msr spsr, r0

     ldr r0, =EL1_Reset_Handler
     msr elr_hyp, r0

This point (line 68) is at the very beginning of the entry, it can be easily reached with DS. And can be easily checked that when we use msr spsr, r0, after this inst executed, the spsr does not equal to r0 (at least the SPSR.E bit is not right) https://github.com/zephyrproject-rtos/zephyr/blob/fd0767557439d04c4a220a9857e901d8d71498db/arch/arm/core/aarch32/cortex_a_r/reset.S#L48-L74
zephyr-spsr-issue.zip includes the two images a)working-with-spsr_hyp and b)not-working-with-spsr

Ah, I see what's happened. This is my mistake with the instruction I suggested. The right/full form of the instruction is msr spsr_<fields>, r0, where <fields> is a set of letters saying which fields in the SPSR should be written. If you look at an objdump of the non-working binary you can see:
    13d0:       e169f000        msr     SPSR_fc, r0

that since the source file didn't specify fields the assembler has defaulted to fc, which means "update bits 7:0 and 31:24 only". To update the whole 32 bits of SPSR we want:
  msr spsr_cxsf, r0

Apologies for misleading you there.

Ah, I see what's happened. This is my mistake with the instruction I suggested. The right/full form of the instruction is msr spsr_<fields>, r0, where <fields> is a set of letters saying which fields in the SPSR should be written.

That's it! Thanks for your clear explanation. I also confirmed it works when we use spsr_cxsf :)


Update the submission service configuration with MongoDb connection

Acceptance

When running the composed image submission service should be able to connect to the MongoDb
README should be updated with additional configuration values required by submission service

Notes
This issue depends on https://github.com/flam-flam/submission-service/issues/7 completion

@timberhill I've started this one, and started getting ideas, wanted to quickly on few things.

Obligatory disclaimer: I am treating this repo purely as a dev environment setup & the compose\docker-compose.yaml will not be used for actual deployment.

.env
Is there any value in not having the default .env file in the repo ?
We can exclude sensitive secretshowever I don't see value in obscuring the Mongo credentials (as long as we don't use the same ones for actual deployment when we get to it). Does this make sense ?
Makefile
Do we need to specify the .env file explicitly, e.g. --env-file ./env.env in the up command definition ?
I have to admit that I was too lazy to set it up on Windows, and I was using shell commands directly, so I could have missed some extra magic.
Extra tools
We could use mongo-express to provide a convenient way to look into the DB without using mongosh. It is fairly easy to add

.env is in .gitignore to prevent people from committing secrets to the repo. But we could have a example.env of course
Not sure about where the .env is set explicitly. I think that docker compose uses a file called .env by default though.
A DB browser sounds hella nice, yes!

@timberhill I've noticed that it is in .gitignore, was questioning whether it should be. However that is fair, have not considered the risk of accidentally committing secrets.
Will add and example.env then.
One more thing - I am not considering MONGO_INITDB_ROOT_USERNAME & MONGO_INITDB_ROOT_PASSWORD (and MONGO_CONNECTION_STRING that I am about to add) to be sensitive values, do you agree ?
Regarding the .env file - I believe it does not do that on Windows by default.
If I don't specify the file explicitly - I'm getting the following output:
PS C:\Storage\development\flam-flam\dev-stack> docker compose -f compose/docker-compose.yaml up  -d
time="2023-03-22T21:28:12+01:00" level=warning msg="The \"REDDIT_CLIENT_ID\" variable is not set. Defaulting to a blank string."
time="2023-03-22T21:28:12+01:00" level=warning msg="The \"REDDIT_CLIENT_SECRET\" variable is not set. Defaulting to a blank string."
time="2023-03-22T21:28:12+01:00" level=warning msg="The \"DISPATCHER_BRANCH\" variable is not set. Defaulting to a blank string."
time="2023-03-22T21:28:12+01:00" level=warning msg="The \"COMMENT_BRANCH\" variable is not set. Defaulting to a blank string."
time="2023-03-22T21:28:12+01:00" level=warning msg="The \"MONGO_CONNECTION_STRING\" variable is not set. Defaulting to a blank string."
time="2023-03-22T21:28:12+01:00" level=warning msg="The \"MONGO_INITDB_ROOT_PASSWORD\" variable is not set. Defaulting to a blank string."
time="2023-03-22T21:28:12+01:00" level=warning msg="The \"MONGO_INITDB_ROOT_USERNAME\" variable is not set. Defaulting to a blank string."
time="2023-03-22T21:28:12+01:00" level=warning msg="The \"MONGO_INITDB_ROOT_PASSWORD\" variable is not set. Defaulting to a blank string."
time="2023-03-22T21:28:12+01:00" level=warning msg="The \"MONGO_CONNECTION_STRING\" variable is not set. Defaulting to a blank string."
time="2023-03-22T21:28:12+01:00" level=warning msg="The \"MONGO_INITDB_ROOT_USERNAME\" variable is not set. Defaulting to a blank string."
[+] Running 5/0
 - Container compose-comment-1        Running                                                                                0.0s
 - Container compose-mongodb-1        Running                                                                                0.0s
 - Container compose-submission-1     Running                                                                                0.0s
 - Container compose-dispatcher-1     Running                                                                                0.0s
 - Container compose-mongo-express-1  Started

That is not the case when I use docker compose -f compose/docker-compose.yaml --env-file ./.env up -d
Could you check if the above runs properly on linux ? If so - we could just specify file explicitly regardless of the OS.
DB browser is settled then :)

Yes, mongo creds are not sensitive, all good. This is only for local development. Any secrets will be set in kubernetes secrets and mounted onto a pod in any kind of "production" use.
Setting the .env file explicitly works on linux, all good!

And here goes the PR: https://github.com/flam-flam/dev-stack/pull/3
Ideally https://github.com/flam-flam/submission-service/pull/10 should be merged first though


Fcs july 2020

37.0.0
This release brings a number of new changes, including a massive enhancement to SemanticClassification types thanks to @cartermp.
From dotnet/fsharp:333eb82c8..d9e070a9d:

now allows for multiple implementations of generic interfaces (preview feature) (thanks @0x53A!)
the default assembly set for script resolution now includes System.Numerics (thanks @KevinRansom)
#r nuget package resolution is now committed eagerly, instead of delayed (thanks @KevinRansom)
reduced allocations for some strings in the compiler (thanks @kerams)
better printing for SRTP constraints (thanks @abelbraaksma/@realvictorprm)
more expressive DUs for semantic classification (thanks @cartermp)
Fixed tostring/equality for StringText (thanks @deviousasti)
Fixed error text for FS0874
Disallow assignment to C# Const/Readonly properties (thanks @baronfel)
Allow Int64.MinValue as a valid nativeint literal (thanks @abelbraaksma)
Enhancements to the nameof feature (preview feature)
String interpolation (preview feature)

Alright, let's release this thing!


⚠ Bofrost.be has degraded performance

In 12759b6, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2965 ms

Resolved: Bofrost.be performance has improved in 9d75b50.