SIGSEGV：segmentation fault happends when close the application using QXlsx

This is my first time to use QXlsx.I tried the example HelloWorld and found an issue.
Everytime this fault will show up when I close the application. The message below will show  when I use debug mode to check:
Signal name: SIGSEGV
Signal meaning: Segmentation Fault
I believe this fault is caused by this function Document::save().
Because this fault disappeared after I blocked this function in the example HelloWorld.

Any access to the file system leads to this.

xlsxdocument.cpp -> load sheets

CellReference::init => static thread_local QRegularExpression
#153

Thank so much.
I just locate the point caused the fault.It's similar to your answer which related to the Access Modifiers thread_local in C++11.
It's in xlsxcellreference.cpp, function col_to_name(int col_num):
static thread_local QMap<int, QString>  col_cache;
I removed the thread_local, then the application exits normally.
I consider to use thread_local after I learn how to use it.

QRegularExpression heir of Q_OBJECT.
Qt self destroye all  childrens objects.
I think thread_local try did  this repeat, but there pointer to null_ptr.

Duplicate of #

not sure

Sorry for the late reply. I am working on weekdays where there is no internet.
Can you pull request the example code where the error occurs to the following repository? Me or someone can help you.

https://github.com/JayTwoLab/qxlsx-issues-156

Sorry, I just saw this message.I'm not able to help you.

https://github.com/jtv/libpqxx/issues/453

I use QXlsx from 06.09.22, Qt 5.15.2 with MinGW 8.1.0 32bits. My simplest proj:
    QXlsx::Document xlsx;
    xlsx.write("A1", "Hello Qt!"); // write "Hello Qt!" to cell(A,1). it's shared string.
    xlsx.saveAs("Test.xlsx"); // save the document as 'Test.xlsx'

The program has unexpectedly finished.
parcer.zip


CalendarExtender causes JavaScript runtime error after typing invalid date

The AJAX Control Toolkit <VERSION>
17.1.0, 17.1.1
The installation method

[ ] Installer
[x] NuGet package
[ ] A custom build from the source code

Minimal steps to reproduce the bug

Create new and empty ASP.NET Web Application project in VS (.NET 4.5)

Add AjaxControlToolkit NuGet package

Add Default.aspx Web Form

Add following controls to Default.aspx:
 <asp:ScriptManager runat="server" ScriptMode="Release" />
 <asp:TextBox runat="server" ID="PayedOn" />
 <ajaxToolkit:CalendarExtender runat="server" TargetControlID="PayedOn" />

Run application

Place focus on textbox

Type something that isn't a date (e.g. "abc")

Leave textbox using "Tab" key

Actual result
JavaScript runtime error:  Unable to get property 'getFullYear' of undefined or null reference
Expected result
No error. Invalid date should simply be ignored as does the 16.x version.
Browser(s) used
Internet Explorer 11, Chrome 59.0, FireFox 54.0
A site deployment method

[x] VS development web-server,
[ ] IIS

Duplicate #331


Other SIR models status - SIRX integration possibility

Summary of question
Besides the SIRF model, the other models (SEIRF, SEWIR, SEWIRF, etc) models you mention, are indeed reliable and can be fully used without any problems? Are they fully functional, implemented and tested? Will you demonstrate them for specific countries scenarios in the notebook analysis soon? Did you have the time to investigate and integrate perhaps the SIRX model? ->
http://rocs.hu-berlin.de/corona/docs/forecast/model/
https://github.com/michibo/COVID-19-JHU-CSSE-data-SIRX-evaluation
https://nbviewer.jupyter.org/github/michibo/COVID-19-JHU-CSSE-data-SIRX-evaluation/tree/master/
Environment

CovsirPhy version: 2.9.1
Python version; 3.8
Installation: Anaconda, Spyder, pip
OS: Windows

SIR-FV model needs the number of vaccinated people, but we do not have it.
This is used for scenario analysis at this time.
https://lisphilar.github.io/covid19-sir/usage_theoretical.html#Scenario-analysis-with-theoretical-data
SEWIR-F: we need to calculate rho1 and rho2 with case reports. (linelist).
https://www.kaggle.com/lisphilar/covid-19-data-with-sir-model#SIR-F-with-exposed/waiting-cases

SIR-FV model needs the number of vaccinated people, but we do not have it.
This is used for scenario analysis at this time.
https://lisphilar.github.io/covid19-sir/usage_theoretical.html#Scenario-analysis-with-theoretical-data
SEWIR-F: we need to calculate rho1 and rho2 with case reports. (linelist).
https://www.kaggle.com/lisphilar/covid-19-data-with-sir-model#SIR-F-with-exposed/waiting-cases

So essentially, the SIR-FV and SEWIR-F models cannot be used at all for the moment on actual data, because for SIR-FV we don't have any actual data on vaccinated people and for SEWIR-F we can't calculate these two parameters without proper linelist data?

Yes at this moment.
#281 will be discussed in advance to use SEWIR-F model or new models.

What is the advantage of SIR-X model?
https://arxiv.org/abs/2002.07572
http://rocs.hu-berlin.de/corona/docs/forecast/model/

From what I know, the only advantage is that it adds an extra compartment X for the quarantined people. With this, we can have an overview of how the number of the quarantined people changes. The SIRX model can easily be extended to SIRF-X model (I had done that on April before abandoning the whole model because of the author note at
http://rocs.hu-berlin.de/corona/docs/forecast/results_by_country/ )
I don't know if it will actually add any extra functionality to our pre-existing SIRF model, but I thought it would be useful to have that X compartment for the quarantined people.

It is difficult to use X/quarantined because we have no records of the number of quarantined cases/people.
I suggest that we use quarantine rate as a factor (Sq, Wq, Iq) of rho parameter.
Please refer to the Kaggle notebook.
https://www.kaggle.com/lisphilar/covid-19-data-with-sir-model#Factors-of-model-parameters

If this implementation for quarantine factor is something relatively easy, okay yes, otherwise I think that we can close this issue and move on from SIRX idea completely. This is not very important for now.

Thank you, we will move forward to #379 and new issues.


fix: no cache dir created when enableCaching is set to false

why
A tmp/.cache directory is created even when enableCaching is set to false.
what changed

Passing enableCaching all the way down to BaseCache
If enableCaching is false, ensureCacheDirectory will not create a directory
Added a devdependency because it eems like "@playwright/test" was missing

test plan

Sincerely appreciate your help and time here in trying to resolve this issue! There might be a simpler short-term fix in #197 in the meantime


Improve spi master constructor

Thank you!
Thank you for your contribution.
Please make sure that your submission includes the following:
Must

[ ] The code compiles without errors or warnings.
[ ] All examples work.
[x] cargo fmt was run.
[x] Your changes were added to the CHANGELOG.md in the proper section.
[ ] You updated existing examples or added examples (if applicable).
[ ] Added examples are checked in CI

Nice to have

[ ] You add a description of your work to this PR.
[x] You added proper docs for your newly added features and code.

Fix #890
This makes master mode spi constructor builder-like with all pins optional.

Is this fine?

I guess we should also start updating other drivers' APIs to be consistent, if this is the pattern we'd like to use moving forward.


Add sentry for exception/error monitoring

https://sentry.io

moving to milestone 0.0.3 so the pipeline can be confirmed functional


Tried to overwrite a file owned by another mod

When attempting to update Solver Engines, it gives me this error.
File           : GameData/SolverEngines/SolverEngines.version
Installing Mod : SolverEngines v1.5
Owning Mod     : ModuleAnimateEmissive
CKAN Version   : v1.10.0-0-gb447380 (beta)

Fix implemented in KSP-CKAN/NetKAN#1835. Should be resolved in the next run of the bot in a few hours.

This should now be resolved, thanks.

Just thought I'd mention that it's still throwing the same error.

This might not be the most satisfying answer: but I just tested and had no issue. Can you try uninstalling SolverEngines and ModuleAnimateEmissive and re-installing?

That seems to have worked, thanks.


composer: add PHP version

This prevents errors on lower PHP versions.
Not sure if the version correct. I guess it based on travis.yml :)

Thanks! Not sure how I forgot this.


Fixed docker build in other directories.

ATM the docker build script only worked in the docker folder. Now you can just call it from the root like ./docker/build.sh.

LGTM Thanks


Fixes V3 verifyOrderSignature signature to validate correctly

Sometimes (just due to how signatures are derived between 0x orders and other standards), signatures would not validate successfully when calling verifyOrderSignature. This fixes that to use a standard way of deriving a signature that can be passed to verify the typed data (since you can't pass a 0x order signature directly to a verifyTypedData signature)

https://github.com/trader-xyz/nft-swap-sdk/issues/34


feat(storage): seperate timeout between process and heartbeat

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
https://github.com/risingwavelabs/risingwave/issues/14327

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

@hzxa21 @wenym1 PTAL


brave-grpc could not work  when update Grpc to 1.2.0

an @ExperimentalApi  method had been removed in  io.grpc.ServerCall ,
So compile error occured at   BraveGrpcServerInterceptor   line 134,
change to
SocketAddress socketAddress = (SocketAddress)this.call.getAttributes().get(Key.of("remote-addr"));
would fix the bug.

Ack. Care to raise a PR?
On 28 Mar 2017 16:14, "Mylog"<EMAIL_ADDRESS>wrote:

an @ExperimentalApi method had been removed in io.grpc.ServerCall ,
So compile error occured at BraveGrpcServerInterceptor line 134,
change to
SocketAddress socketAddress = (SocketAddress)this.call.
getAttributes().get(Key.of("remote-addr"));
would fix the bug.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openzipkin/brave/issues/370, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD61xx6U1JizynMVlHJKy8BjL_1gFT_ks5rqMF4gaJpZM4MrR5p
.

actually the suggested fix won't work because grpc keys are compared by identity (so making a copy wouldn't match).

there's actually two problems here.. one is that "attributes" has been renamed to "getAttributes" the next is where did the remote address attribute go to?
Safest thing at the moment is to remove the client address functionality as it is a locks up the implementation to <grpc 1.2, which is a bad thing..

ok dropping support for client address is the best thing for now. Let's revisit later as I'm aware grpc are adding native tracing support anyway
#371

Brave 4.3 is being released now and has a new package for GRPC. we can update this to detect things about client address, but keep in mind GRPC 1.3 has a new tracing library


Optional parameters for OpenAI queries should be exposed somehow

Currently it is not possible to specify temperature, topP or seed for example when interacting with OpenAI

I see your point. Ad the system message is part of agent's responsibility, probably also openai parameters should be agent's responsibility. This mean they could be exposed in agent configuration or may be part of hard coded parameters for some specific agent (tag for example)
@fjuma your opinion?

