FFImageLoading Crashes android app

An error reporting service called HockeyApp is telling us that FFImageLoading is crashing our application. It happens very infrequently and cannot be reliably reproduced. Good luck :)
Heres the trace given by HockeyApp
    System.NullReferenceException: Object reference not set to an instance of an object
    at com.agilx.fanlete.FFImageLoading.Collections.StrongLruCache`2[TKey, TValue].Add (TKey_key__TValue_value__System.Boolean_overwrite.args:1337)
    at com.agilx.fanlete.FFImageLoading.Collections.StrongLruCache`2[TKey, TValue].Add(TKey_key__TValue_value.args:1337)
    at com.agilx.fanlete.FFImageLoading.Cache.ReuseBitmapDrawableCache.DemoteDisplayedEntryToReusePool (FFImageLoading.Drawables.ISelfDisposingBitmapDrawable_value.args:1337)
    at com.agilx.fanlete.FFImageLoading.Cache.ReuseBitmapDrawableCache.OnEntryNoLongerDisplayed (System.Object_sender__System.EventArgs_args.args:1337)
    at com.agilx.fanlete.FFImageLoading.Drawables.SelfDisposingBitmapDrawable.SetIsDisplayed (System.Boolean_isDisplayed.args:1337)
    at com.agilx.fanlete.FFImageLoading.Views.ManagedImageView.UpdateDrawableDisplayedState (Android.Graphics.Drawables.Drawable_drawable__System.Boolean_isDisplayed.args:1337)
    at com.agilx.fanlete.FFImageLoading.Views.ManagedImageView.SetImageResource (System.Int32_resId.args:1337)
    at com.agilx.fanlete.Fanlete.Android.NotificationsActivity.GetView (Fanlete.Poco.Notification_item__System.Int32_position__Android.Views.View_convertView__Android.Views.ViewGroup_parent.args:1337)
    at com.agilx.fanlete.Fanlete.Android.CustomListAdapter`1[T].GetView(System.Int32_position__Android.Views.View_convertView__Android.Views.ViewGroup_parent.args:1337)
    at Android.Widget.BaseAdapter.n_GetView_ILandroid_view_View_Landroid_view_ViewGroup_ (System.IntPtr_jnienv__System.IntPtr_native__this__System.Int32_position__System.IntPtr_native_convertView__System.IntPtr_native_parent.args:1337)

FFImageLoading 2.2.4 seems to be happening on android only.
Even if you can't nail this down perhaps you could add some more aggressive null checking to help mitigate the problem.

Here some output from the application output window in xamarin studio after implementing IMiniLogger and just doing a Debug.WriteLine() inside the error functions.
    Image loading failed: https://s3.amazonaws.com/fanlete/uploads/dee371d0c35a816d22b067d8862b9cfd2db062c8.png System.NullReferenceException: Object reference not set to an instance of an object.
    at FFImageLoading.Collections.StrongLruCache`2[TKey, TValue].Add (TKey key, TValue value, System.Boolean overwrite) [0x000ae] in C:\projects\ffimageloading\source\FFImageLoading.Droid\Collections\StrongLruCache.cs:146
    at FFImageLoading.Collections.StrongLruCache`2[TKey, TValue].Add (TKey key, TValue value) [0x00000] in C:\projects\ffimageloading\source\FFImageLoading.Droid\Collections\StrongLruCache.cs:113
    at FFImageLoading.Cache.ReuseBitmapDrawableCache.Add (System.String key, FFImageLoading.Drawables.ISelfDisposingBitmapDrawable value) [0x0006a] in C:\projects\ffimageloading\source\FFImageLoading.Droid\Cache\ReuseBitmapDrawableCache.cs:352
    at FFImageLoading.Cache.ImageCache.Add (System.String key, FFImageLoading.Work.ImageInformation imageInformation, FFImageLoading.Drawables.ISelfDisposingBitmapDrawable bitmap) [0x00042] in C:\projects\ffimageloading\source\FFImageLoading.Droid\Cache\ImageCache.cs:95

@rusty21 I'm having the exact same issue!! However, it could be an issue with aws because I can't access the image directly! I get access denied error. I'm having IT look at it. Do you get an access denied error when you try to directly go to the aws link in the browser?

Yes I'm sure your issue is your AWS bucket is private. My bucket is public so that is not a problem. Its pretty clear that FFImageLoading is failing when attempting to cache the image in memory but its unclear as to why.

@owlstack you probably need to configure the bucket permissions in AWS to
allow access. @rusty21 is having a diff issue because you can clearly click
https://s3.amazonaws.com/fanlete/uploads/dee371d0c35a816d22b067d8862b9cfd2db062c8.png
and the image loads.
On Thu, Nov 10, 2016 at 2:05 PM, owlstack<EMAIL_ADDRESS>wrote:

@rusty21 https://github.com/rusty21 I'm having the exact same issue!!
However, it could be an issue with aws because I can't access the image
directly! I get access denied error. I'm having IT look at it. Do you get
an access denied error when you try to directly go to the aws link in the
browser?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/luberda-molinet/FFImageLoading/issues/372#issuecomment-259807331,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVIgLB_Q6Gf0TwtKhavGy1Y144QDgkDRks5q84cogaJpZM4KvFdp
.

Yes you're right but I am getting the same null reference exception: Object reference not set to an instance of an object!

@owlstack Is it consistent or intermittent?

It is consistent!

Perhaps you could post your failing url so that @daniel-luberda can have an easy way to generate the exception and hopefully find a fix.

@rusty21 It's happening to a few of them but here's one:
Image loading failed: http://s3.amazonaws.com/www.qa.mobisave.com/images/offers/thumb_MS_SUNBELT-1-20160928170344.png
System.NullReferenceException: Object reference not set to an instance of an object.

@rusty21 you should test the latest pre-release nugets.

@rusty21 I can no longer reproduce the issue. The issue I was getting with access denied is either

The image does not exist or 2) permission issue.

It turned out that the image url in the db did not exist in that location. That's why I was getting that issue. Make sure your images are in the correct location. I can't reproduce right now. I'll let you know if I run into it again.

How do I go about testing the pre-release version?

Search the Xamain.FFimage nugets and check the box that says something like "Include Prerelease"  verbiage is diff on Xam studio and Visual Studio but its def noticable.

@rusty21 It's fixed (new nuget soon). Thanks for a help! :)

I see you've added a bunch of null checks. What behavior is that going to have? Imagine something failed a null check. Will the image still load and just not be cached, or will the image fail to load silently, will FFImageLoading retry the image?

Image will load. Btw: That exception was not caused by adding to cache,  but by removing from cache and passing null as a key.

I see, sound good! Keep up the good work.


Develop 2.0 - support binary input and output

See my proposed spec https://github.com/swagger-api/swagger-spec/issues/50
These changes in swagger-models are a precondition for an implementation in swagger-codegen of the proposed spec update, as detailed in the above mentioned swagger-spec issue #50, to support binary input and output

See also https://github.com/swagger-api/swagger-codegen/pull/868

We still need to make a decision on that issue before merging this PR.

@boazsapir - finally clearing out the PRs (as much as I can). Based on our discussion, I imagine this is no longer relevant (that is, it needs to be modified)?

I agree.
BTW is the new proposal confirmed or are we still waiting for input from more people?

I believe I talked with Tony about it offline, but let me just make sure :)


GH-3984 improve caching of cardinality

GitHub issue resolved: #3984
Briefly describe the changes proposed in this PR:

introduce a private method that sets/gets the cached cardinality for StatementPattern

PR Author Checklist (see the contributor guidelines for more details):

[ ] my pull request is self-contained
[ ] I've added tests for the changes I made
[ ] I've applied code formatting (you can use mvn process-resources to format from the command line)
[ ] I've squashed my commits where necessary
[ ] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

Before

After
Benchmark                    Mode  Cnt  Score   Error  Units
QueryBenchmark.complexQuery  avgt    5  2.673 ± 0.019  ms/op

Not really showing much improvements in these benchmarks.

Before
Benchmark                                           Mode  Cnt     Score     Error  Units
ComplexLargeBenchmark.noPreloadingNonEmptyParallel  avgt    5  2615.114 ± 122.301  ms/op

After
Benchmark                                           Mode  Cnt     Score    Error  Units
ComplexLargeBenchmark.noPreloadingNonEmptyParallel  avgt    5  2530.961 ± 30.894  ms/op

I've moved the cardinality caching into AbstractQueryModelNode together with a new method that says if the caching should be used or not, that method is then overridden in StatementPattern, TripleRef and in BindingSetAssignment. Further more I have reduced the need for the HashMap for tracking cardinalities, so for many queries we can skip creating the HashMap.


Platform specific API KEY

There is a need to include a platform specific apikey parameter due to restrictions on IOS devices, where it is required that the apikey is set to be for the platform at creation.

It uses the google maps https Places API, so it needs a different apikey than de google maps sdk platform restricted.

Would love to see this as well. Just had a prod bug for this exact scenario after locking our API keys down.


Add support for Parallel Tasks (using PowerShell 3.0 Workflows as back-end)

Psake for now based on Powershell 2.0 and does not support parallel tasks at all.
Parallel tasks is very desired feature, making psake really first-class build system.
The only feature in PowerShell that support parallelism is workflows.
Workflows available since PowerShell 3.0.
So there only way I see to support parallel tasks is to migrating to PowerShell 3.0 and using workflows as back-end abstraction for parallel tasks.

I like this idea a lot.

Output could be:
Task A: whatever output
Task B: whatever output

Could really use this can think of many instances that we can use it

Well does someone want to try implementing it so? :wink:

Workflows can be overkill.
Maybe can be achieved with https://github.com/RamblingCookieMonster/Invoke-Parallel

are there any thoughts on how one would build and/or compose parallel tasks? task Default -parallelDepends t1, t2, t3?

i just had a thought about this. without proper testing, i don't believe that the $psake global and anything bolted onto it (e.g. $psake.context) is safe for concurrency. One might need to copy the variable and pass into an invocation of Invoke-Task.
Maybe the easiest thing to do is to created nested calls to Invoke-psake inside of a Start-Job. i added a PR #152 to show what an example might look like at a Task level.

@sweeneyrobb this seems like a sensible approach to me, and fits in with the existing infrastructure.

@gep13 thanks! I'll put together another PR. Thanks for the response.

@gep13 thanks, I think your solution is well enough/
Start-Job\Wait-Job\Receive-Job combination allows to run tasks as parallel.
I close my issue, I think it is already resolved.

@maximpashuk glad to hear that you were able to make progress and thanks for following up by closing the issue.

Correct me if I'm wrong, if you do Start-Job you are losing the imported modules in the current session and the code sample assumes that psake is loaded prior to all that. While usually in the real world you'd have something like:
powershell.exe -Version 2 -NoProfile -ExecutionPolicy unrestricted -Command "& {cls; Import-Module '.\psake\psake.psm1'; invoke-psake .\build.ps1

Yes, you lose a lot using jobs. Take a look here for an alternative approach: https://github.com/RamblingCookieMonster/Invoke-Parallel/issues/15


Atropisomer is detected and given configuration when aryl ring on one side is symmetrical

In the attached MOL file (ext changed to .txt so I can attach it), the bottom aryl ring is symmetrical, but CENTRES gives the connecting bond a configuration of "M" instead of "ns". I tested this both within our system using the CENTRES API and using the JAR provided in the releases downloads.
atrop_achiral.txt

OK done a bit of probing and long term memory recall. I think this is actually due to an omission in the spec. Double bonds are normally "open'ed up" unless they are connected to the root in the digraph (i.e. C[S@H](=O)CC). However if you do this on atropisomers you artificially split ties... so probably you should open up double bond there.

I don't really understand as the two aromatic bonds in the same ring connected to the aryl-aryl single bond should be equivalent to CIP, but my level of expertise in this area is far inferior. If I can help in any way, please just let me know.

So the issue is when you have a double bond in the digraph you normally open it up:
           |   |
-C=C- => - C - C -

This is to handle the alternating single and double bonds, i.e. in aryl's.
You don't do this on the root node due to tetrahedral stereo involving a double bond. Atropisomers are an odd case because you have a double on the root but it should be duplicated since otherwise you break the symmetry.
Very interesting corner case, but think I know the fix just need to find time to play around with it. Thanks again for reporting these.

BTW you can also just paste the molfile into CDK depict and test it there:

Anytime, and thanks for the link. Thank you for this project!

With the updates, all of our tests pass. Thank you.

Thank you for reporting, any other issues let me know. Despite all the effort I still dislike the CIP system as overly complicated/complex.


chore: add more tests

Description

Adding more tests for the SQLite Driver usage in Queries
Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[x] 📝 Documentation
[x] 🗑 Chore

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Unable to use on device because local network access denied

Having some really weird behavior when trying to run on device.  Logs look like this:
ALVR v20.6.1
hostname: 9977.client.alvr
IP: <IP_ADDRESS>

Cannot connect to the internet

Over and over again. Manually adding the device by name and IP from the Windows side does nothing, it never connects. I've confirmed with nmap that the port is open randomly, it seems to only stay open when discovery is happening which is for a few milliseconds. I'm sometimes able to connect like this:
robbiet480@Roberts-MBP ALVR % nmap <IP_ADDRESS>
Starting Nmap 7.94 ( https://nmap.org ) at 2024-02-05 23:37 PST
Nmap scan report for AppleVisionPro (<IP_ADDRESS>)
Host is up (0.0067s latency).
Not shown: 997 closed tcp ports (conn-refused)
PORT      STATE SERVICE
9943/tcp  open  unknown
49152/tcp open  unknown
62078/tcp open  iphone-sync

Nmap done: 1 IP address (1 host up) scanned in 5.53 seconds
robbiet480@Roberts-MBP ALVR % telnet <IP_ADDRESS> 9943
Trying <IP_ADDRESS>...
telnet: connect to address <IP_ADDRESS>: Connection refused
telnet: Unable to connect to remote host
robbiet480@Roberts-MBP ALVR % telnet <IP_ADDRESS> 9943
Trying <IP_ADDRESS>...
Connected to applevisionpro.
Escape character is '^]'.
Connection closed by foreign host.

I've tried everything to get the local network prompt to pop on device, so far no dice. I even attempted to run a simple HTTP request to a totally unrelated service on the same box running ALVR but it worked fine. The Settings app doesn't show local network access granted. I do get the popup on iOS but only after the app crashes out from a black screen.

Oh and I thought at first it was a OS bug but other apps successfully requested local network access.

Hey I finally got it to pop after a reboot + opening the app from the launcher instead of Xcode. However, the Windows side still can't find it.

I'm wondering if the app requires the multicast entitlement to function on device which is required for sending or receiving any kind of UDP traffic..,.

Brought up the requirement for a mDNS discovery protocol to avoid the entitlement on the ALVR Discord at here

@robbiet480 Check if PR https://github.com/zhuowei/VisionOSALVRClient/pull/6 helps you connect;  I at least get a  connection to Windows from the updated ALVRClientCore.xcframework with Vision Pro hardware when adding it manually.  The stream itself needs a lot of work for me but it connects and shows VR Home when I combine the new xcframework with PR https://github.com/zhuowei/VisionOSALVRClient/pull/3

Yeah I'm able to get connected now but its not pretty as the headset only sends out discovery packets for a few seconds and if the Windows client isn't searching at the same moment they don't link.


Extension API: cursor position (determining current location and moving it)

Seems like the only way to get the current cursor position is if the user explicitly selects something.

Hi @jpoon,
Even if there is no selected text, you have to use the selection object. Something like this:
    // current editor
    const editor = vscode.window.activeTextEditor;

    // check if there is no selection
    if (editor.selection.isEmpty) {
      // the Position object gives you the line and character where the cursor is
      const position = editor.selection.active;
    }

Hope this helps

@alefragnani perfect. I'm going to close this issue :+1:

@alefragnani one more question, is there a way to move the cursor?
Say for the sample code you posted:
    // current editor
    const editor = vscode.window.activeTextEditor;

    // check if there is no selection
    if (editor.selection.isEmpty) {
      // the Position object gives you the line and character where the cursor is
      const position = editor.selection.active;

      // move cursor to this new position?
      var newPosition = position.with(position.line, 0);
    }

It's a setter!

@jrieken The API should probably indicate in the doc comments what can be set.

:heart_eyes:  Perfect!
        const editor = vscode.window.activeTextEditor;
        const position = editor.selection.active;

        var newPosition = position.with(position.line, 0);
        var newSelection = new vscode.Selection(newPosition, newPosition);
        editor.selection = newSelection;

+1 on the docs to denote setters.

All properties that don't have the @readonly tag can be set.


add Iterant.lastOptionL

There is Iterant.headOptionL but no Iterant.lastOptionL

That's cool, but it needs a test.

A very simple test, nothing complicated.

@alexandru I copied IterantHeadOptionSuite.scala with just s/head/last/g

Thanks @volth !


Updated validations.py python script.

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Closes #1
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Checking it out.

@googlebot I signed it!


I can't have a proper output

hello , I'm having some issues with the output it doesn't let me write anything and get response of the chatbot. it looks like it's in reading mode but I didn't change a thing in the code. can somebody help? also I have installed everything that was needed.

can you share an example of the terminal


reordered "Thing" so it doesnt use inheritance anymore.

(It is still supported anyway)
Changes from yesterday. I forgot to commit

somehow my working-branch is behind the main-branch, so i resolved the conflicts and now i should start a new working-branch.


Add fswatch dependency in Savi compiler, for watching file changes.

I intend to add a --watch flag to the Savi compiler, but first I need a cross-platform library for watching file changes.
This PR intends to add that library.

@mneumann - when you get a chance, can you please try this locally on your FreeBSD machine?
We don't yet have a working FreeBSD CI setup, so I can't be sure that I'm not breaking the build for you on FreeBSD.


jimp module

#4 @laktyushin ile:///C:/Users/Stanleystarsly/Downloads/Telegram%20Desktop/ChatExport_2022-09-18/messages.html

What is problems
On Thu, Oct 20, 2022, 3:07 AM aygo162 @.***> wrote:

@.**** commented on this pull request.
master from 58_saving_images_as_jpg
—
Reply to this email directly, view it on GitHub
https://github.com/TelegramMessenger/bodymovin-extension/pull/14#pullrequestreview-1148136934,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZRTZFTGUMWWIR4TUEWL6Q3WEBBGNANCNFSM6AAAAAAQPHBEHI
.
You are receiving this because you are subscribed to this thread.Message
ID: <TelegramMessenger/bodymovin-extension/pull/14/review/1148136934@
github.com>


Listing Characterstics and type management

Q
A

Bug report?
[ ]

Feature request?
[ ]

Support request?
[Y]

Hey @giorgio654, your latest commit regarding listing characterstics and management is very helpful to me, but i do not find any way a to associate any listing characterstic and its value to a listing, so my question is are you working on a way to do so or should i write a code on my own and then give a pull request.

Hi @sarthak-patidar,
You can associate listing characteristics and its value to a listing in the dashboard listing characteristics edition page.

If you want to associate them from admin we will be happy to merge your PR.
Feel free to reopen this issue if needed.
Thanks


Articles

- spawn upgrade product

- spawn what we do
    ref: local-interchain

handling elsewhere no need for a ticket


Bind AsyncLocalStorage to cursor callbacks

Attempting to resolve intermittent request context errors by binding the current async context to the callbacks provided to repo.executeCursor().  I wasn't able to reproduce the error in my local dev environment, so this fix may be incomplete.
See #2871

coverage: 94.091%. remained the same when pulling c330dff78277bc24f61d31dc46829813b8540cc9 on reindex-async-locals into 7ebeefa2e208f5b21adb7a4d68671921f595eb84 on main.


fix(tabs): observing tab header label changes to recalculate width

Uses observe-changes directive that emit an event when the mutation observer notifies a change

fixes #2155

@jelbourn @crisbeto please re-review :)

@andrewseguin can you review as well?


rocker fails: docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449

As part of https://github.com/130s/hut_utakata/issues/32, I was following rocker's instruction, I was installing nvidia-docker2. Then I hit:
$ sudo docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:432: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: cuda error: forward compatibility was attempted on non supported hw\\\\n\\\"\"": unknown.

Unfortunately, the suggestion from autowarefoundation.gitlab.io to restart OS after installing nvidia driver didn't help.

$ nvidia-smi

Command 'nvidia-smi' not found, but can be installed with:

sudo apt install nvidia-utils-435         # version 435.21-0ubuntu7, or
sudo apt install nvidia-utils-440         # version 440.82+really.440.64-0ubuntu6
sudo apt install nvidia-utils-390         # version 390.141-0ubuntu<IP_ADDRESS>
sudo apt install nvidia-utils-450         # version 450.102.04-0ubuntu<IP_ADDRESS>
sudo apt install nvidia-utils-450-server  # version 450.102.04-0ubuntu<IP_ADDRESS>
sudo apt install nvidia-utils-460         # version 460.32.03-0ubuntu<IP_ADDRESS>
sudo apt install nvidia-340               # version 340.108-0ubuntu<IP_ADDRESS>
sudo apt install nvidia-utils-418-server  # version 418.181.07-0ubuntu<IP_ADDRESS>

$ apt-cache policy nvidia-* | more
nvidia-docker2:
  Installed: 2.5.0-1
  Candidate: 2.5.0-1

nvidia-container-runtime:
  Installed: 3.4.2-1
  Candidate: 3.4.2-1

Inspired by https://github.com/130s/hut_10sqft/issues/504#issuecomment-736708815, doing this (I'm not sure why nvidia-384 is not installed on p50 after https://github.com/130s/hut_10sqft/issues/504#issuecomment-736708815):
sudo apt-get install nvidia-384

Still the same.
$ sudo docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:432: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: nvml error: driver not loaded\\\\n\\\"\"": unknown.
$
$ sudo docker run --rm --gpus 1 nvidia/cuda:11.0-base nvidia-smi
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:432: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: nvml error: driver not loaded\\\\n\\\"\"": unknown.
$

$ rocker --nvidia --x11 ros:melodic-ros-base gazebo
:
building > Step 7/7 : ENV NVIDIA_DRIVER_CAPABILITIES ${NVIDIA_DRIVER_CAPABILITIES:+$NVIDIA_DRIVER_CAPABILITIES,}graphics
building >  ---> Running in b3fe7e1aa8ce
building > Removing intermediate container b3fe7e1aa8ce
building >  ---> 27ff5d8b13ff
building > Successfully built 27ff5d8b13ff
Executing command:
docker run -it   --rm     --gpus all  -e DISPLAY -e TERM   -e QT_X11_NO_MITSHM=1   -e XAUTHORITY=/tmp/.docker.xauth -v /tmp/.docker.xauth:/tmp/.docker.xauth   -v /tmp/.X11-unix:/tmp/.X11-unix   -v /etc/localtime:/etc/localtime:ro    27ff5d8b13ff gazebo
/usr/bin/docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"process_linux.go:432: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: nvml error: driver not loaded\\\\n\\\"\"": unknown.
$

Restarting OS.

$ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

Although as kind of predicted that logging on via Window Manager became failing and going on loop same as https://github.com/130s/hut_10sqft/issues/504, ssh-ing in and running rocker seems to be working.
$ rocker --nvidia --x11 ros:melodic-ros-base gazebo
:
Executing command:
docker run -it   --rm     --gpus all  -e DISPLAY -e TERM   -e QT_X11_NO_MITSHM=1   -e XAUTHORITY=/tmp/.docker.xauth -v /tmp/.docker.xauth:/tmp/.docker.xauth   -v /tmp/.X11-unix:/tmp/.X11-unix   -v /etc/localtime:/etc/localtime:ro    27ff5d8b13ff gazebo
/ros_entrypoint.sh: line 6: exec: gazebo: not found
$
$ nvidia-smi
Tue Feb 16 23:52:56 2021
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.141                Driver Version: 390.141                   |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Quadro M1000M       Off  | 00000000:01:00.0  On |                  N/A |
| N/A   44C    P8    N/A /  N/A |    166MiB /  2002MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1847      G   /usr/lib/xorg/Xorg                           158MiB |
|    0      2443      G   /usr/bin/gnome-shell                           4MiB |
+-----------------------------------------------------------------------------+

I guess I'll have to find a configuration for nvidia driver, if I want to stick to this laptop to use Nvidia GPU.

$ ll .Xauthority
-rw------- 1 n130s n130s 161 Feb 17 00:00 .Xauthority

$ ll .ICEauthority
-rw------- 1 n130s n130s 82K Nov 19 22:58 .ICEauthority
$ ll /tmp/
total 160K
drwxrwxrwt 31 root  root   32K Feb 17 00:00 ./
:
$ sudo dpkg-reconfigure lightdm
(Switch from gdm3 to lightdm)
$ sudo reboot

The Display/Window Manager went back to what I had when I got this laptop, which I can't recall but I had some issues. Anyways the problematic part of rocker itself seems to have moved forward.

The issue originally reported is fixed.


Refactors Science Sleuth collection as donorschoose_donations

What's this PR do?

Renames the donation_infos collection to donorschoose_donations
Refactors createDonationDoc to only write documents for successful Donors Choose transactions.

Removes the donation_complete property, as we no longer have a need to store "draft" donations starting in #573. We don't query for a project until the member's profile has been completed (already collected zip, first name, and email)

How should this be reviewed?

Test locally by posting to the donations endpoint, including phone, profile_postal_code, profile_email, and profile_first_name values to post a donation.
Upon successful donation, verify a document has been created in a donorschoose_donations collection, and that it contains accurate member, project, and donation values.

Any background context you want to provide?
Creating a new donorschoose_donations collection to keep data separate from the 2014 and 2015 donation_infos, where it's a mix of successful donations and unsuccessful. It'd be nice to create a backup of the donation_infos collection and then delete from the production database as it's no longer used.
Relevant tickets
Closes todo item in #573
Checklist

[ ] Documentation added for new features/changed endpoints.
[ ] Tested on staging.

Still looking into insufficient balance errors back from DC API, but merging for now to work on other last todos in #573

Confirmed documents are written as expected:


ENH: Enable setting plot options in the containers config

Main contributions:

Seperate top and bottom tiles selection and plotting
Create a DeepMILPlotsHandler to manage all plotting capabilities available in the pipeline
Enable activating certain plot options for validation and test separately
Set plot options in the containers configs
Get rid off of all boolean parameters to activate/desactivate certain plots
Improve WSI ploppts titles by adding true and predicted labels
Group slide figures in the same directory
Delete metrics_utils.py because all functions there were used for plotting and move these to viz_utils.py

Main contributions:

Seperate top and bottom tiles selection and plotting
Create a DeepMILPlotsHandler to manage all plotting capabilities available in the pipeline
Enable activating certain plot options for validation and test separately
Set plot options in the containers configs
Get rid off of all boolean parameters to activate/desactivate certain plots
Improve WSI ploppts titles by adding true and predicted labels
Group slide figures in the same directory
Delete metrics_utils.py because all functions there were used for plotting and move these to viz_utils.py


add clinton wambugu to contributors list

@kwambugu, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

Initially struggle abit with git but felt good when I was finally able to
do it looking for more open source projects
On Mar 13, 2018 16:29, "Roshan Jossey"<EMAIL_ADDRESS>wrote:

@kwambugu https://github.com/kwambugu, I'm quite elated about your pull
request. I wanna evolve this project to addresses various problems faced by
first-time contributors. I'd love to learn about your journey in open
source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a
pull request and learned that I merged it?
We’ve recently added social share to our web app. Could you please go to
https://roshanjossey.github.io/first-contributions/#social-share and
share your first contribution to open source? Also, check out projects with
easy issues while you’re there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Roshanjossey/first-contributions/pull/3371#issuecomment-372664885,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac8y3f1E79diDtoy9ez-ZvhcpDtQ2HI2ks5td8mjgaJpZM4Sokz8
.


Skip examples with no assertions

This is so we can leave :it "example" blocks hanging with no tests to be implemented later, and see that they were skipped when running the specs:
ResponseBuilder
  builds 1xx responses.. OK
  builds 3xx responses SKIP
  builds 2xx responses SKIP
  builds 4xx responses SKIP
  builds 5xx responses SKIP
  can add headers. OK
  can write a body. OK

Makes sense to me.
Thanks!


feat: jolt sdk

Initial implementation of jolt-sdk.

Inputs and outputs are written to examplename.joltdevice
Inputs are expected at the memory location common::constants::INPUT_START_ADDRESS
Outputs are expected at memory location common::constants::OUTPUT_START_ADDRESS
A 1 is written to common::constants::PANIC_ADDRESS if there was a panic at any point during the program execution
Inputs are assumed to be initialized to 0 if not serialized into examplename.joltdevice
Currently no way to feed inputs in using the compiler

Will address this in a follow up PR
This shouldn't be an issue since unset inputs are assumed to zero

Also another follow up PR I need to look at here is to determine stable serialization of the inputs/outputs. Right now we use mem::size_of which has two problems. First, it will not work for pointer types (like Vec<T>) since those will just show up as the size of a pointer, which is wrong. Second, there is no guarantee that size_of is stable across compilations according to the docs. To address we should use some sort of serialization/deserialization scheme instead. We probably want one that is as efficient as possible. One choice that I think makes sense is bincode but open to suggestions.

squashed and incorporated into https://github.com/a16z/Lasso/pull/201


dynamic edgeQueue

Static queue (of a hard-coded length of 5000) caused some larger designs to crash. It's now dynamic using STL queues.

Thanks for the fix, @ax3ghazy!


NIFI-11680 Correct Buffer Size Calculation for Connection Balancing

Summary
NIFI-11680 Corrects PeerChannel methods used for Cluster Connection Load Balancing to avoid potential BufferOverflowException errors with the Bouncy Castle Security Provider for TLS.
The Bouncy Castle ProvSSLSessionBase uses a more coarse-grained calculation for Application Buffer Size and Packet Buffer Size than the standard JDK SSLSessionImpl. As a result of this difference in behavior, the PeerChannel.encrypt() method can expand the encrypted destination buffer greater than the SSLSession Application Buffer Size. The current approach works with the standard JDK implementation, but results in failures with files greater than 500 KB when using the Bouncy Castle Provider.
The revised approach calculates the expanded size of the intermediate prepared buffer based on the size of the destination buffer, as opposed to using the SSLSession Application Buffer Size.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[ ] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks @exceptionfactory changes look good to me. Was able to do some testing and all appears to work as expected. +1 will merge.


Cache dependencies

Looks like $HOME/local can be cached! http://docs.travis-ci.com/user/migrating-from-legacy

Closed with 29ff53d77608e9f09d192df631745d2147933ac7.


How to can i create buy now button?

Is there any function like "api/buy_product/{product_id}" ? How can handle buy product flow?

Hi,
After you've installed the payment integration plugin (2checkout, paypal), create a product and on the product page check for 'Buy button code'.


Implementing "constant references" (ownership/borrow checker)

This would be a separate stage, the borrow checker. A constant reference is denoted with an ampersand, followed by the type that can be passed &T. They have a few rules:

0 - N constant references per owned resource
they are notde-allocated at the end of their lifetime (scope)
they cannot mutate the resource that they refer to

A reference lives from the time it enters scope, and leaves scope. This can cause conflicting scopes.
Passing a reference is also denoted with an ampersand, followed by the resource to pass. So if I had a resource a, to refer to that resource, or create a new reference to it, I would write &a.
For more detailed information, check the spec (WIP).

Will start working on this stuff again soon, loads of college work at the moment...

@felixangell Same with me, man. Two weeks and I'll have free time.


uninitialized constant ApolloUploadServer::Rails on Heroku

I get the following error when trying to initialize the console on Heroku
Running console on ⬢ REMOVED... up, run.3428 (Hobby)
Traceback (most recent call last):
	7: from /app/vendor/bundle/bin/console:29:in `<main>'
	6: from /app/vendor/bundle/bin/console:29:in `load'
	5: from /app/vendor/bundle/ruby/2.6.0/gems/apollo_upload_server-2.0.0.beta.3/bin/console:4:in `<top (required)>'
	4: from /app/vendor/bundle/ruby/2.6.0/gems/apollo_upload_server-2.0.0.beta.3/bin/console:4:in `require'
	3: from /app/vendor/bundle/ruby/2.6.0/gems/apollo_upload_server-2.0.0.beta.3/lib/apollo_upload_server.rb:4:in `<top (required)>'
	2: from /app/vendor/bundle/ruby/2.6.0/gems/apollo_upload_server-2.0.0.beta.3/lib/apollo_upload_server.rb:4:in `require'
	1: from /app/vendor/bundle/ruby/2.6.0/gems/apollo_upload_server-2.0.0.beta.3/lib/apollo_upload_server/railtie.rb:3:in `<top (required)>'
