Android build with WebP and GIF support fails since RN 0.65 (jcenter depedency)

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
Please provide a clear and concise description of what the bug is. Include screenshots if needed.
Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html
When removing jcenter, the android build fails with the following error:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find com.facebook.fresco:webpsupport:2.1.0.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
       - file:/Users/yonom/.m2/repository/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
       - file:/Users/yonom/GitHub/test/MyTestApp/node_modules/react-native/android/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
       - file:/Users/yonom/GitHub/test/MyTestApp/node_modules/jsc-android/dist/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
       - https://dl.google.com/dl/android/maven2/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
       - https://www.jitpack.io/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
     Required by:
         project :app
   > Could not find com.facebook.fresco:webpsupport:2.1.0.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
       - file:/Users/yonom/.m2/repository/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
       - file:/Users/yonom/GitHub/test/MyTestApp/node_modules/react-native/android/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
       - file:/Users/yonom/GitHub/test/MyTestApp/node_modules/jsc-android/dist/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
       - https://dl.google.com/dl/android/maven2/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
       - https://www.jitpack.io/com/facebook/fresco/webpsupport/2.1.0/webpsupport-2.1.0.pom
     Required by:
         project :app > com.facebook.fresco:animated-webp:2.1.0
   > Could not find com.facebook.fresco:animated-drawable:2.1.0.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/com/facebook/fresco/animated-drawable/2.1.0/animated-drawable-2.1.0.pom
       - file:/Users/yonom/.m2/repository/com/facebook/fresco/animated-drawable/2.1.0/animated-drawable-2.1.0.pom
       - file:/Users/yonom/GitHub/test/MyTestApp/node_modules/react-native/android/com/facebook/fresco/animated-drawable/2.1.0/animated-drawable-2.1.0.pom
       - file:/Users/yonom/GitHub/test/MyTestApp/node_modules/jsc-android/dist/com/facebook/fresco/animated-drawable/2.1.0/animated-drawable-2.1.0.pom
       - https://dl.google.com/dl/android/maven2/com/facebook/fresco/animated-drawable/2.1.0/animated-drawable-2.1.0.pom
       - https://www.jitpack.io/com/facebook/fresco/animated-drawable/2.1.0/animated-drawable-2.1.0.pom
     Required by:
         project :app > com.facebook.fresco:animated-gif:2.0.0 > com.facebook.fresco:animated-base:2.1.0

React Native version:
Run react-native info in your terminal and copy the results here.
System:
    OS: macOS 11.5.2
    CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
    Memory: 151.99 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.7.0 - /var/folders/4l/5q_1bbc93mb221kpmsz41jth0000gn/T/yarn--1629981704937-0.7811824049039413/node
    Yarn: 1.22.11 - /var/folders/4l/5q_1bbc93mb221kpmsz41jth0000gn/T/yarn--1629981704937-0.7811824049039413/yarn
    npm: 7.21.0 - /usr/local/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4
    Android SDK:
      API Levels: 23, 24, 28, 29, 30
      Build Tools: 28.0.3, 29.0.2, 30.0.2, 30.0.3, 31.0.0, 31.0.0, 31.0.0, 31.0.0, 31.0.0
      System Images: android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 2020.3 AI-203.7717.56.2031.7621141
    Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_292 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: ^17.0.2 => 17.0.2
    react-native: ^0.65.1 => 0.65.1
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

New project npx react-native init
add animated gif and webp support as per https://reactnative.dev/docs/image#gif-and-webp-support-on-android
Build the app yarn android

Expected Results
Describe what you expected to happen.
The build should compile successfully.
Snack, code example, screenshot, or link to a repository:
Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
You may provide a screenshot of the application if you think it is relevant to your bug report.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve
android/app/build.gradle
dependencies {
  // For animated GIF support
  implementation 'com.facebook.fresco:animated-gif:2.0.0'

  // For WebP support, including animated WebP
  implementation 'com.facebook.fresco:animated-webp:2.1.0'
  implementation 'com.facebook.fresco:webpsupport:2.0.0'
}

Moreover gifs are no more displayed since RN 0.65 on android

Update your fresco dependency to 2.5.0 in your app.gradle file your gif will work fine

This might be a docs issue.
The recommended version of fresco specified here is 2.0.0 / 2.1.0:
https://reactnative.dev/docs/image#gif-and-webp-support-on-android
I don't know if 2.5.0 is tested and fully compatible with react native 0.65 or not

