[Guide] Local harvesting through a remote account

I don't think I was aware of this option, but it should be explained somewhere.
https://nem2.slack.com/archives/C9YKR0EUX/p1608225259204300?thread_ts=1608214610.203500&cid=C9YKR0EUX
https://nemgroup-workspace.slack.com/archives/C015AEQ9ZL2/p1608230255400000?thread_ts=1608219011.393000&cid=C015AEQ9ZL2

now im a bit confused
the solution to my request point to the question?
or does that mean there is no guide available yet and this issue point to that fact and i need to wait?

Currently there are only guides for local and delegated harvesting.
This ticket is a reminder for me to investigate a possible third option and write a new guide if necessary.

i dont understand
each node operator will use delegated harvesting
no node operator would use local accounts with addresses that have their private key written in cleartext in local files
so a guide for local harvesting make absolute no sense
but maybe u mean that with local harvesting
but then ur guide need to start at a differnt point
u need to explain how u handle a XYM address in a wallet
how u create a delegated address how u give that delegated address the right to stake ur coins (or whatever its called in symbol)
how u edit the symbol node conf files with the required changes so ur node stake with ur delegated coins
how u edit the conf that ur delegated coins correct make ur node a supernode
how u edit conf that ur node can act as a finallity signer

Thanks to your comments and some internal discussion I have an idea on how to proceed now.
Given than harvesting through a remote account (to avoid exposing your main account in the node's config, which is stored as plain text) is very similar to delegated harvesting I would merge the two guides.
I'll update the delegated harvesting guide (#531) to include remote harvesting. The only difference is Step 4, where you need to edit the config file instead of sending a persistent delegate request.
Node security will be handled in #549.
Supernodes will be handled in #550.


Unknown types for "VKxxx" structures and constants while building

Describe the Issue
While building Vulkan-ExtensionLayer-sdk version <IP_ADDRESS>, I come up with a set of errors regarding unknown types mostly on VK*** structures and constants.
Environment:

OS: GNU/Linux Slackware
GPU:  [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X]
SDK or header version if building from repo: <IP_ADDRESS>
Options enabled (synchronization, best practices, etc.):

Additional context
Below the command-line I user to compiler the package:
$ cmake                                                       \
  -DCMAKE_INSTALL_PREFIX=/usr            \
  -DCMAKE_INSTALL_SYSCONFDIR=/etc  \
  -DCMAKE_INSTALL_DATADIR=/share      \
  -DCMAKE_SKIP_RPATH=True                  \
  -DBUILD_TESTS=Off                                 \
  -DBUILD_WSI_XLIB_SUPPORT=On         \
  -DBUILD_WSI_XCB_SUPPORT=On          \
  -DBUILD_WSI_WAYLAND_SUPPORT=On \
  -DCMAKE_BUILD_TYPE=Release              \
  -DBUILD_LAYER_SUPPORT_FILES=On    \
  ..

The errors I got look like the following:
[  9%] Building CXX object utils/CMakeFiles/VkExtLayer_utils.dir/generated/vk_safe_struct.cpp.o
In file included from /tmp/Vulkan-ExtensionLayer-sdk-<IP_ADDRESS>/utils/generated/vk_safe_struct.cpp:33:
/tmp/Vulkan-ExtensionLayer-sdk-<IP_ADDRESS>/utils/generated/vk_safe_struct.h:3503:5: error: ‘VkVideoCapabilityFlagsKHR’ does not name a type; did you mean ‘VkVideoCapabilitiesFlagsKHR’?
 3503 |     VkVideoCapabilityFlagsKHR capabilityFlags;
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~
      |     VkVideoCapabilitiesFlagsKHR
In file included from /tmp/Vulkan-ExtensionLayer-sdk-<IP_ADDRESS>/utils/generated/vk_safe_struct.cpp:33:
/tmp/Vulkan-ExtensionLayer-sdk-<IP_ADDRESS>/utils/generated/vk_safe_struct.h:3503:5: error: ‘VkVideoCapabilityFlagsKHR’ does not name a type; did you mean ‘VkVideoCapabilitiesFlagsKHR’?
 3503 |     VkVideoCapabilityFlagsKHR capabilityFlags;
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~
      |     VkVideoCapabilitiesFlagsKHR
/tmp/Vulkan-ExtensionLayer-sdk-<IP_ADDRESS>/utils/generated/vk_safe_struct.h:4612:55: error: ‘VkPhysicalDevicePresentWaitFeaturesKHR’ does not name a type; did you mean ‘safe_VkPhysicalDevicePresentWaitFeaturesKHR’?
 4612 |     safe_VkPhysicalDevicePresentWaitFeaturesKHR(const VkPhysicalDevicePresentWaitFeaturesKHR* in_struct);
      |                                                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                                                       safe_VkPhysicalDevicePresentWaitFeaturesKHR
/tmp/Vulkan-ExtensionLayer-sdk-<IP_ADDRESS>/utils/generated/vk_safe_struct.h:4612:55: error: ‘VkPhysicalDevicePresentWaitFeaturesKHR’ does not name a type; did you mean ‘safe_VkPhysicalDevicePresentWaitFeaturesKHR’?
 4612 |     safe_VkPhysicalDevicePresentWaitFeaturesKHR(const VkPhysicalDevicePresentWaitFeaturesKHR* in_struct);
      |                                                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                                                       safe_VkPhysicalDevicePresentWaitFeaturesKHR
/tmp/Vulkan-ExtensionLayer-sdk-<IP_ADDRESS>/utils/generated/vk_safe_struct.h:4617:27: error: ‘VkPhysicalDevicePresentWaitFeaturesKHR’ does not name a type; did you mean ‘safe_VkPhysicalDevicePresentWaitFeaturesKHR’?
 4617 |     void initialize(const VkPhysicalDevicePresentWaitFeaturesKHR* in_struct);
      |                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                           safe_VkPhysicalDevicePresentWaitFeaturesKHR
/tmp/Vulkan-ExtensionLayer-sdk-<IP_ADDRESS>/utils/generated/vk_safe_struct.h:4617:27: error: ‘VkPhysicalDevicePresentWaitFeaturesKHR’ does not name a type; did you mean ‘safe_VkPhysicalDevicePresentWaitFeaturesKHR’?
 4617 |     void initialize(const VkPhysicalDevicePresentWaitFeaturesKHR* in_struct);
      |                           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                           safe_VkPhysicalDevicePresentWaitFeaturesKHR

A full output can be found in the following attached file:
vulkan.log

It looks like you may be getting stale vulkan headers somehow. For example VkPhysicalDevicePresentWaitFeaturesKHR was added in Vulkan 1.2.185.
Are you using update_deps.py and cmake -C helper.cmake?  If not you may need to set VULKAN_HEADERS_INSTALL_DIR to point to the correct location for the new headers.

I got the same issue using update_deps.py and cmake -C helper.cmake.

I logged the entire output in a file because the whole thing is too big for a copy/paste.
vulkan.log

Using helper.cmake AND setting VULKAN_HEADERS_INSTALL_DIR  will conflict with each other
From your log, it looks like  -DVULKAN_HEADERS_INSTALL_DIR=$PKG/usr wins, and whatever is there is not correct.
********************************************************************************
-- Found VulkanHeaders: /tmp/package-vulkan-sdk/usr/include
-- Found VulkanRegistry: /tmp/package-vulkan-sdk/usr/share/vulkan/registry
-- Configuring done
-- Generating done

Using only helper.cmake should have set VULKAN_HEADERS_INSTALL_DIR to:
 /tmp/Vulkan-ExtensionLayer-sdk-<IP_ADDRESS>/build/Vulkan-Headers/build/install/

Thank you for your help.
I remove the cmake switch and it works.


I have a little bit of an issue with additional URL parameter from my server

Hi, it's not an issue with your panorama per se but you might be able to help

I'm using the standalone version of your viewer
My free web hosting is always adding additional parameter at the end of every URL /?i=1 and this causes the pannelum viewer to display the following error An invalid configuration parameter was specified: i
So instead of server.com I always get server.com/?i=1
I've found sort of a workaround with .httaccess rewrite to remove it but it not always works for unknown reason and additionally when I remove this parameter from every URL, my image gallery doesn't want to load images.
Is there a way to make pannelum standalone to ignore this parameter?

Thanks

How are you specifying the URL parameters? The preferred method is to use # instead of ?, since this avoids sending the parameters to the server. When # is used, the standalone viewer should ignore any parameters specified with ?. The following two examples work fine for me:
https://cdn.pannellum.org/2.5/pannellum.htm?i=1#panorama=https://pannellum.org/images/alma.jpg
https://cdn.pannellum.org/2.5/pannellum.htm#panorama=https://pannellum.org/images/alma.jpg?i=1

This is how my panorama is specified
http://www.xxxx.com/pannellum.htm#panorama=http://www.xxxx.com/panorama.jpg&autoLoad=true&autoRotate=2
I use fancybox gallery and the whole one item looks like this

I have no control over this /?i=1 it gets added by the webhost automatically so I really don't even know in which part of the URL it gets added

Without looking at the actual network traffic, I'm not sure I can really debug this more. Pannellum should ignore the ?=1 if # is used, so I can't think of an obvious reason why it isn't working in your case.


custom job should push built images to additional registries

Commit a143ea095b657ff858303aba9c37f074ee5df2e1 deleted images:push call from custom job.
We found we still need to push to additional registries (reg-aws) because QE is using it.

/lgtm


[Get started] fix pin name for arduino

All Arduino has TX and RX pins this is more accurate.

This has been solved somewhere else.


Unable to add new value to ParameterRecSeries

Checked for duplicates
Yes - I've already checked
Is this a regression?
Yes - This worked in a previous version
Version
1.6
Describe the bug
Cannot add a new value to a ParamRecSeries, see error below

Reproduction

Add ParameterTest activity to a plan using Bananation
Select the activity and try to add a value to something like doubleArray and observe the dev console
Re-select the activity (click off and click back on or refresh the page and re-select) and no parameters will load for the activity

Logs
No response
System Info
Mac Chrome

Severity
Annoyance

Potentially this is a duplicate of
https://github.com/NASA-AMMOS/aerie-ui/issues/662

Verified this is separate and not a duplicate of https://github.com/NASA-AMMOS/aerie-ui/issues/662


Content: Update "Retro Funding + Rounds" contents based on legal requirement

Legal has advised that we should not combine the terms "Retro Funding" with "Round". So, we need to update the following:
Application title
Old: "Apply for Retro Funding Round 5: OP Stack"
New: "Apply for Retro Funding 5: OP Stack" (remove the word Round)

Callouts
Old: "Now taking applications for Retro Funding Round 5: OP Stack"
New: "Now taking applications for Retro Funding 5: OP Stack" (remove the word Round)

Old: "You applied to Retro Funding Round 5: OP Stack"
New: "You applied to Retro Funding 5: OP Stack"

@shaunop
Ready to review


fix: fix bash command formatting

This fixes markdown formatting of bash commands: some of them didn't even render properly before

Thanks for the contribution!

Thanks for the contribution!


Recognize numeric data types

I tried running a query like this:
select date_trunc('day', created_at), count(*) as num_issues from hive.v2.issues group by 1 order by 1

and got:
Data is missing a number field

after checking the query inspector, it turned out that the count is recognized as a string, not an integer.

String is default type when it is not able to find respective converter based on InputTypeName and ScanType is not provided.
What is column database type ?
we can just add converter based on that type and it should work

Done in 18fb8d9199b6b2dcb62f2d060ef505d494074945


Update requirements.txt

This open-cv module makes it easier to use import cv2 inside docker.

Hi @davidgodinez, thank you for this submission of the updated requirements.  Unfortunately, this pull request also includes several other changes that are not yet ready for merging into the datajoint repository.  Please close this pull request and open a new one with only the updated requirements.  Thank you.


Apply the trained KAN model to new data

Hello
I have a kan model trained (Regression), but i can't find any documentation on how to apply the trained model to new data.
Can someone help, with an example?

I've had this issue as well. I recommend that you use symbolic regression to predict new data via formulas.

what's the difference between new data and old data?

what's the difference between new data and old data?

I think he asks for how to predict OOT data without using symbolic formula cuz I have been looking for the same.
I want model.predict() or sth like that in order to score OOT data


Docs migration from rebolt to bs-react-native

There was an extensive work done on rebolt project for documenting lots of react-native components and APIs.  It will be great to migrate those to bs-react-native by using odoc auto generation with macros
Check the following example how docs should look like:
Activity Indicator
And this was the corresponding PR by @grabbou
Currently most of the docs are not migrated and formatted.
I will start opening PRs on docs migration and comment on this issue with PR links.
If you have additional suggestions how to improve docs beyond simple migration from Rebolt, please comment here too.

I'm going to move Button

@vnovick has everything being migrated? Can this issue be closed?

Looks like #294 closed this


Phaser.Physics.Arcade.Body alignIn() and alignTo()

Having those two methods for the Body will be useful. For example, I currently have a 125x125 Sprite that must collide with only its center 20x20 pixels. What I'm currently doing is this:
sprite.body.width = 20;
sprite.body.height = 20;
sprite.body.offset.x = (sprite.width - sprite.body.width)/2;
sprite.body.offset.y = (sprite.height - sprite.body.height)/2;

Having the alignIn() and alignTo() not only in the Sprite, but in the Body itself will allow me to do that:
sprite.body.width = 20;
sprite.body.height = 20;
sprite.body.alignIn(Phaser.CENTER);

It's not that big of a deal, I know. Those things can easily be calculated. Having the methods will make things easier, though.

I did this a few times too and eventually wrote:
Phaser.Physics.Arcade.Body.prototype.resize = function(width, height) {
  var offsetX, offsetY;
  if (height == null) {
    height = width;
  }
  offsetX = 0.5 * (this.sprite.width  - width)  / this._sx;
  offsetY = 0.5 * (this.sprite.height - height) / this._sy;
  width  /= this._sx;
  height /= this._sy;
  return this.setSize(width, height, offsetX, offsetY);
};

Thank you for taking the time to open this issue. However, official support for Phaser 2 has now ended as we focus on preparing Phaser 3 for beta release. In a bid to keep the project tidy, and avoid confusion, we are closing all v2 related issues.
This does not mean your issue won't be looked-at. In November 2016 the Phaser CE (Community Edition) project began. The aim of Phaser CE was to allow the community to continue v2 development. Since then it has gained significant traction, with many updates and releases.
If you are still interested in having your issue investigated we strongly recommend testing the latest Phaser CE release. And only if the problem persists, opening an issue on the Phaser CE repo.


Exercise 8 broken

$ expressworks verify 8-jsonme.js
Verifying "JSON ME"...

ACTUAL:   "[{\"title\":\"Express.js Guide\",\"tags\":[\"node.js\",\"express.js\"],\"url\":\"http://expressjsguide.com\"},{\"title\":\"Rapid Prototyping with JS\",\"tags\":[\"backbone.js\",\"node.js\",\"mongodb\"],\"url\":\"http://rpjs.co\"},{\"title\":\"JavaScript: The Good Parts\",\"tags\":[\"javascript\"]}]"
EXPECTED: "Cannot GET /books"

# FAIL

Your solution to JSON ME didn't match the expected output.
Try again!

#58


chore: add plural form of words and add nuance

The distractor answers should be plural like the real answer. This
commit also adds some context for some confusion around this acronym.
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

I will go ahead and merge this even though the lint check has failed. But I just opened up another issue #77 that might help with this in the future.


Configure Submitter disabling

Follow-up to #386
While Turbo's support for disabling a Form Submissions <input type="submit"> or <button> element is rooted in Rails UJS, it degrades (and has always degraded) the accessibility of those experiences.
To learn more about the risks involved, read the [Don’t Disable Submits][] section of Adrian Roselli's Don't Disable Form Controls along with the additional resources mentioned therein.
The risk of degrading accessibility is especially true for Morph-enabled Form Submissions. If a form submission will trigger a morphing Page Refresh with the submitter focused, it's likely that the focus is intended to remain on the submitter.
With the current [disabled] behavior, that is not possible without a bespoke event handler like:
addEventListener("submit", ({ target, submitter }) => {
  if (submitter) {
    target.addEventListener("turbo:submit-start", () => {
      submitter.disabled = false
      submitter.focus()
    }, { once: true })
  }
})

This commit introduces a Turbo.config.submitter object with two pre-defined keys: "disabled" (the default until we can deprecate it), and "aria-disabled".
When applications specify either Turbo.config.submitter = "disabled" or Turbo.config.submitter = "aria-disabled", they will be able to leverage those pre-packed hooks. Otherwise, they can provide their own object with beforeSubmit(submitter) and afterSubmit(submitter) functions.

@afcapel @jorgemanrubia this is inspired by https://github.com/hotwired/turbo/issues/774, although it not mentioned directly.

@jorgemanrubia @brunoprietog are either of you able to review this proposal (as a follow-up to https://github.com/hotwired/turbo/pull/1217)?


Built in support for srcset?

I notice that srcset doesn't seem to be supported.. if I add a srcset attribute the file will just not load.
Here it looks like this needs to be configured manually: https://github.com/vuejs-templates/webpack/issues/396
Would it make sense to have it supported out of the box since it's a standard?

Hi,
You can easily add loaders to the config by using build.loaders in your nuxt.config.js file to use html-loader or vue-html-loader and set the query parameter.
https://nuxtjs.org/api/configuration-build#loaders

Thanks for the pointer! Though my concern was primarily that shouldn't it
be supported without having to customize config because it is part of HTML?
On Sat, Apr 8, 2017 at 04:56 Alexandre Chopin<EMAIL_ADDRESS>wrote:

Closed #524 https://github.com/nuxt/nuxt.js/issues/524.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nuxt/nuxt.js/issues/524#event-1035093977, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABT8Iz6lnLdQc2pN11SV51XCXbIXTk3yks5rt0vBgaJpZM4M2Od4
.

I was also disappointed not to have this out of the box as responsive images are pretty important.  I don't see the documentation for loaders.  Is that gone now?  If so, can someone point me to the right place?


Direct support for 'expires_at' key when constructing AccessToken

Currently the AccessToken.new/1 method does not use the expires_at param if it is present in the given map, and only uses expires_in or expires. It is common to store access tokens in the DB, so when fetching them back and re-constructing the AccessToken struct it should Just Work™.
This PR changes that to use expires_at when it is already present.

@scrogson There seems to be a problem with the Travis builds. Can you manually restart the failing jobs or update the travis build matrix to install the correct versions?

@sheharyarn long time ... my apologies, trying to help.
Where does expires_at come from?
I searched for it on https://datatracker.ietf.org/doc/html/rfc6749#section-4.1.4 but I couldn't find it.

any updates?


Change FTS sytnax to use the ?= operator

Before this commit, FTS was expressed by using standalone strings in
filter expressions:
read elastic "keyword"

This commit changes the syntax to use a new ?= operator:
read elastic ?= "keyword"

The change includes updating tests and documentation. See the commit message for more details.
Resolves #56.

@demmer
I ended up actually not liking the change much, e.g. the examples in the docs now don’t feel very natural.
I also realized the ?= operator we agreed upon is actually inconsistent with the matching operator (=~) in the position of the = sign. But =? looks even more odd.

Scrapped per https://github.com/juttle/juttle/issues/56#issuecomment-177901363.


[#noissue] fix test

Codecov Report

Merging #6782 into master will increase coverage by 0.00%.
The diff coverage is 96.55%.

@@           Coverage Diff           @@
##           master    #6782   +/-   ##
=======================================
  Coverage   39.14%   39.15%
=======================================
  Files        3136     3136
  Lines       93895    93895
  Branches    11788    11788
=======================================
+ Hits        36755    36761    +6
+ Misses      54180    54174    -6
  Partials     2960     2960

Impacted Files
Coverage Δ

...rcorp/pinpoint/web/servlet/RewriteForV2Filter.java
60.71% <ø> (+3.57%)
:arrow_up:

...filer/instrument/transformer/DebugTransformer.java
15.78% <66.66%> (ø)

...avercorp/pinpoint/bootstrap/ContainerResolver.java
89.47% <100.00%> (ø)

...context/provider/ClassFileTransformerProvider.java
77.27% <100.00%> (ø)

...strument/transformer/DebugTransformerRegistry.java
63.63% <100.00%> (ø)

...pc/server/LoggingServerMessageListenerFactory.java
90.00% <0.00%> (-10.00%)
:arrow_down:

...navercorp/pinpoint/rpc/common/SocketStateCode.java
82.92% <0.00%> (-2.44%)
:arrow_down:

... and 10 more

Continue to review full report at Codecov.

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


opentelemetry collector documentation on monitoring jobs

Purpose of this pull request
This pull request adds documentation introducing monitoring jobs, a new feature in the sumo opentelemetry collector.

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions and updating sections
[X] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

@c-kruse, I noticed this pull request is in draft. When you are ready for us to review it, click the "Ready for review" button.


Update the README file

[x] A more detailed explanation of the course
[ ] Add the course content here step by step
[ ] #5

Creating a proper README for the project...

[ ] A more detailed explanation of the course
[ ] Add the course content here step by step
[ ] Convert one of these check boxed texts to an issue

Slash comments
console.log('hi')

Shipping...  🚢

❤


Notebook menu leaks

https://github.com/microsoft/vscode/blob/a198d712f111ddf8379419b5036a89d378071cb3/src/vs/workbench/contrib/notebook/browser/view/renderers/cellRenderer.ts#L845
The Menu instance that's created from getCellExecuteMenu is never disposed. Leaking menus is really bad because all menus listen to context key changes and those fire a lot, meaning each leaked menu makes that firing slower and slower...
Also, the symbol naming in src/vs/workbench/contrib/notebook/browser/view/renderers/cellMenus.ts is dubious because it "renames" create menu into get menu making it appear as something cheap

closing as dupe of https://github.com/microsoft/vscode/issues/126365


feat: Branch option in all calls to server

Codecov Report
Base: 79.62% // Head: 80.00% // Increases project coverage by +0.38% :tada:

Coverage data is based on head (d923ca9) compared to base (4e0f423).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #209      +/-   ##
==========================================
+ Coverage   79.62%   80.00%   +0.38%
==========================================
  Files          29       29
  Lines        2675     2716      +41
==========================================
+ Hits         2130     2173      +43
+ Misses        432      430       -2
  Partials      113      113

Impacted Files
Coverage Δ

driver/driver.go
82.81% <ø> (ø)

driver/types.go
0.00% <ø> (ø)

driver/grpc.go
81.86% <100.00%> (+0.62%)
:arrow_up:

driver/http.go
71.44% <100.00%> (+0.80%)
:arrow_up:

tigris/client.go
88.88% <100.00%> (+5.16%)
:arrow_up:

tigris/database.go
55.88% <100.00%> (+4.26%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Broken link to 'What is CSE Software Testing"

Under Find Resources->Better Reliability -> See Resources: Testing, one of the topics is "What is CSE Software Testing?".
Clicking on the link displays a 'not found' page (link address is https://bssw.io/what_is/what-is-cse-software-testing )
The article appears to be available in the repository under CuratedContents/WhatIsCseSwTesting.md

Thanks Mark.  I see the same problem.  Nothing jumps out at me in the md source.
@clararaubertas, do you see anything in the logs?

Seems to be working now!
https://bssw.io/what_is/what-is-cse-software-testing

Closing since the link seems to work.


Updated ockam_core::Result alias to allow generic error type

Proposed Changes

Fixes #1925
Enable generic error kind after importing ockam_core::Result

Thank you for sending the PR ❤
Before we can merge, could you accept our CLA
Read the CLA at
https://www.ockam.io/learn/how-to-guides/contributing/cla/
To accept the CLA please send a different PR to our contributors repo indicating that you accept the CLA by adding your Git/Github details in a row at the end of the CONTRIBUTORS.csv file:
https://github.com/ockam-network/contributors/blob/master/CONTRIBUTORS.csv
Looking forward to merging your first contribution!!

@plaxi0s another quick thing we require signed commits.
Could you please sign this commit and the one you send for the CLA
Here's a guide from github on signing commits that maybe helpful.
https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification
https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

Signed the commit.


App crash on iOS on wallet initialization page from fresh install w/ build 188

Steps to Reproduce:
Starting the wallet from a fresh install on iOS, when the wallet attempts to initialize after creating a pin, the initialization screen displays for a while and then the app crashes.
Upon reopening the app and entering your pin, the wallet initialization screen stays on screen indefinitely.
Environment:
Reproduced in Sauce Labs on iOS  along with my own local iPhone 6s.
Build 188
Video and a device log in Sauce Labs if it helps.  (need login) https://app.saucelabs.com/tests/7c2749b4b12f484b88ffacc23eb0192e#102
Workaround:
None, I have had to rollback to build 186, where this wasn't an issue.
Severity:
High
Priority:
High

Fixed in Build 190.


provide support for marker-file

https://github.com/mapbox/carto/blob/master/docs/latest.md#marker-file-uri
there is code for that but we probably broke it: https://github.com/CartoDB/torque/blob/heat/lib/torque/renderer/cartocss_render.js#L72
Make sure this is compatible with node rendering

Fixed as of #80


Report Creator

Special shout-out to @simonsonjack for helping me out with the report creator. Thank you so much Jack, this wouldn't have been possible without you 😄
Description

Implements the LEAN report creator, a new version separating view concerns from calculations/data management and new styling.
Note: I've left my commits un-squashed to provide commit history just in case we may need to revert (doubtful)
Related Issue

N/A
Motivation and Context

Implements calculations on LEAN side for general use, improves report
Requires Documentation Change

Yes.
How Has This Been Tested?

Some unit tests on some mission critical calculations (percent change, cumulative sum)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

There seems to be some effort duplication.
Wondering what the performance of the report creator is for different strategies, say 1, 5, 10 years length, with a daily trade maybe?


VSCode: failed to parse macro invocation following update to latest version of rust analyzer

I closed my VSCode project because the rust analyzer was crashing every few minutes. When I opened my project again, I was told to install the latest version of the analyzer, which I did. The next thing I know, I've got a gazillion "failed to parse macro invocation" error messages in my Problems pane. They aren't real errors, because my project compiles and runs just fine.  Many of them point to a line using the json! macro.  Others point to the first line, first character of a file.  One of them is could not resolve macro `crate::format_args.  These errors are only reported on 3 files of the many that use the json! macro.

I encountered this too, on 0.2.408. Rolled back to 0.2.400, which doesn't have the issue.
(If anyone else needs to, you can do this via Extensions icon -> choose rust-analyzer -> Manage (gear icon) -> Install Another Version)

Duplicate of https://github.com/rust-analyzer/rust-analyzer/issues/6740.
You can find there instructions to disable the warning, and it's likely fixed in the latest nightly build.


Copied from https://github.com/gitblit/gitblit/pull/950

https://github.com/saper/gitblit/blob/c4e5664d9b7bf19dd0f9dee79c8cb0d45f56bb54/src/main/java/com/gitblit/servlet/RawServlet.java
This was originally from https://github.com/gitblit/gitblit/pull/950 but seems to have been reverted when develop branch was merged with master.

Please merge this into master branch once done and re release 1.7.1 or release 1.7.2 since release notes reference Fix nested repository detection in raw servlet


*: Fetch labels at the first encounter with a process

Why?
To fetch the correct metadata information, it's better to fetch the data when we first encounter the process rather than waiting until building the profile before sending it.
Also, it changes some method signatures to improve consistency and avoid unnecessary work.
What?

🤖 Generated by Copilot at d86e6d4
This pull request refactors and simplifies the code related to profilers, labels, and process information in the parca-agent. It uses constants, label sets, and appropriate caching policies to improve the code quality, readability, and performance. It also adds the profiler name as a label to the profiles for the UI. It deletes unused files and adds comments to explain some types.
How?

🤖 Generated by Copilot at d86e6d4

Add constants for profiler status and normalization attempts label values (link, link, link, link, link)
Simplify pid and profiler name handling in label manager and its callers (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)
Remove labels manager from CPU profiler and use process info manager instead (link, link, link, link, link, link)
Rename and modify process info manager methods to avoid confusion with normalizer methods (link, link, link, link, link, link, link)
Add label set field and remove name field from process info type (link, link, link, link, link)
Change label cache expiration policy and add notice about process info manager cache (link)
Add comments to compiler and system providers about their own caches (link, link)
Delete unused process package and its test (link, link)

Test Plan

Test with scripts/local-run.sh
Test with make dev/up

🤖 Generated by Copilot at d86e6d4

parca-agent cleans
profiler and label code
autumn leaves cache

nit: any reason why we don't use profiler and label instead of prflr and lbl ?

It's just a preference, in sync with Go conventions. If the scope of the variable is narrow enough, I tend to use shorter names.
https://research.swtch.com/names

nit: any reason why we don't use profiler and label instead of prflr and lbl ?

It's just a preference, in sync with Go conventions. If the scope of the variable is narrow enough, I tend to use shorter names. research.swtch.com/names

There is actually a technical reason for prflr, it avoids shadowing the import which already uses the name: "github.com/parca-dev/parca-agent/pkg/profiler"


Conan V2

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (48913b1) 75.42% compared to head (2a0c77a) 75.30%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #70      +/-   ##
==========================================
- Coverage   75.42%   75.30%   -0.13%
==========================================
  Files          20       20
  Lines         822      822
  Branches       96       96
==========================================
- Hits          620      619       -1
  Misses        137      137
- Partials       65       66       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Upgrade to psr/log > version 3

🎉 Feature Request
Please upgrade psr/log to version 3.x
Summary
Hello,
I depend on the current version of psr/log. This project still uses the outdated version 1.x.
Thanks

I second that! I just wanted to install it into a Symfony application, but that does not seem to be compatible to each other.

@pud-micha @nopenopenope
Thanks for the poke, this will be part of the next release 👍


Feature request: End early when input received

I use tte for my terminal welcome.
Can add a flag that tte can exit itself when received anything i typing on terminal(and not affect the input content)

TTE handles keyboard interrupts (ctrl-c) to cleanly exit an effect early. I don't know of any way to both detect/capture input within a script and pass that back to the prompt as though it were in the keyboard buffer. Maybe with some pyautogui shenanigans to call the keyboard input api. That's a bit overboard, though. If interrupting via ctrl-c doesn't cover your use case, can you provide more detail? Thanks.

When you type during an effect, the terminal is displaying your input after flushing the buffer containing an effect frame. You are seeing the last character because the frame rate is faster than you can type two characters and between the characters (on each frame) the cursor is re-position such that your keystroke is overwriting the previous character at the end of the canvas. You can see this more clearly by setting the --frame-rate flag to 1 and typing during an effect.
Once the effect is over, your typed text is being buffered by the terminal and will be available at the prompt. It isn't being sent to TTE because the terminal is waiting for TTE to return. CTRL-C works because the terminal detects the special sequence and performs the interrupt. TTE cannot receive your keyboard inputs before that. Using something like the curses library would enable the process to listen for inputs, however, TTE does not use curses.
I'm going to close this issue, feel free to comment further. Thanks for checking out TTE.


Option ValidationOptions(allow_reaction_smiles_only=False) has no effect in validate_message or validate_datasets

Hi all
First: thanks for all your efforts on the ord-schema, it's well developed and very powerful! 💪🏼 🙌🏼
However, I recently ran into an issue when dealing with catalyst SMILES, that cannot be converted into valid molecules using the RDKit. I see that there is the option to disable valid reaction SMILES checks during the validation using ValidationOptions(allow_reaction_smiles_only=False) and passing it to validate_message or validate_datasets. However, this has no effect on any of my tested reactions or datasets.
To reproduce, here's a simple example for a dataset with one reaction:
reaction = message_helpers.load_message(filename, dataset_pb2.Dataset)
options = validations.ValidationOptions(validate_ids=False, require_provenance=False, allow_reaction_smiles_only=False)
validations.validate_message(reaction, options=options)

ValidationError: Dataset.reactions[0].inputs["12148-71-9"].components[0].identifiers[0]: RDKit 2023.03.2 could not validate SMILES identifier [O-]1(C)[Ir+]234([O-](C)[Ir+]1567[CH]=8CC[CH]7=[CH]6CC[CH]85)[CH]=9CC[CH]4=[CH]3CC[CH]92

It also does not work for validate_dataset:
validations.validate_datasets({"_TEST": reaction}, options=options)

_TEST: Reaction.inputs["12148-71-9"].components[0].identifiers[0]: RDKit 2023.03.2 could not validate SMILES identifier [O-]1(C)[Ir+]234([O-](C)[Ir+]1567[CH]=8CC[CH]7=[CH]6CC[CH]85)[CH]=9CC[CH]4=[CH]3CC[CH]92

I would expect that checking SMILES strings using RDKit is disabled when passing the option allow_reaction_smiles_only=False. I know that in this case I could actually get a valid SMILES for the Iridium catalyst, but its mainly for illustration purposes. As a workaround, I can just omit the SMILES for the catalysts, but I'd like to have them there if possible. Or would this become an issue to ultimately load them into the ORD?
Thanks in advance for the support
Versions
ord-schema         0.3.37
protobuf           3.19.6
rdkit              2023.3.2

Thanks, Alex. This is indeed a default part of validate_compound_identifier and we issue a ValidationError for a SMILES, InChI, or MolBlock that RDKit cannot load "properly".
This does seem like it is potentially too strict given that other programs may have more permissive valence rules, particularly for these kinds of complexes where SMILES is a somewhat awkward choice of representation (but a common one).
I would propose to @skearnes that we consider the following:

If MolFromSmiles cannot parse with default params, check if it can parse with sanitize=False. If yes, issue a ValidationWarning. Otherwise, stick to current behavior and issue a ValidationError
Likewise for MolFromInchi
Likewise for MolFromMolBlock but also with strictParsing=False

WDYT?

Thanks Connor, sounds like a good compromise 👍🏼

This should be all set now!

Sweet, thanks a lot!


SAP Cloud Platform Trial, ABAP Trial Create Instance error

Hi,
I have been trying to create instance for ABAP Trial in SAP Cloud Platform under Region: US East (VA) - AWS.
It gives attached error when trying to create instance. Could anyone please help on this

Could it be that you already have an instance created?  Can you click on Service Instances in this screen (just below Service Marketplace) and see if you have any instances created.  In the SCP Trial you only get enough quota for a single instance.  Also have you perhaps created another subaccount or space in this same trial account? You are allowed to have multiple subaccounts but you only get one quota for ABAP. If you've already used that in another subaccount within your trial account you can't get another.


Create some peakers

How to create some color peakers? If I create some instance they crash page or stay on left top corner. Only first peaker work good.
Pickr-version: 0.2.0
Browser-version:  Chrome 68.0.3440.106
Operating-system:  ubuntu

Did you mean multiple instances?

Yes

Okay, I've tried to reproduce it: https://jsfiddle.net/35ukvpty/13/
But everything works as expected. Maybe there was an issue for version 0.2.0 cause 0.2.1 is out. But I've changed nothing relating to dom stuff.
Tested on Chrome Canary 70.0.3530.0 on Windows 10

Did you solved it? If not could you please provide the steps to reproduce it?
Or create a JSFiddle.

I'll close it because of inactivity.


Text::Wrap module / submodule conflict.

Hi, I've previously installed the module Text::Wrap with no issue.
Here is it's meta file:
{
  "perl" : "6.*",
  "name" : "Text::Wrap",
  "license" : "Artistic-2.0",
  "version" : "0.0.3",
  "description" : "Wrap text.",
  "author" : "Jonas Kramer<EMAIL_ADDRESS>  "repo-type": "git",
  "source-url" : "git://github.com/jkramer/p6-Text-Wrap.git",
  "depends" : [],
  "build-depends" : [],
  "test-depends" : [],
  "provides" : {
    "Text::Wrap" : "lib/Text/Wrap.pm6"
  }
}

The module Pretty::Table depends on Text::Wrap. However, Pretty::Table now complains when I try to use it.
===SORRY!=== Error while compiling /home/bazzaar/home#sources/3D8D3D2548BB69EE2C8D1CA7603C838CFAA227E6 (Pretty::Table)
Undeclared routine:
    wrap-text used at line 1049

Now, when I try to install Text Wrap, I instead get the "_" module installed.
bazzaar@localhost:~> zef install --force-install Text::Wrap
===> Searching for: Text::Wrap
===> Updating fez mirror: https://360.zef.pm/
===> Updated fez mirror: https://360.zef.pm/
===> Testing: _:ver<0.0.1>:authzef:codesections
===> Testing [OK] for _:ver<0.0.1>:authzef:codesections
===> Installing: _:ver<0.0.1>:authzef:codesections
bazzaar@localhost:~> zef locate Text::Wrap
===> From Distribution: _:ver<0.0.1>:authzef:codesections:api<>
Text::Wrap => /home/bazzaar/.raku/sources/2036EB45B46316C08264CAC129AF51520F4342FD
I'm just wondering, was it the intention to replace the Text::Wrap module, with the "_"::Text::Wrap submodule?

OK, managed to figure out how to install the Text::Wrap module, so for me this was a useful exercise :
bazzaar@localhost:~> zef -v search Text::Wrap
===> Updating fez mirror: https://360.zef.pm/
===> Updated fez mirror: https://360.zef.pm/
===> Updating cpan mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/cpan1.json
===> Updating p6c mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/p6c1.json
===> Updated p6c mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/p6c1.json
===> Updated cpan mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/cpan1.json
===> Found 3 results
---------------------------------------------------------------------------------------------------------------------------------------------------
ID|From                            |Package                            |Description
---------------------------------------------------------------------------------------------------------------------------------------------------
0 |Zef::Repository::Ecosystems<fez>|_:ver<0.0.1>:auth<zef:codesections>|A meta package for zero-dependency micro packages of under 70 lines of code
1 |Zef::Repository::Ecosystems<p6c>|Text::Wrap:ver<0.0.3>              |Wrap text.
2 |Zef::Repository::LocalCache     |_:ver<0.0.1>:auth<zef:codesections>|A meta package for zero-dependency micro packages of under 70 lines of code
---------------------------------------------------------------------------------------------------------------------------------------------------
bazzaar@localhost:~> zef install "Text::Wrap:ver<0.0.3>"          # <--------- Need to enclose in quotes !!
===> Searching for: Text::Wrap:ver<0.0.3>
===> Testing: Text::Wrap:ver<0.0.3>
===> Testing [OK] for Text::Wrap:ver<0.0.3>
===> Installing: Text::Wrap:ver<0.0.3>

Will close this issue.


[5.5] Disable the development flag on the 5.5 branch, marking 5.5 binaries as release builds

Mark SwiftPM binaries produced from the 5.5 branch as release instead of development binaries.  Among other things this disables the use of 999.0 as a valid package tools version.
Motivation:
This is done for every release branch once it has been created.  As this change is only made on the release branch, main continues to be marked as a development branch.
Modifications:

change a boolean flag in SwiftPM

@swift-ci please smoke test

@swift-ci please test

Failed to download the toolchain in Linux.  Trying test again.

@swift-ci please smoke test linux


Updated the paths for images for java tutorial

Description
Since https://github.com/dmlc/web-data/pull/132 got merged, updating the paths based on that.
@andrewfayres @lanking520 @zachgk @nswamy

@mxnet-label-bot add [pr-awaiting-review]
Thanks for your contribution @piyushghai

Thanks for your contribution @piyushghai , now merge it


constant structs for the property names are incompatible with ARC

These added structs are incompatible with ARC. I get compiler errors "error: ARC forbids Objective-C objects in structs or unions"
Actually, I see "<$if TemplateVar.arc$>__unsafe_unretained<$endif$>" checks in them, but they don't fire for me...
Where is TemplateVar.arc supposed to be set?
I'll try to investigate.
OK, found about the "--template-var arc=true" option. A short but complete up-to-date documentation would be great

Thanks for asking the question actually, this was perfect quick help … and it worked.


Using 'KeyDelimiter' instead of ":"

/cc @ChengTian

Why is testing failing on Travis CI?

What I have seen that there is a test fails in Microsoft.Framework.Configuration.EnvironmentVariables.Test.EnvironmentVariablesConfigurationSourceTest. while all the tests passed successfully in my end

@davidfowl I update the PR to react the changes in ConfigurationBase

Also I reach the changes in ConfigurationSection because it breaks two unit tests, now everything as excepted :smile:

@divega I update the PR

Looks good now :shipit:

Oh, one more thing. Please rebase and squash

Ok @victorhurdugaci

Done @victorhurdugaci

Please squash everything to 1 commit

I squash the commits to 1 :smile:

@mikaelm12 can you please merge this?

@kirthik can you take care of merging this?

:watch:

merged 017b7ba1120ad9cf1ecb29377cafe8617506b3e6


Ability to view rigging to a mesh from specific bone.

The ability to see which vertices of a mesh are rigged to a certain bone. Can be greyscale or in a rainbow heatmap.

I don't think a rainbow gradient would be the right choice here since a rainbow doesn't have a clear transition from dark to light. The different colored hue bands tend to create false patterns and cause confusion. For color ramps, I'll probably end up using a color ramp similar to Blender or Maya. Grayscale is also safe option for intensity values like this.
https://docs.blender.org/manual/en/latest/sculpt_paint/weight_paint/introduction.html#the-weighting-color-code
This will require a number of changes to ssbh_wgpu, so it probably won't be implemented any time soon.

Yeah, that was the color scheme I was thinking of. Also I know it'll take a lot for that to be implemented, I just wanted to put it on your to-do list since the issues tab was a bit lacking.


Improve the css style for the html report

Included a couple of css rules to make the report a bit more elegant. Here's an example output:

Thanks!


docs(reference): add links to top with jump2header

Demo
Generated with:
jump2header --file Reference.md --slug "props-index" --start "source" --end "onFileDownload"

jump2header --file Reference.md --slug "methods-index" --start "extraNativeComponentConfig" --end "clearHistory"

If you don't like the PR but interested in links to top see jump2header for more options.
Summary
jump2header links will help for navigating it md file.
Checklist

[ ] I have tested this on a device and a simulator
[x] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

Thanks @strdr4605 !


Project folder cleanup: helpers, src root naming, and tests

I got a bit carried away here. Really 3 PRs in one related to PR #167 project organization issue.

Moves tests to a src/tests directory. Would have moved them to a top-level /tests dir, but react-scripts forbids it. Not hyped about src/tests but it maintains one folder per concern, technically.
Moves helpers to the more canonically named src/utils directory. Normalizes the file names and deletes unused files. Notably, two of the files that remained were imported only within dead code in another file. If we don't need them, it would be nice to be able to prune these two.
Normalizes the names of all of those components that remain (for now) in the /src root.

Tests passing and nothing looks amiss on the front end or console.

Alright - I can respond to the line comments independently, but I can't respond to the review comments directly, so I'll get them all here. I just need a firm opinion on each to move forward.

Test location: from what I'd been told, the convention with Jest is to put tests next to the files that they test. Is that not the case?

Jest doesn't discriminate, so long as tests are either in a dir named __tests__ or have .test.js as a suffix. I thought about both approaches. Because tests are a concern, just the same as styling or markup, I wanted to maintain our directory per concern approach. If you'd strongly prefer tests alongside their subjects. We may do that.

I do like 'utils' better (it's what I choose for my own projects) and I like the move in general. I'm not sure all of these are 'utils' exactly, though. For example, I wouldn't call the Result class a util. That's more about deciding where those others go, not about choosing the file name, but it is something we should work out.

Results had lived in helpers. Helpers and utils are largely synonymous to me. In my work (using rails), we have what is effectively a non-view, non-model related logic folder for helper objects, named objects as per the ruby on rails convention. I figure for us, that is utils, but it could be generalized to logic. utils is certainly more canonical.

'Beta.js' is meant to contain beta version/prototype stuff, not just the warning. For example, a 'Feedback' button. Now that I think about it, though, the recent discussions about how feedback is going to work imply that there won't be a 'Feedback' button, so maybe that's not the plan we want. Eh, we'll see how it pans out I guess.

If that's the case, I would suggest separate files BetaWarning and BetaFeedback since each is a unique React component. They're not really related and don't have to appear together either spacially or conceptually, so I don't think we need to couple them. I'm in favor of following convention here: one component per file, with the filename matching the component.

Jest

Do whatever convention is and, beyond that, whatever path your heart follows!

Results

The name utils is fine. I'm saying not everything in there should be in there. We'll figure out how nuke 'Results.js', for example.

I would suggest separate files BetaWarning and BetaFeedback

Sounds good!


Add anonymous route access support, when authentication is enabled on a route

Description of the Change
Add support for anonymous access on routes, plus a new helper function to test whether we have an authenticated user or not.
For the anonymous access, a new -AllowAnon switch has been added to Add-PodeRoute. If an unauthenticated user hits a Route with this switch then they can access the page - and not be redirected to the FailureUrl/Login page.
For testing if the user accessing the Route is authenticated or not, there's a new Test-PodeAuthUser function.
Related Issue
Resolves #954
Examples
Add-PodeRoute -Method Get -Path '/' -Authentication 'Login' -AllowAnon -ScriptBlock {
    if (Test-PodeAuthUser) {
        $session:Views++
        Write-PodeViewResponse -Path 'auth-home' -Data @{
            Username = $WebEvent.Auth.User.Name
            Views = $session:Views
        }
    }
    else {
        Write-PodeViewResponse -Path 'auth-home-anon'
    }
}

Now, when an authenticated user hits the page, they're shown the original personal greeting page with view counter. However, when an unauthenticated user hits the page they are shown a generic greeting with a login button.

Oh, this also centralises all of the Using Variable logic for splatting.


Disable table propagation to new shards

We use /docker-entrypoint-initdb.d (https://github.com/ClickHouse/ClickHouse/blob/master/docker/server/entrypoint.sh#L107) to initialize our shards and I'm wondering if it's possible to disable the table propagation for a given CHI? thanks!

I think we need to have 3 options for schema:

Propagate everything (table & databases)
Propagate databases (for Replicated database engine)
Disable propagation

Hi @a-dot , version 0.19 and above has a special setting to disable schema propagation: https://github.com/Altinity/clickhouse-operator/blob/145b1d329c2d1ab1726b654e211b8f44ba2e1c62/deploy/operator/parts/crd.yaml#L672
Set it to None in order to disable, like this: https://github.com/Altinity/clickhouse-operator/blob/145b1d329c2d1ab1726b654e211b8f44ba2e1c62/docs/chi-examples/99-clickhouseinstallation-max.yaml#L168

That's great! I'll close the issue now! Thanks!


Add 0x Tracker to love.yml

Staticaly is being used on the Tokens page of 0x Tracker (https://0xtracker.com/tokens) to ensure token images have proper cache headers. Token images are being pulled from https://github.com/TrustWallet/tokens via the Github API but images served via the Github CDN don't have appropriate cache headers.

Hi @fransallen I've added a description to the PR explaining how they're being used 👍


[FEATURE REQUEST]: Custom Jellyfin Options For Users

I want to be able to make the user enable to show up on the login screen without me having to enable it

Hey, this was closed as completed but how can I utilize it?

Feature requests have moved to https://features.wizarr.dev


Fails to compile on Ubuntu 11.04/w Node 0.4.12

Hi Sannis,
Great work! Your most recent commit looks to have caused a reversion, going back to the prior version allows it to compile:

root@raven:/home/celer/Project# cat /etc/issue.net
Ubuntu 11.04
root@raven:/home/celer/Project# date
Mon Oct 17 19:46:00 MDT 2011
root@raven:/home/celer/Project# node -v
v0.4.12
root@raven:/home/celer/Project# git clone git://github.com/Sannis/node-mysql-libmysqlclient.git
Cloning into node-mysql-libmysqlclient...
remote: Total 2777 (delta 1961), reused 2225 (delta 1693)
Receiving objects: 100% (2777/2777), 562.65 KiB | 705 KiB/s, done.
Resolving deltas: 100% (1961/1961), done.
root@raven:/home/celer/Project#
root@raven:/home/celer/Project# cd node-mysql-libmysqlclient/
root@raven:/home/celer/Project/node-mysql-libmysqlclient# uname -a
Linux raven 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:18:14 UTC 2011 i686 i686 i386 GNU/Linux
root@raven:/home/celer/Project/node-mysql-libmysqlclient#
root@raven:/home/celer/Project/node-mysql-libmysqlclient# node-waf configure
Checking for program g++ or c++          : /usr/bin/g++
Checking for program cpp                 : /usr/bin/cpp
Checking for program ar                  : /usr/bin/ar
Checking for program ranlib              : /usr/bin/ranlib
Checking for g++                         : ok
Checking for node path                   : not found
Checking for node prefix                 : ok /usr/local
Checking for library mysqlclient_r       : yes
Checking for header mysql.h              : yes
'configure' finished successfully (1.918s)
root@raven:/home/celer/Project/node-mysql-libmysqlclient# make
node-waf build
Waf: Entering directory /home/celer/Project/node-mysql-libmysqlclient/build' [1/5] cxx: src/mysql_bindings.cc -> build/default/src/mysql_bindings_1.o [2/5] cxx: src/mysql_bindings_connection.cc -> build/default/src/mysql_bindings_connection_1.o [3/5] cxx: src/mysql_bindings_result.cc -> build/default/src/mysql_bindings_result_1.o ../src/mysql_bindings_connection.cc:455:5: error: prototype for ‘int MysqlConnection::EIO_Connect(eio_req*)’ does not match any in class ‘MysqlConnection’ ../src/./mysql_bindings_connection.h:175:17: error: candidate is: static void MysqlConnection::EIO_Connect(eio_req*) ../src/mysql_bindings_connection.cc: In static member function ‘static v8::Handle<v8::Value> MysqlConnection::Connect(const v8::Arguments&)’: ../src/mysql_bindings_connection.cc:529:73: error: invalid conversion from ‘void (*)(eio_req*)’ to ‘int (*)(eio_req*)’ ../src/mysql_bindings_connection.cc:529:73: error:   initializing argument 1 of ‘eio_req* eio_custom(int (*)(eio_req*), int, int (*)(eio_req*), void*)’ ../src/mysql_bindings_connection.cc: At global scope:      ../src/mysql_bindings_connection.cc:1098:5: error: prototype for ‘int MysqlConnection::EIO_Query(eio_req*)’ does not match any in class ‘MysqlConnection’ ../src/./mysql_bindings_connection.h:242:17: error: candidate is: static void MysqlConnection::EIO_Query(eio_req*) ../src/mysql_bindings_connection.cc: In static member function ‘static v8::Handle<v8::Value> MysqlConnection::Query(const v8::Arguments&)’: ../src/mysql_bindings_connection.cc:1193:70: error: invalid conversion from ‘void (*)(eio_req*)’ to ‘int (*)(eio_req*)’ ../src/mysql_bindings_connection.cc:1193:70: error:   initializing argument 1 of ‘eio_req* eio_custom(int (*)(eio_req*), int, int (*)(eio_req*), void*)’ Waf: Leaving directory /home/celer/Project/node-mysql-libmysqlclient/build'
Build failed:  -> task failed (err #1):
{task: cxx mysql_bindings_connection.cc -> mysql_bindings_connection_1.o}
make: *** [mysql_bindings.node] Error 1
root@raven:/home/celer/Project/node-mysql-libmysqlclient#
root@raven:/home/celer/Project/node-mysql-libmysqlclient#
root@raven:/home/celer/Project/node-mysql-libmysqlclient# git checkout 5447e42388
Note: checking out '5447e42388'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at 5447e42... Add Sergey Novgorodsky to contributors list
root@raven:/home/celer/Project/node-mysql-libmysqlclient# make
node-waf build
Waf: Entering directory /home/celer/Project/node-mysql-libmysqlclient/build' [1/5] cxx: src/mysql_bindings.cc -> build/default/src/mysql_bindings_1.o [2/5] cxx: src/mysql_bindings_connection.cc -> build/default/src/mysql_bindings_connection_1.o [3/5] cxx: src/mysql_bindings_result.cc -> build/default/src/mysql_bindings_result_1.o [4/5] cxx: src/mysql_bindings_statement.cc -> build/default/src/mysql_bindings_statement_1.o [5/5] cxx_link: build/default/src/mysql_bindings_1.o build/default/src/mysql_bindings_connection_1.o build/default/src/mysql_bindings_result_1.o build/default/src/mysql_bindings_statement_1.o -> build/default/mysql_bindings.node Waf: Leaving directory /home/celer/Project/node-mysql-libmysqlclient/build'
'build' finished successfully (4.688s)

Looks like I make mistakes in #defines. I'll check it with v0.4.12 today.

1.2.5 published, thanks for reminding.


[WFCORE-5018] Upgrade woodstox:stax2-api 4.2.1

JIRA: https://issues.redhat.com/browse/WFCORE-5018
Signed-off-by: Jeff Mesnil<EMAIL_ADDRESS>
Tag: https://github.com/FasterXML/stax2-api/releases/tag/stax2-api-4.2.1
Diff to previous integrated release: https://github.com/FasterXML/stax2-api/compare/stax2-api-4.2...stax2-api-4.2.1

Core - Full Integration Build 9733 outcome was FAILURE using a merge of 3a3012d76ee374c10ef5ed28bc7d9c29bd25f363
Summary: Compilation error: Compiler (new) Build time: 00:00:59


Persistent USB Naming Broken/Changed

Home Assistant release with the issue:
0.70.0

Last working Home Assistant release (if known):
0.69
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io

Component/platform:
Persistent USB names.

Description of problem:
Persistent USB names are broken in the new release.  Zwave device is no longer configured properly because the component cannot locate the USB zwave stick using the "by-id" name.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
#Zwave
zwave:
  usb_path: '/dev/serial/by-id/usb-0658_0200-if00'

Traceback (if applicable):

Additional information:
N/A

I have the same issue using Hass.io on an Ubuntu linux server

Closing as duplicate.

People reported this issue for a plain Docker install. @balloob confirmed this in the forum.
So the issue is not hassio specific therefore no duplicate?

Please open a new issue for plain docker.


wizard must execute reload from jenkins

On the release of Core-1.4.2 I was not able to get the buttons and news articles to work until "reloading core releases" via CMM. I guess this needs to be accomplished in the Release Wizard somewhere so that other steps can complete properly.

After reloading the core releases, I was presented with two news articles... Which seems odd - it should only present one - the most recent.

dup

dup


more explicit license info?

I see MIT in your Cargo.toml but it might be nice to get that into the README and maybe a copy of the file with copyright info into the repo: https://opensource.org/licenses/MIT
Maybe it doesn't really matter but on github, you end up having to know to look into Cargo.toml to find it..

Hey, thanks for getting in contact. Sure thing, I'll update the repository shortly with the licensing information.


Pace is very slow on iOS 11 Safari

It goes slowly to 99% and stops for a few seconds on iOS 11 Safari. On desktop Safari or Chrome there's no problem, but on iOS Safari, it rises slowly to 99 % and stops for about 30 seconds before finishing (if it finishes at all, that is).

Did you try with an another browser on your phone?

It looks to have solved by itself (probably was my iPhone's fault). Sorry for having bothered you.

I have the same problem. For me it's an autoplayed inline video, whose loading is blocked by webkit if the iPhone is on "Power saving" mode.
No real solution found yet. I might have to display some text to enquire users to turn off this mode or to use a GIF instead...


New api

This introduces new API for creating producers / consumers.

It allows defining custom RequestStrategy
It allows passing additional kafka-specific settings

Some nice additions @kciesielski - looking forward to see them in the next version!

Nothing more to add from me, the changes look good!!

:+1: looking good

:+1:


Fix Invalid path error in TravelLogUnit

This should fix EDDiscovery/EDDiscovery#2917

Thanks.  I'll do another EDD soon.


Whitespace coloring

A recent update to doom-theme (that I still cannot find) trailing white space in red. How can I disable this? I thought I can control it with 'show-trailing-whitespace' but that variable is already nil.
ws-butler automatically removes these whitespaces on disk (even though it keeps showing them in some cases) making the alert unnecessary.

You're right. This was redundant with show-trailing-whitespace (which is now on by default as of 72e8178e). This should be resolved as of 47f0f77. Let me know if that isn't the case and I will reopen this issue. Thanks for bringing it to my attention!


support CastTimeAsDuration in TiFlash

What problem does this PR solve?
Issue Number: close #5306
Problem Summary:
support CastTimeAsDuration in TiFlash
What is changed and how it works?

register the cast function
implement the calculation for casting time to duration
add tests of conversion

Check List
Tests

[x] Unit test
[x] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/retest

/run-all-tests

/cc @CalvinNeo

/cc @JaySon-Huang

/retest

/cc @ywqzzy

/cc @SeaRise

/run-all-tests

/run-unit-test

/run-integration-test

the pr link of tidb:
https://github.com/pingcap/tidb/pull/37036

/run-integration-test

/rebuild

/run-integration-test

/run-unit-test

the pr link of tidb: pingcap/tidb#37036

like https://github.com/pingcap/tiflash/pull/5156

the pr link of tidb: pingcap/tidb#37036

like #5156

done,thx

the pr link of tidb: pingcap/tidb#37036

like #5156

done,thx

Also please add release notes. like

the pr link of tidb: pingcap/tidb#37036

like #5156

done,thx

Also please add the release note. like

done

/run-all-tests

/cc @ywqzzy

/run-all-tests

/cc @ywqzzy

/cc @Willendless

/merge

/cc @CalvinNeo
/cc @JaySon-Huang


[Regression] Artifical clipping on rotated map (Android only)

Mapsui Version
4.0.0-beta.11
Mapsui Platform
Xamarin.Forms
Device
Android 13
Describe the bug
I'm seeing a problem with rotated maps with v4.0.0-beta.11 on Android.  See screenshot below (map rotated by 90°).
This was working with beta.10 (the problem appeared with beta.11). It works on iOS, but fails on Android. Non-rotated maps work fine. I suspect it was broken by #1959.
Expected behavior
The circle should be drawn over the full viewport and not be clipped artificially.
Screenshots

Oh no, did I push my code to test clipping? I am on phone right now so not easy to check.

I broke it here. https://github.com/Mapsui/Mapsui/pull/1959#discussion_r1176029629. Removing the Grow(-50) will fix it.

Why does it only occur on Android, though?

Probably it also occurs on iOS. I think I simply did not use a rotated map on iOS when I tried it.


[Error: ENOENT: no such file or directory, stat lock file

I just run like as usual. But sometimes got this error
Uncaught Exception: [Error: ENOENT: no such file or directory, stat 'D:\Repositories\dl-traffic-python\data\run\FingerprintPluginV10\e3274\browser.17\s\xbK0UfzU.ini.lock'] {
  errno: -4058,
  code: 'ECOMPROMISED',
  syscall: 'stat',
  path: 'D:\\Repositories\\dl-traffic-python\\data\\run\\FingerprintPluginV10\\e3274\\browser.17\\s\\xbK0UfzU.ini.lock'
} undefined

i catch this error by using below codes
process.on("uncaughtException", (err) => {
    if (!(err instanceof Error)) {
      // If it's not an instance of Error, create one manually to preserve the context.
      err = new Error(String(err));
    }
    logError("Uncaught Exception:", err, err.track);
    // Send some notification about the error
    process.exit(1);
  });

Compromised lock will be ignored and will stop throwing errors - instead, information output via debug has been added so far.
The fix will be available in the new version, if the problem still remains, please let me know.


Create a Stack Exchange Imgur account to host image files

I believe we pay for a custom instance from them: stack.imgur.com. Currently the only way to get images on to it is via API.
We should either set up a page somewhere to allow blog users to upload images to it, or get in contact with them to work out an upload form.
Of course, we could also just set up an account on imgur.com directly.

We do have an arrangement with imgur already - all photos on Q&A posts are hosted there. I usually lazy-upload by starting a new post and uploading from the editor. Would be cool to have a lightweight UI for this. s.tk/upload or something.

Talk to a core dev. They might be able to create an upload page only accessible to employees which re-uses the existing code paths for uploading a file and getting the link.

@ironyx is this something we can do?

@jc4p is taking point on this, working on a UI that lets users upload, (optionally) slice, resize, and push to repo internally. Related issues https://github.com/StackExchange/blog/issues/35 https://github.com/StackExchange/blog/issues/24 https://github.com/StackExchange/blog/issues/20

Spoke with @jc4p on this for a pretty straightforward implementation.

@jc4p any progress on this front?

I take it imgur corporate hosting is sunsetting us? Guess I know what I'm
working on when I return. ;)
On May 7, 2015 8:11 AM, "Jon H.M. Chan"<EMAIL_ADDRESS>wrote:

I figured.
—
Reply to this email directly or view it on GitHub
https://github.com/StackExchange/blog/issues/36#issuecomment-99859582.

Until we figure out what in the seven kingdoms is going with Imgur, @rmaleady and I are using GH Issues and their CDN to host. Closing until we hear more.

Reopening - apparently we're going to be able to continue using Imgur for the forseeable future. We still need to scrub posts and reupload. cc @rmaleady @jc4p

Roll with it as imgur. If we do something else, there will be along enough transition that it won't be that big of a deal to switch it. Program it to an interface or something though so it's an easy swap component. ;)

@jonhmchan any requirements for max long edge/aspect ratio/etc?
I'm going to make all the uploaded images run through an image optimizer (pngcrush/something for JPGs), but do we have any non technical requirements for then pertaining to look and feel?

@jc4p no non-technical requirements

@jc4p ETA on when we can use the tool to do the image conversions?

EOD
On Wed, May 20, 2015 at 9:41 AM Jon H.M. Chan<EMAIL_ADDRESS>wrote:

@jc4p https://github.com/jc4p ETA on when we can use the tool to do the
image conversions?
—
Reply to this email directly or view it on GitHub
https://github.com/StackExchange/blog/issues/36#issuecomment-103892597.

Here's what the latest version of the code for this looks like:

You can then copy that URL and put it into your blog post.
The code for it lives in https://github.com/StackExchange/SEBlogImageUploader -- It's not hosted anywhere yet because I have absolutely 0 clue how to get something hosted internally and I was told that Heroku was bad. How do we do that side of it?
It's also using kraken.io to do the image resizing and image optimization stuff, right now it's on a free tier account, I'm not sure if we'll need to end up upgrading that account to a paid one or not.

Taking it from here - I think I might just get this to be implanted into some part of Core (I also want us to pull in some authentication features that are already built in there). Going to chat with @ironyx about it.

Done here: http://blogtools.ds.stackexchange.com/ (you need to be on the VPN or on the office network to access)


python3Packages.scmrepo: 0.0.16 -> 0.0.17

Description of changes
https://github.com/iterative/scmrepo/releases/tag/0.0.17

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 167720 run on x86_64-linux 1

4 packages built:

dvc
dvc-with-remotes
python310Packages.scmrepo
python39Packages.scmrepo


ERROR: java.io.IOException: Could not read the crosstool configuration file

Hi guys,
so I've been installing Magenta and Bazel and when I type:
bazel test //magenta/...
I get an ERROR message:
ERROR: java.io.IOException: Could not read the crosstool configuration file 'CROSSTOOL file C:/users/fei/appdata/local/temp/_bazel_fei/uyk23a1f/external/local_config_cc/CROSSTOOL', because of a parser error (289:987: Expected identifier. Found '%').
and then followed by:
ERROR: Couldn't start the build. Unable to run tests.
Can anyone help? :'(

I haven't see that error before, but it looks like an issue with bazel on windows. I'd suggest reporting it on the Bazel project issue tracker: https://github.com/bazelbuild/bazel/issues

Okay thanks


feat(#369): Add lots of opcode handlers

Add more opcode handlers and 'benchmark' integration test classes.
This PR is related to: #369

History:

feat(#369): add integration test cases that fail
feat(#369): add more return opcodes
feat(#369): add more load opcodes
feat(#369): add math instructions handler
feat(#369): add convertation opcodes
feat(#369): add comparision opcodes
feat(#369): add branch opcodes

PR-Codex overview
This PR focuses on adding benchmarking functionality to the codebase.
Detailed summary

Added F interface with foo() method
Added App class with run() method
Added Main class with main() method for benchmarking
Modified pom.xml to exclude certain files from coverage and complexity checks
Added BytecodeInstructionEntry class with various methods and instructions

The following files were skipped due to too many changes: src/main/java/org/eolang/jeo/representation/bytecode/BytecodeInstructionEntry.java

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

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 4min)

@rultor release, tag is 0.2.9, title is 0.2.9.

@rultor release, tag is 0.2.9, title is 0.2.9.

@volodya-lombrozo OK, I will release it now. Please check the progress here

@rultor release, tag is 0.2.9, title is 0.2.9.

@volodya-lombrozo Done! FYI, the full log is here (took me 7min)


Support multi-byte ToUnicode entries, when using predefined CMaps (issue 16176)

Hopefully this makes sense, since we already "create" multi-byte ToUnicode entries in other cases (see e.g. the getNormalizedUnicodes table).

/botio test


add support annotation

adding support (and containerImage)

Signed-off-by: razo7<EMAIL_ADDRESS>

disagree, see comments here: https://github.com/medik8s/node-healthcheck-operator/pull/89#discussion_r802937134
/hold

There is no need to fix csv annotations, in particular createdAt, therefore I am changing the PR to adding support(andcontainerImage)

/retest

Trying to only add the support field made the CI fail. @slintes Do you understand why?

/retest

@razo7 can you please add a link to some doc on what this annotation means?

See in OCP or Operator-sdk - the Operator provider, with a name; usually an organization.

@razo7 can you please add a link to some doc on what this annotation means?

See in OCP or Operator-sdk - the Operator provider, with a name; usually an organization.

that's provider, not support 🤷🏼

@razo7 can you please add a link to some doc on what this annotation means?

See in OCP or Operator-sdk - the Operator provider, with a name; usually an organization.

that's provider, not support 🤷🏼

That's correct, here you can see the required fields for OperatorHub and support is one of them - The name of the individual, company, or service that maintains this operator.
Except this link I haven't found any other reference to support in other places :)

thx, I added it to the PR description
/lgtm
/approve
/hold cancel


User story: As an analyst I want access to compiled records so that I can perform coverage reviews

Our ETL process for BigQuery included a script that generated records by merging individual releases for a given OCID together.
This is important when performing coverage reviews, to be able to check how many unique contracting processes have a particular set of fields etc.
As records (latest version of everything we know about a process) are conceptually distinct from releases (whatever information was provided in the last update), an analyst should have to consciously choose which they are querying. I.e. we should likely avoid the case when a query would accidentally check both releases and records (as this could also lead to double counting problems).
Suggested solution:

A step should be added to the pipeline to create merged records;
This step should be optional (we don't always need it), and possible to run on just a sample of the total data for a given publisher;

cc @duncandewhurst Does the above cover what we discussed?

@timgdavies, yes thanks
For reference, this slide and this discussion give some more background on why this is important

@kindly do you fancy doing this?

This would be really useful for some of the work I'm doing on evaluating the NSW Australia data.
I'm trying to check for how many contracting processes a particular indicator can be calculated, based on the presence of a group of OCDS fields, and it would be easier to check that by looking at a single compiled release than by checking whether the group of fields is split across multiple releases.

I would like for transforms – like compiling releases, or upgrading 1.0 data to 1.1 data – to be implemented in a generic, reusable way as described briefly here.
OCDSKit also has a very simple implementation for compiled releases. However, unlike the script linked from the issue description, it doesn't add any record metadata.
In an MVP, we wouldn't need the following, though it could be interesting to explore later:

storing a history of transform operations, e.g. a TransformJob that, for compiling releases, might store the name of the Transform, the inputs to the Transform (e.g. the source and any additional filters), any errors, and the dates it was started, finished, etc. (as we have for gather and fetch)
storing what inputs were used to produce each output within an operation, e.g. a TransformLog that, for compiling releases, might refer to the transform job and store the input (references to specific releases) and the output (reference to specific compiled release)

Note: OCDS Kit's compile command now does the same, and more, than the old linked script.


Update Kubernetes proxy URLs

This is briefly mentioned in the comment of a previous issue https://github.com/apache/incubator-heron/issues/2913#issuecomment-448798534.
Kubernetes made an API change to the proxy URL, which brakes some links in this repository.
Proxy URLs used to have /proxy in the middle, but it is moved to the end (See https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster/#manually-constructing-apiserver-proxy-urls)
The list of links that need to be changed can be found here

Here is a list of links follows to the newest API:

Thanks for the note @ShawnZhong.  We will hopefully get it addressed soon!


Not all VSTS projects are being shown

Not all VSTS projects are being shown if the VSTS account has more than 100 projects.
100 is the default value for the $top parameter
https://www.visualstudio.com/integrate/api/tfs/projects
We could

increase the number of $top
loop until we have no more projects

Fix available in Version 0.4.1


OAuthPage UI customizations

fixes https://github.com/orgs/medplum/projects/1/views/17?pane=issue&itemId=69935428&issue=medplum|medplum|4805

Added welcome string and logo as Attachment to ClientApplication.
New endpoint /auth/clientinfo/:clientId returns welcome string and logo attachment.
Modified OAuthPage to use new endpoint and display custom UI.

Deploying to staging: https://github.com/medplum/medplum/actions/runs/12098813196


perf: ⚡ trigger event when cell view inserted to provide performance optimization point out of X6

Description
perf: ⚡ trigger event when cell view inserted to provide performance optimization point out of X6

Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Enhancement (changes that improvement of current feature or performance)
[ ] Refactoring (changes that neither fixes a bug nor adds a feature)
[ ] Test Case (changes that add missing tests or correct existing tests)
[ ] Code style optimization (changes that do not affect the meaning of the code)
[ ] Docs (changes that only update documentation)
[ ] Chore (changes that don't modify src or test files)

Self Check before Merge

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

model.ts 中的 addCells() 会循环调用同 model 中的 addCell() 方法，导致 batchStart() 后触发 singleStop()，本方式有问题，需要重新设计


Add support for addons on cluster type creation for GKE

This PR adds support for Addons on cluster type creation for GKE.
Not covered in this PR and possible next steps:

support updating existing addons and add/remove addons from cluster type
support for Addons on cluster type creation for other clusters EKS, AKS, OKE

Looks great, thanks!


fix bug where same user whose host and member doesn't show up as host…

If same user is host and member of a collective, currently they won't show up as host and thus no donations can be accepted by collective. For example, see opencollective.com/golix.

But then they will show up twice in the list of users no?
shouldn't we instead return the host as part of returning the group? Since there is a 1:1 relationship here, it would make more sense rather that including that singleton as part of a large selection of users.

Frontend already dedups - I added that as part of the new collective page.
I could see a case for returning HOST as part of the group. I'd say, let's avoid that extra query now and get this out. Sending HOST differently will require changes on the frontend too, instead of relying on UsersByRole, so slightly bigger change.


What are the deps?

The README says to "install deps" but doesn't say what they are.
Thanks

run yarn

So as I understand it that would install yarn. If I run it it tells me that yarn is already up to date. So I take it it's not referring to further dependencies?
I'm asking because I get this:

$ yarnpkg start
yarn run v1.22.10
$ node app
internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module 'fs/promises'
Require stack:
- /home/paul/Projects/actual-server/app-sync.js
- /home/paul/Projects/actual-server/app.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
    at Function.Module._load (internal/modules/cjs/loader.js:667:27)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/home/paul/Projects/actual-server/app-sync.js:2:10)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/paul/Projects/actual-server/app-sync.js',
    '/home/paul/Projects/actual-server/app.js'
  ]
}

I guess I assumed that the missing "fs/promises" module could be part of the dependencies.

OK I've been able to run this up by creating a docker image. I just wanted to try it out to see how it compares to other similar software I've used.
I don't want to waste anyone's time on pursuing this so I'll close this issue.
Thanks anyway.


Search results navigation in Tree using keyboard is not consistent as using mouse

Navigation in search results is as follows:
Using Mouse

clicking with the mouse keeps focus in the tree
double click moves focus to the editor
Cmd/Ctrl+click opens the editor to the side

Using Keyboard

There is no way to do what mouse single click is doing
There is no way to do what Cmd/Ctrl+click is doing

@sandy081 I added support in search to Ctrl+click to open to the side. Cmd+click is taken by the OS to show the context menu so we cannot use it on Mac, but on Windows it should be fine.
I have not heard complains to have a keybinding to keep focus in the tree, so I did not add it.

Also you are free to do anything you want if you implement a TreeController. If you feel for problems you need a keybinding to keep focus, it is up to you to do so.


Keep VCF header when making compatible genotypes

It is useful to keep the names of the samples/individuals in the original VCF.

Fixed by commit e0df7b727db1415e9f9b34c038b5978cd1a44904


Json support

This PR:

Update to Arrow 0.9.0.
Use Arrow Fx style.
Add the ability to read the score error column from benchmark and use it as the threshold.
Add JSON input and output support. We are now able to read and write JSON. Fixes #15.
Both CSV and JSON benchmarks are cross-comparable.
Readme updated accordingly with all defaults too.

Note: Due to some missing fields(rawData) CSV benchmarks are not JSON printable.

Tested and working

@fedefernandez The arrow Fx dsl is ready :ok_hand: :


Consul: Hashicorp Changes Official Download Service to Fastly

Thank you for the contribution. It needed some fixes, so they were made in f107aeb27d4e3f4b68212a7b8227c4a00fa811e5. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Ugly, but it works

Coverage increased (+0.6%) to 91.216% when pulling 94dff8b2b9c9917e8e71693274ac6d98f35d1387 on feature/print-results into 30eefa8ca2ef6a3f61fd86afcf1700cf1a272111 on master.


Remove the shell extension from directory backgrounds

We're removing this because of MSFT:24623699, which prevents us from being able to do the right thing when we're called on the background of a directory for a range of OS builds.
#6414 will track re-adding this to the Terminal when the original issue is closed.

[x] closes #6245
I work here

@msftbot merge this in 6 minutes


ADD Github workflow 'Build and Test'

add a workflow on GitHub that tests the project files and their test on new pushes.
Accept criteria

runs all test related to the project vis the dotnet test command.
runs vis xunit

xunit added and smaller proof of concept tests added

Workflow for github, made and tests are driven and approve of


getting-started.md needs to clarify PV prerequisite

Prior to "Run the following commands to setup and deploy Kubeflow:", the guide needs to clarify that a prerequisite (of vizier-db) is the presence of at least one PV created with no storage class.
For the Acumos project (https://www.acumos.org/), we have work in progress for our current release to support kubeflow. I am creating kubeflow setup tools and I see that after following the process described by https://www.kubeflow.org/docs/started/getting-started/, that the vizier-db pod is failing to start as it's expecting a PV. This seems to be an oversight in the guide.
I worked aound this issue by adding the following script code prior to '${KUBEFLOW_SRC}/scripts/kfctl.sh init ${KFAPP} --platform none'. NOTE the absence of a storageClassName... this is required since vizier-db's PVC does not reference one:
sudo mkdir /mnt/data
cat <pv-volume.yaml
kind: PersistentVolume
apiVersion: v1
metadata:
name: task-pv-volume
labels:
type: local
spec:
storageClassName:
capacity:
and I see that after following the process at https://www.kubeflow.org/docs/started/getting-started/
storage: 10Gi
accessModes:
- ReadWriteOnce
hostPath:
path: "/mnt/data"
EOF
kubectl create -f pv-volume.yaml
kubectl get pv task-pv-volume

I think the issue here is that Katib is by default relying on the existence of a default storage class.
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class-1
If your cluster defines a default storage class then it will automatically provision a PV for that PVC.
If your cluster doesn't have a default storage class then the options are

Create a PV manually (as in the comment)
Disable the use of a PVC and just write to a pod volume

Using a host mounted path in general isn't very robust because pod may be reassigned to a never node.
I think updating the docs to fully describe this would be good improvement.
I'm not sure it makes sense to run Katib without durable storage. That seems like it could cause unexpected failures.
/cc @inc0

@blsaws any interest in providing a PR to update the docs?

Alternative approach would be to refactor Katib to use external DB rather than deploying it on it's own. It would be better in general as deploying mysql is hard.

/close


Passing id to useCallback?

Hey, thanks for this library. It's wonderfully simple. I was using use-react-query-auto-sync but it wasn't working for my usecase & this one did work removing a lot of code.
I am facing 1 problem though. In the README, it's mentioned I should use useCallback but I'm not sure how to pass id to it as I need that in the mutation.
id & text is everchanging in my case.
const updateDraft = useCallback(
    (newText: string) => {
      console.log('updateDraft')
      console.log({ id: snap.doc.id, text: newText })
      updateDocs({ id: snap.doc.id, text: newText })
      toggleIsSaved(true)
    },
    [snap.doc.id]
  )

  useAutosave({
    data: snap.doc.text,
    onSave: updateDraft,
  })

I am using valtio as a global state manager. That's where the snap.doc.id is coming from. But every time, the 1st snap.doc.id gets passed because of useCallback as the same function is used so every time it mutates the same row as snap.doc.id stays the same.
I'd love to know a solution to this.
Complete reproduction on branch react-autosave → https://github.com/deadcoder0904/docs-autosync/tree/react-autosave

Sorry, I think I solved the question as I mentioned [snap.doc.id] in useCallback but I was facing another issue. When I update the text, it changes all the other mutations as the request takes place after too long when my text changes.
I think I solved that one too by passing doc directly to data & destructuring it like:
const updateDraft = useCallback(
    ({ id, text }: Doc) => {
      if (id !== '') {
        updateDocs({ id, text })
      }
      toggleIsSaved(true)
    },
    [snap.doc.id]
  )

  useAutosave({
    data: snap.doc,
    onSave: updateDraft,
  })


aws-sdk v2 support

@lserman any update on aws-sdk v2 support? I see you mentioned it a few times in the comment history. I was trying to use a gem that depends on aws-sdk v2 and just encountered the conflict.

I just noticed that you can use aws-sdk v1 and v2 at the same time, so this isn't actually a problem.

Yeah, where we need aws-sdk we use use aws-sdk-v1. Unsure if I'm going to finish v2, we are attempting to move our deployments to ECS which will allow us to stop using Capistrano altogether. We'll see!

Closing this, see comments on #20.


chore(testng): should not share runner between multiple compiler when run same file

Summary

Require Documentation?

[ ] No
[ ] Yes, the corresponding rspack-website PR is __

!test-ng

!test-ng


Logs to be added for export private key(for generated and imported accounts)

Closed by merging PR: https://github.com/getsafle/safle-vault/pull/260


HNC: release should not re-push an existing image by default

See https://github.com/kubernetes-sigs/multi-tenancy/pull/332#discussion_r360651870. By default, the release should refuse to push an image if it already exists on the repo, although we'll need a way to override (eg to push :latest or to test).

My plan here is to disallow releasing if an image and tag already exists for the resolved tag. There will be a FORCE_RELEASE flag that can be set to override this for test/bad push purposes.

Fixed by #576
/close


Msal with Angular 13

Core Library
MSAL.js v2 (@azure/msal-browser)
Wrapper Library
MSAL Angular (@azure/msal-angular)
Description
I updated to Angular 13 but I have an error with MsalService

Source
External (Customer)

I got this error installing msal on angular v13

Do you have any date for the package update?

https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/4154#issuecomment-974183734

The issue is still present when trying to install @azure/msal-angular in an Angular v13 project. The current version of RXJS when generating a new Angular v13 project is not compatible to the one used within the MSAL library. My fix was to downgrade RXJS version from 7.5.0 to 6.6.7 (the latest before v7).


feat(cloudfront constructs): add s3 access logging to cloudfront access log buckets by default

Issue #, if available:
Addresses Issue #1041
Description of changes:
Adds s3 access logging to the CloudFront log buckets by default
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 3a2043651bf467939b57f7781ccadf42574adc89
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 7a33919a6f9c1c3fc906f6c0184e87ca81fdf3d2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: e59a01bf31578168ead8da0a1e6207060cb7f47d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


[updatecli] Update jenkins/jenkins docker tag version to 2.247

! Experimental project
This pull request was automatically created using olblak/updatecli
Based on a source rule, it checks if yaml value can be update to the latest version
Please carefully review yaml modification as it also reformat it.
Please report any issues with this tool here

Superseded by #347


Error in Code Example

The following code example:
<input value="@CurrentValue"
@onchange="@((ChangeEventArgs __e) => CurrentValue = __e.Value)" />
Generates an error unless I typecast __e.Value by (bool), i.e.,
CurrentValue = (bool) __e.Value

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

ID: be4c4d0c-149c-bde1-c7fa-f082916390ca
Version Independent ID: 9d945996-ad02-bd4b-58ea-c465cc5cc74c
Content: Create and use ASP.NET Core Razor components
Content Source: aspnetcore/blazor/components.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

I don't think that it's an "error" in that sense that it was just an abbreviated example for the @bind equivalent for a textbox shown in the lead-in sentence. It's not meant for you to actually use that code in a component, nor does it currently apply to the checkbox example italicsCheck. I think that example should be based on the prior example (italicsCheck). Thanks for commenting.


Is it possible to use "linebreaks: { automatic: true }," for disp-formula but not for inline-formula?

Issue Summary
We've been using "linebreaks: { automatic: true }," for quite a while now, and for the most part, it seems OK. However, we've recently wondered if we could remove that configuration option for inline-formula but leave it as is for disp-formula.
We think we might prefer a scroll bar when needed, e.g.,

for a longer inline-formula rather than a line break, e.g.,

However, for disp-formulas, we prefer the look of the line breaks when possible, e.g.,

rather than lots of scroll bars, e.g.,

Technical details:
MathJax Version: MathJax.js v2.7.9
Client OS: Windows
Browser: Version 103.0.5060.53 (Official Build) (64-bit)
Renderer: HTML-CSS

Sure, you can use the following as part ofyour configuration:
MathJax.Hub.Register.StartupHook('HTML-CSS Jax Ready', function () {
  var MML = MathJax.ElementJax.mml;
  MML.mrow.Augment({
    _HTMLlineBreaks: MML.mrow.prototype.HTMLlineBreaks,
    HTMLlineBreaks: function (span) {
      if (this.parent.linebreakContainer && this.Get("display") === "inline") return false;
      return this._HTMLlineBreaks(span);
    }
  });
});

That will disable line breaking for in-line expressions, but still break display ones.

Thank you, Davide!

@dpvc We have made it so that line breaks don't occur in inline-formulas; however, sometimes larger inline-formulas (especially on smaller screens like cell phones) get cut off on the right side rather than displaying a scroll bar. Is there a way to make a scroll bar appear for inline-formulas if they're too large to fit in the available space? Here's an example from https://pubs.acs.org/doi/10.1021/acs.jctc.1c01044:
Here's the full equation using Chrome on my 14 in. laptop screen (displays in full):

Here's the same equation on my Samsung Galaxy S23 device (a bit of the equation is cut off on the right; no scroll bar is provided):

Please let me know if you have any ideas for what we could try to do to fix this. Thanks!

Try adding
  styles: {
    ".MathJax": {
      overflow: "auto hidden",
      display: "inline-block ! important",
      "max-width": "100% ! important"
    },
    ".MathJax_Display": {
      overflow: "auto hidden",
      "max-width": "100% ! important"
    }
  }

to your MathJax configuration (at the top level).  This should add horizontal scroll bars to in-line expressions that are wider than the container.  (It also does this for display equations that are wider than the container, which can happen even with line breaking turned on, as there may not be enough potential breakpoints to make it fit, for example.)
See if that does what you need.

Yes, thank you, that was helpful!


docker compose has a wrong clef version

https://docs.ethswarm.org/docs/installation/docker
which use the old  docker compose yaml
https://raw.githubusercontent.com/ethersphere/bee/v0.6.0/packaging/docker/docker-compose.yml

Fixed in latest release.


Add script utility type

Handles the common pattern of EVALSHA then calling EVAL if EVALSHA returns a NOSCRIPT error.
I would be happy to write some unit tests, but wasn't sure the best strategy. Would appreciate any guidance you can provide.

Hi @zombiezen,
I'm going to merge this in 6.0.0 instead of the 5.x version. I'm almost done with some major refactoring and breaking changes for better TLS support, and I'd like to put the 5.x version in maintenance mode. I'll ping you once I come back to this in a couple weeks.

Sounds good to me, thanks!

Added in 6.x


Enable ABI validation

Copy of PR #402 , this time after we've separated the windows and mac builds.

Something is conflicting with the build and causing this to not run correctly. Closing this as it's taking too much time to add and is causing a lot of headache.