[FEATURE] wash up / wash start host

Bring back wash up! A previous supported command in 0.18.0 that would launch a host in the integrated REPL. Though we've found that the REPL isn't the best experience for running a wasmCloud host, it would be great to have this command back again for a simple experience to start a host.
In tandem with #264, the first experience a developer would have with wasmcloud is

Look at documentation
Download wash for their respective OS/ARCH
Run wash install
Run wash up
Proceed with the example documentation

There are some edge cases to look out for, namely that we are going to either require that NATS is installed or accessible by the host.

Would wash up start NATS automatically if it isn't running?

Would wash up start NATS automatically if it isn't running?

I think that would be the best experience, we can always warn level log that we're starting NATS for the user. The balance is just between optimizing the initial developer experience and making sure that advanced use cases don't end up launching NATS accidentally when trying to connect to a remote cluster. For that use case, we should just check and see if the NATS connection succeeds to the URL and launch if not. If it's an issue then we could add a --dont-launch-nats-please-and-error-out flag 😄

Would wash up start NATS automatically if it isn't running?

I think that would be the best experience, we can always warn level log that we're starting NATS for the user. The balance is just between optimizing the initial developer experience and making sure that advanced use cases don't end up launching NATS accidentally when trying to connect to a remote cluster. For that use case, we should just check and see if the NATS connection succeeds to the URL and launch if not. If it's an issue then we could add a --dont-launch-nats-please-and-error-out flag 😄

Yeah I agree that's definitely the best UX experience. Is our eventual goal to get to a place where the average user doesn't care about NATS at all / doesn't need to know about it? That's what I was thinking anyway.

Is our eventual goal to get to a place where the average user doesn't care about NATS at all / doesn't need to know about it?

For the first 50% of using wasmCloud, yes! The user should get right down to writing some business logic and playing with wasmCloud. As soon as they get to deploying to prod and all they will have to think about NATS, but wash is all about making it easy to develop and get started


Can not get whole moment object

Hi, I am currently developing one chrome browser extension and I am using moment.js.
My problem is, when I set the object property to chrome.storage with Chrome API as moment object, when I want to retrieve it, it comes without _d property and I can not get DateTime from it. Check it out.
`let now = moment();
let endDate = moment().add(30, 'days');
console.log("Now ", now);
console.log('Enddate ', endDate);

chrome.storage.local.set({
  startDate: now,
  endDate: endDate,
  remainingCredits: 20,
}, () => {
  chrome.storage.local.get(null, (result) => {
    console.log("Now after", result.startDate);
    console.log("Enddate after", result.endDate);
    resolve(result);
  });
});`

Have you tried just storing the moment dates as strings, then converting them back to moment objects when you retrieve the data? Example:
let now = moment();
let endDate = moment().add(30, 'days');

