Wrong code documentation and possibly non usable function

file : include/faker-cxx/String.h
`
/**
* @brief Returns shuffled STL container.
*
* @tparam T an element type of the container.
*
* @param data The container.
*
* @return Container with shuffled elements.
*
* @code
* Helper::arrayElement(std::string{"abcd"}) // "dcba"
* @endcode
*/
template <class T>
static std::vector<T> shuffle(std::vector<T> data)
{
    std::shuffle(std::begin(data), std::end(data), pseudoRandomGenerator);
    return data;
}

`
Code example should be of Helper::shuffle()
Also I don't think we can pass a string to the shuffle function, no viable conversion from std::string to std::vector

Thanks for creating the issue :)

https://github.com/cieslarmichal/faker-cxx/pull/275


Update sinon-chai.d.ts

declare module chai {
interface Expect {
callCount(count: number): Expect;
}
}
Added --> callCount(count: number): Expect;

@zeethree50 thanks mate!

note
https://github.com/domenic/sinon-chai#assertions


Automatic PR from RestAPI-PR611

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/611

Coverage remained the same at 55.64% when pulling f635c9f038dc496817346bc76f5d4ba69ed3dbb4 on AutorestCI:RestAPI-PR611 into ab67ea477cc00a76f9f6115b943a53fb0763056f on Azure:dev.


Acoustic Decompostion

Can someone explain to me what is exactly happening in the acoustic decomposition ?
as an example , Now i have 180 value of MGC ( 60 , 60 delta , 60 acc. )
What i exactly do to make them just 60 ?
and what if i took the first only 60 values would it make a lot of differences ?
And where is the V/UV used ?
Thanks in advance

if you took the only first values you will only keep the static coefficients and the rendering is not going to be good.
Normally, when you get the coefficients, you should apply the MLPG generation algorithm. You can have a look at this file: https://github.com/CSTR-Edinburgh/merlin/blob/master/src/frontend/parameter_generation.py
then, you get the "final" mgc/lf0/bap. You use SPTK and the vocoder of your choice (STRAIGHT, WORLD depending on what you used to extract your coefficient for the training) to render the signal from it

You can use just first 60 values for both training and testing as in this paper https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/43266.pdf, final output layer should be LSTM layer to get a decent quality speech.
And V/UV values are used to make voiced and unvoiced decisions in F0 (fundamental frequency) values. In training, the F0 values are interpolated for unvoiced regions so we need to revert back based on V/UV values.

Hi all.
I guess a final LSTM layer would be more performant when synthesizing than MLPG?
Also MLPG can not be run on a single feature vector, right?
I've tried to compare the bandmat implementation in merlin with the MLPG implementations of flite and hts_engine - by chance, does anyone know the crucial differences?
I'm trying to come up with a C/C++ implementation that works with the merlin features and variances. I assume the output features of the DNN are considered to be the mean values of a Gaussian and the variances stored in the vars folder are.. 1 variances for each feature dimension?

I guess a final LSTM layer would be more performant when synthesizing than MLPG?
No, clear answer. It depends a lot on the duration of utterances.

Also MLPG can not be run on a single feature vector, right?
Ture.

I've tried to compare the bandmat implementation in merlin with the MLPG implementations of flite and hts_engine - by chance, does anyone know the crucial differences?
I would like to know your observation, haven't tried myself.

I'm trying to come up with a C/C++ implementation that works with the merlin features and variances. I assume the output features of the DNN are considered to be the mean values of a Gaussian and the variances stored in the vars folder are.. 1 variances for each feature dimension?
Are you proposing something similar to this https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/42020.pdf ?

I'm comparing the LSTM variants with a regular feedforward DNN.
I've exported the weights from theano to my own protobuf format and loaded them into a tiny-DNN (https://github.com/tiny-dnn/tiny-dnn) network. After some tinkering I got it to work and produce acoustic features that produce the desired speech when re-exporting to merlin.
Currently I'm transforming only the static features for WORLD and started to look at the MLPG algorithm in Merlin...
So my observations until now:
tiny-DNN is really easy to integrate, runs on most platforms in 32 and 64 bit. But I fear it will be too slow for live synthesis. And: It doesn't support RNNs/LSTMs yet. Adding the MLPG now will make it even slower. There might be a few options to work around that but.. yeah.
I ran the network also with tensorflow in python and it seemed much faster. But Tensorflow is quite a beast to get into e.g. a SAPI DLL on Windows ;). Also it typically comes only with 64 bit build files, while a lot of SAPI applications are 32 bit only.
Integration in iOS and Android seems easy on the other hand.
With the LSTM you could probably run it frame by frame and run each frame through the vocoder, so doing a sort of streaming synthesis.


Updated to 1.0.7

The archive/release.zip no longer exists, so the OCP build fails.

Really?
I just tried to download https://github.com/hawkular/hawkular-grafana-datasource/archive/release.zip ... and succeeded.

I keep getting a 500 error:

localhost:hawkular-grafana-datasource garethah$ curl -L https://github.com/hawkular/hawkular-grafana-datasource/archive/release.zip
500: Internal Server Error

Yep, I have randomly sometimes an error, sometimes success.

Closing. Putting issue down to github being flakey.


Option to retrieve js code from file?

Are there any plans to read javascript from a file rather than entering the code directly in the widget? It would enable quicker development in external code editors

You can already do this by including a Javascript file to your index.html and using the modules and/or functions you defined in there in the snippets. That's how we are currently using it in most projects.

quite often I have a scenario where I just want to load a particular bit of code on one page or section and/or want to refresh when the section it's on is refreshed or made visible - I'd rather not have it loading for all pages, or have to split code into two blocks (with some still written in the widget)

The widget is triggered when a dataview is refreshed. Also conditional visibility in Mendix applies to the widget. So I can't seem to understand the real problem. Can you make an example (mendix) project of what you are trying to do? And explain where the problem exists?

What I really want is to have the widget as it is now, but instead of writing code in a text box in the widget, I can reference a .js file in my project folder. There is no additional use case that your widget doesn’t already cover, but it means I can work with .js files and a full code editor with all the nice developer that entails. Currently i need to copy and paste between my code editor and the widget, and if I am in a quick build/test cycle this can get a bit irritating.
I don’t want to include this code in the index.html file as I only want it to be loaded when it is needed - mendix is bloated enough as it is without lots of extras coming down the pipe when they may not be needed

Ah ok! But that's what I mentioned earlier.

You can already do this by including a Javascript file to your index.html and using the modules and/or functions you defined in there in the snippets. That's how we are currently using it in most projects.

How to do this, in small steps:

Create a JS file in your theme folder. (located in the Mendix project folder)
Include this JS file by a script tag in your index.html file.
Create code in the JS file (with your own IDE) in a way that you can call it from the widget. (global functions or modules)
Insert the JavaScript Snippet widget on a Mendix page.
Write a bit of JavaScript to call the modules/functions defined in your JS file.
Modify code in your JS file via your IDE and rerun Mendix to see the changes.

I hope this helps you. This is a best practice we use in our projects all the time.

I'm aware of how to do what you've described but it still doesn't solve my issue. I will explore other options. Thanks for your time


[camerax] Implement camera preview

Implements Flutter camera API methods related building, pausing, and resuming a preview.
In order to implement this, I also needed to implement methods to create an initialize the camera, as well as callback methods to send information related to camera initialization, the device orientation changing, and native camera errors.
I also added back the example app used in the other plugins, as it will be needed for integration testing and easier to verify feature parity is ultimately reached.
Fixes https://github.com/flutter/flutter/issues/112658.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
[x] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

The only change I would consider is changing the _bindPreviewToLifecycle (and unbind) into helpers that can handle all of the potential use cases (i.e. a _bindUseCaseToLifecycle).
But I think that change is probably easier to make once we have more use cases to work with and it is clearer what assertions are shared.

I agree! I thought the same thing.

@reidbaker Regarding the comments you left on the example app, I agree with them, so I plan to make a cleanup PR to update the camera example apps across the board. I just coped the one from camera/camera here, and I would like the examples to remain consistent.


modify data file name

Current coverage is 45.45% (diff: 0.00%)

Merging #238 into master will increase coverage by 1.44%

@@             master       #238   diff @@
==========================================
  Files            11         11
  Lines          8989       8990     +1
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           3956       4086   +130
+ Misses         3986       3845   -141
- Partials       1047       1059    +12

