Fix Issue with non-capitalized Names

This was supposed to have been fixed in a previous taxcalc release, but the problem is persisting. @MattHJensen are you okay with fixing this on the TaxBrain side?

@brittainhard said in #633:

This was supposed to have been fixed in a previous taxcalc release, but the problem is persisting.

What do you mean by that?  What exactly is wrong and didn't get fixed in Tax-Calculator?
@MattHJensen

The inputs in the taxbrain form look like this:

All those names need to be capitalized. I had code that would capitalize all these names, but @MattHJensen wanted it removed, since the names for the inputs coming from TaxCalc were going to be capitalized.
Took a second look, and it does look like current_law_policy.json params do have capitalized names. I'll take a look at the code and see why this isn't bubbling up.

@brittainhard said:

All those names need to be capitalized.

But don't forget all the acronymns in the "box" names that TaxBrain is incorrectly switching to lower-case.  The most prominent of which, is TaxBrain's use of "fica" instead of "FICA".
@MattHJensen


Request: Add info from the summary table on outbreak.info Mutation Reports

I am trying to use this package to generate large tables which we are currently building manually. We need information which we are currently looking up on the Mutation Report pages on the outbreak.info site:
https://outbreak.info/situation-reports?pango&muts=S%3AT478K&loc=USA&loc=USA_US-NY&overlay=false
We would like to use the R package get the "cumulative prevalence" and "last date found" for individual mutations by location, as shown in the summary table on the above Mutation Report, so that I can use a script to generate these tables for us.

As an update: I worked out how to get the "last date found" from the data available in getPrevalence() by simply extracting the minimum date from the date column for the mutation I queried


Fix "repository not found" error

For private repositories based on this issue

Looks good, thank you.


How to implement this model to enhance my input images? Do I have to train the model to use?

Is their any pre-trained model?

Would also like a bit more details. Seems to be so common on github to just throw stuff up there with totally barebones instructions, without saying "this is what this project does, this is how to use it, etc". More common to just have a few lines of commands and that's it, not sure why that's so common, is it so hard to write another line or two?

Well I see now that it is not something that is ready for use, rather an attempt to start replicating the results of the paper. Would just be helpful to mention this at the top, as an intro, that's all.


Fix exception when receiving POISON_PILL

POISON_PILL is causing writing to closed client due to logic in code.

[retest this please]
Note: This comment is for the CI build. No action required from the author.

Thanks @luvarqpp


remove select

The check of ctx.Done is omitted, because there is no need to check whether it is closed, which can save some time and memory

A good open source practice is to describe why you believe this change is necessary or valuable to the project; "remove select" does not give reviewers enough understanding to know why you think this change is necessary or even valid. Thank you

A good open source practice is to describe why you believe this change is necessary or valuable to the project; "remove select" does not give reviewers enough understanding to know why you think this change is necessary or even valid. Thank you

Got it, I will pay more attention to it in the future, thank you

The check of ctx.Done is omitted, because there is no need to check whether it is close

Why is there no need to check whether the context is closed?

The check of ctx.Done is omitted, because there is no need to check whether it is close

Why is there no need to check whether the context is closed?

This logic is in err! = nil is triggered, at this time is already preparing return

The channel is not buffered and the reader side checks for cancel and exits, making it possible for the goroutine to leak. Even though the function is returning and process will be exiting, it is still best practice to avoid leaking goroutines.

Going to close this one since the check has a valid purpose


Sign-Up Error

When I tried to create a new account, an error occurred telling me that there is no column for the recovery string inside the database. I'm unsure if this is just a problem on my machine.

you need to delete the database create a new one

Got it. That fixed the issue.


Support angular 2.0.1

Angular 2.0.1 is out. There is nothing broken on this project, but it depends on "2.0.0" so npm complains about it.
Angular team said they will use semver from now on (I hope they keep their word), so I think it's safe to use "~2.0.0" now.

Will do, a little swamped now but I want to release something soon, with some features like AOT and stuff.
Will update.

Sorry, miss clicked on the close button


Random test ordering for cargo test

Describe the problem you are trying to solve
Sometimes tests depend on each other and one of the possible counter measures is to shuffle the order in which tests are run.
Describe the solution you'd like
I would like cargo test to take a --random flag, which would shuffle the test order. Ideally it would generate and print the seed used (a u64 integer). This could be used to debug situations, maybe with a corresponding --random-seed <seed> parameter (which would imply --random).
Notes
I had a look at the codebase and I think I identified the place where the sorting currently happens (https://github.com/rust-lang/cargo/blob/master/src/cargo/ops/cargo_test.rs#L67). I'd be happy to try to contribute a PR.

Just to clarify, are you referring to individual #[test] annotated functions, or integration test executables?

Just to clarify, are you referring to individual #[test] annotated functions, or integration test executables?

I did mean #[test] annotated functions. I realize that I might be looking at the wrong code for doing that.


Remove version: qBittorrent.qBittorrent version 4.5.2

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-4.5.2/qbittorrent_4.5.2_lt20_qt6_x64_setup.exe/download
OK
(Automated message - build 923)

Close with reason: Package still available.;


Bug in the examples/kitt

After the latest updates, the example agent KITT does not run
Exception in inference 'SynthesizeStream' object has no attribute 'flush'
Traceback (most recent call last):
  File "examples/kitt/inference_job.py", line 111, in _run
    await asyncio.gather(
  File "examples/kitt/inference_job.py", line 132, in _llm_task
    await self._tts_stream.flush()
          ^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'SynthesizeStream' object has no attribute 'flush'

Exact same problem here, did you find a fix?

No, waiting for @keepingitneil
Just put together a PoC and then it all broke ;-)

No, waiting for @keepingitneil
Just put together a PoC and then it all broke ;-)

Hey, I managed to get the example working using the Dev branch. Hope this helps!

Fixing in this PR: https://github.com/livekit/agents/pull/270. Still having an issue with this on https://agents-playground.livekit.io. ATM not sure if the issues are in the agent or in the playground so I'll wait to merge until I figure that out. But in the meantime you can reference this PR for the api changes.

Thank you, the error is gone.
But now there's no sound from the agent

