Compilation issue with catch.hpp

If you have a question about the RDKit or aren't sure if what you're seeing is the right behavior please use the Discussions tab above (https://github.com/rdkit/rdkit/discussions) instead of posting it here.
Please help us help you: We normally need the information below in order to answer questions or understand bug reports. If you do not provide the information requested we may not be able to help you and will probably close the issue.
PLEASE DELETE THIS SECTION AFTER YOU HAVE READ IT

Describe the bug
The compilation of Release_2021_09_5 fails in Archlinux due to some issue related to catch.hpp
To Reproduce
Compile Release_2021_09_5 ( Note also Release_2021_09_4)  in an updated Archlinux using Release_2021_09_5.tar.gz and it will fail. This is the error you will get that halts the installation:
[ 17%] Building CXX object Code/DataStructs/Wrap/CMakeFiles/cDataStructs.dir/wrap_FPB.cpp.o
In file included from /usr/include/signal.h:328,
                 from /home/hector/ownCloudUOCHB/repo/admin/arch/AUR/rdkit/src/rdkit-Release_2021_09_5/External/catch/catch/single_include/catch2/catch.hpp:8031,
                 from /home/hector/ownCloudUOCHB/repo/admin/arch/AUR/rdkit/src/rdkit-Release_2021_09_5/Code/Geometry/catch_tests.cpp:12:
/home/hector/ownCloudUOCHB/repo/admin/arch/AUR/rdkit/src/rdkit-Release_2021_09_5/External/catch/catch/single_include/catch2/catch.hpp:10815:58: error: call to non-‘constexpr’ function ‘long int sysconf(int)’
10815 |     static constexpr std::size_t sigStackSize = 32768 >= MINSIGSTKSZ ? 32768 : MINSIGSTKSZ;
      |                                                          ^~~~~~~~~~~
In file included from /usr/include/bits/sigstksz.h:24,
                 from /usr/include/signal.h:328,
                 from /home/hector/ownCloudUOCHB/repo/admin/arch/AUR/rdkit/src/rdkit-Release_2021_09_5/External/catch/catch/single_include/catch2/catch.hpp:8031,
                 from /home/hector/ownCloudUOCHB/repo/admin/arch/AUR/rdkit/src/rdkit-Release_2021_09_5/Code/Geometry/catch_tests.cpp:12:
/usr/include/unistd.h:640:17: note: ‘long int sysconf(int)’ declared here
  640 | extern long int sysconf (int __name) __THROW;
      |                 ^~~~~~~
In file included from /home/hector/ownCloudUOCHB/repo/admin/arch/AUR/rdkit/src/rdkit-Release_2021_09_5/Code/Geometry/catch_tests.cpp:12:
/home/hector/ownCloudUOCHB/repo/admin/arch/AUR/rdkit/src/rdkit-Release_2021_09_5/External/catch/catch/single_include/catch2/catch.hpp:10874:45: error: size of array ‘altStackMem’ is not an integral constant-expression
10874 |     char FatalConditionHandler::altStackMem[sigStackSize] = {};
      |                                             ^~~~~~~~~~~~

Expected behavior
It should compile without error
Screenshots
If applicable, add screenshots to help explain your problem.
Configuration (please complete the following information):

RDKit version:  Release_2021_09_5
OS: Archlinux (3/13/2022)
Python version (if relevant): 3.10.2
Are you using conda? No
If you are using conda, which channel did you install the rdkit from?
If you are not using conda: how did you install the RDKit?
GCC version: 11.2.0

Additional context
Add any other context about the problem here.

This seems to be an issue with older Catch2 versions and newer libc.
If you apply this patch
https://patch-diff.githubusercontent.com/raw/rdkit/rdkit/pull/5092.diff
then
rm -rf External/catch/*.tar.gz External/catch/catch

and rebuild the problem should be solved.


add sync register command arg for converter

Would be nice to have a way to define a custom sync write address.

not a priority


Use velocity control on mecanum wheels

Currently we are just sending raw power, but because odometry use velocity * time = displacement, we need to have the wheels in velocity control mode.

We got this working!


Recompile discord RPC and LuaJIT with -fPIC for static lib.

Recompiled discord lib with clang and enabled -fPIC. Recompiled luaJIT with clang and also enabled -fPIC.

:+1:


[swift] Update to Swift3

Added missing keywords
Removed non-swifty atoms
Rearranged more logically

Thanks. Merged as 581854e


Get broker ID after creating broker with NewBroker?

Versions
All versions
Configuration
What configuration values are you using for Sarama and Kafka?
broker := sarama.NewBroker("host:port")
err := broker.Open(sarama.NewConfig())

Problem Description
Is it possible to populate the id field for a seeded broker? When I retrieve the list of brokers with a metadata request, I am able to call broker.ID() and get the correct ID. However, when I create a broker directly with NewBroker, broker.ID() returns -1.
For my use case, I would like to connect to a specific broker by host/port, then use that connection to determine its ID. Is there currently any way to do that?

Closing because I am no longer working on this project


Fix Rails 6 ActionController::Base deprecation warnings

Referencing ActionController::Base within an initializer or railtie causes Rails to print a deprecation warning. The relevant Rails issue is here: https://github.com/rails/rails/issues/36546
This is fixed by using ActiveSupport.on_load before referencing the module in the railtie. I chose to use the :action_controller hook name because the more appropriate :action_controller_base hook is only available in Rails versions >= 5.1. If it's preferable, we could check the Rails version and set the hook name conditionally.

@mgomes Could you review and merge this PR and the other one related #180, please? 🙏

GitHub seems to be having some issues picking up the passed status of the Travis CI job, but I've rebased my branch and solved the merge conflicts. The changes are good to go.

Thanks @taylorthurlow. I've been noticing that as well.
I really appreciate your work. I'll get this merged and cut a new version shortly.

@mgomes I'm thinking I unwittingly introduced an ActiveSupport dependency to the gem with this PR. With the gem being able to be used without Rails (and I assume ActiveSupport) this seems like a problem to me. That said, the railtie file itself isn't conditionally included, so lines with if-statements like this one essentially meant that loading the railtie definition in a gem with no Rails dependency didn't matter. That's not the case anymore.
Do you mind sanity checking what I've said? I can open a new PR to fix this if necessary.


Got stuck when installing oh-my-zsh by using install.sh

Got stuck when cloning from Github, it caused by using --depth=1 option, remove this, the script works.

What git --version do you have?

Can you try changing the parameter to --depth 1 (without the equal sign)?

➜  ~ git --version
git version 2.15.2 (Apple Git-101.1)
This is my git version, and I haven't tried it without the equal sign.

Please run this command: git clone --depth 1 https://github.com/robbyrussell/oh-my-zsh.git and report if it successfully clones the repository.

git clone --depth 1
This works fine for me.

I can't reproduce this behavior in git 2.17.1, can you try the above command with --depth=1?

I have tried --depth=1 and --depth 1, the same behavior. But I used another laptop with git 2.15.2. Both all them works, so I think it could be my system problem~~~ Thanks for your help.

Cool, it must've been a temporary glitch.


Consider scoping environment variables to the specific packaged app

Right now Burrito relies on hardcoded environment variables like APPLICATION_INSTALL_DIR. There's nothing tying these names to the specific app in question, and we probably don't want to leak Burrito as an implementation detail, so we may want want to investigate using environment variables that are based on the name of the application in question, like: MY_APP_INSTALL_DIR
Burrito already has access to the OTP app name, so we could leverage that easily. This would also allow Burrito applications to be configured independently of each other.

this is all set in the latest release!


Request to be a member of Volcano community

Hello, members of Volcano community. I have followed volcano since 2021 when I was first working on k8s cluster-schedule for ML jobs using kube-batch. I found that volcano scheduler is base on kube-batch and has continious upgrade. So I often read the PRs and volcano-scheduler source code and sometimes find some issues.  I'd like to join the volcano community for further contributions.
Here is my PR about some feature enhancement and issues fix .
enhancement

Improve: reduce calculation of total nodes' resource in stead of storing it when snapshot #1578
func FeasibleNodesToFind to use list with a centain order #1574
use root context to handle system signal #1715

issue fix

same job's diffenrent tasks should compare task's priority #1452
lose preemptor when considering Preemption between tasks within same Job #1453
fix issue for func GetDevicesIdleGPUMemory
format docs #1639
fix issue #1711 about empty job queue in metrics #1722

in process

add detail log about allocate/pipeline/evict information
fix: undefined buildJmpDirective on arm64 machine
keep updating task's min available number same as creating podgroup
fix lint error
Enhancement: ambiguity variable refact

/lgtm

@k82cn @kevin-wangzefeng Could you please help to review this request? Thanks.

+1
Welcome to the community!

+1
Welcome to the community!

@lowang-bh Thank you for your contribution and welcome onboard!
You will be receiving the email invitation shortly. You can also visit https://github.com/volcano-sh to accept the invitation.

@k82cn @kevin-wangzefeng Could you please help to review this request? Thanks.

+1
Thanks very much for your great works.

Thanks all. Now I will close it.


fix: compiler docs revamp

What :computer:
Added

the description of EVM storage instructions
missing links to EraVM specifiction
various missing info added to the original repo after it was forked for Code4rena

Removed

redundant and duplicated headers
outdated warning about unsupported Docker
the EraVM extension page, which is terribly outdated, unreadable and broken: will rewrite it from scratch soon with proper references to the EraVM specification

Fixed

formatting of some tables and code blocks
numerous external and internal links
some typos and grammar errors
the structure of EVM instruction reference

@hedgar2017 It looks like you have dead links. You've put hyperlinks inside of the Headers and this breaks dead-link linting. Some options:

Move the hyperlinks to content within each header
Don't link directly to an anchor on the page, but just the page itself (user would have to scroll to exact section)
Add a hidden anchor with each Header containing a hyperlink
Find the "correct" way to reference an anchor that's actually a hyperlink (Unsure what this is)


HttpTrigger / HttpExample

This documentations tells me to "Open the HttpTrigger.cs project file and add the following using statement:", supposedly something that was created in the previous Quickstart article. But, all I was instructed to do there was to create a templated HTTP project which doesn't contain any HttpTrigger files. It contains one file, with a function called HttpExample.
Is this the same file that is meant by "HttpTrigger"? In that case, this needs to be explicit to avoid confusion.

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

ID: ca7362b2-b991-a5bb-45e8-1e6d9ebb04d5
Version Independent ID: 6dd2cefe-f557-0ca9-c8cc-6b0e2f762a9f
Content: Connect functions to Azure Storage using Visual Studio Code
Content Source: articles/azure-functions/functions-add-output-binding-storage-queue-vs-code.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Hi @haugan Thanks for your feedback. We will review and update as appropriate.

@haugan This is already mentioned in the doc. Below is the screen shot for this. I don't think there is a doc change required at this moment. So for now I will proceed with closure of this and If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Yes, I know. The issue it with different naming of HttpTrigger/HttpExample.


New arXiv favicon

Hi there!
This is not really an issue.
I want my site to display the new arXiv favicon [https://jpswalsh.github.io/academicons/].
But I don't know how to modify the settings to make this possible.
Thanks a lot for your help!

If the icon is already showing somewhere, but it is just not the updated one, all you need to do is update the version of academicon used in _config.yml

Thank you!
I just changed it the 1.9.1 to 1.9.4. However, it didn't work.
I had ORCID, Scopus and arXiv academicons showing with 1.9.1, but when I changed the version they disappeared.
Is this because I also need to change the integrity below version?
Thank you!

Yes, you also have to update the integrity. The integrity is the hash of the file. With the wrong integrity the file will not load at all.

As you can see here, the latest academicons npm package is 1.9.2 and not the 1.9.4. So you will not be able to get an integrity for 1.9.4.
For 1.9.2 the integrity is "sha256-CylD++oS3IkJmSs/j4i1w0cv2wpVQRLLQqw/m+Fvxts="
But, the new arXiv icon isn't there as well.

Apparently it's been a while since the npm package was updated. Also there are still missing icons from academicons that could be added (I created a feature request for one a while ago). One day I will create a PR for this.
According to this site, it would be better to load things from CDN since it can load from sources closer to the user. At the same time, loading locally can offer other benefits when used with some other solutions like this one here. I will try to do some more thorough tests with the purgecss solution, then maybe include it with locally loaded academicons too.

I would for now recommend locally loading the academicons package if you want the latest version. If someone could send a PR for this would be great.

I believe this was fixed in #1562


Optimize all SVG icons and remove any possible licenses

This PR makes sure all SVG icons are optimized (a few where not) and further reduce them by removing metadata (possibly containing copyright/license information).
This related to #1158 and probably closes it?

LGTM


Upgrade 3rdparty libraries

As with the previous release, we should evaluate updating to the latest versions of the stable 3rdparty libraries prior to the next (v0.5) OE SDK update. Libraries on the horizon for the end of Feb include:

[x] MUSL libc 1.1.21

Note that the libc-test suite comes from a different, unversioned project at (separate update command in 3rdparty/musl/update.make)
There's been an update in Nov 2018 that we didn't pick up, and we should probably do so now. (added strptime test)

[ ] LLVM libcxx 8.0.0 (final)
[x] mbedTLS 2.7.9

Note that the security approval for the versions of the LLVM libcxx and MUSL libc libraries still stand, so there's not an urgent to upgrade from them for any security reason. Given the slip in LLVM's schedule, we will bump taking the libcxx 8.0.0 update to the next release.

mbedTLS though, does have relevant security fixes, and so is tracked separately by #1446.

For the libc/libcxx updates, they are also a little more involved as we need to identify and evaluate changes to the test set as well. A general outline of the process for onboarding a new version includes:

Update the relevant update.make file for the 3rd party library and run it to pull down and apply the new version.
Attempt to build OE SDK with the updated source code. Find and fix any breaks, and repeat for all build configurations.

A common source of failures will be the mismatch in the test files we expect to be present as used in tests/libc and tests/libcxx; primarily libcxx tests since the libc tests don't change much, but the guidance here applies to both.
Each of those test suites defines a tests.all file which inventories the set of all tests we expect exist for the version of the respective library we're using.
As part of the update, we do a diff of a sorted file tree walk of the new test folder contents against the old tests.all to understand what tests were added/removed/moved, which helps with the next step.

Attempt to run the OE SDK tests with the ENABLE_FULL_LIBCXX_TESTS CMake variable set to true.

This is also the configuration for the Jenkins OpenEnclave-libcxx_tests pipeline, but I would suggest running it locally since it takes a non-trivial amount of time to complete and hog the limited ACC VMs, preventing other pipelines from running.
The libc tests already runs all of the supported tests, so no additional flag is necessary.
The set of supported tests should be expanded to include any new tests.

For libcxx tests, this is defined by the tests.supported file.
For libc tests, this is defined in the tests.cmake file.

Any test failures should be triaged as either broken or unsupported:

A broken test is one that we think should pass, but does not for bug or dependency reasons.
An unsupported test is one where we explicit decide that the failure is by design (e.g. I/O functions where OE provides no I/O support).

We also take the set of previously broken and unsupported tests and run them again to see if any of them have started passing.

Some tests do because they no longer rely on functions not supported in OE SDK, for example.

Update the sets of tests.supported, tests.broken and tests.unsupported so that they reflect the new total set of tests.all.

Usually the triage process for determining the supported/unsupported/broken split requires a bit of insight, and @mikbras, @anakrish & @CodeMonkeyLeet are usually available to consult on those fronts.

In terms of the PR, steps 1 & 2 are usually 1 commit and all of the test modifications and updates are 1 or more subsequent commits to keep the 3rdparty changes separate from the OE test changes.

Simon (@CodeMonkeyLeet) wants to offer some comments on this.

Updated the title and description of this issue to track the LLVM slip.

Info: We are still waiting for a final release on 8.0.0

RC4 has been released:
http://llvm.org/svn/llvm-project/libcxx/tags/RELEASE_800/rc4/
CC: @vlaza

rc5 has been released: http://llvm.org/svn/llvm-project/libcxx/tags/RELEASE_800/rc5/

I have updated the PR for rc5 and re-running all tests.

I have updated the PR with final release and all tests in the updated version are passing.

Closing this as complete except for LLVM 8.0 which is scheduled for v0.6.


default value for Payment::iban() country code

matching the function signature with the doc as defined in Faker\Generator:
 @method string iban($countryCode = null, $prefix = '', $length = null)

Thanks


Create password form field

Please give me a detail over this issue @arantespp
I want to work over this


Answer RESOLVE-PTR with a protocol-compliant error

Relates to #195
Does not exactly fix the problem but eliminates the most offensive symptom.
See #520 for the complete fix which also depends on getting a new Torsocks out to folks.

I'm still seeing a segfault on my machine that has valid reverse DNS. Debug next week?


Feature request: Have two Archive.org options

With some pages, having a direct link to the latest version of the page on archive.org will result in a redirection to another page. This makes it very difficult to go back to an earlier version.
It would be really nice to add an additional option. Have one button be "The Internet Archive (latest)" and the other be "The Internet Archive (all)". OR maybe "The Internet Archive (list)."

This sounds reasonable.


Facebook auth

Add another authentication method -- Facebook OAuth2.
Testing plan:
I have tested this by registering and logging in on my deployed server. I thought about implementing a unit test along the lines of the other auth methods, but that seems to be a whole order of magnitude more work, for which I don't have time.
GIFs or screenshots:

@AJChapman we'd love to see this PR updated so that we can integrate it; it'll need a rebase in addition to resolving the batch of comments above.

Ok, code review comments have been acted upon, and I've rebased against the latest, and the checks are passing.

Ok, code review comments have been acted upon, and I've rebased against the latest, and the checks are passing.


Remove unused conception_probs from Pregnancy

Seems straightforward unless someone is using conception_probs elsewhere?

Unless there is a reference on somebody's non-commited branch, this seems to be a safe change. I didn't find any reference.


Security: dependencies: spring

Github informs me that I need to upgrade:
[ ] org.springframework:spring-beans 3.0.5.RELEASE
[ ] org.springframework:spring-web 3.0.5.RELEASE
[ ] org.springframework:spring-core 3.0.5.RELEASE
[ ] org.springframework:spring-context 3.0.5.RELEASE

Upgrade to <spring.version>5.3.33</spring.version>
Can't go to 6.x without moving to Java 17.


Change ZWO shortest exposure

I cannot see if there's an easy or obvious way to change the minimum camera exposure to be less than 1ms?
My ZWO 178MC can expose at 0.032ms, and I'd like to use this for daytime settings, otherwise the image appears to be washed out.
It may be that the exposure is lower than 1ms but is displayed on the overlay as 0.001s, but the images do appear to be washed out in sunlight.
Where can I see the actual image exposure instead of the jpg overlay?
Speaking of the overlay, how can I change the 1st line to be easier to read, i.e. from 20210208 16:01:02 to something like 08-02-2021 16:01:02?
In fact, customising the overlay text would be great from within the gui side of things, rather than the default date, temperature, exposure and gain.
I'm happy to edit html and a bit of php but no more than that - but it's a case of knowing where to look and what to look for.

Jonk2,
Look in the log file (usually /var/log/allsky.log) for the microsecond exposure time.
A few of us are working on enhancements to allsky, including the ability to specify the time format (see the manual page for strftime(3).  It'll also let you specify whether or not to display the time, a one-line user-specified text line, the sensor temp, the exposure, the gain, and the brightness.  Our changes also include a workaround for a ZWO bug with daytime exposures jumping all over the place - for example, an image at 3 seconds is too dark, but an image at 2 seconds is too bright.
Eric

Hi Eric,
I've looked in the log and can see the values, but this has opened a lot of questions in my head.
I didn't know there were plans for others to improve this software, and I'm really glad about that as it looked like it had gone stale.
With this in mind, I won't bring them up here unless you want me to?
I'd be happy to act as a beta tester if this helps? My PI is on a long term test indoors with nothing else besides an NTP running so I'm happy to make changes without fear of losing anything.
Jon

Jon,
I'm happy to answer any questions you have.
Eric

Ok, when I look in the logfile, there's not really a lot to go on.

It seems that the camera is exposing all the time, but the software only 'grabs' a frame when the time is right, i.e. once every 30 seconds. Is this a function of the way the camera works? I suspect it is, but if not, there's no need to keep exposing continuously as this heats the sensor up and causes more noise and a lot of hot pixels. (I'm currently using a ZWO 178MC but looking to move to a cooled ZWO).

Every 30 seconds (my image refresh rate) only means 'resizing and uploading' are logged, but then I get about 150+ lines with the same timestamp showing the autoexposure and autogain numbers for the previous x number of exposures, like it's being dumped after a certain time into the log. This may be a limitation, or by design, but it doesn't make the log easy to read.

Maybe I'm overthinking it and will wait for any updates and improvements, you guys probably have a list!

Jon,
The new version starts exposing right before a picture and stops exposing right after; we've seen about a 10 degree decrease in temperature.  It also outputs a line to the logfile as it's written.  The current version buffers log output so dumps a bunch of lines at once which makes debugging hard.
If you email me at AstroEric at eccssw dot com I can send you the new code.
Eric

Ok, I will drop you an email - I have looked at your forked version, but if I do a github clone from that, won't it complain that 'allsky' already exists?
Can you rename it perhaps so I can run side by side to compare, or does it not work like that?

I'm not very familiar with GitHub.  What you could do is stop the allsky process, then rename the ~/pi/allsky directory to something else, then do the gethub clone.
Eric

New version has addressed this issue.

Jon, FYI, if you want to manually set the daytime exposure to less than 1 ms, you can.  You'll need to Show Advanced Settings, then disable daytime Auto-Exposure and set the daytime Manual Exposure.  I have mine at .5 ms.  If you have your "Locale" set properly you should be able to use a comma, but try and let me know.
Eric


nixos/mesos: fix non-deterministic service and test failure

Motivation for this change
nixos/tests/mesos failed most of the time on Hydra. This was caused by two different issues:

mesos-slave.service failed if docker.service wasn't ready due to a missing  After= dependency.
The nixos test didn't wait for all relevant services and ports to be available before sending requests.

@grahamcofborg test mesos

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: tests.mesos
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: tests.mesos
Partial log (click to expand)
slave: exit status 0
master: running command: sync
master: exit status 0
test script finished in 33.51s
cleaning up
killing slave (pid 593)
killing master (pid 605)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/qx6a946nmdqs95kvw0b6px09ir7977sn-vm-test-run-mesos


task recipe does not use find_chef_client method

Cookbook version
8.1.6
Chef-client version
12.14.89
Platform Details
Windows Server 2012 R2
Scenario:
Installing the chef-client as a Scheduled Task can have the wrong client bin path
Steps to Reproduce:
In a role, set default_attributes section where node['chef-client']['bin'] is a non-Windows path, like /opt/chef/bin/chef-client and run the chef-client::task recipe as part of the node's run list.
Expected Result:
Looking at the following recipes: cron, all linux *_service recipes,  the chef-client cookbook leverages the #find_chef_client method to find the correct path, but the task recipe does not follow this precedence. Seeing the the find_chef_client method also supports hunting for the client bin in Windows, it seems logical to use this in the task recipe.
Actual Result:
chef_client_scheduled_task resource called in the task recipe uses the node['chef-client']['bin'] value that hasn't been set by a search with #find_chef_client.

Thanks for reporting.

Merged to master


ADMINAPI-1012 1.x MSSQL Deployment in Docker Scenarios

Add docker files to create MSSQL containers (BInaries version)
Add MSSQL containers to use Dev containers from the code

Looks like Swagger is not loading properly for Admin API. Can you double check?


show no votes in red

show no votes in red like in the current DHO:

Hi @leonieherma1 Do you want to implement this on all places where appear the bars?? or just in proposal list when the proposal is opened??? I mean in the vote widget for example I think is a bad option because the background is not white, this is an example for rejected proposal

@jmgayosso good point... ok let's just do it on the proposal list for now and in the profile (while the proposal is open for voting). Not in the proposal detail page.....
Thanks

@jmgayosso actually let's do the proposal detail page too, when the voting is still open:

let's just NOT do it when the voting is finished


unable to alias in update

I am unable to find a way to alias a column name. I want to do this
db('user'+user_id).where({list_id: list_id}).update(column, new_value)

where column is a passed in value. However knex thinks I want to update a column named "column" and while I saw a similar issue (#83) from 2013, the "solution" is crazy unwieldy

Hi @ctkcoding
I am doing something similar in a project I am working on. If I understand your question correctly, you can do this:
const columnName = "my_table_column";
const newValue = 123;
db('user'+user_id).where({list_id: list_id}).update({
   [columnName]: newValue
})

The trick is to use [] brackets around the object property name.

I have no idea what either of you are trying to do. Please tell what kind of SQL you are trying to make knex to generate.
Issue #83 refers to SQL languages alias feature, which allows one to have different names for SQL identifiers... If you are just tying to pass column name in javascript variable, it works just like this:

// looks like you have separate table for each user, which is SQL antipattern
const userTableName = 'user'+user_id;
const updateColumnName = 'first_name';
db(userTableName).where({list_id: list_id}).update({updateColumnName: new_value}).then(res => {
  console.log('Update was success!');
});

The trick is to use [] brackets around the object property name.

Having brackets around property name just does make string conversion from array to column name string, which sounds like some kind of hack to make something to work by accident when using knex with mssql server (mssql uses brackets instead of quotes).

@elhigu The [] brackets have nothing to do with knex or any sql adapters. That's plain javascript, allowing us to use dynamic values as object property keys.  Not sure why you call it as some hack.
The question is about how to use aliases(probably not the most correct terminology) dynamically. And that is what I answered.
const dynamicColumnName = "streetAddress"
// then inside update...
.update({
  [dynamicColumnName]: "Bristol Road" // gives { streetAddress: "Bristol Road" }
})

Being a maintainer, you surely know that the same can be achived using named parameters. :columnName: = :columnValue

@elhigu The [] brackets have nothing to do with knex or any sql adapters. That's plain javascript, allowing us to use dynamic values as object property keys. Not sure why you call it as some hack.

@pupudu wow, sorry about that. I cannot believe that how I've been able to code javascript over 10 years without knowing that :D
And looks like I had another brainfart there in my post mixing object syntax, when I was supposed to use the update syntax of the OP...

I cannot believe that how I've been able to code javascript over 10 years without knowing that :D

@elhigu hahaha not sure if you are trolling or not. Anyways I was just trying to help the person who asked this question. All hail knexJs

@elhigu hahaha not sure if you are trolling or not. Anyways I was just trying to help the person who asked this question.

Sadly no trolling 🙈


Update fs2-core from 3.10.0 to 3.10.1

Updates co.fs2:fs2-core from 3.10.0 to 3.10.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "co.fs2", artifactId = "fs2-core" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #79.


Bring back starting screen

Steps to reproduce
Starting screen option that was removed in the version 1.9.0
Expected behavior
bring back starting screen option in "General tab"
Actual behavior
Starting screen was removed in v1.9.0
Crash logs
No response
Tachiyomi version
1.9.0
Android version
Android 13
Device
Realme Android
Other details
No response
Acknowledgements

[X] This is a TachiyomiSY specific issue that does not happen in Tachiyomi Preview.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 1.9.0.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

This was removed by main tachiyomi app, Sy cant bring it back until they do


az aks update ignoring core.only_show_errors

Describe the bug
When az aks update --attach-acr is run and completes it seems that the command outputs (see below) to stderr even with core.only_show_errors=true set to true.
AAD role propagation done[############################################]  100.0000%

I think when _add_role_assignment in custom.py is called from az aks update --attach-acr I think a check cmd.cli_ctx.only_show_errors is needed to before calling get_progress_controller(True).
To Reproduce
In myResourceGroup create an ACR call myRegistry then create a AKS called myKubernetesService and run the following command.
> az config set core.only_show_errors=true --only-show-errors
> az aks update --resource-group myResourceGroup --name myKubernetesService --attach-acr myRegistry

stderr
AAD role propagation done[############################################]  100.0000%

stdout
{
  "aadProfile": null,
  "addonProfiles": null,
  "agentPoolProfiles": [
    {

Expected behavior
No spinners or progress bars.
> az config set core.only_show_errors=true --only-show-errors
> az aks update --resource-group myResourceGroup --name myKubernetesService --attach-acr myRegistry
{
  "aadProfile": null,
  "addonProfiles": null,
  "agentPoolProfiles": [
    {

Environment summary
> az --version
azure-cli                         2.26.0 *

core                              2.26.0 *
telemetry                          1.0.6
...
Python (Windows) 3.8.9 (tags/v3.8.9:a743f81, Apr  6 2021, 13:22:56)
...

Additional context
I was looking at how to do this in a ARM template but I have yet to find how to do that. So if you know how that can be done would love that!

@gerhardatball Apologies for the late reply. Could you please refer this comment ? Also do let me know if you need any further assistance on this. Awaiting your reply.


Disable warnings and clippy for generated code

The generated code causes a bunch of compiler warnings. It's probably possible to fix these, but the easiest path is just to add #[allow(clippy::all)] and #[allow(warnings)] at the top of the generated code. I can make a PR for this if this is something you want to do.

Also see #412

Yep, that sounds like a good idea, a PR would be great!


Update swift_package generation to store the version as an attribute

It is currently written as a comment. The problem is that Gazelle cannot merge comments.
Add a version attribute to swift_package used to document the version. This value will not be used to download the package.
Can you apply a fix for update-repos like you can for update/fix?

Now that we support bzlmod, I am going to deprioritize issues that are related to the swift_deps.bzl.


Addition of Automatic Node Layout Option

I have come across an annoying issue with regards to arranging programmatically-created nodes within the graph. It appears that the nodes must be rendered before their sizes are properly set, which means that I cannot properly arrange the nodes because their sizes are report as 0 in both dimensions.
I was able to properly arrange a node network by hooking the ContentRendered event on the window it occupies, but the window contains several networks in different tabs. Only the first network, the one that had focus be default, reported proper node sizes; the unfocused networks still had the default 0 sizes. I could not find any event exposed by NetworkView that gave me access to a state where the node sizes of all networks were properly set, and forcing a layout update via the Invalidate functions did not work either.
If there is not a simpler solution to this issue, I would like to suggest an addition to the NetworkView, which I am happy to make a pull request for: a Func<NetworkViewModel> property to contain a function for laying out the nodes, and a bool property to tell whether the network should automatically run the layout function when NetworkView's OnRender() is called. This could possibly mesh with the current layout code in the Toolkit, perhaps by making the Func a generic layout object instead.

I see, that is indeed a problem. The activation/deactivation event of the networkview might be the trigger you are looking for. If not, a temporary workaround could be to observe changes on the width and height of a node and see when they become non-zero, but that's ugly.
I'll be working on the library at the end of this month or the beginning of september, I'll look into it then.

Ok, so it seems there is no ContentRendered for UserControls, only for Windows. The best alternative is to work with the SizeChanged or LayoutUpdated events, but at that point you might as well just observe the Size property of the nodes.
Here is my suggestion:
myNetwork.Nodes.Connect()
   .AutoRefresh(node => node.Size)
   .Where(node => node.Size.Width > 0 && node.Size.Height > 0)
   .Count()
   .Select(sizedNodeCount => sizedNodeCount > 0)
   .DistinctUntilChanged()
   .Subscribe(sizedNodesVisible =>
   {
      // Do layouting here if sizedNodesVisible == true
      // Optionally, you might want to add
      // Where(sizedNodesVisible => sizedNodesVisible == true).FirstAsync()
      // above to observe only the first time a node with non-zero size is visible.
   });

Important note: make sure you include using DynamicData.Aggregation;, otherwise the compiler will use the wrong version of .Count() and the snippet above will not work.

This seems to work! However, as it's written, it will only trigger when the first node in the network viewmodel receives a size. I made the first .Where statement into:
.Where(node => node.Size.Width > 0 && node.Size.Height > 0 && node == model.Nodes.Items.Last())
And this looks like it always triggers once the last node in the viewmodel has a size.

Encountered another issue: The nodes always report a Size of (120, 42) even if they should be bigger, e.g. if they have embedded controls or longer names.

Right, so it seems WPF updates the size of elements a bunch of times until settling on a final value, after which LayoutUpdated is triggered.
Does this produce the correct size for you?
networkView.Events().LayoutUpdated
                .Where(_ => networkView.ViewModel != null && networkView.ViewModel.Nodes.Count > 0)
                .Select(_ => networkView.ViewModel.Nodes.Items.Last().Size)
                .Where(size => size.Width > 0 && size.Height > 0)
                .FirstAsync()
                .Subscribe(size => { Debug.WriteLine("size: "+size); });

(.Events() is part of the ReactiveUI.Events.WPF package)

Looks like that does the trick! Thank you very much!


Add Rootly Integration

Add Rootly Integration
Cf. https://rootly.com/changelog/2022-06-23-backstage-integration
Source: https://github.com/rootlyhq/backstage-plugin

Thanks for this @kwent. The content is great, but the location is slightly wrong. I've moved your content into our plugin directory, rather than our documentation. You can see the result in #840 .
I'll close this since it is now super-seeded.

Thank you 🙏🏻
On Mon, Aug 29, 2022 at 2:14 PM David Tuite @.***>
wrote:

Thanks for this @kwent https://github.com/kwent. The content is great,
but the location is slightly wrong. I've moved your content into our plugin
directory, rather than our documentation. You can see the result in #840
https://github.com/RoadieHQ/marketing-site/pull/840 .
I'll close this since it is now super-seeded.
—
Reply to this email directly, view it on GitHub
https://github.com/RoadieHQ/marketing-site/pull/838#issuecomment-1230868697,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGWZJAEJXLWND6W3FS5QYDV3UR3TANCNFSM57ZCO5FQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Define additional terms for spatial resolution in the GeoDCAT-AP namespace?

:information_source: Following from background discussion in https://github.com/SEMICeu/GeoDCAT-AP/issues/3

DCAT-AP 2 includes two properties from DCAT 2 to specify spatial and temporal resolution:

dcat:spatialResolutionInMeters
dcat:temporalResolution

They will therefore be eventually inherited by the future version of GeoDCAT-AP - ideally, taking into account backward compatibility.
It is worth noting, however, that dcat:spatialResolutionInMeters cannot express spatial resolution as equivalent scale, so an option would be defining a specific property in the GeoDCAT-AP namespace.
Based on the DCAT 2 approach, this property could be named
geodcatap:spatialResolutionAsEquivalentScale
or, shortly:
geodcatap:spatialResolutionAsScale
and take as value an xsd:decimal expressing the fraction. E.g.:
a:Dataset a dcat:Dataset ;
  geodcatap:spatialResolutionAsScale "0.001"^^xsd:decimal ;
.

would state that the spatial resolution of the dataset in equivalent scale is 1:1,000.
This solution can also be extended to other types of spatial resolution:

geodcatap:spatialResolutionAsAngularDistance or, shortly,  geodcatap:spatialResolutionInDegrees
geodcatap:spatialResolutionAsVerticalDistanceInMeters (yes, that's terribly long)

The corresponding tentative definitions:
geodcatap:spatialResolutionAsScale a rdf:Property ;
  rdfs:label "spatial resolution as equivalent scale"@en ;
  rdfs:comment """Spatial resolution expressed as equivalent scale,
    measured by using a representative fraction (e.g., 1:1,000, 1:1,000,000)."""@en ;
  rdfs:range xsd:decimal ;
 .

geodcatap:spatialResolutionInDegrees a rdf:Property ;
  rdfs:label "spatial resolution as angular distance"@en ;
  rdfs:comment """Spatial resolution expressed as angular distance,
    measured in decimal degrees."""@en ;
  rdfs:range xsd:decimal ;
 .

geodcatap:spatialResolutionAsVerticalDistanceInMeters a rdf:Property ;
  rdfs:label "spatial resolution as vertical distance"@en ;
  rdfs:comment """Spatial resolution expressed as vertical distance,
    measured in metres."""@en ;
  rdfs:range xsd:decimal ;
 .

The section 6.13 in the Data Quality Vocabulary (DQV) provides some examples on how spatialResolutionAsEquivalentScale and spatialResolutionAsAngularDistance can be expressed using the properties defined in that vocabulary.
That approach can be adopted without defining additional properties.  DCAT-AP itself suggests to use DQV for describing spatial precision, accuracy, resolution and other statistics.

Thanks, @AntoRot .
Actually, the proposal of using DQV was the original one in https://github.com/SEMICeu/GeoDCAT-AP/issues/3 , where also some possible issues are summarised. Please note, however, that this will still require the definition of new terms.
I'll try to summarise below how to use DQV, so we could better compare it with the idea of extending DCAT2. BTW, for this discussion, it would be worth also looking at https://github.com/w3c/dxwg/issues/84 , which gives the background behind the decision of defining  dcat:spatialResolutionInMeters.
As explained in https://github.com/SEMICeu/GeoDCAT-AP/issues/3

[...] DQV models this information as observations / measurements of a given quality metric (which corresponds to a given type of resolution).
[...]
This would however require the definition of two groups of individuals:

Those corresponding to the different types of resolution (denoting a quality metric).
Those corresponding to each of the different levels of resolution (denoting the measurement of a specific quality metric).

About the first group, they could be defined (in the GeoDCAT-AP namespace) as follows:
:SpatialResolutionAsEquivalentScale a dqv:Metric;
  skos:prefLabel "Spatial resolution as equivalent scale"@en ;
  skos:definition """Spatial resolution expressed as equivalent scale,
	                 by using a representative fraction (e.g., 1:1,000,
                     1:1,000,000)."""@en ;
  dqv:expectedDataType xsd:decimal ;
  dqv:inDimension dqv:precision .

:SpatialResolutionAsDistance a dqv:Metric;
  skos:prefLabel "Spatial resolution as distance"@en ;
  skos:definition "Spatial resolution expressed as distance."@en ;
  dqv:expectedDataType xsd:decimal ;
  dqv:inDimension dqv:precision .

:SpatialResolutionAsHorizontalGroundDistance a dqv:Metric;
  skos:prefLabel "Spatial resolution as distance"@en ;
  skos:definition "Spatial resolution expressed as horizontal ground distance."@en ;
  dqv:expectedDataType xsd:decimal ;
  dqv:inDimension dqv:precision .

:SpatialResolutionAsVerticalDistance a dqv:Metric;
  skos:prefLabel "Spatial resolution as vertical distance"@en ;
  skos:definition "Spatial resolution expressed as vertical distance."@en ;
  dqv:expectedDataType xsd:decimal ;
  dqv:inDimension dqv:precision .

:SpatialResolutionAsAngularDistance a dqv:Metric;
  skos:definition "Spatial resolution as angular distance"@en ;
  skos:definition "Spatial resolution expressed as angular distance."@en ;
  dqv:expectedDataType xsd:decimal ;
  dqv:inDimension dqv:precision .

The second group of individuals could be instead defined in each metadata record.
The resulting specification of spatial resolution in a metadata record could be something like:
my:dataset a dcat:Dataset;
  dqv:hasQualityMeasurement [ a dqv:QualityMeasurement ;
    dqv:isMeasurementOf :SpatialResolutionAsEquivalentScale ;
    dqv:value "0.000001"^^xsd:decimal
  ] ;
  .

your:dataset a dcat:Dataset;
  dqv:hasQualityMeasurement [ a dqv:QualityMeasurement ;
    dqv:isMeasurementOf :SpatialResolutionAsDistance ;
    dqv:value "1000"^^xsd:decimal ;
    sdmx-attribute:unitMeasure <http://www.wurvoc.org/vocabularies/om-1.8/metre>
  ] ;
  .

So, should we go for DQV or extend DCAT2?

I continue to prefer the option to use the DQV properties. In both approaches the first group of individuals should be defined anyway altough in a different way, but in case of DQV an existing solution would be reused, although more complex.
On the other side, defining the new properties as extension of DCAT2 would offer a simplest way to express the resolution.
In any case, as GeoDCAT-AP covers ISO core and INSPIRE metadata, only the corresponding property (i.e. SpatialResolutionAsEquivalentScale in addition to dcat:spatialResolutionInMeters already available) could be defined.

Thanks, @AntoRot .
Actually, although complex, the DQV-based solution provides a common pattern which makes it easier querying metadata compared with having distinct properties for each spatial resolution type. Moreover, it is more sustainable, as it allows a consistent definition of additional types of spatial resolution, if need be.
There are also a couple of other aspects in favour of DQV:

The two approaches are not mutually exclusive, and they could be mapped to each other

As you said earlier, @AntoRot , the use of DQV is recommended in DCAT. Moreover, DCAT may eventually extend support for other types of spatial resolution in its next version - see https://github.com/w3c/dxwg/issues/1263 & https://github.com/w3c/dxwg/issues/1266 . So, DQV might be a safer option for the moment

Based on that, I would propose to go for DQV, and consolidate the draft definitions in https://github.com/SEMICeu/GeoDCAT-AP/issues/15#issuecomment-738277249

So, trying to consolidate the definitions:

Should we merge these two into one?

:SpatialResolutionAsDistance a dqv:Metric;
  skos:prefLabel "Spatial resolution as distance"@en ;
  skos:definition "Spatial resolution expressed as distance."@en ;
  dqv:expectedDataType xsd:decimal ;
  dqv:inDimension dqv:precision .

:SpatialResolutionAsHorizontalGroundDistance a dqv:Metric;
  skos:prefLabel "Spatial resolution as horizontal ground distance"@en ;
  skos:definition "Spatial resolution expressed as horizontal ground distance."@en ;
  dqv:expectedDataType xsd:decimal ;
  dqv:inDimension dqv:precision .

In ISO 19115 "distance" is simply defined as "ground sample distance", that becomes "horizontal ground sample distance" in ISO 19115-1. This rewording I think was justified in order to distinguish it from the new metadata elements introduced in the latest version of the Standard, i.e. "vertical" and "angularDistance" and consequently the two elements corresponds, also because it was not included as revision in the Annex G.
Consequently, I think that we should merge the two properties.
Concerning the definition of the first group of individuals you proposed in your earlier comment, seen the reasoning made in #23 about keeping properties mapped to elements coming from ISO 19115-1 not covered by the GeoDCAT-AP mappings, no objections to also add the properties corresponding to ISO 19115-1 metadata elements mentioned above, contrary to what I said in the previous comment.

Thanks, @AntoRot .
So, maybe we can just extend the first one with some additional textual explanation:
:SpatialResolutionAsDistance a dqv:Metric;
  skos:prefLabel "Spatial resolution as distance"@en ;
  skos:definition """Spatial resolution expressed as distance. It corresponds to the notion of spatial resolution as
    "ground distance" of ISO 19115:2003 and "horizontal ground distance" of ISO 19115-1:2014."""@en ;
  dqv:expectedDataType xsd:decimal ;
  dqv:inDimension dqv:precision .

WDYT?

Another point:

Are you happy with the textual descriptions of this individuals? Is there anything you thing should be added / revised?

I created a full definition in PR https://github.com/SEMICeu/GeoDCAT-AP/pull/54
Please check it out.
@riccardoAlbertoni , as you are co-editor of DQV, it would be great if you could kindly review this work, and let us know if there's anything wrong and/or to be improved. Thanks!

@andrea-perego I think that the textual descriptions of both SpatialResolutionAsDistance and other individuals are fine.
Thanks.

Thanks, @AntoRot .
RDF vocabulary and specification updated via PR https://github.com/SEMICeu/GeoDCAT-AP/pull/54
PROPOSED RESOLUTION: Implement these changes in the current draft with the purpose of supporting the DQV approach for spatial resolution in version 2 of GeoDCAT-AP

I created a full definition in PR #54
Please check it out.
@riccardoAlbertoni , as you are co-editor of DQV, it would be great if you could kindly review this work, and let us know if there's anything wrong and/or to be improved. Thanks!

@andrea-perego: Thank you for pointing to me the use of DQV into GeoDCAT-AP. I  have given a quick read to it. The overall approach seems consistent with the DQV; I suggested some very minor changes in the related PR. I might not be fully aware of the whole context, so please feel free to ignore my rephasings if they do not apply to that specific context.

Many thanks for your review, @riccardoAlbertoni . Much appreciated.
I applied most of your suggested revisions, and left a comment for other ones, proposing a different revision.

Many thanks for your review, @riccardoAlbertoni . Much appreciated.
I applied most of your suggested revisions, and left a comment for other ones, proposing a different revision.

Thanks, it works for me.

Revisions applied, and final editorial fixes and revision completed.
With 1 positive vote and no negative vote, the proposed resolution can be considered approved.
I'm going to merge PR https://github.com/SEMICeu/GeoDCAT-AP/pull/54 and close this issue.
@AntoRot , @riccardoAlbertoni , thanks for your contributions.


test: add basic migrations test

@cjohnhanson looks like the integration tests works - its at least triggering the current failures


Toggle Dark mode

This is a feature request to implement a toggles dark mode into the website so that it make it more appealing and also becomes easier to use this at night.
@allanoguis I would like to work on this issue.
Assign this to me under gssoc-ext and hacktoberfest-accepted labels

Hi @Sarthakkashyapp we already have dark mode enabled on the site. please check your forked repo to make sure that it is the updated version of the project. Cheers!


BUGFIX:

Fixed the bug of the kernel not fully processing all the items when the batch * height * width > number of threads spawned by adding a layer of for-loop
two spaces for minor performance increase:

instead of taking hue_delta as a global memory, take in the value inside hue_delta in order to eliminate unnecessary global memory read
make the copying performed in this conditional: if (!AdjustHue && !AdjustSaturation && !AdjustV) access global memory with coalesced accesses

@chsigg
a small bugfix of adjust_hsv_nhwc kernel ( more details in the commit note )

@tensorflow-bot
run test again

@chsigg
Two Windows Bazel builds failed. Could you help me out?
The error output is:
ERROR: T:/src/github/tensorflow/tensorflow/lite/python/interpreter_wrapper/BUILD:59:1: Linking of rule '//tensorflow/lite/python/interpreter_wrapper:_tensorflow_wrap_interpreter_wrapper.so' failed (Exit 1000): link.exe failed: error executing command


Error: certificate has expired

hi can you help me

verbose: error raised by node:7900 connection:  certificate has expired {"code":"CERT_HAS_EXPIRED","stack":"Error: certificate has expired\n    at TLSSocket.onConnectSecure (node:_tls_wrap:1539:34)\n    at TLSSocket.emit (node:events:513:28)\n    at TLSSocket._finishInit (node:_tls_wrap:953:8)\n    at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:734:12)","timestamp":"2023-01-10T10:40:49.500Z"}
error: caught error 503 connection failed {"body":{"code":"ServiceUnavailable","message":"connection failed"},"jse_info":{},"jse_shortmsg":"connection failed","stack":"ServiceUnavailableError: connection failed\n    at Object.createServiceUnavailableError (/app/src/server/errors.js:56:44)\n    at TLSSocket. (/app/src/connection/connectionService.js:104:20)\n    at TLSSocket.emit (node:events:525:35)\n    at node:net:301:12\n    at TCP.done (node:_tls_wrap:588:7)","timestamp":"2023-01-10T10:40:49.500Z"}

and now the blocks are out of sync，can you help me out ?
image: symbolplatform/symbol-server:gcc-<IP_ADDRESS>

Hi, Here is the docs on cert renewal - https://github.com/fboucquez/symbol-bootstrap/blob/dev/docs/renewCertificates.md
If you need further help you should ask on discord - https://discord.com/channels/856325968096133191/862674505193488415

@Wayonb it works, thank you for your help !


BC-106 GitHub pages custom domain

Description

fix for custom domain base url

This PR solves BC-106.
Steps completed:

According to our definition of done, I have completed the following steps:

[ ] User stories met
[ ] Storybook stories
[x] Unit tests added
[ ] Linting passing
[ ] Unit tests passing
[ ] Docs updated (including config and env variables)
[ ] Translations added
[ ] UX tested
[ ] Browsers / platforms tested
[ ] Rebased & ready to merge without conflicts
[x] Reviewed own code

I think the tests are failing because of environment issues.  Will fix later, since Michal is no longer working on this project.


False positive PD008 when using zipfile.Path.at

ruff==0.0.267 has a false positive PD008:
import io
import zipfile

class MockBinaryFile(io.BytesIO):
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)

    def close(self):
        pass  # Don't allow closing the file, it would clear the buffer

zip_buffer = MockBinaryFile()

with zipfile.ZipFile(zip_buffer, "w") as zf:
    zf.writestr("dir/file.txt", "This is a test")

# Reset the BytesIO object's cursor to the start.
zip_buffer.seek(0)

with zipfile.ZipFile(zip_buffer, "r") as zf:
    zpath = zipfile.Path(zf, "/")

dir_name, file_name = zpath.at.split("/")

> ruff --select=PD008 a.py
a.py:24:23: PD008 Use `.loc` instead of `.at`.  If speed is important, use numpy.
   |
24 | dir_name, file_name = zpath.at.split("/")
   |                       ^^^^^^^^ PD008
   |

Found 1 error.

Thanks! Some of the PD false positives are hard to avoid, but this one should be fixable.


gem: add deprecation notice

and add links to https://github.com/q9f/eth.rb

what do you think @kurotaky


chore: remove b64 from falco dependencies

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
b64 seems completely unused, i think we can remove it
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
chore: remove b64 from falco dependencies

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: a6c6e8fc1266656e3f984ebeae4362a61521abbe

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


feat: use SPARQL for fetching the search results

This PR updates the search API of the Research App. We now use Elasticsearch for fetching search results. But SPARQL gives much greater power. This PR replaces ES with SPARQL. This is a backward-compatible change and doesn't (or shouldn't) impact the frontend.

Looks good. All id's will be urls after this change? This should not be a problem. But we should tests the filtering after this change just to be sure.

Good question. The IDs in the facets will continue to be literals/names, as is currently the case: these literals still come from Elasticsearch. But the IDs in the details of heritage objects (i.e. the search results) will become URLs.


Update CONVENTIONS file

Rendered view

Add something for use of full location not  loc (found in shader mappings)

I think this can be merged. I don't see why this needs to all be figured out right now.


Deleting a custom header removes all custom headers

Using the message[header] = nil method for removing a custom header removes ALL custom headers on that message. See below for an IRB session demonstrating the issue.
ruby-1.9.2-p180 :001 > require 'mail'
 => true
ruby-1.9.2-p180 :002 > m = Mail::Message.new
 => #<Mail::Message:2153412800, Multipart: false, Headers: >
ruby-1.9.2-p180 :003 > m[:test] = '123'
 => "123"
ruby-1.9.2-p180 :004 > m[:foo] = '456'
 => "456"
ruby-1.9.2-p180 :005 > m.header
 => test: 123
foo: 456

ruby-1.9.2-p180 :006 > m[:foo] = nil
 => nil
ruby-1.9.2-p180 :007 > m.header
 =>
ruby-1.9.2-p180 :008 >

The last m.header call should return 'test: 123' but it returns nothing instead.
However, deleting the field object from the header fields list DOES work:
ruby-1.9.2-p180 :001 > require 'mail'
 => true
ruby-1.9.2-p180 :002 > m = Mail::Message.new
 => #<Mail::Message:2153303600, Multipart: false, Headers: >
ruby-1.9.2-p180 :003 > m[:test] = '123'
 => "123"
ruby-1.9.2-p180 :004 > m[:foo] = '456'
 => "456"
ruby-1.9.2-p180 :005 > m.header
 => test: 123
foo: 456

ruby-1.9.2-p180 :006 > m.header.fields.delete_if {|field| field.name == 'foo'}
 => [123]
ruby-1.9.2-p180 :007 > m.header
 => test: 123

ruby-1.9.2-p180 :008 >

I've reproduced this as well.  It has to do with the <=> method in field.rb.
def <=>( other )
  self_order = FIELD_ORDER.rindex(self.name.to_s.downcase) || 100
  other_order = FIELD_ORDER.rindex(other.name.to_s.downcase) || 100
  self_order <=> other_order
end

Which returns 0 when comparing any custom fields.  Which in turn results in  "fields.delete_if { |f| selected.include?(f) }" deleting every custom field.


A set of rules for Linux ELFs

This PR is for some Linux rules as part of https://github.com/fireeye/capa/issues/699.
Example analysis:
+------------------------+------------------------------------------------------------------------------------+
| md5                    | 7351f8a40c5450557b24622417fc478d                                                   |
| sha1                   | 8766d7e0c943ea66ebe90030617881a899b2aa11                                           |
| sha256                 | 0423258b94e8a9af58ad63ea493818618de2d8c60cf75ec7980edcaa34dcc919                   |
| path                   | /[REDACTED]/redxor/po1kitd-update-k                              |
+------------------------+------------------------------------------------------------------------------------+

+------------------------+------------------------------------------------------------------------------------+
| ATT&CK Tactic          | ATT&CK Technique                                                                   |
|------------------------+------------------------------------------------------------------------------------|
| DEFENSE EVASION        | Obfuscated Files or Information:: T1027                                            |
|                        | Obfuscated Files or Information::Indicator Removal from Tools T1027.005            |
| DISCOVERY              | System Information Discovery:: T1082                                               |
| EXECUTION              | Command and Scripting Interpreter::Unix Shell T1059.004                            |
| PERSISTENCE            | Boot or Logon Autostart Execution::XDG Autostart Entries T1547.013                 |
|                        | Boot or Logon Initialization Scripts::RC Scripts T1037.004                         |
|                        | Event Triggered Execution::Unix Shell Configuration Modification T1546.004         |
+------------------------+------------------------------------------------------------------------------------+

+-----------------------------+-------------------------------------------------------------------------------+
| MBC Objective               | MBC Behavior                                                                  |
|-----------------------------+-------------------------------------------------------------------------------|
| ANTI-STATIC ANALYSIS        | Disassembler Evasion::Argument Obfuscation [B0012.001]                        |
| COMMAND AND CONTROL         | C2 Communication::Receive Data [B0030.002]                                    |
|                             | C2 Communication::Send Data [B0030.001]                                       |
| COMMUNICATION               | DNS Communication::Resolve [C0011.001]                                        |
|                             | HTTP Communication::Send Request [C0002.003]                                  |
|                             | Socket Communication::Connect Socket [C0001.004]                              |
|                             | Socket Communication::Create TCP Socket [C0001.011]                           |
|                             | Socket Communication::Create UDP Socket [C0001.010]                           |
|                             | Socket Communication::Receive Data [C0001.006]                                |
|                             | Socket Communication::Send Data [C0001.007]                                   |
|                             | Socket Communication::TCP Client [C0001.008]                                  |
| CRYPTOGRAPHY                | Encrypt Data::RC4 [C0027.009]                                                 |
|                             | Generate Pseudo-random Sequence::RC4 PRGA [C0021.004]                         |
| DATA                        | Check String:: [C0019]                                                        |
|                             | Encode Data::Base64 [C0026.001]                                               |
| DEFENSE EVASION             | Obfuscated Files or Information::Encoding-Standard Algorithm [E1027.m02]      |
| FILE SYSTEM                 | Delete File:: [C0047]                                                         |
|                             | Read File:: [C0051]                                                           |
|                             | Writes File:: [C0052]                                                         |
| IMPACT                      | Remote Access::Reverse Shell [B0022.001]                                      |
| PROCESS                     | Create Mutex:: [C0042]                                                        |
|                             | Create Process:: [C0017]                                                      |
|                             | Create Thread:: [C0038]                                                       |
|                             | Terminate Process:: [C0018]                                                   |
+-----------------------------+-------------------------------------------------------------------------------+

+------------------------------------------------------+------------------------------------------------------+
| CAPABILITY                                           | NAMESPACE                                            |
|------------------------------------------------------+------------------------------------------------------|
| contain obfuscated stackstrings                      | anti-analysis/obfuscation/string/stackstring         |
| read and send data from client to server (2 matches) | c2/file-transfer                                     |
| receive and write data from server to client         | c2/file-transfer                                     |
| create unix reverse shell                            | c2/shell                                             |
| execute shell command received from socket           | c2/shell                                             |
| get current user                                     | collection                                           |
| create UDP socket (4 matches)                        | communication/socket/udp/send                        |
| act as TCP client                                    | communication/tcp/client                             |
| encode data using Base64                             | data-manipulation/encoding/base64                    |
| reference Base64 string                              | data-manipulation/encoding/base64                    |
| encrypt data using RC4 PRGA (2 matches)              | data-manipulation/encryption/rc4                     |
| change file permission (5 matches)                   | host-interaction/file-system                         |
| delete file (3 matches)                              | host-interaction/file-system/delete                  |
| move file (2 matches)                                | host-interaction/file-system/move                    |
| get CPU information                                  | host-interaction/hardware/cpu                        |
| get memory information                               | host-interaction/hardware/memory                     |
| create locked file                                   | host-interaction/mutex                               |
| resolve DNS (2 matches)                              | host-interaction/network/dns/resolve                 |
| get hostname (2 matches)                             | host-interaction/os/hostname                         |
| get distribution                                     | host-interaction/os/version                          |
| get kernel version                                   | host-interaction/os/version                          |
| terminate process via kill (3 matches)               | host-interaction/process/terminate                   |
| create thread (2 matches)                            | host-interaction/thread/create                       |
| persist via .desktop autostart                       | persistence                                          |
| persist via shell profile or rc file                 | persistence                                          |
| persist via rc script                                | persistence/service                                  |
+------------------------------------------------------+------------------------------------------------------+

PR for test file: https://github.com/fireeye/capa-testfiles/pull/104

I'd like to propose the following conventions for naming rules:

when naming an OS-specific rule, use the form "XXXXX on ZZZZZ", like "get current user on Linux". if there's a specific mechanism, then it would be like `XXXX via YYYYY on ZZZZZ", like "encrypt data with RC4 via OpenSSL on Windows".

start with naming the OSes we have experience and examples for (like "...on Linux"). when someone subsequently confirms the behavior matches somewhere else (like on macOS) then we can and should rename the rule. i anticipate that many patterns will work on many unix-like operating systems; however, defining these sets may be tedious and i dont want to over-engineering things too soon. so, i'd propose that we focus on the rules and samples that we know work well.

let me know what you all think. the goal isn't to be annoying or add overhead - just to strive for consistency when it makes sense. once we reach a consensus, i'll update the rule documentation with these suggestions.

im going to take a stab at https://github.com/fireeye/capa/issues/737 (substring feature) because it will improve a bunch of these rules. then i'll propose some changes to this PR and we'll get this merged in. i have no major concerns with the logic here - just some tweaks to naming, splitting up a couple rules, and making use of - os: linux, etc.

I'm on board with the OS conventions! Thanks for handling the substring and the updates here!


feat(notion): reorder/hide props in create database page command

Description

adds a way to control which props to show/hide, and reorder them
todo:

[ ] prevent hiding the title (?)
[ ] add option to show set the end date
[ ] create quicklink to a certain view as a "template"
[ ] make the edit properties page look nicer

Fixes #5016 specify/reorder props in create db page
Fixes #8479 dupe of #5016
Fixes #8443 dupe of #5016
Fixes #2979 old, reorder props
Fixes #2727 old, reorder props
Fixes #9010 hide certain props
Fixes #8438 end date option
Screencast

https://github.com/raycast/extensions/assets/52634785/65b7ae69-c600-438d-b178-36aea47abb52
Checklist

[ ] I read the extension guidelines
[ ] I read the documentation about publishing
[ ] I ran npm run build and tested this distribution build in Raycast
[ ] I checked that files in the assets folder are used by the extension itself
[ ] I checked that assets used by the README are placed outside of the metadata folder

This looks amazing! Way to go!
I think the "show end date" (#8438) fixes need to be moved to a separate PR, as it doesn't relate to this branch.

Sure I can do that. BTW, this new reorder props fix still has some weird bugs I haven't gotten to resolve. Hopefully i'll get the time to fix them and this branch should be good to go

This is looking very nice! Will be game changing for getting things into Notion quickly.


Problem with os.detected.arch on AARCH64

I know that this library does not support AARCH64 at the moment but I tried to build it and see whether I can help supporting it.
Running mvn clean package starts with:
[INFO] ------------------------------------------------------------------------
[INFO] Detecting the operating system and CPU architecture
[INFO] ------------------------------------------------------------------------
[INFO] os.detected.name: linux
[INFO] os.detected.arch: aarch_64
...

and later fails with:
[ERROR] Failed to execute goal on project netty-incubator-transport-native-io_uring: Could not resolve dependencies for project io.netty.incubator:netty-incubator-transport-native-io_uring:jar:0.0.2.Final-SNAPSHOT: Failure to find io.netty:netty-transport-native-unix-common:jar:linux-aarch_64:4.1.54.Final in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]

netty-transport-native-unix-common:4.1.54 does have a binary for aarch64 but there is no _ in its classifier (linux-aarch64):
https://repo1.maven.org/maven2/io/netty/netty-transport-native-unix-common/4.1.54.Final/netty-transport-native-unix-common-4.1.54.Final-linux-aarch64.jar
I have no idea why os-maven-plugin puts this _ in the arch name (https://github.com/trustin/os-maven-plugin/#property-osdetectedarch) but this leads to issues like this one and https://github.com/netty/netty-tcnative/issues/552.

@trustin can you check why the plugin does this and if its a bug or not ?

It's not a bug but a convention. <main_architecture>_<bitmode> for consistency.

We can of course discuss about this and make a breaking change if it doesn't make much sense. :smile:

The problem is in the inconsistency between the classifiers in the different Netty modules. Some use aarch_64 and others aarch64. It seems some modules use os.detected.arch and others - os.arch.

I am open to use whatever seems to be more correct...

Could Netty modules upload with aarch_64 classifier, then?

I was going to suggest to use aarch64 (i.e. os.arch) because of two reasons:

it is more common (uname -p, Linux buildtools (aarch64-linux-gnu-...), etc.)
backward compatibility in old modules like netty-transport-native-unix-common

But this breaks for x86 systems. Java's System.getProperty("os.arch") returns amd64 instead of x86_64.
So, I agree with @trustin that it would be better to use os-maven-plugin to normalize the architectures (i.e. aarch_64). But this may lead to problems for the old modules which already use os.arch.

@martin-g I guess as long as we update all of these together it should be fine...

After upgrading my Ubuntu 20.04.1 to kernel 5.10-rc6 I was able to run all tests successfully on AARCH64!
I had to make 3 things:

Workaround the issue in this ticket with :

diff --git pom.xml pom.xml
index bd35fc8..53c620a 100644
--- pom.xml
+++ pom.xml
@@ -79,7 +79,7 @@
     <skipTests>true</skipTests>
     <netty.version>4.1.54.Final</netty.version>
     <netty.build.version>28</netty.build.version>
-    <jni.classifier>${os.detected.name}-${os.detected.arch}</jni.classifier>
+    <jni.classifier>${os.detected.name}-${os.arch}</jni.classifier>
   </properties>

   <build>
@@ -369,7 +369,7 @@
               <execution>
                 <id>build-native-lib</id>
                 <configuration>
-                  <name>netty_transport_native_io_uring_${os.detected.arch}</name>
+                  <name>netty_transport_native_io_uring_${os.arch}</name>
                   <nativeSourceDirectory>${nativeSourceDirectory}</nativeSourceDirectory>
                   <libDirectory>${project.build.outputDirectory}</libDirectory>
                   <!-- We use Maven's artifact classifier instead.
@@ -405,7 +405,7 @@
                       <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
                     </manifest>
                     <manifestEntries>
-                      <Bundle-NativeCode>META-INF/native/libnetty_transport_native_io_uring_${os.detected.arch}.so; osname=Linux; processor=${os.detected.arch},*</Bundle-NativeCode>
+                      <Bundle-NativeCode>META-INF/native/libnetty_transport_native_io_uring_${os.arch}.so; osname=Linux; processor=${os.arch},*</Bundle-NativeCode>
                       <Automatic-Module-Name>${javaModuleName}</Automatic-Module-Name>
                     </manifestEntries>
                     <index>true</index>

manually make some symlinks:

ll target/native-build/target/lib/
total 2.0M
-rw-r--r-- 1 ubuntu ubuntu 1.9M Aug 21 11:19  libnetty_tcnative_linux_aarch64.so
lrwxrwxrwx 1 ubuntu ubuntu   34 Nov 30 13:14  libnetty_tcnative.so -> libnetty_tcnative_linux_aarch64.so
lrwxrwxrwx 1 ubuntu ubuntu   34 Nov 30 13:13 'libnetty_tcnative-<EMAIL_ADDRESS>-> libnetty_tcnative_linux_aarch64.so
-rwxr-xr-x 1 ubuntu ubuntu  86K Nov 30 15:42  libnetty_transport_native_io_uring_aarch64-0.0.2.Final-SNAPSHOT.so*
-rwxr-xr-x 1 ubuntu ubuntu 1.4K Nov 30 15:42  libnetty_transport_native_io_uring_aarch64.la*
lrwxrwxrwx 1 ubuntu ubuntu   66 Nov 27 13:46  libnetty_transport_native_io_uring_aarch_64.so -> libnetty_transport_native_io_uring_aarch64-0.0.2.Final-SNAPSHOT.so*
lrwxrwxrwx 1 ubuntu ubuntu   66 Nov 30 15:42  libnetty_transport_native_io_uring_aarch64.so -> libnetty_transport_native_io_uring_aarch64-0.0.2.Final-SNAPSHOT.so*
lrwxrwxrwx 1 ubuntu ubuntu   66 Nov 27 13:45  libnetty_transport_native_io_uring.so -> libnetty_transport_native_io_uring_aarch64-0.0.2.Final-SNAPSHOT.so*

export LD_LIBRARY_PATH to /home/ubuntu/git/netty/netty-incubator-transport-io_uring/target/native-build/target/lib

and the result is:
[INFO] Results:
[INFO]
[WARNING] Tests run: 382, Failures: 0, Errors: 0, Skipped: 65
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  02:55 min
[INFO] Finished at: 2020-11-30T15:45:00Z

I hope this is useful to the other ARM64 users out there!


add Mobile App Pentest

What difference does this make ? I feel its better to maintain iOS and Android security separately.


Missing isBroken property into Document types

Add isBroken property into Document types for link resolver
export interface Document {
    // ...
   isBroken?: boolean;
}

What do you thing ?

Hey, as stated here: https://github.com/prismicio/prismic-javascript/issues/27#issuecomment-833459653 first-class TypeScript support is being added in the next version of this kit ☺

Hey @jevillard, I'm happy to announce we just released in beta @prismicio/client and @prismicio/helpers (the new prismic-dom). Stable release is scheduled for November!
Those two packages now come with first-class TypeScript support so I figured out you'd be interested! You can read more about how to give them a try here, your feedback is also very much appreciated~
Cheers!

Fixed in v6 🎉 Thank you for your contribution!
https://prismic.io/docs/technical-reference/prismicio-client?version=v6
If you're still experiencing the issue with the new kit, feel free to reopen!


Invalid store example

https://svelte.technology/guide#the-basics
The supplied example code
import { Store } from 'svelte/store.js';

const store = new Store({
	name: 'world'
});

const { name } = store.get(); // 'world'

store.on('state', ({ current }) => {
	console.log(`hello ${current.name}`);
}); // 'hello world'

store.set({ name: 'everybody' }); // 'hello everybody'

implies that two messages will be logged, "hello world" and "hello everybody".
This is wrong though, the state listener only gets called for changes that occur after it is attached so it never sees the original state.
REPL repro
FWIW I'd love if this example did work as written, but I don't see any support in the generic .on() handler that would let the parent object know when a new listener is attached for a state.

Ah, yeah. This is because you used to do this...
store.observe('name', name => {
  console.log(`hello ${name}`);
});

...and that did fire immediately. I must have missed that comment when updating the docs.
observe was removed in v2 because it's only useful to a subset of people but adds non-trivial weight to a component. The state and update events (and their lifecycle hook counterparts) are more powerful and the code is more concise. But since observe is useful, for the reason you identify, it's still available via svelte-extras:
import { Store } from 'svelte/store.js';
import { observe } from 'svelte-extras';

class MyStore extends Store {}
MyStore.prototype.observe = observe;

const store = new Store({
  name: 'world'
});

const { name } = store.get(); // 'world'

store.observe('name', name => {
  console.log(`hello ${name}`);
});  // 'hello world'

store.set({ name: 'everybody' }); // 'hello everybody'


Add DataGridTableScroll demo #57820

Pull Request
📖 Description
Added new DataGrid demo to show how to use "Table mode" on FluentDataGrid based on discussion #57820

Could you add a screenshot in the PR description to simplify the future Release note?

@dvoituron I would but the app doesn't compile for me:
 build
1>> node ./esbuild.config.mjs
1>
1>file:///G:/Programmierung/fluentui-blazor/src/Core.Assets/esbuild.config.mjs:2
1>import pkg from './package.json' assert { type: 'json' }
1>                                 ^^^^^^
1>
1>SyntaxError: Unexpected identifier 'assert'
1>    at compileSourceTextModule (node:internal/modules/esm/utils:337:16)
1>    at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:163:18)
1>    at callTranslator (node:internal/modules/esm/loader:430:14)
1>    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:436:30)
1>    at async ModuleJob._link (node:internal/modules/esm/module_job:106:19)
1>
1>Node.js v22.2.0

I think I might have the wrong version of node. But couldn't find any info in the repo what I need to install for it.

Weird. This Node version seems enough. Are you using VS 2022 Preview? Or could tou run ˋnpm install` from the Assets project folder ?

@dvoituron I'm using VS 17.10.0

I'm also using this VS and Node 20.10.0 with the same npm fund result.
Microsoft Visual Studio Professional 2022 (64-bit) - Preview
Version 17.10.0 Preview 7.0

The problem is probably elsewhere :-(

@dvoituron it is the nodeJS version. Downgrading to your version works fine for me. Here you go:

@microsoft-github-policy-service agree


QRNormal组件如何设置参数才能正常显示posType为roundRect的二维码

+1, component QRNormal renders completely broken QR code when passed with posType="roundRect":

Sandbox with reproduction: https://codesandbox.io/p/sandbox/modern-fire-w5gwqg?file=%2Fsrc%2FApp.js%3A13%2C9-13%2C28

@cuicui520, were you able to find a workaround? 你能找到解决方法吗？

To whoever lands here in the future: this has been fixed in the master branch in https://github.com/CPunisher/react-qrbtf/commit/b4bda9e370f7f3995c807999906d40d61541096f, but not released. You can install the library from github to use this fix (as of now, you need nodejs v16 to compile it because of the outdated webpack version used).


feature: added zod input validation + fixed merge conflicts

I have fixed the merge conflicts, please merge this PR, let me know if there are any changes to make! Thanks.

@PorePranav , i also want to merge this PR but there are issues. And I appreciate your efforts. While working on this in the meantime you can create PR on other issues as well I will merge those.

@PorePranav , I tried to link your code with frontend but it didn't worked. And you can see your deployed link and test those routes at https://quiz-master-backend-git-fork-por-dec0fe-vishal-kumar-s-projects.vercel.app/
and actual backend is deployed at https://quiz-master-backend-six.vercel.app/api you can test both and work to resolve this & update me ASAP!

As I currently don't have access to the deployed frontend, I am not able to pinpoint the issue, but everything is working flawlessly locally. I have changed the code a bit to improve the validation. Please check and confirm once.
Thank you!

@PorePranav, I have accepted your access request.

@PorePranav, I have accepted your access request.

Seems to be working fine on the preview deployment, can you please confirm once?

@PorePranav , Thanks for your wonderful contribution! Since you've made some changes to the tech stack, I would kindly request you to update the backend documentation accordingly. That will also count towards your Hacktoberfest contribution.


replace devkit with developer nuget

Resolves #447
I wish we could build our test code using the production code's nuget package instead of the local artifacts directory, but I don't see how we can do that without complicating our build environments.
How else could we test the nuget?

FYI, looks good, but has conflicts with main.


Fix broken colors in Catppuccin Mocha

themes.json isn't fully parseable in wezterm's import machinery because of these broken color definitions:
    {
      "name": "CatppuccinMocha",
      "black": "#45475A",
      "red": "#F38BA8",
      "green": "#A6E3A1",
      "yellow": "#F9E2AF",
      "blue": "#89B4FA",
      "purple": "#F5C2E7",
      "cyan": "#94E2D5",
      "white": "#BAC2DE",
      "brightBlack": "#585B70",
      "brightRed": "#F38BA8",
      "brightGreen": "#A6E3A1",
      "brightYellow": "#F9E2AF",
      "brightBlue": "#89B4FA",
      "brightPurple": "#F5C2E7",
      "brightCyan": "#94E2D5",
      "brightWhite": "#A6ADC8",
      "foreground": "#",
      "background": "#",
      "cursorColor": "#"
    },

Colors are inserted here based on the upstream:
https://github.com/catppuccin/wezterm/blob/main/dist/catppuccin-mocha.toml#L12 https://github.com/catppuccin/wezterm/blob/main/dist/catppuccin-mocha.toml#L27

Thank you!


Fix py2.7 always passing on travis bug.

In this travis-ci run you can see that the py2.7 build fails with this patch. (and a deliberately failing test).
https://travis-ci.org/cowlicks/dask/jobs/66322652
And in this build you can see that coverage is still working. Coveralls fails to upload but that is because travis is building from my fork.
https://travis-ci.org/cowlicks/dask/jobs/66323148#L1040

Cool.  Merging.  We'll see what happens.

Thanks for handling this!


Add ownbyKyverno field in validatingAdmissionPolicyBinding

Add ownbyKyverno field in validatingadmissionpolicybinding

Related Issue

https://issues.redhat.com/browse/ACM-15318
Description of changes

Add ownbyKyverno field in validatingAdmissionPolicyBinding

/cc @mprahl

/cc @jlpadilla


fix: change execution order for light node upgrade

🐝 PR preview in Swarm
Preview URL: https://bah5acgzatunrqzhzazvhfzobmzmqumalf5ticn77j4jcwei2uwirrd6zf3ra.bzz.link
Swarm Hash: 9d1b1864f9066a72e5c166590a300b2f668137ff4f122b111aa591188fd92ee2
Commit Hash: b5c8abb6d54475aca475f707db0a1197d65e959c
Commit Message: fix: change execution order for light node upgrade


Deploying Kubeflow behind a proxy server

https://www.kubeflow.org/docs/other-guides/kubeflow-behind-proxy/
It do tells us how to install kubeflow behind proxy but nothing on how to configure further more things, for instance I am not able to download anything from inside my pipeline components and the error I get is "no route to host" which is indirectly related to proxy related only, I have searched everywhere but found no fix for this or the ways to bypass proxy from inside standard containers.

I also encountered the same problem. Excuse me, where can I find the information?

@markqiu The Kubeflow Community has not provided that documentation.    You might try the On-Prem SIG (please find notes here...there is a meeting next Wednesday). https://docs.google.com/document/d/1Qs94d9RPxqiZJnTRvL9iHZrx_jnf59HyJFnbyi1AYjQ/edit#heading=h.w4esj4yrc6i
Alternatively, you might try a vendor who provides Kubeflow consulting services for on-prem installations.

/area installation
/kind question
/priority p2
/area on-prem


perf/feature: new serialization format for constraint systems

Description
This PR uses integer compression techniques  to serialize some constraint systems parts containing ids, offsets, etc and bypass our current cbor choice. (cbor is still used for the rest).
As a bench, using lzss.DecompressionTestCircuit with params landing at 90M constraints (plonk), we go from 9225Mb to 2238Mb size, plus, we serialize (and most importantly deserialize) way faster:
benchmark                                      old ns/op        new ns/op      delta
BenchmarkSerialization/serialize_cbor-96<PHONE_NUMBER>1<PHONE_NUMBER>     -94.38%
BenchmarkSerialization/serialize_cbor-96<PHONE_NUMBER>0<PHONE_NUMBER>     -92.55%
BenchmarkSerialization/deserialize_cbor-96<PHONE_NUMBER>20<PHONE_NUMBER>     -95.77%
BenchmarkSerialization/deserialize_cbor-96<PHONE_NUMBER>78<PHONE_NUMBER>     -96.79%

Very nice optimizations! I think in general is good, but in a perfect scenario I would try to figure out if we can work with io.Writer and io.Reader instead of direct byte arrays as imo otherwise we have many copies of very similar structures in memory (constraint system itself, bytes when serializing them and also byte buffer for internal steps a la serializing calldata). But due to applying compression to uints we still cannot get away with all.
And I completely agree that it doesn't make sense for us to include additional compression in the implementation. It should be straightforward to add gzip etc. when the user is interested in it. Otherwise there is too many options (fast or good compression ...)

Yep, it makes sense that if we work with []byte then can have parallel processing which is more important than saving a few GB in settings where memory usage is in tens of GBs anyway. Added the test corpus.
Good to merge from my side.


Consider adding theme starship?

https://github.com/starship/starship

You can easily achieve this yourself without it being added to Prezto.
First, depending on your config, you may also need to add this line to your .zshrc:
setopt prompt_subst interactive_comments

Then, start a new Zsh session and run this from your interactive Zsh prompt:
# install starship if  we haven't already
command -v starship &>/dev/null || sh -c "$(curl -fsSL https://starship.rs/install.sh)"

# add prompt_starship_setup function to Prezto
ZPREZTODIR=${ZPREZTODIR:-${ZDOTDIR:-~}/.zprezto}
echo 'eval "$(starship init zsh)"' >! $ZPREZTODIR/modules/prompt/functions/prompt_starship_setup

Now, starship is setup as an available Prezto prompt. Feel free to then change to it in your .zpreztorc
zstyle ':prezto:module:prompt' theme 'starship'

Thank you! @mattmc3


Fix nether cyclone targeting

I forgot to put the target in Nether Cyclone.
Fix mysticism skill level range for Stone Form and Cleansing Winds

Cool @Torruin, merged!

Cool @Torruin, merged!


Add php 8.3 to the test matrix

Description
This adds PHP 8.3 to the testing matrix. This is in line with the current Laravel 10 supported PHP versions.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (refactoring a current feature, method, etc...)
[ ] Code Coverage (adding/removing/updating/refactoring tests)
[x] New feature (non-breaking change which adds functionality)
[ ] Remove feature (non-breaking change which removes functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Looks like the culprit is laravel/passport package.
Even on the latest stable release 12.3.0 it still requires league/oauth2-server: ^8.5.3, which in turn requires lcobucci/clock, which fixes the PHP version to either 8.1 or 8.2.
Upgrading that package to a later version which supports php8.3 drops php8.1 support.
So I think the best way of dealing with this is wait until we switch to Laravel 11, dropping php8.1 support anyway.


Deciding  -b [close reference bacterium FASTA file]

PLasmidseeker asks for -b [close reference bacterium FASTA file]. I'm looking at Lactobacillus gasseri plasmids but there are multiple strains of L.gasseri, I'm not sure how to choose the reference file? https://www.ncbi.nlm.nih.gov/nuccore

The reference bacterium should be similar to the one in the sample which means the strain needs to be identified first. This could be done with StrainSeeker or with a similar software or even with mapping.
If a random strain of the same species is provided, the overall results might be less accurate.

Thanks a lot!


Call validate independently of form submission

Hey,
what would be the best way to trigger the synchronous validation independently from actually submitting the form.
I am building a multi step form an before proceeding to the second step I'd like to make sure that certain fields are correctly entered. Hence the idea to reuse my existing validation function.

Synchronous validation happens on every render. How would you want to trigger it?

Perhaps with an action?

Perhaps with an action?

That doesn't make sense with the current redux-form architecture, as the sync validation happens entirely in the component, which does not receive actions. The component is given this.props.errors with the results of the sync validation on every render.

Might be a good consideration for v5. Keeps component logic simple.

My idea was to trigger the validation when a link or a button is pressed and to proceed to the next step only after the validation of the fields passed.
So I basically just have to force a rerender and the errors dict should be populated so that I can display the errors like in the synchronous validation example?

@anrie It sounds a little like a wizard form.

Might be a good consideration for v5. Keeps component logic simple.

@davidkpiano Yep, already in the plans. :-)

@erikas I'd say it looks pretty much like the wizard form.
Sorry for the noise and thanks for the great library!

Hi! Is this possible in v6? I have a wizard form with multiple steps on the same redux form component. Could I validate each field separately?
Thanks!

@anaibol did you find a way?

@MaxInMoon I don't think so, I used https://github.com/davidkpiano/react-redux-form that uses another approach.


@conda-forge-admin add user @beckermr

[ ] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @beckermr in conda-forge/astropy-healpix-feedstock#22.


vGPU unlock on arch kvm?

is it possible to patch on Arch and use vGPU for KVM??

what do you want to patch on arch?
But yes this / and all other solutions with vGPU Unlock are working on arch/ubuntu etc pp with KVM (libvirt) or QEMU

i installed patched drivers on Arch but mdev ctl commands doesn't output anything on Arch host