I think it would be good to update the process_chat_completion and process_single_prompt methods to be able to take optional params to configure this and then this could be added to the agent configuration since we also have the ability to specify the system message there as @maeste mentioned.


Remove None as possible timestamp

In some cases None was assigned as the value of the timestamp, where [] should have been used instead.
Also a minor code-style fix

Codecov Report

Merging #336 (061a6e4) into develop (bd681ab) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop     #336      +/-   ##
===========================================
- Coverage    81.82%   81.80%   -0.02%
===========================================
  Files           49       49
  Lines         5353     5354       +1
===========================================
  Hits          4380     4380
- Misses         973      974       +1

Impacted Files
Coverage Δ

io/eolearn/io/sentinelhub_process.py
88.76% <0.00%> (-0.33%)
:arrow_down:

Continue to review full report at Codecov.

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


Feature request: new command ,man for reading manual pages

So, e.g.
,man direnv

would allow me to read direnv's manual with in a very similar manner as how , allows me to run it.
Use case: I often like to read manual pages as I consider using packages. This feature would allow me to do so in a faster and more convenient manner.

This could be done with , -s direnv and when https://github.com/NixOS/nix/pull/4702 is merged


RoboVac support

I discovered that the wyze-sdk GitHub project provides a Python interface for controlling the Wyze RoboVac. Before I start trying to incorporate any of that into this plugin I want to make sure I am not duplicating anyone else's effort. If you are already looking at this please let me know.
The functionality provided would all be relative to the current map selected via the Wyze app:

Select a room to clean (or "All" to do everything)
Start cleaning
Stop cleaning and return to the dock.

The actual presentation in HomeKit is an issue since HomeKit does not have a "vacuum' accessory type.
I'm thinking an On/Off button with a 'Room' property list but am open to suggestions.....

This was implemented as a separate plug-in: homebridge-Wyze-robovac


URL Preview Widget doesn't have enough right padding

My branch

Didn't actually fox this yet

Fixed


Cassie contact info should return an empty ContactInfo if there are no contacts

Closing since ContactInfo is being deprecated.


chore(release): add release notes for operator and halyard

The list of Operator releases is in title rather than in date order, so v1.10 is not at the top of the list. I'm looking into this.


fix: support for etag with quotes in IfNoneMatch header

Fix

Ignores " if present in the header IfNoneMatch

This PR will fix localstack/issues/5345

Codecov Report

Merging #5715 (ee228e9) into master (2253958) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #5715      +/-   ##
==========================================
- Coverage   96.20%   96.19%   -0.01%
==========================================
  Files         743      748       +5
  Lines       72990    73222     +232
==========================================
+ Hits        70219    70437     +218
- Misses       2771     2785      +14

Flag
Coverage Δ

servertests
36.80% <100.00%> (-0.05%)
:arrow_down:

unittests
96.13% <100.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

moto/s3/responses.py
95.66% <100.00%> (ø)

moto/iam/models.py
95.76% <0.00%> (-0.13%)
:arrow_down:

moto/acmpca/exceptions.py
100.00% <0.00%> (ø)

moto/acmpca/models.py
95.48% <0.00%> (ø)

moto/acmpca/responses.py
93.25% <0.00%> (ø)

moto/acmpca/urls.py
100.00% <0.00%> (ø)

moto/acmpca/__init__.py
100.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


The pipelinerun list paging is incorrect

The paging calculate is incorrect.

The backend does not read the parameter start.  It should be replaced by page.
Refereces

https://github.com/kubesphere/ks-devops/blob/332a5d5764e377c52acc34d35de910e7a84efc8f/pkg/apiserver/query/types.go#L127

/area console

fixed by https://github.com/kubesphere/console/pull/2323
/close
/kind need-to-verify


[Fullstack] Test announcements

Description

We need to verify that admins can create announcements and users receive them
There won't be a PR for this ticket. Instead, leave a comment with the cases you tested and any bugs you encountered

Acceptance Criteria

[ ] Admins can't send empty announcements
[ ] Users can view sent announcements
[ ] Read/unread announcements are updated properly in the user list

Other Notes

Try a variety of inputs and edge cases

Passed Tests:

Admin cannot send empty announcements
Read/unread announcements are updated properly in user list
Users can view sent announcements

Failed Tests:

If I input spaces in the description and title field, it does not give an error


Add pin flag.

Hi! Thanks for really handsome tool.
I do not want to pin dependencies in generated requirements.txt.
How can I do this? Since found no corresponding cli option would like to suggest such one like --unpin   Do not pin versions..

Does the option --comparison-specifier >= suit your needs? Run pigar generate --help for more details.


Context is part of the stdlib in go 1.7

Hum I'm not sure about this change :angel:
This means that right away after the Go 1.7 release, we absolutely need to have Go 1.7 to build traefik… I would have wait a little bit of time before doing that :angel:
/cc @containous/traefik

I tend to agree with @vdemeester, maybe we could wait a bit for that ;)

sounds reasonable, lets kick it down the line for a month or two

@errm Let's rebase it and add something in the README that we only support go1.7 for building træfik :angel:

@errm and in .github/CONGRIBUTING.md :)

This means that right away after the Go 1.7 release, we absolutely need to have Go 1.7 to build traefik

Something we've been doing at Deis for a while is that all our builds are containerized. Having builds and unit tests run within a container is mutually convenient for contributors and maintainers. Contributors don't waste time ensuring they're providing correct versions of tools in your toolchain (which might include Glide as well as Go) and maintainers don't need to ever hear "it worked on my laptop."
Note that we provide a development environment image where builds and tests run, and that's large-ish and completely separate from the substantially lighter-weight images that we bake the pre-compiled binaries into for distribution.
In case this provides any inspiration, here's our development environment: https://github.com/deis/docker-go-dev
Well crafted make targets spare us from ever having to type docker run ............

@krancour All builds have been containerized in Traefik for a long time :)

All builds have been containerized in Traefik for a long time :)

Apologies... I haven't built it from source before.

This means that right away after the Go 1.7 release, we absolutely need to have Go 1.7 to build traefik

Wondering why the above was a concern. Maybe it isn't anymore?

I think the concern was that if we changed a lot of code to be dependent on go 1.7 just a short while after it was released it would make it harder to back out of the change later if we had discovered issues with 1.7, as it is now nothing has come to light so we feel happier about using new features.

exactly what @errm said 😇
LGTM 😇

I think this is good now @emilevauge PTAL


Errors when importing external ES6 module as well as internal module (webpack resolver)

There seems to be a strange issue with eslint-import-resolver-webpack where when importing an internal module (webpack resolve alias) in conjunction with an external ES6 module (not transpiled).
import { get } from 'lodash-es'; // external es6 module
import Thing from 'app/components/Thing'; // internal module
import anotherThing from './relative/path'; // relative path

When this occurs, there are a bunch of errors on the lodash-es import complaining: Resolve error: Unexpected reserved word.
The internal module also has an error complaining that 'app' should be listed in the project's dependencies.
Removing either the external es6 module or the internal module fixes both of these errors, however.

I think #666 is the same issue.

I have the same problem. Any idea of how to solve this? It makes the webpack resolver unusable for me.


Hanging on build - Windows Server 10

Running Nadeko from source and hanging infinitely at the ShardsCoordinator. Windows server 10, 64-bit.

follow the guide 🙋

follow the From Source guide


tests: tests for iponly issue 5066

#734 with updates to the rules to make them load on alpine. ipproto:TCP; didn't load, ipproto:6; does.

Merged, some time ago. Thanks!


Summary telemetry cleanup to make data easier to analyze

Based on investigation in #8963 (Summaries are large: Number of blobs in summaries is large)
Action plan (see whole issue history for background):

Add referenceSequenceNumber to fluid:telemetry:OdspDriver:uploadSummary_end event
Add raw blob sizes (in addition to final total payload) to above. i.e. exclude size of all metadata and encoding.
I'd suggest removing "uploadSummaryWithContext" event - it does not feel like it adds any value.
Rename summarySequenceNumber -> referenceSequenceNumber for "Summarize_end" event (to be consistent across layers).

if there are any other cases like that, do the same rename.

"GenerateSummary" event should be changed to leverage PerformanceEvent and track time to generate summary.
I've love to see "GenerateSummary" repeating all the props that exist on "Summarize_end" that make sense (i.e. fullTree, timeSinceLastAttempt, timeSinceLastSummary, but not refreshLatestAck)
If we can get number of blobs to "GenerateSummary" payload, that would be awesome too!

Other than # 2, it all seems rather simple items that we can change this month.
Maybe even # 2 is simple, if not - fee free to fork into separate issue.

to clarify, for #2, is raw blob size the size of just the snapshot entries? or for each entry, we need to exclude metadata and encoding?

@agarwal-navin

For #4, as per my understanding summarySequenceNumber isn't the same as referenceSequenceNumber. summarySequenceNumer is the sequenceNumber of the summaryOp as stamped by the server. referenceSequenceNumber of the summaryOp should be logged separately.

Ah, Navin is likely right, we can scratch # 4 then.
Re # 2 - each blob has size. I'd love to see a sum of it. Naturally it will exclude all the metadata size, encoding overhead, or JSON serialization overhead. And "size" may mean different things - it may mean bytes or may mean characters (for strings). But if you trace the code, we can see that getBlobSize() that is used to populate totalBlobSize below actually calculates bytes for utf-8 strings.
That looks to be available through summaryData.summaryStats.totalBlobSize;
See IGenerateSummaryTreeResult
Looking at the code, I think summaryData.stage !== "base" case actually adds all props, so it's actually there, just not very obvious. So, I think we can scratch that too :)

Yes, blob size is there. Although, its worth mentioning that it is only available for nodes that are summarized. So its not a good representation of the total blob size of the summary.
I was also looking at the summary telemetry recently and have a couple of thoughts / changes I would like to make. I will probably do that separately but want to call out here;

The sequenceNumber in Summarize_end event is incorrect. It is logged as ackNackOp.sequenceNumber as show below: const telemetryProps: Record<string, number> = {
   ackWaitDuration: ackNackDuration,
   sequenceNumber: ackNackOp.sequenceNumber,
   summarySequenceNumber: ackNackOp.contents.summaryProposal.summarySequenceNumber,
 };

However, sequenceNumber is also logged for (almost) all telemetry as the current sequenceNumber and this conflicts with that. We should rename the above one to ackNackSequenceNumber or something like that.
We should add the GC telemetry to the summary telemetry since we usually want to see them together. For example, I want to see for a GC run, what was the seq#, ref seq#, summary seq#, etc.

We log the following telemetry when a summary successfully completes:
fluid:telemetry:Summarizer:Running:GarbageCollection_end
fluid:telemetry:OdspDriver:uploadSummaryWithContext_end
fluid:telemetry:OdspDriver:uploadSummary_end
fluid:telemetry:Summarizer:Running:GenerateSummary
fluid:telemetry:Summarizer:Running:SummaryOp
fluid:telemetry:Summarizer:Running:Summarize_end

