Unable to install and run Phiv3 vision

I've seen several others have issues installing phiv3 vision, but after following the instructions I was unsuccessful so decided to post my situation to solicit guidance.
Running on Windows 11 Laptop with Geforce RTX 3050 Ti Laptop GPU

Nvidia site says it supports CUDA.
I installed CUDA via windows installer

I installed CUDNN via pip install. List of installed packages provided in the pip list output command attached.
list.txt
Validated the following CUDA_PATH

and PATH are set

I installed the genai cuda libraries
pip install onnxruntime-genai-cuda --pre --index-url=https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-genai/pypi/simple/
I have installed the model cuda-fp16

Try running phi3v.py and receive the onnxruntime_genai module could not be found error.
python phi3v.py -m "C:\cuda-fp16\phi-3-v-128k-instruct-vision.onnx"
Traceback (most recent call last):
File "C:\Python312\Lib\site-packages\onnxruntime_genai_init_.py", line 10, in
from onnxruntime_genai.onnxruntime_genai import *
ImportError: DLL load failed while importing onnxruntime_genai: The specified module could not be found.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\BillBaer\OneDrive - Support Partners\projects\cobra\GPT4Video\phi3\phi3v.py", line 12, in
import onnxruntime_genai as og
File "C:\Python312\Lib\site-packages\onnxruntime_genai_init_.py", line 18, in
from onnxruntime_genai.onnxruntime_genai import *
ImportError: DLL load failed while importing onnxruntime_genai: The specified module could not be found.
I went to the python site packages directory for onnxruntime_genai and I don't see the onnxruntime_genai.dll file.

I've tried reinstalling the onnxruntime_genai_cuda multiple times but it does not seem to install that dll.
Appreciate your help in guiding me on what I'm doing wrong?

The problem seems to be the version of cuda you are using. onnxruntime-genai-cuda requires cuda 11.8 and cudnn 8.x for cuda 11.8.
If you would like to use cuda 12, you can install using:
pip install -i https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-cuda-12/pypi/simple/ onnxruntime-genai-cuda

Thank you, bajiumeswani. I went with your suggestion and went back to 11.8 of cuda and 8.x for cudnn. Here is validation of what I have. I first uninstalled cuda 12 and deleted the cudnn files from that install making it fresh.

I copied the files in this archive into the bin, lib and include folders.