/app/vendor/bundle/ruby/2.6.0/gems/apollo_upload_server-2.0.0.beta.3/lib/apollo_upload_server/railtie.rb:4:in `<module:ApolloUploadServer>': uninitialized constant ApolloUploadServer::Rails (NameError)

Unfortunately, I can reproduce it locally 😢
This is running Rails 6 on the Heroku 18 stack

Looks like running rails c via heroku run actually works so closing this one up!


Updated Turkish translation file

Added the missing words in Turkish language file according to English language file.

Fixed the commented issue.

We're no longer accepting changes for the 1.0 branch since we're so close to a 1.1 release.  Can you please update the PR to resolve the conflicts? Language files have been broken out into separate files by top-level key, instead of being in one large file.

Closed since conflicts not resolved.


Minimal versions

Requires a release of https://github.com/carllerche/iovec/pull/28

Is the CI failure related?

Yes, the iovec needed to make this work has not yet been merged and released.

this can be closed

Why? Has minimal versions support been fixed in the latest release?


Bug: Transaction Execution Error, Fundless Transaction to Burn Address

Describe the bug
Wallet does not execute transaction
Steps

Use the coinbase wallet ios app.
Browse to eternal.social
Connect the wallet. Go to eternal.social/feed
Hit the "post" button.
Type text in the modal. Hit submit button
See error:
TransactionExecutionError: An internal error was received. Request Arguments: from: 0x774069eCF05892e7667FD18B1Edb4645c273351e to: 0x0000000000000000000000000000000000000000 value: 0 ETH data: 0x54657374696e6720636f696e626173652077616c6c657420696f732062726f77736572 gas: 21726 Details: Failed to sign transaction Version: 2.21.1.

Expected behavior
I would expect the transaction to flow through. It seems the app thinks I have "failed to sign transaction" when I have definitely signed the transaction before the transaction execution.
Version
No response
Additional info

Desktop
No response
Smartphone
iphone 15 pro max

Hi @natesena thanks for flagging. I have tried to repo but was unable to. Can you provide more info about how the transaction is constructed. What chain you were using, and any other pertinent info? Thanks.

Hi Jake,
The issue lies within the coinbase wallet app on iPhone. On my app,
eternal.social the transaction never goes through.
Here is a video of the process not working:
https://drive.google.com/file/d/1uGIJjuamIw2in8GhEOejRfLldqDvd0Io/view?usp=sharing
More or less it fails silently.
Appreciate you looking into this - Coinbase Wallet would be my ideal flow
for users to have the best experience before launch.
Nate
On Tue, Oct 29, 2024 at 12:10 PM cb-jake @.***> wrote:

Hi @natesena https://github.com/natesena thanks for flagging. I have
tried to repo but was unable to. Can you provide more info about how the
transaction is constructed. What chain you were using, and any other
pertinent info? Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/coinbase/coinbase-wallet-sdk/issues/1435#issuecomment-2444731405,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTATFTNGU6OAKDHCYC3NP3Z56XOPAVCNFSM6AAAAABQNRSYXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBUG4ZTCNBQGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Interesting. What version of the app are you using. When I first tested I used the mobile to desktop connection (ie walletlink). I just tested with the in app browser and that worked as well. I used mainnet and base on the two tests

The version I have currently is 29.16.0
On Tue, Oct 29, 2024 at 3:24 PM cb-jake @.***> wrote:

Interesting. What version of the app are you using. When I first tested I
used the mobile to desktop connection (ie walletlink). I just tested with
the in app browser and that worked as well. I used mainnet and base on the
two tests
—
Reply to this email directly, view it on GitHub
https://github.com/coinbase/coinbase-wallet-sdk/issues/1435#issuecomment-2445140417,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTATFUCJYNB7WGAPOWCK7DZ57OFBAVCNFSM6AAAAABQNRSYXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBVGE2DANBRG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

I'm using the same version. Is there a specific network you're using? Also, have you tried using the QR code to connect via walletlink? Curious if we can narrow down the issue to the connection type.


[Feature] in vdp2_init, add struct parameter to set resolution

Would be nice to add an optional parameter to resolution (320x224, 320x240, hires,...)

I plan to have a separate function for this. This is for when a user wants to change resolutions at any other time.

that's fine.

I refactored to set resolution: vdp2_tvmd_display_res_set().


Updates to Compose docs and ENV vars

Compose teamhad forgotten some documentation
Updated ENV for Distribution also

Signed-off-by: Mary Anthony<EMAIL_ADDRESS>cc/ @bfirsh and @aanand

@thaJeztah @docker/docs-owners

LGTM!

Tested a link for both changed variables and they pointed to a document, so LGTM :)

Thanks Gents!


Restriction-related fixes (2nd attempt)

Test

kp = publish v4 + this PR (test 2 things together)?

Changes

Restores the previous PR
Addresses the crashing issue with the modal

Note: this sits on top of the v4 branch.  Not meant to be merged directly, but allows easier review.

-- postpone --
Seems like we'll postpone this, so head over to inf to just test v4


Update azure-security.md

WAF gateway picture is of ExpressRoute which does not match the section.  Propose replacing picture with the Application Gateway WAF diagram from here azure-docs/articles/application-gateway/media/application-gateway-web-application-firewall-overview/WAF1.png

@russmsft : Thanks for your contribution! The author, @UnifyCloud, has been notified to review your proposed change.

@TomShinder - Would you review the proposed changes? Thanks

Thank you for your input! We'll schedule that to be fixed with the next revision of the doc. Thanks!

#please-close


[DTC-3268] codify the resource request for jobs runner and make it a separate pod by default

It could avoid customers setting low resources without checking our recommendation
Separate jobs runner pod by default would make it easier for the liveness detection https://github.com/tryretool/retool_development/pull/18728

@JatinNanda I don't have azure storage access.. could you please publish the new version for me?  🙏

merged before i could get to it but LGTM!


Snapshots: Propagate status changes to VolumeSnapshotData

The VolumeSnapshotData.Status is never actually updated: we only care about the VolumeSnapshot objects. I think it makes sense to keep these two in-sync since after the creation the status is always taken from the backend.
This should fix issue #764.

/lgtm


Typo on Process Media Frames with MediaFrameReader page

There is a typo on this page:
https://docs.microsoft.com/en-us/windows/uwp/audio-video-camera/process-media-frames-with-mediaframereader#initialize-the-mediacapture-object-to-use-the-selected-frame-source-group

Next, create a MediaCaptureSettings object that will be used to initialize the MediaCapture object.

Instead of MediaCaptureSettings it should be MediaCaptureInitializationSettings. That word is a hyperlink so the link will need to be fixed too.

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

ID: db4165a7-748e-e566-3b38-21ad71a76489
Version Independent ID: d8762b7e-22b0-cfd6-25b0-5e2a68cdea9f
Content: Process media frames with MediaFrameReader - Windows UWP applications
Content Source: windows-apps-src/audio-video-camera/process-media-frames-with-mediaframereader.md
Product: uwp
Technology: audio-video-and-camera
GitHub Login: @drewbatgit
Microsoft Alias: drewbat

This typo has been fixed. Thank you for reporting this issue.


Update README.md

Update the command issues at line 14, 19,  65.

closing due to inactivity. if this is still an issue please re-create the PR

closing due to inactivity. if this is still an issue please re-create the PR


NIFI-12733 Make Apicurio's groupId optional and configurable and use …

…artifactId instead of name as key

Summary
NIFI-12733
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[ ] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[x] Documentation formatting appears as expected in rendered files

Thanks @juldrixx will review soon!


Running on Home Assistant 0.118.5 with Python 3.8.6

Recently updated to Home Assistant 0.118.5 with Python 3.8.6 (pyenv on Raspian/RPI).
The plugin doesn't start, the following log messages are traced:
Logger: aiohttp.server
Source: deps/lib/python3.8/site-packages/pycountry/__init__.py:12
First occurred: 22:44:11 (1 occurrences)
Last logged: 22:44:11
Error handling request

Traceback (most recent call last):
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 422, in _handle_request
    resp = await self._request_handler(request)
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/aiohttp/web_app.py", line 499, in _handle
    resp = await handler(request)
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 118, in impl
    return await handler(request)
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/homeassistant/components/http/request_context.py", line 18, in request_context_middleware
    return await handler(request)
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/homeassistant/components/http/ban.py", line 72, in ban_middleware
    return await handler(request)
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/homeassistant/components/http/auth.py", line 127, in auth_middleware
    return await handler(request)
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/homeassistant/components/http/view.py", line 129, in handle
    result = await result
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/homeassistant/components/config/config_entries.py", line 136, in post
    return await super().post(request)
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/homeassistant/components/http/data_validator.py", line 60, in wrapper
    result = await method(view, request, *args, **kwargs)
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/homeassistant/helpers/data_entry_flow.py", line 69, in post
    result = await self._flow_mgr.async_init(
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/homeassistant/data_entry_flow.py", line 119, in async_init
    flow = await self.async_create_flow(handler, context=context, data=data)
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/homeassistant/config_entries.py", line 535, in async_create_flow
    integration.get_platform("config_flow")
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/homeassistant/loader.py", line 424, in get_platform
    cache[full_name] = self._import_platform(platform_name)
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/homeassistant/loader.py", line 429, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 783, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/homeassistant/.homeassistant/custom_components/smartthinq_sensors/config_flow.py", line 3, in <module>
    import pycountry
  File "/home/homeassistant/.homeassistant/deps/lib/python3.8/site-packages/pycountry/__init__.py", line 12, in <module>
    __version__ = pkg_resources.get_distribution("pycountry").version
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/pkg_resources/__init__.py", line 480, in get_distribution
    dist = get_provider(dist)
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/pkg_resources/__init__.py", line 356, in get_provider
    return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/pkg_resources/__init__.py", line 899, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/home/homeassistant/.pyenv/versions/3.8.6/lib/python3.8/site-packages/pkg_resources/__init__.py", line 785, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'pycountry' distribution was not found and is required by the application

even if pycountry seems installed.
Thanks for your support

Could you use 3 backticks for code blocks? Also try beta HA and see if the 3.9 helps.

Anyone using with Python 3.8? A friend of mine does not have problems, so it may be just a problem with my installation.

Just discovered that my hass installation has some problems with pip, maybe too updated (20.3.1). Probably the pycountry package could not be installed correctly. Fixed the dependency error I got back my dryer sensors :)
I think you can close this issue....

I have  Home Assistant 0.110.3 with Python 3.8.0 and I have the same error, could you explain how update the dependency?
 You use pip, not apt, for most Python packages.

Home Assistant run on Odroid C1 with DietPi v6.34.3, sorry I don't understand your question

How are you running the command? Command line? SSH add-on?

I run the command in command line, I don't have installed SSH addon

But did you run it in the homeassistant pyenv?

I have Home Assistant 0.110.3 with Python 3.8.0 and I have the same error, could you explain how update the dependency?

My problem probably was due to version of pip itself, that I forced to be updated to 20.3.1 while hass needed 20.2.something.
Please check which version of pip you have installed in your home assistant python environment. I understood that if you update the hass installation you get back all the correct dependencies.

I think it run in pyenv, I installed HA through dietpi-software that is an automatism for install software.
I also run this command
su -s /bin/bash homeassistant
pip3 install pycountry
Requirement already satisfied: pycountry in /usr/lib/python3/dist-packages (17.5.14)

My pip version is
pip 18.1 from /usr/lib/python3/dist-packages/pip
How force update version?

Solved
On the system there are python 3.7 and when I run pip3  install pycountry don't update HA, because HA use another version of python inside homeassistant folder.
So i run this command
/home/homeassistant/.pyenv/versions/3.8.0/bin/pip3 install pycountry
and finally I reinstalled the LG components


Update ObjectMapper to version 3.0

Fix problem of being unable to compile with Swift 4 due to functions used in ObjectMapper 2.x that are now obsolete

need it

@ivanbruel We also need it for our projects. Can you please elaborate on it?


Refresh

To test among other things:

calculate details
full screen image
categoriesexplorer
splash
additives bottom sheet
Ingredients that are ambiguous (542e9fd5c52311cc94876d9062ce6153dc24e413)
Shake to scan removed (0b26fd060d0127541a4f3331371ee408d7ad3297)

Unit test failed. I relaunched the CI
openfoodfacts.github.scrachx.openfood.network.ProductsAPITest > post_product FAILED
    java.lang.RuntimeException at ProductsAPITest.java:255
        Caused by: java.net.SocketTimeoutException at ProductsAPITest.java:46


ENH: Reenable windows

Checklist

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

Let's see how it goes!

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The top level meta key c_compiler is unexpected
The top level meta key cxx_compiler is unexpected

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Support Go controls

Currently this experience is not working on Go in VR mode. The fix should be simple. I have a PR ready.
P.S. I work with Jacob Rossi.

Awesome thanks! I don't have a Go so I couldn't test it myself, but I merged anyways.


add --exists-action to pip-sync

pip has the argument --exists-action:
$ pip --help
...
  --exists-action <action>    Default action when a path already exists: (s)witch, (i)gnore, (w)ipe, (b)ackup, (a)bort.

It is not possible to use --exists-action with pip-sync, isn't it?
The problem: The pip-sync call should not hang with the input question:

What to do?  (s)witch, (i)gnore, (w)ipe, (b)ackup

Yeah, I just ran into this too:
$ pip-sync --version
pip-sync, version 1.11.0

$ pip-sync --exists-action w
Error: no such option: --exists-action

I think that an implementation would look very much like the way #283 solves for #192 by adding a passthrough for --index-url and --extra-index-url.

@vphilippon @davidovich would such a PR be welcome? I'm new to contributing to pip-tools and via jazzband in general. I'm CCing you two based on the pip-tools lead discussion at https://github.com/jazzband/roadies/issues/64, but LMK if there's someone else I should ask. Thanks!

Hi @jasonm, yes PRs are always welcomed!
I had the idea of making a more generic solution, passing all unknown flags to pip so we don't have to redefine them on pip-sync, but it was getting mixed with src_files and it was getting messy, so I've set that aside for now. We can add requested options directly on pip-sync as it's been done before for now.
FYI, pip environment variables can also be used to set options not directly defined on pip-sync.
Ex: PIP_EXISTS_ACTION=w

@jedie FYI, there is tracking issue #321 for additional options to pip-compile and pip-sync.
I'll close this based on the above workaround, but please let us know if it doesn't resolve your issue. Thanks!


Adjustment to the Notification component.

The maximum size of the component should be 500px.

can I do this? :D


Update python version to 3.11 for CUDA and ROCm images

Description

RHOAIENG-11843
Updating python version to 3.11 for Ray CUDA and Ray ROCm images
How Has This Been Tested?

Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

@oksanabaza this requires #242 first so you can change the output-image and additional-tag values accordingly.

@oksanabaza I think we can switch to Python 3.11. Also the tags have to been changed accordingly here: https://github.com/opendatahub-io/distributed-workloads/blob/90f9e75dbd039698c6375b5e00d4a9dd7f1129c3/.tekton/ray-cuda-push.yaml#L26-L29

@oksanabaza I think we can switch to Python 3.11. Also the tags have to been changed accordingly here:
https://github.com/opendatahub-io/distributed-workloads/blob/90f9e75dbd039698c6375b5e00d4a9dd7f1129c3/.tekton/ray-cuda-push.yaml#L26-L29

do we want to keep the tag with py39 here 2.35.0-py39-cu121 or should we change it into 2.35.0-py311-cu121?

@oksanabaza I think we can switch to Python 3.11. Also the tags have to been changed accordingly here:
https://github.com/opendatahub-io/distributed-workloads/blob/90f9e75dbd039698c6375b5e00d4a9dd7f1129c3/.tekton/ray-cuda-push.yaml#L26-L29

I see that these changes are from upstream Konflux. However, since we are considering moving to Python 3.11, should we keep the tag with py39 here 2.35.0-py39-cu121, or should we update it to 2.35.0-py311-cu121 to reflect the new Python version?

@oksanabaza you're right, the tags have to be changed to 2.35.0-py311-cu121  and 2.35.0-py311-rocm61 as part of that PR.

@oksanabaza have you updated the tags in the Konflux pipelines? I can't see the update :)

@astefanutti going to updated it now, thanks

@oksanabaza you don't need to create a new PR. You can update the tags in that PR.

@astefanutti I have updated all labels, could you please check it again?

@astefanutti could you please take a look one more time? I have also separated the Python version and image tag into two separate arguments in the Dockerfile

@astefanutti I have updated all labels, could you please check it again?

@oksanabaza there are two leftovers in the examples, and then it'll be good to go.


Analyser is the wrong abstraction

On each PR, GitHub (and other VCSs eventually) call an Analyser interface which could be Docker or File System. But there's lots of logic inside File System that is duplicated in Docker.
Instead GitHub PR should call some function which accepts an Executor interface, which builds all the exec.Cmd and passes them into an executor, which could be Docker or File System.
package analyser

func Analyse(exec Executor, tools []db.Tool, config Config) ([]Issue, error) {
    exec.Execute([]string{"git", "clone"}
    // etc
}

type Executor interface {
    Execute(args []string) (combined []byte, err error)
}

This would also mean the executers are instantiated for each PR, instead of once at start, so we might need a NewExecuter func being passed around instead of an interface.
No, maybe everything still implements an Analyser, which has a method NewEnvironment() (Executer, error)  which can be called for each PR and returns a new environment to work in.

Fixed in #15


Compile refs in embedded format

Proposed Changes
Adds support for embedding content of a ref in the compiled output.
This allows for revealing compiled files without needing access to ref files.
By running $ kapitan compile --embed-refs, compiled files with refs will have embedded compiled refs under the following format (gkms as an example):
?{gkms:ReallyLongBase64HereZ2FyZ2FiZQo=:embedded}
Which means that compiled outputs with embedded refs can be completely distributed without the need to access ref contents in their refs directory.
Related to #435
Also fixes issue #499

sent fixes for code review comments


CredentialsManager credentials method and Api renewCredentials method do no send parameters

Checklist

[X] The issue can be reproduced in the auth0_flutter sample app (or N/A).
[X] I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
[X] I have looked into the API documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Description
We are using the credentialsManager credentials method auth0.credentialsManager.credentials(); to retrieve and refresh our tokens which has been working fine. The issue we are having is that now we need to pass some parameters which do not seem to reach the auth0 dashboard and our login flow .
However, during the login process we access those parameters through event.request.query which is working as expected:
auth0.webAuthentication(scheme: scheme).login(
            scopes: const {'openid', 'profile', 'offline_access'},
            redirectUrl: redirectUrl,
            useEphemeralSession: preferEphemeralSession,
            audience: audience,
            parameters: {
              ...parameters,
              'prompt': 'login',
            },
          );

But this is not the case for the credentialsManager credentials method where the login flow is triggered but the parameters are not present. It is worth mentioning that we have also tried the following method and still we cannot receive the parameters:
auth0.api.renewCredentials(
        refreshToken: storedRefreshToken,
        parameters: {
          ...parameters,
          'prompt': 'none',
        },
      );

Reproduction

Refresh the tokens by calling auth0.credentialsManager.credentials or auth0.api.renewCredentials and pass some parameters
Check the login flow in auth0 dashboard to verify that the parameters are being retrieved through event.request.query

Additional context
No response
auth0_flutter version
1.5.0
Flutter version
3.19.2
Platform
Android, iOS
Platform version(s)
No response

We are seeing the same issue could we please get a response on this? CC @Widcket @poovamraj

Can you please give us an update on this? We are paying customers if this could help on taking decisions.

Same issue

Any update on this one?

Update: We're planning to fix this as a part of the next major version that we're actively working on. The release is tentatively planned for mid Jan.


Negate Boolean attribute values when preceded by "!"

Describe the issue
In a comment of issue https://github.com/ibissource/iaf/issues/1885 about the Frank!Doc, a note was added about Boolean attributes. It was said that when an attribute setter is of type Boolean, then the Frank developer should be able to write
<SomePipe boolAttribute="! ${boolParameter}"...>

This should perform the not-operator to the Boolean value of boolParameter and assign it to "boolAttribute". It was said (in the issue or through the telephone) that there are Frank configs that apply this feature already.
I have tested whether this behavior has been implemented when the old ibisdoc parsing is used. I wrote a simple adapter. The adapter has active="! ${param}". I ran the adapter with the Frank!Runner and manipulated the value of param through a Java system parameter .\start.bat -Dparam=false. My adapter was not available in Test Pipeline.
The above test suggests that this is a feature request, not a bug, but more research is needed to verify this.
Reporter
Martijn Dirkse
Screenshots
If applicable, add screenshots to help explain your problem.
Configuration
<Configuration
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:noNamespaceSchemaLocation="./frankdoc.xsd"
  name="default"
>
    <Adapter name="default" active="! ${param}">
        <Receiver>
            <JavaListener name="dummy"></JavaListener>
        </Receiver>
        <Pipeline firstPipe="echo">
            <Exit path="EXIT" state="success" />
            <FixedResultPipe name="echo" returnString="My ${param}" substituteVars="false">
                <Forward name="success" path="EXIT" />
            </FixedResultPipe>
        </Pipeline>
    </Adapter>
</Configuration>

Input
Please provide an example of the input message.
Alternatively, provide a Ladybug report.

Environment
Please go to the console of your Frank, click on 'Information' and copy-paste the results here.

Additional Environment

DBMS: [e.g. Oracle, MSSQL, MariaDB, MySql, PostgreSQL]
Browser: [e.g. Chrome, Safari, Edge, Firefox]

Additional Context
Jeroen made the remark in issue https://github.com/ibissource/iaf/issues/1885 that was the reason the create the present issue. I think he should investigate the statement he made before this issue is implemented.

I do not know if it is relevant, but I use this feature succesfully, but I never use a space between the ! and the {
example: active="!${param}"

Thanks, Richard van der Stel.
I updated my example to use another pipe and to omit the space after the !. My updated config contained the line:
<pipe className="nl.nn.adapterframework.pipes.CsvParserPipe"
                name="parse" fileContainsHeader="!${param}">

I started the Frank!Runner like: .\start.bat -Dparam=false. In the Adapter Status page I got the following error:
ERROR: error initializing pipeline, Exception configuring CsvParserPipe [parse]: No fieldNames specified, and fileContainsHeader=false

To see whether this example makes sense, I also tried to remove the "!" sign and to start with -Dparam=true. Then I got no error, so the "!" sign is the only thing that was rejected about my example.
Richard van der Stel, do you have an example where using the !-sign works?

https://vcs.aws.insim.biz/ibissource/dm/ibis4titan/ibis4titan_titan/-/blob/master/src/main/configuration/titan/Configuration_TS_ArchiveDocumentStreaming_4.xml
Code snippets :

			<sender
				active="${active.batch.TS_ArchiveDocumentStreaming_4}"
				className="nl.nn.adapterframework.extensions.cmis.CmisSender"

			<sender
				active="!${active.batch.TS_ArchiveDocumentStreaming_4}"
				className="nl.nn.adapterframework.extensions.cmis.CmisSender"

SideSpecifics_AS.properties:
active.batch.TS_ArchiveDocumentStreaming_4=false
SideSpecifics_MIG.properties:
active.batch.TS_ArchiveDocumentStreaming_4=true
So in the loaded configurations we see that one pipe is active on the AS node and on the MIG node we see that the other pipe is active.

As I informed you, the active-attribute is handled differently from other attributes, the configuration is first processed by https://github.com/ibissource/iaf/blob/master/core/src/main/resources/xml/xsl/active.xsl upon loading, resulting in elements with the attribute active set to !false and true to be copied and those with a different/no value to be removed from the loaded configuration.
I'm not sure how other boolean attributes are handled internally, might be that everything not having the string true actually just becomes false, regardless of the fact that you put an ! in front of the false. I suspect that .\start.bat -Dparam=true, .\start.bat -Dparam=false and .\start.bat -Dparam=randomvalue would all result in the same error in your example, as the ! will ensure it never becomes literal true.

I tested my example with -Dpara=true, -Dparam=false and -Dparam=. In all these cases my configuration was in error, so !${param} evaluated to false. This verifies Ricardo's statement. Richard van der Stel, I guess that in your example you are also experiencing that !${active.batch.TS_ArchiveDocumentStreaming_4} always evaluates to false. I do not know how to test that in your situation, but I trust on the test I did in my simple example.

Implementing the !-operator for attributes other than "active" is more complicated than I initially thought. We do not want to do this. I closed the pull request I was working on, #1906. We are satisfied when the !-operator only works for "active", as has been demonstrated to work. The only remaining task is to update the Frank!Doc. The Frank!Doc has to understand the special behavior of the "active" attribute.


release: 0.13.2

cc @kngwyu
This is the last release I think we need to make for the 0.13 series before we merge a number of breaking changes and start developing for 0.14. We already have breaking changes #1354 #1391 and #1398 waiting to be merged, as well as many #[deprecated] methods we could begin cleaning up.
Making this release will fix the issues with finalization which is blocking pyo3-asyncio from making a first release.
I'll try to release this on Tuesday if I don't hear otherwise. Though I think it'd be nice to merge #1393 and #1379 before we release this, so I might wait if needed.
I suggest the following release text:

This release is a small iteration over PyO3 0.13.1. It adds a serde feature which provides implementations of Serialize and Deserialize for types inside the Py<T> smart pointer.
Of note is that this release disables automatic finalization of the Python interpreter at program exit for Rust binaries embedding the Python interpreter. This was found to cause a number of issues with C extensions such as Tensorflow and Scipy which were sensitive to the deinitialization order. For the vast majority of users this should cause no impact, and fix a number of problem cases. For the minority who did depend on finalization, the unsafe method with_embedded_python_interpreter has been added to manually control the interpreter lifecycle.
For full details of all changes, see the CHANGELOG.
Thank you to everyone who contributed code, documentation fixes, design ideas, bug reports, and feedback. The following users' commits are included in this release:
@daniil-konovalenko
@davidhewitt
@decathorpe
@ijl
@kangalioo
@kngwyu
@nw0

I was thinking #1393 would be merged after this release since 0.13.2 would unblock the first public release of pyo3-asyncio. There are a few API doc links I'd like to add in there that would only be available after docs.rs generates them.
I could probably guess at what they would be in the meantime though, so it's up to you guys.

I was thinking #1393 would be merged after this release since 0.13.2 would unblock the first public release of pyo3-asyncio. There are a few API doc links I'd like to add in there that would only be available after docs.rs generates them.
I could probably guess at what they would be in the meantime though, so it's up to you guys.

I'm flexible. The reason I'm thinking that it would be nice to merge the guide entry first, is then users who will be reading the guide at pyo3.rs/v0.13.2/ will see the new async section. Your call whether you want this, or are happy for the guide to only show on pyo3.rs/master/ (and future v0.14+ releases).

I'm flexible. The reason I'm thinking that it would be nice to merge the guide entry first, is then users who will be reading the guide at pyo3.rs/v0.13.2/ will see the new async section. Your call whether you want this, or are happy for the guide to only show on pyo3.rs/master/ (and future v0.14+ releases).

I'm ok with merging it for 0.13.2. Like you said on the PR, the link to docs.rs should be pretty straightforward

I'm ok with merging it for 0.13.2. Like you said on the PR, the link to docs.rs should be pretty straightforward

Still waiting on the other PRs, which are steadily moving forward. Also the fix in #1405 seems worth including.
I'll rebase this in a few days once they're all ready.

Still waiting on the other PRs, which are steadily moving forward. Also the fix in #1405 seems worth including.
I'll rebase this in a few days once they're all ready.

Thanks for preparing this release!
I'm for including #1405 and #1393

Thanks for preparing this release!
I'm for including #1405 and #1393

The other PRs have now been merged; I'll rebase and release tonight unless I hear a reason not to!

I request #1420 to be decided for this release.

Agreed. The release can wait a little longer, I'm sure 😅

Rebased; I'll release this tomorrow evening unless again there's reasons to wait. I'll probably merge and rebase on #1422 before doing so.

The OpenSSL team will publish a security release on Tuesday 16th February 2021. PyCA Cryptography follows OpenSSL and releases new builds on the same day.
Would it be possible to get a new release of pyo3 out before Tuesday? PyCA Cryptography could then bump pyo3 version for the upcoming release and benefit from @birkenfeld's PR #1420. This would make Debian stable and Alpine 3.12 users happy.
CC: @alex @reaperhulk

FWIW, I see no need for pyo3 to schedule a release around OpenSSL. We
can do two releases of pyca/cryptography, version numbers are free, as
I'm so often reminded.
On Fri, Feb 12, 2021 at 11:31 AM Christian Heimes
<EMAIL_ADDRESS>wrote:

The OpenSSL team will publish a security release on Tuesday 16th February 2021. PyCA Cryptography follows OpenSSL and releases new builds on the same day.
Would it be possible to get a new release of pyo3 out before Tuesday? PyCA Cryptography could then bump pyo3 version for the upcoming release and benefit from @birkenfeld's PR #1420. This would make Debian stable and Alpine 3.12 users happy.
CC: @alex @reaperhulk
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

--
All that is necessary for evil to succeed is for good people to do nothing.

👍 I think this release now has everything it needs, so I'm releasing shortly. (Once CI is green.)

Thanks 🎉


Set a limit to recursive data types

If an Object Type T1 has a field f1 of an abstract type A that might be resolved into the same type as T1 (this happens when T1 is the first A concrete type defined in the schema, because Mirage resolves abstract types by selecting the the first concrete type that appears - see https://github.com/lolaent/gql-oss/issues/12):
interface A {}
type T1 implements A {
  f1: A
}
type T2 implements A {}

# will be treated from the mock generation point of view as
...
type T1 implements A {
  f1: T1
}
...

and a Maximum call stack size exceeded will crash the mock generator. A mechanism that limits the recursivity needs to be implemented.
This can currently be mediated by setting the f1 field type to a concrete type that doesn't implement the recursive field, bypassing the error altogether.

This is non-trivial to do. A warning has been implemented instead. https://github.com/lola-tech/graphql-kimera/blob/master/packages/graphql-kimera/src/engine.js#L66-L74


@Logging.configure throws error in Julia v0.6

When trying to use the logging macros:
julia> using Logging
julia> @Logging.configure(level=INFO)
ERROR: MethodError: no method matching override_info(::Logging.LogLevel)
Closest candidates are:
    override_info(; args...) at /home/vharisop/.julia/v0.6/Logging/src/Logging.jl:143

[vharisop@alwaysbored] julia -v
julia version 0.6.3

same for me on version 0.6.4

By simply following the error hint, I modified the function as below which will work with Julia 0.6.4.

143 #override_info(;args...) = (:override_info, true) in args

144 override_info(level::LogLevel;args...) = (:override_info, true) in args

I found the code in github might not be pushed to julia 0.6.4 package management.
If you install Logging directly from the github, it works for 0.6.4, i.e.,
instead of Pkg.add("Logging"),
do Pkg.clone("https://github.com/kmsquire/Logging.jl.git")


Homebrew doesn't allow side-by-side Xcode 8.3.3 and 9.0 installations

I have both 8.3.3 and 9.0 installed on MacOS High Sierra.
When running brew upgrade xxxx, I am getting Error: Your Xcode (8.3.3) is too outdated. Please update to Xcode 9.0 (or delete it). Xcode can be updated from https://developer.apple.com/download/more/.
This seems a harsh position since 8.3.3 is the current release and 9.0 is only in BETA (and not stable yet).

What is the output of
xcode-select -p

and
brew config

and
brew doctor

Seeing the same issue. @ilovezfs  Here are my outputs:
/Applications/Xcode.app/Contents/Developer```