IMO, its not very apparent what the difference between GenerateSummary, SummaryOp and Summarize_end is. Essentially, they indicate different stages of the summary process. We should rename them to indicate that so that it becomes simpler for the person looking at telemetry (our OCEs for example) to reason about the summary process.

I suggested at the top removing fluid:telemetry:OdspDriver:uploadSummaryWithContext_end.
I'd leave fluid:telemetry:OdspDriver:uploadSummary_end, as that's different layer.
Not sure about GC, but rest likely can be reorganized to be
fluid:telemetry:Summarizer:Running:Summarize_generate
fluid:telemetry:Summarizer:Running:Summarize_Op
fluid:telemetry:Summarizer:Running:Summarize_Ack
fluid:telemetry:Summarizer:Running:Summarize_end

That sounds much better. Although we don't have a separate event for Ack. So, it would be:
fluid:telemetry:Summarizer:Running:Summarize_generate
fluid:telemetry:Summarizer:Running:Summarize_Op
fluid:telemetry:Summarizer:Running:Summarize_end

is blobNodeCount the same with number 7? if so, it's already in the event

Yes, I believe is it the same.


cdc: split down/up-stream TiDBClusterConfig

Signed-off-by: mahjonp<EMAIL_ADDRESS>What problem does this PR solve?
Downstream TiDB doesn't need to apply the fail point settings sometimes, because current the same TiDBClusterConfig is applied when creating upstream and downstream TiDB cluster, so TiPocket haven't support this feature now.
What is changed and how does it work?
This PR uses two TiDBClusterConfigs to deploy a TiDB-CDC-TiDB cluster, which allows upstream and downstream TiDB clusters to use different TiDBClusterConfigs. For example:
	upstreamConfig := c.TiDBClusterConfig
	downStreamConfig := deepcopy.Copy(c.TiDBClusterConfig).(fixture.TiDBClusterConfig)
	downStreamConfig.TiDBFailPoint = ""

	suit := util.Suit{
		Config:   &cfg,
		Provider: cluster.NewDefaultClusterProvider(),
		ClientCreator: creator.PocketCreator{
			Config: creator.Config{
				ConfigPath: *configPath,
				Mode:       "binlog",
				Config:     pocketConfig,
			},
		},
		NemesisGens:      waitWarmUpNemesisGens,
		ClientRequestGen: util.OnClientLoop,
		ClusterDefs:      test_infra.NewCDCCluster(c.Namespace, c.Namespace, upstreamConfig, downStreamConfig),
	}

Check List
Tests

Unit test
E2E test
Manual test (add detailed scripts or steps below)
No code

Code changes

Has Go code change
Has CI related scripts change
Has Terraform scripts change

Side effects

Breaking backward compatibility

Related changes

Need to update the documentation

Does this PR introduce a user-facing change?:

NONE

It seems that we can only specify the upstream tidb failpoints. Is there a way to specify downsteam tidb failpoints in command line?

It seems that we can only specify the upstream tidb failpoints. Is there a way to specify downsteam tidb failpoints in command line?

upstreamConfig := c.TiDBClusterConfig
	downStreamConfig := deepcopy.Copy(c.TiDBClusterConfig).(fixture.TiDBClusterConfig)
	downStreamConfig.TiDBFailPoint = **DO_WHATEVER_YOU_WANT**
	}

As you see, you can do whatever you want on up and downstream :)


POstgreSQL IF statement not working

Loaded DBeaver 4.2.1 (+JRE)
Connected to PostgreSQL 9.6 instance (Google CloudSQL)
Ran simple test script, anonymous procedure, with IF statement as follows:
DO $$
DECLARE
a integer := 10;
b integer := 20;
BEGIN
IF a > b THEN
RAISE NOTICE 'a is greater than b';
END IF;
IF a < b THEN
RAISE NOTICE 'a is less than b';
END IF;
IF a = b THEN
RAISE NOTICE 'a is equal to b';
END IF;
END $$;
Result: internal jdbc driver error - java.lang.ArrayIndexOutOfBoundsException

I tested with DBeaver version 3.8.5, and this code ran with no problem.
Please advise as to any work-around.

This is internal error in PostgreSQL JDBC driver.
Update driver version to the most recent (e.g. 42.1.4).
You can do this in DBeaver driver manager.

Also check fix in #2171


Dependencies Not found

"net.peeweek.build-frontend": "file:D:/Unity/net.peeweek.build-frontend",
"net.peeweek.console": "file:D:/Unity/net.peeweek.console",
"net.peeweek.gameplay-ingredients": "file:D:/Unity/net.peeweek.gameplay-ingredients",
"net.peeweek.third-person-controller": "file:D:/Unity/net.peeweek.third-person-controller",

Copy them from SpaceshipDemo and edit package.json as:
"net.peeweek.build-frontend": "file:../LocalPackages/net.peeweek.build-frontend",
"net.peeweek.console": "file:../LocalPackages/net.peeweek.console",
"net.peeweek.gameplay-ingredients": "file:../LocalPackages/net.peeweek.gameplay-ingredients",
Also need to download net.peeweek.third-person-controller and config json.

Assets\Script\ConsoleCommnands\LoadLevelConsoleCommand.cs(9,44): error CS0246: The type or namespace name 'IConsoleCommand' could not be found (are you missing a using directive or an assembly reference?)
Assets\Script\ConsoleCommnands\LoadLevelConsoleCommand.cs(8,6): error CS0246: The type or namespace name 'AutoRegisterConsoleCommandAttribute' could not be found (are you missing a using directive or an assembly reference?)
Assets\Script\ConsoleCommnands\LoadLevelConsoleCommand.cs(8,6): error CS0246: The type or namespace name 'AutoRegisterConsoleCommand' could not be found (are you missing a using directive or an assembly reference?)
Assets\Script\ConsoleCommnands\LoadLevelConsoleCommand.cs(17,36): error CS0234: The type or namespace name 'Alias' does not exist in the namespace 'Console' (are you missing an assembly reference?)

Hey,man.We must have different version of references!

Sorry about the mess, I totally changed the way to reference the packages recently, now, these are located directly under Packages/ folder making them visible as Development packages. The previous workflow was a bit hectic and the references you got in that version were totally broken.

Sorry about the mess, I totally changed the way to reference the packages recently, now, these are located directly under LocalPackages/ folder (not referencing the git tags anymore). The previous workflow was a bit hectic because I did switch a lot between local references and git references. Now it's more convenient and should be more robust.


Enabling and disabling the TWIM instance

When a new TWIM instance is created, it is automatically enabled. This is very convenient in normal use. For a low power sensor, I found myself in the situation that I needed to deactivate (and later reactivate) the instance in order to safe energy. The simplest way I found to do this, was to add the "enable" and "disable" functions to the instance.
Please let me know, whether you would like to integrate this change into the main branch.

+1 to this! I have done hacks with unsafe in my project to do this from outside the hal, having it in the hal would be very nice!

Maybe there should be some safety against trying to do transfers while disabled?
For more power saving, disconnect the sda/scl pins on disable (dir=input, input=disconnected), and connect them again on enable.


[feature-request] Minimum client size

We already have an option to lock the client, but could we get the option to specify a minimum size?

I guess you can set the client size in the RuneLite settings and then enable locking

That's not setting the minimum size. That's setting it to only have that size.
Very different things.


deploy alertmanager headless service when StatefulSet is used

currently, the headless service for the alertmanager is deployed in all configurations. However, it is only needed when the alert manager is a stateful set.

LGTM, thanks Ken


Ability to add helpful error messages for humans

Issues like https://github.com/cuelang/cue/issues/52 and https://github.com/cuelang/cue/issues/171 would be a step in the right direction, so that automatic errors are more helpful.
However, there's generally quite a bit of context that cue will never be able to infer on its own. For example:
$ cat test.cue
import "list"

needs_foo: bool
foo: [...string]

if needs_foo {
	foo: list.MinItems(1)
}
$ cat test.yaml
needs_foo: true
foo: []
$ cue vet -c test.yaml test.cue
foo: invalid operation [] &! list.MinItems (1) (mismatched types list and list):
    ./test.cue:4:6
    ./test.cue:7:7
    ./test.yaml:2:7

It would be far better if cue vet gave a useful error message, like foo can't be an empty list when needs_foo is true. This is particularly important when the consumer of the errors isn't familiar with cue, or when they don't have easy access to the cue files which are vetting their yaml or json.
One can imagine other scenarios where a human-friendly error message would be far better than a generated one. For example, in the context of Kubernetes, high-level errors can be explained simply, such as Deployment "foo" refers to unknown ConfigMap "bar".
Such human-friendly errors would be optional, and ideally replace generated errors. My initial thought was along the lines of:
foo: list.MinItems(1) // foo can't be an empty list when needs_foo is true

Here's a variant from @rogpeppe:
foo: list.MinItems(1) | error("foo can't be an empty list when needs_foo is true")

@mpvl also had some thoughts on Slack, but I'll let him reply here as that seems better than copy-pasting all of his messages.

I'd add the errors label, but I assume only people with write access to the repo can do that.

I was also wondering if we could use a marker like the current @tag for something like this, such as @doc or @invalid to offer a more readable message when unification fails.
We'd need to consider whether one could attach it to nonscalar values like structs, where fields within the struct could also have values with these markers.

Is this still under active investigation for the roadmap? This is my main concern in considering CUE as a framework, and the fact that this hasn't gotten any traction in over a year is a concerning indicator as to the future of this project.

We are writing a proposal for a set of builtins that will cover this.
The new evaluator was rather a big task to complete, which pushed this to the back, unfortunately. It is not as trivial as it seems, and it requires the new evaluator.

@narzach - just to add to @mpvl's comments in https://github.com/cuelang/cue/issues/291#issuecomment-804353636.
Whilst not reflected in this issue there has been a significant improvement in error messages since v0.2.2. The new evaluator (which represents the bulk of the changes in the soon-to-be-released v0.3.0) was a pre-requisite for many of these changes.
But work on error messages is far from "done", hence the proposal for a set of builtins that @mpvl references.

This issue has been migrated to https://github.com/cue-lang/cue/issues/291.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


⚠ ClamAV has degraded performance

In c60187b, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 589 ms

Resolved: ClamAV performance has improved in 58e6747.


Excelsior desktop application

Video stream (frame sequence) processor application. Supported by VLAN Libraries.
Commands

Acquire

[] Capture
[] Import Video File
[] Import Web Page Streams

Analyze

[] Object Detection / Movement
[] Sequence Camera Orientation
[] Foreground/Background Separation

Process

[] Sequence/Transition Extraction
[] Bug Spray
[] Filter

Effects

