measure_string: factor in underline

I think text measurement should include decoration as well.
Also, embedded-text's automatic fit-to-text function would cut off the underline without this.
Should line_height() also depend on the decoration?

cc @rfuest

cc @rfuest

The decorations should be included in the measurement and this was on my TODO list. Thanks for implementing this and adding the tests I was too lazy to add in the previous PR ;).

Should line_height() also depend on the decoration?

I'm undecided about this one, but lines shouldn't overlap if underlining is enabled. There are at least two ways to implement this: One would be return a fixed line height that is large enough for text with or without underlining. And the other one is to only increase the line height if underlining is enabled.

The decorations should be included in the measurement and this was on my TODO list. Thanks for implementing this and adding the tests I was too lazy to add in the previous PR ;).

Should line_height() also depend on the decoration?

I'm undecided about this one, but lines shouldn't overlap if underlining is enabled. There are at least two ways to implement this: One would be return a fixed line height that is large enough for text with or without underlining. And the other one is to only increase the line height if underlining is enabled.

lines shouldn't overlap if underlining is enabled
And the other one is to only increase the line height if underlining is enabled.

Consider the case where underline is enabled for a single word in a single line. If that single line would be 2px taller, I think I'd get a bunch of issues about it :) On the other hand, detecting a dynamically set underline before measurement requires a second parse of the text, which I'd definitely want to avoid.
Previously, e-t used a line_height same as today, and a line_spacing of 0 by default. This resulted in overdraw, but I think the 6x8 font looked the best this way.
line_height is (I think) the only value e-t can use to step in the y direction. I'd probably leave the default line spacing as 0, so I think I'll (with your approval) go for increasing what's returned by line_height.

lines shouldn't overlap if underlining is enabled
And the other one is to only increase the line height if underlining is enabled.

Consider the case where underline is enabled for a single word in a single line. If that single line would be 2px taller, I think I'd get a bunch of issues about it :) On the other hand, detecting a dynamically set underline before measurement requires a second parse of the text, which I'd definitely want to avoid.
Previously, e-t used a line_height same as today, and a line_spacing of 0 by default. This resulted in overdraw, but I think the 6x8 font looked the best this way.
line_height is (I think) the only value e-t can use to step in the y direction. I'd probably leave the default line spacing as 0, so I think I'll (with your approval) go for increasing what's returned by line_height.

OK, that makes sense, let's increase the line height to take the decorations into account. We might want to add a LINE_HEIGHT constant to the MonoFont trait and return that value in line_height, because the line height should be larger than F::UNDERLINE_HEIGHT + F::UNDERLINE_OFFSET as u32 to make sure the underlining doesn't touch the characters on the next line.

line_height is (I think) the only value e-t can use to step in the y direction. I'd probably leave the default line spacing as 0, so I think I'll (with your approval) go for increasing what's returned by line_height.

Why does e-t use line spacing instead of line height? I might want to add a line_height setting to TextStyle and it would be good if the settings were similar between e-t and Text. I prefer a line height over a line spacing setting because it's independent of the font and IMO more common.

OK, that makes sense, let's increase the line height to take the decorations into account. We might want to add a LINE_HEIGHT constant to the MonoFont trait and return that value in line_height, because the line height should be larger than F::UNDERLINE_HEIGHT + F::UNDERLINE_OFFSET as u32 to make sure the underlining doesn't touch the characters on the next line.

line_height is (I think) the only value e-t can use to step in the y direction. I'd probably leave the default line spacing as 0, so I think I'll (with your approval) go for increasing what's returned by line_height.

Why does e-t use line spacing instead of line height? I might want to add a line_height setting to TextStyle and it would be good if the settings were similar between e-t and Text. I prefer a line height over a line spacing setting because it's independent of the font and IMO more common.

Um, no reason at all. I can be persuaded to change that. But we are working with pixels and for each font the default line height is rather "random".

Um, no reason at all. I can be persuaded to change that. But we are working with pixels and for each font the default line height is rather "random".

We could also add a new enum for the line height setting:
enum LineHeight {
    Default,
    Relative(i32),
    Absolute(u32),
}

We could also add a new enum for the line height setting:
enum LineHeight {
    Default,
    Relative(i32),
    Absolute(u32),
}

Huh I wouldn't want to complicate this.

Huh I wouldn't want to complicate this.

Can you update the branch so that we can merge this? We can implement the line_height changes in a later PR.

Can you update the branch so that we can merge this? We can implement the line_height changes in a later PR.

Github really should know if the branch is conflict-free.

Github really should know if the branch is conflict-free.


添加了部分package-info的javadoc注释

添加了部分package-info的javadoc注释

Dear @Roozenlz
Thank you for your effort in documenting the adf-core-java.
However, we cannot accept your pull request as it is because:

we are an international community, so the content in this repository must be in English
the HTML code you inserted is broken, e.g., you do not include the end tags </li> or </p>
Roozen is not an Author of this classes
https://roozen.top is not an appropriate website to refer to

If you really wants to contribute to our community, please contact one of the Executive or Technical Committee members listed in the RescuSim website.
Kind Regards,


readme is incorrect; this role no longer supports hostvars...

sometimes ansible hostvars collide with other variable namespaces... and this causes problems so let's just not use hostvars... ok? now that we've removed that feature the README needs to be updated.

modify usage examples involving hostvars

No, hostvars are great …


Don't pass in version when updating cluster.

Our upsert would pass in ES version on update which invalid according to
AWS spec .. as a result it would fail. Now we only pass in version on
create but not on update.

👍


Is Semantic UI still under active development?

I'm looking for a css framework to use with vue. I really like the way semantic ui looks, but it seems like it is no longer under active development.

What is the current situation with Semantic UI?

And how will that affect this Vue js adaptation of it?

