[Installation]: Gemma2 Installing Flash Infer [rank0]: TypeError: 'NoneType' object is not callable

The source of your error is that you have installed the wrong version of FlashInfer.
FlashInfer builds wheels for specific torch and cuda versions. vLLM v0.5.1 uses torch==2.3 and cuda==12.1. So you will likely want to download the following wheel:
pip install flashinfer -i https://flashinfer.ai/whl/cu121/torch2.3

[rank0]: TypeError: 'NoneType' object is not callable

pip install flashinfer -i https://flashinfer.ai/whl/cu121/torch2.3

The same error occurred when I use torch==2.3 and vllm==0.5.1, but when I installed it as above, the model was loaded.
However, a segmentation fault occurs.

On the other hand, if you run vllm/vllm-openai:latest using Docker, it works well.

i still have this problem, can anyone help?

i still have this problem, can anyone help?

Can you try again on latest release (v0.5.5). We have resolved some issues with Gemma in this version


Prometheus stats with label envoy_worker_id are double-counted with sum

In #21756, a tag-extraction rule for envoy_worker_id was added. However, the stats with a label for the worker-id (the per-worker stats) and the global stat have the same basename, resulting in the following output from /stats/prometheus:
envoy_listener_downstream_cx_total{envoy_listener_address="vip"} 2
envoy_listener_downstream_cx_total{envoy_worker_id="0",envoy_listener_address="vip"} 1
envoy_listener_downstream_cx_total{envoy_worker_id="1",envoy_listener_address="vip"} 1

The problematic case is the following:
sum(envoy_listener_downstream_cx_total) will produce 4, which is misleading because there are only 2 connections.
Workaround: sum(envoy_listener_downstream_cx_total{envoy_worker_id=""}) will produce 2 as expected.

cc @davinci26 @jmarantz

I suggest we fix it by modifying the regex to not exact worker.
Current:
  // listener.<address|stat_prefix>.(worker_<id>.)*
  // listener_manager.(worker_<id>.)*
  // server.(worker_<id>.)*
  addRe2(
      WORKER_ID,
      R"(^(?:listener\.(?:<ADDRESS>|<TAG_VALUE>)\.|server\.|listener_manager\.)(worker_(\d+)\.))",
      "");

Suggested:
  // listener.<address|stat_prefix>.(worker_<id>.)*
  // listener_manager.(worker_<id>.)*
  // server.(worker_<id>.)*
  addRe2(
      WORKER_ID,
      R"(^(?:listener\.(?:<ADDRESS>|<TAG_VALUE>)\.|server\.|listener_manager\.)worker_((\d+)\.))",
      "");

I think this will result in something more like this, with different base names:
envoy_listener_downstream_cx_total{envoy_listener_address="vip"} 2
envoy_worker_listener_downstream_cx_total{envoy_worker_id="0",envoy_listener_address="vip"} 1
envoy_worker_listener_downstream_cx_total{envoy_worker_id="1",envoy_listener_address="vip"} 1


SAK-33536 Resources default upload overwrite option to new version

Okay, this seems good. I'll make a note to Wilma to include this option in the documentation. This should also get back to 11


This is the April 2024 Update (v2.21.0)

These are the final bugfixes and patch notes for 2.21. It's still draft for a reason, we still have work going on...
Fixes #2026
Fixes #2000
Closes #2005
Fixes #2010
Fixes #1500

I think I've got all the low-hanging fruits for the next update, will finalise the patch notes once the natives work has concluded.

This is ready for review.


Hotlink to GHE personal token

It would be nice if when selecting a domain that is not github.com that this linked to https://${domain}/settings/tokens/new?description=Refined%20GitHub&scopes=repo
https://github.com/sindresorhus/refined-github/blob/f36d4f10c725b4511e0d28d5c1fec2cf1b2a22b6/source/options.html#L9

If you don't want to do this, I'll see if I can crank out some of the GHE issues this week.

Duplicate of
https://github.com/sindresorhus/refined-github/issues/2408


whatsmyuri command is broken

That command has been broken since #534, when we made Handler a shared object between all connections. Let's keep it shared but pass connection information to the handler method via context. That's a temporary solution until we understand what exactly we need in other handler methods.

[ ] Update documentation for Handler type to clarify that handler is shared between all connections.
[ ] Add ConnInfo struct to conn package with a peer address as a string.
[ ] Add withConnInfo(ctx context.Context, connInfo *ConnInfo) context.Context function that returns derived context with connection information set (using WithValue under the hood). Use that function in route.
[ ] Add GetConnInfo(ctx context.Context) *ConnInfo function that would return that information.
[ ] Move MsgWhatsMyURI to handlers/common, use connection information to implement that function.
[ ] Use that function in all three handlers. Update integration test to use two connections with different you responses. Ports will be different.

@AlekSi a couple of questions for clarity:

Docs for Handler type - do you mean handlers.Interface or all the implementations? Or both interface and implementations?
conn package - do you mean clientconn?


global tags, upgrade to influxdb, upgrade to telegraph

This contains the following

Upgrade to InfluxDB 0.11.1 - I was causing crashes in 0.10.x
Upgrade to Telegraf 0.11.1 - 0.10.x was possibly causing leaked sockets
Upgrade to Alpine 3.3
Conversion of envtpl for telegraf to dockerize - this was done to add support for global tag as an environment variable
Optional disabling of Prometheus integration -  I normally just rebuild and delete the code related to this, but this will allow me to turn it off and make no difference on the Deis side.
Stripe duplicate blanks lines from the config template that is generated.  - Makes it easier to read

@jchauncey this is part of my stab at  #78

All you needed to do was add your range section to the template and that would do exactly what you wanted without having to change the entire template. Also if you turn off the prometheus part you wont receive any metrics from kubernetes which we are building dashboards for.

@jchauncey I don't currently run prometheus.  I may in the future or when your dashboard exists.  I'm using heapster to collect my kubernetes metrics.  This weekend I can revert all of those changes to the template and use sprig instead.  Envtpl has no documentation and I had no clue it included sprig.

No you dont need prometheus. We are gathering the kubernetes metrics which are exposed as prometheus endpoints and sending them to influx.

Not all of my nodes are kubernetes nodes

What do you mean? This project is kind of built to gather metrics from a kubernetes cluster.

@jchauncey I can certainly fork your stuff if you prefer to not add the configuration option.  I mean I run both a kubernetes cluster and a few nodes that are not part of the kubernetes cluster, but are part of the same fleet cluster.
So far as long as the prometheus integration configurable I can use everything else.

I also currently run a Deis cluster and am looking forward to the 2.0 release.

Well this particular component is meant to provide a robust metrics system for deis running on k8s so thats kind of the base. I like the global tags part of the PR just wonder about making the prometheus portion configurable.
Basically telegraf will only run on your kubernetes cluster anyways when you install this (using the monitor chart we are building).

in the case were you want to collect metrics from non-k8s nodes you could just run the official docker image of telegraf.

annnnnd I just accidently wiped out all my changes...  give me a few moments

@jchauncey converted everything back to envtpl and used sprig.
I changed the disabling of the k8s by checking if the file exists instead of a flag.
There is no official telegraf docker container.  Along with anything I contribute here I would have to reproduce like the global_tags in this pull request.  I would prefer not to run 2 seperate telegraf setups, but I will if I must it's just less desirable.

K let me think over the weekend about how to best approach this. I never really considered running this outside of k8s so it may mean rethinking stuff. but there is an official image now - https://github.com/influxdata/telegraf-docker

ya an official image using trusty, before using that I would just fork this project.

Ok im liking what I see here. @sstarcher could you format your commit message using these guidelines - https://github.com/deis/workflow/blob/master/src/contributing/submitting-a-pull-request.md
Once you do that we can work on getting this merged.

@jchauncey I reformatted the commit message


Sync wrappers with underlying contracts

Note: it might be good for the future to remove generated code from the repo and automatically do it as part of the build

I agree

However, then when people clone the repo to view the code, their IDE will complain with lots of static analysis errors, as source code won't exist. This will lead some people to conclude that the code in the repo is broken.

I don't think that will be too much of an issue.
Our ReadMe can indicate that you need to run a Gradle build (or at least trigger the generator task), which isn't an uncommon practice, so I don't imagine most people will be stumped by this. However, at the moment our Gradle build triggers both unit and integration tests, the latter of which requires a test network to have been spun up apriori and takes a fair bit of time to execute. This makes things a bit more onerous for a person that just wants to explore the codebase. The solution to this, however, I think is a combination of a) separating the running of our integration tests from the standard build task, and b) using hardhat to minimise the overheads of the test network.


Decide and implement new name for kedro-datasets optional dependencies