Pixelize
Posterize
Object Chroma on Grey


"context deadline exceeded" with consecutive requests

  gotenberg:
      image: gotenberg/gotenberg:7.7
      ports:
          - "3000:3000"
      command: [
          gotenberg,
          --chromium-ignore-certificate-errors=true,
          --chromium-disable-web-security,
          --uno-listener-restart-threshold=0
      ]

With the following code:
$partialDocuments = [];
foreach ($document->getAllChildren() as $child) {
    $html = $document->renderDocument($params);
    $request = Gotenberg::chromium($this->baseUri)->html(
        Stream::string($child->getPdfFileName() . '--transient.html', $html)
    );
    $partialDocuments[] = Gotenberg::save($request, SYSTEM_TEMP_DIRECTORY . DIRECTORY_SEPARATOR);
    sleep(2);
}

Next step is to merge the separate PDF:s but cannot reach it because the third $child crashes Gotenberg.
2022-11-18 15:00:31 {"level":"info","ts":1668780031.5957,"logger":"api","msg":"request handled","trace":"2f01838c-53b2-4d19-a0ad-b005cd94b324","remote_ip":"<IP_ADDRESS>","host":"gotenberg:3000","uri":"/forms/chromium/convert/html","method":"POST","path":"/forms/chromium/convert/html","referer":"","user_agent":"Symfony HttpClient/Curl","status":200,"latency":2557421751,"latency_human":"2.557421751s","bytes_in":4011,"bytes_out":18070}
2022-11-18 15:00:47 {"level":"info","ts":1668780047.2433655,"logger":"api","msg":"request handled","trace":"4e0f0f1c-f587-4756-ae79-eccc3da6b5bb","remote_ip":"<IP_ADDRESS>","host":"gotenberg:3000","uri":"/forms/chromium/convert/html","method":"POST","path":"/forms/chromium/convert/html","referer":"","user_agent":"Symfony HttpClient/Curl","status":200,"latency":2398633335,"latency_human":"2.398633335s","bytes_in":8009,"bytes_out":18448}
2022-11-18 15:01:28 {"level":"error","ts":1668780088.1366816,"logger":"api","msg":"convert HTML to PDF: convert to PDF: chromium PDF: wait for events: wait for event networkIdle: context deadline exceeded","trace":"bf54e5fc-ad6b-4f28-b8ca-f6f41f2e3386","remote_ip":"<IP_ADDRESS>","host":"gotenberg:3000","uri":"/forms/chromium/convert/html","method":"POST","path":"/forms/chromium/convert/html","referer":"","user_agent":"Symfony HttpClient/Curl","status":503,"latency":30012295722,"latency_human":"30.012295722s","bytes_in":11648,"bytes_out":19}

The PHP exception is:
"Gotenberg\Exceptions\GotenbergApiErroed: Service Unavailable in vendor/gotenberg/gotenberg-php/src/Exceptions/GotenbergApiErroed.php:16
Stack trace:
#0 vendor/gotenberg/gotenberg-php/src/Gotenberg.php(55): Gotenberg\Exceptions\GotenbergApiErroed::createFromResponse(Object(GuzzleHttp\Psr7\Response))
gotenberg/gotenberg-php#1 vendor/gotenberg/gotenberg-php/src/Gotenberg.php(71): Gotenberg\Gotenberg::send(Object(GuzzleHttp\Psr7\Request), Object(Symfony\Component\HttpClient\Psr18Client))
gotenberg/gotenberg-php#2 GotenbergPhp.php(182): Gotenberg\Gotenberg::save(Object(GuzzleHttp\Psr7\Request), '/var/www/...')
gotenberg/gotenberg#394 GotenbergPhp->buildPdf(Object(\Document\Printpage), Object(stdClass))
gotenberg/gotenberg-php#4 Processor.php(130): Web2Print\Processor\GotenbergPhp->buildPdf(Object("

I can also confirm that this happens with version 7.8.0 on a machine with more than enough resources. If I use 7.4.2 it works normally.
NAME="Ubuntu"
VERSION="20.04.4 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.4 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

A Docker-powered stateless API for PDF files.
Version: 7.8.0
-------------------------------------------------------
[SYSTEM] modules: api chromium gc libreoffice logging pdfcpu pdfengines pdftk prometheus qpdf uno uno-pdfengine webhook
[SYSTEM] prometheus: collecting metrics
[SYSTEM] gc: application started
[SYSTEM] uno: long-running LibreOffice listener ready to start
[SYSTEM] pdfengines: pdfcpu pdftk qpdf uno-pdfengine
[SYSTEM] api: server listening on port 3000
{"level":"error","ts":1674551185.839853,"logger":"api","msg":"convert to PDF: lock long-running LibreOffice listener: start long-running LibreOffice listener: execute LibreOffice listener: context done: context deadline exceeded","trace":"6eef1be1-7f0f-48f6-b5ad-f349b5ae7e52","remote_ip":"<IP_ADDRESS>","host":"gotenberg:3000","uri":"/forms/libreoffice/convert","method":"POST","path":"/forms/libreoffice/convert","referer":"","user_agent":"python-requests/2.28.2","status":503,"latency":10001830810,"latency_human":"10.00183081s","bytes_in":14665,"bytes_out":19}

I don't know what else I can contribute with in this issue. Could never resolve it on my own.

Closing this for now. Feel free to reopen this issue if it happens with the latest version.

Today I saw a issue that looks familiar to yours. I'm running gotenberg for paperlessngx on a Synology DS918+. I was able to fix it with defining libreoffice-start-timeout.
Disclaimer: Currently one mail that repetitively failed was now processed successfully. I'm still testing as time goes by.
  gotenberg:
    image: gotenberg/gotenberg:8.8.1
    restart: unless-stopped
    command:
      - "gotenberg"
      - "--chromium-disable-javascript=true"
      - "--chromium-allow-list=file:///tmp/.*"
      - "--api-timeout=900s"
      - "--libreoffice-start-timeout=60s"
      - "--log-level=debug"