Powered by Codecov. Last update f853302...1386574

LGTM


Add log to blacklist / reduce free calls

It would be cool if there is 1 API call for all kinds of info.
For example /versions or /info (just examples) with the following:

Home Assistant version
OS type / version
Hassio Supervisor version
Beta/dev/stable channel information
The architecture of the system

In general, displaying this kind of information in the add-on logs, greatly helps debugging issues.


Unable to create SSL context

With  Kitura (.Package(url: "https://github.com/IBM-Swift/Kitura", majorVersion: 1, minor: 4)) adding SSL Support ( Self-Signed ) giving the error
"Error accepting client connection: Error code: 12, ERROR: Unable to create SSL context."
Whereas the same code is working fine with Kitura Version (Package(url: "https://github.com/IBM-Swift/Kitura.git", majorVersion: 1, minor: 0))

@gtaban @shmuelk
It looks like this problem was originally introduced with IBM-Swift/Kitura-net#155 in this commit between Kitura-net 1.3.0 and 1.3.1
On that commit, the problem goes away with commenting out this line that was added in that commit. However, commenting out that same line on master does not fix the issue. So it looks like some other changes since then makes the problem reappear.
Further investigation is needed to find out how this should be properly fixed.

@navneet thanks for the research work.
@billabt I did an additional test here, after you pointed out to me that SSL on Kitura 1.2 works and fails on later versions. I commented out line 1305 in Socket.swift (self.delegate?.deinitialize() ). This is in the function deinit of Socket.swift. After commenting out that line of code SSL works.
I believe the problem is in the deinitialization of SLLService instances somehow, or somehow they are being shared across Socket instances.

Fixed in BlueSocket v0.12.18 and BlueSSLService v0.12.12.

@billabt Thanks. That fixes the problem for the most part. But in some new unit tests I added in branch 962, there is a new failure:
xctest(6295,0x70000666b000) malloc: *** error for object 0x7fb5c9653af0: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

It seems to occur in this line: let status: OSStatus = SSLWrite(sslContext, buffer, bufSize, &processed) in SSLService. Could you take a look to see if there's something wrong with the test or some other lingering problem?

Did you set a breakpoint in malloc_error_break?  If not, can you try the test again with that breakpoint set and then post the stack trace?

There's actually no freeing of buffers taking place anywhere in this section of code.  It's possible that it's happening inside SSLWrite itself or just prior to it...  The stack trace should give us a clue.

@billabt Here is the stack trace:

@billabt Turns out this was caused by a bug in Kitura where it was calling Socket.write() after calling Socket.close() in some circumstances. I will put in a fix for Kitura. It may be worthwhile to put in a check for this in Socket and/or SSLService as well.

@keshavakarthik Please try again with the fixes in Kitura 1.6


Update index.html

I am adding some comment line to improve understanding the source code.

@deepm019 Thank you, but as I said before, we are going to pass on these.


Grammar railroad diagram

Looking for a railroad diagram for the Swift language I did converted you grammar and https://github.com/swiftlang/swift-book/blob/main/TSPL.docc/ReferenceManual/SummaryOfTheGrammar.md and it seems that there is several missing items on the official documentation.
See here https://github.com/swiftlang/swift-book/issues/337 .

There are a few reasons why this doesn’t match the official grammar. One is that, for reasons of parsing latency, some of the constructs in the grammar have to be simplified to reduce the number of unique parsing states (pattern matching, for instance) — this is done in places where we can make the grammar more permissive without losing specificity. Another is that the actual Swift compiler seems to encode a variety of precedence rules that don’t make it into the grammar, so ambiguous cases would be handled differently between the compiler and a strictly translated version of the grammar. Another third reason is that simply isn’t what I started with when I built this as a hobby project, so the names differ for things I added early.
If you have specific missing features you need then please list them, but simply linking to an issue describing the EBNF for the two grammars is not particularly actionable for me.


Remove outdated time diff info for istioctl ps command.

Please provide a description for what this PR is for,
Since the Nonce changes to UUID, so remove time diff info for istioctl proxy-status command
This PR also include unit test fix and go imports reformat.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure

Hi @AsCat. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@AsCat: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-presubmit-tests-master
36d0520fbeb9953499739b56dabf887bf348d68b
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@AsCat: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-presubmit-tests-master
d670ae5d35923bed06ca2b6042ca18e0e61b58c1
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I think we need to cherrypick to release branch (release-1.1/release-1.2/release-1.3) as well. Thanks.

@AsCat It seems the auto-cherrypick does  not work. Could you manually create a PR to merge this fix to release-1.3? Thanks.

@AsCat It seems the auto-cherrypick does not work. Could you manually create a PR to merge this fix to release-1.3? Thanks.

Sure, i'm now working on it.


Getting issue "no variable found with name: response". Below is complete description.

My code was running fine before adding the 'And match response' step. After adding this step, i am getting below error. The interesting part is that even after removing this step, the error still occurs. I tried maven clean, project clean and other stuff. Karate version used is 0.9.4.
[main] ERROR com.intuit.karate - evaluation of 'karate-config.js' failed: javascript evaluation failed: read('classpath:karate-config.js'), no variable found with name: response

@RYRAJESH sorry, you have to follow this process: https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue

@RYRAJESH Getting the same issue. Persists even after I've removed everything. Did you figure out what it was?

Hi,
Yes, Actually i added some comment in the .js file in the first line. When
i removed that comment, it started reading .js file.
I don't know how.
On Wed, Oct 23, 2019, 2:45 PM UmairKamran<EMAIL_ADDRESS>wrote:

@RYRAJESH https://github.com/RYRAJESH Getting the same issue. Persists
even after I've removed everything. Did you figure out what it was?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/intuit/karate/issues/916?email_source=notifications&email_token=AJ6WB6YUHWAXEVN5NY6QXXDQQBBPFA5CNFSM4I7BJCF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECBITNI#issuecomment-545425845,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ6WB64FJCS5UL5AP4VYMSLQQBBPFANCNFSM4I7BJCFQ
.

I can verify that this worked for me too.

Just ran into this, yes...don't have a comment as the first line in your JS

for me, the root was in a place much before response - when I set path
And path /path/path - forgot to get the path into quotes.
And path '/path/path' worked well

I had a comment as the first line of the ".js" file which was causing this issue. I know this would be documented somewhere not to have this first line as comments but I wish the error message was helpful. The following SO page helped me.
https://stackoverflow.com/questions/46918627/in-karate-dsl-calling-a-javascript-file-returns-java-lang-runtimeexception

@arisingh this is an open-source project, anyone here is welcome to submit a PR to improve the docs or code. I hope that is clear !

I understand @ptrthomas. I added this comment because google sent me to this page when I searched for the error - so I hope it will help others in my situation.
Also, it will help if instead of someone starting from scratch to find a solution, if someone who knows more about the codebase, to point me (or anyone else who may want to fix this) in the right direction. e.g. which part of the code may need change. Anyone knowing the codebase should be able to point this out quickly - which would then enable me (or anyone else) to create a fix in a reasonable amount of time.

@arisingh you can start by looking at the new version. there is a good chance this issue may be fixed or improved: https://github.com/intuit/karate/issues/1373#issuecomment-741991267


RFC: Use MAX_BLOB_COMMITMENTS_PER_BLOCK as max length  for BlindedBlobsBundle SSZ lists

Context
In the below consensus PR, MAX_BLOB_COMMITMENTS_PER_BLOCK was introduced and used in the SSZ specification for blob_kzg_commitments in the deneb beacon block:

https://github.com/ethereum/consensus-specs/pull/3338

The SSZ representation of KZG blobs commitments are currently different in BeaconBlockBody and BlindedBlobBundle:
BeaconBlockBody:
class BeaconBlockBody(Container):
    ...
    blob_kzg_commitments: List[KZGCommitment, MAX_BLOB_COMMITMENTS_PER_BLOCK]  # [New in Deneb:EIP4844]

BlindedBlobsBundle:
 class BlindedBlobsBundle(Container):
     commitments: List[KZGCommitment, MAX_BLOBS_PER_BLOCK]
     proofs: List[KZGProof, MAX_BLOBS_PER_BLOCK]
     blob_roots: List[Root, MAX_BLOBS_PER_BLOCK]

