README: Add link to Hubs sessions episode 2

Episode 2 is now available on YouTube

@spotify/objc-dev

How about extending this with some thumbnails? Visual stuff is always nice and make the hit-target massive. Could look something like (thumbnails could obviously be different):

Episode 1: Content Loading Chain
Episode 2: Creating Components

Markdown:
- [**Episode 1: Content Loading Chain**
<img<EMAIL_ADDRESS>width=320 alt="Hub Framework Sessions - Episode 1">](https://youtu.be/XbMFPtxk_4Q)
- [**Episode 2: Creating Components**
<img<EMAIL_ADDRESS>width=320 alt="Hub Framework Sessions - Episode 1">](https://youtu.be/JpeQhKAen8M)

Current coverage is 93.49% (diff: 100%)

Merging #254 into master will increase coverage by 0.13%

@@             master       #254   diff @@
==========================================
  Files            72         72
  Lines          5015       5015
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           4682       4689     +7
+ Misses          333        326     -7
  Partials          0          0

Powered by Codecov. Last update b9852cb...ea33831

That's an awesome suggestion @rastersize - will do that! Thanks! 😄

Wait a second @rastersize, those images are hosted on your own server or something? Not sure if we can use that here 😅

Merging this for now, and we can update to the thumbnails later once we've figured out where to host them.

@JohnSundell Yeah I pushed the images to my CloudApp account. Just to show how it would look asap :)
We can fix a better hosting method. Also the images I used are in an insane resolution (leading to about 1-2 MB for each) so need to resize them first as well :)


Error install laravel 11.14.0

I installed Laravel 10.10 and it was fine, but when I installed Laravel 11 an error occurred, or there was a step I missed.

Hi! Thank you for the report.
I have fix problem in new release, so update your Composer.
Any other suggestion is appreciated :)


Click the button to request data asynchronously, then copy the invalid data, and then click the second time

🐛 Bug Report

Fork this JSFiddle and reproduce your issue.

(A clear and concise description of what the issue is.)
Have you read the Contributing Guidelines on issues?
(Write your answer here.)
Expected Behaviour

I thought that by going to the page '...' and pressing the button '...' then '...' would happen.
Tip: Try to use screenshots, gifs, videos, always remember people better understand with a visual way.
Actual Behaviour
Instead of '...', what I saw was that '...' happened instead.
To Reproduce
(Write your steps such as:)

Step 1...
Step 2...
Step 3...

Browsers Affected
I tested on all major browsers and only IE 11 does not work.
Operational System
(Place here your Operational System.)

Hi @lahala, thanks for reporting your issue here.
Could you please provide the steps to reproduce it, a demo using JSFindle, and details following the guidelines?
I was not able to reproduce the issue by following only the title information 😁
Thanks.


Add default voice setting and apply to chat

A new tab is added to settings and the end-user can select one's favorite voice now.
Please see the screenshot.

Testing done:

Select Default in voice settings -> click the speaker icon -> ✔
Select Rocko (English (United States)) in voice settings -> click the speaker icon -> ✔

BTW, I reuse the speaker icon on the tab. It would be good if one could help to create a new icon.

Amazing stuff, Thanks for the PR! I fixed and refactored some code, please try it out and let me know if it works as intended on your end!

Amazing stuff, Thanks for the PR! I fixed and refactored some code, please try it out and let me know if it works as intended on your end!

Thanks for the review and refactoring! Everything works as expected.

Good to hear! everything LGTM, Thanks!


Develop and Run SAP Fiori Application With SAP Business Application Studio

Tutorials: https://developers.sap.com/tutorials/abap-environment-deploy-cf-production.html
Hello Experts,
In step 8, I could not choose OData V2 service for IAM App.

Please advice. Thanks.
BRs,
Bryant

Hi @xiebryant ,
can you try it out with OData IWSG?
Best regards,
Merve

Thank you for your feedback. We haven't heard from you in a while, so we are closing the issue.
If you still have questions, feel free to reopen the issue.


Update v3api.py

deprecation warning: '.reindex_axis' is deprecated and will be removed in a future version. Use '.reindex' instead.

good question. I am not even sure how you check that but a quick search
looks like it goes back to 0.15 or earlier.
On Wed, Sep 19, 2018 at 10:40 PM Paul Mestemaker<EMAIL_ADDRESS>wrote:

@PaulMest commented on this pull request.
In tia/bbg/v3api.py
https://github.com/PaulMest/tia/pull/1#discussion_r218973358:

@@ -406,7 +406,7 @@ def as_frame(self):
data = {sid: pd.Series(data) for sid, data in self.response_map.items()}
frame = pd.DataFrame.from_dict(data, orient='index')
# layer in any missing fields just in case

   frame = frame.reindex_axis(self.request.fields, axis=1)

   frame = frame.reindex(self.request.fields, axis=1)

Thanks for this.
What's the earliest version of pandas that supports DataFrame.reindex?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PaulMest/tia/pull/1#pullrequestreview-157033943, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AZekSDKtCwCAbh1sHpVWhAzdYQAiPTvdks5ucrnlgaJpZM4WxAyU
.


Dashrews/ROX-15162 helm example files should match shape

Description
The example files had db as a peer of central instead of a child of central like the shape did.  This PR resolves that.
Checklist