`
``


[BUG] - Pull Requests have to be reviewed before merging

Why am I getting this message when I am the person who created the issue and pull request, and it is my repository? How can I change that?

This is not a "bug" with the code but involves how this repo is set up.


A Kitura-Websocket app takes a long time to build

I tried building the test server(see this),  that we use with autobahn, with Kitura-Websocket (master branch) with 4.1, 4.2.1 and 5 in release mode. Builds take a long time:
Swift 4.1: 22 minutes
Swift 4.2.1: Completed resolution in 838.20s - 21 minutes
Swift 5: Completed resolution in 638.82s - 11 minutes

Posted a question on the SwiftPM slack, learnt that this is known limitation with the current resolver and is being worked upon. Moving this to backlog.

Since this is a known SwiftPM issue and does not block anything directly in Kitura-WebSocket, I think it makes sense to close this issue.


Upgrade to Elm v0.19

Upgrade to Elm v0.19
https://github.com/elm/compiler/blob/master/upgrade-docs/0.19.md

Done! :dancer:


The simplified MockInstance<T> type does not work with function overloads

Describe the bug
It won't work with function overloads, refer to the reproduction.
Reproduction
type error in v2
https://stackblitz.com/edit/vitest-dev-vitest-hlq3zj?file=test%2Fbasic.test.ts
No type error in v1, but seems the other overload signature is being ignored
https://stackblitz.com/edit/vitest-dev-vitest-cayu3q?file=test%2Fbasic.test.ts
System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Memory: 7.79 GB / 31.69 GB
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.1 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.5.0 - ~\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Edge: Chromium (126.0.2592.87)
    Internet Explorer: 11.0.22621.3527

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Thanks for the report. I haven't thought about this case.
Similar code on Jest has no type errors, but it looks like it still has some limitations with function overloads.
test("overload", () => {
  // they have dedicated `Spied` type to align `spyOn` return type.
  // so assignment works fine
  let spy: jest.Spied<Element["scrollTo"]>
  spy = jest.spyOn(Element.prototype, "scrollTo");

  // but only 2nd overload argument types
  spy.mock.calls satisfies [x: number, y: number][];

  // for `Mock`, probably Vitest and Jest work same.
  let mockFn: jest.Mock<Element["scrollTo"]>;
  mockFn = jest.fn(Element.prototype.scrollTo);

  mockFn(0, 1); // 2nd overload ok

  // @ts-expect-error
  mockFn({ top: 0 }); // 1st overload error
})

Probably this comes down to Parameters picking up only one of the overload
type OverloadFn = {
  (x: number, y: number): void;
  (someOptions?: { top?: number }): void;
}

// this becomes `[x: number, y: number]`
type OverloadArgs = Parameters<Element["scrollTo"]>

That's true. Like I provided above, even in v1, because that I'm using Parameters<T> manually, hence there's no type error because only 1 overload is picked up, but truly it is the limitation, since .mockImplementation() won't support another overload in that case.

Seems like a hard limitation there, emmm,..... 🤦♀

But I think at least we should try to find a way to avoid the type error there, and maybe document the TS limitation on function overloads

This type mismatch is probably because we split types here MockInstance<(this: R, ...args: A) => R>. If we can somehow preserve it as MockInstance<T[M]>, then typescript won't probably complain.
https://github.com/vitest-dev/vitest/blob/99a12aec2bb3baf361bf15afb2a9df9b0938518b/packages/spy/src/index.ts#L401-L408


[WIP] Fix #9 and #43 (port oscoin multibase abstraction to this project)

Currently a work in progress, but the key idea is that I have used a Symbol instead of a Nat to represent encodings which have the same "number" (i.e. 32 vs 32z, 58btc vs 58flickr etc).
NOTE: The "NG" module was added only to simplify the review process. Once assessed this is going into the right direction, I will ultimately replace the Multibase one with this.

exe:git-remote-ipfs from git-remote-ipfs-<IP_ADDRESS>).
cabal: Failed to build git-remote-ipfs-<IP_ADDRESS> (which is required by
see the error.
Warning: Some package(s) failed to build. Try rerunning with -j1 if you can't
| ^^^^^^^^^^^^^^^^
56 | import Servant.Client (ServantError(..))
|
Module ‘Servant.Client’ does not export ‘ServantError(..)’
src/Network/IPFS/Git/RemoteHelper/Client.hs:56:34: error:

🤔

@kim , this is now ready for review (I am off on Monday, so you might have to wait till Tuesday before cursing me 😛 ). At the end of the day the design revealed to be slightly more boilerplat-y than I would have hoped, mostly because my initial type signature decode :: Multibase -> Either String (AtBase b) was a bit of a lie, as in practice that would mean simply removing the code from the input bytestring but it's not that useful -- in practice, you also want to decode, hehe (as per original behaviour).
However, this meant that now I had no mention of the type variable b in the type signature, which meant I could invoke fromCode (as part of typeclass) anymore, which meant in turn fromCode had to live as a standalone (verbose) function.
An alternative would be to tag Multibase with a phantom type b as in Multibase b, but this is quite heavy I think, and would later on hamper our ability to treat is as an opaque blob (and implement uknownMultibase).

@kim I also now added support for the base32z encoding, which is where the Symbol approach starts to pay off.
Unfortunately I couldn't plug this back into oscoin just yet as radicle would need to be upgraded to support the change of interface (now decodeBase64 doesn't live in Multibase anymore, but in BaseN). Doing that might be wasted effort considering our plans to remove radicle from oscoin anyway.
The issue with decodeAtBase and encodeAtBase is still open, but I am happy to scrap those 2 functions from multihash-serialise.

The issue with decodeAtBase and encodeAtBase is still open

Do we have reasons to not do multibase(multihash(x))? I forget

Do we have reasons to not do multibase(multihash(x))? I forget

To be honest with you I don't know -- these shims were ported from oscoin and were already there by the time I refactored the initial strand of code 😅

@kim monsieur (I am not really here today 😁 ) , I have fixed CI and removed the encode/decodeAtBase helpers, as I don't mind keeping them in application code. Do you think you can merge this guy now or is there anything else you would like to see?

@adinapoli-mndc A rebase would be nice :)

@kim Done! 😉

Damn, I did it again, I commented with my doppelganger! 💔


pMessageIdName maybe NULL.

Author water-chika not on autobuild list. Waiting for curator authorization before starting CI build.

Author water-chika not on autobuild list. Waiting for curator authorization before starting CI build.

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

CI Vulkan-Tools build queued with queue ID 12833.

Just commenting (since I forgot to put a message in the review) - Thanks for the fix! I checked the spec and indeed the pMessageIdName can be null. Thats a rather nasty oversight.

CI Vulkan-Tools build # 1085 passed.


git cmd not right at readme

git clone https://github.com/Calinou/godot-syntax-themes.git ~/.config/godot/text_editor_themes
# instand of
# git clone https://github.com/Calinou/godot-syntax-themes.git "~/.config/godot/text_editor_themes"
...

Thanks for reporting this :smiley:


Sync

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 81.57895% with 14 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

...rc/main/java/seedu/address/model/PropertyBook.java
72.00%
7 Missing :warning:

...u/address/model/property/UniquePropertiesList.java
78.57%
4 Missing and 2 partials :warning:

src/main/java/seedu/address/MainApp.java
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ
Complexity Δ

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)
2.00 <0.00> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
91.86% <100.00%> (+1.07%)
36.00 <6.00> (+5.00)

src/main/java/seedu/address/model/UserPrefs.java
85.00% <100.00%> (+2.14%)
14.00 <2.00> (+2.00)

...roperty/exceptions/DuplicatePropertyException.java
100.00% <100.00%> (ø)
1.00 <1.00> (?)

...property/exceptions/PropertyNotFoundException.java
100.00% <100.00%> (ø)
1.00 <1.00> (?)

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...u/address/model/property/UniquePropertiesList.java
85.71% <78.57%> (+33.54%)
18.00 <11.00> (+13.00)

...rc/main/java/seedu/address/model/PropertyBook.java
72.00% <72.00%> (ø)
8.00 <8.00> (?)

... and 1 file with indirect coverage changes


Suggestion: Include a link to the community release plans/roadmap from the OCM repo

Currently the community release info is in OCM Community webpage->Community. I would like to propose we add a direct link to the community release info from the OCM repo since there's an affinity between the Github issues and the community releases in which they would be resolved in.

Thanks Mike...looks good!


Add version (or hash) to welcome page

this would be an easy way to know what version/commit we are currently in

here is a command that will return the current head commit
git rev-parse HEAD


Put executable file into cmd/nudely

Hi Katsuya.
I prefer to name nudely instead of go-nudely for an executable binary.
previously;
go get -u github.com/gotokatsuya/go-nudely -> To install $GOPATH/bin/go-nudely
now;
go get -u github.com/gotokatsuya/go-nudely/cmd/nudely -> To install $GOPATH/bin/nudely
Then, just type $ nudely -path="whatabeautifulenude.png" to execute binary not go run main -path="whatabeautifulnude.png".
This is a very common method to install executable file in golang.
Thanks for your consideration in advance.

Hi, boss.
This is an awesome pr.
Thank you so much !


#32301 - Configure tusd to not print so much during run-dev startup

Hey there, I've addressed the issue with excessive tusd logging in the run-dev script.
I made the following changes in the zerver/management/commands/runtusd.py file:
BEFORE --

AFTER --

This change adjusts the logging level to error so that only error messages will be printed during the startup of run-dev, which solves the issue of excessive logs during development.

Please fix the linter errors and commit message. Can you also point to the documentation on the log levels? I wonder if there's some tier we could use that would still log information about individual uploads (which might be useful in production at least, and maybe in development too), just not this extra on-startup content.

@timabbott Hello! I’ve added --log-level=warn in the runtusd.py file to reduce verbose startup messages. This change is intended to avoid excessive logging during startup, resulting in cleaner output.
The correct commit ID is: b082b6f with the message 'tusd: Configure logging to reduce verbose startup messages'.
Please consider this as the final commit and ignore the other duplicate commits. I’ve attached a screenshot showing the final changes for clarity.

"I am having trouble with cleaning up the commit history. Please keep only the commit 'tusd: Configure logging to reduce verbose startup messages'. Other commits are either duplicates or not essential for this change. Apologies for the extra commits. I ended up with multiple commits with the same message ('tusd: Configure logging to reduce verbose startup messages'). Please keep only the commit with ID b082b6f as it has the correct changes. The other commits with the same name can be ignored."
Thanks!

That option seems to not actually exist? I opened https://github.com/tus/tusd/issues/1216 to ask upstream how to do this; probably they need to add something and release it.
I think you're likely not ready to be picking up projects in a large OSS project yet; I suggest taking some time to master Git (we have some great resources) and also work on your software engineering habits -- asking us to review a PR that involves adding an option that doesn't actually exist and just causes tusd to crash is not contributing.


Homework-9

GlobalExpHandler

InvalidArgumentException

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
2

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0

https://video.drift.com/v/abeG0vvLnufStCO3slGsbPvSBVJ976ybfhpFBYoCvmIY/


Add CLI switch to auto approve "extract-reward-tokens" command

As the summary states, can a switch be added to the oracle-core "extract-reward-tokens" command so that reward tokens can be claimed automatically via script?

I tested ./oracle-core extract-reward-tokens ADR <<< 'YES', and it works. Would it be sufficient?

The goal is to automate reward claiming, so this solution works.  Appreciate it!


Advertising on Webtor

Is there a possibility to have an ad-free player?
Or is it the indirect way to stimulate the payment of money to your project?
I think the one you provide is an excellent service, but I try to use it in Samsung's Tizen browser, which doesn't support extensions like Adblock, and I can't watch a movie without the same Webtor.io player showing me pornographic or product advertisements. random, for the same reason I ask again, is there a way to have a clean version of the code?

Hi @urltv
You can always become a patron of webtor to remove ads, also starting from "Silver Backer" it is possible to use webtor embed without ads on specific domain. There are only two steps to do this:

Become a "Silver Backer"
Send me a message at Patreon with your domain name

@urltv Hi! Can you share your account name at Patreon?
Why I added a few users to Spam: earlier at Patreon it was possible to become a backer without any payment at first month (payment was retrieved only next month). And some users used that feature, so they got maximum tier, used all benefits all month and then just declined payment.


Error:  Unrecognized user license type id

I'm not sure if this is a bug or my inexperience is the issue.
I seem to be having an issue PortalLicenseUserTypeId field.
I've tried "Creator", "CreatorUT" and "Administrator. All throw the above error.
Should point out trying to install 10.7.1 on a single machine build over VMs

@aaron1uk I believe it's case sensitive. Try "creatorUT".
If you open the Portal Authorization json file with a text editor you will see all the available options.

Ah what a classic, moved on to another error now regarding a default user to enable automatic account creation, didn't think that was required if "EnableAutomaticAccountCreation" was set to flase?
Set-PortalSecurityConfig Response:- A default user type id must be specified to enable automatic account creation for your Enterprise portal.  The SendConfigurationApply function did not succeed.

@aaron1uk
Glad to hear the original issue is resolved. Could you open a new issue for the default user type error? That way this one can be closed since they are two separate issues. In the new thread could sgare your json file (scrub out sensitive info)?
Thanks,
Cameron K.


npm

Let's make mcclient npm installable

Ok, npm released aleph to us 😎
Can you get this ready for push and I'll make you a collaborator first thing?

oh awesome, will do 👍


chore(package): update standard to version 6.0.8

http://greenkeeper.io/

I updated all the deps separately, thanks.


Add support for service accounts

Add support for service accounts

User can login the same way as with a username/password except that they have to previde the clientId/secret.

Improve the error message when facing a 401 as it may happen if the user provides an invalid clientId/secret pair
Change project version to 2.2.0 SNAPSHOT

LGTM. The question is will token caching work fine with service accounts? Can we add a test?
Thanks 👍
Yep it will work because the caching is done one layer above - so the method that calls the service to authenticate has no idea of wheter a username is an actual username or a clientId and will store the token regardless (it's only in the client methods that the logic is different). I could add a test but it is actually already tested since it's the same method (so the test would be testing the same thing) so I think it's better to keep it like that


Add autoscaling load balancer methods

This adds three methods to the autoscaling service: attach_load_balancers, describe_load_balancers, and detach_load_balancers; all of which manipulate "classic" Elastic load balancers and their association to an autoscaling group.

Coverage increased (+0.01%) to 92.491% when pulling ab30f9aa223d20bbae820dc14ddd98ff21e95098 on captainkerk:autoscaling-attach-load-balancer into f3623e3cd3845411a2ff31a71b83f412e86f6a41 on spulec:master.

Coverage increased (+0.01%) to 92.488% when pulling 1227ad19d17c1029eb381e546e05e717dd321844 on captainkerk:autoscaling-attach-load-balancer into 5ef236e96666debfac0cf8374afc798a525c8141 on spulec:master.

Coverage increased (+0.01%) to 92.488% when pulling 1227ad19d17c1029eb381e546e05e717dd321844 on captainkerk:autoscaling-attach-load-balancer into 5ef236e96666debfac0cf8374afc798a525c8141 on spulec:master.

Coverage increased (+0.01%) to 92.488% when pulling 1227ad19d17c1029eb381e546e05e717dd321844 on captainkerk:autoscaling-attach-load-balancer into 5ef236e96666debfac0cf8374afc798a525c8141 on spulec:master.

Coverage increased (+0.02%) to 92.498% when pulling 90892d25f5838b6cb18a51ec297ed2a080229a3f on captainkerk:autoscaling-attach-load-balancer into 5ef236e96666debfac0cf8374afc798a525c8141 on spulec:master.

Coverage increased (+0.02%) to 92.498% when pulling 90892d25f5838b6cb18a51ec297ed2a080229a3f on captainkerk:autoscaling-attach-load-balancer into 5ef236e96666debfac0cf8374afc798a525c8141 on spulec:master.

Coverage increased (+0.02%) to 92.499% when pulling 90892d25f5838b6cb18a51ec297ed2a080229a3f on captainkerk:autoscaling-attach-load-balancer into 5ef236e96666debfac0cf8374afc798a525c8141 on spulec:master.

Coverage increased (+0.02%) to 92.499% when pulling 90892d25f5838b6cb18a51ec297ed2a080229a3f on captainkerk:autoscaling-attach-load-balancer into 5ef236e96666debfac0cf8374afc798a525c8141 on spulec:master.

This is so slick.

This is released as Moto 1.1.23


Add gender

Hi @bluzi and everyone: Should we add "sex" or "gender" to the JSON file structure?
Users might want to know whether a name is male, female or unisex. Especially if the name is from a language foreign to them.
Just a suggestion ...

Hey @CodeWritingCow,
I agree.
In your opinion, what would be the best way to implement it? We need to consider contributor's convenience and readability.
I mean, it could be something like: male female unisex, but it may cause trouble because or typos or people who write females or something like that.
Alternatively, we could use numbers, such as: 0 = unisex, 1 = male, 2 = female. But that damages readability so I tend to go with the first option.
Any ideas?

Single characters, such as m, f, and u, could reduce the incidence of misspellings while still keeping a decent amount of readability.

@roastchicken I was thinking the same thing. Single characters are a good compromise between using numbers and spelling entire words.
If we do use characters, we should explain the meanings of m, f and u in readme.md.

Sounds good to me, I'm in!
Anyone wants to implement it and create a PR?
You should:

Update the documentation
Add a test
Create an issue for adding genders

@bluzi I'll do it tonight!

Awesome!

Hi @bluzi, I implemented sex in my fork's readme.md and test.js. However, I'm having trouble making a PR.
This might be due to a previous PR that's open at #225 ... Can you close that PR for me? My apologies.

So all of your changes are at #225
Anyway, that's fine, the problem is I cannot merge the change because the tests failing. That's probably because you made the sex field mandatory. I think it should be optional, at least until we have it in the whole collection.

Hi @bluzi,
I've commented out the sex field tests for now. All the other tests have passed.

Opened issue #456 for adding genders.

Hi @bluzi,
I followed your suggestion and made the field optional. If the field exists in a name field, then the test checks it for validity.
If the field contains only "", should it be allowed to pass the test? Some contributors might include "sex": "" if they aren't sure of a name's gender.

If you ask me, I think it should be illegal. If you don't know the sex, don't specify the sex property at all.

I agree with @bluzi, the sex field should require a value.

@bluzi and @roastchicken, I updated the test so sex field is optional. But, if a file includes the sex field, then it cannot be empty.

Merged it, thanks a lot! @CodeWritingCow

@bluzi you are very welcome! Thanks for your patience.

This was merged two years ago in #467. The architecture changes specifically were in the two commits Add gender to name file specs and Add tests to check validity of gender.
The blames and logs are a bit confusing because there are two identically named pull requests with very similar commits, #467 and #474. But I believe the second, #474, was only to add sex fields to more names and didn't actually implement the architectural changes.


Detect time zone displacement out of range in ogr2ogr2

ERROR 1: COPY statement failed. ERROR: time zone displacement out of range: "2016/02/13 22:50:25+2445"

from:
["/services/importer/lib/importer/loader.rb:335:in `check_for_import_errors'",
"/services/importer/lib/importer/loader.rb:268:in `run_ogr2ogr'",
"/services/importer/lib/importer/loader.rb:63:in `block (2 levels) in run'",
"/services/importer/lib/importer/loader.rb:62:in `block in run'",
"/services/importer/lib/importer/loader.rb:52:in `run'",
 "/services/importer/lib/importer/runner.rb:236:in `file_based_loader_run'",

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


