Config files used during Build, Deploy and Launch ...

I have started my "deep dive" into ASP.Net Core by creating an EMPTY web app (website) project that serves only static files - no MVC, no Razor, nothing fancy.   I use COMMAND line tools (msbuild) to compile (build) the project, and to deploy it to a local test or production directory.  I then use the "dotnet" command to launch the website.  (Using command line tools makes documentation easier than trying to grab screen snapshots of GUI tools that seem to change each year).
My specific questions are posted on StackOverflow at:
https://stackoverflow.com/questions/58940101/asp-net-core-launch-website-via-visual-studio-vs-command-line
In my opinion, the best way to tackle the various configuration files is by showing a complete cycle for a specific platform and hosting environment, for example:
WINDOWS SPECIFIC:
BUILD, DEPLOY AND RUN A WEBSITE LOCALLY USING IIS EXPRESS.

Show command(s) and config files needed to build the website
Show command(s) and config files needed to deploy the website
Show command(s) and config files need to launch the website

BUILD, DEPLOY AND RUN A WEBSITE USING AZURE APP SERVICES

Show command(s) and config files needed to build the website
Show command(s) and config files needed to deploy the website
Show command(s) and config files need to launch the website

BUILD, DEPLOY AND RUN A WEBSITE USING AZURE VIRTUAL MACHINE (IIS)

Show command(s) and config files needed to build the website
Show command(s) and config files needed to deploy the website
Show command(s) and config files need to launch the website

LINUX SPECIFIC:
(as above)
As icing on the cake, please provide a link that describes the various options / nodes available in each of the config files -- currently, trying to find what options and values are even allowed in the various config files has consumed a large amount of time; and in most cases, I have been finding the answers via StackOverflow rather than in the official documentation -- which is very disappointing.
Thank-you for your consideration.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0eb4d762-3910-2c57-8741-3306c15537b6
Version Independent ID: ba2254a0-ea8e-9b28-e94b-edd0fc58c043
Content: Configuration in ASP.NET Core
Content Source: aspnetcore/fundamentals/configuration/index.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @guardrex
Microsoft Alias: riande

Thanks for the feedback and questions @bdcoder2. I’m just off to 🛌, so I’ll get back to you on this in the morning.

We're collecting feedback on how configuration files are covered. There have been a few inquiries on the subject, but not many to my knowledge from watching the issues come in.
Today, there are many configuration "files" for aspects of configuration:

App
Host
Server/service
Tooling

Thus far, we've adopted the strategy of covering configuration files (in the broadest sense) with the technology to which they apply. This makes sense owing to the fact that ASP.NET Core/.NET Core is cross-platform and cross-tooling ... there are many platforms and many tools now, thus many files.
To get a full handle on configuration files, one should access the documentation areas where those files apply. For example, web.config is covered in the IIS/ANCM section. App configuration files are covered in this topic. launchSettings.json is covered where VS is addressed (i.e., many places throughout the docs).
We'll continue to collect feedback, and perhaps management will one day ask for some sort of explicit coverage of most configuration file types in one spot.
You asked two specific questions ...

I cannot find the port numbers in any configuration file (.json or web.config) within the published directory - so where are these port numbers coming from?

Ports 5000 and 5001 are the defaults for the Generic Host URLs and covered in .NET Generic Host: URLs.

How can I configure / control which ports are used when the website is published to either a test or production environment (using command line tools)? - is this done via a .pubxml file? If so, what node(s) must be included within the .pubxml file? ... Or is this done via some other config file when the website is launched, i.e.: web.config?

This is where configuration depends on the scenario, and you didn't describe your environment/approach completely. You seem to be deploying to IIS for a local development experience. Ordinarily, I'd point you to Development-time IIS support in Visual Studio for ASP.NET Core, but you said "command-line tools." Therefore, take a look at the Publish an ASP.NET Core app to IIS tutorial. You'll see there that the port is set in the binding in IIS as usual. There's nothing for you to set for the app in the base/default scenario.
When using the in-process hosting model (the default), the IIS binding is the app's port. When using the out-of-process hosting model, the ANCM (ASP.NET Core Module) forwards requests from IIS (again, with the port determined by the app's binding in IIS) to the app on a random port, which you obviously don't interact with. For more info on the hosting models, see Host ASP.NET Core on Windows with IIS.
I'm going to close as answered, but we'll keep an :ear: open for more feedback on configuration.

@guardrex - Thank-you.  I very much appreciate the time you have taken to explain things; and your patience with a newbie such as myself.
As an engineer, let me illustrate the difference between documentation of years gone by compared to today.  Lets pretend 30+ years ago (I know, hard to imagine), ASP.NET Core was released, and I just cracked open the manual entitled "ASP.NET Core 3.0 - Windows" (note the clarification; this particular manual would be Windows specific).   Others might crack open a manual entitled "ASP.NET Core 3.0 - Linux" or "ASP.NET Core 3.0 - iOS" -- the point being, right from the top, the docs should be platform specific.
Moving forward in the Windows specific manual, I find an an "Introduction".  I probably would have found another section entitled "Configuration Files", One of the files described would be "launchsettings.json".  The manual would describe the following:

What launchsettings.json does.
The process(es) or tools that read launchsettings.json
The valid sections and values that launchsettings.json may contain.

Nice, simple, done.
Fast forward to the here and now, and I have to jump around docs.microsoft.com, stackoverflow.com and about a dozen other blogs and articles to piece together the above; in addition to reading about other platforms or settings that do not even apply to my environment.
For example, I have yet to find a complete schema for the launchsettings.json file - instead I keep finding code examples that make use of various "sections" of the launchsettings.json file.  A typical search scenario goes as follows:
Google: Site:docs.microsoft.com launchsettings.json schema
Result:
https://docs.microsoft.com/en-us/visualstudio/containers/container-launch-settings?view=vs-2019
The article describes a “Docker” section; great, but I am not using Docker ...  lets try ...
Google: Site:docs.microsoft.com launchsettings.json logging section
Result:
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/logging/?view=aspnetcore-3.0#configuration
Logging section described! - great, now how about a section for controlling the port numbers?
... off I go to Google, StackOverflow, blog, etc.
Had a single article described the various sections that are available in launchsettings.json I would have been able to answer every question I have when it comes to configuration.
Please understand, I am not trying to belittle the good work you are doing -- I am just saying that better ways have existed when it comes to technical documentation and I hope Microsoft might consider adopting some of those tried and true methods.    In the end, I think it would save everyone a LOT of time.
Thanks again!


Add documentation for using text labels in datasets

Add documentation for the function get_text that retrieves text labels from the stored dataset.
Function definition:- https://github.com/activeloopai/Hub/blob/master/hub/collections/dataset/core.py#L655
Examples of usage:-
Pytorch: https://github.com/activeloopai/Hub/blob/master/examples/fashion-mnist/train_pytorch.py#L95
Tensorflow: https://github.com/activeloopai/Hub/blob/master/examples/fashion-mnist/train_tf_gradient_tape.py#L84

Am i need to just add the comments on function working want to work.

Assigning you to the task.
You can add it after Combine here https://github.com/activeloopai/Hub/blob/master/docs/source/concepts/dataset.md

Thanks for assigning

Can I do this?


RNN-cells interface has changed

It seems that the way to import the RNN cell has changed:
Traceback (most recent call last):
  File "char-rnn.py", line 192, in <module>
    QueueInputTrainer(config).train()
  File "/home/patwie/git/tensorpack/tensorpack/train/base.py", line 58, in train
    self.setup()
  File "/home/patwie/git/tensorpack/tensorpack/train/base.py", line 130, in setup
    self._setup()
  File "/home/patwie/git/tensorpack/tensorpack/train/feedfree.py", line 101, in _setup
    cost, grads = self._get_cost_and_grad()
  File "/home/patwie/git/tensorpack/tensorpack/train/feedfree.py", line 47, in _get_cost_and_grad
    self.model.build_graph(actual_inputs)
  File "/home/patwie/git/tensorpack/tensorpack/models/model_desc.py", line 108, in build_graph
    self._build_graph(model_inputs)
  File "char-rnn.py", line 72, in _build_graph
    cell = tf.nn.rnn_cell.BasicLSTMCell(num_units=param.rnn_size)
AttributeError: 'module' object has no attribute 'rnn_cell'

What do you think about an additional repository https://github.com/tensorpack/data with dummy data, to also test this example using Travis-CI? It seems that in the nearby future they will change a lot of APIs before the final v1.0.
see:
https://github.com/tensorflow/tensorflow/commit/b8101a2b0a7ff1b96999c8e7ad213d1f36b4a4ab
They make it hard to maintain examples. Hopefully, their release of v1.0 will fix that.

You'll also need to fix tf.nn.rnn, replace it by tf.contrib.rnn.static_rnn.
Maybe it's better to write several dummy training scripts containing lots of features for testing. This may avoid downloading mnist or prepare dummy data for examples. What do you think?

Maybe it's better to write several dummy training scripts containing lots of features for testing. This may avoid downloading mnist or prepare dummy data for examples. What do you think?

Do you really want to maintain additional examples without any function? Maybe just putting some images (some of image2image produced to not violate copyrights) and a small textfile into a repo and wget. The release to run the real examples on very small datasets.
This will require a more flexible testing with teardown to clean up dirs such as train_logs

I'm not sure what's the best way. Dummy data would work for some of the examples, but for others like mnist, it has to download the whole dataset.
But maybe we'll only test those that work with dummy data? Sounds OK.


isolated wasm executor

