Parse STM32CubeMX database directly

Instead of using hacky export scripts, parse the STM32CubeMX database directly :grin:
Example: https://github.com/LibrePCB/stm32-db/blob/parse-db/data/STM32L071KBTx.json Nice, isn't it? :slightly_smiling_face:
@ubruhin the JSON files also contain information about the pin signals. That could be used in the future in case we add support for pin signals in LibrePCB!
CC @ouabache

Can you get the alt pin functions? I could never get those using the hack
On Sun, Feb 23, 2020, 4:15 PM Danilo Bargen<EMAIL_ADDRESS>wrote:

Instead of using hacky export scripts, parse the STM32CubeMX database
directly 😁
@ubruhin https://github.com/ubruhin the JSON files also contain
information about the pin signals. That could be used in the future in case
we add support for pin signals in LibrePCB!

Reply to this email directly, view it on GitHub
https://github.com/LibrePCB/stm32-db/pull/4?email_source=notifications&email_token=AAKX3XDT2T5T2ZQ5F6NEOZDREMGRRA5CNFSM4KZ7GNMKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IPTFI3Q,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKX3XHPEZBXKQWGPT6FXRDREMGRRANCNFSM4KZ7GNMA
.

Can you get the alt pin functions? I could never get those using the hack

I could (with the JAR bytecode patching hack), but we don't need them for LibrePCB. The pin numbers and signals are sufficient.


Could not find com.raizlabs.android:DBFlow-Compiler:2.1.0

Although the changelog said that 2.1.0 version is available on jCenter, when I add it to my project, the Gradle sync return this error:
Error:Could not find com.raizlabs.android:DBFlow-Compiler:2.1.0.
Searched in the following locations:
    https://jcenter.bintray.com/com/raizlabs/android/DBFlow-Compiler/2.1.0/DBFlow-Compiler-2.1.0.pom
    https://jcenter.bintray.com/com/raizlabs/android/DBFlow-Compiler/2.1.0/DBFlow-Compiler-2.1.0.jar
    https://repo1.maven.org/maven2/com/raizlabs/android/DBFlow-Compiler/2.1.0/DBFlow-Compiler-2.1.0.pom
    https://repo1.maven.org/maven2/com/raizlabs/android/DBFlow-Compiler/2.1.0/DBFlow-Compiler-2.1.0.jar
    https://raw.github.com/Raizlabs/maven-releases/master/releases/com/raizlabs/android/DBFlow-Compiler/2.1.0/DBFlow-Compiler-2.1.0.pom
    https://raw.github.com/Raizlabs/maven-releases/master/releases/com/raizlabs/android/DBFlow-Compiler/2.1.0/DBFlow-Compiler-2.1.0.jar
    ...

You can see that I even added the custom maven repo, but still no success.

For now you can add repo:
maven { url 'https://dl.bintray.com/raizlabs/Libraries' }

That won't work either because they didn't push it to https://github.com/Raizlabs/maven-releases/tree/master/releases/com/raizlabs/android/DBFlow either.
My guess is that they thought they pushed it to maven, but didn't. Actually pushing to maven is not that easy ;-). They probably forgot that they have to manually release it in https://oss.sonatype.org/. But just guessing.

@pboos I have tried adding the custom maven repo above and it's working now.

@rey5137 I can't get it working...
Could you explain which changes did you make?

Just get it working:

buildscript {
repositories {
jcenter()
mavenCentral()
}
dependencies {
classpath 'com.android.tools.build:gradle:1.2.3'
classpath 'com.neenbedankt.gradle.plugins:android-apt:1.4'
}
}
allprojects {
repositories {
jcenter()
maven { url 'https://dl.bintray.com/raizlabs/Libraries' }
}
}

Thanks!

hey its finally up on jCenter(). Just took some time. Ensure you reference jCenter() in your libraries and not mavenCentral()


DBFacade and getCheeps implementation

I have added an initial implementation of the DBFacade class that queries all Cheeps from the DB. The CheeoService GetCheeps is refactored to collect these cheeps and return a list. I have also moved the CheeoViewModel to a seperate record class.

This looks very nice and clean.


Why using menuOpen and not ContextMenu.IsShow in the Editor?

Only a ContextMenu can be open at a time and so the ContextMenu.IsShow property is static. @tznind I don't know if there is some specific reason for you don't use it.

Not sure I follow, which part of the codebase is this?

Not sure I follow, which part of the codebase is this?

Here:
https://github.com/gui-cs/TerminalGuiDesigner/blob/5dd62b5f404814b3eb5ba3a55ecfac4f38880c32/src/UI/Editor.cs#L28
Here instead of this:
https://github.com/gui-cs/TerminalGuiDesigner/blob/5dd62b5f404814b3eb5ba3a55ecfac4f38880c32/src/UI/Editor.cs#L281
you can use :
if (keyEvent.Key == this.keyMap.ShowContextMenu && !ContextMenu.IsShow)

Not needed, so closing this.


Add a code of conduct

We need a code of conduct as we have an issue with users such @dgenr8 making repeated derogatory comments.

We have one already
I recommend closure of this pull request.
@cointracker: If you have a complaint to make the email address to contact is in the link above.

Thanks for the work @cointracker. We appreciate it, closing this in favour of the one thats been drawn up and placed on the main site
Ahmed


Refactor secrets and auto-generate password + ssh_key