```Leo-Natans-Wix-MPB:~ lnatan$ brew config
HOMEBREW_VERSION: >1.2.0 (no git repository)
ORIGIN: https://github.com/Homebrew/brew
HEAD: 76ed7898d002ed36e397c908f00589f62b78e641
Last commit: 3 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 623377fa6c659c89c1f8601fbdf0b2da59b76329
Core tap last commit: 3 months ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local/Homebrew
HOMEBREW_CELLAR: /usr/local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: octa-core 64-bit haswell
Homebrew Ruby: 2.3.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
xcodebuild: error: SDK "/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.0.sdk" cannot be located.
clang: error: unable to find utility "clang", not a developer tool or in PATH
Clang: N/A
Git: 2.12.2 => /usr/local/bin/git
Perl: /usr/bin/perl
Python: /usr/local/bin/python => /usr/local/Cellar/python/2.7.13/Frameworks/Python.framework/Versions/2.7/bin/python2.7
Ruby: /Users/lnatan/.rvm/rubies/ruby-2.0.0-p643/bin/ruby
Java: N/A
macOS: 10.13-x86_64
Xcode: 8.3.3
CLT: <IP_ADDRESS>.1.1497666128
X11: N/A```

```Leo-Natans-Wix-MPB:~ lnatan$ brew doctor
xcodebuild: error: SDK "/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator11.0.sdk" cannot be located.
clang: error: unable to find utility "clang", not a developer tool or in PATH
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: You are using macOS 10.13.
We do not provide support for this pre-release version.
You may encounter build failures or other breakages.
Please create pull-requests instead of filing issues.

Warning: Ruby version 2.3.3 is unsupported on 10.13. Homebrew
is developed and tested on Ruby 2.0, and may not work correctly
on other Rubies. Patches are accepted as long as they don't cause breakage
on supported Rubies.

Warning: Your Xcode (8.3.3) is too outdated.
Please update to Xcode 9.0 (or delete it).
Xcode can be updated from
  https://developer.apple.com/download/more/

Warning: Your Xcode (8.3.3) is outdated.
Please update to Xcode 9.0 (or delete it).
Xcode can be updated from
  https://developer.apple.com/download/more/

If 9.0 is installed, you may need to:
  sudo xcode-select --switch /Applications/Xcode.app
Current developer directory is:
  /Applications/Xcode.app/Contents/Developer

Warning: Broken symlinks were found. Remove them with `brew prune`:
  /usr/local/share/man/man1/prj2make.1
Leo-Natans-Wix-MPB:~ lnatan$ xcode-select -p
/Applications/Xcode.app/Contents/Developer```