[ ] Investigated and inspected CI test results
~- [ ] Unit test and regression tests added~
~- [ ] Evaluated and added CHANGELOG entry if required~
~- [ ] Determined and documented upgrade steps~
~- [ ] Documented user facing changes (create PR based on [openshift/openshift-docs]~(https://github.com/openshift/openshift-docs) and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Simple updates example values files.  nothing to test.

/retest


No attribute 'exponential_query_iterator' when running descriptor_eval.py

Hi, when I reproduce the baseline, I meet this problem.
Here is detail error message

AttributeError: module 'faiss.contrib.exhaustive_search' has no attribute 'exponential_query_iterator'
It seems faiss contrib remove the attribute 'exhaustive_search.exponential_query_iterator'? Which version of faiss should I use?

[Update] faiss-cpu version seems no such problem.

We tested on version 1.7.2 and the main branch near when 1.7.3 was released, so we expect 1.7.3 to work as well. If the error was for an earlier version of faiss, that is expected.
The faiss exhaustive_search library was changed significantly in recent faiss versions, making it difficult to implement range search based on a global result budget in a way that works for both 1.7.2 and earlier faiss versions (at least for inner-product similarity).
For a version that works with earlier faiss versions, this codebase's _global_threshold_knn_search is similar to search_with_capped_res from the Image Similarity Challenge codebase, but the ISC version targets earlier versions of faiss:
https://github.com/facebookresearch/isc2021/blob/main/isc/descriptor_matching.py#L63


blog: blog posts, fix

Error: YAML Exception reading /home/runner/work/blog/blog/_posts/2024-10-10-SharpiegateTrumpAddedDickheadConeUncertainyDorian.md: (): could not find expected ':' while scanning a simple key at line 7 column 1


Entrypoint trap trimed out: the forkserver injection failed, or the target process never reached its entrypoint.

Hi, i want to use winnie but i have an error following the walkthrough for the toy_example sample.
CMD Used: afl-fuzz -i in -o out -t 1000 -I 1000 -- -bbfile basicblocks.bb -- -harness harness.dll -no_minidumps -debug -- toy_example.exe @@
-debug option returns:

Winnie 1.00 -- Forkserver-based Windows fuzzer
Based on WinAFL 1.16b and AFL 2.43b
[+] You have 4 CPU cores and 2 runnable tasks (utilization: 50%).
[+] Try parallel jobs - see docs\parallel_fuzzing.txt.
[*] Checking CPU core loadout...
[+] Found a free CPU core, binding to #0.
[*] Setting up output directories...
[+] Output directory exists but deemed OK to reuse.
[*] Deleting old session data...
[+] Output dir cleanup successful.
[*] Scanning 'in'...
[+] No auto-generated dictionary tokens to reuse.
[*] Creating hard links for all input files...
[*] Using fullspeed (fault-based) instrumentation.
[*] Attempting dry run with 'id_000000'...
[*] Debug mode enabled

  cmd: toy_example.exe out\.cur_input
  PEB=0x000000000021D000, Base address=0x0000000000030000
  Binname: toy_example.exe, OEP:<PHONE_NUMBER>001435
  Entrypoint =<PHONE_NUMBER>031435

[-] PROGRAM ABORT : Entrypoint trap trimed out: the forkserver injection failed, or the target process never reached its entrypoint.

         Location : spawn_child_with_injection(), D:\WORK\codes\winnie\afl-fuzz\forkserver.c:448

BB File generated with IDA Pro 7.5 using the script provided
Compilation of Winnie and the toy example:
Windows 10 19044.1526
CSRSS Offsets generated successfully

Used Visual Studio 2019
Used SDK 10.0.22000
Used MSVC v142

No errors during compilation

I've tried to disable windows binary protections from settings but nothing.
Thanks and Regards!

Could you compile in Debug mode and run it? There should be some more output I think

Hi, I am facing the same problem.
cmd: toy_example.exe out.cur_input
PEB=0x000000000028B000, Base address=0x0000000000030000
Binname: toy_example.exe, OEP:<PHONE_NUMBER>001438
Entrypoint =<PHONE_NUMBER>031438
TRACE: Watchdog timeout
[-] PROGRAM ABORT : Entrypoint trap trimed out: the forkserver injection failed, or the target process never reached its entrypoint.
     Location : spawn_child_with_injection(), e:\winnie\afl-fuzz\forkserver.c:448

@HE-UMU @kmackinley @newuser54
I figured it out. It is because the DLL injection works only when 32bit injects 32 exe or 64 bit inject 64bit. In this repo, the author by default sets the toy_example project to x86. Recompile both afl-fuzzer and toy_example.exe with x64 works.
However, I am facing another bug: "Failed to set process affinity" pops up in the forkserver.exe. This seems to be caused by the author assumed the host machine contains more than one cpu. But I ran the code on a one-core machine. Still working on this issue.

Ohhhh, finally it worked. I configured the virtual machine to contain 4 cores rather than one core and the problem solved. This is really a damn awesome project!

@LeoLiu-2020 Thank you!
I will update the documentation to specify the machine must be multicore.


Fix potential integer overflow loading ELF files

When loading ELF files we calculate the location of a section header in a way that can overflow a uint32_t value producing a wrong result.
This commit fixes the issue by using the fact that section headers are contiguous in the ELF file.
Resolves #147

@matt-gretton-dann if we care about this, there is libfuzz based approach we took to harden flush out issues in the library used by Prevail and ebpf-for-windows.
https://github.com/microsoft/ebpf-for-windows/tree/main/tests/libfuzzer
We can probably port it over fairly easily, but I don't have time right now to fix any additional bugs it finds as it's not used by ebpf-for-windws.


fix: virtual environment to be able to run make test

The virtual environment expects people can run make test without installing pytest.
This PR fixes issue https://github.com/TRI-ML/dgp/issues/104
Before this fix
copying dgp/utils/torch_extension/stn.py -> build/lib/dgp/utils/torch_extension
running egg_info
creating dgp.egg-info
writing dgp.egg-info/PKG-INFO
writing dependency_links to dgp.egg-info/dependency_links.txt
writing entry points to dgp.egg-info/entry_points.txt
writing requirements to dgp.egg-info/requires.txt
writing top-level names to dgp.egg-info/top_level.txt
writing manifest file 'dgp.egg-info/SOURCES.txt'
reading manifest file 'dgp.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '*.proto' found under directory '*'
writing manifest file 'dgp.egg-info/SOURCES.txt'
PYTHONPATH=/home/nehal/dgp: \
pytest -v /home/nehal/dgp/tests/
/bin/sh: 1: pytest: not found
make: *** [Makefile:72: test] Error 127

After this fix
================================================= 56 passed, 3 skipped, 4 warnings in 13.57s ==================================================

This change is

Link for virtual environment doc
https://github.com/TRI-ML/dgp/blob/master/docs/VIRTUAL_ENV.md

I got the following error in super linter (even though I didn't touch that comment); so fixing it
/github/workspace/docs/VIRTUAL_ENV.md
  22:208  ✓ error  Incorrect usage of the term: “repo”, use “repository” instead  terminology

✖ 1 problem (1 error, 0 warnings)
✓ 1 fixable problem.

Ever since this commit, I think we need to instruct users to pip install -r requirements.txt -r requirements-dev.txt.

Yup, I agree with you!

As for the comment issue, usually tools don't lint portions of files but the entire thing, so it looks like that might have been a latent issue since before linting was enabled?

Oh, that makes so much sense, thanks!

Thanks for the merge again!


3D radial trajectory bundle

This PR adds four 3D radial trajectories from the literature mentioned in issue #106:

initialize_3D_phyllotaxis_radial from "Spiral Phyllotaxis: The Natural Way to Construct a 3D Radial Trajectory in MRI" Davide Piccini et al. (2011). Radial shots are oriented following a Fibonacci sphere lattice.
initialize_3D_golden_means_radial from "Temporal Stability of Adaptive 3D Radial MRI Using Multidimensional Golden Means", Rachel W. Chan (2009). Radial shots are oriented following Fibonacci-based non-repeating angles.
initialize_3D_wong_radial from "A Strategy for Sampling on a Sphere Applied to 3D Selective RF Pulse Design", Sam T. S. Wong and Mark S. Roos (1994). Radial shots are oriented following one or multiple spiral(s) over the k-space sphere.
initialize_3D_park_radial from "A radial sampling strategy for uniform k-space coverage with retrospective respiratory gating in 3D ultrashort-echo-time lung imaging", Jinil Park et al. (2016). This pattern is based on Wong et al. (1994) from initialize_3D_wong_radial, enforcing a single spiral and ordering shots in a different way.

Documentation & examples coming soon.
The illustration below shows the tips of each radial shot for each of the four patterns.

Could you resubmit with only c98d54a61695a2de94ec66954bb7dddc843fd1d0 I think that the only one you want in the branch ?

I have also come across AZETK: https://pubmed.ncbi.nlm.nih.gov/32936490/
The advantage of this is that we can group a bunch of shots present spatially close in time and expect nearly good "uniform coverage still", sorta similar to 3) and 4).
@philouc when it comes to shot order atleast, I feel these methods are way better than what we used to do. I plan to take these methods in as good SPARKLING initalizers eventually

Coming to the examples, maybe we come up with "Trajectories" gallery which is more automatized? This could be a subject of another PR , which brings get_trajectory in place. WDYT @paquiteau

Thanks @chaithyagr ; SHould we put that in the Maxime's plate for fMRI?

I think with the help of SHFJ (its a work from their team) we could see if we can get their implementations up. This could be a good oppurtunity for them to showcase their work and also foster better collaboration!

This PR can be closed, as a cleaner version is available in PR #115.


feat: full docker containerization

What does this change?
I wanted to compare giant with aleph and datashare and found it's pretty hard to run giant, so I made a Dockerfile for it to run everything with single command.
How to test
Run docker compose up in root, then visit http://localhost:9001
Have we considered potential risks?
I also fixed package-lock in frontend (it missed hash for one dep so it was not installable with npm ci, also I run npm audit fix and updated caniuse-lite db).
For postgres/migrate-db, I added postgrator-cli to run migration easily and without custom script.
Also I made docker image with java17 because it's default java in debian bookworm (current stable), this forced me to remove some deprecated cli opts not supported anymore in java17. If you still need it to run on java11 with this options, should they be moved somewhere else?
Some config options also became configurable via ENV and default endpoints changed from localhost to docker-compose hosts.
Deps in docker-compose were updated to latest non-breaking change.

Thanks for this @komachi! We'll go through this PR this week. At a quick glance looks like a whole bunch of very helpful changes, we'll just need to review to check for compatibility with our production cluster.


[flash_ctrl] Update bank erase assertion

fixes #11309

Signed-off-by: Timothy Chen<EMAIL_ADDRESS>

@tjaychen : Now test is failing for something which was passing before:
xmsim: *E,ASRTST (/scratch/google/goo_opentitan/nikolam/flash_ctrl_mp_regions/flash_ctrl_wrapper-sim-xcelium/default/src/lowrisc_prim_fifo_0/rtl/prim_fifo_sync.sv,175): (time 9126167 PS) Assertion tb.dut.u_rd_fifo.RvalidKnown_A has failed
UVM_ERROR @   9126167 ps: (prim_fifo_sync.sv:175) [ASSERT FAILED] RvalidKnown_A

@tjaychen : Now test is failing for something which was passing before: xmsim: *E,ASRTST (/scratch/google/goo_opentitan/nikolam/flash_ctrl_mp_regions/flash_ctrl_wrapper-sim-xcelium/default/src/lowrisc_prim_fifo_0/rtl/prim_fifo_sync.sv,175): (time 9126167 PS) Assertion tb.dut.u_rd_fifo.RvalidKnown_A has failed UVM_ERROR @ 9126167 ps: (prim_fifo_sync.sv:175) [ASSERT FAILED] RvalidKnown_A

@nikola-miladinovic could you send instructions on how to reproduce?

@nikola-miladinovic could you rebase your flash_mp_regions test onto master first?
I was having some rebase conflicts when I pulled it down to head of tree.  I couldn't reproduce in my area with a reseed of 25, so maybe it's best if you bring it to top of tree first.

@tjaychen : I have done rebase and prepare test - https://github.com/nikola-miladinovic/opentitan/tree/flash_ctrl_mp_regions. Execute any seed and observe "bank_erase_en". First it is set to 2'b11 and that part of test is passing but the other where it is set to 2'b00 test fails - UVM_ERROR @<PHONE_NUMBER> ps: (flash_mp.sv:329) [ASSERT FAILED] BankEraseInfo_a.

@tjaychen : For now 3 tests passed with run of ~3h per each. Now regression of 8 tests is started and tomorrow it will be finished. After that I will know finally if all OK.

wow that's...really slow. Are you having the same issues as @TimEwins in terms of timing? Because yesterday I ran 25 tests that took an hour at most.
If your local environment different in terms of iterations?

Entire bank is programmed,erased and read. This takes time,especially when there is 256 pages.

merging this first and will debug latest issues separately.


add modals

Add a basic modal and a modal with form.
Maybe they could be combined using an Option ?
e.g.
{ if !self.props.form.is_some() {html!{

                    { for self.props.form.iter() }

}} else {html!{}}}

It seems like the only differences are in the id fo the html element. I am not sure if the CSS would be happy using the with-form variant without a form inside, I haven't tried yet.

I took a quick look at the HTML demos … https://www.patternfly.org/v4/components/modal/html-demos
It looks to me like as if there is always a pf-c-modal-box__body, and sometimes even two.
So maybe an alternative would be to use the children property (which is a bit special) as a "list of bodies" and auto-wrap them with
? So each child would gets it own wrapper. But you could still only add a single child.

like this ?
                { for self.props.children.iter().map(|c|{
                   {html!{

{c}

                       }}
                }) }
                ```


Show vulnerability severity value in Web-App-Reporter

When using the scan-report-web-app.html, it gives a good overview of security vulnerabilities, but only coloured icons indicate the severity. The actual value can only be found out in the AsciiDoc_vulnerability_report.pdf.
It would be nice to have a new column where the severity provided by the security provider is displayed.

I would prefer to implement this as a tooltip instead of a separate column. As a workaround you can click on the column filter, there it shows the icons and the associated severities.
The same applies not only to the vulnerability severity but also to issues and rule violations.

I think you're right - "Tooltip"/"Mouse over" would do the trick
At least for the user it would be great to get a feeling about the real values ❤
I was also thinking about showing two values - Depending on the applied Vuln. Databases values could differ and therefor a "Min" and "Max" value would be great.
The attached picture contains the initially proposed "column-based-solution" but would also apply to Tooltips ;-)

The "column-based-solution" would be nice! Any updates on this?


Anyone know if this will work with Pi Camera v2?

Just wondering if this will work with the latest version of the Pi camera?
cheers
Chris

+1

https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=145815#p960956

Thanks @6by9 I'll get one of the new cameras to play with then :)

I have just tested the new camera with picamera v1.10.
Works (after update of rasbian and firmware) ok!
What sticks out:

image is horizontally flipped with mine and i used to need to do a 180 rotation, now 180 rotation not needed but hflip=True is needed
think the modes (resolutions) in 1.10 do not support V2 camera yet...

Is there an update of picamera expected that will support V2 functionality of the camera?

HFlip is a firmware issue that has been fixed. sudo rpi-update.
It was actually missing a VFLIP - H+V = rotate 180.
Likewise the modes currently don't match up - read https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=145815 for the current mode list.
There will be a firmware update hopefully within the next week which will align them slightly more closely (obviously 8MP instead of 5, and the exact frame rates/resolution combinations will vary slightly).

@partach yup, working on the update at the moment - the Pi foundation were kind enough to furnish me with a couple of v2 cameras a couple of weeks back which I've been playing with. 1.11 will support the new resolutions, but I'd like to wait for the sensor mode updates (if only so I can get them in the docs prior to the release).

@waveform80 great news and great work :)
I have now installed 3 new cameras (replacing the v1.3) for my home security system with the RPIs. Did a latest update today of the RPI firmware.
(@6by9: that indeed solved the problem for the single one that was flipped and rotated)
Current things that seem not working for me that well yet for the last couple of days:

Exposure_mode 'night' does not work well on V2 (does not seem to work at all really). With the v1.3 there was a very noticable difference.
When exposure_mode is set to auto (in the morning, see note below) the camera gets very over exposed  when the sun rises  (almost white screen, nothing visible). It takes some time for the camera (few hours) to recover automatically.
As with v1.3 i take a snapshot each second with the camera that i can see on an ipad with a regular camera view app. Every 10-30 seconds one of the pics is garbled in different ways each time. I wonder if that is a camera thing or a file system thing (reading the jpg file when it is not fully written?). Not sure if this is related to camera at all but just would like your expertise on this :)

Note:  i have py program that also looks at sunrise and sunsite time and from that sets the exposure_mode twice a day, from auto to night and back.
I did this becuase auto did not work that wel with v1.3 in that it would not automatically go all the way to how far night mode goes.
Hope this helps you too with fixing the open items for V2 :)
Thanks for all your great support guys!

I don't know if it's normal behaviour (haven't tested with a v1.3), but when recording to a circular stream (default bitrate), the 20 seconds parameter (I'm using the 'Recording to a circular stream' basic recipe) turns into more than a minute of footage before the fake motion event. I've set the resolution at 1280x720 and the resulting file weights about 31MB.

@julesrenaud - er, weird place to ask but as it happens: yes, this is normal (read the note at the bottom of the recipe: there's at least 20 seconds of data in the buffer - it's a lower bound calculated from the expected bitrate which may be a massive underestimate if the scene contains little motion or complexity). If you require to copy only the last 20 seconds of the content of the buffer you need to look at the frame timestamps (or wait for 1.11 which includes a new PiCameraCircularIO.copy_to method which accepts a seconds parameter)

@waveform80 Thank you for the response despite my being off topic. I'll wait for 1.11 to try out the copy_to method.

Perhaps the sections referring to the camera LED in http://picamera.readthedocs.io/en/latest/recipes1.html#controlling-the-led and http://picamera.readthedocs.io/en/latest/recipes2.html#using-a-flash-with-the-camera need a small note regarding the lack of LED on the V2 cameras?

Yes - I also need to add something about LED control on the Pi3 (i.e. that I can't yet :)

Pi3 LED control is just being discussed on https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=109137&start=100#p989832, although that's really a comment for #265 (this issue is good at going off topic!)

Closing as this definitely works on the V2 module (the vast majority of the test suite passes - there's a couple of obscure failures, and max. resolution does require gpu_mem increases but that's now added to the docs). It's good enough for 1.11 anyway.


One or more enabled YUM repo are currently unsupported.

Could you please advise how can i resolve these issues?

2023-01-30 11:35:08 [ERROR] 1 package(s) installed from unsupported YUM repo 'ul_auto' from /etc/yum.repos.d/ul_auto.repo
2023-01-30 11:35:08 [ERROR] 4 package(s) installed from unsupported YUM repo 'ul' from /etc/yum.repos.d/ul.repo
2023-01-30 11:35:08 [ERROR] 2 package(s) installed from unsupported YUM repo 'hgdedi' from /etc/yum.repos.d/dedi.repo
2023-01-30 11:35:08 [ERROR] 1 package(s) installed from unsupported YUM repo 'UL_paper_lantern_themes' from /etc/yum.repos.d/UL_paper_lantern_themes.repo
2023-01-30 11:35:08 [ERROR] 2 package(s) installed from unsupported YUM repo 'ul_bluehost' from /etc/yum.repos.d/UL_bluehost.repo
2023-01-30 11:35:08 [WARN] *** Elevation Blocker detected: ***

Can you try delete this repo?
rm /etc/yum.repos.d/ul_auto.repo
rm /etc/yum.repos.d/ul.repo
rm /etc/yum.repos.d/dedi.repo
rm /etc/yum.repos.d/UL_paper_lantern_themes.repo
rm /etc/yum.repos.d/UL_bluehost.repo

Let us know if someone proceed with the upgrade ignoring this warning. I have the same error with with a VPS in Hosgator.

Eu fiz o procedimento ignorando este aviso e estou com problemas, pois só tenho acesso no ssh (ao menos isso). Agora vou ter que abrir um "chamado" como orientou o toddr.


fix minor issues found with static analysis tools

Before submitting the PR please make sure you have run ci scripts:

./ci/build_against_kernel (see --help for all options)
We need backward compatibility and this script is a handy way of testing
build compliance with many kernel versions.
./ci/run_style_check
We want to be as style compliant as possible. Again, this is a handy way of
checking it.

If you have more than one change consider creating separate PRs for them; it
will make the review process much easier. Also provide some description (links
to source code or mailing list are welcome - this might help to understand the
change).
Thanks for the contribution!

Hi,
Great PR :+1:
Can you say what tool did you use for the analysis?

I used coverity, we use it in-house in Canonical to find kernel and security related bugs. I think I mentioned  that these are found using Coverity in the commit messages.

Ah, yes, you did :)


Problems with connection and with tipping

Hello team!
During the test call, there were problems with connection and with tipping:

I used Chrome, Firefox and Brave browsers.

This is a network issue with aeternity middleware


[labs/analzyer]: should support JSDoc types before names

Which package(s) are affected?
Other/unknown (please mention in description)
Description
JSDoc types typically precede the name. See the JSDoc class example:
/** Class representing a point. */
class Point {
    /**
     * Create a point.
     * @param {number} x - The x value.
     * @param {number} y - The y value.
     */
    constructor(x, y) {
        // ...
    }

    /**
     * Get the x value.
     * @return {number} The x value.
     */
    getX() {
        // ...
    }

    /**
     * Get the y value.
     * @return {number} The y value.
     */
    getY() {
        // ...
    }

    /**
     * Convert a string containing two comma-separated numbers into a point.
     * @param {string} str - The string containing two comma-separated numbers.
     * @return {Point} A Point object.
     */
    static fromString(str) {
        // ...
    }
}

Note how github's syntax highlighting (treesitter) correctly identifies the type string.
Now let's paste in a snippet from a test fixture from the analyzer package as of commit 28c33d2
/**
 * A cool custom element.
 *
 * @fires event
 * @fires event-two This is an event
 * @fires event-three - This is another event
 * @fires typed-event {MouseEvent}
 * @fires typed-event-two {MouseEvent} This is a typed event
 * @fires typed-event-three {MouseEvent} - This is another typed event
 * @fires external-custom-event {ExternalCustomEvent} - External custom event
 * @fires local-custom-event {LocalCustomEvent} - Local custom event
 * @fires generic-custom-event {CustomEvent<ExternalClass>} - Generic custom event
 * @fires inline-detail-custom-event {CustomEvent<{ event: MouseEvent; more: { impl: ExternalClass; }; }>} Inline
 * detail custom event description
 * @comment malformed fires tag:
 *
 * @fires
 */
export class ElementA extends LitElement {}

Note that treesitter does not highlight the type strings. If we then correct the type strings, treesitter picks them up:
/**
 * A cool custom element.
 *
 * @fires event
 * @fires event-two This is an event
 * @fires event-three - This is another event
 * @fires {MouseEvent} typed-event
 * @fires {MouseEvent} typed-event-two This is a typed event
 * @fires {MouseEvent} typed-event-three - This is another typed event
 * @fires {ExternalCustomEvent} external-custom-event - External custom event
 * @fires {LocalCustomEvent} local-custom-event - Local custom event
 * @fires {CustomEvent<ExternalClass>} generic-custom-event - Generic custom event
 * @fires {CustomEvent<{ event: MouseEvent; more: { impl: ExternalClass; }; }>} inline-detail-custom-event Inline
 * detail custom event description
 * @comment malformed fires tag:
 *
 * @fires
 */
export class ElementA extends LitElement {}

But analyzer will then produce results like this:
"events": [
  {
    "name": "event",
    "type": {
      "text": "Event"
    }
  },
  {
    "name": "event-two",
    "type": {
      "text": "Event"
    },
    "description": "This is an event"
  },
  {
    "name": "event-three",
    "type": {
      "text": "Event"
    },
    "description": "This is another event"
  },
  {
    "name": "{MouseEvent}",
    "type": {
      "text": "Event"
    },
    "description": "typed-event-three - This is another typed event"
  },
  {
    "name": "{ExternalCustomEvent}",
    "type": {
      "text": "Event"
    },
    "description": "external-custom-event - External custom event"
  },
  {
    "name": "{LocalCustomEvent}",
    "type": {
      "text": "Event"
    },
    "description": "local-custom-event - Local custom event"
  },
  {
    "name": "{CustomEvent<ExternalClass>}",
    "type": {
      "text": "Event"
    },
    "description": "generic-custom-event - Generic custom event"
  },
  {
    "name": "{CustomEvent<{",
    "type": {
      "text": "Event"
    },
    "description": "event: MouseEvent; more: { impl: ExternalClass; }; }>} inline-detail-custom-event Inline\ndetail custom event description"
  }
]

Reproduction
Analyze a class with JSDoc as follows:
/**
 * A cool custom element.
 *
 * @fires event
 * @fires event-two This is an event
 * @fires event-three - This is another event
 * @fires {MouseEvent} typed-event
 * @fires {MouseEvent} typed-event-two This is a typed event
 * @fires {MouseEvent} typed-event-three - This is another typed event
 * @fires {ExternalCustomEvent} external-custom-event - External custom event
 * @fires {LocalCustomEvent} local-custom-event - Local custom event
 * @fires {CustomEvent<ExternalClass>} generic-custom-event - Generic custom event
 * @fires {CustomEvent<{ event: MouseEvent; more: { impl: ExternalClass; }; }>} inline-detail-custom-event Inline
 * detail custom event description
 * @comment malformed fires tag:
 *
 * @fires
 * @cssProp {<color>} --has-syntax
 * @cssProp {<color>} --has-syntax-with-description Description for --has-syntax-with-description
 * with wraparound
 * @cssProp {<color>} --has-syntax-with-description-dash - Description for --has-syntax-with-description-dash
 */
export class ElementA extends LitElement {}

Workaround
There is no workaround for this that I can tell
Is this a regression?
No or unsure. This never worked, or I haven't tried before.
Affected versions
v"@lit-labs/analyzer": "^0.9.0",     "@lit-labs/gen-manifest": "^0.2.4",
Browser/OS/Node environment
Node v18.12.1

Closed by #4132


resin command fails silently if the resinrc.yml is invalid

I tried on windows with the contents RESINRC_RESIN_URL=resinstaging.io

Additional work is done here https://github.com/resin-io-modules/resin-settings-client/pull/40 to make the exception much more informative

This is fixed but not yet released.


Upgrade to json-sKema Library for JSON Schema Validation

According to the documentation, the JSON schema validation is using the Everit library which is currently in maintenance mode.
What are the plans (if any) to migrate to json-sKema?
Unlike the currently library that's used, this one implements the draft 2020-12 specification.

We are currently looking to host JSON Schemas somewhere, and AWS Glue Schema Registry is being considered, but the lack of support for even 2019-09 standard might be a dealbreaker.
Are there any plans/roadmap to support the most recent version of the standard (which is four years old)?


Updates from testing Terraform

This PR has updates I found from testing our Terraform deploy script with Terraform 0.12.29. I ran terraform plan and terraform apply, and validated that an Approzium instance came up with the Authenticator running as configured.
These changes are intended to be included in the 0.2.0 release.

Merging this in so I can continue working on the release branch.


Wrong version value for PKCS#8 output for ed25519 keys?

Hi, using OpenSSL 1.1.1a 20 Nov 2018 on Windows and running the following commands:
```
$ openssl genpkey -algorithm Ed25519 -out ed25519key.pem
$ openssl pkcs8 -topk8 -outform DER -in ed25519key.pem -out ed25519key.pfx -nocrypt
```

I receive an output that I cannot insert into some other crypto libraries (see https://github.com/briansmith/ring/issues/740). The advice is that the version number in the asn.1 output is of an incorrect value. In my understanding, it should be zero. Is this a bug in OpenSSL or is something else amiss here?

Assuming this is a test key you can share, what do you get from:
openssl asn1parse -in ed25519key.pfx -inform DER

and
hexdump -C ed25519key.pfx

For one I just generated I get:
openssl asn1parse -in ed25519key.pfx -inform DER
    0:d=0  hl=2 l=  46 cons: SEQUENCE
    2:d=1  hl=2 l=   1 prim: INTEGER           :00
    5:d=1  hl=2 l=   5 cons: SEQUENCE
    7:d=2  hl=2 l=   3 prim: OBJECT            :ED25519
   12:d=1  hl=2 l=  34 prim: OCTET STRING      [HEX DUMP]:04204E00D60E854B037CC52BD6BFAF6CFD1DD8CB45A955905D19BDD85CFECED8C68F

and
hexdump -C ed25519key.pfx
00000000  30 2e 02 01 00 30 05 06  03 2b 65 70 04 22 04 20  |0....0...+ep.". |
00000010  4e 00 d6 0e 85 4b 03 7c  c5 2b d6 bf af 6c fd 1d  |N....K.|.+...l..|
00000020  d8 cb 45 a9 55 90 5d 19  bd d8 5c fe ce d8 c6 8f  |..E.U.]...\.....|
00000030

Which clearly shows the version as "0" - which seems correct.

Thank you for these commands. Looks like my editor completely messes up binary to hex conversion, very sorry for the noise.


WSL is not loading

Version
Microsoft Windows [Version 10.0.19043.1586]
WSL Version

[ ] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Startup cmd.exe then type in wsl
Expected Behavior
WSL starting up
Actual Behavior
The terminal hangs infinitely.
Diagnostic Logs
No response

Fixed it by disabling then re-enabling wsl


Project Moved

https://github.com/peterwillcn/rails4-autocomplete  Moved to this project(https://github.com/bigtunacan/rails-jquery-autocomplete).  :-)

@peterwillcn Thanks for updating.


Correctly comment or remove Metrics Cache

The base RunInference metrics collector has a cache for metrics loaded during setup.

Either comment why it is necessary or remove it.
Imported from Jira BEAM-14229. Original Jira may contain additional context.
Reported by: Ryan.Thompson.
Subtask of issue #21435

Unable to assign user @ryanthompson591. If able, self-assign, otherwise tag @damccorm so that he can assign you. Because of GitHub's spam prevention system, your activity is required to enable assignment in this repo.


sshcommand acl-add dokku  is not idempotent

If you add the same key multiple times, it will keep creating entries in .ssh/authorized_keys. I suppose that is rarely the expected behaviour so it would be nice to add a quick check to make sure the key doesn't already exist.

This should probably be logged against https://github.com/progrium/sshcommand

Ok thanks, I created an issue there https://github.com/progrium/sshcommand/issues/14


Update example in rs-configuration.md

summary:
Align example with best practices - use "aio:///dev..." instead of "/dev/..."
Background:
In preparation of experimenting with OpenEBS on a home cluster I'm reading the docs. It seems to me that the 'best practice'  in the table at the end of https://openebs.io/docs/user-guides/replicated-storage-user-guide/replicated-pv-mayastor/rs-configuration#create-diskpools does not align with the subsequent example config. The best practice apparently is to prepend the device by aio:///, but in the example this is not done.
I don't know why the aio:/// or uring:/// is better so perhaps someone more knowledgable (e.g. the reviewer of this PR? :-) could add that to the docs.
If I understand the docs correctly, the example should be updated as I have done here. If this is wrong, the docs are unclear on this point and need some further clarification in my opinion.

Disk(non PCI) with disk-by-guid reference (Best Practice)	Device File	aio:///dev/disk/by-id/ OR uring:///dev/disk/by-id/

👍
I will try to get this commit signed properly tomorrow such that the pipeline is happy, again something that GH online editor apparently doesn’t automatically do.

A separate “issue” is in that case that it’s not really clear if there is a preference for a aio (which I take from your answer to be the default?) or uring. Reading up on it it’s clear that there is a difference, but it’s not immediately apparent which is “best” for OpenEBS.
If it’s a topic that may have very different answers depending on specific configuration, that may also be useful to say explicitly (essentially instructing users to run some benchmarks and see what works best for them on their hardware for their workload). Ideally a sensible default should be suggest.

👍 I will try to get this commit signed properly tomorrow such that the pipeline is happy, again something that GH online editor apparently doesn’t automatically do.

That took a bit longer, family fell ill and then I forgot for a while to be honest... Signed off now tho!

A separate “issue” is in that case that it’s not really clear if there is a preference for a aio (which I take from your answer to be the default?) or uring. Reading up on it it’s clear that there is a difference, but it’s not immediately apparent which is “best” for OpenEBS.
If it’s a topic that may have very different answers depending on specific configuration, that may also be useful to say explicitly (essentially instructing users to run some benchmarks and see what works best for them on their hardware for their workload). Ideally a sensible default would be suggested in the docs.
In the end I expect most people will start by copying the example (the bit that I edited), so that should preferably be the “sane default”.

Not sure if there's a best, they are definitely different implementations and uring can yield better performance.
Perhaps we should do some IO tests with various parameters and the different modes (aio/uring/pcie).

👍 I will try to get this commit signed properly tomorrow such that the pipeline is happy, again something that GH online editor apparently doesn’t automatically do.

That took a bit longer, family fell ill and then I forgot for a while to be honest... Signed off now tho!

No worries at all, thank you for updating this and hope all is well with the family!

Would you be able to update the main version of the documentation as well btw?

Hi there Tiago, probably happy to help but not entirely clear what you're asking wrt "the main version"?

Clear now, thanks, and done

Thanks @jcjveraa !


Python 3.7

Issue description
Given that Python 3.7 is no longer supported, will this be removed from the BTP build packs? Also, can instructions on how to reference specific versions of Python be published? The build packs provide all versions, from 3.7 to 3.10, so how to specify a specific version would be very helpful.
Feedback Type (Optional)
other
Page Title on SAP Help Portal (prefilled)
Developing Python in the Cloud Foundry Environment
Page URL on SAP Help Portal (prefilled)
https://help.sap.com/docs/btp/sap-business-technology-platform/developing-python-in-cloud-foundry-environment

Thank you for your feedback! We’ll look into it and come back to you if we have any questions.

Hi @jeffvc,
Thank you for your feedback!
With the latest update of SAP BTP, Python 3.7 is now removed from the documentation. See:  Supported Versions
To learn how to specify a particular buildpack version that contains the Python version(s) you need, see:  Specify a buildpack version in manifest.yml
You can specify a specific Python version for your application in the runtime.txt file. For example:
python-3.11.*
To see a full end-to-end Python tutorial, see: Create an Application with Cloud Foundry Python Buildpack
Hope that helps! 🙂
Best regards,
Gergana


[Subtask][spark-connector] support query on files directly

Describe the subtask
val sqlDF = spark.sql("SELECT * FROM parquet.`examples/src/main/resources/users.parquet`")

Parent issue
#1227

I think we'd better also support gvfs, please think about this.

I think we'd better also support gvfs, please think about this.

ok


Preferences page is unreadable

Background and text do not have readable contrast.

Yeah, I haven't been able to style any of the unibody elements yet (like that preferences page), since this was only tested on MacOS up until now. I should be able to put up some Windows-related styling up soon enough

Just pushed some changes, & it should look alright now. Give it a try and feel free to point out anything off


Added some unit tests for GIN

Description
The GIN algorithm returns the graph and the causal order. In this algorithm, the causal order and the causal graph correspond to each other, so only the causal order in the result is asserted.
Updates

Fixed the independence test problem in GIN
Added assertion to the previous test cases
Removed the plot function in previous test cases for GIN
Added tests to test GIN algorithm using the hsic independence test.
Updated docstring
Removed default parameter of indep_test
Refactored the test code

Test Plan
python -m unittest tests.TestGIN # should pass

Updates

Added tests to test GIN algorithm using the hsic independence test.
Updated docstring
Removed default parameter of indep_test
Fixed tests

Test Plan
python -m unittest tests.TestGIN # should pass

BTW, I really like the three tests you designed. I think that's great. :)
Also a small nit: when you made later changes, you can update your description and test plan instead of commenting a new one --- people will generally read the first one instead of scroll down to check all the conversions. This makes this PR clearer for other people. :)

@zhi-yi-huang do you mind addressing the comments? After that, I think we can merge this PR --- very close now

Sorry, I missed the email from GitHub.

This is awesome! I think this PR is ready to be merged. :)
cc @kunwuz


graphiQl

I've just forked your repo and got the example to appear here:
http://localhost:3000
awesome!
But when I visit http://localhost:3000/graphiql  - I get a 404 - any ideas?
It looks like it could be something with next - in the terminal there is a log about:
Client pings, but there's no entry for page: /graphiql

@headwinds dunno, will look, thanks)


🐛 BUG: wrangler init --yes leads to interactive prompt

Which Cloudflare product(s) does this pertain to?
Wrangler
What version of Wrangler are you using?
3.0.0
What operating system are you using?
Mac
Describe the Bug
Hi, I'm a maintainer for the Homebrew package manager (also a wrangler user) and I was working on updating our formula to version 3.0.0 but I'm encountering a bug with the --yes option of wrangler init.
Our test runs wrangler init --yes, with the expectation that this will not produce any interactive prompts. This worked fine in previous versions but I'm now seeing the following with 3.0.0:
$ wrangler init --yes
 ⛅ wrangler 3.0.0
------------------
Using npm as package manager.
▲ [WARNING] The `init` command is no longer supported. Please use `npm create cloudflare@2` instead.

  The `init` command will be removed in a future version.

Running `npm create<EMAIL_ADDRESS>Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y)