Refactor secrets values to implement #14 and #16. Since these changes overlap, I combined them into one PR.
BREAKING CHANGE:
Move secrets.st2.{username,password,ssh_key,datastore_crypto_key} values into st2.* (implements #14).
Plus, auto-generate password and ssh_key secrets (implements #16), so that the stackstorm-ha installation is a bit more secure by default. On upgrade, use lookup to pull the current secrets from k8s APIs.
Resolves: #14
Resolves: #16
Closes: #62

rebased on master

Thanks! Looks great at a high level.
Based on the CI run (https://app.circleci.com/pipelines/github/StackStorm/stackstorm-ha/1251/workflows/dbc5fbc0-7557-4eb1-987e-a6d480366c3a/jobs/4191), looks like the st2 password is not showed up in the NOTES when doing the initial Helm chart install:
2. Login with the following credentials:
username: st2admin
password:

This is a high-profile feature that'll affect everyone and so a few more cycles of testing won't hurt, especially around the corner cases we mentioned.

Yeah. That's very sad - the lookup works on upgrade but not install.
Also, lookup always returns nil when using helm template to debug because helm is not supposed to contact the cluster during template.
I'll do a bit more research to see if there's a good way to grab the auto-generated value in multiple places. If you come across anything please let me know.

Helm templates all of the files at once, before applying the resources, so we cannot lookup in NOTES what was generated in another file. For that matter, during the same helm run, we can't lookup anything generated in one template file from another template file.
Also, NOTES is stored with the other release information. By default helm 3 uses secret storage for that, but also allows using configmap and postgresql storage backends. It makes sense to minimize the number of places that expose the plain secrets, without regard to how the cluster is [mis-]configured. So, I think using kubectl to retrieve the password instead of embedding it directly in the NOTES marginally improves security for the default st2 ha installation.
So, I changed the NOTES to explain how to retrieve the password with kubectl. Wdyt?

I agree that it's a step forward to not just print the password in the NOTES.  Providing the kubectl command to retrieve it is far safer and nearly as simple from a user experience perspective.
Printing passwords at every upgrade when they weren't requested is a bad thing.  They could get caught in log files and terminal output all over the place, and this is the admin password!
Great idea for a PR, and I think the implementation looks nice!
Any reason not to also implement the "auto-generate if not defined" behavior for the crypto key?


BUG: Allow non-zero GDF rows

Resolves #80.

@KavlinClein, cleaned up the PR. Same changes as old PR but I'm overriding or merge.


[types] use multisig authentication keys

Force the input of AccountAddress:from_public_key and AuthenticationKey::from_public_key to be a Ed25519PublicKey
Interpret authentication keys created from a single Ed25519PublicKey as a 1-of-1 multisig key
Fake the existence of the threshold part of a transaction by assuming it's always 1 in the transaction prologue logic. This lets us change the auth key format here, but defer changing  the tx format (which will be a more invasive change) to a later PR.

Motivation
Conversion to multisig.
Have you read the Contributing Guidelines on pull requests?
Y
Test Plan
All tests that check auth keys continue to pass, should be pure refactoring

:umbrella: The latest upstream changes (presumably cd8147897f8d9e658b2c7cead6a3dc4ee6500cfa) made this pull request unmergeable. Please resolve the merge conflicts.


Update migration controller manifests.

Description

Update migration controller manifests based on PR https://github.com/projectcalico/kube-controllers/pull/401
Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit f23ee8b1150b510dff86f80ddcc28bfdee8cfe54
https://deploy-preview-2830--calico.netlify.com


tabline not showing

sorry, my fall. my opened windows was opened in buffers, not i tabs.... when i opened in tab with "tab split" all works good. but, by default all open in buffers, i think would better to change it


Fix pubspec for analyzer_plugin

Ensure packages are resolved before analyzing

CC @MichaelRFairhurst
...it couldn't be this easy, could it?

This should be everything you need, yes!


Too Many Requests (Mempool)

/labelbase/import/
429 Client Error: Too Many Requests for url: https://mempool.space/api/tx/
Use BGT/queue

We use electrum now.


perf: RandomStrategy.PickOutbound reuse statusMap

reuse statusMap, should gain some performance boost.

Hi! Thanks for the pull request.
I was unable to understand what operation you are attempting to reduce:
Is that s.observatory.GetObservation(s.ctx) or common.Must2(s.observatory.(features.TaggedFeatures).GetFeaturesByTag(s.settings.ObserverTag)).(extension.Observatory).GetObservation(s.ctx) ? they will be executed in with or without this merge request. Assume that is the case, if they are not executed every time, then stall result should be eliminated by maybe have a cache life time setting?
Are you attempting to reduce map allocation? That was not the most expensive operation here.
Please let me know what kind of operation you are intent to reduce, and we can discuss a plan.

The intent was to merely reduce map allocation, not some great boost but better than nothing...
On the other hand, should any optimization be added to GetObservation (via cache or other means), I believe that should be implemented on the observatory side.

I have checked your code, and I was not convinced that reducing a map allocation would make sense when it comes increased code complexity, considering:

The shared map is not emptied before each use. Since outbound can be removed and subsequently untracked by the observatory, stalled value must be removed from the cached map structure.
The shard map is must be guarded with synchronization primitives like memory barrier and even locks, as it could be accessed from more than one threads. This operation would nullify whatever performance gain by avoiding a map allocation.

Oh my... thanks for the suggestions!


Add influx 2.X exporter

The agent currently only supports influx 1.X, thus integrating it with influx 2.X is only doable with workarounds.
Addtionally, influx 1.X is not supported anymore as of 2022.

Hi,
yes, currently there is no metric exporter existing for InfluxDB 2. As soon as we've migrated to OTel, you could use the OTLP exporter to export metrics to an OTel Collector which can push the metrics into InlfuxDB 2.X


re-order CloudFront behaviors to ensure image optimisation takes precedence over static images

This update re-orders the CloudFront cache behaviors to ensure that the image optimisation function takes precedence - please see before and after screenshots from AWS console.

closes #31

Thanks for the PR @adatoo.
Are you able to explain a little bit more as to why this resolves the issue?
Also give me a little bit of time to do some additional testing on this for multi-zone, etc.

This is working for both single zone and multi-zone deployments.
Thanks for fixing this issue @adatoo

Thanks for accepting the PR.
Additional context as to what has changed as requested...
The  PR comments above show 2 tables from the Behaviors tab from the AWS CloudFront Console. The items in the table represent the rulse set for resolution of paths in a request.
If you look at the before image, image optimisation is the 7th row (ID 6). Unfortunately it will never get triggerred because the 3rd row (ID 3) has a wildcard that is a superset.
The code changes move the image optimisation to top row taking precendence.
It would probably be sensible to spend some more time optimising the behaviors - suggest you look at something like the SST project to see their approach.


Bump bokeh minimum version to 3.1.0

Companion PR to https://github.com/dask/distributed/pull/8861 on the dask/dask side

thx


Add overflow menu item for autofill

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #2125   👈

This comment was auto-generated by Graphite.


feat(pixels): Added the ability to hover pixels

Checklist

[x] I ran npm test locally and it passed without errors.
[ ] I only edited the _data/pixels.json file.
[ ] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

Description
I added the ability to see the contributor by hovering a pixel

Related issues
See #215 and #226

Thank you for your contribution @boserup! I really appreciate it :) Since @athif23 had claimed this issue first in his original issue, I went ahead and merged his implementation in #284 but thank you so much for working on this!


use bitwise ops rather than B to check for numeric flags

This abuses the fact that bitwise ops change behavior based on the
internal type of a value. This avoids the memory cost of loading B, and
ends up being faster as well.
We first us an & to shorten the input, so we don't end up operating on a
long string.
"0" & 0 -> 0
"0" & "" -> ""
"0" & $string -> $character
0 ^ 0 -> 0 (false)
$character ^ $character -> "\x00" (true)
Previous attempts to use this technique didn't include the & step to shorten the value, and were thus slower than using B for long strings.
This is a revision of PR #1, including a fix for perl < 5.14, as well as documenting the purpose of the checks better.

Merged. Thanks! I'll re-release to cpan this weekend.


An unusual request for Scott Anderson

Attach the save file
Add the .sav file to a zip, and attach the .zip file to this issue.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hi Scott,
I contact you this way because I can't find another way to contact you. As you surely know has Tom of Railroad Online Extended recently decided to discontinue his work on it because of the lack of support from the RRO team. Since you with RailroadStudio now seem to have just about everthing figured out, including a great map for Aurora Falls (for all of it I want to congratulate you!), I wanted to ask you, if it might be possible for you to have a look at the RROX code, which is also on Github, and see if you can see a way if you or somebody could update RROX and bring it up to scratch. I don't know whether this would be alright with Tom, but I can't really see why he would object if somebody else picks up his work. There seems to be no copyright or something!
Thanks for your excellent work!

This is not something I have interest in taking on.


Feedback requested re: v1.1

On behalf of the spec editors, I'd like to solicit general feedback on the v1.1 release candidate to understand how things are going in the community.
We are currently in an awkward state, unable to finalize v1.1 due to the caveat described in the status section:

This version is expected to be finalized and released on January 31, 2019 (provided there are two compliant implementations by that date; if not the release will wait until such implementations exist to prove its viability).

It's inarguably a bad sign that we're now more than five months past this date without yet being aware of multiple compliant server and client implementations of the v1.1 RC. Now it's possible that we're simply out of the loop, and v1.1 has been fully implemented by several libraries that we (the editors) don't happen to be using. However, it's also possible that the new-to-1.1 profiles feature has proven too onerous, impractical, or undesirable to be implemented widely (and this is of course the precise reason that we added that caveat in the first place).
With that in mind, we're reaching out with a few questions to JSON:API implementors:

Have you attempted to implement any part of v1.1? If so, what part?
Which parts of v1.1 do you find useful?
Which parts of v1.1 do you not find useful?
Have any parts of v1.1 proven to be too onerous or impractical to implement?

For reference, the major deltas introduced in 1.1 are listed in the update history section of the home page and copied below:

New features include: profiles, "@-Members", and error object type links.
There are editorial clarifications around: query parameters (their parsing/serialization, and reserved parameter names), the appropriate status code for specific responses, and the presence of the included key even when its value is an empty array.
JSON:API switched to recommending camelCased names.

Please feel free to speak openly in comments below. We are trying to revitalize the spec and push forward on some much needed initiatives. However, we're also willing to re-examine and change some aspects of v1.1 first, because it has definitely become a blocker.
Thanks for any feedback you can provide.

Thanks for the call!

Have you attempted to implement any part of v1.1? If so, what part?

I've added full v1.1 support in https://github.com/lode/jsonapi (see https://github.com/json-api/json-api/pull/1377), which is a server implementation. Next to allowing any custom profile, I've also added an implementation of the Cursor Pagination profile.
Good to know, my library doesn't yet offer any parsing or assistance for handling the request. It is up to the user (of the library) to handle the request and direct the library. So any tricky things in handling query parameters or profile media type isn't something I bumped into. The library currently only handles the output, so for example profile links and content-types are handled.

Which parts of v1.1 do you find useful?

The type links are good to have. And I like the possibilities of profiles, although I think it would be good if there's a way for profiles to allow things that the spec doesn't. As the profiles anyway have to be announced & negociated, it allows for more experimentation.
Also, although minor maybe, I like the camelCase recommendation.

Which parts of v1.1 do you not find useful?

The @-members. For me it feels like a weird addition to the spec.

Have any parts of v1.1 proven to be too onerous or impractical to implement?

Again the @-members. See also the discussion https://github.com/json-api/json-api/issues/1367. Without them the spec is very clear in what is allowed where. There is a certain structure and semantics to it. The @-members skip all of that and being allowed everywhere is actually more hard to implement than being allowed in specific places.
I have implemented them, but as I don't use it, and the spec is very broad, I'm unsure if they work as expected or are useful.
Hope this helps.

from the www.crnk.io perspective we already follow the parameterization and camcelCase recommendations. The profile implementation we can take on our roadmap for version 3.1. So it should manifest in the coming 4-6 weeks. It has not yet been an overly interesting target as of yet. Nothing wrong with the specification, but I think the real value will only manifest when there are also concrete profile specifications in the various areas. I could imagine meta modelling, filtering, nested filtering, full-text search, facetted search, bulk operations/sideloading, maybe an optional slightly simplified response structure (directly inlined inclusions, no "attributes" and "relationship" wrappers to make it a bit more approachable/look-alike to regular APIs). In various areas we already have stuff not backed by any specification and would love to not having to do that anymore.
given that GraphQL gets plenty of love currently, some alignment with that might also be worthwhile.

The profiles feature was first proposed on April 15, 2018 before being finalized on September 18, 2018. We have waited six months(or ten months post finalization) for implementation feedback. This reflects a lot on the focus given to our community. However, I would humbly request the authors to go ahead with the v1.1 release(including the  profiles feature) without further delay.
The entire community is excited for v1.2 and have been waiting for the LocalID, Operations, Sideposting, etc features for more than a year. Any further delays in enhancing JSON:API spec would push people to alternatives thereby, further shrinking the community.

I just want to add to what @jugaadi said above... I run a Laravel JSON API package.
I love JSON API but have been worried about the stagnation. Profiles etc look great, but they don't really help me with any of the issues that get raised in my package. Features or issues that will be solved by operations are constantly requested. So really, I'm waiting for 1.2, not 1.1.
The community focused approach is really commendable, but I strongly feel it's time we move on to 1.2!

Thanks to everyone who replied with feedback. Kudos to @lode for implementing the cursor pagination profile in https://github.com/lode/jsonapi as well as some other aspects of 1.1. And thanks to @remmeier for moving crnk.io to the new recommendations as well as committing to some future support for profiles. Last but not least, thanks to @jugaadi and @lindyhopchris for encouraging us to move the spec forward as quickly as possible. I agree that the current pace is unacceptable.
Based on the relatively low amount of feedback here, and the anecdotal evidence I've heard firsthand, it's become clear that many implementors consider that profiles, as currently spec'd, are either too onerous to support fully and/or not worth the effort to support. Some aspects, such as member aliasing, don't appear to have any implementations yet, and so we're planning to remove them from the spec. @gabesullice has begun some simplification work in #1410.
Another thing that has become obvious from discussions about profiles, and even concrete proposals for profiles, is that we've done a poor job communicating the intended limitations of profiles. Profiles are introduced in this way:

JSON:API supports the use of “profiles” as a way to indicate additional semantics that apply to a JSON:API request/document, without altering the basic semantics described in this specification.

The second part of that phrase ("without altering the basic semantics described in this specification") is often missed. Perhaps a clearer way of saying this is that profiles must describe behavior that is completely conformant to the base spec. Profiles are intended to describe how the spec is used, but not extend the allowed usages. If profiles were allowed to introduce a top-level member in the document, say operations for instance, then the spec itself could never introduce that same member. Forward progress on the spec would effectively stop if profiles had this kind of unlimited power.
With that said, there is incredible pressure built up over years to allow for new capabilities to be added to the spec. I feel this strongly myself, having authored both the proposals for local identifiers and operations. Both of these proposals have been queued up for over a year as we have waited for profiles and v1.1 to be completed and proven with implementations.
In hindsight, I can now say that it was probably a mistake to introduce profiles in their current form in the order they have been introduced. We need to unlock forward progress without compromising the spec long term.
I've been meeting weekly with @gabesullice now to regain momentum. Our plans include:
A) Remove the release candidate status from v1.1.
B) Simplify the spec's requirements around profiles.
C) Consider extending the scope of v1.1 to include support for schemas and extensions such as bulk, identifiers, and operations.
Obviously point C sounds extensive and will need to be spelled out in more detail as we arrive at a proposal. However, we are considering including new capabilities in v1.1 because it seems that, otherwise, profiles will continue to be misunderstood and play a much larger role than originally intended. Furthermore, since we're going to require a new release candidate for v1.1, we have the opportunity to reconsider what's included.
Thanks for everyone's continued support. We'll try to move forward as quickly, and as publicly, as possible. Please stay tuned ...

