Add published contracts page in teams, account and project layout

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on refactoring components related to contracts in the dashboard application, improving layout structures, and enhancing the handling of published contracts with better user experience and navigation.
Detailed summary

Updated DeployedContractsPage to remove unnecessary class names.
Refactored layout components to use SidebarLayout for better navigation.
Introduced PublishedContractsPage with improved structure and loading states.
Implemented authentication checks for account addresses before rendering pages.
Enhanced UI elements in DeployedContractsPageHeader and added links for publishing contracts.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#5659  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Any plans to upgrade node-gyp to latest version?

Any plans to upgrade node-gyp to latest version? Then we are not forced to use Python 2, we are able to use Python 3 instead.


Lots of whitespace between the "Accept" and "Reject" for managing group join requests.

There is a lot of whitespace between the "Accept" and "Reject" buttons when managing group join requests.  It feels like the Reject CSS is broken, because it's way off the right.
006.zip

possibly related https://github.com/hydroshare/hydroshare/issues/4050

possibly related https://github.com/hydroshare/hydroshare/issues/4050


Windows 7

Does this work with Win 7?
Thanks

No, since:

Python3.11 is not compatible with W7
Qt6 is not compatible with W7/8
Winget is not compatible with W7/8


Bug fixes in UG

Add Command Format section in UG
Fixes #218 #204

Hi @chewjh1234, could you resolve the merge conflicts? Thanks!


Dataset-specific and project-specifig URIs

Checkbox would be great!
Just the last bit of the URI needs to be adapted
e.g.
http://data.socialhistory.org/resource/med_clean/codelist/reden
instead of
http://data.socialhistory.org/resource/med_clean/codelist/di_nm_reden
In case of project-specific URIs, for example Ivo has identifiers for people across several datasets.

Subissue of #51


Updating az capi to store name of aks infrastructure resource group and the aks vnet as environment variables

Description
Updating az capi to store name of aks infrastructure resource group and the aks vnet as environment variables. They are needed for the scenario that the traffic from internet to k8s API server port 6443 is blocked by a network security group. The solution to that is to run k8s e2e tests in a pod on the aks worker node. This requires that aks cluster and k8s client either in the same vnet or in peered vnets. After aks cluster is created, store the aks infrastructure resource group name and the vnet name so that we can use them when peering the aks vnet and k8s vnet later in the template file.
Also add sshd to devcontainer.json so the binaries can be copied out of the container.
History Notes
Updating az capi to store name of aks infrastructure resource group and the aks vnet as environment variables

This checklist is used to make sure that common guidelines for an Azure CLI pull request are followed.

[X] The PR title and description has followed the guideline in Submitting Pull Requests.
[X] I adhere to the Command Guidelines.
[X] I adhere to the Error Handling Guidelines.

@mboersma looks like linter error due to large module.  Should we split out some of the functionality or skip linter error for this?

C0302: Too many lines in module (1021/1000)

We have hit this several times before and taken it as an opportunity for refactoring code out of custom.py into the other modules. That would be best, although it would require more than just moving find_resource_group_name_of_aks_infrastructure elsewhere, since apparently the file is at 999 lines already. :-|
So we could just add pylint: disable=too-many-lines to this PR. I created issue #185 to track refactoring of custom.py separately (it was already a problem before this PR).
@bingbing8 thanks for the PR! Let me know if this makes sense.

Also, you can test your linting changes locally with azdev style.

also please squash commits once this is ready for merging

C0302: Too many lines in module (1021/1000)

We have hit this several times before and taken it as an opportunity for refactoring code out of custom.py into the other modules. That would be best, although it would require more than just moving find_resource_group_name_of_aks_infrastructure elsewhere, since apparently the file is at 999 lines already. :-|
So we could just add pylint: disable=too-many-lines to this PR. I created issue #185 to track refactoring of custom.py separately (it was already a problem before this PR).
@bingbing8 thanks for the PR! Let me know if this makes sense.

Thanks

Member

** mboersma**

Thanks @mboersma. I will make change per your suggestion!

@bingbing8, at the top of the custom.py file there is this line:
# pylint: disable=missing-docstring

You can change it to:
# pylint: disable=missing-docstring,too-many-lines


Can a new release tag be created to enable Windows support in the vcpkg port?

Looks like the last release tag and vcpkg port have not been updated in a couple years. Is it possible to create a new release tag soon? I don't mind making a pull request to update the port.

New release will be made soon. Stay tuned!


Crash after update to latest release

I got a prompt to install the latest release today (x64 windows). Clicked the update button and then after the install completed, and everytime I then attempted to run it I got the following stack trace:
System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XDocument.Load(String uri, LoadOptions options)
at SyncTrayzor.Services.Config.ConfigurationProvider.LoadFromDisk(Configuration defaultConfiguration) in c:\projects\synctrayzor\src\SyncTrayzor\Services\Config\ConfigurationProvider.cs:line 145
at SyncTrayzor.Services.Config.ConfigurationProvider.Initialize(Configuration defaultConfiguration) in c:\projects\synctrayzor\src\SyncTrayzor\Services\Config\ConfigurationProvider.cs:line 85
at SyncTrayzor.Bootstrapper.Configure() in c:\projects\synctrayzor\src\SyncTrayzor\Bootstrapper.cs:line 85
at Stylet.BootstrapperBase.Start(String[] args)
at System.Windows.Application.<.ctor>b__1(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
I then downloaded 1.0.21 manually (x64 windows installer) and completed the install which went OK. Tried to run it and got the identical stack trace.
The relevant bit of the log file for the auto-update is as follows:
2015-05-29 14:41:49.4802 [Info] SyncTrayzor.Services.UpdateManagement.UpdateManager: Auto-installing 1.0.21
2015-05-29 14:41:49.5352 [Info] SyncTrayzor.Services.ProcessStartProvider: Starting C:\Program Files\SyncTrayzor\ProcessRunner.exe --nowindow -- "C:\Program Files\SyncTrayzor\ProcessRunner.exe" --runas --launch=""C:\Program Files\SyncTrayzor\SyncTrayzor.exe"" -- "C:\Users\syncuser\AppData\Local\Temp\SyncTrayzor\SyncTrayzorUpdate-1.0.21.exe" /SILENT
2015-05-29 14:42:17.2647 [Debug] SyncTrayzor.Services.Config.ApplicationPathsProvider: ExePath: C:\Program Files\SyncTrayzor
2015-05-29 14:42:17.6837 [Debug] SyncTrayzor.Services.Config.ApplicationPathsProvider: LogFilePath: C:\Users\syncuser\AppData\Roaming\SyncTrayzor\logs
2015-05-29 14:42:17.6837 [Debug] SyncTrayzor.Services.Config.ApplicationPathsProvider: SyncThingBackupPath: C:\Program Files\SyncTrayzor\syncthing.exe
2015-05-29 14:42:17.6837 [Debug] SyncTrayzor.Services.Config.ApplicationPathsProvider: ConfigurationFilePath: C:\Users\syncuser\AppData\Roaming\SyncTrayzor\config.xml
2015-05-29 14:42:17.6837 [Debug] SyncTrayzor.Services.Config.ApplicationPathsProvider: ConfigurationFileBackupPath: C:\Users\syncuser\AppData\Roaming\SyncTrayzor\config-backups
2015-05-29 14:42:17.6837 [Debug] SyncTrayzor.Services.Config.ApplicationPathsProvider: CefCachePath: C:\Users\syncuser\AppData\Local\SyncTrayzor\cef\cache
2015-05-29 14:42:18.8808 [Debug] SyncTrayzor.Services.Config.ConfigurationProvider: Loaded default configuration: <Configuration ShowTrayIconOnlyOnClose=False MinimizeToTray=False CloseToTray=True ShowSynchronizedBalloon=True ShowDeviceConnectivityBalloons=True SyncthingAddress=localhost:8384 StartSyncthingAutomatically=True SyncthingApiKey= SyncthingEnvironmentalVariables=[] SyncthingUseCustomHome=False SyncthingDenyUpgrade=False SyncthingRunLowPriority=False Folders=[] NotifyOfNewVersions=True LastNotifiedVersion= ObfuscateDeviceIDs=True UseComputerCulture=True SyncthingConsoleHeight=100 WindowPlacement= SyncthingWebBrowserZoomLevel=0 LastSeenInstallCount=0 SyncthingPath=%APPDATA%\SyncTrayzor\syncthing.exe SyncthingCustomHomePath=%LOCALAPPDATA%\SyncTrayzor\syncthing>
2015-05-29 14:42:19.0638 [Debug] SyncTrayzor.Services.Config.ConfigurationProvider: Found existing configuration at C:\Users\syncuser\AppData\Roaming\SyncTrayzor\config.xml
2015-05-29 14:42:19.3878 [Error] SyncTrayzor.Bootstrapper: An unhandled exception occurred
That is then followed by the same stack trace mentioned above.

Mind posting the contents of C:\Users\syncuser\AppData\Roaming\SyncTrayzor\config.xml? Censor as appropriate.

It's empty... pretty sure it shouldn't be!

It's timestamp was about when I clicked the upgrade button.

Ah, I was worried that might be the case. The only thing I can think of is that the upgrade kicked in at exactly the wrong time: while SyncTrayzor was writing to its config file. Due to a legacy issue with the embedded browser component, the installer currently need to kill SyncTrayzor in quite an ugly way. There's the foundation for a fix for this out there, but I need to wait until people have upgrade to that version before I can put the other half of the fix in place!
I'm afraid you'll have to delete the (now empty) config file, and let SyncTrayzor regenerate it. If you've got a backup config file (they're generated during config file version migrations, and will be in C:\Users\syncuser\AppData\Roaming\SyncTrayzor\config-backups), you can copy that back and that will be used as a starting point.

Thanks - that fixed it. Despite not having a 'config-backups' folder, it still retained my settings (folders and paired peers) so everything is back up and running. Thanks for the help.

Yeah, Syncthing's config is separate from SyncTrayzor's. SyncTrayzor's config stores stuff like how to close to the tray, whether to watch folders for changes, the size of the console area, etc. For a full list, see what's in the settings menu.
I'll leave this issue open for now: I've had two people with corrupt config files recently (for completely different reasons), and it's something I should probably catch a bit better...