The warning states that init is no longer supported but wrangler --help still lists wrangler init as a command. I figured I would flag this --yes issue if it's something that can/should be fixed.
Otherwise, is there something more appropriate that we could/should be doing to test wrangler as a package manager? This would preferably be something that involves some basic functionality without depending on remote requests, authentication, etc. wrangler init was fine for our purposes but we may have to fall back to wrangler --version (which we try to avoid) if init will be removed in the future and there isn't a suitable alternative command to test.

Thanks for raising this! The --yes flag not being respected is a regression in v3 that we'll be fixing in a future version. However, as the warning notes, wrangler init will be deprecated in a future version (in favour of npm create cloudflare), and so it's probably not a good long term way to test a Wrangler installation. I think wrangler --version is probably the best option for now—a lot of Wrangler's functionality relies on remote calls to the Cloudflare API, or expects user interactive.
As a side note, I notice that the brew package is called cloudflare-wrangler2—is there any way that could be changed to wrangler? It could be fairly confusing to users to have Wrangler v3 installed by a package called wrangler2

Thanks for confirming. Due to the --yes behavior in 3.0.0, I think we'll have to fall back to wrangler --version in this version and we'll probably end up having to stick with that. After looking at the existing wrangler commands, it does appear that everything else (excluding init) involves network requests or some interactivity.