Very much appreciate you diving back into moving this forward.@gdeb and  @gabesullice
Might it make sense to update the homepage and status page to reflect the update you posted above? (including, perhaps, linking to your update comment. Or, at the very least, removing the "expected to be finalized and released on January 31, 2019")

@gabrielgrant yes, I will update that right away. Thanks for the reminder.

hi @dgeb, I am @gdeb, and it took me a while to understand why I was pinged...

The update history and upcoming version spec too needs to be updated.

@dgeb Thanks for the update! Would it be possible to get minutes from these weekly meetings (even very brief) posted in https://discuss.jsonapi.org/c/meeting-minutes, or something similar? I am excited to see progress – please let me know if there's anything I can do to help.

Any updates?

Any updates?

@jugaadi et al - I've just posted a proposal for a change in direction for v1.1 in #1435

I am excited to see progress – please let me know if there's anything I can do to help.

@tobyzerner thank you for your offer, and apologies for taking so long to reply. I will discuss your offer with the other editors (@gabesullice + @wycats) and see what they think. I definitely want to be more open about decision-making and get as much community buy-in and feedback as possible as we move towards finalizing v1.1.

Any updates?

Closing now that v1.1 RC3 has been released with all the planned updates discussed here. At this point we're just making fine tweaks and waiting for a couple initial implementations to be finished.


fixed typo leading to broken task definition

Additional question: As the gnucobol extension has no ts source at all - can we add this here?

The task provider is under the experimental flag and if or when it is released from this flag, I will have tested it/documented or removed it if the experiment fails.

for the reference - typo fixed as part of 5c1e09584945aa8eed89b00942b28fd11b97edfb


Update examples.md with toggle theme example

A basic theme toggler built using React-Hooks and Context.
The purpose of building this app is to get familiar with React-Hooks and Context.
https://react-hooks-toggle-theme-example.now.sh

Hello @chinmaykude!
As examples section is no longer maintained I will close this PR as outdated.
Thank you!


ipad5(gen) A9 16.6.1 touch broken after jailbreak

Hello! After jailbreaking my iPad 5 using Dopamine 2.0.4, I’ve encountered an issue where the touchscreen is unresponsive (however, it recovers after a forced restart). Could you please advise on how to solve this problem? Is there any additional information needed from me?

I have the same issue on my iPhone 8 on 16.6 Beta 1 and I've tried to troubleshoot for hours it seems to be an issue with replacing the display though other jailbreaks work and it works unjailbroken

Disable all of your tweaks, Does it still happen?

Disable all of your tweaks, Does it still happen?
Definitely interested in this as I’m thinking of updating then futurerestoring an 8+ to this version from a working iOS 14 jailbreak just a test this

I haven’t installed any tweaks through dopamine jailbreak (touch issues preventing me from installing tweaks), and yet, this issue still occurs
If you are referring to Bootstrap, I have cleared out Bootstrap, but I am not sure if this is related to the issue at hand.

Disable all of your tweaks, Does it still happen?
Definitely interested in this as I’m thinking of updating then futurerestoring an 8+ to this version from a working iOS 14 jailbreak just a test this

If you go to #296 I test this thoroughly on my iPhone 8


Create eval wrapper function that parses input before execution to verify it's valid lave output and not malicious arbitrary code

this is a neat idea, but outside the scope of this project.


Could it detect image file?

like title...

@jkiss Yes .

Yes.

ThanksSent using CloudMagicOn Wed, Jan 28, 2015 at 12:24,  Sindre Sorhus<EMAIL_ADDRESS>wrote:            Closed #23.
—Reply to this email directly or view it on GitHub.


error in migrating the old python version cheat to new go version - failed to load sheet: conf.yml

Thanks for submitting a bug report. Please provide the following information:
A description of the problem
Hello, I am trying to migrate my old python cheat setup to use the current golang version, but after setting in the conf.yml file to point the personal cheatsheet to the old .cheat location, I am having the following error:
failed to list cheatsheets: failed to load cheatsheets: failed to load sheet: conf.yml, path: /Users/ipstone/.ipdot/.cheat/conf.yml, err: failed to parse front-matter: failed to delimit frontmatter

cheat version info
Please paste the output of cheat -v here.
4.1.0

cheat configuration info
If your bug pertains to how cheatsheets are loaded and/or displayed, please
paste here the following information:

The output of cheat -d

community: /Users/ipstone/.config/cheat/cheatsheets/community
personal:  /Users/ipstone/.ipdot/.cheat

The contents of your conf.yml file

# The editor to use with 'cheat -e <sheet>'. Defaults to $EDITOR or $VISUAL.
editor: vim

# Should 'cheat' always colorize output?
colorize: true

# Which 'chroma' colorscheme should be applied to the output?
# Options are available here:
#   https://github.com/alecthomas/chroma/tree/master/styles
style: monokai

# Which 'chroma' "formatter" should be applied?
# One of: "terminal", "terminal256", "terminal16m"
formatter: terminal16m

# Through which pager should output be piped? (Unset this key for no pager.)
pager: less -FRX

# The paths at which cheatsheets are available. Tags associated with a cheatpath
# are automatically attached to all cheatsheets residing on that path.
#
# Whenever cheatsheets share the same title (like 'tar'), the most local
# cheatsheets (those which come later in this file) take precedent over the
# less local sheets. This allows you to create your own "overides" for
# "upstream" cheatsheets.
#
# But what if you want to view the "upstream" cheatsheets instead of your own?
# Cheatsheets may be filtered via 'cheat -t <tag>' in combination with other
# commands. So, if you want to view the 'tar' cheatsheet that is tagged as
# 'community' rather than your own, you can use: cheat tar -t community
cheatpaths:

  # Paths that come earlier are considered to be the most "global", and will
  # thus be overridden by more local cheatsheets. That being the case, you
  # should probably list community cheatsheets first.
  #
  # Note that the paths and tags listed below are placeholders. You may freely
  # change them to suit your needs.
  #
  # Community cheatsheets must be installed separately, though you may have
  # downloaded them automatically when installing 'cheat'. If not, you may
  # download them here:
  #
  # https://github.com/cheat/cheatsheets
  #
  # Once downloaded, ensure that 'path' below points to the location at which
  # you downloaded the community cheatsheets.
  - name: community
    path: /Users/ipstone/.config/cheat/cheatsheets/community
    tags: [ community ]
    readonly: true

  # If you have personalized cheatsheets, list them last. They will take
  # precedence over the more global cheatsheets.
  - name: personal
    path: ~/.cheat
    tags: [ personal ]
    readonly: false

    #path: /Users/ipstone/.config/cheat/cheatsheets/personal
    #path: ~/.cheat

  # While it requires no configuration here, it's also worth noting that
  # 'cheat' will automatically append directories named '.cheat' within the
  # current working directory to the 'cheatpath'. This can be very useful if
  # you'd like to closely associate cheatsheets with, for example, a directory
  # containing source code.
  #
  # Such "directory-scoped" cheatsheets will be treated as the most "local"
  # cheatsheets, and will override less "local" cheatsheets. Likewise,
  # directory-scoped cheatsheets will always be editable ('readonly: false').

Trying to debug this: I think the problem is mostly likely from the conf.yml file, initially I thought it might be the delimiter issue, but upon inspecting the content: (my conf.yml was first generated with the cheat --init  command):
The first line in the conf.yml is "---" :
- This line is the cause of the error - after removing this line, everything works fine.
So I would suggest to update the code to remove that line from the cheat --init command.
Thanks

Another strange issue is the golang version of cheat has strange behavior, when called with the full path, such as '~/bin/cheatvs.cheat:     on both mac, and linux, when I call it with the full path, everything works fine, but when with just cheat`, it will give the error of ```failed to load config: failed to resolve symlink: Users/ipstone/.ipdot/.cheat: lstat Users: no such file or directory

Sorry it has taken me so long to respond.
It's hard to know what went wrong here (--- is a valid first-line for YAML files), but it's possible there was some issue with that line and front-matter parsing or something.
Given that this ticket pertains to such an old version of cheat, I'll assume I can safely close it.


Create additional generic page types for local testing

Might be better to have this work come after #44 is completed

This is covered by the Brand Guide


uncurated paper summary

Create a page listing/summarising the uncurated papers (title, authors, years...- or something along those lines) with links to claiming the publication in canto

I worry that it'll be a boring laundry list on a page, but if users like it, I don't have to look at it.

I doubt it will encourage people to curate much.... I'll put low priority and we can discuss if we really want to do this. MAybe there are better ways...