chrome.storage.local.set({
  startDate: now.toString(),
  endDate: endDate.toString(),
}, () => {
  chrome.storage.local.get(null, (result) => {
    console.log("Now after", moment(result.startDate));
    console.log("Enddate after", moment(result.endDate));
    resolve(result);
  });
});`

I'd avoid toString().  Use toJSON() or toISOString() to store as a string, or valueOf() to store as unix timestamp in milliseconds.

Please re-open if you still have issues.


refactor: use <cWORD> instead of <cword>

To capture special characters such as ===.
Fixes #10

Closing because of other issues.


GEOMESA-848 Density iterator for z3 index

Includes performance improvements in non-z3 density queries

Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

Committed as 67aaba597a4a35cf864a47d83951f5ff88baba60 on master.


Throw exception when part is accessed that is not requested

Proposed Changes

(Describe the changes and rationale behind them)

Related Issues

(Github link to related issues or pull requests)

Codecov Report

Merging #59 (83db9d6) into main (0449843) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #59   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          325       362   +37
  Branches        42        49    +7
=========================================
+ Hits           325       362   +37

Impacted Files
Coverage Δ

src/youtubeaio/models.py
100.00% <100.00%> (ø)

src/youtubeaio/types.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Large balances don't render correctly

What did you do?
Loaded an account with a large balance (>=1000XLM)
What did you expect to see?
Your balance:
1000.0000000

What did you see instead?
Your balance:
.

It looks like this began after #95 was merged, something about the formatting seems to break it

Do I understand correct? stellar account can carry only a few lumens now to be transfer by Ledger nano S?

There was a bug related to the balance being show, the balance on the account managed by the Ledger Nano was not affected.


Fix stack buffer overflow in addrlib2

Make sure we do not write past the end of fix-sized arrays.
Validate the number of mip levels during image creation.

@RobMartin-AMD @JakeMerdichAMD PTAL

Test summary for commit 0d05ec301620b75ac01ef55a34f78a065b62936c
CTS tests (Failed: 0/186371)Built with version <IP_ADDRESS>
Rhel 8.2, Gfx10
Passed: 36631/65208 (56.2%)
Failed: 0/65208 (0.0%)
Not Supported: 28577/65208 (43.8%)Warnings: 0/65208 (0.0%)

Ubuntu 18.04, Gfx9
Passed: 29989/55953 (53.6%)
Failed: 0/55953 (0.0%)
Not Supported: 25964/55953 (46.4%)Warnings: 0/55953 (0.0%)

Ubuntu 20.04, Gfx8
Passed: 38930/65210 (59.7%)
Failed: 0/65210 (0.0%)
Not Supported: 26280/65210 (40.3%)Warnings: 0/65210 (0.0%)

Ping

Is an application attempting to create an image with too many mipmap levels?

Exactly. This is difficult to debug because of this memory corruption, which manifests later in other code inside LLPC that misbehaves

Exactly. This is difficult to debug because of this memory corruption, which manifests later in other code inside LLPC

Interesting... I looked through the code and saw that the only places we get into this function are during the set-up for certain blits and copies.   Shouldn't the invalid Image have been rejected at creation time?  (I.e., Pal::IDevice::CreateImage)

Sorry for the radio silence, but I've been really busy with other things recently and haven't had a chance to look at this further.  I'll try to correct that this week.

I traced another stack buffer overflow in AddrMgr2::InitSubresourcesForImag, which has another fixed-sized array: ADDR2_MIP_INFO mipInfo[MaxImageMipLevels] = { }. It's possible to catch in Image::Init by checking m_createInfo.mipLevels > 16. It seems to me like a reasonable place for a check if we can expose MaxMipLevels from addrlib2 there. What do you think?

I think if you move the definition of MaxImageMipLevels from addrMgr2.cpp to image.h, you could put the validation into Image::ValidateCreateInfo().

Thanks for the feedback, @RobMartin-AMD. I moved validation to Image::ValidateCreateInfo and added assertions to each function with a fixed-sized array, which should tell us if the validation is sufficient or not.

Test summary for commit 4721982c94ab40144a54d4bd48246bf588a88b14
CTS tests (Failed: 1/167905)Built with version <IP_ADDRESS>
Rhel 8.2, Gfx10
Passed: 35765/63748 (56.1%)
Failed: 0/63748 (0.0%)
Not Supported: 27983/63748 (43.9%)Warnings: 0/63748 (0.0%)

Ubuntu 18.04, Gfx9
Passed: 24745/40407 (61.2%)
Failed: 1/40407 (0.0%)
Failures:
FAILURE: dEQP-VK.subgroups.quad.graphics.subgroupquadswapvertical_i16vec2
Stack trace: Script:
Crash

Not Supported: 15661/40407 (38.8%)Warnings: 0/40407 (0.0%)

Ubuntu 20.04, Gfx8
Passed: 38010/63750 (59.6%)
Failed: 0/63750 (0.0%)
Not Supported: 25740/63750 (40.4%)Warnings: 0/63750 (0.0%)

retest this please

Test summary for commit 4721982c94ab40144a54d4bd48246bf588a88b14
CTS tests (Failed: 0/179976)Built with version <IP_ADDRESS>
Rhel 8.2, Gfx10
Passed: 35765/63748 (56.1%)
Failed: 0/63748 (0.0%)
Not Supported: 27983/63748 (43.9%)Warnings: 0/63748 (0.0%)

Ubuntu 18.04, Gfx9
Passed: 27857/52478 (53.1%)
Failed: 0/52478 (0.0%)
Not Supported: 24621/52478 (46.9%)Warnings: 0/52478 (0.0%)

Ubuntu 20.04, Gfx8
Passed: 38010/63750 (59.6%)
Failed: 0/63750 (0.0%)
Not Supported: 25740/63750 (40.4%)Warnings: 0/63750 (0.0%)

@WenqingLiAMD @JaxLinAMD @amdrexu Could you merge this please?


Constructor support.

Please correct me if I'm wrong, but looks like we don't support constructor yet?

Yep, that's right. I'm not sure what calling convention do compilers use for constructors, and similar, so right now they aren't parsed.
I haven't (nor plan in the short term) tried to figure out a way to call a C++ constructor from rust directly. Hopefully they use something like placement new under the hood and we can call them, but...

Was this implemented with #332?

Right.


📃 Fix description for parameter "generate_during_eval" in dpo_config

What does this PR do?
The description of the "generate_during_eval" parameter is incorrectly that of "truncation_mode" in the DPO config.
I aligned it with other similar trainer configs such as BCO or KTO.
Before submitting

[x] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a GitHub issue? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

Thanks!

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


[HOLD] GH1053: Adds ability to download scripts as nuget packages

Conversations from the first pull request can be found here https://github.com/cake-build/cake/pull/1070

Hi @robgha01, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, DNFBOT;

@robgha01 good work on getting the feature branch created.
The errors that you are seeing are with regard to the Unit Tests that are executed on each build of the project.  Looks like the changes that you have made have broken some of those Unit Tests.  These would need to be corrected.

Relates to #1053

@gep13 i will see what i can. :)

@gep13 the result in ScriptRunner.cs line 125 when i debug the test this returns null and it wont go into the method that i created Analyze(scriptPath.GetFilename(), out scriptAnalyzerContext)
do i have to implament that method in the test somewere ?

@gep13 nvm i found it :)

@gep13 Should_Throw_If_Path_Contains_Illegal_Characters() in PathTest.cs line 92
throws error saying it contains illigal characters i have not modified anyting in path io in the core what i can remember how do i fix this unit test ? do i need to update someting from the dev brance to the fethure brance ?

@gep13 nvm, i downloaded a clone of dev and it seams it throws even there so its not my code anyway i fixed the other tests that failed related the my code :)
So what do i do know i guess i should ignore the other failures of the test that throws even in the main dev brance as its not related to this feture ?

Im going to play around a bit with modularity of the processor and script runner etc.

I have modified some things to make it possible for modulared processors i have added ProcessorValues it handles the actuall data for a processor ex: insteed of doing
IList<PackageReference> Tools in ScriptInformation.cs one can use the new
ProcessorValues ProcessorValues object to store its value it has one add method that looks like this:
Add(ILineProcessor key, object value) meaning if i create a processor i only have to do this
public sealed class LoadRemoteProcessor : UriDirectiveProcessor
    {
        private readonly ICakeComponentFactory _componentFactory;

        public LoadRemoteProcessor(ICakeEnvironment environment) : base(environment)
        {
            _componentFactory = new CakeComponentFactory();
        }

        protected override string GetDirectiveName()
        {
            return Constants.DirectiveName;
        }

        protected override void AddToContext(IScriptAnalyzerContext context, Uri uri)
        {
            var package = _componentFactory.CreatePackageReference(uri);
            **context.Script.ProcessorValues.Add(this, package);**
        }
    }

and it will save the value im not complitly done yet but later on this object will be used to resolve the actuall objects that a processor needs to process so for example the method in ScriptRunner.cs
_processor.InstallTools(result, toolsPath); can take its values from the ProcessorValues insteed, the tools is a core thing i took it as a example what i want to say is this opens up for external processors and script runner installers to work outside of the core but it will work with the core. open the world for extensions xD

@robgha01 as you will see from the below, all our CI servers are currently failing.  Before being able to look at this properly, we would need to have all of those builds passing.  Does this build correctly for you locally in Visual Studio, in both Debug/Release Configuration?

@gep13 yes thay build with no errors in both debug and release.

@gep13 im going through the unit tests that fails will update shortly.

@gep13  I fixed the unit tests related the the PR the other thors in the main dev brance here is the debug files i use for tests https://1drv.ms/u/s!AvOXr9f-QF0pwGl_A-7MsCvFonEo

@gep13 im done with the code but im going to build some modularity for PackageType its a enum but its only viable in the core and now im using NugetScript as a value im going to add a new method that takes in a fileExtension this way processor modules that want to use the installer can pass in a file extension insteed of a PackageType.

@gep13 ok that is done, with this change i can move the dependency code on enum value PackageType nuget script to my written module insteed of the enum i route the logic through a string called fileExtension now i can finaly use json.net for the config file :dancers:
I think everyting is now moved out of the core cake and the modularity sould be finished if you do howerver find anyting that need modularity just give me a shot and il look into it it dose not have to be related to this PR :) i love to refactor and make code esey and better.

Cake.LoadRemote.Module is moved to my github repo here https://github.com/robgha01/Cake.Modules

When this is introduced it would be nice for an additional section in cakebuild.net that lists all modules :)

@robgha01 yes, I had had the same thought. Haven't discussed that with the rest of the team yet though.

@gep13 ok :)

@gep13 Hey, i'm just checking in for some status on what is going on have anyone had time to look at this yet ?

@robgha01 we haven't forgotten about it.  The @cake-build/team are all busy with the port of Cake to the CoreClr, which is a reasonably large undertaking, and as a result we are not prioritizing larger Pull Requests just now, as mentioned here: http://cakebuild.net/blog/2016/07/cake-v0-15-0-released

@gep13 ok, thancks for the fast status report :)

Hey @gep13 how is it going and what is the status on this pull ?

I'm very interested in this feature, would be glad if going to be merged and released soon... Thanks

I'm not 100% sure what I'm doing but it seems to work with Cake 0.17.0
By using those two lines you can load Cake scripts from a NuGet package.
#tool nuget:?package=SomeId.BuildScripts.Cake&include=*.cake
#load "tools\SomeId.BuildScripts.Cake\SomethingInThePackage.cake"

The ugly thing is you have to replicate the tools path but as a workaround it might be ok...

When the line preprocessor would come after the tool processor (Cake.Core.Scripting.Analysis.ScriptAnalyzer) it would be possible to have such a workaround:
#tool nuget:?package=SomeId.BuildScripts.Cake&include=*.cake
#load tools\SomeId.BuildScripts.Cake\Defaults.cake

But unfortunately this is not...
Does anybody know any other workaround which works with Cake 0.17?

@Sam13 currently there's no good work around, you could have an tools.cake with all tools that you execute before build.cake, or add your script nuget package to package.config.

@robgha01 sorry for taking so long to get back to you about this.  Put simply, other items were on my todo list, with a higher priority.
I have now had time to sit down again and look at this PR, and as I mentioned during the creation of this PR, I was considered that too many parts of the internals of Cake were changing, and as a result, there was a chance that this PR would not be pulled it.  Unfortunately, this is the case with this PR 😢
Myself and @patriksvensson sat down this morning, and spiked out a solution to what is requested in #1053 which doesn't impact on as any areas of the system, and a PR will be coming soon in order to review it.  The PR will contain the bare minimum of functionality, mainly:

To allow the referencing of a nuget package in the load pre-processor directive, similar to #load nuget:?package=Cake.Recipe
When this is used, Cake will find that NuGet package, extract it to the tools folder, and then load all .cake files into the current script

If this doesn't cover all your use cases, the changes that will be made to the load pre-processor also mean that you can extend far more easily using a Module than was possible before, so you will have the option to use your own implementation as well.
I hope you understand why this decision was made, and we really appreciate the effort that was put into this PR, which if nothing else, started the conversation on this topic, and allowed us to include this functionality.  This functionality should be available in the 0.18.0 release of Cake.

@gep13 that is strange, the required parts was extended processor and the extended script runner the factory part and some other things are irelevant im sorry that you could not consider fixing the code to youre standards and my time is wasted totally, i created this https://github.com/robgha01/Cake.LoadRemote.Module wich now is worhtless all my time and efforts trached now i know that you people dont care for stuff that you dont need to use. Thancks for nothing. im going to keep on using my own version untill i can find a new build system that suites my needs.

I also see no problem with those changes in the core but i guess you folks dont care opening up 2 3 parts in the core or even building a adaptor around it to solve the issue...

I need to go somewere and destress, im using anti-depresive medecine and right now i can say its not good.

@robgha01 I am sorry that your time has been wasted, but I distinctly remember saying during this process (perhaps in a Gitter conversation) that there was a chance that your work would not be pulled in.  This PR is dealing with some fundamental portions of the internals of Cake, and as a result, we wanted to make sure that it was done in a way that would not impact on other parts of the system.
While we were working on the spike, myself and @patriksvensson, decided that the best course of action was to start from scratch, rather than adapt this PR, as it is quite old of date compared to the latest develop branch (NOTE: this is our fault, as it took us a long time to get back to reviewing this), and also, we wanted to take a slightly different approach to what was suggested in this PR.

@robgha01 said...
wich now is worhtless all my time and efforts trached now i know that you people dont care for stuff that you dont need to use.

This is quite simply not true.  We care deeply about all of our Community Members, and we take great pains to try to not upset anyone.  In this instance, we felt that this was the best option all around.  While I understand your annoyance at your Module no longer working, based on our understanding, your use case is now handled directly within Cake, and a Module is no longer required.  If this is not the case, and your use case is not met, then the extension points that have been added into Cake now make it much easier to extend to include them.

@robgha01 said...
Thancks for nothing. im going to keep on using my own version untill i can find a new build system that suites my needs.

I am truly sorry to hear that.  I really hope you will be able to take advantage of the new functionality that is being added to Cake in this next release, and continue to be a valued member of the community.

@gep13 yea we will see, im a bit unstable as you have noticed my life is not in order well more clearly i cant controll my fealings... So the next version may not use the same kind of solution but it should produce the same result if im not mistaken ?

@robgha01 that is correct.
You should be able to do:
#load nuget:?package=Cake.Recipe
(As an example)
And it will download the nuget package from NuGet.org, extract it to the tools folder, and load load each of the .cake files that were contained within it.`

@gep13 Hi, its been some time have had a nice vacation sort of xD but now i got some time to upgrade my implementation "the old feature request" to this one and test that it all works nicely.
I managed to upgrade with the latest bootstrapper the none deprecated one :)
when i run the build it seams to find the .cake script that i use "#load" with but it what is not working is this:
I have some addings included in the nuget package they are not getting included in the #load process ?
else everything else seams to work so far 👍

@robgha01 glad to have you back!
I have been using this new functionality extensively when using Cake.Recipe, and it is happily working across almost 50 seperate repositories.


Update index.css

On hover ,it changes the animation and shadow effect.

Thanks for the PR, however as the author of that code is @Faizan-Alam-1 .
So, @Faizan-Alam-1 do you thing that the changes is good and should I merge it here?

