Issue running native compiled games

Hi there,
i'd compiled OpenGothic on my machine. One can run it, but not in a wolf container.
Here's my log.
_Started initial process 11710 from ./Gothic2Notr.sh -g /var/shared_folder/Games_V2/Gothic II
Start monitoring process.
OpenGothic v1.0 dev
ALSA lib confmisc.c:855:(parse_card) cannot find card '0'
ALSA lib conf.c:5204:(_snd_config_evaluate) function snd_func_card_inum returned error: No such file or directory
ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings
ALSA lib conf.c:5204:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1342:(snd_func_refer) error evaluating name
ALSA lib conf.c:5204:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5727:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2721:(snd_pcm_open_noupdate) Unknown PCM default
---crashlog(std::system_error(No device))---
GPU: AMD Radeon RX 570 Series (RADV POLARIS10)
#1: std::unexpected() - /lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt10unexpectedv+0) [0x75634c627a55]
#2: std::unexpected() - /lib/x86_64-linux-gnu/libstdc++.so.6(+0xbb391) [0x75634c63d391]
#3: Tempest::SoundDevice::Device::Device(std::basic_string_view<char, std::char_traits >) - /var/shared_folder/Games_V2/Gothic II/libTempest.so(_ZN7Tempest11SoundDevice6DeviceC1ESt17basic_string_viewIcSt11char_traitsIcEE+0x1cb) [0x75634c9658db]
#4: Tempest::SoundDevice::PhysicalDeviceList::device(std::basic_string_view<char, std::char_traits >) - /var/shared_folder/Games_V2/Gothic II/libTempest.so(_ZN7Tempest11SoundDevice18PhysicalDeviceList6deviceESt17basic_string_viewIcSt11char_traitsIcEE+0x11b) [0x75634c965a1b]
#5: Tempest::SoundDevice::SoundDevice(std::basic_string_view<char, std::char_traits >) - /var/shared_folder/Games_V2/Gothic II/libTempest.so(_ZN7Tempest11SoundDeviceC1ESt17basic_string_viewIcSt11char_traitsIcEE+0x6e) [0x75634c96521e]
#6: Resources::Resources(Tempest::Device&) - /var/shared_folder/Games_V2/Gothic II/Gothic2Notr(_ZN9ResourcesC1ERN7Tempest6DeviceE+0xb3) [0x641f0bc95b93]
#7: main - /var/shared_folder/Games_V2/Gothic II/Gothic2Notr(main+0x207) [0x641f0bb09577]
Monitored process exited.
Initial process has exited (return code: 134)
All processes have quit
Exit with return code 134_

i'd compiled OpenGothic on my machine. One can run it, but not in a wolf container

Have you actually built a docker image with OpenGothic in it or just built the binary on your host? Wolf runs Docker images on-demand, and since it runs inside a container itself it doesn't have access to your host OS apps (this is by design).
If, instead, you've built a docker image, I can probably help you if you share the Dockerfile used.


THRIFT-3081 consolidate client processing loops

This pull request consolidates the client processing loops contained within TSimpleServer, TThreadedServer, TThreadPoolServer that were all similar but not functionally identical. This will improve maintainability.

Again, just minor issues.  +1 after they get fixed.
As with the THRIFT-2441 review, avoid inlined virtual dtors.  Try to scrub all the 'concurrency::' usages.

Okay this one is ready for re-review now.  I'll remind folks that this change and THRIFT-2441 have an interaction, so whichever one is merged first, I will need to refresh the other to line up with it.  The changes are minor, mostly in stop() being moved to the .cpp file(s).


Document features that require upgrade finalization

This list in not exhaustive. Instead, it focuses on key
user-facing features that aren't enabled until finalization.
Fixes #4486.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/4f6872f4c6867ed15257b15c48b271e70504bd6d/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/72560235b5853f28c5cf026bae06a7744d3a8d88/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c97e5a55206ed1397e5b23c2a292f2b41e118bd2/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/2c799ab32aa555b3c8ae6b7558f75d448b157f2a/


Aurelia Bundler produces invalid sourcemap file and second sourcemap url

I'm submitting a bug report

Library Version:
0.5.0 --> 0.6.0

Please tell us about your environment:

Operating System:
Windows 7

Node Version:
6.2.0

NPM Version:
4.1.1

JSPM OR Webpack AND Version
JSPM 0.16.53

Browser:
Chrome Version 58.0.3029.110 (64-bit)

Language:
TypeScript 2.4.0

