RHMC cleanup

[ ] Formatting makes hisq smearing and force modules and associated files difficult to read. Should be cleaned up.
[ ] DSlash has HisqMdaggMFunctor which is not used anywhere? Should be deleted, since one would guess the applyMdaggerM method calls it, but it doesn't.
[ ] hisqforceconstructs header has a hisqforce include guard. Meanwhile hisqforce.h has no include guard. Can be fixed with #101

I may add more things. I'm cleaning up the formatting stuff right now while adding some documentation, but the other changes require testing so I'm going to postpone them to a different commit.

[ ] The HisqSmearing class has a smearAll method carrying out the level 1 hisq smear, unitarization, and level 2 smear. Separately is class has a SmearLvl1 method and a ProjectU3 method, apparently because they are used in the force. Would it make sense to have the smearAll method call these two, to reduce code redundancy?

[ ] There is some "GAUGE_NAIK" shared memory, which is only used by level 1 smearing... That's a bad typo, in case someone else wants to share with the Naik term in the future...

    //this is only a placeholder function for testing, real implementation is in HISQ force! REMOVE for production!
    void make_f0(Spinorfield<floatT, onDevice, Even, HaloDepthSpin> &phi, std::vector <floatT> rat_coeff);

This is in our integrator.h...  What do I do?
I'm adding a bunch of you guys b/c I want your perspectives on some of the stuff I'm putting in here.

[ ] both plaqconstructs.h and rectconstructs.h have the same include-guard... how is this possible? Lukas you wrote these, do you know what happened?


Support for PHP_CS Sniffs?

There are currently 2 separate discussions (I am trying to bring them together) about creating a Composer Installer for PHP CodeSniffer Sniffs.[1][2]
Would a PR for such an installer be welcomed once that discussion has been brought to a successful completion?
[1] https://github.com/squizlabs/PHP_CodeSniffer/pull/936
[2] https://github.com/wimg/PHPCompatibility/issues/102

So... Bump?

I'm very much in favour of having one official composer plugin to install PHPCS standards.
The fact that there are several available now which each work slightly differently and a number of which have serious bugs, makes things confusing for the end-user and adds an additional support burden on maintainers of PHPCS standards.
Having one actively maintained official composer plugin would make life easier.

@alcohol As I still don't see a PHP_CodeSniffer installer in the list, I would think this is still applicable.

There are many installers not in the list, so that is a somewhat flawed argument. We do not build installers, but merely accept proposals/submissions. As long as one is not provided, there is nothing for us to accept. The original post referenced two discussions, neither of which seem to have reached a definitive answer.

... merely accept proposals/submissions. As long as one is not provided, there is nothing for us to accept.

@alcohol The first step in that case would be to answer the question asked in the original issue post by @Potherca :

Would a PR for such an installer be welcomed

Installers are welcome.


Multiple outfiles folders in tsconfig.json no longer work in 1.48 debugger

Issue Type: Bug

Create a multi-project workspace with two folders imporrted
helloworld/
library/

run npm init in helloworld folder

npm install -S @types/node
npm install -S @types/reflect-metadata

create a tsconfig.json with

{
    "compilerOptions": {
        "target": "es2017",
        "lib": ["es2017","dom"],
        "types": ["reflect-metadata","node"],
        "module": "commonjs",
       "sourceMap": true,
         "outDir": "app",
        "baseUrl": "src"
    },
    "include": [
        "src/**/*",
    ]
}

Create src/helloworld.ts

import "reflect-metadata"
console.log("Hello world");

Create launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "protocol": "inspector",
            "name": "Launch",
            "cwd": "${workspaceFolder}",
            "sourceMaps": true,
            "program": "${workspaceFolder}/src/helloworld.ts",
            "outFiles": [
                "${workspaceFolder}/app/**/*.js",
                "${workspaceFolder:library}/**/*.js",
            ],
         }
 }

Start debugging, you will receive an error on the line importing "reflect-metadata" in v1.48

Works in  v.1.47!!

Remove the second outFiles: [ ] entry   "${workspaceFolder:library}/**/*.js" and it will work again in v.1.48... but this means that working with typescript/javascript files across multiple project folders is no longer possible.

VS Code version: Code 1.48.2

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz (4 x 3193)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
11.92GB (2.38GB free)

Process Argv

Screen Reader
no

VM
0%

Can you please try with the night extension? Previously the 'bootloader' script we injected use reflect-metadata internally which may have caused your issue.


Found bug where the workflow status is maintained as RUNNING.

Hi
netflix conductor build version: 2.31
db: mysql 8.x
Workflow is over, but it's status still running.
It was useless to add Terminate Task at the end.
Terminate Task document url: https://netflix.github.io/conductor/configuration/systask/#Terminate Task
(Terminate Task)
Is there any solution?
I need help.

Hello @UDragon-CK Do you have lock enabled for the workflow exeuction in your property file? As by default, it is disabled, and that could cause the risk condition for issues like what you saw.

#enable locking during workflow execution
workflow.decider.locking.enabled=false

BTW, we no longer support 2.31, and users are encouraged to migrate to 3.x
https://github.com/Netflix/conductor/discussions/2734

2.31.8 is the final release of 2.31 branch. As of Feb 2022, 1.x & 2.x versions are no longer supported.

@jxu-nflx
workflow.decider.locking.enabled
I didn't set this property.
very tired
I think the workflow status status status is being managed by ElasticSearch But I don't think it's synchronized.
Does it have anything to do with mysql?

@jxu-nflx  ~hi
I solved it by creating a scheduler in the next ui area that changes the nodejs-based RUNNING state to COMPLETED.
I'll show you the source code, too. I hope we can be of help each other.
There's only one file, and the js file itself doesn't go up, so I'll compress it into zip.
I used two api to solve the problem.

/api/wfe/bulk/pause
/api/wfe/bulk/resume

nrpWorkflowStatusUpdateScheduler.js.zip
I hope you'll always be healthy. Thank you.

Hello @UDragon-CK I am not sure I follow your solutions there. To clarify, you are using Elasticsearch as indexing server and mysql as the persistent storage, and you are not using locks, right?
my suggestion would be to enable locks so you don't end up in any inconsistent states, and if you supect there is lag/sync errors with Elasticsearch, then maybe look into that as well. As the UI is just using the search API of conductor, which does search Elasticsearch.


Fixes for the read-only root name space

Tested with and without:
echo 'OVERC_ESSENTIAL_MODE="read-only"' >> conf/local.conf

It seems like this is not based off the OverC meta-oci branch.
i.e.: linux-yocto.inc: Trust the BSP instead
I can do the cherry picks, but this prevents me from merging directly.

It might have been off an older version.  I'll rebase and add another patch in just a bit.

The other patch isn't ready yet, so we can go with what already works.  We are down to just 4 patches.

staged. in testing now.

merged


feat: command-palette group

I'm getting the docs list from this link
is it a good idea to have a docs-list-script in nuxt repository and whenever the docs ci runs, it also run the docs-list-script ?
command palette wth groups:
https://github.com/nuxt/devtools/assets/38922203/a3435658-8d36-4895-8c31-e7680ade047c

Having them in the commands sounds like a good idea, but I am not very sure about the custom search syntax and the dropdown - ideally command palette should be easy to use with only the text as the input. Maybe we could find another way to present?

@antfu Yes, thats right😁. thanks, By another way to present is something like: show the tabs and when user searchs filter between tabs, docs, ... is it a good idea?

I am thinking we could have something like Raycast, to have a second-level commands when going into some entries:


Update BOUNTIES.md re. Toyota SecOC and community bounty.

Removing text/link mentioning the community bounty as it is shuttered in favor of just saying "support" as the community bounty is shuttered for reasons listed in the reddit post:
https://www.reddit.com/r/Comma_ai/comments/1d5r7xr/state_of_toyota_security_key_secoc_and_community/
Instead, the tracking of numerous bounties around this topic will be done.
I'm not sure what criteria the $5k comma is offering for the Toyota SecOC bounty is. I'll leave it to comma to fill this out and decide what to do with that beyond the placeholder text of "support" I've put in here.
IMO and FWIW, if Willem is community, I'm cool with that bounty just being his as well as the Rav4 Prime PR appears to be on its way. If not, I'll just keep in mind and document the particular comma bounty, any stipulations comma may place on it, and any other updates about it.

Just removed it since I consider this "locked" to Willem.

I'm not sure what criteria the $5k comma is offering for the Toyota SecOC bounty is. I'll leave it to comma to fill this out and decide what to do with that beyond the placeholder text of "support" I've put in here.

Our criteria is completely unambiguous and exactly the same as every other car port we care about - get it listed on https://comma.ai/vehicles. We're uninterested in anything that doesn't look like a normal car port.

That makes sense. Thanks for the update.


On Windows OS pressing the question mark for the Help system displays 'No documentation located'

Error occurs on all tabs and events that invoke the built-in help content

Resolved by handling the difference between Windows and masOS or Linux systems.  Changed lib/clientIO.js to append a '/' on the tail end of the documentation search key.


Get pub/sub working

Features that need to be implemented for this to happen:

[x] message typesupport and serialization
[ ] rmw_create_publisher, rmw_destroy_publisher

[ ] rmw_publish

[ ] rmw_create_subscriber, rmw_destroy_subscriber
[ ] rmw_wait
[ ] rmw_create_guard_condition, rmw_destroy_guard_condition (possibly optional, but helpful)

[ ] rmw_trigger_guard_condition (optional)

Closing this out to archive the repository.


Setting up dns-sd failed: Address already in use (os error 98)

Due Diligence

[X] I have done my due diligence

What can we help you with?
I'm on Ubuntu 22.04 on x86.  I cannot figure out what the reason is for this error.  Nothing is running on 5353 (netstat and ss both come up clean).  I've tried removing the avahi-daemon package and rebooting with no luck.  I think this may have started after installing KVM and a virtual machine.  This used to work just fine.  I tried updating to the latest version of raspotify.  I've tried changing the discovery port in the config and through librespot command line.  I've seen that this issue may arise if wireguard is installed, but I don't have that installed on this system.  I've tried doing iptables -F to see if it might be a firewall issue.  I haven't been able to figure out where this error even comes from in the code to see if I can trace back what could be going wrong.  I can start avahi and it runs fine on 5353.
Any ideas on what could be causing this are welcome.
Edit: Can confirm it has something to do with libvirt.  I remove libvirt0 and all the dependencies it installed, rebooted, and it works again.
Edit2: Nevermind, it just takes a little time after the reboot before it stops working.  Something is starting later in the boot process that's breaking it.  Even with libvirt0 removed, problem still exists.

This does not sound like a librespot/Raspotify issue. This sounds like a system configuration issue.