Semantic-Org/Semantic-UI#6109
Good question! (Disclaimer: I'm not a maintainer.)

This repo is a component library based on Semantic UI. I do not contribute to Semantic UI, so I cannot answer your first answer, but the links that @edjroot posted should explanatory.

And how will that affect this Vue js adaptation of it?

This integration has the goal of implementing the js part of the latest Semantic UI version. If they keep working on it, we'll follow their changes, otherwise, it'll stay like it is now.
If you like how Semantic UI looks now, I don't see how the fact that the development on their side is slowing down would affect you.

I'm closing this. Will reopen later if necessary


Zabbix 5.4: method not found. Incorrect API "application"

Describe the bug
I began rebuilding my Zabbix/Grafana monitoring again from scratch (I wanted to start over) using Docker containers.
I had everything functional and suddenly Grafana won't display some values on a Dashboard with error Incorrect API "application". I haven't been able to narrow down exactly why some values will display and some wont.
I went so far as to start over with Grafana in case I I'd caused the issue but a fresh installation of Grafana and the plugin result in the same issue.
Expected behavior
Grafana should show all widgets.
Screenshots
Non-functional default Zabbix Dashboard

Error from non-functional default Zabbix Dashboard

Other default dashboard still functional: (Github won't let me upload it for some reason)
https://imgur.com/a/llyY3Kp
Network data
{"datasourceId":1,"method":"application.get","params":{"output":"extend","hostids":[]}}
{"error":"Internal Server Error","message":"Method not found. Incorrect API \"application\"."}
Software versions

Grafana
Zabbix
Grafana-Zabbix Plugin

7.5.4
5.4.0rc1
4.1.4

To be clear, I'd spent all day yesterday building a dashboard with various data on it and everything functioned fine. Near the end of that work while I was editing a widget I started receiving this error and I haven't been able to figure out what is causing it.

I checked the latest Zabbix API docs and application.get seems to be there. So I guess it's Zabbix bug (rc1 is not a stable version, so this is more than probable).

@alexanderzobnin, it's not a bug, it's a feature: ZBXNEXT-2976. Likely changes have not been documented yet. But it's clear that applications are gone.

Confirm, critical implementing from Zabbix, breaking this plugin completely.

Anyone got any pointers how to downgrade zabbix? Through apt or something

@TheCoolOne123, it is not possible if you don't have DB backup. During major upgrades Zabbix server and proxies apply database upgrade patches which are irreversible. You can downgrade Zabbix server binary through package manager like you usually do, but it will likely complain about DB version mismatch.

Any pointers on that, i've not been sucessfull going back to 5.3-beta2

It looks like application API was deleted in 5.4 https://support.zabbix.com/browse/ZBXNEXT-2976

Yes, and long time ago. Now Zabbix 5.4.0 Beta 3 are so-so stable build, but this "improvement" completely break you great plugin functionality. And no way to downgrade Zabbix (only revert to backup dump of mysql base).

Yes, and long time ago.

..and in 100% secrecy. Zabbix does not share design documents and still has not updated documentation (proof). Please understand that @alexanderzobnin  can't start working on the fix before new API is documented. I encourage you to contact Zabbix and share your opinion on their policies.

Thanks for the replies, everyone - I'm sort of glad it isn't just me - I thought I was going crazy.
I appreciate your work, @alexanderzobnin - I eagerly but patiently await your fix [for Zabbix's trash fire.]
cheers!

Grafana 8.0.0 beta1  and Zabbix 5.4.0 0.8rc2 - Error still exist.

Hi, now the stuff it's gonna explode. I stepped into this bug because my automatic docker script upgraded today to zabbix to 5.4 .
Shame on zabbix to release undocumented changed which brakes backward compatibility.

Welcome to the party, everyone. Have some popcorn while we wait for Zabbix.

Well, at least changes are documented now:

Upgrade Notes
API Changes
Item Tag

Zabbix 5.4.0 Error still exist.(

Not sure if known, but I discovered a hack in Grafa  to resurrect broken graphs. You edit your graph and then remove the content of "Application" field, leaving the item and the rest of them untouched, then it started to present graph. Discovered accidentialy because one of graphs had the application field empty and that one worked well after zbx 5.4.0 kicked in yesterday.
Link to evidence.

I can confirm this workaround works, I am running zabbix 5.4.0 and Grafana v7.4.2. You still get the "Method not found. Incorrect API "application"." error but at least you can see the data!

privjet @alexanderzobnin
thanks for the quick fix, but the error has not yet been completely resolved (please reopen this Ticket).
Now i get all values again, but i get this error message when I refresh.

@StefanSa you obviously cannot use Applications since it were removed in Zabbix. This is only compatibility fix, Applications will be replaced by tags in next plugin release.

Spasibo @alexanderzobnin
thank you for the clarification

Thank you @alexanderzobnin. I'm also waiting for this.

I have managed to fix by deleting data source and adding again with the same name.

Not sure if known, but I discovered a hack in Grafana to resurrect broken graphs. You edit your graph and then remove the content of "Application" field, leaving the item and the rest of them untouched, then it started to present graph. Discovered accidentialy because one of graphs had the application field empty and that one worked well after zbx 5.4.0 kicked in yesterday.
Link to evidence.

thanks bro..... this trick is  working

@StefanSa you obviously cannot use Applications since it were removed in Zabbix. This is only compatibility fix, Applications will be replaced by tags in next plugin release.

Hello, do you have an estimate when the next plugin release will arrive?
For us this is a blocking factor at the moment to upgrade Zabbix because it will break our Grafana graphs completely.
Thanks.

Zabbix 5.4.2 on Ubuntu 20.10, Grafana v8.0.5 (cbb2aa5001.
Same problem:
Method not found. Incorrect API "application".
Are there any plans to finally fix this? It breaks many Grafana dashboards. :/

UPDATE:
Upgraded alexanderzobnin-zabbix-app to v4.1.5 in Grafana and everything works without any problems!
Thank you, guys!

UPDATE #2
Although all of my Grafana panels/graphs work, I am unable to query 'Application' items:

@akibukis, see https://github.com/alexanderzobnin/grafana-zabbix/issues/1188#issuecomment-844095602


Fix several Puppet lint issues

Please merge.

The Travis CI issues are solved via #51.

This should also be addressed in https://github.com/codylane/golja-influxdb/tree/devel


Network Provider: Hardened UNC Paths (SYSVOL)

[] 16.05.2022 15:05:49 - Getting machine information
[] Domain role: MemberServer
[] Windows: Windows Server 2022 Datacenter
[] Windows edition: ServerDatacenter
[] Windows version: 2009
[] Windows build: 20348.1.amd64fre.fe_release.210507-1500
[] System-locale: de-DE
[] Powershell Version: 5.1
Commandline:
Invoke-HardeningKitty -EmojiSupport -FileFindingList .\lists\finding_list_msft_security_baseline_windows_server_2022_21h2_member_machine.csv
ID 10653, Network Provider: Hardened UNC Paths (NETLOGON), Result=RequireMutualAuthentication=1,RequireIntegrity=1, Severity=Passed
[😿] ID 10654, Network Provider: Hardened UNC Paths (SYSVOL), Result=RequireMutualAuthentication=1,RequireIntegrity=1, Recommended=RequireMutualAuthentication=1, RequireIntegrity=1, Severity=Medium
The recommendation of the second case. contains a space character and might lead to the Severity=Medium instead of Severity=Passed. Both cases are configured exactly the same on my systems.

Hi Felix
Thank you for rising this issue. I created a workaround for Hardened UNC path in the development version of HardeningKitty, see https://github.com/0x6d69636b/windows_hardening/commit/05f2a2d9728de6ea4437020baf3bed4ddff6a3d5. In the next release this exception will published on this repo as well.

And now I released a new version and this issue is fixed in this repo as well


HTML

HTML
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
so that I easily find and view information.
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and JavaScript with associated notes listed

.


feat: added some caching

Description
TODO: Need to do vary by in certain cases and also, this might be better handled at the middleware level.
What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Steps to QA

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[ ] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

Closing this for now. Will revisit.


Install Stave via pip

This PR fixes #183.
Description of changes

Add setup.py and MANIFEST.in to package Stave. MANIFEST.in includes two package data:

Copy db.sqlite3 to stave/simple-backend/nlpviewer_backend and modify settings.py to reroute database to the new path.
Copy build folder to stave/simple-backend/nlpviewer_backend/lib/.

Update StaveViewer interface: remove the build_path parameter since it is already copied to the same directory of stave_viewer.py. manageproject.py is also updated to reflect this change.

Possible influences of this PR
Larger repo size because of the build folder. May be harder to maintain since every update to the frontend code should be manually migrated to the build folder under stave/simple-backend/nlpviewer_backend/lib/ (by running npm run build and then copy the build/ to the package path).
Demonstration of results

Install

Approach 1: Go to stave/ and run pip3 install ..
Approach 2: The source archive and built distribution are already uploaded to TestPyPI. Run the following command to install:

pip3 install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple stave

Test Snippet

from nlpviewer_backend.lib.stave_viewer import StaveViewer
sv = StaveViewer(in_viewer_mode=False)
sv.run()
sv.open()

May be harder to maintain since every update to the frontend code should be manually migrated to the build folder under stave/simple-backend/nlpviewer_backend/lib/ (by running npm run build and then copy the build/ to the package path).

We can automate this process as a Github action like here: https://github.com/asyml/forte/blob/master/.github/workflows/main.yml#L150
So it can automatically build the project if you create a tag, and upload it to PyPI as a version. You can also make an individual workflow that can be triggered manually: https://github.com/asyml/forte/blob/master/.github/workflows/pypi.yml

This PR is migrated to #186.


Feature Request: Improve services/regulated-assets-approval-server tests

What would you like to see?
A few outstanding items

Use cases for the ServeHTTP for both json and form and also all edge cases for h.isRejected tests the same parts of the code three times.

Have full coverage of all edge cases for the json.
Cover just the happy path for the other two options.

Add a unit test for the TOML file.

Tests were improved in prior PRs
https://github.com/stellar/go/pull/3595
https://github.com/stellar/go/pull/3592
https://github.com/stellar/go/pull/3590


Face number-of-glyphs() / number-of-faces() methods missing

Changed documentation to match actual names; num-glyphs() and num-faces().


Backreference Subjects

Currently, when we look up an artifact on Rekor we do not get the full graph of attestations.  We can solve this issue by performing lookups in a recursive manner on subjects that have a GID relating to the pipeline run or source material
For example:

Gitlab Attestor has:
https://witness.dev/attestations/gitlab/v0.1/joburl:https://gitlab.com/testifysec/demos/witness-demo/-/jobs/2147238887
https://witness.dev/attestations/gitlab/v0.1/pipelineurl:https://gitlab.com/testifysec/demos/witness-demo/-/pipelines/481493969

Git Attestor Has
https://witness.dev/attestations/git/v0.1/commithash:c55ea178682d9df6b759d0726e4aff49c2557cae

When witness verify finds an attestation that satisfies at least one step defined in the policy it should make a rekor query for backreference subjects as indicated in the attestation definition.
Recursion should continue until a MAX_DEPTH is reached, the policy is satisfied, or all backreference subjects have been searched.
We should also provide the evidence, or references of the evidence to the client as part of our public API as a part of this PR.

@mikhailswift this is the API I had in mind.  I've never worked with custom struct tags before, but it looks pretty easy.
	JWT          *jwt.Attestor `json:"jwt,omitempty"`
	CIConfigPath string        `json:"ciconfigpath"`
	JobID        string        `json:"jobid" use:"subject"`
	JobImage     string        `json:"jobimage"`
	JobName      string        `json:"jobname"`
	JobStage     string        `json:"jobstage"`
	JobUrl       string        `json:"joburl"`
	PipelineID   string        `json:"pipelineid"`
	PipelineUrl  string        `json:"pipelineurl" use:"backref,subject"`
	ProjectID    string        `json:"projectid"`
	ProjectUrl   string        `json:"projecturl"`
	RunnerID     string        `json:"runnerid" use:"subject"`
	CIHost       string        `json:"cihost"`
	GitHash	     string    	   `json:"githash" use:"backref:sha1,subject:sha1"`
}

https://github.com/testifysec/witness/blob/main/pkg/verify.go#L44
this should be changed to support a reference to the evidence.  i.e. rekor uid

https://github.com/testifysec/witness/blob/main/pkg/verify.go#L109
we should be able to grab the 'backref' subjects here

We should make the public API for this feature available in the Rekor package.
https://github.com/testifysec/witness/blob/main/pkg/rekor/rekor.go#L15

policy.Verify needs to return the steps that pass validation so we can marshal them and get the backref subjects to begin the search.


Post editing improve

Post editing should allow thumbnail changing, but nothing else is changeable after publish.

@feruzm  I think it is already supported, is it malfunctioning?

@noumantahir melinda earlier reported similar issue, looks like it was image link issue... 👍


Windows 2008 R2 support

I've been trying out the framework on Win 2008R2 (64bit), BizTalk 2009 and VS 2008. The BizTalkDeploymentFramework.targets needs a new target  for 2008R2 (see below). Also, in the Windows 2008 SetWinVer60 target, the PropertyName should be Win2008.

This work item was migrated from CodePlex
CodePlex work item ID: '4997'
Assigned to: 'tfabraham'
Vote count: '2'

[tfabraham@10/13/2009]
Is there a functional reason for this, or just to properly display the OS name in the output?

[UnknownUser@11/11/2009]

[giuliov@11/11/2009]
I found the same issue. MSBuild stops with an error otherwise.

[tfabraham@11/11/2009]
Could someone post the error message please?  I do not have a 64-bit OS to test with, so I am somewhat in the dark on this one.  Thanks!

[robertkokuti@11/13/2009]
It is a WS2008R2 issue, not a 64bit one. For WS2008R2, the OSVersion is advanced to 61, so the BizTalkDeploymentFramework.tragets build script calls the target 'SetWinVer61' target here:

[tfabraham@11/13/2009]
Got it.  Thank you for the clarification.

[UnknownUser@1/3/2010]

[UnknownUser@1/3/2010]
Associated with changeset 33024.

[UnknownUser@1/3/2010]
Associated with changeset 33025.

[UnknownUser@1/3/2010]
Resolved with changeset 33030.

[UnknownUser@2/21/2013]

[UnknownUser@5/16/2013]


ArgumentException when using a float/boolean uniform in shader

When using a single value uniform float or boolean in a shader, the following Exception occurs in UniformBuffer.fs createLeafTransformation: transpose:bool -> outputType:Type ->input : Expr -> Expr:

for a boolean

An unhandled exception of type 'System.ArgumentException' occurred in FSharp.Core.dll

System.ArgumentException was unhandled
Message: An unhandled exception of type 'System.ArgumentException' occurred in FSharp.Core.dll
Additional information: Type mismatch when building 'f': expected function type in function application or let binding. Expected 'Microsoft.FSharp.Core.FSharpFunc`2[T,TResult]', but received type 'Aardvark.Base.PrimitiveValueConverter+booleanConversions@155'.

for float:

An unhandled exception of type 'System.ArgumentException' occurred in FSharp.Core.dll

System.ArgumentException was unhandled
Message: An unhandled exception of type 'System.ArgumentException' occurred in FSharp.Core.dll
Additional information: Type mismatch when building 'f': expected function type in function application or let binding. Expected 'Microsoft.FSharp.Core.FSharpFunc`2[T,TResult]', but received type 'Aardvark.Base.PrimitiveValueConverter+fractionalConversions@146-2'.

The error occurs on following setup
Type that represents object which influence the rendering result:
type PseudoType = {
        PseudoBool      : bool
        PseudoFloat     : float
    }

Add to uniform scope:
 type UniformScope with
            member uniform.PseudoBool    : Arr<N<Config.LTC.maxNumberOfPolygonLights>, bool>  = uniform?PseudoBool
            member uniform.PseudoFloat   : Arr<N<Config.LTC.maxNumberOfPolygonLights>, float>  = uniform?PseudoFloat

There are more of the PseudoType objects that are used in the shader, so they are loaded as an array
let unpack f = Mod.map (fun x -> x |> Seq.map f |> Seq.toArray) l

sg
    |> Sg.uniform "PseudoBool" ( unpack (fun x -> x.PseudoBool) )
    |> Sg.uniform "PseudoFloat" ( unpack (fun x -> x.PseudoFloat) )

The error occurs when they are used in the shader such that they effect the resulting color.
let private FragmentShader(v : Effects.Vertex) =
    fragment {
        let mutable sum = 0.0
        for i in 0 .. uniform?NumberOfPseudoTypes - 1 do
            let mutable pseudo = 1.0

            if uniform.PseudoBool.[i] then
                pseudo <- uniform.PseudoFloat.[i]

            sum <- sum + pseudo

       return V4d(sum, sum, sum, 1.0)
    }

If the shader does not use them, as shown in the following code, no exceptions are thrown
let private FragmentShader(v : Effects.Vertex) =
    fragment {
        let mutable sum = 0.0
        for i in 0 .. uniform?NumberOfPseudoTypes - 1 do
            let mutable pseudo = 1.0

            if uniform.PseudoBool.[i] then
                pseudo <- uniform.PseudoFloat.[i]

            sum <- sum + pseudo

       return V4d(1.0,1.0,1.0,1.0)
    }

see https://github.com/vrvis/aardvark.rendering/blob/a894c4f8e80763d829aa4dbe5718deb9155b8a7f/src/Demo/Scratch/Experiments/RecordUniforms.fs


Adding Pick your Poison crashes apon startup

Mod Name
Pick Your Poison
Mod Homepage
https://modrinth.com/mod/pick-your-poison
Minecraft version
1.20.1
Describe the bug
Adding Pick your Poison crashes apon startup
Steps to reproduce

Add pick your poison to the mods list
start the instance
crash
...

Logs
https://mclo.gs/P5NsDTC
Additional context
No response

As our LTS support target, 1.20.1 now only receives critical fixes related to Connector bugs. Please upgrade to the latest version for mod compatibility support.


PKCS#7: initial support

needed on the way to implement the SCEP certificate enrollment.
The ultimate intention is  to implement the CISCO's enrollments protocols (SCEP and EST) for ESP32 with the primary support of secure element (smart card) in the limits needed to enroll the certificate and use it for SSL/TLS .

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

Hi @viktorTarasov ,
Thanks for sending this contribution and for your patience while someone got back to you.
As you've probably noticed, last month we refactored mbedTLS to be hosted from a submodule which is a fork of the upstream project with a few minor fixes/tweaks (that we intend to contribute back).
For major new non-ESP32-specific funcionality like this, we'd very much prefer that it went via the upstream project first and then we can update once mbedTLS releases a new version. Have you considered sending this to the mbedTLS project directly?
Angus

As @projectgus mentioned, it will be great if you can raise this as PR on mbedtls project, we try to keep in sync with their latest release with minimal or no-changes from our side. For now I will close from here. Thanks.


runtime/abi: poll_oneoff: support clock event type

Currently poll_oneoff suspends the program if clock event type is specified.
See https://github.com/CraneStation/wasmtime/blob/master/docs/WASI-api.md#poll_oneoff

Not sure if this is appropriate for Gate at this level.


'Parse/Parse.h' file not found when using cocoapods1.0.0

It's ok when I using cocoapods 0.x, but yesterday I update to 1.0.0, 'Parse/Parse.h' file not found.
My Podfile is:
platform :ios, '8.0'
use_frameworks!
target 'MyApp' do
pod 'Parse'
end

Build success when select simulator, but wrong when select devcie.

I have the same error even with simulator.

I have the same issue - if I comment out use_frameworks! it works again - however this is not an option for me as I need to include for IBdesignables. Only happened after updating cocoapods to 1.0.0

@skyhacker2 Did you manage to resolve this? I was unable to build for device and simulator - until I remove use_frameworks from my podfile and update.

I've rolled back to cocoapods 0.39.0, hit update pods - and all good again... hmmm

There's bug fix in cocoapod 1.0 that I need.  Too bad I can't really rollback to 0.39.0.  I hope there's quick fix.  Removing use_frameworks doesn't work for me neither as most of my pods are swift.

@DeepLight No, Now I just temporarily removed use_frameworks! .

Hey everyone, this seems to work now as of 1.14.1.
Please reopen/comment here or open a new issue if you guys still experience this issue.


PROV Data Model

Develop a simple graphical and or tabular representation of how the used PROV model looks like.
The initial model can be the one used by #2.
Annotate nodes with their type.

Models have been added to the docs/ directory.


Documentation is out of date

Noticed there were a few places where it was confusing v3 versus v4 usage. And in the v4 usage, there are several references to --envs which isn't a thing. Just FYI. Thanks for the great work.

Thank you to @tingaloo for fixing the documentation in https://github.com/rocketjob/symmetric-encryption/pull/85


What is TP and SL?

Take Profit, Stop Loss. Google is your friend to find out more.

@mengjin-tes  Check out https://www.investopedia.com/terms/s/stop-lossorder.asp

Thanks, I'm referring to your code to implement the version of golang. Thank you for your dedication.


created new button

this is my first pull request in hacktoberfest

Thank you for your contribution. 🤩
Please Star the repo and Follow. 🌟


run: do not duplicate stdio if it is not a terminal

running containers under ginkgo or go test was causing issues
trying to duplicate stdio. with this patch stdio will be
duplicated only if stdio is a terminal
fixes #208
Signed-off-by: Julio Montes<EMAIL_ADDRESS>

Coverage remained the same at 39.171% when pulling 4983c8207c333ec5efdcfb74eea9b4602e7492dd on devimc:topic/fixDupStdio into 66b54638c5125167fe852dce4a45c2a1d01c9e27 on clearcontainers:master.

Coverage decreased (-0.2%) to 37.812% when pulling 7a461e9ef82421f3215ba712ce63c40155283a89 on devimc:topic/fixDupStdio into 946820d426c0566c2bd8362d366c2cfa40c191dd on clearcontainers:master.

Coverage decreased (-0.2%) to 37.812% when pulling 3b7122543f4d88af26a94fc401b2ba881a738a7c on devimc:topic/fixDupStdio into 946820d426c0566c2bd8362d366c2cfa40c191dd on clearcontainers:master.

@sameo fixed

Coverage increased (+0.2%) to 38.214% when pulling 00247d3518197dcb2f3c1985c9ee663c78dce185 on devimc:topic/fixDupStdio into 946820d426c0566c2bd8362d366c2cfa40c191dd on clearcontainers:master.

Coverage increased (+0.2%) to 38.214% when pulling 4218877d42c9d5123624ca988c18117f1ca83db7 on devimc:topic/fixDupStdio into 10cd35e9b4a1f12ac1e7b09d484ad68333aab349 on clearcontainers:master.

LGTM

LGTM


Typo: Replaced = with space

Looks like a typo to me.

Thanks - I took the opportunity to regenerate vs Go 1.12 at the same time.


Flag spin_forts doesn't work

I tried to debug it and print str(config.spin_forts) in pokecli.py, it says {u'avoid_circles': False, u'max_circle_size': 10}. What is wrong?
Expected Behavior
when I config spin_forts to false, it should not spin the forts.
Actual Behavior
when I config spin_forts to false, it still spins the forts.
Steps to Reproduce
just try set spin_forts to false
Other Information
OS:
Git Commit: (run 'git log -n 1 --pretty=format:"%H"' and paste it here)

Please specify the OS and Git Commit


(chore): New readme badges plus added renovate bot

Closes #42

Pull Request Test Coverage Report for Build 323249652

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 323236424:
0.0%

Covered Lines:
36

Relevant Lines:
36

💛  - Coveralls


feat: Move logging to log crate

Fixes #2
This implementation uses the log crate, as specified, for providing the mechanism by which messages are logged. Additionally, the fern crate is used to control the output. If you'd like to use something else as mentioned in #2, just let me know. Currently, log messages look like:
[2020-10-01][14:29:57][s3rename][DEBUG] debug message
[2020-10-01][14:29:57][s3rename][INFO] debug message
[2020-10-01][14:29:57][s3rename][WARN] warn message
[2020-10-01][14:29:57][s3rename][ERROR] error message

This is controlled by the strings passed to format_args! and chrono's format, so they're easily tweakable.
By nature of setting a logger to show debug messages, when --verbose is passed, the value of --quiet is ignored. If this isn't what you're looking for, let me know and we can work out how it'd best be presented.

Thanks, this looks great, I'll test and merge the build tonight and add CI to this repo.

Cool! Happy to help. Happy October!


Adds space between "your local" and IRCC on the confirmation page.

Before
After

|

I alluded to this ~bug~ not actually a bug when the abbreviation PR was merged.
Adding an extra space throws off our french translation, ie we end up with d‘ IRCC on the page, which isn't right. So we added an extra space to the english messages.json file. For some reason, it doesn't show up when you run yarn dev (the extra space is missing), but it does show up when you run yarn start.
So the app when it's deployed always looks good. When developing locally, we just have to grit our teeth and ignore it. :(


Error when including customHelpMenuSections

When deploying metadata to packaging org, receive the following message:
No parser configuration found for subdirectory customHelpMenuSections
Is tied to a CCI error - https://github.com/SFDO-Tooling/CumulusCI/issues/1832

CCI bug has been resolved so added back in on most recent commit.


Question on statefile for the backend

Is there a requirement that the tfstate file for the backend resources needs to be part of the deployment that uses the backend? I don't see anything in the docs regarding this but whenever I deploy with the s3/dynamo backend, terraform always tried to destroy the s3 state bucket and dynamodb lock table. I wouldn't think they are necessarily coupled but maybe it's a requirement by terraform? Makes for very messy deletion because you're deleting backend resource at the same time as everything else.

@rtomlinson-latacora this sounds like maybe you're initializing the state backend, but then not importing the state. Please note this workflow is different from every other terraform module invocation. We have documented the process here: https://github.com/cloudposse/terraform-aws-tfstate-backend#usage and we've scripted it here: https://github.com/cloudposse/terraform-root-modules/blob/master/aws/tfstate-backend/scripts/init.sh
Basically, the process is you provision the backends using terraform but without remote state. Then you re-run terraform init with backends configured and it will prompt to import the backend state to S3.

@osterman If I'm understanding this correctly, the point of the script is to make the backend resources part of state. That is effectively what the second terraform init is doing. All resources that you later add, will also be a part of this state. You have one state file which has the backend resources plus anything else you add to your deployments.

That's sounds correct. One backend can be shared by multiple projects. Just use different key prefixes (e.g. us-west-2/vpc/terraform.tfstate). We recommend using one bucket per AWS account. Also, for true terraform-HA don't even share the bucket across regions.

Okay, I think I'm sorta understanding how you would namespace the other backends. I'll just do a little experiment to confirm. Since you're storing the state file that manages the dynamodb and bucket for the backend itself in said bucket, you'd obviously run into problems when trying to delete the backend. And since deleting the backend shouldn't need to occur often I'm assuming that this is just a management cost that you'd have to deal with in the event that you actually need to do something with the backend.

@rtomlinson-latacora here's the process of destroying the bucket: https://github.com/cloudposse/terraform-root-modules/blob/master/aws/tfstate-backend/scripts/destroy.sh

@rtomlinson-latacora thanks for reporting your issues with the coldstart process and destruction. If you have further issues, please let us know! I'm going to close this issue for now.


Drop the okhttp-bom module

I think the benefit is unclear and it's already cost me 90 minutes of fighting
with Maven central.

It might be possible to make the BOM work, but it’s not working now and I don’t have the patience to fight it any longer.

@swankjesse damn, just as gradle 5.2 adds better support.  Agree this is appropriate.  FWIW I've found the benefit of bom to be when using common libraries like jackson or netty and avaoiding mixing versions transitively.

I think we gotta follow their structure, possibly making the parent project extend the bom vs. being independent?
I assume the parent pom can't be the the boom?


Remove deprecated function runSimulation

runSimulation function (_technical_indicator module of tti.indicators package) has been replaced by the getTiSimulation function in release 0.1.b3. It should be removed prior to release 1.0.0
Tasks:

[x] Remove runSimulation function from module
[x] Remove the TtiPackageDeprecatedMethod exception from the tti.utils package, exceptions module
[x] Remove unit test case for the runSimulation function
[ ] Execute regression testing

Ran 1558 tests in 507.587s
OK

Ran 1558 tests in 507.587s
OK


[pentest] Add new alert handler to tests

This commit adds the new alert handler format to the Ibex FI tests.

Merging this PR since ci just failed due to a flaky test.


Create console scripts

Description of the Feature
Commands like python -m kivymd.tools.patterns.create_project are unwieldy and can be improved via console scripts. For example, the aforementioned command can be shorted to create_project via a console script.

@JulianOrteil
python kivymd/tools/release/make_release.py release 1.0.1 1.1.0.dev0 - https://kivymd.readthedocs.io/en/1.0.0/api/kivymd/tools/release/make_release/

@JulianOrteil
python -m kivymd.tools.patterns.add_view - https://kivymd.readthedocs.io/en/1.0.0/api/kivymd/tools/patterns/add_view/

@HeaTTheatR Both modules are implemented as requested. PR is ready to merge unless you have others you'd like done.


Fix export map example and explain

@DanielRosenwasser can you take a look? We should maybe update the blog post too.

Huh, I was going to copy these changes back to the release notes, but the export map example there is different and already correct


Improve starter docs

Docs need to be made more clear for work enviornment setup

@jakeangus  Is this still the case or are docs good enough now?


Clean result message code in test-js-with-node.

Remove duplicate code after quick fix in passing returned code.
Fixes: 1489.

Automated message from Dropbox CLA bot
@TomaszKolek, it looks like you've already signed the Dropbox CLA. Thanks!

Merged, thanks @TomaszKolek!


HADOOP-18695. S3A: reject multipart copy requests when disabled (#5548)

Description of PR
cherrypick of #5548
How was this patch tested?
aws cloud tests in progress
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

all good test run
time mvit -Dparallel-tests -DtestsThreadCount=8 -Dscale -Dprefetch

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 46s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 8 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
39m 17s

branch-3.3 passed

+1 :green_heart:
compile
0m 33s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 31s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 41s

branch-3.3 passed

+1 :green_heart:
javadoc
0m 35s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 20s

branch-3.3 passed

+1 :green_heart:
shadedclient
25m 48s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 35s

the patch passed

+1 :green_heart:
compile
0m 29s

the patch passed

+1 :green_heart:
javac
0m 29s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 19s

the patch passed

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 22s

the patch passed

+1 :green_heart:
spotbugs
1m  9s

the patch passed

+1 :green_heart:
shadedclient
25m 20s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 27s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 33s

The patch does not generate ASF License warnings.

103m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5658/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5658

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux ce0165cab71a 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / d1f90f880923f345fc5d3d9a32b790edfd01a22a

Default Java
Private Build-1.8.0_362-8u362-ga-0ubuntu1~18.04.1-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5658/1/testReport/

Max. process+thread count
572 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5658/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Change icons to materialdesignicons

mdi doesn't show properly.

Now fixed!

It turns out this was for the main site.

Closing this as default.html is now ngMaterial!


fix clang installation instruction for debian os

Added clang-3.9 to debian install command. Without it, cargo build of libbindgen-tutorial-bzip2-sys fails with:
/usr/include/stdio.h:33:11:` fatal error: 'stddef.h' file not found, err: true

Hmm, interesting, thanks!
@bors-servo r+

:pushpin: Commit 839e977 has been approved by emilio

:hourglass: Testing commit 839e977 with merge c85fa24...

:sunny: Test successful - status-travis
Approved by: emilio
Pushing c85fa24f1697d5f53c4d5cff8954b10f1ca56543 to master...


Remove hand types, and just use symbols, to make core method type-stable

I think, for progress sake, this seems like a good idea. Pros / cons:

Pro: the core method, evaluate5, is now type-stable, and can be type-stable all the way up the call graph
Con: this kind of limits us to the CPU because symbols are not isbits, but I think that's okay.

Ultimately, the hand type is, at the moment, only needed for log/IO purposes, and the actual return integer is the key piece. If we wanted to still make this data available, we could return integers for the hand type and encode which hand type we have based on the second returned integer.

bors r+

bors r+


Update rainbow_circular_buffer.yml

replace learn_schedule with min_replay_history in config

Marlgrid configs are going to be updated with #204.

You need to update wandb settings
Rename the configs according to comments in #204

Changes already integrated with other branches


ERROR: No matching distribution found for functorch==0.1.0

Hi,
Thanks for great research work.
I'm trying to install by following the instructions, but encounter an error, see below.
The conda create command works fine:
(base) joel@ubuntu:~/TPSR$ conda create --name tpsr python=3.7
Channels:
 - defaults
Platform: linux-aarch64
Collecting package metadata (repodata.json): done
Solving environment: done

## Package Plan ##

  environment location: /home/joel/miniconda3/envs/tpsr

  added / updated specs:
    - python=3.7

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    certifi-2022.12.7          |   py37hd43f75c_0         149 KB
    openssl-1.1.1w             |       h2f4d8fa_0         3.7 MB
    pip-22.3.1                 |   py37hd43f75c_0         2.7 MB
    python-3.7.16              |       h89984f6_0        44.8 MB
    setuptools-65.6.3          |   py37hd43f75c_0         1.1 MB
    wheel-0.38.4               |   py37hd43f75c_0          63 KB
    ------------------------------------------------------------
                                           Total:        52.5 MB

The following NEW packages will be INSTALLED:

  _libgcc_mutex      pkgs/main/linux-aarch64::_libgcc_mutex-0.1-main
  _openmp_mutex      pkgs/main/linux-aarch64::_openmp_mutex-5.1-51_gnu
  ca-certificates    pkgs/main/linux-aarch64::ca-certificates-2023.12.12-hd43f75c_0
  certifi            pkgs/main/linux-aarch64::certifi-2022.12.7-py37hd43f75c_0
  ld_impl_linux-aar~ pkgs/main/linux-aarch64::ld_impl_linux-aarch64-2.38-h8131f2d_1
  libffi             pkgs/main/linux-aarch64::libffi-3.4.4-h419075a_0
  libgcc-ng          pkgs/main/linux-aarch64::libgcc-ng-11.2.0-h1234567_1
  libgomp            pkgs/main/linux-aarch64::libgomp-11.2.0-h1234567_1
  libstdcxx-ng       pkgs/main/linux-aarch64::libstdcxx-ng-11.2.0-h1234567_1
  ncurses            pkgs/main/linux-aarch64::ncurses-6.4-h419075a_0
  openssl            pkgs/main/linux-aarch64::openssl-1.1.1w-h2f4d8fa_0
  pip                pkgs/main/linux-aarch64::pip-22.3.1-py37hd43f75c_0
  python             pkgs/main/linux-aarch64::python-3.7.16-h89984f6_0
  readline           pkgs/main/linux-aarch64::readline-8.2-h998d150_0
  setuptools         pkgs/main/linux-aarch64::setuptools-65.6.3-py37hd43f75c_0
  sqlite             pkgs/main/linux-aarch64::sqlite-3.41.2-h998d150_0
  tk                 pkgs/main/linux-aarch64::tk-8.6.12-h241ca14_0
  wheel              pkgs/main/linux-aarch64::wheel-0.38.4-py37hd43f75c_0
  xz                 pkgs/main/linux-aarch64::xz-5.4.5-h998d150_0
  zlib               pkgs/main/linux-aarch64::zlib-1.2.13-h998d150_0

Proceed ([y]/n)?

Downloading and Extracting Packages:

Preparing transaction: done
Verifying transaction: done
Executing transaction: done
#
# To activate this environment, use
#
#     $ conda activate tpsr
#
# To deactivate an active environment, use
#
#     $ conda deactivate

However, the pip install -r requirements.txt command fails:
(base) joel@ubuntu:~/TPSR$ pip install -r requirements.txt
Defaulting to user installation because normal site-packages is not writeable
Collecting args==0.1.0 (from -r requirements.txt (line 1))
  Downloading args-0.1.0.tar.gz (3.0 kB)
  Preparing metadata (setup.py) ... done
Collecting attrs==21.4.0 (from -r requirements.txt (line 2))
  Downloading attrs-21.4.0-py2.py3-none-any.whl (60 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.6/60.6 kB 736.7 kB/s eta 0:00:00
Collecting backcall==0.2.0 (from -r requirements.txt (line 3))
  Downloading backcall-0.2.0-py2.py3-none-any.whl (11 kB)
Collecting cachetools==5.3.0 (from -r requirements.txt (line 4))
  Downloading cachetools-5.3.0-py3-none-any.whl (9.3 kB)
Collecting certifi==2021.10.8 (from -r requirements.txt (line 5))
  Downloading certifi-2021.10.8-py2.py3-none-any.whl (149 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 149.2/149.2 kB 2.1 MB/s eta 0:00:00
Collecting charset-normalizer==2.0.12 (from -r requirements.txt (line 6))
  Downloading charset_normalizer-2.0.12-py3-none-any.whl (39 kB)
Collecting clint==0.5.1 (from -r requirements.txt (line 7))
  Downloading clint-0.5.1.tar.gz (29 kB)
  Preparing metadata (setup.py) ... done
Collecting cloudpickle==2.2.1 (from -r requirements.txt (line 8))
  Downloading cloudpickle-2.2.1-py3-none-any.whl (25 kB)
Collecting coverage==6.3.2 (from -r requirements.txt (line 9))
  Downloading coverage-6.3.2-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (211 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 211.9/211.9 kB 4.5 MB/s eta 0:00:00
Collecting cycler==0.11.0 (from -r requirements.txt (line 10))
  Downloading cycler-0.11.0-py3-none-any.whl (6.4 kB)
Collecting decorator==5.1.1 (from -r requirements.txt (line 11))
  Downloading decorator-5.1.1-py3-none-any.whl (9.1 kB)
Collecting deepspeed==0.8.0 (from -r requirements.txt (line 12))
  Downloading deepspeed-0.8.0.tar.gz (749 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 749.9/749.9 kB 3.4 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
Collecting fonttools==4.31.2 (from -r requirements.txt (line 13))
  Downloading fonttools-4.31.2-py3-none-any.whl (899 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 899.5/899.5 kB 3.8 MB/s eta 0:00:00
ERROR: Could not find a version that satisfies the requirement functorch==0.1.0 (from versions: 1.13.0, 1.13.1, 2.0.0)
ERROR: No matching distribution found for functorch==0.1.0

Here is some information on my platform:
(base) joel@ubuntu:~/TPSR$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.3 LTS
Release:	22.04
Codename:	jammy
(base) joel@ubuntu:~/TPSR$ uname -a
Linux ubuntu 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:29:11 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

Thanks for any advise on how to resolve!
/Joel

Hi @joelonsql , Thank you for reaching out and for your interest in our project!
It looks like the functorch version might not be compatible with your setup. This repo works best with functorch==0.1.0 and torch==1.11.0, paired with python 3.7. Could you let me know which Python version you're using in your tpsr environment? Also, make sure to activate the environment with conda activate tpsr before installation.


In-Game: Can't buy group Forum

When you goes to Forum Page in Catalog, gives an Critical Exception, in wrong Request.
Probably packet is wrong, and this happens because the structure is wrong (because the sended packet is wrong)

Fixed


Get a domain for the association

It would be nice to have one

Took two domains on Infomaniak, where I set up a PoC Association account:

cloud-native-romandy.ch (primary)
cloud-native-suisse-romande.ch

It will take a while to provision everything, but stubs are there


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 216 ms

Resolved: ClamAV performance has improved in 83d36ba after 534 days, 17 hours, 36 minutes.


fix: resolve mobile keyboard fluctuation during search

Fixes Issue
closes #9208

Changes proposed
fixed the issue where the mobile keyboard would intermittently disappear and reappear during searches by replacing the usage of router.replace with window.history.replaceState.

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Current behavior:
https://github.com/EddieHubCommunity/BioDrop/assets/73095526/a3b02cf0-809b-4456-8617-3c46b42b9829
Expected behavior:
https://github.com/EddieHubCommunity/BioDrop/assets/73095526/c901ed95-9702-409c-b774-7f414195d8a0

Note to reviewers
Users can use the back button and also share a deep link to their search results.
https://github.com/EddieHubCommunity/BioDrop/assets/73095526/20d4ec8e-e92e-4d4a-8088-7f84ec8f4fd6

Hey, any news regarding this PR? Thanks.

@eddiejaoude any advice or guidance regarding this PR

Sorry I am moving house and country so behind on notifications at the moment

Thanks @sital002 for your great suggestion👍 @eddiejaoude can you take a look now

I think we should wrap the input in a form and only update the URL on submit instead on change since we are planning to do a db call for searching users using on change will have unnecessary db calls this will solve the fluctuation error the issue is whenever we update the query params using next router the default behavior is that it rerenders the whole page this means it is running all the useEffect every time the input data changes and the focus  is rerunning.

I think we should wrap the input in a form and only update the URL on submit instead on change since we are planning to do a db call for searching users using on change will have unnecessary db calls this will solve the fluctuation error the issue is whenever we update the query params using next router the default behavior is that it rerenders the whole page this means it is running all the useEffect every time the input data changes and the focus  is rerunning.

Thank you for your co-operation. That's a great idea👍
I would like to hear other maintainers thoughts on it since this will change searching behavior

I think we should wrap the input in a form and only update the URL on submit instead on change since we are planning to do a db call for searching users using on change will have unnecessary db calls this will solve the fluctuation error the issue is whenever we update the query params using next router the default behavior is that it rerenders the whole page this means it is running all the useEffect every time the input data changes and the focus is rerunning.

I think this is a good idea also 👍

Test on local environment works well
can you add the missing dependency on the useEffect https://github.com/EddieHubCommunity/BioDrop/pull/9248/files/0db01c52abb61e2ac56b8a1fa776d825fbb8e50f..0272140c79a7bfe45eb269408e7fc2138d34faca#diff-99c55e6229f7a0d904e59da5da6e77729e62b05852484cf2afff2e13292b50b1R147


Change reason not stored on delete

Describe the bug
If you add _change_reason to an object and then delete it, the change_reason is not stored in the historical model instance.
To Reproduce
Steps to reproduce the behavior:

Create an instance of a model that has a HistoricalRecords() field.
obj._change_reason='test'
obj.delete()

Expected behavior
Change reason should be added to the historical model instance.
Environment (please complete the following information):

Django Simple History Version: 3.2.0
Django Version: 3.2.14

I think it might have something to do with the instance in the post_delete signal not being the same as the instance that has been called delete on (if you look at the def delete on models.Model it uses a Collector and recreates the instance sort of).

Update:
The _change_reason was not stored, because I added it to the QuerySet instance of the model.. Oops, sorry to raise this issue!


Update successful measurements

A long delay between success measurements.
Collect the deltas between measurements if one delta less than one metre return one of nearby measurements.

The new algorithm checked two success deltas in row three times)


DRY Specifications via $ref

So I realize there is some discussions regarding some "similar" things, but I'm not quite sure they're similar enough - if so, please say so and I'll contribute to the other discussions accordingly and close this one out. Other similar but not quite as extensive discussions I have found:

https://github.com/OAI/OpenAPI-Specification/issues/556 : polymorphism around $ref
https://github.com/OAI/OpenAPI-Specification/issues/417 : paths and $ref

Basically, one should be able to write their OpenAPI specification in as DRY a manner as possible. Presently this is not possible because:

$ref is not valid at all the right places
allOf is not valid at the right places (which could make up for point 1)
$ref can't be specified numerous times next to itself appropriately

Let's give this some better clarity via an example. Discussing API Header Fields provides a good example such as the following which similar to #417 but I'm going more general where that seems to be focused on path objects:
paths:
    /:
        get:
            parameters:
                - $ref: `#/components/headers/x-my-header-1`
                - $ref: `#/components/headers/x-my-header-3`
            responses:
                '401':
                    headers:
                        $ref: `#/components/headers/x-my-header-1`
                        $ref: `#/components/headers/x-my-header-3`
                '403':
                    headers:
                        $ref: `#/components/headers/x-my-header-1`
                        $ref: `#/components/headers/x-my-header-3`
                '200':
                    headers:
                        $ref: `#/components/headers/x-my-header-1`
                        $ref: `#/components/headers/x-my-header-2`
                        $ref: `#/components/headers/x-my-header-3`
               '301':
                    headers:
                        allOf:
                            - $ref: `#/components/headers/x-my-header-1`
                            - $ref: `#/components/headers/x-my-header-2`
                            - $ref: `#/components/headers/x-my-header-3`
                default:
                    headers:
                        $ref: `#/components/headers/x-my-header-1`
                        $ref: `#/components/headers/x-my-header-3`
        post:
            parameters:
                - $ref: `#/components/headers/x-my-header-1`
                - $ref: `#/components/headers/x-my-header-2`
            responses:
                '401':
                    headers:
                        $ref: `#/components/headers/x-my-header-1`
                        $ref: `#/components/headers/x-my-header-3`
                '403':
                    headers:
                        $ref: `#/components/headers/x-my-header-1`
                        $ref: `#/components/headers/x-my-header-3`
                '200':
                    headers:
                        $ref: `#/components/headers/x-my-header-1`
                        $ref: `#/components/headers/x-my-header-2`
                        $ref: `#/components/headers/x-my-header-3`
                default:
                    headers:
                        $ref: `#/components/headers/x-my-header-1`
                        $ref: `#/components/headers/x-my-header-3`
    /howdy:
        delete:
            parameters:
                - $ref: `#/components/headers/x-my-header-1`
                - $ref: `#/components/headers/x-my-header-2`
            responses:
            '401':
                headers:
                    $ref: `#/components/headers/x-my-header-1`
                    $ref: `#/components/headers/x-my-header-3`
            '403':
                headers:
                    $ref: `#/components/headers/x-my-header-1`
                    $ref: `#/components/headers/x-my-header-3`
            '200':
                headers:
                    $ref: `#/components/headers/x-my-header-1`
                    $ref: `#/components/headers/x-my-header-2`
                    $ref: `#/components/headers/x-my-header-3`
            default:
                headers:
                    $ref: `#/components/headers/x-my-header-1`
                    $ref: `#/components/headers/x-my-header-3`
components:
    headers:
        x-my-header-1:
            required: true
            description: my first header
            schema:
            type: string
            format: uuid
        x-my-header-2:
            required: true
            description: my second header
            schema:
            type: string
        x-my-header-3:
            required: true
            description: my third header
            schema:
            type: integer

The above is missing a lot of stuff, but only in order to show the re-use and avoid having to put a complete spec here. I know some of the above can be fixed by moving up a layer in the referencing, e.g create a component for the header set and reference that instead; however that can then dictate a bad spec by forcing all headers to be pushed to header sets which then can also be an issue for 1-off header combinations.
Goal here is to enable spec writers to manage their specifications by creating re-usable modules that can be continuously re-used. To achieve this, $ref would need to be valid in essentially ever object to replace anything in the object. F.e if you have a description field you want to re-use, define it once and use it 10 times.
Two parallel $ref values should be valid and able to point to separate objects, neither being discarded, or allOf could be used to combine the contents of both $ref references to create the same effect (good solution for one-offs).
When building larger APIs using tooling like OpenAPI being able to be a DRY as possible is key to keeping bugs from creeping into the specs as it reduces the ability for any one instance to be mis-typed. For instance, if you had to type x-my-header-3 for every single Request object and x-my-header-2 for every single Response object - one typo of my-header-3 or xmy-header-3 could easily create something hard to detect where using the $ref objects would make it fail validation and be easily caught in gate checks (PR builders, etc).
To re-iterate - please let me know if I need to file this with JSON Reference/Schema too. I did not find anything suitably talking about these aspects while reading through any of the repos I came across, but have in general there does seem to be some of sentiment that this is an issue.

@BenjamenMeyer I'm not sure I follow your example as the only recognizable JSON Schema keyword is $ref.  Could you please show a bit more context?  In particular, please make clear what is OAS (because I don't have the whole OAS spec memorized) vs JSON Schema vs new proposals vs example names (e.g. I'm assuming "collection" is an example name, not a keyword of any sort)
Sorry I did not notice that you'd updated this, I try to keep on top of at-mentions but this one slipped through.

@handrews no problem: I'm not on github.com as much myself nowadays either so I may take a bit longer to respond too.
To answer your question, my example is very generic, kind of on purpose - so everything falls into being an example name.
To try to bring some more clarity...

I don't have the work I was doing accessible at the moment so going off the cuff for this...
I don't have the spec down either, so I used https://github.com/OAI/OpenAPI-Specification/blob/master/examples/v3.0/petstore.yaml as an example to draw some stuff from for the below.

But to take a stab at it against what I was doing it'd be something like:
# openapi.yaml
openapi: "3.0.0"
info:
    version: 1.0.0
    title: Example
paths:
    /:
        $ref: "root.yaml#/root"
...
------------------------------------------------------
# root.yaml
root:
    get:
        summary: hello
        operationId: getHello
        responses:
             '200':
                  $ref: "response.yaml#/helloWorld"
             '401':
                   $ref: "responses.yaml#error/auth_401"
    post:
        $ref: "submission.yaml#post/hello"
...
------------------------------------------------------
# responses.yaml
helloWorld:
    description: Hello World
    content:
        $ref: "#/content/json/hello/"
content:
     json:
         application/json:
              schema:
                  $ref: "#/schemas/hello"
...

Essentially, once past the basic path, almost anything could use a $ref to re-use the information.
And yeah, I know - I'm not following the general structure of the field naming at the top level; but this should be able to be structured in a way that makes sense to document writers and enables them to easily expand the document out and re-use material.

@BenjamenMeyer sounds like you are looking to add more $ref for things outside of the schema object, so that's outside of what I do with my JSON Schema hat on.
Since allOf is very much a JSON Schema construct relating primarily to constraints rather than definitions, I'm not sure it would make much sense outside of JSON Schema.  I could possibly be convinced otherwise, but I'd want to really understand how the semantics are consistent with the JSON Schema usage.  Otherwise, a different keyword would be preferred.
With my "interested party but not all that proficient in OpenAPI" hat on, I generally like allowing $ref for any coherent object, but not for splicing objects.
@BenjamenMeyer you asked about the history of only allowing $ref where a schema is allowed.  In draft-04, JSON Reference was its own specification, and JSON Schema technically wasn't aware of it at all.  So there was no notion of being able to restrict its usage.
The problem with this is that if you can use $ref in other places, it gets much harder to reason about schema objects in code.  You can't, for instance, figure out the property set that is relevant to additionalProperties without following a $ref if the whole value of properties is a $ref.  And doing that doesn't give you much over $ref-ing a schema that is just a properties keyword anyway.
If you go further and say that you can do something like {"properties": {"allOf": [{"$ref": "..."}, {"$ref": "..."}]}}, in addition to being confusing (although not impossible) to distinguish from a property named "allOf", you get into schema merging and splicing.
That is an incredibly complex topic spread across numerous issues across at least two repositories with well over 500 comments in total.  If you really want to know I'll point you to them, but I recommend against it.  The TL;DR is "it doesn't solve as many problems as you think, and it introduces new and extremely difficult problems as well".
In place of schema merging/splicing, we are pursuing json-schema-org/json-schema-spec#556.  It may not be obvious how those relate, but again, the backstory is extremely involved.

@handrews thanks for the insight.
I can certainly understand the issue with the properties, and appreciate the concern of complexity.

@handrews @MikeRalphson but what about combining objects other than schemas, since they are not schemas can't we just do something like merge ? For example, in order to extend an operation with a new response couldn't we do something like
  get:
    $merge
      - $ref: openApi-registry.com/foo#components/operation/greatOperation
      - responses:
          418:
            ...

Which would just do a deep copy of both json instances... Jackson implemented this here https://github.com/FasterXML/jackson-databind/issues/1399

$merge is deeply problematic.  There are well over 500 comments on this spread across four or five issues (and I am not exaggerating- one issue alone has over 230 comments).  I don't want to get into it, but just no.

Just to point out that YAML has anchors and you can work around this issue today. Example

Repeated nodes (objects) are first identified by an anchor (marked with the ampersand - “&”), and are then aliased (referenced with an asterisk - “*”) thereafter.

Now I know it's a different story for JSON, but most examples in this thread were in YAML. Hopefully this helps.

@fenollp $ref works just fine as a JSON replacement for YAML anchors, as far as I know.  It's just a question of whether OAS wants to allow a $ref here, and maybe whether there's some way to apply specific combination semantics along the lines of allOf.
The reason allOf (and the draft-08 unevaluatedProperties keyword) work and $merge does not is that the former keywords are defined in terms of JSON Schema semantics, so they are consistent with the overall processing model.  $merge is simply syntactic splicing, so the semantics of the input and output are not predictably related.  In some ways that's not much of a practical concern, but it turns out there are also several situations where syntactic splicing does not help (involving oneOf, anyOf, and if, all of which require dynamic evaluation with an instance to fully determine their effects- since $merge is static, it cannot work well with those keywords).


Windows terminal icon doesn't show properly

Not sure what happened. Used to work in previous versions.
It's supposed to look like this:

Indeed, thanks for the feedback, this is fixed in last version :-)


Support ring-bond stereo flags in CXSMILES

This adds c:, t:, and ctu: to the CXSMILES readers and writers. These only apply to ring bonds.
It also:

updates the documentation to include the newly supported CXSMILES features and to document where stereo information comes from.
Fixes #5585

This had a bad interaction with #5576 which is causing the CI builds to fail. I'm going to revert this, fix the problem, and then do a separate PR.


Feature/2729 ng13

Changes proposed in this Pull Request:

Go Angular 13

Similar to how we feed the showcase in the angular-components repo, I've added the npm-watch dependency and some additional tsconfig profiles to the local demo.
From the example folder:
yarn start:lib uses the local version of the auth-workflow.
yarn start:npm uses the published auth-workflow.

To Test:

yarn start:example

do I need to do something with lib? I ran yarn && yarn start:example

ignore my comment above. I ran again and it's ok now.

everything NG13 looks good. I was wondering about the change password screen in the example. It seems to have more height than other screen for some reason.

and the create account error state helper text for phone number seems off.

The change password page might look a little off due to the adjusted default padding of the inputs; we can updated the size of the Change Password dialog as part of this PR.
Also the "Code is Required" looks like either a wrong translation, or the wrong text being used.


Add parameters for PauliString and GlobalPhase

Allows parameters for coefficient of PauliString and GlobalPhase:

Fix up the types.
Only cast to complex in initializer if it's numeric.
Add handlers for parameter resolution.
Raise errors in a couple functions that do non-basic math on coefficient (most functions just multiply, which should be fine).
Return False from has_unitary. (Side note, should we just add that check to the protocol method itself--we repeat it everywhere?)
Add a block for circuit_diagram_info when the coefficient is parameterized.
Add tests, update pydocs.

Also tests and fixes #4508 @tanujkhattar

@daxfohl Great timing! I added a comment / complaint in https://github.com/quantumlib/Cirq/pull/5085 today that GlobalPhaseGate don't support symbols. Looks like they will soon. :))

(Note that contrary to what I said the linked issue, decompose doesn't work when parameterized anyway since it's not unitary, so we actually didn't need to change GlobalPhaseGate here. But I'd already done it before I noticed it was unnecessary, so I figured I may as well leave the change in place since it seems non-invasive and probably useful.)

Fixed diagonalgate while I was here.

@tanujkhattar do you mind taking this one?

Automerge cancelled: A required status check is not present.
Missing statuses: ['Misc check', 'Notebook formatting', 'Pytest MacOS (3.8)', 'Pytest MacOS (3.9)', 'Pytest Ubuntu (3.7)', 'Pytest Ubuntu (3.8)', 'Pytest Ubuntu (3.9)', 'Pytest Windows (3.7)', 'Pytest Windows (3.8)', 'Pytest Windows (3.9)', 'Type check', 'Typescript lint check', 'Typescript tests', 'Typescript tests coverage']

@tanujkhattar Can you kick cirqbot again?


Reduce duplicated code involved in running a query

In particular, this makes there be only one copy of the code that processes the input reports for an IPA query.

This is scaled back a bit from what I had originally tried to do. I tried to make the query processing generic over the return type of the query, i.e., a query would return Vec<O: Serializable> instead of Box<dyn ProtocolResult>. But I ran into some issues doing that and in the interest of getting what we need now done, removed those changes.


Debugger Tool appears below while there isn't any opened tab

VSCode Version: 1.26.1
OS Version: Mac OS High Sierra

Steps to Reproduce:

Run any node project
Make debugger tool downside of the line.
While debugging, close all tabs

This is as designed, the toolbar does not move automatically. You can drag it back up if you do not like it there.
Closing as designed as we have no plans to change this in the immediate future


Is it possible to do lazy loading of page components in router

Found an issue or bug with electron-vue? Tell me all about it!
Questions regarding how to use electron or vue are likely to be closed as they are not direct issues with this boilerplate. Please seek solutions from official documentation or their respective communities.
Describe the issue / bug.
#
How can I reproduce this problem?
#
If visual, provide a screenshot.
#
Tell me about your development environment.

Node version:
NPM version:
vue-cli version: (if necessary)
Operating System:

If you are looking to suggest an enhancement or feature, then feel free to remove everything above.

{ path: '/about', component: () => import(/* webpackChunkName: "about" */ './pages/About.vue') },


Import masks for genes and chromosomes

I figured we can activate all three components with flags. then we can do pdk genome -genes -chromosomes to add these two to the existing index.


Fix attachments list in edit comment

#11141 broke the appearance of dropzone attachments when editting
comments causing poorly updating lists.
This PR fixes this.
Fix #12583
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

could be backported to 1.12

Codecov Report

Merging #13036 into master will decrease coverage by 0.00%.
The diff coverage is 90.90%.

@@            Coverage Diff             @@
##           master   #13036      +/-   ##
==========================================
- Coverage   42.62%   42.61%   -0.01%
==========================================
  Files         672      672
  Lines       73785    73795      +10
==========================================
- Hits        31448    31447       -1
- Misses      37247    37256       +9
- Partials     5090     5092       +2

Impacted Files
Coverage Δ

modules/upload/upload.go
78.94% <90.00%> (+2.35%)
:arrow_up:

routers/repo/issue.go
36.86% <100.00%> (ø)

modules/indexer/stats/db.go
52.17% <0.00%> (-17.40%)
:arrow_down:

modules/log/event.go
56.60% <0.00%> (-0.95%)
:arrow_down:

models/repo_list.go
78.57% <0.00%> (-0.90%)
:arrow_down:

models/error.go
34.34% <0.00%> (-0.51%)
:arrow_down:

modules/util/timer.go
100.00% <0.00%> (+14.28%)
:arrow_up:

Continue to review full report at Codecov.

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

Unfortunately I don't think this is a fix for #12573 but rather is a fix for #12583.
I'm still struggling to completely replicate #12573

Codecov Report

Merging #13036 into master will increase coverage by 0.00%.
The diff coverage is 90.90%.

@@           Coverage Diff           @@
##           master   #13036   +/-   ##
=======================================
  Coverage   42.61%   42.62%
=======================================
  Files         673      673
  Lines       73858    73868   +10
=======================================
+ Hits        31477    31484    +7
- Misses      37271    37274    +3
  Partials     5110     5110

Impacted Files
Coverage Δ

modules/upload/upload.go
78.94% <90.00%> (+2.35%)
:arrow_up:

routers/repo/issue.go
36.86% <100.00%> (ø)

modules/log/event.go
59.90% <0.00%> (-0.95%)
:arrow_down:

services/pull/pull.go
40.78% <0.00%> (-0.50%)
:arrow_down:

modules/indexer/stats/db.go
69.56% <0.00%> (+8.69%)
:arrow_up:

Continue to review full report at Codecov.

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

It makes sittuation better!
but now I get this relicts after editing (no page reload):

:point_up: edit add second image
after a page reload all looks fine

@6543 That's odd... are you sure your javascript is up to date?

I'll retest with a different browser ... lets look how this playes

Yes

What does yes mean?

I have tested the this patch on a fresh browser so there should be no old java in the cache ...

Check the DOM and tell me where those nodes are and what they are contained in.

I've managed to reproduce ... give me a few mins.

Now there's one other weird thing this PR doesn't sort which handling what happens when you remove an attachment from an empty comment...

OK @6543 ready again.

wow - thanks!!

Unfortunately backporting this is much more involved than it would at first seem. It might take a while to do.


 when calling "timm.create_model('beit_base_patch16_224', pretrained=True)"

Describe the bug
For several models, including 'beit_base_patch16_224', an exception is thrown when trying to load it with pretrained weights.
The problem occurs on all machines and python versions I tried it on, including Google Colab.
To Reproduce
import timm
model = timm.create_model('beit_base_patch16_224', pretrained=True)
Gives the following stack trace
UnpicklingError                           Traceback (most recent call last)
 in ()
----> 1 model = timm.create_model('beit_base_patch16_224', pretrained=True)
7 frames
/usr/local/lib/python3.7/dist-packages/timm/models/factory.py in create_model(model_name, pretrained, checkpoint_path, scriptable, exportable, no_jit, **kwargs)
72
73     with set_layer_config(scriptable=scriptable, exportable=exportable, no_jit=no_jit):
---> 74         model = create_fn(pretrained=pretrained, **kwargs)
75
76     if checkpoint_path:
/usr/local/lib/python3.7/dist-packages/timm/models/beit.py in beit_base_patch16_224(pretrained, **kwargs)
359         patch_size=16, embed_dim=768, depth=12, num_heads=12, mlp_ratio=4,
360         use_abs_pos_emb=False, use_rel_pos_bias=True, init_values=0.1, **kwargs)
--> 361     model = _create_beit('beit_base_patch16_224', pretrained=pretrained, **model_kwargs)
362     return model
363
/usr/local/lib/python3.7/dist-packages/timm/models/beit.py in _create_beit(variant, pretrained, default_cfg, **kwargs)
350         # FIXME an updated filter fn needed to interpolate rel pos emb if fine tuning to diff model sizes
351         pretrained_filter_fn=checkpoint_filter_fn,
--> 352         **kwargs)
353     return model
354
/usr/local/lib/python3.7/dist-packages/timm/models/helpers.py in build_model_with_cfg(model_cls, variant, pretrained, default_cfg, model_cfg, feature_cfg, pretrained_strict, pretrained_filter_fn, pretrained_custom_load, kwargs_filter, **kwargs)
468                 in_chans=kwargs.get('in_chans', 3),
469                 filter_fn=pretrained_filter_fn,
--> 470                 strict=pretrained_strict)
471
472     # Wrap the model in a feature extraction module if enabled
/usr/local/lib/python3.7/dist-packages/timm/models/helpers.py in load_pretrained(model, default_cfg, num_classes, in_chans, filter_fn, strict, progress)
187     if pretrained_url:
188         _logger.info(f'Loading pretrained weights from url ({pretrained_url})')
--> 189         state_dict = load_state_dict_from_url(pretrained_url, progress=progress, map_location='cpu')
190     elif hf_hub_id and has_hf_hub(necessary=True):
191         _logger.info(f'Loading pretrained weights from Hugging Face hub ({hf_hub_id})')
/usr/local/lib/python3.7/dist-packages/torch/hub.py in load_state_dict_from_url(url, model_dir, map_location, progress, check_hash, file_name)
593     if _is_legacy_zip_format(cached_file):
594         return _legacy_zip_load(cached_file, model_dir, map_location)
--> 595     return torch.load(cached_file, map_location=map_location)
/usr/local/lib/python3.7/dist-packages/torch/serialization.py in load(f, map_location, pickle_module, **pickle_load_args)
711                     return torch.jit.load(opened_file)
712                 return _load(opened_zipfile, map_location, pickle_module, **pickle_load_args)
--> 713         return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
714
715
/usr/local/lib/python3.7/dist-packages/torch/serialization.py in _legacy_load(f, map_location, pickle_module, **pickle_load_args)
918             "functionality.")
919
--> 920     magic_number = pickle_module.load(f, **pickle_load_args)
921     if magic_number != MAGIC_NUMBER:
922         raise RuntimeError("Invalid magic number; corrupt file?")
UnpicklingError: invalid load key, '='.
Finally
Kind regards!