[UI]Trip type not changing after going to results

Expected behavior
It should be oneWay trip in /results screen

Closed by #901


[stable/sonarqube] Changing plugins doesn't restart the pods

Is this a request for help?: NO

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Version of Helm and Kubernetes: v2.13.1 / 1.11
Which chart: stable/sonarqube
What happened: When changing the list of plugins for an already installed release, the pods will just continue running and never be recreated or pick up the new plugins automatically.
What you expected to happen: Pods should be restarted gracefully and pick up the new plugins during startup.
How to reproduce it (as minimally and precisely as possible):
helm upgrade my-sonarqube stable/sonarqube --install
... (wait + check that no plugins are installed) ...
cat > values.yaml <<EOF
plugins:
  install:
    - "https://github.com/AmadeusITGroup/sonar-stash/releases/download/1.3.0/sonar-stash-plugin-1.3.0.jar"
EOF
helm upgrade my-sonarqube stable/sonarqube --install  --values=values.yaml
... (wait + check that still no plugins are installed) ...

Anything else we need to know:
I think that implementing a checksum annotation for the plugin list as suggested in the official Chart tips and tricks would solve it.

For everyone else looking into this - adding --recreate-pods to the helm command is a workaround of course.


Add #[is_variant] to enable adt.is_Variant() and adt.get_Variant()

This adds support for the following:
#[is_variant]
pub enum Maybe<T> {
    Some(T),
    None,
}

pub fn test1(m: Maybe<u64>) {
    match m {
        Maybe::Some(_) => assert(m.is_Some()),
        Maybe::None => assert(m.is_None()),
    };
}

pub fn test2(m: Maybe<u64>) -> bool {
    ensures(|res: bool|
        (m.is_Some() >>= res == (m.get_Some().0 == 3)) &&
        (m.is_None() >>= !res)
    );
    match m {
        Maybe::Some(v) => v == 3,
        Maybe::None => false,
    }
}

where is_Some, is_None, and get_Some are auto-generated by the #[is_variant] attribute-proc-macro.
is_Some and is_None are tagged as #[verifier(is_variant)] and encoded using AIR/SMT's builtin (is-Variant) (like pattern matching VCs).

Once this is approved, I'll add #[is_variant] this to, e.g. pervasive::Option.

It looks like the is_variant feature goes straight to the underlying VIR/SMT UnaryOpr::IsVariant, which is efficient.  On the other hand, m.get_Some().0 introduces a pattern match, tuple construction, and tuple selection, which is less efficient than just a direct field selection.  Is there any way we can support direct translation into a VIR/SMT field access, similar to the treatment of is_variant?

I've discussed this with @Chris-Hawblitzel offline, and implemented direct field selection, with the scheme described here https://github.com/secure-foundations/verus/discussions/41
Will wait for comments there before merging.


Question about the limits of bosun

Hi!
Are there people who use bosun and BosunReporter.NET in production to measure app metrics like service or page calls.
I am very interested in the kind of throughput that people are able to achieve.
So far, I only got the information that StackExchange's setup can cope with 15k entries per seconds which amount to about 3GB of data a day.

We have lots of metrics which are measured on every page load. These are generally aggregated by reporting intervals though (BosunReporter defaults to 30 seconds). For example, when we measure response times, we don't send one data point per page load. We send a set of aggregates (min, median, max, average, etc) every 30 seconds.
I think your question might be more of a Bosun question than a BosunReporter question though. Feel free to ask for more information over there. If you have specific questions on how to use this library to send data, then ask that here.

Hi @bretcope,
thanks for your input and redirecting me to the right place.


Update Lychee to v1.7.0

Updated lychee to solve https://github.com/lycheeverse/lychee-action/issues/191
Signed-off-by: Vipul Gupta (@vipulgupta2048) <EMAIL_ADDRESS>

Please make sure to read the CONTRIBUTING document before opening the PR for relevant information on contributing to the documentation. Thanks!

@balena-ci I self-certify!


Helpers vs. Utilities Category

I was going to open a pull-request to add rxi's terrific log.lua library to the list, but I couldn't decide whether it belonged under 'Helpers' or under 'Utilities'.  And when thinking about it, personally, I don't see a clear difference between the two categories.  Maybe we should either elaborate on their distinctions or, preferably in my opinion, merge the two together into one category?

My initial idea was:
Helper Libraries - Libraries that bundle common function and mostly serve multiple functions
Utilities - Small Meta-Libraries that help you achieve a very specific purpose which isn't game centric
But I understand your argument. Maybe we should rephrase it. Any suggestions? Vivid might be wrong in the helper category as well.
I would put log.lua in the utilities category.

Those descriptions as stated seem sufficiently defined and different to keep separate in my opinion. Are they not stated in the contributing and/or the actual list? If so, they should be.

Thank you both for the feedback!
@JanWerder
The distinction you describe---libraries of general purposes versus libraries of very specific purpose---is a useful one, in my opinion, and it would be useful to keep them in separate categories.  I don't think "Helper Libraries" and "Utilities" clearly convey that distinction though.  However, I also must admit I do not have better suggestions to provide; perhaps something like "General-Purpose Libraries" and "Game-Specific Libraries"?
I also think, regardless, we should heed the great suggestion by @Guard13007 and add a short description of categories in CONTRIBUTING.md.  For example, I know what 'Tweening' and 'Entity' and 'Serialization' mean in this context, but I can easily imagine someone just starting out who doesn't understand those terms in the context of game development.  If you think describing the categories in the Contributing document is a good idea then I'd be happy to write the patch for their inclusion.

I added a little description under the title of each Category. I would like to keep it there, since you shouldn't have to look in teh CONTRIBUTING.md to udnerstand the main list


No jira fix Missing Exporters Register

@HemanthDogiparthi12 could you just run go fmt against the files that have some inconsistencies with the formatting? After that, if the matrix tests are passing and the exporters are getting registered okay, we can go ahead and merge

@HemanthDogiparthi12 could you just run go fmt against the files that have some inconsistencies with the formatting? After that, if the matrix tests are passing and the exporters are getting registered okay, we can go ahead and merge

We can proceed to merge this. The exports tests passed on the run.


SelectableObjectProps missing some keys

Hey folks at Seats.io. I am currently using your React renderer, and I've been getting into some custom object colors/icons. I notice the description for the objectColor getter function states the following:

objectColor
Type: function(object, defaultColor, extraConfig)
By default, color will be grey if the object is not available for selection, or the category color otherwise.
A function that determines the object color. Can be based on object.status, object.category, object.selectable or on other criteria.