I reinstalled the models into c:\cuda-fp16.
Download just the FP16 model
$ huggingface-cli download microsoft/Phi-3-vision-128k-instruct-onnx-cuda --include cuda-fp16/* --local-dir .  --local-dir-use-symlinks False
I reinstalled onnxruntime
pip install --pre onnxruntime-genai-cuda --index-url=https://aiinfra.pkgs.visualstudio.com/PublicPackages/_packaging/onnxruntime-genai/pypi/simple/
Cleaned out the cuda packages installed in pip. Here is my latest list.
pip list.txt
Updated my path

Reinstalled the C++ redistributables just in case.
Wrote a small program to test the onnx package version
import onnxruntime_genai
print(f"onnxruntime version: {onnxruntime_genai.version}")
Here is the output

Tried running phi3v.py again and received load error 126 which looks to have gotten further into the code.

Here is my onnxruntime_genai folder.

Any ideas what this new problem might be?

onnxruntime requires cudnn 8.x for cuda 11.8. Download link: https://developer.nvidia.com/downloads/compute/cudnn/secure/8.9.7/local_installers/11.x/cudnn-windows-x86_64-<IP_ADDRESS>_cuda11-archive.zip/

baijumeswani, thank you for all of your guidance and sorry I still had the wrong cudnn. I had grabbed the most recent archived version for that version, but apparently chose wrong. The script now works so thank you again. All the best. Bill

I installed cuda 11.8 and cudnn <IP_ADDRESS> on windows11 but still not work.


Adding social previews

This adds social media previews via the sphinx-social-previews extension.
The extension is still in the works so this is installing from main. I think that should be OK since we control it, I mostly wanted to dogfood this on our sites to see how it looks. It shouldn't be disruptive at all from our perspective.
Here's how it'll work:

By default, it activates the sphinxext.opengraph extension and will add an image to each page by default
By default, it'll include a base 2i2c logo image and will use the site's metadata to generate a card
Any sphinxext.opengraph configuration will override the default behavior

Here's an example of how it looks:

This one is kind-of out of left field, but I thought this would be a nice way to dogfood the social media preview stuff. If we merge this, it means the next time we build our documentation then we'll start auto-generating opengraph images that'll display in social media previews.

This one is kind-of out of left field, but I thought this would be a nice way to dogfood the social media preview stuff. If we merge this, it means the next time we build our documentation then we'll start auto-generating opengraph images that'll display in social media previews.

I think this is a nice idea to experiment with, and I trust you on the implementation side (from a high-level overview, LGTM).

OK, I'll merge this one in and see if it works in our repositories :-)


In dark theme, endpoint scrollbar is too glaring

The scrollbar for the endpoints is very bright and attracts a lot of attention. On the other hand, the scroll bar on the right-side for the clusters table is much less intrusive.
They should look the same.

The scrollbar is also covering the blue boundary around the selected endpoint.

REviewing this and I still see the same thing with the scroll bar, it is as though it is from the light theme.

Both Timotej and myself are not able to see this as corrected. I'm moving this back to To Do, something different needs to be done here because we both still see the glaring white scroll bar on Linux and Mac. Thanks


[Failing Test]: JS2PY not supporting Python 3.12

What happened?
Beam YAML added added a dependency on js2py library:
https://github.com/apache/beam/blob/eb5c73da86f87d65109ca84e917fdaaeb61f7cf1/sdks/python/apache_beam/yaml/yaml_mapping.py#L34
It currently doesn't work for Python 3.12:

https://github.com/PiotrDabkowski/Js2Py/issues/282#issuecomment-1327954348
https://github.com/PiotrDabkowski/Js2Py/issues/317

This means that YAML functionality might not be available in Python 3.12 until the issue is resolved. It seems that there has been no releases to Js2Py since 2022.
How critical is this dependency for Beam YAML? @Polber would you have time to investigate whether this dependency is still required and/or work with Js2Py maintainers on adding Python 3.12 support?
Thanks!
To repro,  we need to make some patches to Beam repo like ones in #30828, create a py3.12 envrionment, run:
(py312) :python$ pytest apache_beam/yaml/programming_guide_test.py
=========================================================== test session starts ============================================================
platform linux -- Python 3.12.2, pytest-7.4.4, pluggy-1.4.0
rootdir: /home/valentyn/projects/beam/beam/beam/sdks/python
configfile: pytest.ini
plugins: xdist-3.5.0, requests-mock-1.12.1, timeout-2.3.1, hypothesis-6.100.0
timeout: 600.0s
timeout method: signal
timeout func_only: False
collected 0 items / 1 error

================================================================== ERRORS ==================================================================
_______________________________________ ERROR collecting apache_beam/yaml/programming_guide_test.py ________________________________________
/home/valentyn/.pyenv/versions/3.12.2/lib/python3.12/importlib/__init__.py:90: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
<frozen importlib._bootstrap>:1387: in _gcd_import
    ???
<frozen importlib._bootstrap>:1360: in _find_and_load
    ???
<frozen importlib._bootstrap>:1310: in _find_and_load_unlocked
    ???
<frozen importlib._bootstrap>:488: in _call_with_frames_removed
    ???
<frozen importlib._bootstrap>:1387: in _gcd_import
    ???
<frozen importlib._bootstrap>:1360: in _find_and_load
    ???
<frozen importlib._bootstrap>:1331: in _find_and_load_unlocked
    ???
<frozen importlib._bootstrap>:935: in _load_unlocked
    ???
<frozen importlib._bootstrap_external>:995: in exec_module
    ???
<frozen importlib._bootstrap>:488: in _call_with_frames_removed
    ???
apache_beam/yaml/__init__.py:18: in <module>
    from apache_beam.yaml.yaml_transform import *
apache_beam/yaml/yaml_transform.py:39: in <module>
    from apache_beam.yaml.yaml_combine import normalize_combine
apache_beam/yaml/yaml_combine.py:33: in <module>
    from apache_beam.yaml import yaml_mapping
apache_beam/yaml/yaml_mapping.py:34: in <module>
    import js2py
/home/valentyn/.pyenv/versions/3.12.2/envs/py312/lib/python3.12/site-packages/js2py/__init__.py:72: in <module>
    from .base import PyJsException
/home/valentyn/.pyenv/versions/3.12.2/envs/py312/lib/python3.12/site-packages/js2py/base.py:2965: in <module>
    @Js
/home/valentyn/.pyenv/versions/3.12.2/envs/py312/lib/python3.12/site-packages/js2py/base.py:165: in Js
    return PyJsFunction(val, FunctionPrototype)
/home/valentyn/.pyenv/versions/3.12.2/envs/py312/lib/python3.12/site-packages/js2py/base.py:1377: in __init__
    cand = fix_js_args(func)
/home/valentyn/.pyenv/versions/3.12.2/envs/py312/lib/python3.12/site-packages/js2py/utils/injector.py:27: in fix_js_args
    code = append_arguments(six.get_function_code(func), ('this', 'arguments'))
/home/valentyn/.pyenv/versions/3.12.2/envs/py312/lib/python3.12/site-packages/js2py/utils/injector.py:121: in append_arguments
    arg = name_translations[inst.arg]
E   KeyError: 3
============================================================= warnings summary =============================================================
apache_beam/__init__.py:74
  /home/valentyn/projects/beam/beam/beam/sdks/python/apache_beam/__init__.py:74: UserWarning: This version of Apache Beam has not been sufficiently tested on Python 3.12. You may encounter bugs or missing features.
    warnings.warn(

<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: Type google._upb._message.MessageMapContainer uses PyType_Spec with a metaclass that has custom tp_new. This is deprecated and will no longer be allowed in Python 3.14.

<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: Type google._upb._message.ScalarMapContainer uses PyType_Spec with a metaclass that has custom tp_new. This is deprecated and will no longer be allowed in Python 3.14.

../../../../../../.pyenv/versions/3.12.2/envs/py312/lib/python3.12/site-packages/js2py/utils/injector.py:141
  /home/valentyn/.pyenv/versions/3.12.2/envs/py312/lib/python3.12/site-packages/js2py/utils/injector.py:141: DeprecationWarning: co_lnotab is deprecated, use co_lines instead.
    code_obj.co_firstlineno, code_obj.co_lnotab,

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
========================================================= short test summary info ==========================================================
ERROR apache_beam/yaml/programming_guide_test.py - KeyError: 3

Issue Failure
Failure: Test is continually failing
Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

There are actually some known performance issues with that library that were recently discovered after running some load tests. I was planning on revisiting and possibly using a different library/solution for JavaScript UDF's. It was safeguarded by marking as "experimental" so I see no reason in disabling the feature for the time being.

That makes sense to me. I added that logic in: https://github.com/apache/beam/pull/30843


Vulkan: Support for Capture without vkQueuePresentKHR

Description
When there is no window, or when there is a window but no vkQueuePresentKHR call is made, renderdoc discards the capture as if nothing ran.
This is a request to add support for capturing and replaying whatever was vkQueueSubmited to the GPU even if there is no terminating vkQueuePresentKHR.
I noticed this in two cases:

A window is made, some work is done on a swapchain image and the results read back on the CPU. This involved vkQueueSubmit and vkQueueWaitIdle, but not vkQueuePresentKHR. Renderdoc didn't create a capture to be replayed. I worked around this by doing an unnecessary present)
No window is made, all work is done on off-screen VkImages. Renderdoc didn't create a capture. There's no workaround (unless a window is created for no reason).

Repro steps
Record a command buffer, vkQueueSubmit it and terminate the application without presenting.
Environment

RenderDoc build: 26d823905
Operating System: Linux
API: Vulkan
GPU: Intel, Mesa 18.0.3

Just to clarify: You say that RenderDoc 'discards' the capture when there's no window, but rather it's just not possible to make a capture using the default process since it is indeed default based around delimiting frames by window presents.
For headless programs that don't have a those default frame boundaries you can use the in-application API which RenderDoc provides. This is also useful even when your application does have a window, if some work outside of a normal frame e.g. to cache or bake some results.
The API allows you to start and stop the capture at a time of your choosing to define the boundaries of the 'frame'. When there's only one graphics device present you can call StartFrameCapture(NULL, NULL) and EndFrameCapture(NULL, NULL).

Just to clarify: You say that RenderDoc 'discards' the capture when there's no window, but rather it's just not possible to make a capture using the default process since it is indeed default based around delimiting frames by window presents.

Yes, I guessed this (as the captured frames are clearly separated at present calls). This issue is a request to actually add support for such a use case. I suspect this issue affects situations like this too:

Render, present, repeat
Render, terminate

With the last bit of rendering not getting captured by RenderDoc. The issue is likely not too difficult to resolve. Instead of "saving" each frame when "present" is seen, RenderDoc can do it when either "present" is seen or the device is destroyed. That would automatically support all these use cases.

It feels like there's still a miscommunication or misunderstanding here. RenderDoc does not capture every frame in the application when a present is seen, it only captures specific frames when prompted - either by a keypress, a trigger from the UI either immediately or delayed - using presents to mark the boundaries. Alternatively the API linked previously can be used to start and stop a capture at any time.
If you don't have the delimiter of presents to a window then I don't think there's a good way to know how to subdivide the work and determine which subsets should be captured as a 'frame' or not. That's why I recommend in this case that you use the API to determine exactly what should be included in what you want to capture.
If I understand your suggestion to be treating each vkQueueSubmit as an individual 'frame' in this case that is not going to be desirable in many cases since there are typically multiple submits in one 'unit' of work. Though again if an application isn't presenting to a window it's very hard to reason about what is a meaningful unit of work at all, hence why it's better to leave it up to the user to define.
Yes you would also get into difficulty if you triggered a frame capture relying on the implicit present boundaries, and then destroyed the device mid-way through the frame. If a user wanted to capture that final frame then they would also be best using the API as well.

First, I am now capturing through the API just fine.
My suggestion wasn't to treat each vkQueueSubmit as an individual frame though. It was to threat vkDestoryDevice as a frame delimiter too. The work is still subdivided into frames by present calls, except the trailing work before a device destory is captured into one final frame. Does that make sense?

If you don't have any present calls in the frame, as described in your original post, then treating vkDestroyDevice as a frame delimiter to end any final frame capture won't help since there's nothing to start the capture in the first place.
If you're talking about a case where you do have window presents then it's different to what you originally described. It seems like you're asking about a hypothetical case and not something you've actually run into.
It's a pretty obscure edge case and it can already be solved by the user using the API to define the capture for the final frame before destroying their device.

Let's focus on the case without window. Wouldn't selecting Queue Capture with Frame 0 already start the capture right at the beginning? vkDestroyDevice would end that and voila, one frame with all the commands!

That would capture the entire application's work for however long it runs which is definitely not desired.
Queuing a capture of frame 0 is undefined when the application has no frames. As with many other examples you could construct where there's no easily delimited frame, it is easier and more reliable to have the user define what their workload boundary is rather than trying to automatically guess it and exposing sharp edges and pitfalls.
It sounds like you want to abuse RenderDoc to capture the work of an entire application. That is not its purpose nor an intended use, though of course if you really want to you can use the API to capture as much as you want. This is also far off-topic from the original question which was how to capture work when there are no window present operations - to which the simple answer is that you can use the RenderDoc API to define the bounds and you've already said that works well for you.

I would be fine if your answer is "I don't feel like doing it", but your reasoning is not exactly great.

That would capture the entire application's work for however long it runs which is definitely not desired.

Not definitely. I did just ask for it, so there is desire by some.
I will be keeping the commit that adds renderdoc API capture lying around, but it would have been far more convenient if the capture just worked in renderdoc itself.

Queuing a capture of frame 0 is undefined when the application has no frames.

Undefined by who? It can be very well defined if you want it. To me, "Queuing a capture from frame 0" would mean capture whatever comes after vkCreateDevice.

It sounds like you want to abuse RenderDoc to capture the work of an entire application.

If the application is a conformance test that runs for a short time, why would capturing the entire application be an abuse?

That is not its purpose nor an intended use, though of course if you really want to you can use the API to capture as much as you want.

I think you just answered yourself here. Also, I didn't notice anywhere RenderDoc saying it's intended for capturing window-based workloads only. In fact, the task is already doable with the API, it's just the UI that's missing a feature.

This is also far off-topic from the original question which was how to capture work when there are no window present operations.

Nope, the original issue was "a request to add support for capturing and replaying whatever was vkQueueSubmited to the GPU even if there is no terminating vkQueuePresentKHR".

You could end this discussion with "I don't want to do it, do it yourself if you really care" which I think is more reasonable.

I'm trying to debug some conformance tests. These tests don't generate traditional frames and are pretty short. Would be really nice if RenderDoc could capture everything from CreateIntance or CreateDevice to the corresponding Destroy.

Capture all of an entire application's work from start to finish is explicitly not a goal of RenderDoc.
As mentioned above if you want to capture a section of work that's not delimited by frame boundaries you can use the RenderDoc API to start and stop the capture at any time. I know at least that the vulkan conformance tests do exactly that.
Please don't comment on closed issues, if there is still a bug or a new request then you can open a new issue.


Subject can´t emit changes in callback

I am not sure if is an nativescript-sockeio error or a Nativescript error. For example:
    this..ws.on("new", (response) => {

      this._list= response.list;
     this._listSubjet$.next(this._list);

    });

what platform are you using ?

@triniwiz
More information:
    "tns-android": {
      "version": "2.1.1"
    }
  },
  "dependencies": {
    "@angular/common": "2.0.0-rc.3",
    "@angular/compiler": "2.0.0-rc.3",
    "@angular/core": "2.0.0-rc.3",
    "@angular/http": "2.0.0-rc.3",
    "@angular/platform-browser": "2.0.0-rc.3",
    "@angular/platform-browser-dynamic": "2.0.0-rc.3",
    "@angular/platform-server": "2.0.0-rc.3",
    "@angular/router": "3.0.0-alpha.7",
    "email-validator": "1.0.4",
    "nativescript-angular": "0.2.0",
    "nativescript-social-share": "1.2.0",
    "nativescript-socketio": "^2.1.2",
    "tns-core-modules": "2.1.0"
  },

Nativescript + Angular2 RC.3. I am using Observables and Observers but with Subject. I have a service to request server for information. In the other hand, that service uses a WebSocket to recieve more information.

 private _woList$: Subject<WO[]>;
  private _woList: WO[];

  constructor(private httpService: HttpService, private socketService: SocketService) {
    this._woList$ = new Subject<WO[]>();
  }

  public get woList$() {
    return this._woList$.asObservable();
  }

  public readMany(callBack?) {
    this.httpService.get("ots/?expand=ot,materials,tools,username", callBack || (response => {
      this._woList = response.ots;
      this.emitChanges();
    }));
  }
   emitChanges() {
    this._woList$.next(this._woList);
  }

  public listenSocketEvents() {
    this.socketService.ws.on("newWO", (wo) => {
      this.readMany();
    });
  }

wo.component.ts

  public ngOnInit() {
    this.woList = this.wotService.woList$;
  }

Well, if a button has a tap event witch execute emitChanges(), it works nice. And the httpService.get callback workd nice too. But it does not work in callback of socket.
I don´t know if is a Nativescript issue or not.

Your use of the plugin is pretty simple and should work... We'd need a better description of the problem you're going through. Sounds like a lot of different breakdowns could be happening including your socket server not emitting to the socket.

Thanks @db3dev
Server is emitting. I am using a Android Emulator but now I am going to try it in a device. It´s very strange. Now my code is following:
    this.woService.woList$.subscribe(m => {
      console.log("List size before: " + this.woList.length)
      this.woList = m;
      console.log("List size after: " + this.woList.length)
    },
      error => {
        console.log(error);
      });

Server emit a newWO event and it arrives to front. woList$ emits a change and console.log is working but. I can see:
List size before:  0
List size after: 1  (this one is the new one emitted by socket)
but screen does not show changes.
For this reason it´s probably a Nativescript issue, not a nativescript-socketio one.

If the data is updating and you're not seeing it changed then in your view it may actually be more along the lines of angular. I'd recommend checking out your subscription and see if it is managing the change properly.

I'd recommend checking into your angular bindings and how you're rendering the view.


Fixed not appearing landscape image.

This PR fixes #26
The problem was arising due to a missing statement in line 82.

This doc will be hosted in prod. So changing it directly to localhost:3000 will break it. It will not work on the web. Closing.

I am sorry what i meant to say was between localhost & VS code live server.
The landscape image doesn't appears in vs code live server and I am certain it's because of
landscape image tag code for image
Line 82

square image tag code
Line 90

It still works my side 🤔 I still can't figure out how it's not working your side. Can you record a video and send over discord?


TeXstudio crashes on open file dialog

Issue description
TeXstudio 2.12.20 crashes whenever I try to access the open file dialog.  The terminal output is:
(texstudio:19954): GLib-GIO-ERROR **: 11:08:09.532: Settings schema
'org.gtk.Settings.FileChooser' does not contain a key named 'show-type-column'
Trace/breakpoint trap

My desktop manager is MATE 1.22.1.
Steps to reproduce
Open TeXstudio.  Click File -> Open.  TeXstudio crashes.
Technical details

system: "x86_64-linux"
host os: Linux 4.19.44, NixOS, 19.09pre180443.4dd5c93998d (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2
channels(root): "nixos-20.03pre211190.a21c2fa3ea2"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

I can't reproduce this on 2.12.20 or 2.12.22, but I run KDE, so that might be a factor.
Do you experience similar problems with other QT apps?

Not as far as I can tell.  I just tried SMPlayer and Media Player Classic Qute Theater, both of which seem to use QT, and was able to access the open file dialog in each.

Hello,
I don't know if you'll still be getting updates on this issue but I found the same problem in TexStudio 3.0.1 running on Gnome in a different distro (Manjaro).
What fixed it for me was to force TexStudio to not use the Gnome file dialog. I went to .config/texstudio/texstudio.ini and changed the line
Files\Use%20Native%20File%20Dialog=true to
Files\Use%20Native%20File%20Dialog=false.
It is a bit unfortunate as I prefer Gnome's dialog over TexStudio's default one, but it did the trick. I haven't had this issue with any other Qt5 apps. I would bet this is a TexStudio bug and not a distro-specific one (but I honestly don't know).

Thanks, I am now on MATE 1.24.0, and can no longer reproduce the issue.  I still have TeXstudio 2.12.20.

Here is a solution that worked for me:
https://discourse.nixos.org/t/firefox-crashes-when-opening-a-file-dialog/5323/13

Works env -i HOME="$HOME" DISPLAY="$DISPLAY" WAYLAND_DISPLAY="$WAYLAND_DISPLAY" XDG_RUNTIME_DIR="$XDG_RUNTIME_DIR" ./result/bin/texstudio


NullPointerException when LZ4Factory is loaded by bootstrap class loader

At https://github.com/jpountz/lz4-java/blob/aef24cfbbf53d6ade60073b287edc610be743e43/src/java/net/jpountz/lz4/LZ4Factory.java#L149, LZ4Factory.class.getClassLoader() might return null if LZ4Factory is loaded by the bootstrap class loader. It results in a NPE.
LZ4Factory is loaded by the bootstrap class loader in my application because I am using lz4 in a Java agent and this Java agent is loaded by the bootstrap class loader.

+1

Closing as I merged https://github.com/jpountz/lz4-java/pull/60


TryGetDestination error

Please refer the below issue for the context
https://github.com/SAP/cloud-sdk-java/issues/482

Hi Team,
We have tried tweaking the timelimiter , have added 30sec. Still the issue is giving timeout error.
Regards
Akash

Closing this issue as I have re-opened https://github.com/SAP/cloud-sdk-java/issues/482.


extent4_type required?

Hi,
Error I received after using BIDS2NDA to generate image03:
Field extent4_type is conditionally required when image_num_dimensions > 3
Field map scans with 2 encoding directions (AP/PA) are currently missed.

Those field maps should be split into 3D files. One file per encoding direction.

Ah - I had 4 volumes for each direction, I will split those up then

FYI - I tried to clear up the language describing the phase encoding fieldmaps in the spec. Please have a look: https://docs.google.com/document/d/1HFUkAEE-pB-angVcYe6pf_-fVf4sCpOHKesUvfb8Grc/edit#heading=h.fcegd01wpsf8

correct link: https://docs.google.com/document/d/1HFUkAEE-pB-angVcYe6pf_-fVf4sCpOHKesUvfb8Grc/edit#heading=h.6gef31kvsx0l


Respect the newline style of existing changelog files

This patch updates scriv to follow the newline style of existing changelog files.
If no changelog file exists, scriv will fallback to Python's universal newline support so new files are created with the platform's default newline style.
Please let me know if you have any suggestions or want something done a different way.

Thanks! :)


Use #blank? to check for Github key in estimate_skills

In this PR, I've switched the check on ENV['GITHUB_KEY'] from .empty? to Rails' .blank? method, which returns true on both empty string and nil. Fixes #1592. Seeding the DB now works without setting a GitHub key.
While testing, I also came across a rogue object that looks like it might have been copied by accident from a puts or something, so I've deleted that.

Lovely work!


get-childitem with -recurse and -file won't recurse on wildcard match

Steps to reproduce
Have a folder that has another folder, and that folder having a file.
\foo
\foo\bar
\foo\bar\foo bar.txt
Try to use the following to find the TXT file.
get-childitem -file '\foo\*a*' -recurse

Expected behavior
an object returned that contains foo bar.txt
This is expected because -file should only restrict the output, not the input
Actual behavior
no object is instead returned
It appears that the input wildcard path is being filtered by -file before -recurse can occur.  If at least one file matches, then the recursion will occur.  So now create file \foo\bar.txt, and the expected behavior will occur, but also \foo\bar.txt also appears in the result object (it does match the wildcard).
Now add \foo\foo and copy \foo\bar.txt to \foo\foo.  This location of the file will also be included, indicating that the wildcard in the path is only restricting the output, not the available folders in recursion.  Remove \foo\bar.txt and the problem returns of no output.
I am considering this an issue as it relates to the fact that path input to Get-ChildItem could have been supplied by someone less familiar with PowerShell and Get-ChildItem, as they were provided the script, or the script simply provides a prompt.  It otherwise works fine if wildcards are not included in -path, but instead in -filter or -include.
Environment data
> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.3
PSEdition                      Core
GitCommitId                    v6.0.3
OS                             Microsoft Windows 10.0.17134
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

I ran in to this, because I was trying to get a listing of all files without an extension:
dir *. -file
doesn't work.  CMD 'dir /a-d *.' recognizes this as get only files without extensions.  However I did catch it find a file '.sou', or other files and folders that start with a '.' and don't have any additional '.'s.
dir -file -filter *.
does work as did this:
dir .\* -file -exclude *.*
if you just try:
dir *.
it works except it includes directories.

I think this is a related issue. The -File and -Exclude parameters don't work when used together.
Count of files without any exclusions
PS C:\Program Files\PowerShell\6.0.4> (Get-ChildItem).count
389
Count of files when excluding pwsh.exe
PS C:\Program Files\PowerShell\6.0.4> (Get-ChildItem -Exclude pwsh.exe).count
388
Count of files when excluding pwsh.exe and only listing files
PS C:\Program Files\PowerShell\6.0.4> (Get-ChildItem -Exclude pwsh.exe -file).count
0

Dup #9014


Enhance find command capabilities

Also do ensure that your code passes checkstyle tests (both in main and test).


Compilation Error Error: 2 arguments required, but only 1 was passed.

ERROR:
Compilation Error Error: 2 arguments required, but only 1 was passed.
What should be the error here, otherwise this also worked in the past ?
// * Converts a pixel value to rem, relative to the body font size (or any other value).
// *
// * Usage:
// * font-size:rem(12px) (if based on body font size)
// * font-size:rem(12px, 18px) (if based on a parent with a relativ font size of 18px)
// *
// * @param  {string} $to-size   Target pixel value
// * @param  {string} $from-size: $base-font-size (optional) Font size of the parent
// * @return {string}           Calculated rem value
@function rem($to-size, $from-size: $base-font-size) {
  @if $to-size == 0px { @return 0 }
  @return $to-size / $from-size * 1rem;
}

max-width: rem($rowMaxWidth);

SASS made change in v1.65 to allow new, currently experimental, functions to be parsed as valid CSS. Segment copied below, for reference

1.65.0

All functions defined in CSS Values and Units 4 are now parsed as calculation
objects: round(), mod(), rem(), sin(), cos(), tan(), asin(), acos(), atan(), atan2(), pow(), sqrt(), hypot(), log(), exp(), abs(), and sign().

Deprecate explicitly passing......

As you can see rem() is one of these. It's a function that gives you the remainder of two divisible numbers.
You will need to rename your function to something else, maybe asRem(), to remove the error
Hope this helps 😁

UPDATE: SASS released v1.65 which rolled back support for CSS Units and Values 4 as it caused an unintentional breaking change (as was the case with this issue). The extension was patched in v6.1.1 to reflect this. Support will be coming back but not before proper deprecation warning have been in place for at least 3 months

Closing as fixed in V6.1.1

Hey, many thanks for your quick reply, I set the extension to the penultimate version on the same day so that I could continue working quickly. I had also looked into it shortly after and read that it was the latest version of SASS itself, but it sounds like good news!


[FR] Ubuntu Docker image lacks package necessary for FiftyOne to work out-of-the-box

A user reported that the standard Ubuntu docker image lacks a key package to support FiftyOne. It should be easy enough to discover what package this is and provide a fix/documentation for the issue.

Got this on a fresh install under ubuntu:latest (which is 20.04; haven't tested 18.04):
/usr/local/lib/python3.8/dist-packages/fiftyone/db/bin/mongod: failed to launch (code 127): /usr/local/lib/python3.8/dist-packages/fiftyone/db/bin/mongod: error while loading shared libraries: libcurl.so.4: cannot open shared object file: No such file or directory
Some distros' docker images already come with libcurl, but some need it (for examples, see the dockerfiles here - note that they were intended for minimal packaging tests and would not be ready for users). I'm a bit hesitant to add libcurl as a dependency to the installation instructions because the user-facing versions of most distros already have it. Maybe it could go on the troubleshooting page.
A proper docker image has been requested before, and once ready, it would be simpler to point to it than to update the installation docs with problems that only docker image users encounter. There are some obstacles to that, e.g. figuring out what to recommend for using the app in docker.


Add a histogram_quantiles function

We often calculate 3 quantiles for our metrics, 0.5, 0.9 and 0.99. Instead of having to duplicate definitions and metric evaluations, it'd be beneficial to have a variadic function to calculate all at once. That would save operations in rule evaluations.
histgram_quantiles(<vector>, ...<quantile>)

I'm still open to add variadic arguments.
This of course reverses our regular argument order, which is not exactly intuitive.
This in itself won't be usable since histogram_quantiles doesn't attach a quantile label to the result metrics or similar.
So you couldn't differentiate between the different quantiles in your result.

This function would generate one timeseries with a label {quantile="<quantile>"} for each of the <quantile> arguments.

We could go even further and default to 0.5,0.9,0.99 to match summaries.

I'm not sure about this.
Duplication in rules files isn't an argument, as that can be handled by configuration management. It'd also be the first function to return multiple results, which seems a bit messy to me.

I had the discussion about quantile labels with @beorn7 in the past.
I wanted to assign them in recording rules to be symmetric with summaries. Apparently there has been a discussion a long time ago that the label was a mistake in the first plat. The argument being, that every label should be meaningful to aggregate over.

Indeed. I Find the {quantile="..."} label highly problematic. It's handy to plot multiple quantile graphs, but semantically, it would make more sense to have them in the label name (e.g. job:request_duration_seconds:median, job:request_duration_seconds:99perc).
Similar to @brian-brazil , I don't really have a problem with duplication in rules. We have that anyway, and deliberately.
I can see the argument of saving computational resources, but I'd only take that as a last resort. We had problems with rule evaluation times in the past (especially when it came to histograms), but with 0.18, that's pretty much solved (and further improvements are still possible with time-based indices).
As a more general note, I believe many users calculate quantiles in situations where they really want something like "percent of queries served within 100ms" (or an Apdex score, which is very similar). Those numbers are way more naturally to calculate with Prometheus, and often more meaningful. I assume that the love for quantiles comes from a history where quantiles were more naturally to compute than an Apdex score. Rather than making in easy to mass-calculate quantiles, I'd first like to encourage people to think if they really want a quantile.

You're right. I got so used to our quantile labels that it never occurred to me that they violate our label guideline.

@beorn7 by now I agree that it's better off in the name.
Since client_golang will experience breaking changes, would it make sense to switch summaries from the label to the :99perc suffix?
I realize that's quite invasive. But most other clients don't even have client-side percentiles so it wouldn't cause too much friction across languages.

:99perc suffix

Colons should only really be added when aggregating, as we don't know the relevant aggregation levels down in instrumentation. _99p or something would be better.

The quantile labels are everywhere. They are essentially the way we flatten the complex "summary" metric type into individual time series:

See summary representation of the text format.
See how the Prometheus server breaks down a summary into time series.

So we needed to change many places. The "proper" solution would be to make complex metric types like "summary" and "histogram" first class citizens (and make the flattening into elementary time series an internal implementation detail).


changed the coordinates according to the pom file details

This part is done for maven in [1]
[1] https://github.com/jeremylong/DependencyCheck/issues/665


replace remaining asserts

Replace torch._asserts as a follow up to this PR https://github.com/pytorch/vision/pull/5587
Thanks @datumbox for raising it in https://github.com/pytorch/vision/issues/5494

tests are failing because of this change: https://github.com/pytorch/vision/pull/5636/files#diff-678e419692ae76586d9f58ce62d2841be82d607637b7d507ead76eca412fcdd1R244
I am thinking to revert and leave this particular torch._assert because its traceable.
@NicolasHug do you know if I have other options here?

Sorry, I thought I had replied to this comment but it looks like I didn't :man_facepalming:
I don't know if there is a good workaround for this. But I'm surprised that we did not encouter the same error for the changes we did in https://github.com/pytorch/vision/pull/5587. Do you know why that might be the case?

I had a very quick look on https://github.com/pytorch/vision/pull/5587 and I think it works because all of our Exceptions are either on utils/methods that are not part of the models or on model constructors. I agree with jdgomes that we should probably close the PR and leave the assertions as is.

Looks like even in https://github.com/pytorch/vision/pull/5587 there were a bunch of changes made to the forward pass of e.g. RAFT, but it looks like we don't test RAFT against fx

Abandoning this PR and will follow up with another PR reverting some of the recent exceptions added after the offline discussion with @datumbox


Fixes bug with insufficient nil check on joining ziplines

What was going wrong?
There was improper nil checking in the code for joining a zipline at the ForwardDirection and BackwardsDirection table values. This meant at times the player could try to move onto a non existent power line which caused the game to crash.

Makes sense to me, nice find 👍


Generate Github releases automatically.

This change uses the name format that nginx install will expect (so feedback on the naming is welcome too.)
CircleCI does not allow "." in an executor name, although this not as far as I can tell a restriction on YAML keys in general.

I expect there is probably some bug that will show up when we try to actually cut a release in the release branch.  :(

The PR for the akita-cli side is https://github.com/akitasoftware/akita-cli/pull/198
I think probably in the long run we will want to have a script in this repository that generates the correct name for the binary?  I think this convention will be OK for now.


Strip Meta Data seems to do nothing

magick-wasm version
^0.0.26
Description
Im trying to remove meta data such as copyright information from AVIF files but still appears despite adding strip.
Steps to Reproduce
                     ImageMagick.read(image_data, async (img) => {
                        img.quality = 75;
                        img.format = "AVIF";

                        // strip all meta data
                        img.settings.setDefine(MagickFormat.Heic, "strip");

                       img.write((data) => {
                           // encode still has pointlees meta data
                        });

                 });

Images
No response

Yes this worked, seems like all information is removed.


Upgrade Bloom Frontend to Node 17

Overview
We would like to upgrade Bloom-frontend to Node 17 as a step to the latest. There is likely to be dependency issues as part of this change so it will require a bit of time.
Action Items

[ ] Create a branch from develop
[ ] Have a look through the code and see all the places where the Node version is specified. I will list some but perhaps not all examples below.
[ ] Update node version locally and try and install packages and run the application. You will probably encounter some errors which you will need to fix.
[ ] Update ReadMe to specify Node version
[ ] Update github actions to use newer version
[ ] Commit and Push and tag @kyleecodes and @eleanorreem

Resources/Instructions

https://medium.com/the-node-js-collection/node-js-17-is-here-8dba1e14e382
https://blog.appsignal.com/2021/10/27/what-s-new-in-nodejs-17.html

Hi!
If no one's taken this up, I can try and take a run at it!
Thanks!

@DustyDogCodex issue assigned.
Thank you!

Hi @kyleecodes ,
Hope you are enjoying your Friday!
I am currently working on this issue and I wanted to know if there is a specific version of Node17 you want me to install? Currently I have node v17.9.1 installed for this project, which was the last major update to node 17. Please let me know if you would like me to switch to a different version.
Thanks!

@DustyDogCodex Yes, that node 17 version works! You may need to change to other node 17 versions depending on other dependencies, but overall the last updated full release is preferred.
Also, I want to note that this issue may not be possible without more significant code changes, so if needed I'll monitor to split this up into more issues and take on some of those code changes myself.
As for Cypress, yes, you may update or rollback any other dependencies like Cypress as needed.
Thanks again and happy hacking!

@DustyDogCodex - thanks for your efforts so far! Just to let you know - I am doing a Nextjs Update to 13.5.4 which is now on develop. This update might impact this. Hopefully not! Just incase, ensure you have pulled the most recent develop to ensure you have the most recent package.json.

@DustyDogCodex you bring up a great point, thanks.
We are looking into this now, thank you for your patience. I will comment here and tag you ASAP with updates. Meanwhile, are you able to share more details about the error / screenshots?

Hi @kyleecodes ,
Hope you are enjoying your Friday :)
Here is a screenshot of the 401 error I get. Additionally I've also added the error message I received in my terminal. All of these were received when I start up the porject and run it on localhost:3000.

Error 1

Error: Request failed with status code 401
    at createError (C:\Users\varun\OneDrive\Documents\OS Forks\bloom-frontend\node_modules\axios\lib\core\createError.js:16:15)
    at settle (C:\Users\varun\OneDrive\Documents\OS Forks\bloom-frontend\node_modules\axios\lib\core\settle.js:17:12)
    at IncomingMessage.handleStreamEnd (C:\Users\varun\OneDrive\Documents\OS Forks\bloom-frontend\node_modules\axios\lib\adapters\http.js:293:11)
    at IncomingMessage.emit (node:events:539:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'Error',
  config: {
    transitional: {
      silentJSONParsing: true,
      forcedJSONParsing: true,
      clarifyTimeoutError: false
    },
    transformRequest: [ null ],
    transformResponse: [ null ],
    timeout: 0,
    xsrfCookieName: 'XSRF-TOKEN',
    xsrfHeaderName: 'X-XSRF-TOKEN',
    maxContentLength: -1,
    maxBodyLength: -1,
    headers: {
      Accept: 'application/json, text/plain, */*',
      'User-Agent': 'axios/0.24.0'
    },
    baseURL: 'https://api.storyblok.com/v2',
    proxy: false,
    params: { version: 'published', token: '' },
    method: 'get',
    url: '/cdn/links/'
  },
  status: 401,
  page: '/444.js'
}

