Rebuild the autoconf files during CI testing

Although the autoconf related files don't change often, it's useful to
ensure they can be rebuilt.  This will help catch possible breakage and
make it easier for pull requests which modify src/configure.in to get
sanity tested.

James McCoy wrote:

Although the autoconf related files don't change often, it's useful to
ensure they can be rebuilt.  This will help catch possible breakage and
make it easier for pull requests which modify src/configure.in to get
sanity tested.

I'm not sure about this. Autoconf is known for an incompatible change
once in a while.  Since the generated configure script is in the
distribution this won't break building Vim.
Also, with this change the distributed configure script is not tested.
I prefer to have this test do the same as what Vim users do, thus use
the distributed configure script.
--
hundred-and-one symptoms of being an internet addict:
188. You purchase a laptop so you can surf while sitting on the can.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

On Thu, Dec 03, 2015 at 12:18:01PM -0800, Bram Moolenaar wrote:

James McCoy wrote:

Although the autoconf related files don't change often, it's useful to
ensure they can be rebuilt. This will help catch possible breakage and
make it easier for pull requests which modify src/configure.in to get
sanity tested.

I'm not sure about this. Autoconf is known for an incompatible change
once in a while.

Isn't that even more reason to have it automatically tested?

Since the generated configure script is in the
distribution this won't break building Vim.

Except when people need to patch configure.in, which then means they
have to rebuild configure.
If configure isn't being routinely rebuilt, then the user trying to
contribute their own patch touching configure.in may then have to figure
out why building configure is failing due to something they didn't
change.

Also, with this change the distributed configure script is not tested.

Fair point.  Rebuilding configure could be performed on just one axis of
the matrix of builds.
Cheers,
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy<EMAIL_ADDRESS>

I've updated the patch to only rebuild the autoconf files when performing the "all features enabled" build.  The small and tiny builds will use the configure script from the repo.

Updated to merge in the shadowdir testing.

IMHO configure should not be rebuilt systematically, not even "on
every Huge build". The distributed auto/configure should be good
enough for most users, and certainly for me who prefer not even to
modify the Makefile (I pass the configure arguments to make by means
of environment variables). If the build process could modify a file
which is under version control, that could give problems at the next
run of git or Mercurial, which would stop in error, telling you you
need to commit your changes before you may pull from the remote.
Best regards,
Tony.
On Sat, Dec 5, 2015 at 2:11 AM, James McCoy<EMAIL_ADDRESS>wrote:

I've updated the patch to only rebuild the autoconf files when performing
the "all features enabled" build. The small and tiny builds will use the
configure script from the repo.
—
Reply to this email directly or view it on GitHub.
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>For more options, visit https://groups.google.com/d/optout.

On Wed, Dec 30, 2015 at 10:42:52AM +0100, Tony Mechelynck wrote:

IMHO configure should not be rebuilt systematically, not even "on
every Huge build". The distributed auto/configure should be good
enough for most users, and certainly for me who prefer not even to
modify the Makefile (I pass the configure arguments to make by means
of environment variables).

I'm not suggesting it should be rebuilt as part of the normal build that
users perform.
I'm suggesting that the CI infrastructure rebuilds it for a couple
reasons.

Make it easier for pull requests which modify configure.in to be
verified.
Catch problems with newer autoconf versions automatically, as the CI
infrastructure updates.

These seem like reasonable things to have the CI doing.
Cheers,
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy<EMAIL_ADDRESS>

On Wed, Dec 30, 2015 at 1:08 PM, James McCoy<EMAIL_ADDRESS>wrote:

I'm not suggesting it should be rebuilt as part of the normal build that
users perform.
I'm suggesting that the CI infrastructure rebuilds it for a couple
reasons.

Make it easier for pull requests which modify configure.in to be
verified.
Catch problems with newer autoconf versions automatically, as the CI
infrastructure updates.

These seem like reasonable things to have the CI doing.
Cheers,

Er, sorry, I think I've hit a vocabulary problem. What do you mean by
CI? I tried to look it up on Wikipedia but even in the "Computing"
section of that homonymy page
https://en.wikipedia.org/wiki/CI#Computing there are various different
meanings listed, none of which seems to make obvious sense in the
present context.
Best regards,
Tony.


Generate documentation from comments in the values.yaml file.

Includes a very simple script that parses the values.yaml file and generates a markdown (GFM) table with keys that have been documented with a comment starting with the string #- (configurable).
I looked for other programs that could do this (yamldoc, Frigate, and Ruamel.yaml), but they are all sub-optimal for our use case.
Discussion Points

Do we want to proceed with this?
Does anyone care what string is used to introduce a documentation comment?

I don't think we need, or want to, document every value in the values.yaml file, but I think we do want to document Galaxy specific configuration values.
I have included a VALUES.md file to view the output of the script.  The markdown table could be pasted into the README, or the README could link to the VALUES.md file.

Hi @jacobtomlinson there were few things I was looking for in a documentation tool.

Being able to use a special marker like #- so only the documentation comments are included in the output.  This allows us to comment out sections or include comments, examples, etc. that aren't meant to be included as part of the documentation.
The documentation comments should be able to span multiple lines and come before the key they are documenting.
Only keys that have documentation comments should be included in the output.  There are only so many times we need to document that *Probe.enabled enables the [startup|readiness|liveness] probe.

I did the search several months ago, so I don't recall if all of those applied to Frigate, but I wasn't able to find anything that handled all of those cases.

Thanks @ksuderman that's really helpful. You're right that we don't support any of that today, I don't think 1 and 3 would be much of a lift at all. 2 is a little harder due to the way we use Ruamel.yaml but I'm keen to explore it.

I don't think any of the tools I looked at handled the second item, and I think that is a function of the way ruamel handles comments.  Keep us updated!


Use PHPUnit\Framework\TestCase instead of PHPUnit_Framework_TestCase

I use the PHPUnit\Framework\TestCase notation instead of PHPUnit_Framework_TestCase while extending our TestCases. This will help us migrate to PHPUnit 6, that no longer support snake case class names.
I just need to bump PHPUnit version to ^4.8.35 and ^5.7, that support this namespace.

According to https://github.com/reactphp/socket/issues/132 it should be 5.7.11 as min version.

@clue Done. Added PHPUnit 6 support :white_check_mark:

Rebased now that #244 is in :shipit:


Support passing JVM arguments to the AOT optimizer process

Feature description
See https://github.com/micronaut-projects/micronaut-maven-plugin/issues/795

This is indeed a mistake in the plugin, these methods should be public. This went unnoticed because they can be called from Groovy build scripts :facepalm:

Wow... Thanks for the quick fix. Now I'll just await the next release before I venture further with Loom.


Changing Jira Server docker compose configuration

Summary
The current Docker compose got stuck in my configuration (which might not be enough good reason to change this). I think this docker-compose is more complex because it also has an external database, but it's also more configurable with the $VERSION envvar.
The $JDK_VERSION has to be also configurable, since Jira 7 doesn't support openjdk-11, but openjdk-8.
Let me know what you think!
I'll be updating the plugin documentation too to explain how to use this.
Ticket Link

Thanks for looking into this @javaguirre! A couple things come to mind here:

I'm wondering what issues you run into with the existing docker setup, and why I don't run into the same issues 🤔

This was the bug I encounter.
The thing is I only used the automatic installation, didn't try to use the Manual installation mode because I didn't want to spend a lot of time on that, but maybe doing that would solve the problem

In this PR we're creating a new page in the docs related to development, though one already exists called environment.md. I suggest we merge the content between these and name the file development.md as you have here. We also need to update the link at the bottom of the README.

I didn't want this documentation to be more "important" in terms of hierarchy than others that are already there. Since it's also something optional that probably not many people need, I decided to create a page that has less importance.

We're renaming the compose file to docker-compose-jiraserver.yml which will make the docker-compose not work without specifying the name of this file. I suggest keeping the old name docker-compose.yml. Maybe move this file into a folder called dev, and create a make command in build/custom.mk like make run-jira to spin up the instance, and document the command.

I did that intentionally because IMHO this docker-compose is entirely optional and if I specify the name of the file with more "detail" I don't need to read the file to know if it's needed for me as a developer while working on the plugin. But I don't mind going back. :-)
I am ok doing the make command.

If we are going to make big changes like this to the docker environment, I suggest we also support "portable" installations, where I could have a Jira instance running, create a zip file from some folder(s) that are mapped as docker volumes, and give someone else the zip file so they can have an identical Jira setup. What do you think about this?

I think it's a good idea, although I'm starting to think that my changes here aren't really "useful" for many people, so maybe it's better if we close the PR and we reopen it if in the future someone has this problem? I think it could be a bit out of scope.
Also probably Atlassian might fix this in the future. I'm not sure if it's only something I'd use it doesn't make much sense to make the docker-compose build more complex. WDYT?

The thing is I only used the automatic installation, didn't try to use the Manual installation mode because I didn't want to spend a lot of time on that, but maybe doing that would solve the problem

Interesting, so the container started up fine but you ran into an issue during Jira setup? I too use the automatic setup. I was going to suggest trying to use platform: linux/amd64

I think it's a good idea, although I'm starting to think that my changes here aren't really "useful" for many people, so maybe it's better if we close the PR and we reopen it if in the future someone has this problem? I think it could be a bit out of scope.

Sure, closing the PR sounds find to me :+1:


ARCore 1.26.0, Filament 1.12.0 Update. Refactoring

Changed

Updated build.gradle parameters

compileSdkVersion 30 -> 31
targetSdkVersion 30 -> 31
sourceCompatibility VERSION_1_8 -> VERSION_11
targetCompatibility VERSION_1_8 -> VERSION_11

Updated dependencies

filament 1.10.7 -> 1.12.0
arcore 1.25.0 -> 1.26.0
appcompat 1.2.0 -> 1.3.1

Compiled filament materials for version 1.12.0
Refactored a few big functions and splitted them into smaller parts
Updated and tested all samples

Fixed

Fixed a few deprecation warnings
In CameraStream the function initializeTexture was called twice. This is now fixed

Added

Added in BaseArFragment a new function to close a session

public void closeSession() {
    if(arSceneView.getSession() != null)
        arSceneView.getSession().close();
        arSceneView.setSession(null);
    }
}