This is blocking work.

OK. Please try this:
sudo mv /Applications/Xcode.app /Applications/Xcode-8.3.3.app
sudo mv /Applications/Xcode-beta.app /Applications/Xcode.app

@ilovezfs I actually wish to use 8.3.3, not 9.0

@LeoNatan we don't using 8.3.3 with brew on 10.13, but of course you can revert to whatever arrangement you want after doing whatever you need to do with brew.

That's a problem because one of the formulas does not support Xcode 9.
Why are you hardcoding which Xcode is used on which OS? Even after beta timeframe is over, it should be possible to switch an Xcode version on the fly using Apple provided tools, and brew should respect that setting.

That's a problem because one of the formulas does not support Xcode 9.

You can use brew install --force-bottle foo to use the Sierra bottle.

Why are you hardcoding which Xcode is used on which OS? Even after beta timeframe is over, it should be possible to switch an Xcode version on the fly using Apple provided tools, and brew should respect that setting.

Allowing arbitrary Xcode versions leads to avoidable build failures and additional support burden.

Does my suggestion in https://github.com/Homebrew/brew/issues/2835#issuecomment-311949286 get brew working again? (There's another thing I'd like you to test after testing that if possible.)

The formula is build from source, using a --HEAD argument.

Allowing arbitrary Xcode versions leads to avoidable build failures and additional support burden.
I don't see how it is different right now.