Error 2

Error: Request failed with status code 401
    at createError (C:\Users\varun\OneDrive\Documents\OS Forks\bloom-frontend\node_modules\axios\lib\core\createError.js:16:15)
    at settle (C:\Users\varun\OneDrive\Documents\OS Forks\bloom-frontend\node_modules\axios\lib\core\settle.js:17:12)
    at IncomingMessage.handleStreamEnd (C:\Users\varun\OneDrive\Documents\OS Forks\bloom-frontend\node_modules\axios\lib\adapters\http.js:293:11)
    at IncomingMessage.emit (node:events:539:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  config: {
    transitional: {
      silentJSONParsing: true,
      forcedJSONParsing: true,
      clarifyTimeoutError: false
    },
    adapter: [Function: httpAdapter],
    transformRequest: [ [Function: transformRequest] ],
    transformResponse: [ [Function: transformResponse] ],
    timeout: 0,
    xsrfCookieName: 'XSRF-TOKEN',
    xsrfHeaderName: 'X-XSRF-TOKEN',
    maxContentLength: -1,
    maxBodyLength: -1,
    validateStatus: [Function: validateStatus],
    headers: {
      Accept: 'application/json, text/plain, */*',
      'User-Agent': 'axios/0.24.0'
    },
    baseURL: 'https://api.storyblok.com/v2',
    proxy: false,
    params: { version: 'published', language: 'en', token: '', cv: undefined },
    paramsSerializer: [Function: paramsSerializer],
    method: 'get',
    url: '/cdn/stories/home',
    data: undefined
  },
  request: <ref *1> ClientRequest {
    _events: [Object: null prototype] {
      abort: [Function (anonymous)],
      aborted: [Function (anonymous)],
      connect: [Function (anonymous)],
      error: [Function (anonymous)],
      socket: [Function (anonymous)],
      timeout: [Function (anonymous)],
      prefinish: [Function: requestOnPrefinish]
    },
    _eventsCount: 7,
    _maxListeners: undefined,
    outputData: [],
    outputSize: 0,
    writable: true,
    destroyed: true,
    _last: true,
    chunkedEncoding: false,
    shouldKeepAlive: false,
    maxRequestsOnConnectionReached: false,
    _defaultKeepAlive: true,
    useChunkedEncodingByDefault: false,
    sendDate: false,
    _removedConnection: false,
    _removedContLen: false,
    _removedTE: false,
    _contentLength: 0,
    _hasBody: true,
    _trailer: '',
    finished: true,
    _headerSent: true,
    _closed: true,
    socket: TLSSocket {
      _tlsOptions: [Object],
      _secureEstablished: true,
      _securePending: false,
      _newSessionPending: false,
      _controlReleased: true,
      secureConnecting: false,
      _SNICallback: null,
      servername: 'api.storyblok.com',
      alpnProtocol: false,
      authorized: true,
      authorizationError: null,
      encrypted: true,
      _events: [Object: null prototype],
      _eventsCount: 9,
      connecting: false,
      _hadError: false,
      _parent: null,
      _host: 'api.storyblok.com',
      _readableState: [ReadableState],
      _maxListeners: undefined,
      _writableState: [WritableState],
      allowHalfOpen: false,
      _sockname: null,
      _pendingData: null,
      _pendingEncoding: '',
      server: undefined,
      _server: null,
      ssl: null,
      _requestCert: true,
      _rejectUnauthorized: true,
      parser: null,
      _httpMessage: [Circular *1],
      write: [Function: writeAfterFIN],
      [Symbol(res)]: null,
      [Symbol(verified)]: true,
      [Symbol(pendingSession)]: null,
      [Symbol(async_id_symbol)]: 67916,
      [Symbol(kHandle)]: null,
      [Symbol(lastWriteQueueSize)]: 0,
      [Symbol(timeout)]: null,
      [Symbol(kBuffer)]: null,
      [Symbol(kBufferCb)]: null,
      [Symbol(kBufferGen)]: null,
      [Symbol(kCapture)]: false,
      [Symbol(kSetNoDelay)]: false,
      [Symbol(kSetKeepAlive)]: false,
      [Symbol(kSetKeepAliveInitialDelay)]: 0,
      [Symbol(kBytesRead)]: 747,
      [Symbol(kBytesWritten)]: 200,
      [Symbol(connect-options)]: [Object],
      [Symbol(RequestTimeout)]: undefined
    },
    _header: 'GET /v2/cdn/stories/home?version=published&language=en&token=&cv=undefined HTTP/1.1\r\n' +
      'Accept: application/json, text/plain, */*\r\n' +
      'User-Agent: axios/0.24.0\r\n' +
      'Host: api.storyblok.com\r\n' +
      'Connection: close\r\n' +
      '\r\n',
    _keepAliveTimeout: 0,
    _onPendingData: [Function: nop],
    agent: Agent {
      _events: [Object: null prototype],
      _eventsCount: 2,
      _maxListeners: undefined,
      defaultPort: 443,
      protocol: 'https:',
      options: [Object: null prototype],
      requests: [Object: null prototype] {},
      sockets: [Object: null prototype] {},
      freeSockets: [Object: null prototype] {},
      keepAliveMsecs: 1000,
      keepAlive: false,
      maxSockets: Infinity,
      maxFreeSockets: 256,
      scheduling: 'lifo',
      maxTotalSockets: Infinity,
      totalSocketCount: 0,
      maxCachedSessions: 100,
      _sessionCache: [Object],
      [Symbol(kCapture)]: false
    },
    socketPath: undefined,
    method: 'GET',
    maxHeaderSize: undefined,
    insecureHTTPParser: undefined,
    path: '/v2/cdn/stories/home?version=published&language=en&token=&cv=undefined',
    _ended: true,
    res: IncomingMessage {
      _readableState: [ReadableState],
      _events: [Object: null prototype],
      _eventsCount: 3,
      _maxListeners: undefined,
      socket: [TLSSocket],
      httpVersionMajor: 1,
      httpVersionMinor: 1,
      httpVersion: '1.1',
      complete: true,
      rawHeaders: [Array],
      rawTrailers: [],
      aborted: false,
      upgrade: false,
      url: '',
      method: null,
      statusCode: 401,
      statusMessage: 'Unauthorized',
      client: [TLSSocket],
      _consuming: false,
      _dumped: false,
      req: [Circular *1],
      responseUrl: 'https://api.storyblok.com/v2/cdn/stories/home?version=published&language=en&token=&cv=undefined',
      redirects: [],
      [Symbol(kCapture)]: false,
      [Symbol(kHeaders)]: [Object],
      [Symbol(kHeadersCount)]: 38,
      [Symbol(kTrailers)]: null,
      [Symbol(kTrailersCount)]: 0,
      [Symbol(RequestTimeout)]: undefined
    },
    aborted: false,
    timeoutCb: null,
    upgradeOrConnect: false,
    parser: null,
    maxHeadersCount: null,
    reusedSocket: false,
    host: 'api.storyblok.com',
    protocol: 'https:',
    _redirectable: Writable {
      _writableState: [WritableState],
      _events: [Object: null prototype],
      _eventsCount: 2,
      _maxListeners: undefined,
      _options: [Object],
      _ended: true,
      _ending: true,
      _redirectCount: 0,
      _redirects: [],
      _requestBodyLength: 0,
      _requestBodyBuffers: [],
      _onNativeResponse: [Function (anonymous)],
      _currentRequest: [Circular *1],
      _currentUrl: 'https://api.storyblok.com/v2/cdn/stories/home?version=published&language=en&token=&cv=undefined',
      [Symbol(kCapture)]: false
    },
    [Symbol(kCapture)]: false,
    [Symbol(kNeedDrain)]: false,
    [Symbol(corked)]: 0,
    [Symbol(kOutHeaders)]: [Object: null prototype] {
      accept: [Array],
      'user-agent': [Array],
      host: [Array]
    }
  },
  response: {
    status: 401,
    statusText: 'Unauthorized',
    headers: {
      'content-type': 'application/json; charset=utf-8',
      'content-length': '24',
      connection: 'close',
      date: 'Fri, 20 Oct 2023 16:24:50 GMT',
      server: 'nginx/1.18.0',
      'x-frame-options': 'SAMEORIGIN',
      'x-xss-protection': '1; mode=block',
      'x-content-type-options': 'nosniff',
      'x-download-options': 'noopen',
      'x-permitted-cross-domain-policies': 'none',
      'referrer-policy': 'strict-origin-when-cross-origin',
      'cache-control': 'max-age=0, public, s-maxage=604800',
      'x-request-id': 'ffe5f785-1e9f-40aa-82d0-6a31d4e505e6',
      'x-runtime': '0.005691',
      vary: 'Origin',
      'x-cache': 'Error from cloudfront',
      via: '1.1 1d70b90303ff56b86662db87683a2a04.cloudfront.net (CloudFront)',
      'x-amz-cf-pop': 'MIA3-C1',
      'x-amz-cf-id': '0SfDtNvMuQ7Kr3Y5qS_8Azl1rwHC9rHv12sadH2cbk3u2EgeIGajyw=='
    },
    config: {
      transitional: [Object],
      adapter: [Function: httpAdapter],
      transformRequest: [Array],
      transformResponse: [Array],
      timeout: 0,
      xsrfCookieName: 'XSRF-TOKEN',
      xsrfHeaderName: 'X-XSRF-TOKEN',
      maxContentLength: -1,
      maxBodyLength: -1,
      validateStatus: [Function: validateStatus],
      headers: [Object],
      baseURL: 'https://api.storyblok.com/v2',
      proxy: false,
      params: [Object],
      paramsSerializer: [Function: paramsSerializer],
      method: 'get',
      url: '/cdn/stories/home',
      data: undefined
    },
    request: <ref *1> ClientRequest {
      _events: [Object: null prototype],
      _eventsCount: 7,
      _maxListeners: undefined,
      outputData: [],
      outputSize: 0,
      writable: true,
      destroyed: true,
      _last: true,
      chunkedEncoding: false,
      shouldKeepAlive: false,
      maxRequestsOnConnectionReached: false,
      _defaultKeepAlive: true,
      useChunkedEncodingByDefault: false,
      sendDate: false,
      _removedConnection: false,
      _removedContLen: false,
      _removedTE: false,
      _contentLength: 0,
      _hasBody: true,
      _trailer: '',
      finished: true,
      _headerSent: true,
      _closed: true,
      socket: [TLSSocket],
      _header: 'GET /v2/cdn/stories/home?version=published&language=en&token=&cv=undefined HTTP/1.1\r\n' +
        'Accept: application/json, text/plain, */*\r\n' +
        'User-Agent: axios/0.24.0\r\n' +
        'Host: api.storyblok.com\r\n' +
        'Connection: close\r\n' +
        '\r\n',
      _keepAliveTimeout: 0,
      _onPendingData: [Function: nop],
      agent: [Agent],
      socketPath: undefined,
      method: 'GET',
      maxHeaderSize: undefined,
      insecureHTTPParser: undefined,
      path: '/v2/cdn/stories/home?version=published&language=en&token=&cv=undefined',
      _ended: true,
      res: [IncomingMessage],
      aborted: false,
      timeoutCb: null,
      upgradeOrConnect: false,
      parser: null,
      maxHeadersCount: null,
      reusedSocket: false,
      host: 'api.storyblok.com',
      protocol: 'https:',
      _redirectable: [Writable],
      [Symbol(kCapture)]: false,
      [Symbol(kNeedDrain)]: false,
      [Symbol(corked)]: 0,
      [Symbol(kOutHeaders)]: [Object: null prototype]
    },
    data: { error: 'Unauthorized' }
  },
  isAxiosError: true,
  toJSON: [Function: toJSON],
  page: '/'
}