We need a way to isolate wasm executor for different chopsticks instance in memory.
Right now, if there are multiple chopsticks instances, they will share a worker, which is fine, and the same wasm executor.
And then if one of the execution got panic (e.g. #551), the other execution will also panic. Most likely because the global panic handler is been modified by the panicking execution.

less important after #565 as it really shouldn't panic anymore


feature request: transparency -> white

For images with transparency, the dithering algorithm currently treats this as black, which is pretty ugly - it would be good to assume that this should be white (or provide an option for this)

I'm not really familiar with the details of the Apple image decoder. I just ask it to decode the incoming image and don't distinguish from different types / or alpha info. Do you know how to implement this change?


Verify license boilerplate on all files with CI/CD

All of the project files must be verified as having the APLv2 license boilerplate on each file. This should be done automatically with pre-commit hooks or something similar. It must be automatic at least for stable release, but more ideally for every commit and PR.

Please don't go with precommit hooks.
I believe that adding apache rat maven plugin in the pom is enough. You can activate it in the verify phase for instance

Thanks for the pointer, I'll do that instead!

The main branch now has the apache rat maven plugin running on all modules for all Java source files.
The build will fail if it is attempted with a missing license header.
Generated directories are excluded, as these are derivatives of other licensed content.


Not possible to record videos when running tests in parallel

Hi
I'm running playwright scenario's with cucumber-js. One of the cucumber options is to run tests in parallel. When running scenario's in parallel no video captures are created.
Using:
"playwright": "^0.11.1-next.1583993157193",
"playwright-video": "^0.5.0",
"cucumber": "^6.0.5",
Regards
Marco

@mortelee Thanks for reporting this issue, it should work in parallel. Do you mind running it with the DEBUG=playwright-video* environment variable and including all the logs.

Will keep you up to date. Can be next week unfortanetly

@mortelee just want to confirm you have FFmpeg installed?

I've used "npm i playwright@next playwright-video ffmpeg-static"

In my package.json I've the following debug entry:
"debug": "node --inspect-brk=1337 --nolazy node_modules/cucumber/bin/cucumber-js --tags @debug"
In my launch.json I've added:
"DEBUG": "playwright-video*"
and
"logging": {
"trace": true,
"traceResponse": true,
"engineLogging": true
}
With this config everything works fine.
When I add --parallel 2 to the debug entry in package.json, the debug session does not do anything . Turning on exceptions breaks in a lot of places but does not make sense to me.

Successful run without parallel option:
Document1.txt

I've tried to create a small demo app (based on the code that I already had) to show the problem.
After "npm install" I see that in utils.ts (playwright-video) CRBrowserContext cannot be found.
What am I doing wrong?
 Something in my own source code.

Glad to hear you figured it out 🙏. Let me know if you run into further issues.


cuSOLVER wrappers

It would make sense to add a wrapper around cuSOLVER.  Note that the cudatoolkit 7.5 conda package (as of this issue) does not include the library and needs to be updated to include it.  The cudatoolkit 8.0 package in the numba channel on Anaconda Cloud does already have cuSOLVER.  (conda install -c numba cudatoolkit).

FYI, I have some BSD-licensed CUSOLVER bindings in scikit-cuda that could potentially be modified for this purpose.

Oh hey, I didn't realize you were the scikit-cuda developer!  We would be very interesting in figuring out where we could collaborate, given the high overlap between our projects.
To be honest, pyculib exists mainly so that both CPU memory NumPy arrays and GPU memory Numba device arrays can both be passed to these libraries through a single API.  One thing on my wishlist is to figure out a simple protocol for Python objects that encapsulate GPU memory ndarrays to interoperate between libraries like Numba, PyCUDA, PyTorch, TensorFlow, etc.  That would allow a library wrapper like scikit-cuda or pyculib to exist independent of any of the particular GPU python projects.

Sure - collaboration would be great! We can discuss further on some other channel (email, a separate git issue, etc.) - let me know.
By "protocol", I assume you are suggesting something that would convert between different GPU-based array backends for Python rather than provide a canonical backend?

Yeah, I borrow the term from the Python buffer protocol: https://docs.python.org/3.6/c-api/buffer.html
A GPU version of that would allow any Python package to determine the basic data type, shape, and layout of a GPU device allocation, along with a way to get the device pointer.  It's unlikely that all these projects would (or should) agree on a single container object, but they all could easily expose some Python attributes on their own device allocations that would allow other packages to use them.

Hi all, thanks for this discussion. If you need help in porting cuSOLVER to the pyculib, I can help. Now I want to use cuSOLVER in my python application, so I can try to adopt it based on pyculib api.

We'd be happy to review a PR for this, and it looks like you could base it on the code in scikit-cuda.


ntr increased proteasome localization to the nuclear periphery

standard def
PMID:16096059

increased proteasome localization to nuclear periphery FYPO:0005217

edit file: 8bb855d981e006750a0fed14cfb4fd3a85a1c59f
release: 8bb855d981e006750a0fed14cfb4fd3a85a1c59f


[Feature Request]: Stripe-Payment Integration for invest option

Is your feature request related to a problem? Please describe.
Yes, the current project is lacking backend integration, which is crucial for processing payments effectively. Additionally, there’s no investment payment integration in place. This means that we can't handle payments or transactions as required, which is a significant issue for our project's functionality and user experience.
Describe the solution you'd like
To address the issue, I propose integrating Stripe as our payment service. Stripe provides robust support for card-based payment options, which will enable us to process transactions securely and efficiently.
Additional context
I would like to add this feature into the project. I've worked on this earlier in my projects and here is the representation on how this feature enhance this website as well

https://github.com/user-attachments/assets/94f821c2-4254-4fd3-b048-85917a180494

Hey, @Priyaaa1  I'd like to work on this, i request you to assign me the issue under GSSOC'24 . The code is all ready to make a pull request..!

@Priyaaa1 kindly assign me !

Hey, @Priyaaa1 I've raised PR!


dd and yyyy inverted for date input

Only Parenthesis inverted, should be typed mm-dd-yyyy and displays as yyyy-mm-dd


K8s API error patching CRs is not caught

Description
K8s does not support patch strategy for CRs and kubectl des return an error when trying to patch a CR. But for an unknown reason the reconciler does not.
Expected result
Error is returned when patching a CR and process is stopped.
Actual result
Reconciler returns success and CR does not have the changes applied.
Steps to reproduce

Deploy Kyma into a cluster
Upgrade a component containing a CR (e.g. monitoring) having changes on the CR
Check the CR after the update and see that it is not updated.

Troubleshooting
Issue was discovered in: #662
See https://github.com/kubernetes/kubernetes/issues/97423

We are facing some weird error messages after Helm call was trying to patch a CR:
#1: unable to build kubernetes objects from current manifest: unable to recognize "": Get "https://api.c-64c814d.stage.kyma.ondemand.com/api?timeout=32s": dial tcp: lookup api.c-64c814d.stage.kyma.ondemand.com on <IP_ADDRESS>:53: no such host
#2: Failed to get manifest for component 'monitoring' in Kyma version '2.0.0': failed helm client render: loader failed to load helm chart: Chart.yaml file is missing

2022-01-14T15:30:36.676+0100	DEBUG	invoker/localinvoker.go:107	Local invoker is updating operation (schedulingID:local--64506ecc-f620-446c-80e3-135f3a312edf/correlationID:local--0311a26a-a048-40aa-ab97-ebea3c83e1df) to state 'failed': Failed to get manifest for component 'monitoring' in Kyma version '2.0.0': failed helm client render: loader failed to load helm chart: open /Users/d069409/.kyma/sources/2.0.0/resources/monitoring/.helmignore: too many open files

We assume these issues are side-effects of the failed patch call.

This issue is probably obsolete since #678 is in place.

Has to be verified if this was an error at all. Issue was probably caused by wrong call of the Helm Client when processing CRDS.
@clebs  / @ruanxin  - can you confirm this assumption? If yes, let's close this issue as obsolete.

Yes, that was the case. This can be closed.


Facebook SDK 4.XX

There were changes in the facebook sdk since the version used in the CognitoSyncDemo (3.20).  Will the samples be update for the latest facebook SDK (4.5.1)?
ex.  com.facebook.Request is now com.facebook.GraphRequest (src file:  com.amazonaws.cognito.sync.demo.MainActivity.java)

Thanks for reporting this.  We will definitely update our samples soon!  Will leave this issue open until we have pushed changes.

Late in closing, but we upgraded to the latest FB SDK ages ago (see the Gradle file in the sync demo)


Regression: rubocop 1.45.0 crashes when we use rubocop-i18n

After upgrading rubocop 1.45.0, rubocop crashes:
$ bundle exec rubocop
NoMethodError: private method `begin_investigation' called for #<RuboCop::Cop::I18n::RailsI18n::DecorateStringFormattingUsingInterpolation:(...snip...)>
.../rubocop-1.45.0/lib/rubocop/cop/commissioner.rb:100:in `block in begin_investigation'
.../rubocop-1.45.0/lib/rubocop/cop/commissioner.rb:99:in `each'
.../rubocop-1.45.0/lib/rubocop/cop/commissioner.rb:99:in `begin_investigation'
...

This seems to be introduced at 3c9c49416c0fd3db077cec8410cb1280f6771dbb.
Before:
@cops.each { |cop| cop.send :begin_investigation, processed_source }

After:
@cops.each do |cop|
  cop.begin_investigation(processed_source, offset: offset, original: original)
end

RuboCop::Cop::Base#begin_investigation is moved to public section,
but RuboCop::Cop::Cop#begin_investigation is still in private section.
rubocop-i18n's cops are extended from RuboCop::Cop::Cop instead of Base.

Expected behavior
Rubocop works with no errors.
Actual behavior
Rubocop crashes.
Steps to reproduce the problem
$ bundle init
$ bundle add rubocop rubocop-i18n
$ echo "require: [rubocop-i18n]" > .rubocop.yml
$ bundle exec rubocop

RuboCop version
1.45.0 (using Parser <IP_ADDRESS>, rubocop-ast 1.24.1, running on ruby 3.1.3) [x86_64-linux]
  - rubocop-i18n 1.12.0

Same issue in our build/test pipeline. It's blocking our ability to merge code. Can be this fixed soon please?


Change effective privileges in some cases

Especially users having "high" roles but being restricted to some projects do have effectively access to many things they shouldnt have. Especially the global settings like workers, encoding profile (contents/properties) etc. should be inaccessible to a user that is restricted to projects.

@a-tze With the new restricted superuser role, is this still an issue?

@jjeising Yes. It seems that restricted superusers can create new users and give them access to other projects or even admin privileges.

Looks good


synonym replacement

Information
The question or comment is about chapter:

[ ] Introduction
[ ] Text Classification
[ ] Transformer Anatomy
[ ] Multilingual Named Entity Recognition
[ ] Text Generation
[ ] Summarization
[ *] Question Answering
[ ] Making Transformers Efficient in Production
[ ] Dealing with Few to No Labels
[ ] Training Transformers from Scratch
[ ] Future Directions

Question or comment
On p272, the authors said "we'll focus on using synonym replacement.....", but on p273 example was given using naw.ContexualWordEmbsAug() instead of naw.SynonymAug(). Can the authors explain the difference?

Hi @JingchaoZhang thank you for spotting this! The text is indeed unclear here and we should not have used the word "synonym" to refer to using the masked language model to generate new substitutions. We'll add it to the book's errata.
Thank you!


Features/17 import 2009

there should be 2008 and 2009, there might be some needed update
I'm open to suggestion

Backported by @JosePaumard
Fixup by @PerfectSlayer (event attachments restored)


feat: support for did element

addes support for did element and tests
closes #138

Signed-off-by: sudesh.shetty<EMAIL_ADDRESS>

@sudeshrshetty  after this PR is merged we need to add new profile in sandbox https://github.com/trustbloc/edge-sandbox/blob/master/test/bdd/fixtures/scripts/vcs_configure.sh#L42
https://github.com/trustbloc/edge-sandbox/blob/master/cmd/issuer-rest/static/index.html#L39

@sudeshrshetty after this PR is merged we need to add new profile in sandbox https://github.com/trustbloc/edge-sandbox/blob/master/test/bdd/fixtures/scripts/vcs_configure.sh#L42
https://github.com/trustbloc/edge-sandbox/blob/master/cmd/issuer-rest/static/index.html#L39

Sure

I'm not a golang expert, but the JS parts look correct. Great work!

Thanks @OR13


What can BlockLauncher do in the future?

Now official support texture pack in MCPE 0.15.0.The most important reason why we still use BlockLauncher is that the MOD,ModPE and Addons.
In the future,official will support more just like the PC JAVA version.l think it's necessary for BlockLauncher to have a new function.
I suggest that we can have a new kind of package that can contains ModPE,Mod,Addon,Texture pack,Game Worlds and Skins.It's easy for Player who want to play games made by others.
And more,we can develop an APK to encrypt this package.In this way,this package can be only used on BlockLauncher and authors will not be afraid of their Worlds,Mods and so on be stolen.
That is my suggestion.
However my English is not good.If there are any grammar mistakes,please ignore it. :)

