Relaes v1.13.1 announced but in the asset as download is still v1.13.0

As it says already in the title.
Relaes v1.13.1 announced but in the asset as download is still v1.13.0
if i download and install i still get informed that a newer version is available.

Oh no! I did it again. v1.13.1 is having version number v1.13.0. You can ignore by clicking "Ignore this version".

But i cannot make it work again .. i was hoping it needs version compatibility but my webos with newest developer mode v2.1.2 (released at 02.04.2024) is not responding to the webos dev manager. i tried telnet the port 9922 ant it seems a legit openssh is running. So from my network seems everything ok .. i didn't change anything, anyway.

also the installer has the exacply same size like the older 1.13.0 version .. does it really is only a forgetting to increment the version thing?

Hi,
Same issue for me, updated to 1.13.0 + developer mode 2.1.2 but cant uninstall/update youtube adfree for example, cant see my installed apps, etc

Hi,
Same issue for me, updated to 1.13.0 + developer mode 2.1.2 but cant uninstall/update youtube adfree for example, cant see my installed apps, etc

Same for me. As soon as I updated Dev Mode and this app, I'm unable to install apps. I can connect to the terminal using the prisoner username, and I can also see TV info like free space etc. It's just app installing that doesn't work anymore.

I have released v1.13.3. It should work now!


function term for "tRNA wobble position uridine thiolation"

http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0002143
There is no MF term for this activity, presumably because it is performed by multiple gene products (but is this a reason not to have an MF term?)
In E. coli, the first step of the reaction is reductive elimination of sulfur from L-cysteine by IscS cysteine desulfurase to form an enzyme-bound cysteine-persulfide intermediate. Then, five essential gene products, TusA, TusB, TusC, TusD and TusE, mediate a sulfur relay that delivers the terminal sulfur of persulfide from IscS to MnmA12. The last protein, MnmA catalyzes the transfer of the sulfur from IscS to an ATP activated U34 of the tRNA.
So which MF term would we use?  This seems similar to ubiquitination, and we have MF terms for these.....Presumably we should have MF terms for this pathway as its fairly well characterized....so its a shame to only have BP...

If the thiolation requires multiple steps, then the activities should be the mfs, but the term above would have to be a process. However, when I get back, I'll make sure there isn't a one-step activity out there.

I can't find any evidence for a single step activity that does this for wobble base thiol modifications.
This is because the thiolated products in the anticodon are complex: eg, mnm5s2U, mcm5s2U. Not like at position 8 or 9, for s4U, which is carried out by a single gene product.
See for example Table 1 in "Biosynthesis and Function of Modified Nucleosides (GR Bjork), in tRNA: Structure, Biosynthesis, and Function (eds: Soll and RajBhandar).

So which MF term describes this activity?

Will need some time to dig this out.
https://www.researchgate.net/figure/51610626_fig5_FIG-6-Uridine-modification-by-MnmE-MnmA-in-collaboration-with-other-proteins-carries
I seem to have lost my ability to attach a file here
see url
sothe steps involved in one type of final modification; the first step is S2U34, FIG. 6. Uridine modification by MnmE. MnmA (in collaboration with other proteins) carries out thiolation at the 2-position of the wobble uridine, whereas an ␣ 2 ␤ 2 heterotetrameric complex formed by MnmE and MnmG independently catalyzes the first step of the cmnm 5 modification at the 5-position. MnmC has two enzymatic activities that transform the cmnm 5 intermediate into the final mnm 5 modification in certain bacteria. (Adapted from reference 283 by permission of Oxford University Press.)

Now that I know the gene or a gene,found
a uridine34 in tRNA + a [TusE sulfur carrier protein]-S-sulfanylcysteine + ATP + a reduced electron acceptor → a 2-thiouridine34 in tRNA + a [TusE sulfur carrier protein]-L-cysteine + AMP + an oxidized electron acceptor + diphosphate + H+
If I don't find something in ec or metacyc, I'll need to create the term

From HumanCyc
TusE functions as a sulfur mediator during synthesis of 2-thiouridine of the modified wobble base mnm5s2U in tRNA. TusE directly interacts with both the TusBCD complex and the MnmA-tRNA complex, but not with tRNA itself [Ikeuchi06].
This is getting messy.
2-thiouridine formation in vitro is greatly enhanced in the presence of TusE. TusE is labeled by 35S sulfur during 2-thiouridine formation in vitro [Ikeuchi06].
A tusE deletion mutant lacks mnm5s2U, accumulates mnm5U and has a growth defect. The cysteine residue C108 is required for sulfur transfer [Ikeuchi06].

NTR: tRNA U34 thiolation activity
def: Catalysis of the reaction:  uridine34 in tRNA + a [TusE sulfur carrier protein]-S-sulfanylcysteine + ATP + a reduced electron acceptor → a 2-thiouridine34 in tRNA + a [TusE sulfur carrier protein]-L-cysteine + AMP + an oxidized electron acceptor + diphosphate + H+
Related Synonym: tRNA-specific 2-thiouridylase
Exact Synonym: tRNA U34 2-thiouridylase
PMID:16387657
PMID:12549933
is_a various terms already existing;

Hi Harold,
It seems that this term just needs to be added?
Val