Current behavior:
I have my bundles.js config set to be inline, the bundler produces a separate (invalid) map file anyway with contents 'undefined' inside.  It then appends a second sourcemap URL entry inside the app bundle after the base64 encoded inline content.
"bundles": {
    "dist/app-build": {
        "includes": [
            "[**/*.js]",
            "**/*.html!text",
            "**/*.css!text"
        ],
        "options": {
            "sourceMaps": 'inline'
            "inject": true,
            "minify": true,
            "depCache": true,
            "rev": true
        }
    },

What is the expected behavior?
Expected behavior is what happens in 0.4.0, the inline encoded sourcemap url is the only entry in the app-build.js file and there is no invalid app-build.js.map file generated.  I have reverted to 0.4.0 to get work done.

What is the motivation / use case for changing the behavior?
So that I can debug successfully in Chrome.

@Bitfiddler Pushed a new release out (0.6.2). Should fix this issue. Let us know if that works.

I was unable to test 0.6.2, but I attempted to migrate to 0.6.4 and it causes SystemJs loading errors so I have reverted back to 0.4.0 again.


⚠ Hartman Foundation has degraded performance

In e7d7f8c, Hartman Foundation (https://gordonhartman.com/) experienced degraded performance:

HTTP code: 502
Response time: 7639 ms

Resolved: Hartman Foundation performance has improved in 98372ac.


let cmake download includeos_install and bundle all libraries within "build" directory

Main goal is to make the build system self-contained, i.e., all needed libraries (included downloaded ones) should be within the build directory.
This also removes the need for external download tools.

Some files still need conversion (and are still used form ~/IncludeOS_Install): crtbegin.o, crti.o crtend.o crtn.o and some include directoires (api, api/sys, mod/GSL)

meh. only thing missing is libcrti and libcrtn... and those need special treatment.

@alfred-bratterud , @ingve : would it be possible to merge this?
TL;DR can build includeos without ~/IncludeOS_install
This changes the cmake based build process so that:

includeos_install will be downloaded within the build directory
during an in-place build, i.e., make within a build directly, all are generated within the build directory, all libraries included are used from the build-directory. Linker.ld, etc. are used from within the current source or build directory
make install installs libs, objects, etc. into the CMAKE_INSTALL_DIR library (slightly different directory style then ~/InludeOS_install).

Great @andreashappe, thanks!


write readme

2048 Game using Cursive
This is a Rust implementation of the popular 2048 game using the Cursive library for building terminal user interfaces. The game is played on a 4x4 grid where the player combines tiles with the same number to create a tile with a larger number. The goal is to create a tile with the number 2048.
Installation
To install the game, you need to have Rust and Cargo installed on your system. Once you have Rust and Cargo installed, you can clone the repository and run the following command:
cargo run --release
This will build and run the game in release mode.
How to Play
The game is played using the arrow keys on your keyboard. You can move the tiles left, right, up, or down. When two tiles with the same number touch, they merge into one tile with the sum of their numbers. The game is won when a tile with the number 2048 is created. The game is over when the board is full and no more moves can be made.
Features

Terminal user interface using Cursive
Random tile generation
Score tracking
Game over detection
Game won detection

Code Structure
The main game logic is implemented in the board.rs file. The Board struct represents the game board and contains methods for moving tiles, generating new tiles, and detecting game over and game won conditions. The board in game.rs is responsible for rendering the game board in the terminal using Cursive.
Contributing
Contributions are welcome! If you find a bug or have an idea for a new feature, please open an issue on the project or submit a pull request.
License
This project is licensed under the MIT License - see the LICENSE file for details.


Jcache removeAll(Keys) Method is not working ***

Hi,
removeAll (keys) Method is not working for "org.redisson.jcache.JCache".  Keys are still exising in the cache after After the execution of removeAll (keys).
Below Method in org.redisson.jcache.Jcache is returning 0.
private long removeValues(Object... keys) {
List params = new ArrayList(keys.length);
encodeMapKeys(params, Arrays.asList(keys));
return evalWrite(getName(), codec, RedisCommands.EVAL_LONG,
"redis.call('zrem', KEYS[2], unpack(ARGV)); "
+ "return redis.call('hdel', KEYS[1], unpack(ARGV)); ",
Arrays.asList(getName(), getTimeoutSetName()), params);
}
remove(key) is working fine.
Please find My code snippet below
public void invalidate(String region, Collection keys) {
if(keys == null || keys.isEmpty()){
return;
}
Cache<String, Serializable> cache = getCache(region);
	if (cache != null && !Formatter.isEmpty(keys)) {
		cache.removeAll(new HashSet<String>(keys));
	}

}

Please let me know if anything is Wrong from myside.
Thanks

Fixed! Thanks for report


PACKAGES: maintemplate desktop CI

desktop
We have .app and .exe and "exe"

Make an installer for each OS

hover packages code:
msi
pkg (dmg are old)
Linux snap, etc, etc

sign
https://github.com/itchio/itch-setup/blob/master/scripts/ci-build.sh#L73

1.5 push me the devs
1.7 push to app-store

auto-update (later)
https://www.electronjs.org/docs/api/auto-updater

squirrel desktop electron
mobile: see ci/update.

references:
Splash
https://github.com/asticode/go-astisplash
Notifications
https://github.com/asticode/astilectron/issues/24

will not work !!

hover use wixl to create msi installer for windows in linux, but the problem is wixl doesn't handle the UI, one solution is to use "mono-wine" + "wix msi toolset"
example:
Step-by-step guide on how to create a Windows flat installer package on linux
https://wiki.gnome.org/Projects/GTK/Win32/WiX


feat(#minor); Arrakis Finance; price lib support for polygon and optimism

Existing version was built pre-polygon/optimism support in price libs.
Incorporating latest price lib in order to support Arrakis subgraphs on polygon and optimism
Related to #1122

Deployments for QC:
Optimism deployment: https://subgraphs.messari.io/subgraph?endpoint=l0c4t0r/laboratory2&tab=protocol
Polygon deployment (pending version of l0c4t0r/laboratory4): https://subgraphs.messari.io/subgraph?endpoint=https://api.thegraph.com/subgraphs/id/QmNZhvMQoEw6rzmwCsyNj36TGbNzKuv6UwWBZmDF8UPrc2&tab=protocol


LayoutAnimation displays black background on view with borderTopRightRadius

🐛 Bug Report
A parent view has style={{ overflow: 'hidden', borderTopRightRadius: 5 }}
Inside the parent a child view is rendered with a LayoutAnimation. The surface which is hidden behind the rounded corners has a black background color during the LayoutAnimation
To Reproduce
Using LayoutAnimation to display a view inside a parent View that has style={{ overflow: 'hidden', borderTopRightRadius: 5 }} on it.
The bug is reproducable with any of the border(Top)(Bottom)(Left)(Right)Radius properties. There is no problem when using borderRadius.
Expected Behavior
There should be no black background color during the animation.
Code Example
https://snack.expo.io/@bugreport2/layoutanimation-bug
Environment
React Native Environment Info:
System:
OS: macOS 10.14.3
CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Memory: 2.49 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.2.0 - /usr/local/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
IDEs:
Android Studio: 3.2 AI-181.55<IP_ADDRESS>56338
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.1 => 0.59.1
npmGlobalPackages:
react-native-cli: 2.0.1

Bug confirmed on latest version of React Native 0.59.1

The issue is reproducible with the latest release (0.59.5)


Re-voting for Formal specification and analysis of Attestation in Confidential Computing

Background material
Previous relevant Attestation SIG presentations:

Date
Track
Presentation
Presenter
Materials

2023-02-14
Proposal
Transparency and Interoperability for Attestation in Confidential Computing
Muhammad Usama Sardar (@muhammad-usama-sardar)
slidespaper

2022-10-11
Information & data models for attestation
Preliminary proposal: Addressing 3 Key Problems of Attestation in Confidential Computing
Muhammad Usama Sardar (@muhammad-usama-sardar)
paper

2022-05-24
Information & data models for attestation
Intel TDX
Muhammad Usama Sardar (@muhammad-usama-sardar)
slidespaper

2022-03-29
secure channel establishment
Formal analysis of Enclave Key Exchange Protocol (EKEP)
Tom Roeder (@tmroeder)
ProVerif modelprotocol spec

Relevant IETF/IRTF discussions:

Proposed Formal Methods RG
some discussions at mailing list

Proposal
Formal specification and analysis of all phases of attestation mechanisms in Confidential Computing using ProVerif for the following TEEs:

Intel TDX
Arm CCA
AMD SEV-SNP

The deliverables for each of the above TEEs are as follows:

formal specification and analysis of initialization and attestation protocol phases in Proverif
formal specification and analysis of provisioning phase in ProVerif

Proponents
Muhammad Usama Sardar (@muhammad-usama-sardar)

Summary of public vote of chairs:
@thomas-fossati vote: https://github.com/CCC-Attestation/governance/issues/9#issuecomment-1472365248
@KeithMoyer vote: https://github.com/CCC-Attestation/governance/issues/9#issuecomment-1474113493
@gkostal vote: https://github.com/CCC-Attestation/governance/issues/9#issuecomment-1476230860
@shnwc: we wait for your vote.
@MikeCamel: The last time he was seen in the SIG is 18th Jan, 2022!

I resigned from the co-chairmanship soon after. No idea why this wasn't recorded.
On 3 April 2023 18:39:01 BST, Muhammad Usama Sardar @.***> wrote:

Summary of public vote of chairs:
@thomas-fossati vote:
https://github.com/CCC-Attestation/governance/issues/9#issuecomment-1472365248
@KeithMoyer vote:
https://github.com/CCC-Attestation/governance/issues/9#issuecomment-1474113493
@gkostal vote:
https://github.com/CCC-Attestation/governance/issues/9#issuecomment-1476230860
@shnwc: we wait for your vote.
@MikeCamel: The last time he was seen in the SIG is 18th Jan, 2022!
--
Reply to this email directly or view it on GitHub:
https://github.com/CCC-Attestation/governance/issues/10#issuecomment-1494722026
You are receiving this because you were mentioned.
Message ID:
@.***>

-Mike.

Thanks for recreating the issue so we can assess from a clean slate.
The co-chairs will initiate a vote once they have had a chance to review and discuss.

Thanks for recreating the issue so we can assess from a clean slate. The co-chairs will initiate a vote once they have had a chance to review and discuss.

It has already been sufficiently discussed for several months in SIG meetings as well as in #9.

Roll call vote taken at 2023/04/11 meeting.
@thomas-fossati @shnwc @gkostal voted yes.
@KeithMoyer absent, but sent a yes over email to the other co-chairs.
The repo was already created, so I don't think there is anything to do.
@muhammad-usama-sardar  please just double check that the final version of the scope is reflected in the repo.


Failure to note that new badge URL is case sensitive causes "Repo or workflow not found" after #8671

Are you experiencing an issue with...
shields.io
🐞 Description
Changing from

to
<img src="https://img.shields.io/github/actions/workflow/status/rcmaehl/MSEdgeRedirect/mser.yml?branch=<IP_ADDRESS>-dev&style=for-the-badge" height="45px" />
Causes "Repo or workflow not found". This is due to the previous method not being case sensitive for workflows, and the new method being case sensitive.
🔗 Link to the badge

💡 Possible Solution
Update documentation and #8671 to note this discrepancy

I've added a note to the top post in https://github.com/badges/shields/issues/8671 that it is case sensitive.


v0.8.3_11: Scroll bar is missing

SEVERITY: Minor
MODULE: Mountain Chart
Platform:  iPad Air 2 iOS(8.3) / Safari 8.0
RELEASE: v0.8.3
STEPS TO REPRODUCE:

Navigate URL: http://static.gapminderdev.org/vizabi/release/v0.8.3/preview/mountainchart.html
Mountain chart page will be loaded
Tap “Stack”
Note that scroll bar is missing under “Manual sorting of groups”

ACTUAL RESULTS:
Scroll bar is missing under “Manual sorting of groups”
EXPECTED RESULTS:
Scroll bar should be there under “Manual sorting of groups”
SCREENSHOT:

closing ad duplicate of #640


Added authentication to webdriver

Maybe it would be very safe to add security to the webdriver url. Like this feature https://github.com/aerokube/selenoid-ui/issues/151

@aprilahijriyan already implemented in Ggr.

@aprilahijriyan already implemented in Ggr.

@vania-pooh Hmm, I think it's better to apply it to "selenoid". rather than creating another library.

@vania-pooh Hmm, I think it's better to apply it to "selenoid". rather than creating another library.

@aprilahijriyan this does not scale. Everything more than 50 parallel Selenium sessions will require 2 or more hosts.

@aprilahijriyan this does not scale. Everything more than 50 parallel Selenium sessions will require 2 or more hosts.


Bundled tauri.js api can cause problems with targeted webview browsers

Describe the bug
The new bundle available for consuming from the npm tauri package is not compatible with some of the targeted browsers used by webview (in this case - Edge).
To Reproduce
Steps to reproduce the behavior:

Have a project using 0.7.1 that can target Edge
Upgrade tauri npm package to 0.8.0
Run the project, should still bring up window and pull in any css styles.  Any javascript created elements will likely not be generated.
Notice new error in console (a vague error from Edge that can mean an unsupported ... spread operator)

Steps to fix as the api consumer

Change any tauri imports from javascript to the esm build instead of the default rollup bundle. e.g. tauri/api/event -> tauri/api/esm/event

Expected default behavior
The default bundle to be able to be run on Edge for windows platforms.  Or a documentation section on requiring transpiling the bundle to the targeted browsers (although this may not work - see additional notes at the bottom).
Platform and Versions (please complete the following information):
Operating System - Windows_NT(10.0.18363) - win32/x64

Node.js environment
  Node.js - 12.18.2
  tauri.js - 0.8.0

Rust environment
  rustc - 1.44.1
  cargo - 1.44.1
  tauri-bundler - 0.6.0

Global packages
  NPM - 6.14.5
  yarn - 1.22.4

App directory structure
/.git
/.idea
/bindings
/dist
/node_modules
/src
/src-tauri

App
  tauri.rs - 0.7.0
  mode - no-server
  build-type - bundle
  CSP - false
  Windows - Edge
  distDir - ../dist
  devPath - http://localhost:8080

Additional context
On an additional note, I've tried to force transpiling of all dependencies with babel to the targets.
Using the webpack rule
{
  test: /\.m?jsx?$/,
  use: "babel-loader",
}

should also catch any javascript dependencies and pass them through babel.  In my experience though, the tauri bundle did not get transformed for whatever reason.
Comparing working versions (esm) vs the not working version (rollup bundle) the following code was the only code difference that used the spread operator that was not included in the esm build.
async function a(t){return await new Promise((n,e)=>{o({callback:i(n),error:i(e),...t})})}

I wrote a small equivalent that I think covers the object rest spread pattern used above in typescript.
async function test(t: object){
  return await new Promise(()=>{
    console.log(JSON.stringify({...t}))
  })
}

Compiling that code with babel (not tsc although it works too) and including a call to it when that app starts up still seems to work.  Which leads me to believe that the code in the rollup bundle cannot/is not being transpiled properly when pulled in as a dependency although others are.  Additionally, that code is transformed to not include the spread operator, instead using some helper from babel.
Also, the following code uses the spread operator too, but is included in the esm build also and still works on Edge.  In my vendor bundle, the previous and the following spread operators are the only ones found in 78.5 KiB in compressed code (for a total of 3).  It may be the case where it's the only dependency pulled in that directly uses the spread operator but I thought it was interesting to bring up.
function i(t, n = !1) {
    const e = r() + r() + "-" + r() + "-" + r() + "-" + r() + "-" + r() + r() + r();
    return Object.defineProperty(window, e, {
        value: r => (n && Reflect.deleteProperty(window, e), function (t) {
            let n = void 0, e = t[0], r = 1;
            for (; r < t.length;) {
                const o = t[r], i = t[r + 1];
                if (r += 2, ("optionalAccess" === o || "optionalCall" === o) && null == e) return;
                "access" === o || "optionalAccess" === o ? (n = e, e = i(e)) : "call" !== o && "optionalCall" !== o || (e = i((...t) => e.call(n, ...t)), n = void 0)
            }
            return e
        }([t, "optionalCall", t => t(r)])), writable: !1
    }), e
}

This is semi-related.
yarn tauri dev is still broken because in development builds, the esm build of tauri results in having an object spread operator as you can see in this gist.  This results in the same error SCRIPT1028: SCRIPT1028: Expected identifier, string or number from Edge.
Downgrading npm's tauri from 0.8.0 to 0.7.1 to allow dev mode works fine as long as you don't update the rust crate version.  Keeping the rust crate version to 0.6 works with tauri.js 0.7.1 but not 0.7 because (I think) it relies on some of the changes in tauri.js


ERR_TIMEOUT with Epson Printer U220

Hi, we have Epson U220 Printer and we are currently using beta version of this package. We've encountered an issue with this model of printer. When attempting to print, we receive the error ERR_TIMEOUT, Failed to communicate with the device within the specified time.
Platform

[x] Android
[x] iOS

We would greatly appreciate any assistance or guidance in resolving this issue

+1

@tr3v3r All prints to U220 fail and gibberish is being printed. Please take a look:

Could you help us debug maybe? :)

Okay, we have found the issue. We were passing EPOS_TM_U220 as the printer name (we had an override series setting).
Removing the override fixed it

@tolypash hello! could you please explain a bit more in detail how it was at what you did to fix that?
Have you used the old version or a new one?

Hello! So basically I was passing the wrong printer name (Instead of TM-U220 - I was passing EPOS2_TM_U220 (as a way of overriding the series from past version). Removing the override fixed it :)


AGDIGGER-61 - Allow to obtain build logs

Motivation
Allow to fetch build logs using java client.
Review @matzew @odra @luigizuccarelli

:+1:

Minor change introduced


Fix prod CVI Bernouilli

The purpose of this pull request is to make the functionality of the CVI to work with the Bernoulli distribution. The following changes have been made:

The sign of the Bernoulli log-normalizer has been corrected.
A new test has been added to ensure that the Bernoulli natural parameters align with ProdAnalytical().
A test has been added to verify that prod(::CVI, ::Bernoulli, ::Bernoulli) operates as intended.

With these changes in place, the CVI with Bernoulli distribution works.

Codecov Report
Base: 62.17% // Head: 61.34% // Decreases project coverage by -0.83% :warning:

Coverage data is based on head (2b9e9e4) compared to base (a363b8e).
Patch coverage: 100.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #273      +/-   ##
==========================================
- Coverage   62.17%   61.34%   -0.83%
==========================================
  Files         195      195
  Lines        7302     7236      -66
==========================================
- Hits         4540     4439     -101
- Misses       2762     2797      +35

Impacted Files
Coverage Δ

src/distributions/bernoulli.jl
93.54% <100.00%> (ø)

src/score/score.jl
25.00% <0.00%> (-36.54%)
:arrow_down:

src/nodes/gcv.jl
0.00% <0.00%> (-33.34%)
:arrow_down:

src/helpers/macrohelpers.jl
56.86% <0.00%> (-19.51%)
:arrow_down:

src/constraints/specifications/constraints.jl
0.00% <0.00%> (-10.35%)
:arrow_down:

src/rule.jl
56.15% <0.00%> (-8.49%)
:arrow_down:

src/addons.jl
61.90% <0.00%> (-8.47%)
:arrow_down:

src/constraints/specifications/form.jl
0.00% <0.00%> (-6.67%)
:arrow_down:

src/addons/logscale.jl
50.00% <0.00%> (-5.18%)
:arrow_down:

src/constraints/specifications/meta.jl
0.00% <0.00%> (-2.05%)
:arrow_down:

... and 1 more

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.


Tweaks from clang-tidy

This is (perhaps) mainly for discussion as I saw you removed clang-tidy checks last year. These fix a variety of minor things.
With one of the options that I was using, these still remain:
/Users/bruce/Development/custodian/cpptrace/src/symbols/../utils/utils.hpp:235:22: warning: noexcept specifier on the move constructor evaluates to 'false' [performance-noexcept-move-constructor]
  235 |             noexcept(std::is_nothrow_move_constructible<T>::value)
      |                      ^
/Users/bruce/Development/custodian/cpptrace/src/symbols/../utils/utils.hpp:250:64: warning: noexcept specifier on the move assignment operator evaluates to 'false' [performance-noexcept-move-constructor]
  250 |             noexcept(std::is_nothrow_move_assignable<T>::value && std::is_nothrow_move_constructible<T>::value)
      |                                                                ^

Regarding the warnings on the noexcepts, I used the same exception specification as std::optional and the move constructor/assignment operator are really only noexcept if T is nothrow move constructible. The move assignment could be relaxed to not require std::is_nothrow_move_assignable<T>::value, or alternatively maybe it should be implemented to actually use an assignment operator. But that wouldn't resolve the clang-tidy warning of course.
Does clang-tidy give any information about what T is leading to a false noexcept here? Or is it just waning that it could be false?


Length of Logs Are Much Longer than Expected

Training and Test Logs record many more values than would be expected. Currently, there are 4 observations around this problem:

Beginning of episodes initialize twice (2 step 0s)
First condition runs for 56 steps and restarts, twice at first episode
Number of episodes are 5x what is expected (e.g. test_episodes=20 results in 100 episodes run)
The logs end earlier than expected. It seems that the Unity executable is unable to log all of the episode steps before training completes.

is explained by the additional env.reset() that occurs in a vectorized environment.

This is resolved through the use of a DummyVecEnv rather than using the make_vec_env() function.
2 is explained by the env validation.
This is resolved through the addition of a validation mode flag to the Unity executable.

is explained by the decision steps parameter in Unity. Each decision in the environment is made every 5 steps in Unity.

Solution is to multiply maxSteps by the number of steps per decision in Unity.

For 4, it seems as if the executable from ml agents and the training code from SB3 are not working in synchrony. The final logged timestep seems to change with each run. Altering the total_timesteps value for model.learn results in the logs also stopping at random timesteps. Setting the buffer size to be larger than the steps_per_episode * train_eps results in code continuing to run until approximately the buffer size. However, it continues to end at a random point before that


Feature/raid 87

Add DOI authentication session service
Add DOI creator

Writes raid metadata into DOI DESC field

Change ID handler from apids to DOI
Add DOI link in frontend, on raid details page

Was included in https://github.com/au-research/raido/commit/48a47f7c2fe7b1e29bf15319c940eebf49c4844e


added data-srcset to last-seen-product

To make LazyLoading capable of LastSeenProducts I added data-srcset.

Thanks :blush:


fix workflows

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

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

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
5272

Relevant Lines:
5294

💛  - Coveralls


feat: Closes #290, implemented request body stream reading for PutObj…

Implemented request body streaming for PutObject and UploadPart actions

closing this, and contiuing work in #331


[media-gallery] Added Gallery Watch feature

Hello Raymes,
https://codereview.chromium.org/440813002 brought Gallery Watch private feature to public API.
BUG=#312
TBR=@raymes

Updated https://chrome.google.com/webstore/detail/media-gallery-sample/lidepfgfmameopopgagobnpndcnfgbnk


Update References.md

TITLE
Description
Description of the pull request changes and motivation.
Type of change
Please delete options that are not relevant.

[ ] New feature
[ ] Bug fix
[ ] Optimization

Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

[ ] This change is an Optimization

[ ] Benchmarks added/run

Codecov Report

Merging #122 (989ae0a) into main (e18f727) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #122   +/-   ##
=======================================
  Coverage   95.83%   95.83%
=======================================
  Files          44       44
  Lines        4440     4440
=======================================
  Hits         4255     4255
  Misses        185      185

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


79| Word Search | Java

Title - Word Search
What will change - I will add a Java implemented Algorithm for the above problem
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] Java

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

@efguydan I have a working solution in my back pocket. Would love to add it here as a contribution. It would be awesome if you could assign this to me. Thanks!

@efguydan you wanna work on this or do I assign it to @jedau

Yeah, i want to work on it @SSKale1.


[Bug]: Error [ERR_REQUIRE_ESM] with "sortTailwindcssClasses"

Description
Setting "sortTailwindcssClasses" to true results to the following error:
["ERROR" - 12:29:07] Error formatting document.
["ERROR" - 12:29:07] Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/idrisn/dev/todolu/tailwind.config.js from<EMAIL_ADDRESS>not supported.
Instead change the require of tailwind.config.js in<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.
Error: Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/idrisn/dev/todolu/tailwind.config.js from<EMAIL_ADDRESS>not supported.
Instead change the require of tailwind.config.js in<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.
    at /Users/idrisn/dev/todolu/node_modules/blade-formatter/dist/bundle.js:59:2579
    at async /Users/idrisn/dev/todolu/node_modules/@shufo/prettier-plugin-blade/src/worker.js:5:18
["INFO" - 12:29:07] Formatting completed in 22ms.

Expected Behavior
<form action="#" class="relative">

        Test

</form>

This test file should be sorted correctly.
Actual Behavior
The formatter fails and stops with the error mentioned above.
Additional Context
"prettier": "2.8.8",
"tailwindcss": "3.3.2",
"@shufo/prettier-plugin-blade": "^1.8.13",
# .prettierrc
{
    "plugins": ["@shufo/prettier-plugin-blade"],
    "overrides": [
        {
            "files": ["*.blade.php"],
            "options": {
                "parser": "blade",
                "tabWidth": 4,
                "sortTailwindcssClasses": true,
                "wrapAttributes": "auto"
            }
        }
    ]
}

It seems ESM setting used in your project causes this error.
Currently @shufo/prettier-plugin-blade does not support ESM so it could not read tailwind.config.js.
For work around, you can use CommonJS style config for tailwind.config.js
Delete type module setting from package.json
-"type": "module"

tailwind.config.js
e.g.
const defaultTheme = require("tailwindcss/defaultTheme");

module.exports = {
    theme: {
        screens: {
            sm: "0",
            md: "834px",
            lg: "1024px",
            xl: "1200px",
            xxl: "1440px",
            xxxl: "1900px",
            ...defaultTheme.screens,
        },
    },
};

But I'll consider dual support for ESM and CommonJS. Thanks @IdrisN

@shufo This sort of works but Laravel vite expects the file to be an ESM module so making this change makes "npm run dev" break. I'm using VS Code so I could use this workaround instead:

Do the steps above and restart VS Code
Undo the changes above, somehow VS Code still "remembers" the previous changes so sorting works and running npm commands as well. (At least until it's restarted again)

Might be worth moving to ESM even with a major version bump seem that seems the direction most JS packages are going.

@jahvi
Yes, I'm now working on ESM support.
https://github.com/shufo/blade-formatter/issues/820#issuecomment-1614132967
It depends on some CJS package so I must upgrade dependency packages first.
It might take about 1~2 weeks.

Undo the changes above, somehow VS Code still "remembers"

I also had that weird VSCode behaviour in past. Probably VSCode caches configs reading from this package.
I too restarting the VSCode is the only workaround.

Fixed at https://github.com/shufo/prettier-plugin-blade/releases/tag/v1.9.1.
Please try upgrade to ^1.9,0.

Getting the following error when trying to format a blade file:
Error: Unknown node type: undefined
    at Object.p [as print] (/doc/node_modules/@shufo/prettier-plugin-blade/src/options.ts:3:3)
    at callPluginPrintFunction (/doc/node_modules/prettier/index.js:8601:26)
    at mainPrintInternal (/doc/node_modules/prettier/index.js:8550:22)
    at mainPrint (/doc/node_modules/prettier/index.js:8537:18)
    at printAstToDoc (/doc/node_modules/prettier/index.js:8529:18)
    at coreFormat (/doc/node_modules/prettier/index.js:8837:20)
    at formatWithCursor2 (/doc/node_modules/prettier/index.js:9021:18)
    at /doc/node_modules/prettier/index.js:38183:12
    at Object.format (/doc/node_modules/prettier/index.js:38197:12)
    at t.PrettierMainThreadInstance.format (/live/.vscode/extensions/esbenp.prettier-vscode-9.19.0/dist/extension.js:1:18023)
    at t.default.format (/live/.vscode/extensions/esbenp.prettier-vscode-9.19.0/dist/extension.js:1:16114)
    at t.PrettierEditProvider.provideEdits (/live/.vscode/extensions/esbenp.prettier-vscode-9.19.0/dist/extension.js:1:12672)
    at U.provideDocumentFormattingEdits (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:101:45790)

File:

asd

Version: 1.9.1
Node: 18.12
Prettier: 2.8.8

@jahvi
Thanks for trying upgrade.
From 1.9.0, @shufo/prettier-plugin-blade depends on Prettier >= 3.0 so can you try upgrade prettier to ^3.0?
Prettier introduces breaking change between 2.0 and 3.0.
$ npm install -g<EMAIL_ADDRESS>
or it's better to use local dependencies cause it can enclose the dependencies.
$ cd your_project
$ npm install --save-dev prettier @shufo/prettier-plugin-blade
# yarn add -D prettier @shufo/prettier-plugin-blade
$ ./node_modules/.bin/prettier ~~~


crypto/tls: support X25519 key exchange

It's now shipped in BoringSSL and Chrome stable, and the RFC is basically 100% final, it'd be awesome if crypto/tls could be a leader in getting this rolled out.
Requires bringing X25519 itself into crypto/.

BoringSSL actually implemented this in their testing harness: https://boringssl.googlesource.com/boringssl/+/cba2b62a85215889285dfbe464f383397538760a^!/

Should be working as of 9e98e7e6686a500f87352e3721038d194b1db33c.


what's the difference between network embedding and graph embedding ?

Is there some formal definition ?

Network/Graph embedding are the same, both of which try to project nodes into a low-dimensional embedding space.


feat(docker): ghapp cli added

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Remove support for blobs snapshots from Dart VM

Now that we can write/read ELF we should remove the blobs format by

[ ] Mark the blob related functionality as deprecated
[ ] Notify all known embedders of this change
[ ] Fix embedders we care about ourselves
[ ] Make AppJIT snapshots use ELF instead of blobs

For context, we're deprecating blobs in favor of Assembly and ELF snapshots.
The blobs form currently has two significant limitations:

We cannot add new sections without updating all the Dart and Flutter embedders.
We cannot control or predict the relative positions of sections, inhibiting PC-relative loads and calls.

With Assembly and ELF snapshots we can add new sections without updating the embedders and discover the address of the new sections at runtime by offset from any of the existing sections.


fix: correct homepage link which was missing full dir name

Summary
The homepage link in the package results in a 404 error as the directory name had been cut off.
Test plan
–

@alopix thanks


Changing pybind11 bindings to used SHARED rather than using MODULE

This subtle change basically allows the python bindings to work correctly on windows.
For some background, I don't think I've ever gotten OIIO python bindings to work on windows, I've always chalked this up to using different versions of MSVC and never thought much of it (and just learned to only use the bindings at work).
All dependencies would have been installed via vcpkg.
The sort of error I would typically see was:
>>> import OpenImageIO
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: DLL load failed while importing OpenImageIO: The specified module could not be found.

Not terribly informative, but if instead I do:
from ctypes import cdll
cdll.LoadLibrary("./OpenImageIO.cp38-win_amd64.pyd")

We get a popup message saying the following symbol couldn't be resolved:
??9TypeDesc@OpenImageIO_v2_3@@QEBA_NAEBU01@@Z
Running that through https://demangler.com/ we get:
public: BOOL __cdecl OpenImageIO_v2_3::TypeDesc::operator!=(struct OpenImageIO_v2_3::TypeDesc const & __ptr64)const __ptr64
The actual definition of which is:
    constexpr bool operator!= (const TypeDesc &t) const noexcept { return ! (*this == t); }

And if we run dumpbin on the python module we can see:
    OpenImageIO.dll
             1800D3280 Import Address Table
             1800EDBB8 Import Name Table
                     0 time date stamp
                     0 Index of first forwarder reference

                         14A ??9TypeDesc@OpenImageIO_v2_3@@QEBA_NAEBU01@@Z
                         ...

Somehow the python shared object, has a dependency on a constexpr function, which could (and I haven't looked into this) have something to do with declaring OIIO_API at the class level.
In any case, changing pybind11_add_module to use SHARED rather than implicitly MODULE fixes this (which is something I've seen using GCC/Linux on in-house codebases).

Hmmm.
So, we recently got the Python bindings working for the Windows CI build. A handful of tests in Windows CI are still failing and we're working our way through them, but the Python bindings definitely can work without this fix.
So I'm not sure that it's inherently broken with MODULE. But I don't know enough about Windows dev. Could it depend on which MSVS? Could the VCPkg setup have something different that is relevant? Is there a problem with the symbol visibility where we're doing something that's subtly wrong in this case?
If I understand the docs, SHARED is supposed to be for shared libraries that you link against, whereas MODULE is specifically for a runtime-loadable library, like a plugin (or python module). MODULE being the default that pybind11's utility functions impose is also strong circumstantial evidence that this is the usual choice for building loadable python modules.
I don't know all the ways that SHARED vs MODULE  differ on each OS. I know that for MacOS, they imply different file extension (by common convention, anyway) of .dylib vs .so. So I wouldn't want to end up with any oddities on other platforms by making a change here.
So here is how I would like to propose proceeding:

Since the docs appear to make it clear that this is more of a MODULE situation, let's be careful not to change or break any platforms where it currently works. So at the very least, it should only use SHARED -- if indeed that is the right solution anywhere -- on Windows.

Are we sure that the problem isn't a missing OIIO_API, or an OIIO_API where it shouldn't be, or some symbol visibility or compiler flag set incorrectly, that SHARED jiggles something that makes it work coincidentally, but that's not the most correct solution?

Hmmm.
So, we recently got the Python bindings working for the Windows CI build. A handful of tests in Windows CI are still failing and we're working our way through them, but the Python bindings definitely can work without this fix.
So I'm not sure that it's inherently broken with MODULE. But I don't know enough about Windows dev. Could it depend on which MSVS? Could the VCPkg setup have something different that is relevant? Is there a problem with the symbol visibility where we're doing something that's subtly wrong in this case?
If I understand the docs, SHARED is supposed to be for shared libraries that you link against, whereas MODULE is specifically for a runtime-loadable library, like a plugin (or python module). MODULE being the default that pybind11's utility functions impose is also strong circumstantial evidence that this is the usual choice for building loadable python modules.
I don't know all the ways that SHARED vs MODULE  differ on each OS. I know that for MacOS, they imply different file extension (by common convention, anyway) of .dylib vs .so. So I wouldn't want to end up with any oddities on other platforms by making a change here.
So here is how I would like to propose proceeding:

Since the docs appear to make it clear that this is more of a MODULE situation, let's be careful not to change or break any platforms where it currently works. So at the very least, it should only use SHARED -- if indeed that is the right solution anywhere -- on Windows.

Are we sure that the problem isn't a missing OIIO_API, or an OIIO_API where it shouldn't be, or some symbol visibility or compiler flag set incorrectly, that SHARED jiggles something that makes it work coincidentally, but that's not the most correct solution?

Yeah it does appear pybind11 does just pass it directly to add_library.
https://github.com/pybind/pybind11/blob/master/tools/pybind11Tools.cmake#L145-L151
And I'll be honest, before pybind11 I wasn't even aware of MODULE (and from what I can see, it does sound like it should result in just a .dll/.so with no .lib/.a).
Not really sure about the extension changing although on Windows, it appears to always result in a .pyd.
I managed to capture a diff between some of the generated things that sounded relevant (left is MODULE and right is SHARED):
PyOpenImageIO.vcxproj: https://editor.mergely.com/l9zdnZBA/
CL.command.1.tlog: https://editor.mergely.com/fpdqbBBP/
link.command.1.tlog: https://editor.mergely.com/LWgyhoCe/
Nothing really seems (to my eyes anyway) to standout here, which makes this even more confusing.
I attempted to use THIN_LTO and NO_EXTRAS, both of which didn't seem to do anything of note.
I removed the OIIO_API call from being at struct OIIO_API TypeDesc and sprinkled them into the respective implementation calls, and I can confirm that this causes the new unresolved symbol to move to:
public: int __cdecl OpenImageIO_v2_3::ParamValue::nvalues(void)const __ptr64
And TypeDesc references are no longer found as imports (via dumpbin).
So I did the same thing to ParamValue and ParamValueList, which then pushed the list of unresolved things onto:
public: unsigned __int64 __cdecl OpenImageIO_v2_3::ImageSpec::scanline_bytes(BOOL)const __ptr64
It would appear that putting OIIO_API explicitly on every function rather than at the class level fixes whatever symbol lookup problem is being casued (although I guess it wouldn't protect from a third-party library that might be in a header doing the same thing).
I'm not entirely sure WHY this is the case, because presumably, it's been like this for a while.

Yeah it does appear pybind11 does just pass it directly to add_library.
https://github.com/pybind/pybind11/blob/master/tools/pybind11Tools.cmake#L145-L151
And I'll be honest, before pybind11 I wasn't even aware of MODULE (and from what I can see, it does sound like it should result in just a .dll/.so with no .lib/.a).
Not really sure about the extension changing although on Windows, it appears to always result in a .pyd.
I managed to capture a diff between some of the generated things that sounded relevant (left is MODULE and right is SHARED):
PyOpenImageIO.vcxproj: https://editor.mergely.com/l9zdnZBA/
CL.command.1.tlog: https://editor.mergely.com/fpdqbBBP/
link.command.1.tlog: https://editor.mergely.com/LWgyhoCe/
Nothing really seems (to my eyes anyway) to standout here, which makes this even more confusing.
I attempted to use THIN_LTO and NO_EXTRAS, both of which didn't seem to do anything of note.
I removed the OIIO_API call from being at struct OIIO_API TypeDesc and sprinkled them into the respective implementation calls, and I can confirm that this causes the new unresolved symbol to move to:
public: int __cdecl OpenImageIO_v2_3::ParamValue::nvalues(void)const __ptr64
And TypeDesc references are no longer found as imports (via dumpbin).
So I did the same thing to ParamValue and ParamValueList, which then pushed the list of unresolved things onto:
public: unsigned __int64 __cdecl OpenImageIO_v2_3::ImageSpec::scanline_bytes(BOOL)const __ptr64
It would appear that putting OIIO_API explicitly on every function rather than at the class level fixes whatever symbol lookup problem is being casued (although I guess it wouldn't protect from a third-party library that might be in a header doing the same thing).
I'm not entirely sure WHY this is the case, because presumably, it's been like this for a while.

Can you check something briefly for me? Instead of relying on the default behavior of pybind11_add_module implying MODULE, what happens if you pass MODULE explicitly (instead of SHARED) to pybind11_add_module?
I was looking at the source of pybind11_add_module and there is something that looks suspiciously like there might be a bug in how this is handled.  (... haha, yes, and it has been fixed already in their master branch, though I'm not sure it affects us here or not)

Can you check something briefly for me? Instead of relying on the default behavior of pybind11_add_module implying MODULE, what happens if you pass MODULE explicitly (instead of SHARED) to pybind11_add_module?
I was looking at the source of pybind11_add_module and there is something that looks suspiciously like there might be a bug in how this is handled.  (... haha, yes, and it has been fixed already in their master branch, though I'm not sure it affects us here or not)

"blanket using SHARED":
I don't like this solution because it seems to contradict the stated meaning of SHARED/MODULE. The cmake docs say

SHARED libraries are linked dynamically and loaded at runtime. MODULE libraries are plugins that are not linked into other targets but may be loaded dynamically at runtime using dlopen-like functionality.

That really makes it sound like python modules (not linked against explicitly, but runtime loaded by the python interpreter) is precisely the case where MODULE is intended to be used.
In practice, on some platforms (including Linux), there is no effective difference between the two, but on others there may be, so this just doesn't seem safe or future-proof to me.
"Keeping MODULE but changing OIIO_API declerations."
If it were just one or two small classes where moving the OIIO_API from the class def to every non-inline method declaration might fix, I would say that sounds like the best fix. But it looks like we have lots of classes like that, so I'm not quite ready to encourage such an extensive change unless it's unnecessary
"Adding SHARED to just Windows":
This is certainly the simplest change (one word!), and has the merit of being certain not to break any platforms that are currently working.
The only thing I worry about is that, because we don't fully understand why this works when it seems to contradict the CMake docs -- and that other Windows users including our own Windows CI seem to have it working just fine now -- is that adding the SHARED will break some other Windows case. Maybe whatever is going wrong is particular to the specific version of MSVS, or cmake (maybe a bug was added, or fixed, deep in cmake's handling of SHARED vs MODULE for Windows).
But at least if, after making this change, if it turns out that other people complain that it breaks for them, it's also extremely easy to reverse and then try one of the more difficult solutions or to keep searching to understand the real underlying issue.
I do have one more alternate idea, will put in a different comment after I check a couple things.

"blanket using SHARED":
I don't like this solution because it seems to contradict the stated meaning of SHARED/MODULE. The cmake docs say

SHARED libraries are linked dynamically and loaded at runtime. MODULE libraries are plugins that are not linked into other targets but may be loaded dynamically at runtime using dlopen-like functionality.

That really makes it sound like python modules (not linked against explicitly, but runtime loaded by the python interpreter) is precisely the case where MODULE is intended to be used.
In practice, on some platforms (including Linux), there is no effective difference between the two, but on others there may be, so this just doesn't seem safe or future-proof to me.
"Keeping MODULE but changing OIIO_API declerations."
If it were just one or two small classes where moving the OIIO_API from the class def to every non-inline method declaration might fix, I would say that sounds like the best fix. But it looks like we have lots of classes like that, so I'm not quite ready to encourage such an extensive change unless it's unnecessary
"Adding SHARED to just Windows":
This is certainly the simplest change (one word!), and has the merit of being certain not to break any platforms that are currently working.
The only thing I worry about is that, because we don't fully understand why this works when it seems to contradict the CMake docs -- and that other Windows users including our own Windows CI seem to have it working just fine now -- is that adding the SHARED will break some other Windows case. Maybe whatever is going wrong is particular to the specific version of MSVS, or cmake (maybe a bug was added, or fixed, deep in cmake's handling of SHARED vs MODULE for Windows).
But at least if, after making this change, if it turns out that other people complain that it breaks for them, it's also extremely easy to reverse and then try one of the more difficult solutions or to keep searching to understand the real underlying issue.
I do have one more alternate idea, will put in a different comment after I check a couple things.

The "other thing" I mentioned didn't pan out.
After a little more thought, I think we should go ahead with the simple "use SHARED on Windows" strategy, using a modified version of this PR:
Near the top of the pythonutils.cmake, where the other options are, put this:
if (WINDOWS)
    set (PYLIB_LIB_TYPE SHARED CACHE STRING "Type of library to build for python module (MODULE or SHARED)")
else ()
    set (PYLIB_LIB_TYPE MODULE CACHE STRING "Type of library to build for python module (MODULE or SHARED)")
endif ()

and change the call to
pybind11_add_module(${target_name} ${PYLIB_LIB_TYPE} ${lib_SOURCES})

This makes it very easy to override with a config-time -DPYLIB_LIB_TYPE=MODULE, in case anybody else's build is broken by your change.
If lots of people report that using SHARED breaks and it's only you and a minority of other people with a particular situation for whom MODULE is not the right choice, we could later change the default for Windows (like for the other OS's) back to MODULE, but then you would have a way to easily override to fix your builds.
What do you think?

The "other thing" I mentioned didn't pan out.
After a little more thought, I think we should go ahead with the simple "use SHARED on Windows" strategy, using a modified version of this PR:
Near the top of the pythonutils.cmake, where the other options are, put this:
if (WINDOWS)
    set (PYLIB_LIB_TYPE SHARED CACHE STRING "Type of library to build for python module (MODULE or SHARED)")
else ()
    set (PYLIB_LIB_TYPE MODULE CACHE STRING "Type of library to build for python module (MODULE or SHARED)")
endif ()

and change the call to
pybind11_add_module(${target_name} ${PYLIB_LIB_TYPE} ${lib_SOURCES})

This makes it very easy to override with a config-time -DPYLIB_LIB_TYPE=MODULE, in case anybody else's build is broken by your change.
If lots of people report that using SHARED breaks and it's only you and a minority of other people with a particular situation for whom MODULE is not the right choice, we could later change the default for Windows (like for the other OS's) back to MODULE, but then you would have a way to easily override to fix your builds.
What do you think?

I think this makes perfect sense!
PR updated.

I think this makes perfect sense!
PR updated.


Force user to re-type Parity phrase before showing address to prevent typos leading to later-inaccessible wallet

"When someone enters in a private key or parity recovery phrase on the "view wallet" feature, do not let them view the address until they've re-entered it."
(via https://twitter.com/ryancdotorg - 5.22.17)

Will be removing Parity phrases for v4.


Duplicate Channel Names in programming files - a problem?

Because we have multiple repeaters owned by some groups, we end up with duplicate channel names in our programming files (just the call sign of the controlling organization).
So it's difficult to identify the specific channel being used on the radio.  This may especially be a problem when "hunting" for contacts by scanning.  It won't be clear on which channel you are actually making contact.
Some radios have limited number of characters to disambiguate the channels if the full call sign is used as well.
Perhaps channel numbers should be preserved between all the programming files, so the channel number can be used to cross-reference a numbered list in the repeaters.md file (web page).
For example - these names might be good if they would fit:
WW7PSR-2m
WW7PSR-6m
WW7PSR-dmr

I imagine most of the digital radios may not have this issue because of their displays, but I am guessing the vast majority of HTs use liquid crystal with very limited space. My own radios stop at six and seven characters... which is truly unhelpful, we agree !
I'm not sure what to do about this. I am reluctant to have empty channels depending on the programming file, because it might be easy to oversee a bunch of repeaters that way. I was imagining that people might log channel numbers and then cross-reference with the file they used to program things. Maybe we should seek community input on this ?

Baofeng has a 7-character limit for these.  So, most call signs would afford one additional digit.
If we add numbering to the HTML page, then retain the same numbering in the programming files, I think that would be helpful.
Alternatively, simple solution could be to rename displayed repeaters and WWPSR1, WWPSR2, etc. (without and mnemonic convention for band or mode - just a disambiguating digit - but only for the groups that have multiple repeaters).

So my only thought : I've asked people to log repeater callsign and output frequency, so that I can tell them apart. If we now introduce a new code that is sometimes a repeater callsign and sometimes isn't, it may get confusing. I don't think there's a clear answer here, but I'm inclined to generate files with no gaps and count on people logging internally their channel number.
As I type that, actually, perhaps the best is to ask folk to log a "RR Channel Number" and, as you say, generate files with gaps where needed so that numbering is consistent. Then we ask folk to log the repeater callsign and channel number, forgetting output frequency.

Channel names can stay the same, only if we make channel numbers consistent.  My radio, does display channel number as well as channel name - so I would be able to tell which one I'm on.
I think logging a RR Channel Number is easier (as long as we don't change them during the contest!) for folks as well...so, I'd be in favor of that change as well.

Alright, I'll begin working on that.
Quentin CAUDRON, PhD
quentincaudron.com
On Sun, 6 Nov 2022 at 18:15, Mike Koss @.***> wrote:

Channel names can stay the same, only if we make channel numbers
consistent. My radio, does display channel number as well as channel name -
so I would be able to tell which one I'm on.
I think logging a RR Channel Number is easier (as long as we don't change
them during the contest!) for folks as well...so, I'd be in favor of that
change as well.
—
Reply to this email directly, view it on GitHub
https://github.com/QCaudron/repeater_roundabout/issues/8#issuecomment-1304996303,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA576GYBVQB73RSDA5VDR6LWHBJZRANCNFSM6AAAAAARX4PCGQ
.
You are receiving this because you commented.Message ID:
@.***>

Addressed by #17.

I like it!


CRITICAL - sharp: Installation error: certificate has expired

Possible install-time or require-time problem

[x] I have read the documentation relating to installation.
[x] I have ensured that the architecture and platform of Node.js used for npm install is the same as the architecture and platform of Node.js used at runtime.

Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

What is the complete output of running npm install --verbose --foreground-scripts sharp in an empty directory?

npm info run<EMAIL_ADDRESS>install node_modules/sharp (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)

><EMAIL_ADDRESS>install
> (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)

sharp: Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.14.2/libvips-8.14.2-win32-x64.tar.br
sharp: Installation error: certificate has expired
sharp: Please see https://sharp.pixelplumbing.com/install for required dependencies
npm info run<EMAIL_ADDRESS>install { code: 1, signal: null }
npm notice
npm notice New minor version of npm available! 9.5.1 -> 9.6.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.2>
npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm verb stack Error: command failed
npm verb stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\@npmcli\promise-spawn\lib\index.js:53:27)
npm verb stack     at ChildProcess.emit (node:events:512:28)
npm verb stack     at maybeClose (node:internal/child_process:1098:16)
npm verb stack     at ChildProcess._handle.onexit (node:internal/child_process:304:5)
npm verb pkgid<EMAIL_ADDRESS>npm verb cwd C:\Users\Belial\Documents\GitHub\sharp
npm verb Windows_NT 10.0.19045
npm verb node v19.8.1
npm verb npm  v9.5.1
npm ERR! code 1
npm ERR! path C:\Users\Belial\node_modules\sharp
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
npm verb exit 1
npm verb unfinished npm timer reify<PHONE_NUMBER>894
npm verb unfinished npm timer reify:build<PHONE_NUMBER>967
npm verb unfinished npm timer build<PHONE_NUMBER>968
npm verb unfinished npm timer build:deps<PHONE_NUMBER>968
npm verb unfinished npm timer build:run:install<PHONE_NUMBER>975
npm verb unfinished npm timer build:run:install:node_modules/sharp<PHONE_NUMBER>975
npm verb code 1

npm ERR!      C:\Users\Belial\AppData\Local\npm-cache\_logs\2023-03-24T20_56_17_847Z-debug-0.log

What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
  System:
    OS: Windows 10 10.0.19045
    CPU: (32) x64 AMD Ryzen 9 5950X 16-Core Processor
    Memory: 31.94 GB / 63.92 GB
  Binaries:
    Node: 19.8.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 4.0.0-rc.37 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    sharp: ^0.32.0 => 0.32.0

Created in both repos, feel free to close one.

https://www.githubstatus.com/incidents/x7njwb481j9b


@ prevents wildcard capture

While attempting to save email addresses, I discovered the following.
Using this script:
+ save email *~5
- {keep} saving email <cap> ^save(email,<cap>)

We can see the following results:
You> save email one two three

Bot> saving email one two three  //one two three is saved as expected
You> save email one. two three

Bot> saving email one  //message broken into two sentences, one is still captured, as expected.
You> save email<EMAIL_ADDRESS>
Bot>                     //with @symbol, nothing is captured
You> save email one@two

Bot>                     //with @symbol, nothing is captured
You> save email one @ two

Bot>                     //with @ symbol, nothing is captured
You> save email one.two three

Bot> saving email one //message broken into two sentences, one is still captured
You>

As a side note, that the message gets broken into two after a period(even if no trailing space after period) is probably the right thing. still sorting out the implications for capturing email addresses in that situation. in the interim have been using + trigger * then processing against this.message.original.  Given that any email address will necessarily be split into two messages, i can see this leading to unexpected results.

Why don't you try processing the input with a function then create a filter
that
also extracts the email as a capture?
The current parser is based on RegEx so there are a lot of characters that
are
escapes in conversations, therefore gambit rules/wildcards can't handle all
these situations. If they did you would need a syntax such as (*)@(*).(*)
which does not work now because the period is escapes. So... Functions. :-)
Hint: look in the wiki at using filter functions in triggers (not()
function)

I am currently doing something similar - i think. https://gist.github.com/Lewwwk/feca922f5c68175c4bf4

Clarifying - it's not that the input isn't being captured, is that it's returning an empty reply. So this means the only way to process an input that has a @ in it is by using a * wildcard (which will accept the message and parse it into two sentences because of the .tld).

@Lewwwk I want to follow up and see if this behavior is fixed with the change to the lexor splitting sentences now.

Unfortunately not. Parsing returns empty message when an @ symbol is included in a wildcard capture. (running ss 0.10.5)

I believe this works as expected in 0.10.7. The change was in here - https://github.com/silentrob/superscript/blob/master/package.json#L57
You might need to blow out your node_modules and re-run npm install


Revert "Implement parallel foreach() for easier multithreading"

Reverts https://github.com/godotengine/godot/pull/72784. The WTP changes will be reverted until the topic can be discussed in its entirety, with some possibly coming back when there's a stronger agreement.
(CC @myaaaaaaaaa)

To address @reduz's points from #72784 :

I really, really think this should not have been merged. You don't need the syntactic sugar for something very seldom used that all it does is make readability worse.

See the following PRs for places where readability is improved:
#78016 ( Relevant commit: https://github.com/godotengine/godot/pull/78016/commits/1048a464c781d6f1ed4574fc98de591a393528d2 )
#79481
#79490
Note that the current signature is due to prioritizing feature parity with WorkerThreadPool::add_*_group_task() and for(), since most of the work is in the above three PRs that do most of the refactoring. I would recommend renaming it with a cleaner signature in the future.

This is not a general purpose function, it is meant for large tasks. if you use it in any array all you will achieve is it probably being much slower than just doing a regular for loop and users will not understand why.

This is addressed by #72716 .

Thanks! Let's discuss this more thoroughly (on the contributors chat, preferably) and find a good solution that we can implement in one go. I think readability improvements from this change were great, but we need to make sure it doesn't come at a cost of confusion or, worse, performance.

...find a good solution that we can implement in one go.

I generally prefer to approach refactors and changes to core in small commits, since it lets each change be tested in isolation, makes things easier for reviewers,[^refactor] and makes any potential regressions easier to bisect.
But I see that doing things this way created its own problems by making things overly confusing to keep track of.
[^refactor]: Huge squashed commits are generally discouraging to review and get delayed a lot in practice. #49362 is possibly the biggest victim of this.
In that case, would you be willing to accept a PR with multiple commits (obviously with each individual commit passing CI)? This way, reviewability and bisectability are maintained, while making it easier to keep track of the big picture under one PR.
This is assuming of course that parallel_for() is still a desired feature, since reduz seemed particularly against it.

But I see that doing things this way created its own problems by making things overly confusing to keep track of.

Well, it's more about the snowballing effect. We merge one change that looks okay-ish, and it breaks stuff, and so we patch it, and it potentially breaks more stuff. And each solution becomes progressively more hacky, making the whole thing much less appropriate and much less likely to pass the quality control for the core.
So to avoid that we need to arrive to a well-vetted solution before implementing it.


New extension suggestion: Magnetize

This simple extension scans selected text for a BitTorrent infohash and opens the corresponding magnet link. Useful for fast downloading of files for which the infohash is available, if a compatible client is installed.

Hey thanks for this. It seems cool. I'm not too clued up on BitTorrent however. Could you post an example of a BT infohash for me to test this with?

Of course! I created a small test text file that I now share through the BT client on my Mac. It has the following infohash: 45d0215e5a87f81fc45cbf096c899d9017d542f6.
If you select this hash and click Magnetize in the PopClip row, it should open up the related magnet link in your BT client. This of course requires a client that supports magnet links; I use Transmission (https://transmissionbt.com). If your client opens the link but nothing happens, it is probably because I switched off my Mac (since it's a peer-to-peer system) 😉
Let me know what you think!


unable open the modal from right or left

I also want this feature.

Check line 448 in index.js for this project. Change to something like this:
style={[styles.wrapper, size, this.props.style, {transform: [{translateY: this.props.sideOpening == 'horizontal' ? offsetX : this.state.position}, {translateX: this.props.sideOpening == 'horizontal' ? this.state.position : offsetX}]} ]}
I added props called sideOpening so when it's horizontal it opens from the right to left and when it's vertical it opens from bottom to top. It's just a quick fix. Works for my current project.
Cheers.

I have the same issue did you solve it? @cindyya

this.calculateModalPosition(this.state.containerWidth, this.state.containerHeight);

Very nice work @prodoxx !
I used your description to make a version that work from left to right with other parts of his lib working like pan gestures and animations.
I used the prop entry with the value 'left' instead of creating a new one.
https://github.com/AugustusCosta/react-native-modalbox


Adding a table to TPC-C

What steps should I follow if I want to add a table to the TPC-C benchmark?
Right now I'm adding a table by changing the TPCC_TABLE_LIST marco, as well as adding an additional RegisterTable call in the constructor of class tpcc_bench_runner. It compiles, loads, and the output appears to show the correct numbers/types of tables being initialized. However it will then reliably crash upon calling OrderedIndex::remove() (in Delivery transactions). It crashes on base_txn_btree.cc:209, for a completely different table (not the new table I added). And the only thing I changed was adding a table...
It's confusing isn't it... Any help/insight is greatly appreciated.

Turns out it has nothing to do with adding tables to benchmarks... see #6


fleetctl: print out result message explicitly

Fleetctl stop or unload has been always printing out somewhat ambiguous messages like below:
  Unit app.service loaded on 0eb1b9b6.../coreos1

For better usability, print out a better result message, either about stopping (or unloading) successfully, or failing to do.
Partially resolves: https://github.com/coreos/fleet/issues/1432
/cc @kayrus @tixxdz

Updated, to print friendly messages for both stop and unload.

Merged https://github.com/coreos/fleet/pull/1577. Thanks.


Format PYI files in docs correctly

Summary
Now that docs are formatted by the Ruff formatter, https://github.com/astral-sh/ruff/pull/13087. It is also possible to format pyi-style examples with the pyi-style format fixing https://github.com/astral-sh/ruff/issues/11568.
One concern I have with this update is that syntax highlighting is currently not implemented in MK docs for PYI examples. Therefore, we need to decide if it is better that the docs are formatted correctly or if syntax highlighting is more important. If the latter is the case, I can investigate this further and draft this PR for now.
Test Plan

CI to check that docs are formatted correctly

CC @AlexWaygood, I would appreciate it if you could review this PR as you opened the issue that prompted this update. I think it would be useful to sense-check the examples that I updated to PYI, as well as let me know and further examples that would benefit from pyi style formatting and I can update as required.

Nice, this looks great!

One concern I have with this update is that syntax highlighting is currently not implemented in MK docs for PYI examples.

Hmm, that is a shame (and might indeed be a blocker here, sadly ☹). Did you find this out from reading the docs, or by experimenting? I can't immediately find anywhere where this is documented :/

This was found with experimentation. Hopefully, the lack of highlighting of .pyi files should be fixed with this PR and a subsequent release of pygments.
I tested this by installing locally with pip install git+https://github.com/calumy/pygments.git@add-pyi-short-name (sorry, I have not had a chance to use UV yet). Then running mkdocs serve -f mkdocs.public.yml and checking one of the updated pyi docs, e.g. http://<IP_ADDRESS>:8000/ruff/rules/unprefixed-type-param/. Which resulted in the following:

Do you know of any other places where .pyi file syntax highlighting is missing that would be a blocker?
Should I draft until the next release of pygments or would you consider pinning to a commit of pygments in the requirements? If so, which requirements file would be best for this, as there appear to be a couple in the docs directory?

Hopefully, the lack of highlighting of .pyi files should be fixed with this PR and a subsequent release of pygments.

Woah, nice! Thanks so much for figuring out the root cause there and filing a PR to solve it — that's awesome 😃
(It's late here so I'll get to your other questions tomorrow :)

https://github.com/pygments/pygments/pull/2773 has been merged and added to the next release milestone. I am unsure of the schedule of the next release of pygments.

pygments/pygments#2773 has been merged and added to the next release milestone.

I saw! I'm currently looking into whether it's feasible for us to pin pygments to a commit on their main branch -- if so, we can land this immediately. If not, we'll need to wait.
If we do need to wait, we should pick up the latest release of pygments in CI as soon as it's released. The depdendency comes from mkdocs-material's pyproject.toml file here: https://github.com/squidfunk/mkdocs-material/blob/6f3c05b6fa7e42279ea7604aedc4e4333131fe57/requirements.txt#L26. And the dependency is permissive enough that it should allow pygments==2.19.0 as soon as it's released.

I think pinning to a main branch commit works -- I pushed the new pins to this branch, so we should be good to go. Thanks again for this -- really great contribution 😃


Implement Offset Commit/Fetch API

This needs to be implemented in protocol.py and in any relevant objects.

[ ] Implement wire protocol in protocol.py
[ ] Add offset commit/fetch functionality to Broker
[ ] Finish SimpleConsumer implementation, Issue #115.
[ ] Add offset commit/fetch to SimpleConsumer

(I'm just adding a librdkafka label for now, because I'll be tracking your design work on a offset fetch/commit api. There's still some work to do on this in python-librdkafka as well, which for now I'll be tracking at https://bitbucket.org/yungchin/python-librdkafka/issue/7 )

In progress here

Implemented all API requests and responses under this section. There are still two response tests that I can't get decent test data for.

Turns out that this is correct and we should clear up the name differences between the "Offset API" and the "Offset Commit/Fetch API". We need one term for committing and fetching actual offsets - for this, I think commit_offset and fetch_offset make sense. We also need a term for fetching earliest and latest offsets - perhaps fetch_offset_range and fetch_offset_bound make sense here.

:+1:

I've added the offset management functionality to the SimpleConsumer and tested it against my local kafka instance. As far as I'm concerned this ticket is done.


Selection Annotation is hard

Link to PDF file (or attach file here):
Mario Mystery.docx (2).pdf
Configuration:

Web browser and its version: Chrome 50.x
Operating system and its version: Mac
PDF.js version: 1.5.222
Is an extension: No

Steps to reproduce the problem:

Select hyperlinks in the document attached

What is the expected behavior? (add screenshot)
It should just select the text
What went wrong? (add screenshot)
It selects the whole page
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Duplicate of #7013?

Closing since this is a duplicate of #7013.


[GO Live][28 July]

Docs Build status updates of commit b098dbf:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a044b73:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/enable-and-configure-your-app-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/assets/images/apps-in-meetings/in-meeting-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/apps-in-meetings/in-meeting-people-card.png
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


DropdownMenu: Cannot read properties of null (reading 'nodeType') (Svelte 5)

Describe the bug
The Bits-UI Dropdown component crashes, in my case using Svelte 5.  The cause seems to be a TypeError relating to this line:
  if (hydrating && hydrate_node.nodeType === 1) {
    element2 = /** @type {Element} */
    hydrate_node;
    hydrate_next();
  }

The Problem is reproduceable in the StackBlitz. I will try to test this in svelte 4 as well!
Reproduction
https://stackblitz.com/edit/github-lahshv?file=src%2Froutes%2F%2Bpage.svelte
Logs
chunk-ZVMKZQ3Q.js?v=a584a1f4:1013 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'nodeType')
    at element (chunk-ZVMKZQ3Q.js?v=a584a1f4:1013:33)
    at bits-ui.js?v=a584a1f4:14870:7
    at chunk-ZVMKZQ3Q.js?v=a584a1f4:399:41
    at update_reaction (chunk-HBONSL6F.js?v=a584a1f4:829:23)
    at update_effect (chunk-HBONSL6F.js?v=a584a1f4:947:21)
    at create_effect (chunk-HBONSL6F.js?v=a584a1f4:1470:7)
    at branch (chunk-HBONSL6F.js?v=a584a1f4:1592:10)
    at chunk-ZVMKZQ3Q.js?v=a584a1f4:399:28
    at update_reaction (chunk-HBONSL6F.js?v=a584a1f4:829:23)
    at update_effect (:5173/node_modules/.vite/deps/chunk-HBONSL6F.js?v=a584a1f4:947:21)TypeError: Cannot read properties of null (reading 'nodeType')
    at element (chunk-ZVMKZQ3Q.js?v=a584a1f4:1013:33)
    at bits-ui.js?v=a584a1f4:14870:7
    at chunk-ZVMKZQ3Q.js?v=a584a1f4:399:41
    at update_reaction (chunk-HBONSL6F.js?v=a584a1f4:829:23)
    at update_effect (chunk-HBONSL6F.js?v=a584a1f4:947:21)
    at create_effect (chunk-HBONSL6F.js?v=a584a1f4:1470:7)
    at branch (chunk-HBONSL6F.js?v=a584a1f4:1592:10)
    at chunk-ZVMKZQ3Q.js?v=a584a1f4:399:28
    at update_reaction (chunk-HBONSL6F.js?v=a584a1f4:829:23)
    at update_effect (chunk-HBONSL6F.js?v=a584a1f4:947:21)

System Info
System:
    OS: macOS 15.0
    CPU: (10) arm64 Apple M1 Max
    Memory: 1.33 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.5.1 - /opt/homebrew/bin/node
    npm: 10.8.2 - ~/VSCode/SONICA/Sonica/front/node_modules/.bin/npm
    bun: 1.1.20 - ~/.bun/bin/bun
  Browsers:
    Chrome: 126.0.6478.183
    Safari: 18.0
    Safari Technology Preview: 18.0
  npmPackages:
    @sveltejs/kit: ^2.5.18 => 2.5.18
    bits-ui: ^0.21.12 => 0.21.12
    svelte: ^5.0.0-next.197 => 5.0.0-next.197

Severity
blocking all usage of bits-ui

Please raise this issue Svelte instead of here. There is nothing we can do in Bits (running Svelte 4) to aid in Svelte 5 issues.

seems to be related to https://github.com/sveltejs/svelte/issues/12601 .
Thanks for clarifying!


code

May I ask when you can upload the code?

Hi, I've just uploaded the code. Thank you for waiting.


New option for fontcustom, versioning changed

I've added an option to set the autowidth property used by fontcustom to automatically trim the icons.
Also; when using middleman 4, this extension gave a dependency error even though it didn't need to (seems to work just fine with the MM beta)

Looks good. Thanks :smile:


Eager loading fix

Added an element query modification to allow eager loading to work with Focus Point.

I am having issues with Eager Loading still. See these posts.
https://github.com/aelvan/Imager-Craft/issues/168#issuecomment-384717517 and
https://github.com/smcyr/Craft-FocusPoint/issues/22
I am still trying to get to the bottom of it and understand exactly what is causing this to fallover, it seems as though it is getting a value from a previous asset or something?
Digging a little deeper into the database, I noticed two rows for the same asset.
10813	1988	31	0.07	0.17	1989	2018-04-26 20:24:39	2018-04-26 20:24:39	6bfbb940-d66e-418d-b211-6dfa6676acd3
5604	1988	9	0.01	-0.04	1989	2018-03-03 13:52:24	2018-03-03 13:52:24	f68806d6-e332-4881-b5ce-014fe2159571
I am wondering if with this fix, it is in-fact getting/selecting the wrong FocusPoint, where it has been used for a different field. Is there a way to extend this to match the right field ID?
I might be wrong in my assumption, but my PHP isn't strong enough to test or resolve.
Thanks.


Fixes #335

-DiskLayout BIOS was exiting with error and failing to complete bcdboot and remainder of script. Added BIOS to if statement. Tested, working.

ping @pronichkin and @mebersol

Talked to @pronichkin via email.  Looks good to him :)


Add sitemap

This PR adds a sitemap.xml file to the website. Resolves #215, contributes to #214.
The SVG files have been formatted because I've added the XML plugin for Prettier.

LGTM. We could submit it to see how it works.


Discussion: Queries on array-indexed objects

This is a follow-up on a brief discussion I had with @mchacki at Distributed Matters conference about particular queries (objects nested in arrays) in conjunction with the upcoming array indexes.
Example document:
{
    "_key": 75,
    "objectName": "GS Kunst 3138",
    "title": "Vuë d´un combat naval",
    "categories": [
        "Grafik",
        "Militaria",
        "Schifffahrt"
    ],
    "administrationName": "Abteilung Tiefdrucke",
    "production": {
        "dateEnd": 1790,
        "dateStart": 1766,
        "period": "2. Hälfte 18. Jh."
    },
    "creator": {
        "name": "Probst, Georg Balthasar"
    },
    "dimensions": [
        {
            "type": "Höhe",
            "part": "Bild",
            "unit": "cm",
            "value": 26.6
        },
        {
            "type": "Breite",
            "part": "Bild",
            "unit": "cm",
            "value": 39.6
        },
        {
            "type": "Höhe",
            "part": "Blatt",
            "unit": "cm",
            "value": 29.6
        },
        {
            "type": "Breite",
            "part": "Blatt",
            "unit": "cm",
            "value": 41
        }
    ],
    "reproduction": {
        "referenceNumber": "33_00009021.jpg"
    },
    "input": {
        "user": "j.doe",
        "date": "2002-10-25"
    }
}

Array index: at least on dimensions[*].type
Desired query: find documents whose height (Höhe) is greater than 40 cm, pseudo query:
dimensions[*].type == "Höhe" AND dimensions.unit[*] == "cm" AND dimensions[*].value > 40

The problem: the following document part matches the value-criterion
        {
            "type": "Breite"
            "part": "Blatt",
            "unit": "cm",
            "value": 41
        }

because value > 40 is true, but it's not of type "Höhe". Another dimension element contains type == "Höhe", hence the document matches. The actual intention of the query is to match all criteria within the same array element / object however, and the example document does not satisfy all 3 conditions in a single dimensions object.
A new keyword could be introduced to tell the query executor to find dimensions.type == "Höhe" using the array index, and then perform additional checks on the matching array elements only:
dimensions[*].type == "Höhe" WHEN dimensions[*].unit == "cm" WHEN dimensions[*].value > 40

Or another crazy idea:
FOR doc IN collection
    WITH doc.dimensions AS d
        FILTER d.type == "Höhe" AND d.unit == "cm" AND d.value > 40
        RETURN doc
    //WITH_END?

AQL doesn't actually support a statement like doc.dimensions[*].type == "Höhe" however, and WITH is ugly (could just use a FOR loop). The following does work in current AQL:
FOR doc IN test
    FOR d IN doc.dimensions
        FILTER d.type == "Höhe" AND d.unit == "cm" AND d.value > 40
        COLLECT a = doc._key INTO b
        RETURN b[0].doc

From 2.7 on, the COLLECT/RETURN hack can be replaced by a simple RETURN DISTINCT doc (DISTINCT prevents a document to be returned multiple times caused by the dimensions FOR loop).
My question: can the array index on .type be utilized in such a query, with a for-loop over the dimensions array?
An alternative way to formulate the query I want (works in 2.7 devel):
FOR doc IN collection
    FILTER LENGTH(doc.dimensions[* FILTER CURRENT.type == "Höhe" AND CURRENT.value > 40])
    RETURN doc

An inline-filter is used, which will only return array elements of the dimensions attribute if all conditions are true. If there's at least one matching dimension, the FILTER criterion will evaluate to true (LENGTH != 0) and return the document - without the need for a loop, COLLECT or RETURN DISTINCT!
It seems way more natural and flexible then the earlier proposed WHEN operator. Question is again, if array indexes can/will be used to make this query efficient.
Furthermore, I wonder if above query could be made faster by explicitly returning 1 inside the inline filter to speed it up (we aren't interested in what CURRENT actually contains) - or is there already an optimizer rule to avoid unnecessary copying of data to the outer FILTER?

As a side note: RETURN DISTINCT doesn't support the expansion operator it seems, but it would actually be quite handy.
FOR doc IN test
    RETURN DISTINCT doc.dimensions[*].type

  [
    "Höhe",
    "Breite",
    "Höhe",
    "Breite"
  ]

vs.
FOR doc IN test
    FOR dimension IN doc.dimensions
        COLLECT type = dimension.type
        RETURN  type

[
  "Breite",
  "Höhe"
]

The RETURN DISTINCT in the last example is not applied on the value doc.dimensions[*].type (so it may be an array with duplicate values), but on the results produced by the FOR loop. So the for loop will not return the same two values.
For example, if there are 4 documents with these values in doc.dimensions[*].type: [ 1, 2, 3 ], [ 1, 1, 2, 3 ], [ 3, 2, 1 ] and [ 1, 2, 3 ], then the FOR loop will produce the following result: [ 1, 2, 3 ], [ 1, 1, 2, 3 ] and [ 3, 2, 1 ]. One element (the last) will get removed because it's identical to the first. The second element will not get modified, even though it contains duplicate elements. This is because of the DISTINCT being applied on the FOR loop level.

You're right, I imagined a single document only. To apply DISTINCT on the values, something like this would be required:
RETURN DISTINCT[*]  doc.dimensions[*].type

http://stackoverflow.com/questions/37029697/query-nested-arrays-in-arangodb/37115219?noredirect=1#comment61989851_37115219 has a similiar topic.

Hi there. This is an old thread but it exactly matches what I'm trying to. The only variation I have is that I'm trying to do this in ArangoSearch. The following example works. It finds a document that has a subarray containing both a given tag_id (123) and value (456). The additional FILTER -- albeit the fastest solution I've found -- doesn't seem optimal:
FOR doc IN page_view SEARCH doc.tags.tag_id == 123 AND doc.tags.values == 456 FILTER LENGTH(doc.tags[* FILTER CURRENT.tag_id == 123 AND CURRENT.values ANY == 456]) RETURN doc
Is there, or could there be, a better way to SEARCH by two attributes in the same subarray, without resorting to FILTERing? Thanks.

CC @gnusi @Dronplane

Related: #10583 #10847

@gghdev we plan to add a functionality to allow efficient search within sub-objects, but unfortunately there is not ETA atm.


fix xorm models with wrong name, using mapping name

Problem: starting up the app, and test using the default example, got error "Error 1054: Unknown column 'i_d' in 'field list'"
Cause: bussiness_group.go struct "BusinessGroup", it's ID field with the wrong name, xorm uses SnakeMapper defaultly, So the name converted into 'i_d'
Reference: https://lunny.gitbooks.io/xorm-manual-zh-cn/content/chapter-02/3.tags.html

tks

Problem: starting up the app, and test using the default example, got error "Error 1054: Unknown column 'i_d' in 'field list'"
Cause: bussiness_group.go struct "BusinessGroup", it's ID field with the wrong name, xorm uses SnakeMapper defaultly, So the name converted into 'i_d'
Reference: https://lunny.gitbooks.io/xorm-manual-zh-cn/content/chapter-02/3.tags.html

tks


seg fault instantiating image io

I started with a fresh ubuntu 22.04 system and installed python 3.10.12 and then ran pip install itk-ioomezarrngff but I get a seg fault when I try to use it.
$ python
Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import itk
>>> iio = itk.OMEZarrNGFFImageIO.New()
Segmentation fault

I also tried in google colab, and there it crashes the notebook kernel:
https://colab.research.google.com/drive/11B3OUETuDJ_HmFlYqOc8LBMLPpKScTwN?usp=sharing

@pieper fix in progress in #63

Thanks @thewtex !

@pieper new package uploaded. Please give it a try. Note that you should also be able to use itk.imread and itk.imwrite.

Great - works now!


collector-http connection error log is too verbose

When upstream server is causing client errors on c.client.Do, HTTPCollector logs an error on every request that fails.
To my opinion this is too verbose. The client may have a state and can log only when the state changes.
This is clear enough and don't cause log spamming when upstream server is in error state.
Please give your opinion on this.
Cheers

@posener wingtips from nike (@nicmunroe) has an interesting approach, which is to log error on interval with a sample of the error. For example, instead of logging a variable rate, budget for one log message per minute. This would keep the logs from getting full, but still allow someone to know the status. This is a variant on the "log once" pattern, except takes into account that the backend can resolve at some point.

Thanks, I must say I prefer the log once every state change approach: it will log when the backend fails, but it will also log when the state goes from error to passing. you don't actually need more than that.

ack. was just food for thought

I prefer a solution where we have a rate limit on the amount of same log errors (interval based de-duping with an occurrence counter for each time window).
For now I'll keep as is and wait for this to become a more popular topic.

closing due to no traffic.


Update Github sponsor text and logos

Also enhance the code to automatically update the README.
Rendered view: https://github.com/jonchang/brew/blob/enhance-sponsors/README.md#sponsors

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?
[x] Have you successfully run brew man locally and committed any changes?

Review period will end on 2021-02-16 at 02:46:44 UTC.

Review period ended.

@jonchang Any thoughts on my comments?

Opened https://github.com/Homebrew/brew/pull/10643 to tweak these.

What would you think about having the maintainers update be part of this scheduled job too?

I thought these were in a scheduled job but they aren't (yet). That'd be a good thing, though.


Feat/guidelines

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

36 of 36 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 99.074%

Totals

Change from base Build<PHONE_NUMBER>3:
-0.02%

Covered Lines:
4931

Relevant Lines:
4953

💛  - Coveralls


how to train on non instruction dataset .

basically i want to train on github repos that are not in question and answer type dataset but just simple python or any other language code . how to train on this this kind of data?  @Carolinabanana @William-Wildridge @shaper @Qubitium @bet0x @sebdg

Just feed it to the trainer but don't apply the instruction template.

ok thanks

Hello @hemangjoshi37a, you can keep the dataframe.instructions = NULL, it will work fine. Instructions are not necessary in the dataframe.

We have a generic text completion notebook for just text data on our Github page!

https://colab.research.google.com/drive/1ef-tab5bhkvWmBOObepl1WgJvfvSzn5Q?usp=sharing

thank you so much for helping out . but do you think the text completion type trained model would work for the instruction type inference ? Do I need to create a instruction type dataset compulsorily for this or text completion would work by giving appropriate prompt for getting output like a QnA ?

The notebook you sent is good for story kind of text for text completion but how to use that in code? i mean in code you have to have a instruction type dataset and model.