We still need blocklaucher for the texturepacks!Minecraft is being stingy and you have to buy them and no custom neither :/

@VickyGaming in the /games/com.mojang folder, create a folder resource_packs
in that folder, extract the texture pack you want to use.  It needs to be 0.15 compatible.  From there you will be able to use the native texture pack menu in Vanilla Minecraft to load that texture pack.
We will still need the TP loading from BL for mods that add new items.  If BL still supports full texture packs, I'll probably load them through BL so I don't have to manage my TP in two places nor worry about extracting them all the time.  I use a custom one where I manually merged 4 TPs together, so a FULL load is important to me and I won't update my TP until I find out if BL does a FULL load or not.
Check www.mcpedl.com there is a good guide on there to setup Vanilla Minecraft with a 0.15 compatible TP.

I still don't understand😂😂😂

@VickyGaming did you look on MCPEDL.COM?
http://mcpedl.com/how-to-install-minecraft-pe-texture-packs-for-android/
I'm not sure I can make it simpler than that.

@zedman2000
Excuse me, l don't know what is TP loading?
To add a new item's texture, we can use the modpkg.

@XFY9326 texture pack.  :-)
Textures can come into the game's memory many ways.  Using 0.15 there is now an official way.
Essentially I was saying:
*drop support for FULL texture packs so Zhuowei doesn't waste time on that code - officially it is supported now
*continue/enhance the item textures - as you said, these can be in a modpkg, or .zip as it is now.  I personally like the non-modpkg due to WHEN BL loads the textures my try/catches can cause false triggers.  I also like the NON-modpkg because then the texture pack icons are displayed and you can see them nicely listed.
My point above mostly stems from that Zhuowei should do what ever is easiest to maintain.  The more time he spends on fixing issues due to complex configurations for texture packs, the less time he has to add new features or correct bug fixes as Minecraft PE evolves.  For instance, there are many functions that need constant attention.  I am guessing because while the function name that Zhuowei hooks into does not change, the logic inside does -  which then requires an update to BL to allow the MODPE community to keep using that function.  The more optimized his time is, the better Block Launcher can become!

I'll put it in English.
Get a file manager app or connect your phone to a PC with a USB cable.
Next, head over to your games folder. Inside, find the folder that says:

com.mojang

In there, create a folder named:

resource_packs

This "resource_packs" folder is where you will move your texture packs. If the texture pack is a .ZIP file (which it most likely is), extract it right in the "resource_packs" folder. Delete the .ZIP once it extracted so you can save a bit of memory.
Now open up Minecraft PE and head to the options. Below the "Third Person View" option, you can choose which texture packs to install. Make sure you move your own texture pack to the right, so the game loads it.
And that should be it. If it doesn't work, then it's probably because the texture pack hasn't been updated to 0.15.x.

If this is resolved, please close this so Zhouwei does not spend time reading this through only to realize he has taken time to review something he needn't have.  Again, we need to be the best community we can to help him spend MORE time on the guts of BlockLauncher, so that we do NOT spend his time dealing with paperwork.  I'd MUCH rather he fix functions and get a new version of BL out to us, not sit here for 2+ days clicking close on issues that need to be closed.
Thanks!

@XFY9326 that last message was meant for you.  Sorry, I forgot to tag you to make sure you get an alert.


[Feature][Connector-V2][Jdbc] Add OceanBase catalog

Purpose of this pull request

Add OceanBase catalog in jdbc connector, close #5076.
Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

Tested on my dev environment and all tests passed.

@EricJoy2048 PTAL

I tried to enable the oceanbase it case with the new docker image, and there are still some issues about the container startup, which I will fix in another pr. The label is removed by the bot, PTAL again @EricJoy2048

The ci failure is not related to this pr. I tried the case JdbcVerticaIT on my dev machine and it executed successfully, it's a little weird.
https://github.com/whhe/incubator-seatunnel/actions/runs/6465553249/job/17560811546

https://github.com/whhe/incubator-seatunnel/actions/runs/6492005114/job/17630374248


question about more than 4 stepper

Hi Egor. Thank you for the work done. If it doesn't bother you, help me with advice on how to expand this firmware to work with a little more motors. everything works great with 4 stepper motors. I haven't figured out the home assistant yet, but I hope I'll set it up somehow. Is it possible to make a connection via a pcf8574 type expander over the i2c bus, I just need a slightly larger number of steppers. How can I increase the number of motors in the interface? To be honest, I want to connect 16 steppers, and I don't want to occupy 4 esp 32 with them. But there is a necessary number of expanders. There are examples of connecting stepper motors via i2c on the network, but only for arduino, and unfortunately I didn't find anything with the esp. Thank you in advance for the answer.

Hi!
Glad to see it's useful for you. Feel free to give a star to this repo ;)
I've not tried this, but it looks possible with some changes.

From interface side you should change that line at main.cpp:
https://github.com/eg321/esp32-motorized-roller-blinds/blob/c73b0099cf9474bf3646499c489f52eed5b7ea85/src/main.cpp#L2

It will be enough to update web interface with needed bars and configurations for each stepper. MQTT part also will be updated automatically.

Main issue will be adapting CheapStepper library to work with i2c expander. It doesn't know about expanders and does not know how to work with them. As quick dirty hack, you can replace pinMode with pcf8574.pinMode (or what library you'll use) and digitalWrite with PCF8574.digitalWrite and so on.

Also do not forget to update this function:
https://github.com/eg321/esp32-motorized-roller-blinds/blob/c73b0099cf9474bf3646499c489f52eed5b7ea85/src/Helpers/StepperHelper.cpp#L26

And that's it.
If you'll find better way, please tell me. I'll try to support that. This definitely can be useful.
Please keep us updated about results. It's quite interesting experiment.

Hi. Thank you for your prompt reply. I will try your advice. I'm just  starting to learn esp 32.  I have never done coding at all, I will study it slowly. Most of the connected sensors and modules are made in node-red by copying and pasting. Here come out tasks that no one has done before. If it fails,  will have to temporarily donate 4 esp. I will try to rework your project as soon as I understand at least a little what to do)


Editor freeze on importing wav file

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Arch linux, master branch
Issue description:
If you add some *.wav file to project, engine will reimport it. And stops on it. Only killing of the process can help.
In debug I see, that it take Segmentation fault exception in object.cpp in _predelete() method because of "this" is NULL.
Stacktrace:
Object::_predelete object.cpp:384 at
predelete_handler object.cpp:1774 at
memdelete memory.h:107 at
unregister_gdnative_types register_types.cpp:252 at
unregister_module_types register_module_types.gen.cpp:147 at
Main::cleanup cami.cpp:1714 at
main godot_x11.cpp:55
I think. that something in process of importing wav file brake the engine and it tries to finish process.

Happens to you with any wave file? Even a really small one?

@marcelofg55 Yes, I tried on sound_coin.wav from platformer demo project. It is only 63Kb. And on other files from jsfxr.

This has been happening to me too, both on importing and trying to re-import .wav files.


Enhancement: Integrate treasury to collective and membership

Integrate pallet_treasury with collection and membership

I think, I have included this on PR #20

Thanks, but we need to separate the council for treasury and council for sudo/technical.  I will just make the adjustments.  Thanks much.  We will first do the thorough test on the collective and membership before we move on to the next issue.

This is done: https://github.com/Xode-DAO/xode-blockchain/commit/90bff63a4763c304ca4e6a5cf2d5d1fa815e191b


Update Composer dependencies (2022-03-05-00-06)

Visual regression test passed!
View the visual regression test report


Refactor Idempotency code snippets

Hi @heitorlessa. I'm already working on it and will send a PR.


core[patch]: introduce ToolMessage.status

would also add to ChatBedrockConverse

Could be worth some description in the PR summary of the motivation for the new attribute. e.g.,

Supported by certain providers (Anthropic, others?)
Enables more precise control in orchestration (e.g., can force certain behavior or constrain agent actions if a tool errors)
???

main motivation is first point. its part of the api of some providers (bedrock and anthropic) and currently our messages aren't expressive enough to match those apis

@baskaryan could you update the PR summary to explain the motivation. Are those APIs taking the tool status as an input?


Support 7-zip

Issues to fix when implemented.

[ ] https://github.com/AdamRaichu/vscode-zip-viewer/issues/48

https://github.com/nika-begiashvili/libarchivejs seems promising.


Fix example code.

cc @paramaggarwal

Ah good catch. Could you remove the multiple=false bit - it's not needed.

@paramaggarwal Done!

Thanks!


The current TensorFlow lite version cannot be built with Visual Studio 2017.

System information

OS Platform and Distribution: Windows SDK version 10.0.17763.0 to target Windows 10.0.19042
TensorFlow installed from (source): master, commit 67a9764695429fc5963aeeb905526bfe5af45739
TensorFlow version: 2.4?
CMake version: 3.18.5
Compiler version: Visual Studio 2017 (MSVC 19.16.27045.0)
CUDA/cuDNN version: 10.2, 11.1
GPU model and memory: GeForce 1080 Ti

Describe the problem
The current TensorFlow lite version cannot be built with Visual Studio 2017.
Provide the exact sequence of commands / steps that you executed before running into the problem
D:
mkdir TF
cd TF
git clone https://github.com/tensorflow/tensorflow.git src
mkdir build
cd build
cmake -G "Visual Studio 15" -A x64 -D CMAKE_DEBUG_POSTFIX:STRING=d -D CMAKE_INSTALL_PREFIX:PATH=D:\TF\install -D TFLITE_ENABLE_GPU:BOOL=OFF -D GIT:FILEPATH=D:\dev\Tools\GIT\bin\git.exe D:\TF\src\tensorflow\lite
msbuild INSTALL.vcxproj /maxcpucount /nodeReuse:false /nologo /p:Configuration=Debug

Any other info / logs (translated from german)
       "D:\TF\build\INSTALL.vcxproj" (default target) (1) ->.
       "D:\TF\build_BUILD.vcxproj" (default target) (3) ->.
       "D:\TF\build\tensorflow-lite.vcxproj" (default target) (4) ->
       (ClCompile target) ->
         D:\TF\src\tensorflow-lite\kernels\elementwise.cc(299): fatal error C1001: Internal compiler error. [D:\TF\build\tensorflow-lite.vcxproj]

