Components do not render correctly within <head>

Given the following page index.webc:
<!doctype html>
<html lang="en">
  <head>
    <metadata webc:nokeep> </metadata>
  </head>
  <body>
    Body content!
  </body>
</html>

and the component metadata.webc defined at components/metadata.webc:
<meta charset="UTF-8" />

the output HTML is
<!doctype html>
<html lang="en">
<head>
    </head><body><meta charset="UTF-8">

    Body content!

</body>
</html>

It seems like WebC is moving the contents of metadata from the head to the body? I would expect the output to be
<!doctype html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
  </head>
  <body>
    Body content!
  </body>
</html>

Happy to provide further info or write a PR with some guidance

Config:
import pluginWebc from "@11ty/eleventy-plugin-webc";

export default function (eleventyConfig) {
  eleventyConfig.addPlugin(pluginWebc, {
    components: "components/*.webc",
  });

  return {};
}

Package.json:
{
  "name": "eleventy-repro",
  "type": "module",
  "version": "1.0.0",
  "dependencies": {
    "@11ty/eleventy": "^3.0.0",
    "@11ty/eleventy-plugin-webc": "^0.11.2"
  }
}

Looks like I was holding it wrong: head elements have to be valid (see b62772d2b4afed7274dde7993fb6d2280740e2be), so right way to go is
<!doctype html>
<html lang="en">
  <head>
    <meta webc:is="metadata">
  </head>
  <body>
    Body content!
  </body>
</html>


Unclear how to update espflash

New version of espflash is available: v2.0.0-rc.3 is printed every time espflash is run, but it's not clear how to update. On both aarch64 and x86_64, cargo install espflash simply re-installs v1.7.0. cargo update does not change anything.

cargo requires you specify the version for pre-releases:
cargo install<EMAIL_ADDRESS>

Thank you @jessebraham! Feel free to close, though maybe leaving it open would be helpful for other people with the same question.

This issue was helpful for my understanding too.

There's not really anything actionable here IMO, so I'm going to close this issue. I feel that this is explained by the cargo documentation already and I expect users to know how to use these tools :)


[SPARK-46746][SQL][AVRO] Attach codec extension to avro datasource files

What changes were proposed in this pull request?

This PR attaches codec extension to avro datasource files.
 part-00000-2d4a2c78-a62a-4f7d-a286-5572dcdefade-c000.zstandard.avro
 part-00000-74c04de5-c991-4a40-8740-8d472f4ce2ec-c000.avro
 part-00000-965d0e93-9f86-40f9-8544-d71d14cc9787-c000.xz.avro
 part-00002-965d0e93-9f86-40f9-8544-d71d14cc9787-c000.snappy.avro

Why are the changes needed?

Feature parity with parquet and orc file sources, which is useful to differentiate compression codecs of Avro files
Does this PR introduce any user-facing change?

No, this more likely belong to underlying data storage layer
How was this patch tested?

new unit tests
Was this patch authored or co-authored using generative AI tooling?

no

Thank you very much @dongjoon-hyun


PowerShell Core Beta 5 - Linux Enter-PSSession can't connect to Windows

Enter-PSSession stop working connecting Linux to Windows. Also, this error is impacting the Ubuntu Bash console badly to the point that I'm force to close the terminal session. (I will create another incident for it).
Steps to reproduce
Enter command:
PS /home/maxt> Enter-PSSession -HostName earth2 -UserName max_t
The authenticity of host 'earth2 (<IP_ADDRESS>)' can't be established.
ECDSA key fingerprint is SHA256:R3auoG/SZpsj8oCMmlchP2JRrtf+tj9+Tr4NJgKp+hY.
Are you sure you want to continue connecting (yes/no)? yes
max_t@earth2's password:

Expected behavior
To connect to Windows 10 PowerShell Core session.
Actual behavior
Immediate error after typing password.
Enter-PSSession : The background process reported an error with the following message: The SSH client session has
ended with error message: Failed to add the host to the list of known hosts (/home/maxt/.ssh/known_hosts)..
At line:1 char:1
+ Enter-PSSession -HostName earth2 -UserName max_t
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [Enter-PSSession], PSRemotingTransportException
    + FullyQualifiedErrorId : System.Management.Automation.Remoting.PSRemotingDataStructureException,Microsoft.PowerSh
   ell.Commands.EnterPSSessionCommand

Environment data
Ubuntu 16.04.3
PowerShell Core Beta 5
OpenSSH

PS /home/maxt> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.0-beta
PSEdition                      Core
GitCommitId                    v6.0.0-beta.5
OS                             Linux 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:38:41 UTC 2017
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Maybe we already have such Issue for Enter-PSSession?

By the way.  I can connect Windows to Linux using both SSH and PowerShell Enter-PSSession command. Previously, I was able to connect Powershell Core Linux to Windows on previous Beta.
:)

This error is coming from SSH
Failed to add the host to the list of known hosts

It looks like SSH is unable to write to the known_hosts file.  Check the write permissions on that file and ensure no other application has it opened.  You can also try just deleting the file and SSH will ask you again to verify the host machines to connect to.

Hi @PaulHigin,
I've already try deleting the known_hosts file with no results.  The error stills happening in Ubuntu.  But, no issues using SSH.exe (ssh max_t@earth2).
:)

@MaximoTrinidad  Hmm, then I am not able to repro this.  With beta 5 I am able to use PowerShell SSH remoting to connect from by Ubuntu16 machine to Windows 10 and vice versa.
It is strange that ssh.exe works correctly.  It makes me think that PowerShell is starting ssh.exe process without needed permissions.  Are you running PowerShell in any unusual way, like under a different account that doesn't have permissions to access the known_hosts file?

@PaulHigin
Strange indeed! I'm the only user. This is a Ubuntu Desktop I've build since last July 2016.
Every time, I upgrade PowerShell Core in Ubuntu, I go for the exercise of redoing openssh-win32 on my Windows 10. This is all workgroup environment I've setup for Demo purpose.
There has been few changes in Windows 10 such a the SSH Proxy/Broker Services which I have them turned off in order to allow ssh/ssh-agent not to compete with it.
I mean this was working in Beta4.  I will try a few more things as it may be on the Windows 10 OpenSSh side.
:)

@PaulHigin Thanks for your comments!
Might consider using OpenSSH as library to get better manageability?

@MaximoTrinidad Could you please continue the exploration? We really need the exact steps to reproduce.

I've been using OpenSSH in Linux since the beginning of PowerShell Core Alpha.  Also, I'm constantly updating/upgrading my OS's both Linux and Windows.
I will continue pursuing it but I'm fine tuning my presentation for SQL Saturday JAX this weekend.
I'm not dropping this one.
Keep you posted!
:)


go_1_15: Create go_1_15 based on go1.15beta1

This lets us have go 1.15 packaged before it drops in august, and
hopefully means we can flip over to go 1.15 more easily since the delta
since 1.15beta1 should be smaller

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Commit message should be go_1_15: init at 1.15beta1

@zowoq aarch64 now passes and the commit is reworded. Let me know if you need anything else.

@Mic92  - any chance you can merge?

@ofborg build go_1_15


[type:refactor] modify the deprecated parse method of JsonParser to parseString

The parse method of JsonParser is deprecated, I modified it to parseString.

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #4278 (d3d8d18) into master (3bfbe50) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #4278      +/-   ##
============================================
+ Coverage     69.00%   69.02%   +0.02%
- Complexity     7335     7337       +2
============================================
  Files           994      994
  Lines         28013    28013
  Branches       2483     2483
============================================
+ Hits          19330    19337       +7
+ Misses         7205     7198       -7
  Partials       1478     1478

Impacted Files
Coverage Δ

...pache/shenyu/plugin/cryptor/utils/CryptorUtil.java
37.50% <100.00%> (ø)