I agree that I could likely fix it with some sort of system change, but the error message it throws seems incorrect.  It's difficult to troubleshoot without knowing what is actually wrong with the software.  Disabling discovery and manually entering a user and password in the configuration works, but then I assume only that account can use it.  Avahi has no problem running on that port, so why does librespot?  It seems to me, a change to librespot could prevent this issue and make it more stable, but it's hard to tell without knowing what the issue actually is.  Where does the error come from?  Is there a way to get a little more detail on what it's trying to do?

Librespot uses it's own version of mDNS that is a best effort but not nearly as robust as Avahi in my experience. The best long term solution IMHO is for librespot to just use Avahi on Linux but someone would have to implement that.

Avahi has a DBus interface that we could use pretty easily in theory. I'm pretty familiar with dealing with DBus interfaces in Python and JavaScript but I've never messed with them in Rust. It's on my long todo list but if anyone else has a more immediate need they are more then welcome to give it a shot.

I've never coded in Rust before, but I can try taking a look at it.  I agree that using avahi is likely the best option since most systems come with it already installed from what I can tell.  I'll do some research on their dbus interface and Rust and see how big of a lift it'll be.

Even if it's not currently installed as far as Raspotify as a .deb package is concerned it's simply a matter of making avahi a dependency.


Initialize before loading as dependency

Hi... I am trying to test the agGrid component in my project. I already have a running setup of ocLazyLoad working fine in my project. Typically, I define the modules in a config file and then load that config in my ui-router. But, agGrid documentation wants me to register the library as a angular module before I load it as a dependency.
// get ag-Grid to create an Angular module and register the ag-Grid directive agGrid.initialiseAgGridWithAngular1(angular); // create your module with ag-Grid as a dependency var module = angular.module("example", ["agGrid"]);
How can I do this?

I encounter the same issue. Hope one can help.

Just solve the problem by adding the agGrid.initialiseAgGridWithAngular1(angular) before return $ocLazyLoad.load
,
            resolve: {
                loadPlugin: function ($ocLazyLoad) {
					agGrid.initialiseAgGridWithAngular1(angular);
                    return $ocLazyLoad.load([
                        {
                            name: 'agGrid',
                            files: ['js/plugins/ag-grid/ag-grid.min.js']
                        }
                    ]);
                }
            }


Fix fromHex invalid hex behavior

In NodeJS, the behavior of Buffer.from(x, 'hex') differed slightly on its handling of bad hex parsing.
My fix also increased performance. I tried parsing a hex string '7c'.repeat(5e7) and it went from 2.8 s to ~800ms.
// node
> Buffer.from('abc def01','hex')
<Buffer ab>

// this library
> require('./index.js').Buffer.from('abc def01','hex')
<Buffer ab 0c de f0>

Note: This new implementation also mimics the code for NodeJS hex parser used in the from(x, 'hex') portion.
https://github.com/nodejs/node/blob/v14.18.1/src/string_bytes.cc#L246-L261

This broke both the linting and the tests, I've submitted PRs to fix that: #340, #341
ping @dcousens

With CI passing now, I'm slightly more confident with this going out (see https://github.com/feross/buffer/issues/335)

@dcousens, please look at #343 before tagging a release. This PR (#303) added a massive slowdown.


Removed two hardcoded strings in the body of `describe' function

Hi!
Thank you for accepting my proposal in #28!
This PR should remove the hardcoded strings and i believe should not break the existing API.
I have tested this new feature with an i18n program and seems to works! :)
Moreover added a couple of quite crude tests in the suite: describe.
I have also updated the docstring  of describe  to reflect the changes this PR brings, but i my English is a mess :(
Please consider for merging.
Bye!
C.

On Mon, Jul 27, 2020 at 01:36:51AM -0700, Thomas Schaper wrote:

Merged #29 into master.

Thank you! :)
C.


[spotify-player] Add feature "my playlists"

Extension
https://www.raycast.com/mattisssa/spotify-player
Description
I want a feature to search within my playlists and play the selected one [if possible in 2 modes of regular play or shuffle].
I don't know if Spotify provide this API or not, but if you can search within all the playlists it may be possible to search within user playlists also.
Who will benefit from this feature?
Everyone who uses Spotify and has playlists of his/her own.
So I guess whoever installs this extension will be using this feature.
Anything else?
No response

Can we notify developers more efficiently?
Some of the extensions have some real potential, but this type of feature request and submitting an issue will not work as expected.


Adjust visibility of marker points

#1057

@karimnaaji Can you think of a way to do this without RTTI?

Actually I'm gonna try something - hold on.

What we can do is set a property in the mesh class bool isLabelMesh() or something in those lines, and static_cast on it. A lot of those casts are made in the codebase for this particular purpose, that would be good to remove it!

Yeah, I'll do this with a separate change.
It seems that the only RTTI we use in the core code is for checking style types and we can easily replace that with an enum member.


Mobile Improvements

Is there anything on the roadmap that would improve the use of the forum on a mobile device? The creation and contributing to a discussion is a little clunky at the moment.

We could indeed use some improvements, sadly I have a lot of my roadmap already.
I am open for pull requests.


Performance update for --stats feature

test results

cpu usage reduction from ~35% to ~25% @ 10Mbps, 1024 message size (cpu usage without stats is also ~25%)
cpu usage cost tested to be 1~2% cpu time @100Mbps, 1024 message size (~11k msgs/s)

changes

make --stats logging timer-driver instead of message-driven to reduce calculation burden
--stats mode (without -v or --debug) now updates in-place every 500 ms (non-configurable)
--stats -v or --stats --debug still logs a line of stats every 2000 ms (non-configurable)
when --stats enabled only up to 1000 samples (InstantMaxSamples, non-configurable) will be used for instantaneous calculations.

important note:

when --stats -v turned on it will now log a new line every 2000 ms even if no new messages arrive. this may cause excessive logging if client is saving the the output to file leaving the cli open, even when no pass is active.

cpu usage reduction from ~35% to ~25% @ 10Mbps, 1024 message size (cpu usage without stats is also ~25%)

cpu usage cost tested to be 1~2% cpu time @100Mbps, 1024 message size (~11k msgs/s)

Does this mean 100Mbps has lower CPU usage for logging?

additional 1~2%, sorry for the bad wording. i think CLI was using around 40% cpu at 100mbps / 1024 byte chunk size


srs 5.0.166 gb28181.conf allow_update on cannot be enabled. Is it no longer supported?  可以支持用户调用http raw api控制是否以及何时DVR吗

Note: Please read FAQ before file an issue, see #2716

Description
Please description your issue here

SRS Version: x.x.x

SRS Log:

xxxxxxxxxxxx
xxxxxxxxxxxx
xxxxxxxxxxxx

SRS Config:

xxxxxxxxxxxx
xxxxxxxxxxxx
xxxxxxxxxxxx

Replay
Please describe how to replay the bug?
Step 1: xxxxxx
xxxxxxxxxxxx
xxxxxxxxxxxx
xxxxxxxxxxxx

Step 2: xxxxxx
xxxxxxxxxxxx
xxxxxxxxxxxx
xxxxxxxxxxxx

Step 3: xxxxxx
xxxxxxxxxxxx
xxxxxxxxxxxx
xxxxxxxxxxxx

Expect
Please describe your expectation.
TRANS_BY_GPT3

你的问题已经在FAQ中存在，该Issue会被删除，请在FAQ中搜索。#2716


Show image embed for save command

Summary
Currently when using the /save command, the bot will only reply with a text response.

When an image is saved successfully, the bot should display the image which was saved alongside the "Image Saved." text. This is to make it transparent to everyone who is saving what.

The /save command can now respond with the image saved.


Segfault on linux

Environment
I build and run osu!lazer in my own docker container.
Current behaviour
Starting with commit https://github.com/ppy/osu/commit/b9a8a36e60e633e94042734d2a7dc8b81b74bfe3 (which updates the osu framework to version 2019.1128.1) the container exits with return code 139 (segmentation fault).
Since the only thing changed in the commit is updating the framework version, I decided to open the issue in this repository. I hope this is the right place.
Steps to reproduce
Build the linked docker file with the GIT_COMMIT build argument set to any commit set to any commit after https://github.com/ppy/osu/commit/47d0eb1564fab13184d3ba5ca231d9c1dd8492a8 or without any build argument (uses the latest master commit):
docker build --build-arg GIT_COMMIT=b9a8a36e60e633e94042734d2a7dc8b81b74bfe3 -t osu-lazer .

As I do not have a .NET core environment set up, I cannot test if this also happens outside of the docker container.
The error seems to be introduced between the commits 1067c305162c2e039ea770fcd0c7ef781677497a and 198f01e4e42ad5c34fd186124a6fe7aa170f49bd.

Did you try bisecting that commit range? It shouldn't be too taxing if the error reproduces in visual tests. dmesg output post-segfault would also be nice.

Thank you for your reply.
This is the output of dmesg related to the segfault:
[114810.760505] dotnet[320798]: segfault at 8 ip 00007fbf885f35d9 sp 00007fbfb8ff5160 error 4 in libbass_fx.so[7fbf885e2000+16000]
[114810.760511] Code: 3d 4c 52 20 00 e9 e7 1d ff ff 48 83 ec 08 83 3d 34 52 20 00 00 75 16 48 8b 05 23 52 20 00 be 03 00 00 00 48 8b 3d d7 49 20 00 <ff> 50 08 5e e9 a8 ff ff ff 90 90 90 90 90 90 90 90 90 90 90 90 90

Unfortunately I do not have much experience with .NET, so I don’t really know how to build osu!lazer with a specific commit of osu-framework. I tried to look into the (thankfully few) changes between the two versions and the only commits that add changes that were not reverted again are 21d604837f4abaa33f00c13eb819e074b2957047 and b96cdc54507c3cd161f867ccb705771f9474e538.

Looks like it might be the same thing as ppy/osu#7018, which was closed with #3057. Would you mind trying to dotnet run osu.Framework.Tests from this repository's latest master vs 3bd14c80 and seeing if it resolves the problem?
(Alternatively, see instructions for how to run lazer with another framework version - requires having a clone of both and jq installed)

Thank you very much. Sorry for not seeing that issue. The pull request fixes the issue.


Adding column-type constants

Refer to #985 for initial discussion :)

[x] type constants
[x] column option constants
[ ] table option constants
[ ] update doc to refer to these constants
[ ] verify doc mentions ForeignKey constants as well
[ ] remove duplication of "valid column types" sections (which is currently inconsistent and error prone)

I like it too
Can we merge this @lorenzo ?

@igorsantos07 Can you please fix up the failing travis build so we can merge?

https://github.com/cakephp/phinx/pull/1739


[Feature request] Github discussion support

Thanks for the awesome tool!
As Github rolling out discussion feature to repos(https://github.blog/2020-05-06-new-from-satellite-2020-github-codespaces-github-discussions-securing-code-in-private-repositories-and-more), it would be very nice to also have discussion support by Gitify.

Seems Github discussions appear alongside other notifications (which is fine). Clicking on the discussion link dismissed the notification but does not open the link.

Unfortunately this is a bug in the GitHub notifications API - the url field in the notification payload is never populated for some newer types of Notifications, discussion included. I filed it with the team when I was still an employee there, but there isn't anything that can be done about it on this end; when GitHub fixes it it'll automatically start working here.


Find Component Library / Theme with compatible license

The Cloud Portal should be released under Apache 2 license.
The Angular Component Library and the Theme must be compatible.

Duplicate of https://github.com/appuio/cloud-portal/issues/1


Improper display of rolled dice

While working on #80 I found a bug in the tool tip, expanded view of rolled dice.

In the above case the original formula was 1d6 + 2d6.  Since it was a crit hit it became 1d6 + 6 + 2d6 + 12.  And can see the result is a bit messed up.

This won't be fixed, only update for mess that will be coming (regarding rolling issues) is removing them.
My replacement is now submitted and waits for approval. Meanwhile you can download the module and look at its features from its repository:
https://github.com/Moerill/fvtt-mars-5e
Manifest: https://raw.githubusercontent.com/Moerill/fvtt-mars-5e/master/module.json
(I'm currently going through all rolling related issues, pasting this as information and closing them)


Error: package com.equimaps.capacitor_background_geolocation does not exist

I installed the plugin, run CAP SYNC, but when importing it into MainActivity he doesn't find the plugin.

I would expect "capacitor-community-background-geolocation" to appear in the project pane. I wonder why it doesn't?

Perhaps try running File -> "Sync Project with Gradle settings"?

For me Android studio redlined dependency but after gradle install build ran successfuly but the red lines still remained until next restart. Everything worked like expected. Good readme.

Removing everything and installing again, when trying to synchronize with "Sync Project with Gradle Files" I got the following image error. Note that the plugin is not showing up there with the others in the project directories. In the other image it is possible to see that the capacitor finds the plugin at the time of the build, plays for "capacitor.build.gradle" but it is as if it were not on the project's premises.
capacitor.build.gradle
apply from: "../capacitor-cordova-android-plugins/cordova.variables.gradle"
dependencies {
    implementation project(':capacitor-community-background-geolocation')
    implementation project(':rdlabo-capacitor-facebook-login')
    implementation project(':capacitor-apple-login')
    implementation project(':capacitor-firebase-analytics')
    implementation "com.android.support:support-v4:24.1.1+"
    implementation "com.onesignal:OneSignal:3.15.6"
    implementation "com.squareup.okhttp3:okhttp:3.12.0"
}
apply from: "../../node_modules/cordova-plugin-badge/src/android/badge.gradle"
apply from: "../../node_modules/onesignal-cordova-plugin/build-extras-onesignal.gradle"

if (hasProperty('postBuildExtras')) {
  postBuildExtras()
}

capacitor.settings.gradle
include ':capacitor-android'
project(':capacitor-android').projectDir = new File('../node_modules/@capacitor/android/capacitor')

include ':capacitor-community-background-geolocation'
project(':capacitor-community-background-geolocation').projectDir = new File('../node_modules/@capacitor-community/background-geolocation/android')

include ':rdlabo-capacitor-facebook-login'
project(':rdlabo-capacitor-facebook-login').projectDir = new File('../node_modules/@rdlabo/capacitor-facebook-login/android/@rdlabo/capacitor-facebook-login')

include ':capacitor-apple-login'
project(':capacitor-apple-login').projectDir = new File('../node_modules/capacitor-apple-login/android')

include ':capacitor-firebase-analytics'
project(':capacitor-firebase-analytics').projectDir = new File('../node_modules/capacitor-firebase-analytics/android/capacitor-firebase-analytics')

I have no idea what is causing this, please let me know if you find a solution.

Have you added service into AndroidManifest.xml?
ex.
`

    <service
        android:name="com.equimaps.capacitor_background_geolocation.BackgroundGeolocationService"
        android:enabled="true"
        android:exported="true"
        android:foregroundServiceType="location" />