yes

I  Reviewed the code. Yes it is a good change.

Thanks for the response @Faizan-Alam-1 .


Introduced pluggable architecture (pyearthquake + libearthquake.so) for programmable exploration

QUICKSTART
QUICKSTART: Please refer to example/zk/{README.md, config_example.json, example-output}.
NOTE: Pre-built binaries (including earthquake-classic and earthquake-inspector-classsic.jar) are commited in bin.
Implemented Backend and Bindings:

libearthquake: backend library for recording execution history.
pyearthquake: python binding for libearthquake

Implemented Plug-ins:

orchestrator: [BasicOrchestrator]
explorer: [DumbExplorer, RandomExplorer, GreedyExplorer]
process watcher: [BasicProcessWatcher]
Process Watcher watches events from processes, maps event->action, and execute actions. You can check safety properties(i.e. assertion) in Process Watcher.
termination detector: [InspectionEndDetector, IdleForWhileDetector]
Termination Detector detects termination of one-shot execution.
Execution histories are recorded to storage on such terminations.
InspectionEndDetector: detects termination when InspectionEndEvents are observed
from all processes
IdleForWhileDetector: detects termination when no event are observed
for several milliseconds.

Implemented API:

Orchestartor provides RESTful (JSON over HTTP) API.
HTTP enables simplification of connection handling and proxying
Even if inspectors crashed unexpectedly, you can send
InspectionEndEvents to the orchestrator manually with curl/wget.
JSON enables flexible structuralization. Some JSON-friendly
tools (e.g., JQ, MongoDB, ..) can be used with execution history
JSONs.
POST /api/v1 (Non-blocking): send an event
GET /api/v1/<process_id> (Blocking): receive an action for
<process_id>
GET /visualize_api/csv: GET CSV statistics. You may use gnuplot to
visualize CSV

Implemented Entities:

Events: [FunctionCallEvent(with support for args), PacketEvent(WIP),
LogEvent(WIP), InspectionEndEvent]
Actions: [NopAction, PassDeferredEventAction(for FunctionCallEvent and
PacketEvent), ExecuteCommandOnInspectorAction(WIP),
ExecuteCommandOnOrchestratorAction(usable for fault-injection that
kills inspectors)]

Pulled, thanks!


Initialize offset in ConsumerGroup reconciler

When the offset strategy is set to latest, we need to initialize
the offset in Kafka for that particular consumer group.
Signed-off-by: Pierangelo Di Pilato<EMAIL_ADDRESS>Part of #1537

/test unit-tests_eventing-kafka-broker_main


version:1.4.1 has errors : ./run: 4: ./run: Syntax error: "(" unexpected and so on

errors:
Starting task haproxy_-test.5843aef1-8f5d-11e6-87c9-024265313836
./run: 4: ./run: Syntax error: "(" unexpected
Reloading haproxy
cat: /tmp/haproxy.pid: No such file or directory
[ALERT] 284/024941 (29) : Could not open configuration file /marathon-lb/haproxy.cfg : No such file or directory
./run: 4: ./run: Syntax error: "(" unexpected

Having the same issue, problem seems to be with CLI arguments parsing, bash -x:
+ '[' -n 9090,9091,4080,4443 ']'
+ echo 9090,9091,4080,4443
+ '[' -n 2m ']'
+ echo 2m
+ declare -i ssl_certs_pos=0
+ (( i=1 ))
+ (( i<=6 ))
+ '[' sse = --ssl-certs ']'
+ (( i++ ))
+ (( i<=6 ))
+ '[' --marathon = --ssl-certs ']'
+ (( i++ ))
+ (( i<=6 ))
+ '[' http://localhost:8080 = --ssl-certs ']'
+ (( i++ ))
+ (( i<=6 ))
+ '[' --group = --ssl-certs ']'
+ (( i++ ))
+ (( i<=6 ))
+ '[' LICENSE Longhelp.md Makefile README.md __pycache__ bluegreen_deploy.py bluegreen_deploy.pyc build-haproxy.sh common.py common.pyc config.py getconfig.lua getmaps.lua getpids.lua lrucache.py marathon_lb.py marathon_lb.pyc requirements.txt run service signalmlb.lua templates utils.py zdd.py zdd_exceptions.py = --ssl-certs ']'
/marathon-lb/run: line 30: [: too many arguments
+ (( i++ ))
+ (( i<=6 ))
+ '[' --dry = --ssl-certs ']'
+ (( i++ ))
+ (( i<=6 ))
+ '[' 0 -gt 0 ']'
+ SSL_CERTS=/etc/ssl/cert.pem
+ '[' -n '' ']'
+ '[' 0 -eq 0 ']'

the original command was:
docker run --privileged -e PORTS="9090,9091,4080,4443" --net=host \
        -e HAPROXY_RELOAD_SIGTERM_DELAY="2m" \
        -v /etc/sv/marathon-lb/templates:/marathon-lb/templates\
        -v /etc/nginx/ssl:/certs\
        marathon-lb:1.4.1 sse --marathon http://localhost:8080 --group "*"

@tanglianggithub what arguments are you passing?

Please test with the disable-globbing-in-run image tag to see if that resolves this for you.

@brndnmtthws arguments are /marathon-lb/marathon_lb.py     --syslog-socket /dev/null     --haproxy-config /marathon-lb/haproxy.cfg     --ssl-certs "/etc/ssl/cert.pem"     --command "sv reload /marathon-lb/service/haproxy"     --sse   --marathon http://...:10001 --group zzzc --skip-validation --auth-credentials * --dont-bind-http-https --log-format %(asctime)s- %(levelname)s - %(message)s

python3.5.2+ has error when requesting  "http://hostname:10001/v2/events"
should set python version in dockerfile   @brndnmtthws
error is as follows:
`resp = requests.get(url,stream=True,headers=headers,timeout=(3.05, 46))
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/requests/packages/urllib3/connection.py", line 142, in _new_conn
(self.host, self.port), self.timeout, **extra_kw)
File "/usr/local/lib/python3.5/dist-packages/requests/packages/urllib3/util/connection.py", line 98, in create_connection
raise err
File "/usr/local/lib/python3.5/dist-packages/requests/packages/urllib3/util/connection.py", line 88, in create_connection
sock.connect(sa)
socket.timeout: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/requests/packages/urllib3/connectionpool.py", line 595, in urlopen
chunked=chunked)
File "/usr/local/lib/python3.5/dist-packages/requests/packages/urllib3/connectionpool.py", line 363, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/lib/python3.5/http/client.py", line 1107, in request
self._send_request(method, url, body, headers)
File "/usr/lib/python3.5/http/client.py", line 1152, in _send_request
self.endheaders(body)
File "/usr/lib/python3.5/http/client.py", line 1103, in endheaders
self._send_output(message_body)
File "/usr/lib/python3.5/http/client.py", line 934, in _send_output
self.send(msg)
File "/usr/lib/python3.5/http/client.py", line 877, in send
self.connect()
File "/usr/local/lib/python3.5/dist-packages/requests/packages/urllib3/connection.py", line 167, in connect
conn = self._new_conn()
File "/usr/local/lib/python3.5/dist-packages/requests/packages/urllib3/connection.py", line 147, in _new_conn
(self.host, self.timeout))
requests.packages.urllib3.exceptions.ConnectTimeoutError: (<requests.packages.urllib3.connection.HTTPConnection object at 0x7f3823a48358>, 'Connection to . . ..  timed out. (connect timeout=3.05)')`

@brndnmtthws disable-globbing-in-run branch looks good. I haven't test it on real traffic yet, but arguments parsing seems to be working. Thanks Brenden!
Any chance to draft a new release soon?


Remove dependency on ctx->req in purge()

I want to soft-purge cached objects when a response returned by the back-end server contains xkey-purge header. But putting this code in VCL does nothing:
sub vcl_backend_response {
    if (beresp.http.xkey-purge) {
        std.log("Soft-purged " + xkey.softpurge(beresp.http.xkey-purge) + " objects tagged with [" + beresp.http.xkey-purge + "]");
        unset beresp.http.xkey-purge;
    }
}

... since the purge() function requires non-NULL ctx->req to get timestamp. Is it really necessary, or we can safely replace it with ctx->now as suggested by this patch?

Merged.
FWIW to others reading this, ctx->now was added in a98265912a3b30f76726fa1b5a4ff0b5aabbdb4b and is part of 4.1.0.


MacOS version fails without chrome

I just downloaded the latest version (1.4.5) for MacOS and it raises a fatal error when opening without chrome being installed.
My app.log has the following data:
time="2024-01-11T07:35:16-03:00" level=error msg="error loading storage.json: open /Users/---/Downloads/EggLedger/internal/storage.json: no such file or directory"
time="2024-01-11T07:35:19-03:00" level=fatal msg="unable to locate Chrome"`

I do get a popup window asking if I want to install but after pressing "no" it just dies.

You need Chrome to run Ledger. It is built on top of Lorca - this is true for all versions of it - MK2's, synth's and mine.


H2 sni.yaml overrides do not work with accept threads off

With accept threads off, i.e.
CONFIG proxy.config.accept_threads INT 0

There is no accept_obj at this point in the SNIAction handlers, so e..g this fails:
class DisableH2 : public ActionItem
{
public:
  DisableH2() {}
  ~DisableH2() override {}

  int
  SNIAction(Continuation *cont) const override
  {
    auto ssl_vc     = dynamic_cast<SSLNetVConnection *>(cont);
    auto accept_obj = ssl_vc ? ssl_vc->accept_object : nullptr;
    if (accept_obj && accept_obj->snpa && ssl_vc) {

This essentially makes it impossible to turn off H2 via sni.yaml, unless accept threads are enabled. I don't know if any other SNIAction() handlers would have similar issues.

Fix merged to master


MonitoredTrainingSession does not initialize after restore

Describe the problem
local_init_op can be passed to the SessionManager through the scaffold argument in MonitoredTrainingSession. From the doc's from session manager: The local_init_op is an Operation that is run always after a new session was created. This does not work as expected in the below example.
Exact command to reproduce
global_step = tf.contrib.framework.get_or_create_global_step()
a1 = tf.Variable([1,2,3], name='a1')
a2 = tf.Variable([1,2,3], name='a2')
train = tf.assign(global_step, global_step +1)
saver = tf.train.Saver(var_list=[a1],
                        reshape = False,
                        sharded = False,
                        max_to_keep = 100,
                        keep_checkpoint_every_n_hours = 10000.0,
                        name = "CheckpointSaver",
                        restore_sequentially = False,
                        saver_def = None,
                        builder = None,
                        defer_build = False,
                        allow_empty = False,
                        write_version = tf.train.SaverDef.V2,
                        pad_step_number = False,
                        save_relative_paths = False)
hooks = [tf.train.CheckpointSaverHook(checkpoint_dir = "ckpt/",
                         save_secs = None,
                         save_steps = 1,
                         saver = saver,
                         checkpoint_basename = 'model_to_test.ckpt',
                         scaffold = None,
                         listeners = None)]
scaffold = tf.train.Scaffold(saver=saver, local_init_op = tf.variables_initializer([a2]))
with tf.train.MonitoredTrainingSession(master = '',
                         is_chief = True,
                         checkpoint_dir = "ckpt/",
                         scaffold=scaffold,
                         hooks = hooks,
                         chief_only_hooks = [],
                         save_checkpoint_secs=None,
                         save_summaries_steps=None,
                         save_summaries_secs=None,
                         config=None,
                         stop_grace_period_secs=120,
                         log_step_count_steps=100) as mon_sess:
    print(mon_sess.run(a1))
    print(mon_sess.run(a2))
    mon_sess.run(train)

The first time you run this, two variables a1 and a2 will be initialized by the implied (default) initializer from the MonitoredTrainingSession and a checkpoint file will be written to disk for only a1; expected behavior, no errors. The second time you run this, it should load a1 from the previous checkpoint and initialize a2 through the local_init_op given through the scaffold. But it doesn't, instead:

RuntimeError: Init operations did not make model ready for local_init.  Init op: group_deps, init fn: None, error: Variables not initialized: global_step, a2

A hack that circumvents the problem by not using local_init_op is suggested here (as well as a reiteration of the expected behavior):
https://stackoverflow.com/questions/43336553/how-to-use-tf-train-monitoredtrainingsession-to-restore-only-certain-variables
System information

TensorFlow version (use command below):
('v1.2.0-rc2-21-g12f033d', '1.2.0')
Python version:
2.7.10

Never mind, found it, see here:
https://stackoverflow.com/questions/43336553/how-to-use-tf-train-monitoredtrainingsession-to-restore-only-certain-variables

I read the source code then figure it out how tf.train.MonitoredTrainingSession works.
The key point is you should use a new empty checkpoint directory, otherwise the 'init_op' or other ops won't work.
The complete answer is here:
https://stackoverflow.com/questions/48017748/in-tensorflow-when-graph-is-modified-how-to-use-monitoredtrainingsession-to-r/48071975#48071975


feat: add highlight support for epwalsh/obsidian.nvim

Added highlight support for epwalsh/obsidian.nvim for bullets, done checkboxes, reference links
fixes #322

Below is a screenshot of a working example of some of the changes

Thank you! If you have time, feel free to update the wiki plugin configurations with an example usage.

Thank you! If you have time, feel free to update the wiki plugin configurations with an example usage.

Awesome, thanks ! I'll do that !


Update github-actions-demo-maven.yml

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


the AI can't remember previous messages sent to or from it.

is there any way to fix this? I'm planning on just adding all messages to a single prompt to the character, but i get the feeling that it will significantly slow everything down.

Are you using the Room() function? Let's assume you are. At the end, do you declare saving the history with saveHistory?
If you're using Room in a single session, the data gets deleted after a restart because "Temporary memory" is being used. To save the data, you need to call .saveHistory(), and then load the created file into Room with the parameter history_path:
Room(history_path="./history.json").
I'm not denying the fact that the error could be on our side, but without additional information from you, it's hard to say anything for sure.
Actually, there can be many nuances, but I'll work on optimizing all of this a bit later.

What's the room function? I've just been using the create completion function from the documentation

I am almost certain that you will find the solutions by reading this:
https://red-3.gitbook.io/freegptfix/lib/room


Update doc assets

/CC @cvrebert

@cvrebert: hound needs fixing it seems.

Note to self: don't merge this yet until #20302 is sorted

Rebased.

The Hound issue should be fixed in #20446 if I understand correctly.

@cvrebert: bump

This has conflicts—is it good to merge otherwise?

Well, it was good; now I'll need to check for newer versions :p

You can look at #20555 if you want to avoid fixing the conflicts in this. It originally started off as a small PR by now encroaches quite a bit on this.

Nah, I'd rather do it myself.

Not necessary after merge #20555.


start-webserver.sh fail with pydantic schema-for-unknown-type

Hi,
I tryied the colab and it failed with pydantic error.
So i create a new environment on a linux headless server:

pyenv install 3.11.9
pyenv local 3.11.9
clone repo
cd fastsdcpu
pyenv local 3.11.9
chmod +x install.sh
install.sh --disable-gui
./start-webui.sh

and same i get the same error
51 $ ./start-webui.sh
Starting FastSD CPU please wait...
Found python command
Python version : 3.11.9
Settings not found creating default settings
Running on Linux platform
OS: Linux-6.1.0-21-amd64-x86_64-with-glibc2.36
Processor:
Using device : cpu
Found 8 LCM models in config/lcm-models.txt
Found 7 stable diffusion models in config/stable-diffusion-models.txt
Found 4 LCM-LoRA models in config/lcm-lora-models.txt
Found 9 OpenVINO LCM models in config/openvino-lcm-models.txt
/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/controlnet_aux/segment_anything/modeling/tiny_vit_sam.py:654: UserWarning: Overwriting tiny_vit_5m_224 in registry with controlnet_aux.segment_anything.modeling.tiny_vit_sam.tiny_vit_5m_224. This is because the name being registered conflicts with an existing name. Please check if this is not expected.
  return register_model(fn_wrapper)
/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/controlnet_aux/segment_anything/modeling/tiny_vit_sam.py:654: UserWarning: Overwriting tiny_vit_11m_224 in registry with controlnet_aux.segment_anything.modeling.tiny_vit_sam.tiny_vit_11m_224. This is because the name being registered conflicts with an existing name. Please check if this is not expected.
  return register_model(fn_wrapper)
/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/controlnet_aux/segment_anything/modeling/tiny_vit_sam.py:654: UserWarning: Overwriting tiny_vit_21m_224 in registry with controlnet_aux.segment_anything.modeling.tiny_vit_sam.tiny_vit_21m_224. This is because the name being registered conflicts with an existing name. Please check if this is not expected.
  return register_model(fn_wrapper)
/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/controlnet_aux/segment_anything/modeling/tiny_vit_sam.py:654: UserWarning: Overwriting tiny_vit_21m_384 in registry with controlnet_aux.segment_anything.modeling.tiny_vit_sam.tiny_vit_21m_384. This is because the name being registered conflicts with an existing name. Please check if this is not expected.
  return register_model(fn_wrapper)
/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/controlnet_aux/segment_anything/modeling/tiny_vit_sam.py:654: UserWarning: Overwriting tiny_vit_21m_512 in registry with controlnet_aux.segment_anything.modeling.tiny_vit_sam.tiny_vit_21m_512. This is because the name being registered conflicts with an existing name. Please check if this is not expected.
  return register_model(fn_wrapper)
Starting web UI mode
IMPORTANT: You are using gradio version 4.23.0, however version 4.29.0 is available, please upgrade.
--------
IMPORTANT: You are using gradio version 4.23.0, however version 4.29.0 is available, please upgrade.
--------
IMPORTANT: You are using gradio version 4.23.0, however version 4.29.0 is available, please upgrade.
--------
IMPORTANT: You are using gradio version 4.23.0, however version 4.29.0 is available, please upgrade.
--------
IMPORTANT: You are using gradio version 4.23.0, however version 4.29.0 is available, please upgrade.
--------
No lora models found, please add lora models to /home/myuser/project/fastsdcpu/lora_models directory
/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/gradio/components/dropdown.py:179: UserWarning: The value passed into gr.Dropdown() is not in the list of choices. Please update the list of choices to include:  or set allow_custom_value=True.
  warnings.warn(
IMPORTANT: You are using gradio version 4.23.0, however version 4.29.0 is available, please upgrade.
--------
IMPORTANT: You are using gradio version 4.23.0, however version 4.29.0 is available, please upgrade.
--------
IMPORTANT: You are using gradio version 4.23.0, however version 4.29.0 is available, please upgrade.
--------
Running on local URL:  http://<IP_ADDRESS>:7860

To create a public link, set `share=True` in `launch()`.
IMPORTANT: You are using gradio version 4.23.0, however version 4.29.0 is available, please upgrade.
--------
ERROR:    Exception in ASGI application
  + Exception Group Traceback (most recent call last):
  |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/_utils.py", line 77, in collapse_excgroups
  |     yield
  |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/base.py", line 186, in __call__
  |     async with anyio.create_task_group() as task_group:
  |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 680, in __aexit__
  |     raise BaseExceptionGroup(
  | ExceptionGroup: unhandled errors in a TaskGroup (1 sub-exception)
  +-+---------------- 1 ----------------
    | Traceback (most recent call last):
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/uvicorn/protocols/http/h11_impl.py", line 406, in run_asgi
    |     result = await app(  # type: ignore[func-returns-value]
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in __call__
    |     return await self.app(scope, receive, send)
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in __call__
    |     await super().__call__(scope, receive, send)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/applications.py", line 113, in __call__
    |     await self.middleware_stack(scope, receive, send)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/errors.py", line 187, in __call__
    |     raise exc
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__
    |     await self.app(scope, receive, _send)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/base.py", line 185, in __call__
    |     with collapse_excgroups():
    |   File "/home/myuser/.pyenv/versions/3.11.9/lib/python3.11/contextlib.py", line 158, in __exit__
    |     self.gen.throw(typ, value, traceback)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/_utils.py", line 83, in collapse_excgroups
    |     raise exc
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/base.py", line 187, in __call__
    |     response = await self.dispatch_func(request, call_next)
    |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/gradio/route_utils.py", line 675, in dispatch
    |     response = await call_next(request)
    |                ^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/base.py", line 163, in call_next
    |     raise app_exc
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/base.py", line 149, in coro
    |     await self.app(scope, receive_or_disconnect, send_no_error)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__
    |     await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/_exception_handler.py", line 62, in wrapped_app
    |     raise exc
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/_exception_handler.py", line 51, in wrapped_app
    |     await app(scope, receive, sender)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__
    |     await self.middleware_stack(scope, receive, send)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/routing.py", line 735, in app
    |     await route.handle(scope, receive, send)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle
    |     await self.app(scope, receive, send)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/routing.py", line 76, in app
    |     await wrap_app_handling_exceptions(app, request)(scope, receive, send)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/_exception_handler.py", line 62, in wrapped_app
    |     raise exc
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/_exception_handler.py", line 51, in wrapped_app
    |     await app(scope, receive, sender)
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/routing.py", line 73, in app
    |     response = await f(request)
    |                ^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/routing.py", line 291, in app
    |     solved_result = await solve_dependencies(
    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/dependencies/utils.py", line 639, in solve_dependencies
    |     ) = await request_body_to_args(  # body_params checked above
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/dependencies/utils.py", line 813, in request_body_to_args
    |     fields_to_extract = get_cached_model_fields(first_field.type_)
    |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/_compat.py", line 657, in get_cached_model_fields
    |     return get_model_fields(model)
    |            ^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/_compat.py", line 284, in get_model_fields
    |     return [
    |            ^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/_compat.py", line 285, in <listcomp>
    |     ModelField(field_info=field_info, name=name)
    |   File "<string>", line 6, in __init__
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/_compat.py", line 110, in __post_init__
    |     self._type_adapter: TypeAdapter[Any] = TypeAdapter(
    |                                            ^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/type_adapter.py", line 241, in __init__
    |     core_schema = _get_schema(type, config_wrapper, parent_depth=_parent_depth + 1)
    |                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/type_adapter.py", line 156, in _get_schema
    |     schema = gen.generate_schema(type_)
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 452, in generate_schema
    |     schema = self._generate_schema(obj)
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 684, in _generate_schema
    |     schema = self._post_process_generated_schema(self._generate_schema_inner(obj))
    |                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 691, in _generate_schema_inner
    |     return self._annotated_schema(obj)
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1524, in _annotated_schema
    |     schema = self._apply_annotations(source_type, annotations)
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1592, in _apply_annotations
    |     schema = get_inner_schema(source_type)
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in __call__
    |     schema = self._handler(__source_type)
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1682, in new_handler
    |     schema = metadata_get_schema(source, get_inner_schema)
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1678, in <lambda>
    |     lambda source, handler: handler(source)
    |                             ^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in __call__
    |     schema = self._handler(__source_type)
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1573, in inner_handler
    |     schema = self._generate_schema(obj)
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 684, in _generate_schema
    |     schema = self._post_process_generated_schema(self._generate_schema_inner(obj))
    |                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 711, in _generate_schema_inner
    |     return self.match_type(obj)
    |            ^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 794, in match_type
    |     return self._match_generic_type(obj, origin)
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 818, in _match_generic_type
    |     return self._union_schema(obj)
    |            ^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1006, in _union_schema
    |     choices.append(self.generate_schema(arg))
    |                    ^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 452, in generate_schema
    |     schema = self._generate_schema(obj)
    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 684, in _generate_schema
    |     schema = self._post_process_generated_schema(self._generate_schema_inner(obj))
    |                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 711, in _generate_schema_inner
    |     return self.match_type(obj)
    |            ^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 798, in match_type
    |     return self._unknown_type_schema(obj)
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 366, in _unknown_type_schema
    |     raise PydanticSchemaGenerationError(
    | pydantic.errors.PydanticSchemaGenerationError: Unable to generate pydantic-core schema for <class 'starlette.requests.Request'>. Set `arbitrary_types_allowed=True` in the model_config to ignore this error or implement `__get_pydantic_core_schema__` on your type to fully support it.
    |
    | If you got this error by calling handler(<some type>) within `__get_pydantic_core_schema__` then you likely need to call `handler.generate_schema(<some type>)` since we do not call `__get_pydantic_core_schema__` on `<some type>` otherwise to avoid infinite recursion.
    |
    | For further information visit https://errors.pydantic.dev/2.4/u/schema-for-unknown-type
    +------------------------------------

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/uvicorn/protocols/http/h11_impl.py", line 406, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in __call__
    return await self.app(scope, receive, send)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/applications.py", line 113, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/errors.py", line 187, in __call__
    raise exc
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__
    await self.app(scope, receive, _send)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/base.py", line 185, in __call__
    with collapse_excgroups():
  File "/home/myuser/.pyenv/versions/3.11.9/lib/python3.11/contextlib.py", line 158, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/_utils.py", line 83, in collapse_excgroups
    raise exc
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/base.py", line 187, in __call__
    response = await self.dispatch_func(request, call_next)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/gradio/route_utils.py", line 675, in dispatch
    response = await call_next(request)
               ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/base.py", line 163, in call_next
    raise app_exc
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/base.py", line 149, in coro
    await self.app(scope, receive_or_disconnect, send_no_error)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in __call__
    await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/_exception_handler.py", line 62, in wrapped_app
    raise exc
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/_exception_handler.py", line 51, in wrapped_app
    await app(scope, receive, sender)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/routing.py", line 715, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/routing.py", line 735, in app
    await route.handle(scope, receive, send)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle
    await self.app(scope, receive, send)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/routing.py", line 76, in app
    await wrap_app_handling_exceptions(app, request)(scope, receive, send)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/_exception_handler.py", line 62, in wrapped_app
    raise exc
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/_exception_handler.py", line 51, in wrapped_app
    await app(scope, receive, sender)
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/starlette/routing.py", line 73, in app
    response = await f(request)
               ^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/routing.py", line 291, in app
    solved_result = await solve_dependencies(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/dependencies/utils.py", line 639, in solve_dependencies
    ) = await request_body_to_args(  # body_params checked above
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/dependencies/utils.py", line 813, in request_body_to_args
    fields_to_extract = get_cached_model_fields(first_field.type_)
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/_compat.py", line 657, in get_cached_model_fields
    return get_model_fields(model)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/_compat.py", line 284, in get_model_fields
    return [
           ^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/_compat.py", line 285, in <listcomp>
    ModelField(field_info=field_info, name=name)
  File "<string>", line 6, in __init__
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/fastapi/_compat.py", line 110, in __post_init__
    self._type_adapter: TypeAdapter[Any] = TypeAdapter(
                                           ^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/type_adapter.py", line 241, in __init__
    core_schema = _get_schema(type, config_wrapper, parent_depth=_parent_depth + 1)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/type_adapter.py", line 156, in _get_schema
    schema = gen.generate_schema(type_)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 452, in generate_schema
    schema = self._generate_schema(obj)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 684, in _generate_schema
    schema = self._post_process_generated_schema(self._generate_schema_inner(obj))
                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 691, in _generate_schema_inner
    return self._annotated_schema(obj)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1524, in _annotated_schema
    schema = self._apply_annotations(source_type, annotations)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1592, in _apply_annotations
    schema = get_inner_schema(source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in __call__
    schema = self._handler(__source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1682, in new_handler
    schema = metadata_get_schema(source, get_inner_schema)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1678, in <lambda>
    lambda source, handler: handler(source)
                            ^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_schema_generation_shared.py", line 82, in __call__
    schema = self._handler(__source_type)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1573, in inner_handler
    schema = self._generate_schema(obj)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 684, in _generate_schema
    schema = self._post_process_generated_schema(self._generate_schema_inner(obj))
                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 711, in _generate_schema_inner
    return self.match_type(obj)
           ^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 794, in match_type
    return self._match_generic_type(obj, origin)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 818, in _match_generic_type
    return self._union_schema(obj)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 1006, in _union_schema
    choices.append(self.generate_schema(arg))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 452, in generate_schema
    schema = self._generate_schema(obj)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 684, in _generate_schema
    schema = self._post_process_generated_schema(self._generate_schema_inner(obj))
                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 711, in _generate_schema_inner
    return self.match_type(obj)
           ^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 798, in match_type
    return self._unknown_type_schema(obj)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/myuser/project/fastsdcpu/env/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 366, in _unknown_type_schema
    raise PydanticSchemaGenerationError(
pydantic.errors.PydanticSchemaGenerationError: Unable to generate pydantic-core schema for <class 'starlette.requests.Request'>. Set `arbitrary_types_allowed=True` in the model_config to ignore this error or implement `__get_pydantic_core_schema__` on your type to fully support it.

If you got this error by calling handler(<some type>) within `__get_pydantic_core_schema__` then you likely need to call `handler.generate_schema(<some type>)` since we do not call `__get_pydantic_core_schema__` on `<some type>` otherwise to avoid infinite recursion.

For further information visit https://errors.pydantic.dev/2.4/u/schema-for-unknown-type
^CKeyboard interruption in main thread... closing server.

seems to work using the lastest gradio.
 $ source env/bin/activate $ pip install -U gradio $ pip freeze | grep gradio gradio==4.44.0 gradio_client==1.3.0


Add development container and update READMEs. Add Sphinx furo theme.

This PR adds Visual Studio Code development container configs. Development containers make it easier to onboard new contributors without having to set up the development environment and tooling on their host system.
This PR also updates the README of the main repository and the README of pyoxigraph with additional development information.
This PR also includes updating the pyoxigraph sphinx docs theme to furo. https://github.com/oxigraph/oxigraph/pull/221/commits/4a5c6b8444e3ea691c866a500201d55a79b67e38

Screenshots of sphinx classic vs furo theme:
Classic

Furo

I believe you also need to add furo to the dependencies of the artifacts.yml and release.yml.script.

Ah yes!


Results on system UNM Roadrunners

Hi @rysc3, can you please clear the old results? Was the final upload automatically done by the cm command?


chore: bdd-nh-import-1584170381 to 0.0.1

chore: Promote bdd-nh-import-1584170381 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


feat(deprecate): add step to clean up backseat driver

Coverage remained the same at 94.82% when pulling 4da665c837ef7c2745ca08edaf7a38cbea010da5 on stdavis-patch-1 into 9e30275f228da7fa386dc75a9148e043393eae42 on master.


想问大神之前IndexableStickyListView的有的机型崩溃bug，这个新的库解决了么？

崩溃日志是这个：  The content of the adapter has changed but ListView did not receive a notification. Make sure the content of your adapter is not modified from a background thread, but only from the UI thread. Make sure your adapter calls notifyDataSetChanged() when its content changes


Azure Purview access management has moved into data plane. Azure Resource Manager roles aren't used anymore.

Azure Purview access management has moved into data plane. Azure Resource Manager roles aren't used anymore.

https://docs.microsoft.com/en-us/azure/purview/concept-best-practices-collections
https://docs.microsoft.com/en-us/azure/purview/catalog-permissions

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

ID: 80001cb2-79da-3d98-5872-8fa693e4d514
Version Independent ID: 887424be-b915-cb8f-6805-00d45d1961fc
Content: Azure Purview readiness checklist for the data management and analytics enterprise-scale scenario - Cloud Adoption Framework
Content Source: docs/scenarios/data-management/best-practices/purview-checklist.md
Service: cloud-adoption-framework
Sub-service: scenario
GitHub Login: @Zeinam
Microsoft Alias: zeinam

Thank you
#assign: @abdale
#label:"data management and analytics"

The following users don't have valid GitHub IDs, or are not collaborators on this repo: le
#label"data

#label:"data management and analytics"

#assign: @abdale

cc @zeinab-mk

Thanks @isdataninja. We noticed some of the roles guidance was outdated so we linked it directly to the Purview docs to avoid any confusion.

@abdale please can you link the pull request so that this can be closed off.

@abdale please can you link the pull request so that this can be closed off.

I don't seem to have the permissions to do that. Here's the PR MicrosoftDocs/cloud-adoption-framework-pr#3091

@abdale, can you please confirm the PR#?

@abdale, can you please confirm the PR#?

Try this: https://github.com/MicrosoftDocs/cloud-adoption-framework-pr/pull/3091

@abdale, can you please confirm the PR#?

Try this: https://github.com/MicrosoftDocs/cloud-adoption-framework-pr/pull/3091

 i do not have access to pr-3091

@abdale here is the link for ALL pull requests --> https://github.com/MicrosoftDocs/cloud-adoption-framework/pulls can you confirm which here is the one to resolve this issue?

https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/data-management/best-practices/purview-checklist this page is still reference rbac, please remove
@abdale

updated

#please-close


Easily create Issue from within Bot

User can write issue from within telegram.

Created Issue, Bug command, that will send you the link to the Github Issue Page. Creating a command, that would instantly create a Issue would cause spamming.


fix os old url not working

cherry pick from dev to master

LGTM
@AlPha5130 Can you help test this one?


docs(mediator): Updated the readme and docker with type of key forma…

…t used for mediator identity
Description:
Summarize the changes you're submitting in a few sentences, including Jira ticket ATL-xxxx if applicable.
Link to any discussion, related issues and bug reports to give the context to help the reviewer understand the PR.
Alternatives Considered (optional):
Link to existing ADR (Architecture Decision Record), if any. If relevant, describe other approaches explored and the selected approach. Documenting why the methods were not selected will create a knowledge base for future reference, helping prevent others from revisiting less optimal ideas.
Checklist:

[X] My PR follows the contribution guidelines of this project
[X] My PR is free of third-party dependencies that don't comply with the Allowlist
[] I have commented my code, particularly in hard-to-understand areas
[] I have made corresponding changes to the documentation
[] I have added tests that prove my fix is effective or that my feature works
[] I have checked the PR title to follow the conventional commit specification

What do you think about also removing the default keys for #264 ?
And switch for a tutorial how to create the keys (2 or 3 paragraphs maximum)

What do you think about also removing the default keys for #264 ? And switch for a tutorial how to create the keys (2 or 3 paragraphs maximum)

I think we should have 2 modes dev and prod as you mentioned, I think for getting started quick guide default keys are better
And we could a tutorial for genrating keys for PROD purpose


fix(scrolling): viewport ruler events being run inside zone

Fixes the resize and orientationchange events of the ViewportRuler being run inside the NgZone, if the subscription comes from inside the zone.

Bumping to a P2 since we got a report about this potentially affecting perf.

Is there any blocking issue that causes this MR to not be merged? Just for know.
I also miss the 'zone re-entering' of the subscriptions that need it. For example the select component & the paginated-tab-header.
Here I have a proposal MR (same of this one, I actually copy the tests, thanks @crisbeto) where I do this 'zone re-enterings':
https://github.com/angular/components/pull/18548/files


bytesize talk Resources to learn nextflow

Hi @FranBonath could you update my current position to Bioinformatics Pipeline Engineer, Bluestar Genomics ?


Build action doesn't properly compare date version parts to integer version parts

I still have some issues with the build action implemented in #14. Take the following config:
__config_version__ = 1

GLOBALS = {
    'serializer': '{{year}}.{{month}}.{{build}}',
}

FILES = ['setup.py']

VERSION = [
    {
        'name': 'year',
        'type': 'date',
        'fmt': 'YYYY'
    },
    {
        'name': 'month',
        'type': 'date',
        'fmt': 'MM'
    },
    {
        'name': 'build',
        'type': 'integer',
        'start_value': 0
    }
]

VCS = {
    'name': 'git',
    'commit_message': "Release {{ new_version }}",
}

ACTIONS = {
    'build': {
        'type': 'conditional_reset',
        'field': 'build',
        'update_fields': ['year', 'month']
    }
}

And the following version file:
year = 2017
month = 6
build = 8

When I simulate a build action, the new version is '2017.6.0'. The reason for this is this condition in the action module:
    if new_version == version:
        reset_part.inc()
    else:
        reset_part.reset()

Here new_version and version are considered different, even though they both point at 2017.6.8. The problem is that the new_version points at '2017', '6', 8. While the version points at 2017, 6, 8. That is, the types of the fields are not equal. The new_version contains integers and strings, while the old version contains only integers.
So there should probably be some normalisation.

I see, actually you mentioned this problem in the former issue, and I thought I solved it. Thanks for the report, I'll work on it asap

@vovanbo thank you for PR #16! @href can you try that solution while I review the PR?

I'm afraid it doesn't seem to work for me. I'm using Python 3.5 and this is the repository I'm running the command against: https://github.com/OneGov/onegov.applications. Running punch.py --action build -s still gives me "2017.6.0".

@href It will be fine if your punch_version.py will contain string representation of year and month. After first run of fixed punch.py version file will be updated to correct state.
@lgiordani Also, for now if you will change format of month to 0M, then non-fixed punch.py will generate incorrect version file, for example:
year = 2017
month = 06
build = 13

Note, that month is incorrect octal number now.

That did it @vovanbo, thank you. I tested it successfully now.

@vovanbo if I get it correctly, the issue here is that the configuration file contained integers instead of strings, right?

#22 should fix this problem, @href can you check that as well? @vovanbo solution fixed the issue, but we didn't have any test

I tested the change by @vovanbo before and it solved my issue.

@lgiordani I think all values stored in version file must be strings. And should be deserialised to proper value after parsing version file. Another approach as I understand from your comment at my PR (#17) is store valid Python code in version file. So, may be fix of this issue is not just a stringify of version part values, but store date version parts as Python datetime objects. And after vp.DateVersionPart should get part of datetime (year, month, day etc.) from punch_version.py file.

@href thanks, but I do not agree with the implementation he proposed, so I tried to come up with another solution. Unfortunately the only test case we have is your configuration, so I started from that and I tried to come up with some code. This is why I asked if you could test my code. I think your version file is wrong because it contains integers instead of strings. Why is that? Did you write the file manually? Or did punch write it?
@vovanbo I'm afraid I didn't understand your point, sorry. Date parts are strings because they are formatted with a specific format that returns strings ('fmt' is a valid parameter for strftime()). Other parts like IntegerPart are integers because, well, the name says integer. Storing date version parts as datetime objects is, in my opinion, overkill. The punch_version.py is intended to be readable, and datetime objects are not that clear if you want to represent only one part of the whole date, I think. If you have a counterexample on this, feel free to post it. Please open another issue, however, as this one is dealing with a specific bug.
Overall, I'm afraid I do no understand what we are trying to solve, sorry. If we can come up with a test or a use case that shows a problem, we can perhaps further discuss the issue. I proposed #22 as a solution for a wrong punch_version.py file, which contained integers instead of strings. If this is not the problem, as I thought, please can you help me understand the issue?

@lgiordani Oh sorry, I didn't read your message properly. I actually think I tested #22 before and that's what I was referring to. I thought I mentioned that somewhere, but I must have imagined that.
Anywho, I tested it again to be safe and I can confirm that your approach works. So from my perspective this ticket can be closed as soon as #22 is implemented and released :)
Sorry for the confusion!
Also, since you are asking why my version file contains integers instead of strings. Punch wrote that file from what I can tell and it seems to still do so with your solution. I don't know if this should be the case or not, but the result is fine.

@lgiordani I just try to find good solution for this issue. Nothing more. In #16 i will try to use native representation of version's parts values. I think __repr__ is exactly that wanted here, because version part saved in Python file and must be a valid Python code. Therefore i've changed version file writer in PR to something like this (here):
f.write('{0.name} = {0!r}\n'.format(new_version.parts[i]))

So, it's my vision of solution. May be integers must not to be represented as strings.
About readability of punch_version.py. I think if users will use more complex behaviour to get some version values, then readability of version file will be lost anyway. But, I agree that this issue is not good place to discuss it.

@vovanbo thanks! Yeah I know you are trying to help, and it is really appreciated. Sorry if I sounded rude, I just wanted to understand the issue. I think I understand your #22 solution better now. I think you are correctly trying to check if we need to generalise the read/write operation on version parts, and probably __str__ is what we want (as __repr__'s target is a unique internal representation). I will move the discussion to #16 as the use case has been understood and will be solved by one of the PRs (I'll close this as soon as we merge a solution). Thanks

As I commented in #16 I'm sorry that in the last two months I didn't have time to follow the project, so my understanding of the whole issue is a bit lost. I think #22 solves the issue, but feel free to reopen an issue if something is still wrong. Thanks for the collaboration and sorry again for ignoring the thread for a long time. #22 will be merged in version 1.4.1, I'll release it today.

Thanks @lgiordani. Fwiw, I've been using the PR and it has been working as expected.

Thank you!


[Bug] CREATE USER ·····UNBOUNDED，中UNBOUNDED参数无效

Search before asking

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

Version
2.0.2
What's Wrong?
CREATE USER jack IDENTIFIED BY '123456'  FAILED_LOGIN_ATTEMPTS 3 PASSWORD_LOCK_TIME UNBOUNDED;
UNBOUNDED 参数无法生效，如果是具体天数锁定可以生效。
What You Expected?
UNBOUNDED 参数可以生效
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

I will fix it

https://github.com/apache/doris/pull/26585


[FEAT] Adjust package names to use @synergy-design-system as prefix

All packages must be prefixed using @synergy-design-system

What about the tag name? Just we change it right now in this PR (from "sds-" to "syn-") or will we do this at a later point?


Include thumbnail images in datasource and model catalog entries

A small image representing a slice of the data, as a 'preview'.

Settle on size and format (128*128, png?) 256*256 jpg
Collect the images as scivision/catalog/data/thumbnails/datasources/{NAME}.png (with the name of a corresponding entry in datasources.json), or perhaps scivision/catalog/data/resources/datasources/{NAME}/thumb.png, anticipating other resources associated with an entry
Display these alongside the datasource in the frontend (in the datasources table, or on a data card)

TODOs

[ ] Add an image for each model
[ ] Add an image for each datasource
[ ] Rename (or delete) datasources called data-00X

Launch a PR that changes the json (and thumbnail if appropriate) and tag relevant person
Make sure any notebooks using the datasource are updated

Most of these are done, will open separate issues for entries without them


How do I hide the "Code" column (or make it smaller)?

The code column (showing 1, 2, 3,....) it pretty wide.
How can I make it smaller?
Or even better: hide it (temporarily?

Hi, You cannot hide or change the width of line numbers.
If you need more space, you can make the code window wider by stretching the middle gap.


Add Dataset.drop_dims

[x] Closes #1949
[x] Tests added
[x] Fully documented, including whats-new.rst for all changes and api.rst for new API

Hello @kmsquire! Thanks for submitting the PR.

In the file xarray/core/dataset.py, following are the PEP8 issues :

Line 2833:80: E501 line too long (83 > 79 characters)

In the file xarray/tests/test_dataset.py, following are the PEP8 issues :

Line 1872:34: E231 missing whitespace after ','
Line 1872:38: E231 missing whitespace after ','
Line 1879:37: E231 missing whitespace after ','
Line 1880:34: E231 missing whitespace after ','
Line 1880:38: E231 missing whitespace after ','
Line 1890:34: E231 missing whitespace after ','
Line 1890:38: E231 missing whitespace after ','
Line 1894:30: E231 missing whitespace after ','
Line 1895:34: E231 missing whitespace after ','
Line 1895:38: E231 missing whitespace after ','

I was looking for this functionality and ran across #1949.
There was one bit of behavior that was unclear to me.  Say I have
In [6]: data = xr.Dataset({'A': (['x', 'y'], np.random.randn(2, 3)),
   ...:                    'B': ('x', np.random.randn(2)),
   ...:                    'x': ['a', 'b'], 'z': np.pi})

In [7]: data
Out[7]:
<xarray.Dataset>
Dimensions:  (x: 2, y: 3)
Coordinates:
  * x        (x) <U1 'a' 'b'
Dimensions without coordinates: y
Data variables:
    A        (x, y) float64 -0.662 -0.705 -0.1866 -0.8655 0.5816 -0.2308
    B        (x) float64 -0.1002 2.402
    z        float64 3.142

In [8]: data.drop_dims('x')
Out[8]:
<xarray.Dataset>
Dimensions:  ()
Data variables:
    z        float64 3.142

In this case, I dropped x, but because that eliminated variable A, I also dropped my y dimension, since A was the only variable using y.
At one point, I implemented this slightly differently, which instead gave
In [8]: data.drop_dims('x')
Out[8]:
<xarray.Dataset>
Dimensions:  (y: 3)
Dimensions without coordinates: y
Data variables:
    z        float64 3.142

In some ways, this seems preferable, especially if y has coordinates.  The only downside I can see is that this version called Dataset._replace_vars_and_dims(), the docstring for which says it's deprecated (although it's still widely used).

@shoyer I'm sure you're busy... wondering if you might have time to review this (or direct it to someone else to review)?
Other than my question above, it should be pretty straightforward.

It's OK to use _replace_with_new_dims still. I think we'll eventually replace it in favor of _replace_with_new_dims but we aren't there yet.
I agree that it makes sense to recompute dimensions from variables. There's not much point in keeping around extra dimensions that don't have corresponding variables, and I'm pretty sure that this is consistent with how Dataset.drop() works.

I agree that it makes sense to recompute dimensions from variables.

Okay, that's what this PR already did (via the call to _replace_with_new_dims).
Rebased on master.  From my perspective, this should be good to go.

@shoyer I force pushed the requested changes.  Please let me know if there is anything else.  Thanks!

Rebased to fix the NEWS conflict.

thanks @kmsquire, especially for your patience here!

No worries--thanks for merging!

Is there currently a way to drop unused coordinates, like this?

I guess ds = ds.drop([c for c in ds.coords if c not in ds.dims]) works. Might be nice to have a convenience function for that though.


SDK ceiling up CPU on 5-10K/s TrackEvent calls without sending any data

If you are reporting bug/issue, please provide detailed Repro instructions.
Repro Steps

Implement a processor that drops all Event documents (see BlockTracesAndEventsTelemetryProcessor.zip for example)
Implement any logic that would call TrackEvent at a rate of 5-10K calls per second

Actual Behavior
Process uses up all CPU, with most of the time spend inside Initialize method
Expected Behavior
Since no data is being send, no noticeable impact on process CPU time from adding TrackEvent calls

Version Info
SDK Version : 2.4.0
.NET Version :	4.7
How Application was onboarded with SDK(VisualStudio/StatusMonitor/Azure Extension) : VisualStudio
OS : Windows Server 2016
Hosting Info (IIS/Azure WebApps/ etc) : Cloud Service (PaaS v1)

Closing old issue.
Even if no data is sent, all TI is still run.


[Ready for Review] Added annotations for Batch

Runtime changes detected. pull request created. CI running:

@alvadb could you pls review?

Runtime changes detected. pull request created. CI running:

Runtime changes detected. pull request created. CI running:


Appium is unable to detect the on/off recurring button

Describe the bug
Appium is unable to detect the on/off recurring button within the drop-in card component during integration testing. This prevents us from writing comprehensive test cases for this specific feature.
To Reproduce
Steps to reproduce the behaviour:

Launch the mobile app.
Navigate to the screen containing the drop-in card component.
Locate the on/off recurring button within the component.
Attempt to interact with the button using Appium's locators.

Expected behaviour
Appium should be able to identify and interact with the on/off recurring button within the drop-in card component, allowing for automated testing of its functionality.
Screenshots

**Smartphone: *

Device: iPhone
OS: Any

Additional context
"@adyen/react-native": "1.2.0",

Hi @iranaahsanali,
What locator strategy do you use and what element do you look for?
Underlying SDK does not handle "row" click and user must tap on the switch itself.
If you use Appium Inspector, please try drilling down to the switch element and locating it instead of locating the row.
We also plan to use Appium internally and we are keen to make changes that would make testing easier!

Hi @atmamont,
We are using findElement using "xpath" or "id" to find the toggle button. We cannot rely on offset coordinate of toggle button since we are not executing our testcases on single ios device. If we rely on coordinates then our testcases will fail on executing on different ios devices whose resolution differs. Moreover through appium inspector whenever we try to highlight toggle button it is highlighting the whole row instead of toggle button separately.

Hi, @Vikas-lebara
I'm commenting to keep this one alive.
Please take a look here for a short description.
I will update you when we have a solution that fits both accessibility and testing requirements.

We found the way to keep existing VoiceOver capabilities and satisfy tools like Appium, it seems to be a good compromise. We plan to release it soon for iOS SDK and shortly after that for React Native.
If you want to know more, here are some links that explain this is the issue that no one wants to own:

https://discuss.appium.io/t/unable-to-locate-some-elements-in-ios-same-elements-can-be-found-via-calabash/24810/5
https://github.com/appium/appium/issues/6517

Unfortunately, xcuitest-driver Appium uses to traverse a native mobile app, relies on accessibility layer so we have to be creative.

@Vikas-lebara
It's released for the main iOS SDK and will be included in the following React Native release.

@descorp Any tentative timeline for releasing the above Native iOS fix on our React Native SDK?

Hey @ahsan-lebara
This will be included into next release.
ETA end of November


train

It's not appropriate to pass the depth information directly, it's equivalent to getting the GT directly

Thank you for your message. I believe that depth information and GT are not equivalent. Directly transmitting depth information does not mean directly transmitting GT. There is a fundamental difference between the two.

Thank you for your reply. I have another question. How do you determine the best epoch during training? I see in the paper that you mentioned it's based on the weighted F-measure, but I don't see the relevant code. It only saves periodically.

We adopted the most straightforward approach, which involves testing the MAE metric at each epoch. The epoch corresponding to the lowest MAE value is selected as the best epoch.


Fixed doctests

See https://github.com/Chilipp/docrep/pull/7

Coverage remained the same at 96.216% when pulling 88757836d464c70a78fe93f7c63e84b822c03efd on dev into 2c8ab4da983b78409ed76fb09ca32e1f74bd8b4d on master.

Coverage remained the same at 96.216% when pulling 88757836d464c70a78fe93f7c63e84b822c03efd on dev into 2c8ab4da983b78409ed76fb09ca32e1f74bd8b4d on master.


Postgres getting started script Update

The PR includes the option to set the Zitadel Database variable and also set Postgres as default if the variable is unset.
Checklist

[x] Is it a bug fix
[x] Is a typo/documentation fix
[x] Is a feature enhancement
[x] It is a refactor

The current solution works also in that way.


ProjectCard is missing

after deploying an app it works but when logged in back the ProjectCard is missing, it doesn't appear in the projects page
only one help please help me fix.

The ProjectCard is located in side the projects folder, you can find it here https://github.com/websitesieutoc/platform/tree/master/app/(dashboard)/projects/components/Projects


TST: Update tests to use new data API

Updated the tests that were using the old data API. After discussion with @jbredeche a couple of the tests that have use cases we don't really support anymore(test_get_sid, for example), have been killed.
The PR itself is still WIP because I'm adding another commit that tests that the old and new data APIs return identical results for OHLCVP, but this commit itself is ready to be looked at.
UPDATE: Added a test that verifies old and new data APIs both hit the same code path.

Updated to also test history vs data.history, in addition to the ohlcvp fields.


Mixed chart with stacked bars - incorrect max height

Codepen
codepen to demonstrate the issus.

Following https://github.com/apexcharts/apexcharts.js/issues/26, In mixed chart type, should be able to have stacked bars, without affecting how the line and area chart types and have correct max height of the graph.
What is happening instead?
If enabling the stacked chart as in the example code pen, the max height is to big.

Here is a cleaned up code pen.
https://codepen.io/genadis/pen/wZXRVv
This is still using the sum of all the values as the max of the yscale, when it shouldn't. Maybe adding a different axis would help?

Hi, I'm experiencing the same issue with stacked bar + line combo, where the max height is incorrect (too big).
When displaying the bars as lump sum, the max height is correct.
Did anyone find a workaround? I've tried to manually set the max but that messes with the forceNiceScale parameter of the y-axis.


POWER_WATT was used from amshan, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead

Warnings after upgrading to HA Core 2024.1.0 4.1.2024
Logger: homeassistant.const
Source: helpers/deprecation.py:204
First occurred: 17:51:09 (17 occurrences)
Last logged: 17:52:52
POWER_WATT was used from amshan, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead.
ELECTRIC_CURRENT_AMPERE was used from amshan, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfElectricCurrent.AMPERE instead.
ELECTRIC_POTENTIAL_VOLT was used from amshan, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfElectricPotential.VOLT instead.
ENERGY_KILO_WATT_HOUR was used from amshan, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.KILO_WATT_HOUR instead.

So, where/how do I change this?

The values are assigned  in sensor.py and field native_unit_of_measurement is the one getting warnings
https://github.com/toreamun/amshan-homeassistant/blob/master/custom_components/amshan/sensor.py
    AmsHanSensorEntityDescription(
        key=obis_map.FIELD_ACTIVE_POWER_EXPORT,
        device_class=SensorDeviceClass.POWER,
        native_unit_of_measurement=ha_const.POWER_WATT,
        state_class=SensorStateClass.MEASUREMENT,
        icon=ICON_POWER_EXPORT,
        name="Active power export (Q2+Q3)",
        decimals=0,
        use_configured_scaling=True,

Valid values are included from HA:
from homeassistant import const as ha_const
so defined here:
https://github.com/home-assistant/core/blob/dev/homeassistant/const.py
...
Power units
class UnitOfPower(StrEnum):
"""Power units."""
WATT = "W"
KILO_WATT = "kW"
BTU_PER_HOUR = "BTU/h"

_DEPRECATED_POWER_WATT: Final = DeprecatedConstantEnum(
UnitOfPower.WATT,
"2025.1",
)
"""Deprecated: please use UnitOfPower.WATT."""
_DEPRECATED_POWER_KILO_WATT: Final = DeprecatedConstantEnum(
UnitOfPower.KILO_WATT,
"2025.1",
)
Electric_current units
class UnitOfElectricCurrent(StrEnum):
"""Electric current units."""
MILLIAMPERE = "mA"
AMPERE = "A"

_DEPRECATED_ELECTRIC_CURRENT_MILLIAMPERE: Final = DeprecatedConstantEnum(
UnitOfElectricCurrent.MILLIAMPERE,
"2025.1",
)
"""Deprecated: please use UnitOfElectricCurrent.MILLIAMPERE."""
_DEPRECATED_ELECTRIC_CURRENT_AMPERE: Final = DeprecatedConstantEnum(
UnitOfElectricCurrent.AMPERE,
"2025.1",
)
"""Deprecated: please use UnitOfElectricCurrent.AMPERE."""
and so on also for the other units.

Should be fixed in next release.

Should be fixed in next release.

When will that air on hacs?

Now!


Searching cards in Searching cards resource should be black and white friendly.

https://cs-unplugged-dev.appspot.com/en/resources/searching-cards/
Issue: Printing the animal searching cards in colour is adequate (I have my own personal issues with it, but I'm allowed to say that because I made them), but when using only black and white ink, the difference between the different coloured animals is hard to tell.
Currently, there are multiple instances of the same animal and the only way to tell the difference between them is because they're a different colour.
This is an issue because when printing in black and white/greyscale, it is hard to distinguish the difference between the otherwise identical animals.
This can be fixed by adding a different distinguisher like different patterns to replace the different colours. (Also it would fix my own personal issue with the green sheep looking too much like a broccoli, gross.)
Currently:

How to fix:

(Or something similar)
Also gross...

BW_Blank_solid_mix.pdf
Colour_Blank_solid_mix.pdf
+Added separate B&W and Colour versions of PDF.
+Added space under animals so text label can be added (e.g. 'Spotty Elephant' or maybe even just 'Elephant'). Left blank intentionally for translations.


Refactor for Cleaner Code & Stability

!!!NEVER MERGE INTO MAIN BRANCH!!!
Refactored by Sourcery AI and Revieved by me.
Everything seems okay.
If Merged then send any issues to LOPEKINZ/taipy or<EMAIL_ADDRESS>Stats:
2 Commits
153 Files Changed
1,195 Additions
1,123 Deletions
Most Common changes:
Replaced i with _ for Counting
Replaced "String" + "String with f"String {string}"
Changed Formats for better readability.

@jrobinAV @FabienLelaquais
This PR is far from up to date. What can we do about it?

@jrobinAV @FabienLelaquais This PR is far from up to date. What can we do about it?

close it

I would certainly spend a day looking at this and integrating those that make sense, and are still relevant with the current state of the source code.

@FabienLelaquais I can take care of this if you may

Finished in https://github.com/Avaiga/taipy/pull/1007