{"asctime": "2024-05-04 14:31:18,802", "level": "ERROR", "name": "asyncio", "message": "Task was destroyed but it is pending!\ntask: <Task pending name='Task-25' coro=<InferenceJob._run() running at examples/kitt/inference_job.py:110> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]>>", "job_id": "AJ_89P5sAy3UAMF", "pid": 57551}
...
{"asctime": "2024-05-04 14:33:16,393", "level": "WARNING", "name": "livekit.agents", "message": "Running <Task pending name='Task-29' coro=<SpeechStream._run_ws..send_task() running at python3.11/site-packages/livekit/plugins/deepgram/stt.py:270> wait_for= cb=[gather.._done_callback() at /Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/asyncio/tasks.py:754]> took too long: 0.95 seconds", "job_id": "AJ_aHMFk2az8q3i", "pid": 56747}
...
{"asctime": "2024-05-04 14:34:52,651", "level": "ERROR", "name": "livekit", "message": "livekit_api::signal_client::signal_stream:178:livekit_api::signal_client::signal_stream - unhandled websocket message Err(Protocol(ResetWithoutClosingHandshake))", "job_id": "AJ_aHMFk2az8q3i", "pid": 56747

There's no sound from the agent
File "/usr/local/lib/python3.10/dist-packages/livekit/plugins/elevenlabs/tts.py", line 340, in recv_task\n    raise Exception("11labs connection closed unexpectedly")\nException: 11labs connection closed unexpectedly"}
Here is the full log
{"asctime": "2024-05-04 21:08:03,817", "level": "INFO", "name": "livekit.agents", "message": "starting worker", "version": "0.6.dev1"} {"asctime": "2024-05-04 21:08:03,862", "level": "INFO", "name": "livekit.agents", "message": "registered worker", "id": "AW_yWGyXdnaLMrP", "server_info": "edition: Cloud\nversion: \"1.6.1\"\nprotocol: 13\nregion: \"Germany\"\nnode_id: \"NC_DFRA1A_B37CTGiMSWmg\"\n"} {"asctime": "2024-05-04 21:08:49,804", "level": "INFO", "name": "livekit.agents", "message": "accepted job AJ_fr3H9dF4ku3d", "job": "id: \"AJ_fr3H9dF4ku3d\"\nroom {\n  sid: \"RM_DGNK8KAZd8S8\"\n  name: \"ob2l-TrBN\"\n  empty_timeout: 300\n  departure_timeout: 20\n  creation_time:<PHONE_NUMBER>\n  enabled_codecs {\n    mime: \"video/H264\"\n  }\n  enabled_codecs {\n    mime: \"video/VP8\"\n  }\n  enabled_codecs {\n    mime: \"video/VP9\"\n  }\n  enabled_codecs {\n    mime: \"video/AV1\"\n  }\n  enabled_codecs {\n    mime: \"audio/red\"\n  }\n  enabled_codecs {\n    mime: \"audio/opus\"\n  }\n  version {\n    unix_micro:<PHONE_NUMBER>020298\n  }\n}\nnamespace: \"default\"\n"} {"asctime": "2024-05-04 21:08:49,812", "level": "DEBUG", "name": "livekit.agents", "message": "process started", "url": "wss://vindo-tje6i0dq.livekit.cloud"} {"asctime": "2024-05-04 21:08:49,816", "level": "INFO", "name": "livekit", "message": "livekit_ffi::server:125:livekit_ffi::server - initializing ffi server v0.5.0"} {"asctime": "2024-05-04 21:08:49,818", "level": "INFO", "name": "livekit", "message": "livekit_ffi::server:125:livekit_ffi::server - initializing ffi server v0.5.0", "job_id": "AJ_fr3H9dF4ku3d", "pid": 52319} {"asctime": "2024-05-04 21:08:49,818", "level": "INFO", "name": "livekit", "message": "livekit_ffi::cabi:27:livekit_ffi::cabi - initializing ffi server v0.5.0"} {"asctime": "2024-05-04 21:08:49,819", "level": "INFO", "name": "livekit", "message": "livekit_ffi::cabi:27:livekit_ffi::cabi - initializing ffi server v0.5.0", "job_id": "AJ_fr3H9dF4ku3d", "pid": 52319} {"asctime": "2024-05-04 21:08:49,822", "level": "INFO", "name": "livekit", "message": "livekit_api::signal_client::signal_stream:88:livekit_api::signal_client::signal_stream - connecting to wss://vindo-tje6i0dq.livekit.cloud/rtc?sdk=rust&protocol=9&auto_subscribe=0&adaptive_stream=0&access_token=..."} {"asctime": "2024-05-04 21:08:49,823", "level": "INFO", "name": "livekit", "message": "livekit_api::signal_client::signal_stream:88:livekit_api::signal_client::signal_stream - connecting to wss://vindo-tje6i0dq.livekit.cloud/rtc?sdk=rust&protocol=9&auto_subscribe=0&adaptive_stream=0&access_token=...", "job_id": "AJ_fr3H9dF4ku3d", "pid": 52319} {"asctime": "2024-05-04 21:08:49,840", "level": "DEBUG", "name": "livekit", "message": "rustls::anchors:150:rustls::anchors - add_parsable_certificates processed 137 valid and 0 invalid certs"} {"asctime": "2024-05-04 21:08:49,840", "level": "DEBUG", "name": "livekit", "message": "tokio_tungstenite::tls::encryption::rustls:103:tokio_tungstenite::tls::encryption::rustls - Added 137/137 native root certificates (ignored 0)"} {"asctime": "2024-05-04 21:08:49,841", "level": "DEBUG", "name": "livekit", "message": "rustls::client::hs:73:rustls::client::hs - No cached session for DnsName(\"vindo-tje6i0dq.livekit.cloud\")"} {"asctime": "2024-05-04 21:08:49,842", "level": "DEBUG", "name": "livekit", "message": "rustls::client::hs:132:rustls::client::hs - Not resuming any session"} {"asctime": "2024-05-04 21:08:49,845", "level": "DEBUG", "name": "livekit", "message": "rustls::client::hs:615:rustls::client::hs - Using ciphersuite TLS13_AES_128_GCM_SHA256"} {"asctime": "2024-05-04 21:08:49,845", "level": "DEBUG", "name": "livekit", "message": "rustls::client::tls13:142:rustls::client::tls13 - Not resuming"} {"asctime": "2024-05-04 21:08:49,846", "level": "DEBUG", "name": "livekit", "message": "rustls::client::tls13:381:rustls::client::tls13 - TLS1.3 encrypted extensions: []"} {"asctime": "2024-05-04 21:08:49,846", "level": "DEBUG", "name": "livekit", "message": "rustls::client::hs:472:rustls::client::hs - ALPN protocol is None"} {"asctime": "2024-05-04 21:08:50,270", "level": "DEBUG", "name": "livekit", "message": "tungstenite::handshake::client:95:tungstenite::handshake::client - Client handshake done."} {"asctime": "2024-05-04 21:08:50,595", "level": "DEBUG", "name": "httpx", "message": "load_ssl_context verify=True cert=None trust_env=True http2=False"} {"asctime": "2024-05-04 21:08:50,598", "level": "DEBUG", "name": "httpx", "message": "load_verify_locations cafile='/etc/ssl/certs/ca-certificates.crt'"} {"asctime": "2024-05-04 21:08:50,676", "level": "ERROR", "name": "livekit.agents", "message": "unhandled exception in the job entry <function entrypoint at 0x7f64bf27bd90>", "exc_info": "Traceback (most recent call last):\n  File \"/root/agent/agent.py\", line 146, in entrypoint\n    async with asyncio.TaskGroup() as tg:\nAttributeError: module 'asyncio' has no attribute 'TaskGroup'\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n  File \"/root/agent/agent.py\", line 149, in entrypoint\n    except BaseExceptionGroup as e:\nNameError: name 'BaseExceptionGroup' is not defined. Did you mean: 'BaseException'?"} {"asctime": "2024-05-04 21:08:50,690", "level": "ERROR", "name": "livekit.agents", "message": "unhandled exception in the job entry <function entrypoint at 0x7f64bf27bd90>\nTraceback (most recent call last):\n  File \"/root/agent/agent.py\", line 146, in entrypoint\n    async with asyncio.TaskGroup() as tg:\nAttributeError: module 'asyncio' has no attribute 'TaskGroup'\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n  File \"/root/agent/agent.py\", line 149, in entrypoint\n    except BaseExceptionGroup as e:\nNameError: name 'BaseExceptionGroup' is not defined. Did you mean: 'BaseException'?\n", "job_id": "AJ_fr3H9dF4ku3d", "pid": 52319} {"asctime": "2024-05-04 21:08:50,690", "level": "INFO", "name": "root", "message": "Running inference with user transcription: "} {"asctime": "2024-05-04 21:08:50,690", "level": "INFO", "name": "root", "message": "Running inference with user transcription: ", "job_id": "AJ_fr3H9dF4ku3d", "pid": 52319} {"asctime": "2024-05-04 21:08:50,693", "level": "ERROR", "name": "root", "message": "Exception in inference 'SynthesizeStream' object has no attribute 'flush'", "exc_info": "Traceback (most recent call last):\n  File \"/root/agent/inference_job.py\", line 111, in _run\n    await asyncio.gather(\n  File \"/root/agent/inference_job.py\", line 132, in _llm_task\n    await self._tts_stream.flush()\nAttributeError: 'SynthesizeStream' object has no attribute 'flush'"} {"asctime": "2024-05-04 21:08:50,697", "level": "ERROR", "name": "root", "message": "Exception in inference 'SynthesizeStream' object has no attribute 'flush'\nTraceback (most recent call last):\n  File \"/root/agent/inference_job.py\", line 111, in _run\n    await asyncio.gather(\n  File \"/root/agent/inference_job.py\", line 132, in _llm_task\n    await self._tts_stream.flush()\nAttributeError: 'SynthesizeStream' object has no attribute 'flush'\n", "job_id": "AJ_fr3H9dF4ku3d", "pid": 52319} {"asctime": "2024-05-04 21:08:51,777", "level": "INFO", "name": "root", "message": "Committing agent response: Hello, I am KITT, a friendly voice assistant powered by LiveKit Agents.         You can find my source code in the top right of this screen if you're curious how I work.         Feel free to ask me anything \u2014 I'm here to help! Just start talking or type in the chat."} {"asctime": "2024-05-04 21:08:51,778", "level": "INFO", "name": "root", "message": "Committing agent response: Hello, I am KITT, a friendly voice assistant powered by LiveKit Agents.         You can find my source code in the top right of this screen if you're curious how I work.         Feel free to ask me anything \u2014 I'm here to help! Just start talking or type in the chat.", "job_id": "AJ_fr3H9dF4ku3d", "pid": 52319} {"asctime": "2024-05-04 21:09:13,537", "level": "ERROR", "name": "livekit.plugins.elevenlabs", "message": "11labs connection failed", "exc_info": "Traceback (most recent call last):\n  File \"/usr/local/lib/python3.10/dist-packages/livekit/plugins/elevenlabs/tts.py\", line 365, in _run_ws\n    await asyncio.gather(send_task(), recv_task())\n  File \"/usr/local/lib/python3.10/dist-packages/livekit/plugins/elevenlabs/tts.py\", line 340, in recv_task\n    raise Exception(\"11labs connection closed unexpectedly\")\nException: 11labs connection closed unexpectedly"} {"asctime": "2024-05-04 21:09:13,538", "level": "ERROR", "name": "livekit.plugins.elevenlabs", "message": "11labs connection failed\nTraceback (most recent call last):\n  File \"/usr/local/lib/python3.10/dist-packages/livekit/plugins/elevenlabs/tts.py\", line 365, in _run_ws\n    await asyncio.gather(send_task(), recv_task())\n  File \"/usr/local/lib/python3.10/dist-packages/livekit/plugins/elevenlabs/tts.py\", line 340, in recv_task\n    raise Exception(\"11labs connection closed unexpectedly\")\nException: 11labs connection closed unexpectedly\n", "job_id": "AJ_fr3H9dF4ku3d", "pid": 52319} {"asctime": "2024-05-04 21:09:13,539", "level": "ERROR", "name": "asyncio", "message": "Unclosed client session\nclient_session: <aiohttp.client.ClientSession object at 0x7f64b996dbd0>"} {"asctime": "2024-05-04 21:09:13,540", "level": "ERROR", "name": "asyncio", "message": "Unclosed client session\nclient_session: <aiohttp.client.ClientSession object at 0x7f64b996dbd0>", "job_id": "AJ_fr3H9dF4ku3d", "pid": 52319}

Thanks for reporting this everyone, this was fixed in https://github.com/livekit/agents/pull/271 and has now been released in the latest stable package.


Playground: add sample for adding external lib and exposing it globally

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: StasZelenskiy sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

This sample uses exactly the same monaco editor APIs as https://microsoft.github.io/monaco-editor/playground.html#extending-language-services-configure-javascript-defaults , so I believe it is redundant.
I agree that this sample shows how it is possible to add two different .d.ts files and then import from one, and export to the global list from the other, but that is very specific to the TypeScript language. There are very many patterns in the TypeScript language that can be used in .d.ts files and the scope of this playground is limited to show editor API. In this case, the used editor API is equivalent to the editor API used in https://microsoft.github.io/monaco-editor/playground.html#extending-language-services-configure-javascript-defaults .
So what I am saying is that while this sample is very useful, it is redundant from an editor API point of view, as the used editor API is already covered in another sample.

OK, I mostly agree, even though I find the typings addition aspect pretty hidden behind this configure defaults example. I'd prefer a dedicated demo, particulary because this is a pretty specific thing. Just my 2 cents.


[Question] about dependency rich-click

Hi,
is there a reason that the dependency rich-click is pinned to version 1.4? Because of this, I cannot use higher version of rich-click in my projects. The actual version of rich-click is 1.6.1.
When I update the rich-click version with pip, pip says
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
robotframework-tidy 4.0.1 requires rich-click==1.4, but you have rich-click 1.6.1 which is incompatible.

maybe you can change the dependency to >=1.4?

No reason, I went with whatever was stable when I was adding rich click to tidy. I can bump version - but I will most likely keep closed requirement (up to 1.4.1 or whatever is most recent now) just to be safe. It is under active development and there were versions with regression.

And I will set dependabot to remind me to update dependecies when there is release

I think that would be good.
but I would include the patch versions, so something like >=1.4,<1.7

I did setup dependabot and I have successfully updated all the packages,, except the rich_click which failed :) https://github.com/MarketSquare/robotframework-tidy/pull/518 But I have narrowed it down to 1.5.0 and code update which force different mode when it's running in the Github actions. No issue in the rich_click but this feature makes it unable to test it. I will need to workaround it first

Thanks!


Fixed link to „Hugo + Staticman“

@ChrisLasar Due to b9e53f788d718eecbd09e49101b9fc5e8fdcde13, I think you can close this issue.


(maint) Expect with hash arguments instead of kwargs

Facter verifies partial doubles so arguments are checked against the original method and to ensure methods that don't exist can't be stubbed. RSpec 3.11.2 changes how keyword arguments are verified[1].
So previously you could write expect(:m).with(a: true) and it would pass if the method was called with a hash or keyword arguments. But now the expectation must expect a hash, not keyword arguments.
[1] https://github.com/rspec/rspec-mocks/commit/bc1a68725d57e167c885763e7f3edc236f92b7b5

See also https://github.com/puppetlabs/puppet/pull/8942


Windows line endings in scripts

Windows line endings does not recognized by bash:
root@536137b2e733:/workspace# chmod +x manage.py
root@536137b2e733:/workspace# ./manage.py runserver
/usr/bin/env: ‘python\r’: No such file or directory

Please instead of ./manage.py runserver  use this command  manage.py runserver


Very long execution time running the examples

Running the given examples take a lot more time than using the cli version on the same machine.
texture-synthesis --out out/01.jpg generate imgs/1.jpg
took 20 seconds
while
cargo run --example 01_single_example_synthesis
took like 12 minutes with cpu on full throttle.
Device:

OS: Os X 10.13.6
rustc 1.38.0 (625451e37 2019-09-23)
Version 0.6.0 master branch freshly compiled today.

Run the example twice after compilation. Same.
Thanks.
jan