I'm going to close this. I don't think it will be so helpful compared to other actions/activities. We will gear up to these in the New Year with the community curation paper/ tutorials etc

We can always revisit later

We can always revisit later

I like Antonia's suggestion.
At some point I'd like to have a page that gives an overview of all pombe papers, with curated vs uncurated, high vs low throughput, number of annotations per paper and number of genes per paper.  So like the Canto stats page but just for papers and with links to various lists (like the list of uncurated papers).
I've put no thought into how this would work or look.  Or if it's at all useful.  :-)

Yes actually I agree a summary table would be nice. It would be useful to have a public snapshot of curation progress/triage status. I was thinking  only of long lists.
I will re-open this one

I'll close this.
We already have an annotation stats page
https://curation.pombase.org/pombe/stats/annotation
with details of curated/uncurated papers.
The most likely place  people will look is the actual publication page, and this will have a clear message saying the paper is uncurated and asking people to contribute.
I think we could encourage more people to curate by asking them to check the status of their publication pages.


chore(test-mkdocs): test if mkdcoks config needs to be in the root

The purpose of this PR is to test whether or not mkdocs actually requires mkdocs.yml to live in the root of the repo.

Turns out that the mkdocs.yml that lives in docs isn't actually getting read, but the builds are generating a new one each time. The cat mkdocs.yml is missing the extra nav configuration this branch added.


Function to properly create DownloadTarget from an url

Switching to draft because I'm not super convinced by this last commit, but it's an attempt at having a way to not insert mirrors which are the same for the same host. An improvement over this would be to completely make the map an opaque type, not a global map, so that it cannot be possible to insert a mirror without that check. I considered it but had to revert to this because there is a lot to change to get there, including the python usage. However if some agree here I will do the effort.

There is one last issue to fix for making this work with the libmamba integration, working on it.

This should be sufficient to use in the libmamba integration PR, or so I think.


Add authentication on prometheus and alertmanager

Add authentication on prometheus and alertmanager

Could test with nginx-ingress basic auth

Done with oauth2 proxy.
https://github.com/equinor/sdp-flux/commit/ffc9846729bfc9bca11e84319f1de7156801d238


I can't run examples

I got this

../../../src/renderer_gl.cpp (4541): BGFX Failed to compile shader. 0: 0:11(2): error: array index must be < 1
../../../src/bgfx.cpp (57): BGFX 0x00000002: Failed to compile shader.
Aborted
and I have this
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) IGD
OpenGL version string: 2.1 Mesa 10.5.4
OpenGL shading language version string: 1.20

Are you in runtime directory when you run examples?
https://bkaradzic.github.io/bgfx/examples.html#examples

yes, as i am running debug it show me a lot of messages please check this
http://pastebin.com/gjNqrsfB

What GPU you have?

Ok grab latest and try again. If it fails again post another TTY debug info.

Some of examples works others slowly and some crashs please see the list http://pastebin.com/BnPKgGcE
Probably because this too old and limited GPU, anyway maybe this helps bgfx compatibility with old hardwares
Thanks

Is this some Intel integrated GPU pre SandyBridge?

sadly yes this https://wiki.gentoo.org/wiki/Intel says that is Gen3 Intel i915.

Yeah, minimum requirement is GL2.1/GLES2/D3D9 level GPU. Technically you can use it for your projects where you don't do more complex shaders, but examples won't work.


need to add an option for ignore nuclear remnant in particle searches

All final-state particle searches now ignore nuclear particles. A separate function exists for getting final-state nuclear particles.


Re-importing the same report leaves the duplicates in status mitigated

Bug description
When we import a report which includes itself duplicates, when re-importing the same report, the duplicates get mitigated.

first import:

1 active, verified
1 inactive, duplicate

after reimport:

1 active, verified
1 inactive, mitigated, duplicate

It doesn't seem correct to me. I'd expect to have :

1 active, verified
1 inactive, duplicate (same status as before the reimport as we have just re-imported the same report)

The problem is that when matching the new findings to the existing findings, we always match the new findings to the same single original finding (the one that's not duplicate). Consequently, the duplicates from the original report are flagged as mitigated because no new finding was matched against them.
i think the issue is here (serializers.py and test/views.py)
                if findings:
                    # existing finding found
                    finding = findings[0]

Intead of working on the first finding that matches, we should work on all of them (might need a bit of tuning in order not to re-save the same findings multiples times...)
Sample data: with checkmarx parser attached
Steps to reproduce
Steps to reproduce the behavior:

Import the report once
Re-import the same report
Expected behavior
The status after the re-import is the same as after the initial import

Deployment method (select with an X)

[ ] Kubernetes
[x ] Docker
[ ] setup.bash / legacy-setup.bash

Environment information

DefectDojo Commit Message:

$ git show -s --format="[%ci] %h: %s [%d]"
[2021-02-26 17:14:50 +0100] 4f789bc7: fix flake8, fix Q queries, add  unit tests [ (HEAD -> reimport-configurable-dedupe, myOrigin/reimport-configurable-dedupe)]

Sample scan files (optional)
See attached
checkmarx_duplicate_in_same_report.zip
Screenshots (optional)
Console logs (optional)
Additional context (optional)
I've found this while working on https://github.com/DefectDojo/django-DefectDojo/pull/3753 and the provided report will produce the issue after this is merged. The problem was present before PR 3753 but the test data provided might not replicate it.

It looks like this was fixed via https://github.com/DefectDojo/django-DefectDojo/pull/3753

I was under the impression this was fixed, but may not be @valentijnscholten  could you please confirm?

This still happens when an import contains duplicates, i.e. 3 findings getting the same hash_code. On the next reimport of that report, there is no way to uniquely match the incoming 3 findings against the 3 existing one. So the 3 incoming findings will all get matched against the 1st existing finding with the same hash_code. This finding will remain open. The other 2 will be marked as mitigated as it appears they are no longer present in the report.
Usually it means the deduplication algorithm is not 100% correct for the scanner, or the parser doesn't do a good job around dupe_key deduplication. But still I think we should try to improve the situation as it appears very confusing currently.  In the past we had matching on title, cve, cwe, etc. Maybe we should fall back to those if there are multiple existing findings with the same hash_code.

don't think it was fixed

Any updates on this issue? Still annoying in 2024


[9.x] Adds to_path helper

In the spirit of the to_route helper introduced in #40522, this PR adds a to_path helper for readability when returning to a path.
As an example of how it'd read compared to how it currently reads:
// return redirect()->to('/welcome');
return to_path('/welcome');

Named redirect_to will better  ？？

Named redirect_to will better ？？

Name pair with this, I guess
https://laravel.com/docs/9.x/helpers#method-to-route

Can't you just use return redirect('/welcome')?

No more global functions please

redirect to is not use many.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Remove justfile

And replace it with pixi.toml. We also need to take a pass on the names of the commands in pixi.toml to make them consistent.

Part of #3717


Feature request: Logger - ability to clear state

Use case
Hi - we're beginning to use Powertools Logger as a canonical logger. By that I mean we append various key/values to the logger as the lambda executes and then flush them to stdout by calling a write method e.g myLogger.info('canonical');
Chatting with @am29d and @dreamorosi on Discord, it was confirmed there's no way to clear the keys that were added using appendKeys(). This means that those keys remain present during the next warm lambda invocation.
Solution/User Experience
Providing a logger method such as clearState() that clears down any user appended keys would solve the problem.
Alternative solutions
The only other solution in user land is to keep track of the appended keys and clear them down using removeKeys

Acknowledgment

[X] This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
[X] Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers
Please react with 👍 and your use case to help us understand customer demand.

Hi @rcoundon, thank you for opening this issue.
As mentioned on Discord, I think it’d make sense to have this convenience method, so I am going to put the item in our backlog so it can be picked up.
Just to manage expectations I think it’s unlikely it’ll make the cut for this week release, but if not, it’ll be included in the following one (~next week or the following one).

That's great, thanks again for accepting it and putting it into the backlog so quickly

I have started looking into this and I might have found a slight inconsistency or rather something that we should address as part of this work.
Right now internally we treat what we call "persistent attributes" and "ephemeral attributes" the same - aka they're placed in the same object. The description of these and the clearState feature is quite ambiguous about this, but even though internally they're the same, the actual current behavior is:

customers can add attributes to a Logger instance in 4 ways: 1/ via the persistentLogAttributes constructor option at instance creation, 2/ via the addPersistentLogAttributes method at runtime, 3/ via the appendKeys method also at runtime, and 4/ via the setPersistentLogAttributes method at runtime - this last method replaces the pre existing values.
when using the class method decorator or Middy.js middleware with the clearState option enabled we keep track of any attribute added during the invocation either via addPersistentLogAttributes or appendKeys and restore the initial state after the invocation. We do this by taking a snapshot of the attribute immediately before the handler is executed and then restoring it right after
there is not equivalent of the behavior described in 2/, which is why this feature request was opened

Below a simplified pseudo-code representation of the current implementation:
// middleware AND decorator
const injectLambdaHandler = (logger: Logger) => {
  let initialAttributes = {};
  const before = () => {
    initialAttributes = logger.getAttributes();
  };

  const after = () => {
    logger.setPersistentLogAttributes(initialAttributes)
  };

  return {
    before,
    after,
  }
}

With the middleware or decorator above, the usage would be like this (showing only middleware but the decorator works the same):
const logger = new Logger({
  persistentLogAttributes: {
    accountId: '01234567891012'
  }
});

export const handler = middy(async (event: unknown) => {
  logger.appendKeys({
    event
  });

  logger.info('CANONICAL');
}).use(injectLambdaHandler(logger, { clearState: true }));

The result of this would be a canonical log that contains:

the accountId key with the same value for all invocations
the event key with a value corresponding to the payload for each invocation

The above is the behavior documented in the docs, which is fine. What is not included in the docs however is that this is also possible:
const logger = new Logger({
  persistentLogAttributes: {
    accountId: '01234567891012'
  }
});

export const handler = middy(async (event: unknown) => {
  logger.appendKeys({
    event
  });

  if (condition) {
    logger.addPersistentLogAttributes({ foo: 'bar' });
  }

  logger.info('CANONICAL');
}).use(injectLambdaHandler(logger, { clearState: true }));

Because of the names of the methods, and especially the "persistent" word, I would expect the foo key added via the corresponding method to not be cleared after the invocation. This however is not true and instead all keys added during the invocation are cleared regardless of the method used.
Based on the implementation and meaning of the names, I think this should not be the case and persistent attributes should be treated as such and thus only cleared after customers remove them explicitly (i.e. removeKeys).
To this end, I propose to consider the current behavior as unintended effect (aka bug) and rectify the implementation so that both the new clearState method and the existing corresponding option in the middleware and decorator would only clear the keys added via the appendKeys.
Additionally, I would also:

mark the setPersistentLogAttributes method as deprecated and to be removed in the next major version.
mark the persistentLogAttributes constructor option and addPersistentLogAttributes method as deprecated and add respectively a persistentKeys option and appendPersistentKeys method - this would be just a renaming for consistency and the old naming ones would be removed in the next major version
persistent keys would be removable only by calling the removeKeys method
improve the documentation to clarify the behaviors described above

commenting later today :)