The formula is build from source, using a --HEAD argument.

Then you'll need to wait for it to be fixed with Xcode 9 (or help to fix it).

I'll take a look, thanks

I'll take a look, thanks

You're welcome. Thanks for pitching in!

(There's another thing I'd like you to test after testing that if possible.)

Specifically (if you get a chance to test this), does brew work if you have the original names
/Applications/Xcode.app
/Applications/Xcode-beta.app

and just run
sudo xcode-select -s /Applications/Xcode-beta.app/Contents/Developer

?

This gives me a different failure:
/usr/local/opt/carthage/bin/carthage
/private/tmp/fbsimctl-20170629-88584-2o09wx/fbsimctl /private/tmp/fbsimctl-20170629-88584-2o09wx
*** Skipped downloading GCDWebServer.framework binary due to the error:
	"API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)"
*** Checking out GCDWebServer at "3.3.3"
*** xcodebuild output can be found in /var/folders/d0/q423mrk13bn_bx8wr416nsq40rv2wb/T/carthage-xcodebuild.b61q9y.log
*** Building scheme "GCDWebServers (Mac)" in GCDWebServer.xcodeproj
Build Failed
	Task failed with exit code 1:
	/usr/bin/xcrun dsymutil /tmp/fbsimctl-20170629-88584-2o09wx/fbsimctl/Carthage/Checkouts/GCDWebServer/Carthage/Build/Mac/GCDWebServers.framework/GCDWebServers -o /tmp/fbsimctl-20170629-88584-2o09wx/fbsimctl/Carthage/Checkouts/GCDWebServer/Carthage/Build/Mac/GCDWebServers.framework.dSYM