Screenshot Of Error

Hey @DustyDogCodex! Thank you so much for your patience.
Can you try the token listed in our tech volunteer guide here?
Let me know how that works, thanks again!

Hi @kyleecodes ,
Hope you are doing well! thanks for your response. This does indeed fix the issue I encountered.
Thanks again!

Closing this issue because it's been solved in recent app upgrades done by our dev team, thank you for your time!


TypeError: unhashable type: 'list'

import torch
import torchvision
from torchviz import make_dot
model = torchvision.models.detection.retinanet_resnet50_fpn(pretrained=True)
model = model
model.eval()
x = [torch.rand(3, 300, 400)]
predictions = model(x)
print(predictions)
g = make_dot(predictions)
g.render('espnet_model', view=False)

the official example of PyTorch failed.

https://pytorch.org/vision/stable/models.html#retinanet

Hi,
The make_dot function expects either a Tensor or a tuple of Tensors as input. You're giving it a list of dictionaries right now.

thank you～

I'm sorry for necrobump. My problem is relevant
I'm training SSD model for object detection, which outputs dictionary like:
{
    "boxes": [],
    "scores": [],
    "labels": [],
}

How I can visualize this model? The problem is same:
TypeError: unhashable type: 'list'


⚠ Bofrost.de has degraded performance