Project file built with Visual Studio:
42>D:\TF\src\tensorflow\lite\kernels\elementwise.cc(299): fatal error C1001: Internal compiler error.
42>(Compiler file "msc1.cpp", line 1518)
42> Simplify or modify the program in the environment of the items listed above. Select
42>Use the "Technical Support" command in the "Help" menu of Visual C++,
42>or open the technical support help file for more information.
42>INTERNAL COMPILER ERROR in "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\HostX86\x64\CL.exe".
42> From the Visual C++ Help menu, click Technical Support,
42> or open Technical Support Help for more information.

Can you check our Visual Studio compatibility matrix for each TF version at https://www.tensorflow.org/install/source_windows#tested_build_configurations ?
Thanks

Hi bhack,
the list gives an overview of TensorFlow, not TensorFlow lite. For lite a C++11 compiler is supposedly sufficient as it can be found e.g. in the Micro documentation (https://www.tensorflow.org/lite/microcontrollers#supported_platforms). Also, there is a CMake build instruction https://www.tensorflow.org/lite/guide/build_cmake without any restrictions.


Built in changelog and voting system for new features

[x] change log page
[ ] Automatically show the changelog page to users who haven't played since a change
[ ] Allow users who have beaten 10 or more levels to vote on future changes
[x] Display upcoming changes

Changed mind, any user account can vote, and the changelog is not automatically shown.


when do we divide by met_batch_size?

which one is the correct one to be doing:
            # Accumulate gradients wrt meta-params for each task
            qry_loss_t.backward()  # note this is more memory efficient (as it removes intermediate data that used to be needed since backward has already been called)
            # (qry_loss_t / meta_batch_size).backward()  # note this is more memory efficient (as it removes intermediate data that used to be needed since backward has already been called)

ref: https://stackoverflow.com/questions/66606540/when-does-one-divide-by-the-meta-batch-size-for-maml-during-meta-learning

this is not exactly related but if you have the grads field not being populate see this: https://github.com/facebookresearch/higher/issues/129


[WIP] Save unique_set_size when saving process info

Why?  USS is a more reliable mechanism for tracking workers with runaway
memory growth.  PSS is great, until the server process that forks new
processes grows large. As each new worker is forked, it inherits a share
of the large amount of the parent process' memory and therefore starts
with a large PSS, possibly exceeding our limits before doing any work.
USS only measures a process' private memory and is a better indicator
when a process is responsible for allocating too much memory without
freeing it.
Depends on:

[ ] https://github.com/ManageIQ/manageiq-schema/pull/139
[ ] https://github.com/ManageIQ/manageiq-gems-pending/pull/317

@miq-bot add_label gaprindashvili/yes

@miq-bot add_label enhancement

@gtanzillo @Fryguy I tested this PR along with it's two dependent PRs in schema and gems pending.
This only stores USS in the database.  It does NOT log it, show it in rake evm:status or change the worker monitor code to use USS for the threshold checking.  Those will be done next.

Merged both dependent PRs.

@Fryguy This is finally 💚   🎉

Gaprindashvili backport details:
$ git log -1
commit f37cf886dd953f6a2f5e73d9b9a4258a3f00e384
Author: Oleg Barenboim<EMAIL_ADDRESS>Date:   Fri Dec 1 13:41:04 2017 -0500

    Merge pull request #16569 from jrafanie/add_uss_to_servers_workers

    Save unique_set_size when saving process info
    (cherry picked from commit d50a4d9d22b48dbb888f586d549f4ad7b566c456)


Question about train dataset and test dataset split

In the paper, you mentioned '(70000 scenarios after filtering) are further split into a training dataset (50,000 cases) and a non-overlapping test dataset (1,000 cases).' However, I did not see the how you did it in 'init_dataset.py' and 'act_dataset.py'. So how exactly did you split these scenarios?

Hi, we manually split the data into different folders in advance.


Difference between queryresults in tests and run/debug

Gitea version (or commit ref): 53e6c94
Git version: 2.7.4
Operating system: Ubuntu
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Description
The query below is working when debugging/running the application with a postgresql database.
But when running make test, thus using an inmemory sqlite database, the query always returns nothing, despite an existing HookTask from fixture.
tasks := make([]*HookTask, 0, 10)
err := x.Where("is_delivered=?", false).Find(&tasks)
if err != nil {
    log.Error(4, "DeliverHooks: %v", err)
}

To check I ran following query in a testcase and the results are now correct.
tasks := make([]*HookTask, 0, 10)
err := x.Where("is_delivered IS NOT", true).Find(&tasks)
if err != nil {
    log.Error(4, "DeliverHooks: %v", err)
}

How could it be that they are different? The same phenomena occurs when querying for users and filter by prohibit_login = false.
IMO this means that test cases aren't reliable.

if is_delivered IS NULL, then is_delivered=false is false but is_delivered IS NOT true is true. That's caused by upgraded when add a new column and didn't update all the old records value.

Problem with that is that they are treated differently for each database.
So I propose to add NOT NULL DEFAULT x to all booleans.

I agree that booleans fields should be set as not null default true/false (depending on default)

Closed in favour to a direct proposal #2632


[Feature] Calculate initial PIP position correctly based on orientation

Purpose

Simplified getting size of pip
Calculate the correct position when rotating
Show pip under infoheader

...

Does this introduce a breaking change?

[ ] Yes
[X ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

Simplified getting size of pip [OK]
Calculate the correct position when rotating
Show pip under infoheader [OK]

For 2) I noticed that the position of the pip view is off the screen when I rotate orientation on iPad Pro 12.9 inch simulator iOS 15.2. video attached
https://user-images.githubusercontent.com/90668345/165395413-e450ff9c-b8a1-4145-ad16-dc98a1fa87e2.mov

Simplified getting size of pip [OK]
Calculate the correct position when rotating
Show pip under infoheader [OK]

For 2) I noticed that the position of the pip view is off the screen when I rotate orientation on iPad Pro 12.9 inch simulator iOS 15.2. video attached
rotation.pip.position.issue.iPad.mov

Good catch, I will take a look!


Context.ContextActivities vs Context.Extensions.CourseArea

I might be missing something here, but we seem to have two properties doing similar things in the vle recipes. It
In the documentation most of the common structures can use CourseArea extension, which (I think) was originally used  to link to the UDD in the context. This does have an ID too, which I think Adam was using to using to find where resources lived.
ContextB however allows for a contextActivities property with a ‘grouping’, that allows an additional ObjectA statement in the context to be associated to the activity described in the statments object.
The only statement templates to use contextB are the assignment graded and assigned. Both these statements in the Moodle and Blackboard examples use the contextActivities, but it has also snuck into the blackboard courseaccess example, although if that is using the resource viewed template then it should be using contextA which doesn't allow contextActivities.
In both the Blackboard and Statement template the type in the ContextActivites object is courseArea while the moodle example uses http://xapi.jisc.ac.uk/define/vle/course.
Are these properties doing the same thing now? Or should ContextActivities groupings be an option property to more of the generic recipes with the blackboard course content access using it.
I'm not sure how the analysts are using it..

#165

One of the problems I think we identified was that contextActivities is framed as an open list, which we felt to be problematical from a practical point of view. This is, however, the "standard xAPI" way. I think we ended up with two ways of doing the same thing because we wanted to have the cake and the ha'penny:

something standards-y so other people might be able to use the data who worked that way
something we would actually use ourselves

OTOH, I might be thinking about something a little different to what you are querying, David...

I think that this is basically correct, in that the courseArea extension does the same job as the contextActivities grouping structure - it's for showing the wider context in various ways. However, it also links the UDD and vle module IDs, so I'm not (yet) sure if that works with contextActivities.
If it's possible to drop the courseArea extension and use courseArea in the contextActivities structure, I think that would be preferable (but I would say that, wouldn't I?). We'd need to check that it supports all the data we need there. And it there are technical issues, probably live with what we've got.
Also, we'll need to be careful about the meaning of the various contextActivities. We may / should apply them to some sections of our current design work, or we may be re-inventing some wheels. This refers: https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Data.md#context.
For example: "a Statement about a quiz question would have the quiz as its parent Activity." Note - NOT as its grouping Activity. So, most modules would have a Course as their Parent (and grouping wouldn't be appropriate).

From Monday call. Remove Context.ContextActivities from recipes as Context.Extensions.CourseArea duplicates this information

This changes the statements for assignment graded and assignment submitted from contextB common statement to ContextA as the only difference between the statements is the  addition of Context.ContextActivities... which we have just decided to remove. I will leave ContextB in the common statements with a deprecated tag for now

updated to remove context.contextactivities. Moodle and blackboard json examples need updating.


Nested embedded schema build_generated throws an error.

Steps to Reproduce
The nested embedded schema build_generated throws an error.
Code sample

Main Class
-----------

import 'package:isar/isar.dart';
import 'product_basic.dart';

part 'products.g.dart';
@Collection()
class Products {
  Id? id = Isar.autoIncrement;
  String? documentId;
  ProductBasic? productBasic;
}

Nested Level 1:
--------------

import 'package:isar/isar.dart';
import 'product_main_cat.dart';

part 'product_basic.g.dart';
@embedded
class ProductBasic {
  String? productName;
  String? productPurchaseDate;
  ProductMainCat? productMainCat;
}

Nested Level 2:
---------------

import 'package:isar/isar.dart';
part 'product_main_cat.g.dart';
@embedded
class ProductMainCat {
  String? documentId;
  String? categoryName;
}

Error Details
A value of type 'Null' can't be assigned to a parameter of type 'Map<String, Schema<dynamic>>' in a const constructor. (Documentation)

Try using a subtype, or removing the keyword 'const'.

Offical Docs says
It's often helpful to have nested objects in your collection model. There is no limit to how deep you can nest objects. Keep in mind, however, that updating a deeply nested object will require writing the whole object tree to the database.

Details
I don't know where I went wrong.

Platform: MacBook Pro ,Apple M1 chip
Flutter version: [3.3.10]
Dart version:[2.18.6]
Isar version: [3.0.5]
isar_generator: [3.0.5]
build_runner:[2.3.3]

I figured out it happens when you divide your classes into multiple files. If you have them all in one file its working properly. So for now you can continue that way :)
PS: Has nothing todo with your request but I would suggest you to rename your products class to product (singular) as its storing one product.

Thanks a lot. If it's a single file, its works as a charm. It would be great to support multiple files.

What news about this issue? I do not want to place different domain entities in the sage file. If I will have 100 embedded classes so how my target class will looks? This is no go.

I fixed this in my project by adding missing imports for all embedded (at all nesting depths) schemas to the root collection schema.
import 'package:isar/isar.dart';
import 'product_basic.dart';
import 'product_main_cat.dart'; // this should be added

part 'products.g.dart';

@Collection()
class Products {
  Id? id = Isar.autoIncrement;
  String? documentId;
  ProductBasic? productBasic;
}

No further need to store it in a single file.


