iOS app crashing on simulator after trying to enable GoogleMaps

I'm trying to enable GoogleMaps on the iOS version of my app. After following advice in this issue thread and then from Option 1 in this documentation, my app is now crashing when I try to start it up.
The terminal window tells me that the build has succeeded, and my app opens on the simulator, then immediately crashes. There are no warnings, errors, or outputs of any kind telling me what is wrong.
I'm not sure where to go from here to troubleshoot it--I tried to undo some of the last changes I had made in my xcode project before it happened but no success.
I can easily provide more information if needed, I just have no idea what to provide for this!

I haven't tried it on iOS yet but one thing I realized is that when making a lot of these changes I had to completely start the emulator over again instead of just refreshing it. So (if you haven't done this already) I would try to shut down the simulator/emulator and run:
watchman watch-del-all
npm clean cache
...and then try again?

Thanks for the suggestions @chapeljuice! I gave them a try and no luck, though--still crashing.

Alright, removing "AirGoogleMaps" from where I had moved it to (as recommended by Option 1 in the link in my original post) stops the app from crashing, but I'm back to square one where I can't enbable GoogleMaps on iOS.

I recently made a fresh example build with pods and GoogleMaps with no issues.
https://github.com/alvelig/react-native-maps-pods-example.
Try to check it out or build through the README.MD. If it does not help, let me know.


Fix RN 0.60+ installation by including podspec in package.json file list

This is required so the podspec will be downloaded and found by CocoaPods when installing pods locally during installation.
Closes #21.
@Traviskn Could you have a look and make a new NPM release if everything looks okay? I tried it with my forked repo and it worked 👌 Thank you!

thanks for fixing this!


Remove deprecated static functions replaced by UserSession

Can we get an estimate of how many apps will break if we do this?
The CLI will need to be refactored as well to accommodate this.

@zone117x So all the work to add in UserSession was back in April 2019.


feat(WEB-821): Add onScreenChanged callback to widget

In order to track analytics events once the user interacts with the embedded Typeform, I introduced a callback onScreenChanged activated by the form-screen-changed event introduced with this PR on stakhanov.

[BOT] Preview available: https://embed.typeform.com/45e901b6d9f495aad1ea1fd7515b9d0fc2dec0a9/embed.js

[BOT] Preview available: https://embed.typeform.com/ac1484633f2211f27c3bdd966599c4b4efc7ccbc/embed.js

[BOT] Preview available: https://embed.typeform.com/33955332f3718308dbf0f05a69a0ecc4e81aaa51/embed.js

:tada: This PR is included in version 0.28.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix: Improper whitespace trimming of column values

Additionally, this fixes a bug in the first substitute call, where the regex was looking for a string consisting of entirely whitespace. This could have been fixed by changing it to
call map(column, 'substitute(v:val, ''\s\+$'', "", "g")')

but the trim() function handles both cases without needing any regex.

thanks!


Translated UI & Some comments

Translated UI & Some comments
Program crashes when there's no Live2D Folder in Res. So, added Try~Catch in App.xaml.cs(Line62).

Thank you.
Was adopted from the commit history as much as possible.


Upgrade to 2024-01-08 rust toolchain

Relevant PRs:

https://github.com/rust-lang/rust/pull/119601
https://github.com/rust-lang/rust/pull/119146
https://github.com/rust-lang/rust/pull/119174

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

Thanks for doing this, @zhassan-aws ! Do you have any remarks on the regression we saw in #2962? It looks like the change in program steps and VCCs is still there but it doesn't affect solving time in the latest CI run.

The failure in the benchcomp run is due to an increase in the solver runtime for s2n-quic/quic/s2n-quic-core/sync::spsc::tests::alloc_test from 27 to 42 seconds (~55% increase). However, this increase only results in a 39% increase in the overall verification time (from 40 to 56 seconds), which is within our 50% threshold.

Thanks for doing this, @zhassan-aws ! Do you have any remarks on the regression we saw in https://github.com/model-checking/kani/pull/2962? It looks like the change in program steps and VCCs is still there but it doesn't affect solving time in the latest CI run.