Great discussion and a nice improvement to reduce cognitive overload to everyone! Answering in line, with only one suggestion and one caveat on deprecation method.

mark the setPersistentLogAttributes method as deprecated and to be removed in the next major version.

+1, I’d suggest deprecating now but removing in the 2nd major version (e.g., 4.x) to give ample time. Logger is widely used in nearly if not all customers.

mark the persistentLogAttributes constructor option and addPersistentLogAttributes method as deprecated
+1.

and add respectively a persistentKeys option
and appendPersistentKeys method
this would be just a renaming for consistency and the old naming ones would be removed in the next major version
persistentLogAttrs > persistentKeys

If you allow me, I'd like to suggest a different approach:

Keep only the constructor level. Give one option to customers to persistent data across state flushes. It'll be less confusing and aligned with other languages.
Create a new feature request. Since the method already exists but it's undocumented, we can gauge solid use cases for having a method to persist data across state flushes.

To the best of my knowledge, customers persist keys across state in two ways only: (1) Logger Constructor for simple company standard use cases, and (2) Logger Custom Formatter for complex and dynamic company standards. This means whoever set those standards have access to the constructor and often export an instance of a Logger. Whoever uses it, can still use appendKeys / removeKeys as part of the transaction if they wish to have the key as early as possible.

improve the documentation to clarify the behaviors described above

+1. Keeping one option for persisting across state will also simplify the documentation and make it less ambiguous.

I would like to pick this one up. Thanks for the clear description of the issue.


Wildcards expansion is silenty skipped when the pattern comes from a complex expression

Steps to reproduce
Programmatically generate a file pattern that contains a wildcard and try to create an item list from it. Compare the results to a hard-coded pattern, or a pattern that comes directly from a property.
Project file
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" DefaultTargets="MyTarget">
	<PropertyGroup>
		<MyPattern>*.txt</MyPattern>
	</PropertyGroup>

	<ItemGroup>
		<GenItem1 Include="*.txt" />
		<GenItem2 Include="$(MyPattern)" />
		<GenItem3 Include="$(MyPattern.Replace('this does', 'nothing'))" />
	</ItemGroup>

	<Target Name="MyTarget">
		<Message Text="Direct wildcard: @(GenItem1)" />
		<Message Text="Via property: @(GenItem2)" />
		<Message Text="Via complex expression: @(GenItem3)" />
	</Target>
</Project>

Directory contents:
/
- a.txt
- b.txt

Command line
msbuild my.proj

Expected behavior
Wildcards should be expanded according to the final value of the expression, even if it is a complex expression. Output should be:
Direct wildcard: a.txt;b.txt
Via property: a.txt;b.txt
Via complex expression: a.txt;b.txt

Actual behavior
When the pattern is generated by some expression, wildcards are not expanded. Output is:
Direct wildcard: a.txt;b.txt
Via property: a.txt;b.txt
Via complex expression: *.txt

Environment data
msbuild /version output: <IP_ADDRESS>107
OS info: Microsoft Windows [Version 10.0.18363.836]
If applicable, version of the tool that invokes MSBuild (Visual Studio, dotnet CLI, etc): CMD

This because the result of property functions is an escaped string. If you want to unescape it, you can use the property function $([MSBuild]::Unescape()).


Can't find working directory

Thanks for sharing this great work!
I'm getting the following error with intv.pyFile when I try this command.  "python intv.py -f 4 -vdir C:\Users\importon\Documents\CURE-main\video_data\FF.mp4 -rs 1280,720 -nf -1 -d 1"
Why is it trying to make a "video_data" directory before my root directory?
"intv.py", line 39, in video_interpolate
os.mkdir(frame_dir_ori)
OSError: [WinError 123] The filename, directory name, or volume label syntax is incorrect: './video_data/C:\Users\importon\Documents\CURE-main\video_data\FFframes/'

Thanks for point out this! You could try to enter relative path for the video filename. In this case, try with this command: "python intv.py -f 4 -vdir FF.mp4 -rs 1280,720 -nf -1 -d 1".


Feature - Implement forget password feature

Describe the bug/feature
Currently there is no forget password functionality in application.

Implementing backend route for the same.
one time password reset link will be sent to user through email.
Integrating backend route with frontend.

Additional context
@kanak22  @rockingrohit9639, I'd like to work on it, please assign 🚀

@naveen8801 I have assigned you this issue. Make sure you complete it in 6 days


[PL-46738] SMP patch 0.13.1 release notes

SMP patch release 0.13.1 release notes
Note: Air gap bundle and Helm chart links are placeholders and won't be active until the patch is deployed.
For reviewers, a preview is available:
https://65b9e6382c9f7d8fd730334a--harness-developer.netlify.app/release-notes/self-managed-enterprise-edition#january-30-2024-patch-version-0131
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65b95069996c4a319ed5a5b0--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65b9e6382c9f7d8fd730334a--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65bad5acc67bb537b5406016--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65bcec1ada9c218990bb5405--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65bcee5a6846f88b4498727c--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65bcf005929de08b002d4218--harness-developer.netlify.app


Paypal donate link?

Hey Man, really appreciate your work. It's really good and it's been of major use to me. Do you have a paypal donation link or something similar?

Hey,
I'm really flattered but to be honest I have never considered that. I need to check how to make that Donate button because I do not know anything about it 🙂 I will add it over the weekend if standard paypal account allows that. I will, of course, list your name in the new Supporters section in the readme if you do not mind 😄

@wojtkowiak Sounds good to me! This evening I was looking for a postgres npm package and saw a donate link on their NPM page https://www.npmjs.com/package/pg-promise They use something called "Pledgie" this maybe might be a good fit for you.

Yeah, thanks for this info, this Pledgie seems good and transparent 😄 So I will add the link tomorrow to readme. I have already signed a campaign there: https://pledgie.com/campaigns/33341

The link is here https://github.com/wojtkowiak/meteor-desktop#contribution
Feel fry to donate :) Thanks a ton for this initiative.


stm32f4/io.fs incorrectly using stm32f1 register layout

The F4 has the io mode and PP/OD state in separate registers, unlike the F1 where they're interleaved in CRL/CRH. The constants and the io-mode! word are copied almost verbatim from the F1 code and are therefore not working.

Maybe the stm32l0/io.fs code would be a better starting point? I haven't used the F4 much, I admit.

I managed to put together a working replacement myself, but since it's pretty much the first real Forth I've written it's pretty suboptimal :) - I'll test the L0 code and if it's good (or only needs minor tweaks) I'll report back.


feat: a more comprehensive select component based on rc-select

A more comprehensive select component based on rc-select
The implementation references ant-design
https://user-images.githubusercontent.com/96771399/173327888-1a8a6796-8a73-4309-be51-fbc45160a264.mov

May use the rc-select in the EnumField too?

May use the rc-select in the EnumField too?

Yes, I've tested it briefly, but I'm not sure if there are any other style problem. So for now only one part of the EventWidget has been modified. I will test it more thoroughly and replace all the chakra select


Icons are wack

Some of the icons aren't showing properly. Here (will be) is a list of them and what is wrong with them.

[ ] acorn
[ ] apple
[ ] anvil
[ ] ankh
[ ] angel wings
[ ] anchor
[ ] all for one
[ ] alien fire
[ ] archer
[ ] archery target
[ ] arrow flights
[ ] arson
[ ] axe
[ ] axe swing
[ ] ball
[ ] barbed arrow
[ ] barrier
[ ] bat sword
[ ] battered axe
[ ] batteries
[ ] battery positive
[ ] bat wings
[ ]
[ ]

Duplicate issue.


Update message envelopes & responses to include before field

Fixes DOC-8518
Update to the Responses and Message Envelope section on the Changefeed Messages page to add some detail on the before field in changefeed messages.

Thanks for reviewing @miretskiy !


How can I use install the opencv that build by vcpkg in python3 whitch installed by vcpkg

Describe the bug
vcpkg install  opencv[python] python3 is installed ok.
Environment

OS:Windows
Compiler: vc14

To Reproduce
Steps to reproduce the behavior:

vcpkg install  opencv[python] python3
See error
In the python cmdline,import cv2 get error, through pip install opencv-python sovled this, but I wan't use the opencv[gstream] witch build by vcpkg, I copy the cv2 derectory I found in /registry/Lib/site-packages/cv2  to lib/sitepackage/cv2 doesn't work ether.

already solved,
config.py
import os
+os.add_dll_directory("D:/vcpkg/installed/x64-windows/bin")
BINARIES_PATHS = [
os.path.join('D:/vcpkg/packages/opencv4_x64-windows', 'bin'),
os.path.join(os.getenv('CUDA_PATH', 'C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.7'), 'bin')
] + BINARIES_PATHS
config-3.11.py
PYTHON_EXTENSIONS_PATHS = [

os.path.join('/registry/Lib/site-packages/cv2', 'python-3.11')

os.path.join(os.path.split(os.path.realpath(file))[0], 'python-3.11')
] + PYTHON_EXTENSIONS_PATHS