In 4e214ec, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1061 ms

Resolved: Bofrost.de performance has improved in 1aabcdd.


Fix uninitialised constant Gem::ConfigFile::SYSTEM_CONFIG_PATH

What was the end-user problem that led to this PR?
bundle env uses the constant Gem::ConfigFile::SYSTEM_CONFIG_PATH which is not defined in early versions of RubyGems.
See: https://travis-ci.org/bundler/bundler/builds/276981165
What is your fix for the problem, implemented in this PR?
While SYSTEM_CONFIG_PATH is not defined for earlier versions of RubyGems, a constant called Gem::ConfigFile::SYSTEM_WIDE_CONFIG_FILE does appear to be both in current and early versions of RubyGems which contains the path (plus the ruby config file) we want.
Why did you choose this fix out of the possible options?
This fix is compatible with all the tested versions of RubyGems in CI and is not overly complex.

I'd recommend adding a small comment to that explaining why it's used in favor of SYSTEM_CONFIG_PATH, just so the context is there w/o digging around for the specific commit where you fixed it.
Something like # SYSTEM_CONFIG_PATH is unavailable on older versions of RubyGems, so use SYSTEM_WIDE_CONFIG_FILE instead.

@colby-swandale thanks for figuring this out!
@bundlerbot r+


The request is invalid. Details: definition : Error in Vectorizer 'xxxxx' : Invalid resourceUri. Provide a valid resourceUri for the Azure Open AI service.

