Support for Postgresql

Postgresql is also a very common engine used together with Ruby on Rails.
Implement Postgresql instrumentation similar to the one for Mysql.
BTW, wouldn't it be easier to create instrumentation for ActiveRecord and Sequel than for each database or that would not give enough information?

BTW, wouldn't it be easier to create instrumentation for ActiveRecord and Sequel than for each database or that would not give enough information?

It would, but it would miss calls that don't use an ORM.

When I use rack mini profiler, I changed it  to focus on ActiveSupport notifications. Calls that do not fetch rails objects (e.g.: pluck, count, min, max) tend to not be represented well - specifically pluck not having a row_count.
But I found ActiveSupport notifications, even with that caveat, worked better for my needs and covered a majority of the use cases.
It may be possible to leverage knowledge from the monkey patches used by rack mini profiler, app profiler, bullet, or the myriad of other gems that have profiled database interactions over the years. for sure, they will highlight the difference between mysql, postgres, and other database drivers (mongo, redis?).

Hi @kbrock, I am currently working on a task that involves comparing the traces captured between ActiveRecord instrumentation and PG instrumentation. Debating as to whether the transition from the former to the latter would be worth the effort.
I would love to know more about what you may have uncovered using your profiler (and other gems), if you don't mind sharing. Thanks!

Hi @theabhishekg
(sorry, just found a tab open with this comment in it)
I use https://github.com/MiniProfiler/rack-mini-profiler in development, but I believe discord uses that in production. It is backed by some pretty strong names (Sam was a ruby fellow) and there is even a rails cast from 2012.
If you note [sql_patches.rb](https://github.com/MiniProfiler/rack-mini-profiler/blob/f20c4c6315bcd5bbfba234fc0a65edbf30d7c165/lib/patches/sql_patches.rb#L30-L47], there are a few patching options.
They use patch_rails? to choose ActiveSupport::Notifications vs monkey patching the rails classes themselves. Quite a few years ago, New Relic rpm transitioned from patching rails directly to using notifications. I think close to when the notification framework came out. I'd even like to say there was some collaboration on that one, but that may have been my misunderstanding. Rack mini profiler has been slower to the transition away from monkey patching.
Let me know if the patch link is not crystal clear.
Keenan
Tangent:
Also, you may want to keep an eye on https://github.com/jhawthorn/vernier
Aaron paterson demoed this at Rails World 2023 https://youtu.be/GnqRMQ0iQTg?si=Mq4hYX4VmkX0EYIV&t=1228


Support credentials for PSGalleryModule and PSGalleryNuget

This is an update of the functionality written by @alphakilo45 to address issue #94 .
As part of this change I also modified barriers to using the nuget based code cross platform. I have successfully tested both PSGalleryModule and PSGalleryNuget dependencies in PowerShell Core on OSX.

@RamblingCookieMonster Let me know if anything else is required.

Wheee! Awesome!  I'll poke around when I have the chance, might be later this week - sorry, I'm sloooow!

Gentle bump

Wheee!  Merging now, will deploy tonight or tomorrow AM depending on timing, thanks : D

@RamblingCookieMonster My pleasure. Thanks for incorporating it.


Add git repo checker step in transfer-rendered-files.yml

Purpose/implementation Section
What changes are being implemented in this Pull Request?
I wanted a way to have the transfer-rendered-files.yml to run only if the companion Leanpub repository exists. BUT I don't want it to look like it fails if it doesn't exist because that's okay to skip it if it doesn't exist.
So I needed to first write a thing that would give me a TRUE/FALSE does this repo exist, but bash doesn't have a great try/catch system so I had to make an Rscript and function to do this.
What GitHub issue does your pull request address?
Related to the errors happening on github actions: https://github.com/jhudsl/DaSL_Course_Template_Bookdown/actions/runs/1261933208

Yay! https://github.com/jhudsl/DaSL_Course_Template_Bookdown/runs/3677464022?check_suite_focus=true
Now to change the title as not to confuse people.

I've updated the Wiki instructions accordingly! One thing off of the checklist!

Yay it works: https://github.com/jhudsl/DaSL_Course_Template_Leanpub/pull/80


feat(client): adapt openAPI "listDiffData"

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 16 (12.5%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 82.729%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tensorbay/client/dataset.py
2
16
12.5%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
5269

Relevant Lines:
6369

💛  - Coveralls


Add jiffies builtin with bpf_jiffies64

Add jiffies builtin, one of the use case is to calculate the sched_clock indirectly within some old kernels.
Result:
bpftrace --unsafe -e 'BEGIN { system("grep jiffies: /proc/timer_list | head -1"); print(jiffies); exit() }'
Attaching 1 probe...
jiffies:<PHONE_NUMBER>
4325204697

Checklist

[x] Language changes are updated in man/adoc/bpftrace.adoc and if needed in docs/reference_guide.md
[x] User-visible and non-trivial changes updated in CHANGELOG.md
[x] The new behaviour is covered by tests

Thanks a lot for implementing this!
Looks good, a couple of things are missing, though:
* detection if the helper is present in the kernel, it should go to `BPFFeature` and then be called from semantic analyser with a proper error message if the helper is missing,

* semantic analyser tests,

* runtime tests, although I'm not sure if we can come up with something useful here.

See e.g. my recent PR #2692 for inspiration how to implement the above points.

I'm quite unfamiliar here, thanks for the advising! Pushed a new commit, fixed those things.
As for the runtime tests, I want to compare the jiffies between bpftrace and /proc/timer_list, but neither the test engine nor the bpftrace can achieve that easily (the system() in bpftrace cannot be extracted, put compare outside will cause a huge jiffies delay between them), so yes, nothing useful idea has came up :face_in_clouds:.

Please fix the problems reported by clang-format.

Thanks!

Thanks for the cleanup!

Could you squash the first two commits together? Thanks!

Could you squash the first two commits together? Thanks!

Done!


Need to add SUBMIT_EXPRS into the config files

Monitoring and GlideinWMS use the SUBMIT_EXPRS classad to know what to report from the schedd logs.  These are controlled by the schedd for local submissions, but not remote submissions, meaning our DAGs have these pieces of information, but not our normal remote submissions.  We need to add these expressions into the jobsub_lite_configs repo.
Farrukh said he'd give us a config file we could test with, and if it works, we'll put it into a 1.1.1 release.

This was deployed yesterday on our test machines, and all looks good.  I'll add it to the jobsub_lite_config repo and cut a new RPM, then close this.

Merged in https://github.com/marcmengel/jobsub_lite_config/pull/6.  Closing this.


Migrate Heapster to use Kubernetes 1.3

[ ] bump godeps
[ ] change tests to run on 1.3

cc @mksalawa @mwielgus

We should absolutely update cAdvisor dependency.

Is this going to resolve the issue in #1237 ?
I0809 17:35:05.658704       1 rate_calculator.go:51] Skipping rates for namespace:default/pod:gumco-223788322-yeys9/container:gumco - different create time new:2016-08-09 17:08:03.148174048 +0000 UTC  old:2016-08-09 17:08:03.139173623 +0000 UTC
I0809 17:35:05.658751       1 rate_calculator.go:51] Skipping rates for namespace:kube-system/pod:influxdb-grafana-dnwdh - different create time new:2016-08-09 17:07:51.450595189 +0000 UTC  old:2016-08-09 17:07:51.458595589 +0000 UTC
I0809 17:35:05.658788       1 rate_calculator.go:51] Skipping rates for namespace:kube-system/pod:kubernetes-dashboard-3717423461-n00hf - different create time new:2016-08-09 17:07:52.062625845 +0000 UTC  old:2016-08-09 17:07:52.060625744 +0000 UTC
I0809 17:35:05.658801       1 rate_calculator.go:51] Skipping rates for namespace:default/pod:kube-lego-2628658575-nbegw - different create time new:2016-08-09 17:25:09.245173745 +0000 UTC  old:2016-08-09 17:25:09.255174511 +0000 UTC
I0809 17:35:05.658824       1 rate_calculator.go:51] Skipping rates for namespace:kube-system/pod:kube-controller-manager-ip-10-0-5-158.ec2.internal - different create time new:2016-08-09 17:07:53.482696741 +0000 UTC  old:2016-08-09 17:07:53.48469684 +0000 UTC
I0809 17:35:05.658905       1 rate_calculator.go:51] Skipping rates for namespace:default/pod:kube-lego-2628658575-nbegw/container:kube-lego - different create time new:2016-08-09 17:27:40.598496929 +0000 UTC  old:2016-08-09 17:27:40.586496204 +0000 UTC
I0809 17:35:05.658942       1 rate_calculator.go:51] Skipping rates for namespace:kube-system/pod:kube2iam-4ie1g/container:kube2iam - different create time new:2016-08-09 17:08:03.722201157 +0000 UTC  old:2016-08-09 17:08:03.732201629 +0000 UTC
I0809 17:35:05.658968       1 rate_calculator.go:51] Skipping rates for namespace:default/pod:nginx-1537048879-eo10z - different create time new:2016-08-09 17:07:53.049675347 +0000 UTC  old:2016-08-09 17:07:53.047675248 +0000 UTC
I0809 17:35:05.659031       1 rate_calculator.go:51] Skipping rates for namespace:kube-system/pod:heapster-1006675365-4psz8 - different create time new:2016-08-09 17:07:53.60270267 +0000 UTC  old:2016-08-09 17:07:53.623703708 +0000 UTC
I0809 17:35:05.659088       1 rate_calculator.go:51] Skipping rates for namespace:kube-system/pod:influxdb-grafana-dnwdh/container:influxdb - different create time new:2016-08-09 17:07:51.708608106 +0000 UTC  old:2016-08-09 17:07:51.718608607 +0000 UTC
I0809 17:35:05.659140       1 rate_calculator.go:51] Skipping rates for namespace:default/pod:gumco-223788322-yeys9 - different create time new:2016-08-09 17:07:51.76361086 +0000 UTC  old:2016-08-09 17:07:51.775611461 +0000 UTC
I0809 17:35:05.659153       1 rate_calculator.go:51] Skipping rates for namespace:kube-system/pod:kube2iam-4ie1g - different create time new:2016-08-09 17:07:52.665656111 +0000 UTC  old:2016-08-09 17:07:52.675656613 +0000 UTC
I0809 17:35:05.659221       1 rate_calculator.go:51] Skipping rates for namespace:kube-system/pod:kube-controller-manager-ip-10-0-5-158.ec2.internal/container:kube-controller-manager - different create time new:2016-08-09 17:07:53.829713887 +0000 UTC  old:2016-08-09 17:07:53.830713936 +0000 UTC

