Overbuffing Weapon Damage

Would it be possible to save some resources on the weapon damage when it is overcapped to use for the spell damage test?
Total Weapon Damage: 3798.0
Weapon Damage Test takes 1 adventure (predicted: -13).
Total Spell Damage: 1768.0
Spell Damage Test takes 26 adventures (predicted: 26).
The Cargo Pants pocket (Rictus of Yeg) and the Wizard Snack Voucher (wasabi marble soda) seem like they could have been better be used on the spell damage equivalents in my last ascension.  Detailed data below if it's helpful.

    Equipment changed.

type
source
Weapon Damage
Weapon Damage Percent

Item
seal-skull helmet
+1.00
= +1.00

Item
dented scepter

Equipment Power
15% weapon power
+30.00
= +31.00

Item
august scepter

Item
pantogram pants
+20.00
= +51.00

Item
Brutal brogues

Item
Powerful Glove

Item
Kremlin's Greatest Briefcase

Equipment Power
15% weapon power
+15.00
= +66.00

Item
candy cane sword cane
+5.00
= +71.00

Skill
Claws of the Walrus
+7.00
= +78.00

Effect
Disdain of the War Snapper
+5.00
= +83.00

Effect
Meteor Showered

Effect
Billiards Belligerence

Effect
Jackasses' Symphony of Destruction
+12.00
= +95.00

Effect
Tenacity of the Snapper
+8.00
= +103.00

Effect
Carol of the Bulls

Effect
Frenzied, Bloody

Effect
Rage of the Reindeer
+10.00
= +113.00

Effect
Scowl of the Auk
+10.00
= +123.00

Effect
Song of the North

Effect
Pronounced Potency
+5.00
= +128.00

Effect
Wasabi With You

Effect
Do You Crush What I Crush?

Effect
Destructive Resolve
+20.00
= +148.00

Effect
Seeing Red
+25.00
= +173.00

Effect
Cowrruption

Effect
Imported Strength

Effect
Weapon of Mass Destruction

Effect
The Power of LOV

Effect
Lack of Body-Building

Effect
Rictus of Yeg

Boom Box
These Fists Were Made for Punchin'
+21.00
= +194.00

Effect
Offhand Remarkable

[Weapon Damage] seal-skull helmet (1.0)
[Weapon Damage Percent] dented scepter (50.0)
[Weapon Damage] 15% weapon power (30.0)
[Weapon Damage Percent] august scepter (50.0)
[Weapon Damage] pantogram pants (20.0)
[Weapon Damage Percent] Brutal brogues (50.0)
[Weapon Damage Percent] Powerful Glove (25.0)
[Weapon Damage Percent] Kremlin's Greatest Briefcase (25.0)
[Weapon Damage] 15% weapon power (15.0)
[Weapon Damage] candy cane sword cane (5.0)
[Weapon Damage Percent] candy cane sword cane (50.0)
[Weapon Damage] Claws of the Walrus (7.0)
[Weapon Damage] Disdain of the War Snapper (5.0)
[Weapon Damage Percent] Meteor Showered (200.0)
[Weapon Damage Percent] Billiards Belligerence (50.0)
[Weapon Damage] Jackasses' Symphony of Destruction (12.0)
[Weapon Damage] Tenacity of the Snapper (8.0)
[Weapon Damage Percent] Carol of the Bulls (100.0)
[Weapon Damage Percent] Frenzied, Bloody (50.0)
[Weapon Damage] Rage of the Reindeer (10.0)
[Weapon Damage] Scowl of the Auk (10.0)
[Weapon Damage Percent] Song of the North (100.0)
[Weapon Damage] Pronounced Potency (5.0)
[Weapon Damage Percent] Wasabi With You (150.0)
[Weapon Damage Percent] Do You Crush What I Crush? (100.0)
[Weapon Damage] Destructive Resolve (20.0)
[Weapon Damage] Seeing Red (25.0)
[Weapon Damage Percent] Seeing Red (100.0)
[Weapon Damage Percent] Cowrruption (200.0)
[Weapon Damage Percent] Imported Strength (50.0)
[Weapon Damage Percent] Weapon of Mass Destruction (30.0)
[Weapon Damage Percent] The Power of LOV (50.0)
[Weapon Damage Percent] Lack of Body-Building (25.0)
[Weapon Damage Percent] Rictus of Yeg (200.0)
[Weapon Damage] These Fists Were Made for Punchin' (21.0)
[Weapon Damage Percent] Offhand Remarkable (50.0)
[Weapon Damage] Bow-Legged Swagger (194.0)
Weapon Damage => 388.0
[Weapon Damage Percent] Bow-Legged Swagger (1705.0)
Weapon Damage Percent => 3410.0
Total Weapon Damage: 3798.0
Weapon Damage Test takes 1 adventure (predicted: -13).

type
source
Spell Damage
Spell Damage Percent
Cold Spell Damage
Hot Spell Damage
Sleaze Spell Damage
Spooky Spell Damage
Stench Spell Damage
Sauce Spell Damage

Item
Hollandaise helmet
+1.00
= +1.00

Item
august scepter

+50.00
= +50.00

Item
Powerful Glove

+50.00
= +100.00

Item
codpiece
+50.00
= +51.00

Item
hewn moon-rune spoon
+10.00
= +61.00

Item
wrench

+100.00
= +200.00

Skill
Eldritch Intellect

Skill
Eternal Flame

+1.00
= +1.00

Skill
Master Saucier

+10.00
= +210.00

Skill
Subtle and Quick to Anger

+10.00
= +220.00

Skill
Intrinsic Spiciness

Effect
Meteor Showered

+200.00
= +420.00

Effect
Jackasses' Symphony of Destruction
+12.00
= +73.00

Effect
Arched Eyebrow of the Archmage
+10.00
= +83.00

Effect
Carol of the Hells

+100.00
= +520.00

Effect
Mental A-cue-ity

+50.00
= +570.00

Effect
Simmering

+100.00
= +670.00

Effect
Song of Sauce

+100.00
= +770.00

+50.00
= +51.00

Effect
Visions of the Deep Dark Deeps

+50.00
= +820.00

Effect
Do You Crush What I Crush?

+100.00
= +920.00

Effect
Hot in Herre

+20.00
= +71.00

Effect
Fortunate Resolve
+10.00
= +93.00

Effect
Destructive Resolve
+20.00
= +113.00

Effect
Lantern-Charged

+50.00
= +970.00

Effect
Cowrruption

+200.00
= +1170.00

Effect
Imported Strength

+50.00
= +1220.00

Effect
AAA-Charged

+50.00
= +1270.00

Effect
We're All Made of Starfish

+25.00
= +1295.00

Effect
The Magic of LOV

+100.00
= +1395.00

Effect
Warlock, Warstock, and Warbarrel

+150.00
= +1545.00

Effect
Hot-Headed

+15.00
= +86.00

Effect
In the 'zone zone!
+50.00
= +163.00

Effect
Spirit of Peppermint
+10.00
= +173.00

Effect
Offhand Remarkable

+50.00
= +1595.00

[Spell Damage] Hollandaise helmet (1.0)
[Spell Damage Percent] august scepter (50.0)
[Spell Damage Percent] Powerful Glove (50.0)
[Spell Damage] codpiece (50.0)
[Spell Damage] hewn moon-rune spoon (10.0)
[Spell Damage Percent] wrench (100.0)
[Spell Damage Percent] Master Saucier (10.0)
[Spell Damage Percent] Subtle and Quick to Anger (10.0)
[Spell Damage Percent] Meteor Showered (200.0)
[Spell Damage] Jackasses' Symphony of Destruction (12.0)
[Spell Damage] Arched Eyebrow of the Archmage (10.0)
[Spell Damage Percent] Carol of the Hells (100.0)
[Spell Damage Percent] Mental A-cue-ity (50.0)
[Spell Damage Percent] Simmering (100.0)
[Spell Damage Percent] Song of Sauce (100.0)
[Spell Damage Percent] Visions of the Deep Dark Deeps (50.0)
[Spell Damage Percent] Do You Crush What I Crush? (100.0)
[Spell Damage] Fortunate Resolve (10.0)
[Spell Damage] Destructive Resolve (20.0)
[Spell Damage Percent] Lantern-Charged (50.0)
[Spell Damage Percent] Cowrruption (200.0)
[Spell Damage Percent] Imported Strength (50.0)
[Spell Damage Percent] AAA-Charged (50.0)
[Spell Damage Percent] We're All Made of Starfish (25.0)
[Spell Damage Percent] The Magic of LOV (100.0)
[Spell Damage Percent] Warlock, Warstock, and Warbarrel (150.0)
[Spell Damage] In the 'zone zone! (50.0)
[Spell Damage] Spirit of Peppermint (10.0)
[Spell Damage Percent] Offhand Remarkable (50.0)
Spell Damage => 173.0
Spell Damage Percent => 1595.0
Total Spell Damage: 1768.0
Spell Damage Test takes 26 adventures (predicted: 26).

It's not trivial for the script to decide what resources to cut when different accounts with different set-ups may have different goals post-CS.
What you can do is to follow the FAQ and set instant_explicitlyExcludedBuffs=<comma-separated effect IDs> to avoid buffing up on various buffs you think you'd like saving.
For example, set instant_explicitlyExcludedBuffs=2590,827 will prevent the script from using the cargo shorts for Rictus of Yeg and your wizard snack voucher on Wasabi With You (as a small little bonus, the script will then default to using the wizard snack voucher on the spell% potion instead, but will currently not use your cargo shorts for a spell% buff)