The root cause of the problems we had last week (see #306) with the optional dependency group names in pyproject.toml is that kedro-datasets extras names just don't align with Python packaging standards: https://packaging.python.org/en/latest/specifications/core-metadata/#provides-extra-multiple-use

Provides-Extra (multiple use)
Changed in version 2.3: PEP 685 restricted valid values to be unambiguous (i.e. no normalization required).
...
A string containing the name of an optional feature. A valid name consists only of lowercase ASCII letters, ASCII numbers, and hyphen.

Therefore, pip install kedro-datasets[pandas.CSVDataSet] is out of line with current packaging standards.
From https://peps.python.org/pep-0685/:

When comparing extra names, tools MUST normalize the names being compared using the semantics outlined in PEP 503 for names:
re.sub(r"[-_.]+", "-", name).lower()
The core metadata specification will be updated such that the allowed names for Provides-Extra matches what PEP 508 specifies for names.

So, why was this working before? See also in the PEP:

Tools generating metadata MUST raise an error if a user specified two or more extra names which would normalize to the same name.

The reason is: setuptools hasn't fully implemented PEP 685 yet: https://github.com/pypa/setuptools/issues/3586
So, our mangling of extras in setup.py before https://github.com/kedro-org/kedro-plugins/pull/263 worked, but after transitioning to self-referential extras, we fell victims of name normalization.
I'm voting against switching to Poetry, Hatch, PDM, or any other system that allows this behavior, because it's going to bite us in the future. We need a short-term solution (either revert #263 or go for @DimedS #307) and a long term solution (possibly deprecating extras names with dots and offer an alternative syntax for our users).
Originally posted by @astrojuanlu in https://github.com/kedro-org/kedro-plugins/issues/306#issuecomment-1680094495

Notice that this is starting to creep up as we do dynamic inclusion of requirements.txt in projects pyproject.toml. This happened to me yesterday after installing a wheel coming from a kedro package:
❯ pip install ./spaceflights-namespaces/dist/spaceflights_namespaces-0.1-py3-none-any.whl                                                                                (advkedro310)
Looking in indexes<EMAIL_ADDRESS>Processing ./spaceflights-namespaces/dist/spaceflights_namespaces-0.1-py3-none-any.whl
...
WARNING: kedro-datasets 1.3.0 does not provide the extra 'pandas-csvdataset'
WARNING: kedro-datasets 1.3.0 does not provide the extra 'pandas-exceldataset'
WARNING: kedro-datasets 1.3.0 does not provide the extra 'pandas-parquetdataset'

Contents of requirements.txt:
kedro-datasets[pandas.CSVDataSet, pandas.ExcelDataSet, pandas.ParquetDataSet]~=1.0

(coming from https://github.com/kedro-org/kedro-starters/blob/38e81fba49702d0c8851ad4dcd488bafd08f1a36/spaceflights/{{ cookiecutter.repo_name }}/src/requirements.txt#L8)

Another user confused by this https://linen-slack.kedro.org/t/16176249/requirements-txt-line-11-3-8-2-warning-kedro-datasets-2-0-0-#72d04177-c93b-4199-8853-da3d59aa52e6

Extras with illegal names are not being pulled anymore in pip 23.3 onwards https://github.com/kedro-org/kedro-plugins/issues/553
This was already marked as high, but now it's affecting users for real cc @noklam @ankatiyar

The workaround for now is to tell users to install, say, kedro-datasets[pandas] instead of kedro-datasets[pandas.ParquetDataset], since the former is legal and the latter isn't. But still, this would pull lots of unneeded dependencies.

Sorry for the delayed response, and thank you for looking into this. Since you've been able to recreate the problem, it doesn't sound like you still need me to post the stacktrace. I've been using pipenv to manage my environments.
I'm actually a bit confused right now ... I just created a new kedro project. Piopenv sees the requirements.txt file and uses it. Previously this didn't seem to install pyarrow or fastparquet, and pandas displayed a warning message that one of those two packages was going to be a non-optional requirement. But my current project did in fact install pyarrow.

Another user have a problem. At first he has a bug where fastparquet is installed but ParquetDataset wouldn't work with a "file is closed" error. This is a legit bug itself.
But pyarrow should be the industry standard by now, he arrives this error because pip install kedor-datasets[optional] is missing the dependencies, and the error suggest user to install fastparquet or pyarrow.

The key decision here is: do we still want to provide an optional group per-dataset?
If yes, we have to decide a naming scheme.
If no, that's a breaking change (kedro-datasets 3.0?) but also the current non-standard names don't work anyway. And besides, the dataset groups already have legal names and we don't need to change those (kedro-datasets[pandas] etc).

From the Airflow 2.8.2 release notes:

Airflow extras now get extras normalized to - (following PEP-685) instead of _ and .
(as it was before in some extras). When you install airflow with such extras (for example dbt.core or
all_dbs) you should use - instead of _ and ..

https://github.com/apache/airflow/pull/36537
This is exactly our problem.

Fixed by #570, will see the light in the next release 👍🏽


Update flow-plugin-base, flow-server to 23.3.9

About this PR
📦 Updates

com.vaadin:flow-plugin-base
com.vaadin:flow-server

from 23.3.6 to 23.3.9
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (23.3.6).
You might want to review and update them manually.
build.sc
itest/src/skeleton-starter-flow-spring-v23.3.6/pom.xml

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.vaadin" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.vaadin" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #25.


Fix various lint issues - part 4

Bug: #60
Change-Id: If094a17e440e4e497561ab48d16a8550a4a5f3e3

Summary by CodeRabbit

Bug Fixes

Improved error handling and logging for file operations and database interactions across various functions.
Enhanced stability by catching and managing exceptions like FileNotFoundError and JSONDecodeError.

Refactor

Renamed variable nickname to user_display_name for clarity.
Adjusted logging and messaging within the rock-paper-scissors game logic.

@coderabbitai review


Progressive list rendering.

Change longer lists to render progressively in pieces rather than all at once in order to not block up the UI.

Automated message from Dropbox CLA bot
@brockwhittaker, it looks like you've already signed the Dropbox CLA. Thanks!

I'm not doing a thorough review on this yet, but, broadly, this seems like a really nice encapsulation, so I like the general direction it's heading.  I'd be curious to see how easily it could be extended to work for the buddy list, which is a little more dynamic in nature (but at the end of the day, just has single-item deletes/inserts to deal with, beyond what you've already done).

It would be possible on the list to proxy the array protoype and intercept incoming requests to display, but then again we may as well just use vue, in which case this closure will still exist but without the append to DOM code (just the append to DOM array code).

We should definitely have a unit-testing strategy for the main piece of this, which is the lazy list rendering.  If there are small pieces of this series that can be merged ahead of time, we should do try to work on getting those in first, and then spend some time making this code really testable.  Node tests can handle some jQuery interactions ok, but it might make sense to have some functions that are easily stubbable, which might change how the code is organized a bit.

This is really cool, but I'm not thrilled with how this has been developed, in that the last commit has a bunch of work that we're going to need to semi-redo due to merge conflicts, and that probably just shouldn't have been started until we had merged the framework and were happily using it in at least 1 place.  Oh well.
To try to expedite progress on this project, I merged the first 3 commits (all but actually using the framework), after tweaking a bunch of comments and other style things in the actual rendering implementation.  It's mostly harmless in that the code is unused, but I expect we'll need to do more work to make it work perfectly; but this should make it easy to work on the various pieces separately.
I think next we should proceed with 2 things in parallel:

Start merging few applications of this.  @brockwhittaker can you extract out the changes for e.g. the "stream subscribers" UI and submit a PR just adding those?  You only need to port the changes from the last commit (and given the changes, it might be easiest to just use the git show output for that last commit as a reference and redo things over trying to resolve merge conflicts).  And then we can add additional widgets as we go.
I agree that ideally we'd write a good test suite for this library.  @showell is probably best equipped to do that work; maybe makes sense to wait until we have 1 application working before starting on it.  I imagine there'll be some refactoring and cleanup as part of that process.

Thanks for working on this @brockwhittaker!  I'm going to close this PR -- we can use new PRs for further work on this.

@brockwhittaker @timabbott I'm happy to help on the unit tests.  I agree that the merge conflicts were a bit unfortunate (my fault, although I felt the admin split took priority), and perhaps a more incremental approach would have been better, but this is also really exciting, so I look forward to more progress here.


resolveRemoteChunk url is not working on my side

ChunkManager.configure({
resolveRemoteChunk: async (chunkId) => {
return {
url: http://localhost:5000/${chunkId},
};
},
});
@zamotany

I need some more information what's happening:

Do you test application in development mode or production?
Do you have additional server running on localhost:5000 which would serve the remote chunks?
Do you get any errors in the console/XCode/Android Studio?
Are you using Re.Pack's native module?
Are you using dynamic import(...) function or you're doing code splitting manually?

We'r testing on development mode.
I write localhost just for testing , but i'm using my own link, in which i upload JS file.
No i did'nt get any error from android studio. Application is running but chunk.manager function is not invoked.
I did'nt get your point but i'm using repack library.
Yes

Ok, in development mode all chunks are resolved and downloaded from the Development server. So resolveRemoteChunk is not called by design. By default the resolveRemoteChunk is only used in production mode.
Today I released a new version that allows to force the resolution to happen through resolveRemoteChunk.
Please read the updated documentation:

https://re-pack.netlify.app/docs/api/react-native/classes/ChunkManager
https://re-pack.netlify.app/docs/api/react-native/interfaces/ChunkManagerConfig#forceremotechunkresolution

In order to use Code Splitting from Webpack & Re.Pack in React Native, Re.Pack provides a native module. It should be automatically linked, but it's good to do pod install for iOS to make sure it's picked up.

I'm going to close this issue for now. If there are any more problems, feel free to reopen it.

Thank You soo much @zamotany

What's the error message of the crash you're getting?


Tapestry Loom: view HTML output in content section

First off, congratulations on the very successful Kickstarter campaign! I'm excited to back the project and see where this all goes.
Second, I'm not entirely sure where the best place for this is, so if the Kickstarter campaign's comments section is a better location for the following, let me know and I can re-post.
That said…
A modest feature request
…and a question:
What HTML markup is supported in a Post? I don't expect this is the entirety of HTML and the API docs are ambiguous.
Irrespective of the answer, it would be helpful if Tapestry Loom displayed (or had a button/toggle/etc.) to view the HTML output when viewing a Post. I'm thinking of the area at the bottom of the window beneath "Creator Avatar."

In the screenshot above, my plugin code has formatted the output with each line wrapped in a <p> element. It'd be useful to have some capability to examine the output to make sure it matches plugin author expectations, check for validity, etc. etc. etc.
Thanks for your consideration!

Closing this one as resolved by @chockenberry in 858fb58 and by an update to the Tapestry Loom beta (as noted in the new Tapestry Loom user guide).
Thanks so much! 🙌🏻


Don't depend on external resources in test

Currently, the test suite attempts to contact a number of sites during testing. Ideally, all these artifacts would be stored locally and DNS resolution mocked out to a local web server also started during test.

This app is essentially in maintenance mode and I'm not worried about these external deps. camo has been running for half a decade at GitHub so I think it's the type of thing that will be replaced before it's enhanced significantly.


Allow = as separator for named parameter default value

analyzer issue for #27634

This was implemented as part of the spec change CL from @lrhn.


Update interconnect-china.md

Updated because of doubled

@FloKlaffenbach : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign off


CASMTRIAGE-6385-1.6 : Stuck while terminating nexus-data PVC (Nexus recovery)

Description
Resolves CASMTRIAGE-6385 for CSM 1.6
Tested on starlord
Checklist

[ ] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[ ] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[ ] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.5


[WIP] feat: add api for token information

Resolves: https://github.com/Magickbase/ckb-explorer-public-issues/issues/374

hold on，the ui needs change here, and i18n resouce needs to be completed

Please convert this PR to a draft if it's still WIP(it's marked in the PR title)

How is it going

Please replace the content of the description

Term
Description

Token Type
Please select the Token Type based on the actual Cell type used for this SUDT.

Args
Args is the Args field in the Cell data structure in CKB. Please provide the Args field from this SUDT Cell.

Symbol
Symbol of the SUDT

Name
Name of the SUDT

Decimal
Decimal precision of the SUDT

Description
Description of the SUDT

Website
Website of the SUDT project or organization, if available

Creator Email
Email address of the creator of the SUDT project or organization. This is crucial for future updates to SUDT information.

Logo
Token logo for the SUDT

Please replace the content of the description
Term	Description
Token Type	Please select the Token Type based on the actual Cell type used for this SUDT.
Args	Args is the Args field in the Cell data structure in CKB. Please provide the Args field from this SUDT Cell.
Symbol	Symbol of the SUDT
Name	Name of the SUDT
Decimal	Decimal precision of the SUDT
Description	Description of the SUDT
Website	Website of the SUDT project or organization, if available
Creator Email	Email address of the creator of the SUDT project or organization. This is crucial for future updates to SUDT information.
Logo	Token logo for the SUDT

cc @zhangyouxin

ok I'll update description refer to provided infomation

The entries to update token info in the following places are not updated

Footer: https://ckb-explorer-frontend-in-magickbase-repo-git-24445f-magickbase.vercel.app/
NFT Collection Page: https://ckb-explorer-frontend-in-magickbase-repo-git-24445f-magickbase.vercel.app/nft-collections

Any update on this PR

Any update on this PR

The entries to update token info in the following places are not updated

Footer: https://ckb-explorer-frontend-in-magickbase-repo-git-24445f-magickbase.vercel.app/
NFT Collection Page: https://ckb-explorer-frontend-in-magickbase-repo-git-24445f-magickbase.vercel.app/nft-collections

After alignment with PM, the NFT info is different from sUDT, so it will be taken care of in another issue, and the footer will remain the same for now.

The upload action is performed when I click on the delete button
https://github.com/Magickbase/ckb-explorer-frontend/assets/7271329/fa32c40a-f18a-4b90-b7de-f2272a40578d


Update Bookstack from 22.04.2 to 23.05

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
Update Bookstack from 22.04.2 to 23.05
Download:
cd /var/www
git clone https://github.com/BookStackApp/BookStack.git --origin release --single-branch bookstackv23.05
cd bookstackv23.05
composer install --no-dev
Deprecation Notice: Using ${var} in strings is deprecated, use {$var} instead in                                                                                phar:///usr/local/bin/composer/vendor/symfony/console/Command/DumpCompletionCom                                                                                mand.php:48
Deprecation Notice: Using ${var} in strings is deprecated, use {$var} instead in                                                                                phar:///usr/local/bin/composer/vendor/symfony/console/Command/DumpCompletionCom                                                                                mand.php:56
Do not run Composer as root/super user! See https://getcomposer.org/root for det                                                                                ails
Continue as root/super user [yes]? yes
Deprecation Notice: Using ${var} in strings is deprecated, use {$var} instead in                                                                                phar:///usr/local/bin/composer/src/Composer/Autoload/AutoloadGenerator.php:881
Deprecation Notice: Using ${var} in strings is deprecated, use {$var} instead in                                                                                phar:///usr/local/bin/composer/src/Composer/Autoload/AutoloadGenerator.php:886

@php -r "!file_exists('bootstrap/cache/services.php') || @unlink('bootstrap/ca                                                                                che/services.php');"
[...]
63 packages you are using are looking for funding.
Use the composer fund command to find out more!
@php artisan cache:clear

INFO  Application cache cleared successfully.

@php artisan view:clear

INFO  Compiled views cleared successfully.
php artisan migrate
Do you really wish to run this command? (yes/no) [no]
❯ yes
In Connection.php line 760:
SQLSTATE[HY000] [1045] Access denied for user 'forge'@'localhost' (using password: NO) (SQL: select * from information_schema.tables where table_schema = forge and table_name = migrations and table_type = 'BASE TABLE')
In Connector.php line 70:
SQLSTATE[HY000] [1045] Access denied for user 'forge'@'localhost' (using password: NO)
I just want to Update. I am new to Bookstack. I need help, pls.
Exact BookStack Version
22.04.2
Log Content
No response
PHP Version
8.1
Hosting Environment
Ubuntu 22.04

Since there's been no further follow up I'll close this off.


Change in behavior between 3.3.2 and 3.4.0-RC3 for naming

Type of issue: bug report

Impact: naming behavior change (back to old behavior)

Development Phase: request
Other information

If the current behavior is a bug, please provide the steps to reproduce the problem:
Given a somewhat weird (but useful) pattern:
import chisel3._
import chisel3.stage.ChiselStage

class Example(n: Int) extends MultiIOModule {
  val out = Seq.tabulate(n) { i =>
    val ioOpt = (if (i % 2 == 0) None else Some {
      val x = IO(Output(UInt(8.W)))
      x
    })
    ioOpt
  }

  out.foreach(_.foreach(_ := 0.U))
}

println((new ChiselStage).emitVerilog(new Example(4)))

The type of val out is Seq[Option[UInt]], this is actually very useful because the inner option allows us to skip indices in the namespace when there are Nones:
What is the current behavior?
In Chisel v3.4.0-RC3, this gives:
module Example(
  input        clock,
  input        reset,
  output [7:0] out_ioOpt_x,
  output [7:0] out_ioOpt_x_1
);
  assign out_ioOpt_x = 8'h0; // @[main.scala 15:27]
  assign out_ioOpt_x_1 = 8'h0; // @[main.scala 15:27]
endmodule

What is the expected behavior?
In Chisel v3.3.2, this gives:
module Example(
  input        clock,
  input        reset,
  output [7:0] out_1,
  output [7:0] out_3
);
  assign out_1 = 8'h0; // @[main.scala 15:27]
  assign out_3 = 8'h0; // @[main.scala 15:27]
endmodule

What is the use case for changing the behavior?
Restore previous (useful) naming behavior

An example of what I suspect is the same issue happens in rocket-chip here: https://github.com/chipsalliance/rocket-chip/blob/c6b41bf5918bbafc7dccee70e208352e029d9505/src/main/scala/devices/debug/Periphery.scala#L112
Simple example of the bug: https://scastie.scala-lang.org/A2AN5lgAQHaRfWDFbOoyjQ
Example of a workaround: https://scastie.scala-lang.org/UQoz4TceRxCFQIWZx8S37A

This issue stems from the behavior of autoSeed on ports (https://github.com/freechipsproject/chisel3/blob/26deb7703389b78a9b2a61f7e191f3f0e2a6623b/core/src/main/scala/chisel3/Data.scala#L289). Basically, ports have special behavior where the first seed wins. The "first seed wins" is nice because it fixes https://github.com/freechipsproject/chisel3/issues/1352. It's not really clear how we both fix this issue and #1352.


Solution is unclear

This is described as one solution to multiple merge bases:   or merge target into main.  Could you provide more detail on this as I am unsure what is meant by this.

@shudson302 -- thank you for your feedback.  Are you following a particular docs.microsoft.com article?  Meanwhile, please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

For this issue, the Merge strategies and squash merge article wording “Either rebase your branch on target, or merge target into main” was probably intended to be “Either rebase your branch on target, or merge target into your branch”. However, I have doubts about whether a Git merge/rebase would work on branches that don’t have a common ancestor commit - more than likely Git will throw an error. I'll look into this and update the article.

Article link: https://docs.microsoft.com/en-us/azure/devops/repos/git/merging-with-squash

Ok, thank you for the clarification

I filed a PR to get the article updated. I'll add a comment to this issue once the article is updated.


Material Form Divider

VERSIONS:
Angular: 16.2.1
Angular Material: 16.2.1
Formly Core: 6.2.2
Formly material-legacy: 6.1.1
ISSUE
I am trying to add a material divider between certain form controls and I don't see it on the API or in the docs.
Am I missing it or is there a preferred way of accomplishing this ?
Any help would be appreciated.

Was able to resolve this using existing "Nested Forms" functionality.

Was able to resolve this using existing "Nested Forms" functionality.


VeaScan route to a specific message id

Route: /chainIdFrom/chainIdTo/msgid
❓Is a dedicated page per message necessary?
⚠ Assumes a single Vea deployment between these 2 chains where the msgId is unique.

imo, it would be the most useful feature of veascan.
after my cross-chain dapps sends a message to vea, i want to provide the user with information about that message, and track it's status, estimated time until successful bridging, a manual relay button if it's ready, etc.
imo this is why veascan is useful, everything else is a nice to have.
almost noone is interested in generic views, or even knowing about 'snapshots'


sink(ticdc): adjust sql mode compatibility for mysql sink

Signed-off-by: qupeng<EMAIL_ADDRESS>What problem does this PR solve?
Close #3810.
Check List
Tests

Unit test

Code changes
Side effects
Related changes
Release note
None

test fail

/run-verify

Codecov Report

Merging #3938 (72da0d9) into master (3873d39) will decrease coverage by 1.7669%.
The diff coverage is 63.9143%.

Flag
Coverage Δ

cdc
58.2917% <63.9143%> (+0.0551%)
:arrow_up:

dm
52.7631% <ø> (-3.2715%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #3938        +/-   ##
================================================
- Coverage   57.0741%   55.3071%   -1.7670%
================================================
  Files           478        484         +6
  Lines         56551      59231      +2680
================================================
+ Hits          32276      32759       +483
- Misses        20978      23162      +2184
- Partials       3297       3310        +13

/run-MySQL-integration

A little question:
Do we need a unit test to cover some detail scenes, like "0000-00-00 00:00:00" for timestamp? Or mockDB is sufficient  for this case?

A little question: Do we need a unit test to cover some detail scenes, like "0000-00-00 00:00:00" for timestamp? Or mockDB is sufficient for this case?

It's relative about how a sql mode handles uncompatible records. I think it's unnecessary because it's already described by MySQL document. So just testing the result of "select sql_mode from downstream" is enough.

/run-leak-test

/merge

/merge

/run-/dm-integration-test

/run-dm-integration-test

/run-cherry-picker


Enrollment with HCID failed for hctester100

[ ] Add to an appropriate Epic.

Tester (if different from issue creator):
Site: hcommons-dev.org
URL: https://registry.hcommons-dev.org/registry/co_people/canvas/127312
Test Account: hctester100
Area (CORE, sites, profiles, groups, general): enrollment
If issue discovered on dev, does it also exist on prod? No
Describe the issue
Tried to enroll hctester100 in HC with an HCID. Got an error on creating a username/password that the identifier was invalid. User ended up in confirmed status.
https://registry.hcommons-dev.org/registry/co_people/canvas/127312
Could not copy the error because it flashed at the top of the screen and disappeared. It then refreshed and gave me "An Internal Error Has Occurred."
Username was not created, had to search for user by email.
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Optional details, if they seem relevant
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This is fixed. Closing.


TypeScript: aggregate errors for file from all projects

I have a project with three folders, two of which are TS projects and the third of which is shared between them:

shared
service-worker (with tsconfig.json)
browser (with tsconfig.json)

Both "browser" and "service-worker" depend on "shared".
However, when I open a file in "shared", I only see errors related to one of the tsconfig.jsons—usually this will be the tsconfig.json  used for the file I navigated from previously.
It would be great if VSCode could aggregate all errors for the current file for all matching TS projects.

This issue was moved to Microsoft/TypeScript#20185


Plugin for Angular (v2+)

You have the "eslint-plugin-angular" package in your list but it's only for AngularJS (= Angular v1, deprecated).
An awesome one (maintained and widely used) for Angular (not AngularJS) is https://github.com/angular-eslint/angular-eslint

That is awesome to see. Do you mind making a pull request to add it to this list?

@dustinspecker Done is #182


Document dynamic network selection based on IP utilization

Feature Request
Document dynamic network selection based on IP utilization added in https://github.com/jenkinsci/openstack-cloud-plugin/pull/279

Hey, this is documented in Jenkins config UI. It can also be found on JENKINS_URL/configuration-as-code/reference. For your convenience this is the source https://github.com/jenkinsci/openstack-cloud-plugin/blob/master/plugin/src/main/resources/jenkins/plugins/openstack/compute/SlaveOptions/help-networkId.html

cool, thanks! Closing ...


Crash   when ship assemble

https://paste.dimdev.org/kofoxowapu.mccrash
Latest Jenkins VW

2
https://paste.dimdev.org/etebalomif.mccrash

I think I've fixed it. Try it again with build 442.


[React Native | Hermes] Code Push for Hermes-Enabled Apps in Monorepos

We have a React Native Android app within a monorepo, where the react-native package installs in the root-level node_modules.
Currently, when attempting to code push for a React Native app in a monorepo, the process fails when attempting to convert the JS bundle to byte code via Hermes (see output below).
Converting JS bundle to byte code via Hermes, running command:

node_modules/hermesvm/osx-bin/hermes -emit-binary -out /var/folders/q3/fzyknkyx3cv21d6lxj0k3vnw0000gn/T/code-push2020113-30003-1c4vji1.e8hb/CodePush/index.android.bundle.hbc /var/folders/q3/fzyknkyx3cv21d6lxj0k3vnw0000gn/T/code-push2020113-30003-1c4vji1.e8hb/CodePush/index.android.bundle
node:events:304
      throw er; // Unhandled 'error' event
      ^

Error: spawn node_modules/hermesvm/osx-bin/hermes ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:269:19)
    at onErrorNT (node:internal/child_process:465:16)
    at processTicksAndRejections (node:internal/process/task_queues:80:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:275:12)
    at onErrorNT (node:internal/child_process:465:16)
    at processTicksAndRejections (node:internal/process/task_queues:80:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn node_modules/hermesvm/osx-bin/hermes',
  path: 'node_modules/hermesvm/osx-bin/hermes',
  spawnargs: [
    '-emit-binary',
    '-out',
    '/var/folders/q3/fzyknkyx3cv21d6lxj0k3vnw0000gn/T/code-push2020113-30003-1c4vji1.e8hb/CodePush/index.android.bundle.hbc',
    '/var/folders/q3/fzyknkyx3cv21d6lxj0k3vnw0000gn/T/code-push2020113-30003-1c4vji1.e8hb/CodePush/index.android.bundle'
  ]
}

The problem is this function which assumes hermes-engine (or hermesvm) will be found within the project's node_modules. The react-native-codepush package threw errors with similar causes in the build process. These were solved by setting the nodeModulesPath in our project's gradle.properties.
An easy solution would be checking the app's gradle file for hermesCommand or nodeModulesPath values (as code push does here to determine whether to run hermes in the first place). This would also bring the code push cli behavior more in line with the code push package's build behavior. Then, perhaps, we could add some documentation about how AppCenter behaves with Hermes-enabled apps, as others have run into issues 1 2 2.
I tried implementing this with the intent of opening a PR but wasn't able to build appcenter-cli locally.
Also note that the cli doesn't detect that we're on<EMAIL_ADDRESS>because it's using hermesvm rather than hermes-engine. This may have something to do with react-native being installed at root node_modules.
Details:
appcenter cli: 2.7.3
react-native: 0.63.3
hermes-engine: 0.5.0
react-native-code-push: 6.4.0

Closing as fixed.


Cannot Detect IMU D435i

Required Info

Camera Model
D435i

Firmware Version
<IP_ADDRESS>.00

Operating System & Version
Linux (Ubuntu 22)

Kernel Version (Linux Only)
5.15.0-56-generic

Platform
PC

SDK Version
2.53.1

Language
{ python }

Issue Description
After following the tutorial for the linux installation and upgrading the firmware on my D435i, I can successfully viewer the RGB and Depth information in RealSense Viewer. I cannot view and IMU information and cannot even find the rs-imu-calibration script after 2 installs of the packages. Even trying the rs-motion example leads to a response of Device supporting IMU not found, which should not be the case.
I have not tried building it from source.
Tutorial I followed to install https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md#installing-the-packages

Hi @dariandzirko  Is the camera name shown as D435i at the top of the RealSense Viewer's options side-panel?

Oh wow the order and box said D435i but RealSense Viewer says D435. I missed that thanks.

The RealSense SDK identifies the camera name from the camera components that the firmware driver can detect.  So it may indeed be a D435i unit but is being identified by the firmware as an IMU-less D435 because the firmware cannot detect the IMU component for some reason.

Hi @dariandzirko  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


Make ln-dlc-node tests a bit more resilient

This was some work that I've been collecting as I've been trying to verify that the LN channel is usable after a DLC channel has been opened beside it.

bors r+


primary group changes when switching in between servers

primary group changes when switching in between servers. In the database it says I have the group but after I switch to a different server it says I'm back to default.

Check your UUID forwarding settings.
https://www.spigotmc.org/wiki/bungeecord-ip-forwarding/


Unable to push OCI Index manifests

Hi,
Not able to push an OCI Index manifest because the current implementation is trying to check the existance of the MediaType field.
specs.Versioned field in OCI Index manifest doesn't have MediaType field. While Versioned struct from Manifest List of docker/distribution has MediaType field.
Because of this, the current implementation is not compatible with OCI Index manifest and only works with Manifest List of docker/distribution

Closing this for now, It seems that I wasn't initializing my client properly.


Remove brittle spec

Provides no real value, since it stubs out the thing it was supposed to test.

haha funny. :+1:
while we're in here are we also able to remove this now?

Quite possibly, I'll remove it and see what happens.

:+1:

:+1:

:+1:


Add ability to provision persistent disks to agents (part1)

I continued the work:
Changes:

We compute the disks syntax and send it to the agent crd
In the operator you can configure the mapping between a type and storage class. Also you can define default storage class name and default disk size. Note that the storage class must already exists.


feat: Add plurals support to checkTranslations script

Proposed changes
What changed

i18next provides support for plurals, but plural forms differ between languages

https://www.unicode.org/cldr/cldr-aux/charts/29/supplemental/language_plural_rules.html
lodash.differenceWith is used to apply a set difference over the language keys

Why did it change

Issue tracking

Checklists
Environment variables or secrets

[x] No environment variables or secrets were added or changed

Other considerations

[ ] Update README with any new instructions or tasks

Nice use of Loadash, we could probably simplify the script even more by looking at other loadash features. But a story for another time

Yeah, there's some set theory stuff that could be useful here, but it's a little too tricky to pick apart at the moment. I think we'd need it if we decided to support a 3rd language, but hopefully by then we'll generally have a more robust solution in place :)


feat(ToolBar): Add logo to top navigation - UX Improvement: add Logo …

…#260
Add logo to top navigation - UX Improvement: add Logo #260

Codecov Report

Merging #285 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #285   +/-   ##
=======================================
  Coverage   79.62%   79.62%
=======================================
  Files          17       17
  Lines         216      216
  Branches        9        9
=======================================
  Hits          172      172
  Misses         42       42
  Partials        2        2

Continue to review full report at Codecov.

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

thx @cschomer!


pangeo-forge-runner error handling is broken

I just called a recipe test here https://github.com/pangeo-forge/staged-recipes/pull/183#issuecomment-1251257574
The resulting pangeo-forge-runner subprocess call failed with a KeyError

2022-09-19T16:31:51.157842+00:00 app[web.1]: subprocess.CalledProcessError: Command '['pangeo-forge-runner', 'bake', '--repo=https://github.com/eooffshore/staged-recipes', '--ref=037542663cb7f7bc4a04777c90d85accbff01c8c', '--json', '--prune', '--Bake.recipe_id=eooffshore_ics_cmems_WIND_GLO_WIND_L3_NRT_OBSERVATIONS_012_002_MetOp_ASCAT', '-f=/tmp/tmp5_e7dib5.json', '--feedstock-subdir=recipes/eooffshore_ics_cms_WIND_GLO_WIND_L3_OBSERVATIONS_Metop_ASCAT']' returned non-zero exit status 1.
2022-09-19T16:31:51.157842+00:00 app[web.1]:
2022-09-19T16:31:51.157842+00:00 app[web.1]: During handling of the above exception, another exception occurred:
2022-09-19T16:31:51.157843+00:00 app[web.1]:
2022-09-19T16:31:51.157843+00:00 app[web.1]: Traceback (most recent call last):
2022-09-19T16:31:51.157844+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/uvicorn/protocols/http/h11_impl.py", line 373, in run_asgi
2022-09-19T16:31:51.157844+00:00 app[web.1]: result = await app(self.scope, self.receive, self.send)
2022-09-19T16:31:51.157851+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/uvicorn/middleware/proxy_headers.py", line 75, in __call__
2022-09-19T16:31:51.157851+00:00 app[web.1]: return await self.app(scope, receive, send)
2022-09-19T16:31:51.157851+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/fastapi/applications.py", line 208, in __call__
2022-09-19T16:31:51.157852+00:00 app[web.1]: await super().__call__(scope, receive, send)
2022-09-19T16:31:51.157852+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/applications.py", line 112, in __call__
2022-09-19T16:31:51.157853+00:00 app[web.1]: await self.middleware_stack(scope, receive, send)
2022-09-19T16:31:51.157853+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/middleware/errors.py", line 181, in __call__
2022-09-19T16:31:51.157853+00:00 app[web.1]: raise exc
2022-09-19T16:31:51.157854+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/middleware/errors.py", line 159, in __call__
2022-09-19T16:31:51.157854+00:00 app[web.1]: await self.app(scope, receive, _send)
2022-09-19T16:31:51.157854+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/middleware/cors.py", line 84, in __call__
2022-09-19T16:31:51.157855+00:00 app[web.1]: await self.app(scope, receive, send)
2022-09-19T16:31:51.157855+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/exceptions.py", line 82, in __call__
2022-09-19T16:31:51.157855+00:00 app[web.1]: raise exc
2022-09-19T16:31:51.157856+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/exceptions.py", line 71, in __call__
2022-09-19T16:31:51.157856+00:00 app[web.1]: await self.app(scope, receive, sender)
2022-09-19T16:31:51.157856+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/routing.py", line 656, in __call__
2022-09-19T16:31:51.157856+00:00 app[web.1]: await route.handle(scope, receive, send)
2022-09-19T16:31:51.157857+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/routing.py", line 259, in handle
2022-09-19T16:31:51.157857+00:00 app[web.1]: await self.app(scope, receive, send)
2022-09-19T16:31:51.157857+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/routing.py", line 64, in app
2022-09-19T16:31:51.157858+00:00 app[web.1]: await response(scope, receive, send)
2022-09-19T16:31:51.157858+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/responses.py", line 159, in __call__
2022-09-19T16:31:51.157858+00:00 app[web.1]: await self.background()
2022-09-19T16:31:51.157859+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/background.py", line 35, in __call__
2022-09-19T16:31:51.157859+00:00 app[web.1]: await task()
2022-09-19T16:31:51.157859+00:00 app[web.1]: File "/usr/local/lib/python3.9/dist-packages/starlette/background.py", line 18, in __call__
2022-09-19T16:31:51.157859+00:00 app[web.1]: await self.func(*self.args, **self.kwargs)
2022-09-19T16:31:51.157860+00:00 app[web.1]: File "/opt/app/pangeo_forge_orchestrator/routers/github_app.py", line 838, in run_recipe_test
2022-09-19T16:31:51.157860+00:00 app[web.1]: await run(*args, **kws, gh=gh, db_session=db_session)
2022-09-19T16:31:51.157860+00:00 app[web.1]: File "/opt/app/pangeo_forge_orchestrator/routers/github_app.py", line 618, in run
2022-09-19T16:31:51.157860+00:00 app[web.1]: if p["status"] == "failed":
2022-09-19T16:31:51.157861+00:00 app[web.1]: KeyError: 'status'

which indicates that the assumption that failed pangeo-forge-runner calls will always provide a log line with a "status" field
https://github.com/pangeo-forge/pangeo-forge-orchestrator/blob/ac024db502586aaba7340949e977424c54509b10/pangeo_forge_orchestrator/routers/github_app.py#L615-L618
is faulty.

Note: the patch implemented in #154 can be removed if/when this issue is resolved upstream.


Stop the bot from walking on water

Expected Behavior
It's not really expected to walk on water, I'm a pokémon trainer not Jesus.
Actual Behavior
Does not care about water at all, just walks on it.

Why does it matter? You could be using a boat.

I seem too looooove boats then, and I have a lot of them!
It matters as it's pretty easy to detect this is a bot, and we should try to avoid that. It's not the most important thing right now, but it's good to know for the future - and maybe someone with nothing to do can look into how you detect water with the Google Maps API :-)

I feel like this could be a useful addition too, as when near water it does tend to cross it often, which could look odd to a bot-detection system.
However, I think simply setting the start location somewhere away from water is a fairly viable solution for now.

@kaise123 That is a solution for now, but I think that there are other ways that are easier to detect so for now it's not so important.

Maybe just get path by google api (from current point to next point) and walk by this path?

Yes, that seems like a good way to do it, and would seem pretty human as well for bot detection.

@Saturate and simulate not accurate gps signal :) Its very hard for detect more bots, maybe.