@andyxning I bumped cadvisor to v0.23.2-79-gc6c06d4 in #1252. We're trying to keep this in sync with the version in Kubernetes.
@lattwood probably not. I posted an update on #1237

@piosz that's ok and we should keep in sync with kubernets. 👍

fixed in #1282


Extra nonce

What do we do when nonce overflows?
Do we want to add a extranonce field field to the transaction structure?
The Bitcoin nonce is 4 bytes and the extranonce is 2-100 bytes.

Yes, I think we need to investigate this case.
As a solution, I was thinking about adding "general use" field to transaction.
We can use the unused part of the "general use field" to increment as a extra nonce.
It could be used to add String to transaction (like a description in real banking)
Also it could be used as a chat system and transactions as chat messages.
(we can add length of description at the beginning of it, to know where the extra nonce starts)

Why not a dedicated extranonce field? Also, Incrementing the extraNonce field entails recomputing the merkle tree, as the coinbase transaction is the left most leaf node.

OK, fine with me.
Yes, lets decouple and have dedicated extranonce.
My whole reasoning was about saving space, but I guess it doesn't make sense.

There will be additional source of randomness: timestamp when we create a block and push it to POW. We should include miliseconds - this will give miners a way to manipulate hash as well (= change milliseconds in order to change hash)

+1
On Wed, Sep 6, 2017 at 2:59 PM sennui<EMAIL_ADDRESS>wrote:

There will be additional source of randomness: timestamp when we create a
block and push it to POW. We should include miliseconds - this will give
miners a way to manipulate hash as well (= change milliseconds in order to
change hash)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aeternity/epoch/issues/66#issuecomment-327461303, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABJZ7cKsamp1KFUrm4Eb3QxlZ778OpMks5sfokWgaJpZM4PN-pk
.

--
__
CTO, æternity
http://linkedin.com/in/joelreymont

Nonce should just be 8 or even 12 bytes rather than Satoshis 4. For reasons and other tweaks to Bitcoins design made by BitGo for. Royal Mints Gold private Blockchain see here
https://www.provachain.com/design-documents

@sennui This only applies to the coinbase transaction, I'll amend the description. Also, we should make it a byte array.


stellar/horizon: Calculating reingest range seems like a pain

What problem does your feature solve?
Normally when reingesting what we care about is reingesting the range after a given protocol upgrade, but we have to go figure out what ledger that happened at, then calculate the upgrade % 64 to get the right ledger start value.
What would you like to see?
A way to express something like horizon reingest --since-protocol 14.
What alternatives are there?
The values never change for pubnet, so we could just do a docs page that lists the same info with the commands, to copy-paste?

Or something like --from-ledger 123400000 so I don't need to even lookup the current elder ledger in horizon.


chore: automate secret creation using tf #2101

#2101

Reviewers
Functional:
@atolopko-czi
@ebezzi
Notes for Reviewer
Work in progress but creating the PR early for visibility.

This PR will be merged with #2677 to consolidate the changes as they are dependent on each other.


Shinobido 2: Revenge of Zen [PCSE00015]

Game summary

Game name: Shinobido 2: Revenge of Zen
Game serial: PCSE00015
Game version: 1.02

Vita3K summary

Version: v0.1
Build number: 847
Commit hash: https://github.com/vita3k/vita3k/commit/b376b10

Test environment summary

Tested by: Zangetsu38
OS: Windows 10 17.763
CPU: AMD Ryzen 7 2700X @ 4.2 Ghz
GPU: NVIDIA 1080 Ti
RAM: 16 GB DDR4 3600 Mhz

Issues

Few NID function not found causing Vita3K don't try opening game file.

Screenshots

Log
vita3k.log

On my last PR, few NID implemented
Screenshots :

I have an issue where I have to open the game more than 5 times before it actually loads up. Once I'm in, the game runs completely until 15-20 minutes or so of gameplay that the game freezes and the emulator crashes.

Game Summary
Game name: Shinobido 2: Revenge of Zen
Game serial: PCSE00015
Game version: 1.00

Vita3K Summary
Version: v0.1.9
Build number: 3353
Commit hash: https://github.com/Vita3K/Vita3K/commit/master

Test Environment Summary
Tested by: Hotate90
OS: Windows 10
CPU: Intel Core i7 8700
GPU: NVIDIA 1060 6GBs
RAM: 16 GB DDR4 3600Mhz

Issues
Game renders properly and it's completely playable on Vulkan (upscaled to 1080p), but after two or three in-game missions or when there are too many sounds playing at the same time, the audio stops working correctly. Some audio cues stop working (like the slashing SFX) while others still work (character voices, for example). There were also very rare instances of subtitles getting stuck on-screen after skipping a cutscene.

Screenshots

Log
vita3k.log

I would like to know how to make part of the sound in this game not disappear after 10 minutes in the vita3k PC version?


Advance ObjC versions to v1.0.1-pre1

Package will be pushed to CocoaPods repo after this PR is approved.
cc: @nicolasnoble @hsaliak

Cool thanks. Wait for test and #8402


support multiline input

I'm hoping for a new feature!
A variant of the Input type that could handle a multiline pasted (or typed?) input. In the polyseam/cndi CLI, I am aiming to collect a multiline JSON string, and Cliffy interprets each line of input as a response to successive prompts.
This variant could be behind a boolean like multiline: true. Submission would require some other user input, maybe a dedicated key or combo like ctrl+o or tab or something.
If anyone has a better way to serve this need in an interactive Cliffy CLI that would be really helpful too!

closing in favour of https://github.com/c4spar/deno-cliffy/issues/9


Add support to change weekend days

There is an option to change first day of week, but there isn't one for changing the weekend days (for highlighting).
Here it's Friday / Saturday (and I assume it's the same for whoever uses Sunday as first day of week, but I might be wrong here)
Thank you very much

@sagilo This can be done already although there isn't yet a proper UI for it. Please see the release notes for version 0.10.16: http://www.mowglii.com/itsycal/versionhistory.html

Version 0.11.1 let's you highlight arbitrary days. You can use this to define 'weekend' any way you like.


Unpublished Yarn Berry files

Describe the bug
When using Yarn Zero Installs, you are not intended to publish the dependencies (any of the Yarn files) to the registry.
Accordingly, this package is WAY too large on the NPM registry.

Thanks for reporting this. This is now fixed in v1.0.2.


relax jsonschema, fix test invocation

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Notes:

restores pip check from #2

patches the jsonschema dependency in setup.py

upstream PR: https://github.com/dbt-labs/hologram/pull/51

adds tests

patches to use default_factory

upstream PR: https://github.com/dbt-labs/hologram/pull/50

adds coverage, with a 90% threshold

while it's possible there's something in the remaining 10% of coverage that will break with jsonschema>3, i'd be much more confident shipping this

@conda-forge/hologram ready for review

@conda-forge-admin please rerender


Telescoping cache precision/throughput issues

We have implemented a Triton kernel for matmul operations involving a telescoping cache in the telescoping-kernel branch. These kernels pass their respective correctness checks (also included), but deploying to our training pipeline is not straightforward because Triton does not support atomic-add in bf16 (see here).
We instead cast to fp16 before this op, but loss curves on a test llama3-1.8B model diverge when we do this:

Loss curves do not diverge when running the kernels in fp32. Unfortunately this sacrifices our speed gains. We're currently evaluating fp32 atomic-adds only, and will update here.
Running these matmuls in fp16 also breaks the vanilla pytorch code, so this is almost certainly a precision issue. If internal fp32 casting does not fix the diverging loss, can the kernel code be massaged to avoid these issues?

Update: performing atomic-adds in fp32 produces the desired behavior, with minimal extra speed/memory overhead. Now it's a question of optimizing throughput: we're currently getting ~3850 tokens/sec/gpu for this particular training setup, compared to ~2550 for pure pytorch baseline and ~10600 for flash attn

Update 2: it turns out that the way we implemented the forward pass around the above kernels also made it amenable to standard attention with a custom mask (visualized below for seq len 512). So we're now running telescoping cache training - stably and relatively quickly - at 8B scale, using memory-efficient attention through PyTorch SDPA (as SDPA-flash attention still doesn't support custom masks, apparently). Further speedups will be possible if we can enable Flash Attention with custom masks in this context.


Question - API url version differs from installed media (beta vs v1.0)

Describe the issue
I have a local BC docker container based on app version 16.1.12629.12805, and a UAT environment at the customer where the exact same version is installed from the installation media.
However, locally I can access the API using http://bc16:7048/BC/api/v1.0, but in the installed environment it is http://bc16:7048/BC/api/beta
Is there a config that I am missing? I just need to understand the reason for the difference in api version.
Scripts used to create container and cause the issue
$containerName = 'bc16'
$artifactUrl = Get-BcArtifactUrl -type 'OnPrem' -version '16.1.12629.12805' -country 'w1' -select 'Latest'
$licenseFile = 'C:\temp\partner.flf'
New-BcContainer `
    -accept_eula `
    -containerName $containerName `
    -credential $credential `
    -auth $auth `
    -artifactUrl $artifactUrl `
    -licenseFile $licenseFile `
    -memoryLimit 12G `
    -updateHosts

Full output of scripts
BcContainerHelper is version 1.0.19
BcContainerHelper is not running as administrator
Host is Microsoft Windows 10 Enterprise - 1909
Docker Client Version is 20.10.2
Docker Server Version is 20.10.2
Fetching all docker images
Using image mcr.microsoft.com/businesscentral:10.0.18363.1256
Creating Container bc16
Version: 16.1.12629.12805-w1
Style: onprem
Multitenant: No
Platform: 16.0.12630.12758
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.18363.1256 (1909)
Host OS Version: 10.0.18363.1316 (1909)
WARNING: Host OS and Base Image Container OS doesn't match, defaulting to hyperv. If you do not have Hyper-V installed or you encounter issues, you could try to specify -isolation process
Using hyperv isolation
Using locale en-US
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file C:\temp\braintree.flf
Files in C:\ProgramData\BcContainerHelper\Extensions\bc16\my:
- AdditionalOutput.ps1
- license.flf
- MainLoop.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container bc16 from image mcr.microsoft.com/businesscentral:10.0.18363.1256
0ab56c07a1450b85981351e253f2d06033447fabbe83936ca6461258fc159c05
Waiting for container bc16 to be ready
Using artifactUrl https://bcartifacts.azureedge.net/onprem/16.1.12629.12805/w1
Using installer from C:\Run\150-new
Installing Business Central
Installing from artifacts
Starting Local SQL Server
Starting Internet Information Server
Copying Service Tier Files