The field I'd like to use in my case is object.status, however the SelectableObjectProps interface does not include it. I do however see the status field in the object if I console log inside the objectColor function. I'm not sure if in this case, the status field is missing from SelectableObjectProps, or if the function argument should be something different like BookableObjectProps, which does include the status field. Or even something like (object: SelectableObjectProps | BookableObjectProps).
If you do change the function argument though, we also need this field in the objectIcon and objectLabel getter typing as well, so it would be great if it could be updated for them all.

Actually, I was able to get the correct type by first using the isSeat type guard function you have exported from the react package. Is doing that the intended behavior?

The function signature is actually correct: some of our customers let their users select sections instead of specific seats. In that case, objectColor (and the other callbacks) receive a SelectableObjectProps object that does not comply with BookableObjectProps.

In that case, it would still make more sense to to provide the function with a union of all of the possible types for object, instead of just providing the minimum overlap ((object: SelectableObjectProps | BookableObjectProps)). If done that way, users still have to check for existence of the attributes that are specific to one of the arguments in order to narrow the type of the argument. Something like this:
export const getObjectColor = (
  object: SelectableObjectProps | BookableObjectProps,
  defaultColor: string,
): string => {
  // This casting shouldn't be necessary, but the type definitions are wrong.
  // https://github.com/seatsio/seatsio-types/issues/9
  if ('status' in object && object.status === 'MY_CUSTOM_STATUS') {
    if (object.selectable) {
      return '#365DEA';
    }
  }

  return defaultColor;
};

Realistically, the SelectableObjectProps type itself would be better off as a union of the potentially selectable object types, instead of just the always available props. That would prevent the need for type assertions (which are generally not a recommended approach if avoidable), and could be narrowed natively using built-in typescript functionality.
For example, I know you guys have these type guard functions in your react package:
export const isSeat = (obj: SelectableObjectProps): obj is SeatProps => obj.objectType === 'Seat'
export const isTable = (obj: SelectableObjectProps): obj is TableProps => obj.objectType === 'Table'
export const isSection = (obj: SelectableObjectProps): obj is InteractiveSectionProps => obj.objectType === 'section'
export const isBooth = (obj: SelectableObjectProps): obj is BoothProps => obj.objectType === 'Booth'
export const isGeneralAdmission = (obj: SelectableObjectProps): obj is GeneralAdmissionAreaProps => obj.objectType === 'GeneralAdmissionArea'

These shouldn't even be necessary if you typed each of these objects with fixed string props for their objectType.

Say for example, you used these interfaces instead;
export interface SeatProps extends BookableObjectProps {
  readonly objectType: 'Seat'
  readonly center: { x: number; y: number }
  readonly isOrphan: boolean
  readonly viewFromSeatUrl?: string
  readonly parent: { type: 'row' | 'table' }

  pulse: () => Promise<void>
  unpulse: () => Promise<void>
}

export interface TableProps extends BookableObjectProps {
	readonly objectType: 'Table'
    readonly seats: NonBookableTableSeatProps[]
    readonly center: { x: number; y: number }
}

// ...etc...

export type SelectableObject = SeatProps | TableProps // ...etc...

Given the fixed value for objectType, you wouldn't even have to use a type guard to determine the type of the object props, as they'd already be easily natively determined using union discrimination. You can see in this example, that TS knows just by checking objectType what the typing of the object is:

I know your packages already do something very similar to this with your EventManagerConfigOptions, which narrows the types of the available config options as soon as you pass in the mode attribute. It would be great if this approach could be extended to the object types to avoid having to assert types, as that's not a very safe approach to using third party typescript libraries in general.

Thanks for the suggestions, we made some changes to increase type safety in v3.0.0.

@mroloux I just checked out the PR and tried the changes locally, and they work great! I was able to remove all of my casting, and everything is still working properly.
Thanks a lot for taking my recommendation into consideration!

Also, could you guys update your react package to use the newest types?


Improved code for supporting multiple Windows versions

Hi again, I read your comment in my previous PR #92 and supporting multiple Windows versions definitively complicates the code so it makes sense to limit the scope of the project.
Anyway, I made some improvements to the code for supporting multiple Windows versions and I guess you can merge them into the same branch as the other Windows 10 support:

Added a multiple-windows-versions feature flag without which the code uses the previous approach of only supporting the latest COM interfaces.

Nearly no changes were made to the code outside of interfaces.rs (compared to the code in the main branch).
Support for multiple Windows versions is done via interfaces_multi.rs which works as a drop in replacement for interfaces.rs when the feature flag is used.

Support same Windows versions as mzomparelli/VirtualDesktop: C# wrapper for the Virtual Desktop API on Windows 11..
Minimized work for adding new Windows versions.

Add new module in interfaces_multi.rs
In the new module declare the new COM interfaces.

If only the interface ids has changed then we can use the reusable_com_interface macro to easily re-use the interface definitions from a previous version, like in build_22631_3155.rs

If the code in comobjects.rs or the other files uses new methods then add those to the definitions in build_dyn.rs.

DLL Size
I checked the size of the DLL (built in release mode) with and without the multiple-windows-versions feature:

Multiple Windows versions: 363 KB
Latest Windows version only: 342 KB

Tests
I also ran all the tests and they did pass on Windows 10 (well, except for the ones using features that weren't supported):
running 12 tests
test tests::test_desktop_count ... ok
test tests::test_desktop_get ... ok
test tests::test_kill_explorer_exe_manually ... ok
test tests::test_listener_manual ... ok
test tests::test_desktop_moves ... ok
test tests::test_errors ... ok
test tests::test_move_notepad_between_desktops ... ok
test tests::test_switch_desktops_rapidly_manual ... ok
test tests::test_pin_notepad ... ok
test tests::test_pin_notepad_app ... ok
test tests::test_rename_desktop ... FAILED
test tests::test_threads ... FAILED

@Lej77 how do you get the IIDs and know what was changed for each windows version?

@eythaann Unfortunately I didn't figure that out myself. I just used the same IIDs as Slion/VirtualDesktop: C# wrapper for the Virtual Desktop API on Windows 11.. I also looked at some earlier commtis in this repository. I link to some of these places in the docs for interfaces_multi.rs.
Under the Windows version support heading of the Slion/VirtualDesktop repo it is mentioned that you can use regedit to find the IIDs of the current Windows installation. So that could be worth trying but I don't know how to discover what functions exist on COM objects.

oh I understand, I though that we can made the exposed api functions returns and error Err(UnsuportedWindowsVersion), actually the app just panics when is trying to get the unvalid COM object. I do a workaround just creating a helper function to check is I can use winvd, but return a Result::Err will be a easy way to handle error for all the Clients of this crate!.

I guess you want to check if the hardcoded IID matches the actually IID for the COM interfaces and return your Err(UnsuportedWindowsVersion) if that isn't the case? That could help but we might not need to know the real IID to do this since if the IID is incorrect then the query_service call will likely fail (since the IID is unlikely to be used by another interface). One issue with this is that it still would not detect a version mismatch where the IID was the same but the interface definition changed.
This PR does have code to detect the current Windows version and that might be useful to return an error when a too old Windows version is used. We can't really return errors for too new versions since we don't know in advance when the interfaces will change.

oh sure, I'm sure that windows-rs crate have a way to test if a IID is valid as a COM object before create it. so it could be the solution, In my case I'm using this crate for a module on my last project Seelen-UI and some users report crash on last 24h2. I for now I just will disable the Virtual desktop module for 24h2 and later I will try to do some changes in my fork to later be added to this PR, mostly to avoid cases where the program may crash without allowing the client to handle the error.

FWIW, I know this doesn't sound helpful, but to me ideal multiple-version support is different DLLs.
On your application code look Windows version and LoadLibrary older DLL.
Windows 11 has already had 6 backward incompatible IIDs, and they are not just IIDs, they change the interfaces. Managing multiple old interfaces in one code base is quite difficult.
Ideally, I would keep only the latest code in the codebase and have old DLLs available.

@Ciantic I can understand that perspective but I disagree that the tradeoff isn't worth it. This is your library of course so I will just continue to maintain a fork with my changes. There are many advantages to supporting multiple versions in the same library:

The binary size is smaller (363 KB vs about 10 * 300 KB = 3 000 KB).
Its easier to deploy a program that is statically linked than to bundle the executable with 10 or so dll files. (This is the largest issue I think.)
The old dll files might have bugs or missing features that are easier to update if we just release a single new dll file.

For example the Windows 10 dll was released before the COM interfaces were correctly defined and it also didn't include functionality for creating or removing virtual desktops. Both of which are fixed in my fork.

A program can still support newer versions by optionally loading a dll. I do this in my virtual-desktop-manager program with the vd.rs file.
I wanted an alternative to Slion/VirtualDesktop: C# wrapper for the Virtual Desktop API on Windows 11 and that library supports multiple versions.

The only disadvantage to supporting multiple versions is that it complicates the library code. That is quite a large issue but I think it is worth it, at least for me. It is quite self contained so it is really only the interfaces.rs file that needs changes, the rest of the library code can remain virtually unchanged.


feat: added avatar component

Added Avatar Component

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@2e7a5f0). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head edd6254 differs from pull request most recent head 38a7035. Consider uploading reports for the commit 38a7035 to get more accurate results

@@           Coverage Diff           @@
##             main     #131   +/-   ##
=======================================
  Coverage        ?   80.99%
=======================================
  Files           ?       54
  Lines           ?     1421
  Branches        ?      576
=======================================
  Hits            ?     1151
  Misses          ?      261
  Partials        ?        9

Continue to review full report at Codecov.

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


flutter: Expose flutterDrv, patch directories for external use

The Flutter package provides a mkFlutter function to allow customized Flutter derivations to be made.
Internally, however, it uses a flutterDrv function that calls mkFlutter with URLs generated from the given version number. Patches are also used internally, but there is no way (that I know of) to access these externally.
I propose that flutterDrv and flutter2Patches/flutter3Patches attributes get added to the attribute set along with mkFlutter, to make it easier to create custom Flutter derivations.

@babariviere @ericdallo

I was actually just about to file a bug about fluffychat which produces this error instead of building, wonder if it's related, since it's breaking on flutter? cc @mkg20001
error: hash mismatch in fixed-output derivation '/nix/store/h4pc4zxns82zllgc2r68aabs2mlgwvrz-fluffychat-1.2.0-deps-flutter-v2.10.5-x86_64-linux.tar.gz.drv':
         specified: sha256-1PDX023WXRmRe/b1L+6Du91BvGwYNp3YATqYSQdPrRY=
            got:    sha256-9nQaxpStbb8obsTqeuQnzEORFB/r9soW43kNEeTpn2E=

Sounds good @hacker1024


Different results with GetObject and FGetObject

I am trying to make thumbnails from files saved with minio. No i get different results with GetObject and FGetObject. Below is sample code without error handling:
package main