</application>

`

This looks like an issue with Android Studio to me.

Perhaps try running File -> "Sync Project with Gradle settings"?

This worked for me!

Removing everything and installing again, when trying to synchronize with "Sync Project with Gradle Files" I got the following image error. Note that the plugin is not showing up there with the others in the project directories. In the other image it is possible to see that the capacitor finds the plugin at the time of the build, plays for "capacitor.build.gradle" but it is as if it were not on the project's premises.
OBS: For iOS works fine!
capacitor.build.gradle
apply from: "../capacitor-cordova-android-plugins/cordova.variables.gradle"
dependencies {
    implementation project(':capacitor-community-background-geolocation')
    implementation project(':rdlabo-capacitor-facebook-login')
    implementation project(':capacitor-apple-login')
    implementation project(':capacitor-firebase-analytics')
    implementation "com.android.support:support-v4:24.1.1+"
    implementation "com.onesignal:OneSignal:3.15.6"
    implementation "com.squareup.okhttp3:okhttp:3.12.0"
}
apply from: "../../node_modules/cordova-plugin-badge/src/android/badge.gradle"
apply from: "../../node_modules/onesignal-cordova-plugin/build-extras-onesignal.gradle"

if (hasProperty('postBuildExtras')) {
  postBuildExtras()
}

capacitor.settings.gradle
include ':capacitor-android'
project(':capacitor-android').projectDir = new File('../node_modules/@capacitor/android/capacitor')

include ':capacitor-community-background-geolocation'
project(':capacitor-community-background-geolocation').projectDir = new File('../node_modules/@capacitor-community/background-geolocation/android')

include ':rdlabo-capacitor-facebook-login'
project(':rdlabo-capacitor-facebook-login').projectDir = new File('../node_modules/@rdlabo/capacitor-facebook-login/android/@rdlabo/capacitor-facebook-login')

include ':capacitor-apple-login'
project(':capacitor-apple-login').projectDir = new File('../node_modules/capacitor-apple-login/android')

include ':capacitor-firebase-analytics'
project(':capacitor-firebase-analytics').projectDir = new File('../node_modules/capacitor-firebase-analytics/android/capacitor-firebase-analytics')

I'm getting the exact same issue on version 1.0.2 for capacitor 3

Sorry, but why was this issue closed? I have the same problem building for Android.
My build fails with, "This dependency not met. You can install it with npm install @capacitor-community/background-geolocation", however, the module is clearly found in "src-capacitor/node_modules/@capacitor-community/".
I would love to know what's causing this error.
I installed the native Geolocation capacitor plugin with no issues, but it seems that all the community plugins are broken in capacitor V3...


Update broken Storm links

As seen in https://artifacthub.io/packages/helm/gresearch/storm, links to Storm source are broken. With this PR, links are fixed:

https://github.com/G-Research/charts/src/storm is now https://github.com/G-Research/charts/tree/master/src/storm
all https://github.com/G-Research/charts/storm links are removed

Ok so, i've repackaged storm charts (versions 1.0.9 to 1.0.14) only Chart.yaml files, with sources list updated:

https://github.com/G-Research/charts/src/storm is now https://github.com/G-Research/charts/tree/master/src/storm
all https://github.com/G-Research/charts/storm links are removed

Also, i had to repackage siembol charts (versions 0.1.3 to 0.1.6) doing the same thing.
Finaly, running helm repo index . updated the index.yaml file correctly, so we should be good to go from here i think

Ok so, i've repackaged storm charts (versions 1.0.9 to 1.0.14) only Chart.yaml files, with sources list updated:

https://github.com/G-Research/charts/src/storm is now https://github.com/G-Research/charts/tree/master/src/storm
all https://github.com/G-Research/charts/storm links are removed

Also, i had to repackage siembol charts (versions 0.1.3 to 0.1.6) doing the same thing.
Finaly, running helm repo index . updated the index.yaml file correctly, so we should be good to go from here i think

This looks awesome now! I'm just not sure if we want to re-package the old version, IMHO I would apply this fix to future versions only as it would be wrong to change something which users are already using it... but we can discuss that after holidays :) 🎄

I'm just not sure if we want to re-package the old version, IMHO I would apply this fix to future versions only as it would be wrong to change something which users are already using it... but we can discuss that after holidays :) 🎄
Of course. I was thinking the same 😄

This is great work @pavlovic-ivan!
I agree with @ljubon that we should probably only make this change for the future versions. Retroactively changing released software does not sit right with me somehow 😅

If we are going to update only future versions, then i think that i can't do anything right now. I mean, the PR will have no purpose. And Alex's request to update the links will not be done. I say that because each time helm package . gets executed, it overwrites the contents of the index.yaml file. And inside of that file are the links that artifacthub picks up. So, this might be just a "PoC" then, more than a PR to be accepted. 🤔

As discussed offline, I think the approach would be to bump the version of the storm package and publish that new one. The links will then be right for that latest version on artifacthub, which is the default that people will see.

All right. Please take a look now ☺ @ljubon @jgiannuzzi @mkomatinovic

Clean for me! 🚀

hey @pavlovic-ivan, you could take the opportunity of this change to kill two birds with one stone if you also address https://github.com/G-Research/charts/issues/62 at the same time! I believe this change would also justify bumping the version number to 1.1.0 instead of 1.0.15.

Bumped storm version to 2.3.0 and Chart to 1.1.0. Version 1.0.15 is removed. Please review :)

Awesome, i will create a public PR. Thanks team :)


Prevent linear values from appearing in loops

Linear values defined outside a loop should not be allowed to appear in the body of a loop, as they'd be potentially consumed multiple times.

This is already implemented somehow??? Unit tests: 28f9244ab750dcc3a5b3cf790122042c701564a6 and ac461fb5fcd53824515d2ad241841a6ddff388a2


Update 9934d828-963f-403a-a0da-7a52e0224ef5.md

Probably need to add a link to Twitter

Probably need to add a link to Twitter

@takemycooffee Thanks for the catch!


Added Kusto

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

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

have you setup a command review with the team @oflipman?
cc: @tjprescott

Hi @adewaleo,
Thanks for the response.
I did not set up a command review, and I would like to set it please.
With whom should I set it with?

Feel free to email the team here Azure Python CLI WG<EMAIL_ADDRESS>


Update README.md with information about availability

Update README.md with information about availability of inspiration

Hey, it looks like that link is dead. I just removed the sentence. Thanks though!


Remote Containers: Shell integration cannot be activated due to complex PROMPT_COMMAND: prompt;history -a

Tried opening the C# remote container sample, see ugly warning on every terminal. Ideally we'd not be broken here, but at minimum maybe only show the error once?

Will
Be fixed by #148848

Curious about why that prompt command would be happening for a remote container 🤔. Where is that set?

@meganrogge different containers are based on different Linux distros, it's up to the distro how the shells are setup

looks good


Update html_for_tweet to support extended tweets

Based on the documentation at https://dev.twitter.com/overview/api/upcoming-changes-to-tweets I've added support to Twython.html_for_tweet to support extended tweets (both in compat and extended modes).
A couple of notes on my interpretation of the docs,

the prefix and suffix regions should not be rendered as part of the display text region. Docs indicate that these "must instead be rendered as metadata" and there is an example of how replies (in prefix) can be rendered.

New css classes twython-tweet-prefix and twython-tweet-suffix denote their respective regions and will allow devs to style or hide these regions where required.

I've created some demos (from the sample JSON payloads in twitterdev/tweet-updates + custom css) to demonstrate how the extended tweets can look like.
http://codepen.io/anon/pen/vXyBLW?editors=1000

Coverage increased (+0.5%) to 56.585% when pulling c57c4bfc3488c0905de49dbcfdd06a121d55f4b8 on ping:extended-tweet into 975095d8d20cb9966d0226b32a70b7a41cef2fb4 on ryanmcgrath:master.

Hm. I concur with the code changes. As far as how it's displayed, do you think this is a good solution?
@philgyford opinions?
I'm perfectly fine with the presentation.

I think it looks fine, well done @ping.
For something that seems so simple, tweets sure are getting complicated!


Prepare release candidate v0.1.0-beta.9

This release candidate fixes a bug where editing item titles was no longer possible, from v0.1.0-beta.8.

Tested the item CRUD functionality, resolving secret references and also checked that the bugs we have recently fixed are indeed fixed. Everything was in order ✅


input fields widening mobile webpage

Hello,
I've noticed that the labels on input fields often widen a mobile webpage, it makes the webpage horizontally scrollable. For as far as I know, this only happens when the input field has a prefix icon, pushing it right far enough to make it pop out of the screen.
I also have a quick fix for this:
label {     max-width:240px;   }
Works for me, but perhaps a real fix can be implemented some day?
Thanks.

Have you tried the latest master commit? Im pretty sure this was fixed


fix: change fg color for non-current statusline

If current and non-current statusline highlight groups are the same, neovim will use "^^^" in the status line of the current window. Changing the foreground to a muted grey will prevent this from happening.
Closes #22

Thanks man! Can you add a small comment into the Changelog about this? Cheers


Update Site settings “info”

Automatically generated by Netlify CMS

👷 Deploy Preview for fervent-turing-932f6f processing.
🔨 Explore the source changes: c1ac9582a598f33045ddfa106e76cada8b0c95c7
🔍 Inspect the deploy log: https://app.netlify.com/sites/fervent-turing-932f6f/deploys/621db4f2fdc7c400088d3e7e


Read more button appear after dequeue in UItableView, initially it doesn't show.

Read more button appear after dequeue in UItableView, initially it doesn't show.

You need to call layoutIfNeeded() on the cell it self, before setting up the ExpandableLabel.
(Had the same issue myself and then I looked at the demo code).

Another solution (that eventually helped me as well):
The library is using the label’s width to calculate where the “Show more” text would be placed.
Since after dequeuing for the first time the bounds are not calculated properly, I ended up calculating the width manually and setting up the label’s width programticlly (according to the constraints I set up) before assigning the text - kinda hacky, and not optimal - but it works perfectly.

@zaltzy Any other work arounds? I am having the same issue and the problem is solved after reloaddata or after scrolling a couple of times.

@mavris did you find a workaround?

i am facing the same issue in my app. First cell of tableview not show "Read more" but i scroll little bit and cell is deque then read more is show. Any workaround?

@inzamamxiq I doubt that you'll find much luck here, there is no activity on this issue

@t0milee  Just solve this issue by reload tableview on main thread with 0.001 delay. it solves.


[SPARK-49637] Changed error message for INVALID_FRACTION_OF_SECOND

What changes were proposed in this pull request?

In this PR, the error message for INVALID_FRACTION_OF_SECOND is changed, such that it no longer suggests turning off ANSI flag. Now, the error suggests using try_ variants of functions for making timestamps. This PR will is done in conjunction with https://github.com/apache/spark/pull/48624, where the try_ variants of these functions are implemented.
Why are the changes needed?

These changes are needed as part of the effort to move to ANSI by default.
Does this PR introduce any user-facing change?

Yes, the error message is changed.
How was this patch tested?

Tests not needed.
Was this patch authored or co-authored using generative AI tooling?

No

If CI passes, hopefully it can be merged today


Realize Reproducible Builds by stabilize name of the KoinMeta file

Current implementation decides the name of KoinMeta file randomly, and it makes the build not reproducible. In other words, kspKotlin task generates different output even when input is same.
By this behaviour, Gradle tasks depending on the generated KoinMeta file like compileKotlin are executed even though no code has been changed. I will share screenshot of Gradle build scan for reference:

I want to suggest this change to stabilize name of the KoinMeta file. By this change, koin-ksp-compiler will compute digest of generated file, then use it to name the KoinMeta file. It will make the kspKotlin task reproducible, and make successor tasks able to use build cache.

note that this change includes the fix suggested by #195

Thank you!


Blog fixed

Yo! I forked your repo and fixed the blog post parsing, that is currently broken because of the new SL portal design...
I used some standard python regex and JSON.
I was trying to keep the code backwards compatible and change as little as possible, but had to remove the recent_posts and recent_news parts (also from readme).
I hope you will like it and you'll be able to merge it and publish the update to PyPi too...
This is my first time forking someone elses repo and initiating a pull request.. I followed this guide:
https://akrabat.com/the-beginners-guide-to-contributing-to-a-github-project/
Best regards
Tibor

Thanks for the contribution, any help is much appreciated! ♥ I will review your contribution ASAP and hopefully merge it to the master.


Fix for async code running in background

This fix applies an "await" to two calls to the "start" function within
the "reverse_game.js" file which were causing a double output while
playing the game. Since these functions were run in the background and
were not awaited, their output doubled up to the console at the same
time, making it appear that the start function logged twice, when it was
a function being called twice without being awaited.

Thank you @Dangeranger!

Thanks @Dangeranger!


AbstractFunctionCompiler cleanup

removed Function/Supplier/ConsumerFactories by modifying SOURCE_CODE_TEMPLATE
removed Example main from src/main/java/org.springframework.cloud.function.compiler

rebased and merged as https://github.com/spring-cloud/spring-cloud-function/commit/11b8654e099131b81ef3a4578e4d041407f1f6e2


Created auto-comment.yml

@cgokmen Review

Hi, we do not require such a feature currently and do not want to expose our self-hosted runners to the myriad of custom actions used here. Also, we have recently been receiving a lot of these suspicious tiny contributions, so we are preemptively rejecting all of them. Thanks.


Updated release Workflow to use diff-targets

Current dependencies on/for this PR:

main

PR #469   👈

This comment was auto-generated by Graphite.


Improve the routing key DSL

You mentioned supporting something like (hash(fields) mod n) in another issue.  This feature is usually called bucketing and is often implemented outside of partitioning (Hive, Spark, ...). I don't think we have to support this now. I'd be happy with simply supporting multiple fields as a partition key.

I believe this has been solved by #2553.


[Question] How to escape {{ inside the K8s resource spec

I use DataDog for the logs of our system, and I also create some alerts based on the logs.
For example, I have an alert when the log payment failure is found in the past 5m.
DataDog alert can be created as a K8s resource using DatadogMonitor controller (more info here), something like this:
apiVersion: k8s.datadoghq.com/v1alpha1
kind: DatadogMonitor
metadata:
  name: {{.Chart.Name}}-paymen-failure
spec:
  name: "[{{ .Values.environment }}][{{ .Chart.Name }}] Payment failure"
  type: "log alert"
  query: "logs(\"service:payment-service env:{{.Values.environment}} status:error Payment failure\").index(\"*\").rollup(\"count\").last(\"1h\") > 0"
  message: |
    Payment failure occurred. Please have a look.
    @slack-payment-alerts
  {{ end }}
  tags:
    - "env:{{.Values.environment}}"
    - "service:{{.Chart.Name}}"
{{ end }}

Let's focus on the message.
It contains the alert message and the Slack channel to be notified.
 Please have a look.
@slack-payment-alerts
{{/is_alert}}

Please note that {{#is_alert}} and {{/is_alert}} is DataDog syntax, not variables from helm.
However, I do not know how to escape {{# characters and add {{#is_alert}} to the message value.
Helm failed to parse the special characters like { or #.
I tried a couple of ways, but nothing helped, as mentioned here.
How can I do it?
Helm version:
> helm version
version.BuildInfo{Version:"v3.10.3", GitCommit:"835b7334cfe2e5e27870ab3ed4135f136eecc704", GitTreeState:"clean", GoVersion:"go1.18.9"}

apiVersion: v1
kind: ConfigMap
metadata:
  name: scratch_349
data:
  test: |
    {{ "{{#is_alert}}" }}
    Payment failure occurred. Please have a look.
    @slack-payment-alerts
    {{ "{{/is_alert}}" }}
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: scratch_349
data:
  test: |
    {{#is_alert}}
    Payment failure occurred. Please have a look.
    @slack-payment-alerts
    {{/is_alert}}


Make Prefixes case-insensitive

What are the changes:

Prefix.java: prefix String is made to lowercase
ArgumentTokenizer#findPrefixPosition: change the whole argsString to lowercase to compare
UG note

Some considerations, but can ignore if you feel that it's not really good

sounds good, thanks for your suggestion

Can add in some test case to ensure that it works? For example test for edit and add with prefixes in upper case / mixed case

Sure, I am adding now


Fix coalesce, struct and named_strct expr_fn function to take multiple arguments

Which issue does this PR close?
Closes https://github.com/apache/datafusion/issues/10320
Rationale for this change
There was a regression in the coalesce function's signature due to lack of testing
What changes are included in this PR?

Fix signature
Add test coverage

Are these changes tested?
Yes, by existing CI and new tests

Are there any user-facing changes?

Thanks @jayzhan211


Fix github and extension name in the README

The links in the README are pointing at the pre-rename repo (?)
s/kantlove/mt40/g
s/vscode-todo-parser/minhthai.vscode-todo-parser/g

That is true. Thanks for the PR!


Remove (no stack) string for unhandledReasons

The string in the console makes it hard to debug since the object will not be printed anymore.

Note, I deal with this issue with a different approach in https://github.com/kriskowal/q/pull/817


Installation folder is not found when executed thru GithubAction

Describe the bug
Installation folder is not found when executed thru GithubAction
To Reproduce
Steps to reproduce the behavior:

create a GitHub repo with Wordpress in the root folder
create file .github/workflows/wp-vulnerability-check.yml (attached)
trigger action

Expected behavior
The vulnerability scan should be executed

on: [push]
name: WordPress Vulnerability Check
jobs:
  wp_vulnerability_check_github_action:
    runs-on: ubuntu-latest
    name: Checks
    steps:
    - name: Vulnerability Check
      id: check
      uses: umutphp/wp-vulnerability-check-github-action@v13
      with:
        path: '.'
        token: '{omitt3ed}'
Loading

Hi @dschmidtadv ,
Many thanks for the issue :). We will try to fix and update you asap.


[flink] Add query service test with deletion vectors options

Purpose
Test query service with deletion vectors options, its okay for table with option 'deletion-vectors.enabled' = 'true'

Linked issue: close #4265

Tests

Add test testQueryServiceWithDeletionVectors
API and Format

No
Documentation

No

In my test,CALL sys.query_service('default.DIM', 1) can be submitted to the flink cluster,but it will always restart due to exceptions.I don’t know if you have actually tested it on the flink cluster.
java.lang.IllegalStateException: SortedRun is not sorted and may contain overlapping key intervals. This is a bug.
at org.apache.paimon.utils.Preconditions.checkState(Preconditions.java:182)
at org.apache.paimon.mergetree.SortedRun.validate(SortedRun.java:90)
at org.apache.paimon.mergetree.SortedRun.fromUnsorted(SortedRun.java:67)
at org.apache.paimon.mergetree.Levels.updateLevel(Levels.java:190)

Hi @herefree ,I test it in local standalone cluster,  it does throw this exception. Due to add option 'deletion-vectors.enabled' = 'true', the file level is upgrade from level-0 to level-5 duration compaction. So duration process element, the file was added to sortRun file again which lead to file duplicate and that cause validate sortRun failed.
Add I find another bug duration test.
I only insert one record, but query service show process 2 records.
And I will raise another issue to follow this.

Hi @herefree ,I test it in local standalone cluster, it does throw this exception. Due to add option 'deletion-vectors.enabled' = 'true', the file level is upgrade from level-0 to level-5 duration compaction. So duration process element, the file was added to sortRun file again which lead to file duplicate and that cause validate sortRun failed. cc @JingsongLi
Add I find another bug duration test. I only insert one record, but query service show process 2 records. And I will raise another issue to follow this.

Thanks your reply, look forward to your repair~


Got some errors when trying to install as follows. This is from production but I also get similar errors when I try to install into a sandbox. Any ideas?

......
Status: InProgress
Status: Completed
Deployment Complete
Failures:
classes/WelcomeControllerTest.cls(36,38):Dependent class is invalid and needs recompilation:
WelcomeController: line 54, column 4: Dependent class is invalid and needs recompilation:
Class.RollupService.rollup: line 174, column 14
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/WelcomeController.cls(54,4):Dependent class is invalid and needs recompilation:
Class.RollupService.rollup: line 174, column 14
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupSummaryEnhancedController.cls(153,3):Dependent class is invalid and needs recompilation:
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupSummariesTest.cls(41,2):Dependent class is invalid and needs recompilation:
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupSummariesSelector.cls(67,45):Dependent class is invalid and needs recompilation:
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupSummaries.cls(140,106):Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupServiceTest3.cls(44,2):Dependent class is invalid and needs recompilation:
Class.RollupService.rollup: line 174, column 14
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupServiceTest2.cls(44,2):Dependent class is invalid and needs recompilation:
Class.RollupService.rollup: line 174, column 14
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupServiceTest.cls(89,3):Dependent class is invalid and needs recompilation:
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupService.cls(174,14):Dependent class is invalid and needs recompilation:
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupActionCalculate.cls(42,60):Dependent class is invalid and needs recompilation:
Class.RollupService.rollup: line 174, column 14
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupActionCalculateTest.cls(65,62):Dependent class is invalid and needs recompilation:
Class.RollupActionCalculate.RollupToCalculate.toServiceRollupToCalculate: line 42, column 60
Class.RollupService.rollup: line 174, column 14
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupCalculateController.cls(43,3):Dependent class is invalid and needs recompilation:
Class.RollupService.rollup: line 174, column 14
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupCalculateJob.cls(41,2):Dependent class is invalid and needs recompilation:
Class.RollupService.rollup: line 174, column 14
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupController.cls(266,2):Dependent class is invalid and needs recompilation:
Class.RollupService.rollup: line 174, column 14
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupControllerTest.cls(68,37):Dependent class is invalid and needs recompilation:
Class.RollupController.init: line 266, column 2
Class.RollupService.rollup: line 174, column 14
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
classes/RollupJob.cls(34,2):Dependent class is invalid and needs recompilation:
Class.RollupService.rollup: line 174, column 14
RollupSummaries: line 140, column 106: Variable does not exist: LookupRollupSummary__c.FieldToOrderBy__c
triggers/RollupServiceTest3Trigger.trigger(12,6):Variable does not exist: RollupService
triggers/RollupServiceTestTrigger.trigger(12,6):Variable does not exist: RollupService
triggers/RollupSummariesTrigger.trigger(30,31):Variable does not exist: RollupSummaries.class
triggers/RollupServiceTest2Trigger.trigger(11,5):Variable does not exist: RollupService
permissionsets/LookupRollupSummariesFull.permissionset(LookupRollupSummariesFull):invalid parameter value
permissionsets/LookupRollupSummariesReadOnly.permissionset(LookupRollupSummariesReadOnly):invalid parameter value
pages/managetrigger.page(managetrigger):Apex class 'RollupController' does not exist
pages/rollupcalculate.page(rollupcalculate):Apex class 'RollupCalculateController' does not exist
pages/rollupsummaryenhanced.page(rollupsummaryenhanced):Apex class 'RollupSummaryEnhancedController' does not exist
pages/welcome.page(welcome):Apex class 'WelcomeController' does not exist

Oops sorry about this, will sort this out, in the meantime are you sure you want to deploy the code unmanaged? You can use the package install links to install the tool as a package, which is the recommended route for sandbox and production.

Yes. Managed would be preferred. Where are the package install links?
Should I wait until you resolve the load issues, or May that not get the error?
Thanks for your help on this.

I found the managed package link, used it and it installed fine as a managed package. Yay!
So I am good to go now and starting to use the tool.
Thanks for your help and for creating this tool.
Guy

Your very welcome, i'll sort this issue in due course as well...

Fixed


Installing SAP HANA, express edition with Docker

Tutorial URL: https://developers.sap.com/tutorials/hxe-ua-install-using-docker.html
Please specify the step you are referring to
Step 11: (Optional) Log Into System or Tenant Database

The JDBC URLs have the wrong format, they should look like this:
jdbc:sap://<ip_address>:39017/?databaseName=<database_name>

(notice the ? in front of databaseName)
And a link to the JDBC Connection Properties would also be nice
https://help.sap.com/viewer/0eec0d68141541d1b07893a39944924e/2.0.03/en-US/109397c2206a4ab2a5386d494f4cf75e.html

Thanks for these corrections. The JDBC URLs were corrected in hxe-ua-install-using-docker and hxe-ua-install-using-docker-xsa. A link was added to the JDBC connection properties topic.


added tests

git town config --setup will now still prompt you to enter in values for configuration parameters if values are already set. For main-branch-name it'll show you the current value (if there is one) and if you press enter it'll just use the current value. For perennial-branch-name, it'll show you the current value (if there is one) and if you press enter, it'll change it to be none.

:ship:


[Bug] Scenario "Holy Mansion" Labeled as Incorrect Language

The scenario "Holy Mansion" is labeled as English, but the actual text is in another language.  I don't know if this is intentional for some reason, but I assume it is an error of some sort.
If this wasn't the right place to post this, I apologize.  But this scenario has been sitting in the English section for a LONG time, and I thought it would be helpful to point this out since it appears nobody is playing it since it's not in the correct language category.

It's something that the author must change. The scenario is actually in Italian. Let's see if @flopez86 can read this and fix it.

https://github.com/flopez86/HolyMansionScenario/issues/1#issuecomment-695986183

I will create a Valkyrie package fixing this issue, and at the same time, adding the Spanish translation. In a few days I will send it to @flopez86

Package sent to author. It should solve the problem with the wrong language flag. Now it shall appear in Italian and Spanish, but not in English.

Fixed, @strategywizard . You can close this issue now.


Move out Authorization sections into 1 single place in Common?

I would suggest to move out the different Authorization sections from within (https binding) Catalog, Negotiation and Transfer into a singel place in Common.
Any thoughts?

https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/catalog/catalog.binding.https.md#31-authorization


fix/rename segmentation namespace

Description

rename segmentation directory
update topic namespace /perception/object_segmentation/pointcloud -> /perception/obstacle_segmentation/pointcloud
simulation stack is fixed in https://github.com/tier4/AutowareArchitectureProposal.iv/pull/739

Review Procedure

Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Read pull request guidelines
[x] Code follows coding guidelines
[x] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the guidelines.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

/perception/object_segmentation/pointcloud remains.
https://github.com/tier4/AutowareArchitectureProposal.iv/blob/14bff6670fd205568ece869fcc244c239962826e/simulator/util/dummy_perception_publisher/launch/dummy_perception_publisher.launch.xml

/perception/object_segmentation/pointcloud remains.
https://github.com/tier4/AutowareArchitectureProposal.iv/blob/14bff6670fd205568ece869fcc244c239962826e/simulator/util/dummy_perception_publisher/launch/dummy_perception_publisher.launch.xml

@tkimura4 Thank you for your review :+1: and, dummy_perception_publisher is fixed in the other PR (https://github.com/tier4/AutowareArchitectureProposal.iv/pull/739)

https://github.com/tier4/AutowareArchitectureProposal_launcher/pull/139
と一緒にlogging_simualtor.launch.xmlでチェック.


[events] Move events to JavalinConfig & convert EventListener to EventConfig

Resolves #1936

Changes didn't affect tests, the API from user perspective should be the same. Some types are different, but it doesn't change the way users should use them.

Looks good !


Finds command error on no specified option

Codecov Report

Merging #168 (08fcbe8) into master (5aa6b68) will increase coverage by 3.08%.
The diff coverage is 92.09%.

@@             Coverage Diff              @@
##             master     #168      +/-   ##
============================================
+ Coverage     52.87%   55.96%   +3.08%
- Complexity      529      604      +75
============================================
  Files           106      106
  Lines          2188     2312     +124
  Branches        259      274      +15
============================================
+ Hits           1157     1294     +137
+ Misses          970      957      -13
  Partials         61       61

Impacted Files
Coverage Δ

src/main/java/manageezpz/MainApp.java
0.00% <0.00%> (ø)

...c/main/java/manageezpz/logic/parser/CliSyntax.java
93.33% <ø> (-0.42%)
:arrow_down:

src/main/java/manageezpz/model/task/Task.java
76.92% <ø> (+11.13%)
:arrow_up:

...ain/java/manageezpz/model/util/SampleDataUtil.java
0.00% <ø> (ø)

...ava/manageezpz/logic/parser/AddressBookParser.java
55.17% <50.00%> (-4.09%)
:arrow_down:

...a/manageezpz/model/task/TaskMultiplePredicate.java
83.01% <78.57%> (+33.01%)
:arrow_up:

...nageezpz/model/person/PersonMultiplePredicate.java
86.20% <86.20%> (ø)

...manageezpz/logic/parser/FindTaskCommandParser.java
89.47% <90.62%> (-3.21%)
:arrow_down:

...geezpz/logic/parser/FindEmployeeCommandParser.java
98.07% <98.07%> (ø)

...manageezpz/logic/commands/FindEmployeeCommand.java
100.00% <100.00%> (ø)

... and 17 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 58ef833...08fcbe8. Read the comment docs.


New tip regarding command line history

The following PR adds a new tip about command-line history.

Thanks for the contribution 🙂. This repo/module isn't quite ready yet, and I haven't publicized it yet, so I'm surprised (and happy and impressed) that you found it and made a PR already 🎉


Akka HTTP: Add option to extract arbitrary data from request and pass to handler

This PR allows the user to extract arbitrary data from an Akka HTTP request, and have it passed to the route handler. It's inspired by the tracing code, and could theoretically replace it entirely since it's a more general version of the same thing.
There are a few examples of where this would be helpful already. I had a look for relevant open issues:

@eli-jordan asking for this feature directly: https://github.com/twilio/guardrail/issues/381
Me, wanting to inject a Directive0: https://github.com/twilio/guardrail/issues/645. I realized later that while a Directive0 would be useful, I'm already extracting an Authorization header by means of a header parameter in the OpenAPI spec. This PR would solve both issues for me.
@edmondo1984 wants to access Authorization data in the handler: https://github.com/twilio/guardrail/issues/117
Providing a better place to inject the oauth directive discussed in https://github.com/twilio/guardrail/issues/90, so authorization can now be checked after path matching. Wondering if this would address @Stinger911's comment about it being "enough".
@willgu-gdm wants to extract the whole request, which would now be possible: https://github.com/twilio/guardrail/issues/616
@ssboisen could extract the body: https://github.com/twilio/guardrail/issues/552#issuecomment-634460237
@kimxogus would have a workaround for extracting cookies: https://github.com/twilio/guardrail/issues/298

Because of the composability of Akka Directives, you can really do a lot of different things with this! Some of those things may warrant a specific solution as well, but until those more specific solutions are developed, this may be a good escape hatch.
Notes:

Am very new to Scala Meta, so let me know if I did things strangely
I'm not very familiar with Http4s, so didn't want to go too far down the road of implementing it there. Plus, I think there's already some similar functionality with mapRoute there?
I chose to make this feature entirely optional, like tracing. But, I could also see it being always-on with a default no-op customExtract (again similar to mapRoute which has a no-op default, looks like). Am happy to make that happen if desired.
I did add one test, but can add more if needed.
I didn't look into adding the new option to any of the build plugins yet, but can do if this seems like a good idea

Thanks for having a look!
Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[x] I acknowledge that all my contributions will be made under the project's license.

Codecov Report

Merging #747 into master will increase coverage by 0.04%.
The diff coverage is 84.61%.

@@            Coverage Diff             @@
##           master     #747      +/-   ##
==========================================
+ Coverage   81.20%   81.24%   +0.04%
==========================================
  Files          78       78
  Lines        5197     5251      +54
  Branches      139      136       -3
==========================================
+ Hits         4220     4266      +46
- Misses        977      985       +8

Impacted Files
Coverage Δ

...il/generators/Scala/EndpointsServerGenerator.scala
0.00% <0.00%> (ø)

.../guardrail/protocol/terms/server/ServerTerms.scala
0.00% <0.00%> (ø)

...il/generators/Java/DropwizardServerGenerator.scala
96.29% <66.66%> (-1.73%)
:arrow_down:

...ail/generators/Java/SpringMvcServerGenerator.scala
90.67% <66.66%> (-1.22%)
:arrow_down:

...drail/generators/Scala/Http4sServerGenerator.scala
93.50% <66.66%> (-0.86%)
:arrow_down:

.../src/main/scala/com/twilio/guardrail/Context.scala
100.00% <100.00%> (ø)

...n/scala/com/twilio/guardrail/ServerGenerator.scala
100.00% <100.00%> (ø)

...ail/generators/Scala/AkkaHttpServerGenerator.scala
92.72% <100.00%> (+0.93%)
:arrow_up:

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 55447a0...4aa0c3d. Read the comment docs.

Thanks @kelnos! I can definitely write some docs. Seems like a new section on https://guardrail.dev/scala/akka-http/generating-a-server might be the best place for it? Probably a runtime test would help too.
Here's a short example of how it works with customExtraction = true, just extracting the whole Akka HttpRequest:
// Guardrail-generated code
trait UserHandler[E] {
  def createUser(respond: UserResource.CreateUserResponse.type)(body: definitions.User)(extracted: E): scala.concurrent.Future[UserResource.CreateUserResponse]
}

object UserResource {
  def routes[E](handler: UserHandler[E], customExtract: String => Directive1[E])(implicit mat: akka.stream.Materializer): Route = // .... for details see the test
}

// user-written code
class UserApi extends UserHandler[HttpRequest] {
  override def createUser(respond: UserResource.CreateUserResponse.type)(body: definitions.User)(req: HttpRequest): scala.concurrent.Future[UserResource.CreateUserResponse] = {
    println(s"here's the whole Akka request: $req")
    ???
  }
}

val extractReq = (operationId: String) => extractRequest // Directive from Akka HTTP

val userRoutes = UserResource.routes(new UserApi, extractReq)

val binding = Http().bindAndHandle(userRoutes, "localhost", 1234).futureValue

I didn't compile this, but you get the idea hopefully. And am realizing the handler should be contravariant, so that you could extract a subclass of what the handler expects. Will change that as well.

Oh wow, that's really cool.  Is there a way to extract multiple things?  Like say I wanted to provide a custom extractor that composes two akka-http directives, and ends up returning a Directive2?
Yes, generating-a-server is probably a good place for docs.
I'm not sure overall about the proposed mechanism for enabling/disabling this; would like @blast-hardcheese to weigh in on that.

Is there a way to extract multiple things?

You could do this by extracting a tuple. Akka already using this mechanism internally (there's no such thing as a Directive2, only Directive1[Tuple2[A, B]]. They do a bit of magic to make the extraction nicer, see https://doc.akka.io/docs/akka-http/current/routing-dsl/directives/index.html#automatic-tuple-extraction-flattening-.
We don't have any magic to make the handler flatten the tuple into separate params, but I think that's OK.

I'm not sure overall about the proposed mechanism for enabling/disabling this

I'm not sure either. It's not a thing that everyone will use, certainly, and it does add a bit of noise to the generated handler trait if you're not using it. Hence the initial thought of making it optional via the build plugin. But, definitely open to other ideas.

OK, I rebased on latest master, made the handler contravariant, cleaned up the type param declaration, and added some docs.
I looked at adding a runtime test, but it looks like that might require getting further into how this feature will be enabled, so held off for now.

Just FYI we are awaiting this with great anticipation :)
Anything we can do to get this moving? We need it for supporting POST of application/zip

@anagrius Hey, very sorry to keep you all waiting on this! It has been on my list, but I recognize that it has taken some time.
I've blocked off some time on my calendar to review the open question here; if I don't have an answer for you tomorrow, I'll at least provide an update around where I got.
Thank you for your contribution so far!

I'm not very familiar with Http4s [...] I think there's already some similar functionality with mapRoute there?
This is actually a good call-out; mapRoute may warrant being added to akka-http as well, in the form of (String, HttpRequest, Future[HttpResponse]) => Future[HttpResponse], though anything that could be done with that would be possible via customExtraction, so this is more of a call-out in case others recognize the need for their use case.

I chose to make this feature entirely optional [but] I could also see it being always-on with a default no-op [...].
I used a strategy sort of like this to control when the user desired hashing file upload contents in-flight:

        val Unmarshalfile2Part = handler.uploadFileUnmarshalToFile[Option](None, handler.uploadFileMapFileField(_, _, _))...
        val Unmarshalfile3Part = handler.uploadFileUnmarshalToFile[Id]("SHA-256", handler.uploadFileMapFileField(_, _, _))...

which removed the possibility of losing the desired hashing strategy ("SHA-256") along the way and ending up with a None.get. Under the hood this uses Functor[Option] and Functor[Id] to do the work, which could be employed here as well to have this sort of "enabled by default but stubbed out" behaviour, kind of like:
def addPet(respond: PetResource.AddPetResponse.type)(): Unit => scala.concurrent.Future[PetResource.AddPetResponse]
def addPet(respond: PetResource.AddPetResponse.type)(): RemoteAddress => scala.concurrent.Future[PetResource.AddPetResponse]

or something, but to the best of my knowledge there's no way to implement this without burdening the user with additional syntactic noise.
To that end, I think enabling it via simple CLI flag and options in the build tooling makes the most sense, at the expense of broadening the different varieties of generated Handler interfaces, increasing the cognitive burden when configuring the plugin.

also rebased to resolve merge conflicts

also addressed some build warts from the recent Scala Dropwizard addition.

To that end, I think enabling it via simple CLI flag and options in the build tooling makes the most sense, at the expense of broadening the different varieties of generated Handler interfaces, increasing the cognitive burden when configuring the plugin.

Agreed, thanks for plumbing that all the way through.

Sounds good, and thanks!
On Mon., Sep. 7, 2020, 10:49 Devon Stewart<EMAIL_ADDRESS>wrote:

@blast-hardcheese commented on this pull request.
In modules/microsite/docs/scala/akka-http/generating-a-server.md
https://github.com/twilio/guardrail/pull/747#discussion_r484475675:

For example, to extract an X-User-Id header value from an incoming request, your code might look like this:
-class UserApi extends UserHandler[String] {
-  override def createUser(respond: UserResource.CreateUserResponse.type)(body: definitions.User)(userIdHeader: String): scala.concurrent.Future[UserResource.CreateUserResponse] = {
-    println(s"The supplied X-User-Id header is: $userIdHeader")
+class UserApi extends UserHandler[Tuple1[String]] {
+  override def createUser(respond: UserResource.CreateUserResponse.type)(body: definitions.User)(extracted: Tuple1[String]): scala.concurrent.Future[UserResource.CreateUserResponse] = {
+    println(s"The supplied X-User-Id header is: ${extracted._1}")

I'll revert back to your previous strategy, merge, and release.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/twilio/guardrail/pull/747#discussion_r484475675>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHHKSVBWST3HOH34HTCDHTSETXHJANCNFSM4PY7EHUA>
.

Tried this out today in our codebase, and it's working nicely! Thanks again for getting it merged.

Great to hear, and thank you for both your contribution and patience through the process! If you're comfortable being listed on our Adopters list, would you mind opening a PR for that?

@blast-hardcheese I would very much like to, but will have to decline for now. If anything changes I'll open up a PR.

Not a problem, thank you again for the contribution 🙂


WIP: COMP: Include Halide v18.0.0 in build system

@allemangD
Closes #2
A few questions/notes regarding the implementation:

Should the logic be moved from the main CMakeList to a GetHalide.cmake (or another name) file?
When linking against Halide zlib is required, should we also build/include this in the build system? Or require the user to have this installed already?
Everything is working up until I am linking against Halide::Generator, which throws errors since it cannot find llvm, what are your thoughts here?

[ 70%] Built target HalideFilters
[ 74%] Linking CXX executable /root/ITK-build/bin/HalideFiltersTestDriver
/usr/bin/ld: cannot find -lLLVMAnalysis: No such file or directory
/usr/bin/ld: cannot find -lLLVMBitReader: No such file or directory
/usr/bin/ld: cannot find -lLLVMBitWriter: No such file or directory
/usr/bin/ld: cannot find -lLLVMPasses: No such file or directory
/usr/bin/ld: cannot find -lLLVMObject: No such file or directory
/usr/bin/ld: cannot find -lLLVMOrcShared: No such file or directory
/usr/bin/ld: cannot find -lLLVMOrcTargetProcess: No such file or directory
/usr/bin/ld: cannot find -lLLVMSupport: No such file or directory
/usr/bin/ld: cannot find -lLLVMTargetParser: No such file or directory

So far I have tested this on Linux and Windows.

I'm not quite sure why the CI runs are failing... I think it may just be that I had not closed the changes in my initial review, so they were not actually re-run? I just approved those changes and manually re-ran the actions to see what happens.

CI seems inconsistent; I tested locally with an equivalent dashboard.cmake with no errors, and indeed the latest build-test-cxx ubuntu-22.04 succeeded without issue. I'll go ahead and merge/close this and we can resolve the CI inconsistency separately, in parallel with work to proceed with implementation.

Normally I would rebase-and-merge, but I'll squash to clean up the "WIP" commits.


Returning sub-map with select, not value

Hello! Been a while.
I'm writing some ETL code which basically filters a map by another map. Specter seems right for this. For example:
{:a
  {:b {:c 4 :d 5}
   :e {:f 6 :g 7}
   :h {:i 8 :j 9} }}

filter by [ [:a :b :c] [:a :e :f] ]

 ---> {:a
        {:b {:c 4}}
         :e {:f 6}}

I think the main thing I'm not understanding is getting select to return a sub-map, instead of the value. For instance (select [ALL :a :b :c]) returns "4" instead of {:a {:b {:c 4}}.
What concept am I missing?

Here's one way to write your function:
(defn filter-map [paths input]
 (reduce
   (fn [m p] (setval p (select-one p input) m))
   {}
   paths
   ))

(filter-map [[:a :b :c] [:a :e :f]]
 {:a
  {:b {:c 4 :d 5}
   :e {:f 6 :g 7}
   :h {:i 8 :j 9} }})
=>  {:a {:b {:c 4}, :e {:f 6}}}

Interesting -- I didn't think of building a new map instead of filtering the original. Thanks!


BAW compression + encryption(coming)

Here's first approach into compression. Works fine etc., but times of loadings compressed model are much worse then the raw one (3-4 times longer) (tested ofc on release :D with this big 18MB tallguy model). However I managed to shorten this time by ~10-15% by messing with lzma properties (lzma gives more flexibility, but unfortunately is much less documented - actually no docs at all). Also a thing to do is (if possible) get to know some kind of upper bound of lzma compression size (similarly as in lz4 compression) so that we can decide whether we can compress to [preallocated] memory on stack.

Ok, so a few remarks:
A) Interestingly enough, supposedly, lzma has roughly the same decompression speed as lz4
B) I suggest hashing of post-encryption and post-compression data, has is there only to check blob was not corrupted by the disk i/o errors

If the loading is slow, then maybe we should up the thresholds for compression blobLz4EncrThresh(4096), blobLzmaEncrThresh(32768) to something higher?
I also think that compression level parameter and algo should be exposed in writeprops.
Also can you check if the hash function in lz4/xxHash is the same one as in coreutil.h?
Finally I don't think you should worry about getting an upper bound on compression size, as we already threshold to compress stuff larger than 4k and 32k and the max stack we can take without crashing people's programs is 16k.
So it's safe to assume to always allocate on the heap and not worry about doing things on the stack for compressed blobs.

Also can you check if the hash function in lz4/xxHash is the same one as in coreutil.h?

No, it's something different, not even one-call. A few functions forming some "hashing pipeline".

from what I gathered by reading the source of xxHash is that it can be done in bulk or streamed mode.
Bulk consists of 1 function -- XXH64 ()

Here comes encryption with two notes as for now:

No MAC checking yet
I didn't really have a neat idea about how to do "no password" thing, so here's kinda a little monster. Please look closer at this, maybe it is ok...

About MACs: I had an idea of making another block in our format (before block of offsets for example; it will be 0-size block when no blob is encrypted) and also another few bytes for MAC-count. I'll have to spend a little more time to tell how complicated it will be, but for now I think it'd work fine.

Like we dont care about rejecting other content, we only care about that content being protected.

Also now the convert2BAW tool will now have to take a password argument :)

Added some comments in the latest push

Also can we have an option to specify whether to save texture paths relative to the input or output files in the Convert2BAW tool? (by implication also have this option in WriteProps, i.e. if non 0 length relative path exists then save relative to that path instead of the output file)


Update documentation for changes based on test review

The documentation needs to be updated based on changes made when reviewing tests.

This was previously completed.  Close the issue.


Add filters to .dockstore.yml

Is your feature request related to a problem? Please describe.
Some users create multiple workflows from a single GitHub repo. This more easily allows the different workflows to share code. The .dockstore.yml supports this via a list of workflows.
In this "one GitHub repo, many workflows" model, versions from different workflows show up associated with every workflow from the repo. This makes it hard for a user to view the relevant  versions for a particular workflow.
Describe the solution you'd like
The .dockstore.yml should have a filters section. See CircleCI filters as an example of one way to implement this.
Another benefit of this approach is that it gives users control over whether to publish branches or not. We've discussed this a few times whether Dockstore should or shouldn't publish branches; this gives the workflow developer fine-grained control over it.
A third benefit would be that it could limit the amount of data Dockstore indexes.
Slightly Detailed Proposals
If the filters section is not specified, then the branch/tag is processed by Dockstore.
If the filters section is specified, then it's processed by Dockstore if it meets the filter condition.
CircleCI divides filters into branches and tags; Dockstore could do the same, and/or also support releases. Or we have a simple filter. Rough ideas:
workflows:
  - name: gwas
    primaryDescriptorPath: /gwas.wdl
    filter:
      - gwas*
      - develop

Or
workflows:
  - name: gwas
    primaryDescriptorPath: /gwas.wdl
    filter:
      - tags:
        - gwas*
      - branches
       - develop
       - master

Describe alternatives you've considered
Hide the version after publishing
The Dockstore API lets you hide versions for published workflows. This approach has some limitations.

You can only hide the version after exists.
User would need to figure out how to automatically invoke it. Push to GitHub triggers Dockstore to read version; what then triggers the API call to hide it?
The versions would still be there in the database and in the My Workflows view.

Push to another repo
One of our users is doing a version of this. This approach will work great, and will be the best in the that it gives the user a chance to run tests and flatten descriptors.

Workflow is pushed to GitHub repo A.
CI server, e.g., Travis or CircleCI, auto runs tests; if they pass

Optionally flattens the descriptors (combines workflows' descriptors into one descriptor)
Pushes to GitHub repos B, C, and D (one for each workflow)
GitHub repos B, C, D are configured with Dockstore GitHub app; Dockstore gets notified and reads the latest.

The main downside of this approach is initial set-up work, but once you have it, it gives you a lot of flexibility, and you'll have the confidence of tests validating your code.
Have different .dockstore.yml's in different branches and/or tags
Before creating a tag/release, change the .dockstore.yml to match the the tag being released.
Starting point:
...
workflows:
  - name:  gwas
    primaryDescriptorPath: /gwas.wdl
  -name: align
    primaryDescriptorPath: /aligner.wdl

Before creating GWAS release, change the .dockstore.yml to get rid of align:
...
workflows:
  - name:  gwas
    primaryDescriptorPath: /gwas.wdl

Now before creating align release, the change the .dockstore.yml to get rid of gwas and add align
...
workflows:
  -name: align
    primaryDescriptorPath: /aligner.wdl

Downsides:

Cannot release multiple workflows off the same commit
.dockstore.yml will be changing frequently. Not necessarily a bad thing, but it's typically fairly static in other user cases.

┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Sprint: Backlog
┆Issue Number: DOCK-1513

I am a big fan of filtering by tags or branches separately.

I like
workflows:
  - name: gwas
    primaryDescriptorPath: /gwas.wdl
    filter:
      - gwas*
      - develop

I think the only think to add is that this would be a new feature whereas "Have different .dockstore.yml's in different branches and/or tags" is a workaround that could work today.

I love the filters idea, it seems the most configurable.
The push to multiple repos idea.. you're right that it's not too bad once it's automated, but it does make a clutter of repositories which I don't love, and duplicates code. The testing benefit of this proposal is unclear to me, we already have automated plumbing and scientific tests for each pipeline we release in our one repository, and it's been made a bit 'smart'- it only runs the tests for pipelines that have changed.
Thanks for looking into this, I love the filters idea and would be happy to use that feature when it exists!

@kbergin

Do you see a need to distinguish tags that are releases from tags that aren't releases? I'm wondering if we should account for that.
I see your point about pushing to multiple repos; I think there's validity both ways.

@coverbeck

We don't usually use tags that aren't releases, I'm not sure if that's typical or not.
Yea the multi repo vs single repo thing usually comes down to preference.


Save in-memory db to disk after all

Allow for persisting a in-memory db, aka 'i changed my mind', aka save()

not now


Build the CLI using pkg

See https://github.com/zeit/pkg

So does that (effectively) do the same thing as your node-static-entry-point thing?

Yep, but we'll try to re-use as most as we can in order to avoid having to maintain custom code.

Should node-static-entry-point now be marked as a 'deprecated' project?

Done!


yellowtailflounderGB with the mincatch option fails.

There are two problems:

/data/data_raw/AssessmentHistory/yellowtailflounderGB_Discard.csv is missing.
The following code is missing the bit to read in the yellowtailflounderGB_Discard.csv.
https://github.com/lkerr/groundfish-MSE/blob/170517f04d2ae9fe75ee35beb6f79267fabd6430/functions/managementProc/get_nextF.R#L219-L246

@mle2718 is working on item 2.

Yellowtail flounder historical data and US discards have been updated.


A few comments on Overpass API

Quick comment on the Overpass section in https://github.com/wcedmisten/wcedmisten.fyi/blob/e73fa7d431b506fb963129eea61a73015f2e4640/articles/how-to-query-osm.mdx#1-overpass-turbo:
Rate limits - since the service is provided to the public for free, it has limitations on the size and duration of each request.

    Queries that take longer than 180 seconds will be canceled
    Queries that use more than 512 MiB of RAM will be canceled
    Just for context, this means we can find all Italian restaurants in Virginia, but not in the whole US

180s and 512MB are only default settings for a query, which are used unless you override the settings in your query. They're not hard limits. The OSM wiki has some details on both settings, and how to tweak them:

timeout
maxsize

So yes, you can request all Italian restaurants across the whole US, absolutely no issue with that:
[out:json][timeout:600];
area["ISO3166-1"="US"]->.searchArea;
nwr["amenity"="restaurant"]["cuisine"="italian"](area.searchArea);
out center;

By the way, this isn't directly related to rate limiting either, which is something different again for Overpass API. That's a story for another time...

Thanks for clarifying that! Renamed to "resource limits" and clarified the behavior of Overpass:
https://github.com/wcedmisten/wcedmisten.fyi/commit/a6fe8e4437de7d060e91fa4288facaa6c76ccb85


Can I get an Array of Arrays instead of an Array of Objects?

Is it possible to get an Array of Arrays from a query instead of an Array of Objects?
I mean, instead of this:
var result = alasql('SELECT field1, field2 FROM table_name');
// result = [{field1: "value1", field2: "value2"}, {field1: "value3", field2: "value4"}]

This:
var result = alasql('SELECT field1, field2 FROM table_name');
// result = [["value1", "value2"], ["value3", "value4"]]

I know I can do it myself afterwards, but maybe there is a way of telling alasql to do it internally so that the results are not iterated over again by me. If result has 300k rows * 10 fields this makes a difference.

By prepending MATRIX OF  before SELECT you will get what you are looking for.
var result = alasql('MATRIX OF SELECT field1, field2 FROM table_name');
// result = [["value1", "value2"], ["value3", "value4"]]

https://github.com/agershun/alasql/wiki/Matrix


Update TableDetail Page

Summary of Changes
This PR makes the following changes to features on the TableDetail page.

Updated the styles  regarding the column name and column type that will allow for long column titles to wrap.

Updated the table lineage section to only render if the url is neither null nor an empty string.

Updated the explore sql button to only render if the url is neither null nor an empty string.

Fixed a regression in the tableMetadata reducer that prevented the failure status code from getting passed back to the application, causing the preview button to be stuck on "Loading". This fixes issue #202 .

Tests
N/A. The TableDetailPage is currently intentionally uncovered due to an upcoming major refactor. The unit tests for ducks/tableMetadata exist in PR but have not yet been able to be merged to master. PR #208 will be updated after a rebase to test this logic.
Documentation
N/A. No new features or apis have been added.
CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes, including screenshots of any UI changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public python functions and the classes in the PR contain docstrings that explain what it does

[x] PR passes all tests documented in the developer guide
[x] I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message"

Codecov Report

Merging #210 into master will decrease coverage by 0.09%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master     #210     +/-   ##
=========================================
- Coverage   58.53%   58.43%   -0.1%
=========================================
  Files         123      123
  Lines        3053     3058      +5
  Branches      345      347      +2
=========================================
  Hits         1787     1787
- Misses       1235     1240      +5
  Partials       31       31

Impacted Files
Coverage Δ

...plication/static/js/ducks/tableMetadata/reducer.ts
35.29% <ø> (+1%)
:arrow_up:

...ts/TableDetail/DetailList/DetailListItem/index.tsx
0% <0%> (ø)
:arrow_up:

...ication/static/js/components/TableDetail/index.tsx
0% <0%> (ø)
:arrow_up:

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 719f9fc...64968a1. Read the comment docs.


VM: NixOS, with Mycelium and way how to see Mycelium addr in UI (Portal)

Verified:

Devnet
f3e199e


Add chart to a helm chart repository

What would you like to be added:
Can we put this in a proper helm chart repository?
Why is this needed:
Helmfile doesn't like raw tgz files, if this is in a helm repository it would be much easier to work with and be like everything else.  Helmfile works just fine w/ custom repos so it doesn't really matter where it goes just needs this setup: https://helm.sh/docs/topics/chart_repository/

I will be working on this sooner than later. please feel free to comment any other requirements.

Hello,
our chart is hosted on github pages. you can pull as below
helm repo add splunk https://splunk.github.io/splunk-connect-for-kubernetes/

helm show values splunk/splunk-connect-for-kubernetes > values.yaml

helm install sck splunk/splunk-connect-for-kubernetes -f values.yaml


Crash in ios 11

react-native: 0.39
react-native-camera:0.4
Every time I take or select a photo on an iphone with IOS 11 it crashes.

Works perfect on IOS 10 or earlier.

Sorry was fixed here.
https://github.com/lwansbrough/react-native-camera/issues/923


Can one XML depend on another XML?

The SBE depends on XML file to generate the encoder and decoders. Can we define another XML which has some common definition  being used in the original XML. This will help to avoid writing same message types used my multiple services.

Yes see this example.
https://github.com/real-logic/simple-binary-encoding/tree/master/sbe-samples/src/main/resources

Thanks. Thats helpful.


[Featurerequest] Generic io.Writer interfaces for every log interface

It is a very common case to pass contents to an io.Writer.
In many cases one would just want this content to end up in your logs.
For example when one creates a cobra command you pass os.Stdout to the out parameter of the new command.
It would be very helpful to have access to each implemtations io.Writers like impl/cli/cli.go does
(see https://github.com/mattfarina/log-go/blob/main/impl/cli/cli.go#L23-L43).
For example for impl/std/std.go each of the structs field could point to os.Stdout.
As a result every logger would become more easy to replace by another implementation (which is not possible for us at the moment we have to stick to impl/cli for now (example: https://github.com/mattfarina/hypper/blob/viccuad/add-list/cmd/hypper/list.go#L74-L81).

There is a problem with exposing the io.Writer for each implementation. Some of the implementations do not make that accessible and do not have one easily accessible internally. If the Logger were to expose an io.Writer interface, which level should it be? Some might want info while others want Debug or Trace levels.
My solution can be found in the io package. Instead of exposing something internally, it makes any level accessible as an io.Writer. Even if the underlying implementation does not provide it.
Does that work?

That would suffice, I'm consuming io for hypper list and hypper install succesfully. E.g: https://github.com/mattfarina/hypper/pull/37/commits/9d8878005e4d94409fc377d7bd44afbad59a6457


Add better support for T4 templates in NSwag.MSBuild

I'm generating clients and controllers from swagger and using T4 templates and the NSwag.MSBuild package for that.
At the start of my templates, I have something like this:
...
#><#@ assembly name="$(SolutionDir)\packages\NSwag.MSBuild.9.9.0\build\NJsonSchema.dll"
#><#@ assembly name="$(SolutionDir)\packages\NSwag.MSBuild.9.9.0\build\NJsonSchema.CodeGeneration.dll"
#><#@ assembly name="$(SolutionDir)\packages\NSwag.MSBuild.9.9.0\build\NJsonSchema.CodeGeneration.CSharp.dll"
#><#@ assembly name="$(SolutionDir)\packages\NSwag.MSBuild.9.9.0\build\NSwag.Core.dll"
#><#@ assembly name="$(SolutionDir)\packages\NSwag.MSBuild.9.9.0\build\NSwag.CodeGeneration.dll"
#><#@ assembly name="$(SolutionDir)\packages\NSwag.MSBuild.9.9.0\build\NSwag.CodeGeneration.CSharp.dll"
...

But every time there's an update to NSwag, I have to change the version number on all T4 templates.
Reading this article, I made the following change to the NSwag.MSBuild.props file:
<?xml version="1.0" encoding="utf-8" ?>
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <PropertyGroup>
        <NSwagExe>$(MSBuildThisFileDirectory)\NSwag.exe</NSwagExe>
        <NSwagDir>$(MSBuildThisFileDirectory)</NSwagDir>
    </PropertyGroup>
</Project>

and, now, my templates are like this:
...
#><#@ assembly name="$(NSwagDir)\NJsonSchema.dll"
#><#@ assembly name="$(NSwagDir)\NJsonSchema.CodeGeneration.dll"
#><#@ assembly name="$(NSwagDir)\NJsonSchema.CodeGeneration.CSharp.dll"
#><#@ assembly name="$(NSwagDir)\NSwag.Core.dll"
#><#@ assembly name="$(NSwagDir)\NSwag.CodeGeneration.dll"
#><#@ assembly name="$(NSwagDir)\NSwag.CodeGeneration.CSharp.dll"
...

At the moment, this only works on Visual Studio (2015), but I'm working on making it work on MSBuild too.
In the mean time, would it be acceptable to add that change to the NSwag.MSBuild.props file?

Seems good to me...

Please reopen if not solved.

Thanks for the PR.

Working like a charm.


Correct column widths when table data contains colspans

If a row contains data with colspans, the column width calculations are thrown off.
Example 1: A table has a header row with two columns: one with a colspan of 9 and the other with a colspan of 4.  The next row has 13 normal columns.

Current Behavior: The width of the second column on the next row becomes 1/4 the width of the second column in the first row (the one with the colspan of 4).
Expected Behavior: The width of the second column on the next row is calculated by the data within the column itself.

Example 2: A table has a row in which the first column has a colspan of 2, and the following 10 columns are normal.  The last column has a very large width.  The next row has 13 normal columns.

Current Behavior: The width of the second-to-last column on the next row is identical to the width of the last column on the first row (the one with the very large width).
Expected Behavior: The width of the second-to-last column on the next row is calculated by the data within the column itself.

An example HTML template can be provided on demand to illustrate the problem if necessary.

Thank you for your work! And sorry for the delay.
This looks correct, we will test it on some of our examples in jsreport and come back here.

@fmmich thanks for your work here. i'm going to merge the PR

An example HTML template can be provided on demand to illustrate the problem if necessary.

it will be great if you include a test with this example HTML in another PR, so we keep track of the case that was failing for future changes