Just using cargo run builds and runs the executable in debug mode, which is slow.
Use: cargo run --release -- --example 01_single_example_synthesis to run an optimized release build which is much faster


Rename repository to ory/works

Currently, the URL and titles are duplicate: ory/oryworks. I suggest renaming this repo to ory/works

@tacurran
Lets rename the repo?
I think its a good idea!

done


fix: Add impersonate_user setting to import/export datasource

When exporting or importing a datasource/DB, it is necessary get the impersonate_user setting, as it is a key part of the configuration of that datasource. This unfortunately requires a code change, as this list of fields is whitelisted today.
SUMMARY

The UI lets a user control whether a particular datasource supports impersonation, which is very helpful when creating it interactively. However, when exporting the datasource or importing it programmatically, the value for impersonate_user is not exported/imported, leading to a gap in functionality.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A
TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@itay sorry for the long delay, but would you be able to rebase this PR to resolve the conflict? The fix looks legit but just got buried under other PRs 🙁

@villebro done - hope it helps, would be great to have it merged.

@itay LGTM, but it appears you need to update the failing tests

@villebro let's see if this update resolves it

@betodealmeida thanks for the feedback. The requirements for getting the change in are getting bigger than I have time to put in at the moment - I originally needed this change back in May and have a mini-fork of Superset with just this change, and wanted to contribute it upstream. However, given 6 months have passed, I don't quite have the time to understand the test structure and add the changes right now.
I'm happy if someone else wants to take over this change, or I can try and add the tests as I get some time to do it, but it likely won't be soon.

@betodealmeida thanks for the feedback. The requirements for getting the change in are getting bigger than I have time to put in at the moment - I originally needed this change back in May and have a mini-fork of Superset with just this change, and wanted to contribute it upstream. However, given 6 months have passed, I don't quite have the time to understand the test structure and add the changes right now.
I'm happy if someone else wants to take over this change, or I can try and add the tests as I get some time to do it, but it likely won't be soon.

I totally understand, and I know how this is frustrating, so my apologies for the delay. Either me or @villebro can take a stab at the tests.

No problem - open source maintenance is hard especially for a project as successful as Superset, so I know how difficult it can be to get to the PRs, and I appreciate the response and engagement from the team.

I'm happy to push a few tests to this PR if needed! Again, thanks so much for you patience and understanding!

@itay any luck with the tests?


Flaky test - CliqueProposeRpcAcceptanceTest

example failure https://github.com/hyperledger/besu/actions/runs/12131035525/job/33822468361
CliqueProposeRpcAcceptanceTest > shouldNotAddValidatorWhenInsufficientVotes() FAILED
    java.lang.AssertionError:
    Expecting actual:
      1
    to be greater than or equal to:
      2
        at org.hyperledger.besu.tests.acceptance.dsl.condition.blockchain.ExpectBlockNumberAbove.lambda$verify$0(ExpectBlockNumberAbove.java:46)
        at org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53)
        at org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:248)
        at org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:235)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
        at java.base/java.lang.Thread.run(Thread.java:1583)

another one https://github.com/hyperledger/besu/actions/runs/12149639539/job/33880752770?pr=7979

should be fixed by #7993

another one https://github.com/hyperledger/besu/actions/runs/12227197580/job/34103578101

another one https://github.com/hyperledger/besu/actions/runs/12281573767/job/34270784699?pr=8018

another one https://github.com/hyperledger/besu/actions/runs/12343809466/job/34445457215
different method though
CliqueProposeRpcAcceptanceTest > shouldAddValidators() FAILED


If a user has Link Preview disabled in their settings, bot does not function

Due to the way that Nadeko embeds its links through markup wizardry, if a user has Link Previews turned off in their client-side settings, then nothing shows up when the bot posts:

There is no fallback text link!

That's not a bug. Nadeko posts using Discord embeds, so if users don't have Link Previews enabled they obviously won't see anything. That's how it is and there's nothing that can be done about it.

No, it's a bug.  Turning link preview off is a legitimate Discord setting that users can--and will--utilize. If the bot doesn't support it, then your bot is broken.  You might think it's awesome and clever to embed images that way, but as someone who doesn't want link previews cluttering the chat interface after I've viewed it (or mobile users who don't want it eating their mobile data), it makes your bot not function.
As a result, our server owner is already looking for alternative solutions.

Good luck finding a bot that doesn't use embeds.

Bot is using embeds. If you don't want to see embeds, you can't see bot's responses. Logic - not a bug.

I think its already reported several times in Discord Devs Server, Discord shouldn't block the embed posts when only embeded link previews are disabled.


Add framework for end to end tests

Okay just rebased and squashed the previously awfully big number of commits. If you could please give it a onceover at some point @zanemountcastle that would be great :). And if you merge it please do it with the rebase as I think this PR is too big to squash and I already squashed my commits to be more modularized (went from like 30 to 7).

Before merging this in, could you add a Wiki page on writing end-to-end tests for future devs? It isn't super clear from the code.

Oh yeah, framework is maybe a bit misleading, I guess it's more like prerequisites. When we merge this in I already have this branch ready to create a PR for: https://github.com/thegazelle-ad/gazelle-server/compare/feature/simple-end-to-end-test...feature/initial-end-to-end-tests which can be an example, and I'm working on a few more more complex tests to provide more examples.
And then I think I'd also add something to the wiki about running the end to end tests maybe, but he writing should hopefully be clear from examples

And about the code how was that? Did you find anything you wanted changed there?

Okay I'll override merge it in as the dismissal of the state review was due to me pushing some code and then removing it again so it's the same as you first looked at @zanemountcastle :).
Can't wait until all of this is completely live!


Support installing npmjs.com plugins via CLI

Currently it expects a github.com URL and fails

Nope. See #4


[FEATURE REQUEST] Optimization only

First was js been faster. But after adding some modularity tool compatilibity code my code was slowed down.
After minifed with Closure compiler my js again almost same as before.
Now i want, no variable shortening, no minify. Just optimize. I think this will be amazing.
Thanks

You could create a custom build of the compiler and turn off the renaming. However this rarely makes sense. The compiler performs whole-world optimizations and the assumptions allowing many of those optimizations are the same as is needed to do renaming.
Simple mode has all the optimizations that are proven safe without the whole world optimizations.

You can try using the Compiler via the Java API for finer control over which optimizations you want enabled.

I want move variables in need place. And loop optimization too

Have you tried using SIMPLE mode with the --assume_function_wrapper flag?

I trying with online way


Added thickness parameter for drawing bounding boxes

Added a thickness parameter for the DrawBoundingBoxesV2 op after the color parameter.
Previously, there were two kernel ops, DrawBoundingBoxes and DrawBoundingBoxesV2, but both of them referenced the same function. Still haven't completely understood this design choice, but it would be nice if that could be simplified.
Also not sure where to add tests for the same, if any. Would appreciate assistance on the testing front, if it is required.

We can't add new inputs to existing operations, since they get serialized in SavedModels having only the original number of inputs.
That's why we have V2 of the op, and it's why we'd need V3 to add this new input.
How were you planning to expose this to users?
Adding @tanzhenyu who has worked on image ops before.

We can't add new inputs to existing operations, since they get serialized in SavedModels having only the original number of inputs. That's why we have V2 of the op, and it's why we'd need V3 to add this new input.

Ah okay, did not know that. If that is going to be the case, I was actually thinking of adding a dash-interval functionality too(for making a dashed-line), should probably add that before finalizing a V3

How were you planning to expose this to users?

I thought this might make a good addition to the existing draw_bounding_boxes functionality. However, I'm not sure where the gen_image_ops gets generated from/find the file. Do you have any recommendations/thoughts?

We can't add new inputs to existing operations, since they get serialized in SavedModels having only the original number of inputs. That's why we have V2 of the op, and it's why we'd need V3 to add this new input.

Ah okay, did not know that. If that is going to be the case, I was actually thinking of adding a dash-interval functionality too(for making a dashed-line), should probably add that before finalizing a V3

How were you planning to expose this to users?

I thought this might make a good addition to the existing draw_bounding_boxes functionality. However, I'm not sure where the gen_image_ops gets generated from/find the file. Do you have any recommendations/thoughts?

If you add a V3 version of the op, it'll have its own binding generated automatically. You could just switch the Python to calling _v3.
I would suggest adding to the Python API and adding some tests if the op is changing. But I have very little background on image ops, so I'm not a great person to decide on whether it's a good idea to add these / if there are existing alternatives / if this could be expressed as a composition of smaller ops. Maybe Zhenyu can chime in there, and eventually it'll need an API review anyway.

@rsnk96  Can you please check @allenlavoie's comments and keep us posted ? Thanks!

Which paper is this to support?

You could just switch the Python to calling _v3

I'm trying to find where the Python --> C kernel binding is being defined, but am unable to find it. Could someone please assist with this?

Which paper is this to support?

This isn't to support a paper, this is just a functionality to make the draw box function more usable. In cases where the image is too big, a 1-pixel-width line is not too visible. So what I'm hoping thru this PR is to add a thickness parameter (and soon also a dashed-configuration for the rectangle). Any comments/recommendations?

You could just switch the Python to calling _v3

I'm trying to find where the Python --> C kernel binding is being defined, but am unable to find it. Could someone please assist with this?

These rules: https://github.com/tensorflow/tensorflow/blob/131a9225ed292e762e668cca72bb1ebe3625904c/tensorflow/python/BUILD#L2844
You can follow it to the .bzl file it's defined in, and you'll find some C++ that generates some Python for the gen_*.py file. That communicates with the runtime via string op names at the moment. Not sure how useful that is for adding a new op; I'd just do what the other ops are doing.

@rsnk96  Can you please check @allenlavoie's comments and resolve conflicts?. Thanks!

@rsnk96  Can you please check @allenlavoie's comments and keep us posted ? Thanks!

For a new op there is a three-week forward compatibility window to allow serving binaries to be updated, see https://www.tensorflow.org/api_docs/python/tf/compat/forward_compatible

Included the forward compatibility check now @allenlavoie

Looks like there's also a relevant compile failure (you may have to specify int32/int64 in the REGISTER_OP call):

2020-09-01 20:09:12.927904: F tensorflow/core/framework/op.cc:214] Non-OK-status: RegisterAlreadyLocked(deferred_[i]) status: Invalid argument: Reference to unknown attr 'int' from Input("thickness: int") for Op DrawBoundingBoxesV3

Looks like there's also a relevant compile failure (you may have to specify int32/int64 in the REGISTER_OP call):

2020-09-01 20:09:12.927904: F tensorflow/core/framework/op.cc:214] Non-OK-status: RegisterAlreadyLocked(deferred_[i]) status: Invalid argument: Reference to unknown attr 'int' from Input("thickness: int") for Op DrawBoundingBoxesV3

@rsnk96 Can you please check @allenlavoie's comments and keep us posted ? Thanks!

@rsnk96  Any update on this PR? Please. Thanks!

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

@rsnk96 Any update on this PR? Please. Thanks!

I'm going to go ahead and close this PR, because it seems to have stalled. If you're still interested in pursing this (and responding to my comments), please feel free to reopen!


[Feature request] Use a specific browser profile for authentication