import (
        "bytes"
        "fmt"
         "image/jpeg"
         "io"
         "os"
	"github.com/bakape/thumbnailer/v2"
	"github.com/minio/minio-go"
)

func main() {
	endpoint := "play.min.io"
	accessKeyID := "Q3AM3UQ867SPQQA43P2F"
	secretAccessKey := "zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG"
	useSSL := true

	minioClient, _ := minio.New(endpoint, accessKeyID, secretAccessKey, useSSL)
        minioClient.FPutObject("files", "test", "./2.mp4", minio.PutObjectOptions{})

        // Exchange this line with commented ones and all is ok
        f, _ := minioClient.GetObject("files", "test", minio.GetObjectOptions{})

	// err = minioClient.FGetObject("files", "test", "./3.mp4", minio.GetObjectOptions{})
	// f, err := os.Open("./3.mp4")
        // defer f.Close()

        _, thumb, err2 := thumbnailer.Process(f,
		thumbnailer.Options{ThumbDims: thumbnailer.Dims{Width: uint(150), Height: uint(150)}})

	if err2 != nil {
		panic("Something wrong")
	}

	var jpgBuffer bytes.Buffer
	jpeg.Encode(&jpgBuffer, thumb, &jpeg.Options{Quality: 70})

        of, _ := os.OpenFile("./thumb.jpg", os.O_RDWR|os.O_CREATE, os.ModePerm)

	defer of.Close()
	io.Copy(of, &jpgBuffer)
}

So, it looks like the stream returned by the function GetObject is not binary corresponding to the contents of the file. If i using FGetObject and working with produced file, all is ok
2.zip
I attach zip file with mp4 movie. Please help me sort out this problem.

You are not closing the file @halfshoe when returned from GetObject()

@harshavardhana, I missed this in the example, but I do not think that this is related to the problem

@harshavardhana, I missed this in the example, but I do not think that this is related to the problem

@halfshoe that is not possible because FGetObject is using the same code underneath - so it is an implementation issue here on your end.

@harshavardhana, you can try ). I attached mp4 file on which the problem is reproduced

@halfshoe I have to install lot more packages to try this example out. One thing I noticed was that you should change "github.com/minio/minio-go" to "github.com/minio/minio-go/v6"

package main

import (
         "io"
	"log"
         "os"
	"github.com/minio/minio-go"
)

func main() {
	endpoint := "play.min.io"
	accessKeyID := "Q3AM3UQ867SPQQA43P2F"
	secretAccessKey := "zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG"
	useSSL := true

	minioClient, _ := minio.New(endpoint, accessKeyID, secretAccessKey, useSSL)
        minioClient.FPutObject("files", "test", "./2.mp4", minio.PutObjectOptions{})

        // Exchange this line with commented ones and all is ok
        reader, _ := minioClient.GetObject("files", "test", minio.GetObjectOptions{})

	 err := minioClient.FGetObject("files", "test", "./3.mp4", minio.GetObjectOptions{})
	 f, _ := os.Open("./3.mp4")
        defer f.Close()

	localFile, err := os.Create("4.mp4")
	if err != nil {
		log.Fatalln(err)
	}
	defer localFile.Close()

	stat, err := reader.Stat()
	log.Println(stat.Size)
	if err != nil {
		log.Fatalln(err)
	}

	if _, err := io.CopyN(localFile, reader, stat.Size); err != nil {
		log.Fatalln(err)
	}
}

If you see if the above example, I saved the file in both cases and did a linux diff command on the saved files and did not find any difference.
Closing this issue here, please feel free to reach out to us at https://slack.min.io for further questions.


Misinformation in M122.0.6261.169 release notes

SSE2 builds are not provided for x64, since it doesn't make sense. Every x64 CPU except the very first x64 CPU (The original 1st Gen AMD Opteron from 2003) has SSE3.

Actually many 1st gen of Athlon 64 (FX) processors has no SSE3, namely:
https://en.wikipedia.org/wiki/List_of_AMD_Athlon_64_processors#"ClawHammer"_(C0_&_CG,_130_nm)
https://en.wikipedia.org/wiki/List_of_AMD_Athlon_64_processors#"Newcastle"_(CG,_130_nm)
https://en.wikipedia.org/wiki/List_of_AMD_Athlon_64_processors#"Winchester"_(D0,_90_nm)
https://en.wikipedia.org/wiki/List_of_AMD_Athlon_64_processors#"SledgeHammer"_(C0_&_CG,_130_nm)
https://en.wikipedia.org/wiki/List_of_AMD_Athlon_64_processors#"ClawHammer"_(CG,_130_nm)
https://en.wikipedia.org/wiki/List_of_AMD_Athlon_64_processors#"ClawHammer"_(C0_&_CG,_130_nm)_2
https://en.wikipedia.org/wiki/List_of_AMD_Athlon_64_processors#"Odessa"_(CG,_130_nm)
https://en.wikipedia.org/wiki/List_of_AMD_Athlon_64_processors#"Oakville"_(D0,_90_nm)
i.e. AMD processors released on or before Oct 2004 has no SSE3.

@Alex313031 I was going to make an issue about this, or more specifically that I can't find a difference between SSE2-AVX2 and that there's no reason that I can find to build anything beyond SSE2.
My data is here, and it's what influenced me to make only SSE2 builds for r3dfox.
https://board.eclipse.cx/viewtopic.php?t=669

@roytam1 Well, I meant Bulldozer based FX


Allow language to be passed into document object

This is a companion to this PR against cucumber-ruby, which allows language to be passed in as a command line option. It allows the language to be passed into the Cucumber::Core::Gherkin::Document object on initialization, and creates a TokenMatcher object using that language when parsing the document.

Do you think we should ship this in a 1.5.1 release rather than bundling it in with 2.0? That's the one reason I'm not hitting the merge button right now.

Since it's not a breaking change, I think it can go in with the next minor release.

I agree @danascheider, but (having had a discussion with @brasmusson on the core team hangout on Friday) we think we'll go for a quick 3.0 release anyway, so I don't think we need to worry about making a minor release. If we need to we could always cherry-pick this. I'll merge it.


[Draft] Adding Multi device iterator Serialization and De-serialization

Context:
The idea is to be able to save and restore iterators (The iterators that can be saved) for multi worker training. This will allow for training to be resumed mid-epoch instead. This reduces wasted compute cycles when restarting training jobs.
With this change the Backup and restore keras callback can include the iterator (if supported), and actually restore the keras model to a state mid epoch also.
Description:
Adding a serialization and de-serialization to multi device iterator.
Added Save and Restore in both the Multi Device Resource and the Multi Device Buffer.
Design.
New operators added for Multi Device Iterators to serialize and de-serialize
Multi device buffer will save its buffer and host_iterator.
Multi device Resource will restore by creating a new buffer because the host iterator is const.
It will then call the multi device buffer to restore its own buffer.
Test.
Using a Range Dataset(10)
Save after 0-5, then restore in a new session, and verify 6-9

@sboshin  This PR is in draft, any update on this? Please. Thanks!

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

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

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

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


Outdated GIT commands

Type: Bug
Doing a Fetch produces warning messages in the Git log:
2023-04-21 16:42:41.864 [info] > git status -z -uall [140ms]
2023-04-21 16:42:50.557 [info] > git fetch [3876ms]
2023-04-21 16:42:50.557 [info] warning: git-credential-manager-core was renamed to git-credential-manager
warning: see https://aka.ms/gcm/rename for more information
warning: git-credential-manager-core was renamed to git-credential-manager
warning: see https://aka.ms/gcm/rename for more information
..snip..
2023-04-21 16:42:50.631 [info] > git config --get commit.template [64ms]
2023-04-21 16:42:50.645 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/feature-?????refs/remotes/feature-?????[72ms]
2023-04-21 16:42:50.755 [info] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [98ms]
2023-04-21 16:42:50.799 [info] > git status -z -uall [149ms]
2023-04-21 16:42:52.862 [info] > git config --get commit.template [69ms]
2023-04-21 16:42:52.867 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/feature-?????refs/remotes/feature-?????[77ms]
2023-04-21 16:42:52.992 [info] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [113ms]
2023-04-21 16:42:53.028 [info] > git status -z -uall [155ms]
2023-04-21 16:42:57.090 [info] > git log --oneline --cherry feature-?????...feature-?????@{upstream} -- [70ms]
2023-04-21 16:42:59.769 [info] > git pull --tags origin feature-?????[2671ms]
2023-04-21 16:42:59.769 [info] warning: git-credential-manager-core was renamed to git-credential-manager
warning: see https://aka.ms/gcm/rename for more information
warning: git-credential-manager-core was renamed to git-credential-manager
warning: see https://aka.ms/gcm/rename for more information
From https://github.com/?????/?????

branch              feature-?????-> FETCH_HEAD
2023-04-21 16:42:59.848 [info] > git config --get commit.template [69ms]
2023-04-21 16:42:59.859 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/feature-?????refs/remotes/feature-?????[75ms]
2023-04-21 16:42:59.970 [info] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [101ms]
2023-04-21 16:43:00.030 [info] > git status -z -uall [166ms]
2023-04-21 16:43:02.074 [info] > git config --get commit.template [73ms]
2023-04-21 16:43:02.081 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/feature-?????refs/remotes/feature-?????[74ms]
2023-04-21 16:43:02.199 [info] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [103ms]
2023-04-21 16:43:02.245 [info] > git status -z -uall [157ms]

VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.20348
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-12700H (16 x 2688)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_softwarewebgpu: disabled_off

Load (avg)
undefined

Memory (System)
23.35GB (6.72GB free)

Process Argv
--folder-uri file:///c%3A/Users/Administrator/source/repos/FMSystemsGroup/employee-rso365-addin --crash-reporter-id f2bff332-4d8d-47af-8826-cfdd04d7776a

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

csharp-to-typescript
adr
1.12.1

vscode-eslint
dba
2.4.0

xml
Dot
2.5.1

prettier-vscode
esb
9.12.0

classic-asp
ili
0.0.4

powershell
ms-
2023.3.3

csharp2ts
raf
0.0.26

code-spell-checker
str
2.20.3

asp-classic-support
zbe
0.6.1

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
nodejswelcome1cf:30587006
282f8724:30602487
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
showlangstatbar:30672706
azdwalk:30721579
pythonms35:30701012
pythonfmttext:30716742

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.77.3. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

The warnings are coming from the Git Credential Manager and not VS Code. I would suggest that you install the latest version of Git for Windows as that includes the latest version of Git Credential Manager.

I am running the lastest version: git version 2.40.0.windows.1

Yes, happens from Terminal too.
Did some hunting ad found this reference: https://github.com/git-ecosystem/git-credential-manager/blob/main/docs/rename.md
Apparently a manual edit is needed of .gitconfig to remove the warning. Just updated an existing installation doesn't fix it.