I try to connect data from Azure Storage Account or Azure SQL Server to AI Search and use Vector search following the instructions and examples in these websites: Integrated data chunking and embedding in Azure AI Search, Vector Search with Azure SQL Database, AzureSQLACSSamples
I have tried to create the resources from Azure Portal and also from a python script, but I keep getting the same error. The resourceUri has this format: https://.openai.azure.com and if I try to change it to the endpoint that the resource has in Azure portal with format https://.api.cognitive.microsoft.com/ keeps showing the same error.

I have just tried with other Azure OpenAI resource that its endpoint shown from azure portal has the format that the AI Search vectorizer needs: https://xxxxx.openai.azure.com. This other resource is from West Europe and the AI Search is from North Europe. I was trying with East US Azure OpenAI resources and was not working out


Set up Storybook

:tada: This issue has been resolved in version 1.212.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Updates webhook to use app.kubernetes.io selector label

Changes
As part of https://github.com/knative/serving/issues/12215 we're planning to transition from the serving.knative.dev/release label to the recommended app.kubernetes.io label in Serving. This PR updates the net-certmanager validating webhook to use the new label.
Release Note

Switches selectors for Knative resources to use the recommended `app.kubernetes.io` labels

/assign @dprotaso

/cancel approve
(release lead super power)

/remove-approve

/lgtm
/approve


Logical deletion is supported

You want to be able to support logical deletions, which can be useful in real projects.
In addition, I found that there is a PR about this function, and the time interval is long. Can you deal with it as soon as possible?

https://github.com/spring-projects/spring-data-relational/pull/230

https://github.com/spring-projects/spring-data-relational/issues/771

https://github.com/spring-projects/spring-data-relational/pull/1486

No, we cannot address all requests as soon as possible but once we have time for these.


chore: run test over src instead npx

I think is more reliable in this way, otherwise need to rely in a previous published version
I'll check windows failure test

Hey @juanpicado, this working without previous published version. Maybe you missed the the yarn link.
Best Mirko

yarn link? I am missing something, could you give me a hint?

Please have a look on the prepareTests.sh script


fix a bug, which has the little probability of producing nan in the loss

This is the simplest way to prevent calculating log(0). And this is nesseceray when the embedding dim is large. When feature representations have very high dimensions, the maximum inner product is very likely to be the inner product with itself. After subtracting the maximum value, this will result in a lot of negative values in non-diagonal positions. This means that after exp(), it's very likely to be zero anywhere but the diagonal. In this case, since the diagonal position is not considered inside the log(), there is a probability that log(0) will be computed, resulting in nan.

This is the simplest way to prevent calculating log(0). And this is nesseceray when the embedding dim is large. When feature representations have very high dimensions, the maximum inner product is very likely to be the inner product with itself. After subtracting the maximum value, this will result in a lot of negative values in non-diagonal positions. This means that after exp(), it's very likely to be zero anywhere but the diagonal. In this case, since the diagonal position is not considered inside the log(), there is a probability that log(0) will be computed, resulting in nan.

Thank you very much for solving the problem that loss is NaN. Will your loss become higher and higher when you train? I look forward to your reply!

This is the simplest way to prevent calculating log(0). And this is nesseceray when the embedding dim is large. When feature representations have very high dimensions, the maximum inner product is very likely to be the inner product with itself. After subtracting the maximum value, this will result in a lot of negative values in non-diagonal positions. This means that after exp(), it's very likely to be zero anywhere but the diagonal. In this case, since the diagonal position is not considered inside the log(), there is a probability that log(0) will be computed, resulting in nan.

Thank you very much for solving the problem that loss is NaN. Will your loss become higher and higher when you train? I look forward to your reply!

Did you solve this?


add nextraConfig.unstable_readingTime option for blog theme

fixes https://github.com/shuding/nextra/issues/683
disabled

enabled

another example

@B2o5T Excellent work 🎉. May I ask you Is there is reason for putting the tags on next line? Isn't it possible to just inline the reading time between date and tags?

didn't want to put too many things on one line, let's wait for the thought of @shuding

Great feature, thanks @B2o5T!
When there're many tags it looks cleaner to break into a new line indeed. BTW can we make them top-aligned?

Yes, I also agree. Moving tags on the next line only when there are many tags and aligning back-button and theme-switch with date will also work.

@shuding rebased and fixed vertical alignment, what about adding the same in docs theme? which place will be the best to put it there?