@IndoorAdventurer what version of timm? beit checkpoints changed location, the master is updated but I haven't backported to pypi 0.5.x release... I did do a 0.6.2.dev0 release that can be installed with pip install --pre or timm==0.6.2.dev0

Ah, I was using the default 0.5.4 version. I just tried 0.6.2 on Google Colab and it works! :-D (I did try 0.6.2 locally and got the same error, so I probably forgot to delete a wrong .pth file)
Thank you so much for the quick respons!
Kind regards
Vincent


add doc_auto_cfg to relevant sdk crates

Problem
The new SDK crates put a bunch of code behind feature gates, which means those items won't be visible on docs.rs. This wasn't a big issue with solana_sdk and solana_program because those crates enable almost all their features by default.
Summary of Changes
For each crate in sdk/ where this is an issue, add
all-features = true
rustdoc-args = ["--cfg=docsrs"]

to [package.metadata.docs.rs]
and add #![cfg_attr(docsrs, feature(doc_auto_cfg))] to each module that contains feature-gated public items.
This makes docs.rs show these items with a note that they require certain features (or targets etc). This solution is fairly common: tokio is a prominent crate that does this.
To emulate what docs.rs generates, you can cd to the individual crate directory and run RUSTDOCFLAGS="--cfg docsrs" cargo +nightly doc --all-features --no-deps
I published a toy example crate to demonstrate that this works on docs.rs: https://docs.rs/doc-feature-examples/latest/doc_feature_examples/