Guest network becomes unknown over time

Not directly related to restarting home assistant. Manually restarting wifi registrar services fixes issues.

May be due to csrf token becoming expired.


Usage of DARTEL

Hello,
I have a study in which due to the second level masking of SPM, we end up losing activation at the posterior sides of the brain.
So I used DARTEL, and the template that is generated from aamod_dartel_createtemplate (for example, wTemplate and Template)
What is the difference between these two templates? Is one the group average, and the other one is group averaged to normalized space? Furthermore, when I do second level using DARTEL, are the results normalized as well, so should I use wTemplate to visualize results?
Lastly, both templates show gray matter or whitematter only, and the render resolution is a little low. Is there a way to make this template more MNI-like (ie., show all of the brain, not just GM, WM differences)

Hi,
Correct, the Template* are the the group average, while the wTemplate* are the ones in MNI space. However, they are templates only, including GM and WM only (as you noted), and used by DARTEL. I do not recommend using any of them for visualisation.
I suggest using the MNI template (from FSL, which is high-res) or the group-average of the normalised T1 images.

Thanks a lot for your answers.

or the group-average of the normalised T1 images.

How can I obtain this?

Use aamod_dartel_norm_write to normalise the structural stream (typically the T1 images).
Set aap.tasksettings.aamod_secondlevel_threshold.overlay.template = 'averaged_structurals'

Thanks a lot.
You may recall from our previous meeting that I was running into this second level masking issue caused by participants with smaller brains relative to the MNI template. Because of this, activity that corresponds to the occipital cortex/pole in these participants, instead moves more towards the midline. Which misrepresents the finding.
I used DARTEL, but the issue remains. In fact, in terms of activation t-maps, I can not see any difference between DARTEL normalized and regular normalization on the MNI template.
But when I render this based on the Template* or wTemplate, I do see those activations at the surface of cortex.
Furthermore, when I eyeball and compare wTemplate with Template, I see that they are identical. Which makes me think if I may have done something wrong?

I used DARTEL, but the issue remains. In fact, in terms of activation t-maps, I can not see any difference between DARTEL normalized and regular normalization on the MNI template.

Okay, there is some subtle differences, but in terms of the spread of activity that I see, they are mostly similar.

Furthermore, when I eyeball and compare wTemplate with Template, I see that they are identical. Which makes me think if I may have done something wrong?

The Template and wTemplate in the module folder are identical; however, the actual (non-normalised) DARTAL template is in the structural folder of the first subject. Check out stream_dartel_template_outputfrom_aamod_dartel_createtemplate_00001 for the path.

I also suggest rerunning the analysis from scratch (unless you did so already) to avoid using already existing files from the other workflow.

I did, but I will re-preprocess because I noticed I had not set writenormimg for smoothing to 0.
Also, does aamod_norm_write_dartel  also do smoothing? The output files are named "swarsub" which indicates smoothing. Because I did smoothing myself as well, they ended up becoming "sswarsub". So I removed smoothing and set the FWHM to my desired value for the normalization module itself.

I did, but I will re-preprocess because I noticed I had not set writenormimg for segmentation to 0.

That explains the similar results.

I removed smoothing and set the FWHM to my desired value for the normalization module itself.

Good.

I've been playing around with this for the last few days, and as far as I can see:
DARTEL doesn't change much in terms of activation at the occipital pole. For example, 5 participants who have small brains have common activation in their calcarine sulcus, but since their brains are small, when they are normalized their activity falls more towards the anterior of the calcarine sulcus.
Using the averaged structurals is good in terms of showing the actual location of activation, but the resolution is low, which makes it not so nice looking for the paper.


Cannot Sign In After Build/Run

I was able to build and run this application but I'm not able to sign in and upload my own models. I have already set invite only mode to false. I also tried setting it to true and adding my credentials to the Addresses array. Both have the same results (see attached image). I have very little experience with web applications so I'm sure that I did something wrong. Any ideas what it could be?

I figured it out. My application URL had an extra / in it. Removing it fixed my issue and everything is working great.


Retention count of the scheduled scan is not maintained

On 2.5-head - commit id: 7e386eba

Deploy CIS v2
Create a scheduled scan.
Give in retention count 1/2/4
When scan runs, retention count see in the dropdown of how many reports are saved is always 3
View in Yaml shows retention is correctly saved

@sowmyav27 I dont see this happening. I set the count to 2 and I can see only 2 reports in the dropdown always.

On 2.5-head - commit id: b2953cb

Deployed a custom cluster
installed CIS v2
Deployed a schedule scan with retention-2
Only 2 are seen retained.
Original issue is NOT seen.

Closing it for now.


Error when deleting a model

When trying to delete a model and the virtual column contains any JSON an QueryExceptions is thrown. It seems to be caused by line 87:
$result = parent::fireModelEvent($event, $halt);
Changing the line as follows removes the exception after deleting a model:
$result = ('deleted' !== $event) ? parent::fireModelEvent($event, $halt) : null;

The previous mentioned code change only fixes the QueryException but is has some side effects. When using in combination with https://github.com/richan-fongdasen/eloquent-blameable the deleted_by won't get written to DB.

Can you explain exactly when does this happen?
I use this in stancl/tenancy and deleting tenants works just fine.

It doesn't. And are you sure the issue is with this package? Rather than the blameable one

Yes, I'm sure, because if I don't encode the attributes in case of deleted event the following error occurs:
Illuminate\Database\QueryException
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'manufacturer' in 'field list'
(SQL: update `articles` set `data` = ?, `deleted_by` = 1, `manufacturer` = ?, `recommended_retail_price` = ?, `vat` = ?, `weight` = 11, `width` = 10, `height` = 20, `length` = 30, `search_keywords` = ? where `id` = 2)

The getCustomColumnsof the model looks like this:
public static function getCustomColumns(): array
{
	return [
		'id',
		'name',
		'created_by',
		'updated_by',
		'deleted_by',
		'created_at',
		'updated_at',
		'deleted_at',
	];
}

The update query contains columns which are not real columns in the database table and the population of these columns is done by your trait.

Okay.
I can't work on this myself, so if you want this changed, please send a PR.
I'll accept a PR assuming:

A regression test is added, ensuring this behavior is fixed forever
Existing tests pass
stancl/tenancy tests pass (docker-compose up -d && ./test) when you use your modified version of this package - please present a screenshot showing this

Sorry for the complex requirements, but my main priority with this package is to support stancl/tenancy and I don't want to risk breaking any apps just to support some edge case that's not even used by my package.
Thanks!


Mac OS // App shuts down when going into Preferences

Hello,
when i click “SHOW HISTORY RATES” FIRO electrum suddenly shuts down with an error. After that when I reboot FIRO electrum whenever I click on “preferences” the app shuts down.
the only solution to this is to go into the directory where FIRO electrum is and delete the whole folder.
After doing this I can go into “preferences” where the settings are reset (because of the deletion of the directory folder)
I use the latest MAC OS, MacBook Pro

For those who also encounter this problem, you can do the following to be able to start Electrum Firo again:

Open the Electrum Firo data directory.
Open the config file and remove this line. Save and exit.
"history_rates": true,
You should be able to start Electrum Firo again.

Fixed in #39


Don't make me think Chapters 12 and 13

The final chapters of Don't Make me Think book club.

Closing branch, the book is done.


file Singularity is not needed within project

https://github.com/nf-core/bcellmagic/blob/11d19bc2c68633cca93c522736552691fff459da/Singularity#L3
As per discussion on slack, this file is not needed and should be removed from the repo.

fixed by #54


Add support for reading the app data directories

Looking to be able to use this in one of my apps vs my really crappy old android_app_info plugin, this is basically the main thing it's missing. Other than that, it's perfect!

Thanks a lot for your PR.
I will merge it and release a new version.

Thanks!


readme: fix spelling error

"least significant", not last. got it right in other places though!

Thank you!


OnNotificationReceived not called when app is closed/killed/terminated

🐛 Bug Report
I'm not sure if this is by design from Firebase, but OnNotificationReceived() is called when app is in the foreground and background, but not when the app is killed. I want to store data that is in the message onto the app's database, but it doesn't seem to save it.
Expected behavior
OnNotificationReceived to be called when the app is closed/killed/terminated.
Reproduction steps
My sample notification is:
{
"to": "/topics/testtopic",
"content_available": true,
"data": {
"testdata1": "123",
"testdata2": "456",
"testdata3": "789"
},
"priority": "high"
}
I have OnNotificationReceived in my app.xaml.cs.
Configuration
Version: 3.3.10
Platform:

[x] :iphone: iOS
[x] :robot: Android
[ ] :checkered_flag: WPF
[ ] :earth_americas: UWP
[ ] :apple: MacOS
[ ] :tv: tvOS
[x] :monkey: Xamarin.Forms

In my project.notification  is still received even when the application is closed.but i use localpush notification
// Push message received event
CrossFirebasePushNotification.Current.OnNotificationReceived += (s, p) =>
{
NotificationCenter.Current.Show(new NotificationRequest()
{
BadgeNumber = 1,
Description = p.Data["title"].ToString(),
Title = p.Data["content"].ToString()
}); ;
System.Diagnostics.Debug.WriteLine(DateTime.Now.ToString()+":Received"+JsonConvert.SerializeObject(p.Data));
};

Can you show an example payload where this works for you? Does it also work on Android? If so can you show where MessageReceived is triggered because I got it to work on iOS but not Android, even when putting on MainApplication class OnMessageReceived.

