jenkins_private_key_credentials forces id to be UUID when human readable text is allowed

Hi
I was attempting to use the jenkins_private_key_credentials lwrp.
I wanted to pass in a human readable ID because I am going to be using these credentials in job configurations created automatically via the DSL.  Per the Job DSL documentation, since version 1.2.1 of the credentials plugin, I should be able to find credentials using the ID instead of the description (https://github.com/jenkinsci/job-dsl-plugin/wiki/Migration#finding-credentials-by-description).
Unfortunately, the lwrp is forcing me to make my credential IDs UUID-formatted.... so instead of "github_key", I'm forced to name it something like "aaaaaaaa-aaaa-4aaa-aaaa-aaaaaaaaaaaa" because of:
https://github.com/opscode-cookbooks/jenkins/blob/195c379ea321049f0a7842112b5a93bc54fc28c7/libraries/_helper.rb#L50
https://github.com/opscode-cookbooks/jenkins/blob/master/libraries/credentials_private_key.rb#L40
Also, when you manually configure credentials via the Jenkins UI, you are allowed to use regular human readable text as the ID.
Is there any way to remove this check? Or make this check configurable so I can turn it off? I understand this cookbook is for generic jenkins and this is specific to my plugin version so perhaps just allowing it to be configurable would be a good compromise? Those on the latest plugin can turn the check off, those still on the old plugin can stay the same?
Thanks!

+1 Also having the same issue. Also setting it to some fixed UUID. Would be nice to be able to set the human readable ID
On the other hand though, installing the latest LTS installs the older plugin by default, and you then need to update it to the latest Credentials plugin before you'd be able to use the human readable SSH credential feature.

I'm using human readable text too so I just plop in this quick and dirty monkey patch in my cookbook I use this resource in
# Monkey Patch
class Chef
  class Resource::JenkinsPrivateKeyCredentials

    attribute :id,
              kind_of: String,
              regex: /.*/, # Accept anything vs Private Key credentials must still have a UUID based ID
              default: lazy { SecureRandom.uuid }
  end
end
# End Monkey Patch

Unfortunately, @DanielRedOak's hack isn't enough because there are a bunch of checks for UUID regexps in the code.
In addition, it looks like a bunch of the jenkins_ssh_slave credentials code is trying to be clever and detect if an "id" or "username" is being passed in.
I would recommend ditching this smartness and requiring a credentials "ID" everywhere or a credentials Resource (which would have that id).

Here's a better workaround:
require 'securerandom'
require 'chef/mixin/params_validate'

begin
  orig_verbose, $VERBOSE = $VERBOSE, nil
  Jenkins::Helper::UUID_REGEX = /.*/
ensure
  $VERBOSE = orig_verbose
end

resource_class = Chef::ResourceResolver.resolve(:jenkins_private_key_credentials)
resource_class.attribute :id,
                         kind_of: String,
                         regex: Jenkins::Helper::UUID_REGEX,
                         default: Chef::Mixin::ParamsValidate.lazy { SecureRandom.uuid }

Since that's replacing the constant it deals with @docwhat's concerns.
Someone should just make a PR and fix this though, seems like an easy fix.

I'm seeing this too.  Not sure if this helps, but for me, the human readable name works on initial creation, but then subsequent chef-client runs, it errors:
STDERR: ERROR: Unexpected exception occurred while performing groovy command.
    java.lang.NullPointerException: Cannot get property 'plainText' on null object


Using batch write size on Teradata source

Is it possible to manage the write batch size on the Teradata source? For example if we are using Azure Database there is an option to change the write batch size from 10000 to 60000 to help performance. I was hoping for such a setting for Teradata as that would help where we are trying to copy data from an on-premise system onto a could blob storage or Azure Database.
Thank you

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

ID: a317cac0-e27c-7263-8c85-e44243b21234
Version Independent ID: 8d0f5788-07f2-56e4-79c1-7ee944976f77
Content: Copy data from Teradata Vantage by using Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/connector-teradata.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@vlado101 Thank you for reaching out. At this time we are reviewing the feedback and will provide an update as appropriate

@vlado101 There is no such property for source settings. Even for Azure Database 'write batch size' setting is available only on sink side.
If you have any suggestion/feedback/idea regarding this connector, I would request you to please share it in ADF user voice forum. All the feedback shared in this forum is actively monitored and reviewed by ADF engineering team.
Please do share the feedback link here, once it is created, as it would be help others to up-vote or/and comment on your idea.

@vlado101 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.


xrdp and pulseaudio support & documentation

Is this informaiton still valid ?   Its quite old (2013) so I was wondering if there was updated build information for xrdp & pulseaudio support.
http://www.xrdp.org/index.php?option=com_content&view=article&id=19:xrdp-pulse-sink
thanks
brian

AFAIK it is outdated.
sesman/chansrv/pulse/pulse-notes.ubuntu.txt also needs to be updated but still valid.

the pulse module building instructions are OK.
you just don't need to create an default.pa file anymore.
I'll make an updated version of this to our  github wiki.
On Mon, Jun 27, 2016 at 3:12 AM metalefty<EMAIL_ADDRESS>wrote:

AFAIK it is outdated.
sesman/chansrv/pulse/pulse-notes.ubuntu.txt also needs to be updated but
still valid.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/393#issuecomment-228631816,
or mute the thread
https://github.com/notifications/unsubscribe/ADTH1AmQzMDOI7ImPbcN_Fp3jXl4JHFGks5qPxVmgaJpZM4I-irK
.

Iv'e updated wiki now, look [here] (https://github.com/neutrinolabs/xrdp/wiki/Audio-Output-Virtual-Channel-support-in-xrdp)
HTH.

Thanks so much for the update to the docs.
I'd needed to rebuild the xrdp pulse modules but then saw most of the docs
seem to be from 2013 including the xrdp pulsaudio info so I thought I'd ask
in case I was looking in the wrong places for documentation.
Brian
On Mon, Jun 27, 2016 at 2:50 AM, Idan Freiberg<EMAIL_ADDRESS>wrote:

Iv'e updated wiki now, look here
https://github.com/neutrinolabs/xrdp/wiki/Audio-Output-Virtual-Channel-support-in-xrdp
HTH.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/393#issuecomment-228666554,
or mute the thread
https://github.com/notifications/unsubscribe/ABmtp3uF24gIlxTu-dFMKx65j1w0hhrvks5qP3KxgaJpZM4I-irK
.

Idan..
I followed the instructions of the new wiki info but pardon my being dumb
but on the  page:
https://github.com/neutrinolabs/xrdp/wiki/Audio-Output-Virtual-Channel-support-in-xrdp
this section tells me what to do but then only says "copy the file"... I've
looked at all the directories involved and still
am not sure "what file" this is talking about ?
You need to edit the Makefile in order to build the pulse sink.
Edit PULSE_DIR at the top of the file to point to pulseaudio source
directory you extracted to above.
Then run make.
*Then copy the file *to pulseaudio system modules directory on your system:
for example: /usr/lib/pulse-2.0/modules/
After the "make" what file does someone need to copy to
/usr/lib/pulse-x.0/modules  ?
Brian
On Mon, Jun 27, 2016 at 2:50 AM, Idan Freiberg<EMAIL_ADDRESS>wrote:

Iv'e updated wiki now, look here
https://github.com/neutrinolabs/xrdp/wiki/Audio-Output-Virtual-Channel-support-in-xrdp
HTH.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/393#issuecomment-228666554,
or mute the thread
https://github.com/notifications/unsubscribe/ABmtp3uF24gIlxTu-dFMKx65j1w0hhrvks5qP3KxgaJpZM4I-irK
.

After 'make' is completed successfully you'll find an library called
module-xrdp-sink.so in the directory where you ran make.
בתאריך יום ב׳, 27 ביוני 2016 ב-19:24 מאת bmullan<EMAIL_ADDRESS>
Idan..
I followed the instructions of the new wiki info but pardon my being dumb
but on the page:
https://github.com/neutrinolabs/xrdp/wiki/Audio-Output-Virtual-Channel-support-in-xrdp
this section tells me what to do but then only says "copy the file"... I've
looked at all the directories involved and still
am not sure "what file" this is talking about ?
You need to edit the Makefile in order to build the pulse sink.
Edit PULSE_DIR at the top of the file to point to pulseaudio source
directory you extracted to above.
Then run make.
*Then copy the file *to pulseaudio system modules directory on your system:
for example: /usr/lib/pulse-2.0/modules/
After the "make" what file does someone need to copy to
/usr/lib/pulse-x.0/modules ?
Brian
On Mon, Jun 27, 2016 at 2:50 AM, Idan Freiberg<EMAIL_ADDRESS>wrote:

Iv'e updated wiki now, look here
<
https://github.com/neutrinolabs/xrdp/wiki/Audio-Output-Virtual-Channel-support-in-xrdp
HTH.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/neutrinolabs/xrdp/issues/393#issuecomment-228666554
,
or mute the thread
<
https://github.com/notifications/unsubscribe/ABmtp3uF24gIlxTu-dFMKx65j1w0hhrvks5qP3KxgaJpZM4I-irK
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/neutrinolabs/xrdp/issues/393#issuecomment-228797334,
or mute the thread
https://github.com/notifications/unsubscribe/ADTH1LYkPN3jyJk911CqWSVZMJis75EPks5qP_kggaJpZM4I-irK
.


Importing from Fabric Warehouse

Hi, I'm following the directions for connecting with Azure MFA to a Fabric Warehouse so I can import tables to a semantic model.
But just want to make sure this is supported? The last section on authenticating with server principal or SQL authentication once it's been saved to the model might stop me with that as I'm not sure that's supported in Fabric just yet.

Hi @SwiftDerek - apologies for the late reply.

I'm following the directions for connecting with Azure MFA to a Fabric Warehouse

Which directions are you referring to here? Note that Tabular Editor 2 only supports importing tables using legacy (provider) data sources and SQL-based partitions. In theory, it should work with Fabric, but semantic models created in Power BI Desktop (or Tabular Editor 3), generally use implicit data sources with M-based partitions.

Hi both,
I hope this applies to the same question.
I want to create a new semantic model in import mode in Tabular Editor 2, connected to a Fabric warehouse (or Lakehouse) SQL endpoint.
I managed to connect to the data in Tabular Editor 2 with the MSOLEDBSQL driver as described here (https://docs.tabulareditor.com/te2/Importing-Tables.html) for the Azure SQL Database. However, when I deploy the model to Fabric, I can't process the model and get the following error:
Exception has been thrown by the target of an invocation.;Cannot set the AccessToken property if 'Authentication' has been specified in the connection string. The exception was raised by the IDbConnection interface. Table: products.
The documentation points out that "When deploying your model to Analysis Services, you will most likely need to specify other credentials, such as a Service Principal application ID and secret or a SQL account, in order for Analysis Services to authenticate itself against the source when refreshing table data. This can be specified using TMSL or SSMS post-deployment, or you can set this up as part of your CI/CD deployment pipeline."
But the link is broken.
How do I set up the connection correctly on the Fabric/Power BI side?

I would recommend setting up a dummy model in Power BI Desktop, which loads data from the same source. Then, using Tabular Editor 2, you can copy the table/partition metadata from that dummy model over to the actual model you're working on. That way, the table will be configured in the same way as what Power BI Desktop does, and that should allow the service to perform the refresh.
Note that Tabular Editor 2 will not be able to update the table schema, or import additional tables that use the M-based partitions. So for that, you'll need to (temporarily) switch back to the MSOLEDBSQL approach that you used before, or once again copy a table from a dummy model created in Power BI Desktop.


Simplify the issue template

The template below is way too much. Please consider to reduce it to the headers and allow users to simply fill in the blanks?
** PLEASE READ THIS BEFORE FILING AN ISSUE **
RMWC or MDC?
RMWC is a React wrapper for Google's official MDC that provides a props based interface for their components. Is the bug being caused by RMWC, or MDC? Please do your best to track down where the bug is originating from and post your issue to the proper repository. MDC bugs should be filed here https://github.com/material-components/material-components-web/issues.
Bugs
Follow the template below to ensure the quickest and most accurate response to your issue.
What RMWC Version are you using?

Please be specific, e.g. major.minor.patch

What build system are you using?

Webpack, Create React App, Browserify, SystemJS, None, etc. Also mention if you are using Typescript or Flow.

What are the steps to reproduce the bug?

Please write the steps which need to be taken in order to reproduce the bug. These steps should be
as detailed as possible. PLEASE use the Code Sandbox
to reproduce the bug which will allow a quicker resolution to your issue.

Javascript Sandbox https://codesandbox.io/s/kpy13vqnr
Typescript Sandbox https://codesandbox.io/s/kl0w4xp95

What is the expected behavior?

Please describe what the component/code should be doing that it's not.

What is the actual behavior?

Please describe what the component/code is actually doing that's different from what it should be
doing.

Any other information you believe would be useful?

Done and done


Code Folding bug when @Metadata tags present

Checked for duplicates
Yes - I've already checked
Is this a regression?
No - This is a new bug
Version
90b9f25
Describe the bug
If a certain code branches contain metadata, the individual commands with @metadata tags are collapsible but not the entire logical branch.
Reproduction
https://github.com/user-attachments/assets/7b753d74-9ac2-4c8b-81d0-9fa7f7ce52e1
Logs
No response
System Info
Aerie-prod

Severity
Minor

Notes from tagup

It's confusing that the turnbuckles are aligned with the metadata tag, not on the line of the stem.
If we can only show one turnbuckle collapsing the IF/WHILE is more useful than collapsing the metadata
The indentation of metadata and model should be shifted to align with the command its attached to
Prefer not to have things collapsed by default


Update InteractsWithInput.php

Get all of the input except for a specified array of items after changing names in the form of an array

No plans on adding.


Does this support chef installation on a windows box

Does  config.omnibus.chef_version = :latest install appropriate version of chef on a windows box?

I spent a few minutes trying to make it work, and couldn't.
+1 on a feature request to make this work.

@adamb0mb ...it worked for me on a windows box

Are you using a public windows box? If so, which one? I tried with
opentable/win-2008r2-standard-amd64-nocm.
--
Adam
On Mon, Nov 23, 2015 at 11:00 AM, Sai Sindhur Malleni <
<EMAIL_ADDRESS>wrote:

@adamb0mb https://github.com/adamb0mb ...it worked for me on a windows
box
—
Reply to this email directly or view it on GitHub
https://github.com/chef/vagrant-omnibus/issues/124#issuecomment-159028426
.

Can you try ferventcoder/win7pro-x64-nocm-lite

FYI... I'm trying, but I'm running into Vagrant/box issues that I'm trying to figure out. I'll post here when I get the ferventcoder/win7pro-x64-nocm-lite box running.

OK. I can't get ferventcoder/win7pro-x64-nocm-lite to successfully start (Host: Mac El Capitan, Vagrant 1.7.4, VirtualBox 5). I'm going to have to go down a different path. If I make any progress, I'll let you know.

OK. I figured out my issue. You need to explicitly set config.vm.guest = :windows. The way the ferventcoder/Win7 image is setup, you're required to set that parameter anyways... so vagrant-omnibus came along for the ride.
config.omnibus.chef_version = :latest
config.vm.guest = :windows

There is already an issue for the problem: #90.


Add naming rules for App Insights in NameStep

Regexp to use: ^[-\w._()]+$

Lol if you're going to create an issue it should be in the functions or app service repo
We almost never look through or triage vscode-azuretools

I'll remember to do it, don't worry! 😅


MakeConst demo not working at all

[Enter feedback here]
Not able to build:

So I think the test project is messed up, so remove the test project, and rebuild:

The package already restored:

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

ID: 6e3fc905-7aa1-7f5e-9bfe-fbcef461ad5e
Version Independent ID: a286e20b-1e43-dc57-e0fb-5a9dee7ec3f6
Content: Tutorial: Write your first analyzer and code fix
Content Source: docs/csharp/roslyn-sdk/tutorials/how-to-write-csharp-analyzer-code-fix.md
Product: dotnet-csharp
Technology: csharp-roslyn
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

I see the fix now: https://github.com/dotnet/roslyn-sdk/commit/fdecce7c015b07a9429a4821534e55beec7b4643


Toolchain: Fix $HTTP_RAW_POST_DATA bug

Automatically populating $HTTP_RAW_POST_DATA is deprecated

This is a bug with PHP 5.6. It can be resolved by editing php.ini, and un-commenting the line that says
always_populate_raw_post_data = -1
This only affects the toolchain. PHP 7 does away with this property and error.
The fix is to automatically make that change to php.ini.
References: https://www.drupal.org/node/2456025#comment-9908705

This should be fixed, now that we're using PHP 7.


Language request: Google SQL

https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax
Also known as Google Standard SQL, in use in BigQuery

It seems that Google Standard SQL can be considered as an alias of MySQL. Do you find any difference in SQL syntax?

@raphaelfff I'm still looking forward to your feedback. Per my investigation, we can build Google SQL with MySQL flavor. And we can use SQL() method to build non-standard SQL syntax. If you find any difficulty to build SQL using MySQL, feel free to reopen this issue and let me know.


Check if directory exists before cloning

Can you just raise that as an issue?  I did this with a quick 10 mins of free time that I had and I'm not sure when I'll get another bit of free time to sort it out

@insacuri No worries. I already had both implemented in https://github.com/ONSdigital/rasrm-acceptance-tests/pull/49.

@jcox-dev how long is your PR going to take?  This is ready now whereas yours looks like it might take a little while and this is an issue that's a bit of a pain when setting up


Invalid request (Unsupported SSL request) on Localhost

Hi.
I just cloned this project on my own pc and then used "php spark serve" to test it.
but the problem is, whenever I try to access it through "http://localhost:8080/", it redirects me to "https://localhost:8080/" and then the browser shows "This site can’t be reached-localhost refused to connect-ERR_CONNECTION_REFUSED" and also the console keeps saying "Invalid request (Unsupported SSL request)"
I double-ckecked config files, htaccess and also php serve arguments but nothing seems wrong!
Thanks in advance for your attention.

Hi,
If you want to access without SSL, Set $forceGlobalSecureRequests = false.
https://github.com/codeigniter4projects/website/blob/855dc78202a5445c4c5f7f097a1097d323ff9c68/app/Config/App.php#L137

Hi, If you want to access without SSL, Set $forceGlobalSecureRequests = false.
https://github.com/codeigniter4projects/website/blob/855dc78202a5445c4c5f7f097a1097d323ff9c68/app/Config/App.php#L137

Tnx Man

I sent PR #387 to fix README:
https://github.com/codeigniter4projects/website/blob/bede17ba383dbbf0ea46bbc444a13a1306c6e400/README.md#installation


Make drupal build.sh optional for custom setups.

In some cases one would like to use Wundertools as a base for a project but one might not necessarily need the drupal/build.sh script - for example project might not have site.make file or it's some kind of unique setup. So how about we make the download/update optional?
Here is a patch for a start.

This is a really good point, but I think the better aproach would be to add a parameter to project.yml and then checking against that. Then there is no need to answer the prompt every time running the update.

Yes, that's even better idea. Maybe something along the lines of
buildsh:
  enabled: true
  branch: develop
  revision:

Exactly. Then you have $buildsh_enabled variable available in build.sh that you can check against.

Adjusted code accordingly.


Unit test

Use https://facebook.github.io/jest/
I have been working with it the last couple of weeks. Super simple to get going.


Add validation to getByNameLater() when the task is not known

PR: https://github.com/gradle/gradle/pull/5390
The getByNameLater API will fail if there isn't any Task created, either lazily or eagerly, before the call. Let's discuss if this is the kind of validation we want to add for this issue.

I cherry-picked this to release


[BEAM-8376] Initial version of firestore connector JavaSDK

Added initial version of firestore connector for JavaSDK.

Please note that WriteBatch is atomic transaction.
Large WriteBatch could lead to contention and high error rates.
We are working on launching a batchWrite API for non-atomic data ingestion use cases. Before it gets launched, the next best option is writing each document separately.
(BTW, we have a max 500 write per commit limit.)

Thanks @fredzqm.
@djelekar please let us know when current comments are addressed.

Any updates ?
Thanks.

Hi @chamikaramj , yes the tests are there and I addressed all your comments in code. However, I'm having issues running integration tests on my machine (windows). Once, that is working I'll bump you for one more review.
Hi @fredzqm, I understand your concerns, however, we have better experience running jobs with WriteBatch command. Namely, by doing data imports on large amounts of data, we witnessed faster processing times with WriteBatch then single writes. Can you point me to some documentation or else that aligns with your point?
Additionally, the code utilizes AdaptiveThrottler, with the max batch value of 500, so hopefully, that obeys with the limit.

Hi @djelekar, I work on the Firestore backend, and chiming in to second @fredzqm point. There are two interlocking issues when using atomic WriteBatch for large ingestion (throughput) jobs.
First, under load and based on size, Firestore will split your dataset across multiple servers. When writing atomically to multiple documents, this increase the chance that the write will need to coordinate a 2-phase commit across multiple servers, which will increase the latency of the operation.
Second, Firestore uses a pessimistic locking model under the hood. If the WriteBatch takes longer to execute (because of the issue above, or just because it is doing more work) it will be holding locks longer and disrupt unrelated read/write traffic on the document or index entries.
I can see reasons why the experience looks better with WriteBatch, for example:

when using single writes, those should be asynchronous, and can (and should) be parallelized more aggressively
if the ingestion key range is not split, or not actively accessed by other processes, there will initially be no contention and good performance with WriteBatch, however there is a limit to how much throughput you will get from them once the ingestion runs longer and ramps up to more parallelism.

Does that make sense? We are hoping to launch a dedicated feature for writing batches in a non-atomic fashion, but it is unclear at this point when this will be generally available, and as @fredzqm point out, single writes are the best option for now.

"any comment"

Hey @fredzqm @clement are there any updates regarding the mentioned non-atomic batch writing capability?

What is the state of this PR? Do you need help?

I noticed the aforementioned bulk writer feature for Firestore has been made available in some clients, such as Java and Node. Can the PR now be continued using this new API for parallelized writes?

Does the new batch writer mean we could reopen this?


Please add a mention that MemoServ is supported

Libera suports the useful MemoServ service but it is not mentioned anywhere on the homepage, so the discoverability is low.
The only way to discover the service is by encountering it on other network and then blindly trying to message MemoServ on Libera.
Are there other services that are supported but not mentioned anywhere?
Thanks.

Memo Serv is supported

But where on the website is this mentioned? Unless an user already knows MemoServ, he can not find out about Libera.chat MemoServ services.


Sentinel2 default start_date out of range

Fix for issue #9

I tried writing a good unit test for thie issue, but I was unable to find an elegant way to set the timezone of the system. You could do something like, but this only works linux:
os.environ['TZ'] = 'Europe/Amsterdam'
time.tzset()
with freezegun.freeze_time(...):
    search.sentinel2(....)


chore(master): release 1.14.0

:robot: I have created a release beep boop
1.14.0 (2023-02-21)
Features

add forgotten password feature (be97ec1)
add forgotten password feature (5420614)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/indykite/indykite-sdk-python/releases/tag/v1.14.0 :sunflower:


Audio issue

There is a glitch where after joining a lobby, all of the audio from the quest (even outside of beat saber) can be cut and to fix it you would need to restart the headset. I'm not sure how it is caused or a way to fix it properly without a headset reset.

If it requires a headset restart it's more than likely an issue on the headset end, as no mod can affect anything outside the game

Do you know a fix for it other than a restart?
On Tue, 16 Nov 2021, 17:52 EnderdracheLP, @.***> wrote:

If it requires a headset restart it's more than likely an issue on the
headset end, as no mod can affect anything outside the game
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EnderdracheLP/BeatSaberServerBrowserQuest/issues/1#issuecomment-970518844,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVCAR3SL7P54NPRGFVJJVYDUMKK6BANCNFSM5IC5CPJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Not at the moment, but I guess you could try looking up the issue with all the audio dissappearing, the last time I had that issue is a long time ago though and it only ever happened 2 times to me


Live Preview MultiBrowser does not work with local server for PHP

Hi,
When i launch a Live preview in my PHP project (don't know if other langages are concerned), Firefox (v34.0.5) open on the right page but it never refresh.
The live preview icon in brackets say : "Live Preview : Connecting..."
but never "connect"

@busykai What priority would you recommend for this issue?

@pthiess, let's give it medium priority. MultiBrowser is experimental feature still, but it is important to get it on par with the CDT-based one ASAP.


Update build to 5.0.0-beta.3

Will be paired with upcoming frigate 0.13 beta 3, which should be ready in a day or two time. I believe this can be merged now and a release done in sync with the 0.13 beta 3 release

@NickM-27 FYI: Integration release is staged and ready -- will wait for your go ahead.

Thank you :)


Gogs REST API

Hi there,
It's great that I'm able to make a POST HTTP request to the REST API that Gogs exposes to create a repository and all that, but I can't seem to find documentation on how to go about deleting a repository that was created via the same interface.
Is that just not documented? Or is it not supported via the currently exposed REST API?
Thanks a bunch!

Hmm.. all docs are here in Wiki: https://github.com/gogits/go-gogs-client/wiki

@Unknwon Thank you for the prompt reply, I appreciate it.
So, using the documentation you provided, I am able to create a repo via a POST like so:
$ curl -H 'Accept:application/json' -H 'Content-Type:application/json' -H 'Authorization: Basic bmFzczpwYXNz' -d '{"name":"SomeAmazingRepo"}' -X POST https://dev.myserver.com:10080/api/v1/user/repos
{
 "id": 20,
 "owner": {
   "id": 1,
   "username": "nass",
   "full_name": "",
   "email"<EMAIL_ADDRESS>   "avatar_url": "//1.gravatar.com/avatar/abdb83fbee6662589eae168c3f6e6669"
 },
 "full_name": "nass/SomeAmazingRepo",
 "private": false,
 "fork": false,
 "html_url": "https://dev.myserver.com:10080/nass/SomeAmazingRepo",
 "clone_url": "https://dev.myserver.com:10080/nass/someamazingrepo.git",
 "ssh_url": "ssh://git@dev.myserver.com:10022/nass/someamazingrepo.git",
 "permissions": {
   "admin": true,
   "push": true,
   "pull": true
 }
}

How do I make a REST call to delete the repo?

How do I make a REST call to delete the repo?

Not implemented yet, but I can make it :sweat_smile:

Thank you! I would appreciate that very much.
How do I make a REST call to add a user as a collaborator to my repository? Is that also not implemented?

@nasali yeah, many APIs are missing, most of implemented ones are because internally need that. And yes if you make request, will have higher priority to implement them first.

Okay, good to know that.
How do I make a request to have the complete set of CRUD operations exposed on repository, user, collaborator and org via the REST API then?

It certainly takes time, you can make an issue which contains a checklist of API endpoints you want to  https://github.com/gogits/gogs/issues

Done. https://github.com/gogits/gogs/issues/1692
Thanks again!


Capitalizations in the logs

A commit that fixes (lack of) capitalization in some of the CLI logs

hey, thanks for this PR! You have some merge conflicts -- going to close out and let you re-open later if you'd like.


Fix test main

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1318

Relevant Lines:
1699

💛  - Coveralls


Docstring text hover not properly

Does this issue occur when all extensions are disabled?: Yes

版本: 1.78.2 (user setup)
提交: b3e4e68a0bc097f0ae7907b217c1119af9e03435
日期: 2023-05-10T14:39:26.248Z
Electron: 22.5.2
Node.js: 16.17.1
OS: Windows_NT x64 10.0.19045
Steps to Reproduce:
I find that vscode hover for docstring can not properly process a long text without newline, as it will affect left-alignment of arguments below.
with newline after word "learning rate" for first argument learning_rate

without newline after word "learning rate" for first argument learning_rate

Is there any one can help to solve this?
demo code:
class SGD:
    """Stochastic Gradient Descent.

    Args:
        learning_rate (Union[float, optim.lr.LRScheduler], optional): The learning rate
            used to update parameter(s). Defaults to 0.001.
        weight_decay (Optional[Union[float, regularizer.L1Decay, regularizer.L2Decay]]):
            Regularization strategy. Defaults to None.
        grad_clip (Optional[Union[nn.ClipGradByNorm, nn.ClipGradByValue, nn.ClipGradByGlobalNorm]]):
            Gradient cliping strategy. Defaults to None.

    Examples:
        >>> import ppsci
        >>> model = ppsci.arch.MLP(("x",), ("u",), 5, 20)
        >>> opt = ppsci.optimizer.SGD(1e-3)((model,))
    """

    def __init__(
        self,
        learning_rate: Union[float, optim.lr.LRScheduler] = 0.001,
        weight_decay: Optional[
            Union[float, regularizer.L1Decay, regularizer.L2Decay]
        ] = None,
        grad_clip: Optional[
            Union[nn.ClipGradByNorm, nn.ClipGradByValue, nn.ClipGradByGlobalNorm]
        ] = None,
    ):
        self.learning_rate = learning_rate
        self.weight_decay = weight_decay
        self.grad_clip = grad_clip

/extPython

It looks like this is caused by the Python extension. Please file the issue to the Python extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


AdditionalGids must include effective group ID

cherry-pick moby commit:
https://github.com/moby/moby/commit/e44d7f735ef6e59e0a724e1920f19f288b30a331
Signed-off-by: Rudy Zhang<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

lgtm


Emulated Hue spamming logs when using non-default port

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.55.2
Python release (python3 --version):
3.6
Component/platform:
Emulated Hue
Description of problem:
After changing the default port on emulated hue to 8090, it is spamming the logs
`
Home Assistant
0.55.2
Path to configuration.yaml: /config
Developed by a bunch of awesome people.
Published under the Apache 2.0 license
Source: server — frontend-ui
Built using Python 3, Polymer 2.0.1, Icons by Google and MaterialDesignIcons.com.
The following errors have been logged this session:
2017-10-20 23:04:05 WARNING (SyncWorker_1) [homeassistant.components.emulated_hue] Alexa type is deprecated and will be removed in a future version
2017-10-20 23:04:55 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:04:55 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:04:55 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:04:55 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:04:55 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:04:55 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:04:55 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:04:55 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:04:55 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:04:55 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:06 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:06 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:06 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:06 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:06 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:06 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:06 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:06 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:06 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:06 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:16 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:16 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:16 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:16 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:16 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:16 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:16 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:16 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:16 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:16 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:26 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:26 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:26 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:26 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:26 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:26 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:26 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:26 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:26 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.
2017-10-20 23:05:26 WARNING (MainThread) [homeassistant.components.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.`
Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:

There was a recent change from using emulated_hue to emulated_hue_hidden in your customize.yaml. You need to update all of them to reflect this new naming convention. e.g.
 emulated_hue_hidden: true

I am getting this same SPAM and I have changed ALL instances of the Emulated_hue to the correct wording.  You can verify in my repo : https://github.com/CCOSTAN/Home-AssistantConfig/search?utf8=✓&q=emulated_hue%3A&type=
I don't know where else to look to resolve this issue.
Running on 0.56.2 currently on RPI.

@CCOSTAN You are still using emulated_hue in many places. You need to change all of those to emulated_hue_hidden.

@arsaboo - No.. Those top 2 packages are disabled (not yaml endings) and the 3rd one is just a text file.  I don't have any instances of emulated_hue in the yaml files..

@CCOSTAN Wondering if those files are also included. Can you comment out or change those files as well? I am not getting any more warnings.

Yes.. let me just delete them actually.

OK .. looks like this might have fixed it!  So weird.. It should have ignored it.. but the errors are gone now.  Thanks @arsaboo!

I am having the same error.  have tried everything i can think of to include uninstalling/reinstalling, replacing the 'customize.yaml' and commenting out 'emulated_hue' from my config.  The only fix was commenting 'emulated_hue' out which is obviously not the answer.  I anyone get put a second set of eyes on my yaml files to see what i am missing would be much appreciated.
running 0.56.2 on ubuntu 16.04
Thanks
P.S. This is the first time i uploaded a repo not sure it is going to the right location, when i clicked the link to confirm it is working it sends me to a 404.  Cutting and pasting the link in the address bar however works for me.  Not sure what to do for that.
https://github.com/mudfinger/HA-Config

Spoke too early.. they are back..
Oct 26 14:49:13 Carlo-Pi hass[23656]: 2017-10-26 14:49:13 WARNING (MainThread) [homeassistant.compo
nents.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hid
den' in your configuration file.
Oct 26 14:49:13 Carlo-Pi hass[23656]: 2017-10-26 14:49:13 WARNING (MainThread) [homeassistant.compo
nents.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hid
den' in your configuration file.
Oct 26 14:49:13 Carlo-Pi hass[23656]: 2017-10-26 14:49:13 WARNING (MainThread) [homeassistant.compo
nents.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hid
den' in your configuration file.
Oct 26 14:49:13 Carlo-Pi hass[23656]: 2017-10-26 14:49:13 WARNING (MainThread) [homeassistant.compo
nents.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hid
den' in your configuration file.
Oct 26 14:49:13 Carlo-Pi hass[23656]: 2017-10-26 14:49:13 WARNING (MainThread) [homeassistant.compo
nents.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hid
den' in your configuration file.
Oct 26 14:49:13 Carlo-Pi hass[23656]: 2017-10-26 14:49:13 WARNING (MainThread) [homeassistant.compo
nents.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hid
den' in your configuration file.
Oct 26 14:49:13 Carlo-Pi hass[23656]: 2017-10-26 14:49:13 WARNING (MainThread) [homeassistant.compo
nents.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hid
den' in your configuration file.
Oct 26 14:49:13 Carlo-Pi hass[23656]: 2017-10-26 14:49:13 WARNING (MainThread) [homeassistant.compo
nents.emulated_hue] 'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hid
den' in your configuration file.

This is definitely a bug in my opinion.   My repo is free of the old emulated_hue.  @arsaboo

Agreed...there is a delay between when starting HA and the messages start spamming that may lead one to believe it is working properly.
Plus i have stripped my config to the bare bones, removed all custom yaml files (replacing with blanks) and by simply adding 'emulated_hue' into the config, and that will be all that it needs to start the spam fest.
Here is the only code I added:

emulated_hue:
host_ip: <IP_ADDRESS>
expose_by_default: false
light:
platform: hue
host: <IP_ADDRESS>
allow_unreachable: true
allow_hue_groups: false
allow_in_emulated_hue: false

Unless something is conflicting between the two, idk what else it could be other than a bug.

I am having this same issue. I literally only have "emulated_hue" in only two places in my own repo. One here in my configuration.yaml file to enable it and and another here in my customize.yaml file to expose one switch.
I'm guessing that when the emulated hue component loads it is scanning all of the devices looking for "emulated_hue_hidden" and if it is not found it is incorrectly assuming that it has the deprecated value. Looks like it was PR #9382 that did it. @rbflurry want to take a look at it?

Looks like this was fixed over here. Can you confirm? https://github.com/home-assistant/home-assistant/pull/9894

Confirmed Fixed.


Bug: "the ClickLine" attribute/function should return the " of "

Currently, "the clickline" returns only the line number of the field's clicked row, not the full parent, in the form of "line 1 of <card | background> field ".
This bug can be found in the "Audio Help" stack.
It can be duplicated by writing a simple mouseUp script on a locked text field:
on mouseUp
answer the clickLine --should answer "line x of card field x"
end mouseUp

I will be working on this fix and send a PR when I am done.

Quick update. I got this functionality working. I will finish the test and the PR Friday (tomorrow for me).

I submitted a Pull Request

Sorry, it's probably me learning Github, but I can't find your review comments for the pull request on pull #113. I am looking at the Conversation tab for it and see 0 🧐
Sent from my iPhone
On May 31, 2022, at 7:41 PM, Matt DeFano @.***> wrote:

Thanks, @ooper-zzhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fooper-zz&data=05|01||0c1a7a5d50af41508f5e08da4378389f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637896480871770154|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=TSplip8Jy9%2FnUtukqlIYlbqfvI5lWFw9oWASkjWFSjM%3D&reserved=0 . I left you a review comment—I think the implementation for the clickLine can be simplified. Take a look and let me know if you disagree.
—
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdefano%2Fwyldcard%2Fissues%2F106%23issuecomment-1143056892&data=05|01||0c1a7a5d50af41508f5e08da4378389f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637896480871770154|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=VTBJE1UfFXSgPfzUG9Sqs%2FzD%2BVwXj9qynqmgsAxJPWE%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAZ473XFS6VSNTJYGSGIUQLVM3EVJANCNFSM5W3XP3UQ&data=05|01||0c1a7a5d50af41508f5e08da4378389f|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637896480871770154|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=IRDGYQARdVmL2fkhgjxjstbK3X4uAWX%2FgOMw1n5iVhY%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

Hey @defano, I'm sorry, I can't find the PR review comment and what the simplification should be :( If you could add a link to this thread, It would be great and highly appreciated. Thanks!
At any rate, I am on vacation and will be until the latter part of week of June 13.

Thanks @defano, we did!
I submitted the changes you suggested. Best approach, for sure.
Take care.

Awesome—thanks, @ooper-zz. I have merged your changes.


Broken on recent versions of discourse

This plugin is broken in recent versions (true as of 2.5.6) of discourse.
The Stacks Foundation is looking for help with updating the plugin. (https://github.com/stacksgov/Stacks-Grants/issues/29)
Related issues/info:
https://github.com/blockstack/blockstack.org/issues/392
https://github.com/blockstack/blockstack.org/issues/1159
https://github.com/blockstack/omniauth-blockstack/blob/master/lib/omniauth/strategies/blockstack.rb#L39-L42

I spent a couple hours taking a look at this today.
@wileyj writes:

Pretty sure the issue is here:
https://github.com/blockstack/omniauth-blockstack/blob/master/lib/omniauth/strategies/blockstack.rb#L39-L42

One issue is here. What's supposed to happen is when /auth/blockstack?manifest=true is fetched by the authenticator, the manifest json is returned. It appears discourse changed behavior such that it instead returns an HTML page with a button the user has to click on before the JSON is returned by the omniauth strategy. I imagine this has something to do with the discourse folks trying to address cross-site scripting, but it breaks our authentication flow.
One short-term way to work around this to put the discourse installation behind a proxy and intercept requests to /auth/blockstack?manifest=true and return the manifest json.
A longer term solution would be really digging into the internals of discourse to figure a better way to do this - there might not be away to do it in a supported fashion.
A second issue was reported by @tvr132b here: https://github.com/blockstack/blockstack.org/issues/1159#issue-687503148

This issue is with the content security policy added by discourse. You need to disable to included content security policy on discourse or add the unsafe-inline keyword (unclear how to do this in on discourse in a supported way).

hmm, the proxy idea might be the path of least resistance here.
I think we can give it a shot, and see if it works

hmm, the proxy idea might be the path of least resistance here.
I think we can give it a shot, and see if it works

Cool! Let me know how it works!

Cool! Let me know how it works!


Sibling folder strategy

Hi,
I wanted to consider files in folders named the same as a given file, so this structure:
post.html
post/image.jpg

Can turn into:
post/index.html
post/image.jpg

I've extended the functionality of linksets, if set to folder then this folder strategy is used.

Thanks for the PR.
Could you resolve the conflicts or create a new PR based off master?
Also add documentation to the readme please.

Hi @woodyrew, thanks for looking at the PR. I'll rebase my changes and force-push to this branch.
I note master is currently failing build, will this be fixed?

Hi @woodyrew,
I've updated the branch, rebased off of master. With linting disabled the tests are passing. I no longer use this library so the change is a bit theoretical at this point... we can merge or close the PR as you wish. Thanks for making the library available BTW.

Thanks for the PR. Segmentio have provided write access to the plugins to the Metalsmith community so we can move things forward now.
Fixed the build, it was due to a linting issue from a PR that was before the CI was introduced.
Fixed conflicts and merged changes into master.


Implement TaskSeq.takeUntil, takeUntilAsync, takeUntilInclusive and takeUntilInclusiveAsync

This partially fixes #130.
These are basically the counterparts to takeWhile. This implements:

takeUntil
takeUntilAsync
takeUntilInclusive
takeUntilInclusiveAsync

If both are to be retained, I wonder whether there's a way to do the tests to make it clear that one is the same as the other with a flipped condition?

Good point. I may consider updating this using such tests instead.

PS: all suggestions have been applied to #136, it was by accident that this PR included those changes as well. I will rebase.

Ok, rebased this such that it is now properly based off of main instead. See for the doc-comment changes that I applied from your review comments: #136.

Apologies for not paying attention to your responses on my comments as I made them
Sounds like we are on the same page
The final one alluding to Async.Parallel is the crux of it all
I need to be afk for most of the rest of the day now (and am travelling later this week so will have simialrly patchy responsiveness) but should hopefully be able to fit in responding to your responses and re-reviewing later on

Awesome! Much appreciated!  The main use-case would be that it isn't trivial to write takeUntil through takeWhile, and this would help users write clearer code. Another use-case would be that if takeUntil is needed and you would write takeWhile (f >> not) this would not perform as well, however that issue is not resolved here.
We can always revisit once we have sorted out the other low-hanging fruit.


Ability to select specific sound device or roll backwards

Right now we can goto the next device but I would love to be able to go backwards and/or some command to select a specific one using your same program.
Use case:
I have a keyboard with macros and have set two buttons to use your switcher but they should be able to scroll forwards and back but instead both go forward for now. Would love to make this work and maybe include a fast switch button as well.

It's easier for me to just implement a backwards selection right now, I've also thought about the device-specific shortcut idea myself for a long while now, it just needs a bit more complicated logic. I will try to get the backwards-next device selection to the next version (RC8).

also you can use command-line mode of AudioSwitch where you can specify the device either by sequence number or by device name. Just open the command prompt in AudioSwitch folder and type AudioSwitch /help


Cannot make outbound call from client to client

Description
I have installed the quickstart swift app on both my iPhone 7 and my iPad, and used different identities ("alice", and "ipad") to call from one device to another. However, I could not make any outbound call, and only received "Welcome to Twilio" message.
I have tried using both the Node.js server and the Python server. It turned out that the app was making a POST request to the root "/" instead of "/makeCall" every time I pressed the "Call" button on the app. I think the app should make a POST request to "/makeCall" but please correct me if I am wrong.
Note: I could replicate the quickstart tutorial until "Step 10. Receive an incoming call," so I believe that push notification and API Keys are set properly.
Steps to Reproduce

Install Quickstart Swift version app on two iOS devices.
Start a Node.js server with credentials.
Set the identity of an app as "alice", which is default, and the other one as "ipad".
Open the app with "alice" and type "ipad" and press "Call."

Code
let accessTokenEndpoint = "/accessToken"
let identity = "ipad" // this could be alice on another device
let twimlParamTo = "to"

func performVoiceCall(uuid: UUID, client: String?, completionHandler: @escaping (Bool) -> Void) {
      guard let accessToken = fetchAccessToken() else {
          completionHandler(false)
          return
      }

      let connectOptions = ConnectOptions(accessToken: accessToken) { builder in
          builder.params = [twimlParamTo: self.outgoingValue.text ?? ""]
          builder.uuid = uuid
      }

      let call = TwilioVoiceSDK.connect(options: connectOptions, delegate: self)
      activeCall = call
      activeCalls[call.uuid!.uuidString] = call
      callKitCompletionCallback = completionHandler
  }

I am suspecting that this part of the code is making a POST request to "{server url}/" instead of "{server url}/makeCall"
// This is called every time instead of /makeCall
app.post('/', function(request, response) {
  response.send(welcome());
});

app.post('/makeCall', function(request, response) {
  makeCall(request, response);
});

Expected Behavior
The device with the identity "ipad" receives an incoming call.
Actual Behavior
The device with the identity "ipad" does not receive any incoming call. Rather, the device with the identity "alice" receives the message that says "Welcome to Twilio".
Reproduces How Often
100% of the time.
Twilio Call SID(s)
Account SID: AC13a6c72c3c7173ca7c8586a3a5e29cf0
Logs
2021-01-24 17:25:59.541901+0900 SwiftVoiceQuickstart[3144:99707] StartCallAction transaction request successful
2021-01-24 17:25:59.556785+0900 SwiftVoiceQuickstart[3144:96157] provider:performStartCallAction:
2021-01-24 17:26:01.582600+0900 SwiftVoiceQuickstart[3144:96157] provider:didActivateAudioSession:
2021-01-24 17:26:02.976376+0900 SwiftVoiceQuickstart[3144:96157] callDidConnect:
2021-01-24 17:26:02.976566+0900 SwiftVoiceQuickstart[3144:96157] performVoiceCall() successful
2021-01-24 17:26:03.012683+0900 SwiftVoiceQuickstart[3144:96157] AVAudioSession setAggregatedIOPreference:error: Error Domain=NSOSStatusErrorDomain Code=560030580 "(null)"
2021-01-24 17:26:12.745419+0900 SwiftVoiceQuickstart[3144:96157] Call disconnected
2021-01-24 17:26:13.726699+0900 SwiftVoiceQuickstart[3144:96157] provider:didDeactivateAudioSession:

Versions
TwilioVoice version: 6.1.0
Voice iOS SDK
11.0 via CocoaPods
Xcode
12.3
iOS Version
14.3
iOS Device
iPhone 7 and iPad Air 2

Hi @yabutaka
Thanks for reaching out.
For your use case, /makeCall is the correct app endpoint. For this example endpoint, the to parameter will determine which TwiML verb will used in the response: https://github.com/twilio/voice-quickstart-server-python/blob/master/server.py#L98
In case you are still getting trouble connecting the caller and callee, you can provide us Twilio Call SIDs so we can check the details of the call.

Hi @yabutaka
Thanks for reaching out.
For your use case, /makeCall is the correct app endpoint. For this example endpoint, the to parameter will determine which TwiML verb will used in the response: https://github.com/twilio/voice-quickstart-server-python/blob/master/server.py#L98
In case you are still getting trouble connecting the caller and callee, you can provide us Twilio Call SIDs so we can check the details of the call.

Hi @bobiechen-twilio
Thank you for your clarification. I have been looking into this issue a while now, and I have found that the iOS SDK tries to connect to "{server url}/" instead of "{server url}/makeCall" when I press the "Call" button. I actually changed the function inside the Node.js server as shown below.
// This is the original code. You will get "Welcome to Twilio" message.
app.post('/', function(request, response) {
  response.send(welcome());
});

// I changed the code to the makeCall funcriton as the following.
app.post('/', function(request, response) {
  makeCall(request, response);
});

When I changed the code to makeCall function, pressing the "Call" button did in fact enabled outbound call from the original phone to the target phone. So, based on this situation, I think the issue is that iOS SDK or sample code tries to connect to the root while it should have been sending a request to the "{server url}/makeCall" endpoint. Is there any way of changing the endpoint that the iOS sample code makes a request for? Could you tell me if there is anything I can do to change this behavior?
Successful Call ID: CAdc2cfc1be6a2023098022b519f50dc84

Hi @bobiechen-twilio
Thank you for your clarification. I have been looking into this issue a while now, and I have found that the iOS SDK tries to connect to "{server url}/" instead of "{server url}/makeCall" when I press the "Call" button. I actually changed the function inside the Node.js server as shown below.
// This is the original code. You will get "Welcome to Twilio" message.
app.post('/', function(request, response) {
  response.send(welcome());
});

// I changed the code to the makeCall funcriton as the following.
app.post('/', function(request, response) {
  makeCall(request, response);
});

When I changed the code to makeCall function, pressing the "Call" button did in fact enabled outbound call from the original phone to the target phone. So, based on this situation, I think the issue is that iOS SDK or sample code tries to connect to the root while it should have been sending a request to the "{server url}/makeCall" endpoint. Is there any way of changing the endpoint that the iOS sample code makes a request for? Could you tell me if there is anything I can do to change this behavior?
Successful Call ID: CAdc2cfc1be6a2023098022b519f50dc84

Thanks for the update @yabutaka.
The call routing logic is determined by the endpoint specified in the TwiML application.
From the mobile client standpoint, it will try to connect to a TwiML application - the endpoint URL that you specify in the voice incoming call handler of your Twilio number. This is the place where you specify which server endpoint, /makeCall or /placeCall, works best for your application logic. The application will then use the Application SID in the access token for making outbound calls.
I am closing the ticket for now since the original issue seems to be resolved, but please feel free to reach out.
Cheers,
-bobie


Update meta.json

The original image used in the #GOOSE community collection’s #logo is relatively large and cannot be displayed! So I re-engraved a 400*400 one, which has been updated. Please help me merge it, thank you~~

Hello, please modify my pull request. My LOGO uses an engraving ID of 400*400.
Another thing is: Can the pictures of the #fractal #GOOSE collection be displayed like the #BTC mainnet? Please help me adjust it to the appropriate proportion on the front end, thank you~~
Here’s a comparison between #BTC and #FRACTAL

Our dev fixed it. Please have a check. @fackjack001

Looks good now.
thank you
cloud6605 @.***>于2024年10月23日 周三下午12:57写道：

Merged #674
https://github.com/unisat-wallet/fractal-ordinals-collections/pull/674
into main.
—
Reply to this email directly, view it on GitHub
https://github.com/unisat-wallet/fractal-ordinals-collections/pull/674#event-14800649099,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDCVHPCYFVO4OPPHF64EER3Z44UBXAVCNFSM6AAAAABQJSH6WKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUHAYDANRUHEYDSOI
.
You are receiving this because you were mentioned.Message ID:
<unisat-wallet/fractal-ordinals-collections/pull/674/issue_event/14800649099
@github.com>

Let me reiterate that there is no project party for this project, only the
community! Our community is the first to publish this index! Since his
pictures that did not meet the specifications were not included, he
obstructed them in every possible way! In the end, you actually let a
pirated version be included in your collection. Where is the authenticity
and fairness?
#goose There is only the community, not the project party. The person who
claims to be the project party is a liar! Hey~~~
Shaniqua Tlucek @.***>于2024年10月23日 周三下午1:25写道：

Looks good now.
thank you
cloud6605 @.***>于2024年10月23日 周三下午12:57写道：

Merged #674
https://github.com/unisat-wallet/fractal-ordinals-collections/pull/674
into main.
—
Reply to this email directly, view it on GitHub
https://github.com/unisat-wallet/fractal-ordinals-collections/pull/674#event-14800649099,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDCVHPCYFVO4OPPHF64EER3Z44UBXAVCNFSM6AAAAABQJSH6WKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUHAYDANRUHEYDSOI
.
You are receiving this because you were mentioned.Message ID:
<unisat-wallet/fractal-ordinals-collections/pull/674/issue_event/14800649099
@github.com>


Crash in libavcodec-amplituda.so

Describe the bug
I have a chash, when I generate wave:
Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x3c in tid 3546 (DefaultDispatch), pid 3481 xxxx
crash_dump64                         A      #01 pc<PHONE_NUMBER>070df4  /data/app/com.xxxx.android-R6ols2eWjmjo4OxXw7PH2Q==/lib/arm64/libavcodec-amplituda.so
To Reproduce
My code abowe:
waveSeekBar.setSampleFrom(file)
Smartphone (please complete the following information):
Huawey p10, android 9
Samsung A52, android 13

Up

Any solution you found for this. Also facing kind of same crash

I think the crash happened because I ran 'waveSeekBar.setSampleFrom(file)' from different threads simultaneously. I created a queue, and now it doesn't repeat the issue.


Option to switch to JPG instead of PNG

Would it be possible to add an option to save screenshots as JPG's instead of PNG's? What advantage does PNG screenshot have over JPG?
Thanks.

JPG is a 'Lossy' image format, so you can't get a perfect representation on the UI under test.  Compression artefacts may also make image comparison less reliable.


Add PARETO

Insert URLs to the project here:
https://github.com/project-pareto/project-pareto

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as 'Good First Issue' of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.

@melody-shellman @Andresj89 @tarnold17

@melody-shellman @Andresj89 @tarnold17

@Ly0n Thanks for this! I was unaware of your list until now. One project which I do not see included on the list that you might be interested in is DISPATCHES (https://github.com/gmlc-dispatches/dispatches).

@tarnold17  Many people are involved in this projects from the beginning. I'm just the guy who did not stop working on it ;). DISPATCHES is an great hint. Thanks :+1:


Wrong public path

Hi, I think I found a bug. In my project I changed a name of public directory via nuxt.config dir.public to Public and I see that build process do not take into that name. As a result, the font file is missing in the build

fixed in 1.1.0
https://github.com/coremyslo/nuxt-icon-font/pull/10


Parameter isn't recognized in a filter using the language function

When a filter that uses the LANG function is used in a query grlc doesn't recognize the parameter in that line (example).
The same query does work when there isn't a filter with the language function (example), or when the language tag in the function is not a variable (example).

It seems like the issue is that (according to rdflib) in this query:
PREFIX prov: <http://www.w3.org/ns/prov#>
PREFIX schema: <http://schema.org/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX hisco-code: <https://iisg.amsterdam/resource/hisco/code/hisco/>

SELECT ?names ?code WHERE {
  ?s schema:occupationalCategory ?category .
  ?category schema:codeValue ?code .
  ?s schema:name ?names .
  FILTER(LANG(?names) = ?_lan).
  FILTER(regex(?names, ?_name, "i")).
}
ORDER BY ASC(?names)
LIMIT 1```
`?_lan` is not a variable, and grlc tries to replace variable in the query.

The following query, should allow for `?_lan` to be a variable

```SPARQL
PREFIX prov: <http://www.w3.org/ns/prov#>
PREFIX schema: <http://schema.org/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX hisco-code: <https://iisg.amsterdam/resource/hisco/code/hisco/>

SELECT ?names ?code WHERE {
  ?s schema:occupationalCategory ?category .
  ?category schema:codeValue ?code .
  ?s schema:name ?names .
  ?_lan a rdfs:Literal.
  FILTER(LANG(?names) = ?_lan).
  FILTER(regex(?names, ?_name, "i")).
}
ORDER BY ASC(?names)
LIMIT 1

and because a language should always be a rdfs:Literal this should work.
If this works for you, we can close this issue.

Closing this issue. If the proposed solution does not work, please re-open it.


Added leet HelloThere

Happy 40th Birthday, Tarah.

Please note there's an authors.txt file you may wish to add your name to now! :-)


Add Password Policy and audit log overlays as configurable items

Add ppolicy and auditlog overlays as configurable options. Tested on CentOS 7.
The defaults behaviour should not have changed.

This is a great contribution but given some major changes to the cookbook and that parts of the PR don't account for various platforms I'm closing this but would love to see a new PR if still interested in this functionality.


[Question] Has any cloud provider been formed based on the Harvester?

As I am developing a business model to launch a cloud company based on Harvester, I need to get benchmarks from businesses that provide services on Harvester. Have any harvester-based cloud service providers yet been established? I would appreciate it if you could introduce those startups/companies if there are any.

Hi @perpi ,
Since Harvester just reached GA in December last year, it's still relatively new. We haven't seen much Harvester-based cloud provider service yet.
But we do think this is a potential opportunity there, especially if the target user group is Kubernetes users.
If you have any questions, feel free to let us know.

Hey.

especially if the target user group is Kubernetes users

Um, I'm working on a IaaS business for the demands of cloud servers! Why Kubernetes users since Kubevirt is a tool for creating virtual machines?

#Up

especially if the target user group is Kubernetes users

Would you please explain more or link me to a reference?


Degree symbol by key 'd'

What is your problem
I want to type degree symbol using 'd'
Describe the solution you'd like
When d key, show degree symbol—°

Maybe better to attach to either the zero or asterisk keys, as "degree" in other languages does not necessarily begin with a 'd'?


Enhance SQL logging including time to run queries

Same LOG_SQL config var controls this option - but now includes time to run queries and uses cleaner interface.

Hello @pbugni! Thanks for submitting the PR.

In the file portal/sql_logging.py, following are the PEP8 issues :

Line 16:25: E128 continuation line under-indented for visual indent
Line 25:25: E128 continuation line under-indented for visual indent
Line 31:1: W391 blank line at end of file


Kitematic browser link

It would be nice to have a Kitematic protocol that could reference a docker image and automatically start Kitematic and run that container.
My use case is a place like Docker Hub; search for a container you want, click a, "Launch with Kitematic" link and have a container launch in Kitematic.

+1


feat: add ability to use repo url in quay binding without https

Signed-off-by: Pavol Baran<EMAIL_ADDRESS>What does this PR do?
When a user created token binding for quay and specified repoUrl in format: quay.io/namespace/repo instead of https://quay.io/namespace/repo the binding would fail to recognize the service provider.
This PR fixes this problem.
Screenshot/screencast of this PR

What issues does this PR fix or reference?

solves https://issues.redhat.com/browse/SVPI-109
How to test this PR?

To test locally on minikube (with ingress adon):

deploy operator with changes; wait for all components to be running
make deploy_minikube SPIO_IMG=quay.io/pbaran/spio:SVPI-109-QUAY

create a token binding that uses repo url in the format: quay.io/namespace/repo
kubectl apply -f samples/binding-quay-without-protocol.yaml

check that the binding has a linked access token in status
TOKEN=$(kubectl get spiaccesstokenbindings test-binding-quay-without-protocol -o=jsonpath='{.status.linkedAccessTokenName}') && echo $TOKEN

check that the access token has labels for service provider: quay
kubectl describe spiaccesstoken $TOKEN

can we have test for this?


fix: tutorial typo

No big deal, but I pasted this typo in my shell by mistake and it could have installed a fake package or something

Nice catch! Thanks 👍


Switch to UTF-8 input on Windows

Get rid of this whole workaround:
https://github.com/vezel-dev/cathode/blob/5f6d532af5848b1572766a345bd33a2c9d5b825b/src/core/Terminals/Windows/WindowsTerminalReader.cs#L50-L129
There should be no functional change; this is just cleanup. Maybe some slight performance gains at best.

Some context:

microsoft/terminal#4551
microsoft/terminal#7777
microsoft/terminal#11956

Looks like there is interesting progress happening on this: https://github.com/microsoft/terminal/pull/14745

Note to self: Need to investigate how well UTF-8 input works on the latest Windows Terminal version. If it mostly Just Works, then we should switch to using it (and it'll be yet another strong argument for #102).

Need to investigate how well UTF-8 input works on the latest Windows Terminal version.

Quite well, as it turns out! 🏴☠ (4 code points) roundtrips as it should both with UTF-16 input (status quo) and UTF-8 input (with the ReadConsoleW workaround removed).
However, in cmd.exe, it only roundtrips with UTF-16 input. So, this really comes down to #102.


Use only stable channel + flow diagram update

Follow-up of https://github.com/openshift/external-dns-operator/pull/146.  This PR aims at finishing the migration to v1beta1 API version but letting only the stable channel include it.
Plus a small bonus of the flow diagram which was out dated since the migration to the single namespace.

The channel changes look fine.  I have a some comments about the updated diagram in docs/images/external-dns-flow-openshift.png:

The CRs in the green boxes are truncated at the bottom.
The meaning of the diamond shapes is unclear.  You have two CRs named "one" and "two", and then two diamonds labeled "external-dns-one" and "external-dns-two"; do these represent deployments, or just abstract external-dns instances?
What's up with the AWS logo in the box for the hosted zone and the icons for Azure and GCP off to the side?  We want to indicate that the hosted zone could be configured using any one of these providers, right?  Could we put the provider icons together (in the hosted-zone box, on the edges between external-dns and the hosted zone, or just off to the side) to indicate that they represent alternatives and that no one of them is special?

Thanks for the review @Miciah !

CR truncation is fixed
Yes, it was from draw.io Kubernetes specific charts and yes it meant a deployment. I put Deployment word to make this clear.
Yeah, the idea was to show different options for the DNS provider. I put they side by side with Infoblox logo as well. Let me know if you have a better idea.

Quota problem on GCP.
compute.googleapis.com/n2_cpus is not available in us-central1 because the required number of resources (12) is more than remaining quota of 4
/retest

/retest

/retest

Thanks!
/lgtm

/hold
Stop the robot, GCP quota issue is ongoing

/unhold

/retest

/retest

/retest

/label docs-approved
/label px-approved
/label qe-approved


package.json: Add engines.node field to ensure the node.js version >=10

The requirement of NodeJS >=10 from the README only applies to our test suite and tooling. Prism itself works all the way down to NodeJS >=6. We just can't test that because our tests don't run.

Thansks, I see. So do we need to change it to NodeJS >= 6?

Thank you for contributing @shfshanyue!


hetznerHEAD: init at 0.9pre20221026.

0.8.3 is out of date, in particular it does not support rescue mode with SSH keys specified.
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@shlevy: Hm, maybe I really should do a new release. I'm currently on the road, but can do that on Tuesday.

@aszlig Cool, works for me!

I haven't forgotten about this, but I've fallen ill and am on the mend.


fixed go.mod module lib -> github.com/getbrevo/brevo-go

error:
go<EMAIL_ADDRESS>parsing go.mod:
module declares its path as: lib
but was required as: github.com/getbrevo/brevo-go

thanks for doing this. I had the same error. how can I bypass this in the meantime?

@getbrevo @ekta-slit@jain-raunak
can we look into this pls?


Don't drop unreduced variables

[x] Closes #5368
[x] Tests added
[x] Passes pre-commit run --all-files
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst

Reduce methods such as mean drop non-numeric variables. However, there's no need to drop variables that are not actually reduced (i.e., when "reduce_dim" not in da.dims).
cc: @rcaneill

Great! Thanks @malmans2 !

I'll leave this open for a day or so, as this is the sort of area where I'm going to miss some intricacy that someone else is familiar with.

@malmans2 would you like to add a whatsnew?

@malmans2 thank you and please feel free to add a whatsnew in another PR!


I found these potential error(s) in the commit data for (i.e. https://github.com/octocat/Spoon-Knife/commit/d0dd1f61b33d64e29d8bc1372a94ef6a2fee76a9):

I found these potential error(s) in the commit data for (i.e. https://github.com/octocat/Spoon-Knife/commit/d0dd1f61b33d64e29d8bc1372a94ef6a2fee76a9):require "scientist"

I found these potential error(s) in the commit data for (i.e. octocat/Spoon-Knife@d0dd1f61b33d64e29d8bc1372a94ef6a2fee76a9):require:require) "scientist"


Allow nesting under standalone question/answer

It almost works, I just need to strip the delimiter from the header.

Another thing that does not work: The "Rot / Phagocytose"  card is not created.


Improve story poster image fallback

Feature Description
When users don't add a story cover image (poster image), we use the following image as a fallback:
https://github.com/google/web-stories-wp/blob/7fc1c9af6a1e43c0edc2ec57a45f82eccb1d8d08/assets/images/fallback-poster.jpg
This is basically a last resort to ensure the image meets the poster requirements.
~However, the image is too small, and doesn't meet the requirements anymore. Search requires at least 1200px wide images, and AMP changed its requirements too, see #3297. So we'd need to update that poster.~ -> covered by ##3839
There are two steps to improve this:
First, the pre-publish checklist can provide guidance to ensure users add a cover image.
Second, and as discussed below, we can automatically create a poster by using something like html2canvas to take a "screenshot" of the first story page. The exact UX for this is TBD.
Alternatives Considered
Stop providing a fallback, causing this to be flagged in Search Console. (not good)
Additional Context

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

This may need to be broken up to address the two issues:

fallback image is not the right size
fallback is bad image and can be improved.

@o-fernandez please confirm if this ticket (regarding improvment) is needed for stable release

An idea discussed in sprint planning, was if a user do not select a poster image, we generate one for you. Similar to how video poster image works currently. Basically take a snapshot of the first page of the story and save it as an image, then set it as the poster image.
Not sure what this should look like for the user. Maybe a nag in the checklist.
"It appears that you did not upload an a poster image. Poster images are requires"
<button>Upload custom poster</button>
<button>Generate from first page of story</button>

Or if it should just do this for you automatically if a poster is not set.
I would love feedback from @o-fernandez and @samitron7 on this idea, as is a product spec change and needs UX.

^ Above would be in-line with guidelines too:

The poster image should be representative of the entire AMP story.
The poster image should be visible to the user when the AMP story begins.

The poster image is the first thing viewers sees on any surface so we should probably not even allow publishing without it. A story without a cover looks very broken and unprofessional for the creator and the surface it's represented on.

Nobody is saying otherwise.
But instead of having the user open Photoshop to create a cover image that follows best practices, or having them take a screenshot of the first page that also meets the guidelines, we can just create a poster for them.

Yes, was just replying to the alternative consideration "Should we make the poster image mandatory before publishing?". Was a bit confused by that.
@spacedmonkey Let's automatically generate one for the users (+1 to your recommendations here) and they can change if they like.  We can flag as guidance in the pre-publish list and I'll need to think about whether or not we need additional buttons with the message. This will depend on how I build the pre-publish list.

I think we should close this ticket and create a new ticket, that is assigned to the workspace pod.
My recommendation would be if a user tries to publish the story without a poster only then it generates this poster.

Yes, we should definitely do this. @swissspidy and @spacedmonkey is this something you can work on without a product brief/spec, or would you wait until we can provide one? LMK and I'll try to prioritize as necessary.

@o-fernandez Yeah this can be easily added behind a flag without requiring a brief or UX. Just noting that it's more fitting for the workspace pod' as it's not really a WordPress-related feature. Happy to consult on it though, or plan it for one of our next sprints if we do have some capacity left.

Makes sense - let me just put it under ready for sprint and we can all collaborate on the solution once it's being picked up. This is pretty important for launch, so will keep as a 1.0 Stable requirement for now.

This was flagged as a potential 1.0 launch blocker, let's discuss if there's a quick solution for it. Adding back to 1.0 Stable scope.

@carlos-kelly to connect with @swissspidy and confirm on how to address this.

@carlos-kelly, can you make sure to link the PR for this one? I can't (easily) find it.

@barklund Linked PR #4350 correctly 👍

This needs more work. Currently, it's not generating a good cover image at all. Let's consider options and get some workable solution in for Stable.
In addition, we should ensure that the cover image is autogenerated upon publishing if there is no cover image set. Right now, I don't see that happening.

Made non-blocking for RC1, even though it's a shame not to have this working. Will start a thread to get something in for the Stable release.

Thoughts to unblock stable -- let's make this a very simple solution. As mentioned above:

Best case scenario, the user sets a cover image themselves that follows our cover image guidelines.
If the user doesn't set a cover image, we autogenerate one and set it automatically at publish time.

Generation options:

If the first page of the story has a bg image or video, use an appropriately cropped version of that as the poster/cover image.
If the first page doesn't have a bg image/video, find the first image/video in the story (Starting in page 1) and use that instead. In the case that there are multiple media elements on the first page with media, use the "largest" one based on area it takes on that page in the canvas.

EXCEPTION: if the image/media resolution is low enough that the cover image would not meet minimum dimensions (at least 640 x 853) we should skip that and find another one.
This is not a great solution, but it's better than the current situation in which there's no poster/cover image set at all.

Yeah that looks right to me @o-fernandez. In the case where the story has no image/video, can we generate a default? This is better than no image.

In the case where the story has no image/video, can we generate a default? This is better than no image.

Our very last resort in case there is absolutely no poster is currently this one:

Feedback from weekly review: prefer block publishing vs. using a placeholder poster (in the last resort case where the story has no images/videos).
Since we want to avoid blocking publishing due to story guidelines in general (e.g. missing title), let's actually remove the fallback image and let the story have no poster (become invalid). This will avoid ugly stories showing up on surfaces we care about.
Ditto re: missing title.

@choumx Is this specifically referring to https://github.com/google/web-stories-wp/issues/3671#issuecomment-690584619 above? If there are some images we could use for the poster, we should try to use that still, correct?

We might want to split this ticket up:

One ticket for removing the existing fallback (use this one?)
One ticket for encouraging users to add a cover image (new one)

Yes, this ticket is just for "remove fallback", don't use a fallback any longer.
For encouraging users to add a cover image, that should be covered by #78, so hopefully we prioritize that.

We will need detailed testing instructions for this as it's quite complex.

We will need detailed testing instructions for this as it's quite complex.

It's actually quite simple to test 🙂
Testing instructions added to #4480

FYI: AMP plugin v2.0.2 has been released which facilitates Web Stories being served as without the poster-portrait-src while also omitting the amp attribute to prevent GSC from complaining about known invalid AMP documents. For relevant change, see https://github.com/ampproject/amp-wp/pull/5388.


Refs #29280 -- Moved release note about transaction_mode to "Database backends" section.

Thank you!


"FutureWarning: Possible nested set" not treated as warning

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2022.11.11 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
Related to: https://github.com/yt-dlp/yt-dlp/issues/5749
The FutureWarning from jsinterp.py is not treated as a warning. It is printed when --no-warnings parameter is given and it's printed to stderr.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
>yt-dlp -vU --no-warnings --skip-download -- jzRrUPQgrpc
[debug] Command-line config: ['-vU', '--no-warnings', '--skip-download', '--', 'jzRrUPQgrpc']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.11.11 [8b64402] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 5.1.2-full_build-www.gyan.dev (setts), ffprobe 5.1.2-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4
[debug] Proxy map: {}
[debug] Loaded 1723 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.11.11, Current version: 2022.11.11
yt-dlp is up to date (2022.11.11)
[debug] [youtube] Extracting URL: jzRrUPQgrpc
[youtube] jzRrUPQgrpc: Downloading webpage
[youtube] jzRrUPQgrpc: Downloading android player API JSON
[debug] Loading youtube-nsig.e96685ea from cache
yt_dlp\jsinterp.py:346: FutureWarning: Possible nested set at position 1
[debug] [youtube] Decrypted nsig tUD2xVWMYRhcAXPrz => tOO7XgR6I0kELg
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] jzRrUPQgrpc: Downloading 1 format(s): 315+251

>yt-dlp --no-warnings --skip-download -- jzRrUPQgrpc 2>&1 1>nul
yt_dlp\jsinterp.py:346: FutureWarning: Possible nested set at position 1

This warning is coming directly from the Python interpreter instead of yt-dlp, so it cannot be suppressed by --no-warnings. See #5749 for more information
The cause of this warning was fixed in b44cd29851fdc2fadb283adb59a074f89a27ba7e. You could wait for the next release, use the master branch or try the unofficial daily builds
Closing as duplicate


equals example is dangerous and confusing

As you know, most modern programming languages contain at least two and sometimes three equals operators. This is because value equality and identity comparison are type specific and open up a whole can of worms.
It therefore surprised me when you suggested defining equals as:
let equals = fn(a, b) {
  let x = a >= b;
  let y = lazy b >= a;
  return x && y;
}

This seems to over-complicate the issue by either assuming generics or duck typing? Generics are scary!
 Someone died once due to buying cheep generic medicine online!

PS: Why is y lazy?


chore: implementing TW's feedback in the comments in Compute Samples

I agree with all Amanda's proposals.

Updated per your recommendations.

Failures are unrelated and being tracked:

#1311 for SQL
#1272 for Storage

Force merging.


Bump version 4.9.2

Description
This pull request bumps Wazuh version to 4.9.2 revision 00 to add support to the new version.
Issues Resolved
#293
Changelog

Check List

[x] All tests pass

[x] yarn test:jest
[ ] yarn test:jest_integration

[ ] Update CHANGELOG.md
[x] Commits are signed per the DCO using --signoff

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (4.9.2@7202d7f). Learn more about missing BASE report.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##             4.9.2     #294   +/-   ##
========================================
  Coverage         ?   31.31%
========================================
  Files            ?     2211
  Lines            ?    44413
  Branches         ?     6871
========================================
  Hits             ?    13909
  Misses           ?    29884
  Partials         ?      620

Flag
Coverage Δ

Linux_1
31.31% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


[SPARK-46480][CORE][SQL] Fix NPE when table cache task attempt

What changes were proposed in this pull request?

This pr adds a check: we only mark the cached partition is materialized if the task is not failed and not interrupted. And adds a new method isFailed in TaskContext.
Why are the changes needed?

Before this pr, when do cache, task failure can cause NPE in other tasks
java.lang.NullPointerException
	at java.nio.ByteBuffer.wrap(ByteBuffer.java:396)
	at org.apache.spark.sql.catalyst.expressions.GeneratedClass$SpecificColumnarIterator.accessors1$(Unknown Source)
	at org.apache.spark.sql.catalyst.expressions.GeneratedClass$SpecificColumnarIterator.hasNext(Unknown Source)
	at scala.collection.Iterator$$anon$10.hasNext(Iterator.scala:458)
	at org.apache.spark.shuffle.sort.BypassMergeSortShuffleWriter.write(BypassMergeSortShuffleWriter.java:155)
	at org.apache.spark.shuffle.ShuffleWriteProcessor.write(ShuffleWriteProcessor.scala:59)
	at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:99)
	at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:52)
	at org.apache.spark.scheduler.Task.run(Task.scala:131)
	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:497)

Does this PR introduce any user-facing change?

yes, it's a bug fix
How was this patch tested?

add test
Was this patch authored or co-authored using generative AI tooling?

no

cc @cloud-fan @yaooqinn

which variable can be null?

@cloud-fan according to the stack,the DefaultCachedBatch.buffers[i] is null.

@mridulm yes, to make sure the cached rdd is materialized after all the tasks are succeeded

Thanks, merged to master according to the affect versions in JIRA

@yaooqinn There are some conflicts. I created https://github.com/apache/spark/pull/44457 for branch-3.5


Will Waveshare Game Hat with Pi Zero/Pi 3A+ compatible with McAirpos?

I want to build my game control with Waveshare Game Hat , but I am not sure the contoller or the display compatible with McAirpos.
Another question is about the performance, will Pi zero run majority program smoothly?
How long will it take to startup the OS(I am new in Pi)?
Thanks.
Eric

Hi Eric,
Thanks for trying out McAirpos and reaching out!

I want to build my game control with Waveshare Game Hat , but I am not sure the contoller or the display compatible with McAirpos.

I am not sure if the Waveshare Game Hat would work with McAirpos, and, sadly, no way to test it my self at home. But if the controller has a pretty standard driver and a USB interface, or GPIO/HAT interface, there is a good chance it will work, at least with manual configuration of the key mappings. In any case, it would be nice if you tried and shared your settings here. I will try to help the best I can, but might take a while between answers now that summer vacation is getting closer, with the usual rush just before, and planning going offline during.

Another question is about the performance, will Pi zero run majority program smoothly?

The Pi zero is in my experience capable to run most MakeCode Arcade games as Linux .elf executables quite smoothly. For other emulators, your mileage may vary and you reach max performance quite quickly for the "newer" retro game systems.

How long will it take to startup the OS(I am new in Pi)?

Depends on your distro. I currently have a RetroFlag GPi with a RPi Zero v1 running RetroPie with a lot of games, where especially EmulationStation brings the total boot time up to about 2 minutes. With less games and slimmer distros, it will boot much faster, and of course the RPi Zero v2, is a whole other beast, much faster, comparable to the RPi 3B, if I remember correctly.

Thanks.
Eric

Good luck!

Hi Vegz78,
Thank you for your help!
I want to know if RPiZero 2/2W are compatiable with McAirpos except little bugs?
BTW, i am new with RPi, if some app like McAirpos, will it make big different(bugs) between Zero/Zero2 and Zero W/Zero2 W.
That means, if Zero can run smoothly, then the Zero W will run smoothly, too. Am I right?
Thanks
Eric

Hardware-wise, all Pi Zero and Zero W and Zero 2 and Zero 2W should run fine with MakeCode Arcade games, both good enough, but 2/2W less chance of lags/slowdowns.
Regressions that occur since this worked fine, if any, are more likely due to recently changes in ARM Linux which are not adressed by MakeCode or newer changes in MakeCode which do not consider Linux ARM.
Mvh
Vegard

jun. 2023 kl. 04:10 skrev ericwen888 @.***>:

Hi Vegz78,
Thank you for your help!
I want to know if RPiZero 2/2W are compatiable with McAirpos except little bugs?
BTW, i am new with RPi, if some app like McAirpos, will it make big different(bugs) between Zero/Zero2 and Zero W/Zero2 W.
That means, if Zero can run smoothly, then the Zero W will run smoothly, too. Am I right?
Thanks
Eric
—
Reply to this email directly, view it on GitHubhttps://github.com/Vegz78/McAirpos/issues/48#issuecomment-1592234865, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALWCWWJF4H7JQMCFHFJFF53XLJVKVANCNFSM6AAAAAAZF3DGPY.
You are receiving this because you commented.Message ID: @.***>

Hi @ericwen888,
Any news on how this worked out for you with the Waveshare Game Hat and different RPi models?