OK, I've got a better error message in there. Closing.


Suggestion: Mark package as discontinued on pub.dev

Hey @erluxman, I would recommend marking this package as discontinued at pub.dev because you don't maintain it for more than a year now.
For example, this package is still not null safe on pub.dev and uses a deprecated version of the Android embedding.

Hi @devj3ns , @erluxman added me to maintain this package. I will release a new version ASAP.

Hi @devj3ns , @erluxman added me to maintain this package. I will release a new version ASAP.

Awesome @maherjaafar 😀🥳


Default MDC entries not propagated to LocalActivities

Expected Behavior
WorkflowId, RunId etc should be propagated to LocalActivities.
Actual Behavior
MDC entries like WorkflowId, RunId etc are not propagated to LocalActivities. These entries are absent.
This section from ActivityWorker is not present in LocalActivityWorker handle method
From the thread: https://community.temporal.io/t/mdc-values-not-present-for-local-activities/2502/4
Steps to Reproduce the Problem

Create a Workflow.
Create a LocalActivity.
Invoke local activity from workflow.
Inside local activity print MDC.get(LoggerTag.WORKFLOW_ID)  .

Specifications

Version: 1.0.9
Platform: java-sdk

This a duplicate of https://github.com/temporalio/sdk-java/issues/489 and it's fixed. We also have a unit test checking MDC propagation + local activities: https://github.com/temporalio/sdk-java/commit/b23edac35fc6ef4fe44685f9897027f9d1d5569e#diff-061e39ce33d4eacc5c8d5a281e5497251fa53188779217af391d87c363e4c918R1107
Please feel free to reopen this issue with a test or code demonstrating a problem.


Problem

After entering the api key of the pterodactyl, nothing happens

You should get a popup to select a server.
I haven't fully handled the panel responding with something protocol-ish invalid (e. g. TLS errors), or not responding at all, so that's likely the issue here.
Do you have at least one server which you are owner of or added as subuser?


[CX_CLEANUP] -  Support state update for dependency tasks

What is this task and why do we need to work on it?
In https://github.com/EspressoSystems/HotShot/pull/3066, we moved the state update from the proposal handling function to the vote_if_able function, which is used only in the current logic but not in the refactored dependency tasks. We should add it to the vote task as well.
What work will need to be done to complete this task?
No response
Are there any other details to include?
No response
What are the acceptance criteria to close this issue?
The change is pushed to either https://github.com/EspressoSystems/HotShot/pull/3066 or main and the state is updated in the vote task as well.
Branch work will be merged to (if not the default branch)
No response

The relevant PR #3093 was merged into #3066, which was then merged into main.


darktable: 2.4.3 -> 2.4.4

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/darktable/versions.
These checks were done:

built on NixOS
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/darktable had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/darktable-rs-identify had a zero exit code or showed the expected version
/nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/darktable-cltest passed the binary check.
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/darktable-cli had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/darktable-generate-cache had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/darktable-cmstest had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/darktable-chart had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-rs-identify-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-cltest-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-cli-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-generate-cache-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-cmstest-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-chart-wrapped had a zero exit code or showed the expected version
1 of 14 passed binary check by having a zero exit code.
0 of 14 passed binary check by having the new version present in output.
found 2.4.4 with grep in /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4
directory tree listing: https://gist.github.com/5bf935d4e34e2708e7c6c17628c7ee7b
du listing: https://gist.github.com/b5ad3482552e5573dfaea42499dc0fb2

meta.description for darktable is: '"Virtual lighttable and darkroom for photographers"'.
cc @cillianderoiste @rickynils @flosse @mrVanDalo for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout 46f03200093529374b94430039ae4013d41d5b13 && nix-shell --pure -I nixpkgs=. -p darktable

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: darktable
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: darktable
Partial log (click to expand)
shrinking /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-cltest-wrapped
shrinking /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-cli-wrapped
shrinking /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-generate-cache-wrapped
shrinking /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-cmstest-wrapped
shrinking /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin/.darktable-chart-wrapped
gzipping man pages under /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/share/man/
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/lib  /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4/bin
patching script interpreter paths in /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4
checking for references to /build in /nix/store/jgj8pvq3axhdwb75mjz3pv6a0fricl5s-darktable-2.4.4...

Failure on aarch64-linux (full log)
Attempted: darktable
Partial log (click to expand)
'+fp' is not a recognized feature for this target (ignoring feature)
'+fp' is not a recognized feature for this target (ignoring feature)
building of '/nix/store/vhmf28hfxpzxa86mja42pi0yd97div6q-rustc-1.26.2.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/560k72x3gw1gbis2fhxw2dsd9shsivc8-cargo-1.26.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/fa14m90h5firblf1m8qf1qcgww51f3fq-librsvg-2.42.4.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/wqwg410fnw9iaym374r8zb3jd7wky8px-hook.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/yfpn31bbp0snabqyac37lkbqpy6fmig0-icon-naming-utils-0.8.90.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/36xdfr0agr22ikp33y604zm6y103y5kh-adwaita-icon-theme-3.28.0.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/r35w7cslnj3aq5927d15l43n1ckd9jff-darktable-2.4.4.drv': 4 dependencies couldn't be built
error: build of '/nix/store/r35w7cslnj3aq5927d15l43n1ckd9jff-darktable-2.4.4.drv' failed


Fixed 10686 -- Added abstract permission inheritance

I'm awaiting feedback before rebasing the commits into a single commit.

This seems to be two distinct features which could be added in separate commits at least, however, I'm not convinced that Meta.inherit_permissions is needed. Is there a problem with something this:
class Meta:
    permissions = BaseTask.Meta.permissions + (more permissions)

@timgraham you don't get the specific class name in the permission code, say you need app.view_task1 and app.view_task2 where Task1 and Task2 are sharing a common ancestor.
I agree with the inherit_permissions, I included it because they were both in the same ticket and original patch.

buildbot, test this please

I think if you want to inherit the base permissions, you could do Meta(BaseTask.Meta).

Isn't that a bit counter intuitive? All other attributes (except for a few
obvious ones like abstract) are inherited by default, no?
On Feb 1, 2016 10:10 PM, "Tim Graham"<EMAIL_ADDRESS>wrote:

I think if you want to inherit the base permissions, you could do
Meta(BaseTask.Meta).
—
Reply to this email directly or view it on GitHub
https://github.com/django/django/pull/6071#issuecomment-178192149.

According to the ticket, "The inherit_permissions flag would only be required in the case that one wanted Django's current behavior which is to discard base class permissions when explicit permissions are declared on the child class." I think it's better to use normal inheritance mechanisms, etc.
I'm also a bit hesitant to proceed with an enhancement like this as it adds further coupling between Meta and a contrib app. This doesn't seem like good separation of concerns. It could be useful to raise a discussion on the django-developers mailing list to see what others think.

In that case I rest my case, will adapt the changes when I have the time.
On Feb 1, 2016 11:40 PM, "Tim Graham"<EMAIL_ADDRESS>wrote:

According to the ticket, "The inherit_permissions flag would only be
required in the case that one wanted Django's current behavior which is to
discard base class permissions when explicit permissions are declared on
the child class." I think it's better to use normal inheritance mechanisms,
etc.
I'm also a bit hesitant to proceed with an enhancement like this as it
adds further coupling between Meta and a contrib app. This doesn't seem
like good separation of concerns. It could be useful to raise a discussion
on the django-developers mailing list to see what others think.
—
Reply to this email directly or view it on GitHub
https://github.com/django/django/pull/6071#issuecomment-178235854.

I've started the discussion on the mailing list.

When revising this, I'd suggest to implement it as two commits if possible: first the inheritance changes, then the interpolation additions.

Do you want the two commits in a single PR, or 2 PRs? I suspect the former.
On Feb 5, 2016 17:56, "Tim Graham"<EMAIL_ADDRESS>wrote:

When revising this, I'd suggest to implement it as two commits if
possible: first the inheritance changes, then the interpolation additions.
—
Reply to this email directly or view it on GitHub
https://github.com/django/django/pull/6071#issuecomment-180438492.

Either is okay.

Please send a new PR when you return to it.


Latex Rendering Issues

I have been having a few Latex rendering errors. I Believe that something goes wrong when you have too many subscripts or superscripts with brackets {}, however everything compiles fine in Obsidian. There are two possible ways for me to write the output below:

I can either use predefined macros in a preamble.sty file and an extension in obsidian, and that will get me the above output perfectly. If I try to compile this in quartz I get the following:

Or, for everywhere I want plaintext inside of math mode in latex I can use \text{}. This also works fine in Obsidian, but if it is compiled in quartz I get

Similarly, if I have too many subscripts within math mode then I get something like this:

When I should be getting something like this:

I have tested this in both Safari and Chrome and in neither of them it works. It would be great to fix these bugs.

I'm seeing similar issues, where more complicated latex expressions don't get rendered properly. For example
Quartz:

Obsidian:

My Quartz repository is based at d56a580 and my only commits on top have been changing the content folder and changing the domain name. I tried on Chrome and Firefox and both showed the same issue.
My repository can be found at https://github.com/abhmul/quartz.

It's because underscores are interpreted as italics by the Markdown parser, just use \_ when you need an underscore in LaTeX (and \\_ for an actual underscore to render).

How hard do you think it would be to modify the Markdown parser so it matches the underscore behavior in Obsidian? I can try making a PR if it's feasible.

Does this issue seem related? https://discourse.gohugo.io/t/katex-in-hugo/43274

@amzon-ex Your link looks a slightly different issue. The issue here is with a discrepancy between how underscores are parsed in math environments between obsidian.md and quartz.

@abhmul the reason I shared the discourse is quartz uses Hugo to publish the website, which also provides the markdown parser and it kicks in before Katex does, thereby converting certain symbols as if they were in markdown before Katex can act on it to generate math equations.

@amzon-ex If I understand correctly, you're saying the issue is with how Hugo handles markdown parsing and Katex. It seems then the fix of the root cause might just be to swap the ordering in which Katex and the markdown parser run?
If it's a Hugo issue, then it seems this is not really the place to fix it. A hack to fix this for us could just be to perform the underscore escaping described above before Hugo runs.

