Design for adding a new Quote to a Notable Person page

Hey @forabi @wholesomedev I have added a floated button that brings out a form for input and submitting quote. Waiting for your feedback.

BTW, there is something strange with Stylelint. For CSS it requires:
[stylelint] Expected newline after "," in a multi-line list (value-list-comma-newline-after)
when you format it correctly and push it reformats it back into a single line. Maybe something wrong on my side.

@Maxgrb Thanks for sending this. Here's my feedback so far:

The button looks too strong, and it feels unrelated and foreign to our web app.

Apologies for not being more clear, but:
Even though we are borrowing the Floating Action Button (FAB) concept from Material UI, I don't think Material UI shadows and elevations look good on our UI since we are not actually using Material UI in the rest of the app. Should we tone these things down a bit to make the button appear more native to our app?

The goal of https://github.com/hollowverse/hollowverse/issues/537 is to just design the button and a menu that will open when the button is clicked. We don't need to design the UX for adding a quote just yet.
When the FAB is clicked, it needs to pop-out a menu with items. One item should say "Add a quote". When the user clicks on "Add a quote", nothing will happen (until we design that part of the experience as well)
Again, sorry about not being more clear about that earlier.

In Storybook, there's the "Device" dropdown. From there, you can choose "Responsive" to see what the FAB looks like on a desktop.
I see that on a desktop, the FAB will not stay within the main container of the app. It will follow the edge of the view port, which isn't ideal in my opinion. Can we make the FAB stay within the main container of the app?

@Maxgrb Please hold off on making the changes that I requested. We are currently thinking about the future direction of component development, and the decision may affect how we proceed with this issue.
CC @forabi

@Maxgrb, Fawwaz (@forabi) and I discussed this and we think that we should fully adopt Material Design for Hollowverse. Doing that will allow us to use Material-UI.
The challenge we are facing is that if we start adding Material UI components to our current UI, things will not look harmonious. But this is a compromise that we've decided to live with until we migrate all of our UI to Material UI.
So for this issue, what we need is a Material Design Speed Dial.
The Material Design Speed Dial is implemented in Material-UI here.
Can we use the Material-UI implementation in this issue?
With regard to the Material-UI SpeedDial, I see in their demo that the labels don't show up until the SpeedDial icon is hovered over. That is not ideal. We need the labels to be displayed permanently with the SpeedDial buttons.

Hi @wholesomedev, @forabi,
Do you mean text labels (tooltips "Copy", "Save" in their demo) or action buttons (which appear when hovering on the floated button) should be displayed permanently?
I think keeping buttons opened is possible. But tooltips aren't. As I've seen their code its a part of SpeedDialAction component logic.
https://github.com/mui-org/material-ui/blob/303199d39b42a321d28347d8440d69166f872f27/packages/material-ui-lab/src/SpeedDialAction/SpeedDialAction.js
Another question – do you plan additional actions except "Add Quote" for floating button? Material Design guidelines recommend "A speed dial should include at least three options". I think there is a sense include at least two options. If we have a single option – FAB can handle it itself.
https://material.io/design/components/buttons-floating-action-button.html#types-of-transitions

Do you mean text labels (tooltips "Copy", "Save" in their demo) or action buttons (which appear when hovering on the floated button) should be displayed permanently?

@Maxgrb We are actually just going to use the Speed Dial component from Material-UI as is.

Another question – do you plan additional actions except "Add Quote" for floating button? Material Design guidelines recommend "A speed dial should include at least three options". I think there is a sense include at least two options. If we have a single option – FAB can handle it itself.

@Maxgrb We do plan to add more actions in the future. Actually, we had a rather long discussion in #dev about using the FAB and we were not really sure what the best variant of the FAB we should use. We concluded that the Speed Dial is our best option for now, even if it only has one action currently. The reason we didn't go for a simple FAB (without a Speed Dial) is because the "Add Quote" feature of Hollowverse is not easily conveyed with just an icon. I don't think users would expect that clicking a button that only has a "+" sign is going to add a new quote.

The purpose of speed dial pattern is providing multiple options.

We are aware that this is a violation of the Material Design guidelines and is not probably the best UX. But we evaluated the options and made this trade-off. I don't think clicking twice to perform an action is necessarily a bad action. I think it depends on the context. Anyway, I still think clicking twice is better UX than the confusion an ambiguous button with no clear text would cause.

As for "+" icon – we can use another icon on FAB button that is more related to quote action.

I'm totally okay with a better icon if it can convey "Add Quote".
@wholesomedev Feel free to chime in!

@forabi what do you think about the icon on FAB from the current PR?
Let me know if you decided to go with SpeedDial. Adding this component into the project seems quite simple, it ready-to-use and doesn't require any designing skills. Any way I can help with it :)

@Maxgrb I think a "+" for the main FAB is OK. But we'll need an icon specifically for adding a quote on the Speed Dial Action itself.
@Maxgrb I think we still want to go with SpeedDial. And we still need your skills with selecting colors, icons, etc 😄
Color, component selection, and general UX will continue to be important as we migrate the rest of the website to Material UI.


[spdlog] Update to 1.2.0

Note: regresses arm-uwp and x64-uwp.

@alexkaratarakis What's the problem with x64-uwp ? Can you share more details please?

@alexkaratarakis
Can you review PR again?
I rebased commit to latest spdlog 1.2.0 version. Also, I disabled builds for bench and exmaples, that breaks uwp builds.

@alexkaratarakis @ras0219-msft ping

Looks like we took so long processing that this was automatically picked up as part of our rolling upgrade system[1].
Thanks again for the PR!
[1] https://github.com/Microsoft/vcpkg/commit/9c62c6a37ac940abbb4f19237d9a891881421a1a


Add unchecked TOTP constructor and URL parsing methods

Fixes https://github.com/constantoine/totp-rs/issues/46
This adds TOTP::new_unchecked as discussed.
This also adds TOTP::from_url_unchecked which uses TOTP::new_unchecked internally to allow unchecked URL parsing.
I will rebase #47 after this is merged.

I just noticed I didn't add tests for this. I'll do that later.

Codecov Report
Base: 96.69% // Head: 95.81% // Decreases project coverage by -0.88% :warning:

Coverage data is based on head (d293068) compared to base (d460bd2).
Patch coverage: 75.47% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #48      +/-   ##
==========================================
- Coverage   96.69%   95.81%   -0.89%
==========================================
  Files           4        4
  Lines        1242     1290      +48
==========================================
+ Hits         1201     1236      +35
- Misses         41       54      +13

Impacted Files
Coverage Δ

src/lib.rs
94.65% <75.47%> (-1.39%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Somehow mod operation causes overflow

Related: #6683
53 % 614_889_782_588_491_410 # -617331001(53 is expected)

With -D preview_overflow option it raises OverflowError.

I think it has something to do with differently sized integers(53 is Int32, 614... is Int64), but not all mod operation like this causes overflow. I guess modulo which is larger than a certain number causes error, but seemingly it's not true.
53 % 532_000_782_588_491_410 # overflow
53 % 533_000_782_588_491_410 # no overflow
53 % 534_000_782_588_491_410 # overflow

If I use 53_i64 the problem doesn't appear. I don't know why, but casting to bigger size(in this case Int64) can be a solution.


Use the generic networking constant for shutdown

use standard const, which is better
stop modifying the default in the test, which is ugh a bit :)

/assign mattmoor @dprotaso

/approve


Tree: fix empty primary fields of contextually typed data

Description
This fixes an issue setting an empty primary field of contextually typed data.
Some concerns
It might be arguable, that, in contrast to the sequence fields, for which root.foo = [] makes foo to be "really" non-existent, doing same for the primary fields should not make them to be non-existent, as primary fields have a special meaning.
If not fixed, an issue occurs while creating the chunk tree out of a corresponding delta, since chunkField requires the fields to have at least one node, which is not the case for primary fields set via contextually typed.
Reviewer Guidance
The review process is outlined on this wiki page.

It might be arguable, that, in contrast to the sequence fields, for which root.foo = [] makes foo to be "really" non-existent, doing same for the primary fields should not make them to be non-existent, as primary fields have a special meaning.

Fields always exist (accessing the field via the property or calling getField will give you the field), we simply chose that for MapTree, empty fields are supposed to be normalized to not being in the map, and iterating over fields in EditableTree skips empty fields.
If you have an array like node (node with primary sequence field) and you put it in an optional field, doing parent.child = undefined or delete parent.child will delete the array node while doing parent.child = [] with replace the array node with a new empty one. parent.child.delete() will empty the sequence on the existing array node.
At least I think that's how the current implementation will behave (assuming your fix is merged), and I think is reasonable.
Note that the schemaAware API currently doesn't support primary field unwrapping, so it will be typed wrong, but EditableTree should do it properly.
Regardless, this is a great fix with a good regression test. Thanks for the contribution!


React-dashboard

I would like to add a react dashboard

program name?

Hi @Kritika30032002 Can I work on this issue under Codepeak-23

@Debshibraj123  Are you working on this?


error when using render react component functionality with latest react version

Recently came across an issue using riteway from the context of a next.js app. Below is a stack-trace showing the specifics.
npm run test

><EMAIL_ADDRESS>test
> riteway -r @babel/register 'source/index.test.js' | tap-nirvana

 renderComponent
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
    ✖  TypeError: Cannot read properties of null (reading 'useRef')
    ----------------------------------------------------------------
        operator: deepEqual
        diff:
        source: at _callee$ (/nextjs-app/source/features/LandingPage/component.test.js:6:13)

passed: 0,  failed: 1  of 1 tests  (558ms)

I wasn't making use of hooks yet, so I could rule that out and move on to checking the versions my project had installed. This led me seeing that riteway had a react-dom version that conflicted with my project.
npm ls react-dom
<EMAIL_ADDRESS>/nextjs-app
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>

below is a sample repo showing riteway behaving correctly when installed alongside next@11 react@17 react-dom@17
https://github.com/tgrecojs/riteway-react-error-repro

Should be fixed in<EMAIL_ADDRESS>- please re-open if you still have trouble.


When run the test_model.py, the checkpoint loader seem to be wrong, the error imformation is below.

File "/data1/program/digital-cousins/tests/test_models.py", line 228, in
main(args)
File "/data1/program/digital-cousins/tests/test_models.py", line 201, in main
test_perspective_fields(args)
File "/data1/program/digital-cousins/tests/test_models.py", line 36, in test_perspective_fields
PerspectiveFields().estimate_camera_intrinsics(input_path=TEST_IMG_PATH)
File "/data1/program/digital-cousins/digital_cousins/models/perspective_fields.py", line 36, in init
self.model = _PerspectiveFields(version)
File "/data1/program/digital-cousins/deps/PerspectiveFields/perspective2d/perspectivefields.py", line 163, in init
self._init_weights()
File "/data1/program/digital-cousins/deps/PerspectiveFields/perspective2d/perspectivefields.py", line 181, in _init_weights
state_dict = torch.hub.load_state_dict_from_url(
File "/home/yrk/anaconda3/envs/acdc/lib/python3.10/site-packages/torch/hub.py", line 871, in load_state_dict_from_url
return torch.load(cached_file, map_location=map_location, weights_only=weights_only)
File "/home/yrk/anaconda3/envs/acdc/lib/python3.10/site-packages/torch/serialization.py", line 1326, in load
with _open_zipfile_reader(opened_file) as opened_zipfile:
File "/home/yrk/anaconda3/envs/acdc/lib/python3.10/site-packages/torch/serialization.py", line 671, in init
super().init(torch._C.PyTorchFileReader(name_or_buffer))
RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory

My Pytorch version is 2.5, and the checkpoint seem to be download completely, so may I ask how can the error can be fixed?

OK, I download the perspective checkpoint manually, the problem seem to be resolved.

Great!


Update API docs

.. for all the new APIs introduced in this project.

/lgtm

@sbose78 can you fix the merge conflicts, so that we can merge pls

sure!

Will get back to this 🤦


Consider making constructor writable

It's a minor issue and it's completely reasonable if you wish to close this, but I run into a TypeError issue when running under 'use strict' - more information in TypeScript since it's technically an issue there and not here: https://github.com/Microsoft/TypeScript/issues/6887. Basically, assignment to this property throw a TypeError under 'use strict' because it takes shadowing into account even though it's a different object (just a part of the prototype).

I will make it writable and configurable as it is the case for Error.prototype.constructor in v8 4.5.

Published as v1.1.1. :)

Thank you! :+1:


Guest user and old search quick fix for DSS server.

DSS blacklight app database table hacks.

There is a new cron that is taking care of this now, created as a resolution to https://github.com/pulibrary/DSS/issues/180. Since that's running perhaps we don't need hard way documentation. I think we should probably close this PR. @kevinreiss what do you think?


i3lock-color: 2.13.c.2 -> 2.13.c.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/PandorasFox/i3lock-color/releases.
meta.description for i3lock-color is: "A simple screen locker like slock, enhanced version with extra configuration options"
meta.homepage for i3lock-color is: "https://github.com/PandorasFox/i3lock-color"
meta.changelog for i3lock-color is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/8slvcklvf8yl6rjzskkdpd9dsmymidnl-i3lock-color-2.13.c.3/bin/i3lock-color passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 2.13.c.3 with grep in /nix/store/8slvcklvf8yl6rjzskkdpd9dsmymidnl-i3lock-color-2.13.c.3

found 2.13.c.3 in filename of file in /nix/store/8slvcklvf8yl6rjzskkdpd9dsmymidnl-i3lock-color-2.13.c.3

directory tree listing: https://gist.github.com/f0a0892f9fe4782faae67ae75e78afac

du listing: https://gist.github.com/ebb64ef85719ea8d572975b72e598ede

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
4 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
betterlockscreen
i3lock-color
i3lock-fancy
multilockscreen

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8slvcklvf8yl6rjzskkdpd9dsmymidnl-i3lock-color-2.13.c.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A i3lock-color https://github.com/r-ryantm/nixpkgs/archive/bb426073898338059813494a1864eb834a12de1a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8slvcklvf8yl6rjzskkdpd9dsmymidnl-i3lock-color-2.13.c.3
ls -la /nix/store/8slvcklvf8yl6rjzskkdpd9dsmymidnl-i3lock-color-2.13.c.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

betterlockscreen
i3lock-color
i3lock-fancy
multilockscreen

Maintainer pings
cc @malyn for testing.

Result of nixpkgs-review pr 124849 at bb426073 run on aarch64-linux 1

4 packages built successfully:

betterlockscreen
i3lock-color
i3lock-fancy
multilockscreen

This has been taken care of in #125417


Feature chalk docs

The long awaited documentation for all the new features. All the newly introduced color fields are documented, new elements Line and Radial, and new modules Platform and Feature. Two guides are added in order to give a clearer direction for developing on Pebble.js in light of supporting Chalk.
Once everything looks good, a CloudPebble update will be requested, and this will be merged. This will address #96, #116, #156 .

You seem to use links inconsistently in your section headers (I marked a bunch, not all) - not certain if intentional or not...

Yes, intentional, the links are only defined if they are necessary. When the header has no strange symbols in it no anchor tag is necessary and it automatically works, but for some odd reason when there are parens or square brackets it's necessary to define your own, or possibly I've not figured out the escape sequence.

Thanks for the quick look over! I updated the docs per the comments. I want to eventually add anchors for all headers, but I'm unsure if that's the right way to use Flatdoc at the moment. When I figure out more, I'll fix them all up.
One of my main concerns is if I ordered the guides correctly. I kept Using Images and Using Fonts first since they're short. The two new guides are much longer, but I put the one that most users would find more immediately useful first, which I assume is Using Color. The one gotcha is that it uses Feature before they even read the Feature Detection guide, so I was unsure about that order. Maybe that makes sense since it just subtly introduces Feature.color and Feature.round in the examples, and they can read Feature Detection if they want a fuller understanding since they are actually simple functions anyway.


proxychains-ng issue

Ubuntu 20.04 LTS
DRipper doesn't want to start before proxychains checks every proxy in the config? For example, whenever I check my IP with curl, I'm getting similar results. This is the first time I'm getting such a thing; other programs I have run work as usual with it.

UPD: Also, only running commands with python3 seems to work for me, for some reason.

DRipper requires python 3.9 or better. Pls update python and check

@SomalianCoolhacker is it still actual? Did you try the latest version with proxy support?


How To Read from extension controllers

I've looked over: https://github.com/thp/psmoveapi/wiki/Extension-Devices
and
https://github.com/thp/psmoveapi/wiki/Sharp-Shooter
But i'm not seeing how to read extension data in this package. I assume I'm just missing something obvious :)

When I tried to read the extension data I had to add access to psmoveapi myself: https://github.com/zelmon64/psmoveapi/commit/90eed15ee30af5e0a455abbad431b58727ad82a2
That was a while ago so it might have been added since. If not you could add my additions to your source code and rebuild it.

That'd be great, do you have that in a branch? If not whats the best way I could get that from you :)

I was a bit dense earlier, just noticed you had a link in your post. Thanks :)

I just made a new branch that's up to date with the master: https://github.com/zelmon64/psmoveapi/tree/EXT_support

Thanks, just cloned it and building now. Ever think of submitting a pr on those changes?

I was just pondering a PR in fact. When I originally made those additions I wasn't that familiar with git and GitHub and it was only very recently that I made my first PR. Let's see how you get on with it to make sure there are no new bugs then I'll make a PR (if you're okay with that).

Sounds great, I'll post my update here once I've got some testing in.
I'm still really new to psmove-unity. All I should have to do is replace the dll's that came bundled with psmove-unity5 with the new ones I'm building from psmoveapi right?

Cheers.
There's probably some code that needs to be added to psmove-unity so that it knows about the additions to to the dlls and how to use them. For example, the corresponding additions I made to use them in FreePIE are here:
https://github.com/zelmon64/FreePie-PSMoveAPI-clone/commit/e7fdccc0e0e79a4f6455df315fd3248813144e17

I finally made some time to try and make a successful build of your branch of psmoveapi, but am having some issues.
using visual studio 2017 community edition in a git bash shell
here is the build process I followed after checking out the project:
mkdir build
cd build
cmake ..
opened ALL_BUILD.vcxproj in visual studio
right clicked the solution and selected build solution
I took the resulting dll from build/Debug/psmoveapi.dll and dropped it into Assets\Plugins\x86_64 over the dll that was already there. The example project ran before replacing the dll.
with the new library it throws this error:
Failed to load library D:/VR/psmove-unity5/Assets/Plugins/x86_64/psmoveapi.dll (ErrorCode: 193)
UnityEngine.Debug:LogError(Object)
PSMoveWorker:LoadLib(String) (at Assets/psmove-unity5/PSMoveManager.cs:1001)
PSMoveWorker:WorkerSetup(PSMoveWorkerSettings) (at Assets/psmove-unity5/PSMoveManager.cs:325)
PSMoveWorker:OnGameStarted(PSMoveWorkerSettings) (at Assets/psmove-unity5/PSMoveManager.cs:280)
PSMoveManager:Awake() (at Assets/psmove-unity5/PSMoveManager.cs:121)
does that mean anything to you?

I kept putting off trying to get this to work months ago because I never could get a successful build. coming back to it again I'm still having the same issues

@wirelessdreamer I'm a little busy right now to dive into this sorry but I want you to know that it's on my todo list. If I don't get back to this in a couple of weeks or so please give me a poke.

Cool, no rush. just updated this thread when you have a little free time and i'll do whatever I can to help on this side.


About worker.js

Hi.
My project is based on Quasar+vue3+vite,I have installed the latest version of @ffmpeg/ffmpeg.But there is a problem, that is, when await ffmpeg.load() is executed, a 504 error about worker.js will appear.This strange url appeared
http://localhost:3000/@fs/D:/Vue/xstudioquasar/node_modules/.q-cache/vite/spa/deps/worker.js?type=module&worker_url_file.
Please help me to achieve the goal of normal operation by modifying the configuration of quasar.config.js
Thanks.

@tomahawkfeng I faced the same issue, solve with adding this config into vite.config.ts
optimizeDeps: {
    exclude: ['@ffmpeg/ffmpeg', '@ffmpeg/util'],
},

follow this project configure


Added STAKING CALCULATOR

-This is a CRYPTO AND CARDANO MARKET PROJECTION TOOL WITH MACROECONOMIC ANALYSIS & STAKING CALCULATOR, powered by Latino Staking Pool.
-This tool allows the user to make future projections of the crypto and Cardano markets. It is important to understand that these are projections only and their accuracy cannot be assumed or guaranteed.
-This is a Cardano-focused tool that allows users to make projections with a macroeconomic approach of the general crypto market for the next 2 decades as well as ADA price projections for the same period as a direct consequence of the percentage of dominance within the market.
-This tool works with updated information from the website www.coinmarketcap.com and from Google Finance financial functions. The current values of the crypto market used in the calculator are updated every hour and a new record is added to  the history dominance table of BTC, ETH and ADA on a daily basis with the information for each day.
-This tool will be maintained and updated as changes are required. For example, when the year 2022 begins, a new line will be added to the historical market performance table and the necessary changes will be made so that the tool continues to work properly.

Thanks for your approval


Either expose DefaultCryptoProvider or update your documentation

Currently during the initialization of the SDK, it is not possible to "just call a configure method" as claimed here, because the DefaultCryptoProvider is not exposed as discussed here.
Either expose DefaultCryptoProvider such that it can be somehow imported even if the package is added through SPM, or alternatively update your documentation such that is clearly explains that developers are expected to implement a crypto provider by themselves to be passed to the Web3Wallet configuration as a parameter.

Thanks for response. Different clients uses different crypto libraries. So we cannot depends on Web3.swift or CryptoSwift in our SDK. But It's a good call to update our integration docs if it's no clear for developers

cc @alexander-lsvk

Just ran into this issue as well while updating. Its not clear what this is for or how I should implement it. I'm not using an Ethereum chain, but the CryptoProvider protocol requires me to implement a func that takes an EthereumSignature as a parameter

@simonmcl here is my implementation
struct WC2CryptoProvider: CryptoProvider {
    public func recoverPubKey(signature: EthereumSignature, message: Data) throws -> Data {
        return SECP256K1.recoverPublicKey(hash: message, signature: signature.serialized)!
    }

    public func keccak256(_ data: Data) -> Data {
        return data.sha3(.keccak256)
    }
}

EthereumSignature is part of the WalletConnect SDK. You don't need to create or implement it.
Depending on the libraries you use, you may not have access to those methods above, but the idea should be clear.

@muratogat thanks for the help. Can you link me to the lib you are using for this:
SECP256K1.recoverPublicKey(hash: message, signature: signature.serialized)!

This is the file in web3swift, which I forked, where the functionality is.
https://github.com/muratogat/web3swift/blob/develop/Sources/web3swift/Convenience/SECP256k1.swift
However, this is in the background importing the base secp256k1 library (import secp256k1 at the top), which is linked as a static library in web3swift (https://github.com/muratogat/web3swift/tree/develop/Sources/secp256k1). Not sure how it would work for you.


0.62.2 (Podspec)

No Podspec found.

i ve used this package  with all new features with react native greater than 0.60 support  react-native-receive-sharing-intent


UseragentStylesheet required?

Small question,
does Atlantafx also work, when not setting the useragent stylesheet? Can it also work by only setting the stylesheet of the Scene?
I thought about adding an AtlantaFX Demo to the JPro Website, but changing the user agent stylesheet, would also affect the other demos.

Yes, it will work when added to the Scene stylesheets observable list. That in fact what Sampler uses to provide hot reload. But leaving platform UA stylesheet unchanged at the same time, means that Modena (or whatever default JavaFX theme for the target platform) styles will also be applied, so your controls will be styled from both AtlantaFX and Modena. As far as I know, it's possible to override platform UA stylesheet for specific Scene, so you probably could try it that way.


Flex Consumption deployment (Node Azure Functions App)

I see that this PR by @patelchandni https://github.com/Azure/functions-action/pull/229 adds support for Flex Consumption plan of Azure Functions. I've tried deploying my Node Azure Function app to Flex Consumption with this yml actio:
    - name: 'Run Azure Functions Action'
      uses<EMAIL_ADDRESS>      id: fa
      with:
        app-name: ${{ env.AZURE_FUNCTIONAPP_NAME }}
        package: ${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}
        publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }}
        sku: flexconsumption
        remote-build: true

but this fails with:
Run<EMAIL_ADDRESS>  with:
    app-name: fitfunctionsapi
    package: .
    publish-profile: ***
    sku: flexconsumption
    remote-build: true
    respect-pom-xml: false
    respect-funcignore: false
    scm-do-build-during-deployment: false
    enable-oryx-build: false
  env:
    AZURE_FUNCTIONAPP_NAME: fitfunctionsapi
    AZURE_FUNCTIONAPP_PACKAGE_PATH: .
Successfully parsed SCM credential from publish-profile format.
Using SCM credential for authentication, GitHub Action will not perform resource validation.
Successfully acquired app settings from function app (with SCM credential)!
Will archive . into /home/runner/work/_temp/temp_web_package_3544899524961187.zip as function app content
Will use Kudu https://<scmsite>/api/publish to deploy since Flex consumption plan is detected.
Will use parameter remote-build: true
Package deployment using One Deploy initiated.
Starting deployment pipeline.
[ValidationStep] starting.
[AppSettingValidation] starting.
[DeploymentStorageValidation] starting.
Validation completed
[SourcePackageUriDownloadStep] starting.
Zip package is present at /tmp/zipdeploy/787287ed-8789-40f4-9f05-f9e150f41c70.zip
[ExtractZipStep] starting.
Cleaning files in /tmp/zipdeploy/extracted
Extracted zip package in /tmp/zipdeploy/extracted
[OryxBuildStep] starting.
Running oryx build command: oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform nodejs --platform-version 20.11.1
sh: 1: tsc: Permission denied
sh: 1: tsc: Permission denied\n/opt/Kudu/Scripts/starter.sh oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform nodejs --platform-version 20.11.1
Failed during oryx build due to sh: 1: tsc: Permission denied\n/opt/Kudu/Scripts/starter.sh oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform nodejs --platform-version 20.11.1
Deployment failed with Error: sh: 1: tsc: Permission denied\n/opt/Kudu/Scripts/starter.sh oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform nodejs --platform-version 20.11.1
Error: Failed to deploy web package to Function App.
Error: Execution Exception (state: PublishContent) (step: Invocation)
Error:   When request Azure resource at PublishContent, oneDeploy : Failed to use /home/runner/work/_temp/temp_web_package_3544899524961187.zip as OneDeploy content
Error:     Package deployment using ZIP Deploy failed. Refer logs for more details.
Error: Deployment Failed!

Am I doing something wrong? I'd appreciate any help and would be happy to provide more logs/test solutions :)

I am experiencing exactly the same error, with exactly the same settings in the action.
@miszu did you find a solution?

I am experiencing exactly the same error, with exactly the same settings in the action. @miszu did you find a solution?

@Yvand unfortunately I did not find a solution and gave up for the time being :(

I checked the deplyment logs on the app service side, and it looks like a dumb warning on a deprecated package causes the failure:
[ // removed irrelevant content
    {
        "log_time": "2024-07-02T13:08:44.7964544Z",
        "id": "335bd5f8-5624-4bf9-823c-5b500503e551",
        "message": "npm WARN deprecated<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)\\nnpm notice \\nnpm notice New minor version of npm available! 10.2.4 -> 10.8.1\\nnpm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.8.1>\\nnpm notice Run `npm install -g<EMAIL_ADDRESS>to update!\\nnpm notice\\n/opt/Kudu/Scripts/starter.sh oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform nodejs --platform-version 20.11.1",
        "type": 2
    },
    {
        "log_time": "2024-07-02T13:08:44.7968642Z",
        "id": "335bd5f8-5624-4bf9-823c-5b500503e551",
        "message": "Failed during oryx build due to npm WARN deprecated<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)\\nnpm notice \\nnpm notice New minor version of npm available! 10.2.4 -> 10.8.1\\nnpm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.8.1>\\nnpm notice Run `npm install -g<EMAIL_ADDRESS>to update!\\nnpm notice\\n/opt/Kudu/Scripts/starter.sh oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform nodejs --platform-version 20.11.1",
        "type": 2
    },
    {
        "log_time": "2024-07-02T13:08:44.8228944Z",
        "id": "335bd5f8-5624-4bf9-823c-5b500503e551",
        "message": "Deployment failed with Error: npm WARN deprecated<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)\\nnpm notice \\nnpm notice New minor version of npm available! 10.2.4 -> 10.8.1\\nnpm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.8.1>\\nnpm notice Run `npm install -g<EMAIL_ADDRESS>to update!\\nnpm notice\\n/opt/Kudu/Scripts/starter.sh oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform nodejs --platform-version 20.11.1",
        "type": 2
    }
]

@miszu and @Yvand - The error occurs during oryx build so, it is not an issue with this GitHub action but some dependency in your package itself is deprecated and so oryx build is failing. Please correct the version is your app.

You are totally right, I can repro the same warning message on my machine if I delete folder node_modules and then run npm install.
Based on the package-lock.json, it is @azure/cosmos 4.0.0 that explicitly depends on debug" 4.1.1, hence causing the warning message.
Thank you for your very useful input!


NetBeans support

Hello Geert and others,
IntelliiJ is all the rage and I use it for Android, but Netbeans is just plain comfy to build code for hours and relax.
How would we go about adding bld there instead of ant or maven? I mean, it is easy for me to run a script but we have big buttons on the IDE to compile things. Maybe possible to request integration with NetBeans too?
Many thanks!

Hi!
Since nobody on the bld team actually uses Netbeans, we have very little incentive to add support for it, nor to research how to do it. I'm sorry, but at this time this is a very low priority for us.
Take care,
Geert

No worries, thank you for the quick reply.


Compiler error when building shaderc in Ubuntu

==== Building shaderc (release64) ====
lex  -t ../../../3rdparty/glsl-optimizer/src/glsl/glcpp/glcpp-lex.l > ../../../3rdparty/glsl-optimizer/src/glsl/glcpp/glcpp-lex.c
glcpp-lex.c
<stdout>: In function ‘yy_get_next_buffer’:
<stdout>:1949:47: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
yacc  ../../../3rdparty/glsl-optimizer/src/glsl/glcpp/glcpp-parse.y
yacc: e - line 162 of "../../../3rdparty/glsl-optimizer/src/glsl/glcpp/glcpp-parse.y", syntax error
%error-verbose
^
<builtin>: recipe for target '../../../3rdparty/glsl-optimizer/src/glsl/glcpp/glcpp-parse.c' failed
make[2]: *** [../../../3rdparty/glsl-optimizer/src/glsl/glcpp/glcpp-parse.c] Error 1
Makefile:168: recipe for target 'shaderc' failed
make[1]: *** [shaderc] Error 2

Disregard this. Failure on my end after more investigation.

git checkout * and try building it again...

No change.

Something is wrong with your local machine setup, this doesn't appear at CI build:
https://travis-ci.org/bkaradzic/bgfx/jobs/266618887
Build configuration for CI is here:
https://github.com/bkaradzic/bgfx/blob/master/.travis.yml

I had the same issue, try installing bison instead of byacc.


Convert "chunky" fields like datetime into flat ones.

Requires #105 to be implemented first if it is going ahead. Otherwise these will become private fields with properties.
Properties for datetimes can be converted to be stored as pure integers, since we always assume UTC. This should reduce memory usage for each guild/member/etc that exists.
The accessor can then build a value on the fly instead.

We should double check any internal implementation of datetime in CPytthon's source prior to doing this


latest version crashing on second start up

Describe the bug
im using the mod in a modpack for the item esp functions, but I'm noticing that it boots up fine the first time, but the second time, it consistently crashes every time, I have to go in and delete the config files it generates to get it to start up properly again, I tried downgrading, and it starts, but the functions say their activated, except they arent, the latest one is the only one where the features work for me.
To Reproduce
Steps to reproduce the behavior:

Install the mod
run the game
exit
try to start the game a second time

Expected behavior
start properly each time the game is started
Version Info (please complete the following information):

OS: Windows
Mod Version: v1.4.8rc2

Additional context
the crash logs if you need them: https://pastebin.com/p5zsRxhb

Thanks for the heads up! I'll investigate this as soon as I am able to.
On Wed, Nov 6, 2024, 2:24 PM starstriker @.***> wrote:

Assigned #81 https://github.com/gavinsmod/gavinsextensiblemod/issues/81
to @GT3CH1 https://github.com/GT3CH1.
—
Reply to this email directly, view it on GitHub
https://github.com/gavinsmod/gavinsextensiblemod/issues/81#event-15159515445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENJREOU5JQHTYHKJDJ2IS3Z7KCJLAVCNFSM6AAAAABRJX7CLOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGE2TSNJRGU2DINI
.
You are receiving this because you were assigned.Message ID:
@.***
com>

👍

Hey,
I am unfortunately unable to reproduce the issue using v1.4.8-rc2. v1.4.7 and below had a bug where the ESP engine wouldn't render in some cases.
Would you be able to do the following?

Please attach a list of the mods loaded in your client. Sometimes some mods play well with gavinsmod, other's don't.
Delete any other versions of gavinsmod you may have in your mods folder.
Download a fresh copy of v1.4.8rc2 here: https://github.com/gavinsmod/gavinsextensiblemod/releases/tag/v1.4.8-rc2

Please not that v1.4.8-rc2 is currently built for Minecraft 1.21.1 - I am working on updating it to 1.21.3 here shortly.

oh, sure, heres the list of mods and versions
Southgate SMP Modpack 1.21.csv
and, the exact mod files folder if you want it
there arent any other versions of gavinsmod installed
and, I'm using mc version 1.21 not 1.21.1 or above, so I thought that might be the reason, but it doesn't explain why the mod works when there's no config files

just downloaded a fresh copy, same problem, works fine on the first run(the one without config files) but then on the second run(with config files) it crashes

Just to clarify - are you running Minecraft 1.21 or 1.21**.1** where this issue is occurring?

i am running minecraft 1.21, but like i said, the mod runs fine the first time with no problems, without its config files, so its not a Minecraft version compatibility issue

I am unable to reproduce this issue using 1.4.8-rc2 with Minecraft 1.21.
Would you be able to attach the settings.json generated after the first launch and when the crash occurs (eg, the settings file before and after)? It's under %APPDATA%/.minecraft/mods/gavinsmod. I am suspecting that one of those mods that you sent me earlier are doing something funny with the X-Ray feature which is causing the crash.

im so sorry i didn't notice you replied until now
here's the file after the first run
settings.json
and here it is after the crash
settings.json
crash logs again just incase
crash-2024-11-09_22.07.47-client.txt

Thanks for those files. I'll be trying to sort out this out, it seems like its going to be a bit of a rabbit hole of a bug to sort out, since I am unable to reproduce this issue locally. Thanks for those files. I'll keep you updated as I find more out.

👍

I actually think I figured out what was going on - I've made a new release under the releases page. Please grab a new copy of the mod here: https://github.com/gavinsmod/gavinsextensiblemod/releases/tag/v1.4.8-rc3 - Make sure to NOT use the file ending in -sources.jar

ok, ill try it

nope, didnt fix it, ive replaced the mod but its having the same problem, I still have to delete the config files for it boot up a second time, I tried everything short of reinstalling the Minecraft instance even deleting everything in the configs folder that should have no relation
crash-2024-11-10_18.42.08-client.txt
full logs if you want
https://mclo.gs/OoYAbHC

Thanks for the crash report - this looks like it's an issue with prism
launcher compatibility. I'll try and take a look into it.
On Sun, Nov 10, 2024, 5:14 PM starstriker @.***> wrote:

nope, didnt fix it, ive replaced the mod but its having the same problem,
I still have to delete the config files for it boot up a second time, I
tried everything short of reinstalling the Minecraft instance even deleting
everything in the configs folder that should have no relation
crash-2024-11-10_18.42.08-client.txt
https://github.com/user-attachments/files/17693642/crash-2024-11-10_18.42.08-client.txt
full logs if you want
https://mclo.gs/OoYAbHC
—
Reply to this email directly, view it on GitHub
https://github.com/gavinsmod/gavinsextensiblemod/issues/81#issuecomment-2467005828,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENJREMTDNWSQHVYG5LAZQLZ77ZH3AVCNFSM6AAAAABRJX7CLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRXGAYDKOBSHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

which launcher do you use? because i just copied the mods folder over to ATlauncher and had the same issue

I usually just use the default Minecraft launcher. I installed ATlauncher today, and I created an instance with the following jar files installed in the mods folder for the instance:

fabric-api-0.102.0+1.21.jar
fabric-language-kotlin-1.12.3+kotlin.2.0.21.jar
gavinsmod-1.4.8-rc3+1.21.1-dev.jar

Here's what I did:

Loaded into the game
Made changes to the config file
Stopped the game
Started the game
Loaded back into the game

And the client did not crash. I also copy+pasted the configs you gave me, and tried the downgrading to v1.4.8-rc2, and the client still did not crash.
I then googled the error message provided (Caused by: com.google.gson.JsonIOException: Failed making field 'java.util.Optional#value' accessible; either increase its visibility or write a custom TypeAdapter for its declaring type.) and this actually might be caused by a dependency of my mod needing to be updated - I've since made the change (as seen in commit 1bd0d93e) and have built this on my CI server. I have attached the new build titled gavinsmod-1.4.8-rc4+1.21.1-dev.jar on the releases page here: https://github.com/gavinsmod/gavinsextensiblemod/releases/tag/v1.4.8-rc4
Would you be able to try that version and let me know if it crashes again? If it does, I may have to downgrade the dependency rather than update it. We shall see.
Thanks for helping out on this, I do appreciate it!

nope, still having the same issue, honestly, im at a loss for whats wrong, but I did decide to record it this time
https://github.com/user-attachments/assets/0dcd5e19-b384-48be-9a9f-aa8242f12035
and here are the crash logs for this attempt, ill try with prism launcher again but I don't think it'll work
crash-2024-11-11_21.29.42-client.txt

I'm at a loss too - I'll have to dig into it a bit more. I'm suspecting
that one of the mods in the list you gave me is causing some sort of weird
compatibility problem. I'll update you as I find out more.
On Mon, Nov 11, 2024, 9:08 PM starstriker @.***> wrote:

nope, still having the same issue, honestly, im at a loss for whats wrong,
but I did decide to record it this time
https://github.com/user-attachments/assets/0dcd5e19-b384-48be-9a9f-aa8242f12035
and here are the crash logs for this attempt, ill try with prism launcher
again but I don't think it'll work
crash-2024-11-11_21.29.42-client.txt
https://github.com/user-attachments/files/17710978/crash-2024-11-11_21.29.42-client.txt
—
Reply to this email directly, view it on GitHub
https://github.com/gavinsmod/gavinsextensiblemod/issues/81#issuecomment-2469550185,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENJRELMN27C4ITTOP7KJUT2AF5KJAVCNFSM6AAAAABRJX7CLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRZGU2TAMJYGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

I have been able to reproduce the issue by downloading and activating one of the following mods:

Gamma Utils
worldweaver
YungsApi
YetAnotherConfigLib
YouDied
Zoomify
libIPN
owo

Update: This appears to be a compatibility issue with owo-lib.

I believe I have fixed this issue, since I am no longer crashing with owo-lib installed running along side my client.
Please check here for the rc5 release (again - make sure to not download the -sources file!) https://github.com/gavinsmod/gavinsextensiblemod/releases/tag/v1.4.8-rc5

Hey I just wanted to make sure that you saw my previous message.

I believe I have fixed this issue, since I am no longer crashing with owo-lib installed running along side my client.
Please check here for the rc5 release (again - make sure to not download the -sources file!) https://github.com/gavinsmod/gavinsextensiblemod/releases/tag/v1.4.8-rc5

Oh, shoot, sorry, had exams going on so I wasn't paying attention, I'll check it out later today

No worries. I hope they went well.
On Sat, Nov 16, 2024, 9:38 AM starstriker @.***> wrote:

Oh, shoot, sorry, had exams going on so I wasn't paying attention, I'll
check it out later today
—
Reply to this email directly, view it on GitHub
https://github.com/gavinsmod/gavinsextensiblemod/issues/81#issuecomment-2480646807,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENJRELYC27YG6NI25R4M5L2A5YHDAVCNFSM6AAAAABRJX7CLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBQGY2DMOBQG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

it works!! thank you!

Awesome, thanks! Please feel free to open another issue if you find a bug/have a cool idea for the mod.


Node v18 throwing credential implementation issue but not with node v16

Describe your environment

Operating System version: Docker using FROM node:18.16
Firebase SDK version: 11.9
Firebase Product: auth
Node.js version: 18.16
NPM version: 9.5.1

Steps to reproduce:
When I upgraded my docker node from 16.19 to 18.16, I get this error:
credential implementation provided to initializeapp() via the "credential" property failed to fetch a valid google oauth2 access token.

However, if I downgrade it back to 16.19, the notifications get pushed out.
From the package.json it says that it can support node 14 and higher but its failing on v18 for me.
Relevant Code:
I'm using very basic:
initializeApp({
    credential: applicationDefault(),
})

Operating System Version: node:18.15
Firebase SDK version: 11.9
Firebase Product: auth
Node.js version: 18.15
NPM version: 9.6.2
I have the same issue in local development. I've tried all the initialization approaches recommended in Firebase docs.
Error Message:
Credential implementation provided to initializeApp() via the \"credential\" property failed to fetch a valid Google OAuth2 access token with the following error: \"Error fetching access token: Error while making request: connect ETIMEDOUT 2404:6800:4009:820::200d:443
Code:
`
var credentials = require("path/to/serviceAccountKey.json");
initializeApp({
credential: cert(credentials),
});
`

Same issue here

Hey folks, I am unable to reproduce this on v18.15.0 and<EMAIL_ADDRESS>Do you only experience this issue on linux environments?

Hey folks, I am unable to reproduce this on v18.15.0 and<EMAIL_ADDRESS>Do you only experience this issue on linux environments?

I haven't tested it on any other environment. I'm using mine on a docker container with node:18.16 image.

Thanks @rossjackson-ma. Could you share a minimal repro or a minimal version of your docker file?

Here is a repo you can clone.  I added some README


fix: exception when form autocompletes and key is undefined

Signed-off-by: Jeremy Wickersheimer<EMAIL_ADDRESS>What is it?

[ ] Feature / enhancement
[X] Bug
[ ] Docs / tests

Description
When a form field is filled from the browser autocomplete this inserted Qwik code will (somtimes) cause an exception in the console as key is undefined.
Use cases and why
Adding this simple guard prevents the exception.
Checklist:

[X] My code follows the developer guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Is there an issue preventing merge or was the CI just being capricious?


Need a voluntarily documenter for the simplelogin docs?

@nguyenkims I wanted to know if you guys are looking for a voluntarily documenter whom is willing to work on simplelogin's docs?

@therealmrmuffin yes, as non-native English speakers we make probably a lot of mistakes so if you spot any error, please create a pull request to fix it.

@nguyenkims Always happy to help with typos (and vise versa 😉). But do note that i was offering to help make and maintain the docs (and not only fix typos).

@therealmrmuffin do you mean having the github permission to merge/review PR? Currently only our team members have this permission on our github actually.

@therealmrmuffin do you mean having the github permission to merge/review PR? Currently only our team members have this permission on our github actually.

@nguyenkims not persay, just someone who is a voluntarily documenter part of the SimpleLogin community who wants to help make very, very dilated docs for SimpleLogin (Kind of like how Wikipedia has comunity editors who edit wikipedia on a voluntarily bases).

Or like how, cpanel in has a documentation team that gets assistants from the community.

I see, currently the best way for us to receive contributions is via pull request. It's similar to the contributing method on wikipedia but requires markdown knowledge. It can be nice though as people can edit directly on github and create a merge request after that.

I see, currently the best way for us to receive contributions is via pull request. It's similar to the contributing method on wikipedia but requires markdown knowledge. It can be nice though as people can edit directly on github and create a merge request after that.

True, but i am mostly talking about making articles, doc instructions, guides, etc (whatever you want to call it) that don't exists yet. How would you coordinate that with the community?

I would love to go ham and make like 20 domain name registrar guides for you, if you wish. But the community just needs to know what docs you want help with and stuff.

@therealmrmuffin I've updated to readme to include a section on how to add new files :)

@nguyenkims love it, you bet i'll be busy working on then docs for SL now. :D


Set right button icon and event

If we want to use something other than an actions menu there doesn't seem to be a way to replace the right button on the nav bar.

Fixed https://github.com/lazaronixon/react-native-turbolinks/releases/tag/v1.6.4


Party game - Encoding not displaying correctly?

Storytime: FeelsBirthdayMan and his brother  PogChamp are going to ReykjavÃÂÃÂÃÂÃÂk by bus.
ReykjavÃÂÃÂÃÂÃÂk is supposed to be Reykjavík (That i is not normal ASCII 'i')

Should be fixed in bb435b5b46113211b81dc53892b12f6ac8a7ef3d
Once we have fixed the corrupted json files, we won't see them anymore


IntelliSense will crash in large projects that use a lot of node modules

From @RonanQuigley on April 6, 2018 14:12

VSCode Version: 1.22.1
OS Version: Windows 10

Steps to Reproduce:

clone the following repo and navigate to the test>back-end>routes.test.js file:
git clone https://github.com/RonanQuigley/vscode-intellisense-bug .
run yarn to install the node_modules folder. You do not need to execute any script to see this problem.
Adjust the import path as demonstrated in the gif below. Notice that aside from being slow (around 1s to update a path, intellisense eventually hangs on 'Loading...' and won't work without an update.

I've tried to replicate this with a barebones project i.e. just two files but it never happens. I've also managed to narrow it down to the node_modules folder. Intellisense, when scanning that folder, will crash if the project has a lot of modules. Just before the crash I've consistently have had this sort of cpu spike:

If you delete the node modules folder, the issue is gone. If you reduce the number of modules, whilst intellisense is a bit slower, the issue is also gone. If you use require instead of import, the issue is also there. I tried to see if it was a specific module causing it, but my tests have shown that it's not the case. It's just the sheer number of modules being used.
Is there intellisense logging that I can provide that would help? The only current workaround is to restart vscode, which if like me, you encounter this issue incessantly is a complete pain in the butt to deal with.
There's loads of other files in this project; I've just left them in in case there's something contributing to the issue that perhaps I'm missing. So whilst I have tried to minimise the project to the least amount of files, it only happens in larger setups unfortunately.

Does this issue occur when all extensions are disabled?: Yes
Copied from original issue: Microsoft/vscode#47327

Similar repo steps (path completions) to https://github.com/Microsoft/vscode/issues/46025 and https://github.com/Microsoft/vscode/issues/45993

@RonanQuigley can you please try out the next drop that gets release tonight to see if it helps.

that is typescript@next published tomorrow<EMAIL_ADDRESS>to be exact.

@sheetalkamat Perfect! That's it working now and the path finding is snappier too 👍 Thanks to all of you for the quick fix.


Typo in German translation

Gitea version (or commit ref): 1.5.0+rc1-214-g552d8d3a4
Git version: Not relevant
Operating system: Not relevant
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
"Selbstegistrierung deaktivieren" --> is missing letter 'r'
Screenshots

Translations are managed using crowdin. Please suggest changes in https://crowdin.com/translate/gitea/68/enus-de


GitHub Actions

Workflow file is taken from https://github.com/ARK-Builders/ark-rate-desktop
We must build the project and publish the sample's AppImage on each commit.
Later, we should also separate different components. Each would have its own sample to conduct QA.

@kirillt lgtm, we can merge it


createSSRApp not found in 'vue'eslintimport/named

I created a new project and I can't find all of vue's built-in methods.

use pnpm

I'm not sure how pnpm organizes things, but I also don't see createSSRApp in<EMAIL_ADDRESS>


Fix for non-updating text

This fixes an issue where the text Binding wouldn't update. CodeEditTextView would receive updates to input just fine, but the client wouldn't get any updates about the changes in the string.

Please fix the listing error on line 172


Databricks SQL Support

Is your feature request related to a problem? Please describe.
I would love for dbt-sugar to support Databricks SQL.  We use Databricks for our warehousing, and it prevents us from using dbt-sugar.
Describe the solution you'd like
Either a way for DBT sugar to support Databricks, or a flag to turn off database checking?
Thank you!

I'd welcome a contrib to use databricks but I will not be able to do it myself.
I'll think about not checking the db but it might make the tool a little less useful for you. Although not entirely I guess.


Setting output.dir and dita.temp.dir in a DITA-OT project file

Expected Behavior
As a user I'm expecting to set all params in the DITA-OT project file. As I have learned now (thanks @raducoravu and @chrispy-snps) the <output> element and the output.dir parameter are two different things and they are relative to each other. But I cannot set output.dir in the project file.
Actual Behavior
I would like to do something like this:
<?xml version="1.0" encoding="UTF-8"?>
<project>

  <deliverable name="Output Dir" id="output-dir">
    <context name="Output Dir" id="output-dir-context">
      <input href="output-dir.ditamap"/>
    </context>
    <output href="./output-dir"/>
    <publication transtype="pdf2">
      <param name="clean.temp" value="no"/>
      <param name="dita.temp.dir" value="./temp"/>
      <param name="output.dir" value="./new-out"/>
    </publication>
  </deliverable>

</project>

But it fails with something like this:
Developers-MacBook-Pro:bin raducoravu$ sh dita -p /Users/raducoravu/Desktop/output-dir/output-dir.xml
Error: [DOTJ085E][ERROR] The 'output.dir' parameter cannot be set with 'param' in project files. Use 'output' instead.

Possible Solution
That's the question.
Steps to Reproduce
Just publish the DITA-OT file.
output-dir.zip
Copy of the error message, log file or stack trace
Environment

DITA-OT version: 3.6.0
Operating system and version: Windows 10
How did you run DITA-OT? oXygen
Transformation type: pdf2

The console reports two errors in this case and breaks:
 Error: [DOTJ085E][ERROR] The 'output.dir' parameter cannot be set with 'param' in project files. Use 'output' instead.
Error: dita.temp.dir property must be an absolute path: ./temp

I think the second one proves to be fatal.

@xephon2 - can you share more about your desired use case? For example,

For setting the temporary directory, is it because the default location is not desirable?
For setting the output directory, are you looking to define an absolute path or some kind of global relative path?

@chrispy-snps
The use case is, that, when I do plugin development, I want the temporary files in the directory where I have my test files, because I want to open them easily via the oxygen project view.
For the output directory, I basically want to have a better control where the output files end up. I have a multi-project repository with thousands of topics and different nesting levels. But I want that all my deliverables are stored in the directory myrepostory/out. Unfortunately, thw two output directory parameters are conflicting. The directory you have chosen with the oxygen DITA-OT project file editor in text view with autocompletion might not be the directory that will be used, because the default transformation scenario interferes with the additional.args out setting. Then technical writers ask me where they can find there files and I have to reply that they have used the default oxygen transformation and this will shift the files to another directory level


Fix code example

Fixes #24926
Thanks @jerrevds! :rocket: ... I'll ping Tanay to look, too, but see if the additional update here makes sense to you. There's a duplication of guidance for the Pages/_Host.cshtml page that I'm striking in the process.
Tanay ... This is Javier's original code for the scenario and then updated from https://github.com/dotnet/aspnetcore/issues/37713#issuecomment-961838175 and his following answer to my question there.
However, this looks correct. In the Prerender and Integrate topic, we guide adding the Component TH to Pages/_Host.cshtml ...
<component type="typeof(App)" render-mode="WebAssemblyPrerendered" />

... in the NON-auth case. Then, the WASM security doc should just pick up from there.
Cross-reference: Step 4 of https://docs.microsoft.com/en-us/aspnet/core/blazor/components/prerendering-and-integration?view=aspnetcore-6.0&pivots=webassembly#prerendering-configuration
In the WASM security doc, I'm dropping the extra bit of guidance for the _Host.cshtml file because ... as @jerrevds points out ... the dev should've already taken care of it by following the Prerender and Integrate topic guidance (Step 4). What we'll be left with in the WASM security doc is ...

Factor services to a common location.
AVOID prerendering for relative paths that start with /authentication with the code provided (i.e., @jerrevds update to Javier's code).

Hi @guardrex as you asked to verify on my side too, the explanation and proposed adaptation seems valid

Thanks @jerrevds ... now, we'll just get Tanay's feedback/updates/approval and then this can go in. Thanks again for your help. These are some tricky bits 😈 to explain 😵😄.

@TanayParikh ... I'm going to proceed with this given that it's a doc 🐛. I'd like to get it live asap.
Let me know if you have a concern about the PR ... a further patch for the content ............. or a 💀 death threat 💀😆.


Padding breaks mouse selection

Adding padding to a profile (e.g. "padding": "20, 20, 20, 20") breaks selecting text with your mouse. The selection is offset with the padding.

edit: Windows build 10.0.18890.1000, just in case that's relevant

I noticed this in 18362.86 as well. It's not as bad as in your case as I have set the padding to be 10, 10, 10, 10 only.

I believe @carlos-zamora is working on this :)

Yeah. It's off by the amount of padding. I have it in code review in our other system (still transitioning over to GitHub) so this'll be fixed soon. 😊


Temporarily disable a SILVerifier check for valid accessed storage.

This won't actually affect compilation. The verifier check makes sure
that all formatlly accessed storage has a recognized source to guard
against the possiblity for exclusivity optimization to be overly
optimistic. The check currently fails on address-type block arguments,
but the cases where it fails don't actually need to be recognized for
exclusivity optimization to work properly (don't worry, we won't
actually drop any checks in these cases). I plan to completely
disallow address block args instead before reenabling the access
verification.
There are still some loop passes that clone regions without properly
sinking projections. It should be straightforward to adapt
SinkAddressProjections to handle loops.
Fixes rdar://57291811 and rdar://56914099
SIL verification failed: Unknown formal access pattern: storage

@swift-ci smoke test


First pass at adding cdi-full to interceptors tests

Part 1 of #262
Moves @ Interceptors tests under org.jboss.cdi.tck.tests.full.interceptors.* package
Add cdi-full group to tests
Adds bean defining annotations needed for these tests to pass weld master
[INFO] Tests run: 45, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.319 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 45, Failures: 0, Errors: 0, Skipped: 0
Signed-off-by: Scott M Stark<EMAIL_ADDRESS>

Ok, I'll redo the PR to keep org.jboss.cdi.tck.interceptors.tests and replace the use of @Interceptors in most locations. I guess the only @Interceptors test to keep for full would be those explicitly adding multiple interceptors?

@interceptors test to keep for full would be those explicitly adding multiple interceptors?

I think I added comments to all the test classes that need changing. Some of those classes where you only marked certain methods as Full were IMO correct.

I'm going through the tests, and I'm not sure what is being tested in org.jboss.cdi.tck.tests.interceptors.definition.lifecycle.order.LifecycleInterceptorOrderTest.
It looks like it is testing that "If an interceptor is enabled for the application and for the bean archive, then the enablement from the bean archive is ignored by the container.", so that the ordering of the AnotherInterceptor and TransactionalInterceptor should be

AnotherInterceptor because it has an @Interceptors binding which is higher than @InterceptorBinding
TransactionalInterceptor because it has an @InterceptorBinding

It seems like this test should be updated to use @InterceptorBinding and @Priority and kept in Lite. The fact that the beans.xml interceptors is used will be ignored in lite, and since it is also ignored in full, the test should work in both?

@starksm64 from what I can tell, the test tries to assert these two statements - https://github.com/eclipse-ee4j/cdi-tck/blob/master/web/src/main/resources/tck-audit-cdi.xml#L5060-L5072
None of the two is related to Lite as we:

Do not support interceptors declared on target class
Do not support usage of @Interceptors

It looks like it is testing that "If an interceptor is enabled for the application and for the bean archive, then the enablement from the bean archive is ignored by the container."

I am not seeing that anywhere in LifecycleInterceptorOrderTest. One interceptor is using @Interceptors which doesn't require enablement and the other is via bindings and enabled in beans.xml file.
So unless I am missing something, I would say this belong to Full group.

Superseded by #285. All changes suggested on this issue should be in that PR.


<!--

Affected page

To reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

System

Device: [e.g. iPhone6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.4]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]

Additional context

Originally posted by @Lindakay82 in https://github.com/freeCodeCamp/freeCodeCamp/issues/44521

Hi, I'm closing this because it looks like it has been opened by accident.


How to properly setup a one to one relationship in case of circular dependency?

This is a question rather than an issue. I have opened a question in SO and can't get an answer for it.
My idea is to upload all files in one table and store their Ids in the related tables. at the same time, I want to maintain a referential integrity between those related records for example,
    public class FileUpload : BaseEntity {
            [Key, DatabaseGenerated (DatabaseGeneratedOption.None)]
            public long RecordId { get; set; }
            public string UserId { get; set; }
            public ApplicationUser User { get; set; }
            public long? RecordKey { get; set; }
            public long? Length { get; set; }
            public string PhysicalPath { get; set; }
            public string Name { get; set; }
            public OffsetDateTime? LastModified { get; set; }
            public LocalDateTime? ValidUntil { get; set; }
            public FileCategory FileCategory { get; set; }

        }

UserAvatarId is just a property that is related to the File Upload Table RecordId. (one to one relationship)
The related entity is,
        public class ApplicationUser : IdentityUser {
            [Required, StringLength (50)]
            [Display (Name = "First Name")]
            public string FirstName { get; set; }
            public long? UserAvatarId { get; set; }
            public virtual ICollection<FileUpload> UploadedFiles { get; set; }
    }

my fluent API model builder is
    builder.Entity<ApplicationUser> ()
             .HasMany (c => c.UploadedFiles)
             .WithOne (c => c.User)
             .OnDelete (DeleteBehavior.Cascade);

    builder.Entity<FileUpload> ()
            .HasOne (c => c.User)
            .WithOne ()
            .OnDelete (DeleteBehavior.SetNull);

The problem here now is that,
If I delete a user from ApplicationUser, all related records in  FileUpload are not deleted, UserId is set to null.
if I try to delete a record from FileUpload that has a related record in ApplicationUser (PK-Fk) on UserAvatarId-RecordId, I get an error with regards to FK constraints.
Desired behavior:
What I am looking for is,
if I am deleting a record from ApplicationUser should cascade delete all related ones in FileUpload.
if I am deleting a record from FileUpload that is in use in ApplicationUser, UserAvatarId in ApplicationUser should be set to null.
what is the correct config for the fluent API here in this case?
Further technical details
EF Core version: (2.1.3)
Database Provider: (Microsoft.EntityFrameworkCore.SqlServer)
Operating macOS:
IDE: (Visual Studio 2018 1.25)

@embryologist at first glance the configuration code you posted seems insufficient to configure the 1:1 relationship between FileUpload and ApplicationUser. E.g. it is missing mentioning that UserAvatarId is the FK pointing to FileUpload.RecordId.
I haven't tested your model, but I think in absence of this information, and since the name of the FK does not match any convention, I think it is possible that EF Core is creating a separate non-nullable FK property in shadow state, which would make the relationship required. Can you try adding the missing information in the configuration of the relationships?

@divega , thank you for your response.
You are right, so I modified the fluent API to:
 builder.Entity<FileUpload>()
             .HasOne(c => c.User)
             .WithOne(c => c.UserAvatar)
             .HasForeignKey<ApplicationUser>(c => c.UserAvatarId)
             .OnDelete(DeleteBehavior.SetNull);

now with this config. I am able to achieve the one of the behaviours that I am looking for,

if I am deleting a record from FileUpload that is in use in ApplicationUser, UserAvatarId in ApplicationUser should be set to null.

now if I am trying to add the one to many relationship config. between ApplicationUser and FileUpload, to achieve the second behavior,

if I am deleting a record from ApplicationUser should cascade delete all related ones in FileUpload.

I get multiple cascade path exception from SQL server,

Introducing FOREIGN KEY constraint 'FK_FileUploads_AspNetUsers_UserId' on table 'FileUploads' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.

I am config. the fluent API as follows,
builder.Entity<ApplicationUser>()
             .HasMany(c => c.UploadedFiles)
             .WithOne()
             .HasForeignKey(c => c.UserId)
             .OnDelete(DeleteBehavior.Cascade);

currently, I am being forced to set the column value to null instead, (this is NOT what I am looking for)
builder.Entity<ApplicationUser>()
            .HasMany(c => c.UploadedFiles)
            .WithOne()
            .HasForeignKey(c => c.UserId)
            .OnDelete(DeleteBehavior.SetNull);

I am attaching an Image to show the table build,

is there a workaround it?
Thank you again.

@embryologist Is it your intention to create two relationships? That is, a one-to-one and a one-to-many? If so, then these two relationships must use different navigation properties and foreign keys. That is, multiple relationships cannot share the same navigations.

@ajcvickers , yes my intention is to create two relationships,
The one - one relationship is between (UserAvatarId <-> RecordId)
The one - many relationship is between (UserId <-> UserId). so by this design, I have more than one FK. How can I change the navigation prop though?

@embryologist
protected override void OnModelCreating(ModelBuilder builder)
{
    builder
        .Entity<ApplicationUser>()
        .HasMany(c => c.UploadedFiles)
        .WithOne()
        .HasForeignKey(e => e.UserId)
        .OnDelete(DeleteBehavior.Cascade);

    builder
        .Entity<FileUpload>()
        .HasOne(c => c.User)
        .WithOne()
        .HasForeignKey<ApplicationUser>(e => e.UserAvatarId);
}

Notes:

Uploaded files can be accessed through user.UploadedFiles, but there is no inverse navigation property.
The user avatar can be accessed through file.User, but there is no inverse navigation property.
You can add inverse navigations if you want, but they will need to be different properties on the entities--i.e. User cannot also be used as the inverse for UploadedFiles.
Cascade deletes should work as you specified.
SQL Server is pretty limited in what it can handle with regard to delete behaviors so I removed the SetNull specification. This means that as long as the ApplicationUser entity is loaded into the context, then when the related FileUpload is deleted the UserAvatarId will be set to null. However, if it is not loaded, then SQL Server won't do it for you--it will instead generate a referential integrity violation. This is a lmiitation in SQL Server.

Thank you so much for the elaborate response.


[full-ci] bump reva to 02af5a266

pull in https://github.com/cs3org/reva/pull/4835 to test a fix for https://github.com/owncloud/ocis/issues/9933

ok, this fails:
  @issue-4421

  Scenario Outline: sharee PROPFIND same name shares shared by multiple users using new dav path                     # /dronesrc/tests/acceptance/features/apiSharingNg1/propfindShares.feature:53
    Given using <dav-path-version> DAV path                                                                          #FeatureContext::usingOldOrNewDavPath()
    And user "Alice" has uploaded file with content "to share" to "textfile.txt"                                     #FeatureContext::userHasUploadedAFileWithContentTo()
    And user "Alice" has created folder "folderToShare"                                                              #FeatureContext::userHasCreatedFolder()
    And user "Carol" has uploaded file with content "to share" to "textfile.txt"                                     #FeatureContext::userHasUploadedAFileWithContentTo()
    And user "Carol" has created folder "folderToShare"                                                              #FeatureContext::userHasCreatedFolder()
    And user "Alice" has sent the following resource share invitation:                                               #SharingNgContext::userHasSentTheFollowingResourceShareInvitation()
    | resource        | <resource> |
    | space           | Personal   |
    | sharee          | Brian      |
    | shareType       | user       |
    | permissionsRole | Viewer     |
    And user "Brian" has a share "<resource>" synced                                                                 #SharingNgContext::userHasShareSynced()
    And user "Carol" has sent the following resource share invitation:                                               #SharingNgContext::userHasSentTheFollowingResourceShareInvitation()
    | resource        | <resource> |
    | space           | Personal   |
    | sharee          | Brian      |
    | shareType       | user       |
    | permissionsRole | Viewer     |
    And user "Brian" has a share "<resource-2>" synced                                                               #SharingNgContext::userHasShareSynced()
    When user "Brian" sends PROPFIND request from the space "Shares" to the resource "Shares" using the WebDAV API   #SpacesContext::userSendsPropfindRequestFromTheSpaceToTheResourceWithDepthUsingTheWebdavApi()
    Then the HTTP status code should be "207"                                                                        #FeatureContext::thenTheHTTPStatusCodeShouldBe()
    And the "PROPFIND" response to user "Brian" should contain a space "Shares" with these key and value pairs:      #SpacesContext::theResponseShouldContainMountPoint()
    | key       | value         |
    | oc:fileid | UUIDof:Shares |
    | oc:name   | Shares        |
    And the "PROPFIND" response to user "Brian" should contain a mountpoint "Shares" with these key and value pairs: #SpacesContext::theResponseShouldContainMountPoint()
    | key            | value             |
    | oc:fileid      | UUIDof:<resource> |
    | oc:name        | <resource>        |
    | oc:permissions | S                 |
    And the "PROPFIND" response to user "Brian" should contain a mountpoint "Shares" with these key and value pairs: #SpacesContext::theResponseShouldContainMountPoint()
    | key            | value               |
    | oc:fileid      | UUIDof:<resource-2> |
    | oc:name        | <resource-2>        |
    | oc:permissions | S                   |
  Examples:
    | dav-path-version | resource      | resource-2        |
    | old              | textfile.txt  | textfile (1).txt  |
        Failed step: And the "PROPFIND" response to user "Brian" should contain a mountpoint "Shares" with these key and valuepairs:
      wrong fileId in the response
        Failed asserting that an array contains 'a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668!a4fd2951-56cf-4bd4-88b7-d05f299384d0:9ddc3a0-055d-46f3-b47a-222cf50f01d0:526c46a9-7ded-4e54-ae6d-b57433a9a419'.
    | old              | folderToShare | folderToShare (1) |
        Failed step: And the "PROPFIND" response to user "Brian" should contain a mountpoint "Shares" with these key and valuepairs:
      wrong fileId in the response
        Failed asserting that an array contains 'a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668!a4fd2951-56cf-4bd4-88b7-d05f299384d0:38e0f3d-1bbf-4964-92e0-ea5d4cdc8fd5:b13cdcfa-5eb8-44bb-ba08-ac763e52f3ae'.
    | new              | textfile.txt  | textfile (1).txt  |
        Failed step: And the "PROPFIND" response to user "Brian" should contain a mountpoint "Shares" with these key and valuepairs:
      wrong fileId in the response
        Failed asserting that an array contains 'a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668!a4fd2951-56cf-4bd4-88b7-d05f299384d0:40676d9-9256-4b21-9c4d-aceeede012e4:e0f82b48-8997-4e0d-b18c-3ef16ca57983'.
    | new              | folderToShare | folderToShare (1) |
        Failed step: And the "PROPFIND" response to user "Brian" should contain a mountpoint "Shares" with these key and valuepairs:
      wrong fileId in the response
        Failed asserting that an array contains 'a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668!a4fd2951-56cf-4bd4-88b7-d05f299384d0:d39f88a-f1f2-4792-93b3-688a4b1d049b:fc5efc5d-94d4-4b53-be5e-d83f352ab56f'.

@issue-4421
🤔

That leaves
Scenario Outline: recipient of the shared resource tries to remove a tag                                   # /drone/src/tests/acceptance/features/apiSpaces/tag.feature:153
  Given user "Alice" has sent the following resource share invitation:                                     # SharingNgContext::userHasSentTheFollowingResourceShareInvitation()
    | resource        | folderMain         |
    | space           | use-tag            |
    | sharee          | Brian              |
    | shareType       | user               |
    | permissionsRole | <permissions-role> |
  And user "Brian" has a share "folderMain" synced                                                         # SharingNgContext::userHasShareSynced()
  And user "Alice" has created the following tags for <resource-type> "<resource>" of the space "use-tag": # TagContext::theUserHasCreatedFollowingTags()
    | tag in a shared resource |
    | second tag               |
  When user "Brian" removes the following tags for <resource-type> "<resource>" of space "Shares":         # TagContext::userRemovesTagsFromResourceOfTheSpace()
    | tag in a shared resource |
    | second tag               |
  Then the HTTP status code should be "<http-status-code>"                                                 # FeatureContext::thenTheHTTPStatusCodeShouldBe()
  When user "Alice" lists all available tags via the Graph API                                             # TagContext::theUserGetsAllAvailableTags()
  Then the HTTP status code should be "200"                                                                # FeatureContext::thenTheHTTPStatusCodeShouldBe()
  And the response <should-or-not> contain following tags:                                                 # TagContext::theFollowingTagsShouldExistForUser()
    | tag in a shared resource |
    | second tag               |
  Examples:
    | permissions-role | resource-type | resource                       | http-status-code | should-or-not |
    | Viewer           | file          | folderMain/insideTheFolder.txt | 403              | should        |
    | Editor           | file          | folderMain/insideTheFolder.txt | 200              | should not    |
    | Viewer           | folder        | folderMain                     | 403              | should        |
    | Editor           | folder        | folderMain                     | 200              | should not    |        Failed step: And the response should not contain following tags:        the response should not contain the tag tag in a shared resource.        Response        Array        (
          [0] => second tag
          [1] => tag in a shared resource        )                Failed asserting that true is false.

ok ... the test is wrong, it assumes the resource id of the shared resource is the same as the mountpoint. unfortunately that is no longer a valid assumption.

after debugging I see that:
PROPFIND https://ocis-server:9200/remote.php/dav/spaces/a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668/folderToShare (1) virtualSpaceUUID/folderName doesn't contain folderUUid "4b371513-f50c-4f21-b071-ab596d38a246$2c7ab090-26ec-4845-823a-80cd51248cbd!f84f399f-37c5-49be-b2ed-b847fbcb2141"
but in the same case when folder wasn't renamed (prefics (1)) -> that works fine
In the process, I honestly got confused with these tons of uuid and what should be there and what should not.
here is my screens:

regarding
Scenario Outline: recipient of the shared resource tries to remove a tag                                   # /drone/src/tests/acceptance/features/apiSpaces/tag.feature:153
    Given user "Alice" has sent the following resource share invitation:                                     # SharingNgContext::userHasSentTheFollowingResourceShareInvitation()
      | resource        | folderMain         |
      | space           | use-tag            |
      | sharee          | Brian              |
      | shareType       | user               |
      | permissionsRole | <permissions-role> |
    And user "Brian" has a share "folderMain" synced                                                         # SharingNgContext::userHasShareSynced()
    And user "Alice" has created the following tags for <resource-type> "<resource>" of the space "use-tag": # TagContext::theUserHasCreatedFollowingTags()
      | tag in a shared resource |
      | second tag               |
    When user "Brian" removes the following tags for <resource-type> "<resource>" of space "Shares":         # TagContext::userRemovesTagsFromResourceOfTheSpace()
      | tag in a shared resource |
      | second tag               |
    Then the HTTP status code should be "<http-status-code>"                                                 # FeatureContext::thenTheHTTPStatusCodeShouldBe()
    When user "Alice" lists all available tags via the Graph API                                             # TagContext::theUserGetsAllAvailableTags()
    Then the HTTP status code should be "200"                                                                # FeatureContext::thenTheHTTPStatusCodeShouldBe()
    And the response <should-or-not> contain following tags:                                                 # TagContext::theFollowingTagsShouldExistForUser()
      | tag in a shared resource |
      | second tag               |

    Examples:
      | permissions-role | resource-type | resource                       | http-status-code | should-or-not |
      | Viewer           | file          | folderMain/insideTheFolder.txt | 403              | should        |
      | Editor           | file          | folderMain/insideTheFolder.txt | 200              | should not    |
      | Viewer           | folder        | folderMain                     | 403              | should        |
      | Editor           | folder        | folderMain                     | 200              | should not    |
        Failed step: And the response should not contain following tags:
        the response should not contain the tag tag in a shared resource.
        Response
        Array
        (
            [0] => second tag
            [1] => tag in a shared resource
        )

        Failed asserting that true is false.

tests used PROPFIND "https://ocis-server:9200/dav/spaces/a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668/folderMain" to get folderId -> folderID is "a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668!4b371513-f50c-4f21-b071-ab596d38a246:7b277db6-7f0d-4b21-a98a-41253295349d:4cb75799-8708-426d-a382-d93cbb7560c2"

using this folderUUid tries to delete tag
curl 'https://ocis-server:9200/graph/v1.0/extensions/org.libregraph/tags' -XDELETE -ubrian:1234 -d'{"resourceId":"a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668!4b371513-f50c-4f21-b071-ab596d38a246:7b277db6-7f0d-4b21-a98a-41253295349d:4cb75799-8708-426d-a382-d93cbb7560c2","tags":["second tag"]}'  -vk

user gets 200 but tags are exist: GET https://ocis-server:9200/graph/v1.0/extensions/org.libregraph/tags ["second tag", "tag in a shared resource"]

we were using the resource id from the share jail instead of the actual resource id. fixed with https://github.com/owncloud/ocis/pull/10172/commits/0f525e9575e53ea6f27ba299b22db505417d1a2b

I merged the reva PR as @ScharfViktor and fixed the remaining bug and added the sharee PROPFIND same name shares shared by multiple users using new dav path scenario to expected failures for now.
enabling auto merge


Correction for raw affiliation INSERM U1242, OSS, Univ Rennes, Rennes, France.

Correction needed for raw affiliation INSERM U1242, OSS, Univ Rennes, Rennes, France.
raw_affiliation_name: INSERM U1242, OSS, Univ Rennes, Rennes, France.
new_rors: 015m7wh34;02vjkv261;00bf6bf92
previous_rors: 015m7wh34;02vjkv261
works_examples: W4315619047
contact: a6b20a123dfafa7516d12bcc55abdc01:972aa04498878970f79a65ddd1534148 @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


IGNITE-13634 Changes scope of Ignite and integration target dependencies to provided.

@samaitra I would appreciate it if you would take another look. I expanded the PR as discussed [1].
[1] - http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Release-Ignite-streamer-extensions-td49858.html

@ololo3000 The changes looks good, I have also look into test results in teamcity and they are looking good.
We have 3 tests failures in kafka module which are unrelated to these changes.
https://ci.ignite.apache.org/buildConfiguration/Tests_IgniteExtensions_Build/5730804?buildTab=tests&status=failed


Add button and hover selector to each components.

I would like to make it attractive by adding buttons and hover effect. Please assign this issue to me under gssoc'24 extended with label gssoc'24 and hacktoberfest.

@ADITHICJ, Share what your design solution looks like.
we are working on the design of the project, so join the Figma link here and make some of its design. Then code it.
Here is the Figma link:
https://www.figma.com/design/Gpp9lztaz36xu9nuGt7FBE/Frontend-Mentor?node-id=0-1&t=vJh3LEbs3Fw4ZmwL-1
If you have any doubts, feel free to ask and resolve them sooner on the Discord server below. It's a good idea to communicate better.
https://discord.gg/eXrQqgRX

Here is my design : https://www.figma.com/proto/Gpp9lztaz36xu9nuGt7FBE/Frontend-Mentor?node-id=41-3&node-type=canvas&t=n8s9DIKTcJ1hEXP4-1&scaling=min-zoom&content-scaling=fixed&page-id=0%3A1
Is this good?


Plugin not finding nim compiler in $PATH

When opening a test .nim file using Vim or GVim 7.4 on Ubuntu 14.10:
"test.nim" [New File]
Error detected while processing /home/.vim/bundle/nimrod.vim/autoload/nim.vim:
line 9:
the Nim compiler must be in your system's PATH

The nim compiler is definitely in the PATH (I can call it without issues), and this error even appears when I set vim to silent. The issue doesn't occur on a similar installation on OS X.
Also, I should note the syntax and indentation is working as expected, there is just a spurious error when launching.

update your shell profile, typically:   ~/.profile or ~/.bash_profile
as recommeded Dennis Felsing:
http://www.howistart.org/posts/nim/1


.github: Run GitHub Actions on master

Running our GitHub Actions on every push to master should help us notice and find the origin of regressions if we ever let some fall between the cracks.

Coverage decreased (-0.01%) to 37.863% when pulling f08a3a899da601f6d56d6b800deec96e26084104 on pr/pchaigno/run-github-actions-on-master into 78739a12e64286d6f41941ec629935812436f0b8 on master.

@pchaigno I was not aware of this PR, otherwise I would have added master branch in https://github.com/cilium/cilium/commit/51934c83a9268cc749a65a95c7fabef65e0eb182 as well.
As this PR is kind of ready, I will send update separately.

As this PR is kind of ready, I will send update separately.

@sayboras Could you also remove the path filter from the new Helm lint GitHub action? We've had issues in the past with path filters on Required GitHub actions. Basically, those actions don't always run, but GitHub's UI still fails PRs on which they don't run. The Helm lint GitHub action isn't yet required, but we will probably want it required soon :-)

As this PR is kind of ready, I will send update separately.

Could you also remove the path filter from the new Helm lint GitHub action? We've had issues in the past with path filters on Required GitHub actions. Basically, those actions don't always run, but GitHub's UI still fails PRs on which they don't run. The Helm lint GitHub action isn't yet required, but we will probably want it required soon :-)

Noted and thanks :100:

@pchaigno When I pressed Rebase and Merge (we don't have "create a merge commit" enabled on this repo), GitHub for some reason just pushed a merge commit into this, making it unready to merge :astonished:
I'll remove my commit from the branch. Not sure if this is GitHub being buggy or if this actually related to the PR?

I think 'update branch' button makes a merge commit.
On Tue, 12 May 2020, 8:36 am Sebastian Wicki<EMAIL_ADDRESS>wrote:

@pchaigno https://github.com/pchaigno When I pressed Rebase and Merge
(we don't have "create a merge commit" enabled on this repo), GitHub for
some reason just pushed a merge commit into this, making it unready to
merge 😲
I'll remove my commit from the branch. Not sure if this is GitHub being
buggy or if this actually related to the PR?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/cilium/cilium/pull/11439#issuecomment-627168868, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB5MSZIWXRHYFSEVIEFTQTRRD377ANCNFSM4M4POCXQ
.

I think 'update branch' button makes a merge commit.

Ah! If I accidentally clicked that, this would explain it.

I think 'update branch' button makes a merge commit.

Ah! If I accidentally clicked that, this would explain it.

On the other hand, I only pressed one single button and it completely blocked out the merge UI (with both buttons), with saying: "merge failed - please reload the page".


Characteristics

@AdamPJohnson the merge conflicts are minor things that I can resolve in the UI, but if I resolve them, then I have to commit the merge. So just let me know if it's otherwise good, and if so, I'll resolve them and merge.

@AdamPJohnson disregard the previous comment. Review as you normally would!

So good!


1.7.5 Patch Release.

This is a bug-fix release for 1.7.

[x] https://github.com/dmlc/xgboost/pull/8991
[x] https://github.com/dmlc/xgboost/pull/8692
[x] https://github.com/dmlc/xgboost/pull/8855
[x] https://github.com/dmlc/xgboost/pull/8860
[x] https://github.com/dmlc/xgboost/pull/8850
[x] https://github.com/dmlc/xgboost/pull/8853
[x] https://github.com/dmlc/xgboost/pull/8997
[x] https://github.com/dmlc/xgboost/pull/8998

Hi @hcho3 , I have submitted the update to both pypi and cran (which is still being tested). Could you please help make the maven release when you are available?

The JVM packages are now up.

Thank you for making the jvm release!


Opt cosine_similarity by avx2

The dimensions of the vectors are generally very high when performing brute-force vector retrieval calculations. In our online scenarios, there are at least 800 dimensions, and the use of SIMD instructions has a clear optimization effect. The optimization method is similar to: https://github.com/nmslib/hnswlib/blob/master/hnswlib/space_ip.h
The results are consistent with the test case results in the previous unit test：

What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.yulongzhao seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 0 / 7 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/math_functions.cpp
0
7
00.00%
[754, 755, 756, 757, 760, 762, 845]

@yulongfufu you have to run ./build-support/clang-format.sh to format cpp code.

@yulongfufu you have to run ./build-support/clang-format.sh to format cpp code.

Thank you for your guidance~
I have formatted my cpp code and pushed it up again.

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 0 / 24 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/math_functions.cpp
0
24
00.00%
[754, 755, 756, 757, 758, 759, 760, 844, 847, 848, 849, 850, 851, 852, 854, 855, 858, 859, 860, 861, 864, 866, 867, 871]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 0 / 24 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/math_functions.cpp
0
24
00.00%
[754, 755, 756, 757, 758, 759, 760, 844, 847, 848, 849, 850, 851, 852, 854, 855, 858, 859, 860, 861, 864, 866, 867, 871]


Compilation failure

Cloned latest and tried bin/run-once.sh
Got the following issue:
DDF/core/src/main/java/io/basic/ddf/BasicDDFManager.java (at line 20)
[ERROR]         public String getEngine() {
[ERROR]                       ^^^^^^^^^^^
[ERROR] The method getEngine() of type BasicDDFManager must override a superclass method

Hi @binhmop @jordaanw what's happening with this issue?


The link of Charades-STA dataset in CPL is no longer valid.

Could you provide the I3D feature for the Charades-STA dataset please? The link of Charades-STA dataset in CPL is no longer valid.

Sorry, I don't have the dataset anymore.
You may request the dataset from the authors of CPL
Thank you.
2024년 4월 22일 (월) 오후 7:25, YuxiangShao @.***>님이 작성:

Could you provide the I3D feature for the Charades-STA dataset please? The
link of Charades-STA dataset in CPL is no longer valid.
—
Reply to this email directly, view it on GitHub
https://github.com/sunoh-kim/pps/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOCULXYJUKQOS6TSOHHRKVDY6TQRFAVCNFSM6AAAAABGSPW4DSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI2TMMJWG4YDSNQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Enable stega on draftMode() only.

Is your feature request related to a problem? Please describe.
Using this template, i'm trying to enable stega only on draftMode() like this:

but im getting this typescript error:

Which i think it means you have to add support for this.
Maybe there is another way to do it or i'm missing something?
Thanks!

This is resolved in<EMAIL_ADDRESS>queryStore.loadQuery(query, params, {
  stega: draftMode().isEnabled,
})