I'm interested in hearing people's thought about whether MAX_BLOBS_PER_BLOCK or MAX_BLOB_COMMITMENTS_PER_BLOCK should be used in the BlindedBlobsBundle SSZ specification. AFAIK this has no impact on serialisation or deserialisation, but will be used in computing the signing root for the BuilderBid.
I think we'd be okay either way, as this tree hash root isn't stored anywhere and only used for bid signatures, which means it's short lived. Using MAX_BLOB_COMMITMENTS_PER_BLOCK for max length gives us consistency with the beacon block representation, which means in some languages we could reuse the same type (not necessary important I guess?). On the other hand, using MAX_BLOBS_PER_BLOCK means it's probably more consistent with the rest of the API specs - maxItems: 6 is specified for all blob related lists, including blobs_sidecars.
I don't have a strong opinion here, keen to hear people's thoughts!

To me it makes sense to use MAX_BLOB_COMMITMENTS_PER_BLOCK. We wouldn't have to worry about updating it if we have a hardfork to update MAX_BLOBS_PER_BLOCK.

I'm convinced to use MAX_BLOB_COMMITMENTS_PER_BLOCK as well - I think there isn't much upside to go with the alternative, and it isn't worth having to add logic / types to update the signing root computation between forks on both the relay and CLs.

This does end up impacting the hash tree root of List because max size is used in chunk_count in the spec: https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md?plain=1#L136
which is passed to get_power_of_two_ceil here: https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md?plain=1#L185
so in this case if MAX_BLOBS_PER_BLOCK is 9 or higher (or 4 or lower) the root changes

This does end up impacting the hash tree root of List because max size is used in chunk_count in the spec: https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md?plain=1#L136
which is passed to get_power_of_two_ceil here: https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md?plain=1#L185
so in this case if MAX_BLOBS_PER_BLOCK is 9 or higher (or 4 or lower) the root changes

interesting @realbigsean , there may be a discrepancy in the specs, as I was referencing this: https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md#merkleization
for the chunk_count where I think for this example would be indifferent to the size of the list

I think it's consistent cause N is the max size of the list (what we're updating) in List[B, N]


Refactor: Use nullish coalescing operator to simplify undefined checking

Typescript support this feature in version 3.7
I thought it's a good idea to replace  comparison between value and undefined.
{
    disabled: disabled ?? isSubmitting,
};

would complile to:
{
    disabled: (disabled !== null && disabled !== void 0 ? disabled : isSubmitting),
};

I also upgraded prettier to support this syntax feature.
https://github.com/prettier/prettier/issues/6595

Coverage increased (+1.5%) to 80.714% when pulling dc7c6737f42dc598649ef7762c417f7afa93358f on Mosoc:master into 29848beb73bc4aa53c01e227376e835f58f036bc on stackworx:master.


thunderFX : pass to remove empty autocast regions

Fixes https://github.com/Lightning-AI/lightning-thunder/issues/1342

Ping @t-vi for review and approval


Request: Please produce a deployment guide without rover

The use of the rover tool complicates the deployment from an enterprise perspective and makes the deployment dependent on a bespoke (and rather poorly documented) piece of tooling.
Enterprises therefore have to interpret the entire deployment through the lense of rover, before they can conceptualise it within their own existing enterprise deployment toolsets (e.g Jenkins, Gitlab, Ansible). This means all code and configuration within the repo must be understood first in the rover context before it can be implemented within an organisations existing deployment model. This makes the landing zone example difficult to evaluate, and as difficult as implementing LZ examples from scratch without a guide!
Ideally, deployment documentation should show how to deploy using standard, widely adopted tooling for which there is vendor support, or at least widespread open source community support, e.g BASH, az cli, Powershell, Ansible, Python etc ... "rover" does not meet this ideal.

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

ID: 2e2bf90e-7bf4-d00c-c3fe-af0a3668d2d9
Version Independent ID: 50e5d069-0928-a483-753a-9b61e47d47ef
Content: Use Terraform to build your landing zones - Cloud Adoption Framework
Content Source: docs/ready/landing-zone/terraform-landing-zone.md
Service: cloud-adoption-framework
Sub-service: ready
GitHub Login: @arnaudlh
Microsoft Alias: brblanch

Hi @archmangler
Sorry for the delay.
Thanks for the feedback.
In the doc, the rover benefits are explained. It is a core part of the solution as written and it was selected in a deliberate and intentional way.
We are continually evaluating how these articles serve the needs of the community. We will share your thoughts with our internal team.
#please-close


Add v20.1.4 release notes issues

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9cfc57b42ab47208e86a1ecc8071550c565a0476/
Edited pages:

releases/v20.1.4.md


Installation question

Where to put the  epoch=1-step=8687.ckpt checkpoint?
Which dinov2 checkpoint to download and where  to put it?
revise /configs/anydoor.yaml for the path (line 83) <- what to revise?

You can put it wherever. Just edit the path of "pretrained_model" in inference.yaml and demo.yaml to match where you put it. I.e., if you put it at the root, just use the value "epoch=1-step=8687.ckpt" for it
I got this link from the repo: https://dl.fbaipublicfiles.com/dinov2/dinov2_vitg14/dinov2_vitg14_pretrain.pth
Just as earlier, you download the dinov2 model, and put it somewhere in your folder. Then you should edit "path/dinov2..." to the actual path to where you chose to put it

Actually anyone use anydoor for AMD gpu? Does it work or it only works for Nvidia gpu?

I got this error. Anyone know what I did wrong?
Traceback (most recent call last):
File "F:\AnyDoor-for-windows\run_gradio_demo.py", line 32, in
model = create_model(model_config ).cpu()
File "F:\AnyDoor-for-windows\cldm\model.py", line 26, in create_model
model = instantiate_from_config(config.model).cpu()
File "F:\AnyDoor-for-windows\ldm\util.py", line 81, in instantiate_from_config
return get_obj_from_str(config["target"])(**config.get("params", dict()))
File "F:\AnyDoor-for-windows\cldm\cldm.py", line 310, in init
super().init(*args, **kwargs)
File "F:\AnyDoor-for-windows\ldm\models\diffusion\ddpm.py", line 565, in init
self.instantiate_cond_stage(cond_stage_config)
File "F:\AnyDoor-for-windows\ldm\models\diffusion\ddpm.py", line 632, in instantiate_cond_stage
model = instantiate_from_config(config)
File "F:\AnyDoor-for-windows\ldm\util.py", line 81, in instantiate_from_config
return get_obj_from_str(config["target"])(**config.get("params", dict()))
File "F:\AnyDoor-for-windows\ldm\modules\encoders\modules.py", line 287, in init
dinov2.load_state_dict(state_dict, strict=False)
File "F:\AnyDoor-for-windows\venv\lib\site-packages\torch\nn\modules\module.py", line 2152, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for DinoVisionTransformer:
size mismatch for cls_token: copying a param with shape torch.Size([1, 1, 384]) from checkpoint, the shape in current model is torch.Size([1, 1, 1536]).
size mismatch for pos_embed: copying a param with shape torch.Size([1, 1370, 384]) from checkpoint, the shape in current model is torch.Size([1, 1370, 1536]).
size mismatch for mask_token: copying a param with shape torch.Size([1, 384]) from checkpoint, the shape in current model is torch.Size([1, 1536]).
size mismatch for patch_embed.proj.weight: copying a param with shape torch.Size([384, 3, 14, 14]) from checkpoint, the shape in current model is torch.Size([1536, 3, 14, 14]).
size mismatch for patch_embed.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.0.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.0.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.0.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.0.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.0.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.0.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.0.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.0.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.0.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.0.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.1.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.1.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.1.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.1.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.1.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.1.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.1.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.1.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.1.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.1.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.2.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.2.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.2.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.2.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.2.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.2.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.2.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.2.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.2.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.2.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.3.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.3.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.3.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.3.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.3.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.3.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.3.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.3.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.3.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.3.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.4.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.4.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.4.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.4.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.4.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.4.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.4.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.4.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.4.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.4.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.5.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.5.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.5.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.5.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.5.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.5.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.5.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.5.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.5.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.5.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.6.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.6.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.6.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.6.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.6.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.6.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.6.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.6.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.6.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.6.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.7.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.7.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.7.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.7.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.7.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.7.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.7.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.7.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.7.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.7.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.8.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.8.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.8.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.8.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.8.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.8.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.8.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.8.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.8.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.8.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.9.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.9.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.9.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.9.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.9.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.9.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.9.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.9.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.9.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.9.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.10.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.10.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.10.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.10.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.10.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.10.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.10.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.10.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.10.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.10.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.11.norm1.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.11.norm1.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.11.attn.qkv.weight: copying a param with shape torch.Size([1152, 384]) from checkpoint, the shape in current model is torch.Size([4608, 1536]).
size mismatch for blocks.11.attn.qkv.bias: copying a param with shape torch.Size([1152]) from checkpoint, the shape in current model is torch.Size([4608]).
size mismatch for blocks.11.attn.proj.weight: copying a param with shape torch.Size([384, 384]) from checkpoint, the shape in current model is torch.Size([1536, 1536]).
size mismatch for blocks.11.attn.proj.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.11.ls1.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.11.norm2.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.11.norm2.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for blocks.11.ls2.gamma: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for norm.weight: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).
size mismatch for norm.bias: copying a param with shape torch.Size([384]) from checkpoint, the shape in current model is torch.Size([1536]).


