Update README.md

unexpected char in title.

 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.

LGTM

LGTM


Allowed-Values-Should-Actually-Be-Allowed does not work with Microsoft.Common.Dropdown elements with multiselect

If i have a parameter such as:
"couchbaseServices": {
  "type": "array",
  "defaultValue": [ "data", "index", "query" ]
},

Even if all of those items in the default value are present in a corresponding Microsoft.Common.Dropdown, it will fail
          {
            "name": "couchbaseServices",
            "type": "Microsoft.Common.DropDown",
            "label": "Couchbase Services",
            "multiselect": true,
            "selectAll": true,
            "toolTip": "The services that the primary cluster will utilize",
            "constraints": {
              "allowedValues": [
                {
                  "label": "Data",
                  "value": "data"
                },
                {
                  "label": "Index",
                  "value": "index"
                },
                {
                  "label": "Query",
                  "value": "query"
                },
                {
                  "label": "Search",
                  "value": "fts"
                },
                {
                  "label": "Eventing",
                  "value": "eventing"
                },
                {
                  "label": "Analytics",
                  "value": "analytics"
                },
                {
                  "label": "Backup",
                  "value": "backup"
                }
              ]
            },
            "visible": true
          }

There's also a bug with Microsoft.Common.Dropdown with mutliselect that if a user does not interact with the element, it will return a string value instead of an array value.  I've reported that here as I did not know where else to report it

@malscent thanks for pointing this one out.  We will see if we can expand this case to handle multiselect.

should be in #652


Cast all years to ints

Somewhere along the lines some of these were turning into floats and the program was throwing an error on some range() functions.

Rebased on main just as mypy has got more picky of late


Set up CSP in the nginx conf files

Right now the only way to have a working CSP is to allow 'unsafe-inline' for both style-src and script-src.
The reason why we have to use it with script-src is because it is necessary for django-cms. It seems like they are trying to fix this in this PR, but there hasn't been much activity lately so this might take a while.
The reason why we need to use 'unsafe-inline' with style-src is because of the way we make our pages. Plugins use an HTMLfield for the text, this allows for inline css to be used, there is currently no way around this unless we want to completely change the way we add content to the page


Paola interp

Fixes issues:
#27 #22 #21 #19 #18 #14 #15 #16
#23 in part
More work needs to be done for delimiting time axis correctly
I also updated readthedocs conf.py so I need to merge this to be able to see if documentation can now compile correctly

Updated database so now #27 is properly fixed and also #26


Questions about redirection method

In the common/corscheck.py file, when the request is sent in the send_req method, the allow_redirects parameter is set to True. What are the considerations for this design? When detecting domain name A, if there is a redirection, I think the response from the first request should be used to determine whether the vulnerability exists, because after redirecting to domain B, the access-control-allow-origin parameter is set by domain B, it can no longer reflect the CORS status of the domain A.

Thank for the question. I think we have considered the false positives caused by cross-domain redirections and have removed those cases using the following code:
https://github.com/chenjj/CORScanner/blob/dea5ed2f8fa8d424c3a874c2d66dddb4a58b7c9b/common/corscheck.py#L50-L55


Add AWS Bedrock Converse Provider

Add AWS Bedrock Converse Provider
Overview
This PR adds support for AWS Bedrock's Converse API, which provides a unified interface for interacting with various language models including Amazon's own models (Nova), Anthropic Claude, Mistral, Meta Llama, Cohere, and AI21 models. The Converse API offers enhanced capabilities such as streaming with tools and inference profiles for supported models.
Key Changes
1. New Provider Implementation

Added BedrockConverseHandler class implementing the ApiHandler interface
Supports both streaming and non-streaming responses based on model capabilities
Handles various AWS Bedrock-specific errors with clear error messages
Implements tool configuration for models that support it

2. Model Support
Added comprehensive model definitions with detailed capabilities:

Amazon Nova models (Pro, Lite, Micro)
Anthropic Claude 3 models
Mistral models (Large, Small, Mixtral)
Meta Llama 3.1 and 3.2 models
Cohere Command models
AI21 Jamba models

Each model includes:

Token limits
Context window size
Support for images
Support for computer use
Support for streaming with tools
Support for inference profiles
Pricing information

3. Message Transformation

Added bedrockconverse-format.ts to handle message transformation
Supports system prompts by incorporating them into the first user message
Handles inference configuration for cross-region inference
Manages tool configuration based on model capabilities

4. UI Integration

Added "AWS Bedrock Converse" option in the provider dropdown
Reuses existing AWS credentials UI (access key, secret key, session token)
Added region selection with support for cross-region inference
Displays model-specific capabilities and pricing in the UI

Testing

Tested streaming functionality with tools using Amazon Nova models
Verified non-streaming functionality with Mistral and Meta Llama models
Confirmed error handling for various AWS-specific error cases
Validated cross-region inference configuration
Tested UI integration and model selection

Benefits

Enhanced Model Selection: Access to a wider range of models through a single provider
Advanced Features: Support for streaming with tools on compatible models
Regional Flexibility: Cross-region inference support for better latency and availability
Clear Capabilities: Detailed model information including pricing and feature support
Robust Error Handling: Specific error messages for AWS Bedrock-related issues

Notes