Thank you for the script!  Just wanted to say that I added the line you recommended, and it no longer uses the Yeg Motel Toothbrush.  It does, however, harvest them from the shorts (I forgot to harvest the Yeg's Motel hand soap before pressing go).

Ah right, that's because there's a separate task specifically for the cargo shorts. You can prevent the toothbrush from being harvested with set instant_saveCargoShorts=true.

Any chance the script could use the Yeg Motel Soap if it's on hand?

There usually are better pulls for profit (like any of the desk bells), but if you're gunning for something else, this is a little unconventional but it should work - set instant_spellTestPulls=10607. If you already have a Motel Soap on hand, it'll skip past pulling from Hagnk's and go directly to using the item.

Thank you!  85 turns!


HPA doesn't work on 1.9 with metricsServer enabled or disabled

It seems since 1.9 these flag is enabled by default on the controller managers

     - --horizontal-pod-autoscaler-use-rest-clients=false

as explained in this PR https://github.com/kubernetes/kubernetes/issues/57673. However in order to make it work with the metrics server kube-aws should also enable the API agreggation layer as discussed on #1180 so the metrics.k8s.io api is registered and can be used.
If you have heapster in the cluster it won't be used, i have a working workaround that when you disable metric server it will set to false the hpa flag.
To be able to use metric-server API agreggation layer should be enabled, so until API Agreggation sup
port is merged we should not recommend people to deploy metric server.
This is what you would see in an HPA on a 1.9 cluster with metrics server enabled.
Metrics:                                               ( current / target )
  resource cpu on pods  (as a percentage of request):  <unknown> / 80%
Min replicas:                                          2
Max replicas:                                          50
Conditions:
  Type           Status  Reason                   Message
  ----           ------  ------                   -------
  AbleToScale    True    SucceededGetScale        the HPA controller was able to get the target's current scale
  ScalingActive  False   FailedGetResourceMetric  the HPA was unable to compute the replica count: unable to get metrics for resource cpu: unable to fetch metrics from API: pods.metrics.k8s.io is forbidden: User "system:anonymous" cannot list pods.metrics.k8s.io in the namespace "default".
Events:
  Type     Reason                        Age                 From                       Message
  ----     ------                        ----                ----                       -------
  Normal   SuccessfulRescale             22m                 horizontal-pod-autoscaler  New size: 2; reason: Current number of replicas below Spec.MinReplicas
  Warning  FailedComputeMetricsReplicas  16m (x12 over 21m)  horizontal-pod-autoscaler  failed to get cpu utilization: unable to get metrics for resource cpu: unable to fetch metrics from API: pods.metrics.k8s.io is forbidden: User "system:anonymous" cannot list pods.metrics.k8s.io in the namespace "default".
  Warning  FailedGetResourceMetric       2m (x40 over 21m)   horizontal-pod-autoscaler  unable to get metrics for resource cpu: unable to fetch metrics from API: pods.metrics.k8s.io is forbidden: User "system:anonymous" cannot list pods.metrics.k8s.io in the namespace "default".

Hi @Fsero yeah many 1.8+ services are now rely on the API aggregation layer being enabled and configured. I hit the same thing with stash 0.7.x which now requires the aggregation layer to even run. There is a separate issue #1180 after enabling the API aggregation layer.

since #1197 is now merged (thank you so much @mumoshu ) and there are people working already on enabling aggregation layer #1180 #1136  closing this issue


Socket Error in scan controller

I am running an application on my localhost . Whenever I am trying to test the page I am getting error . I am sharing the screenshot .

Issue is resolved. The issue is because of redis-server. I have to externally install redis-server and  run sidekiq.
Do:
Sudo apt-get install redis-server
redis-server (On one terminal)
redis-cli(on other terminal)
Now run the command:
export REDIS_URL=redis://<IP_ADDRESS>:6379/0 && bundle exec sidekiq


CI for Node

Adding node.js workflow.

Initializes with two players, Starts the game with a random player & Sets the current player to be whoever it is not


bug: Eslint throws: TypeError: context.getSource is not a function when disabling/breaking react-hooks plugin rules.

Provide environment information
System:
OS: macOS 14.4.1
CPU: (14) arm64 Apple M3 Max
Memory: 10.59 GB / 36.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 21.7.1 - ~/.nvm/versions/node/v21.7.1/bin/node
npm: 10.5.0 - ~/.nvm/versions/node/v21.7.1/bin/npm
pnpm: 9.0.6 - ~/Library/pnpm/pnpm
bun: 1.1.0 - ~/.bun/bin/bun
Describe the bug
I noticed when I tried to disable react-hooks/exhaustive-deps eslint crashes. The lsp stops working in the specific file and even though the rule is disabled whenever I run pnpm lint it crashes failing ci with the error:
TypeError: context.getSource is not a function
Furthermore I notice that if I add the deps in the deps array of the useEffect eslint lsp starts working again and the error is gone when doing pnpm lint.
Link to reproduction
https://github.com/ypanagidis/eslint-turbo-TypeError
To reproduce

Clone the repo and cd into it
Run pnpm install
Run pnpm lint

Additional information
No response

should be fixed in https://github.com/t3-oss/create-t3-turbo/commit/19a823e66db0fa1c46bc2782a996c3caeb22e8f5

Absolute legend, thank you so much!!!!


Documents assumes azure only supports C#

Azure platform claims it supports every programming language but documents are just for .Net.
The last page I am referring is:
https://docs.microsoft.com/en-us/azure/azure-functions/functions-triggers-bindings

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

ID: 7d575e82-637b-32de-e64d-75adf4b6d976
Version Independent ID: e346a973-fcb9-0c10-c1ed-17acd806ced9
Content: Triggers and bindings in Azure Functions
Content Source: articles/azure-functions/functions-triggers-bindings.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

Hi @egiray Thank you for your feedback! We will review and update as appropriate.

@egiray I believe the claim that you are referring to is by Azure App Service on Linux, which allows you to use any runtime (thereby programming language) with its support for running custom docker containers.
Here is a doc for this, Also, support for Windows Containers has been announced and is in preview.
As for Azure Functions, the language support is dependent on Azure Functions Host.
This doc lists the languages supported.
And you can find samples in multiple languages for working with Triggers/Bindings under Reference -> Bindings

That being said, quite a few of the docs do have code for just C# and JS, mainly because these languages are Generally Available (GA). Java and Python are still in preview.

@egiray Just following up... Hope me comment clears things up. 😄


Release Note Automation

Some of our repositories have changelogs in their release notes (check out packit's release notes for example). This information is helpful for users, but can be time consuming for maintainers. It's also not standardized across our buildpacks and other repos.
We should create some kind of automation that will auto-generate a changelog in the release notes when the create-draft-release workflow runs so we can have consistent notes across our community.

I've noticed that since the changelog update went out to the Paketo repos, the Create/Draft release job has been failing in this way:
https://github.com/paketo-buildpacks/go/runs/2410575650
https://github.com/paketo-buildpacks/go-dist/runs/2410518137
Something is off about the YAML, perhaps...

Should be resolved by https://github.com/paketo-buildpacks/github-config/pull/263

Confirmed to be resolved by #263.


Fix existing linter errors

After adding flake8, there are some files failing the linter check. See flake8 output for details.

Lint stage is failing because base branch changed -- for some reason github context doesn't change in this situation.


Export stopping

Hello,
Sketch 53.1.
Stop the export on the first symbol. I have been exporting the same file for 6 month, first time I have a problem.

We're having this problem too. Exporting stalls on a specific step (always the same symbol), every time.

@MarcOckam Please give this a try: #536

It seems to have solve the problem, thanks


[Sentinel] Sentinel Feign fix NPE when invoke default method in interface

Which Component
Sentinel
Describe the bug
@FeignClient(name = "service-provider")
public interface EchoService {
	@RequestMapping(value = "/divide", method = RequestMethod.GET)
	String divide(@RequestParam("a") Integer a, @RequestParam("b") Integer b);

	default String divide(Integer a) {
	    return divide(a, 1);
    }
}

invoke divide(Integer a) throw NPE.
Expected behavior
Invoke normally

Has the problem been solved so far?

Has the problem been solved so far? @fangjian0423


Added an updated package-lock.json

The build process did not seem to update package-lock.json, which happens when you run npm install, so will need to look at that for future releases.

@dwhite-nuodb You keep using the same branch and having merged in changes appear in your PRs.
Please use a different branch for each PR to avoid this.

Adrian, please help me understand what problem this creates, as I mentioned git allows this, so as I try to settle on a development strategy, I need to know what this is breaking.

It looks like you are using the GitHub UI to merge the PR, then continuing to work on the branch, which has now diverged from master in the commit stream, even though there are changes in common that were squashed.
When you use the GitHub UI to squash and merge this PR, it will detect that there are common changes and remove them from the commit that gets generated, but you are still forcing everyone to review the same changes over and over.

Adrian, I see your concern, and at the moment I am not sure how to make it clear what needs to be reviewed on top of what was reviewed already, so if there is no easy way to discern what is new in the PR, then I will abide.  In this particular case, all these changes are targeting the same goal, so in my mind they are all related, I was hoping to make all 4.0.0 changes on the same branch, but apparently that is giving a headache.

Deleted branch per the point brought up by Adrian.


Allow limiting PageChooserBlock to specific page type.

Tested, pep8 checked, implements nicely. Currently, I override PageChooserBlock in my project the same way and use that 'PageChooserBlockOverride' class in my StreamFields when needed. Using Wagtail (1.0), Django (1.8.3) no issues detected.
This was a feature I needed for my project. It is amusing to notice that PageChooserPanel has such functionality but block doesn't.

Thanks! Looks good, but needs a test or two.

It passed current tests and I used built in methods that I assumed were tested so I didn't write any additional test.
I will see what I can do later today.

There is a bug with 'render_html()' method in AdminPageChooser model when content_type is passed as init argument.
'get_instance_and_id()' mysteriously ends up executing 'else', thus returning tuple (instance, instance) and not (instance, id). I really can't figure it out why it doesn't stop at 'elif isinstance():'.
Changing 'get_instance_and_id()' to return 'value.pk' in 'else' condition introduces various bugs  in wagtail admin so I decided for additional 'value' check just before it is used to serve expected type.
I am also watching issue #1533 and can update PageChooserBlock with same functionality once #1533 is finished.

Implemented in #3072.


Try executing swift package generate-xcodeproj outside of Rake

Short description 📝
Test on Travis CI
Solution 📦
Not sure it will be fixed yet
Implementation 👩💻👨💻
In brief, I'm calling swift package generate-xcodeproj outside of rake test and with travis_wait in the case it takes more than 10 minutes without output.

@cotsog could you figure out why Xcode commands doesn't run on this repository? I've tried several things but none of them work. It doesn't seem to be related to the .travis.yml because I'm using a similar setup in other projects and it works in them.


iss claim in jwt proof type must be omitted for pre-authorized code flow according to the openid4vci spec

iss: OPTIONAL (string). The value of this claim MUST be the client_id of the Client making the Credential request. This claim MUST be omitted if the access token authorizing the issuance call was obtained from a Pre-Authorized Code Flow through anonymous access to the token endpoint.
https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0-14.html#section-<IP_ADDRESS>-2.2.1

Dear @khaingphyo
Thanks for reporting this.


Logged in user auto redirect to product

The logged in user will now get redirected into the product after 5s with 2s response time.
If the user cancels the redirect sequence, the modal is suppressed for the next 3 visits
The modal will try to get primacyCTA link from the BlockMediator, but will resort to using the querySelector to find a link that either matches the floating CTA on the page or the button with 'primacyCTA' class.
There's some refactor done to the existing delay load product code.
Utils proactively export helper functions and placeholders in a delayUtils package to delayed.js
This feature will only work when all placeholders pieces are in place (cancel, bmtp-header, bmtp-cancel-text).

Resolves: [Desktop] RTP CCX0137- Direct Path to Product
Test URLs:

Before: https://stage--express--adobecom.hlx.page/express/feature/image/remove-background?martech=off
After: https://login-auto-redirect--express--adobecom.hlx.page/express/feature/image/remove-background?martech=off

This feature requires login status to test. Might need to make its way into stage before we can do any testing. To see only the modal behavior with mocked user, please use:
https://login-auto-redirect-mock--express--adobecom.hlx.page/express/feature/image/remove-background?martech=off

Currently waiting for Abhinav to confirm on delay second number

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

Comparison is base (41a9292) 31.95% compared to head (cc11a72) 31.96%.
Report is 1 commits behind head on stage.

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #388      +/-   ##
==========================================
+ Coverage   31.95%   31.96%   +0.01%
==========================================
  Files         125      125
  Lines       23998    23998
==========================================
+ Hits         7668     7672       +4
+ Misses      16330    16326       -4

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


AspNetCoreModuleV2 - web.config - but no module in publish

Hi
I have an asp.net core 2.2.1 application, that i upgraded from 2.0, using the full framework. When i deploy the application to Azure It writes this to the web.config file:
<system.webServer>
      <handlers>
        <remove name="aspNetCore" />
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath="%LAUNCHER_PATH%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" arguments="%LAUNCHER_ARGS%">
        <environmentVariables />
      </aspNetCore>
    </system.webServer>

But the AspNetCoreModuleV2 module is not publish to Azure App Service. I can not find it in Nuget or as a part of the All package.
Hope somebody can clarify this.

@kenso23 did you see the "Availability in Azure App Service" section in the announcement blog: https://blogs.msdn.microsoft.com/webdev/2018/12/04/asp-net-core-2-2-available-today/

Ahh, no I didn’t- sorry I should have noted it.
Thank you for quick answer!


Combine forces with torch.jl

@dhairyagandhi96 is working on another Torch backend, with autoconvert and flux interop. It makes sense I think to focus on one torch package
https://github.com/dhairyagandhi96/Torch.jl

Actually, I see there's awareness of torch.jl already. Do these packages have different goals?


IntersectBed error with gff.gz file as input

Dear all,
This is the same as issue #353 but using bedtools v2.25.0-69-g401c61d since I am still getting the same error after the fix.
When using two gff.gz files as input to intersectBed I get a format error that stops the program before the end.
I am doing this:
~/bin/bedtools2/bin/bedtools intersect -wao -a contiguousAlignments.gff.gz -b annotatedExons.gff.gz | gzip > contiguousAlignments_intersected.txt.gz 2> intersect.err
and I am getthing this in standard output
Error: line number 18921599 of file contiguousAlignments.gff.gz has 6 fields, but 9 were expected.
However my file contiguousAlignments.gff.gz is well formatted:
zcat contiguousAlignments.gff.gz | awk '{n=split($0,a,"\t"); print n}' | sort | uniq -c
18921671 9
Could you please let me know if it is possible to fix this problem or if I should rather use bed files as input?
Thanks,

I'm bumping into the exact same bug. Please let me know if any fix is planned!

I reran this with your test data using the latest version in the repository v2.25.0-114-g780faf7-dirty and I am still unable to recreate this error:
bedtools --version
bedtools v2.25.0-114-g780faf7-dirty
bedtools intersect -wao -a contiguousAlignments.gff.gz -b annotatedExons.gff.gz > /dev/null

Could you please test this again with the version above?

Dear Aaaron,
thanks for looking into this again.
With the current version v2.25.0-116-ge88e919 the problem is indeed solved.
Will this fix be incorporated in the next release then?
Best regards,
Sarah

Great news. Yes, this will indeed be in the 2.26.0 release.

We today encountered this issue also but we already use 2.26.0. Is it possible that the bug is still present?


Mobile fixes

Fixed green labeled issues from the QA spreadsheet: https://docs.google.com/a/nd.edu/spreadsheets/d/1Vxr-PXJoYjZZtYuwA82VBtKbUeOan4I7p9jjZD7P7MU/edit?usp=sharing

@awetherill Can you address the hound issues that are complaining about the properties order?

:+1:

:+1:

:+1:


Refactor commandAction to return a Promise with async/await

Refactor commandAction to return a Promise with async/await. Closes #3430
I want to explicitly thank @Jwaegebaert for helping on this one ❤ 🥳

Refactors commandAction to return a promise
Refactors commandAction to use async/await

Hi @milanholemans ,
thank you. Awesome work.
I think it would be easier to rewrite the history of all your commits to one and then try to rebase it from our main before starting a review.
What do you think?
Cheers

Closing this one in favor of another PR where all commits are squashed.


python311Packages.aiomqtt: 1.2.1 -> 2.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.aiomqtt is: The idiomatic asyncio MQTT client, wrapped around paho-mqtt
meta.homepage for python311Packages.aiomqtt is: https://github.com/sbtinstruments/aiomqtt
meta.changelog for python311Packages.aiomqtt is: https://github.com/sbtinstruments/aiomqtt/blob/2.0.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.0 with grep in /nix/store/64r6ypzrckzjsa7g20abyg0g2j7ghiza-python3.11-aiomqtt-2.0.0
found 2.0.0 in filename of file in /nix/store/64r6ypzrckzjsa7g20abyg0g2j7ghiza-python3.11-aiomqtt-2.0.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.yolink
python311Packages.aiomqtt
python311Packages.yolink-api

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/64r6ypzrckzjsa7g20abyg0g2j7ghiza-python3.11-aiomqtt-2.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.aiomqtt https://github.com/r-ryantm/nixpkgs/archive/0569b0e619a39f02510ebbada2f35eadfd2c629a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0569b0e619a39f02510ebbada2f35eadfd2c629a#python311Packages.aiomqtt

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/64r6ypzrckzjsa7g20abyg0g2j7ghiza-python3.11-aiomqtt-2.0.0
ls -la /nix/store/64r6ypzrckzjsa7g20abyg0g2j7ghiza-python3.11-aiomqtt-2.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python311Packages.aiomqtt
python311Packages.yolink-api

Maintainer pings

Result of nixpkgs-review pr 282096 run on x86_64-darwin 1

4 packages built:

python311Packages.aiomqtt
python311Packages.aiomqtt.dist
python311Packages.yolink-api
python311Packages.yolink-api.dist


ubuntu 16.10 compiling pacakges

I compiled it successfully by adding those extra packages, quite heavy > 400 Mb, even much more on a fresh non graphic VM > 930 Mb.

Hi!
I only just now noticed this fork. Did you intend this PR to be targeted to the main repo? If you know this is what works on Ubuntu, I'd love to merge.


When will it be published in Markeplace on github ?

I like your githubaction, it is simple (no extra features) and concise. I would like to know when you plan to publish it in the github marketplace.
I think many people will find it useful.

I appreciate your compliments. I just published my action!
https://github.com/marketplace/actions/deploy-lambda-action


[BUG] Setting static requestSpecification multiple times stacks duplicates cookies and headers

For whatever reason setting the requestSpecification value multiple times causes unexpected side effects. Is this a groovy-ism under the hood or something? In any case I think it should be considered a bug. It took me a while to track down why my tests were replicating cookies/headers over and over again as more tests were run in large batches.
import io.restassured.RestAssured;
import org.junit.jupiter.api.Test;

import static io.restassured.RestAssured.get;
import static io.restassured.RestAssured.given;

public class blah {

    @Test
    public void before() {
        RestAssured.port = 80;
        RestAssured.requestSpecification = given()
                .header("header", "header-value")
                .cookie("cookie", "cookie-value");
        RestAssured.requestSpecification = given()
                .header("header", "header-value")
                .cookie("cookie", "cookie-value");
        RestAssured.requestSpecification = given()
                .header("header", "header-value")
                .cookie("cookie", "cookie-value");
        RestAssured.requestSpecification = given()
                .header("header", "header-value")
                .cookie("cookie", "cookie-value");
        get("http://www.google.com/");
    }
}

2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "GET / HTTP/1.1[\r][\n]"
2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "Cookie: cookie=cookie-value; cookie=cookie-value; cookie=cookie-value; cookie=cookie-value[\r][\n]"
2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "Accept: */*[\r][\n]"
2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "header: header-value[\r][\n]"
2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "header: header-value[\r][\n]"
2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "header: header-value[\r][\n]"
2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "header: header-value[\r][\n]"
2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "Host: www.google.com:80[\r][\n]"
2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "Connection: Keep-Alive[\r][\n]"
2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "User-Agent: Apache-HttpClient/4.5.5 (Java/9.0.4)[\r][\n]"
2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "Accept-Encoding: gzip,deflate[\r][\n]"
2019-11-21 09:28:24 DEBUG org.apache.http.wire -  >> "[\r][\n]"

given() return preconfigured specifications

@dr29bart Ah I see. I'll close this down then.


Entropy Maps

Hello! How to draw Entropy Maps in figure4.(b) in your paper? Will you update you code? Or you just visualize features of "pred_trg_entropy " in entropy_rank.py in line 167. Do you use some special tools?

Hi we just use a very simple visualization tool matplotlib to draw the entropy map.


Bug with connecting

I found 3 errors when running the packages:
error: TS2339 [ERROR]: Property 'resolveDns' does not exist on type 'typeof Deno'. 'Deno.resolveDns' is an unstable API. Did you forget to run with the '--unstable' flag?
  resolveDns: typeof Deno.resolveDns;
                          ~~~~~~~~~~
    at https://deno.land/x/mongo@v0.24.0/src/utils/srv.ts:15:27

TS2339 [ERROR]: Property 'resolveDns' does not exist on type 'typeof Deno'. 'Deno.resolveDns' is an unstable API. Did you forget to run with the '--unstable' flag?
  constructor(resolver = { resolveDns: Deno.resolveDns }) {
                                            ~~~~~~~~~~
    at https://deno.land/x/mongo@v0.24.0/src/utils/srv.ts:39:45

TS7006 [ERROR]: Parameter 'record' implicitly has an 'any' type.
    const servers = srvRecord.map((record) => {
                                   ~~~~~~
    at https://deno.land/x/mongo@v0.24.0/src/utils/srv.ts:86:36

Found 3 errors.

Code Used:
import { configs } from "../src/configs.ts"; // link to mongoose connection URL (string)
import { mongoose } from "./deps.ts"

// deno run --allow-read mod.ts

const client = new mongoose.MongoClient();

await client.connect(configs.mongodb.url);

deps.ts
export * as mongoose from<EMAIL_ADDRESS>
Mongo will not even start.

enable unstable API


modelgen: Separate API for data and template

This changes the API for Modelgen such that:

We call to get a *template.Template which can be modified with further calls to Parse
We call to GetXTemplateData to get the data for that template
It places Enum expansion inside it's own template

LGTM


fastdist does not wotk with python3.9 + numba 0.51.2 + numpy 1.19.4

Hello,
When I call examples from the fastdist I get the following errors:
from fastdist import fastdist
import numpy as np
a = np.random.rand(10, 100)
fastdist.matrix_pairwise_distance(a, fastdist.euclidean, "euclidean", return_matrix=False)
TypingError                               Traceback (most recent call last)
 in
3
4 a = np.random.rand(10, 100)
----> 5 fastdist.matrix_pairwise_distance(a, fastdist.euclidean, "euclidean", return_matrix=False)
/opt/venv/python3.9/lib/python3.9/site-packages/numba/core/dispatcher.py in _compile_for_args(self, *args, **kws)
413                 e.patch_message(msg)
414
--> 415             error_rewrite(e, 'typing')
416         except errors.UnsupportedError as e:
417             # Something unsupported is present in the user code, add help info
/opt/venv/python3.9/lib/python3.9/site-packages/numba/core/dispatcher.py in error_rewrite(e, issue_type)
356                 raise e
357             else:
--> 358                 reraise(type(e), e, None)
359
360         argtypes = []
/opt/venv/python3.9/lib/python3.9/site-packages/numba/core/utils.py in reraise(tp, value, tb)
78         value = tp()
79     if value.traceback is not tb:
---> 80         raise value.with_traceback(tb)
81     raise value
82
TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function() found for signature:

arange(int64)

There are 2 candidate implementations:

Of which 2 did not match due to:
Overload in function 'np_arange': File: numba/np/arrayobj.py: Line 3842.
With argument(s): '(int64)':
Rejected as the implementation raised a specific error:
UnsupportedError: Failed in nopython mode pipeline (step: analyzing bytecode)
Use of unsupported opcode (IS_OP) found

File "../../opt/venv/python3.9/lib/python3.9/site-packages/numba/np/arrayobj.py", line 3879:
    def impl(start, stop=None, step=None, dtype=None):
        <source elided>
        # Allow for improved performance if given literal arguments.
        lit_start = start_value if start_value is not None else start
        ^

raised from /opt/venv/python3.9/lib/python3.9/site-packages/numba/core/byteflow.py:269
During: resolving callee type: Function()
During: typing of call at /opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py (320)
File "../../opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py", line 320:
def cosine_pairwise_distance(a, return_matrix=False):

n = a.shape[0]
rows = np.arange(n)
^
During: resolving callee type: type(CPUDispatcher(<function cosine_pairwise_distance at 0x7fd0f85dd8b0>))
During: typing of call at /opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py (975)
During: resolving callee type: type(CPUDispatcher(<function cosine_pairwise_distance at 0x7fd0f85dd8b0>))
During: typing of call at /opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py (975)
File "../../opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py", line 975:
def matrix_pairwise_distance(a, metric, metric_name, return_matrix=False):

if metric_name == "cosine":
return cosine_pairwise_distance(a, return_matrix)
###########################################################################################
from fastdist import fastdist
import numpy as np
a = np.random.rand(25, 100)
b = np.random.rand(50, 100)
fastdist.matrix_to_matrix_distance(a, b, fastdist.euclidean, "euclidean")
TypingError                               Traceback (most recent call last)
 in
5 b = np.random.rand(50, 100)
6
----> 7 fastdist.matrix_to_matrix_distance(a, b, fastdist.euclidean, "euclidean")
8 # returns an array of shape (25, 50)
/opt/venv/python3.9/lib/python3.9/site-packages/numba/core/dispatcher.py in _compile_for_args(self, *args, **kws)
413                 e.patch_message(msg)
414
--> 415             error_rewrite(e, 'typing')
416         except errors.UnsupportedError as e:
417             # Something unsupported is present in the user code, add help info
/opt/venv/python3.9/lib/python3.9/site-packages/numba/core/dispatcher.py in error_rewrite(e, issue_type)
356                 raise e
357             else:
--> 358                 reraise(type(e), e, None)
359
360         argtypes = []
/opt/venv/python3.9/lib/python3.9/site-packages/numba/core/utils.py in reraise(tp, value, tb)
78         value = tp()
79     if value.traceback is not tb:
---> 80         raise value.with_traceback(tb)
81     raise value
82
TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Failed in nopython mode pipeline (step: nopython frontend)
Internal error at <numba.core.typeinfer.CallConstraint object at 0x7fd0f44248e0>.
Failed in nopython mode pipeline (step: analyzing bytecode)
Use of unsupported opcode (IS_OP) found
File "../../opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py", line 23:
def init_w(w, n):

"""
if w is None:
^
During: resolving callee type: type(CPUDispatcher(<function init_w at 0x7fd11bd73f70>))
During: typing of call at /opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py (364)
Enable logging at debug level for details.
File "../../opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py", line 364:
def euclidean(u, v, w=None):

n = len(u)
w = init_w(w, n)
^
During: resolving callee type: type(CPUDispatcher(<function euclidean at 0x7fd0f85dda60>))
During: typing of call at /opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py (985)
During: resolving callee type: type(CPUDispatcher(<function euclidean at 0x7fd0f85dda60>))
During: typing of call at /opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py (985)
During: resolving callee type: type(CPUDispatcher(<function euclidean at 0x7fd0f85dda60>))
During: typing of call at /opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py (934)
During: resolving callee type: type(CPUDispatcher(<function euclidean at 0x7fd0f85dda60>))
During: typing of call at /opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py (934)
File "../../opt/venv/python3.9/lib/python3.9/site-packages/fastdist/fastdist.py", line 934:
def matrix_to_matrix_distance(a, b, metric, metric_name):

for j in range(m):
out[i][j] = metric(a[i], b[j])
^

Hi,
Unfortunately I'm unable to replicate this error. When I run with the versions you've described, the code compiles with no errors. Perhaps there's something weird with different dependencies? I'll keep looking into it.
Thanks!


Livesearch device_list and ipaddress_list query_urls invalid

Issue type: Bug
Python version: 2.7.5
NetBox version: v2.0-beta1
The query_url settings for the Livesearch widget across various fields within the Circuits, DCIM and IPAM forms appear to refer to the old API naming convention where underscores were used (e.g. dcim-api:device_list vs dcim-api:device-list.
This causes any page utilising a livesearch field (which includes Add / Edit IP Address, Connect Interfaces etc) to throw a Fatal error, manifesting as something like:
NoReverseMatch: Reverse for 'ipaddress_list' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: []

Commit 46b8f3e3470fe56e5bae4c899756997343ac8a21 resolves this - happy to submit a PR if this is deemed the correct fix.

Looks like this has already been fixed in v2-develop as part of #997.


Preview/thumbnails

This is a big one, so I added everyone as reviewers.   Not everyone needs to review, though.  In this PR:
1.) Adds job using Shrine to generate thumbnail derivatives from uploaded files.  Right now we can process thumbnails for image types (like .pngs and .jpegs), .pdfs, and docxs.
2.) Users can toggle the display of an auto-generated thumbnail 'on' or 'off' from the Work and Collection settings pages.  It is defaulted to 'off' whenever a Work or Collection is created. The auto-generated thumbnail is displayed in the settings page so the user can see what it looks like before toggling on.  The 'Thumbnail' section of the settings page will not render if the Work or Collection does not have any thumbnails.
3.) Thumbnails (if one exists and auto-generate is toggled on) will display in place of the placeholder icons in the resource cards that show in the catalog, dashboard, featured page, and collections.  If no thumbnail exists or auto-generate is toggled off, the placeholder icons will show.
There are some system packages required to get the derivative creation to work if you are running the app locally.  The tests that require these packages are skipped locally with skip: !ci_build?, so you don't need to install this stuff to run the tests and develop.  If you do want to get the derivative creation working, the dockerfile documents what should be installed if you want this to work locally:
https://github.com/psu-libraries/scholarsphere/blob/preview/thumbnails/Dockerfile#L6-L10
The circle ci config also has this info.  You'll also need to configure ImageMagick to handle pdfs and docxs.
This PR completes checkbox 1, 3, 4, and 6 in #1114.  I'll finish up the rest in a separate branch/PR in the next sprint.  Also, we can work on handling more file types in the next sprint.
@whereismyjetpack Feel free to add to this.

Thanks @rschenk.  I'll try to get these changes in before lunch.  Then, we should be ready to go!


Create option to keep dhcp clients alive so they can manage (and renew) leases even after pipework exits

Per this Issue https://github.com/jpetazzo/pipework/issues/181 , give users option to keep udhcpc and dhclient around to manage the lease. Also updated README.md to describe how it works and how to manage it.

LGTM. Tanks for the contribution!

:-)


Update renovatebot/github-action action to v39.2.1

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
minor
v39.1.4 -> v39.2.1

Release Notes

renovatebot/github-action (renovatebot/github-action)
v39.2.1
Compare Source
Build System

deps: update dependency @semantic-release/github to v9.2.4 (588a09b)

Continuous Integration

deps: update renovate docker tag to v37.87.0 (2919482)
deps: update renovate docker tag to v37.87.2 (5c29fe4)

v39.2.0
Compare Source
Features

volume-mount: mount docker volumes as input (#797) (fcce0a0)

Documentation

update references to renovatebot/github-action to v39.1.4 (6846445)

Miscellaneous Chores

deps: lock file maintenance (225ff94)
deps: update dependency @types/node to v16.18.63 (73cf27f)
deps: update dependency @types/node to v16.18.64 (0459abb)
deps: update dependency @types/node to v16.18.65 (3e0f1fb)
deps: update linters to v6.12.0 (6d16470)
deps: update linters to v6.13.0 (6ea4d95)
deps: update linters to v6.13.1 (b2a5353)

Continuous Integration

deps: update renovate docker tag to v37.71.0 (a577ba0)
deps: update renovate docker tag to v37.74.3 (e10ef3b)
deps: update renovate docker tag to v37.77.1 (68dcaf4)
deps: update renovate docker tag to v37.81.0 (028a7a7)
deps: update renovate docker tag to v37.81.4 (19f74b2)
deps: update renovate docker tag to v37.83.0 (a42d58f)
deps: update renovate docker tag to v37.83.2 (42620a0)
deps: update renovate docker tag to v37.83.5 (6bd5cd8)

Configuration
📅 Schedule: Branch creation - "before 5am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Branch automerge failure
This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


Register provider via policy For ComputeFleet.

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run java - computefleet - ci

API change check
API changes are not detected in this pull request.


Android sound Android O+

For android 26+ setting sound doesn't work anymore. We need to create a channel on android.
So, this code not gonna work on newer versions of android.
$notification->setSound('police.wav');
this will
$notification->setSound('police.wav'); //old versions of android and ios $notification->setJsonKey('android_channel_id', 'noti_push_app_1'); //new android
Maybe, we could have something like
$notification->setSound('police.wav', 'noti_push_app_1' /*this part not been required*/);
or
$notification->setChannelId('noti_push_app_1');

@steks89 thanks for the new version.
I can receive the notification with my channel id but i don't have the sound.
I think that the device can not find the audio file.
What is your plugin.xml config ?
Plugin.xml


Support mender-partuuid feature

I added support for mender-partuuid feature.
Edit: signed off commit

please make small log text change (previous comment)
please modify commit message: feat: support mender-partuuid feature

otherwise looks good to me


onClone event fires even if the element is moved, not cloned

As mentioned on title, the onClone event fires even if the element is just moved, not cloned.
Besides that

onClone: function (ev) {  console.log(ev.clone) }
above code returns a DOM element that you can't even find on the document when you click the result on the console. but it's supposed to return nothing (when the pull is not set to "clone")

onClone: function (ev) {  console.log(ev.clone) }
if we check it with pull: 'clone', it returns the original element. but it's supposed to return the cloned element

console.log(ev.item ) should return the whole original element (with pull: 'clone'). but it's returning only the actual element without the nested childs

here's a preview of the issue https://codesandbox.io/s/hopeful-thompson-9t0q18?file=/src/index.js:1147-1178

Hmmm.. ?

seems issue_4 is solved (or maybe it was never there. the prob was on my browser). but what about the rest three?


Quickstrom intermittently fails and doesn't produce report.

Running into an intermittent issue where quickstrom will fail and not produce a valid HTML report. Not sure what the issue is that causes the failure but it seems to be related to the Web Driver. Attached is the error seen in the failed report. Note that re-running the command does produce a full report and quickstrom finishes as normal. The described behavior happens for 1 out of 10 tests.
Env info:

OS: [Ubuntu latest]
Quickstrom version or commit [latest]
Browser and webdriver information: [selenium/standalone-chrome:3.141.59-20200826 and Chrome]
Build environment or installation method [docker]

That's weird. It looks like some async webdriver call times out (30 seconds is the default in that client, AFAICT).
If you run with the console reporter, do you get the same limited error message?
Also, can build from source? Maybe you could remove the headless config and that way find out when the problem occurs.
As a final note, both error reporting and async handling is going to be greatly improved in the upcoming version 2 of Quickstrom. It's been a long time coming but I'm really looking forward to releasing that and helping people migrate over.


Allow send messages to user, not only to channel

Hi!
It's possible to send message to user by using "@username" as channel parameter.
For now, it's hardcoded to add # sign to channel name.
Below my patch that will add # sign only if channel name doesn't start with it nor with @ sign. So it's possible to send messages with "-c @username" option.
--- a/slacktee.sh
+++ b/slacktee.sh
@@ -98,7 +98,10 @@ function send_message(){
            message_attr="\"text\": \"$escaped_message\","
        fi

-        json="{\"channel\": \"#$channel\", \"username\": \"$username\", $message_attr \"icon_emoji\": \":$icon:\" $parseMode}"
+       if [[ ( "$channel" != "#"* ) && ( "$channel" != "@"* ) ]]; then
+               channel="#$channel"
+       fi
+        json="{\"channel\": \"$channel\", \"username\": \"$username\", $message_attr \"icon_emoji\": \":$icon:\" $parseMode}"
         curl -X POST --data-urlencode "payload=$json" "$webhook_url" &> /dev/null
     fi
 }

Thank you for the great improvement idea! I didn't know we can send direct message with @username.
I will implement the function based on your patch and publish it as soon as possible.

I just published v1.2.1 which support direct messaging using '@username' channel notation.
Thank you for letting me know your great idea!!


Updating README to include easier installation

Fixes #37, adds information on Homebrew installation

Thank you for your contribution 👍


XMLSchemaParseError: fractionDigits error

Attached xsd results in XMLSchemaParseError: fractionDigits require a {http://www.w3.org/2001/XMLSchema}decimal base type!
A new type is declared with base of xsd:decimal but when derived type is used it throws error.  Sample xsd attached.  (Couldn't attach xsd so I had to zip it)
Code resulting in error:
import xmlschema
path = "usage.xsd"
xs = xmlschema.XMLSchema(path)`

usage.xsd.zip

thx!


versions:set - add "removeSnapshot" property (squashed)

This PR supersedes https://github.com/mojohaus/versions-maven-plugin/pull/52. I took the liberty of squashing @designhaiku's commits into one, as per @tchemit's request.

The problem i have seeing what is really changed based on the format change...can you fix that?

@khmarbaise Certainly. I was trying to not to interfere with the original commits, but the formatting changes could be dropped from this PR.


[ORA-1613] Initial Value for emission per unit staked token = target

What is the purpose of the change
We calculate target emission and the emission rate on a monthly cadence. In the first month we have no previous history to use for the exponential moving average which returns e_i. Therefore, in that case, we use the target e_i instead of the exponential moving average, directly.
Testing and Verifying
Our existing tests should at least cover that this does not break anything
Documentation and Release Note
No Documentation changes needed.

we should close #481 and use this instead


Register

Registration pull request updated: JuliaRegistries/General/95301
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 786aa1af4d720f1abaac164295e7644cf30bf97d
git push origin v0.1.0


Dev: implement Password page

lock sign up/collection creation behind password for now

"as soon as you try to sign in, we can gate that with password page"


Running bash with box86 errors with Error initializing native libtinfo.so.6

Trying to run steamcmd.sh with bash, and it errors with Error: file is not found (check BOX64_PATH)
setting BOX86_LOG=1 lets us see that the problem is libtinfo.so.6:

Debug level is 1
Dynarec for ARMv8, with extension: HALF FAST_MULT EDSP NEON VFPv4 IDIVA PageSize:4096 Running on Neoverse-N1 with 4 Cores
Params database has 22 entries
Box86 with Dynarec v0.3.1 5cdc1b9f built on Jun 11 2023 02:04:53
Using default BOX86_LD_LIBRARY_PATH: ./:lib/:lib32/:x86/:i686/
Using default BOX86_PATH: ./:bin/
Counted 6 Env var
Looking for /root/box86/tests/bash
bash detected, disabling banner
argv[1]="/root/Steam/steamcmd.sh"
argv[2]="/bin/bash"
Rename process to "bash"
Error initializing native libtinfo.so.6 (last dlerror is libtinfo.so.6: cannot open shared object file: No such file or directory)
Error loading needed lib libtinfo.so.6
Error loading one of needed lib
Error: loading needed libs in elf /root/box86/tests/bash

I've tried installing these libraries with no luck : libncurses6 libncurses5 libtinfo5 libtinfo6
This is the Dockerfile I'm trying to run in a Oracle server with arm/v8:
FROM weilbyte/box:debian-11

RUN apt-get update && apt-get install -y \
    git \
    wget \
    libncurses6 libncurses5 libtinfo5 libtinfo6

# Download and install SteamCMD
RUN mkdir -p ~/Steam && \
    cd ~/Steam && \
    wget https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz && \
    tar zxvf steamcmd_linux.tar.gz && \
    chmod +x steamcmd.sh

RUN git clone https://github.com/ptitSeb/box86 ~/box86

ENV BOX86_LOG=1

ENTRYPOINT ["/usr/local/bin/box86", "/root/box86/tests/bash", "/root/Steam/steamcmd.sh"]

But running directly the steamcmd executable directly seems to work:
root@15265adcc673:/# /usr/local/bin/box86 /root/Steam/linux32/steamcmd
Dynarec for ARMv8, with extension: HALF FAST_MULT EDSP NEON VFPv4 IDIVA PageSize:4096 Running on Neoverse-N1 with 4 Cores
Params database has 22 entries
the x86_64 bash "/bin/bash" is not an x86_64 binary
Using default BOX86_LD_LIBRARY_PATH: ./:lib/:lib32/:x86/:i686/
Using default BOX86_PATH: ./:bin/
Counted 11 Env var
Looking for /root/Steam/linux32/steamcmd
steam detected
Rename process to "steamcmd"
Using native(wrapped) librt.so.1
Using native(wrapped) libdl.so.2
Using native(wrapped) libpthread.so.0
Using native(wrapped) libm.so.6
Using native(wrapped) libc.so.6
Using native(wrapped) ld-linux.so.2
Redirecting stderr to '/root/Steam/logs/stderr.txt'
Using native(wrapped) crashhandler.so
ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt".
[  0%] Checking for available update...
[----] Downloading update (0 of 59532 KB)...
[  0%] Downloading update (0 of 59532 KB)...
[  0%] Downloading update (0 of 59532 KB)...
[...]
[----] Installing update...
[----] Cleaning up...
[----] Update complete, launching...

Also reported here: https://github.com/ptitSeb/box86/issues/840

I had the same problem...
with box64 it works fine tho, so maybe try this?
By searching for an answer as well, I found out that libtinfo.so.6 somehow doesnt seem to exist on the system after installing "libncurses6 libncurses5 libtinfo5 libtinfo6". And someone on a forum wrote that it doesnt get shipped with some versions of them. So using a different source for those packages might be the answer to solving this problem.


animateToCoordinate sends me to Africa

this._map.animateToCoordinate({
coordinate: {
                      latitude: 28.869236999,
                      longitude: -81.234822999
                    }},
                    2);

<MapView ref={(map)=>this._map = map}

Even with explicitly defined coordinates...

You shouldn't be putting the extra "coordinate:" key in your call.
This works for me:
this._map.animateToCoordinate({
  latitude: 28.869236999,
  longitude: -81.234822999
}, 2);

How do you use this if the mapView is under MapView.Animated

@jeffreymendez1993
this._map._component.animateToCoordinate({
  latitude: 28.869236999,
  longitude: -81.234822999
}, 2);

The documentation is misleading. https://github.com/airbnb/react-native-maps/blob/master/docs/mapview.md
Same problem

what's wrong with Africa, racist 😒


Error with Xformers newest version

I'm trying to run this using Xformers 0.0.25 because I have to run latest Torch 2.2.1 which Google Colab just updated to, and xformers 0.0.24 only works with Torch 2.2.0, so installing 0.0.24 takes ~5 minutes and a Restart to downgrade to torch 2.2.0.  I got it working in my app at DiffusionDeluxe.com using the recommended 0.0.24 (although keeps running out of RAM), but with 0.0.25 I'm getting this error:
Traceback (most recent call last):
  File "/content/sdd_colab.py", line 46547, in run_crm
    crm_model = CRM(specs).to(torch_device)
  File "/content/CRM/model/crm/model.py", line 46, in __init__
    self.unet2 = UNetPP(in_channels=self.dec.c_dim)
  File "/content/CRM/model/archs/unet.py", line 43, in __init__
    self.unet.enable_xformers_memory_efficient_attention()
  File "/usr/local/lib/python3.10/dist-packages/diffusers/models/modeling_utils.py", line 295, in enable_xformers_memory_efficient_attention
    self.set_use_memory_efficient_attention_xformers(True, attention_op)
  File "/usr/local/lib/python3.10/dist-packages/diffusers/models/modeling_utils.py", line 259, in set_use_memory_efficient_attention_xformers
    fn_recursive_set_mem_eff(module)
  File "/usr/local/lib/python3.10/dist-packages/diffusers/models/modeling_utils.py", line 255, in fn_recursive_set_mem_eff
    fn_recursive_set_mem_eff(child)
  File "/usr/local/lib/python3.10/dist-packages/diffusers/models/modeling_utils.py", line 255, in fn_recursive_set_mem_eff
    fn_recursive_set_mem_eff(child)
  File "/usr/local/lib/python3.10/dist-packages/diffusers/models/modeling_utils.py", line 255, in fn_recursive_set_mem_eff
    fn_recursive_set_mem_eff(child)
  File "/usr/local/lib/python3.10/dist-packages/diffusers/models/modeling_utils.py", line 252, in fn_recursive_set_mem_eff
    module.set_use_memory_efficient_attention_xformers(valid, attention_op)
  File "/usr/local/lib/python3.10/dist-packages/diffusers/models/attention_processor.py", line 253, in set_use_memory_efficient_attention_xformers
    raise ModuleNotFoundError(
ModuleNotFoundError: Refer to https://github.com/facebookresearch/xformers for more information on how to install xformers

I'm hoping you can figure out a solution to fix the breaking change to make it compatible with both, but always nice to be using the newest versions.  Thanks, tried to trace the problem down myself, but didn't understand it enough.

My testing environment is torch==1.13.0+cu117. Maybe you can try torch 1.x? I am not sure whether will torch 2.x work.

I have tested a new environment (torch2.2.2+cu118), and used the newest xformers.
You can use the offcial method to get the newest version.
# cuda 11.8 version
pip3 install -U xformers --index-url https://download.pytorch.org/whl/cu118

Here are my steps:
# python.version //3.8
# print(torch.__version__) //2.2.2+cu118
git clone https://github.com/thu-ml/CRM.git
cd CRM
pip install -r requirements.txt
pip install ninja
pip3 install -U xformers --index-url https://download.pytorch.org/whl/cu118
pip install git+https://github.com/NVlabs/nvdiffrast
# other package(forget)

I made a docker image in CodeWithGPU platform, Here are the page: Page Link.
It is under reviewing and will take two days.
docker pull registry.cn-beijing.aliyuncs.com/codewithgpu2/thu-ml-crm:x00G39kpFb

Along the way, I also encountered some strange things:

I found the .pth and .bin files will be storaged in the ./.cache/huggingface/hub/model*, it  is difficult for me to move them directly.

I can not run the code python run.py "imgfile" in juypter, it will raise errors about Connection with huggingface.co, but I can run this code in the terminal.

I have tested a new environment (torch2.2.2+cu118), and used the newest xformers. You can use the offcial method to get the newest version.
# cuda 11.8 version
pip3 install -U xformers --index-url https://download.pytorch.org/whl/cu118

Here are my steps:
# python.version //3.8
# print(torch.__version__) //2.2.2+cu118
git clone https://github.com/thu-ml/CRM.git
cd CRM
pip install -r requirements.txt
pip install ninja
pip3 install -U xformers --index-url https://download.pytorch.org/whl/cu118
pip install git+https://github.com/NVlabs/nvdiffrast
# other package(forget)

I made a docker image in CodeWithGPU platform, Here are the page: Page Link. It is under reviewing and will take two days.
docker pull registry.cn-beijing.aliyuncs.com/codewithgpu2/thu-ml-crm:x00G39kpFb

Along the way, I also encountered some strange things:

I found the .pth and .bin files will be storaged in the ./.cache/huggingface/hub/model*, it  is difficult for me to move them directly.
I can not run the code python run.py "imgfile" in juypter, it will raise errors about Connection with huggingface.co, but I can run this code in the terminal.

Thanks a lot! I solved my issues by installing xformers: pip3 install -U xformers --index-url https://download.pytorch.org/whl/cu118.


Unclear directions for locating .bashrc or .profile file in Windows

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows
What part(s) of the article would you like to see updated?
The Windows portion of the article is unclear about where to find the \.bashrc or \.profile file in the Git shell.
Currently, the sentence reads as:

You can run ssh-agent automatically when you open bash or Git shell. Copy the following lines and paste them into your ~/.profile or ~/.bashrc file in Git shell:

This may be unclear to someone without a bash/linux - based background.
Expected outcome: Add directions to locating the \.bashrc or \.profile for Windows users.
Additional information
No response

@victoremeka Thank you for opening an issue and linking it to your PR! ✨

Closing per comment here 💛


Contradictory instruction in flutter-firebase codelab 6, GoogleService-Info.plist

According to step 6 in the flutter-firebase codelab:

Add the bundle ID and the reverse URL of your client id to the main dictionary of your app's GoogleService-Info.plist file

According to https://pub.dartlang.org/packages/google_sign_in

Then add the CFBundleURLTypes attributes below into the [my_project]/ios/Runner/Info.plist file.

The two instructions contradict each other. I ended up using the latter and it worked.

@jmnyv this has been updated.

Closing per last comment. Thanks!


Add class cell to method scopes.

This is a basic implementation that I think should be good enough for __super__ to work.
This should be passed through to the metaclass to allow some more advanced trickery, but I think this is good enough. There's a more optimal implementation than a whole dictionary just for this, which we can sort when we come to optimise local variables.

A cellvar is the just cpython name/implementation for variables that captured from non-local, non-global scopes/the optimisation that makes them fast. I may be vague on the details too!


Remove the limitation that incremental annotation processors must not depend on com.sun.source.util.Trees

Description
This current limitation prevent spring boot to enable incremental annotation processing. Therefore an enormous number of developers are having a build time penalty because of this limitation and Kotlin users (KAPT) have by default a warning.
You can follow the original issue here:
https://github.com/spring-projects/spring-boot/pull/16603
I feel like this should be somewhat prioritized.
Expected Behavior
No such limitation, at least for the Trees API
Current Behavior
Non-incremental annotation processing on the most popular backend framework

The limitation is present in the Gradle 6.3 documentation

They must not depend on compiler-specific APIs like com.sun.source.util.Trees. Gradle wraps the processing APIs, so attempts to cast to compiler-specific types will fail. If your processor does this, it cannot be incremental, unless you have some fallback mechanism.

https://docs.gradle.org/6.3/userguide/java_plugin.html#sec:incremental_annotation_processing


add Simplified Chinese prefix of Gherkin language

Support for Given/When/Then prefixes using other languages than English was added in RF 6.0 (#519) along with other translation related enhancements. This PR is thus outdated.


even_odd_site.cc

Description Program does not compile.
Steps to Reproduce
First step Run program.
Expected Behavior Should print numbers from file sorted by even/odd.
Actual Behavior Compiler error.
Operating System: Windows
Browser: Google Chrome
Possible Solution In for loop, change i+ to i++ to increment the loop.
Priority High priority
Reproducibility Always

Fixed it


Bugfix distribution-algorithm, improved algorithm, better debugging

Bugfix for the distribution algorithm in info.py.
Now it actually creates an even distribution of assignments.

Thanks


[C] Change log_file_name to fixed size string

It would be better to adjust the size of the allocate to add the string at the end of the struct and simply point the pointer at it. Thus 1 alloc and no wasted space.

I didn't got your idea, you can pick and modify my patch to show you idea

Closing due to lack of progress.


Is there "Got it" button support for this library. It will be so good , if this thing is there. Can anybody tell answer me.

[x] I have verified the issue exists on the latest version
[ ] I am able to reproduce it

Version used:
Stack trace:
Android version:

Some other applications using some showcase library are having this feature.

This doesn't conform to the material design guidelines, so no.


iOS AppDelegate changes no longer permit configuring a loading view fade delay to avoid native -> JS "white flash"

New Version
0.71.1
Old Version
0.70.6
Build Target(s)
iOS
Output of react-native info
System:
OS: macOS 13.2
CPU: (10) arm64 Apple M1 Pro
Memory: 85.22 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 19.4.0 - /private/var/folders/lx/8pd1v4bj6656dm288zdsl9p00000gn/T/xfs-1926afa9/node
Yarn: 3.3.1 - /private/var/folders/lx/8pd1v4bj6656dm288zdsl9p00000gn/T/xfs-1926afa9/yarn
npm: 9.2.0 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /Users/craig/.rvm/gems/ruby-2.7.6/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK:
API Levels: 24, 25, 26, 27, 28, 29, 30, 31, 33
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.1, 30.0.2, 30.0.3, 31.0.0, 33.0.0
System Images: android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom_64, android-30 | Google Play Intel x86 Atom, android-30 | Google Play Intel x86 Atom_64
Android NDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: 11.0.12 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.1 => 0.71.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Issue and Reproduction Steps
First of all, thank you for all the hard work improving React Native! The changes made to both the Android and iOS setup configs are great (and welcomed) however we are running into a challenge on iOS. Previously we could write something like the following:
NSDictionary *initProps = [self prepareInitialProps];
RCTRootView *rootView = (RCTRootView *)RCTAppSetupDefaultRootView(bridge, @"ExampleApp", initProps);

if (@available(iOS 13.0, *)) {
  rootView.backgroundColor = [UIColor systemBackgroundColor];
} else {
  rootView.backgroundColor = [UIColor whiteColor];
}

self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
UIViewController *rootViewController = [UIViewController new];
rootViewController.view = rootView;
self.window.rootViewController = rootViewController;
[self.window makeKeyAndVisible];

UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
UIView *loadingView = [[storyboard instantiateInitialViewController] view];
[rootView setLoadingView:loadingView];
rootView.loadingViewFadeDelay = 0.5;
rootView.loadingViewFadeDuration = 0.5;

to, in the user's eyes, delay the fade out of the launch screen to avoid the white flash between the native launch screen and our JS "splash" screen. This has been working well for countless releases. With the root view logic being internalized to the RN setup, it is not clear how to keep this behavior (if at all possible). From what I gather, the new architecture doesn't have a mechanism to accomplish this either. So the ask is 1) expose some config variables for (existing architecture) to keep this functionality in place for those that currently use it 2) implement a way for the new architecture to have this same behavior (eventually the switch will be made).

Potential workaround:
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  self.moduleName = @"MainApp";
  // You can add your custom initial props in the dictionary below.
  // They will be passed down to the ViewController used by React Native.
  self.initialProps = @{};

  BOOL success = [super application:application didFinishLaunchingWithOptions:launchOptions];
  if (success) {
    // Modify as needed to match the main color of your splash.
    self.window.rootViewController.view.backgroundColor = [UIColor colorNamed:@"primary"];
  }
  return success;
}

@mysport12
this worked for me:
  UIStoryboard *sb = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];   UIViewController *vc = [sb instantiateInitialViewController];   ((RCTRootView *)self.window).loadingView = vc.view;

@alpha0010 your solution didn't get me all the way there but provided me with enough insight to get things working as intended (see below)
BOOL success = [super application:application didFinishLaunchingWithOptions:launchOptions];
if (success) {
  RCTRootView *rootView = (RCTRootView *)self.window.rootViewController.view;
  UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
  [rootView setLoadingView:[[storyboard instantiateInitialViewController] view]];
  rootView.loadingViewFadeDelay = 0.5;
  rootView.loadingViewFadeDuration = 0.5;
}
return success;

@jafar-jabr I couldn't seem to get your solution to work as is but like alpha's proposed solution, gave me clues into what I needed to do.

hello @mysport12 can you please show a little bit more of your code, I am still unable to solve this :/ Did you place your code inside of this - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions code block? Thank you

@mysport12 Running into the exact same issue, thanks for posting. I used your example to do something a little different and thought I'd post too in case it's helpful to anyone. For reference, I am also using Codepush and react-native-bootsplash.
This is what my launch options looked like at React Native 0.70.0
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
  RCTAppSetupPrepareApp(application);

  RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:launchOptions];

  #if RCT_NEW_ARCH_ENABLED
  _contextContainer = std::make_shared<facebook::react::ContextContainer const>();
  _reactNativeConfig = std::make_shared<facebook::react::EmptyReactNativeConfig const>();
  _contextContainer->insert("ReactNativeConfig", _reactNativeConfig);
  _bridgeAdapter = [[RCTSurfacePresenterBridgeAdapter alloc] initWithBridge:bridge contextContainer:_contextContainer];
  bridge.surfacePresenter = _bridgeAdapter.surfacePresenter;
  #endif

  NSDictionary *initProps = [self prepareInitialProps];
  UIView *rootView = RCTAppSetupDefaultRootView(bridge, @"RnDiffApp", initProps);

  if (@available(iOS 13.0, *)) {
    rootView.backgroundColor = [UIColor systemBackgroundColor];
  } else {
    rootView.backgroundColor = [UIColor whiteColor];
  }

  self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  UIViewController *rootViewController = [UIViewController new];
  rootViewController.view = rootView;
  self.window.rootViewController = rootViewController;
  [self.window makeKeyAndVisible];
  return YES;
}

This is what it looked like after 0.71.0:
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
self.moduleName = @"App Name";
return [super application:application didFinishLaunchingWithOptions:launchOptions];
}

Big difference! rootView was completely gone so I couldn't set backgroundColor that way anymore. Here is what worked for me after tailoring your solution.
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
  self.moduleName = @"App Name";
  BOOL success = [super application:application didFinishLaunchingWithOptions:launchOptions];

  // Hide the Codepush white flash
  if (success) {
    RCTRootView *rootView = (RCTRootView *)self.window.rootViewController.view;
    rootView.backgroundColor = [[UIColor alloc] initWithRed:0.13 green:0.13 blue:0.13 alpha:1];
  }
  return success;
}

Actually, you can do whatever you want with the RootView.
The RCTAppDelegate.h exposes methods that you can override in order to customise your views.
For example, this method allows you to get the default UIView * and to customise it:
//in your AppDelegate.mm

- (UIView *)createRootViewWithBridge:(RCTBridge *)bridge
                          moduleName:(NSString *)moduleName
                           initProps:(NSDictionary *)initProps
{
  UIView * rootView = [super createRootViewWithBridge:bridge moduleName:moduleName initProps:initProps];

  // set your background color

  Return rootView;
}

And there are a method to customise the view controller if needed.
I’m sorry to see this issue only now.

Thanks @gabriellend, the suggested code worked out great.

@zallanx @gabriellend @mysport12 @jafar-jabr @alpha0010: please, refer to my comment above as the proper way to customise your Views and ViewControllers is to override template methods the RCTAppDelegate.h class provides you.
Let me know if they work (as they should). Meanwhile, I'll close this issue.

Here is another example that worked for me:
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
  self.moduleName = @"RnDiffApp";

  [super application:application didFinishLaunchingWithOptions:launchOptions];

  // Hide white flash
  self.window.rootViewController.view.backgroundColor = [[UIColor alloc] initWithRed:0.13 green:0.13 blue:0.13 alpha:1];

  return YES;
}

@cipolleschi Where would that snippet go in AppDelegate? In launch options?

@gabriellend That's another method of the app delegate.
So you can just add the snippet below the application:didFinishLaunchingWithOption:
So, something like:

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
  self.moduleName = @"RnDiffApp";

  return [super application:application didFinishLaunchingWithOptions:launchOptions];
}

- (UIView *)createRootViewWithBridge:(RCTBridge *)bridge
                          moduleName:(NSString *)moduleName
                           initProps:(NSDictionary *)initProps
{
  UIView * rootView = [super createRootViewWithBridge:bridge moduleName:moduleName initProps:initProps];

  rootView.backgroundColor = [[UIColor alloc] initWithRed:0.13 green:0.13 blue:0.13 alpha:1];

  return rootView;
}

This should simplify the app code quite a bit, limiting the possibility that something can go wrong! 😉

@cipolleschi I was able to get that approach to work for preventing the flash, but the storyboard launch screen size was all out of whack so for now will stick with the original approach I posted above (in 'didFinishLaunchingWithOptions) for my use case. Agree though that for setting a background color it works perfectly fine

Uhm.. @mysport12 that should not be the case...
Just to make sure, your code of the createRootView was something like this?

- (UIView *)createRootViewWithBridge:(RCTBridge *)bridge
                          moduleName:(NSString *)moduleName
                           initProps:(NSDictionary *)initProps
{
  UIView * rootView = [super createRootViewWithBridge:bridge moduleName:moduleName initProps:initProps];
  UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
  [rootView setLoadingView:[[storyboard instantiateInitialViewController] view]];
  rootView.loadingViewFadeDelay = 0.5;
  rootView.loadingViewFadeDuration = 0.5;

return rootView;

?
React Native does nothing specific with the View Controller, so as long as you use the UIView created by the framework, you should be good...
Also, why you need to access the storyboard to retrieve the loading view? Can't it be init in isolation?
(I'm trying to understand the use case, to make sure we can support everyone of you! 😊)

Yes that's correct. Only difference being the rootView declared as RCTRootView to have access to the loading view methods/params.
- (UIView *)createRootViewWithBridge:(RCTBridge *)bridge
                          moduleName:(NSString *)moduleName
                           initProps:(NSDictionary *)initProps
{
  RCTRootView * rootView = (RCTRootView *)[super createRootViewWithBridge:bridge moduleName:moduleName initProps:initProps];
  UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
  [rootView setLoadingView:[[storyboard instantiateInitialViewController] view]];
  rootView.loadingViewFadeDelay = 0.5;
  rootView.loadingViewFadeDuration = 0.5;

  return rootView;

We want the loading view to be the launch screen which just has a background color and a centered image (some of my apps have a slightly more complicated image arrangement). That way launch -> loading -> JS splash are consistent so the user doesn't perceive a difference as those transitions take place.
The behavior witnessed was that the centered image was scaled pretty large to the point where it was clipped by the edges of the device. It almost seems like the bounds weren't correct. Could it be the order of operations of when the following line gets called?
self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
in the code block from the AppDelegate.mm from react native
UIView *rootView = [self createRootViewWithBridge:self.bridge moduleName:self.moduleName initProps:initProps];

  if (@available(iOS 13.0, *)) {
    rootView.backgroundColor = [UIColor systemBackgroundColor];
  } else {
    rootView.backgroundColor = [UIColor whiteColor];
  }

  self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  UIViewController *rootViewController = [self createRootViewController];
  rootViewController.view = rootView;
  self.window.rootViewController = rootViewController;
  [self.window makeKeyAndVisible];

Prior to 0.71.0 when our individual apps called the code, the self.window logic was executed prior to the loading view logic. Just spitballing. I will try and dig into it more tonight/tomorrow.

The gist of the above being that it seems to work when the loading view is set AFTER the window is set. Combined approaches with code snippets below for conciseness
Pre 0.71.0 (working):
self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
   UIViewController *rootViewController = [UIViewController new];
   rootViewController.view = rootView;
   self.window.rootViewController = rootViewController;
   [self.window makeKeyAndVisible];

   UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
   UIView *loadingView = [[storyboard instantiateInitialViewController] view];
   [rootView setLoadingView:loadingView];
   rootView.loadingViewFadeDelay = 0.5;
   rootView.loadingViewFadeDuration = 0.5;
   return YES;

0.71.X BOOL success = [super application:application didFinishLaunchingWithOptions:launchOptions]; (working):
BOOL success = [super application:application didFinishLaunchingWithOptions:launchOptions];
  if (success) {
    RCTRootView *rootView = (RCTRootView *)self.window.rootViewController.view;
    UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
    [rootView setLoadingView:[[storyboard instantiateInitialViewController] view]];
    rootView.loadingViewFadeDelay = 0.5;
    rootView.loadingViewFadeDuration = 0.5;
  }
  return success;

0.71.X createRootViewWithBridge (not working - launch screen image scaling oversized):
- (UIView *)createRootViewWithBridge:(RCTBridge *)bridge
                          moduleName:(NSString *)moduleName
                           initProps:(NSDictionary *)initProps
{
  RCTRootView * rootView = (RCTRootView *)[super createRootViewWithBridge:bridge moduleName:moduleName initProps:initProps];
  UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
  [rootView setLoadingView:[[storyboard instantiateInitialViewController] view]];
  rootView.loadingViewFadeDelay = 0.5;
  rootView.loadingViewFadeDuration = 0.5;

  return rootView;

Appreciate the dialog and the assistance on this FWIW. It seems to have helped others as well which is always beneficial.

@cipolleschi Ok I tried your example but it didn't take care of the white flash so I'm just going to stick with my original fix. The white flash happens when CodePush finishes downloading the new JS bundle and the JS app is restarted. I don't know enough to add any hypotheses of why your solution didn't work in my case, but I really appreciate your help!

Oh.. I understood what's the culprit.
What we did, to simplify the client code, was to encapsulate the initialization logic into the RCTAppDelegate class. The reason is that , in that way, we can minimize changes for you in the future, with the hope not to touch the AppDelegate ever again (I guess you'd love a simplified update experience, right?).
In doing so, we moved the code as it was to that class, adding some hooks you can override to further customization.
Among these hooks, there is createRootViewWithBridge that is used to create the view at line 55. The problem is that, 2 lines below, we preset the background color for you.
So, given that you are actually updating the only property the AppDelegate is modifying, your change get lost. :(
So sorry for this. I'll create a task for myself to expose a last resort method to customize the rootViewController, hence giving you the final word on it and on its rootViewController.view objects.
How does this sound?
I'm sorry for the disruption it may has caused.

@cipolleschi I'm not familiar enough with the native side of things to totally follow so this could be wrong but the line of code you reference at your link for "we preset the background color" is no longer present in React Native 0.71. It sounds like you are saying that since it's being set there, any changes we make later (i.e. with your new code) are being overridden. But in 0.71, that "setting" block is gone so it seems like it's not being set and therefore not overriding anything. I don't know if that's clear. If you want to find another solution that is better, that would be great, but honestly I'm happy with the solution I found for now. It's not been a huge disruption at all, and I thank you for your attention to this issue.

I'm seeing a blank white screen before my splash screen after upgrading too.
Previously I solved the problem by adding this snippet below into didFinshLaunching:
self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  UIViewController *rootViewController = [UIViewController new];
  rootViewController.view.backgroundColor = [UIColor colorWithRed:1.00 green:0.00 blue:0.40 alpha:1.00];
  self.window.rootViewController = rootViewController;
  [self.window makeKeyAndVisible];

I tried using what you suggested @cipolleschi but I didn't have any luck.

Hi @gtokman, you are right.
Currently, there is a bug in RN 0.71 for the backgroundColor only, as explained it here. Basically, you can customize the view, but then we will replace the background color. 🤦
This will be fixed in 0.72, but I can try to backport it to 0.71.
Meanwhile, what you can do is the following:
// In AppDelegate
 - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  self.moduleName = @"InteropApp";
  // You can add your custom initial props in the dictionary below.
  // They will be passed down to the ViewController used by React Native.
  self.initialProps = @{};
-  return [super application:application didFinishLaunchingWithOptions:launchOptions];
+ BOOL result = [super application:application didFinishLaunchingWithOptions:launchOptions];
+  self.window.rootViewController.view.backgroundColor = [UIColor colorWithRed:1.00 green:0.00 blue:0.40 alpha:1.00];
+  return result;
}

And it will do the trick

@cipolleschi How i can show the splash screen in the transition ,instead of showing a background color as u did above?

Property 'loadingView' not found on object of type 'UIView *'

Ok, I think that you can do it similarly to what I suggested above:
// In AppDelegate
 - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  self.moduleName = @"InteropApp";
  // You can add your custom initial props in the dictionary below.
  // They will be passed down to the ViewController used by React Native.
  self.initialProps = @{};
-  return [super application:application didFinishLaunchingWithOptions:launchOptions];
+ BOOL result = [super application:application didFinishLaunchingWithOptions:launchOptions];
+ UIStoryboard *sb = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
+ UIViewController *vc = [sb instantiateInitialViewController];
+ self.window.rootViewController.view.loadingView = vc.view;
+ return result;
}

Property 'loadingView' not found on object of type 'UIView *'

Right, because the View returned by the rootViewController is a UIView *, but you can safely downcast it to RCTRootView.
So, the code I posted above must be changed to:
//....
RCTRootView * rootView = (RCTRootView *) self.window.rootViewController.view;
rootView.loadingView = vc.view;
Return result;

+ BOOL result = [super application:application didFinishLaunchingWithOptions:launchOptions];
+  self.window.rootViewController.view.backgroundColor = [UIColor colorWithRed:1.00 green:0.00 blue:0.40 alpha:1.00];
+  return result;

After it's fixed in a future release, should we still do it this way?

@Dajust No, after the fix lands, the right way to do it will be to override the createRootViewWithBridge in your AppDelegate:
- (UIView *)createRootViewWithBridge:(RCTBridge *)bridge
                          moduleName:(NSString *)moduleName
                           initProps:(NSDictionary *)initProps
{
  // get the base, preconfigured view for React native
  UIView * view = [super createRootViewWithBridge:bridge
                          moduleName:moduleName
                           initProps:initProps];
  // Add your customisations
  view.backgroundColor = [UIColor colorWithRed:1.00 green:0.00 blue:0.40 alpha:1.00];

  // Return the customised view
  return view;
}

Hey all,
In case someone struggles as I did with showing a splash screen instead of the custom background, here's the code snippet which works for me with react-native-bootsplash library.
❗Note: order matters 😅
  self.initialProps = @{};

  BOOL result = [super application:application didFinishLaunchingWithOptions:launchOptions];

  [RNBootSplash initWithStoryboard:@"BootSplash" rootView:self.window.rootViewController.view];

  // Hide white flash
  self.window.rootViewController.view.backgroundColor = [UIColor colorWithRed: 0.03 green: 0.09 blue: 0.24 alpha: 1.00];;

  return result;

Hi @professorkolik, thank for the question. Let me understand, it's only a matter of updating the doc or you feel blocked somehow?
The proper way to apply these changes:
UIStoryboard *sb = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
  UIViewController *vc = [sb instantiateInitialViewController];
  rootView.loadingView = vc.view;

In 0.71 and onward, is to override
- (UIView *)createRootViewWithBridge:(RCTBridge *)bridge
                          moduleName:(NSString *)moduleName
                           initProps:(NSDictionary *)initProps;

in your AppDelegate.mm with something like:
- (UIView *)createRootViewWithBridge:(RCTBridge *)bridge
                          moduleName:(NSString *)moduleName
                           initProps:(NSDictionary *)initProps
{
  let rootView = [super createRootViewWithBridge:bridge moduleName:moduleName initProps:initProps];

  // workaround:
  UIStoryboard *sb = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
  UIViewController *vc = [sb instantiateInitialViewController];
  rootView.loadingView = vc.view;

  return rootView;
}

We can update the documentation with this approach, if that's what you were looking for (or we welcome contributions to the website too! 😄 It is backed by this GitHub repo: https://github.com/facebook/react-native-website ).

@cipolleschi Thank you for response!
It's both documentation and block. And one comes from other, so we are blocked and I think may be I do smth wrong.
I tried all the suggestions. It actually works, but not as expected or not as before.
To give a background:
We had a UIStoryBoard with app icon, when the bundle loaded we have the same SplashScreen component but with loading indicator, when StoryBoard hides for our users there is no change in behaviour just loading spinner appears.
When I implement new way of controlling the Flash screen. I got behaviour that UIStoryBoard hides but with animation.
I checked in sources of RCTRootView that animation is applied with 2 options
_loadingViewFadeDelay = 0.25;
_loadingViewFadeDuration = 0.25;

Changing this values to 0, doesn't work as well.
To summarize, if I just put the solution from docs into didFinishLaunchingWithOptions of RCTAppDelegate.mm, between
[self.window makeKeyAndVisible] and before return YES; I'm getting desired behaviour
Thank you again, any hint is appreciated 🙏

Ah... that's weird. 🤔
The two behaviors should be identical.
Just to make sure, you changed the private _loadingXXX props or did you act on these?
Would you be able to prepare a simple reproducer using this template?

Just to make sure, you changed the private _loadingXXX props or did you act on these?

Both tried 😄

Would you be able to prepare a simple reproducer using this template?

Definitely, though might take some time, thank you

Hi @cipolleschi
Just trying to work out, with version 0.71.xx, the correct way to go about preventing the blank screen flash between the splash screen and the display of the root application view.
These are the, now outdated but still live docs. Have tried the solutions on this thread but no luck so far.

@joegoodall1 thanks for trying. Yeah, that doc is live but outdated.
If you could create a repro using the template above, I can try to figure out how to fix it properly and then I'll update the doc accordingly.

@cipolleschi
Here you go https://github.com/joegoodall1/whiteflashsplash
Intentionally extremely simple changes (changed backgrounf of splash screen and 1st RN screen to red so white flash is visible)
https://github.com/facebook/react-native/assets/8888799/5aeb29ce-f141-4aac-a335-688a4364bea7

@joegoodall1 before @cipolleschi will take a look, I don't see you applied suggested changes in AppDelegate.mm file.
So I'm not sure what you expect

@professorkolik Thanks for the quick response
Do you mean like this?
#import "AppDelegate.h"

#import <React/RCTBundleURLProvider.h>

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  self.moduleName = @"ReproducerApp";
  // You can add your custom initial props in the dictionary below.
  // They will be passed down to the ViewController used by React Native.
  self.initialProps = @{};

  return [super application:application didFinishLaunchingWithOptions:launchOptions];
}

- (UIView *)createRootViewWithBridge:(RCTBridge *)bridge
                          moduleName:(NSString *)moduleName
                           initProps:(NSDictionary *)initProps
{
  let rootView = [super createRootViewWithBridge:bridge moduleName:moduleName initProps:initProps];

  // workaround:
  UIStoryboard *sb = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
  UIViewController *vc = [sb instantiateInitialViewController];
  rootView.loadingView = vc.view;

  return rootView;
}

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
#if DEBUG
  return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index"];
#else
  return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif
}

@end

Seeing this error with that code

@joegoodall1 let is a typo you don't need it, remove it
maybe you'll need to type rootViiew
UIView *rootView = .....

@cipolleschi @professorkolik
Now seeing this error

I tested the repro and with the proper patch, it is fixed (no white flash anymore). This is the right fix for both architectures:
// At the beginning of the AppDelegate.mm file

#import <React/RCTRootView.h>
#if RCT_NEW_ARCH_ENABLED
#import <React/RCTFabricSurfaceHostingProxyRootView.h>
#endif

// ...

- (UIView *)createRootViewWithBridge:(RCTBridge *)bridge
                          moduleName:(NSString *)moduleName
                           initProps:(NSDictionary *)initProps
{
  UIView * view = [super createRootViewWithBridge:bridge moduleName:moduleName initProps:initProps];

#if RCT_NEW_ARCH_ENABLED
  RCTFabricSurfaceHostingProxyRootView * rootView = (RCTFabricSurfaceHostingProxyRootView *)view;
#else
  RCTRootView * rootView = (RCTRootView *)view;
#endif

  // workaround:
  UIStoryboard *sb = [UIStoryboard storyboardWithName:@"LaunchScreen" bundle:nil];
  UIViewController *vc = [sb instantiateInitialViewController];
  rootView.loadingView = vc.view;

  return rootView;
}

The createRootViewWithBridge method returns a different UIView * based on the architecture you are building against.
There is still a bug in the New Architecture that makes the flash appear, currently, but it is in the internals. It has to work this way.
We are also working on the APIs to make sure we can soon remove those ugly #ifdefs.
But on the old architecture, it works properly.

@cipolleschi Yep, that's done it 🙂
Thanks for the quick response

This is the way i did it to access rootView
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  self.moduleName = @"DApp";
  // You can add your custom initial props in the dictionary below.
  // They will be passed down to the ViewController used by React Native.
  self.initialProps = @{};

  BOOL success = [super application:application didFinishLaunchingWithOptions:launchOptions];
  if (success) {
    UIViewController *rootViewController = [UIApplication sharedApplication].delegate.window.rootViewController;

    // Force disable dark mode
    if (@available(iOS 13.0, *)) {
      rootViewController.view.overrideUserInterfaceStyle = UIUserInterfaceStyleLight;
    }

    rootViewController.view.backgroundColor = [[UIColor alloc] initWithRed:0.0f green:0.0f blue:0.0f alpha:1];
  }

  return success;
}

@fadi-quader-mox this is not the right way to do it.
You should override this method to customize the appearance of your view.