This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/d0/q423mrk13bn_bx8wr416nsq40rv2wb/T/carthage-xcodebuild.b61q9y.log

However, in the linked log, build seems to have succeeded:
** BUILD SUCCEEDED **

"API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)"

You should be able to fix that by setting the environment variable HOMEBREW_GITHUB_API_TOKEN to your token. You can create one if you haven't already.

Doesn't that just give me a prebuilt framework? That's not a solution to the build issue.

Well currently it looks like it's just failing because that download is failing. It would be good to see if that dsymutil error goes away once you get the download working.

$ xcode-select -p
/Applications/Xcode.app/Contents/Developer
$ brew config
HOMEBREW_VERSION: 1.2.3
ORIGIN: https://github.com/Homebrew/brew
HEAD: ed9942fbd1ec4243f0a92ab8f9b2411c8b1fb091
Last commit: 3 weeks ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: e5a81708bd4e4a85395d96277e20aa266607a6da
Core tap last commit: 7 days ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local/Homebrew
HOMEBREW_CELLAR: /usr/local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: octa-core 64-bit haswell
Homebrew Ruby: 2.3.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Clang: 8.1 build 802
Git: 2.12.2 => /usr/local/bin/git
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /usr/local/bin/ruby => /usr/local/Cellar/ruby/2.4.1_1/bin/ruby
Java: 1.8.0_102, 1.8.0_25, 1.7.0_51
macOS: 10.13-x86_64
Xcode: 8.3.3
CLT: N/A
X11: 2.7.11 => /opt/X11
$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!
Warning: You are using macOS 10.13.
We do not provide support for this pre-release version.
You may encounter build failures or other breakages.
Please create pull-requests instead of filing issues.
Warning: Ruby version 2.3.3 is unsupported on 10.13. Homebrew
is developed and tested on Ruby 2.0, and may not work correctly
on other Rubies. Patches are accepted as long as they don't cause breakage
on supported Rubies.
Warning: Your Xcode (8.3.3) is too outdated.
Please update to Xcode 9.0 (or delete it).
Xcode can be updated from
https://developer.apple.com/download/more/
Warning: Your Xcode (8.3.3) is outdated.
Please update to Xcode 9.0 (or delete it).
Xcode can be updated from
https://developer.apple.com/download/more/
If 9.0 is installed, you may need to:
sudo xcode-select --switch /Applications/Xcode.app
Current developer directory is:
/Applications/Xcode.app/Contents/Developer