Models require appropriate AWS permissions and regional availability
Some models have specific limitations (e.g., Mistral models don't support streaming with tools)
Cross-region inference and inference profiles are only supported by certain models
Pricing varies significantly between models and should be considered when selecting a model

Thank you, will review this ASAP!

Does this support prompt caching for anthropics claude models on Amazon Bedrock?

Does this support prompt caching for anthropics claude models on Amazon Bedrock?

Not yet as the feature is only in preview I cannot test it.


update proposeMinReplicas

What type of PR is this?
enhancement
What this PR does / why we need it:
Update algorithm for proposing minReplicas in HPA recommendation.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

/lgtm


Any update for iOS 14 for this?

I'm noticing some theme changes with iOS 14. I can provide examples if needed.

Yes, I need some examples, thanks.


Update dependencies across packages

Ran flutter update-packages --force-upgrade across all packages
One win: utf is now dropped from flutter_tool

A test failed that I'm not clear how to fix.
I'll file a separate bug to do this roll before the next release – it will eliminate some dependencies!


autorefresh wallet balance

Describe the feature request
You can add autorefresh wallet balance, or add a reload button for it
Because it shows real balance only after reloading the page
Describe alternatives you've considered

Additional context

@KorbinianK @xiaodino when we bridge something, the balance should be refreshed. Please test the new UI.

fixed in https://github.com/taikoxyz/taiko-mono/pull/14539 for v2


Is it possible with infinite scroll function?

Description:

User can filter the items or scroll down the page.
If user filtered the items, while the page is scrolling down, new items attached to the page, and is filtered accordingly. The page will return some strings when data end.
User also can scroll down the page, then reach for the filters. Next, it will filter accordingly.

Current Situation:

I am using php to pull the data from mysql and display it on page. Pagination is used for view more data.

How to do so easily? Use Ajax? I am newbie in JQuery.
So sorry if the question sounds dumb...

Hello @ceresyuyi,
this is currently something that will not be easily do-able but I'm looking into implementing functions to add and remove items dynamically to your Filterizr gallery in an upcoming patch.

When do you plan to add this feature?

@matmar-91 there's no concrete date yet but sometime during the summer, unfortunately I've got too much on my plate right now


fix: #651 GetSceneAt assumes default scene

Changed to GetActiveScene

is the syntax on this correct?

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


Fix usage metrics collection for static pods

What does this PR do?
This PR fixed the support for OpenShift 3.9 & containerd.
Though, it introduced a regression as usage metrics (memory.usage and filesystem.usage) for static pods are not collected anymore.
Because of https://github.com/kubernetes/kubernetes/issues/61717 the /pods does not contain the ContainerStatus section for static pods. Therefore, the current logic was not able to get the container id of the static pod.
With this new logic, if the pod is static we use the pod uid (which is the only uid available).
Note though:
The UID of the static pod from the kubelet's API is not the same as the one from the APIServer. This is not impacting the logic here, just a behaviour to be aware of.
Motivation
Fix collection of usage mertrics for static pods.
Review checklist

[x] PR has a meaningful title or PR has the no-changelog label attached
[x] Feature or bugfix has tests
[x] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
[ ] If PR adds a configuration option, it has been added to the configuration file.

Additional Notes
Anything else we should know when reviewing?

It should not be too greedy, I'll make a custom build to try on a big cluster to confirm.


incompatible dimensions for orog error

I don't have a reproducer for this, so I'm not sure what causes this issue, but here is an error I ran into with @trontrytel
ERROR: LoadError: incompatible dimensions for orog
Stacktrace:
  [1] error(s::String)
    @ Base .\error.jl:35
  [2] write_field!(writer::ClimaDiagnostics.Writers.NetCDFWriter{…}, field::ClimaCore.Fields.Field{…}, diagnostic::ClimaDiagnostics.ScheduledDiagnostics.ScheduledDiagnostic{…}, u::ClimaCore.Fields.FieldVector{…}, p::ClimaAtmos.AtmosCache{…}, t::Float32)
    @ ClimaDiagnostics.Writers C:\Users\kawcz\.julia\packages\ClimaDiagnostics\gzst4\src\netcdf_writer.jl:330
  [3] ClimaDiagnostics.DiagnosticsHandler(scheduled_diagnostics::Vector{…}, Y::ClimaCore.Fields.FieldVector{…}, p::ClimaAtmos.AtmosCache{…}, t::Float32; dt::Float32)
    @ ClimaDiagnostics C:\Users\kawcz\.julia\packages\ClimaDiagnostics\gzst4\src\clima_diagnostics.jl:95
  [4] DiagnosticsHandler
    @ C:\Users\kawcz\.julia\packages\ClimaDiagnostics\gzst4\src\clima_diagnostics.jl:56 [inlined]
  [5] IntegratorWithDiagnostics(integrator::ClimaTimeSteppers.DistributedODEIntegrator{…}, scheduled_diagnostics::Vector{…})
    @ ClimaDiagnostics C:\Users\kawcz\.julia\packages\ClimaDiagnostics\gzst4\src\clima_diagnostics.jl:280
  [6] macro expansion
    @ C:\dev\CliMA\ClimaAtmos.jl\src\solver\type_getters.jl:709 [inlined]
  [7] macro expansion
    @ .\timing.jl:503 [inlined]
  [8] macro expansion
    @ C:\dev\CliMA\ClimaAtmos.jl\src\utils\utilities.jl:331 [inlined]
  [9] get_simulation(config::ClimaAtmos.AtmosConfig{…})
    @ ClimaAtmos C:\dev\CliMA\ClimaAtmos.jl\src\solver\type_getters.jl:708
 [10] top-level scope
    @ C:\dev\CliMA\ClimaAtmos.jl\examples\hybrid\driver.jl:15
 [11] include(fname::String)
    @ Base.MainInclude .\client.jl:489
 [12] top-level scope
    @ REPL[3]:1
in expression starting at C:\dev\CliMA\ClimaAtmos.jl\examples\hybrid\driver.jl:15
Some type information was truncated. Use `show(err)` to see complete types.

This is why we had OutputPathGenerator. NetCDF files come with defined dimensions that you are not allowed to change. If you re-run a simulation with the same output_dir and change anything about it, you will end up with incompatible NetCDF files. This happens very frequently when developing in the REPL, so the solution was that every time a new Simulation is created, a new folder is also created. Previous folders are retained to ensure that one can still inspect the output there.
I am transfering this issue to ClimaAtmos.


Config API reference for v1.25

This PR batch updates the references for configuration APIs, generated using the genref tool, based on the new release tags for kubernetes v1.25.

@tengqm please set a PR description - it won't be obvious to everyone what this is about.

@tengqm please set a PR description - it won't be obvious to everyone what this is about.

Done.

Preview:
https://deploy-preview-36208--kubernetes-io-main-staging.netlify.app/docs/reference/config-api/

/lgtm

/approve


Improve parser to detect errors and provide line

What do you think about improving the parser to provide line debugging if encounters some error?

We can live with what we have for a while but It's a super good idea, definitely something we need if we want people to create Dogfiles :)

It should probably complain when it finds things it doesn't understand, to prevent misspellings and the like.

This issue has been closed together with other old issues as part of a cleanup process.
Feel free to reopen or reference it if necessary.


Fix Chrome SIGABRT on macOS

python resume.py on macOS results in:
Wrote resume.html
Found Chrome or Chromium at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[0316/071703.668323:WARNING:crash_report_exception_handler.cc(240)] UniversalExceptionRaise: (os/kern) failure (5)
Chrome died with <Signals.SIGABRT: 6> but you may find resume.pdf was created succesfully.

This appears to be harmless. resume.pdf is created just fine. But it's not a great UX.

Idea for this: compare the mtime before and after running chrome. If it's changed, assume resume.pdf was written succesfully and log SIGABRT at info level. Then raise chrome --log-level to get rid of its warning.

No longer seeing this in CI or locally, so closing, but may need to reopen.


ValueError in filter_gap_SVs.py (get_query_bed_coords)

Hi Michael,
Thanks for the great tool and documentation! I went through previous issues and wiki, but I couldn't find cause/solution for the following error at the get_query_bed_coords of filter_gap_SVs.py when I use -s -b -g 100 -i 0.2 -C:
ValueError: invalid literal for int() with base 10: '10733601_RaGOO'

I'm aligning a couple of contig.fasta each with two reference.fasta. I'm only getting the error for one combination of contig.fasta and reference.fasta.
Thanks!
Alexis
Thu Apr 16 14:18:11 2020 --- Running : filter_gap_SVs.py ../../reference.fasta
Traceback (most recent call last):
  File "/work/virtualenvs/venv_devopspy/bin/filter_gap_SVs.py", line 4, in <module>
    __import__('pkg_resources').run_script('RaGOO==1.1', 'filter_gap_SVs.py')
  File "/work/virtualenvs/venv_devopspy/lib/python3.6/site-packages/pkg_resources/__init__.py", line 666, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/work/virtualenvs/venv_devopspy/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1469, in run_script
    exec(script_code, namespace, namespace)
  File "/work/virtualenvs/venv_devopspy/lib/python3.6/site-packages/RaGOO-1.1-py3.6.egg/EGG-INFO/scripts/filter_gap_SVs.py", line 135, in <module>
  File "/work/virtualenvs/venv_devopspy/lib/python3.6/site-packages/RaGOO-1.1-py3.6.egg/EGG-INFO/scripts/filter_gap_SVs.py", line 131, in main
  File "/work/virtualenvs/venv_devopspy/lib/python3.6/site-packages/RaGOO-1.1-py3.6.egg/EGG-INFO/scripts/filter_gap_SVs.py", line 69, in make_svs_bed
  File "/work/virtualenvs/venv_devopspy/lib/python3.6/site-packages/RaGOO-1.1-py3.6.egg/EGG-INFO/scripts/filter_gap_SVs.py", line 52, in get_query_bed_coords
ValueError: invalid literal for int() with base 10: '10733601_RaGOO'
Traceback (most recent call last):
  File "/work/virtualenvs/venv_devopspy/bin/ragoo.py", line 4, in <module>
    __import__('pkg_resources').run_script('RaGOO==1.1', 'ragoo.py')
  File "/work/virtualenvs/venv_devopspy/lib/python3.6/site-packages/pkg_resources/__init__.py", line 666, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/work/virtualenvs/venv_devopspy/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1469, in run_script
    exec(script_code, namespace, namespace)
  File "/work/virtualenvs/venv_devopspy/lib/python3.6/site-packages/RaGOO-1.1-py3.6.egg/EGG-INFO/scripts/ragoo.py", line 757, in <module>
  File "/work/virtualenvs/venv_devopspy/lib/python3.6/site-packages/RaGOO-1.1-py3.6.egg/EGG-INFO/scripts/ragoo.py", line 480, in get_SVs
  File "/work/virtualenvs/venv_devopspy/lib/python3.6/site-packages/RaGOO-1.1-py3.6.egg/ragoo_utilities/utilities.py", line 25, in run
RuntimeError: Failed : filter_gap_SVs.py ../../reference.fasta

Hi there
I have a guess as to what is happening. Is there ":" characters in your reference headers?

Thanks for the quick reply.
I ran samtools faidx to double check fasta headers for both reference.fasta and contig.fasta.

reference.fasta: all "chr" and number or X, Y, MT -- no spaces, ":", "_", "-", or ";" characters
contig.fasta: polished primary contigs from FALCON-arrow, so "000001F|arrow", "000002F|arrow", etc.

The strange thing is that the reference.fasta works fine for the same sample's haplotigs and both the primary contigs and haplotigs for a second sample. And this contig.fastaworks fine with my otherreference.fasta. My two reference.fasta` files are full genomes from two different mammals.

That is interesting. Can you share a representative header from ragoo.fasta. From your error message, I would expect something to have the suffix 10733601_RaGOO

I found the culprit:
000065F|arrow_chimera_broken:10520800-10733601_RaGOO
Should I not be using -c (Break chimeric contigs) with SV calling? Or insert a step to rename/exclude these before SV calling?
One thing I noticed: 000065F|arrow_chimera_broken:10520800-10733601_RaGOO is very large (200kb). All of the ragoo.fasta from successful runs have broken chimeric contigs < 33kb (all but one are <1kb).

oops, my apologies. This is an unplaced contig that was broken during chimeric contig correction. In hindsight, I shouldn't be putting the "_RaGOO" suffix on these (that will not happen in v2), though that is not relevant here.
Stay tuned for an update that addresses this.

oops, my apologies. This is an unplaced contig that was broken during chimeric contig correction. In hindsight, I shouldn't be putting the "_RaGOO" suffix on these (that will not happen in v2), though that is not relevant here.
Stay tuned for an update that addresses this.

This bug should be fixed in 030bb1ba48c4992509111a0321b290f226dc88c0.
Please verify and I will close the issue.

Success! It's working. Thanks so much!

You are welcome. Thanks for bringing this to my attention.


added icons

so i bascially added the login from X and Linkden also alsogn with changing the google icon display

Hey @mrpeace07 also add the same icon on the register page for consistency.

i have added that can u please check that and cinfrim it


Allow Disabling of the Automatic Display of User Messages

I've created a prop which prevents the default behavior of updating the view with the new user message. Consumers of this widget can disable auto-adding in order to either customize the user's input in some way before sending it back using addUserMessage, or to rig it up so that text is only displayed once it has reached the server.
I've set all defaults to the previous behavior so this is non-breaking for people upgrading to it.
I believe this will solve Issue #45, or at least provide the tools for it to be solved easily.
Full disclosure, I'm new to Jest so if I have taken any missteps in my testing, please let me know and direct me to proper resources and I'll do my best to fix them; similarly, if someone out there wants to tune them up I'm more than happy to accept the help. There wasn't any validation around redux behavior so I just piggy-backed onto the mocked dispatch function, validating its input as that seemed better than nothing.

autoAddUserMessage
I installed using npm install but I am not able to use above props.
It seems it is not merged to master.
Could you please merge this mater so that i can use? thanks so much.

How to install it? Tried different approaches that I found online and it's not working for me...

They haven't merged this yet but if you want to use it for now you can do so by adding it to your package.json like:
"react-chat-widget": "github:DrGodCarl/react-chat-widget#allow-custom-user-message-handling-build",
Generally not recommended, especially for you, because I could change it out from under you or delete that branch, but if you want to use my code that's how to do it.

Now is it merged to master branch?? I want to use it can you guide me how to do include it?


October 26th Community Meeting

Please add a topic in this thread and add a link to the Github issue associated with the topic.
Please make sure you give folks enough time to review/discuss the topic offline on Github before coming into the meeting
(optional) Paste the image of an animal smile

@ricardomaraschini - demo ImageStreams

The project I will be presenting is @ https://github.com/ricardomaraschini/it
Here goes a smiling Capivara for you all

#419 -- talk about source vs. sources, and touch on upon introducing v1alpha2.

Issue about Tekton bump: https://github.com/shipwright-io/build/pull/447

Meeting minutes:

Will talk to adam offline about the Tekton bump isse
Ricard gave an awesome demo to introduce the new ImageTag/ImageStream CRD/controller, it is very cool


Integrate xbrl to dbf utility ID mapping

still so much TODO.

[x] settle on pudl table schema
[x] add new ferc util id mappings into package_data
[x] extract pudl util id mappings from mega mapping spreadsheet
[x] transition pudl utility ids in mega plant's mapping spreadsheet
[x] add new table(s) to schema
[x] add new table(s) to pudl.glue.ferc1_eia.glue
[x] add this new utility_id_ferc1 into the data tables during the transform step
[x] Change pinon plant ID (related to #1919)

OOS for this PR (despite some draft attempts)

[ ] enable semi-automatic updates of ferc + pudl util if mappings with new ids.

[x] draft
[ ] integrate into devtools script

[ ] enable semi-automatic updates of pudl utility ids in mega plant's mapping spreadsheet (hard?)

Notes:

I broke out the ferc util ids into a new module... but i kinda think they should be squished into ferc_eia.py. idk?

@cmgosnell  I merged in the update to xbrl_integration that uses the newest FERC 1 data archive, and now the FERC 1 plant ID assignment process is failing, because a column that's used in that process which was previously all integers now also contains some pd.NA values too. Not sure what column it is. Trying to figure it out locally.
@zschira Looking a rebuilding my local FERC 1 databases, I see that the etl_full.yml settings still specify that only the 2021 XBRL data should be loaded into the databases for all of the FERC Forms.  Is that appropriate, given that there are updated filings from previous years as well?
The case of duplicated filings within the XBRL alone is dealt with in the translation to SQLite, right? But in the ETL it seems like we're also going to have to deal with duplicates where an older filing reported in DBF now has an update that appears only in XBRL.  But given that this error is coming up with just the 2021 data being loaded from XBRL, it seems like this can't be the source of the current failure.
I guess we'll also need to update the pydantic validation in the pudl.settings.Ferc1Settings class that partitions the years into DBF and XBRL years, since it seems like any year could have XBRL data, if the filing was updated, and we've seen them update filings 10+ years after the fact before when it was all DBF.
The fun never ends with FERC!

Looks like there's a single record in the new 2021 data that ends up with a null utility_id_ferc1 (for that 1300MW plant named "0") and 6 previously unmapped plants. However, pudl.glue.ferc1_eia.get_missing_ids() is returning a MultiIndex rather than a DataFrame so some stuff downstream from that is breaking now.

I suppose we could start loading older years into the SQLite DB's. We'll need decide how we want to handle these overlapping years in the ETL, but they shouldn't cause a problem in the raw DB's.

The case of duplicated filings within the XBRL alone is dealt with in the translation to SQLite, right?

That's correct, for duplicate filings in the same year of XBRL data, it will only use the most recently submitted filing.

I created an issue for dealing with the restated filings / overlapping years: #1968


Temperature Sensor Integration

Description: Connect temperature sensor to BITS

Basic code structure in place, we still need to test to make sure that the sensor can be plugged in and the values can be read into the database. Basic functionality in place, but custom code will need to be written to address this problem. I will be working with @callie-jones and @JackDinkel to get sensor hooked up and integrated.

I have solved my issue reading from the sensor discussed in the team meeting as part of #10. Hopefully that ticket will allow me to replace the pcsensor file with a custom driver.

The current pcsensor driver for the temperature sensor works great.
In the future, the generic sensor development will be tracked in #10


Add to Line Chart ability to select x-axis other than date field, or add a new Line Chart that is not time series

At the moment, Line chart is a time series chart and X-Axis always is the date in the time section

It would be a great addition to have Line Chart that allows X-axis to be any filed so can be used to compare trends despite without link with dates.
Use case at the moment, I  want to compare different customers' growth by the month of Customer Acquisition date but all of them have a different start dates.
For example this dataset :

This is the best chart that I can do with the Line Chart

If I create a metric as the:  datediff('month', start_date,sales_date) I would like to be able to do a chart like this.

It is possible with Bars but it is harder to see trends and do comparison with the bars, in addition, bars get even more confused when the field to breakdown has many distinct values

dropboxers are requesting a similar feature

🏷chart

will implement numeric and categorical line chart with new echarts soon

@junlincc  any ETD?

@junlincc  any ETD?

this chart is support the above and more
https://5fec4c81935a8c002151e85f-nfsmejbgts.chromatic.com/?path=/story/plugins-composed-chart--all-types
https://github.com/nielsen-oss/superset-viz-plugins/

this chart is support the above and more
https://5fec4c81935a8c002151e85f-nfsmejbgts.chromatic.com/?path=/story/plugins-composed-chart--all-types
https://github.com/nielsen-oss/superset-viz-plugins/

will implement numeric and categorical line chart with new echarts soon

how soon?

Hi, this feature would be very much appreciated.

@x670 @stephanclaus this is being worked on right now (some recent development linked to this old issue: #822)

@ValentinC-BR , this is already fairly stable on master branch. Just enable the GENERIC_CHART_AXES feature flag.

Didn't see that, thanks !
Since when (which version) is this feature available ? I have some troubles finding it, and we're still in 1.5 in our company.

I't not really ready on 1.5, so I do recommend waiting until the forthcoming 2.1 release (release date still unknown). But if you want to take a sneek peak and do some early testing, please try out master branch locally with the relevant feature flag enabled.

Got it, thanks.
We'll wait for the 2.1 then.

2.0.1 would be a good release for those looking to upgrade. Meanwhile, since this feature is out there in the wild, I'll go ahead and close the issue for now. Bugs and whatnot can be taken up in new threads! Thanks!

Line chart x-axes label without time: how to create?


Removing DeepL manifest directory to utilise ms store

[N/A ] Have you signed the Contributor License Agreement?
[Yes ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[No ] This PR only modifies one (1) manifest
[ N/A] Have you validated your manifest locally with winget validate --manifest <path>?
[ N/A] Have you tested your manifest locally with winget install --manifest <path>?
[N/A ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/112349&drop=dogfoodAlpha

@Trenly the biggest issue is we utilise an installer called 0install, this handles all of the install/upgrade functions. We've tried to future proof the manifest with <IP_ADDRESS>68, but each version generates a new SHA. By removing the manifests and utilising the ms store install we would ensure that the behaviour of install/update/uninstall is as we intend.
I'll do some digging to see if we can get the behaviour we want from install/uninstall/update within the manifest and also createa pipeline that manages creating a new PR with each new version

Ah, I see

Close with reason: One package version removal per pull request;


Update the AWS load balancer type

Update the Nginx annotations to use AWS NLB instead of AWS ELB. AWS ELB does not support WebSockets and we need WebSocket support for Jupyter Kernels.

Closed by illumidesk/helm-chart#46


(#1) Add support for Github login

Description
Fix: https://github.com/GeeksCAT/anem-per-feina/issues/1
This PR adds a new feature, login with your Github account.

Environment variables

SOCIAL_AUTH_GITHUB_KEY: Key of Githbu third-party login App
SOCIAL_AUTH_GITHUB_SECRET: Secret of Github third-party login App

Code formating
The code has to be well formatted following the formatting rules. For example in Python the code has to follow the PEP8.
Before create your PR, please make sure your code is well formatted and styled doing:
$ >> pre-commit run --all

Nice job!


about more record index

I found the  biggest  record index  is  2^20  in  paper. Can it support  bigger  record? example 2^24 or more?

This may be possible, especially for SpiralStream / SpiralStreamPack, but this library does not support it yet. If we do add support for this, it will be in the new Rust repo (https://github.com/menonsamir/spiral-rs).
Also, if database records are small in size, then accommodating a larger number of elements is possible as long as you are willing to sacrifice on the rate. For example, we could accomplish serving a 2^24 x 16 byte database by instead using a 2^15 x 8192 byte database, though our response sizes would have to be quite large relative to the actual plaintext size.

Thanks，I got it.  I have  another problem  on this potorcol about  how to use retireval the value by the keyword


Trying to use .env-cmdrc.js fails with "Invalid .rc file path"

I'm trying to use the support for .env-cmdrc.js along with the --environments flag to allow me to do merging of environments within the environments file to avoid my scripts from getting too long.
Unfortunately it seems like there's a bug in env-cmd around resolving the fallback files. I can see where the code is set up to try and do that, but it fails on the first file.
I've created a repro as a gist
Here's the error I get when trying to use env-cmd with a .env-cmdrc.js file in the same dir:
Error: Invalid .rc file path.
    at Object.<anonymous> (C:\Users\tivac\Desktop\env-cmd-test\node_modules\env-cmd\dist\parse-rc-file.js:27:19)
    at Generator.throw (<anonymous>)
    at rejected (C:\Users\tivac\Desktop\env-cmd-test\node_modules\env-cmd\dist\parse-rc-file.js:5:65)

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

I've tracked down the problem. The problem is that https://github.com/toddbluhm/env-cmd/blob/master/src/get-env-vars.ts#L54 doesn't await the promise ever, which means it never catches the error. Additionally, env-cmd is being compiled for pre-Node v8, which is strange, seeing as how Node v6 is dead and v8 is going to EOL at the end of this year too.

<EMAIL_ADDRESS>has been published with this fix


NTR: normal protein localization to iMTOC/eMTOC 	PMID:19001497

NTR: normal protein localization to iMTOC
NTR: normal protein localization to eMTOC
Standard defs
PMID:19001497
(Would it be possible for all of the terms containing eMTOC/iMTOC to have these as primary names instead of synonyms as this is the community usage...they never write it out in full and the abbreviation is easier to read/distinguish quickly)

new terms
normal protein localization to eMOTC FYPO:0005707
normal protein localization to iMOTC FYPO:0005708
name/synonym swaps done
edit file: b195a9d2b07819052614b9be249a6853a8888f7e
release: 99819ea12811962b4b71c6793722c4377f141fde


Update _index.md

Updated CNI under values that was missing an indentation and throwing a syntax error in the Cluster Explorer. As per https://istio.io/latest/docs/setup/additional-setup/cni/#helm-chart-parameters, it should be indented.
Credit to @it-slav for identifying the bug and fix

Closing as this was created in error and @it-slav has since successfully installed Istio with the "invalid" yaml


Add LICENSE and README Info

Closes #18

Coverage remained the same at 83.761% when pulling 9032b168dfb4df9408774fdd6b0de2ef897ded2b on psastras:master into 39552b0e5b796e29725b69da7077591799683a1f on OpenChatAlytics:master.


move examples out of lib/

This moves the coap and cc2538 examples out of the lib/ crate into their own workspace crates.
The main benefit is that now edhoc-rs doesn't have to specify any coap dependencies anymore.
Another piggybacked commit removes edhoc-rs' "hex-literal" dependency, which seems to have been superseded by "hexlit".

I like how this simplifies the library dependencies, thansk for providing the PR!


AKS does not have HA master!

"The AKS control plane components for your cluster are also spread across zones in the highest available configuration when you create a cluster specifying the --node-zones parameter."  is wrong and should be removed until it is available.
See correct documentation: "KS provides a single-tenant cluster master, with a dedicated API server, Scheduler, etc" https://docs.microsoft.com/en-us/azure/aks/concepts-clusters-workloads#cluster-master

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

ID: 471c32a2-1f6a-88d1-7df4-80b8f6fbc4a4
Version Independent ID: 10de5ee1-942d-e30f-5f0c-f163bd45904d
Content: Use Availability Zones in Azure Kubernetes Service (AKS)
Content Source: articles/aks/availability-zones.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

Thanks for the feedback! We are currently investigating and will update you shortly.

adding @MicrosoftDocs/aks-pm to confirm.

@jluk assigned to you to work with @mlearned to update one of the two docs based on the discussion offline with @denniszielke

@mimckitt this is taking much too long.

Can anyone please provide an update on this?

"single-tenant control plane, with a dedicated API server" does not directly correspond to 1 API server, it intends to indicate the control plan is dedicated for each customer and not multi tenant.
I can review the language if it's not clear.
The sentence "The AKS control plane components for your cluster are also spread across zones in the highest available configuration when you define the --zones parameter at cluster creation time." is correct, as such we will proceed to close this ticket.

#please-close


Break up bitwise operation into two shorter operations

This fixes #171

Hi there. The DCO sign off needs to be in its own line I'm afraid. Can you modify the commit and force push again? Thanks.

no problem, done!

@codeanticode It looks like the DCO bot doesn't like the fact your GitHub 'full name' is not your actual full name, or that you have your local GitHub config set with the wrong full name:-
Commit sha: [8b966c6](https://github.com/theheraldproject/herald-for-ios/pull/174/commits/8b966c639f4812b9cbdc422ced34b534f8f5fff6), Author: codeanticode, Committer: codeanticode; Expected "codeanticode [andres.colubri@gmail.com](mailto:andres.colubri@gmail.com)", but got "Andres Colubri [andres.colubri@gmail.com](mailto:andres.colubri@gmail.com)".

Try running this locally, altering the commit, and force pushing again please. Once you have it configured correctly it'll just work each time then.
git config --global user.name "Andres Colubri"
git config --global user.email<EMAIL_ADDRESS>

oh, that's becasue I used my name instead of my github handle (codeanticode), I cannot get this right :-) I will correct shortly.

Looks like it should work now!


[BUG] - Android Emulator - Backspace not working as expected, skip characters while removing

Package Version
super_editor, GitHub, main branch
User Info
individual
To Reproduce
Steps to reproduce the behavior:

Run example app on Android emulator
clear the whole editor
type 2 paragraphs, 2 ordred list items, 2 paragrapghs
keep the cursor at the end and press and hold backspace on android keyboard
See error

Actual behavior
On press and hold backspace, the last 2 paragraphs clears fine but the cursur skips to the start of the last list item and keeps moving without clearing.
Expected behavior
On press and hold backspace, it should clear all characters
Platform
Android Emulator
Flutter version
3.22.1
Screenshots
untitled.webm

This looks to be a Flutter bug. The TextPainter.getFullHeightForCaret is reporting incorrect results spans with multiple styles
I filed https://github.com/flutter/flutter/issues/152006

@talhakhan1297 Which Android version are you using in this emulator?

@talhakhan1297 Which Android version are you using in this emulator?

Android 14

@talhakhan1297 Could you please run the demo with the IME logs enabled and post the logs here? To enable the logs, please do the following change on the main file of the demo app:
Future<void> main() async {
  initLoggers(Level.FINE, {
    // editorScrollingLog,
    // editorGesturesLog,
-   // editorImeLog,
+   editorImeLog,
    // editorImeDeltasLog,
    // editorKeyLog,
    // editorOpsLog,
    // editorLayoutLog,
    // editorDocLog,
    // editorStyleLog,
    // textFieldLog,
    // editorUserTagsLog,
    // contentLayersLog,
    // appLog,
  });

  runApp(SuperEditorDemoApp());
}


'json' encoding stringifies data before being inserted into db

Since JSON is the native encoding to IndexedDB, it shouldn't be necessary to stringify data before storing it. Is it AbstractLevelDOWN that does the conversion? Does it make sense to replace 'json' encoding with raw:true when the database is opened?
I'm using the following to make sure I can cleanly work with JSON in both node and browser environments, but it feels like a hack:
package.json:
  ...
  "browser": {
    "leveldown": "level-js",
  }
  ...

index.js:
var levelup = require('levelup');
var leveldown = require('leveldown');
var leveljs = require('level-js');

var options = {
  db: leveldown
};
if (leveljs !== leveldown) {
  options.valueEncoding = 'json';
}
var db = levelup(name, options);

@mcollina good point.
I also have a performance concern about this, but it will be good to see if it actually hurts something. It's possible that it doesn't

Hi @Ivshti, we ended up going a different direction. Our primary motivation for using indexeddb was performance rather than offline access. Instead of focusing on building a database engine (because a year ago, that's really what you had to do to practically use indexeddb, even with helper libraries), we instead worked on improving API response times and adjusting UI feedback to improve the initial-load experience.

if you want level.js to get the raw values, +1 on this pull request: https://github.com/Level/abstract-leveldown/pull/85

<EMAIL_ADDRESS>is out! so if you want to bypass encoding completely, simply do this:
db._serializeKey =
db._serializeValue = function (data) { return data }

by the way, since we added custom codecs you could do valueEncoding: {encode: id, decode: id} where id is the id function: function id (e) { return e }

The problem was that abstract-leveldown would still (!) convert everything to a string of buffer. That can be bypassed now. So yeah you need to set those options on levelup and leveldown for now.

oh I see. well, we have encodeing.buffer: boolean right, maybe we need encodeing.string: boolean and then you can have naked encoding {encode: id, decode: id, buffer: false, string: false} ?


Missing full name using Sign in with Apple

Bug report
Describe the bug
When authenticating via Sign in with Apple, despite the full name scope being set, the created user is missing the full name claim.
This works when signing in with Google instead.
Fundamentally, the difference seems to be that Google (correctly) provides the full name as part of the ID token. Apple, on the other hand, has its own custom return type AuthorizationCredentialAppleID which may contain a given and family name.
The current flow retrieves the ID token via the native modal, and then uses signInWithIdToken^2 to create the user. If the data is not in the ID token, it just won't be available to the backend.
I found some previous discussion in #105 - where they reached the same conclusion as ourselves.
To Reproduce
SupaSocialsAuth must be configured as follows:
          SupaSocialsAuth(
            socialProviders: [OAuthProvider.apple],
            enableNativeAppleAuth: true,
            onSuccess: _onSuccess,
          ),

The Flutter app must be configured to use sign_in_with_apple^4.
Deploy the app to iOS. Now you may attempt the Sign in with Apple flow.
Finally, go to Supabase, in the table view, and check auth.users.  Under raw_user_meta_data it'll be a JSON object with claims coming from the ID token, confirm that the full name is not there.
To perform further tests, since Apple sends the full name only once per app, on iOS:

Go to Settings > Apple Account[^5] > Sign in with Apple
If the app is there, it means a previous sign in was performed - the full name won't be provided again - tap on it
Tap Delete > Stop Using

Expected behavior
I would expect the user name to be available in Supabase Auth.
System information

OS: iOS (macOS too, I think)
Browser (if applies): I'm not sure how to fix it here, as a "plain OAuth" flow is used, with browser redirection

Additional context
We have a proposed fix in our fork^1, I'm happy to contribute this in its own branch if you'd like to upstream this specific fix.
Our proposal is to add a call to updateUser^3 if a given and/or family name are provided.
[^5]: This is the very first entry in the settings app, the one referring to your Apple ID

In my flutter code I fixed it by adding the following code after signInWithIdToken:
    await supabase.auth.updateUser(
      UserAttributes(
        data: {
          'given_name': credential.givenName,
          'family_name': credential.familyName,
        },
      ),
    );


avoid download file twice

avoid download file twice

Thanks for the contribution! However, this is a read-only mirror. please read the contribution guide. Also, feel free to join us on chat!


Question / Possible bug:  Need to refresh the page for hero search to work right?

I followed the example in the documentation in the  HTTP Tutorial: Search-by-name section.   I am trying to do the same thing trying to create search functionality to learn observables (I created a repository https://github.com/daBishMan/ng2-observables to help me out).
In the TOH when the user find what they are searching for he/she clicks on the button /hero on go to a different page.  What I am trying to accommodate is the user select and stay and the same page, and can delete the selection and start again.
This does not seem to work, it seems that we are per the documentation inside the class, it states "switch to new observable each time", I think that is the problem since we are using the "async" pipe.
How can I change (or is this a possible bug) to accommodate what I am asking?  Can you help?

Sorry for mega late response.
How is this going? You shouldn't ever need a refresh. That is the idea behind SPAs :P

NP, thank for responding.  Yes, I addressed this.  I will close it.


npm support

Provide ability to publish the package to npm .
I make a release here : https://www.npmjs.com/package/ns-popover
fell free to take the ownership
close https://github.com/nohros/nsPopover/issues/92

Why the package name needs to be changed?
I am not familiar with nodejs and do not know if this library could be used in node directly, can you clarify the use case?

npm is a package manager which could be used for server and front end.
You can build a frontend app throught browserify or webpack and use a node module with require() call like you do in a nodejs app.
Even if the package is not npm compliant ( it doesn't export a module ) you could use npm to share and download it like you do with bower.
In my case i have ns-popover in dependencies in my package.json. When i type npm install, all my dependencies are loaded from npm.
Now if i use browserify or webpack i just have to require ns-popover in my code and it's loaded exactly as if i added a

Ok, thanks for the explanation. I really need to rename the package? This will cause conflicts with bower users that already use the nsPopover.

On npm yes , you can't use camelCase :
"New packages must not have uppercase letters in the name."
https://docs.npmjs.com/files/package.json


Backport 2.7: Replace Windows API threading with CRT functions

Description
Backport of #1777.
In Visual C/C++ programs that use CRT library, should do threading with _beginthread, _beginthreadex and _endthread, _endthreadex functions instead of Windows API functions CreateThread, ExitThread and CloseHandle.
Otherwise some CRT funtions could fail, and memory leaks are possible.
Timer tests in selftest.c with the new code were successful.
Status
READY
Migrations
NO
Todos

[ ] Tests
[ ] Documentation
[ ] Changelog updated
[ ] Backported

retest

retest

retest

retest


KNL-1397 SakaiContextLoader improvements

Removal of contextSharedLocation
Convention for loading additional bean defs from sakai.home for webapps

Doesn't the removal of contextSharedLocation prevent the loading of portal resources from the library project? So won't org.sakaiproject.webapp.api.WebappResourceManager no longer work?

moved this convo to JIRA..
https://jira.sakaiproject.org/browse/KNL-1397


Deal -1 Cards for Armor Penalty

Would be cool if the system could be smart enough to deal out -1 cards if you have armor like Hide Armor or Chainmail.

Would need to take into account any "perks" which allow you to ignore negative item effects (Berserker has this)
Since people may not equip the armor for each mission, maybe want to just put the -1 cards on top of the Armor orthogonally and let the player put them in their modifier deck.

Yeah, that would be cool. The perk information already has the flags for
ignoring negative item effects, so that would be easy to do. I think it one
could put the items in the deck automatically when the item is equipped
(which can be determined from its position).
However, one thing that currently hinders me to do that, are the spoilers.
:-) I don't want to look through all items to see which items add how many
negative cards.
Seferan<EMAIL_ADDRESS>schrieb am So., 28. Juni 2020, 16:31:

Would be cool if the system could be smart enough to deal out -1 cards if
you have armor like Hide Armor or Chainmail.

Would need to take into account any "perks" which allow you to
ignore negative item effects (Berserker has this)
Since people may not equip the armor for each mission, maybe want to
just put the -1 cards on top of the Armor orthogonally and let the player
put them in their modifier deck.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Sebaestschjin/gloomhaven-saveloader/issues/29, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHP6RVHAT4DTBQBSOBZRJLRY5H3DANCNFSM4OKRYO2A
.


Connectors script does not seem to properly restart the dataproc agent

This is another issue I have with the connectors/connectors.sh script: After I create my cluster, all the pyspark jobs I run are resulting in a Task was not acquired error. I have to manually restart the dataproc agent on both master and workers to make it work properly.


DiAbstractServiceFactory Recursion

[x] I was not able to find an open or closed issue matching what I'm seeing.
[x] This is not a question. (Questions should be asked on chat (Signup here) or our forums.)

The Zend\ServiceManager\Di\DiAbstractServiceFactory when used as an abstract factory is causing recursion.
The issue is caused by Zend\ServiceManager\ServiceManager::has() function implementation and Zend\ServiceManager\Di\DiAbstractServiceFactoryFactory: :__invoke() function which is using DiAbstractServiceFactory::USE_SL_BEFORE_DI and Zend\ServiceManager\Di\DiServiceFactory: :get() method which is sending the object initialization request back to the Zend\ServiceManager\ServiceManager and as a result creating the recursion.
During object initialization by ServiceManager via DiAbstractServiceFactory the DiServiceFactory::get() method checks whether it should call ServiceManager (Service Locator) first by the following code (line 126) and therefore sends the object initialization request back to the ServiceManager because both conditions for the if statement are correct in this situation.
// Allow this di service to get dependencies from the service locator BEFORE trying DI.
if ($this->useContainer === self::USE_SL_BEFORE_DI && $this->container->has($name)) {
     return $this->container->get($name);
 }

As the object initialization request is sent or pushed back to the ServiceManager and the ServiceManager will forward the request again to DiAbstractServiceFactory therefore creating the recursion (sending the request back and forth) and the end result is system memory exhausted.
Code to reproduce the issue
Please just use Zend\ServiceManager\Di\DiAbstractServiceFactory as an abstract factory
and then use ServiceManager to get/initialize an object. This object should not have any other factory class defined in the config. The only factory which should initialize this object should be Zend\ServiceManager\Di\DiAbstractServiceFactory.
Expected results

No Recursion.
Actual results

Recursion

Originally posted by @mirza572 at https://github.com/zendframework/zend-servicemanager-di/issues/19

I created the following to test this:
// in src/Example.php:
namespace Test;

class Example
{
}

// in test.php:
use Test\Example;
use Zend\ServiceManager\Di\ConfigProvider;
use Zend\ServiceManager\Di\DiAbstractServiceFactory;
use Zend\ServiceManager\ServiceManager;

require './vendor/autoload.php';

$container = new ServiceManager((new ConfigProvider())->getDependencyConfig());
$container->addAbstractFactory($container->get('DiAbstractServiceFactory'));

$instance = $container->get(Example::class);
var_export($instance);

This mimics how zend-servicemanager-di would register its services, and demonstrates how to add its abstract factory to the container after initialization.
This definitely reproduces the issue.
I'm not certain how quickly we will try to address it, particularly as zend-di provides comprehensive support for zend-servicemanager as of version 3. We typically recommend using that support if you are able to to, as it provides a better path from development to production, and more flexibility in how users interact with their container.
Interestingly, I checked to see if this worked in that paradigm as well:
use Test\Example;
use Zend\Di\ConfigProvider;
use Zend\Di\Container\ServiceManager\AutowireFactory;
use Zend\ServiceManager\ServiceManager;

require './vendor/autoload.php';

$container = new ServiceManager(array_merge_recursive(
    (new ConfigProvider())->getDependencyConfig(),
    [
        'abstract_factories' => [
            new AutowireFactory(),
        ],
    ]
));

$instance = $container->get(Example::class);
var_export($instance);

Surprisingly, the behavior is exhibited there as well. (Anecdotally, I'm surprised, as I've used the autowire factory before when prototyping functionality, and it worked fine.)
I'm curious if the issue is due to having an empty constructor. Can you provide some information about the class you're trying to retrieve from the container?

Originally posted by @weierophinney at https://github.com/zendframework/zend-servicemanager-di/issues/19#issuecomment-558818981

The issue exists in both cases whether the class has an empty constructor or not. Following is the class constructor
    /**
     * Constructor
     *
     *  \Vendor\Framework\App\ResourceConnection $resourceConnection
     */
    public function __construct(
        \Vendor\Framework\App\ResourceConnection $resourceConnection
    ) {
       $this->connection = $resourceConnection->getConnection();
    }

A quick solution to this issue is changing Zend\ServiceManager\Di\DiAbstractServiceFactoryFactory: :__invoke() method as following i.e. replace DiAbstractServiceFactory::USE_SL_BEFORE_DI by DiAbstractServiceFactory::USE_SL_NONE or DiAbstractServiceFactory::USE_SL_AFTER_DI
    /**
     * Class responsible for instantiating a DiAbstractServiceFactory
     *
     * @param ContainerInterface $container
     * @param string $name
     * @param null|array $options
     * @return DiAbstractServiceFactory
     */
    public function __invoke(ContainerInterface $container, $name, array $options = null)
    {
        $factory = new DiAbstractServiceFactory($container->get('Di'), DiAbstractServiceFactory::USE_SL_NONE);

        if ($container instanceof ServiceManager) {
            $container->addAbstractFactory($factory, false);
        }

        return $factory;
    }

Originally posted by @mirza572 at https://github.com/zendframework/zend-servicemanager-di/issues/19#issuecomment-559056476

This package is considered feature-complete, and is now in security-only maintenance mode, following a decision by the Technical Steering Committee.
If you have a security issue, please follow our security reporting guidelines.
If you wish to take on the role of maintainer, please nominate yourself
You can now use laminas/laminas-di directly with laminas/laminas-servicemanager.


added json file

Pull Request Type
What kind of change does this PR introduce?
[ ] Solved an issue/task #1596
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
What is the current behavior?

Issue Number: [Insert Issue Number (if applicable)]
What is the new behavior?

Other information

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


azure-cli support for federated identity credential CRUD operations

xref: https://azure.github.io/azure-workload-identity/docs/faq.html#how-does-the-azwi-cli-differ-from-the-azure-cli
This issue is to track the azure-cli support for adding/deleting/updating federating identity credentials

azure-cli v2.40.0 and above supports adding federated identity credential for Azure AD Apps and user-assigned managed identities.
ref: https://learn.microsoft.com/en-us/cli/azure/identity/federated-credential?view=azure-cli-latest and https://learn.microsoft.com/en-us/cli/azure/ad/app/federated-credential?view=azure-cli-latest


Correctly calculate intrinsicContentSize before first layout run

This pull requests adds the ability to calculate the intrinsicContentSize of TagListView without requiring a full layout-run. This is for example the case if some one wants to pre-calculate the sizes of UICollectionViewCells (with systemLayoutSizeFitting (...)) that have a TagListView embedded.
In my case, the intrinsicContentSize was always wrong (height: number of tag x tag-height) because the tag list inside my static prototyping cell (which is used for size-pre-calculation) was not layouted yet. And since layouting the whole cell is more expensive then using systemLayoutSizeFitting() while gathering the correct cell sizes is critical for scrolling performance of the whole collection view, I had to find a way to calculate the intrinsicContentSize without that dependency from the view's frame.
BTW: Even Apples documentation for intrinsicContentSize says:

This intrinsic size must be independent of the content frame

My solution is inspired from UILabel's preferredMaxLayoutWidth, since multiline labels have the same requirement to calculate their height depending of their width, which they don't know prior layouting.
So in rearrangeViews() the TagListView uses the newly introduced preferredLayoutWidth property (if set to a proper value) for calculating the distribution of all tags (instead of frame.width).
The getter of intrinsicContentSize then looks for the widest rowView to determine the tag list view's intrinsic width.
When using autolayout, the tag list view will then be sized based on it's intrinsicContentSize.

And how your solution will work for iPad and iPhone? Different preferredLayoutWidth?

@mikestalker Yes, similar to UILabels preferredMaxLayoutWidth you need to set the value depending on the available space, which might be (but doesn't have to) different on iPhone and iPad.

this saved me 🙏 thank you very much!


added controllers spec

Blog app - controllers specs :control_knobs:
In this project, I set up tests on the controllers recently added to the Blog app.
Highlights :1st_place_medal:

Add RSpec as a gem to your project.
Create a Request spec file for all your controllers.
Make sure that for each action you check:

If response status was correct.
If a correct template was rendered.
If the response body includes correct placeholder text.

Cheers :clinking_glasses: and happy reviewing! :+1:

Thank you @CollinsTatang for approving my project :pray:


Titles, aliases, and description for SchemaModels

Let me first say how much I love pandera and the appreciate the effort to maintain and write such a great package!
Is your feature request related to a problem? Please describe.
Errors can be difficult to debug without extra context. Say, a check fails, the only information to the user is that the column failed that particular check.
Now, would it not be better for the user to understand why the column should pass this check? A very simple way to do this is to give more context, i.e. more information about what this column actually contains, where it comes from, etc. This can also help to actually understand why the issue appears and how it can be debugged.
Describe the solution you'd like
pydantic allows titles and descriptions, aliases, etc. in their Field object. I wonder if this could be added to pandera. Together with some smart sphinx plugin, you could even turn this information into a full and automatic data dictionary (see https://sphinx-pydantic.readthedocs.io/). Maybe it is possible to make Fields subclasses of the pydantic fields and schemas subclasses of BaseModel (not sure I am considering all challenges)?

Let me first say how much I love pandera and the appreciate the effort to maintain and write such a great package!

thanks @jdb78!
I think this would be a fantastic addition to pandera! I think before delving more into implementation details, I'd like to understand a little bit better what additional context would be helpful.
I understand the reasoning behind title and description: basically it provides additional annotation capabilities that gives the user more human-readable metadata. However,

Now, would it not be better for the user to understand why the column should pass this check?

Implies something more that I'm not sure how adding a title and description to fields would solve... or am I missing something? A concrete code sketch/example with realistic (but toy) data often helps with these kinds of discussions... basically I think it would help illustrate what the limitations are of the current state of pandera and how the solution would address them.
Currently, pandera reports the failure cases that were the reason behind the failed check (in the case that the check returns a boolean vector), e.g. here, and also gives the user access to a dataframe of all the failure cases across all the checks via lazy validation, see here.
P.S. #329 adds support for field aliases in via the class-based API

I am also interested in this enhancement. In my case, I'm looking to pair it with the to and from yaml capabilities of pandera. The extra metadata supporting a title and/or a description will turn the produced yaml files into a full-fledged data dictionary.
I would like to read something like the below yaml file (note I also think a title/description to the DataFrame schema as well is a good idea).
schema_type: dataframe
version: {pa.__version__}
title: Example Schema
description: This is a description of the DataFrame schema ....
columns:
  column_1:
    description: Column 1 represents ....
    pandas_dtype: int
    nullable: false
    checks:
      greater_than: 0
    allow_duplicates: true
    coerce: false
    required: true
    regex: false
  column_2:
    description: Column 2 represents ....
    pandas_dtype: float
  ....

I will have capacity to submit a pull request, but before I go about generating one, I wanted to pick your brain on what you were thinking.

Are you thinking about having a field object that holds both the title and description like pydantic or were you open to adding the title and description as attributes under the Column/Index? Again in my use case I think about this in terms of the yaml file being used to create the schema. Thoughts are below.

As field attribute -
...
columns:
  column_1:
    field:
      title: Column 1 Title
      description: Column 1 represents ....
    pandas_dtype: int
    nullable: false
    checks:
      greater_than: 0
    allow_duplicates: true
    coerce: false
    required: true
    regex: false

As standalone attributes -
columns:
  column_1:
    title: Column 1 Title
    description: Column 1 represents ....
    pandas_dtype: int
    nullable: false
    checks:
      greater_than: 0
    allow_duplicates: true
    coerce: false
    required: true
    regex: false

What objects should have the title/description added? The original request from @jdb78 mentioned columns. Should the Index object be included as well? I also think it would be beneficial to have similar information available for the Schema (both DataFrame and Series) objects.

Also, thank you for the time you've put toward pandera!
Dustin

I am also interested in this enhancement. In my case, I'm looking to pair it with the to and from yaml capabilities of pandera. The extra metadata supporting a title and/or a description will turn the produced yaml files into a full-fledged data dictionary.
I would like to read something like the below yaml file (note I also think a title/description to the DataFrame schema as well is a good idea).
schema_type: dataframe
version: {pa.__version__}
title: Example Schema
description: This is a description of the DataFrame schema ....
columns:
  column_1:
    description: Column 1 represents ....
    pandas_dtype: int
    nullable: false
    checks:
      greater_than: 0
    allow_duplicates: true
    coerce: false
    required: true
    regex: false
  column_2:
    description: Column 2 represents ....
    pandas_dtype: float
  ....

I will have capacity to submit a pull request, but before I go about generating one, I wanted to pick your brain on what you were thinking.

Are you thinking about having a field object that holds both the title and description like pydantic or were you open to adding the title and description as attributes under the Column/Index? Again in my use case I think about this in terms of the yaml file being used to create the schema. Thoughts are below.

As field attribute -
...
columns:
  column_1:
    field:
      title: Column 1 Title
      description: Column 1 represents ....
    pandas_dtype: int
    nullable: false
    checks:
      greater_than: 0
    allow_duplicates: true
    coerce: false
    required: true
    regex: false

As standalone attributes -
columns:
  column_1:
    title: Column 1 Title
    description: Column 1 represents ....
    pandas_dtype: int
    nullable: false
    checks:
      greater_than: 0
    allow_duplicates: true
    coerce: false
    required: true
    regex: false

What objects should have the title/description added? The original request from @jdb78 mentioned columns. Should the Index object be included as well? I also think it would be beneficial to have similar information available for the Schema (both DataFrame and Series) objects.

Also, thank you for the time you've put toward pandera!
Dustin

Awesome, thanks @dustindall!

Are you thinking about having a field object that holds both the title and description like pydantic or were you open to adding the title and description as attributes under the Column/Index?

I think all schemas and schema components should have a title and description, so that would be DataFrameSchema, SeriesSchema, Column, Index, and MultiIndex in the object-based API.
title and description should probably also be available in the model.SchemaModel and model.components.Field in the class-based API.
The implementation should be fairly straightforward since these attributes shouldn't really effect any part of the validation process. The three parts I can think of are:

error reporting: when pandera raises a SchemaError or SchemaErrors exception, the title and description should probably be part of the error message somehow.
__str__/__repr__ methods: sort of related to (1), but these dunder methods should also include title and description
yaml/python script IO: as you mentioned, the new attributes should be added when calling the to_script and to_yaml methods.

I will have capacity to submit a pull request

That would be awesome! It might make sense if you added the title and description attributes to all relevant class definitions, and maybe part (3) as you're interested in this part of the enhancement. If you're up for it, (2) would also be fairly straighforward... (1) might be a little bit of a pain, as the way error-handling is done in the code-base is a little confusing and would stand to be improved from a developer perspective. Let me know what you feel like doing!
Also feel free to ping me here if you need any help re: setting up your dev environment.

Awesome, thanks @dustindall!

Are you thinking about having a field object that holds both the title and description like pydantic or were you open to adding the title and description as attributes under the Column/Index?

I think all schemas and schema components should have a title and description, so that would be DataFrameSchema, SeriesSchema, Column, Index, and MultiIndex in the object-based API.
title and description should probably also be available in the model.SchemaModel and model.components.Field in the class-based API.
The implementation should be fairly straightforward since these attributes shouldn't really effect any part of the validation process. The three parts I can think of are:

error reporting: when pandera raises a SchemaError or SchemaErrors exception, the title and description should probably be part of the error message somehow.
__str__/__repr__ methods: sort of related to (1), but these dunder methods should also include title and description
yaml/python script IO: as you mentioned, the new attributes should be added when calling the to_script and to_yaml methods.

I will have capacity to submit a pull request

That would be awesome! It might make sense if you added the title and description attributes to all relevant class definitions, and maybe part (3) as you're interested in this part of the enhancement. If you're up for it, (2) would also be fairly straighforward... (1) might be a little bit of a pain, as the way error-handling is done in the code-base is a little confusing and would stand to be improved from a developer perspective. Let me know what you feel like doing!
Also feel free to ping me here if you need any help re: setting up your dev environment.

Thanks @dustindall for being willing to submit a PR :)  Some pointers for the SchemaModel compatibility:

Field is just a function that generates a FieldInfo which constructs a Column/Index for SchemaModel.to_schema(). You could add title and description to Field/FieldInfo and pass those info when constructing the column/index.

We need to add a title/description to Config

Maybe it's just me, but I feel like the distinction between DataframeSchema.name (technical name) and DataframeSchema.title (reporting name) is very thin. I can see how it could be useful but the difference should be clearly explained in the doc.

Thanks @dustindall for being willing to submit a PR :)  Some pointers for the SchemaModel compatibility:

Field is just a function that generates a FieldInfo which constructs a Column/Index for SchemaModel.to_schema(). You could add title and description to Field/FieldInfo and pass those info when constructing the column/index.

We need to add a title/description to Config

Maybe it's just me, but I feel like the distinction between DataframeSchema.name (technical name) and DataframeSchema.title (reporting name) is very thin. I can see how it could be useful but the difference should be clearly explained in the doc.

but I feel like the distinction between DataframeSchema.name (technical name) and DataframeSchema.title (reporting name) is very thin

agreed. Is there a good reason (besides consistency) to have a title and name at the dataframe level? I think semantically they're different for columns/indexes since name maps onto the column/index name so having a human-readable title makes sense.
AFAIK, a dataframe only has a name attribute in a Groupby.apply function, where name is the discrete groupby value.
One solution would be to deprecate name in favor of title to represent a "human-readable label for the dataframe schema", and raise a DeprecationWarning when name is provided at the dataframe-level.

but I feel like the distinction between DataframeSchema.name (technical name) and DataframeSchema.title (reporting name) is very thin

agreed. Is there a good reason (besides consistency) to have a title and name at the dataframe level? I think semantically they're different for columns/indexes since name maps onto the column/index name so having a human-readable title makes sense.
AFAIK, a dataframe only has a name attribute in a Groupby.apply function, where name is the discrete groupby value.
One solution would be to deprecate name in favor of title to represent a "human-readable label for the dataframe schema", and raise a DeprecationWarning when name is provided at the dataframe-level.

Hey @tfwillems I saw you submitted #440, let me know if you're willing to make a PR for this :)
It should be pretty straight-forward to add these properties to all the relevant objects, since they don't touch the validation parts of the library.


Send email and create a stop file on build failure

Resolves issue #980.

Unfortunately the tests will likely always fail because it can't send mail...

@drkitty  This seems fine to me now.  Should I wait to merge and let you make test changes or just merge?

Uh, I'll look at tests. I'd like to avoid having failing tests on master.

Fixed!


[Frontend][Feature] Add jamba tool parser

Add JambaToolParser to support tool calling for ai21labs/AI21-Jamba-1.5-Mini and ai21labs/AI21-Jamba-1.5-Large

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

PR Description updated to latest commit (https://github.com/coffin5257/vllm/commit/25d839d61eec05da46a7cc3393306c5e866c7880)

Preparing review...

PR Reviewer Guide 🔍
Here are some key observations to aid the review process:

⏱ Estimated effort to review: 4 🔵🔵🔵🔵⚪
🧪 PR contains tests
🔒 No security concerns identified
⚡ Recommended focus areas for review
Possible BugThe test case 'test_extract_tool_calls_no_tools' does not seem to cover the scenario where the model output contains tool calls but they are not properly extracted. This should be further validated.
Code SmellThe method extract_tool_calls_streaming contains a lot of nested conditionals and logic, which can be hard to follow and maintain. Consider refactoring for clarity and readability.
Error HandlingThe error handling in extract_tool_calls_streaming logs an error but then skips the chunk. This might lead to data loss or incorrect parsing. Consider a more robust approach to error handling.

Preparing review...

Persistent review updated to latest commit https://github.com/coffin5257/vllm/commit/25d839d61eec05da46a7cc3393306c5e866c7880

Preparing review...

Preparing review...

Preparing review...

Persistent review updated to latest commit https://github.com/coffin5257/vllm/commit/2a25f1079b0472a2e45bc9595ad14715f8d8b0b6


Shadowrun 5e hide unused and show all buttons no longer work

Clicking the buttons hide unused skills and show all do not do anything when clicked, tested in multiple browsers. There is no way to add points to skills that were previously hidden, or default on them if they were previously hidden.
Edit: it is the Shadowrun 5th Edition (Advanced) version

Go to Attributes and Abilities => search for skillshowcheckbox and write on for the skills you want to see

Go to Attributes and Abilities => search for skillshowcheckbox and write on for the skills you want to see

There is no Attributes and Abilities page or skillsshowcheckbox on this sheet. There is a "main" page where attributes are, and a "skills" page where they are. On the skills page there is a list of every skill and buttons above each section that say 'hide unused ' and 'show all' and clicking these buttons used to make the skills appear. Now they do nothing.  There is no way to add in skills.

Even above that. Roll20 provides 3 tabs: Bio, Character and Attributes&Abilities I think.
The buttons should be fixed together with the import, when the code is merged next time

Even above that. Roll20 provides 3 tabs: Bio, Character and Attributes&Abilities I think.
You can also trigger it for single skills. They are ordered in appearance
The buttons should be fixed together with the import, when the code is merged next time

Yes, as you can see above when i tried the method you suggested, everything was deleted. All physical skills disappeared and I could not find a way to bring them back when I put "on" in the areas you said to, so that did not work and didn't turn out to be a viable work around.

I am also facing the issue and have managed to find a temporary work-around!
once more, go to the "Attributes & Abilities" tab.
There, find all the "skillhideunusedcheckbox(number)" and "skillshowcheckbox(number)" lines
Their values will either be 0 or "on". Both of these values are incorrect and result in hiding the skills.
What you want to do is switch the value to "1". Doing that reveals the box whose value you've changed.
The buttons still don't work but at least all the skill are visible now and none of the previously modified skill were changed.
Hope this helps!

This is resolved

@bananaferret


plugin: yaml library panics when used from plugin

I have already raised this with the yaml library here, hoping to narrow down the issue, but unfortunately the project doesn't seem to be terribly active. However I don't see how this problem could be the fault of the library.
What version of Go are you using (go version)?
go version go1.8rc3 linux/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/oliver/workspace"
GORACE=""
GOROOT="/nix/store/nz3j87ls421358ks5bd24dgq9c8z59sn-go-1.8-dev/share/go"
GOTOOLDIR="/nix/store/nz3j87ls421358ks5bd24dgq9c8z59sn-go-1.8-dev/share/go/pkg/tool/linux_amd64"
GCCGO="/nix/store/jm8nf0p2n6m092385kmb87zxhanxigvc-gccgo49-wrapper-4.9.4/bin/gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/run/user/1000/go-build507203162=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
What did you do?
// main.go
package main

import "plugin"
import "gopkg.in/yaml.v2"

func main() {
	var baz map[string]string
	yaml.Unmarshal([]byte("foo: bar"), &baz)

	handle, _ := plugin.Open("plugin.so")
	symbol, _ := handle.Lookup("Go")
	symbol.(func())()
}

// plugin.go
package main

import "gopkg.in/yaml.v2"

func Go() {
	var baz map[string]string
	yaml.Unmarshal([]byte("foo: bar"), &baz)
}

# Makefile
build: clean
	@go build -buildmode=plugin -o plugin.so plugin.go
	@go build -o main main.go

clean:
	@rm -rf main *.so

Build and run the executable with make && ./main.
What did you expect to see?
The program should complete successfully.
What did you see instead?
The following panic:
panic: expected end of document event but got 7 [recovered]
	panic: expected end of document event but got 7

goroutine 1 [running]:
plugin/vendor/gopkg.in/yaml%2ev2.handleErr(0xc420053ed8)
	/home/oliver/workspace/src/plugin/vendor/gopkg.in/yaml.v2/yaml.go:153 +0x95
panic(0x5a0c80, 0xc4200106e0)
	/nix/store/nz3j87ls421358ks5bd24dgq9c8z59sn-go-1.8-dev/share/go/src/runtime/panic.go:489 +0x2e7
plugin/vendor/gopkg.in/yaml%2ev2.(*parser).document(0xc4200be000, 0x7f24b3c8a144)
	/home/oliver/workspace/src/plugin/vendor/gopkg.in/yaml.v2/decode.go:141 +0x203
plugin/vendor/gopkg.in/yaml%2ev2.(*parser).parse(0xc4200be000, 0x5d3ce8)
	/home/oliver/workspace/src/plugin/vendor/gopkg.in/yaml.v2/decode.go:116 +0x100
plugin/vendor/gopkg.in/yaml%2ev2.Unmarshal(0xc4200106a0, 0x8, 0x8, 0x59a360, 0xc4200ac6c8, 0x0, 0x0)
	/home/oliver/workspace/src/plugin/vendor/gopkg.in/yaml.v2/yaml.go:84 +0x177
plugin/unnamed-8517ae4ac6807292a59c508315fef6ff06256b82.Go()
	/home/oliver/workspace/src/plugin/plugin.go:7 +0x9e
main.main()
	/home/oliver/workspace/src/plugin/main.go:9 +0xaa

The ordering of the yaml.Unmarshal() calls between the executable and the plugin doesn't seem to matter, but it does have to be called from both.
Tracing through the code, it seems that the plugin takes a completely different (and wrong) codepath when provided with the same input, and at certain points it changes when adding a simple fmt.Printf().

I can reproduce this with 1.8, but not with tip.  One of the recent plugin fixes might have resolved it, can you verify?

Confirmed fixed on tip.


Dependency Injection with Spark

Hello Dear,
Congrats by make this exceptional microframework.
I liked so much
Do you have some plan about DI native in Spark project?

Thanks! No plans for DI, we're trying to keep Spark as simple and small as possible.

Hello!
Jetty 9, already support for CDI, therefore I guess that this feature will not make spark bigger.


WIP: blog post Extend Falco inputs by creating a Plugin: Distribute the plugin

…ugin

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind user-interface

/kind content

/kind translation

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area videos

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 398464ea16b196235ba60de0f0f903d1e8c47860

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS [Issif,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


xcode build fail in Xcode 14

Discussed in https://github.com/fastlane/fastlane/discussions/20700

Originally posted by q1019736727 September 26, 2022
+-----------------------------------------------------------+-----------------------------------------------------------+
|                                                Summary for gym 2.210.1                                                |
+-----------------------------------------------------------+-----------------------------------------------------------+
| scheme                                                    | TMProject                                                 |
| output_name                                               | 420_10683_11113                                           |
| clean                                                     | true                                                      |
| configuration                                             | Release                                                   |
| export_method                                             | app-store                                                 |
| include_symbols                                           | false                                                     |
| include_bitcode                                           | false                                                     |
| xcargs                                                    | DEBUG_INFORMATION_FORMAT="dwarf-with-dsym"                |
| output_directory                                          | ./fastlane/build/420_10683_20220926                       |
| export_xcargs                                             | -allowProvisioningUpdates                                 |
| workspace                                                 | ./TMProject.xcworkspace                                   |
| silent                                                    | false                                                     |
| skip_package_ipa                                          | false                                                     |
| skip_package_pkg                                          | false                                                     |
| export_options.provisioningProfiles.com.tianma.yirenyibin | YiRenYiBin_dis_0312                                       |
| build_path                                                | /Users/tianma/Library/Developer/Xcode/Archives/2022-09-26 |
| result_bundle                                             | false                                                     |
| buildlog_path                                             | ~/Library/Logs/gym                                        |
| destination                                               | generic/platform=iOS                                      |
| xcodebuild_formatter                                      | xcpretty                                                  |
| skip_profile_detection                                    | false                                                     |
| xcodebuild_command                                        | xcodebuild                                                |
| skip_package_dependencies_resolution                      | false                                                     |
| disable_package_automatic_updates                         | false                                                     |
| use_system_scm                                            | false                                                     |
| xcode_path                                                | /Applications/Xcode.app                                   |
+-----------------------------------------------------------+-----------------------------------------------------------+

[13:43:14]: $ set -o pipefail && xcodebuild -workspace ./TMProject.xcworkspace -scheme TMProject -configuration Release -destination 'generic/platform=iOS' -archivePath /Users/tianma/Library/Developer/Xcode/Archives/2022-09-26/420_10683_11113\ 2022-09-26\ 13.43.14.xcarchive DEBUG_INFORMATION_FORMAT="dwarf-with-dsym" clean archive | tee /Users/tianma/Library/Logs/gym/TMProject-TMProject.log | xcpretty
[13:43:18]: ▸ Clean Succeeded
[13:43:23]: ▸ ** ARCHIVE FAILED **
▸ Clean Succeeded
** ARCHIVE FAILED **
[13:43:23]: Exit status: 65

+---------------+-------------------------+
|            Build environment            |
+---------------+-------------------------+
| xcode_path    | /Applications/Xcode.app |
| gym_version   | 2.210.1                 |
| export_method | app-store               |
| sdk           | iPhoneOS16.0.sdk        |
+---------------+-------------------------+

[13:43:23]: ▸ /Users/tianma/.jenkins/workspace/TMAutoProject/TMProject/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 5.0, but the range of supported deployment target versions is 11.0 to 16.0.99. (in target 'SAMKeychain' from project 'Pods')
[13:43:23]: ▸ /Users/tianma/.jenkins/workspace/TMAutoProject/TMProject/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.0.99. (in target 'TMWebAliLoginSDK' from project 'Pods')
[13:43:23]: ▸ /Users/tianma/.jenkins/workspace/TMAutoProject/TMProject/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.0.99. (in target 'GKPageScrollView' from project 'Pods')
[13:43:23]: ▸ /Users/tianma/.jenkins/workspace/TMAutoProject/TMProject/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.0.99. (in target 'FCVideoTV' from project 'Pods')
[13:43:23]: ▸ /Users/tianma/.jenkins/workspace/TMAutoProject/TMProject/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 11.0 to 16.0.99. (in target 'JXPagingView' from project 'Pods')
[13:43:23]:
[13:43:23]: ⬆  Check out the few lines of raw `xcodebuild` output above for potential hints on how to solve this error
[13:43:23]: 📋  For the complete and more detailed error log, check the full log at:
[13:43:23]: 📋  /Users/tianma/Library/Logs/gym/TMProject-TMProject.log
[13:43:23]:
[13:43:23]: Looks like fastlane ran into a build/archive error with your project
[13:43:23]: It's hard to tell what's causing the error, so we wrote some guides on how
[13:43:23]: to troubleshoot build and signing issues: [https://docs.fastlane.tools/codesigning/getting-started/](https://docs.fastlane.tools/codesigning/getting-started/%1B[0m)
[13:43:23]: Before submitting an issue on GitHub, please follow the guide above and make
[13:43:23]: sure your project is set up correctly.
[13:43:23]: fastlane uses `xcodebuild` commands to generate your binary, you can see the
[13:43:23]: the full commands printed out in yellow in the above log.
[13:43:23]: Make sure to inspect the output above, as usually you'll find more error information there
[13:43:23]:
[13:43:23]: Fastlane打包失败,具体原因请查看日志
+------------------+------------------+
|            Lane Context             |
+------------------+------------------+
| DEFAULT_PLATFORM | ios              |
| PLATFORM_NAME    | ios              |
| LANE_NAME        | ios appstore_dis |
| BUILD_NUMBER     | 11113            |
+------------------+------------------+
[13:43:23]: Error building the application - see the log above

+------+------------------------------+-------------+
|                 fastlane summary                  |
+------+------------------------------+-------------+
| Step | Action                       | Time (in s) |
+------+------------------------------+-------------+
| 1    | default_platform             | 0           |
| 2    | xcode_select                 | 0           |
| 3    | increment_build_number       | 1           |
| 4    | Switch to ios package lane   | 0           |
| 5    | Switch to ios updateCer lane | 0           |
| 6    | update_app_identifier        | 0           |
| 7    | update_code_signing_settings | 0           |
| 8    | automatic_code_signing       | 0           |
| 9    | get_build_number             | 0           |
| 💥   | gym                          | 15          |
+------+------------------------------+-------------+

[13:43:23]: fastlane finished with errors

 gym(
      scheme: "#{SCHEME}",
      output_name:"#{AppID}_#{AppVersion}_#{get_build_number()}#{ENV_PREFIX}",
      clean:true,
      configuration:option[:configuration],
      export_method:option[:exportMethod],
      include_symbols: false,
      include_bitcode: false,
      xcargs: 'DEBUG_INFORMATION_FORMAT="dwarf-with-dsym"',
      output_directory:"./fastlane/build/#{AppID}_#{AppVersion}_#{currentTime}",
      export_xcargs: "-allowProvisioningUpdates"
 )
```</div>

I'm having the same issue.
Xcode IDE build and archive commands succeed, although many errors are emmitted:
...
error: Dependency for P1:target-Redacted:Release:SwiftDriver Compilation Requirements Redacted normal arm64 com.apple.xcode.tools.swift.compiler is not absolute (Pods/GoogleMaps/Base/Frameworks/GoogleMapsBase.framework/Modules/module.modulemap). (in target 'Redacted' from project 'Redacted')
...

Xcode command line tool xcodebuild fails, most likely because of these errors. Although it does produce the .xcarchive file.
This looks like an issue in Xcode 14.0.
https://developer.apple.com/forums/thread/714549?login=true&page=1#729945022

We had the same issue, maybe the following things you can try to fix it:

By adding --versbose at the end of the fastlane command, there are more details, you might be able to find something useful.
Check the gym log, in our case, it is the gym log shows the right direction to fix this issue.

Our issue contains two parts:

It complains that the target contains macOs which is not included in the distribution file, so by removing the macOs from the General tab can fix this error
Some of the Pods don't have developer team selected, which is new on XCode 14, I think this might be some kind of bug in the new XCode. But the fix is also easy, this post is very helpful. (https://github.com/fastlane/fastlane/issues/20626)

After fixing the above two errors, my build is working fine. Hope the solution helps.

I've looked at the gym log file. There are many SwiftDriver errors emitted indeed by xcodebuild, but they do not seem to break the build. The list of errors end with:
...
error: Dependency for P1:target-[Redacted]-4d48d69388424f8acfb0a5e7d92f4c924d62802467c101da85f5b2047549d072-:Release:SwiftDriver Compilation Requirements Redacted normal arm64 com.apple.xcode.tools.swift.compiler is not absolute (Pods/GoogleMaps/Base/Frameworks/GoogleMapsBase.framework/Modules/module.modulemap). (in target 'Redacted' from project 'Redacted')

Command SwiftDriver Compilation Requirements emitted errors but did not return a nonzero exit code to indicate failure

The build log continues after the above and the build succeeds. Following the build CodeSign is invoked and the binary is signed successfully, generating the .app file. When I run Xcode > Archive from Xcode IDE, this is where the archive process ends and a popup window opens with the archive file, allowing me to export the archive as ad-hoc.
However, when running with fastlane from the command line, gym fails the archive and the command line output ends as follows:
** ARCHIVE FAILED **
ERROR [2022-10-13 17:30:29.41]: Exit status: 65

+---------------+-------------------------+
|            Build environment            |
+---------------+-------------------------+
| xcode_path    | /Applications/Xcode.app |
| gym_version   | 2.210.1                 |
| export_method | ad-hoc                  |
| sdk           | iPhoneOS16.0.sdk        |
+---------------+-------------------------+

Having the same issues - have not been able to create any builds in CI using xcode 14.

https://github.com/fastlane/fastlane/issues/20810#issuecomment-1303004100

I'm falling same issue...

Facing the same issue with this Xcode 14.0.x, on macOS 13.2 (Ventura)

Facing the same issue on macOS Sonoma and Xcode 15


'TeViT is not in the models registry'

Hi, I am trying to run this repo and i have followed all the steps mentioned in the description.
While running the inference code, I am getting the following error.
python tools/test_vis.py configs/tevit/tevit_msgshift.py checkpoints/tevit_r50.pth Traceback (most recent call last):   File "tools/test_vis.py", line 130, in <module>     main(args)   File "tools/test_vis.py", line 53, in main     cfg_options=args.cfg_options)   File "/home/quidich/.virtualenvs/tevit/lib/python3.6/site-packages/mmdet/apis/inference.py", line 43, in init_detector     model = build_detector(config.model, test_cfg=config.get('test_cfg'))   File "/home/quidich/.virtualenvs/tevit/lib/python3.6/site-packages/mmdet/models/builder.py", line 59, in build_detector     cfg, default_args=dict(train_cfg=train_cfg, test_cfg=test_cfg))   File "/home/quidich/.virtualenvs/tevit/lib/python3.6/site-packages/mmcv/utils/registry.py", line 212, in build     return self.build_func(*args, **kwargs, registry=self)   File "/home/quidich/.virtualenvs/tevit/lib/python3.6/site-packages/mmcv/cnn/builder.py", line 27, in build_model_from_cfg     return build_from_cfg(cfg, registry, default_args)   File "/home/quidich/.virtualenvs/tevit/lib/python3.6/site-packages/mmcv/utils/registry.py", line 45, in build_from_cfg     f'{obj_type} is not in the {registry.name} registry') KeyError: 'TeViT is not in the models registry'
Kindly, could you guide me if I want to create a file that directly runs this algorithm on a video or set of images and provide an out in the form of images and json format which gets saved in some folder?

Hi, @PoojanPanchal!
In most cases, registry issues is caused by inappropriate mmdetection installtion. You can run python setup.py develop to install TeViT. If you had installed other mmdetection based repo in your workspace before, these repos may be conflict to each other. You can use pip uninstall to uninstall the already installed mmdetection version and then reinstall the correct one!
Hope your ongoing research goes well!😁

Hey, I had the same issue because I tried to install mmcv-full before doing the python setup.py develop.
What worked for me was: pip uninstall mmcv and pip uninstall mmdet, then pip install mmcv==1.4.8 and finally cd into your cloned TeViT/ directory and do pip install . to install the correct mmdet version.


Will there be a plan to break down patch and contribute some patches to the upstream?

Why you need it?
When I read the source, I found that Higress uses a single patch to record the change from the upstream projects.
Therefore, Higress now have some huge patch file (9000 lines+), which will make the maintenance very hard.
Some features require patching several projects. For example, to add sentinel support, both go-control-plane and istio are patched. If we can move the patch into upstream, we can avoid some patches.
How it could be?
Break down the patch into multiple ones according to their features.
If possible, we can contribute some patches back to the upstream.
Other related information

Great idea, we'll be doing this during upgrade work #8, and we'll do our best to get most of these changes accepted by the upstream's community.

@spacewander I am +1 on this. We should reduce patches, otherwise it will be hard to maintain.


zfs version detection is edge-casey

User requirement
As a dotmesh user, I want zfs version detection to work in the case that I've got zfs loaded in my kernel but I've lost my /bundled-lib docker volume (dotmesh-kernel-modules) so that dotmesh can be restarted without be restarting docker.
Steps to reproduce / test a fix
Without restarting docker:

dm cluster init
docker volume rm dotmesh-kernel-modules (or docker volume prune)
dm cluster reset && dm cluster init

Fixed I think