Similar to how a browser profile can be specified when launching a console, I would also like to specify a browser profile to open the authentication links.
The main use case is I have a work browser profile where I log in to our company's SSO every morning. The SSO is linked to many things, including AWS SSO. If the authentication links open in this profile, I simply need to "accept", but it always open in the default browser profile, which is my personal profile, and I don't want to SSO into the work account from my personal profile because it messes up Google, Microsoft, and GitHub login sessions.

Hey @khuongduybui! You should be able to use the following command to achieve this:
granted browser set-sso

I'll close this issue but please reopen it if it doesn't work for you :)

The problen with
granted browser set-sso

is it doesn't let me select a specific profile.
It doesn't let me enter a custom command either (with which I can inject the profile argument).

My apologies - I misread your initial question here as being related to selecting a browser rather than a browser profile. I’ve reopened the issue, this is something we should support for sure.

+1 for that, I have exactly the same issue.
@chrnorm we talk about granted browser set-sso, but even for granted browser set - is it possible to set the default browser profile instead of specifying it each time running assume?
assume profile-name -c --browser-profile "<your_browser_profile>"

I had this issue and solved it by using the profile settings in Edge itself to open/use a specific profile when it was given a specific URL.
But I agree, something more programmatic at the assume level is required to support browsers that may not have that feature.


Builders: NodeJs Builder

doesn't follow builders guidlines

Reorganized the code to match the new structure and I am trying to make the install work.

The build and install now work fine without any errors and I can run npm. However, I am getting a message that bower is deprecated, so I am looking at other alternatives to be used instead. I also upgraded the node version but yet to find out if it will work out well with scality.

-verified.


Make nekt.compose.css enums consistent with WebCompose style

Compare:
# web compose

interface DisplayStyle: StylePropertyEnum {
    companion object {
        inline val Block get() = DisplayStyle("block")
        inline val Inline get() = DisplayStyle("inline")
        ...
        inline val Initial get() = DisplayStyle("initial")
        inline val Unset get() = DisplayStyle("unset")
    }
}

# kobweb compose

enum class FontStyle(val value: String) {
    NORMAL("normal"),
    ITALIC("italic"),
}

We should match upstream style, especially we hope someday that maybe they'll implement the holes we're filling

I did this at some point


Moby container runtime

What this PR does / why we need it:
Deprecates docker-engine in favor of moby.
See:
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-linux#register-microsoft-key-and-software-repository-feed
Includes a prototype of a feature-flag-enabled VHD CI process. This prototype assumes that at CI time, we include an environment variable string that includes a list of enabled feature flags. E.g.:
FEATURE_FLAGS="feature-foo,feature-bar"
And then VHD CI would evaluate like this:
if [[ $FEATURE_FLAGS == *"feature-foo"* ]]; then...
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

Testing is currently blocked on:
$ kubectl describe hpa php-apache-kubernetes-eastus-50779-53479
Name:                                                  php-apache-kubernetes-eastus-50779-53479
Namespace:                                             default
Labels:                                                <none>
Annotations:                                           <none>
CreationTimestamp:                                     Mon, 24 Sep 2018 17:28:06 +0000
Reference:                                             Deployment/php-apache-kubernetes-eastus-50779-53479
Metrics:                                               ( current / target )
  resource cpu on pods  (as a percentage of request):  <unknown> / 5%
Min replicas:                                          1
Max replicas:                                          10
Conditions:
  Type           Status  Reason                   Message
  ----           ------  ------                   -------
  AbleToScale    True    SucceededGetScale        the HPA controller was able to get the target's current scale
  ScalingActive  False   FailedGetResourceMetric  the HPA was unable to compute the replica count: unable to get metrics for resource cpu: no metrics returned from resource metrics API
Events:
  Type     Reason                        Age              From                       Message
  ----     ------                        ----             ----                       -------
  Warning  FailedGetResourceMetric       2s (x3 over 1m)  horizontal-pod-autoscaler  unable to get metrics for resource cpu: no metrics returned from resource metrics API
  Warning  FailedComputeMetricsReplicas  2s (x3 over 1m)  horizontal-pod-autoscaler  failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

FYI same symptom above w/ Azure CNI or Kubenet.

@jackfrancis .. @cpuguy83 graciously agreed to help with this one. I shared with him the high level details.
@ritazh FYI

Ok... here's the problem.
Registration of the Docker container factory failed: failed to validate Docker info: version string "dev" doesn't match expected regular expression: "(\d+)\.(\d+)\.(\d+)"

This error is from the kubelet when it is registering cadvisor metrics handlers (FYI, kubelet uses an internal cadvisor to collect metrics for the "docker" runtime).
When building we need to set a version to use otherwise the version output is:
Server:
 Engine:
  Version:      dev
  API version:  1.38 (minimum version 1.12)
  Go version:   go1.10.3
  Git commit:   09f5e9d
  Built:        Wed Sep 19 16:55:45 2018
  OS/Arch:      linux/amd64
  Experimental: false

To set the version, when building moby you must specify -ldflags="-X dockerversion.Version=<version>.
This will instruct the compiler to overwrite the default variable set in github.com/moby/moby/dockerversion.Version

Or just hardcode it...

Thanks I will revisit the build process and make sure version is attached
Get Outlook for iOShttps://aka.ms/o0ukef