Not sure if we want to put this on the docs theme (maybe as an option that defaults to false) because usually when people look at docs, they only check the section that they need (hence https://tailwindcss.com uses the search bar as CTA), unlike blogs.

We can ship this first and have a discussion about that feature in docs!


When scrolling away the header, the page body should not jump around

From @pbakaus
"Right now, when loading a page such as https://material-dot-web-central.appspot.com/web/tools/setup/workspace/setup-buildtools, the page does a jump when you scroll down and it's very irritating. Let's solve this without jumpy jump jump."
This is in respect to the header in Web Fundamentals if you scroll down slowly, when the subheading collapses the body moves up.
I don't know what the desired behaviour would be for this. It might be solved in 2.0 if we introduce less magic in terms of structure of the page.

The waterfall header is usually animated. Not sure how that got lost. It would make it sufficiently un-jumpy, I guess.

It could be that I'm doing something wrong on WF.

More feedback on this:
"Scrolling the page, the header quickly jumps to its smaller fixed position. It doesn't feel right and isn't the MD spec. Instead, the bar should ease/transition to it's final state.
Something like:
https://elements.polymer-project.org/elements/paper-scroll-header-panel?view=demo:demo/index.html"

Valid point. I’ll leave this open for the layout rework

I can't load the initial webpage that showed the problem:
https://material-dot-web-central.appspot.com/web/tools/setup/workspace/setup-buildtools
So I want to ask if the problem can be seen in this template page http://www.getmdl.io/templates/android-dot-com/index.html
If you load the page and quickly scroll down, at some point the page will jump to the top.
It's the unique template with this behaviour -I suspect- because is the unique template demo with a drawer,
I believe I'm currently experimenting the same problem in a website I'm working in (I'd like to submit it for the showcase, though), and exploring over some sites submited for showcase I can exactly see the issue in the following threads:
@ealsur https://github.com/google/material-design-lite/issues/1389#issue-100816129
@daretodave https://github.com/google/material-design-lite/issues/1389#issue-100816129
@czenisek https://github.com/google/material-design-lite/issues/1860#issuecomment-155252083
Not sure, I'm not an expert developer, but seems that the "jump" happens when the elements in the DOM are "upgraded".
I'd be glad to provide more details or feedback if neccesary. Thanks!

It does happen when upgrade occurs, because that is when logic is done moving nodes around and creating new containers and such.
There is nothing that can be done about this until the 2.x refactor of Layout since it fundamentally changes how the component operates. It is one of the many in a long list of known 1.x Layout problems.

Are there any suggested solutions to the 'jumping to the top' issue / is there a timeline for 2.x release?
Currently I'm obscuring the page on load and showing a spinner and revealing the page upon 'mdl-componentupgraded' to prevent users from scrolling before the layout is upgraded. This makes it seem to the user that the page is taking much longer to load than it really does - not user friendly.

No timeline on V2 and no recommended solutions to hotfix 1.x with.

We are working on a complete V2 rewrite currently. Closing this issue out since Layout is being broken down and simplified in this effort so this issue should naturally get solved.


Update text of widget tooltips

Fixes #11467
Category widget

Histogram widget

I'm not sure about the category widget tooltip, in the issue it says "Custom ramp", but the label says "Custom categ." / @arianaescobar

Hi Ruben!
I discussed it over with @makella and she reminded me that we only use the term ramps for TurboCARTO. So we are going to stay away from that and even tho the correct naming is "Schemes" we both agree on simplifying it for the end user and going with just "Custom colors" on both widgets.
Sounds good?

Sounds good, thank you!

retest this please


Update mandatory properties to allow a 'nil' value

From enum.json#/$defs/NilValues.

Raised by discussion:
usedProcedure on SoilProfile
SS: In NatSoil we have 15,682 (of 25,476) with NULL o_type (meaning no usedProcedure).  Should we default to a particular value, change the Mandatory to Preferred, or accept 60% of our data cannot be loaded into ANSIS.
AR: Stuart’s right, at present you’ll find it hard to populate this. There is no ‘unknown’ option as we never made a formal decision on doing this (so no issue raised) but I suspect that for every mandatory property I should go and add nil value options to the linked vocabs. Probably an hour to fix. Your call.
PW: Didn’t we discuss a set of values for this sort of thing? NIL when not present, UNKNOWN when not provided, NULL when not provided but should be (although this would negate Mandatory) – good to add the first two at least.

Define the rules at entity, not property? required is set in entity.json. A property may not be required in another context so shouldn't have global options.

Summary of required properties and their data types:
"SoilSite.geometry"                 -> result - object
"SoilSite.relatedProject"           -> object - ref
"SiteVisit.endedAtTime"             -> string (date time)
"SiteVisit.startedAtTime"           -> string (date time)
"SiteVisit.relatedProject"          -> object - ref
"SiteVisit.relatedVisitor"          -> object - ref
"SoilProfile.depth"                 -> result - Quantity
"SoilProfile.geometry"              -> result - object
"SoilProfile.usedProcedure"         -> enum
"SoilSample.component"              -> result - enum
"SoilSample.depthLower"             -> result - Quantity
"SoilSample.depthUpper"             -> result - Quantity
"SoilLayer.depthLower"              -> result - Quantity
"SoilLayer.depthUpper"              -> result - Quantity
"SoilHorizon.depthLower"            -> result - Quantity
"SoilHorizon.depthUpper"            -> result - Quantity
"SoilHorizon.designation"           -> result - object
"Outcrop.abundance"                 -> result - enum
"CoarseFragments.abundance"         -> result - enum
"Cracks.width"                      -> result - enum
"Cutans.abundance"                  -> result - enum
"Cutans.ansisType"                  -> enum
"Mottles.abundance"                 -> result - enum
"Mottles.ansisType"                 -> enum
"Pans.ansisType"                    -> enum
"Pores.abundance"                   -> result - enum
"Pores.diameter"                    -> result - enum
"Roots.abundance"                   -> result - enum
"Segregations.abundance"            -> result - enum
"Segregations.material"             -> result - enum
"SoilStructures.ansisType"          -> enum
"SoilStructures.grade"              -> result - enum
"Erosion.ansisType"                 -> enum
"Inundation.frequency"              -> result - enum
"StreamChannel.development"         -> result - enum
"Microrelief_biotic.agent"          -> result - enum
"Microrelief_biotic.component"      -> result - enum
"Microrelief_gilgai.ansisType"      -> enum
"Microrelief_hummocky.ansisType"    -> enum
"Microrelief_other.ansisType"       -> enum
"Consistence.moistureStatus"        -> result - enum
"Consistence.strength"              -> result - enum
"LandformElement.morphologicalType" -> result - enum
"LandformElement.slope"             -> result - enum
"LandformPattern.relief"            -> result - enum
"LandformPattern.slope"             -> result - enum
"SoilPlasticity.ansisType"          -> enum

Proposed solution.

Note: using nil instead of null because null has meaning ... null, where nil means null but with a reason ... nil:witheld.

Provide nil values as an option at the entity level where the property is linked to an object (entities.json), not at the property level (properties*.json). Because ... required is set at the entity level, and whether a property is required will vary with use cases (entities.json is use case specific).
A nil property will always be a single string value from the NilValues enumeration. Means only one test for a nil value is needed, and don't have to faff around looking for nil reasons in different places depending on the property/object type.

Examples
Schema definition
"depth": {
    "oneOf": [
        {
            "$ref": "./enum.json#/$defs/NilValues"
        },
        {
            "$ref": "./properties.json#/$defs/_obs/$defs/depth/$defs/Quantity"
        }
    ]
}

Populated value
"depth": {
    "result": {
        "value": 2,
        "unit": "unit:M"
    }
}

Nilled value
"depth": "nil:unknown"

Branch version-1.0-rc3.

Ultimately reverted to no nils given complexity of parsing a document with this form of data type polymorphism.


Data url decoding

Target
Make the repo more easy to use for people who aren't planning on using the data url directly.
Checklist

[X] Documentation updated
[X] Tests cover new or modified code
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] New dependencies added
[ ] Includes breaking changes
[ ] Version bumped

Hi @biegehydra. Could you re-open new PR, besides we need to run pipelines when the branch name begin with "feature/*"

Hi @biegehydra. Could you re-open new PR, besides we need to run pipelines when the branch name begin with "### feature/*"


cnijfilter2: init at 5.30

Motivation for this change
I tried printing with my brand new Canon PIXMA MG7720 using cups-bjnp and Gutenprint, but the printer just spews out an endless pile of papers with a thin, faint scratchy line at the bottom.
To fix that, I've packaged up cnijfilter2, which provides support for the following series:
MG7500, MG6700, MG6600, MG5600, MG2900, MB2000, MB2300, iB4000, MB5000, MB5300, iP110, E450, MX490, E480, MG7700, MG6900, MG6800, MG5700, MG3600, G3000
I've confirmed that the drivers are working wonderfully with my MG7720.
Things done

[x] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

This is ready to merge.
I do, however, have a question for someone who has a better understanding of CUPS. The web interface provides me with the list of Gutenprint PPDs when I select "Canon" as the model, but it doesn't show me the PPDs I've copied into $out/share/cups/model. Is there something I need to do in this package so this package's PPDs show up in the web interface?

The web interface provides me with the list of Gutenprint PPDs when I select "Canon" as the model, but it doesn't show me the PPDs

according to https://nixos.wiki/wiki/Printing
# /etc/nixos/configuration.nix
{
  services.printing.enable = true;
  services.printing.drivers = [
    pkgs.gutenprint
    pkgs.gutenprintBin
    pkgs.cnijfilter2
  ];
}

The web interface provides me with the list of Gutenprint PPDs when I select "Canon" as the model, but it doesn't show me the PPDs

according to https://nixos.wiki/wiki/Printing
# /etc/nixos/configuration.nix
{
  services.printing.enable = true;
  services.printing.drivers = [
    pkgs.gutenprint
    pkgs.gutenprintBin
    pkgs.cnijfilter2
  ];
}


simpleAuthProvision fails with 'BadRequest'

My deployment keeps failing at the simpleAuthProvision resource with a generic error message of "Object reference not set to an instance of an object". I feel confident I have met the prerequisites: deploying to a region that supports the required services and owner access on the subscription I am using. The Base Resource Name I am using is all lowercase letters. I am not trying to use any customizations, just following the build instructions as written.
I am using a CDX environment tenant with a VSE subscription (63P) and am wondering if that could be what's causing the error? I was able to replicate the same error on a Developer tenant, also using the VSE subscription. Thanks!

I saw the fix action for this in closed issues immediately after I hit submit! Editing the template fixed it. Thanks!


Aegisub Create 8975-master-8d77da3.yaml

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

This is the most updated build of Aegisub.
Microsoft Reviewers: Open in CodeFlow

/azp run


Python SDK: Feat. process specific pages, Other fixes and improvements

Python SDK
Changes:

Feature added: now specific pages can be processed with the python sdk using "select_pages" param. Incorporates #23, #24 for python sdk
workflow for the above feature: create a new temperory pdf (Refer: py_zerox/pyzerox/core/zerox.py) in the tempdir if select_pages is specified and follow the rest of the process as usual and finally map the page number in the formatted markdown to get the actual number instead of index. Added a helper function in py_zerox/pyzerox/processor/utils.py.
raise warning when both select_pages and maintain_format used. Refer: py_zerox/pyzerox/core/zerox.py
required adaptations and updates in messages, exceptions, types, processor, utils etc

Fixes/improvements:

memory efficient pdf to image conversion, utilizing paths only option to directly get sorted image paths from pdf2image api. Refer: py_zerox/pyzerox/processor/pdf.py

Misc:

Bump the version tag
documentation updated

@annapo23, @tylermaran Could you review this one.


Phpvms V5 to V7 Importer

Doing a legacy import from v5 to v7 produces a server 500 error and the database is not imported are required.

Need more details. Any logs? If you look at the database afterwards, any clues as to where the import might have stopped or errored out?

Based on larvael logs,
[2021-06-09 07:12:00] production.INFO: Table groups doesn't exist
[2021-06-09 07:12:00] production.INFO: Table airlines doesn't exist
The importer is unable to detect or sense the existing db table to be imported
[2021-06-09 07:12:06] production.ERROR: View [home] not found. {"exception":"[object] (InvalidArgumentException(code: 0): View [home] not found. at /home/singap08/public_html/test/vendor/laravel/framework/src/Illuminate/View/FileViewFinder.php:137) [stacktrace]
A fresh db has been used with the default theme.
Not sure if they are any help


Permanently delete cad file

Permanently remove cad file.
example-data\pyfluent\Wind-Loading>rm windload_geometry.scdoc.pmdb
example-data\pyfluent\Wind-Loading>cd ..
example-data\pyfluent>rmdir Wind-Loading
example-data>git commit -a -m "delete unwanted file permanently"
example-data>git filter-repo --invert-paths --path Wind-Loading
example-data>git push origin del_confidential
example-data>git diff master
diff --git a/pyfluent/examples/Wind-Loading/windload_geometry.scdoc.pmdb b/pyfluent/examples/Wind-Loading/windload_geometry.scdoc.pmdb
deleted file mode 100644
index b50736f..0000000
Binary files a/pyfluent/examples/Wind-Loading/windload_geometry.scdoc.pmdb and /dev/null differ

@akaszynski can you and the team please check this?

@seanpearsonuk The title of the PR is "Permanently delete cad file" but in the files tab - there are no file deletions.

@seanpearsonuk The title of the PR is "Permanently delete cad file" but in the files tab - there are no file deletions. I see in your comment a mention of a wind-loading file but when I open the public repo in the master branch there is no such file.
It looks like this PR just a rewrite of git history to remove that file from all branches - is that right?

correct


Improve test coverage for ClinicIO

Work on commons and logic.

Commons

HashUtil.java

Logic

ParserUtil.java
PatientUtil.java
ClinicIoUtil.java
LogicManager.java

Pull Request Test Coverage Report for Build 725

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.5%) to 61.075%

Totals

Change from base Build 714:
2.5%

Covered Lines:
2250

Relevant Lines:
3684

💛  - Coveralls


Depricated IAspNetCoreAppModule

I've merged both IAspNetCoreAppModule and IOwinAppModule into IAppModule, and it's going to be released soon.
Thanks for your attention. We're thankful about that.

It seems that we've to update our working .net core private build to the stable release of .net core 2.1 too.


General Info

[X] I would like to propose new content
[ ] I would like to propose changes
[ ] I would like to propose another thing

Suggestion Description
Geodes can be pretty hard to find, so I'd suggest adding a tool that'd aid in discovering them.
Something like a divining rod combined with the type of material that you'd want to find, that'd increasingly shake when you're facing and getting closer to a geode of its type. Or maybe something a bit more high-tech, redstone-esque style.

the idea behind Ge-ores is that they are hard to find but once found rewarding, for the time being I will have to say no to adding this, if more people want this I can think about adding such feature.


ReasonML: Add list of reserved keywords

As discussed here, it is a good idea to have a list of reserved keywords.
It would also be interesting to discuss certain syntax desugaring (such as __x for first pipe placeholder and type_ vs. type conversion in object attributes).

It was mentioned in the thread that OCaml docs already maintain a list of keywords: http://caml.inria.fr/pub/docs/manual-ocaml-312/manual044.html
It might make sense to maintain just a list of Reason changes on top of that list. E.g., private -> pri, match -> switch, etc. Of course we would also point to the OCaml reserved words index and say something like, 'ReasonML reserved words are substantially the same as OCaml's, documented here: ... with the following changes: ...'

@yawaramin Is it bad to just copy paste it? I think it's better UX to have a complete list right inside the docs to prevent forwarding users to the OCaml manual (we can neither use OCaml nor Reason keywords for variable names, it would be great to have a total overview!)... I guess it's good for DRYness, but on the other hand, keywords won't change that often.

Copy-pasting with attribution and a link to the source should be fine. Although depending on how we want to show it in the Reason Association docs, it might not really be a straight copy-paste but rather a fairly complete re-organization of the index.

I'm of the mind that sending people outside of docs for other docs is bad practice. What needs to be known should exist in a single spot so it can be consumed, contemplated, and edited as a single creation. Reason is not OCaml.

@amartincolby I kind of refer to this as the 'curse of crossover technologies', you're always going to have to refer to something external :-)
That said, for the keyword list I agree it's a good idea to document it in one place since it's so intrinsic to Reason syntax.

We will find a way to make it a one page! @yawaramin I really like your argument about attribution, I still need to figure out all the license details for colocating information from different sources.

Considering that the list is purely informative, there is no copyright, so no legal need for attribution. One cannot copyright facts. I still think it a good idea to offer the attribution, though, since even though Reason and OCaml are not the same, understanding their similarities is important.

There are some additional words in Reason that get special treatment (e.g. not gets rewritten as !) due to the fact that the parser makes some assumptions about the stdlib. I realize that's not quite the same thing as being a "reserved word" but it would be really great if those were documented somewhere.

The correct list of keywords will always be in the source code: https://github.com/facebook/reason/blob/master/src/reason-parser/reason_declarative_lexer.mll#L85-L144

Fixed in #163


Error when adding a spm package

Describe the bug
Build error after adding FLCharts as SPM package. Error description: "manifest property 'defaultLocalization' not set; it is required in the presence of localized resources".
To Reproduce
Steps to reproduce the behavior:

Go to Xcode.
Create a new project.
Add FLCharts as a SPM Package.
Build project.
See error in log.

Expected behavior
Package added without errors.
Screenshots

Desktop (please complete the following information):
– macOS Ventura 13.1
– Xcode version 14.2 (14C18)
Smartphone (please complete the following information):
Without using smartphone.
Additional context
After adding 'defaultLocalization' in Package.swift, package works correctly.

PR with fix – https://github.com/francescoleoni98/FLCharts/pull/62


Updated Team Component and Started import Testcases

Updated Team Component and Started import Testcases
Added ngx-drozone-wrapper which is an interface and dropzone component

Coverage remained the same at 95.381% when pulling bdac745400dc5465527a7b01b91601d731648727 on Angular-Client into<PHONE_NUMBER>4ffc39ba7ca7bb011483d262922a17 on master.


bug(COMPONENT): MatRadioButton

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
14.2.7
Description
Click event is firing twice when clicking on the radio label text. The issue is only happening when clicking on the label text.
The event will only fire once when clicking on the radio control element.
Reproduction
StackBlitz link: https://stackblitz.com/edit/jephxf?file=src%2Fexample%2Fradio-overview-example.css
Steps to reproduce:

Just click on the radio label text.
And open the inspector and check the console log. You will get the logged value from the click event.

Expected Behavior
The event should fire only once.
Actual Behavior
When clicking on the radio label text the event is firing twice.
Environment

Angular: 16.2.1, 15.2.9
CDK/Material: 16.2.1, 15.2.9
Browser(s): Chrome, Firefox.
Operating System (e.g. Windows, macOS, Ubuntu): Windows

This is the native browser behavior, not something coming from Material. In general we don't address cross-browser differences like this unless they affect the user experience.


fix/UB-590_flex_log_is_not_compressed

To compress the flex log to save the disk space
Signed-off-by: feihuang<EMAIL_ADDRESS>

This change is

approve to merge it to dev.

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

Comments from Reviewable

"compress" works in dev build 176, also remove "daily" here, it is not useful  and dup with sleep 24 hours in setup_flex.sh.
So tested with below config, and it works in latest build 176
/usr/libexec/kubernetes/kubelet-plugins/volume/exec/ubiquity-k8s-flex.log {
su root root
size 50M
rotate 5
compress
copytruncate
create 0600 root root
}


Weather Shows as night (moon icon) even in the afternoon

Weather Shows as night (moon icon) even in the afternoon
To Reproduce
Using YR.no
Expected behavior
Shouldn't be moon before sunset
Screenshots

Smartphone (please complete the following information):

Device: Xiaomi Poco X3]
OS Version:  Android 12]
App Version (2.3.3

Widget shows Moon icone during the day and sun icone during the night.
How can I fix the issue?


Question on combineReducers depends on process.env.NODE_ENV  'production'

I'm looking at the redux source code and find this line
https://github.com/rackt/redux/blob/master/src/utils/combineReducers.js#L128
So looks like it is assuming that people will always use the same string production as node argument when they deploy to production?

Yes. This is a very common idiom, and React does it too. Since most Redux projects also use React it makes sense for us to do the same instead of adopting some other convention that isn't as popular.

Also it's not about deploying to production. You need to use envify (Browserify) or DefinePlugin (Webpack) when bundling your code.

Yes, I meant bundling not deploying to production.  Thanks for quick response.


java.time.LocalDate with @Future javax.validation annotation

The @Future annotation does't seem to have any effect on the json schema.
.
.
.
@Future
private LocalDate date;
.
.
.

The generate schema looks like
.
.
.
"date": {
	"type": "array",
	"items": {
		"type": "integer"
	}
},
.
.
.

Is there any other way to enforce date validation?

There is currently no support forjavax.validation.constraints.Future.
You have two choices:

Send PR with added support for it.

Use the @JsonSchemaInject-annotation to insert the schema-code you want.
https://github.com/mbknor/mbknor-jackson-jsonSchema#flexible

I actually thought about writing this as part of my earlier javax.validation contributions, but I don't think it's actually possible for v4 schema. I'm not exactly an expert on JSON schema, so if I've missed something, or someone knows how to do this, please do chime in.
Neither JSON nor the json-schema-validation draft spec contain a first-class type for date/time, This means that you get to use either a numeric value (think epochal timestamp) or a string. The validation spec does contain defined formats for dates and times as strings, but that doesn't really help us because a @Future annotation concerns the value of the field.
Without first class support for date/time you can't really do something like "is X after <some date/time>" because you have no way to make the comparison. And even if you could somehow compare it, there's no concept of "now" to compare it to.
I did look at json-schema-org/json-schema-spec#99 as well as the related json-schema-org/json-schema-spec#116, but it looks like these are still open.