@abhmul You're right, that's what I mean. Katex is not a core feature of Hugo and the way Hugo is supplemented with Katex creates these issues if I've understood it right. (Perhaps @jackyzha0 can throw some more light on this?)
I think a fix is possible within Quartz, but it would be more like a workaround.

This issue should be fixed in Quartz 4. I'll be closing it for now but please reopen this issue if this persists in the new version.

The  issue is still in Quartz 4.

It does render correctly in Obsidian

@TheRealAnonymous008 can you provide the raw Latex source?

In Linear Discriminant Analysis (LDA) simplifies QDA as follows: $$
\begin{split}
P(y=c\mid x,\theta)&=\text{softmax}(\eta)_c \
\eta &=
\begin{bmatrix} \beta^T_1x+\gamma_1
\ \vdots \
\beta^T_C+\gamma_C
\end{bmatrix}\
\beta_c &= \Sigma^{-1}\mu_c \
\gamma_c &= -\frac{1}{2}\mu^T_c \Sigma^{-1}\mu_c+\log{\pi_c}
\end{split}
$$

You'll need hard line breaks \\ instead of \. This renders fine for me. Alternatively, you can use MathJax rendering so it doesn't error out like you saw but you still need to use \\ to get the desired break.
Obsidian has non-standard behaviour here so I'm sticking with official Latex syntax.

For future reference as well, the $$$$ block has to exist in its own line. It ended up working after doing this

In Linear Discriminant Analysis (LDA) simplifies QDA as follows:
$$
\begin{split}
P(y=c\mid x,\theta)&=\textrm{softmax}(\eta)_c \
\eta &=
\begin{bmatrix} \beta^T_1x+\gamma_1
\ \vdots \
\beta^T_C+\gamma_C
\end{bmatrix}\
\beta_c &= \Sigma^{-1}\mu_c \
\gamma_c &= -\frac{1}{2}\mu^T_c \Sigma^{-1}\mu_c+\log{\pi_c}
\end{split}
$$


Commands throw an error

When using -checkMask or -resetMask I get this error message:
It is about the AbnormalityParser.

-<color="yellow">checkMask
An error has occured
<color="#ff4040">System.TypeLoadException: Could not resolve type with token 0100001e (from typeref, class/assembly GameAbnormalityCheck, Assembly-CSharp, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null)
at AbnormalityParser.AbnormalityParser.CheckMask (System.String param) [0x0000c] in <3599d7f7cfab4a41aa7677fe8975a488>:0
at XConsole.ExecuteCommand (System.String cmd) [0x00189] in <8be0b94ee4174803af906bc5fe28296c>:0

Did I do something wrong or is it the newest DSP Update?

Thanks for notifying me of the error. The abnormality detection system had a rework with one of the newest updates, which broke the mod's commands. I'll have to rewrite the mod. Fortunately, it looks like the new system logs detailed info on detected abnormalities, so I should be able to add commands that give much more information than before.

Fixed in #f27a1bb


Add support for fractional weights in approx_percentile

Closes #758
A lot to change, I may have missed some things, thank you in advance for your guidance.
In particular I didn't know what/if anything needs to be updated in ./presto-product-tests/src/main/resources/sql-tests/testcases/math_functions/checkMathFunctionsRegistered.result which currently has lines like approx_percentile | bigint | bigint, bigint, double | aggregate | true | |. (PS it looks like these lines should rather be in testcases/aggregate?)

CLA submitted.
IIUC current CI failure is because test is not being run against bleeding edge airlift?
[ERROR] /home/travis/build/prestosql/presto/presto-main/src/main/java/io/prestosql/operator/aggregation/ApproximateLongPercentileAggregations.java:[118,27] incompatible types: possible lossy conversion from double to long

that line is
        digest.add(value, weight);

@cla-bot check

We've released a new version of Airlift and we're updating it here: #838

@MichaelChirico, the airlift update has been merged. Would you rebase this PR on the latest master to get the build going again?

seems to have failed, but i cannot make heads or tails of the Travis log to be able to get an idea of why...

This is the failure:
[ERROR] testApproxPercentile(io.prestosql.tests.TestQueryPlanDeterminism)  Time elapsed: 0.094 s  <<< FAILURE!
java.lang.IllegalArgumentException: Too many nodes in deserialized tree. Possible corruption
	at com.google.common.base.Preconditions.checkArgument(Preconditions.java:141)
	at io.airlift.stats.QuantileDigest.<init>(QuantileDigest.java:189)
	at io.prestosql.operator.aggregation.state.DigestAndPercentileStateSerializer.deserialize(DigestAndPercentileStateSerializer.java:67)
	at io.prestosql.operator.aggregation.state.DigestAndPercentileStateSerializer.deserialize(DigestAndPercentileStateSerializer.java:30)
	at io.prestosql.$gen.BigintBigintDoubleDoubleApproxPercentileGroupedAccumulator_20190602_141158_10474.addIntermediate(Unknown Source)
	at io.prestosql.operator.aggregation.builder.InMemoryHashAggregationBuilder$Aggregator.processPage(InMemoryHashAggregationBuilder.java:384)
	at io.prestosql.operator.aggregation.builder.InMemoryHashAggregationBuilder.lambda$processPage$1(InMemoryHashAggregationBuilder.java:144)
	at io.prestosql.operator.TransformWork.process(TransformWork.java:44)
	at io.prestosql.operator.HashAggregationOperator.addInput(HashAggregationOperator.java:421)
	at io.prestosql.operator.Driver.processInternal(Driver.java:384)
	at io.prestosql.operator.Driver.lambda$process$9(Driver.java:310)
	at io.prestosql.operator.Driver.tryWithLock(Driver.java:675)
	at io.prestosql.operator.Driver.process(Driver.java:309)
	at io.prestosql.testing.LocalQueryRunner.executeInternal(LocalQueryRunner.java:656)
	at io.prestosql.testing.LocalQueryRunner.lambda$executeWithPlan$3(LocalQueryRunner.java:611)
	at io.prestosql.transaction.TransactionBuilder.execute(TransactionBuilder.java:150)
	at io.prestosql.testing.LocalQueryRunner.inTransaction(LocalQueryRunner.java:623)
	at io.prestosql.testing.LocalQueryRunner.executeWithPlan(LocalQueryRunner.java:611)
	at io.prestosql.testing.LocalQueryRunner.execute(LocalQueryRunner.java:605)
	at io.prestosql.tests.AbstractTestQueryFramework.computeActual(AbstractTestQueryFramework.java:118)
	at io.prestosql.tests.TestQueryPlanDeterminism.computeActual(TestQueryPlanDeterminism.java:94)
	at io.prestosql.tests.AbstractTestQueryFramework.computeActual(AbstractTestQueryFramework.java:113)
	at io.prestosql.tests.TestQueryPlanDeterminism.computeActual(TestQueryPlanDeterminism.java:87)
	at io.prestosql.tests.AbstractTestQueries.testApproxPercentile(AbstractTestQueries.java:712)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:645)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:851)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1177)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

Here's an updated PR with the comments applied: https://github.com/prestosql/presto/pull/1168. Closing this one.

ok thanks. it's been somewhere on my to-do list but haven't found time.
in particular I wanted to get to setting up a containerized environment I could develop&test from, do you have any recommendations there? maybe an official dev presto docker image or the like?

What OS are you running? If you're developing on MacOS or Linux, you shouldn't need a containerized environment. All you need to be able to build Presto is Java, Maven and a checkout of the Presto codebase. I'd also suggest using IntelliJ as your IDE -- it's what all Presto developers use currently.

for Spark I ran into a problem on Mac of having the wrong Java installed &
have only had bad experiences trying to mess around w Java versions so I
figured it'd be simpler to run Docker.
At home I'm on Linux Mint & more comfortable messing around but my home
setup is not the greatest at the moment
On Wed, Jul 24, 2019, 8:58 AM Martin Traverso<EMAIL_ADDRESS>wrote:

What OS are you running? If you're developing on MacOS or Linux, you
shouldn't need a containerized environment. All you need to be able to
build Presto is Java, Maven and a checkout of the Presto codebase. I'd also
suggest using IntelliJ as your IDE -- it's what all Presto developers use
currently.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/prestosql/presto/pull/765?email_source=notifications&email_token=AB2BA5OLZST2GFLHLPNVIBDQA6SLBA5CNFSM4HMUTZJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2U27MI#issuecomment-514437041,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2BA5POWXZNX4TEODPKDSDQA6SLBANCNFSM4HMUTZJA
.

@MichaelChirico instructions for running from IntelliJ: https://github.com/prestosql/presto/#running-presto-in-your-ide
running Presto in Docker:
# Build Presto the fastest way known to me
./mvnw -pl '!presto-server-rpm,!presto-docs,!presto-proxy,!presto-testing-server-launcher' clean install -TC2 -DskipTests -Dmaven.javadoc.skip=true -Dmaven.source.skip=true -Dair.check.skip-all=true

# Run Presto with tpch and hive connectors installed & configured
# `presto-master` container is configured to expose 8080 port
./presto-product-tests/conf/docker/singlenode/compose.sh up hadoop-master presto-master

# Execute CLI (the `--catalog hive --schema default --user hive` part is totally optional):
./presto-cli/target/presto-cli-*-executable.jar --debug --catalog hive --schema default --user hive

# ... or inside docker container:
./presto-product-tests/conf/docker/singlenode/compose.sh run application-runner /docker/volumes/conf/docker/files/presto-cli.sh --debug --catalog hive --schema default --user hive

have only had bad experiences trying to mess around w Java versions so I
figured it'd be simpler to run Docker.

If you don't want to have Java on the host, you will need somehow to build Presto in docker container.
You can easily mount workspace in container and run ./mvnw ... inside, but my experience
(with Docker on Mac) is that it's prohibitively slow. It looked to me like file access is much slower.

Thanks @findepi very helpful!


feat: update configuration to deploy readme.md