I find it a little bit difficult to profile and analyze the memory footprint of Sceneform on my laptop. The Laptop is not strong enough :).
Here is a visualization of a captured java/kotlin object allocation, when the gltf sample app was running.

As you can see the allocation rate rises continuously until the GC is cleaning unused objects. From the result I can't tell if the Trackable object allocation every frame has a huge impact. But the PlaneRenderer has still a huge impact.

Ok found the updateTrackable calls

looks not so bad, especially if you compare it with the PlaneRenderer

You are right, the updateTrackable doesn't consume so much but the problem was/is that it generates leaks since the created Trackable array elements are never cleaned and each call generates new ones. That made/makes a good part of the memory consumption increasing from what I think.
For the PlaneRender, we should check why normalToTangent is taking so much.

You are right, the updateTrackable doesn't consume so much but the problem was/is that it generates leaks since the created Trackable array elements are never cleaned and each call generates new ones. That made/makes a good part of the memory consumption increasing from what I think.
For the PlaneRender, we should check why normalToTangent is taking so much.

Maybe this is something for a separate Branch/PR?


Title color attribute doesn't change color

titleColor attribute doesn't work, rest attributes are working.

I don't have this issue. Are you able to provide some more details?


Sparkline - width cannot be adjusted + unexpected behavior when different X values

Screenshot

Description
Chart: Time-series Table
Type: Sparkline
Two issues:

Width of the Sparkline part cannot be adjusted. Seems to be permanently set to ~300px.
Series with different X values are not connected by line. Once filtered it acts as expected (second screen).

so please merge this and close this issue

Trying to spin up a test env on that PR to make sure it doesn't cause new problems. Most people won't like having to scroll to see an entire sparkling, so I just want to kick the tires before approving/merging.

I think I'd rather see a fix to make the width adjustable, rather than fixed. With a fixed width, there will be times it looks too narrow with a bunch of whitespace, or times where a chart in a dash is narrow and we have side-scrolling/cropping issues.


Add com.snowplowanalytics.snowplow.storage/observed_type/jsonschema/1-0-0

Ideas for better name will be highly appreciated.
Right now this is required for BigQuery loader, but idea of payload is very generic. Some Transformer-like application encounters new shredded type in a stream and sends a command with this payload to special topic, where another application can receive this command and perform corresponding ALTER TABLE statement on assigned storage.
Payload should be following:
{
  "schema": "com.snowplowanalytics.snowplow.storage/alter_table_command/jsonschema/1-0-0",
  "data": {
    "schema": "iglu:com.acme/new_event/jsonschema/1-2-3",
    "type": "DERIVED_CONTEXT"
  }
}

Interesting - the payload doesn't look much like a alter_table_command to me. The payload looks more like something like newly_observed_type. There's no command here like "mutate x to y".

Good point. But in fact there's actually nothing saying that is new. It is just a notion of snowplow self-describing entity.

Right now we used to call it "shredded type", but in fact it is something like self_describing_type

Right, I'd be leaning more towards something like:
{
  "schema": "com.snowplowanalytics.snowplow.storage/observed_type/jsonschema/1-0-0",
  "data": {
    "schema": "iglu:com.acme/new_event/jsonschema/1-2-3",
    "location": "DERIVED_CONTEXT"
  }
}

I was wondering if com.snowplowanalytics.snowplow.storage vendor and observed_type are overly specific. Because in fact there's nothing in payload saying that schema was observed and that it is going to be used for storage. It's simply a "shredded type", nothing more: schema and column in canonical enriched event. On the other hand, depending on what migration strategy will be chosen we might want to add here more specific information: e.g. window (when it was observed).

Agree, com.snowplowanalytics.snowplow and shredded_type are probably better...


Juneteenth Holiday Needed

I ran the latest version of holidays and see that there is no entry for Juneteenth, a new holiday starting in June 2021 in the United States.  Hopefully, you can add it soon.  Thanks

Hello @bhackett  I have submitted the PR #488 it should be fixed soon

Merged in beta.. thx!

Thank you.  It works great!
Brian
On Sun, Jul 18, 2021 at 4:00 AM Maurizio Montel @.***>
wrote:

Closed #482 https://github.com/dr-prodigy/python-holidays/issues/482.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dr-prodigy/python-holidays/issues/482#event-5034780638,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEAOQPLB6CWIADFUPQRMSDTYKCZZANCNFSM477QG6PQ
.


[DevCentral Migration] Archive this repo

To wrap up the migration and notify users of the change, this repo needs to be archived.
This should include updating the repo banner/headings with proper notifications and links to the new repo location

Since the repo was moved, there is no need to archive the original


Block Grids?

Hi Developers,
Do your have any plans to introduce block grids similar to Foundation ones in v4?

Duplicate of #18407. Please search next time!


added tests for widget functions

This adds some tests to hopefully ensure smooth usage and detecting issues early on.

Codecov Report

Merging #16 (7308d2a) into main (4342d9f) will increase coverage by 46.55%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##             main      #16       +/-   ##
===========================================
+ Coverage   33.33%   79.88%   +46.55%
===========================================
  Files           3        3
  Lines         147      174       +27
===========================================
+ Hits           49      139       +90
+ Misses         98       35       -63

Impacted Files
Coverage Δ

src/napari_vedo_bridge/_tests/test_widget.py
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add visible bonus icons to the total score for a player

The highest bonus is counted at full value.  Every icon after that add one to the score.
So, two 5 bonuses and a 2 bonus would be:
5 + 1 (for the extra 5) + 1 (the 2) = 7

It might also be nice to show the visible icons and their individual contribution.  Isotropic highlights the bonus that is full value and shows the rest of the visible bonuses in a slightly muted color to make it clear which ones have full value.  I don't know if we want to do that, but it is nice from a user's perspective to know the bonus contribution.
This feature is also needed for the cities expansion as well.

I was studying the code for the score update and it looks like the score is only written to the DB when a dogma during an action causes the score to be updated.  So other actions (like tucking or melding) will not result in the score being updated.
For the bonus icons, these can appear (and modify) the score during other types of actions that are not scoring directly.  So I think we will need to recalculate the score every time (or maybe the bonus contribution) when the board changes.
There are some weird cards (like Artificial Heart Age 10) that can temporarily modify the score during a dogma action as well.  I don't know how we would display that.  Maybe the score would go up during the dogma and then return to normal afterwards?

For Artificial Heart, I wouldn't bother changing the visible score. All that affects is the check for achievement eligibility.


Refresh Token option with .NET Core 2 Compatibility

How do i implement refresh token with  .NET Core 2 Compatibility?

I'd recommend OpenIddict for this. There is a refresh token flow sample you can look at. 👍


[Bug?] Profile API endpoint redirected to Twitter unless it's bot UA

When accessing the profile API endpoint (for example https://api.fxtwitter.com/TOBOOKS), only requests with bot UA will returns a JSON response, others will be redirected to Twitter instead. Is this a intended behaviour?

No, this is not intended behavior and likely broke recently due to an internal rewrite of our router. I'll investigate how this unintentionally broke.

Fixed


requires  "cartalyst/sentry": "~3.0",

when I use "composer update "
the error message is
- graham-campbell/credentials 0.4.x-dev requires cartalyst/sentry ~3.0 -> no
matching package found.
where can I find this package?
"cartalyst/sentry": "~3.0",
thanks

You need to add this to your composer.json:
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/BootstrapCMS/asset"
        },
        {
            "type": "vcs",
            "url": "https://github.com/BootstrapCMS/sentry"
        },
        {
            "type": "vcs",
            "url": "https://github.com/GrahamCampbell/framework"
        }
    ],


Failed to obtain package metadata: cargo metadata

When I run Anchor build I recive this error:
Failed to obtain package metadata: cargo metadata exited with an error: error: failed to load manifest for workspace member \\?\C:\Users\lucas\Desktop\gem-farm\programs\*
Caused by:
failed to read \\?\C:\Users\lucas\Desktop\gem-farm\programs\*\Cargo.toml
Caused by:
La sintassi del nome del file, della directory o del volume non è corretta. (os error 123)
How can I fix?

Are you used windows? try to use WSL
it's work for me

HEY,
Update your cargo.toml in main folder as:-
members = [
"programs/gem_bank",
"programs/gem_farm",
"lib/gem_common",
"lib/proc_macros",
]
to get more help join  my discord  THIRD EYE

@lucastoian did you ever get this fixed?

I have this issue when trying to use anchor build on Window 11. I solved it via installing WSL. https://ubuntu.com/tutorials/install-ubuntu-on-wsl2-on-windows-11-with-gui-support#1-overview
After installing, you can follow this tutorial to setup the Solana environment.
https://medium.com/@sncryldrm/setup-solana-development-environment-on-windows-cbed9e42ccef
Hope it helps!


internal: remove subcommand and re-structure codebase to enhance modularity and improve logging

This PR serves the following purposes:

Restructure codebase to enhance modularity.
Since binary is self-explanatory, getting rid of the subcommand as it is implicit.
Add proper logging for tracking steps and failures.
Fail in case of an error in place of continuing migration for the rest of the remaining PVCs.

Closes: https://github.com/ceph/persistent-volume-migrator/issues/14
Signed-off-by: Yug Gupta<EMAIL_ADDRESS>

Updated PR as per the suggestions. PTAL @travisn @leseb @Madhu-1 . Thanks!

Thanks for the reviews! Merging now :)


No alt text attribute?

Haven't tried this project out yet, but looking through the docs and the code I don't think I see an option to add alt text?

#29

@the8thbit From the docs:

All other props are passed through to the underlying img element after the image is loaded.


style scss syntax broken

How can I apply scss syntax in style tag with no attributes or only "scoped" attribute ?
(I use postcss.)
http://imgur.com/a/29kKp

You should be able to do something like:
<style nolang="scss">

It's not possible to do without attributes

Thank you for answering.
I tried your solution but
<style nolang="scss"> and <style lang="scss"> do not work, too.

My env is OS X, zsh, neovim.
the file extention is *.vue.

init.vim includes

autocmd BufRead,BufNewFile *.vue setlocal filetype=vue
autocmd FileType vue syntax sync fromstart

style code saved in test.vue file