if don't mind, we can wait @joncinque or @febo to have a chance to look

@joncinque could you merge please? Looks like automerge is still disabled


Project Status

Is this project dead?

Hello, thanks for your message, it is not, after a short break we are preparing a new setup.
We are now delivering a few projects with Condensation which help us to prepare the javascript version to present demos/tutorials for web applications. We are also investigating new business opportunities.
We will communicate soon about the status of the project.

Thanks for reply. I am happy to know that this project is not dead. Developers like me are looking for a better database to replace decades old RDMS.
I am unable to find information about query language in documentation. I suggest a Datalog like query language(https://terminusdb.com/docs/terminushub/reference/woql or https://docs.flur.ee/guides/1.0.0/analytical-queries/inner-joins-in-fluree). I also suggest a discord server for community building.

Thank you for the suggestions.
Condensation does not currently have a query language in the conventional sense, and this is not even a goal. Condensation offers the following structures:

Synchronized documents: This works great for generic data which should to be available on multiple devices, and synchronized across them. Examples: messenger (Twelve), photo album, or any business-specific app where people are working on the same data. A document is kept in-memory, and can be traversed using the tools your programming language offers. There is no need to learn a query language. This works great for what I call "small data" (< 10 GB, small enough to keep in memory). Most data people are dealing with is < 100 MB.

Timeline data: Timeline data is ubiquitous - any sensors measuring something (IoT) produces timeline data, your email feed or any chat history is timeline data. With Condensation, such data is stored as a blockchain-like structure, and you can efficiently query slices (i.e., all data from time X to time Y). Once you have such a slice, you again process it with the tools provided by your programming language. This works equally well for "small data" and "big data", because you always work with a manageable slice.

Index: This is basically a searchable index, mapping keywords/ids to documents or objects, e.g. the list of all employees of a large corporation, or an index of videos by title, or pictures by location. This is not really a query language either, or just a very simple one. Since we are operating in a distributed system, the index is not always consistent with the data - it is eventually consistent.

The concept of a query language is tightly linked with the structure of relational databases (whether SQL or NoSQL). Condensation is more like a network of documents linked with each other, and you are navigating through that network.

Condensation is more like a network of documents linked with each other, and you are navigating through that network.

Condensation is like a graph database and all graph databases have a query language. It would be difficult to build apps without a proper query language.

No, Condensation is not a graph database. Just like an animal with pointy ears isn't necessarily a cat.
Query languages are of interest if the computation is carried out on another computer. With Condensation, data is kept locally anyway. Your app can just read and process the data. You don't need a query language. It's much simpler than that. Once you've opened the data, you navigate through a tree (a bit like a filesystem), and gather the information you need.

How is it possible to store whole database (multiple gbs) on user's device specially on mobile phones.

In case you are looking for a traditional centralized database with a query language, then Condensation isn't for you, I'm afraid. There are plenty of centralized cloud solutions out there. We have no intention to compete in that market.
Regarding user data:
When using Condensation, you design your system in such a way that the users' data can reside on the users mobile phone. The approach we take is very different from a centralized cloud solution.
Since users only keep their own data on the device, the device memory is usually big enough. Take a typical messenger app, such as WhatsApp: the users' data is stored on the device, sometimes taking several GB (with photos and media). Many other apps require far less data.
There are projects where the device memory is not enough, and there are a few simple solutions for that:

In some situations, old data can be archived or deleted. Since Condensation allows for easy data synchronization, it is fairly straightforward to push such data to a server. However, you'll have to provide enough server space (# users * many GB).

When talking about a large library, say a video platform, users would query an index server (see above) with a keyword to find their video, and download that video on demand. Condensation can do such things very efficiently.

Index server is like a traditional centralized database without a query language right? I am very much interested in a new database, just trying to understand how Condensation works.

We are talking about a distributed system. An index server is comparable to an expert in our society. If you have a question regarding a specific topic, you contact this expert.
You may have an index server knowing all employees by name, for example. If you are an employee of the company, you'd register yourself with that index server, and this index server adds you to the list. If you're looking for another employee, you can send a query to the index server.
An index server infrastructure actually consists of two parts:

The index master, who creates and maintains the index. Usually a single machine.
Index query servers who reply to queries. These servers receive regular updates from the index master. Depending on the size of your system, you may have dozens of such index servers.

For performance reasons, an index query server typically keeps the whole index in memory (or on high speed disks). Queries are often made using HTTP/REST requests.
Index masters/query servers contain some application-specific code. The index master may have to identify you as an employee, for example. The index master may also aggregate or compute data. An index query server may limit the number of results to prevent misuse.
For maximum scalability, every index master/server manages a single index only. For small systems with little load, they may all run on the same physical/virtual server, however.
For maximum security, the index master runs in a secure location outside of the datacenter, and reads messages asynchronously. Index query servers run inside the datacenter and are publicly accessible, of course.
Unlike with classical databases, indices are eventually consistent only, and sometimes not consistent at all by design. E.g., you may be able to participate in the system without registering with the index of employees. These things are application-specific.
As you can see, with Condensation you are building a (distributed) data system with multiple "actors" (as we call them) that communicate with each other. For small systems, we usually have all actors running on the same virtual machine in some datacenter. For larger systems, you can easily scale up.

Thanks for the detailed explanation.

Thank you for your questions Ansar, they are very helpful to prepare the next step for Condensation which is to create a more comprehensive and step-by-step introduction - for that we are preparing further materials which will be published on a dedicated website this autumn. If you are interested in contributing and doing a deep dive into the core please directly contact Thomas by email.

Yes I am interested. Could you please share Thomas's email address?

Sure, you can find his details here (https://viereck.ch/thomas/)

I am about to start a new project and I would to love to use Condensation. Is it somehow possible to play with Javascript version?

every index master/server manages a single index only.

If we have separate index servers for customers, products and orders then how can we query all customers who bought a particular product in last months.

Answer 1
In a typical SQL database, you'd have three tables: customers, products, and orders. With Condensation, you would think about this differently:

The customer is the actor who places the order. Technically, you don't need a customer "table" at all. The customer data belongs to the customer, and is managed by themself.
Products are a public list. Every product could be a separate object/document. Whenever you modify a product, you get a new hash. Hence, products are automatically versioned.
Orders are timeline data. You're mostly interested in the most recent orders (perhaps the last 2 years or so), and older data is archived. Every order is signed by a customer. It contains a list of references to products, a delivery address and other relevant information.

With this structure, your query would be executed as follows:

Get a slice of the last few months of orders.
Loop through these orders.
If the order contains the product we are looking for, add the customer (actor hash) to the result set.

Answer 2
Let's assume you have a similar problem, for which you really have three "tables" with three indices.
You would create an analytics actor. This actor would load all three indices directly (not query the index servers, but get the indices from the respective index masters), and process that data. Implementing this is not as elegant as writing a SQL statement, but it's just a couple of loops, nothing complicated.
If you do such queries a lot, you'd build a new index with exactly this data, organized in an efficient way, and set up an index server to respond to queries.
For small systems, you could just create a single index master + index server, create all indices there, and keep everything in memory.

Answer 1 looks viable but the question is where all customers/products/orders data will be stored and where the computation will be performed If we are building an eCommerce platform for a big retailer with thousands of customers/products/orders, surely it can't be done on user device. We also need customer/product names and other properties and not just hashes.
I am asking these question as we need to show developers that CondensationDB is better than other available solutions.

Every actor stores all data they need. More precisely:

Every user (actor) stores their profile and cart locally¹.
The product manager (actor) stores the list of all products.
The eCommerce platform (actor) stores all orders. Since orders reference products, it also stores a copy² of these products.

An order contains/references everything necessary to fully process the order. It would contain a shipping address and a payment method, for instance.
Some eCommerce platforms provide the possibility of storing more than one delivery address, and then pick one when ordering. The list of delivery addresses are user-private data. The order contains the chosen delivery address.
When submitting an order, the user actor sends a message with the order to the eCommerce actor. The eCommerce actor verifies the order and replies with a appropriate message.
Every product is an object (or small tree) containing all information about the product (id, name, description, image references³, ...).
When searching for products, the user queries the product index, and then retrieves the found products. A user doesn't generally store products locally, except perhaps for products in his cart / wishlist, or recently visited products.
Footnotes:

If you provide a login server, users can log in using a username and password, and an encrypted copy of the user data will be stored on your Condensation store. A login server sort of reverts Condensation back to a cloud solution (from the user's perspective). You still get all the advantages of Condensation. Using a login server is optional, and even if you provide one, users can still opt out and manage their data on their own, without using the login server.
The product actor and the eCommerce actor may use the same Condensation store, so that the data is not physically duplicated.
Images, technical datasheets, ... are stored as Condensation objects. No separate storage for that is necessary.

It means CondensationDb design is very flexible and it can be used for different use cases.
Messages are like bidirectional streaming RPCs via web sockets right?

Yes, you can look at messages as RPCs.
Protocols:

Most of the time, we use HTTP(S) to connect to Condensation stores. We have a well-defined protocol for that, and every implementation supports this.
Inside our own systems, we sometimes use a simple proprietary protocol over TCP. This is slightly more efficient.
For IoT sensors submitting low-bandwidth measurements, we use a simple UDP protocol. We are about to have a working implementation, and I'll publish/document this within the next few months.
Web sockets: we don't currently have any web socket implementation, but this would be feasible.

Note three things regarding messages:

Messages are asynchronous. You are posting a message, and the corresponding actor is processing this message at some time in the future ("eventually"). For actors running all the time, messages are delivered immediately (i.e., within network/processing delay).
There is no intrinsic order. If you send messages A and B, the recipient may process them in any order.
Messages can be updated. You can send A1, then update it to A2. The recipient may receive A1 and A2 (in any order), or only A2.

We are about to have a working implementation, and I'll publish/document this within the next few months.

I can work on documentation site If you need helping hand.

I will close this issue, Ansar to continue the conversation I invite you to use the discussion section in GitHub HERE


[zh-cn] fixed /config-api/kubelet-config.v1beta1.md

fixed links and typo.
Preview: https://deploy-preview-35091--kubernetes-io-main-staging.netlify.app/zh-cn/docs/reference/config-api/kubelet-config.v1beta1/

We'd better resolve this from the English version and then sync the translated version.

We'd better resolve this from the English version and then sync the translated version.

Find @Sea-n has fixed those link in the en version at #34155.

/lgtm
/approve