From: Brian Goff<EMAIL_ADDRESS>Sent: Tuesday, October 2, 2018 15:09
To: Azure/acs-engine
Cc: Khaled Henidak (Kal); Comment
Subject: Re: [Azure/acs-engine] [WIP] Moby container runtime (#3896)
Ok... here's the problem.
Registration of the Docker container factory failed: failed to validate Docker info: version string "dev" doesn't match expected regular expression: "(\d+).(\d+).(\d+)"
This error is from the kubelet when it is registering cadvisor metrics handlers (FYI, kubelet uses an internal cadvisor to collect metrics for the "docker" runtime).
When building we need to set a version to use otherwise the version output is:
Server:
Engine:
Version:      dev
API version:  1.38 (minimum version 1.12)
Go version:   go1.10.3
Git commit:   09f5e9d
Built:        Wed Sep 19 16:55:45 2018
OS/Arch:      linux/amd64
Experimental: false
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Facs-engine%2Fpull%2F3896%23issuecomment-426447129&data=02|01||7dd54d624bc049573cb308d628b3a930|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636741149424457538&sdata=mOHkXBZY%2BaIeowy1P4tySw7B1BrfpGLL9Jw9yQn6Snw%3D&reserved=0, or mute the threadhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKMDQ1QLw2bFEycmFjn0vO8AR226tZDqks5ug-P9gaJpZM4W3B6k&data=02|01||7dd54d624bc049573cb308d628b3a930|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636741149424457538&sdata=Z%2BJxvPl8R8hACDNSwiecyDYp5h6mprASVfYuffmN5tg%3D&reserved=0.

To set the version, when building moby you must specify -ldflags="-X dockerversion.Version=<version>.
This will instruct the compiler to overwrite the default variable set in github.com/moby/moby/dockerversion.Version

for future us it is actually make VERSION=<version> the variable above is set by scripts.

Initial tests of Windows hybrid clusters against this changeset are 💯

🎉


refactor: Pull CDK app into main directory

@l0b0 , this change might make a sense, but to me it looks to me that some more directories structure refactoring might be needed (for example moving  backend dir to datalake ?).

@l0b0 , this change might make a sense, but to me it looks to me that some more directories structure refactoring might be needed (for example moving backend dir to datalake ?).

Would that maybe fit better into another PR?

We can do it in next PR, but really should be done then.


Added Sankt Annæ Gymnasium

Thanks for your great work!
Great products

@TheHenckel Thank you for your warm words!
Please provide us with a proof (.pdf or a screenshot are OK) showing that the school recognizes the domain which you are submitting (undervisning.kk.dk) as an official email domain for the students.

@TheHenckel You might miss my previous comment. Please react.


Update Composer dependencies (2024-10-03-00-11)

Visual regression test passed!
View the visual regression test report


Fix failing newview

There was some refactor of Quantity upstream that we didn't properly accommodate.
This PR incorporates #885 too.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (4793c27) 79.88% compared to head (5049e70) 79.88%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #886   +/-   ##
=======================================
  Coverage   79.88%   79.88%
=======================================
  Files          24       24
  Lines        6035     6035
=======================================
  Hits         4821     4821
  Misses       1214     1214

Impacted Files
Coverage Δ

spectral_cube/lower_dimensional_structures.py
84.70% <100.00%> (ø)

spectral_cube/masks.py
80.25% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

I removed #885 and force-pushed to see if that causes tests to fail (with that included, tests passed!)

We still don't have a test that checks for the deprecation in #883, but that's probably b/c we're not checking for deprecations in tests.

The CASA test has been hung waiting for a runner for 5 hours now; everything else is green.  I'm merging.


snutt 전체 마이그레이션

course book

[ ] GET /course_books
[ ] GET /course_books/recent
[ ] GET /course_books/official

colors

[ ] GET /colors
[ ] GET /colors/:colorName

lecture

[x] POST /search_query

tags

[ ] GET /tags/:year/:semester/update_time
[ ] GET /tags/:year/:semester

auth

[ ] POST /auth/request_temp
[x] POST /auth/login_local
[x] POST /auth/register_local
[ ] POST /auth/login_apple
[ ] POST /auth/login_fb
[x] POST /auth/logout
[ ] POST /auth/password/reset/email/check
[ ] POST /auth/password/reset/email/send
[ ] POST /auth/password/reset/verification/code
[ ] POST /auth/password/reset
[ ] POST /auth/id/find

users

[x] GET /user/info
[ ] DELETE /user/email/verification
[ ] POST /user/email/verification
[ ] POST /user/email/verification/code
[ ] GET /user/email/verification
[ ] POST /user/password
[ ] PUT /user/password
[ ] POST /user/facebook
[ ] DELETE /user/facebook
[ ] GET /user/facebook
[x] POST /user/device/:registration_id
[x] DELETE /user/device/:registration_id
[ ] DELETE /user/account

timetables

[x] GET /tables/
[x] GET /tables/recent
[x] GET /tables/:id
[x] GET /tables/:year/:semester
[x] POST /tables
[ ] POST /tables/:timetable_id/lecture/:lecture_id
[ ] POST /tables/:id/lecture
[ ] PUT /tables/:table_id/lecture/:lecture_id
[ ] PUT /tables/:table_id/lecture/:lecture_id/reset
[ ] DELETE /tables/:table_id/lecture/:lecture_id
[x] DELETE /tables/:id
[x] POST /tables/:id/copy
[x] PUT /tables/:id
[x] PUT /tables/:id/theme

notificiation

[x] GET /notification
[x] GET /notification/count

admin

[x] POST /admin/insert_noti
[ ] POST /admin/change_pw
[ ] GET /admin/recent_fcm_log
[ ] GET /admin/coursebooks
[ ] GET /admin/statistics

ev-service (얘네는 어짜지)

[ ] GET /ev-service/v1/users/me/lectures/latest
[ ] GET /ev-service/*

etc

[ ] POST /feedback
[ ] GET /popups

1/3 달성


Added   Binary.cpp code

Hey , I have Added the Ques along with the code😊 Please Check it 😊
On Wed, 5 Oct 2022, 21:58 Harjas kaur, @.***> wrote:

Okay 😊 Sure , Will Add it Soon 👍😊
On Wed, 5 Oct 2022, 21:11 VanshikaSharma, @.***>
wrote:

add question link in your code
—
Reply to this email directly, view it on GitHub
https://github.com/Vanshika2063/Leetcode-Questions/pull/262#issuecomment-1268609446,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXODHJN67PQAYMCMR6QLMFDWBWOSVANCNFSM6AAAAAAQ5TGEK4
.
You are receiving this because you authored the thread.Message ID:
@.***>


[openapi] Add support for security scheme

I think this PR touches the right codepaths, but I'm not sure. I also think this feature should support a list of schemes, not just one scheme. I'm not sure how to connect the actual list of schemes to the rest of the documentation yet though.

@tipsy I have already looked at #805, and made some changes at my local repo. Was waiting you to release multi module to fork it and PR with my way I see this feature.

@sealedtx Please push it now, I keep going back and forth on the multi-module decision.

@tipsy I could push my commits tomorrow, maybe on Monday

That would be great, thanks!


Change Layouts on Homescreen

change the logout button and rulebook button so logout is farthest right as in most applications
change the buttons in the middle so that there are two rows of two buttons, rather than 3 on one side and 1 on the other. I.e., move join button below statistics.

closed with commit https://github.com/sopra-fs23-group-37/client/commit/d092250bc338b74fb1f3f635e8b53a571720dab7


Print warning when selected runtime version is/will be going EOS

Similar to the work done in the Node.js and Go Buildpacks, we should start printing deprecation messages in the NGINX Buildpack that lets users select a runtime version when a dependency is/will be EOS.

@thitch97 Should we prioritize this? (Also, is this a good "first-time" story)

I feel like this should be handled automatically by the logger now no?


Please move the service fabric settings reference document to its own, more discoverable page

The settings reference for service fabric clusters is very important and useful so it should have its own page with a table and contents and so on. Right now its difficult to find since its inside a how-to specifically for azure.

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

ID: 6005a24c-118d-6c56-5525-4616e9102fe0
Version Independent ID: 429e2d0f-d5da-8972-2890-52081eee3330
Content: Change Azure Service Fabric cluster settings | Microsoft Docs
Content Source: articles/service-fabric/service-fabric-cluster-fabric-settings.md
Service: service-fabric
GitHub Login: @ChackDan
Microsoft Alias: chackdan

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

@aL3891 I have assigned this issue to the content author to review your suggestion.
@ChackDan Please take a look and let us know what you think.

Thankyou for the feeback. We are working on this.

#please-close . This work is in our queue now.


Migrate to .NET 4.5.2

Closes #198.
This will allow me to use IReadOnlyDictionary where I need to (e.g. useful for #157).
Note that the unit test project have to use .NET 4.6.1 because of the test libraries we use. I wouldn't consider that as an issue though.

Thanks for your review.


SSKW-28 Users Management (page)

Checklist ✅

[x] I have followed the contributor guideline
[x] Tests are included
[x] Documentation is changed or added
[x] Related issue has been created
[x] Commits messages follows commit guideline

resolves #28

Testing is very limited for now.


GSoC 2019 Project Title - ProgressPlugin Refactor

Hello, This project is listed for GSoC 2019. I wanted to ask that is this project still open for contribution. I want to contribute to this project during GSoC 2020.
Project link - https://docs.google.com/document/d/19ZCaBt5UQJ45reIpCKQo_oeICpk9sPW5YjqO7ciAQh4/edit

@advaitranade It would be really appreciated if you put this question somewhere else!!
It seems like creating an issue on Webpack core isn't exactly the greatest Idea!!
Though!
If you want to contribute to this Project listed above it is all about the Proposal you make! If WebPack Joins the GSOC 2020!!

If we participate in GSoC 2020 we will work out projects for you. We haven't decided on projects yet.


Added a DSA course in hindi

What does this PR do?
Add resource(s)
For resources
Added a DSA course in hindi
Why is this valuable (or not)?
Yes
How do we know it's really free?
It is on youtube.
Checklist:

[ x] Read our contributing guidelines.
[x ] Search for duplicates.
[x ] Include author(s) and platform where appropriate.
[ x] Put lists in alphabetical order, correct spacing.
[ x] Add needed indications (PDF, access notes, under construction).
[x ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

@eshellman Please review my changes and merge my pull request.
Thank you

@eshellman I have made the changes


feat: complete nighthawk integration with meshery modules

Signed-off-by: Kush Trivedi<EMAIL_ADDRESS>Description
This PR fixes #1498
Signed commits

[x] Yes, I signed my commits.

/cc @leecalcote Finally we have got a nice little new radio button with label Nighthawk


Vendor chunk hash varies when app chunk changes

My goal is to separate the app code and the vendor code in two different chunks. This works, but my issue is that the vendor chunk changes slightly based on the content of the app chunk. If I for instance require a new file in the app chunk there are some ID's and stuff in the vendor chunk that changes and I need to check that big file into source control every time.
I would very much prefer if the vendor chunk would be consistent between builds, even if the app code changes. I'm using the OccurenceOrderPlugin but it doesn't seem to help achieving this.
Is there anything I am doing wrong, or is this currently how Webpack works by design?
My config file:
webpack({
  entry: {
    vendor: ["react", "react-router", "lodash", "jquery", "bluebird"],
    app: "app.js",
  },
  output: {
    path: paths.jsPublicDev,
    filename: "app.bundle.js",
  },
  plugins: [
    new webpack.optimize.OccurenceOrderPlugin(true),
    new webpack.optimize.CommonsChunkPlugin({
      name: "vendor",
      filename: "vendor.bundle.js",
      minChunks: Infinity,
      }),
    ],
   }
})

Apart from this, Webpack works very well for me. Thank you!

:+1:

Have you managed to find a solution to this? I have the same problem with basically the same config and haven't been able to find much information regarding it.

This bug make the common vendor pattern useless.

Duplicate of #1315. Closing.


[Feature] Hierarchy Tree Folder per Text Collection

Hey!
Firstly, thanks for your hard work on this project.
Secondly, it'd be nice to have a foldout/folder in the hierarchy tree per text collection.
In my case, I have a few collections (UI and LockMessages) and it would be nice just to have the separation to make my list a bit cleaner without having to prepend it to the key.

Wrong repo. Haha. Sorry, I been clicking around a bit.


Span context breaks when manually setting the parent

Describe the bug
When creating the span with SpanOptions MakeCurrentContext = false, and setting this span as a parent of a different span. The context option is ignored, and the span starts having more children assigned.
Steps to reproduce

Create a span with MakeCurrentContext = false
Create a second span with ParentContext set to the first span, and MakeCurrentContext to false
Create a third span without options
Observe that the third span is the child of the first span, instead of the root.

Environment

BugSnag Performance library version: 1.41
BugSnag Error Monitoring library version (if any):
Unity version: 2021.3.36
iOS/Android/macOS/Windows/browser version: irrelevant
simulator/emulator or physical device: irrelevant
Initializing bugSnag performance via a Unity GameObject or in code?: in code
Player Settings:

Scripting backend (Mono or IL2CPP): irrelevant
API compatibility level for .NET: irrelevant
Stack Trace level for all error types (None/ScriptOnly/Full): irrelevant

Fixed in 1.4.2


onDidCloseTextDocument doesn't trigger when create file and close it

import * as vscode from 'vscode';

export function activate(context: vscode.ExtensionContext) {
    vscode.workspace.onDidCreateFiles(async ({ files }) => {
        const document = await vscode.workspace.openTextDocument(files[0].fsPath);
        await vscode.window.showTextDocument(document);
    }, context.subscriptions);

    vscode.workspace.onDidCloseTextDocument((document) => {
        console.log('file path:', document.uri.fsPath);
    }, context.subscriptions);
}

export function deactivate() {}

Reproduce:

copy above code to extension.ts
debug extension
create a new file named a.txt
close a.txt

Output:

Expectd:

should output: /Users/yutengjing/code/fe-test/a-http/a.txt, but none, seems onDidCloseTextDocument of it didn't triggered
why here output file path: /Users/yutengjing/code/fe-test/a-http/a.txt.git

Versions:
Version: 1.70.0-insider (Universal)
Commit: b4d5b4ed69af953901051b1f049851b9dca3563e
Date: 2022-07-28T05:18:00.860Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 21.5.0

/duplicate
Please search for onDidCloseTextDocument

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Bot doesn't show correct info with new account

Expected Behavior
Show correct stats with a new account
Example:
2016-08-07 23:11:41,333 [       cli] [INFO] Ran for 0:15:42
2016-08-07 23:11:41,333 [       cli] [INFO] Total XP Earned: 12345  Average: 12345.00/h
2016-08-07 23:11:41,333 [       cli] [INFO] Travelled 1.23km
2016-08-07 23:11:41,333 [       cli] [INFO] Visited 123 stops
2016-08-07 23:11:41,333 [       cli] [INFO] Encountered 123 pokemon, 123 caught, 53 released, 0 evolved, 123 never seen before
2016-08-07 23:11:41,333 [       cli] [INFO] Threw 123 pokeballs
2016-08-07 23:11:41,333 [       cli] [INFO] Earned 12345 Stardust
123 values are example values, not actual ones ;)
Actual Behavior
Outputs:
2016-08-07 23:11:41,333 [       cli] [INFO] Ran for 0:15:42
2016-08-07 23:11:41,333 [       cli] [INFO] Total XP Earned: 0  Average: 0.00/h
2016-08-07 23:11:41,333 [       cli] [INFO] Travelled 0.00km
2016-08-07 23:11:41,333 [       cli] [INFO] Visited 0 stops
2016-08-07 23:11:41,333 [       cli] [INFO] Encountered 0 pokemon, 0 caught, 53 released, 0 evolved, 0 never seen before
2016-08-07 23:11:41,333 [       cli] [INFO] Threw 0 pokeballs
2016-08-07 23:11:41,333 [       cli] [INFO] Earned 0 Stardust
Steps to Reproduce

Register new account @ PTC
Edit config.json
Run bot
Quit bot

Other Information
OS: macOS 10.11
Git Commit: fc4e802dd760508e45c9e2f79cdc9704a514b896
Python Version: 2.7.12

You need to complete the tutorial in the game before your stats will work properly.

They work when I run the bot a second time


Add listening address for embedded journal

Fixes https://github.com/Alluxio/alluxio/issues/10693

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7515/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7519/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7628/
Test PASSed.

alluxio-bot, merge this please.


Pass dateFormatCalendar to MonthDropdown

resolves #849

pass dateFormatCalendar down to MonthDropdown
use the format to determine nominative or genitive display of month names

Codecov Report

Merging #858 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #858   +/-   ##
=======================================
  Coverage   85.89%   85.89%
=======================================
  Files          12       12
  Lines         645      645
  Branches      120      120
=======================================
  Hits          554      554
  Misses          7        7
  Partials       84       84

Impacted Files
Coverage Δ

src/calendar.jsx
87.71% <ø> (ø)
:arrow_up:

src/month_dropdown.jsx
87.17% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Add GhostNet

Add a new backbone GhostNet model in CVPR 2020 paper "GhostNet: More Features from Cheap Operations" (which was cited by 100+ papers in the past year). https://arxiv.org/abs/1911.11907
Pretrained model: GhostNet-1.0x with 73.9 ImageNet Top-1.

/retest

/recheck


tensorflow version 2.12

Following PR #353 the current TF dependency is hardoced to version tensorflow-cpu==2.12.0rc0,
Please update it, if possible, to the final 2.12.0 version, which was recently released.

Closed by PR #356.


Add a homebrew formula

After working out what needs to happen to support brew-based installs, you can now run the following to install it on macos. Will add support on brew for linux soon.
brew tap fubarhouse/pygmy-go && brew install pygmy-go

This will install the latest tagged release of pygmy-go.


[SE-0202] Rename Random to SystemRandomNumberGenerator

This also includes changes from: https://github.com/apple/swift/pull/17716 which lets us remove some constraints from the static methods on FixedWidthInteger.

cc: @airspeedswift

Thanks @Azoy


ADBDEV-4902-9: Fix null checks in cdbpullup_findEclassInTargetList()

Fix null checks in cdbpullup_findEclassInTargetList()
Removed extra while loop. All values of key with RelabelType kind will be
already skipped at this point by previous while loop with the same condition.
There is no point in the second one.
Added null checks in dangerous places. There is tlist_member_ignore_relabel()
and tlist_member_match_var() which have similar null checks.

Allure report https://allure-ee.adsw.io/launch/63347

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1035953

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1035954

update base brunch to 4726

Allure report https://allure-ee.adsw.io/launch/63445

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1040835

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1040836

There is tlist_member_ignore_relabel()
and tlist_member_match_var() which have similar null checks.

How does this relate to the changes in the current patch? If those functions have the same bug, can they also be fixed in this patch?

How does this relate to the changes in the current patch? If those functions have the same bug, can they also be fixed in this patch?

They are search functions too, and they are checking each entry in a targetlist similarly. They already had NULL checks, but cdbpullup_findEclassInTargetList() didn't.


Isogram has wrong test cases

https://exercism.org/tracks/ruby/exercises/isogram has some wrong test, we are testing that it is not isogram but instead of asset it is using refute!. I think refute can't be used because still we have string to compare so there is already not in the strange. It will still remain assert
Example
def test_word_with_one_duplicated_character_from_the_end_of_the_alphabet
    input = "zzyzx"
    refute Isogram.isogram?(input), "Expected false, '#{input}' is not an isogram"
  end

We are saying refute but output of this test would Expected false, '#{input}' is not an isogram so it is actually doing assert with a negative phrase. There are few more in it. so I am making a PR

We are saying refute but output of this test would Expected false, '#{input}' is not an isogram so it is actually doing assert with a negative phrase. There are few more in it. so I am making a PR

I suspect that you are misinterpreting what the second argument of the refute does.  That is a message that appears if the test does not pass, rather than what is expected.

Following is example taken from https://github.com/exercism/ruby/blob/23f3c3cd9d9c1cceafd7a6e2b5a39ffaacf20069/exercises/practice/isogram/isogram_test.rb#L23C1-L27C6
require 'minitest/autorun'

module Isogram
  ALLOWED_CHAR = [' ', '-']
  def self.isogram?(input)
    if isValid?(input)
      "Expected true, '#{input}' is an isogram"
    else
      "Expected false, '#{input}' is not an isogram"
    end
  end

  def self.isValid?(input)
    return false if input.empty? || input.nil?

    hash = Hash.new(0)
    input.each_char { |char| hash[char] += 1 unless ALLOWED_CHAR.include? char }
    hash.values.max < 2
  end
end

class IsogramTest < Minitest::Test
  def test_word_with_one_duplicated_character_from_the_end_of_the_alphabet
    input = "zzyzx"
    refute Isogram.isogram?(input), "Expected false, '#{input}' is not an isogram"
  end
end

here zzyzx is not Isogram, so message will also come "Expected false, '#{input}' is not an isogram" but if this is reply we won't refute but we will assert

Request mentoring for the exercise, this will get resolved there.
The problem is, restricted to only this issue, that the refute is checking for a "boolean" answer, but this answer is always evaluated as truth, as the only things that evaluate as false is false and nil.


Create typename variable when generating models.py

If you want to throw an already exist error, you currently do:
raise exceptions.AlreadyExists('MyOrg::Foo::Bar', model.BarId)

It would be nice if this could be:
from models import resource_type
raise exceptions.AlreadyExists(resource_type, model.BarId)

or even
raise exceptions.AlreadyExists(model)

that makes sense, we'll need the type name for metrics publishing anyway so this would be a great enhancement.
just need to find a home for it. since it's very difficult to change the type name after initialisation of the codebase, i'd be inclined to add it to handlers.py as a constant and pass it to Resource when we initialise that.


Automatically close inactive pull requests

We have quite a few PRs that are sitting unmerged / unattended way too long. This is a suggestion to eventually close them - open to discussion.

[x] Passes pre-commit run --all-files

Wonder if a happy medium for now would be marking issues/PRs as stale but not closing them automatically? This would give us some time to gauge if the automated label/comment actually revives old issues/PRs in practice, and we could presumably update the workflow retroactively if we decide we do want to automatically close them moving forward.

We already do that. They are marked with "needs attention" label. Right now we have 18 open PRs marked with that:
https://github.com/dask/dask/pulls?q=is%3Apr+label%3A"needs+attention"+is%3Aopen
Which is actually not a lot, so not many people would be affected (and upset) by this change.

I think we need to differentiate between PRs needing attention from contributors and from maintainers.
Right now we add the needs attention label automatically to prompt maintainers to look at the PR. I think closing PRs with that label automatically is a bad idea because the action is on us to review. This would be a bad contributor experience.
If we review and ask for changes then I think it would be ok to automatically close the PR if the contributor doesn't follow up.

This would be a bad contributor experience.

@jacobtomlinson - I appreciate your perspective on this (it's one I hadn't really considered). Just curious. Would it still be a bad contributor experience if the automation left a comment that was was positive and friendly? (e.g. "This PR is being closed because .... However, we are excited that you are contributing to Dask. Please re-open this PR if you are still planning to get your contribution merged.")

The main thing that leads to the bad contributor experience I'm talking about is having a PR that nobody ever looks at. I've opened PRs in the past that don't get reviewed or commented on at all and just get a stale label slapped on after 30 days and then closed after 60.

It also sucks if you open a PR, someone reviews asking for changes, you make those changes, and then it never gets looked at again and eventually gets closed by a bot.

Good point. Ideally, we would only want to close stale PRs when the last comment came from a maintainer. There doesn't seem to be an option for that with stale action.
I'm going to close this PR, but the discussion has been useful, at least to me!. Thanks to everyone who participated (@jrbourbeau @jacobtomlinson @rjzamora @charlesbluca).

Thanks for pushing this forward @j-bennet. My intent wasn't to block this PR, I agree with the intent.
Perhaps a good next step would be to create a new workflow with a separate stale action that closes PRs with the needs info label after a certain amount of time. Then update our review process so that if we request changes or follow-up information we add the needs info label.
Other considerations:

Do we need an automation to remove the needs info label if the contributor comments or pushes to the PR?
Can we have an automation that adds the needs info label if someone reviews and selects the Changes requested option?


Fix resolvers not updating properly when referencing other files.

Issue #893

Thank you for the contribution.


Add bootstrap dependency to jquery and json/ajax seeds

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

Added bootstrap as a dependency to the jquery and json/ajax challenge seeds. Closes #9957

LGTM :+1:
Thanks for contributing :tada:


What if some extractors have their own DEFAULT_OUTTMPL?

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[x] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Description of your issue, suggested solution and other information
In YoutubeDL.py in def prepare_filename(self, info_dict) in line 660
outtmpl = self.params.get('outtmpl', DEFAULT_OUTTMPL)

outtmpl does not depend on value of "extractor" key in template_dict
So outtmpl is '%(title)s-%(id)s.%(ext)s' most of the time
And it's perfectly fine
But when extractor is "Imgur", well... it would be nice to have outtmpl equal '%(playlist_title)s-%(id)s.%(ext)s'
Something like this:
            def from_extractor(default, info):
                if info["extractor"] == "Imgur":
                    return '%(playlist_title)s-%(id)s.%(ext)s'
                return default

If you run $ youtube-dl https://imgur.com/gallery/gH2YifC you will get
[download] Destination: Imgur-PMVKzz1.mp4

When I run my patched youtube-dl I get
[download] Destination: Message in a bottle-PMVKzz1.mp4

Who knows, maybe other extractors have more suitable DEFAULT_OUTTMPL as well, right?

oh and this bug too:
$ youtube-dl https://imgur.com/gallery/HvW5QyI
[imgur:gallery] HvW5QyI: Downloading JSON metadata
[download] Downloading playlist: ¯\_(ツ)_/¯
[imgur:gallery] playlist ¯\_(ツ)_/¯: Collected 1 video ids (downloading 1 of them)
[download] Downloading video 1 of 1
[Imgur] FzIfHVd: Downloading webpage
[download] Destination: ¯_(ツ)_¯-FzIfHVd.mp4
[download] 100% of 880.96KiB in 00:00
[download] Finished downloading playlist: ¯\_(ツ)_/¯

Destination should be ¯\_(ツ)_/¯-FzIfHVd.mp4  and not ¯_(ツ)_¯-FzIfHVd.mp4

oh and this bug too:
Destination should be ¯_(ツ)/¯-FzIfHVd.mp4 and not ¯(ツ)_¯-FzIfHVd.mp4

not a bug, try to create the file manually.

I got [download] Destination: ¯⧹_(ツ)_⧸¯-FzIfHVd.mp4 with this:

works for both Windows and Linux.

Duplicate of #3101.


Add ActivationControls for WPF

Hello @soldierq,
I created this to add WPF support to Activation tool.

It would be nice to also provide a sample WPF app using your new implementation.

Many thanks.


Security related issues should be sent via Email instead of creating issues here

See details at: https://github.com/casdoor/casdoor/blob/master/SECURITY.md

Hi @hsluoyz,
To avoid similar confusion in the future, I'd suggest setting up a security policy via https://github.com/casdoor/casdoor/security or adding the reporting channel to the project's readme page.

@yassineaboukir done at: https://github.com/casdoor/casdoor/pull/1192

hey @hsluoyz
I sent a security report via email and it has been some days with no reply. Can you please check on it?
thanks

Me too, I also sent a security report though email but i don't receive any reply even though several days have passed. Could you please check on it, too?
Thanks

Email is ignored, sent critical security vulnerability reproducable example and patch more than month ago, no fixes in master, no reply!
original Sep9, sent duplicate today (oct14).
@hsluoyz after which point of not answering it is considered etical to publish this publically? it's really serious concern for community having this vulnaribility is "in wild"!


rpcbind: Patch for CVE-2017-8779

Motivation for this change
Part of vulnerability roundup https://github.com/NixOS/nixpkgs/issues/32117
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Backported to 17.09 in https://github.com/NixOS/nixpkgs/commit/bc54631f4dcb3abfd9b8ecac76807bd9ff103b97


Charger charges too fast in solar mode

Describe the bug
When I plug in my car, it starts to load with around 10kw and normally it should go down to around 4kw, but this does not happen most of the time. It works, when I plug out from one car and plug in into another car. But if the charger was plugged out for too long and then I plug in it fails to get to 4kw.
What also helps is to switch from Solar to Fast mode and then back to Solar. Then it easily changes the charging speed.
I had a discussion https://github.com/evcc-io/evcc/discussions/13888 where I got the hint to write an issue.
evcc-20240516-161251-debug (1).log
Steps to reproduce

Leave wallbox unplugged for a while, have enough SoC in battery for battery-supported charging
Plug-in cable
Charging starts with over 9kw and does not go down

Configuration details
# open evcc at http://evcc.local:7070
network:
  schema: http
  host: manpi.local # .local suffix announces the hostname on MDNS
  port: 7070

log: debug
levels:
  etrel: trace
#  cache: error

# unique installation id
plant: *****

interval: 60s # control cycle interval

sponsortoken: *****

# sponsors can set telemetry: true to enable anonymous data aggregation
# see https://github.com/evcc-io/evcc/discussions/4554
telemetry: false

meters:
  - type: template
    template: sonnenbatterie
    usage: grid
    host: <IP_ADDRESS>
    port: 8080
    name: grid1
  - type: template
    template: sonnenbatterie
    usage: pv
    host: <IP_ADDRESS>
    port: 8080
    name: pv2
  - type: template
    template: sonnenbatterie
    usage: battery
    token: *****
    host: <IP_ADDRESS>
    port: 8080
    name: battery3

vehicles:
  - name: ev4
    type: template
    template: hyundai
    title: IONIQ5
    user: *****
    password: *****
    vin: *****
    capacity: 70
    language: de
    mode: pv
  - name: ev5
    type: template
    template: bmw
    title: BMW iX3
    user: *****
    password: *****
    vin: *****
    capacity: 74
    mode: pv

chargers:
  - type: template
    template: etrel
    host: <IP_ADDRESS>
    port: 502
    name: wallbox6

loadpoints:
  - title: Carport
    charger: wallbox6
    mode: now

site:
  title: Zuhause
  residualPower: 100
  meters:
    grid: grid1
    pv:
      - pv2
    battery:
      - battery3

tariffs:
  currency: EUR # (default EUR)
  grid:
    type: tibber
    token: *****
  co2:
    type: grünstromindex
    zip: 50354

influx:
  url: http://localhost:8086
  database: evcc_log
  token: *****
  org: home

Log details
[site  ] DEBUG 2024/05/16 16:05:52 ----
[lp-1  ] DEBUG 2024/05/16 16:05:52 charge power: 0W
[lp-1  ] DEBUG 2024/05/16 16:05:52 charge currents: [0 0 0]A
[site  ] DEBUG 2024/05/16 16:05:52 pv power: 1637W
[site  ] DEBUG 2024/05/16 16:05:52 battery soc: 79%
[site  ] DEBUG 2024/05/16 16:05:52 battery power: -1234W
[site  ] DEBUG 2024/05/16 16:05:52 grid meter: -44W
[site  ] DEBUG 2024/05/16 16:05:52 site power: -1178W
[lp-1  ] DEBUG 2024/05/16 16:05:52 charger status: A
[site  ] DEBUG 2024/05/16 16:06:02 ----
[lp-1  ] DEBUG 2024/05/16 16:06:02 charge power: 320W
[lp-1  ] DEBUG 2024/05/16 16:06:02 charge currents: [0.944 0.768 0.752]A
[site  ] DEBUG 2024/05/16 16:06:02 pv power: 1662W
[site  ] DEBUG 2024/05/16 16:06:02 battery soc: 79%
[site  ] DEBUG 2024/05/16 16:06:02 battery power: -1229W
[site  ] DEBUG 2024/05/16 16:06:02 grid meter: 14W
[site  ] DEBUG 2024/05/16 16:06:02 site power: -1115W
[lp-1  ] DEBUG 2024/05/16 16:06:02 charger status: C
[lp-1  ] INFO 2024/05/16 16:06:02 car connected
[lp-1  ] DEBUG 2024/05/16 16:06:02 vehicle api refresh
[lp-1  ] DEBUG 2024/05/16 16:06:02 pv timer elapse
[lp-1  ] DEBUG 2024/05/16 16:06:02 pv timer inactive
[lp-1  ] INFO 2024/05/16 16:06:02 start charging ->
[lp-1  ] DEBUG 2024/05/16 16:06:02 wake-up timer: stop
[main  ] DEBUG 2024/05/16 16:06:21 vehicle status: A (IONIQ5)
[main  ] DEBUG 2024/05/16 16:06:23 vehicle status: C (BMW iX3)
[lp-1  ] INFO 2024/05/16 16:06:23 vehicle updated: unknown -> BMW iX3
[lp-1  ] DEBUG 2024/05/16 16:06:23 vehicle status: C
[lp-1  ] DEBUG 2024/05/16 16:06:23 vehicle soc: 74%
[lp-1  ] DEBUG 2024/05/16 16:06:23 vehicle range: 259km
[lp-1  ] WARN 2024/05/16 16:06:23 charger out of sync: expected disabled, got enabled
[lp-1  ] DEBUG 2024/05/16 16:06:23 charger enable
[lp-1  ] DEBUG 2024/05/16 16:06:23 pv charge current: 4.56A = 2.94A + 1.62A (-1115W @ 3p)
[site  ] DEBUG 2024/05/16 16:06:23 ----
[lp-1  ] DEBUG 2024/05/16 16:06:23 charge power: 9920W
[lp-1  ] DEBUG 2024/05/16 16:06:23 charge currents: [15.2 14.7 14.9]A
[site  ] DEBUG 2024/05/16 16:06:23 pv power: 1698W
[site  ] DEBUG 2024/05/16 16:06:23 battery soc: 79%
[site  ] DEBUG 2024/05/16 16:06:23 battery power: 4540W
[site  ] DEBUG 2024/05/16 16:06:23 grid meter: 4450W
[site  ] DEBUG 2024/05/16 16:06:23 site power: 9090W
[lp-1  ] DEBUG 2024/05/16 16:06:23 vehicle odometer: 7598km
[lp-1  ] DEBUG 2024/05/16 16:06:23 detected active phases: 3p
[lp-1  ] DEBUG 2024/05/16 16:06:23 charger status: C
[lp-1  ] DEBUG 2024/05/16 16:06:23 soc estimated: 74.07% (vehicle: 74.00%)
[lp-1  ] DEBUG 2024/05/16 16:06:23 vehicle soc: 74%
[lp-1  ] DEBUG 2024/05/16 16:06:23 vehicle range: 259km
[lp-1  ] DEBUG 2024/05/16 16:06:23 pv charge current: 0A = 6A + -13.2A (9090W @ 3p)
[site  ] DEBUG 2024/05/16 16:06:32 ----
…
now switching to mode now and back to pv:
…
[site  ] DEBUG 2024/05/16 16:12:12 ----
[lp-1  ] DEBUG 2024/05/16 16:12:12 charge power: 9984W
[lp-1  ] DEBUG 2024/05/16 16:12:12 charge currents: [15.1 14.7 15]A
[site  ] DEBUG 2024/05/16 16:12:12 pv power: 4204W
[site  ] DEBUG 2024/05/16 16:12:12 battery soc: 74%
[site  ] DEBUG 2024/05/16 16:12:12 battery power: 4525W
[site  ] DEBUG 2024/05/16 16:12:12 grid meter: 1883W
[site  ] DEBUG 2024/05/16 16:12:12 site power: 6508W
[lp-1  ] DEBUG 2024/05/16 16:12:12 detected active phases: 3p
[lp-1  ] DEBUG 2024/05/16 16:12:12 charger status: C
[lp-1  ] DEBUG 2024/05/16 16:12:12 soc estimated: 75.24% (vehicle: 74.00%)
[lp-1  ] DEBUG 2024/05/16 16:12:12 vehicle soc: 75%
[lp-1  ] DEBUG 2024/05/16 16:12:12 vehicle range: 259km
[lp-1  ] DEBUG 2024/05/16 16:12:12 pv charge current: 0A = 6A + -9.43A (6508W @ 3p)
[lp-1  ] DEBUG 2024/05/16 16:12:13 set charge mode: now
[site  ] DEBUG 2024/05/16 16:12:13 ----
[lp-1  ] DEBUG 2024/05/16 16:12:13 charge power: 9984W
[lp-1  ] DEBUG 2024/05/16 16:12:13 charge currents: [15.1 14.7 15]A
[site  ] DEBUG 2024/05/16 16:12:13 pv power: 4212W
[site  ] DEBUG 2024/05/16 16:12:14 battery soc: 74%
[site  ] DEBUG 2024/05/16 16:12:14 battery power: 4520W
[site  ] DEBUG 2024/05/16 16:12:14 grid meter: 1896W
[site  ] DEBUG 2024/05/16 16:12:14 site power: 6516W
[lp-1  ] DEBUG 2024/05/16 16:12:14 detected active phases: 3p
[lp-1  ] DEBUG 2024/05/16 16:12:14 charger status: C
[lp-1  ] DEBUG 2024/05/16 16:12:14 soc estimated: 75.25% (vehicle: 74.00%)
[lp-1  ] DEBUG 2024/05/16 16:12:14 vehicle soc: 75%
[lp-1  ] DEBUG 2024/05/16 16:12:14 vehicle range: 259km
[lp-1  ] DEBUG 2024/05/16 16:12:14 max charge current: 16A
[site  ] DEBUG 2024/05/16 16:12:14 set battery mode: hold
[site  ] DEBUG 2024/05/16 16:12:22 ----
[lp-1  ] DEBUG 2024/05/16 16:12:22 charge power: 9920W
[lp-1  ] DEBUG 2024/05/16 16:12:22 charge currents: [15.2 14.7 14.9]A
[site  ] DEBUG 2024/05/16 16:12:22 pv power: 4253W
[site  ] DEBUG 2024/05/16 16:12:22 battery soc: 74%
[site  ] DEBUG 2024/05/16 16:12:22 battery power: -2W
[site  ] DEBUG 2024/05/16 16:12:22 grid meter: 6326W
[site  ] DEBUG 2024/05/16 16:12:22 site power: 6424W
[lp-1  ] DEBUG 2024/05/16 16:12:22 detected active phases: 3p
[lp-1  ] DEBUG 2024/05/16 16:12:22 charger status: C
[lp-1  ] DEBUG 2024/05/16 16:12:22 soc estimated: 75.28% (vehicle: 74.00%)
[lp-1  ] DEBUG 2024/05/16 16:12:22 vehicle soc: 75%
[lp-1  ] DEBUG 2024/05/16 16:12:22 vehicle range: 259km
[lp-1  ] DEBUG 2024/05/16 16:12:24 set charge mode: pv
[site  ] DEBUG 2024/05/16 16:12:24 ----
[lp-1  ] DEBUG 2024/05/16 16:12:24 charge power: 9984W
[lp-1  ] DEBUG 2024/05/16 16:12:24 charge currents: [15.2 14.7 14.9]A
[site  ] DEBUG 2024/05/16 16:12:24 pv power: 4270W
[site  ] DEBUG 2024/05/16 16:12:24 battery soc: 74%
[site  ] DEBUG 2024/05/16 16:12:24 battery power: -2W
[site  ] DEBUG 2024/05/16 16:12:24 grid meter: 6354W
[site  ] DEBUG 2024/05/16 16:12:24 site power: 6452W
[lp-1  ] DEBUG 2024/05/16 16:12:24 detected active phases: 3p
[lp-1  ] DEBUG 2024/05/16 16:12:24 charger status: C
[lp-1  ] DEBUG 2024/05/16 16:12:24 soc estimated: 75.28% (vehicle: 74.00%)
[lp-1  ] DEBUG 2024/05/16 16:12:24 vehicle soc: 75%
[lp-1  ] DEBUG 2024/05/16 16:12:24 vehicle range: 259km
[lp-1  ] DEBUG 2024/05/16 16:12:24 pv charge current: 6.65A = 16A + -9.35A (6452W @ 3p)
[lp-1  ] DEBUG 2024/05/16 16:12:24 max charge current: 6.65A
[site  ] DEBUG 2024/05/16 16:12:25 set battery mode: normal
[site  ] DEBUG 2024/05/16 16:12:32 ----
[lp-1  ] DEBUG 2024/05/16 16:12:32 charge power: 3648W
[lp-1  ] DEBUG 2024/05/16 16:12:32 charge currents: [5.65 5.33 5.58]A
[site  ] DEBUG 2024/05/16 16:12:32 pv power: 3926W
[site  ] DEBUG 2024/05/16 16:12:32 battery soc: 74%
[site  ] DEBUG 2024/05/16 16:12:32 battery power: -1W
[site  ] DEBUG 2024/05/16 16:12:32 grid meter: 187W
[site  ] DEBUG 2024/05/16 16:12:32 site power: 286W
[lp-1  ] DEBUG 2024/05/16 16:12:32 detected active phases: 3p
[lp-1  ] DEBUG 2024/05/16 16:12:32 charger status: C
[lp-1  ] DEBUG 2024/05/16 16:12:32 soc estimated: 75.29% (vehicle: 74.00%)
[lp-1  ] DEBUG 2024/05/16 16:12:32 vehicle soc: 75%
[lp-1  ] DEBUG 2024/05/16 16:12:32 vehicle range: 259km
[lp-1  ] DEBUG 2024/05/16 16:12:32 pv charge current: 6.23A = 6.65A + -0.414A (286W @ 3p)
[lp-1  ] DEBUG 2024/05/16 16:12:32 max charge current: 6.23A
[site  ] DEBUG 2024/05/16 16:12:42 ----
[lp-1  ] DEBUG 2024/05/16 16:12:42 charge power: 3776W
[lp-1  ] DEBUG 2024/05/16 16:12:42 charge currents: [5.79 5.49 5.71]A
[site  ] DEBUG 2024/05/16 16:12:42 pv power: 3623W
[site  ] DEBUG 2024/05/16 16:12:42 battery soc: 74%
[site  ] DEBUG 2024/05/16 16:12:42 battery power: -2W
[site  ] DEBUG 2024/05/16 16:12:42 grid meter: 684W
[site  ] DEBUG 2024/05/16 16:12:42 site power: 782W
[lp-1  ] DEBUG 2024/05/16 16:12:42 detected active phases: 3p
[lp-1  ] DEBUG 2024/05/16 16:12:42 charger status: C
[lp-1  ] DEBUG 2024/05/16 16:12:42 soc estimated: 75.31% (vehicle: 74.00%)
[lp-1  ] DEBUG 2024/05/16 16:12:42 vehicle soc: 75%
[lp-1  ] DEBUG 2024/05/16 16:12:42 vehicle range: 259km
[lp-1  ] DEBUG 2024/05/16 16:12:42 pv charge current: 5.1A = 6.23A + -1.13A (782W @ 3p)
[lp-1  ] DEBUG 2024/05/16 16:12:42 max charge current: 6A

What type of operating system are you running?
Linux
Version
0.126.4

Ich war in die Diskussion involviert.
Die Box fängt nach dem Anstecken eigenmächtig an mit voller Leistung zu laden.
Dann kommt charger enable und weil bufferSoc überschritten ist, wird weitergeladen.
evcc denkt es wird mit 6A geladen und greift nicht weiter ein.
Wenn der Hausspeicher noch ziemlich leer ist, wird direkt wieder ausgeschaltet. Die Steuerung an sich funktioniert also.
MMn fehlt in Zusammenhang mit dem eigenmächtigen Start und charger enable noch ein max charge current: 6A.

loadpoints:
  - title: Carport
    charger: wallbox6
    mode: now

Die Vorgabe ist ja auch hierdurch sofort mit voller Leistung zu laden.

Ja, das war ein Versuch.  Dann hatte ich das mit off getestet und dann noch mit now.  Da stimmt doch schon was nicht???

 Warum ist aus dem Log nicht klar- da müsste man wohl mit dem Debugger rein schauen.
Besteht das Problem denn immer oder nur manchmal?

bufferSoc ist überschritten.
Wenn der Speicher "leer" ist, funktioniert das abschalten.
https://github.com/evcc-io/evcc/discussions/13888#discussioncomment-9590025

@VolkerK62 Du bist ein Schatz! Siehe https://github.com/evcc-io/evcc/pull/14126 um das im Log klarer zu machen, zumal wir auch den bufferSoc sonst nicht mit loggen...

Löst aber das Problem nicht.

Die Box fängt nach dem Anstecken eigenmächtig an mit voller Leistung zu laden. Dann kommt charger enable und weil bufferSoc überschritten ist, wird weitergeladen. evcc denkt es wird mit 6A geladen und greift nicht weiter ein. Wenn der Hausspeicher noch ziemlich leer ist, wird direkt wieder ausgeschaltet. Die Steuerung an sich funktioniert also. MMn fehlt in Zusammenhang mit dem eigenmächtigen Start und charger enable noch ein max charge current: 6A.

Bin nicht sicher- aber kann doch einfach morgen im nightly ausprobiert werden!

Ok dann logge ich das mal mit dem Nightly

Na mega, jetzt funktioniert es! Lag das an der Änderung in der if-condition?
evcc-nightly-filtered.log

Sieht so aus als wäre es ein Zufall, dass es geklappt hat oder ich hab was Neues entdeckt evcc-20240604-1527-trace-filtered.log
Klappt wieder nicht :/

Zusätzlicher Datenpunkt von mir:
2024-06-05 Log-Auszug.txt
evcc setzt den Ladestrom um 11:03:26 auf 9A hoch, um 11:03:46 ist das sichtbar.
Um 11:04:47 wird versucht, ihn wieder auf 6A herunterzusetzen, das klappt aber offenbar nicht. Es wird aber auch kein Fehler protokolliert.
 Damit beziehen sich alle weiteren Berechnungen auf einen zu kleinen Wert, und wenn der schon das Minimum 6A ist, sieht nie die Notwendigkeit, noch weiter runterzugehen. Erst ein erneutes Hochschalten des Ladestrom wenn mehr Sonne da ist bringt die Logik wieder ans Laufen, weil lp.chargeCurrent dann wieder auf einen höheren Wert gesetzt wird.
Evtl. würde ein Debug-Logging auch in setLimit() weiter helfen? Problem scheint ja zu sein, dass der Charger auf den Befehl nicht reagiert. Bei mir ein Hardy Barth eCharge ePH1-2T22.

@andig Irgendwas stimmt da immer noch nicht.
evcc-20240611-182110-trace-filtered.log
Um 17:46 ging's los, der Charger startet wie immer von alleine. Dann wurde das Auto erkannt und auf PV mode gewechselt, aber die Ladegeschwindigkeit bleibt bei 9k...

Damit wir es nicht doppelt machen: es gib schon eine Discussion dazu. 1x reicht.


Can not find the module of calculating importance

after reading code，i can not find the module of calculating importance.
ps: if i missed it, please tell me where it is.thank u very much
(I'm a beginner, so please allow me to express my sincerest apologies for any offense)

have found it


fix python bindings

Change module names in init.py

Oh, this might have got corrupted in rebase. Thanks for fixing it.


Type: investigate support for HF safetensor

this won't be needed. It is easy to do safetensor -> torch tensor -> DocArray therefore no need to have safetensor specific for now.


PP-646 remove unneeded files

these are causing problems for the demo service, jquery is already on the page

Will sample-integration work on its own without these files?

@ijmad yes, jquery is already included and there is no JavaScript


Upload Llama Unlearning Checkpoints

I would like to use the Llama model for evaluation. I see you put the metrics for models finetuned on various splits of the data in the data directory. I also see you uploaded the model finetuned on the entire dataset for Llama, but not ones with unlearning performed on it like you did for Phi. It would be great to have access to those for baselines since I am running into some architecture limitations for running the forget script.

Thank you! I have a deadline coming up. If there is any way to upload these soon, I would really appreciate. By the new year would be great if at all possible :)

@shariqahn I will try my best. Uploading every checkpoint for every unlearning method might take a while. Is there a setting that you want us to prioritize?

Preference is the forget10 setting with whatever models are quickest to upload. Appreciate it!


Dropdown Styling issue

Super small issue with the new style changes. Looks like the icon in the select field is slightly off.

Might be a browser-specific issue; what's this in?

Might be a browser-specific issue; what's this in?

Ha, I asked him the same thing :)
In Firefox, I'm getting a gray select:

That's solved by just putting bg-white on the select.
In Chrome, I'm not seeing any issues.

In #2434 I've added just that to the select field as I noticed it was missing a bg color, likely after the removal of the forms plugin, so that will fix the gray select issue (and possibly this issue, if related).

Was fixed in https://github.com/tinacms/tinacms/pull/2434


Generate JSON badges without using a template [*****]

Started this as a warm-up for #2428, so it would be great to get it merged quickly if possible.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against 96d77cb341a1cca903f6b31d105dcb46c2048197

Remaining failures seem to be unrelated.

Remaining failures seem to be unrelated.

The tests failing on label mismatches on the GitHub badges has me a bit puzzled 🤔

The tests failing on label mismatches on the GitHub badges has me a bit puzzled 🤔

We probably could try to improve the error messages our test helper is generating. I think what's happening is that we're getting something like issues | inaccessible.

I think what's happening is that we're getting something like issues | inaccessible.

I think you're right.

Thanks for reviewing!


Update the wording for billing FAQ

to be consistent with the billing page https://azure.microsoft.com/en-us/pricing/details/app-configuration/.

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

Add @AlexandraKemperMS for reviewing

#sign-off

@zhenlan: I'm sorry - only the author of this article, @lisaguthrie, 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.


MM-36912 - Checklist header, collapsible, with progress bar

Summary

New checklist header. It:

is collapsible (decided to add that in this PR, but not "save state per user"--that's another PR)
ellipsizes the title
shows number of tasks completed / total
has progress bar
has add task on hover; background changes on hover
colors slightly darken on hover to indicate clickable
makes crescent-shaped ice cubes
babysits your kids

Try it out

Looks like:

Ticket Link

https://mattermost.atlassian.net/browse/MM-36912

Checklist

[ ] Telemetry updated
[ ] Gated by experimental feature flag
[x] Unit tests updated

This looks really slick! Looping @calebroseland in to review this one.