Fetch all videos with search request rather than only approx. 500 video results.

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[x] I've searched the bugtracker for similar questions including closed ones

Question

As the problem stated in the title, how can I fetch all the video search results rather than just a part of results, approximately 500 results. I'm not sure this is the limit from youtube or youtube-dl?
Currently, I'm using the search command with youtube-dl like this youtube-dl ytsearchall:"ditempat"

With the git master I have 501 results. The limit in the extractor itself is infinite, so perhaps there's a server-side limit, maybe depending on the API key in use.

dirkf 500 is a lot, is that a single page? Im pretty sure that you can do pagination with youtubei

30 pages, and then that's it.

That might be all thats possible. I know with the Google Play API, it maxes out at about 600. In the past I have worked around this by using search operators:
after:2013-01-01 before:2014-01-01

The website also only loads 30 pages

So someone who wanted an exhaustive search could either

guess a small enough timeslice to have fewer than 500 results at most and iterate from the birth of YT to now, or
binary chop the period from the birth of YT to now to get periods that each have fewer than 500 results and iterate over those,

or a combination of the two.

afaik, this is not possible with INNERTUBE APIs since the website only provides a limited list of date filters. It may be possible to come up with more generic filters by analyzing the protobuf? (cc @coletdjnz)

IIRC at least one extractor implements a scheme similar to those I described, but making use of a proper date-range query and a total results field.

It wouldn't be a filter, you'd just use search operators as part of the query:
https://www.youtube.com/results?search_query=cats+after:2013-01-01+before:2014-01-01

The URL in my previous comment was just a proof of concept. The proper usage would be something like this:
youtube-dl ytsearchall:'cats after:2013-01-01 before:2014-01-01'

although I dont know the current support of something like this in YouTube-DL.

Request like this works as expected:
POST /youtubei/v1/search?key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8 HTTP/1.1
Host: www.youtube.com

{
  "context": {
    "client": {
      "clientName": "WEB",
      "clientVersion": "2.20201021.03.00"
    }
  },
  "query": "cats after:2013-01-01 before:2014-01-01"
}

If you check the publishedTimeText in the result, they are all one of these:
8 years ago
9 years ago

Tested but failed with error like this:
ERROR: Unable to recognize tab page;

As advised in the related thread, you need the git master, or PR #27749.
The cats query is very productive so testing it on a scale of months produces strange results (more cats in the last six months of 2013 than the whole year, eg).
But I do believe the result that 8 "cats" were posted in 2013-01-01..02 and 20 in 2013-01-01..05.
$ python -m youtube_dl -v --flat-playlist 'https://www.youtube.com/results?search_query=cats+after:2013-01-01+before:2013-01-02'
[debug] System config: [u'--prefer-ffmpeg']
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'--flat-playlist', u'https://www.youtube.com/results?search_query=cats+after:2013-01-01+before:2013-01-02']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Git HEAD: 60f014a47
[debug] Python version 2.7.17 (CPython) - Linux-4.4.0-210-generic-i686-with-Ubuntu-16.04-xenial
[debug] exe versions: avconv 4.3, avprobe 4.3, ffmpeg 4.3, ffprobe 4.3
[debug] Proxy map: {}
[download] Downloading playlist: cats after:2013-01-01 before:2013-01-02
[youtube:search_url] query "cats after:2013-01-01 before:2013-01-02": Downloading page 1
[youtube:search_url] query "cats after:2013-01-01 before:2013-01-02": Downloading page 2
[youtube:search_url] playlist cats after:2013-01-01 before:2013-01-02: Downloading 8 videos
[download] Downloading video 1 of 8
[download] Downloading video 2 of 8
[download] Downloading video 3 of 8
[download] Downloading video 4 of 8
[download] Downloading video 5 of 8
[download] Downloading video 6 of 8
[download] Downloading video 7 of 8
[download] Downloading video 8 of 8
[download] Finished downloading playlist: cats after:2013-01-01 before:2013-01-02
$

afaik, this is not possible with INNERTUBE APIs since the website only provides a limited list of date filters. It may be possible to come up with more generic filters by analyzing the protobuf? (cc @coletdjnz)

even if we could, manipulating protobuf in youtube-dl/p is not something we can easily do


Unable to delete app- option disabled

The Delete icon (trash can) is disabled which prevents me from deleting an app I created while testing. How can I remove this unneeded/unused test app?

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

ID: b28c3b2e-d661-682d-df1b-68d941016e87
Version Independent ID: b2ebf2b0-f9d3-2583-4e64-54fa083b5a57
Content: Integrating Applications with Azure Active Directory
Content Source: articles/active-directory/develop/active-directory-integrating-applications.md
Service: active-directory
GitHub Login: @CelesteDG
Microsoft Alias: celested

Thanks for your feedback! We will investigate and update as appropriate.

Hi @DeanGross,
There are several options you can check. This often happens either if the app service is still running or has some dependencies in another resource.  This can also happen if you do not have the right permissions or administrative access to the application. I would first go to the App Service and hit "stop", and then try deleting again. Then make sure that you delete any dependencies within that resource (database, app service plan, etc).
You can also delete the application through Powershell by running the following script:
Remove-AzureADApplication
-ObjectId
[-InformationAction ]
[-InformationVariable ]
[]
https://docs.microsoft.com/en-us/powershell/module/azuread/remove-azureadapplication?view=azureadps-2.0

I'm going to close this out if this answers your question. Please open a new issue if you need additional information.


feature request: claim fly

similar to a feature that the lands plugin offers, the ability to allow users to fly in their own claim with a permission node (or others with a different perm).
this feature would also preferably have some config options similar to lands (see here).
there are also plugins like this for grief prevention, but I couldn't find anything for husk claims.

This plugin will work https://www.spigotmc.org/resources/choco-fly-1-20-x.95180/

This plugin will work https://www.spigotmc.org/resources/choco-fly-1-20-x.95180/

oh, neat, I'll give this a try; thank you! 😄

Closing in favor of an external plugin ^^

Closing in favor of an external plugin ^^

to be honest chocofly works horribly, fly keep working when players get out of the claim, would be nice this feature to be build-in to not happen bugs like that


