Nukieplanet gets syndie airlocks

About the PR

the nukie planet now has syndicate airlocks for syndicate syndie agents
i also accidentally moved the fake nuke disk and free syndie pAI in the process
Why / Balance

Syndie controlled location? syndicate access doors, simple as
Media

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

Changelog
:cl: JoeHammad

tweak: The nukie planet now has syndicate airlocks

by the way, im editing the nukie shuttle right now, so i savemap or savegrid? i think its savegrid but its in /Maps/ for some reason and is making me think twice

ill save it as a grid

didnt work


MudListItem: SecondaryText Feature

Description

Added SecondaryText parameter to MudListItem.
How Has This Been Tested?

Already using with MudListItemExtended.
https://github.com/MudBlazor/MudBlazor/assets/78308169/450bdca1-67ac-43f4-8daa-c371a73b2536
Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

Checklist

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

@henon test done.

Thanks!

@henon I was reminded that mud is missing a basic implementation of  .
Taking this opportunity, what do you guys think about introducing a simple implementation?

@Alerinos I struggle to imagine how it should look like compared to MudList. Can you share examples from other toolkits that have what you mean?

@henon

I made such a thing, it is a simple list. I am missing such a component in MudBlazor.
You might want to make a new component called <SimpleMudList>?

That is so simple that it is probably not worth adding this. Can't you just directly use <ul> and put <MudText> inside the  <li> ?

@henon
You can manually do it but it spoils our look and doesn't fit with the rest.
Having the Mud component everything is nicely compatible with each other, if we want to change the look of the layout everything changes nicely. We should have as many components as possible
I'm just in migration, MudList requires T parameter, shouldn't we allow nullable?
Currently this is what my code looks like:

I'm just in migration, MudList requires T parameter, shouldn't we allow nullable?

Nullable types are allowed, for instance int?.

@henon

I meant that MudList requires T, should be default value or nullable possible.

I know, I would prefer that too, but Blazor doesn't allow it

Can't we set a default T, or make it null?
    public partial class MudList<T> : MudComponentBase, IDisposable : this(default(T))

Alternatively, it is possible to do “overloading” and create two classes, one with T and one without. In this case, we will handle everything.


Refactor/dssm preprocessor

Codecov Report

Merging #389 into 2.0 will not change coverage.
The diff coverage is 100%.

@@         Coverage Diff         @@
##            2.0   #389   +/-   ##
===================================
  Coverage   100%   100%
===================================
  Files        35     35
  Lines      1053   1038   -15
===================================
- Hits       1053   1038   -15

Impacted Files
Coverage Δ

matchzoo/preprocessor/dssm_preprocessor.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Update to use custom sha256 fingerprints in stash for files

use stash to store sha256 fingerprints
add migration tool to move hashes to stash fingerprints, must be run manually add requirement for stashapp-tools for new file_set_fingerprints() func

note to self: add migration task in code


feat: add inactivity-timeout to sessions

Adds the ability for sessions to time-out after a period of inactivity. "Activity" is defined as refreshing the session.
This can be configured by setting the GOTRUE_SESSIONS_INACTIVITY_TIMEOUT to a duration.
Since this PR modifies the database by adding a new refreshed_at nullable column to sessions, it also adds some useful columns to the sessions table to track the User-Agent and IP address that performed the refresh / session creation.

Added one change I did not foresee and that is, if the session has no refreshed_at value it should use the token's updated_at value instead so that old sessions that had not been touched in a while (but are still valid per the inactivity timeout) don't just get killed.


Update nginx.conf.template

server_name is not necessary and can lead to misinterpretation, in case the host value should be read from the header X-Forwarded

Implemented in pull request "feature/137-integrate-with-nina"


False Positive on Microsoft.AspNet.FriendlyUrls.Core

False positive on Microsoft.AspNet.FriendlyUrls.Core - reported as cpe:2.3:a:microsoft:asp.net:*:*:*:*:*:*:*:*

Location to download package: https://www.nuget.org/packages/Microsoft.AspNet.FriendlyUrls.Core/
I think this may be a false positive as I have been unable to find any refrences to it being vulnerable, similarly when running audit.net & safenuget they do not report it to be vulnerable

In testing with 6.0.3-SNAPSHOT - these FP appear to be resolved.  I did add a rule for another library while researching the reported FP.  Thanks!

Brilliant thanks @jeremylong


shortFlag XOR longFlag possibility

One thing that happens with having shortFlag be mandatory is that since its only a single character, you quickly get collisions, and thus are forced to use random characters for an option (-y, --check-file). I think in such a case, it would be better to have the option to specify only a longFlag. You could make a case for the other direction too of course, thus I'm thinking it be useful to have the ability to exclusively choose a shortFlag or longFlag for an Option.

@beltex In general I think having both short and long flags is the best choice, but I suppose there are cases where it doesn't make sense. I'll see if I can tackle this without having to drop optionals all over the place.

@jatoben Awesome, thanks! :)


Fix missing originating element in generated adapters

Fixes #233
I think before this Just Worked because the generated adapter was a nested type of a class that did have its originating element set, but when it's top-level it does need it set anyway. This sets it for both just to be doubly sure.
CC @gavra0

In 1.3.70 KAPT will have better logging regarding this. To figure out what is causing it to fail, you can create a breakpoint in https://github.com/JetBrains/kotlin/blob/a9686c94474c9d442db61b45f60e6ff326fdb7db/plugins/kapt3/kapt3-base/src/org/jetbrains/kotlin/kapt3/base/incremental/incrementalProcessors.kt#L119 (this is tag v1.3.61).

I've figured it out. This is a bug in JavaPoet, where calling TypeSpec#toBuilder() leaves out the originating elements.
https://github.com/square/javapoet/issues/749


Implement DECIMAL type support for mysql

Implement DECIMAL type support for mysql.
Close #202

Please add integration tests to mysql-types under tests/. See postgres-types for an example of big decimal tests.

General framework of this looks fine. We do want to support both text and binary formats.
Assigning @abonander to review the details when he gets a chance as he did the big decimal stuff for postgres.

@xiaopengli89 Sorry for not pointing this out but you'll need to add the bigdecimal feature to CI for mysql around here: https://github.com/launchbadge/sqlx/blob/master/.github/workflows/rust.yml#L206

Thanks for the work on this. 😄


Page title updates