Regarding the cloudflare-wrangler2 formula name, I agree that it's not ideal but there are technical reasons for it. Homebrew has had a wrangler formula since at least 2009, so we had to use cloudflare-wrangler for the initial Rust 1.x versions. When the JavaScript 2.0.0 version was released, we had to create a separate formula for it, as both the Rust and JS versions were being maintained and there were users of both. The JS version was in the cloudflare/wrangler2 repository (though the command was still wrangler), so we followed the upstream naming convention and named the formula cloudflare-wrangler2.
At this point, we have a deprecated cloudflare-wrangler formula and cloudflare-wrangler2 formula, so we can't rename the latter to the former and are probably unlikely to do so until after 2023-08-01 (when v1 becomes officially unsupported by Cloudflare). In the interim time, I've suggested renaming the formula to either cloudflare-wrangler3 or something unversioned like cloudflare-wrangler-js until the Rust formula is eventually deleted and we can even consider the possibility of using cloudflare-wrangler for this formula.
It's not an ideal situation but hopefully that explains why this formula is named the way that it is and why we can't easily rename it to cloudflare-wrangler (let alone wrangler).

@samford Thanks for clarifying the naming, and that makes sense. I don't know what Homebrew's policy is on re-naming formulas, but would something like renaming cloudflare-wrangler to cloudflare-wrangler-legacy and cloudflare-wrangler2 to cloudflare-wrangler work?

Personal addition, I use wrangler init -y all the time when creating new projects.
I haven't moved to v3 yet so this luckily hasn't impacted me so far but, it would be good to know what I'm supposed to do. The warning says to do npm create cloudflare@2 but doing npm create cloudflare@2 -y just brings an interactive prompt, going through doesn't result in the same thing either (I can't have a vitest test created)
In v2, init was made to be really powerful, I'd personally love for that to stay or c3 to do the exact same (right now at the very least, it's missing non-interactive and testing).
Also small nit, wrangler.toml from create cloudflare is interesting... I'm gonna be deleting 80% of it every time. I'd personally just rather a comment saying like "see the docs for information on how to configure your wrangler.toml: "
I can see the current one being quite overwhelming.

The init command with the -y flag should be non-interactive since this fix https://github.com/cloudflare/workers-sdk/pull/3359 – can you confirm this fix works for your use-case?

The init command with the -y flag should be non-interactive since this fix #3359 – can you confirm this fix works for your use-case?

Unfortunately this still leads to the same interactive prompt on 3.1.1 for me:
$ wrangler init -y
 ⛅ wrangler 3.1.1
------------------
Using npm as package manager.
▲ [WARNING] The `init` command is no longer supported. Please use `npm create cloudflare@2 -- --wrangler-defaults` instead.

  The `init` command will be removed in a future version.

Running `npm create cloudflare@2 -- --wrangler-defaults`...
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y)


Drop curl for external settings

I can’t afford having 2 hours window for getting artifacts from the mirror after they get out, see https://travis-ci.community/t/disable-google-maven-central/5301

Then

have empty settings.xml, as there is no need to redefine jakarta repos
have that settings.xml file in this Eclipse's repository, and not in project-external location.

Then

have empty settings.xml, as there is no need to redefine jakarta repos
have that settings.xml file in this Eclipse's repository, and not in project-external location.

... and apply and maintain the same, likely temporary file which is to go away/become unused in a few weeks, in >15 more repositories. I do not think I'm willing to do that. What I need right now is something allowing me to get from 1st repo to the last in less than a day while not having to run all tests and checks locally and not breaking anything.

Thanks for sharing. All comments together are quite different than initial

travis mirrors everything through some global mirror, so whatever is set in project poms, is by passed

travis mirrors everything through some global mirror, so whatever is set in project poms, is by passed

travis is apparently evolving ;-)


Determine if project is amethyst or not

This issue is for discussion on the way that we should determine if we are in an amethyst project directory or not. Related to #25.

Since we've discussed and merged #25, I think we can mark this issue as resolved.

This still needs some more discussion in how we detect the validity of a given config.yml file and resources directory structure.

@ebkalderon Is there a set of options that are guaranteed to be used in any given game? Things like title might not be used (e.g. CLI game).

@ogoding you can discuss ut here https://github.com/amethyst/amethyst/issues/29

@White-Oak Whoops, sorry. Will repost my comment there.

Closing until we can demonstrate why this is necesary


Dockerfile with Python client and dependencies

Using this file, the client can be set up more easily. Having Docker installed, it is just "docker build . -t neo-python" from the main directory of the repository and "docker run -it neo-python" to start the client.

Coverage remained the same at 57.877% when pulling fbf9c3c769dae311b0283057069b3bffbcda20d0 on JorritvandenBerg:patch-2 into 3875c64a6919af70724522e379a6a156b8b82b24 on CityOfZion:master.

Hi JorritvandenBerg,
Docker file looks good!  Could you perhaps make a pull request against the development branch instead of master?
Going forward we will have all PRS go through development.
Thanks!


using commas in nagios_service "check_command" option breaks stuff unexpectedly

example (_check-test.rb):
nagios_command 'system-load' do
  options 'command_line'    => '$USER1$/check_load -w $ARG1$ -c $ARG2$'
end

nagios_service 'system-load' do
  options 'check_command'       => 'system-load!15,10,5!30,25,20',
          'use'                 => 'default-service',
          'hostgroup_name'      => 'linux'
end

results in this in services.cfg:
define service {
  use                  default-service
  service_description  system-load
  hostgroup_name       linux
  check_command        20
}

Also, something else funky is happening, as I see this show up in the commands.cfg file:
# Skipping 10 because command_line is missing.

# Skipping 20 because command_line is missing.

# Skipping 25 because command_line is missing.

# Skipping 5!30 because command_line is missing.

# Skipping system-load!15 because command_line is missing.

If I drop the commas from the check_command option, everything works as expected: with the exception that I still see a comment in the commands.cfg file:
# Skipping system-load!15!30 because command_line is missing.
I'm not sure if other characters or symbols might break as well.  I'm still researching, but wanted to report the issue.

Thats indeed strange behaviour.. Will need to investigate why this happens...
Please let me know if you find some pointers

In regards to the odd output in commands.cfg, it looks like the check_command option is mistaken for a nagios_command stanza during the find_object phase in libraries/nagios.rb
using -l debug switch during kitchen converge:
   [2015-08-17T21:29:22+00:00] DEBUG: Loading Recipe tec-nagios::_checks-test via include_recipe
   [2015-08-17T21:29:22+00:00] DEBUG: Found recipe _checks-test in cookbook tec-nagios
   [2015-08-17T21:29:22+00:00] DEBUG: Nagios debug: Creating entry for Nagios::Command with name: system-load
   [2015-08-17T21:29:22+00:00] DEBUG: Nagios debug: Creating entry for Nagios::Service with name: system-load
   [2015-08-17T21:29:22+00:00] DEBUG: Nagios debug: Found entry for Nagios::Hostgroup with name: linux
   [2015-08-17T21:29:22+00:00] DEBUG: Nagios debug: Creating entry for Nagios::Command with name: system-load!15
   [2015-08-17T21:29:22+00:00] DEBUG: Nagios debug: Creating entry for Nagios::Command with name: 10
   [2015-08-17T21:29:22+00:00] DEBUG: Nagios debug: Creating entry for Nagios::Command with name: 5!30
   [2015-08-17T21:29:22+00:00] DEBUG: Nagios debug: Creating entry for Nagios::Command with name: 25
   [2015-08-17T21:29:22+00:00] DEBUG: Nagios debug: Creating entry for Nagios::Command with name: 20

While I admit that the behaviour is not correct, can you please explain what you are trying to achieve?
Because I'm wondering why you use 'system-load!15,10,5!30,25,20' as the command name.
This could be the command line that you want to execute, but I cannot find any command named like that.

that is the check_command (with arguments) for that service.  I am not using that as a command name.  I updated my example recipe above in hopes that it will clarify.

Got it..... And that functionality indeed doesn't work at the moment.
I have not tested anything with this kind of format, so we will need to add that..

What you can try in the meantime is escaping the ! and , with an
That might do the trick...

that was the first thing I thought to try :)
Doesn't fix :(

@TheCase can you try the branch: https://github.com/schubergphilis/nagios/tree/enable_service_arguments
I think that should fix your problem, but need to review the impact of this.
Also still need to write some tests for it, but did some local testing and seems to work fine.
Please let me know how this works out for you....

While driving home I thought about this and think I made the wrong decision by adding the arguments to the command, while they should be part of the service. That would make more sense I think.. Will need to update the branch with that logic, but that I will do later tonight...

yeah - that fixed it, and I'm still using the same options as listed in the first post.
Still curious as to why the 'check_command' line is getting picked up as a nagios_command without a command_line option:
in commands.cfg:
# Skipping system-load because command_line is missing.

I have updated the branch. Can you test again because I think this will also fix your missing line as here above.
Only have the problem that if you don't specify the command separately and define everything within the service, that it will break the nagios config because the service name will be wrong.
But fixing that will be the next step...

On the other hand, this should be sufficient for now.
I was still thinking about something like this, for example you specify this within your cookbook:
nagios_service 'system-load!15,10,5!30,25,20' do
  options 'use'                 => 'default-service',
          'hostgroup_name'      => 'linux'
          'command_line'        => '$USER1$/check_load -w $ARG1$ -c $ARG2$'
end

With the current setup, this goes correct but your service name will contain illegal values.
So will need to parse this and replace the illegal values to _ or something.....
But then you will end-up with names that nobody wants any way.
So defining the command first like you do and then create the service, gives you the possibility to specify any kind of name you want. And this will look something like:
nagios_command 'system-load' do
  options 'command_line'    => '$USER1$/check_load -w $ARG1$ -c $ARG2$'
end

nagios_service 'system-high-load' do
  options 'check_command'       => 'system-load!20,15,10!40,35,30',
          'use'                 => 'default-service',
          'hostgroup_name'      => 'high_load_servers'
end

nagios_service 'system-medium-load' do
  options 'check_command'       => 'system-load!15,10,5!30,25,20',
          'use'                 => 'default-service',
          'hostgroup_name'      => 'medium_load_servers'
end

And since this is also a bit more advanced, not a lot of people will use the feature I guess.
Next to that, chef is generating the config anyway, so not having the arguments option will not be that big of a deal I assume.
Will try to write some test for this, so that some variations will be tested. And if you want to help me out on this, please feel free to add some :)
Gr Sander

@TheCase do you have any comments on this? And did you manage to test the updated branch?

I haven't had time to test.  Hopefully some time this week.

I haven't had time to test.  Maybe some time this week.

made some time for this.  It is not working correctly.  Anything after the first bang in the check_command option is now truncated.  Your test stanzas above create the following in services.cfg:
define service {
  use                  default-service
  service_description  system-high-load
  hostgroup_name      high_load_servers
  check_command        system-load
}

define service {
  use                  default-service
  service_description  system-medium-load
  hostgroup_name      medium_load_servers
  check_command        system-load
}

@TheCase thank you for the feedback, I will need to review why this goes wrong :(

@TheCase I have fixed the problem and also added some test kitchen checks.
Can you test again please :)

created PR #416 for this issue..

yes - tests look good.  Thanks!


Added support for generating QTS Certificates for teachers exempt from induction

Context
Teachers who are exempt from induction should get a different QTS certificate than those that are required to do induction.
Changes proposed in this pull request
Changes to V3 API endpoints to generate PDF using appropriated template + some changes to NOT allow downloading certificates for teachers who have qualified in Wales.
Guidance to review
N/A
Checklist

[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Access Quals/ID snags


Custom skim action from library

I'm trying to bind a few custom keys from a skim selector. I'm new to the skim library crate, and relatively new to Rust in general. I found how to bind internal actions in skim, with something like:
let options = SkimOptionsBuilder::default()
    .height(Some("50%"))
    .multi(false)
    .bind(vec!["alt-a:accept"])
    .build()
    .unwrap();

That works fine. However, I want to bind keys to functions external to skim. Given the function  other_skim_action(), I'd like to be able to
    .bind(vec!["alt-a:other_skim_action"])

or something similar. If there's a way to pass arguments that would be even better, but if not just being able to call a function would be sufficient. Does skim's library provide a way to accomplish this? Thanks!!

What would you want to achieve ? We could think about implementing this, but you'd need access to quite a lot of components inside skim, which is not easy


Shogun 2 schemas out of date/missing values

Shogun 2 schemas appear to be missing database information compared to the Assembly Kit files and how they appear in DAVE. Other values do exist in the schema but are recorded under incorrect or different names, or their default values vary (like some boolean values having a default of 0 rather than false).
As an example, loading the units table in DAVE there are quite few differences from the schema provided with RPFM. The fitness and era columns are missing, the pdlc column is missing (though it is blank in every base-game unit) and upkeep_cost is labeled as unkeep. The vo_actor_numbers value is also labeled as having a default value of None when according to DAVE it should be "0". There are similarly strange issues in the unit_stats_land table, where (what I assume are supposed to be) dismounted_loose_formation_* values are called loose_loose_formation_* in the schema. fatigue_resistant is called fatigue_resistance, is_immune_to_attrition is called is_inmune_to_attrition, etc. On top of all this, almost every table I've loaded in RPFM has a different and much more nonsensical column order.
Although I can't be certain, I noticed the game hard-crashing at load with database info that previously seemed to work fine in TWEAK which is not something I've ever seen Shogun 2 do, and I suspect it may be because of this (the dumps record a division by zero error).

Update: The divide-by-zero error turned out to be decidedly not caused by the schema, it was my own stupidity. I am still leaving the issue up as the other problems still remain, though I'm back to being unclear on whether or not they have any real effect.


fix: broken brand logo image carousal effect on homepage 🧑🏻🏭🛠

Close #1351
Description

This PR fixes the broken brand logo image carousal effect on Sponsers section of OS-CODE Homepage

Screenshots

Checklist:

[x] I have linked the PR to the correct issue.
[x] I have read the Contribution Guidelines
[x] I have built and tested the changes, and they do not break or show any errors.

@Vaishnavi-Patil2211 Your review is highly appreciated 🙌🏻


Weakly clean but not clean

On the "Suggested additions" page, an example of a weakly clean but not clean ring is asked for.
On page 1599 of J. Ster. "Corner rings of a clean ring need not be clean" (2012) a proof is given that Ring 70 (Bergman's exchange ring that isn't clean) is weakly clean, so assuming it is correct, then this provides an example.
But on the "Ring detail" page for Ring 70, that paper is already cited, so maybe you know of some problem with the proof?
By the way, I got quite confused by the fact that there are two meanings of "weakly clean" in the literature, which are not equivalent. The other one is that every element is either the sum u+e or the difference u-e of a unit u and an idempotent e. Probably you're aware of this, but if not then it might be something to be careful about.

The paper's already cited because its main example was used for https://ringtheory.herokuapp.com/rings/ring/67/ . At this point I do not know of any problems with Ster's work, but when I do find something I put it in the errata part of the website.
I did not know of the difference definition, but I think the two definitions are manifestly equivalent, no?
Suppose all elements are u+e clean.   Then for an arbitrary element x, -x=u+e, implies x=(-u)-e which is a difference of a unit and idempotent.   Likewise if they are all u-e clean, then for a given element -x=u-e -> x=-u+e is clean, a sum of a unit and idempotent.
I will look into the first thing!  In focusing on the main example I probably overlooked that comment.

Sorry, I didn't write that very clearly. I meant that every element is either a sum u+e or a difference u-e, but some elements can be sums and others can be differences.
I found a simple example of "weakly clean but not clean" in a paper that used that definition of "weakly clean". Let R be the ring of rationals whose denominator is divisible by neither 3 nor by 5. It's not clean, since 6 cannot be written as u+e, but is weakly clean by this alternative definition (for any x, at least one of x-1, x, x+1 must be a unit). I didn't realise they were using a different definition, and was confused becuase I was fairly sure that I could show that it is not weakly clean. And indeed, if you use DaRT's definition, it is not weakly clean.

Oh!  Yeah, I've never heard that one...  I'll stay on guard for that confusion in the future.


Screenshot (Jan 17, 2022 4:12:54 PM)

Termux-url-opener

Explain

ed.
HTTP request sent, awaiting response... 200 OK          Length: unspecified [text/plain]                        Saving to: ‘/data/data/com.termux/files/home/bin/termux-url-opener’

Setting Up Storage ...
Please Allow Storage Access!
It appears that directory '~/storage' already exists.   This script is
going to rebuild its structure from
scratch, wiping all dangling files. The actual storage
content IS NOT going to be deleted.
Do you want to continue? (y/n) y
Please Wait ...                                        mkdir: cannot
create directory
‘/data/data/com.termux/files/home/storage/shared/YouTube-DL’: File exists
mkdir: cannot create directory
‘/data/data/com.termux/files/home/bin’: File exists
--2022-01-17 16:20:20--  https://pastebin.com/raw/dqBrGtRP
Resolving pastebin.com...
<IP_ADDRESS>, <IP_ADDRESS>, 2606:4700:10::6817:62be, ...
Connecting to pastebin.com|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK          Length: unspecified
[text/plain]                        Saving to:
‘/data/data/com.termux/files/home/bin/termux-url-opener’
/data/data/co        2.58K  --.-KB/s    in 0s
2022-01-17 16:20:26 (23.6 MB/s) -
‘/data/data/com.termux/files/home/bin/termux-url-opener’ saved [2647]
On Mon, Jan 17, 2022, 4:18 PM Team Ezra @.***> wrote:

Closed #5 https://github.com/teamezra/ezrayt-dl/issues/5.
—
Reply to this email directly, view it on GitHub
https://github.com/teamezra/ezrayt-dl/issues/5#event-5902537507, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJJO7QA4OBNTVNF3AHHIOHDUWPGEXANCNFSM5MEAOS7Q
.
You are receiving this because you authored the thread.Message ID:
@.***>


Fix segfault in get_ao_compression_ratio (#907)

Problem:
Segfault happened in the queries with 'get_ao_compression_ratio' function in the target list and the argument for this function that was taken from a table. The problem was reproduced in the release build. In the development build the same queries led to assertion.
Cause:
Function 'get_ao_compression_ratio' executes a query on 'pg_aoseg.pg_aoseg_' table to calculate the compression ratio. A function that accesses hash-distributed or randomly distributed tables must be executed on coordinator. But the planner created plans with the 'get_ao_compression_ratio' function which was executed on segments. Inside 'get_ao_compression_ratio' there was an assert to check this case, but on the release build the assert was removed. So, the code of the function was executed on a segment and got unexpected results from 'pg_aoseg.pg_aoseg_', that led to a segfault.
Fix:
Assert is changed to a runtime check. Now, if the planner creates a plan with the function which is executed on segments, the user will get a proper error message. It is also done for the similar functions 'gp_update_ao_master_stats' and 'get_ao_distribution'. Plus, unreachable code is removed from internal functions.
Note: it seems that a fully proper way would be to mark these functions as PROEXECLOCATION_MASTER instead of PROEXECLOCATION_ANY, but that would require changing of the system catalog, and it is acceptable only between major versions update. So this approach is not used.
Note2: for an empty column-oriented table 'get_ao_compression_ratio' returns -1, but for an empty row-oriented table 'get_ao_compression_ratio' returns 1. This behavior is inconsistent, but it is not altered by this commit as not related to the original issue. It has a reflection in the added test case. Be aware.

use -x option with cherry-pick

rebase to 7.2.0

Please fix the PR description, or, if commits shouldn't be squashed, all the commits's descriptions should be properly formatted and fully documented.

@dkovalev1  Please use -x option with cherry-pick to preserve authorship and place a note in the description that commits shouldn't be squashed.

bender build


upgrade search by Id

add clearer logic and remove unnecessary additional functions, bring everything into a more compact form

[x] FastIdPeople->People
[ ] FastIdClub->SearchClubAnime->SearchClubMangas->SearchClubMemebers->SearchClubCharacters->SearchClubClubs->SearchClubImages->SearchClubCollections->ClubJoin->ClubLeave
[ ] FastIdManga->SearchMagaExternalLinks->SearchMangaFranchise->SearchRelatedManga->SearchMangaRoles->SearchSimilarManga
[ ] FastIdAnime->SearchAnimeExternalLinks->SearchAnimeFranchise->SearchRelatedAnime->SearchAnimeRoles->SearchSimilarAnime

FastIdAnime; FastIdManga; FastIdClub; FastIdPeople;
If the result is not found, we get zero slice and panic.


[BUG] Intermediate bool value cast as PyObject * and DECREFed

Describe the bug
In the result of the example code given below, I get:
  /* "test.pyx":10
 *
 * def f2(x):
 * 	f1(False if x is None else x)             # <<<<<<<<<<<<<<
 *
 * f2(None)
 */
  __pyx_t_2 = (__pyx_v_x == Py_None);
  if (__pyx_t_2) {
    __pyx_t_1 = ((PyObject *)0);
  } else {
    __pyx_t_3 = __Pyx_PyInt_As_bool(__pyx_v_x); if (unlikely((__pyx_t_3 == ((bool)-1)) && PyErr_Occurred())) __PYX_ERR(0, 10, __pyx_L1_error)
    __pyx_t_1 = ((PyObject *)__pyx_t_3);
  }
  __pyx_t_4 = __pyx_f_4test_f1(((bool)__pyx_t_1)); if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 10, __pyx_L1_error)
  __Pyx_GOTREF(__pyx_t_4);
  __Pyx_DECREF(__pyx_t_1); __pyx_t_1 = 0;
  __Pyx_DECREF(__pyx_t_4); __pyx_t_4 = 0;

So it's taking the bool from the if expression (0 or __pyx_t_3, depending on the branch), and casting it to a PyObject * (__pyx_t_1). Then later it casts the pointer back into a bool to pass it to the function, which works, but afterwards it tries to call __Pyx_DECREF on it, causing a segfault.
Code to reproduce the behaviour:
# cython: language_level=3

cdef extern from "<stdbool.h>":
	ctypedef int bool

cdef f1(bool x):
	pass

def f2(x):
	f1(False if x is None else x)

f2(None)

Built with cython --embed
Expected behaviour
In the C code above, __pyx_t_1 should be a bool.
OS
Linux
Python version
3.9.18
Cython version
3.0.2
Additional context
No response

It's in 0.29.x too so doesn't appear to be a regression. The typedef also isn't relevant - just defining f1 as int works the same.

There's also two issues
    __pyx_t_1 = ((PyObject *)__pyx_t_3);

is also wrong


Serving static file using async functions

Fixes #43

This approach is slower even for large files.
But this approach helped me find that the html service files are not robust enough.
fn read_file(file_path: &str) -> String {
    let mut file = File::open(file_path).unwrap();
    let mut buf = vec![];
    file.read_to_end(&mut buf).unwrap();
    String::from_utf8_lossy(&buf).to_string()
}

This should be the real implementation.

This was a bad idea. Clearly slower in all the cases. It helped us identify a flaw so not too bad.
We will add the option to mount the folder once we switch to actix.


CA certificate from secret is not served

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
I did create an secret with cert-manager which contains the server certificate and the ca certificate.
apiVersion: v1
data:
  ca.crt: LS0tLS...
  tls.crt: LS0tLS...
  tls.key: LS0tLS...
kind: Secret

After adding an IngressRoute with secretName set, I call "openssl s_client" to fetch the certificates from the https port.
What did you see instead?
"openssl s_client" only shows the "tls.crt" certificate, the "ca.crt" certificate is missing.
What version of Traefik are you using?
rancher/mirrored-library-traefik:2.6.2
What is your environment & configuration?
apiVersion: v1
kind: Secret
metadata:
  name: ca-key-pair
  namespace: cert-manager
data:
  tls.crt: LS0tLS1CRUd...
  tls.key: LS0tLS1CRUd...
---
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: cert-manager-issuer
  namespace: cert-manager
spec:
  ca:
    secretName: ca-key-pair
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: web-certificate
  namespace: web-namespace
spec:
  commonName: kunde.tld
  duration: 8760h
  dnsNames:
    - kunde.tld
  secretName: web-certificate
  issuerRef:
    name: cert-manager-issuer
    kind: ClusterIssuer
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: web
  namespace: web-namespace
spec:
  entryPoints:
    - web
    - websecure
  routes:
    - match: Host(`kunde.tld`)
      kind: Rule
      services:
        - name: backend
          port: 80
  tls:
    secretName: web-certificate

If applicable, please paste the log output in DEBUG level
No response

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.


Windows from the special workspace loose their focus when switching workspaces

Hyprland Version
Hyprland, built from branch HEAD at commit 3bb9c7c5cf4f2ee30bf821501499f2308d616f94  (props: bump ver to 0.33.0). Tag: v0.33.0  flags: (if any)
Bug or Regression?
Bug
Description
Windows from the special workspace loose their focus when switching workspaces.
How to reproduce

Use empty/default Hyprland config.
Press SUPER+Q (run kitty).
Run from kitty's prompt: hyprctl dispatch togglespecialworkspace.
Press SUPER+Q (run another kitty instance in the special workspace).
Switch around workspaces with SUPER+1, SUPER+2, SUPER+1.

Kitty's window in the special workspace should retain its focus when switching workspaces, but it doesn't.
Crash reports, logs, images, videos
No response

I think this can be closed now.

@dranull, I will close the issue when I verify it in the next release.

it's fixed in git, I will not wait for the next release. Feel free to reopen if the issue arises again


Invalid linker library in README.md for compiling MLIR -> native

I believe the command to compile to native program is outdated in the ##From MLIR to native binary section in README.md.
# compile natively
"$MLIR_SYS_180_PREFIX"/bin/clang program.ll -Wno-override-module \
    -L "$MLIR_SYS_180_PREFIX"/lib -L"./target/release/" \
    -lsierra2mlir_utils -lmlir_c_runner_utils \
    -Wl,-rpath "$MLIR_SYS_180_PREFIX"/lib \
    -Wl,-rpath ./target/release/ \
    -o program

Here, I think -lsierra2mlir_utils should be -lcairo_native_runtime

Good catch! want to send a PR correcting it or should we go ahead and fix it quick?

@igaray, actually, running this command by itself does not work out of the box. I had to write a wrapper C file to set it up. Is this intended?
For example, here is the command I ran for simple Cairo file compiled down to Sierra.
// example.cairo
fn main() -> u32 {
    println!("hello world");
    1
}

// wrapper.c
#include <stdint.h>

extern void alias_example_main(int64_t, __int128);

int main() {
    int64_t arg0 = 0;
    __int128 arg1 = 0;
    alias_example_main(arg0, arg1);
    return 0;
}

// program.ll

// v added this line
@alias_example_main = alias { i64, i128, { i64, [24 x i8] } } (i64, i128), void (i64, i128)* @"example::example::main(f15270207278767002344)"

// main function definition
define { i64, i128, { i64, [24 x i8] } } @"example::example::main(f15270207278767002344)"(i64 %0, i128 %1) {
// ...

clang wrapper.c program.ll -Wno-override-module \
    -L "$MLIR_SYS_180_PREFIX"/lib -L"./target/release/" \
    -lcairo_native_runtime -lmlir_c_runner_utils \
    -Wl,-rpath "$MLIR_SYS_180_PREFIX"/lib \
    -Wl,-rpath ./target/release/ \
    -o program

Even though I could compile the file, I still get a segfault 56807 segmentation fault  ./program.

actually, running this command by itself does not work out of the box. I had to write a wrapper C file to set it up. Is this intended?
It's not whether it's intended or not, but rather:

Cairo always generates function names with their module, therefore it's impossible to have a main function.
Any non-trivial program will require gas and builtins, which do not exist in C, making the interface not work even if we solved the first problem.

As for your test program, try compiling it to Sierra and checking its function signature. In your case it's the following:
sample::sample::main@0([0]: RangeCheck, [1]: GasBuiltin) -> (RangeCheck, GasBuiltin, core::panics::PanicResult::<(core::integer::u32,)>);

As you can see the function needs RangeCheck and GasBuiltin, and returns (RangeCheck, GasBuiltin, core::panics::PanicResult::<(core::integer::u32,)>). You'd need something like this:
#include <stdio.h>
#include <stdint.h>

// Type consistency.
typedef __uint128_t uint128_t;

// Cairo Native types.
typedef struct __attribute__((aligned(16))) felt252_t
{
    uint64_t data[4];
} felt252_t;

typedef struct native_array_t
{
    void *data;
    uint32_t start_offset;
    uint32_t end_offset;
    uint32_t capacity;
} native_array_t;

// Our function's return values (check out the C ABI for more info).
typedef struct cairo_main_t
{
    uint64_t range_check;
    uint128_t gas;
    union {
        struct { uint8_t tag; uint32_t value; } ok;
        struct { uint8_t tag; native_array_t msg; } err;
    } result;
} cairo_main_t;

// The weakref is the symbol name. You should make sure it matches the one in the MLIR output,
// including the `_mlir_ciface_` prefix.
static cairo_main_t *cairo_main(cairo_main_t *, uint64_t, uint128_t)
    __attribute__((weakref("_mlir_ciface_program::program::main(f0)")));

int main()
{
    cairo_main_t ret_data;

    // You don't need to initialize the range check and gas into the return pointer, you can pass
    // them directly too. The final builtin counter and gas will be stored in the structure, so
    // having them originally there may make it easier to understand.
    ret_data.range_check = 0;
    ret_data.gas =<PHONE_NUMBER>000;
    cairo_main(&ret_data, ret_data.range_check, ret_data.gas);

    // You can check either `ret_data.ok.tag` or `ret_data.err.tag`. They are the same field, but
    // must be declared separately in each variant due to the way our enums work (if it was a common
    // field, then the alignment of the payloads would be messed up).
    if (ret_data.result.ok.tag == 0)
        printf("cairo_main() returned Ok(%u)\n", ret_data.result.ok.value);
    else
    {
        felt252_t *error_msg = (felt252_t *) ret_data.result.err.msg.data;
        size_t i;

        // Here's an example on how to read the arrays (for the error messages):
        printf("cairo_main() returned an error:\n");
        for (i = ret_data.result.err.msg.start_offset; i < ret_data.result.err.msg.end_offset; i++)
        {
            // Note that they're in reverse order. It's intentional because they're written in
            // little-endian.
            printf(
                "  %016lx%016lx%016lx%016lx\n",
                error_msg[i].data[3],
                error_msg[i].data[2],
                error_msg[i].data[1],
                error_msg[i].data[0]
            );
        }
    }

    return  0;
}

Disclaimer: The C program hasn't been tested.

@azteca1998 thank you very much for the detailed response! I understand the flow much better now


Fix: css selector

Closes #59

Thank you for opening a PR!

👍
Seems I can't merge myself, so I'll let you merge at your own convenience 🙂


SVELTEKIT: Streaming queries causes error.

Bug report

[ x ] I confirm this is a bug with Supabase, not with my own application.
[ x ] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
When trying to navigate after the initial load (which works just fine), you get an Error thing.catch is not a function on preload-data links.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
export const load: PageServerLoad = async ({ locals: { safeGetSession, supabase }, params: { id } }) => {
	const { session } = await safeGetSession()

	if (!session?.user.id) {
		throw redirect(303, '/login')
	}

       const profile = supabase.from('profiles').select().eq('id', id)

      // this is not part of the issue but show cases how SvelteKit wants you to handle errors on streams, but can't do this since there is no catch method. throwOnError() doesn't provide it with a catch() method either.

       profile.catch(e => console.log(e))

	return {
		profile
	}
}

Expected behavior
There should be a catch method
System information

OS: Linux Mint
Browser (if applies) Chrome
Version of supabase-js: 2.39.1
Version of Node.js: 21.7.3

Hi @themixednuts I am not super familiar with Sveltekit so you might need to educate me a bit!
By stream, you mean streamed promise? What stops you from streaming the promise and catching on Svelte's side with {:catch}? I might be wrong but I thought that was the recommended practice

All good! I think the docs will explain the best here https://kit.svelte.dev/docs/load#streaming-with-promises.
In the code side, sveltekit checks for a .catch() on the promise, and since there is none it throws an error. So {:catch} wouldn't even be possible even so.

Thanks for the pointer, so it looks like the call you make returns a PromiseLike from the PostgrestBuilder object that does not implement catch (see here)
What you could do is map the throwOnError to catch for Svelte to pick up but possibly others have different ideas?

Hey @themixednuts, you can also do this by wrapping the call in an async function:
export const load: PageServerLoad = async ({ locals: { safeGetSession, supabase }, params: { id } }) => {
	const { session } = await safeGetSession()

	if (!session?.user.id) {
		throw redirect(303, '/login')
	}

       const profile = (async () => await supabase.from('profiles').select().eq('id', id))()

      // this is not part of the issue but show cases how SvelteKit wants you to handle errors on streams, but can't do this since there is no catch method. throwOnError() doesn't provide it with a catch() method either.

       profile.catch(e => console.log(e))

	return {
		profile
	}
}


Expression of type 'System.Object' cannot be used for parameter of type 'Microsoft.EntityFrameworkCore.Metadata.IEntityType'

Since updating to v2 I now get the following exception from one of my unit tests:
System.ArgumentException : Expression of type 'System.Object' cannot be used for parameter of type 'Microsoft.EntityFrameworkCore.Metadata.IEntityType' of method 'Void StartTracking(System.Object, Microsoft.EntityFrameworkCore.Metadata.IEntityType)'
Parameter name: arg1

In order to get the test to pass I have had to change:
var projects = this.context.Projects
                        .Include(p => p.Windfarm)
                        .Include(p => p.Turbines)
                        .Where(p => p.Windfarm.ClientId == clientId && p.IsActive)
                        .GroupBy(g => g.WindfarmId)
.Select(s => s.OrderByDescending(o => o.DateStarted).FirstOrDefault())
                        .ToList();

to the following:
var activeProjects = this.context.Projects
                        .Include(p => p.Windfarm)
                        .Include(p => p.Turbines)
                        .Where(p => p.Windfarm.ClientId == clientId && p.IsActive)
                        .GroupBy(g => g.WindfarmId).ToList();

            var projects = activeProjects.Select(s => s.OrderByDescending(o => o.DateStarted).FirstOrDefault())
                        .ToList();

    public class Program
    {
        public static void Main(string[] args)
        {
            using (var db = new MyContext())
            {
                // Recreate database
                db.Database.EnsureDeleted();
                db.Database.EnsureCreated();

                // Seed database
                db.AddRange(
                    new Blog
                    {
                        Posts = new List<Post>
                        {
                            new Post(),
                            new Post(),
                            new Post()
                        }
                    },
                    new Blog
                    {
                        Posts = new List<Post>
                        {
                            new Post(),
                            new Post(),
                            new Post()
                        }
                    }
                    );

                db.SaveChanges();
            }

            using (var db = new MyContext())
            {
                // Run queries
                var query = db.Set<Post>()
                    .Include(p => p.Blog)
                    .GroupBy(p => EF.Property<int?>(p, "BlogId"))
                    .Select(g => g.OrderBy(e => e.Id).FirstOrDefault()).ToList();
            }

            Console.WriteLine("Program finished.");
        }
    }

    public class MyContext : DbContext
    {
        // Declare DBSets
        public DbSet<Blog> Blogs { get; set; }

        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            // Select 1 provider
            optionsBuilder
                .UseSqlServer(@"Server=(localdb)\mssqllocaldb;Database=_ModelApp;Trusted_Connection=True;Connect Timeout=5;ConnectRetryCount=0")
                //.UseSqlite("filename=_modelApp.db")
                //.UseInMemoryDatabase(databaseName: "_modelApp")
                .EnableSensitiveDataLogging()
                .UseLoggerFactory(new LoggerFactory().AddConsole());
        }

        protected override void OnModelCreating(ModelBuilder modelBuilder)
        {
            // Configure model
        }
    }

    public class Blog
    {
        public int Id { get; set; }
        public List<Post> Posts { get; set; }
    }

    public class Post
    {
        public int Id { get; set; }
        public Blog Blog { get; set; }
    }

Include with GroupBy and Select with single result operator.
This is regression from 1.1.2
@anpete

@maumar this bug!

Just when I thought I might have gotten through with migrating to 2.0.. .more Entity Framework regressions.
Back to 1.x I go I suppose.

@twilliamsgsnetx i'm also disappointed that I have had to retest my entire code base because this has affected a few places but I wouldn't be so hasty as to roll back, especially if you've already done the hard part of migrating. I would suggest simply using ef to do the selects but for any grouping operations do that after you have called toList

Problem is that when we apply Include on the selector, need to special case group by (apply include on element selector, rather than on qsre directly) - QueryModelExtensions.GetOutputExpression
However, for more complex scenarios the logic is not correct, as we only look at the top level query model and top level expression type. In the problematic case group by is "hidden" in a subquery.
Workaround: add ToList() after GroupBy call, there is no perf hit, since (in 2.0) everything after Groupby is performed on the client anyway

Please consider a patch release - on myget, or an alpha on nuget?
There are a number of blocking bugs preventing us from migrating to 2.0. It would help tremendously to get a prerelease just so we can continue.

Hi @dannythomas13, @twilliamsgsnetx, @grokky1. We are gathering information on the use of EF Core pre-release builds. You reported this issue shortly after the release of 2.0.0 RTM. It would be really helpful if you could let us know:

Did you consider testing your code against the pre-release builds?
Was there anything blocking you from using pre-release builds?
What do you think could make it easier for you to use pre-release builds in the future?

Thanks in advance for any feedback. Hopefully this will help us to increase the value of pre-release builds going forward.

@ajcvickers Hey thanks for looking into this! We upgraded to netcoreapp2.0 a few days after release. We managed to upgrade both ASP.NET Core and EF Core (after dealing with various breaking changes). But then various tests started failing! After much investigating, we realised it wasn't our code, but the new bits (BTW all our problems have something to do with Include() and ThenInclude()).
After ensuring it wasn't because of breaking changes, and realsing that the workarounds were too brittle (and reluctance to change our working code), we decided to just cut our losses and go back to 1.1.
My thoughts:

If there were patches for various bugs, we'd have definitely used them and given feedback. We spent over a week doing the upgrade, so it was difficult for us to admit defeat and roll back! Would have loved to actually finish the job. Though we'd wait for a stable before pushing our new code into production, we could at least move forward.
Like others have mentioned, when you folks release a patch/hotfix/whatever,  please ensure they cover the issues only, and don't introduce new features at the same time, or change any existing features. Otherwise it's not really a hotfix and our tests may start failing for other reasons.

Hope to see 2.0.1 soon! 😄

@grokky1 Thanks for the feedback. Could you provide some more information on how the EF Core releases are different from what you are suggesting? (It seems what you describe is what is happening, so I am probably missing something.) For example, was there a patch release that included changes you considered to be features? Or is it more that these releases don't come out fast enough? Thanks again for your thoughts.

@ajcvickers Maybe I'm the one who is confused... 😆 I remember trying one of the myget releases and it fixed something but then something else broke (I guess that's to be expected as it's a alpha/beta after all). I was looking in these forums and noticed others complain about the same thing. Maybe we were all mistaken!
So I'm glad you say the release plan works that way. But there should be more docs around this matter.
Please correct me if I'm wrong:

There is a nuget for EFCore stable
There are nugets for prereleases, basically betas
There are nugets on myget - I assume these are alphas / nightlies / whatever - basically the latest builds from your team, including new features

How do I get my hands on a hotfix without new features - which nuget do I use?

@smitpatel What's the status of this issue?

@grokky1

NuGet

RTM Patch releases (e.g. 1.1.0 -> 1.1.1) containing important bug fixes and no new features.
RTM Point releases (e.g. 1.0.x -> 1.1.0) containing bug fixes and new non-breaking features
RTM Major releases (e.g. 1.x.x -> 2.0.0) containing bug fixes, new features, and possibly breaking changes
Pre-releases in each of these categories, although we haven't yet done any pre-releases on NuGet for patch releases due to logistical issues on our side.

MyGet

Nightly builds, C.I. builds, etc. (That is, not releases)

This patch bug is approved for the 2.0.x patch. Please send a PR to the feature/2.0.1 branch and get it reviewed and merged. When we have the rel/2.0.1 branches ready please port the commit to that branch.

@ajcvickers Thanks for that breakdown! I'm sure it's documented somewhere but I didn't know for sure until now.
2.0.1 is coming... excited!

Hi, we have a public test feed that you can use to try out the ASP.NET/EF Core 2.0.3 patch!
To try out the pre-release patch, please refer to the following guide:

https://github.com/aspnet/Announcements/issues/274 (info)
https://github.com/aspnet/Home/issues/2254 (discussions and questions)

We are looking for feedback on this patch. We'd like to know if you have any issues with this patch by updating your apps and libraries to the latest packages and seeing if it fixes the issues you've had, or if it introduces any new issues. If you have any issues or questions, please reply on this issue to let us know as soon as possible.
Thanks,
Eilon

@maumar I came across similar issue with @paillave, i don't know if he solved it or not.
Created a new issue at #22016 since it seems different than the topic.


krusader does not run, and does not run well...

Describe the bug
Was not able to run krusader through nix-env -i ... , in a debian host.
And in nixos with `nix-shell -p krusader', all the icons are missing.
in the sequence of this package request: https://github.com/NixOS/nixpkgs/issues/178186
Steps To Reproduce

install it
try to run it.

Expected behavior
Run on host debian.
Having icons on host nixos.
Screenshots
On debian host:
14:15:57.715-warning qt.glx unknown@0 # qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlagsQSurfaceFormat::FormatOption(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
14:15:57.721-warning qt.glx unknown@0 # qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlagsQSurfaceFormat::FormatOption(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
14:15:57.725-fatal default unknown@0 # Could not initialize GLX
Aborted
Additional context
Notify maintainers
Metadata

krusader in a KDE session on NixOS is perfectly fine - it appears though that it's impure and looking for something in the global environment and not finding those without various KDE components present.

yes ::: surely missing dependencies when installed as stand alone.
O.o ... yet if may not stand alone ::: should be part of a bigger package, and not be able to be installed alone... o.O?... or include all dependencies it needs to run... :) ... as expected from all packages... right?

should be part of a bigger package, and not be able to be installed alone…

It doesn’t declare all its dependencies, which it should. Running KDE applications on !NixOS isn’t very well tested which is why this has slipped through the cracks. We have issues with other applications as well (amarok comes to mind).

strace shows access to
/run/current-system/sw/share/kservices5/
/run/current-system/sw/share/kservices5/emoticonstheme_kde.desktop
/run/current-system/sw/share/icons/
/run/current-system/sw/share/icons/breeze-dark/index.theme
/run/current-system/sw/lib/qt-5.15.5/plugins/iconengines/
/run/current-system/sw/share/mime/generic-icons

/run/current-system/sw/share/icons/ is probably found via XCURSOR_PATH
echo $XCURSOR_PATH | tr : $'\n'
/nix/store/3n7kzs4b6kd3qxishy646igkw21y4csm-plasma-workspace-5.25.4/share/icons
/home/user/.icons
/home/user/.local/share/icons
/home/user/.nix-profile/share/icons
/home/user/.nix-profile/share/pixmaps
/etc/profiles/per-user/user/share/icons
/etc/profiles/per-user/user/share/pixmaps
/nix/var/nix/profiles/default/share/icons
/nix/var/nix/profiles/default/share/pixmaps
/run/current-system/sw/share/icons
/run/current-system/sw/share/pixmaps
~/.icons
/var/empty/share/icons
/var/empty/share/pixmaps
/var/empty/X11R6/lib/X11/icons

the breeze-dark theme is probably chosen from ~/.config/kdedefaults/kdeglobals
grep -r breeze-dark ~/.config/kde*
/home/user/.config/kdedefaults/kdeglobals:Theme=breeze-dark