We were seeing weird ErrCodeProtocol stream errors, so we stopped using the bundled x/net/http2 and switched both to using x/net/http2 explicitly (with http2.ConfigureTransports and http2.ConfigureServer, so the bundled one isn't used).
Our x/net git version is https://github.com/golang/net/commit/aaa1db679c0d7765d2b1cb1f92cac8ebf4d94c53, which is today's current master.
After hacking it up locally to add some expvar counters on which paths in http2.Server were returning the protocol error, we found it was here:
https://github.com/golang/net/blob/aaa1db679c0d7765d2b1cb1f92cac8ebf4d94c53/http2/server.go#L1835
// http://tools.ietf.org/html/rfc7540#section-5.1.2
// [...] Endpoints MUST NOT exceed the limit set by their peer. An
// endpoint that receives a HEADERS frame that causes their
// advertised concurrent stream limit to be exceeded MUST treat
// this as a stream error (Section 5.4.2) of type PROTOCOL_ERROR
// or REFUSED_STREAM.
if sc.curClientStreams+1 > sc.advMaxStreams {
        if sc.unackedSettings == 0 {
                // They should know better.
                return streamError(id, ErrCodeProtocol)
        }

So, the Go http2 client (Transport) and/or server is getting its concurrent/max streams accounting wrong.
Perhaps interesting: the backend (the http2.Server that the ReverseProxy's Transport is hitting) has extremely long-running http.Handlers (like: days or weeks longs) alongside many short ones. That might explain why this bug hasn't been reported by more people.
I see no recent commits that suggest this is a regression. This server is new, so I also can't say whether it worked previously.
/cc @neild @bcmills @fraenkel @dmitshur @dsnet @josharian

possible? https://github.com/golang/go/issues/42777

CC @neild.


Can I have some help?

I'm getting this: Im with FreeTS.ovh and I'm unaware of what to do, I've put the IP in the config and set the ids of the groups: Im getting this in console:
03.11 12:47:04 [Server] INFO Enabling UltimateTs v2.1.4
03.11 12:47:04 [Server] INFO (TeamSpeak) Bot Online!
03.11 12:47:05 [Server] INFO [SEVERE] TS3 command error: {msg=invalid loginname or password, id=520}
03.11 12:47:06 [Server] INFO [SEVERE] TS3 command error: {msg=insufficient client permissions, id=2568, failed_permid=43}
03.11 12:47:07 [Server] INFO [SEVERE] TS3 command error: {msg=insufficient client permissions, id=2568, failed_permid=43}
03.11 12:47:07 [Server] INFO [SEVERE] TS3 command error: {msg=insufficient client permissions, id=2568, failed_permid=43}
03.11 12:47:07 [Server] INFO [SEVERE] TS3 command error: {msg=insufficient client permissions, id=2568, failed_permid=43}
03.11 12:47:08 [Server] INFO [SEVERE] TS3 command error: {msg=insufficient client permissions, id=2568, failed_permid=43}
03.11 12:47:08 [Server] INFO [SEVERE] TS3 command error: {msg=insufficient client permissions, id=2568, failed_permid=43}
03.11 12:47:08 [Server] INFO [] ------------------------------ []
03.11 12:47:08 [Server] INFO UltimateTs | v2.1.4 | Author: DiscowZombie.
03.11 12:47:08 [Server] INFO Using 1.8.8-R0.1-SNAPSHOT | git-Spigot-21fe707-e1ebe52 (MC: 1.8.8) | v1_8_R3.
03.11 12:47:08 [Server] INFO Your perms system is Vault.
03.11 12:47:08 [Server] INFO You can links ranks with Vault.
03.11 12:47:08 [Server] INFO Using FILE as storage type.
03.11 12:47:08 [Server] INFO [] ------------------------------ []

Hi,
You simply have entered a bad username or password.

How do I find this information out?

If you are on a dedicated hosting (or a VPS), all informations (username + password) has been given the first time that you start your TeamSpeak (with the main privilege key). If you aren't with a dedicated machine (or a VPS), ask your hosting provider to get informations that you need.


Tractor data: GPS positions do not match for NDVI and temperature

Description
There are some differences between the number of GPS points measured for thermal, sonar and NDVI data. Basically, on all sampling dates, the number GPS points for NDVI are fewer (140 - 180 samples) than for the other types of data.
Can any one comment on that.

@Mamatemenrs I've assigned this to @Andrade-Pedro. I believe @anfrench and @kthorp also run the tractor. For reference, here is a paper that describes the tractor
(Sanchez et al 2014)

@Mamatemenrs is there an open issue specifying tasks related to the tractor data?

@Mamatemenrs See also #150 because the workflows are similar for these platforms

Yes sir. There are less points for NDVI due to 'skips' in the serial output of the RT200 controller. The green seeker sensors are on a can bus network with the RT200 unit. The output message from the RT200 on the serial port was configured to output at 5Hz. Every once and awhile, there is a blank message (contains only the new line and carriage return characters). It appears to be random and no adjustments or a change in settings make a difference.


I'm curious about 2.png of assets.

Hello,
I would like to get some results such as 2.png of assets.
How can you get that graphs ?
Do you use your code of model.py ?

Well, these images are obtained by  tensorboard. And the codes to merge all the losses into the tf.summary are written in the original materport repository, you don't need to change too much. For more details of the charts, you can check out the tensorboard tutorial. :)


Remove team email address

it removes the team_email_address field from Group
all reported profiles e-mails are sent to the defined support e-mail address

Rebased, deconflicted, and merged.


Font Size possibly should be based on unitsPerEm

It is a bit unclear to me how font size works, but it seems like the way our path based text engine handles the font size isn't how the browsers or any other renderer really handles it. So far we defined it to be the distance from the ascender to the descender, but it seems like it may be the unitsPerEm value of the head table that we should be using instead. This needs to be investigated further. If this turns out to be true, we should switch to it and adjust the font size related constants accordingly.

This post seems to confirm it as well: https://tonsky.me/blog/font-size/

Long story short, this [em] square is what you actually control when setting font size.

The em square apparently is super arbitrary, and the blog post recommends cap height instead (which we almost definitely can't portably query), so I'd say the ascender descender distance is the next best thing. So this probably can already be closed again.

I'm closing this as what we are doing seems good enough.

I'm closing this as what we are doing seems good enough.


Build with docker python package make 3 images / containers

Building via docker python package make 3 images, we want make only one.
CC: @pacifikus

Docker SDK for Python has rm parameter in the build method to remove intermediate containers


cmd/go: go env incorrect quoting for values with double quotes

What version of Go are you using (go version)?

» go version
go version devel go1.21-b35ee3b0467 Wed Mar 1 14:25:13 2023 +0000 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
» go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/user/.cache/go-build"
GOENV="/home/user/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS="-trimpath "-ldflags=-s -w""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/user/.data/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/user/.data/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/user/sdk/gotip"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/user/sdk/gotip/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="devel go1.21-b35ee3b0467 Wed Mar 1 14:25:13 2023 +0000"
GCCGO="gccgo"
GOAMD64="v3"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="0"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build547532058=/tmp/go-build -gno-record-gcc-switches"

What did you do?
» go env -w GOFLAGS='-trimpath "-ldflags=-s -w"'

» go env | grep GOFLAGS
GOFLAGS="-trimpath "-ldflags=-s -w""

What did you expect to see?
GOFLAGS='-trimpath "-ldflags=-s -w"'

or
GOFLAGS="-trimpath \"-ldflags=-s -w\""

What did you see instead?
incorrect quoting of values with double quotes

cc @bcmills @matloob

Yep, that's wrong. 😩
The bug is here:
https://cs.opensource.google/go/go/+/master:src/cmd/go/internal/envcmd/env.go;l=418;drc=db259cdd80eff527e8f344d678031c516167d258
We have a quoted.Join function that is used elsewhere in envcmd/env.go. It should probably be used in PrintEnv as well.

If you don't mind, I'd like to fix this bug.

Fixed in CL 488375


ifm: add -fcommon workaround

Workaround build failure on -fno-common toolchains like upstream
gcc-10. Otherwise build fails as:
ld: libvars.a(vars-freeze-lex.o):src/libvars/vars-freeze-lex.l:23:
  multiple definition of `line_number'; ifm-main.o:src/ifm-main.c:46: first defined here

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

/cc @orivej


Build the Debian Desktop AMI on a Graviton (AMD64) instance

🗣 Description
This pull request modifies the Packer code to build the Debian Desktop AMI on a Graviton (AMD64) instance.
💭 Motivation and context
Running the AMI on Graviton should be cheaper and better for the environment.
🧪 Testing
All automated tests pass.  I also built a staging AMI with these changes and verified that it functions as expected.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
[x] All new and existing tests pass.
[x] Build and test a staging AMI with these changes.

✅ Pre-merge checklist

[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

Hi Team @all , In the README.md file the link in this sentence returns a 404 error: "If you have appropriate permissions for the repository you can view existing secrets on the 'appropriate page' in the repository's settings. The link is pointing to the following "github.com/cisagov/debian-packer/settings/secrets/actions

Hi Team @ALL , In the README.md file the link in this sentence returns a 404 error: "If you have appropriate permissions for the repository you can view existing secrets on the 'appropriate page' in the repository's settings. The link is pointing to the following "github.com/cisagov/debian-packer/settings/secrets/actions

@dv4harr10 - I think you get a 404 just because you lack the permission to view those settings.  The link you listed works fine on my end.

I just wanted to voice some hesitancy on wholesale switching to ARM on this image as opposed to building an AMI for both (AMD64 and ARM64) architectures.

This AMI is not very used much at all.  The only environments where I see it being used are our sandbox for testing user access and a WAS/ZAP testing environment.  I think the risk of migrating wholesale to ARM is minimal here, but we can reach out to those WAS/ZAP users and find out if this will affect their work.

I think the risk of migrating wholesale to ARM is minimal here, but we can reach out to those WAS/ZAP users and find out if this will affect their work.

I emailed that team and will post an update here when we get more info.

I think the risk of migrating wholesale to ARM is minimal here, but we can reach out to those WAS/ZAP users and find out if this will affect their work.

I emailed that team and will post an update here when we get more info.

The WAS team is no longer using that environment.  I'm not aware of anyone actively using this AMI at the moment, so the risk of moving it to ARM is very low.

I just wanted to voice some hesitancy on wholesale switching to ARM on this image as opposed to building an AMI for both (AMD64 and ARM64) architectures.

Please see cisagov/skeleton-packer#355.  If that PR is preferred then I will close this one (as well as cisagov/samba-packer#48 and cisagov/terraformer-packer#54) and launch a cisagov/skeleton-packer mini-Kraken.

Closed in favor of #64.


Add support for overriding animation style

Is your feature request related to a problem? Please describe.
The default spring animation looks good in certain situations, but not when margins are small between the edge of the control area and the active control, as the active control indicator "overflows" the control area during the spring animation
Describe the solution you'd like
The ability to customize easing method of the animation

Thanks for pointing it out @kristfal. Will work on the same and fix it.


Mobile > Home > .search-suggestions: bullets are visible, and some text is cut off

List items on the .search-suggestions section have styling issues:

bullets are visible on each row
longer strings are cut off

iPhone 5

iPhone 6

Expected Results:

The bullets should not be visible
The list items should not be cut off on mobile devices

Tested on:

iPhone 6, iOS 8.1
iPhone 6 Plus, iOS 8 (via BrowserStack)
iPhone 5S, iOS 7  (via BrowserStack)
Samsung Galaxy S5 (via BrowserStack)

Improved the formatting of this list on mobile/tablet, @irfanpirbhai can you please re-test this?

Awaiting a push to production before I can test.


Should route definitions be colocated with their containers?

In creating a moderate size app using react-boilerplate, one will soon find their routes.js file becoming somewhat monolithic and hard to work with.  In my current codebase I have refactored app/routes.js to enable importing separate route definitions, which are located in a route.js file within the container's folder.
This works well for me, as the route definitions are now located alongside the container, reducers and sagas they use, so are easy to find, and easier to work with.  Code below shows my current implementation of this, is there any appetite for a PR to this end?
app/routes.js
import homeRoute from './containers/HomePage/route';
import featureRoute from './containers/FeaturePage/route';

import { getAsyncInjectors } from '../utils/asyncInjectors';

const errorLoading = (err) => {
  console.error('Dynamic page loading failed', err); // eslint-disable-line no-console
};

const loadModule = (cb) => (componentModule) => {
  cb(null, componentModule.default);
};

const createRoutes = (routeCreators) => (store) => {
    return routeCreators.map(routeCreator =>
        routeCreator(
            createRenderer,
            errorLoading,
            getAsyncInjectors(store)
        )
    );
}

export default createRoutes([
    homeRoute,
    featureRoute
]);

app/containers/HomePage/route.js
export default (createRenderer, errorLoading, { injectReducer, injectSagas }) => ({
      path: '/',
      name: 'home',
      getComponent(nextState, cb) {
          const importModules = Promise.all([
              import('containers/HomePage/reducer'),
              import('containers/HomePage/sagas'),
              import('containers/HomePage'),
          ]);

          const renderRoute = loadModule(cb);

          importModules.then(([reducer, sagas, component]) => {
              injectReducer('home', reducer.default);
              injectSagas(sagas.default);

              renderRoute(component);
        });

            importModules.catch(errorLoading);
      },
});

Thanks for posting ✨ There is a very similar discussion going on in #1550, did you want to move this into there?

@alsiola Your thoughts and experience are appreciated! Please join in #1550.
Closing to keep things cleaned up.


MSSQLSink LogEvent column to be varbinary(max)

It is nice if MSSQLSink can support compressed LogEvent column. Their could be a configuration to turn the compression on and off.
MSSqlServer supports Compress function to GZip data in SQL level. https://learn.microsoft.com/en-us/sql/t-sql/functions/compress-transact-sql?view=sql-server-ver16.
Currently Binary columns a re not supported as a data type.

Hi @asiridissa!
Thanks for getting in touch. We currently have no resources to implement this but we are always open for useful contributions.
Generally new features can be discussed in the discussions section. But i'll leave this issue open with type enhancement.
Best regards,
Christian


Question about evaluation

I wonder how to evaluate a pretrained model in various datasets? I see an eval script is available, but when I run it using this
poetry run ocl_eval +evaluation=projects/bridging/outputs_movi +train_config_path=<config_path> +checkpoint_path=<checkpoint_path> +output_dir=<output_dir>

I am getting an error that it cannot locate certain configs.

Same problem for me, any updates?


Clmm and Amm IDL mismatch.

I built the "clmm" contract with "anchor build" after adding the appropriate "idl-build" features as instructed by the errors.
The resulting IDL a
ppears to be for the "Amm" contract, instead for the "Clmm" one.
Here is the resulting IDL
amm_v3.json
Is that an expected behaviour or have I made a mistake when building?

That is correct, there is no problem, usually you only need to execute the anchor build command in the project directory.


chore(ci): Further improvements GH actions II

Ok, now we are talking!

@all-contributors please add @josepot for infra


Linux and SwiftPM Support

This should be successor of #229, a final version of support for Linux and SwiftPM(on Linux).
It builds and passes all tests on my Ubuntu 16.10 with these versions of Swift:
3.0.1
3.0.2
DEVELOPMENT SNAPSHOT 2016-12-14

Woof.

@hkellaway I have absolutely no idea why that build on Travis CI failed. Could you please take a look and let me know? Thank you.
BTW Could we please get Travis CI to try build Gloss on Linux as well? Thanks.

@rbukovansky im not familiar with Linux in the least; not sure how to get Travis CI to build Gloss on Linux as well

@rbukovansky this PR seems to include changes already in develop not made by you (e.g. update to the CHANGELOG and podspec) - i'm having trouble telling what changes are specific to you. is there a way to remove any changes that weren't made by you?

Failing tests:
	-[DecoderTests testDecodeUInt64()]
	-[DecoderTests testDecodeUInt64Array()]
	-[FlowObjectCreationTests testObjectDecodedFromJSONHasCorrectProperties()]
	-[FlowObjectCreationTests testObjectDecodedFromJSONHasCorrectProperties()]
	-[OperatorTests testDecodeOperatorUInt64ArrayReturnsDecoderUInt64Array()]```

Yeah, I will rework this... 🙄 Sorry!
And will take a look on that Travis guy as well... Thanks.

no problem! i appreciate the effort


Cache the redis connection at the celery app level.

This allows to reuse the connection pool, instead of reinstantiating one
at each task execution.

Nice, I guess the new connection is responsible for the slowness I am seeing with a lot of tasks!
See https://github.com/tripadvisor/celery-once/commit/83a59677ea7956201238031978f35793d13256b7 for another attempt in TripAdvisor's fork.

Hi @brouberol, first off apologies for the insane delay in getting to this PR, I'm trying to give this project some much needed love and think this is a great addition. I've ported it to #47 to work with the new custom backend approach in 1.0. I am aiming to get a release out later today. Thanks for the PR.

Released in 1.2.0.


Unable to select video which is on iCloud

I have some videos on icloud because of iPhone Storage. I won't be able to select those videos and images. Please help.!
Thanks

You might have to change some settings on your PHImageManager. Check the documentation.


README.md under /modules/cli should probably be copied at top level

https://github.com/astriaorg/astria-cli-go/issues/124


Assistant demo method commented out, but works fine

The demo::demoRunThreadAndWaitUntilComplete call is commented out.
I uncommented it locally and it succeeds.
It was commented out here: https://github.com/sashirestela/simple-openai/pull/71
It can be uncommented now.

Take a look at this comment:
https://github.com/sashirestela/simple-openai/issues/97#issuecomment-2091379198

Since assistants V1 will be removed in 3.0.0. This issue is irrelevant.


[ENH] improved conditional testing

This PR brings the conditional testing framework in a line with sktime logic:

only those objects are tested whose modules or base class modules have changed
estimators whose dependencies are not present are not tested
adds mirror of fix https://github.com/sktime/sktime/pull/5473

We're currently processing your upload.  This comment will be updated when the results are available.


Integration Test - Release - 2019/02/26 02:01:43

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest2 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.

@PRMergerTest2 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.


Group items in Examples

Currently, the "Examples" list is quite long. If some additional examples are added, it may not be visible on small screens.
I suggest using nested lists within the example dropdown. The current examples can be organized as follows:
Reflection of light

images-formed-by-two-mirrors.json
parabolic-mirror.json

Refraction of light

reflect.json (despite the name, it is more related to refraction)
internal-reflection.json
prisms.json
apparent-depth-of-an-object-under-water.json
chromatic-dispersion.json
bended-pencil.json
broken-pencil.json

Lens

concave-lens.json
convex-lens.json
lens-images.json
zoom-lens.json
spherical-aberration.json
compound-microscope.json
NL-simulation.json

Miscellaneous

reflection-and-refraction-of-a-single-ray.json
spherical-lens-and-mirror.json

And I think there may be a way to make the addition of new examples to the lists easy.

+1
Le jeu. 22 sept. 2022 à 02:35, Yi-Ting Tu @.***> a
écrit :

Currently, the "Examples" list is quite long. If some additional examples
are added, it may not be visible on small screens.
I suggest using nested lists within the example dropdown. The current
examples can be organized as follows:
Reflection of light

images-formed-by-two-mirrors.json
parabolic-mirror.json

Refraction of light

reflect.json (despite the name, it is more related to refraction)
internal-reflection.json
prisms.json
apparent-depth-of-an-object-under-water.json
chromatic-dispersion.json

Lens

concave-lens.json
convex-lens.json
lens-images.json
zoom-lens.json
spherical-aberration.json
compound-microscope.json

Miscellaneous

reflection-and-refraction-of-a-single-ray.json
spherical-lens-and-mirror.json

And I think there may be a way to make the addition of new examples to the
lists easy.
—
Reply to this email directly, view it on GitHub
https://github.com/ricktu288/ray-optics/issues/54, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHRGDW6GRAWOQGNSKLHLDSLV7PAWVANCNFSM6AAAAAAQSTWTYY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Other possible designs:

Use a sidebar, instead of the dropdown, to show a nested list of the examples
Let the dropdown scrollable, and sort the items according to the groups, with a label added before each group.
make the dropdown multi-column, where each column represent one group.

I am planning to replace the Examples menu by a gallery webpage, so this is no longer necessary.


Add suppress-warnings to shared_conf.py

This suppresses the following warnings (which pollute the log).
(WARNING/2) Document headings start at H2, not H1 [myst.header]

WARNING: skipping unknown output mime type: application/vnd.holoviews_exec.v0+json [mystnb.unknown_mime_type]

WARNING: 'myst' reference target not found: ../../user_guide/Widgets.ipynb

WARNING: 'myst' reference target not found: ../../user_guide/Widgets.ipynb

Isn't this one an actual error?
Other than that, it'd be great if you could add comments in nbsite/shared_conf.py about suppress_warnings to indicate why these warnings are suppressed (basically copying your original post). Noticed this kind of stuff tends to stick forever otherwise.

TBH, I just added it because I saw the warning a lot. I should have thought about it a bit more :upside_down_face:
I have downloaded the build docs step from this run (13_build docs.txt) and can see this warning is raised 147 times.
An example of a warning is
2023-04-09T15:47:29.8157231Z /home/runner/work/holoviews/holoviews/doc/gallery/demos/bokeh/dragon_curve.ipynb:10002: WARNING: 'myst' reference target not found: ../../topics/geometry/lsystems.ipynb and when looking in the notebook I can see the link here in the first cell:
Dragon curve example from the [L-systems](../../topics/geometry/lsystems.ipynb) topic notebook in ``examples/topics/geometry``.

So yes it seems to be a valid warning. I will remove it and add comments to the other two.


Ritai#4

We've got some content!
My thoughts: I like the carousel, the paragraph need some work (and images to go along with them). The background color is somewhat gaudy - let's work on that. I want to get another paragraph with out github logo and slack channel like so:

We also need to fix the issue I'm having with the navbar where there is a little gap. I'm not sure how to fix it but the issue goes away when we remover the navbar in it's entirety. It's hideous, see below:

Looks good!


Correction for raw affiliation Ryerson University, USA#TAB#

Correction needed for raw affiliation Ryerson University, USA#TAB#
raw_affiliation_name: Ryerson University, USA#TAB#
new_rors: 05g13zd79
previous_rors:
works_examples: W1526731712;W2806363353;W2806829681;W2806851634
contact: 7a60804f227b4964b64d12455722123b:43f73835 @ ourresearch.org

This issue was accepted and ingested by the OpenAlex team on 2024-12-21. The new affiliations should be visible within the next 7 days.


Added "Publish with Ghost" badge

added "Publish with Ghost" badge to the bottom left corner of the screen when the portal popup is open

How does one remove this badge? Or how can we edit it, maybe just "Ghost" or something?
I could not find the portal files anywhere.


District wise daily cases and testing count Python scripts  and corresponding json files

Python scripts for daily district wise number of cases and testing count and the corresponding json files

We're planning to add num_cases to v1 and v2 of raw_data as well. Will review this PR once again after the format changes.

This has already been implemented and the data is available in v3 and v4. If there are more requirements kindly raise an issue and let's discuss first.
Closing this.


upgrade doobie to 1.0.0-RC4

I attempted to PR this but had some issues (type inference on getTypeMap which is strange, something about Class[_] vs Class[_ <: Object]) which I don't feel comfortable in submitting the PR.
Could this be project be upgraded to RC4?
The Transactor now needs a LoggingHandler which is effectful.
Here's the code I came up with:
package com.ovoenergy.natchez.extras.doobie

import cats.data.Kleisli
import cats.effect.Async
import cats.implicits._
import com.ovoenergy.natchez.extras.core.Config
import com.ovoenergy.natchez.extras.core.Config.ServiceAndResource
import doobie.WeakAsync
import doobie.free.KleisliInterpreter
import doobie.util.log
import doobie.util.log.LogHandler
import doobie.util.transactor.Transactor
import natchez.{Span, Trace}

import java.sql.{Connection, PreparedStatement, ResultSet}

object TracedTransactor {
  private val DefaultResourceName = "db.execute"

  type Traced[F[_], A] = Kleisli[F, Span[F], A]
  def apply[F[_]: Async: LogHandler](
    service: String,
    transactor: Transactor[F]
  ): Transactor[Traced[F, *]] = {
    val kleisliTransactor = transactor
      .mapK(Kleisli.liftK[F, Span[F]])(implicitly, Async.asyncForKleisli(implicitly))

    implicit val lh: LogHandler[Traced[F, *]] = new LogHandler[Traced[F, *]] {
      override def run(
        logEvent: log.LogEvent
      ): Traced[F, Unit] = Kleisli.liftF(implicitly[LogHandler[F]].run(logEvent))
    }

    trace(ServiceAndResource(s"$service-db", DefaultResourceName), kleisliTransactor)
  }

  private def formatQuery(q: String): String =
    q.replace("\n", " ").replaceAll("\\s+", " ").trim()

  def trace[F[_]: Trace: Async: LogHandler](
    config: Config,
    transactor: Transactor[F]
  ): Transactor[F] =
    transactor
      .copy(
        interpret0 = createInterpreter(config)(WeakAsync.doobieWeakAsyncForAsync[F]).ConnectionInterpreter
      )

  private def createInterpreter[F[_]: Trace: LogHandler](
    config: Config
  )(W: WeakAsync[F]): KleisliInterpreter[F] = {
    new KleisliInterpreter[F](implicitly[LogHandler[F]])(W) {
      override lazy val PreparedStatementInterpreter: PreparedStatementInterpreter =
        new PreparedStatementInterpreter {

          type TracedOp[A] = Kleisli[F, PreparedStatement, A] //PreparedStatement => F[A]

          def runTraced[A](f: TracedOp[A]): TracedOp[A] =
            Kleisli {
              case TracedStatement(p, sql) =>
                Trace[F].span(config.fullyQualifiedSpanName(formatQuery(sql)))(
                  Trace[F].put("span.type" -> "db") >> f(p)
                )
              case a =>
                f(a)
            }

          override val executeBatch: TracedOp[Array[Int]] =
            runTraced(super.executeBatch)

          override val executeLargeBatch: TracedOp[Array[Long]] =
            runTraced(super.executeLargeBatch)

          override val execute: TracedOp[Boolean] =
            runTraced(super.execute)

          override val executeUpdate: TracedOp[Int] =
            runTraced(super.executeUpdate)

          override val executeQuery: TracedOp[ResultSet] =
            runTraced(super.executeQuery)
        }

      override lazy val ConnectionInterpreter: ConnectionInterpreter =
        new ConnectionInterpreter {
          override def prepareStatement(a: String): Kleisli[F, Connection, PreparedStatement] =
            super.prepareStatement(a).map(TracedStatement(_, a): PreparedStatement)
          override def getTypeMap = primitive(_.getTypeMap)
        }
    }
  }
}

Found this https://github.com/tpolecat/doobie/blob/main/modules/core/src/test/scala/doobie/util/StrategySuite.scala#L47
Which also fixes the compile issue, and at least you have the comfort that you're not the only person without knowledge of what it means

Related to https://github.com/ovotech/natchez-extras/pull/108

@massimosiani kindly picked this up and updated the original proposal, that PR has now been merged and is available for testing in the latest milestone release: https://github.com/ovotech/natchez-extras/releases/tag/8.0.0-M4


GFG-10858

What

Remove numeric validation because its not a real rule on Datajet

Non sense branch name


Fix deprecation replacement for Project.buildDir

Minor edit, I believe Project.buildDir was a File so this keeps the type untouched. Not the end of the world but this way the replacement is straightforward

Hi Martin 👋
Good catch!
Looks like the DCO check is failing, could you please fix this?
https://github.com/gradle/gradle/pull/26013/checks?check_run_id=15585196419

Sorry about that, I made the edit from the GitHub UI, didn't realise it wasn't signing off commits. It should be all good now!

Thanks Martin, DCO is good.
I just realized this is a "documentation" change only and the deprecation of Project.buildDir happened in 8.3-rc-1. Could you please change your PR to target our release branch? That way your fix would be in 8.3 alongside the actual deprecation.

Could you please rebase your changes on top of the release branch and edit your PR to target the release branch?

Should be all good!
I also took this opportunity to move the asFile at the end of the expression because @Vampire finds it reads better and I somewhat agree.
layout.buildDirectory.get().asFile
// vs previously
layout.buildDirectory.asFile.get()

But no strong opinion there, feel free to move it back to its original place!

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.

Sure thing! For complete information, there's a bug in KTIJ that prevents the replacement to work in most of the cases at the moment. But at least you can navigate to the source at copy/paste from there.


Add official Python 3.11 support

Adds Python 3.11 to the CI
Adds Py3.11 support in the classifiers

Signed-off-by: Eric Brown<EMAIL_ADDRESS>

I feel stupid asking this, but why does this PR change these two lines?
https://github.com/PyCQA/bandit/pull/964/files#diff-fa602a8a75dc9dcc92261bac5f533c2a85e34fcceaff63b3a3a81d9acde2fc52R35
https://github.com/PyCQA/bandit/pull/964/files#diff-fac4c6890301d4de5c3f4266837803d5240c84a3d8b6c735bbc6a64c39d2f94eR10
tomli should not be required in Python 3.11, see #829.

@mportesdev @bersbersbers good catch, you are correct. Will remove.


funopen() unavailable in gcc-mingw-w64-x86-64

In upgrading to libconfuse 3.1, I am now receiving the following error on mingw builds for Windows:
libconfuse.a(libconfuse_la-fmemopen.o): In function `fmemopen':
fmemopen.c:110: undefined reference to `funopen'

This can be reproduced on Debian/Ubuntu by installing the mingw crosscompiler:
sudo apt install gcc-mingw-w64-x86-64
cd confuse
CC=x86_64-w64-mingw32-gcc ./configure --enable-shared=no --disable-examples
make

Then try linking libconfuse.a to a trivial app. Since I never build the libconfuse examples in my Windows builds, I hadn't realized that they didn't compile with mingw, but in theory, they could show the issue too. If nothing else, you can see the warning the funopen isn't defined when compiling fmemopen.c.
I'm not completely sure how best to work around this issue. In the past when I've run into uses of fmemopen, it has been pretty easy to remove them, but I don't think that's the case here. However, I also don't know how one would implement fmemopen without funopen. Hence I'm posting here to see if there are any other ideas.

P.S. Sorry to not have caught this before the 3.1 release. I wasn't paying attention until after I received the 3.1 release email. :(

That's unfortunate, fmemopen() is POSIX.1-2008 and usually systems that don't have it at least have funopen().  Windows is not a primary target for the project, so I never tested there.
I added fmemopen() to libConfuse to make the code paths for parsing a file and parsing a buffer equal.  The reason was the massive amounts of memory leaks and code complexity in both the parser engine and the lexer.
Not really sure how to approach this, if there is anything in mingw that can emulate reading from a FILE like fmemopen() it should be straight forward.

@fhunleth What do you think, should I pull the release ZIP (Windows) for v3.1, or just update the release notes with this limitation?

I'll have to dig a little deeper. I don't normally use Windows either, but I have a bunch of users of one of my projects on Windows.
As for pulling the Windows release, I'm not sure that's necessary. I'm pretty sure that cygwin and Windows Bash mode users will be fine with v3.1. I don't know about Visual Studio users. Also, there's an off chance that the error is related to Ubuntu and Debian packaging old versions of mingw, since I've run into that before. Let me investigate when I get a break from some other work...

There is no equivalent in MS libc. You'd have to redefine FILE, emulate fmemopen to generate a special FILE *, wrap all functions taking a FILE * and call out to helpers if the special memory backed FILE * show up. So, it can be done, but it's going to be ugly as hell and break whenever someone decides to use some new api (or some new aspect of a previously used api) taking a FILE *.
libconfuse is unusable to me if windows support is blown away like this. Please fix whatever problem was fixed with fmemopen in some other way. I have zero time to work on this right now.

But of course, that above assumes that the redefined FILE doesn't need to be leaked out in the libconfuse API. Haven't checked that...

@fhunleth OK, sounds reasonable, I'll keep the zip then.

Guys, I'm sorry I've broken¹ your use-case.  Unfortunately I'm the only active maintainer atm and my time is very limited. Reverting to the situation before fmemopen() is not an alternative (massive memory leaks).
Maybe on Windows fmemopen() could be implemented as a tmpfile()?

¹ https://xkcd.com/1172/

@troglobit Thanks for maintaining libconfuse. It has saved me quite a bit of time, and it's reassuring to know that someone responds to bug reports (pretty quickly I might add).
I tried out a few things this morning:

tmpfile() returns NULL on mingw-w64 4.0.4. It's deprecated in mingw-w64 5.0, so this doesn't look like a good option.
I tried mkstemp(), but it's segfaulting for me on mingw-w64 4.0.4.

I'll take another pass tomorrow.

@fhunleth No problem, and thank you for the kind words.
Interesting to know of the deprecation of tmpfile().  Windows has some issues with this, seems it requires admin rights to create a tempfile?
I'll see if I can set up a small mingw-w64 enviroment to test some ideas myself.

Regarding the xkcd link: Kill Windows support, and then ridicule any complainers, is that it?

@peda-r That was really not my intention, I was simply trying to convey the humor of it all.

On a more constructive note. Maybe this could help us?
https://sourceforge.net/p/mingw/msys2-runtime/ci/f21dc72d306bd98e55a08461a9530c4b0ce1dffe/tree/newlib/libc/stdio/fmemopen.c

Nope, msys2 is a fork of Cygwin. I.e. a completely different libc.

@peda-r Was thinking we could take that stand-alone implementation to replace our current src/fmemopen.c, at least on Windows. All it seemed to require from the OS was sbrk()?

Hopefully, with PR #97 we can put this issue to rest.  I've done my best to test it with mingw and Wine on Linux, but I don't know if it works on Windows.
Also, I feel really bad about the whole direction this thread took. It was of course never my intention to break Windows with the work I did to fix the memory leaks in #75, or for that matter to inadvertently offend any of the users of libConfuse. I don't like that feeling this has left me with ...
So, if the fixes in #97 are to your satisfactory I'll merge them and release v3.2, which would likely be the last release I do.

I'll try this out tonight. From a brief skim, I expect it to fix the issue for me. Thank you so much for looking into this.

@troglobit, you can't seriously consider stepping down over my heated remarks? I was just frustrated with the apparent disregard for Windows (which is all to common in various OSS projects, it gets very old). I'm truly sorry to have offended you, and I sincerely hope you reconsider!

@peda-r Yes, yes I did actually. It is an uphill climb as it is, so that was just uncalled for. The simple reason for Windows not being a primary target is that I haven't used it in 20+ years.
Now, let's move on and do some coding! :smiley:

@troglobit All of my project's regression tests pass on the Windows build, so I'm good with your PR!

@fhunleth Awesome, thank you for testing it! I'll probably merge it first thing tomorrow morning (CET :)

Fix(es) merged.

Thank you for this work, 6 years later. Simply thank you.


[Question] Use alpine postgres image

The sample docker-compose uses postgres.
Is it safe to use the alpine postgres image instead?

Hi. To my knowledge, the Alpine variant doesn't differ from the Debian variant in any way that's meaningful to the application, so I believe it's safe. I ran Debian variants in production, that's why the samples use them.

Thanks for confirming.


API Notice doc update

Summary
Adds a notice to the readme and Overview Docs page to let users know the upcoming changes to the API.
#866

This is the best! Thanks!


0.3.0: mutable struct KronigPennyModel changed to struct Model{KrongPennyPotential}

@JuliaRegistrator register()

Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue.


RE Ruby 2/Rails 4 upgrade yesterday

Hey Folks,
Ed Burke emailed me today suggesting we leave a branch in this repo for rails 3 and ruby 1.9.3 (ie what it was before I upgraded everything yesterday to rails 4/Ruby 2). I'd agree with that. Anyone who has access, could you create a branch called
rails3ruby1.93
and another branch
rails4ruby2?
I've got pull requests ready to go on them here:
https://github.com/paterson/selfstarter/tree/rails3ruby1.93
https://github.com/paterson/selfstarter/tree/rails4ruby2
I then suggest we have a quick chat below about which one we want as master. They both work fine, but might be worth it anyway.
Thoughts?

fixed on #114


Remove topology configmap on kuadrant operator uninstall

Link the lifecycle of the kuadrant operator with the topology configmap. Currently, when the operator starts, it will create and maintain the topology configmap in the namespace where the operator is deployed. It is missing the implementation of the removal of the topology configmap when the operator is deleted.

Note: The ConsolePlugin resource, together with the associated deployment and service, follows the life events of the topology configmap. When the topology is created, so it is the ConsolePlugin (on openshift). Whereas when the topology is deleted, so it is the ConsolePlugin and associated resources.  The ConsolePlugin was introduced in https://github.com/Kuadrant/kuadrant-operator/pull/884

Is this essential for v1?

I would say it is not.

Release attribute now is unset


oauth2: remove email claim check

The email claim is not necessary for OIDC.
If only openid scope is used (without email, profile, etc.) the email claim will not be available.
Instead, it would make more sense to check for "sub" but this will work without that check for now.
The email claim could later be added by using a transform directive (action add email<EMAIL_ADDRESS>I've tested this manually and it works for our use case, allowing us to resolve the final issue with this plugin.
This won't break existing configuration as this is only a validation step.

Any chance this could be merged and integrated into caddy-security soon? We'd like to use the caddy-security plugin from official sources but this is holding us back.

@simaotwx , I will take a look at it over the weekend. Did you have a chance to read CONTRiBUTING.md and follow it? Generally, with changes like this one, you need introduce the option to disable email check, because you are changing the default behavior. Here, default behavior of checking email should stay.

@greenpau

Did you have a chance to read CONTRiBUTING.md and follow it?

Thanks for pointing me towards the CONTRIBUTING.md file. I've read it and realized I haven't opened an issue prior to creating the PR. I submitted the CLA consent PR's.

Generally, with changes like this one, you need introduce the option to disable email check, because you are changing the default behavior. Here, default behavior of checking email should stay.

I'm not sure if this default behavior is desired. AFAIK the email claim is not required by standard and thus erroring when checking it causes problems with OIDC providers that only have the openid claim (which does not include email). I can add the option to disable this via an option, though.

This is done via disable email claim check directive.


Deploy doesn't seem to deploy completely

For example, #185, the console output for the automated deploy suggests that the repository was installed correctly, however /cvmfs/main.galaxyproject.org/config/shed_tool_conf.xml does not contain an entry for kc_align version 0.1.7, and /cvmfs/main.galaxyproject.org/shed_tools/toolshed.g2.bx.psu.edu/repos/iuc/kc_align/13a99f96d6cc was not created.
The install database, however, did get updated.

I don't see any changes to shed_tool_conf.xml in the deploy output of that PR.

Fixed by @mvdbeek in #189


PromQL builder open sourced from grafana?

Hi!
One of the things that is essential when using the sdk is to build queries and expressions(the expr field of DataqueryBuilder) for prometheus metrics backed panels and alerts, and I struggled to find a good promQL builder in Typescript that are open sourced. Since Grafana UI has a good builder tool, I wanted to ask if there's anything open sourced from Grafana?
Thanks!

Hi!
I am not aware of any Typescript library to build Prometheus queries. I'll ask around internally :)

Hey, I've built a PromQL query builder https://www.npmjs.com/package/promql-query-builder.

Closing this issue, since it's out of the scope of the Foundation SDK :)