<style nolang="scss">
.container {
  .main-title.active {
    color: #868AE5;
  }
  .divider {
    height: 1px;
    margin: 10px 0;
    border-top: 1px solid #eee;
    list-style: none;
    &:last-child {
      border-top: 0;
    }
  }
  .inputbox {
    color: #FF74F7;
  }
}
</style>

I plug-installed only this vim-vue for vuejs.

Here my new screenshot with your solution.
http://imgur.com/wFDs2RW

I have found &:last-child in .container .divider  has a problem while I'm writing this comment.
This is the screenshot $:last-child removed version.
http://imgur.com/TLPWRd3

and Is there any reason that nested classes has different color from parent class ?
As you can see the screenshot, parent class has green color and nested classes have white color.

I can reproduce that, even with lang="scss":

It looks like it doesn't use the scss highlighting at all, but just uses the highlighting from css.
I have noticed it before though, it just hasn't really bothered me enough. I will have a look at what is causing this soon. My initial guess is that css matches scss, but I'm not sure.

It's not because scss gets matched as css, since we don't have those rules set up. Vim-vue inherits the html syntax, which already provides css highlighting. So my initial guess wasn't right.
I use cakebaker/scss-syntax.vim for scss highlighting. I found out that when I remove the runtime! syntax/css.vim lines, the scss highlighting works perfectly fine in vue files, so it must have to do something with the css syntax file.

Thanks @adriaanzon !  I got to know why.
I use cakebaker/scss-syntax.vim, too.
Temporarily, I modified it and syntax/vue.vim for supporting lang="postcss" (just hard-coding at scss region like *\(scss|postcss\) :(  ).
My co-workers use another editors like VS-code, Atom and etc...
Their vue-style-syntax for postcss in each editor need lang="postcss".
And explicit lang attribute of style tag looks better for maintenance.
So we decided to add lang="postcss" to code consistently.
P.s.
Actually, if lang="postcss" is nothing, it is loaded well for using nuxt.js with nuxt.config.js - build.postcss. I think this build.postcss config overrides css-loader)

hmm, i'm having this issue as well, i tried @adriaanzon 's fixed and no dice, i'm using cakebaker/scss-syntax on top of this syntax and sekel-vim-vue-syntastic

Is there a tidy solution to this? Do I need to modify my CSS syntax file?