i suggest to change the issue with an IMPROVEMENT tag

Guys, really some people may care about this feature, other don't. If this gets implemented can you make it optional in a config like "traverses_everything". I really don't mind this behavior... Thanks!

@Saturate question offtopic, how did you make your bot put a red dot on his path

@mehdi-S Update the web submodule and it's a setting


snprintf函数第二个参数应该为buf_len + 1

What problem were solved in this pull request?
Issue Number: close #xxx
Problem:
What is changed and how it works?
Other information

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.gzj seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

You're right. But you submitted the code with wrong author.

You're right.

You're right.

Please refer to
https://www.bing.com/search?q=git+reset+--amend+reset+author&qs=n&form=QBRE&sp=-1&lq=0&pq=git+reset+--amend+reset+auth&sc=0-28&sk=&cvid=4F3F85037952481E9EAB0F3B612B77DD&ghsh=0&ghacc=0&ghpl=

And you should config your email to your github email first.


Update overview.md

minor update

Docs Build status updates of commit 52bb0d6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/overview.md
:bulb:Suggestion
View
Details

msteams-platform/overview.md

Line 77, Column 29: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/graph/teams-concept-overview' will be broken in isolated environments. Replace with a relative link.
Line 155, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/javascript/api/@microsoft/teams-js/?view=msteams-client-js-latest&preserve-view=true' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit c34ad7a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/overview.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Parse vCard from QR-code