xcode-select -p is printing /Applications/Xcode.app/Contents/Developer
If /Applications/Xcode.app is Xcode 8, that will not work.

Josephs-Mac:~ joe$ brew config|grep -i xc
Git: 2.13.0 => /Applications/Xcode-beta.app/Contents/Developer/usr/bin/git
Xcode: 9.0 => /Applications/Xcode-beta.app/Contents/Developer
Josephs-Mac:~ joe$ xcode-select -p
/Applications/Xcode-beta.app/Contents/Developer
Josephs-Mac:~ joe$

If Xcode 9 is Xcode-beta.app as it is for me,
sudo xcode-select -s /Applications/Xcode-beta.app/Contents/Developer

@ilovezfs I ran your mv commands, and yes that does fix the issue and I was able to update the formulae.

@jkili cool. And does it also work the other way, when Xcode.app is 8 and Xcode-beta.app is 9, and you've run sudo xcode-select -s /Applications/Xcode-beta.app/Contents/Developer ?

@ilovezfs Yes, that works as well.

Cool. Then it sounds like everything is behaving as intended, and side-by-side Xcode installs are possible.

With Xcode-beta-3, Xcode-beta overwrites Xcode.app.
In order to make brew happy I came down to this horrible solution.

@ilovezfs : in my case, it works bro. thanks