in app.xaml.cs share code
`
// Push message received event
CrossFirebasePushNotification.Current.OnNotificationReceived += (s, p) =>
{
NotificationCenter.Current.Show(new NotificationRequest()
{
BadgeNumber = 1,
Description = p.Data["title"].ToString(),
Title = p.Data["content"].ToString()
}); ;
System.Diagnostics.Debug.WriteLine(DateTime.Now.ToString()+":Received"+JsonConvert.SerializeObject(p.Data));
};
in mainapplication.cs android
[Application]
public class MainApplication : Application
{
public MainApplication(IntPtr handle, JniHandleOwnership transer) : base(handle, transer)
{
}
    public override void OnCreate()
    {
        base.OnCreate();

        //Set the default notification channel for your app when running Android Oreo
        if (Build.VERSION.SdkInt >= BuildVersionCodes.O)
        {
            //Change for your default notification channel id here
            FirebasePushNotificationManager.DefaultNotificationChannelId = "FirebasePushNotificationChannel";

            //Change for your default notification channel name here
            FirebasePushNotificationManager.DefaultNotificationChannelName = "General";
            FirebasePushNotificationManager.DefaultNotificationChannelImportance = NotificationImportance.Max;
        }

        //If debug you should reset the token each time.

#if DEBUG
FirebasePushNotificationManager.Initialize(this, true);
#else
FirebasePushNotificationManager.Initialize(this,false);
#endif
        //Handle notification when app is closed here
        CrossFirebasePushNotification.Current.OnNotificationReceived += (s, p) =>
        {
        };
    }
}

in MainActivity.cs android
protected override void OnCreate(Bundle savedInstanceState)
{
TabLayoutResource = Resource.Layout.Tabbar;
ToolbarResource = Resource.Layout.Toolbar;
        base.OnCreate(savedInstanceState);
        global::Xamarin.Forms.Forms.Init(this, `savedInstanceState);
        LoadApplication(new Portable.App());
        FirebasePushNotificationManager.ProcessIntent(this, Intent);

    }