Storing the QR code in a vcard format. Is there any option in this module to parse the vcard that is embed in a QR code that is saved in a png or jpeg format? Or the string vcard can we process using this library?

You can parse the vCard string from the QR Code.
https://github.com/jeroendesloovere/vcard#parsing-examples

But i can see only the option to parse from the .vcf file only, not from the image files like .png or .jpeg. Can i just rename the .vcf  extension to that .png or .jpeg

Handling QR codes is not something jeroendesloovere/vcard library handles.
You need another library to read the "text" from the QR-image.
With that "text" (= string) you can probably parse it to a vCard.

Yes got it clear.

Will this plugin work in php 7? When i run composer command i got like this

Can you try composer install jeroendesloovere/vcard:^1.6 ?

This is also not working for me

Sorry, typo, should be: composer require jeroendesloovere/vcard:^1.6

Again same issue.

Can you remove the vendor folder and the composer.lock file?
Then execute the command again.
Are you using the vcard-bundle?

No


need to build source and binary distributions

Under ASF guidelines, projects deliver source releases. Binaries like jars are a convenience.
See https://logging.apache.org/log4j/2.x/download.html for an idea of what the official downloads are meant to look like.
We will deliver jars to Maven Central too - but we also need to these source and binary distributions - typically in tgz and zip formats.
https://github.com/apache/daffodil appears to use sbt-native-packager plugin to create these. Release are downloaded from https://daffodil.apache.org/releases/3.4.0/
https://github.com/apache/incubator-nlpcraft also has a sbt build (not many ASF projects do) - but it also has a maven build and it isn't immediately clear how they package their distros.
There are other sbt plugins that may be a better fit - https://index.scala-lang.org/xerial/sbt-pack is one worth looking at
The source archive will probably just be a snapshot of the files in the git repo at release time - possibly with some stuff pruned. We should probably have a separate markdown file that describes the sbt commands to build the jars and docs.
The binary archive is a bit more problematic. For an app like Apache Spark, the bin archive provides a 1 stop solution for getting all the jars and the shell scripts to run spark-submit, the Spark REPL, etc.
A Pekko binary archive would include all the Pekko jars built for this Git repo and all the dependency jars. We should probably aim to have one or more sample apps and the shell (or sbt) scripting necessary to run those sample apps. These sample apps can be very simple examples that just prove that the jars all work together.
References