Splash screen is hiding after a few seconds and white screen is dispalyed for 2-3 seconds

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[ x ] 3.x
I'm submitting a ...  (check one with "x")
[ x ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
When application runs,

splash screen is shown for a 2-3 seconds (no matter what is set in SplashScreenDelay
splash hides and white blank screen is shown for 2-3 seconds
main page is shown

p.s Even if I remove splashScreen.hide(); from app.component.ts, still splash screen will hide very fast (as before)
Expected behavior:
Splash screen last as long as the time specified in SplashScreenDelay, then hides
config.xml
    <preference name="SplashMaintainAspectRatio" value="true" />
    <preference name="FadeSplashScreenDuration" value="300" />
    <preference name="SplashShowOnlyFirstTime" value="false" />
    <preference name="SplashScreen" value="screen" />
    <preference name="AutoHideSplashScreen" value="false" />
    <preference name="SplashScreenDelay" value="15000" />

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
global packages:

    @ionic/cli-utils : 1.3.0
    Cordova CLI      : 7.0.1
    Ionic CLI        : 3.3.0

local packages:

    @ionic/app-scripts              : 1.3.7
    @ionic/cli-plugin-cordova       : 1.3.0
    @ionic/cli-plugin-ionic-angular : 1.3.0
    Cordova Platforms               : android 6.2.3
    Ionic Framework                 : ionic-angular 3.3.0

System:

    Node       : v6.9.1
    OS         : Windows 10
    Xcode      : not installed
    ios-deploy : not installed
    ios-sim    : not installed

runtime need time

Hello! Thank you for opening an issue with us! Would you be able to provide a sample application via GitHub that demonstrates the issue you are having? Thanks for using Ionic!


sometimes slimjar task stucks

14:24:16: Executing task 'publishToMavenLocal'...

> Task :publishToMavenLocal UP-TO-DATE
> Task :common:generatePomFileForShadowPublication

> Task :common:compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :common:processResources NO-SOURCE
> Task :common:slimJar

its not passing the slimjar task for about 4~ minutes. but sometime it does immediately.

If this is with 1.2.2, this is likely due to the extra compile time resolutions


in need for non-standard function code 0x13

Hi, I've been using this library for about two years now on ESP32, to my great content. But now for some chinese device, I need to write to the input registers (typically the 0X10 is used for this) via code 0x13, according to the manufacturer modbus protocol.  But as expected the addRequest of this message returns 'Error creating request: 01 - Illegal function code'. What would be the easiest way to make an alteration to the library source? I tried commenting the 'if (functionCode == 13) return ILLEGAL_FUNCTION; // FC 13 does not exist' in modbusmessage.ccp but no luck....

Augh! 0x13 is explicitly set to ILLEGAL_FUNCTION, because the Modbus Standard does not allow user defined codes in that range ("intentionally left blank"). These Chinese...
It may work to map the code as a user defined code, though, but that will require some more changes.
I could offer to write a service call to explicitly add any FC to the USER_DEFINED group, so you could write your own check code for these codes as you need to.

Hi, the device in question is not one I can easily swap with another one that follows the modbus standard. I guess the manufacturer wanted to incorporate some sort of tamper protection by deviating from the modbus standard. The 0x13 function call is not the only one they've taken the liberty to work with, they've also used other strange function call-numbers. Ideally would be a solution where the user can freely choose a function call number and tell the library 'make the modbus message as if it were 0x05,0x06, 0x10 function call. But I guess that's already determined by the passed arguments to the 'addMessage' function? A free FC to the user defined group could work for me, I have someone working on the project with good programming skills for the check code-part.

I am thinking of some call to release any arbitrary FC from the bounds of the standard to have it handled completely by the application.
A message then will have to be set up with add() calls, starting with the server ID and function code proper. There is one addMessage() call already that takes a prebuilt ModbusMessage as a parameter. Of course no message internal parameter checks will be done in it.
Give me a day or so to implement it.

that would be great, thank you.

On the way. There is a "FC-redefinition" branch now that already has the required functionality, but is completely untested yet. It compiles and passes the standard test sketch, but the new feature has not been tested.
If you are adventurous enough, you may try it 😉
There is a set of FC types now:
enum FCType : uint8_t {
  FC01_TYPE,              // Two uint16_t parameters (FC 0x01, 0x02, 0x03, 0x04, 0x05, 0x06)
  FC07_TYPE,              // no additional parameter (FCs 0x07, 0x0b, 0x0c, 0x11)
  FC0F_TYPE,              // two uint16_t parameters, a uint8_t length byte and a uint16_t* pointer to array of bytes (FC 0x0f)
  FC10_TYPE,              // two uint16_t parameters, a uint8_t length byte and a uint8_t* pointer to array of words (FC 0x10)
  FC16_TYPE,              // three uint16_t parameters (FC 0x16)
  FC18_TYPE,              // one uint16_t parameter (FC 0x18)
  FCGENERIC_TYPE,         // for FCs not yet explicitly coded (or too complex)
  FCUSER_TYPE,            // No checks except the server ID
  FCILLEGAL_TYPE,         // not allowed function codes
};

You can assign a new type to any function code by
Error ModbusMessage::redefineFunctionCodeType(uint8_t fc, FCType t);

So to use your 0x13 code exactly as 0x10, you will have to put
ModbusMessage::redefineFunctionCodeType(0x13, FC10_TYPE);

in your setup(). A call with addMessage(1, 0x13... will (should, as of now) behave exactly like the addMessage(1, WRITE_MULT_REGISTERS... now.

Master
Request message format

Slave  Address
Function Code
Starting Address
Numbers of the register
Register-1 value
。。。
Register-N value
CRC16

1 byte
1 byte
2 bytes
2byte
2bytes
N-2
2bytes
2 bytes

Byte
Byte
Hi   Byte Lo   Byte
Hi   Byte Lo   Byte
Hi   Byte  Lo Byte
。。。
Hi Byte  Lo Byte
Hi Byte  Lo Byte

Hi, no luck yet; I get timeout.
Below is the protocol description of the device in question. I'm a bit confused by the lack of a byte count as specified in the modbus.org standard. Could it be that this is not like 0x10 function code?

Master
Request message format

Slave  Address
Function Code
Starting Address
Numbers of the register
Register-1 value
。。。
Register-N value
CRC16

1 byte
1 byte
2 bytes
2byte
2bytes
N-2
2bytes
2 bytes

Byte
Byte
Hi   Byte Lo   Byte
Hi   Byte Lo   Byte
Hi   Byte  Lo Byte
。。。
Hi Byte  Lo Byte
Hi Byte  Lo Byte

Yeah, looks like the message format is different.
MB.addRequest(m);

yess, succes! After messing around a bit to find out that the token needs to be passed as second argument in the addrequest when using self composed MBmessage, I was able to write to the register and readback the altered register content.

Glad to read it worked. Sorry, I wrote the post on my mobile and do not know all the calls by heart...

@TLS1000 Please note that the RTU-issues branch ist supposedly getting merged with master. The way to redefine function codes has slightly changed, so you will have to modify your code once again. Sorry for that, I was not happy with the way I had implemented it before.
There is a table of allowed function code types:
enum FCType : uint8_t {
  FC01,              // Two uint16_t parameters (FC 0x01, 0x02, 0x03, 0x04, 0x05, 0x06)
  FC07,              // no additional parameter (FCs 0x07, 0x0b, 0x0c, 0x11)
  FC0F,              // two uint16_t parameters, a uint8_t length byte and a uint16_t* pointer to array of bytes (FC 0x0f)
  FC10,              // two uint16_t parameters, a uint8_t length byte and a uint8_t* pointer to array of words (FC 0x10)
  FC16,              // three uint16_t parameters (FC 0x16)
  FC18,              // one uint16_t parameter (FC 0x18)
  FCGENERIC,         // for FCs not yet explicitly coded (or too complex)
  FCUSER,            // No checks except the server ID
  FCILLEGAL,         // not allowed function codes
};

You will have to use one of these to redefine a function code. Redefinition is done by
const FCType redefineType(uint8_t functionCode, const FCType type);

If you will omit the type parameter, type FCUSER is used as a default.
This is possible only for function codes not covered by the Modbus standard, that initially will have a type of FCILLEGAL. After the modification, the new function code may not change its type again.
The function call will return the now active type - if it is identical to that you attempted to set, you were successfull.
Any function code's type can be read with
const FCType getType(uint8_t functionCode);

Hope that will work for you.

Hi Michael,
Sorry for my late response, I'm in the middle of updating PCB's in order to
get them to the factory....
'After the modification, the new function code may not change its type
again'.  I'm using multiple strange FC's in succession 0x42,0x49. You mean
I cannot do multiple 'redefinitions+addrequests'?
regards,
Wouter
Op zo 22 mei 2022 om 17:00 schreef Michael Harwerth <
@.***>:

@TLS1000 https://github.com/TLS1000 Please note that the RTU-issues
branch ist supposedly getting merged with master. The way to redefine
function codes has slightly changed, so you will have to modify your code
once again. Sorry for that, I was not happy with the way I had implemented
it before.
There is a table of allowed function code types:
enum FCType : uint8_t {
FC01,              // Two uint16_t parameters (FC 0x01, 0x02, 0x03, 0x04, 0x05, 0x06)
FC07,              // no additional parameter (FCs 0x07, 0x0b, 0x0c, 0x11)
FC0F,              // two uint16_t parameters, a uint8_t length byte and a uint16_t* pointer to array of bytes (FC 0x0f)
FC10,              // two uint16_t parameters, a uint8_t length byte and a uint8_t* pointer to array of words (FC 0x10)
FC16,              // three uint16_t parameters (FC 0x16)
FC18,              // one uint16_t parameter (FC 0x18)
FCGENERIC,         // for FCs not yet explicitly coded (or too complex)
FCUSER,            // No checks except the server ID
FCILLEGAL,         // not allowed function codes
};
You will have to use one of these to redefine a function code.
Redefinition is done by
const FCType redefineType(uint8_t functionCode, const FCType type);
If you will omit the type parameter, type FCUSER is used as a default.
This is possible only for function codes not covered by the Modbus
standard, that initially will have a type of FCILLEGAL. After the
modification, the new function code may not change its type again.
The function call will return the now active type - if it is identical to
that you attempted to set, you were successfull.
Any function code's type can be read with
const FCType getType(uint8_t functionCode);
Hope that will work for you.
—
Reply to this email directly, view it on GitHub
https://github.com/eModbus/eModbus/issues/184#issuecomment-1133914474,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFLMWOQ6VPKIVW4XEFIZMXLVLJDZHANCNFSM5UIRGXHQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
ing. Kestelyn Wouter,
Greenergy Solutions
Heufkensstraat 70B
9630 Zwalm, BE
ING bank:<PHONE_NUMBER>-77
mobile: +32 (0)484/ 41.80.66
VAT: BE0816.878.768

No worries. That was supposed to explain that a function code like your 0x42 and 0x49 can be set to type FCUSER or whatever in setup() and will keep that type throughout the remainder of the program. You will not be able to some time later change again to, say: FCGENERIC, the code will keep the first type you assigned.

Closing now again, as the change is mainstream now.


feat(explorer/recent): allow removing all recent builds

Closes #889

Messages

:book:

:white_check_mark: All tests are passing
Nice one! All 125 tests are passing.

:book:

:floppy_disk: Here's the built vsix for this change.

  Generated by :no_entry_sign: dangerJS against 2d1e4423bceed40e5ce4495a31918c729b06b5db


KAFKA-9775: Fix IllegalFormatConversionException in ToolsUtils

The runtime type of Metric.metricValue() needn't always be a Double,
for example, if it's a gauge from IntGaugeSuite.
Since it's impossible to format non-double values with 3 point precision
IllegalFormatConversionException resulted.

@omkreddy @ijuma and chance of a review?

@tombentley Nice caching!
How did you discover this issue? Is there a log of test case showing the IllegalFormatConversionException

@chia7712 I was just running the kafka-consumer-perf-test with --print-metrics (in a 2 broker cluster, if that makes any difference). I've added a regression test.

retest this please

@ijuma, @omkreddy, @chia7712 thanks for the review, updated.

retest this please

retest this please

Thanks @omkreddy. Do I need to be on a whitelist, or can I trigger the tests too?

retest ths please

@tombentley currently only admins (committers) can trigger the builds.


404 response when K8s ingress is set with path: "/*" pathType: ImplementationSpecific

Bug Description
When user sets rules in K8s ingress with path: "/*", pathType: ImplementationSpecific, Istio messes up in routing and returns 404.
If we change config to use  path: "/", pathType: Prefix, it works.
Version
1.14 and above

Additional Information
No response
Affected product area

[ ] Ambient
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

@keithmattix this is the bug we had discussed

/cc @jaellio this is the issue I told you about

I believe @jaellio fixed this in 1.18

Fixed by #44898


operator crunchy-postgres-operator-rhmp (5.0.5)

Signed-off-by: Andrew L'Ecuyer<EMAIL_ADDRESS>

We  are working on fixing this Pipeline issue for you.  I'm going to temporarily close this PR but I will re-open it shortly.


Fix remove trustline

Reopening #8 with some additional changes.

Maybe I should choose a different changelog message, because I realized the library already allowed removing a trustline, by not specifying any limit:
https://github.com/aurora-rs/stellar-base-rs/blob/9070dd02978231e552c490de879a6a7ce775d080/src/operations/change_trust.rs#L65-L68
It just didn't allow explicitly passing 0, but not setting any limit would make it default to 0 (unlike the Stellar Laboratory, which then defaults to maximum int64).


New ExtensionPoints for Kubernetes Plugin

Hey, I just made a Pull Request!
Hi, the kubernetes-node plugin has been modified to house a new extension points for Kubernetes backend plugin;
KubernetesClusterSupplierExtensionPoint is introduced .
kubernetesAuthStrategyExtensionPoint is introduced .
kubernetesFetcherExtensionPoint is introduced .
kubernetesServiceLocatorExtensionPoint is introduced .
The kubernetes-backend plugin was modified to use this new extension point.

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

These changes take us most of the way to #17853

Hello, Any feedback would be appreciated !

Hey @benjdlambert, based on comments like this it sounds like the CI checks just aren't gonna go green until @emotion/serialize has a fixed release. Would it be appropriate for you, with your core-maintainer-powers, to merge this one anyway?


Use voicingUtteranceQueue singletone instead of phet.joist.sim.voicingUtteranceQueue

From https://github.com/phetsims/scenery/issues/1217

sim.voicingUtteranceQueue has been removed in branches and in master, all usages have been replaced with the global singleton. This can be closed.


tensorflow.python.framework.errors_impl.InvalidArgumentError: Dimension size must be evenly divisible by 1408 but is 122880 for 'loss/Reshape_1' (op: 'Reshape') with input shapes: [8192,15], [3] and with input tensors computed as partial shapes: input[1] = [?,128,11].

ValueError: Dimension size must be evenly divisible by 1408 but is 122880 for 'loss/Reshape_1' (op: 'Reshape') with input shapes: [8192,15], [3] and with input tensors computed as partial shapes: input[1] = [?,128,11].

是tag个数对不上导致的，你在albert_ner里把有11的地方都改成15，同时metric_fn也修改一下就好了


⚠ Jenkins Plugins Artifactory has degraded performance

In 530cdb1, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 2502 ms

Resolved: Jenkins Plugins Artifactory performance has improved in bbfd961 after 1 hour, 31 minutes.


Download QR image locally

Implement a facility to be able to download the QR image of an easy link.
the download button could be placed next (or below) the copy to clipboard icon

Implemented


Remove token balances in deposit dropdown list

The list of tokens in the select box for depositing tokens shows each token's balance in the user's Ref Finance account. There have been many posts in the support channels from users who think this number is the balance in their wallet, and believe that there is a problem with ref not being able to see their tokens in their wallet. Messages related to this increased substantially when the 4x farming incentive started. Users would go to deposit ref they withdrew from farming rewards, see that there was a "0" next to the REF token, and close the select box without clicking on the token.
I think the ideal solution would be to show the user's wallet balance for each token. However, a quick fix that can be implemented now is to not show any balances at all.  The only change necessary is in DepositPage, where the TokenAmount balances property should be changed to null.
<TokenAmount
  amount={amount}
  max={max}
  total={max}
  tokens={[nearMetadata, ...tokens]}
  balances={null}
  selectedToken={selectedToken}
  onSelectToken={setSelectedToken}
  onChangeAmount={setAmount}
  calledBy="deposit"
/>

If this is an acceptable solution, then it would be great if it could be implemented before the next incentive promotion begins.

I think we still have to solve this problem by improving the user experience instead of removing it. I will talk to our UI deisgner to improve this UI/UX.

I think we still have to solve this problem by improving the user experience instead of removing it. I will talk to our UI deisgner to improve this UI/UX.

Agreed. However if there are other priorities that would prevent the better solution from being implemented before the next incentive is announced, then I, and other mods in the rf telegram/discord groups would appreciate it if this fix could be applied.


A bug? two menu item hightlight at same time

See below screenshot from online demo, You should recreate the issue with below steps:

Open demo page
Click on section 2
Scroll up a little to section 1.

Fix:
onScroll(event) {
        this.currentItem = this.getItemInsideWindow();
        if (this.currentItem !== this.lastActiveItem && this.currentItem) {
          this.removeActiveClass();
          this.$emit('itemchanged', event, this.currentItem, this.lastActiveItem);
          this.lastActiveItem = this.currentItem;
        }
        // Current item might be null if not inside any section
        if (this.currentItem) {
          this.removeActiveClass();
          this.currentItem.classList.add(this.activeClass);
        }
      },

I also added an empty check on line 3 because sometimes, i found the currentItem is undefined but the itemchanged even still triggered.

Hello there,
Could you give me more information regarding OS and Browser version?
I'm testing on MacOS High Sierra 10.13.4 on Chrome version 66.0.3359.181 and looks like it's working as always.

Hey,
My OS is totally same as yours and chrome version is 66.0.3359.139.
I tried in Safari and other machine chrome, both them works good normal. So, it only happened in my machine.
I did a debug and i found the difference: In safari, when I click the section links, it will trigger onScroll method when running at scrollTo => window.addEventListener('scroll', _this3.onScroll);. then it will update the currentItem instance and make the left thing works good. However, in my chrome, the onScroll method will not be triggered by window.addEventListener('scroll', _this3.onScroll);.


Error in auto-failover-group image

second listener should say "Read-only listener" in media/sql-database-auto-failover-group/auto-failover-group.png

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

ID: e22db66f-542f-bc95-c232-fe775754a015
Version Independent ID: c08d859c-0725-7944-ef32-8ee13ccbf8fa
Content: Failover groups - Azure SQL Database
Content Source: articles/sql-database/sql-database-auto-failover-group.md
Service: sql-database
GitHub Login: @anosov1960
Microsoft Alias: sashan

Same issue in the second image.

@MashaMSFT  please work with @anosov1960  to respond to this git issue


Add tweaks for compatibility with AGL

Added _sota overrides to configuration snippets, so that they can be included regardless of whether we are using agl-sota or not. Fixed otaimg in wic.

Review Score: 11/11


Unwrap syntax sugar with ? operator

For functions that don't return any type of Result<_>, the ? operator could be used as a sugar for unwraping.
So for example,
fn test() {
    some_func()?;
}

could be
fn test() {
    some_func().unwrap();
}

since the function test() doesn't return a result.
I think this could be a great use for the ? operator, as typically, either a function returns a result, in which case the error should (usually) be propagated upwards, or the function doesn't and instead unwraps anything it needs.

I don't like this. This hides a panic, which isn't that good, panics should stand out. Also it makes refactoring more error prone because you can change the function from returning a Result to something else and not realize that you aren't handling some errors correctly.

I think that the ? operator does quite a good job of standing out and saying "hey there could be an error here!" The main motivation behind this is that currently, unwrap is too verbose, and it can be very easy to write code that calls a function, unwraps, calls, unwraps, etc, and we get that it can panic there.
I think this use of the ? operator is in fact, very consistent when it comes to reading code, since always ? will mean this code can error. The way the error is handled might be different, but ? will still tell the developer that an error could occur.
As for refactoring:
First, I wanna say that you're definitely right that it's more error prone going from returning result to returning something else. But, going the other way around, the migration from returning something else to returning maybe a Result<_, Box<Error>> (or any other standard/unifying result type) would be extremely easy and not error prone at all.

Remember that "going from returning result to returning something else" can be done accidentally in a function body without changing the function signature. Consider code like this:
fn test() {
  let foo: Option<Foo> = some_func();
  let bar: Option<Bar> = foo.map(|value| value.try_bar()?);
}

This would silently resolve the ? to .unwrap(), where currently it would fail to compile because the function argument to Option::map mustn't return a Result. I think this is a pitfall much worse than the small convenience gain.

I'm not sure if I understand your example, but wouldn't we want the code above to desugar to the code below?
fn test() {
  let foo: Option<Foo> = some_func();
  let bar: Option<Bar> = foo.map(|value| value.try_bar().unwrap());
}

I think it makes a lot of sense that the ? would desugar into an unwrap in that case.
But I can see a case where this would be really really bad:
fn test() -> Result<_, _> {
  let foo: Option<Foo> = some_func();
  let bar: Option<Bar> = foo.map(|value| value.try_bar()?);
}

It would be reasonable to read that code and think any error from value.try_bar() gets propagated to the test function, but of course it doesn't and the ? would instead would desugar into an unwrap.

As a general Rust rule of thumb, unwrapping should be very rare. In fact, you don't even need unwrapping at all, since you can just return a Result from main:
fn main() -> Result<(), Error> {
    foo()?;
     There are exceptions where unwrapping is acceptable, but they're rare and ad-hoc.
The problem is even worse in libraries: if a library returns Result you can choose whether to propagate it or unwrap. But if the library unwraps, then you have no choice.
As such, I don't like the idea of making unwrapping more ergonomic, since it goes against good Rust principles, and leads to worse libraries. Instead, Rust programmers should be encouraged to structure their code in order to avoid unwrapping.
If there is some situation where Result is unergonomic (and thus encourages unwrap), we should fix that problem instead.

I agree. Also, errors can be propagated upwards and unwrapped at the top if needed. Closing.


Research AI Scan methods(OpenAI)

How does the NFT-Go App solve this problem? It probably could be a solution.


is clearfix missing code?

Why clearfix was changed on v4?
original:
.clearfix:before,
.clearfix:after {
    content: " ";
    display: table;
}

.clearfix:after {
    clear: both;
}

https://github.com/twbs/bootstrap/blob/v4-dev/scss/mixins/_clearfix.scss
right now is
@mixin clearfix() {
  &::after {
    content: "";
    display: table;
    clear: both;
  }
}

Your first version (original) supports IE8. In Bootstrap 4 refused to support IE below 9 version. This version Clearfix does not support IE9. See "Beat That ClearFix", a clearfix for modern browsers

^^^ Yup, that :D.

Thanks @mrmlnc for the plug but my latest recommendation is to use display:block instead of display:table; check The very latest clearfix reloaded.
I'll create an issue.


Issue 106 details-columns

Adds support for "columns (details-columns)", slightly structured content on one side and an image (with optional link) on the other.
Also added "either-side" capability to "case-study" style of columns.
Other minor fix to "info-card" to fix vertical alignment.
Fix #106
Test URLs:

Before: https://main--vonage--hlxsites.hlx.page/unified-communications/
Before: https://main--vonage--hlxsites.hlx.page/drafts/columns-details-columns
After: https://issue-106-details-columnns--vonage--hlxsites.hlx.page/unified-communications/
After: https://issue-106-details-columnns--vonage--hlxsites.hlx.page/drafts/columns-details-columns

@dkuntze , I'm not sure what is slowing down the main /unified-communications/ page but it's not anything I added. ;) Running it live (on main and my branch), it looks like the top menu is taking a while to load.


Arguments containing dashes are not parsed correctly

I've tried using the initify package, however, if I choose a license with a 'dash' the value is not recognized.
Steps to reproduce
initify my-app --license apache-2.0
Expected behavior
{
  _: ['my-app'],
  license: 'apache-2.0'
}

Actual behavior
{
  _: ['my-app'],
  license: 'apache2.0'
}

So the license file is not found.

Closes #3


Classes from com.google.code.findbugs missing in shaded jar

Description
The classes from the com.google.code.findbugs dependencies belonging to package javax.annotation are relocated in the shaded jar, but since the dependency has scope provided, they are not really included. This leads to warning messages, at least when using the shaded jar with scala.
How to reproduce
Build a scala project with the shaded docker-client jar.
What do you expect
No warnings about missing classes from com.spotify.*.
What happened instead
A lot of warnings show up.
Warning: scalac: Class com.spotify.docker.client.shaded.javax.annotation.Nullable not found - continuing with a stub.

Software:

docker version: N/A
Spotify's docker-client version: 8.2.0

Full backtrace
N/A

@burgerdev I don't see com.google.code relocated in the pom. I'm not sure why I made com.google.code deps have the provided scope though (see this PR). Maybe it shouldn't be?

The package com.google.code.findbugs contains classes with package javax.annotation (I arrived at this conclusion by googling for Nullable). Those are relocated, but the relocated classes are not packaged because of scope provided. Does it make more sense now?

Yes, thanks. If you remove the provided scope, install the jar locally, then build your scala project. Do the warnings go away?


testing sass in travis

Build passed, despite the build hook between Travis and GitHub being broken today.


Lazy-display of missing dependencies warning

Idea: avoiding warnings of missing dependency (using INFO instead) until one is actually using the feature in which case an exception should be raised.

This is to remind to check it, most of it should have been done already.


bump dependencies

Bumps dependencies to the latest versions of prost and tonic.

I just saw the commit signing constraint.
I'll configure my machine up today to rebase the commit history and sign it.

made a git rebase HEAD~2 to rebase adding commit signing.
Hope it will be good for you, otherwise feel free to give me guidance.


Identity and Recipient Not Available at Runtime

First off, thanks for this package, I appreciate having these bindings available.
I'm encountering an issue where the Identity and Recipient types are not available at runtime, even though they are defined in the source code.
Steps to Reproduce

Install the pyrage and pyrage-stubs packages.

Try to import Identity and Recipient:
from pyrage import Identity, Recipient

This results in the following error:
ImportError: cannot import name 'Identity' from 'pyrage'

What I've Tried

I've checked the installed package, and it seems that Identity and Recipient are not being exposed in the __init__.py file.
The type checker (e.g., in VSCode with Pyright) can see these types, but they are not available at runtime.
I've tried modifying the pyrage-stubs package (e.g., adding py.typed, converting *.py files to *.pyi, adding __all__), but the issue persists.
I've also tried rebuilding the package using maturin and even starting fresh with a new project structure using rye, but no luck.

Additional Context

I'm working on an Apple M1 machine, but I don't think this issue is platform-specific.

I've pushed a fork of the repository with my attempts to resolve the issue: here

I have a temporary workaround in my project where I define the following:
from pyrage import ssh, x25519

Identity = ssh.Identity | x25519.Identity
Recipient = ssh.Recipient | x25519.Recipient

type IdentityT = ssh.Identity | x25519.Identity
type RecipientT = ssh.Recipient | x25519.Recipient

Doing this allows for using the types as both annotations and for instance checking them, e.g.,
from collections.abc import Sequence
from typing import Any, TypeGuard

from pyrage import IdentityError, RecipientError, x25519
from .types.age import Identity, IdentityT, Recipient, RecipientT

def _is_sequence(obj: Any) -> TypeGuard[Sequence]:
    return isinstance(obj, Sequence) and not isinstance(obj, str | bytes | bytearray)

def ensure_recipient_sequence(obj: Any) -> Sequence[RecipientT]:
    try:
        if isinstance(obj, str) and (_recipient := x25519.Recipient.from_str(obj)):
            obj = _recipient
        if isinstance(obj, Recipient) and not _is_sequence(obj):
            return [obj]
        if _is_sequence(obj) and all(isinstance(_, Recipient) for _ in obj):
            return obj
        raise RecipientError
    except Exception as exc:
        raise RecipientError from exc

I am not very familiar with maturin or Rust development in general, so any help or guidance on how to properly expose Identity and Recipient at runtime would be greatly appreciated! My best guess is that while these are certainly type annotations, they may just need to be defined as such Union objects in the Rust source.

Thanks for the report.
Can you say more about what you're trying to accomplish? pyrage is the concrete implementation and pyrage-stubs is the PEP 561 type information package, meaning that you should install both into your development environment if you want type checking.
Notably, you should not import pyrage-stubs (or modify it on disk): it's intended only for the typechecker, not for API usage.
TL;DR: your custom unions/type aliases look fine. pyrage doesn't expose an Identity union type in its actual code, so defining it yourself is perfectly appropriate.
(We could expose one, although that would require converting pyrage from a pure-pyO3 package into a hybrid one with Python source files.)

The reason I was attempting to do things this way to begin with is due to the fact that, if you have the stub package installed as I do, and you are importing directly from pyrage, users are lead to believe that there are in fact such objects for Identity and Recipient.
I've attached a screenshot of what this looks like in VSCode with Pylance, to show what I mean. This is using the latest release without modifying anything. If I run this code, I will get an import error immediately due to the fact that these types are defined, but as you've stated, they are not actually exported from the core package.

Meanwhile, somewhat ironically, as shown here for x25519.Identity.generate(), I am able to fully utilize this function as intended and generate an Identity, but the type checker is unable to infer anything about this function or its return types.

So to answer your question, my hope was that I could correct this inconsistency, otherwise I would not have been modifying anything. Since I could not, I just wanted to bring it to your attention.

I've attached a screenshot of what this looks like in VSCode with Pylance, to show what I mean. This is using the latest release without modifying anything. If I run this code, I will get an import error immediately due to the fact that these types are defined, but as you've stated, they are not actually exported from the core package.

Ah, gotcha -- I wasn't aware that it an IDE would present those aliases as if they're actually importable. That's helpful context; I'll see if I can improve the hinting there tonight or tomorrow.

Meanwhile, somewhat ironically, as shown here for x25519.Identity.generate(), I am able to fully utilize this function as intended and generate an Identity, but the type checker is unable to infer anything about this function or its return types.

Not sure what's up with that one -- from the stubs, it's definitely annotated to return an x25519.Identity there:
https://github.com/woodruffw/pyrage/blob/cd023bca1a89d2a6b76cd5f0e7dc323b4f3a5424/pyrage-stubs/pyrage-stubs/x25519.py#L5-L7
I don't use Pylance, however, so I don't have a clear sense of how it differs from mypy.

Not sure what's up with that one -- from the stubs, it's definitely annotated to return an x25519.Identity there:
https://github.com/woodruffw/pyrage/blob/cd023bca1a89d2a6b76cd5f0e7dc323b4f3a5424/pyrage-stubs/pyrage-stubs/x25519.py#L5-L7

I don't use Pylance, however, so I don't have a clear sense of how it differs from mypy.

I will take another look at this when I get a chance here shortly and see if I can get things to look right on my end, since we are using different environments. As far as I know, for VSCode, Pylance is the default for Python; it's just Pyright.
Regardless, I actually ran into another peculiarity here, and when this happened I started to wonder if this might be specific to my environment, so I actually cleared all the cached packages and other Python files out, syncing everything anew just to confirm. It does not appear to be anything on my side specifically. Rather than get into every little detail, let me just ask:
https://github.com/woodruffw/pyrage/blob/cd023bca1a89d2a6b76cd5f0e7dc323b4f3a5424/pyrage-stubs/pyrage-stubs/__init__.pyi#L19
Is this meant to be typed for in_io, out_io, and Recipients parameters? For me, this function will only work if provided all three arguments. Meanwhile, Pylance is again alerting to the fact that this, according to the typing, is incorrect.

Rather than get into every little detail, let me just ask:
https://github.com/woodruffw/pyrage/blob/cd023bca1a89d2a6b76cd5f0e7dc323b4f3a5424/pyrage-stubs/pyrage-stubs/__init__.pyi#L19
Is this meant to be typed for in_io, out_io, and Recipients parameters? For me, this function will only work if provided all three arguments. Meanwhile, Pylance is again alerting to the fact that this, according to the typing, is incorrect.

Yeah, that one looks like a typing bug, introduced with streaming in #77.
The actual signature is here:
https://github.com/woodruffw/pyrage/blob/cd023bca1a89d2a6b76cd5f0e7dc323b4f3a5424/src/lib.rs#L268-L273
If you'd like to send a PR to fix that, I'd be happy to merge it and get a fixed stubs package out ASAP. Otherwise I'll have time to fix it when I look at this more generally.

(More generally, this suggests that the CI for pyrage should probably be running mypy on the unit tests...)

Got it, opened a PR and I believe I have managed to address the other issues as well. Not sure if you will agree about making the Identity and Recipient types private, but this seemed to be a reasonable solution for the time, as I understood this to mean that these were not originally intended to be part of the public API to begin with.

Not sure if you will agree about making the Identity and Recipient types private, but this seemed to be a reasonable solution for the time, as I understood this to mean that these were not originally intended to be part of the public API to begin with.

Makes sense to me -- those were indeed intended to be private, in the sense that they were there just to provide uniform typing within the stubs themselves. From re-reading the typing docs, it seems like prefixing them with an _ is absolutely correct for that purpose.

Thanks for the PR -- I've cut 1.2.2 of the stubs and they should be available on PyPI shortly. Let me know if you have any other typing issues (and sorry for the misunderstanding originally).


8312 - update db POST route and create helper script

Shippable/pm#8312
https://github.com/Shippable/admiral/issues/193#issuecomment-294044148

complete. closing.


Question about DSVT-P on waymo

In paper B.1.1，it is mentioned here that both DSVT-P and DSVT-V have 4 DSVT blocks, but it seems that dsvt_models/dsvt_plain_1f_onestage.yaml is only 1 block.

you can refer config. The set info is 36, 4, indicating 4 blocks. You can print the model architecture by running the code.


I cant get rid of VRPerfKit properly from my vrchat

Try the latest release:
https://github.com/tappi287/openvr_fsr_app/releases/tag/0.9.9


Sidekick pushes down office frame, hiding the bottom bar

Sidekick pushes down the entire Word/Excel iframe, pushing the bottom 49 pxels out of the viewport. This makes the status bar at the bottom inaccessible.

:tada: This issue has been resolved in version 3.25.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


opaevfio, opae.io: explicitly bind to vfio-pci

On recent kernels, eg >= 5.15, writing to new_id on the first attempt
after creating the VFs successfully binds the VF to vfio-pci. However,
after the VF is released, trying to bind it again without an explicit
write to vfio-pci's bind sysfs node fails. Handle EBUSY in the case
that the driver bind is attempted after the first write to new_id.
On subsequent writes to new_id, explicit binding is required.
Signed-off-by: Tim Whisonant<EMAIL_ADDRESS>

Coverage increased (+0.03%) to 66.055% when pulling 1f25749bbb55c14acb84b28b6381cc5502a30b35 on tswhison/vfio into 6a22123cad5a2eb10ba58080dc99618cc6b70619 on master.


Fix args of feature docstrings

Fix Args section of feature docstrings.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Add built-in AwsLambdaReceiver

Description
We have been recommending the combination of ExpressReceiver + aws-serverless-express for AWS Lambda deployments. https://slack.dev/bolt-js/deployments/aws-lambda
Although it's still a great option for running Bolt apps on AWS Lambda, initializing an Express app plus running aws-serverless-express as an adapter may cause unnecessary overhead for both booting and response time.
const { App, AwsLambdaReceiver } = require('@slack/bolt');

// processBeforeResponse: true by default
const receiver = new AwsLambdaReceiver({
  signingSecret: process.env.SLACK_SIGNING_SECRET,
});
const app = new App({ receiver });
app.event('app_mention', async ({event, logger}) => {
  logger.info(event);
})

module.exports.main = receiver.toHandler();

For OAuth flow handing, we still recommend using ExpressReceiver and aws-serverless-express. The reason for this is that @slack/oauth package depends on the standard HTTP module in Node. The following is a simple SAM app example. You can find the complete version here: https://github.com/seratch/bolt-js-aws-lambda
const { App, ExpressReceiver, AwsLambdaReceiver } = require('@slack/bolt');

const myInstallationStore = {
  storeInstallation: async (installation) => { ... },
  fetchInstallation: async (query) => { ... },
};

// OAuth Flow
const expressReceiver = new ExpressReceiver({
  clientId: process.env.SLACK_CLIENT_ID,
  clientSecret: process.env.SLACK_CLIENT_SECRET,
  scopes: process.env.SLACK_SCOPES,
  stateSecret: 'my-secret',
  installationStore: myInstallationStore
});
const awsServerlessExpress = require('aws-serverless-express');
const server = awsServerlessExpress.createServer(expressReceiver.app);
module.exports.oauthHandler = (event, context) => {
  awsServerlessExpress.proxy(server, event, context);
}

// Slack Event Handler
const eventReceiver = new AwsLambdaReceiver({
  signingSecret: process.env.SLACK_SIGNING_SECRET,
});
const app = new App({
  receiver: eventReceiver,
  authorize: async (source) => { myInstallationStore... }
});
app.command("/hello-bolt-js", async ({ ack }) => {
  await ack("I'm working!");
});
module.exports.eventHandler = eventReceiver.toHandler();

See also:

https://github.com/slackapi/bolt-js/issues/361

What type of issue is this? (place an x in one of the [ ])

[ ] bug
[x] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[x] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

We'll use issue #815 to add documentation and example code for AWSLambdaReceiver.

@seratch @mwbrooks I am still having issues with the AWS Lambda + OAuth process. I am using it bolt successfully for handling events, dialogs etc. But I am trying to convert our old code to both for our oauth install and callback.
We are getting the following error.
api | [WARN]   Unexpected content-type detected: undefined
api | [ERROR]   Failed to parse body as JSON data for content-type: undefined

Here is an example of the code - https://gist.github.com/viperfx/310a5ad7aed0f300889d52234b2fb85e

Are there plans to make the AwsLambdaReceiver capable of handling OAuth?


PVDataSource should only correct PVOutput.org timezone on "legacy" PVOutput.org data

Since PRs https://github.com/openclimatefix/pvoutput/pull/102 and https://github.com/openclimatefix/PVConsumer/pull/11, our PVConsumer code will convert datetimes to UTC. But nowcasting_dataset assumes that PVOutput.org data is in Europe/London timezone (see these two lines of code in nowcasting_dataset). Somehow, nowcasting_dataset needs to know if the PVOutput.org is already in UTC, or if it still needs to be converted from localtime to UTC.
Context

https://github.com/openclimatefix/pvoutput/issues/14
https://github.com/openclimatefix/pvoutput/pull/102
https://github.com/openclimatefix/PVConsumer/pull/11
https://github.com/openclimatefix/PVConsumer/issues/8

Implementation
Perhaps the easiest solution might be to convert the PVOutput.org data we currently have on disk to UTC, and then remove these two lines from nowcasting_dataset.
Or, perhaps a better solution would be to modify pvoutput so it explicitly sets the timezone to UTC on all the datetimes (see https://github.com/openclimatefix/pvoutput/issues/14#issuecomment-1070456676). Then nowcasting_dataset would only assume PVOutput.org data needs converting from Europe/London timezone to UTC if the timestamps lack an explicit UTC offset.

perhaps #563 could be done first


chore(build): add automerge workflow

Description
Adds a GitHhub action workflow to auto-merge release branch to master branch.
Changelog
New

A GitHhub action workflow to auto-merge release branch to master branch.

Thanks @emyarod for reviewing!


crash: unexpected fault address

Seems to be originating from gorilla secure cookie dependency.

Since this is faulting on a non-nil address, I would suspect there is a data race somewhere that is corrupting memory.

Looks like the modifications made to the gui bit sorted this out, been monitoring the mainnet test instance for a while now for bugs. Haven't caught anything in weeks. Would like to be certain before closing this however. Leaving it open.

I saw this error whilst running this commit https://github.com/decred/dcrpool/commit/02316c25888848fd9e131a69c91e9268a47e9903
hence why I created the PR updating the dependencies

This just happened again while I was running https://github.com/decred/dcrpool/commit/d2181e147fa7aa0533dd481b56ec67f359a8592b with a few local changes (only GUI files changed)
Here is the dcrpool output seg fault.log

It happened again, and this time i was running the go.mod changes proposed in #108
error2.log

build with -race and check the output for any discovered data races.

I'm on my third run with -race and I still haven't reproduced it locally.

Did some more testing after updating my build. Still cannot reproduce this issue, I restarted the pool several times running the harness as suggested, no dice. Shifting focus.

@jholdstock please test with a -race built binary since you are the only one that is hitting this.

Found a race, fixed in #122. Seems to be unrelated because even with the fix, the crash above is still happening. No further races detected

How about with -msan (to enable the LLVM memory sanitizer)?

Tried this, the crash still occurs and the output appears to be the same:
error3.log


Feature request: be able to provide a specific image for landscape mode

Currently, we have to provide a single square image that will be used both for portrait and landscape modes.
However that only works if the logo is in the middle of the image.
In my case the center of my image is empty because I display both my logo and the name of my app, as on the picture below. Beside the fact that I like it that way, one the advantages of doing this is that Cordova's spinner at load doesn't overlap with my logo as shown on this screenshot:

My picture is fine when cropped by the genie in portrait but not in landscape:

So I'd like to be able to provide a landscape-specific version of my image.
What do you think? Thank you

This will be possible with the complete rewrite of Icon Genie v2 (by using multiple profile files).


Re-add old PL code for deriving a cost basis for shares owned in a synthetic short

From Alex on Discord:
"essentially we'll need to recreate the data that was in the moneySpent column there
and for any sale transaction the cost basis will be amount of position sold * moneySpent / amount owned before trade
using actual on chain owned shares.. hm so we'll need that data too
oh we should have that though, just their share balance
for the issue btw its not just specific to synthetic shorts but its mostly relevant for them since I think if all we had was longs things would just work
I'm wondering about my previous comment too about the share balances being available. This is for historical data so I dont think it is
so we'll need the numOwned data from the old PL to come back as well
actually I think we may still calc that one sec
nah we dont store historical amounts. We'll need that as well
cost basis for longs that are selling synthetic shorts is gonna be fun
just a sum of the cost basis for each outcome"

@adrake33 is this for the transaction pg

@Chwy5 Yeah, I believe this was referring to the cost basis on the tx page. Since we removed that from v1, this would need to be done for v2.

@nuevoalex -- This looks to be a ticket related to what we were talking about last week re: netPosition and actual position.
I can't recall if that still needs to happen,

I vaguely recall this not being an issue in V2 though I think I'd need the context of the actual feature desire again

I have a feeling we don't actually want to do this and we really just want to simplify the data export so that its easily importable by any of the crypto tax packages.
Meaning, we just export raw values and don't try to continually calculate the basis in terms of the export.

Closing as irrelevent in V2


Each plugin hook should link to example plugins built with it

https://datasette.readthedocs.io/en/latest/plugins.html#plugin-hooks


Zipmark for ACH?

We're pretty far along with Citizens (#3366), but it's always good to have options on the table. I learned about https://zipmark.com/deposit last night from Andrew Somerville.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/18338088-zipmark-for-ach?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

Called and left a message for the salesperson that Andrew gave me contact info for.

I filled out the contact form on their website.

Had a phone call. Follow-up scheduled for next Monday. Asked to have someone there that can talk to us about underwriting.

They collect name, SSN, mailing address, email address. Sounds like an iframe workflow.

Called back to fast-track, because Balanced deletes information a week from tomorrow. Call set for 2:15 (~45 minutes), to include their founder (@jakehow) as well as their bizdev person.

From a slide deck:

Transparent, Tiered Pricing

volume
$/ea

0-500
0.50

501-2,500
0.35

2,500+
0.25

The monthly minimum of $250 is applied to the ﬁrst 500 transactions of the month, and
transactions 501+ are billed at the rates noted above.

Docs (login required, and there's no open registration):
https://dev.zipmark.com/docs/disbursement/creating_a_disbursement
https://dev.zipmark.com/docs/disbursement/creating_a_disbursement__no_vendor_relationship
https://dev.zipmark.com/docs/disbursement/listing_disbursements
https://dev.zipmark.com/docs/disbursement/viewing_a_disbursement

Just got off the horn. Sounds like this might actually work. !m @catskul

Honestly, though, it's a little unsettling that they have no underwriting process whatsoever. After dealing with Citizens (#3366), this feels like a pendulum swing too far in the other direction. :-(

Hey guys. Let me know if you have any questions.
Re: underwriting
I assume gratipay.com is the merchant of record for this app.  If you guys go to production you will go through our underwriting process.
Our transactions are eventually routed to our partner banks so we abide by the same restrictions you might see if you go direct we are just much better at helping you through the process and automating the parts that can be.

Thanks @jakehow. We just got rejected trying to go direct (#3366), so it looks like you're our best bet. :)
I've got docs in email from your team, will be following up shortly ...

@whit537 sounds good feel free to send us your emails to<EMAIL_ADDRESS>for invites to our team slack if you need help.

@whit537 also, make sure you are using the newest docs... http://docs.zipmark.com
If you don't have the login ping us on the same email.

Cool, just emailed re: @rohitpaulk and myself.

@jakehow Yeah, I have the login. I'll share it with @rohitpaulk. When will that be out of beta?

New API: http://docs.zipmark.com/api#make-a-deposit.

@whit537 its in production we just have not finalized docs yet.

Okay, cool.

@jakehow Looks like webhooks aren't deployed yet? How are failures currently handled?

Note for Gratipay team: Zipmark has a $250/minimum, which at 50¢ per transaction is 500 transactions. We're not going to meet that for a while, which means this is going to be really expensive for us until we do. We were almost up to that level before the Gratipocalypse, and now we're back down to about 25 per month.
@jakehow Any chance you can cut us a break on the minimum for 3 months while we rebuild our userbase? See Gratipocalypse and Gratipay 2.0 for backstory. I'm happy to explain more if need be ...

Re: Webhooks ...

I think that warning may be a little overzealous just because we may adjust the attributes still
I’m looking into how webhooks currently operate as compared to the docs, I’ll let you know when I’m done.

Docs sent to Zipmark.

The webhooks endpoint will work per the docs.  The issue is that none of the available resources on the docs are currently enabled to send notifications.   For example, you can POST to the webhooks endpoint to create a webhook that will receive notifications, but no events - like say creating a deposit - will not send a notification to the URL of that webhook.  We will be working on that and will let you know when we are finished. This is the last piece to get turned on in production and we will keep you posted on its status.  Are there any specific needs, concerns, or requirements you have for your webhooks that you want us to know about?

Me:

Thanks, []. The one webhook we're currently using at Balanced is ACH credit failures. How are those currently handled in the absence of webhooks?

Docs sent to Zipmark.

Okay, with that, I'm closing this out! Migration reticketed as #3522, and modifying payday as #3523.
!m *
:dancer:

Awesome!

From: Zipmark

Let's schedule a call tomorrow to go over your business model. We want to make sure that your new model is in compliance with regulations - a measure you seem to have taken. On the call will be Jake, whom you've been communicating with. Does 11am work for you?

Also, we will need an updated bank letter that is addressed to Zipmark.
To: Zipmark

Hah! I knew it. :)

Yes, happy to discuss. I can make 11am tomorrow work, yes. As background for our call, here is Gratipay's risk management program.

I will get you the new bank letter, either tomorrow or Monday.
lol

From: Zipmark

Thanks for being so transparent. Just crossing our Ts and dotting our Is.

Talk to you tomorrow.

To: Zipmark

Thanks for the call. I really appreciate your willingness to help Gratipay clear the bar on BSA/AML compliance. Here is our current review procedure. I'll watch for a list of vendors from you and I'll come back to you with questions as we upgrade our CIP/CDD procedures this next week or so. Our target at this point would be to process on Zipmark on June 18, or June 25 at the latest.

I'll watch for a list of vendors from you and I'll come back to you with questions as we upgrade our CIP/CDD procedures this next week or so.

The list of vendors is included in a sales slide deck I received in private email. Here's the content (linkified) from the two relevant slides, with the original slides screen-capped below.

Integrations

Zipmark integrates with leading verification services, so we can validate customer information on your behalf with no additional work by your team.

Plaid
Clearbit
MicroBilt
BlockScore
Jumio

Other Integrations

Some of these are proposed integrations and if there’s a need we will work with you to get them implemented.

Account Authentication

Plaid
Intuit
Yodlee
MicroBilt
Accuity

Fraud Scoring

SiftScience
Signifyd
Feedzai
Early Warning

Device Verification

ThreatMetrix
Maxmind minFraud

Business & Personal Data

SmartyStreets
iovation
Trusteer

Verification

Neustar
Clearbit
kickbox.io
FullContact
41st Parameter

Identity Verification

Blockscorehttps://blockscore.com/
EveryoneAPI
Jumio
MicroBilt
IDology

Two Factor Authentication

Authy
Twilio
VoiceVault

To: Zipmark

I've moved the list to a private repo, and updated this comment.

Note that we won't ultimately be able to keep the integrations we're using under wraps, for two reasons. First, our code is open source, so whatever third-party vendor(s) we end up using will show up in our public source code repo on GitHub.

Second, and more importantly, I'll need to publicly discuss and decide together with the Gratipay community what vendor(s) we're in fact going to use for AML. Ease of integration with Zipmark would naturally be one of the criteria, but if you're willing to work with whomever we pick, then I guess we can simply pick based on other criteria.

From: Zipmark

Thanks for doing that.

We'll be ready to release that information soon so what you're doing now is fine by privatizing the repo.

From: Zipmark

How is everything coming a long on your end? Do you need anything from me?

I'm out of the office, but I'm available by email and my office line directs to my cell.

Talk to you soon.
To: Zipmark

Thanks for reaching out, []. I was able to connect with [] in Slack the other day, and we have an initial understanding of the work Gratipay needs to do to clear the compliance bar with Zipmark. If you can believe it, we've got a couple even hotter fires to put out this week, after which AML and Zipmark will become our top priorities.

The good news is that we have an extra week with ACH on Balanced (we found out last week). I expect we'll need it in order to achieve our compliance goals before migrating, so our current target is to run ACH on Zipmark on June 25.

Here are the details of our scheduling and prioritization. Let's touch base again early next week.

Thanks! :)

From: Zipmark

Sounds good to me. I'll reach out to you on Monday or Tuesday and we'll work to get you processing by June 25th.

From: Zipmark

Hope you had a great weekend. I briefly skimmed over the links you sent in your previous email. Looks like we need to hammer down an AML solution in order to begin implementation. How have discussions gone on your end? Do we need to schedule another call help facilitate this?

To: Zipmark

Thanks for checking in.  Comments/questions:

I believe we're primarily looking at four pieces to this puzzle:

individual identity verification

business identity verification
sanction screening
suspicious activity monitoring

Does that match your expectations?

Our ideal at this point will be for Gratipay to implement a program with global reach, even though with Zipmark we'll just be doing ACH for U.S. receivers.

Does Zipmark offer IAT?

What do you understand Gratipay's requirements to be in terms of suspicious activity monitoring and reporting?

Here are the vendors we're currently evaluating for individual IDV and sanction screening:

Trulioo

IDchecker
Veratad IDMatch
Integrity
BlockScore
Jumio
Accuity

IDV Check

Any recommendations or red flags, looking at that list?

Here's where we're looking at business IDV. How does business IDV impact our Zipmark integration?

To: Zipmark

Our best option may be to scrap the Balanced migration data and sign up all users from scratch (we only have 16 users that we've already onboarded on the new Gratipay w/ bank payouts). Can we schedule a call or chat to discuss what that would look like?

How about tomorrow (Thursday) at 11am or 2pm?
h/t @kaguillera @dmk246

Had a call with Zipmark. It turns out that they need to perform identity checks on their side.  Any information collection we do on our side would then simply pre-load the workflow in their iframe, and they would hit identity services again. They're going to put together a pricing package for us.

@whit537:

It turns out that they need to perform identity checks on their side. It's not enough for us to perform the identity checks on our side

Would that mean it would be possible to offload identity checks onto ZipMark entirely?

To: Zipmark

We've decided not to move forward with Zipmark for Gratipay, due to time constraints, the complexity of the task, and the low volumes we're operating at right now. I appreciate your willingness to try to make it happen for us, and especially your feedback on our AML program. Thank you.

You have an export file from Balanced with our users' information. Could you please see to it that that information is securely deleted? Thanks.

Would that mean it would be possible to offload identity checks onto ZipMark entirely?

Not in a simple way, as I understand it.
I've made the call to pull out here.

From: Zipmark

Thank you for the update. I'd like to talk to you about your decision soon so I can get a better understanding of what we can do to help you out. Let's stay in touch because Jake and I both believe that your volume will return to the level that which you had prior to the Balanced shut down.

I'm out of the office today (sick), but I will make sure that the information we received is securely disposed of when I'm back in the office.

Received in private email:
Subject: Intro: Zipmark and Gratipay

Hi Chad,

I recently came across Gratipay and I wanted to reach out.

At Zipmark, we process payments for a wide range of companies, from on-demand service marketplaces to insurance companies, and to everything in-between. We provide a completely white-labeled solution, which helps our clients replace checks, offers flexible escrow management and enables faster clearing times for ACH transactions.

As a result, we have a lot of experience solving a wide range of payment issues. If your team is experiencing any pain points around its current process, I would be more than happy to set up a call. You can also schedule some time to talk by clicking the "My Calendar" button in my signature line.

Best,

[]

Thanks Simona. No pain points right now, but I will keep you in mind.
P.S. Here's a record of our history with ZipMark:
https://github.com/gratipay/gratipay.com/issues/3491


NIFI-4045: POST lineage may not respond with eventId

NIFI-4045:

Addressing issues causing the eventId to not be relayed when submitting a lineage request under certain conditions.

+1, code LGTM, build OK, event ID is correctly populated in the requests.


Make connect() and connect_with() take a FnOnce for the codec

This PR changes the signature of serde_transport::tcp::connect() to take a FnOnce() -> Codec for its codec parameter, which makes it symmetric to its listen()  counterpart:
let server_transport = tarpc::serde_transport::tcp::listen(addr, Json::default).await?;

// Can now be called with `Json::default` instead of `Json::default()`:
let client_transport = tarpc::serde_transport::tcp::connect(addr, Json::default).await?;

This prevents a minor footgun in which a user calling connect() with e.g. Json::default instead of Json::default() would get an inscrutable error from rustc.

@googlebot I signed it!


Not running on ARM architecture (Odroid C2)

Hi,
I have the following docker-compose file:
version: '3.4'
services:
ntp:
#build: .
image: cturra/ntp:latest
container_name: ntp
restart: always
ports:
- 123:123/udp
cap_add:
- SYS_NICE
- SYS_RESOURCE
- SYS_TIME
environment:
- NTP_SERVERS=time.cloudflare.com
I tried to run it on my ArchLinux Odroid C2 Server but I always get the error:
ntp    | standard_init_linux.go:211: exec user process caused "exec format error"
Then I copied the same docker-compose file to my Macbook Pro and ran it there with Docker-Compose up and everything just worked out of the box.
I prefer using Docker-Compose instead of Dockerfile.
Is there any chance I can run my personal ntp server on the Odroid?
When I googled the error message I came across a post where someone has written that it is a architecture problem.

I'm new to Docker, so pardon me if I made a stupid mistake or if I don't get something right. But I think I 'understood' how docker should be running.
Kind regards,
Daniel Oberlechner

thanks for reaching out @DanielOberlechner and i'm sorry this container is not working for you on your odriod c2. unfortunately i have no way to reproduce this error myself so it may be difficult to come up with a solution for you.
let me think on this a little bit and get back to you. if i do make a chance, i will need help testing it. that may mean working from a branch in this repository - is that something you're comfortable doing?
do you have other containers successfully running on this odriod? and if so, do you by chance know if any of them are based on alpine linux?

@DanielOberlechner an update for you to test, when you have a moment. i've built a test container image that supports the following architectures: linux/amd64, linux/arm64 and linux/arm/v7.
when you use the following image, it should automatically run the native version on your odriod c2 (assuming it's linux/arm64 or linux/arm/v7).
in your docker-compose file, can you update the image to image: cturra/ntp-test:latest and try running again?

Hi cturra,
thank you for taking time to solve this problem!
I created a new image from cturra/ntp:latest but I get the same error.
I think that you got the wrong architecture.
The Odroid CPU is:
Amlogic S905 : Quad Core Cortex™-A53 (ARMv8 64bit) processor with Triple Core Mali-450 GPU
that means it is ARMv8 not v7 ...
I have the pihole running and a nginx instance.
Do you need further information?
How can I help you the best?
Greets from Italy,
Daniel :)

thanks for your help to test this change and i'm so happy to hear this new build process resolved the issue you were seeing.
for now, please feel free to continue to use the ntp-test container image on dockerhub. i need to re-tool a couple things on my end to build/push in the same way to the main ntp dockerhub project. once that's complete, i will reach out so you can verify that all worked as expected also.
i really appreciate your help! and greetings from Canada. 🇨🇦

That's cool. I'm happy to help if I can! :)
Just let me hear if I can do help you.
Greets Daniel

@DanielOberlechner i have an update i'd love your assistance in testing. i have now created a new dockerhub repository for multi-architecture support. would you be able to update your docker-compose file to this new image and give it a restart for me?
image: cturra/ntp-multiarch:latest
if that works as expected for you, i will remove the ntp-test repository since that's not a super friendly name (it was afterall, just a test).
i have also updated the documentation around this if you want to give it a review:

https://hub.docker.com/repository/docker/cturra/ntp-multiarch

thanks again for all your help!

Hi @cturra,
I've updated the image name and everything works like it should! :)
One small thing I noticed:
The clock is now not synced and therefore it doesn't work yet.
You could add https://hub.docker.com/r/cturra/ntp here a small text,
and tell the people that it will work after some time?!
I tried ntpdate -qd  and it shows me the offset.
I guess it takes some time until everything is synchronized.
Maybe some people will not get it instantly that everything works just fine.
But thats just my opinion, I guess it could help some folks out there ...
If you need more help don't hesitate to contact me.
Kind regards,
Daniel :) 👍

@cturra - cturra/ntp-multiarch:latest seems to work on rpi3. Any thoughts on time sync @DanielOberlechner is talking about, though?

thanks for your patience with my reply @DanielOberlechner @mkozjak.
i suspect the flapping you're seeing over time with synchronization may be the results of using a single ntp server. if you update your NTP_SERVERS environment variable in your docker-compose file to use more than one ntp server, it may initially take a longer to get all the peers sychronized when you start the container, but probably will stay in sync since you have more endpoints to query. can you folks try using google's time servers again and report back?
snippet from docker-compose file:
environment:
      - NTP_SERVERS=time1.google.com,time2.google.com,time3.google.com,time4.google.com

just a heads up that there's been another issue opened to look into the skew that you both might be interested in checking out. see issue https://github.com/cturra/docker-ntp/issues/17 for some updates i have made. any assistance you can provide in testing would be wonderful!
note: i have not yet built the updated feature branch with multi-arch support, so it will only work on amd64 at the moment.


MODULE_NOT_FOUND error

In your package.json, you keep referencing dist/index.cjs. However, it doesn't exist, so I keep getting MODULE_NOT_FOUND:
Error: Cannot find module '/opt/app/node_modules/ethers-decode-error/dist/index.cjs'
at createEsmNotFoundErr (node:internal/modules/cjs/loader:1181:15)
at finalizeEsmResolution (node:internal/modules/cjs/loader:1169:15)
at resolveExports (node:internal/modules/cjs/loader:591:14)
at Function.Module._findPath (node:internal/modules/cjs/loader:668:31)
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1130:27)
at Function.Module._resolveFilename.sharedData.moduleResolveFilenameHook.installedValue [as _resolveFilename] (/opt/app/node_modules/@cspotcode/source-map-support/source-map-support.js:811:30)
at Function.Module._load (node:internal/modules/cjs/loader:985:27)
at Module.require (node:internal/modules/cjs/loader:1235:19)
at require (node:internal/modules/helpers:176:18)
at Object.<anonymous> (/opt/app/src/index.ts:14:1) {
code: 'MODULE_NOT_FOUND',
path: '/opt/app/node_modules/ethers-decode-error/package.json'
}

I don't fully understand what's going on. This is the only code I've written with the package:
const errorDecoder = ErrorDecoder.create([interface])

@snnbotchway Thanks for highlighting this issue! I think I may have overlooked the commonjs import and missed the typo in the extension name. I have just released a new fix for this. I have tested it and I have no problem importing it now. Can you update your package to 2.1.3 and see if your error goes away?🙇♂


add flag to specify cilium pod labels

Remove the hardcoded "k8s-app=cilium" label used to get all Cilium pods, and instead,
use a value which can be provided by the user. The default is still "k8s-app=cilium".
Example:
python cluster-diagnosis.zip sysdump --cilium-labels=k8s-app=cilium,kubernetes.io/cluster-service=true

Signed-off by: Ian Vernon<EMAIL_ADDRESS>

This change is

Merging, this has been out for review for a long time.


fortran-lang.org home page "News"

The https://fortran-lang.org homepage has a "News" sidebar on the right-hand side of the page.  The most recent of these items is from June of 2022.  It might be better to eliminate this side bar if the most recent item is almost two years old.

Should we delete the entire section, or simply hide it until there’s a recent news update?


chore: use yargs's built-in version instead of rolling our own

Summary
This is just less code on our side. Behaves the same

Test plan
Green CI

Hopefully this will work on Windows too 🤞

Codecov Report

Merging #6215 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6215   +/-   ##
=======================================
  Coverage   64.37%   64.37%
=======================================
  Files         219      219
  Lines        8453     8453
  Branches        4        4
=======================================
  Hits         5442     5442
  Misses       3010     3010
  Partials        1        1

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 9867e16...866a3d0. Read the comment docs.

Just wanna clarify here the --version code was probably written in 2011 when there was no yargs :D Thanks for cleaning up things.


Dependency on statsd-ruby breaks installation

Thank you for open sourcing trashed. Although I'm not using it anymore I thought I would point out the following in case I'm not the only to experience this issue.
It looks like the new dependency on a 37signals specific version of statsd-ruby has broken installation of trashed as version 0.3.1.signals.1 of statsd-ruby has not been pushed to rubygems.
The dependency was added in bb28604.

Ah, right! You can depend on this version by bundling from https://github.com/jeremy/statsd-ruby.


[Multichain] Introduce a L1ToL2 transaction type

Based on the #731 L1ToL2 message solution, we need to introduce a new L1ToL2 transaction type.
In the beginning, I wanted to handle the L1ToL2 message via the contract, but if we want to support arbitrary transactions from L1(force inclusion), we need to support call MoveAction in Move #486. However, there are some security issues to support dynamic invocation.
So, introducing a specific transaction type for the L1ToL2 transaction is a simpler solution.
From
pub struct RoochTransactionData {
    /// Sender's address.
    pub sender: RoochAddress,
    // Sequence number of this transaction corresponding to sender's account.
    pub sequence_number: u64,
    // The ChainID of the transaction.
    pub chain_id: u64,
    // The max gas to be used.
    pub max_gas_amount: u64,
    // The MoveAction to execute.
    pub action: MoveAction,
}

To
pub struct RoochTransactionData {
    //....
    pub payload: TransactionPayload,
}

pub enum TransactionPayload{
   Action(MoveAction),
   L1BlockHeader(L1BlockHeader),
   L1ToL2Message(L1ToL2Message),
}

pub struct L1BlockHeader{
  pub coin_id: u64, // distinguish different chains, defined in MultiChainAddress, maybe need a better name?
  pub header: Vec<u8>,
}

pub struct L1ToL2Message{
  pub coin_id: u64,
  pub inclusion_proof: Vec<u8>, // proof the message is included in a block header.
  pub codec_type: u8, // BCS, RLP, or ..
  pub message: Vec<u8>, // decode to L1EventMessage via codec type and coin_id
}

pub struct EVML1EventMessage{
  pub sender: EVMAddress,
  pub max_gas_amount: u64,
  pub action: MoveAction,
}

When TransactionPayload::L1ToL2Message, the `sender` in `RoochTransactionData` is relayer's address, and the `sender` in `EVML1EventMessage` is the real user to execute the MoveAction.

But we also need to validate the `EVML1EventMessage` before executing it, and the validated result also needs to be recorded in the `TransactionExecutionInfo`.

For force inclusion:

only messages from arbitration chain can be arbitrated
user generate proof off-chain then call abitration contract on L1 (L1 could check this proof), after verification, L2 have to give the inclusion proof within a fixed time window

@jolestar

It seems like we do not need to introduce a new transaction type. We just need to design a new authentication validator, the validator's authenticator is the inclusion_proof.

It seems like we do not need to introduce a new transaction type. We just need to design a new authentication validator, the validator's authenticator is the inclusion_proof.

@jolestar except inclusion_proof, it should check the MoveAction include needed functions for messaging and checks

Finished, we introduce LedgerTxData
pub enum LedgerTxData {
    L1Block(L1Block),
    L1Tx(L1Transaction),
    L2Tx(RoochTransaction),
}


Config file appears to be ignored

Environment

System OS: MacOS Big Sur

Python Version: 3.9.1

Install Source:
GitHub
pip install https://codeload.github.com/spotDL/spotify-downloader/zip/master

Version OR Commit hash:
Not sure.

Expected Behaviour
config.yml contains output_file: '{artist}/{album}/{track-name}.{output-ext}', would expect to be saved as such.
Actual Behaviour
Songs get saved in the directory using the default output.
The configuration wasn't created when I first ran the app, as expected, so I created it manually. Still was ignored.

spotDL v3 has  no config file.
The config file was used in v2.

spotDL v3 has  no config file.
The config file was used in v2.

There is no option for changing the output directory/format?

There is no option for changing the output directory/format?


Can artifacts be organized into subfolders?

For example I have roughly 20 function apps that get deployed into individual resource groups in addition to many other resources for an enterprise solution. Can the resource group artifacts be group like artifacts/functions/... my artifacts?

It is a good idea, but not likely something we are going to implement based on current priorities. It'd be a great one to submit a PR for :)

@alex-frankel I will have to look into that, sure would make life easier.

It is a good idea, but not likely something we are going to implement based on current priorities. It'd be a great one to submit a PR for :)
EDIT: actually, looks like we may have just gotten a PR for this! @filizt is this PR doing what @tanzencoder is looking for?

@alex-frankel yes we have! We have merged it already. @tanzencoder Import-AzBlueprintWithArtifact cmdlet in Version 0.2.10 of Az.Blueprints PS module has the ability to look into sub folders for artifacts. Just use the -IncludeSubFolders switch in the commandline to turn it on.

Going to close this - I think this is resolved with the latest release of the modules.


Add with NodeCollection(node_list):

Since we are now nuking the TensorNetwork object, we should have an easy way to collect nodes into a list/set automatically.
I purpose doing what Ash suggested before we decided to nuke TensorNetwork and use a with context manager.
It would look something like this
node_set = set()
with NodeCollection(node_set):
  a = tn.Node(...)
  b = tn.Node(...)
assert nodes_set == {a, b}

If you passed a list instead, it would append to the list in the order the nodes were created.
I think this should be fairly easy to do, and it would alleviate most of my concerns around nuking TensorNetwork.

Sounds good, I can work on this.

Great! Go for it!


[DO-NOT-MERGE] Investigate if PR 18320 causes R tests flaky

What changes were proposed in this pull request?
This is just based on my wild guess. Please allow me to test before/after. It is hard to reproduce in my Mac and other OSs too.
How was this patch tested?
N/A

Test build #78805 has started for PR 18456 at commit 9f86d2f.

retest this please

Test build #78807 has started for PR 18456 at commit 9f86d2f.

retest this please

Test build #78808 has started for PR 18456 at commit 9f86d2f.

Test build #78805 has finished for PR 18456 at commit 9f86d2f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78805/
Test PASSed.

Merged build finished. Test PASSed.

Test build #78807 has finished for PR 18456 at commit 9f86d2f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78807/
Test PASSed.

Test build #78808 has finished for PR 18456 at commit 9f86d2f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78808/
Test PASSed.

retest this please

retest this please

Test build #78823 has started for PR 18456 at commit 9f86d2f.

retest this please

Test build #78826 has started for PR 18456 at commit 9f86d2f.

retest this please

Test build #78828 has started for PR 18456 at commit 9f86d2f.

Test build #78823 has finished for PR 18456 at commit 9f86d2f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78823/
Test PASSed.

Test build #78826 has finished for PR 18456 at commit 9f86d2f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78826/
Test PASSed.

Merged build finished. Test PASSed.

Test build #78828 has finished for PR 18456 at commit 9f86d2f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78828/
Test PASSed.

Test build #78832 has started for PR 18456 at commit bfa56c8.

retest this please

These 6 tests are before that PR.

retest this please

test this please

Test build #78833 has started for PR 18456 at commit bfa56c8.

retest this please

Test build #78834 has started for PR 18456 at commit bfa56c8.

Test build #78836 has started for PR 18456 at commit fd90b32.

Test build #78836 has finished for PR 18456 at commit fd90b32.

This patch fails due to an unknown error code, -10.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78836/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #78839 has started for PR 18456 at commit fd90b32.

Test build #78840 has started for PR 18456 at commit fd90b32.

Test build #78839 has finished for PR 18456 at commit fd90b32.

This patch fails due to an unknown error code, -10.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78839/
Test FAILed.

Merged build finished. Test FAILed.

Test build #78840 has finished for PR 18456 at commit fd90b32.

This patch fails due to an unknown error code, -10.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78840/
Test FAILed.

These three tests are R-only tests after that PR.

Test build #78832 has finished for PR 18456 at commit bfa56c8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78832/
Test FAILed.

Test build #78833 has finished for PR 18456 at commit bfa56c8.

This patch fails due to an unknown error code, -10.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78833/
Test FAILed.

Test build #78834 has finished for PR 18456 at commit bfa56c8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

these three tests are full tests after that PR.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78834/
Test PASSed.

hmm... should i revert it for now then it sounds like?

Yes... it looks so... could I ask twenty minutes?  I can't reproduce this on ...
CentOS Linux release 7.3.1611 (Core) / R version 3.4.0 / Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
macOS 10.12.3 (16D32) / R version 3.4.0 / Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
but now I am running on ...
Ubuntu 14.04 LTS / R version 3.3.1 / Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Just want to be sure on this.

sure. I'll check back in an hour or so. I think we are not in a hurry but seems like lots of R tests are failing

btw, is it really 10, not -10?
errno.h
#define ECHILD          10      /* No child processes */
which would seems related. perhaps it happens when it tries to kill the child but the child is gone

I suspect if there is a race condition here - if child can somehow gracefully exit by itself then there is nothing to kill, right?
        if (unserialize(data) == exitCode) {
 +          # If so, we terminate this child.
 +          tools::pskill(child, tools::SIGUSR1)
 +        }

Thanks for good hints! I will take a look and yea, it sounds worth checking.
One thing I wonder is though, I ran R tests 10-ish times on CentOS and Mac OS and 2 times on Ubuntu just now but I can't reproduce this. Should we maybe go reverting this for now? I will open a PR for this again after being reverted.
Sounds I only can reproduce this with Jenkins and I need some debugs with it ...

reverted in master. JIRA reopened.https://issues.apache.org/jira/browse/SPARK-21093

Thank you @felixcheung.

I am closing this.


createSubscriptionClient() should throw error when subscription doesn't exist

Is your feature request related to a problem? Please describe.
We had a subscription "expire" after 14 days, and couldn't figure out why. I would have thought that it would be useful for people to get an error when attempting to connect to a subscription that doesn't exist.
Describe the solution you'd like
  const subClient = sbClient.createSubscriptionClient(topicName, subscriptionName);

This could throw an error, or even
const messages = await subClient.peek();

This could throw one.
Describe alternatives you've considered
Right now, I think the only way is to look in the portal, and see if the subscription exists.
Additional context
Thanks for reading!

The createSubscriptionClient wouldnt throw an error as creating the client does not involve making any connection to the service. But, calling any methods on it like you did for peek() should have thrown an error.
We do have tests for this in case of non existing entities, see https://github.com/Azure/azure-sdk-for-js/blob/%40azure/service-bus_1.1.7/sdk/servicebus/service-bus/test/serviceBusClient.spec.ts#L342-L352
@HarshaNalluru The test above was for a method on the receiver. Can you see if peek() throws  the expected error? If so, then the difference boils down to non existing subscription vs an expired subscription.

We had a subscription "expire" after 14 days, and couldn't figure out why.

@dougmolineux, If the subscription is created in the azure portal, the "Auto delete on idle" property is set to 14 days by default which is probably why the subscription was expired after 14 days. (Inactivity)

You are allowed to pick a higher value or even check "Never auto-delete".

I couldn't repro the problem that is mentioned in the issue though.
@ramya-rao-a, when the await subClient.peek(); is called, MessagingEntityNotFoundError is thrown for the non-existing subscription and for the expired subscription (same error for a deleted subscription too).
(To make the subscription expire while testing, I had set the "Auto delete on idle" property to 6 min.)

Thoughts and followup questions.. @dougmolineux,

You've mentioned that you've haven't seen an error, does it mean the peek call returned with zero messages? Do you corresponding logs so that it would help us understand better?
Do you think it is possible that when your code was executed, the subscription did exist, but when the portal was checked at a later point of time, the subscription expired?
Can you please provide more info on the activity of the subscription during the time it existed?

Thank you for the responses, perhaps I am doing something wrong. I was running this code
  try {
    for (let i = 0; i < 20; i++) {
      const messages = await subClient.peek();
      console.log(messages);

messages was undefined, and no error was thrown by peek. I am using version "@azure/service-bus": "^1.1.5",.
You are correct about it expiring, I had it set to 14 days, so it expired due to that. I refreshed it recently. I will need to do some more testing, perhaps a good test will be to set it to 5 minutes, let it expire and then re-run my code.
For your third item, I am experimenting with the behavior of the azure sdk when adding messages. I'm particularly interested in whether to keep a topic client connection open, and when to close it. I have read the documentation on this, but wanted to just confirm the behavior.

I have actually just realized that my code only has a try {} and finally {} block, i suspect this may have been the issue. Sorry about that! I will close this.


Syncing 1 entries with HASSIO from getPsList. U No results found.

I get the following "error"
2024/01/29 16:32:45 INFO: Syncing 1 entries with HASSIO from getPsList.
U
No results found.
2024/01/29 16:35:35 INFO: Syncing 1 entries with HASSIO from getPsList.
U
2024/01/29 16:38:25 INFO: Syncing 1 entries with HASSIO from getPsList.
U
No results found.
2024/01/29 16:41:15 INFO: Syncing 1 entries with HASSIO from getPsList.
U
No results found.
No results found.
2024/01/29 16:44:05 INFO: Syncing 1 entries with HASSIO from getPsList.
U
No results found.
2024/01/29 16:46:55 INFO: Syncing 1 entries with HASSIO from getPsList.
U

Same or similar as #34  and #14

same issue here, didn't figure out yet.


MYSQL random query not supported by yii2

Model::find()->orderBy(['item_no'=>'RAND()']);

the code above didn't work~

use yii\db\Expression