openshift: allow custom payload images for development

Sometimes we need to test new builds of RPMs, for example to
verify a bug in QEMU, kata-runtime or other packages.
For this purpose the user can now add a configmap with a single data
entry that specifies a URL to a container image, e.g.
quay.io/someuser/repository:tag.
The ConfigMap will be added to the Pod spec of the installer daemon pods as an
environment variable. If the variable is set the daemon will use it. If
not the default mechanism for choosing the payload image is used.
The purpose of this feature is for development purposes only. When the
ConfigMap is used the operator will print a warning that using
self-built RPMs taints the kataconfig installation.
Also add a description in docs/HACKING.md on how to use the ConfigMap
and how to build a custom payload image.
Signed-off-by: Jens Freimann<EMAIL_ADDRESS>

@zanetworker

@jensfr nice :)

Just realized the daemon is also part of this repo now and I can include the change in this PR. Will update the branch soon.

One other thing, are you also planning to cherry pick this master?

One other thing, are you also planning to cherry-pick this to master?

Yes, I'll send a PR for master as well but it requires some small changes.


HDDS-1921. TestOzoneManagerDoubleBufferWithOMResponse is flaky

What changes were proposed in this pull request?
Currently testDoubleBuffer waits for a specific transaction count and checks lastAppliedIndex, which is updated last in flushTransactions on another thread.  I guess this may be the cause of flakiness.  By swapping the order in the test, we ensure that when the wait is over, all operations (transaction count increase, etc.) are done.
https://issues.apache.org/jira/browse/HDDS-1921
How was this patch tested?
Ran TestOzoneManagerDoubleBufferWithOMResponse a few times.

/label ozone

@bharatviswa504 please review when you have some time

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
128
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
826
trunk passed

+1
compile
462
trunk passed

+1
checkstyle
106
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
1178
branch has no errors when building and testing our client artifacts.

+1
javadoc
226
trunk passed

0
spotbugs
520
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
782
trunk passed

_ Patch Compile Tests _

+1
mvninstall
722
the patch passed

+1
compile
445
the patch passed

+1
javac
445
the patch passed

+1
checkstyle
83
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
735
patch has no errors when building and testing our client artifacts.

+1
javadoc
193
the patch passed

+1
findbugs
663
the patch passed

_ Other Tests _

+1
unit
342
hadoop-hdds in the patch passed.

-1
unit
2424
hadoop-ozone in the patch failed.

+1
asflicense
64
The patch does not generate ASF License warnings.

9555

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestMultiBlockWritesWithDnFailures

hadoop.ozone.client.rpc.TestSecureOzoneRpcClient

hadoop.ozone.TestStorageContainerManager

hadoop.ozone.client.rpc.TestOzoneRpcClient

hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

hadoop.ozone.om.TestScmSafeMode

hadoop.ozone.client.rpc.TestCommitWatcher

hadoop.ozone.client.rpc.TestWatchForCommit

hadoop.ozone.client.rpc.TestOzoneRpcClientWithRatis

hadoop.hdds.scm.pipeline.TestRatisPipelineCreateAndDestory

hadoop.ozone.client.rpc.TestBlockOutputStream

Subsystem
Report/Notes

Docker
Client=19.03.0 Server=19.03.0 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1238/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1238

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux f59460a8e48f 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 8cef9f8

Default Java
1.8.0_212

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1238/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1238/1/testReport/

Max. process+thread count
4111 (vs. ulimit of 5500)

modules
C: hadoop-ozone/ozone-manager U: hadoop-ozone/ozone-manager

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1238/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

I will commit this to the trunk and 0.4 branch.

Thank you @xiaoyuyao for review and @bharatviswa504 for review+commit.


need to document development branches

Problem
the main, hotfix, and dev branches exist, but there is no mention of them in the CONTRIBUTING.md documentation. Contributions would be easier to make if the development process had documentation surrounding the intended use of these branches and the release path process.
Solution
Document development process; docs don't need to be perfect, but should indicate expected pathing for contributions.

Totally agree with this.
Honestly, still don't understand the hotfix system that @MikhailZex suggested. If it was documented I might be able to understand it.
Additionally, PRs with major bugfixes seem to be going to the hotfix branch, & the hotfix branch doesn't get pushed to master, so the bugfixes never end up on our PyPi releases.
Either revert to only master & dev, or if better docu's were around imo

I'm going to put this issue on hold, while we deal with our Git workflow internally.


AI will send email after refusing to do so

https://drive.google.com/file/d/1CkUlGV1r79u0TPbRO5_SmuFT1uDUjGtI/view?usp=drive_link

think this is solved with #249

https://drive.google.com/file/d/1Eaaphc5EoFNB28R0KoWloZO8ypNyI_Kt/view?usp=drive_link


Modify the build scripts in CoastalApp to accommodate for METIS/PARMETIS configs from user

ParMetis is not included in CoastalApp. At this point, both WW3 and SCHISM require the library for their build.
User should be warned that the library is required and that he/she needs to set the METIS environment variables properly.
There should be an option (in place) to download the Parmetis libraries in thirdparty and compile the libraries from within CoastalApp (enhancement).

As SCHISM (unfortunatley) comes with ParMetis included in the source tree, we should, for consistency reasons, simply make a link.  the following worked for me:
mkdir -p thirdparty_open/ParMetis
ln -sf ./SCHISM/schism/src/ParMetis-4.0.3/metis thirdparty_open/ParMetis/Metis

Better, of course, if both SCHISM and WW3 honored an environment variable ...

Thanks Carsten.
So by setting the link to thirdparty_open for ParMetis the compilation was
successful.
I'll be working on the build scripts regarding ParMetis (allow the users to
use their own ParMetis, download it
to thirdparty_open, etc). The build script will set the environment
variables for METIS/PARMETIS as well.
Per NOAA guidance, I have removed the ParMetis from
CoastalApp/thirdparty_open
In WW3, they are moving away from ParMetis, just to let you know.
Thanks
Takis
Panagiotis Velissariou, Ph.D., P.E.
UCAR Scientist
National Ocean and Atmospheric Administration
National Ocean Service
Office of Coast Survey CSDL/CMMB
Project Lead - Coastal Coupling
cell:<PHONE_NUMBER>
email: @.***
On Fri, Aug 12, 2022 at 11:10 AM Carsten Lemmen @.***>
wrote:

As SCHISM (unfortunatley) comes with ParMetis included in the source tree,
we should, for consistency reasons, simply make a link. the following
worked for me:
mkdir -p thirdparty_open/ParMetis
ln -sf ./SCHISM/schism/src/ParMetis-4.0.3/metis thirdparty_open/ParMetis/Metis
Better, of course, if both SCHISM and WW3 honored an environment variable
...
—
Reply to this email directly, view it on GitHub
https://github.com/noaa-ocs-modeling/CoastalApp/issues/120#issuecomment-1213281607,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APC7TP7OOIBCOY4Z2YGI4QTVYZZOJANCNFSM56IMWWBQ
.
You are receiving this because you were assigned.Message ID:
@.***>

Parmetis / Metis compilation is the user responsibility. Code will not be a part of CoastalApp.

@saeed-moghimi-noaa of course the code should not be part of it.  As it is a requirement of two of the submodules of Coastalapp (ww3 and schism), and it is part of the source coming with schism, we can still provide a consistent build (either with the schism-provided Metis for WW3 also, or with a user-provided Metis lib)

Build scripts have been modified to allow user to supply ParMeti/Metis library locations or, to allow downloading ParMeti/Metis and have the build script to compile the library. The updates will be pushed upstream on 08/22/2022 after final testing. I will ask Carsten and Jianhua to retest with SCHISM and WW3 on their side. For SCHISM+WW3 compilation, WW3 should be able to use SCHISM's ParMetis.

-thirdparty argument to ./build.sh does not honour input
./build.sh -plat femto -component WW3 -thirdparty "metis parmetis"
...

   THIRDPARTY     = PARMETIS
   PARMETISHOME   = /sciclone/home20/clemmen/devel/noaa/CoastalApp/SCHISM/schism/src/ParMetis-4.0.3

and later does not even find the library provided with the PARMETISHOME environment variable.
compileMetis (main): called from: functions_build (build.sh)
        the source directory for the ParMetis/Metis library is not a valid directory:
          srcDIR = NOTFOUND
        searched in rootDIR = /sciclone/home20/clemmen/devel/noaa/CoastalApp/thirdparty_open

Linking into /sciclone/home20/clemmen/devel/noaa/CoastalApp/thirdparty_open/parmetis/ does not work, either
@pvelissariou1 this is a showstopper for our work on CoastalApp.

Updated CoastalApp and SCHISM to allow the use of externally built ParMETIS library. Upon testing, changes to CoastalApp will be pushed upstream. SCHISM has the capability now to:

[ ] do the partitioning without ParMETIS (NO_PARAMETIS)
[ ] do the partitioning using externally built ParMETIS
[ ] do the partitioning using internally available ParMETIS

Changes have been pushed to SCHISM PR: https://github.com/schism-dev/schism/pull/78
Pending successful testing and approval.

It will be closed today

@Lemmen, Carsten @.> , @Y. Joseph Zhang
@.> The PR #78 is finalized by me. With the modifications on
the cmake files SCHISM+ParMETIS (external, internal, NO_PARMETIS options)
compiles fine outside CoastalApp and in CoastalApp.
The only issue within CoastalApp for SCHISM is the Makefile in schism-esmf
and at lines 81, 82
Over there the "install-nuopc" rule tries to install libmetis.a and
libparmetis.a that breaks the install sequence
when the external ParMETIS is used or the NO_PARMETIS option is activated
(no $(SCHISM_BUILD_DIR)/lib/lib*metis.a libraries for these two cases).
I don't think these libraries need to be installed. Carsten, Joseph could
you please fix this (delete the lines)?
With the PR merged and the Makefile fix, I'll update the SCHISM sources in
CoastalApp.
I will close the issue today.
Thank you
Takis
Panagiotis Velissariou, Ph.D., P.E.
UCAR Scientist
National Ocean and Atmospheric Administration
National Ocean Service
Office of Coast Survey CSDL/CMMB
Project Lead - Coastal Coupling
cell:<PHONE_NUMBER>
email: @.***
On Mon, Aug 29, 2022 at 9:21 AM Saeed Moghimi @.***>
wrote:

It will be closed today
—
Reply to this email directly, view it on GitHub
https://github.com/noaa-ocs-modeling/CoastalApp/issues/120#issuecomment-1230380238,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APC7TP2R6OF4CA5D34USNOLV3TBNFANCNFSM56IMWWBQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

The issue has completed. CostalApp SCHISM/WW3/ParMETIS are successful after PR #78 for SCHISM. Still waiting approval from @josephzhang8 , @platipodium


Download Error 404

I know this fixed and 1.8.2 had been released but I am a 1.7.3 user like most people to download sub-only vods. Is there any change to change this version's API? I know you do not want to continue with the cracked program but please...
(Or if anyone else knows how to download sub-only vods please answer.)