It appears scss syntax is not applying for me as well (I use cakebaker's scss plugin as well).

@adriaanzon Do you have a set of steps the community can take to work together and resolve this issue? You seem to know the most about it. Will we need to PR cakebaker/scss-syntax.vim?

While trying out a fix for #95, I found out that scss works fine when syntax/less.vim isn't loaded.

When removing the runtime! syntax/css.vim lines from syntax/less.vim, scss also works (ref. https://github.com/posva/vim-vue/issues/68#issuecomment-300161558).
What also somehow works is moving LESS to the top of this list: https://github.com/posva/vim-vue/blob/3cc4ac7b02b4ee76a5f16d8b39bf559042f6b266/syntax/vue.vim#L46-L55

Bookmarking this issue so I can remember what to change when I run my plugin updates xD - I wonder if this would be of interest to @cakebaker in the off-chance event that others would rather see his syntax highlighting for vue vs css.

When removing the runtime! syntax/css.vim lines from syntax/less.vim, scss also works (ref. #68 (comment)).
What also somehow works is moving LESS to the top of this list:
https://github.com/posva/vim-vue/blob/3cc4ac7b02b4ee76a5f16d8b39bf559042f6b266/syntax/vue.vim#L46-L55

Strange, i have to move this to the end of the list. Now it's working.

Not sure if something has changed since this fix was implemented but I also have to move less to the end of the list to get SCSS syntax highlighting in vue components.

Is there a way without changing the syntax source?  I don't this those workarounds are legit fix.

You could try setting the g:vue_pre_processors variable to 'detect_on_enter', so it only loads the languages that are needed.

@adriaanzon I tried to set "nolang", "lang", and set let g:vue_pre_processors="detect_on_enter" in my nvim init file. I still have bad syntax check:

@adriaanzon I tried to set "nolang", "lang", and set let g:vue_pre_processors="detect_on_enter" in my nvim init file. I still have bad syntax check:


Add custom goverance to action configs

🤔 Why?

Add custom governance related configurations.
🤓 What?

As titled.
🧪 Tested?

N/A.

Please run https://github.com/MetaphorData/connectors-action/actions/workflows/manual.yml once to verify that it's working end-to-end.

@mars-lan  it works: https://github.com/MetaphorData/connectors-action/actions/runs/6853041811

@mars-lan it works: https://github.com/MetaphorData/connectors-action/actions/runs/6853041811

Didn't seem to populate? https://stage.metaphor.io/dataset/8CDF81FE6B8050607E78C53E8B704B05/columns

@mars-lan it works: https://github.com/MetaphorData/connectors-action/actions/runs/6853041811

Didn't seem to populate? https://stage.metaphor.io/dataset/8CDF81FE6B8050607E78C53E8B704B05/columns

I ran it against QA: https://qa.metaphor.io/dataset/8CDF81FE6B8050607E78C53E8B704B05/columns

@mars-lan it works: https://github.com/MetaphorData/connectors-action/actions/runs/6853041811

Didn't seem to populate? https://stage.metaphor.io/dataset/8CDF81FE6B8050607E78C53E8B704B05/columns

I ran it against QA: https://qa.metaphor.io/dataset/8CDF81FE6B8050607E78C53E8B704B05/columns

I see. Seems like the tags are not populate, probably because the corresponding tags don't exist yet. Consider verify using an existing tag, like Classification=Public.

@mars-lan it works: https://github.com/MetaphorData/connectors-action/actions/runs/6853041811

Didn't seem to populate? https://stage.metaphor.io/dataset/8CDF81FE6B8050607E78C53E8B704B05/columns

I ran it against QA: https://qa.metaphor.io/dataset/8CDF81FE6B8050607E78C53E8B704B05/columns

I see. Seems like the tags are not populate, probably because the corresponding tags don't exist yet. Consider verify using an existing tag, like Classification=Public.

https://stage.metaphor.io/dataset/8CDF81FE6B8050607E78C53E8B704B05/columns
Column tags : Gold, Bronze

@mars-lan  let's merge this?


Couldn't find a project to run. Ensure a project exists in D:\Blazor\WebServerApplication1, or pass the path to the project using --project.

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/blazor-tutorial/run
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Hi @sharvari257
Could you please list the content of D:\Blazor\WebServerApplication1 ?

For some reason your folder does not contain project file (should be  webserverapplication1csproj in your case). Could you please try to create a new solution and start from scratch?

Sure, I will do that.
Thanks for your help btw.
On Thu, Aug 12, 2021 at 9:20 PM Adam Sitnik @.***>
wrote:

For some reason your folder does not contain project file (should be
webserverapplication1csproj in your case). Could you please try to create
a new solution and start from scratch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/6572#issuecomment-897752318, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATTUR6IKGFX65MTPENJ56GLT4PUU5ANCNFSM5CASJU5Q
.
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&utm_campaign=notification-email
.

Did starting over work?

Yes, it worked.
Thanks for your help.
On Tue, Aug 17, 2021 at 3:02 AM Maira Wenzel @.***>
wrote:

Did starting over work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/6572#issuecomment-899832274, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATTUR6OEBZ4X5EBEQ2NNKVLT5F7W3ANCNFSM5CASJU5Q
.
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&utm_campaign=notification-email
.


⚠ Mobitopup has degraded performance

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

HTTP code: 200
Response time: 5604 ms

Resolved: Mobitopup performance has improved in 95bc77d after 12 minutes.


Cannot move inside a song when playing through Aurora

Move in time in a song when song is played using Aurora backend (typically for FLAC files) does not work.

Actually, this only happens for FLAC files and is due to https://github.com/audiocogs/flac.js/issues/8.


All new dashboard with Material Design

Major redesign of Main.elm with MD.
Signed-off-by: Lauren Behan<EMAIL_ADDRESS>TODO:

Finish up the Regulations model to rid it of Paper elements. 👍
Delete the remaining WebComponents no longer being used. 👍
Figure out the constantly frustrating height issues and why it's shortening the drawer when changing from desktop -> mobile
Landscape on mobile drawer scroll and overflow scroll in general. Something isn't right.

This compiles but won't work as intended. When I add Ports.applyMDC to Cmd.batch list on line 27 the compiler says all the entries need the same type. In the process of learning and figuring out union types and if that will help.

I hope you don't mind the unsolicited comment, but I'm still subscribed to the repo and I love watching the progress. Mapping each JS interaction as a pair of ports is a bit of an anti-pattern. A nicer approach is to have one pair of ports for your whole application.
This concept was summarized really nicely by Murphy Randle at elm-conf last month. The video of his talk is posted and I highly recommend it! https://www.youtube.com/watch?v=P3pL85n9_5s
If you have any follow up questions, I'll do my best to help.

@joelclermont thank you! Your insights are always welcome. Amazing timing, I had actually watched that video and went back and listened to the Elm Town podcast episode on Sunday, and have a TODO to implement that pattern to coalesce the ports as advised in that talk. I had purchased a ticket to ElmConf earlier in the year and am really sad I had to return it when I wasn't able to attend.
The big issue we are trying to overcome here is timing the call to window.mdc.autoInit(); to line up appropriately with when Elm adds nodes to the DOM, since we want the MDC library to animate the text fields. It seems that this use case has been accepted as a new feature for elm, #19 on the list at elm-lang/html#53. Since that isn't available yet, an alternative I just worked out is to use Arrive.js to watch for element creation (using the MutationObserver API). This seems preferable to the other hacks I've seen like https://github.com/fredcy/elm-defer-command.

@statik very interesting approach and seems like it fits your use case well. If you make it to next year's elm-conf, we'll definitely have to meet up. elm-conf and StrangeLoop is already blocked on my calendar for 2018 😄

@laurencaitlan I think this is working pretty smoothly now! I also adjusted the autoInit call to suppress the warnings about already initialized components because we get triggered once for every text field that is added, but I think thats reasonable per the MDC autoInit docs we were looking at today.

@joelclermont @statik Thank you both for the help! I can always use it, and especially with learning elm :)


Libgdx not working on my computer

Please ensure you have given all the following requested information in your report.
Issue details
Libgdx not working
Reproduction steps/code
i cant run a build(desktop) in my computer the files are the template files generated by libgdx generator
Stacktrace
harshet@harshet-desktop:~/Desktop/a/LibGDX/Drop$ ./gradlew desktop:run
Starting a Gradle Daemon, 5 incompatible and 1 stopped Daemons could not be reused, use --status for details

Task :desktop:run
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.lwjgl.LWJGLUtil$3 (file:/home/harshet/.gradle/caches/modules-2/files-2.1/org.lwjgl.lwjgl/lwjgl/2.9.3/3df168ac74e4a8c96562cdff24ad352e255bf89c/lwjgl-2.9.3.jar) to method java.lang.ClassLoader.findLibrary(java.lang.String)
WARNING: Please consider reporting this to the maintainers of org.lwjgl.LWJGLUtil$3
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Inconsistency detected by ld.so: dl-lookup.c: 111: check_match: Assertion `version->filename == NULL || ! _dl_name_match_p (version->filename, map)' failed!

BUILD SUCCESSFUL in 2m 21s
5 actionable tasks: 5 executed
harshet@harshet-desktop:~/Desktop/a/LibGDX/Drop$
Please select the affected platforms

[ ] Android
[ ] iOS
[ ] HTML/GWT
[ ] Windows
[ #] Linux
[ ] MacOS

This is most certainly caused by LWJGL 2. Just switch to the LWJGL 3 backend as described here. Also see #6426.

You can also switch your JDK to AdoptOpenJDK; 8 is best-supported by libGDX, but 11 also works (Java 16 does not work currently because Gradle hasn't updated to support it yet). Just get the JDK (not the smaller JRE) for your architecture, which is almost certainly x64. AdoptOpenJDK, for whatever reason, works with LWJGL2 and LWJGL3 on all platforms you can install AdoptOpenJDK, while the default JDKs for most Linux distros only work with LWJGL3 out-of-the-box. If you use IntelliJ IDEA or Android Studio, you can also download an AdoptOpenJDK JDK from the IDE (File -> Project Structure -> SDKs -> Plus at the top -> Choose what JDK you want; though I don't remember the last steps that well, I think they are straightforward).

thank you for your help tommyettinger crykn btw is there is any discord community for libgdx

Yep, it's very active. https://discord.gg/nVT3Xgh


Inline More Angular Examples

This is such a cool project, thanks for putting it together.
I noticed for angular examples that there is a mix between components that have separate files and inline/ single file components (I noticed it even in react styles example but not sure if react can't handle styles inline).
In later versions of angular the language service processess inline html and css/sass correctly.
So I think a lot more angular examples can just be a single file.
E.g. the event handler where it shows an example of (click) event can just be a single file.

I don't mind creating pull requests of these.

@matschik, you are right I was just wondering why some examples where inline and some not.
I found this reference so I guess that's why:
https://angular.io/guide/styleguide#style-05-04


Change API and Bridge Path on Ingress (from subdomain to suffix)

Is your feature request related to a problem? Please describe.
Currently, we are often using xip.io and nip.io as dns provider for bridge.keptn. and api.keptn.. These services are not available all the time, and therefore, some requests or tests fail. Additionally, when using a LoadBalancer, a customer would need two Load Balancers at the moment which could cause additional costs. At least, we currently need to configure the subdomain in the Ingress objects, which causes some additional manipulation.
Describe the solution you'd like
We should make the api and bridge available under the URL https:///bridge and https:///api. For compatibility reasons, we could support the "old" notations and deprecate it with keptn 0.8 or later.
Additional context
This can be either achieved by duplicating the current api endpoints or by rewriting everything which is sent to /api

Talked to @grabnerandi and we both think that it would be nice to add the "new" endpoints alongside to the old ones and deprecate the old ones after a while. Anyway, I would suggest that keptn-on-k3s (as it is a sandbox project) will only configure the new endpoints by default.


[Bug]:  Issue Templates Not Working Due to YAML Syntax Errors

Description
Currently, some of the issue templates on this repository are not working as expected. Specifically, the following issue templates are affected:

documentation.yml
feature_request.yml
other.yml

The reason for this is that there are syntax errors in the YAML files of these templates. As a result, users are unable to create issues using these templates.
To Reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Anything else?
No response
Code of Conduct

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

Sure, go ahead!

Issue fixed by #749


Support any level of nested directories

TIL php's glob() function does not support globstar (**), and treats it as a single *. This means that the Model finder is only matching php model classes that are one level deep. Based on my research, i can't find anything that would suggest that you can change that. Due to this, I have replaced the glob match with a RecursiveDirectoryIterator that will retrieve model files that are nested any level deep

It seems like the tests are failing for this one. Can you fix them?

Thank you!


Fix GzDecoder Write partial filenames and comments

If the gzip header contains an optional filename or comment but they are not completely contained in the first buffer sent to a write::GzDecoder, then a valid header is created, missing data from these optional sections. A subsequent write call with the remaining header will treat the remaining header as encoded data and attempt to decode it, making the file appear to be corrupt.
This change rewrites the header parsing code to handle partial headers correctly for both Read (where WouldBlock is handled specially) and Write (where UnexpectedEof is handled specially).
The parsing code moves from bufread.rs to mod.rs to emphasize that it is also used by write.rs. write.rs no longer uses any symbols from bufread.rs.
The only test in bufread.rs tested Buffer which is no longer needed, so it was removed. The support code in the bufread tests module was used by a test in mod.rs which tests a read::GzDecoder so the support code and the test move to read.rs.
Fixes #320

After fixing the bug, it took a few iterations to get the size of GzDecoder back to its previous size. On 64-bit, write::GzDecoder<&mut [u8]> is now 216 bytes (previously 224 bytes). Moving the header into bufread::GzState makes bufread::GzDecoder<&[u8]> 176 bytes (previously 296 bytes).

Thanks for merging. It is a pleasant surprise when a well-aged PR finally gets merged. This patch has been running with no problems in our infrastructure for 9 months, so I'm reasonably confident that it is an improvement with no major downsides.


updated hopper-disassembler (3.11.13)

Thank you for the contribution. It was merged directly as 3d6da08d2076aa25366188f1d9fed4d2f74170ce to keep commit history cleaner. Your contribution is still credited to you.


Precompiled headers not used in unity target

When using a unity target the precompiled headers are not used.
Is this normal or am I doing something wrong?

Pretty sure that's normal since a unity build would not benefits from using a precompiled header.

Why not? A unity build includes a few of my own files that change frequently, and a lot of system includes that never change. If I modify my code and recompile, having the system includes precompiled could be much faster, no?
Is there a way to have a target with both unity and precompiled headers enabled?

Any update on that point ?

It is even more important when using cotire with COTIRE_MAXIMUM_NUMBER_OF_UNITY_INCLUDES


[0.7.0-beta.1] Cascader init data bug

Version
0.7.0-beta.1
Environment
macos
Reproduction link
https://stackblitz.com/edit/ng-zorro-antd-setup-xz9flq?embed=1&file=app/app.component.ts
Steps to reproduce
set init data for the cascader, then click.
What is expected?
data in every level will be right
What is actually happening?
data in first level is blank
Other?

@fbchen

The method writeValue causes 1st column options lost, for not calling the nzLoadData. We will fix it soon. Thanks @pengsoftdotcom


backfeed Flickr tags on your photos

On Flickr, your contacts have permission (by default*) to add arbitrary text tags to your photos.
If your photo is a POSSE copy of an original post on your site, Bridgy should backfeed these as "tag-of" responses to the original post.
This is currently brainstormed here: https://indieweb.org/tag-reply#How_to_simple_tag-reply
In short with a class="u-tag-of" href="originalpostURL" and p-category properties of the text tags in the content of the h-entry.
Though as of this issue creation, there are no documented real world examples in the wild. I may have to change that and will follow-up once there are real world examples.
(*default: you can change permissions on Flickr to let anyone tag your photos, or no one, etc.)

Related but different: https://github.com/snarfed/bridgy/issues/488

API support for this is unclear. the only method i've found that seems likely to return it is https://www.flickr.com/services/api/flickr.photos.getInfo.html , but not even sure about that.

@tantek confirmed that these tags from other users show up immediately, and the <tag> elements returned by getInfo have an author attribute, so i expect that's it.

also as far as we know, flickr is the only (bridgy) silo with this feature.


Add documentation on how to read range keys

Currently (AFAICT) we don't explicitly document how to read the keys when they are pretty-printed.  It's not that intuitive until you spend time learning how to do it (esp. how the output format displays indexes).
Luckily the key format is described very nicely by the Mappingf table data to key-value storage blog post.
Possibly this is a more general version of #2909
Would definitely have been useful during work on #2769 and #2282
Related work:

file issues on cockroach to get all of the key printing to use the same output format
started on this with https://github.com/cockroachdb/cockroach/issues/24740

see also: https://github.com/cockroachdb/cockroach/blob/master/docs/tech-notes/encoding.md

Relates a bit to https://github.com/cockroachdb/docs/issues/2862

We have closed this issue because it is more than 3 years
old. If this issue is still relevant, please add a comment and re-open
the issue. Thank you for your contribution to CockroachDB docs!


BSD socket offload with IPv4 and IPv6 disabled breaks all net samples

Is your feature request related to a problem? Please describe.
When using the socket offload API where IPv4 and IPv6 are disabled, all net samples are broken due to their dependence on NET_CONFIG_* settings.
Describe the solution you'd like
In a perfect world, samples would still work -- the main issue being where to get things like peer server address.
Describe alternatives you've considered
Just starting the discussion.  I haven't explored alternatives yet.
Additional context
Devices like TI's SimpleLink Wifi and the upcoming modem context changes allow for them to be used without the majority of the Zephyr IP stack -- instead offloading the IP stack onto the NCP via the NET_SOCKETS_OFFLOAD config.
This saves quite a lot of flash and processing when combined with CONFIG_IPV4=n and CONFIG_IPV6=n, but means the user has to customize each networking sample.

@pfalcon @GAnthony starting the discussion

also adding @rlubos

When using the socket offload API where IPv4 and IPv6 are disabled, all net samples are broken due to their dependence on NET_CONFIG_* settings.

Could you elaborate this a bit more? At least compilation seems to work just fine if I disable IPv4 and IPv6. What kind of issues there are in runtime (I do not have any offloaded devices that I could try myself)?.
What I did to test the compilation:

Create samples/net/sockets/echo_server/overlay-offload.conf with this content

CONFIG_NET_IPV4=n
CONFIG_NET_IPV6=n
CONFIG_NET_OFFLOAD=y
CONFIG_NET_SOCKETS_OFFLOAD=y

$ cd samples/net/sockets/echo_server
$ cmake -B build -DBOARD=cc3220sf_launchxl -DOVERLAY_CONFIG=overlay-offload.conf .
$ make -C build

@jukkar You are correct.  The server-based samples might work somewhat.
However, many of the client-based samples all use logic like this in echo_client/tcp.c::start_tcp():
https://github.com/zephyrproject-rtos/zephyr/blob/master/samples/net/sockets/echo_client/src/tcp.c#L175
All functions of tcp are wrapped with IS_ENABLED(CONFIG_NET_IPV*) checks.
Or the coap_client:
https://github.com/zephyrproject-rtos/zephyr/blob/master/samples/net/sockets/coap_client/src/coap-client.c#L66
(Fixes title of the issue to be more specific)

All functions of tcp are wrapped with IS_ENABLED(CONFIG_NET_IPV*) checks.

Indeed, that is unfortunate. One option could be to change the IS_ENABLED(CONFIG_NET_IPV*) to IS_ENABLED(USE_IPV*) and then have in the code something like this
#if defined(CONFIG_NET_IPV6) || defined(CONFIG_NET_OFFLOAD)
#define USE_IPV6
#endif

After some thinking, I think we need to leave the IS_ENABLED(CONFIG_NET_IPV*) as is in the samples as they depend on an IPv6 feature. Enabling IPv6 feature is a generic thing and has nothing to do with offloading.
We need to fix the other part of the system so that if the user enables offloading, then we disable core IPv6 & IPv4 stuff. In practice this probably means adding some new kconfig options and some voodoo magic in CMakeLists.txt file, or something like that. I try to come up with some patches for this.

I've used NET_RAW_MODE for some time with nRF91, it did its job, yet it proved to be too strict and disabled too much. I'd also avoid disabling native TCP/IP stack solely on the offloading option, as it would prevent the use cases that #18106 will open (like running both native and offloaded stack).
I think that Jukka got the point here, that we'd need a new Kconfig (perhaps something like CONFIG_NATIVE_IP_STACK), that would control only the inclusion of the native stack, w/o messing with the app protocols or utils. The config should be enabled by default, and the offloaded engines (or samples) could decide whether they disable the native stack or not.

I created a PR that allows user to disable native IP stack. It is only build tested as I do not have proper hw to test it.

NOTE TO BE INCLUDED IN THIS FIX
The LwM2M subsys makes use of several CONFIG_NET_IPv* checks which include 1 for DNS.   When using offloaded APIs there is no requirement for IPv4/IPv6 to be enabled and this is currently being worked around by defaulting offload APIs to hint at using IPv4 DNS lookups.
A proper solution needs to be implemented: as in we might force offloaded drivers to define which IP versions they support.   With the addition of NET_NATIVE this wouldn't add the internal stack-based code, but would allow subsystems to still use this information in an intelligent way.


Subsystems of r1146 and r1135

Description of the issue:
The subsystems assigned to reactions r1146 and r1135 seems incorrect. The (main) metabolites involve in these reactions are reactant/product of reactions in exclusively the Cholesterol metabolism subsystem.
Expected feature/value/output:
Assign the reactions to the Cholesterol metabolism subsystem.
Current feature/value/output:
Currently r1146 is assigned to the "Transport reactions" subsystem and r1135 is assigned to "Miscellaneous"
I hereby confirm that I have:

[X] Tested my code on my own computer for running the model
[X] Done this analysis in the master branch of the repository
[X] Checked that a similar issue does not exist already

Thanks for posting the issue. I assume this suggestion is based on the metabolic network maps from Metabolic Atals. If you can add a photo or a link to the map that provides this association.

Actually I suggested this based on the GEM Browser pages of the main metabolites:
https://www.metabolicatlas.org/explore/gem-browser/human1/metabolite/m00968r
https://www.metabolicatlas.org/explore/gem-browser/human1/metabolite/m03158r
https://www.metabolicatlas.org/explore/gem-browser/human1/metabolite/m00809r
The map is actually incorrect since r1146 is already assigned to the Cholesterol metabolism subsystem, but it helps to notice the problem. Indeed, it seems r1134 should also be assigned to that subsystem.

This map is a piece of strong evidence. The proposed change will be applied as soon as possible. Thanks @pecholleyc

Now this has been fixed in devel.


cmd/compile: syntax error when const & label names overlap

The following example fails to compile with syntax error: unexpected :, expecting semicolon or newline or } on go1.6beta1:
package main

const (
	test = 1
)

func main() {
	goto test
test:
}

started


OpenSlides 3 tests (WIP)

@CatoTH Thanks for you work. We will fix the tests here and if everything is right (with empty tests) we will merge this, so then we can add tests during development.

Is it possible in travis to run the js-tests in a different test (like the different test for python 3.6 and python 3.7)? So a python change does not have to wait for js-tests?


Fix(ResourceTimeSeriesChart.js): change shares-> cores

Change text shares to cores in ResourceTimeSeriesChart.js
Closes Issue 333
Testing

Trade-offs

Dependencies

Screenshots

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

For reviewers: https://jira.mesosphere.com/browse/DCOS-38736

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


Bitvavo

Hello can you add bitvavo

Probably not in the near future. Honestly, I haven't even known this  market until now. There will be an update with support for Kraken this year. Then I will probably focus on more functionality...


Fix CORS limitation for chrome-extension

CORS from chrome-extension
There is a limitation on the current version of zio/zio-http
The CORS middleware not working with origin: chrome-extension://appid
See https://github.com/zio/zio-http/issues/2489
I started a PR https://github.com/zio/zio-http/pull/2490 to fix this on the Library level.
After being fixed there we just need to wait for release and we can update to the latest version
Affects
This problem only affects agents calling the mediator directly from a Chrome extension (and you need CORS headers)
Mitigation
The issue is mitigated by setting up the CORS on the PROXY level.
All current deployments have this configured.

This is fixed


PR: Enable/disable folding guides when cursor enters/exits the left panel

Description of Changes
This PR disables folding guides visibility by default, instead, they will be shown only if the cursor enters the left panel and disabled when the cursor leaves it. We also re-enable the folding support for large files that was disabled previously.

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

Issue(s) Resolved

Fixes #
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @andfoy

Nice work @andfoy !
I suggest we always display the folded indicators, (much like VSCode doeS)

Hello @andfoy! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/editor/panels/codefolding.py:

Line 255:80: E501 line too long (83 > 79 characters)
Line 263:80: E501 line too long (83 > 79 characters)
Line 264:80: E501 line too long (83 > 79 characters)
Line 268:80: E501 line too long (86 > 79 characters)

@goanpeca Here it is:

Awesome! 🥳

@ccordoba12, this is ready for a final review


Various improvements for e1000 and igc

Summary

drivers/net/{e1000|igc}: configure RX/TX descriptors from Kconfig
configure E1000/IGC RX/TX descriptors from Kconfig
drivers/net/igc: make Interrupt Throttle configurable
drivers/net/{e1000|igc}: fix link status crash
netdev_lower_carrier_xxx API can't be used in interrupt context
drivers/net/{e1000|igc}: reset TX ring when disconnected
drivers/net/{e1000|igc}: limit no packet is transmit after carrier off

Impact

moved some hardcoded values to Kconfig
fixed various issues when repeatedly pluggin and unplugging the eth cable

Testing
intel hardware

[Experimental Bot, please feedback here]
Yes, this PR appears to meet the basic NuttX requirements, but could be improved with more detail.  Here's a breakdown:
Strengths:

Summary:  Provides a decent overview of the changes, touching upon the "what" and "why."
Impact:  Identifies key impacts (configuration changes, bug fixes).
Testing:  Confirms testing was done on Intel hardware.

Weaknesses & Areas for Improvement:

Summary: Lacks sufficient detail on how the changes work.  More explanation is needed for each bullet point, particularly the fixes.  What was the exact nature of the crash? How was the TX ring reset implemented? What was the limitation applied to prevent transmissions after carrier off?  Linking to a related NuttX issue would greatly strengthen this section.
Impact:  Needs more specific YES/NO answers to the listed questions.  For example:

Impact on user: YES (Users can now configure RX/TX descriptors via Kconfig)
Impact on build:  Potentially YES (If Kconfig options are added, users might need to reconfigure). Explain what configurations are impacted.
Impact on hardware: YES (Specifically affects Intel network drivers - e1000 and igc).
Impact on documentation:  Potentially YES (If Kconfig options are added, documentation should be updated). Explicitly state if documentation updates were included.
Impact on security: NO (or YES if applicable – explain why).
Impact on compatibility: Potentially YES (if changing descriptor counts could affect existing users).

Testing:  Severely lacking detail.

Build Host(s): Be specific.  "Linux" is insufficient.  Provide distro, version, kernel version, compiler version (e.g., "Ubuntu 22.04, Linux 5.15, GCC 11.2.0").
Target(s):  Which Intel hardware? Be precise (e.g., "Intel i210, using the xyz board configuration").
Logs:  Absolutely essential to include before and after logs demonstrating the fixes.  Showing the crash before and its absence after, the TX ring behavior, etc., is crucial for reviewers.  Without these, the PR is difficult to evaluate properly.

In short: The PR provides a starting point, but needs significant expansion, particularly in the Impact and Testing sections, to meet the NuttX standards fully. Providing clear, specific information is key to a successful review process.


atom auto-complete with ensime stopped

Hi is it possible to have the default atom autocomplete when ensime server is stopped?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/28321395-atom-auto-complete-with-ensime-stopped?utm_campaign=plugin&utm_content=tracker%2F14719420&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F14719420&utm_medium=issues&utm_source=github).

Should be, you mean that after ensime has been started and then stopped there is no autocomplete in scala files? Sounds like a cleanup issue…

I have this issue, but it wasn't always like this. So I don't know if it's related with Ensime or with some other plugins that I have..

the autocomplete comes back when disabling the plugin, any idea how this can be debugged? nothing shows in the console...

I'm looking into this. Can't seem to find a way to "de-register" the provider. I want to be able to exclude other providers when Ensime is on. The provider api seems to only cleanup when the package is de-activated, but that is something we cannot do. We need our own lifecycle handling because reasons.
Posted: https://github.com/atom/autocomplete-plus/issues/616

Ping @caente, @laughedelic
To summarize: It seems the autocomplete-plus plugin only removes our provider when the package is disabled. The whole provider api is kind of static: https://github.com/atom/autocomplete-plus/wiki/Provider-API
I can currently only give a one-off boolean in "excludeLowerPriority" on activation time of the package. I definitely WANT to remove bloat while an Ensime instance is active so I want excludeLowerPriority set to true. I'm suggesting autocomplete-plus adds a possibility to put a function there that is called each time instead.
As a temporary workaround, we can simply add a setting for excludeLowerPriority. Not very nice though.

@hedefalk you mean a setting in the atom plugin? how is that different from simple go there and disable it?

Yes. With a bool setting you can keep default provider even with ensime started. Will be dups though.

ah I see... well at least I'll be willing to give it a try


Fix funky cluster icons

Issue
Tweet clusters on the map are functioning normally, but the icons seem to be rendering incorrectly.

What do you mean?

Can you see the screenshot? It looks like the icons' colors are messed up.

Part of the requirement was the coloring, so I added I modify the pixel argb when producing the bitmap

We need to color the nodes unfortunately because of the requirements.


Move kubernetes and crio jobs to run as prow periodics

The jobs updated in https://github.com/openshift/aos-cd-jobs/pull/1162 need to be managed by prow with the prospect of moving them to run by the ci-operator.
@stevekuznetsov @paradigm

/assign @bbguimaraes

They're on the Trello card already
/close


Pico: restore squeeze and trigger click actions

apparently the pico needs these, too.

These actions are not supported by the Focus 3. If you want you can add them for Pico in the if block.

These actions are not supported by the Focus 3. If you want you can add them for Pico in the if block.

Done.

fixed conflict.

nice!


reconsider key capture method

With the native winit keypress capturing, we are unable to block keypresses from continuing to the desired window (for as far as I know). Thus an issue that we have is that when you are trying to type in japanese, the actual keys you are typing are still being sent to the focused window. We need more low level access (to x11?) to be able to intercept and stop keypresses from continuing.
Two potential options are:

InputBot: seems simple, but requires it to be run as root
ktrl: maybe overkill for what we are doing, also has pretty length setup on the user part

another option is to write my own x11 adapter code for specifically grabbing inputs with x11rb. this code already sorta exists in the history of matsuba - before i switched to wgpu based rendering. I could potentially salvage this and use it exclusively as the keyboard input code

went with the platform dependent method and using x11rb - implemented in #19


Editor prototype

Coverage decreased (-1.0%) to 56.878% when pulling fb3d6715df2e59e84616e28bc2d683e929615315 on editor-prototype into 523983688bc33c000db8249ce11f236c1ecd55b9 on master.


Update spec.ts

fix import and text check

I signed it!

dfdfd

It seems the second await is only needed because of the last promise skip bug

Double checked, so with the current typescript 2.0.3, it is needed to have the second async
otherwise, the expect - check wont be done. (e.g. if in the next test you write
await browser.get('google.com')
it will throw an exception because the previous test hasn't been finished.) It seems this is only needed if there is at least one await call before the expect.

Thanks for the fix!


mjml2: Render and redirect the result to a file

If I want to render the result to a file with
mjml input.mjml -o my-email.html
it behaves like the output to terminal
mjml input.mjml
Working with mjml 2 and node 4.4.3
Maybe a bug? Any workarround?

+1
In my case, i don't have any error on screen with command line and the file is not generated
If i use the watch option I have :
/home/vagrant/.node_modules_global/lib/node_modules/mjml/node_modules/mjml-cli/lib/client.js:106
bufferPromise.then(function (mjml) {
^
TypeError: bufferPromise.then is not a function
at render (/home/vagrant/.node_modules_global/lib/node_modules/mjml/node_modules/mjml-cli/lib/client.js:106:17)
at StatWatcher. (/home/vagrant/.node_modules_global/lib/node_modules/mjml/node_modules/mjml-cli/lib/client.js:162:12)
at emitTwo (events.js:100:13)
at StatWatcher.emit (events.js:185:7)
at StatWatcher._handle.onchange (fs.js:1369:10)
Only solution is to get the output on console ....
thanks in adance for your help

@francoismart it looks like you have a node version issue, can you give me your node version using node -v ?
@Bloggerschmidt I'll take a look, thanks for reporting it !

@iRyusa Thank you for your great work. I find out, that
mjml -r input.mjml -o my-email.html
works. So, this issue is about the -r

@iRyusa i get 5.6.0 so i'm going to upgrade to 6  ?
another solution would be the desktop app isn't it ?

@francoismart I was mislead by the error, @GuillaumeBadi has opened a PR #206 it should fix the watch option sorry about that !

@iRyusa  nice. but my first issue is to have a log on screen or file when nothing is generated .... is there a way to see errors ? thanks in advance

@francoismart can you share your mjml ? thanks

@iRyusa Got the exact same error "TypeError: bufferPromise.then is not a function"
as @francoismart since update 2.0 when compiling with the -w option, any help ?

@pixelize this is fixed by the latest pull request, it will be updated soon on npm

Thanks, awesome work guys ;) If anyone would be kind to have a look to my problem :
https://github.com/mjmlio/mjml/issues/204
Thanks in advance ;)

@iRyusa done on slack ... thank you and waiting for th update

Hi !
It should be ok now on 2.0.1 ! I close it, you can re-open if needed


v2 Istio - Combine 1.7.301 & 1.7.302 charts

rancher/rancher:v2.5.4-rc6
In the dev branches we have chart versions for both 1.7.301 & 1.7.302, but our latest published chart is 1.7.300.
https://github.com/rancher/charts/pull/848/files - 1.7.301 for a Kiali fix
https://github.com/rancher/charts/pull/850/files - 1.7.302 for CNI/Jaeger
Instead of publishing two new charts, we should combine the two into 1.7.301.

rancher/rancher:v2.5.4-rc8

Charts are combined into one version: 1.7.301
Fresh install Istio 1.7.301 with cni, Kiali, Jaeger enabled - all tests succeeded
Upgrade from v2.5.3 - Istio 1.7.300 to v2.5.4-rc8 - Istio 1.7.301

enable Jaeger and cni on upgrade
then disable Kiali, Jaeger and cni post upgrade - all tests succeeded


Feature/logging system

Added global logger using loguru and attached it to the app instance.
Instantiated the logger in main.py
Added logging tests
The logger configuration file is in app/internal and can be used to change log rotation, retention and file location.
To use the logger:
app.logger.debug(message)
app.logger.info(message)
app.logger.warn(message)
app.logger.error(message)
app.logger.critical(message)

Codecov Report

Merging #112 (973b4fc) into develop (d706153) will decrease coverage by 1.83%.
The diff coverage is 94.59%.

@@             Coverage Diff             @@
##           develop     #112      +/-   ##
===========================================
- Coverage   100.00%   98.16%   -1.84%
===========================================
  Files           16       11       -5
  Lines          544      273     -271
===========================================
- Hits           544      268     -276
- Misses           0        5       +5

Impacted Files
Coverage Δ

app/internal/logger_customizer.py
93.75% <93.75%> (ø)

app/main.py
95.45% <100.00%> (-4.55%)
:arrow_down:

app/internal/agenda_events.py
93.75% <0.00%> (-6.25%)
:arrow_down:

app/routers/event.py
100.00% <0.00%> (ø)

app/routers/agenda.py
100.00% <0.00%> (ø)

app/database/models.py
100.00% <0.00%> (ø)

app/routers/profile.py
100.00% <0.00%> (ø)

app/database/database.py
100.00% <0.00%> (ø)

app/routers/invitation.py

app/internal/utils.py

... and 5 more

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 d706153...e71328d. Read the comment docs.

Codecov Report

Merging #112 (973b4fc) into develop (d706153) will decrease coverage by 1.83%.
The diff coverage is 94.59%.

@@             Coverage Diff             @@
##           develop     #112      +/-   ##
===========================================
- Coverage   100.00%   98.16%   -1.84%
===========================================
  Files           16       11       -5
  Lines          544      273     -271
===========================================
- Hits           544      268     -276
- Misses           0        5       +5

Impacted Files
Coverage Δ

app/internal/logger_customizer.py
93.75% <93.75%> (ø)

app/main.py
95.45% <100.00%> (-4.55%)
:arrow_down:

app/internal/agenda_events.py
93.75% <0.00%> (-6.25%)
:arrow_down:

app/routers/event.py
100.00% <0.00%> (ø)

app/routers/agenda.py
100.00% <0.00%> (ø)

app/database/models.py
100.00% <0.00%> (ø)

app/routers/profile.py
100.00% <0.00%> (ø)

app/database/database.py
100.00% <0.00%> (ø)

app/routers/invitation.py

app/internal/utils.py

... and 5 more

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 d706153...e71328d. Read the comment docs.

Please resolve the conflicts :)

Please resolve the conflicts :)

Please resolve the conflicts :)

Done, I was sure you told me to add vscode to gitignore :O

Please resolve the conflicts :)

Done, I was sure you told me to add vscode to gitignore :O


Build an image with the database already configured.

It seems silly to say this... but a docker image that requires 10 minutes to start is just plain ridicules. And unusable. Images of MySQL, Aurora, Postgres, etc. all start and are available in seconds.
At the heart of this is the fact that you think it's ok to create/configure the database during "docker run" instead of "docker build". The database should be created and configured during "docker build". I don't understand why you believe this is not an option.
Just use dynamic listener registration instead of a listener.ora file, and the dynamic docker hostname should be detected and used at startup time.

Yes it is. Not sure if it's suitable for you but you can find here instruction how to speed this up: https://medium.com/@ggajos/drop-db-startup-time-from-45-to-3-minutes-in-dockerized-oracle-19-3-0-552068593deb

The database character set has to be specified on DB configuration and cannot be changed anymore later on. While AL32UTF8 may be good enough for you, there are plenty of other users out there that have said AL32UTF8 is not an option for them. We didn't even have the option to specify the character set in the beginning and got a lot of feedback that it is needed.
The same goes for the SID. We didn't think we need to provide an option to specify your SID, it's a container, what do you care, right? Well, think again. Many folks had the need or wanted to have their SIDs the way they specified and so we also gave that option.

I asked you to "create an image"... not "stop creating anything else and only create this one image". By all means, continue to produce what you currently produce... many people with customization requirements will find these images useful. But start providing a few already configured images with a few standard charactersets and a constant SID name.

Now, for a long time have we provided a sample on how you can build an image with the DB inside, see https://github.com/oracle/docker-images/tree/master/OracleDatabase/SingleInstance/samples/prebuiltdb
You need to modify the Dockerfile once and commit the image once, is that really too much effort?

All of your competitors (you know... the ones with increasing market share) provide this, and you are the only ones that don't. So I would ask you the same question... is this really too much effort for you to produce?

@stewartbryson I understand that you might be somewhat frustrated, but I don't think passive-aggressive comparisons to competitors is warranted. Especially considering Oracle has been publicly publishing our Dockerfiles for significantly longer than any of them and has certified our products in containers for longer again.
Let's just stick to the topic at hand, shall we? And on that note:  we welcome and accept submissions to this repo, so pull requests (that meet the contribution guide) welcome!

@stewartbryson I understand that you might be somewhat frustrated, but I don't think passive-aggressive comparisons to competitors is warranted. Especially considering Oracle has been publicly publishing our Dockerfiles for significantly longer than any of them and has certified our products in containers for longer again.

Just let me know when I can docker run oracle... because I can do that with every other... Oh yeah, sorry for comparing you again.

Shall i open a new Issue for my Question then?

Shall i open a new Issue for my Question then?

I'm happy to reopen @Lordroran if my Issue description is in-line with your request. I think the maintainers are hoping for a PR from someone and probably aren't going to prioritize this. I've moved all my ODI-based images to use MySQL instead of Oracle... but I can't do that with other FMW products. So I still use Google compute instances in those areas where the spin-up time is too excruciating to use these images.
So... shall I reopen?

I would like to have this Issue reopened, because i do not see a possibility to automate this with the current images.

@gvenzl and I discussed this and I believe he is working on updating the Dockerfiles to remove the EXPOSE and VOLUME directives that are no longer necessary. This will allow for automatic Database creation during build to persist to the image.
Though, I suspect that changing the ORACLE_BASE and ORACLE_HOME parameters from /opt/oracle would probably do the same thing right now, i.e. just move the oradata directory out from the VOLUME location.

Though, I suspect that changing the ORACLE_BASE and ORACLE_HOME parameters from /opt/oracle would probably do the same thing right now, i.e. just move the oradata directory out from the VOLUME location.

I suspected this, but i have troubles starting Oracle while at build time. Last time i tried the script did not return and i was stuck in the start script.
Do you have an example for starting Oracle manually?

No, but if changing the environment variables causes the container not to start correctly, I would consider that a bug.

This is not about changing environment variables. This is about starting the DB while doing a dockerbuild. We need to start Oracle during the dockerbuild to initialize the DB.
I tried to do this by hand with either /opt/oracle/runOracle.sh or /opt/oracle/createDB.sh, but both of the scripts do not seem to terminate after the DB is ready.

This is not about changing environment variables. This is about starting the DB while doing a dockerbuild. We need to start Oracle during the dockerbuild to initialize the DB.
I tried to do this by hand with either /opt/oracle/runOracle.sh or /opt/oracle/createDB.sh, but both of the scripts do not seem to terminate after the DB is ready.

runOracle.sh is designed to run perpetually... it's what is specified as the CMD in the Dockerfile.
You can simply remove the tail -f part from this script so that it completes, and then userunOracle.sh && tail -f <whatever> as the CMD and it should be equivalent.

My 2c: even if it results in a big image, I'd warmly welcome containers with a pre-built DB that I can run with a simple docker run oraclexxx.
No need for custom service names or character sets.
Atm I am dabbling with adding oracle to a docker-compose stack, and the download+build time is quite long (I have basically forked the oracle 18 container inside my project).
For persisting data, I use host mounts instead of volumes, and I think that it is not hard, for anyone who desires so, to add to her own docker shell scripts or docker-compose config the bit that brings back the data files to the host. The main problem seems to be with how the db is not natively capable of (re)creating the datafiles if those are missing at boot.
This could be fixable f.e. by keeping copies of empty data files in a separate location and having a shell script running at container start that copies them over if oradata dir is empty. Kinda like what runOracle.sh currently does (except for the fact that runOracle.sh moves the existing files, which makes it work only once and break if the volume gets manually cleaned up before a container restart).
Maybe theer is even a better, native solution that I am not aware of that would cretae data files... my oracle-fu is getting rusty

runOracle.sh is designed to run perpetually... it's what is specified as the CMD in the Dockerfile.
You can simply remove the tail -f part from this script so that it completes, and then userunOracle.sh && tail -f <whatever> as the CMD and it should be equivalent.

My Problem right now is that even if i remove the tail part, the script calls the other script createDB.sh and this script doesnt return. I dont know if i did not wait enough, but "docker ps" says its over one hour. The last output message is "Completing Database Creation".

@Lordroran I have done presumably the exact same thing: in my container, runOracle.sh has been customized with a simple removal of the tail/wait part. the container's ENTRYPOINT and CMD are changed to run my own shell script, which does call runOracle.sh and then goes waiting on its own.
It does work, but it takes a long time on the first start of the container. I am using a 16GB, 2 CPU cores laptop, running docker in a linux VM on windows, and I get 5-10 minutes for db creation.
The code can be seen here: https://github.com/gggeek/db-3v4l/tree/oracle_support/docker/images/oracle/18.4
And here is the output of 'docker log'
oracle_18_4_1            | [Thu Mar  5 13:57:40 UTC 2020] Handing over control to runOracle.sh...
oracle_18_4_1            | ORACLE PASSWORD FOR SYS AND SYSTEM: 3v4l
oracle_18_4_1            | Specify a password to be used for database accounts. Oracle recommends that the password entered should be at least 8 characters in length, contain at least 1 uppercase character, 1 lower case character and 1 digit [0-9]. Note that the same password will be used for SYS, SYSTEM and PDBADMIN accounts:
oracle_18_4_1            | Confirm the password:
oracle_18_4_1            | Configuring Oracle Listener.
oracle_18_4_1            | Listener configuration succeeded.
oracle_18_4_1            | Configuring Oracle Database XE.
oracle_18_4_1            | Enter SYS user password:
oracle_18_4_1            |******
oracle_18_4_1            | Enter SYSTEM user password:
oracle_18_4_1            | ***
oracle_18_4_1            | Enter PDBADMIN User Password:
oracle_18_4_1            | ***
oracle_18_4_1            | Prepare for db operation
oracle_18_4_1            | 7% complete
oracle_18_4_1            | Copying database files
oracle_18_4_1            | 29% complete
oracle_18_4_1            | Creating and starting Oracle instance
oracle_18_4_1            | 30% complete
oracle_18_4_1            | 31% complete
oracle_18_4_1            | 34% complete
oracle_18_4_1            | 38% complete
oracle_18_4_1            | 41% complete
oracle_18_4_1            | 43% complete
oracle_18_4_1            | Completing Database Creation
oracle_18_4_1            | 47% complete
oracle_18_4_1            | 50% complete
oracle_18_4_1            | Creating Pluggable Databases
oracle_18_4_1            | 54% complete
oracle_18_4_1            | 71% complete
oracle_18_4_1            | Executing Post Configuration Actions
oracle_18_4_1            | 93% complete
oracle_18_4_1            | Running Custom Scripts
oracle_18_4_1            | 100% complete
oracle_18_4_1            | Database creation complete. For details check the logfiles at:
oracle_18_4_1            |  /opt/oracle/cfgtoollogs/dbca/XE.
oracle_18_4_1            | Database Information:
oracle_18_4_1            | Global Database Name:XE
oracle_18_4_1            | System Identifier(SID):XE
oracle_18_4_1            | Look at the log file "/opt/oracle/cfgtoollogs/dbca/XE/XE.log" for further details.
oracle_18_4_1            |
oracle_18_4_1            | Connect to Oracle Database using one of the connect strings:
oracle_18_4_1            |      Pluggable database: oracle_18_4/XEPDB1
oracle_18_4_1            |      Multitenant container database: oracle_18_4
oracle_18_4_1            | Use https://localhost:5500/em to access Oracle Enterprise Manager for Oracle Database XE
oracle_18_4_1            | The Oracle base remains unchanged with value /opt/oracle
oracle_18_4_1            | #########################
oracle_18_4_1            | DATABASE IS READY TO USE!
oracle_18_4_1            | #########################

Btw: I did not test this theory yet, but it might be that merging this PR ( https://github.com/oracle/docker-images/pull/1537 ) could make it easier to share a pre-built container which has a ready-to-use database:

the original container gets built with a ready-to-run-db, having a predetermined sys password and charset. The image is big in size, but downloading it once is enough to run it many times locally. Data is only persisted inside the container, so it is not recommended to be used as-is for persistent scenarios. Resetting the container to its pristine image corresponds to a db reset.
once the end user has downloaded it locally, she can add opt for adding a docker mount/volume that maps to '/oradata' inside the container. When the container is started the next time, the db will be freshly recreated (without need to reinstall the oracle software), and from then on it will be persisted on the host

runOracle.sh is designed to run perpetually... it's what is specified as the CMD in the Dockerfile.
You can simply remove the tail -f part from this script so that it completes, and then userunOracle.sh && tail -f <whatever> as the CMD and it should be equivalent.

My Problem right now is that even if i remove the tail part, the script calls the other script createDB.sh and this script doesnt return. I dont know if i did not wait enough, but "docker ps" says its over one hour. The last output message is "Completing Database Creation".

Nevermind... I just came back from lunch and it says 51% complete. So it is just still running.

I need to build an already configured Oracle image to speed up Oracle database start-up during CI tests.
I let this here if anyone one wants to build an already configured Oracle image, please let me know if you know a better way to do.
You have to first checkout this branch or apply the following patch
Then type the following
$ ./buildDockerImage.sh -v 18.4.0 -x
$ docker run -d  -e ORACLE_SID="XE" -e ORACLE_PWD="adminpass" -e ORACLE_PDB="ORCLPDBTEST" -e ORACLE_CHARACTERSET="AL32UTF8" -p <IP_ADDRESS>:1521:1521 oracle/database:18.4.0-xe
96764ef54ac7e4d6144f5e13d01f1dd8535d4ef743c07c82ebfca16aaea795bc
$ # Wait for Oracle to be completely started
$ docker logs 96764ef54ac7e4d6144f5e13d01f1dd8535d4ef743c07c82ebfca16aaea795bc
$ docker stop 96764ef54ac7e4d6144f5e13d01f1dd8535d4ef743c07c82ebfca16aaea795bc
$ docker commit 96764ef54ac7e4d6144f5e13d01f1dd8535d4ef743c07c82ebfca16aaea795bc oracle-configured

You could have changed the ORACLE_BASE environnement variable from the docker build command line, but you 'd still need to add this line to make it properly work.
I try another approach which would have not needed to commit and only a call to buildDockerImage, but it fails with the following error
ERROR:
ORA-01017: invalid username/password; logon denied

If someone knows why...

I use the Docker file from https://github.com/deusaquilus/docker-oracle-xe that initialize the base at build time, then the 'docker run' is fast.
I run it by mounting an existing database:
docker run -d \ -p 32118:1521 \ -p 35518:5500 \ --name=oracle-xe \ --volume /your-data-folder/oracle-data:/opt/oracle/oradata \ oracle-xe:18c
May it help some of you.

We support prebuiltdb extension for the same purpose now. You can extend the base image with this extension to create the database and store the datafiles inside the image itself. So, you can run this extended image and it will start in couple of seconds. This extension is supported from 19c onwards.


Load backgrounds from scene files

Bevy has the capability to load entities from scene files. https://github.com/bevyengine/bevy/blob/main/examples/scene/scene.rs
Instead of hardcoding backgrounds like what was done in Amethyst Thetawave, we should define the entities in these scene files. Currently, there are gltf model files for the earth and sun located in the Amethyst Thetawave repo. Since everything else in the game (player, enemies, items, etc) is generated at runtime, the scene file should only contain these background model files.

Barriers are also constant throughout the game. They should also be defined in Bevy scene files.

Arena border barriers are also constant they can be defined in scene files as well.

It seems that at this point scene files aren't meant for/ aren't capable of handling entities at the complexity level needed. If this changes we will switch to scene files, otherwise we can store the data to define level backgrounds in .ron game data files.
Discussion:
https://github.com/thetawavegame/thetawave/blob/cdsupina/load_background_scene/src/main.rs


A version in Elixir

Basically the same as your Go version. https://www.bortzmeyer.org/files/tiny-resolver.tar . You are welcome to include it in your Github repository / article if you wish.

added to the README, thanks!


Fix docker-lab/helios#462 (Authentication against private registry.hub.docker.com repositories)

This change is

[Current coverage][cc-pull] is 51.82%

Merging [#473][cc-pull] into [master][cc-base-branch] will increase coverage by 0.39%

@@             master       #473   diff @@
==========================================
  Files            80         80
  Lines          2973       2981     +8
  Methods           0          0
  Messages          0          0
  Branches        417        418     +1
==========================================
+ Hits           1529       1545    +16
+ Misses         1308       1300     -8
  Partials        136        136

Powered by Codecov. Last updated by [cfeff16...65bf453][cc-compare]
[cc-base-branch]: https://codecov.io/gh/spotify/docker-client/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/spotify/docker-client/compare/cfeff16cdfa3b51a0e356ba0f54b90ac8f1f4a97...65bf4531e0e159c711ccbac18b1f98bc8ebdc2f4?src=pr
[cc-pull]: https://codecov.io/gh/spotify/docker-client/pull/473?src=pr

@elifarley sorry for the delayed review, but can you provide some more context on what fix docker-lab/helios#462 means?

Sorry, I should have typed something else:
"Fix spotify/helios#462".
Fixed now.

👍

@elifarley thanks!


unzip is required by fpm-cookery for zip files

see https://github.com/bernd/fpm-cookery/blob/master/lib/fpm/cookery/source_handler/curl.rb#L32

0.1.7 is cut with these two PRs.


wasm: js fallback

Feature request

What is the expected behavior?
WebAssembly should work on every plateform regardless of its actually support for wasm.
What is motivation or use case for adding/changing the behavior?
@lukewagner suggested it.
How should this be implemented in your opinion?
Webpack's runtime can detect the support for WebAssembly (or for specific features) and potentially fallback to a JS chunk (download it like we would do for wasm). This JS chunk is compiled AOT from the initial WebAssembly module using wasm2js (from binaryen).
On a side note, Webpack shouldn't parse the JS since it will be pretty big.
This should be opt-in since it requires the binary in the $PATH.
Are you willing to work on this yourself?
yes

yep, same opinion.
Relying on a binary isn't a good option. Is it possible to consume wasm2js as (wasm) npm module?

Ideally it would happen without the user having to setup anything, right?
Binaryen has a JavaScript port (binaryen.js), I don't know if it's part of their API tho.

Binaryen has a JavaScript port (binaryen.js), I don't know if it's part of their API tho.

That would be a good option. If it's not part of the API we may be able to send a PR.

Yes, agreed.
I don't think that's a priority right now.

Bump

Bump, not high priority

I'm not sure that's really relevant now because most browsers have WebAssembly support

I think so


Info box for emapis layer

We'd need also infobox for the "strukturverbesserungen" layers.

The basic chsdi info is now in the BOD.
CHSDI will still not be able to use it, since the layers have at the moment no topic. This will be corrected by Mario tomorrow

Layers are correctly in a topic and should behave exactly as every other chsdi layer


Publish release

Can you publish a release with the latest changes from May 8th? This is breaking for us after upgrading esbuild.

Done: https://github.com/marvinhagemeister/karma-esbuild/releases/tag/v2.3.0


[4.0] [QoI] Improve diagnostics of unsatisfied generic requirements

Description: Fixes a problem related to presence of InOutType in function parameters
which diagnostics related to generic parameter requirements didn't handle
correctly, and improves diagnostics for unsatisfied generic requirements
in operator applications, which we didn't attempt to diagnose at all.

Origination: Once String because a Sequence some of the diagnostics degraded, this patch attempts to correct this situation by improving diagnostics to generic requirements.

Risk: Low.

Tested: Added new tests, Swift CI.

Reviewed by: Doug Gregor, Jordan Rose.

Resolves: rdar://problem/33477726
(cherry picked from commit 242006706e76436fe2b7d63d2863c42c12fb5f9e)

@swift-ci please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 4d22e6f7efef01d553ef5b7c4779082410026ae2
Test requested by - @xedin

@swift-ci please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 4d22e6f7efef01d553ef5b7c4779082410026ae2
Test requested by - @xedin

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 4d22e6f7efef01d553ef5b7c4779082410026ae2
Test requested by - @xedin

@DougGregor please review for 4.0


ISPN-13421 Address doc review comments

https://issues.redhat.com/browse/ISPN-13421

@danberindei Shall I go ahead and merge this or would you like more approvals?

Go ahead and push the button @oraNod

thanks @danberindei


Updating Change basemap, Display a Map, and Display a Scene to use basemap styles

accidentally opened before ready.


update template to no longer use vault file

update template to use encrypted strings instead of vault file

is there much to do here? Today, this template doesn't include instructions on how to encrypted the files in vaults/.
This issue might be resolved with some instructions on how and why to encrypted values and not whole files.

Good practices goes into more details and some issues that vaulted files can cause

well I am not finding it in there now, I will try and find out if it is still a thing or if I can just close this

I linked to Ansible Tips and Tricks, which discuss this topic, in my first
comment.
(I'm not sure with Automation Good Practices covers this, too)
On Mon, Jul 8, 2024, 15:13 David Danielsson @.***>
wrote:

well I am not finding it in there now, I will try and find out if it is
still a thing or if I can just close this
—
Reply to this email directly, view it on GitHub
https://github.com/redhat-cop/aap_configuration_template/issues/13#issuecomment-2215174015,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMKE6TWWSLCUP5HPIG3ZTLZLLXGBAVCNFSM6AAAAABKKK52JOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJVGE3TIMBRGU
.
You are receiving this because you commented.Message ID:
@.***>


How can I deploy skywalking 6.6 in k8s

Please answer these questions before submitting your issue.

Why do you submit this issue?
[x] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?
--- I want deploy sw6.6 in k8s Cluster，not use helm,I can't found 6.6skywalking's image address，can you help me ?

Bug

Which version of SkyWalking, OS and JRE?

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

Requirement or improvement

Please describe about your requirements or improvement suggestions.

Sorry, this hasn't been provided. @innerpeacez has network issue because of the public health situation. Most configurations should be as same as the old release for most features.

You mean that the official doesn't provide 6.6 skywalking image  now?  Can you describe what is network issue in detail?

Image yes, helm no.

It is a personal network issue, he couldn't test and then, he could not start the official apache release process.

I see,thanks

notice you don't intend to use helm to deploy skywalking into Kubernetes
cluster, Can you share what's your concerns about helm?
JCchenxiang<EMAIL_ADDRESS>于2020年2月11日周二 下午4:12写道：

I see,thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/skywalking/issues/4347?email_source=notifications&email_token=AAO6UWIZIT265WE73TQ43DLRCJMVFA5CNFSM4KS3TZ22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELLQ2JI#issuecomment-584518949,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAO6UWOBKQOINNHCC5ZICMLRCJMVFANCNFSM4KS3TZ2Q
.

--
Hongtao Gao
Apache SkyWalking && Apache ShardingSphere
Twitter, @hanahmily

Release vote passed. @innerpeacez will post the announcement soon.