Integration with JPhyloRef

Added code that sends the JSON-LD export (implemented in #73) to a server hosted on your local laptop for reasoning (see phyloref/jphyloref#12), and then highlights the results on all included phylogenies by the use of CSS classes. Testing this revealed that the JSON-LD library being used by JPhyloRef couldn't read the JSON-LD context file in phyx.json, so this PR also modifies those so that the Curation Tool is well integrated with JPhyloRef.
I'm holding off on testing the JSON-LD file produced as we can perform ad-hoc testing by seeing if phyloreferences are resolved as expected using JPhyloRef, but this will be tracked by #83.

Thanks for the comments, Hilmar!

Aside from those, I'm wondering whether the communication with the reasoner isn't best implemented through web sockets.

 How does keeping the server connection open make this faster or easier?

Also,, are we putting this on a path to eventually migrate to Owlery, or is Owlery for some reason not going to work.

If we could turn the JSON-LD file the Curation Tool produces into a knowledgebase exposed through Owlery, then we should be able to adapt our existing code to use the Owlery API to look up the instances (nodes) contained in a particular phyloreference class. So one half of the integration is done: we produce OWL ontologies that Owlery should be able to read and reason over. The missing piece is modifying the Curation Tool to read the included nodes via Owlery API calls.

Thanks, Hilmar! I'll go ahead and merge this then. I tried to fix that in this pull request, but that caused the reasoner to fail. So I've filed that as #92 and will take a stab at it later!


Date fields produce no results when searched

Single years tested (2016, 2015, 2014, 2013, 2012) produce a "No Results" page.
Date range 2001-01-01 to 2018-01-01 produces a "No results" page.

Closed -- turns out that I had to rebuild my index after latest doc mapping changes.


Microsoft.OneDrive.Internal.Slow version 23.050.0307.0001

Result: Installation Failed

Manifest
Add/Remove Programs

Name
SchemaCrawler

Version
16.19.9

Publisher
Sualeh Fatehi

ProductCode

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 6812

Installing in a sandbox gives the error:

Manifest Error: The multi file manifest has inconsistent field values. [ManifestVersion] Value: 1.0.0 File: Microsoft.OneDrive.Internal.Slow.locale.en-US.yaml

Hi @vedantmgoyal2009,
These OneDrive PRs always have problems going through validation, and my sandbox won't run them. They appear to be constructed differently than other PRs, as GitHub shows them as removing 2 files from a previous version and adding 2 new files. Is there something unique about these PRs that causes an issue?

Manual Validation failed with:

Installation failed with exit code -2147012867
2023-04-03 13:20:07.531 [CORE] DeliveryOptimization error: 0x80072efd, extended error: 0x00000000
2023-04-03 13:20:07.532 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FF945931EFD: (caller: 00007FF9459327D0) Exception(1) tid(69c) 80072EFD
2023-04-03 13:20:13.046 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(52)\WindowsPackageManager.dll!00007FF9458F12BA: (caller: 00007FF9458F2129) Exception(2) tid(69c) 80072EFD     Msg:[InternetOpenUrl() failed.]
2023-04-03 13:20:13.110 [CLI ] Failed to download, waiting a bit and retry. Url: https://oneclient.sfx.ms/Win/Installers/23.050.0307.0001/amd64/OneDriveSetup.exe
2023-04-03 13:20:24.334 [CORE] DeliveryOptimization error: 0x80072efd, extended error: 0x00000000
2023-04-03 13:20:24.334 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FF945931EFD: (caller: 00007FF9459327D0) Exception(3) tid(69c) 80072EFD
2023-04-03 13:20:26.611 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(52)\WindowsPackageManager.dll!00007FF9458F12BA: (caller: 00007FF9458F2129) Exception(4) tid(69c) 80072EFD     Msg:[InternetOpenUrl() failed.]
2023-04-03 13:20:26.769 [CLI ] Caught wil::ResultException: D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(52)\WindowsPackageManager.dll!00007FF9458F12BA: (caller: 00007FF9458F2129) Exception(4) tid(69c) 80072EFD     Msg:[InternetOpenUrl() failed.]
2023-04-03 13:18:29.579 [CORE] DeliveryOptimization error: 0x80072efd, extended error: 0x00000000
2023-04-03 13:18:29.580 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!5634877F: (caller: 56348E35) Exception(1) tid(1f74) 80072EFD
2023-04-03 13:18:31.864 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(52)\WindowsPackageManager.dll!563096C9: (caller: 5630A6D1) Exception(2) tid(1f74) 80072EFD     Msg:[InternetOpenUrl() failed.]
2023-04-03 13:18:32.005 [CLI ] Failed to download, waiting a bit and retry. Url: https://oneclient.sfx.ms/Win/Installers/23.050.0307.0001/OneDriveSetup.exe
2023-04-03 13:18:43.588 [CORE] DeliveryOptimization error: 0x80072efd, extended error: 0x00000000
2023-04-03 13:18:43.588 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!5634877F: (caller: 56348E35) Exception(3) tid(1f74) 80072EFD
2023-04-03 13:18:45.865 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(52)\WindowsPackageManager.dll!563096C9: (caller: 5630A6D1) Exception(4) tid(1f74) 80072EFD     Msg:[InternetOpenUrl() failed.]
2023-04-03 13:18:45.930 [CLI ] Caught wil::ResultException: D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(52)\WindowsPackageManager.dll!563096C9: (caller: 5630A6D1) Exception(4) tid(1f74) 80072EFD     Msg:[InternetOpenUrl() failed.]

Msg:[InternetOpenUrl() failed.]

This might be due to a datacenter block to prevent automated downloads.


fix: add module name

This MR adds the module name in zephyr/module.yml, as is stated in the official documentation:

Each Zephyr module is given a name by which it can be referred to in the build system.
The name should be specified in the zephyr/module.yml file. This will ensure the module name is not changeable through user-defined directory names or west manifest files.

will do, thanks


Assert in the profiler (Win8.1)

Hello, I have an assert on the example 02_Compute after about 30 seconds.
The Forge targets Win 10 and I'm on a Win 8.1 so that could be the problem.
The failed assert is in the profiler when g_ProfileGpuLog is null, this happens here:
https://github.com/ConfettiFX/The-Forge/blob/3cccad9a1364f5d7a21a245e9334a60234bb5656/Common_3/Tools/Profiler/ProfilerBase.cpp#L150
when the destructor of g_ForceProfileShutdown is called, this is the call stack:
02_Compute.exe!ForceProfileShutdown::~ForceProfileShutdown() Line 150
	at e:\engine\the-forge\common_3\tools\profiler\profilerbase.cpp(150)
02_Compute.exe!`dynamic atexit destructor for 'g_ForceProfileShutdown''()
02_Compute.exe!__dyn_tls_dtor(void * __formal, const unsigned long dwReason, void * __formal) Line 123
	at d:\agent\_work\1\s\src\vctools\crt\vcstartup\src\tls\tlsdtor.cpp(123)

Commenting this line solves the problem:
https://github.com/ConfettiFX/The-Forge/blob/3cccad9a1364f5d7a21a245e9334a60234bb5656/Common_3/Tools/Profiler/ProfilerBase.cpp#L156
So from what I understand, a thread dies, since g_ForceProfileShutdown is P_THREAD_LOCAL it dies too and it resets g_ForceProfileShutdown which is global and not thread local. I don't know what thread dies but it happens 100% after 28 seconds.
Not sure if related, but in the log I see this error every second:
filesystem.cpp:367    ERR| Could not open file \\.\pipe\microprofile-contextswitch
This error starts here:
https://github.com/ConfettiFX/The-Forge/blob/3cccad9a1364f5d7a21a245e9334a60234bb5656/Common_3/Tools/Profiler/ProfilerBase.cpp#L3065
No idea about named pipes, but shouldn't it be created first?
https://github.com/zeux/microprofile/blob/35291b789723221a9740c5b12e4e6a669330a2f9/src/contextswitch_etw/contextswitch_etw.cpp#L79
About Win 8.1, it works great with Vulkan. The only problem is 'GetDpiForSystem' missing in 8.1, it is here:
https://github.com/ConfettiFX/The-Forge/blob/3cccad9a1364f5d7a21a245e9334a60234bb5656/Common_3/OS/Windows/WindowsBase.cpp#L625
but it could be loaded with GetModuleHandle or GetModuleHandleEx+FreeLibrary:
https://github.com/Leandros/tracy/commit/34533ad4f13a5cec77f449c4b2ca200c54800a10
The DX11 works too but only after removing the flags D3DCOMPILE_ALL_RESOURCES_BOUND, D3DCOMPILE_ENABLE_UNBOUNDED_DESCRIPTOR_TABLES from the shader compiler. This seems to cause some errors (MaterialPLayground) and artifacts (LightShadowPlayground).

I believe there's a fix for the crash in the pipeline. You can work around it for now by changing line 100 of ProfilerBase.cpp from:
ProfileThreadLog*			g_ProfileGpuLog = 0;
to
P_THREAD_LOCAL ProfileThreadLog*			g_ProfileGpuLog = 0;

A better fix comes with the next release ... hopefully tomorrow.

On an unrelated note: we are testing more now on a Win 7 box ... so Win 8.1 should be supported better. One of our customers requires Win 7 ...

Thank you for quick replies. That's good, I'll wait for the next release and no worries I'm already all set now.
Feel free to close this.


General code quality fix-2

This pull request is focused on resolving occurrences of Sonar rules
squid:S1155 - Collection.isEmpty() should be used to test for emptiness.
squid:UselessParenthesesCheck - Useless parentheses around expressions should be removed to prevent any misunderstanding.
squid:S2147 - Catches should be combined.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S1155
https://dev.eclipse.org/sonar/rules/show/squid:UselessParenthesesCheck
https://dev.eclipse.org/sonar/rules/show/squid:S2147
Please let me know if you have any questions.
Faisal Hameed

Close/reopen to force travis-ci build.

@nrlakin It looks like there is an issue in travis configuration.
https://travis-ci.org/ResearchStack/ResearchStack/builds/133513442

It builds on the main branch, but Travis appears to be inconsistent in loading the config file if it doesn't exist in the pull request branch. Try merging and updating the pull request.

I don't have rights to merge pull requests.

You don't need to merge, just update the pull request.  There shouldn't be merge conflicts. It's an issue with Travis CI, it isn't finding the .travis.yml file in your branch because it didn't exist when you forked.

@nrlakin Ok, I will rebase my branches from master.

@nrlakin Done.

@faisal-hameed Thank you, I will be dealing with outstanding pull requests in the coming days. Sorry for the hassle, should be a one-time migration issue.

Yes, many apologies for the hassle, @faisal-hameed -- we are still getting our act together with best practices on running this as a community-driven project. Deeply appreciate your contributions!


[Feedback] New Items in Feedback do not get the tools button associated with them

User cannot click tool to add as issue to Github.

Fixed with #206


[OpenRPC] Translate metadata to OpenRPC document

Description:
Generate an OpenRPC document from Frequency/Substrate metadata.
Former OpenAPI project document:
Ref doc link
Acceptance criteria

Valid OpenRPC document that includes all RPC methods
Code should be open source with the possibility of contributing changes to Parity.
Future: #851

Implementation
The implementation will be a fork of Parity's typegen utility which is part of the PolkaDot JS API suite.  The tool will download metadata from a Frequency node and generate an OpenRPC document from it.
OpenRPC
https://spec.open-rpc.org
@polkadot{.js} typegen
https://github.com/polkadot-js/api/tree/master/packages/typegen
** Repository **
https://github.com/LibertyDSNP/polkadot-js-openrpc

The non-trivial issue with this project, regardless of implementation/approach, is the mapping of complex Rust/Substrate types to OpenAPI types.  OpenAPI has a handful of primitive types with Schema Objects for more complex/object types.  It's unclear how the Substrate runtime can automatically perform this mapping.  This is distinct from the overall serialization of the document.  See also: https://spec.openapis.org/oas/v3.1.0#data-types and https://spec.openapis.org/oas/v3.1.0#schemaObject

Is the resulting OpenAPI document limited to just Frequency pallets (msa/messages/schemas) or to the entire runtime?

Additionally, the Substrate metadata doesn't appear to contain any RPC methods.  Therefore, we would need to obtain them separately.
curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method": "rpc_methods"}' http://localhost:9933/ > rpc_methods.json

I asked OpenAI and here's what it said:
Parity Substrate is a blockchain development platform that allows you to build custom blockchains and decentralized applications (DApps). It provides a runtime environment and modular architecture for building and deploying decentralized applications.
OpenAPI (formerly known as Swagger) is a specification for building APIs that enables you to describe the structure and behavior of your APIs in a machine-readable format. It provides a way to document your APIs in a way that is easy for developers to understand and use.
To map Parity Substrate runtime types to OpenAPI types, you will need to consider the data types and structures used in your Parity Substrate runtime and map them to the corresponding OpenAPI types.
Here are some examples of common mappings between Parity Substrate runtime types and OpenAPI types:
Parity Substrate u32 (unsigned 32-bit integer) maps to OpenAPI integer with a format of int32.
Parity Substrate i32 (signed 32-bit integer) maps to OpenAPI integer with a format of int32.
Parity Substrate u64 (unsigned 64-bit integer) maps to OpenAPI integer with a format of int64.
Parity Substrate i64 (signed 64-bit integer) maps to OpenAPI integer with a format of int64.
Parity Substrate bool maps to OpenAPI boolean.
Parity Substrate Vec (vector of elements of type T) maps to OpenAPI array with the items field set to the appropriate OpenAPI type for T**.**
You will need to map any other custom types or structures used in your Parity Substrate runtime to the appropriate OpenAPI types as well.
It may be helpful to reference the OpenAPI specification and the documentation for the data types and structures used in your Parity Substrate runtime to determine the appropriate mappings.

OLD/OBSOLETE NOTES

Implementation: example
Extending codegen tool to create a swagger type generator
Specifically actual logic to convert metadata to document generate_swagger_from_url, where metadata is read from live chain url (example code)
If needed support generating swagger using metadata file similar to codegen
Checkout a simple unit test creating a swagger document

Please add your planning poker estimate with Zenhub @rlaferla

If this is going to eventually be included in the GitHub CI workflow, perhaps we should also obtain the metadata directly from a WASM release asset?

We should create a RPC on the chain to return the OpenRPC document:
{
  "methods": [
    {
      "name": "rpc.discover",
      "description": "Returns an OpenRPC schema as a description of this service",
      "result": {
        "name": "OpenRPC Schema",
        "schema": {
          "$ref": "https://raw.githubusercontent.com/open-rpc/meta-schema/master/schema.json"
        }
      }
    }
  ]
}

OpenRPC types utilize JSON Schema types as specified:
4.2.1. Instance Data Model
JSON Schema interprets documents according to a data model. A JSON value interpreted according to this data model is called an "instance".
An instance has one of six primitive types, and a range of possible values depending on the type:
null:
A JSON "null" value
boolean:
A "true" or "false" value, from the JSON "true" or "false" value
object:
An unordered set of properties mapping a string to an instance, from the JSON "object" value
array:
An ordered list of instances, from the JSON "array" value
number:
An arbitrary-precision, base-10 decimal number value, from the JSON "number" value
string:
A string of Unicode code points, from the JSON "string" value

Should we specify servers in the document?  If so, should it include Rococo in addition to Mainnet?  Or should we do a separate document for each (because they could differ)?

We need to understand what the valid format is for the result section of a method in the OpenRPC JSON document.

We can possibly include Errors in the OpenRPC document.  It needs to be researched and evaluated.

We need to have a discussion around the description fields in the OpenRPC document which is derived from Rust library comments.  We may need to sanitize and better format the comments in the Rust code.

The initial implementation is working but needs more refinement and testing.

There a handful of minor finishing touches that can be implemented:

Output just the openrpc.json file (no output directory) if the --openrpc option is specified.
Add a CLI option for chain title/version
Fill out a few more of the less commonly used complex types for completeness

After some discussion with @wilwade, we are going to see if we can develop a more comprehensive set of types using the TS defs script rather than the TX script that was initially used.


Add Mattermost Icon

Added Icon to the README 💄

Thank you for the contribution @shin-migami!
Attached is how the README file would look like, and unfortunately the icon doesn't fit the title well.. We'd probably need to update the icon so it's better positioned with the "Mattermost Desktop" text.
While we really appreciate your contribution, we'll not be able to take the pull request at this time.
Please consider taking a look at other open issues on the repo, including issues labeled for Hacktoberfest, and consider joining our Desktop community channel to meet other contributors and discuss the future of the project.

Will it be alright if the title is included with the icon so that the whole thing is a icon and it's looks nice ??

Nice suggestion @shin-migami, let me check with the team to see if we'd have an icon that works.

Thank You @jasonblais for going through the trouble

Sorry for the delay @shin-migami, I've sent a question to our UX team and will get back here,
Thank you again for your interest!

Hey there @shin-migami, we can use an image from here: https://www.mattermost.org/wp-content/uploads/2016/03/logoHorizontal.png
We could change the README file to display the icon instead of having "Mattermost" text in the title. What do you think?

@jasonblais The image looks nice, however I think it can't tell that the repository is for desktop app. Any thoughts?

@yuya-oc True, would your thought be adding the icon but keeping the "Mattermost Desktop" in the title?
Or should we hold off on adding a title for now?

@yuya-oc @jasonblais We can just add the "Desktop (beta)" as a subtitle to the title then it would serve all purpose. Please give your thoughts about this.

@jasonblais Please share your thoughts on this

@jasonblais Please share your thoughts on this

Hey @shin-migami, the Mattermost branding guidelines won't allow us to change the icon itself.
I checked other desktop apps and I generally didn't see an icon associated with them, at least for the ones I checked

I seem to have overlooked that. I think we should close this PR then.
Thanks for your time.
On 13 October 2016 at 20:41, Jason Blais<EMAIL_ADDRESS>wrote:

Hey @shin-migami https://github.com/shin-migami, the Mattermost
branding guidelines https://www.mattermost.org/brand-guidelines/ won't
allow us to change the icon itself.
I checked other desktop apps and I generally didn't see an icon associated
with them, at least for the ones I checked
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mattermost/desktop/pull/329#issuecomment-253542803,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ6nhkEbKVcU35JHk3luZKdS-HHvVu0Pks5qzko9gaJpZM4KL8XX
.

Hey @shin-migami and sorry for the back-and-forth here.
If you're not a member, please consider joining our Desktop community channel to meet other contributors and discuss the future of the Desktop project.


cifs-utils causing Depsolve errors with RHEL8

While the initial sudo meza deploy monolith command runs to completion and installs a demo wiki on RHEL8, it seems subsequent runs get cranky with rpm/yum/dnf depsolve issues:

This error occurs in base: Upgrade all packages except python and ansible
I have a feeling cifs-utils is the culprit and adding either EPEL or Rocky-Extras is causing some weirdness. Need to investigate.

This issue seems to be resolved by using the Red Hat-specific ansible-2 repos and not including Rocky-Extras.repo. The rhel8-35.x repo as of commit e35525f should resolve this issue.
Doing some more testing before I close this one.

Tested on multiple runs of sudo meza deploy monolith with no further issues. Resolving.


Feature/pla 370 aws naming conventions

Could you please add a meaningful description? Our PRs normally prompt you to fill out a template with the headings

Summary
Notable Changes
QA

@sldsmkd mind having a look (i added dev,stage,test and live). Are these the only places we use these?

@biggianteye mind having a look a the markdown to see if it make sense?

@biggianteye updated. My changes are based on: https://github.com/DavidAnson/markdownlint

@biggianteye is there anything left to change?

@h-bragg Happy with the changes, though the travis builds are failing.

thats because travis is only setup for another branch currently (although just merged)


XML Data Types Link Broken

https://www.w3schools.com/schema/schema_dtypes_date.asp does not work.

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

ID: c0ec37aa-f814-8277-60b7-0dc4f91834f1
Version Independent ID: c59b6608-e19f-3ee8-8fe6-f47428a13e6c
Content: Azure Diagnostics extension 1.3 and later configuration schema
Content Source: articles/monitoring-and-diagnostics/azure-diagnostics-schema-1dot3-and-later.md
Service: monitoring-and-diagnostics
GitHub Login: @rboucher
Microsoft Alias: robb

@whytoe Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@whytoe Just checking in again.

@MicahMcKittrick-MSFT  can you close this issue?  @whytoe You are welcome to reopen it or create a new issue if this is still problem.  I just need some clarification as mentioned above.


Fix #140 – indicator constraints not being removed

I am not sure this is a good solution. Also, need to extend solution in
case we're adding support for quadratic constraints.

Codecov Report

Merging #144 into devel will decrease coverage by 0.05%.
The diff coverage is 70%.

@@            Coverage Diff            @@
##            devel    #144      +/-   ##
=========================================
- Coverage   89.86%   89.8%   -0.06%
=========================================
  Files           9       9
  Lines        2507    2512       +5
  Branches      553     554       +1
=========================================
+ Hits         2253    2256       +3
- Misses        167     168       +1
- Partials       87      88       +1

Impacted Files
Coverage Δ

optlang/interface.py
91.39% <ø> (-0.03%)
:arrow_down:

optlang/cplex_interface.py
91.52% <70%> (-0.25%)
: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 194caef...2205ad4. Read the comment docs.

fixes #140

@KristianJensen can this be merged?

I’ll take a look at it tomorrow

Den 8. nov. 2017 kl. 09.19 skrev Nikolaus Sonnenschein<EMAIL_ADDRESS>@KristianJensen can this be merged?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Fix S3 Bucket ACL conflict with BucketOwnerEnforced

We received this error when deploying this solution:

ResourceLogicalId:UserImportJobMappingFilesLogsBucket, ResourceType:AWS::S3::Bucket, ResourceStatusReason:Bucket cannot have ACLs set with ObjectOwnership's BucketOwnerEnforced setting (Service: Amazon S3; Status Code: 400; Error Code: InvalidBucketAclWithObjectOwnership; Request ID: 55BAZN6ED158H9A0; S3 Extended Request ID: Xyuo3mSIU9QcRheNg96VLQLZrB8u333eN629//mAEZ+AVRDP7UfBh4KTWq2luwt0AJPInIl/C8BjjvyGi4OKuA==; Proxy: null).

This change to S3's behavior caused this bug: https://aws.amazon.com/about-aws/whats-new/2022/12/amazon-s3-automatically-enable-block-public-access-disable-access-control-lists-buckets-april-2023/
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Fixed in v1.0.2


tiny legs

When I click on accept and return all gifts in the main gift page. It has come up 3 days in a row now that the mouses tiny legs could not retrieve and the attached error

Also, when clicking on accept all, it does not accept all gifts available to be accepted and I have to click the button twice to get all gifts accepted.

am using 24.1 as a tampermonkey script on chrome

I've been noticing a higher number of errors as well.
There's a fix coming for the having to click twice to actually accept all the gifts, hopefully I can fix the errors as well.

Related: #185


Deployment with gunicorn is not possible using host_prefix.

See discussion for #50. The tested setup is:

factgenie commit https://github.com/kasnerz/factgenie/commit/64c54e56089069945c78f89a3143f5b30c96bfe3
python -V   # Python 3.11.5 (I believe anything 3.7+ is fine)
gunicorn (version 22.0.0)

Update the host_prefix in factgenie/config.yml  from " to "have" I replicate the behavior. See the full config below.
(Note that production factgenie/config.yml config should have debug: false.)
---
debug: true
host_prefix: "hidave"
logging_level: INFO
login:
  active: true
  username: admin
  password: factgenie

The server was started with:
gunicorn -w 1 --threads 2 'factgenie.cli:create_app()' --bind <IP_ADDRESS>:8080
The error is for wget:
get localhost:8080/hidave
--2024-07-16 14:44:45--  http://localhost:8080/hidave
Resolving localhost (localhost)... ::1, <IP_ADDRESS>
Connecting to localhost (localhost)|::1|:8080... failed: Connection refused.
Connecting to localhost (localhost)|<IP_ADDRESS>|:8080... connected.
HTTP request sent, awaiting response... 404 NOT FOUND
2024-07-16 14:44:45 ERROR 404: NOT FOUND.

I also tried to fix it with gunicorn -w 1 --threads 2 'factgenie.cli:create_app()' --bind <IP_ADDRESS>:8080 --env "SCRIPT_NAME=/hidave". Note the --env SCRIPT_name=XY based on this answer.
I tried to combine --env SCRIPT with and without using host_prefix in the config, but none worked fully.
FYI @kasnerz

I managed to get this working with the --env SCRIPT_NAME=/myprefix tip! Thanks

I managed to get this working with the --env SCRIPT_NAME=/myprefix tip! Thanks

Hi @dmhowcroft can you pls share with us how?
Here or PM works too.
I would love to use gunicorn further on with prefix

@oplatek I just tried running the app with gunicorn on quest in my nlg virtual machine and it seems to be working without issues.
Can you describe what exactly does not work for you?
My setup when running factgenie on https://quest.ms.mff.cuni.cz/nlg/factgenie/:

nginx config (/etc/nginx/sites-enabled/default)

location /factgenie {
    proxy_pass http://localhost:9989/;
}
location /factgenie/ {
    proxy_pass http://localhost:9989/;
}

config.yml:

host_prefix: "/nlg/factgenie"

To run the app:
gunicorn -w 1 --threads 2 'factgenie.cli:create_app()' --bind <IP_ADDRESS>:9898

@oplatek I just tried running the app with gunicorn on quest in my nlg virtual machine and it seems to be working without issues.
Can you describe what exactly does not work for you?
My setup when running factgenie on https://quest.ms.mff.cuni.cz/nlg/factgenie/:

nginx config (/etc/nginx/sites-enabled/default)

location /factgenie {
    proxy_pass http://localhost:9989/;
}
location /factgenie/ {
    proxy_pass http://localhost:9989/;
}

config.yml:

host_prefix: "/nlg/factgenie"

To run the app:
gunicorn -w 1 --threads 2 'factgenie.cli:create_app()' --bind <IP_ADDRESS>:9989

I was able to run the code successfully by running:
gunicorn --env SCRIPT_NAME=/my_host_prefix -b :80 -w 1 --threads 2 factgenie.cli:create_app()

after the changes specified in this PR: https://github.com/kasnerz/factgenie/pull/53


Set up a way to track bonus payments from surveys, prompts, and other game elemens

When given surveys such as this one:

Need to be able to track and pay the promised bonuses.

Deprioritizing this for now.

For now, choosing not to offer bonus payments this way.


[INSTALL ISSUE] MPI4PY installation bug

MPI4PY installation fails on Candide

This seems to be solved now, see https://github.com/CosmoStat/shapepipe/pull/661


Pool creates many connections when under high contention

Bug Description
The initial symptom of this bug was pools not being at full capacity yet many clients getting kicked back with PoolTimeout errors.
We also noticed total_auth_attempts was very high (20k/s).
Checking netstat, it appeared that a lot (5k+) of connections were being created per second from a single node, and destroyed in quick succession. Most of the connections were in FIN_WAIT (i.e. the application had already closed the socket and the operating system was in the process of cleaning it up).
Further investigation and eyeballing of the code led us to acquire() in inner.rs.
There's a single big timeout around acquiring the semaphore, taking idle connections and creating new connections.
What was happening in our scenario was that there were thousands of clients waiting on the semaphore. If the acquire timeout happened to coincide with the time waiting on the semaphore, they would get the permit, either take an idle connection or start a new one, and then timeout the acquire, cancelling the task and then drops the connection it had created or acquired from the idle pool.
Under heavy pressure, assuming there's some fairness on the semaphore, once this starts happening it will keep happening as the permit acquisitions closest to the acquire timeout will be at the front of the queue.
A quick fix we made was to separate the permit acquisition from the connection acquisition. This may mean waiting 3x the acquire timeout, but that's preferable to hammering our postgres instances.
https://github.com/pinecone-io/sqlx-fork/blob/repro/sqlx-core/src/pool/inner.rs#L247
Minimal Reproduction
There is code to repro the condition here: https://github.com/pinecone-io/sqlx-fork/blob/repro/tests/repro.rs
Run the test for a few minutes, you'll eventually start to see pool size flap around max. Checking the number of tcp connection initialization via tcp dump will show there are a lot. You won't see too many FIN_WAITs in netstat if the postgres is local, as the same kernel owns both ends of the connection.
tcpdump -i lo 'tcp[tcpflags] & (tcp-syn) != 0 and dst port 5432'

Info

SQLx version: 0.7.3
SQLx features enabled: uuid, chrono, postgres, sqlite, tokio-rustls
Database server and version: Postgres aurora engine version 14.8
Operating system: Linux 6.5.0-1014-aws
rustc --version: rustc 1.75.0-nightly

See also: #2848 #2854


Setup semaphore

Hey @kallyas,
Something went wrong with the build.
TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
View build log
TravisBuddy Request Identifier: 8ba8cfb0-d7ff-11ea-bd95-7fd687ac1006


Theme: Using mobile device, can not scroll to bottom of system/ boot up shutdown page (Safari iOS 9)

When using an iPhone 6 on safari I can not scroll to bottom of the boot up shutdown page. Upon touching the screen to continue scrolling, the page automatically returns to the top.

I don't know how to reproduce it as I don't have an iPhone. I will see what I can do, probably ask someone. Are there emulators for that? Because if I use Safari emulation, all works fine?

I should have mentioned, 1.780 and 17.70 are the we min and theme versions.

Other pages scrolled correctly?

Works fine on desktop safari, and on mobile version of chrome.
With mobile safari I get the same behavior on the file manager tab. As soon as I touch the screen a second time to continue scrolling to the bottom, the screen returns to the top. I can never get to the bottom of the page.

That sounds very strange. Are you on iOS beta version?

No beta
Sent from my iPhone

On Feb 17, 2016, at 11:44 AM, Ilia Rostovtsev<EMAIL_ADDRESS>wrote:
That sounds very strange. Are you on iOS beta version?
—
Reply to this email directly or view it on GitHub.

I thought I posted this before. If you install XCode on your MacBook Pro, you can use the iOS Simulator to preview your work. Works great and lets you test on all iOS Devices. There's even a WatchOS simulator too. haha.
/Applications/Xcode.app/Contents/Developer/Applications/Simulator.app

Yes, I remember. I just haven't had chance to do it yet.

Same issue here. Lovely theme, just so frustrating that it's almost unusable on iPhone 6

I'll take a look. It's not closed. :)
I have a lot of other major improvements to do now. I will install XCode of my Mac sooner or later and try fixing it. (in case it's not going to be resolved by upcoming 18.00)

This issue should be solved in 18.00.
Report back please.

Sadly the issue persists on the home (System information) page.  As soon as I scroll down, it starts re-rendering the page.
On the plus side, the new version appears to have resolved this issue on other pages, e.g. Postfix configuration page, which was really annoying.

I honestly have no idea why in the World that would happen.
Glad to hear about other issues got resolved. I bet you can't reproduce it on iPhone using Chrome/Firefox, right?

That's what I thought, but I was able to reproduce it on both Chrome and Firefox for iOS

Really!?
Let me see...
Alright, have a look. This is Chrome on Android 6.0.1:
http://rostovtsev.ru/pub/src/authentic/18.01b/working_scroll_under_chrome.mp4
Tell me something, what if you click option Menu on top right and select Display Desktop version of the site, does it do anything?

Did you try Desktop mode? It should help.

Any news here? Switching to desktop helps, right?

It makes no difference. I'll try to create a short video to this

Ok, thanks!

https://vimeo.com/170363558
This is on my live server, so I set a password to protect my details. I'll send you the password via your website contact form now.

Ok.

This is bizarre! I have not even remote idea of why this is happening!
What about Chrome?

.. or that was Chrome?

I tried everything, Chrome and Firefox for iOS and switching to Desktop mode. No worries, I can live with this 😄 It used to happen on every page, which made the theme almost unusable. Now it only happens on the front page, so it's not a major issue

Hmm.. Really!? All other pages were fixed after 18.00?
..hmm...

Yeah other pages were fixed after 18.00 - I know because before it was really annoying to save any changes, e.g. to Postfix settings, because by the time I scrolled to the bottom to Save, the page would bounce back up. This is not happening anymore, which is great.

Wow! Cool!
.. I have set it all in my mind now. ..maybe the solution will come by itself, maybe not. .. I'm intended to fix it, whenever it is..
Thanks, pal.

This problem stil exists. It sounds related to a problem described here: https://github.com/kbwood/countdown/issues/50
Could you check if this is the same issue? Looks like iOS Safari doesn't like iframes.

What theme version do you have installed?

Interesting post in the link, thanks. Could you try the solution that is in this StackOverflow answer?

This is the solution, after adding the css style snippet in the StackOverflow answer to the theme extension styles.css the page no longer snaps back to the top on my iPhone. I am running version 18.03 af the theme.
Thank you!

Oh, that is nice. Finally. OK. Do you have any changes on Desktop version? Will it work if you remove height property?

Removing the height property has no influence. Removing the overflow however causes the jumping behaviour to return. I have not encountered any negative effects in desktop safari so far.

Thanks, pal. I might release a fixed version very soon.

YW, thank you for developing the theme!

Will be fixed in 18.04 within an hour.

18.04 is out, please upgrade! :wink:

This issue is back in 18.20 :(

It truly don't see how it's possible. I haven't done any changes.
However, I'll double check.

I can conform that it is back. When I reapply the custom CSS mentioned earlier the issue goes away again.

@casparz could you please post your custom CSS please?

@qooob
html, body {
overflow: auto;
-webkit-overflow-scrolling: touch;
}

Here is why I removed it, I even commented it. Try it only on body tag:
/* When using overflow: autoon <html> -window.scrollTo(0,document.body.scrollHeight) doesn't work*/

Ahh, well. It wouldn't work.

It's only happening in Safari browser?

Hi,
Here is the fix that will satisfy all. Please add it to your custom scripts.js extension and check it on Safari in iOS:
const __ua__ = window.navigator.userAgent,
    ___is_iOS = (!!__ua__.match(/iPad/i) || !!__ua__.match(/iPhone/i)),
    ___is_webkit = (!!__ua__.match(/WebKit/i)),
    ___is_iOSSafari = (___is_iOS && ___is_webkit && !__ua__.match(/CriOS/i) && !__ua__.match(/OPiOS/i));

// Mobile Safari (iOS) fix with pages not scroll to bottom issue #394
(___is_iOSSafari &&
    ($.injectCSS({
        "html": {
            overflow: "auto",
        }
    })));

Wait.. It will fail for an iframe. Try this:

// Mobile Safari (iOS) fix with pages not scroll to bottom issue #394
(___is_iOSSafari &&
    ($('html').css('overflow', 'auto'))
);

I can confirm it works!

Great. I will add it to 18.30. Now all will be happy.


[SPARK-40719][SQL] CTAS should respect TBLPROPERTIES during execution

What changes were proposed in this pull request?
This PR aims to propagate table properties during CTAS query executions.
Why are the changes needed?
Currently, CREATE TABLE ... USING ... TBLPROPERTIES (...) AS ignores table properties while CREATE TABLE ... STORED AS ... TBLPROPERTIES (...) AS respect them.
spark-sql> CREATE TABLE t1 STORED AS PARQUET TBLPROPERTIES (parquet.compression 'zstd') AS SELECT 1;
spark-sql> CREATE TABLE t2 USING PARQUET TBLPROPERTIES (parquet.compression 'zstd') AS SELECT 1;

$ ls spark-warehouse/t1
_SUCCESS
part-00000-c28a99f0-a88f-448d-a60d-e8204bf2f3a7-c000.zstd.parquet

$ ls spark-warehouse/t2
_SUCCESS
part-00000-3c5853d0-308d-4571-86c3-3e1a31eacfe6-c000.snappy.parquet

Does this PR introduce any user-facing change?
Yes,
How was this patch tested?
Pass the CI with the newly added test case.

Hi, @cloud-fan . I know that we have OPTIONS clause for storage options, but can we allow this too at CTAS?

Do you know why STORED AS works? AFAIK the storage options should be specified by storage properties, but not table properties.

@cloud-fan . Apache Spark CTAS with STORED BY ... TBLPROPERTIES table has been simply consistent with CREATE TABLE + INSERT INTO like the following.
spark-sql> CREATE TABLE t(a int) STORED AS PARQUET TBLPROPERTIES (parquet.compression 'zstd');
spark-sql> INSERT INTO t VALUES(1);

$ ls -al spark-warehouse/t
total 24
drwxr-xr-x  6 dongjoon  staff  192 Oct  9 21:13 .
drwxr-xr-x  3 dongjoon  staff   96 Oct  9 21:13 ..
-rw-r--r--  1 dongjoon  staff    8 Oct  9 21:13 ._SUCCESS.crc
-rw-r--r--  1 dongjoon  staff   12 Oct  9 21:13 .part-00000-0a4b4b66-8970-4223-8263-18d35c3eee43-c000.zstd.parquet.crc
-rw-r--r--  1 dongjoon  staff    0 Oct  9 21:13 _SUCCESS
-rw-r--r--  1 dongjoon  staff  450 Oct  9 21:13 part-00000-0a4b4b66-8970-4223-8263-18d35c3eee43-c000.zstd.parquet

What's the behavior of CREATE TABLE t(a int) USING PARQUET TBLPROPERTIES (parquet.compression 'zstd') + INSERT INTO t VALUES(1)?

Oh, got it. It doesn't work, either.
$ ls -al spark-warehouse/t
total 24
drwxr-xr-x  6 dongjoon  staff  192 Oct  9 21:25 .
drwxr-xr-x  3 dongjoon  staff   96 Oct  9 21:24 ..
-rw-r--r--  1 dongjoon  staff    8 Oct  9 21:25 ._SUCCESS.crc
-rw-r--r--  1 dongjoon  staff   12 Oct  9 21:25 .part-00000-b7924aff-f367-4043-b3af-0ef9fbadef54-c000.snappy.parquet.crc
-rw-r--r--  1 dongjoon  staff    0 Oct  9 21:25 _SUCCESS
-rw-r--r--  1 dongjoon  staff  443 Oct  9 21:25 part-00000-b7924aff-f367-4043-b3af-0ef9fbadef54-c000.snappy.parquet

Ah, sorry. After looking at the log, I realized that we did and documented this officially.
https://github.com/apache/spark/blob/cf053836e8f75645dab9551683a4e9e32e9625c8/docs/sql-migration-guide.md#L539

According to the migration guide, we fixed STORED AS ... TBLPROPERTIES at Apache Spark 2.4.

https://github.com/apache/spark/blame/master/docs/sql-migration-guide.md#L539

Since Spark 2.4, Spark respects Parquet/ORC specific table properties while converting Parquet/ORC Hive tables. As an example, `CREATE TABLE t(id int) STORED AS PARQUET TBLPROPERTIES (parquet.compression 'NONE')` would generate Snappy parquet files during insertion in Spark 2.3, and in Spark 2.4, the result would be uncompressed parquet files.

So the problem is different data sources may interpret table properties differently. Hive serde parquet table respects the parquet options in table properties, but native parquet table does not. If we want to support it, we should clearly define the relationship between table properties, storage properties, and options.

Ya, I agree. According to the current support rule,
https://github.com/apache/spark/blob/cf053836e8f75645dab9551683a4e9e32e9625c8/sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveMetastoreCatalog.scala#L134-L138
The following is our support rule.
  private def isOrcProperty(key: String) =
    key.startsWith("orc.") || key.contains(".orc.")

  private def isParquetProperty(key: String) =
    key.startsWith("parquet.") || key.contains(".parquet.")

I have two ideas in my mind.

We can allow the same pattern here for ORC and Parquet.
We can introduce a new configuration for a pattern to select table property in a more general way. For example, orc|parquet or '*'.

I'll convert this to the Draft and rethink about the issue. Thank you!

When we read/write Hive Parquet tables using native Parquet data source, we extract read/write options from table properties:
https://github.com/apache/spark/blob/master/sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveMetastoreCatalog.scala#L132-L138
I don't know the reason of this special case (the code seems to be there for a long time), but this seems like something we can always do: when read/write a data source table, combine table properties and storage properties as the read/write options.

Thank you, @cloud-fan .


[Bug]多卡启动一个进程会报0卡内存不足

Checklist

[ ] 1. I have searched related issues but cannot get the expected help.
[ ] 2. The bug has not been fixed in the latest version.

Describe the bug
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 172.00 MiB. GPU 0 has a total capacty of 15.57 GiB of which 127.38 MiB is free. Including non-PyTorch memory, this process has 15.45 GiB memory in use. Of the allocated memory 15.33 GiB is allocated by PyTorch, and 711.50 KiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
Reproduction
CUDA_VISIBLE_DEVICES='0,1,2' lmdeploy serve api_server ../Qwen1___5-7B-Chat --server-name <IP_ADDRESS> --server-port 8011  --tp 1
Environment
T4 8*16G，lmdeploy0.2.6(安装0.3.0版本运行报错：argparse.ArgumentError: argument command: conflicting subparser: chat，因此降了版本)

Error traceback
No response

@userandpass hi，7B models with fp16 needs at least 14G GPU mem to load and need extra mem for KV cache. You may need to use tp>1

@userandpass hi，7B models with fp16 needs at least 14G GPU mem to load and need extra mem for KV cache. You may need to use tp>1

CUDA_VISIBLE_DEVICES='0,1,3,4' lmdeploy serve api_server ../Qwen1___5-7B-Chat --server-name <IP_ADDRESS> --server-port 8011  --tp 4
Think you，I used the default qwen configuration of 'torch_dtype: bfloat16', it said that this type is not supported, only float32 will do, but it needs to use 4 cards to not report out of memory, I executed the command will prompt：
2024-04-17 13:50:46,043 - lmdeploy - ERROR - Init tp model failed with error: [RuntimeError('Trying to create tensor with negative dimension -28: [-28, 64, 8, 128]'), RuntimeError('Trying to create tensor with negative dimension -28: [-28, 64, 8, 128]'), RuntimeError('Trying to create tensor with negative dimension -28: [-28, 64, 8, 128]'), RuntimeError('Trying to create tensor with negative dimension -28: [-28, 64, 8, 128]')]
qwen config.json:
{   "architectures": [     "Qwen2ForCausalLM"   ],   "attention_dropout": 0.0,   "bos_token_id": 151643,   "eos_token_id": 151645,   "hidden_act": "silu",   "hidden_size": 4096,   "initializer_range": 0.02,   "intermediate_size": 11008,   "max_position_embeddings": 32768,   "max_window_layers": 28,   "model_type": "qwen2",   "num_attention_heads": 32,   "num_hidden_layers": 32,   "num_key_value_heads": 32,   "rms_norm_eps": 1e-06,   "rope_theta": 1000000.0,   "sliding_window": 32768,   "tie_word_embeddings": false,   "torch_dtype": "float32",   "transformers_version": "4.37.0",   "use_cache": true,   "use_sliding_window": false,   "vocab_size": 151936 }

hi,

T4 does not support bf16, you can change to fp16 in config.json torch_dtype: 'float16'
Can you install the latest from main branch or can you try with python<=3.10 on v0.3.0. Could reproduce your issue and it works well with tp=4 on 4 a100 with Qwen1.5-7B-Chat on my machine on main or v0.2.6

hi,

T4 does not support bf16, you can change to fp16 in config.json torch_dtype: 'float16'
Can you install the latest from main branch or can you try with python<=3.10 on v0.3.0. Could reproduce your issue and it works well with tp=4 on 4 a100 with Qwen1.5-7B-Chat on my machine on main or v0.2.6

I changed to fp16, it can run on 2 cards, thank you.


getMediaById.php

Can I take instagram user story by id?

i did it before but through facebook sdk


acceptance test cachefile use

Bitbucket: https://bitbucket.org/pypa/setuptools_scm/issue/5
Originally reported by: Ronny Pfannschmidt
Originally created at: 2010-05-26T02:25:09.438

acceptance test and fix version from cachefile, fixes #5
→ <<cset 66c37cb291cc>>

Original comment by: Ronny Pfannschmidt


Support conversion on properties with generation strategy

It would be nice if properties with conversions would allow a generation strategy.
For example:
protected override void OnModelCreating(ModelBuilder builder)
{
    builder.Entity<Game>()
      .Property<GameId>()
      .HasConversion(id => id.Value, id => new GameId(id))
      .UseNpgsqlSerialColumn();
}

I think by using the provider ClrType instead of the property ClrType this should work.

@KarelCoudijzer This looks interesting, but we'll need to reevaluate after dev is ported to preview7 (should be in the near future).

@ajcvickers any thoughts about this? It doesn't seem to be supported in SqlServer...

@roji Looks like this: https://github.com/aspnet/EntityFrameworkCore/issues/11597

@ajcvickers any chance you could give this a review and confirm the approach should work? I'm not sure I have all the implications in my head.
@KarelCoudijzer assuming @ajcvickers approves, can you please rebase this on top of the latest dev?

@roji The main considerations in https://github.com/aspnet/EntityFrameworkCore/issues/11597 are that converters can change both the type and/or the valid key space. So, for example, if you have a value converter from string to int, then should it use int key generation? What if you have GUID to string? Should it use GUID key generation? We haven't really come to any concrete conclusions as to how to resolve these things, which is why the issue is marked as needs-design.

@ajcvickers thanks, makes sense!
I think we should hold off on merging anything like this in EFCore.PG specifically, as the problem isn't PostgreSQL-specific and the questions @ajcvickers raised are quite important.

@roji I agree. So it's better to close this PR and try to support this feature in aspnet/EntityFrameworkCore by solving issue aspnet/EntityFrameworkCore#11597.

@KarelCoudijzer thanks for your understanding!


Result mismatch with headdim=256 bwd

Hello,
I'm trying to test head_dim=256 backward performance on H100, with below modifications, I manager to make it run. However, it reports test mismatch in result comparing.
Modifications:

add run_mha_bwd_hdim256 in hopper/flash_bwd_launch_template.h,
64,64 is refering to https://github.com/Dao-AILab/flash-attention/blob/main/csrc/flash_attn/src/flash_bwd_launch_template.h#L301:

void run_mha_bwd_hdim256(Flash_bwd_params &params, cudaStream_t stream) {
    constexpr static int Headdim = 256;
    BOOL_SWITCH(params.is_causal, Is_causal, [&] {
        BOOL_SWITCH(params.is_local, Is_local, [&] {
            BOOL_SWITCH(params.cu_seqlens_q != nullptr || params.cu_seqlens_k != nullptr, Varlen, [&] {
                BOOL_SWITCH(params.deterministic, Deterministic, [&] {
                    run_flash_bwd<Headdim, 64, 64, T, Is_causal, Is_local && !Is_causal, Varlen, Deterministic, false, false, 1, 2, 1>(params, stream);
                });
            });
        });
    });
}

change head_size limit from 128 to 256 in hopper/flash_api.cpp
uncomment "flash_bwd_hdim256_fp16_sm90.cu" in hopper/setup.py

When running 'hopper/benchmark_attn.py', with 'batch_size = 1, seqlen=8192, nheads = 36', I came across this error which indicates result mismatch:
### mode = 'bwd', batch_size = 1, headdim = 256, seqlen = 8192, causal = False ###
Traceback (most recent call last):
  File "/workspace/code/flash-attention/hopper/benchmark_attn.py", line 294, in <module>
    torch.testing.assert_close(ref_dv, dv, atol=0.05, rtol=0.05)
  File "/usr/local/lib/python3.10/dist-packages/torch/testing/_comparison.py", line 1530, in assert_close
    raise error_metas[0].to_error(msg)
AssertionError: Tensor-likes are not close!

PS: I noticed there is a TODO for headdim256 bwd in hopper/flash_api.cpp, could this lead to the mismatch, anything needed to tuning the number in it? Seems my modification above shouldn't introduce above error.
else if (head_size == 256) {
        // TODO for hdim 256
        if (num_n_blocks <= 40) {
            start_threshold = .24f;
        } else if (std::log2f(num_n_blocksf) <= 8) {
            start_threshold = .33f + std::max(0.f, (std::log2f(num_n_blocksf) - std::log2f(50)) * 0.02971f);
        } else {
            // Just split freely
            start_threshold = .8f;
        }

Oh seems like I didn't paste full error log, add it here:
### mode = 'bwd', batch_size = 1, headdim = 256, seqlen = 8192, causal = False ###
Traceback (most recent call last):
  File "/workspace/code/flash-attention/hopper/benchmark_attn.py", line 294, in <module>
    torch.testing.assert_close(ref_dv, dv, atol=0.05, rtol=0.05)
  File "/usr/local/lib/python3.10/dist-packages/torch/testing/_comparison.py", line 1530, in assert_close
    raise error_metas[0].to_error(msg)
AssertionError: Tensor-likes are not close!

Mismatched elements: 5463253 / 75497472 (7.2%)
Greatest absolute difference: 4.13671875 at index (0, 4096, 1, 136) (up to 0.05 allowed)
Greatest relative difference: inf at index (0, 1857, 28, 186) (up to 0.05 allowed)

Please try the tdd branch which supports bwd for hdim up to 256. We'll merge it soon.

Thanks! I will try

Please try the tdd branch which supports bwd for hdim up to 256. We'll merge it soon.

Thank you for the solution, now I can run hdim256 bwd with aligned output!
One more thing, it looks like hdim256 bwd 9.215 ms is >4x latency to fwd 1.926 ms, it there any room for further improvement?
### mode = 'fwd', batch_size = 1, headdim = 256, seqlen = 8192, causal = False ###
Fav2: 7.572ms, 326.7 TFLOPS
Fav3: 3.476ms, 711.7 TFLOPS
Fav3 varlen: 3.870ms, 639.3 TFLOPS

### mode = 'fwd', batch_size = 1, headdim = 256, seqlen = 8192, causal = True ###
Fav2: 4.137ms, 299.0 TFLOPS
Fav3: 1.926ms, 642.1 TFLOPS
Fav3 varlen: 2.014ms, 614.3 TFLOPS

### mode = 'bwd', batch_size = 1, headdim = 256, seqlen = 8192, causal = False ###
Fav2: 23.420ms, 264.1 TFLOPS
Fav3: 17.491ms, 353.6 TFLOPS
Fav3 varlen: 18.090ms, 341.9 TFLOPS

### mode = 'bwd', batch_size = 1, headdim = 256, seqlen = 8192, causal = True ###
Fav2: 11.967ms, 258.4 TFLOPS
Fav3: 9.215ms, 335.6 TFLOPS
Fav3 varlen: 9.771ms, 316.5 TFLOPS

You're welcome to work on it!
We've been best perf with CUDA 12.3.


Get My Location button update the map

This PR contains fixes for issue #76
Closes #76

I have tested the code, it's working fine


add jit.si as an authorized provider

per conversation with GSO, jit.si is going to become an authorized conference_provider

turns out we already had it, but were calling it Jitsi Meet -- updating to Jitsi


refactor: replace async pipes with signals

Less to add to the bundle size!

#468  👈 (View in Graphite)
main

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


Updating constraint branch with go dep

Is there a way to update the constraint branch using dep ?
we have something like this:
[[constraint]]
  branch = "master"
  name = "<internal package>"

we want it to load different branch based on our deployment.
e.g. when building for our staging server, we want it to look like this:
[[constraint]]
  branch = "staging"
  name = "<internal package>"

we tried to do dep ensure --update <internal package>@staging
but it is showing error
Invalid arguments passed to ensure -update:

  ✗ version constraint staging passed for <internal package>, but -update follows constraints declared in Gopkg.toml, not CLI arguments

update arguments validation failed

dep:
version     : v0.4.1
build date  : 2018-01-27
git hash    : 37d9ea0
go version  : go1.9.3
go compiler : gc
platform    : darwin/amd64

Can we have a dep command to update this constraint in the .toml file instead of manually performing the update?

Up this. Is there a reason this is not available?

After adding the contraint to Gopkg.toml, I had to run dep ensure --update  and that updated the vendor files to the branch I wanted.

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!


[🐞] HMR not working in starter template (issue with Vite 5.0)

Which component is affected?
Starters / CLI
Describe the bug
I created a new Qwik project with npm create qwik@latest.
The issue is that HMR doesn't work on every file. For example:

updating starter/hero/hero.tsx --> HMR works
updating starter/footer/footer.tsx --> HMR doesn't work

The issue seems to be linked to Vite version. Vite 5.0 default installed version seems to be causing the issue. Installing Vite 4 last version resolves the issue.
Reproduction
https://stackblitz.com/edit/github-y5nrmn?file=src%2Fcomponents%2Fstarter%2Fhero%2Fhero.tsx
Steps to reproduce
On your local machine, run npm create qwik@latest and follow the steps.
The issue:

updating starter/hero/hero.tsx --> HMR works
updating starter/footer/footer.tsx --> HMR doesn't work

Now revert back to Vite 4 and HMR works again :
npm uninstall vite
npm install -D vite@4

System Info
System:
    OS: macOS 14.2.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 115.95 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
  Browsers:
    Chrome: 120.0.6099.234
  npmPackages:
    @builder.io/qwik: ^1.4.1 => 1.4.1
    @builder.io/qwik-city: ^1.4.1 => 1.4.1
    undici: * => 6.4.0
    vite: ^5.0.12 => 5.0.12

Additional Information
No response

Hmm. There are also some weird errors with Vite 5 sometimes. I suppose we should downgrade Vite to 4 in the starters, there's no real downside to that.

@balaji-sivasakthi Github closes issues automatically when their PR gets merged :)


[Bug]: Table cuts off records from view on last page of multi-page query

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I try to view a table that has multiple pages, the final page will not display all the records if the remaining records is equal or near the pageSize value of the table.
Example:

A query has 63 records.
A table has a pageSize of 16, with Default height as the property.
There will be a total of 4 pages needed to view the records (63/16 = 3.9)
Pages 1 - 3 display records 1-14 completely, with record 15 slightly cropped and record 16 not visible. The table has the ability for the user to scroll on these pages to see records 15 and 16 fully.
The final page, 4 in this example, follows the same viewing pattern EXCEPT the scrolling functionality is no longer available which leaves record 15 slightly cropped and the final record (16) entirely inaccessible.

I marked this as 'Medium' but not displaying all records - when each are critically important to our operations - could be considered 'High' at least it is in our workflow.
Ticket
Steps To Reproduce
Using public sample below:

Preview pages 1-3 and observe all 16 records using the scrolling functionality.
Preview page 4 and notice only 14 records fully visible, 15 slightly cropped, and 16 inaccessible due to the scrolling functionality disabled.

Public Sample App
https://actve.network/app/testing-table/page1-66a4049073fe0449d79b534e?environment=production
Environment
Production
Severity
Medium (Frustrating UX)
Issue video log
No response
Version
Self Hosted - v1.26

@leestreetnet can you set the query to read the limit as the {{Table1.pageSize}} so that there is no scroll on the first page. This way your records become predictable and you can adjust the table height to perfectly fit the last record of the page

@Nikhil-Nandagopal it is already currently set to {{Table1.pageSize}}. This is the query:
SELECT id, name FROM public."users"  LIMIT {{Table1.pageSize}} OFFSET {{Table1.pageOffset}};
I updated the Sample App to show the differences between a table with the same properties, one with data and one without. The Default row height is set to 'Default' for both tables, yet you can see the difference in row height between the table with data and the data without.

@leestreetnet I understand there is a difference in the heights of the table and that does look like a bug but I'm still unable to understand the situation where you are unable to see the last row of the 4th page. The app only has 2 pages of data and I can see both

@Nikhil-Nandagopal I was using the Appsmith 'users' table for sample data and that likely is reset now that I think about it. So at the time I had added records so the total count was 64, but I see it is now back down to 23 records.
I changed the datasource to my own hosted database that has 64 records, I see now the final page does have the scrolling functionality now - was anything changed on your end?
I also updated the sample app to show the difference in table row heights when 'Server Pagination' is turned ON vs OFF. The data is the same for each, but the height changes based on that setting.

No nothing was changed on our end, the issue was likely the database getting reset. I understand the issue with the height changing. Can you open a new issue related to that?


bst checkout fails due to artifact cache error when remote execution is enabled

See original issue on GitLab
In GitLab by [Gitlab user @jmacarthur] on Sep 14, 2018, 11:13
Summary
Steps to reproduce
Run bst checkout hello.bst with remote execution set up. hello.bst is from the autotools example, in doc/examples/autotools/elements.
What is the current bug behavior?
bst checkout hello.bst test/
[--:--:--][][] START   Loading elements
[00:00:00][][] SUCCESS Loading elements
[--:--:--][][] START   Resolving elements
[00:00:00][][] SUCCESS Resolving elements
[--:--:--][][] START   Resolving cached state
[00:00:00][][] SUCCESS Resolving cached state

Error while staging dependencies into a sandbox: 'Artifact hello.bst is configured to use remote execution but has no push remotes. The remote artifact server(s) may not be correctly configured or contactable.'

What is the expected correct behavior?
bst checkout works as per the documentation regardless of whether remote execution is enabled or not.
Possible fixes
From the logs above (supplied by [Gitlab user @finnball]) it looks as though remote caches aren't set up for a checkout command, which would have made sense before remote execution was present. Since remote execution runs integration commands as well as builds, it's necessary to run a checkout too. The SandboxRemote class should initialize remote caches independently if they haven't already been set up, but it's possible the configuration necessary for those caches hasn't been done in this case.
Other relevant information

In GitLab by [Gitlab user @jmacarthur] on Sep 14, 2018, 17:33
mentioned in merge request !800

In GitLab by [Gitlab user @jmacarthur] on Sep 14, 2018, 17:36
It's nothing to do with integration commands. The problem occurs simply because we're using SandboxRemote to hold the artifact temporarily whether or not any commands need to be run. !800 allows checkout to work again but still uses SandboxRemote - it'd be better if we could avoid using SandboxRemote for checkout jobs.

In GitLab by [Gitlab user @juergbi] on Sep 25, 2018, 07:16
[Gitlab user @jmac] Do you still see a remaining issue or can we close this now that !800 has been merged? Some platforms may not even have a local sandbox, as mentioned in !800.

In GitLab by [Gitlab user @jmac] on Sep 25, 2018, 09:16
Wrong jmac! :smile:

In GitLab by [Gitlab user @jmacarthur] on Sep 25, 2018, 10:07
I'm closing this issue. Running without a local sandbox is an improvement we can make in the future.

In GitLab by [Gitlab user @jmacarthur] on Sep 25, 2018, 10:07
closed


Cannot read Parquet files that do not specify Map keys as required

Describe the bug
The Parquet Format specifies that:

The key field encodes the map's key type. This field must have repetition required and must always be present.

I.e.
<map-repetition> group <name> (MAP) {
  repeated group key_value {
    required <key-type> key;
    <value-repetition> <value-type> value;
  }
}

However, most implementations of the format do not appear to enforce this in the Thrift schema, and producers such as Hive/Spark/Presto/Trino/AWS Athena do not produce Parquet files like this. A huge number of such files are widely found on data lakes everywhere, and rewriting such files in order to comply with this does not seem feasable.
To Reproduce
        let url_str = "https://overturemaps-us-west-2.s3.us-west-2.amazonaws.com/release/2023-07-26-alpha.0/theme%3Dtransportation/type%3Dconnector/20230726_134827_00007_dg6b6_01b086fc-f35b-487c-8d4e-5cdbbdc1785d";
        let url = Url::parse(url_str).unwrap();
        let storage_container = Arc::new(HttpBuilder::new().with_url(url).build().unwrap());
        let location = Path::from("");
        let meta = storage_container.head(&location).await.unwrap();
        let mut reader = ParquetObjectReader::new(storage_container, meta);

        // Parquet schema can be printed
        let mut p_metadata = reader.get_metadata().await.unwrap();
        print_schema(&mut std::io::stdout(), p_metadata.file_metadata().schema());

        // Metadata cannot be loaded
        let metadata = ArrowReaderMetadata::load_async(&mut reader, Default::default())
            .await
            .unwrap();

Results in:
thread 'main' panicked at src/main.rs:79:10:
called `Result::unwrap()` on an `Err` value: ArrowError("Map keys must be required")

Expected behavior
Map keys are assumed to be required, regardless of explicit specification in the Thrift schema, and data is read accordingly.
Additional context
This has come up in a PyArrow issue: https://github.com/apache/arrow/issues/37389
Enforced here: https://github.com/apache/arrow-rs/blob/9fda7eab0c9fb55c90194865ca921c094b78dae9/parquet/src/arrow/schema/complex.rs#L289-L291

The conclusion of https://github.com/apache/arrow/issues/37389 appears to be that we are correct to refuse to read such malformed files, am I missing something here?

It was discussed, but I don't think that was the conclusion. The creator's issue was resolved by rewriting a file.
In order to operate with precious Parquet files from huge data lakes (e.g. DataFusion probably would want to support files produced by other systems), I'm of the opinion that it should tolerate this like most of the other implementations do (e.g. DuckDB, parquet-tools, and probably many more).
I'm all for correctness, but in this particular case you need to consider the intention and purpose.
There is no way that an optional key can be intentional. Being compatible with a vast amount of data is the purpose of Parquet integration.

We could probably just ignore the malformed map logical type and decode such columns as a regular list of structs. This would allow the data to be read, without needing to implement custom dremel shredding logic to handle the case of malformed MapArray, and allowing users to determine how they wish to handle this situation.
Tagging @mapleFU who may have further thoughts on this

It works when removing/reducing the check with all files I tested. I have not been able to produce any files that have invalid data to match such a schema, but I'd assume it would error as it would for any invalid data.


Mac: git's bash integration scripts report modifications when there are none

Open Terminal
Clone\mount a VFS4G repo
Run the following commands:

source /Applications/Xcode.app/Contents/Developer/usr/share/git-core/git-completion.bash
source /Applications/Xcode.app/Contents/Developer/usr/share/git-core/git-prompt.sh
export GIT_PS1_SHOWDIRTYSTATE=true
export PS1='\n[\h:\w$(__git_ps1)]\n \u\$ '

Navigate to freshly cloned repo

Observe:  Bash prompt displays a * in the prompt:
[GVFSs-MBP:~/GVFSTest/src (master *)]
Indicating that it thinks there are modifications.
Other thoughts
The scripts that ship with git appear to be using git diff --no-ext-diff --quiet  and it is returning a non-zero exit code.
On my machine git diff shows no differences but git diff --raw shows differences in .gitattributes (it could be related to timestamps?)

The issue is that git diff –no-ext-diff --quiet is returning 1.
git diff -no-ext-diff has no output, git diff --raw does.
@jobriggs, @wilbaker and I think this can go to pri2, please let us know if you disagree.


Feature-Request: Custom Key Labels

I would like to be able to :

Display only Key name without Octave (e.g. , "C", "D",... instead of "C4", "D4"
OR
Display "Do", "Re", "Mi",...

I suggest:
pianoView.setKeyLabels(labels: [Int:String])

Where labels is a dictionary of [MidiNote : Label]
Alternatively, labels could be a simple array of a fixed size of 128, to set ALL labels.

You seem to have many specific requirement, might I suggest you maintain your own fork instead?

Addressed in 1.0.18


Provider ai21 model does not support chat.

Is there support for the AI21 Labs models using ChatBedrock ? I am getting the error NotImplementedError: Provider ai21 model does not support chat.

ai21.jamba-instruct-v1:0
ai21.j2-mid-v1
ai21.j2-ultra-v1

+1 I'm also interested in having native chat support for AI21 models in ChatBedrock.


ROX-10894: Remove extra namespace selection in Network Graph integration test

Description
Problem
Network Graph Search should filter to show only the stackrox namespace and deployments connected to stackrox namespace
AssertionError: expected 0 to equal 1

https://app.circleci.com/pipelines/github/stackrox/stackrox/11382/workflows/bc2e5f1b-1e5f-41c0-b3de-018cd5cc2ad5/jobs/526549
https://app.circleci.com/pipelines/github/stackrox/stackrox/11481/workflows/cbdb83cc-1336-4a1e-b259-a83ea793712e/jobs/532109
https://app.circleci.com/pipelines/github/stackrox/stackrox/11571/workflows/e2719a4b-2bae-4b7c-89d5-1995f5f3f725/jobs/536637

Analysis
Each namespace selection causes a pair of networkgraph and networkpolicies requests:

Visit helper function waits only for one pair of requests.
Select helper function might click to select additional namespaces so quickly that multiple pairs of requests become scrambled.

From failed integration test, see networkpolicies request after wait for requests and even after wait for 100ms:

From local deployment, see multiple pairs of requests:

Solution

Because stackrox is the only non-orchestrator namespace that is available for tests in both CI and local deployment, select only one namespace in tests.
Move intercept and wait into select helper functions, in case future tests select multiple namespaces. Additional calls in a test can select additional namespaces.
Delete arbitrary cy.wait(100) from getCytoscape command.
For now, delete assertion for number of namespaces to let the assertion pass even if array is empty.

Residue

Replace cy.visit with helper functions in other general tests for page titles.
The interaction to select namespaces is inconsistent:

On toolbar, click Namespaces to open drop-down menu, and then click to select or clear check boxes.
In empty graph area, click Namespace(s) to open drop-down menu, and then as soon as you click a check box, the graph replaces the menu.
If you intended to click another namespace, now you must select on the toolbar.
Therefore, it seems more consistent, and possibly less frustrating, for people to select from toolbar only. Render a message in the empty area.

Do graph connections for Active depend on networkpolicies in addition to networkgraph response? Or is networkgraph response enough information?
Move network.test.js file into networkGraph folder. Maybe separate it into general and specific test files.

Checklist

[x] Investigated and inspected CI test results
[x] Edited integration tests

Testing Performed
Ran test in local deployment

For Residue:

This is something I noticed as well an it is a little awkward. It might be worth bringing up quickly with the UX team and see if they have any suggestions. e.g. Removing it entirely, making it a "single select" to kick off rendering and not present the user with multiple choices they can't select anyway.
For this, I'm not sure that the Active state depends on the networkpolicy response, but it is mixed with the networkgraph response based on this snippet that is called when both requests return:

        let newState = {};
        newState = setEdgeMapState(flowGraph, newState, 'active');
        newState = setEdgeMapState(policyGraph, newState, 'allowed');
        return newState;


Speed up multi grid ndt build

Use multithread to build NDT when there are changes in the map segments
Tested on shiojiri dataset

The results of regression_test also confirm the speedup.

https://github.com/tier4/ndt_omp/actions/runs/8246065407/artifacts/1317846806
Great job!

This PR a a bit too big. I need to separate it to smaller PRs so I temporarily close this PR.


Fixer mixer

Description
This pull request addresses various typo corrections across multiple files in the repository. The changes ensure consistent spelling and improve documentation and workflow clarity.
Details

Corrected typos in workflow files (.github/workflows/nightly.yml) to ensure accurate terminology, such as "permissionless" instead of "permisionless."
Fixed minor spelling issues in documentation files (docs/migrate/upgrade.md and docs/use-native-token/use-native-token.md) for better readability. Examples include "Unified bridge exchanges" and "let's transfer."
Updated template fields in .github/ISSUE_TEMPLATE/feature_request.yml to maintain uniform labeling ("behavior" instead of "behaviour").

References (if applicable)
N/A

Commit Summary

typo feature_request.yml: Fixed label spelling in feature request template.
typos nightly.yml: Resolved spelling inconsistencies in workflow files.
typo: Corrected documentation typos in migration and usage guides.
various typos: General cleanup of remaining typos in workflow and documentation.

Testing
These changes have been reviewed for accuracy and clarity. No functional code modifications were made, ensuring no unintended impacts on existing functionality.

Checklist

[x] Documentation updated with corrected typos.
[x] Workflow files reviewed for syntax and consistency.
[x] Changes verified for no impact on functional workflows.

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


Fixed counters bugs

Could not increment by 2
Could not pass variables to increment counters

Apart from the minor nit about indentation, we should add an integration test for it, but otherwise it looks good to me.

Ticket: CSHARP-281

fixed identation

Created another branch with the fix (provided by @trurl123) and with integration tests.
https://github.com/datastax/csharp-driver/pull/239

Merged #239 that includes an integration test.
Thanks @trurl123!


⚠ Bofrost.lu has degraded performance

In 22da9fc, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1906 ms

Resolved: Bofrost.lu performance has improved in 428ac79.


containers: use ssl and align with kubernetes entities in openshift

This patch switches to use https for the kubernetes connection. All the provides already defined in the database will stop working as they'll probably need to update the port (from 8080 to 6443). Since we're still in a development phase this shouldn't be a problem (not worth a migration script) provided that all the developers are aware of it.

/cc @abonas @oschreib @dkorn @zeari

@miq-bot add_label providers/containers

:-1: this is not ready yet. I require some other changes.

Please also do the rubocop changes as listed above.

:+1: now it should be ok, I tested it with refresh and events.

Do you have a place to default the port?  The caller/user shouldn't have to know the value.  I know for OpenStack it's defaulted in the UI here (ick, but it is what it is).
One approach might be to set default_value_for :port in the model.

Do you have a place to default the port? The caller/user shouldn't have to know the value. I know for OpenStack it's defaulted in the UI here (ick, but it is what it is).
One approach might be to set default_value_for :port in the model.

we can definitely add it in several places - provider backend, kubeclient gem, etc.
doesn't have to be part of this particular patch imo, unless @simon3z prefers it here.

@abonas @Fryguy I'll get both suggestions path/port. I'll respin later.

@abonas @Fryguy I'll get both suggestions path/port. I'll respin later.

ok, keep me posted. I actually removed path as part of my openshift provider work (since kubeclient supports it now anyway), but it will take a while till it's ready, and I can rebase on this one of course.

@abonas @Fryguy ok this is good to go :+1:
I verified that the refreshes are ok, relationships are ok, events watches are ok, adding a new provider is ok (default port 6443), ssl was enabled on all the checks.

@Fryguy I modified the endpoint.targetRef part as you suggested.

:+1: Looks good to me.


Implement SSfoo functions from R

Running example(selfStart) in R ultimately lists 10 transformation functions
List of 10
 $ SSasymp    :function (input, Asym, R0, lrc)
 $ SSasympOff :function (input, Asym, lrc, c0)
 $ SSasympOrig:function (input, Asym, lrc)
 $ SSbiexp    :function (input, A1, lrc1, A2, lrc2)
 $ SSfol      :function (Dose, input, lKe, lKa, lCl)
 $ SSfpl      :function (input, A, B, xmid, scal)
 $ SSgompertz :function (x, Asym, b2, b3)
 $ SSlogis    :function (input, Asym, xmid, scal)
 $ SSmicmen   :function (input, Vm, K)
 $ SSweibull  :function (x, Asym, Drop, lrc, pwr)

that are often used in PK / PD models, which we will need if we want to write a stan_nlmer function that is similar to lme4::nlmer. These are relatively easy to implement because these R functions also calculate the gradient with respect to all arguments except the first and return it as an attribute of the output. Just execute body(SSfoo) to see the R implementation.

Where do these go?  Are they going to be functions exposed in the Stan language?
We should define the math first and then implement them from scratch to avoid any IP issues with GPL-ed code.

Rayleigh is working on this. Yes, they should be defined first in Stan
Math, then exposed in the Stan language, doc'd etc. The FSF doesn't think
of translating a simple mathematical function from one language to another
as a derived work.
On Tue, Sep 15, 2015 at 12:32 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

Where do these go? Are they going to be functions exposed in the Stan
language?
We should define the math first and then implement them from scratch to
avoid any IP issues with GPL-ed code.
—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/math/issues/144#issuecomment-140452918.

Moving the conversation over from email where we've been talking about organization and what is needed.
Do we need a version for these functions with a scalar input? If they're all link functions for non-linear regressions, such as SSasymp, the results don't seem meaningful if called with one value.
Also, I've been assuming the other parameters, such as Asym, R0, lrc, are scalar, because that's how it's implemented in R. Is this a safe assumption?

I think the vast majority of the time people would call these functions
with a vector as the first argument and scalars for the remaining
arguments, but we do need versions for any combination of scalars and
vectors, inclusive of all scalars and all vectors. This really doesn't add
that much to the coding burden because every other function should just be
calling the all scalar function at every iteration of its loop over the
vectors.
On Fri, Oct 2, 2015 at 4:02 PM, rayleigh<EMAIL_ADDRESS>wrote:

Moving the conversation over from email where we've been talking about
organization and what is needed.
Do we need a version for these functions with a scalar input? If they're
all link functions for non-linear regressions, such as SSasymp, the results
don't seem meaningful if called with one value.
Also, I've been assuming the other parameters, such as Asym, R0, lrc, are
scalar, because that's how it's implemented in R. Is this a safe assumption?
—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/math/issues/144#issuecomment-145141355.

It actually adds a lot to the coding burden because
of the combinatorics of testing.
Do you really need every argument to possibly be a vector?
If so, what's the return type?  How is the function defined
for vectors other than in the vectorized position in the R code?

Bob

On Oct 2, 2015, at 4:50 PM, bgoodri<EMAIL_ADDRESS>wrote:
I think the vast majority of the time people would call these functions
with a vector as the first argument and scalars for the remaining
arguments, but we do need versions for any combination of scalars and
vectors, inclusive of all scalars and all vectors. This really doesn't add
that much to the coding burden because every other function should just be
calling the all scalar function at every iteration of its loop over the
vectors.
On Fri, Oct 2, 2015 at 4:02 PM, rayleigh<EMAIL_ADDRESS>wrote:

Moving the conversation over from email where we've been talking about
organization and what is needed.
Do we need a version for these functions with a scalar input? If they're
all link functions for non-linear regressions, such as SSasymp, the results
don't seem meaningful if called with one value.
Also, I've been assuming the other parameters, such as Asym, R0, lrc, are
scalar, because that's how it's implemented in R. Is this a safe assumption?
—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/math/issues/144#issuecomment-145141355.

—
Reply to this email directly or view it on GitHub.

It wouldn't make sense for the first argument to be a scalar and any of the
subsequent arguments to be a vector. It would make sense for the first
argument to be vector-like and any of the subsequent arguments to be a
scalar or vector-like with the same length as the first argument like we do
for sampling statements (except a vector-like thing would be returned). We
could probably write a test-generating function like we do with the
densities. But it is fine to start with the case where the non-first
arguments are scalars and get that one working.
On Fri, Oct 2, 2015 at 5:58 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

It actually adds a lot to the coding burden because
of the combinatorics of testing.
Do you really need every argument to possibly be a vector?
If so, what's the return type? How is the function defined
for vectors other than in the vectorized position in the R code?

Bob

On Oct 2, 2015, at 4:50 PM, bgoodri<EMAIL_ADDRESS>wrote:
I think the vast majority of the time people would call these functions
with a vector as the first argument and scalars for the remaining
arguments, but we do need versions for any combination of scalars and
vectors, inclusive of all scalars and all vectors. This really doesn't
add
that much to the coding burden because every other function should just
be
calling the all scalar function at every iteration of its loop over the
vectors.
On Fri, Oct 2, 2015 at 4:02 PM, rayleigh<EMAIL_ADDRESS>wrote:

Moving the conversation over from email where we've been talking about
organization and what is needed.
Do we need a version for these functions with a scalar input? If
they're
all link functions for non-linear regressions, such as SSasymp, the
results
don't seem meaningful if called with one value.
Also, I've been assuming the other parameters, such as Asym, R0, lrc,
are
scalar, because that's how it's implemented in R. Is this a safe
assumption?
—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/math/issues/144#issuecomment-145141355.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/math/issues/144#issuecomment-145166283.

They're rather different implementation paths, I think,
between writing a simple function and a vectorized density
The former is simple and the latter really needs to use all
the traits and expression template stuff we have in place.
Is the one that takes multiple vector arguments just
returning a single value?  Is the one taking vector
arguments in the first position returning a single value?
I'm not entirely clear what signatures are under discussion here.
If they don't combine into a single value, then the implementation
is going to be different again, because we don't return a single
constructed autodiff var, but many.  So it's fewer of the moving
pieces.  For efficiency, I doubt they'll just loop over the
scalar functions, but we could do that to start.
I've been thinking about general patterns for vectorization, but
it'd require writing the unary version as a functor and then
passing that functor's type to helper functions.  I have it worked
out, but it'd need to be implemented.  But for 10 functions with
lots of arguments that are just distributed, it might be worth it.
And it'd let us easily vectorize what's left of the functions
in Stan, too.
Rayleigh also said that one of the functions is a density
(Gompertz, I believe).  So that should be implemented like our
other ones.  And should ideally include CDFs and RNGs, but it's
not a hard requirement.
Is there a priority order for these or is it all or nothing?

Bob

On Oct 2, 2015, at 6:04 PM, bgoodri<EMAIL_ADDRESS>wrote:
It wouldn't make sense for the first argument to be a scalar and any of the
subsequent arguments to be a vector. It would make sense for the first
argument to be vector-like and any of the subsequent arguments to be a
scalar or vector-like with the same length as the first argument like we do
for sampling statements (except a vector-like thing would be returned). We
could probably write a test-generating function like we do with the
densities. But it is fine to start with the case where the non-first
arguments are scalars and get that one working.
On Fri, Oct 2, 2015 at 5:58 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

It actually adds a lot to the coding burden because
of the combinatorics of testing.
Do you really need every argument to possibly be a vector?
If so, what's the return type? How is the function defined
for vectors other than in the vectorized position in the R code?

Bob

On Oct 2, 2015, at 4:50 PM, bgoodri<EMAIL_ADDRESS>wrote:
I think the vast majority of the time people would call these functions
with a vector as the first argument and scalars for the remaining
arguments, but we do need versions for any combination of scalars and
vectors, inclusive of all scalars and all vectors. This really doesn't
add
that much to the coding burden because every other function should just
be
calling the all scalar function at every iteration of its loop over the
vectors.
On Fri, Oct 2, 2015 at 4:02 PM, rayleigh<EMAIL_ADDRESS>wrote:

Moving the conversation over from email where we've been talking about
organization and what is needed.
Do we need a version for these functions with a scalar input? If
they're
all link functions for non-linear regressions, such as SSasymp, the
results
don't seem meaningful if called with one value.
Also, I've been assuming the other parameters, such as Asym, R0, lrc,
are
scalar, because that's how it's implemented in R. Is this a safe
assumption?
—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/math/issues/144#issuecomment-145141355.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/math/issues/144#issuecomment-145166283.

—
Reply to this email directly or view it on GitHub.

The number one priority signature is to input a var vector and a few var scalars and output a vector. But if we implemented it with VectorViews, then some mix of vectors and scalars wouldn't require extra implementations.
The Gomperz density is different from the Gompertz transformation function
https://en.wikipedia.org/wiki/Gompertz_distribution#Probability_density_function
https://en.wikipedia.org/wiki/Gompertz_function#Formula

On Oct 3, 2015, at 7:24 PM, bgoodri<EMAIL_ADDRESS>wrote:
The number one priority signature is to input a var vector and a few var scalars and output a vector. But if we implemented it with VectorViews, then some mix of vectors and scalars wouldn't require extra implementations.

If we need all those variants then this is the only
way to go.  If there aren't custom derivatives, it's
not much harder.  If there are, then it has to all
be done like the densities.
Do all the functions just distribute through the
different positions?  So that there's an underlying
scalar function like f(a,b) and the vectorized form
f(av, bv) is just (f(av[1],bv[1]), ..., f(av[N], bv[N]))
And if av or bv is a scalar, it's just broadcast for
reuse in every position.
That's what I think is worth somehow metaprogramming.
I don't think it'll be too hard without custom derivatives.
As soon as there are custom derivatives, then you need to
think about which intermediate things to cache.

The Gomperz density is different from the Gompertz transformation function
https://en.wikipedia.org/wiki/Gompertz_distribution#Probability_density_function
https://en.wikipedia.org/wiki/Gompertz_function#Formula

And this is just the transform?

Bob

For the first current version of SSfoo, can I just implement the following:
SSfoo(std::vector& input, T2 param1, T3 param2, etc.)
which returns a std::vector of the boosted type that is the same length as input?
Also, are there certain functions that you want out of the 10 functions?
Finally, how are you planning on use these functions? I understand that it's used as a link function for a nlmer call in R so is it something that'll be used by Rstan arm code primarily? If so, how will it be used there?

I think the main issue here is whether we can write these things with specialized signautres that have double values rather than having everyting flexible enough to enter into Stan's language?  If it has to go into the language, we'll have to make everything polymorphic.

We want to be able to do models like these
http://lme4.r-forge.r-project.org/slides/2010-05-26-Muncie/slidesD.pdf
It would suffice to start by implementing all the SSfoo() functions in Stan
assuming var for everything except the output and the first input is a var
vector. But ultimately I think they are going to have to get implemented
like the densities, except returning a var vector rather than a var scalar.

OK --- that's a lot of work in testing for a four-element
function if we're going to be rigorous like we're doing now.
It either means generalizing or building a paralell testing
framework to the densities due to return value.
I've been tinkering with some template-based list approaches
to dealing with this that I think are promising.
The question is whether we need them exposed in the language, or
whether it'd be enough to have them in the math libs.
The second question is breadth vs. depth.  Is it better to get
limited versions (in terms of efficiency and generality of
arguments as var and vector) of them all, or do one all the way
through to start?

Bob

On Oct 16, 2015, at 2:22 AM, bgoodri<EMAIL_ADDRESS>wrote:
We want to be able to do models like these
http://lme4.r-forge.r-project.org/slides/2010-05-26-Muncie/slidesD.pdf
It would suffice to start by implementing all the SSfoo() functions in Stan
assuming var for everything except the output and the first input is a var
vector. But ultimately I think they are going to have to get implemented
like the densities, except returning a var vector rather than a var scalar.
—
Reply to this email directly or view it on GitHub.

I think they would need to be exposed in the Stan language, even if they
are initially unlikely to be used outside of a .stan file in a future
rstanarm. Thusfar, we haven't added any hacks to rstanarm that would enable
it to do things that a motivated user couldn't do ordinarily with the Stan
language, and I would rather keep it that way.
So, it would be fine to start with something like
vector SSfoo(vector, real, real, real) {
// implementation
}
so that in a few months we could write a stan_nlmer() function that would
enable us to do what lme4 can do now:
nm1 <- nlmer(circumference ~ SSlogis(age, Asym, xmid, scal) ~ Asym|Tree,
data = Orange, start = startvec)
But it may be more total work to do a limited implementation of the SSfoo
functions now and do a complete reimplementation later.

I think this is a long way off, so closing.

Closing again.


Refactor some bits of the triggers API.

Some bits of the triggers API did include duplicated code.  Didn't get around to post comments to the specific PRs so here are my proposed fixes.
@mdeuser would you have a look please?

@markusthoemmes PG?

@csantanapr PG4 1344 🔵


Delete 3vHSsV6mgvpa1JVuuDZVB72vYbeUNzW4mBxiBftwzHEA

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

NEED THIS FILE DELETED ASAP!!! We needed a folder not a file. This is preventing our logo from populating on the explorer. Please help us as we're in our token generation event and cannot even see our logo on the explorer.


CI: update test execution on nightly pipelines

We don't support regression-bigiso and koji tests in nightly pipelines
so don't run them.
This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

Just a nightly testing changes, we don't need to wait for the full CI here.


Error : 'FAIL : Load model from xxx failed:/onnxruntime_src/onnxruntime/core/graph/model_load_utils.h:47 void onnxruntime::model_load_utils::ValidateOpsetForDomain(const std::unordered_map<std::basic_string, int>&, const onnxruntime::logging::Logger&, bool, const string&, int)

Do the ONNX model quantization, after running the command python -m onnxruntime.quantization.preprocess --input xxx.onnx --output xxx-infer.onnx to preprocess my onnx model, the generated model xxx_infer.onnx cannot be loaded for the following quantization, it returns the error:
FAIL : Load model from onnx_path failed:/onnxruntime_src/onnxruntime/core/graph/model_load_utils.h:47 void onnxruntime::model_load_utils::ValidateOpsetForDomain(const std::unordered_map<std::basic_string, int>&, const onnxruntime::logging::Logger&, bool, const string&, int) ONNX Runtime only guarantees support for models stamped with official released onnx opset versions. Opset 3 is under development and support for this is limited. The operator schemas and or other functionality may change before next ONNX release and in this case ONNX Runtime will not guarantee backward compatibility. Current official support for domain ai.onnx.ml is till opset 2
Any help will be appreciated.

did you resoled it? i have the same issue..


Sanity Check TPL dependencies at the axom config level

The current logic in the generated CMake Axom config allows for a host application to use different TPLs than the ones used by Axom. For example, a host application may be using one version of Conduit and bring in Axom that was built with a different version fo Conduit.
https://github.com/LLNL/axom/blob/3128c6cbd68cb184202488dd85feafc467faa6cf/src/cmake/axom-config.cmake.in#L63-L70
The host-application and Axom, are typically pointing to the same TPLs, e.g., Conduit, HDF5, RAJA, Umpire, etc.
There could be some serious complications that could arise otherwise.
In our generated CMake Axom config, we have the opportunity to catch that at the build system level, instead of allowing things to build and potentially lead to bugs that will be hard to detect and resolve downstream.
I cannot think of a real use-case where we'd want to allow for this.
If throwing an error seems too restrictive, we should at minimum issue a warning message (and hope it is not ignored).

will reopen if needed.


UITableView Error

Could you post some relevant code from your cellForRowAtIndexPath method?

Closing this as cannot reproduce.


Implement paratest for local testing

It will be nice to have "paratest" as dev dependency by default for local testing, even if it's not used with github workflows #1265.

I would say we want to avoid adding dependencies that Lunar isn't using. If it's something you use yourself and want to use it across projects, maybe look at installing it globally.


[Release] Verify 2.0.0-rc2

@github-actions crossbow submit -p release=2.0.0 -p rc=2 -g verify-rc

Closing since the vote has passed.


Align icons with text in navigation link

This allows the icon to be vertically aligned with a text inside a navigation link.

LGTM, but will defer to @sgomes for a second review and merge.

LGTM, thanks @tleunen!


[Wave 6: Tags] CRITICAL: Backend updates to enable creating a money request with a tag and billable value

Update the following to accept tag and billable parameters:

CreateIOUTransaction Auth command
RequestMoney API command
CreateDistanceRequest Auth command
CreateDistanceRequest API command

Implementation tracking
tag param:

[x] https://github.com/Expensify/Auth/pull/8714
[x] https://github.com/Expensify/Web-Expensify/pull/38894
[x] https://github.com/Expensify/App/pull/27674

billable param:

[x] https://github.com/Expensify/Auth/pull/8748
[x] https://github.com/Expensify/Web-Expensify/pull/38929
[x] https://github.com/Expensify/App/pull/27910

billable PRs are up

We're all deployed here, closing!