That won't happen. 1.7.3 suffers from other issues that have been resolved over time and honestly I am surprised that it somehow works again because 1.7.3 was dead for a very long time in the past. The only way for a software is forward. I need to catch up to the ever changing system that is called Twitch.tv and it's nothing that I decide personally. Twitch changes their API's constantly and so I have to "keep up" constantly.
As a little mood boost: I have information that I can POTENTIALLY make sub-only downloads working again. But don't ask for an estimate...

That won't happen. 1.7.3 suffers from other issues that have been resolved over time and honestly I am surprised that it somehow works again because 1.7.3 was dead for a very long time in the past. The only way for a software is forward. I need to catch up to the ever changing system that is called Twitch.tv and it's nothing that I decide personally. Twitch changes their API's constantly and so I have to "keep up" constantly.
As a little mood boost: I have information that I can POTENTIALLY make sub-only downloads working again. But don't ask for an estimate...


Engine Licence Script should run on Windows

Currently, I have to make my changes on Windows, commit everything, check everything out on my Linux box, run the licence script there, and - finally - commit the changes made by the licence script.

Dupe of https://github.com/flutter/flutter/issues/8405


reverted methods removal

added missed Vpn gateway methods...

@MikhailTryakhov what is the intention behind this change, the changes were merged in the last PR, you will have to go through the whole cycle of dotnet sdk code generation and publishing the package now.
How did we miss this piece?

@dsgouda  we had a breaking changes approval for another peace of code and I've made mistake.
not sure where this removal from... Whole cycle is OK...

Automation for azure-libraries-for-java

@azuresdkci Test this please

Automation for azure-sdk-for-node

Automation for azure-sdk-for-python

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go


Locating MD Files is not  working

The  Choose botton of Folder Containg Markdown Reading Note is not working.  Nothing show up after I click the  Choose botton.
And I copy the file path of md notes in the text box, but the pulug in still can not find md nites.

thanks for bringing to my attention. I introduced a bug in that button when I was working on something else. Upgrade to https://github.com/daeh/zotero-markdb-connect/releases/tag/v0.0.20 and let me know if that resolves your issue or not

The Choose botton of Folder Containg Markdown Reading Note is working now. But it seems that snyc Tags is not working, I am sure the file path is  correct.

I'll need more info to help with that. What's the path, what's the filter filter, and what's an example markdown note that you expect to be matched?

The path is the Export Path of BibNotes Formatter. But the Note Title is not {{citekey}}, I change it to {{title}}, I don't know whether it is the problem.

So it's 2 things.

your custom file filter regex is looking for files that begin with @. To find your reading notes use ^.+\.md$.

if you're using a custom file filter, you'll need to specify how the plugin should match the markdown files to zotero items. Assuming that you're using BBT, then the citekey needs to be in the metadata, like in the example MD files of the readme:

The literature note content template I use is
---
citekey: {{citekey}}
year: {{year}}
authors: {{authorString}}
title: "{{title}}"
aliases: ["@{{citekey}}", "@{{citekey}} {{~#each entry.author~}} {{~#if @last}} ({{~family~}}) {{~/if~}} {{~/each}} {{title}}"]
authorFirst: {{entry.author.[0].family}}, {{entry.author.[0].given}}
authorLast: {{#each entry.author ~}} {{~#if @last~}} {{~family}}, {{given~}} {{~/if~}} {{~/each}}
publication: {{containerTitle}}
doi: {{DOI}}
zoterouri: {{zoteroSelectURI}}
obsidiankey: "@{{citekey}}"
tags:
- readingNote
---

**{{title}}**
{{authorString}}
({{year}}) {{~#if containerTitle}} {{containerTitle~}} {{~else~}} {{~/if}}
[@{{citekey}}]({{zoteroSelectURI}})

(with the title template @{{citekey}})

My markdb-connect config is like this:

My literature note content template I use is like this

The error report are:

Could you please tell me how to set the yaml keyword

put this in the "Literature note content template"
---
CiteKey: {{citekey}}
---

so that the very top of the MD file begins with
---
CiteKey: sonImplantableNeuralStimulator2020
---

and put CiteKey  in the yaml keyword field of the plugin

I have tried to manually modify the Metadata in two ways, it seems that they are both ineffective. And I have made so many notes that I can't bear the consequences of completely regenerating the files in the new format. I'm afraid I have to give up using this plug-in regretfully. Thank you for your help. If the subsequent update allows me to use this plug-in without regenerating notes, I will start using it again.

sure. It looks like you're not including the --- above and below CiteKey: sonImplantableNeuralStimulator2020. Markdown metadata (aka frontmatter) is defined by having three dashes at the head of the file and another three dashes at the end the frontmatter. The example MD file in the readme of this plugin gives an example; you can also see the obsidian guide:
https://help.obsidian.md/Advanced+topics/YAML+front+matter
Again, it should work if that file begins with
---
CiteKey: sonImplantableNeuralStimulator2020
---

# An Implantable....

closed by ce46c9b3496c44a33d99288f6d311ee5389a9978


Rule works in debug mode but not in production

config file -
.
.
run_every:
  minutes: 1

buffer_time:
  minutes: 10

alert_time_limit:
  days: 2
.
.

Rule file -
alert:
- alerta
alert_missing_value: '-'
alerta_api_url: my-server-url
alerta_attributes_keys:
- d-event_timestamp
alerta_attributes_values:
- '%(@timestamp)s'
alerta_correlate: []
alerta_environment: Prod
alerta_event:  is_winter_coming?
alerta_group: BS
alerta_origin: '41'
alerta_resource: elastalert
alerta_service:
- elastalert
alerta_severity: minor
alerta_tags: []
alerta_text: winter is coming
alerta_type: frequency
es_host: some-ip
es_port: 9200
filter:
- query:
    query_string:
      query: 'a simple filter'
index: stark-*
name: winterfell
num_events: 1
realert:
  minutes: 120
timeframe:
  minutes: 2
type: frequency

Yeah I know, it doesn't make sense to use frequency for one event, but I have tested it with Any type too

In kibana I can see there is a data for this period -

However there was no alert , and as expected on Kiban rule status was -

So when I tested it for the same duration with elastalert-test-rule I got hits and match!
Would have written the following documents to writeback index (default is elastalert_status):

silence - {'exponent': 0, 'rule_name': 'is_winter_coming?', '@timestamp': datetime.datetime(2020, 8, 18, 17, 43, 30, 835490, tzinfo=tzutc()), 'until': datetime.datetime(2020, 8, 18, 19, 43, 30, 835477, tzinfo=tzutc())}

elastalert_status - {'rule_name': 'is_winter_coming?', 'endtime': datetime.datetime(2020, 8, 18, 4, 4, 22, tzinfo=<UTC>), 'starttime': datetime.datetime(2020, 8, 18, 4, 3, 22, tzinfo=<UTC>), 'matches': 5, 'hits': 5, '@timestamp': datetime.datetime(2020, 8, 18, 17, 43, 30, 838319, tzinfo=tzutc()), 'time_taken': 0.01810431480407715}

I have observed such behavior in other rules as well.
I have around 200 rules. have I touched some limit here ?
Earlier I used to run these in single docker container but for now I am running these in 3 different containers on same host and they all write to different index on es.

My best guess here is that the matching documents don't get added to Elasticsearch in real time. If you upload a document with timestamp 12:00 at 12:10, which is common if you're using some non-realtime logging infrastructure, then Elastalert would miss it. You could verify this by taking one of the queries (from es_debug_trace or just doing it manually) for the most recent 10 minutes, and then running it again for the same time period 15 minutes late. If you get 0 results the first time but some results the second time, that would confirm the issue.
As to fixing it, you could try extending your buffer_time, or use query_delay, or change how timestamping works in your data ingestion to get a field that matches time of ingestion rather than time of event, and use that for ElastAlert.

Thanks a lot for the prompt reply!!!

My best guess here is that the matching documents don't get added to Elasticsearch in real time. If you upload a document with timestamp 12:00 at 12:10, which is common if you're using some non-realtime logging infrastructure, then Elastalert would miss it.

Yes I have observed the delay of around 5 mins that's the reason buffer_time is set to 10 mins!
Could it be the problem because of a volume of rules ? I didn't find any spike in memory or cpu usage though.

I don't see how it could be that. If you have too many rules, you'll notice that the querys start to drift further apart than your run_every, which doesn't seem to be the case. If you turn on --es_debug_trace trace.log, run elastalert briefly, then you should be able to find the exact (except elasticsearch-py changes the hostname) query that's being made, in curl form. You can run that yourself and verify the behavior that at the time it's made, 0 results were returned, and that some time later, it does return results.
If you try that and it's not the case that eventually it returns results, then something very strange is going on. elastalert-test-rule should be basically doing the exact same query but with a whole 24 hours at once.

I don't see how it could be that. If you have too many rules, you'll notice that the querys start to drift further apart than your run_every, which doesn't seem to be the case.

ok, I can see that the rule is executed every minute as expected!

If you turn on --es_debug_trace trace.log, run elastalert briefly, then you should be able to find the exact (except elasticsearch-py changes the hostname) query that's being made, in curl form. You can run that yourself and verify the behavior that at the time it's made, 0 results were returned, and that some time later, it does return results

I have enabled it but they are so many that am not able to extract it for this particular time, I will try to test it this real time to exclude this probability.

If you try that and it's not the case that eventually it returns results, then something very strange is going on. elastalert-test-rule should be basically doing the exact same query but with a whole 24 hours at once.

I ran for the exact time period , I found on the logs in Kibana.


Update legacy.json

added bhbotlist

Won't work. You need to add a whole file for your bot list, as others did


Cannot delete branches with slashes in the name.

Gogs version (or commit ref): <IP_ADDRESS>3
Git version: <IP_ADDRESS>
Operating system: CentOS 7.3.1611
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[x] SQLite

Can you reproduce the bug at https://try.gogs.io:

[x] Yes (provide example URL) https://try.gogs.io/psi-jack/yum-zabbix/branches/task/erenfro/remove-yum-cookbook/delete?commit=fc3fd5dd6f63d156309efadc612ef10c09e52d03&redirect_to=/psi-jack/yum-zabbix/pulls/1
[ ] No
[ ] Not relevant

Log gist:
xorm.log:
[xorm] [info]  2017/02/06 01:10:55.904407 [sql] SELECT id, lower_name, name, full_name, email, passwd, login_type, login_source, login_name, type, location, website, rands, salt, created_unix, updated_unix, last_repo_visibility, max_repo_creation, is_active, is_admin, allow_git_hook, allow_import_local, prohibit_login, avatar, avatar_email, use_custom_avatar, num_followers, num_following, num_stars, num_repos, description, num_teams, num_members FROM user WHERE id=? LIMIT 1 [args] [1]
[xorm] [info]  2017/02/06 01:10:55.905125 [sql] SELECT id, lower_name, name, full_name, email, passwd, login_type, login_source, login_name, type, location, website, rands, salt, created_unix, updated_unix, last_repo_visibility, max_repo_creation, is_active, is_admin, allow_git_hook, allow_import_local, prohibit_login, avatar, avatar_email, use_custom_avatar, num_followers, num_following, num_stars, num_repos, description, num_teams, num_members FROM user WHERE id=? LIMIT 1 [args] [1]
[xorm] [info]  2017/02/06 01:10:55.905787 [sql] SELECT id, lower_name, name, full_name, email, passwd, login_type, login_source, login_name, type, location, website, rands, salt, created_unix, updated_unix, last_repo_visibility, max_repo_creation, is_active, is_admin, allow_git_hook, allow_import_local, prohibit_login, avatar, avatar_email, use_custom_avatar, num_followers, num_following, num_stars, num_repos, description, num_teams, num_members FROM user WHERE lower_name=? LIMIT 1 [args] [linux-help]
[xorm] [info]  2017/02/06 01:10:55.906493 [sql] SELECT id, owner_id, lower_name, name, description, website, default_branch, num_watches, num_stars, num_forks, num_issues, num_closed_issues, num_pulls, num_closed_pulls, num_milestones, num_closed_milestones, is_private, is_bare, is_mirror, enable_wiki, enable_external_wiki, external_wiki_url, enable_issues, enable_external_tracker, external_tracker_format, external_tracker_style, enable_pulls, is_fork, fork_id, created_unix, updated_unix FROM repository WHERE owner_id=? AND lower_name=? LIMIT 1 [args] [2 cookbook-yum-zabbix]
[xorm] [info]  2017/02/06 01:10:55.907067 [sql] SELECT id, lower_name, name, full_name, email, passwd, login_type, login_source, login_name, type, location, website, rands, salt, created_unix, updated_unix, last_repo_visibility, max_repo_creation, is_active, is_admin, allow_git_hook, allow_import_local, prohibit_login, avatar, avatar_email, use_custom_avatar, num_followers, num_following, num_stars, num_repos, description, num_teams, num_members FROM user WHERE lower_name=? LIMIT 1 [args] [psi-jack]
[xorm] [info]  2017/02/06 01:10:55.954675 [sql] SELECT id, user_id, repo_id, mode FROM access WHERE user_id=? AND repo_id=? LIMIT 1 [args] [1 29]

Description
When a branch has slashes in the name, much like is often used in Agile-style development branching, after merging a branch and trying to use the delete branch option, it gives a HTTP-style authentication request and then a 404 error after supplying credentials.
In my test case scenario on try.gogs, I updated my master branch and my task/erenfro/remove-yum-cookbook branch, merged it to master, then tried to delete it, and the same thing occurred.
Often this is used for various types of tracking of the development workflow, such as:
bug/${developer}/${issuenumber}-description-of-work
task/${developer}/${issuenumber}-description-of-work
feature/${developer}/${issuenumber}-description-of-work
etc...

Patch has pushed to fix this issue, please test on develop branch or https://try.gogs.io.
Note that you can't use problematic URL produced before to test because the URL format has been changed during the fix.

I just tested this out, and I actually was able to merge the previously attempted branch before, and it worked, but as a precaution, I also tested in a brand new repository to double confirm, and that worked without any issues as well.

@erenfro yes if you click on the button, Gogs redirects to new URL for you as expected. :trollface:


How get input data in UpdateCacheHandler?

Hi!
How get input data from mutation in body UpdateCacheHandler?
final UpdateCacheHandler<$MyMutation> myMutationHandler = (
  CacheProxy proxy,
  QueryResponse<$MyMutation> response,
) {
  final query = MyQueryToUpdate();
  final result = proxy.readQuery(query);

  /// update the result
  proxy.writeQuery(query, result);
};

You can access the mutation via the queryRequest property on QueryResponse.
Also, if you want to pass in additional data that isn't an input to the mutation, you can pass in a Context object when creating the mutation.
For example:
/// Create a ContextEntry subclass
class UserContextEntry extends ContextEntry {
  final String userId;

  UserContextEntry(this.userId);

  @override
  List<Object> get fieldsForEquality => [userId];
}

/// When instantiating your mutation...
final mutation = MyMutation(
  updateCacheHandlerKey: "myMutationKey",
  /// ...pass in an instance of the ContextEntry subclass
  context: Context.fromList([UserContextEntry("user123")]),
);

final UpdateCacheHandler<$MyMutation> myMutationHandler = (
  CacheProxy proxy,
  QueryResponse<$MyMutation> response,
) {
  final query = MyQueryToUpdate();
  final result = proxy.readQuery(query);

  /// Access the data passed in through ContextEntry
  final userId = response.queryRequest.context.entry<UserContextEntry>().userId;

  /// update the result
  proxy.writeQuery(query, result);
};

I recognize that subclassing ContextEntry as demonstrated above just to pass in a userId String is a bit verbose. I'm open to suggestions to improve the API (@klavs any thoughts here)?


Update documentation with keyring details

The documentation should be updated to include details about the keychain support added in PR #63. I would recommend an example under the Authentication section.
@bdrung Thanks for this feature as well. As with the config file, would you be able to add a few notes to this issue about keychain support? Perhaps a quick example on usage?

Quickest example: Call ProfitBricksService() without specifying a password. If the keyring is installed, it will try to read the password from the keyring.
I'll try to schedule some time to update the documentation. Feel free to go ahead and write some documentation that I will be happy to review.


nixos/kubernetes: Bump CoreDNS and Dashboard

Motivation for this change
Versions of both of the bundled Kubernetes addons are getting old. We should bump those to the latest versions before 19.03 branch-off.
i.e.

coredns 1.2.5 -> 1.3.1
dashboard 1.8.3 -> 1.10.1

Although kubernetes-dashboard maintainers officially state that the latest version of the dashboard doesn't support k8s v1.13 (https://github.com/kubernetes/dashboard/releases/tag/v1.10.1); both components have been tested on Kubernets v1.11.6 and v1.13.3 and they work fine. In any case, the newest version of the dashboard must be best at supporting the newest version of k8s.
The dashboard release note also states that a new flag has been added. In order for users to be able to take advantage of this flag (and others), I've added a new option to the dashboard module, extraArgs with which additional cmdline args to the dashboard can be appended.
@GrahamcOfBorg test kubernetes.dns.singlenode kubernetes.dns.multinode
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[X] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval

@GrahamcOfBorg eval

third time's the charm
@GrahamcOfBorg eval

@GrahamcOfBorg test kubernetes.dns.singlenode kubernetes.dns.multinode

Can you elaborate a bit on your considerations regarding the dashboard compatibility chart? The fact that it has an explicit X and not just a question mark worries me, this seems like they know there are things that do not work, doesn't it?

Looks like the issue at hand is the heapster v. metrics change.

I agree with your concerns, but on the other hand I feel that dashboard v1.10.1 by definition has to support k8s 1.13 better than v1.8.3 does (which also has the x next to 1.13 by the way). I somehow feel that the x is there only to indicate that they can't guarantee everything works. I already tested basic features on the dashboard with the 1.10, 1.13 combination, and it seems to work just fine.
IMHO, either we ship the dashboard as is, while keeping it as updated as possible, or we abandon support for the dashboard alltogether, with reference to the compatibility mismatch. I prefer the former. What do you say? :)

You're right, I completely overlooked the v1.8.3 issue, thanks


Severe online stuttering

There’s drastic stuttering during some hits and connects. Anyone know how to fix it?

Was caused by the custom input lag table in the Lag Manager. Since then we disabled it by default.


boards: st: nucleo_h743/h753 use the default FDCAN clock

When using the FDCAN1, use the default HSE clock source on the nucleo_h743zi or nucleo_h753zi boards, now that sysclck is 480MHz
This is fixing the error when running the  tests/subsys/canbus/isotp/implementation/  on the nucleo_h743zi since the
sysclock is 480MHz (https://github.com/zephyrproject-rtos/zephyr/pull/73705)

Any chance of selecting a more appropriate clock frequency? 80 MHz is preferable.

Set to 'DNM' until this point is verified

Changed to FDCAN clock sourced by the PLL2q at 80MHz for nucleo_h743zi or nucleo_h753zi boards

tests/subsys/canbus/isotp/implementation/ successfully executed on nucleo_h753zi :
TESTSUITE isotp_implementation succeeded

------ TESTSUITE SUMMARY START ------

SUITE PASS - 100.00% [isotp_implementation]: pass = 9, fail = 0, skip = 0, totas
 - PASS - [isotp_implementation.test_bind_unbind] duration = 2.506 seconds
 - PASS - [isotp_implementation.test_buffer_allocation] duration = 1.551 seconds
 - PASS - [isotp_implementation.test_buffer_allocation_wait] duration = 1.203 ss
 - PASS - [isotp_implementation.test_send_receive_blocks] duration = 0.451 secos
 - PASS - [isotp_implementation.test_send_receive_net_blocks] duration = 1.008 s
 - PASS - [isotp_implementation.test_send_receive_net_sf] duration = 0.006 secos
 - PASS - [isotp_implementation.test_send_receive_net_single_blocks] duration =s
 - PASS - [isotp_implementation.test_send_receive_sf] duration = 0.006 seconds
 - PASS - [isotp_implementation.test_send_receive_single_block] duration = 0.15s

------ TESTSUITE SUMMARY END ------

===================================================================
PROJECT EXECUTION SUCCESSFUL

tests/subsys/canbus/isotp/conformance/ or tests/subsys/canbus/isotp/implementation/ successfully executed on nucleo_h753zi :

Perfect, thanks for switching to a 80MHz clock. In the future, I recommend using tests/drivers/can/timing/ for validating CAN clock configuration.
For this board, now that you've switched to 80MHz, it should even be possible to run that test with all bitrates by adding a board configuration file in tests/drivers/can/timing/boards/, setting CONFIG_TEST_ALL_BITRATES=y.


Dependency review

What was the end-user problem that led to this PR?
The problem was that we were using some outdated test dependencies.
What was your diagnosis of the problem?
My diagnosis was that we can upgrade them, since the comments justifying them being pinned are no longer relevant.
What is your fix for the problem, implemented in this PR?
My fix is to unpin the dependencies, and remove the comments no longer applying.
Why did you choose this fix out of the possible options?
I chose this fix because it was the only fix I could think of.

I think we should be able to use rack 2 now?

According to the comment I left in there, the version of the artifice gem we're using does not support it...

Ah sorry I didn’t see that
@bundlerbot r+

Thanks for reviewing @segiddins!


Added dump_args statement function for debugging puppet code

This adds a new function that outputs the variables to STDOUT.  Its pretty dead simple and when used with an rspec test it can decrease debug time greatly. The only other option is to use a bunch of notify resources which to me is not as fast and does not display the variables correctly when you have hashes and arrays in your variables.  If you think this is not useful imagine storing a large hash in hiera and wanting to know why your custom parser is blowing up on your data and the notify statement does a poor job of displaying your 50 line data hash.  Its really nice to see whats in your puppet variables and this helps immensely.
Another use case is trying to find out why create_resources isn't working as expected because your data being passed in is all wrong.
Basically it works like this:
puppet code below:
$var1 = 'foo'
$var2 = ['bar']
$var3 = {'foo' => 'bar'}
dump_args($var1, $var2, $var3)

yields the following in STDOUT
[
  "foo",
  [
    "bar"
  ],
  {
    "foo": "bar"
  }
]

@logicminds thank you for updating this!
here's a diff that should make… a better config of rubocop pass:
diff --git a/lib/puppet/parser/functions/default_content.rb b/lib/puppet/parser/functions/default_content.rb
index dc38c02..8b16050 100644
--- a/lib/puppet/parser/functions/default_content.rb
+++ b/lib/puppet/parser/functions/default_content.rb
@@ -1,22 +1,20 @@
-module Puppet::Parser::Functions
-  Puppet::Parser::Functions.newfunction(:default_content,
-                                        :type => :rvalue,
-                                        :doc => <<-'ENDOFDOC'
+Puppet::Parser::Functions.newfunction(:default_content,
+                                      :type => :rvalue,
+                                      :doc => <<-'ENDOFDOC'
   Takes an optional content and an optional template name to calculate the actual
   contents of a file.

   This small function abbreviates the default initialisation boilerplate of
   stdmod modules.
   ENDOFDOC
-  ) do |args|
-    content = args[0]
-    template_name = args[1]
+) do |args|
+  content = args[0]
+  template_name = args[1]

-    Puppet::Parser::Functions.autoloader.loadall
+  Puppet::Parser::Functions.autoloader.loadall

-    return content if content != ''
-    return function_template(template_name) if template_name
+  return content if content != ''
+  return function_template(template_name) if template_name

-    return nil
-  end
+  return nil
 end
diff --git a/lib/puppet/parser/functions/dump_args.rb b/lib/puppet/parser/functions/dump_args.rb
index 37f7587..1db1c6b 100644
--- a/lib/puppet/parser/functions/dump_args.rb
+++ b/lib/puppet/parser/functions/dump_args.rb
@@ -1,17 +1,13 @@
 require 'json'
 require 'puppet/parser/functions'

-module Puppet::Parser::Functions
-  newfunction(:dump_args, :type => :statement,:doc => <<-EOS
+Puppet::Parser::Functions.newfunction(:dump_args, :type => :statement, :doc => <<-EOS
      dump_args - prints the args to STDOUT in Pretty JSON format.

      Useful for debugging purposes only. Ideally you would use this in
      conjunction with a rspec-puppet unit test.  Otherwise the output will
      be shown during a puppet run when verbose/debug options are enabled.
-
   EOS
-  )  do |args|
-    puts JSON.pretty_generate(args)
-  end
-
+) do |args|
+  puts JSON.pretty_generate(args)
 end
diff --git a/spec/unit/puppet/parser/functions/dump_args_spec.rb b/spec/unit/puppet/parser/functions/dump_args_spec.rb
index 79d32c9..b42e1e8 100644
--- a/spec/unit/puppet/parser/functions/dump_args_spec.rb
+++ b/spec/unit/puppet/parser/functions/dump_args_spec.rb
@@ -1,10 +1,9 @@
 require 'spec_helper'
 require 'json'
-describe "dump_args" do
+describe 'dump_args' do
   let(:scope) { PuppetlabsSpec::PuppetInternals.scope }

-  it "should exist" do
-    Puppet::Parser::Functions.function("dump_args").should == "function_dump_args"
+  it 'should exist' do
+    Puppet::Parser::Functions.function('dump_args').should == 'function_dump_args'
   end
-
 end

you can join the rubocop discussion here: https://github.com/puppet-community/modulesync_config/issues/14

@igalic just rebased after applying the diff. Rubocop only warns on some things that should be excluded which I commented on in the rubocop discussion.

@logicminds can you rebase and try again?

@jyaworski justed rebased

Merging despite rubocop.....


Note that Firefox works too.

Why:

#704
What's being changed:

I changed that to Chrome, Firefox, or any Chromium-based browser (like the new Edge).
Check off the following:

[x] All of the tests are passing.
[x] I have reviewed my changes in staging.
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

Thanks @KTibow I'll get this branch updated and merge once tests are passing 🍏


errors: should have minimal dependency on reflectlite

On go1.19, A blank import of "errors" increases the binary size by ~15.5KiB due to the transitive dependency on reflectlite.
The hard dependency occurs because of the program initialize variable for:
var errorType = reflectlite.TypeOf((*error)(nil)).Elem()

We could consider a trick similar to 419757
This is relevant since many packages depend on errors only for errors.New, and we should not expect those packages to force reflectlite to be transitively linked in.

I also wonder if programs that depend on both reflect and reflectlite could just end up using the reflect package instead and save that ~15.5KiB. I don't know how to implement that without some linker magic.

Perhaps the reflect package can can just import reflectlite and build on top of it, instead of duplicating code. (The reflectlite package may need to export more things for reflect to use, and that is fine, as it is an internal package.)
It would look nicer if the reflect package is self-contained. But probably okay if it is not.

It would look nicer if the reflect package is self-contained. But probably okay if it is not.

For "look nicer", are you referring to how the package appears in pkgsite? Implementing "reflect" in terms of "reflectlite" will probably require the primary types to be declared in reflectlite with type aliases left in "reflect". For an unrelated package split that I was doing, @mvdan mentioned that we might want to teach the pkgsite certain patterns where it hoists a type alias as if it were declared locally (in terms of presentation).

I was mostly thinking about reading the code. It would be nicer if the code stays together.
For documentation, reflectlite doesn't define many types for reflect to export, so it is probably not too bad. We probably alias Kind and Type, or duplicate them, which shouldn't be too bad. I don't think we can alias Value as we need to define more methods on reflect.Value. reflect.Value could probably wrap reflectlite.Value.

The issue has been settled
go build the following code, with or without import errors, is 1.4M in size
package main

import _ "errors"

func main() {

}

See https://github.com/golang/go/issues/54341#issuecomment-1879968971 , I think this issue can be closed.
@dsnet Could you please close this issue?

Closing based on previous comment.  Please comment if you disagree.  Thanks.


Three bugs in AzurePortalSigninfromanotherAzureTenant.yaml

The latest update for the analytic rule "Azure Portal sign in from another Azure Tenant" contains three bugs that will prevent us from updating the rule.
The first bug: On lines 26 and 27 the line "with(format='multijson')" exists 2 times. The solution is to remove "with(format='multijson')" from line 27 as I did locally.
The second bug: the function "ipv6_is_in_any_range" is not available for Log Analytics but for Azure Data Explorer. No solution found, I've commented these out.
The third bug: The error in "Alert Description Format" in the section "Alert details" is "Too many column names. You can define up to 3 column names". The solution is to delete the latest sentence with a column "with the User Agent of {{UserAgent}}."
I did the bugfixes locally and the validation passed

Hi @esschotenw Thanks for flagging this, we have raised a PR - #7967 for resolving the first and third bug and for second bug that you have reported regarding the ipv6_is_in_any_range() function, we tried running the below test query in workspace for the given function
let LocalNetworks=dynamic([
"a5e:f127:8a9d:146d:e102:b5d3:c755:f6cd/112",
"0:0:0:0:0:ffff:c0a8:ac/60"
]);
let IPs=datatable(IP:string) [
"a5e:f127:8a9d:146d:e102:b5d3:c755:abcd",
"a5e:f127:8a9d:146d:e102:b5d3:c755:abce",
"a5e:f127:8a9d:146d:e102:b5d3:c755:abcf",
"a5e:f127:8a9d:146d:e102:b5d3:c756:abd1",
];
IPs
| extend IsLocal=ipv6_is_in_any_range(IP, LocalNetworks)
We observed that the results returned after running this query are as expected so the workspace is accepting this function as required, if there is anything else we can assist you with please let us know, thanks!

Hi @v-vdixit, Thank you!
I've tested your query on our workspaces and it's working properly as you said. So, the second one is no bug!
But it's still weird that Logs, where we put the KQL, marks this function with a red line and error text: "The name 'ipv6_is_in_any_range' does not refer to any know functions.


Visual surround with tag doesn't work

Checklist

[x] Have you updated the plugin to the latest version on main branch?
[x] Have you read through :h nvim-surround to see if there might be any relevant information there?

 The 'Enter an HTML tag: ` remains in the command line but the buffer does not update.
Expected behavior
Give what the expected buffer output should be after the keystroke sequence.
return html`<span>${this.theEvent.opp.oddsPre}</span> ${this.theEvent.opp.odds}`

Additional context
Wondered if this was related to Dressing, but have removed that from my config and problem remains.

Hi @benfrain, it looks like my messages might have been a bit unclear; when it asks for the tag you don't need the opening and closing <, > markers. However, I'll still implement it so that it works with the angle brackets on a new branch fix-html-patterns. If there's anything else you'd like to mention, don't hesitate to do so

I think the existing implementation is actually fine, it just wasn't what I expected coming from tpope's surround. Perhaps just detail that needs adding in the readme? I'm happy to add a little there if it saves you adding more code and let's you deal with actual bugs rather than just 'different' way of doing things?

I'm currently working on a massive overhaul of how this project is documented/how features are shared, to better help people understand the feature set/what the defaults are. I also hold the design philosophy that the best design is the one that you don't notice; e.g. in this case ideally you wouldn't need any explanation to know how to use it. Also for this particular use case it's only a few characters so don't worry about it too much :) I would also ask that you try out branch refactor-code, as I also did an overhaul of the internals and will be making most commits there, before merging that branch into main. Thanks!
P.S. Feel free to re-open this issue if necessary.


Accessibility improvements

Hi! Thanks for a nice library.
I think it's accessibility could be significantly improved. Currently, when some element is highlighted, keyboard focus is not restricted within this element so you can press Tab and focus will move out of highlighted element bounds. As well, popover buttons are made of <a> so they are not clickable by pressing Space.
I see two potential improvements:

Create a focus trap on highlighted elements (see https://hackernoon.com/its-a-focus-trap-699a04d66fb5)
Use semantic markup for popover controls (e.g. <button> instead of <a href="javascript:void(0)">

Really cool indeed! I’m also interested in looking into using this for accessibility reasons. My website - datorskolan.com - is targeting elderly people. This would be a great way of guiding them where to click!

Hey Andrew, thank you for the feedback.
I have fixed the markup. But for the focus trap, we won't be adding it into the core of the library just yet but I am planning to add the plugin mechanism to make it easier to add additional functionality on top of it so to keep the original library light-weight. And then may be we will release a plugin for this.
Thanks

Just FYI, accessibility is also the main criteria that prevents me from using this awesome lib.
A simple example: navigating through the example demo page only with the tab key. Outline is not set on elements, visual transitions do not happen as with the mouse...