@mjonyh glad to hear it.

`$ xcode-select -p
/Library/Developer/CommandLineTools
$ brew config
HOMEBREW_VERSION: 1.5.4
ORIGIN: https://github.com/Homebrew/brew
HEAD: 021fe22e3c982b08346422d1e7897e929a709380
Last commit: 10 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: e42ae6e44bd6c6b49d9715148d341fb596e9277c
Core tap last commit: 2 hours ago
HOMEBREW_PREFIX: /usr/local
CPU: quad-core 64-bit broadwell
Homebrew Ruby: 2.3.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/bin/ruby
Clang: 9.0 build 900
Git: 2.13.2 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
Perl: /usr/bin/perl
Python: /usr/local/opt/python/libexec/bin/python => /usr/local/Cellar/python/2.7.14/Frameworks/Python.framework/Versions/2.7/bin/python2.7
Ruby: /Users/sarvani/.rvm/rubies/ruby-2.4.1/bin/ruby
Java: 1.8.0_131
macOS: 10.13.1-x86_64
Xcode: 8.3.3
CLT: <IP_ADDRESS>.1.1510905681
X11: N/A
$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected header files:
/usr/local/include/bits/stdc++.h
Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run brew link on these:
libyaml
portaudio
ruby
Warning: Your Xcode (8.3.3) is too outdated.
Please update to Xcode 9.2 (or delete it).
Xcode can be updated from the App Store.
Warning: Your Xcode (8.3.3) is outdated.
Please update to Xcode 9.2 (or delete it).
Xcode can be updated from the App Store.
Warning: Broken symlinks were found. Remove them with brew prune:
/usr/local/etc/bash_completion.d/_brew_services`
I want to install yarn and gave a command brew install yarn
It gave an error like: Error: Your Xcode (8.3.3) is too outdated. Please update to Xcode 9.2 (or delete it). Xcode can be updated from the App Store.
Can you plz help me out.


Adds Unit tests for NativeEngines990KnnVectorsWriter

Had to separate out the common code in NativeEngines990KnnVectorsWriter to make it easy to write tests. Mocking was difficult to do with the functional interfaces and it was throwing NPE in the test especially with the mock of NativeIndexWriter::flush and NativeIndexWriter::merge where it wasn't able to recognize the mocked writer.
Check List

[x] New functionality includes testing.
[x] Commits are signed per the DCO using --signoff.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Please rebase the code to fix the CIs.


How can I change the styling of read messages?

Hi, thank you for your great package. Everything is nice and easy when installing it. Just a simple questions, the unread messages have blue-ish box, and the already read messages have the white font color. How can I change that? Sorry for my noob questions.
Many thanks

div class="media alert alert-success"
alright, i'm getting there.. just a little bit..

Yup, done. Like I said, sorry for my noob question :)
I just do this:
@if ( $thread->userUnreadMessagesCount(Auth::id()) == '0')

@else

@endif
Now I just need to style it as necessary. AdminLTE has some predefined alert styling actually. Nice..
Again, thanks for this great package


Responsive Layout

About styles 🛠
Hi! This is a great starter kit for many projects!
I was wondering how you would achieve responsive column / row layout like Bootstrap provides, for example if I want layout split in 3 columns on desktop to become 1 column layout on mobile.
What would you recommend to achieve responsive composition?

The Grid component is what zeit-ui/vue lacks now, I'll make up for this ASAP.

Thank you @unix! I really appreciate this project and you trying to help!


Fixes the tests by adding missing css file

Also the .gitignore file is updated so the test/node_modules directory is not excluded. This makes it harder to accidently forget including files in test/node_modules.

Sorry, I didn't see the PR :(
It's already fixed in the master branch: https://github.com/jtangelder/sass-loader/commit/3ae649b05dfbee2ca7d9d56cb8c130c1214d6196


Does the env yaml file not works on windows?

I cloned your repo and tried to create env by
conda env create -f lasr.yml
then I got following messages.
Solving environment: failed
ResolvePackageNotFound:
  - lz4-c==1.9.3=h2531618_0
  - cudatoolkit==11.0.221=h6bb024c_0
  - ca-certificates==2021.5.30=ha878542_0
  - openssl==1.1.1k=h27cfd23_0
  - libwebp-base==1.2.0=h27cfd23_0
  - tk==8.6.10=hbc83047_0
  - numpy==1.20.2=py38h2d18471_0
  - sqlite==3.35.4=hdfb4753_0
  - numpy-base==1.20.2=py38hfae3a4d_0
  - jpeg==9b=h024ee3a_2
  - freetype==2.10.4=h5ab3b9f_0
  - intel-openmp==2021.2.0=h06a4308_610
  - mkl_random==1.2.1=py38ha9443f7_2
  - pytorch3d==0.4.0=py38_cu110_pyt171
  - pyyaml==5.3.1=py38h8df0ef7_1
  - zstd==1.4.9=haebb681_0
  - ld_impl_linux-64==2.33.1=h53a641e_7
  - pytorch==1.7.1=py3.8_cuda11.0.221_cudnn8.0.5_0
  - readline==8.1=h27cfd23_0
  - xz==5.2.5=h7b6447c_0
  - libtiff==4.2.0=h85742a9_0
  - lcms2==2.12=h3be6417_0
  - cudatoolkit-dev=11.0.3
  - ncurses==6.2=he6710b0_1
  - zlib==1.2.11=h7b6447c_3
  - mkl_fft==1.3.0=py38h42c9631_2
  - mkl-service==2.3.0=py38h27cfd23_1
  - libgcc-ng=9.1.0
  - libffi==3.3=he6710b0_2
  - libstdcxx-ng==9.1.0=hdf63c60_0

when I delete the build then error disappears, but I'm not sure this is right way.
Is this repo is not compatible with windows?

Nope, the repo is only tested on linux-64. You may need to manually install packages, or use the docker build.


farrah/fix: test workflow

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
6391

Relevant Lines:
6952

💛  - Coveralls


Format all code with latest black version and config

This formats all code files with the latest black version (see https://github.com/quantumlib/Cirq/pull/5157) and options (see https://github.com/quantumlib/Cirq/pull/5170). The main formatting difference from the version bump is to remove whitespace around the ** operator, which generally matches hand-written style and makes precedence more clear. The skip-magic-trailing-comma option makes formatting more deterministic and generally reduces vertical space (here we remove ~6000 lines altogether). Doing this in one commit ensures that logic changes to these modules will not be mixed in with formatting changes. Once this is merged we will add the commit hash to .git-blame-ignore-revs to ensure this doesn't obscure the history as seen by git blame.

Did you check for matrix formatting?  I have a PR in flight that keeps many of the matrix cases formatted in a more readable form.

#5259 has matrix format preserving where I could find it.  I wonder why we have different file counts?

I'm happy to close this and defer to #5259.

Closing in favor of #5259.


Manage action.id_root = ""

Following #942 and #943 , we need to find a way to change/enhance the way we check animation here :
https://github.com/KhronosGroup/glTF-Blender-IO/blob/19665b05a59550dee1aeaf24d548e2ce8477f4ba/addons/io_scene_gltf2/blender/exp/gltf2_blender_gather_animations.py#L51
Seems that id_root is always set to "OBJECT" or "KEY" when creating "by hand" in the UI, but sometimes the field is empty (for example when importing fbx file).
What I am proposing:

Open a bug report for fbx importer
in glTF exporter: Check the value of id_root. If set --> no change regarding the way it's handle for now in master. If id_root is empty, we need an extra search to be able to determinate if the action is an object/armature animation, or if this is a morph animation.

Since __get_blender_actions knows whether each action was found on an object or a shapekey, it could return that piece of data along with the action and track name, and then gather_animations could check that instead of id_root.

Yes, LGTM


TotalProfitAnalysis with SHORT positions

I've been looking into code of TotalProfitAnalysis Analyze.
It looks we have miscalculation for all short positions.

Closing - thanks again for your PR @awsom82


Dividing in python

In python 2
print(35/6)

OUTPUT:
5

In python 3
print(35/6)

OUTPUT:
5.833333333333333

@satwikkansal

This one is a well-known change between Python 2 to Python 3, readers would rather be annoyed if it is included at this stage. Moreover, we might be dropping Python 2 content in the future (see https://github.com/satwikkansal/wtfpython/issues/179).
So closing this due to the above reasons.


fix app search on firefox

Firefox doesn't appear to support .addRule() or .rules on a CSSStyleSheet object (anymore?), so I've added in a check for both of these, and if they don't exist replace them with .insertRule() and .cssRules accordingly.
I also updated the parameters for .insertRule() as they differ to .addRule()
This was breaking the search functionality on the app so here is a quick fix.

Thank you! 🎉🎉