`

@ALBERT-son  did you manage to resolve this issue ?

any updates on this? Thanks a lot! @ALBERT-son @kamilkosek

Same question - when the app is minimized I get the notifications, but when the app is in the foreground the normal notification doesn't show, also when the app is killed the notifications don't show.

This is expected behavior from firebase if using an notificaiton message. If you want OnNotificationReceived to be hit use a data message.
https://firebase.google.com/docs/cloud-messaging/concept-options#notifications_and_data_messages

This is expected behavior from firebase if using an notificaiton message. If you want OnNotificationReceived to be hit use a data message.
https://firebase.google.com/docs/cloud-messaging/concept-options#notifications_and_data_messages

I am actually using a data message and it is working when the app is in background. Though, when the app is killed (from task manager), it doesn't hit the OnNotificationOpened method.

We also face the similar issues on iOS and Android. On our end seems like following:
Android foreground: notification is not received at all
Android background: notification is received, event is fired properly (after tapping on notification)
Android killed: notification is received, event is fired properly (after tapping on notification)
iOS foreground: notification is received, event is fired properly (after tapping on notification)
iOS: background: notification is received, event is fired properly (after tapping on notification)
iOS killed: notification is not received at all
We are using notification message combined with data message, as Firebase docs recommends:

Use notification messages when you want FCM to handle displaying a notification on your client app's behalf. Use data messages when you want to process the messages on your client app.

FCM can send a notification message including an optional data payload. In such cases, FCM handles displaying the notification payload, and the client app handles the data payload.

Any ideas? Any thoughts how this could be fixed?

I'm facing the same issue. Did anyone resolve this?


fontSize for labelStyle does not change for android

Yeah that's correct, I should update the documentation. Unfortunately you're unable to style the android picker like that (see: https://reactnative.dev/docs/picker-style-props)


Multiple engines in multiple threads

Hi, I wrapped your main file into a class and created 4 objects, each running in separate threads. However, I have doubts that the GPU processes are truly running in parallel because when I increase the feeding rate to the engines, the memory usage keeps increasing until it's full. Is there any specific configuration or changes in code for support this?

You shouldn't need code changes for multithreading, but GPU memory is shared between threads, so high feeding rates can cause memory saturation.

Thanks for your hint! Do you have any suggestions for handling this on a GPU? Any extra code or changes needed?

No code changes should be necessary in my opinion. It is possible to just wrap the engine class and run it in a multithreaded environment. I would check these things first:

Ensure your models and data fit within the GPU's memory limits.
Make sure you're properly freeing up memory to avoid leaks.
Use CUDA streams if possible: They can help manage multiple tasks on the GPU more efficiently.


USB HID Joystick on ESP32

Title ** note lower priority **

We don't have a HID joystick specification yet. Do we need this?

I think adding this is a stretch.
We do not even currently have a joystick extension for makecode, though the code for hid joystick exists in codal. I think P2 is the correct priority to have for now.

Moving it to p3

udpated platform


Add fix for issue 15

I've just added the little fix to listener.rs to allow pending outbound messages to be sent on the socket before it gets locked up again by the listener loop. It successfully built for me using cargo 0.12.0-nightly. Please let me know if I've done this correctly!

Would yield_now() https://doc.rust-lang.org/std/thread/fn.yield_now.html be more appropriate than sleeping for 1ms?

I was about to say yes, yield_now is much better, but I'm finding it doesn't fix the issue. I have some reasoning for why: yield_now() does open the socket to threads that have already made a call to send_message at the time of the yield, but that isn't the case for a thread waiting on the receiver side of the channel for incoming messages. That thread still needs some time to check if the message it's receiving is a ping, or some other message, before it makes its call to send_message with an appropriate response. And while it might be enough time in some cases, it isn't necessarily enough time in all (and in my case, isn't enough time in any).

Does it make any sense to handle this inside the listener loop?

I need to look more closely at this problem. If something is fixed by a 1ms sleep but not by a yield then this sounds inherently racy and there should be a cleaner fix.

too old


operator datasance-pot-operator (3.4.7)

/pipeline restart operator-hosted-pipeline

/pipeline restart operator-hosted-pipeline

/pipeline restart operator-hosted-pipeline

/pipeline restart operator-hosted-pipeline

/pipeline restart operator-release-pipeline

/pipeline restart operator-release-pipeline


Allow null value for parameter

This PR should solve issue #90
Gently give feedback to fix or improve the PR

@stefanorg Thanks, merging it.

I've also fixed some of the ooold DateType issues. I'll write an example to illustrate what was changed.

:+1:


Only one instance at a time supported

This line overrides the socket/pipe used in the library.
https://github.com/KRTirtho/mpv_dart/blob/5367567962930be19a442c4b745d84c2fbcf6783/lib/src/mpv.dart#L112C1-L113
Since it can't be manually configured, I can't set an application ID or unique instance ID to use for the socket instead. This ends up meaning that only one thing on an entire system can use mpv_dart at any given time.

Hey unfortunately this library is not maintained anymore. Although I accept PRs
You can instead use https://github.com/media-kit/media-kit which uses libmpv with bindings instead of IPC so it's better in that aspect
If you only need mpv for video or audio using media_kit is the best
Also if you need lower level control you can copy the generated bindings from media_kit repo


Add text method to element

yeah I'll take a look

@iamneal ,
Maybe we could add a GetNodeString function to Result for retrieving a part of the string?
Something like:
// GetNodeString
func (r *Result) GetNodeString(n *Node) string {
	return r.expression[n.start:n.end]
}

This would require to parse the Node to the Result, but it keeps the Node struct light and does not unnecessary create a lot of new strings. (only when truly required).


Create referral links for gear

bear canister
bug spray
freeze dried food
tent
shoes
water filter
water bottle
electric lighter
sporks
stove
fuel
tvp
wet wipes
after bite

@lgastineau


Remove @api-label support from resources

Resources having their own labels is unnecessary, and is never used within the library or any generated formats.
Pull support for it.

It's used in Blueprint generation, but should be renamed to something like @api-resourceName so it's clearer what it is.


helm repo add fails on wildcard certificates

Executing the following command:
helm repo add example https://some-namespace.gitlab-pages.some-domain.lan/path/to/helm-charts
leads to:
Error: Looks like "https://some-namespace.gitlab-pages.some-domain.lan/path/to/helm-charts" is not a valid chart repository or cannot be reached: Get https://some-namespace.gitlab-pages.some-domain.lan/path/to/helm-charts/index.yaml: x509: certificate is valid for *.some-domain.lan, not some-namespace.gitlab-pages.some-domain.lan
The certificate is imported and works well on curl/wget and all browsers...
Output of helm version:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.9", GitCommit:"16236ce91790d4c75b79f6ce96841db1c843e7d2", GitTreeState:"clean", BuildDate:"2019-03-25T06:30:48Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}

My fault... the wild card does not match sub-subdomains... but i'm now stucked at #5632


[BUG] Statsmodel is a new dependency, missing in info.py

This is actually incorrect. Sorry about that.


Implement #60. Adds U2DCheckVerbosity Setting

Adds capability for a property defined in BaseOptionModel to be attributed to override the default collection and data type where the setting is stored in the Visual Studio SettingsStore. This functionality was then used to implement getting and setting the General\U2DCheckVerbosity setting.

Figured I'd give implementing this one a shot as a learning exercise.
Once I determined that the ShellSettingsManager SettingsStore was merely a proxy to the Visual Studio registry hive, the real trick was figuring out how to expose this in the Tweaks User Interface. I thought the way the Options menu was generated was pretty elegant, and it made sense to put the setting there, so that is where I looked to. Unlike the other Tweaks, where the settings feed into other extensibility points, I just needed to be able to directly read/write a setting from a different SettingsStore collection and using a specific datatype/serialization method rather than the default storage of the setting into a binary serialized base64 string.
This was achieved by the addition of two attributes that can now be applied to a property to indicate where and how to store and retrieve the setting, and a change to the BaseOptionModel<T> LoadAsync and SaveAsync to respect these attributes. I only implemented a Boolean datastore type, but that mechanism can be easily extended for other data types by adding support in load/save. This gives a simple way of adding new Tweaks that only need to change some of the more 'hidden' settings of Visual Studio, like this one does.
One warning - while this functions as expected when installed as a vsix - changing the setting will immediately impact the build system output based on the current value of the U2DCheckVerbosity setting, when debugging via the experimental instance the setting is properly loaded and saved but has no impact on the build output. Any ideas why this is the case?

Awesome. Thank you!!


Delete files in file browser not working

Environment
DNN 9.4.4 Virgin install using .net 4.7.2 on IIS / SQL Server 2016.
Steps to reproduce
When trying to delete files or folders in the file system (dnn.DigitalAssets.js) there is no confirmation dialog, and the delete fails. There are no console errors.
Expected
User is asked to confirm, and file / folder is deleted upon acceptance.

This also seems to affect the deletion of modules from the dropdown menu..

Did you check that the worker process has full permissions on the folder, I had no issues deleting...

Investigating now..

The IIS App Pool has full control - This is happening for me on 2 separate servers with DNN 9.4.4 on IIS 10.0.14393 .Net 4.7.2 and .Net 4.8

This can be closed - Apologies it's the SKIN causing the JS issue..

Cool


[Excel] (ribbon) changed control and tabs limits

these numerical changes don't need a review

Docs Build status updates of commit c915dc7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/design/contextual-tabs.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c915dc7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/design/contextual-tabs.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Question: ToolButton doesent actuallay have transperent background

Hi, While using BlurWindow to get a acrilic effect in my app, it turns out that ToolButtons don't actually have transperent background. Are there any workarounds/code modifications to fix this?

Thanks!

Well if you look closely, you can see that the normal buttons also dont have it

@rdbende it would be soo nice pf you if you implement this!!

Well, Tkinter (tcl/tk) doesn't support any transparency except that it has a transparentcolor attribute on Windows and Mac OS, and that it has an alpha option (yahh, it's really useful to make the title bar transparent). The alpha would make sense if it was only in areas where transparentcolor is present.  That's why I had to cheat.
The ToolButton, and the background of every widget isn't actually transparent, but the same color as the background of the one behind it, so it looks like it's transparent.
This background color should be the same everywhere, so instead of 'green' transparentcolor you can use the background color the theme uses (you can get it with ttk.Style().lookup(".", "background")) and make that color transparent instead.
Although I don't recommend this blur effect, because when you use transparentcolor than you can click through these "transparent" areas, which is really frustrating.

Thank you!!

@rdbende how did you make it so that it doesn't have the green lines around the labels?

And you said you dont recommend using this blur effect. Is there anyone that you recommend using? (Sorry for bothering you with all these questions)

I deleted the app.config(bg="green") line,
and edited the following lines:
app.wm_attributes("-transparent", "green")

[...]

time_selected_display = tkinter.Label(master = app, text = f'{timer_hours} Hours, {timer_minutes} Minutes, {timer_seconds} Seconds', font = ("Segoe UI Variable", 10), bg="green", fg="white")

[...]

time_display = tkinter.Label(master = app, text = f'{timer_hours} : {timer_minutes} : {timer_seconds}', font = ("Segoe UI Variable", 30), bg="green", fg="white")

to
bg_color = ttk.Style().lookup(".", "background")

app.wm_attributes("-transparent", bg_color)

[...]

time_selected_display = tkinter.Label(master = app, text = f'{timer_hours} Hours, {timer_minutes} Minutes, {timer_seconds} Seconds', font = ("Segoe UI Variable", 10), bg=bg_color, fg="white")

[...]

time_display = tkinter.Label(master = app, text = f'{timer_hours} : {timer_minutes} : {timer_seconds}', font = ("Segoe UI Variable", 30), bg=bg_color , fg="white")

so first query the background color of the window, which is defined in the theme, and then set it everywhere instead of the "green" background color. Obviously you also need some function to update these colors when the theme changes.
Actually I like the BlurWindow module, and for Tkinter it is the only way to blur the background of the window. But to do that you have to use the -transparentcolor option, which lets you click through the window, which is really frustrating to me. However I don't know, if this is a feature or a bug.

Thank you so much!


Remove version: REALiX.HWiNFO version 8.14

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

Close with reason: URL works;


.Net: Where is IVectorSearch?

This page states:
The VectorizedSearchAsync method allows searching using data that has already been vectorized.

This method takes a vector and an optional VectorSearchOptions class as input. This method is available on the following interfaces:

IVectorizedSearch<TRecord>
IVectorStoreRecordCollection<TKey, TRecord>
Note that IVectorStoreRecordCollection<TKey, TRecord> inherits from IVectorizedSearch<TRecord>.

And this unit test confirms that by grabbing IVectorSearch off the collection interface:
var collection = kernel.Services.GetRequiredService<IVectorStoreRecordCollection<ulong, TestRecord>>();
Assert.NotNull(collection);
Assert.IsType<QdrantVectorStoreRecordCollection<TestRecord>>(collection);
var vectorizedSearch = kernel.Services.GetRequiredService<IVectorizedSearch<TestRecord>>();

However, I'm using Microsoft.SemanticKernel.Connectors.Qdrant version 1.22.0-alpha and the reference is not resolved:

And the source does not show IVectorStoreRecordCollection inheriting from IVectorizedSearch:
[Experimental("SKEXP0001")]
#pragma warning disable CA1711 // Identifiers should not have incorrect suffix
public interface IVectorStoreRecordCollection<TKey, TRecord>
#pragma warning restore CA1711 // Identifiers should not have incorrect suffix
    where TKey : notnull
    where TRecord : class
{

Dupe of https://github.com/microsoft/semantic-kernel/issues/9141
Not sure why docs are released before the code is ready.

@lilhoser, the packages are now published and contains the new vector search capabilities. Apologies again for the delay and confusion.
Check out version 1.24.1 of any of the out of the box connectors, e.g.
https://www.nuget.org/packages/Microsoft.SemanticKernel.Connectors.InMemory/1.24.1-preview
https://www.nuget.org/packages/Microsoft.SemanticKernel.Connectors.AzureAISearch/1.24.1-preview
https://www.nuget.org/packages/Microsoft.SemanticKernel.Connectors.Redis/1.24.1-preview
etc.
Also, see here for a full list:
https://learn.microsoft.com/en-us/semantic-kernel/concepts/vector-store-connectors/out-of-the-box-connectors/
Note that the Pinecone connector is the only one that doesn't have VectorSearch implemented yet, as documented in limitations here, but this will follow soon.


Create a pick Recipes page, maybe as part of the Wiki

pick is really awesome, in less than a month it's become a great friend to me. It makes working with git branches and commits a lot easier, but maybe I wouldn't have thought to use it like that if I hadn't seen the gif in the README.
My point is that pick is a versatile tool whose possibilities aren't necessarily obvious at first. I think having a Wiki-style section for Recipes could bring in creative, cool use cases, and give new users more ideas of how to use pick.
I wrote a post about how I use it with git, I basically wrote some helper functions that wrap pick to make operations with branches and commits very fast.
This is the kind of stuff I think could go into Recipes, snippets of code using pick and gifs showing them in action. If this seems like a good idea I would love to contribute.

Hey @kylebebak, thanks for the feedback and for writing a great blog post!
Here's a similar post that @mike-burns and I wrote when we announced Pick on the thoughtbot blog: https://robots.thoughtbot.com/announcing-pick
I think a Recipes page or section in the Wiki is a great idea for collecting these in one place, and would love to review your contributions!
I'm not super-familiar with the Wiki feature of GitHub. Is it possible for you to propose changes to the Wiki in some way?

I'd also be interested in a package that I can install that gives me these recipes.

@calleerlandsson @mike-burns
I found a gist with a workflow that would allow you to Merge Wiki Changes From A Forked Github Repo
In short, there's no way for a contributor to make a pull request for changes that only affect the wiki. Instead, the contributor pushes changes to his fork of the wiki repo, a repo that depends of the main repo but is sort of separate from it. He then sends you guys a link to his fork of the wiki repo, you review the changes, pull them to your clone of the main wiki repo, and push them to the main repo.
Sort of cumbersome, but it looks like the only way for you to have control of what gets committed to the wiki. If this sounds OK, I'd be glad to propose an initial version of the recipes page like this.
P.S.
Right now, I think anyone can edit the wiki on GitHub. I just created a test page and then deleted it. But I can't push changes from my clone of the wiki repo to the remote wiki repo: Permission to thoughtbot/pick.wiki.git denied to kylebebak.
This page says by default only collaborators can edit the wiki, which is weird, because I had no problem creating the test page.

@kylebebak if you can just directly edit the wiki for thoughtbot/pick, that'd be best.

Can a file in this repository be used instead? This way all changes will
go through our usual PR-workflow.

Sure, that seems fine too. Even a PR against the README.md will be a great start.

@mike-burns @mptre
Sorry for disappearing, I'll get on this over the weekend and make a PR against the README. The wiki is just a glorified README anyway. It might also make sense to put the recipes in a separate file and link to it from the README, if you don't want the README getting cluttered. Let me know how you prefer it.
I can write a package wrapping the Git tools and make it installable via Homebrew. I don't know about distribution on Linux and Windows, but I could certainly learn =)
Thanks all!

I think a README section would be a great start. If it gets unwieldy, we can always extract it into a separate file later.
Thanks for working on this @kylebebak!

Hey guys, sorry for disappearing again...
I wanted to contribute something useful and @mike-burns got me thinking that a package for these tools would be better than just a recipes page, so I wrote pick-git.
It's a Python 2/3 package installable via pip that works on OSX and most flavors of Linux. The README gives a rundown of functionality and explains how to get it set up. I would be really happy if you guys tried it out for yourselves and told me what you think!
Again, sorry for taking so long to get back on this, and thanks for writing pick. I've been loving the the vertical scroll you added in 1.5 =)

Hey @kylebebak, I'm happy you've found a way to improve your workflow with pick!
I'm currently using gitsh for most of my git work but will try pick-git out when I get a chance.

Thanks @calleerlandsson for pointing me towards gitsh. It's much more general-purpose than pick-git, but I imagine pick-git would be a useful complement for tasks involving branches, commits, and files.
Thanks also for giving it a try when you have time, I look forward to getting some feedback. Cheers!