fix typo in README

fixing typo

Checklist

Issue number for this PR: #nnn (required)
Docs included?: (yes/no; required for all API/functional changes)
Test units included?: (yes/no; required)
e2e tests included?: (yes/no; required for multi-function/multi-class changes)
In a clean directory, npm install, npm run build, and npm test run successfully? (yes/no; required)

Description

Code sample

I signed it!

looks like the bot is acting up and double posting

Thanks!


Performance regressions since DataFusion 15.x

Describe the bug
I noticed that some benchmark queries are slower in DF 16.

q17 is a good example. DF 16 uses a cross join instead of an inner join.
DataFusion 15.0.0
Projection: CAST(SUM(lineitem.l_extendedprice) AS Float64) / Float64(7) AS avg_yearly
  Aggregate: groupBy=[[]], aggr=[[SUM(lineitem.l_extendedprice)]]
    Filter: CAST(lineitem.l_quantity AS Decimal128(30, 15)) < CAST(__sq_1.__value AS Decimal128(30, 15))
      Inner Join: part.p_partkey = __sq_1.l_partkey, lineitem.l_partkey = __sq_1.l_partkey
        Inner Join: lineitem.l_partkey = part.p_partkey
          TableScan: lineitem projection=[l_partkey, l_quantity, l_extendedprice]
          Filter: part.p_brand = Utf8("Brand#51") AND part.p_container = Utf8("JUMBO BAG")
            TableScan: part projection=[p_partkey, p_brand, p_container], partial_filters=[part.p_brand = Utf8("Brand#51"), part.p_container = Utf8("JUMBO BAG")]
        SubqueryAlias: __sq_1
          Projection: lineitem.l_partkey, Float64(0.2) * CAST(AVG(lineitem.l_quantity) AS Float64) AS __value
            Aggregate: groupBy=[[lineitem.l_partkey]], aggr=[[AVG(lineitem.l_quantity)]]
              TableScan: lineitem projection=[l_partkey, l_quantity, l_extendedprice]

DataFusion 16.0.0
Projection: SUM(lineitem.l_extendedprice) / Float64(7) AS avg_yearly
  Aggregate: groupBy=[[]], aggr=[[SUM(lineitem.l_extendedprice)]]
    Filter: part.p_partkey = lineitem.l_partkey AND part.p_brand = Utf8("Brand#51") AND part.p_container = Utf8("JUMBO BAG") AND lineitem.l_quantity < (<subquery>)
      Subquery:
        Projection: Float64(0.2) * AVG(lineitem.l_quantity)
          Aggregate: groupBy=[[]], aggr=[[AVG(lineitem.l_quantity)]]
            Filter: lineitem.l_partkey = part.p_partkey
              TableScan: lineitem
      CrossJoin:
        TableScan: lineitem
        TableScan: part

To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Configuration settings used:
    "datafusion.explain.logical_plan_only": "false",
    "datafusion.optimizer.repartition_aggregations": "true",
    "datafusion.catalog.has_header": "false",
    "datafusion.execution.parquet.pruning": "true",
    "datafusion.catalog.default_schema": "public",
    "datafusion.optimizer.top_down_join_key_reordering": "true",
    "datafusion.execution.batch_size": "8192",
    "datafusion.optimizer.enable_round_robin_repartition": "true",
    "datafusion.optimizer.filter_null_join_keys": "true",
    "datafusion.optimizer.hash_join_single_partition_threshold": "1048576",
    "datafusion.execution.coalesce_batches": "true",
    "datafusion.catalog.create_default_catalog_and_schema": "true",
    "datafusion.execution.collect_statistics": "false",
    "datafusion.execution.parquet.skip_metadata": "true",
    "datafusion.optimizer.repartition_joins": "true",
    "datafusion.optimizer.repartition_windows": "true",
    "datafusion.execution.time_zone": "+00:00",
    "datafusion.execution.parquet.reorder_filters": "true",
    "datafusion.explain.physical_plan_only": "false",
    "datafusion.catalog.default_catalog": "datafusion",
    "datafusion.execution.target_partitions": "24",
    "datafusion.catalog.information_schema": "false",
    "datafusion.optimizer.prefer_hash_join": "true",
    "datafusion.execution.parquet.pushdown_filters": "true",
    "datafusion.execution.parquet.enable_page_index": "true",
    "datafusion.optimizer.skip_failed_rules": "true",
    "datafusion.optimizer.max_passes": "3"

The expected plan in
https://github.com/apache/arrow-datafusion/blob/master/benchmarks/expected-plans/q17.txt
is still showing the inner join?

Yes, I checked that as well. I wonder if it this bug is triggered by the specific options I am setting (noted in the issue)

oh, wait .. the API chaged betwee 15 and 16 and df.logical_plan now returns the unoptimized plan ...

https://github.com/apache/arrow-datafusion/issues/5646


Synchronize metadata types between pgvector.add_texts() and pgvector.similarity_search_with_score_by_vector()

…similarity_search_with_score_by_vector()
pgvector.add_texts() stored metadata to postgresql is from dict to string, but pgvector.similarity_search_with_score_by_vector() get metadata just string from database, when struct Document object, report error:
pydantic.error_wrappers.ValidationError: 1 validation error for Document
metadata
  value is not a valid dict (type=type_error.dict)

thanks fro pr @yungang!
where do you see pgvector.add_texts() converting dicts to strings? or does that happen on postgres side?

@yungang Hi , could you, please, resolve the merging issues and address the last comments (if needed)? After that, ping me and I push this PR for the review. Thanks!

Closing because the PR wouldn't line up with the current directory structure of the library (would need to be in /libs/langchain/langchain instead of /langchain). Feel free to reopen against the current head if it's still relevant!


makefile: feature: added commit id and build time

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

I don't think this code bakes the build time and commit id directly into the binary. It seems to echo it to terminal, I'm not sure if that's what the maintainer wants.

Got your point.

@Flamingo09 just wanted to check on the progress with this PR and incorporating @pavan-kalyan's feedback.

This feature was added in #295


Changing RHEL version requirements

Removing RHEL 7.2 to 7.x requirements by linking to Compatibility Matrix

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Looking at that Compatibility Matrix, the s390x entries only seem to list RHEL 7.4, not 7.3.  Am I misreading? :smile:

Approving with @bermudezmt

So, it's been approved even though it's wrong, the incorrect info was pointed out ages ago, and - checking again - it's still wrong?

Relates to https://github.com/docker/docker.github.io/pull/6452 as well.

@justinclift sorry we missed your previous comment. We're looking into correcting this at the moment.

@david-yu Can you please address @justinclift's comment? https://github.com/docker/docker.github.io/pull/7201#issuecomment-411930390 CC: @bermudezmt

Opened another PR to address those issues that conflict to the compat matrix: https://github.com/docker/docker.github.io/pull/7933


Automatically detect redundant namespaces on the page

Is your feature request related to a problem? Please describe.
On a daily basis, we should include required namespaces in GIP->namespacesRequired. It's ok for 2-3 namespaces but for large projects, it's hard to remember and maintain which namespaces should be included and which should be removed. For example, we have a namespace called validations_namespace. It contains translates for error messages. We should use it on every page where form validation is needed, actually on every page with form. Let's say we're going to add a newsletter form on the homepage, then we should include validlations_namespace in its GIP. And if we decide to remove a form we should delete validations_namespace. Also, let's say we have a pricing section which should be reused on several pages. This page has its own namespace which should be included on such pages. Actually, it's hard to maintain big number of namespaces.
We're investigated interesting behavior. If the namespace is not included, it renders translation code on SSR but then loads translate on the client-side. So there is only one way to detect missing namespace - check how does the page is rendered on the server-side and compare it with the client side. We're using a custom HTTP backend to load translates from the database.
Describe the solution you'd like
Would be nice to show some warning in the console like 'namespace validations is required on the page index.tsx' for missing namespaces. Also, it would be nice to show a warning like 'namespace validations is included but not used on the page index.tsx' for redundant namespaces.
Describe alternatives you've considered
For the moment I don't have any alternatives. Will be appreciated any suggestions.
Additional context
There is an example of our homepage namespacesRequired

Sounds like a job for some rollup plugin, because it's similar to the 'treeshaking'.
I see it like having any number of source translations files, but on build time the bundler will come and split all this translations into chunks suitable for different routes automatically, considering usage statistics.
Separate question - how to deal with non-unique keys declared in different namespaces.

Did you check if something from this list is close?
https://www.i18next.com/overview/plugins-and-utils

@ivadimko The problem you are describing is a difficult one, and it's not as simple as "treeshaking", unfortunately.
The most straightforward way to solve this problem would be to do away with the concept of namespaces entirely, and simply do tree-traversal, pushing each used key into a keysNecessary array on the first render, and then re-render with your unique subset.
This approach has two drawbacks:

Degrades SSR performance (but SSG and ISR would remain unchanged)
No ability to detect dynamically-composed keys, or keys that become required after user actions

Another possible approach, which is currently just a proof of concept, can be seen here.
The short answer is that the problem you have described is an unsolved problem, but is basically the final step in "solving" translation in JavaScript.


USHIFT-4025: Implement MicroShift image mode container build procedure

packaging/imagemode/Containerfile.repobase looks like a usable Containerfile to productize this.

/lgtm


Makes gcp attributes accessible

Just like my last pull request adding a function to Subscriber, this pull request adds a function to SubMessage making the underlying attributes sent with GCP accessible.

Coverage remained the same at 45.194% when pulling 61c2a7c1c9f6f244f74d0d8955de508a382d0ded on wezzle:gcp-attributes into 49569794cd14dfc6c8be1ade960878e5541dbb9a on NYTimes:master.

Unfortunately, this change breaks the interface contract on gizmo/pubsub.Subscriber:
	*Subscriber does not implement "github.com/NYTimes/gizmo/pubsub".Subscriber (wrong type for Start method)
		have Start() <-chan *SubMessage
		want Start() <-chan "github.com/NYTimes/gizmo/pubsub".SubscriberMessage

Is there any way you can encapsulate the information you need inside the message payload? Perhaps an 'envelope'-like struct that holds metadata and the payload?

Sorry, totally missed that. I'll take another stab at it.

Ok so i've changed back the interface part to pubsub.Subscriber. The public gcp.SubMessage now has Attributes that is filled on Receive if msg is of type messageImpl to make sure code does not break on type conversion during tests where the msg is of type testMessage.
External code can now use msg.(*gcp.SubMessage).Attributes to access the original GCP Attributes sent with the message itself.
Also i've added a test to prevent future errors with the pubsup.Subscriber interface.
Please let me know if you see anything wrong with this, or any improvements.

Coverage decreased (-1.2%) to 43.967% when pulling 5d4750c18be469e1766dd6a23a87ed5e33884719 on wezzle:gcp-attributes into 49569794cd14dfc6c8be1ade960878e5541dbb9a on NYTimes:master.

Ok, I think that's an acceptable workaround for folks who really need the attributes.
Looks like we have some kind of merge conflict on this now. If you can clean that up, I'll pull this in.

How can I see what the conflict is? The message under this pull-request shows there are no conflicts with the base branch?

Ah, it just wouldn't let me 'rebase and merge'. Squashing and merging...

🌮 thanks again!


db:seed does not work

Hi,
Does not have possibility to seed database?
I suggest one simple trick to force auth by first user, what you think about.
# malhal/laravel-createdby/src/CreatedBy.php line 52
if (!$user && App::runningInConsole()) {
    Auth::loginUsingId(1);
    $user = Auth::user();
}

Hi thanks for using the project! Usually with seeding it's all static data so you would just hard code created_by 1.

Hi thanks for your reply.
My problem is when you runnig php artisan db:seed that does not exist user to use, so $user->getKey() does not exists.
But yes, second solution work fine, but if you want save time to user, you can add this lines to project, can I open one branch for that if you want.

just seed the user first and keep the $user variable to use

Or if this is a different file just load the user with user = User::find(1);

Overall I think logging in the user with Auth in your seed file is probably the way to go.


[Catalog] Clicking a system in catalog leads to 404

Clicking a system in the catalog leads to a 404
Expected Behavior
It'd be great to see a nice system overview page!  Or not be linked at all, yet.
Current Behavior
A brief blip of the outline of a page, followed by an entity not found page takeover.
Possible Solution

If a system page exists, let's link it / use it (or if we have a mock/comp for such a page, let's implement it!)
If we don't have such a page yet, we should at least un-link the system in the catalog table.

Steps to Reproduce

Your Environment
https://demo.backstage.io

Transferred the issue to the backstage/demo repository since the problem doesn't exist in the example-app of the backstage/backstage repository (just verified by clicking on a system from catalog page). Thanks!

Fixed in #24

Wohoo!


cultist

General information:
Project issue is for:
3.8.0
Expected result:</br
Actual result:
Went into raid to kill cultist for quest killed them but noticed no bot spawned at all only 3 cultist only tested on factory (only got them to spawn once so far) console also thorwing error
How to reproduce:

get cultist to spawn
kill them
see if game has any other bot spawn in

Log files:
Server: (found in /user/logs/server-yyyy-mm-dd-xx.log)
BepinEx: (found in /BepinEx/LogOutput.log)
Client: (found in /Logs/log_<date>_<version>/<date>_<version> traces.log)

Attachments

server-2024-01-11.log (1527 KiB)
LogOutput.log (82 KiB)
2024.01.11_18-41-26_<IP_ADDRESS>.28375 traces.log (326 KiB)

Originally written by hughz001

dont know if this is still an issue, please can you check this again on 3.9.0? will close for now

Originally written by CWX


Make newest version of redbeat work with py2.7 and our version of celery 3.1.420

 [cap @ 0.5d] properly get celerybeat updating req's and re-ship segment PR


io: print less confusing error message if IO_uring is not available

When IO_uring is disabled (eg, by default in docker), kernel returns ENOSYS, and Zig converts that to SystemOutdated. This is misleading --- the system might be perfectly up-to-date, and the io_uring just disabled by some security policy.
As we have an explicit version check above, it is most likely that SystemOutdated means security stuff, so print an appropriate error message.
I wish I could point the user at a specific security policy, but it looks like there are at least two ways to disable io_uring:

via seccomp
via systcl https://lwn.net/Articles/937013/

related: #2241

Aha, so if it is not permission denied, then it must be seccomp! Added that case!

Yeah, linking to docs sounds like a fantastic rule of thumb for cases like these!


Freeze npm dependencies

When starting from scratch, this gives a clean working frontend environment that passes the Selenium tests.

I discussed that with nickjs himself, and in the case of hopscotch his changes were merged upstream from v0.2.8 onwards. In the case of react-bootstrap-date-picker, all but one of his changes were merged upstream from v5.0.0 onwards, and the missing change is irrelevant since ANET does not use the clear button on any date picker.


Fix custom visual shader nodes not being loaded at startup

Fix https://github.com/godotengine/godot/issues/67268

Thanks!


Fix PyPi README

https://pypi.python.org/pypi/open_source_library_data_collector/

Hi @thinkingserious can you expatiate on this?

Hi @andela-ijubril,
The README is not showing up on PyPi. It should look something like this: https://pypi.python.org/pypi/sendgrid

Hi @thinkingserious I just sent a PR for this issue and I saw that if failed to pass on Travis.
While setting up on my machine I also discovered that it is breaking. I think you might want to include the version of each of the package you have that is working at your end in the requirements file, because when I try to downgrade some packages I passed some blockers while setting up e.g I downgraded sendgrid to sendgrid==2.2.1 and I met another blocker in the github package. so I feel explicitly specifying the packages with version numbers would help pass the blocker.
Also, I sent in the contributors agreement already.
Thanks... I'm sorry for the long comment

Thanks for the feedback @andela-ijubril, I will take a look.
With Best Regards,
Elmer

@andela-ijubril,
Please take a moment and fill out this form so we can send you some swag: https://docs.google.com/forms/d/e/1FAIpQLSelP4uF-wGJebxVYq1DYw5WzHomEUauab3YiqrshyCkRs0fqw/viewform#start=invite
Thanks!


feat: support vue router next

close #15

:tada: This PR is included in version 2.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Local author id (me) as property

I'd like to have option for changing author me as it would erase needment for writing middleware that would be replacing it for correct id (possibly with huge performance impact upon message batch loading from server).

Yep, should be awesome if you can declare "me" as a prop so we can use ID instead of me. Would be silly to write some function that detects who is me at what time :)

Hello and thanks for stopping by.
I definitely agree. me doesn't make much sense to be honest.
@MaeseppTarvo's proposal makes sense, if you could make a PR I would merge it and make the final adjustments if needed.
Cheers.

@mattmezza I created PR #116

being worked on in #194


Rename ParticlesMaterial to ParticleMotionMaterial

Closes https://github.com/godotengine/godot-proposals/issues/5047.
As according to the original proposal, the reasoning for this PR is because its original name could be too vague, should there be more types of Particle-related materials in the future.
Also affects their file names and documentation.

I suppose I should do something like that for the other class getting a rename, too?

Does it make sense to still call it material when it no refers on how the particle renders?

Please feel free to discuss it, especially in the proposal. I just did this to close something on the 4.0 milestone.
For me, it's still technically a "Material", as it affects the way particles are rendered, but most especially, it inherits from Material.

ParticlesMaterial not only affects particles' motion, but also their color, scale, and emission location, whereas ParticleMotionMaterial implies that it is only useful for motion related properties. So I don't think this is a good rename.

ParticlesMaterial not only affects particles' motion, but also their color, scale, and emission location, whereas ParticleMotionMaterial implies that it is only useful for motion related properties. So I don't think this is a good rename.

Can it be separated? Maybe you want particles what have same motions but different scale, color, emission, etc

Closing, as the original Proposal has been modified.

Indeed this could've just been force-pushed on top of the existing PR, but no matter at this point. It's already superseded by https://github.com/godotengine/godot/pull/64566.


support private endpoint using private link resource alias

Issue-id
PR Checklist

[x] I have added example(s) inside the [./examples/] folder
[] I have added the example(s) to the integration test list for normal (~30 minutes) or long runner >30 minutes
[x] I have checked the coding conventions as per the wiki
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change?

Description
I would like the possibility to create a private endpoint for the external private link resources using private_connection_resource_alias. It will be useful when it is required to establish an internal connection with external providers or even connection to non peered vnet (when vnet addresses are overlapping)
Does this introduce a breaking change

[ ] YES
[x] NO

Testing
an example added in the example folder. but I could not provide any valid private link resource alias to test.

Hi @LaurentLesle @arnaudlh. Will you consider supporting this feature?


The provided data is invalid

The provided data is invalid
https://connecthkuhk-my.sharepoint.com/:f:/g/personal/jiepeng_connect_hku_hk/Er7bpbBAxMBBnZfDvdvrO1kBu2tkTpnMw9XXfeuQzkwOlA?e=Yf0Bbj

I apologize for the inconvenience, but my previous university storage account has expired. Please use the following new link to access the relevant data: https://1drv.ms/f/c/0beb177a0003262c/EiwmAwB6F-sggAsiBAAAAAABb0F_gavzzsqE4MLdqmkhgw?e=jQwoo5.
If you encounter any issues downloading the data, please don't hesitate to reach out to me via email.
Best,
Jiepeng


ffprobe_path returns ffmpeg path

ffprobe_path() uses sidecar_path() which hardcodes .join('ffmepg').
Seems like it needs ffmpeg_sidecar_path() and ffprobe_sidecar_path().

@prabirshrestha thanks for pointing this out.
I'll merge a PR with the quick fix -- however I'll address this more thoroughly when also investigating using ffmpeg-static as the source of binaries. That will address a few other outstanding issues:

Download path differs between cargo test, cargo run, and cargo run --example -- and sometimes the downloaded binary can't be found
Some distributions do not include ffprobe in the first place


Neo cli multisignature contract creation feature

added multisignature contract creation function extends create command.  …
close #150
usage:

dotnet neo-cli.dll
open wallet MYWALLET.json/.db3
create multisig { owners:["MYACCOUNTPUBLICKEY","034d6dcbf866c428ea3061b94cc271f5955acd87891001b2086198d405a717d6f4","038bb46ca1d4237edf875faa2dafe7a020a9d8597cce401ee5372b0ae3e800f5f4","03b257916c38f64582ebb2a21a15bf419b45d433c382e18eb7f97e36be4dc21303"], required: 3 }

Useful for development.
Enjoy it!
<EMAIL_ADDRESS>

I will accept @lock9's implementation. #156


new simple theme

Look great for technical blog, so I want ported this
Port from Hugo theme
https://github.com/ojroques/hugo-researcher

ported from Jekyll theme
https://github.com/ankitsultana/researcher

OR
https://github.com/heiswayi/thinkspace

https://oroques.dev/notes/
https://muhammadraza.me/


Fix currying in production

Fixes https://github.com/acdlite/recompose/issues/55

Current coverage is 99.50%

Merging #56 into master will decrease coverage by -0.50% as of 659b99c

@@            master    #56   diff @@
=====================================
  Files           39     39
  Stmts          202    202
  Branches         0      0
  Methods          0      0
=====================================
- Hit            202    201     -1
  Partial          0      0
- Missed           0      1     +1

Review entire Coverage Diff as of 659b99c

Powered by Codecov. Updated on successful CI builds.


Adds TraceListener and adds server property to request events

https://github.com/hyperf/hyperf/pull/6062


Add interactions search endpoint

It was a bit unfortunate that I had to modify those query tests in the other search apps – I think we could probably move those up a level and maybe consolidate them?
I've also used a DRF serialiser here to validate the POST body. I think we can look at doing this across the search apps. I've seen a few other things that we could probably tidy up as well.

Codecov Report

Merging #419 into develop will increase coverage by 0.03%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #419      +/-   ##
===========================================
+ Coverage    96.02%   96.05%   +0.03%
===========================================
  Files           89       90       +1
  Lines         2994     3020      +26
  Branches       258      260       +2
===========================================
+ Hits          2875     2901      +26
  Misses          82       82
  Partials        37       37

Impacted Files
Coverage Δ

datahub/search/elasticsearch.py
95.53% <100%> (+0.2%)
:arrow_up:

datahub/search/interaction/serializers.py
100% <100%> (ø)

datahub/search/interaction/signals.py
100% <100%> (ø)

datahub/search/interaction/views.py
100% <100%> (ø)

datahub/search/omis/views.py
97.87% <100%> (-0.05%)
:arrow_down:

datahub/interaction/views.py

datahub/interaction/serializers.py

Continue to review full report at Codecov.

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

Can you just remove the [DH-488] from the commit messages? You can add it to the PR text as reference.

Then the commits won't appear in JIRA and it's a useful point of reference when looking at why something changed in a file etc. They could go in the second line but then it'd be the only thing there in most cases.


Change git password

Just changed my github password but can’t for the life of me find where to change it in stash. Tried to follow the code backwards but have got nowhere.
I’m trying to clone a private github repo if it helps

Did that, still throwing a 401 error when I try to clone and I also noticed I’m now getting the following error on pushing (to a public repo)
stash: <type 'exceptions.AttributeError'>: 'function' object has no attribute 'urlparse'

as a temporary workaround, in bin/git.py, at line 391, change
config = repo.repo.get_stackedconfig()
to
config = repo.repo.get_config()

Also, implement the fix in #332:  search and replace all urlparse.urlparse with simply urlparse.

Thanks, I'll give it a go

Okay, #333 fixes the first issue as well.

Ok given it a go, done the find and replace but my git.py (python modules/site-packages/stash/bin/git.py) does not have that on line 391 or in it at all, any get config is already config = repo.repo.get_config().
Cloning a non private repo now works under python 2.7 though is completely silent, still fails under python 3 complaining about no module called urlparse (though this is a separate issue).
Committing also still has the same problems
I am still unable to clone a private repo with the same dulwich 401 error

I feel this issue has got out of hand though, I’m closing this (I’ve fixed my password) and will open sone new issues.


Add output boolean device for each timer to trigger automations

Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
When an octopusagile.timers time period becomes active (on), set a boolean (like input_boolean) that can be used to trigger an automation. The boolean should become inactive (off) when the timer is no longer triggered. Each boolean output would be named using a timer "name" attribute.
Describe alternatives you've considered
The following snippet doesn't appear to work (log: helper fails to find entity):
timers:

day_from: tomorrow
day_to: tomorrow
entity_id: input_boolean.immersion_request

Additional context
The idea is to find the cheapest time(s) to turn on a device, but with the ability to override with automation conditions. E.g. turn on immersion heater at cheapest time(s), but only if current price < 3p and "holiday mode" input_boolean is false. If the immersion doesn't come on, I have gas as a backup.

allow input_boolean as an output #31


Configuration of the appearance of the copy-to-clipboard icons

Thanks for a great Hugo theme!
For my site I don't want the copy-to-clip-board icon for inline code tags but keep it for code tags within pre tags. I was able to achieve this by adding this css:
:not(pre) > code + span.copy-to-clipboard {
    display: none;
}

It would be really handy if it would be possible to configure the appearance of the copy-to-clipboard icons from the config.toml file.  Maybe this could be considered for future versions of the theme.

Fixed in v2 8dccd68886ab09ea4b9bb755c5b0bca3758b269c


Log Out from Queue

Describe the bug in current situation
When user tries clicks on Log Out button, (top right hand corner of the queue screen) they are taken to an error screen.
Error Message Showing
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">SOAP-ENV:BodySOAP-ENV:FaultSOAP-ENV:ClientSOAP Processing Error. Exception processing request</SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
Link bug to the User Story
Impact of this bug
User is unable to log out successfully
Chance of Occurring (high/medium/low/very low)
High - happening for both Jacklyn and Matt
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Steps to Reproduce
Steps to reproduce the behavior:

Log in with IDIR
Wait for Queue to Load
Click on Log Out

Actual/ observed behaviour/ results
After conversation with Abin is appears to be a permission issue. We will troubleshoot and fix so all users who log in will be able to Log Out
Expected behaviour
A clear and concise description of what you expected to happen. Use the gherking language.
Screenshots/ Visual Reference/ Source

@m-prodan created bug here and assigned to @abin-aot we can meet tomorrow to troubleshoot together.

Fix Details:
The expected role to be associated with staff must be reviewer.
Made changes in realm.
Can you please retest.


Fix a typo in README.md

Fix the typo in README.md
Motivation:
https://lists.apple.com/archives/xcode-users/2007/Jan/msg00073.html
"The C language is case-sensitive. Compilers are case-sensitive. The Unix command line, ufs, and nfs file systems are case-sensitive. I'm case-sensitive too, especially about product names. The IDE is called Xcode. Big X, little c. Not XCode or xCode or X-Code. Remember that now." — Chris Espinosa

@swift-server-bot test

Thanks!


Revert "Add class to ingress"

Reverts lightbend/akka-operator-helm#15

yup, it must only be updated by the release.
I think @chbatey updated it because of some integration test. Might have to follow up on that.


🌱 change GVK to use olm.operatorframework.io

solves #340

e2e / upgrade-e2e failure is expected, since gvk will not be the same across versions for the upgrade, and is a breaking change.

The upgrade e2e is failing...

I expect we may also need to change this in config/samples?


‘XInputGetStateEx’ was not declared in this scope

Hi,
I tried to compile the 64 bit version of your library but ran into this problem after installing libwine-dev libsdl2-dev cmake and build-essential using apt-get on an Ubuntu 17.04:
user@calculator:~/Downloads/koku-xinput-wine-1.2.1$ cmake -DBUILD_M32=OFF .
-- The C compiler identification is GNU 6.3.0
-- The CXX compiler identification is GNU 6.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Checking for module 'sdl2'
--   Found sdl2, version 2.0.5
-- Found wine headers: /usr/include/wine/windows
CMake Warning at CMakeLists.txt:84 (message):
  No 32-bit cross-compiler; skipping 32-bit tests

CMake Warning at CMakeLists.txt:97 (message):
  No 64-bit cross-compiler; skipping 64-bit tests

-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

    BUILD_M32

-- Build files have been written to: /home/user/Downloads/koku-xinput-wine-1.2.1
user@calculator:~/Downloads/koku-xinput-wine-1.2.1$ make
[ 12%] Building CXX object CMakeFiles/koku-xinput-wine64.dir/xinput.cpp.o
/home/user/Downloads/koku-xinput-wine-1.2.1/xinput.cpp:319:23: error: ‘XInputGetStateEx’ was not declared in this scope
 koku::jumper<decltype(XInputGetStateEx)> XInputGetStateExJumper;
	               ^~~~~~~~~~~~~~~~
/home/user/Downloads/koku-xinput-wine-1.2.1/xinput.cpp:319:23: error: ‘XInputGetStateEx’ was not declared in this scope
/home/user/Downloads/koku-xinput-wine-1.2.1/xinput.cpp:319:40: error: template argument 1 is invalid
 koku::jumper<decltype(XInputGetStateEx)> XInputGetStateExJumper;
	                                ^
/home/user/Downloads/koku-xinput-wine-1.2.1/xinput.cpp:320:50: error: ‘XINPUT_STATE_EX’ has not been declared
 DWORD WINAPI XInputGetStateEx(DWORD dwUserIndex, XINPUT_STATE_EX *pState) {
	                                          ^~~~~~~~~~~~~~~
/home/user/Downloads/koku-xinput-wine-1.2.1/xinput.cpp: In function ‘void koku::XInputInit(void*)’:
/home/user/Downloads/koku-xinput-wine-1.2.1/xinput.cpp:382:59: error: cannot convert ‘koku::jumper<unsigned int(unsigned int, int*)>’ to ‘int’ in assignment
	 koku::make_jumper(address, &koku::XInputGetStateEx);
	                                                   ^
CMakeFiles/koku-xinput-wine64.dir/build.make:86: die Regel für Ziel „CMakeFiles/koku-xinput-wine64.dir/xinput.cpp.o“ scheiterte
make[2]: *** [CMakeFiles/koku-xinput-wine64.dir/xinput.cpp.o] Fehler 1
CMakeFiles/Makefile2:67: die Regel für Ziel „CMakeFiles/koku-xinput-wine64.dir/all“ scheiterte
make[1]: *** [CMakeFiles/koku-xinput-wine64.dir/all] Fehler 2
Makefile:83: die Regel für Ziel „all“ scheiterte
make: *** [all] Fehler 2

Any idea what I am missing?

I removed all parts which contain XINPUT_STATE_EX and XInputGetStateEx in your code because it seems these things are no more included in xinput.h
After also installing gcc-multilib and g++-multilib I was finally able to compile but now the linker does not find -lSDL2. How can that be?
user@calculator:~/Downloads/koku-xinput-wine-1.2.1$ make
[ 50%] Built target koku-xinput-wine64
[ 62%] Building CXX object CMakeFiles/koku-xinput-wine.dir/main.cpp.o
[ 75%] Building CXX object CMakeFiles/koku-xinput-wine.dir/xinput.cpp.o
[ 87%] Building CXX object CMakeFiles/koku-xinput-wine.dir/device.cpp.o
[100%] Linking CXX shared library koku-xinput-wine.so
/usr/bin/ld: cannot find -lSDL2
collect2: error: ld returned 1 exit status
CMakeFiles/koku-xinput-wine.dir/build.make:146: die Regel für Ziel „koku-xinput-wine.so“ scheiterte
make[2]: *** [koku-xinput-wine.so] Fehler 1
CMakeFiles/Makefile2:104: die Regel für Ziel „CMakeFiles/koku-xinput-wine.dir/all“ scheiterte
make[1]: *** [CMakeFiles/koku-xinput-wine.dir/all] Fehler 2
Makefile:83: die Regel für Ziel „all“ scheiterte
make: *** [all] Fehler 2

After apt-get purge libsdl2-dev and apt-get autoremove I finally was able to apt-get install libsdl2-dev:i386 with its dependencies without problems and the compilation of the 32 bit library was also successful.
Now the library works without problems. I still don't know what's the issue with XINPUT_STATE_EX and XInputGetStateEx.


Tenant domain error in EI logs

Description
When running the services, the below WARN message is observed.
[2023-03-20 15:11:40,001]  WARN {org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver} - Tenant domain is not available in tenant request message context, hence it might not be set in the thread local carbon context
We were able to reproduce the issue when executing a task in a tenant environment, and from that task, we need to trigger a sequence where it calls an external endpoint.
We observed that when using an external endpoint only this WARN is getting printed now, and for internal endpoints, the flow is working as expected.
Steps to Reproduce

Create a tenant in EI 6.6.0 server.
Deploy the below task and sequence in the created tenant.
You will be able to see the below WARN message in the logs when executing the task.

[2023-03-20 15:11:40,001]  WARN {org.wso2.carbon.core.multitenancy.MultitenantMessageReceiver} - Tenant domain is not available in tenant request message context, hence it might not be set in the thread local carbon context
<?xml version="1.0" encoding="UTF-8"?>
<task xmlns="http://ws.apache.org/ns/synapse"
     name="testtask"
     class="org.apache.synapse.startup.tasks.MessageInjector"
     group="synapse.simple.quartz">
  <trigger interval="2"/>
  <property xmlns:task="http://www.wso2.org/products/wso2commons/tasks" name="message">
     sdaas
  </property>
  <property xmlns:task="http://www.wso2.org/products/wso2commons/tasks"
            name="sequenceName"
            value="testseq"/>
  <property xmlns:task="http://www.wso2.org/products/wso2commons/tasks"
            name="injectTo"
            value="sequence"/>
</task>

<?xml version="1.0" encoding="UTF-8"?>
<sequence xmlns="http://ws.apache.org/ns/synapse" name="testseq">
  <call>
     <endpoint>
        <http method="GET"
              uri-template="http://run.mocky.io/v3/59d0baf2-15ee-4e67-93cc-d66ba6976e74"/>
     </endpoint>
  </call>
  <log level="custom">
     <property name="### task executed ####" value="response received ####"/>
  </log>
  <drop/>
</sequence>

Affected Component
Enterprise Integrator
Version
6.6.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

Hi @chaveeka , @AnuGayan ,
As mentioned in comment [1] internal,
Since this is a critical flow. we will evaluate the feasibility of fixing this and update you asap.
Update:
working on reproducing and analyzing the flow.
[1] https://github.com/wso2-enterprise/wso2-apim-internal/issues/2386#issuecomment-1477467998
Thanks,
Malaka


Files downloading from page driven by PHP router.

I'm trying to use PHP Router in my app, and the problem is when I call the .pdf file to download.
Here is an example code
FILE
The router goes to the 404 page.
Could you advise any solution?
Thanks

The default htaccess file causes requests for pdf files to be directed to the router. Update your htaccess to remove rewrites for pdf files.
RewriteEngine On RewriteCond %{REQUEST_URI}  !(\.png|\.jpg|\.webp|\.gif|\.jpeg|\.zip|\.css|\.svg|\.js|\.pdf)$ RewriteRule (.*) routes.php [QSA,L]

Yes, It's obvious. It works perfectly.
ThX


v1.0.1 - Can't resolve 'uuid' in AccordionItem

I upgraded from 0.5.0 to 1.0.1 this morning and I am getting this message.
./node_modules/react-accessible-accordion/dist/AccordionItem/accordion-item.js
Module not found: Can't resolve 'uuid' in '/test/node_modules/react-accessible-accordion/dist/AccordionItem'

Hi @DavidFreetly,
uuid got replaced by consecutive. I suspect your node_modules to haven't updated properly.
Could you please make sure you nuke the node_modules folder (or at least /node_modules/react-accessible-accordion) and reinstall please?
Let me know how you go after that. Thanks.

Hi @vincentaudebert,
I thought the same thing so I did these things:

uninstalled the react-accessible-accordion
blew away my node_modules folder
cleared my npm cache....had to give the --force option to make it happen
installed the react-accessible-accordion

So, I did those steps and I still get the same error.
I checked your github repo and I see the changes to the code but it's like the npm registry is giving me the wrong stuff back when I do the npm install.
I've downgraded back to 0.5.0 and got my code working again so you can close this if you would like.

Thanks @DavidFreetly, looks like we might have mucked up our last build! We're going to re-publish immediately, so watch out for a new version in the next 10 mins or so.

Should be good now @DavidFreetly - version 1.0.2
Really sorry about that.
Let us know and I'll close issue if it's all good for you.

It's all good!


Fixed Issue#1

Brief Description of Fix
fixed a typo inside h1
Linked Issue
Closes #_ 1

!bounty 10


[1.21.1 NeoForge 21.0.167] broken kalan recipe

Describe the bug
unable to make the kalan, in my JEI menu the recipe shows "Empty Tag:  c:iron_ingots" with the error icon
To Reproduce
placing the recipe with 7 terracotta, 1 campfire, and 1 iron ingot does not create the kalan
Expected behavior
Screenshots or Videos

Operating System
win 11
Mod Version
0.2.0
Minecraft Version
1.21.1
Fabric/Forge Version
neoforge 21.0.167
Other Mods
farmer's delight
JEI
pufferfish's skills + attributes
farmer's structures
easy anvils
easy magic
mrcrayfish's furniture mod: refurbished
xareo's minimap
clumps
tree harvester
Please provide a list of all mods also being used.
Additional context
Add any other context about the problem here.

Appreciate you opening the issue! I’ve fixed the issue in development, and it will be included in version 0.2.0-beta-3, though it still needs a bit more work before release. If you would like to fix it right away I have attached a datapack that fixes the recipe. (Idea from discord, thank you!) If you add it to the datapack folder of your world you will be able to craft the kalan.
udKalanRecipeFix.zip

waahhhh thank u sm :) 🖤 having so much fun with the ube recipes !!
On Tue, Sep 24, 2024 at 11:00 ChefMooon @.***> wrote:

Appreciate you opening the issue! I’ve fixed the issue in development, and
it will be included in version 0.2.0-beta-3, though it still needs a bit
more work before release. If you would like to fix it right away I have
attached a datapack that fixes the recipe. (Idea from discord, thank you!)
If you add it to the datapack folder of your world you will be able to
craft the kalan.
udKalanRecipeFix.zip
https://github.com/user-attachments/files/17118581/udKalanRecipeFix.zip
—
Reply to this email directly, view it on GitHub
https://github.com/ChefMooon/ubes-delight/issues/27#issuecomment-2371953539,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BLQKA54XAWSTHD33NJUZDXLZYGSEXAVCNFSM6AAAAABOVU42USVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZRHE2TGNJTHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Just released version 0.2.0, which includes this fix. Glad you are enjoying the mod! New features are currently in development!
Modrinth | CurseForge


[deliver] submitted ipa for review using Deliver submit_build but it got released after the review

New Issue Checklist

[ ] Updated fastlane to the latest version
[ ] I read the Contribution Guidelines
[ ] I read docs.fastlane.tools
[ ] I searched for existing GitHub issues

Issue Description

Submitted a ipa for review using Deliver submit_build but it got released after the review, this is a serious issue..please look into this asap
Complete output when running fastlane, including the stack trace and command used

[INSERT OUTPUT HERE]

Environment

[INSERT OUTPUT HERE]

What exact command did you use to submit the build?
Did you set automatic_release?
Please also fill the issue template so we know what fastlane version you are using etc.

fastlane deliver submit_build --build_number '  options[:build_number]  ' -u "$username" --app_identifier "$app_identifier" --metadata_path "$meta_path" --screenshots_path "$screenshot_path" --run_precheck_before_submit false --force true --skip_screenshots true --skip_metadata true      This is the command i used to submit


Publish benchmarks

1. Describe the feature
Create benchmarks to quantify how kyuubi can speed up queries (these might be really hard to setup and understand this might not be realistic).
2. Motivation
If we can show kyuubi speeds up workflows then it'll be easier to get users!
3. Describe the solution
Setup a "typical environment" that organizations have.  We'll want this environment to be realistic and demonstrate the challenges that this typical environment can't handle (permissions, tuning, load balancing, etc.).
Setup a similar environment with kyuubi to demonstrate how this framework solves core business problems facing the organization.  The benchmarks should demonstrate that speed improvements are one of the benefits.
4. Additional context
This request might not be realistic because spinning up entire environments is costly and takes a lot of time.
That said, think there would be a big benefit of having these setup for user adoption.  If I can create a videos and show people how kyuubi solves a lot of their organizational challenges, then they'll have a compelling reason to start using the framework.

This is a nice suggestion. At NetEase,  we are in the middle of helping one of our inner customers port their legacy Hive queries(5k~7k) directly to Kyuubi. The current numbers show that they save both 50% compute resources and 70% total time cost at the same time. If converted to performance gains, that would be about a 6 to 8 times improvement. I hope it can be summed up as a success story ASAP.
It would be also nice that we can do a benchmark to compare Kyuubi, STS, and HiveServer2

also cc @turboFei @pan3793 @zwangsheng @ulysses-you

@yaooqinn - those are some juicy performance gains!
Send me a link to that case study after you write it up and I'll take a look.


Correctness issue with keyed virtual nodes

Minimal working example: http://jsfiddle.net/CARogers/o1m76ek8/2/
In the above example there are 3 states (see gridsOfNodesToRender) - a 5x2 grid, followed by a 5x3 grid then a 5x2 grid. Each virtual node is keyed with a unique key for it's position in the grid (the key is also the text of each square). At the end we should be left with a 5x2 grid, but it is diffed or patched wrong so there is at least one node in the wrong place (see 2-4):

Frame 1 - 5x2
Frame 2 - 5x3
Frame 3 - 5x2

This is a pared down example of a real problem I encountered in production code. I made an example closer to the actual problem here: http://jsfiddle.net/CARogers/tsjLprv0/
You can drag the squares around and they'll hide if they go off the edge of the grey square. Example video: https://www.dropbox.com/s/bnxf995zpjqit33/virtualDom.mov?dl=0

is this fixed with #181?  even though you're referencing a commit after that fix was applied, dist doesn't include that fix.

Oh awesome! Probably should have tried the latest version. Would it be possible to make point release with this fix (and possibly the other changes since 1.3.0) in it?

cc @Matt-Esch - can you do a release?

This doesn't appear to be fixed. I ran npm dist on top of latest master (3ea4f0e - I made a gist of it: https://gist.github.com/CRogers/b5328187a3223e6defc3) and it still fails in a different but equally bad way. See http://jsfiddle.net/CARogers/88d5dqj3/ (it has an updated external resource) and:

Frame 1 - 5x2
Frame 2 - 5x3
Frame 3 - 5x2

I've also updated the more complicated example: http://jsfiddle.net/CARogers/tsjLprv0/1/

@CRogers :disappointed: i'm sorry  about that.  the first part of fixing this is to get a reduced test case like https://github.com/Matt-Esch/virtual-dom/commit/ee8d4a25724fd874aa7907898748d2935b2436f8.  my plate is kind of full right now and i'll eventually get to this if someone doesn't do it before me but if you have any time to come up with a PR of a failing test case that will help get this done sooner.

Cool - I'll have a go at making a failing test case.

Is there a getting started dev guide anywhere?

good question... i don't think so but here's a quick start for you.

clone the repo
npm install
npm run browser - will start a server that serves the tests to the browser.  i write a failing test case and often use test.only( ... ) to isolate that one test and from there, i use the developer tools to debug the issue.  write some code, try again, and again, and again...
when i think i've fixed the bug, i make sure to change test.only( ... ) back to test( ... ) and run npm test to double-check that everything else is still working.

Thanks for that! Saved me loads of time. I've managed to make one test case (this time using smaller grids, which is nice) at https://github.com/CRogers/virtual-dom/commits/feature/191-keyed-correctness-tests. I'll try to make more if I can make any other small ones.

I tried debugging it myself, it seems the patch produced for the second call of diff is producing REMOVE patches for the right elements, but I can't work out the numbering/indexing system used for the ORDER patch, especially the reverse section.

i'm quite confident that the patches will be correct.  the likely candidate for the cause of this bug is (another) off-by-one error in https://github.com/Matt-Esch/virtual-dom/issues/104#issuecomment-73732749

to explain what you're looking at in a patch, the hash describes how to move nodes:
{
  0: 4
}

means move previous node 4 to position 0
reverse is the same thing in reverse
{
  4: 0
}

this helps with optimizing the reordering of nodes.  working from lowest index, to highest, we can figure out if a node currently at a lower index will be moved later and so we can leave it in place for now and maybe even won't need to move it if we put enough other nodes before it.

I think I've found where it's going wrong - it's the first patch call. The patch produced by diff seems correct, as on paper after the diff it should end up as:
0-0
1-0
0-1
1-1
0-2
1-2
(assuming that INSERTs insert at the end and the reverse property on ORDER is a mapping from old positions to new ones)
Whereas rootNode ends up like this after patch is called:
0-0
1-0
0-1
1-1
1-2
0-2

yeah, so you want to focus your attention at https://github.com/Matt-Esch/virtual-dom/blob/3ea4f0e6afe6ff01c056513d3b5743c540b45419/vdom/patch-op.js#L138-L174 which is where we take the diff and apply it to the nodes.  there must be an off-by-one error in there (again :disappointed:)

I'm now trying to follow along on paper but it's quite complicated. I going to have to give up for the day soon anyhow.

no problem, the test case helps me a lot and i'm glad to have someone new that at least takes an interest in that code - i definitely use paper when working on that section.  it's simple enough to get that code right without optimizations but the optimizations are what make it more difficult.

Mmmm, I would like to get involved in the project (primarily because it makes the haskell-on-the-web story a lot better) but I'm also trying to apply this at work to get rid of some mutable-spaghetti render code.
I've also just pushed up a simplified version of the test case (no more grids, only one diff/patch). I'm going to clean it up a bit more now.

awesome... if you use irc at all, join us at #virtualdom.  i'd love to do whatever i can to help anyone with an interest.


mgmt, add storage scope for auth

Description
fix https://github.com/Azure/azure-sdk-for-java/issues/39561
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


add: support for microsoft v1 endpoints which requires resource for token aud

Context: Azure and Dynamics365
Resource parameter depicts the identifier of the WebAPI that your client wants to access on behalf of the user. Most flows in OAuth involve 4 parties, the resource owner (aka user), the client (aka app), the authority (aka identity provider) and the resource (aka webapi). The audience of the access token that the authority generates is the resource identifier.

sorry i'll check this at next monday, thanks for your contribution :)

Hello @LucianDavies
Could you provide some pages about the resource param from MS help ?
Regards,
Theo

Hi @LucianDavies
Back to you again, one question, do you want to use light-odata in backend and consume service with ADFS oauth token by the client credential flow, because typically for server side, the authorized code flow is not worked.
in that case, we can add the 'scope' param in the oauth request
Regards,
Theo

let merge it firstly, I'll do some update later


Automated Package Upgrade

:tada: This PR is included in version 5.3.47 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Rakish Audacity & Sneak Attack trigger at the same time

Rakish Audacity (Swashbuckler feature) and Sneak Attack (Rogue feature) both trigger at the same time so the sneak attack add 2d6 bonus damage instead of 1d6.

If your rakish audacity has a damage formula in it, you aren't using the CPR one. Non-cpr issue.


[HUDI-235] Log files generated after pending compaction does not get deleted when using restoreToCommit

@n3nash : This is the bug fix that you made in production branch. Can you review it.

Closing this as dupe


amplify push "Packaging lambda failed function failed."

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.17.0
Amplify CLI Version
4.52.0
What operating system are you using?
Mac
Amplify Categories
storage, function, api
Amplify Commands
push
Describe the bug
After running amplify push, after confirming the changes I want to push, I get the following error
Packaging lambda failed function failed. Could not find npm executable in the PATH.
The npm executable is definitely on my path, so I'm not sure why it fails. However, the issue goes away after an amplify env checkout.
Expected behavior
amplify push succeeds.
Reproduction steps

git pulled our amplify package from master.
Make changes to schema.graphql (add two non-required fields to existing table)
amplify push
y when asked to confirm that I want to push changes.
get the error, "Packaging lambda failed function failed. Could not find npm executable in the PATH."

GraphQL schema(s)

Added two new fields to existing table, (names have been changed)

    newFieldA: AWSDateTime @auth(rules: [
        {allow: groups, groups: ["admin"],  operations: [create, update, read]},
        {allow: private, provider: iam, operations: [create, read, update, delete]}
    ])
    newFieldB: AWSDateTime @auth(rules: [
        {allow: groups, groups: ["admin"],  operations: [create, update, read]},
        {allow: private, provider: iam, operations: [create, read, update, delete]}
    ])

Log output
No response
Additional information
No response

Hi @yiweixia, do you use a node version manager like nvm? What version of npm is installed?

However, the issue goes away after an amplify env checkout.

After running checkout, are you able to push changes to your schema?

Nope, don't have nvm installed. Using npm version 6.14.13.

After running checkout, are you able to push changes to your schema?

Yeah, push succeeds and everything is working fine after amplify env checkout, so I'm not being blocked. It's just a weird issue that popped up.

Closing this issue as it seems to be working , if it fails with same error , comment on it and we will open this again


snippets: Add setInterval snippet

This PR adds the setInterval function snippet to JavaScript for parity with setTimeout.

Thanks!


gnome-terminal not working

When the install script runs the following line:
gnome-terminal --title "CONNECTOR B" -e "docker run --publish 8081:8081 --name connectorb --network=broker-localhost_default dscb"

it opens a new terminal window that immediately closes. The container is not started up.
If I replace the -e option with -- , then the terminal stays open but shows the following error message:
Failed to execve: No such file or directory.

The workaround from #39 works. I would propose that the install.sh script should not open a new terminal window but use the -d option for starting the containers. This might fix #42 too.

Thank you for your issue.
The initial idea was to let the users see how the components behave by looking at the terminal. I will look into removing the gnome-terminals and showing the users how to take a look look at the logs if they choose to.

In my case I needed to use
sudo apt install gnome-terminal
instead of
sudo apt-get install gnome-terminal

The new install script has removed the use of gnome-terminal as is now launching the components in detatched mode. This should be fixed with PR 41.


Unable to authenticate oculus account Gorilla Tag

Not sure if this is the right place to post this so sorry for wasting your time if it is. When I patch gorilla tag it says that it cannot authenticate my account so I was wondering if that was just something that happens when you have a dev version of the game or if there is something that I'm doing wrong. Thanks in advance 👋

That's normal behavior - you would need to make some kind of mod for gorilla tag to disable authentication by using a different server. Then you could use the patched version.


Ability to customise icon colour

I'm thinking of adding some setting where you would have a colour picker to choose icon colour.
There will also be some setting to keep the icon colour untouched.

Hey, I was thinking about picking this up but the requirements don't seem as fleshed out as I'd like so I have a few questions.

Where would this fit within the UI? On the context menu when you right-click? On the file info section on the side(I would guess the former rather than latter...)?

There will also be some setting to keep the icon colour untouched.

Wouldn't this just be the default and not an explicit setting (unless you meant to reset to the original colour)

Are there any other requirements that might have been missed out?

hey i would like to work on this, but one question this is feature is going to be only available for svg icons ?


Additional Examples

Added checkbox to dialog
Added Timer function
Removed Idle()

Thank you Ken. However the idle function could be useful for operations that have to be done sincronously with the interface update. So should be better to reintegrate also the idle function.

It might be worth changing the comment in the code to something like:
     """ Useful function to schedule tasks that need to be synchronised

with the interface update; otherwise use a Timer
Called every UPDATE_INTERVAL """
On 15/11/2015 22:23, Davide wrote:

Thank you Ken. However the idle function could be useful for operations
that have to be done sincronously with the interface update. So should be
better to reintegrate also the idle function.
—
Reply to this email directly or view it on GitHub
https://github.com/dddomodossola/remi/pull/73#issuecomment-156864189.
No virus found in this message.
Checked by AVG - www.avg.com http://www.avg.com
Version: 2016.0.7227 / Virus Database: 4460/11006 - Release Date: 11/15/15

wait, @dddomodossola did you merge this commit including the idle removal? was that the aim?

@nzjrs
I committed other changes, and added again the idle function. Maybe this is not the right way to do this, your right.


lodash version issue with v3.9.6

Hello,
I've installed the latest update : homebridge-config-ui-x v3.9.6
here the messages I get:

/homebridge # npm audit
                   === npm audit security report ===

                             Manual Review
         Some vulnerabilities require your attention to resolve

      Visit https://go.npm.me/audit-guide for additional guidance

Moderate        Prototype Pollution
Package         lodash
Patched in      >=4.17.11
Dependency of   homebridge-nest
Path            homebridge-nest > request-promise > lodash
More info       https://npmjs.com/advisories/782
Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   homebridge-nest
Path            homebridge-nest > request-promise > lodash
More info       https://npmjs.com/advisories/577
found 2 vulnerabilities (1 low, 1 moderate) in 2381 scanned packages
2 vulnerabilities require manual review. See the full report for details.

I've tried this:
$ npm i -g npm
$ npm i --save lodash.update

and even after a reboot, I still have a "lodash issue"
Any idea ?
Thanks for your help

This plugin has up-to-date dependencies to that fix these vulnerabilities. GitHub spams me with alerts if I don't action them :)
These issues, as noted by your logs are being caused by the homebride-nestplugin.
Additionally, you may want to enable this plugin in Docker using the supported method which takes care of all the setup/permissions for you:
https://github.com/oznu/homebridge-config-ui-x/wiki/Enabling-UI-with-Docker

Hello,
I've uninstall the homebridge-nest plugin and you are right, the npm audit is then clean.
But even if I reinstall the plugin via the Docker up to date as well as the homebridge-config-ui-x, I still have the 2 vulnerabilities (1 low, 1 moderate).
I'm gonna ask @chrisjshull for that.
Thank you.

It's a nested dependency, and I would say the risk is very low, but the reason it keeps that version keeps getting installed is its defined in the plugins package-lock.json:
https://github.com/chrisjshull/homebridge-nest/blob/master/package-lock.json#L622
An npm update / npm audit fix on that plugin should be all that is required.


Optionally allow auto-deregister on downtime.

Should we listen for when the process is exiting and automatically fire out a de-register if we boot with a config option that tells us to? I think it could be useful.

Should be able to call the new stop() method from #24. Should we add a listener in our module for the 'exit' event?

I'm thinking optionally yeah. By default, maybe not, but it could be a configuration option.

Okay so what if we do a deregisterOnCrash flag that is set to true by default, and then add process event listeners for uncaughtException and beforeExit, and check if the flag is true. If it is, call stop.

+1 @kesne

It feels a little aggressive. The deregister is going to happen automatically when the heartbeats fail. Also it makes it so you would probably never see DOWN in Asgard like we do today, it would show N/A instead because the instance wouldn't be registered at all. The Eureka status page would also look fine because it wouldn't show anything is down, you would have to notice that there's all the sudden 9 healthy instances instead of 10 (instead of 9 healthy and 1 down). You kind of lose track of that instance.
There's other options like taking it out of service... But that's usually used to enable / disable traffic. I'm not sure if that's better.

The main idea here is to notice the instances are down faster than the heartbeat can tell.

Totally understand the idea. I think calling stop on beforeExit sounds good (and a config option to disable), because it's intentional.
For uncaught exceptions let's just let the heartbeats fail as normal. With node process managers that auto-restart, users already have options to bring their app back up quickly to minimize periods where instances are down and Eureka isn't aware yet. Also under the normal model, clients have retry logic in so that if the first instance doesn't respond, the next one get's tried, etc. They have to have this, because while the Eureka server may know an instance has deregistered or gone down, clients (like ours) may not have that in their local cached registry. Odds are, even if you deregister early the clients wont find out for another 60 seconds anyway. But, I like the idea of doing it on an intentional exit.

I don't think this should be the responsibility of the eureka client. It provides a stop method which does all the necessary operations. Any consumer should preferrably close it gracefully before terminating.
In the event of a crash, Eureka correctly removes the service when heartbeats fail. Clients using the service must have circuit breakers built in (as theres no way to guarantee that we will always deregister - imagine a pulled TCP cable).
IMO this should be closed and the functionality should be implemented by consumers.

I'm good with that. Thanks for providing your thoughts!


added a Feature Histogram Widget

Linked to issue #58
New features:
This PR introduces a new widget to create Histograms from feature data in Labels/Points/Shapes/Tracks/Vectors layers. It's strongly based off of the ScatterWidget. I wasn't sure whether scatter.py was the right place to put it, but it felt like a better fit than histogram.py, which essentially just works with image intensity data rather than tabular data.
Example code snippet
This code snipped demonstrates what it does:
import numpy as np
import napari
from napari_matplotlib import HistogramWidget, FeaturesHistogramWidget

n_points = 1000
random_points = np.random.random((n_points,3))*10
feature1 = np.random.random(n_points)
feature2 = np.random.normal(size=n_points)

viewer = make_napari_viewer()
viewer.add_points(random_points, properties={'feature1': feature1, 'feature2': feature2}, face_color='feature1', size=1)

widget = FeaturesHistogramWidget(viewer)
viewer.window.add_dock_widget(widget)
widget._set_axis_keys('feature1')
widget._key_selection_widget()
widget._set_axis_keys('feature2')
widget._key_selection_widget()

This code is essentially also what I added to the tests (tests are passing locally).
Looking forward to hear your thoughts on this! :)

PS: @dstansby I didn't see that there was ongoing work on a different PR because it wasn't linked to the issue. Feel free to treat this as stale for while.

Hi @dstansby ,
thanks a lot for taking the time to review this! I think I can definitely get those changes done myself. I'll be on vacation in the coming week so PR should come sometime in the second-to-next week.

Hi @dstansby ,
I added your suggestions from above and replaced the magicgui widgets with pyqt code as has been done in the scatter widget in the meantime.

@pre-commit-ci autofix

Hi @dstansby ,
I'm not sure what you mean by figure test? I did add the following to the tests. This adds two points layers to the viewer with two sets of features assigned to each. I check whether the figure in the widget changes upon changing the key for the histogram and whether the plot changes as it should when the selected layer is changed.
    n_points = 1000
    random_points = np.random.random((n_points, 3)) * 10
    feature1 = np.random.random(n_points)
    feature2 = np.random.normal(size=n_points)

    viewer = make_napari_viewer()
    viewer.add_points(
        random_points,
        properties={"feature1": feature1, "feature2": feature2},
        name="points1",
    )
    viewer.add_points(
        random_points,
        properties={"feature1": feature1, "feature2": feature2},
        name="points2",
    )

    widget = FeaturesHistogramWidget(viewer)
    viewer.window.add_dock_widget(widget)

    # Check whether changing the selected key changes the plot
    widget._set_axis_keys("feature1")
    fig1 = deepcopy(widget.figure)

    widget._set_axis_keys("feature2")
    assert_figures_not_equal(widget.figure, fig1)

    # check whether selecting a different layer produces the same plot
    viewer.layers.selection.clear()
    viewer.layers.selection.add(viewer.layers[1])
    assert_figures_equal(widget.figure, fig1)

For a figure test, see e.g.,
https://github.com/matplotlib/napari-matplotlib/blob/87d34f586ae59e596507914479ce8b431b890d50/src/napari_matplotlib/tests/test_histogram.py#L8-L16
This using the pytest-mpl plugin to compare the generated image with an image stored in the repository in this directory: https://github.com/matplotlib/napari-matplotlib/tree/main/src/napari_matplotlib/tests/baseline

For the figure test: So @pytest.mark.mpl_image_compare will compare the returned image to any image in the baseline directory?

No, you'll need to generate the new test image - see https://github.com/matplotlib/pytest-mpl#usage for instructions.

@dstansby

No, you'll need to generate the new test image - see matplotlib/pytest-mpl#usage for instructions.

Ok, I added the baseline image, but for some reason, the generated baseline is not detected by the test...Sorry for the back and forth, I'm not so familiar with these testing schemes 🙈
Just as a sidenote: Setting everything up for pytest --mpl seemed quite complicated to me. It requires a few additional installation steps (pip install pyqt6 tinycss2) that did not seem evident to me from the.

No worries! If you don't mind, I'd be happy to pick this up and get the test working?

No worries! If you don't mind, I'd be happy to pick this up and get the test working?

Not at all! Would be cool though if it were documented somewhere for future contributions 👍

Looks like the test image was just in the wrong directory :) I also did a few other minor fixes, will merge this and do a new release of napari-matplotlib if the tests pass. Thanks a lot for the contribution, and sorry for how long it took...

Looks like it's just code coverage failing


v5 Namespace issues with Result

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[x] I have read the wiki page and cheat sheet, but there is no information I need.
[x] I have searched in existing issues, but did not find a same one.
[x] I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description
What
Trying to update to v5, we are seeing namespace conflicts with the new Result type that as added. We have a Result type as well that is shared across our projects. This is not your problem, but I was just reading this weekend that Apple is officially adding a Result type to Swift in the future (I assume with Swift 5). See that info here: https://forums.swift.org/t/accepted-with-modifications-se-0235-add-result-to-the-standard-library/18603
My suggestion would be to re-name Result to be a but more specific for Kingfisher, as I would be surprised if other users did not run into this if they have their own Result type. This would also future proof Kingfisher whenever Apple does release its own Result

Thanks for opening this issue.
The Swift module is just for this. To prevent this kind of conflicting, you can change Kingfisher related Result to Kingfisher.Result. This should be the correct way to do it.
However, this should be only required when you need to create the Kingfisher.Result for your own. When used in a method callback, the context of Kingfisher should be inferred for you and there should be no such case. May I know your use case? So I can give a better suggestion.
Apple's Result in the standard library is also considered. There is a plan to use some conditional compilation flag with Swift version to control which Result to be used. For now, we just keep the API similar so we can avoid most migration issues when official Result comes out.
So the design of the current Kingfisher.Result is intended, and I don't think there is a need to rename it.

@onevcat We have a pad, URBNSwiftyConvenience, which also includes a Result type. We reference our type throughout our app-- for now to be able to update to v5 I had to just be more specific with our references, ie URBNSwiftyConvenience.Result instead of Result (which now gives compile errors due to namespace issues).
This "workaround" does work for us now so we will be upgrading to v5! Our eventual plan also is to use Apple's Result as well whenever that is a thing.
Thanks again for your prompt responses!


fix: redirect to email sign up on first login

I'm using acceptedPrivacyTerms as a proxy for 'has logged in before'.  In reality new users have to have accepted the terms before logging in, but it's a useful flag that can be used to ask them (once) if they would like the newsletter.  I think we should migrate to a better name, though.
Also, this breaks the redirect via query parameters. Sorry about that - I'll try to restore it later.

@raisedadead, Updated the UI.

Thanks, the UI looks better, but we should use a native check box instead of this radio button (atleast thats what it appears like to the unsuspecting user).


Gulp to apache migration on server

Migrating my project from gulp to apache.
I am able to successfully run my UI and API is also running by using ProxyPass in my local system.
But components are not getting called in my server system as in server I have a domain name instead of localhost.
I am not sure what to use in Proxy for components.
Local Code : (Working fine)
ProxyPass /api http://localhost:8080/api
ProxyPassReverse /api http://localhost:8080/api
ProxyPass /components http://localhost:3000/components
ProxyPassReverse /components http://localhost:3000/components
Server Code (Not working)
ProxyPass /api http://localhost:8080/api
ProxyPassReverse /api http://localhost:8080/api
ProxyPass /components http://abc:3000/components
ProxyPassReverse /components http://abc:3000/components
#ProxyPass /components http://localhost:3000/components
#ProxyPassReverse /components http://localhost:3000/components
Brief Info:
Gulp is running on 3000
Apache : 80
Api : 8080
Error : Failed to load resource: the server responded with a status of 502 (Proxy Error) - for components.
Neither localhost nor domain name works in server. Please guide how can I check proxy pass.
Please guide.
Also please guide me how can I bypass using proxy pass for components, because if I use it, it works only after gulp serve.

Closing the issue.
Resolution : Copy the components folder (or all required folders) in apache source folder.


docs: Update documentation on metal support via NODE_LLAMA_CPP_METAL env

Description of change
Update the documentation of enabling or disabling metal support via the NODE_LLAMA_CPP_METAL environment variable. The current example only shows how to disable metal support when building llama.cpp bindings via the CLI command.
Pull-Request Checklist

[x] Code is up-to-date with the master branch
[x] npm run format to apply eslint formatting
[x] npm run test passes with this change
[ ] This pull request links relevant issues as Fixes #0000 N/A
[ ] There are new or updated unit tests validating the change N/A
[x] Documentation has been updated to reflect this change
[x] The new commits and pull request title follow conventions explained in pull request guidelines (PRs that do not follow this convention will not be merged)

@timothycarambat This environment variable only affects the compilation of llama.cpp; setting it in runtime like the example you provided is not supported.
There's already documentation for this environment variable here.
Thanks for the contribution anyway :)

@timothycarambat node-llama-cpp builds llama.cpp at runtime if no binaries are available.
It looks to you that this code works because you run it locally on a dev environment that doesn't have any pre-built binaries.
It won't work on a second run or on the module that's uploaded to npm


[Feature Request] Persistent notification when printing

I don't know if this is possible, but is there any way to have a persistent notification that is always on the lock screen when the print is ongoing? Maybe with a little bit of progress information.

Never saw a persistent notification. This is an interesting idea. Will check it out. Have you see the Today's widget? It shows progress and remaining time for all your printers in OctoPod.

Nice. Did not know about the widget. I just enabled it and put it at the top. I do feel that a persistent notification(again, if it's possible) would be a lot more useful since I the lock screen is a little more 'front and center' than the widgets screen.

Also, I just Googled it, and in the notifications settings, there is apparently in option to make notifications persistent, whereas temporary is the default. I turned it on just now, but I'm not 100% sure what that does.

Hey @simpat1zq , been reading about persistent or sticky notifications and from what I see it is up to users to configure how they want to treat certain notifications (e.g. if they want to stay and not disappear from the UI). However, I cannot see that it is possible to refresh content of a notification that is already on the phone. I guess that is what you were after.

I don't think persistent notifications are possible in iOS, not the way they exist in Android anyway (where some of them just get sticky and won't die). It is however possible for apps — well, for their back-ends anyway — to 'cancel' notifications already sent, so they disappear. iMessage is a prime example of that, where reading messages on a Mac will make the notifications disappear on the phone; and this is certainly available to other third-party apps too because Telegram does exactly the same thing. I'm not sure if it's possible to just nuke all previous notifications or if they have to be surgically removed one by one, but it may be possible to do so and send new ones, so that there's just one with the latest data. That's the closest to a persistent notification I can think of, personally.


[V3] findByID error on media collection in beforeValidate hook

Describe the Bug
Not 100% certain if this is a bug, or if it is something that I missed (or is missing) in the migration guide. But after migrating from V2 to V3, I noticed that I no longer could save my pages. I have been able to isolate the bug and put that in a repo for you to reproduce. In short;
The following code
hooks: {
    beforeValidate: [
        async ({data}) => {
            const res = await payload.findByID({
                collection: "media",
                id: data.blocks[0].id,
            })
        }
    ]
},

Will throw the following error
ERROR: The collection with slug media can't be found. Find By ID Operation.
err: {
    "type": "APIError",
    "message": "The collection with slug media can't be found. Find By ID Operation.",
    "data": null,
    "isOperational": true,
    "isPublic": false,
    "status": 500,
    "name": "APIError"
}

Link to the code that reproduces this issue
https://github.com/JeffreyArts/payload3-blocks-findByID-error
Reproduction Steps

Add an image to the media collection, any jpg will do
Add an entry to the demo collection, and add 1 block that relates to the image
A Something went wrong error will occur in the UI and the entry won't save ( The collection with slug media can't be found. Find By ID Operation will be thrown in the CLI)

Which area(s) are affected? (Select all that apply)
area: core
Environment Info
Payload: 3.1.0
NodeJS: 20.10.0
NextJS: 15.0.0

The hook should have req, and you should use req.payload.findByID. Can you try that?

That resolves it.
Just for my understanding. Is that because in V2, payload was initiated as a global object? By which I mean that the payload object that you import from node_modules got configured/modified, but in V3 this is no longer the case. When I import payload in V3, it always retrieves the "clean", "untouched", "fresh" payload object?

The hook should have req, and you should use req.payload.findByID. Can you try that?

Had to use req in a CheckboxFieldLabelServerComponent
const UseAsLabel: CheckboxFieldLabelServerComponent = async ({ req, siblingData }) => {

  const result = await req.payload.find({
  	collection: 'posts
  	where: {
  		id: {
  			equals: siblingData.post
  		}
    	}
  })

	return `Hey`
}

export default UseAsLabel


poll.poll() and EINTR

poll.poll() can currently return io::ErrorKind::Interrupted when an inner system call is being interrupted.
As all examples tend to ignore this, I was wondering whether this behavior was intentional, or if the function should silently retry when it happens. I'd be glad to submit a pull request for the later.

It was intentional to not catch it.
There should definitely be a way to call poll that doesn't catch EINTR, however if that should be the default, I don't know... Also, handling EINTR in the examples would add a bunch of noise :P.
Maybe it could be included in the documentation?

@carllerche since almost all users need to handle it, and not doing so is a common source of subtle errors, I certainly wouldn't consider having it in the examples as noise. Examples should show good usage -- as a template for actual programs -- not something overly simplified that nobody should actually use as is.
(For the same reason, the examples probably shouldn't use a ridiculously large event buffer, which caused the performance problems in https://github.com/servo/ipc-channel/pull/94 ...)

I would be open to having two fns. Poll::poll and maybe Poll::interruptible_poll that doesn't handle it.
Thoughts @alexcrichton

I'm not currently aware of any concrete use case to actually handle EINTR, so I'd be fine changing the behavior to handle EINTR and just leave the door open to adding a second fn in the future which doesn't handle it.

@carllerche I noticed the change reverted in 0.7, but could not find any related issues or discussion. Could you pls add some links here?

It was removed in #1056 to reduce the API surface, users can implement this functionally quite easily themselves. Furthermore EINTR should be properly handled by the user, e.g. process a signal, usually you shouldn't ignore this return value.

@Thomasdezeeuw thanks for reply. From other discussions, EINTR actually should be ignored by user in async code. Yes, it is quite easily to implement indeed.

Does tokio also require this?

Does tokio also require this?

What do you mean with this question?

Do applications using tokio also need to intercept EINTR?

No. If EINTR is not handled it is a bug.
On Wed, Feb 3, 2021 at 2:44 PM Frank Denis<EMAIL_ADDRESS>wrote:

Do applications using tokio also need to intercept EINTR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tokio-rs/mio/issues/494#issuecomment-772877667, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAABQJCJJZBT3UEQUFA4Q6LS5HGT5ANCNFSM4CVRXJFQ
.


Update/Delete Parent Spaces without having to rebuild the rig

One solution would be to add a fake field ps_nodes on the child node and connect all the nodes created during the parent space creation to that attribute.
when updating, simply delete all those nodes and re-create the parent space.

closed by 866897cf98f998ac777b8e480037a63c80e3e158


⚠ Silicon Valley Power has degraded performance

In 855cfe3, Silicon Valley Power (https://www.siliconvalleypower.com) experienced degraded performance:

HTTP code: 200
Response time: 10721 ms

Resolved: Silicon Valley Power performance has improved in 1c5089f after 14 minutes.


Gh 103 signature input does not work with lambda functions

Codecov Report

Merging #104 into develop will increase coverage by 0.08%.
The diff coverage is 66.66%.

@@              Coverage Diff              @@
##             develop     #104      +/-   ##
=============================================
+ Coverage      72.17%   72.26%   +0.08%
- Complexity       866      870       +4
=============================================
  Files            128      128
  Lines           2552     2553       +1
  Branches         266      267       +1
=============================================
+ Hits            1842     1845       +3
+ Misses           584      583       -1
+ Partials         126      125       -1

Impacted Files
Coverage Δ
Complexity Δ

.../java/uk/gov/gchq/koryphe/signature/Signature.java
81.81% <66.66%> (+2.74%)
16 <3> (+3)
:arrow_up:

.../java/uk/gov/gchq/koryphe/util/ReflectionUtil.java
75.86% <0%> (+1.14%)
28% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

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


[Failing Test]: PreCommit Java failures: org.apache.beam.runners.spark.CacheTest > cacheCandidatesUpdaterTest

What happened?
PreCommit Java checks fail forCacheTest > cacheCandidatesUpdaterTest as shown.
Issue Failure
Failure: Test is continually failing
Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
Issue Components

[ ] Component: Python SDK
[X] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[X] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

fixed by #31184


Moving Power BI Columns

The instructions for moving Power BI columns do not work with the current version of Power BI Desktop.

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

ID: bd156d86-a695-872c-1823-0d9181cf67cf
Version Independent ID: 50ea6b24-9d9d-2bef-baae-361263c514be
Content: Move columns - Power Query
Content Source: powerquery-docs/move-columns.md
Service: powerquery
GitHub Login: @jessli20
Microsoft Alias: bezhan

Hi @LimKaamen
Could you be more specific about what doesn't work? I tested moving columns with the April 2022 version of Power BI and was able to successfully move columns by using the Move option in the column dropdown and by dragging and dropping.

Closed due to lack of customer input.


Feature request: Possibility to disable Auto Timeout

currently when i use
.Notify(Callback, options);
The callback is triggered after 7 seconds with the callback result Action NotificationAction.Timeout
Even when IsClickable  is set to true in the NotificationOptions.
Because of that behavior after 7 seconds the notification is not able to react to that click event properly.

The notification should disappear after 7 seconds, hence they would be unable to click it. Is it possible to extend the time the notification appears, and is this happening for you?

I have the following situation. (on Ios but probably same on Android)

i get a notification.
the notification shows up in front (clickable)
the notification disappears from front to tray after few seconds(7?)
(and gets Timeout which executes its Action(with timeout result))
when i open the notificationTray and click on that notification, the notification (click) action is not executed because its already executed with an Time Out

Without that 7 second "AutoTimeOut" it would be possible to get the click Event from notifications that are stored in the notificationTray.

Sorry, but when the notification closes, it goes to the notification center. From there, the app can't access it. When you click on the notification from there, you can only know you clicked on it by overriding DidReceiveRemoteNotification in the iOS AppDelegate.cs.


restored the commented out code, this is also how it works in extensi…

…ons.
I created branches on github, then push a branch from here, so the name isn't good, it is the check io before abort io fix.

;	bruceuncle
;	14/10/2013
;
; The V2.00 source has these lines commented out.
; The Ultimate Amiga replacement binary has them restored:
;

;  Author:  Unknown???
;    Date:  14/10/2013
;
; The V2.00 source has some lines commented out in the device handling
; section.  A replacement binary in the Ultimate Amiga / AMOS Factory
; Downloads pages has them restored.  This required access to the sources
; as it's been assembled, not hacked.  So is presumably a necessary bug-fix.
; (I haven't covered devices in my own education yet!)
;

"this is also how is works in the extensions"
with Visual Studio Code and ctrl/shift/f
I searched and found the same pattern in many places, the code is also active in those places.

the comments in the code talk about "A replacement binary in the Ultimate Amiga / AMOS Factory Downloads pages"
I didn't know about this history, can anyone elaborate?

I am now concerned, this needs testing - I remeber when I used to use the produced version of amospro when i first started developing it would crash alot more often when saving files, i want to confirm to my self some how as this point of code is actually the master call to _LVOAbortIO from the whole amos system - I did loose work before trying to save, and I'm sure other have experienced this wher you have to recover from the .bak file - but i have not experienced that for a while - so again, this may actually a bug fix added after the production release and not a "mistake" that we should revert, so this issue should be up for more discussion and testing - i will do some confirmations for myself as well - so do not merge until testing is complete thank you.

tested against a previous build that had it commented out and my concerns must be unrealted to this.
It is ready for merge, as said the other parts of the code do this sma action.


[BUG] It will raise the exception of "conflict primary key" when inserting into auto_random primary column

Describe the bug

It will raise the exception of "conflict primary key" when inserting into auto_random primary column.
What did you do

execute in tidb
create table t(a biting primary key auto_random,b int)
execute in tispark

for i in range(100):
    insert into t values({i},{I})

execute in tidb

for i in range(100):
    insert into t(b) values(1)

What do you expect

success
What happens instead

tidb raise Duplicate entry '37' for key 'PRIMARY'
Spark and TiSpark version info

Git Commit Hash: 9687b70202584883fe5b88d39fb62d64867ebde2
Git Branch: release-2.3
UTC Build Time: 2020-10-16 02:40:15
Supported Spark Version: 2.3 2.4
Current Spark Version: 2.4.3
Current Spark Major Version: 2.4
TimeZone: Asia/Shanghai
TIDB: release-4.0

should throw error
add to document

writing to table with auto_random column is disable
https://github.com/pingcap/tispark/pull/1837


nri-bundle open CVEs on nri-kube-events container image

Bug description
Containers images that we use from the nri-bundle have been consistently failing security scans with trivy (https://github.com/aquasecurity/trivy) due to open CVEs.
Version of Helm and Kubernetes
$ helm version
version.BuildInfo{Version:"v3.5.1", GitCommit:"32c22239423b3b4ba6706d450bd044baffdcf9e6", GitTreeState:"clean", GoVersion:"go1.15.7"}
Which chart?
nri-bundle-3.3.1
What happened?
These are the containers that we use from the nri-bundle which have open CVEs
newrelic-fluentbit-output - 1.10.0
nri-kube-events - 1.6.0
What you expected to happen?
We expect the security scan to pass on all the containers we scan from the nri-bundle
How to reproduce it?
$ trivy image newrelic/newrelic-fluentbit-output:1.10.0
$ trivy image newrelic/nri-kube-events:1.6.0
Steps to reproduce the problem, as minimally and precisely as possible.
Run the trivy commands listed above and inspect the CVEs listed by trivy
Anything else we need to know?
Could you upgrade the nri-kube-events bundle to use the 1.7.0 version which currently has no open CVEs.

Closing this ticket because it was solved a few days ago.


IndexError: list index out of range

When im trying to access /clanwars/statistics/CLAN/players or clanwars/profile in both cases i get Internal Server Error.
Log:
2015-02-15 11:25:42,122 ERROR: Exception on /profile [GET]
Traceback (most recent call last):
File "/var/www/super/env/lib/python2.7/site-packages/flask/app.py", line 1817, in wsgi_app
response = self.full_dispatch_request()
File "/var/www/super/env/lib/python2.7/site-packages/flask/app.py", line 1477, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/var/www/super/env/lib/python2.7/site-packages/flask/app.py", line 1381, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/var/www/super/env/lib/python2.7/site-packages/flask/app.py", line 1475, in full_dispatch_request
rv = self.dispatch_request()
File "/var/www/super/env/lib/python2.7/site-packages/flask/app.py", line 1461, in dispatch_request
return self.view_functionsrule.endpoint
File "/var/www/super/whyattend/webapp.py", line 152, in decorated_function
return f(*args, **kwargs)
File "/var/www/super/whyattend/webapp.py", line 1843, in profile
performance = analysis.player_performance(played_battles, [g.player])
File "/var/www/super/whyattend/analysis.py", line 30, in player_performance
replay_major_version = int(replay_version_tokens[1])
IndexError: list index out of range
2015-02-15 11:24:52,484 ERROR: Exception on /statistics/5UPER/players [GET]
Traceback (most recent call last):
File "/var/www/super/env/lib/python2.7/site-packages/flask/app.py", line 1817, in wsgi_app
response = self.full_dispatch_request()
File "/var/www/super/env/lib/python2.7/site-packages/flask/app.py", line 1477, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/var/www/super/env/lib/python2.7/site-packages/flask/app.py", line 1381, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/var/www/super/env/lib/python2.7/site-packages/flask/app.py", line 1475, in full_dispatch_request
rv = self.dispatch_request()
File "/var/www/super/env/lib/python2.7/site-packages/flask/app.py", line 1461, in dispatch_request
return self.view_functionsrule.endpoint
File "/var/www/super/whyattend/webapp.py", line 152, in decorated_function
return f(*args, **kwargs)
File "/var/www/super/whyattend/webapp.py", line 176, in decorated_f
return f(*args, **kwargs)
File "/var/www/super/whyattend/webapp.py", line 198, in decorated_f
return f(*args, **kwargs)
File "/var/www/super/whyattend/webapp.py", line 1829, in player_performance
result = analysis.player_performance(battles, players)
File "/var/www/super/whyattend/analysis.py", line 30, in player_performance
replay_major_version = int(replay_version_tokens[1])
IndexError: list index out of range

Looks like one of your replays has some strange version format. Can you please save the following script as "findreplay.py" file to your tracker installation directory, activate your virtual environment and run it via python findreplay.py? https://gist.github.com/ceari/fee8d1fcca4bcd6b274d

(myenv)root@domeczek:/var/www/super# python findreplay.py
322
<IP_ADDRESS>
323
<IP_ADDRESS>
325
<IP_ADDRESS>
326
<IP_ADDRESS>
327
<IP_ADDRESS>
328
<IP_ADDRESS>
329
<IP_ADDRESS>
330
<IP_ADDRESS>
331
<IP_ADDRESS>
334
<IP_ADDRESS>
335
<IP_ADDRESS>
336
<IP_ADDRESS>
337
<IP_ADDRESS>
338
<IP_ADDRESS>
339
<IP_ADDRESS>
340
<IP_ADDRESS>
341
<IP_ADDRESS>
342
<IP_ADDRESS>
343
<IP_ADDRESS>
344
<IP_ADDRESS>
345
<IP_ADDRESS>
346
<IP_ADDRESS>
347
<IP_ADDRESS>

Thanks. The format of the version changed in 9.6.0, please try again with the new code.


Feature/allowing env in dotnet core

Description
Hi,
as I pointed out in this slack message, I want to use the Kubernetes Downward API to access k8s metadata like the namespace or node name as environment variables. This was previously not possible as this requires setting env: instead of envFrom:, i.e. not referencing a configMap. An example could be:
# deployment.yaml
spec:
  containers:
      env:
        - name: MY_NODE_NAME
          valueFrom:
            fieldRef:
              fieldPath: spec.nodeName`

I configured the chart so setting the values
# values.yaml
global:
  env:
    - name: MY_NODE_NAME
    valueFrom:
      fieldRef:
        fieldPath: spec.nodeName

should work now, enabling us to access k8s metadata as environment variables.
Chart
Select the chart that you are modifying:

[ ] core
[x] dotnet-template
[ ] pact-broker
[ ] azure-functions

Checklist

[x] Description provided
[ ] Linked issue
[x] Chart version bumped
[ ] README.md updated with any new values or changes
[x] Updated template tests in ${CHART}/tests/*.py

Closing this PR. Krzysztof was afraid enabling the K8s Downward API could be misused by some developers, e.g. by introducing a dependency on K8s infrastructure in code.
For the purpose of logging there are also other options


[Bug]  3 Follower 3 Observer 集群，挂掉一个Follower以后 show proc '/frontends' 非常慢

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
1.2.2
What's Wrong?
3 Follower 3 Observer 集群，挂掉一个Follower以后 show proc '/frontends' 非常慢，需要1分多钟才能查询结果。

What You Expected?
这种慢查询似乎不符合预期，查看Master 日志与平时没有太大的异常。
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Is it because of the network?
Will there be similar problems in the future?


Add jsDelivr links

jsDelivr is the fastest opensource cdn available and built specifically for production usage. It can serve any project from npm with zero config just like unpkg. This PR adds it to the readme as an alternative to unpkg.

Cool, thanks.


schema should load only those with suffix .graphql?

hi,
is it possible to limit
graphql.MustParseSchema(schema.GetRootSchema(), &resolver.Resolver{})

to only load file with extensions *.graphql?
im wondering if it also loads .go files as i can see schema/bindata.go and schema/bindata.go
im planning to add README.md into the directory schema...
thank you

@u007 Go-bindata allows you to ignore files, so you can supply a regex like -ignore=\.go to ignore go files. Unfortunately golang doesn't support negative lookahead/behind, so it's hard to write a regex that ignores anything but .graphql files.
But since go-bindata only compiles assets, you can define your GetRootSchema() function anyway you want. For example
func GetRootSchema() string {
	buf := bytes.Buffer{}
	for _, name := range AssetNames() {
                // Ignore files without .graphql extension
		if match, _ := regexp.MatchString(`\w+\.graphql$`, name); !match {
			continue
		}
		b := MustAsset(name)
		buf.Write(b)
		if len(b) > 0 && b[len(b)-1] != '\n' {
			buf.WriteByte('\n')
		}
	}
	return buf.String()
}

Hi, I don't think that this is an issue with the library. As @hampusohlsson has pointed out how you load the data is up to you. The schema is agnostic of whether you use a file/go-bindata/data store etc.


Try fixing enterprise contracts (again...)

/recheck

As FBCs builds are working, it seems there is no error in builds itself. Merging, as both the container image substitution and the hermetic configurations are required