🙋 Feature Request
When publishing .NET Templates, a configuration update is required in order to automatically include the readme.md documentation during the push to NuGet.org.  For reference.

🤔 Expected Behavior
Deploy readme.md as package template root readme.

😯 Current Behavior
Requires manual upload from *.csproj\readme.md

💁 Possible Solution
Update .nuspec or .csproj or other files to configure appropriately.

🔦 Context

💻 Examples

This is automatically done through the .nuspec files


Warning: Each child in a list should have a unique "key" prop

My react app looks like this:
import React from "react";
import "./App.css";
import { Client, Resource } from "ketting";
import { KettingProvider, useCollection, useResource } from "react-ketting";
const client = new Client("http://localhost:5000/");

export type Customer = {
  customerId: string;
  name: string;
};

const CustomersView = () => {
  const { loading, error, items } = useCollection<Customer>("/customers");
  if (loading) return
Loading...
;
  if (error) return
{error.message}
;
  console.log("items", items);

  return (

      {items.map((item) => (
        <CustomerView resource={item} />
      ))}

  );
};

function CustomerView({ resource }: { resource: Resource<Customer> }) {
  const { loading, error, data } = useResource(resource);

  if (loading) return
loading...
;
  if (error) return
boo
;

  return (

      {data.customerId} - {data.name}

  );
}

export function App() {
  return (
    <KettingProvider client={client}>
      <CustomersView></CustomersView>
    </KettingProvider>
  );
}

export default App;

Everything works but react throws a warning at runtime:
Warning: Each child in a list should have a unique "key" prop.

Check the render method of `CustomersView`. See https://reactjs.org/link/warning-keys for more information.
CustomerView@http://localhost:3000/src/App.tsx?t=1618102718401:69:22

The warning refers to this block

      {items.map((item) => (
        <CustomerView resource={item} />
      ))}

I know I need to e.g. set <CustomerView resource={item} key={<customerId>} /> but I don't have access to the Customer instance here because item is of type Resource<Customer>.
How do I solve this?

Every Resource has uri property, so that's an excellent key!

Yes, that's even better, thanks!


[Documentation Update]: Want to add security policy

Is there an existing issue for this?

[X] I have searched the existing issues

Issue Description
Add security file in.md extension
Suggested Change
Add security
Rationale
No response
Urgency
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

please assign me the issue
@Trisha-tech


compatible document navigation plug-ins

能否兼容文档导航插件，属性面板放在下面，文档导航放在上面

I have never used that plugin. I guess both attach themselves to the same container and whichever is called first will then be the first 🤔
I will take a look and try to find if there is an easy solution.

DOM

On the other hand, I think the attributes panel should also be like the document navigation plug-in, behind the .property-top, because when I added the document to the flashcard review, the properties panel was also highlighted

Hope div.plugin-database-properties-wrapper can behind .protyle-top

Good idea and input. I'll try out what that looks like and if it's feasible.

I've tried adding the HierarchyNavigate plugin and with the changes from 0.4.0 the order of the two plugins looks better. But it might just be luck on my side 🤷♂
Can you confirm @Achuan-2?

it looks great！


Nav Items only created on the first 2nd level menu.

On Windows, getting a issue where the 3rd level headings are not being created after the 1st 2nd level heading.
I have the following menu structure in doctor.json
"menu": {
        "QuickLaunch": {
          "items": [{
            "id": "bestpractice",
            "name": "Best Practices",
            "url": "",
            "items": [{
                "id": "solutions",
                "name": "Solutions",
                "url": ""
                },
                {
                "id": "canvas",
                "name": "Canvas Apps",
                "url": ""
                },
                {
                "id": "model",
                "name": "Model Driven Apps",
                "url": ""
                }]
            },
            {
            "id": "processes",
            "name": "Processes",
            "url": ""
            },
            {
            "id": "accelerators",
            "name": "Solution Accelerators",
            "url": ""
            }]
        }
    }

The following page menu item gets created:
menu:
  QuickLaunch:
    name: "Power Platform Default Publisher"
    id: defaultpublisher
    weight: 4
    parent: bestpractice/solutions

The following page menu items don't:
menu:
  QuickLaunch:
    name: "Control Naming Conventions"
    id: controlnaming
    weight: 4
    parent: bestpractice/canvas

or
menu:
  QuickLaunch:
    name: "Entity Naming Conventions"
    id: controlnaming
    weight: 4
    parent: bestpractice/model