https://infra.apache.org/release-distribution

I couldn't really find any sbt plugins that support generating source distributions in the right format.
I have worked on some prototype code that can ultimately be rewritten to work in sbt - https://github.com/pjfanning/source-dist

we have a solution - I'm sure it could be better but I think it is sufficient for a 1.0.0 release


Support/no more setup toolchain

Ticket

A problem unearthed by this is that the Ledger runners don't seem to have KVM: https://github.com/LedgerHQ/ledger-live/actions/runs/11705866070/job/32606630914?pr=8308#step:7:36


Fix update snapshots for ml

Doh!

Coverage remained the same at 92.134% when pulling eb862228885aa51b9da2aa8943d35a64460367ba on fix-update-snapshots-for-ml into 8372fa61acc99db96c35a7c5464b08b311c43609 on master.


the lib super sensetive to GHC version

I tried 8.10.1, 8.10.4, 8.8.4 and 8.4.4
Only 8.4.4 is working. Others fail on step of building true-name.
Warning: /home/dan/.stack/config.yaml: Unrecognized field in ConfigMonoid: compiler
WARNING: Ignoring p's bounds on template-haskell (==<IP_ADDRESS>); using template-haskell-<IP_ADDRESS>.

last applicable template Haskell library version is not compatible with base for ghc 8.10