I was going to make an ec request first, but THEN I read that this enzyme appears to be the last step, but I need to confirm this (that is, you don't find a U34thio-S by itself. )
Will sort out in a bit.

Ok, I thought I read something different, but PMID:12549933 has a figure that outlines the steps. So I'm putting this in now.

Done. GO:0106054, tRNA U34 thiol-transferase activity

hmm, is this the same thing?
https://www.yeastgenome.org/go/GO:0061708
at sgd this is
tRNA-specific 2-thiouridylase; responsible for 2-thiolation of the wobble base of mitochondrial tRNAs
and has
Gene Ontology Term: tRNA-5-taurinomethyluridine 2-sulfurtransferase
GO ID
GO:0061708
Aspect
Molecular Function
Description
Catalysis of 5-taurinomethyluridine in tRNA + a [protein]-S-sulfanylcysteine + ATP + a reduced electron acceptor = a 5-taurinomethyl-2-thiouridine in tRNA + a [protein]-L-cysteine + AMP + an oxidized electron acceptor + diphosphate + H+.
is taurinomethyluridine an alternative name?

not to self, I think I'm looking at ctu1/2 cyto and slm3 mito

Not that I know sfa about this stuff, but none of the structures in Harold's figure match the structure CHEBI has for 5-taurinomethyluridine
http://www.ebi.ac.uk/chebi/searchId.do?chebiId=CHEBI:87172

Hmm, I'm either looking at the wrong thing, or this is multifunctional....or is it some intermediate...
Harold, any ideas?

Well, I was just looking to make sure the thiolation occurred first.
The Def came from the gene entry for   MmnA that I saw on Metacyc (but didn't have a metacyc id).
5-taurinomethyluridine looks like a sufate derivative.
Note that the reaction I just added uses cysteine as a donor,
The product of the reaction that Val found is CHEBI:87171,  has BOTH a sulfate group (at 5) AND a thiol group at 2. Note the same reaction.

OK I'll look at the paper used at SGD to annotate this term. Thanks,

All clear from the abstract
https://www.yeastgenome.org/reference/S000080941


Improve LBS configuration guide of the Laird Sentrius RG1XX Gateway

Summary
Improve the LBS configuration of the Laird Sentrius RG1XX gateway with detailed LNS and CUPS configuration screenshots.
Changes

Added separate gateway configuration sections for the CUPS and LNS.

Checklist

[x] Scope: The referenced issue is addressed, there are no unrelated changes.
[x] Run Locally: Verified that the docs build using make server, posted screenshots, verified external links. Test with HUGO_PARAMS_SEARCH_ENABLED=true if style changes will affect the search bar.
[ ] New Features Marked: Documentation for new features is marked using the new-in-version shortcode, according to the guidelines in CONTRIBUTING.
[x] Style Guidelines: Documentation obeys style guidelines in CONTRIBUTING.
[x] Commits: Commit messages follow guidelines in CONTRIBUTING, there are no fixup commits left.

@nejraselimovic
The images were from the Laird product documentation. (page no: 15) Ref: https://www.lairdconnect.com/documentation/application-note-setting-basic-station-things-stack-v3
We don't have a laird physical gateways with us to add the original screenshots. Let us know if you have them we can add those into the PR.

@nejraselimovic
The images were from the Laird product documentation. (page no: 15) Ref: https://www.lairdconnect.com/documentation/application-note-setting-basic-station-things-stack-v3
We don't have a laird physical gateways with us to add the original screenshots. Let us know if you have them we can add those into the PR.

Ah, I see. No, unfortunately I don't have the gateway. Let's just leave it like this for now


GoBot breaks when calling Tensorflow

The GoBot example from tutrorial says at runtime:
2020-05-12 08:01:47.577 INFO in 'deeppavlov.core.data.simple_vocab'['simple_vocab'] at line 101: [saving vocabulary to /home/sgladkoff/Documents/MyWork/assistant_bot/word.dict]
WARNING:tensorflow:From /home/sgladkoff/Documents/MyWork/env/lib/python3.7/site-packages/deeppavlov/core/models/tf_model.py:37: The name tf.Session is deprecated. Please use tf.compat.v1.Session instead.
WARNING:tensorflow:From /home/sgladkoff/Documents/MyWork/env/lib/python3.7/site-packages/deeppavlov/core/models/tf_model.py:222: The name tf.placeholder is deprecated. Please use tf.compat.v1.placeholder instead.
WARNING:tensorflow:From /home/sgladkoff/Documents/MyWork/env/lib/python3.7/site-packages/deeppavlov/core/models/tf_model.py:222: The name tf.train.Optimizer is deprecated. Please use tf.compat.v1.train.Optimizer instead.
It looks like code in deeppavlov/core/models/tf_model.py does not correspond to current state of Tensorflow... Or am I doing smth wrong?

Hi @sgladkoff,
This is an expected behavior, there are no errors.
We do have plans on updating properly but no timeframe yet, as there is a lot of work involved.


feat: add stringify option

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing
[x] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:
Close #382

Like that?
function _fetch(...) {
//...
if (method[0] === 'P' && data)
      mergedOptions.body = passedInstanceOptions.stringify
        ? passedInstanceOptions.stringify(data)
        : JSON.stringify(data)
}

export interface OptionsRaw<R extends ResponseAsTypes = ResponseAsTypes>
  extends Omit<Options<R>, 'headers' | 'signal'> {
 //...
  stringify?: (data: any) => string
}

Thanks, I couldn't push so I merged locally


CompositeException -> getActivity().getApplicationContext() is null

When a CompositeException occurred then the getActivity().getApplicationContext() (in getContext() method on each Fragment) or getContext()(provided by support fragment) is null.
Not sure but I think it's related with this https://github.com/ReactiveX/RxAndroid/issues/21

Can you write down the steps to reproduce this?

@spirosoik I touched the code these days, so closing this issue until we can reproduce it.
We can reopen it later ok? :smiley:

Yes of course :+1: . I will send the steps also.


FR: No line between quote and math block option for Paragraph blank lines

Is Your Feature Request Related to a Problem? Please Describe.
I use similarly styled blockquotes and mathblocks so I can join them to give the mathblock a title. The Paragraph blank lines option is one I always use, but it frustrates me to no end when it adds a line between my math and quote blocks.
Describe the Solution You'd Like
Please add an option for this exception.
Thank you for your work!

before linting with Paragraph blank lines

after linting with Paragraph blank lines

I'd like the option for linting to not add the space shown in the second image. Also an option for not adding said blank line between a quote-1 and quote-2 would be nice.

Coukd you provide the source values (i.e. Markdown) instead of screenshits of the live preview mode? Thanks!

is this ok?

That works as a way I can copy over the source for testing.
You mentioned something about quote-1 and quote-2, but I don't see it in your example. If you don't mind explaining what a quote-# is, that would help as well.

A quote-# is a blockquote where the number of > is #. That is:

this is a quote-1

this is a quote-2

In the Shimmering Focus theme (and probably others), quote-2s following quote-1s (like above) are used to name the source of the quote, so it'd be nice if that could be added as an option as well.

Gotcha. I see what you mean now. I will see what can be done.

Given how much time has passed, I do not believe that this feature will be implemented. I believe that it makes sense to focus on other issues that have been reported and other feature requests with more users indicating their desire for them. As such, I will be closing this issue.
We can reconsider this at a later time if users do indeed want this specific feature.
Do note that ranged ignores were added and can probably be used to handle this. Do note that it will turn off all Linter rules for the contents inside the ranged ignores. But it could allow for this effect. You could also use custom regex replacements if you are so inclined.


Improve search function to filter/segment

This relates to #107, but I also want to filter by responses that are multiple choice questions. Examples:
What is the device you use the most often to connect to the Internet?
&
What is the primary way you connect to the Internet?
This will need to take in account that we changed forms throughout the last two years from a drop-down menu question to a multiple-choice question. Language might have also been changed in the answer options.

Initial version added with commit https://github.com/smartchicago/kimball/commit/28e6ea19e87a98d6634d2334a5a8df220726bd22
for device type and connection type
@smarziano On staging. Right now there is just one device/connection type filter and then it checks both primary and secondary. (This is how the Device Description and Connection Description searches were set up.) I can switch it to only search primary or however you want.

I also updated tags to pre-populate list of tags and made it multiselect

Initial thoughts:

It looks a bit bulky right now because it shows all of the responses instead of having a drop-down menu option.
It would be good to have an option to let it search for only primary OR both primary and secondary
I am unable to deselect an option once it has been selected

Regarding bulkiness: I understand that this allows for selecting multiple options. It would be ideal still to have a way to select multiple options from a drop-down. At this time it is sufficient, but @shua123 please keep investigating. I worry specifically about the Tags list getting too long.
Re: deselecting: We figured out the workaround to select Control/Command + Click at this time. Might be good to add to "Search tips"
Tiers of searching:
First column should be about the person -- Name, email address, zip code, Tags can also fit here
Second column should be about device type & connection type & preferred contact method
Third column should relate to descriptions
Things that are not as important or frequently searched:

Verified?
Form submission content
Event (this will become less of a priority on the search page when we work on other enhancements, see #95)
Ward (this is outdated)

I have reordered the search options based on the above comment. The not important ones are in a div that starts out hidden. https://github.com/smartchicago/kimball/commit/154681e985b455abeff39e7bdf791d91fe0f0bef

@shua123 Address field can be added to the not frequently searched list.
Right now we also have "Show advanced search" from the old version, which can be removed. New "Click to Show Additional Options" can be put in that place and renamed to "Show additional options."

Make "Show Addtional Options" a button

"Show Additional Options" is now a button https://github.com/smartchicago/kimball/commit/342e651c738caba28eedde5c548bdabfecec6ca9

This works for our current needs. Closing issue.


Debugger: Disconnect/Terminate button gets stuck on one option when overriding Option Key

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.83.1 (Universal)
OS Version: MacOS Sonoma 14.0

I have the debug kill button set to Terminate by default. Holding down the option button temporarily changes the button to Disconnect.
I also use a popular Alt+Tab software (https://alt-tab-macos.netlify.app) to create a shortcut (option+tab) to switch between windows. Upon holding down the Option key (switches to Disconnect), clicking the Tab key switches my active window.
However, VSCode Debugger toolbar gets stuck on Disconnect mode until I hit and release the Option key to bring it back to Terminate.
https://github.com/microsoft/vscode/assets/30972202/9f8cb5b9-61bd-4b13-a730-74e08fa4e605

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

I also use AltTab and I haven't seen this happen


Error with 10.2.5

1x ColorPickerPlus/ColorPickerPlus.lua:325: attempt to index global 'ColorPickerWheel' (a nil value)
[string "@ColorPickerPlus/ColorPickerPlus.lua"]:325: in function CleanUpColorPickerFrame' [string "@ColorPickerPlus/ColorPickerPlus.lua"]:1109: in function Initialize_UI'
[string "@ColorPickerPlus/ColorPickerPlus.lua"]:1137: in function `?'
[string "@ColorPickerPlus/ColorPickerPlus.lua"]:137: in function <ColorPickerPlus/ColorPickerPlus.lua:137>
Locals:
self =  {
CreateClassPalette =  defined @ColorPickerPlus/ColorPickerPlus.lua:613
CreateCheckerboardBG =  defined @ColorPickerPlus/ColorPickerPlus.lua:374
CreateOpacityBar =  defined @ColorPickerPlus/ColorPickerPlus.lua:920
ShowHideAlpha =  defined @ColorPickerPlus/ColorPickerPlus.lua:291
CleanUpColorPickerFrame =  defined @ColorPickerPlus/ColorPickerPlus.lua:322
Initialize_UI =  defined @ColorPickerPlus/ColorPickerPlus.lua:1108
UpdateOldColor =  defined @ColorPickerPlus/ColorPickerPlus.lua:222
CreateHelpFrame =  defined @ColorPickerPlus/ColorPickerPlus.lua:1051
UpdateOpacityBarThumb =  defined @ColorPickerPlus/ColorPickerPlus.lua:260
CreateTextBoxes =  defined @ColorPickerPlus/ColorPickerPlus.lua:950
UpdateHexText =  defined @ColorPickerPlus/ColorPickerPlus.lua:1264
CreateColorGradient =  defined @ColorPickerPlus/ColorPickerPlus.lua:731
Hooked_OnShow =  defined @ColorPickerPlus/ColorPickerPlus.lua:308
UpdateAlphaText =  defined @ColorPickerPlus/ColorPickerPlus.lua:1288
UpdateHSVfromColorPickerRGB =  defined @ColorPickerPlus/ColorPickerPlus.lua:194
PLAYER_LOGIN =  defined @ColorPickerPlus/ColorPickerPlus.lua:1135
UpdateRGBTexts =  defined @ColorPickerPlus/ColorPickerPlus.lua:1252
UpdateChosenColor =  defined @ColorPickerPlus/ColorPickerPlus.lua:216
UpdateColorTexts =  defined @ColorPickerPlus/ColorPickerPlus.lua:1234
CreatePalette =  defined @ColorPickerPlus/ColorPickerPlus.lua:555
UpdateHueBarThumb =  defined @ColorPickerPlus/ColorPickerPlus.lua:267
CreateColorSwatches =  defined @ColorPickerPlus/ColorPickerPlus.lua:415
SetRGBfromHSV =  defined @ColorPickerPlus/ColorPickerPlus.lua:197
CreatePaletteSwitcher =  defined @ColorPickerPlus/ColorPickerPlus.lua:1093
UpdateHSVTexts =  defined @ColorPickerPlus/ColorPickerPlus.lua:1240
GetAlpha =  defined @ColorPickerPlus/ColorPickerPlus.lua:201
CreatePaletteFrame =  defined @ColorPickerPlus/ColorPickerPlus.lua:1068
ADDON_LOADED =  defined @ColorPickerPlus/ColorPickerPlus.lua:226
UpdateColorGraphics =  defined @ColorPickerPlus/ColorPickerPlus.lua:274
CreateCopyPasteArea =  defined @ColorPickerPlus/ColorPickerPlus.lua:446
UpdateGradientColorOverlay =  defined @ColorPickerPlus/ColorPickerPlus.lua:211
UpdateGradientThumb =  defined @ColorPickerPlus/ColorPickerPlus.lua:245
HexTextChanged =  defined @ColorPickerPlus/ColorPickerPlus.lua:1176
RGBTextChanged =  defined @ColorPickerPlus/ColorPickerPlus.lua:1141
CreateHueBar =  defined @ColorPickerPlus/ColorPickerPlus.lua:827
AlphaTextChanged =  defined @ColorPickerPlus/ColorPickerPlus.lua:1274
HSVTextChanged =  defined @ColorPickerPlus/ColorPickerPlus.lua:1200
}
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = "attempt to index global 'ColorPickerWheel' (a nil value)"
isClassic = false
isWrath = false
dialogHeight = 380

Hey, i commented my fix on CurseForge, this is more meant for the author if he is busy and wants one solution to the errors.

Hello, on todays patch they did some changes to various stuff, i overwrote my export code so i cant see the previous version for the ColorPickerFrame but managed to get it to work.
They renamed OpacitySliderFrame to OpacityFrameSlider, replacing all instances of this worked.
Seems like they changed the organization of the frame, earlier it was ColorPickerFrame:SetColorRGB but it is now ColorPickerFrame.Content.ColorPicker:SetColorRGB, replacing all instances of this worked.
In your function CleanUpColorPickerFrame you are hiding several frames, since their reorganization the names are changed so i simply commented out all of those except for OpacityFrameSlider, instead added
local ColorPickerFrame = ColorPickerFrame
ColorPickerFrame:HookScript("OnShow",
 function ()
	ColorPickerFrame.Content.ColorPicker.Alpha:Hide();
	ColorPickerFrame.Content.ColorPicker.AlphaThumb:Hide();
	ColorPickerFrame.Content.AlphaBackground:Hide();
	ColorPickerFrame.Content.ColorPicker:Hide()
	ColorPickerFrame.Content.HexBox:Hide()
	ColorPickerFrame.Content.ColorSwatchOriginal:Hide()
	ColorPickerFrame.Content.ColorSwatchCurrent:Hide()
 end
)

It works, dont know if this is a bad way to solve it though, i couldnt do it like you did since blizz now seems to call Show each time the main window shows.
After calling SetColorRGB you seem to call ColorPickerFrame.func, since i dont have the previous version i dont know what function this is, i found ColorPickerFrame.swatchFunc which i guess is the renamed function. However in blizz documentation they comment that "SetColorRGB must be called last since it triggers swatchFunc", so simply commenting out all instances of ColorPickerFrame.func in your addon fixed that issue, i guess in the previous version SetColorRGB didnt call func.
And with those changes the addon seems to be working again, cheers!

Is there an update? I don't see anything on CurseForge yet>


athena-tu-darmstadt-exercise:0.1.0

I am submitting

[x] a new package
[ ] an update for a package

Description: This is an unofficial exercise template for the University TU Darmstadt (Technische Universität Darmstadt) following the design guidelines and imitating the official LaTeX template.

I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Please note that the current image in the README does not match the provided image in the preview folder. The reason for this is that the image in the README points to the image file within the repository. However once this template is ready to get submitted this PR will get merged and change the image to the current version. If this is not wanted I can change the README to use the image in preview.

It's fine to have the images in the README reference the original repository I think.
As for the template not compiling however, this will need to be fixed, we want to guarantee that all projects created from templates compile. What you can do is have a fake logo, such as an image that just says "replace me".

I added a replacement image. The only failing tests now are kebab casing. However we are currently not planing to change the casing. If that is problematic please let us know.

No it is not mandatory to use kebab-case, it is just the most common convention for Typst packages and we try to encourage it, but it is up to each package author to decide how they want to name their functions.
Thank you for adding the placeholder logo.


VNC docs

needs to be added

Waiting for changes to VNC

Waiting for changes to VNC

added but needs testing

Tested with Preview 4


#3884 Update root's updated_by anytime any node in the tree is updated

This is so that when we display a list of keys by root nodes, the updated_last data in the root reflects the entire tree. (Of course this means now you won't always know when the metadata of a key was last updated.)
A couple notes on the location of the new callbacks:

self.root is undefined in after_destroy and even in before_destroy if before_destroy is placed after the has_closure_tree declaration (suggesting whatever clears root on self happens in has_closure_tree's before_destroy).

self.root is undefined in after_save and all tests fail (on creating leads) unless after_save is placed after has_closure_tree (suggesting that root is set on a lead in has_closure_tree's after_save).

Sorry, I should have chimed in on this earlier.

No problem.

there are no cascading updates like this intended

I'm fine with making the changes, but just to make sure I'm thinking of this right: that will make displaying a list of all keys with housekeeping info considerably more expensive, right? We'll have to query every lead node in the database every time.
Paging would help, but not in the case of the Recent updates list at /leads/, where again we'd need to query every lead node in the database to figure out the n most recently edited leads.
Also there will be no record of an update if a couplet was deleted from a key.
Does that sound okay, or any other thoughts?

that will make displaying a list of all keys with housekeeping info considerably more expensive, right? We'll have to query every lead node in the database every time.

Yes and no.   p.root_taxon_name.self_and_descendants.maximum(:updated_at) is 1/2 second for > 84k descendants, our keys will not be anywhere close to that size.

Also there will be no record of an update if a couplet was deleted from a key.

Understood.  If we want to capture this we'll want to add a new attribute on Lead.  This brings in the concept of Versioning etc., which is good to think about, but I'm personally not super concerned about it at the moment, and if we do want to introduce this concept I'd like to do it with a generalized approach/concern that could be re-used.


Feat: Make beforeSend async

:scroll: Description

:bulb: Motivation and Context
https://github.com/getsentry/sentry-dart/issues/459
:green_heart: How did you test it?
:pencil: Checklist

[x] I reviewed submitted code
[ ] I added tests to verify changes
[ ] I updated the docs if needed
[x] All tests passing
[ ] No breaking changes

:crystal_ball: Next steps

Codecov Report

Merging #494 (ee8c7a3) into main (6873600) will increase coverage by 2.34%.
The diff coverage is n/a.

:exclamation: Current head ee8c7a3 differs from pull request most recent head 23d89fe. Consider uploading reports for the commit 23d89fe to get more accurate results

@@            Coverage Diff             @@
##             main     #494      +/-   ##
==========================================
+ Coverage   91.24%   93.58%   +2.34%
==========================================
  Files          63        5      -58
  Lines        2091      156    -1935
==========================================
- Hits         1908      146    -1762
+ Misses        183       10     -173

Impacted Files
Coverage Δ

dart/lib/src/sentry_envelope_item_header.dart

dart/lib/src/transport/rate_limit.dart

dart/lib/src/platform/platform.dart

dart/lib/src/hub_adapter.dart

dart/lib/src/scope.dart

dart/lib/src/protocol/sentry_event.dart

dart/lib/src/protocol/sentry_level.dart

dart/lib/src/diagnostic_logger.dart

dart/lib/src/throwable_mechanism.dart

dart/lib/src/protocol/sentry_stack_frame.dart

... and 46 more

Continue to review full report at Codecov.

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


Fix issues in rstudioapi emulation

Resolves the issues discussed in #421:

If an addins.dcf file from a package is malformed it could cause an error when trying to write the JSON to drive the addin picker. This error could cause the vsc.attach function to fail to run fully. This was not very common. I found only one example in {shrcts}.

I added extra checks to look for malformed files, and to only select the first few columns, assuming those contain the information I want to display. The whole update_addins_registry call is wrapped in a try-catch so that if it throws an error it is converted to a message about the failure and the consequences. vsc.attach will complete otherwise normally.

On Windows library(tidyverse) fails due to the cli package trying to interrogate the version of RStudio if it is available. I have put in implementations for getVersion and versionInfo that should allow this to work in the short term.

The plan is to discuss this with RStudio to see if we can get something less fragile.
Finally, to use the RStudio API emulation the user must set options(vsc.rstudioapi = TRUE) in the .Rprofile. I have put documentation about this in the README and will add it to the wiki.
Sorry for the hassles!

@Ikuyadeu We might need a release once this PR is merged and notice users that options(vsc.rstudioapi = TRUE) should be used to enable rstudioapi emulation in the changelog.
When the feature become more stable, then we could make it TRUE by default.

Maybe off the topic but https://github.com/Ikuyadeu/vscode-R/blob/master/src/rstudioapi.ts#L306 could be removed.

Still not sure if this is working properly on Windows. I just tried to install the vsix and I am getting issues. Not sure if I installed the right thing.

Oh yeah looks like I installed an old one. Let me confirm.

No. I'm seeing something very strange.
Using the vsix file built by the CI:

On Linux, no issues.
On my Windows work computer:

[ins] r$> .vsc.attach()
Error in .vsc.attach() : object 'rstudioapi_util_env' not found

Which is totally weird, since I can do:
[ins] r$> vsc_attach_env <- environment(.vsc.attach)

[ins] r$> vsc_attach_env$rstudioapi_enabled()
[1] TRUE

But if no rstudioapi stuff is in that environment, and no lockfiles etc created on in tmp folder.
It's really spinning me out.

OK OK OK. I got it. It was an issue with my .Rprofile which had some old stuff in there, manually sourcing init.R.
ALL GOOD. 😌

I tried the latest commit on macOS and Windows 10 VM and everything looks good so far.

Error in .vsc.attach() : object 'rstudioapi_util_env' not found
I got it. It was an issue with my .Rprofile which had some old stuff in there, manually sourcing init.R.

@MilesMcBain, I have the same error message on my Ubuntu.
could you explain in more detail, how you solve this problem?

@almaceleste .vsc.attach() is called at the end of an init.R script that runs when an R terminal is created. I was getting this error because I had call to vsc.attatch() in my .Rprofile, which I think was a hangover from an old way that the extension used to work.
Check for any calls to this function in any of your session startup code and remove.

@MilesMcBain, I have no vsc.attach() in my .Rprofile, only this code:
source(
    file.path(
        Sys.getenv(
            if (.Platform$OS.type == "windows") "USERPROFILE" else "HOME"
        ), ".vscode-R", "init.R"
    )
)
options(vsc.rstudioapi = TRUE)

@almaceleste options(vsc.rstudioapi = TRUE) should run before source(), or otherwise it won't work.

@renkun-ken, thanx, it helps me.
now I do not get errors when running Create R terminal and Launch RStudio Addin commands, and I get RStudio Addins list successfully.
I think this should be described more obviously in the instruction and in the wiki

@almaceleste Good to know it works for you now.

I think this should be described more obviously in the instruction and in the wiki

Definitely. @MilesMcBain Would you mind updating docs so that users know how to enable it exactly? (e.g. https://github.com/Ikuyadeu/vscode-R/pull/422#issuecomment-723541397 won't work)

I added a bit extra to the wiki: https://github.com/Ikuyadeu/vscode-R/wiki/RStudio-addin-support#enabling-rstudio-addin-support


[IA-2538] Release Galaxy to all skins

https://broadworkbench.atlassian.net/browse/IA-2538
Blog, docs, etc are set to go out today. I think this is the only UI change needed.
Tested locally

tried locally...can verify create galaxy button shows up in notebooks tab

PO has approved this, btw


NTR:cytosol to ERGIC protein transport

Hello,
I was wondering if we could create a new GO term describing "cytosol to ERGIC protein transport" based on the following
source: PMID:30374053; UniProt: TMED10 (P49755)
It would show that TMED10 acts as a channel transporting leaderless proteins from the cytosol to the lumen of the ERGIC.
Thank you,
Lucille

suggested def wording
suggested parent?

Can you use a pattern similar to GO:0043001 Golgi to plasma membrane protein transport?  Def = The directed movement of proteins from the Golgi to the plasma membrane in transport vesicles that move from the trans-Golgi network to the plasma membrane.
I think the parent could be 'GO:0015031 protein transport' - I dont find a more specific term.
Thanks, Pascale

It's odd  (but interesting) if this is a channel ,  because I was under the  impression the intermediate compartment was vesicles moving between the ER and the Golgi...
TMED10 is a vesicle coat protein?
It's  erv25 in yeast, there is quite a large family, they are all coat proteins:
https://www.pombase.org/gene_subset/interpro:IPR015720
Is it acting as a 'channel' or a 'cargo receptor"?

Can you use a pattern similar to GO:0043001 Golgi to plasma membrane protein transport?

That was my textbook view, that proteins are contranslationally placed in the ER membrane or ER lumen and then travel via the ERGIC to the Golgi and then to the cell surface or extracellular space. But this term request is for a function that enables an initially cytosolic protein to enter the ERGIC, which is definitely not textbook.

I remember been told many years ago by John Armstrong  that proteins could get into the ER but not via the translocon, but the mechanism was not known

I can't find TMED10 in this paper?

I made a comment about ignoring the TMED10 as any part of the def, but I think I put it in the wrong ticket. Need more coffee.

Ah, found it
The 'UniProt: TMED10 (P49755)' would not be used in the def anyways; the PMID is ok and enough.
What is the purpose of this? Is it because you want to annotate the new term to this protein?

This paper doesn't appear to be about  ERGIC though?

I just did a full scan of paper; the words ER, endoplasmic reticulum do not appear.
This is same paper used for the other ticket on ERGIC
@LucillePo  can you check if the PMID is valid?

Sorry i was referring to this paper PMID:32272059

It's odd (but interesting) if this is a channel , because I was under the impression the intermediate compartment was vesicles moving between the ER and the Golgi...
TMED10 is a vesicle coat protein?
It's erv25 in yeast, there is quite a large family, they are all coat proteins:
https://www.pombase.org/gene_subset/interpro:IPR015720
Is it acting as a 'channel' or a 'cargo receptor"?

It seems to have two dinstinc functions: 1) one as a cargo receptor (well characterized) and 2) a new function as channel transporting cytosolic proteins (here leaderless proteins) within the lumen of the ERGIC

Now that have correct reference, are we good to go with this?

yes, go ahead

+id: GO:0106273
+name: cytosol to ERGIC protein transport


Deprecate the Elmah SQLErrorLog

Remove the Elmah SQLError Log. There is the Azure Storage error log.

This is used in the local debugging workflow, cannot be deleted unless it is replaced.


[enhancement]: Support for JAX &  Google TPUs

Is there an existing issue for this?

[x] I have searched the existing issues

Contact Details
No response
What should this feature add?
Kaggle offers 20 hours of free TPU use, which greatly speeds up image creation (6 sec for 8 images). Huggingface diffusers already offer JAX implementation in their models. I checked their repo and don't think the implementation difficulty of this is high. A matter of changing a few API calls.
Is there any interest in incorporating this into the main branch? I'd be willing to give it a try myself.
Details can be found here:
https://huggingface.co/blog/stable_diffusion_jax
Alternatives
No response
Aditional Content
No response

Your offer of help is gladly accepted. Do you need any pointers? We are currently in a transition between ckpt models and diffusers models. Please confine any changes to the diffusers part of the code, as the ckpt part is going to be deprecated and removed.

Great, I'll dive into the code and see what I can come up with. If you have any tips or recommendations, please let me know. I envision a simple setting in options where you can switch between TPU and GPU.

At the moment, we have our own subclass of the diffusers pytorch StableDiffusionPipeline: https://github.com/invoke-ai/InvokeAI/blob/371edc993a36e00bc6f5a3598ee5c83cc65b509f/ldm/invoke/generator/diffusers_pipeline.py#L237
and there are a bunch of methods on it. It will take some refactoring to move them to be less dependent on subclassing so it's easier to switch out that pipeline class, but that's not an insurmountable task by itself.
But that only gets you partway there. It might be enough to use other pytorch-based diffusers pipelines, but there is significant use of pytorch in the InvokeAI code, both in the implementations of those subclass methods and elsewhere.
Some of the code, like the stuff that uses the CLIP text encoder, the easiest way would be to leave it in pytorch and run it on CPU, because it's not so computationally expensive.
Other stuff like the cross-attention controls you'll need to come up with a JAX implementation for.
I don't have anything against JAX personally, but I fear maintaining both JAX and PyTorch pipelines in one project would be biting off more than we can chew.
There is another option: While the current diffusers TPU-compatible pipelines are written with Flax, Flax (and JAX) are not the only way to run something on a TPU. You could also investigate using torch_xla to keep the code based on pytorch and execute it on a TPU device.

Thanks for your comment. Looking through the code, I realize I've underestimated the effort it would take. Although it's nice to have, I agree it's probably too much effort to maintain for such a niche use case. I'll look into the torch xla option, but I suspect it's too much of an undertaking for me right now to implement.
Feel free to close this ticket if you don't want it clogging up your backlog, I can always reopen it later.


No filters list in Apigility Admin

No filters list for fields in apigility admin, angular error you can see the screen:

Guys, I have the same problem. Any solution?

This repository has been closed and moved to laminas-api-tools/api-tools; a new issue has been opened at https://github.com/laminas-api-tools/api-tools/issues/34.


BakeChain  The connection to '<IP_ADDRESS>' failed

Hi there,
My app shows pretty much all parameters "0" and when I checked Fiddler I saw the message below. Is it normal behaviour?

[Fiddler] The connection to '<IP_ADDRESS>' failed.
Error: ConnectionRefused (0x274d).
System.Net.Sockets.SocketException No connection could be made because the target machine actively refused it <IP_ADDRESS>:8338

I see this too... after upgrading to .3, the current level and current cycle entries are 0.  This concerns me

Is it affected baking?

I don't know, yet... I only have 1 roll, I have an endorsement scheduled in 16 hr, so I'm curious to see if it misses it while running this version

Oh...I'll start baking in cycle 12.... please post if yours do not work and maybe I roll back to the previous version 0.2.0

will do

Looks like newly released version .4 fixed it!  Thanks Stephen!

We have this problem again :(

Yes, it was working fine until I closed bakechain to reboot my computer... when I turned it back on the Current Cycle and Current Level both read 0.  However, I still received endorsements in this condition.  And just this morning, it gave the "low balance" issue again.  Is the network being attacked again?

Fixed, Thanks!


Connection of LoRa SX1278 433Mhz v1.0 with a Raspberry Pi 4 model B to send data to a gateway using ChirpStack ?

How does one connect LoRa SX1278 433Mhz v1.0 with a Raspberry Pi 4 model B to send data to a gateway using ChirpStack checked out and realized the Gateway Name called AdemneaGW has a Gateway Profile: RAK7249 WisGate Edge Max Gateway? I'll be glad for a positive response, thank you.

I've seen that you have posted the same question on the forum (forum.chirpstack.io) already. That is a better place for such questions than GitHub issues (which is intended for feature and bug reports).


Added a QFT tutorial to Quantum Information tutorials.

Included link in index.ipynb and circuit image in images/
Made sure that MathJax rendered properly in GitHub.

Hi @attp i will merge this but when we have the circuit plotter we should edit this and remove the png and have the tutorial make the circuit.


experiment: enum => object

Resolves #301.

Hey @CodyJasonBennett
thanks for the fix,
interesting why it didn't create new version of the package? https://github.com/pmndrs/three-stdlib/actions/runs/6409130873/job/17399718921#step:7:50

I didn't tag it right for semver. Can put it through now.


Add a Gitter chat badge to README.md

loklak/loklak_webclient now has a Chat Room on Gitter
@sudheesh001 has just created a chat room. You can visit it here: https://gitter.im/loklak/loklak_webclient.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Closing this. False Alarm


Logic App Consumption Export error

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.77.3
OS Version: 13.2.1 (22D68)

When trying to export Logic App (consumption)
Error message: "createChild" is not implemented on  "m".
Source: Azure Logic Apps (Consumption) (Extension)

/causedByExtension

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!


[Production & Staging] Dragging project or component in Dashboard to ineligible row causes highlight to persist

Steps

Go to osf.io.
Go to your Dashboard.
Click the row of one of your projects or components.
Drag and drop to the "All my projects" row.
Click any other row.

Expected behavior
I expected that dragging and dropping a project or component around to any row (other than a collection) would cause the highlight on that other row to disappear.
Actual behavior
When I drag a project into the "All my projects" row, a light blue highlight stays over that row even when I click another row. (You can replicate this effect in more ways as well).
Projects and components can only be dragged successfully into a collection, which will flash a green highlight.

I just replicated the issue.  Can I grab this one? Thanks :)

:+1:


Create new Minutes directly from within latest finalized Minutes

Hi all,
I often run into the issue that I have opened the latest meeting minutes which is already finalized. So I am not able to add information (e.g. when I worked on an action item and I would like to note down the result as a new detail item of the action item).
To be able to do this, I have to go to the minutes overview and create a new minutes there (which of course is not much effort but somehow annoys me).
It would be nice to have the possibility to create the next meeting minutes directly in the latest finalized meeting minutes.
This would also be helpful when you just finalized the minutes and you want to set up the next minutes right away.
As a suggestion, you might have at the top of the minutes beside the “Previous” link also the “Next” link (like for previous minutes) which does not show a date (because there is none yet :-)) but something like “create new minutes”. Clicking on this link shall then work in the same way as the button in the meeting minutes overview.
Best regards, Christoph

I would change 5 a little bit. After creating new minutes, I would like to have this new minutes opened directly to be able to edit it immediately.

I would agree with @fd0cwp - we should jump to new minutes on acceptance criteria#5.
And I would add acceptance criteria #6:

After click on "Create New Minutes" on the minutes view (only!) a security question "Do you really want to create new minutes?" [Yes/No] should prevent the user from accicently create new minutes.
Rationale: When user navigates a longer sequece of minutes just by clicking the "Next: YYYY-MM-DD" link multiple times, on the last minutes this link surprisingly changes to "Create New Minutes". So it may happen that the user creates the new minutes without intention. Security question shall prohibit this.

Unfortunately, the solution merged with PR #520 doesn't work anymore as expected. The link "Create New Minutes" exists on the minutesedit page of the latest minutes. If you click this link a new minutes will be created but the open topics won't be copied 😕

I cannot explain why this bug didn't appear when developing this feature 🤷♂ but I can explain the cause: When creating new minutes we collect the topics associated with the meeting series from the topics collection. On the meetingSeriesDetails-Template we have an active subscription on this collection which we don't have on the minutesedit-Template.
A quick fix could be adding the line this.subscribe('topics', meetingSeriesId); when doing the subscription on the  minutesedit-Template:
https://github.com/4minitz/4minitz/blob/8de5a8c9cbf9994dc13b9c469cfc6c3a56a8150e/client/templates/minutes/minutesedit.js#L161
I am not sure if it is a good idea to prepare the new minutes on the client side 🤔
What do you think @derwok

I opened two PRs:

#545 Added a subscription to the topics collection from the minutesedit template
#546 Moved the topics preparation for new minutes within the meteor method

Both solves the issue mentioned in my last comment. @derwok & @migerh which solution do you prefer?

... was more complicated than expected....  :-)
Thx Felix!


Translated and fixed libraries page in hi.yml

Fixes #656
Changes:
Added Hindi translations for libraries page in hi.yml file.

@shaharyar-shamshi @montoyamoraga Please review this PR.

@ayushjainrksh @montoyamoraga it look perfect to me and good to be merged


Feature request: Add support for Oracle Container Registry automatic authentication

I'd like to authenticate automatically to Oracle Container Registry using something similar to:
https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contenggrantingworkloadaccesstoresources.htm

To implement auth for Oracle, we'll need some org to sponsor the Flux project so we can run e2e tests and provision clusters and registry repos in Oracle Cloud. The workload id code to access container registries is here https://github.com/fluxcd/pkg/tree/main/oci/auth. The oci/auth package is used by the Flux CLI, source-controller and image-reflector-controller, if we are going to support Oracle IAM, we'll need to integrate it with all Flux components.


Unit & Integration Tests

Motivation
We'd like to have comprehensive unit and integration tests so we can rely on automated testing when making changes.
Acceptance Criteria

Unit tests are written for units providing function and logic.
Integration tests are written for all scenarios/use cases that Janet covers.

Out of scope

CI, as it does not exist (yet)

sequenceDiagram

actor Alice
actor Bob

Alice ->> Bob: Hello


Add Pixel History columns for dual source output and blend src/dest on Vulkan

Description
This PR adds new columns to the pixel history view for the dual source output on shaders, and also for the blend source and destination factors. It also allows enabling the pre-mod value as an extra column, since there's a chance it could be useful. All of these extra columns are hidden by default, and can be accessed by right-clicking anywhere in the pixel history view and then editing the columns.
It also fixes a few minor bugs and typos with pixel history, including the buffer not being large enough if you have a large quantity of primitives hitting the same pixel within a single drawcall. Now, up to 255 are handled correctly (at which point the scissor-based approach stops letting us distinguish pixels), and more than 255 will show the first 255 without crashing.
I also added demos and automated tests for these features.
This PR only implements it for Vulkan. On other APIs, the columns will show as "Unavailable" (it probably would be possible to implement it, but I imagine trying to modify shaders textually for OpenGL would be a massive pain, and I don't know enough about D3D to do it there). Additionally, if blending is disabled or if dual source blend is disabled, the relevant data will not be collected and the columns will show as "Unavailable" (so this change should not have any impact on performance if blending or dual source blend is not in use).
Resolves #2461.

I'm not going to give this a detailed review as the PR itself is too large for the moment - see the contributing guidelines - please split up the PR further as 1000 lines changed should be an absolute maximum. For example you could separate PR the core implementation and testing, and you could further split the core implementation up into separate logical PRs as possible to reduce the amount of code to be reviewed - aim for only a few 100 lines changed at once when the PR is complex. Aside from that I think there are some high level things that should change and a detailed review would be redundant.
Implementing fetch of dual source blending data is good, but I do not want to add any new columns for it. The only thing this change should do is obtain the dual source second factor (when referenced) and it can display that data with the rest of the shader output. The vastly overwhelming number of cases using dual source blending will only use an additional alpha, so this should be added to the shader out as "A2: x.yyy" after the existing R/G/B/A. If someone is actually using a dual source colour blend factor you could add "R2: x.yyy, G2: x.yyy, B2: x.yyy" in the shader output as well.
Since we know that dual source blending is only used with a single render target, it makes most sense to display it directly with the shader output as-if there were 5 components output instead of 4.
I agree that supporting this on GL is not feasible due to the need to patch shaders, but this should be very easily supportable on D3D11 since D3D doesn't use the somewhat obtuse 'index' system of GL/VK, and just sources dual source blending information from the second render target. No shader patching is needed in that case. If you want to have another look at it in that case that would be appreciated, but if you don't want to touch the D3D11 code at all I can do a follow on fix.
Similarly looking briefly at the shader patching for vulkan I think your approach is more complex than is needed - I think the simpler approach would just be to patch any location = 0, index = 1 outputs to location = 1 when fetching shader output values and bind two render targets to obtain both outputs. Having a system of swapping between index=1 and index=0 makes things more complicated than necessary especially with what you've found regarding needing to handle annotations being missing on index=0.

I'm not going to give this a detailed review as the PR itself is too large for the moment - see the contributing guidelines - please split up the PR further as 1000 lines changed should be an absolute maximum. For example you could separate PR the core implementation and testing, and you could further split the core implementation up into separate logical PRs as possible to reduce the amount of code to be reviewed - aim for only a few 100 lines changed at once when the PR is complex.

The commits are generally targeted at one of API (data_types.h), Vulkan implementation, UI, or Vulkan testing (I think all of them are exclusively one of these but I'd need to double-check), Everything depends on the interface, and Vulkan testing depends on the implementation for the tests to pass (but could still compile on its own). So I could create 4 PRs, one for the API on its own, and 3 containing the API commits and then the other commits. Or do you want something else?

but I do not want to add any new columns for it

Do you have an opinion on adding columns in general? In particular, this PR also adds optional columns for the blend source factor and the blend dest factor. Theoretically this could be a separate change (and I have everything related to that in separate commits already, apart from the python test for dual source blending which also checks that info). I could create separate PRs for that feature as well, but then it would be even more PRs with somewhat convoluted interdependencies. I'm a bit worried about making it hard to review because of that (and having to deal with updating several PRs to account for a change to one of them).

The only thing this change should do is obtain the dual source second factor (when referenced) and it can display that data with the rest of the shader output.

The downside of doing this is that you can't see the color itself visually, but on the other hand the main alpha value isn't displayed visually either (except when the alpha channel is the only channel enabled in the texture viewer). So this wouldn't be too different from the status quo.

I think the simpler approach would just be to patch any location = 0, index = 1 outputs to location = 1 when fetching shader output values and bind two render targets to obtain both outputs.

That probably is simpler overall. There is still some awkwardness with location = 0 being implicit, but it wouldn't be too bad.
The mildly annoying thing about this is that the Vulkan spec doesn't actually mandate that there be only one render target when using dual-source blending; instead it defines both maxFragmentOutputAttachments and maxFragmentDualSrcAttachments. In practice I think maxFragmentDualSrcAttachments is always 1, but I'm not 100% sure of this. The existing swap approach works around this by not caring about which output location is being used, and instead swapping everything and letting the existing logic handle choosing one of the render targets (based on what was selected in the UI).

I have split this PR into 4 separate PRs:

#3009
#3010
#3011
#3012

Hopefully these are of a more managable size; if needed I can split them further on a per-commit basis.
I have not yet updated those PRs to account for the feedback provided here, though I did rebase them.

An alternative way to look at it - PRs only have to be well formatted and compile (and not break things, though that comes up in review). Crucially there's no requirement for a PR to be a self-contained working piece of code end to end, and indeed with a larger feature that you're breaking up that might be the best way to do it. You could first submit only the shader patching helper function even if nothing calls it. Then the fetching of dual-source blend outputs just writing to dummy local variables. And so forth from there.

I will try to keep this in mind in the future. I personally like to try and get something functional that I can play around with, so that I can make sure my assumptions are correct and the design isn't a dead-end. But that approach does also mean that I end up with a lot of code that could be submitted for review all at once, which is a larger burden for you, and it's definitely important for you to be able to review everything.
To get a better idea of what you want: assuming we did still go with additional columns, would 33f4b4bb7365c9c45c9895ed345df3d5450dcd20 ("Use an enum for pixel history column ids instead of magic numbers") on its own be something you want as a single pull request, or would you prefer that bundled with other commits that actually add more columns? Adding more columns without getting rid of the magic numbers is impractical, but getting rid of the magic numbers without other context also seems wrong to me.

The way I would suggest to think of it is that while code development normally happens with an indirect route and you might go back and make changes after finishing a later part, once you have a logical portion.

I feel like you are missing part of the sentence here. Can you clarify what you meant by this?

I don't see a value to having these extra columns. The source and destination blend factors are either implicit from the fixed blend setup that is visible in the pipeline state, or they are the tex before/shader output value already displayed. I don't think there is any benefit to re-displaying them in a slightly different form.

To clarify: it's not the factors themselves that I'm showing, but instead the source blend factor times the source color and the dest blend factor times the dest color. Unfortunately I don't know of a specific name for these.
The source column shows what the result would be if the destination factor is set to 0 for that primitive only (with all previous primitives still being blended normally), while the destination column shows the source factor set to 0. (The blend op is always set to VK_BLEND_OP_ADD as well, so it is always the case that for the source column, R = Rs0 × Sr and for the dest column, R = Rd × Dr.)
For simple blend configurations where the source and destination factors are both 0/1/alpha, this is still not particularly useful. But if the factors are colors (not necessarily using dual source), then there is a benefit to it: you see the multiplied color, which is somewhat hard to mentally follow. Being able to see both halves of a more complicated blend operation is helpful in my opinion, though it certainly is not something that's needed by default.

As you say this is already not always the case, and honestly I would place my bets that there is no currently running code on any GPUs today that actually uses the RGB dual source blend factors for a real purpose. Dual source alpha certainly makes sense, but using RGB is a very narrow niche and I'm not aware of any use cases. Adding significant extra scaffolding for what is possibly a theoretical use case is not justified in this case.

OpenGL's ARB_blend_func_extended lists two potential uses, both of which seem to be used in the wild:

Example Use Cases
There are several potential uses for this functionality. A first example
is in the implementation of sub-pixel accurate font rendering algorithms.
Given a known layout of pixel elements (red, green and blue components),
coverage may be calculated independently for each element and passed
to the blender in the second source color as a per-channel opacity. To use
this mode, use the following blend functions:
glBlendFunc(GL_SRC1_COLOR, GL_ONE_MINUS_SRC1_COLOR);

As a second example, consider a partially reflective colored glass window.
It will attenuate light passing through it, and reflect some of the light
that strikes it. Using an appropriate combination of functions, this effect
may be simulated in a single pass using only fixed-function blending
hardware. In this case, the following blend functions may be used:
glBlendFunc(GL_SRC_ALPHA, GL_SRC1_COLOR);

The sub-pixel font rendering case is used by web browsers; Firefox (WebRender) uses it. There's a long document discussion how they do text rendering, with a brief mention of dual source blending. They did implement that and it is used in some cases, but I haven't tried to trace down exactly when it's enabled (I suspect they have some checks to make sure the monitor has an expected subpixel configuration and such). I also was unable to capture it in RenderDoc (they have instructions but I couldn't get it to work) so I'm not 100% sure it's used in practice. This is also a case where, although there are 3 values + alpha for the second output, the values are not really meaningful as a color, so visually the color column wouldn't help (but blend source/dest could still be useful).
The colored glass window case does seem to exist, too. I found a paper (PDF) discussing transparency in Cyberpunk 2077 (released 2020). It includes this paragraph:

Glass Blending. Unlike smoke and other participating media, glass
tints the objects behind it, in addition to "additive blending effects".
Therefore, traditional alpha blending does not work: we would
need to sacrifice either one or the other. To address that, we utilized
dual-source blending. This allowed us (with some limitations) to
have the best of both worlds with little to no overhead.

Unfortunately, it seems it was for a talk at a 2021 SIGGRAPH session which was not recorded. So there isn't any further context beyond that. But I assume this is a case where SRC1_COLOR is used, and more importantly represents a color in the game world, so a column for it would be informative (and blend source/dest would also be informative, as multiplying colors in your head isn't easy).
The Witness (released 2016) also has a section with tinted glass that attenuates the colors behind it (the bunker/greenhouse), but it doesn't seem like they ever discussed how that was implemented, and it might just use SRC_COLOR instead since I'm not sure if they actually have an additive blending component to it. I haven't captured either of these games, since they aren't mine, of course.
And of course there's whatever's happening with emulation where the emulated hardware has some other blending feature/quirk that dual source blending is used to implement/approximate. Dolphin only uses alpha, but other emulators might need to do other things (though I haven't looked for evidence of this).

I will try to keep this in mind in the future. I personally like to try and get something functional that I can play around with, so that I can make sure my assumptions are correct and the design isn't a dead-end. But that approach does also mean that I end up with a lot of code that could be submitted for review all at once, which is a larger burden for you, and it's definitely important for you to be able to review everything.

If you want to be able to prove out some code end-to-end then that's totally fine but you then bear the risk of having to throw away more code if something you did at the start was in an undesired direction. Generally I don't recommend getting too far ahead of what you've landed - you can take advantage of being able to land supporting/interim code upstream to keep your feature branch from getting too large.
You can also always ask about an intended design - e.g. I could have let you know early not to add any new columns, not to worry about handling multiple output attachments, and not to do anything special with the colour1 parameter (only treat these as 'extra alpha channels' on the shader out effectively).

To get a better idea of what you want: assuming we did still go with additional columns, would https://github.com/baldurk/renderdoc/commit/33f4b4bb7365c9c45c9895ed345df3d5450dcd20 ("Use an enum for pixel history column ids instead of magic numbers") on its own be something you want as a single pull request, or would you prefer that bundled with other commits that actually add more columns? Adding more columns without getting rid of the magic numbers is impractical, but getting rid of the magic numbers without other context also seems wrong to me.

That would be fine to include with other commits, especially the other UI changes as they are logically bundled together and any review feedback will likely affect them as a whole. You could probably land that on its own if you wanted, a refactor to improve readability is fine if you explain the intention (I might reject it only if you didn't explain why you wanted to change it). The limit of 1000 lines is pretty arbitrary and more a rule of thumb than anything else. 1000 lines could be very easy to review or could be incredibly dense, so I set the guide conservatively so that at least there was a specific guide and it wasn't just up to my whims.

I feel like you are missing part of the sentence here. Can you clarify what you meant by this?

Looks like this is a thought I didn't finish while drafting the response. I think what I was meaning was that code development doesn't always get things right first time, and if a feature is large enough the first PR you land doesn't have to be 'final code'. Any PR will be reviewed on its own merits and any issues immediately apparent will get resolved that way. If you're developing a feature and it lands over 3 or a dozen or a hundred PRs it isn't a problem if one PR changes some code that seemed reasonable in an earlier PR. That's just how code works and past a certain scale (1000 lines is the one I picked out of a hat) you shouldn't try to perfect everything before reviewing and landing it.
As soon as you have some kind of logical chunk of code completed you can PR that - even if you haven't written the rest of the code, and it doesn't do anything on its own or is even referenced. Until quite recently there was stub D3D8/D3D9 code which was committed years ago on its own and kept around. I appreciate with a change like this it's close to small enough for one PR where it might be a harder call to make, but you would have to go to extremes before I'd start rejecting a feature like this for being split into too many PRs if you explained what the end goal was, so I'd say err on the side of looking for smaller chunks if you're starting to reach that 1000 diff litmus test.

OK. For now, I think I'll open a new PR containing only b57b488aa71d3c8159ed2b2e83a3e77f3885227c. That one is probably a good starting point as it's a stand-alone fix for an issue there's already a TODO comment for. (It does become a easier to trigger when PerFragmentInfo increases in size, though.) I also already have a demo+automated test for that in c115cb68d2ed433cfb094c95ca09a1b968ce0f55, though the automated test also checks blendSrc/blendDst currently (which would not be hard to remove/re-add later if needed). Do you want that as part of the same PR, or submitted later?

That sounds good to me, that commit is a useful bugfix regardless so it works in isolation - looking at it, I think that explains and fixes a bug @Zorro666 noticed a few days ago while testing 1.28 before release.
Whether to include the test is up to you - I never require tests for bugfixes but it's certainly welcome. As you say it would need to be modified a bit to work with the current API surface and is a bit much for just that fix, but makes sense if it's going to be more useful once other things land. An alternative would be to add a new 100s-of-overlapping-tris draw to VK_Pixel_History that fails the depth test so no other checks need to be changed, but I'm fine if you include the test as-is with minimal modifications to work.

I'm going to close this PR now as I think you are still planning to split it out into separate PRs as you have been doing and having a stale PR open is unnecessary.

OK, I'll open additional split out PRs in the future once I have them ready. (I haven't taken the time to work on this in a while though, beyond locally resolving merge conflicts.)


Filter recognizers based on locale/country

Is your feature request related to a problem? Please describe.
The number of recognizers in Presidio are growing which is great, but it also means that recognizers are more likely to be irrelevant to some users. Running all recognizers means more processing time and more false positives.
Describe the solution you'd like
The ability to provide the RecognizerRegistry (or AnalyzerEngine) with a country code to either include or filter will allow users to use only a subset of recognizers that is relevant to their tasks

@omri374 Can I give it a shot ?

Absolutely!

@omri374 I am facing difficulties while setting this up locally on a Windows OS . The documentation is a bit unclear to me. Can you help ?

Sure. Which documentation are you following? What issues are you facing?

@omri374 This is the documentation I am following.
https://microsoft.github.io/presidio/development/
Steps I followed :-
1.First I created a Pycharm project with virtual env enabled
2. Clone the Repo
3. pip install --user pipenv
4.pipenv install --dev --skip-lock (ran in the presidio-analyze directory)
Then it says 'installing dependencies' and it gets stuck there without even showing an error, nor does it proceed.

@AmanSal1 I'm not sure why this is happening, but pipenv isn't mandatory. You can install the package locally (preferably in a virtual environment) using pip: pip install -e . (in the presidio-analyzer folder)

@omri374 Okay, got it. I just want to confirm: Is the UI developed using Docker? And when I change the code base for some tweaks, do we rebuild the image, right?

By UI do you mean the demo website? It is built using Docker, see code here: https://github.com/microsoft/presidio/blob/main/docs/samples/python/streamlit/index.md
I suggest to start with the Python API, and then add this capability into the REST API later on.

@omri374 Okay, I will look into that, but I've thought of a solution. First, we'll modify the structure of the recognizers_map in the RecognizerRegistry, and then we'll introduce a country code parameter. This parameter will be optional and can be specified whenever an object of that class is instantiated.
Something Like this :
recognizers_map = {
"en": {
"US": [
UsBankRecognizer,
UsLicenseRecognizer,
UsItinRecognizer,
UsPassportRecognizer,
UsSsnRecognizer,
NhsRecognizer,
SgFinRecognizer,
],
"AU": [
AuAbnRecognizer,
AuAcnRecognizer,
AuTfnRecognizer,
AuMedicareRecognizer,
Do you think this is the right approach?

Thanks, yes that sounds like a good approach. Note that there will be some universal recognizers, like credit card or URL who don't belong to any country.

Do we also need to add a country field to the EntityRecognizer class?

Thanks, yes that sounds like a good approach. Note that there will be some universal recognizers, like credit card or URL who don't belong to any country.

es": {
"ES": [EsNifRecognizer],
"ALL": [
CreditCardRecognizer,
CryptoRecognizer,
DateRecognizer,
EmailRecognizer,
IbanRecognizer,
IpRecognizer,
MedicalLicenseRecognizer,
PhoneRecognizer,
UrlRecognizer,
],
},
"it": {
"IT": [
ItDriverLicenseRecognizer,
ItFiscalCodeRecognizer,
ItVatCodeRecognizer,
ItIdentityCardRecognizer,
ItPassportRecognizer,
],
"ALL": [
CreditCardRecognizer,
CryptoRecognizer,
DateRecognizer,
EmailRecognizer,
IbanRecognizer,
IpRecognizer,
MedicalLicenseRecognizer,
PhoneRecognizer,
UrlRecognizer,
],
},
It will look like this for the common recognizers

AnalyzerEngine

@omri374   Adding the country code directly to the EntityRecognizer class might not be the most feasible option because the country code is typically associated with specific recognizers rather than being a generic property of all recognizers. What do you think ?

@omri374 Additionally I was also thinking that it would be more feasible if we declare country code parameter in the RecognizerRegistry it is a good approach as it make it central place for it but I guess it can also be done without declaring it in the RecognizerRegistry and directly be declared in the AnalyzerEngine.

By UI do you mean the demo website? It is built using Docker, see code here: https://github.com/microsoft/presidio/blob/main/docs/samples/python/streamlit/index.md
I suggest to start with the Python API, and then add this capability into the REST API later on.

@omri374  When I follow the given steps in the above given url I get an error

Thanks. I'll look into why the demo is not working.

@omri374 Yes their is some problem with recognizer_register file I guess because if we dont use the the demo and use it externally then also the same error is shown .

@AmanSal1 I couldn't reproduce this. Is your code completely in sync with the one in the main branch?

@omri374 Yes you are now it works .
` from presidio_analyzer import AnalyzerEngine
text1 = "I suspect Professor Plum, in the Dining Room, with the candlestick"
analyzer = AnalyzerEngine()
results = analyzer.analyze(text=text1, language='en')
print("Results:")
print(results) `
Is this a valid code ?

Yes

@omri374  I get this error when I run the above code.

can you please share your TEST.py?


Specify multiple push destinations using dsn

As 0.2.0 version introduces push/pull destination supply through a generic dsn format. It could be event better to be able to push to multiple destinations using that format. Mixed destination types should be possible.
Desired behavior:
$ trousseau s3://id:secret@bucket:region/path s3://id:secret@otherbucket:otherregion/otherpath scp://login:pass@host:port/path

Deprecated.


5.0.8 Patch Release

Prerequisites

[x] DEV: Create branch release-x.x.x-rc.x - tested in stable-5.0

[ ] DEV: bump ocis version in necessary files

[ ] DEV: sonar-project.properties
[ ] DEV: ocis-pkg/version/version.go

[ ] DEV: prepare changelog folder in
[ ] DEV: update production docker tag in the production.yml file in the continuous deployments

[ ] DEV: Check successful CI run on release branch
[ ] DEV: Create signed tag
[ ] DEV: Check successful CI run on v5.0.8 tag / BLOCKING for all further activity
[ ] DEV: Merge back release branch

QA Phase

[ ] QA: Confirmatory testing (if needed)

[ ] https://github.com/owncloud/enterprise/issues/6873

[ ] https://github.com/owncloud/web/issues/11031

[ ] QA: Compatibility testing between 5.0.7 and 5.0.8
[ ] QA: Performance test  see result here
[ ] QA: e2e with different deployment:

[ ] QA: wopi against smoke test

note: we didn't port https://github.com/owncloud/ocis/commit/f29b2543333d8ba56e29474205a22de6527ae379 to stable-5.0 so we get error:
{"level":"error","service":"notifications","error":"mail: no address","time":"2024-09-20T14:49:44+02:00","message":"parsing error, the 'smtp_sender' must be a valid single RFC 5322 address."}
nothing critical - ocis still works

Compatibility test between owncloud/ocis:5.0.7 and owncloud/ocis:5.0.8
shares:

[ ] public share (with an expiration date)
[ ] share with user as role editor (with an expiration date)
[ ] share with user as role viewer
[ ] share with group "Users"

project space:

[ ] uploaded folder & files
[ ] trashed files
[ ] share space with user
[ ] public share space

files:

[ ] uploaded folder & files
[ ] version of files
[ ] trashed files
[ ] GDPR export

users

[ ] non demo user with role admin
[ ] non demo user with role user
[ ] created new user
[ ] disabled user
[ ] created new group

settings

[ ] language settings
[ ] update logo админ
[ ] new password

Remarks: no remarks

[ ] merge https://github.com/owncloud/ocis/pull/10138 for clean reva version

Compatibility test between owncloud/ocis:5.0.7 and owncloud/ocis:5.0.8
after reva bump
(https://hub.docker.com/layers/56940/ocis/dev/images/sha256-b09cb1925a386fef983dfda8f07322722491fe4a3a50f154270b240cb2004f3e?context=repo)
shares:

[x] public share (with an expiration date)
[x] share with user as role editor (with an expiration date)
[x] share with user as role viewer
[x] share with group "Users"

project space:

[x] uploaded folder & files
[x] trashed files
[x] share space with user
[x] public share space

files:

[x] uploaded folder & files
[x] version of files
[x] trashed files
[x] GDPR export

users

[x] non demo user with role admin
[x] non demo user with role user
[x] created new user
[x] disabled user
[x] created new group

settings

[x] language settings
[ ] update logo админ
[x] new password

Remarks: the logo didn't load

K6 tests:
https://grafana.k6.infra.owncloud.works/?orgId=1&refresh=15m&var-test_id=86fef651-a756-438e-af7d-d1c89638c439
checks.........................: 100.00% ✓ 50924     ✗ 0
     data_received..................: 24 GB   18 MB/s
     data_sent......................: 16 GB   12 MB/s
     http_req_blocked...............: avg=71.5µs   p(95)=7.42µs   p(99)=11.56µs  count=48498
     http_req_connecting............: avg=6.6µs    p(95)=0s       p(99)=0s       count=48498
     http_req_duration..............: avg=124.27ms p(95)=302.48ms p(99)=717.76ms count=48498
       { expected_response:true }...: avg=124.27ms p(95)=302.48ms p(99)=717.76ms count=48498
     http_req_failed................: 0.00%   ✓ 0         ✗ 48498
     http_req_receiving.............: avg=9.68ms   p(95)=595.08µs p(99)=426.48ms count=48498
     http_req_sending...............: avg=4.68ms   p(95)=42.27µs  p(99)=1.19ms   count=48498
     http_req_tls_handshaking.......: avg=58.9µs   p(95)=0s       p(99)=0s       count=48498
     http_req_waiting...............: avg=109.89ms p(95)=263.48ms p(99)=418.07ms count=48498
     http_reqs......................: 48498   36.323652/s
     iteration_duration.............: avg=11.73s   p(95)=19.57s   p(99)=23.94s   count=28467
     iterations.....................: 28467   21.320991/s
     vus............................: 1       min=0       max=300
     vus_max........................: 300     min=64      max=300

🎉  Infinite Scale 5.0.8
Docker
docker pull owncloud/ocis:latest
OR
docker pull owncloud/ocis:5.0.8
Binaries
https://download.owncloud.com/ocis/ocis/stable/5.0.8/

https://drone.owncloud.com/owncloud/ocis/39468 was happy but I couldn't find 5.0.8 in the https://download.owncloud.com/ocis/ocis/stable
@micbar I remember it doesn't show up right away, but after a few tries I didn't find it. Do you know what I did wrong?

https://drone.owncloud.com/owncloud/ocis/39468 was happy but I couldn't find 5.0.8 in the https://download.owncloud.com/ocis/ocis/stable
@micbar I remember it doesn't show up right away, but after a few tries I didn't find it. Do you know what I did wrong?

It will be published on the full hour

Binaries are published.

Changelog
Reva

Fix cs3org/reva#4761: Quotes in dav Content-Disposition header
Fix cs3org/reva#4853: Write upload session info atomically
Enh cs3org/reva#4701: Extend service account permissions


Add deprecation notice and further instructions to QuantumInstance migration guide

This is a proposal to address https://github.com/Qiskit/documentation/issues/1696, which doesn't correspond with my original reply.
While updating to the changes in ISA handling doesn't seem to complicated, I realized that updating the guide to use Primitives V2 seems very strange to me (because that is not how the migration was done at the time). The current guide is a (in my opinion, valid) reflection of what the motivations were with primitives V1, and the reason why it was appreciated was because it reflected well the evolution of the code. I also think that it is commonly understood that migration guides are written at a specific point in time, and may require "chaining" with a further migration guide to reach the current state of the package. So, instead of migrating everything to V2, I propose adding a warning at the beginning of the guide pointing to the V1 to V2 migration guide.
Once again, this is just a proposal, and I am happy to rethink this.

I think this is a reasonable approach.


Question: AcceptOffers got "403 Forbidden"

I build a small mesos cluster(1 master 1 slave) use docker to run the persistent_scheduler in mesos-go/examples/persistent_scheduler and got a "403 Forbidden" error when scheduler send AcceptOffers.
I read the mesos-go code and the scheduler api doc, to use /api/v1/scheduler api, driver should first send a Call_SUBSCRIBE message, and use another connection to send subsequent Call_ACCEPT message.
Scheduler must make additional HTTP requests to the “/scheduler” endpoint only after it has opened a persistent connection to it by sending a SUBSCRIBE request and received a SUBSCRIBED response. Calls made without subscription will result in a “403 Forbidden” instead of a “202 Accepted” response.
seems mesos-go driver use a RegisterFrameworkMessage to register with mesos instead of SUBSCRIBE, is there a plan to fix problem?
======================================
my test env
ubuntu 14.04
docker version 1.11.1
docker run -d -e MESOS_HOSTNAME=<IP_ADDRESS> -e MESOS_IP=<IP_ADDRESS> -e MESOS_PORT=5051 -e MESOS_MASTER=<IP_ADDRESS>:5050 -e MESOS_RESOURCES="cpus:1.2" -v /sys/fs/cgroup:/sys/fs/cgroup -v /var/run/docker.sock:/var/run/docker.sock --name slave --net host --privileged mesoscloud/mesos-slave:0.28.1-ubuntu-14.04
docker run -d -e MESOS_HOSTNAME=<IP_ADDRESS> -e MESOS_IP=<IP_ADDRESS> -e MESOS_PORT=5050 --name mesos-master --net host --restart always mesoscloud/mesos-master:0.28.1-ubuntu-14.04

It sounds like you're using the code on mesos-go/master (uses the older, mesos v0 API) but you're reading the mesos docs for the newer v1 API. The mesos-go project has been building support for the v1 API in the mesos-go/next branch. That branch is currently under development, so please vendor appropriately. There is also example code in that branch that demos how to use the new API.


feat: new hook useMeasure

What new hook does?
Uses ResizeObserver to track element dimensions and re-render component when they change.
Checklist

[x] Have you read contribution guideline?
[x] Does the code have comments in hard-to-understand areas?
[x] Is there an existing issue for this PR?

#33

[x] Have the files been linted and formatted?
[x] Have the docs been updated?
[x] Have the tests been added to cover new hook?
[x] Have you run the tests locally to confirm they pass?

Why not just call this "useResize"?

Why not just call this "useResize"?

It does not resize anything? 🤔
I also dont really like useMeasure, but this name is quite widespreaded and looks like most suitable for what it does.


add mish op

添加mish算子

I'm very sorry. This is my first PR, and i want to PR to the branch forked by my classmate for further modification. This was a wrong operation. I apologize again.

I'm very sorry. This is my first PR, and i want to PR to the branch forked by my classmate for further modification. This was a wrong operation. I apologize again.

Thanks for the contribution! No worries at all, welcome to send it out if it's ready!


Bazel test fail. Error deduced conflicting types.

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution: Mac OS Mojave 10.14.1 (18B75)
TensorFlow installed from (source or binary): source
TensorFlow version: branch r1.12
Python version: 3.6.6
Installed using virtualenv? pip? conda?: building is in a virtualenv created by pyenv virtualenv 3.6.6 my_tf_build_env
Bazel version (if compiling from source): from source. 0.15.0
GCC/Compiler version (if compiling from source): Apple LLVM version 10.0.0 (clang-1<IP_ADDRESS>)
CUDA/cuDNN version:  no cuda, build only for cpu
GPU model and memory: Intel Core i7, 16 GB

Describe the problem
I was following the tutorial to build tensorflow from source.  I was on the r1.12 branch, root directory, typed bazel test -c opt -- //tensorflow/... -//tensorflow/compiler/... -//tensorflow/contrib/lite/.... Error Message:

Provide the exact sequence of commands / steps that you executed before running into the problem
commands sequence is same as this tutorial.
In the ./configure part, my configuration is like below:

Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Added a PR #24237 for the fix.

Added a PR #24237 for the fix.

Thank you.


Create manifest.webmanifest in a sub directory of public

Greetings,
Firstly, I want to express my gratitude for the outstanding plugin you've developed. It has greatly enhanced my project's functionality.
Issue Overview:
I've encountered a challenge while utilizing the vite-pwa nuxt 3 plugin within my project. In my project's public folder, I have a subdirectory designated for displaying various assets. However, my reverse proxy setup is configured to deny access to all other subdirectories except this designated one.
Upon running the Nuxt build process, the plugin generates the following output structure:

.output

public

subdirectory

favicon.ico
sw.js
workbox.js

manifest.webmanifest

While I've successfully managed to configure the service worker (sw.js) and the Workbox file (workbox.js) to be served from the subdirectory by incorporating the following configuration in nuxt.config.js:
workbox: {
  swDest: '/public/subdirectory/sw.js'
}

However, the challenge arises when attempting to automatically generate the manifest.webmanifest file within the subdirectory during the manifest generation process facilitated by the plugin.
I am unable to locate any configuration options within the plugin's documentation that would allow me to specify the output directory for the manifest file.
Any sort of guidance or assistance in resolving this issue would be really helpful.

Dont change web manifest and sw location, the sw scope cannot be outside the subfolder (you will need to add service-worker-allowed: / http header or similar). The icons can be in any subfolder.

all of the files (nuxt script, icons, assets) are in the subdirectory file. I don't think it will be an issue to serve it from the subdirectory.

The .output/public folder is your app's root context, Vite/Nuxt will copy your public folder assets to that folder (preserving subfolders structure): the sw is under subdirectory path. The sw.js request is <base>/subdirectory/sw.js, the browser will prevent that sw to be installed with scope <base>


Can't install the package

When I add the mentioned section to the stack.yaml, I get the following error
YAML parse exception at line 73, column 0,
while scanning a simple key:
could not find expected ':'
See http://docs.haskellstack.org/en/stable/yaml_configuration/

Guys, I think you have started an amazing project and I want this project to be continued, so I want to contribute and use this project, but first I need to install & see it how it is working.


is there a api way of pulling this info:  tag-support.csv

it would be more better and dynamic to have api way of pulling this info, may be via resource provider objects? do we have a way to do this?

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

ID: 66769e1b-720b-f1b1-a5e3-ed5cb24cd233
Version Independent ID: b6272e61-58c1-3e2f-3e36-a9ee920c0915
Content: Tag support for resources - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/tag-support.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@mganeshphani Thanks for the feedback!
@tfitzmac Can you please provide your insights on this feedback ?

@mganeshphani - sorry, there is not a way to programmatically get this info currently. If that changes, we will update this guidance to point people to the easier way to get the info.

#please-close


[Feature]: Can I use proxy to connectOverCDP?

🚀 Feature Request
I want to connect remote chrome browsers ,  which may be started on AWS or GCP. but in my country,the network can't be reached .  I want to have a ConnectOverCDPOptions , like 'proxy' to set a http proxy to connect them.
Example
overCDPOptions.setProxy("<IP_ADDRESS>:8000");
Motivation
I want to connect remote chrome browsers ,  which may be started on AWS. but in my country,the network can't be reached .  I want to have a ConnectOverCDPOptions , like 'proxy' to set a http proxy to connect them.

There is no built in proxy support for connectOverCDP. The easiest you can do probably is to bring up local server that would forward the requests via proxy to AWS.
Closing this issue as we are not planning to implement this.


Fix import session bug in example application

Hey Nartex,
Can you only let your "Fix import session bug" commit in your pull request? I will merge the pull request from zulkis.
Thanks!

Also: please use SCRecordSessionSegmentFilenameKey instead of the string value directly.


Possible performance issue with fragment shaders and overdrawn geometry

Describe the bug
I noticed a significant performance hit that seems to depend on the resolution, for opaque geometry that is overdrawn and for which I didn't expect the fragment shader to run. I suspect there's more to it but I'm not sure what.
I'm not sure how to investigate this properly, but here's how I made a simple test case:

I made a sphere.obj with 4k triangles, then another sphere_dedup.obj where all the triangles are duplicated N times (until I get about 1 million triangles, so ~250x times the original sphere).
I removed all the mesh optimizations from MeshAssimp::setFromFile
I added some timing code in material_sandbox.cpp, commented out SDL_Delay(16) in FilamentApp.cpp, and added a flushAndWait after the rendering.

The results I get on a 1080ti are:

sphere.obj renders in 1.5ms, 10ms when the window is maximized (maybe that's ok)
sphere_dedup.obj renders in 6.3ms, 46ms when maximized

Doesn't it sound too much ?
In the first case, I understand the fragment shader has more fragments to compute when the window is maximized; I guess that there are also a lot of work to do that don't depend on the geometry I'm pushing.
In the second case, I don't get where the additional 30ms come from, assuming most fragments should be discarded.
Could there be an issue with zwrite and depthCulling not working as intended or was I just being too optimistic with my GPU?
Edit: actually, this zwrite/depthCulling wouldn't save the lighting computation by themselves, I guess this would/should be taken care of by an unlit z-pass but I don't know.
Edit2: or maybe it would? the zpass could save the lighting of invisible faces, but isn't the depthCulling supposed to avoid reshading the same triangle again and again?
Note that my real case was me trying to duplicate skinned geometry to workaround the fact that there's no instancing available, but this test case seems to capture the essence of it. I could also be completely wrong and maybe this is normal for this many triangles.
To Reproduce
Steps to reproduce the behavior:
I attached the 2 obj to this ticket, plus a patch of the quick changes I made to have some sort of performance measurement (displays the average render time in seconds every 100 frames). Note that the GetTime code I used is for windows.
spheres_and_profile_patch.zip
Expected behavior
I expected both render time to be cheap as in theory the sphere_dedup.obj doesn't need more lighting computations than sphere.obj.
Desktop (please complete the following information):

OS: Windows
GPU: NVIDIA GTX 1080
Backend: OpenGL

You are most likely suffering from additional quad shading here. We used to have a depth prepass to combat this but it was causing a lot of compatibility issues on various GPUs and sometimes performance was worse because of the extra draw calls.
I don't think this test is representative of what would happen if you duplicated skin geometry.

So... In theory the fragment shader shouldn't run each time, but we should make sure we set the depth buffer test so that equal depths are discarded. I think we're doing this right, but it's worth double checking. I will do that on Monday.
Second point, you may just be overwhelming the vertex stage and/or the rasterization stage. But that theory might not hold because performance degrades significantly with the resolution.
Could you try to create sphere debug so that ask the extra triangles are inside the sphere (by using a smaller radius), this should guarantee that these triangles won't be shaded.
You could also try this year with an unlit, trivial, shader.

Well as I had no way of controlling the number of instances, some were overdrawing themselves, and the framerate was tanking when getting close to those ones. I'm just moving them out of the view now but I thought this could be the symptom of some other problem.
So without a depth pre-pass, your render time depends on how lucky you are with the order of the primitives, right? I guess you can sort entities at a higher level to minimize the overdraw, I don't know. On my scenes I'm struggling a bit to keep at 60fps on my 1080, already had to give up MSAA.
@pixelflinger : this definitely looks like equal depth fragments are re-shadowed; I'm not sure I want to create 250 new spheres to test that :)

If you give them proper bounding boxes the front to back sorting + depth buffer should eliminate most of the overdraw. It won't however fix overshading due to quad shading, we still need to add support for LODs to solve this (or bring back a more robust depth prepass). But yes, within a single model the order in which the primitives get processed by the GPU will impact the result (at least for primitives that don't get backface culled).

I'm out of luck then because the bounding box of my fake-instanced geometry is very big :)

Can it be smaller? :)

Not really, I'm using a single entity to display n characters at various locations, which was the point of instancing. Note that for something like trees or vegetation, this would be the same issue.

Does it have to be a single entity? You will definitely lose out on the sorting and culling we perform in engine.

I actually have more than 1 entity, but their instances need to be far apart for you not to see them being repeated.
The more spread out they are, the less you see it; so yeah, it implies big bounding boxes.
I guess one day there will be true instancing in filament and maybe the depth pre-pass will be back, so I'm not worried :) I hope these use cases help you evaluate what could be useful.

I still don't get why you can't have 1 entity per instance (or at least per few instances). Multiple entities can share the same vertex and index buffers. The "only" added cost will be the per entity UBO but those are small (they only contain the transform matrix).

I still don't get why you can't have 1 entity per instance

10000 animated characters is currently a big no-no. setBones is already costly (I've seen it mentioned in another ticket), there's no way I can call this 10k times.
Maybe I should consider sharing the vbos but it's currently not the bottleneck, and not doing it will help me create more visual variety.

Currently, to simulate instancing, you need to create N renderables, each using the same vertex/index data, which will allow you to have a tight bounding box.
Using large bounding boxes with a lot of empty space in them, will hurt filaments culling and sorting significantly.

@pixelflinger I can't create 1 renderable per animated character for that many characters: as mentioned above, setting their pose individually would be too costly. I'll keep this in mind though, maybe it can be useful for other things.
I knew big BBs would come with compromises, I already disabled shadows on them; I didn't expect the overdraw problem though.

Why would it be too costly? And how many are we talking about?

Why would it be too costly?

It's computing quats out of matrices each time you call setBones, when I only want to do it once for the few different poses I compute.

And how many are we talking about?

A very large crowd; my initial need was 10k people, I'm already quite below that :)

Note that there is a version of setBones() that takes quarternions directly. You could use that to avoid the matrix to quat conversion.
Honestly, I would try this, rather than messing with the bounding boxes.
There are definitely many things we can improve for your use case, and I'll look into it, but given the current situation, the best approach would be one renderable per instance, tight bounding boxes and the version of setBones that takes an array of Bone.


Consider use of release branches

Once we need to support a version for a given period of time, we will need to backport bug fixes to it, and also continue to develop new features for future versions.
There are a number of schemes for this such as "Git Flow", "Github Flow", "Gitlab Flow", etc. but these are either overcomplex or unsuitable for our use case.

We should definitely use release branches, we can work with SR to handle this as required.


Update to LND v0.13.3 due to CVE-2021-41592

A vulnerability deacribed in:
https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-October/003257.html
Can use the UPDATE menu to download the version, but LND v0.13.3 should be the part of RaspiBlitz v1.7.1 as default.

The latest version of C-lightning is not known to.be vulnerable:
cdecker in https://t.me/lightningd/7713:

Trying to dig up the details from the internal discussion, it looks to me like c-lightining always enforced the dust limit be below the reserve amount which means we were handling things correctly, but I'll let Rusty confirm that.

RC3 released on dev branch for final testing.


This is a bug bounty test, looking for security issues, please ignore...  zqllsz

This is a bug bounty test, looking for security issues, please ignore...  zqllsz

The OVH BugBounty program only allows hunters to work on the OVH services and does not allow Social Engineering (more information here: https://yeswehack.com/programs/ovh). The account has been banned from this organization and the malicious PR rejected.