Its tested from my end. Working fine
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Simon Farshid @.>
Sent: Wednesday, September 1, 2021 6:38:58 PM
To: facebook/react-native @.>
Cc: sallarahmed @.>; Comment @.>
Subject: Re: [facebook/react-native] Android build with WebP and GIF support fails since RN 0.65 (jcenter depedency) (#32091)
This might be a docs issue.
The recommended version of fresco specified here is 2.0.0 / 2.1.0:
https://reactnative.dev/docs/image#gif-and-webp-support-on-android
I don't know if 2.5.0 is tested and fully compatible with react native 0.65 or not
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/react-native/issues/32091#issuecomment-910295064, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGLUDENFGKQUMTBB3EGGLTTT7YUHFANCNFSM5C3JBMKQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Does it work in release mode too? I have the same issue and in dev mode, everything works fine but in release mode, I can't see the gifs.

Update your fresco dependency to 2.5.0 in your app.gradle file your gif will work fine

2.5.0 solves the issue

adding this line to android/app/build.gradle fixed it for me:
  // For animated GIF support
  implementation 'com.facebook.fresco:animated-gif:2.5.0'

adding this line to android/app/build.gradle fixed it for me:
  // For animated GIF support
  implementation 'com.facebook.fresco:animated-gif:2.5.0'

same problem here but ended up with this solution where i upgraded the com.facebook.fresco:animated-gif and com.facebook.fresco:webpsupport to 2.50
 // If your app supports Android versions before Ice Cream Sandwich (API level 14)
    implementation 'com.facebook.fresco:animated-base-support:1.3.0'

    // For animated GIF support
    implementation 'com.facebook.fresco:animated-gif:2.5.0'

    // For WebP support, including animated WebP
    implementation 'com.facebook.fresco:animated-webp:2.1.0'
    implementation 'com.facebook.fresco:webpsupport:2.5.0'

    // For WebP support, without animations
    implementation 'com.facebook.fresco:webpsupport:2.0.0'```

Update your fresco dependency to 2.5.0 in your app.gradle file your gif will work fine

Thanks, only thing that worked for me on react-native 0.64

I'm upgrade to RN 0.66 and this works for me, just follow the  - https://frescolib.org/docs/index.html -1. Update Gradle configuration and  2. Optional: Add additional Fresco feature modules, I upgrade  the fresco dependencies to 2.6.0.

The documentation has been upgraded to use 2.5.0, these new versions no longer cause issues.
Closing issue


chore(monorepo): update node to v18

Update node to v18
Fixes https://github.com/RoadieHQ/roadie-backstage-plugins/issues/999
:heavy_check_mark: Checklist

[ ] Added tests for new functionality and regression tests for bug fixes
[ ] Added changeset (run yarn changeset in the root)
[ ] Screenshots of before and after attached (for UI changes)
[ ] Added or updated documentation (if applicable)

@schultzp2020 would you mind taking a look at those failing tests?

Hi @schultzp2020 is there anything we can do to help you with this one?


v5 support

Any chance there's any work on PIXIv5 support. It currently has issues because they changed up PIXI.Graphics() by moving graphicsData and some functions around.

I've ported the original source js file to typescript and fixed it to work with PIXIv5. I'm not sure how to make it work perfectly because I'm still missing some fill in the test001 file. It works for my purposes though. Thank you for the source. You can find the ported version on my fork.


[Menu, DropdownMenu] Allow CheckboxItem state to be indeterminate

Description
Addresses #1581 — allows the Menu.CheckboxItem/DropdownMenu.CheckboxItem to have an indeterminate state (and aria-checked='mixed' attribute). Implementation was largely referenced from the core Checkbox primitive, where this was already available.
Some notes:

I'm extremely late to learning Typescript in my career, so please let me know if there are any cleanups/improvements that could be made in that respect (or any other respect, of course)
I exported isIndeterminate, getState, and the CheckboxState type from the Checkbox package instead of recreating these for MenuCheckboxItem — I'm not sure if this change warrants a minor release, but I figured all the affected packages should get the same bump. Let me know if this is incorrect?
ContextMenu was flagged for an update only because I needed to add type arguments to the useState calls in the Checkbox Item story — again, not sure if this should warrant a release or not?

I've tested my changes via updated stories for Menu and DropdownMenu ('Checkbox Items' in both).
Happy to make any changes as necessary!

i'm not sure it makes much sense to create a dependency between @radix-ui/react-checkbox and @radix-ui/react-menu here given that the menu never renders the checkbox component.
personally i'd copy/paste the type and utils you're re-using here, they're very small.

@jjenzz I wondered about that as well. I thought syncing up these up might help to prevent breaking this feature parity in the future, but if the cost of creating the dependency outweighs that risk, I'm of course happy to change it!

I agree with Jenna, let's duplicate the bits mentioned rather than add a dependency.

@jjenzz @benoitgrelard Done! Please let me know if you see any other changes/improvements to be made.

Not quite sure how to roll that back as it doesn't appear in the release options now, any ideas?)

You can delete the version file and re-run the command.

Thank you, done!

@jjenzz @benoitgrelard Just checking in — any other changes you'd like to see, or do you reckon this can proceed to workflows & merging? Thanks!

@benoitgrelard Requested changes are in, let me know if you'd like any other updates!


implement bookworm serve for website without apache

Working with a grad student, it seems like maybe the headaches related to Apache installations could be alleviated for first-draft installations by using a python server instead.
I can confirm that in a running bookworm directory, this gist works to fully clone the linechart browser and get it running on OS X 10.9 and Ubuntu 14.04 when other things are installed, without requiring an Apache server.
(running inside a clone of this repository after setting up the database)
mkdir GUI
make linechartGUI webDirectory=GUI
git clone git@github.com:Bookworm-Project/BookwormAPI GUI/cgi-bin
cd GUI; python -m CGIHTTPServer 8000

Visit http://localhost:8000, and click to navigate to whatever the bookworm name is.
I don't know what user it's querying the database under--presumably the administrator, though. That means it's

Way easier to set up--the apache user and apache config seems to be far and away the hardest part
Less secure (ie, maybe a creatively malicious person could use a proper combination of escapes and semicolons to slip a "DROP DATABASE" statement through.)

Changing the title: bookworm serve under the module/argparse architecture would be a clean way to spin up a local webhost in a subdirectory using python CGIHTTPServer.
Probably use either 8004 or 8003 as the port because they look, to me, like the word "book."

Implemented at https://github.com/Bookworm-project/BookwormDB/commit/37d7599c6d11d1212ac2edf9286f95e4d0258e3e


[MODEL EVALUATION REQUEST] neuralmagic/Sparse-Llama-3.1-8B-2of4

Model ID
neuralmagic/Sparse-Llama-3.1-8B-2of4
Model type
Decoder model (e.g., GPT)
Evaluation languages

[X] Danish
[X] Swedish
[X] Norwegian (Bokmål or Nynorsk)
[X] Icelandic
[X] Faroese
[X] German
[X] Dutch
[X] English

Merged model
Not a merged model

Live on leaderboards now 🎉


Document OSM Readiness and Liveness health probes

Please document the readiness and liveness probes.
See PR: https://github.com/openservicemesh/osm/pull/1659

This is no longer needed.


runtime mapping of variables

Currently, the mapRuntimeVariables function, does the mapping for all the variables. It's been agreed to modify this later, so we only map the variables that are used within a function during the simulation.

This is much later. Perhaps for milestone 2 after first alpha release.

Closing, not convinced this is still on the roadmap.


bugfix: yurt-controller-manager cannot restart

What type of PR is this?
/kind bug
What this PR does / why we need it:
When yurt-controller-manager restart, it will encounter fatal error and exit because the mutatingwebhookconfiguration and validatingwebhookconfiguration has already exists.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

@gnunu @LindaYu17 PTAL


Fix overlaps when two voices in the same staff

This PR fixes layout errors due to overlaps in notes, chords and rests when there are two voices in the same staff (e.g. test score 00633):
Lomse (before this PR):

Lomse (after this PR):

The solution has been to create a NoterestsCollisionsFixer object that will receive all note/rest shapes at a given staff and timepos, to check for overlaps and solve any detected issue by moving sideways the conflicting objects. The NoterestsCollisionsFixer object is created in the spacing algorithm in the TimeSliceNoterest objects.
When this task was started, the collision scenarios I had in mind were very simple, just unisons, notes a second apart and rests and notes collisions. But as I started to work and studied collision scenarios and engraving rules in these situations, it resulted that there are many engraving rules involved and the number of collision scenarios is overwhelming, requiring in practice near a case by case solution.
Therefore, this PR is a first step, fixing most collision cases between chords, notes, rests and accidentals. But not cases involving dots and collisions with flags, that introduce an extra level of complexity. So I prefer to take a rest on this issue for a while.
Limitations
Current implementation has some limitations:

The solution is currently restricted to fix overlaps in two voices. If there are more than two voices in the same staff the collisions will be fixed for two voices but nothing will ensure that there are no overlaps with the other voices.

Overlaps between noteheads one third apart are considered false positives as both noteheads should touch each other. But when the noteheads are of different types (e.g. a quarter note and a half note) it can be a real overlap and this is not fixed in this PR.

I preferred not to deal with these two cases until having real scores displaying these types of problems, to confirm the need and to have more knowledge about the specific problems and the possible solutions.
Also, as commented, this PR does not deal with dots and with cases involving collisions with flags.

Thank you. Merged


Database pool

This should resolve issue #22

This change is

Reviewed 4 of 8 files at r1, 14 of 17 files at r3, 2 of 2 files at r4, 2 of 2 files at r5.
Review status: 22 of 23 files reviewed at latest revision, 1 unresolved discussion.

src/tests/src/test_mysql_database.cpp, line 25 [r5] (raw file):
Don't forget about this!

Comments from the review on Reviewable.io

Reviewed 1 of 17 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io


Parametrizing RDM: "ERROR: DomainError with ..." log error

I'm having some trouble parametrizing the RDM, despite using priors that I'd think would be alright (but here's probably my mistake).
Very often, the sampling errors with the following:
ERROR: DomainError with -1.4187210312401369e-50:
log was called with a negative real argument but will only return a complex result if called with a complex argument. Try log(Complex(x)).
... [about log]
Stacktrace:
  [1] throw_complex_domainerror(f::Symbol, x::Float64)
    @ Base.Math .\math.jl:33
  [2] _log(x::Float64, base::Val{:ℯ}, func::Symbol)
    @ Base.Math .\special\log.jl:301
  [3] log
    @ .\special\log.jl:267 [inlined]
  [4] log
    @ C:\Users\domma\.julia\packages\ForwardDiff\PcZ48\src\dual.jl:240 [inlined]
  [5] logpdf
    @ C:\Users\domma\.julia\packages\SequentialSamplingModels\T1Z4T\src\RDM.jl:55 [inlined]
  [6] logpdf(d::RDM{ForwardDiff.Dual{ForwardDiff.Tag{DynamicPPL.DynamicPPLTag, Float64}, Float64, 4}}, r::Int64, rt::Float64)
    @ SequentialSamplingModels C:\Users\domma\.julia\packages\SequentialSamplingModels\T1Z4T\src\RDM.jl:144

Code:
using CSV
using DataFrames
using Turing
using Pigeons
using SequentialSamplingModels
using StatsModels
using StatsPlots
using GLMakie
using RCall

# Read data
df = CSV.read(download("https://raw.githubusercontent.com/RealityBending/DoggoNogo/main/study1/data/data_game.csv"), DataFrame)

# RDM model
@model function model_rdm(data; min_rt=minimum(data.rt), isi=nothing)

    # Priors for coefficients
    drift_intercept ~ filldist(truncated(Normal(6, 1), 0.0, Inf), 1)

    A ~ truncated(Normal(1, 0.3), 0.0, Inf)
    k ~ truncated(Normal(0.5, 0.1), 0.0, Inf)
    τ ~ truncated(Normal(0.2, 0.05), 0.0, min_rt)

    for i in 1:length(data)
        drift = drift_intercept
        data[i] ~ RDM(drift, k, A, τ)
    end
end
dat = [(choice=1, rt=df.RT[i]) for i in 1:length(df.RT)]
chain_rdm = sample(model_rdm(dat, min_rt=minimum(df.RT), isi=df.ISI), NUTS(), 500)
StatsPlots.plot(chain_rdm; size=(600, 2000))

Any tips?
Which makes me think that it would be amazing to add the docs, when listing all parameters, some info (where available, it can be a work-in-progress goal) to help people parametrize, e.g.: for sigma, "Cannot be negative", for drift in DDM: "typical range: [..., ....]"

Your prior distributions look good to me. I think it is an issue with numerical stability.  I get the following error when setting the seed to 50:
ERROR: DomainError with -4.91550493136807e-18
which occurs around here
but the error might originate deeper in the code. My guess is there is some numerical instability, which could be exacerbated only having 1 accumulator. I will dig into it more over the next couple of days. Thank you for reporting.
I like your idea of including parameter ranges in the docs.

Under the conditions above, the log likelihood evaluates to 0 but due to numerical instability, a small negative number was passed to log, thus triggering a complex number error. This is likely to happen in your model because you have a lot of parameters relative to the number of response alternatives. The best approach would be to rewrite the log likelihood in terms of logs of individual terms rather than logpdf(...) = log(pdf(...)). Unfortunately, I am not sure if there is a clean way to do so given the number terms added here. If other problems continue to emerge, I can look into a solution using logsumexp.  For now, the solution I implemented seems to work. I'll release an update. The change is breaking (due to some other changed already on master), but it should not affect your models.

Following up on this as I ran into similar, if not the same, numerical instability issue when creating mwe with the RDM. Where the changes released?

It looks the fix was released in v0.9.0. Can you provide a MWE if the issue still persists?


Error when sending payloads with OData type annotation

While trying to call a method of odata2ts generated service with @odata.type annotation inside a POST payload to create an Entity that contains a complex type, I encountered the following error:
app-error-handler.ts:35 Error: Property<EMAIL_ADDRESS>not found (in strict mode)! Known user model props:
    at QueryObject.js:100:27
    at Array.reduce (<anonymous>)
    at QueryObject.js:87:42
    at Array.map (<anonymous>)
    at Configuration.convertToOData (QueryObject.js:86:31)
    ...

The error occurred here:
https://github.com/odata2ts/odata2ts/blob/main/packages/odata-query-objects/src/QueryObject.ts#L158
Here is an example of POST payload for a complex type entity: https://www.odata.org/getting-started/basic-tutorial/#modifyData.
It seems that the library is not recognizing the @odata.type annotation.

Hi @oartyshko,
the changes:

convertTo doesn't throw if it meets unannounced properties (wrong default)
Annoations or better to say "control information" are now supported by default for create, patch and update

If you're inclined to check the spec against my understanding (as it is laid out here: #261) you're more than welcome. Open any discussion / issue if you find something.
Released with

@odata2ts/odata2ts version 0.33.2
@odata2ts/odata-service version 0.18.0

If the release fixes your issue, then please close the ticket.

Hi @texttechne!
Thanks a lot for this improvement! 👍  I've just tested it ✅  It works perfectly!


[language] Change test generation to no longer directly create a TransactionExecutor

Previously this setup the VM for running a generated module in much the same way as we do in cost synthesis. However, in this case we don't need to directly interact with the interpreter, so we can call in via normal means. Also, directly setting up the VM will cause problems shortly when we update to an on-chain gas schedule so removing this out in preparation for that diff, and also because it's the right thing to do :)

@bors-libra r=dariorussi

:pushpin: Commit c5382aa has been approved by dariorussi

:hourglass: Testing commit c5382aa19d80725047a4257e762a9c675ef51a66 with merge a2ce8b5e2c325d5483f8abd07efb479bde6d4f3c...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: dariorussi
Pushing a2ce8b5e2c325d5483f8abd07efb479bde6d4f3c to master...


Usage component dashboard

Summary
This PR implements the Usage Component Available on dashboard page as  per the new design.
Issue : #425
How to Test the Changes
To test the changes you will have the render the dashboard component from the pages folder.
Screenshots or Recordings
Expected UI :

Implemented UI :

Checklist

[x] I have added/updated tests that cover the changes.
[x] I have updated the documentation to reflect the changes.

I am working on it

@001AM can you provide latest recording of the UI.


Version bump to 0.4.4

@wesley-harding I'm subbing you in for review since David is out. This is a change as part of our CORS updates to allow localhost to continue to work as Comply engineers are used to.

@aguilinger I think wesley will be busy for a bit. I can give you context on this if you need, but just a version bump to prep for release. Then I'll be updating auth-api to point to the new version in a follow-up PR.


[Bug]: n_predict error and chat don't work. App: 1.6.0

Describe the bug
Change n_predict value and chat don't work and I see error.
Now nothing work even when I set value to any number.
To Reproduce
Steps to reproduce the behavior:

Go to Models
Click on Settings
Change value n_predict to 5000 (miss click, value I wanted was 500)
See error "value must be between 1 to 4096"
Write good value 500
Load model
Say something on chat
See error "Completion failed: Value n_predict cannot be cast from String to double"

Expected behavior
Simple change value n_predict without error
Screenshots
Error on chat:

Change value:

Model:

Environment:

Device: [Pixel 6a ]
OS: [ (GrapheneOS) | Android 15 ]
App Version: [ 1.6.0 (39) ] - app from Github

Additional context
When I add this model, and use Default value, nothing change, then everything work good.
When I change n_predict then I see error.
Any solution is to delete model and add again and do nothing in settings.

BTW. A see something strange, (Bug?) when I want change Template, click to scroll down list: "custom" and nothing happens.
I must click on left, no to center word "custom", then list show up.

Yes, I had that issue as well, so I probed further. What I did first was copy the value and change the n_predict, which is by default 400, to 200, which is supposed to be the minimum. Then I chatted, but I received the same message. So, I selected all, pasted the value, and saved it. I chatted again and encountered the same error. This issue is not limited to n_predict. It also applies to the seed. Leaving n_predict unchanged and editing the seed will lead to the same error. I did some research and found out that any changes to n_predict and seed are seen by the app as strings rather than integers.


Lomkile

Hi  @LomNtetha ,
When opening an issue, please try to provide all or some of the information indicated in the template.
Closing this issue, since no information has been provided.
Thank you.


Updated README.md

Summary of your changes
Added one link in the Interview Preparation section.
Description
Added the following link for Core Java Interview preparation: Core Java Interview preparation
The webpage is live and working fine.

Checklist

[x] My change follows the Contributing Guidelines
[x] I have added only one new link to the list.
[x] I have checked that the link that I added does NOT exist in the project already.
[x] I have sorted the link alphabetically under the related section.

@sdmg15 is the PR alright?

Does the PR require any changes, @sdmg15?

@sdmg15 ?

@sdmg15 is there any problem in the Pull Request?

@sdmg15 ?
IF you've been busy, then maybe I can ask any other reviewer.
Can you tell me who?


feat(masthead): adding shadow parts

Related Ticket(s)
ADCMS-5170
Description
Adding shadow parts to the Masthead component so it can be styles outside of the Shadow Tree.
Snapshots updated.

Hey guys @andy-blum @Valentin-Sorin-Nicolae @marcelojcs @m4olivei
I have addressed the comments from John, can you please check it now? I have just simplified the naming convention for all the shadow parts.
Thank you!!


@types/aws-lambda is a dependency

https://github.com/prisma/graphql-yoga/blob/master/src/types.ts#L18 requires @types/aws-lambda. And when using graphql-yoga in a TypeScript "native" project, this produces errors:
$ yarn tsc --noEmit
yarn run v1.10.1
$ /Users/skainswo/dev/kumo/node-api/node_modules/.bin/tsc --noEmit
node_modules/graphql-yoga/dist/types.d.ts:11:64 - error TS7016: Could not find a declaration file for module 'aws-lambda'. '/Users/skainswo/dev/kumo/node-api/node_modules/aws-lambda/lib/main.js' implicitly has an 'any' type.
  Try `npm install @types/aws-lambda` if it exists or add a new declaration (.d.ts) file containing `declare module 'aws-lambda';`

11 import { APIGatewayProxyEvent, Context as LambdaContext } from 'aws-lambda';
                                                                  ~~~~~~~~~~~~

Hey folks, I'm facing the same issue:
node_modules/graphql-yoga/dist/types.d.ts:11:64 - error TS7016: Could not find a declaration file for module 'aws-lambda'. './node_modules/aws-lambda/lib/main.js' implicitly has an 'any' type.
  Try `npm install @types/aws-lambda` if it exists or add a new declaration (.d.ts) file containing `declare module 'aws-lambda';`

11 import { APIGatewayProxyEvent, Context as LambdaContext } from 'aws-lambda';
                                                                  ~~~~~~~~~~~~

node_modules/subscriptions-transport-ws/dist/server.d.ts:2:28 - error TS7016: Could not find a declaration file for module 'ws'. './node_modules/ws/index.js' implicitly has an 'any' type.
  Try `npm install @types/ws` if it exists or add a new declaration (.d.ts) file containing `declare module 'ws';`

2 import * as WebSocket from 'ws';
                             ~~~~

Found 2 errors.

The issue only occurs when "noImplicitAny": true or "strict": true is set in tsconfig.json.
There are 2 solutions for users:

Turn "noImplicitAny": false in tsconfig.json (when "strict": true, this results in some bizarre error messages which might require extra annotations, see https://github.com/Microsoft/TypeScript/issues/18687)
Manually add those dependencies (as suggested by the error message - npm install @types/aws-lambda).

Would be great to merge this just to improve the first-use experience of graphql-yoga. Setting "strict": true is best practice in Typescript, and the errors are pretty confusing, especially when you're not using lambda or subscriptions in your project. Also, all other type definitions are already dependencies as opposed to devDependencies, so I don't see how this could cause any issues.
#490 is a duplicate of this.
A similar PR (for ws) is open in subscriptions-transport-ws: https://github.com/apollographql/subscriptions-transport-ws/pull/486
Thank you, appreciate it!

bump

bump

This should have now been resolved by #576, so this can be closed


Bug in JavaScript Syntax Hightlighting

The following JavaScript is incorrectly parsed. I think it has to do with the function keywords appearing inside strings.
var f = function(y) {
  if (a) {
    a.push('x' + y + ':function()');
  } else {
    this.part.is.not.correctly.syntax.highlighted();
  }
};

Closing this as it's being tracked over in https://github.com/atom/language-javascript/issues/76


Use Redis#exists? instead of Redis#exists

Follow the advice warned by recent versions of redis-rb:
Redis#exists(key) will return an Integer in redis-rb 4.3. exists? returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set Redis.exists_returns_integer = false, but this option will be removed in 5.0. (~/.rvm/gems/ruby-2.6.3/gems/sidekiq-cron-1.2.0/lib/sidekiq/cron/job.rb:464:in `block in save')

Coverage decreased (-15.7%) to 75.81% when pulling 65e45c26152a08a90dd5795f5c9c149f68b0db24 on spacebat:Fix-deprecated-use-of-redis-exists into 7ca90f95f1f8776e84546e69d82f7f6ab1b31233 on ondrejbartas:master.

Coverage decreased (-15.7%) to 75.81% when pulling 65e45c26152a08a90dd5795f5c9c149f68b0db24 on spacebat:Fix-deprecated-use-of-redis-exists into 7ca90f95f1f8776e84546e69d82f7f6ab1b31233 on ondrejbartas:master.


[Desktop] Starting Minimized

If option to start minimized is turned on, app starts minimized correctly, but also searches for a contact named "minimized"

i thought it was too haha


Add Sample data and Dashboards for the SQEF

Description
We want to more widely distribute the dashboards (and the nice sample data) for the Search Quality Evaluation Framework (SQEF?) to people.    One way is to add these to the nightly playground environment and maybe soon as one of the standard datasets.   This is the first step by getting these artifacts into a Opensearch repo.
Issues Resolved
This will help move https://github.com/opensearch-project/opensearch-devops/issues/214 forward.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

What does this mean?
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 4 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 1.08 KiB | 1.08 MiB/s, done.
Total 4 (delta 3), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
remote: error: GH013: Repository rule violations found for refs/heads/add_sqef_dashboard.
remote: Review all repository rules at https://github.com/opensearch-project/user-behavior-insights/rules?ref=refs%2Fheads%2Fadd_sqef_dashboard
remote:
remote: - Changes must be made through a pull request.
remote:
To github.com:opensearch-project/user-behavior-insights.git
 ! [remote rejected] add_sqef_dashboard -> add_sqef_dashboard (push declined due to repository rule violations)
error: failed to push some refs to 'github.com:opensearch-project/user-behavior-insights.git'

I want to add to the README:
The `sample_search_quality_evaluation_data.ndjson` was generated via the `../ubi-data-generator/` script.

What does this mean?
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 4 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 1.08 KiB | 1.08 MiB/s, done.
Total 4 (delta 3), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
remote: error: GH013: Repository rule violations found for refs/heads/add_sqef_dashboard.
remote: Review all repository rules at https://github.com/opensearch-project/user-behavior-insights/rules?ref=refs%2Fheads%2Fadd_sqef_dashboard
remote:
remote: - Changes must be made through a pull request.
remote:
To github.com:opensearch-project/user-behavior-insights.git
 ! [remote rejected] add_sqef_dashboard -> add_sqef_dashboard (push declined due to repository rule violations)
error: failed to push some refs to 'github.com:opensearch-project/user-behavior-insights.git'

@epugh The problem is your branch was pushed to this repository and is not coming from a fork. Any branch that gets pushed to this repository becomes a protected branch and must be committed to via a pull request. So let's merge this branch, and then make the README change in a new pull request from a branch in your fork.


owr_transport_agent_set_local_port_range

Hi,
What is the use of the this function "owr_transport_agent_set_local_port_range" and "owr_session_set_local_port"? and when we need to use these functions?
Thanks
Suganthi

I think you should call it after alloc owr_transport_agent, if you dont call it,
it's going make local ice agent port star from 0 .....


Argument 2 passed to Symfony\Component\HttpKernel\EventListener\ProfilerListener::__construct() must be an instance of Symfony\Component\HttpFoundation\RequestStack, null given

I've run composer update and see this error:

I have this two dependencies in composer.json related to silex:
"silex/silex": "~1.3",
"silex/web-profiler": "1.0.x-dev"

I presume you've solved this, but for anyone else who winds up here: check minimum-stability and prefer-stable in your composer.json.
I had "minimum-stability": "beta" and "prefer-stable": false, which was causing Composer to pull the v3.0.0-BETA1 tag of symfony/http-kernel instead of ^2.7. In Symfony 2.8 the last argument of the ProfilerListener constructor (RequestStack $requestStack = null) was moved forward into position two of the argument list, and had its default value/nullable trait removed (the reason for the relocation, I'd guess).

I had  same problem, it´s was  update silex and composer automatically update to "symfony/http-kernel" : "~3.0" since that is a dependency of symfony/web-profiler-bundle and I didn't have another to limit manually the version of "symfony/http-kernel" : "<3.0"


fix: app bar icon colors

This should fix #1156 it needs to be tested, also let me know if there is a better implementation.

Re: simpler implementation, you could try setting the theme data at the AppBar: https://stackoverflow.com/a/57738275/86433


Check builder prerequisities

We should check if docker is installed for docker builder, rhpkg for osbs, etc.

Closed via https://github.com/jboss-container-images/concreate/pull/74


ci: add spack test

The Linux build got much further but failed with this near the very end:
2020-11-16T21:01:37.3810795Z ==> Error: OSError: Cannot call rmtree on a symbolic link
2020-11-16T21:01:37.3811081Z
2020-11-16T21:01:37.3811692Z /home/runner/work/charm/spack/var/spack/repos/builtin/packages/charmpp/package.py:301, in install:
2020-11-16T21:01:37.3812240Z         298                        os.rename(tmppath, filepath)
2020-11-16T21:01:37.3812591Z         299                    except (IOError, OSError):
2020-11-16T21:01:37.3812874Z         300                        pass
2020-11-16T21:01:37.3813206Z   >>    301        shutil.rmtree(join_path(builddir, "tmp"))
2020-11-16T21:01:37.3813514Z         302
2020-11-16T21:01:37.3814184Z         303        if self.spec.satisfies('@6.9.99'):
2020-11-16T21:01:37.3814799Z         304            # A broken 'doc' link in the prefix can break the build.
2020-11-16T21:01:37.3815244Z
2020-11-16T21:01:37.3815501Z See build log for details:
2020-11-16T21:01:37.3817008Z   /tmp/runner/spack-stage/spack-stage-charmpp-develop-mcvl5dowlcd7qsrwamploktdzaltsjhd/spack-build-out.txt
2020-11-16T21:01:37.3819175Z

Spack is probably expecting builddir/tmp to be a folder and not a symlink to builddir/include. This may need to be fixed upstream.


Error in APF update

Thanks for your great paper and this repo. Looks like you made a type-o in the APF update step at
https://github.com/jelfring/particle-filter-tutorial/blob/16142c850fcbbef67ebcfb7d895a617514f59357/core/particle_filters/auxiliary_particle_filter.py#L78
by multiplying the compute_likelihood by the previous weight par[0] to form the current tmp_likelihood estimate. As such, your temporary weight uses $w_{k-1}^2$ and your final weight is (with simplified notation) $\frac{p(x|y)}{w_{k-1}p(\mu|y}$.

Yes, you are right. The multiplication with par[0] is currently present twice and can be removed in line 78. Thanks for noticing. It would be great if you can create a pull request for fixing the typo.

I pushed the change to a local fork and make a pull request.


Creation of footer and header for better appealing visual ui

The site doesn't consist of the designated header and footer so i want to contribute to that and will give a border aspect for its development better for  navigation.
if possible with gssoc-ext please assign me with hacktoberfest-accepted

Duplicate #17.


Update to Swift 5.0.1 breaks builds on Ubuntu 18/04

This commit breaks builds on Ubuntu 18.04: https://github.com/apple/swift-docker/commit/724a1d10c12da1006c1433da4e521894aaf14ef0#diff-a3be029562676b6e61a37c312894681e Everything worked fine with the previous release of this Dockerfile.
Somehow it got released despite failing tests on this version of OS: https://ci.swift.org/job/swift-docker-PR-linux/27/console#console-section-2
STR: Use this image and try to compile a Swift project
Result: Missing openssl and zlib. Output:
'swift-nio-ssl-support' openssl.pc: warning: couldn't find pc file
'swift-nio-zlib-support' zlib.pc: warning: couldn't find pc file
[1/50] Compiling CNIOZlib empty.c
[2/50] Compiling CNIOSHA1 c_nio_sha1.c
[3/50] Compiling CNIOOpenSSL shims.c
[4/50] Compiling CNIOOpenSSL helpers.c
[5/50] Compiling CNIOLinux shim.c
[6/50] Compiling CNIOLinux ifaddrs-android.c
In file included from /app/.build/checkouts/swift-nio-ssl/Sources/CNIOOpenSSL/helpers.c:14:
/app/.build/checkouts/swift-nio-ssl/Sources/CNIOOpenSSL/include/c_nio_openssl.h:17:10: fatal error: 'openssl/conf.h' file not found
#include <openssl/conf.h>
         ^~~~~~~~~~~~~~~~
In file included from /app/.build/checkouts/swift-nio-ssl/Sources/CNIOOpenSSL/shims.c:16:
/app/.build/checkouts/swift-nio-ssl/Sources/CNIOOpenSSL/include/c_nio_openssl.h:17:10: fatal error: 'openssl/conf.h' file not found
#include <openssl/conf.h>
         ^~~~~~~~~~~~~~~~

Expected result: successful build.

The removal of certain packages was intentional in https://github.com/apple/swift-docker/commit/966cfdef637e319d28b681e42bdb905b070bf338.
The Swift images are intended to contain the minimum set of packages needed to build and run Swift programs.  zlib and OpenSSL development headers are not required by every Swift program - as you can see they are dependencies of SwiftNIO, not Swift.
Please add the packages SwiftNIO needs in your Dockerfile.

Thanks!

You're welcome.  Sorry for the inconvenience but this is worth it for keeping the images as slim as possible for all users.

Just in case someone else runs into the same problem with SwiftNIO dependencies (mine was a part of a Vapor app): all you need is apt-get install -y libssl-dev libicu-dev.

Using a Vapor 3 project that uses SwiftNIO I had to install only libssl-dev.

Thanks for the info.  I think when Vapor 4 is released you won't even need that, because SwiftNIO 2 does not require a system libssl.

Vapor 4 still needs OpenSSL for crypto. Adding these two packages gets things working for me:
libssl-dev zlib1g-dev

Ah cool, thanks Tanner.

What about macOS 10.14.5 (fresh install) with Swift 5.0.1, how to fix 'openssl/conf.h' file not found on it?

Hahah, fixed just by regenerating xcodeproj 🙂 the problem appeared just because I copied project from another machine instead of doing git clone && swift package generate-xcodeproj


Error: Failed to launch chrome! on Heroku 20

I'm getting this error on Heroku after updating to Heroku 20:
Error: Failed to launch chrome!
Nov 20 13:06:19 tablelist-api-dev app/web.1 /app/node_modules/puppeteer/.local-chromium/linux-588429/chrome-linux/chrome: error while loading shared libraries: libffi.so.7: cannot open shared object file: No such file or directory
I was able to get things working by downgrading all the way back to Heroku 16, though I'm not 100% why that is. I believe Heroku 18 was working before, so might be something else. Not sure if you have any ideas. I'll update with more information as I go, switching between Heroku stacks.

Update:
I was able to get it working again on Heroku 20 after following these steps to clear my build cache:
https://help.heroku.com/18PI5RSY/how-do-i-clear-the-build-cache
Not sure why this works though, any ideas?

Wondering if this issue is related to https://github.com/jontewks/puppeteer-heroku-buildpack/issues/72 and the cache not getting cleared?

@officert Yeah I'm pretty sure this error was caused by the cache not being invalidated on stack upgrade (ie: #72).

Hey sorry about that. Yes I'll be working on adding that here shortly. Glad you got it worked out though.

Hey sorry about that. Yes I'll be working on adding that here shortly. Glad you got it worked out though.


Typo "@project_stream"→"@project_stream"

Italic with escape characters
https://docs.microsoft.com/en-us/sql/integration-services/deploy-and-execute-ssis-packages-using-stored-procedures?view=sql-server-2014

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Corrections confirmed. Thanks.


🚀 feat:  go_router_builderの導入

close #192

Codecov Report

Merging #193 (14d7161) into develop (c5787a7) will decrease coverage by 0.99%.
The diff coverage is 86.17%.

@@             Coverage Diff             @@
##           develop     #193      +/-   ##
===========================================
- Coverage   100.00%   99.00%   -1.00%
===========================================
  Files           52       53       +1
  Lines         1258     1302      +44
===========================================
+ Hits          1258     1289      +31
- Misses           0       13      +13

Flag
Coverage Δ

unittests
99.00% <86.17%> (-1.00%)
:arrow_down:

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

Impacted Files
Coverage Δ

...b/presentation/pages/repo/avatar_preview_page.dart
100.00% <ø> (ø)

...sentation/pages/repo/components/selected_repo.dart
100.00% <ø> (ø)

lib/presentation/pages/repo/repo_search_page.dart
100.00% <ø> (ø)

lib/presentation/pages/repo/repo_view_page.dart
100.00% <ø> (ø)

lib/config/router.g.dart
81.25% <81.25%> (ø)

lib/config/router.dart
92.39% <87.50%> (-7.61%)
:arrow_down:

...tation/pages/repo/components/repo_detail_view.dart
100.00% <100.00%> (ø)

...entation/pages/repo/components/repo_list_view.dart
100.00% <100.00%> (ø)

...ages/repo/components/search_repos_text_button.dart
100.00% <100.00%> (ø)

lib/presentation/pages/repo/repo_index_page.dart
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


segfault when using one parameter as default from another one in initialize

Hi,
It seems to segfault when referencing another parameter as default from one parameter in the initialize method.
This is kind of strange usage, I agree, but I think it should either not compile or work, but runtime segmentation fault is ugly.
class Foo
  def initialize(@name : String, @id : String = @name)
  end
end

p Foo.new name: "hello"

leads to
$ crystal run test.cr
Invalid memory access (signal 11) at address 0x4
[0x559470c77b76] *CallStack::print_backtrace:Int32 +118
[…]

Crystal 0.24.2 [4f9ed8d03] (2018-03-08)
LLVM: 4.0.0
Default target: x86_64-unknown-linux-gnu
Linux Debian Stretch, Arch, online playground.

Duplicate (or similar, same cause) of https://github.com/crystal-lang/crystal/issues/3413


add a default sorting option

Make sure we Include the sorting option that was added at the end of the method UpdateRowset into the sorting logic.

Sorting options added to the installation, the personal preferences and the grid header. The default sort is based on installation, overridden by preferences and can be overridden by the user based on the sorting in the grid header.


Show Timestamp while Debugging

Geetings,
I am debugging my JavaScript files in VSCode with the ChromeDebugger extension. I recognized that I cant activate timestamps in the DebugConsole in VSCode.
Is it possible to show timestamps like in Chrome DevTools? Or is this a ChromeDebugger extension Feature request?
No Timestamps:

Want Timestamps:

If we would like to tackle this generally we would have to add it to the debug protocol, thus assigning to @weinand
Assigning also to @roblourens to consider adding it to chrome debug specifically

Open DevTools and then
Step1

Step2:

Thanks. I think it would be best as part of the debug protocol, so it can be styled/formatted/behind a setting in a nice consistent way, not something that the DA tacks onto the log message.

+1 would love to have this!

I've created https://github.com/microsoft/debug-adapter-protocol/issues/81.
When implemented we should show the timestamp in VS Code.

@weinand
Any update on this issue?
Thanks.

Looking for this capability as well

That would be indeed VERY useful

Anything?

Would love to have this

+1
Any progress?

Any update?

Bump.
Surprised previously I did find this issue and commented already.
I don't understand why it doesn't get implemented in the both aspects its usefulness and simplicity.


CEXT-3242: Release the new version of commerce webhooks without admin UI

Purpose of this pull request
This pull request (PR) adds information about the latest release of commerce webhooks
https://jira.corp.adobe.com/browse/CEXT-3242
Affected pages

https://developer.adobe.com/commerce/extensibility/webhooks/release-notes/

Links to Magento Open Source code

...

@oshmyheliuk i've created a PR into your fork to fix the links that are failing validation: https://github.com/oshmyheliuk/commerce-extensibility/pull/1


Update README.md

According to the new composer https://github.com/symfony/demo/blob/master/composer.json#L8

For maintainers, what about the version of symfony main repo and skeleton repo ´s composer? Should we open same PR ?
Thanks

@noniagriconomie thanks for fixing this!
Please note that this is a bit tricky:

Symfony 5 requires 7.2.5
A few days ago, because of some mistake that it's now fixed, required 7.2.9
Twig 3 requires 7.2.9

PHP 7.2.5 is an important version for some LTS Linux distribution, so Symfony 5 will stick to 7.2.5 ... and Twig requirement may be a mistake that could be fixed soon ... or maybe it's OK. Meanwhile, let's merge this PR. Thanks!


VtM 20th AE i18n formatting test

I tried to create an i18n formatted character sheet to translate it in italian myself and permit other translations.
It should need a test to fix possible bugs due to my lacks of coding knowledge.
I also created manually a .json translation file with the corrisponden keys used in this html.

Gave this a quick look.  It mostly looks good, with a few small potential issues.  Importantly, I'd look at your spelling of 'strength-u' in a few places, and more importantly, in the sections near the bottom (<div class="DP2">, DP3, and so on) it looks like you copied your changes from DP1, which is mostly fine, but the attribute being used is wrong (look at the name of the selection element for each block and the roll it is doing in the button element--all referencing DP1).
I'm going to close this PR.  Once you make these fixes, it should be fine to make them directly to the V20.html rather than a new file, so please do that and make a new Pull Request.  Thanks!

Ok, perfect, thanks for the hints. Prepare for the fixed file ! ;)
2017-06-26 17:59 GMT+02:00 Jeffrey Lamb<EMAIL_ADDRESS>
Gave this a quick look. It mostly looks good, with a few small potential
issues. Importantly, I'd look at your spelling of 'strength-u' in a few
places, and more importantly, in the sections near the bottom (, DP3, and so on) it looks like you copied your changes from
DP1, which is mostly fine, but the attribute being used is wrong (look at
the name of the selection element for each block and the roll it is doing
in the button element--all referencing DP1).
I'm going to close this PR. Once you make these fixes, it should be fine
to make them directly to the V20.html rather than a new file, so please do
that and make a new Pull Request. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Roll20/roll20-character-sheets/pull/2711#issuecomment-311103022,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab64_oe2hWf4g85cS8Znbu_IOFWtku9qks5sH9VcgaJpZM4OBIX3
.


Migrate operator-sdk, deps and Makefile targets from v1.4.2 to v.1.34.2

The following PR applies a series of migrations to update the MultiClusterObservability operator's operator-sdk tooling and accompanying dependencies from v1.4.2 to v1.34.2. The following migrations were applied:

Upgrade the operator-sdk from v1.4.2 to v1.34.2
Upgrade the controller-gen from v0.4.1 to v0.11.4.

Steps: v0.4.1 -> v0.7.0 -> v0.8.0 -> v0.9.0 -> v0.9.2 -> v0.10.0 -> v0.11.0 -> v0.11.4
Note: Newer version than 0.11 require go 1.22 thus skipped for now!

Migrated the PROJECT configuration from layout version go/v3-alpha to go/v3.

Note: Not applied newer project layout based on go/v4 because it requires significant code base refactorings

Updated operators/multiclusterobservability/Makefile:

Added missing targets for managing the bundle, i.e. bundle-build, bundle-push, catalog-build, catalog-push
Centralized the shell flags for bash as per requirement for kubebuilder/operator-sdk's scripts.
Added support USE_IMAGE_DIGESTS=true to generate a bundle using SHA256 digests.
Added support for make docker-buildx to enable testing multi-arch image builds locally.
Supported platforms: linux/arm64, linux/amd64, linux/s390x, linux/ppc64le
Added all missing .PHONY directives for phony targets.

Remove admissionReviewVersions={v1beta} from webhooks as per dropped support since k8s 1.22.

Notes for the reviewer

The commits in this PR are outlined as per one for each operator-sdk version migration steps.
Although each commit represents the migration steps per operator-sdk version, some versions are skipped because they did not require any.
All operator-sdk migrations applied are documented here: https://sdk.operatorframework.io/docs/upgrading-sdk-version/

Open issues:

[ ] Still unclear if we need this patch although we have webhooks in place.

/ok-to-test

/ok-to-test

/ok-to-test

/test test-e2e

/test test-e2e

@periklis you're a rockstar! Thanks for this. Will wait to merge later :)

/test test-e2e

/retest

/retest


File retention policy on Rox

Is your feature request related to a problem? Please describe.
The docker container for Rox is currently keeping all of the generated media files (e.g. from the TTS engine), which causes an increase in disk utilization.
Describe the solution you'd like
We should have a cleanup mechanism to remove unused files. For example,  a cron job that runs every n hours and removes files that haven't been accessed for x hours.
Describe alternatives you've considered
We could add a flag on Rox to avoid storing files.
Additional context
None

@psanders  https://github.com/fonoster/rox/pull/9


Sync eng/common directory with azure-sdk-tools for PR 1496

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/1496  See eng/common workflow

/check-enforcer override


"loopOut()" expression not working

I have an animation where only a part of it loops infinitely, in after effects i created this using a loopOut() expression.
When i imported the animation into lottie , it didnt work ,
Setting loop prop to true only resets the entire animation ,
UPDATE: it was a problem in the bodymovin script , fixed

I have the same problem, what have you fixed?


commonFramework-d332a71687.js Error

Challenge Bonfire: Seek and Destroy has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
I have been able to successfully run the below code in Chrome's console and on Codecademy.com. When I run on FCC I get the response: "i is not defined". When I look at the console to determine if there are any errors, I see the following message:
i is not defined(anonymous function) @ commonFramework-d332a71687.js:1

Successful test on other javascript console:  http://bit.ly/1PwjqZa
My code:
function destroyer(arr) {
    for(i = 1, al = arguments.length; i < al; i++){
        argValue = arguments[i];
        arr = arr.filter(eliminator);
    }
    return arr;
}

function eliminator(value){
    return value != argValue;
}

destroyer([1, 2, 3, 1, 2, 3], 2, 3);
//Tested in console returns [1,1]

//destroyer([1, 2, 3, 5, 1, 2, 3], 2, 3);
//destroyer([3, 5, 1, 2, 2], 2, 3, 5);
//destroyer([2, 3, 2, 3], 2, 3);
//destroyer(["tree", "hamburger", 53], "tree", 53)

You are creating global variables by leaving off the var in front of variable declarations. This is bad practice and fails in strict mode, which is what our tests now run in.
Thanks and happy coding!


Rtl support

hi friend ,
can you add support for right to left language  like Persian or Arabic ?
if any help requested i can help you for that .

Any help would be greatly appreciated! Feel free to point out all broken widgets and layouts you spotted.
I was thinking about RTL support for a long time, but nobody asked, so I put that away. I've never used any of these languages, so I'm not sure which things should be inverted. Like, for example, the check graphics in CheckBox?

Carbon in most cases supports RTL layouts without any changes, because it uses Android widgets as a base. I've added suport for Toolbar and TableLayout. If you notice that something is not working as expected, please open another issue for that specific thing. Attach a screenshot and a short explanation.

hi again , and sorry for late.
android only support layout direction in api 17 and up . and this is the real problem .

You're right. It's a large task and I'm not sure if I can backport directionality to older platforms. I would have to reimplement layouting, directionality attributes, text drawing and many other things. It could break low-level View compatibility with other libraries and built-in Android UI.
For now Carbon supports RTL only if it's supported by the system.
I'm reopening this issue to keep it in mind.

hi ,
i do this work in other way in my own app before and ill hope it can be done here.

i create Utility class with RtlUtil name that

public class RtlUtils
{

    private static final Set<String> RTL;

    static
    {
        Set<String> lang = new HashSet<String>();
        lang.add("ar"); // Arabic
        lang.add("dv"); // Divehi
        lang.add("fa"); // Persian (Farsi)
        lang.add("ha"); // Hausa
        lang.add("he"); // Hebrew
        lang.add("iw"); // Hebrew (old code)
        lang.add("ji"); // Yiddish (old code)
        lang.add("ps"); // Pashto, Pushto
        lang.add("ur"); // Urdu
        lang.add("yi"); // Yiddish
        RTL = Collections.unmodifiableSet(lang);
    }
    public static boolean isRTL(Context context){
        return isRTL(context.getResources().getConfiguration().locale);
    }
    public static boolean isRTL(Locale locale)
    {
        if(locale == null)
            return false;

        // Character.getDirectionality(locale.getDisplayName().charAt(0))
        // can lead to NPE (Java 7 bug)
        // https://bugs.openjdk.java.net/browse/JDK-6992272?page=com.atlassian.streams.streams-jira-plugin:activity-stream-issue-tab
        // using hard coded list of locale instead
        return RTL.contains(locale.getLanguage());
    }

then i add other xml layout for existing layout like this one for navigation view.
its your default nav row xml layout

and i add this one is rtl nav row

with this xml file
<?xml version="1.0" encoding="utf-8"?>
<carbon.widget.LinearLayout
    android:layout_height="wrap_content"
    android:layout_width="match_parent"
    xmlns:android="http://schemas.android.com/apk/res/android"
    android:orientation="vertical"
    android:clickable="true"
    android:focusable="true">
    <carbon.widget.RelativeLayout
        xmlns:android="http://schemas.android.com/apk/res/android"
        xmlns:app="http://schemas.android.com/apk/res-auto"
        app:carbon_rippleColor="?attr/carbon_rippleColor"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
       >
        <carbon.widget.TextView
            android:layout_alignParentLeft="true"
            android:layout_alignParentTop="true"
            android:layout_toLeftOf="@+id/carbon_itemIcon"
            android:paddingLeft="@dimen/carbon_padding"
            android:paddingRight="@dimen/carbon_padding"
            android:textSize="25sp"
            android:text="سطر تستی"
            android:id="@+id/carbon_itemText"
            android:gravity="center_vertical"
            android:layout_width="match_parent"
            android:layout_toRightOf="@+id/carbon_itemIcon"
            android:layout_height="@dimen/carbon_toolbarHeight" />
        <carbon.widget.ImageView
            android:layout_alignParentTop="true"
            android:layout_alignParentRight="true"
            app:carbon_tint="?attr/colorAccent"
            android:id="@+id/carbon_itemIcon"
            android:padding="@dimen/carbon_padding"
            android:layout_width="@dimen/carbon_toolbarHeight"
            android:layout_height="@dimen/carbon_toolbarHeight"
            android:background="@android:drawable/ic_delete"/>

    </carbon.widget.RelativeLayout>

</carbon.widget.LinearLayout>

and when i going to inflate navigation layout i inflate it in below way:
 if (Build.VERSION.SDK_INT < Build.VERSION_CODES.JELLY_BEAN_MR1 && RtlUtils.isRTL(parent.getContext())) {
                    view = inflater.inflate(R.layout.carbon_navigation_row_rtl, parent, false);

                } else
                    view = inflater.inflate(R.layout.carbon_navigation_row, parent, false);

thank you.

I understand your approach, but I would like to have something more universal. Picking rtl or ltr layout works well with your specific cases, but a user may want to use a generic layout with items ordered using toEndOf, gravity="start", etc. A good library should provide a generic way of layouting for both directionalities.
As for your directionality detection - Locale class has some definitions which may be useful. You may find this code http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/5.1.1_r1/android/view/View.java/#13194 interesting. I'm not sure if that would work on old Android.

Seems like detection and layouts are not the real problem. EditText is much worse with all these weird selection/edition behaviors when mixing languages. Unfortunately I won't be able to backport that.


An item is in error state

I'm getting the following error when navigating from the startpage to '/guides/' (it works when accessing it directly, as the static build suceeded):
An item is in error state path=content%2Fguides&id=

I suspect this might be because Github Pages can't serve up the .json file, as the file is clearly there in the repo.
Maybe index routes should be stored as index.json rather than .json?

That did nothing, unfortunately.

I already got similar issues in the past and found this https://help.github.com/articles/files-that-start-with-an-underscore-are-missing/ that helped me. I will try to have a look in a few days. Contribution welcome if you have the time. So not hesitate to ask for help if you struggle with a contribution, I will do my best even if I don’t have a computer atm.

I think creating a _config.yml with the following content fixed it:
include:
- *.json

I will try to make this invisible to end users, probably by avoiding this .../.json files.


fix: fix all bugs in mergeGroup().

Proposed changes
fix all bugs in mergeGroup()
Problem summary
bug:

Removed Group (after merge) also may be in Job Stack.
mergeGroup() should deal with separately the different condition (whether reinsertGroupExpr and existedGroupExpr are in same Group)
Due to PhysicalEnforcer just in lowestCostPlans, isn't in groupExpressions, need to notice it.
PhysicalEnforcer have a owner Group, but owner-Group's physicalExpression don't include it (due to avoid dead loop)
we also should move/merge

physical property in GroupExpression
lowestCostPlans in Group

.... more detail bug

Checklist(Required)

Does it affect the original behavior:

[x] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[x] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[x] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 36.05 seconds
load time: 506 seconds
storage size:<PHONE_NUMBER>5 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230118194726_clickbench_pr_83611.html


rad clone fails in a singe-node scenario with failed no seeds found

https://github.com/radicle-dev/heartwood/commit/e584bd6c1cbb5c8bb9b74a856f6fdd7c22392efe: If you push a project to your node and then try to clone it from same profile/node, you'll encounter:
== Clone failed no seeds found for rad:z5mjpEsLp9yLYyD5gez85eamUEmk

this problem doesn't exist in a multi-node setup.

looked into clone and we can try a checkout here but this doesn't seem to be the right way to go about this, e.g. it could also be the case that the network is temporarily down, in that case does it default to local clone?


Publish CAS Events

Allow CAS to publish events based on Spring, specific to the following cases:

Establishing of an SSO session
Destruction of an SSO session
Generation of a Service Ticket
Validation of a Service Ticket
Adding/Removing Services

(The list above closely follows the inspektr AUDIT events)
Should probably happen once we upgrade to Spring 4.2. This opens up a possibility to register Spring's ApplicationListeners for event(s) of interest and proceed with custom computation(s) based on those events.

https://spring.io/blog/2015/02/11/better-application-events-in-spring-framework-4-2

https://github.com/Unicon/cas-addons/tree/master/src/main/java/net/unicon/cas/addons/info/events

What's the goal of publishing all these events? Compared to the audit logs?

The audit log is purely for auditing and tracking purposes. It makes upper management happy basically, and allows the CAS deployer to keep track of sometimes strange login activity.
This feature on the other hand is targetted towards the CAS developer. It is the case where you would want to gather stats about a particular CAS event and do something about them later. While the audit log has a fixed and clear format, this will be in the hands of the deployer to decide what should be saved, how and where in a very decoupled manner without ties to any hardcore APIs. It has other use cases, such as keeping track of login history to be used with MFA use cases.

Depends on https://github.com/Jasig/cas/issues/1084

Should be done after #1192 closes. The event support should be in its own module.

another example of this use case is, cache listeners for hazelcast for instance can start to publish events when tgts expire. so that the logout  manager can then be invoked without so wiring the logout module to the hazelcast module.
or think about gathering stats on casimpl so that we could later do risk based authn.

working on this issue next.


Remove duplicate swagger operationIds

Ensure each declared operationId is unique, and that overloaded endpoints' docs are declared in only one location so that they are formatted in the swagger doc as variations of the same endpoint

Codecov Report

Merging #1195 (a08d8cd) into master (218d301) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1195   +/-   ##
=========================================
  Coverage     99.50%   99.50%
  Complexity     3081     3081
=========================================
  Files           470      470
  Lines          9054     9054
  Branches        480      480
=========================================
  Hits           9009     9009
  Misses            5        5
  Partials         40       40

Flag
Coverage Δ
Complexity Δ

unittests
99.50% <ø> (ø)
0.00 <ø> (ø)

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

Impacted Files
Coverage Δ
Complexity Δ

...n/java/com/quorum/tessera/api/ReceiveResponse.java
100.00% <ø> (ø)
11.00 <0.00> (ø)

...rum/tessera/api/common/RawTransactionResource.java
100.00% <ø> (ø)
5.00 <0.00> (ø)

...com/quorum/tessera/q2t/EncodedPayloadResource.java
100.00% <ø> (ø)
20.00 <0.00> (ø)

...va/com/quorum/tessera/q2t/TransactionResource.java
100.00% <ø> (ø)
21.00 <0.00> (ø)

...a/com/quorum/tessera/q2t/TransactionResource3.java
100.00% <ø> (ø)
15.00 <0.00> (ø)

Continue to review full report at Codecov.

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


The function 'layers/convolutional.pydoes not followtf.GraphKeys` convention

In convolutional.py bias and weight variables are created and named kernel and bias. However according to the conventions defined in tf.GraphKeys.md those variables should be named  weights and biases and assigned the corresponding collections. There is some (third party) functionality which utilizes this convention, including tf.contrib.layers.summarize_weights.
In addition, the names to be used are also stored in the constants tf.GraphKeys.WEIGHTS and tf.GraphKeys.BIASES. So instead of writing the strings hard in the code, I would suggest utilizing those constants. Do you agree with that? I am happy to submit a pull request solving this issue, if desired.

@fchollet: Is a PR welcome?

No, the proper convention is kernel and bias, which is used throughout core layers. This has been extensively discussed internally.

ok, you are right. From what I understand by now the https://github.com/tensorflow/tensorflow/blob/master/tensorflow/g3doc/api_docs/python/functions_and_classes/shard8/tf.GraphKeys.md conventions are not about the names of Variabels but collections those Variabels should be added.
So  the following lines should be in there:
    tf.add_to_collection(tf.GraphKeys.WEIGHTS, self.kernel)
    tf.add_to_collection(tf.GraphKeys.BIASES,  self.bias)

I am happy to put this into a pull request.

These keys are almost never used.
The only layer that uses them is:  "contrib.layers.legacy_fully_connected".
(Then a few things in contrib.layers book-keeping ops read them, they're mentioned in the contrib/layers/README.md)
There is no way to automatically set these, like with trainable variables.
For it to actually work as tf.contrib.layers.apply_regularization wants it to, it would need to be set everywhere, not just in convolutional.
So I don't think fixing convolutional.py is the right choice.
Currently the core tf.layers is not using them so that may be a clue that they are not part of the future.


[Spotify Player] Menu Bar Player and Now Playing doesn't work as expected

Extension
https://www.raycast.com/mattisssa/spotify-player
Description

Error:
Run Error: Command terminated, code: 14 (Timeout)

Steps To Reproduce
Open Raycast and Type Now Playing or Menu Bar Player while Spotify App is playing the music in the background.
Current Behaviour
They show a loading screen or Error and doesn't load the song that is currently playing.
Expected Behaviour
Now playing is expected to show the currently playing song and Menu Bar Player is supposed to load the song name on the menu bar.

same


embedded-redis initialisation fail

FixedHostPortGenericContainer creation done using
RedisProperties.dockerImage and RedisProperties.port fields instead of using getters.
In case RedisProperties instance is CGLIB enhanced by Spring - these properties have null value
which causes initialisation failure.
FixedHostPortGenericContainer instantiation should be done useing redisProperties getters.

although it's indeed an issue, I wonder why so far only you faced it.
In any case, feel free to submit PR, I do have nothing against using setters.

Hi,
please give me permissions.

@anoiio unfortunately we cannot give you permissions to the repo, you will need to fork the repo to make the changes. please check https://github.com/Playtika/testcontainers-spring-boot#how-to-contribute guide


Post process events

For serverless implementation, add an event when batch processing is complete.
Also optimize batch processing to do nothing when there are no messages in the queue, and avoid setTimeout if delay is set to 0.

@ittaibaratz,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


added function "semver_id_fwrite()"

This function is useful for debugging purposes.

This implementation isn't cross platform and does not follow the global code style of the library.

I do not understand why the build fails on AppVeyor: it looks like standard C99 to me, with variable length arrays.
About the code style: is it because of blanks, or variable naming, or both?

The microsoft c compiler does not fully support c99 in old versions, I'm known this reduce the way to write code and force us to use bad patterns but I want the code to be Win compatible without using mingw or related.
No variables naming is fine, I just mean code formatting, I use this
void func_name(void) {
  /* do something */
}

@uael Or we can use the /TP compile option on msvc to compile C99 code as c++. Or add set_languages("c99") in xmake.lua. xmake will automatically handle C99 compilation problems on msvc.

@waruqi cool :+1:


feat: improve task naming

A couple improvements to task naming:

For function commands, search for first occurrence of a filename argument, and strip from that point onwards.
For commands in general, strip common package runner prefixes (and their options): npm, npx, yarn (unless it would strip the entire command).
Drop the ellipsis from function commands, to be consistent with non-function commands.

Fixes: #828

Looks nice, and a good improvement!
Let's just leave out the second bullet of stripping out prefixes to simplify code and not cause unexpected issues (users not recognizing the command).

It seems the path match doesn't quite work on Windows:
- LOG [Function] prettier --write [started]
- LOG [Function] prettier --write [completed]
+ LOG [Function] prettier --write C:\projects\lint-staged-test\AqocQtX4BMGjgyZNYR1jx\test.js [started]
+ LOG [Function] prettier --write C:\projects\lint-staged-test\AqocQtX4BMGjgyZNYR1jx\test.js [completed]

Appveyor logs

Maybe the simplest method would be to, for the string npm run test -- -u src/staged.js, to do:

Get the os path separator from path.sep. Eg. /
Split the command string from this and get the first part, eg npm run test -- -u src
Split the above from the last space and get the first part, eg npm run test -- -u

It should also be try/catched to a short fallback if no path.sep is not found, so that the entire string would not end up in the console.
What do you think?

Maybe the simplest method would be to, for the string npm run test -- -u src/staged.js, to do:

Get the os path separator from path.sep. Eg. /
Split the command string from this and get the first part, eg npm run test -- -u src
Split the above from the last space and get the first part, eg npm run test -- -u

It should also be try/catched to a short fallback if no path.sep is not found, so that the entire string would not end up in the console.
What do you think?

Wouldn't that fail for commands with no path separators (staged files in same directory), as well as potentially strip out starting from a non-staged file, such as config?
I'm thinking to tokenize the command (taking quotes into account), then walk through each token, checking for the first one that matches to the staged set (can resolve and compare absolute paths, if we want to be certain it's same file). Then strip from that point onwards. I can optimize the check against the staged set, if we're concerned about perf.

@jd20 You are true about the failing!

@iiroj  I'm interested in this as well.  I'm Wondering if something simpler like being about to put in a manual override would be better.  I'm also wondering why the command is getting cut off in so few characters?  It seems like it could afford to go up to the width of the terminal.

@fantapop thanks for the terminal width suggestion! That seems like a pretty easy improvement.

I opened PR https://github.com/okonet/lint-staged/pull/865 which will always take the full length task title (for both "simple" and functional tasks), and then truncates it to the current terminal columns, minus the prefix padding length caused by listr2. This means the task title will be as long as possible to fit on a single line, and will be clipped with an ellipsis ….
I'll close this PR since that should be a good enough solution.

This solution is working great. Thank you!


CF-Worker header info is wrong

Which Cloudflare product does this pertain to?
Workers
Existing documentation URL(s)

https://developers.cloudflare.com/fundamentals/get-started/reference/http-request-headers/#cf-worker

Section that requires update
The CF-Worker behavior is wrong.
What needs to change?
How the CF-Worker header is explained
How should it change?
It should mention that it'll always be your_org.workers.dev.
Additional information
No response

In what cases does this not use the zone name and always uses the workers.dev?
My Workers custom domain https://subrequest-headers.erisa.party/
and Workers Route https://erisa.party/subrequest-headers
both are sending Cf-Worker: erisa.party in subrequests to a non-cf origin

Oh. I guess I was mislead. =P

Is it possible to have like Cf-Worker: example.erisa.party too?

It's the zone name (what Cloudflare dashboard calls "websites"), so that would only happen if I added example.erisa.party as a separate subdomain zone: https://developers.cloudflare.com/dns/zone-setups/subdomain-setup/


Incorrect orientation of the north | Heading / Yaw

Hi,
I'm trying to rotate the image to north. I use the map.setYaw( HEADING) function to rotate.
The rotation does this, but the north is not good.
Even if the north is not the right direction, the photo should be oriented in the same direction all the time.
I have 100 pictures on a trajectory.
and finally, the compass doesn't look in the same direction as the picture.
demo1 : https://i.imgur.com/lDiMKRj.jpg
demo2 : https://i.imgur.com/rfE8ZtU.jpg
demo3 : https://i.imgur.com/ZVBOpZo.jpg
for(k in indexFile) {

                let filename = indexFile[k].img;
                let roll = indexFile[k].roll;
                let pitch = indexFile[k].pitch;
                let heading = indexFile[k].heading;

                let marker = L.marker([indexFile[k].lat, indexFile[k].lng], {icon: greenIcon}).on('click', function(e) {

                    viewer = pannellum.viewer('panorama', {
                        "type": "equirectangular",
                        "panorama": "https://atgt.s3.eu-west-3.amazonaws.com/"+project_id+"/"+filename,
                        "autoLoad": true,
                        "compass": true,
                        "northOffset": heading
                    });

                    console.log(filename);

                    viewer.setPitch(pitch);
                    viewer.setYaw(heading );

                    console.log(heading);
                });
}

What to fix? Thank you!

I see that you're setting a northOffset. The setYaw function calculates yaw based on image coordinates only (center of panorama is zero) and does not account for this offset, which is only used for the compass display (and sameAzimuth hot spot parameter). If you want to account for the north offset in setting the yaw, you'll need to do so manually.


Group Greetings

John Gulon and Jakob Linscheid greetings.
CoAuth: TheGreenN1nja<EMAIL_ADDRESS>

Very nice, I like


[Bug]: distribution url to index.json is being cached by CloudFront leading to old value of latest url

Describe the bug
The latest url has a logic to read from index.json https://github.com/opensearch-project/opensearch-build/blob/main/deployment/lambdas/cf-url-rewriter/cf-url-rewriter.ts#L14 However, this url is being cached by CloudFront.
When the following URl
https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/1.3.0/latest/linux/arm64/builds/opensearch/manifest.yml it shows the latest number is 1024

However, by visiting the S3 bucket, the content is the file is actually 1028

Based on my research, by the default, the CF cache is 24hours which means that currently the latest url is using whatever built 24 hours ago. https://aws.amazon.com/premiumsupport/knowledge-center/cloudfront-serving-outdated-content-s3/
To reproduce
See the description part.
Expected behavior
The latest shall get the actual latest or at least a much short cache ttl (maybe 5mins?)
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output
No response

Based on my research below, I may need to invalidate the url by '/*'
https://aws.amazon.com/premiumsupport/knowledge-center/cloudfront-serving-outdated-content-s3/
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html#invalidation-specifying-objects
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html#invalidation-specifying-objects-paths
cc @dblock @seraphjiang for visibility.

Just updating Invalidation doesn't work during my local test. Notice there is another layer of cache at origin configuration.
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/origin-shield.html
Dig more.

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/distribution-web-values-specify.html#DownloadDistValuesObjectCaching

Thanks @sichend for sharing knowledge that invalidation is one-time thing and is not lasting.

These are the current settings in the cloudfront:
https://github.com/opensearch-project/opensearch-build/blob/main/deployment/lib/artifacts-public-access.ts#L34-L54
Can you check what needs to be changed?

These are the current settings in the cloudfront:
https://github.com/opensearch-project/opensearch-build/blob/main/deployment/lib/artifacts-public-access.ts#L34-L54
Can you check what needs to be changed?

yep. I am checking the syntax to add a custom cache policy to the CloudFront and will run experiments in my personal AWS account.

Add               defaultTtl: Duration.seconds(0) to the following block. Running cdk deployment locally to see if it can take effect.
behaviors: [
            {
              isDefaultBehavior: true,
              compress: true,
              allowedMethods: CloudFrontAllowedMethods.GET_HEAD,
              lambdaFunctionAssociations: [{
                eventType: LambdaEdgeEventType.VIEWER_REQUEST,
                lambdaFunction: urlRewriter.currentVersion,
              }],
              defaultTtl: Duration.seconds(0)
            },
          ],

Verified the proposed change. Making a PR...


Animate in/out for PDS change, invite code change, etc.

Little follow up to https://github.com/bluesky-social/social-app/pull/3148
Adds some animations to the signup Step 1 so that transitions are not as jarring.
https://github.com/bluesky-social/social-app/assets/153161762/752ca305-1534-4dde-801e-221197075055

@mozzius Since you actually got around to doing the ALF login sooner than I thought it was going to happen, I say we just wait to merge those in 🚀


Having difficulty installing the Componentize.DotNet package

I was reading about this project and tried following the demo.  As expected, the following steps worked fine:
dotnet new console --name hello-wasm
cd hello-warm
dotnet new nugetconfig

Update nuget.config to reflect the following:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
 <packageSources>
    <!--To inherit the global NuGet package sources remove the <clear/> line below -->
    <clear />
    <add key="dotnet-experimental" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-experimental/nuget/v3/index.json" />
    <add key="nuget" value="https://api.nuget.org/v3/index.json" />
 </packageSources>
</configuration>

The problem comes on the next step:
dotnet add package BytecodeAlliance.Componentize.DotNet.Wasm.SDK --prerelease

My console reads the following:

PS C:\Users\whit_\source\repos\WasmDotNet\hello-wasm> dotnet add package BytecodeAlliance.Componentize.DotNet.Wasm.SDK --prerelease
Build succeeded in 0.8s
info : X.509 certificate chain validation will use the default trust store selected by .NET for code signing.
info : X.509 certificate chain validation will use the default trust store selected by .NET for timestamping.
info : Adding PackageReference for package 'BytecodeAlliance.Componentize.DotNet.Wasm.SDK' into project 'C:\Users\whit_\source\repos\WasmDotNet\hello-wasm\hello-wasm.csproj'.
info :   GET https://pkgs.dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_packaging/fe324174-469a-4296-a9cb-1fd885bb6f2b/nuget/v3/registrations2-semver2/bytecodealliance.componentize.dotnet.wasm.sdk/index.json
info :   NotFound https://pkgs.dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/packaging/fe324174-469a-4296-a9cb-1fd885bb6f2b/nuget/v3/registrations2-semver2/bytecodealliance.componentize.dotnet.wasm.sdk/index.json 198ms
error: There are no versions available for the package 'BytecodeAlliance.Componentize.DotNet.Wasm.SDK'.
PS C:\Users\whit\source\repos\WasmDotNet\hello-wasm>

I see the package on Nuget.org so I thought that perhaps the readme was out of date and I could just install from the public NuGet, but that still can't seen to find the package:

PS C:\Users\whit_\source\repos\WasmDotNet\hello-wasm> dotnet add package BytecodeAlliance.Componentize.DotNet.Wasm.SDK --prerelease
Build succeeded in 0.7s
info : X.509 certificate chain validation will use the default trust store selected by .NET for code signing.
info : X.509 certificate chain validation will use the default trust store selected by .NET for timestamping.
info : Adding PackageReference for package 'BytecodeAlliance.Componentize.DotNet.Wasm.SDK' into project 'C:\Users\whit_\source\repos\WasmDotNet\hello-wasm\hello-wasm.csproj'.
error: There are no versions available for the package 'BytecodeAlliance.Componentize.DotNet.Wasm.SDK'.
PS C:\Users\whit_\source\repos\WasmDotNet\hello-wasm>

What am I doing wrong? Thank you!

Interesting, I just tried this out and I am getting the initial 404 but then it finds it on nuget.org's package list:
 dotnet add package BytecodeAlliance.Componentize.DotNet.Wasm.SDK --prerelease

Build succeeded in 1.5s
info : X.509 certificate chain validation will use the default trust store selected by .NET for code signing.
info : X.509 certificate chain validation will use the default trust store selected by .NET for timestamping.
info : Adding PackageReference for package 'BytecodeAlliance.Componentize.DotNet.Wasm.SDK' into project 'C:\Users\jstur\projects\wasm-compontents\hello-wasm\hello-wasm.csproj'.
info :   GET https://pkgs.dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_packaging/fe324174-469a-4296-a9cb-1fd885bb6f2b/nuget/v3/registrations2-semver2/bytecodealliance.componentize.dotnet.wasm.sdk/index.json
info :   GET https://api.nuget.org/v3/registration5-gz-semver2/bytecodealliance.componentize.dotnet.wasm.sdk/index.json
info :   OK https://api.nuget.org/v3/registration5-gz-semver2/bytecodealliance.componentize.dotnet.wasm.sdk/index.json 79ms
info :   NotFound https://pkgs.dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_packaging/fe324174-469a-4296-a9cb-1fd885bb6f2b/nuget/v3/registrations2-semver2/bytecodealliance.componentize.dotnet.wasm.sdk/index.json 101ms
info : Restoring packages for C:\Users\jstur\projects\wasm-compontents\hello-wasm\hello-wasm.csproj...
info :   GET https://pkgs.dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_packaging/fe324174-469a-4296-a9cb-1fd885bb6f2b/nuget/v3/flat2/bytecodealliance.componentize.dotnet.wasm.sdk/index.json
info :   GET https://api.nuget.org/v3-flatcontainer/bytecodealliance.componentize.dotnet.wasm.sdk/index.json
info :   NotFound https://pkgs.dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_packaging/fe324174-469a-4296-a9cb-1fd885bb6f2b/nuget/v3/flat2/bytecodealliance.componentize.dotnet.wasm.sdk/index.json 119ms
info :   OK https://api.nuget.org/v3-flatcontainer/bytecodealliance.componentize.dotnet.wasm.sdk/index.json 75ms
info :   GET https://api.nuget.org/v3-flatcontainer/bytecodealliance.componentize.dotnet.wasm.sdk/0.5.0-preview00008/bytecodealliance.componentize.dotnet.wasm.sdk.0.5.0-preview00008.nupkg
info :   OK https://api.nuget.org/v3-flatcontainer/bytecodealliance.componentize.dotnet.wasm.sdk/0.5.0-preview00008/bytecodealliance.componentize.dotnet.wasm.sdk.0.5.0-preview00008.nupkg 279ms

Are you not seeing those additional look ups?  What version of .NET are you using?

Nope - the log is precisely as I pasted earlier. I'm running .NET 9.0.100 (per dotnet --version).

It looks like it's not finding the nuget package source.  It should use the local one, but any chance you have configuration else where? https://learn.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior#how-settings-are-applied


Clear search term when pressing the 'X' button.

The sidebar returns to the legend as it should, but when returning to search the input field should be empty (i.e., pressing 'x' should also clear the search term).

Update here: Let's follow diverseLevant mobile and use a back arrow to exit out of text search. This will keep mobile and desktop versions a little closer. The 'x' button is not necessary, unless you want to use it to clear the search term (and not exit search). I do, however, still think we need an obvious clear results button here when searching via click or area a la #142, so shouldn't use the back button in those cases.


webui: infinite loading of the boot files

The "Nodes" tab will display continuous loading icons for each of the boot files.

Regarding this feature, I believe it should be entirely dynamic, capable of handling any files that appear in the result folder. For instance, if we choose to package the kernel, ramdisk, and kexec-script into a archive for single download only, it should be able to manage it. Additionally, since we plan to provide a choice between the isoImage and kexecTree output formats, it should be able to handle that as well.
I would like to hear @jhvst's opinion on this.

P.S. I tried adding the '-r' flag to the build command to resolve the symlinks, as it also changes the permissions, but that did not help.

Got it, the paths here are wrong: https://github.com/ponkila/HomestakerOS/blob/f2ed12f0a29651b5f1a331197e54290e6f167b0c/webui/src/Context/NodeInfoContext.tsx#L33-L46
They should be:
/nixosConfigurations/${hostname}/result/<filename>

They should be:

Good to know 👍
As for handling arbitrary files in the result folder, the simplest option I see is to have some sort of files.json that describes the available files. The frontend can then read this file.

Closed by #27.


[ERD] Tables are shown incorrectly if they are resized and then arranged

System information:

Operating system (distribution) and version win 10 x64
DBeaver version 7.0.1 EA

Steps to reproduce, if exist:

Open any ERD
Change table size to smaller
Arrange diagram - Problem is solved after refreshing

Fixed

verified


Display of all browser windows

Describe the bug
If you have many browser windows open, TabTabTab cannot display them all.
To Reproduce
Steps to reproduce the behavior:

Set the TabTabTab width to 400.
Open a lot of windows
Open TabTabTab and see that you can't see all windows in the window selection at the top.

Expected behavior
I would expect a scroll bar so that all windows can be displayed in TabTabTab.
Screenshots

System information

OS: Windows 11
Browser: Microsoft Edge or Google Chrome
Version of TabTabTab: 2.19.1

done by #202


ES6 instead of CoffeeScript

Guys, I suggest to replace CoffeeScript with new JavaScript standart - ES6 in Backbone Base, so I need your opinion on this.
The main reason is that ES6 includes most of the same features as CoffeeScript, and has a lot of new pieces that CoffeeScript doesn't, as well as many sweet tricks which will be included as a native syntax in browsers in future.
Another reason is that the current and newly appearing tools (such as JSPM and others) are based on ES6 features. In the nearest future JavaScript community will update all new frameworks and libraries using ES6 syntax and constructions, so I am sure that it eventually replace CoffeeScript. Overall I think that it will be easier to build rich JavaScript applications with ES6, trying new tools and frameworks. It will also be easier to understand different documentation b/c it will be fully based on JavaScript syntax. And obviously ES6 is a standart, while CoffeeScript is just a convenient metalanguage. So now I have an experience of how to move BB on ES6 with all current functionality but I need just your approving.
Here’s an awesome presentation about ES6: https://speakerdeck.com/rauschma/using-ecmascript-6-today.

Done. According to https://github.com/fs/backbone-base/pull/80 and https://github.com/fs/backbone-base/pull/81


Fixed some issues with the Fill class.

Needed a better implementation of the fill class, also managed to simplify the PostedPriceAuctionLike trait...

Coverage increased (+1.2%) to 69.231% when pulling a54888cd9b626e65c4adf710e3ede09ce4481943 on hotfix-fill-impl into f253bee059dae0248230036e3654d29ff5fd308a on develop.


Typescript support?

Hello!
Was wondering if typescript is on the roadmap for the dynamodb encryption SDK?
Chida

Hi @cananda,
It's on our roadmap, but no date has been decided right now.
Could you tell us more about your use case for TypeScript support?
Thanks!

Also very interested in this. Use case is to encrypt specific field values in records to protect user privacy.
Given that Typescript/Javascript and Python are by far the most popular languages for Lambda functions it is odd that neither are supported.
According to Datadog, nearly 80% of Lambda invocations are in one of these two runtimes. AWS probably know this already :)


Fix ambiguous instructions in Step 48 of Decimal to Binary Converter challenge

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #55995

Hey @FranThe3rd
Thank you for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


[BUG] unable to edit deployment rancher 2.6.8

Rancher Server Setup

Rancher version: v2.6.8
Installation option (Docker install/Helm Chart):

HA Helm RKE 1

Information about the Cluster

Kubernetes version: v1.24.4
Cluster Type (Local/Downstream):
Downstream RKE hetzner

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)
admin

Describe the bug
If you create a deployment with more than one Container you are unable to edit the second pod after creating.
To Reproduce

Create deployment with 2 Containers
Save
Edit

Result
Now you are unable to switch between containers (for example, look at healthcheck port)
!None! of the Form value updates
Expected Result
Form values should all be switched to correct container.
Additional context
Example yaml... where an example health check port should switch between 80 & 8080 on edit.
apiVersion: apps/v1
kind: Deployment
metadata:
  name: test
  namespace: default
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      workload.user.cattle.io/workloadselector: apps.deployment-default-test
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        workload.user.cattle.io/workloadselector: apps.deployment-default-test
    spec:
      affinity: {}
      containers:
      - image: nginx
        imagePullPolicy: Always
        name: container
        readinessProbe:
          failureThreshold: 3
          periodSeconds: 10
          successThreshold: 1
          tcpSocket:
            port: 80
          timeoutSeconds: 1
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      - image: nginx
        imagePullPolicy: Always
        name: anothercontainer
        readinessProbe:
          failureThreshold: 3
          periodSeconds: 10
          successThreshold: 1
          tcpSocket:
            port: 8080
          timeoutSeconds: 1
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30

Probably related / similar to #38871 (if someone what to see how the UI gets messed up between containers).