I wanted to use this library to debug GHC api (parseDynamicFlags returns type without Outputable/Show instances).

Fixed in release <IP_ADDRESS>


Create dist directory in BuildFromSource

In preparation of #19, I thought it might be useful to bundle all resources that are necessary for a working installation into one directory. Being a total Haskell noob, there are probably way nicer ways of achieving the same thing, but I wanted to know first whether you think that this is reasonable approach in general.
If you set your ELM_HOME to $INSTALL_DIR/Elm-Platform/0.13/dist/share and add the bin to your $PATH respectively, you can directly use it.

I guess this is outdated and can be closed?

Yep, you're right.


[Feature Req] code-generator: needs to support custom find_operation

Is your feature request related to a problem?
In case 'Find' api is not available for a resource, I see that code-generator returns return nil, ackerr.NotImplemented in sdkFind() function. There doesn't seem to be a way to write custom find function.
I see that there is custom function available for update method using update_operation tag in generator.yaml. But I dont see find_operation tag where we can specify custom function for find operation.
As an example, there is not find method available for https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateNetworkAclEntry.html
But I can write custom code using https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeNetworkAcls.html and extract network_acl_entries from network_acl.
But I don't see an easy way to add this custom find function
Describe the solution you'd like
The solution would allow us to implement custom find function. The name could be written in generator.yaml as find_operation: <name-of-function> similar to update_operation. And generated code for sdkFind() would call this custom find function. The find function itself could be written in hooks.go.
Describe alternatives you've considered
My first try was to use hooks (sdk_read_one_pre_build_request, sdk_read_many_pre_build_request, etc) to get around this problem. But when find function is not available, then find related hooks are not effective. Because code-generator takes templates/pkg/resource/sdk_find_not_implemented.go.tpl path (where hooks logic is not available), instead of templates/pkg/resource/sdk_find_read_many.go.tpl, where hooks logic is available.

@nnbu you need to put the following in your generator.yaml file:
operations:
  DescribeNetworkAcls:
    operation_type: READ_MANY
    resource_name: NetworkACL

and the code-generator should be able to figure things out from there.

@jaypipes Thanks for reviewing.
However, there are 2 different apis for 2 resources networkAcl and networkAclEntry.
There is create, describe, delete apis for networkAcl.
But there is only create and delete apis for networkAclEntry. It does not have describe/find api.
The concern here is for supporting networkAclEntry resource. Of course, that will be done after supporting networkAcl resource, which should not have any problem.
The way to verify if networkAclEntry resource is existing or not, is to check describeNetworkAcl resource and iterate over networkAclEntry list inside it and figure out if the networkAclEntry is existing or now. That is why it needs a custom find function.

@nnbu OK, yeah, I think it would be best to only create a NetworkACL resource and have a Spec.Entries custom field on that NetworkACL resource that corresponds to the CreateNetworkAclEntry/DeleteNetworkAclEntry calls. This is how I did things for the IAM controller's Role, User and Group resources which each have a Spec.Policies field. This Spec.Policies field is defined in the generator.yaml file and populated with custom code hooks

@jaypipes  I see. Let me check this way of handling this using custom hooks.
Btw, irrespective of this case, do you think that we should have a way to write custom find function similar to custom update function?

@jaypipes  I reviewed your suggestions.
There are a few differences between IAM's group, policy groupPolicy related change and EC2's networkACL, networkACLEntry.

In case of IAM, group and policy are the actual resources, whereas groupPolicy provides association between group and policy. i.e. user creates group and policy independently. and then associates them together using groupPolicy. So, in this case, we are able to have group and policy in generator.yaml under resources section.

In case of networkAcl and networkAclEntry, networkAcl is purely a resource. But networkAclEntry is a resource as
well as association. i.e. We cant create  networkAclEntry without having networkAcl. So, we must have networkAcl
and networkAclEntry in resources section in generator.yaml.

For all the resources in generator.yaml, there needs to be find/describe operation available. Otherwise IUC, find-not-implemented kicks in and thereby stalls reconciler's progress.