I also tried adding it to doctor.json and it doesn't get added:
        "QuickLaunch": {
          "items": [{
            "id": "bestpractice",
            "name": "Best Practices",
            "url": "",
            "items": [{
                "id": "dataverse",
                "name": "Dataverse",
                "url": ""
                },
                {
                "id": "solutions",
                "name": "Solutions",
                "url": ""
                },
                {
                "id": "canvas",
                "name": "Canvas Apps",
                "url": "",
                "items":[{
                    "id": "namingconventions",
                    "name": "Naming Conventions",
                    "url": "bestpractice/namingconventions.aspx"
                }]
                },
                {
                "id": "model",
                "name": "Model Driven Apps",
                "url": ""
                }]
            },
            {
            "id": "processes",
            "name": "Processes",
            "url": ""
            },
            {
            "id": "accelerators",
            "name": "Solution Accelerators",
            "url": ""
            },
            {
            "id": "workshops",
            "name": "Workshops",
            "url": ""
            }]
        }
    }```

Great catch @P3N-101 - This should now be fixed in the latest beta.

Love the project... Now we just the Markdown webpart to support the latest version of markdown.js and have github styling... How awesome would that be...

Thanks for the verification.

It would already be great if they would allow more configuration options. As currently, the SP web part restricts a lot.
We can always create our own web part which would be installable from the tool.


Update Tutorial.md

(https://heretto.com/wp-content/uploads/2020/12/CSS-Feature-Image-1080x675.jpg) this link is no longer working hence the tutorial.md showed no image of CSS. So added link for different image which fixes the issue.

That image is not required so it would be better if you will remove it and push the changes


GTDB 207 Kraken db vs maxikraken2_1903_140GB db classification rate

Hi,
I have some trouble understanding the differences in classification rates between your GTDB 207 release Kraken database and the widely used maxikraken db from 2019, which is roughly half the size. I am classifying ~150 human stool sample metagenomes with kraken2 (2.1.2), using a 0.75 confidence score and default parameters otherwise and am consistently getting a ~10% higher unclassified rate with the GTDB database.
This seems to stem a higher classification rate of bacteria in the maxikraken db. On the other hand I do get substantially higher sensitivity for Archaea with the GTDB one.
Example (only highest levels):
GTDB 207:
 37.77  12279770        12279770        U       0       unclassified
 62.23  20227993        68658   R       1       root
 62.01  20159210        3273025 D       609216830         Bacteria
  0.00  125     0       D<PHONE_NUMBER>        Archaea

maxikraken:
 26.57  8637310 8637310 U       0       unclassified
 73.43  23870453        5007    R       1       root
 73.19  23793211        1103748 D       2           Bacteria
  0.00  68      0       D       2157        Archaea
  0.00  68      0       D       2759        Eukaryota
  0.00  257     0       D       10239     Viruses

I am confused as to why that is. I could understand that, given the much higher information content in the GTDB db, some classifications would be 'pushed' higher in the tax hierarchy with the confidence threshold used, as it turns out that with more data some k-mers aren't specific/unique for a taxon at that rank anymore. But since in my case they aren't even pushed to the root node but to unclassified, it seems to me that there are quite some k-mers that are just entirely missing from the GTDB db but present in the maxikraken one? Is this expected?
Best
Oskar

The basic answer is the difference in representation between the 2 databases. You should be able to determine how microbial detection differs at resolved taxonomic levels (e.g., genus) by comparing the abundances of taxonomic groups classified by each database (e.g., x-axis: genus-gtdb, y-axis: genus-maxkraken, point size or color: median relative abundance across metagenome samples).
I'm guessing that the maxkraken database is more biased towards certain bacteria, especially well-characterized ones that are often found in the gut, while the GTDB includes a very broad representation of microbes found in all biomes.


Add per instance locking to get_instance

Closes #1183.
Benchmarks didn't change much, if at all, after these changes.
Not sure we should merge this, as it adds complexity without clear advantages. Tried it with different number of threads / contracts, without seeing significant differences in performance in any scenario.

I't unfortunate this needs even more locking in order to avoid other locking.

My thoughts exactly.

From my point of view we can close this. Any additional thoughts?

No. Closing in earnest.


AddToQueue method plays the specific track directly

Hi,
when I call the method with a Spotify-Uri the actual track (currently playing in the application and stored in the queue) gets stopped and the specified track behind the uri starts playing (+ queue gets cleared). Is this the right behavior?
When I add a track to the queue in the Spotify application via context menu it is get set behind the current track and all "next titles" remains.
Best Regards

Hi,
This method is quite experimental.
It worked when I tested it months ago, but then suddenly it behave strange and just played the song. Spotify might changed something on their side (maybe need to update parameters or sth).
When I have more, I will look at it and check if we can fix it :+1:
(Marked it as obsolete for now, so there is no further obscurity)

Spotify Connect Endpoints are implemented in 2.14.0, which also has some kind of queuing AFAIK


Remove branch requirement for deployments, since it seems broken in combination with tags

This fixes the fact that AppVeyor currently does not upload releases even though they are tagged. Apparently the branch name is replaced by the tag name (in contraditiction with their examples...)

Also proposing that we remove the two deployments I created while testing :)

:+1:
Sounds good. Will you remove the releases?

Done! First real release released :smile:


Refactor the CacheableResponsePlugin to a separate class

R: @addyosmani @gauntface
This is part of #282, in which the Plugin classes are refactored to extend a base class, and expose the lifecycle methods.
In addition to refactoring, it also adds tests, as this module was previously untested.

I've changed one of the names, and I also realized that adding some logging would be a good idea.
Let me know your thoughts about the other variable names.


Why do they call it oven when you of in the cold food of out hot eat the food?

@nickname2002 What about a microwave? That is not micro at all, it is quite large actually!

@nickname2002 What about a microwave? That is not micro at all, it is quite large actually!

Maybe you put micro things into it

@nickname2002 What about a microwave? That is not micro at all, it is quite large actually!

Maybe you put micro things into it

The things I enter into the microwave are actually quite large, such as a bapao last night!

I am also having this issue, is there a fix yet?

@MartV0 after a weeks of research and a lot of guidance from professionals within the field, I can confidently say that this is probably the solution:
"When food cold out, eat food the cold, in not out oven hot. So, when hot in oven food, you out hot food eat, and of cold out food, whereby, food hot is."

That makes a lot of sense, thanks!
AI could never make something that makes so much sense.

Good to hear a fix has been found.
Does anyone know where I the oven can Catppuccin theme?

@MartV0 after a weeks of research and a lot of guidance from professionals within the field, I can confidently say that this is probably the solution:
"When food cold out, eat food the cold, in not out oven hot. So, when hot in oven food, you out hot food eat, and of cold out food, whereby, food hot is."
Source: definitely not AI

I'm having a stronk

elephant says meow

Meow meow meow meow


test: fixed test cases of potential duplicates filter

Clickup
https://app.clickup.com/t/86cw7ngz0

@devendrafyle unit tests are still breaking. Are you fixing those in incremental PRs?

Ohh okay, can ignore. that is the percentage which is failing


PRE-BUILDING ON WINDOWS

Command prompt -
Happily prebuilding windows
Writing build log to: C:\Users\Jesson\AppData\Roaming\npm\node_modules\rapidgame\build.log
key (inside func)=2.0
checking version = 2 against highest 0
key (inside func)=14.0
checking version = 14 against highest 2
key (inside func)=12.0
checking version = 12 against highest 14
key (inside func)=3.5
checking version = 3.5 against highest 14
key (inside func)=4.0
checking version = 4 against highest 14
Final MSBuildToolsPath: C:\Program Files (x86)\MSBuild\14.0\bin
Building Windows Debug cocos2d-win32.vc2012.sln...
Succeeded.
Building Windows Debug libJSBinding.vcxproj...
Build failed. Please run with --verbose or check the build log: C:\Users\Jesson\AppData\Roaming\npm\node_modules\rapidgame\build.log
Error from the build log -
C:\Users\Jesson\AppData\Roaming\npm\node_modules\rapidgame\src\cocos2d-js\frameworks\js-bindings\cocos2d-x\cocos\base/CCConsole.h(42): fatal error C1083: Cannot open include file: 'thread': No such file or directory [C:\Users\Jesson\AppData\Roaming\npm\node_modules\rapidgame\src\cocos2d-js\frameworks\js-bindings\cocos2d-x\cocos\2d\libcocos2d.vcxproj]
I can't pre build rapidgame after installing, any ideas?

Did you run as administrator?

I'm having the same problem. The verbose mode outputs this ...
"error MSB8020: The build tools for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please install Visual Studio 2010 build tools."
And I have Visual Studio 2015 installed.

Are you able to compile the cocos2d-x test project with Visual Studio 2015? Last I heard cocos2d-x doesn't work with the 2015 version, but they may have fixed it as of 3.7.

3.7 works fine at least, haven't tried 3.6. Rapidgame still uses 3.6 I guess?

It did, yes. I just published version 0.9.10 that uses 3.7.

Also, the newest version of RapidGame (now 0.9.11) allows you to manually set the path to the VCTargetsPath directory, which is likely related to the build tools path error you experienced. Just upgrade rapidgame (npm update rapidgame -g) then attempt to prebuild. If it fails you can navigate to <username>\AppData\Roaming\npm\node_modules\rapidgame and manually edit vctargetspath.txt.
Closing this issue for now. Feel free to reopen if needed.

Nope, still same problem. Now (with 0.9.,11) it just gives error from v140 tools.
Also all those paths in .txt files looks valid to me. Weird...
Here is the build.log
http://pastebin.com/9pKE4VYQ
I'm running on Windows 10 if that matters anything.
I can also build template projects made with cocos console just fine.

It looks like you need to manually edit your vctargetspath.txt. Maybe change it to v120?

The path in vctargetspath.txt was actually already pointing to that
Now I changed msbuildpath to 14.0 from 12.0
"C:\Program Files (x86)\MSBuild\14.0\bin\MSBuild.exe"
And vctargetspath to V140 from V120
"C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140"
In both cases, 12.0 and V120, the folders and files are there, but for some reason it is not working.
But now when I open the Visual Studio project from the newly created rapidgame project it throws the same error
warning  : The build tools for Visual Studio 2010 (v100) cannot be found. To build using the Visual Studio 2015 (v140) build tools, either click the Project menu or right-click the solution, and then select "Upgrade Solution...". Install Visual Studio 2010 (v100) to build using the Visual Studio 2010 (v100) build tools.
I tried to upgrade the project to 2015 version, but I'm unable to build the template project as it gives some errors.

Good. The prebuild is now working and it's an easy fix to get rapidgame.js to recognize 14.0 and v140.
Next will be to fix the template project. Any chance you could post your template project's upgraded vcxproj file? It should have some lines that will detect and use the 14.0 version tools. Moreover, it should be backwards compatible. I will then take a look at the errors. Also can you tell me which errors you are getting? (Only the first few if you are getting lots of them.)

https://dl.dropboxusercontent.com/u/1641946/rapidgame/TestProject.vcxproj
There is just error one at the beginning.
Error C2872 'Game': ambiguous symbol	TestProject c:\users\ossir\documents\projects\testproject\projects\appdelegate.cpp	62
That line is
Game::setContentRect(contentRect);
I quickly tried to comment that line out, but then it will give you some more
Error LNK1104	 cannot open file 'libpng-2015.lib' TestProject	C:\Users\ossir\Documents\Projects\TestProject\Projects\windows\LINK	1

Thanks, will start working on the fixes. Here's instructions on how to fix those two errors if you like:

Comment out the friend class Game in 0.9.11\cocos2d\x\include\cocos\base\CCProperties.h.
Copy all the *-2015.lib files from src\cocos2d-x\build\Debug.win32 into 0.9.11\cocos2d\x\lib\Debug-win32\x86.

Ok, got it running.
There was file called libpng-2015.duplicate-lib. I renamed that to libpng-2015.lib

Awesome!

Fixes are checked in, tested and part of 0.9.12.


Define what constitutes a 'Vertical' for the VMR build

Unified Build specifies that the product should be built as a series of verticals. A vertical is built on a single machine. A good example of such a vertical would be the Linux distro source-build vertical.
We need to determine what will constitute a vertical. When should a new vertical be created and when should new build features be added to an existing vertical? There are some 'obvious' boundaries between verticals. A difference in build host (Mac vs. Linux) would identify a place where a vertical boundary must be drawn. There are less obvious, but possible boundaries, though:

Target architectures in context of a host that can cross build all targets (e.g. win-x64 vs. win-arm64 vs. win-arm32)
There are multiple runtimes redistributed as part of the .NET product (mono, AOT).

There are also likely places where a boundary cannot be drawn because of single-instance restrictions. For instance, let's say that windows-x64 and windows-arm64 builds create MSI containing the same set of binaries. They essentially install the same product Those MSIs are then chained into two other MSIs that could be installed on the same system. It may be necessary that the chained MSI only be built once. While I believe these issues to be few and far between, and more likely represent artifacts that should be built at a join point (e.g. in this case, the parent MSI would be built in the join), it is worth calling out.
We should create a definition that:

Creates vertical boundaries where they are required, while adding other possible boundaries that
Allow for reasonable efficiency gains by increased parallelism (building the same thing multiple times), without
Introducing a large quantity of verticals that may compromise reliability

This vertical definition should be able to be applied cleanly across the product.
In addition, vertical build implies some level of "overbuilding". Our RID agnostic assets would be built multiple times. Much of the time, these are just getting packaged up into a unique asset that would be built only on one vertical. For example, roslyn might be built 10 times, but packaged into as many SDK layouts built on unique verticals (i.e. you only build the linux-x64 and win-x64 SDKs once in separate verticals, and build the roslyn inserted into those SDKs on each of the verticals). There will be cases where a distributable asset (e.g. NuGet package) is built on multiple verticals. It is important to have a definition of "which asset wins" when selecting what Microsoft ships. For instance, if System.Text.Json.nupkg is built on every vertical (being RID agnostic), which one actually gets shipped to customers?
Objectives

[ ] Create and document a concise definition of what a vertical constitutes.
[ ] Identify existing set of verticals in .NET
[ ] Define how we select duplicate distributable assets from the verticals.

T-Shirt Size: Small (remaining work)

I think it's important to make a distinction between verticals in an official build (maybe even PR builds too) and local build context. In an official build, it is about defining the right boundaries so that we can produce artifacts that make up the product in the most efficient way possible. Locally, it's more about how I can build a certain slice of the product the fastest so that I can validate a change, run tests, etc. In other words, what we mean by vertical can and should be different.
Up until this point, our conversations about verticals have been mostly desktop centric. Let's build everything that falls out from osx-x64, for example. Easy to reason about.
Here's what a makeup of that vertical in the official build could be. This is assuming that we are able to build runtime within the VMR more than once:

CoreCLR osx-x64
NativeAOT osx-x64

iOS NativeAOT arm-64
iOS Mono arm64

MacCatalyst x64
MacCatalyst arm64

OSX x64 iOS Cross Compiler
OSX x64 MacCatalyst Cross Compiler

Android x64
Android arm64

OSX x64 Android Cross Compiler
OSX x64 Android Cross Compiler

Within the above list, there are two different categories of artifacts. One that makes up the desktop product we want to ship and packs, tools, etc that typically come after the fact from nuget / some other place.
The local build on the other hand, should be much more targeted by default. For example, I'm just making a change in the SDK, I'd usually want an osx-64 SDK with a coreclr runtime. If I targeted iOS, I'd want an osx-64 SDK with all of the supported iOS runtime packs. That way, when I produce a self-contained iOS app, it would pull in the nugets I just built.
What I'm trying to say is our vertical make up should be about efficiency. Can the VMR handle a bunch of different runtime builds (or whatever other repo) multiple times or is it better to draw some sort of line and build a subset of the VMR in a different job?

Another thing to think about is fragility. If we take everything under the heading osx-x64 (build host?) and the current runtime build is not designed to build all the variants in a single invocation, then:

I'm giving up some efficiency since I need to invoke it multiple times and
We may potentially hit fragility issues since the build isn't being run in a clean environment each time.

I'm not arguing explicitly against such a definition of a vertical, but we should take those points into account.
Do you have any idea what a build time for runtime would be if you built all that in osx-x64 (excluding tests and other things that don't explicitly contribute to the shipping product).

In the table below, a "Tall Stack" is a full SDK build (build through installer). When building a short stack, the build is only run through runtime.

Vertical Name
Build OS
Target OS
Build OS Arch
Target Arch
Short Stack/Tall Stack
Key Artifacts
PoC Complete?


Super Category Pages STAGING

Staging version of https://github.com/parameter1/pmmi-media-group-websites/pull/686

 Super Category Pages


[docs][material-ui] Improve nav link tab example

Closes: #35388
An alternative to #35597
Preview: https://deploy-preview-38315--material-ui.netlify.app/material-ui/react-tabs/#nav-tabs

No, I don't think so, the point is that SEO and Cmd + click points to the right page.


Frequency unit

Have you guys chosen the appropriate unit of frequency? In our case, G1, we assigned that as cycle per month averages. Please let us know about yours so that we can compare our results, particularly for unit.

I am not sure about this unit, we have to give some thoughts on this.


zenodo prep

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

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

Totals

Change from base Build<PHONE_NUMBER>4:
0.0%

Covered Lines:
35745

Relevant Lines:
38429

💛  - Coveralls


SP DatabaseBackup: compress not accepted

SP databasebackup states 'compress=Y is not allowed'. Well, it works fine. I checked that by removing the check on the compress parameter in the SP. And indeed, backup is 75% smaller.
SQL Server version and edition
ProductVersion: 15.0.4123.1
Edition: 2
EditionId: -1534726760
Version of the script
2020-12-31 18:58:56
What command are you executing?
EXECUTE [dbo].[DatabaseBackup]
@Databases = 'RSA',
@Directory = @location,
@BackupType = 'FULL' ,
@Verify = 'Y',
@Compress='Y' ,
@CleanupTime = 72,
@CheckSum = 'Y',
@LogToTable = 'Y'
What output are you getting?
The value for the parameter @Compress is not supported.

Is this issue still happening?

I dont know, i switched off the check in the procedure.
Op vr 31 dec. 2021 om 19:34 schreef Ola Hallengren @.***

Is this issue still happening?
—
Reply to this email directly, view it on GitHub
https://github.com/olahallengren/sql-server-maintenance-solution/issues/526#issuecomment-1003432908,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHBVXJ3JZLPDTWZCCZOJLDUTXZS7ANCNFSM44X5ES5A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
<olahallengren/sql-server-maintenance-solution/issues/526/1003432908@
github.com>

I dont know, i switched off the check in the procedure.
Op vr 31 dec. 2021 om 19:34 schreef Ola Hallengren @.***

Is this issue still happening?
—
Reply to this email directly, view it on GitHub
https://github.com/olahallengren/sql-server-maintenance-solution/issues/526#issuecomment-1003432908,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHBVXJ3JZLPDTWZCCZOJLDUTXZS7ANCNFSM44X5ES5A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
<olahallengren/sql-server-maintenance-solution/issues/526/1003432908@
github.com>

I am not able to reproduce it, with the version and edition that you have.
Could you try to enable the check again? If you get the error, please post the complete output.

I am not able to reproduce it, with the version and edition that you have.
Could you try to enable the check again? If you get the error, please post the complete output.

Hello Ola,
sorry for the late reply. It works now. Maybe it did not work because on
server level 'compress' was not enabled. Thanks for replying.
Regards
Frank
Op za 1 jan. 2022 om 19:43 schreef Ola Hallengren @.***

:

I am not able to reproduce it, with the version and edition that you have.
Could you try to enable the check again? If you get the error, please post
the complete output.
—
Reply to this email directly, view it on GitHub
https://github.com/olahallengren/sql-server-maintenance-solution/issues/526#issuecomment-1003599414,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHBVXK6ZO4RBBT2ADEZCQ3UT5DONANCNFSM44X5ES5A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
<olahallengren/sql-server-maintenance-solution/issues/526/1003599414@
github.com>

The server - level 'backup compression default' should not matter here.
In any case, I am not able to reproduce the issue.


Changed &mut PipelineCache to &PipelineCache

This was missed in #7205.
Should be fixed now. 😄
Migration Guide

SpecializedComputePipelines::specialize now takes a &PipelineCache instead of a &mut PipelineCache

bors r+


ds.filter = None when loading from HDF5

Original report by Galen O'Neil (Bitbucket: oneilg, GitHub: oneilg).

This causes phase_correct_2014 to fail, since it tries to use ds.filter.filt_noconst and that doesn't exist.
In [17]: ds.phase_correct2014(10, plot=True)
channel 1 doing phase_correct2014 with 50000 good pulses
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-17-6eac86ecbaf5> in <module>()
----> 1 ds.phase_correct2014(10, plot=True)

/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/mass/core/channel.pyc in phase_correct2014(self, typical_resolution, maximum_num_records, plot, forceNew)
   1070             prompt = self.p_promptness[:]
   1071
-> 1072             dataFilter = self.filter.filt_noconst
   1073             tc = mass.core.analysis_algorithms.FilterTimeCorrection(
   1074                     data, prompt[g], self.p_pulse_rms[:][g], dataFilter,

AttributeError: 'NoneType' object has no attribute 'filt_noconst'

Original comment by Galen O'Neil (Bitbucket: oneilg, GitHub: oneilg).

better fix for hdf5 failing to populate ds.filter
closes #15


RFC: Add data-file output option

Prompted by issue #303 and PR #304
Add a data-file output option (under Metrics)
Metrics:
.....
-D, --data-file NAME     Create an CSV-formatted data file of response times (nanoseconds)

This produces a data file of response times suitable for analysis such as that described in PR#304.
Example:
datetime, sample, raw, co_adjusted
2021-04-05T14:30:01Z,1,5465,5485
2021-04-05T14:30:01Z,2,,5465
2021-04-05T14:30:01Z,3,,5445

where:

datetime: ISO-8601 date-time stamp of the start of the Goose run. Used to distinguish between Goose runs.  Not used to calculate response times. Not used to debug.
sample: integer, row counter
raw: integer, raw response time (nano-seconds)
co_adjusted: integer, CO-adjusted response time (nanoseconds)

Please see the --requests-file which is intended to provide request-related logs. It can be written in multiple formats, including csv, json, and raw (ie, Rust's debug display of a struct). When I only want a subset of the information, I generally create a json log and then use jq to grab the specific columns I'm interested in.
A datetime field would need to be added, PR welcome.
We don't currently count the rows, I'm not sure what it adds / why it's necessary? As there's lots of threads making requests at the same time we'd have to "fake" it with the counter.
Finally, the individual response times are not adjusted, so the last two rows aren't an option (and this is the same in HdrHistogram). If you review the mitigation section of the README you can see an example of what shows up in the Requests log. Specifically, if the coordinated_omission_elapsed column is non-zero, this metric was generated through coordinate omission mitigation.

BTW: It's also worth noting that I'm reworking the logger logic in this issue which should get merged soon:
https://github.com/tag1consulting/goose/pull/302

Please see the --requests-file

Yes the requests file is a reasonable workaround.
The data file is targeted at analysis uses cases, for questions such as 'Is this latency sample distribution different from a prior run?'

We don't currently count the rows, I'm not sure what it adds

It adds two things:

It aids when truncating k-samples at a common row count. I've added an --append option which will help produced single (stacked) data file for analysis.
It's a ready made index that combined with the date-time should be unique in most cases.

If you review the mitigation section of the README...

Apologies for seeming obtuse, but I found it very confusing.  I'll add comments in the relevant PR.

I'd consider a PR that makes it configurable which fields from a given entity are logged, but for now I think it's enough to just be sure that all necessary fields are included. I don't want to get to bogged down in this just yet when tools already exist that can easily map the --requests-file to what you need.
Due to the way that GooseUser's each run in their own thread, I don't think you're going to find sufficient consistency simply numbering all requests in the order made: this will inherently get shuffled a little each time you run (not due to Goose which works very hard to ensure each test is sequenced the same, but due to whatever Goose is interacting with and the network in between).
Instead, perhaps it would work better to filter by a given GooseUser (they each have in integer ID, starting at 0 and incrementing by 1) and then to compare the elapsed times for requests made by that thread. You could potentially include a per-GooseUser counter to aid in comparisons.

Apologies for seeming obtuse, but I found it very confusing. I'll add comments in the relevant PR.

Not at all: it's new documentation and a work in progress. PRs to improve readability are welcome.

I don't want to get to bogged down in this just yet when tools already exist that can easily map the --requests-file to what you need.

Agree the requests file is a existing workaround.  This is aimed at making it convenient to generate data ready for analysis.
One thought was to alter the RFC to be a generic solution:
--analysis-file NAME  Create an CSV-formatted data file for analysis
--analysis-fields F1,F2,..FN Comma delimited field names to output to analysis-file.  Field names: <TBD>

I don't think you're going to find sufficient consistency simply numbering all requests in the order made

Not a problem. Generally people seem interested in the distributional properties, e.g. the tail, 99th %-tile etc.  For distributional purposes the order requests are made is not relevant, hence the absence of a request time stamp - the datetime field is a 'run' identifier.
While time-series properties are, IMO, of interest, e.g. are slow/fast responses clustered (tests for heteroskedasticity are well established), they are not at this stage the subject of this RFC.
That is for the reason you cite - its not yet clear to us that Goose/Gaggle can generate that data.
Though, as we mentioned elsewhere, it is not clear to us these systems are always ergodic - perhaps that is why we generally see no sophisticated analysis of this type?

Instead, perhaps ...

Hopefully all that analysis is possible given the updated RFC.

PRs to improve readability are welcome.

OK we'll open a RFC to discover direction.

We won't be able to pursue this.


fix: add extension overview page download button

Types

[x] 🐛 Bug Fixes

Background or solution
close #306
实现插件市场详情页的下载按钮，和已安装按钮的逻辑。

Changelog

add extension overview page download button

Codecov Report

Merging #308 (bafe53a) into main (6146569) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #308      +/-   ##
==========================================
- Coverage   59.33%   59.32%   -0.02%
==========================================
  Files        1182     1182
  Lines       72666    72685      +19
  Branches    15056    15062       +6
==========================================
+ Hits        43116    43118       +2
- Misses      26929    26943      +14
- Partials     2621     2624       +3

Impacted Files
Coverage Δ

...nsion-manager/src/browser/vsx-extension.service.ts
0.00% <0.00%> (ø)

packages/extension-manager/src/common/index.ts
0.00% <ø> (ø)

...ackages/terminal-next/src/node/terminal.service.ts
41.44% <0.00%> (-4.72%)
:arrow_down:

packages/core-common/src/node/port.ts
43.93% <0.00%> (-3.04%)
:arrow_down:

Continue to review full report at Codecov.

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

点击安装的时候，左边列表下的 XML 插件状态好像没有关联变化


Support type extensions?

Schema extensions
Type extensions

Closed because there appears to be no demand for that feature. If you need this, please open a new issue.


cmd/compile: feedback-guided optimization

This is an umbrella issue for supporting feedback-guided optimization. This has been discussed offhand in a few other contexts (inlining decisions: #17566, code layout decisions: #20356, language changes: #24204, stack growth: #18138).
It is not clear what the design for FGO/PGO support might look like. In particular, what do the feedback/profile files look like?
@aclements observed during conversation at GopherCon 2018 that in order to preserve reproducible builds and efficiency, the feedback file needs to be hashed by cmd/go along with all other inputs, which suggests that it ought to be committed to version control.
cc @randall77 @ianlancetaylor @aclements @crawshaw @bradfitz @CAFxX (and the list could go on, but I'm sure everyone will find it)

Oh, hey, I have a concrete example of a potentially-relevant case for this, which is a recurring thing that bites people with microbenchmarks, but may also affect real code:
In rare cases, trivial questions of code alignment can produce very large performance differences. I had a test case, at one point, where I had two functions which were getting roughly a 2x performance difference in benchmarking. (As in, one took twice as long as the other.) But the more I experimented, the more confused I became, because it turned out the functions were identical, and I could change which one was faster by reordering them in source.
The microbenchmark case probably doesn't matter, but there are real-world cases where a couple of likely-concurrent hot paths end up with some kind of problem which is entirely a function of the exact location of their code -- I'm guessing either "aligned or not aligned with cache line" or "in same cache-associativity group as other hot paths", but I don't have the expertise to dive into it far enough to be sure.
My guess is that there's some actual specialized code out there where inserting a handful of nops before some specific functions could produce a +/-20% performance change in the program as a whole. Figuring out which ones seems likely to be arbitrarily hard; you'd need some kind of framework for figuring out how to benchmark the functions, and how to benchmark different sets of functions in parallel, and so on.
This is the sort of thing which is a huge amount of work, and which doesn't provide any noticeable benefit until it does, and then it can be inordinately significant. (The big question is whether you end up perceiving it as "sometimes we get lucky and our code runs faster" or "sometimes we get unlucky and our code runs slower").

Here's a related idea I've been kicking around.
Instead of doing running program -> profile -> compiler, add an extra intermediate step: running program -> profile -> optimization file -> compiler. The optimization file consists of optimization information and directives to the compiler.
There are a few advantages to this:

the compiler can stay simpler
being able to inspect and edit the optimizations file directly (or via a tool) will make it easier to understand what is happening, bisect, test, and minimize issues
it opens the door for other mechanisms/tooling to add information and optimizations, such as: offline static analysis, offline human analysis, bespoke profiling techniques, or combining profiles taken across a fleet of machines

Is this the type of thing that could get covered in the “Compiler and Runtime Meeting Notes“ tracking issue #43930 ?
That did seem useful, although I know it takes some work.

CC @josharian
Yeah. I haven't been maintaining that of late. My apologies. (It's kinda fallen on the pile of "stuff I should get to".) I'll try to do better. :)
Having said that it's unlikely that PGO would have made that tracking issue. PGO started in experimental form, and we were only trying to see if it was worth pursuing. Our experimentation and the results from some external groups lead us to believe PGO might make the 2022 roadmap, but we're still trying to figure out what form it will take.

Regarding PGO in the latest .NET 6 release https://devblogs.microsoft.com/dotnet/announcing-net-6/#dynamic-pgo and https://devblogs.microsoft.com/dotnet/announcing-net-6/#dynamic-pgo

@mvdan I'm sorry it seems that there is a lack of transparency by the Go team.  The compiler team at Google hasn't done any work on PGO that is not public.  The code in #49688 was developed entirely independently at Uber.  The compiler team only became aware of it relatively recently when Uber reached out privately.  The public #49688 is a step toward transparency and keeping everybody in the loop.
It would have been better to make a public announcement about it first.  Still, we would now be in the same position anyhow.  The communication on this is a lesson to bear on mind the next time there is a substantial privately developed contribution.  Sorry for the confusion and angst.

Perhaps I'm not seeing the full picture - in https://github.com/golang/go/issues/28262#issuecomment-945837783 it was described that some prototype work was already taking place, and in https://github.com/golang/go/pull/49688#issuecomment-975753265 it seems like the design and coordination with Uber to upstream their work is currently underway.
These updates are certainly welcome, and I'm really excited to see some progress in this space. However, I'd like to clarify that I don't think we'd have arrived at the same position anyway. To once again take Josh as an example, he's only learning about developments around this proposal via comments that feel like after-thoughts, leaving him little room to participate or even be kept in the loop with some detail. Which is unfortunate, given he's the author of the proposal and some of its design ideas, and has been one of the most reliable compiler contributors over the years :)
Maybe the way the compiler team functions is indeed to work on this issue privately, and then come out publicly with a proposal document and possibly even a prototype implementation. I'm trying to argue, hopefully in a constructive way, that we should aim to be more transparent and welcoming to external contributors. A good first step would be to post regular and early updates somewhere like https://github.com/golang/go/issues/43930, making it easy for others to be kept up to date in a timely manner. Ideally some of the team's communication channels would be public too, much like golang-tools has been doing for years, but at least weekly written updates are an easier incremental step.

@mvdan I don't think you're missing the picture – there are a few details that could help fill you in, but most of it is all current events.
A bit of background:
The Go Compiler and Runtime team is split between two locations, Cambridge MA (with a small contingent in NYC), and Sunnyvale. The majority of the generics work has been handled in Sunnyvale, and while Go focused on 1.18, Cambridge decided to minimize instability in the compiler and runtime. So, we decided to do some experimentation. While lots of times work is internally motivated by things Google would like to see from Go (like the register ABI in 1.16/1.17/1.18), Google's happy if we just focus on generics right now. CAM decided to spend a small amount of resources to characterize what PGO would give us, but we didn't know if we would go further than experimentation. (and we still don't)
The present day:
About when Cherry started to get numbers from PGO inlining, Uber reached out about a PGO implementation they have. They have been thinking about it for longer than we have, and implemented more than we have with our recent experiments. Uber has expressed that they want to upstream their work, but we don't know it's the right thing for the Go ecosystem as a whole, so we need to take a look at it. I will be honest and say that there are parts of it weren't not sure are a good fit for cloud Go users and embedded Go users, but at first blush lots of decisions they've made sound good. We still need to see what they've got before we make any decisions. I doubt their work will be upstreamed without modification.
That is where we are. Uber wants us to consider their inlining implementation, and we need to take a look at it.
The feedback that the compiler and runtime team could do a better job is correct, but in this instance, I feel like we communicated when we knew things. The PGO work we undertook in 2021H2 was truly an experiment. We do experimentation all the time, and when we can share results (ie, it isn't based on internal Google data), we do.
I hope this explanation helps, and I'm happy to chat at any time.

Thanks, Jeremy - I appreciate the extra updates and context on PGO in this thread, as well as all the work that is happening here.

The Go Compiler and Runtime team

Just so we're clear, this implies only Google, correct? I think that's what I'm trying to get at. People like Josh certainly deserve being considered part of the compiler team, but are repeatedly kept out of relevant threads and video calls simply because they are not employed by Google :)
I admit this is getting off-topic, though, so this will be my last comment on the topic here. I've already outlined how I think you could improve transparency and encourage more significant contributions from non-Googlers, and I'd rather not repeat myself as I don't have much else to add.
I hope it's clear this is not an anti-Google sentiment in any way - but rather, how other companies (like Josh's Tailscale or this thread's Uber) would likely participate more regularly and actively in those teams if they were given an honest chance.

Just so we're clear, this implies only Google, correct? I think that's what I'm trying to get at. People like Josh certainly deserve being considered part of the compiler team, but are repeatedly kept out of relevant threads and video calls simply because they are not employed by Google :)

Sorry, yes. That's how we split things up within google. These are the people within Google who think about the C&RT, don't mean to sound like we're alone in this fight. :)

@mvdan posted a comment at https://github.com/golang/go/pull/49688#issuecomment-1222093959 asking for a tracking bug, and updates on what's going on. This is the right tracking bug.
Apologies for lack of updates, our progress has been very on-and-off with other things going on. The current status here is:

@rajbarik and others at Uber have been prototyping compiler internals of a few different types of optimizations that we could do with profiling data. Their prototype is in https://github.com/golang/go/pull/49688.
@cherrymui, myself, and @aclements have been thinking about what an interface to PGO could look like in terms of profile collection and use via the go tool. We hope to have a concrete initial proposal to post in the next few weeks, which will be a good discussion point and hopefully can accelerate progress around collaboration on optimizations, etc.

The proposal @prattmic mentioned above is filed at #55022 . (Filing a new issue to make it clearer what we are proposing.)
Thanks.

Go already supports PGO, why not close this issue?

The initial PGO work is done at #55022, and some followup works are tracked at #62463. We can close this issue.


MissingRegistration error not handled

Or rather, it's partially handled.  This error may be returned by GCM if registration_id is missing.  Normally this is checked upon entry to plaintext_request/json_request, but because of #66, the registration_id isn't being encoded correctly and so GCM errors out silently.  It should at least be checked in raise_error so that a failure doesn't pass silently to the rest of the app.

Will be fixed by #81


Safari key window AIS-122

Creating a SFSafariViewController and adding a temporary key window was interfering with partners applications:

Losing the keyWindow focus stalled UI initialization.
Controls would lose firstResponder status.
The Facebook login controller wouldn't appear correctly.

This patch fixes those problems.

Again, make sure you tag someone to review this or it's just going to sit around. I'll review now.

I dynamically subclassed the SFSafariViewController so that it would not become the first responder, and so it wouldn't steal the focus from other views or controls.
I do this dynamically at runtime so that we don't have to require that the SafariServices library is linked to the app.
This PR was tested on Xcode 7 and 8, iOS 7/8/9/10.  I tested with both SafariServices linked and not linked.

@derrickstaten It'd be good for you to take a gander at this PR too since you're most familiar with this code.
@E-B-Smith Have you tested that before /v1/install, there's a request to /strong_match? And that this functionality still works as intended?

If this (1) works on iOS 10 (and preferably 9) and does not cause issues compiling on older Xcodes and OSes, then this looks fine to me.

@derrickstaten  Yes, I tested this code on iOS 7/8/9/10 and Xcode 7 & 8.  That's why the storyboards were updated.


Add set text analyser for MySQL lexer

This PR ports pygments MySQL text analysis to chroma/go. Original code can be found at: https://github.com/pygments/pygments/blob/master/pygments/lexers/sql.py#L752
The current pygments analysis seems to be wrong according to some reasearch on the documentation and local testing. There's no way to use square brackets to compound MySQL queries. As it's a veredict I removed all the logic comparison between square brackets and backticks. Here's the PR opened for pygments.
https://stackoverflow.com/a/9719904/833531
https://dev.mysql.com/doc/refman/8.0/en/identifiers.html
Fixes: wakatime/wakatime-cli#91

What I wanted to say here is, that we have to return 0.5 to have the same behavior like the pygments implementation.

@dron22 I reverted back to the original porting from Pygments. Could you please review it?


Add sqlalchemy-hana to genericsql

Status
Ready/In Progress/In Hold (Reason for hold)
Related Content Pull Request
Related PR: link to the PR at demisto/content
Related Issues
Related: link to the issue
Description
As a result of the issue, I added support for sqlalchemy-hana to
genericsql.

The PR is pending approval

Still pending approval

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: RotemAmit:x: JudahSchwartzYou have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: RotemAmit:x: JudahSchwartzYou have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: RotemAmit:x: JudahSchwartzYou have signed the CLA already but the status is still pending? Let us recheck it.


Include pre-compiled definitions

This allows us to include the package into our projects without having to run the build script on post install, which is somewhat slow.
I'm unsure if this is how you wanted the setup to be but I feel it makes using the package more straight forward.

I updated the the package to build on prepublishOnly. Supporting multiple versions is going to be more complicated and not immediately useful for most people. I suppose we're going to need a base definition file of whatever lowest patch we want to support, then include additional definitions for the changes in each patch similar to how lua-types handles it.


False image delegation in sharing method

Hi Lukas, thank you again for Camera Roll.
I have two bugs but I can't properly reproduce them at the moment 😱  :

Sometimes wrong images are selected when I want to share them. It looks fine in Camera Roll but when I want to share the image, another one is delegated to the other app. I *believe it happens only after I took a new picture.
Reopening Camera Roll and pressing back button freezes the app sometimes.

I'm very sorry that I don't have more details at the moment but maybe you have a clue already.
Thank you in advance

Are you still experiencing these issues?
I couldn't reproduce them.

Hm, I'm not sure but I think it works now.

I was wrong. It still happens in current version on F-Droid (1.0.4?).
I saved an image on Twitter and tried to share it in a direct contact in signal.

Can you consitenly reproduce the issue?

In the last version, I'm still experiencing the issue that if I opened a folder, then use other apps for a while, then come back to camera roll and click on the back button to return to main view, it just gets blank, and i have to close the app and reopen for it to work.

The issue I just mentioned is perfectly described in #191.


Download button won't do anything

After updating to version 1.1.18 and even trying removing it and reinstalling it the download button will not do anything.
Firefox version 88.0.
Once it did managed to download and the resulting file only contained this:
`