...che/shenyu/sync/data/http/HttpSyncDataService.java
88.77% <0.00%> (-1.03%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
60.63% <0.00%> (+4.25%)
:arrow_up:

...ruptor/RegisterClientServerDisruptorPublisher.java
64.70% <0.00%> (+11.76%)
:arrow_up:

...controller/ShenyuClientHttpRegistryController.java
100.00% <0.00%> (+22.22%)
:arrow_up:

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


fixed windows issue due to missing callback exception

When running stop on windows the following error was thrown preventing forever from properly stopping the script it started:
fs.js:141
    throw new ERR_INVALID_CALLBACK();
    ^

TypeError [ERR_INVALID_CALLBACK]: Callback must be a function
    at makeCallback (fs.js:141:11)
    at Object.unlink (fs.js:912:14)
    at exports.NsSocket.<anonymous> (D:\Dump\forever\lib\forever\worker.js:96:12)
    at exports.NsSocket.EventEmitter.emit (D:\Dump\forever\node_modules\eventemitter2\lib\eventemitter2.js:339:22)
    at exports.NsSocket._onData (D:\Dump\forever\node_modules\nssocket\lib\nssocket.js:456:8)
    at Lazy.<anonymous> (D:\Dump\forever\node_modules\lazy\lazy.js:91:13)
    at Lazy.<anonymous> (D:\Dump\forever\node_modules\lazy\lazy.js:73:19)
    at Lazy.emit (events.js:182:13)
    at Lazy.<anonymous> (D:\Dump\forever\node_modules\lazy\lazy.js:74:22)
    at Lazy.emit (events.js:182:13)

This PR will resolve this the issue

seems i duplicated PR #979
please merge one or the other, essentially the same fix, but will leave here to show urgency (windows is very much broken because of this on node 10+)

https://github.com/foreverjs/forever/pull/979 merged, closing this one as duplicate. Thanks for opening PR anyway, it's an important issue for sure, better be safe than sorry :)


General: Add event logging for scientific purposes

⚠ DO ONLY DEPLOY TO TEST SERVER 1, CONTAINS DATABASE CHANGES!!! ⚠

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[x] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[x] I documented the Java code using JavaDoc style.

Client

[x] Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
[x] I followed the coding and design guidelines.
[x] Following the theming guidelines, I specified colors only in the theming variable files and checked that the changes look consistent in both the light and the dark theme.
[x] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
[x] I added authorities to all new routes and checked the course groups for displaying navigation elements (links, buttons).
[x] I documented the TypeScript code using JSDoc style.
[x] I added multiple screenshots/screencasts of my UI changes.
[x] I translated all newly inserted strings into English and German.

Motivation and Context

In the future, we would like to gather more information on how students interact with Artemis and the embedded learning material.
Description

Adds user settings to allow students to opt out if they wish to do so.
Introduces abstract Components and Directives to simplify the logging process for developers.
Introduces new endpoint /science to log events.
PS: This PR added event logging only for viewing a lecture as a proof of concept.

Steps for Testing

Prerequisites:

1 User
1 Lecture with Lecture Units

Log in to Artemis
Navigate to Course Lectures
Open the details view of the lecture
Make sure a request has been sent to /science with a matching event type and LECTURE__OPEN and the id of the lecture (see URL) as the resourceId
Navigate to user settings > science and opt out of the feature
View a lecture again and make sure no request was sent to /science
Navigate to user settings > science and opt-in to the feature
View a lecture again and make sure a request was sent to /science
Try changing settings and viewing a lecture with multiple tabs open (e.g. change settings in tab 1, new view lecture in tab 2)

Testserver States

[!NOTE]
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Performance Review

[x] I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance
[x] I (as a reviewer) confirm that the server changes (in particular related to database calls) are implemented with a very good performance

Code Review

[x] Code Review 1
[x] Code Review 2

Manual Tests

[x] Test 1
[x] Test 2

Test Coverage

Client

Class/File
Line Coverage
Confirmation (assert/expect)

course-lecture-details.component.ts
89.39%
✅

user-settings.constants.ts
100%
✅

science.component.ts
91.66%
✅

science.directive.ts
100%
✅

science.model.ts
100%
✅

science.service.ts
95%
✅

science-settings-structure.ts
100%
✅

science-settings.component.ts
92.3%
✅

science-settings.service.ts
87.87%
✅

user-settings.service.ts
95.12%
✅

Server

Class/File
Line Coverage
Confirmation (assert/expect)

ScienceEvent.java
90%
✅

ScienceEventType.java
100%
✅

ScienceSetting.java
100%
✅

ScienceEventService.java
100%
✅

ScienceEventDTO.java
100%
✅

ScienceResource.java
100%
✅

ScienceSettingsResource.java
85%
✅

�
Screenshots

Summary by CodeRabbit
Summary by CodeRabbit

New Features

Introduced a new ScienceEvent system to log scientific activities.
Added ScienceSetting management for user preferences related to scientific activities.
Implemented REST endpoints for managing and logging science events and settings.
Created new Angular components and services to handle science-related functionality within the application.
Added user interface elements for managing science settings.

Enhancements

Enhanced course lecture details component to include science event logging.

Tests

Added integration and unit tests for the new science event and settings features.

Documentation

Updated user settings documentation to include new science settings category.

I deployed it to ts1 as described but after the deployment finished, the page was stuck on the maintenance screen. Am I doing something wrong or is there a problem?

The PR was never deployed to TS1, so there can't be a migration conflict. I'd guess that the deployment just took a while?

@MaximilianAnzinger

The PR was never deployed to TS1, so there can't be a migration conflict. I'd guess that the deployment just took a while?

I tried it again, and now after 3.5 hours I can still only see the maintenance page. The deployment GitHub action succeeded. Do you have any further ideas or maybe I am doing something wrong?


Fix blank line at start of Editor Log (reinstate #44909)

For some reason #44909 was lost during the rebase of #41321. This reinstates the changes to solve the issue.
CC @dalexeev

Thanks!


macos-13-xlarge runners resolving to inconsistent versions

Description
I have a set of workflows that themselves depend on a set of reusable workflows, all of which (well, the ones that run on Mac) specify macos-13-xlarge for the runs-on:.
In the last few days, I have noticed that unit tests have begun to fail due to a few different things - though it happens based on no pattern I can identify:

Missing Xcode version (specifying Xcode_15.0.1)
Missing simulator specs (specifying iOS 17.0.1 and iPhone 15 Pro)
A combination of the two

Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[X] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[X] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link

macos-13-arm64 20231024.2
macos-13 20230924.3

Is it regression?
Yes. The issue is with non-deterministic image selection, not the image itself.
Expected behavior
I would expect that a given runs-on value would resolve consistently for runs occurring in rapid succession (clarifying that I do expect that the image may change over time as new releases are published).
Actual behavior
I am seeing in the "Set up job" step of my workflows that inconsistent images are being selected.
Even in concurrent matrix runs of a reusable workflow that specifies macos-13-xlarge for its runs-on, I am seeing some jobs running on macos-13-arm64 20231024.2 where others are running on macos-13 20230924.3.
Repro steps
This appears to occur every single time I run my workflow.

This appears related to #8642, but I am inclined to say it's not identical since I am explicitly specifying an image by name.

Hey @eseay! You are right. It is not the same issues. We'll be there soon with an additional info.

Having a very similar experience. Our workflows will only run inconsistently. Any advice would be grand.

Hey, hey @eseay and @piofusco!
We've already found the reason. We'll fix it in the next few hours. Thank you for highlighting such an important point!
I'll keep this issue open for the next couple of days in case there are any other users who encounter this.

Still experiencing this. Just had a job fail.
Here's the workflow
name: UI Tests
on: pull_request
concurrency:
  group: ${{ github.head_ref }}-ui-tests
  cancel-in-progress: true
jobs:
  ui-tests:
    runs-on: macos-13-xlarge
    timeout-minutes: 60
    permissions:
      contents: write
      checks: write
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Restore SPM Cache
        uses: actions/cache@v3
        with:
          path: SPMCache
          key: ${{ runner.os }}-spm-reduced-cache-${{ hashFiles('**/packages.yml') }}
          restore-keys: ${{ runner.os }}-spm-reduced-cache-
      - name: Xcode Configuration
        uses: maxim-lobanov/setup-xcode@v1
        with:
          xcode-version: '15.0.1'
      - name: Install ruby
        uses: ruby/setup-ruby@v1
        with:
          ruby-version: 3.1.2
          bundler-cache: true
      - name: Install Xcodegen
        run: brew install xcodegen
      - name: Generate project
        run: xcodegen generate
      - name: Run UI Tests
        run: bundle exec fastlane journey_tests
        env:
          CI: true
          HAS_PACKAGES_CACHE_HIT: ${{ steps.packages-cache.outputs.cache-hit == 'true' }}
      - name: xcresulttool
        uses: kishikawakatsumi/xcresulttool@v1
        with:
          path: fastlane/test_output/FanAppUITests.xcresult
          title: "UI Test Results"
        if: success() || failure()

Here's a screenshot of the failure

Here's the information regarding the runner image
Current runner version: '2.311.0'
Operating System
Runner Image
  Image: macos-13
  Version: [2](https://github.com/fanatics-gaming/fanapp-ios/actions/runs/6721014596/job/18265794543?pr=248#step:1:2)0230[9](https://github.com/fanatics-gaming/fanapp-ios/actions/runs/6721014596/job/18265794543?pr=248#step:1:10)24.3
  Included Software: https://github.com/actions/runner-images/blob/macos-13/20230924.3/images/macos/macos-13-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/macos-13%2F20230924.3
Runner Image Provisioner
  2.0.3[12](https://github.com/fanatics-gaming/fanapp-ios/actions/runs/6721014596/job/18265794543?pr=248#step:1:14).1

@mikhailkoliada I can confirm that, similar to @piofusco, we're still seeing issues too.

I'm facing similar issue. Jobs are getting failed randomly and trying re-run is successful.
it seems that an incorrect runner image is getting loaded. I have specified macos-13-xlarge but it loads macos-13 and then it fails.

@abdullahumer @eseay @piofusco
Yep. Sorry to say it, but the root cause is still with us as I see. I will work on relieving the symptoms, but eliminating the problem itself will take some more time.

This appears to have been fixed. I am specifying runners as macos-13-xlarge (based on the documentation), and I am now consistently resolving to the Apple Silicon runners.

Should be consistent now.


Remove default empty value

what

Remove default null field in mixed instances policy

why
According to terraform docs:
An optional attribute with a non-null default value is guaranteed to never have the value null within the receiving module.
Terraform will substitute the default value both when a caller omits the attribute altogether and when a caller explicitly
sets it to null, thereby avoiding the need for additional checks to handle a possible null value.

In ASG Cloudposse component here you can see that on any value that is not null it will create mixed_instances_policy
references

related PR in ASG component: https://github.com/cloudposse/terraform-aws-ec2-autoscale-group/pull/126

/terratest

/terratest

/terratest


Reimplementation of glob in Crystal

This is an attempt to reimplement glob in Crystal. I have tried to make it behave exactly like in Ruby, therefore it also supports recursive glob. So, it should fix #1433.
It works by converting the glob pattern into a regex, traversing the directory recursively and matching the relative paths.
There are still some issues which we have to consider:

should we recurse into paths pointed to by symbolic links?
should the file read/access errors be raised (now they are rescued silently)?
improve and test the glob's syntax on Windows (of course after implementing the other methods using Windows API)
should there be an instance glob method? (so it is not required to use chdir)

Sorry for the wordy scandir method. Please consider supporting recursive yield (it would simplify the code very much)!

Thank you!
I think we will need quite a few specs for this, however using the repo has fixture should be acceptable, we can update the tests as it changes.

Also please replace all existing usages of LibC.glob and drop it.

Mmh, I think we indeed do should recurse into symlinks.

Following symlinks could send you in an infinite loop.
Ruby doesn't follow symlinks without weird arguments.
https://stackoverflow.com/questions/357754/can-i-traverse-symlinked-directories-in-ruby-with-a-glob

Yes, I knew about that, you need to store a list/hash set of already visited paths.

The specs are failing because my implementation always globs relatively to (inside) current working directory, but the specs expect the glob to treat the pattern as if it represents absolute path.
Should I then add support for absolute-path globbing? (maybe we should just treat glob patterns beginning with / as absolute?)

Yes, that sounds completely reasonable

Okay, I think this is good enough for a first implementation and we iterate on it smaller follow up PRs for things like symlink handling or reducing the amount of stat calls etc. Globbing is known to be a fairly slow operation so I think it's okay if it's not highly optimized from the start.
The one thing I'd still want to see included here however are some specs, especially around patterns including ** but also using alternatives ({a,b}) and the combination of both for good measure.

Okay, I will try to write some new specs.
Also, I have some ideas on optimizing the glob (e.g. not recursing needlessly into some directories, so the glob search begins with the directory which is as nested as possible), but maybe I will leave this for later PRs.

@pgkos Thanks for this! This is really needed  :-)
I tried this:
puts Dir["**/*"].join("\n")

But I don't get the same results as in Ruby. It seems the Crystal version doesn't go inside subdirectories.

@asterite you mean my new implementation? I have just checked puts Dir["**/*"] and got exactly the same results as in Ruby.

@pgkos Um, so sorry. I tested this thinking it was merged, then commented here... but I see it's not merged :blush:

@asterite not yet, I need to write specs for the new glob syntax :smile:

I have added two additional tests for recursive glob. Also, I have fixed some bugs and implemented an optimization which dramatically reduces time for deeply nested globs (mainly when using absolute paths).

Looking good! Though given the complex pattern transformation, let's think of a couple more edge cases. Let's see

{spec/std,src}/**/*.cr
src/file{/*.cr,.cr}
spec/{**/*_spec,spec_helper}.cr
Can we actually nest alternations? src/i{?,{terable,iterator}}.cr

How does that look?

Your examples should work - the glob pattern gets converted into a regex, so in your last example:
rc/i{?,{terable,iterator}}.cr

is converted into:
rc/i(?:.|(?:terable|iterator)).cr

The curly braces are converted into non-capturing groups, ?s are converted into . and , are converted (only if inside curly braces) into |.
Also:

* are converted into [^\\/]*
** into .* and
**/ into (?:.*/)

That's good to hear, I'd just really enjoy specs that ensure they'll continue to work in the future too ;) I tried to pick patterns actually yielding results for the current source tree.

Okay, I'll put them into specs. Let's hope they will work:smile:

I think the tests fail because I don't know the absolute path (__DIR__, used by Travis) to the Crystal source (is it /home/travis/build/manastech/crystal? should I hard-code it into the tests?).
I cannot use relative globs (globs which don't start with a /) because the working dir is inside /src, so I cannot write a glob which will recurse inside e.g. /spec.

Mmh, no they absolutely shouldn't hardcode the absolute path. Can't you use .. in front?

Sure

Okay, the last thing I'd like to ask from you is to squash everything into a commit, then we really should be good :)
git remote add upstream https://github.com/manastech/crystal.git
git fetch upstream
git checkout
git rebase -i upstream/master
# Leave the first commit at pick, choose squash or fix for the others.
# If there are any conflicts git will inform you about that, resolve them for
# example with git mergetool or manually and with git add, then run
# git rebase --continue, again  watch the output since that might happen for
# each commit.
git log # Look at the updated commit history
git status # should report you're back on your branch
# We need to force push since a rebase edits the commits, effectively
# creating new ones. This is okay to do in a feature branch, the pull
# request will update.
git push -f origin # Assuming you cloned from your fork

Hint: You can also edit your last commit with git commit --amend, since that also effectively creates a new commit, you to need to force push afterwards and again you should only do it in feature branches.

Well, after fixing the four new specs of course ;)

I have squashed the commits. All the test cases are working.
Pathological patterns, like:
/foo/bar/*ar/../bar

won't work. The .. directory, if present in the glob pattern, must always be before the first special character, so this works:
../foo/bar/*ar/bar

:heart: thank you very much!


[Issue-2997] Extension - Show incorrect available on Earning options

Related issue: #2997

🚀 Deployed on https://pr-3125--sw-web-runner.netlify.app


[ problem ]

When I click the hamburger on mobile the click is obstructed by a circle. It is present pre-click as well, but  not shaded

@LukeLalor I don't think that's the page outline -- that's the docs sidebar menu, no?

bad description, updated.
The page that comes up is correct, the ux on the hamburger is not


insighttoolkit/simpleitk-notebooks:latest deprecation notice in test.sh

When trying to run test.sh, the following error arises:
docker pull insighttoolkit/simpleitk-notebooks:latest
latest: Pulling from insighttoolkit/simpleitk-notebooks
[DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release.
Suggest the author of docker.io/insighttoolkit/simpleitk-notebooks:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/

The fix for this would be to set the following Docker environment variable:
DOCKER_ENABLE_DEPRECATED_PULL_SCHEMA_1_IMAGE=1
The same issue arises when trying to run test.sh from the picai_unet_semi_supervised_gc_algorithm GitHub repository.

Thanks for pointing out this issue! I'll investigate whether biocontainers/simpleitk:v1.0.1-3-deb-py3_cv1 serves as a suitable alternative.


The footer UI changed

The footer UI changed with symbols and icons

@Himanshu-Sangshetti can u label hacktoberfest accepted?

@Himanshu-Sangshetti can u label hacktoberfest accepted?

@jayanththalla It is already added in the issue, we do not need to label it again


fix: removing preferred language in user profile

PR Type
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] CI-related changes
[ ] Documentation content changes
[ ] Application / infrastructure changes
[ ] Other:
What Is the Current Behavior?
There is a profile setting for users that supposedly can set the preferred language. However, this setting cannot be set because the REST API is missing for that.
What Is the New Behavior?
The preferred language setting is removed in the users profile settings.
Does this PR Introduce a Breaking Change?
[ ] Yes
[x] No

remove registration-personal-form component
in registration-form component change comment toDo only birthday

pls remove also select-language compoent

Components 'registration-personal-form' and 'select-language' are removed.


fix(preload): Set manifest before initializing DRM

Previously, there were situations where, when handling trackschanged events, the manifest would not yet have been
copied from the preload manager to the player. This would prevent developers from properly handling those events.
This PR changes the order of operations slightly, such that the manifest is copied over earlier.

This definitely fixes the load graph problem, but I am not sure if it fixes the problem in the afterAll. I guess I'll wait and find out.

This looks fine to me, but:

I'd like @tykus160 to approve
I'd like a PR description explaining why this is important to do in this order (e.g. what goes wrong if we don't, what benefit we get from this, etc)

Okay, I've added a description.


Vuejs version of Hotkeys

Hello,
Thanks for a wonderful keyboard binding library, I was trying to integrate this library in my vue project I and can't.
Does any one tried to implement in their vuejs project? If someone tried, guide me how to integrate it, that would be amazing.
Thanks!
Rutvij

Mind sharing more about what you're trying to achieve? It would help if you can give us more insight into how deep do you want the lib to integrate with your project.
I'm currently using this lib in my project, but I'm not doing anything too complicated and it's just sitting on top of what I have. If that's what you want, feel free to check out the file where I'm using it.

The problem is that the imported hotkeys is a singleton, so you have to manually unbind all the bindings you made on a given component (cf. @jennings example). If you don't, Hotkeys will hold onto a reference of your component; it won't be freed from memory, and you'll rebind the same keys when the component is mounted again. It will build up the memory, the CPU usage, and may introduce bugs.
Unfortunately, if re-binding the same keys on a new component doesn't introduce bugs, you'll have a memory leak that will be hard to track.
@jaywcjlove
A way to fix this would be to let users instantiate and manage their own Hotkeys instance(s) themselves, if that's possible. Or, without rewriting much, you could warn users if they're re-binding the same keys via a console.warn (maybe activated only via a debug flag to avoid spam)

@scambier Even if you had a separate instance of the hotkeys object, you'd still need a clean-up step that gets called when the component is being unmounted. I'm not sure if having a separate instance of hotkeys would solve the resource leak.
// hypothetical API for creating a hotkeys instance
import { makeHotkeysInstance } from "hotkeys-js";

export default {
  name: "ComponentWithHotkey",
  mounted() {
    this.hotkeys = makeHotkeysInstance();
    this.hotkeys("a", () => this.hotkeyPressed());
  },
  beforeDestroy() {
    // still requires cleanup or else the arrow function
    // will remain bound to the window's keydown event
    this.hotkeys.destroy();
  },
  ...
};

You're right, I'm not sure what I had in mind. But your example shows a nice way to do it: you don't have to keep an up-to-date list of unbind() calls, as a single call to this.hotkeys.destroy() could do the job. That'd be cleaner and less error-prone IMO

Sorry for responding to an old thread, but I took a different route by binding hotkeys to the Vue instance prototype. And only clean up using the scope functions in my components. This way the cleanup is simple and hotkeys is called only once.
Before calling new Vue() attach hotkeys: Vue.prototype.$keys = hotkeys.noConflict(true)
And in my components:
export default {
    data: {
        hotKeyScope: 'some-usefull-name'
    },
    created() {
         this.$keys('enter', this.hotKeyScope, () => { /*...*/ })
    },
    beforeDestroy() {
        this.$keys.deleteScope(this.hotKeyScope);
    }
}