If this understand is correct, then networkAclEntry needs to have find function available.
In IAM's case, in fact, we have find function available for all group, policy and groupPolicy. So, we did not face this issue. But networkAclEntry does not have find available. I feel that is the problem here. wdyt?
[As a side note, in IAM's case, policy has arn to uniquely identify it which you used in generator.yaml. But networkAclEntry does not have arn. This is secondary at this time because the main issue, IMO, is the need to have find function for resources defined in generator.yaml. ]


SMI adapter should be installed into istio-system namespace

Description
The SMI adapter installation uses the namespace chosen in Meshery UI. So the servicaccount and deployment are created in whatever namespace is chosen. But - it leaves the clusterrolebinding unchanged - like this:
     - kind: ServiceAccount
           name: smi-adapter-istio
           namespace: istio-system

this causes the SMI adapter pod to fail because it has no permissions.
Expected Behavior
As I see it we should:
either - install SMI adapter into istio-system no matter what is chosen in UI
or - modify the 'clusterrolebinding' to grant the permissions to serviceaccount in the chosen namespace.
I'm in favor of the first option as this will be in line with the way Istio itself is installed.

[Optional] To Reproduce
Steps to reproduce the behavior:

Get Meshery connected to a K8s cluster
Install Istio
Without changing namespace - install SMI adapter
See that SMI adapter deployment is created in 'default' namespace and the pod enters CrashLoopBackoff

@leecalcote @girishranganathan are you ok with always installing SMI adapter into istio-system? If yes - I think I already know where to fix this. :)

After discussion on my hasty PR - it's better to properly support user-defined namespaces.
Should probably be done after https://github.com/layer5io/meshery-istio/issues/29, even though there is no direct dependency.

Good! The quality of work in this write up warms my heart.


'Validates entity fields in repository findBy, findBy*, findOneBy, findOneBy*, count and countBy* method calls' not working anymore

This seems not working anymore with the last version (0.12.42):
Validates entity fields in repository findBy, findBy*, findOneBy, findOneBy*, count and countBy* method calls.

The result seems to be recognized only as a plain object. I got tons of errors aka

expects App\Entity\XXX, object given.
Call to an undefined method object::getId().

After reverting to version 0.12.39 the errors are gone.
Example Call:
$ticket = $this->entityManager->getRepository(Ticket::class)->find($ticketId);

Using $ticket as parameter in method with type Ticket results in error:
Parameter #1 $ticket of method  App\Service::method() expects App\Entity\Ticket,  object given.

Hi, it's most likely that the type was previously mixed for you and that this shows some kind of bug you have in your codebase. Can you please add these calls and let me know what PHPStan outputs for the file?
\PHPStan\dumpType($this->entityManager);
\PHPStan\dumpType($this->entityManager->getRepository(Ticket::class));
\PHPStan\dumpType($this->entityManager->getRepository(Ticket::class)->find($ticketId));

Also: are you using the objectManagerLoader option or not?
Thanks!

Thanks for quick response. Here is the output:
Dumped type: Doctrine\ORM\EntityManagerInterface
Dumped type: App\Repository\TicketRepository<App\Entity\Ticket>
Dumped type: mixed

I have this in my phpstan.neon.dist:
  doctrine:
    objectManagerLoader: tests/phpstan-object-manager.php

with tests/phpstan-object-manager.php:
<?php declare(strict_types=1);

use App\Kernel;

require dirname(__DIR__).'/tests/bootstrap.php';

$kernel = new Kernel($_SERVER['APP_ENV'], (bool) $_SERVER['APP_DEBUG']);
$kernel->boot();