`
and no extension (for the file).

Still seems to work for me on Chrome, FWIW, but it did say it required new/updated permissions.

@frozenpandaman @geoleven
Yes, I changed the permission, add a domain cdninstagram.com
Trying to reinstall and still have problems? I tested it and it works.
https://github.com/mittya/media-helper/blob/3b44db4a77933ce94467927da76a3af043d2845b/chrome/manifest.json#L26-L43

I tried it and it still not gonna work.
It is a different problem than before (before version 1.18.0) as stated.

I'm having the same problem with the new version <IP_ADDRESS> on Firefox 88.0.1, the download button doesn't do anything, nothing happens, anywhere on Instagram, it does present the icon like before but clicking on it won't do anything.
The version before would attempt do download but fail and I would need to copy the link and open a new tab to then get the file to download manually, now nothing happens at all.


KeyAction Cell

This PR implements a KeyAction Cell, Component, and front-end infrastructure for binding key combo events in the UI.
Motivation and Context

Issue #112 identified the need to a Cell that could bind key combinations to some action.
NOTE: Together, let's make some examples that are more real-world in the playground just to test this out

Approach

Cells / Backend
On the backend, we introduce a new cell class called KeyAction, whose constructor looks like this:
def __init__(self, keyCmd, callback, wantedInfo=None, priority=4, stopsPropagation=False):

where a given keyCmd is the string representation of either a single key ("X") or a modifier key and other key combination ("Alt+i", "Meta+D", "Ctrl+Y", etc). In the UI, when this key command is pressed, an event will occur and data about it will be sent back to the host KeyAction cell over the socket. KeyAction will then pass that information to any callback parameter that was provided to it, either a lambda or other function that takes a dictionary as the sole arg.
Front End Implementation
KeyListener
We introduce a new class / singleton called KeyListener that knows how to bind these key combinations and add them to the global event listening space in the browser. Because of the way key events work on elements, this needs to be done at the highest scoped level.
KeyListener has two useful methods: start() which binds a single global listener to all keydown events and then re-routes all constituent key combo listeners, and pause() which removes that single global listener. Together these can be used to start and stop listening for any cell-produced key events as needed. By default, we start once the dom content has loaded (see the main.js file).
In main.js, we create a singleton of KeyListener and then add it as a class-level property on Component, such that all components can access it as needed via someComponent.constructor.keyListener. This is, in fact, how the corresponding KeyAction component works.
KeyAction Component
The component KeyAction is a simple wrapper for the Cell data. It uses the constructor.keyListener method described above to bind a keybinding/listener based on the properties specified by the corresponding Cell.
On Non-Displayedness
Because KeyAction does not have any visual component on its own, it does not create any visible UI structure on the front end. This means we have created a new "kind" of cell -- a so called "non-display" Cell, that the UI needs to know to skip over when it comes to trying to make DOM elements in any cell creation handler.
In order to facilitate this, the parent Cell class was given a new property called shouldDisplay which is by default set to True. This information is now passed over the socket on any updateMessageFor composed message, and the front end then has all the info it needs.
How Has This Been Tested?

We have created a simple test in the Playground that will display a timestamp of when the Alt+t keycomo gets pressed.

Screenshots or console output (if appropriate)

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Closes
#112
Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

@braxtonmckee I have responded to your review here and also pushed some requested changes you should know about:

Better documentation about keyCmd values and event data you can request, now in the key_action.py module as commended notes
A blur/focus capability on CodeEditor components, that will force our custom action listener to stop when the editor has focus and to start again when an editor loses focus. This should prevent clashes between registered key listeners in Ace vs KeyAction. They are now totally separate in both implementation and effect.

OK, that sounds good. Needs rebase and squash. I think the code looks good. Testing mac/pc, you just need to run the browser on a mac, not the server, if you want to test out how the key combos will come across...

@braxtonmckee squashed and pushed. CI seems to be failing from some HTTP error but the "real" checks all seem to be passing

Yeah, that's happening more and more. Some pip/coverage stuff.
On Thu, Jul 11, 2019 at 11:29 AM Eric Gade<EMAIL_ADDRESS>wrote:

@braxtonmckee https://github.com/braxtonmckee squashed and pushed. CI
seems to be failing from some HTTP error but the "real" checks all seem to
be passing
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/APrioriInvestments/nativepython/pull/152?email_source=notifications&email_token=AB6OHBF42SS6VIOCLMHQGPDP65GVDA5CNFSM4H6NGBP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZXCJ6A#issuecomment-510534904,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6OHBFVM3BFOSCQXCSSFVLP65GVDANCNFSM4H6NGBPQ
.


Ops-agent with custom metrics

Hi,
what is the preferred way to send custom metrics with Ops Agent? I would like to send metrics containing dockers' containers memory usage. Previously I did it with collectd. Does Ops Agent allow to replace this use case? If not, is there any preferred way to do this now?
Thanks.

The legacy agent (stackdriver) supported this, but did not support logging. This new Ops Agent supports logging, but doesn't support custom metrics. This is a blocker because it seems you cannot install both stackdriver and ops agent at the same time since ops agent deprecates/replaces stackdriver once installed.
This means we can either have custom metrics (which is needed for MIG autoscaling) or service logging, but not both.
Would greatly appreciate someone from Google chiming in on this apparent loss of functionality and what the new procedure is for getting custom metrics collected using ops agent.

There are two feature releases that enable collecting and sending custom metrics with the Ops Agent :

Ops Agent release 2.31.0 - OTLP receiver (Public Preview) - Public Documentation
Ops Agent release 2.25.0 - - Prometheus receiver - Public Documentation


Variadic templates support for tuple

Variadic templates support for tuple. Removed faux variadics support files and flags.

Looks pretty good to me!