Interestingly, the failure we were seeing in recovery::rtt_estimator::test::weighted_average_test with the previous PR (https://github.com/model-checking/kani/pull/2962) is no longer occurring. In fact, verification time improved by ~5% for this test (down from 104 seconds to 98).


I get an Unknown Error with entering browser.

Describe the bug

When I entered the browser(https://aims2.llnl.gov/search), I got an Unknown Error and couldn't go to page 'Sign In'.
Yesterday, I put some datasets into a cart and off my computer.
When I entered the brower, I got an Unknown Error and "please empty cart"(I don't remember exactly;).
I went to 'Cart' page(including 10 datasets) but its loading was too long.
After I deleted Chrome site records and cookies, I entered the brower again.
And here's my situations: Unknown Error / 'Sign In' page is 'BAD GATEWAY' / 'Cart' page is empty

+I reboosted my system but it didn't work.
What can I do?
Desktop (please complete the following information):

OS: Windows 10

Browser and Version: Google Chrome Version 129.0.6668.59 (Official Build) (x86_64)

To Reproduce

Expected behavior

Screenshots

Additional context

I have the same issue

Did someone have a solution?

Hi, for the pre-release you can try https://esgf-dev1.llnl.gov/  will have better functionality.
For an older stable release but several versions back you can try https://nimbus.llnl.gov/metagrid
We are working on a solution, but might not be working until next week.

Sorry for the delay, the original link is now updated and functional again.


[BUGFIX] fix failed testcase in test_models_gpt.py

Description
fix to pass
python3 -m pytest --device="cpu" --device="gpu" test_models_gpt2.py
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Thanks for the fix. I noticed that this pr triggered Unknown event.


clock: Add test coverage for SimpleIntervalClock

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Adds test coverage for SimpleIntervalClock
Which issue(s) this PR fixes:

Fixes #
NA
Special notes for your reviewer:
NA
Release note:
NONE

/assign @MikeSpreitzer @dims

/approve
/lgtm


Fix destroy thumbnail

This was a subtle bug.  As it turns out some associations have already been updated before the before_destroy callback is called, therefore image.observations, for example, is already empty at that point.  This is why unit testing is so important!

Coverage: 92.712% (-0.0003%) from 92.713% when pulling 75322b4390a497d87b631f36e0f2f6e76aadfac2 on fix-destroy-thumbnail into 02a4938ddc99213b2a038820b6ae007a97b58971 on master.

Hi @pellaea  - sorry I'm getting to this late, I couldn't read the code on my phone.
The attribute names seem a bit better, but still pretty confusing in my opinion.
It makes sense to me for an image to be a "glossary_term_thumbnail", "observation_thumbnail" or a "user_thumbnail", but "thumbnail_glossary_term" reads like a type of glossary term, and "subject" is none too clear, especially when users may pick mushrooms as their thumbnail image. Making these consistently "x_thumbnail" would read better in both directions, IMO.
It also goes along with the table names, "observation_images", "project_images" etc.

Well, I made the names going from image to glossary term, so that's right!
But maybe we can reverse it the other direction?  Wait, it is reversed the
other way:
image.thumbnail_glossary_terms --> yields glossary terms
glossary_term.thumb_image --> yields an image
I didn't like the randomness, best_glossary_terms and thumb_clients.
Neither made sense to me!
I guess in long-hand it would be
"glossary_terms_whose_thumbnail_is_this_image".  So what's a better
shortened version of that?  I didn't like my choice at first either, but it
grew on me and I like it now.  But I could probably learn to like something
else, too.  Let's just make sure it's the same convention for both
glossary_terms and observations!!
-Jason
On Mon, Jan 16, 2023 at 2:02 PM andrew nimmo @.***>
wrote:

Hi @pellaea https://github.com/pellaea - sorry I'm getting to this
late, I couldn't read the code on my phone.
The attribute names seem a bit better, but still pretty confusing in my
opinion.
It makes sense to me for an image to be a "glossary_term_thumbnail",
"observation_thumbnail" or a "user_thumbnail", but
"thumbnail_glossary_term" reads like a type of glossary term, and "subject"
is none too clear, especially when users may pick mushrooms as their
thumbnail image. Making these consistently "x_thumbnail" would read better
in both directions, IMO.
It also goes along with the table names, "observation_images",
"project_images" etc.
—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1283#issuecomment-1384445041,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYTNNJDOAWQU5S5DFCLBCTWSWLKRANCNFSM6AAAAAAT4AAFFM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Oh! If that's what it is, then i like it. Sorry for misreading it.
Definitely agree with the impulse to make it not random. Let's make it similar for obs, glossary and user all three.
So @image.thumbnail_glossary_term is the glossary term that has this image as a thumbnail...
Instead of subject for the user whose thumbnail is this image, how about thumbnail_user.

Don't forget there could be multiple of each going from images to
users/terms/obs (not sure why, but it's allowed!)
observations.thumb_image <-> image.thumbnail_observations
glossary_term.thumb_image <-> image.thumbnail_glossary_terms
user.image <-> image.(what?)_users
Is it okay that it is "thumb" on one side, and "thumbnail" on the other?  I
mean, we could normalize that, too.  I would recommend against changing
"thumb_image" to "thumbnail_image" because I think that's all over the
place (and would require a change to the database!), but the reflected
association is barely used at all, so we could easily change it to
image.thumb_observations and image.thumb_glossary_terms.
I have a little resistance to image.thumbnail_users.  Ideally we would also
change user.image to something else.  Technically it's the "profile image",
so that would be my preference:
user.profile_image <-> image.profile_users
Ugh, no, that doesn't work... or does it?  I don't know, maybe thumb would
be better...
user.thumb_image <-> image.thumb_users
Hmmm.  There is such a thing as making it too symmetric.
And it is entirely possible we are obsessing over this too much. :)
On Mon, Jan 16, 2023 at 3:23 PM andrew nimmo @.***>
wrote:

Oh! If that's what it is, then i like it. Sorry for misreading it.
Definitely agree with the impulse to make it not random. Let's make it
similar for obs, glossary and user all three.
So @image.thumbnail_glossary_term is the glossary term that has this
image as a thumbnail...
Instead of subject for the user whose thumbnail is this image, how about
thumbnail_user.
—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1283#issuecomment-1384519685,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYTNNMBTZBCUPTWXY74YM3WSWU37ANCNFSM6AAAAAAT4AAFFM
.
You are receiving this because you were mentioned.Message ID:
@.***>

It's ok, discussion's good. Naming is half the battle in documentation. You don't want some future numbskull like Nimmo asking you what the heck a "subject" is for an image.
I vote for symmetrical and simple. Howsabout thumb_profile_users, thumb_observations, thumb_glossary_terms.
It's definitely preferable to the current situation with best_glossary_terms and subjects.

Okay, since I'm doing the actual PR, I broke the ties -- which is to say,
in effect I completely ignored your votes! :)
thumb_glossary_terms
thumb_observations
profile_users
But note that User#image remains because, alas, renaming it to
profile_image would require changing the name of the database column.  Not
worth it!
On Mon, Jan 16, 2023 at 6:24 PM andrew nimmo @.***>
wrote:

It's ok, discussion's good. Naming is half the battle in documentation.
You don't want some future numbskull like Nimmo asking you what the heck a
"subject" is for an image.
I vote for symmetrical and simple. Howsabout thumb_profile_users,
thumb_observations, thumb_glossary_terms.
It's definitely preferable to the current situation with
best_glossary_terms and subjects.
—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1283#issuecomment-1384667887,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYTNNNT7UIMONAM3NBIMIDWSXKB5ANCNFSM6AAAAAAT4AAFFM
.
You are receiving this because you were mentioned.Message ID:
@.***>

I approve!


⚠ AlphaRatio has degraded performance

In f2b5b77, AlphaRatio ($AR) experienced degraded performance:

HTTP code: 200
Response time: 2208 ms

Resolved: AlphaRatio performance has improved in 0e62222 after 11 minutes.


Auto detect apparmor files based on vim syntax comments

Example found on Ubuntu 19.10
head /etc/apparmor.d/abstractions/ubuntu-browsers.d/user-files
# vim:syntax=apparmor

  # Allow read to all files user has DAC access to and write access to all
  # files owned by the user in $HOME.
  @{HOME}/ r,
  @{HOME}/** r,
  owner @{HOME}/** w,

  # Do not allow read and/or write to particularly sensitive/problematic files
  #include <abstractions/private-files>

Reacting to these comments would add some convenience (when often viewing AppArmor profiles), because currently one has to press {Ctrl} + {K}, {M} type 'aa' and press {Enter} to set the language to AppArmor.

@Caelagor thanks for the suggestion. I went through the vscode documentation and could not find a way to support this at the moment.
I opened an issue on their repo, as soon as that feature is supported I will implement it.

Could this be supported through https://github.com/ctlajoie/vscode-modelines if this extension adds an apparmor language code too?
With the modelines extension, # vim:syntax=aa did work for me, but not yet # vim:syntax=apparmor.


feat: have vs let linter

The have vs let linter flags uses of have to introduce a hypothesis whose Type is not Prop.
Here is a summary of the PR.  Besides changes have --> let this is everything else.

Mathlib/Analysis/Convolution.lean: two parallel simplified proofs.
Mathlib/CategoryTheory/Limits/Final.lean: the only have that could not be replaced by let.
Mathlib/Combinatorics/SimpleGraph/Connectivity.lean: vanishing haveSuffices due to have --> let.
Mathlib/LinearAlgebra/TensorProduct/Graded/Internal.lean: have := ...; exact this becoming exact ....
Mathlib/CategoryTheory/Sites/{ Sheaf.lean, SheafOfTypes.lean}: replace to let -- this is probably a regression.

I'm slightly concerned that the haves you're turning into lets were declaring data that we didn't care about and that Lean now has the option of unfolding when we know it is unnecessary.

Could you benchmark this PR once CI is green?
Could the linter only run on definitions and incomplete proofs? If a proof is complete, we know for sure the haves can stay haves. In a definition however, a type-valued have is most certainly a mistake.

Yaël, with respect to benchmarking, I was definitely planning on doing that, once I finish up the missing replacements.
Running the linter only on incomplete proofs: this is something that can probably be done.  My first approach would probably be to run the linter only if the command emits a warning.  I would probably still not run the linter with errors since then the type information is probably unreliable.

Is it possible to split this PR into:

Add the new linter, disabled-by-default
Enable the linter and fix all the occurences

Scrolling through 150 files to find the new meta code is pretty annoying, especially over a train internet connection...

@eric-wieser, I opened #12190 that contains only the linter and the tests.  I did not disable the linter, but I also did not import the file anywhere.

Actually, I don't really like my previous comment anymore. What about this instead?
The linter should send a warning on:

a Prop-valued let
a Type-valued have in an erroring branch of a proof

Note that the "Type-valued have in a completed sorry-free def" that I was referring to before is actually not bad since it's defeq to its value once the same is completed.


Uncaught Error: Cannot call function 'getPosition' on missing remote object 653Error: Cannot cal...

[Enter steps to reproduce:]

...
...

Atom: 1.38.2 x64
Electron: 2.0.18
OS: Ubuntu 18.04.2
Thrown From: Atom Core
Stack Trace
Uncaught Error: Cannot call function 'getPosition' on missing remote object 653
Error: Cannot call function 'getPosition' on missing remote object 653
at throwRPCError (/snap/atom/232/usr/share/atom/resources/electron.asar/browser/rpc-server.js:143:17)
at EventEmitter. (/snap/atom/232/usr/share/atom/resources/electron.asar/browser/rpc-server.js:354:7)
at emitMany (events.js:147:13)
at EventEmitter.emit (events.js:224:7)
at WebContents. (/snap/atom/232/usr/share/atom/resources/electron.asar/browser/api/web-contents.js:296:13)
at emitTwo (events.js:126:13)
at WebContents.emit (events.js:214:7)
At /snap/atom/232/usr/share/atom/resources/electron.asar/renderer/api/remote.js:221

Error: Cannot call function 'getPosition' on missing remote object 653
Error: Cannot call function 'getPosition' on missing remote object 653
    at throwRPCError (/snap/atom/232/usr/share/atom/resources/electron.asar/browser/rpc-server.js:143:17)
    at EventEmitter.<anonymous> (/snap/atom/232/usr/share/atom/resources/electron.asar/browser/rpc-server.js:354:7)
    at emitMany (events.js:147:13)
    at EventEmitter.emit (events.js:224:7)
    at WebContents.<anonymous> (/snap/atom/232/usr/share/atom/resources/electron.asar/browser/api/web-contents.js:296:13)
    at emitTwo (events.js:126:13)
    at WebContents.emit (events.js:214:7)

    at Object.exception (/snap/atom/232/usr/share/atom/resources/electron.asar/renderer/api/remote.js:221:30)
    at metaToValue (/snap/atom/232/usr/share/atom/resources/electron.asar/renderer/api/remote.js:225:28)
    at Object.remoteMemberFunction (/snap/atom/232/usr/share/atom/resources/electron.asar/renderer/api/remote.js:125:16)
    at AtomEnvironment.getWindowDimensions (/snap/atom/232/usr/share/atom/resources/app/static/<embedded>:1:703887)
    at AtomEnvironment.storeWindowDimensions (/snap/atom/232/usr/share/atom/resources/app/static/<embedded>:1:704302)
    at WindowEventHandler.handleWindowBlur (/snap/atom/232/usr/share/atom/resources/app/static/<embedded>:11:284649)

Commands
     -1:20.6.0 autocomplete-plus:confirm (input.hidden-input)
  3x -1:20.3.0 core:move-right (input.hidden-input)
     -1:19.1.0 core:backspace (input.hidden-input)
  3x -1:17.7.0 core:save (input.hidden-input)
     -1:03.8.0 core:backspace (input.hidden-input)
     -1:00.2.0 autocomplete-plus:confirm (input.hidden-input)
  3x -0:59.7.0 core:move-right (input.hidden-input)
     -0:58.7.0 core:backspace (input.hidden-input)
     -0:58.1.0 editor:newline (input.hidden-input)
     -0:57.3.0 core:backspace (input.hidden-input)
  2x -0:56.5.0 core:undo (input.hidden-input)
  3x -0:53.6.0 core:save (input.hidden-input)
     -0:29.5.0 autocomplete-plus:confirm (input.hidden-input)
  3x -0:29.1.0 core:move-right (input.hidden-input)
     -0:27.9.0 core:backspace (input.hidden-input)
 11x -0:26.6.0 core:save (input.hidden-input)

Non-Core Packages

Thanks for contributing!
We noticed that this looks like a duplicate of https://github.com/atom/atom/issues/16630 so you can subscribe there for updates if you'd like (we believe that this will be fixed in a future Electron upgrade).

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


safe write of manifest and lock: cannot delete : remove  directory not empty

go get -d github.com/gopheracademy/gopher
cd $GOPATH/src/github.com/gopheracademy/gopher
dep init
Importing configuration from godep. These are only initial constraints, and are further refined during the solve process.
Detected godep configuration files...
Converting from Godeps.json ...
  Using ^0.7.0-171-g7eaaec9 as initial constraint for imported dep cloud.google.com/go
  Trying * (7eaaec9) as initial lock for imported dep cloud.google.com/go
  Trying * (5120085) as initial lock for imported dep github.com/ChimeraCoder/anaconda
  Using master as initial constraint for imported dep github.com/ChimeraCoder/tokenbucket
  Trying master (c5a9275) as initial lock for imported dep github.com/ChimeraCoder/tokenbucket
  Using master as initial constraint for imported dep github.com/azr/backoff
  Trying master (53511d3) as initial lock for imported dep github.com/azr/backoff
  Using master as initial constraint for imported dep github.com/dustin/go-jsonpointer
  Trying master (ba0abea) as initial lock for imported dep github.com/dustin/go-jsonpointer
  Using master as initial constraint for imported dep github.com/dustin/gojson
  Trying master (2e71ec9) as initial lock for imported dep github.com/dustin/gojson
  Trying * (4f191fd) as initial lock for imported dep github.com/garyburd/go-oauth
  Trying * (9f174c9) as initial lock for imported dep github.com/golang/protobuf
  Using ^1.3.0-6-g4c1c395 as initial constraint for imported dep github.com/gorilla/mux
  Trying * (4c1c395) as initial lock for imported dep github.com/gorilla/mux
  Using ^0.1.0-2-gb5c480d as initial constraint for imported dep github.com/nlopes/slack
  Trying * (b5c480d) as initial lock for imported dep github.com/nlopes/slack
  Trying * (48359f4) as initial lock for imported dep golang.org/x/net
  Trying * (f047394) as initial lock for imported dep golang.org/x/oauth2
  Using master as initial constraint for imported dep golang.org/x/sync
  Trying master (f52d181) as initial lock for imported dep golang.org/x/sync
  Trying * (19e5161) as initial lock for imported dep golang.org/x/text
  Using master as initial constraint for imported dep golang.org/x/time
  Trying master (8be79e1) as initial lock for imported dep golang.org/x/time
  Trying * (0209b31) as initial lock for imported dep google.golang.org/api
  Trying * (d80a6e2) as initial lock for imported dep google.golang.org/genproto
  Using ^1.2.0-119-g2739967 as initial constraint for imported dep google.golang.org/grpc
  Trying * (2739967) as initial lock for imported dep google.golang.org/grpc
  Locking in master (2cadd47) for transitive dep github.com/googleapis/gax-go
  Locking in  (0209b31) for direct dep google.golang.org/api
  Locking in v1.0.0 (150dc57) for transitive dep google.golang.org/appengine
  Locking in v1.1 (1ea2538) for transitive dep github.com/gorilla/context
  Locking in  (48359f4) for direct dep golang.org/x/net
  Locking in  (5120085) for direct dep github.com/ChimeraCoder/anaconda
Old vendor backed up to /home/florin/go/src/github.com/gopheracademy/gopher/_vendor-20170828105311
safe write of manifest and lock: cannot delete /tmp/dep219341519/vendor: remove /tmp/dep219341519/vendor/google.golang.org/api: directory not empty

dep version: f1346974068313371d889e120ec9e01f5ba43642

i can't replicate this locally on either linux or OSX. is it replicable for you?


how to change opengl profile / graphics api in C# version? [question]

I could compile the c/c++/notepad++ version with
echo Set desired OpenGL API version: 1.1, 2.1, 3.3
SET GRAPHIC_API=GRAPHICS_API_OPENGL_21 // line 74

in notepads compile script ::raylib_source_compile link
but could not find a way how to change opengl profile / graphics api in C# version (my machine does not support preconfigured version)
Is it possible to do just with nuget package without cloning this repo?

Hi @riffshark,
To do this, you need to compile raylib yourself as the version provided via NuGet is from raylibs GitHub Releases. Once you have compiled your own version, all you need to do is drop the library into the build folder of the application - there should be no need to clone this repo.
We currently have no plans to provide a custom version of raylib with raylib-cs
Let us know if you have any more question or issues 😄

ok, I have next issue: I'm getting "System.BadImageFormatException" in Raylib-cs.dll on InitWindow()

I recompiled raylib.dll and /include/raylib.h with OpenGL2.1 (also tested in C that it works)
I had to replace raylib.dll in C:\Users\USERNAME\.nuget\packages\raylib-cs\<IP_ADDRESS>\runtimes\win-x64\native beacause on each run the dll was copied and replaced
on run this error occurs
how to fix this?

The default build output folder is bin/[Configuration]/[Framework] Configuration is usually Debug, Framework is sometimes omitted.  The win-x64/native folder is used for runtime/OS specific libraries in their "native" format; our NuGet package copies the libraries there on build.
BadImageFormatException Can mean a lot of things, most likely that the file you are trying to inter-op with is not valid (i.e. it is corrupt or in the wrong format/file type)


Igniters could provide more fully-fleshed email sender modules

Igniters such as ash_authentication.add_strategy password generate sender modules that look like this:
defmodule Tunez.Accounts.User.Senders.SendPasswordResetEmail do
  @moduledoc """
  Sends a password reset email
  """

  use AshAuthentication.Sender
  use TunezWeb, :verified_routes

  @impl true
  def send(_user, token, _) do
    # Example of how you might send this email
    # Tunez.Accounts.Emails.send_password_reset_email(
    #   user,
    #   token
    # )

    IO.puts("""
    Click this link to reset your password:

    #{url(~p"/password-reset/#{token}")}
    """)
  end
end

It took me a bit to realize that to actually send the email, I would have to create the Tunez.Accounts.Emails module, and define that function with the right copy and then create and send an email.
My thinking was that the igniter could generate something more fully-featured, like the example in the tutorial - https://hexdocs.pm/ash_authentication/confirmation.html#confirming-newly-registered-users, eg.

Create/update an Emails module with the new function eg. send_password_reset_email (and a deliver function if one doesn't exist)
Update the sender module to call that function in the Emails module
The email content can then be moved to the Emails module function
If adding the deliver function, it can print out the content and perhaps have the other content from the docs included but commented out

  # For simplicity, this module simply logs messages to the terminal.
  # You should replace it by a proper email or notification tool, such as:
  #
  #   * Swoosh - https://hexdocs.pm/swoosh
  #   * Bamboo - https://hexdocs.pm/bamboo
  #
  defp deliver(to, subject, body) do
    IO.puts("Sending email to #{to} with subject #{subject} and body #{body}")

    new()
    |> from({"Zach"<EMAIL_ADDRESS># TODO: Replace with your email
    |> to(to_string(to))
    |> subject(subject)
    |> put_provider_option(:track_links, "None")
    |> html_body(body)
    |> MyApp.Mailer.deliver!()
  end

So, we can do this, but to do it right we likely need to add a couple swoosh specific helpers, i.e Igniter.Libs.Swoosh. Eventually we'd like these to be extracted out to their respective libraries.

@sevenseacat I imagine you'd like this in for the auth chapter in the book. It also makes sense from our live stream today with Peter who expected to go to the dev mailbox and see the email right away. We ought to be able to set it up without too much hassle.

I'll try and do this tomorrow, but it might have to wait til next week.

Yes I did the exact same thing as Peter; when I saw the output in my logs I expected to also see it in an email in the dev mailbox.
Maybe it doesn't have to go that far, but having the Emails module set up ready to plug a mailer straight into would be a good compromise.


Bug #11223: Fixed returning an empty array when DbManager::getRolesByUser() was called on a user with user id 0

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues
#11223

Fixed returning an empty array when DbManager::getRolesByUser() was called on a user with user id 0

How about a unit test?

@SilverFire done and also tested if it actually tested the issue.

Looks good to me
@samdark ?

Yes. Good for me as well.

Thanks!


[wip] test: add local-gadget test

In this PR, we test IG and related BPF features on Flatcar with local-gadget.
We basically install local-gadget and prepare its run using CLC.
How to use
./build kola
./bin/kola list | grep gadget
bpf.local-gadget			[all]								[all]		[cl]		[all]		[all]

Testing done
=== RUN   bpf.local-gadget
=== RUN   bpf.local-gadget/dns_gadget
--- PASS: bpf.local-gadget (20.63s)
    --- PASS: bpf.local-gadget/dns_gadget (18.47s)
PASS, output in _kola_temp/qemu-2021-12-01-1126-8837

Related-to: https://github.com/flatcar-linux/Flatcar/issues/89

@pothos thanks for this quick review :joy: but it's still WIP, currently adding seccomp-gadget test.


group by changes for ibm details header

issue: https://issues.redhat.com/browse/COST-1372
group by changes for ibm details header

Codecov Report

Merging #2106 (9bc2a6e) into react-intl_changeover (3ba2124) will not change coverage.
The diff coverage is n/a.

@@                  Coverage Diff                   @@
##           react-intl_changeover    #2106   +/-   ##
======================================================
  Coverage                  70.37%   70.37%
======================================================
  Files                        410      410
  Lines                       7506     7506
  Branches                    1457     1457
======================================================
  Hits                        5282     5282
  Misses                      2192     2192
  Partials                      32       32

Impacted Files
Coverage Δ

src/locales/messages.ts
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 98af905...9bc2a6e. Read the comment docs.


Invalid prerender server output from jus-styles with material-ui beta

Problem description
The styles classes are mixed in production mode for server rendering (i use prerender)
To avoid the issue, i just applied as Jss use by default for the function generateClassName
var globalRef = typeof window === 'undefined' ? global : window;
var namespace = 'JSS_VERSION_COUNTER';
if (globalRef[namespace] == null) globalRef[namespace] = 0;
// In case we have more than one JSS version.
export default function createGenerateClassName(): generateClassName {
return (rule: Rule, sheet? : StyleSheet):
string => {
var ruleCounter = globalRef[namespace]++;
// etc...
if a not global var is used then jss produce same class name for some component (and the render is not correct)
I did not noticed any problem in virtual dom rendering , only in SSR
Link to minimal working code that reproduces the issue
Versions

Material-UI: Beta

You need to customize the createGenerateClassName on the server so that it match the one of the client. The guide

Yes  but in fact it's not a problem of SSR, (i did a mistake to write that)
I don't use any renderToString , my app is a single app
I use prerender as i told you , and the output of jss is not like in client mode, i don't know why but for me i need a global var else the styles are mixed
Nota; it's the render of the class  root of Drawer component who is mixed with the class of Paper himself,
At this point i'm sure that it's an issue, and not relative to my code

Hmm sorry a little mistake in fact it's due a bit to my code ,
My prerender merge all styles tag in head in one tag, and this merge 2 same name of class,
when the styles are rendered in different style tag the issue is not displayed, but still we have same class for 2 different component in production so it's not correct and can reproduce some issues


Loading model error

Couldn't create context with path /data/user/0/com.whispercppdemo/files/models/tiny.en.pt
8GB+128GB  android phone

".pt" doesn't seem like the correct extension. It should be something like "ggml-tiny.bin"

"ggml-tiny.bin" it work, thanks

Perfect :)


[WIP] Optimize performance of arrow fragment to dynamic fragment

What do these changes do?

Related issue number

Fixes

Codecov Report

Merging #1458 (c8b96ff) into main (2cdeb8e) will decrease coverage by 38.53%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #1458       +/-   ##
===========================================
- Coverage   73.65%   35.12%   -38.54%
===========================================
  Files          88       88
  Lines        9703     9703
===========================================
- Hits         7147     3408     -3739
- Misses       2556     6295     +3739

Impacted Files
Coverage Δ

python/graphscope/tests/unittest/test_lazy.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...ython/graphscope/tests/unittest/test_cython_ast.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...ython/graphscope/tests/unittest/test_serailaize.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...aphscope/tests/kubernetes/test_resource_builder.py
0.00% <0.00%> (-100.00%)
:arrow_down:

python/graphscope/analytical/udf/patch.py
3.47% <0.00%> (-96.53%)
:arrow_down:

...thon/graphscope/tests/unittest/test_scalability.py
0.00% <0.00%> (-96.16%)
:arrow_down:

python/graphscope/tests/unittest/test_app.py
0.00% <0.00%> (-95.53%)
:arrow_down:

...hon/graphscope/tests/unittest/test_create_graph.py
0.00% <0.00%> (-92.00%)
:arrow_down:

...on/graphscope/tests/kubernetes/test_demo_script.py
0.00% <0.00%> (-91.75%)
:arrow_down:

python/graphscope/tests/unittest/test_graph.py
0.00% <0.00%> (-84.68%)
:arrow_down:

... and 47 more

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 2cdeb8e...c8b96ff. Read the comment docs.

Performance comparison

Graph
single thread
multi-thread


Can't build because 'stdio.h' can't be found

I am trying to use the wtransport crate for a project, and wtransport uses ls-qpack.
While building ls-qpack on Windows, it fails with Unable to generate bindings: ClangDiagnostic("./deps/ls-qpack\\lsqpack.h:38:10: fatal error: 'stdio.h' file not found\n").
I tried to build the same program under linux (Ubuntu 22.04 LTS) and it worked perfectly.
Any help resolving this problem would be great! I love rust because I can rely on cargo as my only package manager. It defeats the purpose if I have to start managing C/C++ dependencies for my rust project.
Update:
I managed to get it to build by running cargo build from inside the Developer Command Prompt for VS 2022 (instead of a regular command prompt). While this works, I still feel like it's a little clunky.
It would be great if there could be an alternate, more rust-like solution, or perhaps update the documentation so people know that they need to build ls-qpack from inside of an environment with stdio.h

From my prev answer here: https://github.com/BiagioFesta/ls-qpack-rs/issues/2#issuecomment-1575711072
Unfortunately it is harder to deal with dependencies in Windows I guess. However, I built this crate in Windows without any problem by just ensuring to have installed:

Windows C compiler and runtimes (Windows Visual Studio)
Rust windows toolchain (via rustup)
LLVM (I've tested LLVM 9.0.1, for example: https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1)
CMake

I am not a Windows-guy, but I guess, in your case, your environment is missing some variable (e.g., PATH or something). The C toolchain (compiler, std headers, ...) are installed with Windows Visual Studio (with a default installation, everything should be easily found by bindgen).

It would be great if there could be an alternate, more rust-like solution, or perhaps update the documentation so people know that they need to build ls-qpack from inside of an environment with stdio.h

I totally agree on these points.
Allow me to comment on these two points:

This library is a Rust-FFI patter to the underlying C library implementing QPACK (needed by WebTransport). This obviously requires bindgen (and thus to compile the C library). I have created this crate for wtransport library because there are no alternative around. I really would like to avoid depending on something as heavy as Windows Visual Studio (which is a pretty heavy development tool) just to be able to compile a pretty small C library.

I am considering to limit QPACK functionalities in wtransport in order to use a minimal rust-pure implementation, but it is more of a temporary workaround than a definitive solution.
There are no rust libraries implementing QPACK (beside this one), but h3 (not stable yet) implements HTTP3 protocol which also depends on QPACK. I had the intention of asking the maintainers of h3 to try to export their rust QPACK implementation into a dedicated crate, but that's not within my control.

I totally agree on the documentation. I could simply add what I wrote at the top of this message in the README of this project.

Thank you for your feedback, and any help is more than welcome!

I would agree that updating the documentation is a good short-term solution.
Ultimately, I like the idea of asking the h3 maintainers to put their qpack implementation into a dedicated crate.
For the time being, I will continue to build my code from inside a Visual Studio environment, with the hopes that this problem will be addressed in the future. If I get the motivation and time, I might reach out to the h3 maintainers and 'politely beg' them to put their qpack implementation into a dedicated crate myself.
Thanks for the help! :)

I was doing some unrelated research and came across https://github.com/mozilla/neqo/. A mozilla-maintained QUIC implementation. In the source tree, there's a crate called neqo-qpack. neqo isn't available on crates.io but it still may be worth looking into!

I did not mean to close the issue...

Just a note: if you were using wtransport (https://github.com/BiagioFesta/wtransport).
Starting from today (master branch, but a release will come soon), ls-qpack-rs is not needed anymore.
wtransport now is pure-rust implementation and it does not require cmake, llvm, C-compiler anymore. You can read more here: https://github.com/BiagioFesta/wtransport/pull/119

You should now be able to compile wtransport just with rust toolchain

That's awesome. In that case, my problem is resolved. I'll keep this issue open since it'd still be nice to be able to natively build ls-qpack.
Feel free to close the issue if you're not interested in resolving this.

ls-qpack-rs is back-ed by ls-qpack (a C library); and that implies ls-qpack-rs requires some deps to build with C code.
As mentioned, ls-qpack-rs requires:

cmake (as ls-qpack C code uses that as build generator system)
C-compiler (of course, as ls-qpack -not rs- is written in C)
libclang shipped by LLVM (required by ls-qpack-rs for generating C bindings, thus Rust-code can interact with)

I know this should be properly documented, as required in: https://github.com/BiagioFesta/ls-qpack-rs/issues/8
ls-qpack-rs will never be a Rust-pure native library, as it would need to write another completely different library.
Even because that's what I've actually done in wtransport, writing a pure-rust (minimal) QPACK module.

Regarding your particular issue, if you have the above requirements installed everything should work quite out of the box. I have tested by myself, and CI (in wtransport) when it used to use ls-qpack-rs was working.
By just looking at your log-error, I guess it might be something depending on the environment. For example, VisualStudio is not installed, or it conflicts with another C-compiler (.e.g, mingw). Headers file (SDKs, etc) are not correctly installed/something is missing in the C-toolchain

Sounds good! I will go ahead and close this issue in favor of #8 for better documentation.
Thanks for the help :)


get valueOrDefault functionallity

Documentation Is:

[X] Missing or needed?
[ ] Confusing
[ ] Not sure?

Please Explain in Detail...
in this link the project is using valueOrDefault function, but I can't find it anywhere, I want to run chartjs on vuejs and trying to change my chart a bit with this example I mention
Your Proposal for Changes
add this function please
Example
No response

Since you are using vue and can't use the helper functions I expect you are using a bundler to build your code. In this case you will need to import these helper functions seperatly as described here in the documentation.
import { valueOrDefault } from 'chart.js/helpers';

Wow thank you very much, I did not see anything about that, it will be nice if someone who will search for this issue will find this thread sometime, meanwhile thank you and I'm closing the issue.


Add ConvertTo-Base64String and ConvertFrom-Base64 String cmdlets

Summary of the new feature/enhancement
With the help of @vexx32 I've put together a C# module that includes both ConvertTo-Base64String and ConvertFrom-Base64String which supports using the standard encodings available from System.Text.Encoding. I would like to see this included as part of PS Core, but am unsure of the process. I've heard rumblings the ideally the process moving forward would be to maintain it as module, and then add it in PS Core that way, but am fuzzy on the details
Proposed technical implementation details (optional)
I would like to see these two cmdlets make it into core, and am looking for direction as the best way to handle this moving foward. Should I PR the codebase in Core proper? Or should I PR the proposal to add the module as a dependency?
For your review the codebase is housed here: https://github.com/steviecoaster/PSBase64
NOTE: I still need to look at the documentation for adding good comment-based help to this module. It's my first foray into C#!

A couple of comments:

Not sure if this is a good thing or not.  cmdlets are nice and all, but having the full power of .NET with a simple method call (okay, it takes two method calls), makes this particular function seem overkill for C#, except maybe for handling io.streams.  Calling cmdlets take time and resources, directly calling the methods is much faster and uses fewer resources.

Case in point.  This line quickly decodes, alters, and then re-encodes and formats the string back to original, and it processes multi megabyte files in a blink of an eye.  (this manipulates a text file that has been encoded within a <data> element inside a .NET RESX file, returning it to the RESX file in an altered state.) https://github.com/msftrncs/PwshIFMResXTools/blob/master/IFM MPC RESX Reducer.ps1#L102-L108
$datablock.value = ([Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes(
            # convert from Base64String
            [Text.Encoding]::UTF8.GetString([Convert]::FromBase64String($datablock.value)
                # remove effectively empty S3, S2, or S1 DATA records
            ) -replace 'S(?:(?:3.{4})|(?:2..)|(?:1)).{6}(?:FF)+..\r*\n')
        # take the new Base64String and break it into 80 character lines formatted as assumed for the RESX file
    ) -replace '.{1,80}', "`n        `$&") + "`n"

On the other hand, wouldn't the PowerShell Gallery be an ideal place to showcase something like this?
Would there not be some use in providing other parameters from the .NET functions, such as the start character and length of characters, formatting options, or even the ability to input/output char[] (Base64CharArray())?
The other possibility I have seen used is to create custom types to alias these method calls, so again, a cmdlet may be overkill.  See https://tfl09.blogspot.com/2013/02/working-with-base64-strings-in.html.  (this is an example of adding a custom method to the string type to handle both encoding (fixed to Unicode) and conversion in a single virtual method.)  I could see this being improved to add additional methods to byte[] for the encoding, and that would make both functions more simple to use.  $newString = $origString.toUTF8ByteArray().toBase64String(), $decoded = $encoded.ConvertFromBase64().toUTF8DecodedString()

Working on a TextUtility module that will include this

Hi @SteveL-MSFT,
This has been quiet for a while, are you still working on this?
If not, can @steviecoaster's additions be added?

ConvertTo-Base64String would be very useful, especially if it had parameters LineLength with ValidateRange(64, 76) and EndOfLine with ValidateSet('CRLF', 'CR', 'LF').

For reference, the Microsoft.PowerShell.TextUtility module  @SteveL-MSFT mentioned does appear to have Base64 support, see ConvertBase64Command.cs. It doesn't appear that it was ever published to PowerShellGallery.com though.

Apologies on not getting around to publishing the module.  Was working on a new cmdlet to add to it, got sidetracked by other important things, and then simply forgot about it.  I'll see about getting what I have published as a preview the next few weeks.  There will be a separate repo for it, so we'll carry this conversation over there once it's created.

This work is happening in https://github.com/powershell/textutility and already published to powershellgallery

Think it's very useful, would it become a built-in module?


Group replication improvements

Test name
Status

demand-backup
failed

auto-config
failed

init-deploy
failed

gr-init-deploy
failed

gr-demand-backup
failed

monitoring
failed

semi-sync
failed

config
failed

service-per-pod
failed

scaling
failed

sidecars
failed

one-pod
failed

limits
failed

users
failed

haproxy
failed

version-service
failed

tls-cert-manager
failed

We run 17 out of 17

commit: https://github.com/percona/percona-server-mysql-operator/pull/262/commits/886ba7877ecebfafdc87e667d106c5427acba035
image: perconalab/percona-server-mysql-operator:PR-262-886ba78

Test name
Status

init-deploy
passed

demand-backup
passed

auto-config
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

config
passed

service-per-pod
passed

gr-demand-backup
passed

sidecars
passed

limits
passed

one-pod
passed

version-service
passed

haproxy
passed

tls-cert-manager
passed

scaling
passed

users
passed

We run 17 out of 17

commit: https://github.com/percona/percona-server-mysql-operator/pull/262/commits/34ee76156c36947e4ffb44d3ecf9976e51e57fb6
image: perconalab/percona-server-mysql-operator:PR-262-34ee761

Test name
Status

auto-config
passed

demand-backup
passed

init-deploy
passed

gr-init-deploy
passed

monitoring
passed

semi-sync
passed

service-per-pod
passed

config
passed

sidecars
passed

one-pod
passed

limits
passed

haproxy
passed

version-service
passed

gr-demand-backup
passed

tls-cert-manager
passed

scaling
passed

users
passed

We run 17 out of 17

commit: https://github.com/percona/percona-server-mysql-operator/pull/262/commits/7e2b392e3d267cd9c3c9ab4be0662a47ed366916
image: perconalab/percona-server-mysql-operator:PR-262-7e2b392


unable to run a pod with two spin apps side-by-side

I was trying out a scenario where two spin apps are running side-by-side in a pod. it seems to fail to start with address <IP_ADDRESS>:80 is already used error
pre-requisite: runtime and shim configured. I used following commands:
setting up the cluster
k3d cluster create wasm-cluster    \
       --image ghcr.io/spinkube/containerd-shim-spin/k3d:v0.13.1  \
       --port  "8081:80@loadbalancer" \
       --agents 2

kubectl apply -f https://github.com/spinkube/spin-operator/releases/download/v0.1.0/spin-operator.crds.yaml
kubectl apply -f https://github.com/spinkube/spin-operator/releases/download/v0.1.0/spin-operator.runtime-class.yaml
kubectl apply -f https://github.com/spinkube/spin-operator/releases/download/v0.1.0/spin-operator.shim-executor.yaml

apply the workload with multiple spin apps
kubectl apply -f - <<EOF
apiVersion: apps/v1
kind: Deployment
metadata:
  name: spin-test-multi-container
spec:
  replicas: 1
  selector:
    matchLabels:
      app: spin-test
  template:
    metadata:
      labels:
        app: spin-test
    spec:
      runtimeClassName: wasmtime-spin-v2
      containers:
      - name: spin-test
        image: rajatjindal/http-rust-cooler:v1
        command: ["/"]
        ports:
        - containerPort: 80
      - name: spin-test-service
        image: ghcr.io/spinkube/containerd-shim-spin/examples/spin-rust-hello:v0.13.0
        command: ["/"]
        ports:
        - containerPort: 8080
EOF

Error from containerd logs:
time="2024-03-27T08:09:37.929901245Z" level=error msg="ERROR >>> Trigger executor failed: Unable to listen on <IP_ADDRESS>:80

Caused by:
    Address in use (os error 98)"

It is probably happening because the spin-addr is hardcoded to <IP_ADDRESS>:80 in the shim.

if we add args to the pod spec, I verified they show up as args in shim.
time="2024-03-27T15:28:59.884400276Z" level=info msg="setting up wasi ["/", "--listen", "<IP_ADDRESS>:8080"]"

The next question is how to parse those args. Also depending on the trigger type, the arguments can be different.
one way we could do is to have trigger-specific parser of args. need to check how we can do that (even better if we can reuse some of that code from spin here).

It is probably happening because the spin-addr is hardcoded to <IP_ADDRESS>:80 in the shim.

this makes sense: https://github.com/spinkube/containerd-shim-spin/blob/34e35ed84a14ac6948e395aa739dada57cafe75b/containerd-shim-spin/src/engine.rs#L27
Does the spin toml file have a way to configure this?

Does the spin toml file have a way to configure this?

I was thinking about this, need to check with team. But also I was thinking we need to be able to change this port in the pod-spec, and if I understand correctly, spin.toml is pushed as part of the OCI artifact.
may be we can use runtime config for this? need to check this as well.

The next question is how to parse those args.

runwasi provides the args via the RuntimeContext: https://github.com/containerd/runwasi/blob/f7ef51e3f7a909b730b9f7954de77cd8ec42ef3b/crates/containerd-shim-wasm/src/container/context.rs#L14

I was thinking about this, need to check with team. But also I was thinking we need to be able to change this port in the pod-spec, and if I understand correctly, spin.toml is pushed as part of the OCI artifact.
may be we can use runtime config for this? need to check this as well.

Alot of times this port and address are configured via ENV variables, that might be the way to handle it here with a default in the  spin toml/runtimeconfig?

Alot of times this port and address are configured via ENV variables

that is a good one. there is indeed an env variable, but need to check how that works without clap parsing here.

I can take a look at this issue

Sorry being distracted away by all the other stuff. Using env vars is a sounding solution which I would still love to explore.

just thinking out here. could we introduce an environment variable such as SPIN_LISTEN_ADDRESS, which overrides the default value?

I am not sure https://github.com/fermyon/spin/pull/2547 is needed to enable setting the listen addr in the shim, since regardless we need to pass the spin_trigger_http::CliArgs object.
We could add the following to the shim without any changes to Spin:
https://github.com/spinkube/containerd-shim-spin/compare/main...kate-goldenring:containerd-shim-spin:configure-listen-address?expand=1

Hi @kate-goldenring, that is right. I wanted to add the flag to spin so that we can be consistent in both spin and shim here.
I have also been exploring ways to allow passing arguments via pod configuration, and would love to pair on that with you. I have some basic idea of how it would work, but will be great to hear what others think about that approach.

I was trying this out today, and realized that while it may be straightforward from shim perspective, but we also need a way to configure this on spinapp crd. This is required so that spin-operator can configure deployment and pod accordingly.

@rajatjindal I put together some thoughts around configuration in a SKIP: https://github.com/spinkube/skips/pull/4. I'd love to hear your thoughts.


Content-Type not supported

Hi there,
I have same requirements as described in:-
https://github.com/danialfarid/angular-file-upload/issues/88
Using version 2.1.1
Code is pretty simple, as follows.
In my html I have:-
<script src="/js/angular-file-upload/angular-file-upload-shim.js"></script>
<script src="/js/angular-file-upload/angular-file-upload.js"></script>

<input type="file" ng-file-select ng-file-change="onFileSelect($files, $event)" />
<button class="btn" ng-click="flip()">Flip</button>

In my backend controller, I have:-
$scope.onFileSelect = function($files, $event) {
	$scope.file = $files[0];
};

$scope.flip = function() {
	$upload.http({
		    url: '/image-flip',
		    headers: {'Content-Type': $scope.file.type},
		    file: $scope.file
	}).progress(function(evt) {
		console.log('progress: ' + parseInt(100.0 * evt.loaded / evt.total) + '% file :'+ evt.config.file.name);
	}).success(function(data) {
		console.log('file ' + config.file.name + 'is uploaded successfully. Response: ' + data)
	}).error(function(data) {
	       //error
	});
};

When I execute the code the request is sent with Content-Type: application/json which is obviously wrong - should be image/jpeg - and is therefore rejected by the server which is expecting image/jpeg.
There is clearly something obvious that I am missing here but I can't spot what it is.  I did try debugging through the code but always end up in the angular code that strips content-type header before sending each request.
Any help, gratefully appreciated.

Your code should look like this: https://github.com/danialfarid/angular-file-upload/issues/88#issuecomment-31366487
The second code seems correct. Have a look at the demo page and at the bottom select the second option then click on edit js and see how it's been done and working there.

Also tried:-
   fileReader.readAsArrayBuffer($scope.file);

This does appear to send binary data but it isnt recognized by the server so something still isnt quite right here.  Beginning to think this isn't angular-file-upload.  Will continue to investigate.

The demo page is your best help, you can even edit the javascript and change the url to upload to your server if your server supports cors.

Thanks Danial.  I've been looking at that and retrying my example...I will try running your demo page against my server (if poss).  However, in the meantime I have a little more info...if I use XMLHttpRequest directly; i.e.:-
	var fileReader = new FileReader();
	fileReader.onload = function(e) {
	        var data = e.target.result;
	        var ajax = new XMLHttpRequest();
	        ajax.open("POST", "/transformations/image-flip");
		ajax.setRequestHeader('Accept', 'image/jpeg');
		ajax.setRequestHeader('Content-Type', $scope.file.type);
		ajax.send(data);
	}
        fileReader.readAsArrayBuffer($scope.file);

The binary data is sent to the server fine and returns the expected response.
Perhaps something might have changed in angular's $http?  I am using 1.3.8

Well the demo page is working with angular 1.3.6 and selecting the second option for upload, so if you follow the code in the demo page you should be able to figure out what you are doing differently.

Hi Daniel,
OK.  I spent a couple of hours chasing this down.  I think I have narrowed it down.  Long story short.  If I use the version of angular-file-upload.js that your demo site is currently using then my code also works.  If, however, I use verison 2.1.1 that you released a couple of days back, it fails - for me anyway.  The behavior I get with 2.1.1 is that the request payload is empty.
I did try and diff the site version and 2.1.1 but there is a big delta and it was pretty much impossible for me to spot anything obvious I am afraid.

I just deployed the latest code of the demo page again and it still works. There shouldn't be any diff between the js codes. What files are you comparing?

Nevermind.  I had modified your code (based on something mentioned in issue 88) and had reverted that chnage.  My bad.  Having reverted that it's working fine.  Many thanks.  I will close.


uninitialized constant Homebrew::Service

/usr/local/Homebrew/Library/Homebrew/formula.rb:1267:in service' /usr/local/Homebrew/Library/Homebrew/formula.rb:1238:in plist_name'
/usr/local/Homebrew/Library/Homebrew/formula.rb:1250:in launchd_service_path' /usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/lib/service/formula_wrapper.rb:58:in service_file'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/lib/service/formula_wrapper.rb:92:in plist?' /usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/lib/service/formulae.rb:14:in block in available_services'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/lib/service/formulae.rb:14:in select' /usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/lib/service/formulae.rb:14:in available_services'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/lib/service/formulae.rb:25:in services_list' /usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/lib/service/commands/list.rb:13:in run'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/cmd/services.rb:129:in services' /usr/local/Homebrew/Library/Homebrew/brew.rb:97:in public_send'
/usr/local/Homebrew/Library/Homebrew/brew.rb:97:in `'

brew update


build/ocp: sanitize and add in some status

Removed some cruft, changed some things to seem more sane (like using
params.VAR instead of manually converting env.VAR).
Also added updates to job information to make it easier to see at a
glance what happened with a particular build in the list of builds.

@adammhaile @tbielawa

/lgtm


the page of  container stats is "ugly"

the page of  container stats is "ugly" so that it can not provide useful information

This view will be entirely rewritten soon, follow the evolution here: https://github.com/portainer/portainer/issues/297


TypeError: Cannot assign to read only property 'jsx' of object '#'

Describe the bug
When creating a react-typescript app using
npx create-react-app . --template typescript
The error:
yarn run v1.22.5
$ react-scripts start
/home/aditya/all/yt/twitter/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js:239
      appTsConfig.compilerOptions[option] = value;
                                          ^

TypeError: Cannot assign to read only property 'jsx' of object '#<Object>'
    at verifyTypeScriptSetup (/home/aditya/all/yt/twitter/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js:239:43)
    at Object.<anonymous> (/home/aditya/all/yt/twitter/node_modules/react-scripts/scripts/start.js:31:1)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I have this happening after upgrading to typescript 4.1

Duplicate with https://github.com/facebook/create-react-app/issues/9868

Same issue I am facing. Just ran the npx create-react-app my-app --template typescript command.
When I run it using yarn start, I get this error.

+1
Me too.

Duplicate of #9868

Definitely, a Duplicate of #9868 but also can confirm getting an issue:  -
TypeError: Cannot assign to read only property 'jsx' of object '#<Object>'
    at verifyTypeScriptSetup (/Users/Nathan/Projects/pwa/pwa-react/pwa-react/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js:239:43)
    at Object.<anonymous> (/Users/Nathan/Projects/pwa/pwa-react/pwa-react/node_modules/react-scripts/scripts/start.js:31:1)
    at Module._compile (internal/modules/cjs/loader.js:1156:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
    at Module.load (internal/modules/cjs/loader.js:1000:32)
    at Function.Module._load (internal/modules/cjs/loader.js:899:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)
    at internal/main/run_main_module.js:18:47
error Command failed with exit code 1.

+1 seeing this as well

+1 Now i can't create new typescript anymore !!!

You can fix this issue for the time being by downgrading to Typescript 4.0.5. It is an issue with Typescript 4.1+ being present with CRA 4.0 and may be fixed once CRA 4.0.1 is released.

I've just had this exact error, the problem is increate-react-app\packages\react-scripts\scripts\utils\verifyTypeScriptSetup.js on Line 151 (to find it search for ts.JsxEmit.ReactJ) it was using ts.JsxEmit.ReactJsx but should use ts.JsxEmit.ReactJSX (JSX being upper case)
Thanks to @benneq this is fixed in the master branch (already three weeks ago), just needs a new patch version.
Can somebody release a 4.0.1?

You can fix this issue for the time being by downgrading to Typescript 4.0.5. It is an issue with Typescript 4.1+ being present with CRA 4.0 and may be fixed once CRA 4.0.1 is released.

I tried that. Downgraded to TS 4.0.5 and replace "react-jsx" with "react" in the tsconfig.json jsx field.
But nothing seems to solve this.

please solve this . i have this error too.

I've just had this exact error, the problem is app\node-modules\react-scripts\scripts\utils\verifyTypeScriptSetup.js on Line 150.  I changed hasJsxRuntime && semver.gte(ts.version, '4.1.0-beta') to !hasJsxRuntime && !semver.gte(ts.version, '4.1.0-beta')

Your milage may vary. Personally, I solved it by:
-changing the typescript version in package.json to "~4.0.5"
-changing the value "jsx" in compilerOptions inside tsconfig.json to "react" instead of "react-jsx"
-run npm install so that the older typescript version is installed
-make sure vscode has the intellisense version of ts set correctly Mine is set to use the vscode built-in version 4.0.3
-I was then able to start the project normally with npm start

I just deleted tsconfig.json and ran yarn start, and it recreates it and runs (I did update to ts 4.0.5 too).  But you have to delete everytime you run yarn start.  i.e
rm tsconfig.json && yarn start
Hacky until we get a fix.

I just deleted tsconfig.json and ran yarn start, and it recreates it and runs (I did update to ts 4.0.5 too). But you have to delete everytime you run yarn start. i.e
rm tsconfig.json && yarn start
Hacky until we get a fix.

And the file is actually identical

For anyone also seeing this error.. it is already known, and a fix has been merged to master.
What we are waiting for now is a React-Scripts v4.0.1 patch on npm... no word yet on when that's happening.

I just deleted tsconfig.json and ran yarn start, and it recreates it and runs (I did update to ts 4.0.5 too). But you have to delete everytime you run yarn start. i.e
rm tsconfig.json && yarn start
Hacky until we get a fix.

Yooo. Thanks

You could also comment out the line 239 in verifyTypeScriptSetup.js
if you do not want to remove your
Tsconfig file.
To find this file. You must go to node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js

You could also comment out the line 239 in verifyTypeScriptSetup.js
if you do not want to remove your
Tsconfig file.
To find this file. You must go to node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js

This is not a solution in any kind of production environment that uses a VCS that ignores the node_modules directory.

Solution

A quick solution as mentioned above
yarn add<EMAIL_ADDRESS>rm tsconfig.json
yarn start

You could also comment out the line 239 in verifyTypeScriptSetup.js
if you do not want to remove your
Tsconfig file.
To find this file.   For a quick fix. so you do not have to delete your tsconfig file
If you navigate to node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js  and head to line 239 where it says appTsConfig.compilerOptions[option] = value
You could delete it or comment it. this is a temporary fix until they push another update for react-scripts.

Workaround for those who want to use TypeScript 4.1 and create-react-app 4.0.0: set the environment variable DISABLE_NEW_JSX_TRANSFORM to true to avoid the buggy code in verifyTypeScriptSetup.js until 4.0.1 is released.
The scripts section of my package.json now looks like this:
    "start": "env DISABLE_NEW_JSX_TRANSFORM=true react-scripts start",
    "build": "env DISABLE_NEW_JSX_TRANSFORM=true react-scripts build",
    "test": "env DISABLE_NEW_JSX_TRANSFORM=true react-scripts test",
    "eject": "env DISABLE_NEW_JSX_TRANSFORM=true react-scripts eject"

I solve this issue
"react-scripts": "4.0.0-next.98"
"typescript": "^4.1.2",

yarn start

++

Same issue I am facing. Just ran the npx create-react-app my-app --template typescript command.
When I run it using yarn start, I get this error.

I too : (

"react-scripts": "4.0.0-next.98"

Thank you : )

Modified start script in package.json to this and it works for now.
   "start": "rm tsconfig.json && react-scripts start",

I modified the jsx property in tsconfig.json to "react" instead of "react-jsx" and changed the typescript version in the package.json file. When i ran yarn install , it prompted me to select a typescript version, I chose 4.0.2 and now it runs without any errors!

I just experienced the same issue

Specifying version 4.0.5 fixed this for me.

Solution
Change typescript version in package.json
 "typescript": "~4.0.5",
Change in tsconfig.json
 "jsx": "react"
In the terminal
yarn install
yarn start

it doesn't work

Personally, I was able to fix this issue (this is on a fresh project) by:
-changing the typescript version in package.json to "~4.0.5"
-changing the value "jsx" in compilerOptions inside tsconfig.json to "react" instead of "react-jsx"
-run npm install so that the older typescript version is installed
-I don't think this is needed but perhaps make sure vscode has the intellisense of ts set to the same or similar version to the one you've installed Mine is set to use the local one I just installed - 4.0.5
-I was then able to start the project normally with npm start

worked fine .

works for me with
{
    "react-scripts": "^4.0.1",
    "typescript": "^4.1.2",
}

This issue is fixed now. No error with latest versions of react-scripts and typescript.

works for me with
{
    "react-scripts": "^4.0.1",
    "typescript": "^4.1.2",
}

Worked for me too - but when I run "npm run start"again, tsconfig.json keeps changing jsx from "react" to "react-jsx" which causes errors in my tsx files. Is there something else I need to change? Is this unrelated?

I also find the bug,and I use 'react' to replace 'react-jsx' after run 'npm start' by myself...
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年11月24日(星期二) 凌晨5:46
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [facebook/create-react-app] TypeError: Cannot assign to read only property 'jsx' of object '#<Object>' (#10110)
works for me with
{     "react-scripts": "^4.0.1",     "typescript": "^4.1.2", }
Worked for me too - but when I run "npm run start"again, tsconfig.json keeps changing jsx from "react" to "react-jsx" which causes errors in my tsx files. Is there something else I need to change? Is this unrelated?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

works for me with
{
    "react-scripts": "^4.0.1",
    "typescript": "^4.1.2",
}

Worked for me too - but when I run "npm run start"again, tsconfig.json keeps changing jsx from "react" to "react-jsx" which causes errors in my tsx files. Is there something else I need to change? Is this unrelated?

Update the typescript version of your IDE.

This seems to have resurfaced in 4.0.1. appTsConfig is assigned to readTsConfig (which is a frozen object), so the following errors out.
https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/scripts/utils/verifyTypeScriptSetup.js#L222-#L228

@student020341

causes errors in my tsx files

react-jsx is correct.
Can you build your app and errors are only at your IDE? As @maltoze said, set your IDE to use the typescript version from the app node_modules folder.
I wrote a short blog post on how to do it for IntelliJ IDE.

Yes,it works,I can run my app normaly...
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年11月24日(星期二) 下午4:49
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [facebook/create-react-app] TypeError: Cannot assign to read only property 'jsx' of object '#<Object>' (#10110)
@student020341
causes errors in my tsx files
react-jsx is correct.
Can you build your app and errors are only at your IDE? As @maltoze said, set your IDE to use the typescript version from the app node_modules folder.
I wrote a short blog post on how to do it for IntelliJ IDE.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Worked for me

Set Typescript of editor to use workspace version

ctrl | cmd + shift + p and type "Typescript" - select typescript version uses workspace

Upgrade react-scripts to latest

npm upgrade react-scripts@latest || yarn upgrade react-scripts@latest
will go to version 4.0.1

Upgrade typescript to latest (same command of above but targeted typescript package)
Set "jsx" to "react-jsx" in tsconfig.json

I hope this helps.

works for me with
{
    "react-scripts": "^4.0.1",
    "typescript": "^4.1.2",
}

Worked for me too - but when I run "npm run start"again, tsconfig.json keeps changing jsx from "react" to "react-jsx" which causes errors in my tsx files. Is there something else I need to change? Is this unrelated?

Have updated my initial post (see above)

You can add DISABLE_NEW_JSX_TRANSFORM=true to .env file. This way it'll stop replacing react with react-jsx

@maltoze
@madrus
@gynekolog
Thanks! I changed the typescript version vs code was using and that seems to have resolved the issue. It's still react-jsx, but now it works. Everything set to 4.1.x now.

Can anyone confirm if 4.0.1 resolves this issue? We did patch up some of the issues when modifying the tsconfig.

All the solution above doesn't work for me after downgrading typescript today.

Can anyone confirm if 4.0.1 resolves this issue? We did patch up some of the issues when modifying the tsconfig.

@ianschmitz after i did these steps mentioned here did worked fine

Worked for me

Set Typescript of editor to use workspace version

ctrl | cmd + shift + p and type "Typescript" - select typescript version uses workspace

Upgrade react-scripts to latest

npm upgrade react-scripts@latest || yarn upgrade react-scripts@latest
will go to version 4.0.1

Upgrade typescript to latest (same command of above but targeted typescript package)
Set "jsx" to "react-jsx" in tsconfig.json

I hope this helps.

I just  use default tsconfig.json .

@Luan-Sens @ianschmitz after upgrading to 4.0.1 I personally am not seeing this issue anymore.

I see this issue with my version of TypeScript at 4.0.3 @ianschmitz

It seems like its fixed now with TS 4.0.3 as well

Ran into this issue as well on 4.0.0 with TS 4.1.3, updating to 4.0.1 resolved it.

Ran into this issue as well on 4.0.0 with TS 4.1.3, updating to 4.0.1 resolved it.

Just One thing:
npm install<EMAIL_ADDRESS>&
Restart the server

Just One thing:
npm install<EMAIL_ADDRESS>&
Restart the server

update cra to 4.0.1 or set ts version to "~4.0.5"

update cra to 4.0.1 or set ts version to "~4.0.5"

Personally, I was able to fix this issue (this is on a fresh project) by:
-changing the typescript version in package.json to "~4.0.5"
-changing the value "jsx" in compilerOptions inside tsconfig.json to "react" instead of "react-jsx"
-run npm install so that the older typescript version is installed
-I don't think this is needed but perhaps make sure vscode has the intellisense of ts set to the same or similar version to the one you've installed Mine is set to use the local one I just installed - 4.0.5
-I was then able to start the project normally with npm start

Worked for me. Jan 28th 2020 for existing create-react-app app from 3 months ago.  I tried just changing react-jsx to react but that was not enough. YOu have to change the version too.  Make sure you use ~4.0.5 and not ^4.0.5 as only the former works!

Personally, I was able to fix this issue (this is on a fresh project) by:
-changing the typescript version in package.json to "~4.0.5"
-changing the value "jsx" in compilerOptions inside tsconfig.json to "react" instead of "react-jsx"
-run npm install so that the older typescript version is installed
-I don't think this is needed but perhaps make sure vscode has the intellisense of ts set to the same or similar version to the one you've installed Mine is set to use the local one I just installed - 4.0.5
-I was then able to start the project normally with npm start

Worked for me. Jan 28th 2020 for existing create-react-app app from 3 months ago.  I tried just changing react-jsx to react but that was not enough. YOu have to change the version too.  Make sure you use ~4.0.5 and not ^4.0.5 as only the former works!

A quick solution as mentioned above 👍
yarn add<EMAIL_ADDRESS>rm tsconfig.json
yarn start

It was the rm tsconfig.json that worked for me 🚀 just delete the file then run yarn start again to have tsconfig.json auto-recreated for you.

For me changing "react-scripts" version in package.json from "4.0.0" to "4.0.1" and running npm i fixed the error.

Workaround for those who want to use TypeScript 4.1 and create-react-app 4.0.0: set the environment variable DISABLE_NEW_JSX_TRANSFORM to true to avoid the buggy code in verifyTypeScriptSetup.js until 4.0.1 is released.
Also, "jsx" must be set to "react" in tsconfig.json
The scripts section of my package.json now looks like this:
    "start": "env DISABLE_NEW_JSX_TRANSFORM=true react-scripts start",
    "build": "env DISABLE_NEW_JSX_TRANSFORM=true react-scripts build",
    "test": "env DISABLE_NEW_JSX_TRANSFORM=true react-scripts test",
    "eject": "env DISABLE_NEW_JSX_TRANSFORM=true react-scripts eject"

This solved it for me. thanks

I just deleted tsconfig.json and ran yarn start, and it recreates it and runs (I did update to ts 4.0.5 too). But you have to delete everytime you run yarn start. i.e
rm tsconfig.json && yarn start
Hacky until we get a fix.

Thanks for your methods!but it seems that every time I start the project, I need to delete tsconfig.json again and then yarn start.Moreover,for projects created using RCA, the value of "jsx" in tsconfig.json is "react", but the value of "jsx" in tsconfig.json newly created using yarn start is "react-jsx" ,why?is there any explanation?

I solve this error updating react-scripts to 4.0.3
yarn upgrade<EMAIL_ADDRESS>

Solution
Change typescript version in package.json  "typescript": "~4.0.5",
Change in tsconfig.json  "jsx": "react"
In the terminal
yarn install
yarn start

删除 tsconfig.json 文件，重新运行 npm start 项目能临时起来


All dataset download addresses are invalid

All the download addresses for the datasets you provided are invalid. Could you please provide me with new download addresses for these datasets? thank you very much indeed!

do u solve this problem?

i want the cub_200 pre_trained model.but the link involved is invalid.Could you please update the link ?


Optional input to Voronoi allowing tight control

Substance Designer has a "Distance" node that takes an image (and I think) analyses it to find mean points of possible islands, and then uses these points to draw a Voronoi Diagram.
It's like Worley Noise, only the user can have precise control over how it's going to be done. The benefit of that is, it can be used to generate roads on a world texture, controlling the road density - make more roads in towns, no roads underwater and no roads on the mountains.
Of course output of such an operation would need to be processed to find edges, distort and dialate it before using as a mask.
I've been searching the newest version of Material Maker because I thought something like this existed, but I couldn't find the node to do it. Voronoi doesn't have an optional input. And an optional input that could define the point locations would be excellent here.

I think the Node you're looking for is named Dilate.

Yes!
I have a problem with it though.. Despite being configured to fill the islands with color, there's a bit of a color change resulting in these concentric rays being added to the resulting edge-detection:

I've noticed that changing the size of the circles I used definitely has a huge impact:

I wonder what should I do for a perfectly clean output (no godrays in the islands basically)...
It seems the issue is that Dialate doesn't output "just the color" when the 3rd parameter is set to 1 (as I thought it will)- it overlays that somewhat on the incoming images, or IDK - the image is not flat:

I've tried to correct that using the Quantize node, but then some of my "roads" lead to nowhere:

With making the input circle smaller and softening it up and using QUantize I was able to get this result:

Though some "roads" don't seem like making much sense still - this is not exactly like a Voronoi diagram, as the necessary Quantize operation removes some of the edges.

I was able to get some better results, though it's finnicky:

If I could have a shape node that produces an exactly 1 x 1 px large white dot so I can spray that - this'd solve the problem.

Hmm maybe inserting a Buffer node in front of the Dilate would help.
BTW you may want to join our new Discord server. ;)

What would the buffer improve here? Doesn't it just cache results to speed up processing?


Update mount instructions on docker hub

The documentation on https://hub.docker.com/r/dashpay/dashd is suggesting to mount a volume to /dash, which is not correct since v18.1. Instead the volume should be mounted to /home/dash.
Change
 docker volume create --name=dashd-data  docker run -v dashd-data:/dash --name=dashd-node -d \      -p 9999:9999 \      -p <IP_ADDRESS>:9998:9998 \      dashpay/dashd
to
 docker volume create --name=dashd-data  docker run -v dashd-data:/home/dash --name=dashd-node -d \      -p 9999:9999 \      -p <IP_ADDRESS>:9998:9998 \      dashpay/dashd
This change was introduced by this commit: https://github.com/dashpay/dash/commit/6699b0228f9fd5885ebe60d2e33e4f678ed77c18

Can you make a PR for this?

Can you make a PR for this?

The repository (https://github.com/dashpay/docker-dashd) is archived so no I can not.

Ah, but the docker files live now here https://github.com/dashpay/dash/tree/master/contrib/containers

Right, but the image description is not fetched from there. So I guess the owner of the docker hub account has to change it directly.

Anybody knows who is that? @kwvg @PastaPastaPasta @strophy

Thanks, the docker image page is indeed correct now

Or is it the functionality that is offered for free isn't sufficient for what you talk about?


HEIC Apple Photo Support

Hello, I noticed that I cannot upload any images from iOS / iPhone.  I guess this is a super popular format, would it be possible to gain support, or any workaround I can use to add it myself?

Thanks for letting me know, I'll look into that

I just tested it myself and it worked fine. I clicked 'Select Upload' then I was able to choose between my Camera Roll etc. Can you explain the flow when it doesn't work for you?

Oh I just used your demo site and I could not even choose an heic file.
Apologies I forgot to mention that
On Thu, 16 Apr 2020, 18:05 mayeaux<EMAIL_ADDRESS>wrote:

I just tested it myself and it worked fine. I clicked 'Select Upload' then
I was able to choose between my Camera Roll etc. Can you explain the flow
when it doesn't work for you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mayeaux/nodetube/issues/242#issuecomment-614744856,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKS7W4LV3ECECRPRFSMQ5DRM4UFDANCNFSM4MJTO5QA
.

How can I test this? When I (using iOS 12 so it should be using HEIC), go and try an upload all my photos show up. You're saying that when you hit Select File no images show up, or what do you see on your end? Thanks

Here is what I did, from this page:
https://github.com/mayeaux/nodetube
Is linked your demo site: https://newtube.app
From there, created account and pressed "Upload" to test how it works.
In there it says this:
Supported File Formats
Video: .mp4, .avi, .flv, .MOV, .m4v, .ogv, .webm, .wmv, .mkv, .mov, .m2t, .MTS, .m2ts, .MPG, .AVI, .mpg
Audio: .mp3, .wav, .ogg, .m4a
Image .png, .jpg, .jpeg, .gif, .JPG, .PNG

But I try anyway to upload HEIC file.
And I CAN select it, and start the upload, but after it starts, I finally get this:

The issue is that browsers can't display .heic files, so there would have to be some serverside conversion but there's not really any good tools for that that I can find. If you want to dig into this a little bit more I'm happy to hear your suggestions.

Imagemagick supports for a long time now.
https://imagemagick.org/script/formats.php

The issue is that we would be adding a dependency for such a small feature (I had never heard of or used .heic before). If someone wanted to make a PR for it though I would accept it provided that it was supported as a flag so someone could run the app full fledged without having to install Imagemagick. I want to try and support as many file formats as possible but at the same time I want to make the installation process as simple as possible and adding a whole installation step to support .heic files isn't worth the tradeoff at the moment, though like I said if it was optionally made available through the .env.settings file I would support a PR for that.

Ok. I'll look at it. Which image processor do you currently use for still
image manipulation?
On Fri, 17 Apr 2020, 17:22 mayeaux<EMAIL_ADDRESS>wrote:

The issue is that we would be adding a dependency for such a small feature
(I had never heard of or used .heic before). If someone wanted to make a PR
for it though I would accept it provided that it was supported as a flag so
someone could run the app full fledged without having to install
Imagemagick. I want to try and support as many file formats as possible but
at the same time I want to make the installation process as simple as
possible and adding a whole installation step to support .heic files isn't
worth the tradeoff at the moment, though like I said if it was optionally
made available through the .env.settings file I would support a PR for that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mayeaux/nodetube/issues/242#issuecomment-615306049,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKS7W774FSWOTMUUATI2LTRNBX47ANCNFSM4MJTO5QA
.

None! Browsers are really good at handling images so we don't do any post-processing of images at the moment. Though probably in the future this should be changed so that images have thumbnails so less bandwidth is used when displaying them as thumbnails. I just made a ticket for that: https://github.com/mayeaux/nodetube/issues/244
I'm still a little iffy on introducing another installation step for such a small use case but as long as it was put behind a flag it would be fine.


refactor: Add settings and plugins attributes to Project

These changes seem to simplify quite a few things, and also decreased the amount of time it takes to run the tests by approximately 40%, which suggests that these changes improves Meltano's performance.
In a nutshell, since the project instance had to be passed around everywhere, and because of Project.find caching it was basically a singleton, now we make use of it by doing stuff like project.settings instead of ProjectSettingsService(project). This saves us from repeatedly instantiating many "service" classes over and over again (hundreds of times per executions in some cases), which was rather slow. We do need to re-instantiate them to reflect changes to the outside world (e.g. changes to env vars, changes to config files, etc.), so a refresh method has been added to Project which causes it to replace itself with a fresh instance, keeping the same object so that any existing references to it get the new "service" instances it carries.
I've also removed several unused params that would allow us to provide pre-instantiated  "service" classes. Each such param multiplies the complexity of the object because it provides a whole new set of behaviors, almost none of which were tested. If one really needs to pass in a class with one of these parameters, we can add it back in later. Until then, I think it should be removed. You aren't gonna need it.

@WillDaSilva Giving a tentative 👍 on the overall approach, pending a more thorough review in the next couple days. I think it makes sense and reduces a lot of unnecessary complexity.

@WillDaSilva this is epic 🙌 I've had a look through and overall this is a huge improvement. Kudos! The .refresh() change strikes me as the only minor risk to users - I wonder if our constant refreshing of the settings service might have masked issues with read-write consistency in async or parallel use cases, or in tools/scripts that wrap Meltano (ala Visch). However, as a potential side-effect rather than a feature, I still think it a significant improvement to be more deliberate about when refresh() happens. We should just keep an eye out for potential integration issues in Slack 👍

This PR should not be merged until https://github.com/meltano/meltano/pull/7294 has been merged, since we'll want to release Meltano 2.15.4 with the changes from https://github.com/meltano/meltano/pull/7294, and including these changes in that release would be a risk.


DAC6-1819: Add mandatory-disclosure-rules accessibility statement

Could you please add metadata values for businessArea and typeOfService as described at the end of this section in the readme? https://github.com/hmrc/accessibility-statement-frontend#how-to-add-your-services-accessibility-statement

@kitation I've added it now. I've also added it for register-for-mdr.yml because it was missed from there in an earlier PR as well.


Priority bug for WORST value

I got an email with:
I think there may be a bug in the priority weighting (we’ve copied the motorcycle flag encoder) as if the GetDouble method uses the UNCHANGED value if the priority weighting returns zero which is also the weighting value for WORST.  This would mean that WORST roadtypes are treated the same as UNCHANGED.

The problem is that WORST is 0 which is also used for UNCHANGED in the special clause if ret == 0 then return UNCHANGED. Instead we should think about using negative values for bad priorities and still keep the order of the priorities. Then the following test should run through:
@Test public void testUnchangedVersusWorstPriority_issue399()
{
    OSMWay way = new OSMWay(1);
    way.setTag("highway", "tertiary");
    long encoded = encoder.acceptWay(way);
    long flags = encoder.handleWayTags(way, encoded, 0);

    assertEquals(UNCHANGED.getValue(), encoder.getLong(flags, PriorityWeighting.KEY));
    assertEquals((double) UNCHANGED.getValue() / BEST.getValue(), encoder.getDouble(flags, PriorityWeighting.KEY), .1);

    MotorcycleFlagEncoder motorEncoder = new MotorcycleFlagEncoder(5, 5, 0)
    {
        @Override
        protected int calcPriority( OSMWay way, long relationFlags )
        {
            return PriorityCode.WORST.getValue();
        }
    };
    new EncodingManager(motorEncoder);

    encoded = motorEncoder.acceptWay(way);
    flags = motorEncoder.handleWayTags(way, encoded, 0);
    assertEquals(WORST.getValue(), motorEncoder.getLong(flags, PriorityWeighting.KEY));
    assertEquals((double) WORST.getValue() / BEST.getValue(), motorEncoder.getDouble(flags, PriorityWeighting.KEY), .1);
}

Why not just remove the value WORST from the PriorityCode enum ?
This brings the benefit that priority changing upwards and downwards is symmetrical. It is unlogical that there should be 4 values for decreasing the priority down and only 3 values for boosting up.

Yes, just removing WORST is also listed as possibility here, not sure. For 3 bits we have 8 possibilities and we should use them

Will remove WORST for now as a workaround, still letting this open and postponing.

Ok, using now a simple solution: always writing a value - i.e. we do not need a default to retrieve if 'empty'

The change 29dc23a looks a bit strange to me - these two Priority enums have now the same value 7. Is this per intention? I don't think so:
    VERY_NICE(7),     BEST(7);
A lots of tests fail and I doubt that they only fail for me.

Yes, currently fixing it ...

But the problematic change was not introduced here nor in 29dc23a ... see https://github.com/graphhopper/graphhopper/pull/476#issuecomment-129911374


Cannot connect to identity over Proxy server

Hi,
This is more of a question and much less of an issue. I have been trying to connect to Identity Server endpoint using DiscoveryClient and it works all good however when i connect to the same endpoint over any network which uses a Proxy, i get an error which says The remote server returned an error: (407) Proxy Authentication Required. Is there a way i can get around this ?
Many Thanks 👍

You can pass and HttpMessageHandler to the ctor. On that you can configure proxy settings.

@leastprivilege Thanks so very much


SC4S: Can’t recognize netapp:fas

Request for netapp:fas format
Detail: Podman 3.0.1
SC4S: v2.30.0
Index file: netapp_ontap,index,main
Rsyslog recognize the events as “sourcetype = netapp:fas” (refer to netapp_Prod_screen.JPG), but SC4S put into “sourcetype = sc4s:fallback” (refer to netapp_Dev_screen.JPG).
Use below sample echo during the test (Company relevant filtered off)
_echo "2022-06-24T04:08:11+00:00 test_sample.com test_sever: test_sever: 00000016.019e5dc4 1f1457c9 Fri Jun 24 2022 02:59:50 +05:30 [kern_audit:info:1667] 8503e80000839b68 :: test_severa:ontapi :: <IP_ADDRESS>:52905 :: test_severa:bmcpatrol :: perf-object-get-instances :: Success: " > /dev/udp/<IP_ADDRESS>/514
echo "2022-06-24T04:08:18+00:00 test_sample.com test_sever: test_sever: 00000018.02989ce0 1e913313 Fri Jun 24 2022 03:02:15 +05:30 [kern_audit:info:1667] 8503e80000845775 :: test_severb:ontapi :: <IP_ADDRESS>:52798 :: test_severb:.admin.001 :: nfsv4:node1000^M  :: Pending: " > /dev/udp/<IP_ADDRESS>/514_
attached together with
fallback_contain.txt - Contain in the Fallback folder for above test
netapp.zip - pcap for for above test
netapp.zip
fallback_contain.txt

Looking into this.

it will be added to the sprint of enhancement.

@rjha-splunk Any expectation the release day?
What actions could take as interim while wait for release? Any expectation the release day?

we don’t have a date yet, we will review the logs and keep you posted as soon as we will have the release date.

@Jo-Ng are you able to extract the rsyslog filter that sets the correct sourcetype?

@mateuszpierzchala-splunk
I use below command, I do able to see the Pri=13 on the Splunk Portal and the output go direct to fallback.
echo "2022-08-02T05:57:11+00:00 test_sample.com Jotest_sever_1.4: test_sever: 00000016.019e5dc4 1f1457c9 Fri Jun 24 2022 02:59:50 +05:30 [kern_audit:info:1667] 8503e80000839b68 :: test_severa:ontapi :: <IP_ADDRESS>:52905 :: test_severa:bmcpatrol :: perf-object-get-instances :: Success: " > /dev/udp/<IP_ADDRESS>/514
and here the output when I changed the JoTest_Sever_1.x at the SPlunk Portal

Attached the PCAP from echo. due to restriction  I can't upload the actual data into this Open forum. If need I could open case at Splunk Portal where data more protect, please let me know if this work,
1760a_netapp2.zip
I didn't see any other Netapp sourcetype appeared maybe the netapp only send limited info for this test.
We are using Rsyslog version 7.4.10, didn't have any specific filter in place on it beside below:-
[monitor:///apps/rsyslog/int_san_netapp_fas//]
sourcetype = netapp:fas
index = glm_storage
host_segment = 4
disabled = 0
whitelist = ..log$
blacklist = .(gz|tar)$

Hi, @Jo-Ng again thank you for your response. In case you send message that is missing PRI sc4s will add default PRI- the same happens when you send 'test' string, try it yourself (13 equals to a Priority value of 13 is “user-level” Facility and “Notice” Severity take a look at the table for reference.
On the opposite when we add some PRI to the message it is recognized as a syslog compliant message:
echo '<134>2022-08-02T05:57:11+00:00 test_sample.com Jotest_sever_1.4: test_sever: 00000016.019e5dc4 1f1457c9 Fri Jun 24 2022 02:59:50 +05:30 [kern_audit:info:1667] 8503e80000839b68 :: test_severa:ontapi :: <IP_ADDRESS>:52905 :: test_severa:bmcpatrol :: perf-object-get-instances :: Success: ' > /dev/udp/<IP_ADDRESS>/514

There is some issue for sure, I suppose with how filter is parsing the date because it suppose to look like this:

I will look into this filter today and will try to extend it like I mentioned in one of the messages above. I would suggest to push all messages from Ontap family devices into one sourcetype- the one that is already defined. Let me know if that works for you,

Please feel free to copy this file to your /opt/sc4s/local/config/app_parsers/syslog folder and test it.
I tested it with message that you provided with addition of PRI:
echo "<166>2022-08-03T07:54:12+00:00         test_sample.com Jotest_sever_1.4: test_sever: 00000019.0794c163 055b6737 Tue Jul 20 2022 11:45:58 +00:00 [kern_audit:info:2385] 8503ea0000ba6b71 :: nodea:ontapi :: <IP_ADDRESS>:41464 :: nodea-esx:usera :: clone-create :: Error: Missing input: source-path; Missing input: volume" > /dev/udp/xxx.xxx.xxx.xxx/514
and the effect is following:

I merged this change and closing the issue. If you still need some help with custom change you can reach me on slack group or by email (mpierzchaa@splunk.com).
Thank you.


added lastUpdated, adapted to JS Contoller 3.3, adapted log levels

Added a lastUpdated field to each object. This can be used to determine if a device is still online.
Adapted to async setObjectNotExists calls.
Adapted log levels not log everything in production mode.

Thank you!


feat: clean up storybook

Summary
Clean up Storybook.
Checklist:

[x] I have performed a self-review of my code

Can we remove these files as well?
widget/ui/src/components/Tooltip/useEventListener.ts
widget/ui/src/components/Wallet/Content.tsx
widget/ui/src/icons/Gass.tsx
widget/ui/src/types/meta.ts
Also rgb-hex from package.json (I don't know about react.is. is it necessary? )
In addition, I think we should add copy-to-clipboard package to package json.
moreover:
FirstImage                            unknown  src/components/SelectableCategoryList/SelectableCategoryList.styles.ts:16:14
ImageContent                          unknown  src/components/SelectableCategoryList/SelectableCategoryList.styles.ts:9:14
LoadingContainer                      unknown  src/components/SwapListItem/SwapToken.styles.ts:71:14

In most cases, removing marginLeft and adding Divider caused  Ui bugs. The divider is added to the right, not the left.


I get an error when I run comic.py

Download the latest update and try running it in a virtual environment:
I added the instructions for that in the Readme
https://github.com/ogkalu2/comic-translate#installation


UI suggestion/mock-up for checklist feature in utilities

Come up with an awesome looking UI designed in adobe xd or sketch or whichever design tool that you want to use. Keep in mind that whatever colors you use should be like different shades of blue used in the logo of the app. Ofcourse you can have one complementary color as an accent color.
Once you are done simply post your UI design in the comments below as a png file. Keep in mind that we are just asking for mockup right now and not the fully developed layout through xml. So if you want to work on the issue simply comment below. Once you are assigned the issue you can continue to work on the UI mockup

This looks perfect! Will be creating issues for implementing this UI.