return $kernel->getContainer()->get('doctrine')->getManager();
```

If the last one is mixed, then you cannot be getting this error:
Parameter #1 $ticket of method  App\Service::method() expects App\Entity\Ticket,  object given.

Also, are you ever overriding the find method in your custom repository classes?
Also, this doesn't make much sense to me: App\Repository\TicketRepository<App\Entity\Ticket> - can you show me your generic annotations for your repositories?

Sorry, this was the output for version 0.12.39. For version 0.12.42 i get following output:
  76     Dumped type: Doctrine\ORM\EntityManagerInterface
  77     Dumped type: App\Repository\TicketRepository<App\Entity\Ticket>
  78     Dumped type: object|null

No i didn't override find methods.
The Repository has no specific annotations:
class TicketRepository extends ServiceEntityRepository
{

For the entity Ticket
#[Entity(repositoryClass: TicketRepository::class)]
#[Table(name: 'table_ticket')]
class Ticket
{

So this error is kind of expected. You should be getting an error stemming from the fact you're missing @extends above your TicketRepository class:
/** @extends ServiceEntityRepository<Ticket> */
class TicketRepository extends ServiceEntityRepository
{

Test this and let me know if it works!

It works:
  76     Dumped type: Doctrine\ORM\EntityManagerInterface
  77     Dumped type: App\Repository\TicketRepository<App\Entity\Ticket>
  78     Dumped type: App\Entity\Ticket|null

Ok, then this only worked so far because the return type was mixed. Then I will now mark all my repositories accordingly.
Thank you very much for your help and your work.

If you're on level 6 and NOT have checkGenericClassInNonGenericObjectType: false in your phpstan.neon then you should be getting a PHPStan error about the missing @extends :)


Suspicion value not being updated properly

The suspicion nbt tag is not being updated with the actual sus value

I think it's actually working as intended (tm). After suspicion value is higher than (default) 200, it is reset, player is kicked and number of kicks is increased by one.

I think it's actually working as intended (tm). After suspicion value is higher than (default) 200, it is reset, player is kicked and number of kicks is increased by one.

Oh, that would definitely explain that then

Oh, that would definitely explain that then


Cannot Add Org. User via Web Interface

Is this a bug or a feature request?
Bug
What did you expect?
To be able to create an Org. User from the web interface.
What happened?
Blank page with nothing on it.
What version are your using?
Docker quick start: brocaar/loraserver-docker@6f576509924e41d31c9b282518014c49c25a57d6 which uses the docker image loraserver/lora-app-server:3 I also tested the loraserver/lora-app-server:latest image, both versions exhibit the issue.
How can your issue be reproduced?

Start Loraserver et al.:

$ git checkout https://github.com/brocaar/loraserver-docker.git
$ cd loraserver-docker
$ sudo docker-compose up

Browse to http://localhost:8080 and login as admin
Select lorawan organization
Select Org. Users
Press Add button

N.B. Tested with both Firefox and Chrome, OS: Ubuntu
Could you share your log output?
docker-3.log
docker-latest.log
firefox_console.log
google_chrome_console.log

Thanks for reporting, I've just pushed a fix.

Can this somehow be added to a stable docker release, or do I have to go with latest?
It's a rather critical feature ;)


CONUS404 GLOBUS-Black Pearl data release

Hi all - starting a thread to discuss Black Pearl - GLOBUS endpoint.
@rviger-usgs are you on board with doing a formal data release on ScienceBase if Jeff Falgout gives us the green light?
I believe that means our DOI for CONUS404 would now be pointing to the ScienceBase page (not the Drupal page), right? We will need to update that information in a few places, I imagine.
FYI: @kadunne-usgs @rsignell-usgs @alamotte-usgs

Hi Amelia,
I guess I'd like to make sure no one has an objection based on cost or anything before going from web release to data release. If not, I'm all for it.
The planned page is not intended to directly serve the data content itself, it is a way to aggregate more than one way to pull the content but keep literature citations pointing at a single DOI (regardless of which endpoint a user opted to use). If we can ensure the ScienceBase page can do the same, then yes let's point the DOI at the ScienceBase page. Would be great if we can use the text for the planned drupal page in Sciencebase.
I'm okay with exploring using a ScienceBase/Globus/Black Pearl endpoint as a public distribution channel.

I'm excited about having an endpoint from which people (including us) can actually retrieve the data!   We still anticipate folks will mostly be using our "non-authoritative" access points instead of the globus link to the tape archive, but this seems like a much better path than a web release workaround.

@rviger-usgs - Is there anyone we should check with on the cost or other potential objections besides ScienceBase, Dave, and Jeff Falgout?

@amsnyder Those three are good. Once we have the technical consensus and any policy thoughts, I'll want to take this to WMA management, if only to let them know of any shift in the plan around the release of CONUS404.

I think I've located most/all of the data on Black Pearl and tracked it in our CONUS404 versions list.
I asked Kyoko for her plans of how and when she will push new years of data to Black Pearl - we might need to talk to SB about making updates to our GLOBUS endpoint and having data release revisions as these years become available.
We have invited Jeff Falgout to the HyTest meeting tomorrow to discuss more, but waiting to hear back if he is available.

After meeting with Jeff, we seem to be in agreement that we will do a data release with a GLOBUS - Black Pearl endpoint.
We need to send Jeff our DOI for the data release. @alamotte-usgs is checking on if we can throw out the DOI he already made so that we can use the DOI that is auto-generated by the ScienceBase data release tool. If we switch to a new DOI, we will need to update (1) the metadata.xml file and (2) send to NCAR for their use in RDA, if it is pursued.
Once we have our final DOI, Jeff will make a GLOBUS endpoint and give me access. I will transfer the wrfout, auxhist24, and wrfxtrm files (see here for details) for all water years into the bucket Jeff has made. @kadunne-usgs - We need to ask Kyoko if we can delete the files from their current locations in /wrfconus404-disk/ and /wrfconus404/ once we have transferred them. She will have access to this new public endpoint, but we want to make sure it won't create any issues with her workflows that she is using.
@alamotte-usgs and I will work on creating the IPDS record and ScienceBase page for the data release today or on Monday.
We know that Kyoko will be adding new years of data as they become available and we will want to add them to the data release. Jeff says adding these to the GLOBUS endpoint will be easy. For the ScienceBase page, we will need to go through a level 3 revision process, which is supposed to be pretty straightforward.
We discussed the cost of this long term storage a bit. We don't have any firm numbers, but we think worst case scenario is $10-15k per decade of storage.
@rviger-usgs @alamotte-usgs - did I miss anything here?

Do you know if we will be able to link to other access pathways (e.g. AODS, RDA) from the ScienceBase page?

@kadunne-usgs I believe we can updated SB pages to include links of related publications/releases after publishing. Happy to dig into this if @alamotte-usgs doesn't know the answer - but let's see if he has input first.

@kadunne-usgs yes, a Sciencebase page can point to multiple endpoints (the John Warner example does this, in fact).
@amsnyder yes, think you've got everything! amazing job. thanks for that. The only thing that we might want to add to that is to have Kyoko or whoever on the NCAR end formally notify us whenever there's a new increment to add to the raw CONUS404 historical dataset.

@rviger-usgs  We will use the previously reserved DOI: 10.5066/P9PHPK4F or to be precise: HTTPS://doi.org/10.5066/P9PHPK4F and the metadata will need to be updated. One thing to consider is the messaging with the data release. It should be painfully clear that the GLOBUS endpoint is probably not the preferred data that a modeler is looking for and has a large download time investment. [or something like that]

@alamotte-usgs understand re: preferred channel. I'm guessing we'd add that language after the initial release (since there won't be another channel until after the initial release). Same applies to adding additional variables to the cloud version (which won't exist initially). Could definitely include warning about usability of the default download channel. I asked Jeff F re: performance; he'll be getting back to us (week after next would be the earliest).


Switch to root user

[x] Update ansible.cfg
[x] Update playbook in README
[x] Release major version

https://github.com/iancleary/ansible-role-docker/releases/tag/v2.0.0


Unable to set width of component to 100% inside Tooltip

If I wrap a component in Tooltip, I am not longer able to set the width of the inner component to 100% and have it fill the outer container. I can see that the Tooltip creates a div that wraps the contents that looks like this:

...

It's that fit-content that is causing me problems, but I don't see any way to access it. I can only change the behaviour of the tooltip window that pops up with e.g. dmc.Tooltip(..., w='100%').
If I set the className of the tooltip, that does show up in that div, but setting width in a stylesheet is overridden by the fit-content.
Any ideas on how I can change that value, or where it is being set?

@CNFeffery, sure! I should have included one in the first place, sorry about that.
import dash_mantine_components as dmc
import dash

app = dash.Dash(__name__)

app.layout = dmc.MantineProvider(
    children=dmc.Stack(
        [
            dmc.Textarea(value="This one stretches to the full width of the stack container", w="100%"),
            dmc.Tooltip(
                label="tooltip label",
                children=dmc.Textarea(
                    value="I would expect this one to also fill the full width, but it does not.", w="100%"
                ),
            ),
        ],
        w="500px",
        style={"border": "1px solid black"},
    )
)

if __name__ == "__main__":
    app.run_server(debug=True

@TimChild As an inline style, it is challenging to address the issue with DMC. I suggest you consider using fac.AntdTooltip() (
https://fac.feffery.tech/AntdTooltip ). Here is a simple example:

import dash_mantine_components as dmc
import feffery_antd_components as fac
import dash

app = dash.Dash(__name__)

app.layout = dmc.MantineProvider(
    children=dmc.Stack(
        [
            dmc.Textarea(
                value="This one stretches to the full width of the stack container", w="100%"),
            dmc.Tooltip(
                label="tooltip label",
                children=dmc.Textarea(
                    value="I would expect this one to also fill the full width, but it does not.", w="100%"
                ),
            ),
            fac.AntdTooltip(
                dmc.Textarea(
                    value="I would expect this one to also fill the full width, but it does not.", w="100%"
                ),
                title='tooltip label'
            )
        ],
        w="500px",
        style={"border": "1px solid black"},
    )
)

if __name__ == "__main__":
    app.run_server(debug=True)

@CNFeffery Thanks. Your component does have the desired behaviour I was looking for there.
@snehilvj , Any chance this is an easy thing to fix in dash-mantine-components? Or am I overlooking the reason why the fit-content inline style is applied in the first place?

You can override the width of the wrapping box by setting the boxWrapperProps property accordingly.
from dash import Dash, dcc, _dash_renderer
import dash_mantine_components as dmc

_dash_renderer._set_react_version("18.2.0")

app = Dash(external_stylesheets=dmc.styles.ALL)

app.layout = dmc.MantineProvider(
    children=dmc.Stack(
        [
            dmc.Textarea(value="This one stretches to the full width of the stack container", w="100%"),
            dmc.Tooltip(
                label="tooltip label",
                children=dmc.Textarea(
                    value="I would expect this one to also fill the full width, but it does not.", w="100%"
                ), boxWrapperProps={"w": "100%"}
            ),
        ],
        w="500px",
        style={"border": "1px solid black"},
    )
)

if __name__ == "__main__":
    app.run_server(debug=True)

I opened an issue in the dmc-docs, so I'll close this here.


Release v0.7.2

Release Checklist

[ ] All OWNERS must LGTM the release proposal
[x] Verify that the changelog in this issue is up-to-date
[x] For major or minor releases (v$MAJ.$MIN.0), create a new release branch.

[x] an OWNER creates a vanilla release branch with
git branch release-$MAJ.$MIN main
[x] An OWNER pushes the new release branch with
git push release-$MAJ.$MIN

[x] Update things like README, deployment templates, docs, configuration, test/e2e flags.
Submit a PR against the release branch:
[ ] An OWNER prepares a draft release

[ ] Write the change log into the draft release.
[ ] Run
make artifacts IMAGE_REGISTRY=registry.k8s.io/jobset GIT_TAG=$VERSION
to generate the artifacts and upload the files in the artifacts folder
to the draft release.

[x] An OWNER creates a signed tag running
git tag -s $VERSION
and inserts the changelog into the tag description.
To perform this step, you need a PGP key registered on github.
[x] An OWNER pushes the tag with
git push $VERSION

Triggers prow to build and publish a staging container image
gcr.io/k8s-staging-jobset/jobset:$VERSION

[ ] Submit a PR against k8s.io,
updating k8s.gcr.io/images/k8s-staging-jobset/images.yaml to
promote the container images
to production:
[ ] Wait for the PR to be merged and verify that the image registry.k8s.io/jobset/jobset:$VERSION is available.
[ ] Publish the draft release prepared at the Github releases page.
[ ] Add a link to the tagged release in this issue:
[ ] Send an announcement email to<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>with the subject [ANNOUNCE] JobSet $VERSION is released
[ ] Add a link to the release announcement in this issue:
[ ] For a major or minor release, update README.md and docs/setup/install.md
in main branch:
[ ] For a major or minor release, create an unannotated devel tag in the
main branch, on the first commit that gets merged after the release
branch has been created (presumably the README update commit above), and, push the tag:
DEVEL=v0.$(($MAJ+1)).0-devel; git tag $DEVEL main && git push $DEVEL
This ensures that the devel builds on the main branch will have a meaningful version number.
[ ] Close this issue

Changelog

@danielvegamyhre @kannon92 the previous minor release was not correct, the container was built from the main branch, not the v0.7.0 branch. This actually surfaced a bug in the main branch: https://github.com/kubernetes-sigs/jobset/issues/729

Release: https://github.com/kubernetes-sigs/jobset/releases/tag/v0.7.2


Missing documentation for ProviderAppAuth input

File: themes/default/content/registry/packages/github/api-docs/provider/_index.md
I have a attempted to use the GitHub provider along wiht a GitHub App I have created, but there is no documentation to the input fields to configure this. For the pemFile argument I am trying to provide a path to the pemFile, but it is giving me the error error: no decodeable PEM data found
So I think that I need to provide the PEM data directly in the input field, but there is no information regarding whether this should be base64 encoded or just as a plaintext string. Would appreciate if there was some additional documentation here to avoid the trial and error approach to have this work.

Hi @Hanskun - thank you for filing this issue! This is an instance of https://github.com/pulumi/pulumi-terraform-bridge/issues/1046 - we'll take a look as soon as we can.

The documentation is still an issue. The current docs show blank spaces here:

Is there a way to pass the app_auth credentials into config without overriding the default provider?
I tried this without success:
config:
  github:app_auth:
    id:
      secure: ****
    installation_id:
      secure: ****
    pem_file:
      secure: ****

This should be fixed via https://github.com/pulumi/pulumi-terraform-bridge/pull/1650, and you should be seeing docs updates on the next release of this provider.