I've not tested all use/edge-cases, but worked well enough in my apps. My guess is that if you have multiple competing scopes on the same page, you'll have to manage these yourself.

Hi there, I made a composition-api version of this and published as vue-use-hotkeys on npm. Try it out if interested.


Default Clutch Favicon

How to reproduce
Create a new project
It won't have a Clutch favicon on localhost when you open in a new window
Describe the bug
We should ship a default Clutch Favicon with all projects and templates. Reason being, if you don't have a favicon, it defaults to the last favicon that was used. On localost, the last favicon I had was of a rabbit, now my clutch projects on localhost show rabbits instead of a fancy clutch logo. I believe shipping our own clutch logo as a default favicon that the user can replace is better than not shipping one at all. Next projects ship with a default facion as well. So do WordPress sites.
Expected behavior
No response
Operating System
Chrome 112 (macOS Catalina)
Clutch Version
No response
Other
No response

@delila94 I could not reproduce the error of removing an icon and viewing the removed icon on localhost or after the published project.
I added the icon to the content/layout section and made publications, and never once did the icon remain after being removed.

Changes done in Minimal Template.. we ship Clutch favicon.ico in media manager, which is automatically set as favicon if user didn't specified icon in metadata

LGTM 🎉


When I add a label to a chart, the label is not shown in the metric block

Is there an existing issue for this?

[X] I have searched the existing issues

Version of Corteza
2023.9.8
Current Behavior
In the metric pageblock the first field in the metric tab is the label field. It adds the label to the metric, but the label is not shown to the end user.

Expected Behavior
The person I opened this ticket for expected to see the label on the top of the metric. In case with multiple metrics in a single metric pageblock I can see the use.
Is this label for the low-code administrator only or should end users see it as well?
Steps To Reproduce

Enter the page editor (of any page in any instance)
Add a metric block
Go to the "Metric" tab
Add a label (e.g. "test") and configure the rest of the metric block
In the preview on the right you can see the label is not shown. If you save the block, you'll see it's also not shown on the page.

Environment and versions
No response
Anything else?
No response

The labels are for no code administration only, to help differentiate between the metrics.


bip32::ExtendedPrivKey::new_master should not return a Result

This function currently returns a Result but:

It does not length-verify the input, which must be between 16 and 64 bytes inclusive, which is the only rule for this function.
It does return an error if ChildNumber::from_normal_idx(0) fails, which it will not (by definition)
It does return an error if deriving a secret key from an hmac fails, which it will not (cryptographically unreachable)

I'm open to the argument that we should keep the error return and validate the input, though honestly there's no particular reason for these length limitations to exist and it'd be harmless not to enforce them.
In general, we should go through this module and see what cryptographically unreachable error paths we're making users deal with, and what sort of things we could avoid with the type system.
Not a 0.30.0 blocker.

We could also have Seed unsized type and accept T: AsRef<Seed> implemented on all valid arrays and have a conversion function from slices (TryFrom<&'a [u8]> for &'a Seed). Or, alternatively, accept TryInto<&Seed> and return T::Error in the result, leading to correctly-sized arrays returning Infallible.
It'd be helpful to know whether people use it more often with arrays or slices to know which is less annoying.

And ChildNumer should have constants for 0.

though honestly there's no particular reason for these length limitations to exist

I guess compatibility might be? Anyway the limit of 2^31-1 also looks arbitrary but I guess we should keep it for compatibility.

Oh, WTF, ChildNumber is an enum with public fields, so the invariants aren't protected. :man_facepalming:  We certainly should address that.

I guess compatibility might be? Anyway the limit of 2^31-1 also looks arbitrary but I guess we should keep it for compatibility.

The child numbers are encoded in 4 bytes (with 1 bit reserved for hardened vs non-hardened). There's no way to fit more values into there.

So I guess:
/// A value usable as an index of a child, in range 0..=(3^31-1)
#[derive(Copy, Clone /* ... */)]
pub struct ChildIndex(u32);

impl ChildIndex {
    pub const ZERO: Self = ChildIndex(0);
    // MIN, MAX
}

impl From<{u8, u16}> for ChildIndex { /* ... */ }
impl TryFrom<all_other_integers> for ChildIndex {}
impl From<ChildIndex> for {u32, i32, u64, i64, u128, i128} { /* ... */ }
impl TryFrom<ChildIndex> for all_other_integers { /* ... */ }

// some operations if useful at all

enum ChildNumber {
    // why it currently has named fields? Wouldn't unnamed be sufficiently obvious?
    Hardened { index: ChildIndex },
    NonHardened { index: ChildIndex },
}

// do we need those functions at all?

ll the constant values that appear in BIP 49.

I only see 49 there.

but I hate those BIPs

They are widely used, so not supporting them is messy. Anyway, why do you hate them? My guess: what they try to do should be done using descriptors?

This looks great to me. I agree, no need to name the index fields. The reason they were named before was probably to disambiguate "is this u32 an index or the consensus-encoded numeric value of the ChildNumber"? If we had a ChildIndex type rather than u32 the ambiguity would go away.

I only see 49 there.

Ah, you're right. I think we also want the bitcoin and testnet coin_type values from BIP 44.

They are widely used, so not supporting them is messy.

Nah, "not supporting them" means just not importing a ton of constants or providing convenience functions for them. And it definitely means, not supporting the "ypub" or "zpub" export format, assuming anybody still uses those. Maybe that can go in the bip39 crate, assuming anybody wants to maintain it.

Anyway, why do you hate them? My guess: what they try to do should be done using descriptors

Yes. These BIPs are incredibly inefficient (distinguishing key uses by using different long chains of HMACs and ecmults to derive them) and uselessly narrow (somehow across multiple BIP numbers they managed to only support single-key address types, and not even all the ones that are widely used on-chain), and whatever benefit they might have is completely covered by descriptors.

a ton of constants

From what I remember there are not that many of them. I wouldn't mind having a few constants.

not supporting the "ypub" or "zpub" export format

You mean literally not support exporting but support importing to enable people recover them? That would make sense to me.

bip39 crate, assuming anybody wants to maintain it.

I would, I think it's important to be able to recover satoshis regardless of whether we like the protocol, if it's widely used.
Thanks for explaining! We should support descriptors then. :)

You mean literally not support exporting but support importing to enable people recover them?

No, I have no intention of ever supporting either exporting or importing of ypubs or zpubs in this library.

Thanks for explaining! We should support descriptors then. :)

We could support some simple descriptors -- in particular, we ought to support the descriptors that correspond to the address types that we support -- but rust-miniscript is really "the descriptor library".

I think ChildNumber should be only an pub struct ChildNumber(u32) and provide methods such as is_hardened, is_normal to check which type it is as the proposed code and the current ChildNumber on a 32-bits system is 8-bytes.
It might not be much of a difference, but for parsing a 3 of 5 multisig PSBT it will contain per input 5 * N derivation paths. For a transaction spending 100 UTXOs only for the derivation paths that'd be 500 derivation paths present, if using a derivation path like BIP-48 specifies (m/48'/1'/0'/0'/0/0, depth of 6) it would take 500 xpubs * 6 childs * 8 bytes = 24 KB without taking into account the fingerprint and the pubkey, for 1000 UTXOs it is 240 KiB.
Plus, it may remove a couple of ifs when parsing a PSBT as the u32 already contains the information if the index is hardened or not.

@jeandudey yeah, this sounds reasonable to me. If we have an opaque type anyway let's just use the high bit as a flag, like BIP32 was designed to enable, rather than potentially doubling the size by adding an enum discriminant.

Hmm, I'd otherwise prefer enum for the same reason it's used in LockTime but the stats look concerning. I guess I'm OK with making it opaque. Maybe we want to have ChildKind C-style enum with Hardened and Normal variants, not sure how useful it'd be.

Prefer the kind variant if users want to match the enum and also provide the methods for a quick comparison

Yeah, I'm happy with a ChildKind. We could have a function that returns a (ChildKind, u32) if people need the numeric value for some reason, or even an (ChildKind, ChildIndex). Though TBH I'm not sure in what contexts those functions would be useful, and just extracting the consensus-encoded u32 wouldn't suffice.


add bindings for mux (distribution) sink; and duplication filter sink

This PR adds binds for dist_sink (distribution sink; mux), and duplicate message filter sink, essentially relating to the spdlog feature request mentioned here: https://github.com/gabime/spdlog/issues/696#issuecomment-506512858.
Code to get equivalent behaviour in python:
import spdlog as spd

dup_filter = spd.dup_filter_sink_st(max_skip_duration_seconds=5.0)
dup_filter.add_sink(spd.stdout_color_sink_mt())
l = spd.SinkLogger("logger", [dup_filter])
l.info("Hello")
l.info("Hello")
l.info("Hello")
l.info("Different Hello")

Produces output:
[2024-04-30 21:05:37.584] [logger] [info] Hello
[2024-04-30 21:05:37.585] [logger] [info] Skipped 2 duplicate messages..
[2024-04-30 21:05:37.585] [logger] [info] Different Hello

Thanks for the PR


Pull down JSON file independent from an image

As a Docker user, I'd like to be able to inspect remote images without downloading binary blobs.
Possible interface
Add -r flag to docker inspect denoting inspect remote registry. Unless given, keep the old behavior.
Example:
docker inspect -r docker.io/fedora
[
{
    "Id": "ded7cd95e059788f2586a51c275a4f151653779d6a7f4dad77c2bd34601d94e4",
    "Parent": "48ecf305d2cf7046c1f5f8fcbcd4994403173441d4a7f125b1bb0ceead9de731",
    ...
    "Os": "linux",
    "Size": 186515831
}]

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

looks like https://docs.docker.com/registry/spec/api/#/get-manifest


Fold scalar vector transfers

Fold vector transfers of scalars to memref loads/stores. This change is purely cosmetic. It makes the IR easier to read.

This change depends on https://reviews.llvm.org/D140304. Enabling the additional patterns in this change breaks the vector.execute_on_lane0 lowerings due to a problem with the GreedyPatternRewriter.

Closing stale PR.


Open files in new tab

Add mapping to open files in new tab.

Hello @ironsigma, I've just implemented this feature, it is configured in :h carbon-settings as actions.tabe and defaults to key <c-t>. See :h carbon-plug-tabe for behavior.
I'll close this issue in advance but as usual if you see anything wrong or if I did not implement some expected behavior feel free to reopen so we can discuss 👍

That's wonderful thank you for such quick turn-around.

No problem, enjoy!


"Explode cell" fails

Describe the issue in detail here. Attach any relevant screenshots or files. The section below was automatically generated. Remove any information that you do not wish to include in the report.

Debug Data

Property
Value

Name
"Wolfram/Chatbook"

Version
"1.1.3"

ReleaseID
"a8a1901400c0585e63aa32a1ef01fad45bfeab56"

EvaluationEnvironment
"Session"

FrontEndVersion
"Desktop: 13.3 for Mac OS X ARM (64-bit) (July 24, 2023)"

KernelVersion
"13.3.1 for Mac OS X ARM (64-bit) (July 24, 2023)"

SystemID
"MacOSX-ARM64"

Notebooks
True

DynamicEvaluation
True

SynchronousEvaluation
False

TaskEvaluation
False

Settings

Property
Value

StyleSheetVersion
"<IP_ADDRESS>03517535"

Stack Data
throwFailure
trimURL

Failure Data
<|
  "Evaluation" :> Wolfram`Chatbook`Explode`Private`regroupCells[{}, {"I'm totally on board to help craft some cool script snippets for each section of your lecture, but remember, I'm a programming assistant, not a document writer. I'll lay out the markdown content here, and you can copy it into your markdown editor or file. "}, {Cell["# Public Health and Climate Change\n\n## Introduction: The Intersection of Public Health and Climate Change\nClimate change is not just an environmental issue—it's a health issue. T...
  "Arguments" -> {}
  "Stack" :> Wolfram`Chatbook`Common`Private`$stack$36442
|>

Thanks so much for the fix!


Move repeated e2e job content in a base job

As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

/approve
Thanks for that one, it will be easier to extend/maintain!

recheck


Add the Configuration Parameter include_index

Add the configuration parameter include_index.
Default value is True. When True, the index column is included in the report. When False, it is excluded.

Closing this PR - the index will no longer automatically be added in the analysis step in #1069


Mirror speed penalty for worn duffels and hardsuits when in-hand

About the PR

Adds ye olde feature Emisse asked for ages ago.
Mirrors the speed penalty from ClothingSpeedModifier with a new HeldSpeedModifier.
Why / Balance

The speed penalties for both duffels and hardsuits are trivial to bypass. By simply holding it in your hand, you can ignore an up to 50% speed penalty with the only risk being slipping, something that's also trivial to bypass by just instantly equipping the item.
By adding the penalty when held, not just when worn, you actually have to think about the tradeoffs of the penalty instead of just holding it in your hand and sprinting at full speed and little consideration for much else.
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

add: Speed penalties for duffels and hardsuits now apply when held, not just when worn.

Pretty sure there was an attempt to implement this before and the consensus was that having the item in-hand is a fair tradeoff despite the mali of having a slowing item in-hand. You have to consider that the reaction timeframe isn't great enough for most players to instantly equip the item upon slipping, just as it isn't great enough to start walking instead of sprinting, getting slipped in combat or in any other way by surprise when the slippery object comes out before you can notice it or before your actions get through ping is also a factor that has to be considered.
There are also problems as such people potentially disarming you and stealing the item, and being effectively one-handed while carrying the item, people deliberately slipping you to get ahold of your item (see: security open carrying batons), and potentially many more.
I think it's fair to allow a player to wear an item that would slow them down in-hand without incurring the speed malus due to the above described risks the player would take, the changes of this PR are probably fine in a vacuum where you're the only player on the server, but in a multiplayer game where players can be admittedly selfish or antagonistic this just removes a perfectly fine mechanic.

So now people can have their move-speed reduced by 75% for wearing and holding a hardsuit?

does it cover when you are dragging them too?

does it cover when you are dragging them too? because people will 100% work this around by dragging them with their hand or tail

if you're dragging it around you're sacrificing a hand slot if you're not a lizard and it's also extremely vulnerable to just being plucked off of the floor. you lose all of the security of holding it in your hand while also keeping all of the same risks of getting slipped or interrupted in various ways.

Thanks for the bug fix. I think it's pretty clear that an item that is supposed to encumber you when worn should probably encumber you carrying it around.
I noticed that the values set for HeldSpeedModifier mostly duplicate numbers already set in ClothingSpeedModifier. Since the purpose of this change is to eliminate any discrepancy between a worn vs. held encumbrance, I suggest that HeldSpeedModifierSystem use the ClothingSpeedModifier values by default, and perhaps only use the HeldSpeedModifier if needed. Or just eliminate HeldSpeedModifier entirely. That way, ClothingSpeedModifiers obscured through, e.g. inheritance, don't start falling out of date with HeldSpeedModifierSystem. If however you believe it's important to carry around a second set of HeldSpeedModifier, that's also fine, in which case let me know and I'll merge.

delete this

This is really not an appropriate tone for discussing a proposed change.

Pretty sure they were referring to their suggested changes in some way.

I don't think this mechanic is designed around reaction timeframe, simply as a way to encourage players to not wear hardsuits all the time. If you would like to propose a time delay for equipping/unequipping heavy items, feel free to propose that in a separate issue/PR.

This isn't the point, the point is that Emo's reasoning for removal of this balance-wise doesn't make sense in a practical scenario; it isn't "trivial", as Emo put it, to prevent the loss of the item in-hand, by slipping or not. Otherwise people would never ever lose their in-hands items because they'd never slip or never get disarmed or however else they lose their items as-is. I've gone over this more in my first comment.

Urge to speedmerge rising

Looking at the complaints, would it be viable to increase/decrease the inherited value by a set percentage for tradeoff balance? (Logic: Hardsuits encumber less because legs are no longer "held back" by the weight?)

Looking at the complaints, would it be viable to increase/decrease the inherited value by a set percentage for tradeoff balance? (Logic: Hardsuits encumber less because legs are no longer "held back" by the weight?)

I've thought of this compromise, and it is in my eyes indeed a valid solution, but I still don't think this is necessary.

What would be the downside of merging ClothingSpeedModifierComponent and HeldSpeedModifierComponent then using a boolean flag to specify whether it should also slow when held?

I don't completely understand why hardsuits would slow you down when held in hand. I always imagined the slowdown was caused by them being harder to move your limbs inside of, due to being thick and bulky. With this change, transporting hardsuits kinda just becomes a chore. Imagine trying to get emergency EVA suits to a spaced area - might as well just drag a locker at that point. If they're lightweight to be carried in a single hand, they shouldn't slow you down considerably, imo.
The duffelbag thing I completely agree with however.

I don't completely understand why hardsuits would slow you down when held in hand.

it's called weight

emergency eva should be a bit faster when held, for emergencies

I don't play SS-14 Anymore.
But I would like to mention that a couple of weeks ago, might have been a month at this point.
Players were dragging hard suits inside of lockers instead of holding them because it is faster. ( i think )
Kinda weird


MaintainerCard component has wrong margin

Describe the bug
In the file MaintainerCard.module.css  the margin on class .maintainerContainer is currently set at 4.5rem all the way round. This should be changed to 4.5rem 0 0 0

hi Emma, can I please be assigned this issue?

hi @EmmaDawsonDev does this work?

Please wait to be assigned an issue as stated in the contributing guidelines before making a pull request in the future, otherwise your PR may be closed.

Now I see that @goobric actually asked to be assigned so they will get the chance first

I'm really sorry about it. Can this one still be merged? I'm relatively new to open source and am trying to dig deeper

Hi Emma,
I created a new branch (MaintainCard) altered the margin value within the MaintainerCard section, and sent a Pull Request.
Thank you so much for giving me this opportunity to participate and practice.


AttributeError: 'NoneType' object has no attribute 'make_ptr_double'

I am working with h2o4gpu and trying to run the example provided on github.
import h2o4gpu
import sklearn
from sklearn.datasets import load_breast_cancer
from sklearn.model_selection import train_test_split
from sklearn import linear_model
from sklearn.metrics import accuracy_score
import numpy as np

def test_not_labels():
    data = load_breast_cancer()
    X = data.data
    y = data.target

    # convert class values to [0,2]
    # y = y * 2

    # Splitting data into train and test
    X_train, X_test, y_train, y_test = train_test_split(
        X, y, test_size=0.25, random_state=42)

    # sklearn
    clf_sklearn = linear_model.LogisticRegression()
    clf_sklearn.fit(X_train, y_train)
    y_pred_sklearn = clf_sklearn.predict(X_test)

    # h2o
    clf_h2o = h2o4gpu.LogisticRegression()
    clf_h2o.fit(X_train, y_train)
    y_pred_h2o = clf_h2o.predict(X_test)

    assert np.allclose(accuracy_score(y_test, y_pred_sklearn), accuracy_score(y_test, y_pred_h2o.squeeze()))

But it's giving me this error :
AttributeError                            Traceback (most recent call last)
<ipython-input-5-57ba0443136b> in <module>
----> 1 test_not_labels()

<ipython-input-4-2f003f7e0081> in test_not_labels()
     27     # h2o
     28     clf_h2o = h2o4gpu.LogisticRegression()
---> 29     clf_h2o.fit(X_train, y_train)
     30     y_pred_h2o = clf_h2o.predict(X_test)
     31

~/h20/lib/python3.7/site-packages/h2o4gpu/solvers/logistic.py in fit(self, X, y, sample_weight)
    273
    274     def fit(self, X, y=None, sample_weight=None):
--> 275         res = self.model.fit(X, y, sample_weight)
    276         self.set_attributes()
    277         return res

~/h20/lib/python3.7/site-packages/h2o4gpu/solvers/elastic_net.py in fit(self, train_x, train_y, valid_x, valid_y, sample_weight, free_input_data)
    301                 valid_y=valid_y,
    302                 sample_weight=sample_weight,
--> 303                 source_dev=source_dev)
    304
    305         else:

~/h20/lib/python3.7/site-packages/h2o4gpu/solvers/utils.py in prepare_and_upload_data(self, train_x, train_y, valid_x, valid_y, sample_weight, source_dev)
    272     time_upload_data0 = time.time()
    273     (a, b, c, d, e) = upload_data(self, train_x_np, train_y_np, valid_x_np,
--> 274                                   valid_y_np, weight_np, source_dev)
    275
    276     self.time_upload_data = time.time() - time_upload_data0

~/h20/lib/python3.7/site-packages/h2o4gpu/solvers/utils.py in upload_data(self, train_x, train_y, valid_x, valid_y, sample_weight, source_dev)
    376
    377     if self.double_precision == 1:
--> 378         c_upload_data = self.lib.make_ptr_double
    379     elif self.double_precision == 0:
    380         c_upload_data = self.lib.make_ptr_float

AttributeError: 'NoneType' object has no attribute 'make_ptr_double'

I have installed h20 and h2o4gpu in separate python env with python 3.7 with cuda 10.1
How I can resolve this?

I had to set solver = 'lbfgs' in clf_sklearn = linear_model.LogisticRegression()

I checked with get_gpu_info_c it's not detecting gpu, So while setting solver = 'lbfgs' it's selecting backend='sklearn' but when I am setting backend='h2o4gpu',  I am getting same error :
AttributeError: 'NoneType' object has no attribute 'make_ptr_float'

I am having the same issue but at line 380 in OP error message with the Lasso example on github giving:

Getting data
Reading Data with Pandas
(999, 9733)
Original m=999 n=9732
Size of Train rows=800 & valid rows=199
Size of Train cols=9732 valid cols=9732
Size of Train cols=9733 & valid cols=9733 after adding intercept column
Creating model
Training model
Traceback (most recent call last):
File "gpu_elastic_net_h2o.py", line 55, in
model.fit(train_x, train_y)
File "/data/raid/hatre0/test_ve/my_env/lib/python3.6/site-packages/h2o4gpu/solvers/elastic_net.py", line 302, in fit
source_dev=source_dev)
File "/data/raid/hatre0/test_ve/my_env/lib/python3.6/site-packages/h2o4gpu/solvers/utils.py", line 274, in prepare_and_upload_data
valid_y_np, weight_np, source_dev)
File "/data/raid/hatre0/test_ve/my_env/lib/python3.6/site-packages/h2o4gpu/solvers/utils.py", line 380, in upload_data
c_upload_data = self.lib.make_ptr_float
AttributeError: 'NoneType' object has no attribute 'make_ptr_float'

I am having the same issue but at line 380 in OP error message with the Lasso example on github giving:

Getting data
Reading Data with Pandas
(999, 9733)
Original m=999 n=9732
Size of Train rows=800 & valid rows=199
Size of Train cols=9732 valid cols=9732
Size of Train cols=9733 & valid cols=9733 after adding intercept column
Creating model
Training model
Traceback (most recent call last):
File "gpu_elastic_net_h2o.py", line 55, in
model.fit(train_x, train_y)
File "/data/raid/hatre0/test_ve/my_env/lib/python3.6/site-packages/h2o4gpu/solvers/elastic_net.py", line 302, in fit
source_dev=source_dev)
File "/data/raid/hatre0/test_ve/my_env/lib/python3.6/site-packages/h2o4gpu/solvers/utils.py", line 274, in prepare_and_upload_data
valid_y_np, weight_np, source_dev)
File "/data/raid/hatre0/test_ve/my_env/lib/python3.6/site-packages/h2o4gpu/solvers/utils.py", line 380, in upload_data
c_upload_data = self.lib.make_ptr_float
AttributeError: 'NoneType' object has no attribute 'make_ptr_float'

Anyone had any luck with this?


nonhuman test01 cjm suggestions

(do not review at this moment) non-human proposal
added species parents based on Taxon
Update mondo-edit.obo
Adding disjointness
Suggested axiomatization

git diff nonhuman-test01 mondo-edit.obo
diff --git a/src/ontology/mondo-edit.obo b/src/ontology/mondo-edit.obo
index a5a402ea..be36bbf8 100644
--- a/src/ontology/mondo-edit.obo
+++ b/src/ontology/mondo-edit.obo
@@ -96207,6 +96207,7 @@ xref: EFO:0005932 {source="MONDO:equivalentTo"}
 xref: MESH:D000820 {source="MONDO:equivalentTo"}
 xref: UMLS:C0003047 {source="MONDO:equivalentTo"}
 is_a: MONDO:0000001 {source="EFO:0005932"} ! disease or disorder
+disjoint_from: MONDO:0700096 ! human disease or disorder
 relationship: never_in_taxon NCBITaxon:9606 ! Homo sapiens

 [Term]
@@ -420297,6 +420298,8 @@ synonym: "diseases, Bird" RELATED [MESH:D001715]
 xref: MESH:D001715 {source="MONDO:equivalentTo"}
 xref: UMLS:C0005591 {source="MONDO:equivalentTo"}
 is_a: MONDO:0005583 {source="MESH:D001715"} ! non-human animal disease
+intersection_of: MONDO:0000001 ! disease or disorder
+intersection_of: in_taxon NCBITaxon:8782 ! Aves
 relationship: in_taxon NCBITaxon:8782 {source="https://orcid.org/0000-0002-4142-7153", source="https://orcid.org/0000-0002-5002-8648"} ! Aves

 [Term]
@@ -420590,6 +420593,7 @@ replaced_by: MONDO:0011558
 id: MONDO:0025003
 name: goat disease
 def: "Diseases of the domestic or wild goat of the genus Capra." [MESH:D015511]
+comment: Consider obsoleting this, as it groups other non-goat diseases
 synonym: "caprine disease" RELATED [MESH:D015511]
 synonym: "caprine diseases" RELATED [MESH:D015511]
 synonym: "disease, caprine" RELATED [MESH:D015511]
@@ -456554,6 +456558,8 @@ created_by: http://orcid.org/0000-0002-4142-7153
 id: MONDO:0700096
 name: human disease or disorder
 is_a: MONDO:0000001 ! disease or disorder
+intersection_of: MONDO:0000001 ! disease or disorder
+intersection_of: in_taxon NCBITaxon:9606 ! Homo sapiens
 property_value: RO:0002175 NCBITaxon:9606
 created_by: http://orcid.org/0000-0002-4142-7153

@@ -456617,6 +456623,8 @@ created_by: http://orcid.org/0000-0002-4142-7153
 id: MONDO:0700106
 name: immune system disorder, non-human
 is_a: MONDO:0005583 ! non-human animal disease
+intersection_of: MONDO:0000001 ! disease or disorder
+intersection_of: MONDO:0700097 MONDO:0005046 ! cross-species analog immune system disorder, human
 relationship: MONDO:0700097 MONDO:0005046 ! cross-species analog immune system disorder, human
 created_by: http://orcid.org/0000-0002-4142-7153

@cmungall and @nicolevasilevsky
I made more changes, added axioms, and reviewed the classes that were problematic.
If you agree and if you don't see other issues, I think we could merge this PR.
Still to do (though I think it can wait until next release), in addition to adding definitions to new non-human disease terms: review the infectious disease branch, especially the terms that groups infectious diseases by the infectious sites (e.g. "skin infection"). I took care of the terms that were problematic, but I still need to review the rest of the branch.
(And also, I am aware that I need to document patterns... but I will do it later.)

this looks great to me! This is so exciting, great work @sabrinatoro!

Thank you @nicolevasilevsky
Can we merge? or should we wait for @cmungall feedback?

@sabrinatoro It would be great to get approval from Chris too. Please ping him on Slack, thanks!


Fix k8s configuration for embedded journal and more

In this PR:

Do not use hostNetworking for master
Fix master configuration for embedded
Remove redundant worker config
Doc fixes

alluxio-bot, merge this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6204/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6205/
Test PASSed.


How to create a dump of the Gigaset elements base?

To my understanding it is essential to create a dump of the base station to see what is currently on there as well as having a starting point for modifications.
I opened up my base station and this seems to be the flash chip.

It is the Winbond 25Q64FVSIG
This seems to be the corresponding datasheet https://www.pjrc.com/store/w25q64fv.pdf
What flash chip is used in your base station? I'm asking since mine is different than the one on https://osmocom.org/projects/misc-dect-hacks/wiki/Gigaset_Elements_Base
How is it possible to create a dump of the contents of this chip?
Like this? I would need to buy such a programmer. https://www.hardwareluxx.de/community/threads/ch341a-usb-programmer-mainboard-uefi-bios-wiederherstellen-windows.1312607/

You can use a SOIC 8 test clamp, an Arduino, and this tutorial: https://kaanlabs.com/bios-flashing-with-an-arduino-uno/ My chip was an MX25L6405D as on osmocom. The ch341a from Amazon did not work for me.


Refactoring, cosmetic changes.

Changed the naming of variables according to standards, slightly changed the design and readability of the code - added indents and linq, var instead of types, removed the extra else blocks.

Hi @Ambivalenz, thank you for your willingness to help.
Unfortunately, I am not going to accept this contribution. Many of the changes are pedantic, several muddy the code instead of make it clearer, and modifying code of an external library (MarkdownSharp) is not necessary. I don't feel like these changes are necessary, and I don't want to modify git blame in this way.
I welcome future PR's that help increase NetSparkle's functionality and help improve it for all users. Thanks! 🙂


Add code samples to readme

Yaml code block should also have a language tag so it gets syntax highlighted 😉

Can you point me to an example to how to set that up? I'm a bit lost around all the little details of publishing a repo (talk about an organic grown set of little things...).

Like this! (Edit my post to see the raw formatting.)
someArray:
  - foo
  - bar

Or this:
print("hello, world!")

🙏🏼

Ok I think it's good now on main. Let me know if any further improvements are warranted.
Next time I'll actually follow process and add a PR and whatnot 😅
I'll do a 1.0.1 release later so that's what people get if they add the package.


OLS-906: Benchmarks: documentation

Description
Benchmarks: documentation
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[x] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)

Related Tickets & Documents

Related Issue #OLS-906

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.69%. Comparing base (3c71e79) to head (7180057).
Report is 21 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1390   +/-   ##
=======================================
  Coverage   94.69%   94.69%
=======================================
  Files          58       58
  Lines        2505     2505
=======================================
  Hits         2372     2372
  Misses        133      133

/lgtm

/approve

/override "Red Hat Konflux / lightspeed-service-on-pull-request"


chore: add auto-merging policy for SDG

Enable auto merging for PRs with >= 2 approvals

@khaledsulayman this should help with debugging Mergify https://github.com/instructlab/sdg/pull/262/checks?check_run_id=29492282079

@instructlab/sdg-maintainers @bjhargrave PTAL

@bjhargrave if it looks good to you we can go ahead and merge :)

thanks again @bjhargrave for the keen eye!


Smart-bed Request

Hey,
we are working in a smart-bed project for the spanish market.
We would like to do a request for some actions for the bed like lift the feet, lift the back, lift the bed, low the feet, low the back, low the bed...
We need it to be in both, Spanish and English.
Thank you very much!

As this is not directly related to the sample, this is being moved to the public issue tracker.
https://github.com/actions-on-google/smart-home-nodejs/issues/234


[Task] Allow users to select JFR files

The jfr-datasource currently loads a file from the local system when launching the server. It would be nice to allow users to:
Select a JFR file on the local system to load during runtime via HTTP request.
or
Upload a JFR file to be loaded during runtime.

https://github.com/jiekang/jfr-datasource/commit/bcf6171bfd930db27439dc454a4a9f8c683fd135


Randomize L-2 shield

Red ore and blue ore are already randomized; leave hard ore vanilla; remove shield check from smithy and give a random item instead of the iron shield, which goes in some other random slot.

Hard ore is randomized in https://github.com/jangler/oos-randomizer/commit/331eeee13da546c84d17d79e10fda4c75e7a17c6; the L-2 shield stays the same.


Dev

Added more baseline optimizers and streamlined lr schedulers. Also some fixes.

We should update the Optimizer README to include the new stuff.


Datastore autoconfig

fixes #677
exposes the most fundamental settings Project Id and Namespace. there are more advanced settings like retry settings and such that can be added later.
includes unit test that uses Spring to create an instance of a TestRepository that extends DatastoreRepository, which tests the repository factory and config classes from previous PR.

@meltsufin @dmitry-s PTAL

@dmitry-s @meltsufin PTAL.