As a developer I want to update the browser window title when the current route changes.
While there is no special support for this use case, it is straightforward to implement via the onAfterEnter route component lifecycle callback (see #23):
onAfterEnter() {
  document.title = 'Title';
}

Related use case:
Sometimes we need to wait for something else to update the page title. For example, a request to the API to know the title of the post. The same could apply to other meta tags such as description.

The problem with the onAfterEnter callback approach is that it can be seen as mixing concerns - the UI component becomes responsible for the page title, which could be understood as the responsibility of the routing table.
If the router instance itself had callbacks (i.e. hooks), users could implement this feature themselves fairly easily:
// strawman
const router = new Router(document.querySelector('main'), {
  onAfterEnter(location, commands, router) {
    document.title = `App | ${location.route.name ?? ''}`.replace(/ \| $/, '');
  }
});

See also #465


Update Composer dependencies (2021-04-29-00-02)

Visual regression test passed!
View the visual regression test report


Unified Distributed Storage API implementation and go dependency pack…

…age updates
What type of PR is this?
Unified Distributed Storage API Implementation and Dependency Package Follow-Up

What this PR does / why we need it:
Complete API design of storage and go dependency package updates

your force push overwrite the origin commit, so reviewers can not get the delta change


[EBPF-429] Increase the limit of allocations in ebpfcheck test to avoid flakes

What does this PR do?
Increase the limit of allocations in the MultipleBatch mode of the entry count function in ebpfcheck.
Motivation
The test pkg/collector/corechecks/ebpf/probe/ebpfcheck.TestHashMapNumberOfEntriesNoExtraAllocations/10000MaxEntries/MultipleBatch was detected as flaky. It fails very sporadically due to an extra allocation over the limit defined as acceptable. Investigating further, it seems that Go might do an extra allocation in the map that maintains the list of keys that were already seen. As we do not have any control over how Go does those allocations, I've just increased the limit to avoid the flakes.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Trivial level solutions

From a discussion at the Explorable Explanations Slack:

15 - easy to fix. Regarding the first screenshot, we would need to change the detector element to only receive photons on one side.
Re other comments from the Explorable Explanations Slack user, I think highlighting the ket viewer and its options, rendered photon on hover in the hints section - that would all help understand what is happening with the photon on the board. Although I am not sure if we can (or should) do anything with this right now.
Also - at a later stage - changing the photon itself, the rendering can be improved.

One thread per issue at a time.
Detecting the direction of the beam would need some changes (these are on the way in quantum-tensors, as a part of more general measurement).
Also: do you have an idea of how to show a plant with light coming from a different angle?

Not sure if I understand what do you mean by showing a plant with light coming from a different angle. The photon getting to the plant from other direction than the mouth? I would leave it green, not affected, or with an outline only, but not "energized". Something like a mirror or beamsplitter absorbing the photon when placed not diagonally.

Currently we don't check for the direction of the photon to trigger the detection event. So the normal detector acts as a 4-way detector. This change has to be made in quantum-tensors elements.


PR #14499 possible BC breaking

Follow-up to https://github.com/yiisoft/yii2/commit/8ae2223c6a50eda8534ea187357df1a167b65cdd
The updated code follows the order, described in documentation:

Built-in validator
Method in model or closure
Custom validator

But still it can break code, relied on previous not-documented behaviour.
How about mentioning it in UPGRADE.md?

Yes, could be mentioned.


Docs update: Load Android Activity (Fragment) inside RN Native Component

Description
I have a RN Native Component and I would like to load the Android Activity inside of it.
From the RN Docs I see that there is a way to load the RN App inside an Android Native App, I need the other way around and looks likes there are a bunch of other people looking for this, would be nice to update the docs with such info.
I know that is not possible to load the Activity inside the RN Native Component but do you know any workaround?
Maybe using an Android Fragment? Convert the Activity code into a Fragment?
Thoughts?
React Native version:
0.64
Steps To Reproduce

Create a RN Native Component
Try to load an Native Android Activity inside the new RN Native Component.

Expected Results
The Activity is initialized and displayed inside the Native Component or inside a RN View.
Snack, code example, screenshot, or link to a repository:
https://stackoverflow.com/questions/69562692/display-android-native-activity-into-react-native-view

Yep, that's the direction I'm taking however how can developers proceed?
Do we convert the Activity to Fragment?
What are things that one should keep an eye on during the process?
Such information is not available in the docs, and per what I've seen there is a bunch of people looking for this.

You should look at the docs, how Native Components are built in android and iOS. Use that instead of an Activity.


Two Questions

Does PKHUD supports obj-c (i.e., calling it from an obj-c class)?
Can I customize the font?

Way to go for this really cool and beautiful library!

Yes you can use it with Obj-C.
Simple as:

[[PKHUD sharedHUD] ...];

Yes. You can either provide an entirely custom content view for the HUD all together, or you can access the titleLabel etc. properties and change their font.

Great - thank you!

@pkluz
Can I cutomize HUD's frame  and how?
Sorry to that  not read code and just go here to ask you question.
And Thanks for this library

@c826 it's better to read the code or at least search for similar questions (#117). By the way I've created a Wiki with the FAQ page

@PGLongo my situation is more complex than that, But anyway thanks for that, i'll read the code and ifx it. Thank you.

@c826 you are welcome. If your situation is more complex you should give more details. I suggest to use Stackoverflow as I've written in the README.md


Merge back release 2.37

Hmm, ui_build_and_release CI check still failing, @Nexucis?

myeah this shouldn't have been triggered since it's a PR and not a push event. That's weird.
And the other things that worried me is it failed to publish which is a chance for us. But it said it's not authorised to publish the package which is weird.

ah ok. What a mess in the github action. Actually this github action has been triggered by the tag pushed not by this PR... So we are good here.
The only thing annoying now is why it is not authorised to publish the packages ....


Add hint to where to put IdProvider

When not at the topmost level, a warning keeps showing.

[x] Use a meaningful title for the pull request. Include the name of the package modified.
[ ] Test the change in your own code.
[ ] Include the URL where we can test the change in the body of your PR.

This pull request:

[ ] Fixes a bug
[ ] Adds additional features/functionality
[x] Updates documentation or example code
[ ] Other

I'm not sure what you mean by topmost? Would you mind sharing the structure you had before that didn't work?
As long as it wraps all of your Radix components it should be fine.

I'm not sure what you mean by "topmost". Would you mind sharing the structure you had that didn't work?
As long as it contains all of your Radix components it should be fine.

In a NextJS app (_app.js) this structure kept giving me the warning:
return (
<QueryClientProvider client={queryClient}>
      <Hydrate state={pageProps.dehydratedState}>
        <Provider session={pageProps.session}>
          <GlobalStyles />
          <GoogleTagManager>
            <IdProvider>
              {shouldDisplayMobilePage ? (
                <MobileWarningPage />
              ) : (
                <>
                  <Component {...pageProps} />
                  <Toaster />
                </>
              )}
            </IdProvider>
          </GoogleTagManager>
        </Provider>
      </Hydrate>
      <ReactQueryDevtools initialIsOpen={false} />
    </QueryClientProvider>
);

// this fixed it:

return (
    <IdProvider>
      <QueryClientProvider client={queryClient}>
        <Hydrate state={pageProps.dehydratedState}>
          <Provider session={pageProps.session}>
            <GlobalStyles />
            <GoogleTagManager>
              {shouldDisplayMobilePage ? (
                <MobileWarningPage />
              ) : (
                <>
                  <Component {...pageProps} />
                  <Toaster />
                </>
              )}
            </GoogleTagManager>
          </Provider>
        </Hydrate>
        <ReactQueryDevtools initialIsOpen={false} />
      </QueryClientProvider>
    </IdProvider>
  );

@hamatoyogi Thanks for that. Had you tried lifting it one level at a time to try identify which one of those components causes it to bug out? For example, wrap it around <GoogleTagManager> first and if that doesn't work still, try around <Provider session={...}> etc.
It would be super helpful to understand which one is the culprit so we can improve the IdProvider as it shouldn't need to be "topmost".  Is your codebase in a public repo anywhere?

Closing this as IdProvider has been deprecated in the latest release.


Cannot find module 'langchain/embeddings/hf_transformers' in node with version 0.0.143

I want to work to HuggingFace Embedding, the "langchain" is "^0.0.143" with preinstalled "@xenova/transformers": "^2.5.4".
I am trying to work with import { HuggingFaceTransformersEmbeddings } from "langchain/embeddings/hf_transformers";
but the node project comes with typescript compiling error :
embedding_test.ts:1:51 - error TS2307: Cannot find module 'langchain/embeddings/hf_transformers' or its corresponding type declarations.
so I look into the source code on the embedding and found that
https://github.com/hwchase17/langchainjs/blob/78eccbaa446a53bb805f005b0a91eadd320caa10/langchain/src/embeddings/index.ts
export { OpenAIEmbeddings } from "./openai.js";
export { CohereEmbeddings } from "./cohere.js";
export { Embeddings } from "./base.js";
export { FakeEmbeddings } from "./fake.js";

that HuggingFaceInferenceEmbeddings is not included. is it the reason the project can't find module 'langchain/embeddings/hf_transformers'

HFTransformers was added in 0.0.144, so you'll need to upgrade (but I think you figured that out!)

Hello,
I've got the same issue, my langchain package version is 0.0.146
Here is a simple way to replicate this issue
import { HuggingFaceTransformersEmbeddings } from 'langchain/embeddings/hf_transformers';

const modelName = process.env.EMBEDDING_MODEL_NAME;

(async () => {
  console.log('Load embeddings...');
  const embeddings = new HuggingFaceTransformersEmbeddings({
    modelName: 'ggml-gpt4all-j-v1.3-groovy.bin'
  });
  console.log('Embeddings loaded!')


Add caching for chunk sizes

This PR fixes #43. It adds an extra field chunk_lengths to DTable. This is used by chunk_lengths function for caching. This code assumes DTables are immutable and sizes don't change.

This is good. There are more cases when chunk_lengths is preserved and that's map, transform and probably something else
You can add it here or as a separate PR later

Will add it as a separate PR later


find libblas.so correctly. use libblas.so for testing by default inst…

…ead of libacml.so
fix issue #168 , issue #155 and issue #142.

the fail on Travis was due to the lack of gfortran compiler on travis system at the moment


@types/jsonwebtoken dependency

[READ] Step 1: Are you in the right place?

For issues or feature requests related to the code in this repository
file a Github issue.

If this is a feature request make sure the issue title starts with "FR:".

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general Firebase discussion, use the firebase-talk
google group.
For help troubleshooting your application that does not fall under one
of the above categories, reach out to the personalized
Firebase support channel.

[REQUIRED] Step 2: Describe your environment

Operating System version: _____
Firebase SDK version: _____
Library version: latest
Firebase Product: _____ (auth, database, storage, etc)

[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
Relevant Code:
// TODO(you): code here to reproduce the problem

Why is @types/jsonwebtoken a dependency and not a dev dep?
See https://github.com/firebase/firebase-admin-node/blob/master/package.json#L28

I believe it is required to support custom token minting and ID token verification in Firebase Auth.

But those are just typescript typedefs no? I can't see them being required (but I can be wrong ofc)

We might be able to get rid of it. I'll try it out and if all goes well fix it in a future release.


cito.lua fails on citations without a cito property

If cito.lua is applied, it throws the following error, if a citation does not have a cito property:
Error running filter cito.lua:
Could not read list: Could not get Inline value: Expected a string but got a nil

It should work anyway and should default to citation or cites.

Fixed in aef0e63ba9605a922bfb279173f7481dee07ada6.


Configure gradle build scan plugin

This small PR configures the build-scan Gradle plugin (https://guides.gradle.org/creating-build-scans/) which yields further insight into the build, allowing the team to make informed decisions on where and when the build may be tweaked to get faster, more performant builds.

👍 thanks!

Thanks! 😄


Performance fix for CoreMessaging_GetMessageConversations and Journal_ListForGroup  Procedure

##Summary
Fixes performance issues experienced with CoreMessaging_GetMessageConversations procedure. The where clause for filtering paging could take 5+ minutes to properly return the result set due to the way the query was written. Added additional CTE to not have to calculate the row count range inside of the where clause.
Fixes issue with Journal_ListForGroup procedure where the page size is set, but the result set is less any deleted journal entries, so the page size is almost always greater, and thus you can never "get more" via the get more button. Proc change allows for Row_number to work properly depending on if you want deleted posts or not.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: ChrisHammond sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@ChrisHammond have you created a GitHub issue? For a quick reference on the process, see this document.

I didn't because someone....... @ohine..... told me not to bother in these two cases :D

I am a fan of having a descriptive pull request description instead of just saying fixes #xyz and putting the info in an issue.

Damn, I noticed again, how badly these procedures were written.
Regarding CoreMessaging_GetMessageConversations: what about dropping the paging altogether and use SELECT TOP (@NumberOfRecords) FROM Conversions WHERE @MessageID > @AfterMessageID ?

@ChrisHammond Do you have any metrics on the sizes of tables that you used to validate these changes against?  I want to make sure we test/validate based on a proper sized data set.

IMO one major performance issue with CoreMessaging: there is no "delete" option, i.e. the tables are growing indefinately. This also conflicts with GDPR.

@mitchelsellers customer that I was addressing the CoreMessaging issue fix for had
~11k records in Messages
~156 unread messages for the user who was attempting to "load more"
When the load more request fired, it would time out server side, manually running the proc with the same parameters would take 5+ minutes.
After my modification, <1 second for result.

Thanks for the confirmation @mitchelsellers


The improvement on GAT

Hi, I check the number of GAT on Pubmed is about 79.0, and the performance of GAT in the figure is about 76% which corresponds to the "None" method. And I am also curious about why GAT performed worse than GCN on CORA/CITESEER/PUBMED?

The fact that GAT actually performs worse than GCN in a fair and thorough experimental setup is not new. This has previously been shown e.g. in (Predict then Propagate: Graph Neural Networks meet Personalized PageRank)[https://arxiv.org/abs/1810.05997] and (Pitfalls of Graph Neural Network Evaluation)[https://arxiv.org/abs/1811.05868]. Evaluating GNNs can be tricky, so I warmly recommend reading either the first paper's experimental section or the second paper.
This is also the reason why you will find that none of the numbers reported in this paper are just copied from the original works. As we mention in our experimental section, we run all of these methods on a consistent setup, optimized all hyperparameters ourself, and use results averaged over 100 random splits and initializations.


python310Packages.hahomematic: 2022.12.0 -> 2022.12.1

Changelog: https://github.com/danielperna84/hahomematic/releases/tag/2022.12.1
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 204381 run on x86_64-linux 1

2 packages built:

python310Packages.hahomematic
python39Packages.hahomematic


Redesign profile page

Description

Waiting for updated Q1 designs

The updated version of the Profile page is here.
The dashboard is your profile page when connected.
The profile page is someone else profile page.
You can see your own profile page as the others see it if you log out.
MY DASHBOARD:

Cover image removed
Story cards updated

PROFILE PAGE:

Side Menu removed
New UI story cards
- The Subscribe CTA will have to be displayed when the subscribing mechanism will be done.

@QuentinSaubadu can this one be closed?


Update dependency symfony/string to v6.2.2

This PR contains the following updates:

Package
Type
Update
Change

symfony/string (source)
require
patch
6.2.0 -> 6.2.2

Release Notes

symfony/string
v6.2.2
Compare Source
Changelog (https://github.com/symfony/string/compare/v6.2.1...v6.2.2)

bug #48615 Fix getting the name of closures on PHP 8.1.11+ (nicolas-grekas)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: composer.lock
Command failed: docker run --rm --name=renovate_sidecar --label=renovate_child -v "/tmp/renovate/repos/github/renovate-reproductions/symfony-flex-backend":"/tmp/renovate/repos/github/renovate-reproductions/symfony-flex-backend" -v "/tmp/renovate/cache":"/tmp/renovate/cache" -v "/tmp/containerbase":"/tmp/containerbase" -e COMPOSER_CACHE_DIR -e COMPOSER_AUTH -e BUILDPACK_CACHE_DIR -e CONTAINERBASE_CACHE_DIR -w "/tmp/renovate/repos/github/renovate-reproductions/symfony-flex-backend" docker.io/renovate/sidecar bash -l -c "install-tool php 8.2.0 && install-tool composer 2.5.0 && git stash -- composer.json && composer install --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins && git stash pop && composer update symfony/string --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins"
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
fatal: detected dubious ownership in repository at '/tmp/renovate/repos/github/renovate-reproductions/symfony-flex-backend'
To add an exception for this directory, call:

	git config --global --add safe.directory /tmp/renovate/repos/github/renovate-reproductions/symfony-flex-backend


Add link to LUG in the top right corner

title

We should minimize the amount of links in the top nav. Perhaps we can add it to the footer nav?

We should minimize the amount of links in the top nav. Perhaps we can add it to the footer nav?

I would be the last person to know about design, Please ping me when a decision is made

Perhaps we can add another section of links in the footer for other orgs and uic links.
We can also include WiCS, LOGICA, etc.
Thoughts @clee231 ?

Perhaps we can add another section of links in the footer for other orgs and uic links.
We can also include WiCS, LOGICA, etc.
Thoughts @clee231 ?

I think that's a good idea. Let's do that.
If it seems too cluttered after adding another column, we may be able to re-organize the footer columns.

I can work on this. Should I keep working on this PR or make a new one?
On Sat, Oct 2, 2021 at 5:42 PM Chase 李 @.***> wrote:

Perhaps we can add another section of links in the footer for other orgs
and uic links.
We can also include WiCS, LOGICA, etc.
Thoughts @clee231 https://github.com/clee231 ?
I think that's a good idea. Let's do that.
If it seems too cluttered after adding another column, we may be able to
re-organize the footer columns.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/acm-uic/acm-uic.github.io/pull/87#issuecomment-932829656,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWJLTZWUES5VK4GVPY4OJDUE6DENANCNFSM5FGXTV7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Soham Gumaste
@.***

Closing in favour of #88


Installation failing in sandbox

I am trying to install this package in our sandbox org and getting compile failure issue. Attached screenshot of mail

Hi @ShijiMathew - that looks like an issue with an existing class in your org called getSetNumbersListener. By default, when installing packages in your org, Salesforce compiles all of the Apex in your org, and this existing issue in your org is blocking the package installation. You can either select the option (during installation) to only compile Apex in the package, or try to fix the errors in your Apex class.

Thankyou for your quick response @jongpie. Installation worked with compilation of apex in the package. This is a new class working by my colleague so I was not aware of it. I will close this issue.


Help with Firebeetle 2/Lora Cover and Bresser 7-in-1 Clearview

Hi there, I bought the Bresser ClearView station (https://www.bresser.de/en/Weather-Time/BRESSER-WIFI-ClearView-Weather-Station-with-7-in-1-Sensor.html) and had a Firebeetle 2 (not 1) lying around (https://www.dfrobot.com/product-2195.html) so I got the DFRobot 868 LoRa cover to go with it, only to realize it was designed for the first iteration of FireBeetle, not the second. I thought I could get it to work regardless but I'm stumped.
I used the same bridges on the LoRa cover, but had to use different pins on the FireBeetle itself, as D4 is actually used for the flash button. Instead I mapped D2, D3, D4 and D5 on the cover to A0, A1, A2, and A3 on the Beetle respectively using Dupont cables.
Using the MQTT custom example as a base, I chose BRESSER_7_IN_1, uncommented what's needed for the regular FireBeetle, and changed the pins to:
    #define PIN_RECEIVER_CS   34 // D4 -> A2

    // CC1101: GDO0 / RFM95W/SX127x: G0
    #define PIN_RECEIVER_IRQ  39 // D3 -> A1

    // CC1101: GDO2 / RFM95W/SX127x: G1
    #define PIN_RECEIVER_GPIO 35  // D5 -> A3

    // RFM95W/SX127x - GPIOxx / CC1101 - RADIOLIB_NC
    #define PIN_RECEIVER_RST  36 // D2 -> A0

SCK, MISO and MOSI are the same on both FireBeetle versions.
I can build and flash just fine, connect to Wifi and MQTT, but I don't see sensor data being picked up. The serial console only prints Checking wifi and MQTT connecting. Any idea what could be wrong?

Hi,
Yes, while selecting "FireBeetle-ESP32" sets the define ARDUINO_ESP32_DEV and we have to guess that this means FireBeetle, selecting "FireBeetle 2 ESP32-W" sets ARDUINO_DFROBOT_FIREBEETLE_2_ESP32E (which is actually meaningful).
This means that you can put your pin definitions in a block starting with
#elif defined(ARDUINO_DFROBOT_FIREBEETLE_2_ESP32E)
(ARDUINO_DFROBOT_FIREBEETLE_ESP32 might become available with arduino-esp32 release 3.x.)

If you enable "Verbose Output" in the Arduino IDE's Preferences, you can check in the compile output if the correct code section and your desired pins are actually applied.

Thanks, they are correctly applied, not sure what's going on. I verified the cover is working at least, I flashed OpenMQTTGateway onto it and it picks up my existing LoRa devices, however if I try to flash OpenMQTTGateway with FSK instead of LoRa it doesn't pick up the weather station. Maybe that's a config issue as far as OpenMQTTGateway is concerned though. Will keep trying stuff. How often is the weather station supposed to broadcast its data?

You can find this in the datasheet. 24 sec is the transmit interval of the weather sensors I'm familiar with.
If you share the compile log and config file, I might be able to help. I'd like to add your HW config to the list of supported devices.

The transmission interval can be found in the sensor's manual. The weather sensors I'm familiar with have an interval of 24 seconds.

Thanks for the quick replies.
Managed to get OpenMQTTGateway to work with FSK. While building the firmware I saw it mapped RF_RECEIVER_GPIO to DIO2 in the code, so I tried plugging DIO2 on one of the FireBeetle pins and voila, I finally received some data.
I didn't see you mention DIO2 in your readme, could that be specific to OpenMQTTGateway?
It seems OMG can handle the data out of the box so I'm probably gonna stick with it since I already have one instance for LoRa and it integrates nicely into home assistant. Unless there's something your work does better that I'm missing?
Here's what the messages look like in OMG:
{"model":"Bresser-7in1","id":43970,"temperature_C":9.6,"humidity":92,"wind_max_m_s":0,"wind_avg_m_s":0,"wind_dir_deg":312,"rain_mm":4.8,"light_klx":0,"light_lux":0,"uv":0,"battery_ok":1,"mic":"CRC","protocol":"Bresser Weather Center 7-in-1","rssi":-93,"duration":38706}

This is strange, because DIO2 is not readily available on a few boards.
If OMG works for you, then keep it. The core functionality seems to be the same. Differences might exist in rain/lightning data post processing and power management.
I'll try to build a configuration for your HW setup next week and ask you to test it.

Hi,
the cover cannot be stacked directly on top of the FireBeetle 2 board, right? That would pretty much prevent using this combination unless you already have the HW available.
I have added the pin configuration you proposed to https://github.com/matthias-bs/BresserWeatherSensorReceiver/tree/feat-firebeetle2. Could you please try it?
Thanks and regards,
Matthias

Closed due to inactivity.

Apologies, didn't see your previous message.
I since switched to a board l was already for LoRa though, which has been working fine for FSK. I returned the LoRa cover.


Flickering sky when running world from sdf file.

Environment

OS Version: 22.04
Binary gz-garden latest release

If this is a GUI or sensor rendering bug, describe your GPU and rendering system. Otherwise delete this section.

Rendering plugin: [ogre2].

[ ] Sensor rendering error.
[x] GUI rendering error.

Generally, mention all circumstances that might affect rendering capabilities:

[x] running on real hardware

Rendering system info:

On Linux, provide the outputs of the following commands:

          LANG=C lspci -nn | grep VGA
\00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:a7a0] (rev 04)

          echo "$DISPLAY"
":0"

          LANG=C glxinfo -B | grep -i '\(direct rendering\|opengl\|profile\)'
                 direct rendering: Yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (RPL-P)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.0.4-0ubuntu1~22.04.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.0.4-0ubuntu1~22.04.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

          ps aux | grep Xorg
fremark+  198327  0.0  0.0   9536  2516 pts/18   S+   10:32   0:00 grep --color=auto Xorg

          sudo env LANG=C X -version
[ogre2.log](https://github.com/gazebosim/gz-sim/files/13646343/ogre2.log)

X.Org X Server <IP_ADDRESS>
X Protocol Version 11, Revision 0
Current Operating System: Linux fremarkus-ThinkPad-X1-Carbon-Gen-11 6.1.0-1027-oem #27-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 15:08:14 UTC 2023 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1027-oem root=UUID=87416edc-a5f8-4f3a-9a10-55881d31e973 ro quiet splash vt.handoff=7
xorg-server 2:21.1.4-2ubuntu1.7~22.04.2 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.40.0

- [x] Please, attach the ogre.log or ogre2.log file from  `~/.gz/rendering` <!-- Choose the relevant version based on what you checked in the "Rendering plugin" question. -->

```
10:23:54: Creating resource group General
10:23:54: Creating resource group Internal
10:23:54: Creating resource group Autodetect
10:23:54: SceneManagerFactory for type 'DefaultSceneManager' registered.
10:23:54: Registering ResourceManager for type Material
10:23:54: Registering ResourceManager for type Mesh
10:23:54: Registering ResourceManager for type Mesh2
10:23:54: Registering ResourceManager for type OldSkeleton
10:23:54: MovableObjectFactory for type 'ParticleSystem' registered.
10:23:54: ArchiveFactory for archive type FileSystem registered.
10:23:54: ArchiveFactory for archive type Zip registered.
10:23:54: ArchiveFactory for archive type EmbeddedZip registered.
10:23:54: DDS codec registering
10:23:54: FreeImage version: 3.18.0
10:23:54: This program uses FreeImage, a free, open source image library supporting all common bitmap formats. See http://freeimage.sourceforge.net for details
10:23:54: Supported formats: bmp,ico,jpg,jif,jpeg,jpe,jng,koa,iff,lbm,mng,pbm,pbm,pcd,pcx,pgm,pgm,png,ppm,ppm,ras,tga,targa,tif,tiff,wap,wbmp,wbm,psd,psb,cut,xbm,xpm,gif,hdr,g3,sgi,rgb,rgba,bw,exr,j2k,j2c,jp2,pfm,pct,pict,pic,3fr,arw,bay,bmq,cap,cine,cr2,crw,cs1,dc2,dcr,drf,dsc,dng,erf,fff,ia,iiq,k25,kc2,kdc,mdc,mef,mos,mrw,nef,nrw,orf,pef,ptx,pxn,qtk,raf,raw,rdc,rw2,rwl,rwz,sr2,srf,srw,sti,x3f,webp,jxr,wdp,hdp
10:23:54: ETC codec registering
10:23:54: OITD codec registering
10:23:54: Registering ResourceManager for type HighLevelGpuProgram
10:23:54: MovableObjectFactory for type 'Decal' registered.
10:23:54: MovableObjectFactory for type 'InternalCubemapProbe' registered.
10:23:54: MovableObjectFactory for type 'Entity' registered.
10:23:54: MovableObjectFactory for type 'Item' registered.
10:23:54: MovableObjectFactory for type 'Light' registered.
10:23:54: MovableObjectFactory for type 'Rectangle2Dv2' registered.
10:23:54: MovableObjectFactory for type 'BillboardSet' registered.
10:23:54: MovableObjectFactory for type 'ManualObject2' registered.
10:23:54: MovableObjectFactory for type 'BillboardChain' registered.
10:23:54: MovableObjectFactory for type 'RibbonTrail' registered.
10:23:54: MovableObjectFactory for type 'WireAabb' registered.
10:23:54: *-*-* OGRE Initialising
10:23:54: *-*-* Version 2.3.1 (Daedalus)
10:23:54: OverlayElementFactory for type Panel registered.
10:23:54: OverlayElementFactory for type BorderPanel registered.
10:23:54: OverlayElementFactory for type TextArea registered.
10:23:54: Registering ResourceManager for type Font
10:23:54: Loading library /usr/lib/x86_64-linux-gnu/OGRE-2.3/OGRE/RenderSystem_GL3Plus.so
10:23:54: Installing plugin: GL 3+ RenderSystem
10:23:54: OpenGL 3+ Rendering Subsystem created.
10:23:54: Found Num EGL Devices: 2
10:23:54: EGL Device: EGL_EXT_device_drm EGL_EXT_device_drm_render_node #0 /dev/dri/card0
10:23:54: Trying to init device: EGL_EXT_device_drm EGL_EXT_device_drm_render_node #0 /dev/dri/card0...
10:23:54: Created GL 4.5 context for device EGL_EXT_device_drm EGL_EXT_device_drm_render_node #0 /dev/dri/card0
10:23:54: Destroying device: EGL_EXT_device_drm EGL_EXT_device_drm_render_node #0 /dev/dri/card0...
10:23:54: EGL Device: EGL_MESA_device_software EGL_EXT_device_drm_render_node #1
10:23:54: Trying to init device: EGL_MESA_device_software EGL_EXT_device_drm_render_node #1...
10:23:54: Created GL 4.5 context for device EGL_MESA_device_software EGL_EXT_device_drm_render_node #1
10:23:54: Destroying device: EGL_MESA_device_software EGL_EXT_device_drm_render_node #1...
10:23:54: Plugin successfully installed
10:23:54: Loading library /usr/lib/x86_64-linux-gnu/OGRE-2.3/OGRE/Plugin_ParticleFX.so
10:23:54: Installing plugin: ParticleFX
10:23:54: Particle Emitter Type 'Point' registered
10:23:54: Particle Emitter Type 'Box' registered
10:23:54: Particle Emitter Type 'Ellipsoid' registered
10:23:54: Particle Emitter Type 'Cylinder' registered
10:23:54: Particle Emitter Type 'Ring' registered
10:23:54: Particle Emitter Type 'HollowEllipsoid' registered
10:23:54: Particle Affector Type 'LinearForce' registered
10:23:54: Particle Affector Type 'ColourFader' registered
10:23:54: Particle Affector Type 'ColourFader2' registered
10:23:54: Particle Affector Type 'ColourImage' registered
10:23:54: Particle Affector Type 'ColourInterpolator' registered
10:23:54: Particle Affector Type 'Scaler' registered
10:23:54: Particle Affector Type 'Rotator' registered
10:23:54: Particle Affector Type 'DirectionRandomiser' registered
10:23:54: Particle Affector Type 'DeflectorPlane' registered
10:23:54: Plugin successfully installed
10:23:54: CPU Identifier & Features
10:23:54: -------------------------
10:23:54:  *   CPU ID: GenuineIntel: 13th Gen Intel(R) Core(TM) i7-1370P
10:23:54:  *   Logical cores: 20
10:23:54:  *      SSE: yes
10:23:54:  *     SSE2: yes
10:23:54:  *     SSE3: yes
10:23:54:  *      MMX: yes
10:23:54:  *   MMXEXT: yes
10:23:54:  *    3DNOW: no
10:23:54:  * 3DNOWEXT: no
10:23:54:  *     CMOV: yes
10:23:54:  *      TSC: yes
10:23:54:  *      FPU: yes
10:23:54:  *      PRO: yes
10:23:54:  *       HT: no
10:23:54: -------------------------
10:23:54: ******************************
*** Starting GLX Subsystem ***
******************************
10:23:54: GL3PlusRenderSystem::_createRenderWindow "OgreWindow(0)_0", 1x1 windowed  miscParams: FSAA=0 border=none contentScalingFactor=1,000000 currentGLContext=true externalGLControl=true gamma=Yes parentWindowHandle=69206042 stereoMode=Frame Sequential
10:23:54: GLXWindow::create used FBConfigID = 485
10:23:54: GL Version = <IP_ADDRESS>
10:23:54: GL_VERSION = 4.6 (Compatibility Profile) Mesa 23.0.4-0ubuntu1~22.04.1
10:23:54: GL_VENDOR = Intel
10:23:54: GL_RENDERER = Mesa Intel(R) Graphics (RPL-P)
10:23:54: GL_EXTENSIONS =
10:23:54: GL_3DFX_texture_compression_FXT1
10:23:54: GL_AMD_conservative_depth
10:23:54: GL_AMD_depth_clamp_separate
10:23:54: GL_AMD_draw_buffers_blend
10:23:54: GL_AMD_multi_draw_indirect
10:23:54: GL_AMD_performance_monitor
10:23:54: GL_AMD_pinned_memory
10:23:54: GL_AMD_query_buffer_object
10:23:54: GL_AMD_seamless_cubemap_per_texture
10:23:54: GL_AMD_shader_stencil_export
10:23:54: GL_AMD_shader_trinary_minmax
10:23:54: GL_AMD_texture_texture4
10:23:54: GL_AMD_vertex_shader_layer
10:23:54: GL_AMD_vertex_shader_viewport_index
10:23:54: GL_ANGLE_texture_compression_dxt3
10:23:54: GL_ANGLE_texture_compression_dxt5
10:23:54: GL_APPLE_packed_pixels
10:23:54: GL_ARB_ES2_compatibility
10:23:54: GL_ARB_ES3_1_compatibility
10:23:54: GL_ARB_ES3_2_compatibility
10:23:54: GL_ARB_ES3_compatibility
10:23:54: GL_ARB_arrays_of_arrays
10:23:54: GL_ARB_base_instance
10:23:54: GL_ARB_blend_func_extended
10:23:54: GL_ARB_buffer_storage
10:23:54: GL_ARB_clear_buffer_object
10:23:54: GL_ARB_clear_texture
10:23:54: GL_ARB_clip_control
10:23:54: GL_ARB_color_buffer_float
10:23:54: GL_ARB_compatibility
10:23:54: GL_ARB_compressed_texture_pixel_storage
10:23:54: GL_ARB_compute_shader
10:23:54: GL_ARB_compute_variable_group_size
10:23:54: GL_ARB_conditional_render_inverted
10:23:54: GL_ARB_conservative_depth
10:23:54: GL_ARB_copy_buffer
10:23:54: GL_ARB_copy_image
10:23:54: GL_ARB_cull_distance
10:23:54: GL_ARB_debug_output
10:23:54: GL_ARB_depth_buffer_float
10:23:54: GL_ARB_depth_clamp
10:23:54: GL_ARB_depth_texture
10:23:54: GL_ARB_derivative_control
10:23:54: GL_ARB_direct_state_access
10:23:54: GL_ARB_draw_buffers
10:23:54: GL_ARB_draw_buffers_blend
10:23:54: GL_ARB_draw_elements_base_vertex
10:23:54: GL_ARB_draw_indirect
10:23:54: GL_ARB_draw_instanced
10:23:54: GL_ARB_enhanced_layouts
10:23:54: GL_ARB_explicit_attrib_location
10:23:54: GL_ARB_explicit_uniform_location
10:23:54: GL_ARB_fragment_coord_conventions
10:23:54: GL_ARB_fragment_layer_viewport
10:23:54: GL_ARB_fragment_program
10:23:54: GL_ARB_fragment_program_shadow
10:23:54: GL_ARB_fragment_shader
10:23:54: GL_ARB_fragment_shader_interlock
10:23:54: GL_ARB_framebuffer_no_attachments
10:23:54: GL_ARB_framebuffer_object
10:23:54: GL_ARB_framebuffer_sRGB
10:23:54: GL_ARB_get_program_binary
10:23:54: GL_ARB_get_texture_sub_image
10:23:54: GL_ARB_gl_spirv
10:23:54: GL_ARB_gpu_shader5
10:23:54: GL_ARB_gpu_shader_fp64
10:23:54: GL_ARB_gpu_shader_int64
10:23:54: GL_ARB_half_float_pixel
10:23:54: GL_ARB_half_float_vertex
10:23:54: GL_ARB_indirect_parameters
10:23:54: GL_ARB_instanced_arrays
10:23:54: GL_ARB_internalformat_query
10:23:54: GL_ARB_internalformat_query2
10:23:54: GL_ARB_invalidate_subdata
10:23:54: GL_ARB_map_buffer_alignment
10:23:54: GL_ARB_map_buffer_range
10:23:54: GL_ARB_multi_bind
10:23:54: GL_ARB_multi_draw_indirect
10:23:54: GL_ARB_multisample
10:23:54: GL_ARB_multitexture
10:23:54: GL_ARB_occlusion_query
10:23:54: GL_ARB_occlusion_query2
10:23:54: GL_ARB_parallel_shader_compile
10:23:54: GL_ARB_pipeline_statistics_query
10:23:54: GL_ARB_pixel_buffer_object
10:23:54: GL_ARB_point_parameters
10:23:54: GL_ARB_point_sprite
10:23:54: GL_ARB_polygon_offset_clamp
10:23:54: GL_ARB_post_depth_coverage
10:23:54: GL_ARB_program_interface_query
10:23:54: GL_ARB_provoking_vertex
10:23:54: GL_ARB_query_buffer_object
10:23:54: GL_ARB_robust_buffer_access_behavior
10:23:54: GL_ARB_robustness
10:23:54: GL_ARB_sample_shading
10:23:54: GL_ARB_sampler_objects
10:23:54: GL_ARB_seamless_cube_map
10:23:54: GL_ARB_seamless_cubemap_per_texture
10:23:54: GL_ARB_separate_shader_objects
10:23:54: GL_ARB_shader_atomic_counter_ops
10:23:54: GL_ARB_shader_atomic_counters
10:23:54: GL_ARB_shader_ballot
10:23:54: GL_ARB_shader_bit_encoding
10:23:54: GL_ARB_shader_clock
10:23:54: GL_ARB_shader_draw_parameters
10:23:54: GL_ARB_shader_group_vote
10:23:54: GL_ARB_shader_image_load_store
10:23:54: GL_ARB_shader_image_size
10:23:54: GL_ARB_shader_objects
10:23:54: GL_ARB_shader_precision
10:23:54: GL_ARB_shader_stencil_export
10:23:54: GL_ARB_shader_storage_buffer_object
10:23:54: GL_ARB_shader_subroutine
10:23:54: GL_ARB_shader_texture_image_samples
10:23:54: GL_ARB_shader_texture_lod
10:23:54: GL_ARB_shader_viewport_layer_array
10:23:54: GL_ARB_shading_language_100
10:23:54: GL_ARB_shading_language_420pack
10:23:54: GL_ARB_shading_language_include
10:23:54: GL_ARB_shading_language_packing
10:23:54: GL_ARB_shadow
10:23:54: GL_ARB_spirv_extensions
10:23:54: GL_ARB_stencil_texturing
10:23:54: GL_ARB_sync
10:23:54: GL_ARB_tessellation_shader
10:23:54: GL_ARB_texture_barrier
10:23:54: GL_ARB_texture_border_clamp
10:23:54: GL_ARB_texture_buffer_object
10:23:54: GL_ARB_texture_buffer_object_rgb32
10:23:54: GL_ARB_texture_buffer_range
10:23:54: GL_ARB_texture_compression
10:23:54: GL_ARB_texture_compression_bptc
10:23:54: GL_ARB_texture_compression_rgtc
10:23:54: GL_ARB_texture_cube_map
10:23:54: GL_ARB_texture_cube_map_array
10:23:54: GL_ARB_texture_env_add
10:23:54: GL_ARB_texture_env_combine
10:23:54: GL_ARB_texture_env_crossbar
10:23:54: GL_ARB_texture_env_dot3
10:23:54: GL_ARB_texture_filter_anisotropic
10:23:54: GL_ARB_texture_float
10:23:54: GL_ARB_texture_gather
10:23:54: GL_ARB_texture_mirror_clamp_to_edge
10:23:54: GL_ARB_texture_mirrored_repeat
10:23:54: GL_ARB_texture_multisample
10:23:54: GL_ARB_texture_non_power_of_two
10:23:54: GL_ARB_texture_query_levels
10:23:54: GL_ARB_texture_query_lod
10:23:54: GL_ARB_texture_rectangle
10:23:54: GL_ARB_texture_rg
10:23:54: GL_ARB_texture_rgb10_a2ui
10:23:54: GL_ARB_texture_stencil8
10:23:54: GL_ARB_texture_storage
10:23:54: GL_ARB_texture_storage_multisample
10:23:54: GL_ARB_texture_swizzle
10:23:54: GL_ARB_texture_view
10:23:54: GL_ARB_timer_query
10:23:54: GL_ARB_transform_feedback2
10:23:54: GL_ARB_transform_feedback3
10:23:54: GL_ARB_transform_feedback_instanced
10:23:54: GL_ARB_transform_feedback_overflow_query
10:23:54: GL_ARB_transpose_matrix
10:23:54: GL_ARB_uniform_buffer_object
10:23:54: GL_ARB_vertex_array_bgra
10:23:54: GL_ARB_vertex_array_object
10:23:54: GL_ARB_vertex_attrib_64bit
10:23:54: GL_ARB_vertex_attrib_binding
10:23:54: GL_ARB_vertex_buffer_object
10:23:54: GL_ARB_vertex_program
10:23:54: GL_ARB_vertex_shader
10:23:54: GL_ARB_vertex_type_10f_11f_11f_rev
10:23:54: GL_ARB_vertex_type_2_10_10_10_rev
10:23:54: GL_ARB_viewport_array
10:23:54: GL_ARB_window_pos
10:23:54: GL_ATI_blend_equation_separate
10:23:54: GL_ATI_draw_buffers
10:23:54: GL_ATI_fragment_shader
10:23:54: GL_ATI_separate_stencil
10:23:54: GL_ATI_texture_compression_3dc
10:23:54: GL_ATI_texture_env_combine3
10:23:54: GL_ATI_texture_float
10:23:54: GL_EXT_EGL_image_storage
10:23:54: GL_EXT_EGL_sync
10:23:54: GL_EXT_abgr
10:23:54: GL_EXT_bgra
10:23:54: GL_EXT_blend_color
10:23:54: GL_EXT_blend_equation_separate
10:23:54: GL_EXT_blend_func_separate
10:23:54: GL_EXT_blend_minmax
10:23:54: GL_EXT_blend_subtract
10:23:54: GL_EXT_compiled_vertex_array
10:23:54: GL_EXT_copy_texture
10:23:54: GL_EXT_debug_label
10:23:54: GL_EXT_demote_to_helper_invocation
10:23:54: GL_EXT_depth_bounds_test
10:23:54: GL_EXT_direct_state_access
10:23:54: GL_EXT_draw_buffers2
10:23:54: GL_EXT_draw_instanced
10:23:54: GL_EXT_draw_range_elements
10:23:54: GL_EXT_fog_coord
10:23:54: GL_EXT_framebuffer_blit
10:23:54: GL_EXT_framebuffer_multisample
10:23:54: GL_EXT_framebuffer_multisample_blit_scaled
10:23:54: GL_EXT_framebuffer_object
10:23:54: GL_EXT_framebuffer_sRGB
10:23:54: GL_EXT_gpu_program_parameters
10:23:54: GL_EXT_gpu_shader4
10:23:54: GL_EXT_memory_object
10:23:54: GL_EXT_memory_object_fd
10:23:54: GL_EXT_multi_draw_arrays
10:23:54: GL_EXT_packed_depth_stencil
10:23:54: GL_EXT_packed_float
10:23:54: GL_EXT_packed_pixels
10:23:54: GL_EXT_pixel_buffer_object
10:23:54: GL_EXT_point_parameters
10:23:54: GL_EXT_polygon_offset_clamp
10:23:54: GL_EXT_provoking_vertex
10:23:54: GL_EXT_rescale_normal
10:23:54: GL_EXT_secondary_color
10:23:54: GL_EXT_semaphore
10:23:54: GL_EXT_semaphore_fd
10:23:54: GL_EXT_separate_specular_color
10:23:54: GL_EXT_shader_framebuffer_fetch
10:23:54: GL_EXT_shader_framebuffer_fetch_non_coherent
10:23:54: GL_EXT_shader_integer_mix
10:23:54: GL_EXT_shader_samples_identical
10:23:54: GL_EXT_shadow_funcs
10:23:54: GL_EXT_stencil_two_side
10:23:54: GL_EXT_stencil_wrap
10:23:54: GL_EXT_subtexture
10:23:54: GL_EXT_texture
10:23:54: GL_EXT_texture3D
10:23:54: GL_EXT_texture_array
10:23:54: GL_EXT_texture_buffer_object
10:23:54: GL_EXT_texture_compression_dxt1
10:23:54: GL_EXT_texture_compression_latc
10:23:54: GL_EXT_texture_compression_rgtc
10:23:54: GL_EXT_texture_compression_s3tc
10:23:54: GL_EXT_texture_cube_map
10:23:54: GL_EXT_texture_edge_clamp
10:23:54: GL_EXT_texture_env_add
10:23:54: GL_EXT_texture_env_combine
10:23:54: GL_EXT_texture_env_dot3
10:23:54: GL_EXT_texture_filter_anisotropic
10:23:54: GL_EXT_texture_integer
10:23:54: GL_EXT_texture_lod_bias
10:23:54: GL_EXT_texture_object
10:23:54: GL_EXT_texture_rectangle
10:23:54: GL_EXT_texture_sRGB
10:23:54: GL_EXT_texture_sRGB_R8
10:23:54: GL_EXT_texture_sRGB_decode
10:23:54: GL_EXT_texture_shadow_lod
10:23:54: GL_EXT_texture_shared_exponent
10:23:54: GL_EXT_texture_snorm
10:23:54: GL_EXT_texture_swizzle
10:23:54: GL_EXT_timer_query
10:23:54: GL_EXT_transform_feedback
10:23:54: GL_EXT_vertex_array
10:23:54: GL_EXT_vertex_array_bgra
10:23:54: GL_EXT_vertex_attrib_64bit
10:23:54: GL_IBM_multimode_draw_arrays
10:23:54: GL_IBM_rasterpos_clip
10:23:54: GL_IBM_texture_mirrored_repeat
10:23:54: GL_INGR_blend_func_separate
10:23:54: GL_INTEL_blackhole_render
10:23:54: GL_INTEL_performance_query
10:23:54: GL_INTEL_shader_atomic_float_minmax
10:23:54: GL_INTEL_shader_integer_functions2
10:23:54: GL_KHR_blend_equation_advanced
10:23:54: GL_KHR_blend_equation_advanced_coherent
10:23:54: GL_KHR_context_flush_control
10:23:54: GL_KHR_debug
10:23:54: GL_KHR_no_error
10:23:54: GL_KHR_parallel_shader_compile
10:23:54: GL_KHR_robust_buffer_access_behavior
10:23:54: GL_KHR_robustness
10:23:54: GL_KHR_texture_compression_astc_ldr
10:23:54: GL_KHR_texture_compression_astc_sliced_3d
10:23:54: GL_MESA_framebuffer_flip_y
10:23:54: GL_MESA_pack_invert
10:23:54: GL_MESA_shader_integer_functions
10:23:54: GL_MESA_texture_signed_rgba
10:23:54: GL_MESA_window_pos
10:23:54: GL_NV_ES1_1_compatibility
10:23:54: GL_NV_alpha_to_coverage_dither_control
10:23:54: GL_NV_blend_square
10:23:54: GL_NV_compute_shader_derivatives
10:23:54: GL_NV_conditional_render
10:23:54: GL_NV_copy_image
10:23:54: GL_NV_depth_clamp
10:23:54: GL_NV_fog_distance
10:23:54: GL_NV_fragment_shader_interlock
10:23:54: GL_NV_half_float
10:23:54: GL_NV_light_max_exponent
10:23:54: GL_NV_packed_depth_stencil
10:23:54: GL_NV_primitive_restart
10:23:54: GL_NV_texgen_reflection
10:23:54: GL_NV_texture_barrier
10:23:54: GL_NV_texture_env_combine4
10:23:54: GL_NV_texture_rectangle
10:23:54: GL_OES_EGL_image
10:23:54: GL_OES_read_format
10:23:54: GL_S3_s3tc
10:23:54: GL_SGIS_generate_mipmap
10:23:54: GL_SGIS_texture_border_clamp
10:23:54: GL_SGIS_texture_edge_clamp
10:23:54: GL_SGIS_texture_lod
10:23:54: GL_SUN_multi_draw_arrays
10:23:54: **************************************
10:23:54: ***   OpenGL 3+ Renderer Started   ***
10:23:54: **************************************
10:23:54: Registering ResourceManager for type GpuProgram
10:23:54: RenderSystem capabilities
10:23:54: -------------------------
10:23:54: RenderSystem Name: OpenGL 3+ Rendering Subsystem
10:23:54: GPU Vendor: intel
10:23:54: Device Name: Mesa Intel(R) Graphics (RPL-P)
10:23:54: Driver Version: <IP_ADDRESS>
10:23:54:  * Fixed function pipeline: no
10:23:54:  * Hardware generation of mipmaps: no
10:23:54:  * Texture blending: yes
10:23:54:  * Anisotropic texture filtering: yes
10:23:54:  * Dot product texture operation: yes
10:23:54:  * Cube mapping: yes
10:23:54:  * Hardware stencil buffer: yes
10:23:54:    - Stencil depth: 8
10:23:54:    - Two sided stencil support: yes
10:23:54:    - Wrap stencil values: yes
10:23:54:  * Hardware vertex / index buffers: yes
10:23:54:  * 32-bit index buffers: yes
10:23:54:  * Vertex programs: yes
10:23:54:  * Number of floating-point constants for vertex programs: 16384
10:23:54:  * Number of integer constants for vertex programs: 16384
10:23:54:  * Number of boolean constants for vertex programs: 16384
10:23:54:  * Fragment programs: yes
10:23:54:  * Number of floating-point constants for fragment programs: 16384
10:23:54:  * Number of integer constants for fragment programs: 16384
10:23:54:  * Number of boolean constants for fragment programs: 16384
10:23:54:  * Geometry programs: yes
10:23:54:  * Number of floating-point constants for geometry programs: 16384
10:23:54:  * Number of integer constants for geometry programs: 16384
10:23:54:  * Number of boolean constants for geometry programs: 16384
10:23:54:  * Tessellation Hull programs: yes
10:23:54:  * Number of floating-point constants for tessellation hull programs: 16384
10:23:54:  * Number of integer constants for tessellation hull programs: 16384
10:23:54:  * Number of boolean constants for tessellation hull programs: 16384
10:23:54:  * Tessellation Domain programs: yes
10:23:54:  * Number of floating-point constants for tessellation domain programs: 16384
10:23:54:  * Number of integer constants for tessellation domain programs: 16384
10:23:54:  * Number of boolean constants for tessellation domain programs: 16384
10:23:54:  * Compute programs: yes
10:23:54:  * Number of floating-point constants for compute programs: 16384
10:23:54:  * Number of integer constants for compute programs: 16384
10:23:54:  * Number of boolean constants for compute programs: 16384
10:23:54:  * Supported Shader Profiles: glsl glsl130 glsl140 glsl150 glsl330 glsl400 glsl410 glsl420 glsl430 glsl440
10:23:54:  * Texture Compression: yes
10:23:54:    - DXT: yes
10:23:54:    - VTC: no
10:23:54:    - PVRTC: no
10:23:54:    - ATC: no
10:23:54:    - ETC1: no
10:23:54:    - ETC2: yes
10:23:54:    - BC4/BC5: yes
10:23:54:    - BC6H/BC7: yes
10:23:54:    - ASTC: yes
10:23:54:  * Hardware Occlusion Query: yes
10:23:54:  * User clip planes: yes
10:23:54:  * VET_UBYTE4 vertex element type: yes
10:23:54:  * Infinite far plane projection: yes
10:23:54:  * Hardware render-to-texture: yes
10:23:54:  * Floating point textures: yes
10:23:54:  * Non-power-of-two textures: yes
10:23:54:  * 1d textures: yes
10:23:54:  * Volume textures: yes
10:23:54:  * Max Texture resolution (2D) 16384
10:23:54:  * Max Texture resolution (3D) 2048
10:23:54:  * Max Texture resolution (Cubemaps) 16384
10:23:54:  * Multiple Render Targets: 8
10:23:54:    - With different bit depths: yes
10:23:54:  * Point Sprites: yes
10:23:54:  * Extended point parameters: yes
10:23:54:  * Max Point Size: 255
10:23:54:  * Vertex texture fetch: yes
10:23:54:  * Number of world matrices: 0
10:23:54:  * Number of texture units: 16
10:23:54:  * Stencil buffer depth: 8
10:23:54:  * Number of vertex blend matrices: 0
10:23:54:    - Max vertex textures: 32
10:23:54:    - Vertex textures shared: yes
10:23:54:  * Render to Vertex Buffer : yes
10:23:54:  * Hardware Atomic Counters: yes
10:23:54:  * Compute max threads per threadgroup per axis: 1024, 1024, 64
10:23:54:  * Compute max threads per threadgroup total: 1024
10:23:54:  * GL 1.5 without VBO workaround: no
10:23:54:  * Frame Buffer objects: yes
10:23:54:  * Frame Buffer objects (ARB extension): no
10:23:54:  * Frame Buffer objects (ATI extension): no
10:23:54:  * PBuffer support: no
10:23:54:  * GL 1.5 without HW-occlusion workaround: no
10:23:54:  * Vertex Array Objects: yes
10:23:54:  * Separate shader objects: no
10:23:54:  * Using Reverse Z: yes
10:23:54: DefaultWorkQueue('Root') initialising on thread main.
10:23:54: Particle Renderer Type 'billboard' registered
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/ogre2/media/2.0/scripts/Compositors' of type 'FileSystem' to resource group 'General'
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/ogre2/media/2.0/scripts/materials/Common' of type 'FileSystem' to resource group 'General'
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/ogre2/media/2.0/scripts/materials/Common/GLSL' of type 'FileSystem' to resource group 'General'
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/ogre2/media/2.0/scripts/materials/Terra' of type 'FileSystem' to resource group 'General'
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/ogre2/media/2.0/scripts/materials/Terra/GLSL' of type 'FileSystem' to resource group 'General'
10:23:54: HLMS Library path '/usr/share/gz/gz-rendering7/ogre2/media/Hlms/Gz' has no piece files. Are you sure you provided the right path with read access?
10:23:54: HLMS Library path '/usr/share/gz/gz-rendering7/ogre2/media/Hlms/Gz' has no piece files. Are you sure you provided the right path with read access?
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/ogre2/media' of type 'FileSystem' to resource group 'General'
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/ogre2/media/materials/programs' of type 'FileSystem' to resource group 'General'
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/ogre2/media/materials/programs/GLSL' of type 'FileSystem' to resource group 'General'
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/ogre2/media/materials/programs/Metal' of type 'FileSystem' to resource group 'General'
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/ogre2/media/materials/scripts' of type 'FileSystem' to resource group 'General'
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/ogre2/media/materials/textures' of type 'FileSystem' to resource group 'General'
10:23:54: Parsing scripts for resource group Autodetect
10:23:54: Finished parsing scripts for resource group Autodetect
10:23:54: Creating resources for group Autodetect
10:23:54: All done
10:23:54: Parsing scripts for resource group General
10:23:54: Parsing script Quad.program
10:23:54: Parsing script picker.program
10:23:54: Parsing script Copyback.material
10:23:54: Parsing script EsmGaussianBlurLogFilter.material
10:23:54: Parsing script DepthUtils.material
10:23:54: Parsing script DPSM.material
10:23:54: Parsing script GpuNormalMapper.material
10:23:54: Parsing script depth_camera.material
10:23:54: Parsing script skybox.material
10:23:54: Parsing script picker.material
10:23:54: Parsing script thermal.material
10:23:54: Parsing script selection_buffer.material
10:23:54: Parsing script gaussian_noise.material
10:23:54: Parsing script gpu_rays.material
10:23:54: Parsing script point_cloud_point.material
10:23:54: Parsing script TerraShadowGenerator.compositor
10:23:54: Parsing script GpuNormalMapper.compositor
10:23:54: Parsing script GpuRays.compositor
10:23:54: Parsing script EsmGaussianBlurLogFilter.material.json
10:23:54: Parsing script Mipmaps.material.json
10:23:54: Parsing script TerraShadowGenerator.material.json
10:23:54: Finished parsing scripts for resource group General
10:23:54: Creating resources for group General
10:23:54: All done
10:23:54: Parsing scripts for resource group Internal
10:23:54: Finished parsing scripts for resource group Internal
10:23:54: Creating resources for group Internal
10:23:54: All done
10:23:54: Added resource location '/usr/share/gz/gz-rendering7/media/materials/textures/' of type 'FileSystem' to resource group 'General'
10:24:05: Added resource location '/home/fremarkus/.gz/fuel/fuel.gazebosim.org/openrobotics/models/baylands/3/media' of type 'FileSystem' to resource group 'General' with recursive option
10:24:05: Initialising resource group General
10:24:05: Added resource location '/home/fremarkus/.gz/fuel/fuel.gazebosim.org/openrobotics/models/baylands/3/media/Textures/' of type 'FileSystem' to resource group 'General'
10:24:05: Can't assign material scene::Material(65515) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:07: Can't assign material scene::Material(65509) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:09: Texture memory budget exceeded. Stalling GPU.
10:24:09: Stalling was not enough. Freeing memory.
10:24:09: Texture memory budget exceeded. Stalling GPU.
10:24:09: Stalling was not enough. Freeing memory.
10:24:09: Texture memory budget exceeded. Stalling GPU.
10:24:09: Stalling was not enough. Freeing memory.
10:24:09: Texture memory budget exceeded. Stalling GPU.
10:24:09: Stalling was not enough. Freeing memory.
10:24:09: Texture memory budget exceeded. Stalling GPU.
10:24:09: Stalling was not enough. Freeing memory.
10:24:09: Texture memory budget exceeded. Stalling GPU.
10:24:09: Stalling was not enough. Freeing memory.
10:24:10: Texture memory budget exceeded. Stalling GPU.
10:24:10: Stalling was not enough. Freeing memory.
10:24:10: Texture memory budget exceeded. Stalling GPU.
10:24:10: Stalling was not enough. Freeing memory.
10:24:10: Texture memory budget exceeded. Stalling GPU.
10:24:10: Stalling was not enough. Freeing memory.
10:24:10: Texture memory budget exceeded. Stalling GPU.
10:24:10: Stalling was not enough. Freeing memory.
10:24:10: Texture memory budget exceeded. Stalling GPU.
10:24:10: Stalling was not enough. Freeing memory.
10:24:10: Texture memory budget exceeded. Stalling GPU.
10:24:10: Stalling was not enough. Freeing memory.
10:24:10: Texture memory budget exceeded. Stalling GPU.
10:24:11: Can't assign material scene::Material(65503) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65502) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65501) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65500) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65499) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65498) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65497) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65496) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65495) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65494) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65493) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65492) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65491) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65490) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65489) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65488) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65487) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65486) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65485) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65484) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65483) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65482) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65481) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: Can't assign material scene::Material(65480) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:11: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material Default/TransGreen must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:11: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material Default/TransGreen must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:11: Couldn't apply datablock '[Hash 0x973c97a7]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:24:11: Vertex Shader: 100000001VertexShader_vs
Fragment Shader: 100000001PixelShader_ps
 GLSL validation result :
active samplers with a different type refer to the same texture image unit
10:24:11: Vertex Shader: 100000002VertexShader_vs
Fragment Shader: 100000002PixelShader_ps
 GLSL validation result :
active samplers with a different type refer to the same texture image unit
10:24:11: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:24:13: Can't assign material scene::Material(65427) because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:13: Vertex Shader: 100000005VertexShader_vs
Fragment Shader: 100000005PixelShader_ps
 GLSL validation result :
active samplers with a different type refer to the same texture image unit
10:24:16: Can't assign material [Default] because this Material does not exist. Have you forgotten to define it in a .material script?
10:24:16: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:16: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:16: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:24:16: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:16: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:16: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:24:16: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:24:16: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:24:16: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:24:18: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:18: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:18: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:24:18: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:18: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:18: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:24:18: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:24:18: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:24:20: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:20: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:20: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:24:20: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:20: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:20: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:24:20: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:24:20: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:24:22: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:22: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:22: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:24:22: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:22: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:24:22: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:24:22: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:24:22: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:27:05: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:05: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:05: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:27:05: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:05: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:05: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:27:05: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:27:05: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:27:06: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:06: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:06: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:27:06: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:06: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:06: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:27:06: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:27:06: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:27:28: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:28: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:28: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:27:28: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:28: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material highlight_material must use shaders in HlmsLowLevel::calculateHashFor at ./OgreMain/src/OgreHlmsLowLevel.cpp (line 160)
10:27:28: Couldn't apply datablock '[Hash 0xae9cf106]' to this renderable. Using default one. Check previous log messages to see if there's more information.
10:27:29: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
10:27:29: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
```

Description

Expected behavior: The sky has a flickering in it.
Actual behavior: The sky should not be flickering.

Steps to reproduce

Download the null island world from: https://app.gazebosim.org/OpenRobotics/fuel/worlds/Null Island
Start with gz sim -r  path/to/null/island.sdf

Output

picture of flickering...

@iche033 is this due to the non-NVIDIA GPU?

I do remember seeing flickering sky issue on user laptops before. It could be a gpu / driver issue.

Ok thanks. I will see if this error happens when i run it using a GPU.

Hi! I am coming here from a post I made on Gazebo Community.
This looks like the same problem I am facing. I wrote an SDF world with a sky and a directional light, and when I toggle the shadows the sky start flickering.
Here some information about my machine, as in the first post in this issue:
$ LANG=C lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-P GT1 [UHD Graphics] [8086:46a3] (rev 0c)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:28a0] (rev a1)

$ echo "$DISPLAY"
:0

$ LANG=C glxinfo -B | grep -i '\(direct rendering\|opengl\|profile\)'
direct rendering: Yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.0.4-0ubuntu1~22.04.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.0.4-0ubuntu1~22.04.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

$ ps aux | grep Xorg
biagio     26878  0.0  0.0   9212  2560 pts/6    R+   20:09   0:00 grep --color=auto Xorg

$ sudo env LANG=C X -version

X.Org X Server <IP_ADDRESS>
X Protocol Version 11, Revision 0
Current Operating System: Linux athena 6.2.0-39-generic #40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 16 10:53:04 UTC 2 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=bb022743-038b-409c-b381-21e78caa4017 ro quiet splash vt.handoff=7
xorg-server 2:21.1.4-2ubuntu1.7~22.04.5 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.40.0

Yes. So I was able to confirm that if I use a GPU then the flickering does not appear.

I wrote an SDF world with a sky and a directional light, and when I toggle the shadows the sky start flickering.

oh sounds like the shadows (or the light) is causing the sky to flicker? One workaround would be to disable shadows for the directional light.

Yes this worked! If I disable the shadows for my sun and enable them for the scene only, I can run the sky.

@iche033 Is having both sets of shadows enabled still a bug?

Is having both sets of shadows enabled still a bug?

I haven't seen any movement on this so I assume it's still an issue.

Hi all,
I am running into the same issue.
With shadows:

Without shadows, it is much better. However, still some flickering occurs:

I am also running it on a laptop without GPU:
$ LANG=C glxinfo -B | grep -i '\(direct rendering\|opengl\|profile\)'
direct rendering: Yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.0.4-0ubuntu1~22.04.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.0.4-0ubuntu1~22.04.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

I see this issue running on multiple computers with an Nvidia GPU. Disabling cast shadows from the sun also fixes the issue for me.


add support of function-style clientConfig

Hello.
This is very important feature in case if you want to wrap apollo configuration in custom module and pass logic to retrieve auth token and connection URL dynamically. Otherwise it's impossible to pass dynamic parameters using closure or nuxt modules to apollo config.

This is not working, I will think how to fix it if it possible. We found workaround instead of this.


Publish GroovyDocs

I should find a place to publish the GroovyDocs for the Groovy client.
They are currently uploaded with each release (feel free to download the groovydoc jar and extract its contents), but not automatically added to any site.

docs are also here: https://github.com/elastic/elasticsearch-groovy/blob/master/docs/quickstart.asciidoc

Hello, as a "super confused" one, I could not figure it out.
I have compiled client for elasticsearch 5.2.2, but I get "unable to resolve class" when I follow directions of both outdated docs and elasticsearch's groovy api docs.
Could you please advise me the correct method to initialize client?


Fix: Add access token to sample code

Fix sample code to add access token.
I don't use Kotlin so it may contains mistakes for StreamFederatedPublicTimeline.kt

Hello @lamrongol Ghanks for your contribution! I guess you ran into an instance where the federated timeline feed required authentication? If yes, could you provide me the instance name? Thanks a lot.

I can test fhe Kotlin part, no worries.

Thanks for the details, will run some tests on my side today. Regarding the connection leakage error. We're already tracking this on this issue here: https://github.com/andregasser/bigbone/issues/123
Should you find more information on the root cause, please feel free to add your comment there. Thank you very much.

Just run a gradlew check to make sure you meet syntax requirements 🙂

I committed the correction just before your comment and now "All checks have passed".


PUPIL-585 Feat/pupil journey list item

How to review this PR
Leave this text block for the reviewer

Check component hierarchy is followed correctly
Check the design Heuristics have been followed
Check naming conventions have been applied
Check for these gotchyas:

Missing exports for Oak components
Accidental export of Internal components
Snapshots of unexpected components have been modified
Circular dependencies
Code duplication (via not using base components)
Non-functional storybook for this or related components
Sensitve files changed eg. atoms, or style tokens
Relative imports
Default exports

Add your PR description below
This is the pupil journey list item to be used for lesson and unit listing pages
it has a disabled state when it is a div otherwise it is a a/button tag
Link to the design doc
https://www.figma.com/file/YcWQMMhHPVVmc47cHHEEAl/Oak-Design-Kit?type=design&node-id=8319%3A15791&mode=dev
A link to the component in the deployment preview
view component
Testing instructions
go to above storybook link; and test styles, content and break points for various use cases
ACs

@benprotheroe just want to check if the pink container is a part of each individual list item, or will the list items be wrapped in a container that will add the margins, border radius, colour token?

Aside from my question above, here is my feedback for this component:

For the mobile version, it looks like the number needs to be updated to use 'heading-5'
On mobile, can we use 'space-between-s' between the number/title and the link/icon? (looks a bit big when compared to the designs:

Issues found:

When the component is a button, there is a redundant href attribute.
There are no controls available in Storybook for this component, which makes it more difficult to test
Design issues (especially on mobile), as noted above by Mike.
The unavailable state has not been implemented, as noted by Mike.

@benprotheroe thanks for the updates, comments here:

I just saw the separate ticket for the OakListingPageLayout Component that's in progress, so that answers my question above, thanks.
The unavailable variant just needs bg-neutral to be applied to the background colour, and border-neutral-lighter applied to the border, and border-solid-m for the border width:

This may not be possible, but could we set a condition for when the title spans a new line so that the alignment is set to start for both mobile and desktop? Let me know if this wouldn't be possible to do. E.g:

Will the optional lesson variant and the lock-up be part of another ticket? E.g: https://www.figma.com/file/YcWQMMhHPVVmc47cHHEEAl/Oak-Design-Kit?type=design&node-id=8318%3A14897&mode=dev

@messmike just checking, the positioning of the lesson number since alignment was updated. It now shows as below (screenshot of mobile view):

Hey @RBrownsett, I had a chant with @benprotheroe yesterday where went back and forth on trying different alignments. I proposed setting a condition to align the number and title to start when the title spans multiple lines, but Ben wasn't sure it was possible without doing a nasty hack to achieve it. E.g:

We could change it to align at baseline, but I think when viewed in a list as they will appear in the product, it will look more balanced visually to keep it centre aligned. It does mean you get this for mobile with longer titles, but I think it will look better in more instances centre aligned. Unless we can extend the component in the future so it can behave as intended in the designs - which would be preferred.

A separate ticket has been added to extend the component that will support optional units: