[ADD] new iOS 17 calendar and reminders permission handling including full access and write only authorization

Goal
Referring to Issue-318 and PR-319: here is the solution to handle the new access levels for calendar and reminders under iOS 17 based on the existing code structure. This PR also takes into account the availability of iOS 17.
I have updated the documentation too.

To be honest, I like the solution in https://github.com/sparrowcode/PermissionsKit/pull/320 more. Because in this PR I feel to have two libraries CalendarFullAccessPermission and CalendarPermission is superfluous. They are about the same but different type only. https://github.com/sparrowcode/PermissionsKit/pull/320 makes is more compact.

Thanks for PR. I see 2 solution - one more library or extend init of calendar. Both are good, need check first which is more structed

I did this approach for a better consistency with the rest of the code. Because there are also two libraries for the permissions of location. I prefer consistency over the whole code base. Otherwise it would be time for a refactoring.

I did this approach for a better consistency with the rest of the code. Because there are also two libraries for the permissions of location. I prefer consistency over the whole code base. Otherwise it would be time for a refactoring.

Ah, I see. In that case you’re right!

I did this approach for a better consistency with the rest of the code. Because there are also two libraries for the permissions of location. I prefer consistency over the whole code base. Otherwise it would be time for a refactoring.

You exactly right but with location was mistake. I need redo it to one permission like calendar.
But thanks for follow current struct, its really show you care about it.
For now PR closed because merged #320


Find out how the History File works

Also, include a history file (+ bumpversion version names) in the history


Explicitly set xref handlers when eglot is enabled

Otherwise major mode's handlers might take place. For
example as in go-mode

Fixes #0000
{{{ Summarize what you've changed HERE and why }}}

Thanks!


Docker debug command in docker-outside-of-docker

The docker debug command doesn't work within a dev container using docker-outside-of-docker. I'd love to see this feature supported within dev containers.

Hi @samruddhikhandale ,
I have analysed this issue and found this:
Additional Debugging with Docker CLI
While there isn't a docker debug command, you can increase the verbosity of Docker CLI commands by using the --debug or -D flag. For example:
docker --debug info

or
docker -D info

@prathameshzarkar9 The docker debug utility provides very different functionality compared to the commands you posted. Here's the documentation on this command.

Hi @samruddhikhandale  @korverdev ,
I observed this feature is available only in beta version of docker cli whereas we are using only released version for docker cli.
Can you help us to know any other feature of devcontainers have this docker debug enabled? or beta version of docker cli installed in any of the features?

@prathameshzarkar9 I'm not sure I understand your question. Can you clarify what you want to know?
I wasn't aware this was considered a beta feature. It seems to come bundled all with Docker Desktop versions as far back as the start of the year and I get a nag encouraging me to use this feature when I stand up a dev container, so I was surprised to find it wasn't supported within a dev container.

Hi @samruddhikhandale ,
Need your intervention here. As this feature is not supported in any release of the docker cli. This feature is supported only in beta version and docker does not give any guarantee this will continue to support. They might discontinue this feature without any further notice.
can you help?

Hi @korverdev 👋

Get a debug shell into any container or image with the new docker debug command (Beta).

As @prathameshzarkar9 mentioned and as highlighted in the release notes you've linked, the docker debug command is currently in Docker Beta.
From the Docker Blog:

To get started, run docker debug  in the Docker Desktop CLI while logged in with your subscription account.

It appears the change isn't needed for the docker-outside-of-docker Feature; instead, users need to take action on their end to use this new command. I'm not sure how we can assist further since the availability is limited to your Docker subscription.
Let us know if anything is still unclear.
Also, once you have the ability to run docker debug, and if we can help support it in the CLI or our Features, don't hesitate to open a new issue. Thanks!

@prathameshzarkar9 @samruddhikhandale That makes sense. Thanks for clarifying!

@prathameshzarkar9 @samruddhikhandale docker debug is no longer in beta.


Sync eng/common directory with azure-sdk-tools for PR 1598

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/1598  See eng/common workflow

/check-enforcer override


feat(sma): add 'edgex-' prefix for executor-based API

Signed-off-by: Chris Hung<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?

For API that relies on executor, user needs to refer to the service by its container name:
curl http://localhost:58890/api/v2/system/metrics?services=edgex-core-data,edgex-core-metadata
207

...

Issue Number: fix #3559
What is the new behavior?
edgex- prefix will be automatically added for default service (those defined in edgex-compose file)
So user can either refer to those services by their service name (e.g. core-data) or container name (e.g. edgex-core-data)
Does this PR introduce a breaking change?

[ ] Yes
[x] No

New Imports

[ ] Yes
[x] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

Codecov Report

Merging #3570 (73b0ac4) into master (c3ee48e) will decrease coverage by 0.33%.
The diff coverage is 46.15%.

@@            Coverage Diff             @@
##           master    #3570      +/-   ##
==========================================
- Coverage   47.43%   47.10%   -0.34%
==========================================
  Files         111      115       +4
  Lines        8143     8214      +71
==========================================
+ Hits         3863     3869       +6
- Misses       3905     3970      +65
  Partials      375      375

Impacted Files
Coverage Δ

...ernal/system/agent/application/executor/metrics.go
0.00% <0.00%> (ø)

...nal/system/agent/application/executor/operation.go
0.00% <0.00%> (ø)

internal/system/agent/application/executor/util.go
54.54% <54.54%> (ø)

...rnal/system/agent/application/executor/executor.go
0.00% <0.00%> (ø)

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 c3ee48e...73b0ac4. Read the comment docs.

Swagger is using service name not container name right now.

currently, the service name in the example is "string", not a real example.
https://app.swaggerhub.com/apis-docs/EdgeXFoundry1/system-agent/2.x#/default/get_system_config__services_


mistral-7b model build failing

I am getting following error
AttributeError: 'NoneType' object has no attribute 'from_pretrained'.
python3 ../llama/build.py --model_dir=/models/mistralai/models--mistralai--Mixtral-8x7B-Instruct-v0.1/snapshots/125c431e2ff41a156b9f9076f744d2f35dd6e67a  --output_dir=./ --use_inflight_batching
--enable_context_fmha
--use_gemm_plugin

How did you fix it?

TL;DR:
pip install --upgrade transformers==4.37.2
pip install --upgrade accelerate==0.27.2

Context:
Apparently the error is caused by the following lines in build.py in the branch corresponding to the tagv0.7.1:
Lines 678-689:
hf_model = LlamaForCausalLM if args.model_type != "mixtral" else MixtralForCausalLM
hf_llama = hf_model.from_pretrained(
    args.model_dir,
    device_map={
        "model": "cpu",
        "lm_head": "cpu",
        "embed_tokens": "cpu",
        "layers": "cpu",
        "norm": "cpu",
    },  # Load to CPU memory
    torch_dtype='auto',
)

So if the model type is detected as mixtral, then MixtralForCausalLM object is used to call .from_pretrained method. However, that's how it's being imported:
try:
    from transformers import MixtralForCausalLM
except ImportError:
    MixtralForCausalLM = None
from weight import (get_scaling_factors, load_from_awq_llama, load_from_binary,
                    load_from_gptq_llama, load_from_hf_checkpoint,
                    load_from_hf_llama, load_from_meta_llama)

So the reason is the outdated version of the transformers package that's being included in the build of the version v0.7.1. (And also accelerate was throwing some error, needed an upgrade as well)
cc @riyaj8888 @teis-e


moving the disclaimer

trying to move the disclaimer text "Please note..." below the drop down bar.
Not 100% sure that this works, therefore creating a branch and requesting a PR.

@michaeljokf I'll check it

So, disclaimer is below dropdown (as you expected):

Thank you @kravets-levko yes agreed - should be less space!
BTW other issue I included a dataset description for Austria - if you have time to run it, I would like to see what it looks like before including all the others. Preparing them offline atm and will upload the rest of the descriptions today.

@michaeljokf Okay, I'll fix that spacing within openspending/subsidystories.eu/issues/31


The type of a class's prototype is interpreted as equivalent to the instance type of that class

TypeScript Version: v4.2.0-dev.20201130

Search Terms: "prototype type", "type of prototype", "typeof prototype"
Code
class C {
    instanceProperty: number;
    constructor() {
        this.instanceProperty = 0;
    }

    classMethod() {}
}

declare let x: C;
declare let y: typeof C.prototype;

x = y;

Expected behavior: An error like, "Property 'instanceProperty' is missing in type '{ classMethod(): void; }' but required in type 'C'."
Actual behavior: No error is reported.
Playground Link: https://www.typescriptlang.org/play?target=1&ts=4.2.0-dev.20201130#code/MYGwhgzhAEDC0G8BQ1XQJYDsIBcyeAFMAFAJwHsAHQ0nATwC5pMBXAWwCMaBuFNYcthykWwHOVIAKAJSI+aNDgAW6CADosufETJUa9aAF5oABl4KAvknnRQkCAFlCy8gBMZiK1YFC4AfUoKcXpqIzkFOygnF3dZBAsAGiQrJFdCO1JCaBBnaAAPJlheNIysnJxoRmgQwnIAM39A8mC6al4kPLC6biA
Related Issues: none
A more specific case involves referencing properties in type annotations.
// no error, as expected (since this aligns with how JavaScript resolves
// property references):
declare let a: C['instanceProperty'];

// no error, but expected an error like "Property 'instanceProperty' does not
// exist on type 'C.prototype'":
declare let b: typeof C.prototype.instanceProperty;

Duplicate of #11558, #20922, #30516.
The gist of those issues is that while it would be possible to synthesize a more correct type for a class's prototype, the benefits of doing so would not be worth the big breaking change to existing real-world code.

Ah, too bad. Thanks for the references!


[BEAM-10937] Tour of Beam use reshuffle before reading files

Use Reshuffle before reading files in the "Reading CSV files" example for the "Reading and writing data" notebook.
This makes sure each worker opens a balanced number of files.
R: @aaltay, @pcoet
Staged:

Notebook -- added a small description of why use Reshuffle and update the code cell to use it.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

I think this example is correct but I do not know if it is necessary to introduce this complication. Reshuffle is useful to prevent fusion. Not all runners do fusion (for example direct runner does not) and I am not sure how much this example explains why reshuffle might be needed here.

I agree that this might not be the best place to introduce this complication.
There seem to be a lot of other changes as well, e.g. WARNING:root:Make sure that locally built Python SDK docker image has Python 3.7s in the outputs.

@aaltay I know it adds more complication and concepts and for the sample data it's not required, but I think it would be a good practice since someone might copy-paste this example to start a new runner, without even being aware that they might need a reshuffle for things to autoscale properly. How about we make the note more explicit saying that it is useful for runners that do fusion?
@robertwb those warnings were introduced, I think in 2.30 or sometime around that version. It's now part of the standard running procedure and there's no way to remove them that I'm aware of. We could get rid of them by manually editing the code cell outputs (but it's very manual and error prone), or find a way to redirect stderr to /dev/null or something like that, but it might look hacky during the notebook setup.

I am not convinced that it is worth adding here and not sure if people will copy this example as is. (Because in a real production pipeline there will be other parts or concerns, this is meant as an example for a concept.)
We could consider adding reshuffle related docs as an option with use cases, and explaining its side effects in a bit more detailed way.


Move the prober library to the networking

Interestingly only test uses anything from pkg.
For #1679

/assign @tcnghia @nak3


fixed markdown

Added support to right links to remove 404 errors page.

@saragibby could you please review this request.


[Enhancement] support cast struct/map/array to json

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #19320
Problem Summary(Required) ：

Implement two functions:

JSON to_json(MAP)
JSON to_json(STRUCT)

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:heart_eyes: pass : 7 / 7 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/PrimitiveType.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/Type.java
2
2
100.00%
[]

run starrocks_admit_test

[FE PR Coverage Check]
:heart_eyes: pass : 10 / 11 (90.91%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/Type.java
4
5
80.00%
[1061]

:large_blue_circle:
com/starrocks/catalog/PrimitiveType.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/Function.java
1
1
100.00%
[]

run starrocks_admit_test

[FE PR Coverage Check]
:heart_eyes: pass : 10 / 11 (90.91%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/Type.java
4
5
80.00%
[1061]

:large_blue_circle:
com/starrocks/catalog/PrimitiveType.java
5
5
100.00%
[]

:large_blue_circle:
com/starrocks/catalog/Function.java
1
1
100.00%
[]

run starrocks_be_unittest

run all

@Mergifyio rebase

@Mergify rebase

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


App crashed when i select and crop image for profile.

Describe the bug.
When I tried to select an image for my profile I clicked on the upload and the complete action. I selected the image I want to use and click on the crop function immediately I clicked on crop the app crashed.
Screen recording.
https://youtu.be/cwIxaIMT6_8
Devices and Versions)

Device: [Gionee, X1]

Version [7.0]

App version [5.5.0]

@Swati4star Can I work on this?

Sure @sukhbeer 👍

@Swati4star I tried a different method for that issue but I didn't find anything wrong with that everything works fine I also test application in android version 7.0 there is no issue. if logcat detailed are provided for this it will be more clear.
Instead of this, I found that when we select or set image in profile and reopen application again user image not appear in navigation drawer and profile Activity also and found this error.

should I post this as an issue

@sukhbeer Then, what did changes you open up these Pull requests with?
regarding the error you posted, is the application crashing here? or you are just seeing this error?

@Swati4star sorry late reply I close the pull request few days ago. I don't see any error with default select image code.
regarding the error app not crashing here. This error come when user select or set image in profile and re-open application again user image is disappear as I earlier mentioned and I also share video
https://youtu.be/0MlIqhsre4o

@sukhbeer This seems to be a different issue than the one described here, please open a new issue. Closing this one since this seems to be fixed.
@darewealth Feel free to reopen if it isn't fixed


Add media indicator

Last chrome versions provide small indicator on tab where audio is playing.
This is very usefull when search these kind of tabs.

Seems, there is an API coming in Chrome 45 (audible). https://developer.chrome.com/extensions/tabs#property-query-queryInfo


language/independent-routines moved and wasn't accounted for

Problem or new feature
This can be a content problem or "just" an infrastructure problem depending on the chosen path.
It seems that https://docs.raku.org/language/independent-routines used to exist, confer https://web.archive.org/web/20221130232023/https://docs.raku.org/language/independent-routines and the content check https://github.com/Raku/doc/blob/0bd60bbfe5e227db21ff77cbf84160ce74b9a664/xt/rakudoc-l.rakutest#L33.
However, it doesn't exist now and instead there is https://docs.raku.org/type/independent-routines.
This means there are about a dozen broken links in the docs itself, and a former valid path that produces a 404 page as of now.
Suggestions
Either a redirect needs to be put into place that emulates the old links (in that case, I would rather rewrite the test to type/independent-routines at least), or the site generation needs to be restored in a way the independent-routines site is generated under language/ again.
Honestly, I think from the content perspective, type/ is a better path since this site is a reference page, not a tutorial - but either solution goes.

Fixed in the source, added a ticket (linked) for the redirect.


Enhance docs to explain deployment scenarios

What would you like to be added:
We maintain a helm chart that should be used in order to deploy OWA productively, however we do not have this documented. A getting started document on how to deploy OWA in a cluster will be helpful for new adopters and users.

Thanks for creating the issue.
A topic worth mentioning in this issue is that kubernetes apiserver will not be able to discover the service by name, based on https://github.com/kubernetes-sigs/kind/issues/1077#issuecomment-572209197 (It is not an issuer for other services.) If you already have a solution, it would great to mention it in the doc. If no solution, the kubernetes service needs to include ClusterIP, so that apiserver can talk to the service directly using the ID.

It would be nice to mention that jwks.keys could be used to configure providers in Registration of Providers. I had to make extra effort and go through the code to discover this.


Candle Stream Connection Failure

Hello all,
I noticed yesterday my script stop receiveing data around 10:13.  When I went to the logs, these were the latest entries. Is it safe to assume that my machine simply lost internet connection for a minute which is why the keepalive pings failed and eventually ended the connection?
DEBUG | 2024-08-08 10:13:26,508 | func: subscribe | line: 441 | sending subscription: {'type': 'FEED_SUBSCRIPTION', 'channel': 1, 'add': [{'symbol': 'SPY', 'type': <EventType.CANDLE: 'Candle'>}, {'symbol': 'QQQ', 'type': <EventType.CANDLE: 'Candle'>}, {'symbol': 'IWM', 'type': <EventType.CANDLE: 'Candle'>}, {'symbol': 'AAPL', 'type': <EventType.CANDLE: 'Candle'>}]} | MainThread: 17344
DEBUG | 2024-08-08 10:13:26,508 | func: write_frame_sync | line: 1174 | > TEXT '{"type": "FEED_SUBSCRIPTION", "channel": 1, "ad...I", "type": "Candle"}]}' [201 bytes] | MainThread: 17344
DEBUG | 2024-08-08 10:13:42,324 | func: keepalive_ping | line: 1261 | % sending keepalive ping | MainThread: 17344
DEBUG | 2024-08-08 10:13:42,324 | func: write_frame_sync | line: 1174 | > PING 10 45 97 98 [binary, 4 bytes] | MainThread: 17344
DEBUG | 2024-08-08 10:13:46,871 | func: _heartbeat | line: 415 | sending keepalive message: {'type': 'KEEPALIVE', 'channel': 0} | MainThread: 17344
DEBUG | 2024-08-08 10:13:46,871 | func: write_frame_sync | line: 1174 | > TEXT '{"type": "KEEPALIVE", "channel": 0}' [35 bytes] | MainThread: 17344
DEBUG | 2024-08-08 10:14:02,337 | func: keepalive_ping | line: 1271 | ! timed out waiting for keepalive pong | MainThread: 17344
DEBUG | 2024-08-08 10:14:02,337 | func: fail_connection | line: 1409 | ! failing connection with code 1011 | MainThread: 17344
DEBUG | 2024-08-08 10:14:02,337 | func: fail_connection | line: 1433 | = connection is CLOSING | MainThread: 17344
DEBUG | 2024-08-08 10:14:02,337 | func: write_frame_sync | line: 1174 | > CLOSE 1011 (unexpected error) keepalive ping timeout [24 bytes] | MainThread: 17344
DEBUG | 2024-08-08 10:14:03,991 | func: connection_lost | line: 1494 | = connection is CLOSED | MainThread: 17344
DEBUG | 2024-08-08 10:14:16,888 | func: _heartbeat | line: 415 | sending keepalive message: {'type': 'KEEPALIVE', 'channel': 0} | MainThread: 17344

It does look like that, but not quite for sure... It is something you've only experienced once? If you can reproduce it then it's likely a bug.

I have experienced it twice, both times last week.
I will monitor/try to reproduce and provide any updates.
On Fri, Aug 9, 2024 at 4:45 PM Graeme Holliday @.***>
wrote:

It does look like that, but not quite for sure... It is something you've
only experienced once? If you can reproduce it then it's likely a bug.
—
Reply to this email directly, view it on GitHub
https://github.com/tastyware/tastytrade/issues/161#issuecomment-2278793314,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BG6IS3ZUJWID27TF5BXXQ23ZQUZ53AVCNFSM6AAAAABMI4IDD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYG44TGMZRGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi @Vscheidell, v9.4 contains some utilities to handle connection failures by automatically reconnecting and optionally running a callback upon reconnection. Check it out, should make your app more resilient to these kinds of failures.


Return 404 when users try to access namespace for on namespaces they don't own

Use the my-namespaces endpoint for the edit namespace form. This automatically filters out namespaces that the user doesn't have access to.

Fixes: ansible/galaxy-dev#253


adjust the --oom-score-adj to -900 or lower (default is -8) for the most critical NB containers

disable oom kill for agent and vpn, and set compute-api, mgmt-api and traefik to -900

disable oom kill for agent and vpn, and set compute-api, mgmt-api and traefik to -900


CA2252 false positives in VS Code after OmniSharp update

I have a solution that sets LangVersion=preview and EnablePreviewFeatures=true. I've confirmed that the compiled assembly gets [RequiresPreviewFeatures] as expected. Yet, I get CA2252 in the editor on code like this:
namespace Vezel.Novadrop.Data.Serialization.Items;

interface IDataCenterItem<T>
    where T : unmanaged
{
    static abstract void ReverseEndianness(ref T item);
}

This didn't happen until I updated OmniSharp today.
Can be repro'd by cloning and building https://github.com/vezel-dev/novadrop at 0df3de26a6f65ff9ad12c1df7a25772a964efc84 and opening it up in VS Code.
Using C# extension 1.25.0-win32-x64 and OmniSharp 1.38.3-beta.87-net6.0.

why are you using 1.25.0 with an old version of OmniSharp? 1.25.0 bundles OmniSharp 1.39.0. Make sure to clear any omnisharp.path setting you might have

@filipw omnisharp.path is/was latest. Checking today, I'm now on 1.39.1-beta.2-net6.0 (I think it updated yesterday or so).

From what I can tell, this issue doesn't exist anymore, so closing.


Change to gratis license

As per discussion with @Amorymeltzer, this is the more appropriate license -- the binary is still free.

Hey @scw I think you meant to submit this PR to https://github.com/caskroom/homebrew-cask, not your own fork...

Yeah, I know -- I was trying to do everything just through the web, but the UI is pretty limited -- I'll create a fresh patch separately, thanks for the ping.

OK, created a valid pull request, thanks!


Incorrect drive type

Describe the bug
Drive A: is represented as a Floppy Disk - When in fact on my machine it is an internal hard drive
To Reproduce
Steps to reproduce the behavior:

In Disk Manager, change a second drives' drive letter to A:

Expected behavior
It's type is of hard disk

Thanks for the report. Drive A is just assumed to be a floppy drive (a bit old school)

Thanks for the report. Drive A is just assumed to be a floppy drive (a bit old school)

Thanks for the report. Drive A is just assumed to be a floppy drive (a bit old school)

LOL - I guess so, I remember the world before floppy's came to be - I often map A: to a NAS or USB drive nowadays. (HEIC to JPEG - dev)

Thanks for the report. Drive A is just assumed to be a floppy drive (a bit old school)

LOL - I guess so, I remember the world before floppy's came to be - I often map A: to a NAS or USB drive nowadays. (HEIC to JPEG - dev)

This issue should be resolved with #3211.

This issue should be resolved with #3211.


[rtl/prim_async_fifo] Fix async fifo typo when depth <= 2

This PR fixes a typo when depth <=2. Looks like the fifo_wptr_gray_d
should depends on fifo_wptr_d instead of fifo_rptr_d.
Details please refer to issue https://github.com/lowRISC/opentitan/issues/6575
Signed-off-by: Cindy Chen<EMAIL_ADDRESS>

Thanks for finding this @cindychip !

wow thanks for catching that @cindychip , kind of scary we didn't see this error sooner...

Formal only tested the sync version of the FIFO, I will add an async support by this week.. Should have been caught by that.


evaluate FRep at vector of inputs

Hello, I'd like to evaluate FReps at a vector of inputs as follows:
julia> using Descartes

julia> c = Circle(1.0)
Circle{Float64}(1.0)

julia> x = rand(2,10);

julia> FRep(c,x[1])
-0.8388503806040237

julia> f = FRep(c,x)
1.382979664762074

I would like the final output f to be a vector of size [1,10] with f[i] = FRep(c,x[i]). Could you help me get started with implementing this?

FYI - I'd like to use Descartes to model geometry for my differentiable meshing algorithms - https://github.com/vpuri3/DiffMesh.jl


Indentation bug

If head and body tags are not indented then output html is fine, but if they are not indented output html is ugly. Try to use blocks and template extension

From the top of the readme:

Issues with the output should be reported on the Nunjucks issue tracker.


Max/Min or principal strain rates

Hello, I noticed that in the output .nc file, there is no Max/min or principal strain rates and "azimuth angle", but in your program output diagram there is principal strain rates, just like the cross line in other diagrams, so how should I calculate the principal strain rate if I want to use my own plot script;
In addition, when input the config.txt, how should I input the parameter of "inc"? I find that the calculated results (the value range) vary greatly depending on the input value. Do you have any suggestions?

Hi, thanks for using the code!  you can calculate any derived strain quantity you need to from the 3 layers exx, exy, and eyy in the output netcdf.   For principal strain rates at a given point, we use the eigenvector function on the three components of the strain tensor.  You can write one into your plotting script or use the same one we use as a starting point (found here )
The "inc" parameter is meant to be the grid spacing of the desired grid in the x and y directions, in degrees, separated by a slash.  I usually use inc = 0.02/0.02 for my applications.  The size of the output grids will obviously decrease if you make the grid spacing larger for the same geographic domain.  Make sure that there's a space around the equals sign, same as for all parameters.  Does that help?


Problem with notifications on mac client Desktop

Hi,
I upgraded my mattermost server on 6.3.1 LTS version and my client mac to 5.02.
I have a problem with notifications and user's status.
Mattermost Desktop pass in offline when i change apps. And i have no notifications for Mattermost !!!!
And i click on Mattermost desktop app, the notifcations appears !!
It's a big problem beacause i don't see the urgent message
I test the mattermost desktop mac version 5.03-rc4 and the problem is already here !
I change the config on the server to increase the time before offline, and pass to 300 secondes at 10800 secondes.
But nothing, the problem is already here !!
Thanks for your help

@teger I'm not sure I fully understand the issue. Are you saying you don't get notifications on the Desktop App? Do you get them when using the browser?

Mattermost pass offline very fast and after, i don't have the notifications !
When i click on the app, the status come back online and the notifications appers ont the dock icon !
Impossible to control the status offline !
Thanks

Same issue here, since the server upgrade clients are going offline randomly. Predominantly Windows Clients, i updated to latest 5.0.4 Version but the problem persists.

@teger @mileagainst Does the issue reproduce in the web browser as well?

Hi,
yes in the browser, all is OK !
The problem is only on the desktop app (in my case, on mac !)
Thanks

Thanks @teger, created a ticket to investigate: https://mattermost.atlassian.net/browse/MM-42016

@teger I'm having trouble reproducing your issue. Can you step me through what you're seeing, possibly with some screenshots or a video? Thanks!

We have a team of 20 having the same issue.
The problem is as they say, the offline status is set automatically randomly.
We have to reload the app and set the status as active to get it.
Can't really give you any screenshot except the status icon but it won't give you any information.
We are all on mac and the version is the self hosted (managed by our hosting provider)

Facing same problem almost every day for a long time (2 years or so) with teammates (20+ persons). Not very critical for us, but annoying sometimes.
Now on Mattermost Desktop 5.22, Mac OS Ventura 13.1
Same behavior on other platforms (tested Ubuntu, Kubuntu, Debian, Windows, OSX) via desktop app. Not using Mattermost via browser, so don't know how it works there.
Server is Omnibus Gitlab selfhosted, deployed via docker image. Gitlab version 15.7.
Push server - default https://push-test.mattermost.com.
Desktop notification settings on desktop app - default "For mentions and direct messages" with Sound.
Today reached this problem during conversation with one teammate. Sent him some messages when he were in status "Away" (autoassigned due to app inactivity, probably). He saw my messages only after 2 hrs when unfolded his app from the "tray".
I face this problem in the same way every time. Open app from background and see there new messages im not notified with. On other platforms (windows and linux) at this moment notifications appears with standard way for OS (popup messages blinks).
Which additional information can I provide to help you with problem resolution?

@mmjurov Are you also seeing the set to Offline bug? I'm wondering if that's the root cause here.

I'm encountering being set to offline every once in a while.
I don't know what kind of info you need to look into it but I can try giving it to you when I know what to log, record, look for.

Nobody able to tell me what info is needed? Looks like this may only be fixed by a new major version by accident without anyone knowing what happened.

Closing as stale/might already be fixed.


[8.x] Fix Rule::in() to work with Enum values

Why
Validation rule In throws TypeError when we pass Enum cases from PHP 8.1:
Rule::in(SomeEnumObject::cases())
Error
TypeError: str_replace(): Argument #3 ($subject) must be of type array|string, \App\Enums\SomeEnumObject given in /vendor/laravel/framework/src/Illuminate/Validation/Rules/In.php:43

Just use the actual enum validation rule: https://laravel.com/docs/8.x/validation#rule-enum

@taylorotwell Enum validation rule is not 100% what I want to achieve. This validation check if value fits in full enum. In some cases, not all enum cases will be expected. For example, you can create public method inside enum, that return array of not all, but some cases.


Fixes for HTTP/3 CONNECT proxy

I'm adding HTTP/3 support to hprox, and find that CONNECT proxy is not (yet) supported. After some investigation and tracing, I find two blocking issues. This pull request contains fixes to make CONNECT proxy working with HTTP/3.
The client I'm using to test is the builtin QUIC Proxy implementation in Chrome 112 (it supports h3 protocol).
~There is still a minor issue that conduit pipes in my implementation is not closed even both client and server closed streams (the same is not happening with HTTP/2), I will try to figure it out why, and possibly open another pull request.~
EDIT: opened PR kazu-yamamoto/quic#54

Merged.
Thank you for your contributions!
I have released a new version.


NPM package is not up to date

I noticed the NPM package is out of sync with the repo, since it hasn't been updated in two years. This is a problem as recent improvements are very useful. Could it be done?
Thanks for this great widget!

Hey. Yes, this has been an intentional choice. I wanted to gather a bunch of fixes, features, and code improvements into one release.
I'm currently tweaking the code to reduce the library's size. Despite all the latest changes/fixes, i think i'll be able to shave 10-20% off :) I'm almost done, and it should be released in the next week.

I just published v0.10.0 to npm :tada:


ARROW-3940: [Python/Documentation] Add required packages to the development instruction

Codecov Report

Merging #3102 into master will increase coverage by 1.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3102      +/-   ##
==========================================
+ Coverage   87.04%   88.16%   +1.11%
==========================================
  Files         492      434      -58
  Lines       69104    65339    -3765
==========================================
- Hits        60153    57603    -2550
+ Misses       8850     7736    -1114
+ Partials      101        0     -101

Impacted Files
Coverage Δ

go/arrow/array/table.go

go/arrow/math/uint64_amd64.go

go/arrow/internal/testing/tools/bool.go

go/arrow/internal/bitutil/bitutil.go

go/arrow/memory/memory_avx2_amd64.go

go/arrow/array/null.go

go/arrow/datatype_nested.go

go/arrow/array/string.go

go/arrow/math/uint64_avx2_amd64.go

go/arrow/array/builder.go

... and 48 more

Continue to review full report at Codecov.

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


Question: Data Box Disk supported operating systems for clients

Are Windows Server 2019 and Windows Server 2022 not tested by Microsoft?

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

ID: de2798ae-fce2-db97-e60f-e4eb0ead61dc
Version Independent ID: 0eec4306-94fb-ec5a-32fd-618eafe753a1
Content: Microsoft Azure Data Box Disk system requirements
Content Source: articles/databox/data-box-disk-system-requirements.md
Service: databox
Sub-service: disk
GitHub Login: @alkohli
Microsoft Alias: alkohli

@tksh164
Thanks for your feedback! We will investigate and update as appropriate.

@tksh164
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly

@alkohli
Can you please check and add your comments on this doc update request as applicable.

@sipastak
could you please review it.

PMs confirmed Windows Server 2019 and Windows Server 2022 are not yet tested by Microsoft (but should most likely work). They are working to test these soon.
#please-close


v1.3.1--Fixes Issue #12

fix texture not fetched in iOS
fix animations not fetched in iOS
convert tuple string to list string when fetching animations and textures

@KamathVishak96 Good job, did you test on android after changes? maybe we need to separate the logic with platform checks.

@m-r-davari Yes, I tested this on Android and Web as well, with the sheen chair and the business man files. I am getting the list of Animations and Textures.

@KamathVishak96 Well done, thanks


fix(curriculum): external soundex links in CIP

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

clear task 106 in #40749

Hey @Sboonny,
I think you should retry this one. It does not match our standards.

What do you think? I don't know if it's ready for review, but I am happy with any feedback


Added MonoRequirement for using installations from official Mono packages.

@alexreg Can you detail which of our current Mono packages in homebrew/core you've tested this with? Thanks!

@MikeMcQuaid Sure. I tested on the cake formula already. Would you like me to test on some others?

Yes, please. As many as possible. Note that this will result in these formulae being essentially depends_on "mono" when poured from a bottle.

Sure, will do. And when you say "test", I suppose you mean that I should verify they install correctly, but also that brew test works on them?
I could also submit a PR for hombrew-core with their updated formulas, if you like.

Verify they install correctly, brew test works with them, that when built from source with the Homebrew Mono they still work at runtime with the non-Homebrew Mono and that they seem to not have any obvious issues.

@alexreg Additionally can you explain why you need this and why this is useful to you?

It's useful because I like to use the official installation of Mono, included with Xamarin (well, Visual Studio for Mac these days). I think many others will too.
Okay, tested all the formulae that depend on mono, and they all seem to install and test correctly. :-) Well, one slight exception: the gitversion test fails, but it was already doing that for me before these changes.
fatal: unable to auto-detect email address (got '_homebrew@Alex-MacBookPro.(none)')

Is that all good with you?

It's useful because I like to use the official installation of Mono, included with Xamarin (well, Visual Studio for Mac these days). I think many others will too.

That explains what you want to do but not why. Can you elaborate on why specifically you want to use it at runtime for Homebrew applications?

It's what and a why. The only alternative is to install a Homebrew version of Mono too now, which is far from ideal.

Sorry, there's still no "why" here except "because @alexreg wants to". So it's saving disk space/saving download time or something else?

Yes, that's right. I thought that was implicit, sorry. It's saving effective duplication of a dependency (hence downloading and installation time, not to mention space).

Also, having two versions of Mono on one's system can mess things up in terms of resolving paths...

Also, having two versions of Mono on one's system can mess things up in terms of resolving paths...

Can you elaborate on this?

Also, having two versions of Mono on one's system can mess things up in terms of resolving paths...
Can you elaborate on this?

The resolution for DLLs (libraries), with regards to the .NET Framework (core libraries) can get muddled, as far as I know.  It can be done, but care needs to be taken, as hinted by this page: http://www.mono-project.com/docs/compiling-mono/parallel-mono-environments/
Regardless, I think that not having two copies installed is a good enough reason, especially given the size of a Mono installation. :)

Doesn't Homebrew basically already provide this in core at least by the regular practice of mono dependencies being semi-consistently => :recommended. Seems like that could just be made wholly consistent rather than adding yet another special dependency.

Unless there's significant use of things detecting the path to mono at buildtime and hardcoding that as a hashbang, but the way I've seen people talk about the => :recommended deps suggests that's uncommon?

The resolution for DLLs (libraries), with regards to the .NET Framework (core libraries) can get muddled, as far as I know. It can be done, but care needs to be taken, as hinted by this page: http://www.mono-project.com/docs/compiling-mono/parallel-mono-environments/

This doesn't seem to be a problem for you personally, though, so I'm going to say this is speculative.

Regardless, I think that not having two copies installed is a good enough reason, especially given the size of a Mono installation. :)

I'm not sure, I don't think that's a good reason or precedent, personally. Will leave this open for a bit for others to think about this.

Okay, @MikeMcQuaid.
Another (small) benefit I thought of, is verifying the version of Mono installed is sufficient, when installing Homebrew formulae depending on Mono. Also, I don't like the :optional/:recommended approach, since that's not what it's meant for. Very hacky.

Passing on this, sorry.

Any particular reason?

No-one else has chimed in in support of this, it wouldn't see widespread usage and there's no real disadvantage beyond disk-space/one-time bandwidth usage.

I think just no-one else has seen it, to be honest! I doubt many people trawl through issues just to give thumbs up/down... but okay. I see disk space as a big point in its favour, as well as other minor ones.


⚠ Samsung has degraded performance

In b48c69f, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 10876 ms

Resolved: Samsung performance has improved in 35b2108.


HDDS-10874. Freon tool DNRPCLoadGenerator should not cache client objects.

What changes were proposed in this pull request?
HDDS-10874. Freon tool DNRPCLoadGenerator should not cache client objects.
The original XceiverClientSpi API always caches client objects to a specific pipeline. But in this freon tool we wanted to have multiple clients to parallelize throughput.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10874
How was this patch tested?
Ran on a real cluster. Other than that it leverages the existing tests.
After this change:
ozone freon dne --clients=32 --container-id=1 -t 32 -n 1000000 --ratis --read-only
rpc-payload
mean rate = 38794.07 calls/second
ozone freon dne --clients=1 --container-id=1 -t 32 -n 1000000 --ratis --read-only
count = 1000000
mean rate = 9987.42 calls/second
But number of clients has no impact for Ratis in write mode and GRPC.

@jojochuang why not make this the default behavior for reads on client side? Maybe we can change the logic on the client side to have a pool of clients per container, I guess the benefit for the client cache is to avoid the setup cost when there is sequential access to the same container but when there is parallel access to the same container we see a performance hit. Having a pool of clients per container and no upper bound on the number of clients across containers might be right way forward. We might still need a TTL or LRU for the clients.

The original XceiverClientSpi API always caches client objects to a specific pipeline. But in this freon tool we wanted to have multiple clients to parallelize throughput.

Distinct clients can be acquired simply by providing pipeline with unique ID.

@jojochuang why not make this the default behavior for reads on client side?

@kerneltime I want to take a different angle. -- I wonder where the overhead is coming from in the first place.
In the case of Ratis, XceiverClientRatis itself does not appear to have much synchronization overhead. So I did a little bit of digging. And I think the limiting factor can be this config in each RaftClient:
raft.client.async.outstanding-requests.max

by default each RaftClient allows 100 outstanding requests. As a result only 100 parallel RaftClient#send can be in-flight at one point:
https://github.com/apache/ratis/blob/release-3.0.1/ratis-client/src/main/java/org/apache/ratis/client/impl/OrderedAsync.java#L160-L183
We should try setting raft.client.async.outstanding-requests.max to 100000 and see what happens. cc @jojochuang @szetszwo

And btw for grpc we also have a similar semaphore config in XceiverClientGrpc that limits parallelization for each XceiverClient instance:
https://github.com/apache/ozone/blob/9b248a0673fb7560f6ec4b04b9b366b549743765/hadoop-hdds/client/src/main/java/org/apache/hadoop/hdds/scm/XceiverClientGrpc.java#L126-L127
and it is set to a default of 32:
https://github.com/apache/ozone/blob/68393452332a2d881c34eb2c21feee4b1a8e58e9/hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/ratis/conf/RatisClientConfig.java#L51-L54

Worth point out that the Echo request is implemented as a blocking call and the number of threads limits number of concurrent requests. And that is consistent across all ContainerProtocolCalls APIs.
For GRPC client, It made no difference increasing hdds.ratis.raft.client.async.outstanding-requests.max. They were all blocked waiting for response from DN.

close in favor of #6945 7044


Add unsafe methods on Maybe & Result

Add "unsafe" methods to retrieve a monad value, throwing an exception if the monad is not in the expected state.
This is a provided workaround for people preferring exceptions instead of using transformation mechanisms (Match, Map, Bind)

@SMadani Indeed, it is on purpose. . It's a workaround to make everyone happy. As we comply with referential transparency (with no exceptions overall), I'd like to make it evident that it is not the "normal" or "expected" way to get the value, and that it does not behave like other methods.


chore: fix config import and refactor paths

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


Fix Rule widget docs

Fix Rule widget title alignment

Merged! Thank you for your contribution. Much appreciated! 👍


remove 3.3.1 from 3.3.0 shim

Is your feature request related to a problem? Please describe.
https://github.com/NVIDIA/spark-rapids/pull/5693#pullrequestreview-990466460 temporarily added 3.3.1 to 3.3.0 while they are working on the 3.3.0 release. Before we ship 22.06 we need to remove that.

spark 3.3.0 is out, we will need to update shim to depends on spark 330


RVEA not reaching specified number of evaluations

RVEA does not complete the specified number of evaluations set by the termination condition.
I've run RVEA on several problems, both those implemented in pymoo and those implemented elsewhere, and never is the algorithm able to achieve the set number of evaluations. Mostly, it finishes in max_evals - pop_size evaluations, however, often it is less, sometimes significantly so. I'm assuming this is a bug and not a feature, as I cannot find mention of some early stopping mechanism in the paper.
As an example of this, I ran RVEA with 100 reference points (Riesz s-energy method) on a large set of 2 and 3 objective problems. The minimize function was used and the termination criteria was 10000 evaluations. Below are the results from individual runs on the CTP problems:
Problem | Total Evaluations
CTP1 | 8246
CTP2 | 9061
CTP3 | 9172
CTP4 | 9101
CTP5 | 9052
CTP6 | 9684
CTP7 | 9631
CTP8 | 9734

One part of the issue is likely due to the setup method that converts the evaluations termination to a generations termination. Here, pop_size is negated from the maximum number of evaluations. In the example above, this results in maximum evaluations being set to 99 as opposed to 100.
    def _setup(self, problem, **kwargs):

        # if maximum functions termination convert it to generations
        if isinstance(self.termination, MaximumFunctionCallTermination):
            n_gen = np.ceil((self.termination.n_max_evals - self.pop_size) / self.n_offsprings)
            self.termination = MaximumGenerationTermination(n_gen)

        # check whether the n_gen termination is used - otherwise this algorithm can be not run
        if not isinstance(self.termination, MaximumGenerationTermination):
            raise Exception("Please use the n_gen or n_eval as a termination criterion to run RVEA!")

The other part may actually be a feature of the survival mechanism. The algorithm's evaluator is recording the correct number of evaluations, despite there being less solutions in the population.

RVEA was proposed as a unconstrained algorithm, thus I don't think it makes sense to test it on the CTP problems.
Originally, the paper has only proposed to have number of generations as termination criterion. However, we have added this fix to provide number of function evaluations as well.

Have you noticed the algorithm terminating early by fixing the number of generations as well?

When I fix the number of generations, it completes these correctly and the algorithm's evaluator records the correct number of evaluations. However, when I try to 'save_history' and check for the number of solutions saved, there are less. The same occurs when I record solutions using a callback.
I'm now testing on the WFG, DTLZ and ZDT suites and I get the same outcomes.

I am not sure if I can follow.
However, when I 'save_history' and check for the number of solutions saved, there are less.

Not all evaluations are stored in the populatio. It might be an offspring is not improving the current population so it will not be contributing. Or are you actually trying to count all offsprings in each iteration?

I meant that the res.history object does not store all evaluated solutions. It was my understanding it should.
Also, just to note, RVEA is listed as handling constraints on this page. Perhaps, it shouldn't?

Thanks for calling this out! I have updated the table. See my commit above.


config.production.json portal disabled entirely by setting "url": false is invalid

Issue Summary
config.production.json portal disabled entirely by setting "url": false is invalid
Steps to Reproduce
1.config.production.json portal set url to false
2.ghost restart
3.

Ghost Version
5.62.0
Node.js Version
16.19.1
How did you install Ghost?
GHOST CLI & UBUNTU
Database type
MySQL 5.7
Browser & OS version
No response
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

The correct way to disable Portal is to disable Members via the settings, or you can hide the Portal icon 🙂

The correct way to disable Portal is to disable Members via the settings, or you can hide the Portal icon 🙂

tks. Problem fixed.


Poller is exiting with error "connection error => no valid version tuple found"

Describe the bug
For few 7mode systems, harvest pollers are exiting with below errors.
{"level":"warn","Poller":"netapp1","caller":"command-line-arguments/poller.go:530","time":"2021-08-02T21:57:30-07:00","message":"init collector-object (ZapiPerf:SystemNode): connection error => no valid version tuple found"}
{"level":"warn","Poller":"netapp1","caller":"command-line-arguments/poller.go:532","time":"2021-08-02T21:57:30-07:00","message":"aborting collector (ZapiPerf)"}
{"level":"warn","Poller":"netapp1","caller":"command-line-arguments/poller.go:255","time":"2021-08-02T21:57:30-07:00","message":"no collectors initialized, stopping"}
{"level":"info","Poller":"netapp1","caller":"command-line-arguments/poller.go:419","time":"2021-08-02T21:57:30-07:00","message":"cleaning up and stopping [pid=14953]"}
Environment
Provide accurate information about the environment to help us reproduce the issue.

Harvest version: harvest version 21.05.3-2 (commit b482aff) (build date 2021-06-28T21:08:05+0530) linux/amd64
Command line arguments used: harvest start netapp1
OS: CentOS Linux release 7.9.2009 (Core)
Install method: rpm
ONTAP Version: 8.2P4 7mode
Other:

To Reproduce
Not sure how to reproduce
Expected behavior
Expect pollers to collect the metrics
Actual behavior
Poller exited with error
Possible solution, workaround, fix
NA
Additional context
NA

hi @madhusudhanarya "No valid version tuple found" means the version information returned from the filer doesn't match what we expect. Can you follow the troubleshooting steps listed here and reply with the output?

@cgrinds : please find the output from the cmd.
[root@harvest-01 harvest]# ./bin/harvest zapi -p netapp1 show system
no valid version tuple found
To verify API access, i tried to connect to the filer using NetApp ZExplore and found SSL errors. Above issue might be because of this.

thanks @madhusudhanarya - interesting, ./bin/harvest zapi -p <poller> show system typically works with 7-mode systems. The system-get-version ZAPI is sent and the result parsed.
Can you login to the admin console on the cluster, run version, and paste the results? I'm guessing some versions of 7-mode don't conform to the pattern we're attempting to parse. Should be straightforward to address.

Here is the result of version command.
netapp1> version
NetApp Release 8.2P4 7-Mode: Tue Oct  1 11:24:04 PDT 2013

Thanks @madhusudhanarya
I've improved the 7-mode version parsing, reported the version info in the error message, and added better unit tests for this in #381
If interested, you can build from source and give it a try. Otherwise we'll be publishing another build later this month and it will be included there.

I built from the source. While building the RPM, encountered below error.
[root@test-vm harvest]# ./package.sh rpm x86_64 21.05.4 1
-- build locally
building [harvest_21.05.4-x86_64.rpm] on local system
copying source files
building binaries
_  _                     _     ___   __
| || |__ _ _ ___ _____ | |  |  ) /
| __ / ` | '\ V / -|-<  |  / / | () |
|||_,||  _/_//_| /()_/
Cleaning harvest files
checking Harvest dependencies
Running gofmt
go fmt ./...
Building harvest
Building poller
Building daemonize
Building zapi tool
Building grafana tool
Building rest tool
building binary tarball
-------------------------------------------truncated long output-----------------------------------
harvest/vendor/golang.org/x/net/PATENTS
harvest/vendor/golang.org/x/net/AUTHORS
harvest/vendor/golang.org/x/net/LICENSE
harvest/vendor/modules.txt

cd /root/rpmbuild/BUILDROOT/harvest-21.05.4-1.x86_64/opt/harvest
echo ' --> installing harvest...'
--> installing harvest...
cd /root/rpmbuild/BUILDROOT/harvest-21.05.4-1.x86_64/opt/harvest
mkdir -p /root/rpmbuild/BUILDROOT/harvest-21.05.4-1.x86_64/var/log/harvest
/usr/lib/rpm/check-buildroot
/usr/lib/rpm/redhat/brp-compress
/usr/lib/rpm/redhat/brp-strip /usr/bin/strip
/usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
/usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
/usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
Compiling /root/rpmbuild/BUILDROOT/harvest-21.05.4-1.x86_64/opt/harvest/cmd/exporters/prometheus/validator.py ...
File "/opt/harvest/cmd/exporters/prometheus/validator.py", line 164
def get_batch_metrics(addr: str, port: int) -> str:
^
SyntaxError: invalid syntax

error: Bad exit status from /var/tmp/rpm-tmp.68lf7n (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.68lf7n (%install)
rpmbuild failed, aborting
run build script

@madhusudhanarya, thanks for posting this message. This probably happens because your rpm-build uses Python2 to compile the python script (which is a non-essential utility for testing). I'll open a PR to fix this.

Btw, what Chris meant was to compile harvest directly on your machine, without RPM, check his link. You should have no issues in that case.

I want to build RPM as i need to install harvest on multiple systems where we are seeing this issue.

While @vgratian fixes #386, can you apply this change locally which should let you build rpms?

#401 is checked in now. That means you should be able to pull the latest and build RPMs. Let us know if you have problems with building. Hopefully that works and we can turn our attention to the selection problem.


Add package bundle to eksa bundle

/hold

Closes: https://github.com/aws/eks-anywhere-packages/issues/798

Closes: https://github.com/aws/eks-anywhere-packages/issues/798

/approve

/test eks-anywhere-release-tooling-test-presubmit


TabNine sometimes autofils the word and prevents me deleting the letters of the word in edit mode

here in this gif when i try to write exists after exi tabnine just inserts e and wont let me delete it. this is really annoying also for some reason it inserted o after exist in the gif .
Is there any way to disable autofil in tabnine and allow only to fill using  or  ?

What is your environment?

osx and tmux @Shougo


Add example for datasource with multiple dynamic tables and legend

There are a few different fixes here (each in separate commits):

Log the values object to allow simpler debugging.  See 4a85611 and  98f0ee7
Report error when the request data json for an attribute is an array instead of an object.  This was hiding an error that the mapfish client had.
Add documentation for DataSourceProcessor
Add an full/mature example of using DataSourceProcessor with TableProcessor when TableProcessor is configured as dynamic.

Looks like I have to generate the image on linux and add so that the similarity is close enough.  it is hard with these big images.

Build is fixed.  This is ready for a review now.

Note:  I had to merge in trunk because the default table template had changed and made all of the expected images obsolete.  That is why the commit list contains a commit which is the merge.

Thanks, this is looking good!


Markdown editor sometimes not save the data

Package
filament/forms
Package Version
v3.2.92
Laravel Version
v11.11.1
Livewire Version
v3.5.1
PHP Version
PHP 8.3.8
Problem description
Hi,
https://github.com/filamentphp/filament/assets/120738508/47c6f253-8648-4f35-8360-124240126748
When you update a resource with the Markdown Editor, sometimes the new data is not saved.
I tried to find the problem before send the bug report, for trying to elucidate the reason why it occurs. But not was possible.
I only detected, that when the resource is not saved, the ajax requests, not have the "updated" field filled about the current form state. Is like, it dont detect the changes in the form state.
I let you a video about the bug, and i let you a demo repo, is a very basic filament panel, so, is not a bug in a complex system, it occurs even in an panel with a one resource, one model and two fields in a model.
Thank you for all.
Expected behavior
Save the data all the times.
Steps to reproduce
Enter o reload resource page, and try to save multiple times the form, sometimes is saved, other times not.
Reproduction repository (issue will be closed if this is not valid)
https://github.com/rubenrcdev/filament-editor-bug
Relevant log output
No response

Donate 💰 to fund this issue

You can donate funding to this issue. We receive the money once the issue is completed & confirmed by you.
100% of the funding will be distributed between the Filament core team to run all aspects of the project.
Thank you in advance for helping us make maintenance sustainable!

I think is related with the issue #12858

I did more testing to find what happens in the markdown editor.
I modified public/js/filament/forms/components/markdown-editor.js file, to include a console.log as can see in the next screenshoot:

So, when i write something, the watch state takes some time to refresh data, it takes about 1 second to refresh, if i save before that happens, the data is not updated.
The bug is not from filament, is about how works livewire.
So, i close the issue.


Navigate > Class opens the right file but doesn't actually take me to the right line of code

When I use Navigate > Class to go to a declaration, we open the right file, but don't move the caret to the location of the declaration.

Works fine for me. The default behavior for any declaration (not just ours), is to navigate to the name the first time, but if you move the caret in the file, then close it, then open the declaration again, it will navigate to the last location, not the declaration name. Is this what you are seeing?

OK, sorry, you're right. I find this a very suboptimal behavior, but, fine, if that's what IntelliJ does, I can live with it. Sorry for the noise.

I agree this might not be a good behavior for external files, but for project files it can be handy, it just navigates where you left, in case you have something to finish at the same location.

Well, I would expect that behavior from ⌘E or ⇧⌘E, but not from ⌘O. I guess it's OK for Java, where you don't usually have more than one class in a file, but I wouldn't say it's perfect for Ceylon, where ⌘O can now take you to a totally different toplevel declaration!


test: Unquarantine working FQDN test

The first commit unquarantines an FQDN test that appears to have been quarantined by mistake (?).  See commits for details.

/test-vagrant

The LB changes are just removing dead code so I think we can skip that review. Maciej review and tests are passing so marking ready to merge.


migrate to neo/falcon hybrid

currently due to supply shortage, there will need to be migration from dual falcon 500s to one NEO motor and a falcon 500
the steering motor will be the NEO due to the lesser power it can drive, while the driving motor will be the falcon 500

[ ] convert physical modules
[ ] simulate NEOs
[ ] implement new NEOs in CTRESwerveModule
[ ] test functional with the physical robot

no longer being used


gym rendering

render=True is confusing, should be that render_mode="human" triggers the window

Hi @christopherhesse,
I'm probably missing something but it's not clear to me how to use render=True from the README.
When I do:
env = gym.make("procgen:procgen-coinrun-v0", start_level=0, num_levels=1, render=True)
I get:
Traceback (most recent call last):
...
  File "~/mtrazzi/procgen/lib/python3.7/site-packages/procgen/gym_registration.py", line 9, in make_env
    env = ProcgenGym3Env(num=1, num_threads=0, **kwargs)
  File "~/mtrazzi/procgen/lib/python3.7/site-packages/procgen/env.py", line 246, in __init__
    super().__init__(num, env_name, options, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'render_human'

And when I do
env = ProcgenGym3Env(num=1, env_name="coinrun", start_level=0, num_levels=1, render=True)
I get:
Traceback (most recent call last):
...
  File "~/mtrazzi/procgen/lib/python3.7/site-packages/procgen/env.py", line 246, in __init__
  super().__init__(num, env_name, options, **kwargs)
  TypeError: __init__() got an unexpected keyword argument 'render'

Would be great to have minimal examples on how to render things in the README.
On a related note, when trying to render with mode=human or mode=rgb_array I don't get anything (maybe because of early reset, as mentioned in the README), and this is still true when using a wrapper from the NeurIPS procgen competion, in particular when running rollouts.py with --video-dir ./outputs (which calls the render() method multiple times inside a Monitor, but then doesn't seem to save any video). Any ideas on why this is hapenning?
Thanks!

@mtrazzi what's the output of pip show procgen and pip show gym3?

(Note: I changed computer but I get the same tracebacks.)
Version: 0.10.1
Summary: Procedurally Generated Game-Like RL Environments
Home-page: https://github.com/openai/procgen
Author: OpenAI
Author-email: None
License: UNKNOWN
Location: /home/a/procgen/lib/python3.6/site-packages
Requires: gym3, gym, filelock, numpy
Required-by:

Name: gym3
Version: 0.3.2
Summary: Vectorized Reinforcement Learning Environment Interface
Home-page: https://github.com/openai/gym3
Author: OpenAI
Author-email: None
License: UNKNOWN
Location: /home/a/procgen/lib/python3.6/site-packages
Requires: imageio-ffmpeg, moderngl, glfw, numpy, imageio, cffi
Required-by: procgen

After updating procgen to 0.10.3 I still get the same Traceback for the ProcgenGym3Env command, but the gym.make command seems to run (and render) something!
Also, I got an answer for the NeurIPS competition, and apparently adding a render_mode="rgb_array" in the config should work.

0.10.3 did contain a fix for that error.  The docs are a bit ambiguous and partially refer to the previous argument, I'll fix them.
In the future to avoid this sort of stuff, the gym environment will take render_mode="rgb_array" or render_mode="human" and the gym3 will accept only render_mode="rgb_array"

The docs are updated, 0.10.4 will likely contain the fix I mentioned, and I'll leave render=True there for backwards compatibility.

Hi, thanks for updating the docs.
It seems that passing render_mode='rgb_array' works fine and sets configs correctly.
A slightly modified of the ViewerWrapper demo (cf. PR) render episodes correctly.
Now the question is how to get a video from rollouts, and it seems that gym3's VideoRecorderWrapper should do the trick.
When I replace the identity env in video_recorder_test.py by
env = gym.make("procgen:procgen-coinrun-v0", start_level=0, num_levels=1, render_mode='rgb_array')
I get
Traceback:
...
  super().__init__(ob_space or env.ob_space, ac_space or env.ac_space, env.num)
AttributeError: 'ToGymEnv' object has no attribute 'ob_space'

and when I replace it with env = procgen.ProcgenGym3Env(num=1, env_name="coinrun", render_mode='rgb_array')
I get
  File "script.py", line 54, in test_recorder
    env.act(types_np.zeros(env.ac_space, bshape=(env.num,)))
  File "~/mtrazzi/procgen/lib/python3.7/site-packages/gym3/video_recorder.py", line 101, in act
    self._append_observation()
  File "~/mtrazzi/procgen/lib/python3.7/site-packages/gym3/video_recorder.py", line 77, in _append_observation
    img = ob[self._env_index]
KeyError: 0

Simply using a Monitor doesn't seem to work for gym3/procgen environments so having a demo for video seems useful.
Any ideas on what I'm missing?
Thanks

Update: problem is solved, code for a video of coinrun here.

That code seems fine, VideoRecorderWrapper will also work, but you have to set info_key="rgb".  The error is because by default it expects that the environment returns images in a numpy array.  A better error message and/or fallback to "rgb" there would be an improvement.

Here is an example script for future reference:
"""
Example random agent script using the gym3 API to demonstrate that procgen works
"""

from gym3 import types_np
from gym3 import VideoRecorderWrapper
from procgen import ProcgenGym3Env
env = ProcgenGym3Env(num=1, env_name="coinrun", render_mode="rgb_array")
env = VideoRecorderWrapper(env=env, directory=".", info_key="rgb")
step = 0
while True:
    env.act(types_np.sample(env.ac_space, bshape=(env.num,)))
    rew, obs, first = env.observe()
    print(f"step {step} reward {rew} first {first}")
    if step > 0 and first:
        break
    step += 1


feat: Apply different LoRA dynamically

Feature Description
Can change LoRA  dynamically after loading LLaMa model.
The Solution
See llama_model_apply_lora_from_file() function in llama.cpp.
https://github.com/ggerganov/llama.cpp/blob/e9c13ff78114af6fc6a4f27cc8dcdda0f3d389fb/llama.h#L353C1-L359C1
Considered Alternatives
None.
Additional Context
No response
Related Features to This Feature Request

[ ] Metal support
[ ] CUDA support
[ ] Grammar

Are you willing to resolve this issue by submitting a Pull Request?
No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.

@snowyu Can you please provide an example of a proposed usage with llama.cpp showing how you would like to use it?
Please provide links to files that you use and what you are generally trying to achieve.
I want to keep the API of this library relatively high-level while still offering advanced capabilities, so I wouldn't necessarily want to expose the llama_model_apply_lora_from_file function as-is, and instead understand your use case better to try to figure out what's the best way to provide support for this.

Just curious if there has been any progress on this?
I think it would be nice to be able to specify a LoRa adapter in the LlamaModelOptions or the be able to call a method on LlamaModel.
If that makes sense, I'd be willing to start looking into it.

@vlamanna The beta of version 3 is now mature enough, so I've added support for loading a LoRA adapter as part of loading a model (#217).
@snowyu Changing a LoRA on a model at runtime is not possible at the moment, as there's no way to unload an adapter after it has been applied to a model; every call to llama_model_apply_lora_from_file loads another adapter onto the current model state.
This feature will be available in the next beta version that I'll release soon.

@snowyu Changing a LoRA on a model at runtime is not possible at the moment, as there's no way to unload an adapter after it has been applied to a model; every call to llama_model_apply_lora_from_file loads another adapter onto the current model state.

@giladgd It can not be done on the lowlevel API. But It could be ok on high level API, like this:
// pseudocode
class LlamaModel {

loadLoRAs(loraFiles, scale, threads, baseModelPath?) {
  let needDeinit = false
  // check loaded loraModels
  for (let i=0; i< this.loraModels.length; i++) {
   const loraModel = this.loraModels[i]
    const ix = loraFiles.indexOf(loraModel.file)
    if (ix === -1) {needDeinit=true;break}
    loraFiles.splice(ix, 1)
  }
  //free model if already load other lora
  if (needDeinit) {
    // deinit and load base model again
    this.reloadModel()
  }
  for (const loraFile of loraFiles) {
    const model = _loadLoRA(loraFile, scale, threads, baseModelPath)
    if (model) this.loraModels.push(model)
  }
}

@snowyu It can be done with the high-level API that I've added.
Providing an API to modify the current loaded model via changing the LoRAs applied onto it on runtime is not preferable since all dependent states (such as contexts) should also be reloaded when switching LoRAs, so since there's no performance benefit to doing that (as unloading a LoRA is not possible to do at low level) then exposing such an API is not worth it as it would only make the usage of this library more complicated.

@giladgd If you only consider the creation of APIs from the perspective of performance, this is indeed the case. But from the perspective of ease of use, it is worth exploring.
Let me talk about my usage scenario, a simple intelligent agent script engine, they can call each other, each agent may use a different LLM. LLM reloading is commonplace. My current pain is that I have to These LLMs are managed in the agent script engine:

Determine LLM’s caching strategy based on memory size
Determine whether to switch LLM or run multiple LLMs simultaneously (based on maximum VRAM and RAM optimal parameters)
Managing and maintaining recommended configurations of LLM

Although these should be the responsibility of the LLM engine and not the agent script engine.

@snowyu We have plans to make the memory management transparent, so you can focus on what you'd like to do with models, and node-llama-cpp will offload and reload things back to memory as needed so you can achieve everything you'd like to do without managing any memory at all, and in the most performant way possible with the current hardware.
Over the past few months, I've laid the infrastructure for building such a mechanism, but there's still work to do to achieve this.
This feature will be released as a non-breaking feature after the version 3 stable release (that's coming very soon), due to it taking much longer than I initially anticipated.
Perhaps you've noticed, for example, that you don't have to specify gpuLayers when loading a model and contextSize when creating a context anymore, as node-llama-cpp measures the current hardware and estimates how much resources things will consume to find the optimal balance between many parameters, while maximizing the performance of each one up to the limits of the hardware.
This is part of the effort to achieve seamless memory management and default zero-config.
Allowing to modify a model state at runtime on the library level will make using this library more complicated (due to all of the hassle it incurs to keep things working or the performance tradeoffs it embodies), and I think is a lacking solution to the memory management hassle that I work on solving from its root.

@giladgd

We have plans to make the memory management transparent, so you can focus on what you'd like to do with models, and node-llama-cpp will offload and reload things back to memory as needed so you can achieve everything you'd like to do without managing any memory at all, and in the most performant way possible with the current hardware.

It's great.looking forward to it.

Perhaps you've noticed, for example, that you don't have to specify gpuLayers when loading a model and contextSize when creating a context anymore.

Yes. I have. Do you think about adding the estimate of memory for mmprojector model?

Allowing to modify a model state at runtime on the library level will make using this library more complicated (due to all of the hassle it incurs to keep things working or the performance tradeoffs it embodies), and I think is a lacking solution to the memory management hassle that I work on solving from its root.

Totally agree.

@snowyu

Yes. I have. Do you think about adding the estimate of memory for mmprojector model?

I don't know what model you are referring to.
I reverse-engineered llama.cpp to figure out how to estimate resource requirements using only the metadata of a model file without actually loading it; it isn't perfect, but the estimation is pretty close to the actual usage with many models I've tested this on.
To find out how accurate the estimation is for a given model, you can run this command:
npx node-llama-cpp@beta inspect measure <model path>

If you notice that the estimation is way off for some model and want to fix it, you can look at the llama.cpp codebase to figure out the differences in how memory is allocated for this model, and open a PR on node-llama-cpp to update the estimation algorithms on GgufInsights.

@giladgd Sorry, I've been busy with my project lately. mmprojector is from Multimodal LLM, maybe you haven't used the llava part yet.
You may be interested in the Programmable Prompt Engine project I'm working on.
I hope to add node-llama-cpp as the default provider in the near future, but for now, I don’t see a good API entry point to start. I need a simple API:
// come from https://github.com/isdk/ai-tool.js/blob/main/src/utils/chat.ts
export const AITextGenerationFinishReasons = [
  'stop',           // model generated stop sequence
  'length',         // model generated maximum number of tokens
  'content-filter', // content filter violation stopped the model
  'tool-calls',     // model triggered tool calls
  'abort',          // aborted by user or timeout for stream
  'error',          // model stopped because of an error
  'other', null,    // model stopped for other reasons
] as const
export type AITextGenerationFinishReason = typeof AITextGenerationFinishReasons[number]
export interface AIResult<TValue = any, TOptions = any> {
  /**
   * The generated value.
   */
  content?: TValue;

  /**
   * The reason why the generation stopped.
   */
  finishReason?: AITextGenerationFinishReason;
  options?: TOptions
  /**
   * for stream mode
   */
  stop?: boolean
  taskId?: AsyncTaskId; // for stream chunk
}
// https://github.com/isdk/ai-tool-llm.js/blob/main/src/llm-settings.ts
export enum AIModelType {
  chat,  // text to text
  vision,  // image to text
  stt,  // audio to text
  drawing,  // text to image
  tts,  // text to audio
  embedding,
  infill,
}

// fake API
class AIModel {
  llamaLoadModelOptions: LlamaLoadModelOptions
  supports: AIModelType|AIModelType[]
  options: LlamaModelOptions // default options
  static async loadModel(filename: string, options?: {aborter?: AbortController, onLoadProgress, ...} & LlamaLoadModelOptions): Promis<AIModel>;
  async completion(prompt: string, options?: {stream?: boolean, aborter?: AbortController,...} & LlamaModelOptions): Promise<AIResult|ReadStream<AIResult>>
  fillInMiddle...
  tokenize...
  detokenize...
}


fix(fsxaremoteapi): uri encoding of user input

We extended the scope of this ticket and added integration tests with it


Update lstm_genre_classifier_pytorch.py

fix the hidden layer initialize problem and add continue train feature between batches

Looks great. Thank you!


[BUG]: drizzle build file has accidential side effect import statement

What version of drizzle-orm are you using?
0.28.6
What version of drizzle-kit are you using?
0.19.13
Describe the Bug
build output in file libsql/index.js has import "@libsql/client" it make module bundler think that was side effect import, so the module bundler will copy all content including @libsql/client/sqlite3, that code will not work on some platform like cf worker, because @libsql/client/sqlite3 is not designed for all platform

Expected behavior
no side effect import
Environment & setup
No response

I dont know how this side effect import was emitted, maybe because the source is import { type X } from "@libsql/client"insteadofimport type { X } from "@libsql/client"`

yes, you are correct, it's a bad type import.

sorry, I'm only look at issues and not at pull request, it must be resolved with #1309


Doorbell not functioning

I use a Vivint security system and it exposes the HTTP automation port for both of my doorbell cameras. I've ensured that I've enabled the doorbell functionality in CameraUI and have entered the correct HTTP port for both doorbells.
Whenever I ring the doorbell, however, I get the following error:
Back Doorbell: {"error":false,"message":"Handling through extern controller.."}
The doorbell notification never comes through on my Homepods. Any help with regard to things to try would be greatly appreciated!

Thanks for the quick reply, @seydx! I turned off streaming on the cameras and turned it back on again, and did the same with the doorbell notifications-- still no doorbell notifications coming through on Homekit.
I turned on debug mode in CameraUI and went to the console to see what happened when I rang the doorbell-- I didn't see anything. Does that mean that Camera UI isn't getting any signal on the http port I specified? (8075)

@ripple7511

Whenever I ring the doorbell, however, I get the following error:
Back Doorbell: {"error":false,"message":"Handling through extern controller.."}

Thats not an error, it means the incoming motion message will be handled through extern controller (hsv)
And enabled doorbell notification also in Apple Home ?
Select camera im Apple Home > Notifications > Scroll Down > Doorbell

@ripple7511 can you share your config for the doorbell?  How did you find the http automation port for the Vivint doorbell?


Remove call to before in Resource::can

See https://github.com/filamentphp/filament/commit/e3ea76431fc697e15b4bfc48516fdb941a3b6a98

Can you also fix this in the RelationManager class please?

Can you also fix this in the RelationManager class please?

Done

Thanks


🚨 Array .map() type too wide

🔎 Search Terms
TypeScript Playground Link
🕗 Version & Regression Information
Unknown
⏯ Playground Link
https://www.typescriptlang.org/play/?#code/MYewdgzgLgBACgQQJICUDKMC8MDaAoGQ3AcgENiAaGABgF0KCidiAjSmARnscOeHYBM3WjFIQYoSFADcePJOgwAwgHkAckoQAVAKJrtOgCJZ4ydADoAtqQAOACgBupADYBXAKZYAfDAAGAEgBvJzd3HDoAXwBaIJCPHC4I31FxBSgASlk8KABPG08lcGBSKHcwEvcAExM7XPyQADNldU1dfV1DdJwwV0sWdwAnWlkgA
💻 Code
const PAIRS = [
    ['a', 0],
    ['b', 1],
    ['c', 2],
] as const;

const CONCATENATED = PAIRS.map(value => `${value[0]}-${value[1]}` as const);

type Concatenated = (typeof CONCATENATED)[number];

🙁 Actual behavior
If you hover over Concatenated, you can see that its type is type Concatenated = "a-0" | "a-2" | "a-1" | "b-0" | "b-2" | "b-1" | "c-0" | "c-2" | "c-1".
🙂 Expected behavior
The expected type should instead be type Concatenated = "a-0" | "b-1" | "c-2".
Additional information about the issue
No response

TS doesn't have direct support for correlated unions as described in #30581. The only support is for generics of the form described at #47109, which is kind of yucky for a case like this:
type PairFor = { [T in typeof PAIRS[number] as T[0]]: T[1] }
type MapRet<K extends keyof PairFor> =
    { [P in K]: `${P}-${PairFor[P]}` }[K]

const CONCATENATED =
    PAIRS.map(<K extends keyof PairFor>(
        value: readonly [K, PairFor[K]]
    ): MapRet<K> => `${value[0]}-${value[1]}` as const);

type Concatenated = (typeof CONCATENATED)[number];
// type Concatenated = "a-0" | "b-1" | "c-2"

Playground link
I don't know if this is considered a duplicate of #30581 or a design limitation.


yntaxWarning: invalid escape sequence - azure-mgmt-keyvault

azure-mgmt-keyvault:
10.3.0:
alpine-3 docker image:
*3.12:

Describe the bug
We are using docker images in K8s cluster. During startup the k8s-worker throws these warnings:
/venv/lib/python3.12/site-packages/azure/mgmt/keyvault/v2023_07_01/models/_models_py3.py:4343: SyntaxWarning: invalid escape sequence '\ '
  """Properties of the vault.
/venv/lib/python3.12/site-packages/azure/mgmt/keyvault/v2023_07_01/models/_models_py3.py:4462: SyntaxWarning: invalid escape sequence '\ '
  """

similar issue with https://github.com/Azure/autorest.python/issues/2551 and is fixed after https://github.com/Azure/autorest.python/blob/main/packages/autorest.python/CHANGELOG.md#2024-04-30---61316. We will release a new package version after upgrade autorest.python

Hi @msyyc ,
Any ETA for this?
Thank you in advance

@ChenxiJiang333 Let's release a new version for azure-mgmt-keyvault

got it

Hi @shekhawatajit, @giotab, a fix version of sdk has been released.


Problem replacing groups of words larger than 10 elements in WHERE clause using LIKE operator

Information

Version of Medoo: 2.1.10
Version of PHP: 8.2.13
Type of Database (MySQL, MSSQL, SQLite...): MariaDB
System (Liunx|Windows|Mac): Linux

Describe the Problem
I had some problem running a select query with LIKE operator: I noticed that when I passed more than 10 elements as argument of the LIKE clause there is an issue in replacing correctly said group of words in the generated query.
I don't know if it is a Medoo problem or it's a db side issue but I managed to fix it by slightly modifying the source code.
I show the problem in details.

The fix I adopted is a simple modification to the index Medoo maps when the LIKE operator is used in the foreach at line 923,
$index = str_pad(strval($index), 3, '0', STR_PAD_LEFT);

In this way, placeholders have all 3 digits and the problem no longer exits.
I repeat, I'm not sure if it's a Medoo related issue or if I missed something in the configuration but you could take a look at the problem and perhaps take this issue into account by implementing a similar change.
Thank you.
PS. your library is really super useful!

Thank you for the feedback.
The problem is about the placeholder replacement and I fixed it with simpler code. 1a892c7


oraclejdk spectre/meltdown update 8u161 -> 8u162

Issue description
http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html
Steps to reproduce
We have 8u161.
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.

Judging from a quick search I came to the assumption that we have 8u172?
https://nixos.org/nixos/packages.html#8u1 . Maybe your system is outdated - if your provide the output of the command mentioned under "Technical details" in your issue we can know for sure.

there is about  7u161 and 8u152

I am sorry to say that, but I do not understand what your about to say @volth . Java version 7 is on update 111 build 01, and java 8 is on update 172 build 02 according to the current nixos-stable repos.

Oh maybe we have them as "psu" variants?
Not sure what that's about, see no mention of CPU/PSU tags on the download site linked to by our expressions.
( http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html )
Oh, according to http://www.oracle.com/technetwork/java/javase/cpu-psu-explained-2331472.html
the CPU are odd numbers and PSU are evens.  So I guess these fixes aren't considered critical?
Shrug, okay! I just wanted to make sure we had whatever fixes we were supposed to.
TIL.


correcting inconsistency about availability of RDS Roles in Server Core

The note is no longer correct. These roles are no longer available.
references:
see also https://docs.microsoft.com/en-us/windows-server/get-started-19/removed-features-19
see also @thefaftek  #4913
see also @Karl-WE #3016
moved notes to bottom for better readability
need help: cannot find powershell feature names for
Remote Desktop Connection Broker **
Remote Desktop Services \ Remote Desktop Virtualization Host **

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

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

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

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

@pronichkin only the powershell names of the roles are missing now. Thanks for review and signoff Artem.

#sign-off

@illfated: I'm sorry - only the author of this article, @pronichkin, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Yes, I know. My sign-off comment is based on an agreement with the team.

@pronichkin Can you please sign off or close this PR? Thanks!

Thanks Seth for active work on help to signoff or close long standing PRs, much appreciated! @sethmanheim

No response from author, closing.


Explore Structure Block as an Schematic alternative

https://www.youtube.com/watch?v=JkQ5TDUnNOg
https://mcreator.net/forum/53290/it-possible-rotate-schematic-when-placing-it
https://github.com/Lunatrius/Schematica/issues/282
Is it possible with a vanilla minecraft to import structure blocks? Are structure blocks as richer as schematics?

https://minecraft.gamepedia.com/Structure_Block
The structures can be mirrored or rotated when they are pasted! We need to explore it carefully because probably we should support for this format!

The rotation for Structure Block is:
Rotation (0, 90, 180, 270)
Sets the rotation of the structure to 0° (no rotation), 90° clockwise, 180° clockwise, and 270° clockwise (or 90° counter-clockwise).

https://github.com/TaylorWilton/Schematic2Structure

https://www.paperpickaxe.com/learn Schematics, and Structure blocks to share regions of minecraft

The conversion between both formats is problematic: https://www.minecraftforge.net/forum/topic/61052-1121-schematic-files-versus-nbt-for-structures-and-ways-to-convert/
MCreator seems to be the most update tool for this kind of things.

I can not find a website  with people sharing structure blocks creations.

The block is available in 1.12.2 as expected

And it seems we can select a region to do things with it!

Ok, let's try to capture a region and save it, and load it. Let's follow:
https://www.paperpickaxe.com/learn

[structures]$ ls -l
total 4
-rw-rw-r--. 1 adelcastillo adelcastillo 196 Jun  9 00:02 gold.nbt

The save has worked. Let's try now to load it.

it works!

So then process is:

Mark a corner with a structure block of type corner and name it
Mark the opposite corner putting a structure block and using detect or using the coordinates fields and use the same name  than before for the block
Press SAVE (no Save)
Add another structure block and select Load type, then define the same name and press LOAD. You need to repeat this step to confirm the loading of the block.

I find it very tricky to define the corners of the selection. It seems that the best approach is to add a corner, then add a save block and play with the coordinates inside the save dialog.

In any case, the saved data is in NBT format, so we can support it. And if we save it in this format, we can load it from Minecraft directly. But in McThings, the idea is to control from Python the loading of the Things in the Scene, so the process will be to load the NBT data from the Structure Block and then draw it from Python code, not inside Minecraft. So for us, the benefits of saving and loading inside Minecraft are not valuable.
As a conclusion, if there are large libraries of NBT structure blocks, we can add the support to McThings in order to add them to the scenes.
Wait a minute, the possibility of storing the scenes in this structure NBT data is interesting so creators can share their creations with others. This could be specially useful for Things (a Scene normally will need more than 32x32x32 blocks, so it is not possible to share it using this NBT data).
So an interesting goal is to support the saving of Things in this NBT format. Let's think about it.

This video shows all the possibilities with detail:
https://www.youtube.com/watch?v=543WnTIThGc
Once you know the basics, it can be followed.

As a conclusion, it could be interesting to save a Thing in Structure Block format so it can be easily reused. But an isolate Thing is not a big deal in McThings, where the combination of Things is the key.
And the process of loading the saved blocks and placing them in the correct position without using McThings is pretty tricky. And if McThings is used to create the Scene, why do it from this blocks version of the Thing?
So for me, the value added of this support is not clear, so I won't beat for it now.
We can continue using Schematics.


xlsxio-0.2.32-binary-win64 cannot be used in x64 projects

The xlsxio-0.2.32-binary-win64 version of the dll cannot be used in x64 projects but can be used in x86 projects

New binaries have been generated and uploaded to https://github.com/brechtsanders/xlsxio/releases/tag/0.2.32


LimitRange example improvements, detailed README

Fixes #5149

Adds a detailed README for when/why you would use a LimitRange.
Moves example files to yaml, ensured new files were caught in example_test
Has the right analytics water-mark

LGTM barring very minor stylistic nits.  @derekwaynecarr I assume that you've run this manually to validate?

@quinton-hoole - will make style updates, and yes, I ran this example as part of collecting the output based on HEAD from this morning.  will ping when updates are made.

Ping @derekwaynecarr ?

Will fix tomorrow.  Had other pressing issues to handle today.  Thanks for the reminder.
Sent from my iPhone

On Jun 8, 2015, at 6:59 PM, Quinton Hoole<EMAIL_ADDRESS>wrote:
Ping @derekwaynecarr ?
—
Reply to this email directly or view it on GitHub.

Ping? @derekwaynecarr
No desperate rush from my side, just want to make sure that this PR goes in eventually.

nits addressed

@quinton-hoole - sent this back your way since comments were addressed and I don't want to self tag a PR with lgtm.

@ihmccreery can you take a look through the README.md file and verify that it works on GCE/GKE?

@derekwaynecarr: Overall, excellent write-up.  Thanks so much for the clear writing; it's really awesome to see a tutorial written with such good explanations.
I added some inline comments for you; otherwise, this looks good to go.  I ran through it on GKE; I still need to test it for GCE, but I'm having some trouble turning up a cluster.

Finished run-through with GCE.  LGTM, once comments are addressed.

I will make the updates requested tomorrow. Thanks
Sent from my iPhone

On Jun 25, 2015, at 4:30 PM, Isaac Hollander McCreery<EMAIL_ADDRESS>wrote:
@derekwaynecarr: Overall, excellent write-up. Thanks so much for the clear writing; it's really awesome to see a tutorial written with such good explanations.
I added some inline comments for you; otherwise, this looks good to go. I ran through it on GKE; I still need to test it for GCE, but I'm having some trouble turning up a cluster.
—
Reply to this email directly or view it on GitHub.

Please update everything to the v1 API.

Addressed all feedback on text.

moved to just kubectl instead of cluster/kubectl.sh
ran through scenario on GCE provider to ensure all is good
updated examples to v1
removed empty values from pod definitions

@bgrant0607 - updated example to use "mylimits" instead of "limits"

LGTM

ok to merge
previous LGTM was here: https://github.com/GoogleCloudPlatform/kubernetes/pull/9264#issuecomment-115398302

Shippable failed with:
the path "examples/limitrange/valid-pod.json" does not exist
!!! Error in ./hack/test-cmd.sh:230

Trying to get this in today, if possible. Rerunning shippable.

@k8s-bot test this please

LGTM and ok to merge, assuming tests pass. We have a new link checker, as of a few minutes ago, so I want to make sure we run through that.

Indeed:
./hack/verify-gendocs.sh
diffing /root/workspace/src/github.com/GoogleCloudPlatform/kubernetes/docs/ against freshly generated docs
Some md files are missing ga-beacon analytics link:
/root/workspace/src/github.com/GoogleCloudPlatform/kubernetes/docs/devel/cherry-picks.md
/root/workspace/src/github.com/GoogleCloudPlatform/kubernetes/docs/ is out of date. Please run hack/run-gendocs.sh

Not from this PR. Will find out what broke.

Looks like PR #10709

Fixed by #11073. Restarting shippable again.

shippable is still complaining about gendocs.

No longer complaining about gendocs, but may have hit a flaky test.

merging for the cut.


Header bar clicks passing to map div

I have header bar and map which has static height.
First image:

Second image:

There is an setClickable() function but how can I use it when page scrolled to bottom if map div goes to under header bar.
I could not find to solve this problem.

Um, in current mechanism, this plugin does not support z-index property.
It means this plugin does not design for this case.

Okay. This is a problem for me. Will you write some code about z-index for newer versions?
Also, you should merge clusters from this fork : https://github.com/identy/cordova-plugin-googlemaps

Sorry, but detecting z-index is difficult for this plugin.
And I don't merge any pull requests at this time.
The source code of this plugin will be changed drastically in next version.

I have a similar problem, could you tell me if it's related?
If open a HTML Popup (dialog) over the map, the touch events is not captured by Popup, but by the map.

Same problem if the header bar is over the map.

It happens both Android and iOS. With JavaScript maps I had no problems.
Ionic 1.7.16
Cordova 6.3.0
cordova-plugin-googlemaps 1.3.9

map.setClickable(true/false)

I was hiding the map with ng-hide (I believe it is the same effect).
The problem is the second question, where is the scroll.
How do I know if the map is behind the Header Bar and then disable the click?

As I said above, the plugin does not support the fixed header (because z-index does not support) currently.
The plugin considers the child elements, but other elements are not.
https://github.com/mapsplugin/cordova-plugin-googlemaps/blob/master/www/googlemaps-cdv-plugin.js#L334-L361

Got it. Thank you.

Sorry

Guys, I found a solution that worked for me.
If the user schrolls the screen I lock the map: map.setClickable(false)
So, when the user touchs on map, I scroll the screen to top: $ionicScrollDelegate.scrollTop()
My View:
<ion-view view-title="Coordinates" >
  <ion-content class="padding" on-scroll="onScroll()"  >
      ...

      ...
  </ion-content>
</ion-view>

My Ctrl:
app.controller('CoordinatesCtrl', function($scope, $ionicScrollDelegate, $ionicGesture) {

  $scope.onScroll = function(){
    console.log("onScroll positon: " + $ionicScrollDelegate.getScrollPosition().top);
    if ($ionicScrollDelegate.getScrollPosition().top <= 35) {
      $scope.map.setClickable(true);
    } else {
      $scope.map.setClickable(false);
    }
  }

  $scope.onMapTouch = function(event){
    $ionicScrollDelegate.scrollTop();
  }

});

@douglasjunior You're a life saver.


Fix script decorator to properly wrap the underlying function

This fixes the script decorator so that -

Args are passed as intended
The wrapper is wrapped with functools.wraps to ensure proper stack traces. See https://docs.python.org/3/library/functools.html#functools.wraps

Does this change usage (in the examples) at all? Or just lets you use args then kwargs when calling?

@elliotgunton it doesn't. It just allows users to use the original function as is.