Screenshots
Container:

PS C:\Users\Ewald.venter> Invoke-WebRequest -Method Get -Uri http://bc16:7048/BC/api/v1.0/ -Credential $credential

StatusCode        : 200
StatusDescription : OK
Content           : {"@odata.context":"http://bc16:7048/BC/api/v1.0/$metadata","value":[{"name":"companies","kind":"EntitySet","url":"companies"},{"name":"subscriptions","kind":"EntitySet","url":"subscription
                    s"},{"name":...
RawContent        : HTTP/1.1 200 OK
                    OData-Version: 4.0
                    Access-Control-Allow-Origin: *
                    Access-Control-Allow-Credentials: true
                    Access-Control-Expose-Headers: Date, Content-Length, Server, OData-Version
                    request-id: 8a5...
Forms             : {}
Headers           : {[OData-Version, 4.0], [Access-Control-Allow-Origin, *], [Access-Control-Allow-Credentials, true], [Access-Control-Expose-Headers, Date, Content-Length, Server, OData-Version]...}
Images            : {}
InputFields       : {}
Links             : {}
ParsedHtml        : mshtml.HTMLDocumentClass
RawContentLength  : 3761

UAT:
ServerInstance : MicrosoftDynamicsNavServer$BC
DisplayName    : Microsoft Dynamics 365 Business Central Server [BC]
State          : Running
ServiceAccount : HC\svc
Version        : 16.0.12630.12758
Default        : False

This is a secondary instance, so different port no. (they didn't want to use port sharing)
PS C:\Program Files\Microsoft Dynamics 365 Business Central\160\Service> Invoke-WebRequest -Method Get -Uri http://bc16:7058/BC/api/beta -Credential $cred

StatusCode        : 200
StatusDescription : OK
Content           : {"@odata.context":"http://bc16:7058/BC/api/beta/$metadata","value":[{"name":"companies","kind":"EntitySet","url":"companies"},{"name":"subscriptions","kind":"EntitySet","url":"s...
RawContent        : HTTP/1.1 200 OK
                    OData-Version: 4.0
                    Access-Control-Allow-Origin: *
                    Access-Control-Allow-Credentials: true
                    Access-Control-Expose-Headers: Date, Content-Length, Server, OData-Version
                    request-id: 3b2...
Forms             : {}
Headers           : {[OData-Version, 4.0], [Access-Control-Allow-Origin, *], [Access-Control-Allow-Credentials, true], [Access-Control-Expose-Headers, Date, Content-Length, Server, OData-Version]...}
Images            : {}
InputFields       : {}
Links             : {}
ParsedHtml        : System.__ComObject
RawContentLength  : 3512

If I try to use API version no. v1.0
PS C:\Program Files\Microsoft Dynamics 365 Business Central\160\Service> Invoke-WebRequest -Method Get -Uri http://bc16:7058/BC/api/v1.0 -Credential $cred
Invoke-WebRequest : The remote server returned an error: (404) Not Found.
At line:1 char:1
+ Invoke-WebRequest -Method Get -Uri http://bc16:70 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Kind Regards,
Ewald

The APIs comes in apps as far as I know.
Look at which apps are installed in docker and you should find something like Exclude_APIV1
Not sure where the .app is on the dvd - but it should be there.

The APIs comes in apps as far as I know.
Look at which apps are installed in docker and you should find something like Exclude_APIV1
Not sure where the .app is on the dvd - but it should be there.

Thank you!

Thank you!


Scheduler Monthly and Yearly RadioButtons won't default select correctly

Scheduler Monthly and Yearly Radio Buttons choices won't default select properly unless the selected radio button is the last one in the group in the HTML. There is a bug with the calling of the ResetGroup() function for each radio button created in the group upon SetInitialState(). This means every call to create a radio button unselects any previous ones in the group. If you set any radio button in a group except the last on to default selected it won't appear selected even thou the hidden radio button is indeed selected. Even your demo page displays the problems notice how nothing is selected in the reoccurring demo when you switch to Yearly reoccurring but the hidden radio actually is selected and you can't see it? This is going to be my fourth bug report with the exact code to change on the scheduler any kind of timeframe?  For this one you need to remove the ResetGroup() function call. It appears to serve no purpose other than to break the initialization because SetChecked() executes that exact same code that's in ResetGroup.....again

If you wouldn't mind providing an example (codepen, jsfiddle, jsbin, etc) we would be happy to take a closer look.

This is a problem with the radio control, not the scheduler. Thanks for pointing this out @razor247. Submitting a fix soon.

Ok awesome..I did find that you can’t remove that function. Instead I passed an optional Initialize flag so that function doesn’t get called on initialize but it will be called on all remaining calls to checked….
From: Kevin Parkerson<EMAIL_ADDRESS>Sent: Thursday, May 21, 2015 10:30 AM
To: ExactTarget/fuelux
Cc: razor247
Subject: Re: [fuelux] Scheduler Monthly and Yearly RadioButtons won't default select correctly (#1306)
This is a problem with the radio control, not the scheduler. Thanks for pointing this out @razor247 https://github.com/razor247 . Submitting a fix soon.
—
Reply to this email directly or view it on GitHub https://github.com/ExactTarget/fuelux/issues/1306#issuecomment-104320659 .  https://github.com/notifications/beacon/AEU00zbQaGQXGxZZkuUAPMCy92ZqyN31ks5oLfF4gaJpZM4Eij3w.gif

Stephen Williams from fuelux just emailed me after your email and said he verified the problem and is working on a fix.
You don’t really need a jsfiddle..Just look on your demo page at the Live Schedule sample. Chose Yearly reoccurance..notice there are two radio button
Options neither of which appears to be selected. However the top option is indeed selected if you look at the hidden radio button. The problem is
In the radio initialization code. That code wipes out all initial settings and will only retain the last radio button in the group’s settings due to the resetGroup  function being called.
From: Stephen Williams<EMAIL_ADDRESS>Sent: Thursday, May 21, 2015 9:31 AM
To: ExactTarget/fuelux
Cc: razor247
Subject: Re: [fuelux] Scheduler Monthly and Yearly RadioButtons won't default select correctly (#1306)
If you wouldn't mind providing an example (codepen, jsfiddle, jsbin, etc) we would be happy to take a closer look.
—
Reply to this email directly or view it on GitHub https://github.com/ExactTarget/fuelux/issues/1306#issuecomment-104298089 .  https://github.com/notifications/beacon/AEU005ls0OQ6oAa5XUfsZC802XPcKRZKks5oLeOWgaJpZM4Eij3w.gif

This looks to be the cause of #1287 too. "Checked radio on init only works if it is last"


Add section about stack handling differences to known differences docs

Add section about stack handling to known-differences-with-cf-for-vms.md
Feel free to correct me about that but to my understanding the current restage/staging behaviour in korifi comes with the difference to CF on VMs below, just to get that written down somewhere as @beyhan pointed me to this doc.
It might make sense to rephrase that by someone with deeper technical knowledge in the Korifi implementation and fact check it.
Is there a related GitHub Issue?
No
What is this change about?
Documentation
Does this PR introduce a breaking change?
No
Acceptance Steps
Crosscheck documentation
Tag your pair, your PM, and/or team
None

Without looking at the code and having experimented with that, here are my two cents.
As far as I know, whenever the stack on the kpack cluster builder changes, (I think) kpack schedules a new kpack build for each app. Once the app image is pushed, it would be set on the CFApp resource as a current droplet. Thus, whenever the app restarts, it would pick up the new version.
TL;DR - we need to experiment to see whether a restage is actually required, or a restart is enough.
The assumptions above is of course true when the default kpack bulder is used as a build runner. A custom build runner could behave differently.

Hey @FloThinksPi
I ran some experiments myself, and TL;DR what you suggest is completely correct.
FWIW, here is my experiment:

I have deployed Korifi on kind and pushed an app. Its workload referenced image sha ...d1e8b76e5
I changed the cluster stack images:

paketobuildpacks/build-jammy-base -> paketobuildpacks/build-jammy-full
paketobuildpacks/run-jammy-base -> paketobuildpacks/run-jammy-full

Changing the stack immediately triggerred a new kpack build and that build produced an app image with sha ...4108c38a5. However, the app workload image DID NOT change
I restarted the app, the workload image DID NOT change again
I restaged the app, and that picked up the new image (sha ...4108c38a5`)

Thanks for testing it out @danail-branekov !
Yea i also thought about possible solutions but there is no easy one that comes to my mind straight away.
The stack seperation in CF is a unique feature that is hard to replicate in K8s and yield specific benefits(cost/resource usage) and behaviour one would lose(gurantees towards app developers). Im not aware if one can combine images on K8s at startup.
Another option is a restart waits until a implicit cnb rebase is finished if a new stack shall be used and "hangs" for some time - however since the app restart is a synchronous api call that just is allowed to return when the restart was propagated correctly to the container runtime - its hard to add this in a compatible behaving way as also more errors could occur in the rebase process that need different api responses likely. However i think a transparent rebase on a restart may be the most viable option here.


DTS reboot hangs

I have successfully updated dasharo firmware, but was need to manually remove power as reboot not happened:
Please verify detected hardware!

Board vendor: PC Engines
System model: apu4
Board model: apu4

Does it match your actual specification? (Y|n)

Please verify detected hardware!

Board vendor: PC Engines
System model: apu4
Board model: apu4

Does it match your actual specification? (Y|n) y

Following firmware will be used to install Dasharo
Dasharo BIOS firmware:
  - link: https://cloud.3mdeb.com/public.php/webdav/pcengines_apu2/v0.9.0/pcengines_apu4_v0.9.0.rom
  - hash: fd9d6aee1b6543d49be101bfed937f937de2e09accf7446b29bdeda2607e59e6

You can learn more about this release on: https://docs.dasharo.com/

Do you want to install Dasharo firmware on your hardware? (Y|n) y

Checking Dasharo firmware checksum... Verified.

Found file config at 0x1eae40, type raw, compressed 3854, size 12269
CONFIG_VBOOT=y
Installing Dasharo firmware...
Successfully installed Dasharo firmware
Syncing disks...

Done.
The computer will reboot automatically in 5 seconds
Rebooting in 5s:
5...
4...
3...
2...
1...
Rebooting

previous firmware was v<IP_ADDRESS>


Added lowercase split value and passing tests#42

This pull request takes care of the lower case support issue and enables the users to follow the normal convention as mentioned in #42
This is mainly a cosmetic change and the dataset labels such as 'TRAIN' ,'TEST', 'VALIDATE' are not compatible as lower cases versions. It does not affect the broader scope of the project. however it may require documentation changes.
Fixes  #42
Cosmetic change. as explained in summary above.
Please delete options that are not relevant.

[ Y ] New feature (non-breaking change which adds functionality)
[ Y ] This change requires a documentation update

Checklist

[Y] My code adheres to the Google Python Style Guide
[Y] I ran make test and all tests pass
[Y] I ran the tool and verified the change works
[Y] I have adequately commented my code, particularly in hard-to-understand areas
[Y] My changes generate no new warnings
[Y] I have corrected any misspellings in my code
[Y] (For feature) I made sure that I'm merging to the dev branch

@cfezequiel kindly review the new commits

@cfezequiel Kindly review the changes

@cfezequiel Did you review the changes ?

@cfezequiel alright,
I will make the changes and hopefully we can publish these last changes as well.

@cfezequiel can you kindly review again and approve ?

@Samad999777 looks like there is a conflict with one of the files. Could you please check?

@cfezequiel its actually fine, My file is updated with lower case values, it should be fine to merge it

@cfezequiel I've resolved the conflict. Can you review ?

@Samad999777 got it. There seems to be a cla issue but it looks like something I need to resolve on my end.

@cfezequiel yes, i think you need to re-submit your CLA.

@cfezequiel can you kindly take care of the CLA so these changes can be pushed?

@Samad999777 I may need to update the commit in your PR and push the change to your branch to address the CLA issue (basically remove the unregistered email address there). Are you ok with that?

@cfezequiel As long as i get to be the contributer of this pull request in the project. I am very much okay with it.

@Samad999777 are you able to revert this commit: "Merge branch 'dev' into main" and do a rebase against the dev branch instead? That way, your commits come out on top in the commit history.

@cfezequiel I have reverted the commit: "Merge branch 'dev' into main". However when i attempted to rebase it says that it is already upto date [see image below]. Am i doing this right ?

@Samad999777 Thanks for the change. Have you tried rebasing the main branch in your fork with this repo's dev branch? PRs should be made off of the dev branch unless it's a hotfix.


Add subdirectory of remote repo

🚀 Feature Proposal
Instead of building up a meta repository of a set of complete sets of other git repositories it would be great to be able to only select subfolders/parts of the other repos to be assembled in the meta repository.
As far as I understand this is not really possible with subtrees but maybe it could be solved by partial clones or sparse checkouts.
https://stackoverflow.com/questions/600079/how-do-i-clone-a-subdirectory-only-of-a-git-repository/52269934#52269934
Just close the proposal if this is not possible or if this is not the direction in which meta should be developed. If this is something you'd like to consider I am happy to contribute.
Example
Meta repository
├── file1
├── externalSubfolders
│      ├── programA               <- subfolder of  program repository
│      ├── programC               <- subfolder of  program repository
Program repository
├── programA
├── programB
├── programC
Right now, to do something like this I would need a separate repository for each program (programA, programB). And with a large amount of programs that would grow hard to manage quite soon.

sounds interesting, though I don't have a use case for it myself at the moment.
meta works based on plugins, and ships with a few standard ones - meta-project and meta-git for example. You don't need to use these plugins though - you could make an alternative to those that allow for the project structure you imagine.

This does not fit the intention of meta. Meta exists as a tool to stitch together git repos in a way that is easier to deal with than alternatives. There would be a large amount of work turning meta into something that itself manages state outside of a git repo.
You could potentially do this now with symlinks, but it would be particular to your solution.

Just to document a working solution. The initial meta git clone <repo> is not possible and the repository needs to be set up with the commands below. After the setup, meta commands can be executed as usual.

#Here is a list of all the repositories from which subfolders are to be added to the meta repository
git clone --filter=blob:none --sparse <repo> <folder>

#Enter the respective repositories and only checkout the needed subfolders
cd <folder>
git sparse-checkout init --cone
git sparse-checkout add <subfolder>
cd -

#Add the repositories to the meta file
meta project import <folder> <repo>

#Update the entire meta project
meta git update


[APIM] Changelog for version 4.2.24

APIM 4.2.24 has been released
📝 Please review and merge this pull request to add the changelog to the documentation.

I have a quick update to do before merging @garethbrinn. Thanks for the validation


fallback scenario indexers issue

In addition to #68 there is probably a bug in fallback scenarios indexers.
they seem to be one object, but they need to be different objects for proper cold users and items processing.
length of scenario user indexer labels is not equal to the number of users in train dataset. also new users from test were not included to the indexers (at least poprec indexers inside Fallback), but should be.
I believe, the length of user indexer for fb_model in scenario should be 6040 as for pure poprec model.

closed by #96


Make optional callback in tango service node and add explicit method to set listener

Fixes #308.

@adamantivm ptal

Thank you for this @PerrineAguiar . I think it is good as is.
Only a couple of optional suggestions:

I think since this is an inner interface inside a class that is already called TangoServiceSomething, it is not necessary to add the TangoService prefix to the interface name, imho.
One alternative way to cover for the case where no listener is set is to create a DefaultCallbackListener class that doesn't do anything (or that logs a message indicating no callback for each method), and set a new instance of a DefaultCallbackListener by default. This has the added benefit that if someone wants to implement only a given listener, they can extend the DefaultCallbackListener and only override the functions that the user is interested in overriding - vs. implementing an interface which forces the user to implement all methods.

@adamantivm Thanks for your comment, I followed your suggestions.


WIP - Added jaeger all in one with badger storage

This is a first draft to get Jaeger all in one in Observatorium. This brings a simple Jaeger setup using the all-in-one strategy and uses the badger storage type.
This does not reflect a production installation as the operator would do. Namely, I removed all the ports that might not be necessary by Thanos. I assume that it will use a Jaeger Agent as sidecar, and this sidecar will then use gRPC to talk to the collectors.
The headless service is to enable the gRPC client side load balancing to work. No services with IP are provided, as I don't think Istio (or other types of ingresses) will be necessary, but I can certainly add an IP-service if needed.
I added a Makefile and added a couple of lines to the readme, based on my needs as someone trying to understand how it all works. Let me know if those aren't appropriate and I'll revert those changes.
cc @aditya-konarde for the main parts, and cc @burmanm for the badger-specific settings.
Signed-off-by: Juraci Paixão Kröhling<EMAIL_ADDRESS>

Is the build supposed to work? I can't reproduce the failure locally, even when using the same build image (quay.io/coreos/jsonnet-ci).


Android Detect App does not draw overlay correctly.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): [No] Further troubleshooting shows a minor change may cause this.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Android 7.1
TensorFlow installed from (source or binary): N/A (Nightly apk)
TensorFlow version (use command below): 1.1,1.2
Phone Hardware: Pixel C Tablet
Exact command to reproduce: Use the Detect App and move your target off centre

Describe the problem
Due to how the Detect act appears to process it's imagery and camera fragments etc it means that the overlay that's drawn drifts from the target when off centre. (Will try to post pics when I can.)
Part of this issue appears to be the fact that camera preview shown in the app is oddly cropped and squished from what the app actually sees (from debug view). Because of this, when the overlays are drawn they do not match the camera feed below. (Noticeable when your target object is towards the edge of the input)
Source code / logs
To reproduce, install the app, load up an image of a human on google images and move your camera so it's on the edge. It doesn't line up with the camera preview. Moving this from side to side helps show the problem.
I have spent many hours at work trying to understand why this is. Unfortunately I find the source code very difficult to work with and understand how it at all works. I've had to start again but I came across this bug.
Thanks

@jubjamie Some screenshots would be very helpful as I don't have a device on hand to verify this with. It's possible this is a bug in how those devices report the camera or display orientation and the code mixes up width and height, or something of that nature.
When you turn on debug visualizations (using the volume keys), what do you see in the thumbnail view? It should be rendering static detections there.

@andrewharp Curiously i'm not getting the same behaviour from my 6P today. However the Pixel C is giving me trouble. It looks like it's to do with how the camera feed is displayed as it is being cropped and squished but the overlay goes on as if it hasn't it.
Using the debug view is fine and shows that the camera preview feed is being cropped as I can see much more in the debug view than the main view.
I also have a feeling that this cropping may happen because I have to force the rotation on the Pixel C as it reports the rotation to be 3 deg. I have to manually set sensorOrientation to 90 for it to capture images the correct way up.
Screenshots:

The target centred.

The target off-centre. See how the overlay "drifts". It looks like it's because the image preview camera feed has been cropped and stretched past the screen.

With debug on this time.

Notice how in the debug window we see that there is some grass to the left of the target. However in our preview window we see that the image is cut of right up to the target. However, we can see that the yellow overlay looks likes it's in the right position if we were given the debug view.

I believe that there is a problem with how the camera view is created and that it's partly to do with the screenOrientation. For some reason the Pixel C will report a rotation of 3 (in the debug view) and have the image rotated by 90 (or 87) degrees when using the default app. The only solution I have found to get the app to "see" pictures in the correct orientation is to change sensorOrientation to this:
sensorOrientation = 90;
Instead of the default found here.
While this appears to be partly caused by the hardware (we have tried on two different Pixel C's) there is also some kind of bug with how the camera feed is drawn. I'm really struggling to understand how it's done in the code so hopefully you can help.
Thanks

Assigning to @andrewharp, to remove from triage queue.

@jubjamie Thanks for the details. Sounds like a bug in the device's camera implementation. 3 is obviously an invalid value for SENSOR_ORIENTATION, so maybe it makes sense to default to the most common setting of 90 when the value % 90 != 0?
However given the undesired squashing and stretching of the image it might be best just to force the pixel C to use the camera 1 API. See #8736 for a partially implemented PR -- if you patch that in, does it resolve the issue?

@andrewharp Not sure i'll get a chance to look at using camera 1 today but reading through that PR it looks like it is incomplete? Do you have any idea if it's at a usable point yet? I'm not a big java person so after going through the commit I couldn't work out if it was suitable yet. Perhaps a ping for @BrianOn99 or @osdamv ??
One concern being that from the comments it appears to remove the red debug boxes to show the results and without that i'm unable to continue troubleshooting this issue properly.

At the moment the stylized demo and classifier demo are working with the api 1, I am working with the detector right now

@jubjamie: Is this issue still occurring after #8736?

tbh I have no idea. I'm not going to have a chance to look at this now. I think that the fix doesn't apply to the detector app which is the one causing the issue. I've seen a similar issue on here somewhere but I can't remember where. Unless something has changed then I don't think it fixed the issue. To replicate, use a Pixel C and rotate the app to landscape and try to use.

I took a closer look and my initial interpretation was a bit off; I was thinking that sensorOrientation referred to camera orientation only when in fact it's a computed variable of both sensor and display rotation relative to device.
The "invalid" 3 value was actually coming from the getWindowManager().getDefaultDisplay().getRotation() call which oddly enough returns an integer constant 1-3. In this case the actual rotation is encoded in the variable name: e.g. android.view.Surface.ROTATION_180 = 2.
Accounting for that and doing a bit of variable swapping for height/width coordinate scaling fixed the issue and now the detector demo works in both landscape and portrait mode (as soon as #14236 goes in).


[Broken] Mediaset [ITALY]

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running yt-dlp version 2021.05.20
[x] I've checked that all provided URLs are alive and playable in a browser
[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

Verbose log

D:\TEMP\YDL\YDLP>yt-dlp -v -F https://www.mediasetplay.mediaset.it/video/loveisintheair/episodio-1_F310769301000104
[debug] Command-line config: ['-v', '-F', 'https://www.mediasetplay.mediaset.it/video/loveisintheair/episodio-1_F310769301000104']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] yt-dlp version 2021.05.20 (exe)
[debug] Python version 3.8.10 (CPython 64bit) - Windows-10-10.0.17763-SP0
[debug] exe versions: ffmpeg N-91266-g8c20ea8ee0, ffprobe N-91266-g8c20ea8ee0
[debug] Proxy map: {}
[debug] [Mediaset] Extracting URL: https://www.mediasetplay.mediaset.it/video/loveisintheair/episodio-1_F310769301000104
[Mediaset] F310769301000104: Downloading JSON metadata
[Mediaset] F310769301000104: Downloading MPEG4 SD SMIL data
[Mediaset] F310769301000104: Downloading MPEG4 HD SMIL data
ERROR: This content is not available in your location.
You might want to use a VPN or a proxy server (with --proxy) to workaround.
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1126, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1147, in __extract_info
  File "yt_dlp\extractor\common.py", line 564, in extract
  File "yt_dlp\extractor\mediaset.py", line 157, in _real_extract
  File "yt_dlp\extractor\mediaset.py", line 142, in _real_extract
  File "yt_dlp\extractor\theplatform.py", line 47, in _extract_theplatform_smil
  File "yt_dlp\extractor\common.py", line 1001, in raise_geo_restricted
yt_dlp.utils.GeoRestrictedError: This content is not available in your location.

Description

Trying to download a video from mediaset.it results in a "Geo Restricted Error" even though I'm attempting the download from Italy, so without the use of a VPN or proxy.
This does not occur with all videos, for example this works right now (https://www.mediasetplay.mediaset.it/video/mrwronglezionidamore/episodio-1_F310575103000102), but it also seem to work fine if the video is not brand new, but not always.
In all cases, videos can be downloaded using the mpd urls instead.

Note for devs: they seem to block VPNs/proxies.

Note for devs: they seem to block VPNs/proxies.

VPN (Nord) works for me, both viewing and downloading.

Related: https://github.com/ytdl-org/youtube-dl/issues/29218

I have the same issue, connecting via Nord Italy servers.
https://www.mediasetplay.mediaset.it/video/masantoniosezionescomparsi/pt1--cap1_F309911301001C01
All episodes of the above show can be played in the browser, but youtube-dl version 2021.06.06 can only download episodes 2, 3, 4, 7, 9 and 10.  Episodes 1, 5, 6 and 8 cannot be downloaded.
I'd be very grateful if a dev could look at this.

@nixxo may be interested

ok, got it.
I think I fixed it. I'll do some more tests to see if it works on other links as well.

Extraction is quirky, is working for the most part, but I have some exampe where is not.
For example:
yt-dlp.exe -v "https://www.mediasetplay.mediaset.it/video/cameracafe5/episodio-69-pezzo-di-luna_F303843101017801"

Returns:
[debug] Command-line config: ['-v', 'https://www.mediasetplay.mediaset.it/video/cameracafe5/episodio-69-pezzo-di-luna_F303843101017801']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] yt-dlp version 2021.08.10
[debug] Python version 3.9.1 (CPython 64bit) - Windows-10-10.0.19041-SP0
[debug] exe versions: ffmpeg git-2020-08-31-4a11a6f, ffprobe git-2020-08-31-4a11a6f
[debug] Optional libraries: mutagen, pycryptodome, sqlite, websockets
[debug] Proxy map: {}
[debug] [Mediaset] Extracting URL: https://www.mediasetplay.mediaset.it/video/cameracafe5/episodio-69-pezzo-di-luna_F303843101017801
[Mediaset] F303843101017801: Downloading JSON metadata
[Mediaset] F303843101017801: Downloading MPEG4 SMIL data
ERROR: None of the available releases match the specified AssetType, ProtectionScheme, and/or Format preferences
Traceback (most recent call last):
  File "c:\users\nicola\appdata\local\programs\python\python39\lib\site-packages\yt_dlp\YoutubeDL.py", line 1199, in wrapper
    return func(self, *args, **kwargs)
  File "c:\users\nicola\appdata\local\programs\python\python39\lib\site-packages\yt_dlp\YoutubeDL.py", line 1224, in __extract_info
    ie_result = ie.extract(url)
  File "c:\users\nicola\appdata\local\programs\python\python39\lib\site-packages\yt_dlp\extractor\common.py", line 575, in extract
    ie_result = self._real_extract(url)
  File "c:\users\nicola\appdata\local\programs\python\python39\lib\site-packages\yt_dlp\extractor\mediaset.py", line 155, in _real_extract
    raise first_e
  File "c:\users\nicola\appdata\local\programs\python\python39\lib\site-packages\yt_dlp\extractor\mediaset.py", line 142, in _real_extract
    tp_formats, tp_subtitles = self._extract_theplatform_smil(
  File "c:\users\nicola\appdata\local\programs\python\python39\lib\site-packages\yt_dlp\extractor\theplatform.py", line 51, in _extract_theplatform_smil
    raise ExtractorError(
yt_dlp.utils.ExtractorError: None of the available releases match the specified AssetType, ProtectionScheme, and/or Format preferences

Meanwhile this is working fine:
yt-dlp.exe -v "https://www.mediasetplay.mediaset.it/video/cameracafe5/episodio-1-cestinismo_F303843107006401"

Nicola, non funziona neppure nel browser

@nixxo See #849, #850, #851


Allow clients to correctly handle partial publishing failures

When publishing batches, Nakadi can return partial success. So far, we throw an EventPublishingException, independently of a validation vs. persistence error, and we  only include the failed BatchItemResponse entries. This means without event-id correlation locally it is impossible for teams to figure out which items from the batch need retrying. It also not obvious from the error, if the batch can be retried or not.
Changes

Removes the filtering for only failed events when crafting the EventPublishingException
Introduces subclasses for validation vs. persistence errors: EventPersistenceException for persistence failures which can be retried, EventValidationException for validation errors which need fixing on the client side and should not be retried.
Adapts the documentation in the README

Rationale
This change allows clients to rely on the element ordering in the thrown exception when considering retrying only the failed events, and properly distinguishing between validation and persistence failures.
Next step towards finishing  #415.

@adyach please take a look

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

Comparison is base (24a672e) 68.94% compared to head (8676f76) 69.03%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main     #424      +/-   ##
============================================
+ Coverage     68.94%   69.03%   +0.09%
- Complexity      619      621       +2
============================================
  Files           114      114
  Lines          2447     2448       +1
  Branches        177      177
============================================
+ Hits           1687     1690       +3
+ Misses          630      629       -1
+ Partials        130      129       -1

Flag
Coverage Δ

unittests
69.03% <100.00%> (+0.09%)
:arrow_up:

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

Files
Coverage Δ

...g/zalando/fahrschein/EventPublishingException.java
100.00% <ø> (+14.28%)
:arrow_up:

...org/zalando/fahrschein/ProblemHandlingRequest.java
75.40% <100.00%> (+0.40%)
:arrow_up:

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

@adyach applied suggestions.

👍

👍


[FALLBACK] brokers v2 api

Fallback to the brokers v2 API in case any problem occurs.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: oleg-yudovich:x: EpsilonTalYou have signed the CLA already but the status is still pending? Let us recheck it.


Rules/triggers not getting updated while using register-rules or register-all

Whenever we are updating any rules or triggers and loading changes via st2ctl reload --register-all or st2ctl reload --register-rules/triggers it is not getting updated.
Have to manually delete the rule and again have to create it and then changes are taking place. This is not particular to rules only,it is happening while loading triggers/actions also.
Stackstorm version: st2 3.5.0, on Python 3.6.8

What deployment type? Is this docker, K8 or standalone install?
When you do the st2ctl reload then when it states the number of rules/triggers loaded, does the number look correct?
Is there any errors reported when you do the reload in the stdout/stderr of the st2ctl reload, or in the ST2 log files? (Sometimes there can be some errors at the start of the output on a reload - that can be missed.

Hi @minsis
No i am not bumping the version.

Again today we faced the same issue. I made a change in rules file and reloaded the configuration by running 'st2ctl reload --register-configs' but it did not update the rules. Then i even restarted the services of st2 to see if it helps but no luck.
Then i deleted the rule and again created it and then to my surprise it started working fine after that.

yes @amanda11  i followed everything and that was mentioned to just tell that i followed whatever steps i could.
Initially i followed 'sudo st2ctl reload --register-rules' this only. But it does not work.

I've just verified this functionality on a 3.7dev machine and can see it is working as expected.
Please can you provide the following:

Location of the rule file you are altering - and show the permissions on that file
Change you are making to the rule file - e.g. are you changing it's name, parameters etc
Output from running reload --register-rules
Check in the st2api.log at the time of the reload, check that it has an entry for the rule you have changed and that no errors appear
Can you double-check that in the /opt/stackstorm/packs//rules area that the rule doesn't appear twice? e.g. two rule files whereby the "name:" parameter in the yaml file is the same? This can cause odd behaviour if you have fileA and fileB both refering to rule with name: C for example.

What is the full path to the rules file that you are editing?
In the st2api.log did you see a GET entry for the rule that you had altered?
Can you try with verbose mode, e.g.
st2ctl reload --register-rules --verbose
In the output of the verbose can you check for your rule at the location of the file that it says it is loading, is the same as the one you are editing. And that it reports that it has done an update on the rule that you are expecting to change.

st2api.log has a get entry for the rule that i altered.
`[root@sjc4-stackstorm1 st2]# grep -i zsnagios.smavd st2api.log
2022-05-16 08:59:01,088<PHONE_NUMBER>99664 INFO logging [-] e2a2cf1b-945a-4af4-8bb7-9ba948f5d3b0 - GET /v1/actions/zsnagios.smavd_mem with query={} (method='GET',path='/v1/actions/zsnagios.smavd_mem',remote_addr='<IP_ADDRESS>',query={},request_id='e2a2cf1b-945a-4af4-8bb7-9ba948f5d3b0')
2022-05-16 08:59:01,096<PHONE_NUMBER>99664 INFO logging [-] e2a2cf1b-945a-4af4-8bb7-9ba948f5d3b0 - 200 1026 7.211ms (method='GET',path='/v1/actions/zsnagios.smavd_mem',remote_addr='<IP_ADDRESS>',status=200,runtime=7.211,content_length=1026,request_id='e2a2cf1b-945a-4af4-8bb7-9ba948f5d3b0')
Can you try with verbose mode, e.g.
st2ctl reload --register-rules --verbose
Answer I ran this command , what i could see that it shows the location and loading of  all the default rules but not the custom ones.
2022-05-16 16:21:54,210 AUDIT [-] Rule updated. Rule RuleDB(action=ActionExecutionSpecDB@139674274093240(ref="core.sendmail", parameters="{'body': 'We received an email', 'to'<EMAIL_ADDRESS>'from'<EMAIL_ADDRESS>'subject': 'Email Received'}"), context={}, criteria={'trigger.from': {'pattern'<EMAIL_ADDRESS>'type': 'contains'}}, description="Rule which sends an email when an email from<EMAIL_ADDRESS>is received", enabled=False, id=623e37b2c81c9cb4463011c9, metadata_file="rules/sample.emailsample.yaml", name="Sample", pack="email", ref="email.Sample", tags=[], trigger="email.imap.message", type=RuleTypeSpecDB@139674213923720(ref="standard", parameters="{}"), uid="rule:email:Sample") from /opt/stackstorm/packs/email/rules/sample.emailsample.yaml. 2022-05-16 16:21:54,212 DEBUG [-] ref_count decrement for TriggerDB(description=None, id=623e37b2c81c9cb4463011c3, metadata_file=None, name="imap.message", pack="email", parameters={}, ref="email.imap.message", ref_count=0, type="email.imap.message", uid="trigger:email:imap.message:99914b932bd37a50b983c5e7c90ae93b") not required. 2022-05-16 16:21:54,213 DEBUG [-] Pack slack does not contain rules.
2022-05-16 16:21:54,197 AUDIT [-] Rule updated. Rule RuleDB(action=ActionExecutionSpecDB@139674274093240(ref="chatops.post_result", parameters="{'channel': '{{trigger.data.source_channel}}', 'user': '{{trigger.data.user}}', 'execution_id': '{{trigger.execution_id}}', 'context': '{{trigger.data.source_context}}'}"), context={}, criteria={'trigger.route': {'pattern': 'hubot', 'type': 'equals'}}, description="Notification rule to send results of action executions to stream for chatops", enabled=True, id=617adb3e4959f8e7287c9f4a, metadata_file="rules/notify_hubot.yaml", name="notify", pack="chatops", ref="chatops.notify", tags=[], trigger="core.st2.generic.notifytrigger", type=RuleTypeSpecDB@139674213923720(ref="standard", parameters="{}"), uid="rule:chatops:notify") from /opt/stackstorm/packs/chatops/rules/notify_hubot.yaml.
I again tried to change the rules file and after changing and reloading it , even the st2 rule get <rule_name> is not reflecting the chnages.
Dont know what is wrong.
The change i made:
`[root@sjc4-stackstorm1 zsi]# cat rule_smavd_mem_crit.yaml | grep SMAVD
description: Rule checks for SMAVD MEMORY alert    # optional
#pattern: "SMAVDMEMORY_USAGE"
pattern: "SMAVD MEMORY USAGE"
Reload performed.
But still below: st2 rule get zsnagios.rule_smavd_mem

I am not sure you are editing the file in the correct location.
When you do a reload it will reload the rules from /opt/stackstorm/packs/packname/rules/*.yaml.
Where is your rule_smavd_mem_crit.yaml?
Given the information above it seems to be in a directory called zsi, so that's not in the packname directory - if your pack is zsnagios.
When you do a reload it only reloads from the directory where the packs get deployed to, i.e. /opt/stackstorm/packs not from any local location that you might have installed the pack from in the first place.

Thanks for pointing it out @amanda11 . Indeed this was the reason that why rules were not getting updated but then this is strange that it does pick it from other directory though and the only concerning thing is that they dont get updated when we make any change . Should not it have the provision that if under rules directory there are subdirectories it should work fine?
In an environment where we have lots of servers to target and many alerts, one will want segregation and might create rules according to that . This is what we did. We created 2 directories under rules directory just for segregation because some of our alerts directly impact the environment and others do not have any impact as such.


Additional db check for data loss

Why was this change made?
Ops wants to have a check for data loss
I opted to switch from strict typing here b/c sorbet complained any? wasn't a method on a Class
for the sig I tried to write: sig { params(klass: Class) .returns(String)  } and wasn't sure how to
wire it up properly.
How was this change tested?
Deployed to stage, verified a failing test with no collections in the db.
Which documentation and/or configurations were updated?
DevOpsDocs pending

If you deploy this it will immediately start alerting for prod.  Are you sure?

Good point. Let's hold off then. We're currently sending all prod alerts to nagios-stage only, but even so, I don't think we want this until we have some collections present.


Remove moot version property from bower.json

Per bower/bower.json-spec@a325da3

Thanks, it will make life a little easier :+1:


iOS: FlutterUploaderIsolate.[number].profiler EXC_BAD_ACCESS (code=1, ... ) while uploading

I know here are other issues regarding EXC_BAD_ACCESS errors #39, but I'm not sure if they are related to each other or if this is a new one. If it's a duplicate, feel free to merge the issues or close the issue.
Anyway, when I simply try to upload one file I get sometimes this error which completely crashes the app.

Commit: dbdc47d33905cc05ae939ab2d5bec2e678923703
My three plist keys are:
FUMaximumConnectionsPerHost: 1
FUMaximumUploadOperation: 1
FUTimeoutInSeconds: 3600
My call:
taskId = await FlutterUploader().enqueue(
        url: url,
        files: [FileItem(path: file.path)],
        method: UploadMethod.POST,
        data: data,
        headers: headers,
      );

Device Info:

OS Version: iPhone OS 13.5 (Build 17G68)
Hardware model: iPad7,5

@Curvel Thank you for testing the branch, I appreciate it.
I will try to reproduce this issue asap.

Hey this error was thrown in simulator but in real device it works

That is interesting. I almost never test in the simulator except for the automated tests. 😀

We are facing the same as well. Any solution?

Please try it again with the latest version 2.0.0-beta.5 which includes a fix for this problem.


Multi-cursor glitching while typing quotes

VSCode Version: 1.5-insider
OS Version: Win10

Steps to Reproduce:

Type this in a new file:

Set language mode as "javascript" or "javascript (babel)" or "javascript react"
Now, select first abc, then Select all occurences of Find Match, then press End, and type " (double-quotes) or ' (quotes).

A mismatching number of quotes are put on selections with odd indices, and matching pair on even indices.
Curiously, this bug doesn't occur with braces or brackets (which are also 'autocompleted' by vscode)

@kumarharsh thank you for opening this issue.
@dbaeumer this bug is confirmed. I cannot reproduce this with other languages.

@alexandrudima this is a multi cursor behavior. Please move back if you think otherwise.

This has been fixed in the meantime. All cursors will now type the same thing.


Use APIv2 to fetch current list of contributors in contribAdder

Purpose
The v1 call to get_contributors was omitting non-bibliographic contribs,
and consequently those users were appearing as addable in the UI.
see: https://openscience.atlassian.net/browse/OSF-5461
Changes
Use the v2 endpoint for fetching Node contributors.

Pass complete, no bugs found. :elephant:
Verified that it works as intended; non-bibliographic contributors are now displayed properly:


Documentation links to broken external project site

https://cython.readthedocs.io/en/latest/src/quickstart/install.html from https://github.com/cython/cython/blob/master/docs/src/quickstart/install.rst points to a pythonxy domain which now seems to host a spam site or has been hacked.
The 'official' site might be https://python-xy.github.io/ or https://github.com/python-xy but it seems rather inactive.

Thanks!


[bug] if the user is logged in via either oidc v1 or keycloak

as of v2.3.1
steps to reproduce:
login, select human multilevel atlas, select any regions
expected behaviour:
regional feature loads
actual behaviour:
regional feature does not load (spinner spins forever)

fixed by c2ec79332c6ce063efd632be445676146d3d67f8

fixed by c2ec79332c6ce063efd632be445676146d3d67f8


Provided link to Azure Training

Yes its a duplicate. Iam closing the PR.

As the entry for the certification is already present Iam closing the PR.


Offer auto completion for full text search

Is your feature request related to a problem? Please describe.
Text Search works actually without auto completion of the search terms. So there are no suggestions derived from the database index.
Describe the solution you'd like
I suggest to offer an auto completion feature for search terms of the full text search derived from the current database index.

@wechsler42, auto completion for FTS would be a great feature. Thanks for heads-up!


Better support for Apple Watch

It would be great if Keybase did a better job integrating with the Apple Watch, currently you get the notification, but cannot read the message on the watch (like you can with other chat clients).

Yes please. This level of notification doesn't help at all!


Client Allocation Request for: tianluo

Client Allocation Questions
Core Information

Name: tianluo
Website / Social Media: http://www.kitchenidea.com.cn/#/CloudKit
Region: Greater China
DataCap Requested: 10TiB
Addresses to be Notarized: f1frrnjahwxvc4z2et6trbmvofccz5sfmokakceri
Notary Requested: ozhtdong

@mykylaturiya17 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Thanks for your application. I have some questions about you and your company:
1.What's your name? What's your position?
2.What's your company's business? Do you have any other social media link?
3.Could you show me your company's business license?
4.How many miners do you want to store your data to? How much data for each miner?
5.Will you record your allocation decision in public? Which platform will you use?
6.What method/tool will you use to inspect miners? Which aspect of miners will you inspect?

My name is Xu Xia. I'm the Supervisor
Kitchenidea, formerly known as Hangzhou Chuyi Technology, was established in 2011. As a service provider specializing in intelligent high-end kitchen appliances, Tianluo Cloud Kitchen integrates product research and development, sales, manufacturing, logistics, one-stop procurement, and service to provide global customers with intelligent AI cooking robots.
We have wechat official account: tianluoyunchu
Yes. I will email you.
2miners.  We will divide to each miner equally.
Yes, we will. We want to use github.
We will use filfox to inspect miners. We will inspect creditable miners.

Here it is.
On Tue, Nov 9, 2021 at 5:45 PM ozhtdong @.***> wrote:

Thanks for your application. I have some questions about you and your
company:
1.What's your name? What's your position?
2.What's your company's business? Do you have any other social media link?
3.Could you show me your company's business license?
4.How many miners do you want to store your data to? How much data for
each miner?
5.Will you record your allocation decision in public? Which platform will
you use?
6.What method/tool will you use to inspect miners? Which aspect of miners
will you inspect?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/filecoin-project/filecoin-plus-client-onboarding/issues/1091#issuecomment-963980716,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWM72VM2EM5VRVYQ36H5ODDULDUR5ANCNFSM5HU2CJCQ
.
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.

Request Approved
Your Datacap Allocation Request has been approved by the Notary
Message sent to Filecoin Network

bafy2bzaceak4lh6jojepfxp2mukqbks35hmgjxfesynmm6rkhpwpvhao3c74m

Address

f1frrnjahwxvc4z2et6trbmvofccz5sfmokakceri

Datacap Allocated

NaNB

Signer Address

f1lwpw2bcv66pla3lpkcuzquw37pbx7ur4m6zvq2a

You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceak4lh6jojepfxp2mukqbks35hmgjxfesynmm6rkhpwpvhao3c74m


CIP-0001 | Section heading specifications

About half of the last few weeks' CIP PRs have come in with the required section headings (Abstract, Motivation, Specification) as H1's (markdown #) instead of the H2's (##) that our planned site generator and current CIP makeover (#389) will apparently require.
Therefore since I often do the first triage for document formatting I've been having to submit the same review each time asking authors to demote the headers: a lot of unnecessary work for authors and/or editors, as in:

https://github.com/cardano-foundation/CIPs/pull/422 (latest of these reviews)
https://github.com/cardano-foundation/CIPs/pull/430 (latest PR having this problem again)

Also because the last few CIPs updated in #389 have had an H1 added of CIP-XXXX followed by the CIP title, I'm assuming this is a second requirement.  Between these two stipulations, the result would be a proper SEO outline structure which would be easily parseable when the new static site generator is built.
Therefore we should add these two requirements to CIP-0001 in the Structure section:

Below the preamble should be an H1 (markdown #) title in the form CIP-XXXX followed by the CIP title (example...)
The required section headings (Abstract, Motivation, Specification, ...) should be H2 (markdown ##), with any subordinate sections having headers of even lower rank.

Perhaps this format nannying shouldn't be necessary: but if it weren't then recent authors would have "gotten the point" and would be submitting CIP PRs with these characteristics already, and by adding it to CIP-0001 we are saving everyone from that nannying process in every affected PR.  And we should do something soon before CIP activity gets up to the speed it was in the middle of Q4 2022.
Note @KtorZ I was preparing a PR for this and then reduced it to an issue in the hope this will also be considered along with restoring the former standard of Motivation and Rationale tags without the definitions afterward (as last mentioned in https://github.com/cardano-foundation/CIPs/pull/437#pullrequestreview-1251648728)... mainly because of the cumbersome and uncertain section anchors it creates (as opposed to simple anchors like #motivation and #rationale that would remain the same even if their definitions are changed).

I'm fine with the long section headings tbh.  There's no reason why this repo couldn't have some CI. A CI job that actually tried to build the site would be nice but that rather depends what you end up going with.

There's already a CI building the website but it doesn't enforce that specific thing. Reason being that there are at the moment many CIPs that do not abide. So before making it an automatic requirement we must first fix the existing inconsistencies.
Yet I agree with you Robert, it's a bit painful to have to do it over and over... I don't know why, I believe people just copy paste a template from an existing CIPs that is malformed and simply replicate the malformation. So I am not sure that adding those extra bits to CIP 1 will help much for people reading CIPs are likely just using the suggested template which is correctly formatted.
So I am all for enforcing it via CI and even have a friendly bot that makes those suggestions automatically instead of us doing it. But first, we need to normalise what is already there.

Sorry for using H1's instead of H2's in CIP-XXX (NFT Metadata Oracle).
Honestly, the thought crossed my mind about using H2's, but I didn't see anything about it in CIP-1, so I kept the H1's as-is.
Should we go ahead and fix our headings as you suggest?

Thanks everybody for chiming in.  I think @GeorgeFlerovsky makes the point that people would happily produce an SEO outline if CIP-0001 just gave them a tip each about the title & heading level.  I believe he's also confirming that a good portion of people are in fact being guided by CIP-0001 (based also on other new submissions).
We could also add such a tip that the longer titles for Rationale and Motivation are literal rather than just an advisement to the author.  Sure @michaelpj I think the best way to adjust this would be format correction, but the long standing problems we've had with framework for this suggest it's also useful to standardise this in the authorship itself.
@KtorZ if you are OK with adding concise "tips" to CIP-0001 for either the first point or both, let me know & I will draft a PR for it.

I also thought over the last month the H2 sections Rationale and Motivation could be one-word H2's (creating easy-to-use section anchors #rationale and #motivation for incoming web links), and the extra subtitle texts
Why is this CIP necessary?
How does this CIP achieve its goals?
as headings demoted below H3 (set as H5 above) so as not to conflict with the H3's that follow in the document text.  That preserves the simple incoming section links while still reinforcing the section purpose for both readers & authors.  But this may be too much format nannying to be done by anything but the CI or web formatter.  In the meantime we could simply add it to .github/CIP-TEMPLATE.md.  @KtorZ if you also think this "tip" and template modification is OK I will include it.
Also I campaigned a few times for CIP-0001 asking people to put a link to the rendered proposal in the OP for their PR but this also never took hold.  It would save us a lot of work, and promote review quality in the time after submission, if we advised authors to do it here (https://github.com/cardano-foundation/CIPs/tree/master/CIP-0001#1a-authors-open-a-pull-request).

Anyway this is potentially 4 "tips" in all now and I think they would give editors peace of mind that we don't have to rush to triage elemental format issues and/or spend time maintaining automation that enforces these requirements.

@rphair not sure about the #rationale and #motivation part, as we can already link to both sections in their current form (github provide anchors if you click next to titles):

https://github.com/cardano-foundation/CIPs/tree/master/CIP-0001#motivation-why-is-this-cip-necessary

But I am all in favor of the rest.

@KtorZ yes I know, and so will most other GitHub / Git Docs users... the shorter title is a convenience for content creators well outside that sphere.  I'm thinking of the many incoming links we should eventually have coming into both the GitHub and derived CIP archives from other sources (blog, forum, Wikipedia, presentation slides).  One-word anchors will be readily used and will generally work, while multi-word titles are less likely to be used and will be spelled, punctuated and written wrong.  I'm thinking of the long term in this case but will leave it for consideration later.

I think we can handle that directly on the website then; as we can specify shorter anchor there and it'll most probably be the source for non github users.

I believe he's also confirming that a good portion of people are in fact being guided by CIP-0001

I may be a special case. I'm very much a "Step 1: Read the manual/spec" type of person. 😄
Others may be more likely to copy an existing CIP they like and then adapt to their needs. CI guidance and an official (up-to-date) template would be helpful.

Actually, the inconsistency in structure of CIPs over time may itself be perpetuating more inconsistency.
When I was structuring our CIP, I almost disregarded CIP-1 when I saw that more recent CIPs diverged significantly from it — it almost seemed like it had gotten stale while informal conventions took over.
The reason why I went back to following CIP-1 was that I saw your recent PRs/discussions about updating it and conforming all the CIPs back to its standard.

Arguably, even Inactive CIPs ought to have a path to active. Because they are usually submitted with "active" as an initial goal. Having said that, I am not sure to get the point you're making here @rphair 🤔 ? do you mean we should emphasis that more in CIP-0001? I don't think we suggest that any section is optional at the moment so I don't see the ambiguity.

Closing this so further discussion & editing can continue in #450.


Photoview does not display text and location maps that have been inserted in album

In my laptop version of Google Photos, I inserted text and location maps between photos. Although they display in my laptop version of the selected album, these additions dot not show when the selected album is displayed by the Photoview app on Roku.

@Rokjzf  - Could you take some screenshots of what you're referring to and email me<EMAIL_ADDRESS>

Chris, thanks for the quick response. Below are the two issues that I described. Thanks – John
The image below taken from my windows laptop shows the text image “Entering Rome” that I inserted below three photos using Google Photos. This image does not show when I review the album through the Roku device on my TV.
The image below shows three photos followed by a map  inserted using Google Photos. The map does not show when I review the album through the Roku device on my TV.
John and Diane Frazer<PHONE_NUMBER><EMAIL_ADDRESS>  NEW PERSONAL EMAIL ADDRESS
From: Chris Taylor
Sent: Wednesday, October 16, 2019 10:14 AM
To: chtaylo2/Roku-GooglePhotos
Cc: Rokjzf ; Mention
Subject: Re: [chtaylo2/Roku-GooglePhotos] Photoview does not display text and location maps that have been inserted in album (#267)
@Rokjzf - Could you take some screenshots of what you're referring to and email me<EMAIL_ADDRESS>—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Got it. So you'll need to add the text details to the photo description in Google Photos, directly. The text that you have inside the album is not something Google exposes via their API. We can only access the description in each photo
In Google Photos > Select Photo > [ i ] > Add Description

Okay thanks. What I may do is create some jpgs with text in them. I presume I have the same issue with the maps?
John and Diane Frazer<PHONE_NUMBER><EMAIL_ADDRESS>  NEW PERSONAL EMAIL ADDRESS
From: Chris Taylor
Sent: Wednesday, October 16, 2019 12:36 PM
To: chtaylo2/Roku-GooglePhotos
Cc: Rokjzf ; Mention
Subject: Re: [chtaylo2/Roku-GooglePhotos] Photoview does not display text and location maps that have been inserted in album (#267)
Got it. So you'll need to add the text details to the photo description in Google Photos, directly. The text that you have inside the album is not something Google exposes via their API. We can only access the description in each photo
In Google Photos > Select Photo > [ i ] > Add Description
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


[FP]: CVE-2022-25914 for jib-build-plan

Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:jib_project:jib:0.4.0:::::::*
CVE
CVE-2022-25914
ODC Integration
None
ODC Version
9.0.5
Description
According to the CVE the vulnerability is in "com.google.cloud.tools:jib-core before 0.22.0". However, the matched maven package is jib-build-plan in version 0.4.0 (which is already the newest).

Jib Build plan is versioned independently of the main jib project, so this is a legit FP.
Approved.


Upgrade to PyTorch 1.7 and Lightning 1.1.6

Pytorch 1.7 will allow to remove np.count_nonzero in get_number_of_voxels_per_class
Lightning 1.1.6 will enable correctly logging the SecondsPerBatch metric on the training set (at the moment it is mysteriously swallowed, even though logged)

Add more checks in _test_model_train: This should check that all metrics are both in train and test metrics, and both files have as many rows as there are epochs.

Add more checks in _test_model_train: This should check that all metrics are both in train and test metrics, and both files have as many rows as there are epochs.

Most work done in #411. Change to torch.count_nonzero in #417


xcodeProjectDir relative path + errors, fixes #226

(String) cast to clarify ambiguous method call
Unit tests for the fix (valid and invalid args)
@Optional for possibly null j2objcConfig members
Single quote for string
Allow relative path for xcodeProjectDir
Reworked error messages to handle relative paths

Switch from upstream branch (and deleted that branch). Merging based on LGMT with PR #227.


CB-1761. Validate node counts in CM cluster request

What changes were proposed in this pull request?
Validate host groups in cluster creation request for CM.

no missing groups: all host groups in the template should be present in the request
no unknown groups: all host groups in the request should be defined in the template
cardinality: nodes requested for each host group should be within the range recommended based on cardinality of the template

Validation can be turned off by setting .cluster.validateBlueprint to false in the request.  However CLI has a bug that makes it impossible to turn off validation since version 964.
UI always turns off validation, cluster with invalid cardinality can still be created through it.
Validation for scaling requests is not implemented yet.
How was this patch tested?
Tested that cluster creation requests invalid due to the above restrictions are rejected with the correct message when sent via CLI.
Examples:
ERROR: status code: 400, message: The following host groups are missing from the request: compute, gateway, quorum
ERROR: status code: 400, message: Unknown host groups are present in the request: unknown
ERROR: status code: 400, message: Node count for the following host groups does not meet requirements: (group: 'worker', required: 1+, actual: 0)
ERROR: status code: 400, message: Node count for the following host groups does not meet requirements: (group: 'master', required: 1, actual: 2)

Also verified that the same requests are accepted with validateBlueprint: false using older CLI.
Added unit test.

Usually we create the compute host groups with 0 instances and you can also scale it to 0 instances. Is that still supported after this patch?

Usually we create the compute host groups with 0 instances and you can also scale it to 0 instances. Is that still supported after this patch?

Yes, still supported.
I had to update the patch for the case when cardinality is not specified in the template (currently only cdp-data-mart.bp lacks cardinality).  Existing fallback logic (taken from UI) had to be moved from the service layer to the template processor.


Updated OpenUI5 library entry to latest theme

sap_belize is the new default for OpenUI5 since version 1.40
the URL is our CDN (Content Delivery Network)
switched order of description

I am from the UI5 team, in case of questions please contact me at<EMAIL_ADDRESS>thank you!

Any update on this pull request? Can it be merged?


Adding groupnorm TPP

Summary:
Adding groupnorm TPP (refactored equation/equatiuon_groupnorm.c sample) similar to what was done for batchnorm earlier.

I'm fine with merging, just holding off for now as it's marked WIP

After fixing a couple of issues (one major for the missing initialization of certain arrays in bwd), the PR is ready to get merged in my opinion.


does the docker image support SSH command?

I'm not really getting the question. You could probably configure a server to have this docker container publish the right ports, and ssh into the container. There is nothing prevent users from doing that in the image.


Smoke effect

Check if smoke effect is set correctly when unloading. Doesn't look like there is anything.

Smoke effect while unloading is working on all 3 trailers


A mistake I met when I run "python test.py --config config/demo-test.yml"

Hello! It's an honor to use and replicate your code. Here I have a small question that I hope you can answer. When I run the following code:
'''
python test.py --config config/demo-test.yml
'''
The following error appears:
'''
[2022-11-07 03:02:27 WARNING] demo test config file of data10K
[2022-11-07 03:02:27 INFO] exp/DEMO/demo-1_step_5000.pt/test_pred.log
/home/tristan/anaconda3/envs/py365/lib/python3.6/site-packages/torch/nn/modules/rnn.py:61: UserWarning: dropout option adds dropout after all but last recurrent layer, so non-zero dropout expects num_layers greater than 1, but got dropout=0.1 and num_layers=1
"num_layers={}".format(dropout, num_layers))
[2022-11-07 03:02:30 INFO] Building test data...
Traceback (most recent call last):
File "test.py", line 92, in
translate_them_all(opt)
File "test.py", line 81, in translate_them_all
main(opt)
File "test.py", line 47, in main
for i, (src_shard, tmpl_shard, src2_shard, tgt_shard) in enumerate(shard_pairs):
File "/home/tristan/HedModTmplGen-master/monmt/utils/misc.py", line 78, in split_corpus
with open(data, "r") as f:
FileNotFoundError: [Errno 2] No such file or directory: 'exp/DEMO/demo-1_step_5000.pt/src2-test.txt'
'''
And I can't find why the error is reported, and there is no exception in the training log.
So would you mind to tell me what lead to this result?

Hi Tristan, thank you for your interest in this work and the efforts for updating this code!
If I remember correctly, src2-test.txt is the template file you generate during pass 1. So a simple copy command will do. A piece of evidence is that, according to the data files in Google Drive, tmpl-valid.txt == src2-valid.txt.

Thank you for your reply and patience, and I hope you will forgive me for my foolishness.I didn't find any ways to run copy-command things.And I can only get :
'''
*** Infobox loaded in 0h 0m 0.27s. ***
*** All together 45603/45603 words, 498 properties. ***
*** Infobox loaded in 0h 0m 0.04s. ***
*** All together 45603/45603 words, 498 properties. ***
*** Infobox loaded in 0h 0m 0.04s. ***
*** All together 45603/45603 words, 498 properties. ***
'''
when I run
'''
python build_dataset.py --config condig/demo-prep.yml
'''
So can you please answer this question in more detail? I will be grateful!!!


Add intro overview

Relates to #1492

This is amazing work! 🎉 I love it.
One question I wonder about: with this, we have two nav items on the left that say "Overview"; should we think about making the "Getting Started" and "Intro" headers clickable, and making these the landing pages? Or are we okay with the two titles being the same?
Don't block on this, of course, let's land this as-is!

@joeduffy I think it's okay as is, since "Reference" has an Overview link as well. Guides and Tutorials currently doesn't have an overview link since we have landing pages for "Guides" (captured in #1644 ) and "Tutorials" (which you've taken care of via #1620).


Memory leak

run this line of code in repl：
(call-with-input-file "1MB.txt" (lambda (file) (let* ([x (lambda (a b) (lambda (n) (string-append a b n)))] [y (x (read-all file) "a")]) (y "b"))))

every time it execute, memory usage increase by 1MB.

Unfortunately scheme.rs does not have a garbage collector. It's probably not a good idea to use it for long running programs (but for shorter ones, this is a good thing :)). I may implement this in the future*.
*: To be honest it'll probably take years as I can't really find any spare time to work on this.


Branch protection: Possibility to not use whitelist but allow anyone with write access

fixes #8288. Related to #5731 (does not solve exactly what poster wants)
Gives three options for pushing to protected branch:

disabled
anyone with write access
only whitelisted

For approvals a new checkbox is added to enable whitelist. Otherwise anyone with write access is considered as a valid approval.
Screenshot

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8f09aff). Click here to learn what that means.
The diff coverage is 15%.

@@            Coverage Diff            @@
##             master    #9055   +/-   ##
=========================================
  Coverage          ?   41.08%
=========================================
  Files             ?      550
  Lines             ?    71552
  Branches          ?        0
=========================================
  Hits              ?    29396
  Misses            ?    38438
  Partials          ?     3718

Impacted Files
Coverage Δ

models/migrations/migrations.go
1.3% <ø> (ø)

modules/auth/repo_form.go
41.73% <ø> (ø)

routers/private/hook.go
50.24% <0%> (ø)

models/migrations/v109.go
0% <0%> (ø)

models/branches.go
45.1% <3.57%> (ø)

routers/repo/setting_protected_branch.go
41.2% <72.72%> (ø)

Continue to review full report at Codecov.

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

Sorry if I didn't get this correctly; the original issue was kind of unclear, but what I understood is that the OP asked for something like...?:

[ ] Allow forced pushs (-f)

This PR seems very useful nonetheless.

Reading the issue again (and also the comment that was in Chinese), I see I misunderstood what the original poster wanted. I though the problem was that you wanted to easily disable only force pushing for everyone but allowing pushing (without having to enter a whitelist), and maybe also that it shall be enforced for all branches (which can be solved by wildcard protected branches).
So yes, enabling force pushing for some users is not solved by this PR.

:eyes:

Please resolve conflicts.

Migration number has changed  +1

So finally I think this PR is ready....


HRA User Stories menu item needs adjustments

Design To Do's
Katy and I discussed that this needs adjustments:

Remove this from the Outreach menu
Design a way for all 7 user stories to be featured, likely on the Use the Atlas overview page
Gather information from Dan
Design area for featuring the HIVE Marker Paper preprint (should be available this Friday 3/8)

Preprint with user stories: https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>7041v1

Content Needed

Content Document

To Do

[ ] Libby: Take first pass at content in doc
[ ] Libby: Send doc to Katy, Lisel, Dan, Yash, and Bruce to edit
[ ] Katy: Edit content until approved
[ ] Libby: Add content to pages
[ ] Libby: Ship design to development

Current Design Updates

Preprint card added to Use the HRA overview page
4 button cards added for 4 new user stories